Related
LAST NIGHT I WAS GIVEN TWO DIFFERENT THINGS TO FLASH ONE WAS THIS
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img AND THE OTHER WAS THIS nvflash --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img CAN SOMEONE PLEASE TELL ME WHICH IS CORRECT. NOTICE ONE HAS .EXE AFTER NVFLASH AT THE BEGINNING AND THE OTHER DOES NOT. I TRIED THE ONE WITHOUT THE .EXE AND IT DID NOT WORK. I ENDED UP DOING A FACTORY RESET ON MY PHONE. (NOT HAPPY ABOUT THAT) NEED SOME HELP PLEASE AND THE CORRECT CODE. THANKS
you'll need to have nvflash setup properly and the NVidia boot-recovery driver installed. good instructions can be found here http://android.modaco.com/content/lg...-links-active/
download test2.img http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz
place the recovery-star-test2.img in your nvflash folder.
download clockwork recovery test2-- http://mirror.dal.tdrevolution.net/c...h-recovery.tgz . extract it.
in the extracted folder of cwm recovery test2, i took all the files except for test2.img and nvflash and put them in my nvflash folder.
- power off your phone. take out the battery. unplug the usb cable from the phone,you can leave the other end plugged in to the pc.
hold down both volume buttons on the phone. while holding them down, plug the usb cable in to your phone. you should hear the windows device connected sound. that's good. you'll see nothing on the phone. you can let go of the volume buttons now.
hold shift and right click an empty area inside the nvflash folder. select "open command window here".
if you can't do that, cd to your nvflash folder.
now, copy and paste this into the command window...
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img
press enter
crazythunder said:
you'll need to have nvflash setup properly and the NVidia boot-recovery driver installed. good instructions can be found here http://android.modaco.com/content/lg...-links-active/
download test2.img http://mirror.dal.tdrevolution.net/ctso/g2x/nvflash-recovery.tgz
place the recovery-star-test2.img in your nvflash folder.
download clockwork recovery test2-- http://mirror.dal.tdrevolution.net/c...h-recovery.tgz . extract it.
in the extracted folder of cwm recovery test2, i took all the files except for test2.img and nvflash and put them in my nvflash folder.
- power off your phone. take out the battery. unplug the usb cable from the phone,you can leave the other end plugged in to the pc.
hold down both volume buttons on the phone. while holding them down, plug the usb cable in to your phone. you should hear the windows device connected sound. that's good. you'll see nothing on the phone. you can let go of the volume buttons now.
hold shift and right click an empty area inside the nvflash folder. select "open command window here".
if you can't do that, cd to your nvflash folder.
now, copy and paste this into the command window...
nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img
press enter
Click to expand...
Click to collapse
ok thanks. i am going to try it that way. i just tried again with the code with .exe in it an my command prompt is just sitting still at nvflash started. in the device manager it says i am hooked up by usb and i have the nvflash folder extracted, the connection test has the system info on it but it says at the end of it command failure, no bootloader was specified. im doing this on a windows xp but will above work on a windows 7 64 bit ??
Even faster, just download "ROM manager" from the marketplace. Press "Flash ClockwordMod Recovery" then choose "Tmobile G2X".
Now you have clockworkmod recovery installed
andonnguyen said:
Even faster, just download "ROM manager" from the marketplace. Press "Flash ClockwordMod Recovery" then choose "Tmobile G2X".
Now you have clockworkmod recovery installed
Click to expand...
Click to collapse
and holding vol. down and power will perform a factory rest afterwards. unless that's been fixed.?
it's been noted here many times that doesn't work. if you get stuck in a bootloop, you can't restore backups. you'll still have to nvflash.
crazythunder said:
and holding vol. down and power will perform a factory rest afterwards. unless that's been fixed.?
it's been noted here many times that doesn't work. if you get stuck in a bootloop, you can't restore backups. you'll still have to nvflash.
Click to expand...
Click to collapse
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
tq745 said:
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
Click to expand...
Click to collapse
I think I am about to do the same. just do the recovery through rom manager and wait till an easier, more clear method is found for nvflash. I just wanted to flash Pauls patch anyway. Thanks
tq745 said:
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
Click to expand...
Click to collapse
there were a couple people out here in a bootloop and a factory reset ended in another bootloop. nvflash is the only cure at that point.
command failure, no bootloader was specified
that's normal
crazythunder said:
there were a couple people out here in a bootloop and a factory reset ended in another bootloop. nvflash is the only cure at that point.
Click to expand...
Click to collapse
Not to mention the fact that I don't really feel like doing a factory reset every time I'm in a bootloop But hey, to each his/her own I guess.
crazythunder said:
command failure, no bootloader was specified
that's normal
Click to expand...
Click to collapse
nothing ever happened on the screen of my phone. and when i held down volume- and power I ended up factory restoring my phone. Did learn that wont remove root or superuser though and they say it is good for the battery anyway so what the heck i guess but I have almost got everything restored and I dont really feel like doing it again. Is there any other way to tell if it worked?? I dont think it did since the phone did nothing.
MWBehr said:
Not to mention the fact that I don't really feel like doing a factory reset every time I'm in a bootloop But hey, to each his/her own I guess.
Click to expand...
Click to collapse
non believers lol. is it possible that some can access recovery by hardware buttons after cwm through rom manager? and others can't?
[email protected] said:
nothing ever happened on the screen of my phone. and when i held down volume- and power I ended up factory restoring my phone. Did learn that wont remove root or superuser though and they say it is good for the battery anyway so what the heck i guess but I have almost got everything restored and I dont really feel like doing it again. Is there any other way to tell if it worked?? I dont think it did since the phone did nothing.
Click to expand...
Click to collapse
unplug your phone from the usb. leave the other end plugged in to the pc.
TAKE OUT THE BATTERY! hold down both volume buttons while plugging in the usb. you should hear the windows device connected sound. let go of the volume buttons.
open the command window by right clicking an empty area inside the nvflash folder,select "open command window here" . copy and paste this into the command window nvflash.exe --bct E1108_Hynix_512MB_H8TBR00U0MLR-0DM_300MHz_final_emmc_x8.bct --bl fastboot.bin --download 5 recovery-star-test2.img .
make sure there are no spaces between emmc and _x8.bct. copying and pasting has done this to me.
now press enter on your keyboard. you should get a software update screen on your phone. and command prompt should say something like test2 sent successfully. unplug the usb. put the battery back in. press volume down and power AND HOLD BOTH FOR AT LEAST 10-15 SECONDS. you should now be in custom recovery.
crazythunder said:
non believers lol. is it possible that some can access recovery by hardware buttons after cwm through rom manager? and others can't?
Click to expand...
Click to collapse
Not that I've seen. I was wondering if it might be possible if you manually copied the update.zip to the _externalSD. Unfortunately I can't test this without reverting back to stock recovery, and I'm far to lazy for this
I'm pretty sure it's not possible without doing this, however, as recovery has no access to the internal SD (which is where Rom Manager puts the update.zip by default).
MWBehr said:
Not that I've seen. I was wondering if it might be possible if you manually copied the update.zip to the _externalSD. Unfortunately I can't test this without reverting back to stock recovery, and I'm far to lazy for this
I'm pretty sure it's not possible without doing this, however, as recovery has no access to the internal SD (which is where Rom Manager puts the update.zip by default).
Click to expand...
Click to collapse
i downloaded cwm 3.0.2.7 through rom manager, then flashed it with nvflash, just to be safe
crazythunder said:
i downloaded cwm 3.0.2.7 through rom manager, then flashed it with nvflash, just to be safe
Click to expand...
Click to collapse
Thanks for the reminder, need to update mine
I know this thread is a bit old but is there anyways someone could upload those files again? The mirrors aren't working =/
Thanks!
tq745 said:
yes you can restore backup...if you get stuck in a bootloop then all you need to do is do a factory reset by holding vol. down and power. download rom manager again and boot into clockwork then you can flash your backup.
as of right now i didn't nvflash. i like the option of having my stock recovery just in case. i also used clock work to flash paul's patch. personally i wouldn't use the nvflash method just yet as there is no roms out that require the nvflash method.
Click to expand...
Click to collapse
This is the worst advice I have ever heard. Do not follow what this guy says.
ALWAYS ALWAYS ALWAYS Nvflash. If you need to reinstall the stock bootloader then nvflash it back... some peoples kids....jeez
Pin it to Win it.
Xura08, here are the files:
NVFlash(internal) http://www.4shared.com/zip/xJJN9V_S/file.html
Gapps http://www.4shared.com/zip/54MpCVPK/file.html
Root http://www.4shared.com/zip/_LhBfM8o/file.html
Unroot http://www.4shared.com/zip/Dkj8D20u/file.html
Cm7-224 http://www.4shared.com/zip/tVg0T0Y4/file.html
Sent from my LG-P999 using xda premium
Do not use rom manager it fake flashes the phone not real cwm if something happens during a flash through rom manager you end up having to do nvflash anyway to fix it
Sent from my HTC Sensation 4G using xda premium
I have a TF300 with cm10 since two weeks.
I have install Rom manager to. He ask me to upgrade cwm. I do that but I don't reboot.
The sunday after, I have install last CM10. After download, the tablet reboot. Now I have only the logo asus and the string "The Device is Unlocked". Nothing else. I try fastboot mode but nothing else. I try apx mode. It work, the device appears in windows device manager.
My question is, can I put CWM on the tablet in apx mode ?
None of the answer in different forums works.
I need help.
bourrin said:
I have a TF300 with cm10 since two weeks.
I have install Rom manager to. He ask me to upgrade cwm. I do that but I don't reboot.
The sunday after, I have install last CM10. After download, the tablet reboot. Now I have only the logo asus and the string "The Device is Unlocked". Nothing else. I try fastboot mode but nothing else. I try apx mode. It work, the device appears in windows device manager.
My question is, can I put CWM on the tablet in apx mode ?
None of the answer in different forums works.
I need help.
Click to expand...
Click to collapse
This is the wrong cwm for your unit; it is for TF201.
This link provides help for your problem. http://forum.xda-developers.com/showthread.php?t=1680570
Look for this heading in the link posted above. - Flashed TF201 Recovery in ROM Manager?
In answer to your question, no.
Good Luck!
The problem is that I can't use fastboot. I only have apx mode than adb command doesn't work.
bourrin said:
The problem is that I can't use fastboot. I only have apx mode than adb command doesn't work.
Click to expand...
Click to collapse
Without nvflash previously installed I have not heard of anyone getting any use of apx.
My understanding you have three choices to recover your unit.
ADB, Fastboot, and recovery. In your case current recovery is out since we know it is the wrong one, that is unless you can flash the correct one.
I have read of people flashing with adb and fastboot even when the unit appeared not to respond and getting their unit restored.
So give the commands even without a response.
On most units when in cwm recovery adb works.
Also with fastboot commands try ( this example would be to flash twrp recovery )
fastboot -i 0x0B05 flash recovery twrp.blob
fastboot -i 0x0B05 reboot
then try
fastboot flash recovery twrp.blob
fastboot reboot
I know the -i 0x0B05 designates our Asus but at this stage your unit does know what it is and may be refusing based on being called Asus, so give the generic command if the normal ones don't work.
I have also read where you use the drivers from tf201 for adb and fastboot and getting their unit to respond. http://downloadandroidrom.com/file/TransformerPrime/drivers
I believe other drivers tried after tf201 were universal naked drivers.http://forum.xda-developers.com/showthread.php?t=1766220
Here is a thread you may fine useful. http://forum.xda-developers.com/showthread.php?t=1936648
Good Luck!
With universal driver, my pad is now reconize under windows. I can push recovery.img with nvflash but I doesn't work. Still block on ASUS screen and I can't access to the recovery.
I think the problem stay on another partition. Can someone do a backup of a TF300 and share this backup ?
bourrin said:
With universal driver, my pad is now reconize under windows. I can push recovery.img with nvflash but I doesn't work. Still block on ASUS screen and I can't access to the recovery.
I think the problem stay on another partition. Can someone do a backup of a TF300 and share this backup ?
Click to expand...
Click to collapse
Sorry, time to collect some info.
1. Before all of this began were you on ICS or JB?
2. The exact command you used to flash recovery.img with nvflash?
3. Exact wording for Asus block?
4. The backup you want? Stock recovery, cwm recovery, twrp recovery, boot, system, etc?
5. What kind of backup, img, blob, etc?
I know this is a lot but necessary so you are working with what you want and not what I think you want.
tobdaryl said:
Sorry, time to collect some info.
1. Before all of this began were you on ICS or JB?
2. The exact command you used to flash recovery.img with nvflash?
3. Exact wording for Asus block?
4. The backup you want? Stock recovery, cwm recovery, twrp recovery, boot, system, etc?
5. What kind of backup, img, blob, etc?
I know this is a lot but necessary so you are working with what you want and not what I think you want.
Click to expand...
Click to collapse
1. I have JB installed before CM10.
2. "nvflash.exe" --bl bootloader.bin --download 9 part9.img
3. The pad boot on the fist logo ASUS with "The Device is Unlocked." on the top left of the screen and stay at this stage.
4. I don't realy know. Every thing who can help me ...
5. nvflash seem need blob
I'm not sure. I try.
bourrin said:
1. I have JB installed before CM10.
2. "nvflash.exe" --bl bootloader.bin --download 9 part9.img
3. The pad boot on the fist logo ASUS with "The Device is Unlocked." on the top left of the screen and stay at this stage.
4. I don't realy know. Every thing who can help me ...
5. nvflash seem need blob
I'm not sure. I try.
Click to expand...
Click to collapse
Good info, thanks. I'll do some work and be back.
Ok. I uploaded what mostly appears to match your command line.
boot.img, recovery.img, and bootloader.bin all from jb 10.4.2.17.
http://www.mediafire.com/?2cpk65c5ddyek36
If you need something more or different please tell me.
Thanks you so much.
Can you just confirm the partition number of each file , please ?
bourrin said:
Thanks you so much.
Can you just confirm the partition number of each file , please ?
Click to expand...
Click to collapse
This is what I believe them to be and matches your nvflash.cfg file ( or whatever the nvflash cfg file is named).
4 - blob.EBT - bootloader.bin
5 - blob.SOS - recovery.img
6 - blob.LNX - boot.img
(the blob naames EBT, SOS, LNX I just renamed to their proper names after I unpacked the full blob)
tobdaryl said:
This is what I believe them to be and matches your nvflash.cfg file ( or whatever the nvflash cfg file is named).
4 - blob.EBT - bootloader.bin
5 - blob.SOS - recovery.img
6 - blob.LNX - boot.img
(the blob naames EBT, SOS, LNX I just renamed to their proper names after I unpacked the full blob)
Click to expand...
Click to collapse
I have no previous backup made with nvflash, do you think I can do a backup now ?
I use nvflash from a package named "tf300_nvflashpack".
There is a command named wheelie who need a file blob.bin
How can I get it ?
bourrin said:
I have no previous backup made with nvflash, do you think I can do a backup now ?
I use nvflash from a package named "tf300_nvflashpack".
There is a command named wheelie who need a file blob.bin
How can I get it ?
Click to expand...
Click to collapse
Here is the info from the nvflash guide page.
To “bootstrap” into nvflash using wheelie simply run the following command:-
$ wheelie --blob blob.bin If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
To me this appears as you rename bootloader.bin to blob.bin which I could have done when I created it. I guess I didn't look far enough ahead.
I am going to provide a link to some random info about the restoral side of nvflash.
http://forum.xda-developers.com/showthread.php?t=1962350
You may find it of use, or not.
I don't think you can backup. The file you need to flash to begin backup is flashed with fastboot and is created for the ICS bootloader. I think that would mean absolute brick if you flashed it.
tobdaryl said:
Here is the info from the nvflash guide page.
To “bootstrap” into nvflash using wheelie simply run the following command:-
$ wheelie --blob blob.bin If successful your device will boot into nvflash mode and the bootloader screen will appear on the device.
To me this appears as you rename bootloader.bin to blob.bin which I could have done when I created it. I guess I didn't look far enough ahead.
I am going to provide a link to some random info about the restoral side of nvflash.
http://forum.xda-developers.com/showthread.php?t=1962350
You may find it of use, or not.
I don't think you can backup. The file you need to flash to begin backup is flashed with fastboot and is created for the ICS bootloader. I think that would mean absolute brick if you flashed it.
Click to expand...
Click to collapse
When I try with bootload.bin I have this error :
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x405efd00daff28
[-] Failed to read RCMVERS from blob file.
bourrin said:
When I try with bootload.bin I have this error :
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x405efd00daff28
[-] Failed to read RCMVERS from blob file.
Click to expand...
Click to collapse
I believe $ wheelie --blob blob.bin is trying to access ebtblob.bin the first thing flashed when setting up nvflash which is the AndroidRoot bootloader. I have an etb blob from the origional blob file ( blob-10-4-2-17.EBT ).I think the one in nvflash folder would brick your unit completely. I can set this file up for you to download if you wish. I'll just put it up and you can decide. http://www.mediafire.com/?c9ybblcq49n61xr
I was just reviewing a thread I helped with previously. It brought something to mind I don't believe you have tried.
An attempt to get into fastboot. Power device on, press and hold volume down and use paperclip to press reset. Several times this has worked to get into recovery or fastboot when nothing else helped.
Reset is located approx one inch or 25.4 mm below the sdcard.
Link to thread mentioned above - may be of use. http://forum.xda-developers.com/showthread.php?t=1944439
I had forgotten to mention something important.
As you go through trying to sort this problem don't forget to recheck adb and fastboot access. I know it sounds silly but sometimes the most minor change or another reboot will give you access that was earlier missing.
I always block on the asus logo. I can't make apx works. I try upgrade on sd card but it does not work to.
Someone does have an idea ?
bourrin said:
I always block on the asus logo. I can't make apx works. I try upgrade on sd card but it does not work to.
Someone does have an idea ?
Click to expand...
Click to collapse
I have see that sometimes adb reconize apx mode. Do you know what driver can I use to try this ? Now I have universal_naked_driver_0.7
SAME PROBLEM as Bourrin
Hey tobdaryl, could you repost that link from mediafire. This one says file deleted and I am having the same problem as Bourrin; hoping this will fix it. Thanks!
tobdaryl said:
I believe $ wheelie --blob blob.bin is trying to access ebtblob.bin the first thing flashed when setting up nvflash which is the AndroidRoot bootloader. I have an etb blob from the origional blob file ( blob-10-4-2-17.EBT ).I think the one in nvflash folder would brick your unit completely. I can set this file up for you to download if you wish. I'll just put it up and you can decide. http://www.mediafire.com/?c9ybblcq49n61xr
I was just reviewing a thread I helped with previously. It brought something to mind I don't believe you have tried.
An attempt to get into fastboot. Power device on, press and hold volume down and use paperclip to press reset. Several times this has worked to get into recovery or fastboot when nothing else helped.
Reset is located approx one inch or 25.4 mm below the sdcard.
Link to thread mentioned above - may be of use. http://forum.xda-developers.com/showthread.php?t=1944439
Click to expand...
Click to collapse
dltabrvo said:
Hey tobdaryl, could you repost that link from mediafire. This one says file deleted and I am having the same problem as Bourrin; hoping this will fix it. Thanks!
Click to expand...
Click to collapse
Sorry, the file expired. Here is a new link for the download. http://www.mediafire.com/?ua7krzmadu3uyc1
Good Luck!
Hi,
Can someone help? My TF300T is bricked and I can't access fastboot or recovery. I can go into APX and I have the nvflash files backup.
I followed this guide http://forum.xda-developers.com/showthread.php?p=40432730
It goes all ok, then when I try to get into recovery (turning the tablet on with vol. down pressioned) it displays:
Platform Pre OS Boot configuration...
Cold booting Linux.
And then it try to boot the stock ICS rom I restaured with nvflash, but freezes on ASUS logo http://puu.sh/3Z522.jpg
I already left it for 1+ hours.
Thanks
foxrlx said:
Hi,
Can someone help? My TF300T is bricked and I can't access fastboot or recovery. I can go into APX and I have the nvflash files backup.
I followed this guide http://forum.xda-developers.com/showthread.php?p=40432730
It goes all ok, then when I try to get into recovery (turning the tablet on with vol. down pressioned) it displays:
Platform Pre OS Boot configuration...
Cold booting Linux.
And then it try to boot the stock ICS rom I restaured with nvflash, but freezes on ASUS logo http://puu.sh/3Z522.jpg
I already left it for 1+ hours.
Thanks
Click to expand...
Click to collapse
Did you use the first set of recovery instructions or the second?
Which firmware version did you unblob to get your files?
Which recovery did you flash?
tobdaryl said:
Did you use the first set of recovery instructions or the second?
Which firmware version did you unblob to get your files?
Which recovery did you flash?
Click to expand...
Click to collapse
I already tried the first method some times:
using blob from official ICS from Asus (versions 9.4.3.30 and 9.4.3.29)
about the recovery I tried ICS CWM recovery, 2.6 ICS TWRP recovery and 2.4 ICS TWRP recovery
without success accessing that menu where I can select recovery, fastboot, android or wipe.
when I try turning the tablet on holding Vol. Down I get that message on my first post.
Then I tried once the second method (the one using bricksafe.img). Still the same.
foxrlx said:
I already tried the first method some times:
using blob from official ICS from Asus (versions 9.4.3.30 and 9.4.3.29)
about the recovery I tried ICS CWM recovery, 2.6 ICS TWRP recovery and 2.4 ICS TWRP recovery
without success accessing that menu where I can select recovery, fastboot, android or wipe.
when I try turning the tablet on holding Vol. Down I get that message on my first post.
Then I tried once the second method (the one using bricksafe.img). Still the same.
Click to expand...
Click to collapse
I can't duplicate your findings. The guide works properly for me, every time.
I'm lost.
If there are no other replies that help I would suggest posting in the nvflash thread.
tobdaryl said:
I can't duplicate your findings. The guide works properly for me, every time.
I'm lost.
If there are no other replies that help I would suggest posting in the nvflash thread.
Click to expand...
Click to collapse
I also tried to use the latest update from asus using a JB TWRP or JB CWM recovery.
The problem still the same.
I can't post on dev's forum.
If there's no problem could you please post link to this thread there?
Thanks
foxrlx said:
I also tried to use the latest update from asus using a JB TWRP or JB CWM recovery.
The problem still the same.
I can't post on dev's forum.
If there's no problem could you please post link to this thread there?
Thanks
Click to expand...
Click to collapse
In my nvflash restore guide I have removed my second restore method till further study can be done.
tobdaryl said:
In my nvflash restore guide I have removed my second restore method till further study can be done.
Click to expand...
Click to collapse
Should I post about this on your thread about the nvflash?
foxrlx said:
Should I post about this on your thread about the nvflash?
Click to expand...
Click to collapse
I don't think it will make a difference.
I have not forgotten you. I glanced through the nvflash thread and found little attempt to help in most cases. I have been through the 100 and the 201 threads and have started through the 700.
I have started reading through the complete 300 thread and taking notes. I did make one addition to my first method of recovery. You might want to try it again.
I have spent several hours and feel I am near completion. I have a new method on paper but I still need to test on my tablet and refine it before suggesting for anyone else to use.
Could you tell me how you came to this point with your tablet? It might give me some insight into what needs to be done.
tobdaryl said:
I don't think it will make a difference.
I have not forgotten you. I glanced through the nvflash thread and found little attempt to help in most cases. I have been through the 100 and the 201 threads and have started through the 700.
I have started reading through the complete 300 thread and taking notes. I did make one addition to my first method of recovery. You might want to try it again.
I have spent several hours and feel I am near completion. I have a new method on paper but I still need to test on my tablet and refine it before suggesting for anyone else to use.
Could you tell me how you came to this point with your tablet? It might give me some insight into what needs to be done.
Click to expand...
Click to collapse
Thank you very much.
Well, I was on some CM10.1 nightly with TWRP, I was going to update to the latest nightly and wipe. I misclicked and wiped the /system.
I installed the CM10.1 and gapps ok. But it wasn't working, the boot was looping.
Then the recovery wasn't working either and there was no option to fastboot.
The first time I tried restoring the nvflash it worked all ok. Then I updated to JB and the recovery was broken again, so I tried the nvflash restore again and that's where everything started.
I tried that new method, only difference the wheelie didn't allow me to use --resume so I used the -r.
But the problem still the same
Maybe that menu where I select recovery, fastboot, wipe, android is broken? because that message shows only when I try to boot holding vol. down.
I already flashed lots of gadgets and never had this kind of problem, I think I wasn't paying much attention when I wiped the /system hahah
foxrlx said:
Thank you very much.
Well, I was on some CM10.1 nightly with TWRP, I was going to update to the latest nightly and wipe. I misclicked and wiped the /system.
I installed the CM10.1 and gapps ok. But it wasn't working, the boot was looping.
Then the recovery wasn't working either and there was no option to fastboot.
The first time I tried restoring the nvflash it worked all ok. Then I updated to JB and the recovery was broken again, so I tried the nvflash restore again and that's where everything started.
I tried that new method, only difference the wheelie didn't allow me to use --resume so I used the -r.
But the problem still the same
Maybe that menu where I select recovery, fastboot, wipe, android is broken? because that message shows only when I try to boot holding vol. down.
I already flashed lots of gadgets and never had this kind of problem, I think I wasn't paying much attention when I wiped the /system hahah
Click to expand...
Click to collapse
Your bootloader (ebt) the menu you mention with fastboot etc. was replaced in the first method.
Your files from blobunpack are from ICS 9.4.3.30?
The asus tablets are an odd breed. Asus created a mess with the bootloader and have continued to make it worse and worse.
Here is some info you may find useful that I posted in another thread.
Bootloaders have been an issue on this tablet since 4.1 (JB) arrived.
I swap at will between the JB bootloaders using stock recovery - next bootloader up or down.
Yes, be careful! Match bootloader, rom and twrp.
Here are the bootloaders, stock roms, and twrp- now you have to match your custom rom.
4.0 bootloader - 9.4.3.17, 9.4.3.29, 9.4.3.30 - twrp openrecovery-twrp-2.5.0.0-tf300t-ICS.blob
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3, 10.6.1.27.1 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
tobdaryl said:
Your bootloader (ebt) the menu you mention with fastboot etc. was replaced in the first method.
Your files from blobunpack are from ICS 9.4.3.30?
The asus tablets are an odd breed. Asus created a mess with the bootloader and have continued to make it worse and worse.
Here is some info you may find useful that I posted in another thread.
Bootloaders have been an issue on this tablet since 4.1 (JB) arrived.
I swap at will between the JB bootloaders using stock recovery - next bootloader up or down.
Yes, be careful! Match bootloader, rom and twrp.
Here are the bootloaders, stock roms, and twrp- now you have to match your custom rom.
4.0 bootloader - 9.4.3.17, 9.4.3.29, 9.4.3.30 - twrp openrecovery-twrp-2.5.0.0-tf300t-ICS.blob
4.1 bootloader - 10.4.2.9, 10.4.2.13, 10.4.2.17, 10.4.2.18, 10.4.2.20 - twrp openrecovery-twrp-2.5.0.0-tf300t-JB.blob
4.2 bootloader - 10.6.1.8 - twrp openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
4.2.1 bootloader - 10.6.1.15.3, 10.6.1.27.1 - twrp openrecovery-twrp-2.5.0.0-tf300t-4.2.blob
Click to expand...
Click to collapse
I unpacked the 9.4.3.30 again
Downloaded the TWRP 2.5 ICS blob file
and tried the nvflash again with those files, the problem still the same.
It's weird, because the first time it worked perfectly. with the same files.
I'll try using the 10.6.1.27.1 and TWRP 2.5 JB
foxrlx said:
I unpacked the 9.4.3.30 again
Downloaded the TWRP 2.5 ICS blob file
and tried the nvflash again with those files, the problem still the same.
It's weird, because the first time it worked perfectly. with the same files.
I'll try using the 10.6.1.27.1 and TWRP 2.5 JB
Click to expand...
Click to collapse
I'm still refining my next offer. I'll give you a shout when I'm finished - testing is in progress but slow.
The only way I found to emulate your tablet was to flash cm 10.1 while running stock ICS 9.4.3.30. The next hour was spent just getting the computer and tablet to communicate. I had to boot linux and use it to gain access. Once I used linux to nvflash 9.4.3.30 bootloader, boot, system, and twrp recovery windows recognized the tablet again but I still had no bootloader menu or useable tablet.
About an hour and a half later I had a fully functional tablet. I can't post or suggest the method I used used to recover as it borders on insanity.
Later tonight I'll try for a much safer and simpler method.
Thanks
I tried with the JB files. But no success
I will wait for your new method
Sent from my Nexus 4
foxrlx said:
Thanks
I tried with the JB files. But no success
I will wait for your new method
Sent from my Nexus 4
Click to expand...
Click to collapse
You're going to need some other help. I have not been able to find anything that is repeatable even with the same brick each time.
Go ahead and post in my nvflash thread and I'll let your post pass. Maybe someone else will respond (it is not a popular thread to post, although many have used the info).
How many posts do you need to be able to post in the developers section?
tobdaryl said:
You're going to need some other help. I have not been able to find anything that is repeatable even with the same brick each time.
Go ahead and post in my nvflash thread and I'll let your post pass. Maybe someone else will respond (it is not a popular thread to post, although many have used the info).
How many posts do you need to be able to post in the developers section?
Click to expand...
Click to collapse
Ok, thanks for all the helping.
I think at least 10 posts.
Is there any way to erase everything before flashing the files? I don't know, maybe there are some data getting in the way.
Sent from my Nexus 4
foxrlx said:
Ok, thanks for all the helping.
I think at least 10 posts.
Is there any way to erase everything before flashing the files? I don't know, maybe there are some data getting in the way.
Sent from my Nexus 4
Click to expand...
Click to collapse
Erasing can be done with fastboot.
Here are the ones I know.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 reboot
I just finished reading the tf700 nvflash thread. They are using the following commands as a standard and I have seen these used on our tablet. I can't prove this at the moment as I have a screen issue.
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
nvflash --resume –go
I'll look through my notes and give you the info I have for the Nvflash IRC.
tobdaryl said:
Erasing can be done with fastboot.
Here are the ones I know.
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 reboot
I just finished reading the tf700 nvflash thread. They are using the following commands as a standard and I have seen these used on our tablet. I can't prove this at the moment as I have a screen issue.
wheelie --blob blob.bin
nvflash --resume --rawdevicewrite 0 2944 bricksafe.img
nvflash --resume --download 14 factory-config.img
nvflash --resume --download 7 unlock-token.img
nvflash --resume –go
I'll look through my notes and give you the info I have for the Nvflash IRC.
Click to expand...
Click to collapse
Hi,
But I can't access fastboot mode
I tried those commands alone and tried combining with the ones on your guide but no success.
I guess I'm out of luck.
When you restore your blob files, does your tablet boot ok? Because mine keep on that ASUS logo with that rotating loading image.
foxrlx said:
Hi,
But I can't access fastboot mode
I tried those commands alone and tried combining with the ones on your guide but no success.
I guess I'm out of luck.
When you restore your blob files, does your tablet boot ok? Because mine keep on that ASUS logo with that rotating loading image.
Click to expand...
Click to collapse
Sometimes I have the booting problem you describe as well as boot looping. I can usually get a normal boot by pressing volume down and pressing the reset. Then let the tablet cold boot. If that fails I'll use wheelie and then nvflash to reboot.
wheelie -r --blob blob.bin
nvflash --resume --go
tobdaryl said:
Sometimes I have the booting problem you describe as well as boot looping. I can usually get a normal boot by pressing volume down and pressing the reset. Then let the tablet cold boot. If that fails I'll use wheelie and then nvflash to reboot.
wheelie -r --blob blob.bin
nvflash --resume --go
Click to expand...
Click to collapse
I tried several times but nothing different happened, I don't know what's happening that my bootloader menu doesn't show up.
What could interfere with this? Besides the blob.ebt file.
When you restore your device what rom and recovery you use?
Thanks.
So two days ago my tablet came back from the service center they repaired my faulty touchscreen yesterday i installed a rom and then did nvflash today i decided to upgrade to the latest bootloader 10.6.1.27.5 and everything went fine after the update I rebooted my tablet and whenever it reaches a state at the spinning asus logo it just freezes for 10 seconds and then reboots?? it happens to every rom i install?
any help?
thanks,
noahvt
Which way did You upgrade? Did tablet boot in android at first time or You reboot it from other mode?
Graiden05 said:
Which way did You upgrade? Did tablet boot in android at first time or You reboot it from other mode?
Click to expand...
Click to collapse
I flashed the rom via fastboot flash ... then i flashed twrp i wiped everything and then i installed the zip file from twrp and then it installed it it rebooted and then the problem started!
What zip it was? Looks like reflash rom through twrp or fastboot should solve problem.
Graiden05 said:
What zip it was? Looks like reflash rom through twrp or fastboot should solve problem.
Click to expand...
Click to collapse
And now the screen is completly black i can't turn it on or get into apx or bootloader any tips?
Apx - hold volume up and power. Bootloader menu - volume down and power.
unfortunately both do nothing
EDIT: i had to make use of the reset hole to get into apx mode: so now i am in nvflash what do i do now to restore my device i've made a backup of every partition!
Try method 7 to enter APX or bootloader described here.
Graiden05 said:
Try method 7 to enter APX or bootloader described here.
Click to expand...
Click to collapse
so i got into nvflash and did rawdevicewrite with the bricksafe.img and it worked now it's back at the spinning wheel of death :'(
Did You rewrite all rom or only bricksafe.img?
Graiden05 said:
Did You rewrite all rom or only bricksafe.img?
Click to expand...
Click to collapse
only bricksafe is i only knew the command rawdevicewrite 0 2944 bricksafe.img lol
Nvflash restore manual.
Graiden05 said:
Nvflash restore manual.
Click to expand...
Click to collapse
I don't have a backup of blob.app i only have the file"09_APP_raw.img" can i do something with that?
(and I also have: bootloader.ebt, bricksafe.img, factory-config.img, partitiontable.txt, recovery.bct)
It goes from unpacked stock rom.
how do i use it then because i used it to flash to the "10" partition and now i get unable to mount /system in twrp
okay i flashed the blob using fastboot and then flashed twrp: the error is gone now
To recover You need blob.bin and recovery.img from nvflash backup. blob.EBT, blob.APP, blob.LNX should be unpacked from ROM same android version as You'r nvflash backup. Nvflash recover manual have link's to blobtools which may unpack stock ROM blob and blobtools manual. So read all that things wisely and redo it right way. And after process of nvflash recover You may need to flash ROM through custom recovery to make it work.
Graiden05 said:
To recover You need blob.bin and recovery.img from nvflash backup. blob.EBT, blob.APP, blob.LNX should be unpacked from ROM same android version as You'r nvflash backup. Nvflash recover manual have link's to blobtools which may unpack stock ROM blob and blobtools manual. So read all that things wisely and redo it right way. And after process of nvflash recover You may need to flash ROM through custom recovery to make it work.
Click to expand...
Click to collapse
all of that didn't work still bootloops (btw when i flash a rom through recovery it takes 5 seconds!! and through fastboot writing the system only takes 124 seconds)
EDIT: also my tablet reboots after each nvflash -r --download is that normal?
What android version did You use when nvflash backup was done? What android rom did You use to grab blob.EBT, blob.APP, blob.LNX? What recovery version did You flash after restore? You can also try wipe all partitions and reflash rom.
EDIT: also my tablet reboots after each nvflash -r --download is that normal?
Click to expand...
Click to collapse
Yes, just reenter to APX and redo "wheelie -r --blob blob.bin".
Graiden05 said:
What android version did You use when nvflash backup was done? What android rom did You use to grab blob.EBT, blob.APP, blob.LNX? What recovery version did You flash after restore? You can also try wipe all partitions and reflash rom.
Yes, just reenter to APX and redo "wheelie -r --blob blob.bin".
Click to expand...
Click to collapse
i was on android 4.2.1 when i took the backup (10.6.1.15.3) I also used the 10.6.1.15.3 files and I flashed twrp after the restore!
Try do not flash twrp and wait about 10-20 min after last nvflash command (nvflash --resume --rawdevicewrite 0 2944 bricksafe.img). Also try flash blob.SOS from ROM instead recovery.img from backup.
Sorry, I'd thought I'd posted under Q&A/Help. Not sure if a moderator can move it where it belongs?
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
APX Mode
wha2do said:
My tf300t (ICS v9.3.4.17) is unlocked, rooted, and has TWRP 2.6.3.0 installed. I also have created the nvflash backups so it's currently running on the AndroidRoot v9.4.3.30r01 bootloader. I've stayed with
ICS and not updated anything except TWRP, but was just about to update to either ICS v9.4.3.30 or jump and install the latest JB.
Earlier today I went into Terminal Emulator, typed su and reboot as I've always done. I thought my tablet had shutdown because the screen stayed blank. I tried the power button and nothing so thought
maybe my power button had given out. I then tried plugging in the charging/usb cable which normally would get it to boot and again blank screen. Last I tried connecting to my pc and found it was in
APX mode. I'm able to boot up from nvflash and function normally but I'm stuck once I shut off the tablet from ICS (have to rerun nvflash to boot up again).
When I power off from APX mode, it automatically restarts back into APX mode. I was able to get into TWRP and tried restoring my latest nandroid (System, Data, Recovery, & Boot partitions) but no
change. Also tried a factory reset but same results - booting into APX yet again...
Ack, at this point I'm about ready to punt. I have my backups (TB & Helium) and am thinking of trying to update to v9.4.3.30 to see if this clears up booting into APX mode. To do this, can I just install the single
zip using TWRP & then re-flash TWRP using adb (or fastboot assuming I get it back)? Or do it via nvflash? If by nvflash, are these the correct commands after unpacking the v9.4.3.30 blob:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
Thoughts or ideas are really appreciated!
Click to expand...
Click to collapse
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
lj50036 said:
WoW that is an old bootloder..... v9.3.4.17 What is the SKU of that bootloader??
Enter APX mode and bootstrap in, If thats the ways its done.. I don't know because, I did my nvflash after jb came out...Run this command
Code:
nvflash -r --go
It will not reboot your tablet but it is supposed to let the bootloader resume on go which should be the next boot....
Just long hold your power button and let your tablet boot normally... Let me know if this helps at all... Thx lj
O yeah just be aware that the newest version of TWRP is having some issues... Just a FYI
Click to expand...
Click to collapse
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
wha2do said:
Thanks for the reply. The bootloader is the original one loaded when I created the nvflash backups. When rebooting from nvflash and holding the vol down button, I see:
Android cardhu-user bootloader <2.10 e> released by "WW_epad-9.4.3.30-20120206"
This had to have been universal for all that ran it way back when, though the SKU on my tablet is US (US_epad-9.4.3.2012...) and no real issues in over the year I've had it.
The nvflash -r --go command is the same as nvflash --resume --go...both reboot the device (nvflash help verifies they're the same).
------> Back to the issue at hand *sigh* <-----
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Sooo...what's my next step? Have noticed TWRP 2.6.3.0 seems to be a bit flaky in the past. Should I try installing US_epad-user-9.4.3.30.zip using TWRP? I have
OTA Rootkeeper installed with SuperSU so root should either remain or be restorable (fingers crossed). Or do I need to use nvflash to flash each partition? Or finally go
back to my original nvflash blobs? I really don't want to move forward and screw up something worse than it is!
Side note: I've tried to install tried & true TWRP v2.3.1.0. Using adb, it appears to flash successfully, I reboot into ICS, and then nvflash boot into TWRP - but I'm still
on v2.6.3.0. Possibly not rebooting smoothly into ICS isn't allowing the img file to take? For now will deal continue using my installed version v2.6.3.0 I guess...
Thanks for direction on where to go next! And if can, spell out my steps to take in detail (sometimes I may be a tad dense and don't mind any eyestrain, lol).
Click to expand...
Click to collapse
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
lj50036 said:
Ok so you are 100% sure that you have had a US SKU version bootloader from when you got it new????
Where are you getting the firmware zip file from??
And you think this all started because of a wrong recovery flash???
Click to expand...
Click to collapse
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started while using the tablet normally. No flashing, restoring nandroids, etc in at least a week or two. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get the behaving normally again. In this case I rebooted using Android Terminal and suddenly only had a black
screen. Finally realized it wasn't powered down but was going into APX mode... Sorry, just tried flashing the older version of TWRP I'd always used since v2.6.3.0 has been flaky off and on. V2.6.3.0 was
originally flashed about 2-3 weeks ago and I'll just stick with it while working on fixing this!
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe foolishly? I let Avast
uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system or data partitions messed up. Could it
be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
wha2do said:
Thanks for the quick reply... I'm positive on the US SKU - I have a screenshot I took of the the SW info when it was brand new - here it is:
http://i1331.photobucket.com/albums...delampSWinfo-2012-11-25-07-29_zps27ba6fc6.jpg
As for the earlier firmware zips I've got, they were provided in one of the XDA posts - possibly this one: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
Nope, it just suddenly started without having done any flashing or restoring nandroids. I was playing one of my games on the tablet and sometimes the graphics will act
funny or it'll fc on me. So I either do a cold restart or reboot using Terminal Emulator to get it back to normal. In this case I rebooted using Android Terminal and suddenly
a black screen. Finally realized it wasn't powered down but was going into APX mode.
The only thing I can think which may be unrelated. My daughter loaded a non-market game that was tagged as having Android:Fujacks by Avast! Being non-market, maybe
foolishly? I let Avast uninstall it. But I'm almost positive I rebooted a few times after without any issues. Also restoring an earlier nandroid didn't help, so don't think it's the system
or data partitions messed up. Could it be the boot partition that's gone funky?
That's why I'm wondering if an "upgrade" to v9.4.3.30 would clear this up - and if so, best/safest way to do it? Hope that helps fill in a little more!
Click to expand...
Click to collapse
Ok the .30 zip from them what is inside the zip??
lj50036 said:
Ok the .30 zip from them what is inside the zip??
Click to expand...
Click to collapse
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
wha2do said:
It's the normal Stock v9.4.3.30 update from ASUS. It's the "US_epad-user-9.4.3.30.zip" which in turn contains the META-INF folder and the blob file. The blob file contains:
blob.APP ; system img
blob.EBT ; bootloader.bin
blob.LNX ; boot img
blob.PT ; partition table I presume
blob.SOS ; stock recovery img
The blob names are exact and I think I have each identified as to their purpose going from old notes. EBT, APP, and LNX are the three that I believe could/would be flashed using nvflash
if necessary (if can't just install the full update zip & reinstall TWRP over the stock recovery)...
Is that what you're looking for?
Click to expand...
Click to collapse
Ok so it just a blob binary and a META-INF folder in the zip??
lj50036 said:
Ok so it just a blob binary and a META-INF folder in the zip??
Click to expand...
Click to collapse
Yep...standard update zip inside a zip that comes from ASUS.
wha2do said:
Yep...standard update zip inside a zip that comes from ASUS.
Click to expand...
Click to collapse
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
lj50036 said:
We need to get to fastboot and verify that we can see your devices boot into the bootloader screen.. As I recall you should have a
usb icon you must select to enable fastboot... Can you get to this point??
Click to expand...
Click to collapse
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So... I'm still having to reboot from APX mode using nvflash and hold the volume down button. At that point I can either enter TWRP or leave it go and it'll cold boot - no icons
display for fastboot, etc. It just shows:
Platform Pre OS boot configuration...
Cold-booting Linux
And then it will boot into ICS, though found it may just go back into APX mode again. It can take several tries, but it'll finally boot properly.
Click to expand...
Click to collapse
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
wha2do said:
No, the icons one normally sees are missing/not available to be selected. When I reboot from nvflash & hold the vol down button, I only have two options. Volume up to enter TWRP as expected, or it begins cold booting. Guess that got lost in my lengthy message above:
So unfortunately, no fastboot - only ADB, APX, and Recovery (TWRP) modes available.
Click to expand...
Click to collapse
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
lj50036 said:
Ok well we need a different version of twrp than what your on now I would highly recommend a version older that what your on now.. as the newer twrps are buggy 2.5.5.0 is a solid one... Make sure you get the one for your tablet...as there are a few different versions... Than rename it
Code:
twrp.blob
Make sure you don't rename it twrp.blob.blob as windows is good at doing still stuff like that.....
Move your twrp.blob to the root of your c drive than open a command window as admin and type
Code:
cd /
This will move you to the root of your c drive in your command window than type
Code:
dir
This will list all the files and folder in the root of your c drive make sure you see the twrp.blob if so your ready
Boot your tablet into APX mode bootstrap into nvflash mode and type
Code:
nvflash -r --download 5 twrp.blob
The output of this will look something like this
Code:
Nvflash v1.13.87205 started
[resume mode]
sending file: twrp.blob
- 8165480/8165480 bytes sent
twrp.blob sent successfully
Than
Code:
nvflash -r --go
Then try to enter recovery...
Let me know
Click to expand...
Click to collapse
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
wha2do said:
Ok - picked up v2.5.0.0 (don't see a v2.5.5.0 on the TWRP website) and successfully installed the .blob file but... As soon as I hit the volume up button it went to cold boot instead. I remembered with the Prime that for some reason, the TWRP img file format needed to be used when on the AndroidRoot bootloader. So long story short, got the img file installed and I have TWRP 2.5.0.0 running at the moment.
So where to next? And thanks so far
Click to expand...
Click to collapse
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
lj50036 said:
So you can get into recovery now??? if so, take the double zipped firmware......unzip it one time and the zip that is made move to.....O
Do you have a way to put that zip on an sdcard so we can get it on your tablet?? If not no big deal.... Just let me know if you can make that happen.....
Click to expand...
Click to collapse
Sorry, I get over wordy (lol)... Yes, I have TWRP 2.5.0.0 installed and was able to get in. I'd already prepared for this - have the unzipped (once) file sitting in my tablet's root folder (/sdcard). Checked and checksum matched so it transferred without errors (used Airdroid, in case wondering).
Took a few extra minutes - wanted double check all was there as I thought. So yes, have the v9.4.3.30 zipfile (containing META files & blob) on tablet's "root" directory. Currently in TWRP v2.5.0.0 and ready to install it (figuring that's the next step)...
Just give me the greenlight, lol
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
wha2do said:
One thing doing quickly is making a nandroid - never can be too safe, heh! Should be about another 5 minutes...
Click to expand...
Click to collapse
No worries at all you take your time.... Let me know....
lj50036 said:
No worries at all you take your time.... Let me know....
Click to expand...
Click to collapse
Good to go!
wha2do said:
Good to go!
Click to expand...
Click to collapse
??????
Still here - at this point have the zipfile unzipped once, on the tablet's root directory, and TWRP v2.5.0.0 installed. I assume going to install the zip file via TWRP Install? Tablet's got plenty of battery charge so good to go - just let me know!