Hi all
Thanks in advance for any advice you give me.
I have a Droid Dna in Europe,and i'm not rooted or unlocked.I have a RUU,and the htc drivers on my Windows 8 laptop.And everytime i try it to run the RUU.exe he just returns the Error 158,and after that the phone reboots and returns to normal.
I think that we cant make the clean all data.
I try it everthing,even advanced settings,to the sign drivers on my Windows 8,stop the anti-virus,close all aplications that are running.shutdown the UAC on my pc.and running program with the administrative priviliges.
This is what my ruu log says:
***<LOG>
<T143439><INFO><VERSION>1.0.1.2013</VERSION></INFO></T143439>
<T143439><INFO>start read zip</INFO></T143439>
<T143439><INFO>The input file() DOES NOT exist.
</INFO></T143439>
<T143439><INFO>Finish read zip.</INFO></T143439>
<T143439><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T143439>
<T143447><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T143447>
<T143447><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143447>
<T143448><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143448>
<T143448><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143448>
<T143450><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143450>
<T143450><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143450>
<T143451><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143451>
<T143451><DEBUG><CMD>adb -s FA2CFS502308 shell cat /sys/class/power_supply/battery/capacity</CMD>
</DEBUG></T143451>
<T143451><DEBUG><OUT>88</OUT>
</DEBUG></T143451>
<T143451><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T143451>
<T143451><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143451>
<T143452><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143452>
<T143452><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143452>
<T143454><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143454>
<T143454><DEBUG><CMD>adb -s FA2CFS502308 shell getprop ro.build.description</CMD>
</DEBUG></T143454>
<T143455><DEBUG><OUT>1.15.605.4 CL123160 release-keys</OUT>
</DEBUG></T143455>
<T143458><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T143458>
<T143458><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143458>
<T143459><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143459>
<T143459><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143459>
<T143501><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143501>
<T143501><DEBUG><CMD>adb -s FA2CFS502308 shell getprop ro.build.description</CMD>
</DEBUG></T143501>
<T143502><DEBUG><OUT>1.15.605.4 CL123160 release-keys</OUT>
</DEBUG></T143502>
<T143521><DEBUG>signed rom
</DEBUG></T143521>
<T143521><DEBUG>(Encrypted) Main version: 2.06.605.1
</DEBUG></T143521>
<T143527><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T143527>
<T143527><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T143527>
<T143529><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T143529>
<T143529><DEBUG>signed rom
</DEBUG></T143529>
<T143529><DEBUG>getImageCount, nHR: 25
</DEBUG></T143529>
<T143529><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143529>
<T143530><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143530>
<T143530><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143530>
<T143531><DEBUG><OUT>List of devices attached
FA2CFS502308 device
</OUT>
</DEBUG></T143531>
<T143531><DEBUG><CMD>adb -s FA2CFS502308 shell /system/bin/reboot oem-78</CMD>
</DEBUG></T143531>
<T143532><DEBUG><OUT />
</DEBUG></T143532>
<T143532><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143532>
<T143533><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143533>
<T143533><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143533>
<T143534><DEBUG><OUT />
</DEBUG></T143534>
<T143535><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143535>
<T143536><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143536>
<T143536><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143536>
<T143537><DEBUG><OUT />
</DEBUG></T143537>
<T143537><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143537>
<T143538><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143538>
<T143538><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143538>
<T143539><DEBUG><OUT />
</DEBUG></T143539>
<T143539><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143539>
<T143540><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143540>
<T143540><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143540>
<T143541><DEBUG><OUT />
</DEBUG></T143541>
<T143541><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143541>
<T143542><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143542>
<T143542><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143542>
<T143543><DEBUG><OUT />
</DEBUG></T143543>
<T143543><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143543>
<T143544><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143544>
<T143544><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143544>
<T143545><DEBUG><OUT>FA2CFS502308 fastboot</OUT>
</DEBUG></T143545>
<T143545><DEBUG><CMD>fastboot -s FA2CFS502308 getvar boot-mode</CMD>
</DEBUG></T143545>
<T143546><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T143546>
<T143546><DEBUG><CMD>fastboot -s FA2CFS502308 erase cache</CMD>
</DEBUG></T143546>
<T143547><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T143547>
<T143547><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T143547>
<T143549><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T143549>
<T143549><DEBUG>signed rom
</DEBUG></T143549>
<T143549><DEBUG>getImageCount, nHR: 25
</DEBUG></T143549>
<T143549><DEBUG><CMD>fastboot -s FA2CFS502308 flash zip "C:\Users\Pedro Fernandes\AppData\Local\Temp\{DE245328-387A-414E-949B-A5D47C647CA9}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip"</CMD>
</DEBUG></T143549>
<T143733><DEBUG><OUT>sending 'zip' (908048 KB)... OKAY</OUT>
</DEBUG></T143733>
<T143733><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T143733>
<T143733><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T143733>
<T143854><DEBUG><OUT>INFOrom parsing start ...</OUT>
</DEBUG></T143854>
<T143902><DEBUG><OUT>INFOrom parsing finish ...</OUT>
</DEBUG></T143902>
<T143902><DEBUG><OUT>INFOzip header checking...</OUT>
</DEBUG></T143902>
<T143902><DEBUG><OUT>INFOzip info parsing...</OUT>
</DEBUG></T143902>
<T143902><DEBUG><OUT>FAILED (remote: 22 loading zip info fail)</OUT>
</DEBUG></T143902>
<T143905><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143905>
<T143906><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143906>
<T143906><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143906>
<T143908><DEBUG><OUT>FA2CFS502308 fastboot</OUT>
</DEBUG></T143908>
<T143908><DEBUG><CMD>adb devices</CMD>
</DEBUG></T143908>
<T143909><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T143909>
<T143909><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T143909>
<T143910><DEBUG><OUT>FA2CFS502308 fastboot</OUT>
</DEBUG></T143910>
<T143910><DEBUG><CMD>fastboot -s FA2CFS502308 getvar boot-mode</CMD>
</DEBUG></T143910>
<T143911><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T143911>
<T143911><DEBUG><CMD>fastboot -s FA2CFS502308 reboot</CMD>
</DEBUG></T143911>
<T143912><DEBUG><OUT>rebooting... </OUT>
</DEBUG></T143912>
<T143912><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T143912>
<T143913><DEBUG><OUT />
</DEBUG></T143913>
</LOG>
****
Sorry my English.
and thanks for any help.
Are you plugging into a usb 2 or 3 port.
Sent from my HTC6435LVW using xda app-developers app
Did you turn off the driver signing feature in Windows 8? I've had two guys ask me to help them and I used the thread on xda, found via google, titled something like "INSTALL ADB and FASTBOOT on WINDOWS 8" and once I finished installing it with that method things were working for them. One only took a minute or two I checked something right off the bat and it solved the problem the other one I had to follow the instructions step by step and install everything according to those instructions.
Bigandrewgold said:
Are you plugging into a usb 2 or 3 port.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I'm with 2.0 usb
CharliesTheMan said:
Did you turn off the driver signing feature in Windows 8? I've had two guys ask me to help them and I used the thread on xda, found via google, titled something like "INSTALL ADB and FASTBOOT on WINDOWS 8" and once I finished installing it with that method things were working for them. One only took a minute or two I checked something right off the bat and it solved the problem the other one I had to follow the instructions step by step and install everything according to those instructions.
Click to expand...
Click to collapse
Yes.i did turn off the driver signature on the advance features of windows8. I have the adb,install on my laptop
Related
Hi,
Sorry to bother with my failure on this but I am here:
"If you encounter problems after this procedure where your device does not boot properly (white screen with HTC logo)"
I have BB WiFi Flyer and followed Part 1 to run the Revolutionary mod. That seemed to go fine and I skipped the ClockWorkMod as directed. Then used the Beginner procedure of Part 2 (ran ARUWizard). In first run I'm sure I saw it clear cache, send, I saw a progress bar mentioning update of Radio. Then it was sending again and taking a long time but I did not want to interrupt it so I left it and couldn't get back until about 6 hours later. Still stuck on sending. The first RUU log only has this in it:
Code:
<LOG>
<T085536><INFO><VERSION>1.0.3.2011</VERSION></INFO></T085536>
<T085536><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T085536>
<T085552><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T085552>
<T085552><DEBUG><OUT />
</DEBUG></T085552>
</LOG>
I went ahead and disconnected USB and got a error right away. Recovery in the ARUWizard didn't seem to really do any good. I retried and seemed to get about the same result but the log now has this:
Code:
<LOG>
<T163217><INFO><VERSION>1.0.3.2011</VERSION></INFO></T163217>
<T163217><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T163217>
<T163221><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T163221>
<T163221><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163221>
<T163222><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163222>
<T163222><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163222>
<T163224><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163224>
<T163224><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163224>
<T163225><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163225>
<T163225><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163225>
<T163226><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163226>
<T163226><DEBUG><CMD>fastboot -s HT15MJN00811 getvar boot-mode</CMD>
</DEBUG></T163226>
<T163227><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T163227>
<T163227><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163227>
<T163228><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163228>
<T163228><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163228>
<T163229><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163229>
<T163229><DEBUG><CMD>fastboot -s HT15MJN00811 getvar boot-mode</CMD>
</DEBUG></T163229>
<T163230><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T163230>
<T163230><DEBUG><CMD>fastboot -s HT15MJN00811 getvar battery-status</CMD>
</DEBUG></T163230>
<T163231><DEBUG><OUT>battery-status: good</OUT>
</DEBUG></T163231>
<T163231><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T163231>
<T163231><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163231>
<T163232><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163232>
<T163232><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163232>
<T163234><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163234>
<T163234><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163234>
<T163235><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163235>
<T163235><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163235>
<T163236><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163236>
<T163236><DEBUG><CMD>fastboot -s HT15MJN00811 getvar boot-mode</CMD>
</DEBUG></T163236>
<T163237><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T163237>
<T163237><DEBUG><CMD>fastboot -s HT15MJN00811 getvar version-main</CMD>
</DEBUG></T163237>
<T163238><DEBUG><OUT>version-main: 2.27.1540.32</OUT>
</DEBUG></T163238>
<T163239><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T163239>
<T163239><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163239>
<T163240><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163240>
<T163240><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163240>
<T163242><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163242>
<T163242><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163242>
<T163243><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163243>
<T163243><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163243>
<T163244><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163244>
<T163244><DEBUG><CMD>fastboot -s HT15MJN00811 getvar boot-mode</CMD>
</DEBUG></T163244>
<T163245><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T163245>
<T163245><DEBUG><CMD>fastboot -s HT15MJN00811 getvar version-main</CMD>
</DEBUG></T163245>
<T163246><DEBUG><OUT>version-main: 2.27.1540.32</OUT>
</DEBUG></T163246>
<T163252><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T163252>
<T163253><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163253>
<T163254><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163254>
<T163254><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163254>
<T163255><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163255>
<T163255><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163255>
<T163256><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163256>
<T163256><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163256>
<T163257><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163257>
<T163257><DEBUG><CMD>fastboot -s HT15MJN00811 getvar boot-mode</CMD>
</DEBUG></T163257>
<T163258><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T163258>
<T163258><DEBUG><CMD>adb devices</CMD>
</DEBUG></T163258>
<T163259><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T163259>
<T163259><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T163259>
<T163301><DEBUG><OUT>HT15MJN00811 fastboot</OUT>
</DEBUG></T163301>
<T163301><DEBUG><CMD>fastboot -s HT15MJN00811 getvar boot-mode</CMD>
</DEBUG></T163301>
<T163302><DEBUG><OUT>boot-mode: RUU (Hboot&Radio PreUpdate)</OUT>
</DEBUG></T163302>
<T163302><DEBUG><CMD>fastboot -s HT15MJN00811 erase cache</CMD>
</DEBUG></T163302>
<T163303><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T163303>
<T163304><DEBUG><CMD>fastboot -s HT15MJN00811 flash zip C:\Downloads\Software\Android\Roms\RUU_Wifi_B09\rom.zip</CMD>
</DEBUG></T163304>
<T170556><DEBUG><OUT>sending 'zip' (655782 KB)... FAILED (data transfer failure (Too many links))</OUT>
</DEBUG></T170556>
<T170626><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T170626>
<T170627><DEBUG><OUT />
</DEBUG></T170627>
</LOG>
It really seems to be doing nothing on the command (I don't see any kind of progress bar on the Flyer screen):
fastboot -s HT15MJN00811 flash zip C:\Downloads\Software\Android\Roms\RUU_Wifi_B09\rom.zip
The send failure listed I believe coincides with me pulling the USB cable again.
Would I get farther using the fastboot commands directly with the PG41IMG-WIFI-B09.zip image?
I thought I saw a post go by where someone mentioned trouble running from Win7-64bit (which is what I'm using).
I am able to get into HBoot (which is 6.11.1111) and go to Fastboot and power down. I connected a charger and the orange led is on giving me the impression it is charging.
Thanks for the work and any help you can offer to get me un-stuck!
Can you boot into normal Android? It keeps searching for an ADB devices.
Looks like the hboot flashed so you should have hc s off hboot. Can you get into recovery
Sent from my HTC Flyer P510e using xda premium
Not sure what you mean by boot normal into Android but I think the answer is no. It just goes to the white screen with green htc logo. Is there something special to make it do what you mean? I have also tried 'fastboot reboot' which boots to the same point.
I can get to the HBoot menu where I see RECOVERY. Is that what you mean by "get into recovery"?
I am a long time developer but have 0 hours in Android so I am still very much a noob.
Thanks.
Yes in hboot select recovery . Does it take you to a black screen with blue letters
Just kill the ruu and run it again.
Sorry for the slow responses. Too many things going on. I will be able to stay with this later this afternoon.
Using recovery in the HBoot menu goes to the same white screen with green letters.
I have retried the ARUWizard a couple of times and it seems to go to the same spot. How long does the overall reflash take typically because it always seems to be just stuck at the same spot sending the image?
This morning I tried:
Booted to FASTBOOT.
Ran:
fastboot erase cache
erasing 'cache'... OKAY [ 0.354s]
finished. total time: 0.354s
fastboot oem rebootRUU
erasing 'cache'... OKAY [ 0.354s]
finished. total time: 0.354s
fastboot flash zip PG41IMG-WIFI-B09.zip
sending 'zip' (655782 KB)...
So should there be a very long pause at this point or should there be some indication of progress? It just sits there.
Looking at the fastboot process, it has a big chunk of memory (~650MB) and is using 0% cpu. The Flyer screen is the black with white htc letters and nothing else.
Ugh.
It is sending a large file. On my hunk of junk PC it takes a long time to send. How long is the pause for you
Sent from my HTC Flyer P510e using xda premium
That first attempt with the ARUWizard, I came back 6 hours later to a PC screen still with Sending..... The dots were moving but, 6 hours?
Those later retries I think the log shows I waited at least a half hour.
Should the Flyer screen show any progress?
No that is too long. I do not want to brick your device on you but if the hboot flashed I would assume you could fastboot flash the components such as radio and recovery then flash a custom rom through recovery. I would either
Wait for globatron to respond or post in his thread.
Sent from my HTC Flyer P510e using xda premium
I don't think I can post in the developer forum until I have more posts. So how do I get Globatron's attention?
I guess I'll try posting this a few more times to see if that gets me access.
Sorry for the spam.
I don't think I can post in the developer forum until I have more posts. So how do I get Globatron's attention?
I guess I'll try posting this a few more times to see if that gets me access.
Sorry for the spam.
I don't think I can post in the developer forum until I have more posts. So how do I get Globatron's attention?
I guess I'll try posting this a few more times to see if that gets me access.
Sorry for the spam but I'm trying to avoid a brick situation.
I don't think I can post in the developer forum until I have more posts. So how do I get Globatron's attention?
I guess I'll try posting this a few more times to see if that gets me access.
Sorry for the spam but I'm trying to avoid a brick situation and don't know a better way.
I do apologize for this but I am just trying to get into the HC thread so I can hopefully get some timely information.
I hope I have not done this for no reason and I do apologize but my situation is leaving me feel I may be losing out on options.
Very sorry. This didn't work anyway. I still can't post in the developer area.
Have you tried placing the zip on your ext SD renaming it to the specific name that the system will flash and then getting into hboot
Sent from my HTC Flyer P510e using xda premium
File name would be
PG41IMG.zip
Sent from my HTC Flyer P510e using xda premium
Also have you considered trying to run the stock ruu for your device
Sent from my HTC Flyer P510e using xda premium
Hey folks,
I'm hoping that someone out there can help me. I'm trying to restore my phone to stock using RUU_ENRC2B_U_JB_45_HTC_Europe_1.17.401.1_Radio_3.1204.168.32_release_299688_signed.exe
I've relocked my bootloader, started up the phone in fastboot usb and ran the RUU. It looks as though it is installing the stock ROM but then it fails. Has anyone successfully restored their X+ to stock and if so is there something that I've done that I need to change?
Any advise would be welcome.
***update, here's the RUU log from the attempted update
<LOG>
<T153600><INFO><VERSION>1.0.9.2012</VERSION></INFO></T153600>
<T153600><INFO>start read zip</INFO></T153600>
<T153600><INFO>The input file() DOES NOT exist.<T153600><INFO>Finish read zip.</INFO></T153600>
<T153600><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T153600>
<T153608><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T153608>
<T153608><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153608>
<T153608><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153608>
<T153610><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153610>
<T153610><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153610>
<T153611><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153611>
<T153611><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153611>
<T153611><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153611>
<T153612><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153612>
<T153612><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153612>
<T153613><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153613>
<T153613><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153613>
<T153614><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T153614>
<T153614><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153614>
<T153614><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153614>
<T153615><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153615>
<T153615><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153615>
<T153616><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153616>
<T153616><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153616>
<T153617><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T153617>
<T153617><DEBUG><CMD>fastboot -s FA2BPW101882 getvar battery-status</CMD>
</DEBUG></T153617>
<T153619><DEBUG><OUT>battery-status: good</OUT>
</DEBUG></T153619>
<T153619><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T153619>
<T153619><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153619>
<T153619><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153619>
<T153620><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153620>
<T153620><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153620>
<T153621><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153621>
<T153621><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153621>
<T153621><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153621>
<T153622><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153622>
<T153622><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153622>
<T153623><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153623>
<T153623><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153623>
<T153624><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T153624>
<T153624><DEBUG><CMD>fastboot -s FA2BPW101882 getvar version-main</CMD>
</DEBUG></T153624>
<T153626><DEBUG><OUT>version-main: 1.17.161.7</OUT>
</DEBUG></T153626>
<T153628><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T153628>
<T153628><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153628>
<T153628><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153628>
<T153629><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153629>
<T153629><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153629>
<T153630><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153630>
<T153630><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153630>
<T153630><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153630>
<T153631><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153631>
<T153631><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153631>
<T153632><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153632>
<T153632><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153632>
<T153633><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T153633>
<T153633><DEBUG><CMD>fastboot -s FA2BPW101882 getvar version-main</CMD>
</DEBUG></T153633>
<T153634><DEBUG><OUT>version-main: 1.17.161.7</OUT>
</DEBUG></T153634>
<T153635><DEBUG>signed rom
</DEBUG></T153635>
<T153635><DEBUG>(Encrypted) Main version: 1.17.401.1
</DEBUG></T153635>
<T153640><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T153640>
<T153640><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T153640>
<T153641><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T153641>
<T153641><DEBUG>signed rom
</DEBUG></T153641>
<T153641><DEBUG>getImageCount, nHR: 19
</DEBUG></T153641>
<T153641><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153641>
<T153641><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153641>
<T153642><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153642>
<T153642><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153642>
<T153643><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153643>
<T153643><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153643>
<T153643><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153643>
<T153643><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153643>
<T153644><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153644>
<T153644><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153644>
<T153645><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153645>
<T153645><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153645>
<T153646><DEBUG><OUT>boot-mode: FASTBOOT</OUT>
</DEBUG></T153646>
<T153646><DEBUG><CMD>fastboot -s FA2BPW101882 oem rebootRUU</CMD>
</DEBUG></T153646>
<T153648><DEBUG><OUT>... INFOSave data from original MSC...INFOSave data from SIF...INFOUpdate partition data to SIF partitionINFOUpdate partition data from original MSC...INFO[MSG] OKAYOKAY</OUT>
</DEBUG></T153648>
<T153648><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153648>
<T153648><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153648>
<T153649><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153649>
<T153649><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153649>
<T153650><DEBUG><OUT />
</DEBUG></T153650>
<T153651><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153651>
<T153651><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153651>
<T153652><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153652>
<T153652><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153652>
<T153652><DEBUG><OUT />
</DEBUG></T153652>
<T153653><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153653>
<T153653><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153653>
<T153654><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153654>
<T153654><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153654>
<T153654><DEBUG><OUT />
</DEBUG></T153654>
<T153655><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153655>
<T153655><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153655>
<T153656><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153656>
<T153656><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153656>
<T153656><DEBUG><OUT />
</DEBUG></T153656>
<T153657><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153657>
<T153657><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153657>
<T153658><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153658>
<T153658><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153658>
<T153659><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153659>
<T153659><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153659>
<T153700><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T153700>
<T153700><DEBUG><CMD>fastboot -s FA2BPW101882 erase cache</CMD>
</DEBUG></T153700>
<T153701><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T153701>
<T153701><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T153701>
<T153701><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T153701>
<T153701><DEBUG>signed rom
</DEBUG></T153701>
<T153701><DEBUG>getImageCount, nHR: 19
</DEBUG></T153701>
<T153701><DEBUG><CMD>fastboot -s FA2BPW101882 flash zip C:\Users\micko\AppData\Local\Temp\{17BCBB79-FEBC-4679-A83C-E2FE483B2096}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T153701>
<T153829><DEBUG><OUT>sending 'zip' (711478 KB)... OKAY</OUT>
</DEBUG></T153829>
<T153829><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T153829>
<T153829><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T153829>
<T153900><DEBUG><OUT>INFOrom parsing start ...</OUT>
</DEBUG></T153900>
<T153905><DEBUG><OUT>INFOtime: 4297</OUT>
</DEBUG></T153905>
<T153905><DEBUG><OUT>INFOrom parsing finish ...</OUT>
</DEBUG></T153905>
<T153905><DEBUG><OUT>INFOYour memory size = 59640MB, choose rawpt_64g.img</OUT>
</DEBUG></T153905>
<T153905><DEBUG><OUT>INFOchecking model ID...</OUT>
</DEBUG></T153905>
<T153905><DEBUG><OUT>INFOchecking custom ID...</OUT>
</DEBUG></T153905>
<T153905><DEBUG><OUT>FAILED (remote: 42 custom id check fail)</OUT>
</DEBUG></T153905>
<T153938><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153938>
<T153938><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153938>
<T153939><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153939>
<T153939><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153939>
<T153940><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153940>
<T153940><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153940>
<T153940><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153940>
<T153940><DEBUG><CMD>adb devices</CMD>
</DEBUG></T153940>
<T153941><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T153941>
<T153941><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T153941>
<T153942><DEBUG><OUT>FA2BPW101882 fastboot</OUT>
</DEBUG></T153942>
<T153942><DEBUG><CMD>fastboot -s FA2BPW101882 getvar boot-mode</CMD>
</DEBUG></T153942>
<T153943><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T153943>
<T153943><DEBUG><CMD>fastboot -s FA2BPW101882 reboot</CMD>
</DEBUG></T153943>
<T153944><DEBUG><OUT>rebooting... </OUT>
</DEBUG></T153944>
<T153944><DEBUG>32bit HTC Sync, strPath = C:\Program Files (x86)\HTC\HTC Sync 3.0\
</DEBUG></T153944>
<T153944><DEBUG><CMD>adb kill-server</CMD>
</DEBUG></T153944>
<T153945><DEBUG><OUT />
</DEBUG></T153945>
</LOG>
Click to expand...
Click to collapse
I have. I used windows 7 x64, made sure HTC smart sync was installed, and made sure official HTC drivers were installed from their website. Also it took a few computer reboots to get everything working.
Yes I did it in fastboot usb mode and I also executed command "fastboot oem lock" before running the ruu.
I can't think of anything else except to make sure you are using a good usb cable, and triple check the drivers in the device manager. Make sure there are no glitches in them!
I drop my 2 cents too... What about your CID? I think you need Vodaphone RUU, 1.17.161.7, checking rug log is written there. I'm not sure it is available yet... If you have no backup done then Im sorry
Sent from my HTC One X+ using xda premium
hey,
i tried to install the RUU for my One X+ because the sd card, wifi network, cell network is inaccsesible right now.
Also the ADB is not accesible, it always returns device not found error. (i double checked everything).
Finally it gets stuck in the way installing:
Code:
<T121536><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T121536>
<T121537><DEBUG><OUT>FA2C7W106219 fastboot</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 getvar boot-mode</CMD>
</DEBUG></T121537>
<T121537><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 erase cache</CMD>
</DEBUG></T121537>
<T121539><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T121539>
<T121539><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T121539>
<T121539><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T121539>
<T121539><DEBUG>signed rom
</DEBUG></T121539>
<T121539><DEBUG>getImageCount, nHR: 19
</DEBUG></T121539>
<T121539><DEBUG><CMD>fastboot -s FA2C7W106219 flash zip C:\Users\Ike\AppData\Local\Temp\{545A2C96-F188-4ED7-93DD-73E45B96952E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T121539>
<T121709><DEBUG><OUT>sending 'zip' (711478 KB)... OKAY</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T121709>
<T121740><DEBUG><OUT>INFOrom parsing start ...</OUT>
</DEBUG></T121740>
<T121744><DEBUG><OUT>INFOtime: 4297</OUT>
</DEBUG></T121744>
<T121744><DEBUG><OUT>INFOrom parsing finish ...</OUT>
</DEBUG></T121744>
<T121745><DEBUG><OUT>INFOYour memory size = 59640MB, choose rawpt_64g.img</OUT>
</DEBUG></T121745>
<T121745><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T121745>
Any ideas?
iTTerror said:
hey,
i tried to install the RUU for my One X+ because the sd card, wifi network, cell network is inaccsesible right now.
Also the ADB is not accesible, it always returns device not found error. (i double checked everything).
Finally it gets stuck in the way installing:
Code:
<T121536><DEBUG><CMD>fastboot devices</CMD>
</DEBUG></T121536>
<T121537><DEBUG><OUT>FA2C7W106219 fastboot</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 getvar boot-mode</CMD>
</DEBUG></T121537>
<T121537><DEBUG><OUT>boot-mode: RUU</OUT>
</DEBUG></T121537>
<T121537><DEBUG><CMD>fastboot -s FA2C7W106219 erase cache</CMD>
</DEBUG></T121537>
<T121539><DEBUG><OUT>erasing 'cache'... OKAY</OUT>
</DEBUG></T121539>
<T121539><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T121539>
<T121539><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T121539>
<T121539><DEBUG>signed rom
</DEBUG></T121539>
<T121539><DEBUG>getImageCount, nHR: 19
</DEBUG></T121539>
<T121539><DEBUG><CMD>fastboot -s FA2C7W106219 flash zip C:\Users\Ike\AppData\Local\Temp\{545A2C96-F188-4ED7-93DD-73E45B96952E}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T121539>
<T121709><DEBUG><OUT>sending 'zip' (711478 KB)... OKAY</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>writing 'zip'... INFOadopting the signature contained in this image...</OUT>
</DEBUG></T121709>
<T121709><DEBUG><OUT>INFOsignature checking...</OUT>
</DEBUG></T121709>
<T121740><DEBUG><OUT>INFOrom parsing start ...</OUT>
</DEBUG></T121740>
<T121744><DEBUG><OUT>INFOtime: 4297</OUT>
</DEBUG></T121744>
<T121744><DEBUG><OUT>INFOrom parsing finish ...</OUT>
</DEBUG></T121744>
<T121745><DEBUG><OUT>INFOYour memory size = 59640MB, choose rawpt_64g.img</OUT>
</DEBUG></T121745>
<T121745><DEBUG><OUT>FAILED (remote: 99 unknown fail)</OUT>
</DEBUG></T121745>
Any ideas?
Click to expand...
Click to collapse
nevermind forgot to relock bootloader
Hello,
I need your expertise help to resolve my phone issues. Hope someone can help. Currently, i am bit panic that my device has become unusable. Please help!!
My problem statement:
1. HTC One M8 is currently in boot loop. It boots approximately around 6 to 7 times and then enters to normal operation. This happens everytime i reboot.
2. WiFi is greyed. unable to "On" the Wifi. Still i can use my data through my SIM card.
One Important information: I DONT HAVE ANY BACKUP. I LOST IT. i kept them in the internal storage and mistakenly wiped the internal storage as well. I am unlucky
Brief of my device:
I bought this device from US. It came with AT&T. I came to India and i was using it without any issues. Howev, it doesnt update at all through Wifi or Data. Hence, with my limited knowledge, i unlocked, rooted and flashed with custom ROM. There the problem started. It got into boot loop and WiFi is greyed out. So, i thought brining back to Stock would resolve the issue and did the Stock ROm flash and recovery as well. No luck. Currently, i still have the boot loop and "WiFi" greyed out.
I used TWRP.
Below is current details & Versions:
-----------------------------------------------------
1. Bootlader:
M8_UL_CA PVT SHIP S-ON
HBOOT-3.16.0.0000
RADIO-1.16.21331931.LA11G
openDSP-V38.2.2-00542-m8974.0311
OS-
eMMC-BOOT 2048MB
Apr 18 2014,16:06:33.0
-----------------------------------------------------
2. fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331931.LA11G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXX
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
---------------------------------------------------------
3. Software information
Androin version: 5.0.1
HTC Sense version: 6.0
Software number: 4.16.401.10
HDC SDK API level: Unknown
Kernel version: 3.4.0-g6af28ec [email protected] #1 SMP PREEMPT
BASEBAND VERSION: 1.16.21331931.LA11G_20.31A.4145.02L
Build number: 4.16.401.10 CL448934 RELEASE-KEYS
------------------------------------------------------------------
Awaiting your valuable help. Thanks in advance!
Apologise if it is not the right forum.
Thank you,
Selvaraj
Hi @selva_rag,
Thanks for posting in XDA Assist. I am going to move your thread to the HTC One (M8) Q&A and Troubleshooting Forum as the users there will be much better suited to help you out.
-- Gandalf
Your firmware is outdated (hboot, radio, etc.) , and does not support any of the current custom ROMs. Broken WiFi is a known result of firmware mismatch; and the boot loops is likely due to the same reason.
Similarly, unless you flashed any but the oldest stock ROMs (1.58.502) you will suffer from the same firmware mismatch issue.
AT&T M8 won't OTA update since you are outside the US and not on the AT&T network (this is a AT&T specific complication).
I would advise to backup your personal data (your phone will be wiped), relock your bootloader (command: fastboot oem lock) then run the 4.28.502.1 RUU here: http://dl3.htc.com/application/RUU_M8[email protected]50319A_40.45.C33065.00_F_release_426617_signed_2.exe
The RUU will update your firmware. From there, you can unlock the bootloader again via HTCDev.com, flash current version TWRP 2.8.7, then flash a current Lollipop custom ROM of your choice.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
selva_rag said:
One Important information: I DONT HAVE ANY BACKUP. I LOST IT. i kept them in the internal storage and mistakenly wiped the internal storage as well. I am unlucky
Click to expand...
Click to collapse
This has nothing to do with luck. This is a failure to use good judgement, or follow some basic precautions:
1) You shouldn't be wiping partitions unless you are completely aware of what it means and what the results will be. The "Advanced" wipe section is called that for a reason, avoid using those options if you don't fully understand them. It says right on the default Wipe screen that the default wipe (user data, cache and Dalvik - leaves internal storage untouched) is the only wipe that is needed most of the time. Again, it says that for a reason, and you chose to ignore it.
2) Copy backups onto your computer, to avoid such situations
HI,
Thanks for the help and agree it was my mistake of deleting the backup.
I tried your suggestion. However, the RUU updater just frozen at "Sending 0/6" on my PC. And on the device it stays on the "HTC" black screen itself and no progress shown.
Steps I did:
1. Reclocked the boot loader using " Fastboot oem lock"
2. Rebooted the device in Fastboot USB
3. Ran the given RUU from my PC and followed the onscreen options.
4. It just stays there in the same stage of Sending 0/6 in my pc for more than 2 hours
5. Device is "HTC" Black screen
Am i making any mistake?
Thank you,
Selva
redpoint73 said:
Your firmware is outdated (hboot, radio, etc.) , and does not support any of the current custom ROMs. Broken WiFi is a known result of firmware mismatch; and the boot loops is likely due to the same reason.
Similarly, unless you flashed any but the oldest stock ROMs (1.58.502) you will suffer from the same firmware mismatch issue.
AT&T M8 won't OTA update since you are outside the US and not on the AT&T network (this is a AT&T specific complication).
I would advise to backup your personal data (your phone will be wiped), relock your bootloader (command: fastboot oem lock) then run the 4.28.502.1 RUU here:
The RUU will update your firmware. From there, you can unlock the bootloader again via , flash current version TWRP 2.8.7, then flash a current Lollipop custom ROM of your choice.
---------- Post added at 01:18 PM ---------- Previous post was at 01:13 PM ----------
This has nothing to do with luck. This is a failure to use good judgement, or follow some basic precautions:
1) You shouldn't be wiping partitions unless you are completely aware of what it means and what the results will be. The "Advanced" wipe section is called that for a reason, avoid using those options if you don't fully understand them. It says right on the default Wipe screen that the default wipe (user data, cache and Dalvik - leaves internal storage untouched) is the only wipe that is needed most of the time. Again, it says that for a reason, and you chose to ignore it.
2) Copy backups onto your computer, to avoid such situations
Click to expand...
Click to collapse
selva_rag said:
HI,
Thanks for the help and agree it was my mistake of deleting the backup.
I tried your suggestion. However, the RUU updater just frozen at "Sending 0/6" on my PC. And on the device it stays on the "HTC" black screen itself and no progress shown.
Click to expand...
Click to collapse
At your own risk, you can try to disconnect the phone, or otherwise kill the RUU. I know it sounds scary, but its not uncommon for the RUU to stall out, then run correctly when you try again. But again, killing the RUU process has its risks; and I won't take any responsibility for any damage that may occur. Although is most likely fine, since its just stuck at "sending" not actually gotten to installing anything; plus it apparently hasn't even started "sending".
What Windows version? Win10 has been reported to be very problematic. I don't know if anyone has even gotten an RUU to run on Win10.
I am using windows 10.
Anyhow, I killed it and got back into fastboot. This time i going to try in Windows 7 PC.
When i rebooted the Devide, it showed ***Security Warning***. But when i rebooted the device, it just gone.
Let me try and update you. Thanks again.
redpoint73 said:
At your own risk, you can try to disconnect the phone, or otherwise kill the RUU. I know it sounds scary, but its not uncommon for the RUU to stall out, then run correctly when you try again. But again, killing the RUU process has its risks; and I won't take any responsibility for any damage that may occur. Although is most likely fine, since its just stuck at "sending" not actually gotten to installing anything; plus it apparently hasn't even started "sending".
What Windows version? Win10 has been reported to be very problematic. I don't know if anyone has even gotten an RUU to run on Win10.
Click to expand...
Click to collapse
selva_rag said:
I am using windows 10.
Anyhow, I killed it and got back into fastboot. This time i going to try in Windows 7 PC.
Click to expand...
Click to collapse
That would be my recommendation. Good luck!
I tried to run in the windows 7 several times. However, the Exe file is not moving after the first screen (After i agree to the terms & condition). Attmpted to run in the compatibility mode...still it is not working.
I checked in the RUU log and it is as below. Also, i copied the ROM.ZIP to my downloads folder. Is it possible to flash this ROM.ZIP manually?
----------------------------------------------------------------
<LOG>
<T223155><INFO><VERSION>2.0.16.2014</VERSION></INFO></T223155>
<T223155><INFO>start read zip</INFO></T223155>
<T223155><INFO>T
</INFO></T223155>
<T223155><INFO>Finish read zip.</INFO></T223155>
<T223155><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T223155>
<T223204><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T223204>
<T223204><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223204>
<T223204><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223204>
<T223205><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223205>
<T223205><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223205>
<T223206><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223206>
<T223206><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223206>
<T223206><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223206>
<T223207><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223207>
<T223207><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223207>
<T223208><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223208>
<T223208><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223208>
<T223209><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 56(ms)</OUT>
</DEBUG></T223209>
<T223209><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223209>
<T223209><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223209>
<T223210><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223210>
<T223210><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223210>
<T223211><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223211>
<T223211><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223211>
<T223211><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 83(ms)</OUT>
</DEBUG></T223211>
<T223211><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar battery-status</CMD>
</DEBUG></T223211>
<T223212><DEBUG><OUT>battery-status: goodExecution time is 4(ms)</OUT>
</DEBUG></T223212>
<T223212><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T223212>
<T223212><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223212>
<T223212><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223212>
<T223213><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223213>
<T223213><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223213>
<T223214><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223214>
<T223214><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223214>
<T223214><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223214>
<T223215><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223215>
<T223215><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223215>
<T223216><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223216>
<T223216><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223216>
<T223217><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 186(ms)</OUT>
</DEBUG></T223217>
<T223217><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar version-main</CMD>
</DEBUG></T223217>
<T223218><DEBUG><OUT>version-main: Execution time is 5(ms)</OUT>
</DEBUG></T223218>
<T223249><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T223249>
<T223249><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223249>
<T223249><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223249>
<T223249><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223249>
<T223249><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223249>
<T223250><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223250>
<T223250><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223250>
<T223250><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223250>
<T223252><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223252>
<T223252><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223252>
<T223252><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223252>
<T223252><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223252>
<T223253><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 62(ms)</OUT>
</DEBUG></T223253>
<T223253><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar version-main</CMD>
</DEBUG></T223253>
<T223254><DEBUG><OUT>version-main: Execution time is 4(ms)</OUT>
</DEBUG></T223254>
<T223254><DEBUG>[ComparisonDlg][_initData()]get rom version
</DEBUG></T223254>
<T223254><DEBUG>[getRomVersion] +++
</DEBUG></T223254>
<T223254><DEBUG>[_getRomVersion] +++
</DEBUG></T223254>
<T223254><DEBUG>[_getRomVersion] single rom, fopen rom.zip
</DEBUG></T223254>
<T223303><DEBUG>[CAruRomHandler::CheckTheFirstZipEncrypted] The first.zip is encrypted!
</DEBUG></T223303>
<T223303><DEBUG>This is NOT a combined ROM, use the original method to get the ROM version.
</DEBUG></T223303>
<T223303><DEBUG>[CAruRomHandler::_getRomVersion] Large and signed rom
</DEBUG></T223303>
<T223303><DEBUG>[_getRomVersion] (Encrypted) Main version: 4.28.502.1
</DEBUG></T223303>
<T223303><DEBUG>[_getRomVersion] ---
</DEBUG></T223303>
<T223303><DEBUG>[getRomVersion] ROM Ver: 4.28.502.1
</DEBUG></T223303>
<T223303><DEBUG>[getRomVersion] ---
</DEBUG></T223303>
<T223327><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T223327>
<T223327><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T223327>
<T223327><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T223327>
<T223327><DEBUG>[getImageCount] Large and signed rom
</DEBUG></T223327>
<T223327><DEBUG>getImageCount, nHR: 24
</DEBUG></T223327>
<T223327><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223327>
<T223327><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223327>
<T223327><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223327>
<T223327><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223327>
<T223329><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223329>
<T223329><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223329>
<T223329><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223329>
<T223329><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223329>
<T223330><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223330>
<T223330><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223330>
<T223331><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223331>
<T223331><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223331>
<T223332><DEBUG><OUT>boot-mode: FASTBOOTExecution time is 138(ms)</OUT>
</DEBUG></T223332>
<T223332><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX oem rebootRUU</CMD>
</DEBUG></T223332>
<T223332><DEBUG><OUT>... (bootloader) Start Verify: 3OKAYExecution time is 19(ms)</OUT>
</DEBUG></T223332>
<T223332><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223332>
<T223332><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223332>
<T223333><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223333>
<T223333><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223333>
<T223334><DEBUG><OUT />
</DEBUG></T223334>
<T223335><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223335>
<T223335><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223335>
<T223336><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223336>
<T223336><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223336>
<T223337><DEBUG><OUT />
</DEBUG></T223337>
<T223337><DEBUG>32bit HSM, strPath = C:\Program Files (x86)\HTC\HTC Sync Manager\HTC Sync\
</DEBUG></T223337>
<T223337><DEBUG><CMD>adb devices</CMD>
</DEBUG></T223337>
<T223338><DEBUG><OUT>List of devices attached
</OUT>
</DEBUG></T223338>
<T223338><DEBUG><CMD>htc_fastboot devices</CMD>
</DEBUG></T223338>
<T223339><DEBUG><OUT>XXXXXXXXXXXX fastboot</OUT>
</DEBUG></T223339>
<T223339><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX getvar boot-mode</CMD>
</DEBUG></T223339>
<T223340><DEBUG><OUT>boot-mode: RUUExecution time is 11(ms)</OUT>
</DEBUG></T223340>
<T223340><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX erase cache</CMD>
</DEBUG></T223340>
<T223341><DEBUG><OUT>erasing 'cache'... OKAYExecution time is 50(ms)</OUT>
</DEBUG></T223341>
<T223341><DEBUG>Try to read image count from android-info.txt in rom.zip
</DEBUG></T223341>
<T223341><DEBUG>The rom is encrypted, read the header instead.
</DEBUG></T223341>
<T223341><DEBUG>[getImageCount] Large and signed rom
</DEBUG></T223341>
<T223341><DEBUG>getImageCount, nHR: 24
</DEBUG></T223341>
<T223341><DEBUG><CMD>htc_fastboot -s XXXXXXXXXXXX -d flash zip C:\Users\Niru\AppData\Local\Temp\{1CD2F576-83BE-4A6B-9BFE-6C43DF2AD8E6}\{50F2F878-636A-496F-A7CB-544C067E0C4B}\rom.zip</CMD>
</DEBUG></T223341>
----------------------------------------------------------------
redpoint73 said:
That would be my recommendation. Good luck!
Click to expand...
Click to collapse
selva_rag said:
I tried to run in the windows 7 several times. However, the Exe file is not moving after the first screen (After i agree to the terms & condition). Attmpted to run in the compatibility mode...still it is not working.
Click to expand...
Click to collapse
Hmmm, I've seen this issue repoorted several times for Win10 (maybe Win8) but don't know if I've seen it happen on Win7.
Do you have USB 3.0 on your ports? This has also been known to not play well with the RUU.
selva_rag said:
Also, i copied the ROM.ZIP to my downloads folder. Is it possible to flash this ROM.ZIP manually?
Click to expand...
Click to collapse
From what has been posted on here, yes. I've never done it myself.
I think you need to rename the file 0P6BIMG.zip and put it on the top directory (not in a folder) of internal storage.
Also, I believe the phone's identifier (FA...) after each line "fastboot devices" in the log you posted, is your phone's serial number.
So you should delete those.
redpoint73 said:
Also, I believe the phone's identifier (FA...) after each line "fastboot devices" in the log you posted, is your phone's serial number.
So you should delete those.
Click to expand...
Click to collapse
Hi,
Thank you so much for your help. I think the problem is with the RUU file itself. I received a new version of the RUU file from my friend in US. It worked fine in Windows 10 without modifying anything. Now my phone is back with Stock 5.0.1.
Appreciate all your help.
selva_rag said:
Thank you so much for your help.
Click to expand...
Click to collapse
No problem, and there is a button for that!
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
< waiting for device >
...
OKAY [ 12.991s]
finished. total time: 12.991s
C:\Program Files\Minimal ADB and Fastboot>
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot-enter-fastboot-common-
func
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Program Files\Minimal ADB and Fastboot>fastboot common
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.125s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11776 KB)...
OKAY [ 0.374s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.390s
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
getvar:all FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Program Files\Minimal ADB and Fastboot>fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Program Files\Minimal ADB and Fastboot>
Why did you format using fastboot? That's not a very good idea.
Sent from my Galaxy Tab 3 using XDA Labs
adriansticoid said:
Why did you format using fastboot? That's not a very good idea.
Click to expand...
Click to collapse
What I have learned....never format in fastboot. I had a HTC one that I did that with...wow, problems. Only solution was a ruu
---------- Post added at 12:58 PM ---------- Previous post was at 12:57 PM ----------
aamszia said:
C:\Program Files\Minimal ADB and Fastboot>fastboot oem unlock
< waiting for device >
...
OKAY [ 12.991s]
finished. total time: 12.991s
C:\Program Files\Minimal ADB and Fastboot>
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot-enter-fastboot-common-
func
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Program Files\Minimal ADB and Fastboot>fastboot common
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if fou
nd,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
C:\Program Files\Minimal ADB and Fastboot>fastboot reboot
rebooting...
finished. total time: 0.125s
C:\Program Files\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (11776 KB)...
OKAY [ 0.374s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.390s
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
getvar:all FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
getvar:all FAILED (remote: Command not allowed)
finished. total time: 0.000s
C:\Program Files\Minimal ADB and Fastboot>fastboot -w
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
C:\Program Files\Minimal ADB and Fastboot>
Click to expand...
Click to collapse
Unfortunately, you jammed your bootloader
Fastboot will not automatically determine the filesystem its formatting. NEVER, ever ever in your entire life format in fastboot unless you know what you're doing. It will eradicate the partition.
Sent from my honor 5X using XDA Labs