Novice here.
Ran the All-in-One utility today and after the CWM installed I hit "Perm root" without reading the thing below telling me to boot to recovery first. It's now stuck in boot loop. Everything went off fine up until the Perm root. Even that said successful and then restarted. Only after the process was completed did the recovery loop begin. No HTC logo loop. Just reboots into CWM over and over no matter what technique I use (except for opening the case).
I've read this: http://forum.xda-developers.com/showthread.php?t=1599363
And am trying to install ADB to push ANY possible ROM over to the SD card. My recovery allows the toggle of /mount sdcard and /mount system, however adb fastboot push doesn't work. "error: device not found"
And I can't do this: http://forum.xda-developers.com/showthread.php?t=1644730 because my phone is stuck in the recovery loop. If I try volume down + power, it just comes back to recovery screen. I've tried factory reset, I've tried wiping cache, I've tried wiping Dalvik, and still nothing. I did flash the SuperSu.zip after I had used the Perm Root button on Haroon2000's app.
I'm incredibly flustered as I've rooted devices for years and this is my first problem. I've seen similar complaints all with ideas of breaking into the phone and unplugging it's battery so I can get to the bootloader etc, but I'm so very confused. So many posts telling me to do so many things.
Can someone please help break down a tangible solution here? I'm freaking out.
Cheers
EDIT: If someone can get my phone fixed, I'll Paypal them $50 USD. I really need my phone back ASAP :\
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
beats4x said:
I don't know if this is your solution, but you did not mention it as one of your attempts.
Have you looked into running an RUU?
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
nik.the said:
I'll update this again once I try breaking the phone down and yanking the battery. But I have tried running the RUU. I can't get to the bootloader right now and it's not listing the device when I adb devices.
I'm going to go home from work since I've spent 7 hours on two machines (XP/7) trying to fix this PoS and redo everything from the ground up. Hopefully my anger will have overcome it.
Something I've noticed however, is that within the CWM recovery, I can use the All-in-one tool to reboot the phone. So it is reacting to ADB commands. Perhaps trying to use ADB fastboot (Right-click method) instead of full ADB installation could be a problem with trying to push a ROM zip. Also, as far as the RUU goes. I don't remember what happened there. I'll edit this when I get home.
Click to expand...
Click to collapse
Okay, update.
I was able to get ADB working and detect my phone.
Next, I was able to push Venom Rom to phone. I factory reset, wiped cache, wiped Dalvik, and was able to install Venom.zip. It then asked to reboot (per Venom screen) and I said okay. It then returned to CWM Recovery. I was confused but left everything as is. I have now reset the phone by holding the power button for around 10 seconds. It then restarted to the HTC Quietly Brilliant screen. I have been looking at that screen for about 5 minutes.
Also pertinent: I did try to run the RUU, but it didn't connect through USB. (I forget what it said verbatim). So that didn't work. I also was able prior to this entire process get into the bootloader via dumb luck.
Any suggestions? I am staring at the HTC boot screen still. Do I try to restart and enter bootloader? If so, then what? It seems there is something wrong with CWM. Can I switch recoveries? Can I uninstall it?
Calm down we have all been there,
When you flashed venom did you flash the boot image? Also i use twrp instead of cwm i find twrp better .
To enter bootloader hold power button and down vol together .
As gazknight said, this seems like proper kernel not being flashed or having an issue. If you flashed the boot.img with fastboot, try again erasing cache from fastboot first. The commands are as follow:
fastboot erase cache
fastboot flash boot boot.img (where this boot.img is the one inside the zip from the rom you choose and must be left in the same folder than fastboot)
It happened to me a couple times when i was on hboot 1.14 that I had to flash the boot.img a second time sometimes, somehow it was not working the first time, randomly, even though the flash had completed ok on fastboot.
If still doesn't work try doing a factory reset from TWRP and flashing ViperOneS again.
If that still doesn't work, you might want to try another rom, like TrickDroid, you would then have to flash the boot.img from this other room with fastboot, remember that.
Try and let us know
Hold down volume down while you're trying to boot, that will get you in boot loader, go to fast boot by pressing the power key, connect your phone to your computer, run the flash viper boot img thingy and you're set!
Envoyé depuis mon HTC One S avec Tapatalk
Same issue with HTC One S bricked but in European version, Stock ROM
hello,
I did't want to start a new topic, as I'm experiencing a similar issue with my HOS. Briefly, yesterday morning I plug the phone from charger at 06.00 am. Play with it for a while and then go to work. Used it at work for a few phone calls until 10.00 am (so 4 hours on fully charge battery). Then at 10.00 am I went into a meeting and left the phone out of my sight for 20-30 minutes. When I came back from the meeting I realize that the phone was closed. I try to open it (power button) but nothing. Press power for 10-30 seconds with volume down - still no effect.
Then I took the charger (the original one that I always use to cherge it) and plug it, left it for 2-3 minutes and press power. The phone starts but all I have is the white screen with HTC logo and if I press the power button + volume down the phone goes into bootloader. That's all I can do with it for now.
I have stock rom, bootloader is locked and I never try to root the phone. Is it any chance to repair it by myself or I have to sent it to the repair shop.
many thanks in advance.
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
nik.the said:
Alright so I feel like I'm getting closer.
Here's whats happening now. It's in the HTC boot screen loop. I can get it into bootloader whenever I want, but now it's not detecting /sdcard in recovery. Within the bootloader, fastboot won't detect my device and my computer (Windows 8) claims the device is malfunctioning. I can still use fastboot adb commands from my computer when it is in recovery. I have gone into bootloader and cleared storage, as well as factory reset after. Also, it used to reboot into recovery endlessly. Now it appears that isn't hte case and reboots from recovery into the OS, but will not work.
I'm going to try and flash using adb w/o sdcard the boot.img as suggested above. I'll keep updating so others can know the process if they soft-brick their phone (I'm assuming this is a soft brick because I can still run things etc).
Update: trying to do fastboot erase cache from within recovery gives me "Waiting for device". As I've said, for some reason, it says the device is malfunctioning/not detected when I'm in the 1.14 Hboot Bootloader. But again, I can issue adb devices from within recovery. Sdcard still not mounting.
Edit: I'm issuing adb commands through adbfastboot files. Do I need to have the Android SDK fully installed with the Manager thing, or does the basic adbfastboot work (From here: http://www.htconeforum.com/forum/ht...e-your-htc-one-s-back-100-stock-relocked.html). That adb fastboot has the following files: adb, fastboot, adbwinapi.dll, adbwinusbapi.dll.
I think the source of the current problem is that I can no longer access my /sdcard or mount it. One step forward, then two steps back -_-.
Click to expand...
Click to collapse
You might need to do it as administrator.
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
nik.the said:
I think I've got it. One last tip. All of the above has been helpful, but I think the problem was trying to use my Windows 8 laptop. The second I got to work, I plugged it in on the bootloader to my XP machine and voila! it recognized fastboot and listed devices.
I have tried to run the RUU 2.35.531.7 but just like unrooting my old phone, I had issues because that update was already on this phone, so it goes through the entire process only to tell me on the windows XP utility that it had failed because it was the wrong update. When I did this to my old One S right before I sent it into Tmobile for warranty, it did the same thing with the 1.53 RUU, then when I found the 2.35, it worked like a charm.
So my last question (hopefully) then is, am I missing something as for installing an OLD or exact same RUU? Or is there a newer one than the 2.35.531.7?
I haven't tried on a Windows 7 machine, but I have one available here at work. I'm wondering if I should try to fastboot a ROM. Any suggestions what I can do to get it back to stock, or an old old stock version? I'd like to root it so I can use my Titanium Backup.
Update: Before ending this reply, I read that the RUU may be failing because the bootloader is unlocked/tampered still. I'm going to run it again to grab the error code to make sure of the issue, because it seems you should be able to revert or use any RUU (correct?).
Click to expand...
Click to collapse
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Darknites said:
The bootloader does need to be relocked for the RUU too work and the RUU you used before should work because I have used the same RUU a few times and it worked fine.
Click to expand...
Click to collapse
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Yeah! Fixed!
After enough toggling, I changed the recovery to the T one and relocked my bootloader. It turns out detecting the device wasn't necessary somehow. Then I ran the RUU and voila!
nik.the said:
I'll try that. thanks.
Now on the same XP computer, it's not showing when I adb devices, however it does show in device manager. This changed after trying to do the RUU without relocking.
Click to expand...
Click to collapse
Not sure whats up with that, never had any issue on win7.
Windows 8 fastboot works on my laptop for some reason. I installed the drivers from the HTC Sync folder.
Sent from my HTC One S using Tapatalk 2
Hi guys,
I recently traded an iPhone for a nexus 5 and I've been loving it except I've been having an issue lately. The phone was flashed with a custom rom and kernel. I had a couple of issues so I attempted a factory wipe via cwm but it seemed to freeze when it says 'wiping cache' etc. so I restarted the phone by pressing the three buttons and now I can't save anything to my phone (it says no sd card) and I keep getting 'google play error reports' and I cant access the camera.
I've been attempting to flash to stock in hopes that it would solve the problem and that I could get updates OTA in future so I downloaded 4.4.2 and managed to get the adb and fastboot files working via nexus root toolkit. When I attempted to flash the rom onto my phone, NRT reboots my phone into fastboot mode and a script comes up saying 'it should take 5 or so minutes' and 'press any key to finish' - except my phone is doing nothing but showing the regular fastboot screen.
So I've looked all over and found a method posted online that uses cmd to flash it but I need a file called something like 'hammerhead434839.img' except I cant find it. I figured that it would be in the recovery rom I got from google so I opened up the .tar file but there is only one file inside.
Theres another method I found that uses some 'flashall.bat' but I am not sure where to find it.
Does anyone have any suggestions? I'd really appreciate it as I cant even make or receive calls or texts anymore. thank you
matbahi said:
Hi guys,
I recently traded an iPhone for a nexus 5 and I've been loving it except I've been having an issue lately. The phone was flashed with a custom rom and kernel. I had a couple of issues so I attempted a factory wipe via cwm but it seemed to freeze when it says 'wiping cache' etc. so I restarted the phone by pressing the three buttons and now I can't save anything to my phone (it says no sd card) and I keep getting 'google play error reports' and I cant access the camera.
I've been attempting to flash to stock in hopes that it would solve the problem and that I could get updates OTA in future so I downloaded 4.4.2 and managed to get the adb and fastboot files working via nexus root toolkit. When I attempted to flash the rom onto my phone, NRT reboots my phone into fastboot mode and a script comes up saying 'it should take 5 or so minutes' and 'press any key to finish' - except my phone is doing nothing but showing the regular fastboot screen.
So I've looked all over and found a method posted online that uses cmd to flash it but I need a file called something like 'hammerhead434839.img' except I cant find it. I figured that it would be in the recovery rom I got from google so I opened up the .tar file but there is only one file inside.
Theres another method I found that uses some 'flashall.bat' but I am not sure where to find it.
Does anyone have any suggestions? I'd really appreciate it as I cant even make or receive calls or texts anymore. thank you
Click to expand...
Click to collapse
Google nexus 5 binaries. Download the 4.4.2 factory image. Use 7-zip to extract it. In there you'll find the flash-all batch file
Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!
hanssw said:
Hi Everyone!
Really new to xda so I'm not sure if this is the right place to post this at (sorry). I have a nexus 5 that after I (purposely) rebooted, is now just stuck on the boot animation, (it was not updating to 5.1.0 or 5.0.1). I tried leaving it on but it just kept spinning until the phone died. I can access fastboot, and recovery, have tried wiping cache, and factory resetting multiple times. Nothing has happened. I have gotten adb and fastboot on my mac, and downloaded a factory image from google to try and reflash, but ./adb devices doesn't show anything, even though the phone is connected in fastboot mode. (On the google website it says drivers shouldn't be an issue?). My nexus 5 is running stock, was unlocked before but now still unrooted, its the US version and I have tried connecting to the computer with multiple micro-usb cables (including the one included in the box). What should I do? Or how do I get my nexus 5 to show in ./adb devices?
I'm stumped, any help would be greatly appreciated , thanks!
Click to expand...
Click to collapse
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1
Mojar7070 said:
As long as you're able to charge the phone still while it's off you'll have some options.
When you do factory reset, does it complete the process and reboot on its own??
Just saw this thread. You might want to try it out.
http://forum.xda-developers.com/showthread.php?t=2957801
Sent from my 1+1
Click to expand...
Click to collapse
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.
hanssw said:
Yes it does does complete it, I reset it from recovery, so it completes and when it restarts its still stuck on the loop again for another hour. I'm downloading the file, hopefully it works
EDIT: Already completed the flash using the tool, but the first boot didn't work, reformatting again after the flash.
EDIT 2: Reboot doesn't work after the reformat after the flash.
Click to expand...
Click to collapse
Have you tried flashing through fastboot?? I'll be honest I'm not to knowledgeable on fastboot, maybe someone else would like to chime in for that.
I've used wug fresh nexus tools but you'll need the phone to boot up properly to get into developer settings to turn on USB debugging.
Sorry if I can't help any further.
Sent from my 1+1
Nexus 5 boot stuck
Bro just try to write the following Command in cmd in the platform devices folder
'fastboot devices' instead adb devices. copy the stock image to the Platform-tools folder and just flash it via fastboot commands. mine was stuck in boot animation and did the same
My device is not unlocked or rooted. It was up to date on the OTA updates then one day it would not boot. I have tried to flash the most current ASUS stock ROM to recover it using the SD card. I renamed the extracted file as EP201_768_SDUPDATE.zip and tried to use that from RCK. It appeared to work but then stuck in a rapid boot loop. I also re-tried the process doing a Wipe Data first with the same exact result. Fastboot sees the device but doesn't appear to accept me trying to send it anything. ADB does not see the device and I know my windows drivers worked fine, I have transferred files using the USB cable often. Do I have any other options?
Sorry man, but that looks like the end of the road for your tablet.
You've tried everything available to you with a locked bootloader. You can't do anything in fastboot - you just won't get past the locked bootloader. Believe me we have tried! There's a thread on the Transformer Forums where I and a few other guys tried everything we could think of to get past it. No dice...
Give the microSD method a few more tries, and then start shopping for a new one....
Sent from my Nexus 5X using Tapatalk
Hey community, today i was sent here by a friend that though maybe this forum can help, a few days ago i was on my Infocus m808 watching videos on youtube, videos were of the new COD WWI, however my phone randomly shut off and then kept vibrating when i turned it on, nothing appeared so i left it a few hours (5 roughly) then i though i would try it again and i tried it again, and now it actually shows me a screen saying "Infocus Powered by android" then below in little white writing it says "Could not load the correct dtb file!!!!!!" any clue how i can fix this?
Jakeyiii said:
Hey community, today i was sent here by a friend that though maybe this forum can help, a few days ago i was on my Infocus m808 watching videos on youtube, videos were of the new COD WWI, however my phone randomly shut off and then kept vibrating when i turned it on, nothing appeared so i left it a few hours (5 roughly) then i though i would try it again and i tried it again, and now it actually shows me a screen saying "Infocus Powered by android" then below in little white writing it says "Could not load the correct dtb file!!!!!!" any clue how i can fix this?
Click to expand...
Click to collapse
Sounds like you modified your boot.img or your boot.img got corrupted.
It seems you'll have to flash your stock firmware to fix this.
Sent from my SM-S903VL using Tapatalk
Response
Hello, I'm experiencing logging problems with the jakeyiii account. However umm your saying its the wrong boot.IMG I haven't touched the boot atall. I was watching YouTube videos while being connected to the laptop for charge. Even if I was to try putting a stock boot image onto the phone its impossible because soon as I see the logo "InFocus" it comes up saying something "cannot load the correct dtb file!!!!" Can't boot into fast boot either as when I try to boot into fastboot that's the message it says "cannot load the correct dtb file!!!!!" When trying to turn on normally it just vibrates and does nothing.
Any clue how to get stock back on?
Jplay444 said:
Hello, I'm experiencing logging problems with the jakeyiii account. However umm your saying its the wrong boot.IMG I haven't touched the boot atall. I was watching YouTube videos while being connected to the laptop for charge. Even if I was to try putting a stock boot image onto the phone its impossible because soon as I see the logo "InFocus" it comes up saying something "cannot load the correct dtb file!!!!" Can't boot into fast boot either as when I try to boot into fastboot that's the message it says "cannot load the correct dtb file!!!!!" When trying to turn on normally it just vibrates and does nothing.
Any clue how to get stock back on?
Click to expand...
Click to collapse
I said it sounded as if "you" modified boot.img OR your boot.img got corrupted "on its own". You said that you didn't modify anything so of the two possibilities I listed, which possibility does that leave?
Sent from my SM-S903VL using Tapatalk
Response
The remaining possibility is it just got corrupt on its own this is the second time this has happened to me. The first one happened like 4 months after getting it and the n again 9 months after that. So currently stuck using a family's phone to message here haha.
If I can't boot the phone in faceboot or even recovery any clue how I can solve this?
Jplay444 said:
The remaining possibility is it just got corrupt on its own this is the second time this has happened to me. The first one happened like 4 months after getting it and the n again 9 months after that. So currently stuck using a family's phone to message here haha.
If I can't boot the phone in faceboot or even recovery any clue how I can solve this?
Click to expand...
Click to collapse
You might can try the script from the thread linked below in the "using adb" section, it might allow you get connected to adb while in bootloop at the InFocus screen.
From there you can try a dd command to push a copy of your device's boot.img if you can find a copy of your firmware and extract the .img from it or you can try getting someone with your device to pull a copy of boot.img from their device for you to use.
Have you tried booting to safe mode?
Sent from my SM-S903VL using Tapatalk
Hello
Yes I've tried to boot into safe mode can't boot what so ever. It just vibrates if I try fast boot I get the DTB file error. And no one near me has a in focus.
I can't enable USB debugging because it won't boot and can't use ADB because it won't find the device as when USB is connected the phone trys to boot and restarts constantly .
have you found solution to it bcos me have same problem
Jplay444 said:
Hello
Yes I've tried to boot into safe mode can't boot what so ever. It just vibrates if I try fast boot I get the DTB file error. And no one near me has a in focus.
I can't enable USB debugging because it won't boot and can't use ADB because it won't find the device as when USB is connected the phone trys to boot and restarts constantly .
Click to expand...
Click to collapse
i need help too