Just received a xt1710-01 from ebay and it is in excellent condition. Still on 7.1.1
I currently have a Droid Turbo thats rooted, now I want to do this z2.
Question is where do I start? Links?
Thank you.
Unlock the bootloader (I guess you know how to do so), Flash or boot TWRP and from it flash Magisk. That should be all.
But see if you can get the latest Oreo update to run first. For a while Moto uses a kernel with a buggy implementation of F2FS so you need to flash a module with Magisk in order to get it to work.
Whew, well I managed to unlock the bootloader. This was my first time (virgin).
Is upgrading to Oreo worth it? It's nagging me to do a update now, but I wasn't sure. I love Kitkat on my Turbo so the latest isn't really important to me, but if you feel I should, I will.
Well I have spent about 2 hours reading and d/ling updates and finally Oreo. Still not comfortable doing the rooting till I understand the procedure more.
This looks doable. https://forum.xda-developers.com/z2-play/development/twrp-3-2-0-0-moto-z2-play-albus-t3715660
Dammit! I read instructions to do a full wipe. Blank phone now. Looking on how to reinstall stock rom.
Finally after 2 days I have a rooted Oreo Z2. To may damn different ways to restore a OS and to root out on the net.
... You only have to boot a TWRP image from fastboot and flash Magisk there. That works for any device with unlocked bootloader, you just have to find the fitting TWRP image.
Related
UPDATE: So, I couldn't really wait, went ahead and flashed TWRP. It installed just fine, as long as you get into recovery immediately, TWRP sticks. I flashed SuperSU and rebooted and got into a boot loop, so had to flash the stock firmware again and everything is fine again. No idea why the bootloop, so if some expert knows, please share
-------------------------------------------------------------
So, T-Mobile/Samsung FINALLY delivered 5.1.1 on the P607T and it looks quite awesome so far. My device was rooted and had twrp, so I had to flash with odin and now have neither twrp nor root. While I know that its only a matter of time before the community updates the tools to make it easy for us to root, I wonder if somebody could tell me if its okay to flash the existing twrp_2.8.7.0_4.4 build on this new ROM?
I vaguely recall reading somewhere that with Lollipop, Android moved to a new FS, but suspect this only applies to the system and boot partitions? That flashing recovery should be fine, and worst case, twrp will not stick? But, just in case, it would be great to know if this is true from someone with more experience ... If yes, then I can try to flash twrp and see if SuperSU still works through ODIN.
Thanks!
Karthik
I tried root/TWRP using the P605 NEE thread method and I get the bootloop. It takes the modified ROM but not the SuperSU. Anyone else get root on P607T 5.1.1 yet?
From what I gather so far, 5.1.1 is rootable, but a bit more complicated than other versions. There are instructions one can follow to 'manually' root (meaning no simple odin flash), but these have not been tested on the Note 10.1 firmware yet and so no guarantees. I am told its just a matter of somebody who knows picking it up and creating a flashable solution, but the device is old and the world has moved on to Android 6.0, so this is not very high priority and we may have to wait a bit more.
The manual instructions, I understand them enough to want to try, BUT am not a developer and am worried about bricking my device! If anybody is brave enough to try,
http://forum.xda-developers.com/apps/supersu/wip-android-6-0-marshmellow-t3219344
http://forum.xda-developers.com/showpost.php?p=63194536&postcount=2076
should get you started.
I'm... asking for a friend....
But seriously, I tried following the instructions on the "[Guide] Step by Step from Stock N910V 6.0.1 to hsbadr's CyanogenMod 13.0 " thread, intending to bypass them when I got to the point of being able to jump over to the newer roms, and all I got was a boot loop when I tried flashing in 5.1.1. Is it because I'm on a retail 910v or was it a user error kinda thing? I tried multiple times and couldn't get it to boot after the flash, ended up flashing 6.0.1 back just to get my phone back.
I'm also ready to free the bootloader and root this thing. It seems emotion OS is the most popular and up to date now, correct?
I have the CPL1 update from Verizon( Dec patch). I know there are a bunch of threads with how tos, but it's unclear how outdated they are and whether it works with these latest versions. If someone can confirm the best way to go from cp1 to emotion.. Let me know.
Also.. I saw a while ago a guide on how to go to developer edition. Why isn't that front and center anymore? Isn't Dev edition completely unlocked... Why wouldn't I want to convert to dev edition before dealing with any rom changes? If someone can give some clarification I'd appreciate it.
Great news, I went for the plunge and succeeded. Confirmed -> stock and latest version software as of Jan 20 2017 (CPL1) can be downgraded to 5.1.1, rooted, TWRPed, and blah blah. I used the same guide you mentioned at top (hsbadr's CM13 guide), except i stopped at step 52 and continued to install emotion OS instead. Highly recommend it.
I'm on EmotionOS now. Wow, it was really worth it. So smooth compared to touchwiz 6.0.1. Haven't found a bug yet, but even if i do, i won't care.
I'm not sure what you mean "when i got to the point of installing newer roms". If you got to that point, why were you trying to flash 5.1.1 again?
How did you root it? I flashed mine back to 5.1.1, but I'm not having any luck rooting.
Michael7332 said:
How did you root it? I flashed mine back to 5.1.1, but I'm not having any luck rooting.
Click to expand...
Click to collapse
Follow the guide. You are going to go through a complicated process using the king root apk. I think the guide makes you use king root 3 times total to accomplish various parts of the process. King root loads up and spins for a few minutes, eventually succeeds, then you gotta punch in some things to command line using adb. I believe this is rooting your phone a few times.
Eventually you end up with twrp bootloader and jasmine Rom and everything just sticks.
So far.. The only annoying thing with emotion is that I lost volte and video calling. Maybe they'll bring it in one day.
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
This excellent guide by HomeBoy76 should give you all the info that you need....
https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-8-1oreo-unlock-t3715279
Hobocoe said:
Hello All,
It been a while since I've been lurking on the forums. Last time I was here was just after when I got the pixel xl and needed to root and unlock it, and was looking for how to update.
Back then when the update past 7.1.1 released they were having issues keeping root and unlocked status after the update.
I'm looking to update my phone now to the newest, stable release, that will let me keep root and unlocked bootloader on a Verizon Google pixel xl.
Here is where I'm currently at:
Verizon Google pixel xl.
Rooted
Unlocked bootloader
7.1.1 (NOF27B) stock image
Flash fire installed
Twrp installed
As of late I've had the common battery issue with this version get worse as the phone ages and now after landing in Indianapolis a few hours ago I'm having radio issues that I'm hoping a fresh install or update will fix.
I'm just looking for some direction on what steps I need to do to update and not lose root or unlocked bootloader.
I need to get full functionality of my phone back asap, so I appreciate all of your help with this.
Thank you
Click to expand...
Click to collapse
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
It's actually pretty simple, just download the latest factory image of either Oreo,. Flash the flash all script included with fast boot. Afterward boot into the system without setting up a pin or password or anything, set it up, then reboot into boot loader and boot the latest TWRP, then within TWRP flash TWRP zip file and Magisk root. Reboot system.
Homeboy76 said:
I do not think there is anyway to upgrade the 7.1.1 firmware to 8.10 firmware and not lose root. I would suggest you use my guide and Do #4 wipe data and then do #7 root.
Why wipe data? There have been a lot of changes to the firmware since 7.1.1 (NOF27B) stock image.
Note: Copy/Backup the information on your internal storage you want to keep to your computer i.e., pictures SMS, files etc. Why? Because using flash-all with the -w will wipe your internal storage.
Click to expand...
Click to collapse
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Hobocoe said:
Thank you everyone for the responses. Homeboy 76, I just had a quick question regarding your guide. The steps for the bootloader. Are you just showing all 3 options (unlock, lock, stock) for thurougness? Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that? Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
Thank you for your help with this. I just don't want to brick my phone while trying to fix it.
Click to expand...
Click to collapse
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Homeboy76 said:
"...for thurougness?
Yes
Or do I have to return the bootloader to stock and lock it before I can install the update and root again?
No, Do not lock the boot loader.
Also I should test a factory reset before I try updating to see if my radio problem is worse than I expected. If I just go into the system and do a factory reset, besides losing root will it be fine doing that?
Yes
If it locks the bootloader, go here to unlock it:
[How-to] Unlock bootloader on Verizon Pixel/XL by burduli
Or does that get it into a weird root/stock limbo and brick it? Or prevent me from installing the update?
No, No.
Click to expand...
Click to collapse
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Hobocoe said:
Thank you homeboy for the assistance. It's much appreciated. Luckily my phone issues were related to the location I was in. Indianapolis doesn't like my phone number for some reason.. But ill still be updating either way.
Thanks again.
Click to expand...
Click to collapse
You're welcome
Hey so I got the Nokia 6.1 unlocked from Best buy and noticed that it's a treble device and also has official twrp recovery. I noticed that we don't really have roms for this phone though and was wondering if I could just flash treble roms and if maybe that's the reason why? I really hope someone can help me out here lol.
There isn't any official bootloader unlock, and the paid, unofficial unlock stopped working long ago.
That is the reason that no developers have any interest in this phone.
As to flashing a treble rom: if you somehow get the bootloader unlocked, you can try. But many phones require some additional tweaks - treble isn't perfect. I don't know about this phone.
runekock said:
There isn't any official bootloader unlock, and the paid, unofficial unlock stopped working long ago.
That is the reason that no developers have any interest in this phone.
As to flashing a treble rom: if you somehow get the bootloader unlocked, you can try. But many phones require some additional tweaks - treble isn't perfect. I don't know about this phone.
Click to expand...
Click to collapse
The paid one is still working. I had to order last week, i had to downgrade from pie and unlock the bootloader, works fine. I can't recommend which one to order becuase of the rules of the forum, but at least one still works.
@SVcross
How did you downgrade?
runekock said:
@SVcross
How did you downgrade?
Click to expand...
Click to collapse
With the same service for unlocking the bootloader.
Well yes it's safe... currently i'm running havoc os 2.0....and it is working like charm...i haven't noticed any bugs yet...you can give it a try
But one thing to notice.... sometimes some magisk modules...like quickswitch for example....changes slot (from B to A in my case) when device is rebooted..and causes my device to stuck at bootloader aka download mode...idk why it happens...however it can be resolved by using fastboot....and typing fastboot --set-active=_b when device is in download mode....hope this helps...i encountered this a lot btw
Hi guys,
I have a problem I need some advice for. A year ago, I purchased my Amami for the purpose of GPS-navigation on my bicycle. It always worked fine and I was able to charge it with my dynohub without any issues. The charging is giving me a headache now though, and all troubleshooting points at the phone being the problem.
Now, a couple months ago I decided to ditch 4.4 and go for a custom ROM (I've tried Oreo and Pie) which worked fine, but the phone doesn't charge as well as it used to on my bike. I'd like to go back to stock to see if that's what is causing the issue and used the Xperia Flashtool to revert to a stock image, but the ones that used to work on the phone now give me bootloops after I've flashed TWRP and ResurrectionRemix and Lineage OS.
Is there anything I need to know before I flash a stock firmware with the tool? Any input would be appreciated.
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
jho55 said:
Sounds like to have not updated to Lolipop and therefore you do not have real recovery. Is your bootloader unlocked? Then you can try EMMA to update to Lollipop.
Click to expand...
Click to collapse
My bootloader is unlocked, I have TWRP installed and am currently running Lineage OS (Android 8). It doesn't matter if I flash Sony's original Kitkat or Lollipop; both will have bootloops. No offense, but I'm not sure you understood my original post: I'd like to go back to an old stock ROM, because 4.4 is the one that I'm sure have me no trouble with charging on my bike.
Proper BL relock:
https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907https://forum.xda-developers.com/xperia-z/general/tutorial-relock-xperia-z-bootloader-t2191907
If you use twrp in fotakernel partition maybe necassary to write back original fotakernel.sin (inside stock.ftf) before relock with flashtool. Remember! After relock with flastool the new BL unlock key here: DEVICESERIAL \ unlock.txt