Root System update

josh007cl · Mar 17, 2013

No I just installed superuser from the app store. I just tried a root checker and it said not rooted. I did everything in the instructions except flash a rom since I want to stay stock (with root).

mogul218 · Mar 17, 2013

ramjet, I installed jbear's 1.50 and now stuck in boot loops again.

Edit: My bootloader says 1.58. Maybe I d/l the wrong file.

ramjet73 · Mar 17, 2013

josh007cl said:
No I just installed superuser from the app store. I just tried a root checker and it said not rooted. I did everything in the instructions except flash a rom since I want to stay stock (with root).

You have to flash a custom recovery and a superuser zip if you want to use the stock ROM and run apps like WiFi Tether that require root. Use one of the guides for rooting to do those two steps and you should be fine.

ramjet73

ramjet73 · Mar 17, 2013

mogul218 said:
ramjet, I installed jbear's 1.50 and now stuck in boot loops again.

Did you format cache+dalvik in recovery after changing hboots? That hboot should be fine for flashing and booting GB and AOSP based ROM's and many other users, including myself, are doing that.

Edit: I just saw your edit that you had the wrong hboot.

ramjet73

josh007cl · Mar 17, 2013

ramjet73 said:
You have to flash a custom recovery and a superuser zip if you want to use the stock ROM and run apps like WiFi Tether that require root. Use one of the guides for rooting to do those two steps and you should be fine.

ramjet73

Okay, I flashed the SU zip now and am all set. Thanks!

mogul218 · Mar 17, 2013

Okay so I flashed the 1.50 hboot and stuck in boot loop still. Should I try the stock 1.50 hboot?

ramjet73 · Mar 17, 2013

mogul218 said:
Okay so I flashed the 1.50 hboot and stuck in boot loop still. Should I try the stock 1.50 hboot?

I don't think that's the problem.

Are you still flashing the same CM10 ROM? Maybe you should try g60's version and see if that will boot with the JBear 1.50.5050 hboot. If the new firmware is affecting the ROM in some way this will be the first case of that AFAIK, but the restore using one of those apps is more likely to work with another CM10 ROM.

ramjet73

circleoflife · Mar 17, 2013

mrg666 said:
Download the OTA but don't start the update process. Open the OTA zip file which is in your sdcard/download directory. I recommend copying the file to your PC and opening it on your PC with 7zip. There is another zip file in it called framework.zip. Open firmware.zip and you will find recovery.img in it. Copy that recovery.img to either your sdcard or your PC. If you use PC, you can use the fastboot command "fastboot flash recovery recovery.img" with USB connection to fastboot. Or, if you install Flash Image GUI on your phone, you can copy the recovery.img file to your sdcard and flash directly from your phone using Flash Image GUI.

I did that and it seemed to be updating then I got a screen with a red triangle exclamation point.

guess it's because I'm rooted?

mogul218 · Mar 17, 2013

I had AOSP up and running then I ran into the issue with the hboot. So now I have my original CM10.1 that I started out with before the firmware upgrade up and running. Do you think it is safe for me to use 4ext to restore the /data at this point?

remanifest · Mar 17, 2013

Some issues with the new firmware have been because of kernels. I don't know what kernels are used by what ROMs, but I know buttered toast (16.3) is a working kernel with the new firmware.

Hedied4me · Mar 17, 2013

remanifest said:
Some issues with the new firmware have been because of kernels. I don't know what kernels are used by what ROMs, but I know buttered toast (16.3) is a working kernel with the new firmware.

And for those running 4.2.2 there is a test kernel (based off of 16.3) of buttered toast that works with this new firmware.

ramjet73 · Mar 17, 2013

mogul218 said:
I had AOSP up and running then I ran into the issue with the hboot. So now I have my original CM10.1 that I started out with before the firmware upgrade up and running. Do you think it is safe for me to use 4ext to restore the /data at this point?

It won't hurt to try but I'd suggest doing a nandroid of what you currently have working before trying that. Based on past experience the booting problem seems to be in the data partition so that still may not work.

ramjet73

mogul218 · Mar 17, 2013

Hedied4me said:
And for those running 4.2.2 there is a test kernel (based off of 16.3) of buttered toast that works with this new firmware.

Link?

ramjet73 · Mar 17, 2013

remanifest said:
Some issues with the new firmware have been because of kernels. I don't know what kernels are used by what ROMs, but I know buttered toast (16.3) is a working kernel with the new firmware.

I think the issues are more with custom kernels working with the updated stock ROM. It's possible but not likely that the updated firmware (minus the 1.58 hboot) would cause problems with other ROM's and kernels.

ramjet73

mrg666 · Mar 17, 2013

circleoflife said:
I did that and it seemed to be updating then I got a screen with a red triangle exclamation point.

guess it's because I'm rooted?

The read triangle and exclamation mark means there was an error. Press volume-up and power buttons to go into the recovery when you see the red triangle. Then, you can see the details of the error message. It will tell you where and why it failed.

I have done the OTA update with rooted stock ROM, unlocked bootloader, and MiRaGe kernel installed. As long as you can resolve the problems in the error messages, OTA will complete.

circleoflife · Mar 17, 2013

mrg666 said:
The read triangle and exclamation mark means there was an error. Press volume-up and power buttons to go into the recovery when you see the red triangle. Then, you can see the details of the error message. It will tell you where and why it failed.

I have done the OTA update with rooted stock ROM, unlocked bootloader, and MiRaGe kernel installed. As long as you can resolve the problems in the error messages, OTA will complete.

Saying assert failed: apply_patch_check("/system/app/plusone.asp",

then gives me a whole bunch of numbers and letters...

e:error in (the update file name)
(status 7)
installation aborted.

This is in Android system recovery <3e>

mrg666 · Mar 17, 2013

circleoflife said:
Saying assert failed: apply_patch_check("/system/app/plusone.asp",

then gives me a whole bunch of numbers and letters...

e:error in (the update file name)
(status 7)
installation aborted.

This is in Android system recovery <3e>

/system/app/plusone.asp should be plusone.apk. is this a typo or did you rename or delete that file.

circleoflife · Mar 17, 2013

mrg666 said:
/system/app/plusone.asp should be plusone.apk. is this a typo or did you rename or delete that file.

Oops typo meant apk. Looks like it belong to Google+.So it looks like I need to find this apk..put it back into the system folder and try the update again, right?

Can you upload and share the file to me?

mrg666 · Mar 17, 2013

circleoflife said:
Oops typo meant apk. Looks like it belong to Google+.So it looks like I need to find this apk..put it back into the system folder and try the update again, right?

Yes, you need to restore that file and possibly some others if you have deleted/modified more. If you have a backup you can extract the missing files from there.

The other option is just doing an RUU and taking the OTA over pristine ROM. But in that case, you will need to restore your personal settings and apps.

Edit: You can download the missing PlusOne.apk at the following link. This was the original version in the stock ROM.
http://www.mediafire.com/?p84zd1c5hfmj3h4

ramjet73 · Mar 17, 2013

mrg666 said:
The other option is just doing an RUU and taking the OTA over pristine ROM. But in that case, you will need to restore your personal settings and apps.

If you are already rooted and can use a utility like Titanium Backup or MyBackup Root you might want to consider this option. Trying to apply the complete OTA update to a modified stock ROM can get quite complicated.

Also, if you haven't seen the other warnings already, updating to the March OTA with S-ON may jeopardize your chances of getting S-OFF in the future since the JuopunutBear wire trick is not officially supported for VM users once the 1.58 hboot is installed by that OTA.

ramjet73

Droidula · Mar 18, 2013

mrg666 said:
Download the OTA but don't start the update process. Open the OTA zip file which is in your sdcard/download directory. I recommend copying the file to your PC and opening it on your PC with 7zip. There is another zip file in it called framework.zip. Open firmware.zip and you will find recovery.img in it. Copy that recovery.img to either your sdcard or your PC. If you use PC, you can use the fastboot command "fastboot flash recovery recovery.img" with USB connection to fastboot. Or, if you install Flash Image GUI on your phone, you can copy the recovery.img file to your sdcard and flash directly from your phone using Flash Image GUI.

I will try this within the next few days, thank you! Hoping this will improve my reception a bit, I seem to get a lot of voicemails without the phone ever ringing.

ramjet73 said:
If you are already rooted and can use a utility like Titanium Backup or MyBackup Root you might want to consider this option. Trying to apply the complete OTA update to a modified stock ROM can get quite complicated.

I keep wondering when I see people recommending using TiBu after the update whether that is a good idea? If I had to end up running the RUU to take the OTAs, I would probably use TiBu to restore most of my apps, but other than maybe email, I think I'd try to leave off restoring the other settings and system apps. Is it possible that restoring the settings might overwrite some newly tweaked files? Or even some tweaked stock apps?

circleoflife · Mar 18, 2013

mrg666 said:
Yes, you need to restore that file and possibly some others if you have deleted/modified more. If you have a backup you can extract the missing files from there.

The other option is just doing an RUU and taking the OTA over pristine ROM. But in that case, you will need to restore your personal settings and apps.

Edit: You can download the missing PlusOne.apk at the following link. This was the original version in the stock ROM.
PlusOne.apk

Thanks for all your help!!!! I really do appropriate it a lot!
Now it says assert failed on system/bin/debuggerd :mad:

Weird It's in the folder and I have another one too called debuggered.bin. I think it was modified when I rooted the phone. Now to find this file from the stock rom.

Is debuggered.bin the backup (original file?) Just have to change the files around?

mrg666 · Mar 18, 2013

circleoflife said:
Thanks for all your help!!!! I really do appropriate it a lot!
Now it says assert failed on system/bin/debuggerd

Weird It's in the folder and I have another one too called debuggered.bin. I think it was modified when I rooted the phone. Now to find this file from the stock rom.

Is debuggered.bin the backup (original file?) Just have to change the files around?

Nothing touches that file (debuggerd) normally. It seems to me that you might not have the first OTA (1.14.652.0). Please check your build number (Settings > About Phone > Software information > More > Build number) If it is 1.13, you need the 1.14 OTA first before applying 2.95. Otherwise, I highly recommend you to do the RUU before applying the OTA update. There seems to be some corruption in your OS.

circleoflife · Mar 18, 2013

mrg666 said:
Nothing touches that file (debuggerd) normally. It seems to me that you might not have the first OTA (1.14.652.0). Please check your build number (Settings > About Phone > Software information > More > Build number) If it is 1.13, you need the 1.14 OTA first before applying 2.95. Otherwise, I highly recommend you to do the RUU before applying the OTA update. There seems to be some corruption in your OS.

It's 1.14.652.0 710RD. I checked the modify date of debuggered and it was right around the time I rooted the phone all the other files in the folder have a modified date of May 2012.

mrg666 · Mar 18, 2013

circleoflife said:
It's 1.14.652.0 710RD. I checked the modify date of debuggered and it was right around the time I rooted the phone all the other files in the folder have a modified date of May 2012.

This is interesting, afaik, nothing touches that file for rooting. Anyway, if you want to keep going, here is the debuggerd from 1.14 build.

debuggerd

Root System update

Newbie

Newbie

Android Expert

Android Expert

Newbie

Newbie

Android Expert

Member

Newbie

Android Expert

Member

Android Expert

Newbie

Android Expert

Android Enthusiast

Member

Android Enthusiast

Member

Android Enthusiast

Android Expert

Android Enthusiast

Member

Android Enthusiast

Member

Android Enthusiast

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads