Database Info

HELP: How to Root but keep stock rom?

Hi, I am currently using the Nexus S i9020a on 4.0.4 and it's unrooted on stock rom.
I wanted to know if it was possible to root it (for apps like AdAway) and maintain the stock rom? The reason why I want to keep the stock is because I tried Cyanogen a few months back and it crashed at least twice a week for me. This is troublesome because at night I use the phone as an alarm and it crashing would kill the purpose.
Thank you!

does it show the unlock icon when you boot?
if so, it should be pretty easy.
just flash a su.zip
if you're locked
you need to unlock your bootloader (which may factory reset your phone)
so backup, unlock bootloader, flash clockwordmodrecovery and su.zip
and there you are, stock, with root

The bootloader is unlocked.
How do I flash su.zip? I had someone do it for me last time so I can't remember how.
I can DL the SuperUser app off the app store but I've learned that it does nothing.
Lastly, is it possible to flash su.zip (wherever that is found) without using a USB cable (mine broke, need a new one I guess)?

Nook000 said:
The bootloader is unlocked.
How do I flash su.zip? I had someone do it for me last time so I can't remember how.
I can DL the SuperUser app off the app store but I've learned that it does nothing.
Lastly, is it possible to flash su.zip (wherever that is found) without using a USB cable (mine broke, need a new one I guess)?
Click to expand...
Click to collapse
you can use SolidExplorer's share files feature (via FTP client) , or AirDroid (via internet browser) to push over su.zip
su is here
http://downloads.androidsu.com/superuser/su-bin-3.0.3.2-efghi-signed.zip
move that to your sdcard and boot into clockwork recovery with (VolUp + Power, then select Recovery)

I tried downloading that file and then going to Recovery.
I did "apply update from /sdcard" and hit the .zip file but I get the following errors:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?

Nook000 said:
I tried downloading that file and then going to Recovery.
I did "apply update from /sdcard" and hit the .zip file but I get the following errors:
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verification failed
Installation aborted.
Any ideas?
Click to expand...
Click to collapse
are you sure you have clockworkmod recovery installed?

Not completely sure, when I go to Recovery, the top says:
"Android System Recovery <3e>"
Edit: I just went to http://www.clockworkmod.com/rommanager to download CWM Recovery but it's an .img file which it won't let me flash after reboot into Recovery.

Flash it either via fastboot or download through Rom Manager and install. I usually do the former.
Open up adb.
Turn off device and power back on into fastboot(power+vol up)
Make sure the recovery image is in the same directory as adb.
Name the recovery image to recovery if it hasn't been changed
Type fastboot flash recovery recovery.img
I've done it that way for a while now no issues. You also need a script or a .zip file that will keep the custom recovery so the stock one doesn't replace it.
You can flash it:
http://forum.xda-developers.com/showpost.php?p=23125913&postcount=2
Or you can edit the file that does this by following these steps in this post
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
HTH

Thank you a whole very much!! Using both of your advice, I was able to root the device. It took a while because despite installing the drivers, when I went into the Bootloader, it wasn't detected. The remedy was manually setting it to the Bootloader driver irregardless of Windows suggesting I shouldn't.
Now it's all good to go! Thanked you both.

chronophase1 said:
Flash it either via fastboot or download through Rom Manager and install. I usually do the former.
Open up adb.
Turn off device and power back on into fastboot(power+vol up)
Make sure the recovery image is in the same directory as adb.
Name the recovery image to recovery if it hasn't been changed
Type fastboot flash recovery recovery.img
I've done it that way for a while now no issues. You also need a script or a .zip file that will keep the custom recovery so the stock one doesn't replace it.
You can flash it:
http://forum.xda-developers.com/showpost.php?p=23125913&postcount=2
Or you can edit the file that does this by following these steps in this post
http://forum.xda-developers.com/showpost.php?p=27027436&postcount=8
HTH
Click to expand...
Click to collapse
He's right...and thanks for the refrence
If you are going to keep stock then when you reboot Clockworkmod Recovery won't stick. Do as I said in the referenced post or flash a new Rom (my choice , or just live with it. If you want CWM you will have to USB, cmd fastboot flash recovery recovery.img every time.
Edit: posted a minute before me. Awesome and enjoy!

Glad to hear it worked! And no problem, bud! I try to keep the good posts saved for situations like this

guide
Personally when i rooted my nexus S for the first time,i followed this guide
Its precise,step-by-step and includes a video incase you need one
i am prevented from posting the link but if you search google for nexusshacks.com,you should easily find it.

[Q] Error on Installing TWRP and Can't recover to ICS, same Problem?

I have had my TF700 for a while, and merrily went from ICS through the various OTA upgrades to 4.2.1
I have attempted to follow along the "All in One Guide" in order to get Rooted so I can install Cyanogenmod or alternative to get rid of the crapware delivered by Asus. But I seem to get stuck when trying to "Flash" anything. Or at least I think so.
I unlocked the bootloader using the apk provided by Asus. Bootloader shows as unlocked when booting.
adb devices shows my device attached. When booted into fastboot mode fastboot devices shows my device attached.
I have also done a complete data wipe, not that that should matter.
1st, I have tried to install twrp using GooManager, and the fastboot method. Using GooManager, the file downloads and then nothing seems to happen. GooManager will also not reboot to recovery. Using the Fastboot method I get "error: cannot load 'twrp.blob': No error". I have downloaded the file multiple times and it does not appear to be corrupted.
I have tried to roll back to ICS by downloading the correct firmware, renaming it and copying to my SDCard, then booting into recovery. US_epad_user_9_4_5_30_20120907_UpdateLauncher.zip I only get the Android guy with the red triangle until it reboots.
I have also tried http://forum.xda-developers.com/showthread.php?t=1929712 but this does nothing as twrp is not installed and the regular recovery doesn't do anything.
What should I try next? It would seem like I'm missing something obvious.

When you download firmware from Asus, the file you need to put on your SDCard is not the file you downloaded, but the zip file contained within. Its a zip in a zip. Extract the file you downloaded and you will find another zip file inside and that's the one you rename and copy to your SDCard. Also make sure your SDCard is formatted FAT32. exFAT will not work and is the default Sandisk format.

Got rolled back to ICS but..
I successfully rolled back to ICS .30
Now adb fails to recognize the device. Previously it did recognize. I reinstalled the drivers in fastboot mode and "normal" mode. I have tried the universal naked drivers and the Asus drivers. fastboot reboot will successfully reboot the device, but nothing shows up when I do a adb devices or fastboot devices.
fastboot -i 0x0B05 flash recovery twrp.blob Gets the same error, error: cannot load 'twrp.blob': No error.
When I run through *** Rooting Your TF700 with Debugfs automated root *** I get the error "You must install device specific drivers...."

Fixed
Adhar said:
I successfully rolled back to ICS .30
Now adb fails to recognize the device. Previously it did recognize. I reinstalled the drivers in fastboot mode and "normal" mode. I have tried the universal naked drivers and the Asus drivers. fastboot reboot will successfully reboot the device, but nothing shows up when I do a adb devices or fastboot devices.
fastboot -i 0x0B05 flash recovery twrp.blob Gets the same error, error: cannot load 'twrp.blob': No error.
When I run through *** Rooting Your TF700 with Debugfs automated root *** I get the error "You must install device specific drivers...."
Click to expand...
Click to collapse
I discovered that I couldn't install twrp as I was in the wrong folder when executing the command. I needed to cd to the folder that contained the .blob file. Then it was trivial to use twrp to flash the root.zip file and gain root, and then flash cyanogenmod 10.0, wipe, and then reboot.
Everything is fine, now downloading Google apps.

Adhar said:
I discovered that I couldn't install twrp as I was in the wrong folder when executing the command. I needed to cd to the folder that contained the .blob file. Then it was trivial to use twrp to flash the root.zip file and gain root, and then flash cyanogenmod 10.0, wipe, and then reboot.
Everything is fine, now downloading Google apps.
Click to expand...
Click to collapse
When I read "seems like I'm missing something obvious" from your original post I went back and re-read it looking for the obvious. It wasn't immediately apparent what was wrong. If you hadn't posted the name of the firmware file it wouldn't have been obvious to me either but I thought I recognized it as the downloaded not the internal zip file name and verified it with my downloaded firmware. Glad to help and that you got it all worked out.

Lost TWRP and root after update to MIUI 10

Hello,
I have a Mi Mix 3, MIUI global 10.2 stable, 10.2.2.0 PEEMIXM.
I managed to root, install TWRP and gcam after a few days of trying.
* Two days ago I updated from phone settings (About phone, Check updates ...)
* I lost both root and TWRP.
* I tried exactly the previous methods to root and phone stuck at booting (three dots flicking on the screen) - via PC / adb / fastboot.
* After that, I reset phone to factory settings and try again - boot in fastboot, try to flash TWRP and I get this error message: error cannot load TWRP.img file (not available or missing).
I also mention:
1. Phone was already rooted by the same procedure
2. Phone is unlocked
3. Dev options / USB debugging check
4. I renamed TWRP.img with recovery.img
5. I even try "TWRP" without extension ".IMG" (last week before the update I succeeded this way - no .img in the name of the file)
Please help
I need something so that I can root phone again AND won't delete TWRP and root after next update.
Thx very very much.

Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.

PWn3R said:
Any software update on this phone will overwrite TWRP if it has a recovery partition image, which most Xiaomi updates do have. There is a way to block it from getting overwritten by booting the phone, which has been implemented in the latest versions of the Chinese TWRP image. I do not know if they have been implmented on the official TWRP for our device.
Based on what you posted, it sounds like you probably need to reboot into the bootloader and use fastboot flash recovery "TWRPIMAGE.IMG" to install TWRP, then hold VOL Down + Power and reboot into TWRP. Once that is done, you can root again using MAGISK or whatever you choose to use for root.
Click to expand...
Click to collapse
Thank you very much for your time and information. I must add that I was able to flash TWRP according to the procedure explained above, but I couldn't enter/access TWRP recovery. Then, I tried to re-flash TWRP and I always get the message: "error cannot load 'twrp.img' no such file or directory"
And I've tried several methods, several TWRP, different USB cables - almost everything you can imagine. Still, I cannot load the TWRP.img - it's not found. I must say I follow exactly the procedure explained in every posts.
What options do I have?

If you are using adb to load twrp, try putting it in the c/ of your pc, and putting twrp image in the adb folder, and if that didnt work, try renaming the img file to pocorecovery

HELP "Your system has been destroyed"!!!

So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help

Try to manual flash using fastboot
Fastboot flash system system.img
Fastboot flash recovery recovery.img
Then flash EU rom

LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
The same thing happened to me when I tried to install and use TWRP.
To fix this, I used the MiFlash tool and flashed the fastboot ROM which you can download from here.

LovingDracula04 said:
So I was trying to install a custom ROM (first time ) did unlock my bootloader and when wiped using twrp and then rebooted to twrp for flashing the ROM it said that system has been destroyed when I tried to reboot to recovery then also it was of no use.I tried to flash fastboot roms via miflash tool. The new versions couldnt find scripts o don't know why so I tried the old ones but the flash got completed in 1 second so it was useless.further more I think that I have anti rollback v2 in my phone and that's why I'm not able to go anywhere..
Is there any fix please help
Click to expand...
Click to collapse
I had the same issue, but my phone went to fastboot from there I flashed it, the process was simple :
1. Download the fastboot rom and extract it (I guess two times, the first extraction extracts a file, open that with some extraction tool and uzip again, there you will see the fw with certain folders and images etc ).
2. Download the adb/fastboot zip file I"ll attach that here, extract it to the same folder where your fw files are. (fw = firmware).
3. You will find 3 bat files, flash all, flash all and lock, flash except storage, choose flash all (execute it).
4. Once done, reboot to recovery (stock), do a data wipe again.
This worked for me, hope it does for you too.

try unlock bootloader via internet

format data once via twrp

Nokia 3 TWRP Unable to flash Magisk

Hello,
I flashed TWRP 3.1.1-0 from this post, but it doesn't seem to work at all. I am only able to view folders, I was able to use 'adb push' to get Magisk zip file to show up, but now when I try to flash it, it keeps giving me errors:
'Updater process ended with ERROR: 127'
'Error installing zip file '/Magisk.zip'
This 3.2.1 Post link is dead.
Same for this one.
I couldn't find any other recovery flashes such as OrangeFox since they don't support my device.
Also, I have unlocked the Bootloader, but when I try to start it I get "Orange State". Kind of annoying.
I am on Android 9.