Database Develop

[Q] No OS, no nothing

Oke guys,
I probally did one of the most stupid things. Got my One transformed tot a GPE 4.3 version works smooth. Yesterday an OTA update to 4.4 really messed up my day. Try to install everything gone....No i am not able to install any version at al.
Got the last version of TWRP installed. got myself an unlocked bootloader even an 4.3 GPE rom. But TWRP keeps giving me the message "Error flashing zip: 'sdcard/<M7_UL_JB443_STOCK_UI.
can someone help me solve this problem..

For 4.3 Roms you need twrp 2.6.3.0 and not 2.6.3.3.
Flash it and let us know
Sent from my HTC One using Tapatalk

Ivanovic said:
For 4.3 Roms you need twrp 2.6.3.0 and not 2.6.3.3.
Flash it and let us know
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Thans for you answer. I now got another one. "Unable to mount /data
unable to mount internal storage
I'm also not able to mount then by the menu.

Why do you need to mount internal storage?
Sent from my HTC One using Tapatalk

After installing the right twrp version. i use ADB to push the image.zip to my phone. Then i use twrp install and browse to my sdcard where the image.zip is transferred to. when i click it it gives that error. By the way he also starts with error flashing zip.
Comlete error is:
Error flashing zip '/sdcard/M7_UL_JB43..
updating partition details
e:unable to mount /data
e: unable to mount internal storage
i fear for my device...

Please anyone who can help me?

what about to boot to Bootloader, connect to some tools like Hasoon2000 Toolkits (cannot post links yet, sorry) and format everything you got, than flash the recovery again and push the rom via adb
make sure you download rom without any downloader
do not worry, i bricked my one the same day i got it and took me two nights to make it work again it needs lot of trying and searching but eventually you fix it

Thanks for your reply, i flashed everything a couple times. I guess is have the right rom. i do worry cause i tried so many things. Thinking about sending in my phone to HTC today..

lenneej said:
Thanks for your reply, i flashed everything a couple times. I guess is have the right rom. i do worry cause i tried so many things. Thinking about sending in my phone to HTC today..
Click to expand...
Click to collapse
what exactly are you trying to flash, link please.

i tried so many things is don't know exaclty the links. I tried different custom recovery. CWM and TWRP. Since i don't have an OS any more i tried to install de M7xxx.zip

Is the error still unable to mount sdcard? If so, follow post # 3 in my Canadian stock link.. You may need to use a recovery closer to your HBOOT version.

lenneej said:
i tried so many things is don't know exaclty the links. I tried different custom recovery. CWM and TWRP. Since i don't have an OS any more i tried to install de M7xxx.zip
Click to expand...
Click to collapse
would you mind sharing what this "M7xxx.zip" is.

I am having the same issue
I am having the exact same issue as OP. I have HBOOT version 1.54 and TWRP 2.6.3.3., my bootloader is unlocked, and I am S-On. Every time i try to flash an image it gives me the unable to mount error. I am trying to use the Stock 4.4 GPE nandroid rom as suggested by @ipfreelytech. Any suggestions? Thanks

nkk71 said:
would you mind sharing what this "M7xxx.zip" is.
Click to expand...
Click to collapse
I think he was trying to flash a RUU.zip or an OTA.Zip through TWRP. which of coarse ain't gona work
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
Silverlateralus said:
I am having the exact same issue as OP. I have HBOOT version 1.54 and TWRP 2.6.3.3., my bootloader is unlocked, and I am S-On. Every time i try to flash an image it gives me the unable to mount error. I am trying to use the Stock 4.4 GPE nandroid rom as suggested by @ipfreelytech. Any suggestions? Thanks
Click to expand...
Click to collapse
it sounds like your also trying to flash a RUU through recovery
go back where you downloaded the file and read the instructions on how to install it

Silverlateralus said:
I am having the exact same issue as OP. I have HBOOT version 1.54 and TWRP 2.6.3.3., my bootloader is unlocked, and I am S-On. Every time i try to flash an image it gives me the unable to mount error. I am trying to use the Stock 4.4 GPE nandroid rom as suggested by @ipfreelytech. Any suggestions? Thanks
Click to expand...
Click to collapse
Does it work on any other TWRP version? Can your phone boot normally?

SaHiLzZ said:
Does it work on any other TWRP version? Can your phone boot normally?
Click to expand...
Click to collapse
I tried TWRP 2.6.3.0 with the same result. I dont know what you mean by "boot normally", but when I turn it on and don't force it to bootloader it just loads a dead android with a ! symbol.

Silverlateralus said:
I tried TWRP 2.6.3.0 with the same result. I dont know what you mean by "boot normally", but when I turn it on and don't force it to bootloader it just loads a dead android with a ! symbol.
Click to expand...
Click to collapse
From fastboot usb and a command prompt run fastboot getvar all
From here you can figure out what RUU you need to get your phone working again
Sent from my HTC One using Tapatalk

I also tried CM 10.2 with TWRP v2.6.3.0 and 2.6.3.3. These are the errors i keep getting no matter what i try:
wwwTAKETHISOUT.imgur.com/FAbiDqd
---------- Post added at 01:04 AM ---------- Previous post was at 12:56 AM ----------
clsA said:
From fastboot usb and a command prompt run fastboot getvar all
From here you can figure out what RUU you need to get your phone working again
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.07.1700.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4286mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
This is the information I got. Not sure what to do with it though.

Silverlateralus said:
I also tried CM 10.2 with TWRP v2.6.3.0 and 2.6.3.3. These are the errors i keep getting no matter what i try:
(bootloader) version-bootloader: 1.54.0000 - your Hboot
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-main: 3.07.1700.1 - your firmware version
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001 - Google Play Edition CID
This is the information I got. Not sure what to do with it though.
Click to expand...
Click to collapse
Using the above info I see you have a google play phone or converted yours into one
To reset your phone your going to need s-off try here http://rumrunner.us/
what is the file your trying to flash in the photo (link to it please)

clsA said:
Using the above info I see you have a google play phone or converted yours into one
To reset your phone your going to need s-off try here
what is the file your trying to flash in the photo (link to it please)
Click to expand...
Click to collapse
I can't use rumrunner, because I don't have usb debugging enabled (which it says it requires).
The two roms i tried installing with TWRP are:
4.4 Nandroid - mega.co.nREMOVETHISz/#!TMlgWLDJ!ZfFlcx...4grwOLi-Ied3Tg
10.2 Cyanogen Mod - download.cyanogenmod.oREMOVETHISrg/get/jenkins/49872/cm-10.2.0-m7ul.zip

HTC one 802w Boot loop and no signals

Apologies to start a new thread, I have done a good research over other threads but I didn't get any solution yet.
1. New HTC one 80w.
2. I Unlocked + Rooted + flashed llabtoofer.[com]/2013/07/23/htc-one-dual-sim-maximushd/ using CWM.
3. Few days it worked like charm.
4. Once because of my carelessness battery got fully drained.
5. Kept the cell on charge and tried switching on.
!!!!! NOW STUCK WITH NO SIGNAL AND BOOT LOOP!!!!!
Please help
Click to expand...
Click to collapse
Below is the extract of fastboot getvar all
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.27.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.39.1402.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HC368W902063
(bootloader) Mod edit: Removed IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7cdug
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0771000
(bootloader) cidnum: HTCCN703
(bootloader) battery-status: good
(bootloader) battery-voltage: 3862mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b78ee36f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
Click to expand...
Click to collapse
Update:
Flashed 802T&D&W-Sense5-JB4.2.2-Soul17.0_mod using CWM, but same result, Boot loop and No SIgnal.
****************************************::::Update::::*********************************************
Captured log using logcat attached the output
****************************************************************************************************

Reflash the rom for a start. If that doesn't help - what recovery are you running? Maybe needs to be updated... Try TWRP recovery.

Moderator update,
I have removed your IMEI number. That is personal information and is not advisable to post online.
Ghost

pablo11 said:
Reflash the rom for a start. If that doesn't help - what recovery are you running? Maybe needs to be updated... Try TWRP recovery.
Click to expand...
Click to collapse
Thanks for the reply.
1. I tried reflashing, same result.
2. I tried stock recovery same result.
3. I tried CWM v6.0.3.2
4. Also tried TWRP for HTC One 802w (version 1.6.0.0)
Same result

Ghost said:
Moderator update,
I have removed your IMEI number. That is personal information and is not advisable to post online.
Ghost
Click to expand...
Click to collapse
Sorry and thanks.

Maybe you need to fastboot flash the boot image..
Sent from my HTC_PN071 using Tapatalk

pablo11 said:
Maybe you need to fastboot flash the boot image..
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply, any idea which boot.img should I flash?

Make sure you read up extremely well about this first. A working boot image for your model and software version is required. If maximus rom dev claims that your device is supported then you should start with that one....
Sent from my HTC_PN071 using Tapatalk

pablo11 said:
Make sure you read up extremely well about this first. A working boot image for your model and software version is required. If maximus rom dev claims that your device is supported then you should start with that one....
Sent from my HTC_PN071 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply,
I just tried with Stock boot.img and MaximusHD 1.0.0 boot.img, but no joy.
Still in boot loop with no radio signals

Flash all firmware package
Sent from HTC One 802w Dual Sim with my hand...

criszz said:
Flash all firmware package
Sent from HTC One 802w Dual Sim with my hand...
Click to expand...
Click to collapse
Thanks,
For flashing the firmware.zip do i need to lock the bootloader?

criszz said:
Flash all firmware package
Sent from HTC One 802w Dual Sim with my hand...
Click to expand...
Click to collapse
I tried all the firmware.zip which I extracted from different OTAs but only the one which is working is below one.
OTA_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1-2.36.1402.1_release_339019
Click to expand...
Click to collapse
This one finishes successfully and other are failing with
FAILED (remote: 43 main version check fail)
Click to expand...
Click to collapse
But still I am stuck with BOOT LOOP and NO SIGNAL

mate, you are s-on, need s-off and try this, all step s >>>> http://forum.xda-developers.com/showthread.php?t=2559891

criszz said:
mate, you are s-on, need s-off and try this, all step s >>>> http://forum.xda-developers.com/showthread.php?t=2559891
Click to expand...
Click to collapse
Actually as the phone is in boot loop, so not able to run the s-off fully.
I tried following ways.
1. revone, its giving error code = 1
2. rumrunner, keeps pouring upto 8-9 bottle and then shows restart, run rumrunner and pray.
3. moonshine, mobile restarts before completion.
While reading few forum posts I came to know boot loop could be because of battery problem also, any idea on this?
Click to expand...
Click to collapse

style_arun said:
Actually as the phone is in boot loop, so not able to run the s-off fully.
I tried following ways.
1. revone, its giving error code = 1
2. rumrunner, keeps pouring upto 8-9 bottle and then shows restart, run rumrunner and pray.
3. moonshine, mobile restarts before completion.
Click to expand...
Click to collapse
run rumrunner manny many time, some ppl said that on 802 subforum's

criszz said:
run rumrunner manny many time, some ppl said that on 802 subforum's
Click to expand...
Click to collapse
Ok, sure, Let me try today and report back.
Also I am planning to visit HTC service center today, just to diagnose if this is related to battery/hardware problem(I read on few forums because of battery issue people have faced same problems)
Thanks

style_arun said:
Ok, sure, Let me try today and report back.
Also I am planning to visit HTC service center today, just to diagnose if this is related to battery/hardware problem(I read on few forums because of battery issue people have faced same problems)
Thanks
Click to expand...
Click to collapse
I tried running rumrunner many times(5-6 times), but still it keeps pouring and then show Error: Read and Run again, same result with moonshine.
The problem is, when these s-off scripts are running my mobile restarts in between causing interruption to these scripts, which i believe is the cause of failure.

any help Experts please?

Any help on this please?

:::::Update:::::
The only RUU i am able to run is PN07IMG_M7C_DUG_JB_50_S1_HTCCN_CHS_CU_2.39.1402.1_Radio_1237.25.32.0717_release_338991
But this also gets stuck after reaching qsc100 in the fastboot command window.
PLEASE HELP

HTC One Looks Dead/Bricked - What to do next

*** SOLVED - Problem was my own stupidity ***
Got the HTC One a couple of days ago. Came back to Android after a few months on iPhone. Figured I'd jump right back into rooting and flashing custom ROMs.
Anyway, unlocked the phone, wanted to install Android Revolution 51, tried to upgrade firmware, and that's when things went sideways. Now, I can't do anything. Can Fastboot, but can't ADB. Have tried to load every driver in the book, but to no avail. CID is CWS_001 if that helps. Have been at this for a day and a half now. I need ideas.
thoughts?

Does it get detected on your window device manager when you plug it in?
sent from my mobile device

SaHiLzZ said:
Does it get detected on your window device manager when you plug it in?
sent from my mobile device
Click to expand...
Click to collapse
Yes. It shows up under Android USB Devices and says "My HTC"

diceman725 said:
Yes. It shows up under Android USB Devices and says "My HTC"
Click to expand...
Click to collapse
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...

Iz3man said:
Then you should be able to restore it with ADB... No idea how yet, but as far as I know your not completely dead here.... I may however be completely out to lunch here...
Click to expand...
Click to collapse
Would be very grateful. I agree, it would seem logical that I could ADB my way out, but at the moment, ADB doesn't recognize the device.

It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2

Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
I don't have a ROM loaded in the Virtual SD. And unless I'm mistaken, I can really only use ADB sideload at this point to load one up

Can you get into basic HTC recovery on the phone? I'm assuming you can if you can get fastboot working.
If so can't you just reflash a actual recovery from there, and then a rom from that? Apologies if this is completely irrelevant, I base all my android knowledge off my Desire.
Sent from my HTC Desire using Tapatalk 2

Adb reboot
sent from my mobile device

Zedrox said:
It does sound more like a recognition issue than a hardware problem to me. Also, correct me if I'm wrong but wouldn't you be using fastboot rather than adb to get out of this situation? Adb is pretty much only usefull with a booted rom in my experience.
Sent from my HTC Desire using Tapatalk 2
Click to expand...
Click to collapse
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.

Iz3man said:
Yeah now it does. I know if windows can see it you should be OK.
Try adb reboot recovery or adb reboot bootloader
Right be able to get into something there.
Click to expand...
Click to collapse
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.

diceman725 said:
Problem is I can't get into ADB. It doesn't recognize the device. Going to try to flash a recovery and see if that works.
Click to expand...
Click to collapse
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!

Iz3man said:
OK I'm lost here Can you boot into recovery? Or do you have a blank screen from the start?
Either way I hope you get it, its a pain when they do that!
Click to expand...
Click to collapse
I can get into recovery, yes...

If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device

SaHiLzZ said:
If you can boot to recovery, are you not able to boot to OS? How does it look dead??
sent from my mobile device
Click to expand...
Click to collapse
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.

diceman725 said:
There is no OS. Somehow I blew it away. When I get home I am going to try to flash a zipped RUU. Hopefully that works.
Click to expand...
Click to collapse
No luck on flashing the RUU file. It sends successfully, but fails on the write.

You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device

also nearly bricked
..

Please make a new thread.
sent from my mobile device

SaHiLzZ said:
You need to post an output of fastboot getvar all (imei /sn removed)
sent from my mobile device
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4088mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Phone is soft bricked, attempts to fix haven't work

Yesterday, I attempted to install a new rom. I had been using CM11 nightlies up till this point, and after being annoyed about certain aspects of my phone not working. I wanted to try something new.
I found ViperOne, and went to install it, thinking that it'll be the standard, run-of-the-mill install with no problems to be had. After getting through the install procedure and attempting to reboot to system, my phone dropped me back off at the bootloader. Thinking that I had forgotten to wipe something, I went into the recovery, wiped data, dalvik cache, and the cache, and attempted the install again. Once again, my phone dropped me off at the bootloader.
I thought, maybe I had a bad download. Re-downloaded the rom, same result. "Oh, I'll just try something else then". I found a Google Play Edition rom for my device, and decided to try that. It got stuck in a bootloop. After some googling, I attempted wiping the data/cache/dalvik cache again hoping it would help. Nope, still stuck in bootloop.
At this point (and after having running into a very similiar situation before) I decided to go for broke. I did a full wipe of the phone, and sideloaded CM10.1.3 (only stable CM rom for this device afaik). As it was installing, I noticed an error. "Unable to mount /data". I've had this problem before, and the way I fixed it last time was to install and run a stock rom. At this point in time, I was also getting frustrated and decided to put the stock rom back on my phone so it would at least be functional.
I found a stock rom and installed it just fine. The phone didn't even get stuck in a bootloop either. However, once the phone had finally booted up, I found that the touchscreen was unresponsive. I remember having this issue the last time I tried to use a stock rom. After a little bit of research, I had found that the problem stems from installing the wrong version of the rom. It was suggested on one of the websites to put "fastboot getvar version-main" into adb to find out what version I needed. It returns "version-main: ".
It was at this point that I remembered that I had made a backup of my phone before I attempted rooting. After some searching around, I managed to find it. That being said, I have no idea what to do with it. The folder where I made the backup contains a handful of .win files and some md5 checksums.
Since then I have been attempting seemingly random RUU versions in hopes of stumbling across the right one. It's been 5 hours, and I haven't had any success.
I would greatly appreciate any and all help that can be provided. If you guys need additional information (I'm not sure what I should include), let me know. I know some of the more basic ADB commands and their functions, so bear with me if I ask some questions about how to do certain things.

Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all

BD619 said:
Boot into bootloader/fastbootusb and type the below command and post the readout here.
fastboot getvar all
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: 4323mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-005bf6a40e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
BTW I removed
serialno:
imei:
meid:

BD619 said:
You can try one of the RUU's found here or follow the guide
Sidenote: don't use the 4.06.651.4 RUU unless you flash the 4.06.651.4 s-on firmware first.
Click to expand...
Click to collapse
I've tried several different RUU's, including the one's I could find here, and none of them have worked. Not sure if it really matters, but I attempted the 4.06.651.4 RUU earlier, but it failed.
BD619 said:
BTW I removed
serialno:
imei:
meid:
Click to expand...
Click to collapse
Why shouldn't those be shared? Are they considered sensitive information?

Ooops for got the link
http://forum.xda-developers.com/showthread.php?t=2503646
Yes they could be considered sensitive.

BD619 said:
Yes they could be considered sensitive.
Click to expand...
Click to collapse
I have no idea what those numbers represent. Why are important?

crazy-asian said:
I have no idea what those numbers represent. Why are important?
Click to expand...
Click to collapse
I have always been told not to include those...could be a way for someone to hack your device but that's just my guess.
http://en.wikipedia.org/wiki/Mobile_equipment_identifier

I had this happen to me also. Ends up i had to flash a new firmware on the phone and it booted right up. Also make sure you are using twrp recovery when you flash this rom. I used cwm and think that is where all my problems started. Hope ya get it worked out and may not be your problem but is exactly what happened to me and have i fixed it.

BD619 said:
http://forum.xda-developers.com/showthread.php?t=2503646
Click to expand...
Click to collapse
I had tried all but one of those in that list. That one that I hadn't used yet appears to be working. Thank you so much for the help.

Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.

crazy-asian said:
Oh god, now I'm back on the stock rom... Any recommendations for a good rom? I enjoy the stock look and feel of android, but running the CM nightlies has been giving me a headache.
Click to expand...
Click to collapse
I'm running BadSeed Sixth Sense
But it's all personal preference everyone will have a different opinion.

Fastboot, on the phone side, isn't connecting to my computer.

crazy-asian said:
Fastboot, on the phone side, isn't connecting to my computer.
Click to expand...
Click to collapse
Are you in bootloader?

BD619 said:
Are you in bootloader?
Click to expand...
Click to collapse
Yes, and it is in fastboot mode.

crazy-asian said:
Yes, and it is in fastboot mode.
Click to expand...
Click to collapse
When you type fastoot devices you don't get a response?

BD619 said:
When you type fastoot devices you don't get a response?
Click to expand...
Click to collapse
correct

crazy-asian said:
correct
Click to expand...
Click to collapse
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly

BD619 said:
Ok go back to my guide and you can get the proper drivers and instructions to get them installed correctly
Click to expand...
Click to collapse
Didn't solve the problem, phone still isn't in "fastboot USB"

crazy-asian said:
Didn't solve the problem
Click to expand...
Click to collapse
Try a different port(usb2 are best)
Try a different cable
Different PC
If you have android sdk setup try updating it.

[Q] Help M7 stuck in fastboot

Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ????
(bootloader) imei: ????
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.

thintin said:
Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
Click to expand...
Click to collapse
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.

Seanie280672 said:
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Click to expand...
Click to collapse
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Click to expand...
Click to collapse
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l

thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Click to expand...
Click to collapse
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
Click to expand...
Click to collapse
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.

Seanie280672 said:
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Click to expand...
Click to collapse
Sure, I appreciate your help with this
<<<< Identifier Token Start >>>>
5A5F19A2F517CC2BEA0DDADB1C3924C7
FA7846F59B3E38FC5897B053899BA233
824B607DDBDD9CE31E453E48CBE4EF5C
8ECD29487C09FE311D30DA91386C56C5
FF130E636BA23977B05905925EB17FC6
3EBBCC1BFCB2383B1A7DAFDCBFBE0AA7
8DA65BF8F702E6F44F24743AFA8573EB
AE8D23E995EED6E7CBC5981CEBBAFC66
694176C863DB9858CC535ED2D3EC609C
043196ED2CDF60AC13DEBBB636AA348E
E748366B4CA16747C0593C363D6B98E2
81C2699B2D1D979E7ACAC97D4187788E
85AEA5F27B48A9F8278A0B49D0D3838B
92E2EDFE6B16EEEDE98F322D92294ED0
E43D1945184BBF8A0CB9661B92CB9E38
040AAF8857A0FC1A4C7682ACF8120340
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
I'm s-on BTW in case that makes a difference; never been s-off.

thintin said:
Sure, I appreciate your help with this
I'm s-on BTW in case that makes a difference; never been s-off.
Click to expand...
Click to collapse
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?

Seanie280672 said:
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Click to expand...
Click to collapse
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?

thintin said:
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
Click to expand...
Click to collapse
yes defiantly, download the attachment and click the link on the email to continue the instructions.

Seanie280672 said:
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Click to expand...
Click to collapse
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.

thintin said:
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
Click to expand...
Click to collapse
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?

Seanie280672 said:
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Click to expand...
Click to collapse
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1

thintin said:
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
Click to expand...
Click to collapse
ok good, also could you post a link to the O2 RUU you downloaded earlier

Seanie280672 said:
ok good, also could you post a link to the O2 RUU you downloaded earlier
Click to expand...
Click to collapse
GRRR!
Following firewater instructions...
adb reboot <–important!!!!
Click to expand...
Click to collapse
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
adb wait-for-device push firewater /data/local/tmp
Click to expand...
Click to collapse
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.

thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
Click to expand...
Click to collapse
try this version of adb and fastboot instead, sounds like its out of date and also check your device manager, make sure it says MyHTC when your phone is plugged in: http://forum.xda-developers.com/showthread.php?t=2588979

thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
Click to expand...
Click to collapse
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.

majmoz said:
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
Click to expand...
Click to collapse
Don't worry, I didn't type the important! bit
I'm not sure how much more time I want to spend trying to reset this device, maybe I'll just return it to O2 as it is and see if they even care that it's been unlocked!
I'll try the link you suggested and report back :tired:

Hi.
I think my guardian angel must have had a hand in this because I was only trying to reset the phone to return it due to the microphone not working. After all of these failed attempts I factory reset the current rom and bingo! Microphone working again and no need to return to O2
But thanks for all of the help you offered, I would have a lot less hair and more wrinkles without you.