Related
So first of all my tablet is brand new and not rooted and I don't want to root it.
When I got it I could update it instantly from 3.0.whateverwastheversionatthetime to android 3.2 (build 7.006.01_COM_GEN1) but it won't go from there to 3.2.1 which I hear is available for my location (France) The update tool tells me that my firmware is up to date.
I've tried a factory reset as advised by Acer customer care services but it wouldn't change. Also no matter what I do (empty cache etc.) the market won't update to Google Play Store and I think the two issues are related.
So I have two (or rather 3) questions:
1) Does anyone know a way around to force the update? (I doubt it's possible but hey "l'espoir fait vivre")
2) If not can I install a stock ROM without root and NOT compromise the warranty?
3) Where can I get such a ROM? I have searched here and here but 3.2.1 is not on the first thread and the links on the second thread are broken, plus I want to make sure that the ROM is the proper one for my region and that comes the ICS OTA update I will have no troubles doing the update.
Thanks in advance to those who will answer.
lunaticwraith said:
So I have two (or rather 3) questions:
1) Does anyone know a way around to force the update? (I doubt it's possible but hey "l'espoir fait vivre")
2) If not can I install a stock ROM without root and NOT compromise the warranty?
3) Where can I get such a ROM? I have searched here and here but 3.2.1 is not on the first thread and the links on the second thread are broken, plus I want to make sure that the ROM is the proper one for my region and that comes the ICS OTA update I will have no troubles doing the update.
Thanks in advance to those who will answer.
Click to expand...
Click to collapse
1) No you cannot force an OTA
2) It depends - others have reported returning there acer with no probs -, i think someone has even returned it rooted and been ok. These things are fairly bulletproof, and really hard to 'brick'. As long as you can read, follow a few steps you shouldnt have any probs. The worse thing you can do is try 2 or 3 different methods all at once because something isnt working right. You're best to pick one and stick with it, if you have probs ask for help in the thread you got the rom from or start your own like you have here
3) The update.zip method from the first link you posted "should" work. Did you "decrypt" the file you downloaded before extracting the update.zip??
You could try timmyDeans v4 method- it will install a stock 3.2.1, it is rooted but you can remove root using the tools he provides. Beware though this will wipe all data so backup anything essential.
The update.zip method will leave your data and settings intact
As always the choice is yours, there are some really excellent custom roms out there - I enjoy the best of both worlds with a backup of my trusty stock 3.2.1, I flash to my hearts content knowing I can always go back to it when the OTA update is out!!! Oh the joys of root priveleges
Thanks for your input, I'll make sure to try all this when I get back from work. I've a few additional questions:
1) If I install a custom rom, will the OTA work from this ROM or, comes the OTA, will I have to restore my actual Stock rom and then proceed with the OTA?
2) I haven't tried the rom on the first link I gave because it is modified and I was searching for the original, pristine, untouched stock ROM for 3.2.1
I've seen such roms around here on xda for 3.2 but none for 3.2.1, if anyone stumbles upon one please let me know.
3) Since I'm still looking for a pristine ROM before trying anything else, I have a friend whose tablet (same brand and model) safely updated to 3.2.1, is there a way to make a rom from is gear? If yes, how to?
4) (related to 3) how can I backup my actual ROM, do I have to be a root user to do so?
THX again!
lunaticwraith said:
Thanks for your input, I'll make sure to try all this when I get back from work. I've a few additional questions:
1) If I install a custom rom, will the OTA work from this ROM or, comes the OTA, will I have to restore my actual Stock rom and then proceed with the OTA?
2) I haven't tried the rom on the first link I gave because it is modified and I was searching for the original, pristine, untouched stock ROM for 3.2.1
I've seen such roms around here on xda for 3.2 but none for 3.2.1, if anyone stumbles upon one please let me know.
3) Since I'm still looking for a pristine ROM before trying anything else, I have a friend whose tablet (same brand and model) safely updated to 3.2.1, is there a way to make a rom from is gear? If yes, how to?
4) (related to 3) how can I backup my actual ROM, do I have to be a root user to do so?
THX again!
Click to expand...
Click to collapse
1. Typically, most people do not take OTA's when running a custom rom, as basically the OTA installs a totally fresh factory Rom. This is true with the 3.2.1 update, which contains a new bootloader. Usually, this means you lose root, and Recovery, then stuck with downgrading to get these things back.
Timmy Deans root tool supposedly maintains a back door method, which s supposed to protect root, in case of an OTA. No, I haven't used this method, as I run my own 501 roms.
2. Vache has a thread "full package and updates" in the 500 Dev forum. There are several factory Roms and Updates. You'll have to look. Chances are, he may not have the specific Com Gen version you want, but probably one close enough.
3. If your friend can get adb running, you can pull a "system dump", which will dump all files/folders in the system folder. The boot.img would be nice to get, but you can probably use the current one you have. Unfortunately, he already rebooted, so you probably can't get the original full update file. If he's rooted, you can use an app called Rom Factory, to get most of what you need. It's always a good time to become familiar with ADB.
4. Well, you can back it up internally, but it's sort of useless if you can't get into your OS You will need to Root, and install a custom recovery to keep your backup externally.
Moscow Desire said:
2. Vache has a thread "full package and updates" in the 500 Dev forum. There are several factory Roms and Updates. You'll have to look. Chances are, he may not have the specific Com Gen version you want, but probably one close enough.
Click to expand...
Click to collapse
ok, as Moscow has pointed out, in vaches thread not all roms are listed. My stock roms (1.016.01 and 1.139.04) for instance weren't - so I spent the last hour or two trying the "EUU gen1" listed at the bottom of the page. Well, it actually worked!! It gave me an OTA to 1.139.04 straight away. After that installed i got the 4.010.40 to 3.2 and then the next 2 for 3.2.1 - 7.006.03 and 7.014.15. So its given me the correct updates for my country AND kept my data and settings too.
SO, since you're on a Gen1 Rom this should work for you too, but still no gaurantee you will get the OTA to 3.2.1, no harm in trying though
btw timmydeans method is a gen2 rom so you can rule that out...
---------- Post added at 11:25 PM ---------- Previous post was at 11:16 PM ----------
just came across this link for an update to stock 3.2.1 build 7.014.14 here - orignal thread here but you need cwm to install it....
unless you can make it into an update.zip???
but thats way outta my league,
moscow may be able to suggest something though
Thank you very much, your answers help a lot! Just a few precisions and I'll stop being a pain in the ass!
1. Typically, most people do not take OTA's when running a custom rom, as basically the OTA installs a totally fresh factory Rom. This is true with the 3.2.1 update, which contains a new bootloader. Usually, this means you lose root, and Recovery, then stuck with downgrading to get these things back.
Click to expand...
Click to collapse
==> @ Moscow, when you say "lose recovery" does it mean I lose the green thingy with gears when I start with volume down and power pressed/ and when I reset to factory settings?
==> @dibb_nz your method is the closest to what I'm looking for, I also hope it will give me the correct updates for my country and since Vache is a fellow countryman it might just be ok.
Anyways thanks again, I'll give a thorough look to all of your solutions and try and do a few things tomorrow afternoon. I'll keep you posted in case this thread interests anyone else.
lunaticwraith said:
==> @ Moscow, when you say "lose recovery" does it mean I lose the green thingy with gears when I start with volume down and power pressed/ and when I reset to factory settings?
Click to expand...
Click to collapse
No, what I meant to say, is when you run a rooted "custom" Rom, and use a "custom" recovery such as RA Recovery or CWM, getting an OTA update, usually wipes that out, and installs the factory bootloader. Your factory recovery....cough cough.... will still be there.
If you are only concerned about stock factory, then don't worry about it. You;re ok. Your factory/stock recovery will be just fine
The reason we root and install custom recoveries, is so we can do 3 primary things.
1. Flash a custom rom
2. Create a complete system backup to our external SD card.
3. Get rid of pre-installed useless apps.
There are other things we can do with it, but these are the primary reasons.
When you have a default factory stock system, the only protection you have, is a factory reset (hope it works), and a couple other methods which require a touch more knowledge.
Anyhow, don't worry about your factory recovery. It's just fine.
1) Just for the sake of knowledge what's the difference between GEN_1 and GEN_2? (and GEN3 and CUS7 and EMEA_TMLP)?
2) @Dibb_nz when you tried with the stock rom from Vache, was it because you encountered the same no FOTA update problem as I did? Or just to try...?
3) Something's still unclear to me after browsing through the forums: If I get an unmodified stock ROM can I flash it with the stock recovery? (so without rooting) Or do I need CWM (so root is needed)
4) What's EUU? (on Vache's thread some roms are listed as EUU)
lunaticwraith said:
1) Just for the sake of knowledge what's the difference between GEN_1 and GEN_2? (and GEN3 and CUS7 and EMEA_TMLP)?
2) @Dibb_nz when you tried with the stock rom from Vache, was it because you encountered the same no FOTA update problem as I did? Or just to try...?
3) Something's still unclear to me after browsing through the forums: If I get an unmodified stock ROM can I flash it with the stock recovery? (so without rooting) Or do I need CWM (so root is needed)
4) What's EUU? (on Vache's thread some roms are listed as EUU)
Click to expand...
Click to collapse
1. The Gen's usually signify regional based roms. More specifically language support, sometimes a wifi tweak, and maybe a couple other things. Mostly though, ComGen1's are for the US and probably canada, and offer about 12 different languages. TMPL is for East Europe mostly, with polish as the default language. All roms contain the english language as far as I know.
3. You basically can't install a full rom on an unrooted tablet without CWM or RA Recovery. You will have to run the update (decrypt the file, remove the update.zip)
4. EUU is a pc based install. Plug in the USB, set your tab to APX mode and run the EUU.
If you did the root, and install a custom recovery, then you could run just about all the full roms. Your custom recovery would be overwritten, and you would lose root access. You would have a stock tablet with the version rom you selected.
You can always wait a week or so. Am sure if the update has been pushed to your country, it's just a matter of time till you get it. It's common for the update process for specific roms, to get fully done in 2-3 weeks. It took well over a week just for users in california to mostly start getting updates.
Well the official release date for the ICS FOTA in France is May 3rd, so I'll wait until then but having other options and the know-how to take actions is always a good basis. (plus I'm really not the patient type ^^)
Stupid question but I'm guessing EUU needs root too?
and also APX means rebooting while holding power and volume - right?
lunaticwraith said:
Well the official release date for the ICS FOTA in France is May 3rd, so I'll wait until then but having other options and the know-how to take actions is always a good basis. (plus I'm really not the patient type ^^)
Stupid question but I'm guessing EUU needs root too?
and also APX means rebooting while holding power and volume - right?
Click to expand...
Click to collapse
I tried the EUU just to see if it would keep me on my regions OTA upgrade path.
Sometimes you can have probs OTA'ing if you aren't using the rom from your region.
But in this case it gave me the correct OTA's.
APX is Acer Download mode, where the OTA upgrades are flashed - this EUU will do it via your PC. Button push method (power/reset button) not required.
No, the EUU does not need root which is why I tried it out for you
You will need to be on 3.2.1 before you will receive the ICS update
I used this EUU from vaches thread -
EUUs_SBK_Acer_A500_1.016.05_COM_GEN1
late for work will check back later
That's really helpful thanks I'm downloading the same EUU you used and will try it today or tomorrow depending on how much time I have, will keep you posted!
Ok so I did the EUU install and it worked fine, the tablet then allowed me to upgrade to 3.01 and then 3.1 then 3.2 via FOTA without any problem. But once I reached 3.2, the update tool informs me that there's no update available and my gear is up to date
So my guess is Acer France are not pushing the 3.2.1 FOTA update anymore...
Any other explanation?
lunaticwraith said:
Ok so I did the EUU install and it worked fine, the tablet then allowed me to upgrade to 3.01 and then 3.1 then 3.2 via FOTA without any problem. But once I reached 3.2, the update tool informs me that there's no update available and my gear is up to date
So my guess is Acer France are not pushing the 3.2.1 FOTA update anymore...
Any other explanation?
Click to expand...
Click to collapse
Glad to hear u got thru the EUU process OK, not so great u still can't ota to 3.2.1
Others have reported similar issues not sure if/how they were ever resolved. As moscow posted earlier,ota,s are not made available to all users in all regions, all at once, so it may be just a matter of waiting for the next "push cycle" to roll round.
At least you know you can always get back to stock if you ever decide to root and go custom There no direct root method for 3.2, just use that same euu to get back to 3.1 and use iconia root and Acer recovery installer from the market and you're ready to flash your rom of choice
Pls post back if u do get the ota - best of luck
rgds Donna
Yeah I was just browsing the XDA forums, contemplating the idea to rollback and root and then installing this
I wonder if it's worth waiting for the OTA... as for what you said about waiting for the next "push cycle" I've been waiting since I got the tablet and the update hasn't come yet, which is strange because the ICS update is due on May 3rd in France and I'd guess they'd have everyone up to date and ready for the update by now!
Rooting seems pretty straightforward and much easier than what it was on my Samsung Galaxy Spica: I found this
, a file called iconiaroot.apk on the sdcard aswell, rebooting your tablet while pushing the volume down button so its starts flashing the buggy honeycomb version.
Then start up the tablet again, rush to the market, download some file manager, with that filemanager explore your sdcard, and install the iconiaroot.apk file, once thats done, rush back to the market and download and install acer recovery installer. At that point you will have CWM (clockworkmod) installed.
Click to expand...
Click to collapse
is that all there is to it?
In any case I'll keep you posted just so it can help anyone with the same issue!
alsoe FYI and just for the anecdote: the reason I'm so cautious about everything and scared ****less of rooting is that the tablet is a present from my girlfriend for my 30th birthday, and she'll hang me with my guts if I brick it.
Ok I rooted and flashed the above-mentioned rom and it works! I'm now under 3.2.1!
Thanks to everyone who helped me! When the ICS update comes I will post here to signal how the FOTA went.
Thanks again!
Lol, good onya for taking the plunge! Yeh acer recovery installer is brilliant, along with iconia root, makes the whole process stress free.
Will be interesting to see if you get a notification for ICS OTA with that rom.
Can always flash one of the leaks if u get impatient??
Glad everything's worked out and yr g/f still talking 2 u
rgds Donna
thx! I will post here when/if I get the OTA. and my love life is safe thanksnto iconia root
okay so the ota has been rolling for over a week and a half now and still nothing for me
I bought it and it appears to have ICS because the Android version is 4.0.3 but that is all I really know right now. I expect that it was never updated OTA though because the guy I bought it off had it for 2 months and he was not the one who rooted it. I was going to leave it as is because I bought it for my 10 year old daughter...but the camera takes very blurry, kind of grainy looking pictures.
I am not afraid to root because I had a Samsung Fascinate and I loved the custom roms I downloaded to it. It had been over a year since i had the Fascinate so i am a little rusty when it comes to all if this. My problem is not knowing where to start with this A500 because I am unsure what has already been done to it.
The guy who sold it to me said he did a factory restore, but when I ran the check root app it does state that it's rooted and I figured it was because there is a app called superuser on the device. I don't know what kernal it has. I don't know if it has a bootloader and/or the version number. I don't know if it has CWM and/or the version. number.
What is the best way to proceed? By the way, the tablet is very clean with absolutely no scratches anywhere. Not a bad buy for $175 with a leather case...
Setting > About tablet. That should tell you quite a bit of info about it no?
download the acer recovery app , it will tell you what Bootloader you have and what recovery
Thanks for the replies! When I get home I will check. I don't want to brick the thing. I ordered a micro SD today and I will get it in 2 days so there is no hurry for me to proceed. Is it worth it to keep it rooted? Is the OTA ICS good enough? I don't think my daughter cares if the tablet is overclocked but if the roms are much better than stock than I would keep it rooted and then download a preferred rom.
Vintage144, in another post you specified that there is a Acer recovery beta...will I need that or would I just get the one from google play? Also when I find out which version of recovery and bootloader I have...I am not sure what to do with the information. Could AfterOta help me accomplish what I want if my goal is to try and fix her camera issue...either by going back to stock or updating the kernal and rom.
I don't want to seem like a noob but my only rooting experience was with my Fascinate which I did everything from stock. Now that I am not coming from stock, I am unsure where to go with what I have. It's like trying to get to a goal but not sure what step to start at. If I was starting from stock I could follow some of the threads here but it's not stock.
What info will I need to post here to let you guys know what is in my A500? I know that the Android version is 4.0.3 , what else will I need to post?
well the beta copy I believe is at thors tegra forum , but its by euclids brother (thats his name on xda) anyway if you've upgraded your BL it will tell you version you have and might give you accurate Recovery as well, if the device is only for your daughter and she's too young to really do anything I would stick with a stock rom and realistically I would upgrade the boot loader , why be left behind?
Theres no reason to root if you dont plan on doing anything major with it,that being said you wont be able to get a newer Boot Loader or custom recovery without it, and custom recovery is well worth the effort!
You guys are the pros so I will take your advise. I don't mind it being rooted and if there are some really nice roms I expect my daughter would like the different looks...it would seperate hers from others.
Android
4.0.3
Kernel version
2.6.39.4+
Image version
Acer_AV041_A500_RV16RB02_WW_GEN1
Build number
KJY2010lcylicious
Anything else I will get when I get home.
I would like to know how to get through all this in case I decide to get myself a A500 it's a really nice tablet.
Okay
Recovery Version: Revamped for Iconia 3.16
Bootloader Version: 3.01
With all the above information what would be my next step?
Sorry
Recovery Version: RA Revamed for Iconia 3.16
Damn auto correct!!!
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
ultramag69 said:
You're already running an older custom rom...
You have root - your words not mine...
You can download another custom rom, put it on the sd card/ internal memory and reboot into recovery. You need to wipe cache, dalvik cache and do a data wipe(factory reset) after which you can install zip from sd card. Go to the rom zip file you put there and install...
Wait until it boots...
I don't know if you're running the new ICS bootloaders or not.
BEFORE FLASHING - make a nandroid backup. If things go bad then you can go back and restore the tab to before the flash...
It's worth getting your CPUID and keeping it safe somewhere and you might think about installing the ICS bootloaders (I'd do it just to be sure I have them) but thats you're choice...
Good luck...
Click to expand...
Click to collapse
Probably want to hold off on flashing roms a second.
He's running an HC Bootloader. I'm 99% sure of this. Reason, RA Revamped 3.16 doesn't work with ICS Bootloaders. So you can install an ICS Rom, but, it has to be an ICS Rom for the HC Bootloader. And the performance under HC BL is not near as good as ICS BL.
I would do like UltraMag mentioned as far as install steps and such. It's how we install roms.
Check this thread;
http://forum.xda-developers.com/showthread.php?t=1622425 (steps 1-6)
, and install an unlocked ICS Bootloader and a CWM 7 or 7.2 recovery. Then install one of the Roms made for the ICS Bootloader.
I know AfterOTA will do some of this for you. But this thread gives a good idea of what's going on.
Thanks for your help. I will be getting my micro sd card on Friday. In the mean time I will do a bunch of reading about the things you guys told me to do...again thanks a lot. I really appreciate the help.
I am the kind of person that really wants to know what I am doing...I don't expect all the answers, I just don't want to brick this device.
Forstir9,
Moscow Desire is a great dev on this board, his information about updating the bootloader is dead on. I recommend reading the entire OP in that thread, and then re-read section listed as Automated Flashing Tools, it really helps tremendously if you are a person familiar with root, but not extremely dynamic with making these changes.
I've rooted several BN Nooks and my A500 many many times and love it. I had the Honeylicious ROM that you listed prior to what I'm currently running. KYJ had a great HC ROM with that one! Personal preference currently for me on the ICS ROM is FLEXREAPER from Civato, poster of the referenced article from MD above, you can find that ROM info here: http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1 Lots of cool features and step by step directions, which are what UltraMag69 listed in their post. There are many many different options though and I recommend reviewing several and then settling in on one when you find the one that fits your (or your daughter's) preferences best.
If you enjoy doing this and playing with the tablet your daughter may not keep it and may end up getting something different, because you may have too much fun with it...good luck, have fun, don't be scared to try things and ask questions (after you read first), and most importantly BACKUP BACKUP BACKUP...
Good luck,
-DB
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
forstir9 said:
Let me get this straight then.
1) boot into recovery and make a nandroid backup.
2) within that backup I should be able to find the CPUID on my sdcard...I will want to write this down and the write it down again somewhere else...out this number on my phone and computer...pretty much don't lose this number.
3) follow steps 1-6 from the link that Moscow Desire posted.
I am going to go with the Flexreaper rom...should I go with the extreme one or is there another Flexreaper rom that isn't extreme?
4) I think the 6 steps above will install a ICS bootloader
5) find and install the newest recovery
I only have 2 questions
How many of these steps does the Afterota app get Rid of?
Should I use the Acer recovery app to install the bootloader and/or the recovery?
Click to expand...
Click to collapse
First off. Thanks for thinking I am the "God" of the 501". Yeah, I know it pretty well.
Second, Ultramag, is is one of my right hand men. So I suggest you heed his advice well. I always trust his judgement. Am sure he has puled my arse out of the wringer a few times. Well, maybe not, but you get the picture. Some of us on XDA, support each other. That's how it is. I just noticed the bootloader version, And being one who likes flashing experimental code, well, I noticed.
So;
1. ALWAYS make a recovery backup. Then, restore it to make sure it works. (lots of people don't do this and they get fubar'd later).
2. UID. Seriously. Ok, the link on the many ways to get it. You don't want to get it, well... your;e pretty much fubar'd
http://forum.xda-developers.com/showthread.php?t=1624645
3. He has the normal, and one with a kernel you can overclock. Your choice. Really, if you don't OC, then you run the same as the original. Please don't ask me the names of Civatos roms. The extreme will be fine for you. Just don't overclock it if you don't want to. Only difference is the kernel. Not the OS.
4. Yes.
5. For recovery, I would say CWM 1.7.2. Should work for you. 1.7.0 is also ok. Publick recovery is ok too.
6. Never ran After OTA. But hear it is good when you already have ICS.
Forget AcerRecovery. You will already have bootloaders and recovery installed.
MD
Know I'll probably get a bashing out of this but there's a V1.7.3 recovery on the site that must not be named (cough, tegraowners, cough) that supports the Aroma installer - on Thor's ICS rom anyway...
Just thought I'd throw that in too...
I am ready to do a backup...it's asking me what I want to backup...it has a (X) next to the following...
Boot
System
Data
Cache
Flexrom
Is this correct the way it is?
EDIT: ignore this post I didn't see page 2 -_-
Sorry that I didn't post this in Friday...but I really want to thank everyone for their help. It went very easy and it want too much different than my fascinate.
The camera still takes grainy pictures and a few apps has sounds issues but she really likes the rom a lot.
Thanks again for the help.
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
electron73 said:
I need help! I need a stock, unmodified recovery partition image.
Anyone here with a vzw tab who DOES NOT yet have CWM installed?.
PLEASE contact me.
Thanks!
Click to expand...
Click to collapse
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
I'll check my laptop at home tonight. I believe I kept my heimdall backup before flashing cwm
Sent from my DROID BIONIC using Tapatalk 2
Just checked, mightve deleted it. Sorry man
aximtreo said:
I have one that hasn't been moded but have no idea how to get you what you want. PM me if you know how to download and send to you and I'll do my best to help.
Click to expand...
Click to collapse
Oh that would be awesome! Are you rooted? Let me find the commands in the meantime, I read somewhere it's a simple one command in terminal to extract the recovery partition into a file on sd card...
WHAT AN ORDEAL !!!!
But in the end: SUCCESS!
I managed to get my tab updated with the Verizon OTA update.
The problem is definitely CWM !!! A rude awakening is in store for everyone with the P6800 CWM installed, because it a) fails to verify the checksum of OTA files correctly on the i815, b) it thinks the tablet is a P6800, so the OTA file fails to run if it assert checks for "SCH-i815" hardware AND lastly c) modem updates don't work because the device /dev/cdma_update doesn't exist, so the modem.bin firmware_update call fails !!!
In short, I had to fumble the OTA file apart and do the update manually in two runs:
First file, kick the checksum, hardware check and modem update out, then manually run the ZIP through CWM. The zip subsequently (LUCKILY) updated the stock recovery and overwrote CWM with a new fresh stock recovery.
Second file had everything kicked out BUT the modem udpate and LTE patch, so with the STOCK recovery this file ran through just fine, updated the modem and then applied the LTE delta patch.
Phew!!!
Of course I had to manually restore root after the update, had backed up with voodoo, auto restore failed, so terminal and hacking it was...
Now I have the tab running on clean stock FD01, baseband and LTE FD01, rooted and stock recovery.
No more CWM, no more "hacking" with the ROM until some dev finally releases a "correct" CWM and at least ANY factory ODIN image is available to bring the tab back to stock if needed!!!
Kinda sick of the non-support for this tab. So much going on for the Galaxy Note and pretty much every other device. I'm starting to regret having bought this "special" Verizon version
Awesome find and great to know for whenever ics does come out. Could you please post the recovery img you got?
Sent from my DROID BIONIC using Tapatalk 2
OK after getting so many responses I decided to just post everything here in hopes that it will help others, too:
All files are here:
http://www.mywo.org:88/XDA/sch-i815/index.php
Step by step procedure to update the Verizon Tab from ..FA02 to ..FD01 build IF YOU ARE stuck with CWM installed on your tab and the original OTA fails with errors:
Upload the SCH-I815_FA02c_To_FD01.1.zip to the INTERNAL(!) SD card. This is important because CWM contains a bug that will only allow you to install from ZIPs stored on the INTERNAL SD storage.
Upload the SCH-I815_FA02c_To_FD01.2.zip to the EXTERNAL(!) (micro SD) card. This is important, because after the factory recovery is restored, it will correctly (and only) look for ZIPs on the EXTERNAL card.
Best way just copy both files to both locations
Fire up CWM and do "install from ZIP" and select SCH-I815_FA02c_To_FD01.1.zip
It should run (takes a while) and eventually tell you all is done. BOOT the tab. It should boot fine but in system it will show the new Android build FD01 but the baseband (radio) will still be the "old" one.
Now press and hold power and vol up again until you see the default Samsung recovery menu. Choose install from ZIP and select SCH-I815_FA02c_To_FD01.2.zip. This will now upgrade the baseband only. When done, reboot and enjoy being back on the "factory upgrade path" with the tab.
I hope someone more savvy than me can "fix" CWM to work properly with VZW tabs (accept the checksum, not fail the check for "SCH-i815" and provide the correct /dev file links for radio upgrades). Until then, I recommend just leaving the tab as-is and not tinkering with the ROM. Not that there is any custom ROM available anyway :-(
I also pulled the NEW factory recovery image FD01_recovery.img with the following command:
dd if=/dev/block/mmcblk0p6 of=/sdcard/FD01_recovery.img bs=4096
So in case anyone with a botched recovery wants to restore factory (Samsung 3e) recovery. This was actually the reason I had to go through all this... There is NO factory recovery image ANYWHERE to be found. I can't believe that I should be the first one ever to post one?? Anyway, hope it will help
I'm still quite new here, so I do really appreciate every click on that "thanks" button
P.S. for tinkerers and devs I also uploaded the original, untouched OTA file (0559c0e4e08e.update_SCH-I815_FA02c_To_FD01.bin) as it came from Samsung or Verizon or whatever and ended up in the /cache partition.
THANK YOU!
Electron,
You sir, are a BOSS! Thank you so very much for doing the work, and sharing it. You just made things one hell of a lot easier on me, and anyone else that follows.
Regards,
-Rob
Also want to say thanks. You rock, dude. I wouldn't have known how to revert **** on my own.
Also, I feel like we need a sticky or something for sch-i815 owners to go to for device specific stuffs, especially since there is little knowledge/info out for this device.
Sent from my Galaxy Nexus using xda premium
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
phigmeta said:
hmm i only ever installed ROM manager ... but i did root it ... problem is ... now i don't have a CWM recovery to flash the file ... any ideas?
Click to expand...
Click to collapse
You're in luck! You don't need to go through the whole ordeal because you do NOT have CWM! You can just update the regular intended way. Go into settings, about phone and then click check for system updates. If it presents you the OTA update, just do it the regular way.
My complicated "hack" is only necessary if you DO HAVE CWM installed.
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
phigmeta said:
Im sorry I did not explain well what my issue is.
I do not have CWM installed, however i did delete a few appilcations using titanium backup. This causes updates to not take. I would really like to just take it back to factory and start over (this time with less stupidity on my part)
I of course would assume that once its at factory i can then install updates again.
Right now when i try i get the "!" droid sign and a reboot
Click to expand...
Click to collapse
Hey
OK unless someone can tell us how to "make" an ODIN flashable ROM for you, here is what I would do (and please don't get scared because it sounds a bit convoluted).
First, you need to be rooted. This is obviously the case.
IMPORTANT since you don't have CWM installed yet, SAVE your factory restore.img before proceeding, this saves you a lot of hassle later!
Open the android terminal, type su (accept the prompt) and then type (or copy/paste)
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/factory_recovery.img bs=4096
Check that you have a "factory_recovery.img" file on your sd card now it should be about 8M big.
Now you're safe to install CWM from the forum, look for the other thread(s) where this is being discussed and follow the instructions for the P6800 "international" version with 3G. CWM Thread here:
http://forum.xda-developers.com/showthread.php?t=1613638&highlight=cwm&page=3
Then (thanks to nicduim!) there is a full factory (rooted) CWM image floating around on the forums here:
http://forum.xda-developers.com/showthread.php?t=1613638&page=6
Which I used to restore my tab to "almost factory" with the missing bloat apps back in place.
I have a copy on my server here: http://ww.mywo.org:88/XDA/sch-i815/ it's the "2012-05-06.22.48.58.ZIP"
unzip that and put the contents on your INTERNAL SD card in the folder clockwordmod. So on your internal SD you should have /clockworkmod/2012-05-06.22.48.58 and inside there the files boot.img, recovery.img etc.
Use CWM recovery to restore this backup. If you never used CWM before. Press power button and volume up and hold both until you see the menu screen with text. You can go up/down with the volume buttons (go slow, it's very laggy) and with the power button you "select" an option. Select the "restore from backup" option and point it to the only folder being offered, the 2012-05-06.22.48.58.
The restore takes a while, then reboot the tab. Now you're back to stock! Last thing you need to do is get rid of CWM again because in the end it's still a bit buggy and will prevent the OTA update from running properly.
Since you luckily have a backup of the factory recovery in form of that factory_recovery.img file, just install and open terminal again, type su and then type (or copy)
dd if=/mnt/sdcard/factory_recovery.img of=/dev/block/mmcblk0p6 bs=4096
This overwrites CWM with your original Samsung Android recovery.
Now you just reboot as usual, connect to the internet and wait until the popup message shows up that a system update is ready, accept it and enjoy
If you don't want to wait for the automatic OTA, you can also stop before killing CWM and use my convoluted 2-step manual update which will get you to the exact same condition as the official OTA.
Hope all this makes sense
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
AlpineMan said:
I was already on stock FD01 when I tried installing CWM for the P6800 that's floating around here somewhere. Odin said it was a success, but it looks like it didn't take. I've done it a few times, but still ended up w/ the stock recovery. However, after reading through your thread, I do not see a /dev/cdma_update in my I815 either. Is it possible that my attempt to install CWM (although unsuccessful) wiped out this file, among others?
Right now, I'm still at stock FD01 (rooted) and everything seems to be working. When I tried doing an OTA update, it just tells me that I have the latest update and no newer update is available.
One other thing, if I have to, I only have the stock recovery right now since CWM didn't take, can I simply flash both zip's using the Samsung stock recovery to put everything back in stock?
SCH-I815_FA02c_To_FD01.1.zip
SCH-I815_FA02c_To_FD01.2.zip
Click to expand...
Click to collapse
Oh wait, so you are saying that in "About device" your Android is 3.2
Baseband i815.04 V.FD01 I815FD01
and your Build number is already at HTJ85B.I815FD01.SCH-I815.I815FD01 ?
That would mean you are already updated. In this case, it should be pretty easy to fix your problem. Which apps did you delete with Titanium? I can back them up from my system and make them available for you. All you'd need to do is drop the backup files into your Titanium backups folder and then fire up titanium and restore them!
The /dev/cdma_update node is only required WITHIN CWM recovery, so that is nothing for you to worry about. The zip files above won't help you because they are incremental updates requiring your system to be at FA02, not FD01 !
Yes... I'm already in the latest update. I already backed up the bloatware using Titanium Backup before uninstalling. So I just need to restore them back in order to receive and apply OTA updates in the future?
Sent from my SPH-D710 using Xparent ICS Blue Tapatalk 2
Please Help
Hi. I'm rooted and removed all sorts of bloatware with Titanium. I did this a long time ago and did not back anything up because I'm used to running hardware with custom ROMs available, and not relying on OTA updates.
Since there aren't any custom ROMs for the i815, I'd like to get ready for the upcoming ICS update. To do so, I want to get FD01 loaded onto my device, but I can't update because I've apparently removed too much of the required bloatware.
Does anyone know WHAT pieces of bloatware I'd need to reinstall in order for the OTA update to apply? I'd assume I can restore them and then apply the update and re-root.
If anyone can help pinpoint what missing APKs might help, I'll give them a shot. And, to the extent I figure anything out, I'll repost here in the hopes that it helps someone else.
electron,
Your instructions worked ... thank you so much
@jkrell... the failed attempt at installing the update should return an error message(s). You just have to read through them until you find the culprit(s). Apparently I uninstalled a few odexed files that were needed. I couldn't update until i hunted them down and restored them.
I guess we all jumped at the opportunity to install the cwm recovery image, that we didn't even think about cmda updates....ooops. So far i had to do a complete factory restore after the update. I was getting soft bricked to the point where I had no choice. Good thing I sent all titanium backups to actual sd card, i was able to salvage 97% f my data..... with the exception of a few downloads i forgot to move.
Gamecih doesn't work anymore (either version). No more automative data hacks I'm not sure what's going on. I uninstalled adfree..used titanium backup to uninstall both versions and reinstalled both several times. Oh well.
It really sucks not having nandroid backups but it's not worth the trouble of having to do this everytime an OTA modem update gets pushed to my tab. Needless to say, I won't be odining the cwm based recovery image again.
I'm with the O.P. I wish i hadn't wasted my money on this tab. No true cwm for this tab, so no dev will ever waste thier time with this tab. The sch i815 will soon be forgotten about and some other tablet will be all the hype before summer ends....that's just how it is. 21 months left on my contract.... [email protected]#k my life. Lol
Thanks Smitty.
When I try to update, I just see the "!" logo and then the device reboots. Is there a log file somewhere I can look at to see what the errors are?
I hear ya on the gloom and doom, but this device has only been out for just over 3 months now. I'd expect a recovery and some custom ROMs to come eventually. I doubt I'll go the custom ROM route unless CyanogenMod is supported, because I have no complaints about the tablet's performance thus far. It's speedy, smooth and the battery lasts forever.
In my book, this is a great tablet and I'm satisfied with the purchase.
I live in the Houston area. Bricked my A500 will pay you to fix email me . I went from CWM v5 1.3.4 to 1.7 and now I can only go into boot loader but nothing can be applied , tried different ROMS wipe everything still nothing
[email protected]
If I lived in Houston I would try to help you, can't you get into recovery? What happens when you connect to your PC ?
twistedknickers said:
If I lived in Houston I would try to help you, can't you get into recovery? What happens when you connect to your PC ?
Click to expand...
Click to collapse
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Moscow Desire said:
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Click to expand...
Click to collapse
I have a similar problem. Bootloader V8 installed fine. But when I flashed different ROMs through CWM (install zip from SD card inside recovery), it hung at the screen "CZ's Bootloader V8, booting primary kernel" forever. Scratched my head for a couple of nights now, wondering what the glitch was. I even tried Bad Sector's V8 green. Same result. Help!!!!
Edit: I can still downgrade by flashing EUU (though not TD's V4, which installs fine but won't boot back up once I turn it off and on again???). Anyway, running HC 3.0.1 does make you feel like a Neanderthal. A clear instance of cruel and unusual punishment, I'd say. Even HC 3.2 won't stick! WTH?
Quandary unsolved
Moscow Desire said:
No kidding, I don't live there either, but to help, we need some more information.
You are probably on the HC bootloader, which is why your roms won't install.
Check the bootloader Install sticky in the dev forum. You need to upgrade it to the V8 bootloader.
Then you can install the ICS and CM10 roms.
MD
Click to expand...
Click to collapse
Hello. Anyone? How about Mockba the Great? I'll do more than thank. I'll grovel at your feet (lol); or fly to your city vodka bottle in hand. Be compassionate and tell me something. Anything. Like my tablet is shot beyond salvage, so I can put it to rest. Why is it that I can flash EUU and use without problems but not any other upgrades? Is it possibly because of physical bad sectors lying in the path of data from the new roms (sizably larger than HC)? Or automatic remapping of NAND shot to hell? There's got to be some explanation.
graphdarnell said:
Hello. Anyone? How about Mockba the Great? I'll do more than thank. I'll grovel at your feet (lol); or fly to your city vodka bottle in hand. Be compassionate and tell me something. Anything. Like my tablet is shot beyond salvage, so I can put it to rest. Why is it that I can flash EUU and use without problems but not any other upgrades? Is it possibly because of physical bad sectors lying in the path of data from the new roms (sizably larger than HC)? Or automatic remapping of NAND shot to hell? There's got to be some explanation.
Click to expand...
Click to collapse
I am not sure, but, I have the same problem. If I flash the EUU (Acer stock 3.01) , I can spend a couple of hours following the upgrade path all the way to ICS 4.03, then it seems no matter the boot loader/recovery combo I flash, I either end up stuck in APX, or I get the new boot loader/recovery, and the original Rom boots fine, but when I try to flash using fast boot I end up with the android on his back with the red exclamation.
It may or not be related, but the very first time I tried flashing a new ROM, I ended up stuck in APX, & the only way I could find to get out was to use Badsector. The next Rom I flashed left me again in APX, so, the first thing I went back to was BadSector, & it would not work. (Can't remember what the error was, but it wouldn't get far before stopping.) So, I tried APXFlash & it worked perfect. (Before I ran BadSector the first time I could not get APXFlash to work at all.)
Now I can flash as often as I want, but still can't get anything to work right. (Except Stock stuff????)
Danny2 said:
I am not sure, but, I have the same problem. If I flash the EUU (Acer stock 3.01) , I can spend a couple of hours following the upgrade path all the way to ICS 4.03, then it seems no matter the boot loader/recovery combo I flash, I either end up stuck in APX, or I get the new boot loader/recovery, and the original Rom boots fine, but when I try to flash using fast boot I end up with the android on his back with the red exclamation.
It may or not be related, but the very first time I tried flashing a new ROM, I ended up stuck in APX, & the only way I could find to get out was to use Badsector. The next Rom I flashed left me again in APX, so, the first thing I went back to was BadSector, & it would not work. (Can't remember what the error was, but it wouldn't get far before stopping.) So, I tried APXFlash & it worked perfect. (Before I ran BadSector the first time I could not get APXFlash to work at all.)
Now I can flash as often as I want, but still can't get anything to work right. (Except Stock stuff????)
Click to expand...
Click to collapse
This is my guess: I was able to get someone with the right equipment to probe into the NAND and scan. The result shows random bad sectors all over the place. The scan lasted for more than a day without finishing, so eventually remapping could not be executed. If the capability of the NAND to remap is exhausted then depending on your luck, if the ROM data fits into good sectors, you get to use the unit. If the cache partition has black holes in it, you'll get errors and operational aberrations. If I'm right, then this is purely a hardware issue which will come back to haunt sooner or later. Makes sense?
Since the NAND is soldered onto the Main Board, there is little chance of replacing the NAND, if you can find one, that is. Darn it!
graphdarnell said:
I have a similar problem. Bootloader V8 installed fine. But when I flashed different ROMs through CWM (install zip from SD card inside recovery), it hung at the screen "CZ's Bootloader V8, booting primary kernel" forever. Scratched my head for a couple of nights now, wondering what the glitch was. I even tried Bad Sector's V8 green. Same result. Help!!!!
Edit: I can still downgrade by flashing EUU (though not TD's V4, which installs fine but won't boot back up once I turn it off and on again???). Anyway, running HC 3.0.1 does make you feel like a Neanderthal. A clear instance of cruel and unusual punishment, I'd say. Even HC 3.2 won't stick! WTH?
Click to expand...
Click to collapse
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Danke schoen dibb nz
dibb_nz said:
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
This gives hope. With TD V4, it stops at power on - power lights on (white LED), but screen remains dark. Thanks for sharing your experience, I will definitely try when I get back to it at the end of the month. So if I'm slow in posting the outcomes, you know why. One more favor to ask: what do you do after fixing permissions while on earlier EUU (I remember seeing that option somewhere in the recovery menu)? Should I proceed to flash V4, then move up from there? If I install V8 Bootloader while on V4's ROM, would that hinder further flashings in any way? Many thanks again. And what is going on now with your JB ROM? And Happy Thanksgiving to all the Yanks in here!
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD
Thanks MD
Moscow Desire said:
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
So you run one of the RUUs files. That's fine. Essentially you should be back on an HC bootloader running an HC rom. At this point, all your partitions should be back in place, especially if you used TD's tool.
While you are in HC, and everything is running fine, you should make a note of your current UID number. Because, after upgrading to ICS, your UID number will probably change. (the converted SBK number should be the same with both). But the RUUs seem to mostly want an HC UID number.
The issue, is when upgrading to ICS. If you do this the normal way via OTA, you should eventually get to ICS with a stock ICS bootloader. At this point, I would leave it alone for a few days, just to make sure it runs normally. Again, get your new UID number.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
The issue, is that if you NVFlash V8 bootloader, and let's say Thor CWM 1.7.2 or 1.7.3, without deleting those aforementioned files, when you boot your tab, guess what? Hasta La Vista CWM, and mr android is on his back deader than a doornail. Not to mention you might screw up a partition or 2 along the way. And then it's back doing the whole thing again, sorta like groundhog day.
If you get Skrilax_CZ's bootloader running, then there's no real reason why you can't load a compatible CWM to flash roms.
Personally, I don't like the little 1-app-does-all. I prefer the old fashioned way. NVFlash from a command line. This way, you can see if there's errors coming up. Also, you may have better luck trying one of the older packages for the V3 or V4 bootloader. If you guys are interested, I can research my other drives in a day or so, and come up with one of the original packages. Am sure I saved it somewhere.
But if you get the V8 loaded, then you can boot it into fastboot mode. From here, you can fastboot a good CWM image. And at this point, I strongly advise CWM 1.7.2 or 1.7.3. After you fastboot it, boot immediately into CWM recovery. Do not pass go, do not collect $200, and do your wipes and formats and immediately install a custom rom. If you boot back into your stock rom, sianara..... This is why it's best to already have your custom rom.zip on your SD card.
Now, roms, kernels and bootloaders. The rom you choose to install, is pretty important. It needs to be recent, and designed for the ICS bootloader (V8). Using some of the earlier roms with kernels is asking for trouble. HC based roms WILL NOT run on an ICS bootloader. Remember that also, and vica-versa.
It's possible, however unlikely, that one of you may have unrecoverable corrupt data on your chipset. It has happened, but it's rare. Generally, you will find this when you can't get anything running. Period. Or in the case I know, the user could not migrate from HC to ICS. But only 1 or 2 people I know have had this. Oh, 3. I forgot Civato who totally cooked his internal memory (more than likely while inventing his own version of TWRP)
Wipes and formats. Again, I can't stress this enough. There have been issues using TWRP when it comes to wipes and formats. It seems, sometimes, things don't get fully wiped. So, as I always do with CWM, remember those versions I quoted), always
Wipe Data/factory reset
Wipe Cache
Wipe Dalvak
Wipe battery stats (optional)
Goto Mounts and Storage
Format System
Format Flexrom
As we say, be nice, wipe twice.....
Then install the custom rom (not a stock rom, remember the 2 recovery files?)
MD
Click to expand...
Click to collapse
Can't thank you enough MD, and dibb_nz too. Can't wait to get back to the tablet. Hopefully things will work out. When they do, I'll post the results for the perusal of similarly situated members.
graphdarnell said:
This gives hope. With TD V4, it stops at power on - power lights on (white LED), but screen remains dark. Thanks for sharing your experience, I will definitely try when I get back to it at the end of the month. So if I'm slow in posting the outcomes, you know why. One more favor to ask: what do you do after fixing permissions while on earlier EUU (I remember seeing that option somewhere in the recovery menu)? Should I proceed to flash V4, then move up from there? If I install V8 Bootloader while on V4's ROM, would that hinder further flashings in any way? Many thanks again. And what is going on now with your JB ROM? And Happy Thanksgiving to all the Yanks in here!
Click to expand...
Click to collapse
Well after u fix permissions u boot straight back into cwmand flash the v8 and civatos cm 10 flex, which is exactly what I did after getting it up n running again. edit: no, u need the latest tdv4 - ...I'll post the link for it shortly....
I'd definitely uninstall the Acer drivers and reinstall them. When u connect to yr PC , windows will try to install the drivers....don't let it search windows updates, u have to be quick to cancel it....then it should install the drivers from the acer folder on yr PC which u just reinstalled....is that clear as mud, lol???
One more thought, u could get round all this driver business if u know linux at all....
But will w8 till u get a chance to spend some quality 'tab time'
Sent from my A500 using Tapatalk 2
Moscow Desire said:
Ok, so here's a little info for you folks. Not sure if it helps you or not, but might clear up some of the mess that's been going on concerning bootloader versions VS Roms.
Now, here may be what you folks are missing.
With the introduction of ICS, Acer pulled a fast one on us. They introduced a little file called recovery-boot.p, and also a recovery.sh file.Both reside in /system (not sure exactly which folder for one of them, might be /system/etc or /system/bin.)
MD
Click to expand...
Click to collapse
So, this might seem kind of obvious, but I want to be sure. I found the Recovery-from-boot.p file easily enough, and I found a file called "Install-recovery.sh" in the etc folder, which seems to call another file called "system/bin/sh".
So, do I delete (or possibly just re-name??) "recovery-from-boot.p" and "Install-recovery.sh"? And do I need to do anything with the "SH" file in "system/bin"? (Like delete or re-name?)
Thanks for this much clearer (but still not 100% clear) info about these files. I had read mention of "recovery-from -boot.p" in another post, but it didn't make clear where to find it, just that you needed to deal with it. This excellent post makes it much more obvious which files & where to find!
Danny2 said:
So, this might seem kind of obvious, but I want to be sure. I found the Recovery-from-boot.p file easily enough, and I found a file called "Install-recovery.sh" in the etc folder, which seems to call another file called "system/bin/sh".
So, do I delete (or possibly just re-name??) "recovery-from-boot.p" and "Install-recovery.sh"? And do I need to do anything with the "SH" file in "system/bin"? (Like delete or re-name?)
Thanks for this much clearer (but still not 100% clear) info about these files. I had read mention of "recovery-from -boot.p" in another post, but it didn't make clear where to find it, just that you needed to deal with it. This excellent post makes it much more obvious which files & where to find!
Click to expand...
Click to collapse
Just those 2 files
This will prevent overwriting your custom recovery on boot.
MD
Moscow Desire said:
Just those 2 files
This will prevent overwriting your custom recovery on boot.
MD
Click to expand...
Click to collapse
OK, Thanks
Progress report
dibb_nz said:
I had similar issue in the weekend, flashed Thor's JB romv17.....stuck on same screen as you, had a heck of a job getting things working again.....
So tdv4 installed without errors but wouldn't boot, is that correct? What screen did it get stuck at? With the earlier versions of timmydeans EUU u must boot straight to cwm and "fix permissions" in the "advanced" menu options (I think its in that option)
Other than that I can't offer u any further suggestions I'm afraid....
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
I was able to follow MD's instructions and installed Re-Flexxx Rom. As to dibb-nz's advice, I couldn't find earlier versions of TD (there was a link that led to some silly software instead - hijacked?). So I reflashed V4 which after the first reboot took me to the setup part fine. However, a second reboot resulted in a dark screen with nothing doing. I tried accessing recovery in vain. I'm not sure earlier TD versions would yield differently. If I recall correctly, V4 only differs from V3 in that TD added XP drivers. Why the tablet behaved thus is beyond me. I intended this superfluous info as a warning to such possibility, however absurd it might appear.
Anyway, thanks to those who came to the rescue, and Merry Xmas to all.
graphdarnell said:
I was able to follow MD's instructions and installed Re-Flexxx Rom. As to dibb-nz's advice, I couldn't find earlier versions of TD (there was a link that led to some silly software instead - hijacked?). So I reflashed V4 which after the first reboot took me to the setup part fine. However, a second reboot resulted in a dark screen with nothing doing. I tried accessing recovery in vain. I'm not sure earlier TD versions would yield differently. If I recall correctly, V4 only differs from V3 in that TD added XP drivers. Why the tablet behaved thus is beyond me. I intended this superfluous info as a warning to such possibility, however absurd it might appear.
Anyway, thanks to those who came to the rescue, and Merry Xmas to all.
Click to expand...
Click to collapse
can u provide a link 2 the tdv4 u used i will check it.....seems couple folks having yr issue, i wanna make sure the zip isn't corrupt...
ALSO: there are 2 ways to use the EUU -
1) as an upgrade tool - used to upgrade from one HC build to the next - just open and run with usb connected and
2) as a downgrade too - used to downgrade from the ICS back to HC - you run it by not connecting your usb cable and force apx mode
Im curoius as to why folks are getting stuck with the black screen - this happened couple months back too
and tho i have been stuck with it myself - i have never been able to replicate the issue..and believe me when i say i've done some crazy things with my tab in the process of trying... so would like to rule out a bad file...just in case its me causing all the problems, lol....feedback would be appreciated....
Sent from my GT-I9300 using Tapatalk 2
Possibly corrupt V4?
dibb_nz said:
can u provide a link 2 the tdv4 u used i will check it.....seems couple folks having yr issue, i wanna make sure the zip isn't corrupt...
ALSO: there are 2 ways to use the EUU -
1) as an upgrade tool - used to upgrade from one HC build to the next - just open and run with usb connected and
2) as a downgrade too - used to downgrade from the ICS back to HC - you run it by not connecting your usb cable and force apx mode
Im curoius as to why folks are getting stuck with the black screen - this happened couple months back too
and tho i have been stuck with it myself - i have never been able to replicate the issue..and believe me when i say i've done some crazy things with my tab in the process of trying... so would like to rule out a bad file...just in case its me causing all the problems, lol....feedback would be appreciated....
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I'm almost sure I downloaded from the link provided in this thread, though I'd appreciate your not quoting me on it (lol). I remember downloading twice but cannot tell now which is which. Either way, I "upgraded" from HC 3.1 to 3.2, which is the version included in V4. Beyond that, I'm not sure what other information would help sort things out. Oddly enough, the first automatic reboot after flashing works fine and takes me through the whole setup process glitchlessly. It only happens on the following reboot. You can get into recovery 1.5, but fixing permissions won't do.
graphdarnell said:
I'm almost sure I downloaded from the link provided in this thread, though I'd appreciate your not quoting me on it (lol). I remember downloading twice but cannot tell now which is which. Either way, I "upgraded" from HC 3.1 to 3.2, which is the version included in V4. Beyond that, I'm not sure what other information would help sort things out.
Click to expand...
Click to collapse
ok thanks for that - the v0-v2 required all sorts of jumping thru hoops to get root/cwm installed....when u finished the first flash you would end up with a LNX check sum error in red text on your tab and have to boot straight to recovery and fix checksum errors (not permissions as i said earlier)
v3/v4 now comes pre-rooted with cwm 1.5, which is what may be corrupting things if you are still have the v8 bootloader - altho in saying that, a few of us have been on HC3.01 with v8 and had no probs flashing a compatible ICS v8 rom from there...maybe it was just a fluke who knows...One thing I do know is you should really have a compatible recovery with the v8 - which is why all the flash packages come pre-loaded with a custom recovery....as MD said above you need to make doubly sure your rom/reocvery/bootloader are all compatible with each other. this applies whether they be stock or custom 'whatevers'....
Oddly enough, the first automatic reboot after flashing works fine and takes me through the whole setup process glitchlessly. It only happens on the following reboot. You can get into recovery 1.5, but fixing permissions won't do.
Click to expand...
Click to collapse
and you have completed all the wipes as MD suggested, including toggling /data/media erase in cwm?
I realise you may have done everything correctly, this is more for the benefit of those folk "trying" to follow along
this is on 3.2?? you run the EUU ok, boot to android, and run thru the setup wizard, then the next reboot goes awry??
dibb_nz said:
ok thanks for that - the v0-v2 required all sorts of jumping thru hoops to get root/cwm installed....when u finished the first flash you would end up with a LNX check sum error in red text on your tab and have to boot straight to recovery and fix checksum errors (not permissions as i said earlier)
v3/v4 now comes pre-rooted with cwm 1.5, which is what may be corrupting things if you are still have the v8 bootloader - altho in saying that, a few of us have been on HC3.01 with v8 and had no probs flashing a compatible ICS v8 rom from there...maybe it was just a fluke who knows...One thing I do know is you should really have a compatible recovery with the v8 - which is why all the flash packages come pre-loaded with a custom recovery....as MD said above you need to make doubly sure your rom/reocvery/bootloader are all compatible with each other. this applies whether they be stock or custom 'whatevers'....
and you have completed all the wipes as MD suggested, including toggling /data/media erase in cwm?
I realise you may have done everything correctly, this is more for the benefit of those folk "trying" to follow along
this is on 3.2?? you run the EUU ok, boot to android, and run thru the setup wizard, then the next reboot goes awry??
Click to expand...
Click to collapse
I was initially on 3.1 stock. I went to stock recovery which proceeded to erase whatever, then showed the android belly up with the triangle exclamation mark and so forth (The sd card contained no ROM at this point). I rebooted, then flashed V4 directly from inside 3.1 with debugging on. It "PASS" uneventfully, rebooted on its own to the setup wizard. Things function normally within that capsule (it showed HC 3.2 I believe). I turned it off after setup was done, then on again to experience the black SOD. I then went to Recovery 1.5, erase everything a few times, then rebooted. Same result. Eerily dead.
Then came the V8 Bootloader and Thor V20, and the tablet was resuscitated. Works fine now.
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