Hello - need help:
My Phone has HTC Bootloader - but says:
*** UNLOCKED ***
htc_ocedug1 PVT S-ON
LK-1.0.0000
[email protected]
OpenDSP-UNKNOW
OS-1.62.400.1
May 11 2017, 15:56:13(925380)
The problem is that the phone always downloads the actual HTC systemupdate - starts it and then craches after 26%. So i decided to re-flash the phone with the stock rom. So i gut the following stock rom file where i guess it's teh rightz one: 2PZFIMG_OCEAN_NOTE[email protected]70502_53.34_release_503372_signed_2_4.zip
The size of the files is 1.87 GB. I guess it's the right file. Then i copied the file into the ADB directory of my pc and renamed it to "HTCROM.zip"
And that what happens:
PS C:\adb> adb reboot download
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
PS C:\adb> fastboot oem rebootRUU
...
OKAY [ 0.000s]
finished. total time: 0.000s
PS C:\adb> fastboot flash zip HTCROM.zip
target reported max download size of 1579200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1960968042 is not a multiple of the block size 4096
sending sparse 'zip' (0 KB)...
error: write_sparse_skip_chunk: don't care size 1960968042 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1960968042 is not a multiple of the block size 4096
OKAY [ 1.009s]
writing 'zip'...
(bootloader) HOSD CL#925380
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_r
(bootloader) 6Nf2a
(bootloader) ERR preload central directory info failed (EOCD).
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap with original ret: 0)
finished. total time: 2.072s
What's wrong???? How do i get ma HTC U ULTRA back to 100% stock - so that it makes the Standard HTC Updates?
Thanks for help!!!!
Did you try the another method?
1. Rename zip to 2PZFIMG.zip
2. Place it on the root of the micro sd card.
3. Reboot the phone into bootloader or download mode and it'll automatically ask to flash the ROM.
razarahil said:
Did you try the another method?
1. Rename zip to 2PZFIMG.zip
2. Place it on the root of the micro sd card.
3. Reboot the phone into bootloader or download mode and it'll automatically ask to flash the ROM.
Click to expand...
Click to collapse
Doing this results in: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
But the OS Version is correct. The problem may be that the bootloader on my phone is unlooked. I also need to relook the bootloader - but i was thinking that flashing will do the job
Please help me to get back to 100% stock for my HTC Ultra
My Phone is a HTC U Ultra U1-u 2PZF200. The only thing i did was going to dev. mode and then also unlooked the bootloader with HTC web page.
I also have the red warning "this build is for ...." when i boot the phone.
I think you're flashing the wrong build, search the build which is compatible with your cid number.
razarahil said:
I think you're flashing the wrong build, search the build which is compatible with your cid number.
Click to expand...
Click to collapse
That's possible because my phone has a strange CID:
GSM version: [email protected]_53.34
Android version: 7.0
Model name: HTC U Ultra
Manufacturer: HTC
Device code: htc_ocedugl
Product name: ocedugl_00400
Product version: 1.62.400.1
Bootloader version: 1.0.0.0000
Cid: HTC__060
Ram: 4GB
Protected: true
Build line: OceanNoteDUGL_SEA_IND_N70_CRC_Sense80GP_Stable
Build changelist: 925380
Build characteristics: default
Build UTC: 1494487447
Build date: 四 5月 11 15:24:07 CST 2017
Build descriptor: 1.62.400.1 8.0_g CL925380 release-keys
Build display id: NRD90M release-keys
Build project: OCEAN_NOTE_DUGL_N70_SENSE80GP:503372
CID HTC_060 is somewhere India I think. Where can I find the correct Firmware? Or does it makes sense to change the CID to supercid? If I do so does the phone makes in the future automatic system updates?
HTC-Maus said:
That's possible because my phone has a strange CID:
GSM version: [email protected]_53.34
Android version: 7.0
Model name: HTC U Ultra
Manufacturer: HTC
Device code: htc_ocedugl
Product name: ocedugl_00400
Product version: 1.62.400.1
Bootloader version: 1.0.0.0000
Cid: HTC__060
Ram: 4GB
Protected: true
Build line: OceanNoteDUGL_SEA_IND_N70_CRC_Sense80GP_Stable
Build changelist: 925380
Build characteristics: default
Build UTC: 1494487447
Build date: 四 5月 11 15:24:07 CST 2017
Build descriptor: 1.62.400.1 8.0_g CL925380 release-keys
Build display id: NRD90M release-keys
Build project: OCEAN_NOTE_DUGL_N70_SENSE80GP:503372
CID HTC_060 is somewhere India I think. Where can I find the correct Firmware? Or does it makes sense to change the CID to supercid? If I do so does the phone makes in the future automatic system updates?
Click to expand...
Click to collapse
Yes CID 60 is for the Indian version. Try to do it by relocking the bootloader.
razarahil said:
Yes CID 60 is for the Indian version. Try to do it by relocking the bootloader.
Click to expand...
Click to collapse
Relooking the bootloader does not work. I tried:
fastboot oem look
but the result is "Command Error"
Even chimera tool is not be able to relook the bootloader...
Does anybody know where i can get the correct flash to go back to 100% stock? I think this is may the best way.
HTC-Maus said:
Doing this results in: 19 RU_MAIN_VER_FAIL os-version in android-info missing or i
But the OS Version is correct. The problem may be that the bootloader on my phone is unlooked. I also need to relook the bootloader - but i was thinking that flashing will do the job
Please help me to get back to 100% stock for my HTC Ultra
My Phone is a HTC U Ultra U1-u 2PZF200. The only thing i did was going to dev. mode and then also unlooked the bootloader with HTC web page.
I also have the red warning "this build is for ...." when i boot the phone.
Click to expand...
Click to collapse
Mate my bootloader was unlocked from HTC Dev, when I put the zip file in the root of my SD card. I didn't get any errors and successfully reverted back to stock. I reckon the issue might be the zip file you are using. Download and flash this:
https://www.androidfilehost.com/?fid=817550096634794461
It worked for my dual sim HTC U Ultra, OS was same as yours 1.62.400.1
nealzXincredible said:
Mate my bootloader was unlocked from HTC Dev, when I put the zip file in the root of my SD card. I didn't get any errors and successfully reverted back to stock. I reckon the issue might be the zip file you are using. Download and flash this:
https://www.androidfilehost.com/?fid=817550096634794461
It worked for my dual sim HTC U Ultra, OS was same as yours 1.62.400.1
Click to expand...
Click to collapse
Thank you!! This worked out for me - now i'm back to stock - but the bootloader is still unlooked. I need to get the bootloader "Locked" (and not Re-locked). I was thinking that this works with going back to stock - but did'nt. How can i get it locked?
HTC-Maus said:
Thank you!! This worked out for me - now i'm back to stock - but the bootloader is still unlooked. I need to get the bootloader "Locked" (and not Re-locked). I was thinking that this works with going back to stock - but did'nt. How can i get it locked?
Click to expand...
Click to collapse
Why do you want to get the bootloader "Locked?" If you are worried about OTA's don't worry, since flashing the stock Rom I have received two OTA updates on my phone and my bootloader is still unlocked.
For any other purposes if you want to relock the U Ultra bootloader, you can do so by running following fastboot command: fastboot oem lock. This will format all the data on your phone. You must realize that since you have already unlocked your bootloader once, the only way to get it locked again is by re-locking it.
Related
After searching around for a bit trying different (known) exploits, I've come to the conclusion that my phone's bootloader cannot be unlocked. If you know otherwise, please link me to the thread. My original goal was to install CyanogenMod, but that requires an unlocked bootloader- again, apparently not possible. Plan B is now to use Safestrap and install a custom ROM that way.
I've successfully rooted it, but that's it. Currently running:
Android Version: 4.1.2,
System Version: 98.30.1
Build Number: 9.8.1Q-94-1
Build Date: Thu Sep 26 12:24:41 CDT 2013
I'm looking for a like-CyanogenMod ROM that will work with Safestrap/locked bootloader.
Any help?
What is your kernel? That android version should be early enough to unlock your boot loader.
Sent from my HTC Vivid 4G using XDA Free mobile app
projectisaac said:
What is your kernel? That android version should be early enough to unlock your boot loader.
Sent from my HTC Vivid 4G using XDA Free mobile app
Click to expand...
Click to collapse
Kernel Version: 3.0.31-gef7deb8 [email protected] #1
SMP PREEMPT Thu Sep 26 12:38:22 CDT 2013
I've tried Motopocalypse several times- here's the output. I put the error in bold.
[email protected]:motopocalypse% ./run.sh
[*] Press enter to unlock your bootloader...
[*]
[*] Waiting for device...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[*] Device found.
[*] Pushing unlock tool...
4021 KB/s (38280 bytes in 0.009s)
[*] Unlocking phone...
[+] TrustZone target address resolved to 2a020a02
[-] TrustZone write failed: -11.
[*] Cleaning up...
[*] Unlocking complete. Rebooting into bootloader mode.
[*] Press enter once the phone has rebooted into bootloader mode.
[*] Displaying bootloader variables:
(bootloader) version-bootloader: 109B(*)
(bootloader) product: smq
(bootloader) secure: yes
(bootloader) mid: 0058
(bootloader) version: 0.5
(bootloader) serialno: ##########
(bootloader) qe: qe 1/1
(bootloader) unlocked: no
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 31457280
(bootloader) emmc-size: 8GB
(bootloader) reason: Flash Failure
(bootloader) revision-hardware: 0x82A0
(bootloader) cpu: MSM8960 CS
(bootloader) uid: C4693B0A02000300000000000000
(bootloader) cid: 0x02
all:
finished. total time: 0.019s
[*] Press enter to reboot and exit.
resuming boot...
OKAY [ 0.005s]
finished. total time: 0.005s
[email protected]:motopocalypse%
Also, I came across this link with someone in what appears the exact same boat- http://forum.xda-developers.com/showthread.php?t=2670263
ProoN said:
After searching around for a bit trying different (known) exploits, I've come to the conclusion that my phone's bootloader cannot be unlocked. If you know otherwise, please link me to the thread. My original goal was to install CyanogenMod, but that requires an unlocked bootloader- again, apparently not possible. Plan B is now to use Safestrap and install a custom ROM that way.
I've successfully rooted it, but that's it. Currently running:
Android Version: 4.1.2,
System Version: 98.30.1
Build Number: 9.8.1Q-94-1
Build Date: Thu Sep 26 12:24:41 CDT 2013
I'm looking for a like-CyanogenMod ROM that will work with Safestrap/locked bootloader.
Any help?
Click to expand...
Click to collapse
Upgrade to 4.4.2 KDA20.62-10.1 with RSD Lite, then root and unlock your bootloader.
Go here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
ATTACK said:
Upgrade to 4.4.2 KDA20.62-10.1 with RSD Lite, then root and unlock your bootloader.
Go here > http://forum.xda-developers.com/droid-razr-m/general/guide-faq-how-to-root-boot-unlock-t2869432
Click to expand...
Click to collapse
This phone is currently in an AP Fastboot loop-thing. I'm able to do the up/down/power combo then boot up normally, but otherwise any time it restarts, it always goes into Fastboot. It says: Fastboot Reason: "Flash Failure"
Also, booting into "Recovery" just brings up the Droid icon with a red exclamation. Should I figure these out before upgrading the firmware and continuing to unlock the bootloader? Or will it even matter?
ProoN said:
This phone is currently in an AP Fastboot loop-thing. I'm able to do the up/down/power combo then boot up normally, but otherwise any time it restarts, it always goes into Fastboot. It says: Fastboot Reason: "Flash Failure"
Also, booting into "Recovery" just brings up the Droid icon with a red exclamation. Should I figure these out before upgrading the firmware and continuing to unlock the bootloader? Or will it even matter?
Click to expand...
Click to collapse
It would be good to know either way, but it shouldn't stop you from continuing to upgrade and unlocking the bootloader.
----------------------------------------------------------------------------------------------------------------------
1. For the fastboot loop go [HERE] and follow #8.
2. The "dead droid" screen is recovery. > https://motorola-global-portal.custhelp.com/app/answers/prod_answer_detail/a_id/88933/p/30,6720,8577
Code:
From the Android system recovery screen, press and hold the VOL UP key for 10-15 seconds. While still holding the VOL UP key tap and release the POWER key.
1. For the fastboot loop go [HERE] and follow #8.
I've tried this several times and it still boots into AP Fastboot Flash Mode, both on OSX and a Windows system. Would flashing the stock ROM remedy?
ProoN said:
. Would flashing the stock ROM remedy?
Click to expand...
Click to collapse
Not sure. What happen to cause the fastboot boot loop?
ATTACK said:
Not sure. What happen to cause the fastboot boot loop?
Click to expand...
Click to collapse
I'm not sure, honestly. It seems like it happened after I installed Safestrap. But I managed to fix it by flashing a stock image back onto it.
So now, I'm using RSD Lite 6.1.5 on Windows, trying to upgrade the firmware to 4.4.2. I had a flash failure alert after decompressing, "getvar" something or other. Edited the xml and removed that line, now it seems to be stuck at '2/20 flash partition "gpt.bin"'
Just an update so this can be "Solved" even though it went way off topic. I successfully flashed it to 4.4.2.
That gpt.bin error seemed to be RSD specific. I ended up manually flashing each file one by one. Had a hiccup at the "NON-HLOS.bin" file (modem), something about the size. Came across a thread suggesting to use a different version of fastboot, so I did (the fastboot.osx version). Restarted the entire process, grimaced when I got to the modem bit, but it ended up working. It went through the sending/writing process of system.img for about 10 minutes, repeating the same message for some reason (100ish times). But I just let it go through. At this moment-
Android Version: 4.4.2
Kernel Version: [email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
I'd just like to apologize for being a n00b in this area. Like most, the biggest worry was bricking the phone so I was kind of hesitant to do anything on my own, even though I read through several tutorials repeatedly.
Much appreciation though, will be looking into unlocking it now that I've gotten this far.
Unlocking it is the easy part... Root with towel root then find motoapokalypse.apk and run it... Then install flashify and flash the latest twrp.
Sent from my Amazon Tate using XDA Free mobile app
ProoN said:
Just an update so this can be "Solved" even though it went way off topic. I successfully flashed it to 4.4.2.
That gpt.bin error seemed to be RSD specific. I ended up manually flashing each file one by one. Had a hiccup at the "NON-HLOS.bin" file (modem), something about the size. Came across a thread suggesting to use a different version of fastboot, so I did (the fastboot.osx version). Restarted the entire process, grimaced when I got to the modem bit, but it ended up working. It went through the sending/writing process of system.img for about 10 minutes, repeating the same message for some reason (100ish times). But I just let it go through. At this moment-
Android Version: 4.4.2
Kernel Version: [email protected] #1
Fri May 2 00:30:06 PDT 2014
Build Number: KDA20.62-10.1
I'd just like to apologize for being a n00b in this area. Like most, the biggest worry was bricking the phone so I was kind of hesitant to do anything on my own, even though I read through several tutorials repeatedly.
Much appreciation though, will be looking into unlocking it now that I've gotten this far.
Click to expand...
Click to collapse
AWESOME!:good: Glad you got it all worked out. Now just root, bl unlock and your good to go.
Hi,
I am looking for free RUU 2.18.401.10 for the HTC M9 HIMAR UHL.
My CID is HTC__034 currently running 2.18.401.10 Firmware but modified system not being able to use OTA files Backup of system and boot before rooting didn't help as restoring still shows modified being unable to flash OTA manually - suckz badly...
Searching the internet for days only returns files for
1. Asian Version
h t t p s : / / w w w . androidfilehost.com/?fid=24459283995312106
h t t p s : / / w w w . androidfilehost.com/?fid=24459283995312105
2. TWRP 3.0.0.1
h t t p s : / / w w w . androidfilehost.com/?fid=24421527759889622
3. PAID Versions on e.g. ir-file host...;-(
h t t p : / / forum.a2phone.ir/download-center-new-firmware-files/574-htc-himar_ml_uhl_m60_sense70gp_htc_europe_2-18-401-10-firmware.html
h t t p s : / / w w w . ir-file.com/portal/index.php?dir=Firmware/HTC/HTC_Android/HIAUR_ML_TUHL/ (2.18.401.8)
I could offer for now for anyone who needs it
1. Full OTA 2.18.401.8 --> 2.18.401.10
2. Signed Firmware 2.18.401.8 --> 2.18.401.10 (out of OTA above)
Any help highly appreciated.
Thanks!
Michael
Huh. Can you provide a little more by the way of identifying information on your phone? I can't find anything about the CID you've mentioned. Can you provide your MID or your SKU?
Hi,
corrected some typos in above post especially regarding the Firmwareversion
Corrected Data:
M9 Prime Camera Edition - Released in Germany end of April 2016 --> I am not sure about the correct abbreviation as everyojne in this forum refers to this mobile differently. Product ID is htc_himaruhl - with an "R" in it
Firmware: 2.18.401.10 --> came with buggy 2.18.401.8 originally
Cidnum: HTC__034 --> unbranded "Europe" Version
In particular I am looking for the following
1. RUU "2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.18 .401.10..."
2. Alternatively a unmodified System and Boot Dump of Version 2.18.401.8 OR 2.18.401.10 would be sufficient as well
If other data needed I will be able to provide it 2nite - I am currently at work.
Thanks for your help,
Michael
Any one here
1. with access to the above mentioned RUU?
2. or could provide me with a clean and unmodified System + Boot Backup 2.18.401.8 or 2.18.401.10 for M9 Prime Camera Edition --> Product ID HIMAR
*bump*
Still no one? ;-(
kernel: lk
product: htc_himaruhl
version: 1.0
imei: XXXXXXXXXXXX
version-main: 2.18.401.10
boot-mode: download
version-baseband: READ version-baseband ERROR
version-bootloader: 1.01.0000
mid: 2PRG10000
cid: HTC__034
Sadly, you're stuck. Pay for S-OFF (fairly surefire) or for access to the RUU collection sites (a bit iffy).
Same problem here... tried to root and always stuck at starting twrp.
Did'nt found RUU or even the stock recovery.
So I have to wait until anyone is helping because I have no idea about restore or root that crab phone....
Edit:
After I flashed TWRP my DATA-partition is cleaned and could not mount anymore. So my System is totally damaged ... now I formated the data and it could mount again. But I have no RUU to rebuild system again.
micha279 said:
*bump*
Still no one? ;-(
kernel: lk
product: htc_himaruhl
version: 1.0
imei: XXXXXXXXXXXX
version-main: 2.18.401.10
boot-mode: download
version-baseband: READ version-baseband ERROR
version-bootloader: 1.01.0000
mid: 2PRG10000
cid: HTC__034
Click to expand...
Click to collapse
Rooting is no problem with stock firmware for that phone. Just flash supersu systemless 2.71 BETA, works like a charm
My Problem is More related to a modified system partition after xposed install - which also works flawlessly! I have performed backups right after unpacking as I am not doing that the first time, had a m7 before which broke after dropping it the 30th time - RIP my m7 (
Restoring the initial backups does not help to get back to unmodified state, therefore I need a clean backup or RUU...
So far: No luck...;-(
micha279 said:
Rooting is no problem with stock firmware for that phone. Just flash supersu systemless 2.71 BETA, works like a charm
My Problem is More related to a modified system partition after xposed install - which also works flawlessly! I have performed backups right after unpacking as I am not doing that the first time, had a m7 before which broke after dropping it the 30th time - RIP my m7 (
Restoring the initial backups does not help to get back to unmodified state, therefore I need a clean backup or RUU...
So far: No luck...;-(
Click to expand...
Click to collapse
Still looking...anyone?
Sensajcon was so kind and shared his files with me, unfortunately the 2PRGIMG_HIMAR... is broken...grrr
@sensajcon can u share this file?
2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.18 .401.10
Riski3Run said:
@sensajcon can u share this file?
2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.18 .401.10
Click to expand...
Click to collapse
Sorry, but I tried to upload the files several times. Don't know why, but its broken anytime.
You cout got it from here:
h t t p : / / forum.a2phone.ir/download-center-new-firmware-files/574-htc-himar_ml_uhl_m60_sense70gp_htc_europe_2-18-401-10-firmware.html
Any news here? Can somebody share the related file please?
Yes.
Here u go:
https://rapidu.net/5015736911/2PRGI...U-W.T-_release_477006_combined_signed_2_4.zip
Great job. Thanks a lot.
Let me know how it works.
Having spent HOURS over HOURS now to flash RUU correctly, I thought I may share what resulted with success for me:
1. Download RUU: https://rapidu.net/5015736911/2PRGI...U-W.T-_release_477006_combined_signed_2_4.zip
2. Download HTC fastboot: https://www.androidfilehost.com/?fid=96042739161891970
3. Reboot to Download Mode
4. Optional: Set Phone to "Relocked" if you like with "fastboot oem lock"
5. fastboot oem rebootRUU
6. Flash RUU.zip with "htc_fastboot flash zip RUUZIPName.zip"
7. Enjoy
Placing ruu.zip on my SDcard having it name "2PRGIMG.zip", trying to install in Stock Recovery by selecting it from a FAT32 formatted External SDcard, etc. pp - ALL did NOT work!
Have fun
How To: Restore to Official ROM
Device: HIMAR_ML_UHL
Main Version: 2.18.401.10
MID: 2PRG10000 | CID: HTC__001, HTC__J15, HTC__034
Prepare
adb & fastboot for HTC devices
HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.18.401.10_Images.zip (boot, recovery, system)
Firmware 2.18.401.10 (decrypted, S-OFF required)
Instruction
Unlock Bootloader
Reboot device to download mode
adb reboot download
fastboot oem reboot-download
Flash boot, recovery, system images
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Flash firmware (S-OFF required)
fastboot oem rebootRUU
fastboot flash zip <firmware.zip>
fastboot oem reboot-download
Reboot
fastboot reboot
Other
RUU:
2PRGIMG_HIMAR_ML_UHL_M60_SENSE70GP_HTC_Europe_2.18.401.10_Radio_1.1550V70.2508.0304_HU[W.T]_release_477006_combined_signed_2_4.zip (thanks @Riski3Run)
TWRP: https://github.com/sabpprook/android_device_htc_himar
twrp-3.0.0-1-himar.img
twrp-3.0.2-0-himar.img
Thanks @sabpprook - but why so complicated restoring partition by partition if you link the signed RUU as well? I mean ok: You won't wipe the userdata partition - fair point. But in the end all you will get is a "dirty flashed" ROM. If you want to do so you should also consider wiping cache partition.
But in my case for example the above did not work as my partition layout seemed to be "corrupt" and also security partitions were messed up. After lock, flashing full RUU and new unlock everything worked like a charm again Most important thing I noted was that I had to use htc_fastboot for M9 which I couldn't find on HTCs official site as they only offer a very old version to download Standard fastboot from mini-sdk in latest version also will fail as it is not able to get pass HTCs size limitation for RUU...
PS: If you like I could provide you with signed firmware 2.18.401.10 as well so that S-OFF is not needed anymore. Or just extract it from the OTA I have sent you earlier - no decrypt required there
Update 2.32.401.1 is available now
HIMAR_ML_UHL it is HTC One M9 Prime Camera Edition ?
A couple days ago, I found this phone (a T-Mobile myTouch 3G with a 3.5mm headphone jack, apparently version 1.2) running CM(5? 6? honestly don't remember) and decided to revert it back to stock. Worst mistake of my life.
Throughout getting back to stock, I have (a) unlocked the phone on HTCDev and downloaded their hboot version, (b) wiped system through fastboot on RUU, (c) get goldcard and flash with a stock cupcake image I found on the forums and (d) flash that image with fastboot on RUU mode. None have worked and I'm stuck.
I extracted rom.zip from (number 57) "2.10.531.4 T-Mobile USA DRD35" on the official list of RUUs. With my phone in RUU mode, I did the following and got the output:
Code:
> sudo ~me/bin/android-sdk-linux/platform-tools/fastboot flash zip rom.zip
sending 'zip' (62177 KB)...
OKAY [ 13.218s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
FAILED (remote: 43 main version check fail)
finished. total time: 33.892s
After further googling, I found that meant that the main version was higher than what was getting flashed. I was pretty confused as I couldn't find a higher version, but I stand corrected, as my phone apparently has it:
Code:
> sudo ~me/bin/android-sdk-linux/platform-tools/fastboot getvar version-main
version-main: 3.57.0.0
finished. total time: 0.001s
I have no idea why it's like that (perhaps the HTC hboot update gave it that, or perhaps whenever I installed CM on it I found that), nor what main-version is.
At the moment, my phone shows this at the top in RUU mode:
Code:
*** RELOCKED ***
SAPPHIRE PVT 32A SHIP S-ON G
HBOOT-1.33.0014 (SAPP31000)
CPLD-13
RADIO-2.22.20.25
Jan 31 2012.14:43:52
Does anyone have advice on how I might get out of this hole I have created for myself? If the phone is bricked, that's meh, but I'd really like to get this working. I do understand that this phone is really old and that most people don't have it, so any help is appreciated. I'm using Ubuntu, but can get my hands on a Windows or OS X machine if needed.
Well, I think you could try making a gold card, flashing an older SPH via HBOOT, then using the RUU to update once again. Or try making an SPH out of your rom.zip, but I have no idea how that works.
By the way, how'd you get fastboot to work? I can't seem to get my drivers working (see my thread in this subsection), although it may be because I'm using Windows XP and you're using some sort of Linux/Unix.
I decided to return my Sprint variant. So i needed to s-on and lock the bootloader. Problem is, now I have a 1 sec bootloop. Here's what I did. No idea how to fix the problem now.
Here's what I did in order to get the phone back to 100% stock to return it.
Changed the CID (incorrectly) to spsc_001 instead of spcs_001 but iddn't notice that.
Managed to get s-on but couldn’t get bootloader locked again.
reinstalled twrp and SU
booted up
installed sunshine and successfully s-off'd & locked
rebooted to download mode
Did a s-on using fastboot oem writesecureflag 3
rebooted and got a 1 sec bootloop
booted back into download mode and tried to factory reset via fastboot but can’t write the partition
tried to flash twrp, but got a security warning BL-unlocked
Now I'm stuck in a super short .5 second bootloop and can’t access stock recovery.
I try to install the ruu.exe and I get a Customer ID error. I try to install RUU.zip and I get a load_file: could not allocate -2146013644 bytes (which I assume means the partition is full but I can't even erase the userdata.) I also get a Security checking failed GT_CONNECT_FAIL on the download mode screen. I'm totally clueless as to how to get out of this situation. Anyone been here before or knows how to deal with this?
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
honestly, I think you're screwed...I don't know how you'll be able to fix this w/o being able to boot up, can't unlock bootloader, can't use fastboot to flash anything, can't flash RUU...somehow u need to get your CID back to SPCS_001...u may just have to return it in that condition & act ignorant.
any ideas @dottat @Captain_Throwback
vijn said:
Now, my vars are:
(bootloader) kernel: lk
(bootloader) product: htc_pmewhl
(bootloader) version: 1.0
(bootloader) max-download-size: 1579200000
(bootloader) serialno: HT64xxxxx6
(bootloader) current-slot:
(bootloader) imei: 99xxxxx1
(bootloader) version-main: 2.42.651.63
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PS640000
(bootloader) cid: spsc_001
all:
finished. total time: 0.009s
Click to expand...
Click to collapse
OMJ said:
u failed to mention that you changed the CID at some point & when you changed it back, u set it wrong...
Click to expand...
Click to collapse
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
vijn said:
You're right, but I had created this post before you guys pointed that out to me in the other thread. So, ya for the record i set the CID as spsc_001 instead of spcs_001 and then locked the bootloader. Great job on my part huh? Anyway, I was afraid you were going to say that I was screwed. I have never made a mistake like this before. So stupid, every letter counts. You'd think I'd have learnt that by now. I'm just hoping there's some really obscure and little-known fix for this that some xda angel will send my way. Hehe. Anyway, thanks for the follow-up OMJ.
Click to expand...
Click to collapse
Well did you attempt to see if HTC dev would give you an unlock token at least?
Sent from my SM-G955U using Tapatalk
---------- Post added at 11:29 PM ---------- Previous post was at 11:28 PM ----------
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
You might be able manually flash the ruu partitions one by one as well. Have you tried that?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-G955U using Tapatalk
dottat said:
Well did you attempt to see if HTC dev would give you an unlock token at least?
Click to expand...
Click to collapse
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
vijn said:
Well, I had already unlocked the phone, rooted, installed other ROMs. When I couldn't unlock the GSM bands, I decided to return the phone so I tried to set the phone back to stock Sprint ROM. I did everything necessary except I put in the wrong CID before relocking the bootloader. So, yes, I had been provided the unlock code by HTC dev. The problem is that I now have a locked bootloader with an incorrect CID, which is why flashing RUUs isn't working.
I don't know if I can flash the RUU partitions with a locked bootloader or if that'll work with an incorrect CID but I'll try anything. Just not sure how to go about doing tht. I'd appreciate any help you can provide. Thanks for the recommendation.
Click to expand...
Click to collapse
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
dottat said:
Attempt to get a new fresh unlock token and tell me what HTC dev says?
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
vijn said:
Actually I had tried that since this bootloop issue came up and was given a new .bin file without any problems. The problem is when i tried to flash the .bin file i got this:
sending 'unlocktoken' (0 KB)...
OKAY [ 1.024s]
writing 'unlocktoken'...
(bootloader) flash unlocktoken
(bootloader) [KillSwitch] : /dev/block/bootdevice/by-name/frp
(bootloader) [KillSwitch] Last Byte is 0X00, disable unlock
(bootloader) [KillSwitch] oem unlock Turn Off!
Click to expand...
Click to collapse
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
OMJ said:
try this, grab the stock boot.img from the firmware zip: https://www.androidfilehost.com/?fid=745425885120723715
copy the boot.img into your sdktools folder
boot into download mode & try to manually flash it
fastboot flash boot boot.img
if that doesn't work, then try this
download the signed firmware: https://www.androidfilehost.com/?fid=745425885120723717
then try one or both of the flashing methods (although I suspect it wont work due to bad CID):
Flash Firmware via download mode (requires micro sd card)....
-rename firmware to 2PS6IMG.zip
-copy 2PS6IMG.zip to ext_sd card
-boot into download mode
-it will scan your ext_sd card, then ask if you want to start the update
-press volume up & let it do it's thing...
Flash Firmware via fastboot, no ext sd card needed...
-rename firmware to firmware.zip
-copy firmware.zip to your adb/fastboot/sdk folder
-boot into download mode
-plug in usb
-type fastboot oem rebootRUU
-when u see the black screen w/ HTC, type fastboot flash zip firmware.zip
-when it's done, type fastboot reboot
Click to expand...
Click to collapse
Ok well, I tried these.
The sd card method failed due to the CID mismatch.
The stock boot.img from the firmware zip method gave the following:
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
The Firmware flash via fastboot, no ext sd card needed gave this:
sending 'zip' (66180 KB)...
OKAY [ 3.269s]
writing 'zip'...
(bootloader) HOSD CL#857212
(bootloader) ERR CID not matched
(bootloader) ERR [SD_UPDATE_ERR] CID NOT ALLOWED
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 7
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 7
(bootloader) [email protected]
FAILED (remote: 7 RU_CID_FAIL cid in android-info mismatched )
finished. total time: 6.456s
I'm screwed aren't I?
dottat said:
Ok. So your only hope would be to get the ruu files extracted and to manually flash each partition by name. Get it to boot and enable oem unlock. Then flash new token and flash twrp and root and S-off via sunshine. Then fix the cid and do the rest the correct way.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
vijn said:
OK, this is slightly above my pay-grade. While I've read up on it it always seemed too complicated to try in the past, but this is as good a time as any to learn. Any way you can point me in the right direction on this? Not sure how to do this. I assume I should use the original sprint RUU.zip?
Click to expand...
Click to collapse
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
dottat said:
Use the original zip and the instructions/tools provided here (https://forum.xda-developers.com/chef-central/android/tool-universal-htc-ruu-rom-decryption-t3382928) to extract your RUU into the basic partition files. Then flash each one using fastboot by name (eg fastboot flash system system_1.img etc)
Click to expand...
Click to collapse
Ok, will try that. You wouldn't happen to know where I can find the zip would you? I always used the exe cause that's what was on the htc site. Not sure where the actul RUU.zip file can be found. I assume I can use the one found here: https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257
And dottat, OMJ, thanks a lot for your help. It's people like you who make this community what it is.
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
vijn said:
Hey OMJ,
I grabbed one of your RUU.zip files from your repository on xda ( https://forum.xda-developers.com/sprint-htc-10/development/ruu-sprint-htc-10-1-24-651-3-t3379257 ). The zip files, when extracted, turn into like 25 zips. When I extract 0.zip (in order to extract the entire array) I get a file corrupt errors for a few of the files. Am I missing something? I don't think the files are actually corrupt but this is a recurring error I've gotten on a number of different .zip files that have the string of multiple zips within them. Got any ideas?
Click to expand...
Click to collapse
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
OMJ said:
u download the 2PS6IMG.zip? If so, u can't extract, it's encrypted. You would need to decrypt using the tool that dottat linked u
BUT, don't waste your time, aint gonna work, u already tried manually flashing the boot.img & u got the failed, s-on error
to confirm, from download mode, u used this cmd? fastboot flash boot boot.img if so, I'm fresh out of ideas....
sending 'boot' (47977 KB)...
OKAY [ 1.606s]
writing 'boot'...
FAILED (remote: cannot flash this partition in s-on state)
finished. total time: 1.656s
Click to expand...
Click to collapse
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
vijn said:
Ya, that's what I'd done, but strangely this time I got a different error:
sending 'boot' (47977 KB)...
OKAY [ 2.529s]
writing 'boot'...
(bootloader) HOSD CL#857212
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
finished. total time: 3.551s
Click to expand...
Click to collapse
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
OMJ said:
odd...u can certainly try to flash the system.img but it will probably give the same error...I can the complete single system.img if u want me to upload or u can use the decrypt tool to decrypt the ruu & flash the individual system imgs
Click to expand...
Click to collapse
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
vijn said:
Would you mind sending the system file? I haven't managed to get the decrypt tool working yet.
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=745425885120734364
Saw your post while looking for an sim unlock for my Japanese HTC 10.
Couldn't resist reading more about your problem tho.
First idea but quite dangerous if done incorrectly..
Try and see if you can change the cid in the ruu.exe with a HEX editor?
If that doesn't work, next try and change the cid of the ruu. zip.
Might be a long shot, but if the files cid's aren't encrypted it might work!
I have hours and lots of GB of bandwidth wasted trying every ROM edition i found about "Moto E4", when i try to install it says "...this package is for device xxxxx, this device is perry"
Nothing worked so far also i didn't create a backup and i can't even find how to turn it back as it was
Can someone please help me maybe there's something i can do or any version i haven't seen?
I'm very new i don't have much knowledge about androids but i learn fast and i have huge knowledge on linux/windows.
daraw said:
I have hours and lots of GB of bandwidth wasted trying every ROM edition i found about "Moto E4", when i try to install it says "...this package is for device xxxxx, this device is perry"
Nothing worked so far also i didn't create a backup and i can't even find how to turn it back as it was
Can someone please help me maybe there's something i can do or any version i haven't seen?
I'm very new i don't have much knowledge about androids but i learn fast and i have huge knowledge on linux/windows.
Click to expand...
Click to collapse
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Official firmware
https://mirrors.lolinet.com/firmware/moto
Or use LMSA'S flash/rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
sd_shadow said:
run
Code:
fastboot getvar all
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
Official firmware
https://mirrors.lolinet.com/firmware/moto
Or use LMSA'S flash/rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Code:
fastboot getvar all
(bootloader) serialno: ZY32298X8N
(bootloader) off-mode-charge: 1
(bootloader) warranty: no
(bootloader) unlocked: yes
(bootloader) efuse: yes
(bootloader) secure: no
(bootloader) kernel: lk
(bootloader) product: WOODS
(bootloader) hwid: 31
(bootloader) version-preloader: 0.1.00
(bootloader) version: 0.5
Thanks to you i found ROM at https://mirrors.lolinet.com/firmware/moto/woods/official/oem/
since my Moto E4 says Woods from fast boot, and on screen reports SKU : XT1761
i've download xt1761_fastboot_woods_oem_user_7.1.1_NMA26.42-11-3_3_release-keys_oem_EMEA
this zip also includes a "recovery.img" is that the stock recovery? i tried to boot it with fastboot but i got this error
Code:
C:\Users\DOPE-PC\Desktop\xt1761_fastboot_woods_oem_user_7.1.1_NMA26.42-11-3_3_release-keys_oem_EMEA>fastboot boot recovery.img
creating boot image...
creating boot image - 11888640 bytes
Sending 'boot.img' (11610 KB) OKAY [ 0.346s]
Booting FAILED (remote: 'invalid kernel address: not lie in memory')
fastboot: error: Command failed
do you have any idea if that's recovery image or something else? also is possible to flash ROM from TWRP or fastboot cli, i tried some other program called "SP_Flash_Tool_v5.1952_Win" but when i open it and try to flash it doesn't connect to my phone :crying:
daraw said:
run
Thanks to you i found ROM at https://mirrors.lolinet.com/firmware/moto/woods/official/oem/
since my Moto E4 says Woods from fast boot, and on screen reports SKU : XT1761
i've download xt1761_fastboot_woods_oem_user_7.1.1_NMA26.42-11-3_3_release-keys_oem_EMEA
this zip also includes a "recovery.img" is that the stock recovery? i tried to boot it with fastboot but i got this error
do you have any idea if that's recovery image or something else? also is possible to flash ROM from TWRP or fastboot cli, i tried some other program called "SP_Flash_Tool_v5.1952_Win" but when i open it and try to flash it doesn't connect to my phone :crying:
Click to expand...
Click to collapse
There's some woods flashing instructions in
https://forum.xda-developers.com/moto-e4/how-to/stock-os-moto-e4-sku-version-xt1760-t3719075
Just for update,
after hours trying i was able to install lineage-15.0-20171216_090858-UNOFFICIAL-nicklaus.zip
however phone stuck in a bootloop, so i gave up and started testing SP flash tool and managed to get stock android back and working as normal.
My point was to get android 9 or 8, if anyone knows or has any idea how to please let me know
i'm talking about Moto E4 (Woods), XT1761,
TWRP Version that's working for me twrp-3.2.2-0-woods.img
other then that i've tested lots of ROM i got none working (was able to install LineageOS 15.0 but ended on bootloop)
daraw said:
Just for update,
after hours trying i was able to install lineage-15.0-20171216_090858-UNOFFICIAL-nicklaus.zip
...
Click to expand...
Click to collapse
Make sure they say woods
Nicklaus is E4 Plus XT1776
https://forum.xda-developers.com/moto-e4/development
Sent from my ali using XDA Labs
sd_shadow said:
Make sure they say woods
Nicklaus is E4 Plus XT1776
https://forum.xda-developers.com/moto-e4/development
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
yeah i tested a lot saying woods none of them worked cause of no SKU match, as far as i've been looking there's no custom ROM for Moto E4 woods, XT1761