Database Develop

[GUIDE] Complete and Thorough Guide to Rooting the Nexus S [+ No wipe] [GRH78C]

May NOT work for 2.3.3, if attempting on 2.3.3 use old part 1! - Will wipe all data though
Windows ONLY!
Hey guys, rooted my Nexus S today, and decided to write a thorough, detailed guide on how I did it, as none of the guides I had found had everything detailed. I came across a few problems, and all of this is in the guide. I successfully completed it on my Nexus S running 2.3.2, so any version below that will also work.
The original guide was made by AllGamer, and can be found here. I followed this guide, and added things when I found it was needed
The full guide with everything (including links, pictures) can be found on my site, Complete Android.
New info: Upon finding another thread over at XDA (http://forum.xda-developers.com/showthread.php?t=931865) it has been realized that you can root your Nexus S without unlocking the bootloader, and therefore not loosing your data on the SD card. Part 1 for the new method is still the same, but choose the new Part 2!
WARNING: Rooting your device will wipe all data off it, so you will loose EVERYTHING! Make sure you backup all important data first. Only applies to old Part 2 (fastboot oem unlock method), but it is still a good idea to backup important information!
Click to expand...
Click to collapse
What you will need:
Nexus S (obviously)
Android 2.3 SDK
USB Cable
PDAnet (for drivers)
Clockwork Recovery Image
Superuser
Part 1
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Once it has finished downloading, unzip it, and run the SDK manager.
Select whatever components you wish to install, but you MUST make sure you install Google USB Driver (Available packages > Third party Add-ons > Google Inc. Add-ons > Google Usb Driver package, revision 4) otherwise this guide will not work!
We must now install the Google USB Driver, or the phone will not be recognised as a device other than a mass storage device.
Connect your Nexus S to your computer, and put it in USB storage mode.
Put it in USB Debugging Mode (Settings > Applications > Development > USB Debugging)
Windows should now recognise your Nexus S when you plug it in, and ask to install drivers. It probably won’t find anything, so we need to help it manually.
(Installing drivers manually varies between Windows versions, so please refer to http://developer.android.com/sdk/win-usb.html if you are having trouble). Launch Device Manager (you can find it in Control Panel), find Other Devices, and listed under that heading, you should find Nexus S. Right click, and select Update Driver Software. Click Browse my computer for driver software, find your SDK folder, then the google-usb_driver folder inside it, click OK, then Next. This should install the USB driver successfully. Reboot your computer.
Power off your Nexus S, connect it to your computer via USB cable, and boot it into the Bootloader Interface (you can do so by holding down the Power and Volume Up buttons at the same time).
It should say LOCK STATE – LOCKED, in white just above the green Android. You are now ready to move on!
Part 2 - Fastboot oem unlock method - WIPES ALL DATA!
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use ‘fastboot oem unlock’ (the rooting command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn’t).
Now in the command prompt, type in (without the quotes) ‘fastboot oem unlock’.
Now turn your attention to the phone, and read through the new information displayed on the screen. Using the Volume keys select Yes, then press the Power button. This will WIPE EVERYTHING! I bear no responsibility for any lost data on your phone!
If everything is successful, on your phone, the LOCK STATE should now read UNLOCKED, and on your computer, the command prompt window should say something like this:
Download the Clockwork Recovery image (here if you don’t already have it) to your Android SDK tools folder (*Android SDK*\tools).
Rename the newly downloaded Clockwork Recovery image to ‘recovery.img’ (no quotes).
Now we need to flash it to our Nexus S, so enter this command into the Command Prompt (make sure it is in the Androis SDK tools folder!) ‘fastboot flash recovery recovery.img’ (without the quotes).
If all is successful, the Command Prompt window should look something like this now:
Download the superuser app to the Android SDK tools folder.
Power on your Nexus S, leaving it connected to USB.
Mount the USB storage, and drag and drop the superuser .zip file you just downloaded into the root of the internal SD card (so Computer > *Device Name*, not in any other folders!). It should look something like this:
Power off the Nexus S, and return to the Bootloader Interface (step 9, part 1).
Select Recovery using the Volume buttons, then the Power button.
The phone should reboot into Clockwork Recovery, but if not don’t panic, just repeat steps 9-12, including downloading a new copy of the file (mine only worked the second time around, don’t worry!)
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot. (You will now also have an unlocked padlock when you boot up)
Done! You now have to set up your phone again like when you first got it, but it will be rooted now.
New Part 2 - Does NOT wipe everything - Keeps a locked bootloader
Make sure Part 1 is completed.
Make sure you have downloaded the Clockwork Recovery file and the Superuser file.
Move the Clockwork Recovery file to your tools folder within the Android SDK folder, and rename it to recovery.img (for simplicity).
Connect your Nexus S via USB to your computer and mount it as USB storage. Copy across the Superuser file to the top level of your sdcard. (So the first window you see, not in any other folders. The sdcard is just where all the files are stored, don't worry about it too much for now).
We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don't worry about this!). Follow along with any other instructions. You should be set now.
With the latest SDK version, some tools have been relocated to another directory, so we need to make a copy and move them back. Navigate to the directory where you unzipped the Android SDK file in part 1. Inside it, go to the platform-tools folder, and copy both AdbWinApi.dll and AdbWinUsbApi.dll. Go back to the main Android SDK directory and find the tools folder. Paste these two files in there, and we are all ready to use 'fastboot boot' (the boot image command) now.
Open a command prompt window (Start > Run > cmd.exe).
Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) 'cd c:\*YOUR SDK*\tools'.
Make sure your Nexus S is still in the Bootloader Interface (refer to step 9, part 1 of it isn't).
We now need to use the 'fastboot boot' command to load Clockwork Recovery onto our Nexus S. In the command prompt, type in the following (but without the quotes, as always) 'fastboot boot recovery.img'
Once you are in Clockwork Recovery (it may take a couple of tries, don't panic, just redownload Clockwork Recovery, and complete steps 3 and 10, part 2) it should look something like this:
Using the Volume buttons and Power button, select install zip from sdcard.
Select choose zip from sdcard.
Select the su-version#-signed.zip file you downloaded earlier and apply it.
Select yes (there are lots of nos).
Confirm it says something like this: install from sdcard complete
Select Go Back.
Select Reboot.
Done! You should still have all your data present on your phone, and have root access!
Notes
As AllGamer said in his tutorial:
It’s normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you’ll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you’ll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Keep this in mind! It's not because you did something wrong
Also, some root apps require BusyBox to be installed, as I found out with Titanium Backup, so once you set up your Nexus S again, head on into the Market, and download BusyBox. It installed fine on my Nexus S this way, and now TB works fine.
I hope this is the best, most thorough guide you will find on rooting the Nexus S. Enjoy! Feedback is appreciated, and I will help out if you need any extra help.

Your guide has been wonderful however I'm stuck on part 2, step 4. I tried writing in the path to my directory and they keep giving me whatever I wrote in the command prompt "is not recognized as an internal or external command, operable program or batch file"
"Change to the tools directory within your Android SDK folder by using the following command (without the quotes and replacing *YOUR SDK* with the path to your Android SDK folder) ‘cd c:\*YOUR SDK*\tools’."
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks

Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.

STARSCR33M said:
This is how my command prompt looks like when I first open it. "C:\Users\Du>"
and this is what I typed in the command prompt: "Downloads\android-sdk_r09-windows\android-sdk-windows"
^^^I did exactly what you said above and nothing is happening. I don't know whether I'm writing in the directory wrong or what. Please help me out thanks
Click to expand...
Click to collapse
Ok so if you want to change directories in the command prompt, you need to use the command
Code:
cd
So in your case I would type in
Code:
cd c:\Users\Du\Downloads\android-sdk_r09-windows\android-sdk-windows\tools
That way is fool proof, however you could take a shortcut, because you are already in the Users/Du folder (because of how it looks when you first open it), you could just type in
Code:
cd Downloads\android-sdk_r09-windows\android-sdk-windows\tools
Hope that helps

ravidavi said:
Your guide is nice, however as shown in distortedloop's stickied Root & Recovery thread, fastboot oem unlock is not required for rooting & flashing. We no longer have to lose all our sdcard data when first rooting and/or flashing a ROM.
Click to expand...
Click to collapse
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
EDIT: New approach added, now there is choice and easyness for all
Other than that, this seems to be a nice amendment of Allgamer's sticked root & recovery thread. I'm sure it will be useful to many.
Click to expand...
Click to collapse
Thanks

Jonathon Grigg said:
I think this way is a cleaner approach personally, but hey choice is good That's what Android is all about
Thanks
Click to expand...
Click to collapse
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step. Once you're in clockwork you pretty much own the phone. I'll be interested to see if someone can use clockwork to flash a new boot image once rooted without the unlock; if so I can't see any reason to unlock the bootloader. That said, mine is unlocked, and I like it that way, but many won't root for fear of losing data on the phone.
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it. I guess that's there own fault for not doing enough searching on their own...
Anyways, nice and thorough effort. I'm sure many will benefit from your additions to AllGamer's tutorial.

distortedloop said:
I'm not sure that wiping all your data pointlessly is "cleaner."
It's not even clear what exactly the oem unlock of the bootloader really does for us, since you can get into clockwork recovery without that step.
Click to expand...
Click to collapse
I have been wondering that myself. My guess is that for the average user you don't need to, but maybe it's for real power users who build their own ROM which has been fully modded or something, I'm not sure.
but many won't root for fear of losing data on the phone.
Click to expand...
Click to collapse
I definitely agree with that, and your guide is probably the best way for those people!
Even if you end up having to do the oem unlock in the long run for some activities you want to do, it seems that rooting, then installing Titanium and backing up your apps and app data fully is a better way to go than just losing all your data (any app that doesn't store its data on the sdcard) that can't be backed up without root would be a lot less painful than WIPING everything on the phone, including the sdcard.
Click to expand...
Click to collapse
Exactly, this is one of the better uses for both methods. I already had to wipe my phone twice due to Samsung CS so I'm used to it Although it does give you a chance to clear out the apps you don't need. Doing that I noticed better battery life on my phone.
It's not worth arguing about, but I think any method that is including the oem unlock step should at least mention that that step can be skipped. How many people will go through the pain of a wipe that they didn't need to because they didn't see that there was an option without it.
Click to expand...
Click to collapse
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Thanks distortedloop

This is awesome cause i relocked my bootloader i really just needed root. Thanks!
Edit oops lost track of tabs open.

I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.

Jonathon Grigg said:
I wasn't going to argue I'm happy to adjust my tut to include something about this, after all it was aimed at more beginners.
EDIT: Added a new part to my tutorial based on your guide, just includes some more detail. Thanks again.
Click to expand...
Click to collapse
Nicely done. Thanks.
sam4free said:
I think we can use this method to unlock oem without wiping data.
boot cw -> full backup -> unlock and flash cw (wipes data) -> restore backup (got ur data back and oem unlocked)
the only problem i can think of is that restoring backup would re-lock oem again but i am not sure of that.
i can't try this right now but if someone could, please give feedback.
Click to expand...
Click to collapse
That's what I suggesting a couple of posts above (root without unlock to at least make a backup of user data).
Restoring a titanium backup would not re-lock the phone. A nandroid restore might, depends on what all it imaged and restores, but it's so easy to re-root, that doesn't seem like a big deal.

Jonathon Grigg said:
Download the Android 2.3 SDK (or direct from Google here, 32MB).
Click to expand...
Click to collapse
Looks like you forgot to add the link in your copy pasta.

AtomicPC said:
Looks like you forgot to add the link in your copy pasta.
Click to expand...
Click to collapse
I've been working on it I just wanted to get it up here as soon as I could That's why I mentioned that the full guide is available on my website. I'm going back to school today, so I don't really have too much time for changing links now. Besides, most people on XDA should know how to look at the 'What's needed' part

Sent from my Nexus S using XDA App

Jonathon,
Thank you for posting this detailed guide to rooting without losing your data! I do have a question. As you've probably heard, there are a few updates coming soon and if they are like they were on the N1, they always broke root. So getting root back was tricky unless I "unrooted" before applying the update. Using your method, is it easy to "unroot"? Thanks!

No problems
As for your problem, I never actually had a N1 so I don't exactly know why that would happen. So far from the 2 updates available to NS owners it seems like the OTA update does break root but it appears to be the same to get it back again. Can someone confirm this? I haven't been through an update with my root yet.
As for unrooting, if you haven't unlocked the bootloader (so you have followed the new part 2) I think it is just a case of finding a stock image (I think there's a GRH78 one around here somewhere) and booting into Clockwork Recovery and flashing it. That should remove root and then also give you a notice to install the GRH78C OTA update so you get the latest version.
I think that is what you meant? If you did unlock the bootloader (using the original part 2) then I think you just have to follow the same steps as I mentioned just then but afterwards go back into the bootloader interface and run 'fastboot oem lock' and it should be right.
Sent from my Nexus S using XDA App

Question on Part 2- step 1.
Code:
# We now need to install PDAnet on our PC so that Windows can see our Nexus S when we are using the Command Prompt. Install PDAnet from here, select Samsung when asked about the Manufacturer, allow the driver to be installed (because the driver is unverified, don’t worry about this!). Follow along with any other instructions. You should be set now.
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.

hmanxx said:
Why above step is required if one already installed USB Driver for Nexus S and "ADB devices" command can find the device ?
On Allgamer thread didnt ask to repeat installing USB driver ?
What purpose for the pdanet driver ?
I dont want to put redundant drivers into my system which may interfere each other during flashing process.
Click to expand...
Click to collapse
When I tried to use the fastboot command with my Nexus S connected, it would hang and not do anything, despite leaving it for about 5 minutes. I searched online, and found the PDAnet solution, so I don't know what the difference is exactly. All I found the Google SDK USB drivers to do is enable you to see your device in Device Manager, however you could try it without the PDAnet drivers, and let me know what happens!
Thanks

Thanks for the prompt reply.. I tried out the google driver..it doesnt work under fastboot. I eventually get the fastboot enabled driver..that could explain why the pdanet driver required.
After i installed the fastboot enabled driver, i could test the connectivity under fastboot with "fastboot devices"
thanks going to try out rooting..i just want simple root access..without wiping data is a ++ ..

I managed to run fastboot boot recovery.img...going into clockwork menu..apply the superuser.zip.(for froyo version)..till completion..no word of failure..
However after rebooting, su and SuperUser.apk are not installed.( I used adb to check the system/app and system/bin folder.
Edit- manage to root properly after system mounting .
Just a note..to properly complete the rooting, one need to apply mounting then mount system before applying the Superuser.zip install from sdcard.
Prior to step 11, you may want to add the following steps for folks having problem to get the superuser.zip to install properly.
Originally Posted by droidmage
So all you guys who are having trouble getting root inside the rom, When your in recovery before you flash the superuser.zip file select -- mounts and storage -- then --mount /system -- then flash the .zip file and reboot
Click to expand...
Click to collapse

Thanks for the extra bit of info, I will attempt to add that in when I get a bit more time on my hands. when I did it it seemed to work fine so thanks for discovering that!
Enjoy your rooted phone
Sent from my Nexus S using XDA App

locked security warning by doing nothing

okay guys this is weird. til now i have only read the forums and did think about rooting my phone to install a custom rom because the latest htc update made my phone so horrible. but now anything changed cause this just happened:
i got an sms (using the preinstalled sms app) and answered to it. send the phone to "sleep" (?) by pressing power button once, like always. laying the phone back on the table, continuing playing darksiders2. maybe 5 minutes later the display brightens up by itself like if an incoming call but nothing happens. i grab the phone and try to press anything or swipe to see whats going on, but no input gets recognized. plus the button row doesnt get lighten up like normally. confused i tried to press the power button but even that shows no reaction. it just stayed that way, nothing i could do. because i had one freeze under 2.3.5 or so i took the battery out to do a hard reset. booting up again gets me now into the screen i only read here before: where you have to go to install roms from zips etc. but i have booted normally, without pressing the volume keys. the title row says: locked, security warning. rebooting the phone out of this only gets me back here. i dont get it. i mean i know this version is messed up but what is this? my phone is broken and i havent even tried to unlock or anything else it... my god. i dont know what to do. next week is coming up and i dont have multiple phones.
has anyone any idea? please help!
ps: please forgive me any language flaws, english isnt my mother tongue.

Possible solutions
- Wipe the data from recovery if you can, or from bootloader
- Install the ruu when you had before

What country are you/the phone from?

And give us the output of the command
Fastboot getvar all
Sent from my HTC Incredible S using xda app-developers app

hello, thank you for your replies!
i bought the phone over amazon.de and i'm from germany.
where do i have to write "Fastboot getvar all"? do i need to install something and connect the phone to usb or anything like that? i mean i read about some incS roms on the forums but never tried anything myself so i have to look into that first on how to set things up..
edit: so i finally managed to setup android sdk adb and get this command running. yay!
C:\Windows\system32>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.0002
(bootloader) version-baseband: 3831.18.00.11_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.10.405.1
(bootloader) serialno: XXXX
(bootloader) imei: XXXX
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4069mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: d41e50e7
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.030s
Click to expand...
Click to collapse

I think your best option is to just run the ruu http://d-h.st/7UC

ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?

benutzer001 said:
ok i have a question: im downloading the exe right now. is this an extracting archive and do i have to do anything with it or is it a real exe and a like precompiled autorun thing? btw what am i downloading here? is this the latest unmodified original htc system for my phone?
and yeah: how do i need to apply it?
Click to expand...
Click to collapse
It is an executable program. Just run it on a Windows PC and follow the instructions.

ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?

benutzer001 said:
ouch. so everything will be gone? i mean a have the sd and sim out but okay..
btw: i just dont get what this is. have you any clue on what happened here and/or why? this just makes no sense to me. how can it corrupt itself?
Click to expand...
Click to collapse
I don't know why this happen but yes everything will be gone.

i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.

benutzer001 said:
i doesnt work.. great..
program runs, checks version, newest version and version on phone are the same, i click okay patch anyway, phone reboots and progress bar shows up on pc. phone boots right to the locked-security warning menu and the pc bar gets stuck at waiting for bootloader. stays there 2 minutes and then aborts patching.
Click to expand...
Click to collapse
Try it again.

error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..

benutzer001 said:
error 171 usb connection error
edit: i found that the fastboot var gives an answer if the phone is connected but (as of my understanding) a basic command like adb devices shows up nothing. is says showing list of devices but the space stays blank. but the fastboot command gets an answer so there must be some sort of communication between phone and pc..
Click to expand...
Click to collapse
Do you have the HTC Sync app installed on your PC? If so, make sure it is not running in the System Tray or remove it all together and try again.
If you don't have HTC Sync installed, then install it to get the current drivers and then you can uninstall it and try it again.

which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.

benutzer001 said:
which parts do i uninstall after installing the sync package? i have the following:
htc sync
htc driver installer
htc bmp usb driver
do i just need to uninstall htc sync and keep the rest or uninstall everything?
edit: i only uninstalled htc sync keeping the rest. same error.
Click to expand...
Click to collapse
You can extract the Rom.zip file that the ruu is using and update manually.
Start the ruu software and stay on the first screen.
In your Start>Search programs and files box type %temp% and press enter. A temp window should appear.
search for rom.zip in that window and copy this file to your fastboot dir.
Now you have 2 options. Flash through fastboot
Code:
fastboot oem rebootRUU
fastboot flash zip rom.zip
or rename rom.zip to PG32IMG.zip, copy to your sdcard root, reboot bootloader(hboot mode) and let the bootloader detect the zip and install.

Nonverbose said:
and copy this file to your fastboot dir.
Click to expand...
Click to collapse
where is my fastboot dir? for the adb commands i've setup an android-sdk-windows folder in C: but nothing else.
just running the "fastboot oem rebootRUU" command from somewhere gets me this:
C:\Users\XXXX>fastboot oem rebootRUU
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(730): error 2
OKAY [ 0.052s]
finished. total time: 0.055s
Click to expand...
Click to collapse
i am doing all this with my bare phone, no sd and sim card inserted. is it necessary to backup my sd card and insert it?!
and does everything needs to be done in an elevated cmd?

Looks like hardware failure. Try the PG32IMG.zip method but I don't like your chances. From what I see, you did everything right.

so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?

benutzer001 said:
so you think it just died? when i try to send the rom.zip in an not elevated cmd over usb it sends correctly, then tries to apply it but aborts with an error saying smth. like flashing over remote is not allowed.
funny thing is that i dont have any other access to my microsd (32gig btw) other than my phone. and right now i cant access it or is there a cmd way? i dont think so because the phone os would be needed to unmount the sd card so that windows can access it, right?
Click to expand...
Click to collapse
I think you have fried emmc chip. Some batches of incS are notorious for it. It commonly occurs by powering down by removing the battery, but It's possible that it just died.
If you have another sdcard, I would try that before giving up hope. You should be able to copy the pg32img.zip by entering hboot USB mode.
edit: I had look back at your previous posts and noticed you didn't have sdcard inserted. It should be installed in the phone.

Rooting the OP3T without loosing anything and being able to revert to unrooted state

Ok, here the thing, I would love to root my OP3T, and I have downloaded the toolkit (https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729) and understood I will have to unlock bootloader and hence wipe everything. However, the backup options of the toolkit backs up apps and app data, but not the rest of the internal SD (i.e. my music, my movies, my files...). Any chances of having a tool with no root that would back up everything, so that I can restore my OP3T to the non-rooted state I had before tweaking it ?
Tried Helium, but no success. Thanks for the help.

StressFull said:
Ok, here the thing, I would love to root my OP3T, and I have downloaded the toolkit (https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729) and understood I will have to unlock bootloader and hence wipe everything. However, the backup options of the toolkit backs up apps and app data, but not the rest of the internal SD (i.e. my music, my movies, my files...). Any chances of having a tool with no root that would back up everything, so that I can restore my OP3T to the non-rooted state I had before tweaking it ?
Tried Helium, but no success. Thanks for the help.
Click to expand...
Click to collapse
How about copying the stuff via mtp or even better with adb (adb pull /storage/emulated/0/ C:\your\destination\folder\here)?

4_ever_dave said:
How about copying the stuff via mtp or even better with adb (adb pull /storage/emulated/0/ C:\your\destination\folder\here)?
Click to expand...
Click to collapse
Yep, agree. Any option for the lazy ones ?
Plus it does not really address the "back to unrooted" request !

[GUIDE]How to save your cactus from a “Vibrate massager”

Hi there,
I just save my cactus from a “Vibrate massager”.
If you got the same problem,this maybe help you.
First,download three tools;
1.MTK-Bypass
2.SP-Flash-Tool
3.MiFlash Professional Edition(Black logo,need install)(If you got a yellow logo edition and not need install,don't use it. It's public edition.)
My internet environment doesn't allow me to access a lot of websites(.etc Google,Youtube,Facebook,Twitter...),so try to google/bing it and download it.
If you got all needed tools,charge your “Vibrate massager”,and...
Here we go!
1.plug your cactus to pc.
2.open Miflash Professional.
3.select SP flash.
4.click "Options".
5.Go to "general".
6.Make sure all three options is "false" now.
7.select appropriate files for DA and scatter BUT WITHOUT "AUTH".
8.hold Volume+ and power,until your computer make response for it.
9.<--DO THIS IN 5 SECONDS-->
(1)Open MTK-bypass IMMEDITELY.
(2)Select MT6765(even cactus is 6762,but select 6765 anyway) IMMEDITELY.
(3)Click Bypass IMMEDITELY.
<--YOU CAN TAKE A BREATH NOW.-->
10.When bypass is complete,back to SP-Flash, and then click flash.
11.Wait patiently.
12.It should boot up now.
P.S. Your bookloader is back to lock. You need to unlock it again.

318cyz said:
Hi there,
I just save my cactus from a “Vibrate massager”.
If you got the same problem,this maybe help you.
First,download three tools;
1.MTK-Bypass
2.SP-Flash-Tool
3.MiFlash Professional Edition(Black logo,need install)(If you got a yellow logo edition and not need install,don't use it. It's public edition.)
My internet environment doesn't allow me to access a lot of websites(.etc Google,Youtube,Facebook,Twitter...),so try to google/bing it and download it.
If you got all needed tools,charge your “Vibrate massager”,and...
Here we go!
1.plug your cactus to pc.
2.open Miflash Professional.
3.select SP flash.
4.click "Options".
5.Go to "general".
6.Make sure all three options is "false" now.
7.select appropriate files for DA and scatter BUT WITHOUT "AUTH".
8.hold Volume+ and power,until your computer make response for it.
9.<--DO THIS IN 5 SECONDS-->
(1)Open MTK-bypass IMMEDITELY.
(2)Select MT6765(even cactus is 6762,but select 6765 anyway) IMMEDITELY.
(3)Click Bypass IMMEDITELY.
<--YOU CAN TAKE A BREATH NOW.-->
10.When bypass is complete,back to SP-Flash, and then click flash.
11.Wait patiently.
12.It should boot up now.
P.S. Your bookloader is back to lock. You need to unlock it again.
Click to expand...
Click to collapse
is it working? Please reply

its possible to do that in 5 seconds if your laptop is not sluggish. im crying got my single core laptop.

ligodligerem said:
is it working? Please reply
Click to expand...
Click to collapse
Yes it's work.
I tried this for three times and all of them are success.

318cyz said:
Yes it's work.
I tried this for three times and all of them are success.
Click to expand...
Click to collapse
Yes 100% , if the issues are the same as posted above.

ligodligerem said:
its possible to do that in 5 seconds if your laptop is not sluggish. im crying got my single core laptop.
Click to expand...
Click to collapse
By the way, you can open MTK-Bypass and press bypass button earlier and it will wait for COM usb port.
When you entered the usb port mode it will pypass it immeditely and you can flash it.
I forgot to write it when I post this thread

Possible reasons to cause this problem:
1. Flashed wrong recovery.
2. Flashed wrong boot/kernel.
3. Wipe logo partition.

How To Guide Improve Battery Life and reduce heat

Battery life on 12 Pro is probably one of the worst I have experienced. My phone is literally sucking battery life to a level I have not seen on any phone. Light usage, FB, Insta, emails, etc and Im down 40% in like 2 hours.
I did all sorts of resets, firmware updates, etc ( although latest Xiaomi EU has made it even worse in my opinion)
The solution I found, and its working amazing ( my batter life is gone from bad to super good) Same usage, same style and there is basically no drain.
The solution is to under clock the CPU. For the the phone must be rooted for the software to allow underclocking. Apk name is called 3C Cpu Manager
I basically run the CPU at around 60% of its max power. This is totally not noticeable for day to day use unless you use the phone for gaming or heavy CPU progarms.
The Snapdragon is very power hungry, all tasks are made with its using the full power which creates unecessary heat and battery drain. Its a pitty that Xiaomi doesn't have the CPU optimized better like some other phones using the same cpu with better battery life.
See images before and after battery usage and CPU settings for under locking

Hello there
I was wondering would ram management be affected after underclocking the processor? As many apps gets restarted when I do multitasking, like payment page gets refreshed when I switch app and then the payment made fails at device end.
I regret buying this super expensive brick whose ram sucks at just basic apps like chrome and gpay.
Kindly guide, as I want to improve battery life as well

It would have been more interesting to post 2 identical diagrams, ie without battery charge.
Wi-Fi is more energy intensive than data.

Is that true? Making connection to cell towers can't be more energy efficient than a close by router not can it? Especiallywhen in the move the reconnecting with and the searching for the network drains more energy I believe
NOSS8 said:
It would have been more interesting to post 2 identical diagrams, ie without battery charge.
Wi-Fi is more energy intensive than data.
Click to expand...
Click to collapse

Danacy said:
Is that true? Making connection to cell towers can't be more energy efficient than a close by router not can it? Especiallywhen in the move the reconnecting with and the searching for the network drains more energy I believe
Click to expand...
Click to collapse
Especially for streaming and downloads.
https://www.scienceabc.com/innovation/does-mobile-battery-drain-faster-on-mobile-data-or-wi-fi.html

NOSS8 said:
Especially for streaming and downloads.
https://www.scienceabc.com/innovation/does-mobile-battery-drain-faster-on-mobile-data-or-wi-fi.html
Click to expand...
Click to collapse
Interesting, tnx for sharing

Hi. What method did you use to root the phone?
I searched online but couldn't do it. I really want to increase my battery life. Yesterday I had only 4:40 hrs SoT with only social apps and web browsing.

[email protected] said:
Hi. What method did you use to root the phone?
I searched online but couldn't do it. I really want to increase my battery life. Yesterday I had only 4:40 hrs SoT with only social apps and web browsing.
Click to expand...
Click to collapse
I tried 3C Cpu Manager and saw no real improvement.
May be a little early to tell but with the latest Xiaomi EU rom A13, it displays 10 hours more at 100% which becomes 6 hours in the end.
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.

NOSS8 said:
I tried 3C Cpu Manager and saw no real improvement.
May be a little early to tell but with the latest Xiaomi EU rom A13, it displays 10 hours more at 100% which becomes 6 hours in the end.
Root:
1. Find or redownload the TGZ file for your current ROM
2. Browse inside the zip file and find boot.img under the images folder
3. Copy this file to a temporary location in your PC first, and then transfer it to your phone
4. Install the desired version of Magisk app (V23?)
5. Run the app and choose Install under Magisk
6. Choose Select and Patch a File, then select the boot.img that was transferred earlier
7. A process will run and create a new .img file in the same folder where the original one was
8. Transfer the new file to your PC in the same directory where fastboot.exe is located
9. Open a command prompt window in that same directory
10. Reboot your phone to fastboot mode and connect to PC, USB2.0 port. Check for connection by running command fastboot devices.
11. Run the command fastboot flash boot_ab magiskXXXX.img
Once it's completed, run command fastboot reboot and the phone should boot and be rooted.
Click to expand...
Click to collapse
Hi. Thanks for the reply.
How was your battery life before compared to the 6 hrs you have now with xiaomi.eu A13??

[email protected] said:
Hi. Thanks for the reply.
How was your battery life before compared to the 6 hrs you have now with xiaomi.eu A13??
Click to expand...
Click to collapse
24 hours, I did a full charge this morning and I will post to let you know whether or not there is really an improvement after 48 hours.

NOSS8 said:
24 hours, I did a full charge this morning and I will post to let you know whether or not there is really an improvement after 48 hours.
Click to expand...
Click to collapse
Great. I will be waiting for your feedback.

Hey. This module is all you need: https://forum.xda-developers.com/t/...ife-more-than-sufficient-performance.4450435/
Try it now and you will feel the effect immediately. No more heat. No battery draining. It's perfect.

I confirm the battery life is improved with A13.

vietbt said:
Hey. This module is all you need: https://forum.xda-developers.com/t/...ife-more-than-sufficient-performance.4450435/
Try it now and you will feel the effect immediately. No more heat. No battery draining. It's perfect.
View attachment 5786745
Click to expand...
Click to collapse
Thank you for the suggestion. I will give it a try

NOSS8 said:
I confirm the battery life is improved with A13.
Click to expand...
Click to collapse
Thanks for the confirmation. I will give it a try later as my phone is rotted.
I prefer to have xiaomi.eu

vietbt said:
Hey. This module is all you need: https://forum.xda-developers.com/t/...ife-more-than-sufficient-performance.4450435/
Try it now and you will feel the effect immediately. No more heat. No battery draining. It's perfect.
View attachment 5786745
Click to expand...
Click to collapse
Which zip you prefer to flash for our Xiaomi 12 Pro 8Gen1 ?

lontu said:
Which zip you prefer to flash for our Xiaomi 12 Pro 8Gen1 ?
Click to expand...
Click to collapse
I recommend the Kirin 980 and SD778G modules.

vietbt said:
I recommend the Kirin 980 and SD778G modules.
Click to expand...
Click to collapse
Are you sure it works for an 8Gen1 when it seems to be more intended for the Snapdragon 888?

vietbt said:
I recommend the Kirin 980 and SD778G modules.
Click to expand...
Click to collapse
this feels like a bad idea try at your own risk,

trinadhchinna7 said:
this feels like a bad idea try at your own risk,
Click to expand...
Click to collapse
Yep, none of these mods is made for the 8Gen 1.