Related
As always, USE AT YOUR OWN RISK. You should a fundamental understanding of how nvflash functions - if you do not, I would not recommend attempting this!
1.0.2 Link (based on TnT Lite 2.2.0): http://www.mediafire.com/?5c7is1eld6j9i6d#1
Alternative link: http://www.megaupload.com/?d=7ROU81O0
md5sum : ee3f346e602437b6a1be2336acb0b3ae
References: http://wiki.tegratab.com/index.php/Nvflash_FAQ#Entering_APX_Mode
http://forum.tegratab.com/viewtopic.php?f=6&t=8
So Why Did You Do This?
My reason for building this out was to have a newer baseline in case I needed to wipe the device using nvflash - I was just sick of seeing the TnT homescreen each time.
So What's Different in This?
- Malata bootloader with a Tegra boot image (you'll see that on bootup). Thanks to rothnic for the pic!
- Clockworkmod .08.
- Changes to ramdisk to allow adb remount to work.
- TnT Lite 2.2.0 baseline.
- NOT an update.zip. this is a compressed nvflash folder with the Windows DLL's and Linux .so's added. I have tested this on Linux only, the Windows stuff I grabbed from Malata.
So How Do I Use This?
You should have a fundamental understanding of how nvflash works, and how it could bork your system if you're not careful. I've run this several times today, but there is speculation that some devices may have a different partition structure. I'm just releasing this as an option to you, if you choose to use. But it's at your own risk!!!!!!!! Bekit has actually suggeted that you just flash things like boot and system manually (and as seen in the the tegratab link) and that might not be a bad idea. But, that would not inlude the bootloader changes.
USE AT YOUR OWN RISK, YOU HAVE BEEN WARNED
For Linux users (which is how I tested): Expand this out, open up a terminal session as root to that folder. Connect your device in APX mode. Then, run this command:
Code:
LD_LIBRARY_PATH=. ./nvflash --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go
This will wipe the bootloader, kernel and system, and then reboot. It will not wipe data.
Once it reboots, you might get a UID error - if so, reboot into clockworkmod and then fix permissions. That should correct it.
EDIT: A post that might help out Windows users: http://forum.xda-developers.com/showpost.php?p=9564270&postcount=28
Again, be very very careful with this - if I'm being redundant it's because it's important to understand what you are doing.
EDIT: 1.0.1+ versions downlevel clockworkmod back to .08, and fixes the VOLD issue. Two annoyances that I felt required a new version.
----------------------------------------------------
Archives:
1.0.1 Link: no longer needed
1.0.0 Link (based of of TnT Lite 2.0.2 + performance pack): http://www.mediafire.com/?hd6aal4857h567h
md5sum: e127b529021c4479bae5c6170c73dbd9
Soooo...
Let me see if I understood.
Compared to the previous post on TegraTab adding both folders together and then runing the bat file to the bootloader I can substitute the content of the zip instead and have TnT2.0.2 with Vega x-pack?
Also I noticed that there were 2 folders for USB Drive including one x64. Do I keep on the original format outside the folders? Or leave as it is when extracted?
Thanks
PS. Dude the moment I get the "how to install " this image this is gold in my hands
Thank you sooo much for your work bro
Edit: Just noticed the lack of a nvflash bat file. Can I use the original one?
Please, help me to understand the benefits of this new bootloader and ADB mounting?
Honestly, I have no clue how to run this in Windows. It's probably similar syntax to what I posted for Linux.
I'm not sure if previous batch files would work, as the syntax is actually different, I believe. Look at the bct and cfg file, for example - those are different than what bekit used.
This is actually 95% Malata, I just replaced the system.img and boot.img files.
flipper9 said:
Please, help me to understand the benefits of this new bootloader and ADB mounting?
Click to expand...
Click to collapse
bootloader has no real benefit, other than having a different boot image.
adb remount is nice because it makes things easier if you are using ADB to make changes to /system. It's like full su acess wihout all the workarounds.
I'm having a problem on mine getting stuck in APX mode after doing the full recovery. Was trying this file you just put up and it gets stuck at;
flash.bct sent successfully
Never goes any further.
How did you ultimately unbrick yours? Anyone have an original image I can push?
cahiatt said:
I'm having a problem on mine getting stuck in APX mode after doing the full recovery. Was trying this file you just put up and it gets stuck at;
flash.bct sent successfully
Never goes any further.
How did you ultimately unbrick yours? Anyone have an original image I can push?
Click to expand...
Click to collapse
I've been using the original Bekit nvflash recovery, which is very similar to this one except it's vanilla 1.0.0 stock (mostly). His dump always worked for me -- https://www.dropbox.com/s/wrcd87u1iy31u4e/nvflash_gtablet_2010110500.zip
Have actually done both of them (but which is the proper one). They will flash correctly and the system will boot. But when I turn it off it goes into APX mode and will not turn back on again. Have to reflash again. If I turn it off it is back in APX.
I've been following along with the TnT Lite adventures. I did this and it worked fine. Thanks for making the gtablet a very usable device. I'm not sure I will keep the performance pack, but there's a tremendous difference.
cahiatt said:
Have actually done both of them (but which is the proper one). They will flash correctly and the system will boot. But when I turn it off it goes into APX mode and will not turn back on again. Have to reflash again. If I turn it off it is back in APX.
Click to expand...
Click to collapse
Try unplugging the tablet and power cycling a few times. Once you're in APX mode, the device will go back to APX mode just from doing a recovery reboot as long as the power supply remains plugged in.
I'm not 100% sure if this is what is happening in your case since it still really shouldn't happen unless you specificially request a recovery reboot, but try unplugging the tablet after the APX flash if you haven't tried that yet.
download.bat
thx69 said:
Soooo...
Let me see if I understood.
Compared to the previous post on TegraTab adding both folders together and then runing the bat file to the bootloader I can substitute the content of the zip instead and have TnT2.0.2 with Vega x-pack?
Also I noticed that there were 2 folders for USB Drive including one x64. Do I keep on the original format outside the folders? Or leave as it is when extracted?
Thanks
PS. Dude the moment I get the "how to install " this image this is gold in my hands
Thank you sooo much for your work bro
Edit: Just noticed the lack of a nvflash bat file. Can I use the original one?
Click to expand...
Click to collapse
Is this it... download.bat was inside the package ---> "nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go
catttman said:
Is this it... download.bat was inside the package ---> "nvflash.exe" --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0xbb0c0011 --create --go
Click to expand...
Click to collapse
That should work, but be very very careful.....
Any noob friendly windows instructions?
Hey Roeby, please do not ever forget about us common folks who can not get nvflash working on their pooters
Even worse case, I was able to put CW on a micro sd, remap command and get back up through interrupting the boot-loop and forcing isntall of CW.
Now have a full CW back up of current TnT Lite 2.0 and the Nvidia 2.03 patch .. all 900mb of it (lot of apps).
I'm not planning to go to nvflash online, anytime soon. This was just a restore point for myself that I wanted to pass on.
Already used it, this morning - I found out that clockworkmod .12 sometimes give you that mismatch error, so I had my nvflash restore image to fix it.
roebeet said:
That should work, but be very very careful.....
Click to expand...
Click to collapse
I will report back tonite after I flash it
I like useing Nvflash ...saved me a lot
and shooting my apk,s back on with adb... fast and clean
Ok, I used windows to flash roebeet's backup. It was scary at first but then got better.
I initially blindly used the Download.bat file, just because it looked good. It finished successfully but I couldn't get the device to boot past the "Malata" screen. I couldn't get into recovery mode either. I was a little scared.
I put the device back into apx mode and then edited the Download.bat file so that it was just this...
"nvflash.exe --bct flash.bct --setbct --bl bootloader.bin --configfile flash.cfg --create --go"
I removed this piece " --odmdata 0xbb0c0011" Not sure what exactly it does but it wasn't in the linux command roebeet posted.
After that it worked and everything booted up normally. I'm still testing but it is looking good.
Going to have a 1.01 version of this, soon. The VOLD issue I found affects this, as well.
EDIT: Uploaded. VOLD issue fixed, and downleveled cwm back to .08 due to the "Mismatch errors" when flashing boot.img files that are not padded.
all went well
working as told... Nice
flashed 1.01 version s
Is the Camera fixed yet
first thanks to all
friend gave me a a500 to unbrick- have no history on it.
been reading and searching for days with no luck.
the only thing i can get done is loading boot loaders in apx mode, but recovery's never get on(maby they do).
i can change the boot loader to anyone i try.
the device will not boot past the acer screen.
when trying to boot or boot into recovery from skrilax_cz bootloader it gets stuck at "booting recovery kernel image" and their she stays.
i am assuming that the kernel is toast. i have tried to search to replace the kernel but have no idea what rom is on, or a guide to help me thru in apx mode.
in apx mode i have watch it successfully watch it write all the images in root-3.2.1-V4.7z
now i am just confused! lol
anyways anyone got some ideas for me?
and thanks again
If you have no issue getting the bootloader to load, and you are on ver 3 or 4, or higher, have you tried "Fastboot" to load a recovery image?
Holding Vol+ and PWR should put you into fastboot mode.
The you can start fastboot from the SDK. Should be able to do it that way to flash a recovery image.
If you install a recovery, and you reboot, and then find the recovery is not there, it's probably because you didn't delete the boot-recovery file from the stock rom after installing. Every time you boot, your recovery gets replaced by a stock acer recovery, which is useless.
Moscow Desire said:
If you have no issue getting the bootloader to load, and you are on ver 3 or 4, or higher, have you tried "Fastboot" to load a recovery image?
Holding Vol+ and PWR should put you into fastboot mode.
The you can start fastboot from the SDK. Should be able to do it that way to flash a recovery image.
If you install a recovery, and you reboot, and then find the recovery is not there, it's probably because you didn't delete the boot-recovery file from the stock rom after installing. Every time you boot, your recovery gets replaced by a stock acer recovery, which is useless.
Click to expand...
Click to collapse
the tab while booting gets stuck at "booting primary kernel image" never goes further on normal boot.
i can change the bootloader but it gets stuck on the acer loader never goes.
if i run nvflash on root-3.2.1 this is the output:
C:\Users\larry\Downloads\root-3.2.1\Image>nvflash --bct flash.bct --setbct --odm
data 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk 0x2F4
26E00 0xEB3DF106 0xAB771504 0x9EE32003 --go
Nvflash started
rcm version 0X20001
System Information:
chip name: t20
chip id: 0x20 major: 1 minor: 3
chip sku: 0x8
chip uid: 0x0380700140ffd397
macrovision: disabled
hdcp: enabled
sbk burned: true
dk burned: true
boot device: emmc
operating mode: 4
device config strap: 0
device config fuse: 0
sdram config strap: 0
sending file: flash.bct
- 4080/4080 bytes sent
flash.bct sent successfully
odm data: 0x100c0105
downloading bootloader -- load address: 0x108000 entry point: 0x108000
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
waiting for bootloader to initialize
bootloader downloaded successfully
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: GP1
creating partition: SOS
creating partition: LNX
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: FLX
creating partition: AKB
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 GP1 please wait.. done!
Formatting partition 6 SOS please wait.. done!
Formatting partition 7 LNX please wait.. done!
Formatting partition 8 APP please wait.. done!
Formatting partition 9 CAC please wait.. done!
Formatting partition 10 MSC please wait.. done!
Formatting partition 11 FLX please wait.. done!
Formatting partition 12 AKB please wait.. done!
Formatting partition 13 UDA please wait.. done!
Formatting partition 14 GPT please wait.. done!
done!
sending file: bootloader.bin
| 714385/714385 bytes sent
bootloader.bin sent successfully
sending file: recovery.img
| 5171200/5171200 bytes sent
recovery.img sent successfully
sending file: boot.img
/ 3125248/3125248 bytes sent
boot.img sent successfully
sending file: system.img
/ 629145600/629145600 bytes sent
system.img sent successfully
sending file: flexrom.img
/ 104857600/104857600 bytes sent
flexrom.img sent successfully
sending file: checksum.img
/ 10485760/10485760 bytes sent
checksum.img sent successfully
everything said successful, but then it sits on the acer screen 4ever.
is that not everything that needs to be flashed?
also i put a freshly formatted sdcard in it(didnt have one) is their any files that should be on it?<<<(sorry for the newbie question)
i glad i can get in apx mode and sill talk to it, the xooms dont have that option if **** goes bad, but no problems their
thanks again for the help.
ok i have been able to get into recovery after fixing some partions ( found a thread.
i have skrilax bootload v8 on.
in recovery i tried installing these 3 roms:
Lightspeed_4.8.zip
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT.zip
and a jelly bean rom.
i still get stuck at "booting primary kernel image.
anyone have any thoughts for me?
pleading for some direction
which recovery did you push
thanks for responding
cwm recovery v5.5.0.x(thor2002ro/digetx rev1.7.3 icconia a500x
liftman- said:
thanks for responding
cwm recovery v5.5.0.x(thor2002ro/digetx rev1.7.3 icconia a500x
Click to expand...
Click to collapse
That's the good one. My "gut" says that you may have an issue with the ICS bootloader. If it were me, I'd start over and ensure that you have the correct SBK...make double sure. Flash the recovery again in fastboot. Test that you can get into recovery through fastboot or the Power+voldown method. Once in recovery, format/wipe everything...except the sdcard of course. Flash a rom that will work with the unlocked ics bootloader.
Another thing to try is to flash twrp 2.0. as your recovery. But I've read that recovery is causing some issues with some folks. Still worth a shot though.
If you still can get it to boot. Start the process over again with a honeycomb bootloader.
Good luck.
i double check my sbk and it was ok, tried a few recoverys all went on fine except the touch screen versions.
does wm recovery v5.5.0.x(thor2002ro/digetx rev1.7.3 icconia a500x touch buttons supposed to work? this might be the reason if the touch screen is fooked. when it starts the kernel on boot i see a quick screen flick then it gets stuck, same reactions on touch screen versions of the recoverys.
little different learning curve then my xoom, bit still enjoying learning a diffent device.
Yes, the buttons in the lower right should work. You can also use swipe gesture...swipe up and down in the menu, swipe right to "enter".
Have you tried going back to a HC BL yet? Maybe the repartitioning of the ICS BL just didn't take.
thanks thanks your your help the the touch screen is broke and is the cause.
it was fun learning another tablet
love my xoom
liftman- said:
thanks thanks your your help the the touch screen is broke and is the cause.
it was fun learning another tablet
love my xoom
Click to expand...
Click to collapse
Instead of using NVFlash to install recoveries, you have some options. Fastboot
Boot V8 Bootloader to Fastboot Mode, plug into PC. Go to the Android SDK on your PC, open a command window in the folder with fastboot.exe (copy your recovery.img file there also) Then type;
Fastboot Flash Recovery nameofyourrecovery.img
The "touchscreen recoveries" are indeed a bit wonky. Sometimes you have to go slow when selecting them.
MD
Similar issue
So i recently tried to update to ics bootloader, and i ended up with skrilax_cz's bootloader V6 (0.03.14-mul).
CWM worked at first and i flashed a rom which i despise, after which point recovery ceased working.
The rom still boots.
Now when i boot into recovery either by holding the up arrow, or the down arrow and selecting recovery from menu it just gets stuck at "booting recovery image"
I can get into fastboot, but i cannot get into apx. I read somewhere that in skrilax_cz it's called debug mode, but debug mode is enabled and i'm not really sure how to tell the bootloader to go to apx mode (i've tried the reset button power button thing).
Does anyone know how to put this thing into apx mode, or how to flash a bootloader through the rom or through fastboot? Any other solutions are welcome, my end goal is to have a functioning recovery.
Thanks
soulbandaid said:
So i recently tried to update to ics bootloader, and i ended up with skrilax_cz's bootloader V6 (0.03.14-mul).
CWM worked at first and i flashed a rom which i despise, after which point recovery ceased working.
The rom still boots.
Now when i boot into recovery either by holding the up arrow, or the down arrow and selecting recovery from menu it just gets stuck at "booting recovery image"
I can get into fastboot, but i cannot get into apx. I read somewhere that in skrilax_cz it's called debug mode, but debug mode is enabled and i'm not really sure how to tell the bootloader to go to apx mode (i've tried the reset button power button thing).
Does anyone know how to put this thing into apx mode, or how to flash a bootloader through the rom or through fastboot? Any other solutions are welcome, my end goal is to have a functioning recovery.
Thanks
Click to expand...
Click to collapse
Since you have a working rom the easiest way might be to try Gersma's AfterOta tool http://forum.xda-developers.com/showthread.php?t=1675939&highlight=afterota.
Be sure to save your SBK if you don't already have it.
Also you could try Blackthund3r's APXtool. It should boot your tablet into APX mode while the rom is running. Either one should get you back on track.
JdgM3NT4L said:
Since you have a working rom the easiest way might be to try Gersma's AfterOta tool http://forum.xda-developers.com/showthread.php?t=1675939&highlight=afterota.
Be sure to save your SBK if you don't already have it.
Also you could try Blackthund3r's APXtool. It should boot your tablet into APX mode while the rom is running. Either one should get you back on track.
Click to expand...
Click to collapse
Thanks for the fast reply. I probably should have mentioned that i had tried both those tool and neither could get into apx. Blackthund3rs 'doesn't detect an apx device' and afterota chuggs along as if it is working, but it doesn't do anything other than cause my rom to optomize the programs again (i suspect it is unable to get the device into apx as neither i or blackthund3r's tool can).
soulbandaid said:
Thanks for the fast reply. I probably should have mentioned that i had tried both those tool and neither could get into apx. Blackthund3rs 'doesn't detect an apx device' and afterota chuggs along as if it is working, but it doesn't do anything other than cause my rom to optomize the programs again (i suspect it is unable to get the device into apx as neither i or blackthund3r's tool can).
Click to expand...
Click to collapse
You've got usb debugging checked I imagine... right? If you do and can use ADB you might consider installing recovery that way.
Also have you tried Acer Recovery Installer by Euclid's Brother? It is in the play store. You should be able to get a custom recovery that way.
If neither of those work I think that you might want to read timmydean's EUU thread and see if that might help you out.
soulbandaid said:
Thanks for the fast reply. I probably should have mentioned that i had tried both those tool and neither could get into apx. Blackthund3rs 'doesn't detect an apx device' and afterota chuggs along as if it is working, but it doesn't do anything other than cause my rom to optomize the programs again (i suspect it is unable to get the device into apx as neither i or blackthund3r's tool can).
Click to expand...
Click to collapse
Ok, have you tried this? Seems you're wasting your time trying all the one click tools.
Boot your tab Vol+ and PWR. If you have the skrilax_cz bootloader installed, it should boot into the boot menu. Select "Fastboot". You probably aren't going to see a bunch of bells and whistles, just at the top it says "fastboot mode".
Copy the CWM 1.7.2 or 1.7.3 image file you downloaded into your Android SDK Platform tools folder where fastboot.exe is located. (you should already have the Android SDK installed) Open a CMD window in the same folder as fastboot.exe (this should be in your platform tools folder. Plug your tab in (make sure windows recognizes it) Then type in the CMD window:
fastboot flash recovery nameofrecovery.img (where nameofrecovery is the recovery image file you are flashing)
Should work. This is why Skrilax_cz gave the bootloader fastboot capability a long time ago around version 3 or 4. Sometimes these 1 click tools just don't co-operate. Using fastboot is by far the easiest. As long as your Acer drivers are installed properly.
Also for your info:
Note that you can only install ICS roms. Forget HC. Also, you must do wipes. Most of the "animation-loop" issues are either because;
a. Wrong Bootloader-Kernel combination. (HC bootloader and ICS kernel, or, ICS bootloader and HC kernel)
b. Data was not fully wiped before installing a rom.
c. Other issues could be incompatible Recovery program. (see b)
Having the wrong or a buggy Recovery can also hang at "loading recovery image" This has happened in the past, and should be easy to fix by doing the initial steps. "should be".
Also, a corrupted file/files on the EXT SD Card may also play a factor. I advise backing up those files, format the card, then try fresh. You can always copy the files back later. Except for old recovery files. Some are not compatible with other Recovery systems.
MD
well i had to know for sure it was the touch screen, so i opened it up and unpluged the atmel board and she booted every time.
anybody have a link or price for the touch screen?
using a tablet with a usb keyboard and mouse seems silly lol
liftman- said:
well i had to know for sure it was the touch screen, so i opened it up and unpluged the atmel board and she booted every time.
anybody have a link or price for the touch screen?
using a tablet with a usb keyboard and mouse seems silly lol
Click to expand...
Click to collapse
As a matter of fact, yes...
Send a PM to Dincdoes.me
He had a cracked touch a month or so ago, and I think he found a replacement for about $70.
If it's not him, then search the forums, because somebody was replacing one not too long ago.
Link for parts breakdown;
http://forum.xda-developers.com/showpost.php?p=15326127&postcount=8
MD
thanks
i found one for about 70 also, not worth it for the price.
One of my counterparts in Germany asked me to post it here. All credit goes to opec. This has been covered a few times, but I like the detailed scenario.
**************************
ERROR: Can´t installl hacked ICS Bootloader
I tried installing Hacked ICS Bootloader in Order to get Moscow Desire´s "Alexandra V a501 ICS 4.0.3 ver 1.4 Final" running on my a501.
The following ways of flashing could get the hacked bootloader on my a501:
"Afterota for A600/G100W" (http://forum.xda-developers.com/show....php?t=1675939),
"blackthund3r´s ATX flash tool A500APXFlash.exe" (see "Automated flashing tools" at http://forum.xda-developers.com/showthread.php?t=1622425")
"Manual flashing via nvflash" (see Manual flashing at http://forum.xda-developers.com/show....php?t=1622425)
Trying to flash with this tools always brought me to a Command Promt saying:
Nvflash started
[resume mode]
APX flash tool hang when it tired to Format Partition 4 etc.
and then doing nothing even if i let it stay for hours. No Information or Error so long.
When i tried flashing manualy (see link above)i finaly saw an error:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information
e: 14) message: nverror:0x4 (0x4) flags: 0
So it seemed however that the partition table on my a501 got messed up. Asking google for "failed executing command 25 NvError 0x120002" brought me to an answer "lcd047" posted on tegraowners (http://forum.tegraowners.com/viewtop...p=15285#p15331)
He desicrbes same problem with messed up partition table an restoring it with timmyDean´s root-3.2.1-V4.7z (http://forum.xda-developers.com/show...&postcount=1):
lcd047 wrote:
"I downloaded timmyDean's root-3.2.1-V4.7z
I booted the tablet (in APX mode) and I connected the USB cable to it
in the directory root-3.2.1/Image I run the command
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk (your sbk number after converting your UID number) 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
without rebooting, I flashed the v7 bootloader and recovery as per the bootloader thread; since the partition table was restored at the previous step, the operation now succeeded;
I rebooted the tablet in recovery, and proceeded to wipe the data and flash a ROM the usual way.
And that worked for me. After flashing, my a501 did a automated reboot, i quickly killed the reboot by holding the Power Button (guessing killing the reboot is not realy necessary because the booting shouldn´t mess up the partition table again) and then brought the devive back to APX Mode (Holding Reset and Power for 3-4 sec. then releasing Power and after 1 second relesaing Reset).
Then i flashed the hacked bootloader via blackthund3rs APX flash tool (see link above).
Then i installed Alexandra V as Moscow Desire descirbes (see "To Install" at http://forum.xda-developers.com/show....php?t=1635577)
It took my 2 days of trial and error, but finaly give me a nice working Alexandra ROM on my a501!
Hope this helps people having the same issues.
Thanks to Moscow Desire, civato, blackthund3r, gersma, zeroNull, lcdß47, timmyDean
***************************************
Note from MD. You guys take note of this. Sometimes, when you get corrupted partition tables, you may have to go back to an HC stock bootloader to get them fixed. Of course there are other methods, but require some indepth knowledge, and this method most people can do easily.
MD
Borked Partition Table
Nice M...thanks for reposting this
will this work on a500
Moscow Desire said:
One of my counterparts in Germany asked me to post it here. All credit goes to opec. This has been covered a few times, but I like the detailed scenario.
Click to expand...
Click to collapse
After hours and hours, this right here was the solution I needed. Many, many thanks.
erndixon said:
After hours and hours, this right here was the solution I needed. Many, many thanks.
Click to expand...
Click to collapse
No problem. Sometimes things get buried back in the threads after awhile.
MD
Help
i'm use a501 3.2.1 stock HC and still unroot.
Now i wanna use alexV ROM, so i have flash ICS BL use blackthunder's flash tools and it's success, with V8a50pub recovery.
but my problem is:
1. still able to boot my stock HC ROM,
2. can't boot into recovery mode, it will display green robot with exclamation in its body
3. can i get guide to flash cwm recovery? i want use CWM-install-A500PubRecovery_v0.2.zip but its extension is .img and i dont know how to use it
sory if i asked noob question
thanks
Go on youtube and just search up how to root acer a500 , its the first video, steps are simple but i'm not too sure you can use pub recovery on honeycomb, after that use one of the flashing tools to install the hacked bootloader ( i prefer the apx flashtool, its fool proof pretty much with the sbk generator built in ) and download the v8 bootloader with your recovery choice and install it, there's even a guide on youtube on how to do it, hope it helps
Sent from my Iconia A501 using xda app-developers app
gigacats said:
i'm use a501 3.2.1 stock HC and still unroot.
Now i wanna use alexV ROM, so i have flash ICS BL use blackthunder's flash tools and it's success, with V8a50pub recovery.
but my problem is:
1. still able to boot my stock HC ROM,
2. can't boot into recovery mode, it will display green robot with exclamation in its body
3. can i get guide to flash cwm recovery? i want use CWM-install-A500PubRecovery_v0.2.zip but its extension is .img and i dont know how to use it
sory if i asked noob question
thanks
Click to expand...
Click to collapse
Please do not post duplicate issues in multiple threads. Please go to your original post.
MD
OK, sorry guys
Sent from my A501 using xda app-developers app
gigacats said:
OK, sorry guys
Sent from my A501 using xda app-developers app
Click to expand...
Click to collapse
No problem
Glad you got things running good. (in the other thread)
MD
Moscow Desire said:
One of my counterparts in Germany asked me to post it here. All credit goes to opec. This has been covered a few times, but I like the detailed scenario.
**************************
ERROR: Can´t installl hacked ICS Bootloader
I tried installing Hacked ICS Bootloader in Order to get Moscow Desire´s "Alexandra V a501 ICS 4.0.3 ver 1.4 Final" running on my a501.
The following ways of flashing could get the hacked bootloader on my a501:
"Afterota for A600/G100W" (http://forum.xda-developers.com/show....php?t=1675939),
"blackthund3r´s ATX flash tool A500APXFlash.exe" (see "Automated flashing tools" at http://forum.xda-developers.com/showthread.php?t=1622425")
"Manual flashing via nvflash" (see Manual flashing at http://forum.xda-developers.com/show....php?t=1622425)
Trying to flash with this tools always brought me to a Command Promt saying:
Nvflash started
[resume mode]
APX flash tool hang when it tired to Format Partition 4 etc.
and then doing nothing even if i let it stay for hours. No Information or Error so long.
When i tried flashing manualy (see link above)i finaly saw an error:
failed executing command 25 NvError 0x120002
command failure: sync failed (bad data)
bootloader status: partition table is invalid, missing required information
e: 14) message: nverror:0x4 (0x4) flags: 0
So it seemed however that the partition table on my a501 got messed up. Asking google for "failed executing command 25 NvError 0x120002" brought me to an answer "lcd047" posted on tegraowners (http://forum.tegraowners.com/viewtop...p=15285#p15331)
He desicrbes same problem with messed up partition table an restoring it with timmyDean´s root-3.2.1-V4.7z (http://forum.xda-developers.com/show...&postcount=1):
lcd047 wrote:
"I downloaded timmyDean's root-3.2.1-V4.7z
I booted the tablet (in APX mode) and I connected the USB cable to it
in the directory root-3.2.1/Image I run the command
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk (your sbk number after converting your UID number) 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
without rebooting, I flashed the v7 bootloader and recovery as per the bootloader thread; since the partition table was restored at the previous step, the operation now succeeded;
I rebooted the tablet in recovery, and proceeded to wipe the data and flash a ROM the usual way.
And that worked for me. After flashing, my a501 did a automated reboot, i quickly killed the reboot by holding the Power Button (guessing killing the reboot is not realy necessary because the booting shouldn´t mess up the partition table again) and then brought the devive back to APX Mode (Holding Reset and Power for 3-4 sec. then releasing Power and after 1 second relesaing Reset).
Then i flashed the hacked bootloader via blackthund3rs APX flash tool (see link above).
Then i installed Alexandra V as Moscow Desire descirbes (see "To Install" at http://forum.xda-developers.com/show....php?t=1635577)
It took my 2 days of trial and error, but finaly give me a nice working Alexandra ROM on my a501!
Hope this helps people having the same issues.
Thanks to Moscow Desire, civato, blackthund3r, gersma, zeroNull, lcdß47, timmyDean
***************************************
Note from MD. You guys take note of this. Sometimes, when you get corrupted partition tables, you may have to go back to an HC stock bootloader to get them fixed. Of course there are other methods, but require some indepth knowledge, and this method most people can do easily.
MD
Click to expand...
Click to collapse
So, While this did not actually work in my case, it led me to do a search on "TegraOwners" for "Partition Table damaged" where I found "BadSector" which totally fixed my problem. So, A Hearty thanks to you Moscow Desire, as well as to BlackThund3r, for without his direction, I never would found your post either.
That being said, a big thanks to all the Dev's on this site, for without their hard work, there would be no reason for any of the fine information available on this site!
Hey i have a similar problem and i cant figure it out ..heres what i get:
bootloader downloaded successfulyy
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
bootloader status: failed to create the partition <code : 10> message: nverror:0x5
<0x1000005> flags: 0
What is the problem here ?
timmydeans toolkit doesnt work for me,bad sector also doesnt work, But i can see my device in safe and remove hardware...
moizsami said:
Hey i have a similar problem and i cant figure it out ..heres what i get:
bootloader downloaded successfulyy
setting device: 2 3
creating partition: BCT
failed executing command 16 NvError 0x120002
bootloader status: failed to create the partition <code : 10> message: nverror:0x5
<0x1000005> flags: 0
What is the problem here ?
timmydeans toolkit doesnt work for me,bad sector also doesnt work, But i can see my device in safe and remove hardware...
Click to expand...
Click to collapse
If these 2 tools "don't work" there are only 2 possibilities
a) you're not doing things correctly
b) your tab has a faulty memory chip and needs a replacement motherboard
Acer a500 stock on acer logo-dead andriod red triangle
Moscow Desire said:
No problem. Sometimes things get buried back in the threads after awhile.
MD
Click to expand...
Click to collapse
Hello Sir
I have seen lots of post from you regarding Hacer a500 tab, I am not a geek nor a tech, but I do have this tab stock on Hacer logo, and when I tried to hard reset it takes me to dead andriod, please help me out here, with steps to bring back my tab back to life..thanks
I have rooted A500
Flexraper R11 - A500 gen 1
kernel 2.6.39.4
CWM v5 thorpro2002
I dicidet that was time to loos the HC bootloder.
I tried to update firs with AfterOTA 1.8 But it was stuck on 3/4 then after 20 min of nothing i removed the USB cabel reboot the tablet from APX and booted back with. Then I tryed APX flashtool it was stuck at
uploading
Click to expand...
Click to collapse
and stoped there. I tried the maual method - i got
partition formating 4
Click to expand...
Click to collapse
and that was all . I tryed diferent bundle - the same. I reinstalledt the drivers. Nothing!
the only reasenoble thing was a Solution from Moscow Desire - http://forum.xda-developers.com/showthread.php?t=1723608
But the thing bodering me is what exacly is the problem with my tablet? Is there a alternatiwe? is that the solutin for me?
This could help, I like blackthund3r's tool easy to use APX mode.
http://forum.xda-developers.com/showthread.php?t=1622425
with this tool i get Nvflash started [resume mode] and it says there
I have tryed every single method discribet without nvflash method and allways the same
NIxana said:
with this tool i get Nvflash started [resume mode] and it says there
I have tryed every single method discribet without nvflash method and allways the same
Click to expand...
Click to collapse
Try the nvflash method described by Moscow Desire. Just remember that --create command for nvflash formats whole eMMC (internal flash).
I've also had similar problem with my a500 and nothing worked (even the --create command). After couple of hours with a great help from Skrillax_CZ I've managed to boot the tablet again. The reason in my case was not corrupted parition table but the eMMC itself (bad sector in eMMC at 1MB offset). With modified parition table I was able to execute --create command and restore the tablet.
the method work like a charm no problem I installed the unlocked bootloader v8 and now I'm a happy user
I have flashed a lot of stuff, but this Iconia is driving me CRAZY.
For starters, the tablet will only boot into APX mode when you turn it on. Blank screen, but the power light is white/blue.
I DO have the SBK, which I grabbed through Ubuntu.
I try using the blackthund3r utility. It detects it in APX mode fine and pops it into the bootloader, but after that it gets stuck. This is at "Flashing Bootloader (EBT) stage two - uploading image..." The command prompt just displays Nvflash started [resume mode].
When I try running v8.bat manually from the command prompt, I usually get a lot of failed command errors which come at different points at times.
The other day I miraculously used the blackthund3r utility and handpicked some bootloader and system files and got it to boot back into Android, but when it tried updating OTA it got stuck on reboot saying the "blob update failed." Now I am back to the start of this post.
I've updated the drivers a few times and also installed the Android SDK. Everything is up to date.
If anyone has any idea what might be holding me up I could use the help. My girlfriend is mad now that I have re-destroyed her tablet after bringing it back to life and I need to get it back to her.
Have you tried using Ubuntu to run the nvflash commands, some have had luck with it where windows won't....
Srbeens guide (its stickied in the general forum) to recovering sbk via Ubuntu also has a few steps in running the nvflash commands directly from Timmy deans v4 EUU which is used to repair partitions, there might be something there u can use...
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
Have you tried using Ubuntu to run the nvflash commands, some have had luck with it where windows won't....
Srbeens guide (its stickied in the general forum) to recovering sbk via Ubuntu also has a few steps in running the nvflash commands directly from Timmy deans v4 EUU which is used to repair partitions, there might be something there u can use...
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
This is working for me up to the same point. I'm getting a "sync failed (bad data)" error and I can't format any partitions.
erndixon said:
This is working for me up to the same point. I'm getting a "sync failed (bad data)" error and I can't format any partitions.
Click to expand...
Click to collapse
k, hopefully its just your partitions messed up and not the dreaded hardware failure... you got couple options left and both of these will work from apx mode
timydeans v4 an EUU based tool which will give you a pre-rooted stock HC3.2 and cwm installed too - it will wipe everything
heres how user lcd047 went about it on his a501 but will work for a500
lcd047 wrote:
"I downloaded timmyDean's root-3.2.1-V4.7z
I booted the tablet (in APX mode) and I connected the USB cable to it
in the directory root-3.2.1/Image I run the command
nvflash --bct flash.bct --setbct --odmdata 0x100c0105 --configfile flash.cfg --create --bl bootloader.bin --sbk (your sbk number after converting your UID number) 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX 0xXXXXXXXX --go
without rebooting, I flashed the v7 bootloader and recovery as per the bootloader thread; since the partition table was restored at the previous step, the operation now succeeded;
I rebooted the tablet in recovery, and proceeded to wipe the data and flash a ROM the usual way.
And that worked for me. After flashing, my a501 did a automated reboot, i quickly killed the reboot by holding the Power Button (guessing killing the reboot is not realy necessary because the booting shouldn´t mess up the partition table again) and then brought the devive back to APX Mode (Holding Reset and Power for 3-4 sec. then releasing Power and after 1 second relesaing Reset).
Then i flashed the hacked bootloader via blackthund3rs APX flash tool (see link above).
Then i installed Alexandra V as Moscow Desire descirbes (see "To Install" at http://forum.xda-developers.com/show....php?t=1635577)
It took my 2 days of trial and error, but finaly give me a nice working Alexandra ROM on my a501!
Click to expand...
Click to collapse
The other way is by using the "babsector.rar" from the russian forums -
you can download it http://forum.xda-developers.com/showthread.php?t=2049778, theres a couple of good links in post 13 of that same thread on how to use it correctly
You don't say which rom was on the tab previously - so once the partitions are repaired and you've run the unlocked bootloader flash you'll need to immediately boot to recovery and flash an ics/jb rom ...do not try booting into android until you have done this....else you'll need to do everything all over again!!!
dibb_nz said:
k, hopefully its just your partitions messed up and not the dreaded hardware failure... you got couple options left and both of these will work from apx mode
Click to expand...
Click to collapse
Very helpful threads. Exactly the problems I was facing. Using the babsector a501a commands, I am getting a "create failed: (bad data)" and "bootloader status: fatal failure to read/write to mass storage" errors right after it creates the partitions. I am guessing that it is probably faulty memory then and it just can't write to it no matter if I am doing it correctly or not. Thanks for all your help.
erndixon said:
I am guessing that it is probably faulty memory then and it just can't write to it no matter if I am doing it correctly or not. Thanks for all your help.
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?p=49951540