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.
Related
I began with the thread http://forum.xda-developers.com/showthread.php?t=1833212
I intended to unlock the bootloaded( completely successfully) , root( not attempted) , install nvflash (since I read its a must have) and install a rom, because the stocks lags horribly
After unlocking I found my way to http://androidroot.mobi/t3_nvflash/ to attempt getting nvflash.
Two things stopped me. For starters the website says the only version is Transformer TF700: 9.4.5.30r01. Now I have seen on the xda thread referenced above "If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE"
So does that mean I cannot get nvflash.
Secondly, the second prerequisite "Working fastboot binary & all necessary drivers" ????? Maybe I missed it but I didn't see any How-To's on fastboot.
Most important to me is understanding what I am doing. Coming from a galaxy s3, the process here seems different.Now I know samsung and asus are different companies. Its just on the S3, I completely understood, that to root for example....I could flash a rooted stock rom, i could use ODIN for example to flash CWM. Then once I had CWM I could back up, restore, install roms at will
With this tablet i still see there is a place for CWM, but I don't see any mention of ODIN. Then there i fastboot. What is it?
If a BIOS is to a windows PC as a bootloader is to my tablet.(I think that's a fair analogy) Then where does fastboot come in
Thanks for any help
Tjisana said:
After unlocking I found my way to http://androidroot.mobi/t3_nvflash/ to attempt getting nvflash.
Two things stopped me. For starters the website says the only version is Transformer TF700: 9.4.5.30r01. Now I have seen on the xda thread referenced above "If you intend to use NvFlash please STAY AWAY from the 9.4.5.30 UPDATE"
So does that mean I cannot get nvflash.
Click to expand...
Click to collapse
The AndroidRoot bootloader is a hacked version of 9.4.5.30 and it can only be installed if your current bootloader is older than 9.4.5.30, e.g. 9.4.5.26. If you didn't upgrade past 9.4.5.26, you can still get nvflash access.
Tjisana said:
Secondly, the second prerequisite "Working fastboot binary & all necessary drivers" ????? Maybe I missed it but I didn't see any How-To's on fastboot.
Click to expand...
Click to collapse
Fastboot is part of the Android SDK, which everyone who is into hacking, rooting and installing custom ROMs should have installed on their PC. If you are running Windows, you also need some USB drivers.
Tjisana said:
Most important to me is understanding what I am doing.
Click to expand...
Click to collapse
Right. Don't do anything before you understand what you are doing. Helps tremendously to avoid stupid bricks due to known reasons. One of these is: Never choose "wipe data" from the bootloader menu if your recovery is broken, it's known to cause trouble.
Tjisana said:
With this tablet i still see there is a place for CWM, but I don't see any mention of ODIN. Then there i fastboot. What is it?
If a BIOS is to a windows PC as a bootloader is to my tablet.(I think that's a fair analogy) Then where does fastboot come in
Click to expand...
Click to collapse
Yes, BIOS and bootloader are roughly comparable in their role, at least in their role to initialize hardware and to load the operating system. Fastboot is a tool to install an operating system kernel. You can't insert a CD or USB stick into this device to (re)install Android.
Maybe you already know that an Android device has two such kernels - it can boot either into regular Android, or into a small recovery system that is used to upgrade or maintain the main system. The recovery, as well as the Android boot image, can be flashed using fastboot. The most popular recovery for the TF700 seems to be TWRP, but CWM is also available.
NVFlash is lower level, it can do everything that fastboot can do (in a slightly different way), and it can read or write any partitions or raw blocks on your device. It even works if your bootloader is broken - fastboot in contrast communicates with the bootloader.
I bought a used TF300T, 16GB
Unlocked
It has TWRP 2.4.4.0, JB 4.2 bootloader, and EnergyROM 3/28 10.6.1.8
Kernel 3.1.10-g59bc3cb
I was wondering if I should leave it alone, or restore it to factory. Is that even possible?
If I keep it as it is, how do I update?
I knew I should have bought a virgin Asus, lol.
Thanks for any info!
You can restore it to factory by flashing a stock Asus blob in recovery (I recommend using the 10.6.1.8 ROM since that was the last one on your tablet). It will wipe all data, including whatever's on the internal storage. Once you get that set up, flash the OTA updates incrementally to avoid issues (there are only two updates to flash). You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be.
All the blobs you need should be on Asus' website. If you need more help, there are lots of "how to flash back to stock" threads with instructions. Just read carefully, and if you decide to flash a custom recovery when you're done, DO NOT flash one with "-JB" at the end of it or you could brick your tablet. You will need a recovery that ends in "-42". Be absolutely sure, because there are 3 different bootloaders for the TF300, and flashing one from either of the other bootloaders will brick your tablet.
EndlessDissent said:
...You just have to download them (one at a time) and put them in /sdcard/ (that's where you start upon opening the file manager) -- be sure to unzip the downloaded file once, so you end up with another zip, and don't unzip that one. Reboot, and the tablet should notify you of an update. Repeat for the second update, and you should be exactly where you want to be...
Click to expand...
Click to collapse
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
skank_boy said:
That isn't doing anything. Is it because I have TWRP? Should I flash from TWRP?
Oh, I couldn't find the exact restore thread for my tablet
Perhaps you could point me?
Thanks again!
Click to expand...
Click to collapse
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
EndlessDissent said:
That part of the instructions requires the stock recovery, which you should have if you flashed the stock blob as per the first sentence.
Click to expand...
Click to collapse
Okay, I will try again. Maybe three times the charm. Thanks!
skank_boy said:
Okay, I will try again. Maybe three times the charm. Thanks!
Click to expand...
Click to collapse
You've flashed the stock blob in TWRP twice already? You're not flashing TWRP afterwards, are you? I've flashed a stock blob in TWRP, and I had the stock recovery afterwards. Are you rebooting into Android after you flash it?
I tried to flash, it failed....BUT this time it worked (??!!) lol.
Obviously I wasn't doing something right, but I have now. I installed 10.6.1.8, now on to the next in the normal manner.
Thanks again!
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:
33colburn said:
TF700T Bricked "booting recovery kernel image booting failed unrecoverable bootloader error 0x00000000"
bootloader error is 0x00000000
I can gain access to fastboot and atx mode. No recovery though. Need someone to help me. Give me a tutorial if this is possible to fix. Am moderately familiar with fastboot but prefer instructions with the code so I can just copy and paste. I think if I could get a kernel on it I'd be good. And maybe there is hope since the computer sees it. Windows vista x86. tf700t firmware 10.6.1.14.1-20130329 A03.
Thank you in advance.
Cole:crying:
Click to expand...
Click to collapse
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.
Tried Fastboot Kernel/Recovery but Failed
dasunsrule32 said:
Reading is your friend
http://forum.xda-developers.com/showthread.php?t=1926286
Seriously though, you can use those directions to flash the recovery. Replace the recovery-jb-touch.img with twrp or whatever recovery you want to use.
Click to expand...
Click to collapse
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
Tell us what you did that cause this issue?? make sure you stated what software version, bootloader/cwm version during the incident.
33colburn said:
I tried that one. But no go. I will attach pic. Do you have any other ideas? Or now and expert I might PM.
Thank you.
Cole
Click to expand...
Click to collapse
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?
Thank you.
MartyHulskemper said:
I had this too, when flashing with the 700 attached to a back USB port (which is the primary set, should be fine in tiself), but via an extension cable (apparently NOT OK). I really recommend playing around with your ports and cables -- it gained me my NvFlash blobs after an evening of hair-pulling.
What driver(s) shave you been using/trying?
Click to expand...
Click to collapse
I exchanged the tablet for a new one. I still think I could have brought it back from the dead. One of the questions I asked in another thread was "would it be possible to make a blob with my device specific code from a TWRP backup"? I also understand that nvflash can only be used with the 9.x.x.x bootloaders but those are not compatible with Jelly Bean 4.2. Kinda stinks since I would have liked to stayed on a 9.x.x.x bootloader but, AFAIK you have to update the bootloader to 10.x.x.x in order do install Jelly Bean.
I am only asking for the sake of knowledge as I am one who does not like not being able to solve a problem. Also maybe the infromation contained in a TWRP backup file does not go deep enough to rebuild a blob from it to restore your device?
Thanks for the help.
Cole:good:
33colburn said:
"would it be possible to make a blob with my device specific code from a TWRP backup"?
Click to expand...
Click to collapse
You mean a blob for wheelie&nvflash that contains your bootloader? No.
33colburn said:
I also understand that nvflash can only be used with the 9.x.x.x bootloaders
Click to expand...
Click to collapse
Not true. You can only create the blob file for wheelie with a hacked 9.4.5.30 bootloader, and to install that, you must be on a <= 9.4.5.26 bootloader. After you have this blob and the other backup files, you can upgrade to whatever bootloader you want and still use nvflash with your saved blob. Just don't ever lose it, it's your unique key to nvflash.
Hi guys,
I'm a total noob regarding ROMs, root, etc..
My Infinity is getting really laggy, and I really need to bring it to a new life..
I was looking for an ideal CMInstaller situation like i used on my Galaxy Note N7000.. This little app is great cuz it does everything for us and noob users like myself don't need to be afraid to brick their devices..
Is there any really easy solution like this so I can safely flash my TF700?
TIA.
I think the answer is yes and no
I run CROMI-X on this tablet, but recently I download the latest CM and the link provided kept bouncing me to the Playstore to dl an installer app. I prefer to use my recovery, so I did not use it. But that's probably what you are looking for.
The thing is, on this device first you need to unlock the bootloader and push a custom recovery to it before you can even use an installer app. You also need to make sure that you have the correct bootloader installed before you flash the CM rom.
Check out the CM thread in the Development section.
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
madz78 said:
CMInstaller so far is only compatible to most common Galaxy and nexus devices, and htc one.
http://wiki.cyanogenmod.org/w/CyanogenMod_Installer#Supported_Devices
I am honestly afraid to flash my device without assistance because there are so many things to do and none of it seems easy.. I'm bootloader unlocked running stock 4.1.2, and the steps needed to take scare me..
1 - update to stock 4.2.1 (according to what I've read..)
2 - Root
3 - NVFlash
4 - Custom recovery
5 - Custom ROM
I don't even know if these steps are in proper order, but seems that so many things could go wrong.. Could you help me doing this easily and problem free? I need to do something to take full advantage of my TF700.. It clearly isn't working properly on stock.
Thanks.
Click to expand...
Click to collapse
I recently wrote a tutorial on Android Central for people who are new to flashing. Check it out and if anything is left unclear - ask
http://forums.androidcentral.com/as...6920-tutorial-flashing-custom-rom-tf700t.html
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
You don't need to be rooted to flash a custom ROM. You can root from 14.8 as you don't need to go to 14.10. If you are on 10.4.4.18 you are on a really old boot loader for 4.1 and will need to upgrade if you want to unlock and flash the latest ROMs.
madz78 said:
Hi, I read the tutorial and I already have some questions even before i start..
- Can't my device be rooted? I believe I need root for apps to access superuser, and for performance menu (or overclock).
- Where's NVFlash? If NVFlash avoids bricking my device I believe this is a MUST have if I intend to grow and experiment different recoveries, kernels and ROMs.
- My device FW ver. is 10.4.4.18, do I need to update to 10.6.1.14.10 in order to continue, or can i do it from 10.4.4.18 and still take advantage of the loophole Motochopper exploited to gain root on this device?
Thanks.
Click to expand...
Click to collapse
Jeez - where did you dig up this version? I believe that was one of the first JB versions? Yes, Motochopper should work, but: Why root if you can't use Goo Manager to get a custom recovery installed? If that is your goal....
Yes, you can just root the stock ROM, but it does not give you that many options to improve the performance of this tablet. And any custom rom is rooted - so why bother?
To have NVflash is great and a wonderful reassurance and I do flash with greater abandon since I got them, but generating the blobs was the most stressful procedure in my limited flashing experience.
I don't know how comfortable you are with using cmd and fastboot - but I sure was glad to have some experience with flashing recoveries and such before I started it!
Generating the NVflash blobs involves flashing a bootloader and recovery build just for that procedure, so you need to know how to flash those in the first place (and how to flash back to your daily driver recovery/bootloader afterrwards).
There's nowhere for you to go without a custom recovery. Start with that.
I have no idea if the recovery most of us use (TWRP 2.6.1 or 2.6.3.1 - both are fine) works with the BL you currently have.
So I would update to the latest firmware, fastboot TWRP and then install CROMi-X.
You can dive into getting your NVflash blobs as soon as you have TWRP installed - that's up to you.
Edit: sbdags was faster - as usual
So there you have it: You have to update your stock firmware before you install TWRP
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fastboot.
Thanks again!
madz78 said:
Wow guys.. This is why i never flash anything since bada on my Wave..
It's all so technical, confusing and intimidating.. God!!
Click to expand...
Click to collapse
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
Ok. I really need to start understanding this, so, if I got it right, I don't need to root because the custom ROM is already rooted.. Good!
Click to expand...
Click to collapse
See? You got that right already.
Now the hard part. Please be patient and gentle, explain me like I'm 5 yo child.
- If I understood correctly first thing is upgrade FW, but to which FW should i upgrade? 10.6.1.14.10 or 10.6.1.14.8? If custom ROM is rooted, does the FW matter or not?
Click to expand...
Click to collapse
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
- Next comes recovery. Again, which one should I choose? (sdbags your opinion would be really important for me here, considering CROMi-X 5.2.2 is developed by you and the ROM i chose)
- I think I'll leave any ROM questions for later, after i finally understand these first 2 steps.
Click to expand...
Click to collapse
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
Also, regarding NVFlash, what the bleep is blobs? I'm comfortable with cmd but never used fast boot.
Thanks again!
Click to expand...
Click to collapse
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
LetMeKnow said:
What if while you are flashing a firmware and your power supply is reaching 0%, could it be a high risk? :silly:
Click to expand...
Click to collapse
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
berndblb said:
Damn you! I was trying to reassure this chap! LOL
There's no remedy for stupidity - so as a scientist you just ignore what you can't account for, right?
Click to expand...
Click to collapse
Just asked a question and thanks for helping... Hahaha:laugh:
LetMeKnow said:
Just asked a question and thanks for helping... Hahaha:laugh:
Click to expand...
Click to collapse
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
berndblb said:
Yes, a just a little, totally correct but diabolical question.....
Didn't know you had that evil streak in you, friend
Click to expand...
Click to collapse
I am trying to relax from a long day of work and tiring of tweaking my device... I am looking for someone to talk to.. Maybe, I need to give up my device and back to my normal boring life...
berndblb said:
Naaah - if I understood it, it can't be technical Just take your time, read - Google is your friend.
See? You got that right already.
It does not matter. As long as you upgrade to a 10.6.1.x version, your bootloader will be compatible with TWRP 2.6.1 or 2.6.3.1 - see below.
sbdags is currently recommending TWRP 2.6.1. That is the version he included in the bootloader/TWRP package he provides in the OP (Original Post) of the CROMi-X thread.
To elaborate: In flashing custom roms the most important aspect is that you always have a compatible bootloader/recovery combination. You use your recovery to flash roms, bootloaders, kernels, wipe all or part of your SD card - the works.
If your recovery gets corrupted but you can still boot into the bootloader, you can install a new recovery using the fastboot protocol (which provides low level access from your computer). If your bootloader gets corrupted (and the most common cause is the wrong recovery) and you cannot boot into recovery, NVflash is your last chance to recover the tablet because: no bootloader = no fastboot access.
The easiest way to get a current bootloader in your situation would be to upgrade your stock firmware. The risk for something to go wrong is close to negative 1
Then you would download TWRP 2.6.1 for the TF700 from the Teamwin website and use the fastboot protocol to install it to it's proper partition.
Risk level is very low if you can follow the instructions in my little tutorial or in the Minimal ADB Fastboot Tool thread.
Once you have TWRP installed (and you tested that it's working) you could - and this is totally optional - flash the bootloader/TWRP package from sbdags OP. Just to make 100% sure you are on the correct combo.....
A blob is a file - better: an image. Binary Large Object is the origin, I believe. For a technical explanation don't ask me! Go here:
http://en.m.wikipedia.org/wiki/Binary_large_object
If you look into the Asus firmware zip file, inside is a blob and a meta data file (if memory serves me right). The blob is the system image.
Click to expand...
Click to collapse
The Asus blob actually contains the system image, kernel, recovery, bootloader and partition table.
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.