Related
Welcome to the general HELP thread I've made.
The idea was given to me, and the TF doesn't have one, so here it is!
I'll be checking this often and appreciate if others do too, and try to help with problems people have.
I notice many of the same questions have been asked constantly, so I want to try and consolidate questions and answers into one searchable thread in Q&A, also to ask in.
DON'T USE ROM MANAGER ON THE TF101, EVER! It causes bootloops!
Go ahead and ask here!
Abuse towards new users isn't tolerated, but neither are very silly questions either.
Please Search before posting though! Seriously, you find lots of answers and cool stuff!
--
ToD
Thing O Doom said:
Welcome to the general HELP thread I've made.
The idea was given to me, and the TF doesn't have one, so here it is!
I'll be checking this often and appreciate if others do too, and try to help with problems people have.
I notice many of the same questions have been asked constantly, so I want to try and consolidate questions and answers into one searchable thread in Q&A, also to ask in.
DON'T USE ROM MANAGER ON THE TF101, EVER! It causes bootloops!
Go ahead and ask here!
Abuse towards new users isn't tolerated, but neither are very silly questions either.
Please Search before posting though! Seriously, you find lots of answers and cool stuff!
--
ToD
Click to expand...
Click to collapse
I just got my transformer upgraded to .24 and rooted with your PERI tool. I have to say it was the easiest root I've performed on any of my Android devices thus far! Thank you for being an awesome resource to the AT community!
Sent from my SPH-D710 using Tapatalk 2
Your opinion on the most stable kernel to OC/UC for a TF noob?
Sent from my SPH-D710 using Tapatalk 2
Definitly Guevor's kernel.
Can find it here: Guevor ICS Test v21.4 (The latest is 21.10 though available towards the end of the thread as an attachment.)
Make sure to use the AOKP version if you're on aokp, megatron on megatron and normal for stock/arhd/revolver roms.
Hello everyone. I'm new. I want to know why my Pad won't boot into CWM using the Volume Down/Power button method. I have to run the rooting tool again to do that.
I don't know if this is normal or not, because my Samsung boots into CWM easily.
Can you get into stock recovery (android with red !) Or just nothing?
If it's nothing at all, you're doing the button combo wrong,
make sure to hold vol-down before pressing power, then release both when it says 'checking for rck...' then press vol-up immediately when it says that.
Hello!
I'm new here so please be patient with me
I want to ROOT my Asus TF101 for the first time. Version .24.
I don't know so much about the technical stuff, but I can learn (I'm still young ).
My question is if the EazyFlasher tool can be ONLY for root and nothing else? All I want is a root to back-up my data.
by following the steps 1 by 1, will I success rooting my tablet? Or there's something that is obvious for advances and that's why it's not written?
I know my questions are silly for you guys, but I'm scared to do something wrong...
Thank you!
You can use the PERI tool I made (in my signature) to easily get root. Just plug in your tf, run the .bat file, and you should have root in about 15 mins pretty easily.
It boots into stock recovery just fine, just not into CWM even after I installed it.
Sent from my Transformer TF101 using XDA
is adb working? any errors thrown? drivers installed? just a bit more info please
Great effort you're doing
What a noble effort and good cause. I'll chime in when I can help out and ask questions when I need to. I know some people find it easier to tell someone who needs help to 'just Google' or 'can't you read' type responses, but that isn't helpful to someone who's gotten a little lost or confused or just doesn't know the right answer yet. There are ways to gently guide new folks to the proper ways to seek out what they need without being rude about it. Good luck with this and keep up the good work.
In a perfect world - our transformers will grant wishes. They don't though... so this is here x3
TF101 / B90 cant boot beyond ASUS screen
as the title says my transformer stuck at the ASUS screen when booting up and isnt getting any further, stock recovery gives me the dead droid with the red warning.
I tried NVFLASH/Wheelie to flash different stock ROMs 1.11, 1.21, 1.24 .. With the same outcome .. cold booting tens of times, nothing happens
I used EasyFlasher to install the Rogue XM Touch Recovery, and tried to install the stock ROM zip file from my SD card ( i cant read internal memory), But wont it install it (i get STATUS 7 error)
I been working on it for more than a week, and I am about to lose all hope
Are you sure you're using NvFlash properly, and do you have ADB access to the device? Usually Nvflash and ADB not working is a driver issue. Please post a screen of what wheelie does when you try to Nvflash your B90 (use the Sbkv2 bat)
I believe i use NVFlash right (but i cant use ADB, it never finds the tablet) .. this is what i am getting
Code:
D:\My Folders\Desktop\wheelie>"wheelie.exe" -2 --bct transformer.bct --bl bootl
oader.bin --odm 0x300d8011
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x299506994287477335
[=] RCM Version: 0x20001
[=] CPU Model: Tegra 2
[=] Secure Boot Key Set: Yes
[+] Sending BCT
Sending file: 100 %
[+] Sending ODMData 0x300D8011
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --bct transformer.bct --setbct --
configfile flash.cfg --create --odmdata 0x300d8011 --sync
Nvflash started
[resume mode]
setting device: 2 3
creating partition: BCT
creating partition: PT
creating partition: EBT
creating partition: SOS
creating partition: LNX
creating partition: BAK
creating partition: GP1
creating partition: APP
creating partition: CAC
creating partition: MSC
creating partition: USP
creating partition: PER
creating partition: YTU
creating partition: UDA
creating partition: GPT
Formatting partition 2 BCT please wait.. done!
Formatting partition 3 PT please wait.. done!
Formatting partition 4 EBT please wait.. done!
Formatting partition 5 SOS please wait.. done!
Formatting partition 6 LNX please wait.. done!
Formatting partition 7 BAK please wait.. done!
Formatting partition 8 GP1 please wait.. done!
Formatting partition 9 APP please wait.. done!
Formatting partition 10 CAC please wait.. done!
Formatting partition 11 MSC please wait.. done!
Formatting partition 12 USP please wait.. done!
Formatting partition 13 PER please wait.. done!
Formatting partition 14 YTU please wait.. done!
Formatting partition 15 UDA please wait.. done!
Formatting partition 16 GPT please wait.. done!
done!
sending file: blob.EBT
| 1454712/1454712 bytes sent
blob.EBT sent successfully
sending file: blob.SOS
\ 4284416/4284416 bytes sent
blob.SOS sent successfully
sending file: blob.LNX
/ 4151296/4151296 bytes sent
blob.LNX sent successfully
sending file: blob.APP
/ 536870912/536870912 bytes sent
blob.APP sent successfully
D:\My Folders\Desktop\wheelie>"nvflash.exe" -r --go
Nvflash started
[resume mode]
sidneyk said:
What a noble effort and good cause. I'll chime in when I can help out and ask questions when I need to. I know some people find it easier to tell someone who needs help to 'just Google' or 'can't you read' type responses, but that isn't helpful to someone who's gotten a little lost or confused or just doesn't know the right answer yet. There are ways to gently guide new folks to the proper ways to seek out what they need without being rude about it. Good luck with this and keep up the good work.
Click to expand...
Click to collapse
I agree with this 100%. I will browse this thread as well and help out when i can.
I'm running stock ROM and Kernel, rooted and NO random reboots or SODs. Think this is a coincidence? Here to tell you it isn't. If you need help, ask and if I know, I'm all yours.
It looks like Wheelie worked fine, you can't get ADB to detect at all? Try running Wheelie in a Linux virtual box (Puppy/Damnsmalllinux work fine and are very small downloads)
I just cant!! its like the 5 time i did it and i cant!!!
i follow the steps and the tf restart 2 times, and all that stuff
but when i try to go into recovery
it just doesnt go!!
i dont know what to do!!!! :'( ill cry
Which tool are you talking about and what are you trying to do?
Thing O Doom said:
is adb working? any errors thrown? drivers installed? just a bit more info please
Click to expand...
Click to collapse
I'm sure the drivers are installed because I rooted it with my computer. But just to make sure, how do I check?
I've tried many solutions (read from various forums) but yet to find a way to recover my bricked TF101.
I totally don't know how to use linux so please help me by using Windows's way.
Thank you.
I will try to describe as clear as possible regarding my issues.
The serial number began with B50K so should be SBKv1.
This tablet belong to my brother, he can't turn on the unit last week and he asked help from his friend.
I have no idea what his friend did but now this tablet only able to be detected in APX mode once plug into Windows PC.
The battery still able to charge via USB cable (I have opened up the casing and measured the battery pack voltage (above 8.0V).
ADB can't find this tablet but NvFlash can upload bootloader.bin successfully when run "download.bat"(the rest of the steps failed).
USB cable and PC, drivers all should be OK as I am able to flash my other TF101 unit.
Please read the below error messages when I tried to run Nvflash and wheelie:
Run NvFlash "download.bat" from DoS Promt, TF101 LCD screen shows:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 037c61542axxxxx
(Nvidia recovery driver still shown in Windows Device Manager)
Run reflash_sbkv1 from DoS Promt, TF101 LCD screen shows:
Entering NvFlash recovery mode / Nv3p Server
Chip Uid: 037c61542axxxxx
!!!!phone update success!!!!
!!!!phone update faileded!!!!
!!!!phone update faileded!!!!
(Nvidia recovery driver still shown in Windows Device Manager)
I've tried on different PC and notebooks, XP, Windows 7 (both 32-bit and 64-bit), all returned same results, no luck.
I've tried Peri Tool 0.4 and EasyFlasher-0.8.3b all can't fix as well.
The TF101 only can detected as APX, tablet screen only turn on during "flashing".
Can't enter recovery mode (Power+Volume Down), can't turn ON (no display nor sound).
This problem possible caused by hardware issues like faulty NAND chip etc?
Please help me to solve this tablet.
Thank you in advance.
The logs show "bad data". Can you re-download everything and start over?
Lethe6 said:
The logs show "bad data". Can you re-download everything and start over?
Click to expand...
Click to collapse
Thanks for your reply..
Tried many times with different nv flash version, same failed results.
Go to this post: http://forum.xda-developers.com/showthread.php?t=1995157
Download the application per the instructions. You are NOT going to install Linux and you will NOT dual boot your tablet.
Once you have the Windows application open you will click on the Flash tab. From the dropdown called Dualboot A/U, select the option that says "Android Only". Make sure you have the system.img file in your images folder which is Roach rooted ROM called "Prime".
The purpose of this is it works directly with your APX mode. I looked at your screenshots and the commands looked odd to me but I could be wrong.
TomTcom said:
Go to this post: http://forum.xda-developers.com/showthread.php?t=1995157
Download the application per the instructions. You are NOT going to install Linux and you will NOT dual boot your tablet.
Once you have the Windows application open you will click on the Flash tab. From the dropdown called Dualboot A/U, select the option that says "Android Only". Make sure you have the system.img file in your images folder which is Roach rooted ROM called "Prime".
The purpose of this is it works directly with your APX mode. I looked at your screenshots and the commands looked odd to me but I could be wrong.
Click to expand...
Click to collapse
Hi,
Thank you for the link, will give it a try.
BTW, why you say "the commands" look odd? I am running the commands in Dos Prompt so that I can see all the logs.
Tried tfubuntu, still got error. Please see the attachment.
ongbs said:
Hi,
Thank you for the link, will give it a try.
BTW, why you say "the commands" look odd? I am running the commands in Dos Prompt so that I can see all the logs.
Click to expand...
Click to collapse
It looks like your nvflash command duplicates what the wheelie command already did. I could be wrong though, there are a couple of ways to input the commands from both wheelie and nvflash.
TomTcom said:
It looks like your nvflash command duplicates what the wheelie command already did. I could be wrong though, there are a couple of ways to input the commands from both wheelie and nvflash.
Click to expand...
Click to collapse
Tfubuntu installer failed with almost same error as NvFlash "download.bat", any clues?
Seems like every time the error shown when trying to create partition.
Anyone know how to use NvFlash to create partition in TF101 manually?
ongbs said:
Tfubuntu installer failed with almost same error as NvFlash "download.bat", any clues?
Seems like every time the error shown when trying to create partition.
Anyone know how to use NvFlash to create partition in TF101 manually?
Click to expand...
Click to collapse
It might be an issue with B50 series...
Here is a manual idea you can try:
From windows dos prompt, go to the directory where the wheelie.exe and nvflash.exe files are located. Don't run your batch file.
Copy this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Once that is done, copy this and hit enter: nvflash -r --getpartitiontable ptable.txt
In that directory, the file will create called "ptable.txt". This is your partition table and identifies what's already set up. I believe BCT should already be set up.
To get out of nvflash mode, type this: nvflash -r --go
Mine looks like this:
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048
Tell me what you get.
TomTcom said:
It might be an issue with B50 series...
Here is a manual idea you can try:
From windows dos prompt, go to the directory where the wheelie.exe and nvflash.exe files are located. Don't run your batch file.
Copy this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Once that is done, copy this and hit enter: nvflash -r --getpartitiontable ptable.txt
In that directory, the file will create called "ptable.txt". This is your partition table and identifies what's already set up. I believe BCT should already be set up.
To get out of nvflash mode, type this: nvflash -r --go
Mine looks like this:
PartitionId=2
Name=BCT
DeviceId=18
StartSector=0
NumSectors=1536
BytesPerSector=2048
Tell me what you get.
Click to expand...
Click to collapse
Thank you for your quick response.
Tried that DOS command, still failed.
Whenever trying to read/write to partition, command will return with errors.
Please refer to attachment.
Possible a hardware failure?
Your partitions probably need formatting. I'll pull the default android only config file from tubuntu application and post some instructions later tonight.
I had to format my partitions before so give me some time.
Sent from my SGH-T999 using Tapatalk 2
Ok we'll do a similar process. I'm not sure on the config file so I don't want to give something that I'm not sure how it worked. I formatted one of my partitions to ensure this command works.
Go back to the DOS prompt where wheelie and nvflash are located.
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
The last command will reboot you. With your current setup you may now need to power off again, go back into APX mode and run your batch file or the Tubuntu application I had you download before.
Let me know what happens.
TomTcom said:
Ok we'll do a similar process. I'm not sure on the config file so I don't want to give something that I'm not sure how it worked. I formatted one of my partitions to ensure this command works.
Go back to the DOS prompt where wheelie and nvflash are located.
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
The last command will reboot you. With your current setup you may now need to power off again, go back into APX mode and run your batch file or the Tubuntu application I had you download before.
Let me know what happens.
Click to expand...
Click to collapse
Thank you my friend.
Will try it when I back home today.
TomTcom said:
Ok we'll do a similar process. I'm not sure on the config file so I don't want to give something that I'm not sure how it worked. I formatted one of my partitions to ensure this command works.
Go back to the DOS prompt where wheelie and nvflash are located.
Type this and hit enter: wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
Type this and hit enter: nvflash -r --format_partition 2 --bl bootloader.bin (If successful you will know it will say this: Formatting partition 2 please wait.. done!)
Type this and hit enter: nvflash -r --go
The last command will reboot you. With your current setup you may now need to power off again, go back into APX mode and run your batch file or the Tubuntu application I had you download before.
Let me know what happens.
Click to expand...
Click to collapse
Tried those commands and returned with error, look like my TF101 doesn't has partition on it.
ongbs said:
Tried those commands and returned with error, look like my TF101 doesn't has partition on it.
Click to expand...
Click to collapse
This idea is at your own risk. I can't test it because that would require me to format my tablet and redo all my stuff. If you don't feel comfortable then I understand.
Download this file, this is my dropbox link: https://www.dropbox.com/s/qnk61hrx5w8s2qp/androidpartition.cfg
This file is a .cfg text file. You can open it in an editor and view it. Put this file in the directory where wheelie and nvflash are located.
We are going to attempt to format all partitions and use this config file to model all your partitions after.
Steps:
1. wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
2. nvflash -r --format_all --create --configfile androidpartition.cfg (if this doesn't work see step 2b.)
2b. nvflash -r --format_all --configfile androidpartition.cfg
3. nvflash -r --go
Let me know what you get.
TomTcom said:
This idea is at your own risk. I can't test it because that would require me to format my tablet and redo all my stuff. If you don't feel comfortable then I understand.
Download this file, this is my dropbox link: https://www.dropbox.com/s/qnk61hrx5w8s2qp/androidpartition.cfg
This file is a .cfg text file. You can open it in an editor and view it. Put this file in the directory where wheelie and nvflash are located.
We are going to attempt to format all partitions and use this config file to model all your partitions after.
Steps:
1. wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
2. nvflash -r --format_all --create --configfile androidpartition.cfg (if this doesn't work see step 2b.)
2b. nvflash -r --format_all --configfile androidpartition.cfg
3. nvflash -r --go
Let me know what you get.
Click to expand...
Click to collapse
I definately will try it later my friend.
Thank you for your help.
TomTcom said:
This idea is at your own risk. I can't test it because that would require me to format my tablet and redo all my stuff. If you don't feel comfortable then I understand.
Download this file, this is my dropbox link: https://www.dropbox.com/s/qnk61hrx5w8s2qp/androidpartition.cfg
This file is a .cfg text file. You can open it in an editor and view it. Put this file in the directory where wheelie and nvflash are located.
We are going to attempt to format all partitions and use this config file to model all your partitions after.
Steps:
1. wheelie -1 -o 0x300d8011 --bl bootloader.bin -c transformer.bct
2. nvflash -r --format_all --create --configfile androidpartition.cfg (if this doesn't work see step 2b.)
2b. nvflash -r --format_all --configfile androidpartition.cfg
3. nvflash -r --go
Let me know what you get.
Click to expand...
Click to collapse
Still got error my friend. Do you think possible all these error caused by faulty hardware?
ongbs said:
Still got error my friend. Do you think possible all these error caused by faulty hardware?
Click to expand...
Click to collapse
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
TomTcom said:
It's probable my commands aren't correct. Hopefully you can see from the idea of how I started the commands and try to figure it out with some google searches. I don't know for sure if that config file is in the correct format for nvflash either. I used it from the Tubuntu application but the Tubuntu application doesn't have a "format all" and recreate everything option.
I believe your partitions are either not set correctly or the partition table is corrupt or non-existent.
I don't think you have faulty hardware at this point because you can execute wheelie and nvflash without problems so as long as you can do that you still have a fighting chance to recover the tablet.
I searched a lot on these commands but you'll need to do some more. I don't know yet what else I can provide. Good luck!
Click to expand...
Click to collapse
Alright. thank you my friend.
I am noob in NvFlash, hope other experienced members can give me some advices.
Hi all,
I've put my transformer into an infinite reboot loop. It starts booting into TWRP, I see the splash and after about 2 seconds it drops to a console with the following message
Code:
Updating partition details...
E:Unable to mount '/staging'
Formatting Cache using make_ext4fs
There are two more lines that come up after that but I can't see because the reboot happens too fast. If hold power up during the reboot, I can get into what ppears to be APX mode, i.e. the tablet stops rebooting, and the screen is completely black. Wheelie detects the device in APX mode but nvflash doesn't work afterwards.
The transformer has a serial number starting with B90, so it's at least SBK2.
Here's how I got into this lousy situation ...
I rooted using the adb commands of the wolf exploit as found in the PERI tool. After that I was trying to install native ubuntu using the net-install rootfs following the instructions in those two links. Everything seemed to work, I got wifi, It downloaded, it installed. But on reboot all I got was an initramfs busybox prompt. I'd chosen the jhinta kernel, so I read though the entire net-install thread again, and found the following three posts:
http://forum.xda-developers.com/showpost.php?p=31458873&postcount=148
http://forum.xda-developers.com/showpost.php?p=31466313&postcount=152
http://forum.xda-developers.com/showpost.php?p=31544961&postcount=162
The short version of which was that the script trying to flash the jhinta kernel didn't work, and I needed to do it manually. So I took the blob from the zip attached to the first post, unpacked it and flashed the unpacked blob to /dev/block/mmcblk0p4, /dev/block/mmcblk0p10 and /dev/block/mmcblk0p9 in turn, testing reboots in between. After flashing to mmcblk0p10 didn't make a difference, I tried flashing on mmcblk0p9 but dd complained about running out of space. The image was 8.8Mb and the partition seemed to be only 8Mb in size. I figured this would be a problem, because that partition is meant to be the recovery kernel I vaguely recalled. So just to be safe, BEFORE rebooting I flashed the recovery image from it's zip file again. I rebooted, and now I'm in the infinite loop.
I don't have access to recovery. I am hoping that I can use nvflash and wheelie maybe to return to stock and go over it again from scratch, but wheelie/nvflash reports the following:
Code:
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Using SBK type 2.
Using bootloader: 'bootloader.bin'.
Using BCT: 'transformer.bct'.
----------------------------------------
[=] Chip UID: 0x37c708340003257
[-] Incorrect SBK or SBK type selected. nverror: 0x4.
Nvflash started
[resume mode]
failed executing command 11 NvError 0x8
command failure: create failed
Nvflash started
[resume mode]
connection failed NvError 0x8
I have a nasty feeling that wheelie doesn't work for my TF101G, but I'm not sure. What else can I try, or should I send it back to ASUS and pay for them them return it to stock?
Thanks in advance
NVFlash and Wheelie do not work with the TF101G as it has a different SBK from the two TF101 SBK's.
The SBK is not known because not enough TF101G users tried to crack it.
You can try flashing a different recovery using ADB when in your current TWRP, but beyond that you may be in trouble.
Might want to try either 2.3.2.3 or 2.5.0.0 TWRP.
Hmm, the machine doesn't stay in recovery long enough to do anything via ADB.
Code:
adb wait-for-device
doesn't unblock through three reboot cycles.
So I have two options:
1. try to crack the SBK
2. ship it off to ASUS
Any ideas on how to start on 1? Loop through all the options of wheelie -o? I'm hoping there's a better way to go about it?
Sadly, that is probably true, but you are forgetting option 3: Get a new tablet.
Sorry, other post is a bit hard to read, was trying to see if upgrading my TF300t (unlocked, rooted, nvflash run) to v9.4.3.30 would fix it - which unfortunately didn't.
I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post for added details is at:
Original post with more details
I'm thinking the AndroidRoot booloader I've been running from when I originally created my nvflash backups got corrupted. The update (via Install Zip in TWRP) does
not seem to have updated the bootloader. In reading even more posts, another user shows:
The Device is UnLocked
Android cardhu-user bootloader <2.10 e> released by "US_epad-9.4.3.30-20120604" A03
Checking for android ota recovery
I see the exact same except my version is "WW_epad-9.4.3.30-20120604", which makes me think the bootloader isn't getting updated correctly & is still the original AndroidRoot
version which became corrupted? I also double checked the new EBT blob I'm flashing via a hex editor and it shows it has a US SKU! So does that mean nvflash isn't truly
flashing it? If not, how can I get it to take either with nvflash, ADB, or TWRP?
Also can see (lack of) progress below *sigh*
wha2do said:
Sorry, other post is a bit hard to read, was trying to see if upgrading to v9.4.3.30 would fix it - which unfortunately it didn't.
I'm having issues resolving powering up and reboots automatically going into APX mode. Plus lost my icons (fastboot, wipe, ? ) when powering up w/vol down
button. Only have choice of Recovery or let it cold-boot into ICS. The original help post is at:
Original post with more details
See (lack of) progress below.
Click to expand...
Click to collapse
Well, still need some suggestions/help. I've run:
nvflash -r --download 4 blob.EBT
nvflash -r --download 10 blob.APP
nvflash -r --download 6 blob.LNX
nvflash -r --download 5 twrp2.5.0.0.img
Didn't do anything to fix the APX issue nor get my fastboot icon back. I'm wondering if I should try using
the bricksafe.img file I'd created before - not sure what exactly it contains and if it would be any different.
At this point I'm days away from seeing if I can return the tablet (under a 2 year warranty plan - thought it
was said if they can't fix, get my money back rather than a replacement) and look at something else.
I've read and read and not found anything useful yet and not much on the nvflash backup file use for restoring...
Help!
You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3
Sent from my TF300T using Tapatalk
f69m said:
You could try erasing the misc partition.
I think this this is the right command, but you might have to check the exact command syntax (don't have nvflash handy right now):
nvflash -r --format_partition 3
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash PartitionId 3 or adb's mount point /dev/block/mmcblk0p3? In
nvflash's partition table list, MSC (assuming this is the same "misc" partition) is listed as PartitionId 12...
When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?
Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...
I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!
wha2do said:
Thx & that's the correct syntax, but what is nvflash's partition 3 (misc)? And is this nvflash partition 3 or adb's mount point /dev/block/mmcblk0p3?
When I do a list of partition tables from nvflash, it shows this as type Partition_table and named PT. I did install the Partition Table app
and see where 3 may be coming from, as in the mount point /mmcblk0p3, labelled as MSC?
Looking at other known nvflash/Partition table comparisons, one nvflashes blob.APP (system) to partition 10 yet the Partition Table app
shows /system, labelled as APP mounted on /mmcblk0p1. And with blob.SOS, nvflash sends it to 5 yet the adb command uses /mmcblk0p4...
I maybe interpreting these all wrong and it's ok - just being very cautious about formatting a partition and what effect it will have... Thanks in advance for clarification!
Click to expand...
Click to collapse
Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.
Sent from my TF300T using Tapatalk
f69m said:
Sorry, my bad, haven't really used nvflash much. Just assumed it would be the same numbers. :/
Yes, I mean the MSC or misc partition /dev/block/mmcblk0p3.
It holds commands for the bootloader, for eaxample "recovery", etc. Cleaning it might make your bootloader behave. Might.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:
nvflash --resume --rawdeviceread 317568 512 msc.img
Should back up what's there if need it afterwards...again being safe, lol!
wha2do said:
No problem at all, I appreciate the help and I just always try to be cautious! Just to be doubly sure, here's the excerpt from
getting the partition table info from nvflash earlier today:
PartitionId=12
Name=MSC
DeviceId=18
StartSector=317568
NumSectors=512
BytesPerSector=4096
So doing the nvflash -r --format_partition 12 command should be safe. Wondering, does it make sense to do this first:
nvflash --resume --rawdeviceread 317568 512 msc.img
Should back up what's there if need it afterwards...again being safe, lol!
Click to expand...
Click to collapse
Yes, this looks like the right one. Unfortunately /proc/partitions does not give a start sector, but the name MSC matches. /proc/partitions gives the size at 2048, but that should be 1K blocks, so maching the 512 4K-blocks shown by nvflash.
Yeah, should be save to erase, but being careful and having a backup never hurts. Might even be interesting to have a glance at the contents.
Sent from my TF300T using Tapatalk
Well, I think if indeed the bootloader is corrupted I've found my flashes of a new one aren't taking. I tried nvflashing blob.EBT, blob.SOS, blob.LNX, and then blob.APP from the stock v9.4.3.30
update (all in same nvflash session) and all listed as successful. The rest did take...but wasn't sure about blob.EBT. I expected to see the US_epad version (and I've checked the blobs
with a hex editor and they indeed have the US SKU).
I ended up sideloading v9.4.3.17 in TWRP and saw the bootloader version stayed the same (WW_epad-v9.4.3.30). With a stock recovery back in place, I tried to see if I could take an OTA
back to v9.4.3.30, but said no updates were available. Ended up sideloading v9.4.3.30 and am back to where I was...
I also let the tablet battery run down completely, charged fully over night hoping something might "reset", but no go...
Last thing I'll be trying later is a factory reset via TWRP (read try doing it three times to be sure) and reload v9.4.3.30. If not, looks like I have two options: 1) try the reformat of the MSC partition
and/or do an nvflash rawdevicewrite of the bricksafe.img file. Just worried with both that it'll create more issues (being very careful since at least I can still get into APX, ADB, and ultimately boot up).
Any recommendations/suggestions on how to get blob.EBT to flash successfully or which step to try next? Please, please, please...lol!
I tried doing a factory reset. Probably overkill, but also wiped cache, Dalvik, and data while in TWRP. Then booted up, skipped set up, and did this two more times. Didn't have any effect,
so I tried sideloading v9.4.3.30 and same old story...
I finally quit and restored my nandroid made prior to the factory resets and now have to decide:
Try the format of the MSC partition or nvflash bricksafe.img. Again just being very cautious since while tedious, I can still use my tablet by restarting via nvflash.
Wish I could get advice from one of the AndroidRoot members!!
Any ideas/recommendations at this point?
Hello,
I have interesting situation with my tf700:
- I have all necessary blobs generated for this device earlier
- installed twrp 2.8+
Then one day I wanted dualboot with Linux. In the failed process installer overwrited recovery partition so I get APX mode and used wheelie:
wheelie --blob blob.bin etc
Unfortunatelly one time I wrongly used nvflash:
nvflash -r --download 4 twrp.img (version 3 naivelly to partition 4).
After that, I went into APX again, used wheelie and... TF started to vibrate. I was trying to use wheelie with --unbrick option but with no success (it just doesn't send file to device)
I've used wheelie v0.1 as well as 0.2 from github.
I'm guessing there is no bootloader for apx->nvflash anymore? Am I doomed? Is there any way to fix this?
Please help