Related
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 ..
i thought of re doing doloop's modd for CDMA TP2
and here it is fully tested to be working
confirmation thnx to ziggy471: http://forum.xda-developers.com/showpost.php?p=6052356&postcount=97
now we can mtty our TP2 without having the need of MTTY and its drivers
INSTRUCTIONS:
- download and unzip
- put you favorite RADIO in the mix
- run then task29.exe and wait for it to finish.....
- device will reboot but will neva go past the bootscreen coz there is no OS to boot
- take our batti and then flash a rom using mSD card or by taking device into bootloader and using customRUU to load ur favorite ROM
DOWNLOAD:
View attachment task29.zip
CREDIT:
all credit goes to doloop for coming up with the idea
doloop said:
Hi,
I hex edited RomUpdateUtility.exe so it runs task 29 right after flashing ruu_signed.nbh
As every one understand this command format the rom,
Just unzip and run task29.exe . You may replace ruu_signed.nbh with the radio of your choice.
After the phone reset itself, your old rom will be gone, so it won't boot: binfs has been formated, your phone memory is clean.
You'll need to power up in bootloader mode (press vol down right after power key), then use the leocustomruu.exe provided with your favorite rom package, or flash it from memory card using standard procedure.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=5845908&postcount=1
Thanks SO much Agent_47 and ALSO Ziggy. I really wasn't familiar enough with all of this to know exactly what to send. Now we can KNOW that what is available to us has been tested and confirmed! You guys are great!
Thanks much agent47 and everyone involved!
why would you wanna format internal memory>
freexx89 said:
why would you wanna format internal memory>
Click to expand...
Click to collapse
Before you flash a new ROM, just to make sure all of the old files get deleted. If some old files are not deleted, they have a chance of creating hiccups with your freshly installed ROM (basically the new ROM cannot over-write, over-ride or remove the old files). This is meant to help with clearing your internal storage.
burtonsnow8 said:
Before you flash a new ROM, just to make sure all of the old files get deleted. If some old files are not deleted, they have a chance of creating hiccups with your freshly installed ROM (basically the new ROM cannot over-write, over-ride or remove the old files). This is meant to help with clearing your internal storage.
Click to expand...
Click to collapse
Ohh okay... make sense...
GaryMcQ said:
Thanks SO much Agent_47 and ALSO Ziggy. I really wasn't familiar enough with all of this to know exactly what to send. Now we can KNOW that what is available to us has been tested and confirmed! You guys are great!
Click to expand...
Click to collapse
It was kinda scary, but enough wine will allow you to do about anything. I figured the worst case was I had to go to the VZW store this morning and get a new one.
Z
Thank you for this agent_47.
Nice to see you here as well Z.
MordyT said:
Thank you for this agent_47.
Nice to see you here as well Z.
Click to expand...
Click to collapse
Amen Brother !
Great work guys!
why is it that everytime i try to run this, i get an error 240?? i tried everything, and i just cant get it to work.... please help me out someone...
raysaboy said:
why is it that everytime i try to run this, i get an error 240?? i tried everything, and i just cant get it to work.... please help me out someone...
Click to expand...
Click to collapse
Do you have HSLP?
What's HSLP?
Is this the Hard SPL unlocker? (So many acronyms... I'm trying to figure things out before I leap )
I am not sim unlocked (do have HSPL), so I can't flash a radio, can I still use this?
HELP
WTH....i flashed task 29 on tp2 ... and reflashed wolfs rom, and all it says its TOUCH PRO 2 when its turned on. How do i get out of this situation, because this task 29 thing isnt working to well
jlove85 said:
WTH....i flashed task 29 on tp2 ... and reflashed wolfs rom, and all it says its TOUCH PRO 2 when its turned on. How do i get out of this situation, because this task 29 thing isnt working to well
Click to expand...
Click to collapse
It won't boot because there is probably no radio. Manually put your phone in bootloader. Connect to p/c and flash radio.
___________________________
solved
Question
I'm Hard SPL unlocked, but not SIM unlocked. Can I still run Task 29 and flash a stock Sprint radio? I've been reading that I can't flash a radio to my TP2 unless I'm SIM unlocked?
Do I need a radio if I use Task29 or can I use the radio I had already on my TP2 which was the stock Sprint CDMA radio?
if I need a radio, where can I get the stock Sprint CDMA radio? Then do I perfom the setup in this manner?
1. Run Task29
2. Enter Bootloader
3. Flash new radio
4. Enter Bootloader
5. Flash new ROM
Thanks
Deltatristar500 said:
Do I need a radio if I use Task29 or can I use the radio I had already on my TP2 which was the stock Sprint CDMA radio?
if I need a radio, where can I get the stock Sprint CDMA radio? Then do I perfom the setup in this manner?
1. Run Task29
2. Enter Bootloader
3. Flash new radio
4. Enter Bootloader
5. Flash new ROM
Thanks
Click to expand...
Click to collapse
sounds about right
here are some stock radios
http://forum.ppcgeeks.com/showthread.php?t=9034
may b i might sound like a noob but want sumone to throw a light on this.
i have a sprint cdma tp2 n its is sim unlocked. i m using it with a gsm sim,
i wanna know tat if i do task 29 n update any radio will it lock my phone,
which radio can i try..
Hey,
My TF101 got bricked by a simple reboot - "encryption unsuccessful" splash screen.
I used the nvflash-package from the devel-section "[Tool] Nvflash unbricking released!" for getting back a fresh, clean install of 3.2.1, which seems to work well.
Sadly, no OTA-Update to ICS is found and no microSD-Update is recognized.
Wipe, another cold-boot tried.
Q:
nvflash repartition and format - thus there couldn't be hassle with my old "broken" Android, right?
Q2:Anyone has an idea why updates dont work? Within the thread mentioned above I found some posts about updates which where recognized.
Searched a lot but nothing specific to the nvflash image solution...
BR / Adarof
NvFlash the RougeXM touch recovery CWM and use that to flash a new ICS firmmware/ROM. That's probably the easiest route to take. You can flash total stock that overwrites the custom recovery if you'd like too. Should fix your ota problem too.
removed
Okay, I have flashed ww-9.2.1.11-CWM-full-rooted.zip.
Wipeing everything tried.
But still no updates...
I found http://forum.xda-developers.com/showthread.php?t=1655976, which are the same log-entries like I found
But no luck on googling further on
If you have anything but a stock recovery, you will not get an OTA. You need to here to get the stock recovery and flash it through CWR. Then when you boot to recovery, using the power+vol down wait to see the text at top right corner and then hit volume up, method, you'll see an android laying on his back with a ! above him. This is stock recovery. Should be able to push OTA through settings after this.
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Thanks again so far!
BR / Adarof
adarof said:
Wohu - Thanks, thats one of the very gernal infos I missed :-/
I tried your mentioned tutorial. The process itself seems to be fine.
But...still no updates (it takes ages for the 1st update-check and is very fast for the 2nd and ongoing checks)
Click to expand...
Click to collapse
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
adarof said:
I'm from Germany, thus I would expect to require a firmware and recoveryimage for DE but the tutorial just links a WW for firmware and just US for reecovery?
Click to expand...
Click to collapse
All you need from that link I posted above is the SURecovery image and nothing else. You can get the firmware.zips from Asus directly. The SURecovery is universal, meaning it will work no matter what region you are in. It is the ROM/Blobs that are region specific. Don't forget that if you download one from the Asus site, that you need to extract it first and then push the zip that was inside the original file you downloaded.
So it would look like this WW.zip->extract->firmware.zip<<<---This is your ROM
adarof said:
Well ... DE has gone to WW since .21, thus I tried ... but the process uses a repacked Android3, thus I should care about DE ?
Might this be the reason? Is there a repacked-CWM-enabled firmware-image with recovery for DE?
Click to expand...
Click to collapse
Not sure about these questions.
Woodrube said:
When the file goes to update, it will fail if there are any apps missing from /system/app that ASUS put in there. There is a checker that looks for these app. If you deleted any of these or any were deleted in the CWR version you flashed earlier, you'll have to replace them before the update will install.
Click to expand...
Click to collapse
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Woodrube said:
All you need from that link I posted above is the SURecovery image and nothing else.
You can get the firmware.zips from Asus directly.
Click to expand...
Click to collapse
SURecoverty means the USRecovery.zip, right?
So, in summarize
1) Rogue XM Touch recovery via nvflash from http://forum.xda-developers.com/showthread.php?t=1446019
2) Use RogueXM to flash original asus-firmware (decompressed download archive)
3) Use RogueXM to flash USRecovery.zip from http://theunlockr.com/2011/11/28/how-to-unroot-and-remove-cwm-recovery-on-asus-transformer/
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
I assume the RogueXM requires a blob-File within the zip, which is not provided by asus-original-downloads?
A bit confused ;-)
BR / Adarof
adarof said:
Okay, I havent known this either...
Is there a list of asus-default installed apps? I havent found :/
Click to expand...
Click to collapse
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs. That way you'll be able to extract the apps from them and push to /system/app on your own (don't forget to set permissions also on the ones you push). If not, I will see if I can pull them from mine, zip them up and them send a link to you, but that won't be until I 1 get home and 2 get some time which unfortunately won't be tonight.
adarof said:
SURecoverty means the USRecovery.zip, right?
Click to expand...
Click to collapse
Yes sorry about that. I was typing too fast. :/
adarof said:
Am I right?
...on 2) I get
Code:
assert failed: write_raw_image("/tmp/blob","staging")
E: Error in /sdcard/WW_epad-user-9.2.1.24.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
adarof said:
...but I could install the repacked-8.2.3.13_WW+root-CWR-update(su_removed).zip.
Click to expand...
Click to collapse
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways. You can root it (if you lose it somehow) with Razerclaw since it is HC.13 (if you accidentally update all the way to ICS .11 without rooting, you can use ViperMod or any of the other root tools out there) Remember that once you root it, you can use OTA Rootkeeper to preserve your Root status, accept the OTA and then restore Root (this is what I have done since HC). Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
I would then uninstall the Recovery Installer to make sure you don't accidentally hit it and you are back where you started. But you'll have the APK to reinstall whenever you want later on.
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Edit::: Check this out too.
Woodrube said:
That is a tough one. i would suggest looking at the OP's for the custom ROMs and see if the have an Add-on pack that will put them in their custom ROMs.
Click to expand...
Click to collapse
Well, Ok...since I "just" would like to have back a real stock system, with OTA - there should be another way ;-)
Woodrube said:
This is the 3rd Status 7 I have seen today from someone. The other two were in my phone forums and it is bc of a mismatched CWR version. In my phone forum, they just needed to flash a different kernel. Not sure what is going on with it here, but see below...
Click to expand...
Click to collapse
Okay! This explains why I cant find any 1000000 hits on google related to my prop, which seems to me rather "simple" in principle ;-)
Woodrube said:
If you can get this far, then NVflash this and get it to boot up completely. That way you shoudl have all the /system/apps anyways.
Click to expand...
Click to collapse
Agreed...apps should be there. But even the Asus storage app was missing? Thus no stock-apps included?
Its an old Andoroid 3.0.1 and it wouldn't find OTA updates - thats correct?
Woodrube said:
Then install this app and flash the USRecovery.zip and you should be good to go. Reboot to full boot up and then try to reboot into recovery using Key Combo. It should throw the Android on his back with ! above him.
Click to expand...
Click to collapse
Okay, while Power-VolDown -> VolUp (this gave me Rogue XM before but since I installed USRecovery it was overwritten, right?) -> a Droid on its back with a "!" comes up.
...and now?
The .24 update on SDCard is recognized but when I try to install the knocked-out droid with "!" comes on reboot again and next reboot yields to a popup "failed update, reverted to old system" or so.
Woodrube said:
Sorry for the long post, just trying to cover everything bc I have log out for a bit and won't be on until later on. Maybe Thing O Doom will swing through, though.
Click to expand...
Click to collapse
THANKS for your time so far and dont stress anything
I really appriciate it! Im feeling lost on android...even I work with Linux/Unices since a decade or so :-/
Woodrube said:
Edit::: Check this out too.
Click to expand...
Click to collapse
Thats a Win-solution :-/
Most propably I need a stock DE .21 or WW .24 , repacked for flashing with CWM ... right? But that doesnt exists?!?! Cant imagine...
BR - Adarof!
Im still on this problem and have no idea - searched a lot, but havent found any real howtos for DE-tf101 for unbricking.
So my main thoughts are about this Error7, which is really ...strange.
I could flash the repacked, which is available for .11. But I dont have a change to get anz further...
I SHOULD be able to flash a original asus stock Firmware with the Rogue XM Touch recovery, right?
Since Im not able to ... should I try an older version of Rogue XM?
BTW: Is the region info somewhat hard-wired thus it couldnt be changed?
BR - Adarof
There's a WW .24 available for tf101 and I'm making a 9.2.2.6 for the Tf101G,
so there is the latest FW available.
If you are flashing, then that means you have a custom recovery. That is why no OTA.
I'm mobile now but IIRC from before, you flash a working CWR version of the ROM. Thne boot up. Then flash the stock recovery. Then you should be able to OTA after that.
Just make sure whatever ROM you flash is full. If you can nvflash that would be better and then put stock recovery in after your first boot.
Thanks to both of you!
@Woodrube: Flashing means using RogueXM...
Summary:
1) Rogue could flash me either CWR/rooted images or the repacked one - both without OTA.
Just RogueXM is left as bootloader, which shouldnt prevent OTA?!
2) Rogue gives Error7 on flashing the asus-downloaded-onetime-depacked-firmwares, doesnt matter if the DE.21 or current WW.24. :-/
Trying to make the long story short:
For comming back to a "known" system I would like to really go back to a stock system.
I conclude that using nvflash would be the best for this, right?
But where do I get the img-Files for flashing using nvflash?
I just found one package which included a download.sh: It repartitioned, formated and installed a WW android3 (3.2.1) version and deleted the RogueXM. It mentioned its a stock firmware (thus should have all apps).
Sadly no updates afterwards...
I think it could be since its the WW version and I would need a WW .21/.24 (since 21/24 dont distinguish DE and WW anymore) or an older DE-version. But for nvflash I need the img files of these firmwares, which I dont find. ...
Maybe you could simply point me to such img files for nvflash, please?
BR / Adarof
Finally I managed to borrow a win pc and thus could give EasyTool of your posting #8 a try: http://forum.xda-developers.com/showthread.php?t=1688012
After some hassle with the driver I managed to flash asus stock download DE_epad-user-9.2.1.21, which is "DE_Special" for coming to WW of german tf101s. the tf was wiped and boots just fine - it states that it has
IML74L.WW_epad9.2.1.21-20120413 - as I think is fine.
Sadly no update again:
The OTA doesnt find any.
The microSD recognizes WW_epad-user-9.2.1.24.zip, but during rebooting I get the Droid with ! and after another reboot a popup with something like "update failed (12)" (in german Systemaktuallisierung fehlgeschlagen (12)). It mentiones that the new version in not compatible ...but ....the .24 is for the DE_special .21 the next ... ?!
I could flash the .24 using Easytool, but this would mean to loose always all data for an update ....
Installing rogue still gives error7 on flashing stock (once decompressed) .zip
I've been reading and Rouge gives errors with stock otas X.x
You can manually install the stock blobs with adb shell, but they will overwrite recovery and etc..
If you want total stock you need to NvFlash, and for whatever reason your tf does NOT like updates.
Rouge V1.3 will take otas, if you don't mind the downgrade.
Thanks for the hint - but I was to lazs to install the rogue 1.3.
I found a .zip, which I tried to install by Rogue 1.5 hoping for a downgrade overall, but during installation it stated "Returning to recovery" and still 1.5 was installed .
What I finally found is a ww-9.2.1.21-to-9.2.1.24-CWM-v1.0.zip image.
I installed this using rogue 1.5 and got a clean .24 installation.
So I'm using this installation hopeing either
1) OTA will work, if asus releases .24++ or
2) I find an ww-9.2.1.24-to-9.2.1.24++
Still I dont get why the EasyTool .21 installation yields to a non-OTA state ... but ...
So, THANKS all of you for your support and hints!
I'll come back here and report further on, if .24++ is out
BR / Adarof
bad luck
....meanwhile my tf101 has started to ignored the dock battery, while the keyboard still works. I tried cleaning ....no luck, the dock battery does not come up within the menues ...
Thus it was returned and I'm waiting for repairing or refunding ...
BR / Adarof
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
So i have a STOCK HTC_M8Wl and a while back I tried to update it and this happened. The phone is no longer activated I've wiped data and cache from recovery mode I can also get into bootloader mode. When I attempt to power on the phone it shows the HTC boot screen for a min then turns off and back on to the same screen and after a minute or two it goes to a black screen then displays the phone with a red triangle and exclamation point in the middle then stays there.
I've looked all around the Internet and found this problem commonly with rooted devices but my problem is that mines is not rooted and is 100% stock. Is there a way to fix this problem from my position please let me know because I would love to make a thread on this problem because I only found one and they never explained how to fix it. (I belive it was the problem as mines) also I don't know much about HTC phones I have worked with rooting android before.
My solution:
Thanks to izzaeroth and the thread he provided me I was able to revive my phone. The ruu zip file kept failing saying signature verification failed do to large img file. So I decided to try the 6.0 ruu exe file instead. (My pc does have drivers to detect the phone while it's in fastboot mode) I launched the exe and it extracted the ruu I plug in my phone and started the process. It flashed all partitions it did take a while to load but after the update the phone booted it began to optimize 226 apps after that it booted and done it finally was fixed.
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
did u power it off while trying to update? you might be able to use one of dottats fuu/ruu files to try and bring it back to life
Click to expand...
Click to collapse
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
-spektor- said:
Yes I belive it did turn off while updating that's what I was told. But how do I fix it with the dottat file? I have OTA update files part 1 and part 2 but I always get the status 7 error.
Click to expand...
Click to collapse
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Sent from my m8wl using XDA-Developers mobile app
izzaeroth said:
you need to go here: http://forum.xda-developers.com/showthread.php?t=2883845
you will need the marshmallow 6.0 file, you might have to use the zip version, option 2. read instructions carefully etc etc
Click to expand...
Click to collapse
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
-spektor- said:
I've downloaded the 6.0 zip file but when using method 2 it said the file was to big n I downloaded the file again to make sure the file downloaded correctly n then it was a signature or a verification issue flashing it via HTC fastboot didn't seem to work either, I can't currently do much do to no Internet connection. So I cant keep re-downloading files to check.
Click to expand...
Click to collapse
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
It said it in fastboot when ever it detected the file n I think it said the same when i tried it with adb/fastboot on windows pc
izzaeroth said:
hmm, where did it say file was too big? not sure on doing it thru adb commands as ive always used the sd card or fuu
Click to expand...
Click to collapse
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
-spektor- said:
The 6.0 run exe worked it took a while to update but it worked and finally got past the same screen and it started to optimize apps that took a good 30 min ill update this thread when I get wifi again thanks for your help
Click to expand...
Click to collapse
awesome! glad u got it working