Need help! I think I bricked my device.. - LG Optimus 4X HD

Hy guys.. I think i messed up.. My phone had unlocked bootloader an non-touch CWM. Then I tryed to install toucn CWM (http://forum.xda-developers.com/showthread.php?t=2298420) I was getting an error "adb is not recognized as an internal or external command operable program or batch file" so I changed path via this http://www.computerhope.com/issues/ch000549.htm. I executed demand and after it finished(or so I thought it finished) i shut the down and whent into recovery. But it didnt want to go into recovery, the half of the screen was in some stripes and it was flashing. I turned it of and on, went into ROM manager and reboot in recovery and the same thing happened again and now I cant turn my phone on! It just shows that weird flashing lines and it turns off.. Help guys!
EDIT! I just managed to turn on my phone! What should I do now? I dont want to go back in recovery through ROM manager because I dont think it will work.. In ROM manager it says that I have a new version available(that I am curently on 5.xxx and there is 6.0.3.1 available..

brunek said:
Hy guys.. I think i messed up.. My phone had unlocked bootloader an non-touch CWM. Then I tryed to install toucn CWM (http://forum.xda-developers.com/showthread.php?t=2298420) I was getting an error "adb is not recognized as an internal or external command operable program or batch file" so I changed path via this http://www.computerhope.com/issues/ch000549.htm. I executed demand and after it finished(or so I thought it finished) i shut the down and whent into recovery. But it didnt want to go into recovery, the half of the screen was in some stripes and it was flashing. I turned it of and on, went into ROM manager and reboot in recovery and the same thing happened again and now I cant turn my phone on! It just shows that weird flashing lines and it turns off.. Help guys!
EDIT! I just managed to turn on my phone! What should I do now? I dont want to go back in recovery through ROM manager because I dont think it will work.. In ROM manager it says that I have a new version available(that I am curently on 5.xxx and there is 6.0.3.1 available..
Click to expand...
Click to collapse
Why in God's name do people insist on trying to use ROM Manager? It is a pile of c**p that causes far more issues than need be. Just read the threads and do it manually so that you understand what you are doing, and why - or worst case use the All-In-One-Toolkit instead.

SimonTS said:
Why in God's name do people insist on trying to use ROM Manager? It is a pile of c**p that causes far more issues than need be. Just read the threads and do it manually so that you understand what you are doing, and why - or worst case use the All-In-One-Toolkit instead.
Click to expand...
Click to collapse
I unlocked my bootloader with All in one tool, and flashed CWM with it.. I installed ROM manager so that I can reboot into recovery easily..
Can you help me fix this problem?

install the recovery manually then try to reboot phone in recovery don't use Rom Manager...
Sent from LG 4X HD using Tapatalk 2

brunek said:
I unlocked my bootloader with All in one tool, and flashed CWM with it.. I installed ROM manager so that I can reboot into recovery easily..
Can you help me fix this problem?
Click to expand...
Click to collapse
I don't think that you have done what you think you have done If you had followed the first thread you listed then you would have installed CWM Touch v6.0.3.1 on your phone as that is the version you would have had to download.
If your phone boots up fine into normal operation then simply follow that guide again TO THE LETTER - and when you reboot into recovery, do NOT use ROM Manager to achieve it - use the proper method.

SimonTS said:
I don't think that you have done what you think you have done If you had followed the first thread you listed then you would have installed CWM Touch v6.0.3.1 on your phone as that is the version you would have had to download.
If your phone boots up fine into normal operation then simply follow that guide again TO THE LETTER - and when you reboot into recovery, do NOT use ROM Manager to achieve it - use the proper method.
Click to expand...
Click to collapse
I started and I got a message c:\adb is not recognized etc..I already changed the path in "envirometn variables" to c:..
When I open cmd it says like this C:\ADB> and then I type there c:\adb>adb shell.. Or should I just type adb shell??

brunek said:
I started and I got a message c:\adb is not recognized etc..I already changed the path in "envirometn variables" to c:..
When I open cmd it says like this C:\ADB> and then I type there c:\adb>adb shell.. Or should I just type adb shell??
Click to expand...
Click to collapse
Common sense is often needed when doing anything with your phone - and a bit of basic computer knowledge.
I've just re-read the thread you linked to as a check. The command "c:\adb>adb shell" is a mistype by the OP. It should be "c:\adb\adb shell" or, if you are already in the C:\ADB folder, simply "adb shell"

SimonTS said:
Common sense is often needed when doing anything with your phone - and a bit of basic computer knowledge.
I've just re-read the thread you linked to as a check. The command "c:\adb>adb shell" is a mistype by the OP. It should be "c:\adb\adb shell" or, if you are already in the C:\ADB folder, simply "adb shell"
Click to expand...
Click to collapse
Ok.. I did that! Now,when I wrote the last comand "sync" it opened a new row [email protected]:/# and the next step in OP is restart in recovery mode.. Should I just turn off the phone and get into recovery? Its the same like the last time..

brunek said:
Ok.. I did that! Now,when I wrote the last comand "sync" it opened a new row [email protected]:/# and the next step in OP is restart in recovery mode.. Should I just turn off the phone and get into recovery? Its the same like the last time..
Click to expand...
Click to collapse
That's the best way to get into recovery, yes.

SimonTS said:
That's the best way to get into recovery, yes.
Click to expand...
Click to collapse
It worked! Thanks man, I dont really know what did I do wrong the first time.. Sorry I bothered you! Thanks again!:good:
But when I open ROM manager(dont be mad I just wanted to see ) it said that I have 5.x.x.x. version and that the new one is available..

brunek said:
It worked! Thanks man, I dont really know what did I do wrong the first time.. Sorry I bothered you! Thanks again!:good:
But when I open ROM manager(dont be mad I just wanted to see ) it said that I have 5.x.x.x. version and that the new one is available..
Click to expand...
Click to collapse
I'm glad it worked. As for ROM Manager, I have no idea as I won't contaminate my device with it. If the Recovery says it's 6.0.3.1 then I'd trust it and uninstall the pointless application.

SimonTS said:
I'm glad it worked. As for ROM Manager, I have no idea as I won't contaminate my device with it. If the Recovery says it's 6.0.3.1 then I'd trust it and uninstall the pointless application.
Click to expand...
Click to collapse
You are right,recovery says its 6.0.3.1. so there must be a bug in application. I deleted ROM manager, it brought me only problems! Thanks again man!:good:

Related

Phone has no O/S installed, cannot detect phone to put rom zip on phone. please help

I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
cburch85 said:
I believe I overwiped my phone, it has no rom on it now, and when I plug it into the computer, it makes the noise, but will not show up in windows explorer. I am able to boot into recovery, TRWN, although I can't do anything from there because I have no rom to install. I have tried installing the latest HTC drivers, using a different cord, disabling antivirus, pretty much everything previously listed in these forums. Is there a way to use the command prompt to send a rom over to the phone? Please help.
Click to expand...
Click to collapse
donwload the all in one toolkit use it to erase cache then install recovery. after that either mount usb otg and copy rom to sd or sideload a rom. all in one toolkit automates everything you need to do:good::good:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
cburch85 said:
I wish I could say that worked, however when I try to use the AIO toolkit, when it launces the command prompt it says 'device not found.' same problem as windows. There has to be a way to force a file on there. Any ideas? Again, I can boot to recovery but have no zip on the phone memory to flash.
Click to expand...
Click to collapse
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
skinsfanbdh said:
if it says device not found press the power button once and try again. it will say once in fastboot close the first window if you close the first window and nothing happens then press power and it should start
if your in fastboot options should be----bootloader----reboot----reboot bootloader----power down
Click to expand...
Click to collapse
Thanks for getting me this far. Mounting didn't work, so I sideloaded rom. it is showing up on the phone as "sideload.zip" i try to run and it fails. Any ideas?
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Guich said:
Have you used this command?
Code:
adb sideload /path/to/rom.zip
If yes, it will work.
Maybe sideload.zip contains rom and if sideload.zip don't have meta-inf it will not flashed
Click to expand...
Click to collapse
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
im guessing your using twrp but just select no dont root the rom is already rooted and it should boot. may take getting through a few aroma freezes but it will boot
cburch85 said:
I get it sideloaded and installed android revolution. however, when I'm done installing the rom, trwn tells me "superuser is not installed, would you like to install now?" I say yes and then the phone goes blank, and reboots to bootloader. Any ideas?
Click to expand...
Click to collapse
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Guich said:
Change the rom or don't say yes when you have the question
Sent from ONE with Tapa4 Beta
Click to expand...
Click to collapse
OK, so I didn't say yes to the question this time after sideloading android revolution. same thing. goes blank then reboots to bootloader menu. So I tried sideloading viperrom 1.04. This time after it finished sideloading it randomly installed instelfl, and now viperrom is installed, its booting up to the phone now finally, yet before anything can initialize, it just reboots again. It's been caught in this boot loop about ten minutes now. No end in sight. Any ideas?
ViperRom from Sprint or AT&T one forum?
Your phone is branded or no-brand?
However, boot into recovery, and use this command:
Code:
adb push name_of_rom.zip /sdcard
, then flash it
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
cburch85 said:
Also, I have now tried flashing and installing TrickDroid which also boots to the O/S but then after a few seconds reboots and starts all over again. I just let it run, and it boots, then reboots, over, and over, and over again. Any ideas?
Click to expand...
Click to collapse
Have you tried to flash the boot.img from fastboot?
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
cburch85 said:
I fixed it!!! I had to download the latest RUU for the HTC One. I ran the RUU after relocking, and then started the root process from scratch. RUU is the only thing that would work. Also, the best rom I have gotten to work for sprint is ViperRom, TrickDroid installed and booted but the camera wouldnt work. Thanks for the help and suggestions!
Click to expand...
Click to collapse
Where did you find the RUU for sprint? I cant seem to find one that works with my CID: SPCS_001.
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
zach832 said:
Hey, im having the same problem. I have nothing on my phone, not even root. I cant use adb commands but fastboot seems to work. Im using TWRP 2.6.3 recovery. If anyone can help that would be awesome!!
Click to expand...
Click to collapse
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Can't detect SD Card
Guich said:
Reflash the latest TWRP and check if adb work.
Becuase without it you can't push/sideload a rom...
Click to expand...
Click to collapse
Hi, I'm having sort of the same problem. My phone is stuck on a bootloop, I flashed a new recovery because the previous TWRP stopped working. When I try to wipe data/factory reset, It says that it can't detect E:\ or the SD Card. I can't even mount it. Any ideas? Please help. Thanks

TWRP 2.6 [stock on "swipe to unlock" in recovery]

I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
chamo311 said:
I went to GooManager and downloaded the new version of TWRP. When I reboot to recovery my phone gets stuck on "swipe to unlock" and doesn't let me do anything but to restart my phone on fastboot. I can't flash any ROMs
Can someone please help me? Thanks in advanced. :crying:
Click to expand...
Click to collapse
did you install the correct version for the htc one sprint(wls)(spr)
Aldo101t said:
did you install the correct version for the htc one sprint(wls)(spr)
Click to expand...
Click to collapse
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
chamo311 said:
I was using the previous version (2.5) just fine and just went to GooManager and I assume that GooManager will download the right for me.
I opened GooManager and click on Menu then Install OpenRecoveryScript and then I manually rebooted to recovery once the download finished. And that's when I get stuck on "swipe to unlock"
Filename was "openrecovery-twrp-2.6.0.0-m7wls.img"
Click to expand...
Click to collapse
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Kraizk said:
I direct downloaded the file from their site and fast boot flashed after verifying MD5. There is definitely a problem with he recovery
Click to expand...
Click to collapse
That sucks! So should I do try adb fastboot or go back to the previous version (2.5)?
What sucks is that without 2.6 working properly, I won't be able to flash any ROM with the new android version (4.2)
Aldo101t said:
well, thats the right one, i would suggest that you manually download the file and install using adb fastboot.
Click to expand...
Click to collapse
Did the ADB and still the same problem. Should I go back to previous version of TWRP?
chamo311 said:
Thank you sir! I am new to this so I am learning as I go. I read that these are the steps to follow to do an ADB Fastboot. Please correct me if I am wrong. Thanks again for your help.
1) Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to "twrp.img"
2) Turn off your device. Turn on the device and keep holding volume down until a menu shows up. Select fastboot from the menu list.
3) Plug the device into your computer. Run the following command via the command line:
fastboot flash recovery "twrp.img"
Bless.
Click to expand...
Click to collapse
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Aldo101t said:
no, thats not right, don't put on your sdcard, download the file, put it in your directory where yoy have fastboot(on your computer. cd to that directory, open command prompt, (administrative) type adb reboot bootloader, when in bootloader (fastboot usb) type fastboot flash recovery(name of file).img
Click to expand...
Click to collapse
It is broken, several users are reporting it in the original TWRP post as well
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
Now that's some "good news" LOL! because I thought I screwed my phone and I wasn't going to be happy about it. I went back to v2.5 and everything works great!!
Thank you so much for all your help, guys!
Bless!!:good:
Kraizk said:
It is broken, several users are reporting it in the original TWRP post as well
Click to expand...
Click to collapse
that could be, thanks for the heads up
STUCK in TWRP Recovery
Aldo101t said:
that could be, thanks for the heads up
Click to expand...
Click to collapse
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
just revert back to 2.5.0.0 and you are good to go
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you just recently update your firmware to the new base? The reason I ask is because after I did I used the the firmware with the bootloader and recovery included. I had reflashed TWRP 2.5. Well I noticed that the method of holding down volume key and and power button would not work for me at all whether I was in the os, bootloader or recovery. So I flashed the Rom I was on again and it fixed it. So I am wondering this is what is happening to you. Maybe just let the phone lose charge then plug it in reboot to the os then into bootloader and flash the 2.5 TWRP recovery. Only thing I can think of your not bricked
Jason0071 said:
Completely stuck in Recovery. Can swipe to unlock screen but can not reboot even with Volume Down and Power button on Sprint HTC One. Just stuck. Phone is useless. Cant throw adb commands, nothing. WTF? What to do any ideas? Just watching the battery go down on the recovery screen...
Click to expand...
Click to collapse
Did you try holding the phone under a bright light then holding power and vol down to reboot. This works sometimes
Sent from my jacked HTC One!!
Aldo101t said:
just revert back to 2.5.0.0 and you are good to go
Click to expand...
Click to collapse
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
mzel said:
Given all the issues with 2.6 listed here, should I update from 2.5 to 2.6? Also, if TWRP says 2..5.0.0 at the top of the screen, how do I know this is the wls version?
Click to expand...
Click to collapse
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Aldo101t said:
look at the zip file you download (openrecovery twrp-2.5.0.0-m7wls.img) m7wls tells you its for sprint.or m7spr whatever
there is a new version 2.6.0.1 but i don't know if it still has bugs or not, i'd stay at 2.5.0.0
Click to expand...
Click to collapse
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
mzel said:
I do not have a separate file. I think my TWRP came as part of some bigger ( root, recovery, permissions) package. I would think it was the Sprint version, but I keep having slight problems - those system apps try reboot after install, but in my case they do not. I have to boot manually, and after each recovery reboot I get a "reboot error notification". Can this be related?
Click to expand...
Click to collapse
that error is nothing don't worry about it, if you install a custom rom(make sure it's for sprint)that will go

[Q] Rooting problems

Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Kdenery said:
Hello XDA I'm new to these forums but i'm hoping you can help me out.
So basically I was following a youtube video I was linked to by a guide on here on how to root my One. and everything was going smoothly and then i got to the stage where i was to boot into recovery mode so i could load into twrp. But what happens on my phone now is the loading screen for recovery mode where it says for developers only ect. will just hang there for a while then the phone will shut off and boot back into regular mode. could use some help. I wouldn't mind resetting and starting fresh if that's what's needed im just not sure how to. thank you guys!
Click to expand...
Click to collapse
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Aldo101t said:
read this: http://forum.xda-developers.com/showthread.php?t=1435228
you will need to reflash recovery using fastboot/adb
Click to expand...
Click to collapse
first problem, how do i select charge only? and second when i try the first command code posted it just wouldn't work and when i tried it while the phone was slected on fastboot usb (just incase that would work) it said no device.
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Kdenery said:
Ok i figured it out i did everything in that thread. the same thing is happening. it just says entering recovery then restarts in normal mode.
Click to expand...
Click to collapse
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
If you are unlocked already, watch this https://www.youtube.com/watch?v=rRkAHw_GmIs&feature=youtube_gdata_player
Sent from my HTCONE using Tapatalk 4 Beta
Aldo101t said:
do you have sdk tools installed on your computer.
make sure usb debugging is on, apperently you do.
did you put the recovery image in the folder where fastboot is then run cmd(as administrator) and cd to that folder(example/:cd c:/Program Files/Android/android-sdk/platform-tools or where ever you have it)then adb reboot bootloader>enter----Then fastboot flash recovery(name of recovery image).img>enter--- then type fastboot reboot recovery
Click to expand...
Click to collapse
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Kdenery said:
yes. the problem is that it just stalls out on the entering recovery screen. with the htc logo and motto in the middle.
Click to expand...
Click to collapse
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Aldo101t said:
which recovery are you installing if its twrp v2.6.0.0 try 2.5.0.0 there was a bug in the 2.6 don't know if they fixed it yet.
Click to expand...
Click to collapse
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Kdenery said:
I tried this yesterday after installing 2.6.0.1 when the problem first happened. then i tried 2.6.0.0 then 2.5.0.0 the problem never went away and today i tried clockwork recovery. same thing. do i need to delete the images i've flashed onto it? if no how?
Click to expand...
Click to collapse
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Aldo101t said:
no i wouldn't think you do, it just overwrites the other, you're sure your bootloader is unlocked, check in settings under development option to make sure debugging is on.man you got me stumped here.
Click to expand...
Click to collapse
I retried the whole process once more and made sure usb debugging was on and its just frozen again.
bigdaddy619 said:
Are you typing "fastboot erase cache" without the quotes after you flash the recovery?
Click to expand...
Click to collapse
Just tried and made sure to do this. same problem.
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Kdenery said:
Perhaps i'm just being extremely retarded. I am unlocked but not rooted, i thought this was how to get rooted. but maybe im just far off.
Click to expand...
Click to collapse
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Aldo101t said:
NO, you are NOT retarded, you install recovery, then su to get root, for all intent and purposes you're doing it all right, just can't figure out why it's not working, one more redundant question, you have fastboot under power settings disabled?? Just tryin to cover all the bases
you are installing the recovery for the m7wls(m7spr)?
Click to expand...
Click to collapse
fast boot is not checked. and i think/hope so, how do i check that?
Kdenery said:
fast boot is not checked. and i think/hope so, how do i check that?
Click to expand...
Click to collapse
in settings under power scroll to the bottom fastboot is there.
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Kdenery said:
Sorry i guess i phrased that wrong. i'm sure fastboot is unchecked, i was asking about the second part of your post, about "you are installing the recovery for the m7wls(m7spr)?"
Click to expand...
Click to collapse
what exactly is the zip you're using,should be something like(fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img
I've tried
cwm-recovery-vivow
openrecovery-twrp-2.5.0.0-m7
openrecovery-twrp-2.6.0.0-m7
openrecovery-twrp-2.6.0.0-m7wls
openrecovery-twrp-2.6.0.1-m7
recovery-clockwork-6.0.3.2-m7spr
recovery-clockwork-touch-6.0.3.3-m7spr

[Q] HTC One (M7) Bricked???

Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
As long as it boots into Recovery its not bricked. Do you have the HTC Driver installed on your computer?
Android Revolution HD 53 requires min. TWRP 2.6.3.3. Your version is too old.
foxgre said:
Hello. I have the following problem. I friend of mine that I've sold him my old rooted Htc One tried to make 4.4. kitkat
He tried to install
Android_Revolution_HD-One-53.0zip
BUT I don't know how he managed to stuck his phone.The problem is when I am power on the phone it shows the white HTC screen with the red letters "this build is for development purpose only..." after a while reboots in TWRP v2.5.0.0
And that's it , I cannot do anything because my PC won't recognize it via USB cable.
Any suggestions?
(excuse me for my English, with love from Greece )
Click to expand...
Click to collapse
From recovery go to fastboot connect phone to pc.
It must be recognized.
Then flash boot.img which is in the Revolution.zip.
Then install the rom via recovery.
Remember for unlock and not s-off users the boot.img must be flashed befor flashing a rom.zip.
Sent by myself, without help )
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
SAME problem (or pretty similar) here
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
foxgre said:
i am doing as you say, but it's not recognized.
I only get a message android phone, not installed properly
Click to expand...
Click to collapse
Duwie_80 said:
SAME problem (or pretty similar) here, trying to instal ARHD61.1... I don't know how did I screw up this so much...
My bootloader is TAMPERED, UNLOCKED, S-On. Recovery TRWP (2.7) launches but... many things don't work.
First thing I have to mention is that I didn't forget to enable debugging before all this started (and now I can't launch android to do it).
My HTC drivers should be up-to-date, as I installed yesterday HTC sync 3.00.52...
In bootloader, if I type "fastboot devices" I get "FA34HW903605 fastboot", and "fastboot reboot.bootloader" does what it is expected to do...
In recovery, "adb push" tells me "error: device not found".
Can someone help me? If you need more details, just ask. Thanks
Click to expand...
Click to collapse
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
nkk71 said:
can you guys check out FAQ #2 in my guide: http://forum.xda-developers.com/showthread.php?t=2541082 if that's the problem you have
Click to expand...
Click to collapse
Let me try and I'll tell you later. I also think it's a matter of drivers, so I was downloading and re-installing it... Thank you for your help
-------------------------------------------------- UPDATE --------------------------------------------------------------------------------
Well, I followed your steps (LET ME THANK YOU FOR MAKING THAT GUIDE) and now the device is "My HTC" as you show.
Something has changed:
If I type "adb devices" (in PC) when phone is in fastboot, the listing is void (before I got "FA34HW903605 fastboot"), and if I do the same while phone is in recovery, I get the mentioned "FA34HW903605 recovery".
In Windows7 I don't see "My HTC" as a conventional USB storage or Memory of a Camera (should it be?)
I've managed to ADB PUSH a ROM (ARHD) in recovery, but now I get an error message: "Unable to mount '/data' " and "Unable to mount internal storage " then FAILED. Now I'll try flashing a new recovery...
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Duwie_80 said:
WOW WOW WOW!! It was enough for me, sir
1st) Solve comunnication issues as shown in FAQ #2 here
2nd) Solve TWRP recovery mount issues by:
2.a) Installing any other (clockwork) in fastboot using One All In One Kit (eaaaasy)
2.b) Formatting cache, system, data partitions
2.c) Installing TWRP again using One All In One Kit (Android Revolution REQUIRES this recovery)
2.d) Sending the ROM ('adb push your_rom.zip /sdcard/wherever_you_want_it')
2.e) Installing it from TWRP recovery.
An that was all. THANKS A LOT nkk71; without your help I still would be here trying to figure out what's broken... Thanks.
Click to expand...
Click to collapse
no problem, glad to be of help
remember for most 4.4 ROMs, (for m7_u/ul) TWRP 2.6.3.3 (or higher) is recommended at the moment.
though you should be good by downloading it, then checking MD5 to make sure the download isnt corrupt (that site doesnt work with download managers), then:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery and push the rom
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
you're really not giving any details... so you hear a sound... what does Windows Device Manager show??
foxgre said:
Thank you all for your support, but still the problem remains.
I have installed HTC Drivers and when i connect the HtcOne i can hear the USB beep from windows but i cannot open the phone like a drive.
In other words i cannot add files to the phone :crying::crying:
Click to expand...
Click to collapse
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Duwie_80 said:
It wont be so easy, I'm afraid. Even if comunication issues are solved, you won't be able to copy your ROM using windows file manager, opening the phone like a conventional drive...
You have to install "ADB" in your PC (search in HTC ONE subforums, there's a lot of info about ADB pusing (=copying) ROMS) and use it to copy your ROM. One advice: while "pushing" the ROM, be patient: it takes a long time. When your ROM is "pushed", just install it in recovery and... that's it!!
I think here you have a good starting point.
Click to expand...
Click to collapse
Thanks again i am already looking for it.
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
foxgre said:
AT LAST!!!
I've managed to push the rom.
Thank you very much for your help
Click to expand...
Click to collapse
Hey, congratulations!! :good::good::good:

HTC One (M7) Sprint Might be Bricked Help?

Hello
Currently my phone is useless, I am blaming myself but somewhat of the ROM I used before this all happened.
For starters, my bootloader is unlocked and s-on. I successfully installed TWRP and rooted using SuperSU. I wanted to try out the custom ROM ViperOne. It installed perfectly fine without any errors. But when I rebooted the phone I am greeted with the lockscreen with no service (x by the bars) and when I go to unlock the phone it goes to a white screen with the HTC logo in the center. It will continue to stay at this screen till it reboots again and does the same thing.
At this point I am frustrated and followed this guide http://forum.xda-developers.com/showthread.php?t=2503646 to revert back to Stock. I was able to do every step correctly besides the flashing of the radio and pushing the Stock_Rom on the phone.
I was able to install the stock rom by putting it on my internal storage and flashing it that way, but still no luck with the radio. But now the Stock_Rom is doing the exact same thing as the Viper, Whitescreen with HTC. Plus it is constantly saying "Unfortunately Phone has stopped" making it unusable.
If someone could please help me out or direct me to another tut to follow I will appreciate it very much. Because at this point I am to believe that I bricked my device and I am unaware if I am able for an upgrade anytime soon.
Thank you for you time.
A little update.
I am not starting to think this whole problem has to do with my radio, simply I do not have 1. How do I get this working again?
Another update.
I tried to follow this guide http://forum.xda-developers.com/showthread.php?t=2250904 (Very helpful btw :good
But still no luck, it froze me at the black screen with HTC and no loading bar.
I just want to be able to use my phone again :crying:
Everything you need is in the first link you posted.
BD619 said:
Everything you need is in the first link you posted.
Click to expand...
Click to collapse
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
kavinsky_ep said:
Thank you for your response.
Like I sad, I tried that link already but with no luck. I could be doing something wrong, but I am following word for word.
Click to expand...
Click to collapse
Latest radio can be found HERE
BD619 said:
Latest radio can be found HERE
Click to expand...
Click to collapse
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
kavinsky_ep said:
I've downloaded 1.00.20.1108 and I am trying to flash it using fastboot flash zip radio.zip (I renamed it to type it in easier).
But every time I press enter it does signature checking... then it says FAILD (remote: 12 signature verify fail)
Any ideas?
Click to expand...
Click to collapse
Flash in recovery like the instructions say lol
BD619 said:
Flash in recovery like the instructions say lol
Click to expand...
Click to collapse
Ok, thank you again. I will try this. I hope to god it works
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
kavinsky_ep said:
Sigh. Another problem
After performing the wipe with TWRP and then i type in the cmd adb push nameofrom.zip /sdcard/ but I get the following error in cmd.
adb server is out of date. killing...
* daemon started successfully *
I am confused by this because my drivers are up to date, unless this is a different problem. Any ideas?
Click to expand...
Click to collapse
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
BD619 said:
It's normal for it to say that.
Do you get your serial number returned when you type
adb devices
Click to expand...
Click to collapse
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
kavinsky_ep said:
Hey! I fixed it, I was able to quickly put the radio.zip into my internal storage before the phone could freak out. Went into TWRP and flashed that *****! IT WORKS!
No more custom ROMS for me, I'll just stick to rooting and keeping stock rom.
I would like to thank you for helping me throughout this, I really appreciate this. :good:
btw, if I were unable to do it the way I did, how would I fix it to work with the adb push command?
Click to expand...
Click to collapse
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
BD619 said:
Depends what is causing the adb to be wonky most likely it's a driver issue.
Drivers install while booted to OS,Recovery,and fastboot.
BTW when you were doing the adb push romname.zip /sdcard/ were you in recovery or OS?
You are very welcome btw
Click to expand...
Click to collapse
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
kavinsky_ep said:
I was in my recovery, TWRP. and using my computer with the CMD. Or by OS do you mean my phone OS. Because I was unable to use my Phone due to the radio not being there.
Click to expand...
Click to collapse
Most likely the drivers were not installed properly while booted to twrp...there are instructions in my guide that will show you how to install them properly.
I was wondering if the phone was booted to OS.
Get yourself S-OFF, and many flashing woes disappear. I have soft-bricked my phone with a Viper myself. You have to be sure you install the correct carrier version and think twice about installing kernels in ViperHub (or whatever they call it). If you install a GSM anything to your Sprint phone, your radio will go away. An RUU will fix this though. Windows 8 does not play well with ADB on our phones, either.
Sent from my One using Tapatalk
I'm having the SAME exact problems as you. Went to flash Viper rom and just get stuck on the white screen with the HTC logo. Glad I'm not the only one!
Hopefully I'll be able to fix mine as well!

Categories

Resources