Database Info

[Solved]

SOLVED!!
Hey guys, i've seemed to set myself up for a soft brick upon me not reading everything clearly and correctly.
I was trying to take an easy route and simply misread a few numbers.
I really need help here, I unlocked my bootloader then proceeded to use a 1 click root solution from here; http://android.modaco.com/topic/327000-08-aug-grj22-colour-revert-superboot-rooting-the-nexus-s/
I just went back to stock after wanting to start clean when I got this phone, anyway I didn't see that this was intended for 2.3 where as my phone was running 2.3.4 and thats where I think I went wrong.
I can access bootloader, after trying this method the phone just boots and hangs at the unlock screen and nothing else. I don't have recovery so I can't get into that, I tried locking and unlocking the bootloader to see if that would help but no luck.
Where do I go from here?
**at&t model

If you can access the bootloader, you're fine. Just install ADB on your computer and flash a custom recovery image. From there, you can flash a ROM.

deejaylobo said:
If you can access the bootloader, you're fine. Just install ADB on your computer and flash a custom recovery image. From there, you can flash a ROM.
Click to expand...
Click to collapse
im trying to push a recovery img from cmd and it's telling me "error: cannot load clockworkXXXXXXXX

I think you may not have entered the full file path when pushing the recovery image.

deejaylobo said:
I think you may not have entered the full file path when pushing the recovery image.
Click to expand...
Click to collapse
I was trying to follow this recent guide here; http://forum.xda-developers.com/showpost.php?p=18257219&postcount=1
the very last part about unlocking the bootloader
and it just keeps giving me that error

Okay, been awhile since I did the whole unlocking bootloader/flashing recovery thing. If I remember correctly, in the command prompt, you should navigate to fastboot which is located in <whatever you named your Android SDK folder>/platform-tools folder. Also, place your recovery image in the same folder. Then enter the command from the tutorial. "fastboot flash recovery <image recovery file name>"

sent you a PM

a huge thanks to deejaylobo for helping me out, a folder wasnt renamed so I had a hard time pushing recovery but he got me back on my feet!
thanks again!!

[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

[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).

Think I messed something up

Not even sure where to start. I've had my One S (TMO) for about 2 weeks now. I immediately followed all the guides to unlock my bootloader, install custom recovery and install custom ROMs. Was running Viper OneS for a while and then switched over to TrickDroid (both 7.0.0 TMOUS and 8.1.0). All of the ROMs seemed to give me some odd issues.
With Viper OneS (after patching my services.jar) I was able to install SManager and run the V6 supercharger script, but after reboot, I was no longer able to get into the ringtone and notification sounds options on the device. When I went to either screen they were just blank and I couldnt choose music from any location on the phone.
With TrickDroid 7.0.0 TMOUS, I was able to patch services.jar and run the supercharger script without any issues at all. However, after a few days of usage, I noticed that calls were no longer forwarding the voicemail number I setup using an MMI code. From there I went to TrickDroid 8.1.0 but even after patching my services.jar, my supercharger settings would not stick after reboot.
Here's where I think something went wrong. I wanted to go back to stock but rooted. Since there were no 2.35 RUUs available for download anywhere, I decided I would download the 1.84 RUU and then get the OTA update. I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems. Unlocked the bootloader and installed TRWP 2.2.2 so that I could flash supersu and root the phone and noticed that the phone was not acting right. From TWRP, its almost impossible to get the phone to reboot. When I choose to reboot, the screen goes blank, flashes once or twice and the notification light keeps turning from orange to green and then back again. I have to hold power down for about 10 seconds, then hold volume and press power to get into bootloader just to turn the phone on.
Decided to try going back to a custom ROM and noticed something else that is strange. I wanted to flash TrickDroid 7.0.0. and during the flashing, it hung on flashing the kernel for like 5 minutes when it usually takes just a second. I then flashed the fusion v2.1 kernel and it hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds. After the flashing was done, I booted up the ROM and when I went into settings, the new kernel was not installed. I flashed it again in recovery and booted back to the ROM and still the stock kernel was showing.
Could I have somehow really screwed up my phone throughout this whole process? Is something corrupted on the NAND that is causing issues with rebooting recovery and flashing things?

[email protected] said:
I relocked by bootloader and ran the 1.84 RUU without any problems. Booted up the phone and got the 2.35 OTA update, again with no problems.
hung on "flashing boot.img" for about 5 minutes as well when it normally just takes a few seconds.
Click to expand...
Click to collapse
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.

dc211 said:
When you did the 2.35 OTA you lost the ability to flash boot.img in recovery. You will need to use fastboot or TWRP's dumlock feature from now on.
Click to expand...
Click to collapse
Thanks for the info! Glad to know I didnt mess anything up .

One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
EDIT: Wow.... i feel really dumb now. All posts I found while searching included the extra "recovery" in the commany. I just ran fastboot boot recovery.img and all is well.

[email protected] said:
One other issue I am noticing is that I cannot boot a recovery image from the bootloader using fastboot. My bootloader is unlocked so I boot up into fastboot mode and run the command "fastboot boot recovery recovery.img" but get an error stating "cannot load recovery". The recovery.img file is the CWM 5.8.3.1 recovery that I have renamed to make typing the command easier. To be sure I was connected, I ran fastboot devices and got back a serial number for my device.
Is this also because of the new hboot that I cannot boot directly to recovery from outside of the device? This is so silly but I really don't want to see the *tampered* message in my bootloader. I thought if I could boot directly into a custom recovery from outside of the device, I could run the RUU once more, unlock the bootloader and gain root without having to flash a custom recovery (which gives me all sorts of issues).
Any additional help would be greatly appreciated. Hboot is 1.14.0004 by the way.
Click to expand...
Click to collapse
.
I doubt that the actual recovery img is named recovery.img. If I am correct that is your problem. You would be trying to boot a recovery img that doesn't exist. It should be:
fastboot boot recovery [name of recovery file].img
Example:
fastboot boot recovery cwm_5.8.3.1_ville_recovery.img or something to that effect (not sure what the actually file name is)

if you are not sure on exact name as behold mentioned, just right click on the file (.img) wherever you have it on pc, check properties, and it will tell you exact name. at that point i just copy and paste it to command window--

Pixel 2 Magisk Bug won't take pin

Pixel 2 XL is soft bricked at the moment and I can't for the life of me think of what I need to do to recover it. I unlocked my bootloader and rooted when I switched to Pie, (I saw people we're already able to use Android pay on a rooted device again and I just couldn't help myself.) I installed twrp accidentally tried to flash TWRP not realizing I needed to temporary boot it and pushing the zip over erasing the recovery I proceeded to just fastboot it and carry on with the normal procedure with my phone. after getting Magisk installed I had my phone all set up until the next time I turned it on and back off again It said I forgot my PIN which I know I didn't I think this was because a glitch with smartlock I just setup so I go to my recovery and wipe the Dalvik cache, cache, Internal storage, and data and low and behold my phone bootloops never making past the final stage before it gets to the lockscreen. I go to Fastboot screen on my phone and my mac can't list my phone as a device in adb and now I am having issues getting back into recovery which I think might be because I am on the stock kernel my Fastboot screen on my phone says Product Name - Taimen, Variant - MSM USF:SAMSUNG(64gig) DDR:SAMSUNG, Bootloader version - TM220j, Baseband version - g899800253-1805232234, my Serial number, Serure boot - Yes, Device status - Unlocked, Vart console - Disabled, HW version - rev_10
I can't get it to stop bootlooping and just turn off.

bump

xda Zed said:
bump
Click to expand...
Click to collapse
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.

robocuff said:
Try flashing the stock boot.img with Fastboot. That might get you out of it. Since you did all the wiping I can't say for sure. However, when you were at the point where it wouldn't take your password, that's all that needed to be done. I ran into the same thing. It's a Magisk bug. Magisk gets flashed to the boot partition so flashing the factory boot.img will fix it. TWRP also gets flashed to the boot partition so if you flashed it too, flashing a factory boot image will get rid of that too. ADB won't see the phone while it's in fastboot mode. You need to use "fastboot devices". You can download a factory image if you don't have one and extract the boot.img from it. Put it in the folder your fastboot is in, and then open a command prompt (terminal? I'm not a MAC person) from that folder and type "fastboot flash boot boot.img" (without the quotes). Make sure you use download the factory image that's the same as what you currently have installed on the phone.
Click to expand...
Click to collapse
I stopped my endless bootloop! Now it says my device is corrupt and cannot be trusted and may not work properly when I tried to start it I couldn't get past the google screen. When I plug it into charge now it doesn't automatically going into a bootloop that can only be stoped by going into the fastboot mode or running out of battery, but the the charging symbol on the screen won't go away. I might have wiped system when I was in TWRP when I couldn't boot back after the first wipe. And I accidentally tried fastbooting Telstra img first. Anyway to get past this white Google screen? Also when I trey to go to recovery now it's the android laying on it's back with a red triangle and it says no command. Should I execute the flash-all script?

Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now

xda Zed said:
Downloaded the stock img files and ran the flash all .sh and now I am back in Android ready to mess something up again I could not thank you enough for your help I am so happy right now
Click to expand...
Click to collapse
Glad to hear you got it working again. As for the recovery screen that say no command, that't the way it works with the stock recovery. When you see that screen, press and hold power and volume up. That will get you into recovery. If you happen to try rooting again and get stuck in a bootloop or some such thing, just flash the stock boot image.. That should get you going again.