Having an Issue
Trying to get past 2.30.401.1 I've attached screens of my current inventory
Output of fastboot:
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: XXXXXXXXXXXXXXX
(bootloader) version-main: 2.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: 11111111
all:
OLD BOOTLOADER
***LOCKED***
htc_hiau_ml_tuhl PVT S-ON
LK-1.01.0000
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-2.30.401.1
Oct 18 2016, 17:41:47(821792)
CURRENT BOOTLOADER
***UNLOCKED***
htc_hiau_ml_tuhl PVT S-ON
LK-1.01.0000
RADIO-UNKNOWN
OpenDSP-UNKNOWN
OS-2.30.401.1
Oct 18 2016, 17:41:47(821792)
I've Registered at HTC Dev and SuperCID my Phone, however any rom I try I am thwarted
with SDCard Method I get "12 RU_ZIP_ERROR"
with RUU's I get "132 SIGNANURE ERROR"
I believe it's firmware that's blocking me but I'm unclear as to the next RUU/OTA that will get my firmware to the needed level as I'm also unclear as to the Process that gets just the firmware on the phone. I've been for the last 2 days all though XDA, GSM, and TAS forms, I'm not new to rooting, flashing. nor modding, I spent a lot of time here when WM 5,6, and 7 were the big thing.
My goal is to get to a TMobile Latest base then try on some new Kitchens (are they still called Kitchens?)
Any help would greatly appreciated and any additional info I will get up as requested
Cid and mid must match firmware being flashed. Supercid is no longer valid.
Unlock the bootloader, root, s-off via sunshine, change cid and mid to match the firmware you're flashing.
Make sure your firmware matches your model of phone too.
Fail to Gain "Temproot" or PermRoot" with sunshine since I've already dev unlocked there is some other issue happening
Don't change your phone's MID!
You own the M9+ which contains a mediatek processor. That's a completely different phone than the M9 which contains the qualcomm snapdragon 810. None of the files in the M9 forum can be used with your phone since they're not compatible.
Edit: And you're already using the latest firmware that's available for that phone. In addition, there don't seem to be any branded firmware variants. I could only find unbranded European and Asian firmware versions/RUUs.
Flippy498 said:
Don't change your phone's MID!
You own the M9+ which contains a mediatek processor. That's a completely different phone than the M9 which contains the qualcomm snapdragon 810. None of the files in the M9 forum can be used with your phone since they're not compatible.
Edit: And you're already using the latest firmware that's available for that phone. In addition, there don't seem to be any branded firmware variants. I could only find unbranded European and Asian firmware versions/RUUs.
Click to expand...
Click to collapse
Thank you Flippy that was informative - I've been attempting first with the EU versions of the OTA's like
0PJAIMG_HIMA_UHL_N70_SENSE80_MR_HTC_Europe_4.14.401.7_Radio_01.01_U114401011_117.00.61117G_2_F_release_490768_signed_2_4 which I understood supported the M9+ to get to Nougat I can live with that since the phone works on TMobile quite well but I can't even get TWRP installed
sending 'recovery' (39400 KB)...
OKAY [ 2.656s]
writing 'recovery'...
(bootloader) HOSD CL#821792
(bootloader) [email protected]
(bootloader) ERR partition_partial_update[ERR]: write failed. fd=16, n=-
(bootloader) 1, No space left on device
(bootloader) ERR partition_partial_update[ERR] lseek64 error!!, offset=3
(bootloader) 4603008
(bootloader) ERR partition_partial_update[ERR] lseek64 error!!, offset=3
(bootloader) 5651584
(bootloader) ERR partition_partial_update[ERR] lseek64 error!!, offset=3
(bootloader) 6700160
(bootloader) ERR partition_partial_update[ERR] lseek64 error!!, offset=3
(bootloader) 7748736
(bootloader) ERR partition_partial_update[ERR] lseek64 error!!, offset=3
(bootloader) 8797312
(bootloader) ERR partition_partial_update[ERR] lseek64 error!!, offset=3
(bootloader) 9845888
(bootloader) [email protected]%
(bootloader) Update partition OK
(bootloader) [email protected]
OKAY [ 1.844s]
finished. total time: 4.500s
So I quess I'm resigned to Andriod 6
No, that's an OTA for the M9 (hima). You can't use it with the M9+ (hiau).
Mediatek devices can't get flashed with fastboot. You need special tools for them. In addition, the M9 twrp version isn't compatible with the M9+.
Sent from my Moto X Style using XDA Labs
Well guess I'll save up for a U12+ I really Liked my M8 course that was a WM Phone and Next to my Elite X3 the quality is superb Everyone @ work has a Sthis or Sthat and everyone is always replacing the back cover or Screen now that I've taken the Android plunge (all Microsofted of course) I think I'll remain an HTC fan (or a Doogee S60)
Thanks again for your insight there's not much in direct Plus Info even in searches I believe if a variant has this much distinguishing changes to the norm it should get it's own forum space
It actually has. I asked the mod team to move this thread and it looks like it's already located in the M9+ section. I wouldn't consider the M9+ as a M9 variant, btw. The two devices only share some parts of their look and the "M9" in their marketing naming. Their codenames make that quite clear (Hima VS Hiau). If one was a variant of the other the codename would be the same but the suffix would differ.
A general advice in regard to HTC devices: take a close look at the specifications before you buy one. If it has a snapdragon processor you can buy it. If it has a mediatek one you should stay away from it.
The mediatek ones don't get much support. Neither from htc nor from xda devs.
Sent from my HTC U12+ using XDA Labs
Related
So, you may have made a bad flash, having trouble to S-OFF or just want to go back to 100% stock ROM and recovery. In that case, the easiest solution is to run your RUU (ROM Update Utility). But unlike the conventional method, this guide is about extracting the rom.zip from your RUU for a faster and more comprehensive installation. The extracted rom.zip will also allow the possibility to decrypt the RUU in order to get access to all the individual files inside the encrypted archive. So, if you want to flash, for example, only the stock recovery, you can do it without having to flash the entire RUU ROM, which will restore the phone's entire software.
Note: Your HTC One can be either S-ON or S-OFF in order to successfully flash RUU rom.zip. But if your device is S-OFF, you do not need to re/lock your bootloader.
Follow the instructions in the given order to avoid any hiccups or possible bricking of your device:
1. You will need to know your HTC One's MID and CID. These codes will allow you to find the required RUU for your phone.
You need adb and fastboot. Go to your Bootloader. Select Fastboot. Connect your HTC One with its original USB cable to your PC. Do:
Code:
fastboot getvar all
and you should see a list of important information about your device. In particular, note the modelid (MID) and cidnum (CID). If you get nothing, there is an issue with the USB connection between your phone and PC.
2. Find the correct RUU. Here's a thread: http://forum.xda-developers.com/showthread.php?t=2428276 to find the correct RUU from the filename but more importantly, make sure that both the MID and CID match exactly with your device. You also need to pay attention if you need the M7 UL or M7 U version, which is in the filename of the RUU. If you can't find your RUU from that site, just google or search on XDA. However, not all HTC One variants have RUUs. But if you are already S-OFF, you can change your MID and CID, which will allow you to use any RUU: http://forum.xda-developers.com/showthread.php?t=2322820
3. Extract the RUU and grab the rom.zip file. This is the most important file you need from the RUU and afterwards you can delete the RUU exe if you want. To get the rom.zip from your RUU exe file, you just need to run the RUU exe file once, and then when the window is ready and waiting for you to press on the "Next" button, just leave it open and go to your temp folder. I'm using Windows XP SP3 32-bit and my temp folder is located at this path: C:\Documents and Settings\Administrator\Local Settings\Temp
Now, you will see several files and folders. Sort everything in that temp folder based on "Date Modified" with the most recent folder showing up above all other folders. This is the folder you want. The folder name will be bunch of letters and numbers. Inside that folder you will find several files, but what you need is rom.zip and android-info.txt. Copy both these files and paste them somewhere safe on your hard drive. The android-info.txt contains crucial information about the compatibility of that RUU for your phone. Here's the android-info.txt extracted from my RUU exe:
Code:
modelid: PN0711000
cidnum: HTC__001
cidnum: HTC__J15
cidnum: HTC__A48
cidnum: HTC__M27
mainver: 1.29.401.2
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
You can then verify that you have the correct RUU if the modelid matches that of your phone and if you can see your cidnum in that list. If either (or both) of the modelid or cidnum does not match that of your phone, the RUU process will fail. The mainver is the firmware that is going to be flashed onto your phone.
For easy reference, create a new folder and name it exactly like the RUU exe file and put the rom.zip and android-info.txt in there so you won't have trouble identifying that rom.zip file later if you need to flash it again. Now, you can close the RUU installation window and all the files in that temp folder containing rom.zip will be instantly erased. Note that if you open the rom.zip with Winzip/Winrar, you will see a list of all the files but if you try to extract or double-click to open any of these files, you will get an error saying that the file is corrupt. This warning is only due to the files being encrypted by HTC, since the RUU is an official release and is digitally signed. To access those encrypted files, you will need to decrypt them on Linux.
4. Go to your bootloader. Do:
Code:
fastboot oem rebootRUU
This will reboot your HTC One and you will see a black screen with a silver HTC logo.
Now, you will need to access the rom.zip file and flash it. I have copied my rom.zip to my adb folder located at: C:/mini-sdk/rom.zip
So, i type:
Code:
fastboot flash zip C:/mini-sdk/rom.zip
Don't touch anything during the flash process. It will start and after some time, you will see FAILED error. Don't worry, it's the file preparation process if you have firmware higher than that of the RUU. Just do the same command again and the flash process will complete successfully this time. Look at the Command Prompt to know when the flash is complete. At the same time if you look at your phone, you will notice a green progress bar. When the flashing is complete on the Command Prompt, you will notice that the green bar is stuck at about 95%. This is normal. It's just a bug in the progress bar - what matters is the output from the Command Prompt window.
5. Then, you reboot. Do:
Code:
fastboot reboot
This will restart your phone. Let it boot up. It might take a little longer for the first boot up sequence. You will then have completely stock software (firmware & ROM). Go to your bootloader and check. Your S-ON/OFF and Bootloader lock/unlock are unchanged from before the RUU rom.zip flashing procedure. You can now also receive OTA updates.
I hope this has been helpful. Just press the THANKS button! :good:
If you're S-OFF you do NOT need to relock the bootloader to flash an RUU - just putting that out there
Opening android-Info.txt
Hey man,
as first thanks a lot, i got it all thanks to you but i'm still having trouble finding the right RUU.
I know you said that opening android-info.txt would help, and that it wont work with WinRar.. which i can see.
I have downloaded the .zip RUU, so.. my question is how do i open this txt file if not without WinRar.
Thanks again
emir1396 said:
Hey man,
as first thanks a lot, i got it all thanks to you but i'm still having trouble finding the right RUU.
I know you said that opening android-info.txt would help, and that it wont work with WinRar.. which i can see.
I have downloaded the .zip RUU, so.. my question is how do i open this txt file if not without WinRar.
Thanks again
Click to expand...
Click to collapse
You don't know how to open a .txt extension file? :cyclops:
Just use any text viewer/editor. I use Notepad++ and you can download it here: http://notepad-plus-plus.org/
Hi I need help!
i do all the steps and i have this massage:" failed remote:24 persing android info fail"
---------- Post added at 08:00 PM ---------- Previous post was at 08:00 PM ----------
Hi I need help!
i do all the steps and i have this massage:" failed remote:24 persing android info fail"
italgal said:
Hi I need help!
i do all the steps and i have this massage:" failed remote:24 persing android info fail"
Click to expand...
Click to collapse
Where do you get this error? At which step? Please provide more information to help resolve your problem.
i try to install many ruu i need ruu 4A.17.3250.14
thanks I will try this method in future.:good::good::good:
i have those
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA38XW900273
(bootloader) imei: 354435053862991
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
italgal said:
i have those
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA38XW900273
(bootloader) imei: 354435053862991
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 4192mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.046s
Click to expand...
Click to collapse
4A.17.3250.14 is baseband version
you need to search for an RUU based on cidnum and model id
judging from your cid .. "HTC_K18" ..its kinda rare .. i think your cid belongs to Israel and to my knowledge there is no RUU for your model
Please Help
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the
flash zip
Click to expand...
Click to collapse
i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
---------- Post added at 10:29 PM ---------- Previous post was at 10:17 PM ----------
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the
Quote:
flash zip
i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
DrDrake23 said:
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
---------- Post added at 10:29 PM ---------- Previous post was at 10:17 PM ----------
Hello dear friend, i am so confused, i changed from apple devices to android, and i still don`t know many things.....
I just need some help, i try to do everything as you wrote and explained but when i get to the
Quote:
flash zip
i get some errors
This is the error:
target reported max download size of 1526722560 bytes
sending 'zip' (671277 KB)...
OKAY [35.288s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 93.188s
This is my information : version: 0.5
version-bootloader: 1.55.0000
version-baseband: 4A.21.3263.04
version-cpld: None
version-microp: None
version-main: 3.62.401.1
version-misc: PVT SHIP S-ON
serialno: FA36RW901770
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3812mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-bb768ae1
hbootpreupdate: 11
gencheckpt: 0
This is the RUU i use : ota_m7_ul_jb43_sense55_mr_htc_europe_3-62-401-1-2-24-401-8_release_338160gxmo5sd9337kadux
Please help, if you cane xplain me what to do....I implore you i wan`t my HTC back to normal
Click to expand...
Click to collapse
When you get the failed message, run the flash zip command again.
Sent from my Nexus 4 using Tapatalk 2
fridgeman said:
When you get the failed message, run the flash zip command again.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Lol that's not what that error is. That's a signature verify fail and I'm pretty sure that means they're trying to flash an unsigned file or a file for another CID on a phone with security on.
Didn`t work
fridgeman said:
When you get the failed message, run the flash zip command again.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
I did it still the same thing
---------- Post added at 03:33 PM ---------- Previous post was at 03:18 PM ----------
xcesivemastub8ah said:
Lol that's not what that error is. That's a signature verify fail and I'm pretty sure that means they're trying to flash an unsigned file or a file for another CID on a phone with security on.
Click to expand...
Click to collapse
Yes i got S-ON please help me what can i do to make it work
Iam using mac, can i use this steps or not? I have sucseed to unlock my htc one S-on but when i try to do recovery the mobile stucks every time ,
@DrDrake23
To find the correct RUU compatible with your HTC One, you need to look at these information:
modelid: PN0710000
cidnum: HTC__032
Then search for the RUU. I was able to find 2 versions at this location: http://www.htc1guru.com/downloads/ruu-file-downloads/
Also, according to this list: http://forum.xda-developers.com/showthread.php?t=2445289 your CID matches the region HTC-EastEurope HTC__032
These 2 RUU's should work for your device. You need to use only one of these.
RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
or
RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed
It is usually recommended to use the most recent RUU. In this case, you should first try the 1.28.401.7 RUU.
However, read the description in the comment section on the site for each of these RUU's.
From your phone information:
version-main: 3.62.401.1
This means that you will need to S-OFF first before you are able to run the RUU since your main version is higher than both of these RUU's.
On another note, you should always read up and do enough research before attempting to modify your phone. Do you really need to go back to 100% stock? You could simply flash a stock ROM or even better, a custom ROM. But if you believe you need to return your device to 100% stock condition, start here: http://forum.xda-developers.com/showthread.php?t=2488772 and then you can flash hboot 1.44 and finally run the RUU.
marjanna said:
Iam using mac, can i use this steps or not? I have sucseed to unlock my htc one S-on but when i try to do recovery the mobile stucks every time ,
Click to expand...
Click to collapse
I tested the entire procedure successfully on my Windows XP SP3 32-bit. So, i cannot say if this would work on another OS or if the commands would be the same for that matter. Maybe someone with a Mac can confirm and help you out.
electronical said:
I tested the entire procedure successfully on my Windows XP SP3 32-bit. So, i cannot say if this would work on another OS or if the commands would be the same for that matter. Maybe someone with a Mac can confirm and help you out.
Click to expand...
Click to collapse
Ok i see. It seems that most use pc:s , i have tryied and still trying to find a Mac user , but no luck so far,
I got a 4.2.2 HTC One
HTC Sense Version 5.0
S-On
Unlocked
Tampered
I have heard that its better and safer to change the S-On to S-Off but no luck yet. this guide looks great but i might wait to be secure so i dont brick the phone trying to.
Take care and thanks for replying ..
:laugh::good::laugh::good::laugh:
This process saved me.
I had a bad flash and could not get adb to recognize my device.
Just a quick note, bootlocker must be re-locked if you on S-on.
Thanks for the help man!
DrDrake23 said:
I did it still the same thing
Yes i got S-ON please help me what can i do to make it work
Click to expand...
Click to collapse
If u are s-on you have to re-lock the bootloader...
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.
I have a problem finding my HTC One M9+ Original RUU. I know how to send it back to stock version but i just have no idea where i can download my phone's original RUU.
some info :
Bootloader screen:
*** Software status: Modified ***
*** UNLOCKED ***
HTC_HIAU_ML 128 SHIP S-ON
CID-HTC__J15
LK-1.01.000068332ab2
OS-1.90.401.3
getvar all result :
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: 358812061576910
(bootloader) version-main: 1.90.401.3
(bootloader) boot-mode: download
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__J15
Me too dude. The worst thing I ever did was flash TWRP. I mean, it's awesome....but without the stock recovery forget about OTA updates forever.
you need help ? or you fix your problem ?
I was able to fix mine. Just have to bite the bullet, pay the $25 to S-Off, then Super CID, and flash whatever region rom you want. Finally got mine taking OTA updates by doing the aforementioned and applying the European image back to the phone.
Now, my only problem is I want to do a FULL backup of the phone so I can continue to play around with rooting and adding TWRP. But I have no idea how to back it up without messing up the factory recovery since TWRP kills it.
Clueless.
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
Start up failed:
Your device didn't start up successfully.
Use the Software Repair Assistant on computer to repair your device.
Connect your device to your computer to get the Software Repair Assistant.
Click to expand...
Click to collapse
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8992-A0.4D
(bootloader) product: clark
(bootloader) board: clark
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x2
(bootloader) emmc: 32GB Toshiba REV=07 PRV=00 TYPE=57 PNM=032G72
(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: ZY223MG4VS
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x8d
(bootloader) uid: 16C4F0001E000000000000000000
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
(bootloader) max-download-size: 536870912
(bootloader) reason: Last time flashing failed
(bootloader) imei: 358195071196980
(bootloader) meid:
(bootloader) date: 11-08-2016
(bootloader) sku: XT1575
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Mon Jul 31 20:42:21 UTC 2017"
(bootloader) ro.build.fingerprint[0]: motorola/clark_retus/clark:6.0/MPH
(bootloader) ro.build.fingerprint[1]: S24.49-18-16/8:user/release-keys
(bootloader) ro.build.version.full[0]: Blur_Version.24.231.16.clark_retu
(bootloader) ro.build.version.full[1]: s.retus.en.US
(bootloader) ro.build.version.qcom: <not found>
(bootloader) version-baseband: M8992_1255331.29.01.88.02R SUPER_NA
(bootloader) kernel.version[0]: Linux version 3.10.84-perf-g94afac7 (hud
(bootloader) kernel.version[1]: [email protected]) (gcc version 4.9.x-goog
(bootloader) kernel.version[2]: le 20140827 (prerelease) (GCC) ) #1 SMP
(bootloader) kernel.version[3]: PREEMPT Thu Dec 8 06:11:12 CST 2016
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) sdi.git: sdi.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-VA0.4D-0-g3d9d261
(bootloader) qe: qe 0/0
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier: retus
all: listed above
finished. total time: 0.466s
Click to expand...
Click to collapse
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
C:\Users\Flia Boquense\Desktop\motox>fastboot flash partition gpt.bin
target max-download-size: 512MB
sending 'partition' (32 KB)...
OKAY [ 0.097s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.816s
BOOTLOADER LOG: "version downgraded for primary_gpt"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash boot boot.img
target max-download-size: 512MB
sending 'boot' (40960 KB)...
OKAY [ 1.142s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.857s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash recovery recovery.img
target max-download-size: 512MB
sending 'recovery' (41040 KB)...
OKAY [ 1.143s]
writing 'recovery'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 1.858s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot"
C:\Users\Flia Boquense\Desktop\motox>fastboot flash system system.img
target max-download-size: 512MB
sending sparse 'system' (509631 KB)...
OKAY [ 15.608s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 16.565s
BOOTLOADER LOG: "hab check failed for boot
failed to verify hab image boot
invalid PIV signed system image"
Click to expand...
Click to collapse
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Your bootloader is locked? It appears so...
(bootloader) unlocked: no
(bootloader) securestate: locked
(bootloader) iswarrantyvoid: no
(bootloader) mot_sst: 0
Click to expand...
Click to collapse
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
acejavelin said:
Your bootloader is locked? It appears so...
How are you flashing TWRP with a locked bootloader?!?!?!
With a locked bootloader you cannot downgrade, the version on Moto's official site (MPH24.49-18_18) is actually just MPH24.49-18, which is the original Marshmallow when first released in December 2015. Moto support has been notified of this mistake in version and date on the website and have yet to change it in over 6 months since it was mis-posted.
You require MPHS24.49-18-16, which is the December 2016 security update released via OTA in February 2017, or newer version, but the problem is that it is not available. At this point we do not know if/when newer versions of factory firmware images will leak out or not in the future. The newest version we have available is MPHS24.49-18-8, you can attempt that and skip bootloader.img and gpt.bin, but I am guessing with a locked bootloader it will fail since it is still a downgrade.
You have a locked bootloader, with a bootloader state of 0? Contact Moto for repair, without an unlocked bootloader there is nothing we can can do at this point.
Click to expand...
Click to collapse
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
pizza_pablo said:
I would contact Motorola support and see what they can do for you.
It will help to know which version of the Moto X that you have. Your thread title has Moto X Style, with the model number of the Moto X Pure Edition. The style is XT1572.
I would tell them that you tried to follow instructions listed on the phone with no luck. Remind them that current software is not available on their web site.
Click to expand...
Click to collapse
Sorry, my bad, i have the Pure edition, XT1575. I will try to do that hoping to have some luck.
lcn23 said:
Yes, my bootloader is locked. I understand that to unlock it, i have to get into developer's tools and change some option so I can get the code, am i right? Unluckily, there's no way i can do that since the phone won't start. Any other way to unlock it?
I tried to load other versions but it wont work, the errors i get are the same i get when installing the version from the webpage, so i guess they are related to the fact that they are older versions.
To sum it all, i have a rock with the form of a phone until Motorola's people hear us and upload the latest version??? Any crazy idea i could try to make the phone work?
Thank you for your time acejavelin, really appreciated.
Click to expand...
Click to collapse
Any other way to unlock? Nope, impossible actually.
Basically, you need to contact Moto... because you are still locked and stock it can be repaired, either in or out of warranty. Once the bootloader has been unlocked Moto won't even look at it. And that "Software Repair Assistant" was Verizon specific I guess (weird, right), but you can try it https://www.verizonwireless.com/support/knowledge-base-209216/ since it seems to have support for Moto Z Force (it's in the sample picture) so who knows, might work.
Motorola doesn't release firmware images, except for what is on their webpage (which is old for all models listed) and even their requirements are for an unlocked bootloader. The only firmware images we have are ones that are leaked, and that source has reported that it is very difficult (almost impossible) to access these builds now... I would speculate it in part goes back to Moto's pattern of planned obsolescence, but at the same time these images affect such a small number of individuals that they probably don't care anyway.
---------- Post added at 08:31 PM ---------- Previous post was at 08:29 PM ----------
I just realized this is in the old Moto X 2013 area... I will request a Mod to move it.
MY wife somehow made it power on today in the morning. I guess that's the only hope as I wait for the Motorola Support to give me an answer. Impossible to send it to them for repair as i'm from Argentina and i bought it in USA.
Sorry about the misplacement.
Is there any recovery image I could somehow install bypassing the locked status?? The Windroid application "installs" a TWRP and it somehow manages to switch the CID from 0xDEAD to 0x0009, whatever that means.
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
Will try! Thank you!
dzidexx said:
You can try flash this (from the OP):
https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863
I suggest flash with fastboot. Just like you did before. @lcn23
Click to expand...
Click to collapse
No man, not working. I only got something different when trying to flash partition gpt.bin. The new error message is this one:
C:\Users\Flia Boquense\Desktop\motox\rom16>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.091s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 0.963s
Click to expand...
Click to collapse
Your phone still is dead?
Try to flash only boot & system. @lcn23
---------- Post added at 06:38 PM ---------- Previous post was at 06:35 PM ----------
Are you using the newest minimal adb...?
https://devs-lab.com/download-minimal-adb-fastboot-tool.html
UPDATE: Somehow the fastboot changed, the buttons with the options turned into a menu with options inside a light blue bubble and an image of the android pet with his belly open appeared. Seeing this, I tried to flash the gpt bin dzidexx gave me and it worked, but after that I tried to flash the bootloader and it didn't work. I guess I will try again later, because now I'm leaving to work. I will try what you told me later dzidexx. Thanks.
UPDATE 2: After that happened and i rebooted the phone, now its status switched from "stuck at fastboot" to "doesn't power up". I guess I screwed up. How can I fix that? When I plug it to the computer, the PC makes the sound of something being connected to one of her USB ports, but other than that there's nothing I get, it doesn't even appear in Windows Explorer as a connected device. @dzidexx
Nothing you can do in home.
I think the motherboard is broken(before you asked here) - memory.
Sometimes it happens.
Only warranty repair or other GSM service(motherboard replacement). @lcn23
I guess it has something to do with the aboot, because that was the only thing that got installed when flashing bootloader.img.
With locked BL you cannot check/repair it. @lcn23
Then I guess I hard fkin bricked it, damn me.
@acejavelin any ideas of how can I take it out of QHSUSB state??
lcn23 said:
@acejavelin any ideas of how can I take it out of QHSUSB state??
Click to expand...
Click to collapse
Nope... Bootloader is gone if it's going QLoad mode, nothing can be done now but get Moto to fix it. We don't have the necessary files to flash in this state.
lcn23 said:
Today in the morning my XT1575 didn't boot and got directly into fastboot mode.
Every time I try to start it I get this message:
I searched for a solution but still can't reach one.
I didn't try to downgrade nothing, in fact the phone isn't mine, it's my wife's and she doesn't know anything about flashing ROMs and stuff, so the problem was not there. The phone actually started to get tilted and slow one or two days ago and then today finally "died".
Here's the getvar all I get:
The CID say 0xDEAD. It switches to 0x0009 when I flash TWRP with windroid but I still can't flash any other rom because I keep getting these errors (the rom im trying to install is the official one, from motorola's web, MPH24.49-18_18):
I can't find a way to make it work again, any help will be appreciated, i'm pretty much a noob in all these stuff.
Click to expand...
Click to collapse
Go here, https://forum.xda-developers.com/moto-x-style/general/xt1575-stock-mphs24-49-18-16-files-t3641863, and flash recovery. Then tell us if it works.
Hi.
I have two HTC M9+ phones, one is the rose gold type and the other is gunmetal, details below:
rose gold
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) version-main: 2.30.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__J15
gunmetal
(bootloader) kernel: lk
(bootloader) product: htc_hiau_ml_tuhl
(bootloader) version: 1.0
(bootloader) imei: xxxxxxxxxxxxxxxx
(bootloader) version-main: 2.27.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: READ version-baseband ERROR
(bootloader) version-bootloader: 1.01.0000
(bootloader) mid: 0PK711000
(bootloader) cid: HTC__J15
On the gunmetal one I installed TWRP and rooted it, but being a noob I didn't fully update it first and now I can't take an OTA. My whole approach was wrong I think. I'd like to get the gun metal one back to stock and start again and was wondering if I could use the working one to do so. I did a lot of research trying various ways to back up the working phone:
Trying to boot CWM via fastboot boot so I could create a backup. Apparently this won't work on this phone.
Trying MTKDroidTools / SPFlash, but it seems the MTK6795 isn't supported with those tools
Using ADB to backup, but since my phone is not rooted it will not work. From what I understand if the phone is rooted and/or the root partition was mounted read/write you won't be able to take an OTA so this method wont work either.
Is there another method I am missing where I could backup my entire working phone to flash the one I messed up? I know RUU is a possibility but I'd really like to go this route instead as all most of the locations to download RUU's seem a bit sketchy. Should I even be concerned with this if I can find a signed RUU?
THanks for any help.
simon