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.
Related
I'm more confused than ever on trying to find the *correct* guide to root my TF300T. The development forum has mislabeled threads, and most guides I found were guiding the root process for a device with a 9.x.x.x firmware. So, that said, can anyone point me to the CORRECT guide so I can root my TF running 10.4.2.17 please? Thanks.
Ramrod421 said:
So first off I totally understand the apprehension. I have rooted a lot thingd and this tablet seems especially technical and convoluted.
First read through this thread:
http://forum.xda-developers.com/showthread.php?t=1697227
1) In that thread download the "unlock bootloader" app, run it and unlock the bootloader. Your device warranty will now be void and it will say "device unlocked" in the top left corner every time you boot it up.
2) Now go to this thread, http://forum.xda-developers.com/showthread.php?t=1845377, scroll down to Part 3 and download the "fastboot + JB recovery" files. Extract them into the Fastboot folder that they are zipped in. There will be two .dll files, an ADB file, a Fastboot file and a twrp.blob file.
3) Turn off your tablet. Once it's off press the power and vol/dwn buttons at the same time. Keep holding them down until you see the screen with "RCK", "android", a usb symbol, and "wipe data". Once in that screen let go and use the Vol/dwn to move the cursor and vol/up to select the USB icon. Plug your tablet into your computer and the computer should recognize it as a "fastboot" device. You can check under "devices and printers".
4) Enter the "Fastboot" folder and while holding down shift, right click the mouse. In the menu you should have the option "open command window here". Select that and it will open a cmd window. Type in the line:
fastboot -i 0x0b05 flash recovery twrp.blob
This will copy the TWRP recovery file to the tablet and flash it. You will see a blue progress bar on your tablet while this is happening. Once that is done type:
fastboot -i 0x0b05 reboot
This will reboot your tablet and you will now have TWRP recovery installed.
5)Once in android again, go to this thread, http://forum.xda-developers.com/showthread.php?t=1668173, and download the "root-signed.zip" file in the second post and copy it to the tablet.
6)Turn off the tablet and boot into recovery by holding power and vol/dwn again. Once at the menu select "RCK" with Vol/up. It will boot into TWRP recovery now. Install the "root-signed.zip" file, reboot and the tablet should be rooted.
At this point I recommend creating a backup in recovery in case anything goes wrong from here on out.
Now you can flash any ROM your heart desires. I recommend CleanROM 2.7. It's fast, clean and very easy to install.
TWRP is easily the best recovery for this tablet. I have had many problems with CWM not installing ROM's properly and causing boot issues.
I hope this help you out. I know it's kind of a mine field of information but it works very nicely.
Click to expand...
Click to collapse
Sent from my Incredible 2 using xda app-developers app
Sent from my Incredible 2 using xda app-developers app
I was just about to link you to the same thing. This process will flash recovery and root your tablet.
d08speed3 said:
http://forum.xda-developers.com/show....php?t=1697227
1) In that thread download the "unlock bootloader" app, run it and unlock the bootloader. Your device warranty will now be void and it will say "device unlocked" in the top left corner every time you boot it up.
Click to expand...
Click to collapse
This is a relatively big deal: while you could root stock ICS ROMs pretty easily, you can't do it on stock JB ROMs without unlocking the bootloader, Once you're unlocked, however, it's a piece of cake.
For the amateurs. Could you elaborate on these steps?
Step (1) (a) which file to download? the .apk for the .exe file?
(b) Download to where (the tablet or onto a laptop/desktop)?
Step (2): (a) Again, download to where? Tablet or laptop/desktop? And extract to where?
Step (3) & (4): This make it sounds like the files in previous steps should be downloaded and extracted to a laptop/desktop?
Step (5) & (6): CleanRom 2.7 is already rooted. Do we need to run these steps? Or can we install CleanRom after Step 4?
Backup: What files to back up? Everything?
Critical Questions:
Do the above steps work for tablets already on Android version 4.1.1 with .29 (or .17) builds?
Sidenote: Last night, my tablets had an ASUS update and it went from build .29 to .17. Is this strange? It's going backward?
I have followed these instructions exactly, but titanium and adaway both cannot aquire root privileges. and reason why?
smokarz said:
For the amateurs. Could you elaborate on these steps?
Step (1) (a) which file to download? the .apk for the .exe file?
(b) Download to where (the tablet or onto a laptop/desktop)?
Click to expand...
Click to collapse
Download the .apk and put it on your tablet. Install it. Run it.
Step (2): (a) Again, download to where? Tablet or laptop/desktop? And extract to where?
Click to expand...
Click to collapse
These files are to be put on your computer. It doesn't matter where you put the directory.
Step (3) & (4): This make it sounds like the files in previous steps should be downloaded and extracted to a laptop/desktop?
Click to expand...
Click to collapse
Yes
Step (5) & (6): CleanRom 2.7 is already rooted. Do we need to run these steps? Or can we install CleanRom after Step 4?
Click to expand...
Click to collapse
These steps are not technically required but I put them in there because then you have a backup copy of stock JB that is rooted.
Backup: What files to back up? Everything?
Click to expand...
Click to collapse
Run TWRP. Press the back up button.
Critical Questions:
Do the above steps work for tablets already on Android version 4.1.1 with .29 (or .17) builds?
Sidenote: Last night, my tablets had an ASUS update and it went from build .29 to .17. Is this strange? It's going backward?
Click to expand...
Click to collapse
This method works for any version.
---------- Post added at 08:32 PM ---------- Previous post was at 08:30 PM ----------
rboutin2 said:
I have followed these instructions exactly, but titanium and adaway both cannot aquire root privileges. and reason why?
Click to expand...
Click to collapse
Have you confirmed that you are truly rooted or are these apps the only ones that can't access the root directory?
So you have to root first in order to do a backup?
No you do not have to root first to do a backup.
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
rboutin2 said:
I have followed these instructions exactly, but titanium and adaway both cannot aquire root privileges. and reason why?
Click to expand...
Click to collapse
I would try and clear the cache and data for supersu under settings>apps and that might make it start working properly.
jerry43812 said:
I'm more confused than ever on trying to find the *correct* guide to root my TF300T. The development forum has mislabeled threads, and most guides I found were guiding the root process for a device with a 9.x.x.x firmware. So, that said, can anyone point me to the CORRECT guide so I can root my TF running 10.4.2.17 please? Thanks.
Click to expand...
Click to collapse
I read the reply's to your Q, but as I have the same build as you I still haven't found one that anyone claims has worked.
You have any success?
Root TF300T
Thank you so very much for that very helpful post. Much appreciated.
After reading your instructions, I'm happy to proceed but may I ask one question first.
I've unlocked my TF300 with the ASUS application.
My build number is 10.4.2.18-20121122. It's a UK model.
Am I safe to use your instructions with this build?
Kind regards
I never obtained root, and since my OP, I've gotten an OTA as well, so it's back to square one in finding a viable root method.
Sent from my LG-P500 using xda app-developers app
I'm in the same boat. Got a 300 for Christmas, bumped up to JB w/o reading here first (yeah...that was dumb). So from looking around the only way to root is to unlock and the only way to unlock right now is via the ASUS tool which - from what I've gathered - will send my serial number to ASUS and void my warranty correct?
A few questions:
1.) does anyone know if work is being done to be able to unlock/relock w/o voiding the warranty? I love root, but I won't do it while in warranty in case something unthinkable happens . I'm not sure how much of this would be true, but can't we use nvflash to download the locked bootloader then find a way to spoof the ASUS unlock authorization? Hell, unless each tablet uses a different signature couldn't we just post the nvflash-able locked/unlocked bootloaders? I'm thinking back to the flash processes from my Tegra2 gTablet. I could be way off base, but it seems plausible with my limited knowledge.
2.) is it possible to root w/o unlocking? I know I won't get CWM/TWRP and the ability to load non-stock ROMs but I can live with that. I'd like to be able to run TiB, ES File - Root, etc though. I thought I saw something about obtaining root w/o unlock, but I can't find it and it might have been ICS instructions.
3.) I take it there's no downgrading back to ICS that would fix this either....
NeoMatrixJR said:
I'm in the same boat. Got a 300 for Christmas, bumped up to JB w/o reading here first (yeah...that was dumb). So from looking around the only way to root is to unlock and the only way to unlock right now is via the ASUS tool which - from what I've gathered - will send my serial number to ASUS and void my warranty correct?
A few questions:
1.) does anyone know if work is being done to be able to unlock/relock w/o voiding the warranty? I love root, but I won't do it while in warranty in case something unthinkable happens . I'm not sure how much of this would be true, but can't we use nvflash to download the locked bootloader then find a way to spoof the ASUS unlock authorization? Hell, unless each tablet uses a different signature couldn't we just post the nvflash-able locked/unlocked bootloaders? I'm thinking back to the flash processes from my Tegra2 gTablet. I could be way off base, but it seems plausible with my limited knowledge.
2.) is it possible to root w/o unlocking? I know I won't get CWM/TWRP and the ability to load non-stock ROMs but I can live with that. I'd like to be able to run TiB, ES File - Root, etc though. I thought I saw something about obtaining root w/o unlock, but I can't find it and it might have been ICS instructions.
3.) I take it there's no downgrading back to ICS that would fix this either....
Click to expand...
Click to collapse
Hi!
You can try to unlock your device with AsusUnlock app ! - is the safe way to unlock bootloader ! ( certainly will void your warranty ! )
I don't think that's cause for concern ...I've unlocked bootloader in the very next day after I bought it ( in august this year )
- so far I think I made five hundred " flash and reflash rom " - ( for testing "custom roms" ) - and the device shows like the first day when I bought it
So, be more confident - the device is not so easily to break , you can install as many "custom roms" as you want - you just have to be very careful about the steps that you make - when you try to install a custom rom !
Good luck ! :good:
regards,
Surdu Petru
Not worried so much about flashing causing issues. I've flashed my gTab more times than I can count. More worried about pre-voiding the warranty should I have any hardware issues. Like my battery life seems to be horrible and it might need sent in for that.
Sent from my ASUS Transformer Pad TF300T using Tapatalk HD
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
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
TwistedPoet said:
Hello everyone. I'm beginning to have a few system problems, (their leader being an overheating system). I'm likely going to have to return the device to Verizon. If so, I'll need to return to stock ROM. I'm running 4.3 OTA and have already hardbricked the device once. I know that with the 4.3 OTA update, flashing options have been restricted. I currently can't put phone in recovery mode. I trip the flash counter and get a message about unauthorized firmware being detected.
That being said, given my situation, is there any tried and true method to return the phone to the original out of the box status?
Thank you in advance for your time and knowledge.
Click to expand...
Click to collapse
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
buhohitr said:
Probably you need to pick the hard brick option, but I give you both:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/showthread.php?t=2586319
------------------------------
HARD BRICK - phone not turn on
http://forum.xda-developers.com/showthread.php?t=2581166
Click to expand...
Click to collapse
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
TwistedPoet said:
I had previously neglected to even attempt to upload the recovery.img. (Huge Oversight). However, I ran it successfully (at least I thought), rebooted the phone into recovery mode and still received same yellow triangle error message.
Click to expand...
Click to collapse
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
buhohitr said:
Now if you able to boot into recovery you need to follow the exact steps here:
SOFT BRICK - able to get to download mode
http://forum.xda-developers.com/show....php?t=2586319
Just flash recovery will not fix the issue.
Click to expand...
Click to collapse
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
TwistedPoet said:
http://forum.xda-developers.com/show....php?t=2586319 - (Dead Link....404 Error)
Please pardon my ignorance but those instructions don't appear to be helpful for restoring the ability to turn the phone on in recovery mode or for getting the phone back to 4.1.2 firmware. Again, please forgive my inability to grasp this.
Click to expand...
Click to collapse
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
That's because there's no way to go back, you are stuck on the 4.3 update.
All you can run is stock 4.3 firmware. It's literally posted everywhere in these forums, and if you searched first you would have found all the answers you needed before you started flashing things that will brick your phone.
This is what you have to do to get a functioning phone again:
http://forum.xda-developers.com/showthread.php?t=2586319
After that, read everything here to understand what you're limited to and what can be safely flashed to the 4.3 update:
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
At last I got to know lot of things from this thread as I'm new to this trade.
TwistedPoet said:
Thanks for that but the title of my post should have indicated that I have done some significant searching. I've already restored the phone to working condition. It was the EZ Unlocker that bricked me. I did neglect in my joy of returning my phone from the dead to flash the recovery.img. I flashed it today and am still unable to get recovery mode. I'm following the SoftBrick guide that buhohitr posted and I'm hoping that I don't find myself in a bootloop afterwards. The second link you provided is very thorough and informative. I bookmarked it for future reference.
Click to expand...
Click to collapse
Update - With some very helpful guides and a little but of explanation, I was able to return to stock ROM, which returned my ability to boot into recovery mode. I also successfully flashed Safe strap Recovery onto my device. After looking at the guide about which custom ROM's can be flashed onto the phone, I'm considering using one but I am a tad hesitant. I know very very little about framework, kernels and modules. So, I guess we'll see. Thanks for the simply excellent links and your time!!!!!
Hi,
I replaced the digitizer in my TF300T, and now I need to run the ASUS touch-tool, to get it to work. However, it's incompatible with Android 4.2 and higher, so I need to flash something older. The problem is, that I cannot find the old bootloader anywhere and ASUS tech support doesn't have it either.
Does anybody have an old backup or something like that? Or maybe there is another way of doing this - if anybody knows, that would be very helpful.
ticorman said:
Hi,
I replaced the digitizer in my TF300T, and now I need to run the ASUS touch-tool, to get it to work. However, it's incompatible with Android 4.2 and higher, so I need to flash something older. The problem is, that I cannot find the old bootloader anywhere and ASUS tech support doesn't have it either.
Does anybody have an old backup or something like that? Or maybe there is another way of doing this - if anybody knows, that would be very helpful.
Click to expand...
Click to collapse
The Old firmwares are located here: http://forum.xda-developers.com/showpost.php?p=33883254&postcount=3
But I'm not sure if you can just flash the 4.1 bootloader and go back to it. There was a method to doing it...Google probably knows :silly: :silly:
Ok, now I'm a bit embarrassed, because it seems the reason I couldn't find anything is I didn't know what I was looking for.
I'm a bit lost - does the firmware file contain the bootloader? My understanding of it was that I need to download the bootloader separately and flash it with Odin, then flash a compatible recovery and ROM (I'm on CM11 now btw). Is that correct?
ticorman said:
Ok, now I'm a bit embarrassed, because it seems the reason I couldn't find anything is I didn't know what I was looking for.
I'm a bit lost - does the firmware file contain the bootloader? My understanding of it was that I need to download the bootloader separately and flash it with Odin, then flash a compatible recovery and ROM (I'm on CM11 now btw). Is that correct?
Click to expand...
Click to collapse
Odin is for samsung :silly: :silly:
With asus, the bootloader is included in the firmware upgrades. But like I said, I'm not sure if you can just flash a previous version to revert. I know it works in some cases, but not all.
cmendonc2 said:
Odin is for samsung :silly: :silly:
With asus, the bootloader is included in the firmware upgrades. But like I said, I'm not sure if you can just flash a previous version to revert. I know it works in some cases, but not all.
Click to expand...
Click to collapse
Well, I used to own a Galaxy S3 :silly:
Anyway, will flashing via fastboot work if I'm on CWM recovery (v6.0.4.5), or do I need the stock recovery? I'm scared to try it blindly after reading all the "bricked tabet" threads...
//Edit
Soooo... nothing seemed to work. I just gave up and sent the tablet to a repair shop, where they actually reprogram the digitizer circuit board. Anyway, thanks, cmendonc2, for trying.
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)