I've been trying to install smoke in a bottle, and when trying to revert back to the original ROM on my G tab, I had issues of it not showing up on my computer when connceted. Now, however, I've run NVFlash...And first it got stuck in an endless boot loop, the N symbol would show up then it would turn off, and restart the process.
I then went ahead and did an NVflash format, a-la http://forum.xda-developers.com/showthread.php?t=974422
Then did a standard NVflash.
Now I get a 'magic number mismatch' with some odd garbled symbols with the occasional V, and refuses to boot at all except into APX mode. I can NVflash it into oblivion, but it still gives that error and has absolutely no indication it is on unless I use NVflash when it's in APX.
Furthermore, it seems to have no recovery mode at all, leaving me wondering if I've managed to just permanently brick this thing.
Wonderful.
If I've managed to overlook something simple, I apologize.
My site.
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
Start with code red.
You are now my personal e-hero. Thank you so much.
For some reason when I performed the "Code Red" it booted back to normal. Now when I restart it goes straight into APX mode. Any suggestions? Also, when I ran NVFLASH it didn't reformat. It is like I just turned it back on. It runs fine until I try and turn it off. Then it will only start in APX mode.
Don't give up!
Here is a link to the series of steps I used that brought my tablet back to properly functioning state (I too struggled for a while with only being able to boot with nvflash). I saw tonight where the steps worked for someone else as well.
http://forum.xda-developers.com/showpost.php?p=15432280&postcount=19
accidentally posted twice....this one can be deleted.
The problem is I can't boot into recovery. I can only boot in to APX mode. It seems all the fixes are for you to be able to boot into recovery. I have been reading for hours and I am lost.
If you read and follow djab67's procedure carefully you'll see that it will force the tablet to boot into recovery. I use the same technique in my procedure (linked below and has the added benefit of not requiring ADB). I highly recommend you try his procedure as I've looked it over very carefully and it should take care of your problem. If it doesn't please let us know and we'll find you another solution.
My procedure: http://forum.xda-developers.com/showpost.php?p=13474033&postcount=114
Been there. Don't fret. I've done so many terrible things to my G Tablet and it hasn't died on me yet. I'm pretty sure with the hardware and this community, this tablet is unbrickable.
If you can get into APX mode and your PC will recognize it when you run the NVFlash script, you are ok. If it doesn't see it when you run the script, there is still hope.
I have tried djab67's fix I don't know how many times now. Every time I click on the .bat file it tells me the file is gone. I have tried downloading it from multiple different posts with the same let down on each of them. Could my problem be that my rom is the current 4349 set up?
cryorayne,
I am going to go out on a limb here because it sounds like you are running windows on your pc (based on you choosing to use the ".bat" file instead of the ".sh" file), so hopefully another current windows user can validate my response.
It may be best to run the bat file from within the windows command window rather than trying to double click launch with in explorer (file manager, not the browser). Once at the command prompt you also need to navigate the old fashioned DOS way to your working folder location.
It is extremely important to set up all the files in a location the bat file expects to find them. Open up the bat file for editing and check any file/folder paths that are defined. You may need to change them to point to your nvflash working area.
Another thing to check is to make sure your user account on windows has administrator permissions (not just "standard user"). A while back, when I used windows more heavily, I seem to recall some cases where I had to give myself "system" level permissions to do some types of things. However, I highly doubt you need that level to run a batch file with nvflash.
Hope this helps. The steps worked for me and I have seen where at least one other person has used them successfully, so they should also work for you. Getting all the tools and files in place and set up for your computer is a key to success.
Finally, if your various downloads came from sources other than those I referenced in the write-up, then I suggest re-downloading and checking the hash sums.
Hope this helps.
Re-posted restore guide with a little additional information
Just wanted to let everyone know that I re-posted the restore steps as a thread (as opposed to a "reply" where it sits today). I was hesitant to do that before I knew the steps had worked for at least one other person. Should be a little easier to find now. Also, I added a little clarifying content to help with understanding APX Mode and nvflash use.
I am hoping the community can help with responding to requests for help. I try to read questions and respond, but don't have the time to be as quick as I would like and I know from experience how frustrating it can be to have "soft bricked" g tab.
As I learn additional information I will add content to the thread from time to time. However, I do not plan on changing the original steps (except maybe for format reasons) since they are the exact ones that worked for me.
Thread Link:
http://forum.xda-developers.com/showthread.php?t=1167944
Related
I hope I have this in the correct area.
I am running a stock unit with Market and Rothnic enhancement pack. I have not gotten an over the air update since just before Christmas. I finally decided to upgrade to the 4349 software that was posted here. I placed my recovery folder with the command line in it and the update.zip file on my sdcard (internal). Booted up with the vol + and power key and it started to upload correctly. When it tried to reboot on it's own, it hung on the "n" screen for over 45 minutes. I manually shut it down. Retried to start it and nothing. Now, if I let it go normally it gets hung up at the "n" screen and does not proceed after this. If I try to force it to go to the recovery mode it just sits there with the little messages saying a recovery key was detected.
What can I do to reload my software? It seems like it can't find the operating system? I do have an external memory card. Can that be used to boot the system from?
Any help would be appreciated. Please keep in mind that I am not Android gifted.
I just found a post from butchconner in another area that may help me. I will try to reboot from them memory card. I will let you know if it worked.
guitar geek said:
I hope I have this in the correct area.
Click to expand...
Click to collapse
You posted this in the wrong section. The Q/A forum section is here:
http://forum.xda-developers.com/forumdisplay.php?f=1101
To answer your question, you need to NVFLASH back to stock. Follow directions found here:
http://forum.xda-developers.com/showthread.php?t=861950
Thank you. I have just tried to reboot from the memory card with out success. I will try the NVFLASH but I am curious how this will work since it will not load from the memory card.
OK I have followed the text. One problem. When I connect the tablet to my PC I hear a ding. I go to my device manager and I see a NVIDA tegra 2 device. I do not have any APX listings and no exclaimantion points. When I run the nvflash program it says USB device not found Press enter to continue. I have attempted to update the drive on the Tegra 2 device but it says the drivers already installed are newer than the one I am trying to load and it stops. So what should I try to do now.
Moved to Q&A.
Eureka Success. The instructions were very clear. Unfortunately, I can't read. I completely skipped over the volume down button. That is why I did not have the APX mode. It is downloading 3588 now. Thanks again dzasta for pointing me in the right direction. And special thanks to roebeet for setting up the cheat sheet.
Glad everything worked out. NVFLASH is a great utility when stuff gets real messed up. Saved me a bunch of times and once you have it all setup, its so easy to use.
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.
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!
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?
Hey all,
I've never rooted a phone before so since I have a spare model, I figured I'd give it a go.
Hearing about this forum, I checked it out and was sent to the Sony site. I understand I needed to unlock the bootloader first, which I did and can confirm I get that alert as my phone starts about it not being safe.
Hint for future readers: don't do this in a virtual environment, I had issues doing this until I used an actual computer and not a VM (mods and folks with more experience: feel free to correct me on this or shed some light). To be clear, I have a separate host running Proxmox (Type I hypervisor) and was able to forward my USB connection to test with ADB and such. I do most things in a virtual environment to not mess up my physical computer.
This was all done last week. Well today, Monday, I decided to continue with my rooting excursion, only to run into the issue I am currently facing.
After many, many Google attempts and following whatever links in this, I finally found this link. Well, I was within a VM, downloaded the linked flashing tool, and ran the first two commands:
- adb devices
- adb reboot bootloader
After doing this, my phone turned off and I wasn't sure what to expect, so I pressed the Power button to see what would happen - nothing. So then I remembered that Friday I was having issues communicating with my mobile phone in the VM to unlock the bootloader in the first place, so I figured I'd try to move it to my physical computer....then I was stuck on a reboot cycle!
To be clear, my issue is that I am stuck on a boot loop. It prompts the error of the device being unsafe, waits 5 seconds, then displays the Sony splash screen. Rinse, wash, repeat; same thing.
I have a Sony Xperia XA1 (G3123) model.
Can anyone shed some light?
Am I screwed?
Please halp!
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
tryingToSurvive said:
I dug around a bit more, found this link but the issue is that I cannot boot into anything, at least not that I'm aware of.
Click to expand...
Click to collapse
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
keifus.rahn said:
have you tried installing a custom recovery?
this may help https://forum.xda-developers.com/xa1-ultra/development/g3221-built-sources-t3622886
Click to expand...
Click to collapse
Hey @keifus.rahn for following up.
I did find that thread after continued poking, which I am still checking now. And I eventually made a post on there just now discussing my current dilemma.
I downloaded the Flashtool but didn't understand how it worked, nor do I still yet. I tried debugging it and the issue is that the "java -version" call doesn't work within the directory's own structure. I do have java installed on my test Linux VM though.
Past that, I tried with the latest boot.img as well as the recovery.img that I found. I think that the build numbers are off, or maybe I am just not understanding where I am lacking.
You can look at the bottom of the last page for a breakdown of what I did:
https://forum.xda-developers.com/xa...21-built-sources-t3622886/page94#post80481385