Related
[Stock Rom] Huawei (Prague) PRA-xxxC432B182
For restoring/ rescue your device.P8 Lite 2017 - PRA-LX1, LX2, LX3, LA-1
P9 Lite 2017
Nova Lite
Honor 8 Youth
Created and tested on this device:
Huawei P8 lite 2017 [PRAGUE]
Model number: PRA-LX1
Build number: PRA-LX1C432B182
free device
The PRA is extrem sensitiv.
Any unconsidered, unofficial intervention, don't forgive it.
Hundreds of users have already "bricked" their device.
The response to the dealers is enormous.
To restore your devices,
I'll provide a complete rom.
It is 100% functional and rooted with SuperSu.
It is to be applied to the device via TWRP restoring.
But it is also suitable for this purpose without an OTA update,
to get the current firmware.
Be sure to read the following instructions carefully.
You're doing it at your own risk!
Rom installation:
In the download folder:
2017-12-30-PRAstockB182root (zip)
there are 26 backup files compressed as Zip files.
After downloading, unpack all files individually into this directory. Then delete all zip's. Now copy the whole directory to your TWRP backup folder. Where your other backups are.
Now flash the stock recovery and perform a factoryreset.
Now flash TWRP and make a wipe of the data and system partitions in TWRP.
Then restore my backup and reboot.
The firmware and the kernel are already rooted.
If necessary, you can install Busybox.
If the device does not boot, the bootloader must be unlocked again with the Huawei unlockcode.
It is a little bit more work for you to unpack everything individually, but this way a faultless installation is possible.
I have tested the up- and download, unpacking and restoring several times. It works perfectly. The rom is bug free.
Now create a new TWRP backup
and remove all older backups from the TWRP backup folder, otherwise they could cause problems later.
Save it to another folder or to
USB-/Stick, or HD.
I would now like to make a few comments on the end of the year:
I've had the P8 lite 2017 for a year.
The first rooting was developed by me.
The SuperSu and the first rooted kernel,
enabled the developers
@Tecalote and KangVip.
TWRP was provided by the LineageOS team. Again and again I have added fresh rootings and roms.
Nevertheless, increased Bricks are not missing.
It took an enormous amount of time to find
help the users. Unfortunately, this didn't work out for everyone.
My recommendation:
Now set up your device completely. Then create a complete backup with the ingenious Huawei Backup App. Now you take the recovery back.
"fastboot flash recovery recovery. img"
Removes TWRP from your brain for the time being.
Your device is now perfect and the firmware is original. You also have root and the OTA update authorization. When OREO comes, you just wait until I announce the new rooting."
I wish you all the best for 2018.
WARNING !
If all this has worked on my device, it does not mean that it goes with everyone else. Follow exactly the instructions to prevent damage. The execution is your risk.
Never make a factory reset in TWRP. Brick !!! Wipes only in stock recovery.
NOTE: Despite careful preparation I can not guarantee that through the implementation of this Guidance does not create damage to the device or operating system, and therefore assume no liability for ensuing damage and malfunction of hardware and software! If you are still unsure, follow these steps: Only perform the procedure if any mentioned conditions (model number, Android version, etc.) apply to you or your device. Read the instructions carefully and completely, check unfamiliar terminology by google or xda. Downloaded files check for viruses. A backup of important settings and data make. The instructions do not perform, if you do not know what you're doing.
Thank you very much: @Tecalote, KangVip,Chainfire, Stephen (Stericson), Jmz Software, LinageOs team, JRummy, as well as.
Huawei Technologies Co., Ltd.
Update 2017-12-31:
I removed the part "dual recovery".
The support on xda is finished.
Only here:
https://www.android-hilfe.de/forum/huawei-p8-lite-2017.2980/
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Restore your last backup and repeat the procedure.
Try this one first:
Root again with the SU (B182) from the download.
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
afit5 said:
I couldn't restore my phone. I followed all of your instructions and after restoring, when I reboot, the phone goes only in TWRP (no volume keys pressed). Any ideas on what I can do?
In any case thank you for the thread, it's good to have a well described procedure for these things
Click to expand...
Click to collapse
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
mbwf said:
Tip for life: try not to trust random nerds on forums, offering "ROMs" and what they call "tutorials". Stick to the outlet which sold you the phone, and deal with them and/or the manufacturer, and you can't go far wrong.
Click to expand...
Click to collapse
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
KuGeSch said:
I had the same situation. It's a bit tricky and you must really know, what you are doing
I rebooted to bootloader an repeated the oem unlock -> this caused a factory reset!!
I am on dual recovery and so I rebooted to twrp, repeated the restore with the b182 stock rom and could reboot to the system
Click to expand...
Click to collapse
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
afit5 said:
UPDATE: I solved in another way, which is: booted to fastboot mode, restored the stock recoveries (recovery1 to recovery1, erecovery to recovery2), then the phone booted normally as it should have had. At that point I could reflash twrp to recovery1, but that is optional.
I think the phone tried to boot but having the wrong recovery in recovery2 slot caused problems (just a random hypothesis). Hope this helps
Click to expand...
Click to collapse
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
KuGeSch said:
What you call erecocery is this the stock erecovery or is it prague311.img from ChinHon? If it is the stock erecovery, where can I find it for download?
Thanks a lot!
Click to expand...
Click to collapse
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
ChinHon said:
-prague311.img is TWRP
-recovery.img is the stock recovery on recovery partition 1
-recovery2.img is the stock eRecovery on recovery partition 2
https://www.mediafire.com/file/r33el93w5wyqwde/recovery2.img
Click to expand...
Click to collapse
Thanks a lot! You are doing a great job!
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
SnoopyDog said:
100% useless post. This does not help anyone.
ChinHon tries to help others and i would trust him more than you...
Click to expand...
Click to collapse
Very good. Keep smiling.
baffo92 said:
Hello!
I want to follow this guide, it should be fine for my Dual SIM Variant, right?
I have a problem with one file, that is 'version.emmc.win.md5.zip' that can't be downloaded from MEGA. Can someone please provide a working link for that file?
Also a doubt: when all the files will be ready my idea is to restore your TWRP backup, flash stock recovery then lock bootloader, to make it as near to stock as possible: will this work? I have another TWRP backup that is running on my phone, but if I lock the bootloader it won't start, if I unlock the bootloader there no problems at all.
Thanks for your interesting topic!
Click to expand...
Click to collapse
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
ChinHon said:
Here's the link.
https://mega.nz/#!4sd3DI6Z!BOfI0teLD_m3aLUROhiMVZuePySmp329RXZpjsH3AM0
Please tell me why you want to take the rom. What's happening?
Click to expand...
Click to collapse
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
EDIT 3: I've done a full phone clean by using the 'Factory Reset' option in 'Settings'... now the phone boots, but:
1. NFC/GPS are not working, they are blinking
2. FM Radio is not working (it says com.huawei.... and has an Android icon instead of the original icon)
baffo92 said:
The link works perfectly. Thanks!
I can now give this stock ROM a try!
EDIT 1: I'm trying to install the ROM but I have a problem with TWRP: I launch the command 'fastboot flash recovery prague311.img' then boot to TWRP, but the touchsceen of the phone is unresponsive and I can't do anything to make it work. Have you got any suggestion?
EDIT 2: I made some mistakes here and there, but the TWRP booted and now I have the phone on your ROM Version! I'm trying to clean everything and do a clean install if I can...
Click to expand...
Click to collapse
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
ChinHon said:
To get the rom completely clean you do the following:
Go to my root thread section: Threadupdate: 2018-01-02 and work through the instructions. Then you have a perfect clean stock rom.
Click to expand...
Click to collapse
Your support is very helpful, thanks!
I have problems on the steps to reproduce, even after reading your guide :')
This is what I do:
1. Wipe Data/Factory Reset + Wipe cache with stock recovery
2. Flash TWRP
3. Open TWRP, clean data, system and also cache + dalvik
4. Reboot the phone to a fully working with B182, in English with Dual SIM fully recognised
5. What I have to do from now on to have a fully stock experience (remove custom Kernel, reflash stock recovery and erecover, re-lock bootloader and fully ready to Oreo)?
Can you please guide me?
Thanks and sorry for my problems, but I work with Nexus devices thare a bit more 'elastic' in flashing
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
ChinHon said:
The kernel is stock. You just have to flash the eRecovery and recovery. That's all.
Click to expand...
Click to collapse
Ok, thanks!
This is what I did before, but I can't do a factory reset due to the problems described (Radio FM not working, NFC not working).
I can't also relock the bootloader, because the phone will boot to erecovery (recovery2) and won't let me reach the boot of the ROM. Have you got any suggestion?
If leave it as it is now (unlocked bootloader with stock recovery1 and recovery2) will Oreo arrive without any problems?
Your support is awesome, thanks
If you now take my UPDATE.APP via dload the problems should be gone.
ChinHon said:
If you now take my UPDATE.APP via dload the problems should be gone.
Click to expand...
Click to collapse
Sounds good!
If I flash the stock recovery, then update officially with an UPDATE.APP from SD Card everything should be ok.
Where can I find your UPDATE.APP? I didn't find it in your MEGA Folder
Thanks, again, for your incredible support!
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.
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Jonny6921 said:
After installing Nitrogen OS and gapps, I have restarted the phone and the following message appears:
Decryption unsuccessful, the password you entered is correct, but unfortunately your data is corrupt. To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have opportunity to restore any data that was backep up to your Google Account
I have formatted all the partitions, I have repaired them, I have reinstalled the operating system again and the same thing keeps appearing ...
TWRP is updated.
Help me! Thank's!
Click to expand...
Click to collapse
Perhaps you should say which version of NitrogenOS you're using. Also asking in Nitrogen's thread has a higher chance of answers for your question.
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
runekock said:
I wonder if you think wipe is the same as format. That is not always the case. You need a real format of the data partition.
Click to expand...
Click to collapse
Additionally TWRP's format function is broken.
Try "fastboot format userdata" if TWRP isn't properly formatting.
Elektroschmock said:
Additionally TWRP's format function is broken.
Click to expand...
Click to collapse
Can you elaborate on this?
I usually try to erase and format in fastboot anyway. But fastboot throws a can't format raw partition or something like that.
format (not wipe) data or use oreo builds
i've already done it
upgrade your twrp if it keeps failing, i'm using the latest release
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Flaco05 said:
Can someone help here? I followed all of the necessary steps to install LineageOS 16 on the Nexus 6 using TWRP and I am having this problem. I am not supremely skilled when it comes to these things, but I did it very carefully and made sure to read the instructions many times and go step by step as indicated. I was really looking forward to injecting new life into my N6, but now I basically have a brick.
Click to expand...
Click to collapse
Without explaining what the problem is, it is hard to help you. Since you are using TWRP, you should have backup to restore.
Thank you for replying. I have the exact problem described by OP. And yes, I have a backup, so technically not bricked, you are right. Just very disappointed that following the flashing instructions let to this problem. Thank you again.
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Hi, that is exactly what I did! I have repeated the process with LineageOS 15.1 (and the matching GApps) and it worked. Might this be an encryption problem related to LinerageOS 16? And thank you for responding.
Incidentally, what GApps package is the one most recommend? I used Open GApps Stock, but some of the Google Apps are acting up.
I use Opengapps Pico Arm (not Arm64).
All I can say is that I've installed LineageOS 16 on 2 N5s, 2 N4s and a Lenovo 8" tablet, all with no problems at all. Your problem is not device-specific, since the original query was not for an N6, and I myself know about this "corrupt" problem because I suffered from it myself a year or so ago on my own N6. The procedure I specified has always worked 100% for me every time.
Looking at the LineageOS 16 thread, there is a specific TWRP linked, and MindTheGapps is also linked which is different than openGapps.
If you haven't decrypted by FORMATING user data (not wiping), that may also be a problem.
Thanks, ktmom. The format was part of my instructions, and Flaco05 says he did exactly that. Normally I don't use fastboot to format - I just rely on TWRP and it's worked fine.
I've always used the standard Opengapps Pico and TWRP 3.3.1, no special versions, and they have always worked flawlessly - never any problems. Still, since Flaco05 is having problems, I guess he has nothing to lose by trying the recommended versions...
Thank you all. I will try some of these things tomorrow. I love this community!
dahawthorne said:
With great respect, I doubt that you actually followed the instructions as closely as you think. Unless your N6 has a hardware problem, the instructions will be correct - and I say this not knowing which instructions you followed, but any bad instructions are generally corrected pretty quickly.
To recap (and anyone please correct or amend anything for accuracy - I'll write this from memory):
- download TWRP 3.3.1 from https://twrp.me/motorola/motorolanexus6.html
- flash it in Bootloader - fastboot flash recovery twrp.img
- while you're there, format data - fastboot format userdata (you can also do this in TWRP, but as Elektroschmock says that TWRP formatting isn't perfect...)
- boot into recovery
- wipe everything - all partitions
- transfer your ROM & Gapps - and Magisk if you want root - to your device (recovery allows a direct connection to your PC)
- flash ROM, Gapps, Magisk
- reboot
- report back
Edit: One more thing just in case. If you get a "can't mount system" message, go back to TWRP main screen, Mount, and ensure that the "system read-only" checkbox is unchecked.
Click to expand...
Click to collapse
OK, I did all this, but have been stuck at the Google screen upon reboot for 30 minutes. Is this bad news, or this normal?
No, definitely not normal. A new ROM takes longer to boot but it's generally ten minutes maximum.
Have you tried flashing only the ROM & Gapps, without Magisk? Once you boot successfully you can then flash Magisk later. Try starting again from the top and see if that works.
(P.S. In a slow quiet thread, as this one is at the moment, there's no need to copy the entire post to which you're replying... )
Edit: No, sorry, not from the top. TWRP will still be there after formatting & wiping, so start at the third (format data) part.
Thank you. There is still some kind of a problem. After I finish flashing ROM and Gapps using the instructions, and then reboot (after wiping cache/davlik, right?), I get the Lineage OS logo in motion, and then finally boots into recovery (not system) again. Not sure what to do. Maybe try a different build? I am currently using the latest LineageOS 16 nightly.
Strange. Maybe try LineageOS 15.1?
I enjoy playing with bleeding-edge software, but when you can't get it to work at all then it sort of ruins the fun. A lot of people seem to prefer the stability of 15.1. Personally I never see much difference between even major versions. Maybe I'm just a bit unobservant...
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp
kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!
jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.
Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.
Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later
Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
If TWRP is not available for your device, you can try using this to enable fastbootd. It won't have any TWRP specific features though.
As far as installing a GSI, you simply flash the system.img to /system. It's that simple. Make sure you wipe data.
SukhrobR said:
Hello everyone. Can You please explain how to install GSI to SM-X205? I'm new to fastboot methods. I can't find proper TWRP for this particular model. I have achieved to unlock bootloader which took two steps (In old Android phone it was just easy with switch in developer options). I have installed TWRP from SM-X200 but it's not working. Restored everything by flashing Official Firmware. The main reason why I'm going to this is shortage of storage. I want to format external SD Card as Internal which is not allowed in new Andoirds. Thank you before hands and respect for ones who contribute their knowledge for community.
Click to expand...
Click to collapse
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Piggybacking on this thread to drop some much needed general resources. I installed LineageOS on my s5e last year but struggled to find resources w/ GSI.
I appreciate all the hard work that the devs do, and typically documentation is not their strong suit, so in the future, maybe those of us who benefit from their work can create clearer documentation to spread around the burden a bit:
FAQ that covers topics like what is Treble, what is GSI, what is the naming conventions for GSI files: https://github.com/phhusson/treble_experimentations/wiki/Frequently-Asked-Questions-(FAQ)
Where as example of a GSI I can download : https://github.com/phhusson/treble_experimentations/releases/tag/v416
What should I know going in: Android 13 versions of GSI still have a few compatibility issues as per the first post in this thread. Android 12 is functioning 100% correctly.
Where can I see a more complete list of the GSI options available to me: https://github.com/phhusson/treble_experimentations/wiki/Generic-System-Image-(GSI)-list
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
SukhrobR said:
I have followed all the instructions. But I'm stuck at stage where rebooting to fastboot from TWRP. Touchscreen stops to respond and I can't enable ADB.
Click to expand...
Click to collapse
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
lewmur said:
You don't need to enable ADB. When the screen says "Entering fastboot mode" then you are connected. You can check this by entering "fastboot devices" from your PC.
Click to expand...
Click to collapse
Device list is empty after entering fastboot mode in twrp
SukhrobR said:
Device list is empty after entering fastboot mode in twrp
Click to expand...
Click to collapse
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
lewmur said:
Do you have the latest version of the Samsung USB drivers? Earlier versions don't have the fastboot driver.
Click to expand...
Click to collapse
Yes I do. I think it dependable on firmware version.
w00tnezz said:
SM-X205 installs the same as SM-X200 - I've followed all the instructions for any TWRP, root, GSI, etc and it all works as others X200's. I've not lost anything on the X205.
Click to expand...
Click to collapse
Does this allow me to use this (https://forum.xda-developers.com/t/...0-for-2021-galaxy-tab-a8-10-5-sm-x200.4488691) for my SM-X205?