Related
I have got an issue with HTC incredible S going in boot loop. The phone is 2 yrs old and was running fine with official ICS installed on it. One fine day it just hung and after restart went into bootlaoder.
HBOOT is unlocked, rooted, and S-ON
HBOOT-2.02.002
RADIO-3831.18.00.11_M
I have tried a lot of things like stock ICS rom, recovery cleanup, cache+dalvik clean-up using recovery, RUU installation etc.
However, it refuses to get repiared . It runs fine for say a day after stock rom update and then starts throwing exception like process android.acore.*** has stopped or similar and after restart again goes to bootloader.
I have tried different RUUs, however, none of theme seems to support and some say error 171 related to customer Id.
Tried to create goldcard but revskills site is down.
So bottomline is I have tried everything possible, and now I think my phone is bricked
Any other suggestions you may have?
Anyone?????? EXperts PLLLLLLLLLZZZZZZ help me out.......................
Whoa !!! Where've all the experts gone ........
Flash boot.img manually..
Fastboot flash boot boot.Img
This ll be inside ur Rom zip :thumbup:
Just in case if u ve forgotten to boot
Sent from my Incredible S
---------- Post added at 11:13 PM ---------- Previous post was at 11:01 PM ----------
If you have a custom recovery installed.. wipe all except your SD.. and then flash a custom Rom and flash boot.img manually as you are S-on. And restart..
Sent from my Incredible S
Thanks for the reply mafie!!!
I had tried it but just wanted confirm it and just connected my IncS to laptop and ou know what ??? my handy is not getting detected... all I can see is
123456789012 fastboot
Is my phone dead???
Fastboot get var all
Give some more info on your phone..
Sent from my Incredible S
Here it is
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.02.0002
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: 123456789012
(bootloader) product: vivo
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.008s
droidseeker1 said:
Here it is
finished. total time: 0.008s
Click to expand...
Click to collapse
1. take down all the imei and stuff like that cuz u really dont want other people to know that stuff.
2. Make sure adb and fastboot drivers are corrrectly installed
3. If its properly installed and you say ure computer can't detect your device, how did u enter command fastboot getvar all??? Is your computer detecting your device properly?
072665995 said:
1. take down all the imei and stuff like that cuz u really dont want other people to know that stuff.
2. Make sure adb and fastboot drivers are corrrectly installed
3. If its properly installed and you say ure computer can't detect your device, how did u enter command fastboot getvar all??? Is your computer detecting your device properly?
Click to expand...
Click to collapse
Hmm sorry for the confusion, but what I meant by *not detecting* was computer is not properly recognizing it properly.
it is running all the fastboot commands but serial id is shown as 123456789012 and charging light is not turning on.
meanwhile, i checked the drivers and they look good to me....
I am worried now
F5 ... Please help me guys....
droidseeker1 said:
F5 ... Please help me guys....
Click to expand...
Click to collapse
So from bootloader can you go to recovery?
poondog said:
So from bootloader can you go to recovery?
Click to expand...
Click to collapse
Sorry couldn't reply .. wasn't wired lately ....
No ... I am not able to go to Recovery and can not even flash it as whenever I try to flash it, it says something about writing error (Perhaps it is because of phone not being recognized)
I am unable to write any thing via bootloaders (i.e. recovery, zip, ruu etc) i have also tried to restore my phone via RUU...setup is shutting down the device but do not boot it up again in bootloader so the setup could proceed with flashing the RUU (as it suppose to)... i m uploading the cmd screen shot for your kind perusal, kindly help me out as well please...
these steps i have tried as yet:
tried (fastboot flash recovery twrp.img)
Tried Flashing OTA firmware (fastboot update firmware.zip)
Tried RUU.exe setup
i can not even flash recovery... whenever i attempt to do so it gives an error as attached!
seems like some sort of security has been activated but can be a hardware issue as well... Please HELP!
Please advise what should i do or what can be done in this matter
Have you tried fastboot erase cache
Sent from my HTC One using XDA Premium 4 mobile app
Try going s off
Sent from my GT-I9305 using xda app-developers app
bored_stupid said:
Have you tried fastboot erase cache
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did... command is not implementing... giving out same error as on recovery flsah!
Thanks... will appreciate more help...
nateboi81 said:
Try going s off
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
i have tried that...
my set is only responding to informational commands like getvar info, device info etc but its not implementing the commands which will write something on internal memory...
s-off = Security off right?
i believe some sort of security has been triggered!
?
Any One please....
Just a couple of shots in the dark.. disable any antivirus also check you have latest fastboot maybe download latest android sdk which will have it and try again.
Try another pc or cable.
Sent from my HTC One using Tapatalk
Mortal Eternity said:
Any One please....
Click to expand...
Click to collapse
are you using USB 3 port/hub, check Device Manager connections... if the "main" (internal) port-structure is USB 3 based, then that could be the problem.
PS: and what version does adb devices give?
nkk71 said:
are you using USB 3 port/hub, check Device Manager connections... if the "main" (internal) port-structure is USB 3 based, then that could be the problem.
PS: and what version does adb devices give?
Click to expand...
Click to collapse
I can offer 20$ for who ever can help me fix my set please...(i know its too low but its all i have for now and i need my cellphone fixed to sale it)
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35FW902658
(bootloader) imei: 355972054420881
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4157mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.342s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>
Mortal Eternity said:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot erase cache
erasing 'cache'...
FAILED (remote: erasing error!)
finished. total time: 1.342s
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>
Click to expand...
Click to collapse
what was the last thing the phone had on it ? I see the bootloader is unlocked so did it already have a custom recovery ? custom rom ? Rooted ?
have you turned the phone completely OFF holding the powerbutton and volume up and down for 2 min ?
did you try a factory reset with stock recovery ?
when you tried the RUU.exe what was the error and what file did you try ?
clsA said:
what was the last thing the phone had on it ? I see the bootloader is unlocked so did it already have a custom recovery ? custom rom ? Rooted ?
have you turned the phone completely OFF holding the powerbutton and volume up and down for 2 min ?
did you try a factory reset with stock recovery ?
when you tried the RUU.exe what was the error and what file did you try ?
Click to expand...
Click to collapse
thats how i messed my set up: i was on TWRP 2.6.3.3 which was working perfectly fine then i thought it would be better if i'd flash a latest recovery so flashed 2.7.0.4 then i tried to flash latest build of insertcoin with that messed up recovery which got me stuck on 7% while flashing the rom, so i restarted by set after waiting for 5 minutes or so... then i tried going in to recovery again and tried to do a factory data reset to reflash the rom... recovery stuck on factory data rest n made me reboot my set... since then the situation is same for me
i did the 2 minutes trick, since my phone is not hard bricked so its just making the set booting again and again in fastboot mode thats it!
yes i did factory reset but with twrp then i got stuck at where i m now... plus i m unable to flash anything on emmc since then...
when i tried RUU.exe the setup shut my phone down but do not restart it in fastboot mode (how it should) i tried to boot my phone manually but didnt help...
Please advice any thing else
2.7.0.4 is for Sprint
Can you force the phone into fastboot oem rebootRUU and try and flash from their?
you can extract the signed Rom.zip from the RUU and flash it that way
the Rom.zip will be in c:\users\yourusername\appdata\local\temp\somerandomfolderthatwasjustcreated (sort by date)(also you have to view hidden folders to see appdata in the user folder)
mine was here "C:\Users\Cliff\AppData\Local\Temp\{A3096E6D-C55A-4EA1-B6B1-1E95174B190C}"
clsA said:
2.7.0.4 is for Sprint
Can you force the phone into fastboot oem rebootRUU and try and flash from their?
you can extract the signed Rom.zip from the RUU and flash it that way
the Rom.zip will be in c:\users\yourusername\appdata\local\temp\somerandomfolderthatwasjustcreated (sort by date)(also you have to view hidden folders to see appdata in the user folder)
mine was here "C:\Users\Cliff\AppData\Local\Temp\{A3096E6D-C55A-4EA1-B6B1-1E95174B190C}"
Click to expand...
Click to collapse
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Click to expand...
Click to collapse
I think your emmc has bad sectors. Whats wrong with htc one? So many bricks because of bad dmmc chip. Jesus
Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
No i can't bro... it says this when i tried to run the command:
C:\Users\Mortal Eternity\Desktop\Fastboot-Win>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
(bootloader) SD: write failed in CMD25.
OKAY [ 1.060s]
finished. total time: 1.061s
Thank you for helping me...
Click to expand...
Click to collapse
Have you at least tried a different PC and/or OS? I remember one guy having tonnes of problems (and we spent hours on teamviewer too), not being able to get anything to work, until we found out that even his USB2 port is based on an internal USB3 connection... he then used a different PC and was up and running again!
Mortal Eternity said:
i flashed the recovery from this thread: http://forum.xda-developers.com/showthread.php?t=2708134 (its not for sprint only - at least its not written in this thread)
...
Click to expand...
Click to collapse
Thanks for posting the link .. i was not aware of that file.
I think I would still try and flashback to 2.6.3.3 ... if you can get back in TWRP
try this file >> https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
clsA said:
Thanks for posting the link .. i was not aware of that file.
I think I would still try and flashback to 2.6.3.3 ... if you can get back in TWRP
try this file >> https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
Click to expand...
Click to collapse
recovery is not accessible... when ever i select the recovery option the set gets unresponsive
can't even factory data reset my phone... sent an email to htc saying if they can replace my set i will pay 100$ t has been 2 days, still waiting for their reply...
lets hope for best :fingers-crossed:
nkk71 said:
Have you at least tried a different PC and/or OS? I remember one guy having tonnes of problems (and we spent hours on teamviewer too), not being able to get anything to work, until we found out that even his USB2 port is based on an internal USB3 connection... he then used a different PC and was up and running again!
Click to expand...
Click to collapse
thanks for your suggestion but its not the cable or port issue i have tried 5 different pcs... i have even visited local market for solution... no one has any solutions for this as yet... but there are many phones with same case... it seems like a hardware flaw at htc's end.
p.s. i m really very thankfull to people who are trying to help me!
darksnoopy said:
I think your emmc has bad sectors. Whats wrong with htc one? So many bricks because of bad dmmc chip. Jesus
Click to expand...
Click to collapse
yes it seems like a common issue to me now... lets hope htc will take some precaution while making such expensive phones...
Mortal Eternity said:
yes it seems like a common issue to me now... lets hope htc will take some precaution while making such expensive phones...
Click to expand...
Click to collapse
Tell me about it! I got an new m7 again (i hate m8 design) but this time i am not going to unlock boot loader not going to s-off and not going to install custom recovery!
This is the thread with the problem i had with my first m7. I haven't quit, still trying to fix it and give it away. Maybe we should make a sticky thread with all those people with problem like this!
http://forum.xda-developers.com/showthread.php?t=2685024&page=3
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
zzmike76 said:
Hello
I'm struggling since some days with my One M7 and since I'm not an expert I'm asking for some help..
I have unlocked the phone, installed twrp and by mistake wiped the os, so the phone doesn^t boot anymore. I would like to restore the original settings before trying again to root and install a custom rom.
The problem is that my phone is currently recognized only by fastboot and not by adb, tried several times with different usb cables and os (Win and mac) without success.
my understanding is that the only way to restore the os is via an official RRU.exe (as the device is s-on),am i correct?
Here the details
hboot 1.57.0000
radio 4t.28.3218.04
Opendsp v32.120.274.0909
I downloaded a RUU.exe but getting a security fail message in bootloader, again my understanding is that the image signature is wrong ? which ruu.exe can I use to successfully restore my device ?
many thanks in advance and best regards
Michele
Click to expand...
Click to collapse
Right first of all adb commands wont work in the bootloader so stop trying different cables etc as your wasting your time, adb is only for when your in a booted rom or in recovery, fastboot commands are for the bootloader.
Next please post your fastboot getvar all without imei and serial number.
also, if you intend on going to a custom rom, there is no point flashing an RUU, you are already halfway there to flashing a custom rom, so which rom do you want to flash ?
hello
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thanks and regards
michele
zzmike76 said:
hello
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP110
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
thanks and regards
michele
Click to expand...
Click to collapse
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Seanie280672 said:
I can tell you now with a CID of VODAP110 there is no RUU for your phone, I used to have a TWRP backup for vodaphone, that was a long time ago before I got s-off, i'll have a look through and see if I can find it, which custom rom do you want to flash ?
Click to expand...
Click to collapse
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
zzmike76 said:
well, actually I would be happy to have my mobile booting again
as I'm not an expert I would kindly ask you for any suggestion for custom roms
thanks a lot!
Michele
Click to expand...
Click to collapse
Rom suggestions are not allowed.
Put TWRP 2.6.3.3 on your phone if you don't already have that version, it must be that version, I know its a bit old but its still the best for sense based rom's, you can get it from here: http://techerrata.com/browse/twrp2/m7
place the img file in the same folder as your adb and fastboot files on your computer then open a command windows from there and with your phone plugged in and fastbootUSB showing on your phone, issue the following commands
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
then download this file, this is stock unbranded rom: http://www.androidrevolution.org/downloader/download.php?file=One_6.09.401.12_odexed.zip re-name it to rom.zip and place it in the same folder as adb and fastboot on your computer, then enter recovery on your phone, just the main screen no sub menu's, and then open a cmd window on your computer from the adb/fastboot folder and with your phone plugged into the computer type this command:
Code:
adb push rom.zip /sdcard/
it will appear unresponsive for quite a while, just leave it alone, takes about 5 mins to push the file but it will let you know when its done.
unplug your phone and flash the rom, when its finished reboot your phone and set it all up.
when everything is done that you want done to it, boot back into recovery and select reboot - system, it will say your rom is not currently rooted, do you want to install SuperSU now, select yes if you want root, your phone will then boot back up, follow the instructions on your phone screen when it boots back up, simple as that to root.
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
zzmike76 said:
thanks for the information, i downgraded twrp to the suggested version but when entering recovery mode i cannot see the phone with the command adb devices...i noticed that when i plug the phone in windows for few seconds show the phone in device manager with name My HTC under android usb devices but then it disappears
i installed the latest htc drivers but still no phone detection
Click to expand...
Click to collapse
that's strange that it pops up and then disappears, are you using the original HTC cable, or try a different one, also make sure HTC Sync is uninstalled, just leave the drivers on your computer, you will need to restart after uninstalling HTC Sync.
Sounds more like a computer issue to me than the phone.
Do you have a USB OTG cable you can use ?
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
zzmike76 said:
original cable (tried also with another one), htc synch uninstalled 8and rebooted), driver version is 2.0.7.23
strang ething it appens on mac as well
i have no otg cable, if i buy one could it solve the issue ?
Click to expand...
Click to collapse
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Seanie280672 said:
yes, you just copy the rom.zip to a memory stick, plug it into one end of the otg cable and the other end into your phone, does away with the use for a computer.
my driver is 2.0.7.28
could be your adb and fastboot, you could always try mine, link below
just find it very strange that it see's it, and then it disappears, ive never experienced anything like this happening to me, yet fastboot works fine, its got to be your drivers, you may have to force your driver in device manager whilst in recovery on your phone, are you using windows 8 ?
Click to expand...
Click to collapse
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
zzmike76 said:
no windows 7 , this evening will try with an old xp laptop..but on the mac as well i can only see the device in fastboot
is there away to reformat the sdcard from twrp ? maybe it is damaged
Click to expand...
Click to collapse
inside twrp you can select wipe and then format data, that will wipe everything all partitions etc, you shouldn't be having any problems with windows 7 though.
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
zzmike76 said:
update..bought an otg cable and was able to restore the image you sent me...MANY THANKS !!
still the device does not show on windows (there must be some driver issue), but now adb commands work on my mac (yesterday they didn't) so i have a working environment
need to understand how to s-off on mac , is it possible or windows is required ?
thanks again for your support!
Click to expand...
Click to collapse
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Seanie280672 said:
the only way to s-off on your current HBOOT is to use sunshine, your best off connecting your phone to wifi and download it straight to your phone as its an apk file actually for your phone, not to be run from the computer, it will check your phone first to see if it can be s-off'd and if it can then you'll have to pay $25 though paypal etc, it will then proceed, its well worth it, you can get rid of that vodaphone branded rubbish straight away and flash any RUU should you come stuck again, I paid to have mine done in a shop in Sheffield before sunshine came about and firewater didn't work.
http://theroot.ninja/
Click to expand...
Click to collapse
another update....it seems that after a while the phone is entering the usb host adapter mode and refuses to charge/being detected by mac/pc..at least i now can see the warning within the phone..now reading this thread http://forum.xda-developers.com/showthread.php?t=2481211
will try again to wipe everything and reinstall to see whether windows can detect it just for s-offing the phone
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__203
(bootloader) battery-status: good
(bootloader) battery-voltage: 4138mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
Here informations you might need
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
usb debugging has nothing to do with the bootloader, adb or fastboot, it is only required to be on when you want to mod something or control your phone using adb commands inside a booted rom, as you cant boot, then that's not an option.
if your bootloader is locked and you have warranty, send it back, because if you unlock your bootloader then your warranty will be void and you'll have to pay for repairs.
Hi there & thnx for your concern,
The warranty is not an option , cause I bought it in another country and have no service support here.
For the usb debugging mode , as far as I know , it needs to be "on" so the smartphone can be connected to adb.
I looked on the net how to turn it on without having access to android I got some command but I need an android command-line shell to make it work , wich is not an option right now.
I'm all open for suggestions.
Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .
Rave201 said:
Is there a way to get out of fastboot and try load the android again ?
I tried turn power down but it opens fastboot automaticly,
I tried
Code:
fastboot reboot
same result as above .
Click to expand...
Click to collapse
only thing you can do is unlock your bootloader, try again, get a new unlock token from HTC Dev.
by the way, adb commands are only for in a rom or in recovery, use fastboot commands only in the bootloader, if you cant unlock the bootloader then theres not a lot you can do.
could you post your fastboot getvar all please, remove imei and serial number information before posting, maybe there is an RUU we can run.
Rave201 said:
Hello there ,
So just so you know I've looked hours in other threads to check answers before posting my own.
I have an HTC One M7 who was stuck on bootloop , I entered the fastbood mode now it is stuck on it.
the HTC is "Locked" "S-ON" and on official rom.
the probleme is USB Debogging is OFF so I can't use ADB
But Fastboot is working fine
Recovery is not working (nothing loads just restarts)
so there is nothing I can do now (can't flash recovery , can't unlock bootloader) , I tried the HTCDev method but nothing prompt After I send the bin file.
I know that everybody's request is important , but I realy can't handle losing this smartphone , only had it for a couple of months and it's a disaster if it ever happens to be lost.
Click to expand...
Click to collapse
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Now try the RUU again
clsA said:
boot the phone to the bootloader / Fastboot USB
plug the phone to the PC and Flash this RUU >> http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
If you get an Error flashing 155 etc)
flash this firmware first >> http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/4.19.401.8.zip
place the file in your fastboot folder on your PC and rename it firmware.zip and flash it with a command prompt
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
Click to expand...
Click to collapse
lol how I missed that I don't know
Thanks ! : downloading , I'll leave answer after I test.
Hi again ;
So I downloaded and followed the steps I got errors :/
on the RUU flash I got Error 171 at "Bootloader waiting" and later saying that it couldn't connect to the device . It did connect to it in the first place though and device rebooted and so .
So I followed the second parts and I got errors aswell :
Code:
c:\mini-sdk>fastboot oem rebootRUU
...
(bootloader) [ERR] Cmd18 polling status timed out, MCI_STATUS: 0x4C2000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) CMD18: cmd failed
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(862): error 2
(bootloader) Start Verify: 3
(bootloader) [ERR] Cmd25 polling status timed out, MCI_STATUS: 0x4C0000
(bootloader) [ERR] sdcc_command: sdcc_poll_status error, rc: 2
OKAY [ 0.016s]
finished. total time: 0.016s
c:\mini-sdk>fastboot flash zip firmware.zip
sending 'zip' (43508 KB)...
OKAY [ 2.870s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
FAILED (remote: not allowed)
finished. total time: 6.538s
Any help please
anyone ?
Rave201 said:
anyone ?
Click to expand...
Click to collapse
bootloader needs to be locked / relocked to flash the RUU or firmware as your s-on.
"fastboot oem lock" is the command without quotes.
Hi there, I did it already , it says device already locked.
Rave201 said:
Hi there, I did it already , it says device already locked.
Click to expand...
Click to collapse
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?
Seanie280672 said:
soz about that, just realised, had a read back through the whole thread to catch up, right, 171 is a USB connection error, so when your phone is in the bootloader, plugged into the computer with fastboot usb showing, have a look in device manager and make sure your computer can see your phone and that you dont have anything like "One" with a yellow exclamation mark.
sounds like a driver problem to me, but are you using the original HTC cable too ?
Click to expand...
Click to collapse
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up
Rave201 said:
Yeah , well I tried like 4 drivers already , fastboot usb is indeed showing, and the RUU does restart the device , but when waiting for bootloader nothing shows =/
Tried with different pc too with different compatiblities.
Only thing left to try is another cable.
Thnx for following up
Click to expand...
Click to collapse
what I meant was when fastboot usb is showing, have a look in windows device manager and make sure it see's your phone, should say MyHTC.
only drivers you need which have never let me down, even on Windows 10 is HTC sync manager, just download and install the latest version from the HTC site, I would uninstall all current phone drivers first, then run a cleaner like CCleaner to remove old files, reboot computer then install HTC sync manager, after the install, un-install HTC sync, just leaving HTC driver package above it alone.
make sure your phone is unplugged when doing the above, leave your phone in the bootloader, and when you have finished the last step of un-installing HTC sync, then plug your phone into the computer and let it load the fastboot driver, thats the main one you need right now.
Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?
Rave201 said:
Hi again , So I tried everything above and nothing , took the device to a guy who's good in repairing and flashing devices and couldn't flash it neither.
for a radical solution , should I change the whole mainboard or there is a specific part ?
Click to expand...
Click to collapse
It's a 2 year old phone, it's really only worth fixing if you already have the parts for free.
This phone sells for $149 New in the US, and even cheaper used on eBay.
Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.
Rave201 said:
Thanks for the advice , but more objectively Motherboard or a specific part ?
Parts here are pretty cheap compared. And I can't afford a new one actually.
Click to expand...
Click to collapse
SD_HW_ERROR = probably a defective emmc. You can't replace the emmc chip, its soldered directly on the Motherboard so you will indeed need to replace the motherboard but like clsA said it really doesnt worth it. You can get a new M7 for 150$. HTC sells their Motherboard around 100$ + you'll probably need to replace the body like many users who tried to open the phone themselves (very fragile around the volume rockers). Even if I love my M7, I wouldn't spent 100$ to replace the MB.
And buying a used motherboard is not a good idea. You don't know if its working good + you don't know if the IMEI is blacklisted.
Thanks for the explanation alray, I excpected the fail in the emmc too cause read_mmc emmc didn't work.
Anway I don't live in the us . Here though, a new one cost roughly 300 $ and the motherboard is about 80$ or less.
Thanks again
With my Htc One M7 802w, I tried to flash the stock google edition using this tutorial but I think i've bricked my device - it's almost completely dead - only fastboot is working but it also seems to be unrecognized :
F:\Android\ADB>fastboot devices
???????????? fastboot
Click to expand...
Click to collapse
Not able to go to "fastboot oem rebootRUU" ... the device is not found when sending this command.
Is there anyway to flash the stock ROM without fastboot mode - like some software or brushtool or whatever.
GETVAR:
F:\Android\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 3551*********10 (hide for security)
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 3385mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
F:\Android\ADB>fastboot flash hboot hboot_signedbyaa.img
target reported max download size of 452980736 bytes
sending 'hboot' (2047 KB)...
OKAY [ 0.109s]
writing 'hboot'...
FAILED (remote: not allowed)
finished. total time: 0.109s
Click to expand...
Click to collapse
F:\Android\ADB>fastboot oem lock
...
(bootloader) Device was already locked!
OKAY [ 0.000s]
finished. total time: 0.000s
Click to expand...
Click to collapse
NEED HELP!!!:silly:
hruaiapunte said:
With my Htc One M7 802w, I tried to flash the stock google edition using this tutorial but I think i've bricked my device - it's almost completely dead - only fastboot is working but it also seems to be unrecognized :
Not able to go to "fastboot oem rebootRUU" ... the device is not found when sending this command.
Is there anyway to flash the stock ROM without fastboot mode - like some software or brushtool or whatever.
GETVAR:
NEED HELP!!!:silly:
Click to expand...
Click to collapse
omg looks like you did everything possible to brick your phone. Yuu can't use RUU for the M7_UL on a dual sim phone. Now you have the wrong bootloader, an incorrect MID and a missing CID. You must restore your original MID and CID and flas the correct dual sim RUU.
btw it looks like you missed the last step of your guide:
Step 8: Enjoy S-OFF! But Be Careful...
Having S-OFF will let you trick your HTC One into installing other phones' RUU files. As long as you only install compatible RUUs, you should be fine, but make sure to double check. This is how real bricks happen.
Click to expand...
Click to collapse
alray said:
omg looks like you did everything possible to brick your phone. Yuu can't use RUU for the M7_UL on a dual sim phone. Now you have the wrong bootloader, an incorrect MID and a missing CID. You must restore your orinial MID and CID and flas the correct dual sim RUU.
btw it looks like you missed the last step of your guide:
Click to expand...
Click to collapse
How to flash those original MID and CID? Is there a way to flash via software like ODIN or whatever...not just a fastboot mode? Thanks for your reply
hruaiapunte said:
How to flash those original MID and CID? Is there a way to flash via software like ODIN or whatever...not just a fastboot mode? Thanks for your reply
Click to expand...
Click to collapse
Odin is for samsung not htc. The corrupted CID/MID is probably caused by having the wrong bootloader on the phone. Normally you can change the CID using "fastboot oem writecid" command. The MID can be modified using a custom recovery. The MID might not be a problem for now since its all * but you'll definitively need to access RUU mode to flash the correct RUU
alray said:
Odin is for samsung not htc. corrupted CID/MID is probably caused by having the wrong bootloader on the phone. Normally you can change the CID using "fastboot oem writecid" command. The MID can be modified using a custom recovery. The MID might not be a problem for now since its all * but you'll definitively need to access RUU mode to flash the correct RUU
Click to expand...
Click to collapse
Yes, i know odin is for samsung, what i tried to say is that are there any flash tool, not through fastboot because as i already mentioned, computer cannot detect the device when
fastboot oem rebootRUU
Click to expand...
Click to collapse
command was given. It says
<waiting for device>
Click to expand...
Click to collapse
and i have to disconnect the USB cable. And then press a volume down+power button to enter fastboot mode again (when i perform this, the device does not power up, it for l goes directly to fastboot mode when pressing the key combination). And after plugin, the result was
*i didn't remember some* remote not allowed something like that
Click to expand...
Click to collapse
Anyway thanks for your response. Please give solution.
hruaiapunte said:
Yes, i know odin is for samsung, what i tried to say is that are there any flash tool, not through fastboot because as i already mentioned, computer cannot detect the device when
command was given. It says
and i have to disconnect the USB cable. And then press a volume down+power button to enter fastboot mode again (when i perform this, the device does not power up, it for l goes directly to fastboot mode when pressing the key combination). And after plugin, the result was
Anyway thanks for your response. Please give solution.
Click to expand...
Click to collapse
Theres no such tool for HTC phones, you must use fastboot. <waiting for device> when using fastboot commands means the computer doesn't detect the phone so even if there was a tool like Odin for HTC phones, it wouldn't work without being able to detect the phone. (there are actually some custom tools but they are only doing the fastboot commands for you by clicking a button instead of writing the commands yourself, they won't work if your phone isn't detected)
Usually, these fastboot connectivity issues are caused by using the wrong drivers, a bad usb cable, bad usb port etc. But i'm afraid that in your particular situation, your connectivity issue might be related to having the wrong bootloader installed on your phone variant. If this is the case, there is nothing you can do yourself. It might be recoverable using Jtag/ riffbox.
Still worth trying the usual troubleshooting (drivers, cables, ports(use only usb 2.0 btw). If you can get fastboot connectivity back, there are some (slim) chances to recover the phone, but without fastboot connectivity, like I said, there is nothing we can do.
alray said:
There no such tool for HTC phones, you must use fastboot. <waiting for device> when using fastboot commands means the computer doesn't detect the phone so even if there were a tool like Odin for HTC phones, it wouldn't work without being able to detect the phone. (there are actually some custom tools but they are only doing the fastboot commands for you by clicking a button instead of writing the commands yourself, they won't work if your phone isn't detected)
Usually, these fastboot connectivity issues are caused by using the wrong drivers, a bad usb cable, bad usb port etc. But i'm afraid that in your particular situation, your connectivity issue might be related to having the wrong bootloader installed on your phone variant. If this is the case, there is nothing you can do yourself. It might be recoverable using Jtag/ riffbox.
Still worth trying the usual troubleshooting (drivers, cables, ports(use only usb 2.0 btw). If you can get fastboot connectivity back, there are some (slim) chances to recover the phone, but without fastboot connectivity, like I said, there is nothing we can do.
Click to expand...
Click to collapse
Thanks for the clarification. I now have only one choice that is to send to the service center.