fastboot error (waiting for device) - One (M7) Q&A, Help & Troubleshooting

I tried to downgrade my hboot from 1.6 to 1.44 by fastboot method as a requirement to install old firmware on my HTC One M7 to resolve my camera Issue which I discussed earlier in other posts.
Downloaded and followed these steps properly..
http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
In result it completed but on mobile the status bar was not completed fully and it hanged so I hold the power button until restarted.
When I verified it showed hboot version 1.44 which means it was installed properly.
Now I am trying to lock my bootloader for the reason to install Stock RUU, the fastboot is not recognizing the device and shows waiting for device...
When I connect my device with computer in fastboot, windows are not recognizing the device. I also installed the latest version of htc usb drivers v4.17.0.001 but still not recognizing.
I also tried installing the below stock but it fails every time (bootloader unlocked). I think may be require locked bootloader??
http://www.htc.com/us/support/htc-one/news/
Attached some screenshots for reference.
Thanks

Leave it unlocked because you're S-OFF
Also hboot 1.44 works only on windows 7, install windows 7 on your pc or try with another windows 7 pc tu run ruu.

lucyr03 said:
Leave it unlocked because you're S-OFF
Also hboot 1.44 works only on windows 7, install windows 7 on your pc or try with another windows 7 pc tu run ruu.
Click to expand...
Click to collapse
Ok thanks I will try to install the RUU on Windows 7...
But can I upgrade my hboot (means any zip file or something) by custom recovery (means not connecting with computer)???

asfandjan1 said:
Ok thanks I will try to install the RUU on Windows 7...
But can I upgrade my hboot (means any zip file or something) by custom recovery (means not connecting with computer)???
Click to expand...
Click to collapse
RUU upgrades hboot.
I suggest you 7.19.401.51 ruu, have 1.61 hboot and it's compatible with windows 8 and 10.
hboot can be upgraded only from fastboot.

lucyr03 said:
RUU upgrades hboot.
I suggest you 7.19.401.51 ruu, have 1.61 hboot and it's compatible with windows 8 and 10.
hboot can be upgraded only from fastboot.
Click to expand...
Click to collapse
Thanks
Now I am going to install the said RUU 7.19.401.51 using Windows 7 because my windows 10 is not recognizing the phone now and I am unable to connect with computer.
Thank you once again..

Related

[SOLVED] Soft bricked after manual OTA

Hi,
First, I'm an idiot.
I tried to manually apply the 4.3 OTA by:
fastboot oem rebootRUU
Then flashed the firmware.zip from the OTA:
flash zip firmware.ota
Got a softbrick.
Tried wiping cache and data, wont boot at all.
HBoot updated to 1.55 and firmware rev appears as 3.62.401.1
I'm S-ON with locked bootloader.
Can't apply earlier RUU.
Is there any way you can think of to restore my phone without unlocking it through htcdev.com and flashing a custom recovery?
Thanks,
flash a 4.3 rom through recovery.
i guess you only flashed the firmware.zip and not the whole ota? 4.2.2 roms do not work for me with this firmware.zip
edit: didn't see your locked. i guess there's no way then.
Nemesis_00 said:
Hi,
First, I'm an idiot.
I tried to manually apply the 4.3 OTA by:
fastboot oem rebootRUU
Then flashed the firmware.zip from the OTA:
flash zip firmware.ota
Got a softbrick.
Tried wiping cache and data, wont boot at all.
HBoot updated to 1.55 and firmware rev appears as 3.62.401.1
I'm S-ON with locked bootloader.
Can't apply earlier RUU.
Is there any way you can think of to restore my phone without unlocking it through htcdev.com and flashing a custom recovery?
Thanks,
Click to expand...
Click to collapse
1- Question: why did you manually flash the OTA, if you're still locked and on stock??????????
2- after "fastboot oem rebootRUU", did "fastboot flash zip firmware.zip" TWICE?? you know that usually the first time it reports as "FAILED, push image again immediately" (or something like that).
nkk71 said:
1- Question: why did you manually flash the OTA, if you're still locked and on stock??????????
2- after "fastboot oem rebootRUU", did "fastboot flash zip firmware.zip" TWICE?? you know that usually the first time it reports as "FAILED, push image again immediately" (or something like that).
Click to expand...
Click to collapse
Hi,
1. It's already established I am an IDIOT. It was even the first line of my post
2. Yes, I have flashed it twice. Stuck at black screen after boot. No ADB. Connecting to the PC shows MTP driver as showing up but failing to install.
Nemesis_00 said:
Hi,
1. It's already established I am an IDIOT. It was even the first line of my post
2. Yes, I have flashed it twice. Stuck at black screen after boot. No ADB. Connecting to the PC shows MTP driver as showing up but failing to install.
Click to expand...
Click to collapse
You're not an idiot, take it easy but maybe next time do some more reading before doing something you're not comfortable with.
At least you flashed it twice, so good chance it updated the firmware correctly, but which version of
1- Windows are you on? (hopefully Win 7)
2- and HTC Drivers? (latest are "HTCDriver_4.8.0.002.exe" AFAIK)
3- you on stock or custom recovery?
3b-- if stock, is the OTA file still on your phone?
4- do you have an OTG cable?
nkk71 said:
You're not an idiot, take it easy but maybe next time do some more reading before doing something you're not comfortable with.
At least you flashed it twice, so good chance it updated the firmware correctly, but which version of
1- Windows are you on? (hopefully Win 7)
2- and HTC Drivers? (latest are "HTCDriver_4.8.0.002.exe" AFAIK)
3- you on stock or custom recovery?
3b-- if stock, is the OTA file still on your phone?
4- do you have an OTG cable?
Click to expand...
Click to collapse
Thanks for your help.
Im running Win7 with latest HTC drivers, stock recovery. I bit the bullet and unlocked the bootloader.
The OTA file is not on the phone, but I have an OTG cable.
Fastboot and ADB are installed and working.
P.S.
I have the decrypted 1.29.401.16 zip available.
Tried flashing the zip to the phone, got an error.
Thanks again,
Nemesis_00 said:
Thanks for your help.
Im running Win7 with latest HTC drivers, stock recovery. I bit the bullet and unlocked the bootloader.
The OTA file is not on the phone, but I have an OTG cable.
Fastboot and ADB are installed and working.
P.S.
I have the decrypted 1.29.401.16 zip available.
Tried flashing the zip to the phone, got an error.
Thanks again,
Click to expand...
Click to collapse
OK so fastboot and adb are working :good::good:
Now let's slow down a bit, and let us what your goal is. (ie what ROM do you want to run, ROOT, and anything else of importance).
nkk71 said:
OK so fastboot and adb are working :good::good:
Now let's slow down a bit, and let us what your goal is. (ie what ROM do you want to run, ROOT, and anything else of importance).
Click to expand...
Click to collapse
Obviously there is no ADB since the ROM doesnt boot, but fastboot works fine.
For now, I would like to get back to stock 4.2.2 (2.24.401.8) or even 4.3 (3.62.401.1) if possible.
The MID is PN0710000 and CID is HTC__102
Thanks
you should have manually flashed ota via stock recovery,need to be s-off as well
sent from my s-off 801n M7_UL
Nemesis_00 said:
Obviously there is no ADB since the ROM doesnt boot, but fastboot works fine.
For now, I would like to get back to stock 4.2.2 (2.24.401.8) or even 4.3 (3.62.401.1) if possible.
The MID is PN0710000 and CID is HTC__102
Thanks
Click to expand...
Click to collapse
adb works in recovery too. Are you on stock or custom recovery?
Sent from my HTC One using Tapatalk
Stock recovery.
Ok, I've installed TWRP, now just waiting to download guru reset.
Nemesis_00 said:
Ok, I've installed TWRP, now just waiting to download guru reset.
Click to expand...
Click to collapse
IMHO, if you are comfortably doing it
get http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/
then use http://rumrunner.us/ to get s-off (there's a package for 3.62.401.1), then use a full RUU (exe) to go back to stock and get the OTAs.
Thanks, That's exactly what im doing.
Just copied the Guru reset to the usb flash
Nemesis_00 said:
Thanks, That's exactly what im doing.
Just copied the Guru reset to the usb flash
Click to expand...
Click to collapse
Any updates mate?
Sorry, ofcourse.
Flashed Guru Reset boots and works fine.
I didnt manage to S-OFF tho.
Followed all instructions except disabling lockscreen which is impossible with this fw.
Win7 x64 SP1. Firewall and AV disabled.
Stuck with the error message: "FATAL: F**k it" after the second boot into bootloader (test3).
Basically the ROM should be stock and no real reason to re-flash stock via RUU, but it seems somewhat less smooth than 4.2.2, and I have a FC from TuneIn Radio the moment I plug it into the original car dock.
So I thought id start again fresh.
I suppose I'll flash a different Sense based ROM and try to S-OFF again.
Nemesis_00 said:
Sorry, ofcourse.
Flashed Guru Reset boots and works fine.
I didnt manage to S-OFF tho.
Followed all instructions except disabling lockscreen which is impossible with this fw.
Win7 x64 SP1. Firewall and AV disabled.
Stuck with the error message: "FATAL: F**k it" after the second boot into bootloader (test3).
Basically the ROM should be stock and no real reason to re-flash stock via RUU, but it seems somewhat less smooth than 4.2.2, and I have a FC from TuneIn Radio the moment I plug it into the original car dock.
So I thought id start again fresh.
I suppose I'll flash a different Sense based ROM and try to S-OFF again.
Click to expand...
Click to collapse
You'll have to be on a ROM that's compatible with your firmware version (which is now 3.6xxxx). Here are a few things to check
1- Are you on Win7, it could work on Win 8 maybe 8.1 but only haphazardly
2- Did you update drivers to "HTCDriver_4.8.0.002.exe"
3- uninstalled HTC Sync
3- did you update adb sdk to latest
4- disable antivirus & firewall & windows defender, etc.
5- on the phone:
----- disable any lockscreen password, pin, etc (so the password or pin or face recognition, not the actual lockscreen)
----- enable USB debugging
----- disable SETTINGS -> POWER -> Fast boot
copy/paste command prompt of rummrunner for us to see
nkk71 said:
You'll have to be on a ROM that's compatible with your firmware version (which is now 3.6xxxx). Here are a few things to check
1- Are you on Win7, it could work on Win 8 maybe 8.1 but only haphazardly
2- Did you update drivers to "HTCDriver_4.8.0.002.exe"
3- uninstalled HTC Sync
3- did you update adb sdk to latest
4- disable antivirus & firewall & windows defender, etc.
5- on the phone:
----- disable any lockscreen password, pin, etc (so the password or pin or face recognition, not the actual lockscreen)
----- enable USB debugging
----- disable SETTINGS -> POWER -> Fast boot
copy/paste command prompt of rummrunner for us to see
Click to expand...
Click to collapse
Hi,
1. Win7 Pro x64. Device connected to USB2.0
2. The installed drivers are "HTCDriver_4.8.0.001.exe" Could not find 002 anywhere.
3. I never had HTC Sync
4. Updated Android SDK with SDK Manager to latest version..
5. Antivirus unloaded completely, firewall (Windows) disabled.
6. FW Version reported by fastboot is 3.62.401.1, same as the one reported by the OS itself.
7. Not password/pin/face lock etc.
8. USB Debugging enabled, and Fast Boot disabled.
9. Rumrunner log is as follows:
Code:
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0710000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (25/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
...................
Thanks,
Nemesis_00 said:
Hi,
1. Win7 Pro x64. Device connected to USB2.0
2. The installed drivers are "HTCDriver_4.8.0.001.exe" Could not find 002 anywhere.
3. I never had HTC Sync
4. Updated Android SDK with SDK Manager to latest version..
5. Antivirus unloaded completely, firewall (Windows) disabled.
6. FW Version reported by fastboot is 3.62.401.1, same as the one reported by the OS itself.
7. Not password/pin/face lock etc.
8. USB Debugging enabled, and Fast Boot disabled.
9. Rumrunner log is as follows:
Code:
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
[PN0710000-1.55.0000]
Test 2 (ALT): Booting device
Rebooting from fastboot
Waiting for ADB (25/120)
Device detected.....................
[------------------------------------------------------------]
Test 3: Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: **** it
...................
Thanks,
Click to expand...
Click to collapse
Let me be honest, I have never tried (at least not yet ) rumrunner (I got S-Off with revone), but I did go through rumrunner thread, and the only two things I can think of, seeing your output:
Code:
Waiting for fastboot (7/120)
FATAL: **** it
that would be caused by the fastboot.exe (maybe the latest version is not the best )
Code:
...................
that's usually caused by a firewall or something else interfering with the internet connection.
I can't remember where I got the drivers from, but uploaded them for you:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
or you could, uninstall HTC xxxxxx, then download and install the latest HTC Sync Manager (from HTC web site), and then just uninstall the sync manager and keep drivers.
If all that doesn't work, I would give the Ubuntu Live CD/USB a try.
nkk71 said:
Let me be honest, I have never tried (at least not yet ) rumrunner (I got S-Off with revone), but I did go through rumrunner thread, and the only two things I can think of, seeing your output:
Code:
Waiting for fastboot (7/120)
FATAL: **** it
that would be caused by the fastboot.exe (maybe the latest version is not the best )
Code:
...................
that's usually caused by a firewall or something else interfering with the internet connection.
I can't remember where I got the drivers from, but uploaded them for you:
HTCDriver_4.8.0.002.exe 15.1 MB
https://mega.co.nz/#!TAcGAJ7L!YdWM4AIji95b1ow8kVgagggOx5Yh7csRN5G0KJaCo6w
or you could, uninstall HTC xxxxxx, then download and install the latest HTC Sync Manager (from HTC web site), and then just uninstall the sync manager and keep drivers.
If all that doesn't work, I would give the Ubuntu Live CD/USB a try.
Click to expand...
Click to collapse
As I've seen rumrunner has it's own fastboot.exe so I doubt it's that. There's also no firewall or anything, fastboot and adb work just fine on their own.
I've also S-OFF using revone, but later the emmc chip died, so I sent it for repair. Got it back with 1.54 hboot.
I'll give the Live CD a try later when I get the chance.

[Q] Help turning GPE back into Sense

I successfully converted my One into GPE some time ago and was trying to change it back. I tried to flash the RUU but my hboot was too new. I flashed to downgrade the hboot to 1.44 but now my phone isn't recognised by my PC in fastboot mode. It is still recognised while booted properly. I can't flash the RUU again because it gets stuck 'waiting for bootloader'. I am S-OFF and my bootloader is 'relocked'. Anyone have any ideas?
Use a windows 7 machine.
SaHiLzZ said:
Use a windows 7 machine.
Click to expand...
Click to collapse
Could that actually be the problem? I've used fastboot commands successfully before (after some problems) on windows 8.1.
From most reports 1.44 HBOOT doesn't work with 8.1.
leo.sutton said:
Could that actually be the problem? I've used fastboot commands successfully before (after some problems) on windows 8.1.
Click to expand...
Click to collapse
Yep use windows 7 machine. I had the same problem. I issued every command on a windows 8.1 laptop until the ruu flash. Once the phone booted into the ruu mode it was an "unrecognized usb device"
Using windows 7 did indeed solve it! Thanks.

[Q] Can't use adb/fastboot while in bootloader, after flashing failed.

Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
rocktv88 said:
I haven't use Windows 8, but so far I don't have any problem with Windows 7. I assume have already install the HTC driver. If not, you can install the HTC syn which comes with the driver.
Click to expand...
Click to collapse
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
TomFader said:
Yes, I already installed the HTC drivers (htc sync +d rivers, then uninstalled htc sync, as it get's annoying while plugin on off of the phone)
My biggest problem is that, now fastboot is not running in bootloader mode, so I can't even flash an image or change back the settings i did.
(And of course seems like in bootloader mode, that windows can't find the phone).
So my Idea would be to flash a Zip.rom, like the over the air updates using the recovery option. It's just that i changed the CID to GOOGLE001. :/
Click to expand...
Click to collapse
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
rocktv88 said:
Yes, you can uninstall it or use MSCONFIG to remove it on start up. : )
ok, have you try boot the phone in fastboot mode and type "fastboot devices" in command prompt?
Click to expand...
Click to collapse
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
TomFader said:
Jep, so what i do is, i power the phone on, it boots into stock android --> adb devices works and retunrs my phonenumber (also the windwos driver is fine while in stock android)
i do adb reboot-bootloader and it starts into the bootloader (fastboot is turned off in the settings)
and then I'm stuck, Windows can't find the phone (get a bunch of errors with unsopoorted usb device)
also adb devices and fastboot devices is not working, so i tried to execute different commands like flashing or oem unlock,
but all i get is the message<waiting on device>
Click to expand...
Click to collapse
Are you on S-off?
Anyway, I would do the RUU. restore your phone and try again with a good custom ROM. Did you check MD5 with the rom you download? You still can connect your phone with ADB. That mean your phone is not brick yet. : )
TomFader said:
Okay so i tried to install a custom rom, but it failed, now when ever i execute adb reboot-boatloader the device goes into the boatloader but i can't use adb/fastboot as it doesn't recognize the device. I have windows 8, and it seems windows doesn't find the driver, but when I boot the phone normaly, i can access it using adb (but not fastboot). Any ideas ?
I still can execute the recovery option in the boot loader, but i have nor Zip file to install. I also changed the cid, so the stock rom won't flash.
Advice appreciated
Click to expand...
Click to collapse
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
clsA said:
windows 8.1 will not work on hboot below 1.54.000 (the only 1.54 that works is from the new GPE 4.4 update).
your going to need access to a windows 7 PC long enough to update your hboot to 1.55 to be able to use fastboot with your phone again. This usually only happens while flashing a RUU not A Rom. Flashing a rom will not affect your version of hboot
Click to expand...
Click to collapse
You are right, i can confirm hboot 1.54.0000 - i was flashing the RUU to convert my HTC ONE toa Google Edition.
So all I need is a windows 7 or lower pc to get fastboot running again?
That's good news, I would have searched for ages.
Yeah it's frustrating I know
If you use the 1.54.000 from the 4.4 GPe update it works also
Sent from my HTC One using Tapatalk

Help please I bricked my htc one

hello everyone
I was having kik kat ROM on my htc one, firmware was latest 4.06.1540.2 also TWRP v2.6.3.3 and every thing was perfect
accidentally I BOOT TO RECOVERY and wipe then advanced wipe and then I select partitions : dalvik cache, system , cache, data, internal storage
I delete every thing in my device except TWRP v2.6.3.3
I tried to reboot and then a message says no OS system in your device device stack on HTC logo , and also your device doesn't appear to be rooted install super su now? tried to connect to computer but my computer cannot recognize my device I try htc sync but nothing
I'm running windows 8.1 enterprise in my computer
now when boot to bootloader this is what I get :
tampered
unlocked
m7_ul pvt SHIP S-OFF RH
CID-HTC_J15
HBOOT- 1.44.0000
RADIO-4A.22.3263.14
OPEN DSP - v26.120.274.0202
eMMC-boot
may 3 2013,17:22:59
my device downgrade the firmware and radio
please help me
If you know how to use adb you can push a ROM manually and flash it provided you still can boot recovery.
tiny4579 said:
If you know how to use adb you can push a ROM manually and flash it provided you still can boot recovery.
Click to expand...
Click to collapse
the problem is my computer cannot recognize my device tried to install htc sync drivers but fail to recognize my device
even I tried tool kit to bush a ROM to my device but still no device detected
Go to pc windows 7
paris07121978 said:
Go to pc windows 7
Click to expand...
Click to collapse
what do mean
dida1 said:
hello everyone
I was having kik kat ROM on my htc one, firmware was latest 4.06.1540.2 also TWRP v2.6.3.3 and every thing was perfect
accidentally I BOOT TO RECOVERY and wipe then advanced wipe and then I select partitions : dalvik cache, system , cache, data, internal storage
I delete every thing in my device except TWRP v2.6.3.3
I tried to reboot and then a message says no OS system in your device device stack on HTC logo , and also your device doesn't appear to be rooted install super su now? tried to connect to computer but my computer cannot recognize my device I try htc sync but nothing
I'm running windows 8.1 enterprise in my computer
now when boot to bootloader this is what I get :
tampered
unlocked
m7_ul pvt SHIP S-OFF RH
CID-HTC_J15
HBOOT- 1.44.0000
RADIO-4A.22.3263.14
OPEN DSP - v26.120.274.0202
eMMC-boot
may 3 2013,17:22:59
my device downgrade the firmware and radio
please help me
Click to expand...
Click to collapse
your not telling the whole truth
it's impossible to get hboot 1.44.000 without flashing it in fastboot oem rebootRUU or you never had 4.06.1540.2
you did all this by yourself ? Installed 4.06.1540.2 and Kitkat Rom ?
clsA said:
your not telling the whole truth
it's impossible to get hboot 1.44.000 without flashing it in fastboot oem rebootRUU or you never had 4.06.1540.2
you did all this by yourself ? Installed 4.06.1540.2 and Kitkat Rom ?
Click to expand...
Click to collapse
first of all am not a laying
see my thread before
http://forum.xda-developers.com/showthread.php?t=2560688
if you are not able to help just go away
dida1 said:
first of all am not a laying
see my thread before
http://forum.xda-developers.com/showthread.php?t=2560688
if you are not able to help just go away
Click to expand...
Click to collapse
well that's just it
I can help but you have to tell how you got hboot 1.44.000
---------- Post added at 10:00 AM ---------- Previous post was at 09:47 AM ----------
dida1 said:
what do mean
Click to expand...
Click to collapse
He means that fastboot will not work in windows 8.1 on a hboot 1.44.000
you have to have a windows 7 pc to use fastboot now
clsA said:
well that's just it
I can help but you have to tell how you got hboot 1.44.000
---------- Post added at 10:00 AM ---------- Previous post was at 09:47 AM ----------
He means that fastboot will not work in windows 8.1 on a hboot 1.44.000
you have to have a windows 7 pc to use fastboot now
Click to expand...
Click to collapse
exactly
clsA said:
well that's just it
I can help but you have to tell how you got hboot 1.44.000
Click to expand...
Click to collapse
here what I did
1- I connect my phone to my com.and delete some file from the phone storage like pictures videos folders etc...
2- I reboot my phone to recovery >wipe > advanced wipe>select all partitions and wipe
3- reboot system I had a message no os system rebooot
4 - my phone stack on htc logo
5- reboot to bootloader and this what I get in screen
tampered
unlocked
m7_ul pvt SHIP S-OFF RH
CID-HTC_J15
HBOOT- 1.44.0000
RADIO-4A.22.3263.14
OPEN DSP - v26.120.274.0202
eMMC-boot
may 3 2013,17:22:59
5- through the tool kit I try to flash RUU ROM but failed
this the hole story
sorry to be road with you but you made me angry I asked for help but you call me a lay
clsA said:
well that's just it
I can help but you have to tell how you got hboot 1.44.000
---------- Post added at 10:00 AM ---------- Previous post was at 09:47 AM ----------
He means that fastboot will not work in windows 8.1 on a hboot 1.44.000
you have to have a windows 7 pc to use fastboot now
Click to expand...
Click to collapse
How about windows xp
I have lap top with xp
how can I get my phone back to live
what do I need?
help please
dida1 said:
here what I did
1- I connect my phone to my com.and delete some file from the phone storage like pictures videos folders etc...
2- I reboot my phone to recovery >wipe > advanced wipe>select all partitions and wipe
3- reboot system I had a message no os system rebooot
4 - my phone stack on htc logo
5- reboot to bootloader and this what I get in screen
tampered
unlocked
m7_ul pvt SHIP S-OFF RH
CID-HTC_J15
HBOOT- 1.44.0000
RADIO-4A.22.3263.14
OPEN DSP - v26.120.274.0202
eMMC-boot
may 3 2013,17:22:59
5- through the tool kit I try to flash RUU ROM but failed
this the hole story
sorry to be road with you but you made me angry I asked for help but you call me a lay
Click to expand...
Click to collapse
no problem
what was the exact error from the RUU
and where you did download it.
also now that the RUU has changed your hboot you need a windows 7 pc to fix it now
and my intention was not to insult you. I just need the whole story
clsA said:
no problem
what was the exact error from the RUU
and where you did download it.
also now that the RUU has changed your hboot you need a windows 7 pc to fix it now
and my intention was not to insult you. I just need the whole story
Click to expand...
Click to collapse
thank you my friend
can I have the instruction how to do that now I asked my friend to get his lap top with windows 7
dida1 said:
thank you my friend
can I have the instruction how to do that now I asked my friend to get his lap top with windows 7
Click to expand...
Click to collapse
this file should get you back to stock from a windows 7 pc
install htc sync drivers first on the laptop and be sure fastboot devices works before continuing on.
then run the command fastboot oem lock before starting the RUU. this relocks the bootloader
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after the RUU finished you will have to start from scratch and unlock bootloader and install custom recovery and Root
clsA said:
this file should get you back to stock from a windows 7 pc
install htc sync drivers first on the laptop and be sure fastboot devices works before continuing on.
after installing the htc sync should I delet the sync and keep drivers
then run the command fastboot oem lock before starting the RUU. this relocks the bootloader
http://www.htc1guru.com/dld/ruu_m7_...1-27_10-31-1131-05_release_310878_signed-exe/
after the RUU finished you will have to start from scratch and unlock boot loader and install custom recovery and Root
Click to expand...
Click to collapse
so first I install htc sync then connect my phone to pc then run command fast boot devices
then lock device
start to unlock boot loader .... etc...
dida1 said:
so first I install htc sync then connect my phone to pc then run command fast boot devices
then lock device
start to unlock boot loader .... etc...
Click to expand...
Click to collapse
yeah
lock
then RUU
then boot phone make sure it works
then start over with the unlock from htcdev
clsA said:
yeah
lock
then RUU
then boot phone make sure it works
then start over with the unlock from htcdev
Click to expand...
Click to collapse
thank you
sorry for bothering you
please keep checking my thread I may need some help?
dida1 said:
thank you
sorry for bothering you
please keep checking my thread I may need some help?
Click to expand...
Click to collapse
here you go
Instructions for Flashing RUU Zip Files:
Download the RUU.zip file and place in your ADB/fastboot folder. I would recommend renaming the zip file to something simple like ruu.zip.
Boot your phone into the bootloader by holding the power and vol up/down buttons at the same time until you see the bootloader screen or if you have your phone booted you can use the ADB command:
adb reboot-bootloader
Now use these fastboot commands:
fastboot oem rebootRUU
Should see the Silver HTC logo. Now issue this command to flash your phone using the ruu.zip file:
fastboot flash zip ruu.zip
Now the first time you issue a command to flash firmware/ruu in fastboot it only prepares the flash. You have to issue the exact command again:
fastboot flash zip ruu.zip
The green status bar usually does not reach the 100% mark. When the output in the command window is complete, you can reboot:
fastboot reboot
Click to expand...
Click to collapse
clsA said:
here you go
Click to expand...
Click to collapse
FINALLY :victory:
MY DEVICE WAKE UP :good:
here is the picture
what is the next step
please help I don't want to do another mistake
waiting your support
I update the ROM to the latest saftware
I'm trying to install super su but I have this error see attached
how can I solve it
I want to flash the latest firmware and kit kat ROM
dida1 said:
FINALLY :victory:
MY DEVICE WAKE UP :good:
here is the picture
what is the next step
please help I don't want to do another mistake
waiting your support
I update the ROM to the latest saftware
Click to expand...
Click to collapse
Well I guess it depends on what you want to do.
the next step for me would be to unlock at htcdev and install custom recovery and root.
you already have s-off so your ahead of the game
Flash this in recovery

Cannot change CID back from SuperCid

Hi all, I have a tricky problem, I converted my M7 to GPE following this thread "[RUU] Google Edition Conversion. 5.0.1 RUU Zip pre-rooted/non-rooted + firmware ". All went fine but in the end the GPE lacks some stuff that I really like on Stock. Long story short I wanted to go back to stock, so I followed the part in the thread refffering to GPE => Stock
Prerequsites:
S-off
1.44 HBoot
RUU for your device (I used )
Ok I thought reversing since I had S-off would be a simple affair and maybe I took a misstep along the way but I got it done.
Here's what worked FOR ME.
1) set CID to superCID
2) install the 1.44 Hboot in RUU mode (thanks SneakyGhost) http://d-h.st/qfc
3) install the RUU for your phone/carrier
Click to expand...
Click to collapse
I just forgot before the last fastboot reboot to change the CID from 11111111 to my cid.
I flashed the 7.19.401.2-FULL_STOCK_WIPE.zip using 1.44 Hboot. Now it is stuck at the HTC logo afterwards and keeps rebooting, and ends up in stock recovery the phone with the red triangle and exclamation sign.
I did a factory reset from fastboot and now i get the phone with the red triangle. which means it is in the stock recovery but something is wrong. I can manage it to put it in fastboot, but that is all.
Windows each time I connect the phone is no longer recognizing the device so adb fails (I assume because it is the wrong CID). It just says waiting for device and nothing happens further.
How do I change the CID if I cannot connect the device? Tricky ... I tried several adb drivers (I use win 8.1) like "minimal_adb_fastboot_v1.2_setup" and "Universal_Naked_Driver_0.72" . The best I got is a driver installed and showing in device manager but with message " device cannot start. (Code 10)".
Any help is really appreciated.
Best regards
gmariust said:
Hi all, I have a tricky problem, I converted my M7 to GPE following this thread "[RUU] Google Edition Conversion. 5.0.1 RUU Zip pre-rooted/non-rooted + firmware ". All went fine but in the end the GPE lacks some stuff that I really like on Stock. Long story short I wanted to go back to stock, so I followed the part in the thread refffering to GPE => Stock
I just forgot before the last fastboot reboot to change the CID from 11111111 to my cid.
I flashed the 7.19.401.2-FULL_STOCK_WIPE.zip using 1.44 Hboot. Now it is stuck at the HTC logo afterwards and keeps rebooting, and ends up in stock recovery the phone with the red triangle and exclamation sign.
I did a factory reset from fastboot and now i get the phone with the red triangle. which means it is in the stock recovery but something is wrong. I can manage it to put it in fastboot, but that is all.
Windows each time I connect the phone is no longer recognizing the device so adb fails (I assume because it is the wrong CID). It just says waiting for device and nothing happens further.
How do I change the CID if I cannot connect the device? Tricky ... I tried several adb drivers (I use win 8.1) like "minimal_adb_fastboot_v1.2_setup" and "Universal_Naked_Driver_0.72" . The best I got is a driver installed and showing in device manager but with message " device cannot start. (Code 10)".
Any help is really appreciated.
Best regards
Click to expand...
Click to collapse
If you have flashed hboot 1.44 to your device then you'll need to get your hands on a windows 7 PC, ubuntu or Mac. Hboot 1.44 won't work with win8. Once done post the output of "fastboot getvar all"
alray said:
If you have flashed hboot 1.44 to your device then you'll need to get your hands on a windows 7 PC, ubuntu or Mac. Hboot 1.44 won't work with win8. Once done post the output of "fastboot getvar all"
Click to expand...
Click to collapse
Thanky you for your quick reply, I suppose it needs to be a real ubuntu machine, cannot use a vmware machine
gmariust said:
Thanky you for your quick reply, I suppose it needs to be a real ubuntu machine, cannot use a vmware machine
Click to expand...
Click to collapse
It will not work in a vm config but will work fine in live mode (you can use Ubuntu without installing it via a live usb or live cd option)
Cool man, this one worked, I managed to change the CID back to the original. I have flashed then, the recovery to twrp and installed the following Guru Reset file "Guru_Reset_M7_3.62.401.1.zip". Is a bit old but nothing that OTA will not solve. Thanks again! It's updating already!

Categories

Resources