[Q&A] Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G) - Nexus 7 Q&A, Help & Troubleshooting

Q&A for Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Flatline - Unbrickable Nexus 7 (Wi-Fi + 3G). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Where do saved files go?
Hello,
Before I bricked my N7 - I saved off all files per the instructions.
After the 'accident' - I can't find the files.
Can you tell me some of the usual locations that I can look - they are not under the \program files...\dir.
The tool told me the files had been saved off before I proceeded - I didn't double-check at the time since I thought all was well.
=== (from another post)
N7 Bricked
Hello,
My N7 bricked as well - stuck in APX mode. Don't know if the SBK is based on the CPU ID or not, and what the correct algorithm would be to recover it.
I did do a backup with NRT before all of this happened - but I can't seem to find those files at the moment.
I also got the 'too many links' message when I tried to flash the N7. It tried to boot; appeared to be running fine; and then did a screen blank; looked like one of the old
b&w TV's.
I did find the following mentioned elsewhere on this site - and I think it describes what may have happened when I was trying to get my N7 out of the infinite boot loop.
==
...the newly flashed BOOTLOADER inherits the crypto-signed details of the pre-existing BOOTLOADER, which exists (or FASTBOOT wouldn't work) and is 'tied' to that specific Nexus 7 via a unique ID.
But if the flash goes wrong, say as a result of a bad USB connection... the old BOOTLOADER is partially/wholly erased, the replacement may successfully flash, but FAILS to acquire the SECURE BOOT KEY (SBK) from the old BOOTLOADER.
The new BOOTLOADER then fails its crypto-sign in check against the Nexus 7's unique device ID when the device is next booted...
===
I did ask NVidia about this - they said I have to talk to ASUS. I have done that and they want $100 for the RMA. Since I got this N7 at the ESC 2103 Android Seminar/Certification Class -
I wonder if it'll cost more to fix once ASUS gets it.
Does anyone know how the SBK is generated for the N7? I get this with nvflash:
e:\NVPACK\Android_OS_Images\Pluto\android_k_pluto_ os_image-17.0r0>nvflash.exe --wait --bct
flash_encrypt_encrypt_encrypt.bct --setbct --odmdata 0x40098008 --configfile flash.cfg --
create --bl bootloader_encrypt.bin --go
Nvflash 3.10.1700 started
chip uid from BR is: 0x0000000000000000015d28569018120c
rcm version 0X4
Command send failed (usb write failed)
I encrypted bct and bootloader_encrypt.bin with this SBK:
0x76B66E00 0x6B991000 0x6362F302 0x9C266D03
but I do not know if that is accurate.
Does NRT have the capability to save off the SBK someplace? Just wondering.
===== talked to ASUS today - they want $200 for the RMA.
Thanks in advance,
jwestmoreland

jwestmoreland said:
Hello,
Before I bricked my N7 - I saved off all files per the instructions.
After the 'accident' - I can't find the files.
Can you tell me some of the usual locations that I can look - they are not under the \program files...\dir.
The tool told me the files had been saved off before I proceeded - I didn't double-check at the time since I thought all was well.
Click to expand...
Click to collapse
The files are saved onto your device, the instructions we provide then tell you to grab those files off your device and store them somewhere safe.
jwestmoreland said:
...the newly flashed BOOTLOADER inherits the crypto-signed details of the pre-existing BOOTLOADER, which exists (or FASTBOOT wouldn't work) and is 'tied' to that specific Nexus 7 via a unique ID.
But if the flash goes wrong, say as a result of a bad USB connection... the old BOOTLOADER is partially/wholly erased, the replacement may successfully flash, but FAILS to acquire the SECURE BOOT KEY (SBK) from the old BOOTLOADER.
The new BOOTLOADER then fails its crypto-sign in check against the Nexus 7's unique device ID when the device is next booted...
Click to expand...
Click to collapse
The newly flashed bootloader doesn't inherit anything. The bootloader is encrypted with the SBK during the flashing process. The SBK is handled at a lower level (from bootrom) and is actually a hardware security feature.
There is also no "partial flashing" that occurs. A blob has integrity checks (signatures) which are ignored when using flatline and checksums (not ignored ever) before a flash begins. Usually if the sigcheck fails the bootloader will not flash. Our secret sauce means this signature check never happens, but before a blob is flashed its checksum is verified. This remains in tact even with our methods, and we would never ignore it because it is pretty reckless to allow such a dangerous operation to occur without safeguards.
If a bad upload due to say a bad usb connection occurred the device would reject the image and not flash it. Also as explained before the SBK is not acquired by the new bootloader. The SBK is burned into a one time programmable e-fuse.
jwestmoreland said:
I did ask NVidia about this - they said I have to talk to ASUS. I have done that and they want $100 for the RMA. Since I got this N7 at the ESC 2103 Android Seminar/Certification Class -
I wonder if it'll cost more to fix once ASUS gets it.
Click to expand...
Click to collapse
Of course they did. nVidia are the chip manufacturer not the ODM. They provide guidelines for the ODM's to integrate nvflash for recovery and bringup but ultimately once they have sold the chip to ASUS it is up to them to implement and no longer in nV's hands.
jwestmoreland said:
Does anyone know how the SBK is generated for the N7?
Click to expand...
Click to collapse
No. nVidia supply a set of guidelines but whether or not they were followed we do not know. For instance the Acer Iconia A500 used an algorithm based off the chipid which leaked .
jwestmoreland said:
I get this with nvflash:
e:\NVPACK\Android_OS_Images\Pluto\android_k_pluto_ os_image-17.0r0>nvflash.exe --wait --bct
flash_encrypt_encrypt_encrypt.bct --setbct --odmdata 0x40098008 --configfile flash.cfg --
create --bl bootloader_encrypt.bin --go
Nvflash 3.10.1700 started
chip uid from BR is: 0x0000000000000000015d28569018120c
rcm version 0X4
Command send failed (usb write failed)
I encrypted bct and bootloader_encrypt.bin with this SBK:
0x76B66E00 0x6B991000 0x6362F302 0x9C266D03
but I do not know if that is accurate.
Click to expand...
Click to collapse
Just picking a random sbk is futile. There are 6.27 * 10^57 possible keys. The chances of picking it at random are very very slim. the 0x4 error is because when you encrypt with the wrong key the bootrom will not have a bar of it and shuts down the USB port. Also bct and bootloader are not enough. There is a first stage bootstrap which also requires encrypting. The process is rather complicated.
jwestmoreland said:
Does NRT have the capability to save off the SBK someplace? Just wondering.
Click to expand...
Click to collapse
No

I've seen discussion of this as well - the 'too many links' error or message popped up when using NRT - I've seen posts that said it was nothing to worry about - but
I guess in this case it did appear to be something to worry about.
The N7 did boot the new image - all looked fine for a few minutes. The screen did one of those things that looked like an old B&W TV losing the channel - then poof. The N7 was in APX/brick mode.
Have you heard of anything like that happening?
Oh, and ASUS wants $200 - not $100. The $100 is apparently just for a battery fix. They will swap the MB for $200. A new N7 can be ordered off of Amazon cheaper than that - plus a new (or used)
MB can be acquired via eBay for much less than that.
lilstevie said:
The files are saved onto your device, the instructions we provide then tell you to grab those files off your device and store them somewhere safe.
The newly flashed bootloader doesn't inherit anything. The bootloader is encrypted with the SBK during the flashing process. The SBK is handled at a lower level (from bootrom) and is actually a hardware security feature.
There is also no "partial flashing" that occurs. A blob has integrity checks (signatures) which are ignored when using flatline and checksums (not ignored ever) before a flash begins. Usually if the sigcheck fails the bootloader will not flash. Our secret sauce means this signature check never happens, but before a blob is flashed its checksum is verified. This remains in tact even with our methods, and we would never ignore it because it is pretty reckless to allow such a dangerous operation to occur without safeguards.
If a bad upload due to say a bad usb connection occurred the device would reject the image and not flash it. Also as explained before the SBK is not acquired by the new bootloader. The SBK is burned into a one time programmable e-fuse.
Of course they did. nVidia are the chip manufacturer not the ODM. They provide guidelines for the ODM's to integrate nvflash for recovery and bringup but ultimately once they have sold the chip to ASUS it is up to them to implement and no longer in nV's hands.
No. nVidia supply a set of guidelines but whether or not they were followed we do not know. For instance the Acer Iconia A500 used an algorithm based off the chipid which leaked .
Just picking a random sbk is futile. There are 6.27 * 10^57 possible keys. The chances of picking it at random are very very slim. the 0x4 error is because when you encrypt with the wrong key the bootrom will not have a bar of it and shuts down the USB port. Also bct and bootloader are not enough. There is a first stage bootstrap which also requires encrypting. The process is rather complicated.
No
Click to expand...
Click to collapse

Error 3 on wheelie command
Code:
C:\Users\Anton\AppData\Local\Android\android-sdk\platform-tools\nvflash-tools-wi
n32>wheelie --blob blob.bin
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d4a8220240205
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
[-] Error 3 sending command
My device bricked by itself when I was just transferring a big file from my tablet to PC. I backed up my blob files months ago and now im stuck with this.

@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img

nervChris said:
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
Click to expand...
Click to collapse
hey hello, sorry for the late answer, but it doesn't matter as whatever i try to flash ends up in a FAILED <FileWriteFailed> message (bootloaders, recoverys, stock images etc ... )

nervChris said:
@Homurato
bootloader-grouper-4.23.img is the current bootloader version,
on your pics i see you flash bootloader-grouper-3.41.img
proper custom recovery twrp-2.8.6.0-grouper.img
Click to expand...
Click to collapse
the problem is that i cannot flash anything, i always get a FileWriteFailed

Related

P7510 (Wifi only) bricked, need NVFlash config +bootfiles to --create

Hi, My Galaxy Tab 10.1 is so far in its Sleep of Death that only the APX connection works (believe me, battery draining, holding Power button, getting into recovery, etc: it doesnt work).
Through NVflash, i can get its partition table and read all partitions 2-17 to .img files, but i can't recreate the entire filesystem because i don't have the right nvflash configfile (mostly named flash.cfg) and i presume i need a fresh bootloader file because i think the bootloader is hosed.
Can anyone help find me these files? Thanks
I had the same thing happen to my Tab.
I eventually sent it back to a Samsung service centre and they fixed it for me.
I was a bit worried because I had flashed an ICS ROM on it but they fixed it FoC and returned it to me. The whole process was really fast taking under a week.
pwhooftman said:
Hi, My Galaxy Tab 10.1 is so far in its Sleep of Death that only the APX connection works (believe me, battery draining, holding Power button, getting into recovery, etc: it doesnt work).
Through NVflash, i can get its partition table and read all partitions 2-17 to .img files, but i can't recreate the entire filesystem because i don't have the right nvflash configfile (mostly named flash.cfg) and i presume i need a fresh bootloader file because i think the bootloader is hosed.
Can anyone help find me these files? Thanks
Click to expand...
Click to collapse
Pershoot has them posted..
Http://droidbasement.com/db-blog
I/O recovery fast boot/nvflash in the middle of the page..
Hope this helps..
Sent from my SPH-D710 using xda premium
z31k said:
Pershoot has them posted..
Http://droidbasement.com/db-blog
I/O recovery fast boot/nvflash in the middle of the page..
Hope this helps..
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Hi, thanks for your help. Unfortunately i already flashed the stock recovery to partition 8, but i need at least the BCT & EPT partition contents, plus a cfg file which tells Nvflash how to recreate the partiitons from scratch. Off it goes to the repair centre, i hope it will return soon.
VERY similar problem
pwhooftman said:
Hi, thanks for your help. Unfortunately i already flashed the stock recovery to partition 8, but i need at least the BCT & EPT partition contents, plus a cfg file which tells Nvflash how to recreate the partiitons from scratch. Off it goes to the repair centre, i hope it will return soon.
Click to expand...
Click to collapse
Have you gotten anywhere with this? I'm in almost the exact same position with my I/O P7510
ayresd54 said:
Have you gotten anywhere with this? I'm in almost the exact same position with my I/O P7510
Click to expand...
Click to collapse
This is all original stuff from I/O tab https://www.dropbox.com/sh/ny5d3iu4mttfhgn/qOQ1IIRnzJ/tab1_3.0.1 hope you can cherry pick what you need from there (It's uploading now as I send this, give it a while to all be there)
If i have locked boot loader how to do this commands
stinky73 said:
This is all original stuff from I/O tab https://www.dropbox.com/sh/ny5d3iu4mttfhgn/qOQ1IIRnzJ/tab1_3.0.1 hope you can cherry pick what you need from there (It's uploading now as I send this, give it a while to all be there)
Click to expand...
Click to collapse
thank you,I downloaded your link files but is it for gt-p7510 32G
I have the same problem metioned above because i repartitioned internal storage with adb shell
but my tab has locked bootloader (0x4 error ) "so can't apply the above commands" and right now the only thing that i can see is apx mode with black screen
draining battery method not worked for me... i took it to center that provide jtag service but he said cant rewrite files "access denied"
so, after two weeks searching and trying my tab still dead. I live in Syria and we have somehow civil ware or revolution and most of people run out the country so i don't know where or how to fix it :crying: :crying:
I had a similar issue with my 4g 7500, just googled the crap out of it and repartitioned and fixed it. Took at least 10 flashes to fix
Sent from my GT-P7500 using xda app-developers app
If you have the eMMC brick bug with a locked bootloader the only way to fix this is to have it repaired by an official Samnsung service center (someone with access to the bootloader). None of the methods that were posted in the long threads will work nor have been reported to work if your bootloader is locked. In many cases it looks like the Samsung repair centers opted to replace hardware rather than flash the bootloader as many people reported their devices coming back with different chip IDs.
There was another soft brick issue before the eMMC brick bug appeared. With this issue it was possible to used the methods described in various threads to fix it (such as the battery drain method) regardless of whether the bootloader is locked or not. These methods do not fix the eMMC brickbug.
This is a long shot.
I also have the regular retail 16GB GT-P7510UW which sleeps the deep sleep of death. So far I tried everything on here, even replaced the battery with a brand new one. But still I can only access it in APX mode.
My Tab is not locked, so I don't get the 0x04 error with nvflash. But it looks like something is messed up pretty bad, in any case, the files from the I/O version do not work.
Does anyone have all the nvflash files and tables for the 16GB version? What parts would I have to rebuild to at least get access to Odin?
I would love to see that old thing live again, so help would be very much appreciated. Thank you very much!
With the C:\nvflash>nvflash --bl bootloader.bin --go command I get 13 lines of system information and then this:
downloading bootloader -- load address: 0x108000 entry point: 0x108000
download command failed NvError 0x120002
command failure: bootloader download failed (bad data)
bootloader status: Bct file not found (code: 21) message: flags: 1073840124
It's the same error with part8.img.

[Q] urgent! stuck in bootloop, how to save data? (cwm? nvflash?)

my rooted stock ics (not cm) thinkpad decided to stuck in the boot screen (lenovo sign) and i wonder if i can do anything to save data (from internal sd, but also all app data i would be happy to have). perhaps cwm can be installed still in some way so i can make a (nandroid) backup of my data, i have many stuff on it and i'm a bit panicked that i will lose everything. i tried to wipe cache but that freezes at the 'deleting..' stage. also i tried adb when in the recovery, but that does not work.
is there any way to install cwm without data wipe? e.g. in the recovery menu there is an option to update from external sd where i can choose the img file, if i choose your cwm recovery.img would it install the cwm or rather brick the device?
as another possibility i just read something about nvflash. can i save my data using that?
please help,
thanks
mnb
if your bootloader is unlocked then you can use nvflash to backup all you partitions, including internal sd.
berbecverde said:
if your bootloader is unlocked then you can use nvflash to backup all you partitions, including internal sd.
Click to expand...
Click to collapse
thanks,
i tried nvflash but it gives this error:
Nvflash started
rcm version 0X4
Command send failed (usb write failed)
so i assume my bootloader is locked? is there still a chance with nvflash. or any other trick? (e.g. updating to the cwm recovery.img i asked about) i use win7 x64 btw, can that cause an issue with nvflash?
Yes it means it is locked. So you can not use nvflash.
I do not know if you can use ADB. You can try to see if you can install CWM.
berbecverde said:
Yes it means it is locked. So you can not use nvflash.
I do not know if you can use ADB. You can try to see if you can install CWM.
Click to expand...
Click to collapse
no, i cannot get to a state when adb works.
i was referring to the recovery menu item 'apply update from external storage', as it asks for an img file. but maybe if my img file is not a system update but only a cwm img, then i brick my device. so i need some exact advice about this.
is there no workaround when nvflash sais that cannot write usb? in the nvflash useful topic they write something about if the usb is set to writeable but i don't know where to check/set this in win7.
also when in the apx mode i did not try adb, could adb work? (i will try this, but seems improbable)
thanks so far
if the bootloader is locked then it is locked and you can not use nvflash.
I am almost 100% sure that the update in the revoery is meant for system updates and not for recovery updates.
Did you try to do a factory reset?Not sure it will help but worth a try. And i think that it does not wipe the data on the internal sd.
about the usb write failed i can not offer any advice.I think that means that the booloader is locked.
berbecverde said:
if the bootloader is locked then it is locked and you can not use nvflash.
I am almost 100% sure that the update in the revoery is meant for system updates and not for recovery updates.
Did you try to do a factory reset?Not sure it will help but worth a try. And i think that it does not wipe the data on the internal sd.
about the usb write failed i can not offer any advice.I think that means that the booloader is locked.
Click to expand...
Click to collapse
thanks. i thought factory reset will wipe all data (except if i already have cwm). in any case i will have to try this at the end, and i am also pretty sure that factory reset will help - either losing all data or at least saving the data on the internal sd.
in any case i wait for a few more days in case somebody has some magic trick.
http://forums.androidcentral.com/lenovo-android-tablets/239622-lenovo-thinkpad-tablet-wont-boot.html
berbecverde said:
http://forums.androidcentral.com/lenovo-android-tablets/239622-lenovo-thinkpad-tablet-wont-boot.html
Click to expand...
Click to collapse
before doing the factory reset i searched for more info about nvflash.
given that we may have an 'sbk' code, is there some way to get data with nvflash?:
http://rootzwiki.com/topic/7593-bootloader/
and the perhaps good sbk code for tpt:
0x0d0a6f49 0x6c577634 0x4d634e55 0x47336d55
see also
http://forum.xda-developers.com/showthread.php?t=1745450&page=5
i think that the sbk code is for the ideapad not for the thinkpad, but you can give it a try.
berbecverde said:
i think that the sbk code is for the ideapad not for the thinkpad, but you can give it a try.
Click to expand...
Click to collapse
i don't know, maybe. still, for using nvflash with sbk there are some additional files and info needed according to that page which i don't know where to get. or how can i try it?
"For devices that use the Tegra's Secure Boot Key (SBK) feature, it is necessary to provide this key as an nvflash argument."
So in theory the commands are the same but you have to specify the sbk.
berbecverde said:
"For devices that use the Tegra's Secure Boot Key (SBK) feature, it is necessary to provide this key as an nvflash argument."
So in theory the commands are the same but you have to specify the sbk.
Click to expand...
Click to collapse
i added --sbk and then the code but then it said that incorrect parameter or something like that, so it seemed that --sbk is not a recognized parameter. did i use a bad version of nvflash maybe?
it is posible, you shoud search for a thread were they use the --sbk argument and try that version of nvflash
Would be news for me that we have the SBK from TPT
As I said I think the Sbk is for the idea pad
Sent from my HTC EVO 3D X515m using xda premium
berbecverde said:
As I said I think the Sbk is for the idea pad
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
i can confirm that it does not work, i tried this sbk with another nvflash, now the --sbk part was ok seemingly but still 0x4 error. so probably the sbk is indeed for the idea pad. it is so stupid that i loose all data just because lenovo does not give out sbk even after dropping support evidently.
factory reset is what comes, no other options.
thanks for all you people for the advices.
AW: [Q] urgent! stuck in bootloop, how to save data? (cwm? nvflash?)
Hi,
I'm from germany and I own a tablet which is the same hardware as K1, but selled under differnt name.
The nvflash for K1 doesn't work for me, because of different sbk? Don't know.
But I can flash particular partitions.
Maybe this will work for you too.
Please check first if you can read the partitiontable.
More can be found here:
w-w-w.avi-plus.com/repair-tips-forum/miscellaneous-software/android-english/nvflash-with-the-medion-lt-p9516-tablet.html
I'm not allowed to post links, please change "w-w-w" from the above link to "www".
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
Ameisentaetowierer said:
Hi,
I'm from germany and I own a tablet which is the same hardware as K1, but selled under differnt name.
The nvflash for K1 doesn't work for me, because of different sbk? Don't know.
But I can flash particular partitions.
Maybe this will work for you too.
Please check first if you can read the partitiontable.
More can be found here:
w-w-w.avi-plus.com/repair-tips-forum/miscellaneous-software/android-english/nvflash-with-the-medion-lt-p9516-tablet.html
I'm not allowed to post links, please change "w-w-w" from the above link to "www".
Micky
Sent from my MD_LIFETAB_P9516 using xda app-developers app
Click to expand...
Click to collapse
thanks, sounds interesting, yet it is too late, i already made a factory reset, so probably i won't risk and spend time on playing around with it. yet if somebody does, i would be interested whether it worked.
berbecverde said:
i think that the sbk code is for the ideapad not for the thinkpad, but you can give it a try.
Click to expand...
Click to collapse
Hi mnb123123.
I'm experiencing the same problem with a Thinkpad Tablet. The "recovery" menu is broken (/missing cache). I can not do a factory reset. And nvflash is disconnecting me on Windows when I execute the nvflash command.
Here it is my suffering thread.

[Q] My A500 Bricked itself...literally...

Hi guys,
I'm not new to the xda forum, used it for ages for bits of info and things and as a result successfully rooted an Orange Barcelona and an Alcatel One, but the problem I have has made me sign up to ask
My A500 was happily playing some music in my bedroom while I was in the bath, when I came out it had switched itself off. Odd I thought, so I tried to turn it on and it got stuck with the flashing android logo. Again odd, so I attempted a reset, same thing, tried a factory rest and got a bootloader error, poo I thought, must have done some wierd update and broke its bootloader.
So starts an ENTIRE day of searching the xda forum looking for a way to unbrick the thing.
So first thing, do I have APX mode - yes.
Do I have an SBK and UUID - no, thats a problem.
So, i've been through ALL these threads, meticulously...
http://forum.xda-developers.com/showthread.php?t=1829731
http://forum.xda-developers.com/showpost.php?p=23783875&postcount=9
http://forum.xda-developers.com/showthread.php?p=32464439
http://forum.xda-developers.com/showthread.php?t=1585907
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
http://forum.xda-developers.com/showthread.php?t=1998650
http://forum.xda-developers.com/showthread.php?t=1762991&page=2
Blackthunders flash tool causes the tab to disconnect and doesn't flash.
V8-UNL-ICS-HC-bootloader-MULTI-cwm generates an error (usb write fail) and causes the tab to disconnect.
I've determined that SBCALC is not generating the correct SBK from the UUID generated by eppeP's apx code. I compiled it several times on a 32bit Ubuntu 13.04 system and again on an 64bit Ubuntu 13.04 system altering this line of code to reflect the relevent OS
printf("uid: %#016lx\n", *(uint64_t*)data);
In one of the threads i found eppeP had offered three versions. The 32bit lines generated UUID's that were too long, the 64bit line generated the correct length but caused the flash tools to fail. I've tried omitting the preceding 0x SBKCalc says check CPUID or just leaving off the 0, that gives me an SBK but still causes the tools to fail, so again, I think it isn;t generating the correct SBK or the apx tool by eppeP isn't retrieving the correct CPUID.
Throughout the whole day I managed to get the tab to factory reset ONCE, got it to boot, got as far as entering my WIFI PSK then it crashed and went back to 'i'm not going to boot so nah nah' mode.
So status is, tab powers and hangs with the Acer logo, and still has APX mode available.
What, if anything, can any of you wonderful people offer as a next step short of calling Acer Monday and paying silly amounts of money for them to unbrick it. (Amusing anecdote, this is my second A500, it was a replacement for a unit I sent in for repair which came back bricked BY ACER.....)
I'm tearing my hair out now, so help greatly appreciated.
Wee update,
Successfully got a working CPUID and SBK by building eppeP's Visual Studio project, had to update it to VC++2012 libraries as I have Visual Studio 2012 Ultimate through my university.
Trying to flash now, so far I've got a wee message saying nvflash started and nothing else, been sat for a good 2 minutes, is it supposed to go faster?
Kess_Tacy said:
Wee update,
Successfully got a working CPUID and SBK by building eppeP's Visual Studio project, had to update it to VC++2012 libraries as I have Visual Studio 2012 Ultimate through my university.
Trying to flash now, so far I've got a wee message saying nvflash started and nothing else, been sat for a good 2 minutes, is it supposed to go faster?
Click to expand...
Click to collapse
Do u have an apx device listed in device manager or safely remove Hardware icon???
I'd say you'll need to d/ babsector.rar to reset yr partitions. Usually its the only thing that works when yr tab has spontaneously bricked itself. You can get the file and instructions from post #2 of the root guide n my sig...probably the only thread u never posted above
good luck
dibb
Sent from my GT-I9300 using Tapatalk 4
All good with device manager, device is seen ok.
RIght, with BabSector, I get failure to read/write mass storage (code: 9) nverror: 0x8 (0x19000008).
I believe this indicates a physical problem with the internal sdcard requiring a motherboard replacement.
Well, that sucks but I've had this two years so I guess it's had a fairly decent run
Kess_Tacy said:
All good with device manager, device is seen ok.
RIght, with BabSector, I get failure to read/write mass storage (code: 9) nverror: 0x8 (0x19000008).
I believe this indicates a physical problem with the internal sdcard requiring a motherboard replacement.
Well, that sucks but I've had this two years so I guess it's had a fairly decent run
Click to expand...
Click to collapse
I got around this very same problem with Timmy Deans solution. Because of the bad blocks of memory, this was the only way I was able to solve. I don't remember which bat file I used. There were two, depending on whether you were doing single or dual partition. But the limitation was that BCT partition that was being format was larger than available. Once I used his script it worked and my brick A500 is still working well today.
EDIT: @Kess_Tacy
could try contacting acer...someone else just recently had some joy with them. They paid shipping both ways and repaired for free!! Worth a shot

[dev][apx][nvflash][tegra-note-7]

While attempting to flash a modified OTA flashable zip I managed to disable the touchscreen by NOT flashing thee important binary blob leaving me in a permanent apx mode and booting into android OS without a functioning touchscreen, Since the update is to 4.3 the device requests permission for adb so no adb reboot recovery... Also cannt access fastboot just apx mode
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Shaky156 said:
While attempting to flash a modified OTA flashable zip I managed to disable the touchscreen by NOT flashing thee important binary blob leaving me in a permanent apx mode and booting into android OS without a functioning touchscreen, Since the update is to 4.3 the device requests permission for adb so no adb reboot recovery... Also cannt access fastboot just apx mode
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Click to expand...
Click to collapse
Good and bad news, but an horizon... Thumbs up Shaky. Can't wait as similar problem to you.
Note
For those who are having problems with ADB/Fastboot commands not working correct on NT7, update them to r16.01
Linux Kernel for SHIELD (and Tegra Note 7) https://github.com/linux-shield/kernel
Shaky156 said:
Procedure to fix coming soon, testing fix at the moment have successfully installed apx drivers
Update: wheelie is currently incapable of reading Tegra notes blob.bin file, unrecognized MCRVER gives it a hang at the moment so cannot take it any further just yet...
Click to expand...
Click to collapse
What happens if one "nvflash --create", would that take one to the recover straight after boot or is the recovery partition also wiped?
e8hffff said:
What happens if one "nvflash --create", would that take one to the recover straight after boot or is the recovery partition also wiped?
Click to expand...
Click to collapse
Nvflash currently doesnt support tegra 4 or atleast looks like that to me as it hangs on rcmver, doesnt pass that, will test... Also that doesnt take you to recovery it formats everything
Shaky156 said:
Nvflash currently doesnt support tegra 4 or atleast looks like that to me as it hangs on rcmver, doesnt pass that, will test... Also that doesnt take you to recovery it formats everything
Click to expand...
Click to collapse
You mahybe correct. The best I could get out of it was reporting my chip UID. Hasn't the Shield users been using nvflash?
e8hffff said:
You mahybe correct. The best I could get out of it was reporting my chip UID. Hasn't the Shield users been using nvflash?
Click to expand...
Click to collapse
Afaik shield users havent been using nvflash
Progress has been made on this...
EDIT: same issue though reading uid fails
EDIT2: Although i have the correct files apart from nvflash, I Talked to someone from nvidia, they have but wont release the nvflash cmd tool for tegra note 7, it wont happen, thread can close
Thread closed at the request of the OP.
MD

a500 hard bricked help

hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
ssvNormandy said:
hi all and thanks for your help in advance...
i have been assigned an a500 which is bricked and only shows the acer logo and nothing goes on from there
i have tried multiple roms along with custom roms as an update.zip into an SD card but it stops at the same position which is about 30% everytime on every rom
ive tried fastboot, says the BL is locked and when i tell it to unlock it it just says OKAY and stays locked
now blackthund3r with his apx flashing tool presented some hope as it detected the apx mode but after the flashing starts it wont go into bootloader mode the screen is just black
i have attached a screenshot of my pc trying to identify the tablet with apx not installed for no driver is found
i have installed every driver i can put my hands on starting with the latest from Acer drivers and none of them seems to give me the apx driver.
i think the only problem i have is the apx driver, can anyone point me in the right direction? ive got my SBK from afterota only one time and it never worked after that time. can anyone help with the drivers?
#edit:
i forgot to mention that even though it says apx is not installed, when i connect it in apx mode i have a little usb icon which says "eject APX" call me crazy but that just says apx IS installed right?
Click to expand...
Click to collapse
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
9918
Moscow Desire said:
Generally, the APX (boot recovery download) driver should be installed with just the normal Acer drivers from the web site. On a Win8 pc, it can be a real pain, so if you have a Win7 pc, I would advise it. I suppose you are looking in Windows "Device Manager"?
Not sure about the "eject APX" message. Sounds strange to me, but maybe it says that on an XP PC, been to long to remember.
Stock Acer bootloader has no "Fastboot" capability. This was added after ICS with a patched bootloader.
Either way, you will need your CPUID number to use any of the NVFlash tools. There are stickies on how to get this, but more than likely you will need a Linux set-up, not sure if there's a windows method.
If the tab had been rooted, and a custom recovery added, there's a possibility there was a backup done, and it would be in the Clockwork Mod folder on externalSD card.
Click to expand...
Click to collapse
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
ssvNormandy said:
I am running win7 x64 and the apx drivers seem to be installed as blackthund3r recognizes it, its just that in blackthund3r apx tool it never seems to want to get into the bootloader mode i have no idea why.
also regarding my CPUID when i used afterota it showed me :
Tablet Serial : 485FEFA483118011
Tablet Cpuid : EMULATOR-5554
Tablet Sbk : 0xF5030000 0x00000000 0xF0D1E302 0xF0D1E302
Android Build : GT-N7000-user
Bootloader : 0.03.01-HC
now isnt the CPUID a 15-16 digit hex number?
and if my CPUID is wrong in this case above it should mean my SBK is wrong aswell right?
the build number is of a galaxy Note device which is also strange.
also, the device came with no SD card and it has not been rooted or a custom recovery installed on it, the owner says "it just died"
I had the Linux idea in mind as a last resort i suppose its time.
thank you for your help
Click to expand...
Click to collapse
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Moscow Desire said:
Oh man, Somebody must have tried installing a Galaxy Note Rom? Got me a little confused on just exactly what you have there mate.
The CPUID as you stated, should be an alpha numeric sequence such as for example (mine)038061c7409fa617.
Why it's telling you it's Emulator-5554 is quite strange. Tell me, how exactly did you get this CPUID? As if the tablet won't boot past the bootloader (Acer screen), then the usual discovery tools we have, can't get it, and this I can promise. I'm guessing it's just spitting out some programming error.
And, I can also say your SBK number is suspect also. Looks weird. Here is mine (no, won't work on yours) 0x79531F00 0xBB680C01 0xFB22E803 0x8ADE2003
I would suggest the following;
There's a user here, dibb_nz, and he has some links on unbricking. Currently he is abroad, so won't answer PM. Also, there is a thread "Why CPUID is Important (might be the same things). In there, are some steps on how to get the number from a dead tablet. No, I've never personally had to do this, but other folks have. I know there's steps from Linux, but believe there may also be windows steps as well.
Another good link from Linux (you can run I dual boot, as I do) http://forum.xda-developers.com/showthread.php?t=1751978 This should be easy to follow, and probably best chance at getting it.
Another good thread from Dibb_nz http://forum.xda-developers.com/showthread.php?t=2049778 Has several unbrick procedures.
I have several factory Roms here on my server. I try getting one whenever I come across them. Acer in all of their infinate wisdom, have shut down their OTA servers for quite some time, and also, they add and delete factory Roms from their official support site all the time.
If I can help you, I will. Some things may be out of my control, but will help as much as possible. We have some pretty good folks here in the 500 forums, but the tablet is getting a bit old, and most have moved on to somehing newer.
MD
Click to expand...
Click to collapse
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
ssvNormandy said:
I got my CPUID from afterota "no idea how but it just worked for one time, and later yesterday worked again".
when i try "adb devices" it just shows nothing, while yesterday also i tried the same command and it returned with EMULATOR-5554 as a device connected and i could get in the shell but could do nothing from there...
i have seen those posts before they have been helpful but as far as using "a500 manager tool" to recover my CPUID, the tool hasent worked.
anyways i suspect the only way of getting my CPUID is through a linux distribution,and from there i can stumble around with nvflash from there or go back to windows. As I dont have any linux expertise it would be a good experience.
Click to expand...
Click to collapse
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Moscow Desire said:
Use Ubuntu for the linux distro. It's by far the most common. Basically you can install it 2 ways.
1) As a dual boot (might have to disable a BIOS setting if your PC is pretty new. Usually only if it was a Win8 new system) Benefit is that the Linux OS will get 100% system resources. Downside is that it'll partition your HDD.
2) Run it under cygwin. Basically an emulator which runs within windows, and you create a virtual drive for the Linux install. The benefit is that you can uninstall it rather easily when finished. Downside is it shares Windows resources.
If you're only after the UID, then probably the cygwin method is better for you.
MD
Click to expand...
Click to collapse
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
ssvNormandy said:
i've never heard of cygwin, i was thinking virtual machine but i was slacking due to the work it needs doing and my impatience... i must ask if afterota is showing EMULATOR-5554 and i managed to get it in adb mode and it still showed EMULATOR-5554 do you think its even recoverable in ubuntu?
Click to expand...
Click to collapse
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Moscow Desire said:
Well, being in the 500 forums, and owning a 501, I can say these tablets are pretty much bulletproof. I've never known one that can't be unbricked. Basically, if it has some life, it can be brought back. Mine blew away the bootloader, hard bricked. Took out the mainboard, slapped it in the oven, reseated some nand chips, and it updated the blob file when I booted it. :good: imagine that!
It's still a little flakey running EUUS files, but it's on 3.2.1 and rooted, so I will leave it on that rather than press the issue any further. Besides, it's only used for You Tube and Browser anyhow.
I would say the Linux method will probably reveal the true CPUID. Afterota seems like it's generating some development code. Like I said, none of those tools will work properly unless the tablet OS is running, so who knows what strange things will happen.
I've never used VM, but it should also boot ubuntu.
This chap just got his CPUID today using a Linux distro.
http://forum.xda-developers.com/iconia-a500/help/a500-brick-firmware-install-t2865167
Click to expand...
Click to collapse
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
ssvNormandy said:
the oven? im confused what reflowing the solder has to do with anything lol and i hope im not going to that stage haha
im downloading ubuntu now as we speak, im hoping it will work but im confused about the libraries that i need to download, GCC and the other ones, are they something special and special installation required? or sniffing around google would do the trick?
Click to expand...
Click to collapse
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Moscow Desire said:
Well, normally after you get an ubuntu install, you can download extra packages. Terminal for one. I'm sure the Ubuntu help center tells you how to get certain packages (lib's and such). Basically you do it via a terminal window. Like I said, I've never used that particular procedure myself, but seems some others got it figured out.
Ha Ha... the oven. Yes, I was skeptical to say the least, but thinking back on rice to dry out a phone, putting a dead HDD in the freezer, well, it seemed plausible. And for me, the oven trick worked. Pressed all the nands back into place, and was able to clear the "Blob update failed" error (was stuck with no working bootloader, hence a hard brick). I attribute it to my 2.5yrs old girl dropping the tab once too often (although was in a good cover).
Click to expand...
Click to collapse
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
ssvNormandy said:
well i have good news and bad news...
i got Ubuntu and i was succeful in retrieving my CPUID and after that my SBK, blackthund3r a500 tool worked and it got into " entering acer download mode" as in it booted in bootloader mode which is very good, but now when i flash something it is stuck at "stage two-uploading image" and the nvflash command screen is stuck at "resume mode".... well great, now what? lol
Click to expand...
Click to collapse
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Moscow Desire said:
Eh, ok, you got the CPUID. Hang on and I'll give you a link for Timmy Deans 3.2.1 rollback.... Sounds like you got a corrupt partition.
OK, download and unzip the contents.
http://www.mediafire.com/download/fo4wqjeald4s3rj/tdv4_rollback_rom.7z
Now, in the contents, you will see the file pbj20upgrage.exe
Run it as "administrator" (right mouse click it and select run as administrator)
Now, don't plug in the tab. After it does a couple things, (installs drivers, starts looking for current build it will eventually prompt you to start your tab in APX mode. Do it. Then connect, enter your CPUID when asked, and it will NVFlash a complete pre-rooted 3.2.1 with CWM Recovery.
Click to expand...
Click to collapse
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
ssvNormandy said:
well well well, it worked and its perfect now. thank you very much for your help MD pbj20upgrade was the answer, now off to install ICS
thank you again
Click to expand...
Click to collapse
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Moscow Desire said:
Great!
Now, just remember, when you install one of the full ICS Update files (I have a thread stickied in one of these forums), it will change the bootloader, and also do away with the CWM custom recovery. A custom ICS ROM will not run on an HC 3.2.1 bootloader. This is why we had the Blackthunder tool and patched V8 bootloader. Just so you are aware.
Good luck!
MD
Click to expand...
Click to collapse
blackthunder's tool just WILL NOT RUN on the tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
ssvNormandy said:
blackthunder's tool just WILL NOT RUN on my tab its always stuck on nvflash resume mode, and uploading image, even after i got the tab back to life i have no idea why, and everytime i try to flash the v8 or even v9 BL it just freezes and i get the acer splash screen again, and then i have to rollback again.
is there any detailed tut on installing ics with the correct steps ? it would be much appreciated, HC wont run any recent app and its ticking me
Click to expand...
Click to collapse
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Moscow Desire said:
Welcome to the world of corrupted nand memory.
You can try running "babsector" and see if it will NVFLASH repaired partitions.
http://forum.xda-developers.com/showthread.php?t=2049778 and go to the second post.
Not saying it will fix it, but it might.
Have you tried running an ICS Update file?
Click to expand...
Click to collapse
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
ssvNormandy said:
i have basically tried every ROM available and got nothing in return, running babsector gave me an error about formatting partition failed, although when i booted i had a green screen with v8 bootloader on it but it wont boot not will it install any rom and it says, kernel failed or something i dont remember. I have decided to abandon the project and just give it back to the owner with HC 3.2.1 and get it over with
edit: i added a picture of the error
Click to expand...
Click to collapse
Yep, same issue with me. I'm stuck on 3.2 HC
Well, it's a secondary tablet anyhow.
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
ssvNormandy said:
Yep well i figured it was unrecoverable and not worth the effort and time put into it, thanks for the rollback method i couldnt have done it without you MD atleast its working now
Click to expand...
Click to collapse
Yeah, and a little bit of knowledge :laugh::laugh::laugh: (maybe too much)
Am glad I could help out!! :good:

Resources