I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
Related
I have yet to find an answer to this while searching for the past day, so I'm going to ask about it here.
My LG Optimus V's (just got it a few days ago as a birthday present) screen seems to be permanently blank... In case someone asks... yes, it is activated.
What Happened:
I rooted the phone using Gingerbreak 1.2, installed rom manager/clockwork recovery mod, then attempted to backup my phone in case something went wrong. However, when I started the backup, I noticed that the screen was completely blank. I was kinda freaking out, so I just took a shower while it did it's thing. When I came back, it was done creating the backup and it showed up in Rom Manager. After toying with some of the things I can do with it rooted (I only rooted it to see how much of a difference it would make without changing the kernel), I decided to recover that backup. When my phone restarted to recover the backup, the screen was blank once again. After waiting for over an hour, I concluded that it must have finished (since my HTC Hero would finish restoring and never reboot until I tell it to) and took out the battery. Afterwards, it would show the LG splash screen... then the blank screen.
What I Did:
I was thinking about the android screencast java application a few hours after my problem first developed. I plugged my phone into my computer, got adb working, and android screencast showed me that my phone was actually getting stuck at the clockwork recovery mod screen. I tried many things... I installed a CM7 rom, flashed 3 different recoveries, flashed an overclocked stock rom, etc. Eventually, I flashed the stock rom (no changes whatsoever) and stock recovery. Now I can hear my phone, but cannot see it. However, I should note that while using CM7 the same thing happened. The only difference being that I could use android screencast to see the screen (the phone was actually working) with CM7. Now with the stock rom, adb is disabled and I cannot see the screen or do... anything.
What I Think I Should Do:
I'm thinking about calling Virgin Mobile and telling them that my screen is defected. If they see the issue they'll probably think that it's a hardware issue (for all I know, it could be) and they'll probably give me a replacement. However, if anyone as had the same problem and fixed it, I would love to know.
I would love you hear your opinion on this and, if possible, a fix. Thanks in advance!
(JIC, if I posed in the wrong section, I'm sorry...)
you poor souls reporting the symptoms of getting the newer screen hardware from the optimus s in your v's don't number in the double digits yet, but it's getting closer.
I posted a fix on AndroidCentral, see it:
here
good luck! the fix has worked for everyone I pointed to it so far.
btw, the screencast idea is excellent!
crud. stock recovery, you may be SOL.
you'll probably have to boot into custom recovery to use screencast or adb now.
use the unplug phone -> pull&replace battery -> hold home+volume down -> keep holding, press and hold power until lg screen goes blank to enter recovery. maybe adb will work in stock recovery, I dunno.
Thank you very much for the reply!
Yeah, you're right, I'm probably SOL... I still have one option though! Theoretically, I should be able to turn on ADB without being able to see my screen. I know how to access the settings without seeing it, but navigating myself to the "Applications", "Development", "USB Debugging" may be a little hard. I will attempt to do so. I will report my progress in a bit.
However, if you (or somebody else) could provide screenshots of a step-by-step process to turn on USB Debugging in the stock rom (since it's kinda hard to do remember where everything is and screenshots of different phones is kinda different) then I would appreciate it VERY much!
I shall update this in an hour or so.
UPDATE (9/2/11 - 9 PM):
I'm going to take a break for now. Good thing I give everyone my Google Voice number, I doubt anyone will notice a change. I'm going to flash a stock rom onto my HTC Hero so I can figure out where things are on the LG Optimus V (Same screen size) in an hour or so. I'll update my progress in like 2 hours.
UPDATE (9/3/11 - 8:10 AM):
I have been unable to turn on USB Debugging and it seems to be because I don't know where the confirmation after turning it on is located. However, I should note that when I boot into (I think) recovery, "adb devices" states that the device is attached but offline. If there is a way to make it "online" from stock recovery then I would love to know. For now, I will try everything I can.
UPDATE (9/3/11 - 8:22 AM):
Ok. I plugged my phone into the back of my computer and now when I do "adb devices" it detects the device in recovery mode. However, when I try "adb shell" it says "- exec '/system/bin/sh' failed: No such file or directory <2> -". I'll try some more stuff, but does anyone have any idea of what I can do? Android Screencast doesn't work either, so that's not an option.
UPDATE (9/3/11 - 9:42 AM):
Crap... now it's indefinatly booting into recovery... I had something like this happen before, I'll report my status in an hour or so...
UPDATE (9/3/11 - 12:36 PM):
My friend finally got my phone booting out of recovery again! Now all I have to do is get "USB Debugging" on and it SHOULD work!
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
glad you got back into recovery again, not too sure how to help at this stage though, since I can't find a way to get into the bootloader with a power-on key combo. just emergency mode (useless to the V since the firmware from LG is missing a file) and safe mode. boo.
there is a youtube video for enabling usb debugging on the v, maybe it'll help you find the right spots to press.
http://www.youtube.com/watch?v=nHal0hPNS6s
edit: you can also try to reboot into the bootloader with adb, even though it's missing the shell... it's worth a try, and if it works you can flash xionia recovery with fastboot and things would be a lot easier from that point.
Code:
adb reboot bootloader
if that works but you need more help, a battery pull is the only way to power off with the bootloader except "fastboot reboot" will try to boot your rom.
Awesome, thanks for the replies! I'm going to try your suggestions now. I'll let you know how things work out in a few hours. I would have replied earlier, but to my satisfaction there was a surprise party planned for me, lol. I will defiantly try these out now.
Once again, thank you very much. I honestly did not expect a reply for something that happens to such few people.
bigsupersquid said:
I <think> there's a key combination to power up into the bootloader. if you can find it with searching here and android central.
I haven't been able to track that down today. If you can get into the bootloader, you can fix it. Search for asadullah's fastboot root instructions here if you find a way to get into the blue screen (the bootloader, which fastboot talks to.)
otherwise, I'll be done taking the kids to the (ugh) pool in a few hours and I'll search more.
try pulling your battery for a few minutes and see if the reboot cyle stops that way, at least it might get into recovery or the rom.
Click to expand...
Click to collapse
I'm honestly not sure what my friend did, lol. She was just messing with it while it was, apparently, in recovery and it ended up rebooting and loading the rom. I, honestly, don't want to risk getting stuck in recovery anymore since taking out the battery for an hour didn't do anything... If I'm unable to get adb on using what I know from that video then I'll try booting into the bootloader. Like I said before, I'll report my status in a few hours. I really appreciate your help up to now!
EXTREMELY HAPPY UPDATE!!! (9/4/11 - 1:22 AM)
I was able to turn on ADB! I used what I learned from that video and how turning on ADB works on my HTC Hero to get it working and it's FINALLY ON! Now I can attempt to flash the recovery, kernel, and everything else in order to get it working! Thank you VERY much! I will let you know how everything turn out
Another Wonderful Update! (9/4/11 - 2:03 AM)
I have flashed the recovery.img (the Xionia CWMA one) and can see my screen in recovery! I haven't seen anything on my screen besides the LG splash screen so I'm overwhelmed with joy! I'm flashing a new ROM and the other stuff now!
Final Update! (9/4/11 - 2:09 AM)
2:05 AM - I see the rom's boot screen!
2:06 AM - I see the CM7 Mod boot screen!
2:08 AM - I see the UI on my screen and everything seems to be working! Thank you VERY much!
Quick question though... If I want to install a new ROM, do I need to flash the xionia anykernel one directly afterwards?
ah, excellent! glad it's working now.
you're the most persistent (and maybe technically apt) person I've helped with this so far.
I still think that using screencast was the best new idea I've seen yet.
yes, you'll need to flash the xionia kernel after flashing any rom or rom update.
roms come with their own kernel in the boot.img, and none of them currently out for the v have the video drivers from the newer sprint kernels.
right now, xionia kernel is the only thing that works.
and, you'll need to flash the key swap after changing roms, as well, but at least forgetting to do that won't take out your display.
now that you've got xionia recovery on your phone, it should be a lot easier next time.
Thank you for both the help and the compliment!
I don't like giving up when it's something I know I can do. I figured that if I was able to mount my SD card without being able to see the screen, I should be able to turn on USB Debugging as well. About the Android Screencast... I didn't actually think about it until it until I plugged in my phone while the screen was blank, ran "adb devices", and saw that my device was detected within recovery. I figured that I might as well give it a shot... and it worked.
Alright, that's what I figured. Hopefully someone realizes what's happening with refurbished Optimus V smartphones and ports the newer sprint kernels to the Optimus V. I feel like I got ripped-off though... I bought my phone "new" and got a refurbished one. I can't really do anything though, we're not technically supposed to be rooting our Virgin Mobile phones anyways, lol. I'll be sure to do that everytime now though. For now, I think I'm good with the Bumblebee rom.
Once again, thank you VERY much for your help! I know I would not have been able to fix my phone without your help.
EDIT:
Oh yeah, btw, if the Optimus V ever gets stuck in stock recovery, press the "back" button then "home" button to boot into the rom. Not sure why it works (I was never able to see the screen), but it worked.
There is a key combo!
First time caller long time listener... I bricked my own Optmus V with a bogus ROM. To boot into recovery without adb press (Home)+(Volume Down)+(Power) Now rocking CM7!
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh:
I have a TF201 that I don't know the history on. It turns on to gears and a red triangle exclamation. The weird thing is if I tilt it, half of the screen shows android start and setup.
I figured I could find the stock rom and flash it using MicroSD, however looking everywhere I can't find a true stock rom. I can find stock roms that are modified to unlocked devices, but not true stock.
When I try to do a wipe, it says 9.4.2.7 at the top I noticed. I don't know if that helps.
Suggestions?
EDIT:
Good source for firmware
http://forum.xda-developers.com/showthread.php?t=1429873
So I found them on ASUS's site. I had no idea they were under Android on there.
However, I can't get adb to find a device on the computer because I only have two icons holding volume and power (Wipe Data, Android).
If I put a SDcard in the tablet like on a TF300T and go into RCK, it doesn't work. Android goes belly up with red triangle. Is it the name i'm using? I tried update.zip, the stock firmware name, and EP201_768_SDUPDATE like I use on the TF300T.
Also, when it's hooked up and I type fastboot device, all I get is waiting for device.
I don't know if this is because it needs to be in a debug USB mode, but I can't get there to check. It does recognize the tab on the computer when I plug it in though.
Ok, so I fixed it.
I downloaded US_epaduser9_4_2_7Updatelauncher.zip
I then put it on a MicroSD card formatted Fat32 and renamed it EP201_SDUPDATE
Then I put it in the tablet and held volume down and power until it prompted to go into RCK and no more dead android, it took and loaded.
EDIT:
DIDN'T WORK (
It loaded like it was going to work, but I am back to the gears and the red triangle.
FUUUUU.JPG
haha, I feel like I am in here by myself. However, I want to document all of this in case somebody else runs into the problem I ran into and they're a rook too.
I fixed it. I wasn't sure what ROM was originally on it and when holding volume and power I noticed the 9.4.2.7 so I assumed that was it. However, I tried that ROM and it seemed like it was going to work but kicked the gear and triangle.
I then figured what the heck and tried the newest rom I could find. The 10.4.2.18?? I think it was. Whatever is the newest on the link I put in the first post.
It ran, and rebooted and Wahla, worked.
It's important to note my directions of FAT32 and the EP201_SDUPDATE as it took me a while to realize those had to be in place properly for the MicroSD card update to work.
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
I have exactly the same problem please someone help us :angel:
virus4o said:
I have exactly the same problem please someone help us :angel:
Click to expand...
Click to collapse
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Same problem while flashing CM
Aduniel said:
I have the same problem too. Only apx.
Please, Anyone knows any solution for this issue?
Click to expand...
Click to collapse
My tf is in the same state. Got there when trying to install CM's nightly build.
Bricked TF201 - Stuck in bootscreen
I have the exact same problem. :crying:
Please, I know that there are many brilliant minds in this forum, help us n00bs get out of this mess and lead us into the light. Oh, and bump this thread
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
spudthedestroyer said:
I hate to be the bearer of bad news, but I hate hit and run thread posters so I will provide an update.
I am afraid that my tablet was bricked. No way back from that state after reading the entire internet. I have purchased a replacement motherboard, popped open the case and replaced this. After replacing the motherboard, I now have a working tablet. I wish someone would have documented the NVFlash process requirements previously, but that's the risk of following guides on android sites I guess.
So to summarise the initial post, if you are in that state, at current and likely forever, you are hardbricked and the tablet can not be recovered in that states without a previous backup. The only way for it to be repaired is to send it to Asus who have a database of firmware, etc. and will charge you for repairs (~200€), or to go on ebay and purchase this motherboard:
0K0AMBA000
This will cost you ~80€ + shipping, and you must be comfortable working with electronics. Its mostly very clear when you pop off the case, everything has its place. You will need some plastic case pries and a small screw driver.
Click to expand...
Click to collapse
This sucks, I did the same exact thing last night factory resetting it to give it to my brother. I still don't understand what exactly I did wrong as I've factory reset this thing before. I had CM on it before but have been using the stock rooted ROM & recovery for the past 6+ months.
bricked?
I've been scouring that internet and haven't been able to find a case exactly like mine, but most are similar. From what I can remember (it's been months since I initially 'bricked' it), I was upgrading a cm nightly and did the data/cache/dalvik wipe like the instructions said and I became stuck in a bootloop after leaving recovery. When I tried volume-down and power, I was left with the original 3 options and after some reboots and shutdowns I ended up doing a factory data wipe. From there, when I rebooted the phone I was left with just 'Wipe Data' and 'Fastboot.' Wipe data does nothing more and when I choose fastboot I am left a message 'Starting fastboot usb download protocol' which never changes.
I have tried to push TWRP onto the device but I can't get into recovery (unless I'm doing something wrong of course). Sorry if I missed a duplicate of my post somewhere on here, but if so can someone at least point me in the right direction? Thanks!
i.imgur.com/LEHNREw.jpg
try another ROM
This has worked for me everytime, possibly due to dud bootloader install or some other thing: so long as I was able to recover to CWM with pwr+vol down, I installed virtuous prime rom. This rom was on sdcard already, not sure if you can get from adb if machine in this state. Anyhow, this virtuous prime rom replaced the booting sequence, restored OS and machine worked again.
Asus TF201 stuck on Asus Logo
My Asus Tablet was slow while browsing, and it had JB 4.1.1 with stock rom, so i tried to unlock the device, which was successful and was planning to push the CM11 Kit Kat. I booted in to recovery mode as i could see the 4 icons and then tried to do wipe data/factory reset and then it rebooted and got stuck on the asus logo and at the right bottow with the message powered by NVIDIA Tegra. I tried all the options to get into recovery and also downloaded drivers on my laptop for APX, but no luck at all. What are my options or if any one was successful to get it fixed. Appreciate any help here from smart guys out there. Thanks
spudthedestroyer said:
I am pretty sure I know the answer but want to make sure its true as its a costly issue: I did some searching and found a lot of threads with different options over the last few years, so just want to confirm; I have:
Asus Transformer Prime TF201, unlocked with latest ICS official (WW) installed via SD Card
I was intending on giving the tablet away to a family member, so decided to factory reset the device. I went to the PWR+VOL Down menu, and selected wipe which I read was the way to perform a factor reset. After a long time of this process, the tablet powered off (was plugged into mains with full batteries). I powered on by pressing PWR button some time later. Now the tablet just boots onto the screen that states "The device is UnLocked" in the top left, ASUS in the middle (and some lies about perfection), and the bottom right "Powered by Nvidia TEGRA".
If I power on:
1. PWR + VOL Down, nothing happens, it boots to the same screen, no menu
2. PWS + VOL UP, the screen is black, the tablet vibrates and if i have it plugged into a PC it detects it in APX mode.
I've tried a full power cycle, and read about the nvflash tool. I unfortunately have no nvflash backups, I'm not sure that tool was around when I unlocked the tablet, and as i'd not been flashing any custom roms (although I had intended) I'd not seen that tool before.
As I understand the state of affairs is:
1. Somehow the bootloader is jiggered, i guess the wipe didn't work right
2. APX is useless if you don't have some backups created with a tool
3. The only current solution is to send it to ASUS and pay almost exactly the same price as a new tablet costs
Is there any other options I can do with an unlocked tablet and only access to APX?
Any likelihood that there is anything that can be done with nvflash in the future without needing a custom backup that is unique per tablet?
Click to expand...
Click to collapse
I had messrd up my tf101 with cm nightly to. I did manage to get it working again with adb tool of sorts. When im home i will tr y to find it on my comp. Th
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?