Related
Its a B-70 running 8.6.5.13 US model.
B70, you have a 50/50 chance.
http://forum.xda-developers.com/showthread.php?p=15974068
Sent from my Transformer TF101 using Tapatalk
Use RazorClaw and then RecoveryInstaller, these two are .apk, so it works with just one click from your Tab.
I've rooted mine like this.
jef_k said:
Use RazorClaw and then RecoveryInstaller, these two are .apk, so it works with just one click from your Tab.
I've rooted mine like this.
Click to expand...
Click to collapse
This works only on 8.6.5.19
kys89012345 said:
Its a B-70 running 8.6.5.13 US model.
Click to expand...
Click to collapse
Best way: Update to 8.6.5.19 -specifically- and use Razorclaw.
Anything above .19 and you get stuck, unless your B70 supports the APX mode access ... which frankly I'd test anyway if you haven't already just to be sure if you'll have a failsafe option.
nvflash method worked for my 8.6.5.13 B70
cmdr001 said:
Best way: Update to 8.6.5.19 -specifically- and use Razorclaw.
Anything above .19 and you get stuck, unless your B70 supports the APX mode access ... which frankly I'd test anyway if you haven't already just to be sure if you'll have a failsafe option.
Click to expand...
Click to collapse
Is this possible? I don't recall there being working dlpkgfiles to get to that update available her for the US version of the tablet.
This might be of interest to you
http://forum.xda-developers.com/showpost.php?p=20787530&postcount=115
Yes of course... Forgot to mention it... He must upgrade to .19 before use RazorClaw
I rooted my tablet and it worked fine. I then proceded to modify my build.prop file. My friend sent me his to work from but i mistakenly copied it over directly. Now the tablet will not boot. How can i restore to factory or whatever i need to do?
(please spare me from the "you shouldn't have done that" speech, trust me i know lol)
need more info
what model number do you have, what can you get into, what cant you get into etc
lowgoz said:
need more info
what model number do you have, what can you get into, what cant you get into etc
Click to expand...
Click to collapse
sorry, late night, not really with it lol
its model tf101 US version and it has the latest ICS firmware, stock recovery. i can get it to load the recovery screen with the wipe data option. sorry for my poor terminology im new to the whole android rooting stuff.
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
baseballfanz said:
You can download the latest firmware from Asus website.
Unzip it to get the zip file from inside and put it on your external sd card. Boot into recovery and let it flash the ROM again.
Plenty of thread to show step by step if needed.
You could also try to adb push the original file to your tf
Click to expand...
Click to collapse
i've already tried this. it just gives me the dead android with a red exclamation point. also for some reason my windows pc says "the device cannot start" and im unable to use adb.
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
baseballfanz said:
What is the serial number of your tf?
Hopefully it's one that's nvflash compatible
Click to expand...
Click to collapse
dont think it is, starts with B90
i think the mods rudely removed my post in general forum where i was actually getting some help, but whatever. still need help here if anyone has any ideas.
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
gee one said:
I think you have several options-
1) use adb to fix your build.prop file. This can be done in the rom or recovery. There are adb guides coming out of the woodworks on here. If windows doesn't recognize your device, then get linux or a mac and kick windows to the curb. Nothing but grief.
2) install the correct build.prop via a flashable zip. You can extract the build.prop from the system dump I have in the dev section. Yeah, it's a slow download, but I'm working on something to move it to a faster server.
There's no easy fix... yet. adb will be the "easiest" fix.
Click to expand...
Click to collapse
ok well heres the issue. earlier way early this morning when this first started i was able to adb in, saw it was going in an infinite loop in logcat. now for some reason windows, and i've tried 3 installations of it, says the device cannot start. to me it sounds like something weird with the device. any ideas?
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
roflcopterofl said:
The exact same thing happened to me. I booted into recovery and restored from a nandroid backup. Maybe their is a way you can still install recovery and you someone can lend you their nandroid?
Click to expand...
Click to collapse
i think its too late for that now, adb wont work. im guessing now maybe the recovery isnt working because i had a newer version of the os than i can get a copy of right now. anyone have/know where i can get 9.2.1.17 fw?
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
gee one said:
If he is getting the dead android, it sounds like he has a stock recovery.
regarding adb, if windows won't start, then get a linux live cd. I think rebound128 has a minimal one in the dev section for nvflash rooting, but it will probably work. Or you can download a ubuntu live cd and boot from there.
one other option would be to wait until asus releases the 9.2.1.17 firmware on their site and download that. You should be able to flash it without the dead android. the 8.6.5.21 won't work because it won't let you install to a previous version. You can only install your current version or later. In your case, that would be 9.2.1.17.
At this point, I would say that windows is holding you back. I wish I had a $1 for every person that gets screwed over by windows- I would be as rich as Bill Gates used to be.
Click to expand...
Click to collapse
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
joshcrumley100 said:
im hearing that from everyone i talk to but in this case i dont think its windows thats causing the problem. like i said, i've tried THREE different installations of windows, and none of them pick up the tablet properly, they see "ASUS Android MTP Device" for some reason, and then it says that device isnt working properly. im probably just gonna wait till asus releases the new firmware. that will definately work....right?
Click to expand...
Click to collapse
just tried it on linux, adb wont detect the device, so no luck there. im just hoping the .17 firmware will work on it, if not idk what to do.
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
gee one said:
In linux, with the TF plugged into the USB, what do you get when you type "lsusb" ??
Click to expand...
Click to collapse
it had Asus Transformer or something like that, it had it listed, but thats all. couldnt interact with the device.
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
gee one said:
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Originally Posted by gee one
Perhaps adb/debugging is not activated in the rom?
I think you'll have to wait until Asus releases a new update, although the last update checked the md5 sum of the build.prop file, so if you made any changes it won't flash.
Click to expand...
Click to collapse
Wait so you're saying even after i get the new firmware it still may not work? What a load of BS...
Click to expand...
Click to collapse
Sorry for the confusion- I think the full 9.2.1.17 rom that asus posts on their website will work, as long as it checks the rom version in recovery default.prop. It's not clear to me how it checks the "rule" that prevents downgrading. It's a maybe, but there's still a chance.
sent from my cyanogen(mod) vision
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Edit: Forgot to also ask, am I just an idiot?
badfontkeming said:
Here's some background: After installing JB on my (sorta) new TF300, it hit me: I hadn't rooted it yet! I head over into this thread, which says that the methods provided work for all firmware versions. I have a recent version of fastboot directly from the Android SDK, re-downloaded the recovery.img to ensure that it wasn't corrupt, copy-pasted the commands, checked them twice, and the recovery still won't load properly.
Here's the issue: When I attempt to load recovery, the tablet says something along the lines of "loading recovery kernel", and hangs on that screen for as long as I've left it. So, here comes the question: Is this an issue with CWM that is to be addressed, or do I just have really bad luck?
Click to expand...
Click to collapse
I have the same issue, no fix yet.
untermensch said:
I have the same issue, no fix yet.
Click to expand...
Click to collapse
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
I have the exact same problem so I right there with ya
Sent from my ASUS Transformer Pad TF300T using XDA Premium HD app
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
badfontkeming said:
Thanks for the quick reply.
Fortunately since it's just the recovery, Android itself is fine, so I'll just wait it out and hope for a fix soon.
Click to expand...
Click to collapse
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
I've noticed the same issue, it exists with the latest TWRP flashed via fastboot as well.
The problem with flashing via the terminal is that we don't have root yet, and need a recovery to get it. Looks like the only option is to wait for a fix.
EndlessDissent said:
You could try flashing the recovery from the terminal instead of fastboot.
Make sure you have the correct recovery image, and put it somewhere easy to remember (preferably on the root of your SD card).
Open Terminal Emulator on your tablet, and type (this assumes that recovery.blob is on your SD card root):
Code:
su
dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4
This should get you a working recovery. If CWM still doesn't work, I recommend TWRP. It's much more reliable and easier to use, imo.
Click to expand...
Click to collapse
Yeah... the issue is, the reason I'm trying to flash CWM is so I can get root.
krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
sparky28000 said:
Same for me... is there anything I can do at this time to unbrick it or do I have to send it for RMA?
Click to expand...
Click to collapse
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
krhainos said:
Asus' official stance is, you unlocked the bootloader and since you ruined the tablet due to this -- they won't help you.
However, there's an official Asus representative and I'm going to reach out to him since flashing a recovery is a fairly innocuous thing to do. And there's at least two people now that have unbootable units.
You can try contacting Gary Key or Asus_USA, to see if they can help -- I sent them a PM about my/our situation
Gary Key : http://forum.xda-developers.com/member.php?u=4025695
Asus_USA : http://forum.xda-developers.com/member.php?u=4029265
Click to expand...
Click to collapse
Now there is atleast 3 people since I bricked mine also
krhainos said:
I wouldn't recommend reflashing CWM -- that was the last thing I did prior to it bricking. I'm stuck at the initial Asus logo, no fastboot, and all I have is APX.
Click to expand...
Click to collapse
just curious how are you able to get in APX mode it seems I cant even do that
Drgravy said:
just curious how are you able to get in APX mode it seems I cant even do that
Click to expand...
Click to collapse
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
krhainos said:
If attach via USB then power the device on while holding down VOL+ (instead of VOL-), you'll notice a new device show up as "Unknown Device\APX" in Windows or "Nvidia Corp." under lsusb in Linux. The display will not light up.
The APX interface is used with nvflash. From what I can understand, you need to have backed up several key pieces of information beforehand to be able to use APX on your own. I'm hoping Asus can whip something up that'll let us recover our devices via APX (or some other method unknown to us), otherwise we have some very expensive tea trays.
Click to expand...
Click to collapse
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Drgravy said:
yeah Ive tried all of that several times I cant even shut my tab down I just get the asus boot logo untill the battery dies
Ive tried holding those buttons the screen goes blank for about 2 seconds then the logo comes back
Im guessing mine might be a lost cause
Thats what i get for being so impatient
Click to expand...
Click to collapse
I used the reset hole in place of the power button when fiddling with button combinations. Hold down VOL+, and poke the reset hole with a paperclip and that'll get you in APX mode -- not like it does any of us any good.
I thought I had bricked mine...
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
jdeatsch said:
as well,
Holding down the power/volume down for about 15 seconds caused a normal boot.
Give it a try.
Jim
Click to expand...
Click to collapse
Not working for me at all...
untermensch said:
I managed to get ClockWorkMod to work by swapping the kernel with the one in the from the Jelly Bean SOS partition.
I remembered that there was a firmware update applied to the camera a figured it was causing a kernel panic.
so this is a temporary situation. I have attached my test file.
>>>>>DO NOT FLASH UNLESS YOU UNDERSTAND THE RISK<<<<<
no other instruction will be given on how to flash, this is to prevent noob bricks.
Click to expand...
Click to collapse
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
---------- Post added at 10:46 PM ---------- Previous post was at 10:40 PM ----------
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Weird. When I try to edit this post, I only get 3/4 of the quote and none of my actual post to edit. Anyway...
Just wanted to clarify: not asking for directions. If the file is what I think it is, I know what I'm doing. I just want to know that the file is what I think it is.
It is the Jelly Bean recovery kernel and the ClockWorkMod ramdisk repacked with mkbootimg, then blobpack,
then I added the "-SIGNED-BY-SIGNBLOB-" header with a hex editor. it seems like ADB does not work but I
was able to root with an update.zip
I installed this with fastboot and erased and re-flashed 4 time's before posting to make sure
it would not cause instant brick.
EndlessDissent said:
So, basically, the kernels in the recoveries just need to be updated, and all recoveries will work? I think we should have proper working CWM and TWRP shortly if that's the case.
Also, can you clarify what this "test file" or "test blob" actually is? From the majority of your post, I assume it's a modified CWM recovery, but that is never explicitly stated. Would be good to know exactly what I'm flashing. Not that I don't trust you -- if Cyanogen himself gave me a zip called "test" without telling me what it did, I would hesitate to flash it. I can't open a blob file to inspect it like a zip, so it's even more important in this case.
Sorry if the previous paragraph was kind of nitpickey. I do appreciate you doing this for everyone, and I'm sure others appreciate it just as much. Just saying, "better safe than sorry", you know?
Click to expand...
Click to collapse
Hi, hope somebody can help me with my B70 TF101, rooted but everything else stock.
Earlier this week I received an Encryption Unsuccesfull message, tablet worked fine in the morning, would not work in the afternoon.
I tried a factory reset (volume down & power, but no luck, it starts but then displays the android with red exclamation mark.
After searching the forum I tried to use Easyflasher's unbricking/ flashing stock firmware tool with the latest Asus update for the US, chose SBK2 as it is a B70, Easyflasher showed succes, however when I tried to reboot the TF I receive the unrecoverable bootloader 0x000000004 error .
Anybody have any ideas what went wrong and how to correct this?
Thank you.
AmstelD said:
Hi, hope somebody can help me with my B70 TF101, rooted but everything else stock.
Earlier this week I received an Encryption Unsuccesfull message, tablet worked fine in the morning, would not work in the afternoon.
I tried a factory reset (volume down & power, but no luck, it starts but then displays the android with red exclamation mark.
After searching the forum I tried to use Easyflasher's unbricking/ flashing stock firmware tool with the latest Asus update for the US, chose SBK2 as it is a B70, Easyflasher showed succes, however when I tried to reboot the TF I receive the unrecoverable bootloader 0x000000004 error .
Anybody have any ideas what went wrong and how to correct this?
Thank you.
Click to expand...
Click to collapse
Can you boot in recovery?
Edit: Err.. did you flash the right ROM? Every one that has that problem is on the Prime, not the TF101. See this thread, brick 1b and 2.
No recovery, I can only get into APX.
Used US_epad-user-9.2.1.27 with Easyflasher. Downloaded from the Asus site.
Lethe6 said:
Can you boot in recovery?
Edit: Err.. did you flash the right ROM? Every one that has that problem is on the Prime, not the TF101. See this thread, brick 1b and 2.
Click to expand...
Click to collapse
AmstelD said:
No recovery, I can only get into APX.
Used US_epad-user-9.2.1.27 with Easyflasher. Downloaded from the Asus site.
Click to expand...
Click to collapse
Any other ideas or suggestions?
Is my TF101 now permanently bricked?
Can you flash it again with easy flasher?
Lethe6 said:
Can you flash it again with easy flasher?
Click to expand...
Click to collapse
I tried reflashing with Easyflasher, it shows success, but gives the same error at reboot.
Can you try an older revision of the firmware?
AmstelD said:
I tried reflashing with Easyflasher, it shows success, but gives the same error at reboot.
Click to expand...
Click to collapse
If flashing stock fails again then try following step
Instead of flashing stock rom, Try flashing recovery(TWRP) through easy flash, if that's a success then get into recovery n DELETE/FORMAT internal memory, cache, dalvik and everything under wipe option... down a custom ROM and flash it.. that might work
Sent from my Transformer using xda app-developers app
Lethe6 said:
Can you try an older revision of the firmware?
Click to expand...
Click to collapse
Looking for an older version of the stock to download, no longer on the Asus site. Where else can I find that? Need a US version of the stock.
udupa82 said:
If flashing stock fails again then try following step
Instead of flashing stock rom, Try flashing recovery(TWRP) through easy flash, if that's a success then get into recovery n DELETE/FORMAT internal memory, cache, dalvik and everything under wipe option... down a custom ROM and flash it.. that might work
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
I have tried to flash TWRP, receive success confirmation, but can not boot into recovery, still giving the unrecoverable boot error message.
Any other suggestions?
Looks like you're using an unsigned loader or something... but at this point I'm not sure how to solve this. Maybe try posting in the easy flasher thread, the author might have some ideas. If you want to start learning the more hardcore stuff, you can take a look here, though it's for a different model but can point you in the right direction.
This guy had the motherboard replaced to fix it.
People having the same problem, you should keep an eye out there as well.
Finally, last ditch effort... maybe roll back to 3.0? See the update in this post.
Even though some help/answers are for different models, they can help you think of new solutions or provide generic tools; it's worth looking into.
Thanks for the assistance. I gave up on the tf101 and bought a Note 2.
Lethe6 said:
Looks like you're using an unsigned loader or something... but at this point I'm not sure how to solve this. Maybe try posting in the easy flasher thread, the author might have some ideas. If you want to start learning the more hardcore stuff, you can take a look here, though it's for a different model but can point you in the right direction.
This guy had the motherboard replaced to fix it.
People having the same problem, you should keep an eye out there as well.
Finally, last ditch effort... maybe roll back to 3.0? See the update in this post.
Even though some help/answers are for different models, they can help you think of new solutions or provide generic tools; it's worth looking into.
Click to expand...
Click to collapse
I have the 3G version of Transformer - the TF101G. I was looking for a way to install this unofficial CyanogenMod 10.1 ROM: http://forum.xda-developers.com/showthread.php?t=2010903 from RaymanFX. Conventional method which is through Recovery (first CWM, then TWRP) - did not work - the rom doesn't want to boot. Yet there are many users reporting it to be working fine. Someone then mentioned nvflashing.. While looking for a solution I came across an information that TF101G cannot be nvflashed. Can anyone confirm this to be true?
Thanks,
Peter
trueptr said:
I have the 3G version of Transformer - the TF101G. I was looking for a way to install this unofficial CyanogenMod 10.1 ROM: http://forum.xda-developers.com/showthread.php?t=2010903 from RaymanFX. Conventional method which is through Recovery (first CWM, then TWRP) - did not work - the rom doesn't want to boot. Yet there are many users reporting it to be working fine. Someone then mentioned nvflashing.. While looking for a solution I came across an information that TF101G cannot be nvflashed. Can anyone confirm this to be true?
Thanks,
Peter
Click to expand...
Click to collapse
The current method of nvflashing sbkv2 devices (wheelie) doesnt support the TF101G, so you can't nvflash it.
Mn5612 said:
The current method of nvflashing sbkv2 devices (wheelie) doesnt support the TF101G, so you can't nvflash it.
Click to expand...
Click to collapse
and problably will never supported or? Because i have also a TF101G, and can only enter APX-mode.
Final step was now to RMA it again, so that Asus nvflashes it for me, because they do have the right tools!
So maybe a chance that nvflash will eer work on TF101G?
Probably not, you'll probably have to live without NvFlash if you have a G variant.
hmm but they DO have an APX-Mode!
or doesn't that mean that it is nvflash-able?
If not for what else stands the APX-Mode?
knopper84 said:
hmm but they DO have an APX-Mode!
or doesn't that mean that it is nvflash-able?
If not for what else stands the APX-Mode?
Click to expand...
Click to collapse
It has the ability to be nvflashed, but the bootloader has been locked by a secure boot key (SBK) that does not allow modification. The TF101 was the same, but the SBK for earlier versions was leaked. Transformers released after this date had a different SBK (SBKv2), which wheelie was designed to circumvent. However the TF101G has yet another SBK (SBKv3) which the wheelie developers (RaYman, littlestevie, etc) have said they were unable to circumvent. There's been no news that anybody is working on TF101G nvflashing.
and for what is the APX-Mode necessary?
Only explanation for me is that at ASUS RMA Center they do have these keys and simply flash it with nvflash!
Could that be?
APX mode allows for a complete reformatting/repartitioning of the device and the flashing of custom images, usually its used to repair a bricked device or to install another OS (e.g. ubuntu).
Yes, the ASUS RMA center would most likely have tools with the various SBKs embedded that would allow them to repair the device.
So is there any chance that the keys could be leaked from there? Especaially the last missing SBKV3?
Maybe from a employee? Or could they not see the keys?
knopper84 said:
So is there any chance that the keys could be leaked from there? Especaially the last missing SBKV3?
Maybe from a employee? Or could they not see the keys?
Click to expand...
Click to collapse
The leak would have to come from nVidia itself. The asus center is probably just given tools with the sbk's built-in and that they would be unable to access, so as to keep the keys from leaking.
Given that the tf101 is an older device, with several new versions of the transformer being sold, it is highly unlikely that the keys will be leaked at all.
And why does nvidia hide the keys in generally, and don’t give it to the public?
Ok its their chip but it would help many people who bricked their device to restore it.
I cant see anything that the keys are secret source code or what else. Only keys for nvflash command.
Cant understand nvidia in this matter...
knopper84 said:
And why does nvidia hide the keys in generally, and don’t give it to the public?
Ok its their chip but it would help many people who bricked their device to restore it.
I cant see anything that the keys are secret source code or what else. Only keys for nvflash command.
Cant understand nvidia in this matter...
Click to expand...
Click to collapse
Hi! Have you managed to flash the tab? I ve faced the same trouble - bricked tf101g... can't nvflash ...
olegkons said:
Hi! Have you managed to flash the tab? I ve faced the same trouble - bricked tf101g... can't nvflash ...
Click to expand...
Click to collapse
Can you access Recovery or ADB mode? From there you can do a lot. I have managed to fix my cousin's TF101G by formatting data partition.
My method is written here: http://forum.xda-developers.com/showthread.php?t=2244728
Sincerely,
Žiga
ZigaG said:
Can you access Recovery or ADB mode? From there you can do a lot. I have managed to fix my cousin's TF101G by formatting data partition.
My method is written here: http://forum.xda-developers.com/showthread.php?t=2244728
Sincerely,
Žiga
Click to expand...
Click to collapse
no adb in fact... the tab freezes at 'loading recovery kernel', wipe data also freezes at boot recovery kernel, android boot finishes with asus logo and continiuos circle spinnig with faulted MTP device in windows device manager with USB connected, usual power stops at eeepad logo..APX is available but have no tool to nvflash because of sbk...
Sincerely
Oleg