I have not rooted my phone yet and previously come from using nexus devices.
I'm on stock lollipop rom and was wondering how I should proceed.
step one would be backing up the TA partition.
following that, unlock the bootloader. After that I was wondering if I need to downgrade to kitkat to continue or if I could flash a kernel with twrp and try to get into twrp, wipe everything and flash cm12.1 + gapps + supersu and proceed from there.
My question is, do I need to downgrade to kitkat stock to proceed or is there a way for me to gain recovery and flash a rom without downgrading?
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Richy99 said:
you will need to downgrade to KK to get root access then install a stock rom that had been pre-rooted for lollipop, you don't have to unlock the bootloader but if you do then you can use a kernel that has recovery built in
Click to expand...
Click to collapse
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Arju007 said:
But to flash a rom one does not need root, just recovery, or am I wrong there? Wouldn't it be possible to flash a kernel using fastboot just to gain access to twrp (I know that would cripple the stock rom), and then wipe everything and then just go ahead and flash cm12.1 using a microsd card?
I might be totally wrong. If there is not other way I guess I need to downgrade.
Oh and my end goal is to flash cm12.1.
Click to expand...
Click to collapse
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
gregbradley said:
But you cannot flash a kernel with a locked bootloader, and you cannot backup the TA without root...
So, you need to root before unlocking the bootloader.
So, downgrade to KK FW .93, root, backup TA partition (If you are going to unlock the boot, otherwise there is no point), install recovery, flash a pre-rooted lollipop rom.
No need for unlocking the boot at all unless you want a custom kernel
But if you want CM12,
downgrade to KK FW .93, root, backup TA, unlock boot, install a recovery of your choice either by a LB way (e.g. dual recovery) or by fastboot a boot.img, flash CM12.1
Click to expand...
Click to collapse
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Arju007 said:
Ah I see, root is needed to backup TA partition.
I know my bootloader needs to be unlocked as I flash Cyanogenmod 12.1 on it. I fell more secure using fastboot soo I'll probably go that way.
So to downgrade, do I use flashtool and find a kk fw .93 ftf file to flash? If I understand correct, this can be done without unlooking the bootloader.
Then from there I'll have to root with looked bootloader, backup TA partition and then unlock bootloader, and then flash kernel with twrp and then proceed to flash cm12.1 or anyother custom rom.
(Sorry If my question is a mess).
Click to expand...
Click to collapse
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
There are plenty of reasons to flash it, only one of them is if it is stable....
gregbradley said:
Yes that's the way,
Downgrade to FTF ending in .93 using flashtool, root using griefroot, backup TA using backup TA tool, unlock boot, fastboot a kernel, flash CM12
Click to expand...
Click to collapse
Thank you! Makes much more sense now.
ondrejvaroscak said:
If u read the CM12 thread there is no way why I would flash it. It is more or less unusable.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Well there are unofficial builds with fixes from members who has the Leo build. The official one does not have all fixes as of yet. There are cm12.1 unofficial builds out now. Being able to test out the latest and greatest is the beauty of it.
gregbradley said:
There are plenty of reasons to flash it, only one of them is if it is stable....
Click to expand...
Click to collapse
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
For some its a first step into something new, it is always a learning curve. Some just like to have the "latest" version.
ondrejvaroscak said:
I agree, development, testing etc. I was more wondering why people experiment with such ROMs when they lack basic knowledge about flashing, TA etc. But it's a bit OT.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Arju007 said:
Coming from a different device does not mean that one does lack basic knowledge. I previously used lg g2 and prior to that I used nexus 5, nexus 4 and older devices. All could be managed using fastboot. Those phones does not have drm keys that needs to be backed up. Hence I did not need that knowledge.
Either way, thank you for enlightning me. I felt to ask here in Q&A section rather than being sorry about not asking.
Click to expand...
Click to collapse
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
ondrejvaroscak said:
OK. Sorry for being a bit too sceptical. Sometimes it is frustrating here with all the same questions and stories of ignorance seems not your case.
Sent from my D6603 using XDA Free mobile app
Click to expand...
Click to collapse
That's fine, I totally understand you! Hope to be pro xperia user soon haha :silly:
@gregbradley Had a noob moment here and now I'm stuck. I tagged you incase you would know how to help me.
So I downgraded to .93 kitkat. All worked well.
Then I managed to root it using giefroot. All worked well.
Then I installed xzdualrecovery. It booted into twrp, I wiped everything beside internal storage and tried to flash cm12.1. I received an error.
I forgot to unlock the bootloader (ofcourse).. which is the mistake I did.
So now I'm stuck. When I turn on the phone the sony bootsplash screen comes on and it does not go past that, due to my device not having a rom.
I tried holding down the volume key and plugging in the device to my computer. My computer does not recognize what device it is but it does make a notification sound saying that I have connected a device to my computer. Fastboot doesn't work on lockedbootloader as far as I know. The flashtool recognizes the device as a flash device for around a minute when connected to the computer using volume down. After a minute my device just turns off and on leaving flash mode. So that's the current status.
Do you or anyone else have any suggestions to how I can revive my phone?
and yes I know, I feel like a noob!
Never mind, I gave it another go with flashtool and managed to get it boot!
and yes, I feel like a pro!
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
gregbradley said:
Don't forget to backup the ta patition before unlocking the bootloader.
Also no need to wipe system when flashing
Click to expand...
Click to collapse
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
Use NDRUtils app to boot to a different recovery
Or just press volume up when the phone vibrates twice when you are booting it to get to CMW
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
/edited
i would wipe really everything despite usb otg and external sd card in advanced wipe of twrp before succeeding.
tell me if that works for you
um, i read you already had that issue again even after unlocked bootloader, try flashing a rooted lollipop .zip in recovery.
and then try wiping and flashing cm12.1 again if a full wipe (also sdcard) doesn't work
---------- Post added at 01:55 PM ---------- Previous post was at 01:51 PM ----------
Arju007 said:
I backed up TA partition 3 times. I've been getting error in twrp when I try to flash cm12.1. I did infact wipe everything even system. could that be the reason for me getting an error in twrp? (can't currently remember what the error was but i wasn't able to flash it.). Is there some problem caused by wiping system?
I finally understand Flashtool and have no problem using it. I also have tested restoring ta partition so I know how stock sony works now. It's just custom roms I have trouble installing. I've been using xzdualrecovery and that recovery pushes me automatically to twrp after I install it. Is there some other recovery i should use instead?
Click to expand...
Click to collapse
well, as you wrote me in pm you did mount "system", just do nothing in the mount menu after entering recovery. i also never did that.
Related
Q&A for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROOT] Root for SHIELD Tablet 2.0 (Lollipop). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
UK Root?
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
DazEB said:
Wondering if i should try root since im in UK.
Heres the boot.img from the UK update, is it any different from the NA version before i try root?
EDIT: Wont let me post outside links
Should i try it or no?
Click to expand...
Click to collapse
If it is the WiFi Only model it should work, but no promises. If it is LTE please PM the link to the boot.img
Cwm and future ota
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Sweet, I followed the "Locked bootloader" method step by step and it working perfectly, no problem whatsoever. Thank you very much!!
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
Cwm had not prevented any OTAs on the shield tablet for me yet.
Sent from my SHIELD Tablet using XDA Free mobile app
Hi,
Thanks for the instructions. I followed the unlocked bootloader one, but now I cant boot. I flashed the modified LTE boot img and now everytime I boot it keeps going into fastboot mode.
Unlocked bootloader
flashed CWM
Booted into CWM and flashed SuperSU Beta
Selected Yes to fix Root
Reboot system
Boot back into fastboot and flash the modified boot.img
Reboot system...............now keeps booting into fastboot.
Please help.
EDIT: I'm an idiot. Unzip the boot.img before you flash it. Problem solved.
layanto said:
Does CWM prevents future OTA? What if I want root but stock recovery? Thanks.
Click to expand...
Click to collapse
You can also restore stock recovery afterward by flashing this
SuperPichu said:
You can also restore stock recovery afterward by flashing this
Click to expand...
Click to collapse
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
layanto said:
Possibly dumb question, but is the stock recovery on 4.4.2 KK the same as stock recovery on L? If I backup the stock recovery on KK with flashify, can I then restore once I am rooted and on L?
Click to expand...
Click to collapse
You can definitely restore it if you make a backup. I'm actually not sure if they are the same.
Can this be done without a computer?
Jaybenosa said:
Can this be done without a computer?
Click to expand...
Click to collapse
No
Sent from my SHIELD Tablet using XDA Free mobile app
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
So I failed miserably, accidentally hit reboot system after step 4 so now I'm on lollipop not rooted and no unlocked boot loader nor have a recovery ??
Jaybenosa said:
Yah I figured. So I'm pretty much a noob and I'm trying to unlock my bootloader right now but I'm so lost lol
Click to expand...
Click to collapse
This is how to unlock the bootloader. It will erase all your userdata.
https://developer.nvidia.com/sites/...eld/SHIELD_tab/HowTo-Flash-Recovery-Image.txt
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
KentuckyHouse said:
In reading through the other thread, I can't seem to definitively find what I'm looking for.
My Shield has a locked bootloader, but I've installed the OTA. Is my only option to unlock the bootloader and then follow the unlocked bootloader root method? Or is there a way to root only (I'd like to keep stock recovery) with the OTA already installed?
Click to expand...
Click to collapse
You will have to unlock. You can restore the stock recovery afterward if you wish
Sent from my SHIELD Tablet using XDA Free mobile app
Does towelroot still work for the LTE devices when moving to lolli?
OK, so I had to unlock my bootloader since I'd already taken the OTA.
Now I'm at this point. I can't seem to get recovery to stick. I've flashed it multiple times in fastboot and it just won't stick. Now, over in the other thread, someone has asked if I've done the "fastboot flash boot boot-root.img" step yet. This confuses me, as that step comes AFTER you flash recovery, then flash SuperSU with CWM. But seeing as how I can't get recovery to stick, I can't flash SuperSU, and that means I can't move on to that step.
So I guess what I'm asking is, can I run "fastboot flash boot boot-root.img" before "fastboot flash recovery recovery.img"? Will that make a difference? Will it brick my tablet?
I'm all out of ideas here.
Locked bootloader and updated to ver 2.0 lollipop.
Hi there.
I have downloaded and installed version 2 lollipop and I would like root to store my games on SD. When checking the root guide it informed me to download update but not install. I have already installed the update and was wandering if they is a way to root my device still.
Kind regards
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
Do you have a custom recovery or flashed a kernel? You must be 100% stock
Sent from my Nexus 5 using XDA Free mobile app
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
eatcyanide said:
I'm on stock android. The only thing I have changed is rooting it and unlocking it
Sent from my Nexus 5
Click to expand...
Click to collapse
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
eatcyanide said:
Im trying to install Android Lollipop on my Nexus 5, but once it downloads I try to install it and it gets about halfway through the install before an error message appears and my phone restarts. My phone is unlocked and has been rooted before, but it isn't at the moment. Any help would be great, Thanks!
Click to expand...
Click to collapse
rahul9five said:
I am stuck in the same situation. Tried it twice with no luck.
I too rooted my phone with towelroot and unrooted it with superSu.
Did you find any solution? Please do share. Thanks.
Click to expand...
Click to collapse
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
wantabe said:
You either have a modified system file or a file left over from being rooted. The easiest and fastest solution would be to fastboot flash the system image. You could of course flash the factory image.
Click to expand...
Click to collapse
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
rahul9five said:
Well now i remember changing the mixer_path.xml ... Will i have to unlock my bootloader to flash the factory image as i had rooted my phone with towelroot so i didnt have to do it earlier..
Also is it possible to replace the mixer path file with the original one from the internet
Click to expand...
Click to collapse
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
wantabe said:
That sucks! ; ) I've always used the sdk so I don't know a whole lot about towelroot. Your bootloader will have to be unlocked to flash the factory image. If you can reroot you could then use the app BootUnlocker.
I just looked and I don't have the stock mixer_paths.xml anymore or I would link to it.
Click to expand...
Click to collapse
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
rahul9five said:
Thankyou for your efforts and advise. I guess i will just rerrot with towelroot, unclock the bootloader with the app you suggestee and flash factory image..
Btw. Will flashing the factory image unroot my phone and lock the bootloader or is there some procedure that needs to be done to do that?
Click to expand...
Click to collapse
Flashing the factory image or a system image will always unroot your device. Lock the bootloader using the sdk. The command is fastboot oem lock.
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Yea, you can't flash the ota through a custom recovery anymore
Sent from my Nexus 9 using XDA Free mobile app
beekay201 said:
Is there a reason why OP needs locked bootloader? Just leave it unlocked, unless you have a really strong reason to. It will spare you hassles in the future.
That said, after unlocking bootloader, you can (at least, we could in the past) flash the update file through twrp (you just need to fastboot boot twrp.img and then flash the update), that will tell you exactly what file(s) doesn't match. Those are the ones you need to replace back to stock.
Edit: read also http://forum.xda-developers.com/showthread.php?t=2949987. Maybe new selinux stuff is playing funny?
Click to expand...
Click to collapse
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
rahul9five said:
Thankyou.. I am more of a soft modder. Like playing with rooted apps and xposed mainly. I dont see myself flashing a custom rom. Love the stock on my nexus 5. So i dont see the need to leave the bootloader unlocked.
Click to expand...
Click to collapse
Err... I didn't suggest that you flash a custom ROM. Read what I said.
I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*
Hey everyone, I've been lurking around for about two months, from when I picked up this phone. It's still completely stock. Unrooted, S-ON, all that. Well, after the update to Nougat, I've been searching for a way to unlock the bootloader & root. Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
acesavant00 said:
Is it safe for me to use WinDroid Toolkit for the process? Just need a guide for the process, for the most part. I appreciate any help that anyone is willing to offer.
Click to expand...
Click to collapse
Go to http://htcdev.com and make an account, then follow the steps and unlock your bootloader from there. After that you fastboot flash TWRP using ADB, and then use TWRP to flash a root solution. I prefer Magisk.
Alright, just unlocked the bootloader, going through the process of setting up my phone once again. Do you have a link to the Magisk & TWRP programs that I can use? Also, should I put the TWRP file in the same folder as the fastboot files?
I greatly appreciate the assistance you've given me so far, I'm deeply grateful man.
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
try this step by step.. :good:
1.Flash TWRP 3.0.3-8 via Fastboot.. Do not reboot into system, enter into recovery..
2.Do a factory Reset via TWRP.. Do not reboot into system
3.Now flash SuperSU 2.79 SR3.. Reboot into system..
couple of bootloops are common, do not give up for at least 3 bootloops..
It will take a long time to boot as you have done a factory reset..
So be patient and wait for at least half hour..
acesavant00 said:
Okay, so I flashed twrp, then the seSuperuser zip that was linked to in CaptainThrowback's thread. Now my phone is stuck in a bootloop, it won't go past the HTC logo with the red warning letters. What do I do now?
Click to expand...
Click to collapse
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Captain_Throwback said:
Sorry about this - I updated the TWRP thread with the current/preferred root method: MagiskSU.
You need to flash a stock boot.img and then flash the Magisk zip from the linked thread.
Click to expand...
Click to collapse
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
acesavant00 said:
Aw crap, I wish I would have seen this yesterday. I tried to format data & flash one of the stock rooted roms for marshmallow roms for my sprint one a9... now it just hangs at the HTC One logo. I'm gonna assume that I'm screwed until a stock rooted Nougat rom is released for sprint.
Click to expand...
Click to collapse
Can't you just flash the Nougat RUU?
Captain_Throwback said:
Can't you just flash the Nougat RUU?
Click to expand...
Click to collapse
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
acesavant00 said:
I found the post about the Nougat RUU, but the program won't recognize my phone cause it won't boot. I'm gonna try & flash the firmware through TWRP.
Click to expand...
Click to collapse
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Captain_Throwback said:
You don't flash firmware with TWRP. But you can use the SD card method to flash the RUU, which doesn't require a computer.
Click to expand...
Click to collapse
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
acesavant00 said:
Sorry to bother you again, but you wouldn't happen to know a method of extracting the rom.zip from the exe file, would you?
Click to expand...
Click to collapse
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Captain_Throwback said:
[TOOL][LINUX|WIN|MAC][64bit][29-SEP-2016]Universal HTC RUU/ROM Decryption Tool 3.1.0
Run the tool with the -z flag to output a zip to the "OUT" folder.
Click to expand...
Click to collapse
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
acesavant00 said:
Thank you so much, man. The zip is prepped, just gotta charge my phone again to 30%. But afterwards, will I have to go through the unlock bootloader process? If I do, I don't wanna mess up on the rooting process.
Click to expand...
Click to collapse
Your bootloader will stay unlocked.
Captain_Throwback said:
Your bootloader will stay unlocked.
Click to expand...
Click to collapse
Awesome, I appreciate all of the help, man. Sorry again if I annoyed you with all of my incessant questions. Just didn't wanna mess up my phone even further.
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
rilley said:
Hello Guys,
I Have an HTC one a9 with 7.0, s-off, bootloader locked
I have some concerns before I root my phone
If I unlock the bootloader and root the phone, Will I have the option of phone encryption as it used to be ?
If I unlock the bootloader with HTCDev and flash the TWRP with SuperSu and boot file, it is a MUST to do a data factory reset? or I`m able to do all the process without loosing my data?
Thank you in advance
Click to expand...
Click to collapse
Unlocking your bootloader will wipe the device.
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
+1 I`m interested on this question, I have Nougat installed
sandreas said:
Hi all, I've been lurking and reading for 2 months, preparing to root my device. So this title fits my mood.
One A9, "factory unlocked version", S-on, running 1.57.617.60
Just did the actual unlock from htcdev so now data is erased. I'm re-reading the threads I saved to prepare, now that it's time to actually finalize what ROM I want to run, but now have a few questions before completing the plunge.
In past threads I read the newer MM and N security prevented rooting, and reverting to Lollipop was necessary. From what I read here that is no longer the case?
If I want to debloat the system I am already running, can I do that without finding a custom ROM to run?
Thank you
Click to expand...
Click to collapse
rilley said:
+1 I`m interested on this question, I have Nougat installed
Click to expand...
Click to collapse
Yes, you can root and debloat Nougat. Though you should make a stock system image backup first of you ever want to receive an OTA again. The TWRP thread FAQ has a lot of information about this.
Hi,
TL-DR; I rooted my phone, and want to update with minimal loss of data.
Sorry for this newbie question but I really couldn't figure out everything and wanted to confirm before proceeding.
I have MHA-L29C185B138 and rooted step-by-step via the instructions on this link:
HOW TO ROOT YOUR MATE 9 with Decrypted Data in TWRP without needing a patched Boot.img
I want to update. What should I do? I isntalled Firmware Finder and downloaded MHA-L29C185B172 FULLOTA-MF. (downloaded all 3 files)
I couldn't find a complete tutorial for rooted roms. Read different and partial recommendations on different threads. Somewhere I read that I need to restore my boot and recovery partition before update. I backed my boot partition as it was a step in rooting guide but I didn't back up my recovery partition.
So could you please point me a beginner friendly guide that explains step by step updating rooted mate 9?
Thanks in advance.
I bump up this question as I'm interested in that answer also
Sent from my MHA-L29 using Tapatalk
Updating and keeping root is basically not possible, as far as I know.
Regardless of installation method, your phone will be re-locked and wiped when new firmware is installed on a rooted phone.
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
vipivj said:
Same question from me as well. I rooted using the method in the link and I wanted to update to C185B172. No idea what's the safe proof way. As this is my daily driver and only phone I can't risk messing with it.
Click to expand...
Click to collapse
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Sent from my MHA-L29 using XDA-Developers Legacy app
jr313 said:
Whenever you update you have to start all over again with the same process you originally rooted with. Like @duraaraa said your bootloader gets locked back down and your recovery gets flashed to stock. So you have to unlock bootloader, then install TWRP, format your data so that you're unencrypted and flash the public then HW data files for the specific firmware you updated to. Basically follow the steps in the root method you initially used. This has to be done everytime
Click to expand...
Click to collapse
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
vipivj said:
So you meant to say if I download 'latest full package ' from Huawei, I can install it and everything go back to stock?
Click to expand...
Click to collapse
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise it will fail.
sent from my rotary phone
jr313 said:
Yes sir. But remember if you're rooted with TWRP you will have to flash stock recovery first before you can even think about updating or taking an OTA otherwise it will fail.
sent from my rotary phone
Click to expand...
Click to collapse
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
itenos said:
Thanks for clarifying but the original question of OP hasn't been answered yet. Where to get the recovery.img from?
I downloaded the full package from firmware finder and extracted everything with 7zip, I found 2 different recovery files with same file size but different content in it.
recovery_a.img and recovery2_a.img
Which one should I use ?
Sent from my MHA-L29 using Tapatalk
Click to expand...
Click to collapse
Sorry about that, you want to use the RECOVERY.img not recovery2. You fastboot that img and you will have stick recovery, and it will place it in the correct spot so need to worry about where you would need to flash it to. Hope that helps
sent from my rotary phone