[GUIDE]A500/501/G100W-Installing ICS V8 UNL-BL & CWM Or back to HC BL(24-6-2012)
- Thread starter civato
- Start date
-
- Tags
- development
I've used the backup/restore/wipe and other features in Thor's CWM 1.7 several times without any problem. I'm on ICS bl and R13. The soft keys, however, behave a little funky at times. Hard keys are OK.
Btw.: love R12.5/13. Both are running smooth, fast and with no issues on my A500.
Last edited:
Same problem
I've had this same problem for ages, no matter which of Thor's recoveries I use. I used TWRP and RA for awhile, but they have not yet updated to support ICS V3 bootloader yet. I've always assumed my data was corrupted after the restore and just rebuilt it. Nice to know it may be okay after all...
I've had this same problem for ages, no matter which of Thor's recoveries I use. I used TWRP and RA for awhile, but they have not yet updated to support ICS V3 bootloader yet. I've always assumed my data was corrupted after the restore and just rebuilt it. Nice to know it may be okay after all...
I must be one of the Stoopid ones here!!
This ain't my first android device I ever rooted or installed custom roms on, so this is really frustrating me.. I have my serial number AND I have used all the methods to pull my CPU ID from my tablet, but all the numbers I am getting are only 11 digits long.. so consequently, when I try to put the generated sdk in, I keep getting an invalid CPU ID.... Any ideas? suggestions??
Note--- I bought this tablet with the ICS leak already installed so I have NO other info about it available..
This ain't my first android device I ever rooted or installed custom roms on, so this is really frustrating me.. I have my serial number AND I have used all the methods to pull my CPU ID from my tablet, but all the numbers I am getting are only 11 digits long.. so consequently, when I try to put the generated sdk in, I keep getting an invalid CPU ID.... Any ideas? suggestions??
Note--- I bought this tablet with the ICS leak already installed so I have NO other info about it available..
Last edited:
bobsie41
Senior Member
I am running the stock ics release on my Liberty tab and everything appears to be the same as on the iconica. I have it sucessfully rooted however i am unable to boot my device into nvflash mode to install the unlocked bootloader.
Does anybody know if the procedure is the same on the liberty tab as on the Iconica?
Does anybody know if the procedure is the same on the liberty tab as on the Iconica?
Exactly the same , I'm running a G100W , make sure you reinstall acer USB drivers first and then try again , or thry the apx flash tool , look into the OP , I updated it with a apx flash package.I am running the stock ics release on my Liberty tab and everything appears to be the same as on the iconica. I have it sucessfully rooted however i am unable to boot my device into nvflash mode to install the unlocked bootloader.
Does anybody know if the procedure is the same on the liberty tab as on the Iconica?
I should probably point out that my flash tool might say "no apx devices connected" for a few seconds because it's a timer. If you're worried wait ~5 seconds and it should change it should also tell you if you need the drivers installing
I am also working on version 0.3.1 (it'll be a minor release but should iron some snags out for y'all). Use the update checker to get an idea as to when this might be out!)
Sent from my Iconia A500 using Tapatalk 2
it should also tell you if you need the drivers installing I am also working on version 0.3.1 (it'll be a minor release but should iron some snags out for y'all). Use the update checker to get an idea as to when this might be out!
)Sent from my Iconia A500 using Tapatalk 2
Last edited:
CPUID != SBK
The SBK is calculated used Vache's site FROM the CPUID
The SBK is 43 digits long (including the 3 spaces and the 0x's at the beginning of each section)
Sent from my Iconia A500 using Tapatalk 2
Thanks civ! Glad I could help
By the way did you generate the package with the kernel with my bundle builder? Because it has an MD5 check which means you can't just drop the kernel.img in (I haven't checked by the way cost I'm on my iconia
)Sent from my Iconia A500 using Tapatalk 2
Yeah I build it with your easy building tool , Thanks for that.Thanks civ! Glad I could help
By the way did you generate the package with the kernel with my bundle builder? Because it has an MD5 check which means you can't just drop the kernel.img in (I haven't checked by the way cost I'm on my iconia
Sent from my Iconia A500 using Tapatalk 2
Will update the guide then .I should probably point out that my flash tool might say "no apx devices connected" for a few seconds because it's a timer. If you're worried wait ~5 seconds and it should change
I am also working on version 0.3.1 (it'll be a minor release but should iron some snags out for y'all). Use the update checker to get an idea as to when this might be out!
Sent from my Iconia A500 using Tapatalk 2
This returns the system stats, but fails because there is no file named bootloader.img.
The file in the ZIP is named bootloader.bin
When I follow the instructions, it just sits at "Nvflash started"
The 1.bat file does reference the correct filename of bootloader.bin.
awesomeness
Well waiting a few days certainly pays off...still not got OTA..so used the tool to flash me sum ice creamy goodness. Ended up on 12,5, my god hc is so last year... nice work civ...now I find some nice new bundles to play round with....oh I am so not going to back to work for next few days thank u Sir Civato
Well waiting a few days certainly pays off...still not got OTA..so used the tool to flash me sum ice creamy goodness. Ended up on 12,5, my god hc is so last year... nice work civ...now I find some nice new bundles to play round with....oh I am so not going to back to work for next few days
thank u Sir Civato
This question is been answered , but one more time as I know you want to be 100% sure.
If you do the test (to check your sbk is correct , not actual flashing anything) and you get the system information you are good to go , don't mind the fail on bootloader.bin at the end. If you see your cpuid in the information you are good to go.
u r the man...and civ....and all the devs workin hard out
Very clever Indeed. Had no probs. You do some pretty amazing stuff, am I pleased u chose the acer
I should probably point out that my flash tool might say "no apx devices connected" for a few seconds because it's a timer. If you're worried wait ~5 seconds and it should change
I am also working on version 0.3.1 (it'll be a minor release but should iron some snags out for y'all). Use the update checker to get an idea as to when this might be out!
Sent from my Iconia A500 using Tapatalk 2
Very clever Indeed. Had no probs. You do some pretty amazing stuff, am I pleased u chose the acer
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
10
Finally had some time to write up on the Linux guide. It's not so much of a guide, but more pointers to the correct working linux nvflash binary and some common sense.
1. There is no need for special APX drivers! Everything works like it is.
2. These additions to /etc/udev/rules.d/51-android.rules might help:
You need to restart udev if you added this.Code:SUBSYSTEM=="usb", ATTR{idVendor}=="0502",ATTR{idProduct}=="3325", MODE="0666", SYMLINK+="a500" SUBSYSTEM=="usb", ATTR{idVendor}=="0955",ATTR{idProduct}=="7820", MODE="0666"
3. The working nvflash tool can be downloaded from nvidia via this link:
http://developer.download.nvidia.com/assets/mobile/files/tegra-linux-12.alpha.1.0.tar.gz
4. If for whatever reason the above link becomes outdated, the official Linux 4 Tegra page, pointing to the latest Linux 4 Tegra tools is here:
http://developer.nvidia.com/tegra-250-tango-development-kits
5. Drop the nvflash binary beside the windows nvflash.exe (they won't bite) and create your own a500.sh file something like this (inspect the original a500.bat for the actual bin and image file names) depending on your needs and wishes:
Code:#!/bin/sh ./nvflash --bct bct.bct --setbct --bl bootloader.bin --configfile flash.cfg --odmdata 0x300d8011 --sbk 0xXXXXX 0xXXXXX 0xXXXXX 0xXXXXXX --sync ./nvflash -r --format_partition 4 ./nvflash -r --download 4 ics_boot_unlk_V3.bin ./nvflash -r --format_partition 6 ./nvflash -r --download 6 recovery_thor17_403.img ./nvflash -r --go
In APX mode, the screen is black but you should see a new usb device with the following id's with lsusb:
Code:$ lsusb ... Bus 002 Device 005: ID 0955:7820 NVidia Corp.
Hope this helps.4Remember this line of the guide
You can also flash the full leaked version of 1.031.00 but then you need to get root so you can delete "recovery-from-boot.p" from /system before you flash the unlocked booloader and custom recovery.
If you flashed the full leak version you need to delete "recovery-from-boot.p" from /system if you don't do that recovery will be replaced everytime you reboot your tablet.
44
Was what I was thinking , I used the uid from my first nandroid backup when it was still a PackardBell HC 3.0.1 rom from the G100W.
But still want them to test there SBK before they complain it got stuck.
