Related
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
So where are you at right now. What rom and what exactly have you done to your tab.
Mkami said:
It seems that I was fiddling with my OTA and I lost my original build Kind of bummed out, and also the fact that I don't even know how to do a full backup. I did a nandroid backup which doesn't even work. I update to the new ICS firmware and messed up everything...Now I'm left in a gutter feeling utterly upset and don't know what to do. If there's anybody who pity's me, please help. It would be sincerely appreciated. I just want to start off fresh.
Click to expand...
Click to collapse
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
shaun298 said:
So where are you at right now. What rom and what exactly have you done to your tab.
Click to expand...
Click to collapse
At this moment right now, my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Moscow Desire said:
Yeah, I share the pity with you Mate. You shouldn't have to look at that busted tab. Just put that shameful thing in a box and mail it to me, to help ease your pain. Heck, I'll toss in shipping so you won't suffer further insult and pain...
Seriously, though, there are plenty of tools and procedures here to bring it back to life.
First off, before you muck things up further, I would look in your nandroid backup, and get the UID number. Hopefully you wrote this down somewhere before you originally messed with things?
For starters, I would goto this link, and see if it works for you...
http://forum.xda-developers.com/showthread.php?t=1699277
The english steps are not the best in the world, but you will get the general idea.
MD
Click to expand...
Click to collapse
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Mkami said:
Hahaha funny guy! If you haven't seen my post its here and the reasons. Also I do have the UID saved on a text format on my pc...will that work??
So here is the issue are the current moment friend.
my a500 tab has that orange light on the bottom and it stays there, and when I turn on the tab it starts up normally like it would, and when it does it turns off. The strange thing is that orange charging light where the power button is, stays on even though I'm not even charging it.
I've tried changing the OTA, but after when it starts in the corner it says something like. " Not official blob" I'm not even sure I know what that even means....I have everything including nandroid backed up all the files into the SD card I had in my tab, I notice is there somewhere due to the amount of space it consumed on my SD.
So please! IF you know of any way to fix this I would be in great appreciation, also it's been a month since I've had this tab, as well I have a 2 year warranty.
Click to expand...
Click to collapse
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
cruise350 said:
Have you tried putting a stock update.zip on the root of your external sdcard and booting the tablet by holding the volume down button (left volume rocker) down while pressing the power button until the tablet finds the file and installs it. This should bring you back to unrooted stock ICS with locked bootloader and you can start over. Remember, this must be an update.zip file that is extracted from a stock RUU. You can't just rename a RUU file to update.zip.
Click to expand...
Click to collapse
What do you mean by RUU? Also I've tried a couple of the OTA updates, when I first got the tab it was on 3.1 HC didn't even update it or anything, just had a custom ICS ROM on it. Do you think you can post the steps or anything on how to do this properly and go fresh? It would be sincerely appreciate buddy.
Moscow Desire said:
Well, you get the orange light because your EC Pwr management is probably fubarred. That should be fixed when you install a stock rom as suggested in both mine and the other poster.
Considering you have your UID, you should be ok.
Of course I don't know if this is a 3.2 or an ICS UID. Best to have both. The sbk is the same, but the uid numbers differ.
If it's a 3.2., check the Q&A thread for a post I did for a guy earlier today.
But you should be able to follow the steps for the update I posted earlier.
Blob means Bootloader. And looks like you had an unlocked bootloader?
Try to roll back to 3.2. That's where I would start.
MD
Click to expand...
Click to collapse
Hmmm....I'm not even sure what I am doing wrong but whatever it is, it seems to be not working. I looked for you post for the earlier person that you did, but don't know what it is under. By the way when I first bought the tab it was under 3.1 HC and after getting flexreaper it became to ICS 4.0.3...
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Mkami said:
So like everytime I turn on the tab it shuts down instantly, as well every time I try to boot an update.zip file onto the SD card it shows this animation of the android with this circular sphere in it's stomach after that it falls over with a red caution sign.
Click to expand...
Click to collapse
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
lcd047 said:
In my experience the common cause for ending up with a caution sign is a corrupted update.zip (incomplete download, bad SD card, etc.). As for the tablet shutting down, my guess is that's related to the power management functions being broken.
Click to expand...
Click to collapse
You're right! I was able to fix it and boot up to the usual! Thanks mate!
chismay said:
im not THEE most savvy here but i do know a few methods and find it easy to discover lesser known ones, i feel bad for you . if you want you can skype video me and ill try talking it over and maybe a few methods? :highfive:
edit: ok from what i can tell your update was bad and your bootloader is causing problems, the power problems are probably arising from the bad power management as moscow desire told.
the tabs obviously rooted n all right? ok so how about flashing the v7 ics bootloader then trying a custom rom?......<-also recommended by moscow desire
Click to expand...
Click to collapse
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Mkami said:
Hi Chismay, well I thought I fixed the issue and the problem. Guess again I did not This I can't believed I used a leaked ICS OTA, kinda ruined most of the things in my tab. Lol just had it for a month and already messed it up by fooling around with it. But your help is greatly appreciated buddy! Would like to get a one on one instructions on what I should do.
Cheers!
Click to expand...
Click to collapse
tkirton said:
Correct me if I'm wrong on this...
1. You originally had Honeycomb on your tablet.
2. You flashed FlexReaper on your tablet
3. You probably got a recent version of FlexReaper.
4. You never upgraded your bootloader.
5. You can still get access to recovery.
If all of these are correct, then I think I know what the problem is. It appears you flashed a rom that requires the ICS bootloader and not the Honeycomb bootloader.
This, I think, is an easy fix...
1. Download the following file: http://www.darktremor.info/files/FLEXREAPER-R12.5-ICS-1.031.00.zip (this is an older version I have on my Acer A500).
2. Put the file on your SD card.
3. Boot up into recovery (if you can't get there, stop here).
4. Once you are in recovery, flash the FlexReaper file you just put on your SD card.
5. Now try to boot and see if it works.
Let me know how it works either here, in a PM, or e-mail me at [email protected]. If you need further assistance, don't hesitate to contact me.
Click to expand...
Click to collapse
Hahaha! Good job on guessing all that! I just followed your order from step to step and I was about to boot up normally! Everything might be erased and stuff, but hey at least I have my tablet working again :good: Case solved!
*** 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
My colleague brought his stock A500 to me in a bricked condition last week.
I need a way to restore it. If I try to do a wipe it will say bootloader error if i try the recovery the droid falls down with the red sign with the exclamation mark.
This tablet has never been rooted, my colleague is not in to such things, it's lived its life with ordinary acer otas and the occational very young human (5 year old) trial wich it has survived.
He has installed all the OTAs he ever got on the tablet and this is in Sweden so it would probably be a 4.0.3 acer stock on it now.
I'm guessing it has died during a OTA or something. if i turn it on it will sit at the acer logo indefinitly.
I Bricked my A500 during a rooting atempt resulting in me needed to flash a stock rom to get it working again, but i cant find the thread i read to un-brick my A500.
Please Help!
try this http://forum.xda-developers.com/showthread.php?t=1839313
dibb_nz wrote:
try this http://forum.xda-developers.com/showthread.php?t=1839313
Click to expand...
Click to collapse
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Hogbola said:
Well that thread seems to hold all i need, although i can't do a full wipe. when i do the flipswitch wipe procedure it halts with bootloader error
Im hoping to just be able to flash the stock rom from the link you gave me. Is it entirely necessary to do the wipe prior to flash? can i wipe it afterwards?
Click to expand...
Click to collapse
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
I am in a similar situation. Push the power button and it goes to a screen with white acer on black and stays there. Totally stock ICS, no root. I tried the update.zip thing and after automatically rebooting it says "Boot verified failed...". I don't have my cpuid, or have installed previously CWM or anything like that. I can get into APX mode. This guy here: http://forum.xda-developers.com/showthread.php?t=1751978 could only get into APX with no cpuid as well, but i don't understand all of the ubuntuu and command line stuff. I would love for someone to be able to walk a dummy like me through this mess. Thanks for any help.
if u got boot verified fail error you need nvFlash to repair that....as u know, with nvflash you need yr cpuid....wot about usbdeview? if you've never plugged yr tab into yr PC - then it won't work and the ONLY other way is Linux....
might be best to start yr own thread with a descriptive title, not just a help I'm bricked no uid, thread there are hundreds of those....the more effort u put into the title the more likely you will attract the attention of someone who can actually help...and remember you just don't need a bit of help but a blow by blow description of what to do and how....this will be very time consuming....at the very least get ubuntu installed, maybe just try a few things, anything to show you are capable of at least giving it a go yourself..
there are others who would like 2 know how to do this as well...having a specific thread of its own would be great
good luck
dibb
Sent from my GT-I9300 using Tapatalk 2
Actually, I have connected it to my PC before. Only for transferring media though. If I've done that, is the some way to retrieve my cpuid from the PC?
yup...usbdeview.zip see the bottom of the OP in the cpuid guide in my sig
Thanks alot for your help. I used usbdeview and got my cpuid. Now I should use nvflash? Know where a good step by step is for that one?
you could try the one in my sig??
dibb_nz said:
you could try the one in my sig??
Click to expand...
Click to collapse
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
NvigR8 said:
Right. Sorry, I didn't notice that before. Thanks again for your direction.
"To install one of these roms you will need a custom recovery and to get that you must flash the patched bootloader FIRSt - once its patched you can install a recovery any old way you like"
Looking at that guide, would you please tell me what a custom recovery is and how to get one? Btw, I don't plan to do a custom ROM yet, I just want to get the damn thing working first. Was thinking of using the HC EUUs from the firmware files list. However there are two files, a .rar and a .exe listed. Which do i use?
Click to expand...
Click to collapse
The .rar EUU is for an A500, the .exe is for the A501, which do you have?
I've got the a500. However, I decided to go with a custom ICS rom after all. I managed to put a new bootloader and custom recovery on using the a500apx flash tool. That part went fine. I flashed this rom:
Acer_AV041_A500_1.054.00_WW_GEN1-FULL-ROOT (original odex)
and that appeared to go well according to twrp, but after rebooting, it just shows the bootloader again and stops there. Not sure what i did wrong.
I renamed the rom update.zip. Should i not have done that?
well congrats for getting thru the flash process with no probs!!!
as far as renaming to update.zip that was not such a good move...hopefully things havent been screwed up too much
just go back into recovery and do a FULL wipe/format
then to flash use the option "install from zip file" not sure where that is in TWRP but it will have one
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
NvigR8 said:
Okay. I will reflash the rom after completely wiping again. Thanks.
On a different note, why do roms require particular bootloaders?
Click to expand...
Click to collapse
The stock ICS BL is encrypted - more or less - the only way to 'flash' a recovery or rom is to have the "key" that "unlocks" - it more or less - if you dont use the right key then the OS will not boot - the 'key' is based on your cpuid which is why everyone is forever telling you to save it somewhere safe....
Also different, how do you like your SGS3? If i can manage to fix this thing, perhaps I'll root my phone...
Click to expand...
Click to collapse
I enjoy the big screen, took awhile to get used to it in my hand, kept dropping it....then I ran it over with my 44tonne truck after 3 days and munted it!!!!
I have a case for it now, and its gr8 - I havent installed a rom on it yet...the forums over there are jampacked and I have no idea what I'm doing, lol - its the first android device I've had that I've left stock for so long...but it does what I want...the camera is awesome -burst mode is the bomb - BUT do I think it was worth the money???? Still on the fence about that one.....
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
NvigR8 said:
Ouch. Sorry to read about running over your phone. That would kill me. I really like my SGS3. I think I'll look into rooting it just to be able to back it up and get rid of the bloatware. I did that on my Captivate and prior to today, thats all I've ever done modding wise to an android device.
So, I managed to get my tab up and running again. Yay! I reflashed the rom w/out changing the name and worked like a charm. Now If only I knew why this happened in the first place... Thanks for all your help.
Click to expand...
Click to collapse
yeh sometimes happens with the tab for some reason - thank your lucky stars it didn't get stuck in apx mode...if that happens its normally a hardware fault so theres not alot u can do...I'm just pleased you got sorted without too much drama and it was as easy as reflashing the zip....so now you have the v8 BL - you're gold!!!
dibb_nz said:
we're assuming the tab is full stock and currently on ICS...
and we're assuming he never tried to 'fix' his tab by flashing one thing or another...
the bootloader error worries me...what exactly does it say...
Yes the wipes are really important!! and not being able to use the button method to do so is concerning...
what happens with the Over The Air (OTA) updates is its just that...an update...it leaves all your settings/data intact. When you OTA from one build to another, like Gingerbread 3.0 to Honeycomb 3.1/2 and then to ICS 4.0 - you drag all your apps and settings with you and of course some things that work with 3.2 will not work under ICS....fjor instance, lots of folk had trouble with wifi disconnects, once they got to ICS - or they had apps force closing and other 'glitches'. This is why everyone tells you to do the wipes - as this fixes these things! In the case of stock ICS my gmail would f/c all the time no matter how many times I wiped/formatted....So for a smooth running tab - flash a custom rom!!!!!!
But getting back to you...
From that link i gave you...download the 3.1_Full.zip....its decrypted so just extract it and get the "update.zip" from it..
This "update.zip" is not an incremental "update" but the full stock rom....
once installed you'll be on GB you will need to root it with iconia root and then use acer recovery installer to flash cwm....(get these from the playstore)
do a backup or adb devices so you can get your CPUID....this is important...if anything goes wrong at any stage this is the only thing that will get you unbricked....see the cpuid link in my sig for more on this, please take the time to read it, even if it doesnt make much sense to you, read it anyway....
AFTER you have retrieved your cpuid, you can nvflash the patched bootloader/recovery pkg which means you are able to flash ICS/JB custom roms
they cannot be flashed via cwm like normal...you must use nvFlash to do it....
OR
take the OTA route to ICS...this takes a bit of time...I did it last week and it was a good 6-7 hours to go from GB to ICS
there are pre-rooted stock roms if you wanna stay stock see civato's stock rom thread for that here http://forum.xda-developers.com/showthread.php?t=1633907
official stock rom list by blackthund3r are here http://forum.xda-developers.com/showthread.php?t=1816560
civs guide to flashing the unlocked bootloader here http://forum.xda-developers.com/showthread.php?t=1622425
Click to expand...
Click to collapse
When i do the wipe it says
Code:
Erasing userdata...
Code:
Unrecoverable bootloader error (0x19000008)
Unrecoverable bootloader error (0x19000008)
Hogbola said:
When i do the wipe it says
Code:
Erasing userdata...
Code:
Click to expand...
Click to collapse
I googled your error - the consensus from what I read is a corrupt OS due to running OTA updates...
Some had luck with rebooting. Others had to send it to Acer.
Did you run the update.zip? so what happens when you run the update.zip
Are you able to get into "apx mode"? If you can, hook up to your PC and see if your tab is recognised as an "apx device" - check "Hardware, Printers in win7"
Thats all I can suggest atm - if your tab does get into apx mode OK then you can find your cpuid by running Linux -
Maybe ask the guy if he's ever had the tab hooked up to his PC like to transfer files and stuff - get him to download "USBdeview" to his PC -
this will show every single device thats ever been connected to the PC and it will show the "cpuid"...
Even if we do get the uid theres no guarantee it will fix the bootloader error - but we may as well explore all the options we can....
dibb_nz said:
USBDeview will only work when you have previously plugged your tab into the PC WHILE you were running HC Rom and BL
1. If you haven't plugged your tab into this pc before, do so now, before you run the program. HC ROM/BL ONLY
1a. Run the exe and you will be presented with a window of all the USB devices you have ever plugged into your computer.
2. Click on "VendorID" column along the top to sort them
3. Look for the number "0502" under Vendor ID AND "3325" Product ID
4. In the serial number column will be a 15-digit number this is your device ID.
5. Write the number down and put a 0 in front of it and now you have your CPU ID!!!
Click to expand...
Click to collapse
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
DennisPimps said:
So, my neighbor bought an Acer A500 a few months back. He ended up not liking it so I bought it off of him. My tablet and I got really close and I fell in love. I started neglecting my girlfriend and all that. We had a beautiful relationship; my tablet and me. But, a couple days ago I was playing N.O.V.A 3 and it froze. I thought nothing of it and just powered it down. To my dismay, it froze at the Acer screen. I restarted it again and got the same thing. My life was over. My heart felt like it was ripped from my chest... I shed a manly tear.
I've tried vol- and power, vol+ and power, the reset button, D/Ling several different update.zip files and copying them to my SD. I've spent the last couple days reading and trying everything. All I get is the Droid guy with the blue thing swirling in his chest and then him laying on the ground with a red triangle and an exclamation point.
I'm told it's most likely not a hardware issue as things things are almost bullet-proof. But, I am pretty good at breaking things
Am I screwed or does someone have a miracle they can share. My gaming life depends on it.
-Dennis.
Click to expand...
Click to collapse
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Danny2 said:
Do you know what you were running on this thing? Was it stock Honeycomb, scock ICS, or was it running a custom ROM? (If so which one?)
Was it ever hooked up to your PC? (This would help with retrieving CPUID, if it was.) Do you know your CPUID? (Or SBK?)
You should at the least know the answers to these questions before you attempt any type of repair, as it is almost certainly salvageable, but you will almost certainly need your CPUID.
Click to expand...
Click to collapse
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
DennisPimps said:
I was running 4.0.1 ICS. I do have my cpuid and SBK. I tried flashing a new rom using blackthund3rs flash tool but it got to about 25% and stopped. I keep losing sync with my PCs, though.
Click to expand...
Click to collapse
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Danny2 said:
So, do you want to go back to stock, or to a custom ROM? If you wanna go stock, the easiest way would be load a 3.01 EUU, & upgrade on the play market to 4.03. That will prove it isn't a hardware issue. Alternatively, you could root, load a recovery, a bootloader, & flash a new ROM.
Click to expand...
Click to collapse
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
DennisPimps said:
To be honest, I really don't care as long as I can getting it working again. But I would rather root it.
I think I can get it to work but neither one of my computers will recognize it. It shows up in APX and says something about recovery driver mode when I plug it into the laptop with Vista automatically downloads a driver and installs it again. I've tried turning off automatic driver install but that doesn't work for some reason. The one with XP Pro just shows up APX device but the APX Flash Tool by blackthund3r says it can't find it. I've downloaded the Acer Iconia 500 drivers and installed them but that doesn't work either. I'm at a loss.
Any tips would be great. I think I have a better chance using my laptop with XP, though. I also need to let you know that I truly do appreciate you trying to help. If you're ever in Columbus Ohio, let me know and I'll buy you a beer. lol
Click to expand...
Click to collapse
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Danny2 said:
Sorry,I thought I responded to this yesterday, but just now noticed I didn't.
Fire it up in APX mode, and install the 3.01 EUU from the development section, (Stock ROM listing) then simply follow the upgrade path to 4.03, then root. If you drivers are installed correctly, everything will work fine, if not, nothing will happen. If it does start to load the stock ROM, then fails with a write error after it attempts to write the bootsector, you may need to run Badsector, or babsector, depending where you look. Search the recent posts on this, you will find lots of stuff.
Click to expand...
Click to collapse
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
DennisPimps said:
How would I go about installing the EUU? I have nvflash and blackthund3r's flashing tools. But I can't seem to get my PC and tablet to connect. When I plug it into my PC without being in APX mode, it just says MTP Device. When I plug it in while in APX mode it does say something about Picasso Recovery Driver.
If you could explain things to me like I'm aN idiot, I'd really appreciate it.
Thanks,
Dennis
Click to expand...
Click to collapse
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Danny2 said:
Sorry for late response, I watched for reply from yourself, but you didn't answer for 10 days, I lost track. Still need help?
Click to expand...
Click to collapse
Yea, it's still bricked. I did finally get the flash tool to recognize it but it kept hanging up. I also tried Timmy Dean's EUU tool and that hangs up too. I did a little more research and found that I may have a faulty emmc. I ran babsector and got 'fatal error code 9 cannot format partition BCT.' I found a thread here that discusses how to write around the bad sectors using Linux. I'm going to give that a go... I've always wanted to learn Linux. Hey, I can't screw it up anymore than it already is, right? Again, thanks for your time and effort in trying to help.
Cheers,
Dennis
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
ericpeacock79 said:
Hey, before you try that, try different USB cables and ports (if u haven't already)
I had a similar problem with my phone not maintaining stable USB link to PC... after 4 days I tried a diff USB cable and boom, snap, working.
Just a thought.....
Sent from my A500 using xda app-developers app
Click to expand...
Click to collapse
I'll give that a go, m8.
Thanks!
-Dennis
DennisPimps said:
I'll give that a go, m8.
Thanks!
-Dennis
Click to expand...
Click to collapse
Just wondering if you ever figured out the errors you were getting during flashing? Currently having the same issues when using babsector.
Isn't there anyone one here who would be willing to make a rom for the ME301t besides the stock ones? If we were willing to donate money to get it done?
krash1256 said:
Isn't there anyone one here who would be willing to make a rom for the ME301t besides the stock ones? If we were willing to donate money to get it done?
Click to expand...
Click to collapse
No offense, but i don't think this is the section for requests. FAQ and general discussion would be more appropriate.
Oops, sorry
DaringDomino3s said:
No offense, but i don't think this is the section for requests. FAQ and general discussion would be more appropriate.
Click to expand...
Click to collapse
Sorry didn't know.
I assumed, that's why i said something as soon as i saw it. I'm new to the posting rules here too, and i have seen that the development section is taken seriously.
Sorry about your device scenario. Im sure something will come along start a thread campaigning in a place where it wont get deleted and you may find more people that know someone wlling.
Cromi-x and Geimlock are already compatible with ME301T... :good::good::victory:
Since the ME301T is so close to the TF300 in terms of specs and because of how easy it was to make the ME301 work on CROMI or GRIMLOCK, its possible that there might only be a few minor things that need to change to make a ME301 work on a CM rom. Since there are no devs who own an ME301T we would needs some help from the community to get it to work.
Mainly we would need for someone with an ME301T to install a CM based rom and see if it will boot. From there you would need to get a logcat and send it to us so we can see if we can fix the issues that are preventing it from working.
hardslog said:
Since the ME301T is so close to the TF300 in terms of specs and because of how easy it was to make the ME301 work on CROMI or GRIMLOCK, its possible that there might only be a few minor things that need to change to make a ME301 work on a CM rom. Since there are no devs who own an ME301T we would needs some help from the community to get it to work.
Mainly we would need for someone with an ME301T to install a CM based rom and see if it will boot. From there you would need to get a logcat and send it to us so we can see if we can fix the issues that are preventing it from working.
Click to expand...
Click to collapse
Someone tried it here. http://forum.xda-developers.com/showthread.php?p=48077047#post48077047
It didn't work for me yet. Maybe you could take a look and see if I'm doing something wrong or if there's something wrong with the file. Am more than willing to help in anyway I can.
krash1256 said:
Someone tried it here. http://forum.xda-developers.com/showthread.php?p=48077047#post48077047
It didn't work for me yet. Maybe you could take a look and see if I'm doing something wrong or if there's something wrong with the file. Am more than willing to help in anyway I can.
Click to expand...
Click to collapse
Sounds like it isn't too far off. What I need is for someone to try and flash a CM rom and send me logs of when it is booting up etc. As a suggestion, I would try this rom: GRIMLOCK_CM_3.0 as it is the rom I am working on. It would be easiest for me to help on that.
hardslog said:
Sounds like it isn't too far off. What I need is for someone to try and flash a CM rom and send me logs of when it is booting up etc. As a suggestion, I would try this rom: GRIMLOCK_CM_3.0 as it is the rom I am working on. It would be easiest for me to help on that.
Click to expand...
Click to collapse
Okay, will do. I'll download and it and give it a shot. I'm not very good with the logcat stuff, lol, but I will do my best.
Well, it boots into the rom and I get a little circle which is a mouse I guess. I can get around and I can get into settings but I can't figure out how to get down to about tablet so I can get to usb debugging. If I try to adb while it's booting up adb just says waiting for device... So I can't do the logcat. Any suggestions on what I'm doing wrong or a way to get adb working?
krash1256 said:
Okay, will do. I'll download and it and give it a shot. I'm not very good with the logcat stuff, lol, but I will do my best.
Well, it boots into the rom and I get a little circle which is a mouse I guess. I can get around and I can get into settings but I can't figure out how to get down to about tablet so I can get to usb debugging. If I try to adb while it's booting up adb just says waiting for device... So I can't do the logcat. Any suggestions on what I'm doing wrong or a way to get adb working?
Click to expand...
Click to collapse
Okay, I messed around and finally got usb debugging turned on. Rebooted and did this logcat. I can't get wifi turned on at all.
BTW: I love this rom without all the google crap on it. I have always hated having to run through all the setup wizard crap too. Thank you for helping with this. I'm very excited about getting this rom for my tablet.
krash1256 said:
Okay, I messed around and finally got usb debugging turned on. Rebooted and did this logcat. I can't get wifi turned on at all.
BTW: I love this rom without all the google crap on it. I have always hated having to run through all the setup wizard crap too. Thank you for helping with this. I'm very excited about getting this rom for my tablet.
Click to expand...
Click to collapse
Try to flash THIS after flashing the rom and see what happens.
hardslog said:
Try to flash THIS after flashing the rom and see what happens.
Click to expand...
Click to collapse
Okay, I wasn't sure if you meant to flash both files one right after the other, so I flashed the rom, then the test. Sticks me at CyanogenMod animation. Then I did a clean flash of just the rom, rebooted and flashed the test, it booted, said Android is updating apps and then gets stuck at starting apps. So then I rebooted just to see if maybe that would do it but that just sticks at CM animation once again.
krash1256 said:
Okay, I wasn't sure if you meant to flash both files one right after the other, so I flashed the rom, then the test. Sticks me at CyanogenMod animation. Then I did a clean flash of just the rom, rebooted and flashed the test, it booted, said Android is updating apps and then gets stuck at starting apps. So then I rebooted just to see if maybe that would do it but that just sticks at CM animation once again.
Click to expand...
Click to collapse
I meant to flash the rom then the test.
Can you get my any logs?
hardslog said:
I meant to flash the rom then the test.
Can you get my any logs?
Click to expand...
Click to collapse
I don't know how to get log during boot. I tried turning on usb debugging first and then flashing the test and then tried to logcat but it just says waiting for device. Is there a specific way to get adb to work during boot?
hardslog said:
I meant to flash the rom then the test.
Can you get my any logs?
Click to expand...
Click to collapse
I wasn't doing adb devices first then the logcat command. Duh. Here's the logcat.
Test # 2
@krash1256
Ok here is another one to try. Again Flash GRIMLOCK_CM first and then try flashing this one. According to the logs its possible that the wifi got fixed but the extra files I put in borked other stuff.
hardslog said:
@krash1256
Ok here is another one to try. Again Flash GRIMLOCK_CM first and then try flashing this one. According to the logs its possible that the wifi got fixed but the extra files I put in borked other stuff.
Click to expand...
Click to collapse
Okay, it now boots into the rom but you still have to use the little circle as a mouse and I can now turn wifi on but it just sticks at turning on wifi.
Turned wifi off and back on now it says To see available networks, turn on wifi.
krash1256 said:
Okay, it now boots into the rom but you still have to use the little circle as a mouse and I can now turn wifi on but it just sticks at turning on wifi.
Turned wifi off and back on now it says To see available networks, turn on wifi.
Click to expand...
Click to collapse
Ok so wifi still doesn't work, but it is a step in the right direction.
I don't really understand what you mean by a little circle as a mouse though?
and again, the more logs the merrier
hardslog said:
Ok so wifi still doesn't work, but it is a step in the right direction.
I don't really understand what you mean by a little circle as a mouse though?
and again, the more logs the merrier
Click to expand...
Click to collapse
Instead of being able to just touch the screen and make choices, this little round circle pops up when you touch the screen and you have to move that little circle around and tap on the circle twice to make choices. It's like using a touch pad for the mouse on a laptop. For instance, if you want to open settings you have to position the little circle on the settings button, tap twice, it opens settings, then you have to position the circle on say wifi and tap the circle again. To scroll, you have to position the little circle at the very bottom of settings, and it's a hit or miss type of thing, tap it and then move it upwards to get to the bottom, like about tablet and tap the little circle again. Does that make since? The rom is basically mouse driven instead of touch driven.
This logcat is while it's booting and also once I'm in the rom.
Bluetooth is definitely working. I connected a bluetooth mouse and I can navigate with that instead of having to navigate with the little circle.