Related
My question is similar to 'nikpmr's troubles but different enough I think they deserve a separate post.
The Problem as UnderstoodI was trying to root my device following the guide at this website. It's so simple it's a wonder I messed up. I think my failure was that I thought the drivers installed when I connected the phone were enough so I skipped that step. Then when running fastboot flash recovery.img the install failed. So I saw on some forum that it was supposed to be fastboot flash boot recovery.img of course now I know if anything it ought to have been "recovery" not "boot".
What I've Tried & Partial SolutionAt first I was just stuck in a boot loop and selecting "sideload" from the CWM recovery failed to allow me to connect with ADB or fastboot. i.e. Running "fastboot devices" and "adb devices" both returned as having no devices connected to my computer. So I installed the HTC Sync and promptly uninstalled the non driver parts of the app. Then I installed USBdeview and used it to uninstall all the USB devices associated with my HTC First. After doing that I learned booting into HBOOT allowed me to connect to the computer using fastboot and after then booting to the CWM Recovery I was able to connect using ADB to do a sideload. So I guess I'm about halfway there. Unfortunately after looking up the newest RUU and attempting to sideload it using "adb sideload OTA_MYST_UL_1.08.502.1-1.08.502.4.zip" the sideload failed. After selecting "- install zip from sideload" I get a message twice of "failed to open driver control: No such file or directory". It also failed when I attempted it with a similar fastboot command. So from all that I surmise my ROM is ruined and just needs to be replaced.
QuestionSo how do I go about replacing this ROM and boot partition? And, which ROM should I use? Is the one I got from the RUU site suitable? And what about the radio? I just need my phone to work. I can worry about rooting later. At this point I think I know what's happened but I don't know where to begin reading to figure out how to fix it myself.
Thanks for reading,
Relevant HBOOT text:
Code:
*** TAMPERED ***
*** UNLOCKED ***
MYSTUL PVT SHIP S-ON RL
HBOOT-2.00.0000
RADIO-1.15.40.00.13_2
OpenDSP-v9.2.0268.1214
eMMC-boot
Mar 22 2013,21:29:50:1682
1. you had to type in fastboot flash recovery recovery.img NOT fastboot flash boot recovery.img
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
abrahammmmmmm_ said:
Well there was an actual all in 1 tool to get cwm/twrp & root with a click for this specific device somewhere around these threads.
1) what exactly is the problem? (Sorry it was just so many words)
I don't think side loading the RUU would work bc I haven't heard its possible to flash it in the phone itself.
2) why don't you just sideload an existing pre-rooted ROM instead of the RUU file?
3) I see you're s-on, did you try flashing just the boot.IMG from the ROM you've got on it?
BTW I've only had luck with twrp on having it successfully detected when wanting to sideload
Click to expand...
Click to collapse
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
bnjo said:
1) The issue is I did "fastboot flash boot recovery.img" rather than "fastboot flash recovery.img" now I don't seem to have a boot mount point.
2) That sounds best. I didn't realize the RUU want a flashable ROM. More I just have to find the updated stable stock ROM.
3) I didn't have a ROM on it. I was just trying to root stock. Seems like I'm pretty close once I find that ROM.
Thanks y'all! Between your answers I think I have enough to go on. Feel free to point me to your preferred stable ROM. I'm content with stock but it would be nice to have Tiranium BU.
Click to expand...
Click to collapse
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Success!
abrahammmmmmm_ said:
Right now our most stable stock ROM is our rooted stock ROM
http://forum.xda-developers.com/showthread.php?t=2287811
We currently have 2 very able recognized devs working on CyanogenMod. You can expect something new in the near future but until then what I've showed you is the best.
Have any problems just come back to the thread
Click to expand...
Click to collapse
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
Great! glad to hear I could help. Yes it's always nice knowing when something I've said has helped someone in any way
bnjo said:
Thanks guys I know I always like to know when something I said was successful in helping someone. I just wanted yall to know after sideloading the most recent Odexed ROM then pushing it to memory after it wouldn't boot I succeeded after taking abrahammmmmm's advice of flashing the boot.img from HBOOT. After a longer boot than I'm used to I was able to get into my phone again. I wasn't able to use my TitaniumBU to restore but that just meant I had to spend a few minutes selecting apps to install.. And restoring a data backup for the only important app that doesn't keep the primary data off the phone.
Thanks again!
tl;dr Flashing the Odexed ROM boot.img fixed my issues. Thx!
Click to expand...
Click to collapse
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
russian392 said:
usually after changing a kernel, it takes a while to boot cause...well you get it right?
Click to expand...
Click to collapse
Yes I get it.
russian392 said:
i think what happened, when you typed in "fastboot flash boot recovery.img" is this
boot, is also known as kernel in aosp and rom building terms, because if you look inside a rom.zip, you will see that the kernel is the boot.img
so what happened is you flashed a recovery as kernel, and duh it wont boot cause if the kernel doesnt work, the os doesnt either
so what YOU did is you simply reflashed the stock kernel, usually after changing a kernel, it takes a while to boot cause...well you get it right?
the kernel is what android is based off of, kind of like ubuntu, its a linux os based on the original linux kernel.
Click to expand...
Click to collapse
That's what I thought happened. If I had stopped to read the help on fastboot before running "fastboot flash boot recovery.img" I wouldn't have made that mistake because I would have seen I wanted to flash recovery. One thing I *did not* know, which I'm glad to know, was that the boot.img contains the kernal. I was thinking Android was more similar to IBM style PCs than it is and therefore the boot.img was analogous to a bootloader like grub or lilo.
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
bnjo said:
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
in a nutshell yes, the boot.img uses the fstab
btw 10 posts you'll be "verified"
So the one thing I don't get is how is partitioning done? I take it Androids have some reserved partition for boot and the boot.img takes care of all system partitioning and mounts /sdcard/ for everything else. i.e. userland; appdata, media, and files. Am I guessing correctly?
Click to expand...
Click to collapse
Yep that's correct.
The name correlation is booting up requires kernel there for kernel is called beet.IMG
Thing about custom kernels, they aren't like that and simply contain modded files and pretty much an in packaged kernel.
Sent from my HTC first using xda app-developers app
stock recovery
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
astrit1995 said:
please can anyone send me the stock recovery.img
when i try to get it from RUU it says archive is corrupted
Click to expand...
Click to collapse
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Serupo said:
here:
http://androidfiles.org/getdownload.php?file=MystUL/Stock_Roms/stockrecovery.img
if you help, press thanks!!
Click to expand...
Click to collapse
Thank you for your help,i solved my problem yesterday but i think im gona need this sometime...
Hi all,
A while ago I rooted my Z3C and flashed a custom ROM. Today I wanted to update to a new version and I messed up very bad. I always was a die-hard flasher so I did things as always. Downloaded the ROM as usual, wiping as usual (I always wipe everything). Tried to install the new ROM and got the message that it can't mount /system. Looked this up and it seems that Sony got a kernel protection for /system and /cache, which I didn't know.
But now the actual problem. For some reason my system partition did got wiped, as result I can only acces recovery. But I still can't flash ROMs due the kernel protection. I tried to sideload the RICDefeat to disable the protection but this didn't work. Also tried to go back to stock with the EMMA tool but this didn't work either as the application doesn't detect the phone.
Anyone has a good idea what I can do now? I didn't backup my system partition, but I guess it doesn't matter as I don't have R/W for system.
So I assume you didn't unlock your bootloader before you tried flashing a custom ROM? Which Recovery do you use?
If you hold volume up while the phone boots up (enter fastboot), does it detect your phone there?
Did you install the proper z3c driver and does your device show up in device manager (maybe as unknown?) ?
This guide might help even if you don't want to root but flash a fresh firmware: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
MyPictures said:
So I assume you didn't unlock your bootloader before you tried flashing a custom ROM? Which Recovery do you use?
If you hold volume up while the phone boots up (enter fastboot), does it detect your phone there?
Did you install the proper z3c driver and does your device show up in device manager (maybe as unknown?) ?
This guide might help even if you don't want to root but flash a fresh firmware: http://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
Click to expand...
Click to collapse
Sorry, I should have mentioned this.
Bootloader is unlocked by the Sony website. For recovery i use XZDual, but for some reason I can only acces TWRP.
Fastboot is detectable and all drivers are installed correctly. Normally it wouldn't been a problem, but I also didn't have my system authorized for ADB as I just upgraded to W10.
You could try to flash cyanogenmod over fastboot now and see what happens (hope you backed up your TA partition first). I usually just prepare the flashtool (select image and press flash so it waits for device), then I hold down volume down and plug in the USB cable.
First I used to have some issues because of Windows driver signature enforcing but after disabling that it seemed to be fine.
Ohh and: Does TWRP print a log when you try to mount /system ? It might help to flash a kernel in fastboot then (could extract the cyanogenmod one from the zip [boot.img]), not too sure since I havent used a Sony Frimware for months now.
MyPictures said:
You could try to flash cyanogenmod over fastboot now and see what happens (hope you backed up your TA partition first). I usually just prepare the flashtool (select image and press flash so it waits for device), then I hold down volume down and plug in the USB cable.
First I used to have some issues because of Windows driver signature enforcing but after disabling that it seemed to be fine.
Ohh and: Does TWRP print a log when you try to mount /system ? It might help to flash a kernel in fastboot then (could extract the cyanogenmod one from the zip [boot.img]), not too sure since I havent used a Sony Frimware for months now.
Click to expand...
Click to collapse
I am trying now as I typ this. The only log I get from TWRP is that it can't mount system.
@ edit: Didn't help. Still getting message that system isn't readable/writeable.
Braindamage1989 said:
I am trying now as I typ this. The only log I get from TWRP is that it can't mount system.
@ edit: Didn't help. Still getting message that system isn't readable/writeable.
Click to expand...
Click to collapse
Did you try to go in TWRP and repair/change /system ? Also make sure you dont have the rm -rf option selected instead of properly formatting.
Hey guys,
I recently purchased a Mi5 in China and had a hellish experience trying to get a working rooted international ROM on it even though I am definitely not a noob at android. I found out that most issues I had were result of small/stupid mistakes that can be easily avoided with the proper knowledge, so I decided to write a super quick how to on the process for anyone that might need it in the future. There are similar guides out there, and I will refer to some (all credit goes to original posters) but I found that most are incomplete/not updated/plain wrong. Please also note that this guide is updated to June 20th, newer ROM versions might require different steps.
This how to assumes you are familiar with the standard ROM flashing process, in case anyone needs a more detailed explaination of some of the steps, you can reply or search XDA elsewhere, most of the stuff has been mentioned here and there before.
1. Check that your hardware is ok (dial *#*#64663#*#* in dialer, you will enter hardware test mode, check every single item carefully)
2. Request a bootloader unlock from Xiaomi, unlock the bootloader: follow instructions here http://forum.xda-developers.com/mi-5/how-to/unlocking-xiaomi-mi-5-bootloader-t3336243
3. Now that Your bootloader is unlocked, you have 3 main options for working ROMs: Xiaomi's Global Stable, Xiaomi's Global Dev, Xiaomi.eu's unofficial Stable. If you want to play it safe, I suggest to go with the Xiaomi's Global Stable, otherwise choose Xiaomi.eu's unofficial Stable. I did not test extensively all three, so this is just a general recommendation.
4. In any case, you will need to use the official Xiaomi's flashing tool (Miflash) to do your first ROM flash. Just follow the process here: http://en.miui.com/a-234.html and you'll have flashed your new ROM. In case you want to flash Xiaomi.eu's unofficial Stable, follow the same process but get the flashable ROM here: https://xiaomi.eu/community/threads/xiaomi-eu-multilang-rom-for-xiaomi-mi5-unlocked-bl-only-released.31231/
5. Boot into your newly flashed ROM, check once again that hardware is ok (see step 1.). Please also see step 10b for a tidbit of additional info if You're in China.
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
7. Once you are in TWRP, the recovery will ask you for a decryption password, just press cancel, then "Swipe to allow modifications"
8. Sideload (you cannot install from internal storage since you will not be able to access it at the moment) the latest SuperSU stable, which you can find here: http://forum.xda-developers.com/showthread.php?t=1538053. Please note that you WILL need the latest version, anything earlier might just get you a bootloop. And please do NOT format /Data to make it accessible to TWRP as that will also likely result in bootloop. Just sideload whatever you need.
9. Do NOT wipe Dalvik or Cache, reboot into System.
10. Congrats, You're done. Have a beer/coffee/tea and pat yourself on the back.
10b. In case You're in China, and this is Your first Android 5.0+ ROM, you will happen into a "bug" (it's not really a bug, but a result of China's Great Firewall), where whenever you connect to a Wifi, the phone will think you have no internet access and that will cause a whole host of issues (won't reconnect automatically, will try to default to 4G etc.). If so, just enable ADB Debugging and type adb shell "settings put global captive_portal_server httpstat.us/204" . That will mostly solve it (you might still get some weird result with some APs, but toggling Wifi should solve the problem for that AP forever.
Lazer Bear said:
6. Reboot into bootloader, boot (only boot, no need to install) TWRP, which you can find here as part of Xiaomi.eu's thread above in step 4. inside a zip packaged with a modded bootloader image. do NOT install the modded bootloader image. Also, this is the only version of TWRP that I found working for my device. There are a couple more versions from chinese developers (cofface, ganfan), but booting either resulted in blank screen.
Click to expand...
Click to collapse
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
m_adnan said:
How do you boot into twrp without flashing it? fastboot boot recovery.img doesn't work for me.. the command was successfull, downloading to the phone, then it's telling me booting, but the phone stay in fastboot.. thx
Click to expand...
Click to collapse
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
no, nothing happens on the screen, it stays in fb mode without any reaction. adb and fb devices doesn't return any device connected.. if i do an fb reboot it told me "waiting for any device" so the only option to get it run again is to power off.. yes of course, it's the recovery.img with the modified boot.img..
Lazer Bear said:
After it says booting, does the screen light up? If so please check wether "adb devices" and "fastboot devices" return anything. If adb returns "recovery" or if both return empty, you're likely bumping into my same issue where the recovery won't boot (to me this happened regardless of whether I flashed or booted it). Are you using the specific recovery version from my point 6?
Click to expand...
Click to collapse
i want only to inform you, i get it to work.. the problem was my rom, miui 8.. for miui 8 you will need a new version of twrp, which you can download here: https://yadi.sk/d/oj6Z-0u7sXdw6 after that, i was able to boot to the twrp recovery without flashing it, so i keept everything original like it was and was able to sideload the supersu and get root without to format my data.. when you start the recovery it came in chinese, but when you click on the right button you can choose your language.. that's it.. thank you for you support dude!!
Is it only way to switch from chinese ROM to official global ROM to have unlocked bootloader? If it is, is there any other way of unlocking it, waiting 15 days to get permission seems ridiculous.
Lovely step by step guide. But, any idea if it will wipe the user data and/or internal sdcard when moving from the chinese to international version?
Since no guide has been updated with information on official TWRP for root and backup reasons, I thought I'd create one.
DISCLAIMER:
To do this method requires you to unlock your bootloader. Your warranty is now void. This method assumes you have basic knowledge of ADB and Fastboot commands and know how to recover your device if you accidentally type a wrong command and now boot to TWRP and can't boot to system. If you cannot recover from this, Read up on guides to "return to stock" and familiarize yourself on how to recover your device should something go wrong.
There are two methods for root. You can flash TWRP to your boot image to be able to reboot to TWRP without a PC, or just a temp boot so you can just have root and not TWRP. I'll put in brackets the minor differences.
1: Get ready
Download latest build of TWRP img file from their website.(Previous link is to their instructions and device specific patches, download page is HERE.) {download the latest zip if you want to flash TWRP}
Download what you want on your phone (SU, Magisk, etc)
2:
Hook phone up to your PC, be sure you have latest adb/fastboot drivers. (I do not support windows related questions. If you have latest drivers, you'll have no issue with the below commands, Linux just works for this kind of thing)
3:
Navigate to your directory that has that img downloaded. (windows, shift right click and say "open command prompt here")
Type the below commands, and terminal output should be similar: (I.E. this is a copy/paste of terminal)
Main thing to remember is "Fastboot boot {filename}.img"
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot boot twrp-3.2.1-1-nash.img
downloading 'boot.img'...
OKAY [ 0.841s]
booting...
OKAY [ 5.135s]
finished. total time: 5.976s
[email protected]:~/Downloads$
BE SURE TO DO BOOT AND NOT FLASH!!! (If you ask why you can no longer boot to system, I'll let you know you missed this line.)
5:
You're now in TWRP!
It will ask you for your password. This is your PIN or password to unlock your phone. Enter it.
TWRP has now decrypted your storage to read the zip file(s) you put on your phone!
Go to install and navigate to your directory where you put that file
Install Magisk/SU/TWRP/whatever you please.
(Note: some root zips require a factory reset)
6:
Reboot!
You're Done congratulations!
Attached are images if they help you see you're doing the right thing.
Special thanks @erfanoabdi @invisiblek @npjohnson @joemossjr @jbats
Without the above people a lot of what's above woudn't have been possible for this device specifically. Also, thanks to everyone who pitched in to get a device over to invisiblek. Leaps and bounds have been done since that donation. And thanks to the other devs who have invested in this phone and their time to help out.
(Quoted from Nathan Chance)
Quite a few people have asked to donate to me in the past and I have turned them down. I am not in this for the money, this is my hobby, something I truly enjoy. If you truly want to donate to something (it is not expected in the slightest), I recommend an entity like the Open Source Initiative, the Free Software Foundation, XDA, or any one of the people I have thanked in the OP. Additionally, you are free to copy any and all of my work; the only thing I request is that you not ask for donations as well (though I can't really enforce this lol). Thank you.
Random issues post:
SU does some wonky edits to the ramdisk. It is highly suggested to flash Magisk for root.
Some have reported needing to wipe data after flashing Magisk. If you can't boot after flashing Magisk, just go back into recovery (can be twrp or stock) and wipe data/factory reset to boot again.
Note: we do not have a recovery partition. Never flash the img file! Download the flashable zip if you want twrp on your phone and flash per OP instructions.
Awesome thanks
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
droidgreg said:
I get into a bootloop and right back into TWRP using this method. I got the failed to mount data invalid argument. I got rid of this by formating data in TWRP. Now I get failed to mount system device or resource busy when I attempt to flash Magisk.
Bootloop.
I am on TMO running the latest 27.1 Oreo
Click to expand...
Click to collapse
Be sure to mount system under the "mount" button
I need the OCX27.1 oreo. I did a return to stock flashall to OCX27 and now reflashed TWRP and Magisk and boots fine but I lost baseband and IMEI
Added warning to OP that some root zips require a data wipe.
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
will4958 said:
I apologize in advance for asking a question that may have an obvious answer, but will this work for the Verizon variant of the Z2 Force? I'm not interested in trying out different ROMs just yet, but I would like to be able to remove adds, bloatware, and go back to using FoxFi the way it was meant to be used, specifically as a wireless hotspot. I can use the hotspot feature built into the phone, but it caps at 15 gigs & gets reduced to low, low speed after. Thanks in advance. Oh, and I should mention I'm currently running Oreo.
Click to expand...
Click to collapse
This guide assumes you can unlock your bootloader. Since Verizon and AT&T feel they have a right to lock down their devices, this guide won't work. That is why I voted with my wallet and left Vz after my M7 due to them putting phone OEM's privates in a vice and forced them to lock out those carrier variants.
Has this method been tested with OCX27.1 Oreo on TMO?
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
It probably hasn't been tested, but it should work in theory.
Uzephi said:
It probably hasn't been tested, but it should work in theory.
Click to expand...
Click to collapse
I was on 27.1 when I attempted to root and got into a bootloop and lost my baseband when I flashall back to stock OCX27. I have a feeling 27.1 update isn't compatible with this method and cannot be downgraded to even OCX 27 Oreo
so no go on 27.1 twrp? I have root on 27.1 TMO obtained post update. Obtained by fastbooting the nash twrp and running magisk 16.zip. No needing to format data or anything
I was just wondering about the installable twrp zip. I am coming from samsung development so all this A/B partitioning and some of the other partitions are new to me.
As soon as I can get twrp on the phone and feel comfortable recovering. The kernels and roms will start coming.
Feels strange not having odin to save my ass
droidgreg said:
Has this method been tested with OCX27.1 Oreo on TMO?
Click to expand...
Click to collapse
tested and working
mattlowry said:
tested and working
Click to expand...
Click to collapse
Have you actually flashed installer.zip to install TWRP or just booted TWRP and only flash magisk or SU for root without installing TWRP?
I fastboot booted the twrp. I didn't try the installer. What is it?
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
luponcooper said:
Doesn't work for me, i've done every step whitout problems but after installing SU and reboot, it wont boot anymore, stays in Moto logo.
Click to expand...
Click to collapse
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Uzephi said:
I'll put a warning about SU then. It also causes other stuff to not flash right. Suggested root is magisk for our device. Reflash your boot.img from the flash all and reroot with magisk then wipe data (wiping might not be needed, I never had to but some people have needed to).
Click to expand...
Click to collapse
Thanks a lot uzephi for answering.
I have the 6gb ram and 64gb model, XT1789-05. I try whit no succes to install Magisk (Error1) so i made a factory reset but still doesn't boot, stays in M logo.
Im super noob, can you guide me? i dont know how to recover the boot.img.
excuse my english.
DISCLAIMER: I'm not responsible if you brick or damage your phone in any way by using this recovery. It is always advisable to fully backup your phone before playing around with recoveries, custom roms and similar stuff.
What has been tested and works:
- Touchscreen
- Installing flashable zips
- Flashing images
- Flashing the recovery itself
- Creating backups (to internal storage, sdcard or OTG)
- Restoring from backups
- Terminal
- adb
- Rebooting to system, recovery, bootloader, ...
That doesn't mean that other things don't work. It just means they weren't tested yet. As I proceed with testing I will update the above list.
Usage (without flashing)
Bash:
# boot to bootloader
adb reboot bootloader
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
If you want to flash you have 2 options
Bash:
# boot to bootloader
adb reboot bootloader
# ********* OPTION 1 *********
# Flash to active slot (replace <slot> with either a or b, depending on the current active slot).
# Of course, you can flash to both by first specifying a and then b.
fastboot flash recovery_<slot> twrp-3.5.2_10-kiev.img
# ********* OPTION 2 *********
# boot to recovery
fastboot boot twrp-3.5.2_10-kiev.img
# Once in the recovery, copy the twrp image file to your internal storage
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
# Then go to Install, then Install image, select the twrp image you pushed before.
# Then select the Recovery partition and swipe to confirm.
# Before swiping you will have the option to decide if you want to flash to both slots.
Download: google drive
Sources will be posted in due time and this post will be updated accordingly.
Built for: Motorola Moto G 5G (Motorla One 5G Ace)
My model: XT2113-3 (kiev)
Credits
To the guys over here for the device tree, especially to SyberHexen for providing me with useful information.
reserved
reserved
Great!
Tested on my Moto G 5G XT2113-3. Seems to work properly. Good job. Awaiting to flash it.
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
It won't brick. I used it. (only once)
clintongsan said:
It shouldn't brick my device as long as I use it as a boot command and not flash, right? Is this associated with Hexen's version of unofficial twrp-3.5.2_10.0_BT-1.3??
Click to expand...
Click to collapse
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
h3xmind said:
By doing fastboot boot recovery.img you will not brick anything. However, I cannot guarantee for any of the functions in the recovery. They should be thoroughly tested before. I used it to fully backup my phone, I used the terminal and adb. Rebooting works, but I haven’t had a chance to test other functions.
Until now I didn’t even know that there’s already another twrp. I thought, judging by the posts in this forum, that there was a recovery in which the touchscreen didn’t work until you decrypted the filesystem with a password/PIN/…
I compiled the kernel by myself. I turned off some CONFIG_XYZ flags in order to be able to load the drivers that I manually extracted from my device. I packed the kernel in the recovery in which I modified some files in order to load the driver at the right point. I’ll post the full tutorial when I have time.
Click to expand...
Click to collapse
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Tomspector said:
Compile the zip for install, I will be the Gina pig for flashing lol.
I need to redo my phone anyway so it's no big deal.
Click to expand...
Click to collapse
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me.
I will do it now,
I would help
h3xmind said:
Great to have guinea pigs LOL. Thanks for your help, man.
Here it is: google drive
Let me know how it goes. I would have tested it by myself, but if something goes wrong I don't have time today and tomorrow for fixing stuff and I really need my phone.
P.S.: I repeat something that I already stated before. I'm a developer with many years of experience in different fields, but this is my first project of this kind, so many of the things (including building this installer) are new to me
Click to expand...
Click to collapse
I will do it now
Tomspector said:
I will do it now,
I would help
I will do it now
Click to expand...
Click to collapse
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Tomspector said:
It installs find but does not boot to it.
Installed this way
Ran fastboot boot twrp. Img
Then installed it while booted to twrp. Img
Zip says it installs fine but hangs during boot.
Mine is the metro version ace
Click to expand...
Click to collapse
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
h3xmind said:
Ok, thanks. I think the best thing is that I test it myself and fix it. I’ll post it when it works. Thank you for your willingness. I’ll remove the file from google drive.
Click to expand...
Click to collapse
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Ok, thanks for your help. I won't be testing anything tomorrow. I have a day off with my family
Tomspector said:
where can I get the latest rom for my phone with the last I tried lilionet roms but it's not there yet
Click to expand...
Click to collapse
Should be here: https://mirrors.lolinet.com/firmware/moto/kiev/official/
Tomspector said:
I did not clear my data, I did not feel like redoing my phone today,
It may be that
Click to expand...
Click to collapse
Anyway, I flashed it by doing the following:
Bash:
# boot to bootloader
adb reboot bootloader
# boot to twrp
fastboot boot twrp-3.5.2_10-kiev.img
# push the recovery image to the Download folder
adb push twrp-3.5.2_10-kiev.img /sdcard/Download
Once inside the recovery I went to Install, then Install image, once I selected the twrp-3.5.2_10-kiev.img file that I previously pushed, twrp asked me on which partition I would like to flash it. I selected the Recovery partition. (Although I ask myself why does the phone have a separate recovery partition if it is an A/B device. I still have to figure this out. Normally in these devices one would have to pack the recovery into the boot imate and than flash the whole thing to the boot partition.)
Then I rebooted to recovery and it took me directly to twrp. The problem, however, is that the touch screen didn't work anymore. So, I guess I got myself some extra work But it'll be fun. I can't wait to put my hands on it.
Did you manage to find the rom for your phone?
PEACH-PIT said:
Hexen's released twrp is just that.
Since the touchscreen-related problems have not been completely fixed, only the source has been released.
The one released here is the first fully functional twrp.
Click to expand...
Click to collapse
I tried Hexen's recovery. It's easily fixable to make the touch work. It took me two minutes. I'll let the guys working on it know how to do it. But first I have to figure out why does the touch screen stop working once you flash the recovery.