Database Users

Need Help Flashing 8gb A500 (BCT problems???)

I've got a couple ICS 8GB A500's I'm trying to flash so I can do the memory swap thing with 16gb microsd's. I'm stuck at the very beginning trying to get an unlocked bootloader and clockworkmod installed.
I've followed several of the guides and they all seem to be failing at the same spot. I've done blackthund3r and afterota and V8-UNL-ICS-HC-bootloader-MULTI-cwm script with no luck.
I'm pretty sure the problem is something to do with my BCT. Running afterota to flash or blackthund3r w/o custom BCT each puts the tablet into the recovery mode but nvflash errors on a bunch of partition commands and fails to upload the images (afterota sticks on 3/5 for instance or blackthund3r hangs uploading the bootloader).
My guess is that it's because my BCT is different from the majority of every elses because I'm using the little 8gb version.
I tried blackthund3r using the extract BCT, but it simply hangs immediately after loading the bct and never gets the tablet into recovery mode. I looked at the extracted bct.dec, and it looks like the same few bytes repeated over and over (nothing like the default bct's) so I'm pretty sure that blackthund3r is failing to extract my BCT properly.
Can anyone assist me in getting a valid bct.bct for my 8gb devices so I can make some forward progress? (calling Blackthund3r if you're out there...)
Version info according to afterota. I also have the serial, cpuid, and sbk according to afterota:
Android Build: Acer_AV041_A500_1.033.00_PA_CUS1
Bootloader : 0.03.12-ICS

The only way to fix bct errors usually is to roll back to HC via timmydeans v4 or with srbeens direct nvflash command... if u have Ubuntu try nvflash with it
One thing tho is I don't know if the partitions, bct are the same for the 8gb - guess only one way to find out aye
U myt wanna look at jdgment3ls easy pass thread regarding reverting to stock
Let us know how u get on, good luck!
Sent from my GT-I9300 using Tapatalk 2

dibb_nz said:
The only way to fix bct errors usually is to roll back to HC via timmydeans v4 or with srbeens direct nvflash command... if u have Ubuntu try nvflash with it
One thing tho is I don't know if the partitions, bct are the same for the 8gb - guess only one way to find out aye
U myt wanna look at jdgment3ls easy pass thread regarding reverting to stock
Let us know how u get on, good luck!
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I tried using jdgment3ls method and that failed (I got the acer icon with the red letters about failed validation or something...can't remember).
I went with timmydeans v4 and boom...back on honeycomb. From there acer recovery got me clockwork. I also ran blackthund3r's upgrader with default bct and it worked perfectly this time so now I have a hacked ICS bootloader and clockwork recovery. As soon as the ICS rom finishes I should be back to ICS and can restore my data.
Thanks for the help.

ybarra said:
I tried using jdgment3ls method and that failed (I got the acer icon with the red letters about failed validation or something...can't remember).
Click to expand...
Click to collapse
oh, "boot recovery failed"?? thanks for testing it out, was worth a go
I went with timmydeans v4 and boom...back on honeycomb. From there acer recovery got me clockwork.
Click to expand...
Click to collapse
just a note, tdv4 has cwm pre-installed
I also ran blackthund3r's upgrader with default bct and it worked perfectly this time so now I have a hacked ICS bootloader and clockwork recovery.
Click to expand...
Click to collapse
Fantastic, pleased it worked for u
As soon as the ICS rom finishes I should be back to ICS and can restore my data.
Click to expand...
Click to collapse
ICS???? Stock???? this will overwrite yr recovery with the stock recovery??
The procedure requires u to put a rom on yr card to flash straight into after patching the BL - most folk flash one of the many custom roms - let us know please how u get on with this!!!
Thanks for the help.
Click to expand...
Click to collapse
nps thanks for posting back, will help others who may be in similar situation!!!

dibb_nz said:
oh, "boot recovery failed"?? thanks for testing it out, was worth a go
just a note, tdv4 has cwm pre-installed
Fantastic, pleased it worked for u
ICS???? Stock???? this will overwrite yr recovery with the stock recovery??
The procedure requires u to put a rom on yr card to flash straight into after patching the BL - most folk flash one of the many custom roms - let us know please how u get on with this!!!
nps thanks for posting back, will help others who may be in similar situation!!!
Click to expand...
Click to collapse
Sure, I was just trying to figure out what did or didn't work after I used tdv4. It appears that it returned my system to "normal" so all the usual tools worked like acer recovery, blackthund3r, etc. I can only speculate that maybe the out-of-the-box 8gb had a different BCT and tdv4 has set it like everyone else's now.
Yes, I returned the system to ICS Stock after validating that blackthund3r worked (it of course overwrote the bootloader). From there I rerooted it with blackthund3r and removed the .sh script that deletes custom recoveries. I then reused blackthund3r to put a patched bootloader and recovery back on. I'll probably look at custom roms later, but for now I just wanted to get to stock w/ the custom bootloader & recovery and root and then use cwm to flash the memory swap mod.
For the record, I used Titanium backup. It failed to backup and restore the Minecraft maps, pictures/videos, and one or two game settings so I lost all of that. Is there a better backup program to use before tdv4? I usually just use the one built into CWM, but obviously I couldn't get to that one before tdv4 on this unit.

[Q] Help with Acer Iconia A500 Tablet

Hello people of the forum, I am newbie with android, I've been asking for help because my tablet stopped working after I followed a tutorial to route it, I used a program "Afterota v1" tutorial here on the forum in order to install APX more now I can no longer start, he did not ask to update.zip, I do not know what it ta asking update the screen as it is in the image Please someone help me to recover it.:crying:
the picture in this link, take the space, as I am new user can not post link, thanks
http : // img43.imageshack. us/img43/8262/a500c. jpg

jinhad said:
Hello people of the forum, I am newbie with android, I've been asking for help because my tablet stopped working after I followed a tutorial to route it, I used a program "Afterota v1" tutorial here on the forum in order to install APX more now I can no longer start, he did not ask to update.zip, I do not know what it ta asking update the screen as it is in the image Please someone help me to recover it.:crying:
the picture in this link, take the space, as I am new user can not post link, thanks
http : // img43.imageshack. us/img43/8262/a500c. jpg
Click to expand...
Click to collapse
the picture looks ok...
check your external sd card - make sure there is not an "update.zip" on that or your internal "sd card"
the writing you see on yr tab is ok you should be able to just
"reboot" the tab and be all good??
try running the afterOTA again....
PS >>> oh are you trying to flash the unlocked bootloader or rollback to HC??

dibb_nz said:
the picture looks ok...
check your external sd card - make sure there is not an "update.zip" on that or your internal "sd card"
the writing you see on yr tab is ok you should be able to just
"reboot" the tab and be all good??
try running the afterOTA again....
PS >>> oh are you trying to flash the unlocked bootloader or rollback to HC??
Click to expand...
Click to collapse
Thanks for responding:good:, so I've tried using afterOTA again, although not the usb connection. I was trying to put recovery_twrp_2.1.3-ICS.img with apx mode, it restarted and gave PASS screen, but now is only on this screen, asking "update.zip", already put in external SD: Acer_AV041_A500_1.031.00_WW_GEN1.zip, FLEX-Resurrection_Rev1-Aroma-Public.zip, cwm_hc_ics_root.zip, and nothing.
I have this information:
Tablet Cpuid: 037C624341E05557
Tablet Sbk: 0x17A51E00 0x94ABD401 0x7BE23003 0x340A2103
Android Build: Acer_AV041_A500_1.031.00_WW_GEN1
Bootloader: 00:03:12 ICS-

jinhad said:
Thanks for responding:good:, so I've tried using afterOTA again, although not the usb connection. I was trying to put recovery_twrp_2.1.3-ICS.img with apx mode, it restarted and gave PASS screen, but now is only on this screen, asking "update.zip", already put in external SD: Acer_AV041_A500_1.031.00_WW_GEN1.zip, FLEX-Resurrection_Rev1-Aroma-Public.zip, cwm_hc_ics_root.zip, and nothing.
I have this information:
Tablet Cpuid: 037C624341E05557
Tablet Sbk: 0x17A51E00 0x94ABD401 0x7BE23003 0x340A2103
Android Build: Acer_AV041_A500_1.031.00_WW_GEN1
Bootloader: 00:03:12 ICS-
Click to expand...
Click to collapse
Because, you still are running a stock rom,. more or less.
The problem happens, because you are re-booting after installing the custom recovery. And the rom you are running, is booting it to stock recovery (it's overwriting your custom recovery) which explains why it's looking for update.zip
What you need to do, is after installing your custom recovery, boot immediately to it Via adb, or shut down and boot using Vol- and PWR. Then install your custom rom.
MD

Moscow Desire said:
Because, you still are running a stock rom,. more or less.
The problem happens, because you are re-booting after installing the custom recovery. And the rom you are running, is booting it to stock recovery (it's overwriting your custom recovery) which explains why it's looking for update.zip
What you need to do, is after installing your custom recovery, boot immediately to it Via adb, or shut down and boot using Vol- and PWR. Then install your custom rom.
MD
Click to expand...
Click to collapse
I understand, I'm stuck in this mode, how can I do the adb, this procedure, detroit afterOTA the folder, I have a folder with adb is this?, as does the process? Thank you.

jinhad said:
I understand, I'm stuck in this mode, how can I do the adb, this procedure, detroit afterOTA the folder, I have a folder with adb is this?, as does the process? Thank you.
Click to expand...
Click to collapse
keep in mind that flashing custom roms and recovery's REQUIRE the unlocked bootloader be flashed FIRST... I'd suggest apxFlash tool to do that....all u need is in civatos bootloader thread, pls read very carefully. do the first 4 steps and then use apxFlash tool to complete the process....if u don't do things exactly as written you'll end up in trouble....
good luck
Sent from my GT-I9300 using Tapatalk 2

SOLVED
dibb_nz said:
keep in mind that flashing custom roms and recovery's REQUIRE the unlocked bootloader be flashed FIRST... I'd suggest apxFlash tool to do that....all u need is in civatos bootloader thread, pls read very carefully. do the first 4 steps and then use apxFlash tool to complete the process....if u don't do things exactly as written you'll end up in trouble....
good luck
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Thank you friend, I managed to solve reading .. is that as I am the brail, my english ta weak and had difficulty understanding, most did all the steps and got .. Thank you.

[Q] Unable to Flash Nexus 7

hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks

Why were you trying to flash the bootloader? Were you trying to update to 4.18?

Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..

Anyway, is it normal for the bootloader flash attempt to fail?

hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.

korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...

This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.

hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked

hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?

ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help

hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first

ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?

hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.

ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild

tried to flash stock rom using wug's rootkit..
this is what happens...

hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?

Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis

I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.

hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.

[Q] Do i have this order correct to update?

So i have an A500 i rooted awhile ago.
It runs android 4.1.2
CM10
cwm bootloader 5.5.0 x thor2002ro rev 1.7
i think i installed it from cm10-flex_v6Supercharged_rev2.3_gappsIncl_public....
now i'm thinking about upgrading to android 4.4, as there seems to be one out for A500.
of course it says i need to upgrade my CWM to 6.0.4.5...
this file of course says i need to install Skrilax bootloader.
And skrilax says i need nvflash to install it.
so considering what i currently have installed, is this the correct and easiest way to go about installing a new rom`?
(i keep getting dizzy every time i try upgrading my tablet, because all these guides are soooo confusing, always referring to something that's not explained in the guides.)

well made it as far as getting the skrilex loader installed..
now i'm trying to fastboot in, and it returns
? fastboot
googling it haven't found any idea as to what is wrong

took a leap of faith.. the ? still allowed it to work..

duckforceone said:
took a leap of faith.. the ? still allowed it to work..
Click to expand...
Click to collapse
The ? means you have a connection between your pc and tab.
You are able to issue fastboot commands from yr pc. If you have a recovery.img file you can ' fastboot flash '.
The other way to flash a custom recovery is to use a 'flashable zip'. You could have used this method, by copying the zip to yr sdcard and booting to your cwm RECOVERY and using the flash zip option in the menu.
No matter tho, u sussed it out yrself, sweet
dibb
Sent from my HTC_PN071 using Tapatalk

[Q] Corrupt boot partition aka aboot

Hi all,
I want to install custom kernel on SHV-E330L, if custom kernel malfunction then phone will not boot. So i want to confirm in which state phone will be, on galaxy s4 startup logo or will not power on at all?
I think aboot and recovery both are bootable partition so it is possible is aboot is does not work then phone can boot into recovery through recovery partition or start in download mode?

Can you still access recovery and download mode?

knuckles1978 said:
Can you still access recovery and download mode?
Click to expand...
Click to collapse
I think didn't understand, i haven't done it. Before playing and bricking phone i am asking what will happen in case of boot partition not able to boot?

galliard said:
I think didn't understand, i haven't done it. Before playing and bricking phone i am asking what will happen in case of boot partition not able to boot?
Click to expand...
Click to collapse
Ahh, okay I see now. If there's a problem with your custom kernel then all you need to do is boot back into download mode which will still work, and then flash the kernel that you were using before again.
So basically, have a copy of a kernel which you know works on your PC ready, in case you have a problem and need to put it back to the way it was.
You shouldn't have a problem though, as long as the custom kernel which you want to install is for the correct android version etc, it should work fine. I've never had such a problem.

knuckles1978 said:
Ahh, okay I see now. If there's a problem with your custom kernel then all you need to do is boot back into download mode which will still work, and then flash the kernel that you were using before again.
So basically, have a copy of a kernel which you know works on your PC ready, in case you have a problem and need to put it back to the way it was.
You shouldn't have a problem though, as long as the custom kernel which you want to install is for the correct android version etc, it should work fine. I've never had such a problem.
Click to expand...
Click to collapse
Thanks for clarification, please tell me that recovery partition is also bootable so if phone can't boot from 'boot' partition so is it possible to phone to boot direct from recovery?
Also please give me an idea if you u don't mind what will b consequences if i try to install GT-I9506 kernel and modem on SHV-E330L?

galliard said:
Thanks for clarification, please tell me that recovery partition is also bootable so if phone can't boot from 'boot' partition so is it possible to phone to boot direct from recovery?
Also please give me an idea if you u don't mind what will b consequences if i try to install GT-I9506 kernel and modem on SHV-E330L?
Click to expand...
Click to collapse
You can only restart the phone from recovery, not boot from recovery. But as I mentioned above, as long as you've got download mode your phone isn't broken. You can mess up anything on your phone, as long as you don't break download mode it's recoverable. You pretty much need to do something really stupid to lose download mode.
Stupid things that could make you lose download mode and completely brick your phone include, but are not limited to: flashing a kernel made for a completely different device Or selecting repartition in Odin but not adding a PIT file.
Never install anything that isn't made for your exact device! There are exceptions, but if you don't know exactly what you're doing then you're just asking for your phone to be bricked. So don't.