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
Hello Everyone, I was attempting root and well alot of things didn't go as planned and as a result I have no recovery, oem-lock as been enabled and I'm only able to boot into fastboot. a "fastboot getvar all" is as follows
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.26(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d6a09b30
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBA.26-0-g87d0ac5
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.323s
Is there anyway back from this? Or is it looking like "get another off ebay, and don't be so [email protected] careless!" Thanks in advance.
tboned82 said:
Hello Everyone, I was attempting root and well alot of things didn't go as planned and as a result I have no recovery, oem-lock as been enabled and I'm only able to boot into fastboot. a "fastboot getvar all" is as follows
Code:
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.26(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE13MB RV=08 PV=0D FV=000000000000000D
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=05 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: d6a09b30
(bootloader) cid: 0xDEAD
(bootloader) channelid: 0x00
(bootloader) uid: 0000000000000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: n/a
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) sbl1.git: sbl1.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) aboot.git: git=MBM-NG-VBA.26-0-g87d0ac5
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.323s
Is there anyway back from this? Or is it looking like "get another off ebay, and don't be so [email protected] careless!" Thanks in advance.
Click to expand...
Click to collapse
Might start here. I'm not sure and can't look right now myself.
http://www.spflite.com/Index.html?Downloads.html
Sent from my [device_name] using XDA-Developers Legacy app
@tboned82
You haven't unlocked the bootloader. OEM lock is not the proper command. You can't just do oem unlock either. You have to get an unlock code from Motorola. You haven't said what you actually did, what happened, what guide you followed, how far you got, nothing.
You have to give some info before anyone can help you.
madbat99 said:
@tboned82
You haven't unlocked the bootloader. OEM lock is not the proper command. You can't just do oem unlock either. You have to get an unlock code from Motorola. You haven't said what you actually did, what happened, what guide you followed, how far you got, nothing.
You have to give some info before anyone can help you.
Click to expand...
Click to collapse
Oh but I have unlocked the bootloader, I got a code and everything I followed all the instructions on this guide
HTML:
https://forum.xda-developers.com/moto-e4/moto-e4-qualcomm-roms-kernels-recoveries--other-development/guide-xt1766-stock-firmware-restoration-t3775347
as well as this one as well
HTML:
https://forum.xda-developers.com/moto-e4/how-to/complete-noob-guide-to-rooting-metropcs-t3701234
I ran into trouble when I formatted /data partition (just wiped it clean, without a way to boot into the system) I then followed the guide in the first link and I'm where I'm at now it's when I downloaded the files from the first link and started issuing the given commands in when oem-unlock when away and it was locked again. But yes I did have the device oem unlocked at one point.
whodisname said:
Might start here. I'm not sure and can't look right now myself.
http://www.spflite.com/Index.html?Downloads.html
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I have done this, without success...I'm just using windows in a Virtual enviroment, though I'm able to access fastboot commands in both my virtualized windows enviroment and my native Manjaro one as well.
tboned82 said:
I have done this, without success...I'm just using windows in a Virtual enviroment, though I'm able to access fastboot commands in both my virtualized windows enviroment and my native Manjaro one as well.
Click to expand...
Click to collapse
Glad you started a thread on this. There is a way out of this.
@kartik verma has a guide that can help you out on this. Since your bootloader is locked again it won't matter if you run the command to lock it back. However, with our variant you might have some trouble, so READ CAREFULLY steps 1-3.
https://forum.xda-developers.com/moto-e4/how-to/moto-e4-guide-stock-firmware-restore-t3661684
Things You Should Know Going Into It:
1. On our variant when you try to erase anything via fastboot is will say "PERMISSION DENIED". Run the command anyway and see what I mean - so you can effectively skip the ERASE PART of the guide. Instead, go straight to reinstalling over the files already there. It does that even when the bootloader is unlocked, and I have no idea why.
2. Download the firmware officially from Motorola from here:https://firmware.center/firmware/Motorola/Moto E4/Stock/ From there, download the following PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml.zip. It's the earliest one I know of that came on my phone that will not give you any problems flashing Magisk v14 later once you restore. Very important.
3. Extract the firmware to a single folder to your desktop. Makes it easier navigating later.
4. Download Minimal ADB and Fastboot. Don't use any other Fastboot. Trust and believe, its easier; Save Minimal ADB and Fastboot to your C:/ Drive.
5. In order to flash the files accordingly, you are going to have to pull firmware individual files (i.e. boot.img and system sparschunk files) to the Minimal ADB folder. Keep track of them.
6. You really only need to follow steps 1-3. Don't go past there.
---------- Post added at 03:52 AM ---------- Previous post was at 03:45 AM ----------
In my case when my phone hard bricked (wouldn't boot past recovery splash or the N/A splash) I could still get to fastboot. I flashed boot.img, and ALL of the system sparse chunk files. That brought me back enough to load recovery and delete everything and flash anew. However, If you think you've deleted the system, plus your bootloader is locked again you're probably going to have to reflash all of those files. I'd say as long as you have fast boot, reflash through fastboot boot.img, and every single system_sparsechunk files. Reboot and see what happens. If it doesn't work, keep on flashing until you re-restore the phone completely. If you start getting errors, refer to the rest of kartik's guide. (Steps 4- to completion) and ask me questions. There really isn't a definitive one size fits all variants for this phone - ours is special.
---------- Post added at 04:06 AM ---------- Previous post was at 03:52 AM ----------
Here is my getvar for you to see in comparison (I blocked off sensitive info like my IMEI and UID)
Code:
Minimal ADB and Fastboot>fastboot getvar all
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8917-BA.09(*)
(bootloader) product: perry
(bootloader) board: perry
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: emmc
(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003
(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F
(bootloader) cpu: MSM8917
(bootloader) serialno: ZY224GRCFF
(bootloader) cid: 0x0016
(bootloader) channelid: 0x8e
(bootloader) uid: ********00000000000000000000
(bootloader) securestate: flashing_unlocked
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei: *classified by order of your government*
(bootloader) meid:
(bootloader) date: 09-13-2017
(bootloader) sku: XT1765
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint[0]: motorola/perry_metropcs_c/perry:7.
(bootloader) ro.build.fingerprint[1]: 1.1/NCQ26.69-46/46:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) poweroffalarm: 1
(bootloader) ro.build.version.full[0]: Blur_Version.26.11.46.perry_metro
(bootloader) ro.build.version.full[1]: pcs_c.MetroPCS.en.US
(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0
(bootloader) version-baseband: M8917TMO_18.08.04.12R PERRY_NA_UMTS_CUST
(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g9acc907-0000
(bootloader) kernel.version[1]: 6-g486eb8a ([email protected]) (gcc ver
(bootloader) kernel.version[2]: sion 4.8 (GCC) ) #1 SMP PREEMPT Tue Jun
(bootloader) kernel.version[3]: 20 09:51:52 CDT 2017
(bootloader) sbl1.git: git=MBM-NG-VBA.09-0-ge2011ab
(bootloader) rpm.git: git=MBM-NG-VBA.09-0-gc6ac81e
(bootloader) tz.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) devcfg.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) keymaster.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) cmnlib.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) cmnlib64.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) prov.git: git=MBM-NG-VBA.09-0-g2883cde
(bootloader) aboot.git: git=MBM-NG-VBA.09-0-gcae5764-dirty
(bootloader) qe: qe 1/1
(bootloader) frp-state: no protection (0)
(bootloader) ro.carrier: metropcs
Well I was hoping to return with a success story, unfortunately that's not the case, I have tried many times on both my Linux and virtualized Windows environment of flashing files from the provided link without luck, as a result of the oem_lock bit being mysteriously reset, (actually upon googling "Failed to initialize partition table" I've found many results, mostly relating to the Moto G4 with others experiencing the same mysterious relocking issue I have)
Since I was getting nowhere very slowly via Fastboot I had started looking elsewhere for a solution and came upon Blankflash (initialized my issuing "fastboot oem blankflash" and operated via the "Qpst" Software squite) which looks very promising except for our stock (and most others actually) firmware files not including the necessary prog_emmc_firehose_8917.mbn files nor the rawprogram.xml files either (
HTML:
https://forum.xda-developers.com/watch-2/development/rom-bootloader-recover-huawei-watch-2-t3624657/post72744084#post72744084
short but alot of useful information on this method... and despite the generic naming of the firehose.mbn files I found they are very device specific I'm currently looking to see if there's a way to extract the information required from the stock Moto Firmware we currently have access to and covert them to the format required my Qfil, but information on flashing through the Qualcomm software is hard to track down.
Through my research I also came across some very interesting exploits that would also solve the flashing issues I'm having https://alephsecurity.com/2018/01/22/qualcomm-edl-2/ but (in my opinion) the methods of carrying out the exploits isn't explained very well, and as I don't understand assembly language am hesitant to experiment with.
My Questions
1. Does anyone have experience flashing through the Qpst suite and be able and willing to help with this?
2. Anyone with enough knowledge of assembly/programming to be able to write code for my device that'll disable the boot locking bit enabling me to flash the already provided Moto Firmware via Fastboot?
Thanks for anyone that takes their time into looking into this for me
tboned82 said:
Well I was hoping to return with a success story, unfortunately that's not the case, I have tried many times on both my Linux and virtualized Windows environment of flashing files from the provided link without luck, as a result of the oem_lock bit being mysteriously reset, (actually upon googling "Failed to initialize partition table" I've found many results, mostly relating to the Moto G4 with others experiencing the same mysterious relocking issue I have)
Since I was getting nowhere very slowly via Fastboot I had started looking elsewhere for a solution and came upon Blankflash (initialized my issuing "fastboot oem blankflash" and operated via the "Qpst" Software squite) which looks very promising except for our stock (and most others actually) firmware files not including the necessary prog_emmc_firehose_8917.mbn files nor the rawprogram.xml files either (
HTML:
https://forum.xda-developers.com/watch-2/development/rom-bootloader-recover-huawei-watch-2-t3624657/post72744084#post72744084
short but alot of useful information on this method... and despite the generic naming of the firehose.mbn files I found they are very device specific I'm currently looking to see if there's a way to extract the information required from the stock Moto Firmware we currently have access to and covert them to the format required my Qfil, but information on flashing through the Qualcomm software is hard to track down.
Through my research I also came across some very interesting exploits that would also solve the flashing issues I'm having https://alephsecurity.com/2018/01/22/qualcomm-edl-2/ but (in my opinion) the methods of carrying out the exploits isn't explained very well, and as I don't understand assembly language am hesitant to experiment with.
My Questions
1. Does anyone have experience flashing through the Qpst suite and be able and willing to help with this?
2. Anyone with enough knowledge of assembly/programming to be able to write code for my device that'll disable the boot locking bit enabling me to flash the already provided Moto Firmware via Fastboot?
Thanks for anyone that takes their time into looking into this for me
Click to expand...
Click to collapse
I'm just getting a notification about this now. Sorry about that. Did you ever unbrick the phone?
To answer your questions, I'm not hip to the Qpst suite. If flashing everything back in Command Prompt on windows didn't work, you may have very well bricked it.
Articul8Madness said:
I'm just getting a notification about this now. Sorry about that. Did you ever unbrick the phone?
To answer your questions, I'm not hip to the Qpst suite. If flashing everything back in Command Prompt on windows didn't work, you may have very well bricked it.
Click to expand...
Click to collapse
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
Mirani said:
i have brick Moto E4 XT 1765
CPU MSM 8917
metropcs
please help me, flash.bat not work i have trying lots of methood but not success
Click to expand...
Click to collapse
I'll try.
Please, in GREAT DETAIL, tell me everything you did to brick it. Step by step. And if you can, tell me the original baseband on the phone. Once I have that I can tell you better how to proceed.
Moto E4 XT 1765 hard brick
Articul8Madness said:
I'll try.
Please, in GREAT DETAIL, tell me everything you did to brick it. Step by step. And if you can, tell me the original baseband on the phone. Once I have that I can tell you better how to proceed.
Click to expand...
Click to collapse
i have unlock boot loader working fine on stock firmware version
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache
Mirani said:
i have unlock boot loader working fine on stock firmware version
NCQ 26.69.46_cid22_subsidy-MPCS_regulatory. but not rooted working charm, after few day i have connected on wifi server suddenly i have received pop up OTA new security patch ready for install i have just installed this patch and my mobile going installing, then erasing after that now not showing anything i have hard brick my own phone with my little negligence.
when i connected to pc just tray icon show HS_USB_Qdloader 9008 and only detected by flash.bat and Qualcomm Snapdragon Flash Tool
plz help me out this headache
Click to expand...
Click to collapse
Let me see if I have this correctly.
You had a stock rom on your phone which you mentioned NCQ.
Then you connected your phone to the wifi.
Then you of your own volition took an update.
This update erased whatever you did trying to get root.
Then your phone bricked.
Now when you attach it to a PC it is showing HS_USB_Qdloader 9008
Is that right?
You need to pull the following firmware and try and flash it...PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml
I've never heard of your firmware. Try that firmware and flash it piece by piece and see if that gets you back working.
Hello, the same problem xt1765 metropcs HS_USB_Qdloader 9008, with that tool will get the firmware? Does not enter fastboot, help
If The phone does not enter fastboot mode you can only fix it by flashin the original stock firmware using SP flash tools and thr correct scatter fileusing format all including formatting the bootloader
TheLastAlphaUK said:
If The phone does not enter fastboot mode you can only fix it by flashin the original stock firmware using SP flash tools and thr correct scatter fileusing format all including formatting the bootloader
Click to expand...
Click to collapse
Again you are answering people with facts about the mediatek version, these ones have the Qualcomm version, therefore, SPflash tool does not apply
My bad cant I use the ADB sideload or update commands to reflash a stock firmware package. ? In kinda in a rush trying to answer all these questions I will look at it when I can sorry
hi,
since last week my phone has been freezing and restarting on its own. i did a hard reset, unlocked the bootloader and flashed a new custom rom but the problem is persistent. im planning to send my phone to htc service center but im afraid that they wont accept the phone due to the unlocked bootloader and custom rom. i tried to flash stock rom but none of the ones i found online are working :crying:
my question is; if i send my phone to htc service center will they accept the phone or not?
(bootloader) kernel: lk
(bootloader) product: htc_ocedugl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: FA73W1700539
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 355167082623511
(bootloader) version-main: 2.19.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF20000
(bootloader) cid: HTC__J15
Hello,
I have a Ultra U, which was stuck in some kind of boot loop / boot screen after a potential update.
I would like to flash a stock rom as the device is and should remain locked and as stock as possible.
Tried already to wipe data/factory reset but without any success.
Where do I find the stock rom? And how to intall it?
Here is the information shown in recovery / fastboot mode:
S-ON
LOCKED
Recovery:
00401/htc_oceuhl
8.0.0/OPRT.170623.032/1031237.1
HTC Download mode:
*** LOCKED ***
*** FUSED (PRODUCTION)***
htc_oceuhl PCT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v24.0.8996.00007_1206_OCE
OS-2.21.401.1
Mar 16 2018,12:21:47(1031237)
HTC TOOLKIT:
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: xxxxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxxxxx
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
all:
finished. total time: 0.049s
Thanks and regards
ultauuser said:
Hello,
I have a Ultra U, which was stuck in some kind of boot loop / boot screen after a potential update.
I would like to flash a stock rom as the device is and should remain locked and as stock as possible.
Tried already to wipe data/factory reset but without any success.
Where do I find the stock rom? And how to intall it?
Here is the information shown in recovery / fastboot mode:
S-ON
LOCKED
Recovery:
00401/htc_oceuhl
8.0.0/OPRT.170623.032/1031237.1
HTC Download mode:
*** LOCKED ***
*** FUSED (PRODUCTION)***
htc_oceuhl PCT S-ON
LK-1.0.0.0000
[email protected]
OpenDSP-v24.0.8996.00007_1206_OCE
OS-2.21.401.1
Mar 16 2018,12:21:47(1031237)
HTC TOOLKIT:
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: xxxxxx
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: xxxxxxx
(bootloader) version-main: 2.21.401.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__034
all:
finished. total time: 0.049s
Thanks and regards
Click to expand...
Click to collapse
Do you have found an OTA.zip file?
I need it too, I have the same problem as you...
david133
Hi,
if you're able to access the phone via fastboot, you can try the following method:
https://forum.xda-developers.com/u-ultra/help/howto-unbrick-ultra-t3891033
Greetings
Try this one:
2PZFIMG_OCEAN_NOT[email protected]80307_63.34_release_522808_signed_2_4 .zip
Rename the file to "2PZFIMG.zip" and place it in root of sdcard. Boot into download mode and confirm flash with volume+ button
(bootloader) kernel: lk
(bootloader) product: htc_oceuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1578400000
(bootloader) serialno: ****
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: ****
(bootloader) version-main: 2.27.710.1
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PZF10000
(bootloader) cid: HTC__039
I'm at my wits end here, I've been trying to find an RUU or a firmware version or anything to try and fix the bootloop my Ultra U is in after it had a flat battery. I have factory reset it as well as cleared cache in the recovery menu, but it still freezes and reboots a few minutes into loading the OS. I am unable to proceed beyond the initial setup. Telstra won't touch it because its warranty expired a month ago. I've exhausted almost every option beside flashing the device in an attempt to maybe fix a corrupt file
I don't care about the data on it, or if I have to root it or anything. I just want to get my device back into some form of working order as I can't afford to pay for it to be repaired or replaced.
Please XDA, tell me there's some light at the end of the tunnel