Hey Guys,
So I have been all threw the forum over the past week plus trying to find a solutions and have tried the majority of the ones on the site. Here is what happend:
HOW I GOT HERE:
I was running a CM10 nightly build from 01/15/2013 that was installed via CWM. I had been running it for about a week. When I went to bed I set my phone on the nightstand. About 2 hours into sleep the phone rebooted as I eventually woke up and noticed it thinking it was just the phone wonking out. When I up fully 6 hours later the phone was still rebooting. Since then when ever I cut on the phone it will no get passed the Google logo with the padlock. I can boot into fastboot and recovery. I am running the latest CWM 6.0.2.5.
PHONE VITALS QUICK GLANCE
Android ROM version: CM10 01/15/2013 Nightly Build
Baseband: D720SPRLC1
Bootloader: D720SPRKC5
Recovery: CWM v6.0.2.5
WHAT I HAVE TRIED
Restoring from backup
My first fix was to flash three different roms via recovery (doing full wipes each time)
Then I tried flashing a new recovery
Formatting /system, /cache, /data, and /boot and then flashing a new rom
Then I focused on trying to get the USB storage to mount so I tried using adb shell to repair the file system and that worked
Then I tried new roms and things got REALLY weird. When I would place a rom on “sdcard” it would be available to flash. When I flashed it though it would not take and upon returning to recovery it wouldn’t be there or when I mounted the storage again. After about 10 times of this I figured let me make sure I am not crazy and try the following.
Format the internal storage. In windows when I tried this windows would show that the device formatted and was empty one I dismounted after putting items on it and go back to storage by both remounting it or by recovery the old data would come right back. In Ubuntu when I tried formatting it both via disc recovery and gparted they both said the device was empty but that they were unable to create a partition.
So then I went down the path of all of the debricking tools out there including the one from AdamOutler's (I think it is called ressurector), ODIN, and the Nexus Root Tool all with varying results.
Ressurector kept saying injection failed
ODIN just does not work on the nexus s from what I can tell (spent a day researching and no one seems to give a definitive answer on this one)
And Nexus Root Tool attempts to flash back to stock but runs into an error with the baseband.
So next I decided to try and flash back to stock using the Google images. Using Ubuntu I ran the flash-all.sh that comes in the zip and kept running into the baseband issue.
So next I found OldBlue910’s post with all the OTA updates and I went after trying to use that to fix my phone. Thanks to the amount of instruction he gives I got a lot further and got the flash-all.sh in his stock zip to give me a better error message telling me which baseband I needed to have to go back to stock which when I double checked he includes in the zip. The problem is when I try to flash that radio fastboot tells me I was successful but the bootloader still reads as D720SPRLC1 and does not change regardless of what I do. When I try flashing the stock images again after flashing the radio I receive the same errors.
So now I think I have hit the real brick wall and unless someone has any advice I will need to go and buy a new phone. Hoping you guys can help. I figured if you guys can figure out a hard brick then this is still doable, I have just exhausted my own realm of knowledge.
Please and thank you’s to anyone with advice.
Could you get any lights ON? The buttons or the screen?
lights are on
Yes during the boot loop the Google logo comes up, then the screen goes black, then the Google logo comes back, and finally in about 20 seconds the lights come on. Once that happens after about 4 minutes the process starts all over again.
Related
Well I was caught my the new MIUI ROM i saw this morning and decided to switch from Bionix. I have flashed many phones and farmiliar with the process. I left my phone alone while the install occured. I watched it wipe data and cache. Now when it powers up, the samsung logo appears for 2 seconds and a quick I9000 logo flashes for like .25 of a second. The 3 button method to force it into recovery. I dont have a usable copy of windows to boot camp from my mac so ODIN is currently not an option.
I can get the phone into download mode so i know its not a lost sailor, i just need a mac solution without booting windows. I really dont want a refurb replacement from warranty either
You want heimdall.
Yup. heimdall rocks
samsung screen of death...
LinuxBozo said:
You want heimdall.
Click to expand...
Click to collapse
SO here goes...
first off i am rooted, have all appropriate drivers, etc, have used dab to root.
I am a total newb, and was experiencing issues flashing a new ROM. when trying to install the zip through cwm the phone said "signature verification failed" or something to that extent. so being the deductive thinker that I am, I formatted everything: boot, system, sd, etc. After doing this, I realized that I totally wiped out all the files on the internal sd.
so i downloaded the heimdall one click- it connects but fails regardless of whether i flash boot loader.
i can access blue 3e recovery and download mode.
now. i want to know if it is possible to push or even install a ROM through adb. I've been playing around with it all day and have gotten nowhere.
i thought maybe i could load up a rom to an external sd but obviously you can't mount an extsd in cwm.
am i screwed?
ill gladly donate through paypal if someone can help me get my baby up and running again. i do not want to be using my nokia from middle school anymore!!
thank you in advance for ANY help you can give me.
Rob
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Edit: Problem fixed. Downloaded the original all in 1 tool for htc one s, plugged phone into comp went to fastboot and with the tool flashed the phones stock recovery. I reset to factory defaults and cleared storage with it from the bootloader. After that, I flashed clockwork mod recovery again and my SD card was able to be mounted and accepted files from my adb push, and I reflashed cyanogenmod. Wuzzah!
milesmarrero said:
Ok guys, new to the forums but this problem has had me fully occupied for the last 6 hours and I feel like I have tried everything. I had cm9 alpha 12, and went to flash TrickDroid v5.0, something happened and I'm currently stuck in some wierd bootloop/soft brick. I had access to CWM but my SD card wouldn't mount and my adb push attempts didn't do anything, for reasons I don't know why. My phone would start up into the wierd trickdroid bootup and last for like 30 minutes. I tried the solution of another thread on how to fix a bootloop/ softbrick, but now I dont have any CWM access and I can only access the bootloader or the endless bootup screen. I tried using the all in one tool to flash the CWM again but it just restarts it and puts it back into the bootup, and when i restart to go to bootloader to acess the recovery, it goes back to bootup. Every solution I try makes my problem worse, and to top it off I cant turn my phone off and keep it off because it will just start back up. Thanks.
Click to expand...
Click to collapse
lol, meant to "quote" not "thanks".
Can you fastboot a new recovery?
Did you do a full wipe coming from CM9 to TrickDroid
Well I can't access the phone from usb on my computer (still takes charge though), so I don't think I can flash a recovery thru fastboot (I'm not too experienced though). From cm9, I wiped all and flashed trickdroid + tweak set, then it just stat their at home screen. CMW being lost occurred later.
Im in the same situation rght now. I have trickdroid and I went into my tweaks to set them back to their original setup...so removing all of the options I chose before when I used the tweaks for the first time. When I rebooted my phone it just hangs on the HTC screen. I can get into recovery and I tried reinstalling trickdroid but its still getting stuck. Not sure what to do at this point. I don't think I can put a recovery file on this since I can't connect it to my computer.
Hopefully someone can help us.
But the thing is I can't access recovery. I try to flash it again with the all in 1 tool and it won't work. It says it went through, but accessing it doesn't work.
If its recognised by USB when plugged in computer just run an ruu that's my solution all The time lol
Sent from my HTC One S using xda premium
Ok i somehow managed to get TWR on my phone, but still unable to mount the SD. How do I run the RUU? I downloaded it, but the instructions are flawed I think
Connect with USB to.computer go into faatboot USB then run ruu on pc
Sent from my HTC One S using xda premium
Well I thought the RUU was going to work, but it just stops at the HTC and gives me an error saying I can't. What now?
Ok currently, I relocked my bootloader in an attempt to do the RUU, but I get a 155 Unknown Error up doing such, using the TMOUS 1.53 ruu... other places I have seen say something about returning to the stock img etc, but I'm quite stuck. Any advice appreciated
htc one s stuck in bootloop almost unresponsive
hey guys, got a brain teaser for you.
i have a tmobile htc one s, unlocked, rooted using all in one htc tool, been at it for two days now. im stuck on the boot screen showing its unlocked, i used to be able to get into the boot loader screen but now it seems ive dead ended. ill hold any combination of power and vol up/down, the keys flash for 10 sec and the screen flashes once, i let go and it reboots, keeps that htc screen, after 20-30 sec goes black. my pc doings like it detects a device but i cant locate it. ive used adb and the htc all in one unlock tool trying to get any kind of os to launch.
Shortly before this i was able to go into the boot loader, clear and master reset the files and cache, and search for the rom zip, thus never allowing me to flash. on a journey to place this in the phone through various combinations of the all in one, adb push, and everything else i found on youtube, countless forum posts, i seem to be in a deeper hole now.
I ultimately want to end with a cm10 nightly on my tmo htc one s. I have never done this to a phone without a sd card. i come to this community humbly seeking any and all advice. thank you.
My phone took a dump on me yesterday and I've been scouring XDA over the last few hours for a solution and I see a lot of similar issues but nothing exactly like mine. Please bear with me...
I was using the latest MIUI version by evol4g and the only persistent issue was some lag, nothing with my SD card or the core android processes. I went to bed last night and my phone was charging then a bright light in my room woke me up at about 0400. I looked at my phone and noticed it had rebooted itself into recovery. I attempted a simple reboot and it got stuck on the black Google screen. I pulled the battery and booted it back into recovery and attempted to restore it but noticed that none of my nand backups were available. I figured, this sucks, but I'm tired so I'll just re-flash the ROM and deal with it later. I attempted to flash a .zip from the SD card and it told me that no SD card could be found. I got up and went to my laptop to copy a ROM from my desktop to the SD card and when I went to mount the USB drive it told me that there was "no file to write to" (or something similar). Basically, I have no SD card access and no way to mount the USB to attempt re-flashing of anything.
I've made multiple attempts over the last 6+ hours to re-flash CWM to the latest version (using both ADB and the fastboot version), I've tried to re-flash through ODIN and I've even gone as far as attempting to UNroot just so I can get this thing to function. Every time, though, it gets stuck while writing the system files then doesn't get any further. When I'm using ABD, I've got no SU access and while in fastboot, the system gets stuck writing .system files. As of right now, it's been attempting to write the system files for the UNroot process via the Nexus S Hacks .zip for over an hour. Any and all advice is welcomed and thanks for reading!
jordanjackthomas said:
My phone took a dump on me yesterday and I've been scouring XDA over the last few hours for a solution and I see a lot of similar issues but nothing exactly like mine. Please bear with me...
I was using the latest MIUI version by evol4g and the only persistent issue was some lag, nothing with my SD card or the core android processes. I went to bed last night and my phone was charging then a bright light in my room woke me up at about 0400. I looked at my phone and noticed it had rebooted itself into recovery. I attempted a simple reboot and it got stuck on the black Google screen. I pulled the battery and booted it back into recovery and attempted to restore it but noticed that none of my nand backups were available. I figured, this sucks, but I'm tired so I'll just re-flash the ROM and deal with it later. I attempted to flash a .zip from the SD card and it told me that no SD card could be found. I got up and went to my laptop to copy a ROM from my desktop to the SD card and when I went to mount the USB drive it told me that there was "no file to write to" (or something similar). Basically, I have no SD card access and no way to mount the USB to attempt re-flashing of anything.
I've made multiple attempts over the last 6+ hours to re-flash CWM to the latest version (using both ADB and the fastboot version), I've tried to re-flash through ODIN and I've even gone as far as attempting to UNroot just so I can get this thing to function. Every time, though, it gets stuck while writing the system files then doesn't get any further. When I'm using ABD, I've got no SU access and while in fastboot, the system gets stuck writing .system files. As of right now, it's been attempting to write the system files for the UNroot process via the Nexus S Hacks .zip for over an hour. Any and all advice is welcomed and thanks for reading!
Click to expand...
Click to collapse
I hate to be the one to tell you this.. sounds like you got bit by the nand flash failure that all of us nexus s owners fear. Warrenty repair is the only recourse in that case.
Sad to say but sounds like you got bit .
I've been searching for 3 days now, and everything I've found has not worked. I am using twrp, and have tried flashing three different roms. Everything in fastboot and twrp runs fine, but as soon as I get to the asus boot screen (I've seen it to be called the circle/ring of death) it freezes, then reboots. I've tried re flashing back to stock rom, upgrading firmware/ downgrading firmware, different twrp versions, stock recovery, hitting my head on the tablet. I don't know what else to do.
My tablet was version 4.2.1 I used the boot unlocker v_8. Tablet was rooted and working for one day, then over night this began.
If someone could please point me in the right direction, or is this just a case of my tablet being done for?
Fox5.56 said:
I've been searching for 3 days now, and everything I've found has not worked. I am using twrp, and have tried flashing three different roms. Everything in fastboot and twrp runs fine, but as soon as I get to the asus boot screen (I've seen it to be called the circle/ring of death) it freezes, then reboots. I've tried re flashing back to stock rom, upgrading firmware/ downgrading firmware, different twrp versions, stock recovery, hitting my head on the tablet. I don't know what else to do.
My tablet was version 4.2.1 I used the boot unlocker v_8. Tablet was rooted and working for one day, then over night this began.
If someone could please point me in the right direction, or is this just a case of my tablet being done for?
Click to expand...
Click to collapse
Do you have valuable data on the tab? If yes, I'd suggest you copy them off your internal storage to your external Sd card with TWRP, then erase everything per buster99's script (search for the name); flash stock rom via fastboot. You don't need to reset the tab by poking the hole since you apparently can get to fastboot without issue.
DO NOT touch the wipe data icon on the boot screen! Do everything with TWRP only. If you choose to do it via SD card, remove the card before rebooting to see what happens. It has occurred to me that leaving the card inside might cause problems. Good luck.
graphdarnell said:
Do you have valuable data on the tab? If yes, I'd suggest you copy them off your internal storage to your external Sd card with TWRP, then erase everything per buster99's script (search for the name); flash stock rom via fastboot. You don't need to reset the tab by poking the hole since you apparently can get to fastboot without issue.
DO NOT touch the wipe data icon on the boot screen! Do everything with TWRP only. If you choose to do it via SD card, remove the card before rebooting to see what happens. It has occurred to me that leaving the card inside might cause problems. Good luck.
Click to expand...
Click to collapse
I copied anything I wanted saved, but I did not do a legitimate backup of software files.
I have pressed the wipe data icon on the boot screen under the confusment of the many different posts. What step does that leave me at?
EDIT:
So crazy Buster99 fastboot flash did it. Sucks because I tried that before but I guess I may have missed one line of the reflashing script. Well thanks, after three days I've finally been put in the right direction.
Seems like that pesky /misc partition is causing problems. Glad you got it sorted out though.
Sent from my SGH-T889 using xda app-developers app
Unlocked, rooted, TWRP, Cataclysm Final Lollipop (my phone never played nice with any MM ROM I tried, so I just went back to this and have been great ever since)
My phone has been rock stable for months, today I pull it out of my pocket and the screen is black. I turn it back on and it freezes on the Google screen with the unlock logo.
I can get into bootloader via power+voldown, but if I launch recovery it gets past the Google screen but then freezes on the TeamWin page.
Any suggestions, please? Searches intimate power button issues, but given I get no bootloops, I can turn the phone off reliably by holding the power button down, and it freezes at the same point consistently, it's hard for me to think that's the issue in my scenario, too. Thank you!
As an update, I used fastboot to successfully flash the newest version of TWRP, just to be sure, but it still gets stuck in the same spot, as does trying to boot normally.
Try flashing a stock ROM including userdata.img file.
audit13 said:
Try flashing a stock ROM including userdata.img file.
Click to expand...
Click to collapse
Thanks for the suggestion. Is there any way to get my personal data off before I do this?
I guess beggars can't be choosers, but I'd hate to lose anything I don't have backed up already if it ends up being another issue after all (the power button, etc.).
A corrupted ROM can prevent a clean, freshly-installed recovery from launching properly?
Thanks again.
Try flashing different version of TWRP? Maybe one of them will allow you to mount the data partition and copy off your data.
While trying to flash the (stock) new system images, I keep getting "remote: flash write failure" and/or "remote: failed to erase partition." This is via a toolkit or manually via fastboot.
The bootloader remains unlocked through all this
It's especially odd, since now I'm getting it on my recovery partition, which I was able to write to earlier today.
A cursory search of this forum suggests I'm SOL unless I replace the whole motherboard, at which point I might as well get a new phone. Do you (all) concur?
Last ditch thought: I went jogging when it went dead--outside chance a connection to the memory on the motherboard got jostled and could be reattached? Or is it fried?
Continued thanks.
The memory is soldered into place but it is possible that something happened during your jog. I also jog with my nexus 5 for 20 to 30 km per week and have done so for the past year without any issues.