[Q] root on the go - Nexus S Q&A, Help & Troubleshooting

Is there a way to quickly root your phone without using a computer? I'm tired of having to nandroid a backup and then losing my root. Please give me suggestions or what you do when your on the go. Thanks.

mmanjj said:
Is there a way to quickly root your phone without using a computer? I'm tired of having to nandroid a backup and then losing my root. Please give me suggestions or what you do when your on the go. Thanks.
Click to expand...
Click to collapse
just root your phone once, the right way. flash a custom rom then backup that rooted custom rom. i backup twice a week(because i flash often). when restoring, restore your most current backup. id take your stock backup off your phones sd and put it on your desktop for safe keeping, you dont need to use it. make a backup of your rooted rom before you flash another rom. that way if you need to restore it, youll have root still and all your current apps/data.

mmanjj said:
Is there a way to quickly root your phone without using a computer? I'm tired of having to nandroid a backup and then losing my root. Please give me suggestions or what you do when your on the go. Thanks.
Click to expand...
Click to collapse
I have restored to 3 different nandroid backups today (stock w/root, CM7 with trinity 1.4ghz kernel, and bionix with trinity 1.3ghz kernel) and restored my wife's to stock w/root then back to CM7 (had to bring it in to tmo as there was a data issue so i took it back to stock). So I really don't understand what you mean about losing root. The only way to lose root is if you A) return to a completely stock nandroid or B) are only using something like z4root to get a temp root. You would lose Clockwork Recovery Mod if you didn't follow all the directions to root via a computer but aside from that man...I have no clue what you're talking about.

kenvan19 said:
I have restored to 3 different nandroid backups today (stock w/root, CM7 with trinity 1.4ghz kernel, and bionix with trinity 1.3ghz kernel) and restored my wife's to stock w/root then back to CM7 (had to bring it in to tmo as there was a data issue so i took it back to stock). So I really don't understand what you mean about losing root. The only way to lose root is if you A) return to a completely stock nandroid or B) are only using something like z4root to get a temp root. You would lose Clockwork Recovery Mod if you didn't follow all the directions to root via a computer but aside from that man...I have no clue what you're talking about.
Click to expand...
Click to collapse
i assumed it was either a or b also..

simms22 said:
i assumed it was either a or b also..
Click to expand...
Click to collapse
-_- I see you beat me to the answer. Now I must duel you.
/glove_pull_up
/glove_slap
/glove_pull_down

for instance i just rooted my phone again now. its stock. if i nandroid it now with no customizations other than root and return to this nandroid i will maintain root correct?

mmanjj said:
for instance i just rooted my phone again now. its stock. if i nandroid it now with no customizations other than root and return to this nandroid i will maintain root correct?
Click to expand...
Click to collapse
Umm again, I don't know how you're rooting and I can only vouch for the adb push method as its what I did with mine and my wife's phones. Assuming you did it that way, assuming you installed CWM, and assuming you changed the name of the recovery installer file you will maintain root through nandroid backups and maintain CWM through reboots as well.

kenvan19 said:
-_- I see you beat me to the answer. Now I must duel you.
/glove_pull_up
/glove_slap
/glove_pull_down
Click to expand...
Click to collapse
dude, i just pulled this ban hamster out in another thread here. you dont want to mess with me
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

kenvan19 said:
Umm again, I don't know how you're rooting and I can only vouch for the adb push method as its what I did with mine and my wife's phones. Assuming you did it that way, assuming you installed CWM, and assuming you changed the name of the recovery installer file you will maintain root through nandroid backups and maintain CWM through reboots as well.
Click to expand...
Click to collapse
i used the sticky for rooting, "flashing clockwork recovery method". I use in cmd prompt fastboot flash recovery recovery.img so what i basically want to know is if im on my stock rom with root, with recovery-install.sh file renamed and nandroid it now, when i flash back to this will i maintain root?

mmanjj said:
for instance i just rooted my phone again now. its stock. if i nandroid it now with no customizations other than root and return to this nandroid i will maintain root correct?
Click to expand...
Click to collapse
yes. if you have root that is. if, for instance, you decided to flash cyanogenmod7, then after you booted up you went back to recovery and made a backup, you would restore cyanogenmod when you restored it. you can make many backups btw, then chose which one you want to restore.

OK I just want a rooted stock image so I can flash from there to my hearts content.
Sent from my Nexus S using Tapatalk

simms22 said:
yes. if you have root that is. if, for instance, you decided to flash cyanogenmod7, then after you booted up you went back to recovery and made a backup, you would restore cyanogenmod when you restored it. you can make many backups btw, then chose which one you want to restore.
Click to expand...
Click to collapse
For reference to the OP, this is what I do. When I see a new rom I want to try I do a backup through Rom manager (it allows you to name Backups rather than just have a date/timestamp). Then I do a titanium back up of all my apps. Next I flash the rom and/or kernel I want to try and then do a titanium restore of my apps, get everything set up how I like it and then immediately do another NANDroid backup through Rom manager.
Right now I have these backups on my phone:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
CM714apps (CM7 rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
Bionixapps (Bionix rom, standard bionix kernel, rooted, with apps set up)
Bionix13apps (Bionix rom, trinity 1.3GHz OC kernel, rooted, with apps set up)
Bionix14apps (Bionix rom, trinity 1.4GHz OC kernel, rooted, with apps set up)
On my wife's:
StockWapps (Stock rom, stock kernel, rooted, with apps set up)
CM7apps (CM7 rom, standard CM7 kernel, rooted, with apps set up)
BionixZuneApps (Bionix rom, standard bionix kernel, ZuneEvo theme, rooted, with apps set up)
If you see the pattern its basically ROMThemeKernelApps for easy reference when restoring. Its so simple that I told my wife this morning to put her phone back to stock and she was able to figure it out with only minimal help getting to the right screen (she is a complete techNOTphile)
Also, I have a backup on my computer of all of the backups. Unlike Simms, I only do backups when I make significant changes to apps, themes etc (by significant I include changing a shortcut on my launcherpro dock lol).

Related

[ROM][STOCK]ReRFS Format Stock ROM EC05 v1.01 w/ CWM3.1.0.1

NOTICE: If you have flashed any ROM, including CyanogenMod, that has converted the phone to MTD (yaffs2 filesystem), then this will not work. I abandoned ReRFS when MTD became the standard for CyanogenMod for the Epic. Only ODIN can be used to restore the phone to RFS from MTD.
The purpose of this ROM is to format the Epic 4G back to RFS, and give a stock EC05 system. Most current ROMs format ext4, and this will bring it back to RFS. This flashes a stock odexed EC05 system, stock EC05 kernel, and ClockworkMod 3.1.0.1 Purple Edition. This can be flashed from either cwm2 for cwm3, and can even be used as a stock ROM on phones already formatted as RFS.
Updated to cwm 3.1.0.1, and as long as your current reboot recovery boots to cwm 3.0.2.5 or 3.1.0.1, ReRFS can be flashed using ROM Manager.
Todo: I'd like to kang chris41g's autoconvert scripts for an automatic backup portion before flashing... I haven't been able to reach him lately, and I'd like his permission before using his script.
This does not touch the modem... use odin to flash the EC05 modem, or use the zip library of tools for ClockworkMod for the epic below, including modem flashes for oder stock modems, stock kernels, and stock recoveries.
IMPORTANT: Make a backup before flashing this- it will format everything on the phone, and destroy all data. It does not touch the sdcard. As with any tool here, I can't be held responsible for any trainwreck that happens to your phone.
I would highly recommend powering off the phone, and booting into cwm with vol down, camera, and power button combo. In recent testing, I've successfully been able to flash ReRFS with ROM Manager with Clean Kernel, as long as reboot recovery brings you to cwm 3.0.2.5 or greater, ROM Manager shouldn't pose any troubles. In the event of flash failure, read the next paragraph.
If for some reason the flash doesn't take, and the phone will not boot afterwards, then perform a 4 finger boot (Vol up + Vol down + camera + power), and flash the ROM again. I haven't needed to do this in my testing, but formatting RFS can be buggy at times, and a reflash of the ROM should take care of it.
If you need to turn in the phone for service or exchange, then flash the ReRFS ROM, and make sure the phone boots. Then go back to ClockworkMod with the 3 finger boot, and flash the Samsung stock recovery, to uninstall ClockworkMod. Only flash the Samsung stock recovery if you need to turn in the phone.
I extend a very special thanks to supercurio- without his voodoo lagfix source, I wouldn't have known the proper fat.format usage, and a trick to write zeros to the system partition before formatting. The exact source is here:
https://github.com/project-voodoo/lagfix/blob/stable/voodoo_initramfs_parts/scripts/rfs_formatter.sh
Thanks to: bikcmp for fossnet server space, and Shabbypenguin for graciously hosting files as mirrors.
Link:
ReRFS Format Stock ROM EC05 v1.01
Tools:
epic4g.stock.recovery.ec05.zip
The Samsung stock recovery, for uninstalling ClockworkMod, useful for turning in the phone to Sprint.
Do not flash the stock recovery unless your phone boots into system, and you need to turn the phone in.
modem.DI18toEC05.zip
update modem from DI18 to EC05, particularly important, coming from DI18
modem.EB13toEC05.zip
modem from EB13 to EC05
modem.DI07toDI18.zip
modem from DI07 to DI18
kernel.stock.EC05.epic4g.zip
Just the stock EC05 kernel by itself, if it's ever needed
DRockstar.Clean.Kernel.EC05.v1.05.zip
Flash this kernel to have root and busybox, this kernel has reboot recovery to cwm 3.1.0.1, and is ROM Manager compatible.
Support:
Either here in the forum, or live at irc.fossnet.info channel #epic
Weblink: http://webchat.fossnet.info/?channels=epic
I support this post! This is incredibly useful if you don't have USB access and need to stock your device before sending it in.
good work man, this is very nice for people looking to replace odin
Edit: omg it sexs me up
To you, sir, I give thanks. You have done a great service to this community.
Awesome work bro. I'm having g some trouble with my phone connecting to any usb. Even to charge. I think its going bad and this I'd awesome if it completely goes out I can still get to stock. Awesome work
Sent From My Evo Killer!!!
musclehead84 said:
Awesome work bro. I'm having g some trouble with my phone connecting to any usb. Even to charge. I think its going bad and this I'd awesome if it completely goes out I can still get to stock. Awesome work
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
I posted a thread about this in General, give a search and try my 'fix'. It might work for you.
k0nane said:
I support this post! This is incredibly useful if you don't have USB access and need to stock your device before sending it in.
Click to expand...
Click to collapse
shabbypenguin said:
good work man, this is very nice for people looking to replace odin
Click to expand...
Click to collapse
You are both so correct on those comments.
I know there will be many happy users once they find this. Going to put this on my card for safe keeping just incase, you know.. The USB takes a dump which at some point it seems to happen to all frequent flashers...
Wow good stuff Rockstar. Great alternative to Odin if you want to restore to stock EC05.
Put the Samsung stock recovery in the tools section of the post...
Flash this with ClockworkMod, to uninstall ClockworkMod, in case the phone needs to be turned in with factory recovery.
If you need to turn in the phone, then flash the ReRFS ROM, and make sure the phone boots. Then go back to ClockworkMod with the 3 finger boot, and flash the Samsung stock recovery, to uninstall ClockworkMod.
Thank u thank u thank u. This made my day as i just started today updating my wife's epic from dk28. I used the ec05 and the kernel and her phone finally is nice to use. No matter how clean of an install it always had some issue. I loathed it, but now she and I am very happy w a 100% functioning phone w 0 problems.
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
sonjohn1 said:
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
You should be able to perform a backup with ClockworkMod before performing this flash. Reboot into android, and check to see that the backup is there in /sdcard/clockworkmod/backup.
After the ReRFS ROM is performed, reboot, and then shut down. 3 finger boot into ClockworkMod 2.5.1.0. Choose mounts and storage > advanced > {select backup} > restore data.
Alternatively, you can use MyBackup Root, available free from the market, and use that. My rooted kernel is also posted in this thread, that you can flash for that purpose.
I will also post the stock kernel by itself for you, and that will be part of my ClockworkMod tools release, with all of the flashes I've made and collected.
Hope this helps!
sonjohn1 said:
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
For a stock kernel check out this thread post#8.
http://forum.xda-developers.com/showthread.php?t=1006894&highlight=dangdang
DRockstar, you da man! Many thanks.
Sent from my SPH-D700 using XDA Premium App
sonjohn1 said:
How about a stock ec05 kernal for folks that have a custom kernel, but not a custom rom. That way I don't have to lose all my settings with a complete wipe and I will still be able to take my phone into Sprint.
Thanks for a great job.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Just so you know, most custom kernels currently published (if not all) still make changes to the system files that would prevent OTA updates, and leave tell tale signs of rooting in the system.
In the event that you really needed to turn in the phone, I would do the following:
* Perform a backup with both ClockworkMod and MyBackup Root (just in case)
* Flash ReRFS ROM
* Boot into cwm > backup and restore > advanced restore > {choose backup} > restore data (optional, may work well, may cause force closes)
* From cwm, flash the Samsung stock recovery, in Tools section of this post, to uninstall cwm, and eliminate all signs of tampering
Just wanted to make that clear... Even the cleanest of custom kernels still leave traces when flashing the stock kernel. Even though my Clean Kernel should allow OTA updates to occur once the stock kernel is flashed again, if I really needed to turn in the phone for some reason, I would do the steps I just laid out.
Hope that clarifies some things.
This helps tremendously. Thanks again.
Sent from my SPH-D700 using XDA Premium App
Xda app thanks button!
Drockstar, you should put the md5 of the file in the OP. Well cuz you know downlaods get messed up at times and seeing how this is a "fix it kind of tool/rom" so to say
Sent from my ComBadge..
This is exactly what I was hoping to find. I had no problems with flashing this and so far it works perfectly. I am really stoked because I recently broke my usb cable and haven't picked up another yet. Thank You!!
Unreal...we have been around wifi mostly but for 6 hours on 3g. This makes me very happy. Battery is at 53% and this is an ec05 epic 4g
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Links dont work for any of the downloads... says there has been too much traffic, or something along those lines.

ClockRecovery version5

I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks
I don't know if I'm replying too late, but here's what I did.
Hold volume button down while turning the phone on. You'll get the white bootloader screen w/ skating androids and then just scroll til you see the "Recovery" option. Highlight and push the power button.
Reinstall your nandroid backup.
Once you can, double check RomManager to see if it's actually upgraded.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The version numbers should match this image. Clockworkmod RECOVERY 5.0.1.0.
reynaldorivera said:
I updated to Clockwork Recovery. Now my phone is stuck on HTC boot screen. I cant even recover my back up's. it keeps getting stuck on boot screen. Nothing is working. What can I do? Is it bricked? Can someone hook me up? thanks
Click to expand...
Click to collapse
Did you try holding volume down and the power button when powering on the phone? You can get to recovery from the bootloader. If that doesn't work, I think your only opton would be reflashing recovery via fastboot.
You may have an older version of rom manager. To get clockwork 5 to work when I flashed it I had to update my rom manager. This happened today I tried to flash miui to review it and it told me I needed new rom manager. But since your stuck on boot screen your other options would be flash a recovery via fastboot OR run a flash with Cmd prompt (assuming you are on windows)
Sent from my Nexus S 4G using Tapatalk
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk
bamaredwingsfan said:
I just installed CM7RC1.7 and now my phone won't boot nothing but the CM7 rom. I keep getting hung up in the white boot screen. I was trying to use a nandroid of sense to get the GPS working with CM7. So have i punched a one way ticket to CM7 or what? How do get my sense nandroid to load? Im on the most current CWR, so im baffled now. I even tried to just install a sense rom instead of going back to an nandroid. Same result, stuck at boot screen, unless i restore that nandroid of CM7 i just installed.
Click to expand...
Click to collapse
I can't get any sense rom to work but all AOSP ones do so I think we are in the same boat... I get bootloops on all sense roms...
bamaredwingsfan said:
Im on the most current CWR, so im baffled now.
Click to expand...
Click to collapse
Some people were having trouble getting the CWR to stick yesterday. Are you certain it updated properly to the new blue 5.0.1.0? If you think the CWR is the problem, you could try to downgrade it before flashing the Sense Rom. Try this link
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Yea I just tried it again... :-( I miss sense...
I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner
dms76 said:
I had to install a fresh from download ROM manager then download cwm 4.0 and recovery worked fine. Somethin is weigh with 5.xx
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
5.xx is working fine on my phone. Plus I like the blue color he used this time. It might be buggy for other phones but on mine it works like a charm
Sent from my Nexus S 4G using Tapatalk
Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner
dms76 said:
Have you tried a restore yet?
Sent from my thunderbolt using Forum Runner
Click to expand...
Click to collapse
I've done a backup and restore. Working fine for me. I do not use ROM manager. Only do backups from cwm. Flashed 5.0.1.0 from hboot. Downloaded the zip from Absolute_Zero's thread in the development section.
yareally said:
perhaps the sense roms are not compatiable yet with the latest recovery. that would be my guess.
Click to expand...
Click to collapse
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.
Hey all . I had the same problem the new version of clockwork will not backup or restore . I had to flash a fresh ROM also to get booted up then downgrade clockwork again. I also noticed that the backups I tried to restore the img files were turned to tars . What up with that ?
Sent from my ADR6400L using XDA App
Jorge330823 said:
If clockwork is your recovery than you can try to install a backup straight from your recovery in bootloader instead of running your phone. Can you get into your recovery
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Cyanogen doesn't support recovery before version 4, but I never searched for the reason. I assume the install script for it.
hallstevenson said:
Shouldn't be the case. At the point that recovery is running, the ROM itself has NO relevance. The ROM and recovery do not run at the same time. It's like the BIOS on a PC - while it's running, Windows, Linux, etc is NOT running.
Click to expand...
Click to collapse
It is the case I can confirm. Also some roms have been known in the past to not work with certain versions of recovery so this is nothing new. I went back to 4.x and sense roms work again.
Ok, managed to get back to a sense rom. I looked up the app version of CWR and it was not the most current it was 03 instead of 05. So i updated the app an had the most current recovery(blue one) and tried to restore my nandroid of sense to get out of CM7 Same result, white brick until i wipe everything an restore the CM7 nandroid. Being baffled, i tried some different combinations, but it was getting late, so i had to stay on CM7. Go to work today, and CM7 is just not cutting it, BT was all over the place. So this time i deleted my Ti backup of CWR, an installed new an fresh. Reinstalled the recovery just to make sure everything was the most current. Thank god before i went to bed last night, i copied over a zip of gingeritis3D as a just incase if all else fails. Well, all else failed, so i had to try a fresh install of a new rom instead of going to a nandroid backup. That failed too. One last try, an here is what worked. I wiped everything but dalvic an did the fresh install of gingeritis3D, an bingo, the phone booted! I was never so happy to see sense as i was at that moment. I then preceeded to delete any an everything off my phone that pertained to CM7. I never had a single problem until i installed that CM7 1.7 rom on my phone. Im not saying that is what caused my problem, but something did. Right now im mainly leaning toward the wiping of the dalvic that was causing most of the trouble. Guess we will see in a few days when i try a different sense rom.
i hope a stable build comes soon.

Losing ROOT on ICS ***FIXED***

Ok. Think I got the problem fixed. see my last post # 37........
I keep losing root, no matter what kernel or rom for ICS i install. this only seems to happen when i going system with root explorer to make changes to media sections. i tried to reflash su, busybox, wipe data-cache. The only way to get root back is to revert back 2.3.5 and then install ics rom- but i soon as i go into system and change it from r-o ro r-w it locks up and locks me out. Superuser is even locked out . Is there a fix for this or am i just out of luck. you can see what i get from superuser update.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are doing the design gears exe you are supposed to lose root.
Sent from my SAMSUNG-SGH-I727 using xda premium
Sheolrock said:
If you are doing the design gears exe you are supposed to lose root.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
not running that.
running sliver03wrx rom- even installed mohans kernel to try and fix it.
installing it via cwm flash
follow these steps
flash darkside through cwm
flash designgears
reflash cwm
flash darkside
flash ANY ics rom, ics perfections 4.2 by mhx is good
problem solved, permanent root
icenight89 said:
follow these steps
flash darkside through cwm
flash designgears
reflash cwm
flash darkside
flash ANY ics rom, ics perfections 4.2 by mhx is good
problem solved, permanent root
Click to expand...
Click to collapse
ok i tried this and it did not work. still lost root..
anymore ideas.
galaxyuser88 said:
ok i tried this and it did not work. still lost root..
anymore ideas.
Click to expand...
Click to collapse
Flash superuser zip in cwm.Make sure busybox is installed if its not search for busynox installer in android market, also update su binary under su app in app drawer.
Sent from my SAMSUNG-SGH-I727 using xda premium
cdshepherd said:
Flash superuser zip in cwm.Make sure busybox is installed if its not search for busynox installer in android market, also update su binary under su app in app drawer.
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
did that all up to date and still lose root. It seems that when i loose root i can reflash and root back, but as soon as i go into systems/media and then change it from ro to rw it looses root and i have to reflash to get it back.
galaxyuser88 said:
ok i tried this and it did not work. still lost root..
anymore ideas.
Click to expand...
Click to collapse
Wait, what? My instructions completely wipe the phone then put on cwm again and an ics rom. If u followed them precisely im sorry but there's no way you're losing root. Please elaborate and what u did
Ok. I followed your steps to the letter. and i even tried a few different roms for the last step. And nothing seems to help me from losing root. As long as i stay out of the system folder (and i havent tried another sys folder) then i dont lose root. I really do not know what else to do or say..
icenight89 said:
follow these steps
flash darkside through cwm
flash designgears
reflash cwm
flash darkside
flash ANY ics rom, ics perfections 4.2 by mhx is good
problem solved, permanent root
Click to expand...
Click to collapse
icenight89 said:
Wait, what? My instructions completely wipe the phone then put on cwm again and an ics rom. If u followed them precisely im sorry but there's no way you're losing root. Please elaborate and what u did
Click to expand...
Click to collapse
Have you tried flashing romancer's kernel, wait 30 seconds, flash it again, then fix permissions and reboot. (Trying a different mod won't really help)
I tried to fix mine several ways, but just reflashing the kernel a few times and fixing permissions was the best fix
Sent from my SAMSUNG-SGH-I727 using XDA
burgeswe said:
Have you tried flashing romancer's kernel, wait 30 seconds, flash it again, then fix permissions and reboot. (Trying a different mod won't really help)
I tried to fix mine several ways, but just reflashing the kernel a few times and fixing permissions was the best fix
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Yeah i have tried rom racers kernel.. tried to fix permissions, (that really locked me out, where flashing su wouldnt take, even flashing su 10 times to try and get it to take) only way to get root back was to wipe and reflash the complete rom..
And before anyone asks. my phone is ATT samsung sgh-i727. so iam not trying to flash anything that doesnt belong to another carrier or phone.. Yes i have rooted and flashed serveral different devices on different carriers with out any issue, except for bricking a galaxy tab 7, but got that back up by doing the unbrickable mod to it. So iam not a newbie by any means..
Flash this in CWM;
http://forum.xda-developers.com/showthread.php?t=1565126
Flash a few times it should let you through.
Fix permissions before reboot.
Then install BusyBox.
let us know.
Curious, do you have the same problem going thru an adb shell to modify the system?
fongz27 said:
Flash this in CWM;
http://forum.xda-developers.com/showthread.php?t=1565126
Flash a few times it should let you through.
Fix permissions before reboot.
Then install BusyBox.
let us know.
Click to expand...
Click to collapse
ok did this a few times, root and busybox installed, but it still does the same thing, as soon i go into system and mount rw, it lets me mount it and then it locks me out again, and then i lose it it again. It seems that root holds as long i stay out of the system files. Seems like the sys/system files have a security measure or something in there to prevent unwanted access.
Even i when i go back to the earlier version 2.3.5 and try to flash ics with no wipe- it gets stuck at a boot loop, samsung- samsung- android, samsung-samsung-blank screen, samsung-samsung-android, etc. I have wait 10 mins for this bootloop to go thru, and nothing. I would have to pull battery, go into recovery and do a wipe, and then reboot into ICS.
This is very confusing and fustrating trying to get this to work.
I am able to regain root when i reflash su and busybox but it seems no matter what rom/kernel-version of cwm- version of superuser, version of busybox, i try i get the same outcome.
If you are going back to 2.3.5, it is recommended you do a FULL WIPE; you are changing kernels and system files and everything else. A clean wipe will give u the cleanest install. You are getting bootloops bcuz of non-clean wipes.
Do an ODIN install to 2.3.x with stock recovery. Then flash the original ICS leak in dev section using ODIN. Then use darkside wipe, then flash your choice of ICS rom; most ICS roms should come with root now. Just need to add busybox.
Seems like you aren't wiping correctly or something.
fongz27 said:
If you are going back to 2.3.5, it is recommended you do a FULL WIPE; you are changing kernels and system files and everything else. A clean wipe will give u the cleanest install. You are getting bootloops bcuz of non-clean wipes.
Do an ODIN install to 2.3.x with stock recovery. Then flash the original ICS leak in dev section using ODIN. Then use darkside wipe, then flash your choice of ICS rom; most ICS roms should come with root now. Just need to add busybox.
Seems like you aren't wiping correctly or something.
Click to expand...
Click to collapse
I did a super wipe using darkside wipe. I wiped everything even both int-ext sd cards. Tried this method as stated in one of the earlier posts.
cschmitt said:
Curious, do you have the same problem going thru an adb shell to modify the system?
Click to expand...
Click to collapse
yup just tried it. let me remount rw system once. closed went back and tried again and mount: read-only file system
lost root again
galaxyuser88 said:
yup just tried it. let me remount rw system once. closed went back and tried again and mount: read-only file system lost root again
Click to expand...
Click to collapse
Are you running one of the insecure kernels? That will put you into root at adb shell without issuing su. From there you an remount system as rw and modify system, give it a shot.
Running stocked, rooted UCALC4 ROM with the mohan_kr insecure kernel and have not problems writing in /system/media with either an adb shell or ES File Explorer.
Didn't do anything special as far as wipe scripts, etc. Just flashed the one click, then CWM, insecure kernel, superuser zip, installed busybox.
Maybe try thru adb shell or a different file explorer app and see if you get different results.
I have a similar problem but only with some roms. I can't use the collective rom even after formatting data as I get locked out from accessing system files
There does seem to be some problem with different versions of CWM not working as well as others with kernel flashing
Personally, I've had far more luck with
http://forum.xda-developers.com/showthread.php?t=1472954
Than any others
Flash that, then flash the unsecure kernel, then flash su. (I don't think another wipe is needed, might be wrong)
Sent from my SAMSUNG-SGH-I727 using XDA

[HOWTO] GB to ICS OTA for Rooted Stock - Keep your data (Revolutionary hboot only)

Provided you meet the prerequisites, this is an easy way to safely update from 2.11.695.19 Gingerbread to 7.02.605.06 to 7.02.605.10 Ice Cream Sandwich via the new OTA and keep root. I have also modified the stock kernel to allow adb remount so you can push/pull files directly from the command line without needing to drop into adb shell. If you do not have the correct Revolutionary hboot or have modified your Gingerbread system files then skip this guide and flash a rooted stock build from the development forum.
ONLY for users with S-OFF revolutionary hboot and running rooted stock. DO NOT USE THIS GUIDE IF YOU ARE HTCDEV UNLOCKED OR HAVE CHANGED OR DELETED ANY OF THE STOCK SYSTEM FILES. FLASH THE RADIO AND FULL ROM INSTEAD.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
REQUIRED Prerequisites:
Revolutionary hboot with S-OFF
Rooted Stock ROM with NONE of the system files missing or changed
Get the files:
- Save the stock recovery image to your fastboot directory: Stock recovery (use the same as your ROM build, 2.11.695.19) or attached below
- Save the custom recovery image of your choice to your fastboot directory: TWRP or CWM
- Optional Superuser or SuperSU recovery flashable .zip package if OTA rootkeeper did not work
- Optional insecure boot.img attached below
Steps:
1) Set your Superuser app for OTA survival mode
2) Reboot into bootloader
If your bootloader does not have "Revolutionary" across the top, STOP immediately. If you take the OTA, you will end up with a locked bootloader.
3) Flash stock recovery
Code:
fastboot flash recovery name_of_stock_recovery.img
4) Reboot, check for the first firmware update and download.
5) Apply update. It should reboot a few times and then reboot back into system when done. Check for the second OTA and download.
6) Apply update. It should reboot a few times and then reboot back into system when done.
7) Reboot into bootloader
8) Flash TWRP or CWM recovery
Code:
fastboot flash recovery name_of_custom_recovery.img
9) Copy the superuser install .zip to the root of your sdcard
10) Reboot into recovery and flash the superuser update package
Optional for insecure boot ie: adb remount works:
1) Download mecha_insecure_boot.img to your fastboot directory
2) Reboot into bootloader
3) Flash:
Code:
fastboot flash boot mecha_insecure_boot.img
Secure boot attached if you want to go back.
Code:
fastboot flash boot mecha_secure_boot.img
Once you are done, your Thunderbolt will have the current ICS rom with data intact, the new radio, working superuser, custom recovery and insecure boot for "adb remount" if wanted.
This looks good, have people had success with it yet? I don't want to lose my data by trying to unroot, but I am already sitting with rooted stock with the 2.11.605.19 recovery installed.
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Looks simple enough. I am going to try this on my wifes tbolt tonight.
Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
Tiezane said:
This looks good, have people had success with it yet? I don't want to lose my data by trying to unroot, but I am already sitting with rooted stock with the 2.11.605.19 recovery installed.
Click to expand...
Click to collapse
So far just me that can confirm this works. I did not wipe at first but ended up doing a factory reset after everything was said and done anyway. There are always bits and pieces of old data that are not quite right going between major versions like this.
KidJoe said:
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Click to expand...
Click to collapse
I can only confirm this worked for me on the Revolutionary hboot. Not going to speculate on others. If the version number in the OTA is higher, it probably will replace what you currently have.
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
A CWM flashable zip would have been nice to have last night! This goat rope is pretty much the same process I used on the G2 and MyTouch. No patience so went with what I know and sharing how I did it.
kpetrie77 said:
A CWM flashable zip would have been nice to have last night! This goat rope is pretty much the same process I used on the G2 and MyTouch. No patience so went with what I know and sharing how I did it.
Click to expand...
Click to collapse
Haha yeah I agree, however I spent last night getting it made up.
Didn't finish till this am.
But truly thank you for sharing this alternate method of keeping root and updating.
I'm sure it's much appreciated by many.
Upload is about halfway...
santod040 said:
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Click to expand...
Click to collapse
Call me timid.....
Thanks in advance santid040.
santod040 said:
Instructions in the OP should work just fine. Thank you kpetrie77 for providing this guide.
However for anyone timid to try this, you may wanna know that I have a stock rooted, deodexed version about to upload.
Click to expand...
Click to collapse
At the risk of sounding like a complete n00b (which I feel like anyway)... will the version you are uploading be run as an update, and therefore maintain data on the phone, or is it going to wipe what I have there now?
Tiezane said:
At the risk of sounding like a complete n00b (which I feel like anyway)... will the version you are uploading be run as an update, and therefore maintain data on the phone, or is it going to wipe what I have there now?
Click to expand...
Click to collapse
It's a full rom install.
But I did not set it up to wipe data.
That doesn't mean it will play well if you don't format first, but you can try.
It's posted HERE
KidJoe said:
I've seen posts of Hboot 6.04.1002
When I go into hboot, I see
****UNLOCKED***** (in pink back ground)
MECHA XD SHIP S-OFF
HBOOT-1.04.0000
I thought I used the Revolutionary tool a while back to get S-OFF. I know my Hboot hasn't changed as I flashed RUU's or OTA's in the past.
Does it matter than I have what appears to be a lower/older HBOOT?
Click to expand...
Click to collapse
Apparently I had an OLD "permanent hboot with S-OFF that was made to not be overwritten.
I chickened out on trying to update. Instead, I reverted from the OLD "permanent" hboot to the old eng 1.40.2000 s-off hboot which could be over written. Then flashed with the 2.11.605.5 RUU to get back to S-ON, and Used Revolutionary to get S-OFF & Root.
So I now have the Revolutionary S-OFF hboot 6.04.1002 and will be upgrading from here.
santod040 said:
It's a full rom install.
But I did not set it up to wipe data.
That doesn't mean it will play well if you don't format first, but you can try.
It's posted HERE
Click to expand...
Click to collapse
I read this post while installing and wiped data/factory reset after installing (without booting first). Will this have the same effect as doing so before installing? Or should I wipe and install again?
Dropbox temporarily suspended... Oops.
lukesed said:
I read this post while installing and wiped data/factory reset after installing (without booting first). Will this have the same effect as doing so before installing? Or should I wipe and install again?
Click to expand...
Click to collapse
As an answer to my own question... I wasn't able to log in to my google account. I did a full wipe and installed again, and now it does work.
I have come to the conclusion that rooting is for people much smarter and with much more time than me. I'm hopelessly confused. I will never root my phone again becasue I simply don't enjoy spending my whole damn night figuring this stuff out... but since my current phone IS rooted and I want the ICS update I have to deal with this migrane.
I appreciate this OP ... but the first thing it says to do is to get the mecha android 3e recovery rom or whatever it is... and when I click that link it takes me to another forum with files all over the place, none of which are called that. What exactly am I supposed to download?
Thanks!
Re: [HOWTO] Apply ICS OTA to Rooted Stock (Revolutionary hboot only)
Good point, updated the OP. Use the stock recovery from Scotty's thread (linked) that matches the ROM version your are on.
Settings > About phone > Software
If on 2.11.605.09 then use the matching 2.11.605.09 recovery. If running 2.11.605.19 rom use 2.11.605.19 recovery.
jdport said:
I have come to the conclusion that rooting is for people much smarter and with much more time than me. I'm hopelessly confused. I will never root my phone again becasue I simply don't enjoy spending my whole damn night figuring this stuff out... but since my current phone IS rooted and I want the ICS update I have to deal with this migrane.
I appreciate this OP ... but the first thing it says to do is to get the mecha android 3e recovery rom or whatever it is... and when I click that link it takes me to another forum with files all over the place, none of which are called that. What exactly am I supposed to download?
Thanks!
Click to expand...
Click to collapse
If you are rooted, why not flash the stock rooted ICS rom?
santod040 said:
If you are rooted, why not flash the stock rooted ICS rom?
Click to expand...
Click to collapse
Because I have no idea how. I'm a complete newbie to this. I got through the rooting process because the nice scripts that were written were easy for even me to follow.... the only reason I rooted at all was so that I could get a proper backup with titanium. I wish now I had not rooted because I am absolutely clueless on how this stuff works. Of course if I unroot, it wipes my phone and I can't restore... without rooting again. lol. I just want to get the update installed without screwing up my phone.... whatever it is I have to do to do that. Unfortunately I really can't seem to find a resource that explains all of this. I've been reading all night and at this point my head is starting to hurt and i'm not much closer to the solution than when I started.
jdport said:
Because I have no idea how. I'm a complete newbie to this. I got through the rooting process because the nice scripts that were written were easy for even me to follow.... the only reason I rooted at all was so that I could get a proper backup with titanium. I wish now I had not rooted because I am absolutely clueless on how this stuff works. Of course if I unroot, it wipes my phone and I can't restore... without rooting again. lol. I just want to get the update installed without screwing up my phone.... whatever it is I have to do to do that. Unfortunately I really can't seem to find a resource that explains all of this. I've been reading all night and at this point my head is starting to hurt and i'm not much closer to the solution than when I started.
Click to expand...
Click to collapse
If you are already rooted, go to my thread, click the link.
Sign into the InfectedROM forums, and grab the stock rom, full or debloated, your choice.
Flash it in Recovery like any other custom rom and reboot.
DONE! Stock ICS rooted... :good:

Here is a list of all .img files in the newest update. Which ones should I NOT flash?

OK so this is going to be a unique question for some reason. I can't find what a lot of these .img files do, and no sites really break it down.
Basically I am rooted/unlocked bootloader on my Google Pixel (from the Google store) and I want to flash everything possible except .imgs that will mess with my bootloader or ones that will wipe my phone.
I understand that flashing all of these are not necessary, as no guides even mention modem.img, but I want to make sure I have the most up to date everything, plus I want to learn what all these imgs are for.
Anyway, here is the complete list:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What is pmic.img? hosd? apdp? rpm?
A lot of guides and sites make no mention on a lot of these, and a lot of them seem important, especially in regards to getting the best signal on my phone, battery, wifi reception, and things like that.
So for argument's sake, say I want to manually flash as many of those img files as possible, but without loosing root, without locking my bootloader, and without losing my data, which ones am I free to flash? Everything but boot.img and bootlocker.img? I have no clue!
Thank you very much in advance for any info!
This won't exactly answer your question but first, nothing but you specifically locking your bootloader will lock it. Flashing an updated bootloader doesn't lock it.
I'm running the completely stock ROM but rooted and with TWRP. When the July update came out, I extracted the full update zip, modified the flash-all.bat to remove the "-w" wipe command from the one fastboot command that includes it so I didn't lose any app data. Then flashed the entire stock ROM and made a TWRP backup of the boot.img.
Then redid the fastboot boot TWRP.img, flashed the full TWRP RC2 zip, rebooted recovery, re-flashed SuperSU v2.82 and everything is golden. Note that I downgrade TWRP to RC1 for back up and restore, and use RC2 for all flashing.
I also did a full Titanium Backup to Google drive and also a full TWRP backup before any of this and copied to a flash drive as things happen.
The TWRP backup of the current correct unmodified boot.img has saved me a couple of times when I was away from the computer and did something to cause the phone to only boot to recovery. After restoring the backup just flash SuperSU again.
roirraW "edor" ehT said:
This won't exactly answer your question but first, nothing but you specifically locking your bootloader will lock it. Flashing an updated bootloader doesn't lock it.
I'm running the completely stock ROM but rooted and with TWRP. When the July update came out, I extracted the full update zip, modified the flash-all.bat to remove the "-w" wipe command from the one fastboot command that includes it so I didn't lose any app data. Then flashed the entire stock ROM and made a TWRP backup of the boot.img.
Then redid the fastboot boot TWRP.img, flashed the full TWRP RC2 zip, rebooted recovery, re-flashed SuperSU v2.82 and everything is golden. Note that I downgrade TWRP to RC1 for back up and restore, and use RC2 for all flashing.
I also did a full Titanium Backup to Google drive and also a full TWRP backup before any of this and copied to a flash drive as things happen.
The TWRP backup of the current correct unmodified boot.img has saved me a couple of times when I was away from the computer and did something to cause the phone to only boot to recovery. After restoring the backup just flash SuperSU again.
Click to expand...
Click to collapse
Thanks! I don't want to flash just the update though; I want to flash the entire release as I am going to be using the t-mobile version from now on. I think the only difference is it fixed the t-mobile glitch where wifi calls don't ring.
I do appreciate all the other advice though!
Anyone with any ideas to me original post, please keep them coming because I am desperate to learn!
daddylonglegs said:
Thanks! I don't want to flash just the update though; I want to flash the entire release as I am going to be using the t-mobile version from now on. I think the only difference is it fixed the t-mobile glitch where wifi calls don't ring.
I do appreciate all the other advice though!
Anyone with any ideas to me original post, please keep them coming because I am desperate to learn!
Click to expand...
Click to collapse
I just want to make sure I was clear. I flash the entire "release", if by release you mean not the OTA but the full large firmware.
Not sure why you want to do it this way, maybe I am missing something. Just download the full factory image for t mobile and use the flash all bat file. If you want to save your data and apps edit it and remove the -w from it.
That flashes everything and does it correctly.
TonikJDK said:
Not sure why you want to do it this way, maybe I am missing something. Just download the full factory image for t mobile and use the flash all bat file. If you want to save your data and apps edit it and remove the -w from it.
That flashes everything and does it correctly.
Click to expand...
Click to collapse
Well I looked inside the text files and it doesn't look like the command flashes literally everything. But maybe I'm wrong?
Also I don't want to lose root or lock my bootloader.
daddylonglegs said:
Well I looked inside the text files and it doesn't look like the command flashes literally everything. But maybe I'm wrong?
Also I don't want to lose root or lock my bootloader.
Click to expand...
Click to collapse
It does everything. You wont relock it unless you yourself issue the fastboot command to lock it. Yea, you will loose root which takes two minutes to do.
If you just want to update use FlashFire from Chainfire and use it to install the ota file feom Google. Me, I just flashall after removing the -w from the flashall bat file and the reroot.

Categories

Resources