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

[Q] Evo Shift Bricked Real Good? Stuck on HTC logo screen.

My first post here so go easy on me
Anyway, I got an Evo Shift, I do not know its history, but its stuck in some sort of a boot loop, on the white screen with green HTC logo.
Things I know:
****UNLOCKED****
SPEEDY XE SHIP S-ON
HBOOT -0.99.0001
RADIO - 1.08.01.0111
Clockwork Recovery v5.0.2.0
I did not get an SD card with it, no recovery image.
RUU says version is 2.77.651.3
I know the S-on is a problem.
I have tried all 4 of the RUU versions - failed.
Tried RUU with Gold Card - failed.
Tried rom.zip from each RUU renamed to PG06IMG.zip - failed.
I have tried custom roms of all sorts, every methoud I found - failed.
Where do I go from here? Is there a way of manually flashing all the partitions from a ROM.zip file via fastboot? Is there a way of disabling a version check in RUU? Or is there a way of disabling MD5 sum in Clockwork so I can try flashing a restore image from another Shift?
I have spent 3 days on this phone, and I would hate to admit defeat, so I am reaching out to the genius minds here. Thanks in advance!

Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.

gzetski said:
Okay, I fixed it. Please delete the thread. Unless someone wants me to do a write up on how I did it in case someone else fubars their phone.
Click to expand...
Click to collapse
Did you unlock the bootloader with htcdev tool?

The bootloader was already unlocked when I got the phone.

Thanks for this. I will test it and add it to my guide.

VICODAN said:
Thanks for this. I will test it and add it to my guide.
Click to expand...
Click to collapse
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Place misc.img and PG06IMG.zip on sdcard using windows explorer or "adb push /sdcard/file.xxx" via usb
Click to expand...
Click to collapse
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!

And BTW, I am now rooted, but with S-ON... Grrr. Superuser works, rom manager works, pretty much anything requiring root access works. I have rebooted the thing like 20 times to see if it goes away, and its sticking just fine, but I am afraid of trying to flash a custom rom with the S-ON.
All attempts to flash ENG bootloader fail, both by flashing via fastboot (all my MD5 sums match, the process is flawless from start to finish, when I reboot, still same bootloader with S-ON), or using ShiftRR.
Any ideas?

gzetski said:
You're welcome... I figured I'd just go hard since it was bricked already.
Speaking of guides though, can I get a bit of clarification on something?
http://forum.xda-developers.com/showthread.php?t=1357157
2.3.4 step 15,
Where is the MISC.IMG coming from, and what is ( rom? which one? etc.)in the PG06IMG.zip?
Thanks!
Click to expand...
Click to collapse
shift-rootkit.rar
Read the prereqs.

Okay, got it.
Too many things floating through the intertubes with similar filenames.

gzetski said:
Okay, got it.
Too many things floating through the intertubes with similar filenames.
Click to expand...
Click to collapse
Yep, I've finally got the thread pinned, and I created 2 videos on how to do it the right way. They are uploading to youtube now.

S-off?
Did you ever figure out how to get S-Off? I seem to be right where you were a few days ago with the phone appearing to have root, but S-on still there. I'm also running HBOOT -0.99.0001 and unlocked via the HTC Dev tool. Is there anyway to downgrade to .93 or to turn S-Off. My ultimate goal is to get Cyanogenmod on this Shift.
Thanks in advance!

I have not messed with the phone for a few days. I am gonna try to go back to 2.3.4 then downgrade again. Most likely what I ended up having is a bunch of borked files, hopefully the latest RUU will fix that. This was really intended as a brick fix and not a legitimate 2.2 downgrade. When I mess with it, I will post the results for you though.

Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.

MTsol said:
Omg thank you! I accidentally bricked one of my evo shifts and spent 3 hours trying to figure out how to fix it. I'm so glad I ran into this thread. Worked like a charm for me.
Click to expand...
Click to collapse
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2

drob311 said:
Its not a brick if you can fix it... Bricked phones are permanent paperweights, nothing more, nothing less...
Sent from my PG06100 using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Yes Sir . Been there done that. Had a HERO that somehow got " water damaged " after it was BRICKED .

signature verify fail
gzetski said:
Okay, I fixed it. did a write up on how I did it in case someone else fubars their phone.
Things you will need:
Android SDK
HTC Drivers
7-zip
RUU_Speedy_Sprint_WWE_1.17.651.1_Radio_1.07.00.112 9_NV_SPCS_1.52_1103_release_160079_signed.exe
On your computer, search for ROM.ZIP. Include system locations and hidden files.
Delete any instances of it that you may find.
Take the SD card out of the phone.
Put your Shift into fastboot (vol/down + power)
Run the RUU, let it get stuck.
On your computer, run a search for ROM.ZIP while the RUU is running. Its gonna show up in some temp folder.
Copy it to your desktop.
Use 7zip to extract it (for whatever reasons Windows can't extract it).
Open the extracted rom.zip folder.
Copy all files and place them in your SDKs platform tools folder.
Shut down the RUU, reboot the phone into recovery (vol/down + power).
Run CMD and change directories to your platform tools folder.
Type the command "fastboot flash recovery recovery.img" (without the quotes) - this gets rid of any custom recovery like Clockwork, etc.
Reboot the phone into recovery again, you should have a triangle with an ! next to it on black background.
Go back to CMD and your platform tools, and start flashing the following:
fastboot flash boot boot.img
fastboot flash dzdata dzdata.img
fastboot flash partition partition.img
fastboot flash radio radio.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Reboot the phone.
After 30 seconds of white HTC screen, your phone should boot up fine and you will be in Android 2.2.
Let me know if it worked out for you, I just fixed mine less than an hour before writing this up.
Also, if anyone out there sees anything redundant, or can help me clean this process up a bit, I welcome your input.
Click to expand...
Click to collapse
First, I want to thank you for posting this even though it hasn't yet worked for me. I'm in essentially the same position you started in. Phone will not boot past the green-on-white HTC logo. I boot to recovery and can get to fastboot mode with USB detected. I flashed recovery.img and boot.img with no problems, but trying to flash dzdata onwards gives me the same error every time: "(bootloader) signature checking... FAILED (remote: signature verify fail)" and will not flash the other components from ROM.ZIP.
Any thoughts on how to proceed? This thing is rapidly approaching permanent brick status.

You need to unlock your bootloader and then flash the rom. zip files through fastboot
The "failed" message means that your bootloader is locked

to get S-off the easiest method is to downgrade your device from 2.3.4 to 2.2 and then FOLLOW THE SAME INSTRUCTIONS AS OBTAINING S-OFF ON 2.3.4. i had the same issue when i first unlocked my Shift bootloader.

[Q] Rooted etc., then flashed RUU, now unable to install recovery or run su!

This is my saga thus far:
1. Followed the guide ... more or less. For some reason it wouldn't install CWM as PG58IMG.zip via fastboot automatically (it detected it, said it was parsing, then just went back to the menu), but I was able to install the img using fastboot flash recovery recovery.img (where recovery.img was the CWM img). Anyway, everything worked properly, I had the SuperUser app, I could use 'su' in the terminal, etc.
2. I flashed 4EXT Recovery. Also worked perfectly.
3. Played around a bit, whatever.
4. Did a backup via 4EXT.
5. I bought this phone used from eBay, so I wanted to ensure there was nothing malicious hiding in the system partition. So I used RUU_Pyramid_BM_1.45.666.5_Radio_10.56.9035.00U_10.14.9035.01_M_release_220007_signed.exe, which is precisely what was installed before. That was successful too.
6. Then, when I set things up, Google started "recovering" my apps, i.e., downloading a bunch of apps I had on my old phone. I was not impressed by this. So I went to Settings > Storage > Factory Reset.
7. Then I reinstalled the RUU. I'm not sure if it was necessary or not.
Now I seem to be stuck. I'm not bricked -- I can do everything an unrooted user can do. But I'm pretty sure I'm NOT rooted. The Superuser app's gone, and when I type su in the terminal, it says "permission denied" (which is interesting, shouldn't it say it can't find it at all?). In the bootloader/fastboot, it says S-OFF. It also says **LOCKED** above that. I'm not sure whether that refers to system access (i.e., root permissions) or the SIM (phone was unlocked before). But the strangest part is with ADB. When the phone is on in normal mode, I can install apps, push/pull, etc. But within the bootloader, adb's not recognizing the device at all! What's particularly weird is that the fastboot command IS recognizing it! And when I do fastboot getvar cid, it's still 11111111. But it won't let me flash a custom recovery.
So, I seem to be stuck. It seems to be S-OFF, but I can't flash a recovery. I can't even restore my backup, since I need the custom recovery to do that!
Any ideas as to what I can do to re-root my phone?
EDIT: I'm watching a YouTube vid of the phone being S-OFF'd. When he started off, his bootloader screen looked identical to mine except it said S-ON. When he finished, it said S-OFF, but it also said **Revolutionary** instead of **LOCKED**. OK, so, if I try running Revolutionary again, will it fix things, or will it do nothing or even brick my phone? Will I have to do the S-ON procedure and then start anew?

You have s-off with a locked 1.27 hboot. That's ok, at least you have s-off so you have access. Don't worry about the "locked" bootloader! adb will not connect in bootloader. That is normal. You must use fastboot when in bootloader. As far as a recovery goes, you'll need a PG58IMG with the correct mid in order for it to flash. From bootloader:
Code:
fastboot getvar mid
You can use 7zip to extract the PG58IMG and notepad++ to view the android-info.txt. Make sure your mid is listed... If it's not listed then you can add it, pack it all back up, put on root of sd and flash through bootloader.
Once you have your recovery you will have to flash superuser to regain root access.

I had this exact issue the other day on a gingerbread RUU, to fix it I ran revolutionary even though I was s off already, then rebooted the phone, and flashed this recovery from bootloader
http://db.tt/CElPBgty
This is the only one I managed to get to work, others just said 'parsing' then did nothing
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

[HOW-TO] Unbrick Your Android Phone (HTC ONE S)

(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up or go to recovery… well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, have found a way to unbrick your device! after bricking my phone and finding different ways how to do it...
Because we are not able to swap or get the sdcard out from the phone, it makes it difficult on how to add a ROM.zip and re-install. Another issue I found is that CWM will not be able to read the sdcard if you do an adb push ROM.zip /sdcard/ROM.zip or by mounting the sdcard adb shell mount /sdcard . If you have this issue will explain later
So let's get started.
Step 1: Turning Off Your Phone and Reboot to Boot-Loader
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to turn off by pressing the volume down + power button until the phone shuts off then turn on to boot-loader by pressing volume down and press for 3 seconds the power button. once in boot-loader select fastboot.
Step 2: Adb push to SD card
I assume that you have install CWM, if you don't you can download it from HERE. Once downloaded install CWM fastboot flash recovery CWM.TOUCH.5.8.3.1.img, where your done go back to boot-loader and select recovery. Once in recovery do an adb push of a ROM, in this example I used "Energy ROM" you can get the ROM from HERE. Once you have your ROM rename ROM.zip and push adb push ROM.zip /sdcard/ROM.zip, you will get a message stating the size of the the push.
If you can't do a push because you got an error message will explain later.
Step 3: Wipe The Phone
Make sure to do a Factory Reset / Wipe before installing ROM
Step 4: Reboot back to fastboot
Once you install the room you will need to make sure you have a boot.img for the ROM your using.
adb reboot bootloader
fastboot flash boot Recoveries/boot.img
YOUR DONE
If your the unlucky one's that can't do an adb push to the SD card do the following.
- Reinstall STOCK Recovery fastboot flash recovery recovery.img
- Lock OEM fastboot oem lock
- Unlock OEM fastboot flash unlocktoken Unlock/Unlock_code.bin
- Reinstall CWM Recovery fastboot flash recovery CWM.TOUCH.5.8.3.1.img
That should fix the problem on how to push back to the sdcard
If you have other methods post them below...

Sticky!!

But this won't work if you flash a wrong radio, will it? I thought that if you flashed a wrong radio, you couldn't get anything done, even not booting into bootloader, because it boots the radio first?

I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..

This tutorial already exists as a sticky in the Q&A section:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC VLE_U using Tapatalk 2

Nice writeup.
For every new Phone I own, the first thing I do after flashing a Custom Recovery is Making a Nandroid Backup of the stock Rom. If something goes wrong after flashing a bad rom I just restore to Stock rom.
A real life Saver for me.

snwman said:
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
Click to expand...
Click to collapse
It worked for me when I bricked my phone and had to find ways how to be able to load a ROM back to the SDcard and reflash it...

This is a combo of a tutorial cannondale wrote and one I wrote myself.
His is stickied in Q&A section, mine is in Android Dev section...
Not sure why this is here lol.

i get the error 155 when trying to install the RUU

420haxr said:
i get the error 155 when trying to install the RUU
Click to expand...
Click to collapse
Try to relock your bootloader first.
In fastboot:
fastboot oem lock
Sent from my HTC One S

Issue
Ok, still running into an issue. No errors when I push, I locked, unlocked, tried everything again. Reset everything, installed fresh CWM, tried it all over...
What's happening is that it's saying it pushed the file over, but I can't find it anywhere after it's done. This happened the first time I installed custom...I just can't remember what I did to get it to work...

Anyone has the link of stock recovery for HTC One S z560e(ville c2)?? i get error 155 when i try to install with RUU.

After i flash the cwm touch recovery I cant boot into recovery... my phone is stuck on the HTC boot logo with the red text underneath. Is it a problem with recovery or should i try install an RUU. My phone is HTC One S villec2 (S3).

[Q] Phone can't boot after kernel flash

Hello,
So I have a rooted HTC Desire S with Hboot 2.00.0002, unlocked bootloader and 4ext touch recovery. After a couple of failed attempts of flashing the MIUI rom and nandroid restoring it, I lost the ability to connect to 3G after the fourth attempt. So, I tried to flash a new kernel on it to see if it would solve anything. It didn't, whenever I boot up my phone it hangs on the HTC logo, then reboots a little while in 4ext recovery mode.
From here I again tried to nandroid restore, but with no luck.
How do I get my phone back to working? (what I had before was rooted stock rom)
I have tried these two kernels: http://bit.ly/ozxbWr (HTC-Kernel-2.6.35.10) and the Reaper 3.0 kernel (http://forum.xda-developers.com/showthread.php?t=1433816).
Thanks.

Alright, found the problem. For future Googlers here is how I fixed it.
So, first I downloaded a custom rom for my phone, MIUI. I placed the zip on my micro-SD card (I have a converter so it will fit into my laptop) and booted into 4EXT recovery. I guess you can use ClockworkMod Recorvery aswell.
In here I picked "choose from SD-card" and picked my .zip file and installed it.
After installation you boot into the bootloader (Volume Down + Power button) and go into fastboot. While in fastboot you plugin your USB-cable.
Set up ADB and Fastboot with this guide http://forum.xda-developers.com/showthread.php?t=1272595
Now go back to where you downloaded the custom rom to and extract the boot.img file to the folder where adb.exe and fastboot.exe is.
Upon up a cmd in your folder where adb.exe and fastboot.exe is in (Use Shift+Right click, pick "Open cmd here").
Now write exactly the following
Code:
fastboot flash boot boot.img
.
Press Enter and let it do it's job. When it's done you can unplug the USB cable and restart the phone as normally. The phone will now function again.

Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.

SimonTS said:
Did you unlock your phone with HTCDEV? If so then it is extremely well documented that you have to flash to kernel separately.
Click to expand...
Click to collapse
And even more so now
Impressed that someone actually resolved their own issue, let this hopefully be a lesson to the crowd
Swyped from my DesireS

The guide for doing this is here: http://forum.xda-developers.com/showthread.php?t=1525100

Thread closed