Ok, girlfriend bought a used TF201, it had some version of cynogen mod installed that was too unstable for her to use. Android was 4.1.1, so I began/completed the nvflash backup instructions
After the files were safe and stored triplicate, I flashed TWRP 2.3.3.0, and attempted to install androwookie 1.51. The device had the cache, dalvik cache, and a factory reset performed. The install was completed without a hitch, upon rebooting, the wookie pops up for a few seconds and i eventually get kicked out back into TWRP.
I can not acess ADB mode (I think), when I boot with the Volume Down pressed, it has no options and boots to recovery in ~5 seconds. I have attempted to restore with nvflash files but for whatever the reason I can not get the thing to boot back up. I have also attempted to use the 'how-to unbrick' guide without success
I have attempted to revert to the stock JB files but those fail to boot as well and im forced to flash TWRP again. Clearly im a noob, and I need some help, anything would be appreciated before she does something horrible to me
Ive been messing with this for so many hours im burned out. I eventually was able to reflash the stock ICS roms on to the device, and it booted up a nasty wookie/asus ics hybrid. I attempted to run the OTA update, and it failed... I think this is now a 'hard brick'.
I have the nvflash files, an unblobed JB, unblobed ICS, androwookie, the JB/ICS versions of twrp, and ran through hundreds of pages of information that didn't end up helping. Now when I try to get wheelie to bootstrap it gets stuck at 100%, the tablet doesn't light up, maybe I had a bad flash im not sure...
My guess is that you are trying to install androwook with the ICS bootloader. You have to install the stock jellybean ROM first (from asus's website...unzip it once after you download...extracted file should be another zip...use this extracted zip file to install the os. After that reinstall twrp for jellybean, then install androwook.
laggyprime said:
My guess is that you are trying to install androwook with the ICS bootloader. You have to install the stock jellybean ROM first (from asus's website...unzip it once after you download...extracted file should be another zip...use this extracted zip file to install the os. After that reinstall twrp for jellybean, then install androwook.
Click to expand...
Click to collapse
Sadly when attempting to go into apx mode the device is recognized by my pc, but when bootstrapping? To get into nvflash mode wheelie gets stuck sending the file 100%. I think I flashed something wrong (was typing commands by hand) and mixed up a 5 with a 4... Anyways the screen won't even display anything at all anymore, it's blank. Do I need to contact asus now, or is there a way to get wheelie/nvflash working?
DocCox said:
Sadly when attempting to go into apx mode the device is recognized by my pc, but when bootstrapping? To get into nvflash mode wheelie gets stuck sending the file 100%. I think I flashed something wrong (was typing commands by hand) and mixed up a 5 with a 4... Anyways the screen won't even display anything at all anymore, it's blank. Do I need to contact asus now, or is there a way to get wheelie/nvflash working?
Click to expand...
Click to collapse
I suggest you contact the dev's in the nvflash thread first... being very poilte of course since in your situation you need all the friends you can get. If they can get you back to ics then go to the hairy bean (androwook) thread, the OP should have all the info you need to go up to jellybean. You should be able to go directly from ics to jb by following the instructions of course. If you have questions prior to making the leap, ask in the thread, the folks there are quite helpful.
Gage_Hero said:
I suggest you contact the dev's in the nvflash thread first... being very poilte of course since in your situation you need all the friends you can get. If they can get you back to ics then go to the hairy bean (androwook) thread, the OP should have all the info you need to go up to jellybean. You should be able to go directly from ics to jb by following the instructions of course. If you have questions prior to making the leap, ask in the thread, the folks there are quite helpful.
Click to expand...
Click to collapse
A very good suggestion, I dont have high hopes for this transformer but it would be nice to see it come back to life. I looked over the 60 something pages of posts in the dev thread but can't post there because i lack the minimum post count. I don't see people with the inability (recently) to get their prime to switch over to nvflash mode using a wheelie bootstrap unless they missed something obvious. As mine was working for 12 solid hours of trying to restore its clear I flashed something wrong, but the nvflash,adb,etc installs are fine.
I will attempt to send a PM, and hope for the best. Thank you Gage_Hero
DocCox said:
A very good suggestion, I dont have high hopes for this transformer but it would be nice to see it come back to life. I looked over the 60 something pages of posts in the dev thread but can't post there because i lack the minimum post count. I don't see people with the inability (recently) to get their prime to switch over to nvflash mode using a wheelie bootstrap unless they missed something obvious. As mine was working for 12 solid hours of trying to restore its clear I flashed something wrong, but the nvflash,adb,etc installs are fine.
I will attempt to send a PM, and hope for the best. Thank you Gage_Hero
Click to expand...
Click to collapse
Ok, for a start if you have the files you created doing nvflash backed up you can always save the device.
Can you still get to fastboot by holding down the power button and volume down button for about 10 seconds until the icons appear?
flumpster said:
Ok, for a start if you have the files you created doing nvflash backed up you can always save the device.
Can you still get to fastboot by holding down the power button and volume down button for about 10 seconds until the icons appear?
Click to expand...
Click to collapse
Hearing that is great
Heres the current situation, I mistyped a 5 with a 4 and told the unit to restart.
So
Power Vol+ = computer recognizes APX mode - however wheelie sends the blob and gets stuck at 100%
Power = Blank screen. HDMI also has no output.
Power Vol- = Blank screen, HDMI has no output.
Using the reset button, i receive the same results
I may be the only idiot to ever brick a prime this hard
DocCox said:
Hearing that is great
Heres the current situation, I mistyped a 5 with a 4 and told the unit to restart.
So
Power Vol+ = computer recognizes APX mode - however wheelie sends the blob and gets stuck at 100%
Power = Blank screen. HDMI also has no output.
Power Vol- = Blank screen, HDMI has no output.
Using the reset button, i receive the same results
I may be the only idiot to ever brick a prime this hard
Click to expand...
Click to collapse
Try following the instructions in this post. If wheelie is still failing try another computer.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
flumpster said:
Try following the instructions in this post. If wheelie is still failing try another computer.
http://forum.xda-developers.com/showthread.php?t=1927818&highlight=nvflash
Click to expand...
Click to collapse
Step 4 always results in the same issue. I have also tried older versions of the universal drivers without success.
Wheelie sends the file, reaches 100%, returns to the next line and remains blank. After sending the command, attempting to send it again from another window (or to send additional commands) the device will not communicate until it is restarted.
I have attempted this on all 3 machines I own (2x windows 7 x64, and a windows 7 X86)
In the past the apx commands worked fine but ever since I messed up the flash and told the device to restart it has had this issue . I have also drained the battery down and attempted to get it working again, and finally opened the device and turned off the mb power and flipped it back on without a change in results.
I also downloaded and ran a linux live CD to run the commands and it was unsuccessful. The screen always remains blank and wheelie always sends 100% and stops.
I appreciate the assistance flumpster
DocCox said:
Step 4 always results in the same issue. I have also tried older versions of the universal drivers without success.
Wheelie sends the file, reaches 100%, returns to the next line and remains blank. After sending the command, attempting to send it again from another window (or to send additional commands) the device will not communicate until it is restarted.
I have attempted this on all 3 machines I own (2x windows 7 x64, and a windows 7 X86)
In the past the apx commands worked fine but ever since I messed up the flash and told the device to restart it has had this issue . I have also drained the battery down and attempted to get it working again, and finally opened the device and turned off the mb power and flipped it back on without a change in results.
I also downloaded and ran a linux live CD to run the commands and it was unsuccessful. The screen always remains blank and wheelie always sends 100% and stops.
I appreciate the assistance flumpster
Click to expand...
Click to collapse
Step 4 isn't really doing anything except putting you into nvflash mode ready to run the next commands.
When it says " 2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)" are you also putting all the files you backed up when you did the nvflash process in the first place in the same folder?
flumpster said:
Step 4 isn't really doing anything except putting you into nvflash mode ready to run the next commands.
When it says " 2. Extract wheelie, nvFlash and the unblob'd ROM to a directory (avoid spaces in the directory path)" are you also putting all the files you backed up when you did the nvflash process in the first place in the same folder?
Click to expand...
Click to collapse
Yes, I copied all of the backed up files into the same directory. Its where all the files are, TWRPJB and TWRPICS, three seperate roms, adb files, etc. Step 4 is (if im remembering correctly, im currently not at home) when the device actually enters nvflash mode - which it fails to do, and the cmd window just sits there. The directory all the files are placed into are c:\android just to keep it simple for me
DocCox said:
Yes, I copied all of the backed up files into the same directory. Its where all the files are, TWRPJB and TWRPICS, three seperate roms, adb files, etc. Step 4 is (if im remembering correctly, im currently not at home) when the device actually enters nvflash mode - which it fails to do, and the cmd window just sits there. The directory all the files are placed into are c:\android just to keep it simple for me
Click to expand...
Click to collapse
I'm in bed at the moment but give me a shout later when you're home and I'll run the commands myself again and see exactly what happens.
But basically wheelie should just use the file you backed up from before on step 4 to enter nvflash mode so nothing should go wrong at that point.
flumpster said:
I'm in bed at the moment but give me a shout later when you're home and I'll run the commands myself again and see exactly what happens.
But basically wheelie should just use the file you backed up from before on step 4 to enter nvflash mode so nothing should go wrong at that point.
Click to expand...
Click to collapse
You betcha, thank you sir
ok so ive reinstalled everything, grabbed one of my backup blobs just in case something went wrong with the one ive been using
Heres a screenshot of what the window looks like after an hour of waiting
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
is there a next step other than contacting asus?
DocCox said:
Ok, girlfriend bought a used TF201, it had some version of cynogen mod installed that was too unstable for her to use. Android was 4.1.1, so I began/completed the nvflash backup instructions
After the files were safe and stored triplicate, I flashed TWRP 2.3.3.0, and attempted to install androwookie 1.51. The device had the cache, dalvik cache, and a factory reset performed. The install was completed without a hitch, upon rebooting, the wookie pops up for a few seconds and i eventually get kicked out back into TWRP.
I can not acess ADB mode (I think), when I boot with the Volume Down pressed, it has no options and boots to recovery in ~5 seconds. I have attempted to restore with nvflash files but for whatever the reason I can not get the thing to boot back up. I have also attempted to use the 'how-to unbrick' guide without success
I have attempted to revert to the stock JB files but those fail to boot as well and im forced to flash TWRP again. Clearly im a noob, and I need some help, anything would be appreciated before she does something horrible to me
Click to expand...
Click to collapse
Not for nothing, and please moderate my knowledge, but I can sell you mine ( unlocked, with Twrp installed, running Hairy Bean 1.5.1 tweaked.... no glitches, score 15,000 on AnTutu....PM me, I'll make the sale and guarantee it's valuable!
Inserted 20¢ for the first three minutes
DocCox said:
ok so ive reinstalled everything, grabbed one of my backup blobs just in case something went wrong with the one ive been using
Heres a screenshot of what the window looks like after an hour of waiting
is there a next step other than contacting asus?
Click to expand...
Click to collapse
Guessing you didnt go back to flumpster... he can help you.... I think you are still safe but dont experiment....
Im unbricked but apparently not out of the woods. Updating past 4.0 seems to be impossible for me right now.
The command to force this type of brick back into nvflash mode is
Code:
wheelie -r --blob blob.bin
Notice it requires "-r" to be added. That was it!
Yea, I just wasted so many hours on this I could have purchased a new tablet. If I had hair I would have pulled it out of my head already!
The first boot looked good, the tegra was bottom right but was stuck loading, I installed TWRP for JB and put myself into another brick. Long story short, I have ICS running 4.0.3, but cant update for the life of me. The screen will go blank (original brick style) or gets into a boot loop or has the unrecoverable boot error
Ive tried just using the update from asus (US version, as is tablet) and it always appears to update correctly (blue progress bar) but never ends up booting. I tried getting out of the boot loop using a guide here and it wasn't effective. I also tried flashing one of the unblobed 4.0's and it didn't work either. Every time ive been forced to reflash 4.0.3. This has/is a learning process for me, my tf700 updates fine and I can flash between roms but I cant get this darn tf201 to do anything without bricking. My ultimate goal here is to get a stable version 1.51 Androwook w/ the 1.7 and data2sd enabled. Anybody willing to hold my hand from my current 4.0.3 state to the final completion?
DocCox said:
Im unbricked but apparently not out of the woods. Updating past 4.0 seems to be impossible for me right now.
The command to force this type of brick back into nvflash mode is
Code:
wheelie -r --blob blob.bin
Notice it requires "-r" to be added. That was it!
Yea, I just wasted so many hours on this I could have purchased a new tablet. If I had hair I would have pulled it out of my head already!
The first boot looked good, the tegra was bottom right but was stuck loading, I installed TWRP for JB and put myself into another brick. Long story short, I have ICS running 4.0.3, but cant update for the life of me. The screen will go blank (original brick style) or gets into a boot loop or has the unrecoverable boot error
Ive tried just using the update from asus (US version, as is tablet) and it always appears to update correctly (blue progress bar) but never ends up booting. I tried getting out of the boot loop using a guide here and it wasn't effective. I also tried flashing one of the unblobed 4.0's and it didn't work either. Every time ive been forced to reflash 4.0.3. This has/is a learning process for me, my tf700 updates fine and I can flash between roms but I cant get this darn tf201 to do anything without bricking. My ultimate goal here is to get a stable version 1.51 Androwook w/ the 1.7 and data2sd enabled. Anybody willing to hold my hand from my current 4.0.3 state to the final completion?
Click to expand...
Click to collapse
Get it back to where you have it working and add me on Google talk on computer.
I will pm you my email for it now.
Also you need to know that I'm UK and we seem to be missing each other time wise so you might have to do this earlier in the day for you.
flumpster is the man. I can't say enough for this guy, he spent countless hours helping me through this unique brick (and lost a nights sleep over it!) when so many others had no interest or were straight up hostile when contacted for help via pm's. My girlfriends tablet is running androwook right now, and I get to sleep in the bed agian!
For others, the brick resulted in anything not ICS resulting in fatal bootloops, impossible to recover from. Power and Volume down resulted in no options avaliable, and unless flashed manually nothing would install. The twrp's would crash repeatedly when sideloaded, installing, using external SD cards, or doing anything but sitting on the home screen. Not sure what caused the issues, not sure how to reproduce it, but flumpster still guided me through the process. The only solution was working with nvflash through linux to gain acess to more advanced commands, and with the knowledge I gleaned from this wizzard I was able to complete the process. Many thanks flumpster.
/me off to bed finally!
Related
Update: Hallelujah, we have seen the birds!
Just for future reference to those of you who may be stuck in an "APX loop", where NVFlashing and even repartioning do not work for you. I tried many things, and only one thing worked.
Didn't work:
1) NVFlashing to anything
2) Repartioning or wiping
3) Wiping out all storage on the SD card
After doing many, many rinse and repeats on the above, the only thing that did work were these instructions:
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Click to expand...
Click to collapse
Now, I don't know of too many cases like mine where APX was the only thing that was working and that no amount of CWM or NVFlashing could bring back whatever was wrong with the bootloader, but this method forced a recovery image restore and got me back to the point where I can now power down and reboot. And for that, I thank this fine community!
I think we need a better guide somewhere on... Stages of recovery. If this doesn't work, here's the next deeper level. (Example: Level 1, wipe data/cache and reflash the rom. Level 2: Repartition and fix permissions. Level 3: NVFlash for 1.1 or 1.2 back to stock. Level 4: run the steps I have listed above. Level 5: fixing the bootloader. Level 6: Remove the case cover and short the back.)
Anyways, thanks again guys. Hopefully someone else will search with the same issue I had and get fixed as I have.
try this (not a developer here) when it boots up use your computer to delete all the files on the sd card so it looks blank- not sure if it will fix your issue but if there is a file on there messing your reboot into cwm that should will get rid of it. let me know how it goes. (standard at your own risk disclaimer) i have done this before just to see what would happen and nvflash brought it back up.
Hey, thanks for the reply. The sdcard was already blanked out through my various steps, so that doesn't appear to be the problem. Same things happen.
Now, that's just the app data and such on the sdcard, so I am guessing if I was able to see/delete all the system files instead via USB and delete it that way, I'd see something else.
just to bee clear i would delete everything on there not just the system files- so when you go to the drive from your computer it shows nothing at all.
here are the steps i would take start to finish.
1 nvflash rom
2 connect to computer, mount usb, then highlight and delete all files on gtab.
3 nv flash again (preferably with a stock rom with cmw pre loaded
4 reboot and pray that this fixed it.
OP - What size is the nvflash file you are using? I have run into a similar issue before with the larger nvflash.exe (like 152kb). It should be 140KB.
Just something else to check.
So to clarify, when you nvflash the 3588 stock image, it will automatically reboot at the end of the nvflash_gtablet.bat batch file?
pugsby said:
Hey all. Little frustrated since I've tried most of the tricks and still have a soft-bricked device. Not sure how it happened originally, but one way or another, I have a bad bootloader and no access to CWM.
APX works. I can NVFlash 1.1 or 1.2-based Stock or otherwise roms, and they boot (once, and only once...) . I can get USB mount. I've tried them with and without CWM pre-installed and see no differences.
But as soon as I reboot or power off, it just returns to APX mode. It is only a black screen, however. No birds, no logo, no nothing. The only way to make it boot again is to NVFlash it again.
All the instructions say to enter CWM to re-partition or to wipe data. That's great, but I have no access to CWM. Pressing the buttons during bootup does nothing because the device never makes it that far through bootup. And the format utility doesn't wipe enough data to return this back to a truly blank device, because when I nvflash, my apps still show to be there and I want it back to a blank slate.
I've tried pressing the buttons directly after a NVFlash to enter CWM that way, but it just goes straight into the rom.
Others have suggested popping off the back of the case and grounding out things to reset that way, but I thought that was just if APX didn't work, but APX is the only thing that DOES work, so not sure if it applies. (Let me know if I'm wrong there)
More things to try?
Click to expand...
Click to collapse
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
After you repartition, wipe data, clear cache, etc. it might still loop into APX. If it does you'll need to force it to install a new bootloader. I'll dig up a link to the procedure if you need it.
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
K J Rad said:
I've worked on quite a few of these and still can't replicate it on my own either. Most of them had flashed an incompatible version of ClockworkMod (usually with ROM Manager) and a few had tried to move from Cyanogen directly to a 1.2 based ROM. A very small minority of them had issues with their internal flash memory. No one consistent thread that ties them all together that I've found. One interesting point though... In every case it was easy to recreate the problem after the tablet had been "Fixed." All I had to do was nvflash with the same image that was traditionally used for returning the devices to stock (bekit 1105).
Click to expand...
Click to collapse
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Acidburn find out a solution for this problem
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
K J Rad said:
With the tablet in APX mode and plugged into your computer...
1) Open a command shell
2) Navigate to your nvflash directory
3) type in the following command but DO NOT hit enter
nvflash --bl bootloader.bin --download 6 part6.img --go
4) Hold down the volume UP key on the tablet and press the enter key on your computer.
5) Continue to hold the volume UP key until the tablet starts the nvflash.
6) Release the volume up key and when the nvflash finishes it should boot into CWM
Click to expand...
Click to collapse
This got me into CWM (Yay!). This, however, did not fix the APX looping (boo).
I repartitioned, wiped, nvflashed, wiped, repeat. Even though I have more options now with CWM, the end outcome is still the same that after the initial boot, it won't boot again.
BUT, I did find a working method. See the original post.
goodintentions said:
I'm interested to know what the hell you did to get to the apx bootloop in the first place. I've gone through great lengths to try to replicate people's problems. I've even purposely done things out of order, done things wrong, drop the gtab couple times, etc. and I've never run into this problem.
Click to expand...
Click to collapse
I was hoping you'd respond, goodintentions, as I used your NVFlash files and instructions this last time around from your very handy site.
I'm not sure exactly what happened. I do know that Rom manager was involved somehow, trying to use that integration with recovery. (I know, not recommended, but at first it acted like it would work).
Also, I think a 1.2 Rom was mistakenly flashed on top of a 1.1 bootloader somehow.
The details are fuzzy. It's been so many things since then that who knows..
goodintentions said:
I'v tried rom manager, wrong cwm version, and wrong bootloader. And I still can't replicate this apx bootloop thing. And I have 2 gtabs to work with. A 3rd one should be coming soon. Weird.
Added by edit.
I'm assuming you're some kind of technician or repairman? If so, then it's good that you're telling me this. I've been considering the possibility that this apx bootloop thing is not really an apx bootloop but rather something the user is doing or a button is stuck or something silly like that. Good to know the problem is real.
Mind telling me how you fix this? Since I can't replicate this, I have no idea how to even begin fixing this.
Click to expand...
Click to collapse
I am a tech. Been working with/on/in electronics and computers for roughly 35 years. I had a hard time believing the problem was real until I had one in my hands that was doing it. I've tried doing it to my own tablet but a simple nvflash always got me going again.
imurg said:
Please check this thread
http://forum.xda-developers.com/showpost.php?p=11306979&postcount=92
Note that he is using the NVFLASH_46 and although is has been deprecated, it works like a charm:
1) NVFlash the g tab_46 (it works with 46 and doesn't with other)
2) Let it finish and boot up
3) Go to storage setting and unmount the sd card.
4) Run a format.
5) Go to security and do Restore to factory settings
6) As part of this it will reboot. When restarts you'll see the birds. Everything is back to normal.
Good luck
Click to expand...
Click to collapse
This is successful in some cases but not all. In some cases the bootloader has to be updated using factory stock recovery. ClockworkMod and nvflash don't update the bootloader (and I suspect some other system related partitions/information) properly. For those cases the fix is a little more complex. This process...
http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
has worked on all but one of the tablets I've recovered. The odd one out required an extra reboot (though I was doing the steps from memory and on an unfamiliar computer so I could be mistaken). However... as noted above... a subsequent nvflash of even the same image resulted in another APX loop. The end result was I had to craft a custom nvflash for each of those machines to avoid the problem in the future. That may or may not be necessary for all cases but since it's relatively easy I just do it out of habit now.
Keep in mind that serious APX looping issues are very rare in the grand scheme of things. Many times folks get confused and fail to follow directions properly and think they have a bigger problem than they really do. The overwhelming majority of times a simple nvflash and repartitioning will fix these things right up.
Added: BTW, the best way I've found to avoid the APX loop issue entirely... do a data wipe before you flash a new ROM and then again immediately after and before you boot it for the first time. I know... one should be enough... but if you make it a habit to do two... then you'll probably remember to do at least one of them ;-)
Great info. I shall try not to enter another painful APX loop. I was shocked how many things I had to try and places I had to go before I found a working method. I guess I really did a number on this thing somehow. But I'm happy that it's back.
I didn't have to do the more painful one you mentioned, but honestly I was ready to try about anything short of slaying a dragon.
Okay, I think I'm completely hosed. But I thought I would ask if anyone has a solution. Here's the deal.
I was running the new stock 5274 on 1.2, went to turn on the tab and it wouldn't power up. This has happened before so I cracked the case, pulled the battery connector and plugged it back in then shorted A4 and powered up into APX. I ran NVFlash for the stock 4349 based image, figuring that I could then update it again after I loaded Clockwork. I've done this a bunch of times before, never had a problem. Until this morning.
When I try and run NVFlash, every time on part7.img I get "Failed to verify partition command failure: create failed" and NV stops dead in its tracks. I also tried to run the Format tool, which I've also done before, and get the same error at the same place. In fact, no matter what flash and try to run, 1.1 or 1.2 BL, NV bombs out at part7.img.
I'm at a loss. The only way to get the tab to power on is to short A4 into APX, but I can't flash anything. Any advice would be greatly appreciated.
Ronin916 said:
When I try and run NVFlash, every time on part7.img I get "Failed to verify partition command failure: create failed" and NV stops dead in its tracks.
Click to expand...
Click to collapse
Looks like you've developed some bad blocks on the NAND flash. Just skip loading that part7.img, then.
On most gTabs, partition 7 is the /misc (MSC in nvflash) partition which is not used by most ROMs (GtabComb uses it to create a single log file). So, it doesn't matter if this partition is not written by nvflash.
On some gTabs (like mine), partition 7 holds the .bmp file for the first splash screen (VS's 3 Gouldian finches). This, too, is not important. You'll just not get that first splash screen.
Just erase the partition, if you can, using the erase_image program in CWM after you restore the remaining partitions using nvflash.
Thanks for the tip. I tried removing part7.img from NV, but now it bombs on part9.img with a NvError 0x30012. So, that's a no-go, and now I can't even get into APX. Maybe the battery died, so I'm going to charge to full and see what happens. Still could use suggestions, though.
EDIT: Well, color me confused. The battery was dead, so I gave it a good 4 hour charge to full. Then I cracked the case and was able to get back into APX. I have NVFlash and the 1.2 4349 load here, so I figured I'd give it a shot. Sure enough, it ran through NV without an issue, and I'm back to stock 4349. Not one hint of an error. Dunno....maybe the tablet gods decided to smile down upon my today. All I know is, I'm back up. Don't know how....don't know why....just is.
so im pretty much a noob to this website and my g tablet but heres my problem
i was stuck at the bootloader (those frickin birds) so i decided to nvflash to get it back to normal, i followed the instructions step by step and it seemed to work, it booted normally and i thought all was good untill it randomly turned off, so i plugged it back into the computer and held the power button and i heard it connect so i nvflashed again and the white writing popped up, it finished, it got to the g tab screen then turned off again. i let it die last night and i just went to turn it on and nothing. help please
Sgt,
You may have to crack open the case and pull the power connection for a few seconds and then plug it back in. Seems like every tab is a little different, but you can reference this thread:
http://forum.xda-developers.com/showthread.php?t=1118087
Maybe that gets you back up into APX at least.
thanks for the help unfortunantly it didnt do anything, i think im stuck in apx mode because i can still nv flash, every time i do it goes straight to gtab screen then shuts off, i turn it back on and i can flash but nothing else
You may want to try this:
http://forum.xda-developers.com/showthread.php?t=1030042
It shows you how to NVFlash Clockwork. If you can then get into that, you could repartition and format you GTab, then load the ROM of your choice.
Posting here in hopes to expand help request.
deleted...
10char..
ok i nvflashed cwm and i believe it worked but i still cant get into it, the moment i turn on my tablet i dont get any load screens it just goes into apx mode thats it
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
Hi all,
Been browsing the forums for a few years quietly in the background, found them very helpful for rooting, Xiaomi and galaxy phones I've had, however, I have just got hold of a Kindle fire HD 7 4th gen (second hand), and to put it bluntly, I think who ever owned it previously has messed around with it.
It has OS 5.1.2.1 (march release) installed on it, and says its got the update sitting there ready to do, however, when I try to install it, it goes through the install process, but it comes back on as the above firmware, It also has random adds that pop up on it.
I have tried several different methods to root the device, so I can downgrade for root access or just upgrade it to the standard stock firmware.
Every time I attempt it it just comes back to the above firmware.
I've loaded all the drivers onto the comp, installed, uninstalled, re-installed. Even ordered a factory fastboot cable, but this doesn't seem to make a difference.
In device manager (with adb enabled on the kindle) it shows up as "android composite adb device" so I assume this is right, but whenever I try to use any of the kindle tools to get it into fastboot mode, the kindle switches off, (still shows as the above device in device manager) but it doesn't appear to enter fastboot mode, the kindle just sits there with a blank screen. No amazon or fire logo, just blank. The different programs I've tried to use, seem to be able to get it to start booting into fastboot, but once its switched off, ALL of the programs sit at "waiting for device" then finally "waiting for any device"
I'm kind of at a loss here. All im interested in now, is getting stock firmware back on it and thats it.
Any help would be hugely appreciated.
Thanks a lot.
I think you may be a bit confused as fastboot mode isn't a thing on these particular tablets as far as I know. Fastboot was needed to install firmware in the older 6 inch fires (2012 models) but these newer models do everything through the stock recovery menu. It sounds like you're going to need to sideload the firmware update through stock recovery, it's simple enough though.
First, make sure you have ADB drivers correctly installed. To do this, from your ADB shell with your Kindle attached type "ADB devices". You should see your device listed in the window. If it is, you're good. If not, you need to figure out the correct driver.
Assuming ADB devices returns the correct info, you then want to download the latest firmware. https://www.amazon.com/gp/help/customer/display.html?nodeId=201596850
This link is for 5.3.3.0 which should be the latest. Once you have the firmware downloaded, follow these steps:
Type "adb reboot recovery"
Use volume keys and power button to navigate to "Apply update from ADB"
From computer type "adb sideload "whatever the name of the firmware you just downloaded.bin"
From tablet select "wipe data/factory reset"
From tablet select "reboot system"
Complete setup
That should at least have you running a stable 5.3.3.0.
Also, credit for the copy-pasta steps I listed go to Powerpoint45. His original thread on how to downgrade to 4.5.3 can be found here: https://forum.xda-developers.com/fire-hd/general/how-to-downgrade-to-4-5-3-root-device-t3139351
Hope that helps.
Jesseb342 said:
I
Type "adb reboot recovery"
Use volume keys and power button to navigate to "Apply update from ADB"
Click to expand...
Click to collapse
Thanks mate much appreciated.
However, when I get to the above command, the kindle reboots but it just has a blank screen, no menu comes up to be able to do the sideload.
Thats where I'm getting stuck. Can't seem to access recovery at all. I have been able to get the device to show up in adb devices, but once I type adb reboot recovery it looks like it just shuts the kindle down, then I have to do a hard reset to get it to come back on again.
I have also tried the Linux ISO un-brick method. I get to do the handshake, but when it comes to the reader.sh step, it doesnt read anything.
I did notice one other person in that thread that also seemed to have a similar problem and it looks like there was no workaround, so I think I may have to get rid of this one and get another one instead.
carpergt said:
Thanks mate much appreciated.
However, when I get to the above command, the kindle reboots but it just has a blank screen, no menu comes up to be able to do the sideload.
Thats where I'm getting stuck. Can't seem to access recovery at all. I have been able to get the device to show up in adb devices, but once I type adb reboot recovery it looks like it just shuts the kindle down, then I have to do a hard reset to get it to come back on again.
I have also tried the Linux ISO un-brick method. I get to do the handshake, but when it comes to the reader.sh step, it doesnt read anything.
I did notice one other person in that thread that also seemed to have a similar problem and it looks like there was no workaround, so I think I may have to get rid of this one and get another one instead.
Click to expand...
Click to collapse
Ah, now I understand. It does indeed seem like someone messed around with it before you got it. I've seen this before and it's usually the result of trying to flash TWRP onto a device running Fire OS 5.x.x.
I'm sure you already know this, but just in case you don't TWRP is a custom recovery that gives the user much more control than the standard stock recovery. Anyway, what happens is that TWRP WILL NOT run if your bootloader is 5.x.x. It runs fine on 4.x.x but not on anything higher. Inevitably though, people on Fire OS 5 will flash TWRP. This overwrites the stock recovery. All is good until they reboot. Upon rebooting with 5.x.x bootloaders, TWRP won't run and stock recovery is gone. Sucky situation but it happens a lot and that seems to be what's happened to your tablet.
There may still be hope however. The most likely way for your stock recovery to have gotten overwritten with TWRP was during an attempt to root. Rooting on the HD 6 / 7 on anything higher than Fire OS 4.5.x isn't easy and requires you to downgrade to 4.5.3, block OTA's, root, then use TWRP to upgrade back to the OS you were on before rooting. Some people go through this long - winded process of rooting and are disappointed at the end to find out TWRP is gone. So they re-flash it and everything goes pear shaped.
Anyway, if you have root access, you can get recovery back. Download Kingroot through the Silk browser and run it. Run the root checker first to see if you do indeed have root access. If you don't, click try to root. Last I checked (about 6 months ago) Kingroot still couldn't root the 6 / 7 on 5.3.1.1 (my current OS) but they're constantly updating so it doesn't hurt to try. Also, rooting attempts rarely succeed on the first try. If it fails just try again. Give it a good six or seven tries. If it hasn't gotten root be the seventh attempt, it won't be able to root. If that's the case you;d be better off taking it back and swapping it out for another.
If, however you already have root access or your attempts to root prove successful, then you're in the clear. First, copy the latest firmware file to the Kindle and change the extension from .BIN to .ZIP. Next, go to this thread: https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950 scroll down to the bottom of post #2 and download the file called "WindowsAutoTWRP_v03.zip". Then scroll up till you see the heading "101 - Automatic installation under Windows !!!". Start with step 2 (step 1 doesn't apply since we're not upgrading from 4.5.3) and continue to follow all the steps, ignoring anything about bootloaders (again, this is for people who are upgrading back from 4.5.3) till you get to step 9. Once in TWRP, simply flash the firmware.ZIP file, then clear system and cache and reboot. If all goes well, you should have a fully restored tablet running 5.3.3.0 with stock recovery back.
Both options will get you a fixed tablet, it really just depends how much time you want to invest in tinkering with it.
Thanks for all your help so far bud.
So, I had another go at kingroot and on the 3rd attempt it showed up saying successfully root.
Downloaded the latest FW, changed the extension to .zip, copied it to the kindle.
downloaded and extracted WA TWRP. Entered cmd, typed into the console the required commands, and it came back with the below.
I can only assume that means the root didn't actually work.......
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's unusual as I've never known Kingroot to give false positives. Try using the ADB.exe that was included in the AUTOTWRP.ZIP file you downloaded instead of the one in your system path. Not sure if that will make any difference, but it couldn't hurt to try. Also, make sure you're running ADB as admin and not in normal mode since this can also effect it.
Give that a go and let me know if it works.
I have a question and hope someone here can help. I have a kindle fire HD 7 and I'm having a similar problem. I can access the tablet via adb, and I've done a few things.
1) I tried installing Amaze File explorer so I could download apks and install them from the tablet. It installed fine, but when I reboot it the tablet, it was gone.
2) I tried to do a factory reset, and although it gives me the option to do so, and reboots and says it will wipe my device, when it boots up, I can still access pictures, and even bookmarks, or the last loaded page on the silk browser, so obviously the factory reset did not work.
Also, any time I try to open the silk browser to go to any site, it just reboots the whole tablet. Actually, once I connect to the internet, and try to do anything, the Tablet reboots. If I leave it alone, it just stays on. So far, the only thing I can do is push apks to it, but once I connect to the internet, it reboots, and the new installs disappear.
Is there any way for me to root it, or force a full factory reset that actually works?
Edit - Forgot to include. I did try rooting it, but although it said successful, I don't think I have root.
carpergt said:
Hi all,
Been browsing the forums for a few years quietly in the background, found them very helpful for rooting, Xiaomi and galaxy phones I've had, however, I have just got hold of a Kindle fire HD 7 4th gen (second hand), and to put it bluntly, I think who ever owned it previously has messed around with it.
It has OS 5.1.2.1 (march release) installed on it, and says its got the update sitting there ready to do, however, when I try to install it, it goes through the install process, but it comes back on as the above firmware, It also has random adds that pop up on it.
I have tried several different methods to root the device, so I can downgrade for root access or just upgrade it to the standard stock firmware:
Click to expand...
Click to collapse
The screen is blank when I'm in fastboot mode too, but if you have the correct drivers for and in recovery mode and fastboot, the commands will work. You would need these in order to adb sideload 4.5.3 in order to root, although, maybe Kingroot would work since you are on 5.1.2. It's possible your tablet was rooted and one of the OTA files was renamed (like ota verifier) and that's why it won't install the awaiting update. There is a tutorial on this forum regarding the adb drivers, but I can't remember where at the moment.
Hello dear expert how can I solve this problem.
i have amazon fire HD 7 (4th generation) screen show this problem "hang on Fire"
Model listed SQ46CW
I just got the Gtab (UPC300-2.2) but it fails to load anything.
It does not boot and gets stuck. I do not know the boot version of it or any versions of anything because I can't access it.
When I try to put it in recovery I only get the following 2 messages:
Recovery Key Detected
Booting recovery kernel image
Thats it. i took the SD out of it and same bit when I tried to access it I seen Update and recovery files and roms folder so looks like someone tried to mod it but failed.
Is there a way I can recover it to working state to ether restore it to factory or any recommended rom...
I kind of need instructions because I never messes with this type of issue yet, as in I haven't bricked a device to this state before.
I also need to find a charger for it. looks like connecting the USB does not charge the Gtab
Id prefer recovering it to FACTORY SOFTWARE.
Im just not sure where to get the Factory software and how to go about recovering it...
So far I found out that this unit possibly has Bootloader v1.2 but recovery that was loaded onto the device was for bootloader v1.1
I do know know what the previous owner tried to do to it but failed and screwed up the device. Im just trying to fix it back to working condition.
It does not matter if its factory rom or a modded rom, as long as its stable.
Also I read up I need NVflash or something like that to recover the units bootloader ignorer to get it to work.
Any help is welcome, and I thank you all in advance.
Well I did the stuff from one of the posts here using nvflash.
Nvflash —bl bootloader.bin —getpartitiontable p.txt
Returned the SOS partition to be 11
Then tried the:
Nvflash —bl bootloader.bin —download 11 recovery.img
Finished successfully but I still have the message while trying to enter recovery:
Recovery key detected
Booting recovery kernel image
Then just sits there with the birds background.
When I try to normally boot it it does boot but I can’t open settings or anything and I constantly get this error message:
The process Android.process.acore has stopped unexpectedly. Please try again with force close button.
It constantly pops up, like once every 3-5 sec.
when i got mine it was messed up too, sounds very similar. When I got to the Viewsonic birds logo I let it sit forever and i thought it was done for, but after sitting for literally hours it actually booted up and i've been using ever since. that was about 6 months ago. just find a charger for it, i cut the end off one with the wrong voltage and attached it to an adapter with the correct voltage and amperage. It says on the back of my device "dc 12V 2A" then get it to the birds logo and set it down. Go have a day at the park or let it sit overnight, go to work for a day, out for dinner. do something so you're not sitting there looking at it every five minutes. Good luck!
Would it be possible for anyone to provide me with either the files or operational links to the files needed to recover this device?
I've scoured this forum and found nothing but dead links to NVFlash and the like. Thanks in advance!
Seems like there are a few of us still rocking this piece of hardware, me included. I"m stuck in the same dilema and the links to all the restore files haven't been preserved. Is it best to just concede that the tablet is ancient history and go purchase a new one or are the nvflash files available somewhere on the web?