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
Related
Soo I guess we are never gonna get NVFlash or any other bootloader unlock method at all?
Only if you can mobilze a million current TF101 owners to convince Asus that you will all "unbuy" your TF101 unless they open up the bootloaders, like people managed to do with the prime.
Yeak. And B70KAS- owners wont really bother to join, because they already have nvflash and all that so they don't care.
The chances looks slim, but not impossibly slim.
Id be willing to spam facebook and email perhaps we should organize something I really want to be able to dual boot ubuntu
Praying for SBKs
jeepjeep2010 said:
Id be willing to spam facebook and email perhaps we should organize something I really want to be able to dual boot ubuntu
Click to expand...
Click to collapse
I hear ya, I'd be willing to do ANYTHING for a working NvFlash.. I have a slider SN: B90 and now its bricked without any usable recovery, and to makethe matters worse, no adb interface access..At this point I'd be willing to PAY so I can use my tablet:crying: again..
Timberwolfhusky said:
I hear ya, I'd be willing to do ANYTHING for a working NvFlash.. I have a slider SN: B90 and now its bricked without any usable recovery, and to makethe matters worse, no adb interface access..At this point I'd be willing to PAY so I can use my tablet:crying: again..
Click to expand...
Click to collapse
No way you can unbrick it using APX Mode ?
Not sure what sort of access you could gain using APX Mode and USB > PC though
*Detection* said:
No way you can unbrick it using APX Mode ?
Not sure what sort of access you could gain using APX Mode and USB > PC though
Click to expand...
Click to collapse
I have a working APX connection to my PC, nVflash does indeed detect my b90 device, BUT any attempt to use any "unbrick" method turns out as an error, for as you may know now the file systems in these devices are encrypted with a 128bit SBK (secure boot key) Which has not yet been cracked, as there are not many B90 users out there to convince ASUS of releasing an unlock key...
But, yeah....I cannot use APX... ;(
Sent from my PC36100 using xda app-developers app
Yea I wasn't suggesting NVFLASH, I know SBK1 are the only TFs unlocked for that, I was just wondering if there was anything else you could do via APX, I don't know if there is, but as that is the only communication you have with the tablet...
Not sure if you can access any file system using APX or not via Linux Terminal commands or something ? Just throwing out ideas
*Detection* said:
Yea I wasn't suggesting NVFLASH, I know SBK1 are the only TFs unlocked for that, I was just wondering if there was anything else you could do via APX, I don't know if there is, but as that is the only communication you have with the tablet...
Not sure if you can access any file system using APX or not via Linux Terminal commands or something ? Just throwing out ideas
Click to expand...
Click to collapse
As far as I know only Nvflash can access the file system, and that is with an cracked SBK..You cannot use it for anything else as far as I know
Hello,
A collegue here at work have a TF101 B70, and he told me he tried every available root methods with no success.
I told him to bring his Transformer, and we tried my method documented here:
http://forum.xda-developers.com/showthread.php?t=1704209
It worked !
Don't know if it will be usefull for anyone but I felt like I had to announce it.
Please report me if it works for you too, and which version of FW and S/N you have.
Thanks,
milo
miloj said:
Hello,
A collegue here at work have a TF101 B70, and he told me he tried every available root methods with no success.
I told him to bring his Transformer, and we tried my method documented here:
http://http://forum.xda-developers.com/showthread.php?t=1704209
It worked !
Don't know if it will be usefull for anyone but I felt like I had to announce it.
Please report me if it work for you too, and which version of FW and S/N you have.
Thanks,
milo
Click to expand...
Click to collapse
With nvflash being available for all TF101 devices, we will always have root, no matter what.
whitekidney said:
With nvflash being available for all TF101 devices, we will always have root, no matter what.
Click to expand...
Click to collapse
Doesn't the nvflash method unlock the device and void the warranty ?
No it doesn't, since the bootloader was cracked and not officially unlocked by ASUS, there's no real way for them to tell. It does no permanent change to your bootloader or APX mode. Nvflash for sbkv2 is in my signature, however, the Tf101G and slider have different bootkeys which have yet to be cracked. Those will have to continue to use exploits. My PERI tool currently works on all devices and firmware (and supposedly the next update) and is a one click root option. You can check it out in my signature.
miloj said:
Doesn't the nvflash method unlock the device and void the warranty ?
Click to expand...
Click to collapse
No.
Rooting voids your warranty too, by the way.
miloj said:
Hello,
A collegue here at work have a TF101 B70, and he told me he tried every available root methods with no success.
I told him to bring his Transformer, and we tried my method documented here:
http://http://forum.xda-developers.com/showthread.php?t=1704209
It worked !
Don't know if it will be usefull for anyone but I felt like I had to announce it.
Please report me if it work for you too, and which version of FW and S/N you have.
Thanks,
milo
Click to expand...
Click to collapse
the link is not working
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 guys, i was looking for more infos about NVflash for TF300 and i came across this post --> http://forum.xda-developers.com/showthread.php?p=31244180.
I know that he is working on a NVflash version for TF300T but maybe the same version it will work on our device too, so i this case i advise you to stay away from Jelly Bean if you are looking an NVflash method.
What's nvflash? Could recover the tablet from brick?
mouse100 said:
What's nvflash? Could recover the tablet from brick?
Click to expand...
Click to collapse
i'll take a crack at an answer. (anyone please correct me if this isn't accurate)
apx mode which nvflash accesses is hard-coded into the chips and is therefor something the end user can't screw up. however, the commands have to be encrypted with (in our case) device specific keys or apx shuts down the usb connection. you can use it to flash or even re-partition all of the internal storage of the device (bootloader, recovery, boot, etc) the bootloader is the important one we want to be able to fix, since you can't boot your device at all (other than apx mode) if it is screwed up. if you have a working bootloader, you can usually recover from any soft brick.
mouse100 said:
What's nvflash? Could recover the tablet from brick?
Click to expand...
Click to collapse
Urrlyx already explained what nvflash is but even if we will have a working nvflash solution for our tf700 i think you will not be able to recover an already bricked device.
So we must follow the procedure before making some rom/recovery change or installation. We get a unique hw key to re-program the original bootloader if I understood correctly.. And this method only works in ics only, not jb.
mouse100 said:
So we must follow the procedure before making some rom/recovery change or installation. We get a unique hw key to re-program the original bootloader if I understood correctly.. And this method only works in ics only, not jb.
Click to expand...
Click to collapse
Here's how it works for the tf201 --> http://androidroot.mobi/2012/07/15/nvflash-for-tegra3-transformer-prime/.
mouse100 said:
So we must follow the procedure before making some rom/recovery change or installation. We get a unique hw key to re-program the original bootloader if I understood correctly.. And this method only works in ics only, not jb.
Click to expand...
Click to collapse
i think the reason you must be on an ics bootloader is because the jb bootloader will only let you flash equal or higher versions. you need to be able to flash the custom bootloader to get the hw keys. once you have those you can flash whatever the hell you want, since you're doing it outside of a running bootloader.
hopefully what xplod is producing will work for tf700 as well, but i wouldn't go betting the family jewels on it.
Hello community,
Well, I'm not sure if it's because I'm an idiot or English isn't my mother tongue (or both...?), but I just can't find out if generating nvflash blobs to make my device "unbrickable" is possible or not?
I'm not sure if this indicates the bootloader-version, but in settings it reads kernel-version 3.1.10-10.6.1.14.10-that8-oc+. So I thought, it would not be possible because I read somewhere else it would just work with [...]14.4 and downgrading the bootloader would be impossible.
Then, a few days later I read this post: http://forum.xda-developers.com/showpost.php?p=51517815&postcount=63 .
Okay, so .8 is more than .4 ... I am confused right now. Will it also work with .10 ?
I don't have this device that long (~14 days) and since for my old TF101 there exists a flashable image which unlocks and unbricks every TF101 device every time without some special bootloader version related things I have not been aware of this issue.
If my device is not able to generate the nvflash blobs to make it unbrickable, what could brick my device? Is it right, if I accidently use settings -> wipe / factory reset from within android (not twrp recovery) this will brick my device? if so, why isn't this option disabled in every custom rom?
Thank you for any advice so far,
regards,
MiM8
MiM81 said:
Hello community,
Well, I'm not sure if it's because I'm an idiot or English isn't my mother tongue (or both...?), but I just can't find out if generating nvflash blobs to make my device "unbrickable" is possible or not?
I'm not sure if this indicates the bootloader-version, but in settings it reads kernel-version 3.1.10-10.6.1.14.10-that8-oc+. So I thought, it would not be possible because I read somewhere else it would just work with [...]14.4 and downgrading the bootloader would be impossible.
Then, a few days later I read this post: http://forum.xda-developers.com/showpost.php?p=51517815&postcount=63 .
Okay, so .8 is more than .4 ... I am confused right now. Will it also work with .10 ?
I don't have this device that long (~14 days) and since for my old TF101 there exists a flashable image which unlocks and unbricks every TF101 device every time without some special bootloader version related things I have not been aware of this issue.
If my device is not able to generate the nvflash blobs to make it unbrickable, what could brick my device? Is it right, if I accidently use settings -> wipe / factory reset from within android (not twrp recovery) this will brick my device? if so, why isn't this option disabled in every custom rom?
Thank you for any advice so far,
regards,
MiM8
Click to expand...
Click to collapse
DId you get my PM ?
lj50036 said:
DId you get my PM ?
Click to expand...
Click to collapse
yes
MiM81 said:
I'm not sure if this indicates the bootloader-version, but in settings it reads kernel-version 3.1.10-10.6.1.14.10-that8-oc+.
Click to expand...
Click to collapse
It doesn't. It says "Kernel version". To see your bootloader version, go to the bootloader menu (Power+Vol-down) and read the text in the upper left corner.
MiM81 said:
So I thought, it would not be possible because I read somewhere else it would just work with [...]14.4 and downgrading the bootloader would be impossible.
Click to expand...
Click to collapse
You could downgrade bootloaders back to 9.4.5.30 if you wanted to. But modern ROMs don't work on such an old bootloader. So yes, you can perform the Flatline procedure.
MiM81 said:
If my device is not able to generate the nvflash blobs to make it unbrickable, what could brick my device? Is it right, if I accidently use settings -> wipe / factory reset from within android (not twrp recovery) this will brick my device? if so, why isn't this option disabled in every custom rom?
Click to expand...
Click to collapse
This option works fine, but only if you have a working recovery. If your recovery is broken or incompatible with your bootloader, it can hard brick your device because it forces booting to the recovery until the factory reset has been performed and the broken recovery won't complete the factor reset. So make it a habit to boot to recovery manually instead (using the bootloader menu and volume keys) and perform the wipe from there - one less chance to brick.
_that said:
It doesn't. It says "Kernel version". To see your bootloader version, go to the bootloader menu (Power+Vol-down) and read the text in the upper left corner.
Click to expand...
Click to collapse
Okay, so then it reads ww_epad-10.6.1.14.10-20130801 in my case.
_that said:
You could downgrade bootloaders back to 9.4.5.30 if you wanted to. But modern ROMs don't work on such an old bootloader. So yes, you can perform the Flatline procedure.
Click to expand...
Click to collapse
Thx for confirming this... makes me hope at least (and thx for your detailed answer in general)