Database Users

Any chance to grabe cpuid after brick?

Hi guys,
after three days of reading and reading and many hands on - thank u all for all the usefull posts here - i need a definitely answer:
- is it possible to grab the acer a500 cpuid under APX Mode or not?
Scenary:
- tablet prompts every day for an update. My friend at last accepted it and then the reboot came and then some problems like restarting, crashes, etc. (I suppose a simple hard reset would fix it and he'd have a clean and workfull update. But he took to a assistence shop near his home and as i can figure it out they tried to flash it instead cos stuck in android after acer splash. And if tried to go into recovery mode only a layed down droid with that red exclamation.
- in my turn first tried to grab cpuid as i read here - thank u all - but all i got 0123456789ABCDEF. Then tried to flash with an update.zip grabbed from some rom version i cant remember after such many readings... No longer, sorry - and after updating completely the TABLET CONFIGURING screen comes out then reboots and BOOT VERIFIED FAILED. I tried also others update.zip but this one is the only one wich can "works". All the others one i tried stop around 33% and the droid lays down again.
That´s why i need an answer to my question cos i think it´s the only way to have a succesfull flashing via APX mode. Am right?
After so much brain stormings i have seen around here about this issue will someone still try to gimme a help?
Thank u all in advance.
Rgds,

If the device is booting into APX mode you should just need to do a read of 8 bytes, this should give you the UID.
I posted some C code for doing this with libusb before.

And this should be posted in Q&A.

My nexus tablet 32gb is permanently bricked

Ok I bought this tablet on 4/7/2014 then yesterday which was 4/8/2014 it bricked on me and it wont power on or charge i tried taking the battery out then replacing it that didnt work next i tried the volume combinations that didnt work either i ran fast boot via pc didnt even picked up the tablet my guess is that either the file structure or NAND went bad and i need to fix that so i can use it again if you know a way to get this tablet working then please tell me also i tried many android toolkits none worked im guessing i need to fix the NAND but dont know how if you can help i would really appreciate it oh btw i was running stock 4.4.2 and had an unlocked bootloader at the time its like my tablet is completely empty.

If you only had it one day is RMA an option? Otherwise your looking at a new motherboard. Does anything happen when you plug it into a PC any noise or connection? Usually corrupted nand will turn on but will bootloop and any attempt to flash will fail. You may be stuck in apx mode with a corrupted bootloader but either way it sounds like your up a creek.
Sent from my C5303 using xda app-developers app

[Q] Nexus 7 (2012) Broken bootloader, apx mode

A few weeks ago my girlfriend rebooted my Neuxs 7 but it somehow got in a bootloop. I tried to fix this but i managed to shred the bootloader i guess because now it won't turn on at all.
I've tried to boot it into fastboot, but that won't work, so i'm pretty sure that the bootloader is broken.
When i plug it in to my computer and hold in the powerbutton it shows up as a apx device, which i guess is a good thing in this situation (meaning i havn't completely broken the device).
I'm not very skilled with these kind of situations and really need help from you guys.
I've read about apx drivers and if i understand the situation correctly i could somehow install a new bootloader this way?
Could anyone help me step by step restoring my precious Nexus?
I could send it to service, but i don't think i have any warrenty left on it since i bought it almost 2 years ago. I also suspect it would cost me a lot of money if i send it to service.
Please give me happy answers

Pretty sure you needed to make a backup of your device first to flash back with apx mode as this is device specific

Same problem here.
From what I read the only way to restore your N7 in APX mode is if you had a backup(again from apx mode).But now the device doesn't have(or its broken somehow) a bootloader anymore so we can't do it.
If you still have warranty return it,if you don't buy a new motherboard(40-60$ on ebay depending on the storage) and change it your self.There is plenty of tutorials on the web how to do it.
Good luck.

I believe I have the same issue. Nothing on screen, does not come up on computer but shows as APX. Does back up have to be from our device or can a backup be made by someone and we restore from that copy?

To the best of my understanding it is device specific so for those who want to be safe make a backup now as you can't use someone elses

demkantor said:
To the best of my understanding it is device specific so for those who want to be safe make a backup now as you can't use someone elses
Click to expand...
Click to collapse
Okay, well that sucks! Guess i'll have to order a new motherboard then.

[Q] [VS980 32GB brick] - No download mode, some form of TWRP

Hello,
I've done a lot of looking through these forums, so I can say that the following doesn't work:
* The solution where and adb command from the TWRP terminal (starting with if=dev/zero) does not work. It does not have the files/directories those commands look for.
* I will be currently trying the solution that boots into Linux and uses gdisk to manage partitions. I have hope in this one, but I am making a head start of looking for advice in case it doesn't.
Any .tot or .kdz methods are useless as my phone /cannot/ get into download mode. If there is a way of telling it to over a cable, like you can with fastboot, I would love to know.
How the problem happened:
Ironically when I finally settled with a rom and wasn't going to do any flashing in the near future, I decided to make a nandroid backup.
I watched its progress now and then and it was working regularly.
Once it finished, I slid to reboot, and walked away. When I came back, the phone was on the LG logo with pulsating blue/green LED.
I went to restore from the backup I had just made, and that's what really messed things up. Ever after, all directories are shown as empty, and if you tell TWRP to do any function like flashing or recovering, it starts, but then crashes and reboots.
To begin with, occasionally it /would/ show my directories populated as they had been... but the crash and reboot thing. Now it never shows anything in the directories.
Since then, I /did/ manage to get into Fastboot ONE TIME, but things didn't work out on the computer end for Flashtools because I was on my campus network.
I have held out for a similarly low odd since, but I have spent hours, and almost all the battery, holding the power up button different times and ways and plugging the USB cable in at different times and ways.
I had Xdabbeb's stock variant installed, XCeed kernel, latest TWRP (thank God for heat control or I would have a screwed screen by now!) and let me know if any other details would be helpful.
I'm about to boot into Linux, I'll see how far I can follow this solution:
http://forum.xda-developers.com/showthread.php?t=2582142
Has anyone been in this spot? What worked?
EDIT: Ubuntu solution no good - my device does not show up as qhsusb_bulk or in sda or sdb tables.
EDIT: I MIRACULOUSLY got into fastboot! Instead of selecting power off or just holding power etc. in TWRP I said to reboot as system - holding the VolUp, even with the cable already plugged in, got me into FastBoot!
Trying the .tot method.
EDIT: I could weep. .tot failed because of
[ 8:50: 3] LAF_READ_GPT_FAILED
[ 8:50: 3] LAF_READ_GPT_FAILED.
[ 8:50: 3] LAF retrieveGPT() failed.
So I thought I should reboot it into download mode (which it was already in...) and I'm back to it being impossible to attain. What worked from TWRP the other time was just lucky.

Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk

dgranillo said:
Here's what I did when I royally screwed up my ls980:
I grabbed SRKTool and nuked my download mode. Then when attempting to enter download mode I was instead kicked into fastboot. From there I flashed stock partition images (in my case aboot, boot, laf, and recovery), rebooted into download mode (which should be restored when the laf partition is flashed), and then was able to flash a stock tot with the LG software. If your tot flash fails because of a device name mismatch I can help you with the hex editing of the tot file as well.
All data lost, but phone was unbricked.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I greatly appreciate your reply.
I managed to get it into download mode one more time (the rate must have been 1 in 80 or fewer, but I had no choice!), and flashed a .tot file (an old one... Jellybean!)
Ever since then, I have been able get into download mode as easily as it should be. One or two things to note though.
Any further flashing of .tot files ends at 6% with the exact same errors as pre-"fix".
Even the successful flash didn't boot successfully at the end, but had a red-triangle android figure
Sometimes it boots successfully into the stock rom, but others it goes into LG logo and blue/green LED, as before.
After a successful boot, it will die/go back into a boot loop some time soon after.
This leads me to think that a significant part of this all happening (I mean, I only did a nandroid backup to start this all off...) is a hardware issue, maybe to do with the flash storage.
By huge luck, I am withing the last 2-3 days of the 30 day period after buying it refurbished from a seller who gives full refunds including postage. Convinced something's not quite right with the hardware, I will be sending it back. I simply can't waste any more time I could be spending with my wife, or out of a returnable period, seeing if there is a fix to it.
Like I said, it means a lot that you would respond to help. Maybe parts of this are useful to someone. Thank you!
Any advice on removing the "rooted" red writing from the download mode screen? Especially as I'm pretty sure it isn't any more.

That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk

dgranillo said:
That is beyond my knowledge. I'm sorry. Haven't seen or read about anything like that before.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
dgranillo, I am sincerely thankful for the time and consideration that you have given my problem.
I will mark this as solved because I did get past the initial problem, and I am thinking the further problems might be hardware.
Thank you again.
EDIT: I can't see how to edit the topic title, perhaps a mod has to mark it as solved.

N7 2012 [WiFi] Grouper - Bricked or the Flash Memory just failed?

Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..

phnxnvrdies said:
Ok, so to start off I'm very familiar with Nexus Root Toolkit an its many graceful features & its ablity to bring the N7 from the brink of destruction (Soft -Brick) "AS LONG AS YOUR PC CAN DETECT THE DEVICE".
Here's the issue.. I was in TWRP (Multi-ROM) just renaming 1 of the Secondary ROMs to more friendly names, I hadn't done any flashing of any zips or roms for a few boots, I just booted into Recovery to do some renaming of Secondary ROMs that I had installed a few nights before but I had been in an out of several different one's just making sure they were all working so anyway.. after I was done renaming, I reboot the system & it just went F'ing blank.. now nothing.. there's no back light, no bootlogo, nothing happens at all when I plug in the charging or hold the power button with or w/out the vol-+ keys, I've checked the battery connection, it was snug but I removed it over night.. still nothing, I'm just clueless.. Before we jump on the NRT do a factory wipe & restore, when I plug it into Windows it instantly pops up with the "Device has Malfunctioned" not the "installing adb drivers" or anything like it has so many times before.. either Im over thinking this an the answer is so simple Im blinded by rage over how much this p1sses me off that it was working fine one moment an then just reboots to blank nothingness.. even if I take the battery out an try plugging it directing into the pc via the OEM usb cable it gives the same error with or w/o the battery in .. the toolkit cant even see it cause windows cant establish what the hell it is.. And yes I've tried installing every android driver possible.. the N7 was primarily for my wife to read e-books on.. so i rarely played with it.. an it was new sealed in the box just bought last year around this time so i can't believe the Flash Memory is shot already, if anyone could throw me their 2 cents it would be greatly appreciated , this is so frustrating but I think its BRICKED.. or at least some tiny flash chip is toast..
its the - N7 2012 Grouper WIFI Only model -
p.s. I apologize for the slight harsh tone, I'm just upset with this issue.. I got this particular tablet with the knowledge an understanding that it was the (almost) un-brickable tablet, yet I managed to do it.. If by some chance I get it to fire up, I will definitely let ya know.. But I have read alot of posts an my guess is somehow I managed to mess up the nvflash an now the memory chip or something is corrupt beyond a NRT Factory reset.. but again it was at almost full battery when i rebooted from within the TWRP Menus & I wasn't flashing anything previous to me being in my Main Rom which was stock rooted 4.4.4 de-bloated, playing a game called Empire 4 Kingdoms for like a 1/2 (just getting my daily's) before i decided to check out my Secondary Roms an rename a few because I wanted to started playing around with them to test how the same game played on different flavors or Android..
Click to expand...
Click to collapse
UPDATE STATUS - If I plug it into the pc without the battery i get a windows driver install box that says "Installing APX..." does this indicate the NVFlash is corrupt or is there a way to get out of apx mode.. im not familiar with that mode .. only ADB & fastboot..
Update 2 - After reading lots, I've come to conclude its hardbricked, must have had an error in memory or whatever.. its stuck in APX mode so im going to replace the whole MB with a working 32GB [model me370t] & start over .. maybe ill not install so many ROMS via multirom.. just a few - THREAD BE CLOSED - I'm done here, good luck to anyone with similar results