Related
Hey everybody! I went to stock from CyanogenMod Nightlyes, and flashed stock 2.3.2 nandroid.
Then I flashed the 2.3.3, it works just fine! But my bootloader is still unlocked!
First thing that i thank was just to install Superuser, but it doesen't work.
I connected it to Pc in fastboot mod, and ran install-superboot-windows.bat (one click root)
But now, it just stuck in Google logo, and I don't know what to do next... I tryed to pull out the battery, nothing...
Update: just reflashed recovery via fastboot flash recovery recovery.img, and got the CWM. Now restoring to 2.3.2.
I think that we can just flash CWM after update, and then install superuser. I'll try and will ask you about any changes.
Update 2:: So, it ran just fine, first installed 2.3.2, then updated it to 2.3.3, and then flashed CWM. It boots up just fine, but in CWM I tried to install superuser.zip, it says: invalid to install
maybe reinstall your backup from CWM?
also the one click root you need to be in a rom and using adb
I did the same thing and ended up in the same situation...ive fixed like this...downloaded odin got back to stock 2.3.1 then downloaded the update,flashed it through stock recovery then flashed recovery.img....flashed su and everything is back on normal now
Hope it helps
Sent from my Nexus S using XDA App
If you unlock already, it is very easy to root again
1. fastboot boot recovery.img
2. flash su.zip
3. reboot
all done
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
2.3.3 root question
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
This does not belong in development.
Sent from my MattedBlues CM7 Google Nexus S!
I have a question is there a way to make the phone as if it was never messed about with, just incase it was ever needed to get repaired under the warrenty
Trinitronik said:
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
Click to expand...
Click to collapse
mount /system inside of clockwork then try.
Sent from my Nexus S using XDA App
Jnowak1981 said:
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
Click to expand...
Click to collapse
Try this..
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>Do not reboot ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
4) Reboot..
Click to expand...
Click to collapse
I am just posting the concept..you need to find out the details steps
Ill keep 2.3.2 until than
Sent from my Nexus S using XDA App
Follow the link, i managed to retain root after 2.3.3 update.
http://forum.xda-developers.com/showpost.php?p=11626567&postcount=70
Code:
I manage to keep the root for 2.3.3 with the flashing sequence listed below.
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>After applying update DO NOT REBOOT ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
=> This step is to reapply Superuser.apk permission setting
4) Reboot..
I am highlighting the concept, for details inter steps..please refer to the first post on the link.
2.3.3 root
is there a method to root 2.3.3 or is it to early i tried allgamer way but it failed
Or you can simply restore 2.3.3 its in the development forum. It had root already on it
Sent from my Nexus S using XDA App
There is a 2.3.3 rooted nandroid backup in development section.
Sent from my Nexus S using XDA App
well tryind to do from 2.3.3
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
kaimyn said:
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
Click to expand...
Click to collapse
If I were currently locked bootloader, I would run a full titanium backup of apps+data, and copy over your entire sdcard contents to your pc, along with the titanium backups (remember, the oem unlock wipes the sdcard also, not just internal space).
Then unlock the bootloader. Easiest way to deal with custom recovery in the future.
There are steps in the 2.3.3 link thread here describing how you can update and get root back even with the locked bootloader; which might be less of a hassle then going through a wipe.
squattingb said:
I tried to do this in clockwork but the installation kept failing, I was getting some messages about "assert failed", wasn't quite clear so I couldn't really make out what the problem was, does anyone have any insights into this? I downloaded the update from http://forum.xda-developers.com/showthread.php?p=11566707 for Nexus S.
Click to expand...
Click to collapse
I'm having the same issue. Any idea how to fix this?
Just load the Nandroid as charlieb620 said. If your already on 2.3.3 you won't lose nowt, just backup your data first.
Cant auto update right when I click update now I get a force close I think I might of deleted something important from TB.... and yes I am rooted when I used tb to delete stuff
Sent from my R800x using XDA App
Use titanium to backup all your apps. Flash full stock tft, lock bootloader, run update, unlock bootloader, root, restore titanium backup.
Sent from my R800x using XDA App
Trying to run fastboot to either unlock my bootloader or run recoveryPLAY comes back with a fail after I did the exact same thing. Relocked my bootlaoder, reflashed the ftf back to stock 2.3.2 then ota'd. Now I am unable to unlock my bootloader and to get into recoveryPLAY as it comes back as "Failed, phone must be rooted".
If I were you I would wait until there is a 2.3.3 ftf file that has root embedded into it or a sure fire way to root 2.3.3, as now i can neither root nor unlock my phones bootloader.
I was able to update and re-root using the exact method I described, except I didn't do a titanium backup.
Sent from my R800x using XDA App
Ain't there a way to just do a factory reset and it will bring everything back?
Sent from my R800x using XDA App
hi. i'm pretty new to all this. a few months ago, i unlocked the bootloader on my atrix 4g and also rooted it. i then flashed the ICS CM7 rom using cwm. after a few days of playing with the new rom, i decided to go back to 2.3.4 by flashing the 2.3.4 fruitcake. i see now that 2.3.6 ota update is available when i check for updates from my phone. if i install this ota update, will i brick my phone? i still have the unlocked bootloader but no longer have root.
Applying the 2.3.6 OTA on a fruitcake 2.3.4 may cause a soft brick/boot loop. IMO wait until others respond with more definitive results. Don't be the first guinea pig . I had a stock, locked and rooted 2.3.4 prior to the 2.3.6 update.
nvd425 said:
hi. i'm pretty new to all this. a few months ago, i unlocked the bootloader on my atrix 4g and also rooted it. i then flashed the ICS CM7 rom using cwm. after a few days of playing with the new rom, i decided to go back to 2.3.4 by flashing the 2.3.4 fruitcake. i see now that 2.3.6 ota update is available when i check for updates from my phone. if i install this ota update, will i brick my phone? i still have the unlocked bootloader but no longer have root.
Click to expand...
Click to collapse
Don't quote me on this, but if you flashed back to 2.3.4 using RSD and then applied the update you should be okay. Caveat emptor, as always, and do it at your own risk.
There may be some unknown consequences, though. Maybe flashing back to 2.3.4 after applying the update will brick your phone, like the 2.3.4 update did with 1.8.3. You will definitely lose root, and from what I hear some of the old rooting methods don't work anymore.
If you are rooted and unlocked and had modified systems flashing worth RSD lite to get back to stock is the way to go before the update. Flashing back to .91 after installing the update WILL brick the phone for sure so don't.
Sent From Rob's ATRIX.
If you are using fruitcake 2.3.4, the OTA update to 2.3.6 will work, as the difference between a fruitcake 2.3.4 and the official one is that it does not touch the recovery and boot. As your phone was running official 2.3.4 before cm7, the changes to boot and recovery are already in place. The only possible downside is that you will not be able to roll back to "official" 2.3.4. You will have to flash CWM and flash fruitcake 2.3.4 to roll back.
This isn't stock ICS is it?
No, it is the latest gingerbread update.
Dogie52 said:
This isn't stock ICS is it?
Click to expand...
Click to collapse
Miguelyl said:
No, it is the latest gingerbread update.
Click to expand...
Click to collapse
Alright thanks
Miguelyl said:
If you are using fruitcake 2.3.4, the OTA update to 2.3.6 will work, as the difference between a fruitcake 2.3.4 and the official one is that it does not touch the recovery and boot. As your phone was running official 2.3.4 before cm7, the changes to boot and recovery are already in place. The only possible downside is that you will not be able to roll back to "official" 2.3.4. You will have to flash CWM and flash fruitcake 2.3.4 to roll back.
Click to expand...
Click to collapse
I think I get it...almost .
Could you verify #2 and fill in #3?
1) locked, stock 2.3.4: recovery and boot are stock
2) unlocked, flash CM7 or other ROMS: recovery and boot are NOT stock...applying the 2.3.6 OTA at this point can semi-fubar your phone with a bootloop and/or softbrick
3) fruitcake 2.3.x : recovery and boot are ???...applying the OTA = ???
I searched xda and could not find anything stating that applying future OTAs over a fruitcake 2.3.x will be successful. My search skillz could be lacking, so apologies ahead of time .
2) You cannot OTA update from those roms, there is no way to do it. I doubt anyone will even try to update.zip the OTA over CM7 or any other custom rom.
3) Recovery is non stock, boot is stock (as last official update installed). After the update, stock recovery will be installed, boot will change to 2.3.6 so it will prevent downgrade. Will have to flash CWM again to have access to custom roms and fruitcakes.
This is as I understand it. If anyone has more info you are welcome to share.
gnahc79 said:
I think I get it...almost .
Could you verify #2 and fill in #3?
1) locked, stock 2.3.4: recovery and boot are stock
2) unlocked, flash CM7 or other ROMS: recovery and boot are NOT stock...applying the 2.3.6 OTA at this point can semi-fubar your phone with a bootloop and/or softbrick
3) fruitcake 2.3.x : recovery and boot are ???...applying the OTA = ???
I searched xda and could not find anything stating that applying future OTAs over a fruitcake 2.3.x will be successful. My search skillz could be lacking, so apologies ahead of time .
Click to expand...
Click to collapse
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
Miguelyl said:
2) You cannot OTA update from those roms, there is no way to do it. I doubt anyone will even try to update.zip the OTA over CM7 or any other custom rom.
3) Recovery is non stock, boot is stock (as last official update installed). After the update, stock recovery will be installed, boot will change to 2.3.6 so it will prevent downgrade. Will have to flash CWM again to have access to custom roms and fruitcakes.
This is as I understand it. If anyone has more info you are welcome to share.
Click to expand...
Click to collapse
Well, crap. Wish I had seen this beforehand. My phone is currently stuck with 3 green Chinese characters on the screen with the goapk website subtitle.
Have unlocked bootloader, upgraded to previous firmware OTA (didn't flash pudding), no ROMs.
Any suggestions would be much appreciated.
Miguelyl said:
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
Click to expand...
Click to collapse
thanks for the update. that's what I thought...once you unlock you can never apply any future OTA updates. After unlocking you can get 'stock' only through fruitcake.
You are stuck on recovery. Goapk is tenfar cwm recovery. Fastboot wipe and then flash 2.3.4 fruitcake.
Eionai said:
Well, crap. Wish I had seen this beforehand. My phone is currently stuck with 3 green Chinese characters on the screen with the goapk website subtitle.
Have unlocked bootloader, upgraded to previous firmware OTA (didn't flash pudding), no ROMs.
Any suggestions would be much appreciated.
Click to expand...
Click to collapse
---------- Post added at 10:31 PM ---------- Previous post was at 10:24 PM ----------
You can normally rsd lite to 4.5.91 but there are reports that after doing that, updating
to 4.5.141 results in a brick. Some have succeeded, some don't.
So the safe route is to wait for fruitcake.
gnahc79 said:
thanks for the update. that's what I thought...once you unlock you can never apply any future OTA updates. After unlocking you can get 'stock' only through fruitcake.
Click to expand...
Click to collapse
For those afraid of losing root
It is true you will lose root after updating and the current root methods no longer work. However, there is one method that still does; the fastboot method. Instructions and files can be found here:
http://www.atrixforums.com/forum/mo...ons-including-stock-locked-2-3-4-2-3-6-a.html
(Note: Instructions are right after Pete's Root Tools Method)
In order for this to work you will need to make sure that all traces of root has been removed from you phone or it will fail to write su to the correct directory due to not enough memory being available. There are a few ways to remove all traces of root. One way is to flash the sbf file of the current version you are on. After flashing just uninstall superuser like you would uninstall any other app.
Another method of completely removing all traces of root is through the preinstall root method. It can be found at the same link from above under How to Un-root after using the /preinstall root method (I think this will only work if you used the fastboot method to gain root, I have not tried it myself).
You could also use the Motorola Software Update Tool to flash the update which should remove all traces of root. It can be found here:
http://direct.motorola.com/hellomot...SoftwareUpdateforATTATRIX4Gversion.4.5.91.pdf
As of right now the fastboot method seems to be the only way to root this version of the software. I actually tried all the current methods including the recent Motofail method that was discovered by Dan Rosenburg, but all have failed.
As a side note, those that are waiting for an official ICS rom will be getting one in the 3Q. Check it out on Motorola's Software Upgrade News page.
https://forums.motorola.com/pages/00add97d6c
Miguelyl said:
Update on this. DO NOT UPDATE ON AN UNLOCKED BOOTLOADER!!! FRUITCAKE OR ANY OTHER CUSTOM ROM. YOU WILL BRICK. WAIT FOR FRUITCAKE.
Click to expand...
Click to collapse
Not sure if this helps anyone, but I had...
1) Stock 2.3.4
2) unlocked bootloader
3) rooted via fastboot (never flashed custom recovery)
4) used Voodoo OTA bootkeeper
5) followed bootkeeper instructions
6) updated to 2.3.6
7) re-rooted
8) currently i have no unlocked bootloader
I am unlocked, and RSD'd back to stock .91 and then applied the update and got a soft-brick - I did discover that I was able to flash the 2.3.6 sbf and it worked fine.... The preinstall method gave me root access back... I would not recommend trying to downgrade back to 4.5.91 after upgrading to 4.5.141 until we have more info about it....
Okay so if I used the pudding method(2.3.4/4.5.91):
1)am I unlocked, or just rooted?
2)what method should I use to install the 2.3.6 update?
OTA obviously isn't working, and I'm thinking I can just flash back to another rom, then OTA update ..any suggestions?
Sent from my MB860 using XDA App
How is the overall feedback of this OTA update? Ya I have seen the change logs but real world feedback from users is always important.
Sent from my MB860 using Tapatalk
Excause me guys but what languages are inclueded in this new firmware?
i want to root my device but then I am also planning to unroot it in the future to try updates ota. and then eventually will root again. my question is it is safe to root and unroot a device multiple times? sorry for the noob question.
Not unless you mess up the process no...
Sent From My Toro+ via Tapatalk
No, it's not safe? Or No, it is safe?
Sent from my Nexus 7 using Tapatalk 2
thank you so much
AMoosa said:
No, it's not safe? Or No, it is safe?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It is safe unless you do something wrong.
As long as you keep the stock recovery and are only rooting the stock Rom. You will still get the ota updates while rooted.
However it is possible that applying the update will remove root, but then you can just root it again anyway
Sent from my HTC One X using xda app-developers app
Why not just apply a rooted version of the update and save time and problems. Sometimes updates half further rooting capabilities
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2
Don't need stock recovery
bagofcrap24 said:
It is safe unless you do something wrong.
As long as you keep the stock recovery and are only rooting the stock Rom. You will still get the ota updates while rooted.
However it is possible that applying the update will remove root, but then you can just root it again anyway
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Not true. You don't need stock recovery. Clockworkmod can apply updates as long as signature verification is disabled. It will patch completely normally but on your next boot will overwrite clockworkmod with stock recovery. You can avoid this by telling it to prevent itself from being modified when it asks when you hit reboot.
Rooting does not prevent updates in any way shape or form. The only things that prevent OTAs are modified fastboot (modified bootloader partition), modified gsm/cdma radio drivers (radio partition, does not apply to nexus 7), modified kernels or boot files (modified boot partition), icon packs, deodexing or other system apk mods (modified system partition), or some very specific changes to the data partition. All of those only include modifying existing files, not adding new files.
Google has a list of checks in their update and what's checked depends on the update so all of those things CAN prevent updating but not all of them will break any one update. If you root it just adds a small binary file onto the filesystem so you're fine. If you use that root to replace the calculator app with the one from gingerbread or something though it will change that file and may prevent updating.
Anyone tried and confirmed working the old adb backup method that doesn't require root?
http://forum.xda-developers.com/showthread.php?t=1420351
Was hoping to use this method to backup before unlocking. I got into the usual problem of not wanting to unlock right away (in case issues etc.) then once I was comfortable with the unit too lazy to want to set up all up again from scratch....
Use helium. Backup each app individually. There are some apps that will Bork restore.
Sent from my Nexus 7 using XDA Premium HD app
bummer screw that for a joke then LOL
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
wintermute000 said:
it will be awhile before I unlock as I'm waiting for the next OTA to deal with the multitouch/gps etc. (hopefully!) I'm hoping it includes some firmware fixes too that we may not be able to flash like a normal ROM.
Click to expand...
Click to collapse
Unlocking doesn't prevent you from getting the OTAs.
If you want root to be compatible with OTAs, see this post:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
yeah I know that, I know I can reflash stock recovery and unroot etc. just too lazy to be bothered setting up all my apps losing saves etc. at this point short of mucking around with carbon. TBH if the multitouch issue is fixed or at least toned down there's not a lot of incentive to root for me aside from adblock.
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
wintermute000 said:
yeah I know that, I know I can reflash stock recovery and unroot etc.
Click to expand...
Click to collapse
My point is you don't need to unroot nor flash stock recovery (though it is safest to flash stock recovery)
The JSS15J OTA update will flash fine with root and twrp with just the small fix I referenced.
wintermute000 said:
I've got a hunch that the next OTA will involve firmware etc. so just reluctant to tinker until the stock base is 100%. Its not directly applicable as its a Nexus but in the past some other components e.g. HTC hboot, Moto (forgot the name) would get in the way of OTA if you unlocked the BL early.
Click to expand...
Click to collapse
JSS15J already included firmware updates, it updated aboot, sbl, tz, and rpm. Bootloader went from 3.05 to 3.14 and it flashed ok with root and twrp (though again, personally I suggest using stock recovery)
Also you don't need to install twrp persistently to root. I just boot into twrp one-time by using fastboot boot twrp.img to install the root files and leave stock recovery on the tablet.
With the one simple fix referenced above, you can have stock recovery, root, and be totally compatible with future OTAs, no need to revert anything. Of course after the OTA is successful, just re-run the SuperSU zip and the fix to set yourself up with root and await the next OTA.
On this nexus, you need to unlock even to do the official factory restore google published. The official images don't come with signatures.
To answer the question re adb bu, yes it works just fine.
Sent from my Nexus 7 using Tapatalk 4