Database Users

root 4.2.2. without flashing customer recovery

Good morning guys,
I see a lot of threads here about rooting 4.2.2, but in all of them it is recommended to root the phone by installing zip archive from a custom recovery.
I don't want to change stock recovery - is there any way to root it by flashing img from adb? I did it in this way on 4.2.1, by installing CF-Auto-Root-mako-occam-nexus4.img file from adb.
Can anyone advice how to get root without flashing custom recovery?

I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.

Look at this How to thread in the general section, I copied and pasted relevant information. I kept a custom recovery and didn't try this method, but it says it will not flash a custom recovery.
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
2) Rename the file to customrecovery.img, and make sure it is in the same directory as your fastboot.exe file;
3) Download (to /sdcard on your device) the latest version of either ChainsDD's Superuser (not currently working), or Chainfire's SuperSU;
4) Restart your device in fastboot mode and plug into computer;
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
6) Wait for it to boot;
7) Navigate the menus the recovery menu on your device and select an option like "update zip from sdcard". Find the zip that you downloaded, and apply it.
8) Reboot. Done.

You can flash custom recovery via fastboot, use it to install su.zip and when you will choose restart after that, you will have question about you want custom recovery permanently or not, if you choose no then after restart you will have stock recovery

scottspa74 said:
I have to ask,....why would you NOT want a custom recovery? What is the point in using a crippled stick recovery?
From my Evo LTE, yup.
Click to expand...
Click to collapse
I want to make installing of future OTA as simple as possible. So I will get root and freeze all the system apps i don't want to be run, but when OTA comes I will be able to install it and will not receive any error messages which i had during this OTA.
It seems like this is a good solution:
5) Open a command prompt in the directory mentioned above and type: fastboot boot customrecovery.img
Click to expand...
Click to collapse
Do i understand correctly that this boots customer recovery on my phone from PC hard drive, but doesn't flash it to the phone? So, I'm able to install root.zip from it, but when i reboot the phone I don't have a custom recovery.

You can do as i mentioned in my post before or you can use as well command mentioned by ketjr81: fastboot boot nameofrecovery.img in both cases you will have had stock recovery after restart

Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.

fatum2002 said:
Thank you guys, you have solved my issue. Now i have to find a ZIP with root to flash.
Click to expand...
Click to collapse
you find it in thread mentioned by ketjr81

[Q] Galaxy S4 GE no root after motochopper

Ok, I'm total noob but not complete idiot. Just want to get that out of the way
I have have the Galaxy S4 Google Edition running Android 4.3.
I unlocked the bootloader before the Android 4.3 update, but have never had root access. I've tried motochopper program, but keep getting failure errors and continued no root.
What I'd like to do is restore my device to stock and run it over again. I'm sure I did something wrong at somepoint.
Can someone please help me?
Thanks

nhlfan14 said:
Ok, I'm total noob but not complete idiot. Just want to get that out of the way
I have have the Galaxy S4 Google Edition running Android 4.3.
I unlocked the bootloader before the Android 4.3 update, but have never had root access. I've tried motochopper program, but keep getting failure errors and continued no root.
What I'd like to do is restore my device to stock and run it over again. I'm sure I did something wrong at somepoint.
Can someone please help me?
Thanks
Click to expand...
Click to collapse
1. Go here and download the CWM / TWRP / MobileODIN installable ZIP
http://forum.xda-developers.com/showthread.php?t=1538053
Place the installable zip on your INTERNAL SD Card.
2. Get CWM:
http://www.clockworkmod.com/rommanager
Go here and grab CWM 6.0.3.6 for the INTERNATIONAL I9505 - yes, it works on the I9505G
Put your phone in fastboot mode by turning off the phone completely. Hold down Vol-Up Vol-Down and power simultaneously.
Since you already seem to have adb, you probably have the fastboot executable.
From your computer's command line type "fastboot boot recovery-clockwork-6.0.3.6-jfltexx.img"
This will boot recovery - temporarily - it will not overwrite the recovery on your phone.
Choose install zip from sdcard. Navigate to the installable zip that you placed on you sdcard in a prior step.
Reboot. When CWM asks to fix "this may overwrite your recovery" SAY NO. Just let it reboot.
You will be rooted. Download and install busybox from the market to complete the process.

bleez99 said:
1. Go here and download the CWM / TWRP / MobileODIN installable ZIP
http://forum.xda-developers.com/showthread.php?t=1538053
Place the installable zip on your INTERNAL SD Card.
2. Get CWM:
http://www.clockworkmod.com/rommanager
Go here and grab CWM 6.0.3.6 for the INTERNATIONAL I9505 - yes, it works on the I9505G
Put your phone in fastboot mode by turning off the phone completely. Hold down Vol-Up Vol-Down and power simultaneously.
Since you already seem to have adb, you probably have the fastboot executable.
From your computer's command line type "fastboot boot recovery-clockwork-6.0.3.6-jfltexx.img"
This will boot recovery - temporarily - it will not overwrite the recovery on your phone.
Choose install zip from sdcard. Navigate to the installable zip that you placed on you sdcard in a prior step.
Reboot. When CWM asks to fix "this may overwrite your recovery" SAY NO. Just let it reboot.
You will be rooted. Download and install busybox from the market to complete the process.
Click to expand...
Click to collapse
Worked like a charm! Only hiccup I had was it wouldn't let me access the file from the SD card, only internal memory.
2nd question is, IF i needed to restore everything to stock again at some point in the future, what steps would I need to take?

nhlfan14 said:
Worked like a charm! Only hiccup I had was it wouldn't let me access the file from the SD card, only internal memory.
2nd question is, IF i needed to restore everything to stock again at some point in the future, what steps would I need to take?
Click to expand...
Click to collapse
Since you have the stock recovery, all you need to do is unroot and you're done. Triangle Away works fine for the I9505G just in case you've bumped you flash counter. Ah yes, search the forums for busybox uninstaller. It's also a flashable zip.
Please hit the thanks button if this helped.
When dialog fails, it's time for violence.

Can someone help me again. I'd like to restore the phone to complete stock. I followed the instuctions here:
http://forum.xda-developers.com/showthread.php?t=2265477
But i get a SECURE CHECK FAIL : SBL2 error.
I just want to start fresh.
thanks.

nhlfan14 said:
Can someone help me again. I'd like to restore the phone to complete stock. I followed the instuctions here:
http://forum.xda-developers.com/showthread.php?t=2265477
But i get a SECURE CHECK FAIL : SBL2 error.
I just want to start fresh.
thanks.
Click to expand...
Click to collapse
Anybody?

nhlfan14 said:
Anybody?
Click to expand...
Click to collapse
U can try follow this guide: HERE

LG G2 upgrade KitKat assistance

I posted yesterday on this topic but wanted to give an update.
I downloaded the cyanogenmod for my LG G2. The you tube video I watched as watch?v=tyBc45ScZzw. When I try to reboot into revovery mode all I get a black screen and little Android guy with a red triangle over the top and a exclamation point in it.
\\\
Any help as to what I am doing wrong to get into recovery mode? I actually factory defaulted yestersday and tried again and the same thing is happening.
Thanks for the help

TheBull50 said:
I posted yesterday on this topic but wanted to give an update.
I downloaded the cyanogenmod for my LG G2. The you tube video I watched as watch?v=tyBc45ScZzw. When I try to reboot into revovery mode all I get a black screen and little Android guy with a red triangle over the top and a exclamation point in it.
\\\
Any help as to what I am doing wrong to get into recovery mode? I actually factory defaulted yestersday and tried again and the same thing is happening.
Thanks for the help
Click to expand...
Click to collapse
Seems you haven't installed a custom recovery yet buddy, if you tried, you've failed.
First root your phone, then install a custom recovery, then try again booting into your recovery.
If your already on stock kk, I don't believe you can install a custom recovery yet, only root it. So you would first have to downgrade back to JB.
Check the

Merfy said:
Seems you haven't installed a custom recovery yet buddy, if you tried, you've failed.
First root your phone, then install a custom recovery, then try again booting into your recovery.
If your already on stock kk, I don't believe you can install a custom recovery yet, only root it. So you would first have to downgrade back to JB.
Check the
Click to expand...
Click to collapse
What would be the best custom recovery to install? I def know my phone is rooted. That I already check. I have yet to go up to KK . My phone says Android Version 4.2.2

TheBull50 said:
What would be the best custom recovery to install? I def know my phone is rooted. That I already check. I have yet to go up to KK . My phone says Android Version 4.2.2
Click to expand...
Click to collapse
Well there only 2 options really, I'd say TWRP is more user friendly, so i would recommend that to you, before installing a rom first read the instructions and make sure they haven't first recommend a recovery for that specific rom installation.
Once you have a custom recovery its very simple to switch between them.
Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2469995
It's an old method but is very easy. This will install twrp but an old version.
So before using the method above first download the latest twrp onto your phone, i don't know what version of the g2 you have so if you reply i can try point you to the latest, but if you search for twrp 2.7 for your phone you should find it. You want it in .zip format.
So after saving the file to your phone, go ahead and follow the instructions above, if it says it successful, try booting into recovery again, the same way you managed to format your phone but this time it should boot your recovery, then press install .zip and flash the latest twrp.
Then your ready to go! just follow the instructions for the roms you'd like and flash them.
Best of Luck!

Merfy said:
Well there only 2 options really, I'd say TWRP is more user friendly, so i would recommend that to you, before installing a rom first read the instructions and make sure they haven't first recommend a recovery for that specific rom installation.
Once you have a custom recovery its very simple to switch between them.
Follow the instructions here: http://forum.xda-developers.com/showthread.php?t=2469995
It's an old method but is very easy. This will install twrp but an old version.
So before using the method above first download the latest twrp onto your phone, i don't know what version of the g2 you have so if you reply i can try point you to the latest, but if you search for twrp 2.7 for your phone you should find it. You want it in .zip format.
So after saving the file to your phone, go ahead and follow the instructions above, if it says it successful, try booting into recovery again, the same way you managed to format your phone but this time it should boot your recovery, then press install .zip and flash the latest twrp.
Then your ready to go! just follow the instructions for the roms you'd like and flash them.
Best of Luck!
Click to expand...
Click to collapse
I'm using a Verizon LG G2 VS980 . I just downloaded TWRP 2.7 though so I am going to give that a go !!

Root stock 5.1 - Ub only

I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.

@levone1 link isn't working! pls fix.

itskapil said:
@levone1 link isn't working! pls fix.
Click to expand...
Click to collapse
Sorry, the parentheses got included in link. It's better now. By the way, I got it from here http://forum.xda-developers.com/son...al/ftf-xperia-z1-compact-d5503-5-1-1-t3201650.
Also, here's a couple more links to make it easier...
https://mega.nz/#!E4UQwIoZ!UFpur2wY3tIAU7SdjuEg5fUA6N4BAVwX_TeK_CFpTyo
https://mega.nz/#!k5E0kQpC!XdTudAe5ISAVyfQAHHMkgvjmNuY6TDxm62HzyOAEgmU
I'll post a CM boot link later if needed, or just download one.

http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799 is a nice addition to this method, (to get recovery and busybox after root). You can flash it with Rashr app on phone with root, (version 2.2.8).

levone1 said:
I'm no expert, so maybe a better way, but it worked for me, so try if you want...
Needed: stock ftf, (I used this https://shry.me/9L9OQ); CM boot img; TWRP img; Flashtool; fastboot, Supersu flashable zip.
1. Flash stock ftf with Flashtool, boot phone, and check 'android debugging ' and 'unknown sources'
2. Power off, hold volume up, and connect in fastboot mode
3. cd to adb directory on PC, type 'fastboot flash boot (CM file).img', and 'fastboot flash recovery (TWRP file).img'
4. disconnect phone, power on, volume up when you see led to enter recovery. Install > Supersu zip.
5. Power off, open Flashtool, and again flash ftf, but in 'exclude' box on right side, check everything except 'boot bundle, kernel, and fotakernel. (hopefully I'm remembering right).
When done, reboot, and you're rooted.
Click to expand...
Click to collapse
Links to these files?

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
3rd post has everything but CM boot. I'll post it if you need it. Or you could just download a ROM and extract.

NRG1975 said:
Links to these files?
Click to expand...
Click to collapse
This should work for boot IMG - https://mega.nz/#!Jh0DETBQ!E-9WTlINpfq5r3PIiKaIXRId7ar8g3c8YHTJha1N6LM

This really is not that easy .... While it may be the easiest way, it is far from easy with Win 8 or Win 10. I am gonna forego root till an easier way is found. Thank you for your efforts.

No Busybox
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
Use stericson busybox from play store. I tried the other one and it didn't work, but that one worked for me. You can also manual push busybox if you have to.

aravindclpy said:
I was able to root my phone following your method. It was easy.. however I can't install busybox or use apps which requires busybox installation. Is there any workaround for this issue?!
Click to expand...
Click to collapse
You can also use this - http://forum.xda-developers.com/son...root-init-d-support-recovery-busybox-t3202799
Since this came out, I recommend it over my method, since everything is included, and it's faster than using FT a second time.

Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)

Jackhass said:
Hey,
Usually this kind of stuff isn't a problem for me, but here I'm stuck at step 4.
When I try to flash superSU.zip, TWRP reboots by itself.
Also when TWRP boots, I'm asked to choose "keep read only" or "allow modifications" for the system partition. Both choices results in a reboot of TWRP.
Any idea ?
(I tried with the method in the link above, same thing happens)
Click to expand...
Click to collapse
Only time I ever got that from twrp was after doing ta update and booting into the new recovery. I just picked 'allow' and everything was fine. Are you booting into recovery the new way, or old? Are you using all of the files I posted, or a different boot, etc? My first shot would be to try a different recovery IMG, like an older twrp,and see if it works. I did all the above with the old recovery method, (wait for LED and vol up). Let me know...

@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway

Jackhass said:
@levone1 Thanks for your answer
I redownloaded all your files, did it again (exactly as it's said in the OP) and... it worked. I've done nothing more or less than last time I tried.. Unexplainable
Thanks anyway
Click to expand...
Click to collapse
Great... If you want busybox, etc., see the posts before yours.

Update (.216)
Just bumping thread for new fw. After FT flash, there is no r/w access. Can't use method in this forum without busybox, so to get busybox, just download nut dual recovery 'installer' option, and run on pc. Steps are same otherwise. I posted an ftf here - http://forum.xda-developers.com/sony-xperia-z1-compact/general/216-stock-ftf-read-flashing-t3243728

levone1 said:
Just bumping thread for new fw. After FT flash, there is no r/w access.
Click to expand...
Click to collapse
The steps I took with UL BL...
Used the Flashtool and XperiFirm to download and flash 216.
Hot booted 368 kernel and flashed SU zip, confirmed root with TB and Root Explorer after reboot to stock 216 kernel.
Installed Busybox from Play Store.
Extracted kernel.sin from ftf and used @[NUT]'s Kernel Builder to add XZDualRecovery.
Extracted boot.img from zip and flashed with Fastboot.
Now I'm in the process of removing bloatware then I'm going to theme it.

Do I just pooch myself?

Ok, so I've read until my head hurts. So please take pity on me if there is a thread that answer this question already. Please direct me if that's the case...
On to my problem.
I was running Optimal Rom 13-1 just fine minus the Samsung bluetooth glitch. But since There have been updates to that ROM since, I figured I'd update to 15-5.
I followed these instructions.
1. Download and install NI2Flasher.apk
2. Download and copy G900V_*_Stock_KERNEL_SafeStrap-Flashable.zip to sdcard.
3. Run NI2Flasher and select flash.
4. Grant root access for NI2flasher
5. After the app flashes the NI2 kernel tap the reboot button.
----This will reboot your device directly to Safestrap.
6. BACKUP YOUR CURRENT ROM!!!
7. Flash OptimalROM_*_BigBot96.zip
7. Do NOT forget to flash the G900V_*_Stock_KERNEL_SafeStrap-Flashable.zip afterwards.
----If you do forget you can always select recovery at the Safestrap splash screen.
8. Reboot system after flashing kernel
I chose the G900V_OG5_Stock_KERNEL_SafeStrap-Flashable.zip MD5: 0c1a06d1358cdfd19513043ee370dac1 file.
I am now in 15-5 Optimal ROM without Root and no ODIN access.
Phone seems glitchy which makes things worse. Play store FC's.
Cant install BusyBox. Im sure there's more.
Please assist as I am frustrated at this point.

Robertjpjr said:
Ok, so I've read until my head hurts. So please take pity on me if there is a thread that answer this question already. Please direct me if that's the case...
On to my problem.
I was running Optimal Rom 13-1 just fine minus the Samsung bluetooth glitch. But since There have been updates to that ROM since, I figured I'd update to 15-5.
I followed these instructions.
1. Download and install NI2Flasher.apk
2. Download and copy G900V_*_Stock_KERNEL_SafeStrap-Flashable.zip to sdcard.
3. Run NI2Flasher and select flash.
4. Grant root access for NI2flasher
5. After the app flashes the NI2 kernel tap the reboot button.
----This will reboot your device directly to Safestrap.
6. BACKUP YOUR CURRENT ROM!!!
7. Flash OptimalROM_*_BigBot96.zip
7. Do NOT forget to flash the G900V_*_Stock_KERNEL_SafeStrap-Flashable.zip afterwards.
----If you do forget you can always select recovery at the Safestrap splash screen.
8. Reboot system after flashing kernel
I chose the G900V_OG5_Stock_KERNEL_SafeStrap-Flashable.zip MD5: 0c1a06d1358cdfd19513043ee370dac1 file.
I am now in 15-5 Optimal ROM without Root and no ODIN access.
Phone seems glitchy which makes things worse. Play store FC's.
Cant install BusyBox. Im sure there's more.
Please assist as I am frustrated at this point.
Click to expand...
Click to collapse
have you tried flashing back to NCG and re rooting?
this might help
http://forum.xda-developers.com/showthread.php?t=2784880

I fixed
Veid71 said:
have you tried flashing back to NCG and re rooting?
this might help
http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
So this thread can be deleted. I am an idiot...
I couldn't get to Odin because I hadn't installed the Samsung drivers since my upgrade to Win 10.
All is well. Flashed my safestrap kernel, restored. Root is intact.