Database Info

[Q] Can't access root and Google apps

I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.

SounderBruce said:
I recently rooted my phone (T-Mobile US Nexus S) and installed the 4.0.3 OTA update from this thread, but now I cannot access any Google apps or get root access on any of the apps that require it.
Click to expand...
Click to collapse
Ok! first download : http://www.4shared.com/zip/XG506hyV/icsroot-fastboot-recovey.html
just unpack, connect your device and click run.bat.....Good luck!

I ran the .bat, but I get an error saying "Device already rooted", but it is still not recognized as rooted by SuperUser.
Alternatively, is it possible to completely wipe the phone of everything (including root) so I can start over with a fresh phone?

Of course you can, and might be the best idea if you don't mind doing it.
Make sure you have the latest CWM recovery on your phone, download the FULL ROM from this thread (i'm not american so i don't know exactly, but from what i know yours is the I9020T, so get that ROM) and copy it to the SDCard. Now go into recovery, wipe system/data and dalvik cache, then flash the ROM.
Do make sure you have the right ROM though. This will get you 100% fresh and untouched 4.0.3. You can probably clear out any non-personal folders on the sdcard too, but that shouldn't do any harm anyway.
After this, use the attached file from this thread to root, and feel free to update root/superuser.

Actually, that's what I did...I can't use CWM recovery because its displaying an error of no root. So how do I wipe this or fix CWM?

Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.

Harbb said:
Is your boot loader unlocked? And are you trying to flash cwm through fastboot?
Note to backup your sdcard if unlocking the bootloader.
Click to expand...
Click to collapse
My bootloader is apparently unlocked and I'm trying to flash through fastboot.

Are you sure the following is satisfied:
-open padlock and google logo on boot
-fastboot (on phone) says "bootloader status: unlocked" or something of the like
-you are using: "fastboot flash recovery "C:\path\to\recovery.img""
-you are using the above command while connected to the PC via USB (with working drivers) and that you are in fastboot mode on the phone (turn off phone --> hold Vol. Up then hold Power TOGETHER for about 2 seconds, should give you reboot and recovery options)
It is necessary to be in the bootloader/fastboot interface on the phone when you run the command. Hopefully it was something simple that i said above, otherwise i'm completely lost.

1. Yes
2. Yes
3. I didn't use that method to root...
4. I'll try that.

3 is just flashing recovery, that is the code u type into cmd/terminal to reflash the recovery img. It isn't rooting the phone. 4 is how to get into the mode on the phone to use the command.
Its a bit confusing at first but makes much more sense once you do it one or two times.

Where do I go to get the recovery image?

The latest ClockWorkMod Recovery can be found on this page. Just scroll down to Nexus S and download 5.0.2.0 crespo .img. Then just direct fastboot to the folder you have it saved in while using the "fastboot flash recovery C:\path\to\recovery.img" command.

Ok. I've tried this, but in command prompt, I get the following error:
C:\Users\Bruce>fastboot flash recovery C:\Users\Bruce\Downloads\recovery.img
'fastboot' is not recognized as an internal or external command,
operable program or batch file.

Check out this rooting guide, however only go up to step 5 (and do NOT type "fastboot oem unlock", do everything up until that point). This will setup fastboot for you, and setup drivers for your computer. Once this is done, do what you did above and it should work successfully.
Remember to cd (change directory) in cmd to where you unzipped that folder.

There isn't a link...

Sorry, stuffed that up. I fixed the link in my previous post pointing to NexusSHacks - How to Root Nexus S.

It's worked, but when I try to go to the recovery menu, the Google/unlocked padlock screen freezes or it displays an Android with its chest compartment open and a red triangular ! symbol.

I just had a really long reply and managed to lose it by closing the page..
That's the stock bootloader you see there, it probably didnt flash or you rebooted your phone. And make sure that you are flashing the latest CWM you downloaded before.

I flashed the latest CWM, but when I try to go to recovery, my phone freezes at the Google logo with the unlocked padlock.

Have you tried flashing it again, or maybe redownloading the file? And of course making sure it is the NEXUS S version which you are downloading.
Alternatively, try just "fastboot boot recovery.img", replacing recovery.img with the full name and path of cwm.
edit: btw, i'll be gone for an hour or two Bruce so i can answer any more questions/issues when i get back

I can't install clockworkmod recovery on nexus s 4g

I rooted my NS4G running stock ics but I get an error when try to flash cwm recovery using ROM Manager. Any advise, I need help please.thanks
Galaxy Note

I'm assuming you unlocked via fastboot? You might be better off flashing the recovery image through there instead. You'll have better luck that way:
Snag the recovery image from here
Make sure the file is in the same location as adb. Turn your phone off and then power it on to the bootloader screen (pwr + vol up). Once there, open your command prompt, attach the phone via USB, and type fastboot devices to make sure your phone is recognized. Once you're okay there, proceed to type
fastboot flash recovery recovery-clockwork-5.0.2.0-crespo4g.img, this is assuming you haven't changed the name of the image. You can copy it and paste it as well.
Once you get the recovery image flashed, you'll need to ensure that the stock recovery doesn't replace CWM. Steps can be found in
This post
HTH

Bootloop (S-ON/No Recovery) :(

Hello,
I have a big problem with my old HTC Sensation.
I tried nearly everything out of other topics, but nothing worked....
The story: Suddenly my Sensation rebooted and from then on it is stuck in an endless bootloop.
The bad thing is, that it was stock/S-ON at this moment.
Informations about the phone:
***UNLOCKED***
Pyramid PVT Ship S-ON RL
HBOOT: 1.27.0000
Radio: 11.24A.3504.31_M
-> I am able to install RUUs (3.33), but after installation i am still in the bootloop
-> I am able to unlock/relock the bootloader
-> I can install a recovery via fastboot, but can't boot into it => bootloop
Maybe you have got a hint to bring the Sensation back to life.
Thank you!

Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!

kevinspl2000 said:
Since your bootloader is unlocked, you can use fastboot to do stuff. Most of the HTC Sensations have a HBOOT version that causes bootloops when flashing roms because their kernel doesn't seem to install properly when flashing roms. The ROM should consist of a file inside the zip, usualy in the kernel folder or in the root of the zip that is called boot.img. That is the kernel. First of all, you need to download the tools that have the fastboot and drivers included. Then unzip all of the contents into a folder. Run and install the drivers that that have come in the folder. Then go into the fastboot and adb folder. Shift rightclick onto the empty space of the folder and click open command window here. Then boot your phone into bootloader mode. You can do this using power button and volume down while your phone is off. Once youre in fastboot mode, navigate to fastboot using up and down volume keys. Then press the power button. Plug in your phone to your computer using your HTC sync cable. Then in the adb and fastboot folder, copy your roms boot.img into the folder. Then in the command window, type 'fastboot flash boot boot.img' without the quotation marks. It should say sending and then writing. The process should take no longer than 20 seconds. Once done, restart your phone. Wolla, your rom should now be working properly!
Click to expand...
Click to collapse
actually he can't even boot to the recovery in order to flash any rom
so what's the point of flashing the boot.img manually?

You can use Sensation all in one kit v3 to unlock boot loader, read this thread for more detail
http://forum.xda-developers.com/showthread.php?t=1497404
after unlocking boot loader, then go to this thread to download 4EXT recovery then use kit to flash recovery, remember to download image file, not zip file
http://forum.xda-developers.com/showthread.php?t=1377759
boot to recovery, then enable smart flash and flash any cook ROM you want. Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck

stripeqn said:
Remenber to wipe everything after having enable smart flash then flash cook ROM
good luck
Click to expand...
Click to collapse
actually first has to wipe and then enable smartflash

Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again

BrainyTheKing said:
Thank you for your ideas!
But unfortunattly i tried most of the things.
@ kevinspl2000
I think normaly the RUU would also install the Boot Image.
But I also tried to manualy flash the boot.img out of the RUU via fastboot, but no success.
I am not able to flash a Custom ROM, because of no Recovery...
@stripeqn
The point is that I am not able to boot to Recovery...
I can flash the Recovery via fastboot, but I am not able to boot into it.
I tried different versions of CWMR and 4EXT but no success...
When I click on recovery, it just shows the HTC Logo and bootloop again
Click to expand...
Click to collapse
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...

kevinspl2000 said:
I think I have a solution. When I installed my custom recovery at first, I also got bootloops when trying to go into the recovery. What I did, is I refalshed the recovery, and then did fastboot erase cache. It wipes all of the cache, and fixed my bootloop before. Try that and see how we get on...
Click to expand...
Click to collapse
I erased the cache before and after flashing recovery.
No success ...

Booting only takes me to TWRP

So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.

Can you load a rom to the internal memory or on the SD card and then flash and install a new rom?

Same Here
droidmark said:
So, I went through the temp root/S-off routine with WeakSauce and Firewater. Then flashed TWRP over adb. Rebooted to TWRP which asked if I wanted to install SuperSU. I said yes. Rebooted again and came back up in TWRP. Cannot boot to system. Rebooting always takes me back to recovery. Help would be much appreciated!
Oh, and I can also boot to the bootloader, if that helps.
Click to expand...
Click to collapse
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.

I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk

edited to fix all my auto-correct typing mistakes.
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Click to expand...
Click to collapse
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...

cntryby429 said:
edited to fix all my auto-correct typing mistakes.
My understanding is that there's two ways of getting into a custom recovery in adb:
1: "fastboot flash recovery nameofrecovery.img" this will flash over the previous recovery whatever that was. It will stick and you get into the new recovery either through hboot or a ROM's advanced power menu.
2: "fastboot boot nameofrecovery.img" this will boot into the recovery temporarily and allow you flash things. Once you reboot from that temp recovery it will boot using whatever kernel (or other .img file in this case) you have flashed into the boot partition.
The syntax for flashing is "fastboot flash <partition> <name-of-file-to-flash-to-that-partition>"
The syntax for booting an image is "fastboot boot <name-of-the-file-to-boot>"
It sounds like you mixed those 2 together and typed " fastboot flash boot nameofrecovery.img" so when you go to boot your phone now the only thing your phone sees to boot is the recovery. That's why your solution is twofold.
1: Flash the kernel to the boot partition: "fastboot flash boot nameofkernel.img" (sometimes these are just named "boot.img"). This will load the Kernel, modules, and ROM so that your phone will boot properly.
2: flash the recovery to the recovery partition: "fastboot flash recovery nameofrecovery.img" This will permanently install your custom recovery so that you can go back into it next time you want to flash ROMs, make/restore backups, etc.
You should be good to go and will likely never make THAT mistake again. Ask me how I know...
Click to expand...
Click to collapse
I didn't use fastboot load TWRP, I used the adb method shown on TeamWin's project page for the Verizon M8:
***********
Download - ADB / Terminal method:
Download the newest .img file from here
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
***********
Thanks all for the other suggestions which I am about to attempt!

I had this happen to me on my Asus EeePad TF101. It seems that TWRP has a bug that prevents it from setting a "boot to system" flag on some devices, causing it to always boot to recovery.
The solution for the TF101 was to reinstall the stock boot image, which appears to align with the instructions already given. Good luck! I know the terrible feeling I had when this happened to my tablet...

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
Whew! Thanks!!
Not only did that save my bacon, it had the added benefit of getting me the insecure kernel which I had forgotten about since going through the whole root/S-off/unlock bootloader/insecure kernel routine with my Droid DNA quite a while back.

Zallantor said:
Hey man the same thing happened to me last night, i thought i bricked my phone. I personally dont think the adb method of getting twrp onto the phone is working right now. If someone knows what we are doing wrong plz let us know.
Here is how i fixed it:
1. Put phone into bootloader, put it on fastboot, plug it into computer. You will see it change to "fastboot usb"
2. Download and do this http://forum.xda-developers.com/showthread.php?t=2708686 . To do this go back to your console (terminal or cmd), navigate back to the folder with adb in it, and instead of running the adb commands just type in " fastboot flash boot M8VZWbootInsecure.img ". its easiest to put that boot img in the same folder as adb and fastboot. once that is done you just need to reboot the phone and you are golden.
3. Problem is, when you do this you can no longer get back to your recovery, you get a screen with a red triangle and exclamation mark. I thought I bricked my phone lol.
4. Doing a alternate soft reset will get the phone back to normal android ( hold down power and volume up for 10 secs)
5. to fix it complete use the flashboot method of copying over the recovery onto the phone as shown here http://teamw.in/project/twrp2/226 . This is essentially the same method as in step 2 its just copying over the twrp.img into the recovery section of the phone.
By doing this I was able to get TWRP to work and be able to boot normally to system. Hope this helps.
Click to expand...
Click to collapse
I was soft bricked and only able to boot into bootloader and recovery and this write up worked for me. Just wanted to say thanks.

Don't use adv/terminal way. It's writing recovery to wrong partition..
Sent from my HTC6525LVW using XDA Premium 4 mobile app

The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.

hanginwithdaddo said:
The fastboot command to flash your recovery is:
fastboot flash recovery recovery.img
where "recovery.img" is the name of your recovery.img file on your host computer. Don't use "fastboot flash boot recovery.img", as I believe this will flash your boot partition, not the recovery partition.
Click to expand...
Click to collapse
if you flash to anything but the recovery partition your in some trouble.
same goes for anything like this, make sure you know what that .img is and you trust it. someone could have renamed an hboot to recovery and you end up flashing an hboot to your recovery partition because someone was careless with naming of files.

So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?

tim.ton said:
So I need help... I'm stuck in a bootloader loop. And every time I try to do this fix, terminal keeps telling me this:
error: cannot open 'M8VZWbootInsecure.img'
Any ideas?
Click to expand...
Click to collapse
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
The Stig 04 said:
I think the command you run has something to do with it. "Fastboot flash boot nameofrecovery.img"
Almost certain the command has to be "fastboot flash nameofrecovery.img"
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
additionally, since you can boot into TWRP, have you tried sideloading a rom?
(in TWRP, go to ADVANCED, click SIDELOAD... i think you need to swipe to activate... then from terminal: adb sideload nameofROM.zip)

RBThompsonV said:
are you on a mac? reboot...
---------- Post added at 08:36 AM ---------- Previous post was at 08:32 AM ----------
This is incorrect.
command is:
fastboot flash recovery nameofrecovery.img
Click to expand...
Click to collapse
Oh yeah! Lol I knew it was something like that. Thanks!
Sent from my HTC6525LVW using Tapatalk

Stuck on Google splash screen after flash of rom.

After about a month of my phone rebooting itself or freezing up on me, I decided to flash a new rom. I made sure I had the most recent TWRP v2.8.7.1, wiped my cache and did a factory wipe. I attempted to flash BlissPop v3.9 and it failed stating, "This package supports booloader (s): HHZ12h; this device has bootloader HHZ11d.
It rebooted and now just sits on the Google splash screen. I can turn it off and manually get into the bootloader screen and TWRP.
How will I be able to download another rom from my computer and put it onto my phone? Please be nice, I really suck at adb. I can I access my phones memory while its in Recovery mode?
And no, I was a dumbass and forgot to back up before I attempted to flash the rom.

abd push (drag desired rom here) /sdcard
After that boot into recovery and flash it. If you can't get to the phone that way then download the factory image from google and fastboot flash, or alternatively download the twrp image and fastboot boot (twrp img) again, just drag the file into the command prompt. If you boot into twrp, or just flash it, you can then push the rom.

Just flash the newer bootloader
Sent from my Nexus 5 using Tapatalk