Related
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.
Hi, everyone...
I need your guide/help with my Iconia A500.
In January it "bricked" (stuck on Acer Logo), I sent it to Acer Support because I tried to flash it but failed every time (and I stucked in APX mode only), but I haven`t warranty, so they only said me "The motherboard is broken, your tablet never turn on again, the repair will cost you 500 dollars" (aprox.)... I didn't accepted the reparation because the tablet cost me 350 dollars (aprox.)... yeah, Acer logic.
When they returned me the tablet I tried to flash it again with APX Flash tool, after a few tries, I could flash with bundle 3 and installed an HC stock rom... the tablet works fine, until I tried to update to ICS (through the Android Update Menu), then my tablet start to update, the proccess finished, but never boot, it stucked on Acer Logo.
So I reflashed bundle 3 with APX Flash Tool and I did it again, the tablet turned on and worked very well... thinking it only was a random error or something like that, I tried to update to ICS again, but this time the update proccess repeat and repeat (the screen with the progress bar) like 3 times and then stuck again in Acer Logo... so I tried to reflash again... but I can't do anymore...
After a nigth of tries and research, I concluded that I messed up the table partition, when I tried to flash with APX mode it stuck in "Formatting 4 (or 6) partition, please wait" and manually with nvflash it shows the "0x120002" error.
What can I do?
I know it isn't a hardware fail, because the tablet worked fine although in Acer Support said me it never work again...
I really aprecciate any help you can give me... thanks!
(Sorry for the long post and my bad English).
It's a hardware fault!!! Sooner or later it will die 0x120002 error.
Install a new motherboard 50$ on ebay
Or just live with hc...
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
It's a hardware fault!!! Sooner or later it will die 0x120002 error.
Install a new motherboard 50$ on ebay
Or just live with hc...
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
How can I "just live with HC"?
I tried and tried to reinstall it, but I couldn't even flash the bootloader...
What should I do to install HC again?
thats the thing with a h/w fault - with the acer its the memory chip, there is no fix except a new mobo - it may already be fried if you cannot flash anything.
I figured if you managed to go back to HC before you could do so again - seems not! Even if you did manage to get something on there, it will happen again and again until it dies. For the sake of $50 I know what I'd be doing...
pholuta efficiency
dibb_nz said:
thats the thing with a h/w fault - with the acer its the memory chip, there is no fix except a new mobo - it may already be fried if you cannot flash anything.
I figured if you managed to go back to HC before you could do so again - seems not! Even if you did manage to get something on there, it will happen again and again until it dies. For the sake of $50 I know what I'd be doing...
Click to expand...
Click to collapse
Bad luck then, and RIP my A500... :/
Thanks for the answers...
Ok here goes. Sorry for the long post but I want to give as much info as possible so I don't leave any of you in the dark about anything. Been working on / researching this for four days now to no avail.
My A500 which was running ICS 4.0.2 just randomly bricked itself one night, so I downloaded EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here. It worked, but I really don't want to stay on HC 3.0.1 so I decided to go through the updates. It updated great, HC 3.1...3.2...then when the ICS update came along BAM it bricked itself again (stuck on Acer loading screen)
So, I decided I might as well root it, since I've always wanted to. Ran EUUS again to reset to HC 3.0.1 then ran gingerbreak. Installed Acer Recovery Installer and used Thor's recovery 1.7 I believe it was. Booted into recovery and tried to install update.zip from the STOCK Acer_A500_7.014.16_041.206.01_COM_GEN1.zip I downloaded and BAM bricked again...my tablet doesn't like ICS now all of a sudden? Strange...
I then downloaded NVFLASH from here and installed skrilax's V8 bootloader w/recovery. Booted into recovery great, wiped the partitions etc. and tried to install the same ICS update.zip. BRICKED again!!!! Back to the drawing board...run EUUS...3.0.1 again...
So after days of working on this I decided maybe my Tab hates ICS now for some reason unbeknownst to me. Not very rational (lol) but anyway. I saw the JB ROM that's been put up http://forum.xda-developers.com/showthread.php?t=2239476&highlight=rom+ics and figured heck, why not, maybe the ICS ROM I have is corrupt. So I used NVFLASH, Skrilax's V8, and flashed the ROM...bricked again
I think the only thing I haven't tried is
I think I'm going to go crazy now.
Please help, I'm at wit's end.
More info:
I have acquired mmcblk0 (renamed to mmcblk0_start), my CPUID, and my SBK
I enable USB Debugging and Unknown Sources every time.
I have Windows 7, but also have UBUNTU installed on a Virtual Machine if the need arises.
Oh and I've booted into fastboot mode and run Babsector as well which did not help.
Hope I didn't miss anything. My brain is tired from working on this for so many days. I really want my A500 back! Either JB or ICS & rooted if possible!!!
Pareeeee said:
Ok here goes. Sorry for the long post but I want to give as much info as possible so I don't leave any of you in the dark about anything. Been working on / researching this for four days now to no avail.
My A500 which was running ICS 4.0.2 just randomly bricked itself one night, so I downloaded EUUs_SBK_Acer_A500_1.016.05_COM_GEN1 from here. It worked, but I really don't want to stay on HC 3.0.1 so I decided to go through the updates. It updated great, HC 3.1...3.2...then when the ICS update came along BAM it bricked itself again (stuck on Acer loading screen)
So, I decided I might as well root it, since I've always wanted to. Ran EUUS again to reset to HC 3.0.1 then ran gingerbreak. Installed Acer Recovery Installer and used Thor's recovery 1.7 I believe it was. Booted into recovery and tried to install update.zip from the STOCK Acer_A500_7.014.16_041.206.01_COM_GEN1.zip I downloaded and BAM bricked again...my tablet doesn't like ICS now all of a sudden? Strange...
I then downloaded NVFLASH from here and installed skrilax's V8 bootloader w/recovery. Booted into recovery great, wiped the partitions etc. and tried to install the same ICS update.zip. BRICKED again!!!! Back to the drawing board...run EUUS...3.0.1 again...
So after days of working on this I decided maybe my Tab hates ICS now for some reason unbeknownst to me. Not very rational (lol) but anyway. I saw the JB ROM that's been put up http://forum.xda-developers.com/showthread.php?t=2239476&highlight=rom+ics and figured heck, why not, maybe the ICS ROM I have is corrupt. So I used NVFLASH, Skrilax's V8, and flashed the ROM...bricked again
I think the only thing I haven't tried is
I think I'm going to go crazy now.
Please help, I'm at wit's end.
More info:
I have acquired mmcblk0 (renamed to mmcblk0_start), my CPUID, and my SBK
I enable USB Debugging and Unknown Sources every time.
I have Windows 7, but also have UBUNTU installed on a Virtual Machine if the need arises.
Oh and I've booted into fastboot mode and run Babsector as well which did not help.
Hope I didn't miss anything. My brain is tired from working on this for so many days. I really want my A500 back! Either JB or ICS & rooted if possible!!!
Click to expand...
Click to collapse
Wow I thought I was the only one who had this issue. My A501 was working fine on Evil-A V2 (4.1.2) for many months and decided one night to crash and now stuck on V8 boot screen. Ive tried everything however I can get it to boot up on a 3.2 update.zip file.
The only recoveries I can get to work are TWRP 2.5.0.0 (on secboot)
Now I cant get it to flash anything other than 3.2.
It is formatted with ext4 partitions
whenever I try to flash it reboots to ACER download screen but the flashers wont get any further than that. (loads Acer boot recovery driver ok)
Any ideas?
Nice to know I'm not the only one. I hope we get some answers!!
*sigh* My situation has gotten worse. Now TDv4/EUUS won't roll back my device and my tab won't go past the recovery bootscreen (Just says "TEAMWIN" on the screen) That is the ONLY recovery that NVFLASH will flash to my device now, for some reason none of the other recoveries will go back onto it.
My stress level has gone up 800% from working on this. I don't have the money to buy a new tab. I really need to get this one working again.
:crying:
Pareeeee said:
Nice to know I'm not the only one. I hope we get some answers!!
*sigh* My situation has gotten worse. Now TDv4/EUUS won't roll back my device and my tab won't go past the recovery bootscreen (Just says "TEAMWIN" on the screen) That is the ONLY recovery that NVFLASH will flash to my device now, for some reason none of the other recoveries will go back onto it.
My stress level has gone up 800% from working on this. I don't have the money to buy a new tab. I really need to get this one working again.
:crying:
Click to expand...
Click to collapse
have you tried lightspeed v8 bootloader and rom? that's the only thing that worked for me. then I could updatw to twrp and jb.
Sent from here
LPMatt said:
have you tried lightspeed v8 bootloader and rom? that's the only thing that worked for me. then I could updatw to twrp and jb.
Sent from here
Click to expand...
Click to collapse
I think my MB is failing/has failed. Either that or something I flashed to it was badly corrupted.
Now my tab has stuck itself in apx mode, bootloader won't load, recovery won't load, every program I have (nvflash, TDv4, EUUs, Babsector, etc) fails. Babsector gives me the fatal error "command 12 NvError 0x120002" and "setting device: 2 3" which I've read means that the tab is shot. Adb.exe tells me the device is not detected, even though all the drivers are installed correctly.
I'm pretty bummed because I don't have the money to buy another tab at the moment, and I used it ALL the time, took it everywhere with me.
On the up-side, I've done some research and it seems if you disassemble your tab and sell the working parts (things like the screen, metal back panel, internal speakers - obviously NOT the MB though!) individually on eBay you can make a bit of your money back.
Can anyone direct me to some good links/video tutorials for dis-assembly?
whoops... I just started a new thread with a very similar issue... My tab also just involuntarily bricked itself... I've made some progress but it's still in bad shape... I don't know about you guys but I had been running at a steady 50% overclock; do you think that could have led to this?
Sorry Man
No @rwilpstra....my a500 is overclocked to 1504 ghz and it runs just fine......as for you pareeeee....Sorry man.....your device is gone....no apx...no fastboot....no recovery.....it's beyond minor corruption....it's like you somehow managed to corrupt every single part of the memory and every partition that there was on your device....you're better off disassembling it.:crying::crying:
Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
thorindwarf said:
Just an idea: take your SIM off and on. Try firmly align it.
I have had (having from time to time) the same problem with my S2. And that always works. I guess because my SIM is very old but it may be from some dislocation of the card.
Hope it helps.
Click to expand...
Click to collapse
I have tried with a couple of SIM cards, and also without it. No luck, the SIM Cards were pretty old tho, I will try with a new one and see what happens.
Other thing, Shouldn't I see the IMEI and baseband without a SIMCARD in anyways??
Thanks
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
raptir said:
I know you said you've flashed stock 4.2.2, but have you tried doing a full flash to a Nexus factory image?
https://developers.google.com/android/nexus/images#occam
You will need Fastboot installed (I recommend using the SDK to install it if you haven't already http://developer.android.com/sdk/index.html). It reflashes every partition on your phone to stock (more than what you can flash/restore through recovery). It's a bit of a "nuclear option" for fixing any software related issue.
Click to expand...
Click to collapse
Hi, I already tried that, the 4.2.2 that i flashed was from there :/ (with fastboot)
Also I completely took apart the phone today, and the motherboard seems fine (for what the naked eye can see)
The battery seems to drain really fast tho.
pocketrussian said:
I have never tried myself but maybe if you put the phone in diagnostic mode and connect it to lgnpst or qpst using the same drivers you used to unbrick the phone, you might be able to read the nvram and look for signs of memory corruption and perhaps correct the values? This is just an idea. I am not an expert and this might not work at all or make things even worse. Perhaps you can pm gigadroid and ask him his opinion?
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
Thank you, I will do that as soon as I figure out how to do it.
With diagnostic mode you mean that download mode or there is another one?
Also I noticed that every time i use LGNPST a window saying that my device is being installed pops up, could it be a driver issue?
I don't think that this would work in download mode. I just tried with LGNPST in download mode and it's asking for an spc code. I tried 000000 but I didn't work. I tried qpst and it says it can't read phone settings in download mode. Again, I don't know much about this but there must be another mode (diagnostic) for which this might work. I googled but wasn't able to find any # codes that work on the n4. Perhaps from the terminal emulator if your phone is rooted. I wish I could help more but I just got this n4 recently and I am not an expert in any of this stuff.
Sent from my cm_tenderloin using xda app-developers app
Same problem here...
venec said:
Hi so, this is my story.
A couple of days ago my phone fell from my pocket while getting out of my car into the driveway. When i noticed i didn't have it i started calling it, and found it ringing outside. When i grabbed it it had the back panel destroyed but no visible damage to the screen (phew). It was working. Next day, battery is dead, so I connected to a USB cable from my PC, but no cigar, the LED was flashing red and it wouldn't turn on. I seached on the forums an finally got it to turn on, but I didn't have a signal. I went to check service providers and it showed an error. Came to the forums again and found out about all this unknown IME and baseband that people were talking about, and I seem to have the same problem. However, I could not solve it with any of the solutions I could find here.
What I've tried:
http://forum.xda-developers.com/showthread.php?t=2347060
(tried this 3 times and no luck)
Flashing several other radios (48 84 33 even 27)
Installed CWM (touchscreen)
Installed a custom ROM (CM10.1)
Flashed android stock 4.2.2
Other details:
I do have Wifi and bluetooth
The baseband version shows correctly in fastboot mode
The battery problem (flashing red light problem seems to still be there, I am charging now only with wall socket to see if it gets fixed)
I opened up the phone, and there is no visible damage to it from the inside, I also took out the battery and checked the connector for the modem
Attached some Screenshots
Can anybody help me, or guide me in some direction please, I really want my phone back. (I'm using my old Nexus one in the meantime )
Some screenshots attached
Click to expand...
Click to collapse
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
stenosis said:
This is exactly what is going on with my phone, except I did not drop. Was there any resolution???
Click to expand...
Click to collapse
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
venec said:
Nope, no solution for me, tried everything that is here in xda, and nothing works :/
Click to expand...
Click to collapse
I'm with the same issue. Any good news?
elbosio said:
I'm with the same issue. Any good news?
Click to expand...
Click to collapse
Nope, tried everything nothing works so far
I'm thinking about sending it to this guys or wait for kitkat and hope for the best:
http://mobiletechvideos.mybigcommerce.com/lg-phones/
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
I'm having the same issue so the phone is going back to Google for replacement. It has been acting wonky for a few days anyways.
I tried the Google factory flash script, flashed a few different radios, and followed this thread:
No luck.
I was running AOKP 2013-10-15 Nightly. And the problem started with the phone doing a constant boot loop for a few hours without me noticing. It was some kind of issue with the power button getting stuck that appears to have resolved itself but it took the radio with it.
Droid2drummer said:
OK. Was your phone on 4.2 when you got it or did you revert to it. I once reverted to 4.2 but did a unbrick write to 4.3 lost my radio and all. But when I realized what I did I fixed by going back to 4.2 Leaving stock and ota each update which fixed my problem.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yes it was 4.2, so you mean do the LGNPST thing and after flash 4.2 image?
I already did that with the 4.2.2 (JDQ39) image and still no luck
I had the same issue, and I solved it by flashing the factory images... Twice.
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