I just got my HTC One less than a week ago, rooted and flashed my first ROM with no issues. Decided to try out a different one today, but after flashing it, my phone rebooted into bootloader and has been stuck there. Anytime I try to reboot the phone or reboot into recovery, it just goes back to the bootloader screen. Same thing when I attempt a factory reset. I've tried reinstalling TWRP recovery and although it says the install is successful, it's still stuck in bootloader. I also tried to install my previous ROM via fastboot command (which is failing), but to no avail. I got the following output:
sending 'zip' (994092 KB)...
OKAY [ 38.486s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 54.083s
I'm on the Sprint version, and I'm aware that 4.2 ROMs don't work on Sprint yet so I'd be using older versions of them for the time being, but I guess I inadvertently used an incorrect version.
Any ideas?
hmm...must really be bricked. :-\
if it is booting into bootloader, it is not bricked...
try connecting your USB cable , select fastboot in bootloader... it should show the FASTBOOT USB
now on your PC, where you have the ADB/Fasboot files, SHIFT+RIGHT CLICK on that folder and select Open command window here.
In command window, enter FASTBOOT ERASE CACHE
and try booting again...it might work.....
mathrania said:
if it is booting into bootloader, it is not bricked...
try connecting your USB cable , select fastboot in bootloader... it should show the FASTBOOT USB
now on your PC, where you have the ADB/Fasboot files, SHIFT+RIGHT CLICK on that folder and select Open command window here.
In command window, enter FASTBOOT ERASE CACHE
and try booting again...it might work.....
Click to expand...
Click to collapse
nope, no luck I also tried flashing recovery again in addition to it, still going straight to bootloader.
nsuviolin2005 said:
nope, no luck I also tried flashing recovery again in addition to it, still going straight to bootloader.
Click to expand...
Click to collapse
Try using the HTC one AIO toolkit to flash a new recovery and see if that helps.
It uses the FASTBOOT method to flash. Plus you have options to try CWM and TWRP.
If that works you should be able to flash a different rom to get your device up and running
gazlufc said:
Try using the HTC one AIO toolkit to flash a new recovery and see if that helps.
It uses the FASTBOOT method to flash. Plus you have options to try CWM and TWRP.
If that works you should be able to flash a different rom to get your device up and running
Click to expand...
Click to collapse
When I click to flash a recovery, it gives me a prompt that there will be 2 screens and to close the 1st one once I'm in bootloader...I do that, then the 2nd screen comes up but nothing happens. Same thing for both the Sprint options
You need to be in the fastboot menu not bootloader menu.
Sent from my HTC One using xda app-developers app
gazlufc said:
You need to be in the fastboot menu not bootloader menu.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I was...FASTBOOT USB mode, my phone is booting into that menu by default
nsuviolin2005 said:
I was...FASTBOOT USB mode, my phone is booting into that menu by default
Click to expand...
Click to collapse
hmmmmm thats strange.
What you could try is download one of the recoveries and unzip the file so you get the .img file of that recovery.
Then try to flash your own recovery option. see if that works
gazlufc said:
hmmmmm thats strange.
What you could try is download one of the recoveries and unzip the file so you get the .img file of that recovery.
Then try to flash your own recovery option. see if that works
Click to expand...
Click to collapse
Is this supposed to be automated or something? All I get with any option is an command line screen that's in the folder but nothing's happening.
nsuviolin2005 said:
Is this supposed to be automated or something? All I get with any option is an command line screen that's in the folder but nothing's happening.
Click to expand...
Click to collapse
could you post screenshots so I could see what happening?
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
The only other thing I could think of is to try an RUU if all else fails but I can't guarantee that it will work
Sent from my HTC One using xda app-developers app
gazlufc said:
could you post screenshots so I could see what happening?
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
The only other thing I could think of is to try an RUU if all else fails but I can't guarantee that it will work
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Profit! Turns out the flash your own recovery option worked, I just didn't follow it all the way through, initially...after I closed the command prompt screen, the Open file menu came up and I was able to pick my TWRP recovery and boot into it. I restored my backup I made right before flashing the bad ROM and the phone is booting past the bootloader now
But.....next issue is that it's booting to a black screen instead of the regular lock screen, and after sitting there in that state for a few minutes, it reboots. :-\ I'm wondering if this is just because I deactivated the phone and switched back to my EVO LTE while trying to fix the One...that would be a first, though, as the phones are usually operational even if they don't have service.
nsuviolin2005 said:
Profit! Turns out the flash your own recovery option worked, I just didn't follow it all the way through, initially...after I closed the command prompt screen, the Open file menu came up and I was able to pick my TWRP recovery and boot into it. I restored my backup I made right before flashing the bad ROM and the phone is booting past the bootloader now
But.....next issue is that it's booting to a black screen instead of the regular lock screen, and after sitting there in that state for a few minutes, it reboots. :-\ I'm wondering if this is just because I deactivated the phone and switched back to my EVO LTE while trying to fix the One...that would be a first, though, as the phones are usually operational even if they don't have service.
Click to expand...
Click to collapse
Glad to hear the recovery worked. As for the phone staying on black. I would just advice to flash a nother rom if the problem still persists mate
gazlufc said:
Glad to hear the recovery worked. As for the phone staying on black. I would just advice to flash a nother rom if the problem still persists mate
Click to expand...
Click to collapse
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
No problem man glad I could help
Sent from my HTC One using xda app-developers app
nsuviolin2005 said:
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
Click to expand...
Click to collapse
\question i am having the same problem you have but i think its due to water damage i am going straight into the bootloader are sometime i can get it into safe mode
nsuviolin2005 said:
Well, flashing and restoring didn't quite work, so I wound up having to do a factory reset (thankfully I had all my files on my PC from when I had to move them from my EVO, and since I'd only upgraded a few days ago, I didn't lose a whole lot) and a re-lock of the bootloader.
Only weird thing is, even re-locking it, the phone remained in S-OFF state. But I was able to rerun the HTC Dev Unlock to unlock the bootloader again and flashed a correct ROM. Back in business.
Thanks for your help...that toolkit you linked me to saved my ass.
Click to expand...
Click to collapse
To be S-ON again you need to reboot into bootloader
Then FASTBOOT USB
then run fastboot and write "fastboot oem writesecureflag 3" and enter. Now you will be S-ON
But do NOT S-ON unless you absolutely need to.
Related
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
camo_flage said:
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
Click to expand...
Click to collapse
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
Fastboot erase cache command will fix this problem. Boot to your bootloader select fastboot usb and run that command.
haha im not too good with computers more of a mobile only tech haha can u explain that please?
gabriel1946 said:
haha im not too good with computers more of a mobile only tech haha can u explain that please?
Click to expand...
Click to collapse
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
---------- Post added at 06:07 PM ---------- Previous post was at 05:54 PM ----------
gabriel1946 said:
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
Click to expand...
Click to collapse
Last time this happened there was a script that was running that corrupted the cache partition. That is why erasing cache fixes it.
esloan said:
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
Click to expand...
Click to collapse
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
gabriel1946 said:
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
Click to expand...
Click to collapse
Okay where is your adb file? Ex mine is in a C:/Android. By default if you installed the android SDK the adb files would be in the SDK folders. Any way if you were fast boot flashing a recovery your going to do the same thing just use fastboot erase cache as the command instead of the recovery command. If none of this makes since PM me.
Resolved via PM
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
megahafo said:
Hello folks,
During update from Revolution HD 3.4 to 3.5 something went wrong and process stopped before it got finished. Now I ended up in bootloop, even recovery is not working. I've tried to use RUU but failed on CID verification as I'm having the phone from 3 IE. Is any chance to bring it back to life or i just got very expensive paper weight ?
Or if anyone can provide RUU for 3 IE I'm willing to pay for it.
Bad day, bad day...
Thank you for any advice.
Click to expand...
Click to collapse
What is happening when you enter recovery?
MacHackz said:
What is happening when you enter recovery?
Click to expand...
Click to collapse
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
megahafo said:
I can see the recovery screen (clockworkmod) for about 0.1 second and it reboots again.
Click to expand...
Click to collapse
try reflashing it and wiping cache etc
MacHackz said:
try reflashing it and wiping cache etc
Click to expand...
Click to collapse
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
tokenwoken said:
Hi, I am having the same issue with my phone as of right now. I tried re-locking bootloader and then unlocking again and also reflashing clockwork and I am still getting the bootloop and cannot access recovery (flashes for 0.1 secs and then disappears).
What exactly did you do to fix the issue?
Click to expand...
Click to collapse
The cue there if wiping the cache partition.
Riyal said:
The cue there if wiping the cache partition.
Click to expand...
Click to collapse
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
tokenwoken said:
Hi Riyal,
I have fixed that issue with fastboot erase cache. Now, I am having a problem loading a ROM because it states in recovery that it "can't mount SD card"?
Click to expand...
Click to collapse
I had the same problem, going to try to sideload this stock de-odexed rom (didn't work the first few times) and CHILL THE PHUCK out until AOKP.
scared me lol first HTC device, brand new, and I thought I broke it.
P.S I realized that REVOHD uses AROMA, that's why it wouldn't sideload.... Am I Rite?
Similar issue
tokenwoken said:
Figured it out, I just had to ADB push a stock rom and then re-wipe/re-flash
Click to expand...
Click to collapse
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
thanks but....
shrex said:
Hi
Greetings,
Did you flashed boot.IMG if no
Extract the boot.img from the Rom
Copy that file to abd/fastboot folder
Now connect you phone with pc with your phone booted in fastboot/bootloader,
Later flash boot.img by following command
"Fastboot flash boot boot.img"
Reboot and your done
If you do not know how to use abd search for it
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium
Click to expand...
Click to collapse
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
suhazgummadi said:
thanks for your advice but how do i extract boot.img when the phone is not even switching on to connect to the pc.
Click to expand...
Click to collapse
You have the zip file of ARHD in your pc extract the boot.img using winrar thats it and you have to put that file in abd/fastboot folder in pc
and everything what i said its to be done in pc
excpet putting phone in fastboot mode
suhazgummadi said:
My HTC One device is actually suffering the same problem.
I bought my HTC One Sprint(Sim-Free Edition) in the US and got it to India.
But after I inserted my Indian Sim it said ''SIM LOCK ENABLED''.....I just got frustrated and
rooted the device and tried to install ''Android RevolutionHD (Odexed)'' Stock ROM with the help of TWRP.
But after I installed the stock rom, my device is just showing the HTC symbol and hanging there itself.
It Hangs there for around 6-7mins and reboots and the same happens again.
The only thing I can do is to get in to the bootloader and Power OFF the Device.
Any Help???? Please..... just having a costly paper weight since 2 weeks.
Please need help urgently....!!!
Click to expand...
Click to collapse
The Sprint version is never going to work on any carrier other than Sprint. It's a CDMA device. The sim slot if for connecting to Sprint's LTE network, but requires a CDMA connection first and foremost to work at all.
Sent from my HTC One using xda premium
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
megahafo said:
Thanks, for hint. Got recovery working again
What I have done.
1.) Unlocked, re-locked bootloader.. (i think this did the trick, full wipe ?)
2.) Wiped cache
3.) Re-flash clockworkmod
4.) Upload ROM using sideload.
Now the phone is back. I hope i will not break something again.
Click to expand...
Click to collapse
Quickest and easiest way to fix this issue is...
'fastboot erase cache'
'fastboot reboot recovery'
hnt20 said:
Thanks, this actually worked for me. I have HTC One TMO edition, i did a sdcard format and things went very bad from there and i was not able to flash anything and recovery kept rebooting.. after i tried this below, it worked like a charm..
Click to expand...
Click to collapse
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
HumorousMaximus said:
I'm stuck on the same boat :\
I was able to finally boot into CWM recovery but I'm getting write errors all over the place.
I used the AIO Kit to re-lock the bootloader and unlock it - Reflashed CWM - Tried to sideload ARHD 10.0 but the DOS prompt errors out saying that it cannot find my device.
Little help?
Click to expand...
Click to collapse
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
mky4b11 said:
i was going through the same thing yesterday and i thought i had bricked my phone. what i did that finally worked, was unplugging the usb, restarting the computer, reinstalling htc drivers, then restarting the computer, then using a different usb port. i was finally able to sideload ARHD whereas before i could do fastboot commands, but it wasn't responding to the sideload, and wasn't able to mount the sdcard, so i thought i was screwed. :good:
Click to expand...
Click to collapse
Thanks for the tip, I was able to get back into AROMA but the original issue that got me to this point came up again. Aroma installer runs and during the install it kicks itself out and sends me back to recovery, so the installer doesn't complete. It gets to about 30% and craps out just after it writes system data and starts to install the .apk's. Screen goes black and it reboots itself and sends me to recovery.
thoughts?
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Hi
Greetings,
Install HTC drivers for abd to recognize your phone, this will help you to atempt abd sideload and also fastboot commands
Flash the recovery againg
"fastboot flash recovery name-of-recovery-.img"
And try again by adb sideload this is your last option before flashing a ruu
Sent from my HTC Sensation Z710e using xda premium
mfadhil said:
Hey guys
I just rooted my HTC One yesterday and installed a custom rom on it, all went well until my brain went stupid and formatted data, system, sdcard and i had no nandroid backup in place. I just upgraded from a HTC One X and from what i know, previously i could just flash CWM and mount usb and it'll go work normally. However, for my situation now, none of the recoveries actually allow me to mount usb.
Also, i'm on 1.29.404 and i can't find any RUUs that is the same as this. I also cant execute adb push for rom because my computer doesnt recognise my phone in adb devices. Can anyone help me out with this issue ?
cheers!
Click to expand...
Click to collapse
I'm in a similar boat, did a "format data" in TWRP and now I can't boot. I can access the phone via ADB tho. I'll let you know if I find a solution.
Same thing here
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
shrex said:
Hi
Greetings,
Have to tried this code after installing the recovery
"fastboot erase cache" if not unlock your bootloader install recovery and try this code
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
NoDroid4U said:
I also did the same thing. However, I can't boot into recovery at all; It says its about to boot into recovery, then the phone just turns off. The only thing I can do is boot into the bootloader, and lock or unlock it. Right now, its unlocked. I've tried everything. I would love to just use an ruu exe., but the only one I've found isn't working for my phone for whatever reason. I kept getting error 132 signature error. The ruu I was using was "RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3" I was using a similar version ( I think it was 1.29.300 or something), and yes, I relocked my bootloader before using the ruu; If anyone knows of a different, newer version, or really, anything at all that can help, it would be greatly appreciated.
Click to expand...
Click to collapse
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
matt95 said:
that RUU won't work because you have to match your version-main to the RUU you are about to flash, if that version-main doesn't match than you will get that error 132 which is normal in your case... if you want to know which is your version main just type
Code:
fastboot getvar version-main
Click to expand...
Click to collapse
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
NoDroid4U said:
Thanks; I've found the correct ruu, but now I have a new problem. As of right now its .zip and not .exe; I cant boot into recovery and adb isnt working either. Any suggestions for getting it on the phones memory, seeing as there is no sd card I can remove?
Click to expand...
Click to collapse
i think you downloaded an OTA and not a RUU
---------- Post added at 09:05 AM ---------- Previous post was at 09:04 AM ----------
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
i won't suggest to hit that factory reset button! causa actually it soft-bricked some devices... you've been lucky
bradr00lzd00d1 said:
I had my phone booting the entering recovery screen for about half a sec and would always boot back into the OS so I installed TWRP through fastboot than went to factory reset in the hboot menu and it booted into recovery it worked for me but Idk if it will work for you
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
as long as i know the only file that you can flash in that OTA is the firmware.zip that will update your bootloader but i'll do it after some more tries...
please paste here the output of
Code:
fastboot getvar all
NoDroid4U said:
No such luck; Is there anyway at all to push it to the internal memory using fastboot?
Click to expand...
Click to collapse
Have you tried "fastboot -w" this will factory reset your phone from fastboot. Then try re-flashing recovery again.
NoDroid4U said:
Hey thanks for replying; Unfourtently, even after reflashing twrp and clearing the cache, it still just shows the entering recovery mode and the restarts. In fact, now it is constantly restarting until I boot it into bootloader and power the system down that way. Any other suggestions?
Thanks
Click to expand...
Click to collapse
I've had this problem on the one x plus, what I did and please bear with me, it does work Firstly flash cwm and clear cache, once you have done that you should be able to boot recovery. Once in cwm format everything including data! yep I said data! then reboot back to fastboot and flash TWRP and rewipe everything again (including data) then sideload or push your rom across to your phone.
Done this twice now on mine when I got bricked (for no reason!) I can only think the file system becomes corrupt somehow.
alright guys, i solved the issue and my phone is back to normal !
to those guys still facing the issue, i suggest you flash the latest cwm then try using the sideload function > adb sideload <filename.zip>
mine came back to life after that, heh
cheers!
Also fixed
Hey guys, thanks so much for everyones help last night. I also got mine all fixed and set away. For anyone interested, I used the ruu and steps in this thread: http://forum.xda-developers.com/showthread.php?t=2250904
Thanks again to everyone for their help!
Okay, I have the HTC One for Sprint. I flashed it using TWRP 2.5 and I can only currently access the bootloader.
I accidentally wiped everything off my phone and when I plug it in my computer sometimes recognizes it has HTCONE or as Android Device, either way I cannot send files over using adb sideload. Gives me the error that there is no device.
Currently my device somehow also got "unrooted" in the process. I am looking at the phone not being able to transfer any roms I want over to install a new OS nor can I restore it to the old OS.
Is there anything I can do?
PS: I did install the drivers and other devices. If someone can please help me even over teamviewer it would absolutely make my day. I have been troubleshooting this device for about 30 hours straight now.
Since you can access bootloader, you'll probably be ok..
What happens when you try to access recovery?
what happens in "fastboot usb" in your bootloader when you command
Code:
fastboot devices
If your device shows just do
Code:
fastboot flash recovery name_of_recovery.img
Download one of these recoveries (since you have the Sprint version) <- this will get you into recovery if you're not already able to access it..
http://techerrata.com/browse/twrp2/m7wls
yup
redbull123 said:
Since you can access bootloader, you'll probably be ok..
What happens when you try to access recovery?
what happens in "fastboot usb" in your bootloader when you command
Code:
fastboot devices
If your device shows just do
Code:
fastboot flash recovery name_of_recovery.img
Download one of these recoveries (since you have the Sprint version) <- this will get you into recovery if you're not already able to access it..
Click to expand...
Click to collapse
Well I have the recovery since thats the only one I can access. Thing is though neither of my computers can recognize the device and I cannot send the rom necessary to boot the OS.
I can access the Bootloader and I can access the Recovery. I cannot access the memory on the phone in order to send files over
Have you tried flashing the RUU? Hopefully this can help:
http://forum.xda-developers.com/showthread.php?t=2250904
sweetnsour said:
Have you tried flashing the RUU? Hopefully this can help:
http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
would I be able to unlock the bootloader after
iivezaj said:
would I be able to unlock the bootloader after
Click to expand...
Click to collapse
important part is getting the phone working again then worry about unlocking bootloader
Can always try flashing a custom ROM using an OTG cable if you've wiped the OS. I always wipe my storage and OS when I do a clean install and then flash the ROM straight from my flash drive ... Obviously you'll need to fastboot a custom recovery, if you are able to.
CheesyNutz said:
important part is getting the phone working again then worry about unlocking bootloader
Click to expand...
Click to collapse
im going to try the method you linked me
When you're in recovery do adb devices. If it shows your phone you can sideload a ROM.
AT&T HTC One
GPe 4.3
hi bro, that happened to me as well, i have installed usb driver but adb cannot detect my device. I was running windows 8 that time but when i used windows 7 adb was able to detect my device with no issues and i was able to transfer custom rom zip file to it. I dont know if that could help you but i'm just sharing my experience.
Sent from my IRON Phone
---------- Post added at 10:32 PM ---------- Previous post was at 10:27 PM ----------
can you even go to recovery? if yes, try using other computer, preferably windows 7 or xp.
Sent from my IRON Phone
---------- Post added at 10:39 PM ---------- Previous post was at 10:32 PM ----------
sorry i didnt read this.
Sent from my IRON Phone
I can access the bootloader and the recovery (switched to PhilZ touch) and sideloaded a couple roms but NONE of them work. One of the roms boots up and goes in a restart loop after hitting the front page (no icons on the screen just top bar) Even the stock version of htc one for sprint didn't work it kept resetting my device.
I tried using the RUU also but it gives me a bootloader error saying it cannot be restored after a few minutes of loading.
Well every rom so far attempted has been a dead end. CM, AOKP, all have booted and started a restart loop. I am not sure if its my kernal or anything else.
I just need some help. What I did notice is that even if the devices were working I had no cell signal. Someone please help lol
iivezaj said:
Well every rom so far attempted has been a dead end. CM, AOKP, all have booted and started a restart loop. I am not sure if its my kernal or anything else.
I just need some help. What I did notice is that even if the devices were working I had no cell signal. Someone please help lol
Click to expand...
Click to collapse
Where are you getting these ROMs from? Have you tried the ones in the Sprint HTC One forums?
Sent from my HTC One using xda premium
Hello,
I have trouble with my nexus 6. I tried to flash the latest factory image for 5.1. But my system.img did not flash... after hours, I did not found any solution, so tried to lock and relock the bootloader again. Locking worked as espected... but unlocking returns the following message:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.004s
Now I sit here, no booting device because of missing android version and I can not unlock the bootloader anymore... Somebody can help?
Thanks
Andy
Sorry - it's not good news:
http://forum.xda-developers.com/nexus-6/general/relock-bootloader-time-updating-to-5-1-t3053497
**** that's really bad!!! But thanks for your reply!!!
ANDYx1975 said:
**** that's really bad!!! But thanks for your reply!!!
Click to expand...
Click to collapse
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk
narezese said:
I did have same problem with system.img, i rebooted my phone and it was on a bunch of fc phone, nfc Bluetooth, etc.. So i went back to recovery tried again, same results. So i decided to flash a lower firmware i think 5.01.. Radio, bootloader and then system.. Damn it... System got a error... Then i did a - w , and flashed 5.1 again.. This time system was successful .. Everything went good.. Reboot my phone.. Went to recovery mode, factory reset.. And rebooted system.. Went good.. Then on Settings developers OEM unlock was uncheck..? Anyway.. Im glad everything works fine..
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!
ANDYx1975 said:
I do not know if it was unchecked... I can not reunlock bootloader anymore.... that's my main problem!!!
Click to expand...
Click to collapse
Im talking about mine.. Before flashing 5.1 the option was checked..
Sent from my Nexus 6 using Tapatalk
You sir have a brick. Your only option as of right now is to try to get Motorola to replace the device for you.
Sent from my Nexus 6 using XDA Free mobile app
ok... tkanks I have to try this... even if I think my chances are almost zero!!! Thanks anyway!!!
Have you tried to adb sideload the ota .zip?
yeah I only have access to fastboot... and he does not find the device
From fastboot can you get to stock recovery? After selecting recovery in fastboot, you'll get the Android dude ... But you have to hit the power and volume up/down as well (forget the exact combo) to get into recovery. From there you select install install via adb (forget the exact verbiage, but it's the second option from the top). From there you run adb, not fastboot
---------- Post added at 04:00 AM ---------- Previous post was at 03:58 AM ----------
http://www.droid-life.com/2015/03/1...1-ota-updates-for-nexus-devices-4-5-6-7-9-10/
^ d/l link with a link to (better) flashing directions
to be honest I do not know it's already out home to the repair service... ****... I should be more patient!!!
Gotcha ... Don't feel bad, you're not alone. I, and many others, did the same/similar and ended up in the same situation.
I been rooting/tinkering for 6+ years across 10 or so devices and it turns out a friggin NEXUS is the first device that I brick! ?
(I'm fully aware of the risks we take with unlocking amd rooting, but IMO Google screwed the pooch with this OEM Unlock "feature" in developer options! Why make unlocking dependent on a setting WITHIN the OS??!)
So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found
ANDYx1975 said:
So hey... I managed to get it back from my post office... when I go into fastboot, I can choose "Recovery Mode" and it seems to boot into it:
But when I try to sideload... I get the following message:
Code:
adb sideload nexus.zip
error: device not found
Click to expand...
Click to collapse
You need to boot into stock recovery. From the screen you are in press volume up and power.
What ^ he said ... Then once in stock recovery select the second option (install update from adb (or something like that))
ok... I can not go into recovery... the google logo appears and nothing happens... ****!!! But hey thanks anyways!!!
That sucks! Sorry man!
@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6
Casper34 said:
@rootSU
At that screen in his pic, isn't he supposed to hit power+volume + or something to get to a different screen?
I might've wrong, but I did read somewhere when you get the dead Droid guy, you hit that combo and it takes you to a different screen.
Sent from my Nexus 6
Click to expand...
Click to collapse
Yes, thats what I said.