Can really use help from anybody that might know what to do. I was in the process of installing PA Rom and it was taking an incredibly long time. It wasn't until afterwards that i realized I should't have done it but I powered off the phone mid installation and now my /system won't mount. I realize now that this phone takes an incredibly long time to actually install ROM's from reading all the other threads. I should have done more research before jumping to conclusions...
Now i'm at the point where the phone will turn on with the LG bootscreen and just sits there. I'm able to get into download mode and I tried this method
http://forum.xda-developers.com/showthread.php?t=2471370
but the software keeps closing on Windows 7. I'm trying to get my hands on Windows XP as one of the posts was successful on it, but now I'm in such a bind.
Anybody else run into such an ordeal? I'm stuck but have my last hope on trying it on Windows XP. If not, then it looks like i've successfully bricked it to the max.
Related
I seem to be having a little problem here. I've been wanting to root an android device and after reading about how simple and fail proof the TF rooting experience is I decided to take the plunge.
I found a tutorial on another site (I'm not able to post the link because of forum rules) and decided to proceed. I followed the instructions to the letter and got confirmation that the “phone update was successful” but after rebooting the TF is stuck on the “Eee Pad” screen. I’ve tried rebooting into APX mode but the computer doesn’t find the device.
I’ve looked elsewhere regarding how to unbrick the device but every solution that I see requires booting into APX. Please help!
Edit: I'm sure that it's important that you know what exactly I did. The site that I got the tutorial was eeepadhacks dot net. I'm almost positive it's using the Nvflash method.
Posted this in the middle of the night and it's almost off the first page. Bumping it for an answer...hopefully.
You are in the wrong section. Look in the Android Development section. The first topic there is about unbricking your device.
http://forum.xda-developers.com/showthread.php?t=1123429
Not too experienced with the TF, but had the same bootloop type problem on Android phones straight after rooting.
Can you still get into recovery (power off, then hold the power button + volume down until the message shows up, then press volume up)? Try this if you haven't already. If you can get into the recovery you've installed (clockworkmod), you'll be able to flash a new ROM such as Prime and it should be working. If it's the same problem I've run into then it's not bricked, it's just somehow screwed up the original ROM during the rooting process.
Try to get into recovery and let me know. If it doesn't work, then hopefully someone else can help but I wouldn't worry much. It should be relatively easy to fix.
I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714
Thanks for the replies guys. I saw your thread last night Vert and that does seem to be the exact problem that I am having. The difference is that I can't get the TF to turn off.
If I hold the power button until the screen shuts off it just reboots. The only way that I can get the screen to turn off is by holding down the volume up button and the power button simultaneously but that doesn't appear to put it in APX mode. At least my computer doesn't seem to recognize it as such.
My plan is to redo it by following the link that you posted (I saw that last night too) but I don't think there's any way to do that until I can get the TF to show up on the PC. Anyone have any suggestions?
After playing with it for a couple of minutes I've noticed that when I put the TF into APX mode a new entry appears under the USB Controllers. It is called NVIDIA USB Boot - recovery driver for Mobile devices.
Hopefully that is helpful information....
Thanks again!!
Are you on windows 7? If so, open up device manager by going to start menu>right click on computer>manage>device manager. Then hold power/vol up on your transformer until the screen doesn't turn on. Device manager should then refresh. Look under Universal Serial Bus controllers and "Nvidia USB Boot-recovery driver for mobile devices" should show up. This means it is in APX mode. If that doesn't show up try reinstalling the drivers. From there you can run root.bat and it will boot up
Good luck
EDIT:Looks like you got it while I was typing lol
Thanks for your help guys!!
I'm back up and running. I'm not rooted but at least my TF is back alive.
I'll try again later today using that video that you posted Vert.
Thanks to all and enjoy the rest of your weekend!
At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.
poltak11 said:
At least you got it back up and running. When you try it again, let us know how it goes. Hopefully should work smoother this time if you know where you went wrong.
Click to expand...
Click to collapse
Yup, got it all up and running and am happy to report that I am now sporting Prime 1.5 on my newly rooted TF. Thanks again to everyone that helped out!
I had this problem earlier, and I used nvflash to recover. I thought I was not in apx mode as well but I was. Win 7 64 did not show it but when I flashes it worked. Just try it.
Sent from my Transformer TF101 using XDA Premium App
Vertiginouz said:
I had the same problem and posted about it here http://forum.xda-developers.com/showthread.php?t=1181795
What happened to me was that I forgot to unzip the boot.img file from 84411.zip and copy it into the "root" folder in tf_rootkit_31, which I downloaded from the rooting tutorial on xda. That caused the transformer not to boot up. I then held power until it turned off, then held power/vol up until the screen turned black, that means it's in APX mode. Then I ran root.bat and rebooted, works fine now!
Not sure if you missed the same step since you used another tutorial, just try starting over again from the tutorial I used here http://forum.xda-developers.com/showthread.php?t=1125714
Click to expand...
Click to collapse
The reason why you forgot may be because in the instructions it tells you to unzip the files higher in the thread before Step 1 begins.
"
extract the file inside the zip to directory root before running root.bat
for ww 8.4.4.11 version. thanks for the help from poet,paddy01,peacemaster,rebound821 provide me the boot file
for tw 8.4.4.11 version thanks for the help from butro for the boot file.
Thanks for the fone_fanatic to do the walkthru.
Ok, just did this and worked flawlessly, have root and CWM in under 10 minutes!
I'll replay step by step what i did to help those that are still confused. (it looks long but its really not, i was just very detailed causing this to be more of a "take my hand and i'll walk you through it")
Some background info. Highly recommend reading these if you don't know what either is!
Rooting Explained + Top 5 Benefits of Rooting by androidpolice.com
What is ClockWorkMod recovery and how to use it by addictivetips.com
STEP 1. Make sure you have all the correct asus drivers installed. Not sure if this is necessary but i had them all installed previously and i didn't run into a single issue.
Hello,
I bought my wife one of these tablets for her birthday. It was running great, decided to root it so that I can uninstall the bloatware that was eating this tablet up after using it for a week. Uninstalled all the happy lenovo stock softs, everything is all good... Well I decided to put JB on this tablet after root stock rom was running great. I made a backup, but somehow I completely crashed the file system, and I can get into recovery VOL+ VOL- POWER, while usb plugged in. I had a hell of a time getting drivers install in windows, and also debian. Drivers are like NOT installing properly, or it will install properly in windows, then I have an error on another device etc. I cannot get past the lenovo splash screen that does nothing, and the only way I can get adb devices to recognize the device, is when it is in splash screen mode on lenovo, but NO other adb commands will work! adb shell will simply freeze terminal or dos. It will not read micro SD card when I boot recovery, linux or windows has no idea how to even read my device when I plug it in while in recovery, im about to buy her a new one. I have googled and googled for days and hours for a fix on this. If you need detail, please ask, and I will gladly give you info. Please help, my wife is super pissed.
Thanks!!!
hey have you managed to solve this problem? I think I have the same issue as you. my tablet just doesn't want to boot normally even after reloading roms.
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
Hello!
THink I have bricked my phone, but just checking before I go through what I suppose is a long process with oneplus.
Looking for any help. I had a working device - unlocked bootloader and installed TWRP and magisk using MauronofrioTool. ok - however, I found out I couldn't use a fingerprint security option on that would have been anoying. So... Long story short. I used MauronofrioTool to relock bootloader. Oops - so that didn't work. THen found out I couldn't do anything except stare at g.co/ADH message on my screen. Couldn
't get to fastboot or TWP. ANyway, so I managed to up and down volume and enter into TWRP. Was still connecting to the tool, so I downloaded factory Zips and tried to install via tool after unlocking - Seemed to be working ... but it stopped mid way through a process and hasbn't come back! NOthing at all. I wonder if I could have triggered an OEM thing? ANyway - literally nothing no buttons work no screen action. I see a QUSB_BULK_CID:etc number when connecting the phone, but that is it. No fast boot or any other actions available.
PLease, pretty devastating, Anyone know if I can do anything?
I'm no pro but I use this tool which helped me:
henk-jan said:
I'm no pro but I use this tool which helped me:
Click to expand...
Click to collapse
Thank you. I feel I am little past this stage now though.. Also trying the brick reprieve software . Just can't get my computer to recognise the phone now. No ability to get to emergency download path - think it is my crappy cihinese pc (old Huawei tablet basically) or Windows via apple that have me stranded.
**********SOLVED
THe crappy Chinese language Windows tablet worked as the unbrick OP said WIndows would. Must be a kink in the Windows via Mac that could get me into the situation, but not out.
Very relieved... Even though I still am not 100% sure what I actually ended up clicking to get it to register and connect with the unblock tool (which of course was in Chinese) hahaha.
Cheers
CHeers though
Glad you got it sorted out! Cheers
Need Help, please
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
rickhurl said:
Just received my OnePlus 8 pro, decided to Root and unlock the bootloader---this went fine.
I then went and upgraded to Android 11 DP3.
I'm now only able to get into Fastboot. at points it will try to boot but only get to the logo screen and then goes black.
When the phone boots up, it goes to Qualcomm CrashDump Mode.
I've been attempting to solve this for half the day with no luck. I've tried Msmtool, but it doesn't recognize the device, even after loading drivers again.
Is there a way to load a ROM from fastboot mode?
Hoping someone can assist, this is super frustrating and I would appreciate any help, please.
Rick
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
cultofluna said:
https://forum.xda-developers.com/oneplus-8-pro/how-to/rom-stock-fastboot-roms-oneplus-8-pro-t4083997
Click to expand...
Click to collapse
Thanks so much. I ended up getting Msmtool to work. Although my device wasn't on (black screen) and it didn't fully show up in the tool, I decided to start the process anyway and it began to load.
I've been on here for over 10 yeas (XDA) I've just lost my account info and made a new one.
Thanks for taking the time to respond. Much appreciated.
Hello!
I recently got my hands on a Nokia Lumia 520 for tinkering with. Its running on really old firmware, and I figured before I try anything weird, I'd mess around with it in its stock state. Thus, I tried updating the firmware.
The internal updater returned an error, stating that it could not contact the server for whatever reason. I figured this is most likely due to the Windows phone being discontinued, so I scoured the internet for firmware files. I eventually stumbled upon a YouTube guide that linked to a guide on Microsoft's Own guides page. It explained how to reinstall the firmware to a stock state. Desperate for progression. I gave it a shot.
The guide provided the "windows Device recovery tool", Which I would install on my windows 11 machine. I then proceeded to run the software and plug in the phone. HURRAY! It was able to tell me exactly what type of phone it was. Clicking the option to proceed, I was shown a screen explaining just how dated my firmware was. Suggesting It would fetch newer if not the latest firmware for me. I clicked on install and it started downloading.
I waited patiently for the software to download the firmware. After which it went to the installation screen. It then attempted to put the phone in flashing mode. Explaining that in this mode, the phone would restart, then have a blank screen. Instead what happened was that the system restarted normally, asking me to unlock the device. I wondered if maybe I had been impatient, so I waited for another while. The phone restarted again, still on the normal lock-screen. This happened another two times before the Recovery tool gave up and told me it had failed.
My question: Is there any reason why it would do this? Are there any methods to get it into flash mode?
I would hate to discard the potential of this device simply due to the inability to flash it. And I really hope it can be helped. Please let me know if there's anything else I should share about this. I'll happily take any help I can get!
Thanks in advance!
Edit, after a lot of trial and error, I managed to force it into flashing mode. Turns out the guides I followed missed a step. Pressing the Power and Camera buttons did the trick