Related
Hi guys,
I've started joining the android tinkering world and have recently acquired a bricked atrix as a hobby. I have poured over the sticky posted in the Atrix Devs part of the forums (and many other threads) for sometime now. I can't find an answer and I'm now stuck in my tinkering. And there seems to be no complete consensus if there is any way to fix a bricked atrix. My atrix does have the same error message of
SVF:105:1:2
Failed to boot 0x1000
Entering NVFlash Recovery Mode
Battery is too low to flash
My own currents attempts have been to create a factory cable, which allowed me to successfully connect to my computer. The drivers recognize that the phone is connected, but when I run NVFlash and do a test command --sync, I get the error:
USB failed to write
So from what I have gathered, Motorola has not released the SBK for the atrix so I cannot flash through this method correct? Is there anything I can do from here, or possibly a different method? Or is this phone simply hard bricked?
Simply hardbricked... Read around the forum. Its posted in many places. You cannot recover a hard brick.
yep. Sorry dude. It doesn't help that the term "brick" is used for so many different failed-to-boot states, but the Unrecoverable Hard Brick is when NVFlash is your only boot option for exactly the reason you stated -- we don't have the SBK from motorola.
(If you have access to any other options, like fastboot or RSD, that's a "soft brick" and it's possible to recover.)
Alright thanks for the help and clarification guys.
But yeah I did look around the forums quite a bit. Its just the information is never quite clear with all the people posting and whatnot.
If bootloader is unlocked you shouldn't have a problem. Try unlocking bootloader again.
Sent from my MB860 using xda premium
Can I still access the bootloader while my phone is bricked? I can't access RSD to start unlocking the bootloader or any other options when I turn on my phone.
yeah it's borked forever. sorry
Alright that's what I thought. I don't mind so much since my main phone is an HTC Sensation. I just started getting interested in tinkering around with phones and learning more. So I'll probably just resell this on ebay or something and take a slight loss in cash.
Did learn a lot from this venture though
Hi!
(I hope this is the right forum for this question)
In short: I currently have a bricked Transformer Prime TF-201, which only lets me boot into APX mode or shows the ASUS logo.
Long version:
I tried to flash CWM Recovery to the Transformer via fastboot, which didn't work. Flashing went okay, but booting the device in recovery mode was impossible, it just loaded forever. Then I tried to flash the TWRP recovery image, which only worked with one specific image. Because I was curious why the CWM stuff did not work, I flashed it again, and then unfortunately made a huge mistake: I used the last option of the boot menu (something like Wipe all data, etc.) from Android, which basically tries to factory-reset the device, and tried to boot into recovery mode, which of course does not work.
Now, everytime I start the device, it apparently tries to automatically start the recovery mode or does something else (without showing log messages, meh...). Holding the power-button and volume-down does not have any effect anymore, which means I can no longer access fastboot to fix this.
The only thing I can reach at time is the APX mode.
I have a few questions regarding this situation, first of all:
1) Does anyone know a method to get out of this? (I haven't activated nvflash, unfortunately)
2) Is the APX mode usable for anything without the previous steps?
3) In case there's nothing more to do, has someone experience in how Asus reacts if I send the device back?
Regards,
Ximion
You have to have your device specific files to nvflash to work.
You can send it to Asus for RMA - they will replace board. You will have to pay for out about 200$. After RMA there is slight chance you won't be able to unlock again.
Sent from my LT30p using Tapatalk 2
Ximion said:
Hi!
(I hope this is the right forum for this question)
In short: I currently have a bricked Transformer Prime TF-201, which only lets me boot into APX mode or shows the ASUS logo.
Long version:
I tried to flash CWM Recovery to the Transformer via fastboot, which didn't work. Flashing went okay, but booting the device in recovery mode was impossible, it just loaded forever. Then I tried to flash the TWRP recovery image, which only worked with one specific image. Because I was curious why the CWM stuff did not work, I flashed it again, and then unfortunately made a huge mistake: I used the last option of the boot menu (something like Wipe all data, etc.) from Android, which basically tries to factory-reset the device, and tried to boot into recovery mode, which of course does not work.
Now, everytime I start the device, it apparently tries to automatically start the recovery mode or does something else (without showing log messages, meh...). Holding the power-button and volume-down does not have any effect anymore, which means I can no longer access fastboot to fix this.
The only thing I can reach at time is the APX mode.
I have a few questions regarding this situation, first of all:
1) Does anyone know a method to get out of this? (I haven't activated nvflash, unfortunately)
2) Is the APX mode usable for anything without the previous steps?
3) In case there's nothing more to do, has someone experience in how Asus reacts if I send the device back?
Regards,
Ximion
Click to expand...
Click to collapse
i had the same promblem,no way to do nothing without nvflash,i returned back to asus where they changed moderboard or something like that and thank God they did not charged me for anything. good luck :fingers-crossed::fingers-crossed:
Your totally wrong dimwit...!...
qery said:
You have to have your device specific files to nvflash to work.
You can send it to Asus for RMA - they will replace board. You will have to pay for out about 200$. After RMA there is slight chance you won't be able to unlock again.
Sent from my LT30p using Tapatalk 2
Click to expand...
Click to collapse
I just got off the phone with ASUS Directly and My TF300T Is in a boot loop no recovery no adb no fastboot, i told the rep at ASUS i unlocked it he said no problem we can flash an updated JB Android O.S. to Your device get it back to You within 7-14 days at a charge of $87 so stop lying to people MOBO Needs changed my A** Your dimwitted and NO ASUS has not changed policy in the last 6 years either stop spouting crap and get on with helping us that have semi bricked devices dum nutzzz good god almighty, and btw i have the device in transformer Prime APX mode yet its not a prime and regardless of the crud your spreading like a nightmare virus, there is no apx instructions to be found online... so rma it they flash the os in factory and iam good to go after i pay $87 bucks, NOTE TO ALL: Your device is not junk UNLESS when you go to turn it on it does NOT 'then' call it bricked and a new mobo would probably cure that too, ps njoy your multimedia XPerience, and dont listen to ANYONE THAT SAYS CRAP like the ubdertoned fool did new mobo lol haha your missing a cog or bean in that brain fooooooo ewllllll cheeerzZz...!...:victory::good:
StanDP said:
I just got off the phone with ASUS Directly and My TF300T Is in a boot loop no recovery no adb no fastboot, i told the rep at ASUS i unlocked it he said no problem we can flash an updated JB Android O.S. to Your device get it back to You within 7-14 days at a charge of $87 so stop lying to people MOBO Needs changed my A** Your dimwitted and NO ASUS has not changed policy in the last 6 years either stop spouting crap and get on with helping us that have semi bricked devices dum nutzzz good god almighty, and btw i have the device in transformer Prime APX mode yet its not a prime and regardless of the crud your spreading like a nightmare virus, there is no apx instructions to be found online... so rma it they flash the os in factory and iam good to go after i pay $87 bucks, NOTE TO ALL: Your device is not junk UNLESS when you go to turn it on it does NOT 'then' call it bricked and a new mobo would probably cure that too, ps njoy your multimedia XPerience, and dont listen to ANYONE THAT SAYS CRAP like the ubdertoned fool did new mobo lol haha your missing a cog or bean in that brain fooooooo ewllllll cheeerzZz...!...:victory::good:
Click to expand...
Click to collapse
TL;DR I know how to make a fool of myself in my first post and my enter key is broken
Had a working Prime with Jelly Bean OTA installed with root, then reset to factory and unlocked bootloader. Worked fine at first and still had root (checked with voodoo ota) and so I tried to install a ROM on it. Used rom manager, flashed latest CWM, and couldn't enter recovery after flashing the recovery. At this point, I could still get into the OS and use it, so I tried to flash a CM10 ROM from rom manager, because I was so stupid as to not check if recovery was working from boot. Well of course the ROM wouldn't install, but fastboot was still operational at the time, just that any selection I chose didn't really do anything. Device froze whenever I chose RCK for recovery, and wipe data didn't do anything either. Couldn't boot into OS at this point. Tried using Urkel's Fresh Start but didn't detect, but now on the tablet, it won't even go past the splash screen. Top left says "The Device is UnLocked." and Center has the Asus logo. No error messages as seen with this thread:
http://forum.xda-developers.com/showthread.php?t=1514088
I'm guessing the bootloader, recovery, and fastboot missing by now? When I connected to the computer once, it installed APX so I guess I'm stuck in APX mode with a hard brick. Warranty ends on 1/11/13 but since it's unlocked, doubt they'll do much. Heard that someone sent in an unlocked bricked TF201 and it was sent back wiped somewhere, but I'd be lucky to have that happen at this point. Anyone got any ideas?
Also, would this method help? Don't think fastboot works on my tablet anymore though...
http://forum.xda-developers.com/showthread.php?t=1773280
EDIT: Installed the naked APX Driver from here:
http://forum.xda-developers.com/showthread.php?t=1379875
can this actually do anything to fix the tablet considering the tablet itself doesn't seem to have fastboot anymore? didn't use nvflash so I guess I'm screwed unless Asus replace the board?
boyang1724 said:
Used rom manager, flashed latest CWM , and couldn't enter recovery after flashing the recovery.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=34944779
Sorry mate, it looks kinda grim
Sent from my GT-N7000 using xda app-developers app
You have bricked as you haven't got nvflash. you can send it to ASUS for repair it will cost you about 200 $
Sent from my GT-I9300 using Tapatalk 2
qery said:
You have bricked as you haven't got nvflash. you can send it to ASUS for repair it will cost you about 200 $
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
GAH read a lot of mixed events in Diamonback's thread, and it appears some people have been contacted with $200-800 (wtf) bills to repair the mainboard, but others even with unlocked and bricked jb devices have had their tablets fixed for no charge. If I don't get anymore answers by Thursday, I'll have to send it back and hope for the best.
Nothing you can do man. RMA.
alright so customer service replied to my rma S/N that the device is out of warranty (since they can check the unlock from their own tool...) since there's mixed reactions to devices needing a $200+ service for mainboard replacement/labor and free repair from their own software, what would my chances with having the repair be under $100 if I could argue that they don't need to replace the mainboard to unbrick the device? It still needs a camera fix due to the green issues... and labor costs. If it ends up being over $200 I'd probably be better off selling this one for parts and getting a refurbished device or the Nexus 7...
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
C-4Nati said:
Hey all, so I was installing HD revolution which is compatible with the T mobile version. I installed it before and had no problems. Went to install the updated version today and did and at the end it says root may be lost and asked to fix it. I said yes. Now the phone is in a boot loop. It goes to the HTC "quietly brillant" screen and has the this build is for developmental purposes at the bottom and what not and then reboots to the same screen but says entering recovery at the top then the screen turns black and it flashes a glimpse of CWM then restarts the process over and over. I tried to boot into recovery and what not through the toolkit but USB debugging isn't available. Please help I have no idea what to do.
EDIT- I can get into the bootloader but I've never done anything with ADB or fastboot so I'm wondering if that can save me?
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Solved, mod please delete.
C-4Nati said:
Solved, mod please delete.
Click to expand...
Click to collapse
Please post your solution, so others can see it.
C-4Nati said:
Also in the bootloader above "unlocked" It says "tampered", not sure if that means anything.
Click to expand...
Click to collapse
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
stevedebi said:
Please post your solution, so others can see it.
Click to expand...
Click to collapse
I went into fastboot usb mode in the bootloader then connected the phone to the computer then dragged the fast boot file inside the sdk rar you download for the One into the command prompt then entered "fastboot erase cache" and hit enter then it let me boot into recovery and I reflashed the rom.
maigre said:
Once you unlock the phone, it'll say "tampered." I don't think you can change that, even if you relock. It's fine, really, though if you want to resell the phone at some point, an unfamiliar user will see this as a red flag, even if you tell them you've rooted the phone. It's sort of a poor choice of working on HTC's part, given that they offer you as a user the tools with which to unlock the phone.
Click to expand...
Click to collapse
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
C-4Nati said:
So essentially if you have a problem and have insurance or a warranty you can't get anything done to repair the phone because even if you re lock the bootloader and unroot they can still see it?
Click to expand...
Click to collapse
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
maigre said:
I hope it's not that extreme. HTC gives you the tools to unlock, after all, for the purpose of doing things that people do with unlocked and rooted phones. At http://www.htcdev.com/bootloader/, HTC says
It is our responsibility to caution you that not all claims resulting or caused by or from the unlocking of the bootloader may be covered under warranty.
So they imply that at least some claims on an unlocked phone will be covered, possibly even some claims related to the unlocking. I don't know what HTC's history is along these lines, but I'd hope that they see it as being in there interest to reasonably support the dev and geeky community. Getting a bad reputation on XDA, for example, doesn't strike me as being a great business tactic. Not that companies are always so benevolent.
There is warranty risk in unlocking any phone, but it's done all the time as the participation in this forum shows.
Click to expand...
Click to collapse
Yeah I understand. I know I'm going to terminate the insurance I have with T-Mobile soon because I've violated the terms with them. I just have a slight screen lift like many others described on the top and bottom by the speakers and it's not bad at all just noticeable because I inspected it like a mad man when I heard the rumors. I can deal with it easily in it's current state as it's not a problem but if it were to become worse I'm not sure what to do. I know the chances being taken by unlocking as I've always done on every device I've had, I've just fortunately never had a defected device so it wasn't a problem.
4_SUXEN said:
When I install a custom rom and get stuck in boot loop. I always do a factory reset and my new rom starts right up. Works every time. I see you solved your problem but maybe next time you try this before you do anything else. Please thank if help
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Nope that didn't work, I've owned several android devices and did what you just said and it always worked. This is the first time I've owned a non Samsung device in a while (because I used Odin with those) and I couldn't get into recovery at all and factory reset in the bootloader did nothing. Not much experience with fastboot as I've never had to use it but I'm glad I did so I have that in case I need to do it again in the future.
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Asus Eee Pad Transformer Prime
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Eee Pad Transformer Prime Q&A, Help & Troubleshooting
Good luck!
Bump, could really use some help...
GiordyWarner said:
Bump, could really use some help...
Click to expand...
Click to collapse
There is only hope, if you can manage to get into bootloader screen by pressing power + vol down.
APX mode would only help you, if you had pulled your nvflash files.
GiordyWarner said:
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Click to expand...
Click to collapse
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
gsanglan said:
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
Click to expand...
Click to collapse
This has nothing to do with what he is asking.
flumpster said:
This has nothing to do with what he is asking.
Click to expand...
Click to collapse
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Jimboy00 said:
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Click to expand...
Click to collapse
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
flumpster said:
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
Click to expand...
Click to collapse
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Jimboy00 said:
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Click to expand...
Click to collapse
Unfortunately unless you have nvflash backups then you will have to get the board replaced. Forget contacting Asus as they would charge you more than the tablet is worth. Try and find one with a smashed screen on ebay etc cheap that still works that you can swap the board out from.
lemicp said:
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Click to expand...
Click to collapse
Thanks for your feedback,
So I don't have these files :crying:
I found also another thread with same story, and it seems that I can search for a new MoBo....
http://forum.xda-developers.com/showthread.php?t=2143942
...or buy a new tablet, maybe the better solution...