Hello everyone, im new to these forums (and new to android) so nice to meet you all!
so i got this htc one m7 from a friend, he said he deleted the internal storage and he cant boot up android anymore.
thought might as well give it a try to fix it.
i tried everything in this thread http://forum.xda-developers.com/showthread.php?t=2258809 but it didnt work.
im getting a fail on the last step when it checks signatures.
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
after some surfing on the forums i found out that i need S-OFF... and mine is S-ON but i cant seem to get if off,
the phone bootloader shows this:
**tampered**
**relocked**
m7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
radio-4A22.3263.03
openDSP-v32.120.274.0909
OS-3.63.111.3
eMMC-boot 2048MB
nov27 2013, 19:12:38.0
is there any way to get this phone working again?
thanks
kn!ves said:
Hello everyone, im new to these forums (and new to android) so nice to meet you all!
so i got this htc one m7 from a friend, he said he deleted the internal storage and he cant boot up android anymore.
thought might as well give it a try to fix it.
i tried everything in this thread http://forum.xda-developers.com/showthread.php?t=2258809 but it didnt work.
im getting a fail on the last step when it checks signatures.
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
after some surfing on the forums i found out that i need S-OFF... and mine is S-ON but i cant seem to get if off,
the phone bootloader shows this:
**tampered**
**relocked**
m7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
radio-4A22.3263.03
openDSP-v32.120.274.0909
OS-3.63.111.3
eMMC-boot 2048MB
nov27 2013, 19:12:38.0
is there any way to get this phone working again?
thanks
Click to expand...
Click to collapse
you dont need s-off, however, if you want s-off it would be advised whilst your on a low HBOOT before you update, but thats a different story.
your re-locked, so do you know if it has a custom recovery on it, or a custom rom, or is it 100% stock, to be sure, unlock your bootloader, because if it is running anything custom, it wont boot with a re-locked bootloader, unlock here:
http://www.htcdev.com/bootloader
just follow the instructions and report back when done, it will give you some adb and fastboot files, keep those, you'll need them and will also teach you how to use them if you dont know. :good:
Seanie280672 said:
you dont need s-off, however, if you want s-off it would be advised whilst your on a low HBOOT before you update, but thats a different story.
your re-locked, so do you know if it has a custom recovery on it, or a custom rom, or is it 100% stock, to be sure, unlock your bootloader, because if it is running anything custom, it wont boot with a re-locked bootloader, unlock here:
just follow the instructions and report back when done, it will give you some adb and fastboot files, keep those, you'll need them and will also teach you how to use them if you dont know. :good:
Click to expand...
Click to collapse
The phone was rooted and was still stock rom.
i just did all the steps to unlock the bootloader. ive got the unlock_bin but i dont see any adb and fastboot files?
just tried to flash it again, now i got a different error: FAILED: <remote: 32 header error>
kn!ves said:
The phone was rooted and was still stock rom.
i just did all the steps to unlock the bootloader. ive got the unlock_bin but i dont see any adb and fastboot files?
just tried to flash it again, now i got a different error: FAILED: <remote: 32 header error>
Click to expand...
Click to collapse
how are you trying to flash if you dont have any adb and fastboot files ?
ive attached mine below, just unzip and put your unlock code bin file in the same folder, then try and flash
Seanie280672 said:
how are you trying to flash if you dont have any adb and fastboot files ?
Click to expand...
Click to collapse
just tried these steps again haha http://forum.xda-developers.com/showthread.php?t=2258809
where can i get adb and fastboot files?
thanks
kn!ves said:
just tried these steps again haha http://forum.xda-developers.com/showthread.php?t=2258809
where can i get adb and fastboot files?
thanks
Click to expand...
Click to collapse
attached the files you need above, if you had of continued the unlock process on the HTC site, they would of supplied you with the files and guided you to use them.
Seanie280672 said:
attached the files you need above, if you had of continued the unlock process on the HTC site, they would of supplied you with the files and guided you to use them.
Click to expand...
Click to collapse
i did all the steps to unlock the phone, guess i mised those then. i downloaded your adb and fastboot. those files were already included in my Hasoons AIO Toolkit download.
this probally is a stupid question.... but what do i do now? haha
thanks
kn!ves said:
i did all the steps to unlock the phone, guess i mised those then. i downloaded your adb and fastboot. those files were already included in my Hasoons AIO Toolkit download.
this probally is a stupid question.... but what do i do now? haha
thanks
Click to expand...
Click to collapse
Is your bootloader unlocked now ? does the phone boot ? what do you want to do, custom rom or back to stock ?
Seanie280672 said:
Is your bootloader unlocked now ? does the phone boot ? what do you want to do, custom rom or back to stock ?
Click to expand...
Click to collapse
in the bootloader it now says unlocked. the phone can boot into the bootloader or in Team win recovery project. i just want the phone working again be it stock or custom rom. you know any good custom roms?
thanks
kn!ves said:
in the bootloader it now says unlocked. the phone can boot into the bootloader or in Team win recovery project. i just want the phone working again be it stock or custom rom. you know any good custom roms?
thanks
Click to expand...
Click to collapse
READ THE WHOLE POST BEFORE TRYING ANY OF THIS AS IVE ADDED A BIT TO THE BOTTOM
what you need to do is flash TWRP 2.8.5.0 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and create a simple backup, just something like the boot, then plug your phone into the computer, whilst its still in recovery mode, that recovery supports MTP so your internal storage should open up on your computer, if it doesnt, you have a driver problem, but if it does, then navigate to TWRP/Backup/Phone serial number/todays date and some other details, delete the backup files out of there and place the files inside this zip in there instead, files only not folders: https://www.androidfilehost.com/?fid=23622183712459333
unplug your phone and restore that backup.
once restored, restart your phone and just do a basic setup.
then put this on your internal storage and again boot into recovery mode and flash it: https://www.androidfilehost.com/?fid=23622183712459512
once finished, do a full restart of the phone, your now nearly full stock, one last step, your need to flash the firmware which is here: https://www.androidfilehost.com/?fid=95747613655045066 once downloaded just name it to firmware for ease and put it in the same folder as adb and fastboot on your computer, reboot your phone to the bootloader and lock the bootloader (required to flash firmware as you are s-on), issue these commands.
Code:
fastboot oem lock
fastboot reboot-bootloader[I] (should now say relocked at the top)[/I]
fastboot oem rebootRUU[I] (screen turn black with silver HTC logo)[/I]
fastboot flash zip firmware.zip [I](failed is normal the first time, it will say please flush again) soooooo[/I]
fastboot flash zip firmware.zip
[I]as long as it says successful at the end this time your good to go, if not, report back here before the next command, if all is ok then:[/I]
fastboot reboot-bootloader
fastboot reboot
when you restart your phone will be full stock and you should now be able to update, recommended as your firmware is quite old, however, I would recommend before updating that you try and get s-off, for this you will need to use rumrunner s-off tool, you can find it here plus the instructions: http://rumrunner.us/ (you might want to try this after: "once restored, restart your phone and just do a basic setup." before flashing the firmware and preload data part)
Seanie280672 said:
READ THE WHOLE POST BEFORE TRYING ANY OF THIS AS IVE ADDED A BIT TO THE BOTTOM
what you need to do is flash TWRP 2.8.5.0 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and create a simple backup, just something like the boot, then plug your phone into the computer, whilst its still in recovery mode, that recovery supports MTP so your internal storage should open up on your computer, if it doesnt, you have a driver problem, but if it does, then navigate to TWRP/Backup/Phone serial number/todays date and some other details, delete the backup files out of there and place the files inside this zip in there instead, files only not folders: https://www.androidfilehost.com/?fid=23622183712459333
unplug your phone and restore that backup.
once restored, restart your phone and just do a basic setup.
then put this on your internal storage and again boot into recovery mode and flash it: https://www.androidfilehost.com/?fid=23622183712459512
once finished, do a full restart of the phone, your now nearly full stock, one last step, your need to flash the firmware which is here: https://www.androidfilehost.com/?fid=95747613655045066 once downloaded just name it to firmware for ease and put it in the same folder as adb and fastboot on your computer, reboot your phone to the bootloader and lock the bootloader (required to flash firmware as you are s-on), issue these commands.
Code:
fastboot oem lock
fastboot reboot-bootloader[I] (should now say relocked at the top)[/I]
fastboot oem rebootRUU[I] (screen turn black with silver HTC logo)[/I]
fastboot flash zip firmware.zip [I](failed is normal the first time, it will say please flush again) soooooo[/I]
fastboot flash zip firmware.zip
[I]as long as it says successful at the end this time your good to go, if not, report back here before the next command, if all is ok then:[/I]
fastboot reboot-bootloader
fastboot reboot
when you restart your phone will be full stock and you should now be able to update, recommended as your firmware is quite old, however, I would recommend before updating that you try and get s-off, for this you will need to use rumrunner s-off tool, you can find it here plus the instructions: http://rumrunner.us/ (you might want to try this after: "once restored, restart your phone and just do a basic setup." before flashing the firmware and preload data part)
Click to expand...
Click to collapse
When i try to make a backup i get the error E:unable to mount '/cache'
E:unable to mount '/data'
E:unable to mount internal storage
and also when i connect the phone to my pc it says drivers are correctly installed but i cant see or open the internal storage.
thanks
kn!ves said:
When i try to make a backup i get the error E:unable to mount '/cache'
E:unable to mount '/data'
E:unable to mount internal storage
and also when i connect the phone to my pc it says drivers are correctly installed but i cant see or open the internal storage.
thanks
Click to expand...
Click to collapse
to clear those errors, in TWRP recovery select wipe - format data, this will wipe the entire phone, then reboot back into recovery.
The internal storage popping up on your computer only works when you are booted into recovery (main recovery screen only) and only with TWRP recovery 2.8.5.0 or 2.8.4.0.
Seanie280672 said:
to clear those errors, in TWRP recovery select wipe - format data, this will wipe the entire phone, then reboot back into recovery.
The internal storage popping up on your computer only works when you are booted into recovery (main recovery screen only) and only with TWRP recovery 2.8.5.0 or 2.8.4.0.
Click to expand...
Click to collapse
*after the format i could indeed make a backup
** restoring backup now, took a few tries to get the good TWRP..
how do i flash the M7_UL_preload_4.20.111.21_(flashbar)?
kn!ves said:
*after the format i could indeed make a backup
ok, i have TWRP v2.6.3.0. in my computer the phone show up as drive E: and looks like a cd-drive (cant open it) is there any other way i can copy the backup files from my computer to phone? or should i skipp that part?
thanks
Click to expand...
Click to collapse
How about updating the recovery to the one specified?
kn!ves said:
*after the format i could indeed make a backup
** restoring backup now, took a few tries to get the good TWRP..
how do i flash the M7_UL_preload_4.20.111.21_(flashbar)?
Click to expand...
Click to collapse
Are you using twrp 2.8.5.0 now ?
once you have restored the backup, boot up your phone, do a basic setup, plug your phone into the computer and copy the preload zip file to your internal storage, reboot back to recovery, select install, select the preload zip from the list and swipe to install.
Seanie280672 said:
Are you using twrp 2.8.5.0 now ?
once you have restored the backup, boot up your phone, do a basic setup, plug your phone into the computer and copy the preload zip file to your internal storage, reboot back to recovery, select install, select the preload zip from the list and swipe to install.
Click to expand...
Click to collapse
almost there, flashing firmware now, first time it said failed <remote: 90 hboot pre-update! please flush image again immediatly>
so i did fastboot flash zip firmware.zip again but now it just hangs on sending "zip"
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.475s
thanks
EDIT: after unlpugging once it worked. phone is now rebooting
kn!ves said:
almost there, flashing firmware now, first time it said failed <remote: 90 hboot pre-update! please flush image again immediatly>
so i did fastboot flash zip firmware.zip again but now it just hangs on sending "zip"
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 10.475s
thanks
EDIT: after unlpugging once it worked. phone is now rebooting
Click to expand...
Click to collapse
you will be full stock now, connect to your wifi and should beable to get all updates to the latest android.
Hit thanks a couple of times please. :good:
Seanie280672 said:
you will be full stock now, connect to your wifi and should beable to get all updates to the latest android.
Hit thanks a couple of times please. :good:
Click to expand...
Click to collapse
Thank you very mutch for your help and parience
im now turning S-OFF. btw with rumrunner s-off, will i also be able to install cracked apps on it?
thanks.
kn!ves said:
Thank you very mutch for your help and parience
im now turning S-OFF. btw with rumrunner s-off, will i also be able to install cracked apps on it?
thanks.
Click to expand...
Click to collapse
If you get s-off, it wil be way way easier to fix, no need to go through all that stuff again, just change cid, mid and run and RUU.
Related
I have an AT&T turned into GPe. After it finished downloading the 4.4 OTA it restarted into TWRP 2.6.3.0 and it launched the Google word and a blue screen appeared. I already tried through TWRP flashing from USB-OTG but I get Updating partition details... and an inmediate Failed. I tried also wipe cache/dalvik and SD data but same sth. Also tried with ADB Sideload but i get error: closed and if I get to copy stock 4.4 or 4.3 through ADB Sideload it gets to 100% on PC but inmediately appears on TWRP Failed. Please help me I'm going crazy.
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSP-v31.120.274.0617
OS-3.07.1700.1
eMMC-boot 2048MB
Hope you can help me, thanks for you support!
philohtc said:
I have an AT&T turned into GPe. After it finished downloading the 4.4 OTA it restarted into TWRP 2.6.3.0 and it launched the Google word and a blue screen appeared. I already tried through TWRP flashing from USB-OTG but I get Updating partition details... and an inmediate Failed. I tried also wipe cache/dalvik and SD data but same sth. Also tried with ADB Sideload but i get error: closed and if I get to copy stock 4.4 or 4.3 through ADB Sideload it gets to 100% on PC but inmediately appears on TWRP Failed. Please help me I'm going crazy.
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-GOOGL001
HBOOT-1.54.0000
RADIO-4A.18.3263.15
OpenDSP-v31.120.274.0617
OS-3.07.1700.1
eMMC-boot 2048MB
Hope you can help me, thanks for you support!
Click to expand...
Click to collapse
i think you need to be stock to run the OTA my mate had same problem.
philohtc said:
After it finished downloading the 4.4 OTA it restarted into TWRP 2.6.3.0
OS-3.07.1700.1
Click to expand...
Click to collapse
You need to have "stock recovery" installed for OTA to work properly, TWRP won't do it.
nkk71 said:
You need to have "stock recovery" installed for OTA to work properly, TWRP won't do it.
Click to expand...
Click to collapse
Could you please give me a detailed description of the steps I should take? Can I flash the ROM from stock recovery? How do I copy the OTA to the SD-card if PC only recognizes it only by fastboot or adb sideload, and in sideload apparently after copying it when it gets to 100% it says Failed. Thanks
I have the exact same problem. I am going crazy. I am used to Nexus devices and if I get an error as this one, I just flash the factory image. In this case is extremely more complex than that. I had Stock 4.3. Suddenly my device showed to get the OTA, TWRP started to flash it and now I can't use it. I have S-ON. Blueish/Greenish screen every time I turn it on. What would be the steps to flash stock "image" and start all over again? Please help, I've read too much and no answer.
philohtc said:
Could you please give me a detailed description of the steps I should take? Can I flash the ROM from stock recovery? How do I copy the OTA to the SD-card if PC only recognizes it only by fastboot or adb sideload, and in sideload apparently after copying it when it gets to 100% it says Failed. Thanks
Click to expand...
Click to collapse
custom recovery (ie CWM or TWRP) won't be able to install the OTA, and you don't really need to copy the OTA to PC.
the reason it's not installing, is that when it reboots to TWRP, it is actually expection "stock recovery", which can complete the process
you flash "stock recovery", using bootloader/FASTBOOT USB:
fastboot flash recovery <name of stock recovery>.img
fastboot erase cache
fastboot reboot
and then the OTA will install properly, no need to do it manually.
your "OS-3.07.1700.1", so you need the stock recovery for that, I'm gonna look a litlle later and see if i can find it for you.....
Hit thanks if i've helped
nkk71 said:
custom recovery (ie CWM or TWRP) won't be able to install the OTA, and you don't really need to copy the OTA to PC.
the reason it's not installing, is that when it reboots to TWRP, it is actually expection "stock recovery", which can complete the process
you flash "stock recovery", using bootloader/FASTBOOT USB:
fastboot flash recovery <name of stock recovery>.img
fastboot erase cache
fastboot reboot
and then the OTA will install properly, no need to do it manually.
your "OS-3.07.1700.1", so you need the stock recovery for that, I'm gonna look a litlle later and see if i can find it for you.....
Hit thanks if i've helped
Click to expand...
Click to collapse
Please friend! The sooner the better, could you give me the link to the recovery I should flash. I wiped DATA and Cache, OTA isn't deleted? Thanks
philohtc said:
Please friend! The sooner the better, could you give me the link to the recovery I should flash. I wiped DATA and Cache, OTA isn't deleted? Thanks
Click to expand...
Click to collapse
Here you go:
stock_recovery_3.07.1700.1.img 7.5 MB
https://mega.co.nz/#!bZc1zDyJ!aiAvuFpBD2WEvnoWdQVN4xvfRy0d4CxA_s-0a1mz_sw
MD5: 32cb0727fa5db04f12b7704432edd904
fastboot flash recovery stock_recovery_3.07.1700.1.img
fastboot erase cache
fastboot reboot
Download & install OTA, should be good now.
nkk71 said:
Here you go:
stock_recovery_3.07.1700.1.img 7.5 MB
https://mega.co.nz/#!bZc1zDyJ!aiAvuFpBD2WEvnoWdQVN4xvfRy0d4CxA_s-0a1mz_sw
MD5: 32cb0727fa5db04f12b7704432edd904
fastboot flash recovery stock_recovery_3.07.1700.1.img
fastboot erase cache
fastboot reboot
Download & install OTA, should be good now.
Click to expand...
Click to collapse
Sorry for my noob question, I already have downloaded the 4.4 ROM. Once I flash recovery it will start up with android 4.3? Steps to install? I'll try this as soon as I get home, I really appreciate all your help bro. Really thank you very much!
philohtc said:
Sorry for my noob question, I already have downloaded the 4.4 ROM. Once I flash recovery it will start up with android 4.3? Steps to install? I'll try this as soon as I get home, I really appreciate all your help bro. Really thank you very much!
Click to expand...
Click to collapse
sorry, didnt understand, i thought your ROM (whatever it is, let's say 4.3), received the OTA notification but could install properly cause of TWRP -> correct?? -> if yes, then flashing the "stock recovery" will allow the OTA installation to complete successfully,
or am i missing something?
nkk71 said:
sorry, didnt understand, i thought your ROM (whatever it is, let's say 4.3), received the OTA notification but could install properly cause of TWRP -> correct?? -> if yes, then flashing the "stock recovery" will allow the OTA installation to complete successfully,
or am i missing something?
Click to expand...
Click to collapse
That is my case and from what I've read is the same as his. I can't try it because I am at work right now, but as I cannot boot, if I install stock recovery, how can I run the OTA? In recovery "Apply update from zip"? Thanks!
sotnasnauj said:
That is my case and from what I've read is the same as his. I can't try it because I am at work right now, but as I cannot boot, if I install stock recovery, how can I run the OTA? In recovery "Apply update from zip"? Thanks!
Click to expand...
Click to collapse
but the OP, is able to boot up, you are not? seems like a different issue
nkk71 said:
but the OP, is able to boot up, you are not? seems like a different issue
Click to expand...
Click to collapse
I turn on my phone and get the Google logo, then the screen turns blue. I can get to recovery and fastboot. At the time being I have TWRP, just as the first message of the post. but my phone won't boot into Android.
sotnasnauj said:
I turn on my phone and get the Google logo, then the screen turns blue. I can get to recovery and fastboot. At the time being I have TWRP, just as the first message of the post. but my phone won't boot into Android.
Click to expand...
Click to collapse
are you s-on or s-off? (sorry if you've already answered that, but i'm not keeping track )
nkk71 said:
are you s-on or s-off? (sorry if you've already answered that, but i'm not keeping track )
Click to expand...
Click to collapse
S-On.. I know if I were in S-Off would be easier, but from what I've read I have to boot to get S-Off. (Do not worry, ask me anything, I am the one who is grateful)
sotnasnauj said:
S-On.. I know if I were in S-Off would be easier, but from what I've read I have to boot to get S-Off. (Do not worry, ask me anything, I am the one who is grateful)
Click to expand...
Click to collapse
4.4 seems to be having lot's of issues with S-On. Do you have a real GPE or are using a custom ROM, if you're using a custom ROM, then it will NOT work with S-On at this time, so better to go back to 4.3.
Hit the thanks button if i've helped
nkk71 said:
4.4 seems to be having lot's of issues with S-On. Do you have a real GPE or are using a custom ROM, if you're using a custom ROM, then it will NOT work with S-On at this time, so better to go back to 4.3.
Hit the thanks button if i've helped
Click to expand...
Click to collapse
I do have a real GPE. So what can I do to restore or get back to 4.3? How can I flash a "factory image"?
Thanks
EDIT: I just flashed the stock recovery but there is nothing I can do in it.
shouldn't need to drop to 4.3 if you have a real GPE
flash CWM.
wipe cache
then restore this nandroid i made of stock 4.4 (extract the zip and copy the folder to /data/media/clockworkmod/backup/):
https://mega.co.nz/#!TMlgWLDJ!ZfFlcxcRkebpb3cciULnlTf4GMJfy4grwOLi-Ied3Tg
Then flash this untouched firmware.zip from fastboot:
http://www.mediafire.com/download/am4jx7jbx2niilv/4.4 firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 firmware.zip
fastboot reboot
that should get you to 100% stock and future OTA should work.
sotnasnauj said:
I do have a real GPE. So what can I do to restore or get back to 4.3? How can I flash a "factory image"?
Thanks
EDIT: I just flashed the stock recovery but there is nothing I can do in it.
Click to expand...
Click to collapse
ipfreelytech said:
shouldn't need to drop to 4.3 if you have a real GPE
flash CWM.
wipe cache
then restore this nandroid i made of stock 4.4 (extract the zip and copy the folder to /data/media/clockworkmod/backup/):
https://mega.co.nz/#!TMlgWLDJ!ZfFlcxcRkebpb3cciULnlTf4GMJfy4grwOLi-Ied3Tg
Then flash this untouched firmware.zip from fastboot:
http://www.mediafire.com/download/am4jx7jbx2niilv/4.4 firmware.zip
fastboot oem rebootRUU
fastboot flash zip 4.4 firmware.zip
fastboot flash zip 4.4 firmware.zip
fastboot reboot
that should get you to 100% stock and future OTA should work.
Click to expand...
Click to collapse
I'll try it at home, I am really thankful I am sure it will work! THANKSS
ipfreelytech said:
shouldn't need to drop to 4.3 if you have a real GPE
flash CWM.
wipe cache
then restore this nandroid i made of stock 4.4 (extract the zip and copy the folder to /data/media/clockworkmod/backup/):
https://mega.co.nz/#!TMlgWLDJ!ZfFlcxcRkebpb3cciULnlTf4GMJfy4grwOLi-Ied3Tg
...
Click to expand...
Click to collapse
I'm closely following this post because I have the same problem, GPE S-ON, bricked becasue non stock recovery OTA update
I flashed stock recovery but if the phone won't boot up, how can I "(extract the zip and copy the folder to /data/media/clockworkmod/backup/):"???
Can I connect the phone to the PC with CWM and copy the files? or how can I do it if I can't get the phone to boot up?
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
ClydeWinux said:
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.33250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
Click to expand...
Click to collapse
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Harish_Kumar said:
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Click to expand...
Click to collapse
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
ClydeWinux said:
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
Click to expand...
Click to collapse
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Harish_Kumar said:
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Click to expand...
Click to collapse
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
ClydeWinux said:
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
Click to expand...
Click to collapse
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Harish_Kumar said:
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Click to expand...
Click to collapse
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
ClydeWinux said:
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
Click to expand...
Click to collapse
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
56562336461
Harish_Kumar said:
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
Click to expand...
Click to collapse
Everytime I tried to flash custom recovery (CWM/TWRP) in cmd it returns "remote: signature verify fail", I used command "fastboot flash recovery cwm.img". And now I tried to load up recovery from menu, and it's stuck on a 'dead-android-icon-with-exclamation-error' logo. @Harish_Kumar
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
I will get there said:
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
I will get there said:
Hi Xda
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
I will get there said:
Hi Xda
Forgive me for what you are about to read, as I have carried out some dumb ### noobness:
I was running Sinless 5.1Gpe rom (great rom) anyways I wanted to return to a sense based rom so decided to go for ARHD 40.2 fter reading a number of posts mentioning doing a complete wipe of the phone including SDCARD. I checked the process of pushing via adb and all seemed simple enough.
I initially did a test and it pushed the file, so then i carried out the complete wipe (no OS, no rom on sd card to flash). I then tried to push the rom and it failed. I tried a number of different ways sideload too.
I managed to get the rom to push in the end using the lastest TWRP of which it would not allow me to do rom failed to flash...
Now this is the stupid part, TWRP became unresponsive, and every time I tried to boot into recovery it would kick me out to the spash screen and bootloop. I did the fastboot erase cache without any success.
I managed to switch to CWM but could not mount anything so came across a post about switching to stock....This is the really stupid part. I flashed a stock recovery and also I now have a relocked bootloader.
Is this phone now bricked??
I have fastboot available
I am S-off
I can boot into stock recovery (Red triangle)
I cannot use ADB (device not recognised)
I cannot re unlock bootloader (tried twice and failed) - I will try again as it got to 4am and had to be up for work at 6am.
Any help really really apreciated.
Many thanks
Mick
Click to expand...
Click to collapse
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
solbirn said:
How did you unlock the first time? HTCDev or S-OFF?
Can you post the error you get when you try to unlock?
Click to expand...
Click to collapse
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
nkk71 said:
if you have s-off you should flash back a custom recovery:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY, and adb should be working again,
use this to unlock your phone: http://forum.xda-developers.com/showthread.php?t=2475914
there's also a handy Guru Bootloader Reset (flashable zip): http://forum.xda-developers.com/showthread.php?t=2527194
but it needs either CWM 6.0.3.2+, or TWRP 2.6.3.3+ to work.
or even "revone -u"
Click to expand...
Click to collapse
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
loughary said:
If you can get to the stock recovery press volume up then power button and quickly release both buttons and you should be in stock recovery. From here you should be able to follow any of the posted steps to flash a RUU back to pure stock.
Click to expand...
Click to collapse
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
I will get there said:
Hi thanks for your response, I initially HTCDev then rumrunner to gain s-off.
The error I get is:
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.
C:\Users\Michael\Desktop\Adb And Fastboot>fastboot flash unlocktoken Unlock_code
.bin
target reported max download size of 1514139648 bytes
error: cannot load 'Unlock_code.bin': No error
C:\Users\Michael\Desktop\Adb And Fastboot>
Hey thanks for your response
I cant flash custom recovery the error i get is similar to trying to unlock.(above)
I cannot also use that thread because I cannot access adb (even though my phone recognises fastboot in device manager, when I go to what is now stock recovery is disappears from device manager)
I have no OS so cannot open up emulator for revone.
Hey thanks for responding
I can get into stock android recovery(3e) it enters after notifying me that it failed to mount sd card 5 times then finishes with cannot mount sdcard (no such file or directory)
then finally write host_mode:0 done
any further suggestions?
Click to expand...
Click to collapse
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
nkk71 said:
You're getting "cannot load"? That just means the filename is wrong, as simple as that. If ur on Windows, check for .img.img (double extension)
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thanks @nkk71
I now have an unlocked bootloader
I have also now flashed CWM 6.0.4.5 however I still do not have adb available. The difference now is fastboot is recognised in device manager as before but when I boot into CWM instead of it dissapearing, it moves to 'other devices' one (with yellow exclamation) I know it did this before because of drivers not being installed/recognised but I have htc sync manager installed which in theory has installed the drivers??!
Anything else I can try without adb?
Again many thanks for your assistance, I see you in a number of threads helping people...top bloke!
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
I will get there said:
Further update
I downgraded my hboot back to 1.55 and now TRWP is now functioning, I have now pushed a rom to the phone, however flash fails due to "unable to mount to internal storage"
Is there a fix for this?
Many thanks
Click to expand...
Click to collapse
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Ivanovic said:
I suggest that you downgrade to Hboot 1.44, keep the bootloader locked and run the 1.28.401.7 RUU to be completely stock. Then its up to you whether you re staying stock or flashing sth custom.
Click to expand...
Click to collapse
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
IF you re flashing a 4.4 ROM then use TWRP 2.6.3.3 or latest CWM
IF you re flashing a 4.3/4.2 ROM then use TWRP 2.6.3.0 or older CWM
Link for the RUU http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
I will get there said:
Thanks @Ivanovic
I have since moved on a little further, i have now managed to push a rom via sideload, when i then go to flash it says:
Updating partion details....
E:unable to open zip file.
Error flashing zip /sdcard/sideload.zip
updating partition..details
failed
do you know a workaround this, if not could you direct me to a page with both hboot 1.44 and the RUU please
Click to expand...
Click to collapse
http://www.htc1guru.com/downloads/ruu-file-downloads/
I had to use the exe version to get it working when I had a similar issue.
Sent from my One using Tapatalk
Yes there is a fix. Install stock recovery. Go to bootloader and select factory reset. It will go to stock recovery and do it's thing and should go into a Bootloop . install custom recovery you should be good
Hi All
Just a quick note, to say all back up and running, thanks for all the respondants who helped.
I wanted add how i got it up and running, so if anyone has similar issues they can use it:
I believe the biggest culprit was the newest Firmware and TWRO 2.3.3.3 in which it did not want to load.
I downgraded by Hboot to firmware 3.xxx and then flashed TWRP 2.3.3.0 and it let me in instead of kicking me out to a bootloop.
I then had access to ADB sideload, which did not work for me in the 1st instance that led me to my problem, This i believe was due to not having the lastest SDK.(upgrade this).
Make sure the Rom you are pushing works well for that downgraded firmware i.e. a solid 4.3 based rom in my case.
Also to note I wiped my external SD card and was unable to mount this to flash, let TWRP sort this by doing a factory reset prior to flashing.
Hope this helps anyone who experienced similar symptoms to me.
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
ubas98 said:
Hello. im new here and i ive just bricked my phone , and i wana get back to stock RUU and i dont know whick RUU to download anny sollutions how to check what RUU do i need? Ps.sorry for my bad english. Anny help would be awesome
Click to expand...
Click to collapse
post the ouput of "fastboot getvar all" except the IMEI and SERIALNO so we can help you determine which RUU you can use if any available for your phone.
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
ubas98 said:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.27.3218.14
OpenDSP -v32.120.274.0909
OS-5.16.161.2 eMMC-boot 2048MB
Ive writed everything that i saw on my screen.if i mised anything please tell me
Click to expand...
Click to collapse
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Seanie280672 said:
that's not your fastboot getvar all, however, the most important part is there which is your OS number, 5.16.161.2 is Vodafone, there is no RUU for your device, do you not have a backup ? how did you brick ?
Click to expand...
Click to collapse
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
ubas98 said:
well ive wanted to get to stock so i unlocked my bootloader and tried to install ruu but it failed. and because i locked the bootloader ive somehow bricked my phone one cm11 loading screen. ive unlocked my bootloader and my recovery was all mesed up it couldnt load anny storage so i cant instal other rooms so im stuck here .i have no clue what to do
Click to expand...
Click to collapse
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
ubas98 said:
well everything worked but when i enter recovery mode it askes me a pasword and i dont know it anny solution?
Click to expand...
Click to collapse
password ? never seen that before, could you post a photo of it ?
Seanie280672 said:
password ? never seen that before, could you post a photo of it ?
Click to expand...
Click to collapse
http://postimg.org/image/ucolu3a83/ here is the img
ubas98 said:
http://postimg.org/image/ucolu3a83/ here is the img
Click to expand...
Click to collapse
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Seanie280672 said:
I have never seen that before in all my years of using TWRP, maybe one of the other guys can help you with that
Click to expand...
Click to collapse
maybe i could use another recovery .if yes anny what is other best recovery?
ubas98 said:
maybe i could use another recovery .if yes anny what is other best recovery?
Click to expand...
Click to collapse
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
ubas98 said:
oh somehow the pasword screen went out and now im in the recovery in which folder i could trasfer my rom to the phone?
Click to expand...
Click to collapse
adb push it straight to the sdcard, make sure your phone is plugged into the computer and the rom is in the same folder as adb and fastboot files, then issue this command:
Code:
adb push (name of rom).zip /sdcard/
it will look like its not doing anything but will let you know when its done, then uplug your phone before flashing the rom.
and both TWRP and CWM have their good points, you need CWM to flash AOSP rom's and TWRP to flash sense rom's
Seanie280672 said:
well as your s-on, you can forget about any RUU's at all for now.
I would recommend you flash twrp recovery, use 2.6.3.3 and then erase cache, then reboot bootloader (see commands below).
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
after that go into twrp recovery and select wipe then format data, this will completely wipe your phone of everything, but as its already messed up then it doesn't really matter, does it.
once that is done, download a sense rom from the development section and try and push it to your internal sdcard, if successful then flash it.
Click to expand...
Click to collapse
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
SGSII_LEDnotify said:
Strangely this is exactly the position I'm in today too.
I wanted to revert to stock after trying cyanogen, relocked the bootloaded and tried to run an RUU. However it stopped with an 'unknown error'. So I tried to push a zip file to it but the adb can't connect to the device and the phone isn't showing up in the device manager (because it's in boot mode?).
I then tried your advice about twrp and tried a different RUU but still get an unknown error and still can't push to the device.
Any ideas of what to try next? My OS is now showing as empty, there was something there previously.
I figured it was time to get some help before I broke things any more.
Click to expand...
Click to collapse
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Seanie280672 said:
first thing to do is unlock your bootloader again, if you've not already done that, then get TWRP 2.6.3.3 recovery on there, that maybe a problem though as your phone isn't showing in device manager.
So put your phone into the bootloader and see what device manager says then, it should say something if its detecting your phone, even if drivers arnt installed.
also, which HBOOT are you on ? and which Windows OS are you using ?
Click to expand...
Click to collapse
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
SGSII_LEDnotify said:
I think I've unlocked the bootloader again, fastboot is available and it's showing 'unlocked' at the top. twrp is on there too and I've done the wipe again. The fastboot commands work but pushing doesn't
error: device not found
HBOOT is 1.55.0000 / win7 64 home
Btw Twrp said it couldn't find cache but the wipe was successful.
Thanks for the help.
Click to expand...
Click to collapse
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Seanie280672 said:
ok I see what your saying now, what you need to do is boot into TWRP, main screen only, no sub menu's, at that point is your phone still detected in device manager ?
if so then............
put the rom you want to flash in the same folder as adb and fastboot files on your computer, then type:
Code:
adb push (name of rom).zip /sdcard/
you cant push files to your phone using fastboot or whilst its in the bootloader, that's strictly for flashing simple files like Radio's, HBOOTS, recoveries.
Click to expand...
Click to collapse
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
SGSII_LEDnotify said:
Well at least I've got something in the device manager even if it is a SAMSUNG Android Phone and not my HTC!
The push command hasn't brought up an error, the cursor is just flashing on the next line. It appears to be doing nothing like you said. So I guess I'm playing the waiting game for ten minutes or so. Will there be a notification when it's completed?
---------- Post added at 08:03 PM ---------- Previous post was at 08:00 PM ----------
Ok, transfer complete
Click to expand...
Click to collapse
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Seanie280672 said:
ok, unplug your phone, then goto install and select the rom from the list you just pushed, follow the Aroma options and instructions and also id recommend when given the option, to wipe data.
Click to expand...
Click to collapse
I renamed the zip file because there were spaces in the name causing errors, would that cause a failure when trying to install?
skipping MD5 check: no md5 file found
Error flashing zip '/sdcard/****.zip'
updating partition details
failed
Hey guys,
Last year I rooted my Incredible S and installed one of the CyanogenMods. Everything seemed to work fine until this spring when it started bootlooping on me. At first I could bootup and after running my phone for a few hours it would start looping. So I got a new battery which I thought would solve the problem, it didn't. Now I can't even boot up anymore without hitting the loop. I can only enter HBOOT.
I've tried following a few guides but I can't get anything going. Buying a new phone Friday but before thought I might as well post here. Any help?
-Revolutionary-
VIVO PVT SHIP S-OFF - RL
HBOOT-6.13.1002
RADIO-3805.6.03.16_M
eMMC-boot
Apr 1 2011, 18:34:39
I can enter fastboot but recovery and factory reset start a loop.
Thanks guys!
What recovery do you use?
Can you enter it?
If yes.. Just download one of your fav's roms, but it in your SD-Card, Wipe Everything, and Flash the rom (&GApps if AOSP) and reboot..
If No, Connect your Phone To PC and fastboot flash recovery recovery.img" :laugh:
Let me know if worked
Download and install a recovery, i recommend 4ext
See if u can enter it then...
I must tell ya, never give up, i remember myself forgetting to flash boot.img and having my dad almost killing me ^^
Thanks for the responses!
@Mohamed Ab M I cannot enter recovery off of hboot. I can flashboot and I tried to flash "recovery-clockwork-5.0.2.0-inc.img" but nothing improved. Is there something else I can try?
@oziboy Do you have a link for 4ext? I see the website but it looks like an app? Also, how do I wipe everything if fastboot is my only option right now?
Haven't given up yet but I only have until Friday!
Edit: Is there any chance this might have something to do with the radio?
ok tried two different things. Downloaded the recovery.img of 4ext from this thread: http://forum.xda-developers.com/showthread.php?t=1377751 and fastboot flashed it. Nothing changed.
So I tried flashing a different radio... still no go.
Not sure what else I can try?
Well.. I can think of one thing :|
Try doing these commands in fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Maybe something is wrong in system.. I don't know
Btw dose it say "success" when you flash a recovery? Or it fails?
And if It didn't work... Try running an RUU :| and you will lose everything:|
Mohamed Ab M said:
Well.. I can think of one thing :|
Try doing these commands in fastboot:
fastboot erase system
fastboot erase data
fastboot erase cache
Maybe something is wrong in system.. I don't know
Btw dose it say "success" when you flash a recovery? Or it fails?
And if It didn't work... Try running an RUU :| and you will lose everything:|
Click to expand...
Click to collapse
I don't mind losing everything, already backed up contacts and messages when I could still access the OS.
Can you recommend a good RUU to try? What is an RUU? Thanks for the help!
Then for a ruu go here http://androidruu.com/getdownload.p...33U_3831.18.00.11_M_release_266013_signed.exe
This should be the ruu that you need assuming your phone is a WWE, if you phone isnt WWE then use this to see what version is for you, make sure u only use vivo and not vivow
If the link to installation in beginning didnt work, that link was a link to the old thread of the RUU'S but anyway i posted the links for ya
Now all you gotta do is download the ruu , get ur phone to fastboot and do fastboot oem lock and then run the ruu on your computer and then go here for the rest http://forum.xda-developers.com/showthread.php?t=1359555
Got into fastboot and entered "fastboot oem lock" but kept getting an error, command error or something.
Downloaded 4 different ruus and got the "rom.zip" file and renamed it to "update.zip" and tried "fastboot update update.zip" on all of them.... no luck. Something about wrong signature or something.
Thanks for everyone's help but I don't see anyway out here!
jwads said:
Got into fastboot and entered "fastboot oem lock" but kept getting an error, command error or something.
Downloaded 4 different ruus and got the "rom.zip" file and renamed it to "update.zip" and tried "fastboot update update.zip" on all of them.... no luck. Something about wrong signature or something.
Thanks for everyone's help but I don't see anyway out here!
Click to expand...
Click to collapse
And u tried to run the ruu.exe without extracting the rom?
It saved my incredible s and my one x+
And to flash a rom.zip u need fastboot flash all rom.zip i think
This is actually doing something! I didn't realize I could run the RUU when plugged into fastboot. Fingers crossed here....
I got two working but both still resulted in a bootloop. Which convinces me the problem must be hardware or something. Oh well, it was a good device in its day.
Thank you for all your help!
Bootlooping is not a hardware failure..
Can you flash a recovery now? And use it?
Erm, now try extracting rom.zip and fastboot erase all and fastboot flash all rom.zip
Then id it does t work, flash the stock recovery from somewhere, only then you can use update.zip, this just came to my mind
If after flashing stock recovery try fastboot oem lock again and then go run the ruu.exe again
If it doesnt work then, then you gotta fastboot flash boot.img manually, this file is located in the rom.zip
If that doesnt work, try update.zip again with stock recovery
Must tell ya, its not hardware
You gotta give up only when your mobo is fried, and thats what i did on my htc one x+...
In the previous step I got S-ON set back on, does that change anything? Because now it seems that fastboot erase all doesn't work
erasing 'all'...
FAILED <remote: not allowed>
Trying the other steps you gave...
edit: I extracted a recovery_signed.zip file from the rom.zip file and tried to flash it using flashboot. Getting a signature error, though I know it is the correct RUU I am getting it from.
FAILED <remote: signature verify fail>
Try fastboot oem lock again, im 100 percent sure thats the command to lock it, i had almost the same issues when i failed my first try at rooting xD
Aight have you tried fastboot flash all rom.zip?
And then manually flash boot.img from the rom.zip?
None of those are working, getting errors on all them.
My HBOOT is not reading this, does this change anything?
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011.18:34:39
jwads said:
None of those are working, getting errors on all them.
My HBOOT is not reading this, does this change anything?
VIVO PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-3805.04.03.27_M
eMMC-boot
Apr 1 2011.18:34:39
Click to expand...
Click to collapse
Hboot is successfully downgraded, now follow this guide http://forum.xda-developers.com/showthread.php?t=2118187
From step 9
I can't follow that guide because I can't get into the android os to turn on usb debugging. My problem is still the boot loop.
oziboy said:
Hboot is successfully downgraded, now follow this guide http://forum.xda-developers.com/showthread.php?t=2118187
From step 9
Click to expand...
Click to collapse
When I run the program it just sits at "waiting for device..."
jwads said:
When I run the program it just sits at "waiting for device..."
Click to expand...
Click to collapse
Lol sorry for that one, i sent you to some adb thingy while ur in fastboot, i totally read over it xD
Anyway niw try unlocking again thru htcdev.com and then flash a recovery and get into it