Related
edit and tldr
ok so i recieved the phone from htc with a bootloop out of the box
instead of sending it back i was a numpty and decided to sort it myself and unlocked it to flash a rom
i accidentially deleted all the data
managed to get my winsows 8 laptop working today and got drivers working smoothly to the point i was able to sideload a rom so the phone finally had life from being a brick
my issue is no matter what rom i load it boots to splash screen, hangs at a black screen with the status bar at the top and battery and time then reboots and repeats.
i want help to get my phone back to life and stable with a workable rom and no bootlooping
i dont know what the issue is
i dont have s off
rumrunner wont work
i cannot boot into phone to allow debugging or disable fast boot
please help
device info
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
i will offer a small sum for who ever gets me a working phone. small exchange for a paperweight !
Deleted. Op edited post to include cash reward. Dont want to look like im helping to receive money.
hi there, thank you for the reply, i have done steps 1, id already done that but ive done it again and installed the sdk into a folder in c drive for ease. the only problem is that when i click on fastboot in xp it comes up with a cmd windows a lot of writing comes down and then it just closes :/
ive already voided the warranty as ive somehow managed to unlock the bootloader and ive flashed cmw now what i need to do is somehow get s off and sideload a rom
another issue i have is that because i cant use fastboot the way youve said, ive downloaded an all in one tool from this forum, when i click a process it dosent do anything for me, but what it does so, is open a cmd window in which im able to type in fast boot commands i did the getvar all command and here is what you requested
'C:\Documents' is not recognized as an internal or external command,
operable program or batch file.
C:\Documents and Settings\fresh\Desktop\one\data>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH39**********
(bootloader) imei: **********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4327mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.328s
C:\Documents and Settings\fresh\Desktop\one\data>
Deleted
garyfl said:
ok so i think this is going to be a little long winded
basically, i got a htc one given to me by htc,
Click to expand...
Click to collapse
Why don't you think they would give you a new working one?... :s (this is just a rhetorical question)
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
the ruu you have linked indicates i need s off, which i am having trouble doing, could you guide me ? i am thinking when i have fixed my windows 8 laptop tommorow this is going to be a smoother process. it also says i need hboot 1.44 and have to flash this
garyfl said:
thanks for your reply, i am not able to open a command by selecting the white space as for toonight im running on a 15 year old xp laptop. i will try the ruu but any i have tried have concluded in giving what i think was a 170 error saying use correct ruu
Click to expand...
Click to collapse
If you don't solve it before I get a lil bit of time, I can try for tonight but can't promise it as it's still hectic here at work, I'll log in remotely and have a look at things if you want, and try to help you get it sorted.
In the meantime, you can take a picture of the hboot or fastboot screen that you get to with power + vol down and post it, and that will help you get the information from us for more information on the phone.
Also post a shot of the correspondence from HTC with your personal information removed/redacted/left out and that will also help us help you.
DO NOT ATTEMPT S - OFF with the knowledge and hardware that you're working with, you first need to use adb and fastboot some and be familiar with it before even going there. I'm not saying not ever, I'm saying not until you've resolved this and the phone's running good.
Deleted
when i run rumrunner with my version 2.24.401.1 it just says run again and read. so obviously failing. i did everything before i typed fastboot devices and got my device code, then getvar ver to get my number and downloaded appropriately but rum runner dosent work. so no s off. i give up.
sorry didnt read your reply, well it didnt initialise so no s off anyway
garyfl said:
sorry didnt read your reply, well it didnt initialise so no s off anyway
Click to expand...
Click to collapse
Take a picture of the hboot screen and post it for us
im sorry i cant take a pic atm no cameras, what i can do is write eveything out as it looks in detail for you
***tampered*** <--- in dark grey
***unlocked*** <--- in pink
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OPENdsp-v31.120.274.0617
OS-2.24.401.1
eMMC-boot 2048MB
Jun 22 2013, 00.54:00.14313
FASTBOOT USB <--- in red
then its just the vol up and down with selecable bootloader, reboot, reboot bootloader, power down at the bottom. i have rooted many phones in the past, desire hd, one x, galaxy note, galaxy s4, its just the trouble i am facing i think is using xp
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
garyfl said:
can anyone shed any light ?
im having so much trouble
no ruus work
cannot for life of me sideload anyfiles it just comes up with errors like dameon not running or device not found
drivers are installed and htc sync is uninstalled. pulling my hair out. any xp drivers ? going to have a good go with it tommorow with windows 8. seems like the device is completely bricked.
Click to expand...
Click to collapse
flash twrp/cwm recovery to your one
open the sideload feature of the customer recovery on your phone and connect to your computer usb
download this and put the downloaded file together with your adb and fastboot folder
then adb sideload or adb push the dowloaded guru reset to your One
once it is done, you can install the guru reset zip using the custom recovery install option
right just to update i have some semi good news and fell im getting somewhere
got my windows 8 laptop up and running today and installed all drivers and adp corrdctly, this accounts for the intel usb 3 mod too. adb and fastboot were recognising the device.
ive succesfully got out of brick mode and managed to get a rom to sideload to the deviice, the rom being viper rom in question, installed successfully, only issue is i have a wierd bootlooping issue where it does actually boot to lockscreen but when i pull lockscreen up with my finger it shows htc splash screen.
having ago with android revolution now.
wondering if i have to flash a boot.img or something
can anyone advise ?
ive spent countless days on this
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
garyfl said:
regarding the current flash, it stays on splash screen and a box pops up system ui stopped. will flashing the guru reset ruu.zip for my version work ? ill try it now otherwise afterthat im out of ideas now,
Click to expand...
Click to collapse
the guru ruu.zip for 2.24.401.1 is sideloading now
guys, the guru stock installed but now im back to the very beginning of the way i recoieved my phone. bootloops to the black screen with bar at top with date and battery, then after a while restarts, please someone help me
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
I think I can recover the phone with instructions (I can't post URLs yet) that will install a different recovery and uses adb sideload. But it also erases the sdcard which I try to avoid.
So, Is there anyone who can advice me what to do? If it cannot be avoided that my sdcard will be wiped; so be it. But I will manage doing that, I'm looking for an alternative at the moment. I suspect that if I find the correct recovery version that it will "mount" the "sdcard" (which I think is an emulation because the HTC One has no sdcard??) will also allow me to recover my phone with sdcard intact. But I find it difficult to find the correct recovery.img. I've tried two versions *can't find numbers back right now, will post if needed*.
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
ruud.walraven said:
I'm the next one in line with the same question, but no other answers helped me yet. What I did wrong was adb sideloading the OTA file using CWM recovery. That part I understand, so completely my own fault.
However, the update is still on the SD card and I tried to load stock recovery via fastboot so that I can install OTA from the SD card. What I get is something I find a lot of others have as well; the recovery fails to mount sd card 5 times. When I try to "Apply from SD card" I get an error "Check cid failed! --invalid operation--" and the phone reboots. The same error happens to users in many places, an example here: androidcentral . com/how-manually-update-your-google-play-edition-htc-one-android-44-kitkat
...
HTC One, converted into GPe (so tampered and unlocked)
HBOOT 1.44
Click to expand...
Click to collapse
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
mbroeders said:
Ruud, I don't know if I completely understand your story, but you are able to get into stock recovery right? If so, do not choose 'Apply from SD card', but 'Apply from phone'. I got the same error messages (fails to mount SD card...), but if the OTA file is on your phone, you have to choose phone storage.
Click to expand...
Click to collapse
I should have mentioned that the other options (apply from phone and apply from cache) don't work either. One thing I am unsure about is if this is indeed the stock recovery.img I put back on. Is there a single recovery.img for HTC One, or a list where I can find which one came standard so I can put it back. My suspicion is that that recovery will work, although the guy I bought the phone from may have installed recovery/images that may have reformatted everything in a way that stock won't work any longer...
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(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: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
ruud.walraven said:
I noticed most people need to post fastboot getvars all. Makes sense to figure out what software I need so here it is:
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(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: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
Click to expand...
Click to collapse
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
I've tried a whole range of things that didn't help. Don't want to preserve the sd card any longer.
Flashed recovery versions: 1.29.401.12, 2.24.401.8, 3.07.1700.1 and 3.58.1700.5.
Neither version was able to reinstall from sdcard. But I found out later that I may have done *something* to the sdcard (see CWM below)
Next I flashed CWM to try flashing a nandroid. However during the process I couldn't browse my sdcard anymore. Before flashing above recoveries I had CWM and then I could see all files. May have done something wrong.
After trying the mentioned nandroid a few times I realized that I am S-ON.
I have been trying to get S-OFF for the last few hours because I found a file I want to use on my phone (See htc1guru . com/2013/11/android-4-4-kit-kat-google-edition-3-58-1700-5-ruu-ota-files/). I've looked at Moonshine, but my phone is not in the list of supported rom versions (1.29.401.12). I tried Revone, but get error = 1.
So now I'm not sure what to do next!!
mbroeders said:
Are you sure this is the GPe version? I get a feeling that you have the Sense version and then it won't work of course. (sorry if I'm wrong)
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
you bought it from an idiot.
you can't properly convert to GPE with s-on. That's why your hboot, mainver and cid are all wrong for a GPE conversion.
I assume you're boot-loader unlocked? flash cwm or TWRP. Then restore this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-htc__102-1-29-401-12-2013-05-16-zip/
after restoring that nandroid try to s-off with revone and or rumrunner.
Revone: http://forum.xda-developers.com/showthread.php?t=2314582
Rumrunner: http://forum.xda-developers.com/showthread.php?t=2488772
once your s-off you can properly convert your phone to GPE. The problem wasn't just that you flashed it with a custom recovery but that the phone was never in a proper state to receive OTA for GPE!
use the RUU from here once your s-off to convert to GPE 4.4 : http://forum.xda-developers.com/showthread.php?t=2358781
you'll also want to go supercid with fastboot oem writecid 11111111
ruud.walraven said:
I am absolutely sure I have a Sense version originally. I bought it from someone who unlocked the bootloader and replaced the sense firmware with GPe. OTA was working because I OTA-ed to 4.3. I've contacted him this morning, but he says to have no idea what files he used.
Click to expand...
Click to collapse
I'm downloading all required files right now. In the meantime looking into everything to make sure to not further brick it once S-OFF. Tricky business!
ipfreelytech said:
you'll also want to go supercid with fastboot oem writecid 11111111
Click to expand...
Click to collapse
There's one question I found: according to this thread SuperCid 11111111 doesn't get OTA and the best bet for me would be HTC__001. Is that correct, or can I also choose from HTC_001 or GOOGL001? (the latter I remember reading is supposed to be good too). In any case ... I suppose I can best follow your instructions and I can change the cid to whatever needed afterwards anyway.
edit: It took 1.5 hours to download the nandroid, but something must have gone wrong because the file cannot be opened by winzip nor 7z. After the failed opening of the file I've md5-ed the entire zip file and it doesn't match the checksum on the download link. So started download again...
I have a problem; the download stops at different points, never completing. Must be a problem in the connection or at htc1guru. Is there an alternative file/download/mirror I can use as well? Have searched google for the same file with no results.
I was finally able to download the file through FF. Every time the download failed I started again, but paused and replaced the .part file with the failed download. When you resume FF detects the last bit and resumes from there. Best part was that I got my Chrome 900+MB download and used that as .part file. So I could resume nearly finished. Ran the checksum to be sure nothing funny had happened because of my tinkering. To quote Borat: great success.
However, after restoring the nandroid through CWM I tried both Revone and Rumrunner. Revone fails error = 1 and Rumrunner assumes I start from my homescreen (which I can't). A bit unwise, but I tried anyway from both fastboot and CWM but in neither case will Rumrunner continue. It claims there is no ADB connection (even though the phone shows up in adb devices).
So I am stuck for now. Still looking at as many posts about S-OFF as I can to see if I find some vital piece of inof I missed or something I can still try. But for now I'd like some idea's how to achieve S-OFF..
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
SaHiLzZ said:
What is the date in your hboot version? If after June, then revone won't work. Have you tried moonshine?
Click to expand...
Click to collapse
hboot has a date? Hboot is 1.44 and bootloader start screen says apr 12 2013, is that what you mean?
My version (1.29.401.12) is not supported by moonshine for as far as I can tell.
I also notice now that fastboot getvars bootmode says: fastboot. Shouldn't this be disabled for revone and/or rumrunner?
ruud.walraven said:
...
(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.12
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 1234567890AB
(bootloader) imei: 123456789000000
(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: 4295mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
...
Click to expand...
Click to collapse
Just a question: In a sense I can't have messed anything up that bad because I'm S-ON. So if I would install the 4.3 release that was on the device before I sideloaded the 4.4 OTA through CWM, wouldn't it just work because all things point to the correct places? Since I broke it with adb sideloading, I could restore the device probably just as well, right?
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
ziolooo said:
I had same problem on my device. I decided to install CWM instead of TWRM, downloaded RUU 4.2.2 and flashed it. Next I get update to 4.3 and 4,4 later and now everytning works perfect.
Click to expand...
Click to collapse
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
ruud.walraven said:
Willing to try, but I don't see the RUU file needed on http://forum.xda-developers.com/showthread.php?t=2428276 nor on htc1guru.com. This should be done through fastboot oem rebootRUU, right? If everything works I'm don. if OTA or some functions don't wrok I maybe able to S-OFF and follow previous instructions till the end. And if it doesn't work I'm back to where I am now anyway.
Click to expand...
Click to collapse
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
ziolooo said:
Here you have good tutorial how to install RUU:
http://htc-one.wonderhowto.com/how-...with-bootloader-recovery-ota-updates-0148068/
Download and flash RUU from this site.
Click to expand...
Click to collapse
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
ruud.walraven said:
Thanks for the link. That won't work though because I'm still trying to achieve S-OFF which is a prerequisite to follow that guide.
Click to expand...
Click to collapse
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
ziolooo said:
http://htc-one.wonderhowto.com/how-to/set-your-htc-one-s-off-using-moonshine-windows-0147992/
Click to expand...
Click to collapse
I already tried that.
ruud.walraven said:
...
In any case; I still would want to S-OFF my device to go through ipfreelytech's steps and get a functioning 4.4 GPe. But So far I found that Moonshine doesn't support my device and for both rumrunner and revone I need to start from a booted up android homescreen. So all three options don't seem to work. Did I really brick my phone, or is there still hope??
Click to expand...
Click to collapse
hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)
progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.
Hi, I bought a used m7 which was rooted and tried to return to stock. However the RUU installer failed and im now stuck with in bootloader which says TAMPERED and RELOCKED
here is fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXX
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3887mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Can anyone tell me which ruu installer i should use or give any other suggestions?
Thanks
zirbenaum said:
Hi, I bought a used m7 which was rooted and tried to return to stock. However the RUU installer failed and im now stuck with in bootloader which says TAMPERED and RELOCKED
here is fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXX
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3887mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Can anyone tell me which ruu installer i should use or give any other suggestions?
Thanks
Click to expand...
Click to collapse
do you know how to use adb and fastboot, also do you have drivers installed on your computer ?
Seanie280672 said:
do you know how to use adb and fastboot, also do you have drivers installed on your computer ?
Click to expand...
Click to collapse
yes i have drivers installed and i got the this info with fastboot. adb doesn't seem to recognize the phone though.
zirbenaum said:
yes i have drivers installed and i got the this info with fastboot. adb doesn't seem to recognize the phone though.
Click to expand...
Click to collapse
adb wont work in the bootloader, heres where the fun starts:
ADB commands only work in a booted rom or in a custom recovery, they don't work in the bootloader
Fastboot commands only work in the bootloader, they don't work in a booted rom or recovery.
phew.....glad we got that bit out of the way
first thing is first, can you start downloading this, its your reset rom file, but the servers are a little slow, that's why I say start, when its finished downloading, rename it to rom.zip for ease, and put it in the same folder on your computer where adb and fastboot files are please, heres the file: http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
whilst that is downloading, you will need to goto HTC Dev and unlock your bootloader, just follow the instructions they give you, its a piece of cake, and as you already have adb and fastboot, you wont need to download the 3 files later on that they tell you to download: http://www.htcdev.com/bootloader/
your flags will then turn to UNLOCKED and TAMPERED, this is normal, nothing to worry about.
report back when done.
Seanie280672 said:
report back when done.
Click to expand...
Click to collapse
Ok i unlocked the bootloader and the phone booted! whew
Thank you so much!
It is till in rooted state tough but i guess it's better than bricked.
zirbenaum said:
Ok i unlocked the bootloader and the phone booted! whew
Thank you so much!
It is till in rooted state tough but i guess it's better than bricked.
Click to expand...
Click to collapse
the phone booted ? lol, that's strange, we're not finished yet lol, strange that it didn't boot whilst relocked but booted whilst unlocked.
Seanie280672 said:
the phone booted ? lol, that's strange, we're not finished yet lol, strange that it didn't boot whilst relocked but booted whilst unlocked.
Click to expand...
Click to collapse
Well I am not complaining The download takes more than two hours. What should i do after it is done?
zirbenaum said:
Well I am not complaining The download takes more than two hours. What should i do after it is done?
Click to expand...
Click to collapse
you could try one of the alternative links on that site, however, if your happy with your phone the way it is now then you wont need that file.
just scroll down the page a little and theres 2 alternative download links.
the ksn
Seanie280672 said:
you could try one of the alternative links on that site, however, if your happy with your phone the way it is now then you wont need that file.
just scroll down the page a little and theres 2 alternative download links.
Click to expand...
Click to collapse
I was hoping to get it in vanilla state but after this nightmare maybe it is better to leave it as it is until ive done some more research
zirbenaum said:
I was hoping to get it in vanilla state but after this nightmare maybe it is better to leave it as it is until ive done some more research
Click to expand...
Click to collapse
whats vanilla state ?, sorry im not familiar with that term, guess we can both teach each other something here
shall
Seanie280672 said:
whats vanilla state ?, sorry im not familiar with that term, guess we can both teach each other something here
Click to expand...
Click to collapse
Its software that is not customized. Wikipedia says:
Computer software, and sometimes also other computing-related systems like computer hardware or algorithms, is called Vanilla when not customized from its original form, meaning that it is used without any customizations or updates applied to it.
http://en.wikipedia.org/wiki/Vanilla_software
Maybe actual vanilla would be stock android without any htc customizatios though.
zirbenaum said:
Its software that is not customized. Wikipedia says:
Computer software, and sometimes also other computing-related systems like computer hardware or algorithms, is called Vanilla when not customized from its original form, meaning that it is used without any customizations or updates applied to it.
http://en.wikipedia.org/wiki/Vanilla_software
Maybe actual vanilla would be stock android without any htc customizatios though.
Click to expand...
Click to collapse
ahh I see, now that's where we were heading originally, to get pure stock rom you will need to download that file I linked you too earlier, and as your phone is booting now, just copy the file to your internal storage not into the adb and fastboot folder.
i'll tell you what to do next if you want to proceed.
Seanie280672 said:
ahh I see, now that's where we were heading originally, to get pure stock rom you will need to download that file I linked you too earlier, and as your phone is booting now, just copy the file to your internal storage not into the adb and fastboot folder.
i'll tell you what to do next if you want to proceed.
Click to expand...
Click to collapse
well the download is going to take forever and it is already 1 am here so maybe i have to do this some other time. But you can give the instuction and i'll do this later.
You have been very helpful, thank you again.
zirbenaum said:
well the download is going to take forever and it is already 1 am here so maybe i have to do this some other time. But you can give the instuction and i'll do this later.
You have been very helpful, thank you again.
Click to expand...
Click to collapse
when the file has finished downloading, check the MD5 and file size before copying it to your phone, just to make sure its not corrupt.
then what you will have to do, is copy that file you are downloading to your internal storage, then reboot your phone to the bootloader and plug it into the computer,. make sure it says fastboot usb on the screen.
then download this file: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
and put it in the same folder as adb and fastboot on your computer, open a command window (CMD) in that folder by holding control + shift + right mouse click in any white area of that folder and select open a command window here, then type the following commands one at a time, wait for each command to finish before issuing the next.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
once that is done, unplug your phone and enter recovery using the volume buttons to navigate and the power button to select.
when in recovery goto wipe and just swipe to factory reset, do not advanced wipe.
when done, goto install and in the list it gives you, select the file you downloaded and copied to your internal storage, swipe to begin the install, follow the instructions, and when it gives you the options, select yes wipe data, yes install stock radio and yes install stock recovery.
once installation is complete, it will ask you to reboot, when you select reboot, if the screen goes black (this doesn't always happen, most times it reboots without any problems), just hold down the power button until the lights on the bottom flash 10 to 15 times and then the phone will boot to full stock rom with OTA ability.
I know this sounds long and confusing, but you will see as you go along its easy, just don't skip any steps.
if you have any problems, just report back here, but if you follow my instructions it should run like clockwork.
Download official ruu from here http://www.htc1guru.com/downloads/ruu-file-downloads/ check the CID ... CID codes are given vit RUU .yrs is HTC_Y13 So try yur cid supported ruu. bootloader must b locked.
Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.