Related
*** SOLVED ***
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Psychlone said:
Hey all.
So I've had my A500 for about a year now and it's been on several different ROMs and kernels over that time.
Most recently, I was running Flexreaper R12 (I believe) and ICS was running very smoothly.
At some point a few months ago (after a Flexreaper update), I was experiencing the Sleep Of Death and flashed an AntiSOD kernel to stop it (which it did). All this time, for some reason or another, I never updated the bootloader past the Honeycomb bootloader - and that's where I'm stuck right now.
I've tried using AfterOTA in every possible way to get anything else loaded.
I've tried Blackthund3r's A500 APX Flash Utility with at least 7 different APX packages, but no matter what I try, I'm still stuck with Flexreaper and the HC bootloader.
FWIW, both AfterOTA and the A500 APX Flash Util experience a problem with my A500 when it reboots. Most of the time I can get the device to be recognized by my OS (Windows 7 x64), but sometimes it doesn't and fails on driver install, even though I've installed the Google drivers direct from the SDK as well as Acer's drivers (USB_Acer_1.00.0524_A30H_A31H_A32H_A500_A501).
I'm pretty sure this is a driver issue, but I'm unclear on how to fix it. I've uninstalled ALL drivers related to the A500, rebooted and reinstalled them, I've uninstalled them and then pointed the installer directly to the unzipped USB driver folder (from above), but it seems that at some point the device fails to be seen, only rarely - but it's this that I think is the main problem... or I'm missing something.
So, any advice for someone that's STUCK on the old 3.01 bootloader?
Psychlone
Click to expand...
Click to collapse
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
gears177 said:
i was stuck to so i downgraded got the ics bootloader from the ota and then used afterOTA to get the unlocked version and it worked
Click to expand...
Click to collapse
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
if your on the honeycomb bootloader simply flash a honeycomb rom and kernel no need to use afterOTA or anything else if i remember correctly
Psychlone said:
So how did you downgrade? I've done everything I can think of - at least 6 times over...
That was the plan after I figured that downgrading back to stock and then going up from there was the only way, but I can't even go back to Honeycomb 3.2 or even 3.1.
Check this out - I even made sure to make a CWM backup of my original setup before I upgraded to 3.2 back almost a year ago...but I can't get it to restore. In fact, I made several different backups and can't get ANY of them to restore.
So, in short, what did you do to go backwards?
Psychlone
EDIT: when I try to get into APX or Bootloader, it always ends up in Thor 1.7 and my computer doesn't recognize the device with a device driver install fail for MTP USB Device, even though I've installed the Acer Recovery drivers and the Google SDK drivers too... wtH?
Click to expand...
Click to collapse
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
dibb_nz said:
you got a couple of choices....
with the HC Bootloader and ics rom...
full wipe and flash an HC rom or
nandroid restore an HC backup or
flash an update.zip
as a last resort - a complete downgrade/rollback use timmydeansv4 EUU - just be sure to follow the instructions in jazzyjames post on how to roll back - iu dont wanna get it wrong and end up stuck in apx mode. If it doesnt work first time....STOP...disconnect yr data cable and reboot tab and pc, use a different USB port and try it again....
Some folks have had issues with win64 so if you are able to then try on a different pc
sometimes a restore wont work unless you restore it with the recovery you used to back up with in the first place which may have been cwm 1.3.4 in your case....maybe???
as far as the MTP driver goes...that can be a pain...i had the same trouble a few days ago on ICS...took ages to get installed....and i still dont know why it did....or why it wouldnt....very frustrating!!!
Click to expand...
Click to collapse
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
gears177 said:
he's not on the ics bootloader though so couldn't he just flash the 3.01 unstable and get the OTA? or go back to a stock rom in general?
Click to expand...
Click to collapse
Yeh 2nd line of my post hc bootloader ics rom, and u correct use 3.01 buggy update,zip or stock update.zip I shoulda been clearer - thanks gears
Thanks guys, I really do appreciate the help, but I'm still having serious issues reverting back to HC.
I feel like an idiot, but I have to say that even though it seems so, I'm actually the owner of a computer repair business, have 28 years experience in PC/Mac repair, and have rooted and modded every android device I've owned (including some for friends as well) - all the way back to the very beginning with the D1. This, however, has thrown me for a loop. NOTHING with this A500 has been this complicated! Everything up to this point has literally been stupid-proof and I've actually been quite impressed at just how easy modding is on the A500...
Anyway...
Here's what's going on and what I've tried today:
I've tried unsuccessfully several times to get ANYTHING working on my laptop, but to no avail. Same story as last night, no progress whatsoever - however, I did note that with CWM 134, I was able to restore an earlier version of ICS 4.03 (Flexreaper R10 I believe) - but it wasn't easy... I ended up restoring the main image and then using parts and pieces (using Advanced Restore) from other saves to finally even get it to boot.
This clearly wasn't getting me anywhere, so I moved the entire operation to another computer - my main rig (also a Win7 x64 - in fact, I don't own a computer that's not Win7 x64)
Now I've got USB driver issues! I can't even install the standard USB drivers from Acer's website because the installer errors out saying that there's no version of Acer Iconia 3G Driver Install is installed. wtF? That's what I'm TRYING to do!
I did get a different USB driver installed - the USB Driver_Acer_1.06.1500_A30H_A500, but nothing wants to use it and Blackthund3r's APX Flash Util won't see it, AfterOTA won't use it, and it's basically useless anyway. AND I can't install the Acer_1.00.0524_A30H_A31H_A32H_A500_A501 drivers no matter if I've got any others installed or not.
In my device mangler, there is no device with an exclamation, and in fact, sees my Acer Iconia A500 under USB Serial Bus Controllers as "Acer Picasso USB Boot-Recovery Driver", only when it's plugged in. NO other instance shows up at all.
I'm actually at the point of trying to follow through with the EUU (dibb_nz's "last resort"), but vache's website is down and I can't download anything for it. In fact, there's nothing from that guide that has a valid link...
(http://forum.xda-developers.com/showthread.php?t=1632392)
So now where do I go? I understand IT really well, so you don't need to talk to me like a complete noob, but dang if I can't figure this one out!
If I can get valid links to all the downloads from the link above, I'd be more than happy to give it a go and see if that works, but I can't piece together all those things from random places. If either of you (or anyone else for that matter) has valid links for everything needed to follow the EUU guide, I'd be very grateful!
Any other advice would certainly be appreciated as well! I don't have to use either of these computers, but as mentioned, ALL of my computers have Windows 7 x64 on them. I suppose I could try one of my customer's computers for all this, but that's not morally right and probably something that I would prefer not to explore.
I feel as if I could get the USB drivers installed properly on EITHER machine, that I'd likely be in good shape. I think that's what my problem actually is on the laptop as well, even though they're all installed and shows as installed until I boot into any recovery - then I get the MTP Device Driver Fail. There's likely other Acer driver issues there though, since Blackthund3r's utils don't follow through for anything... everything just hangs. AfterOTA just hangs.
Advice please?
And thanks again for your knowledge!
Psychlone
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
dibb_nz said:
Yeh I hear u m8, its taken me all nite and day to revert back to HC and then upgrade again....dam pesky Picasso drivers.....
why not do as gears suggested....boot to cwm do all the wipes and formatsand flash an HC rom, ezterrys has a rooted one...no drivers needed . or am I missing something?
D/l link for timmydeans euu in my cpuid thread
Click to expand...
Click to collapse
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
EDIT::
OK, so I'm really in bad shape here - now the EUU (PBJ20upgrade) comes back with the error:
Please download the newer image for the upgrade.
Current image version: Acer_AV041_A500_1,054.Acer_AV041_A500
New image version: Acer_A500_1.016.05_Com_GEN1
What now????
Psychlone said:
Well, I would but no matter what image I put on my SD or even internal SD, and no matter what recovery I use, there's always some type of fail - usually an MD5 fail, or just a fail without any error code at all (little android on his back with the red exclamation, but no code)
I'm clearly missing SOMETHING.
I'm about to try the EUU right now unless there's some other advice...
Click to expand...
Click to collapse
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
dibb_nz said:
oh hell now i'm confused, lol.....the little android dude is the acer stock recovery....i thought you had thors 1.7...oh well, nvm
Hopefully the EUU will install the right drivers for you....just be sure NOT to connect your data cable until u see the "cannot detect yr iconia tab" screen and it will give u instructions on how to get into apx mode...oh just before that window the EUU will try and scan your system image it will take a good 5 mins b4 it pops up the window to go into apx don't panic just let it do its thing....good luck m8!!!!
Oh and this will completely wipe yr system and user data.....
Click to expand...
Click to collapse
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Psychlone said:
Some of the WEIRDEST stuff I've ever experienced - EVER.
Oh, the little dead android is when I'm using the stock recovery - I get different errors in TWRP and all the CWM Thor's that I've tried...(134, 71 and 712)
OK, so now PBJ20upgrade won't let me advance because apparently my CPUID isn't correct... it's the ICS version that's 13 characters long instead of 15, and my dmesg doesn't even contain the word "androidboot" at all (it does, however, contain a crapload of errors.)
What's going on?
OK, I'm an idiot. I really need help. I'm just glad that I'm 40 and don't lose my cool anymore, otherwise, I'd be freaking out about now.
Click to expand...
Click to collapse
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
THANK YOU!
dibb_nz said:
cpuid = 15/16 chars go to one of yr cwm nandroid backups theres a uid.txt file in the folder all the other methods rely on adb??? if not try usbdeview thats in the thread too
Click to expand...
Click to collapse
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Thanks again,
Psychlone
With what I went thru use Civs nvflash and rom and I'd stick with third cement until your safely patched and on ics.do all the wipes and follow instructions to the letter ...I'll check back in shortly
EDIT wtf "third cement" dang auto correct ... should read thors recovery
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
excellent news glad it worked for ya
Psychlone said:
Thanks so much dibb_nz... I've currently got PBJ20upgrade doing *something* (says it's going to take 10 minutes)
Thing is, I didn't get to this point by any conventional means - I followed the destructions several times over but ended up having a newer image than PBJ wanted, or the wrong CPUID.
Click to expand...
Click to collapse
if its referring to newer image then the data cable is connected!
and it will spit this error at you....
I finally got this far by unplugging the tablet while PBJ was running, waiting for it's long error and instructions on how to get into APX (which I've clearly done at least a couple dozen times by now) and for some reason when I plugged it in, it shot forward.
Click to expand...
Click to collapse
yup now you're cookin
We'll see how this goes - I'll keep you posted. I do VERY MUCH appreciate the help. I just might still need it, but hopefully not.
EDIT: Just rebooted and saw a "PASS" on the screen, followed by the "android" loading screen.
EDIT 2: It rebooted all the way in, I signed in (did the entire sign in process) and I'm BACK TO STOCK!!!!
Click to expand...
Click to collapse
oh yeahhhhh!!!!
Ok, so thank you THANK YOU THANK YOU for all the help - just being a sounding board is all I need sometimes.
Click to expand...
Click to collapse
nps glad to be of assistance -
Last questions to get me set up for the future:
What recovery should I create a restore with?
Then after creating a restore, should I use Blackthund3r's utility to flash an unlocked ICS bootloader, and if so, which package should I use to be able to test JB but still be able to go backwards to an ICS (preferably CM9)?
Anything else that I might need to know? (keep in mind that I've read on the order of 30 different threads pertaining to this adventure since it began a couple days ago, but I really appreciate the advice you've given and clearly you know what's up with the A500 - AND, it's hard to disseminate info from all the random threads everywhere. Speaking of which, why is it that there can't be a single thread with most everything that an A500 owner would need? Seriously!!)
Click to expand...
Click to collapse
becoz then you'd have thousands of posts to look thru and no-one would bother reading it all....i try to keep my cpuid thread updated with things 'unbricking' but its too hard to put 'everything' in one post unfortunately
---------- Post added at 07:01 PM ---------- Previous post was at 06:48 PM ----------
Psychlone said:
Wow - what a journey.
I'm now running CM10 and loving it.
I really can't believe the process that I went through over the last couple days - I've rooted and modded two dozen devices in the last year alone, and have been playing with root and modded ROMs since the very beginning, and nothing comes close to what I just did.
I actually have to blame not having everything I need in one place. Mis en place means to have everything you need before you even start - and that used to work back in the day, and still does to an extent for some devices, but anymore, the download links and information are found scattered across many different websites and forums and threads - so much so that it's apparent that this is a product of Google's lack of grip on their hardware and OS.
I do, however, see that you and a couple others have done a KILLER job of getting most everything together in one place to make it easier for those that are searching. I really appreciated your threads that I've read - the way you've written your guides is very intuitive and easy to follow, even if they didn't initially work for me.
Anyway, thanks again. I'm not going backwards now, but if I ever need to for some reason, at least I'm a bit familiar with the "worst-case scenario"!!
Take care man,
Psychlone
Click to expand...
Click to collapse
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
dibb_nz said:
excellent news glad it worked for ya
hell, i havent got round to cm10 yet!! i'm trying to get there but i have too much fun helpin peeps get to grips with flashing BL's...have to really thank the devs they did an awesome job unlocking ICS so everyone can enjoy the custom ICS/JB/CM roms- they've extended the life of our little iconia an extra half year or so if not longer.....imagine if we had to put up with stock 'anything' lol, i'd have traded it in long ago!!
was about to suggest the apxflash bundles as there are alot more options as far as recovery's go but you're all sussed now so thats fantastic....
can u add "SOLVED" to the title in case someone else is looking for help. thanks m8:good:
Click to expand...
Click to collapse
CM10 is SLICK. Think CM9 on graphics steroids and you're close!
I appreciate your position more than most. I get a lot of enjoyment out of helping others as well - I've written overclocking guides for AMD systems that was written years ago, revised a couple/three years ago and is still used to this day, even though I've long since moved over to Intel's "dark side". I also participate pretty deeply in helping others at a couple PC hardware forums pretty much daily, even though that's my actual job - I own 2 computer repair businesses in my hometown, and with well over 20,000 computers to fix, I'm ALWAYS busy but still always find time to help others in need.
As for adding ***SOLVED*** to the title, I'd love to...but it won't let me. Perhaps it's because I don't have a high enough post count, or because it's reserved for Mods, but I can't do it.
Thanks for everything once again - it's quite refreshing to be on the receiving end!
Psychlone
Hey,
first of all: my Acer Iconia A500 is not rootet and I have no custom rom installed. It's all "original" and I don't want to do anything, that kills my warranty.
Yesterday I tried to upload some videos to youtube using "Google Chrome"-browser, but the Tablet crashed when I tried to open the directory where the videos are stored in.
In the top left corner of the screen was written something about a "mounting recovery image" or something like that (I can't remember). After that the tablet restartet but it won't go any further than the "acer"-logo.
I tried a few things I read in the forums but nothing helped:
pressed the "reset"-button at the bottom right side with a needel: tablet restartet but hangs again at "acer"-logo
pressed the "volume down"- and the "power"-button at the same time an released the power-button when the screen turns on: some writings in the top left corner of the screen (something about erasing cache... I could not read it because it disappeared to fast), then an Android-Symbol with some kind of cube in front ob the belly, then an Android-Symbol lying on the back with a red exclamation mark symbol on top of it.
pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Now I really need some help... what can I do to make my tablet work again?
Thanks in advance
Multicoder said:
Now I really need some help... what can I do to make my tablet work again?
Thanks in advance
Click to expand...
Click to collapse
Go Here;
http://forum.xda-developers.com/showthread.php?t=1816560
Take a look for the ICS UPDATE files for the a500. Might be 3 or 4 of them.
Download them to your PC. DO NOT EXTRACT
You may or may not need to decrypt them first. Should be a Decrypt tool on the same thread.
After decrypt, open the rom.zip with 7zip (or similar zip program) Again, DO NOT EXTRACT. Just pull the update.zip out of it. Copy it to your ext sd card.
Holding Vol+ and PWR, boot the tab and remain holding untill you see the install start.
Now, you may have to try more than 1 of those update roms. But one of them should work.
Should get you going. If not,. your bootloader partition may be hosed and need acer repair.
Oh, and you will more than likely lose most of your data, so don't be surprised if some fotos and such are missing.
MD
I have the same problem as TS.
Trying to solve this but i can't find a decrypter.
You say it in the same thread some where, but it reads "coming soon"
Please help
Acer Decrypter
Here is the Decrypter tool.
Unzip the contents to a folder. Select your rom.zip
Decrypt it. New file will have the word "decrypted" in the file name.
Takes a couple of minutes.
MD
Thanks.
Sadly it doesn't work for me.
Nr 4 the one that doesn't have to be uncrypted seems a bit to work.
My tablet starts up with the acer logo and then i see flashing "ANDROID" for 18 seconds then 2 seconds blank screen then the flashing android again.
This goes on and on, i have let it go for about 2 hours but nothing changes.
Anyone any idea?
help please
papafrank said:
Thanks.
Sadly it doesn't work for me.
Nr 4 the one that doesn't have to be uncrypted seems a bit to work.
My tablet starts up with the acer logo and then i see flashing "ANDROID" for 18 seconds then 2 seconds blank screen then the flashing android again.
This goes on and on, i have let it go for about 2 hours but nothing changes.
Anyone any idea?
help please
Click to expand...
Click to collapse
This is what I would do if that was happening on my tablet.
First. I would get Blackthund3rs APX tool. Then I'd run it and follow the directions. Basically it goes something like this. Starting at the first screen of the APX Tool. Browse Bundles. Type in number 17 after getting the bundle list from the bundle market. Set it to be staged for flash. Enter your SBK. Use whichever BCT that you want. Enter APX manually, follow the onscreen prompts. and when you get to the end it will tell you to restart your tablet. But first... This next part is really important if you are on a stock rom. Reboot, but do so with the volume rocker pushed for entering CWM. ( The one on the left in landscape.) If you don't the rom will wipe the recovery that you just installed during the boot process and then you'll get to start all over. Once you get into CWM goto the wipe menu and do them all except the battery stats.
From there you can...
Reboot and see if the rom starts. (I'll bet that it will.)
Or you can flash any custom rom that you want/have, (put it on your sd card before you start.)
Or. If you want to go back to stock you could grab a 3.2 stock rom from the link posted above and install that. It will remove the custom bootloader and CWM. You will be totally factory stock after that.
Good luck.
Wow wait a moment.
I am a complete noob with this.
I don't know the you use and as you may have noticed; you're language is not mine language
Stock rom means the original rom ?
Going to search for the APX tool (whatever that means) and take a look.
Thanks sofar.
<edit> SBK is Secure Boot Key. How do I get this key</edit>
papafrank said:
Wow wait a moment.
I am a complete noob with this.
I don't know the you use and as you may have noticed; you're language is not mine language
Stock rom means the original rom ?
Going to search for the APX tool (whatever that means) and take a look.
Thanks sofar.
<edit> SBK is Secure Boot Key. How do I get this key</edit>
Click to expand...
Click to collapse
This thread by dibb_nz will have all that you need. http://forum.xda-developers.com/showthread.php?t=1751978. I am sorry that I was so long to respond. Please be patient and read carefully. She has links to every thing that you will need to do there.
Good Luck.
Thanks.
going to try it.
I give up, nothing seems to work.
Think i contact acer and send it to them for a repair.
Too bad cost me another lot of money
Anyway Thanks for your support, i learned a lot. :good:
papafrank said:
I give up, nothing seems to work.
Think i contact acer and send it to them for a repair.
Too bad cost me another lot of money
Anyway Thanks for your support, i learned a lot. :good:
Click to expand...
Click to collapse
U will need either "civato's manual nvFlash" or an "EUU" based rollback (timmyDeans V4) to repair the bootloader - once that's fixed u can flash a stock rom to get back to factory original. Links and guides in the cpuid thread - if u need further help, ask away I know it can be really frustrating and the no.1 cause is always 'drivers', once u can get them installed AND adb running correctly then you're halfway home!! One thing I've learned with the Acer is everything is built upon u following the guides in a strictly orderly fashion, try to skip a step or not complete the preceding step correctly will always result in failure BUT the error will not show up straight away - u might get 3 or 4 steps further along b4 error'ing out...which is why its so darn difficult to troubleshoot....the only thing these tools cannot fix is a hardware issue..if this is the case then it will need to be sent to Acer for repairs....good luck
Sent from my GT-I9300 using Tapatalk 2
Last week I sent mine to Acer and yesterday I got it back. Working.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Contacted acer, told about the problem.
The send me a mail with an UPS ticket and phone number.
Next morning UPS pickup the package and in one week a had my acer back.
Perfect. All for free
Kompliments to acer
Multicoder said:
Last week I sent mine to Acer and yesterday I got it back. Working.
Gesendet von meinem GT-I9300 mit Tapatalk 2
Click to expand...
Click to collapse
papafrank said:
Contacted acer, told about the problem.
The send me a mail with an UPS ticket and phone number.
Next morning UPS pickup the package and in one week a had my acer back.
Perfect. All for free
Kompliments to acer
Click to expand...
Click to collapse
Awesome news you 2!! And yes kudos to acer for coming to the party
Sent from my GT-I9300 using Tapatalk 2
Hello to everybody
I was delete all partion on my /dev/mmcblk0 and create a partition with out format.
Now my table a200 do not boot well, just says unrecoverable bootloader error 0x000000000004
how can I fix it?
how can I get acces to the emmc flash drive and reparticioning it?
Thanks
Acer A500 and believing in xda . . . right or wrong?
My past forum posts say it all with exception of this: (in essence: purchased new stock A500 16GB, forgot pattern, locked up during OTA two days before expiration of warranty Sept 2012 used xda developers suggestions for reset (update.zip) and today have nothing but:
Erasing Userdata... (in white on black screen)
Unrecoverable bootloader error (0x19000008) (red on black screen)
During my time trusting xda developers, I've encountered the full spectrum of online personas - both ends of the rainbow people. Regarding software, I found some interesting things in one of the (opened in "read only") "update.zip" files while just looking through the metadata and other files (I could open in notepad read only) hoping to find some useable reference and indeed found them tampered with. Not sure how you can police everything people post for our "help" but now wonder what my options are.
Not that xda could have forseen Acer rescinding the files, I missed the window of the Acer A500 stock rom last year and any reference now is either very old (2011), 404 - not found, or link to sites which install devious 3rd party software. I take precautionary measures hopefully relieving myself of risk but I'm not a tech. My tablet was not rooted nor altered in any way, just locked. I was able to download all my files with Mobogenie because obviously my keypresses were incorrect and all the information was retained on the tablet until last night. Last week, trying to reinstall a new version of the update.zip that didn't have the words "stupid user" and other code with null directives or whatever it's called in "code" lingo, in the binary file (opened in read only), and also before the wipe found a bootloader installed and how to explain is just too much. Is there a validated, quality reference one can use from xda developers that isn't compromised? Which someone with less than an Associate Degree and older than 15 can follow at this point?
I will donate out of my paltry SS income of 600 a month to whomever can lead me, step by step, to recover my A500 or find at this point it necessary to move on. :fingers-crossed:
Multicoder said:
Hey,
first of all: my Acer Iconia A500 is not rootet and I have no custom rom installed. It's all "original" and I don't want to do anything, that kills my warranty.
Yesterday I tried to upload some videos to youtube using "Google Chrome"-browser, but the Tablet crashed when I tried to open the directory where the videos are stored in.
In the top left corner of the screen was written something about a "mounting recovery image" or something like that (I can't remember). After that the tablet restartet but it won't go any further than the "acer"-logo.
I tried a few things I read in the forums but nothing helped:
pressed the "reset"-button at the bottom right side with a needel: tablet restartet but hangs again at "acer"-logo
pressed the "volume down"- and the "power"-button at the same time an released the power-button when the screen turns on: some writings in the top left corner of the screen (something about erasing cache... I could not read it because it disappeared to fast), then an Android-Symbol with some kind of cube in front ob the belly, then an Android-Symbol lying on the back with a red exclamation mark symbol on top of it.
pressed the "volume up"- and the "power"-button at the same time, released the power-button when the screen turns on and switched the lock switch on and off and on and off: top left corner of the screen says "Erasing Userdata... Unrecoverable bootloader error (0x19000008).
Now I really need some help... what can I do to make my tablet work again?
Thanks in advance
Click to expand...
Click to collapse
vivispix said:
My past forum posts say it all with exception of this: (in essence: purchased new stock A500 16GB, forgot pattern, locked up during OTA two days before expiration of warranty Sept 2012 used xda developers suggestions for reset (update.zip) and today have nothing but:
Erasing Userdata... (in white on black screen)
Unrecoverable bootloader error (0x19000008) (red on black screen)
During my time trusting xda developers, I've encountered the full spectrum of online personas - both ends of the rainbow people. Regarding software, I found some interesting things in one of the (opened in "read only") "update.zip" files while just looking through the metadata and other files (I could open in notepad read only) hoping to find some useable reference and indeed found them tampered with. Not sure how you can police everything people post for our "help" but now wonder what my options are.
Not that xda could have forseen Acer rescinding the files, I missed the window of the Acer A500 stock rom last year and any reference now is either very old (2011), 404 - not found, or link to sites which install devious 3rd party software. I take precautionary measures hopefully relieving myself of risk but I'm not a tech. My tablet was not rooted nor altered in any way, just locked. I was able to download all my files with Mobogenie because obviously my keypresses were incorrect and all the information was retained on the tablet until last night. Last week, trying to reinstall a new version of the update.zip that didn't have the words "stupid user" and other code with null directives or whatever it's called in "code" lingo, in the binary file (opened in read only), and also before the wipe found a bootloader installed and how to explain is just too much. Is there a validated, quality reference one can use from xda developers that isn't compromised? Which someone with less than an Associate Degree and older than 15 can follow at this point?
I will donate out of my paltry SS income of 600 a month to whomever can lead me, step by step, to recover my A500 or find at this point it necessary to move on. :fingers-crossed:
Click to expand...
Click to collapse
How bizarre, never encountered files like that here b4?? There's a root guide in my Sig you're gonna need to look at. All files there have been d/l'ed multiple times with never a complaint, so far!!
First off, an update.zip is of no use.
You need an nvFlash-based tool. Either a EUU like tdv4 or the infamous babsector.rar file.
2nd, you are gonna need yr cpuid. See cpuid guide in my Sig. Until you can retrieve it you're stuck with a brick.
Have a read thru those 2 guides. You'll have questions after that so just post back here
Sent from my HTC_PN071 using Tapatalk
Same issue, different divice
I've been looking for the solution to this very same problem, however, I have an Acer Iconia tab A200. After going through XDA I found that there is 0 on my device. Does anyone know of an outside source?
for Unrecoverable bootloader error (0x19000008).
use this solution https://www.youtube.com/watch?v=IIlaWqRYYJw ive tried it and it works ..just need patience...
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
ssvNormandy said:
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
Click to expand...
Click to collapse
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
9918
Moscow Desire said:
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
Click to expand...
Click to collapse
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
ssvNormandy said:
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
Click to expand...
Click to collapse
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Moscow Desire said:
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Click to expand...
Click to collapse
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
ssvNormandy said:
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
Click to expand...
Click to collapse
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Moscow Desire said:
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Click to expand...
Click to collapse
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
ssvNormandy said:
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
Click to expand...
Click to collapse
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Moscow Desire said:
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Click to expand...
Click to collapse
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
ssvNormandy said:
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
Click to expand...
Click to collapse
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Moscow Desire said:
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Click to expand...
Click to collapse
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
ssvNormandy said:
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
Click to expand...
Click to collapse
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Moscow Desire said:
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Click to expand...
Click to collapse
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
ssvNormandy said:
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
Click to expand...
Click to collapse
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Moscow Desire said:
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Click to expand...
Click to collapse
blackthunder's tool just WILL NOT RUN on the tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
ssvNormandy said:
blackthunder's tool just WILL NOT RUN on my tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
Click to expand...
Click to collapse
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Moscow Desire said:
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Click to expand...
Click to collapse
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
ssvNormandy said:
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
Click to expand...
Click to collapse
Yep, same issue with me. I'm stuck on 3.2 HC
Well, it's a secondary tablet anyhow.
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
ssvNormandy said:
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
Click to expand...
Click to collapse
Yeah, and a little bit of knowledge :laugh::laugh::laugh: (maybe too much)
Am glad I could help out!! :good:
Q&A for Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Where do saved files go?
Hello,
Before I bricked my N7 - I saved off all files per the instructions.
After the 'accident' - I can't find the files.
Can you tell me some of the usual locations that I can look - they are not under the \program files...\dir.
The tool told me the files had been saved off before I proceeded - I didn't double-check at the time since I thought all was well.
=== (from another post)
N7 Bricked
Hello,
My N7 bricked as well - stuck in APX mode. Don't know if the SBK is based on the CPU ID or not, and what the correct algorithm would be to recover it.
I did do a backup with NRT before all of this happened - but I can't seem to find those files at the moment.
I also got the 'too many links' message when I tried to flash the N7. It tried to boot; appeared to be running fine; and then did a screen blank; looked like one of the old
b&w TV's.
I did find the following mentioned elsewhere on this site - and I think it describes what may have happened when I was trying to get my N7 out of the infinite boot loop.
==
...the newly flashed BOOTLOADER inherits the crypto-signed details of the pre-existing BOOTLOADER, which exists (or FASTBOOT wouldn't work) and is 'tied' to that specific Nexus 7 via a unique ID.
But if the flash goes wrong, say as a result of a bad USB connection... the old BOOTLOADER is partially/wholly erased, the replacement may successfully flash, but FAILS to acquire the SECURE BOOT KEY (SBK) from the old BOOTLOADER.
The new BOOTLOADER then fails its crypto-sign in check against the Nexus 7's unique device ID when the device is next booted...
===
I did ask NVidia about this - they said I have to talk to ASUS. I have done that and they want $100 for the RMA. Since I got this N7 at the ESC 2103 Android Seminar/Certification Class -
I wonder if it'll cost more to fix once ASUS gets it.
Does anyone know how the SBK is generated for the N7? I get this with nvflash:
e:\NVPACK\Android_OS_Images\Pluto\android_k_pluto_ os_image-17.0r0>nvflash.exe --wait --bct
flash_encrypt_encrypt_encrypt.bct --setbct --odmdata 0x40098008 --configfile flash.cfg --
create --bl bootloader_encrypt.bin --go
Nvflash 3.10.1700 started
chip uid from BR is: 0x0000000000000000015d28569018120c
rcm version 0X4
Command send failed (usb write failed)
I encrypted bct and bootloader_encrypt.bin with this SBK:
0x76B66E00 0x6B991000 0x6362F302 0x9C266D03
but I do not know if that is accurate.
Does NRT have the capability to save off the SBK someplace? Just wondering.
===== talked to ASUS today - they want $200 for the RMA.
Thanks in advance,
jwestmoreland
jwestmoreland said:
Hello,
Before I bricked my N7 - I saved off all files per the instructions.
After the 'accident' - I can't find the files.
Can you tell me some of the usual locations that I can look - they are not under the \program files...\dir.
The tool told me the files had been saved off before I proceeded - I didn't double-check at the time since I thought all was well.
Click to expand...
Click to collapse
The files are saved onto your device, the instructions we provide then tell you to grab those files off your device and store them somewhere safe.
jwestmoreland said:
...the newly flashed BOOTLOADER inherits the crypto-signed details of the pre-existing BOOTLOADER, which exists (or FASTBOOT wouldn't work) and is 'tied' to that specific Nexus 7 via a unique ID.
But if the flash goes wrong, say as a result of a bad USB connection... the old BOOTLOADER is partially/wholly erased, the replacement may successfully flash, but FAILS to acquire the SECURE BOOT KEY (SBK) from the old BOOTLOADER.
The new BOOTLOADER then fails its crypto-sign in check against the Nexus 7's unique device ID when the device is next booted...
Click to expand...
Click to collapse
The newly flashed bootloader doesn't inherit anything. The bootloader is encrypted with the SBK during the flashing process. The SBK is handled at a lower level (from bootrom) and is actually a hardware security feature.
There is also no "partial flashing" that occurs. A blob has integrity checks (signatures) which are ignored when using flatline and checksums (not ignored ever) before a flash begins. Usually if the sigcheck fails the bootloader will not flash. Our secret sauce means this signature check never happens, but before a blob is flashed its checksum is verified. This remains in tact even with our methods, and we would never ignore it because it is pretty reckless to allow such a dangerous operation to occur without safeguards.
If a bad upload due to say a bad usb connection occurred the device would reject the image and not flash it. Also as explained before the SBK is not acquired by the new bootloader. The SBK is burned into a one time programmable e-fuse.
jwestmoreland said:
I did ask NVidia about this - they said I have to talk to ASUS. I have done that and they want $100 for the RMA. Since I got this N7 at the ESC 2103 Android Seminar/Certification Class -
I wonder if it'll cost more to fix once ASUS gets it.
Click to expand...
Click to collapse
Of course they did. nVidia are the chip manufacturer not the ODM. They provide guidelines for the ODM's to integrate nvflash for recovery and bringup but ultimately once they have sold the chip to ASUS it is up to them to implement and no longer in nV's hands.
jwestmoreland said:
Does anyone know how the SBK is generated for the N7?
Click to expand...
Click to collapse
No. nVidia supply a set of guidelines but whether or not they were followed we do not know. For instance the Acer Iconia A500 used an algorithm based off the chipid which leaked .
jwestmoreland said:
I get this with nvflash:
e:\NVPACK\Android_OS_Images\Pluto\android_k_pluto_ os_image-17.0r0>nvflash.exe --wait --bct
flash_encrypt_encrypt_encrypt.bct --setbct --odmdata 0x40098008 --configfile flash.cfg --
create --bl bootloader_encrypt.bin --go
Nvflash 3.10.1700 started
chip uid from BR is: 0x0000000000000000015d28569018120c
rcm version 0X4
Command send failed (usb write failed)
I encrypted bct and bootloader_encrypt.bin with this SBK:
0x76B66E00 0x6B991000 0x6362F302 0x9C266D03
but I do not know if that is accurate.
Click to expand...
Click to collapse
Just picking a random sbk is futile. There are 6.27 * 10^57 possible keys. The chances of picking it at random are very very slim. the 0x4 error is because when you encrypt with the wrong key the bootrom will not have a bar of it and shuts down the USB port. Also bct and bootloader are not enough. There is a first stage bootstrap which also requires encrypting. The process is rather complicated.
jwestmoreland said:
Does NRT have the capability to save off the SBK someplace? Just wondering.
Click to expand...
Click to collapse
No
I've seen discussion of this as well - the 'too many links' error or message popped up when using NRT - I've seen posts that said it was nothing to worry about - but
I guess in this case it did appear to be something to worry about.
The N7 did boot the new image - all looked fine for a few minutes. The screen did one of those things that looked like an old B&W TV losing the channel - then poof. The N7 was in APX/brick mode.
Have you heard of anything like that happening?
Oh, and ASUS wants $200 - not $100. The $100 is apparently just for a battery fix. They will swap the MB for $200. A new N7 can be ordered off of Amazon cheaper than that - plus a new (or used)
MB can be acquired via eBay for much less than that.
lilstevie said:
The files are saved onto your device, the instructions we provide then tell you to grab those files off your device and store them somewhere safe.
The newly flashed bootloader doesn't inherit anything. The bootloader is encrypted with the SBK during the flashing process. The SBK is handled at a lower level (from bootrom) and is actually a hardware security feature.
There is also no "partial flashing" that occurs. A blob has integrity checks (signatures) which are ignored when using flatline and checksums (not ignored ever) before a flash begins. Usually if the sigcheck fails the bootloader will not flash. Our secret sauce means this signature check never happens, but before a blob is flashed its checksum is verified. This remains in tact even with our methods, and we would never ignore it because it is pretty reckless to allow such a dangerous operation to occur without safeguards.
If a bad upload due to say a bad usb connection occurred the device would reject the image and not flash it. Also as explained before the SBK is not acquired by the new bootloader. The SBK is burned into a one time programmable e-fuse.
Of course they did. nVidia are the chip manufacturer not the ODM. They provide guidelines for the ODM's to integrate nvflash for recovery and bringup but ultimately once they have sold the chip to ASUS it is up to them to implement and no longer in nV's hands.
No. nVidia supply a set of guidelines but whether or not they were followed we do not know. For instance the Acer Iconia A500 used an algorithm based off the chipid which leaked .
Just picking a random sbk is futile. There are 6.27 * 10^57 possible keys. The chances of picking it at random are very very slim. the 0x4 error is because when you encrypt with the wrong key the bootrom will not have a bar of it and shuts down the USB port. Also bct and bootloader are not enough. There is a first stage bootstrap which also requires encrypting. The process is rather complicated.
No
Click to expand...
Click to collapse
Error 3 on wheelie command
Code:
C:\Users\Anton\AppData\Local\Android\android-sdk\platform-tools\nvflash-tools-wi
n32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d4a8220240205
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error 3 sending command
My device bricked by itself when I was just transferring a big file from my tablet to PC. I backed up my blob files months ago and now im stuck with this.
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
nervChris said:
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
Click to expand...
Click to collapse
hey hello, sorry for the late answer, but it doesn't matter as whatever i try to flash ends up in a FAILED <FileWriteFailed> message (bootloaders, recoverys, stock images etc ... )
nervChris said:
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
Click to expand...
Click to collapse
the problem is that i cannot flash anything, i always get a FileWriteFailed
Hello , i have a problem which occured from one day to another.My Shield TV was not booting. I tried to go to recvery and do Wipe and reset and it didn't let me.Then I tried with different recoveries from Nvidia , and still no luck.I went i tried it with this https://nvidia.custhelp.com/app/ans...hen-you-are-unable-to-access-android-settings I only got errors Failed to mount... failed to format I/O Error ... also mke2fs returned 1 .....failed to clear BCB message and so on when i start i see the nvidia logo and after a minute the android logo flashing slowly, but after that nothing more. Is my device storage dead???
Did you ever manage to fix the device? I got EXACTLY the same errors on my 2017 shield pro.
Unfortunately not. I ordered a new SanDisc memory and soldered it, but it didn't work. i Also found this site
Unbricking SHIELD TV (2015) with a Bootrom Exploit
Last year, a friend gave me his SHIELD TV when he moved. He worked at NVIDIA and got it for free and had used it only a handful of times before it traveled from his closet to my own. I had forgotten about it until I had a need for a Raspberry Pi and discovered that they were all still sold out...
yifan.lu
and talked to the guy about my atempt.He told me that the Storage chip is somehow bound, and I should try to dump something from the old chip to the new one. I can solder but dumping was to high for me.
You can check his site and try his method described there. I also asked him about which pin has to be grounded and here is a clearer picture than on his site. Good Luck !
Okay if you see APX that’s good because you can use the recovery tools worst case. However, if you have access to your old emmc still, you can dump it and copy it to the new emmc. Also know that the emmc contains per-device unique identifiers that are required if you use Netflix or any drm. If you flash someone’s else’s backup, they wont work.
If all else fails, you need to use the brom exploit and APX to run the recovery cboot and manually flash a backup that way. Not sure if that’s easier or harder than flashing the emmc externally.
Click to expand...
Click to collapse
Thanks for the reply! As fascinating as the linked article is, this is way beyound me. Also, thinkgs will probebly not be 100% the same as I have the 2017 model.