All,
I have updated to 2.3.4, lost root as expected and tried to reroot 2.3.4.
I had no luck, once i ran ./Gingerbreak the script would sit and not do anything after displaying the initial text.
Has anyone successfully done this?
I thought about updating with the prerooted 2.3.4, but the devs started to add all sorts of stuff in there, and right now that is not what I am after.
Thanks!
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
- I didn't unlock the boot loader on the phone and now really don't want to go through the hassle of having the phone reset when I do... too much on it.
- Can't do a nandroid backup (to unlock) because I don't have root.
Catch 22 circle. Am keeping my eyes open, hopefully someone comes up with an alternate method. Once I get root again I will unlock the boot loader after making a backup so this doesn't happen again.
51Cards said:
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
Click to expand...
Click to collapse
Custom bootloader? Just unlock the one you have and flash a new recovery. It takes a whopping 3 minutes to flash recovery, then SU, and reboot. If you want to keep everything stock so you can OTA, the stock ROM will overwrite the recovery when you boot and you'll end up with rooted stock ROM with OEM recovery. If you want to then flash a custom rom, you can do so through ROM manager.
Want to unroot? Download the FRG33 passimg.zip and boot into bootloader.
This stuff is stupid easy on the N1.
ATnTdude said:
Custom bootloader? Just unlock the one you have and flash a new recovery.
Click to expand...
Click to collapse
Ok so feeling like a newb here.
First I meant 'custom recovery', not 'custom boot loader'... mixup in terms on my part.
But to put in a custom recovery I need to unlock the phone. Once I unlock the boot loader doesn't the phone reset to factory state? I had seen that mentioned several times and in the unlock video I was watching. After the phone was unlocked it went back to "Welcome to Android" etc on the next startup. Have far too much in the phone I don't wish to loose and I can't Nandroid it without root.
Thanks for the info.
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
I am attempting to keep my phone as stock as possible and only root to block ads and sometimes push some new app that google wont release to the n1.
I really don't want to mess with custom anything on my daily driver (used for business also). I have my g1 for that
SO....has anyone used gingerbreak successfully on 2.3.4?
Disregard. I misread the post.
MitchRapp said:
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
Click to expand...
Click to collapse
Yeah, the ROM manager option would have worked well before I did the OTA for 2.3.4 and lost root. I will keep it in mind for the future, thanks!
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Exactly what I did. Works smoothly and you're all set in minutes. As long as you had root in the first place, on 2.3.3.
Sent from my Nexus One using XDA Premium App
DownloaderZ said:
All,
I have updated to 2.3.4, lost root as expected
Click to expand...
Click to collapse
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
GnatGoSplat said:
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Click to expand...
Click to collapse
I'm looking to download all the files for this so I'm set from the start. I found FRG33 here but I haven't found the GRI40 update yet (although I haven't really looked yet either, that's not my question). I'm wondering, the site I listed has FRG83 as well as 33, does it matter which to use? 33 mentions a possible error.
What's the deal?
Thanks,
I think you should be able to use FRG83 instead. All you really need is something that can be named passimg.zip installed by the bootloader itself.
I got the GRI40 update from here:
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
GRI22 update:
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Oh yeah, I forgot about that. Flashing PASSIMG.zip wipes out everything because it's a full flash.
brettbellaire said:
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Click to expand...
Click to collapse
There is no way to downgrade Android without wiping everything, as a downgrade is only possible with leaked shipped ROMS (i.e., ROMs that re-write the entire NAND flash memory on the device...
droidexplorer said:
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I do that as well now. However I have some steps I figured out that work for me. It's more direct (only 2 flashes, plus su), but you have to pay attention. If you didn't already have a CWM backup though, it will wipe everything:
1) Flash to FRG33 using PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip (rename to PASSIMG.ZIP), takes you to 2.2
2) Root using Super-One-Click
3) Install ROM Manager and flash CWM
4) Flash b90257ed8cd3.signed-passion-GRJ22-from-FRG33-121341.b90257ed.zip, takes you directly to 2.3.4
5) DON'T LET PHONE REBOOT into Android, go to recovery then Flash su-2.3.6.1-ef-signed.zip
6) Remove/rename /system/etc/install-recovery.sh via ADB
7) If you have a recent backup, use CWM to 'advanced restore' the data portion.
8 ) Profit! (or root)
Step 5 may require explanation:
Android will reboot at least once during the flash, this is ok, as it loads right back into recovery. However after the second reboot, it will boot normally. You must INTERRUPT this boot process (hold power button, battery pull, etc). At this point CWM is still on there (don't know why, I thought flash was going to wipe it).
The reason you have to interrupt the boot process (for anyone who doesn't know) is because of the install-recovery.sh script. Stock android will automatically flash the stock recovery on bootup.
So boot into CWM, then flash su. After bootup up again, CWM will be gone, but we have root! So remove (I renamed) that file (/system/etc/install-recovery.sh), then reflash CWM using ROM Manager.
EDIT: After posting this, I had a thought: it should be possible to remove install-recovery.sh via CWM using ADB. That would remove the step of reflashing CWM a second time. I updated the step-by-step, but left the explanation as-is.
When I originally wrote these steps a few months ago, gingerbreak wasn't released. So I don't rely on it.
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
GnatGoSplat said:
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
Click to expand...
Click to collapse
In theory. It does seem to work for other devices (gTablet). I haven't had much luck with modifying the updater-script inside the zip file however. Whenever I change one, I get errors when I flash the zip. That's why I haven't tried that method.
I wanted to make my own flashable zips to tweak ROMs on my own, but never could get it to work, so I abandoned my work.
In addition though, you could just try to replace the recovery.img in the zip file with CWM. That might work too, as long as signature verification is off. I don't remember if I tried that.
EDIT: Forgot one key thing: Doing this won't prevent the OS from reflashing the stock back anyway on bootup (using install-recovery.sh). You MUST remove that file regardless, if you're on a stock ROM. If you want to remove that from the zip you can, but again requires updater-script changes. However if you want to OTA, then I'd recommend just renaming it, since some OTA's update that file. That way you can rename it back for the update.
On the GRI40 to GRJ22 update, I didn't have to do anything too complicated like modifying scripts. I simply yanked the Recovery folder out of the update and that seemed to do the trick with no error messages and CWM still intact.
So I have an AT&T galaxy s4 and I rooted and installed TWRP recovery. I want to revert my s4 completely back to stock as in remove twrp recovery and unroot. Ive been trying to look for a way to get stock recovery back on my s4 but cant seem to find the answer. Please help me out!!!!!
http://forum.xda-developers.com/showthread.php?p=40976805
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
what is nandroid
cloud628 said:
So I have an AT&T galaxy s4 and I rooted and installed TWRP recovery. I want to revert my s4 completely back to stock as in remove twrp recovery and unroot. Ive been trying to look for a way to get stock recovery back on my s4 but cant seem to find the answer. Please help me out!!!!!
Click to expand...
Click to collapse
I did the "Casual" TWRP Recovery and Root for my AT&T S4 and love it. I booted into recovery and flashed a backup image of my stock device and saved the 3.56 GB nandoid file on both the internal and external SD and put another copy of my original phone image or nandroid or backup or whatever flavor you want to call it, on my PC.
I've frozen 37 phone functions with Titanium Backup and dodged a bullet. I heard there was another over the airwaves update from AT&T a couple days ago, and I am pleased to see it never appeared on my S4. I couldn't be happier. I have yet to try any custom roms as cyanogenmod doesn't seem to be getting any love lately, plus I would not want to give up the universal remote in the on board "watch on" app.
Why do you want to undo TWRP custom recovery and lose root? Titanium Backup needs root. Did you flash a custom rom without going into recovery first and making a backup of your stock handset once you got root and TWRP?
In any case I think there is an Odin thread you need to read: http://forum.xda-developers.com/showthread.php?p=40976805
fukenbiker said:
I did the "Casual" TWRP Recovery and Root for my AT&T S4 and love it. I booted into recovery and flashed a backup image of my stock device and saved the 3.56 GB nandoid file on both the internal and external SD and put another copy of my original phone image or nandroid or backup or whatever flavor you want to call it, on my PC.
I've frozen 37 phone functions with Titanium Backup and dodged a bullet. I heard there was another over the airwaves update from AT&T a couple days ago, and I am pleased to see it never appeared on my S4. I couldn't be happier. I have yet to try any custom roms as cyanogenmod doesn't seem to be getting any love lately, plus I would not want to give up the universal remote in the on board "watch on" app.
Why do you want to undo TWRP custom recovery and lose root? Titanium Backup needs root. Did you flash a custom rom without going into recovery first and making a backup of your stock handset once you got root and TWRP?
In any case I think there is an Odin thread you need to read: http://forum.xda-developers.com/showthread.php?p=40976805
Click to expand...
Click to collapse
well.....Theres nothing wrong with TWRP recovery and root, its just that I have no need for it. I have tried a few custom roms and none offer battery life better than that of the stock TW software so I decided to just stay stock. As you said like 2 days ago at&t rolled out another OTA, however I dont think my phone installed it. It booted into TWRP and it started installing a zip. I wasnt sure if that was the OTA or not. I just dont need the TWRP and root as of now and its kind of a hastle in my current state to flash the new OTA's instead of having it automatically install via stock recovery.
Hello.
Im looking to get some help with an issue i have on my gs4 att, stock + root.
My device keeps loosing root access after a while.
I have unrooted and flashed stock 4 times, but i cant figure out the problem and cant find any information on the fourms.
What version stock?
TheAxman said:
What version stock?
Click to expand...
Click to collapse
stock 4.2.2 UCUAMDL
do do you think it ha anything to do with removing stock samsung apps like hub and att [email protected]?
gsr101 said:
Hello.
Im looking to get some help with an issue i have on my gs4 att, stock + root.
My device keeps loosing root access after a while.
I have unrooted and flashed stock 4 times, but i cant figure out the problem and cant find any information on the fourms.
Click to expand...
Click to collapse
Here I did it before and I never got a message says root access has been lost.
1. Odin it back
2. Root by using causal method
3. When phone reboot itself into recovery TWRP
4. Don't back up just reboot into welcome screen
5. It should ask you to install superuser, just install it
6. Finally, reboot into recovery and make nandroid back up.
On step four, I back up by using nandroid before superuser install. When I change rom, message always telling me I have lost root access quite often this way.
LeonKnight12 said:
Here I did it before and I never got a message says root access has been lost.
1. Odin it back
2. Root by using causal method
3. When phone reboot itself into recovery TWRP
4. Don't back up just reboot into welcome screen
5. It should ask you to install superuser, just install it
6. Finally, reboot into recovery and make nandroid back up.
On step four, I back up by using nandroid before superuser install. When I change rom, message always telling me I have lost root access quite often this way.
Click to expand...
Click to collapse
thats usually what i do, i tried 4 times. It doesnt ask me to install su, its already installed.
i might just have to update and wait for new root method.
Download a superuser/supersu zip file and flash it through your twrp/cwm recovery and reboot.when I first rooted my I337 ATT S4
It would loose just as I would enter recovery and my recovery would ask if I wanted to fix it before rebooting. After flashing the supersu zip file
I have had zero issues with root.
jball said:
Download a superuser/supersu zip file and flash it through your twrp/cwm recovery and reboot.when I first rooted my I337 ATT S4
It would loose just as I would enter recovery and my recovery would ask if I wanted to fix it before rebooting. After flashing the supersu zip file
I have had zero issues with root.
Click to expand...
Click to collapse
thanks for the share, do you happen to have link to the file or thread?
Sorry for the late reply I don't get notification for this site.I Google everything and most of the time it will bring u to xda for what u search .I don't post links cause I don't want trouble from nobody thinking I'm try n to take credit if u know what I mean.just helpful words
Hi
A while ago i flashed leaked android 4.3 from here:
http://forum.xda-developers.com/showthread.php?t=2368401
and suddenly i realized that i have lost root access. I can't get into recovery (TWRP)
What should I do? Please help!
why do you think that you wouldnt lose root after flashing stock? and you didnt lose your recovery, it got replaced by stock recovery, as always when you flash stock. you need to flash your custom recovery of choice via fastboot, then flash the su binaries via your newly reflashed custom recovery. thats all. a simple search would have found you the answer, because mamy people get stuck there after every single new android version. to prevent this from happening, do some research before flashing anything.
simms22 said:
why do you think that you wouldnt lose root after flashing stock? and you didnt lose your recovery, it got replaced by stock recovery, as always when you flash stock. you need to flash your custom recovery of choice via fastboot, then flash the su binaries via your newly reflashed custom recovery. thats all. a simple search would have found you the answer, because mamy people get stuck there after every single new android version. to prevent this from happening, do some research before flashing anything.
Click to expand...
Click to collapse
TWRP is still there because when small update comes (3.9 MB) is doesn't install. Instead it reboots into TWRP
I hope this is in the right place, and im probably the highest level of noob at this so im sorry if i dont get all the terminoligy right
A few weeks ago, i decided to try and root my phone (after seeing that i could connect my usb to it) and had attempted to install philz custom recovery (6?) and install superSu and a custom ROM.
I had failed this and got it stuck in a boot loop (i think i may have done it twice by accident xd) and then my brother had done his magic and put cyanogenmod on the s5.
I just tried to install the same superSu zip. file that i used last time (i thought it should work) but now its telling me there is no Su binary or something, it also appears not to connect to the internet.
I guess my questions are, what did i do wrong?
how can i fix it?
what should i do next time?
Cyanogenmod is pre-rooted, you simply have to enable it from the developer options. SuperSU is not required.
That being said, if you had flashed an official SuperSU Zip through recovery, it should have installed the binary as well, so maybe your Zip is not right?
Official download here:
https://download.chainfire.eu/696/SuperSU
To fix it, re-flash cyanogen or some other rom. Possibly re-flash your modem too if cellular isn't working.
Next time, leave it to your brother to mess with things lol
Sean89us said:
Cyanogenmod is pre-rooted, you simply have to enable it from the developer options. SuperSU is not required.
That being said, if you had flashed an official SuperSU Zip through recovery, it should have installed the binary as well, so maybe your Zip is not right?
Official download here:
To fix it, re-flash cyanogen or some other rom. Possibly re-flash your modem too if cellular isn't working.
Next time, leave it to your brother to mess with things lol
Click to expand...
Click to collapse
so i dont need to download that file atall, if cyanogenmod is pre rooted? i did go into the recovery and only clicked install (was i meant to clear the cache partitions?).
what is pre rooted? i went to download the root checker and it told me that my phone wasent rooted, i said to my brother so do i not need supersu, he said yea u do if u want to root it (so i just went into the SD and redownloaded the one before, but now its telling me that it wasent rooted).
and what happens if i reflash it? will it just get rid of supersu to how it was when my brother gave me it? or will it alter some other stuff aswell
stormy_ll said:
so i dont need to download that file atall, if cyanogenmod is pre rooted? i did go into the recovery and only clicked install (was i meant to clear the cache partitions?).
what is pre rooted? i went to download the root checker and it told me that my phone wasent rooted, i said to my brother so do i not need supersu, he said yea u do if u want to root it (so i just went into the SD and redownloaded the one before, but now its telling me that it wasent rooted).
and what happens if i reflash it? will it just get rid of supersu to how it was when my brother gave me it? or will it alter some other stuff aswell
Click to expand...
Click to collapse
When you re-flash it will go back to being fresh/clean
No, you don't need SuperSU. Cyanogenmod comes with root built-in. Read below.
http://getgoogles.blogspot.com/2015/04/how-to-enable-root-access-mode-on.html