Related
Everything was great.. did the update rebooted gtab worked great. Has always been stock. I shut it down and when I got home from work i hit the power button and I get the viewsonic birds then the tap n tap logo then the n just stays there and that is it has been stuck on the n for hours. I turn it off and back on and the same thing. Any advice would be appreciated.
Thank you
Have the same problem on stock Gtab.Mine gets to the birds and sticks.Tried holding power and volume up at the same time, but won't reset.Can't discharge the battery because it still goes into sleep mode after 10 min.Computer won't read when plugged into USB.Bought on Woot so a return will be a major p.i.t.a. I am new to Android devices
and was just getting enough balls to try rooting and flashing!!! FML
Yea bought mine from woot also... I liked the stock rom was also afraid to try to load a new rom. Looks like I will be sending it back
hvideo1 and sepder,
You have a choice to make. What both of you have is called a "boot loop".
Sometimes they happen because somebody does something wrong -- and
sometimes like in your case they just seem to happen.
You can return them if that is your desire -- or you can try to fix them.
Usually if one partitions the tablet and cleans it up, it can be fixed. But
that means you have to do some quick learning.
First, you have to get back to a fully stock, hopefully working version. Look
at the following procedure -- which we wrote hoping everyone would be able
to understand and use:
http://forum.xda-developers.com/showthread.php?t=861950
If you complete this procedure and the reflashed stock version works, then
we can load a program called CWM and do the partitioning and cleaning. If
the boot loops persist, then a second choice is to nvflash CWM and use it
to partition/clean up.
http://forum.xda-developers.com/showthread.php?t=865245
http://forum.xda-developers.com/showthread.php?t=1030042
The threads above give you more info on the various procedures.
Post back here what you decide to do or if you have questions.
Rev
I would try a simple data wipe first. Much easier and less invasive.
http://forum.xda-developers.com/showthread.php?t=1030915
Thanks for the replies. I don't want to send my gtab back so I'm reading both post and going to see what happens. I will reply back (hopefully with the gtab) Thanks again
I'm in the same boat as hvideo1 and sepde
Already tried the nvFlash first method mentioned by butchconner but can't get past the "Booting recovery kernel image" message, just sits there on the viewsonic splash.
Going to read and try the "CWM and do the partitioning and cleaning" next.
Appreciate everyone's help!
lrgche,
To NVFlash, you have to press Power/Volume - to activate APX. It will usually come
up with the white screen and then turn black.
"Booting recovery kernel image" indicates you may be pressing Power/Volume + , which
starts up Recovery -- a different process.
Go back through the procedure again and double check that everything is right and
it should work.
Rev
K J Rad said:
I would try a simple data wipe first. Much easier and less invasive.
http://forum.xda-developers.com/showthread.php?t=1030915
Click to expand...
Click to collapse
This worked for me. Thank you back up and working. the only reason I didn't go the other way was because I didn't understand alot of reading and just confused me (not hard to do)
Lol. Thanks to both of u
hvideo1 said:
This worked for me. Thank you back up and working. the only reason I didn't go the other way was because I didn't understand alot of reading and just confused me (not hard to do)
Lol. Thanks to both of u
Click to expand...
Click to collapse
Glad to help. You should learn that other procedure if you plan on doing any serious modding in the future though. It may become necessary next time.
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!
I recently bricked my tablet after having it rooted for a very long time...a Samsung-issued update apparently screwed with something crucial.
Anyway, I tried the nvflash recovery methods as mentioned in this thread: http://forum.xda-developers.com/showthread.php?t=1130574
However, it seems that I have what they called a "locked" tablet. I get the 0x4 error he mentions and absolutely nothing happens when I send the command in nvflash.
Is there any update on this recovery method with locked tabs? I tried seeking paid services where they hook up devices to a JTAG and whatnot, but I've only seen that for the original Galaxy and not the 10.1--if you have any information about that route, that would help too.
Thanks!
you can try flashing a old rom if you can thats what i did and it worked for me
samwest39 said:
you can try flashing a old rom if you can thats what i did and it worked for me
Click to expand...
Click to collapse
The thing is I can't flash to different ROMs or even get the Tablet to boot up into download mode...
go to recovery mode
I can't get into recovery mode too. All of the partitions are screwed, and the only way of reviving this device is by flash through the NVidia Recovery Console (nvflash). The thing is, my device is one of the lucky ones that are locked..Thus, it requires a special key to unlock it before I can do anything in nvflash.
I have no idea if this would work, but you could try it ...
A few months ago I was flashing a ROM on a friends phone and something went wrong, the phone wouldn't even boot up any more, the screen stayed blank all the time, no matter which combination of buttons I pressed of how long I held them down for. ODIN didn't recognise it being connected to the PC etc... nothing worked.
Then I tried hooking the phone to the PC again and tried to do something with adb. And somehow, the phone was connected on adb. Tried an adb restart-to-download command and after a minute or two, the phone booted up and I could flash through ODIN again.
I have no idea why it worked, but it did ... lucky me .
So while I doubt it will work, it might still be worth a try. And if adb connects in any way you could maybe figure what was wrong and somehow fix it?
I also heard about some phones being locked out in a similar way and a procedure in the lines of "take the battery out, hold down 3 buttons, slide the battery in WHILE STILL HOLDING the buttons" worked, maybe there's something similarly "hidden" on the tab?
I hope you find your answer!
a while back (about 3 weeks) i bought me a galaxy player us version 4.0. great player.
love it honestly.
but of course i wasnt satisfied.
so i rooted.
that was two weeks ago.
and tonight. i found myself trying to flash a custom kernel. called
"steves kernel" or something like that. and to my surprise using odin, it worked. rebooted. looked around. and the only thing different was the boot logo. booted to home screen. and worked naturally. wanted to boot into te CWM recovery that came with the custom rom to backup. "obviously was too late". and i backed up and rebooted. and of course. it was stuck in a bootloop. witht he fireworks looking thing. i looked for hours on end. for a stock rom of the 4.0 US version. i found what claimed to be 4.0 but either didnt match the md5 or were intl versions or WTF EVER.
(pretty damn steamed over here)
i unplugged my galaxy from my computer. and it instantly shut off. and now what seems to be a (from my experience with a psp; correct me otherwise) in a full brick. because it wont power on. it wont flash. it wont be recognized in windows. or any OS for that matter. nothing. tried battery pulll. nothing. someone.
please.
anyone.
help.
(also think i could get my money back from bestbuy if all else fails??)
When posting things like this, post EXACT links to what you actually flashed.
Flashing something without bootloaders in Odin shouldn't have done this.
try this - forum.xda-developers.com/showthread.php?t=1386669
the unbrickable recovery should be able to get your device back into download mode. when I bricked my player to the point that it wouldn't turn on it was able to save it.
I think it works under windows, download the unbrickable resurrector and the
Samsung bootloaders from the link. you need to have Java runtime installed for it to work too.
open the unbrickable resurrector ".jar" file, and select "galxay player" from the dropdown in the bottom left. plug your player in ane above the text box it should say "device detected." or something to that effect.
now hold the "volume down" button on your player and hit the download mode button in the program. keep holding the download mode button until your device comes on in download mode. if after 5-10 seconds the screen is still black, unplug your player, restart the program and try it again. it took me 4-5 tries sometimes but it always managed to bring it back.
when you do get it into download mode, fire up Odin and flash the player bootloader from the "galaxyplayer-bootloader.zip". make sure to check the flash bootloader box on the left side or Odin. if just the bootloader was screwed up, your device might boot now.. if it gets stuck at the Samsung logo you need to put it back in download mode (power + volume down) and reflash a good rom or recovery rom (not just a kernel). if it doesn't want to go back into download mode you can use the unbrickable process again.
good luck.
i am going to try this method. do you think it will help with my 4.0 though? the tut is for the 5.0.....
this isnt the EXACT link. however this is the exact software i used. (odin was 1.83 i do believe)
http // www anythingbutipod com/forum/ showthread php?t=66820
(fill all spaces with .)
That's why in the notes section for each of Steve's kernels it says not to use CWM
Try following logo20heli's work on it here http://forum.xda-developers.com/showpost.php?p=21302504&postcount=41 since he did the same thing and got stuck in a boot loop
woer said:
That's why in the notes section for each of Steve's kernels it says not to use CWM
Try following logo20heli's work on it here http://forum.xda-developers.com/showpost.php?p=21302504&postcount=41 since he did the same thing and got stuck in a boot loop
Click to expand...
Click to collapse
i looked there. however, i couldnt find any proper download links for anything.
macdomerocker said:
i am going to try this method. do you think it will help with my 4.0 though? the tut is for the 5.0.....
this isnt the EXACT link. however this is the exact software i used. (odin was 1.83 i do believe)
http // www anythingbutipod com/forum/ showthread php?t=66820
(fill all spaces with .)
Click to expand...
Click to collapse
I'm not sure if it'll work with the 4, I doubt trying it would hurt anything though.. just wouldn't work.
exodus454 said:
I'm not sure if it'll work with the 4, I doubt trying it would hurt anything though.. just wouldn't work.
Click to expand...
Click to collapse
well if anyone can help me out. this would be tremendous. i will post the results to that in a wee bit. gotta try it first
Read my thread in development.
Hyperrunner said:
Read my thread in development.
Click to expand...
Click to collapse
yes. however if you have read my problem it is FULLY BRICKED. so i have NO clue on how to get it unbricked. meaning that i couldnt get it to go into download mode if you were here in person. now if you know a way to unbrick me. please say so. THEN i can follow your tutorial.
lol just got back from bestbuy. they swapped me out because i bought it within the last 30 days.. so im good
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Hi
Thanks for writing to us at XDA Assist. Please standby while we have your thread/question moved to the appropriate sub-forum for your device.
For future reference you can find your device sub-forum here (bookmark/subscribe this):
Asus Eee Pad Transformer Prime
Within that section you will find a dedicated q&a sub-forum (this is where your thread is going to be moved to):
Eee Pad Transformer Prime Q&A, Help & Troubleshooting
Good luck!
Bump, could really use some help...
GiordyWarner said:
Bump, could really use some help...
Click to expand...
Click to collapse
There is only hope, if you can manage to get into bootloader screen by pressing power + vol down.
APX mode would only help you, if you had pulled your nvflash files.
GiordyWarner said:
Hi,
I recently unlocked and rooted my device. Asus Transformer Prime (TF201).
I tried to boot it into recovery, wouldn't boot the rom, kept freezing, hard reset it. Then it booted into the official android version, I was running 4.1.1, build # 10.4.2.18
Then I went into recovery, and I was like "oh yeah, I remember reading that it has to be a fresh install, that way there's no incompatibility". So I decided to press the down button until I got to erase everything in the menu, I did it. Erased it, device reset itself, and now it's stuck in the main loading screen, where it says Asus, this device is unlocked in the top left, and the nvidia symbol in the bottom right. The device wont boot into anything, not even recovery settings. Is there a fix? Or did I just make my tablet a paper weight?
I tried searching the web, I found all these articles, and frankly I'm very overwhelmed, and didn't know what to do or which one to read. I just got the tablet as a Valentines Day gift from my wife, and I would have to have ruined it. Please help me.
EDIT: I got my device to appear as "APX" in devices and printers, it's an unknown device. But I'm still lost.
Click to expand...
Click to collapse
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
gsanglan said:
Hi, u can follow the steps listed in this blog. I just installed CM11 using the same steps over the weekend. U need to perform a factory reset and wipe the cache after u installed the ROM using the CWM recovery. If not, it will be struck in the boot screen with the arrow going in circle. Below is the blog address:
d3-media.blogspot.sg/2014/08/upgrading-asus-prime-tf201-to-android.html
Good luck flashing!!
Click to expand...
Click to collapse
This has nothing to do with what he is asking.
flumpster said:
This has nothing to do with what he is asking.
Click to expand...
Click to collapse
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Jimboy00 said:
Hi,
I've same problem!
I tried to flash to android 5.0. I tried many things via twrp and now, thats it:
My TF201 stucks also at bootscreen and the recovery menu (Power on + Vol.Down) won't work. That means I'm not able to get in fastboot mode or something like that. The only possiblity to switch the device off at the moment is to unplug the battery
I've searched for a solution in many boards, but unitl now i haven't found anything.
At the moment it seems that the only possibility we have, is to change mainboard, or to try to connect via an external programmer (for flashing the memory), but that would be for sure not the easiest way, or it could be also nearly impossible.
So at the moment I'm praying to god, that someone will have another solution and will post it here, because otherwise I can cast away my loved transformer prime :crying:
Looking forward to hear any news about that topic :fingers-crossed:
Click to expand...
Click to collapse
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
flumpster said:
You say this "My TF201 stucks also at bootscreen and the recovery menu". Does that mean you can still access recovery (TWRP)?
Click to expand...
Click to collapse
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Jimboy00 said:
No, thats the problem, since yesterday it is not possible, because I tried to flash back to an older version of TWRP, and since that I can't access RCK and then I tried to wipe data, and since that, I even can't access to recovery console (Power on + Vol.Down).
That means I can't do anything at the moment, I see only the asus boot logo and that's it.
So I have no idea to communicate with the tablet at the moment.
The problem was, that I was not really careful, because my opinion was, that it's impossible to brick the whole tablet, but now it's gone!
Is that the end of the story, or do you know therefore a solution?
Regards,
Jim
Click to expand...
Click to collapse
Unfortunately unless you have nvflash backups then you will have to get the board replaced. Forget contacting Asus as they would charge you more than the tablet is worth. Try and find one with a smashed screen on ebay etc cheap that still works that you can swap the board out from.
lemicp said:
Seems that you are in APX mode. Hope you have your blob + nvflash and wheelie to restore the bricksafe.img. (It saved my TF when i was in your position)
Good luck
Click to expand...
Click to collapse
Thanks for your feedback,
So I don't have these files :crying:
I found also another thread with same story, and it seems that I can search for a new MoBo....
http://forum.xda-developers.com/showthread.php?t=2143942
...or buy a new tablet, maybe the better solution...