Well, okay, technically I'm not actually even totally sure what soft-bricked means, but while I can get to both a fastboot screen and into what appears to be CWM (orange recovery with more options than blue), my phone is hanging on the Google boot screen.
Here's what I did.
I have a rooted Nexus S that was running 2.3.3 stock. The OTA update notification came up today, so I allowed it. But then it seemed to hang for, like, half an hour.
So I pulled the battery and allowed it to reset. Which was fine, no biggie. I still had 2.3.3, but no longer had root. So I flashed the GRI40 superboot. Still fine. But I no longer had an update, and it was still 2.3.3.
So I flashed CWM and went to the 2.3.3 stock image. CWM downloaded said image, didn't seem to have any problems, and I clicked to wipe the cache and dalvik.
And now it won't boot beyond the Google screen. But like I said, I'm on fastboot screen now (unlocked) and seem to still have clockwork. Nothing else, though, and there's nothing on my sd card. I know, I know, the lack of back up is a noob mistake.
Help? I'd really just like to get to stock but rooted 2.3.4.
http://forum.xda-developers.com/showthread.php?t=947950
Use this i have got the same problem
that solved
prad1po said:
http://forum.xda-developers.com/showthread.php?t=947950
Use this i have got the same problem
that solved
Click to expand...
Click to collapse
A couple of the other threads by people with hard bricks (problem today?) mentioned Odin as problematic. It's okay to use?
Also, I have to admit, I see a lot of discussion of Odin in the forums, and have Googled it, but I don't actually know what it is or how to use it.
willentrekin said:
Also, I have to admit, I see a lot of discussion of Odin in the forums, and have Googled it, but I don't actually know what it is or how to use it.
Click to expand...
Click to collapse
Odin is the Fkash program from samsung to flash the lhine first time
you have CWM? no need of odin!
reboot into cwm --> mounts & storage --> mount usb
search a the deoxed 2.3.4 rom and download it..
also search the forum for superuser binary to flash
then wipe system and cache
flash zip first the rom then superuser
reboot
have fun
Okay. Almost there, I think.
You're right about CWM. I got it mounted okay, and get a drive on my computer, into which I can copy a zip and then unmount. At which point I get:
Installing {whichever zip I try. So far, I've tried Nandroid Stock 2.3.4_rooted and 2.3.2 GRH78c}
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That's as far as I get right now. And I'm not touching anything. I wiped the data and cache. Do I have to further mount/unmount anything?
willentrekin said:
Okay. Almost there, I think.
You're right about CWM. I got it mounted okay, and get a drive on my computer, into which I can copy a zip and then unmount. At which point I get:
Installing {whichever zip I try. So far, I've tried Nandroid Stock 2.3.4_rooted and 2.3.2 GRH78c}
Finding update package...
Opening update package...
Installing update...
Installation aborted.
That's as far as I get right now. And I'm not touching anything. I wiped the data and cache. Do I have to further mount/unmount anything?
Click to expand...
Click to collapse
wipe system too? :/
do you have the latest recovery?
maybe you have a nandroid backup anywhere?
else download one at the dev section i think are enough backups
copy one to /clockwork/backup/***DATE***
hope that fixes your problem :S
Sent from my Nexus S using XDA App
willentrekin said:
Well, okay, technically I'm not actually even totally sure what soft-bricked means, but while I can get to both a fastboot screen and into what appears to be CWM (orange recovery with more options than blue), my phone is hanging on the Google boot screen.
Here's what I did.
I have a rooted Nexus S that was running 2.3.3 stock. The OTA update notification came up today, so I allowed it. But then it seemed to hang for, like, half an hour.
So I pulled the battery and allowed it to reset. Which was fine, no biggie. I still had 2.3.3, but no longer had root. So I flashed the GRI40 superboot. Still fine. But I no longer had an update, and it was still 2.3.3.
So I flashed CWM and went to the 2.3.3 stock image. CWM downloaded said image, didn't seem to have any problems, and I clicked to wipe the cache and dalvik.
And now it won't boot beyond the Google screen. But like I said, I'm on fastboot screen now (unlocked) and seem to still have clockwork. Nothing else, though, and there's nothing on my sd card. I know, I know, the lack of back up is a noob mistake.
Help? I'd really just like to get to stock but rooted 2.3.4.
Click to expand...
Click to collapse
Just download the 2.3.4 (stock rooted) file on here...in the de section...
its a nandroid back up
then just put it in the clockworkdmod/ folder on your phone
reboot into recovery and restore it
viola!
thats what i did to get mine rooted...its way easier than trying to actually root it!
edit: yeah what the post above mine said...lol..didnt see that posted yet!
Okay. Followed guidance. Still hanging but maybe getting closer.
I made a backup of the borked system, and then went into the clockwork folder and created a new folder within the backups. I unzipped the 2.3.4root ROM and renamed the folder to almost the same name as the borked system. I then tried to restore that.
I got an MD5 fail? I'm not sure what that means.
Maybe I should replace all the files in the legit-made backup with the files from 2.3.4?
Awesome! I got it! I went and got Axura's 2.3.3 stock/rooted and installed that from the zip. I don't know why the other two aborted, but this one worked. So it looks like I've got rooted stock 2.3.3 again!
I'm not so sure I'm going to try for 2.3.4 now.
Thanks for the help!
Ok so I've had this phone forever, mainly use it to play games and stuff on bc im not with sprint any more im using a bionic as main device. But I have always loved to hack this phone with new ROMs and mods etc. bout four months ago Idr why but mine and my gf's were unrooted and I had to re-root them. So I got hers hooked up first to the comp, rooted, adb and everything worked fine I've had custom ROM on hers since. For some reason, I plugged mine in RIGHT after hers, adb wouldn't pick it up as a device for some reason. Now I finally am able to pick it up on ubuntu through adb and i've tested it I can push/pull/sideload etc, fastboot flash recoveries etc. I have flashed several recoveries today to try to flash su binary to root the phone and one recovery worked, IDR which it was because I renamed it to recovery.img but its some kind of touch recovery thats not cwm. that one worked for me to actually load after I flashed it, so I sideload flashed the su zip and on the log it went through chains' little messages and said the root successfully worked. i booted the phone and had superuser, but none of my superuser apps are working. i updated the app. still not working. I tried to boot to recovery, didn't work i get stock recovery. every other recovery i flash will NOT work when trying to boot to recovery. it only takes me to the error page where i can get to stock recovery. can ANYONE help me here. i need to get su working and get the device to where I can really load a custom recovery. any help from anyone will really be appreciated. i've been trying to get this phone flashable for a while. im getting frustrated, once again, like every other time i've tried to do it in past months.:crying:
ok so my problem is fixed. I guess what was going on is I didn't get a successful root by having to sideload & flash the zip through the only recovery that would work. When I flashed TWRP, thankfully to the gods of hacking and Android that worked. So in TWRP I was able to successfully flash the su binary and that allowed me to successfully root/maintain root. Through that my recovery stayed in place and did not go away. Through this I was able to flash a ROM, that being an old (not too old, back in the 2.12 era) and did not work efficiently, everything closed as soon as I opened it. So I found an old GB CM7 ROM on my sdcard and successfully flashed it and since it didn't have GApps I had to go through the browser to download rasbean and flash that. That worked well, although the OP had stated GApps was included and was not, so I had to get him to send me the rb version of the jb 12-12-12 gapps, and flashing that worked and fixed all my issues in that rom so...long story short(after a long story) I got everything working. So basically, for future reference, find a recovery that will stick long enough for you to get the su binary onto storagge and flash it.
Last week I struggle with root on my One-S (S4)
I have followed this thread and it went fine till "root" When downloading / installing TWRP .zip superSU it went wrong, because it is a update file http://download.chainfire.eu/446/SuperSU/UPDATE-SuperSU-v1.99r3.zip, so I downloaded a older version, and then installed update file in recovery
Now SuperSU says SU binary must be updates and I can't update with file under TWRP.
So, now some programs say that I'm rooted and some say I'm not
Another problem is that I can't connect through USB anymore, I tried under win-7 win-8.1 and several PC, yeas I tried also several HTC drivers (it worked in the past with fastboot) In Recovery I CAN mount
WTF went wrong, and more important how can I get proper root
ROM = Twitedkat 2.5
TWRP 2.7
OMG !!!
I can't believe it, while writing post I tried to update SuperSU with update file, just like 7080120 attempts before.
Tried again and now it works like a charm.
I really can't understand what went wrong.
But.. problem solved
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
ilinimud said:
So here is my problem. I was rooted on JB,and getting propmts to update to KK. After some research I found out that is it now rootable/unlockable, so I downloaded the .183 update and used RSD Lite to get on the update. That went well. Used towelroot and motoapocalypse to get rooted and unlocked. Also went well. Used Flashify to install TWRP. Well again. Heres where things fell apart. I booted into recovery to backup my stock ROM. After I did that I moved the backup to my SD card like an idiot not knowing it couldn't be restored from there. So I downloaded Validus 5.2 and Gapps. When I flashed them I was stuck in a boot loop on start up. Power down and tried again, still looping. Fastbooted to Recovery to restore my backup, but it was not there cuz it was only reading from internal storage (oops). So I was screwed. Then I read that CM had updated the modem or something and that you had to update stuff to use it. Still not sure about all that, but anyway. I thought maybe that was the problem, so I downloaded an older version of CarbonROM from June that was before the CM changes thinking I would be good now, but when I flashed it the same thing happened. Boot loop. So I went back into fastboot and flashed the RSD Lite stuff again. Rooted with towelroot. Unlocked with motoapocalypse. Verified status code 3 in fastboot. Verified root with Root Checker. Installed Flashify, but I haven't installed a recovery yet. Was TWRP my problem? Why am I boot looping on custom ROMs? Can someone help me out, or point out something Ive missed here?
Click to expand...
Click to collapse
You have to ensure the ROM you are using is built for the KK kernel. Not all ROMs work with the KK kernel.
Here is a list of ROMs that work with KK:
http://www.droidrzr.com/index.php/topic/48909-kitkat-roms-list/
Anything else will result in what you are experiencing - bootloops.
Hey everyone,
I recently decided to root my stock 5.0 s5 on sprint. I got everything rooted fine using TWRP and decided to flash a custom rom. I made a backup and everything however during the process the flash deleted my internal storage and pretty much everything. I think the root is gone but TWRP still boots up fine and dandy. Can anyone point me in a direction? I tried plugging my phone up through my computer but ODIN won't even recognize it. Any advice would be great. Cheers
Edit: got it working
Glad you got it working. Did installing the stock OA6 file get it?
VandyCWG said:
Glad you got it working. Did installing the stock OA6 file get it?
Click to expand...
Click to collapse
Hey sorry for the late reply. I changed bootloaders to stock and reflashed a stock rom from the s5 root website. I was confused because I thought going into TWRP was going into download mode, which is wasn't. My download mode was working fine and I just reran everything through odin. Had to move my SD card to my tablet to get a rom on it though, and installed from that.