Related
What do I have to do to install a custom recovery and get root?
Where do I get the ASUS specific drivers for all of normal, recovery
and boot-loader modes, for adb, fastboot and 'disk drive'?
I can use ADB and fastboot SDK utilities from the Win7 console prompt.
the appropriate dll's and exe's are in windows path.
Are there special things to do like HTC's hboot unlock procedure?
I saw an apk file on ASUS's website for unlock, how does that work?
I found 1-click root script that is supposed to install an CWM
custom recovery and get root for you. Do I need to do anything prior
to running that to unlock the boot loader, so it will accept the fastboot
commands? Besides setting usb debug and any allowing any apk?
I don't know how to interact with the ASUS boot loader for
loading updates. For HTC I only needed a specially named zip
file on the root of the ext sd card and push buttons to start
the process. Is it similar? :fingers-crossed:
Try reading this.
http://forum.xda-developers.com/showthread.php?t=1697227
All of your questions and answers have been posted a long time ago and is readily available for your reading enjoyment. At least make an attempt to research on your own. Reading is your friend....
Sent from my SGH-I777 using Tapatalk 2
OK -- RTFM *sigh*
Can I flash cwm via fastboot w/o unlocking? I just want to root
to be able to run Titanium backup and Root Explorer tools.
Stock ROM is fine, only need cwm to get root.
The device was purchased a few days ago, (waiting for it
to arrive), so its probably .29 or .30 from factory.
I discussed the issues with ASUS and they kept reading
the text of the warning message about unlocking
instead telling me how / what to do to root.
If I understood correctly, after turning off 'fast boot'
and turning on 'USB debugging', I should be able to get the
stock boot loader into fastboot USB mode following the power on
volume button presses, then use fastboot flash recovery to
store the cwm recovery.img in the recovery partition.
I'm unsure what it is that unlock boot loader apk actually does ?
With HTC it was the hboot software version that determined
if fastboot commands were accepted. Perhaps when I actually
have the device, I'll understand better.
With that done, flash the root-signed.zip from cwm to root?
Cavsoldier already advised you to do your own research. All your questions have been answered, both for your first post and your second.
I'm not entirely sure why you seem so determined to flash CWM for root. They are completely unrelated. You only flash CWM when you unlock the bootloader. You do not have to unlock your bootloader to root the device. Just use this thread.
Also not sure why you're asking Asus how to root their product. That's a big no no. Companies don't like when you root their products. Even if the CSR knows how to root the device, they're not allowed to tell you. They'll just read from a script like they did to you.
Honestly, I'm not sure why I'm bothering to answer this. All the info you could possibly need is in the thread that was linked in the second post. All of it, for every question you've asked in both of your posts in this thread. Anything root or ROM related is in that thread. It links to several rooting methods, most of which do not require CWM, let alone an unlocked bootloader. So, basically, why haven't you clicked the link in the second post? Do it.
*sigh* sorry for being dumb
Alright -- I admit I couldn't find the search forum
button on the phone interface. After I looked via a
laptop (so I had the desktop view) it was where I
thought it was.
In any case, I found the utility script debugfs-root-v1.8
which uses all adb commands so it doesn't need to be able
to run fastboot boot loader commands. It looked like the
tricky stuff was being run on the tablet via adb shell
commands and adb control commands. If I understood
it, it leaves the tablet rooted without unlocking the boot
loader. So if I can live without nandroid backups, I can just
leave the OEM stock recovery alone.
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
fuzzynco said:
*snipped*
Is there more to unrooting than removing superuser.apk
and restoring the stock su?
Would installing the current official firmware work
similar to HTC's RUU's and replace everything?
Click to expand...
Click to collapse
To unroot, there's an option in superuser. Installing the new firmware will not wipe data.
Sent from my Incredible 2 using Tapatalk 2 Beta-5
Thank you.....:good:
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.
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.
Hello People of XDA,
I am wanting some advice for my tablet (TF300t). I want to make an NV backup and duel boot this device with Ubuntu or Arch. I have already unlocked the bootloader and I was looking at backing up my NV Items. To add I have not installed any recovery I was looking at TWRP as it seems to be more stable on the Transformer than CWM. I am currently running10.6.1.8 firmware ( I bought it with this pre-installed) and androidroot.mobi says it requires 10.6.1.15.3 I have downloaded this version of the rom and unzipped put it on the flash and went to the settings and tried to update but its failed a few times and I have also downloaded it a couple of times. Also I was wondering about the boot loader and 3rd party roms. I have been reading but this device is a little harder for me to understand due to the complicated nature of what I want out of it.
Thanks for reading and any advice.
Trigger911 said:
Hello People of XDA,
I am wanting some advice for my tablet (TF300t). I want to make an NV backup and duel boot this device with Ubuntu or Arch. I have already unlocked the bootloader and I was looking at backing up my NV Items. To add I have not installed any recovery I was looking at TWRP as it seems to be more stable on the Transformer than CWM. I am currently running10.6.1.8 firmware ( I bought it with this pre-installed) and androidroot.mobi says it requires 10.6.1.15.3 I have downloaded this version of the rom and unzipped put it on the flash and went to the settings and tried to update but its failed a few times and I have also downloaded it a couple of times. Also I was wondering about the boot loader and 3rd party roms. I have been reading but this device is a little harder for me to understand due to the complicated nature of what I want out of it.
Thanks for reading and any advice.
Click to expand...
Click to collapse
As you are upgrading, I suggest to use the latest version 10.6.1.27.5. It works fine for the nvflash tools. Though there seem to be little (or no?) changes between bootloaders 10.6.1.15.3 and 10.6.1.27.5, the latest version is what most ROM developers use for development and testing.
When you unzip the Asus ROM twice, you find a file named "blob". Flash that using fastboot:
fastboot flash system blob
For more detailed instructions, check the sticky guides in the general section.
Sent from my TF300T using Tapatalk
Thank you very much kind Sir, So I shouldn't use the built in OTA updater right? I heard it re-locks some devices boot loaders. Also to duel boot I have noticed you have to install a custom boot loader and I don't want to loose my booting from the newer releases. I think I am going to go on my 4th read-a-bout as a few of the minor details do not much much sense to me. But thanks for the blob update I did try that but not from fastboot thank you for pointing out my error figured it was something stupid
f69m said:
As you are upgrading, I suggest to use the latest version 10.6.1.27.5. It works fine for the nvflash tools. Though there seem to be little (or no?) changes between bootloaders 10.6.1.15.3 and 10.6.1.27.5, the latest version is what most ROM developers use for development and testing.
When you unzip the Asus ROM twice, you find a file named "blob". Flash that using fastboot:
fastboot flash system blob
For more detailed instructions, check the sticky guides in the general section.
Sent from my TF300T using Tapatalk
Click to expand...
Click to collapse
Trigger911 said:
Thank you very much kind Sir, So I shouldn't use the built in OTA updater right? I heard it re-locks some devices boot loaders. Also to duel boot I have noticed you have to install a custom boot loader and I don't want to loose my booting from the newer releases. I think I am going to go on my 4th read-a-bout as a few of the minor details do not much much sense to me. But thanks for the blob update I did try that but not from fastboot thank you for pointing out my error figured it was something stupid
Click to expand...
Click to collapse
Never used that OTA mechanism myself. Using fastboot or flashing the ZIP (unzipped once) using recovery seems so much more natural to me.
For dual-boot have a look at my MultiROM thread, though Linux support is not there yet.
Sent from my TF300T using Tapatalk
Trigger911 said:
Thank you very much kind Sir, So I shouldn't use the built in OTA updater right? I heard it re-locks some devices boot loaders. Also to duel boot I have noticed you have to install a custom boot loader and I don't want to loose my booting from the newer releases. I think I am going to go on my 4th read-a-bout as a few of the minor details do not much much sense to me. But thanks for the blob update I did try that but not from fastboot thank you for pointing out my error figured it was something stupid
Click to expand...
Click to collapse
No I don't recommend using the built in one due to electrical infetterence. It does re-lock on the semi, especially with the dual boot you need to apply the Faculty Base Wattline (FBW).
Here is how I did mine custom, i can post more pictures if you want:
s7.postimg[_DOT_]org/ubm43p7pn/353535jpg[DOT_]jpg[/url]
I am going use the blob to update I will try to post back what I figure out
OK I got it all working the flatline.img will put the bootloader to what it needs to work and I installed twrp and omnirom seems to run a little smoother still reading up about the linux porting tho.
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.