Yes but that doesn't help anything thx to ASUS' encrypted bootloader partition....
Excuse my ignorance but isn't that removed when you unlock it with the tool they provided?
Yes but that doesn't help anything thx to ASUS' encrypted bootloader partition....
Excuse my ignorance but isn't that removed when you unlock it with the tool they provided?
This is the sad thing about android.... I've always asked myself "why can you brick an android device in the first place"? Can't brick an apple that I'm aware of. You can't brick a microsoft machine, you can always get back windows. It just boggles my mind!
Someone please enlighten me!
Excuse my ignorance but isn't that removed when you unlock it with the tool they provided?
Just curious if the devs think it will become possible to unlock (a Honeycomb version) and install a ROM from the microSD card.
In early January I bricked by Prime where it won't boot up. Because it doesn't boot to the home screen, the device doesn't mount the drives. As a result, I don't have access to use ADB.
I just want to know if it's worth waiting, or if I need to RMA the device back to Asus.
Thanks!!!
Sounds like a software brick. Can you access the stock recovery? If so then you could flash the stock ASUS firmware.
Sounds like a software brick. Can you access the stock recovery? If so then you could flash the stock ASUS firmware.
MasterZen88,
I can access the stock recovery. How do I flash the stock ASUS firmware from there? The only options I am aware of require ADB access to move the blob file using the dd command or launched from Settings/Check for System Update screen.
Update: I probably want to make sure we're clear on access to stock recovery. I can get into the area where I can wipe data and perform a cold reboot. If I press Vol+ instead, I get Android with an exclamation point.
anthonyalberto helped me out. The trick is that the firmware installed from the microSD card must be a later version than the one installed on the Prime.
Thank you very much for your assistance.
Hey could you pass that information along im having the same issue n i cant use the recovery due to the red exclamaiton point.
is there a specific name that we have to rename the firmware file.im still on 9.4.2.13 if someone could help it would be much appreciated. if its like anyother stock recovery the file has to be renamed so.
~globed
I will explain my specific situation as a reference to everyone.
At the time ICS was released in January, I was one of the folks who had trouble with the firmware upgrade to ICS. There were workaround suggestions posted on the forums. I attempted one of the procedures and it bricked my Prime. At the time, no options were available to unbrick the Prime. I didn't have access to ADB because the Prime would hang during the boot up process. The boot process was not getting to the home screen, so I had no option to reflash. As an aside, I purchased another Prime and held on to this one waiting for the unlocked bootloader. It turns out I didn't need too wait...
The firmware version I was on was 8.8.3.33 (Honeycomb 3.2)
What I had been doing was:
1) Download the 8.8.3.33 firmware (I only did this once)
2) Extract the UpdateLauncher_US_epaduser8_8_3_33.zip file
3) Inside the extracted UpdateLauncher_US_epaduser8_8_3_33.zip is a zip file called: US_epad-user-8.8.3.33.zip
4) I renamed the file to EP201_SDUPDATE.ZIP
5) Used my PC to copy EP201_SDUPDATE.ZIP to my microSD card's root directory
6) Inserted my microSD card in the Prime
7) At the same time, I pressed Power and Vol (-)
8) Once the text appeared in the lefthand corner, I let go both buttons, waited a second, then pressed the Vol (+) button.
The android animation would run for about 20 second, then come up with an Android laying down with an exclaimation point.
Based on another suggestion I read earlier today, I followed the same procedure, except instead of using the firmware for 8.8.3.33, I used 9.4.2.7.
In 9.4.2.7,
1) I extracted the file contents from the US_epaduser9_4_2_7UpdateLauncher.zip file
2) Located the US_epad-user-9.4.2.7.zip file
3) Renamed the US_epad-user-9.4.2.7.zip file to EP201_SDUPDATE.ZIP
4) Copy the EP201_SDUPDATE.ZIP to my microSD root directory
5) Then ran the same procedure as outlined above.
It appears the Prime checks if the version of firmware is newer than the one already installed. It worked like a charm.
In your case, I recommend downloading 9.4.2.14 from the ASUS support site and attempt the procedure. Make sure you use the microSD card and not the /sdcard directory on the Prime.
Let me know if you have any other questions.
Okay we successfully un-bricked a Brick 3 just now.
Updating the thread tomorrow.
Me too
ASUS did really screw up this unlock thing... Almost nothing works, everything brick your Prime etc
Not sure if you have the same problem that I had(stuck at eee pad screen with no access to recovery). I used fastboot to flash recovery and stock boot.blob to resolve the issue.
stuck on Brick options 1a
adb devices cannot see my device
does not show up in device manager
But I do have at other devices "Full Android on Emulator"
Any Help
Thanks