Related
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 guys!!!, Today I get the new OTA with the firmware 05Q and I install it. I see in the forum a version of 05Q rooted LINK HERE
I only want to ask if anyone know another way of get root actually or if I should wait until our amazing toolkits for 1+1 get updated.
Thanks i nadvance!!! :cyclops:
You can gain root following, This thread. If you already have a custom recovery install, might be easier to install the pre-rooted 05QA. I went the second route.
P.S. That toolkit will root 05QA, just does not have the new firmware to go back to stock.
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Istvan_86 said:
I have a custom recovery installed ofc, if I install the pre-rooted 05Q I lost all my data and apps? Should I do a factory reset? Thanks for your fast answer mate!!
Click to expand...
Click to collapse
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
rraquib said:
If you have custom recovery installed. Do a back up first. You should not have to wipe or lose anything.
Click to expand...
Click to collapse
Really thanks again mate!! I do it, like you, as soon as possible.
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
rraquib said:
@timmaaa Read carefully I mentioned both option and he was wondering about the pre-rooted version.
Click to expand...
Click to collapse
You said that flashing entire ROM would be easier, it isn't. All that's need to get root is to flash the SuperSU zip. He's already on 05Q so flashing the ROM zip is completely and utterly pointless. It's like telling someone who's run out of petrol to install a entirely new petrol tank that's full of petrol (when all that's actually needed is the fuel).
It doesn't matter what someone thinks might be the solution, if you're going to answer in the q&a section you need to give the best and easiest solution.
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
timmaaa said:
Wait guys, all you need to do is flash SuperSU from your custom recovery. That's it, nothing more.
@rraquib, why on earth would you tell him to flash the entire ROM again??
Click to expand...
Click to collapse
+1
only SU from TWRP
plato79 said:
The thing is flashing update-supersu is not working... for me at least. I updated OTA.. After installation finished, rebooted to TWRP and tried to install update-supersuv2.37.zip...
It doesn't show any error, but when I reboot my phone there is no supersu installed ( actually there is one but it's greyed out with android icon and not showing up on application list )
Click to expand...
Click to collapse
Install a newer version
#stayparanoid
Sorry guys for don´t answer your comments, I have been working out of my country for a couple of weeks.
I get root on 05Q with just flashing SuperSU 2.46 from recovery. Easy and fast, just that.
Anyway you have my thanks in your respective buttons.
EDIT: If moe people with doubts read this. I use the info on this post. http://forum.xda-developers.com/showthread.php?t=2788632
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
cesarp3791 said:
Hi! My question is lame, i know.. But here it goes anyway, i couldn't find a simple and direct answer..
Is less than a week that i have this phone, and i've been reading a lot of guides of how to rollback to cm11s.. the thing is i've flashed the latest CM12S signed zip ota through CM Recovery, everything is fine as i'm testing it right now..
My question is: if i want to go back to CM11S (in the case that i don't like CM12S or have some bugs), can i just wipe data / factory reset and cache in CM Recovery, and then flash the cm11s signed zip?
I haven't rooted or unlocked bootloader, is it relatively easy from what i read around here.. but i wondered if i had to go through all those steps (unlock bootloader, custom recovery, and then flash) or just doing the steps mentioned before will work just fine..
Is it better to fastboot flash or through custom recovery is fine also?
Thanks in advance!
PD: I'm also asking what do you think about some other 5.1.1 Lollipop ROM, custom kernel, etc.. I'm kind of a flashaholic and i would be able to install the custom recovery if would be really worth it
PD2: sorry for the bad english, i'm from argentina
Click to expand...
Click to collapse
Just unlock your bootloader now, the longer you leave it the more difficult it'll be to backup your internal storage beforehand. You should really have it unlocked anyway as insurance against anything going wrong with your phone. Once you have unlocked it you can flash TWRP recovery, then the correct procedure to go back to CM11S would be to perform a full wipe (system, data, cache, dalvik cache) and then just flash the zip. As far as custom ROMs for this device go, there are many excellent options to choose from that offer extra customisation that you won't find on the stock ROM.
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
uansari1 said:
Don't we have to flash the firmware prior to flashing back to CM11s to prevent a hardbrick? I'm looking into doing this as well, so I'm just asking for my own clarity.
Click to expand...
Click to collapse
The firmware is contained in the official zip.
Heisenberg said:
The firmware is contained in the official zip.
Click to expand...
Click to collapse
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
uansari1 said:
Thanks! Stupid question, but can you please link me to the official zip? I already have TWRP installed, so it would be nice to revert sooner than later.
Click to expand...
Click to collapse
You'll find them all here:
http://forum.xda-developers.com/showthread.php?t=2906746
Thanks!
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
cesarp3791 said:
Thank you both, i believe that this week i'll have some time and unlock the bootloader and flashing the TWRP recovery right away.. Then i'll see which ROM suits my use (i'm looking to battery friendly and high screen on time, will see the forums accordingly) and start the journey on this beautiful and well supported device
Also, thanks for the clarification of the modems.. Will be looking after that and make sure not to miss that step if required :good:
Click to expand...
Click to collapse
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
uansari1 said:
Once you've flashed the ROM, please do share your results. I am still unsure if reverting from a Lollipop ROM to CM11S will cause issues with the radio and/or a softbrick of the device, as I've read that this "can" happen.
Click to expand...
Click to collapse
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Heisenberg said:
Reverting from Lollipop to KitKat won't brick your device, whoever said that is wrong, and would have caused a brick because they didn't know what they were doing. You do need to make sure you flash a KitKat modem though, otherwise you'll have issues with the prox sensor.
Click to expand...
Click to collapse
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
uansari1 said:
Thanks Timaaa...last question, I'm downloading the latest modem from this thread http://forum.xda-developers.com/oneplus-one/development/rom-stock-rooted-xnph05q-t3027033.
Is this the correct flashable modem file to use, or do you recommend another for XNPH05Q?
Click to expand...
Click to collapse
That modem should be fine.
hi !
few month ago i rooted my nexus5 and installed a custom rom (pure nexus), everything was OK. but today i tried to install the last version of "pure nexus", so i downloaded the zip file, pushed it on the device, launched a flash zip with nexus root toolkit (everything was ok on the screen) but then it restart, and get stuck during the boot (4 small circle rotating...)
maybe i've done something wrong? how can i fix it?
(sorry i'm a noob !)
thanks!
nel0 said:
hi !
few month ago i rooted my nexus5 and installed a custom rom (pure nexus), everything was OK. but today i tried to install the last version of "pure nexus", so i downloaded the zip file, pushed it on the device, launched a flash zip with nexus root toolkit (everything was ok on the screen) but then it restart, and get stuck during the boot (4 small circle rotating...)
maybe i've done something wrong? how can i fix it?
(sorry i'm a noob !)
thanks!
Click to expand...
Click to collapse
Hi!
Congratulations, this is your first bootloop. Nothing to worry about. I guess your problem is due to the fact that you were coming from a lollipop based custom rom. Before you install a marshmallow based custom rom you need to install the marshmallow factory image first. If you're using the nexus root toolkit you can always click on the magic "flash stock - unroot" button. This is the easiest way for you.
My suggestion is to flash the factory image manually with ADB. In this way you'll know the basics of modding and it will be very useful for you in future. If you want you can follow this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vorinc said:
Hi!
Congratulations, this is your first bootloop. Nothing to worry about. I guess your problem is due to the fact that you were coming from a lollipop based custom rom. Before you install a marshmallow based custom rom you need to install the marshmallow factory image first. If you're using the nexus root toolkit you can always click on the magic "flash stock - unroot" button. This is the easiest way for you.
My suggestion is to flash the factory image manually with ADB. In this way you'll know the basics of modding and it will be very useful for you in future. If you want you can follow this guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
thanks for your answer!
alright, after installing a marshmallow factory image, everything was OK \0/
so i was wondering : is it possible to "update" a custom rom without wiping everything? :/ (is that what people call a dirty flash?)
thanks again for your help
nel0 said:
is it possible to "update" a custom rom without wiping everything? :/ (is that what people call a dirty flash?)
Click to expand...
Click to collapse
Yes, that's what "dirty flash" means. It is possible as long as the update doesn't concern an android version. An example is your case: lollipop-->marshmallow.
In facts custom roms (differently from factory images) do not provide boot.img in their zips; they assume you already have installed in your device. The lack of the correct boot.img caused your bootloop
vorinc said:
Yes, that's what "dirty flash" means. It is possible as long as the update doesn't concern an android version. An example is your case: lollipop-->marshmallow.
In facts custom roms (differently from factory images) do not provide boot.img in their zips; they assume you already have installed in your device. The lack of the correct boot.img caused your bootloop
Click to expand...
Click to collapse
oh, ok, understood. Thanks for the precision !
OK so I'm no noob when it comes to rooting anything up to lollipop, but with marshmallow it seems alot more complicated. Can someone with an HTC a9 6.0.1 plz post step by step guide for flashing TWRP? And if feeling generous, root as well? I see all this stuff about patching boot .imgs and other little stuff, and I'm ready to flash TWRP on my sprint a9 and wanna double check before I do...
bdizzle1686 said:
OK so I'm no noob when it comes to rooting anything up to lollipop, but with marshmallow it seems alot more complicated. Can someone with an HTC a9 6.0.1 plz post step by step guide for flashing TWRP? And if feeling generous, root as well? I see all this stuff about patching boot .imgs and other little stuff, and I'm ready to flash TWRP on my sprint a9 and wanna double check before I do...
Click to expand...
Click to collapse
First you have to enable developer options and click enable OEM Unlocking and usb debugging to on. After that visit htcdev.com and follow the steps to unlock the bootloader. After you have an unlocked bootloader, visit the twrp thread for the HTC One A9, it gives you the download link for the One A9. After doing this, download SuperSU. Zip from online and flash it through twrp.
Htcdev: http://www.htcdev.com/bootloader/
TWRP thread can be found here: http://forum.xda-developers.com/one-a9/orig-development/recovery-twrp-touch-recovery-t3257023/page25
Steps to flash twrp:http://rootmygalaxy.net/how-to-install-twrp-recovery-on-htc-one-a9/
SuperSU: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/page43
(Use the twrp flashable one in this case)
Good luck, and feel free to ask if you have any more questions
MGfusion said:
First you have to enable developer options and click enable OEM Unlocking and usb debugging to on. After that visit htcdev.com and follow the steps to unlock the bootloader. After you have an unlocked bootloader, visit the twrp thread for the HTC One A9, it gives you the download link for the One A9. After doing this, download SuperSU. Zip from online and flash it through twrp.
Htcdev: http://www.htcdev.com/bootloader/
TWRP thread can be found here: http://forum.xda-developers.com/one-a9/orig-development/recovery-twrp-touch-recovery-t3257023/page25
Steps to flash twrp:http://rootmygalaxy.net/how-to-install-twrp-recovery-on-htc-one-a9/
SuperSU: http://forum.xda-developers.com/apps/supersu/stable-2016-09-01supersu-v2-78-release-t3452703/page43
(Use the twrp flashable one in this case)
Good luck, and feel free to ask if you have any more questions
Click to expand...
Click to collapse
Ty, Sry I should've mentioned I already unlocked through htcdev, downloaded TWRP and supersu, installed adb & fastboot/drivers on my CPU, etc.
I'm moreso confused with all this wiping / formatting data to disable encryption, + with the system image backup, do I do that before or after I format data, plus I've seen many say to flash super-su by adb side loading it... can't flash it directly from external SD card?
Pretty much that stuff and the correct order to do that stuff is what has me all flabbergasted right now... lol, any advice would be MUCH appreciated
bdizzle1686 said:
Ty, Sry I should've mentioned I already unlocked through htcdev, downloaded TWRP and supersu, installed adb & fastboot/drivers on my CPU, etc.
I'm moreso confused with all this wiping / formatting data to disable encryption, + with the system image backup, do I do that before or after I format data, plus I've seen many say to flash super-su by adb side loading it... can't flash it directly from external SD card?
Pretty much that stuff and the correct order to do that stuff is what has me all flabbergasted right now... lol, any advice would be MUCH appreciated
Click to expand...
Click to collapse
Lol, forced encryption is no fun, I've never had a problem with it on the stock HTC Sense ROM, only when I've gone to cyanogenmod have I had a problem with it, and when you face that problem you would have to format data (factory reset) to access the internal storage through TWRP. However, in the TWRP thread you can find a file call A9 boot image patcher (or something like that, lol) that you flash after flashing cyanogenmod (or any ROM with forced encryption) but BEFORE you boot the ROM, this will install a custom kernel that disables forced encryption. So basically right after flashing any ROM flash the boot image patcher to never have a problem with forced encryption. You shouldn't have to flash a system image backup, I've never had to do that before when formatting data.
And to answer your second question, I have always flashed SuperSU from external SD card, never have done anything else, so basically it is fine to do so.
Hope you find the answers to all your questions, and good luck :good:
Thanks man, I just want the system image backup just in case, like whenever OTA time rolls around. Not planning on flashing cm or anything, just rooting the stock Rom
bdizzle1686 said:
Thanks man, I just want the system image backup just in case, like whenever OTA time rolls around. Not planning on flashing cm or anything, just rooting the stock Rom
Click to expand...
Click to collapse
Oh I see. Well I'm not sure on that one I usually just flash updates through TWRP