Need help please!!!
I did a really bad mistake last week when I wanted to downgrade my HTC Incredible S to original ROM and now it loop on the HTC logo every 3 sec. Previously I installed iNcReDiBlESeNsEv4.0
ICS ROM and it worked like a charm. I just wanted to downgrade to orginal ROM so I execute the following RRU: RUU_Vivo_BellMobility_WWE_1.37.666.3_Radio_Radio_20.23.30.0802U_38.02.01.17_M_release_174461_signed.exe and this is where my nightmare begin. I’m now unable to access Recovery and stock on the HBOOT menu. I’m able to connect Fastboot and flash radio, flash recovery and boot but without success.
How could I make my recovery worked back and install ROM again? I really miss my Smartphone right now so please help a poor guy like me.
Here is the phone info:
fastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 6.13.1002
(bootloader) version-baseband: 3805.04.03.27_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.46.669.1
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3212000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4098mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-8a731c6e
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
From HBOOT menu:
-Revolutionary-
VIVO PVT SHIP S-OFF RL
HBOOT-6.13.1002
RADIO-3805.04.03.27_M
eMMc-boot
Apr 1 2011,18:34:39
Thanks in advance for your help!!!
No need to donwgrade if you have costum rom before. Just recovery with backup orig.rom
Sent from my HTC Incredible S using xda app-developers app
Thx for your answer,
How I do that? I'm not able to access recovery, it loop on the HTC logo when I select it from the HBOOT menu. I have a backup from clockwork that I did before doing my mistake but I don't know how to restore it.
Could I restore it from Fastboot?
Re install recovery change recovery to 4EXT, you can find thread on forum INC S. if you can access bootloader it will work flash recovery.img via CMD.
Sent from my HTC Incredible S using xda app-developers app
Link
http://forum.xda-developers.com/showthread.php?t=1136463
Sent from my HTC Incredible S using xda app-developers app
I tried to flash recovery using the following command:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
and the output was:
sending 'recovery' (3726 KB)...
OKAY [ 1.154s]
writing 'recovery'...
OKAY [ 0.756s]
finished. total time: 1.914s
But when I tried to access recovery from HBOOT menu, I always get the HTC logo loop. Do you have any idea why this happenning? I had 4Ext before, is-it could be the problem?
Thanks for your help
wesly.btm said:
Re install recovery change recovery to 4EXT, you can find thread on forum INC S. if you can access bootloader it will work flash recovery.img via CMD.
Sent from my HTC Incredible S using xda app-developers app
Click to expand...
Click to collapse
I tried to flash recovery of 4Ext and clockwork without success, my phone is rebooting when I select recovery option. Any idea?
chris_Andrew said:
I tried to flash recovery of 4Ext and clockwork without success, my phone is rebooting when I select recovery option. Any idea?
Click to expand...
Click to collapse
OK, trying to absorb all the different things you have posted in different threads, so forgive me if ask something you already posted on a different thread.
You stated that you were running a custom ICS ROM prior to trying to flash a RUU, right?
Based on the getvar all info you posted, I would suggest you use this Bell Mobility RUU instead of the one you selected.
http://www.filefactory.com/file/c0a...5AU_3805.04.03.27_M_release_199657_signed.exe
I would personally run the RUU without the phone connected and then extract the ROM.zip out of the %TEMP% directory and copy it to your sd card and rename it PG32IMG.zip.
Then boot into bootloder and let it flash it.
If that works, at least your phone should boot and then you could try flash either CWM or 4EXT recovery.
Thanks for your reply,
I already solved my problem last week end. After flashing recovery more then ten times and flashing radio with froyo and gingerbread without success during more then 5 hours, I fall on a post on xda saying that this is the latest ICS radio. I decided to give them a try and flash it using fastboot and guess what? My phone was able to boot and my recovery is now working.
I decided to stay with a custom Rom and try Nik Aura Rebirth Rom and I more then love it.
I'm so happy now and I will not retry to install RUU again .
Thanks everybody for your help and if someone have a similar problem don't hesitate to reply
Sent from my HTC Incredible S using xda app-developers app
chris_Andrew said:
I fall on a post on xda saying that this is the latest ICS radio. I decided to give them a try and flash it using fastboot and guess what? My phone was able to boot and my recovery is now working.
I'm so happy now and I will not retry to install RUU again
Click to expand...
Click to collapse
It shouldn't scare you off RUUs!
Sounds like your original problem was a bad/incorrect Radio Flash with the RUU.
What was your radio prior to the RUU?
Regardless, glad you solved it. Nothing more frightening than a potential brick!!
Related
Hi,
VERY URGENT PLEASSSSSSSSSSS
I was trying to install Android_Revolution_HD-Incredible_S_1.1.3 thru CWM and
it said installed succssfully.
Then I did reboot but the device got stuck on the boot screen.
I have a NAND backup (thanks god) and I tried to do a restore thru CWM 3.0.0.8
When I restarted the phone (Vol down + power) I got Hboot but when trying to go to recovery it didnt run the CWM recovery. So, I am stuck now.
Please help me to get back my phone running up again.
Any idea about how to be able to run CWM recovery?
try to pull out the sd card in start the phone.
Same thing my friend !!!
Anyway, I need the sd card inserted since the backup is in it.
Please I need help?
I am stuck with the Hboot screen and when I go to RECOVERY it goes to the fastboot instead. Moreover, if I run the device normally it gets stuck in the white screen with the HTC Incredible logo
How to get the CWM?
I am trying to install CWM as explained here:
http://forum.xda-developers.com/showthread.php?t=1003723&page=1
but with no luck at all.
If it will solve my issue, can someone help me please?
MAQ7 said:
Hi,
VERY URGENT PLEASSSSSSSSSSS
I was trying to install Android_Revolution_HD-Incredible_S_1.1.3 thru CWM and
it said installed succssfully.
Any idea about how to be able to run CWM recovery?
Click to expand...
Click to collapse
This was taken directly from the Android Revolution Opening Post:
You need ClockworkMod Recovery with EXT4 support from here in order to flash this ROM
The instructions you referenced in your last post were for flashing CWM on a HTC Desire HD. Did you actually flash one of the zip files from that thread?
Click on the "here" link to download the correct one for the IncS and Android Revolution.
Sounds like a friend of mine that flashed a 4ext Rom with a cwm without 4ext.
RTFM is always a god thing ;-)
/ Sent from my HTC IncS
using XDA Premium App /
tpbklake said:
This was taken directly from the Android Revolution Opening Post:
You need ClockworkMod Recovery with EXT4 support from here in order to flash this ROM
The instructions you referenced in your last post were for flashing CWM on a HTC Desire HD. Did you actually flash one of the zip files from that thread?
Click on the "here" link to download the correct one for the IncS and Android Revolution.
Click to expand...
Click to collapse
Isn't it CWM 3..0.0.8 with EXT4 support?
In fact, I couldn't flash any one of them.
Unfortunately, the link that you provided is blocked in our country. If possible, please upload it somewhere else (rapidshare, zShare, multiupload, ...etc). Meanwhile, I will try to open it with proxy.
Thanks
Is there a way to flash the recovery using fastboot command?
I tried: fastboot flash recovery recovery.img
in the command prompt but I got FAILED (remote: not allowed).
Any clue?
MAQ7 said:
Is there a way to flash the recovery using fastboot command?
I tried: fastboot flash recovery recovery.img
in the command prompt but I got FAILED (remote: not allowed).
Any clue?
Click to expand...
Click to collapse
fastboot flash commands will only work if you used AlphaRevX to S-OFF or if you have the ENG HBOOT loaded. If you simply S-OFF using a XTC Clip, not all of the fastboot commands are imlemented in the normal HBOOT. You need to flash the ENG-HBOOT.
would this help to resolve the issue:
C:\android-sdk_r06-windows\android-sdk-windows\tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.92.0000
(bootloader) version-baseband: 2.15.00.07.28
(bootloader) version-cpld: None
(bootloader) version-microp: 0417
(bootloader) version-main: 3.26.605.1
(bootloader) serialno: HT08VHJ00454
(bootloader) product: incrediblec
(bootloader) platform: HBOOT-8x50
(bootloader) modelid: PB3120000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bf6f94d0
(bootloader) hbootpreupdate: 11
all: Done!
finished. total time: 0.010s
Hi tpbklake,
please have a look at the result of getvar all command. do i still need to do anything from what you just said?
tpbklake said:
fastboot flash commands will only work if you used AlphaRevX to S-OFF or if you have the ENG HBOOT loaded. If you simply S-OFF using a XTC Clip, not all of the fastboot commands are imlemented in the normal HBOOT. You need to flash the ENG-HBOOT.
Click to expand...
Click to collapse
It is S-OFF using AlphaRevX.
What should I do now???
Try and find a guide to flash the end-hboot, then use the fastboot commands to flash clockwork mod.
MAQ7 said:
Hi tpbklake,
please have a look at the result of getvar all command. do i still need to do anything from what you just said?
Click to expand...
Click to collapse
LOL! Dude you have an Htc Incredible, not an Incredible S. You are posting in the wrong forum.
MAQ7 said:
Hi tpbklake,
please have a look at the result of getvar all command. do i still need to do anything from what you just said?
Click to expand...
Click to collapse
You need to go to the forum group (HTC Droid Incredible):
http://forum.xda-developers.com/forumdisplay.php?f=635
If you've been trying to flash files from the Incredible S forum, no wonder you are having trouble.
tpbklake said:
You need to go to the forum group (HTC Droid Incredible):
http://forum.xda-developers.com/forumdisplay.php?f=635
If you've been trying to flash files from the Incredible S forum, no wonder you are having trouble.
Click to expand...
Click to collapse
Sorry for the confusion I made !!!!
If it is not the right place and no body can help here then how can I move my thread to the right forum?
I really appreciate your attemps to help.
Everything is fine now.
I put the image in sdcard as PB31IMG.zip and rebooted the device into Hboot and then flashed it.
Now, I am trying to run my backup.
Thanks
MAQ7 said:
Everything is fine now.
I put the image in sdcard as PB31IMG.zip and rebooted the device into Hboot and then flashed it.
Now, I am trying to run my backup.
Thanks
Click to expand...
Click to collapse
Glad you got it working.
hi guys i am new to the forum and i have been searching for my problem and havent found a solution for my problem.
i rooted my HTC ONE i am from Puerto Rico my htc is from claro ( i think is international ) got my bootloader unlock and everything so i downloaded HTC nexus ROM ( http://forum.xda-developers.com/showthread.php?t=2544119 ) and flashed it using TWRP recovery when flashing i got an error and by mistake i hit reboot system and it boot up the ROM and but it was tooo laggy and i tho it was the ROM so i download another one ( http://forum.xda-developers.com/showthread.php?t=2341395 ) and this one i got the same error flashing but it boot up and was laggy too while searching in the forum some people say that i needed to update my recovery so i did to the latest TWRP recovery i factory wipe and flashed the HTC nexus ROM and i am stuck in a boot loop that i cant get rid off i can boot into recovery and fastboot.
The boot loop is basically i boot into the Google screen when selecting the language the screens goes black.
( my bad if i have any bad grammar i am not very good at english )
i hope i can get this boot loop resolve thanks in advance.
Try fastboot erase cache.
What version twrp did you flash and link of twrp
What error was you getting.
Post a fastboot getvar all
Sent from my GT-I9505 using XDA Premium 4 mobile app
bored_stupid said:
Try fastboot erase cache.
What version twrp did you flash and link of twrp
What error was you getting.
Post a fastboot getvar all
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Already tried fastboot erase cache
this one openrecovery-twrp-2.6.3.0-m7.img ( got it from htconeroot dot com ) it doesnt let me post the whole link ;(
right now i got the latest one i think it was 2.7.0.0
this was the error i was getting " error executing updater binary in zip /sdcard error flashing zip "
trying to get the fastboot getvar all on my mac but i cant.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: HTC__332
(bootloader) battery-status: good
(bootloader) battery-voltage: 3878mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0b0efc32
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Flash twrp2.6.3.3. 2..7 has known problems then download ARHD 62
Flash ARHD.. but wipe cache, dalvic cache and system first. Not internal storage..
Sent from my GT-I9505 using XDA Premium 4 mobile app
bored_stupid said:
Flash twrp2.6.3.3. 2..7 has known problems then download ARHD 62
Flash ARHD.. but wipe cache, dalvic cache and system first. Not internal storage..
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how can i add ARHD 62 to my internal storage?
minpao20 said:
hi guys i am new to the forum and i have been searching for my problem and havent found a solution for my problem.
i rooted my HTC ONE i am from Puerto Rico my htc is from claro ( i think is international ) got my bootloader unlock and everything so i downloaded HTC nexus ROM ( http://forum.xda-developers.com/showthread.php?t=2544119 ) and flashed it using TWRP recovery when flashing i got an error and by mistake i hit reboot system and it boot up the ROM and but it was tooo laggy and i tho it was the ROM so i download another one ( http://forum.xda-developers.com/showthread.php?t=2341395 ) and this one i got the same error flashing but it boot up and was laggy too while searching in the forum some people say that i needed to update my recovery so i did to the latest TWRP recovery i factory wipe and flashed the HTC nexus ROM and i am stuck in a boot loop that i cant get rid off i can boot into recovery and fastboot.
The boot loop is basically i boot into the Google screen when selecting the language the screens goes black.
( my bad if i have any bad grammar i am not very good at english )
i hope i can get this boot loop resolve thanks in advance.
Click to expand...
Click to collapse
You have this problem because your device is s-on and it needs to be s-off as stated in the OP for the nexus rom.
You will have to reboot to recovery and sideload another rom to flash, one that doesn't require you to be s-off so that means no google edition roms.... as quoted above ARHD 62.0 is ok for you.
Search XDA for "sideload" and you will find all the info you need to recover your device.
rider5512 said:
You have this problem because your device is s-on and it needs to be s-off as stated in the OP for the nexus rom.
You will have to reboot to recovery and sideload another rom to flash, one that doesn't require you to be s-off so that means no google edition roms.... as quoted above ARHD 62.0 is ok for you.
Search XDA for "sideload" and you will find all the info you need to recover your device.
Click to expand...
Click to collapse
Thanks the only bad thing is i have a mac most of the guide here are using windows.
Hey guys.
I may have wiped my /data and sdcard partitions but have re partitioned them now. I cant bot up and it gets stuck at the green HTC logo... I have been trying to find an ruu to flash as i have no data on my internal storage... I bought my phone out right here in Australia and dont know what ruu im looking for. Would someone be able to help me?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH445W900623
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.242s
Thanks alot
am4476
There are no ruus for that version. You could adb push or sideload a Rom to your phone from recovery. Btw remove your imei from your post
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
There are no ruus for that version. You could adb push or sideload a Rom to your phone from recovery. Btw remove your imei from your post
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cant push as adb device isnt located and sideload wont locate device either
I will suggest the following:
Download files from here: http://forum.xda-developers.com/showthread.php?t=2244106&page=95
Then flash firmware.4.20.980.1.zip in RUU mode..
From bootloader mode, do a factory reset, then flash custom rom.
Try ADB push/sideload again from INSIDE custom recovery.
Post back the results.
SaHiLzZ said:
I will suggest the following:
Download files from here: http://forum.xda-developers.com/showthread.php?t=2244106&page=95
Then flash firmware.4.20.980.1.zip in RUU mode..
From bootloader mode, do a factory reset, then flash custom rom.
Try ADB push/sideload again from INSIDE custom recovery.
Post back the results.
Click to expand...
Click to collapse
i got firther than it did before so its a start! Still getting errors after <bootloafer> zip info parsing...
Heres the log.
target reported max download size of 1514139648 bytes
sending 'zip' (43505 KB)...
OKAY [ 3.051s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 3.298s
Lock bootloader. Try again
SaHiLzZ said:
Lock bootloader. Try again
Click to expand...
Click to collapse
HOLYMOTHEROFANDROID it was successful but it said flush again immediately coz of 90 hboot pre update?
EDIT: So it worked after i re flashed but now i cant boot to bootloader so i can get to recovery
So it worked flashing stock RUU butttt... If i go into recovery i cant mount /data or internal storage through TWRP recovery? should i repeat and stay in stock recovery? What should i do then?
Cheers
Format everything in recovery then push a Rom to your phone
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
Format everything in recovery then push a Rom to your phone
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that just now it says
Updating Partition details...
Full SELinux support is present...
Formatting data using make_ext4fs function.
You may need to reboot to recovery to be able to use /data again.
Updataing Partition details.
EDIT: Ok so now it says i have 26GB of internal storage now... What should i do? It ended up rebooting into recovery with that so i guess it worked?
Ive tried this 2 times and same error..
Im using TWRP and ADB is still not working even after flash... Only fastboot works Only just bought this phone and I need it for work ahahaha
Alrighttt guys. Think i may have a solution! Going up o my local PLE store here in Perth to get a OTG cable. Using ARHD as my rom and will let you know within the next hour or so as to if it works.
The OTG cable will definitely work and it's very handy to have. You mustnt have the drivers installed properly or else adb would work in recovery
Sent from my HTC One using XDA Premium 4 mobile app
nateboi81 said:
The OTG cable will definitely work and it's very handy to have. You mustnt have the drivers installed properly or else adb would work in recovery
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OTG works but the ARHD 51.x file dosnt boot fully, gt stuck at HTC one logo so 1 step after where it stopped last time, i just need to find a stock os zip to flash to it
Solved, No longer bricked thanks the the members on XDA and the lovely 12 dollar OTG cable i have bought. Just put the zip onto the otg cable and flashed to my phone through TWRP. Now fully working and all partitoned.
After months of thinking it through, i finally decided to give up on sense and try cyanogenmod... horrible desicion. I tried the installer and according to to the installer itself the install had concluded without error and all i had to do now was wait for my device to boot. When booting my device off andd after 5 minutes of beeing stuck in a bootloop, i realized that something had gone horribly wrong. I found many solutions online, but ended up narrowimg down to 2 options: wipe data/ factory reset and wipe dalvik through CWM or running a ruu to go bavk to stock and retry from there. Tried doing the wipe but i kept getting the error "Cant mount data" so i pretty much gave up on that option and went for running the RUU. Succesfully locked my bootloader again and all that was left for me to do was run the ruu and wait for my htc one to be running sense again! While going through the installer, i got an error at around the" 1/5" part of the ruu install (i used an exe) which said "error 171, check usb connection" and i also simultaniously got a pop up window that said "htc_fastboot.exe has stopped working" . At this point i really dont know what to do. PLEASE! Someone help me!
josevera30 said:
After months of thinking it through, i finally decided to give up on sense and try cyanogenmod... horrible desicion. I tried the installer and according to to the installer itself the install had concluded without error and all i had to do now was wait for my device to boot. When booting my device off andd after 5 minutes of beeing stuck in a bootloop, i realized that something had gone horribly wrong. I found many solutions online, but ended up narrowimg down to 2 options: wipe data/ factory reset and wipe dalvik through CWM or running a ruu to go bavk to stock and retry from there. Tried doing the wipe but i kept getting the error "Cant mount data" so i pretty much gave up on that option and went for running the RUU. Succesfully locked my bootloader again and all that was left for me to do was run the ruu and wait for my htc one to be running sense again! While going through the installer, i got an error at around the" 1/5" part of the ruu install (i used an exe) which said "error 171, check usb connection" and i also simultaniously got a pop up window that said "htc_fastboot.exe has stopped working" . At this point i really dont know what to do. PLEASE! Someone help me!
Click to expand...
Click to collapse
is your phone recognised by device manager? Are you using Windows and if so what version are you running?
Can you post a fastboot getvar all removing your serial number and imei please and let me know what RUU you are running?
stovie_steve said:
is your phone recognised by device manager? Are you using Windows and if so what version are you running?
Can you post a fastboot getvar all removing your serial number and imei please and let me know what RUU you are running?
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
im using windows 8 and the ruu is
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
josevera30 said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.081s
im using windows 8 and the ruu is
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
Click to expand...
Click to collapse
I think it's down to Windows 8 - fastboot isn't detecting the drivers Which is why it fails with error 171
Have you tried again with a Windows 7 PC?
I think there is a post on here about getting fastvoot drivers to work on Windows 8. I'll have a look
stovie_steve said:
I think it's down to Windows 8 - fastboot isn't detecting the drivers Which is why it fails with error 171
Have you tried again with a Windows 7 PC?
I think there is a post on here about getting fastvoot drivers to work on Windows 8. I'll have a look
Click to expand...
Click to collapse
Please help me! If you can find a fix, please do! i kind of hate the cyangenmod installer for getting me into this mess!! When i get back to stock i'll probably still try to put cyanogenmod on my htc one...
josevera30 said:
Please help me! If you can find a fix, please do! i kind of hate the cyangenmod installer for getting me into this mess!! When i get back to stock i'll probably still try to put cyanogenmod on my htc one...
Click to expand...
Click to collapse
Try this guide
http://forum.xda-developers.com/showthread.php?t=2232799
Followed the guide thoroughly but got this pop up window at the last step.
josevera30 said:
Followed the guide thoroughly but got this pop up window at the last step.
Click to expand...
Click to collapse
Does fastboot work normally or does it only fail when running an RUU, if that's the case uninstall HTC Sync if you have it installed. But leave drivers installed. HTC sync is known to cause problems with RUU's
But there is no RUU that will work for you since your device is s-on and on the latest firmware. Downgrading is not possible with s-on. At this point the best you can hope for is to flash a custom rom. At least you can get the phone booting that way.
Do if adb/fastboot is working normally just push a Rom and install it. If you can't get adb/fastboot working on your Windows 8 pc try my mini guide here to create a bootable Linux pen drive.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Does fastboot work normally or does it only fail when running an RUU, if that's the case uninstall HTC Sync if you have it installed. But leave drivers installed. HTC sync is known to cause problems with RUU's
But there is no RUU that will work for you since your device is s-on and on the latest firmware. Downgrading is not possible with s-on. At this point the best you can hope for is to flash a custom rom. At least you can get the phone booting that way.
Do if adb/fastboot is working normally just push a Rom and install it. If you can't get adb/fastboot working on your Windows 8 pc try my mini guide here to create a bootable Linux pen drive.
Click to expand...
Click to collapse
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
You can't use this RUU on your phone because its an older version. You need s-off to flash lower version RUU. You will need to either s-off your phone or restore it using a nandroid backup of 6.07.1540.1 or flash another custom rom like Danny suggested above. Look in this thread: http://forum.xda-developers.com/showthread.php?t=2355992 you might found a nandroid backup of that version. If you can find it just tell me and I'll upload mine for you. I also have the stock recovery for that version if needed.
to install cyanogenmod you need a recovery with block:by-name support like newer version of TWRP.
http://wiki.cyanogenmod.org/w/Install_CM_for_m7
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
Download the latest CWM recovery and flash it with fastboot. http://downloadandroidrom.com/file/HTCOne/recovery/M7CWM/recovery-clockwork-touch-6.0.4.8-m7.img
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Download CM11 here. Rename the file to rom.zip and place it in your fastboot folder on your pc.
http://downloadandroidrom.com/file/HTCOne/M7/roms/CM11/cm-11-20140624-NIGHTLY-m7.zip
Also download gapps rename it to gapps.zip and place it in your fastboot folder.
http://downloadandroidrom.com/file/gapps/PA/pa_gapps-stock-4.4.3-20140608-signed.zip
Boot your phone to cwm recovery and connect usb. Do a factory reset then in the command window type
Code:
adb push rom.zip /sdcard
Wait for the push to compmete
Code:
adb push gapps.zip /sdcard
again wait for completion, it's normal for the command window to appear unresponsive until the push completes.
Now use cwm to install the Rom.zip followed by gapps.zip.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
Any update?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Any update?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
He also asked me (via PM) a TWRP nandroid backup of stock 6.07.1540.1 which I have uploaded for him yesterday.
No update yet, still don't know if the OP will flash the rom or restore the nand but I think he wants to flash the rom (but have the nand just in case).
alray said:
He also asked me (via PM) a TWRP nandroid backup of stock 6.07.1540.1 which I have uploaded for him yesterday.
No update yet, still don't know if the OP will flash the rom or restore the nand but I think he wants to flash the rom (but have the nand just in case).
Click to expand...
Click to collapse
Lol, he was also pm me, last I herd he was having trouble pushing the cm11 Rom. After successful push the Rom was still not on the device.
I instructed him to use "mount usb storage" in cwm. Not heard anything since
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Solved!
Thank you so much for your help! I did a wipe data/ factory reset and used sideload to push and install cyanogenmod! Thanks for your help :good:
josevera30 said:
Thank you so much for your help! I did a wipe data/ factory reset and used sideload to push and install cyanogenmod! Thanks for your help :good:
Click to expand...
Click to collapse
Thanks for the update, good to know you got it sorted
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk