Related
ok i dont know but my phone has no recovery and does not boot
and i tried the sappimg.zip it hangs on radio when i tried
mytouch 3g 3.5mm fender
THIS IS WHAT IT SAY IN HBOOT:
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0013 (SAPP31000)
CPLD-13
RADIO-6.35.16.19
mismatch spl/radio i know
when i try to this command: fastboot flash (e.g hboot,recovery,and radio) file.
i get the same message
FAILED (remote: not allow)
Download an apropriate RUU and flash it through fastboot.
Fastboot command: fastboot oem rebootRUU
Then run the RUU from PC.
Hope this solves your problem.
alex6vasy said:
Download an apropriate RUU and flash it through fastboot.
Fastboot command: fastboot oem rebootRUU
Then run the RUU from PC.
Hope this solves your problem.
Click to expand...
Click to collapse
okay i tried all 3 ruu from this ruu thread http://forum.xda-developers.com/showthread.php?t=659403 for T-Mobile myTouch 3G 1.2
i tried fastboot oem rebootruu and it goes in ruu usb
they all said error usb connection error
but its plug and this is for
2.10.531.3 T-Mobile USA DRD35
2.10.531.4 T-Mobile USA DRD35
but 1.94.531.1 T-Mobile USA DMD64 loads but at the end it says
find the correct phone version idk help pls
This issue has been answered before by me... it's kinda complicated and requires some thinking... do a search with my name and you shall find the answer and all the necessary files/instructions.
Good luck hunting.
i looked thru all your post but still nothing if u could link me or point me somewhere lol
Download my fastboot commander and provide here ALL device info.
ok i tried fast oem boot and got this
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x98070CA0
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 32
(bootloader) TAG:hwid 0x1
(bootloader) TAG:skuid 0x22800
(bootloader) TAG:hero panel = 0x0
(bootloader) TAG:engineerid = 0x2
(bootloader) radio_flash_id=0x5510BCAD
(bootloader) die_size=0x1
(bootloader) radio_flash_id=0x5510BCAD
(bootloader) die_size=0x1
(bootloader) TAG:die_size = 0x1
(bootloader) Device CID is not super CID
(bootloader) CID is T-MOB010
(bootloader) setting.cid::T-MOB010
(bootloader) serial number: HT043PB03144
(bootloader) commandline from head: no_console_suspend=1 console=null
(bootloader) command line length =337
(bootloader) active commandline: board_sapphire.disable_uart3=0 board_sap
(bootloader) phire.usb_h2w_sw=0 board_sapphire.disable_sdcard=0 smisize=3
(bootloader) 2 androidboot.baseband=6.35.16.19 androidboot.cid=T-MOB010
(bootloader) androidboot.carrier=TMUS androidboot.keycaps=qwerty androidb
(bootloader) oot.mode=normal androidboot.serialno=HT043PB03144 androidboo
(bootloader) t.bootloader=1.33.0013 no_console_suspend=1 console=null
(bootloader) PARTITIOM_NUM_MAX =6 Valid partition num=6
i download your FBCOMMANDO and it wont detect my phone on fast boot this is what i got when i check connection and print device info
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
-----------------------------------.
No fastboot device connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
-----------------------------------.
PRINT OF DEVICE INFO FAILURE - PLEASE CHECK YOUR CONNECTION.
i think it wont detect because i dont have a eng spl or s-off
So now i have a new problem omg lol
it wont boot to hboot anymore
it goes to ruu screen with the mirco-chip crossed out
on every boot or everytime i turn it on
now its stuck on RUU mode
so i cant use adb
no hboot so i cant use a gold card
so i have to flash from the computer (fastboot flash zip sappimg.zip)
only ruu that work is RUU_Sapphire_T-Mobile_US_2.10.531.4
but hangs on radio
-----------------------------------.
HT043PB03144 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.0013.
Radio version: 6.35.16.19.
Main software version: 2.10.531.4.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
I have same problem too
LBOG_Kush said:
-----------------------------------.
HT043PB03144 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.33.0013.
Radio version: 6.35.16.19.
Main software version: 2.10.531.4.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
Click to expand...
Click to collapse
I have the same problem too and i try the same way to get out of Stuck RUU USB Screen and still no luck
here my celphone info too:
-----------------------------------.
HT02BPB02502 Connected.
-----------------------------------.
STARTING PRINT OF DEVICE INFO.
-----------------------------------.
SPL/hboot version: 1.76.0007.
Radio version: 6.35.07.29.
Main software version: 3.57.0.0.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
-----------------------------------.
Print of device info SUCCESSFUL.
This device does not have s-off nor eng hboot.
ARE YOU SURE THAT THIS IS THE RIGHT TOOL FOR YOU?.
I think i need JTAG to fix that problem.
i have the same problem
here is my device information:
***UNLOCKED***
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.76.0013(SAPP 10000)
CPLD-12
RADIO-3.22.20.17
my phone is stuck on vodafone logo and keep restart the
any help to fix it ???
over 1000 posts by you xD
mumilover said:
This issue has been answered before by me... it's kinda complicated and requires some thinking... do a search with my name and you shall find the answer and all the necessary files/instructions.
Good luck hunting.
Click to expand...
Click to collapse
I've looked through a good 90% of your over 1000 posts, can you please pm me the link for the solution? I also seem to have this problem (and I tried fastboot oem rebootRUU and all the ruu updaers, I get an error and it drops the program xD
---------- Post added at 12:52 PM ---------- Previous post was at 12:47 PM ----------
fastboot commander says this (as does the phone when I hold vol down and power)
pressing the home key and power key (and holding) does nothing but freezes at a green mytouch 3g splash logo...
holding vol down and power gives me access to hboot ,
hboot says press back to go to fastboot
fastboot is useless as s-on
I don't have a recovery at all, I guess I don't have a rom at all either, I would think it was a brick, if I couldn't get to hboot and fastboot... wait, IS this a brick?
SPL/hboot version: 1.33.0013.
Radio version: 6.35.16.19.
Main software version: 3.57.0.0.
cid: t-mob010.
cpld: 13.
product: sapphire.
mid: sapp31000.
security: on.
build-mode: ship.
as a curiosity, what type of devices do you have?? 32A or 32B?
george.wgx said:
as a curiosity, what type of devices do you have?? 32A or 32B?
Click to expand...
Click to collapse
Looks like the T-MOB010 cid was used for 32B's and Fender/1.2's. In any case, unless I'm very mistaken, this is a radio mismatch.
Thomas1031, does your phone have a headphone jack?
Hi,
I have a Vodafone (UK) branded Desire Z which today froze whilst I was using it. This left me no option to remove the battery and re-insert it to clear the phone.
Unfortunately the phone will not fully boot now - all I get is the standard HTC screen, followed by the Vodafone logo screen. It then goes black and restarts.
I have tried removing the battery and leaving it for a while before reinserting. I have also removed and replaced the sim and the SD card, but still no joy.
Is there a 'safe mode' way of booting the Desire Z that I could try or has my phone just died?
Any help gratefully received.
http://forum.xda-developers.com/showthread.php?t=842495
Hi again,
Thanks for that link - I have read and re-read as suggested and attempted to follow the instructions but the second link (cwm recovery) is dead - it takes you to a 'removed by mod' post, so I didn't get far!
Just to give a bit further info, I took my device into a local 'fone doctor' shop, where they managed to fix it (or so I thought! - cost me £22 as well! ). The phone was back with the stock HTC Sense on it.
Anyway, within about three hours of the phone working, it froze again - and is now back to being stuck on the White HTC boot screen (rather than the looping it was doing previously). I have a feeling that my phone may just be knackered!
If I do the hold volume and switch on thing, I get the following:-
VISION PVT SHIP S-ON
HBOOT-0.85.0013
MICROP-0425
RADIO-26.10.04.03_M
Apr 11 2011,23:36:27
....plus the usual HBOOT, FASTBOOT, RECOVERY options etc.
To confirm, I have NEVER rooted my phone. Up to the point it originally froze it had only had the official over the air updates.
I do have HTC Sync installed on my PC, so all of the required USB drivers should be available.
I also have the Android SDK installed (I have dabbled in development) so have adb.
I have read many posts over the last couple of days, but the majority seem to say that if you have "S-ON" you could well be screwed.
Also, adb does not seem to recognise my phone - I have no idea if I had "enable USB debugging" checked or not - again, if this was not the case then I fear I could be screwed!
If anyone has any further idea's of how I could possibly bring my phone back to life it would be hugely appreciated.............or should I just give up and look to get my old G1 unlocked?!
Many thanks.
ok ...you can´t reach your phone with adb if your are not booted into a rom.
do you have fastboot installed on your pc?
if yes then enter fastboot menu (power & tp) and then type fastboot devices on your pc...
your device should be listed.
then type fastboot oem boot and if you are lucky your phone boots again
EDIT: or push power & volume+ to enter recovery and wipe cache or do a factory reset... and do some researching about emmc chip
Many thanks hoffmas. I managed to run the fastboot commands you mentioned which did indeed force a reboot, but unfortunately only back to the white HTC splash screen.
The output from the commands was:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot devices
XXXXXXXXXXX fastboot
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot oem boot
...
(bootloader) setup_tag addr=0xA0000100 cmdline add=0x8D0878FC
(bootloader) TAG:Ramdisk OK
(bootloader) TAG:smi ok, size = 0
(bootloader) TAG:hwid 0x0
(bootloader) TAG:skuid 0x25209
(bootloader) TAG:hero panel = 0xF
(bootloader) TAG:engineerid = 0x4
(bootloader) MCP dual-die
(bootloader) MCP dual-die
(bootloader) TAG:mono-die = 0x0
(bootloader) Device CID is not super CID
(bootloader) CID is VODAP001
(bootloader) setting->cid::VODAP001
(bootloader) serial number: XXXXXXXXXXX
(bootloader) commandline from head: no_console_suspend=1
(bootloader) command line length =497
(bootloader) active commandline: board_vision.disable_uart2=0 board_visio
(bootloader) n.usb_h2w_sw=0 board_vision.disable_sdcard=0 diag.enabled=0
(bootloader) board_vision.debug_uart=0 smisize=0 userdata_sel=0 androidbo
(bootloader) ot.emmc=true androidboot.baseband=26.10.04.03_M androidboot
(bootloader) .cid=VODAP001 androidboot.batt_poweron=good_battery androidb
(bootloader) oot.carrier=VODA-UK androidboot.mid=PC1011000 androidboot.ke
(bootloader) ycaps=qwerty androidboot.mode=normal androidboot.serialno=SH
(bootloader) 0BERT06529 androidboot.bootloader=0.85.0013 zygote_oneshot=o
(bootloader) ff kmemleak=off no_console_suspend=1
(bootloader) aARM_Partion[0].name=misc
(bootloader) aARM_Partion[1].name=recovery
(bootloader) aARM_Partion[2].name=boot
(bootloader) aARM_Partion[3].name=system
(bootloader) aARM_Partion[4].name=cache
(bootloader) aARM_Partion[5].name=userdata
(bootloader) aARM_Partion[6].name=devlog
(bootloader) aARM_Partion[7].name=pdata
(bootloader) partition number=8
(bootloader) Valid partition num=8
(bootloader) jump_to_kernel: machine_id(2245), tags_addr(0x4000100), kern
(bootloader) el_addr(0x4008000)
(bootloader) -------------------hboot boot time:66802 msec
FAILED (status read failed (Too many links))
finished. total time: 8.078s
I am guessing that the "FAILED" line at the bottom is another way of saying "Sorry Mate, your phone is knackered!".
I also tried selecting "Recovery" from the menu - that brought up a black screen with the two green arrows around the device picture. This lasted for about 10 seconds, then the phone vibrated about 6 times and went totally blank again - no reboot, no splash screen nothing.
When I try and select the "Factory Reset" option, nothing happens at all. I can move up and down to it using the vol keys, but when I click the power button to select it, nothing happens.
Thanks for all the suggestions anyway - I guess I'll have to get the trusty old G1 unlocked.
I don't think I'll ever tie myself into a two year contract again - bit annoying to be paying for two years when you only get 13months out of the phone!
sry to hear that it didn´t work... but delete the serial number of your phone in your posting.
maybe there is a way to use fastboot for factory reset... but i don´t know how :S
ok... this should be the commands:
fastboot erase userdata
fastboot erase data
fastboot erase cache
Thanks again hoffmas - unfortunately when I run those commands I get this:-
D:\AndroidDevelopment\android-sdk_r12-windows\android-sdk-windows\tools>fastboot erase userdata
erasing 'userdata'...
FAILED (remote: not allowed)
finished. total time: 0.016s
Not looking good.
I'm guessing the "FAILED (remote: not allowed)" means pretty much nothing will work.
Thanks again for your help - it is much appreciated.
yes you are right... looks like you need eng hboot to do this
sry, but i have no idea what else you could try... maybe someone else knows better
Hi all,
I've created a simple guide to restore your HTC One M8 back to stock firmware while still being on S-ON.
This guide will provide you with all the files required to restore your EUROPEAN device back to stock.
If you have an device from another region, you'll need to find the RUU & recovery image yourself. (see below)
Prerequisites:
- HTC Drivers (just install HTC Sync and the included drivers, then remove HTC Sync)
- Fastboot package
- Stock recovery.img (you'll need the recovery.img with the same fw version as the RUU you're going to flash) (Link to 4.16.401.10 recovery.img for European non-carier devices)
- The RUU for your region/carrier. (Link to 4.16.401.10 for European non-carier devices)
If you have an USA /USA carrier device, go here for the RUU files
If you have an device from another region than Europe or USA, good luck finding the correct RUU
Look here to find recovery.img files for all regions (thanks to @exocetdj)
Because this guide is intended for S-ON, only the RUU for your region/carrier will work.
If you don't have an RUU or cannot find one for your region/carrier, S-OFF your device and follow this guide to restore your HTC One M8 back to stock. (thanks to @EddyOS)
After you've gone trough all steps;
- The red text during boot will be gone
- You'll have the stock firmware, system, recovery and boot.img
- Your bootloader will say "Relocked"
- Your bootloader will say "Software status: Official"
Let's start:
Step 1:
Start the RUU exe by double clicking on it, it will take a few seconds before it starts. After it has started, do not continue but go to your temp folder (type %TEMP% in your address bar)
Find the folder with the temporary files from the RUU (mine was called: {C48DBAA3-1CC0-4DF6-B069-B9CCB27F93C9})
Inside this folder there should be a few files and another folder with a long code as name (mine was called: {50F2F878-636A-496F-A7CB-544C067E0C4B})
Inside this folder, scroll down until you find rom.zip, open this file
Extract boot_signed.img and place it in a folder with the downloaded stock recovery and the fastboot.exe file
Now close the RUU installation wizard
Step 2:
Turn off your device
Hold VOL-Down + Power, after a few seconds you'll be in the bootloader. Now release the buttons
Navigate with the volume buttons to fastboot and confirm with the power button.
Step 3:
You should now have a folder with the following files:
- fastboot.exe
- AdbWinApi.dll
- AdbWinUsbApi.dll
- boot.img (extracted from the rom.zip)
- recovery.img (see prerequisites)
Inside the folder while holding shift, click right mouse and choose Open command window here
Before starting, it's recommended to rename the recovery file to recovery.img and the kernel to boot.img
Type the following commands in order (make sure to check the output and see if every command is successful before executing the next command)
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot oem lock
This will push the stock kernel & recovery and relock your device.
Step 4:
Open the RUU installation wizard again and follow the instructions.
It will start flashing the RUU on your device.
After 8-12 minutes, the installation will be complete and your device will boot into system.
Step 5: (optional)
Power off your device
Hold VOL-Down + Power, after a few seconds you'll be in the bootloader. Now release the buttons
Verify that your bootloader says "Relocked" & "Software status: Official"
Congratulations, your device is back to stock again. After it's finished booting and optimizing 261(!) pre installed apps, you'll be greeted by the setup wizard on your phone.
If you have any questions, let me know.
Common problems:
Fastboot cannot find my device?
- try reinstalling the HTC drivers included with HTC Sync, and make sure to remove HTC Sync afterwards but leaving the drivers installed
I've got error 155 when trying to flash the RUU
- make sure your bootloader is locked. This tool only works when you have stock kernel, recovery and your bootloader is locked or relocked.
Reserved
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
This is a great guide for those that just want to return to stock for their own purposes. However, this will not be enough for sending the phone into warranty, for that you'll need to take a few more steps with S-Off to get that RELOCKED flag to say LOCKED.
dima470 said:
This is a great guide for those that just want to return to stock for their own purposes. However, this will not be enough for sending the phone into warranty, for that you'll need to take a few more steps with S-Off to get that RELOCKED flag to say LOCKED.
Click to expand...
Click to collapse
From my experience with HTC warranty repairs, they don't really care about the bootloader being 'relocked', S-Off is a more common cause for them to not repair the device.
But, above differs per repair center / per country
al_wizard said:
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
Click to expand...
Click to collapse
Where did you bought your device?
al_wizard said:
TAMPERED
UNLOCK
M8_UL PVT SHIP S-ON
HBOOT- 3.16.0.0000
RADIO-1.16.2133156.UA15g
OpenDSP-v38.2.2-00542-m8974.0311
OS-1.54.401.10
eMMC-boot 2048MB
ــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــــ
This is my phone , should i do any thing more or just the steps u mentioned???
I was told that i must upgrade my firmware, must i ??
Thanks
Click to expand...
Click to collapse
You are S-ON so you need to relock the bootloader and run the ruu.
If you want to give all info to work with you need to post the outcome of :
Fastboot getvar all
Delete the serial and imei and post the list here.
Or check the firmware & nand backup thread here in the general section. Restore the stock rom and recovery and perform ota updates which also will upgrade the firmware
---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------
Joery360 said:
From my experience with HTC warranty repairs, they don't really care about the bootloader being 'relocked', S-Off is a more common cause for them to not repair the device.
But, above differs per repair center / per country
Where did you bought your device?
Click to expand...
Click to collapse
Has nothing to do with where he bought it from, it is depending on the phones hardware & software, for all we know its imported.
The specs are important not where he got it from. And you can't tie it down on how repair centers handle the phones....that's a matter of good luck !
Joery360 said:
Where did you bought your device?
Click to expand...
Click to collapse
I bought it second-hand from Qatar if you mean country.
Hi. I tried to use this guide but it I couldn't follow it through. I have relocked, tempered, S-ON, CID : TMOB102 phone. It is stuck in the HTC logo after a full wipe from twrp. I don't have OS, and the main version is empty. So far I have tried all the European RUU which gave CID error and 2 T-Mobile RUU's with MID error both. Can anyone give me a suggestion?
Problem extracting boot_signed.img
When I try to extract the boot_signed.img akk I get from Winzip is "cant find central directory"
Any ideas??
This is a great guide for those that just want to return to stock for their own purposes.
Hi,
I just needs to get OTA on my phone and i dont mind it being tampered or unlocked.
Will this method work on my phone ?
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.2133156.UA15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH495WM01309
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
:/
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.895s
I have no OS now if I try to reboot I get stuck on boot logo. What can I do to get back to stock with OTA and everything?
C:\Users\Ali\Desktop\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.61.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
thanks this helped me revive my m8
Pc can't identify my device. phone gets htc logo then it turns black and disconnects from pc. RUU wiz error (170) usb connection error.
royalkalana said:
Hi,
I just needs to get OTA on my phone and i dont mind it being tampered or unlocked.
Will this method work on my phone ?.....
Click to expand...
Click to collapse
Yes
gorner92 said:
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting..
Click to expand...
Click to collapse
Please check if your device is unlocked. You can't flash boot.img's while on a locked bootloader.
Cpre said:
Pc can't identify my device. phone gets htc logo then it turns black and disconnects from pc. RUU wiz error (170) usb connection error.
Click to expand...
Click to collapse
Reinstall the HTC drivers.
gorner92 said:
I tried to flash the boot.img but I get this error:
C:\Users\Ali\Desktop\Fastboot>fastboot boot boot.img
creating boot image...
creating boot image - 8994816 bytes
downloading 'boot.img'...
OKAY [ 0.894s]
booting...
FAILED (remote: not allowed)
finished. total time: 0.895s
I have no OS now if I try to reboot I get stuck on boot logo. What can I do to get back to stock with OTA and everything?
C:\Users\Ali\Desktop\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.33.61.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.020s
Click to expand...
Click to collapse
You are using the wrong command ! It's :
Fastboot flash boot boot.img
NOT
Fastboot boot boot.img ! That's why you got stuck. And indeed make sure the bootloader is UNLOCKED before you flash !
While i don't even know flashing the boot.img and recovery seperatly first is actually needed because all that's needed is to relock the bootloader and run the ruu.exe or the temp rom.zip via sd card.
afaik the ruu method takes care of the boot.img and recovery on its own.
Got a problem with 3rd command (locking oem) in step 3. It goes like this:
C:\adb>fastboot flash boot boot.img
target reported max download size of 1826021376 bytes
sending 'boot' (8780 KB)...
OKAY [ 1.001s]
writing 'boot'...
OKAY [ 0.464s]
finished. total time: 1.465s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1826021376 bytes
sending 'recovery' (16044 KB)...
OKAY [ 1.710s]
writing 'recovery'...
OKAY [ 0.646s]
finished. total time: 2.357s
C:\adb>fastboot oem lock
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id = 0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Too many links))
finished. total time: 1.194s
My getvar all before flashing:
version: 0.5
version-bootloader: 3.19.0.0000
version-baseband: 1.22.21331147A1.29G
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
meid: 0000000000000000
product: m8_ul
platform: hTCBmsm8974
modelid: 0P6B10000
cindum: HTC__032
Now my phone is stuck on my ROM's boot logo and now I can't access bootloader.
EDIT:
I've managed to access bootloader by holding power + volup and then holding vol down. After that installing via RUU went smooth.
Hi, I followed your instructions, but before I could start with 4th device booted up and i accidentaly accepted upgrade. It rebooted and upgraded the device, and then stuck on boot screen. Now I try to update it through RUU but it says image version 4.16.401.13, and I can't find RUU for that version. Any ideas? Can I somehow reinstall twrp and restore nandroid backup?
P.S. in bootloader it still says software status: modified :/
P.P.S. I still managed to make RUU go through all the steps, from a billionth time. It would usually stuck on steps 0, step 1, or step 3. Now it seems like it's booting fine... Time to shower away all the cold sweat from my body.
Hi Guys,
I have windows 8.1 and can't open rom.zip file. I have an error : The compressed Folder is invalid. Installed winzip, 7-zip - can't go ahead.
If you are having trouble sending the ruu and you are stuck at sending 0/7 or 1/8 and only htc logo. then just delete htc sync manager from your pc!!!
Hi All,
I have seemingly broken my system partition and can't boot into Android.
The phone always boots to the bootloader.
Fastboot, Hboot, and stock recovery all work.
Factory reset works, but fixes nothing.
Flashing TWRP works, but it fails to boot into the recovery and returns to the bootloader.
I do not have S-off. I cannot try the Sunshine S-off as I cannot boot the phone.
I have tried flashing a matching stock rom (easy-firmware com/index.php?a=browse&b=category&id=722), but it fails as it has a different CID.
This is my getvar output.
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: [email protected]
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.05.980.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a51_tuhl
(bootloader) platform: hTCBmsm8939
(bootloader) modelid: 0PFJ50000
(bootloader) cidnum: HTC__039
(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: 735c2625
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
(bootloader) mfg-name: 0001
I'm in New Zealand, and I believe the phone is the Australian version, CID: HTC__39.
Does anyone know how I can fix this?
Thanks in advance.
James
I haven't seen a working TWRP for your device model.
Which twrp have you tried? Did you unlock your bootloader?
tomal said:
I haven't seen a working TWRP for your device model.
Which twrp have you tried? Did you unlock your bootloader?
Click to expand...
Click to collapse
Yes, bootloader is unlocked.
I've tried a few of the recoveries on the 820 forums, though I don't remember exactly which ones now.
Edit: This one: "Desire 820 (all models with MSM chipset) TWRP 2.8.7.0"
The working recovery I have is not my original stock one, but one I found on the forums.
Edit: I guess I should mention what I did to break it:
Before I knew the the 820s was dual-sim, I followed these instructions: "[Desire 820s][A50ML]Root - CWM Recovery - Stock Roms - Stock Rom Flashable Zip"
I rooted the phone with Kingroot, but nothing stuck after a reboot.
So without thinking, I flashed a boot img that was meant to allow permanent root onto a partition - thus breaking the system.
I find it disappointing when manufacturers make multiple versions of the same device and I have the one with the least development.
Do you know of anything else I can do to fix the system on the phone?
From the description of above, it seems the variant of a 820n.
emjas said:
I flashed a boot img that was meant to allow permanent root onto a partition - thus breaking the system
Click to expand...
Click to collapse
Check the following link:
0PFJIMG_A51_TUHL_K44_DESIRE_SENSE60_Optus_AU -
http://mobilefileserver.com/category.aspx?get=39048
Thanks for that tomal.
I'll give it a go sometime and return with the result.
Hey tomal, I've successfully restored my phone by flashing the right firmware. Thanks for finding it.
Do you know if it is possible to permanently root or s-off this model?
Kingroot works, but system changes are reverted on reboot.
The modified boot.img and twrp recoveries found on the forum don't work and make the phone unbootable, until I flash the stock img back onto it.
Hello,
The first day I got my moto x style (XT1572) I started to root, everything was more or less well until I tried to install the SU when I finished installing the binary from the TWRP custom recovery-3.0.2-0- clark you say yes to install the root since the phone would not start and remains in boot loop.
After much look I followed some tutorial XDA (http://forum.xda-developers.com/moto-x-style/help/brick-downgrade-6-0-to-5-1-heeeeelp-t3253716) to return to flash the phone with the rom that theory came from factory cbox1s_XT1572_CLARK_RETEU_6.0_MPHS24.49-18-3_cid7_subsidy-DEFAULT_CFC.xml after following all the steps mobile and well lit and seems it was all sorted.
Well, I went back to the load to make root and remove the message that the bootloader was unlocked this time all fu well, except now every time I reboot I enter into fastboot mode and have to select START to boot normal to me.
Any ideas or suggestions to fix it?
regards,
PD: Sorry for my google translate english i'am spanish a my english level is very bad :crying:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
same problem with Motorola z xt1650-03 , unlocked bootloader , every time I start up remain stuck in fastboot mode , after ,push the power button for start , and start normal.
I try to reload stock firmware 7.0 with fastboot mode but when try to flash partition.gpt he say bad key .
now I used like this ,
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
What? how do you do it? can you tell me how to do it more specific? I'm new so I don't understand what you mean and how you do it :/
thank you.
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
You saved my [email protected]#! Thanks.
I'm trying help a friend with her Moto X Style. The buttoms RETURN, HOME and APP is not working. I'm trying upload a ROM, but I got errors everytime and the fastboot was entering every boot.
acejavelin said:
Moto devices have a flashing mode called "fb_mode" that when enabled causes the bootloader to start on each boot, it is used for flashing stock firmware images since in some cases the device needs to reboot after flashing a certain partition or image and it needs a way to return to the fastboot mode. Remember when flashing a stock image you may have entered "fastboot oem fb_mode_set"? If not then a toolkit or other flashing tool may have done it but not cleared it correctly. To clear it manually you need to literally clear it with a fastboot command... With the phone in the bootloader, enter this command from your computer"
fasboot oem fb_mode_clear
And reboot, it should no longer go to the bootloader unless you are holding VOL DN and the operating system should start normally.
Click to expand...
Click to collapse
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Sam to me. Any help?
ninormalen said:
Sam to me. Any help?
Click to expand...
Click to collapse
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.
typo - fastboot, not fasboot
fastboot oem fb_mode_clear
fastboot oem fb_mode_clear
Click to expand...
Click to collapse
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
lucas.passos said:
When I type this commend, I get the following error:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
Can someone tell me whats is the problem?
Click to expand...
Click to collapse
There is no problem... The Moto X does not have A/B software slots, the messages above are merely informational and completely normal.
With mfastboot there is no messages like this. Only "OKAY" one
However it didn't help with my Moto G (falcon).
What helped was checking the kernel. My "smartness" told me to flash Nouagt when I had Pie rom...
Dunken415 said:
Yea I do need help, I had flashed a custom rom with twrp recovery on my phone but every time I reboot I either loads into recovery or boot loader if I fb mode clear or not. Even if theirs a system to boot, I have to manually boot into through boot loader and start. If I go to bootloader logs it just says reboot mode set to fastboot.[/QUOTE
same problem here brother did you find any solution to it?? please help me brother.
Click to expand...
Click to collapse
sagutxo97 said:
SOLVED, the problem was the BP Tools in the fastboot, i had "Fastboot Reason: UTAG "bootmode" configured as fastboot" i changed to "Normal Powerup" and all perfect
Click to expand...
Click to collapse
How'd you do that? i have the same problem how do switch back to normal powerup?
XT-1570 "bootmode-recovery"
Dunken415 said:
I did this several times and it set continues it say fasboot reason reboot mode set to fastboot and I tried fastboot oem fb_mode_clear but it just says boot loader slot count not found and etc
Click to expand...
Click to collapse
I am having the same issue. Would appriciate any help.
E:\fastboot oem fb_mode_clear
...
OKAY [ 0.000s]
finished. total time: 0.016s
PS E:\Backup\Android - XT1570> fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.43
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: no
(bootloader) hwrev: 0x82A0
(bootloader) radio: 0x3
(bootloader) emmc: 64GB Toshiba REV=07 PRV=00 TYPE=57 PNM=064G38
(bootloader) ram[0]: 3072MB SK Hynix S8 SDRAM DIE=6Gb M5=x6 M6=x3 M7=x0
(bootloader) ram[1]: M8=x3B
(bootloader) cpu: MSM8992
(bootloader) serialno: LX7C2xxxxx
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0xDEAD
(bootloader) uid: EFFA2C001E000000000000000000
(bootloader) unlocked: Not supported
(bootloader) securestate: Engineering
(bootloader) iswarrantyvoid: Not supported
(bootloader) mot_sst: 1
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 35550006xxxxxxx
(bootloader) meid:
(bootloader) date: 04-30-2015
(bootloader) sku: XT1570
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Sat Jul 18 7:57:55 UTC 2020"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retasia_ds/clark_ds
(bootloader) ro.build.fingerprint[1]: :6.0.1/MPHS24.107-58-5/4:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.221.5.clark_retas
(bootloader) ro.build.version.full[1]: ia_ds.retasia.en.03
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: <not found>
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-gb67345b (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goo
(bootloader) kernel.version[2]: gle 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Sep 29 00:24:52 CDT 2016
(bootloader) sbl1.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) rpm.git: git=90a41be
(bootloader) tz.git: git=16279de-dirty
(bootloader) hyp.git: git=16279de-dirty
(bootloader) sdi.git: git=52a3f93
(bootloader) pmic.git: git=MBM-NG-VA0.43-0-g8cea836
(bootloader) aboot.git: git=MBM-NG-VA0.43-0-gde54c6f
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.172s
C:\fastboot oem fb_mode_clear
...
OKAY [ -0.000s]
finished. total time: -0.000s