Related
Hello, I am confused. I have heard some people have issues after installing nvflash and then installing a custom recovery. I notice that they are both flashed to the address "0x0b05". Will this cause a problem? For instance, recovery overwrites NVflash or vice versa.
Thanks. Any guidance appreciated
ostar2 said:
Hello, I am confused. I have heard some people have issues after installing nvflash and then installing a custom recovery. I notice that they are both flashed to the address "0x0b05". Will this cause a problem? For instance, recovery overwrites NVflash or vice versa.
Click to expand...
Click to collapse
You do not "install" nvflash. nvflash is a tool that runs on a PC. For using it with the TF700, you first need to flash a hacked bootloader and run a tool to extract a blob file from your tablet. Then you save this blob on your PC and keep it safe. This blob is used with the "wheelie" tool, which prepares the communication with the tablet, so that you finally can use nvflash.
And 0x0b05 is not an address, it is the vendor part of the Transformer's USB ID.
You should read the nvflash-related threads thoroughly, this should clean up some of your confusion. Do not try the procedure before you know what you are doing!
thankyou for clarifying that for me. In this case I have one other question, what are the chances that flashing the bootloader would fail and brick the device?
ostar2 said:
what are the chances that flashing the bootloader would fail and brick the device?
Click to expand...
Click to collapse
It worked fine for me, but for a well-founded answer, we would need some statistical data.
I'd say the chances are greater than 0, but not much, if you know what you are doing. At least I do not know any reports of bricking by flashing the bootloader - all recent bricks I read about in this forum were a result of using some inappropriate way to flash a custom recovery and then trying to wipe data.
_that said:
It worked fine for me, but for a well-founded answer, we would need some statistical data.
I'd say the chances are greater than 0, but not much, if you know what you are doing. At least I do not know any reports of bricking by flashing the bootloader - all recent bricks I read about in this forum were a result of using some inappropriate way to flash a custom recovery and then trying to wipe data.
Click to expand...
Click to collapse
Well, if thats the case poll or survey should be done. Also, I have been back and forth about nvflash and what happens if I flash the Asus jb update after installing the custom bootloader? Will it overwrite the custom bootloader? Thanks.
ostar2 said:
Well, if thats the case poll or survey should be done. Also, I have been back and forth about nvflash and what happens if I flash the Asus jb update after installing the custom bootloader? Will it overwrite the custom bootloader? Thanks.
Click to expand...
Click to collapse
Yes, it will overwrite the custom bootloader. But at that time you should already have pulled your blob and stored it safely on your PC and backed it up multiple times, so you don't need the custom bootloader anymore - it is only required for extracting the blob, not for running nvflash.
Ok, thanks. I just needed to be sure of what would happen. I will install the custom bootloader and recovery, generate blobs and preform nvflash backup. I am still unsure if I want to use the stock ROM with a custom recovery or if I want to use cm10 with a custom recovery.
I am definitly going to use cm10 or cm10.1, custom bootloader with twrp recovery after here that Asus spies on what you do with your tablet.
ostar2 said:
I am definitly going to use cm10 or cm10.1, custom bootloader with twrp recovery after here that Asus spies on what you do with your tablet.
Click to expand...
Click to collapse
Just FYI: CleanROM does not include CMClient and DMClient.
Thanks, I still think I am going to go with cyanogenmod 10.1 when it comes out.
At this point I don't want create $499.99 paper weight.
I have read that nvflash can cause a bootloop. Is this true?
ostar2 said:
I have read that nvflash can cause a bootloop. Is this true?
Click to expand...
Click to collapse
Where did you read that?
Improper use of nvflash can cause all kinds of malfunction, however proper use of nvflash should always be able to repair that (if you have backups).
I read this
d14b0ll0s said:
-----------------------------------------------------------------------------------+
Apps to avoid (causing bootloops etc.)
Beats Audio - see why
Wallpaper Wizardrii - see why
Transformer reboot to recovery - see why
NVFlash = softbrick
CMClient (stock) - see why you should probably
disable it (unless you desire constant surveillance)
LCD Density - see why
Click to expand...
Click to collapse
Here: http://forum.xda-developers.com/showthread.php?t=1764480
_that said:
Where did you read that?
Improper use of nvflash can cause all kinds of malfunction, however proper use of nvflash should always be able to repair that (if you have backups).
Click to expand...
Click to collapse
Also, are there any detailed guides on how install nvflash?
ostar2 said:
Also, are there any detailed guides on how install nvflash?
Click to expand...
Click to collapse
This is the guide: http://androidroot.mobi/t3_nvflash/
Make sure you understand exactly what you are doing before you begin. It's easier to do on a Linux PC because of fewer driver issues.
_that said:
This is the guide: http://androidroot.mobi/t3_nvflash/
Make sure you understand exactly what you are doing before you begin. It's easier to do on a Linux PC because of fewer driver issues.
Click to expand...
Click to collapse
Mainly what I am confused about is this: Do I need any extra blob files to install nvflash other than the ones listed?
I understand that you need to backup the "generated" blob files. If so, where would I get them?
Read the guide again. You do not "install" nvflash, the guide describes the procedure of using a hacked bootloader to extract data (the blob) needed to run nvflash.
_that said:
Read the guide again. You do not "install" nvflash, the guide describes the procedure of using a hacked bootloader to extract data (the blob) needed to run nvflash.
Click to expand...
Click to collapse
I know. When I said install nvflash I was referring to the "AndroidRoot" bootloader.
ostar2 said:
I know. When I said install nvflash I was referring to the "AndroidRoot" bootloader.
Click to expand...
Click to collapse
To install that, you need only the files available on the AndroidRoot site and a working fastboot setup.
Hey everyone. Just wanted to say that I have used these forms a lot in the past with rooting my Droids and phones however I now have the Infinity and I need some advice on how to do the following... I know enough to be Dangerous when dealing with flashing etc on Android so I like to run things by people and get suggestions... So
Currently:
ROOT Original Stock Rom 4.0.3
Kernel - 2.6.39.4
Build - IML74K.US_epad-9.4.5.26-20120720
- Notes: When I first got this when released I used the only rooting option I could find which was some sort of auto command line script.
- I then Installed TWRP via GooManager
- I then UnLocked the Device with the Asus tool they released.
I did that months ago and haven't messed with it since... I have used it more and more lately and its slow in terms or response etc. I see that JB is now out for it. I started to look into CM I believe its called cyanogenmod 10 (it is really that good?) is out. I also see Stock Rooted ROMs.
Here is what I want to do.
1) I have looked and believe that I am able to apply the NVFlash patch so I cant brick my device. What does this actually do and will it mess with my abilities to use Recovery Mangers / Flash Roms / Kernels etc? ... Also if I update the build to a higher number will it take this away?
2) At the time TWRP was the ONLY option for me. How can I remove TWRP and get ClockWork on this? *note I dont care about anything on the device currently.
3) Is installing CM as easy as put the Zip on the SD card and then boot into CWM and install? -- Where can I get the OFFICIAL CM10 download for the infinity?
4) Kernel related - I know that stock kernels dont have the CPU control ability / and also some extras needed for wi-fi tether to fully function does CM come with its own kernel? or Do I have to get it Separately.
5) Basically There are to many guides and posts about what to do its confusing at this point.
I want to Wipe it / Get CWM on there instead of TWRP and Install CM. And if it is safe install the NVFlash.
I will await your guidance. Just past links to what guides to do in order.
Thanks!
bigstack said:
1) I have looked and believe that I am able to apply the NVFlash patch so I cant brick my device. What does this actually do and will it mess with my abilities to use Recovery Mangers / Flash Roms / Kernels etc? ... Also if I update the build to a higher number will it take this away?
Click to expand...
Click to collapse
As long as you don't upgrade your bootloader past 9.4.5.26, you can obtain the required files from your tablet using the procedure described at http://androidroot.mobi/t3_nvflash/ . What it does is described in the dev thread about nvflash - it does not mess with any abilities to flash stuff the normal way.
After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader or even if you erased it. It's a nice low-level way to access the internal storage without requiring any installed bootloader, OS or recovery. Don't ever lose your blobs, they are the only way to enable nvflash.
bigstack said:
2) At the time TWRP was the ONLY option for me. How can I remove TWRP and get ClockWork on this? *note I dont care about anything on the device currently.
Click to expand...
Click to collapse
Easiest way: fastboot flash recovery cwm.blob
_that said:
As long as you don't upgrade your bootloader past 9.4.5.26, you can obtain the required files from your tablet using the procedure described at . What it does is described in the dev thread about nvflash - it does not mess with any abilities to flash stuff the normal way.
After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader or even if you erased it. It's a nice low-level way to access the internal storage without requiring any installed bootloader, OS or recovery. Don't ever lose your blobs, they are the only way to enable nvflash.
Easiest way: fastboot flash recovery cwm.blob
Click to expand...
Click to collapse
1) So Once I follow that Guide I can update my Bootloader to anything even the newest .30 + and It will still be there and allow be to fall back if necessary.... Im on the last parts of the guide nvflash --resume --rawdeviceread 0 2944 bricksafe.img but do I run that in the FastBoot (hold down volume or) the APX (hold up) It didnt work with up trying down now..... Also is there a guide on how to actually Restore to a non bricked device using this?
2) fastboot flash recovery cwm.blob
--figured this out read next post!
*Of course im guessing that once this NVflash is installed its there no matter what I flash or return to stock ?
1) OK I managed to get NVflash installed and ran the last couple commands... Need to find the files to save off
2) I also managed to run the fastboot flash recovery recovery.img to get CMW touch installed and that works..
3) Right now I have the 4.0.3 Stock Still... with the NVflash installed... The Kernel is: 2.6.39.4 and the Build is: 9.4.5.26-....
If I Download a Jellybean ROM or CM10 (isn't this based of jellybean) and Install it I can assume that I can wipe out all my data (which i want)... As for the Kernel / Bootloader .. What if it gets updated to .30 or above? Or That wont matter now that NVflash is installed... I guess basally is NVflash a 1 off... meaning that as long as u can get it installed it will ALWAYS be there even after the updates above to when you could NOT install it?
bigstack said:
When I run the Line for the NVflash i get
C:\adt-bundle-windows\sdk\platform-tools>nvflash --resume --rawdeviceread 0 2944
bricksafe.img
Nvflash started
[resume mode] (it just sits here forever and i kill it)
^C
Click to expand...
Click to collapse
You must run it in APX mode, and you need to run wheelie with your blob before that line.
_that said:
You must run it in APX mode, and you need to run wheelie with your blob before that line.
Click to expand...
Click to collapse
I literally just updated the post above this.. If you could read that and Let me know If what I have done is correct.
bigstack said:
I literally just updated the post above this.. If you could read that and Let me know If what I have done is correct.
Click to expand...
Click to collapse
First save your files. Make backup copies. Post a list of the files that you saved if you are unsure - after you update, it's too late to get more.
Re-read this thread, the guide and the nvflash thread again, they should answer all your questions about nvflash.
To install a custom ROM that is based on JB (which is pretty much all of them), you need to install the Asus JB firmware first to get the latest bootloader. This will overwrite your custom recovery, but you already know how to restore it. Then you can flash whatever ROM you want.
Ok Files that I saved off are screen shot on the attachment... EDIT apparently im not allow to attach files... soo listed
* Also Added note. The driver pack that I downloaded from there site listed the device as a Samsung device in Device manager. However I was still able to enter APX mode and install NVFlash... Not sure if this is a good thing though.
View attachment 1571433
blob.bin
blob.log
bootloader.ebt
bricksafe.img
create.bct
factort-config.img
recovery.bct
unlock-token.img
I have read multiple NVFlash threads and I found * If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE ... Is this only to be able to install it?
If I need to update to the newest Firmware on Asus site wont this be above .30? Also What one on Asus site should I take. I see a ASUS Transformer Pad TF700T Firmware: V10.4.4.23 Only for US SKU (Android 4.1.1) I am in US so I figure that is the right one? Unless someone has a newer one. But will this wipe out NVFlash?
Am I able to update to a JB based rom without losing my NVFlash?
bigstack said:
The driver pack that I downloaded from there site listed the device as a Samsung device in Device manager. However I was still able to enter APX mode and install NVFlash... Not sure if this is a good thing though.
Click to expand...
Click to collapse
Strange, but if it worked, it's good
Just for additional verification, post the content of blob.log, and the file sizes of these 3 files:
bigstack said:
blob.bin
bricksafe.img
unlock-token.img
Click to expand...
Click to collapse
bigstack said:
I have read multiple NVFlash threads and I found * If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE ... Is this only to be able to install it?
Click to expand...
Click to collapse
I already wrote:
"After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader..."
You also didn't "install" nvflash, you just created files so that you can *use* it when you need it. You will be able to use nvflash as long as you have these files, and as long APX mode works - since this is a very low-level mode, you cannot break it unless you have a hardware defect.
bigstack said:
If I need to update to the newest Firmware on Asus site wont this be above .30? Also What one on Asus site should I take. I see a ASUS Transformer Pad TF700T Firmware: V10.4.4.23 Only for US SKU (Android 4.1.1) I am in US so I figure that is the right one? Unless someone has a newer one.
Click to expand...
Click to collapse
10.4.4.23 is obviously newer than 9.4.5.30, and it's the latest one.
Based on your original version
Build - IML74K.US_epad-9.4.5.26-20120720
Click to expand...
Click to collapse
the US firmware is the right one for you.
_that said:
Strange, but if it worked, it's good
Just for additional verification, post the content of blob.log, and the file sizes of these 3 files:
Click to expand...
Click to collapse
blob.log content:
Generating encrypted EBT file 'bootloader.ebt'...done.
Generating encrypted recovery BCT file 'recovery.bct'...done.
Generating encrypted create BCT file 'create.bct'...done.
Generating blob file 'blob.bin'...done.
Adding create BCT to blob file [wheelie]...done.
Adding recovery BCT to blob file [wheelie]...done.
Adding bootloader to blob file [wheelie]...done.
Adding odmdata to blob file [wheelie]...done.
Adding chip id to blob file [wheelie]...done.
file sizes:
blob.bin - 1.87 MB (1,964,842 bytes)
blob.log ~ 1K
bootloader.ebt - 1.79 MB (1,887,968 bytes)
bricksafe.img - 11.5 MB (12,058,624 bytes)
create.bct - 5.98 KB (6,128 bytes)
factory-config.img - 5.00 MB (5,242,880 bytes)
recovery.bct - 5.98 KB (6,128 bytes)
unlock-token.img - 8.00 MB (8,388,608 bytes)
_that said:
I already wrote:
"After you have created your files and stored in a safe place, you can always use them with nvflash, even if you upgraded your bootloader..."
You also didn't "install" nvflash, you just created files so that you can *use* it when you need it. You will be able to use nvflash as long as you have these files, and as long APX mode works - since this is a very low-level mode, you cannot break it unless you have a hardware defect.
10.4.4.23 is obviously newer than 9.4.5.30, and it's the latest one.
Based on your original version the US firmware is the right one for you.
Click to expand...
Click to collapse
Ok I take this as Its ALWAYS there even if I update to later versions.
Next step if to get that downloaded and installed. ( I assume put onto SD then run the update in CWM ?)
*ALSO can a mod take my account out of this limited mode. I cant post links, or images etc. Thanks
bigstack said:
blob.log content
...
file sizes
...
Click to expand...
Click to collapse
Looks fine. Make safe backups of these files, then you should be able to recover from any software-induced brick in the future.
Ah, btw - you should also make a backup of partition 18, just in case. It contains the GPT and it's 524288 bytes. However that one should be identical on all devices (with the same storage size at least), so in an emergency case you could also use a backup from someone else - in contrast to bricksafe, factory-config and unlock-token which are specific to your device.
bigstack said:
Next step if to get that downloaded and installed. ( I assume put onto SD then run the update in CWM ?)
Click to expand...
Click to collapse
Right.
_that said:
Ah, btw - you should also make a backup of partition 18, just in case. It contains the GPT and it's 524288 bytes.....
.
Click to expand...
Click to collapse
How would I go about doing this? what command do I run and from where?
Also was I correct about being able to Update to any build / firmware no matter what version as I always have the NVflash there because I did it before I was on .30
ISSUE
I downloaded and installed the Firmware update.. Installed it Via CWM it went well device was usable. But now I lost root and When I try to Boot to the recovery manager I it trys but then Fails and I get a Droid guy with a Red Triangle.
FIXED: Flashed CWM and then Installed the 3.1.3 Superuser you can download via CWM when normally booted.
bigstack said:
How would I go about doing this? what command do I run and from where?
Click to expand...
Click to collapse
Same environment as in the official guide (tablet in APX mode, etc.). From your PC, enter these commands:
wheelie --blob blob.bin
nvflash --resume --read 18 gpt.img
bigstack said:
Also was I correct about being able to Update to any build / firmware no matter what version as I always have the NVflash there because I did it before I was on .30
ISSUE
I downloaded and installed the Firmware update.. Installed it Via CWM it went well device was usable. But now I lost root and When I try to Boot to the recovery manager I it trys but then Fails and I get a Droid guy with a Red Triangle.
FIXED: Flashed CWM and then Installed the 3.1.3 Superuser you can download via CWM when normally booted.
Click to expand...
Click to collapse
You need to read more carefully. The first question has already been answered in this thread multiple times. Also the issue with the lost recovery should not have surprised you, because I told you about it before.
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
also in the bootloader i can see this
Code:
Key driver not found... Booting OS
Android cardhU-user bootloader <1.00 e> released by "WW_epad-10.6.1.8-20130225" A03
matt95 said:
Hello guys, as the title suggest i can't mount any partition on my tab...
i'm using TWRP 2.4.4.0 and i'm on the 4.2 JB bootloader...
what should i do to get it working again?
Click to expand...
Click to collapse
As long as you can use fastboot, replace it with the version that works on your bootloader:
TWRP 2.4.4. 0-4.2.
CAREFUL: A lot of people bricked their tablets in this state.
Read one of the many threads on this particular issue.
Sent from my TF300T using Tapatalk HD
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
matt95 said:
i've tried to flash the new recovery but it remains always the same, for instance i've flashed the 2.5.0.0 4.2 version but every time i boot into recovery it says TWRP 2.4.4.0 (which is the one i had before)
Click to expand...
Click to collapse
Weird.
Are you using fastboot to flash?
What messages are you getting from fastboot?
Sent from my TF300T using Tapatalk HD
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
matt95 said:
Code:
ERROR: could not get pipe properties
and then it flashes it correctly but nothing seems to change
Click to expand...
Click to collapse
OK, so flashing fails silently for some reason.
Do you see the blue flash bar on the bootloader screen, when fast boot says "writing"?
Never had any fastboot issues on Linux, but I have seen lots of people having issues with drivers on Windows. If you are using Windows, you might want to read up, how to make sure you have the proper drivers installed.
Short of that, no idea. :-/
Maybe can you post the full output of fastboot?
Should not be more than a couple of lines, right?
Sent from my TF300T using Tapatalk HD
i'm not at home now, i'll post them as soon as i get to it...
anyway i used MacOs, Linux and Windows
Make sure you're using the newest fastboot. There may be a bug on your current version.
Back in August I soft-bricked my tablet - no recovery and no ADB access. Fastboot would turn on on the tablet, but fastboot on my computer (Debian) kept hanging on "waiting for device". I had used fastboot on the same computer a couple weeks earlier to flash a recovery, and lsusb showed all the correct device info, so I thought fastboot was broken on the tablet and I was SOL. Well, fastboot got added to the Debian repos at some point, and I installed that version. 8 months and 2 fastboot updates went by before I even attempted to fix my tablet again (2 weeks ago), but somehow it worked, and I now have an awesome tablet to play with. I have no idea what happened with fastboot when my tablet first bricked, but I can only assume that one of the fastboot updates fixed a nasty bug that only showed up when I bricked the tablet.
I know your device is being recognized by fastboot, and your situation is much different than mine was, but you could be experiencing a completely different bug.
EndlessDissent said:
Make sure you're using the newest fastboot.
Click to expand...
Click to collapse
Good point!
matt, any progress?
http://forum.xda-developers.com/showthread.php?p=40809070
mb it will help you
sorry guys today i was very busy, i'll try to solve it tomorrow
matt95 said:
sorry guys today i was very busy, i'll try to solve it tomorrow
Click to expand...
Click to collapse
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
CBank said:
In your bootloader, what version of ASUS firmware does it say you are running. It makes a big difference for which version of TWRP you should be using.
edit:
sorry in your first post i could see you listed it, I think you may be getting this besause you dont have the TWRP version for 4.2 jellybean. the versions that are compatible are labeled -4.2 at the end.
here is the link for the right twrp for asus firmware 10.6.1.8 - http://techerrata.com/file/twrp2/tf300t/openrecovery-twrp-2.4.4.0-tf300t-4.2.blob
Version 2.5.5.0-4.2. of twrp is only compatible with the update for our tab that came out last week-asus firmware 10.6.1.15.3
Click to expand...
Click to collapse
at first i didn't install the correct TWRP but now i can't even flash the correct one that's my problem
I believe this may be the same issue that alot of devices suffered from when the 4.2.1 update first came out.
Here is a thread on the issue
http://forum.xda-developers.com/showthread.php?t=2179874
From what I understand it seems that the 4.2.1 bootloader changed the way that the partition table was setup and thus all previous versions of custom recoveries could not mount any partitions (twrp would ask for password & not be able to mount any partition & cwm also not able to mount any partition) and a new twrp-4.2 version had to be made specifically for the 4.2.1 bootloader.
Still not sure as to why this caused the fastboot issue with the majority of people that flashed an incompatible version of twrp or cwm.
The fastboot issue I am talking about is that when you use the "flash" command everything will seem to go fine , it will say writing... and successful on the command prompt but you will not get any blue progress bar on the tablet itself and after the flash command has completed the fastboot reboot command will not reboot the tablet. Which I find very odd as other fastboot commands will still work without issue.
The only know solution if this is the issue you have is to replace the motherboard.
pjc21 said:
The only know solution if this is the issue you have is to replace the motherboard.
Click to expand...
Click to collapse
bad news
matt95 said:
bad news
Click to expand...
Click to collapse
Well, don't give up yet. That there is no known solution does not mean we can't find any.
If fastboot is broken, can you access via adb, while in recovery?
Also there was a thread on unbricking with fastboot issues. Might try that:
http://forum.xda-developers.com/showthread.php?t=2236885
Sent from my TF300T using Tapatalk HD
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
matt95 said:
i'm able to use adb and also fastboot commands... the recovery however do not work obviously because it isn't the right one... i'm here on xda since 2010 and i still make such mistakes stupid me
Click to expand...
Click to collapse
Just shows that it can happen to the best of us!
Why don't you try the method from the thread in my last post?
Seems the guy had the same issue with fastboot and solved it.
Sent from my TF300T using Tapatalk HD
i'll definitely try that method! i'll let you know, thanks guys
matt95 said:
i'll definitely try that method! i'll let you know, thanks guys
Click to expand...
Click to collapse
I'm in the same situation that you're in. I can send simple fastboot and ADB commands to the tab but as soon as I try to write anything, it just freezes and requires a hard reset. You'll find that you will be able to erase and send simple reset/info request but no write commands. You'll be able to erase your recovery partition but you will not be able write anything new to it. Good luck!
I ordered a MB from ebay last night. Now I just need to find a guide on replacing it.....
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Chazzfazzle said:
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Click to expand...
Click to collapse
Haven't you seen This coming in?
Chazzfazzle said:
So I have a noob question for the experts here. I generated my blob and bricksafe image and related tokens. I just can't figure out how to use them to unbrick the tablet. Got the pinwheel of death after updating bootloader and installing cleanrom inheritance. Tried the recommended downgrade method but no luck. TWRP still works like a champ as well as fastboot and APX mode and I can still get into nvflash. Just don't know how to "flash" the images and tokens to get moving again. I looked through thread after thread telling me how to generate but not one to install or use. If there is and I missed it please do point me to it. Any help is appreciated. Thanks in advance.
P.S. Long time lurker but this is my first post. Quite the place you have here.
Click to expand...
Click to collapse
If your TWRP, fastboot, and adb are still working, then your bootloader and custom recovery are still good.... You may want to format your data partition and wipe everything on your internal SD and then flash your custom ROM again... You may need to check that your TWRP and your bootloader are compatible before installing the custom ROM... Good luck..:fingers-crossed:
graphdarnell said:
Haven't you seen This coming in?
Click to expand...
Click to collapse
I did but I disregarded it since it was done in Linux. I will give it a try though and change commands where needed. Thanks for the reply.
I don't think you need to use the nvflash files as you are not bricked. If you have a spinning wheel and can get to TWRP then make sure you flash the booloader package in the first post of CROMi-X first, reboot and then flash the rom again.
Chazzfazzle said:
I did but I disregarded it since it was done in Linux. I will give it a try though and change commands where needed. Thanks for the reply.
Click to expand...
Click to collapse
You know that you have to boot back into system after flashing the bootloader, do you?
The sequence is:
flash bootloader in TWRP
reboot system
boot back into TWRP
flash rom
I have an Asus TF300T that I have unlocked, and flashed TWRP 10.6.3.1 onto it. I have then flashed the latest 4.4 Cyanogen nightly, and it bootloops. I think this is because of my bootloader.
Normally once I am at the custom recovery point on a device, I have no further issues and flash rom's like crazy. This specific bootloader requirement is new to me. I've farted around on a few devices before (Moto Milestone, HTC Desire Z, HP Touchpad, Sam GS3), but I'm not very technical.
I think my current bootloader is 10.4.2.18. (It reads Android cardhu-user bootloader <1.00 e> released by "WW_epad-10.4.2.18-20121122" A03).
How do I upgrade my bootloader to allow for 4.4 rom's, and must I downgrade my bootloader if I want to install something like Ubuntu?
The instructions mentioned here http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7 took me to http://forum.xda-developers.com/showthread.php?p=49258989 but neither of these post's seem to be talking about the bootloader. Is there a way to simply upgrade just the bootloader? Or must I flash a special stock Asus rom that upgrades it for me, then reflash TWRP and proceed from there?
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
jiddahidda said:
I think I may understand. I've downloaded the latest firmware update from the Asus website. Is this zip flashable within TWRP? Or can I simply fastboot the blob within the firmware zip? If so, what would the command be?
Click to expand...
Click to collapse
Use fastboot to install the latest stock blob. Remember to extract the blob file:
Code:
fastboot -i 0x0B05 flash system blob.blob
Then you can flash TWRP 2.6.3.2 and then a KitKat ROM.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
cmendonc2 said:
Code:
fastboot -i 0x0B05 flash system blob.blob
Click to expand...
Click to collapse
Is there another way to get it into fastboot mode? See my post above this one.
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
jiddahidda said:
I can get into APX mode. Can I fix this using APX mode? I'm googling around but I'll wait for word from you before doing anything, I don't want to make this worse.
Click to expand...
Click to collapse
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
I seem to have lost the ability to get it into fastboot mode to apply your instructions. Is it bricked if it bootloops, and I cannot get into that bootloader screen by holding down the volume down button? Your instructions are straight forward but I haven't had a chance to try them yet because of this new issue. So does this sound like it's bricked?
Click to expand...
Click to collapse
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
cmendonc2 said:
You cannot use APX mode unless you have already made NvFlash Backups. IF you made then, you can recover using that method.
Click to expand...
Click to collapse
I think I know the answer, but I'll ask anyway. Is it possible to use someone elses NvFlash backups? I looked into making these backups but never did it .
cmendonc2 said:
Yes, that does sound bricked. What you can do is look up Buster's recovery script and try using that to recover. It should be in the General Section.
Click to expand...
Click to collapse
I've seen you suggest this script several times in several threads, but could never find it. I've been searching for threads with the word Buster or Recovery or Script and I can't find anything that seem's to be what you're talking about? Sorry to be a pain, what's his XDA username?
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
jiddahidda said:
I think I've found it, but it relies on getting into fastboot, which I can't do. I stumbled on this post earlier while panicing when it first bricked. I think I'm screwed .
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
Yes, but did you try using the paper clip to reset it? try a few combinations of using it.