Hi, there are several mentions of this subject, but none of them really addresses the issue in detail. My A510 is rooted with stock ROM. I installed Thor's recovery image. After a while I found out that there are no real custom ROMs for this tablet out there, only experimental. Now until this happens I would like to get at least the OTA firmware updates and eventually Jelly Bean as soon as it comes out from Acer.
So if I got this all right, my situation is:
1. I can't get OTA if my bootloader is unlocked
2. I can't just re-lock the bootloader via adb
3. I did install the stock recovery, but I am somehow still unlocked
4. When I try to lock/unlock the device, as soon as I push any of the Vol buttons, it says timeout
Any idea what I do wrong here?
Thanks a million for any advice!
JC
Acer Iconia A510
Android 4.0.3
Kernel 2.6.39.4+
Image version: Acer_AV041_A510_RV28RC02_WW_GEN1
Hello,
Im using a previous boot loader for the 4.1 JB versions and would like to update to the latest boot loader, i have tried to look on these forums but nothing specific about updating. I dont know what version bootloader im on but could some one guide me to the steps and where i can get the files from.
olster said:
Hello,
Im using a previous boot loader for the 4.1 JB versions and would like to update to the latest boot loader, i have tried to look on these forums but nothing specific about updating. I dont know what version bootloader im on but could some one guide me to the steps and where i can get the files from.
Click to expand...
Click to collapse
Well im assuming your unlocked, so if you flash an asus stock firmware for twrp it will upgrade the bootloader also. From memory i think i flashed the bootloader file in the energy rom thread, but i wouldnt recommend that method unless youve got access to nvflash.
I'm currently on Android 4.1.2 using Baked 6 and I want to upgrade to Baked 8, or anything on 4.2 for that matter. If I update a ROM, does this also mean it updates my bootloader? If not how to I properly update my bootloader without bricking my tablet? I've been reading around but there's so much data on the forums that I feel like I'm going to accidentally make a mistake
lifewater said:
I'm currently on Android 4.1.2 using Baked 6 and I want to upgrade to Baked 8, or anything on 4.2 for that matter. If I update a ROM, does this also mean it updates my bootloader? If not how to I properly update my bootloader without bricking my tablet? I've been reading around but there's so much data on the forums that I feel like I'm going to accidentally make a mistake
Click to expand...
Click to collapse
No flashing a custom rom will not upgrade your bootloader, only the stock asus firmwares will do this or a custom made blob file.
There are several methods to upgrade your bootloader to a JB 4.2 bootloader which can be found here or here. I prefer using the fastboot method for upgrading but up to you. Just make sure that once you've upgraded your bootloader to a 4.2 bootloader that you flash a -4.2 version of twrp or you will brick. I would suggest upgrading to JB 4.2 - 10.6.1.15.3 & twrp 2.5.0.0-4.2 as I find this more stable than 10.6.1.8 & twrp 2.4.4.0-4.2
If using the fastboot method and you need any help with any step just let me know.
Hello forum,
Device: tf300t Jb 4.2.2
I was trying new roms ( cm10.1 from surdu's, aokp r06a, franco kernel, CROMi-Xenogenesis DEODEX and others) and some of them work and others didn't really worked.
During the installations I used CWMR v6.0.1.3 and used all the standart procs like format wipe cache/dalvik etc.
Since I wasn't able to overclock with the roms that worked on my tf300t, I decided to install my initial functional rom cm10.1 > with perf kernel.
This time when I turn on the device it wont get past the initial bootscreen (black screen/white asus logo). It just loops and loops in an eternal cicle rebooting constantly.
I'm not sure if the tablet is bricked or not so I don't really know what procedure should I use to fix it... Could use some help please.
I don't really understand why some roms didn't work in the first place, I used the same procedure installing other roms and they worked fine....
They were compatible with device and jb 4.2.2 as far as I understand... I don't know what I'm missing.
Thank for your time and attention.
The best regards,
Absinto10
absinto10 said:
Hello forum,
Device: tf300t Jb 4.2.2
I was trying new roms ( cm10.1 from surdu's, aokp r06a, franco kernel, CROMi-Xenogenesis DEODEX and others) and some of them work and others didn't really worked.
During the installations I used CWMR v6.0.1.3 and used all the standart procs like format wipe cache/dalvik etc.
Since I wasn't able to overclock with the roms that worked on my tf300t, I decided to install my initial functional rom cm10.1 > with perf kernel.
This time when I turn on the device it wont get past the initial bootscreen (black screen/white asus logo). It just loops and loops in an eternal cicle rebooting constantly.
I'm not sure if the tablet is bricked or not so I don't really know what procedure should I use to fix it... Could use some help please.
I don't really understand why some roms didn't work in the first place, I used the same procedure installing other roms and they worked fine....
They were compatible with device and jb 4.2.2 as far as I understand... I don't know what I'm missing.
Thank for your time and attention.
The best regards,
Absinto10
Click to expand...
Click to collapse
I really need help dudes... I already tried a bunch of procedures here on Xda but I can't find a solution... Tried adb, installing firmwares etc... nothing works.
Here's more info:
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.9-20120809" A03
absinto10 said:
I really need help dudes... I already tried a bunch of procedures here on Xda but I can't find a solution... Tried adb, installing firmwares etc... nothing works.
Here's more info:
Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.9-20120809" A03
Click to expand...
Click to collapse
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
pjc21 said:
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
Click to expand...
Click to collapse
Thank you so much. I read your how-to tutorial and I think I already understand the process. I was a little bit confused because when I first flashed my tablet I didn't have enough experience with some android slag and definitions and I forgot which bootloader I was using.
Yesterday I couldn't install nothing via fastboot protocol but when the battery died and after charging it I was able to install other firmware(oficial) via fastboot. With the frustration, I installed WW_epaduser_10_4_2_20_UpdateLauncher, then with no success booting this I installed WW_epaduser_10_4_2_9_UpdateLauncher again.
When I read your tutorial I was very optimistic and things started to make sense... but when I tried to apply it, I couldn't install nothing via fastboot again (no blue bar) --". On the terminal it only says after clicking enter: "sending 'recovery' (7766 KB) or "erasing blah blah transfering files"..." And nothing happens...
Is it fast boot bricked? I don't understand why, there's no reason for that i guess!! Well I'll wait 'till the battery dies again and attempt to apply you tutorial once more.
Meanwhile reply please and thank you very much for the assistence
pjc21 said:
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
Click to expand...
Click to collapse
I missed one thing... I have no acess to adb too.
When I type "adb devices" no devices are found.
Thank you
pjc21 said:
The bootloader you show above is not a JB 4.2 bootloader but the very 1st asus JB 4.1 - 10.4.2.9 bootloader/firmware
You will need to upgrade your bootloader depending on which roms you would like to flash, some roms are 4.1 compliant and other are 4.2 compliant so read the rom op for info on which bootloader you need for that rom.
Have a look at my how-to in sig below for info on how to upgrade your bootloader and which recovery is safe to flash for each bootloader.
Let me know if you need any help with any steps or info.
Click to expand...
Click to collapse
Hello my friend once more
So forget the last posts I figured out the problem... So I was fastboot bricked and the only way I found to fix this was it in this post http://forum.xda-developers.com/showthread.php?t=2236885.
So I used he's bootloader.bin so I could "unbrick" my tablet and the fastboot commands. Afterwards I followed your tutorial always using "WW_epad-user-10.4.2.20" (stock firmware) and "openrecovery-twrp-2.5.0.0-tf300t-JB.blob" and everything worked fine. Installed the firmware, twrp, wipe cache/dalvik etc and flashed zip from external sd card. When I rebooted the blue bar and "signature matched" appeard on the screen and loaded just fine, but when it reboots again, the bootloop starts :'(.
This time when I entered again on the bootloader, Twrp was erased of my tablet...
Installed trwp again and on my bootloader I have this current information: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.20-20121228" A03. Fastboot commands work fine so, as far as I understand, there's still hope for poor tf300t x).
I think the problem is the bootlader.bin version but idk. Please help I'm really getting frustrated with this. I'll wait for your reply because I don't want to cause anymore damage to the device :/. Thank you
Ok from what I understand the fastboot flash brick is caused by flashing a non-4.2 version of twrp or any version of cwm on a 4.2 bootloader, but as this was not the case for you I'm not sure of why you were unable to flash via fastboot until the tab had been drained and then recharged. Sounds like similar symptoms to the fastboot flash brick but I don't think people with the fastboot flash brick are able to flash at all even after the tab has drained and been recharged.
I have not heard of anyone with the fastboot flash brick (caused by above situation) unbricking there tab with the fix you tried in the above post.
However you seem to be in a different situation - the fix you tried in your post above, I believe will flash the bootloader bin file from the fisrt ICS firmware 9.4.3.29 which I thought could not be done if you have already upgraded to a JB bootloader.
When you first flashed the bootloader.bin did you happen to take note if your bootloader had changed to 9.4.3.29?
The reason I ask this is that I have tried before to downgrade from JB to an ICS bootloader and had no luck here, I would always get a "signature mismatch" trying to go from JB to ICS - but you appear to be getting this when flashing a JB bootloader. So now thinking this may be the first breakthrough in a way to downgrade from JB to ICS.
Your device is showing that you are now on the last JB 4.1 bootloader (10.4.2.20), so first I would try and flash the system blob for 10.4.2.20 again and see if that fixes the "signature mismatch" issue.
If not I have a thoery that may or maynot work, as you are getting this "signature mismatch" issue (after flashing the bootloader.bin for ICS) when you flash a JB bootloader. You could try (at your own risk) again flashing the ICS bootloader.bin from your above post, then reboot to bootloader and check what bootloader version you then have. If your bootloader is now saying 9.4.3.29 you could then try flashing the system blob from firmware 9.4.3.29 and see if the signature mismatch issue is fixed. If so you should then be able to flash a system blob from a JB firmware.
Not sure if the above will work but try flash the JB system blob from 10.4.2.20 first and if that does not work it's up to you if you would like to try the second.
If you need a step-by-step on how to do any of this or are unsure of anything above just let me know.
pjc21 said:
Ok from what I understand the fastboot flash brick is caused by flashing a non-4.2 version of twrp or any version of cwm on a 4.2 bootloader, but as this was not the case for you I'm not sure of why you were unable to flash via fastboot until the tab had been drained and then recharged. Sounds like similar symptoms to the fastboot flash brick but I don't think people with the fastboot flash brick are able to flash at all even after the tab has drained and been recharged.
I have not heard of anyone with the fastboot flash brick (caused by above situation) unbricking there tab with the fix you tried in the above post.
However you seem to be in a different situation - the fix you tried in your post above, I believe will flash the bootloader bin file from the fisrt ICS firmware 9.4.3.29 which I thought could not be done if you have already upgraded to a JB bootloader.
When you first flashed the bootloader.bin did you happen to take note if your bootloader had changed to 9.4.3.29?
The reason I ask this is that I have tried before to downgrade from JB to an ICS bootloader and had no luck here, I would always get a "signature mismatch" trying to go from JB to ICS - but you appear to be getting this when flashing a JB bootloader. So now thinking this may be the first breakthrough in a way to downgrade from JB to ICS.
Your device is showing that you are now on the last JB 4.1 bootloader (10.4.2.20), so first I would try and flash the system blob for 10.4.2.20 again and see if that fixes the "signature mismatch" issue.
If not I have a thoery that may or maynot work, as you are getting this "signature mismatch" issue (after flashing the bootloader.bin for ICS) when you flash a JB bootloader. You could try (at your own risk) again flashing the ICS bootloader.bin from your above post, then reboot to bootloader and check what bootloader version you then have. If your bootloader is now saying 9.4.3.29 you could then try flashing the system blob from firmware 9.4.3.29 and see if the signature mismatch issue is fixed. If so you should then be able to flash a system blob from a JB firmware.
Not sure if the above will work but try flash the JB system blob from 10.4.2.20 first and if that does not work it's up to you if you would like to try the second.
If you need a step-by-step on how to do any of this or are unsure of anything above just let me know.
Click to expand...
Click to collapse
Hello once more
I just want to clarify two thing first.First, I was a little bit confused on the first reply I did. I was able to use the fastboot commands again because I used the bootloader.bin file not because the device uncharged ok? xD I made some confusion on that issue. Secondly, yes I bealive I flashed a rom only prepared for a 4.2 bootloader when I had the first jb bootlader installed (4.1 I believe). And thats what bricked my tablet.
I'm so sorry if I confused you, like I said earlier, I didn't use to understand a lot of android slag and definitions so I screwed up.
Yes I bealive it's a ICS bootloader. I'll do the proc once more and check the information on the bootloader screen and I'll let you know right away.
pjc21 said:
Ok from what I understand the fastboot flash brick is caused by flashing a non-4.2 version of twrp or any version of cwm on a 4.2 bootloader, but as this was not the case for you I'm not sure of why you were unable to flash via fastboot until the tab had been drained and then recharged. Sounds like similar symptoms to the fastboot flash brick but I don't think people with the fastboot flash brick are able to flash at all even after the tab has drained and been recharged.
I have not heard of anyone with the fastboot flash brick (caused by above situation) unbricking there tab with the fix you tried in the above post.
However you seem to be in a different situation - the fix you tried in your post above, I believe will flash the bootloader bin file from the fisrt ICS firmware 9.4.3.29 which I thought could not be done if you have already upgraded to a JB bootloader.
When you first flashed the bootloader.bin did you happen to take note if your bootloader had changed to 9.4.3.29?
The reason I ask this is that I have tried before to downgrade from JB to an ICS bootloader and had no luck here, I would always get a "signature mismatch" trying to go from JB to ICS - but you appear to be getting this when flashing a JB bootloader. So now thinking this may be the first breakthrough in a way to downgrade from JB to ICS.
Your device is showing that you are now on the last JB 4.1 bootloader (10.4.2.20), so first I would try and flash the system blob for 10.4.2.20 again and see if that fixes the "signature mismatch" issue.
If not I have a thoery that may or maynot work, as you are getting this "signature mismatch" issue (after flashing the bootloader.bin for ICS) when you flash a JB bootloader. You could try (at your own risk) again flashing the ICS bootloader.bin from your above post, then reboot to bootloader and check what bootloader version you then have. If your bootloader is now saying 9.4.3.29 you could then try flashing the system blob from firmware 9.4.3.29 and see if the signature mismatch issue is fixed. If so you should then be able to flash a system blob from a JB firmware.
Not sure if the above will work but try flash the JB system blob from 10.4.2.20 first and if that does not work it's up to you if you would like to try the second.
If you need a step-by-step on how to do any of this or are unsure of anything above just let me know.
Click to expand...
Click to collapse
I fastboot installed the bootloader.bin but I still have the following information on my bootloader: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.20-20121228" A03.
Should I proced and install a ICS firmware like WW_epaduser9_4_3_30UpdateLauncher, TWRP for ICS and then flash the WW_epaduser9_4_3_30UpdateLauncher.zip from my ext-sd card?
absinto10 said:
I fastboot installed the bootloader.bin but I still have the following information on my bootloader: Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.20-20121228" A03.
Should I proced and install a ICS firmware like WW_epaduser9_4_3_30UpdateLauncher, TWRP for ICS and then flash the WW_epaduser9_4_3_30UpdateLauncher.zip from my ext-sd card?
Click to expand...
Click to collapse
No if the bootloader is showing 10.4.2.20 then the bootloader.bin did not flash to the tab.
Did you try flash the system blob from 10.4.2.20 again?
If yes and it did not fix the mismatch issue and bootloop then maybe you could try flashing system blob from a 4.2 firmware like 10.6.1.15.3 and see if that works
pjc21 said:
No if the bootloader is showing 10.4.2.20 then the bootloader.bin did not flash to the tab.
Did you try flash the system blob from 10.4.2.20 again?
If yes and it did not fix the mismatch issue and bootloop then maybe you could try flashing system blob from a 4.2 firmware like 10.6.1.15.3 and see if that works
Click to expand...
Click to collapse
Thank you so much my friend, we've done it, she liveeeeeeesss!!
Flashing system blob from 10.4.2.20 wasn't working. Even though, signatures were matching the bootloop started again.
So I decided following your second advice flashing system blob from a 4.2 firmware, but insted using 10.6.1.15.3, I used "TF300T-WW_epad-user-10_6_1_8UpdateLauncher". Then installed Twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) and did the following steps of your tutorial (wipe/flash rom) and voila, it booted .
So let me see if I got this straight, currently I have 10_6_1_8 bootloader and 4.2.1 android right? So I can flash this rom for example:
[ROM]★●[TF300T/G/201/301][CROMi-Xenogenesis 4.6.6][ODEX/DEODEX 10.6.1.15.3]
Rom Link: http://forum.xda-developers.com/showthread.php?t=2204166
Thank you so much man!! You saved my little tablet xD
The best regards from Portugal,
Absinto10
absinto10 said:
Thank you so much my friend, we've done it, she liveeeeeeesss!!
Flashing system blob from 10.4.2.20 wasn't working. Even though, signatures were matching the bootloop started again.
So I decided following your second advice flashing system blob from a 4.2 firmware, but insted using 10.6.1.15.3, I used "TF300T-WW_epad-user-10_6_1_8UpdateLauncher". Then installed Twrp (openrecovery-twrp-2.4.4.0-tf300t-4.2.blob) and did the following steps of your tutorial (wipe/flash rom) and voila, it booted .
So let me see if I got this straight, currently I have 10_6_1_8 bootloader and 4.2.1 android right? So I can flash this rom for example:
[ROM]★●[TF300T/G/201/301][CROMi-Xenogenesis 4.6.6][ODEX/DEODEX 10.6.1.15.3]
Rom Link: http://forum.xda-developers.com/showthread.php?t=2204166
Thank you so much man!! You saved my little tablet xD
The best regards from Portugal,
Absinto10
Click to expand...
Click to collapse
Glad you got it working and happy to help. :good:
Yes with your current setup (4.2 bootloader & 4.2 twrp) you can flash CROMi-X 4.6.6
I have to upgrade my bootloader but need some advice on which version to install to upgrade.
I bought my tablet in the UK, and it was originally WW. After bricking it with a bad flash I replaced the mainboard today with a US board and on boot I found my bootloader was JOP40D.US_epad-10.6.1.15.3-20130416
I unlocked, flashed nvflash, then TWRP 2.8, KatKISS KK ROM and GApps. I'm having problems with KatKISS (neither external SD card works/mounts - same problem I had before the brick - I should have learned to stay away) so I want to leave it behind and flash the stock bootloader before moving on to another KK ROM.
The problem is that now when I boot into fastboot my bootloader is listed as WW_epad-10.6.1.15.3-20130416
How did that happen? I haven't changed my bootloader, and now I don't know whether to flash WW or US.
I really can't brick again so any advice is desperately needed.
Thanks
be4con said:
I have to upgrade my bootloader but need some advice on which version to install to upgrade.
I bought my tablet in the UK, and it was originally WW. After bricking it with a bad flash I replaced the mainboard today with a US board and on boot I found my bootloader was JOP40D.US_epad-10.6.1.15.3-20130416
I unlocked, flashed nvflash, then TWRP 2.8, KatKISS KK ROM and GApps. I'm having problems with KatKISS (neither external SD card works/mounts - same problem I had before the brick - I should have learned to stay away) so I want to leave it behind and flash the stock bootloader before moving on to another KK ROM.
The problem is that now when I boot into fastboot my bootloader is listed as WW_epad-10.6.1.15.3-20130416
How did that happen? I haven't changed my bootloader, and now I don't know whether to flash WW or US.
I really can't brick again so any advice is desperately needed.
Thanks
Click to expand...
Click to collapse
I've just re-flashed the nandroid I made before installing KatKISS and I'm back on build number: JOP40D.US_epad-10.6.1.15.3-20130416 but the bootloader is listed as WW_epad-10.6.1.15.3-20130416 still.
I'm really not sure which way to jump now? It appears my tablet is both WW and US - can anyone help at all?
SOLVED
be4con said:
I've just re-flashed the nandroid I made before installing KatKISS and I'm back on build number: JOP40D.US_epad-10.6.1.15.3-20130416 but the bootloader is listed as WW_epad-10.6.1.15.3-20130416 still.
I'm really not sure which way to jump now? It appears my tablet is both WW and US - can anyone help at all?
Click to expand...
Click to collapse
OK, so the answer it seems is that whatever your mainboard is - that's the SKU you flash, regardless of what your bootloader version is. ASUS surpisingly were the source of that info, though they declined to help any further because I had modded my device.
I seem to be the only person interested in the answer to this problem, but I thought I'd update in case someone finds themselves in the same boat as me sometime down the line and comes here looking for an answer.
I have flashed the latest ASUS US SKU, and now flashed TWRP 2.8, and both my bootloader and build are now showing as US.