Hi,
I've been doing reading, trying to understand options for recovery and backup.
Are there two different recovery mechanisms/modes: APX and non-APX?
http://forum.xda-developers.com/showthread.php?t=827384#9062668
http://wiki.tegratab.com/index.php/ROMs
and one of these you hold VOL+ vs. VOL-?
And with one of these you use nvflash?
Also, how to create the files needed for these?
Thanks,
Jim
jimcpl said:
Hi,
I've been doing reading, trying to understand options for recovery and backup.
Are there two different recovery mechanisms/modes: APX and non-APX?
http://forum.xda-developers.com/showthread.php?t=827384#9062668
http://wiki.tegratab.com/index.php/ROMs
and one of these you hold VOL+ vs. VOL-?
And with one of these you use nvflash?
Also, how to create the files needed for these?
Thanks,
Jim
Click to expand...
Click to collapse
APX mode is the failsafe mechanism. If all else goes wrong, you can put your G Tablet in APX mode and use the nvflash tool to flash a new image to your tablet. You hold down VOL- when booting to get into APX mode.
Clockwork Mod Recovery is a much simpler tool to use. Once installed, you just press and hold VOL+ while booting, and you get a nice, easy text menu you can scroll through, and you can flash new ROMs from your internal SD card storage (or an external SD card too). You can also backup and restore your whole system as an image stored into the internal SD card, which is absolutely critical if you are trying new ROMs out, so you can restore in case something goes wrong. You can also fix partition issues that sometimes crop up, and clear cache and the Dalvik cache using Clockwork Mod, which can fix many issues when installing new ROMs.
To install Clockwork Mod, see the HOWTO thread here: http://forum.xda-developers.com/showthread.php?t=865245
Hi,
What kind of got me started on this was post #53 on this thread:
http://forum.xda-developers.com/showthread.php?t=844088&page=6
Now, I just got my Gtab this weekend, and I haven't backed it up completely yet, so I was figuring out how to do it. Everybody seems to recommend CWM, but then I saw that thread/post, and went "oh, oh. If I do that, then there'd be no way to get completely back to stock and get OTA updates (because CWM replaces the "stock recovery").
I did see the reply to that, but haven't found the reference mentioned in the reply.
The other thing is that I kept seeing references to the Gtab's "stock recovery", which seemed to be different from the CWM and APX recovery methods, and which I really haven't been able to find an explanation of.
Also, the ways to initiate the recoveries seemed to be different:
Power+VOL-
Power+VOL+
Power+VOL+ AND VOL-, then VOL+ only
Thus, my (still) confusion ...
Jim
jimcpl said:
Hi,
What kind of got me started on this was post #53 on this thread:
http://forum.xda-developers.com/showthread.php?t=844088&page=6
Now, I just got my Gtab this weekend, and I haven't backed it up completely yet, so I was figuring out how to do it. Everybody seems to recommend CWM, but then I saw that thread/post, and went "oh, oh. If I do that, then there'd be no way to get completely back to stock and get OTA updates (because CWM replaces the "stock recovery").
I did see the reply to that, but haven't found the reference mentioned in the reply.
The other thing is that I kept seeing references to the Gtab's "stock recovery", which seemed to be different from the CWM and APX recovery methods, and which I really haven't been able to find an explanation of.
Also, the ways to initiate the recoveries seemed to be different:
Power+VOL-
Power+VOL+
Power+VOL+ AND VOL-, then VOL+ only
Thus, my (still) confusion ...
Jim
Click to expand...
Click to collapse
You definitely can go back to full stock even if you've installed Clockwork Mod, I know a fair number of people have done it. See this thread for one method: http://forum.xda-developers.com/showthread.php?t=861950
However, the *only* reason you'd want to do that is if you are planning on returning the tablet to the store, or if you are developing ROMs like Roebeet. There is no other good reason.
The stock recovery image is extremely minimal. It does exactly one thing, as far as I can tell - when you boot up holding down VOL+, it loads update.zip from the SDCard directory and flashes it. But to the best of my knowledge, there is no recovery mode that will make backups, restore backups, and let you pick ROMs to flash. Thus "stock recovery" just refers to the stock, out-of-the-box image on the recovery partition that lets you flash an update.zip file, rather than to any genuine recovery functionality.
As far as everything we've seen tells us, the stock TNT software will always be worse than the custom ROMs you can download here, and there's no functional reason you'd ever want the stock recovery + stock TNT over a rooted, fixed TNT build like TNT Lite. Or something better like Vegan ROM.
Regarding APX mode, that's not a recovery image that you can boot into like Clockwork Mod. It's a special low-level firmware programming mode in the device that you access by pressing VOL- at boot.
The third thing you mentioned, pressing Power+VOL+ AND VOL-, then VOL+ only, I've never heard of. That sounds like somebody might have been mistaken about something to me. Or it's some really cool function I've just never heard of. To the best of my knowledge, booting into recovery mode is always accomplished by VOL+ while powering on, and booting into APX mode is always accomplished by VOL- while powering on, and that's all there is for special modes.
Hope this helps!
rcgabriel,
I saw a number of references to VOL+/VOL- then VOL+, e.g.:
http://forum.xda-developers.com/showthread.php?t=824804&highlight=flash&page=99
post #990. That calls it "APX mode":
"The first step would be to get into APX recovery mode:", which is what has been confusing me.
Is it just VOL-, or VOL+/VOL- then VOL+?
Jim
Power plus volume up = recovery mode
Power plus volume down = APX mode
APX mode is where you would use a tool like nvflash to backup your device and flash it, but you have to be very careful with that tool. Make one mistake and your partition structure is completely borked. It's fixable, but you have to know what you're doing.
Is there a program that will save all my apps and settings so I can update to a new rom and then load everything back on the new rom?
roebeet said:
Power plus volume up = recovery mode
Power plus volume down = APX mode
APX mode is where you would use a tool like nvflash to backup your device and flash it, but you have to be very careful with that tool. Make one mistake and your partition structure is completely borked. It's fixable, but you have to know what you're doing.
Click to expand...
Click to collapse
roebeet,
My understanding is that when using CWM, you do the power+volume up to get to CWM. Correct?
So, when CWM is installed, it replaces the "stock" "recovery mode". Correct?
Finally, when CWM is installed, is the APX mode (power+volume down) still available? And that's the "ultimate" recover when things go really bad?
Thanks,
Jim
Yes, yes, yes, and yes.
delete post wrong thread
You also need titanium backup to complete your backup arsenal
It will allow you to restore all your appear and their setting between rom version if needed
Sent from my GTablet-TnT-Lite using Tapatalk
Moved to general.
Related
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
jesusgi said:
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
Click to expand...
Click to collapse
nvflash to the version included in the tntlite post there is an apk file link there
Do you mean 3588 stock?
jesusgi said:
Do you mean 3588 stock?
Click to expand...
Click to collapse
yes check the first post in the lite thread. It is linked as APK 3588
I downloaded it, but I am not sure how to use it with nvflash as compared to the restore which was relatively simple using the included bat file. Am I missing something or am I just a hopeless Noob?
jesusgi said:
I stupidly installed TNT Lite 5.0 before reading the instructions. My gtab locked at white screen. I panicked. Did a full restore using Nvflash. That put g-tab to 2638. But when I shut off power I can get nothing but a black screen when powering on. The only way to get the tablet to function again is to flash another full restore, and then same problem occurs when I shut down. I cant update because the tablet screen goes black when attempting reboot. I've been reading posts here in the developers forum all day and I haven't come closer to solving my problem, so I need help from someone smarter please.
Click to expand...
Click to collapse
Hmm?.. Seems there are a lot of users trying to prove the GTAB is in fact Brickable..*lol*
It is NOT!
Go here:
http://forum.xda-developers.com/showthread.php?t=861950
Yes I feel dumb about it. I did read that thread before posting. I did the restore. I can get the gtab to boot up and it is usable.......until I power down, then the only way to use it again is to reflash the restore again. I mean its usable. Not really bricked, really, but I am frustrated because it seems like I am missing the solution.
I used the nvflash from http://forum.xda-developers.com/showthread.php?t=861950 to prep my gtab for 5.0. Once it flashed and booted to the OS, I had it join wireless, then it prompted to start the update to 3588 immediately. Have you tried this?
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
jesusgi said:
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
Click to expand...
Click to collapse
Been there.......months later the tablet is still there. I can not power it off or reboot it. I bought another tablet and use "the unbootable" one at home where it sits in a dock until needed.
I have tried every nvflash recommendation out there...
There are about 4 or 5 tablets like this. Most have either been returned/swapped out or set aside and no longer used (from my reading of others with the same problem).
I can get it to boot by formatting partition 2 so if it ever goes off or I need to "update" it I turn it off.....connect it and nvflash it...holding volume + if I need to get to recovery. If not...once nvflash sends the bootloader over and formats partition 2, the device boots.
Something on mine is preventing the bootloader from booting.....the nvflash sending it over executes it and the tablet runs......
redundant - double posted
jesusgi said:
Yes it downloads the update but to complete the update, it must reboot. When it goes to reboot then the screen goes black and then nothing The only way I can get it to work again is to nvflash it to the complete restore I have been going round in circles with it for hours and hours
Click to expand...
Click to collapse
I got the same problem. I can only power my gtab by doing nvflash, and if i reboot, it only goes into apx mode.
Ouch. That has stopped me in my tracks. It's really bad news.
"Something on mine is preventing the bootloader from booting.....the nvflash sending it over executes it and the tablet runs......"
That's my problem exactly. My wife is going to be very upset. I thought I could keep her gtab updated without bricking it. Oh jeez that's exactly what I've done..........
Suggestion? don't do the update after you nvflash.. let the device boot up normally and put a different ROM zip file on the SD via USB.
Calkulins new ROM is based in TnT is super smooth.
http://forum.xda-developers.com/showthread.php?t=985705
From there try to reboot into recovery mode with an app like quick boot AniReboot and flash the different rom.
It may be the ROM you're trying to flash is corrupt.
I did the same too. . An didn't read the fine print. After getting the info
on how to fix my bricked gtab. Also, I had to do some Googling on apx
USB drivers for windows 7.
Long story short.. had a few pints. .. got it back to stock and installed tntl 5
The next day.. I'm using it now and I'm happy. Time for another pint.
I thought I bricked my GTab, after several hours of tweaking I was
able to flash it and run TnT Lite 5.0 now. Here is the procedure I did:
a. nvflash to stock rom. download the usb driver for windows 7 here and install (link from post by syntrix) : http://developer.download.nvidia.com/tegra/files/os/tegra_ventana_froyo_20110207.msi
b. grab the stock rom from the post by roebeet, choose "nvflash_windows_20100500.zip" and ""nvflash_gtablet_2010110500.zip": http://db.tt/Wm25t7U
c. following roebeet's instruction, put Gtab to APX mode (volume down + power on), run nvflash_gtablet.bat, should flash the rom fine.
d. boot the Gtab after flashing, should be able to run the original stock rom.
e. download the 3588 stock rom from this thread:http://forum.xda-developers.com/showthread.php?t=842000
f. run recovery (volume up + power on) to upgrade to 3588 rom, remember to make a "recovery" folder with "command" (check the prefix and see if is name "sdcard") and rename the downloaded 3588 rom to "update.zip". Put both to the root of the sdcard.
g. now you should have 3588 rom after the recovery
h. download tnt lite 5.0 rom and run a recovery. you will get stuck at a black screen. Just reboot and enter recovery mode again (volume up + power on). do a "wipe data" and reboot. Then you will be able to run TnT lite 5.0. In the recovery mode, the "power" button is "enter", not the "home" button in CWM 0.8. Anyway, just follow the instruction on screen for button layout.
Thanks. I have actually done those and would do them all but G-Tab will only boot once after flash (step d) after that if I power down, I gotta black screened brick until reflashing original ROM again. It is impossible for me to do step "F" from Gaspra post
and with that I give up. I ordered another G-Tab, and I'm using the old one as a plant stand. Who said this can't be bricked? I managed to do it.
Send it to me. I'll pay shipping.
jesusgi said:
Thanks. I have actually done those and would do them all but G-Tab will only boot once after flash (step d) after that if I power down, I gotta black screened brick until reflashing original ROM again. It is impossible for me to do step "F" from Gaspra post
Click to expand...
Click to collapse
did you try to erase the rom? try this before flashing to the stock rom:
http://forum.xda-developers.com/showthread.php?t=974422
I loaded a rom with apparent bugs and now I'm stuck in a contious boot over and over. How do I get to the recovery image to restore my latest nandroid backup? What buttons do I hold, obviously not volume down and power...
92drls said:
I loaded a rom with apparent bugs and now I'm stuck in a contious boot over and over. How do I get to the recovery image to restore my latest nandroid backup? What buttons do I hold, obviously not volume down and power...
Click to expand...
Click to collapse
Did you install clockwork mod with rom manager or NVFlash?
If you installed it through NVflash, clockwork mod is permanently on your phone by holding Volume Down + Power....if your not getting there....you didnt.....
If you used Rom Manager, you fake-flashed and won't be able to get there. The only way is by using NVFlash to install clockwork and restoring your nandroid. Go here
OR if you just wanna go back to stock, factory reset by holding both volume keys and power then releasing power when the screen is on....Good luck!
cthach11 said:
Did you install clockwork mod with rom manager or NVFlash?
If you installed it through NVflash, clockwork mod is permanently on your phone by holding Volume Down + Power....if your not getting there....you didnt.....
If you used Rom Manager, you fake-flashed and won't be able to get there. The only way is by using NVFlash to install clockwork and restoring your nandroid. Go here
OR if you just wanna go back to stock, factory reset by holding both volume keys and power then releasing power when the screen is on....Good luck!
Click to expand...
Click to collapse
Yea I used NVFlash and just hit the root button, then it asked to install something since I didn't have it, I agreed, then it loaded again and was complete. Superuser was added to my apps and that's it. I think I have a brick lol, oh well, I honestly hated not having an led for notifications anyway. I got a weird screen a few mins ago though and it was stuck for like an hour. It said "updating s/w, please wait". Then went away and now it won't go past the LG screen...
Any ideas or anyone want to buy it for like 130?
92drls said:
Yea I used NVFlash and just hit the root button, then it asked to install something since I didn't have it, I agreed, then it loaded again and was complete. Superuser was added to my apps and that's it. I think I have a brick lol, oh well, I honestly hated not having an led for notifications anyway. I got a weird screen a few mins ago though and it was stuck for like an hour. It said "updating s/w, please wait". Then went away and now it won't go past the LG screen...
Any ideas or anyone want to buy it for like 130?
Click to expand...
Click to collapse
The way you described NVFlash seems like you didn't actually use NVFlash. There is no root button involved with NVFlash.
To root the phone, you probably used superoneclickroot.
To install clockworkmod recovery you could have installed it through rom manager or installed it manually using NVFlash, which is a command line utility (unless you used the one click clockwork recovery found in this http://forum.xda-developers.com/showthread.php?t=1056847).
Can you clear these things up so we can further help.
I'll also buy it for 130 if you don't want to deal with it.
Yea you're right, I forgot, sorry finals have fogged my mind the last few days. I used superoneclick for sure and flashed the recovery through ROM manager. Will the NVFlash help get to somewhere to flash by backup or hell, even the stock rom? I just got back to my computer at home and am gonna try some things.. I'll report back..
Edit: Ok I think I found the problem. I have Eagleblood 1.02 ROM and I loaded a Kernel from a p990 (Optimus 2x) and NOT the p999 (G2x). When I plug my phone in it says LGE P990 now. So is there any fixing this? I can plug it in and it'll popo up with the notification window for the safe remove and mass storage but I still can't access the recovery image??
You should definitely flash clockworkmod recovery via NVFlash. The easiest way would be to follow this thread:
http://forum.xda-developers.com/showthread.php?t=1056847
It provides an easy to use user interface to NVFlash to flash clockworkmod recovery. After that, I guess you could flash CM7 nightly and hopefully it'll load the approriate kernel. I'm new to android so I'm not sure if ROMs contain the kernel too, but I'm guessing it is because looking at the CM7 source, they seem to include the kernel. Then after that you can flash the stock nandroid found here:
http://forum.xda-developers.com/showthread.php?t=1048274
Note: you could possibly just flash the stock nandroid instead of CM7 and it could still work out, but I'm not sure.
Sweet NVFlash fixed it, I have my recovery image again, flashed my backup and am right where I left it, Thanks man!
Im also new to rooting and flashing.....I flashed using rommanager and everything was fine till I flashed cyanogen...now I can't get to rcocery screen and I have no computer for the next few days....don't get me wrong ibwant to keep this rom-2.3.4 but it doesn't come with Google apps which i have installed on my SD but can't flash.....someonehelp
Lol, I'm nowhere near new at rooting/flashing but this phone is the first to ever NOT have a back up plan..
You'll have to do exactly what I did. Honestly, NO ONE should flash anything without the REAL recovery image and NOT through ROM manager, otherwise in this case your without a phone until you can get to a computer.
Use the NVFlash method posted above, it takes a couple minutes and then its permanent. Afterwards, if you ever flash something buggy or broken, you can always fall back on vol down and power..
Ok, I swear I have read 100 pages of similar problems, but it looks like everyone else is able to get into apx mode at least to run nvflash or easy flasher.
1. Turn on xformer with power button - stuck at Asus Eee Pad screen
2. Try to boot into recovery with vol - + power;
- volume up to enter recovery, ded android with an exclamation
- volume down to choose between 'wipe' and 'cold boot' both result in getting stuck at Asus screen
3. Plug in xformer, hold power and vol +; nothing. Never shows up in device manager and it doesn't beep or anything like the ones in all the videos do.
I really just want to get up and running at the very least, as I handle all of my businesses billing through my xformer, but my ultimate goal is to get on the HD-ROM.
I have downloaded the newest firmware from asus, have all the drivers installed (I think), have tried booting into recovery with one, some or all of the new software on the sdcard.
Any more ideas I can try? Do you just have to hold your mouth right to get it into apx mode? I have held those buttons so much I think I'm getting Nintendo thumb!!!
Thanks all!
nobody?
Throw something at me! What update.zip file do I put on the sd card? I have tried putting the newest asus update.zip on there with both its original name and the update.zip name. still comes up with a dead android and an exclamation point.
Download a firmware from Asus, rename it to EP101_SDUPDATE.zip
Put it on the root of your sd card and boot into recovery, hopefully it will flash it and let you boot up.
As for NVFlash, make sure you install teh APX driver.
Still won't get past about a second or two of trying to boot with EP101_SDUPDATE.zip on the sd card. Think I'm stuck, or is there something else I need to try?
Thanks!!
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
scottyf79 said:
..Do the apx process and try using brks tool......just dont flash touch recovery! I couldnt get the drivers to show but still managed to nvflash recovery using the tool. Its install solarnz external sd recovery so you can put a rom zip onto micro sd.
My issue was after doing this normal on off reboot kept booting to recovery and i had to cold boot into the rom.
I tried the wheelie beta and it has ended up wiping the tf completely.....so dont do that lol. Its still a soft brick as i could still nvflash recovery but decided that aslongs its wiped of root etc id just send it to asus.
If brks tool flashes for you then id try nvflashing prime and see if that works.......i think it will but i ran out of time and patience this morning to do it......at your own risk of course.
Click to expand...
Click to collapse
i am the same issue by flashed the touch CWM and window wont able to reconigzed my TF as a APX device
i tried many drivers it still not able to work.
how can i get back to normal CWM? i dont have havy roms or update.zip in internal roms.. and Touch CWM wont able to recongized Removerable sdcard
god~~
The root and backup option should flash you an external recovery.
While tablet reboots hold down volume up and power until reboot stops.
Then try brks tool again and select root and backup.......during the process it may ask if you want to back up but its not worth while as i dont think theres anything to backup. You should end up with ext micro sd recovery.
As i said id look for the prime rom thread and download the nv flash version and see if it works first.
If asus restore the wiped TF without question and everything goes ok il let you know as it may be worth wiping it with wheelie nv recovery and just RMA.
I just simply CAN'T get it into apx mode. I've installed, uninstalled and reinstalled the drivers. Trying to flash ep101_sdupdate.zip still just results in an error. crap.
Hold Volume-UP BEFORE holding power, then hold power for 5 secs (Still holding vol-up( doing this all while connected. It should show in device manager.
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
scottyf79 said:
Couldnt get Tf to show in device manager either no matter what.
I know it may not seem as though its in apx but if it has stopped rebooting when you do v up and power then it seems it is......
Seems to be an issue thats starting to become more common and very difficult to fix properly.
PC will just not recognise the TF.
Hmm - sorry i couldnt help more but id still try nv flashing Prime and if you can get to a blank screen using volume up and power without the TF rebooting theres a chance its in apx.
Best of luck dude.......
Click to expand...
Click to collapse
same case for me~~~just cant install the driver
You all can try running Puppy or DSL (damn small linux) in a virtual box on your windows pc. Comes with drivers included and only is a 200/60 Mb download.
Got so frustrated with it I just went and bought a tf-300
c3poman said:
Got so frustrated with it I just went and bought a tf-300
Click to expand...
Click to collapse
no better way to fix it than that
nice one
Yea, I like it pretty good so far. Volume is WAY louder on the 300, even though there is only one speaker. The screen also gets darker, which is nice if you watch tv or browse the interwebs in the bed. Also, wifi reception is great. Haven't tried gps yet, but I'm sure it is improved.
It did get really laggy, but I did a factory reset and it seemed to clear out the cobwebs.
Thanks for y'all's help! I'm still going to try to unbrick that tf-101 and sell it or something. Hate to have a $400 paperweight...
People will buy bricked ones on Ebay for a reduced price, just clarify that it is in fact bricked.
Okay Guys and Gals!
Now comes a mess.
Prestory: I was kinda disappointed by the performance of the stock 4.0 ICS and wanted to try out 4.2 or at least 4.1.
So I went flashing 4.2 and it didn't worked flawlessly. My Power button is somehow broken. I don't know if it's a hardware problem or software. Anyhow, I tried 4.1 and it didn't work aswell. My final conclusion was to send it back to ASUS to repair it. Of course not with a modded OS, so my goal was to flash the stock 4.0 again. Here, the trouble began.
I followed this manual [UNROOT]The easiest unrooting method (http://forum.xda-developers.com/showthread.php?t=1527931&highlight=status+7) and had a Status 7 error. One post assumed that it might be the TWRP (or so) Recovery and to try out a stock CWM.
So I downloaded the latest CWM which causes another trouble, because I downloaded the nonTouch version without possesing a dock. Well. After I got a dock I just thought: Thats it. Nope. When I try to flash a .zip from the SD Card it says, that it can't mount the SD card. So, that seems to be a dead end. I managed to install an older CWM (.13 i think) via ROM Manager but this one can't mount the SD either. The SD is accesible when the tablet is connected to the PC and through ASTRO File Manager.
I also tried Windows Tools like Easy Flasher (which fails because I can't enter APX mode for some reason), 1-Click Transformer Root (which seems to abort because of 4.1.2?) and OneClickrecovery (which also fails)
Some Infos: B40
Currently running on Cyanogen Mod 10-20130131_UNOFFICIAL-tf101 4.1.2
Well, I'm sure I forgot to mention a thousand things, so please ask.
And pleaaaase help me. The Tablet is right now pretty much useless to me and I'm really starting to miss using it.
So if you have any ideas?!
Regards from Germany, Michele
I would first try to reseat the power button by opening the device. That seems to fix the button issues for some. Then give easyflasher another try.
Or, keep trying to go into APX. It's tricky since the device doesn't appear powered on unless you have leaks on your screen, but just keep trying. Eventually you will hear the USB sound of your computer detecting it. Make sure you have the APX drivers installed too.
OK, if you have a recovery that will boot, you can try using PERI to flash Rogue Touch recovery.
The EASIEST way to flash back to stock IMO is this: http://www.transformerforums.com/fo...frederuco-s-guide-flash-tf101-back-stock.html
You can use CWM recovery to flash the stock firmware as well.
Keep in mind, if your tablet is OFF, you can hold VOL UP and then plug in the USB cord to your PC to enter APX mode (plugging it in will trigger the power on).
Same thing to enter recovery manually, hold VOL DOWN, plug in, then hit VOL UP when prompted to enter recovery.
Hi all,
Today I tried to flash an older version of the stock rom (v1.2.1) and thought I didn't need to flash userdata.img. That was a big mistake..
Now the tablet stuck at a bootloop. After that I thought I could simply flash twrp over the bootloader to peform a /cache & /data wipe so that I can fix the bootloop.
And now we come to the other BIG problem. I can't access the bootloader. It directly boots up the tablet with the Nvidia logo. Is there any solution to fix the tablet?
I tried at the bootloop to enter via adb into the bootloader but my PC isn't recognize my device (probably no usb debugging).
There is no way to rescue it? No apx drivers out there?
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
amartolos said:
Your message seems to be unclear about one very important thing:
1. Are you able to successfully access the bootloader? I don't mean your custom recovery. I mean the black screen with very small font words with your serial and shows whether your bootloader is Locked or Unlocked.
From where I'm sitting, it looks like you flashed v1.2.1 without using "flash -w", as well as forgetting to flash ALL the stock img files. Next, it looks like you're expecting a direct boot into the bootloader, which is not possible. You need to hold down the Vol_down button and then hold the Power button until the screen comes on, THEN you need to let go of the Power BUT KEEP HOLDING the Vol_down. If done correctly, you should be at the bootloader.
From the bootloader, you will not be able to run adb commands. Instead, the bootloader takes "fastboot" commands. All this is assuming you've installed the latest nVidia Shield Family drivers from the nvidia gameworks download site.
Click to expand...
Click to collapse
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
ThunderArts said:
Thanks for your answering. I flashed all .imgs, the blob file and the .dtb file . Everything but not the userdata.img. I can't access the bootloader with holding down the vol down + power button. I only can access the apx mode with power + vol up.
Click to expand...
Click to collapse
I notice in your sig that you do in fact seem to have a fully working new replacement tablet. That got me thinking along the following:
1. new tablet is fully functional, old one is not
2. both tablets have the same hardware spec
3. pull firmware from new one, and somehow get it onto the old one
4. hopefully old tablet should work!
The biggest problem is step 3... I only know of nvflash that might be able to help here, but I've never used it myself so I'm completely useless here. Maybe someone more knowledgeable could help out here, but otherwise it seems like you might be out of options.
If you do want to take a stab at nvflash yourself, THIS PAGE has a nice writeup of what some commands do, BUT BEWARE! It's not for our device, so don't just copy-paste commands! As long as you're not writing things to the new tablet, it couldn't hurt to try stuff, right?
It wish someone could help me with NvFlash because I have no knowledge with it.
So it's possible to make a copy of the system of my working tablet and flash it on my old tablet with NvFlash?
I hope someone helpful with NvFlash experience could help me out.
Btw I need to have an un-blob'd stock rom version to get it back alive? Afaik is there no public version.
NVflash is only useful if you have backed up using it BEFORE you brick it.
sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
-deleted-
ThunderArts said:
I have a replacement tablet. I could make a backup from it and use it with my bricked tablet. Do you know how this could work? (As I said I don't have experience with Nvflash yet.)
Click to expand...
Click to collapse
No the blobs are specific to the device.
sbdags said:
No the blobs are specific to the device.
Click to expand...
Click to collapse
Okay. So it seems that there is no way to rescue it. Btw is there no accessible bootloader in OTA 1.2.1 because I flashed the boot.img without any error and I don't understand why I can't access it.
sbdags said:
NVflash is only useful if you have backed up using it BEFORE you brick it.
Click to expand...
Click to collapse
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Bogdacutu said:
can you actually back up anything for nvflash? afaik there's nothing that works on the tegra k1 yet
Click to expand...
Click to collapse
Indeed - I was just talking about nvflash use in general. I haven't seen it used since tegra 3.