Related
To root 10.4.1.B.0.101 Firmware, I need to unlock the bootloader
To unlock the bootloader I need to backup TA
To backup TA I need root ...
Can someone advice how to left this endless circle ?
here u go
http://forum.xda-developers.com/showpost.php?p=51612704&postcount=12
anagramgenius said:
here u go
http://forum.xda-developers.com/showpost.php?p=51612704&postcount=12
Click to expand...
Click to collapse
So much work...
And I wish it would include links.
I really hope there will be a one-click root for 4.4.
It's weird all phones from the competition are easily rootable but someone 4.3 on Sony is so complex.
link for advanced stock kernel xperia zl
http://forum.xda-developers.com/showthread.php?t=2641695
They've closed alot of the bugs that were being used for the previous root methods.
IF you don't care about your data, what you CAN do is to revert to an older FTF, root, backup your TA partition, then go from there... it's a pain... but it works.
Sent from my Touchpad using Tapatalk
anagramgenius said:
here u go
http://forum.xda-developers.com/showpost.php?p=51612704&postcount=12
Click to expand...
Click to collapse
So I saw this and was about to do it, but then read this post:
http://forum.xda-developers.com/showpost.php?p=52371524&postcount=7
Seems much easier (no bootloader unlocking necessary) so I'm trying to figure out why you'd have to do everything listed in the other thread. Any insight?
Bobomo said:
So I saw this and was about to do it, but then read this post:
http://forum.xda-developers.com/showpost.php?p=52371524&postcount=7
Seems much easier (no bootloader unlocking necessary) so I'm trying to figure out why you'd have to do everything listed in the other thread. Any insight?
Click to expand...
Click to collapse
if u want your phone to be stuck in bootloop, go ahead with that method, else you follow the method which i posted. it's a long procedure, but it works!
anagramgenius said:
if u want your phone to be stuck in bootloop, go ahead with that method, else you follow the method which i posted. it's a long procedure, but it works!
Click to expand...
Click to collapse
I don't understand why someone would post bad directions like that. Also they are very similar to Doomlord's own instructions for rooting. He says to flash an old exploitable kernel and then run his exploit and then flash back.
Anyways, your method says to downgrade to .67 firmware, and I can't find that anywhere. Can I downgrade to .423 firmware and use Doomlord's root method instead? Should be the same results, right?
Also, is step 8 necessary? Do I have to flash back stock recovery or can I keep CWM?
And finally, using this method, how will we keep root when 4.4 finally arrives?
anagramgenius said:
here u go
http://forum.xda-developers.com/showpost.php?p=51612704&postcount=12
Click to expand...
Click to collapse
Thanks, It worked without any problem.
I also wouldn't take the risk to flash the Kernel of .423 over the .67 firmware.
Yes they are both Android JB 4.2. But you never know.
About 4.4, we will have to wait what will be the available methods.
Bobomo said:
I don't understand why someone would post bad directions like that. Also they are very similar to Doomlord's own instructions for rooting. He says to flash an old exploitable kernel and then run his exploit and then flash back.
Anyways, your method says to downgrade to .67 firmware, and I can't find that anywhere. Can I downgrade to .423 firmware and use Doomlord's root method instead? Should be the same results, right?
Also, is step 8 necessary? Do I have to flash back stock recovery or can I keep CWM?
And finally, using this method, how will we keep root when 4.4 finally arrives?
Click to expand...
Click to collapse
Bobomo said:
I don't understand why someone would post bad directions like that. Also they are very similar to Doomlord's own instructions for rooting. He says to flash an old exploitable kernel and then run his exploit and then flash back.
Anyways, your method says to downgrade to .67 firmware, and I can't find that anywhere. Can I downgrade to .423 firmware and use Doomlord's root method instead? Should be the same results, right?
Also, is step 8 necessary? Do I have to flash back stock recovery or can I keep CWM?
And finally, using this method, how will we keep root when 4.4 finally arrives?
Click to expand...
Click to collapse
yeah. that kernel method worked for previous firmware. now it won't work. and yeah you can downgrade to any rootable firmware. u are doing this just to backup TA so that you can lock BL. you can keep that advanced kernel. but you wont get OTA updates, better to flash stock kernel and lock your BL. when 4.4 arrives, if no rooting kit is available, you've to unlock BL, install advanced stock kernel which has custom recovery and install SU and flash back stock kernel and lock your BL
After you've rooted, but before you actually unlock your bootloader... if you install the dual boot recovery, you can make a backup of your TA partition information via TWRP as well as by using the other method... (do both to ensure you can revert)...
And then after you unlock your boot loader save ANOTHER TA backup... name them so you know which is which so you can re-lock your TA if you choose if you're running a stock kernel/rom and want the DRM keys back... but that way you don't have to go through the pain for unlocking each time...
Sent from my Touchpad using Tapatalk
Well I ended up not even needing to unlock the bootloader for my goal, which was simply stock + root on .101.
http://forum.xda-developers.com/showpost.php?p=52411661&postcount=23
Only had one small issue with the flashed zip/stripped FTF messing up the XZDualRecovery settings, but deleting xzdr.prop and rebooting fixed it.
When i was searching for, i really thought i was being crazy.
so many devices with a single click to root
I cant wait to start theming my ZL, Some mockups cooking here to new skins, but can't test without that root.
well, Did that steps worked well?
Bobomo said:
Well I ended up not even needing to unlock the bootloader for my goal, which was simply stock + root on .101.
http://forum.xda-developers.com/showpost.php?p=52411661&postcount=23
Only had one small issue with the flashed zip/stripped FTF messing up the XZDualRecovery settings, but deleting xzdr.prop and rebooting fixed it.
Click to expand...
Click to collapse
if u go with method, u have to download those stripped files every time when new firmware arrives. which is kinda boring to download those huge files. whereas in that unlocking BL method, u download only kernels with recovery which is just 15 to 20MB
Hello friends, I just got a new refurbished rogers(canada) HTC M8 GSM phone.Its totally stock at this moment and would like to do sim unlock,s-off and boot loader unlock. But before i would like to get full back up of my stock.Few questions:
1.How can i do full complete backup of my stock phone in case in future i need to revert back?
2. what are the steps to do s-off,sim unlock and bootloader unlock?
Right now phone says:
Android version 4.4.3
HTC sence version 6.0
software number 2.23.631.2
HTC SDK API level 6.25
kernel version
3.4.0--g523xxxxxx
baseband version
1.19.2133xxxxxxxx
build number
2.23.631.xxxxxxxrelease-keys
Thanks in advance...
Go to HTCDev.com to unlock the bootloader. The process is self-explanatory (just follow the website instructions). There is a writeup on the following guide, if you need help. But honestly, if you can follow instruction, the process is self-explanatory as I mentioned: http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Then, to backup the stock ROM and recovery, follow the instructions listed on the following thread under "How do i backup the stock HTC recovery?" : http://forum.xda-developers.com/showthread.php?t=2701376
This process will boot custom recovery without actually flashing recovery it to the phone, allowing you to backup stock recovery as well as the stock ROM (if you flash custom recovery before doing this, stock recovery is over-written and therefore can't be backed up). Note that your version's stock ROM and recovery may already be uploaded to the above thread by another XDA user.
Then achieve root by your preferred method (flash custom recovery and flash SU/SuperSU, or use weaksauce, towelroot, etc.). Then use sunshine to achieve s-off (firewater s-off will likely not work, as it was patched some time ago): http://theroot.ninja/
Then after s-off, you can unlock SIM: http://forum.xda-developers.com/showthread.php?t=2708572
Thanks a lot redpont73 for your directions!!!Will follow your steps and let you know how things went..Thanks
Ok i unlocked my bootloader with htcdev.com and it says unlocked now.
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?please guide me.thanks
ninja_zx11 said:
Now how to backup my stock at this point? I tried this thread you showed me: http://forum.xda-developers.com/show....php?t=2701376 but didn't understand fully. but it says :fastboot boot recovery_filename.img (this does not work on the latest 3.xx firmwares !!! we need to get the stock recoveries from the OTA files)"
I am little confused at this point.How can i back up at this point without installing any recovery software like twrp?
Click to expand...
Click to collapse
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
redpoint73 said:
By placing the custom recovery image in your fastboot folder, you can then boot recovery without actually flashing it to the phone, using the command you quoted. Think of it as remotely running the TWRP software that is still located on your PC (at least I think that is how it works).
Once you are booted into TWRP, you can backup system (stock ROM) and recovery(stock recovery).
Click to expand...
Click to collapse
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.Just trying to learn and don't want to brick my phone with any wrong move.thanks
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
ninja_zx11 said:
i found this thread.
http://forum.xda-developers.com/showpost.php?p=53770286&postcount=4
Will that help?thanks
Click to expand...
Click to collapse
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
ninja_zx11 said:
Could you please help me to find the custom recovery image that i can put in my fast boot folder and please step by step if you don't mind please.
Click to expand...
Click to collapse
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
redpoint73 said:
Yes, that is another method.
---------- Post added at 11:11 AM ---------- Previous post was at 11:05 AM ----------
Go to the General forum section for the M8, and look at the Index thread (sticky at the top of that forum) to find link to recoveries and other resources, including guides and how-tos. Read up and learn.
Taking the time to familiarize yourself with the basic concepts and processes is much more valuable than someone walking your though step-by-step. I won't walk you through step-by-step, as you will learn very little that way.
The process is not that difficult, anyway. You already used fastboot to unlock the bootloader. Other fastboot commands are not any different in execution. If you can't handle taking it from here, modding the phone probably isn't for you.
With S-on, you aren't going to brick the phone by backing up or flashing recovery. Even with s-off, as long as you only flash things intended for the M8 (and only for the GSM version - not CDMA - to be safe), you will not brick. You can only brick the phone if you damage hboot, radio, or partition tables.
Click to expand...
Click to collapse
Yes you are right...I will read more and i want to learn and will try to do it myself.If i will have some confusion, i will ask here.Looks like i need more reading.
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
ninja_zx11 said:
Now what i am planning to do is:
1. Install twrp
2.Take a full nandroid backup.(will it be enough to save me in future if i would like to go back to stock after S-OFF?)
3.root and s-off.
Does it make sense?
Click to expand...
Click to collapse
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
redpoint73 said:
The process to backup stock recovery is easy, by either method we already discussed. If you want to be thorough, backup stock recovery.
Backing up stock recovery and stock ROM is sufficient to return (mostly) to stock. There isn't much else you can do
Click to expand...
Click to collapse
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
BerndM14 said:
huh? Did you flash it and then tried to install it from the play store after it was already "installed" by being flashed in custom recovery? If not, what exactly are you talking about here?
I've never bothered with the play store, just boot the custom recovery and flash the latest SuperSU. That's it... :silly:
Click to expand...
Click to collapse
thanks BerndM14, i just copied supersu zip to internal storage as you said and installed it by booting into twrp from pc. and its done... thanks..
ninja_zx11 said:
UPDATE:
I downloaded latest twrp and i booted into twrp .then took full backup. i also took back up using philz touch same way by just booting into philztouch.
Then i tried to root using supersu by same booting into twrp and tried to root.it created a supersu icon on the spring board and then i tried to install it from play store but it errored out and phone rebooted.After that i tried to remove the supersu icon from the phone but just couldnt. Then i thought of restoring stock backup using twrp and it restored it to stock stage.Atleast now i know that my stock backup worked.!!!
Now my question is why did supersu not root my phone?Should i try another method?please advice.thanks
Click to expand...
Click to collapse
Sounds like a brick in the making.
Make sure that you read and understand what you are about to do before you do it.
A nandroid won't always help you.
If I may make a suggestion, don't go S-Off.
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
ninja_zx11 said:
I am abandoning the idea of doing S-off after the suggestion from xunholyx above and after reading this http://android-revolution-hd.blogspot.ca/2013/06/do-we-really-need-s-off.html.
Click to expand...
Click to collapse
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
redpoint73 said:
I see you are learning. I will never understand why folks seek to get s-off, without even understanding what it means. You should not be attempting any mods, unless you fully understand what the purpose is (such as s-off).
Click to expand...
Click to collapse
thanks redpoint73 for giving me helping hand!! without your help i wouldn't have done it.....
I am considering buying S7 Active, and I have a question about rooting.
I will buy one on ebay, I'm not sure which firmware it will be on.
What is the latest rom that can be rooted, and how can I download that rom? There is no combined guide and it is a little confusing. Once I root my phone I usually use it until I replace my phone, so I would like to get to the latest.
Also how do I root the phone? Do I still need to follow the post?
https://forum.xda-developers.com/s7-active/help/samsung-galaxy-s7-active-root-t3473649
Thank you in advance!
all version are rootable...
that link althou starts out as links to android 6... ends up on 7 at around #700
there is no recovery like twrp,.. but yes they all got root ....
if not follow rom modder thread tut, up to flashfire if you only want root
miniminus said:
all version are rootable...
that link althou starts out as links to android 6... ends up on 7 at around #700
there is no recovery like twrp,.. but yes they all got root ....
if not follow rom modder thread tut, uo
p to flashfire if you only want root
Click to expand...
Click to collapse
Thank you for the reply.
I couldn't understand some parts of your comment... So the latest firmware is still rootable using the method in the above link? Then how can I obtain and flash the latest firmware? I'll not use the phone on AT&T.
Also I couldn't understand the last line of your comment... what did you mean?
think its oulined in the main thread you posted ...
but use this site ..
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/
which has all the 'update' zips, of which you can use in normal stock recovery and load up via memorycard
is a slow process, and wipes everthing (you can stop it before it does, but you gotta be ready, so make backup anyhows !!)
miniminus said:
think its oulined in the main thread you posted ...
but use this site ..
https://cloud.mail.ru/public/BGy7/gKs4xzhRE/
which has all the 'update' zips, of which you can use in normal stock recovery and load up via memorycard
is a slow process, and wipes everthing (you can stop it before it does, but you gotta be ready, so make backup anyhows !!)
Click to expand...
Click to collapse
Thank you for the link! QF2 seems to be the most recent one. I will follow the steps when I get the phone.
EDIT: someone said QF2 is not rootable yet... is it still the case? Then I may have to go for QE1.
well people had issues at the start, as i think they was not using the most recent (2.82) root methods...
but people on the Ufirm Rom modder thread ARE rooted on QF2...
miniminus said:
well people had issues at the start, as i think they was not using the most recent (2.82) root methods...
but people on the Ufirm Rom modder thread ARE rooted on QF2...
Click to expand...
Click to collapse
Ummmm... sorry but what is the 2.82 root method? Is it different from the above method?
2.82 is the newest version of SuperSU which provides you root privileges, and thus the version of 'root.bat' that you run (on your PC with phone connected, with ADB USB debugging enabled in Developer mode)
AFTER you flash the Eng.Boot file (teh engineering boot image that you flash with Odin, while phones in 'download' mode)
miniminus said:
2.82 is the newest version of SuperSU which provides you root privileges, and thus the version of 'root.bat' that you run (on your PC with phone connected, with ADB USB debugging enabled in Developer mode)
AFTER you flash the Eng.Boot file (teh engineering boot image that you flash with Odin, while phones in 'download' mode)
Click to expand...
Click to collapse
Thanks. The post explains based on 2.76, I should do some research how to do that with ver 2.82 when I get the phone.
Hi all, I have an honor 7x (obviously) BND-L21 running EMUI 5.1 and Android Nougat. I have used a guide (which i am sure was from here) to unlock my bootloader and root the phone using twrp a while ago.
I have now noticed there is an OTA update to EMUI 8 and Android Oreo.
My questions are these...
I have downloaded the OTA update and tried to install it only to be taken every time to TWRP. After reading up on this i can see this is obvious but none the less i cant update my phone via this method.
I have copied the files downloaded from the update, (namely update_data_full_public.zip, update_full_BND-L21c_hw_eu.zip and update.zip) to my SD card.
So... 1) can i just flash the above zips using twrp and then reroot again with twrp and be on the latest firmware.
2) if not this method then do i have to remove twrp and then update to then put twrp back on again and root etc.
3) if anyone knows what i should be doing to update without bricking my phone then i apologise but i havent seen the correct thread on this. (seen many indian variants or others i'm not sure are applicable to my device)
Thanks for anything you guys can help with..
You need stock recovery for emui update. Flash stock recovery update. Then flash twrp of you need to root
download multi tool 8 for honor 7x
connect it
go to recovery section
install stock recovery
then u can install oreo update
Just bought op5t ..
i used to flash roms on my previous phone s7 edge, n want to root this phone as well
i came across the desired thread but its mentioned for oos 5.1.5 . i want to know if 5.1.7 can be rooted the same way with files provided in the original post of rooting guide thread ??? do i need diffrnt files from those mentioned in the orignl post of the thread as someone said 5.1.5 users need recovery other than twrp .
m just confused , dnt want to brick my new phone
it should be similar.
Do i need to flash a custom kernel as well ??
or just unlocking boatloader, flashing recovery n rooting will suffice??
No, it's optional.
FWIW, I have tried franco kernel & blu_spark. They both work flawlessly.
Fahad_ahmad said:
Do i need to flash a custom kernel as well ??
or just unlocking boatloader, flashing recovery n rooting will suffice??
Click to expand...
Click to collapse