I can't root my HTC Magic from orange (PL) - myTouch 3G, Magic Android Development

I have htc magic from orange (Poland). I used this 2 methods and I can't root my phone
http://android-dls.com/wiki/index.php?title=Magic_Rooting
SAPPHIRE PVT 32A SHIP S-ON H
HBOOT-1.33.0009 (SAPP10000)
CPLD-12
RADIO-3.22.20.17
May 8 2009, 21:02:32
How should I do it? What I do wrong?

http://forum.xda-developers.com/showthread.php?t=530527
You can try the Rogers root update.zip, it has the same chipset.
This thread might also help you:
http://forum.xda-developers.com/showthread.php?t=523379

hotweiss said:
http://forum.xda-developers.com/showthread.php?t=530527
You can try the Rogers root update.zip, it has the same chipset.
Click to expand...
Click to collapse
Amon_RA said:
Only apply if you have a stock Roger's Magic without root!
The following procedure flashes the stock Roger's boot image with root access enabled to your Roger's Magic :
1. Copy this update to your SD-card.
2. Download RAv1.0's rooted recovery here.
3. Boot the device in fastboot mode.
4. Connect the device to your machine over USB.
5. $fastboot boot recovery-RAv1.0H.img
wait a few minutes and unplug your device from USB
6. Choose option "Apply sdcard:update.zip" from the menu
If the flashing doesn't work you might need to flash this SPL update from your sd-card after fast booting with recovery-RAv1.0H.img
Click to expand...
Click to collapse
I did everything and update SPL-HBOOT-1.33.2005-signed.zip. Now i can't turn on my phone it's stoping on the logo orange. I can't turn on fastboot mode.
What should I do?

piotrgo88 said:
I did everything and update SPL-HBOOT-1.33.2005-signed.zip. Now i can't turn on my phone it's stoping on the logo orange. I can't turn on fastboot mode.
What should I do?
Click to expand...
Click to collapse
Try pressing hold and back for 30 seconds.

Did you test the loading of the recovery rom before you flashed it?

It actually seems as if you have bricked your phone. Exchange it as soon as possible...

hotweiss said:
Try pressing hold and back for 30 seconds.
Click to expand...
Click to collapse
I can't do nothing.
xyzulu said:
Did you test the loading of the recovery rom before you flashed it?
Click to expand...
Click to collapse
No, I don't know how.
I have backup nandroid, but I can't turn on fastboot mode.
What I have to do now? Give this phone to my mobile phone company to warranty or what?

piotrgo88 said:
I can't do nothing.
No, I don't know how.
I have backup nandroid, but I can't turn on fastboot mode.
What I have to do now? Give this phone to my mobile phone company to warranty or what?
Click to expand...
Click to collapse
It sounds like something went wrong during the update, it seems to be bricked. I'd warranty it.

Orange (PL) HTC Magic
Hello All,
I've as well this equipment (32A) and I tried to root it as well. I got the same issue as well, but after an hard reset I'm able to get back to the fastboot mode and I've tried several other rooted OS and in the end I've the same result. The only thing I didn't done (and I think I avoid to brick my device on this situation) was update SPL-HBOOT-1.33.2005-signed.zip. -> Please correct me if I'm wrong! I've noticed if I go to the HBOOT mode I'm unable to communicate with the device. -> Any conclusion?
I've read other questions regarding the root access to android and I'm able to perform update (Like Google Maps), perform over clock on the device but, I'm not able to run some applications like the Quickboot? -> Is it odd? Or I got bad information regarding the root access from other threats like "To root or not to root" here in XDA?
One thing is for sure, I know that all equipments from HTC from Orange they have there specific firmware for Orange and on this equipment there's something fishy on it.. This equipment arrived here not so long ago and it will take time, experiences to solve this enigma. Help is needed and appreciated.
I've the Nandroid backup of my firmware and it has 167.90 M!!!
My Kernel version is [email protected]
Baseband is 62.52S.20.18U_3.22.20.17
Build number is 2.16.401.5 146733 CL#33743
I don't know if this can help on to comparer by the experts here, but anyway !!
Thanks in advance. I'll be waiting for news, until someone who gets it done with the Orange (PL) HTC Magic version.

Related

HELP! My update to new official rom went wrong!

Hello all
I downloaded the new ROM from the TW HTC site some minutes ago and proceed with flashing some time thouought the FLASH the pfone gave an error "Checking Custom ID"
"Update Failed"
And Android Update says ERROR 131 CUSTOMER ID ERROR
Now I can do nothing! The phone goes into HBOOT 1.76.0007 and I have a big icon with a memory chip on the bottom of the screen!
Pleace help me restore the hboot and recovery roms! The rest I'll menage.
same error..
You cant flash the update, don't do it.
Eugene is having a 32B ROM done and i belive he is uploading it atm.
32A users will soon have a flashable ROM.
WebghostDK said:
You cant flash the update, don't do it.
Eugene is having a 32B ROM done and i belive he is uploading it atm.
32A users will soon have a flashable ROM.
Click to expand...
Click to collapse
And for the ones that did it?
Great, i flashed my 32A via fastboot, and now im stuck in some strange state... I think i might have gotten a corrupt radio on it somehow...
Epedemic said:
Great, i flashed my 32A via fastboot, and now im stuck in some strange state... I think i might have gotten a corrupt radio on it somehow...
Click to expand...
Click to collapse
Yup it seems that way, as it now always hangs when flashing radio (trying a official 2.17 upgrade) grr...
Epedemic said:
Yup it seems that way, as it now always hangs when flashing radio (trying a official 2.17 upgrade) grr...
Click to expand...
Click to collapse
Yes. Cause you flashed a new HBoot.
You should wait, while romcookers will find way to downgrade new hboot
or repacked rom to flash properly to all customers, not only taiwanese.
I think it is time to clear things out:
DO NOT FLASH / UPDATE THIS ROM TO YOUR DEVICES!!!! - This means: Wait for someone to release correct ROM Updates to your devices. This official update is ONLY for TW devices. When you decide to flash something to your devices you should be very sure that you are not doing a stupid move! If someone tells you not to do it then you should hear that! Flashing something isn't like dressing a tshirt, and this means that if you choose a wrong size tshirt you can always take it off and dress another that fits you right. Flashing something that doesn't fit your device can easily brick it! Be aware!
5[Strogino] said:
Yes. Cause you flashed a new HBoot.
You should wait, while romcookers will find way to downgrade new hboot
or repacked rom to flash properly to all customers, not only taiwanese.
Click to expand...
Click to collapse
Indeed. I thought i was safe cause i flashed the files (boot.img, radio.img and system.img (which failed) via fastboot... Guess not... So now im stuck at the same screen with the cross over the ram chip
joaosousa said:
I think it is time to clear things out:
DO NOT FLASH / UPDATE THIS ROM TO YOUR DEVICES!!!! - This means: Wait for someone to release correct ROM Updates to your devices. This official update is ONLY for TW devices. When you decide to flash something to your devices you should be very sure that you are not doing a stupid move! If someone tells you not to do it then you should hear that! Flashing something isn't like dressing a tshirt, and this means that if you choose a wrong size tshirt you can always take it off and dress another that fits you right. Flashing something that doesn't fit your device can easily brick it! Be aware!
Click to expand...
Click to collapse
Yes we already know this! But it is too late! So please tell us how to fix the mess we have created!
I agree don't do stupid things in excitement. If you have eng spl etc by flashing all imgs )boot, radio etc) you may brick your device, so please please be careful wait for a update.zip file from greats mods like drizzy, eugene etc.
Once again I want to point that the purpose of this thread is help theese of us that DID the flash NOT knowing that it will NOT work!
OrionBG said:
Yes we already know this! But it is too late! So please tell us how to fix the mess we have created!
Click to expand...
Click to collapse
In my understanding the only thing you can do is to wait the official htc EU flasher (HTC said around mid November) and see if it's able to replace everything loading a proper radio/spl on the bricked device, acting on a lower level.
Otherwise you would just keep that expensive plastic brick ...
I am sorry, i was also eager to upgrade, but if HTC let you download their flasher only with a proper TW serial number, and if they've already advertised that you need to wait 2 or 3 weeks more for european firmware, then there should be a reason: so I didn't.
Hope you will be able to fix, but I am not too confident: guess you will need service.
It's ALIVE!!!! I have no idea how or why, but after tons of failed attempts and failed fastboot commands i now have the 3.03 update on my scandinavian 32a which i thought was bricked!
Epedemic said:
It's ALIVE!!!! I have no idea how or why, but after tons of failed attempts and failed fastboot commands i now have the 3.03 update on my scandinavian 32a which i thought was bricked!
Click to expand...
Click to collapse
Good. Now please write everything, what you did to get device alive)
5[Strogino] said:
Good. Now please write everything, what you did to get device alive)
Click to expand...
Click to collapse
yes yes post it please
i have no idea what actually did it, but it is possible that it was because i did a adb logcat command while the 3.03 update was running..
I can see that i have the 1.76 spl, and the new radio (which kept failing on me before)
i have try now to do adb logcat while update is running, but adb continuos stay in waiting for device, or say adb server is out to date ecc
Epedemic said:
i have no idea what actually did it, but it is possible that it was because i did a adb logcat command while the 3.03 update was running..
I can see that i have the 1.76 spl, and the new radio (which kept failing on me before)
Click to expand...
Click to collapse
Strange thing... adb logcat simply outputs log into console... How outputing logs can affect to flashing properly?
p.s. please post your full SPL-info too.
p.p.s. I think we need get right order to flashing this update. You tried to flash images via fastboot. What order do you have at first (boot - 1, radio - 2, system -3)?
What did you do at last?
i can't accesso to fastboot mode beacuse the phone stay in RUU USB ..

[HOW-TO] downgrade HBOOT 0.92 to 0.80 again

!!!! ROOTING/FLASHING/DOWNGRADING IS ALWAYS ON YOUR OWN RISK !!!!
Attention: This method will completely wipe your phone!!!
You can find the reworked Tutorial here: http://android-tutorials.org/
Video of the first step is online: Step 1
Video of the 3 & 4 step is online: Step 3 & 4
Known Problems
If you have problems while re-rooting or custom recovery (unrevoke) try to downgrade again with the above procedure.
Make sure you have made a new goldcard.
If you have problems e.g. 140 ERROR please follow these instructions (thx to raz2133)
This will fix your MISC Partition so you can flash back original RUU files.
Happy re-rooting
P.S. i hope you can understand this because english is not my foreign language
Great News!
Im not Root-Bricked ^^ but someone else will be happy with it =)
Edit: Why is 1 Pic from July and one from March!? And different times.
Thank you!!!
Maybe you should add: this wipes your device...
This is great, keep up the good work! =)
Edit: Are we sure those that do not have a carrier locked/branded also needs to create a goldcard?
Nitrius said:
This is great, keep up the good work! =)
Edit: Are we sure those that do not have a carrier locked/branded also needs to create a goldcard?
Click to expand...
Click to collapse
Not sure about that. i had a branded Vodafone version and unbranded it.
If someone could try without goldcard and report here
xtcislove said:
Edit: Why is 1 Pic from July and one from March!? And different times.
Click to expand...
Click to collapse
That was when the bootloader was built, not the current time.
sorch said:
That was when the bootloader was built, not the current time.
Click to expand...
Click to collapse
Ah thanks ! Dont know this =)
I hope this will work on generic devices that are not branded...
Sammy83 said:
For everyone how was in bad luck and updated to the original OTA FroYo here is a way how you can revert it.
The User maximini1 has found a thread where they describe how you can downgrade to 0.80 again.
So i try to explain how you have to do it.
Preparation
1. Make a NEW Goldcard (here)
2. Download PB99IMG.zip (here - MIRROR - germany MIRROR2)
3. Rename the downloaded file to "PB99IMG.zip" and copy it onto your SD Card.
Flashing
1. Shutdown yor mobile
2. Hold Volume up and press power
3. wait until PB99IMG.zip was found and checked
4. Press Volume Up <yes> - PICTURE 1
5. Wait until all steps are done. DON't POWER OFF YOUR DEVICE!!! - PICTURE 2
6. After flashing press Volume Up to reboot
7. done
Happy re-rooting
Click to expand...
Click to collapse
Is it working? Did try anyone?
Sammy83 said:
Not sure about that. i had a branded Vodafone version and unbranded it.
If someone could try without goldcard and report here
Click to expand...
Click to collapse
Looks like it's possible for those with an unbranded/unlocked phone:
mbroeders said:
First of all, I have an unbranded simlock-free phone. All I did was
1. download the file to SD card.
2. rename to PB99IMG.zip
3. boot into recovery (turn phone on while holding down volume)
4. just let it load the zip file and press yes when asked to install
Easy as that!
Click to expand...
Click to collapse
SharpSA said:
Is it working? Did try anyone?
Click to expand...
Click to collapse
Yes working 100%
Ok, I never rooted my android before and I have the OTA 2.2 Froyo update on an unbranded Desire. After I complete these steps, what do I need to do to install a custom rom?
Thanks!
Wheezy_be said:
Ok, I never rooted my android before and I have the OTA 2.2 Froyo update on an unbranded Desire. After I complete these steps, what do I need to do to install a custom rom?
Thanks!
Click to expand...
Click to collapse
Root your phone with unrevoked, using on of these guides for example:
Linux:
http://myhtcdesire.com/modding/how-to-root-your-desire-easily-method-1
Windows:
http://myhtcdesire.com/modding/how-to-root-your-desire-easily-method-2
Ok for the dumb and ignorant among us (a.k.a me) what state does this leave your phone in.
I get I downgrade HBOOT to 0.80 and my phone will be wiped, but what ROM will be on the phone after the downgrade will it still be the OTA rom or will it be another one?
Or do I then need to install a ROM of my choice after the downgrade, sorry if this is a really stupid question, I haven't put any custom ROM on my Desire yet and then I got the OTA update as I was thinking about checking out some custom stuff. Not had the phone long.
Thanks.
{EDIT} someone beat me to it as I was typing this post thanks for the above!
u9dbg said:
Ok for the dumb and ignorant among us (a.k.a me) what state does this leave your phone in.
I get I downgrade HBOOT to 0.80 and my phone will be wiped, but what ROM will be on the phone after the downgrade will it still be the OTA rom or will it be another one?
Or do I then need to install a ROM of my choice after the downgrade, sorry if this is a really stupid question, I haven't put any custom ROM on my Desire yet and then I got the OTA update as I was thinking about checking out some custom stuff. Not had the phone long.
Thanks.
Click to expand...
Click to collapse
After you've done the steps above you will have the following:
Blank and wiped device
Firmware: 2.1-update1 UNROOTED!
HBOOT: 0.80
Basband(Radio): 32.36.00.28U_4.06.00.02_2
Kernel: [email protected]#1
Build: 1.21.405.2 CL174215 release-keys
With that you can root and flash anything you want
Thanks for the tuto.
Hello sweety 0.80, bye bye dirty 0.92 ^_^
Worked for me.
Btw, didn't need the gc
Well, if this works AdamG doesn't have to find a way to root hboot 0.92.
:/
Sent from my HTC Desire using XDA App
Has anyone tried this on a branded, but rooted phone?
I've got an O2 branded desire with hb00t 0.83, I can root with unrevoked, but can't boot into recovery =( Hoping this will fix it.
It's works fine! Why doesn't work the recovery bat. on my PC?
u9dbg said:
Ok for the dumb and ignorant among us (a.k.a me) what state does this leave your phone in.
I get I downgrade HBOOT to 0.80 and my phone will be wiped, but what ROM will be on the phone after the downgrade will it still be the OTA rom or will it be another one?
Click to expand...
Click to collapse
Also for me, it's Volume Down + Power

[FIXED] Flashing Issues with Security Unlocked / Not For Resale phone (Error [340])

UPDATE:
I managed to fix it by first running the ACDU fix and then installing the European RUU over it! It even updates now!!
ACDU.exe (click the button on the right to download)
Released RUUs for HTC 8X (make sure to get one that corresponds to your device!)
KEEP IN MIND THAT THIS HAS WORKED FOR ME AND MY SECURITY UNLOCKED DEVICE,
THERE IS NO GUARANTEE THAT IT WILL WORK FOR YOU
IF YOU BRICK YOUR DEVICE, IT'S ON YOU.​
Steps:
Put your device in the bootloader screen by powering it off, and then turning it back on while holding the vol up + vol down buttons simultaneously.
Connect the device to your computer and let Windows locate and install the driver needed. Wait until the driver is fully installed and/or you can see the word USB written on the bootloader screen.
Run the ACDU.exe file and let it do its job (This supposedly unbrands your phone!). It should restart a couple of times showing a green screen and then eventually go into the bootloader menu. It might say something like "UEFI for Key Provision ONLY" in red letters, ignore that.
Run the RUU you've downloaded and if everything goes as planned it should flash correctly. If not, make sure you've downloaded the correct RUU for your device and that it's not corrupted.
Enjoy your (unbricked and) updatable security unlocked device.
I hope this helps!!
Source used (it's in chinese): http://bbs.lumwp.com/thread-133710-1-1.html
---------------------------------------------------------------------------------------
Hello,
I have an HTC 8X that appears to be security unlocked and therefore could not receive updates.
In my infinite wisdom, I decided to try to flash the European RUU that has been released in the internet, hoping it would allow me to update the phone further. I did not proceed unprepared and I did indeed check that the phone was European (it initially had the OS version: 2.00.401.03) so it looked as if everything matched.
However, after starting the update, RUU flashed some UEFI related files and then the phone restarted. It started up and resumed the main firmware flashing process, stopping at the 1% mark and restarting back the bootloader.
The error code reported by RUU is the following:
Error [340]: ENCSS_VERIFY_ERROR
SSD Error, please flash subsystem does not encrypted image
The error message is kinda incoherent and I can't find anything about it (except in a thread in XDA, where someone states that this might be because I need an American firmware?), what's worse is that I'm left with a soft-bricked device that I can do nothing with since it can only boot to the bootloader.
The device is unlocked, unbranded and security unlocked (CID: 11111111), yet I'm still stuck.
If I try to flash only the UEFI stuff (by removing the RUU .nbh from the directory), the device is then able to boot to the HTC logo and get into the dual gear screen, where it gets stuck. The hard reset option does not seem to work at all, the phone restarts at the HTC logo if I keep the vol down button pressed. Strangely, I can get into the lightning screen but I dunno what that might do.
Did I mention that the device cannot shutdown? Yeah... It only restarts...
Does anyone know any way to fix this? Or why this might be occuring?
Click to expand...
Click to collapse
I've managed to fix it and I've included the solution in my first post. I hope this helps.
This just skips the CID check.
You can also change the CID by command to like HTC__001 and get the OTA's and be able to install RUU's the normal way.
help
xmoo said:
This just skips the CID check.
You can also change the CID by command to like HTC__001 and get the OTA's and be able to install RUU's the normal way.
Click to expand...
Click to collapse
i have a 8x(620e) bricked after updating wp8.1.It booted after updated but auto bootboop before wp8.1 gui.I try to hard reset,it can not help.So i try to flash it.but it says image version ledd than device version.Can you help me?Thanks.
fengsam said:
i have a 8x(620e) bricked after updating wp8.1.It booted after updated but auto bootboop before wp8.1 gui.I try to hard reset,it can not help.So i try to flash it.but it says image version ledd than device version.Can you help me?Thanks.
Click to expand...
Click to collapse
Nope I can't. I'm new in the Windows Phone world. I'm a Android pro
help
Potis20 said:
UPDATE:
I managed to fix it by first running the ACDU fix and then installing the European RUU over it! It even updates now!!
ACDU.exe (click the button on the right to download)
Released RUUs for HTC 8X (make sure to get one that corresponds to your device!)
KEEP IN MIND THAT THIS HAS WORKED FOR ME AND MY SECURITY UNLOCKED DEVICE,
THERE IS NO GUARANTEE THAT IT WILL WORK FOR YOU
IF YOU BRICK YOUR DEVICE, IT'S ON YOU.​
Steps:
Put your device in the bootloader screen by powering it off, and then turning it back on while holding the vol up + vol down buttons simultaneously.
Connect the device to your computer and let Windows locate and install the driver needed. Wait until the driver is fully installed and/or you can see the word USB written on the bootloader screen.
Run the ACDU.exe file and let it do its job (This supposedly unbrands your phone!). It should restart a couple of times showing a green screen and then eventually go into the bootloader menu. It might say something like "UEFI for Key Provision ONLY" in red letters, ignore that.
Run the RUU you've downloaded and if everything goes as planned it should flash correctly. If not, make sure you've downloaded the correct RUU for your device and that it's not corrupted.
Enjoy your (unbricked and) updatable security unlocked device.
I hope this helps!!
Source used (it's in chinese): http://bbs.lumwp.com/thread-133710-1-1.html
---------------------------------------------------------------------------------------
Click to expand...
Click to collapse
could you list your bootloader message?
fengsam said:
could you list your bootloader message?
Click to expand...
Click to collapse
Well, after updating to GDR3, it seems that the bootloader messages have changed.
As of right now, it says
Security Unlocked
PM2320001 P S WP8 I (Before flashing ACDU, I think it used to be only "PM230001")
SBL1-1.0.21009.0
SBL2-1.0.21009.0
SBL3-1.0.21009.0
RPM-1.1.03078.0
TZ-303.000.241
UEFI-0.0.3030.0(175731) (Before updating, it used to be something like "15****", where * = numbers)
OS-4.12.401.01 (Before updating, it used to be 2.00.401.03)
CID-11111111
Radio-1.20b-32-19.04_15.67b.32.19 (Before flashing/updating, it used to be something like "1.11b.32.19.23")
fengsam said:
i have a 8x(620e) bricked after updating wp8.1.It booted after updated but auto bootboop before wp8.1 gui.I try to hard reset,it can not help.So i try to flash it.but it says image version ledd than device version.Can you help me?Thanks.
Click to expand...
Click to collapse
Ah, that's unfortunate. I don't know of a way to bypass the version check. =/ I don't understand why they're making things so difficult for end users. If you're flashing a full ROM, then you don't care what the previous one was... The only thing I can think of is that maybe on each update they blow a fuse so that you can't go back, like on the Xbox360
xmoo said:
This just skips the CID check.
You can also change the CID by command to like HTC__001 and get the OTA's and be able to install RUU's the normal way.
Click to expand...
Click to collapse
How would I go around doing that?
Potis20 said:
Well, after updating to GDR3, it seems that the bootloader messages have changed.
As of right now, it says
Security Unlocked
PM2320001 P S WP8 I (Before flashing ACDU, I think it used to be only "PM230001")
SBL1-1.0.21009.0
SBL2-1.0.21009.0
SBL3-1.0.21009.0
RPM-1.1.03078.0
TZ-303.000.241
UEFI-0.0.3030.0(175731) (Before updating, it used to be something like "15****", where * = numbers)
OS-4.12.401.01 (Before updating, it used to be 2.00.401.03)
CID-11111111
Radio-1.20b-32-19.04_15.67b.32.19 (Before flashing/updating, it used to be something like "1.11b.32.19.23")
Ah, that's unfortunate. I don't know of a way to bypass the version check. =/ I don't understand why they're making things so difficult for end users. If you're flashing a full ROM, then you don't care what the previous one was... The only thing I can think of is that maybe on each update they blow a fuse so that you can't go back, like on the Xbox360
How would I go around doing that?
Click to expand...
Click to collapse
Your message is same with mine.http://forum.xda-developers.com/showthread.php?t=2722104
fengsam said:
Your message is same with mine.http://forum.xda-developers.com/showthread.php?t=2722104
Click to expand...
Click to collapse
Well, unless we can find a way to bypass the OS version check set by HTC (or MS?), I guess you're stuck. =(
I was thinking of updating to 8.1 but after the whole ordeal above, I said "**** it, I'll get it when it's updatable! I'm not taking the change of bricking it again.."
..This captcha thing is starting to get very annoying...
Potis20 said:
Well, unless we can find a way to bypass the OS version check set by HTC (or MS?), I guess you're stuck. =(
I was thinking of updating to 8.1 but after the whole ordeal above, I said "**** it, I'll get it when it's updatable! I'm not taking the change of bricking it again.."
..This captcha thing is starting to get very annoying...
Click to expand...
Click to collapse
I think the OS version check set by htc.Because htc8s can still downgrade by reflashing ruu.I am very happy to update wp8.1,but bricked.
@Potis20 Can you re-upload the ACDU.exe file? The link says the file was removed...
Can someone upload ACDU.exe fix file again??
I have HTC wp 8x from O2 and i try to unlock with your instructions :good:
Threshergr said:
Can someone upload ACDU.exe fix file again??
I have HTC wp 8x from O2 and i try to unlock with your instructions :good:
Click to expand...
Click to collapse
I don't have the ACDU file but I was able to unlock my phone using the ACDU_UEFI_PROV_KEY.nbh file.
1. Download ACDU_UEFI_PROV_KEY https://mega.co.nz/#!UlMS1CyQ!rX-5-U6mmBHncVw6etFYeuSuV-OLX1De-jgkgEGf6FU
2. Put the ACDU file in the same directory as the ROMUpdateUtility (move the other .nbh files to another folder)
3. Run ROMUpdateUtility.exe
4. Phone should flash and unlock
5. Delete the ACDU_UEFI_PROV_KEY file
6. Move the UEFI_signed.nbh and RUU_signed.nbh files back
7. Run ROMUpdateUtility.exe again to flash ROM
Can someone upload ACDU.exe fix file again??
please !!!!!!!!!!!!!!
Same issue with HTC 8x Security Unlocked CID 1111111
Error [340]: ENCSS_VERIFY_ERROR
can you share your complete files package here?
thanks
i have downloaded latest nbh files for my HTC 8X by using windows device recovery tool and use the flash utility with nbh files as u said still no results. get the error : 340 encss verify error
SSD Error Please Flash subsystem does not encrypted image

HTC One A9: Remove Hard Brick?

Hi, guys!
Does anyone know how to unhard-brick A9? I killed HBOOT accidentally. Now it's only detected as Qualcomm Device and nothing is being loaded?
I have patched in hex editor and removed all that annoying text that came in red (without changing the checksum) from `aboot.bin`, that I extracted with `dd` from mmcblk0p12 partition. Later, I ran `fastboot flash aboot aboot.bin` under download mode and it didn't work (I also tried it under `fastboot oem rebootRUU`); Writing mmcblk0p12 partition with `dd` under `adb shell` also did not do anything..
Then I rebooted to bootloader and ran `fastboot flash aboot aboot.bin`. The message was - success. I happily rebooted and that was the end of the my HTC One A9 .
Is there a way to fix this dead phone - it's hard bricked!?
Also, could anyone explain, why it happened. I felt like I was doing everything correctly?
Thanks
qooob said:
Hi, guys!
Does anyone know how to unhard-brick A9? I killed HBOOT accidentally. Now it's only detected as Qualcomm Device and nothing is being loaded?
I have patched in hex editor and removed all that annoying text that came in red (without changing the checksum) from `aboot.bin`, that I extracted with `dd` from mmcblk0p12 partition. Later, I ran `fastboot flash aboot aboot.bin` under download mode and it didn't work (I also tried it under `fastboot oem rebootRUU`); Writing mmcblk0p12 partition with `dd` under `adb shell` also did not do anything..
Then I rebooted to bootloader and ran `fastboot flash aboot aboot.bin`. The message was - success. I happily rebooted and that was the end of the my HTC One A9 .
Is there a way to fix this dead phone - it's hard bricked!?
Also, could anyone explain, why it happened. I felt like I was doing everything correctly?
Thanks
Click to expand...
Click to collapse
Post an photo of device manager please [emoji14]
Inviato dal mio HTC One A9 utilizzando Tapatalk
You mean how it's detected under Windows Device Manager? It's actually different in Windows/Linux. I use Linux. But I could reload into Windows?
Thanks, here is the screen-shot of device manager, in case I got you correctly?
So, should I throw it away now?
qooob said:
So, should I throw it away now?
Click to expand...
Click to collapse
Can you get into download mode?
No, just blank screen. Like I already mentioned - HBOOT seems to be dead.
qooob said:
No, just blank screen. Like I already mentioned - HBOOT seems to be dead.
Click to expand...
Click to collapse
Helo guys,
I also hard bricked meine. Is there any solution to get it back ?
Thanks a lot for your answer.
Regards,
petithomme2005 said:
Helo guys,
I also hard bricked meine. Is there any solution to get it back ?
Thanks a lot for your answer.
Regards,
Click to expand...
Click to collapse
I don't think there is a solution yet. You need a programmator (device) to fix it. Take it back to store. They should give you your money back or take it to HTC support, they will fix it very quickly, in case they have a special device.
qooob said:
I don't think there is a solution yet. You need a programmator (device) to fix it. Take it back to store. They should give you your money back or take it to HTC support, they will fix it very quickly, in case they have a special device.
Click to expand...
Click to collapse
I have S-off and have installed cm13. I think that my warranty is gone. Du you think that they will repair it without asking to pay for it ?
Regards.
if warranty is gone than they will not fix it. for free
asadnow2k said:
if warranty is gone than they will not fix it. for free
Click to expand...
Click to collapse
i hope that the community will find a solution. Thanks a lot for your answers.
Regards,
petithomme2005 said:
I have S-off and have installed cm13. I think that my warranty is gone. Du you think that they will repair it without asking to pay for it ?
Regards.
Click to expand...
Click to collapse
They could actually. Do you have bootloader dead? If you hold power + volume-up, does the screen show anything (bootloader)?
Or it's black no matter what?
qooob said:
They could actually. Do you have bootloader dead? If you hold power + volume-up, does the screen show anything (bootloader)?
Or it's black no matter what?
Click to expand...
Click to collapse
The bootloader is dead and when i hold the power+volume-up i get a black screen and after that it stucks on screen with HTC on it with the warning message (red color)
Regards,
petithomme2005 said:
The bootloader is dead and when i hold the power+volume-up i get a black screen and after that it stucks on screen with HTC on it with the warning message (red color)
Regards,
Click to expand...
Click to collapse
It's easy to fix. Your bootloader is not dead. When I get home I'll find exact instructions for you.
qooob said:
It's easy to fix. Your bootloader is not dead. When I get home I'll find exact instructions for you.
Click to expand...
Click to collapse
Thank you, thank you, thank you. You will save my time
Regards,
petithomme2005 said:
Thank you, thank you, thank you. You will save my time
Regards,
Click to expand...
Click to collapse
Meanwhile, tell me - do you want CM or get back to stock?
I would like to install cm13, but the problem that i had is that the updates doesn't work any more for me as since Mail i think cm13 updates are based on 1.57 firmware version and my firmware was 1.27 version.
I would like to upgrade the firmware first before installing the last nightly cm13.
I hope you understood what i mean.
Thanks a lot.
Regards,
My problem was opposite. Back then I couldn't install CM because it didn't work with 1.56 and I had to downgrade from 1.56 to 1.27.
Can not say what is now. If you sure that you have version 1.27 installed and it still doesn't work then you need to upgrade to 1.56.
Go here and download latest ZIP firmware for your region (phone): http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Then flash it by going to Bootloader (turning phone off and then holding together power and volume down) - search Google or check here if doesn't work - http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930
To flash RUU just rename downloaded RUU file to 2PQ9IMG.zip, put it to the flash card and load in Download mode.
It will delete all data from your phone. It's worth trying to make a backup of your data partition first (in case you have apps and its important data). Afterwards, flash CM, and try to reboot. If it works. Flash custom recovery and then restore data partition.
In case it doesn't load, then I can't tell what exactly to do. Like I already said, I had to downgrade to 1.27 to make CM work 6 months ago. CM might change by now and now requires 1.56 to load. It's normal and very possible.
You might search Google to find out how to flash only firmware.zip without deleting data all the time. Back then it didn't work for me.
To downgrade firmare (just in case you need this), just goto to adb mode and run the following code to be able reflash 1.27 version again (need to change the version number to something lower than 1.27 and only then 1.27 RUU zip could be flashed)
Code:
adb shell
echo -ne "1.10.401.7\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot bootloader
Good luck.
qooob said:
My problem was opposite. Back then I couldn't install CM because it didn't work with 1.56 and I had to downgrade from 1.56 to 1.27.
Can not say what is now. If you sure that you have version 1.27 installed and it still doesn't work then you need to upgrade to 1.56.
Go here and download latest ZIP firmware for your region (phone): http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344
Then flash it by going to Bootloader (turning phone off and then holding together power and volume down) - search Google or check here if doesn't work - http://www.technewscentral.co.uk/enter-fastbootbootloader-mode-htc-one/id_7930
To flash RUU just rename downloaded RUU file to 2PQ9IMG.zip, put it to the flash card and load in Download mode.
It will delete all data from your phone. It's worth trying to make a backup of your data partition first (in case you have apps and its important data). Afterwards, flash CM, and try to reboot. If it works. Flash custom recovery and then restore data partition.
In case it doesn't load, then I can't tell what exactly to do. Like I already said, I had to downgrade to 1.27 to make CM work 6 months ago. CM might change by now and now requires 1.56 to load. It's normal and very possible.
You might search Google to find out how to flash only firmware.zip without deleting data all the time. Back then it didn't work for me.
To downgrade firmare (just in case you need this), just goto to adb mode and run the following code to be able reflash 1.27 version again (need to change the version number to something lower than 1.27 and only then 1.27 RUU zip could be flashed)
Code:
adb shell
echo -ne "1.10.401.7\x00\x00" | dd of=/dev/block/mmcblk0p28 bs=1 seek=2208
exit
adb reboot bootloader
Good luck.
Click to expand...
Click to collapse
I can not go to booloader, i tried all the possibilities but without success.

Can`t update software

Hi guys,
Ive got here Android version 8.0.0 and OTA 2.33.401.19 . Try to upload to Android pie but it shows a popup with (there was unexpected error and the file system may be corrupted. Please contact HTC support for further assistance). HTC want me to send my phone and sent me those prices ...had couple of bad experiences previously with their support(HTC M7, U10).
Does anyone have got this problem?
Go to Settings => About => Software Information
and tell us the Software Number.
Install Simple CID Getter from Google Play Store and tell us the CID it shows.
Then we'll find you an appropriate RUU and OTA to update your phone to Android Pie without needing HTC's help at all.
Thanks!
HTC_034 and software number 2.33.401.19
Hi,
I do have exactly the same issue on an untouched U11 single Sim. HTC support is not able to help me.
Current software version is 2.33.161.11 of a German Vodafone Rom with CID VODAP102.
So I am desperately looking for OTA to from 2.33.161.11 to 2.33.161.12 and then to 3.36.161.1 or a RUU for 3.36.161.1.
Any help is more than welcome.
@breno_campolina: have you tried to clear the cache of the those two system apps: update and download manager (Apps -> 3 point menu -> show system apps)? You might also want to try to download the update within the safe mode. I have tried all of this without success.
Cheers
Elendiir
elendiir said:
Hi,
I do have exactly the same issue on an untouched U11 single Sim. HTC support is not able to help me.
Current software version is 2.33.161.11 of a German Vodafone Rom with CID VODAP102.
So I am desperately looking for OTA to from 2.33.161.11 to 2.33.161.12 and then to 3.36.161.1 or a RUU for 3.36.161.1.
Any help is more than welcome.
@breno_campolina: have you tried to clear the cache of the those two system apps: update and download manager (Apps -> 3 point menu -> show system apps)? You might also want to try to download the update within the safe mode. I have tried all of this without success.
Cheers
Elendiir
Click to expand...
Click to collapse
Mine is also untouched and it is dual sim.
Did all this steps with them, did a factory reset too.
After this I think I`m done with them.... tired to be fobbed off
breno_campolina said:
Thanks!
HTC_034 and software number 2.33.401.19
Click to expand...
Click to collapse
Dual SIM right ? If yes, backup your data to your PC and flash this RUU in order to get a fresh start and from there use the Software Update check in Settings to upgrade to Pie.
https://androidfilehost.com/?fid=673956719939818418
To flash the RUU, the easiest way is to put it in the root folder of a MicroSD card, put it in the u11, power off, boot to Download Mode with Vol Down + Power together and follow the simple instructions on the screen to flash the RUU.
htc_one_mini_m4 said:
Dual SIM right ? If yes, backup your data to your PC and flash this RUU in order to get a fresh start and from there use the Software Update check in Settings to upgrade to Pie.
https://androidfilehost.com/?fid=673956719939818418
To flash the RUU, the easiest way is to put it in the root folder of a MicroSD card, put it in the u11, power off, boot to Download Mode with Vol Down + Power together and follow the simple instructions on the screen to flash the RUU.
Click to expand...
Click to collapse
Thanks!! I will try it tonight and come back to you!
htc_one_mini_m4 said:
Dual SIM right ? If yes, backup your data to your PC and flash this RUU in order to get a fresh start and from there use the Software Update check in Settings to upgrade to Pie.
https://androidfilehost.com/?fid=673956719939818418
To flash the RUU, the easiest way is to put it in the root folder of a MicroSD card, put it in the u11, power off, boot to Download Mode with Vol Down + Power together and follow the simple instructions on the screen to flash the RUU.
Click to expand...
Click to collapse
@htc_one_mini_m4 just put it on the sd card and boot on download mode, but it didn't do anything. Could explain me how to do it, please?
Sorry about the noob question.
breno_campolina said:
@htc_one_mini_m4 just put it on the sd card and boot on download mode, but it didn't do anything. Could explain me how to do it, please?
Sorry about the noob question.
Click to expand...
Click to collapse
Sure,
Here are the necessary steps.
Firstly, rename the file you downloaded to 2PZCIMG.zip
Reboot to download mode by powering up the phone with the Vol Down + Power button together.
Once it has loaded it will ask you if you want to perform flash RUU, just press the Volume Up button once to do so.
Wait, keep looking at your phone's screen.
It will reboot when finished, be patient while the flash is ongoing, and if it gets stuck on a black screen, DO NOT do anything, it will take some time until it reboots.
htc_one_mini_m4 said:
Sure,
Here are the necessary steps.
Firstly, rename the file you downloaded to 2PZCIMG.zip
Reboot to download mode by powering up the phone with the Vol Down + Power button together.
Once it has loaded it will ask you if you want to perform flash RUU, just press the Volume Up button once to do so.
Wait, keep looking at your phone's screen.
It will reboot when finished, be patient while the flash is ongoing, and if it gets stuck on a black screen, DO NOT do anything, it will take some time until it reboots.
Click to expand...
Click to collapse
Just did it and rename the file as you mentioned. It appears on the top htc download mode, but it didn't do anything.
can you post a screenshot ( photo ) of your phone at that screen ?
htc_one_mini_m4 said:
can you post a screenshot ( photo ) of your phone at that screen ?
Click to expand...
Click to collapse
Find it attached
Have you formatted your SD Card on your phone ?
And placed the renamed zip file in the main ( root ) folder of the SD Card ?
Follow this video guide, it's good
https://www.youtube.com/watch?v=1ACU3RGm9YI
Yes I did it.
Please check the file attached.
breno_campolina said:
Yes I did it.
Please check the file attached.
Click to expand...
Click to collapse
Just take out one ".zip" here
Once you remove the extra .zip it should do fine
htc_one_mini_m4 said:
Once you remove the extra .zip it should do fine
Click to expand...
Click to collapse
JUST GOT IT!! Thank you so much for your patience ))!
breno_campolina said:
JUST GOT IT!! Thank you so much for your patience ))!
Click to expand...
Click to collapse
You're welcome.
Now you'll be able to find the OTA updates via the Settings => About => Software Updates menu
Let us know if you succeeded in getting to Pie finally
htc_one_mini_m4 said:
You're welcome.
Now you'll be able to find the OTA updates via the Settings => About => Software Updates menu
Let us know if you succeeded in getting to Pie finally
Click to expand...
Click to collapse
Yes!!! Now getting used to android 9.0 :laugh::laugh:
Thank you!!!
Really sorry to just drop this here but I can't find what I need...please push me in the right direction. I have HTC U11 Unlocked, S-ON, I was using TWRP and Magisk for the longest time and fine. I'm afraid based on my latest user expriences with my phone I need OTA badly to get up to speed. Obviously I can't take it, the download gets corrupted. I am back to stock recovery but still rooted. Software Number 2.42.617.7, Android version 8.0. I did nothing but unlock and Magisk to this system since I got it in 2017. Please help me acquire the OTA and apply it or get to a state I can take it over the air.

Categories

Resources