I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
kreep22 said:
I'm trying to RUU back to stock DNA on Verizon but it keeps telling me there is an error
it tells me "ERROR [158]: Image error"
am i missing something?
Click to expand...
Click to collapse
Did you lock the phone again first, if you had previously unlocked/rooted?
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
kreep22 said:
yes, it's showing relocked status and it wont let me do anything just takes me to the bootloader no matter what i do
Click to expand...
Click to collapse
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
.torrented said:
Right Click and Run as Admin try that... make sure you are in fastboot usb mode as well or redownload the RUU maybe you got a bad DL
Click to expand...
Click to collapse
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
kreep22 said:
I tried to Run as Admin and no luck tells me the same error message, i've done it before with the same ruu that i am trying with now but idk what is going on, am i bricked?
Click to expand...
Click to collapse
does your phone boot to android at all? or recovery
.torrented said:
does your phone boot to android at all? or recovery
Click to expand...
Click to collapse
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
kreep22 said:
I got it wprking, just re unlocked and rom came back on. Thank u
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
How did you do it can you please explain?
Tried going back to stock settings
Relocked m errory phone s- off still the ruu wizard keeps giving me error 158? Flashed hboot with no luck. how do I unlock again like I said still s-off
wondering how u unlocked again
chris1569810 said:
How did you do it can you please explain?
Click to expand...
Click to collapse
I'm in the same situation
You flashed the stock hboot with no problems? Which hboot?
Help! I have a similar problem
GreginNH said:
Did you lock the phone again first, if you had previously unlocked/rooted?
Click to expand...
Click to collapse
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
madc321 said:
I used moonshine S-OFF to root my DNA. I dont know how to get back to the stock locked hboot. and i keep getting that error 158.
any recommendations?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2293919
finanandroid said:
http://forum.xda-developers.com/showthread.php?t=2293919
Click to expand...
Click to collapse
Thanks but I tried that with no luck. I was able to flash viper venom though. no idea why the bamf rom did not work.
Solution?
So what ended up being the solution for the Error 158 and being stuck at Fastboot? I can't seem to find one that will work. Check my thread in Q & A: http://forum.xda-developers.com/showthread.php?t=2649525
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
jaymazz13 said:
Before running ruu u should boot into fastboot and make u see fastboot usb then start ruu, the error is because ur device can't boot into bootloader to finish with ruu
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
sasquatch1 said:
I just spent 20 minutes freaking out. I kept getting the 158 error over and over. I fastboot flashed the locked bootloader file and it said RELOCKED, but still errored out.
I was on the ENG hboot at the time and fastboot flashed the vanilla 3.06 hboot and this time the RUU went through.
Hopefully this will help somebody else out.
Click to expand...
Click to collapse
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(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-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
DuceTheTruth said:
How can I do this if phone was fully stock before recieving an OTA via Verizon and now wont get past white HTC screen?
I am s-on...I cant flash anything...and RUU keeps failing.
---------- Post added at 04:56 PM ---------- Previous post was at 04:51 PM ----------
C:\>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.01.1112
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.09.605.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA2BPS501936
(bootloader) imei: 990000671822338
(bootloader) meid: 99000067182233
(bootloader) product: monarudo
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL8320000
(bootloader) cidnum: VZW__001
(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-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
By above post i could understand that your phone is S-On and LOCKED.
If that was the case, How your phone got updated to boot 1.57.0000?
Have you flashed anything (firmware) in fastboot mode?
If yes, You have very less chance to get the phone working unless its JTAGed.
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
---------- Post added at 06:34 PM ---------- Previous post was at 06:19 PM ----------
DuceTheTruth said:
First of all thank you for your reply...
This phone was all stock when I received it in this state...never been rooted ...unlocked or anything....
All I know is that after accepting an OTA update from vzw the phone never booted up fully again...
Now I did try the flashing instructions from .torrented but everything I do fails...
I get "remote 22 loading zip info fail"...
I also get " remote 12 signature verify fail"....
Sent from my SPH-L710 using XDA Free mobile app
Click to expand...
Click to collapse
C:\adb>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.073s]
finished. total time: 0.073s
C:\adb>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.038s]
finished. total time: 0.039s
C:\adb>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\adb>fastboot flash zip PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'zip' (11248 KB)...
OKAY [ 1.343s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.451s
C:\adb>fastboot flash zip PL83IMG_1.15_hboot
error: cannot open 'PL83IMG_1.15_hboot'
C:\adb>fastboot flash zip PL83IMG_1.15_hboot.zip
target reported max download size of 1514139648 bytes
sending 'zip' (434 KB)...
OKAY [ 0.202s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.252s
C:\adb>fastboot flash recovery PL83IMG_3.06_Recovery.zip
target reported max download size of 1514139648 bytes
sending 'recovery' (11248 KB)...
OKAY [ 1.364s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 2.470s
Related
Rogers said the new HTC EVO 3D bootloader would come unlocked, yet, on the bootloader screen, I get this:
Code:
*** LOCKED ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0008
eMMC-boot
Jul 15 2011,14:39:25
Does't look unlocked to me...
Has anyone been able to successfully unlock/root a GSM EVO 3D yet?
Don't take Social Media's "word" as any sort of truth, they just relay information.
HTC hasn't released the OTA yet to unlock the bootloader but they will.
This actually came from a Rogers rep on a Rogers website: http://mobilesyrup.com/2011/07/18/rogers-yes-our-htc-evo-3d-will-have-an-unlocked-bootloader/
Here's the actual Rogers site: http://redboard.rogers.com/2011/eve...oducing-the-htc-evo-3d-and-the-lg-optimus-3d/
Yeah I was hoping it would come unlocked too but it looks like we're going to have to wait.
Sent from my HTC EVO 3D using Tapatalk
Turge said:
This actually came from a Rogers rep on a Rogers website: http://mobilesyrup.com/2011/07/18/rogers-yes-our-htc-evo-3d-will-have-an-unlocked-bootloader/
Here's the actual Rogers site: http://redboard.rogers.com/2011/eve...oducing-the-htc-evo-3d-and-the-lg-optimus-3d/
Click to expand...
Click to collapse
I know where your information came from.
I told you, never take Social Media's information as any form of "truth". Anything they post is still bound by the legal disclaimer on all Rogers websites that their information is subject to change and may not be accurate. Do you really expect a journalist to know anything about a Bootloader? All they do is spew information they're told, and do a half assed job at best with that.
That being said, the bootloader will get unlocked, likely sooner by Revolutionary than by HTC themselves.
Don't feel bad, the European EVO3D users are in the same boat.
It actually shows "locked" in the bootloader? Just out of curiousity, can someone check to see what fastboot commands are available? You can find out by using fastboot oem ? (with the question mark) or fastboot oem h while it is in fastboot mode.
xHausx said:
It actually shows "locked" in the bootloader? Just out of curiousity, can someone check to see what fastboot commands are available? You can find out by using fastboot oem ? (with the question mark) or fastboot oem h while it is in fastboot mode.
Click to expand...
Click to collapse
Here ya go:
(bootloader) command list
(bootloader) get_identifier_token
(bootloader) checkSbl1
(bootloader) checkHWSecurity
(bootloader) keytest
(bootloader) heap
(bootloader) boot
(bootloader) reset
(bootloader) powerdown
(bootloader) rebootRUU
(bootloader) heap_test
(bootloader) rtask
(bootloader) task
(bootloader) enableqxdm
(bootloader) gencheckpt
(bootloader) readpid
(bootloader) writepid
(bootloader) readcid
(bootloader) writecid
(bootloader) readimei
(bootloader) writeimei
(bootloader) readsecureflag
(bootloader) writesecureflag
(bootloader) lock
(bootloader) list_partition_emmc
(bootloader) load_emmc
(bootloader) check_emmc
(bootloader) check_emmc_mid
(bootloader) read_mmc
(bootloader) load_modem_emmc
(bootloader) get_wp_info_emmc
(bootloader) send_wp_info_emmc
(bootloader) get_ext_csd_emmc
(bootloader) get_sector_info_emmc
They must have just added that get_identifier_token command, I don't remember seeing it in the 1.30 hboot and the it's not in the eng hboot either.
Can you give it a try to see what it does?
Code:
fastboot oem writesecureflag 0
fastboot oem get_identifier_token ?
xHausx said:
They must have just added that get_identifier_token command, I don't remember seeing it in the 1.30 hboot and the it's not in the eng hboot either.
Can you give it a try to see what it does?
Code:
fastboot oem writesecureflag 0
fastboot oem get_identifier_token ?
Click to expand...
Click to collapse
From the looks of it, a gold card might be needed?
Code:
fastboot oem writesecureflag 0
...
(bootloader) vreg_set: request is duplicated id 14
(bootloader) shooter_u_init_sd, SD card power on ok
(bootloader) sdcc_init_memory_device done
(bootloader) [FAT_ERROR] fat_open_file: can not find SMART_IO.CRD
(bootloader) [JAVACARD_ERR] SMART_IO.CRD cann't find
(bootloader) writesecureflag: Permission denied, value 1
OKAY [ 1.084s]
finished. total time: 1.086s
fastboot oem get_identifier_token ?
...
(bootloader)
(bootloader) < Please cut following message >
(bootloader) <<<< Identifier Token Start >>>>
(bootloader) 979CAC9BC47B6A2DA6164C92F581BE6C
(bootloader) D48C11BF91C56DF93EB96ABBFDC0B557
(bootloader) 5C3794863CB29EE44BF2BDA4B684ECDC
(bootloader) D091FAA3D9373B838B81138D5E930523
(bootloader) 41343BCE21D915B2926BD3E20F6F62CB
(bootloader) D22B9904764499498AE78DC6880CBD81
(bootloader) 6A337E89DDB34F9970F3CCB3E042FD87
(bootloader) A89849D1FDBE1DAA7E63D979E43B2849
(bootloader) F4D1E2207BEEEE481E4AEF3DF8A569D1
(bootloader) 75C66DAA8B41FA6812A462A0F12E469E
(bootloader) F505A0B8B986E40745A81633FC287B2A
(bootloader) 7C975C2B54AE7FF86002FA119B4ACD66
(bootloader) DC92B98D6C1636F71EC23FBC5FFD153B
(bootloader) 8EEFB5A7A9BF12448EA5234CD62B43B7
(bootloader) 1F97385D6A6D890BBDD3ED1673AB2EBD
(bootloader) FE90D203A4F1EAF01FAC3FC5A4A06627
(bootloader) <<<<< Identifier Token End >>>>>
OKAY [ 0.073s]
finished. total time: 0.075s
The locked part it says must be for world unlocked. To use any sim.
They updated the RedBoard yesterday:
Rogers_Chris says: August 10, 2011 at 5:04 pm
Hi Andy,
When we announced the HTC EVO 3D coming to Rogers, we communicated that the device would launch with an unlocked bootloader (as Katie wrote above). Our apologies – we have since learned that the device will not be shipped unlocked. For more information on webtools, please visit the HTC website ww.HTCdev.com. If you decide to make a change, please note that some actions may void warranties.
Mnemoch said:
They updated the RedBoard yesterday:
Rogers_Chris says: August 10, 2011 at 5:04 pm
Hi Andy,
When we announced the HTC EVO 3D coming to Rogers, we communicated that the device would launch with an unlocked bootloader (as Katie wrote above). Our apologies – we have since learned that the device will not be shipped unlocked. For more information on webtools, please visit the HTC website ww.HTCdev.com. If you decide to make a change, please note that some actions may void warranties.
Click to expand...
Click to collapse
Looks like June 24th all over again.
My "DU4L C0R3 SH00T3R" shot you down in 3D! -Security Off-
Hi,
Unlocked my wife's Legend using the HTC-Dev method. Installed CM7 and she was happy... Now she is missing the HTC weather animations and wants to go back to the stock Froyo.
I have the correct RUU for her phone, carrier, and region, extracted from:
RUU_Legend_BellMobility_WWE_2.02.666.3_Radio_47.37.35.09_7.08.35.05_release_130094_signed.exe
First I tried to flash by renaming the rom.zip to LEGEIMG.zip. The bootloader saw it and chewed on it for a while, but the RUU ended up not being applied and the phone booted back into CM. Confusing.
Next attempt: fastboot, with bootloader unlocked.
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.795s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
[B]FAILED (remote: 99 unknown fail)[/B]
finished. total time: 18.643s
Did some more reading, found that RUUs only apply when the bootloader is locked. So I relocked the bootloader with fastboot oem lock and tried again:
Code:
[[email protected] ruu]# [B]fastboot erase cache[/B]
< waiting for device >
erasing 'cache'...
OKAY [ 0.258s]
finished. total time: 0.258s
[[email protected] ruu]# [B]fastboot oem rebootRUU[/B]
...
OKAY [ 0.017s]
finished. total time: 0.017s
[[email protected] ruu]# [B]fastboot flash zip rom.zip[/B]
sending 'zip' (124420 KB)...
OKAY [ 12.874s]
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...
[B]FAILED (remote: 43 main version check fail)[/B]
finished. total time: 44.062s
And trying the LEGEIMG.zip method after relocking:
Code:
Main version is older!
Update Fail!
Do you want to reboot device?
Here are my bootvars:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.02.0000
(bootloader) version-baseband: 7.13.35.13
(bootloader) version-cpld: None
(bootloader) version-microp: 0816
(bootloader) version-main: 3.30.0.0
(bootloader) serialno: HT05NRA07XX
(bootloader) imei: XXXXX
(bootloader) product: legend
(bootloader) platform: HBOOT-7227
(bootloader) modelid: PB7611000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3905mV
(bootloader) partition-layout: HTC
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-39ec9098
(bootloader) hbootpreupdate: 11
Apparently this means that I'm trying to flash an RUU that is older than what is on the device. The problem is, the RUU update that I last applied was the HTCDev one to allow unlocking. So the most recent "full" RUU is older than the HTCDev RUU and I can't seem to downgrade.
Am I missing something? I must be missing something. Please help, or the wife will have one up on me. Can't allow that
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
When I remember right, there was no version check during installation, you can install it with Clockwork mode Recovery.
alligator_asl said:
Hello,
try this ROM from BlaY0, its an improved stock ROM and you keep root.
Click to expand...
Click to collapse
Thanks, that's an acceptable workaround for now. I ended up going this route. Since CWM 5.X doesn't like "amend" scripting, it took some doing though. :highfive:
If anyone knows of a way to downgrade to a stock RUU after applying the HBOOT 1.02 RUU to the Legend, that would be a help.
I'd suggest if you really need to go back stock froyo it can't be done with hboot 1.02, I have tried various different methods with no success.
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Sent from my Legend using xda app-developers app
ranger4740 said:
I can't remember who, but some where on legend forums (I think in the dev section) there is a method to downgrade back to hboot 1.01, if it works you can do it and flash ruu. I can't confirm if it works or not.
Click to expand...
Click to collapse
Yeah, that sounds right.
So for anyone reading this thread in the future, if you've unlocked your bootloader using HTC-dev you will be unable to return to stock Froyo using an official RUU without first downgrading to HBOOT 1.01 or older.
The HBOOT downgrade process is pretty involved. You need a goldcard and the hack4legend kit. See this thread for details.
And for good measure, here's a thread with someone else working out the same problem we just worked out here... :silly:
At the end of the day, if you ran a nandroid backup of your stock ROM before blowing it away, you won't need all this jazz.
ariaxu said:
Since CWM 5.X doesn't like "amend" scripting, it took some doing though.
Click to expand...
Click to collapse
You can take an older Versin of CWM ( recovery-clockwork-2.5.0.7-legend.zip ), ther are no problems with scripting, a google search brings several results.
If necessary, you lan load the old version of CWM from the new version and then you can flash this ROM !
I wiped everything using TWRP (Dalvik cache - System - Cache - Data - Internal Storage)
Now i don't have any OS.
I'm into TWRP recovery waiting instruction..
Please HELP!!!!
HTC One
AT&T
S-ON
Kitkat
C:\Program Files\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
U wipe system. So everything is gone! Now u need to install hole firmware by odin or u need to install any custom rom (zip file) by TWRP!
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 08:10 AM ---------- Previous post was at 08:03 AM ----------
Ohho odin not for u, because u r using htc
Sent from my SM-N9005 using XDA Premium 4 mobile app
---------- Post added at 08:11 AM ---------- Previous post was at 08:10 AM ----------
Just download "Android revolution hd" and then install it by TWRP
Sent from my SM-N9005 using XDA Premium 4 mobile app
Flash a nandroid if you have one or a Rom. If you don't then
Don't have your device but I would push a Rom onto your device using adb. Boot into recovery and from a command prompt on your pc and
adb push rom.zip /sdcard/download
rom.zip can be any rom for your device. Not sure of the /sdcard/download but it should be the folder you normally flash a rom from. Then boot into twrp and flash it
But can I install a ROM older than KITKAT ??
Which one for example??
psicobelico said:
But can I install a ROM older than KITKAT ??
Which one for example??
Click to expand...
Click to collapse
It doesn't matter what rom. Did you have a custom Rom on before or where you on the stock rom?
I was on the stock AT&T ROM (updated to KitKat)
psicobelico said:
I was on the stock AT&T ROM (updated to KitKat)
Click to expand...
Click to collapse
Then you should return to stock. See this
http://forum.xda-developers.com/showthread.php?p=43458497
Let me see..
Seemingly i have to be "S-OFF"
psicobelico said:
Let me see..
Seemingly i have to be "S-OFF"
Click to expand...
Click to collapse
This might help
Flash this ruu, then update to kitkat again. Think you will have to relock bootloader first.
http://www.htc1guru.com/2013/09/new-ruu-zip-released-android-4-3-firmware-3-10-502-2/
or
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Not sure what the difference is.
I can't install a ROM older than KITKAT, HBoot must be the same or newer version.
Nothing works..somebody help please..!!!!!!!!!!!!!!!!!
psicobelico said:
Nothing works..somebody help please..!!!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Push arhd 52 is your best bet
Sent from my HTC One using Tapatalk 4
when I try ADB sideload using TWRP 2.6.3.3 (to push ARHD 52) got the following error:
Updating partition details....
E: Failed to decryp data.
Also i don't know why when i open TWRP request a password..
!!!!!!!SOLVED!!!!!!!!
Installed ARHD through USB OTG...!!!!
Now is time to wait for official HTC KitKat RUU..
psicobelico said:
!!!!!!!SOLVED!!!!!!!!
Installed ARHD through USB OTG...!!!!
Now is time to wait for official HTC KitKat RUU..
Click to expand...
Click to collapse
Glad you got it working again!
Let this be a lesson to all you FlashCrackers, READ READ and then READ again before experiencing what this poor soul had to go through. Too much stress.
Revert to 2.47
Hi
I have hboot 2.49 want to revert back to 2.47 and plus want to convert it to International version i want to use 407 roms
Details
CID-1111111
HBOOT-2.49.0000
Radio-4T.24.3218.09
OS-2.61.708.1
or can someone provide me latest 2.49 with OS 401
Thanks
Hi
I successfully flashed rom RUU.exe BrightstarUS WWE 1.23.1540.1 (flyhalf's)
and when i got the OTA for 4.4.2 it says my mobile software been modified and cannot update
I used manually to update through fastboot oem rebootRUU
OTA_T6_UL_K44_SENSE55_MR_BrightstarUS_WWE_2.61.1540.1-1.23.1540.1_release
please help me if I did something wrong
Try Change back go stock cid
Sent from my HTC One max using xda premium
I don't really know what is my original CID
HTC___116
something like this not sure
i have seen a list somewhere maybe i will recognize it
EDIT: Actually original software was HK region changed it to WWE US brightstar
I found the CID is HTC__622
i tried to flash it with Brightstar US CID BS_US001
is not working
with original CID HTC__622
is not working
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
I dont know whats wrong,
please help
The Don Jay said:
I found the CID is HTC__622
i tried to flash it with Brightstar US CID BS_US001
is not working
with original CID HTC__622
is not working
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
I dont know whats wrong,
please help
Click to expand...
Click to collapse
Can you check what is your MID ? is it 0P3P50000?
Also can you post the exact error message or a photo?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.46.0000
(bootloader) version-baseband: 4T.21.3218.01
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.19.708.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA3ASWG05176
(bootloader) imei: 357311050403377
(bootloader) meid: 00000000000000
(bootloader) product: t6ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: 0P3P52000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4153mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.121s
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 20.643s
i have succeeded to flash
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_Radio_4T.21.3218.01_10.15.1718.01_release_337043_signed_Hboot_2_4
my boot showing 1.19.708.2 but software version is 1.23.1540.1
what is missing what is the right thing to do ?
please help
Hi
I have HTC One max HK Asia Version HTC__622 i tried to flash this rom in CMW, TWP and stock recovery but not taking
with locked and unlocked bootloader
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
tried wiping data, system and dalvik wipe but still giving me an error file is too large
is there anything i did wrong ?
please help im stuck
looking at the picture of you phone diplaying hboot, you cid is 111111111.
try changing back to a good 1
Hi
Problem solved thanks to Chinese website
changed the CID to the original which is HTC__622
Downloaded and copied and renamed the file
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
to
0P3PIMG.zip and located to external SD card
Locked or Relocked the Bootloader .. better locked to get the fingerprint working (this can be done with scotty's method)
got to bootloader mode and press power button to enter bootloader mode then the file will update automatically without any command
Done
source chinese website which i cant post yet
your help
The Don Jay said:
Hi
Problem solved thanks to Chinese website
changed the CID to the original which is HTC__622
Downloaded and copied and renamed the file
0P3PIMG_T6_UL_JB43_SENSE55_hTC_Asia_HK_1.19.708.2_ Radio_4T.21.3218.01_10.15.1718.01_release_337043_s igned_2_4.zip
to
0P3PIMG.zip and located to external SD card
Locked or Relocked the Bootloader .. better locked to get the fingerprint working (this can be done with scotty's method)
got to bootloader mode and press power button to enter bootloader mode then the file will update automatically without any command
Done
source chinese website which i cant post yet
Click to expand...
Click to collapse
I need to revert back my hboot 2.49 to 2.47 . I would appreciate your help on how did your do it
solved too on me
The Don Jay said:
Hi
Problem solved...
Click to expand...
Click to collapse
Thanks!
BadrSaleh said:
I need to revert back my hboot 2.49 to 2.47 . I would appreciate your help on how did your do it
Click to expand...
Click to collapse
you need soff using firewater.
then you can flash any hboot. but be careful to use the correct one!
hi
A few days ago my phone hard breaked
and i repaired boot with riff jtag box.now phone powerd on and run android but after 2-3 min system errored (process system isn't responding do you want to close it) and rebooted and repeated
phone info
getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.33.0001
INFOversion-baseband: 3A.32.306.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.13.401.4
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA2BPS507022
INFOimei: 3596910********
INFOmeid: 00000000000000
INFOproduct: monarudo
INFOplatform: HBOOT-8064
INFOmodelid: PL8320000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4208mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 041a62aa
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
im cant flashing any thing stock recovery hboot radio rom...
fastboot flash recovery recovery.img
sending 'recovery' (11464 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
im try to flashed any thing , the error is writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
try to unlock with htc dev but error
Error Code: 160.
Error Reason: MID Not Allowed.
please help me :crying:
thx
guitarr said:
hi
A few days ago my phone hard breaked
and i repaired boot with riff jtag box.now phone powerd on and run android but after 2-3 min system errored (process system isn't responding do you want to close it) and rebooted and repeated
phone info
getvar all
INFOversion: 0.5
INFOversion-bootloader: 1.33.0001
INFOversion-baseband: 3A.32.306.04
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 3.13.401.4
INFOversion-misc: PVT SHIP S-ON
INFOserialno: FA2BPS507022
INFOimei: 3596910********
INFOmeid: 00000000000000
INFOproduct: monarudo
INFOplatform: HBOOT-8064
INFOmodelid: PL8320000
INFOcidnum: VZW__001
INFObattery-status: good
INFObattery-voltage: 4208mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 041a62aa
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
im cant flashing any thing stock recovery hboot radio rom...
fastboot flash recovery recovery.img
sending 'recovery' (11464 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
im try to flashed any thing , the error is writing 'recovery'... INFOsignature checking...
FAILED (remote: signature verify fail)
try to unlock with htc dev but error
Error Code: 160.
Error Reason: MID Not Allowed.
please help me :crying:
thx
Click to expand...
Click to collapse
Try using rumrunner or moonshine to get soff and your bootloader unlocked then flash a custom recovery and new ROM.
Jaggar345 said:
Try using rumrunner or moonshine to get soff and your bootloader unlocked then flash a custom recovery and new ROM.
Click to expand...
Click to collapse
ican worked only in fast boot
info moonshine
Ok?
(Yes/No)
Yes
!! Do NOT for any reason touch, unplug, lick or maim your device !!
Checking for updates......
Please wait....
..........
ERROR: run distiller again and READ
any budy hear?
anybody can help me?
When using rum runner, disable all of your antivirus and malware software. Turn off your Firewall as well.
Sent from my HTC6525LVW using Tapatalk
I do the same
ThePunisher said:
When using rum runner, disable all of your antivirus and malware software. Turn off your Firewall as well.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I do the same
i run phone in fastboot mode and later run runner