Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
gbetous said:
Hi all,
I made a huuuuuuge mistake : after a failing update of Magisk (don't know why, I already made zillion of updates), my phone is stuck in fastboot mode. And now is the big mistake : I performed a "fastboot lock" (don't ask why, stupid is stupid).
=> I can't boot in recovery because TWRP is not official
=> I can't unlock it as to unlock, I have to boot a full image and select "allow OEM unlock" in the system preferences
=> I can't even flash stock boot.img or system.img (I could find stock firmware), beacause I receive this error :
$ fastboot flash boot boot.img
Sending 'boot' (18472 KB) OKAY [ 0.551s]
Writing 'boot' FAILED (remote: 'device is locked. Cannot flash images')
fastboot: error: Command failed
Any idea on how to recovery my phone ? :crying:
Click to expand...
Click to collapse
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
totalnoob34 said:
You should be able to flash a stock kdz
Sent from my LG-H850 using XDA Labs
Click to expand...
Click to collapse
Yes !
I used the official LG tool for recovery (see www.lg.com). The magic key is "vol UP + USB plug" and the phone switches in some specific recovery mode. Nothing particular to do, the tool is automatically downloading the latest offical firmware and flash it.
Thanks !!!
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
---------- Post added at 09:47 AM ---------- Previous post was at 09:40 AM ----------
tremalnaik said:
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Heck. I just upgraded but didn't reboot yet, can I install 20.1 via magisk manager and be safe?
Sent from my LG-H850 using XDA Labs
I think that Magisk Manager already patched the boot image, I don't know whst will happen if you patch the 20.2 version with the 20.1. I would suggest you to check in /data/ folder for the boot image backup, copying them to pc if they are there, and then trying to reboot directly into recovery (Magisk Manager>Modules>Menu>Reboot to recovery) and from there flash back the old boot image. In case after reboot you get into fastboot, you can just flash the backup boot image with fastboot flash boot boot.img
tremalnaik said:
Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
tremalnaik said:
To others who have still the phone unlocked: just flash twrp to boot partition. Then boot, you will be in twrp. From there, copy the backup files in /data/ folder to the pc and flash them back with fastboot flash boot boot.img. Tha backups are gz compressed, so you need to extract them before flashing. At the end you will have back Magisk 20.1 and everything else working.
PS. Magisk 20.2 causes LG phones to be stuck in fastboot mode. This has been observed on LG V20, LG G5 and LG G6. So better wait before upgrading Magisk on our devices.
Click to expand...
Click to collapse
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
SrZambie said:
My G5 (H830) didn't go into fastboot mode. Are you on stock ROM?
Click to expand...
Click to collapse
Yes, stock Oreo ROM with MK2000 kernel.
tinyspeck said:
My H850 was stuck in fastboot mode after magisk update. I entered in TWRP and reinstall the kernel. Now, it is stuck on LG logo It seems that System is damaged too. Does someone know what magisk have changed in the System partition? Probably it can be fixed somehow...
For the future, my plan is to cut magisk internet access from the firewall settings, so it will be updated just never.
---------- Post added at 10:25 PM ---------- Previous post was at 10:09 PM ----------
Can you please provide more details about what is backed up in /data and how it can restore the System? I looked in /data and /data/backups but I can't find something like a system backup...
Click to expand...
Click to collapse
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
Click to expand...
Click to collapse
I looked around and found that this isn't LG specific. Someone with the Razor Phone 2 had their partitions wiped aswell. It sounds like it's having issues installing with certain ROMs which would explain why I wasn't affected. It's best to stay with 20.1 on stock ROMs for right now until it's fixed.
tremalnaik said:
Yes, stock Oreo ROM with MK2000 kernel.
System is by definition what Magisk shouldn't touch. Are you stuck on the static LG logo or the animated one?
In /data/ folder you should find at least one folder named "magisk" with others letters following. Inside of it you will find a compressed archive with the boot image inside. You can flash it back with both TWRP or fastboot.
Click to expand...
Click to collapse
It was stuck on static LG logo. I reflashed the same kernel which I installed last July (mk2000 v2.1). I also wiped cache and dalvik (kernel shouldn't need this but just in case...). It is strange that it stuck on static LG logo because later, I followed your advice and I installed the boot.img from /data/magisk_123... and the phone is back, working as new
So magisk is not so bad as it has a backup solution.
Thanks for your support
Static logo is loaded before system, so the problem wasn't the system partition. Probably my phone couldn't load boot partition at all, falling back to fastboot, while yours was loading boot partition but an error was occourring the meanwhile, leaving it at the logo. I'm glad that you solved the problem.
While reinstalling Magisk after the kernel, don't forget to check if the torch is still working: if it's not working, just flash once again the kernel and it should be ok.
Related
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
LucasBS1 said:
My Moto E Hangs when I try to boot a TWRP image
Attempted procedure:
(After booting into stock fastboot)
Code:
fastboot boot twrp-2.7.1.0-condor.img
A reboot to that TWRP was expected instead. But it freezes on bootloader.
TWRP used on the attempt:
dl.twrp.me/condor/twrp-2.7.1.0-condor.img.html
I don't want to flash a different recovery or anything else, just a clean root.
Moto E XT1025 DTV Dual BR
4.4.4
21.12.40.condor_retbr_tv_ds.retvr.en.BR.retbr
Click to expand...
Click to collapse
Sometimes booting recovery doesn't work...You will have to flash it. Perhaps you can flash the stock recovery after successful root? though i am not sure that will work
Also try booting into CWM
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
LucasBS1 said:
Tried the same method with CWM.img
Same result: fastboot frozen (volume buttons not responsive, and PC no longer sends commands)
To flash the stock recovery I would need to back it up first
But guess what's needed to backup ?
Yes, a temporary flashed bootloader with ZIP support
Would you know someone, who knows someone, who knows an master from MTI or Hogwarts or Narnia that knows an alternative ?
I would flash a mod right away if I could backup the original first...
(Unless, as I don't know exactly how this works, the ROM might come with the bootloader (?) Because the stock ROM I can download easily anywhere (already did))
Click to expand...
Click to collapse
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
giaur said:
Hi,
Did you managed it to work? I have exactly the same problem. If I even flash twrp or cwm I still can't boot into it, there is only "no command" message.
I can't get any help anywhere, it makes me crazy. Do you have any custom recovery that worked for you after flashing?? I'm even starting to think that my device is broken somehow.
Click to expand...
Click to collapse
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
LucasBS1 said:
I did NOT flash the recovery yet
I'm trying to run the recovery without flashing it, to avoid problems like yours
You said you flashed both CWM and TWRP ?
And Neither one of them worked ?
I'm screwed too, then...
:crying:
See if you can find the stock recovery somewhere
And NOT here
This forum is not good for it
It's too much phone specific... too narrow... and we get no attention; specially with our "not-mainstream" phone
Generic instruction could work
If you take any action, or find any forum you find helpful, let me know
Click to expand...
Click to collapse
None of them worked. I'm going to resign, because there is nothing I can do. Seems you have exactly the same problem as me. What I tried:
- fastboot boot recovery.img. Phone hangs on bootlogo
- flash recovery, then use go to recovery option in fastboot menu. In this case, 2 possibilities: with usb cable connected, it boots normally to system, not to recovery. With usb cable disconnected, screen goes black and phone looks like powered off. You will need to power it on and it will boot to system.
- On running system with usb debugging enabled. If you type "adb reboot recovery", you will end with dead robot and "no command" error. You can however press VolUP +Power on this screen and you will see Android 3e recovery.
If you have the same problem as me, you are completly lost and it's impossible to intall recovery on your device. I'm close to resign and say "**** this ****ty phone" because (as you already mentioned), there is no any attention on my questions, twrp support was dropped long time ago etc.
Flashing recovery should not wipe your data, so once you try to flash twrp or cwm, please let me know about your results. I'm sure I will never able to solve this problem, but I will feel better knowing that I'm not alone whit it
---------- Post added at 06:05 PM ---------- Previous post was at 06:00 PM ----------
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
Still the same, I'm on stock recovery. In console, no errors:
Code:
[email protected]:~/android/DO_MOTOROLI/twrp/2.8.5$ fastboot flash recovery twrp2.8.5.0-recovery.img
target reported max download size of 299892736 bytes
sending 'recovery' (9046 KB)...
OKAY [ 0.312s]
writing 'recovery'...
OKAY [ 0.860s]
finished. total time: 1.172s
But "adb reboot recovery" - "No command". Damn it...
---------- Post added at 06:26 PM ---------- Previous post was at 06:05 PM ----------
Ok, I'm finished. It's not possible. F U C K Motorola and good night. My advice: don't waste your time if you have the same problem. You will get nothing, except wasted time. It's good that it's not my phone (I own OnePlus One). But I was asked to install CM12.1 on my friend's phone. It's impossible, so I will need to tell him I was failed with that.
mepsilon2 said:
@giaur @LucasBS1
I too have tried booting the recovery ,but it doesn't work. You will have to flash it
if you are seeing 'no command' message it means that you still have stock recovery and the custom recovery wasn't flashed successfully.
try this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-2-0-touch-recovery-t2971601
or this one http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3100879
Click to expand...
Click to collapse
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Seeing giaur on that situation puts me stepping back...
LucasBS1 said:
I see people complaining about bugs or not-working features on the first link
Are you sure it's safe ?
It's not the official TWRP (apparently)
When I google for this bootloader the official page shows version 2.7.1.0
Whereas on your second link they are on the 2.8.2.0
Which one should I trust ?
And to anyone who might answer:
Trough PC is the only/safest way to flash these recoveries ?
Click to expand...
Click to collapse
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
giaur said:
I tested both: latest official 2.7 and linked 2.8. So they are safe. Official support for Moto E was dropped long time ago.
Click to expand...
Click to collapse
Cool
Regarding to safety
Should I flash CWM or TWRP ? Why ?
Regarding the method
Flash through usb->Fastboot or through Apk (like CWM)
Or a third method ?
And why
Between TWRP 2.7 and 2.8, which one is safer ?
And of course...why ?
And a last question, before I leave you guys alone:
Did you manage to root the phone, despite the poblems occurring to you, giaur ?
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Yo !
Flashed TWRP
But wiped things I shouldnt
How to put the ROM back via USB ?
EDIT:
NEVERMIND
Found how to use SD to do that
giaur said:
Once you succesfuly flash twrp, you need to flash supersu then and you are rooted. If you don't have your current system rooted, the only way to flash custom recovery is to flash via fastboot. TWRP is recommended, because it's way better
I can't say anything more, because my moto e is not flashable, so I can't replace stock recovery.
Click to expand...
Click to collapse
I was also struggling a lot many days into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power after executing
Code:
fastboot.exe flash recovery twrp-2.8.1.0-condor.img
. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
Hi,
sorry if i'm the 100th person to ask this question but how can i go back to the stock ROM with OTA?
I currently have a flavor of LinageOS with the Turbo Z kernel installed on my phone but it's just to buggy for me. I want to have root access on my phone for various reasons though.
I tried to just download different (6.0/7.0) stock ROM files but i can't install them with TWRP. I know that 7.1.x was released but i can not find the ROM for it.
What is the easiest way to just go back to a stock ROM? I know my way around the console but i don't want to brick my phone. I made backups of my files and also with TWRP so data loss is not an issue.
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
First things first.
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Use the fastboot flash / erase commands, as in this thread:
https://forum.xda-developers.com/showpost.php?p=73119650&postcount=1
If at any stage your phone get bricked, ie, black screen after reboot, no charging, etc. Use these instructions. They saved me in the last week from returning my device for a replacement(and paying $350.00):
https://forum.xda-developers.com/showpost.php?p=71874880&postcount=1
lollyjay said:
https://forum.xda-developers.com/moto-z/how-to/how-to-update-to-official-7-1-1-moto-z-t3640298
Click to expand...
Click to collapse
Does this work for the EU version too? I'm not sure if the baseband thingy is compatible. I'll need a EU ROM otherwise but i can't find any for Android 7 :/
bert269 said:
On which bootloader are you, MM or are you on Nougat. If your device has been flashed with the 7(N) bootloader, you cannot flash the 6.0 stock, you will have to stay of 7.
Click to expand...
Click to collapse
I've already updated to Android 7 so i guess i've to use a stock Nougat ROM.
Read my last post on page 15 of this thread
https://forum.xda-developers.com/moto-z/how-to/guide-how-to-root-moto-z-supersu-t3551113/page15
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
If you didn't take a backup of your stock boot and recovery before, then i think you'll have to go the long way by flashing the whole rom.
If you manage to install the 7.1.1 OTA after that, boot once into TWRP, backup stock recovery & boot and save it on your sdcard/pc. Then you can start flashing TWRP permantly, root, etc
Someone correct me, if I'm wrong.
Byte_76 said:
Where can I find the stock recovery for XT1650-03 RETEU without downloading an entire ROM zip file?
I have stock 7.0.0 with TWRP and Magisk 13.3.
I want to install the stock recovery so that I can install the 7.1.1 OTA which is available on my device, after which I will flash TWRP and root again. Will this work?
Click to expand...
Click to collapse
What is your build number?
lollyjay said:
What is your build number?
Click to expand...
Click to collapse
The current build number is NPLS25.86-30-12
Byte_76 said:
The current build number is NPLS25.86-30-12
Click to expand...
Click to collapse
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
lollyjay said:
Here is my recovery.img for NPLS25.86-30-12
https://drive.google.com/file/d/0B3gcDbDvV4MkOHhPd0lBVE9IMzg/view?usp=drivesdk
It should work for reteu also if not you can just reflash twrp:cyclops:
Click to expand...
Click to collapse
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Byte_76 said:
Thank you!
---------- Post added at 12:31 AM ---------- Previous post was at 12:15 AM ----------
Your recovery works on my Moto Z.
I now have stock 7.0.0 rooted with Magisk 13.3, stock recovery and unlocked bootloader.
If I proceed with the 7.1.1 OTA, will it work?
Click to expand...
Click to collapse
You must have fully stock. I would suggest that you uninstall Magisk
lollyjay said:
You must have fully stock. I would suggest that you uninstall Magisk
Click to expand...
Click to collapse
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Byte_76 said:
The reason that I installed Magisk is because after unlocking the bootloader with the stock rom, it would not boot anymore. Installing a custom kernel or Magisk solves that issue.
Click to expand...
Click to collapse
I still would suggest that you uninstall Magisk because the OTA would not work.
lollyjay said:
I still would suggest that you uninstall Magisk because the OTA would not work.
Click to expand...
Click to collapse
Okay I uninstalled Magisk which initiated an immediate reboot and resulted in a bootloop just after the bootloader message.
I think the issue occurs because the Data partition gets encrypted when root is uninstalled and decrpyption fails because of a bad key due to the unlocked bootloader.
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption. I then ran "fastboot continue" after which my phone booted back into Android:
https://forum.xda-developers.com/moto-z/help/bricked-moto-z-unlocking-bootlader-t3634701
My phone status was then: Stock Android 7.0.0, no_verity patch (no encryption), stock recovery, unlocked bootloader.
So my phone is about as close to stock as I can get it with unlocked bootloader.
I finally attempted to install the 7.1.1 OTA again. It reboots and indicates that it is installing and then pops up with a message that says "Error".
Pressing the power and up button brings up the recovery screen with the error log (with info that I don't understand) and from there I can reboot into system again where I get another message indicating that the update failed and no changes were made.
I'm hesitant to install RETBR or other non-RETEU roms (Because although they might work, there probably are some differences such as LTE bands etc. and they are not actually correct for my phone) so I'm not sure how else to get to 7.1.1 unless the wifi issue is resolved with the image that Erfanoabdi uploaded in another thread or Lenovo releases an official 7.1.1 firmware package for the RETEU model.
Byte_76 said:
.....
To recover, I used TWRP to wipe/format the Data partition and then flashed the no_verity zip file from the thread below which disables encryption.........
Click to expand...
Click to collapse
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
bert269 said:
You still have a modified ROM as you flashed "no_verity patch"
The best for you would be to search for your version of ROM and FASTBOOT FLASH everything back.
Then see if the 7.1.1 OTA wants to stick.
Click to expand...
Click to collapse
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Byte_76 said:
So far I have been unable to find the official RETEU firmware from Adnroid 7.0.0 and I'm hesitant to flash the firmware for another region because it isn't technically correct for my phone and there are likely small differences that might become an issue at a later stage. (Maybe the LTE bands are different etc...)
Click to expand...
Click to collapse
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
bullfinch110 said:
The LTE band on RETEU is 20 and stays 20 with RETBR. No change and everything works. No issues with LTE.
As I mentioned before, the RETBR version is the only working 7.0 backup for RETEU devices. After flashing RETBR , the softwarechannel changed automatically into RETEU. With this, i took the OTA 7.1.1.
Btw. the 7.1.1 OTA doesn't even change the boot loader Nr.( 0x9107). That means, if you mess up with 7.1.1 you can safely downgrade to 7.0 by flashing RETBR (and take a fresh 7.1.1 OTA again)
Did that twice without issues.(for security reason i always skip the two lines with "bootloader" and "gpt" at the top of the flash commands)
Click to expand...
Click to collapse
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
---------- Post added at 08:46 PM ---------- Previous post was at 08:40 PM ----------
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
Are these the commands that I should run?
fastboot flash partition gpt.bin
fastboot flash motoboot boot.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash system system.img_sparsechunk.10
fastboot flash system system.img_sparsechunk.11
fastboot flash system system.img_sparsechunk.12
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Byte_76 said:
Thank you for the clarification. I will take your advice and flash the RETBR firmware.
---------- Post added at 08:40 PM ---------- Previous post was at 08:01 PM ----------
I cannot get RSDLite to detect my phone in fastboot mode so I guess I'm going to have to run the fastboot commands manually.
What do you mean about skipping the bootloader and gpt commands? If I skip those, I keep my stock "unlocked bootloader" and "gpt" but then the phone probably won't boot again because that is very much like what I have now except that I flashed the no_verity patch when my phone would not boot.
What exactly are you avoiding by skipping those two lines? Should I skip them too?
Click to expand...
Click to collapse
It's out of my knowledge if your verity patch influences either bootloader or gpt partition. So i would recommend to flash those two commands in order to "repair" them. If you'll get an error message, skip them and proceed with the rest.
I always prefer RSD method instead of manually flashing by fastboot commands.
Have you installed the latest version of RSD-lite 6.2.4? Have you installed the latest moto drivers?
If you have extracted the RETBR. zip, search for "flashall.xml" file. Open it with a texteditor and you'll find the correct flashing commands.
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
How did you prepare this?
Do you also have flashable .img of TWRP for G6 Plus?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
Simple Great!
For me adb sideload dont work, even when i type "adb devices" or "sudo adb devices" just appear "no devices/emulators detected" but when I use twrp via "sudo fastboot boot twrp.img" all works propertly. Although i type adb kill-server and sudo adb start-server no fix that than in the another method it works. I think maybe is for version (3.2.3-0) works and in your (3.2.1-0) dont (?) or Is by in one Is installed on the devices and the another not (?)
Thanks in advance for an posible solution. Grettings from México
Many thanks in advance segra246x.
Unfortunately for me, every time I´ve flashed TWRP, then I do not know what may i do to reboot the phone. My phone is unlocked and I am root with Magisk, so I do not know which boot should I flash at the end, so that it starts again and does not stay in a loop with TWRP or in brick.
Couls you tell wich procedure are you using to can start the device normally?
i flashed patched boot image, Should i flash boot patched boot image and re-start again Magisck instalation? Should i flash boot boot.image from the regarding stocke version without loosing root satus?
Thank you, the twrp works fine installed with stock Oreo 8.0.
Worked on G6+ with Pie. Thank you!
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
Please explain your process & is it still working? What version are you on with 9.0?
---------- Post added at 10:04 PM ---------- Previous post was at 10:00 PM ----------
thump said:
Worked on G6+ with Pie. Thank you!
Click to expand...
Click to collapse
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
This method still working for you?? And I don't see any credits so did you create this installer??
I used the exact file and the 5 step method outlined in the original post.
Hey did you create this?
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooed with magisk!!
Click to expand...
Click to collapse
I can't find any credits.
---------- Post added at 08:11 AM ---------- Previous post was at 08:02 AM ----------
segra246x said:
Simple way to install TWRP on Moto G6 plus!!
1. download the twrp-installer.zip
2. boot in TWRP via fastboot boot twrp.img
3. flash twrp-installer.zip to overwrite stock recovery
4. flash the magisk.zip because step 3. will patch your boot.img
5. it's done! you can start TWRP easily like on A-only-slot devices
Works perfect for my Moto G6 plus rooted with magisk!!
Click to expand...
Click to collapse
**I noticed that you have not been logged in here for
about a month. When you get back please inform me.
I have an error to flash the twrp, how did you do it?
Instructions..
HorryStorm said:
I have an error to flash the twrp, how did you do it?
Click to expand...
Click to collapse
Follow the directions. Couldn't be more simple.
First use our official TWRP 3-2-3-0 to BOOT into
There you flash this installer.
I have used this installer and can say it's good.
MPT works.. you can then reboot to recovery at
Anytime. Hope that's helpful. Good luck.
--Ken
the question is that when I try to make the flash it appears a maximum size error.
This is only for Moto G6 Plus. If that's your device
Then idk. I've installed it several times and never had
An issue.
Ok, thanks.
I dont have OS Pie9 after flashing twrp
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
---------- Post added at 01:29 PM ---------- Previous post was at 01:10 PM ----------
lavriiga said:
My step was,
1. flashing Pie9 with cmd in fastboot
2. then i boot in twrp.img and install zip twrp ...
Click to expand...
Click to collapse
I fix it, First i flash PIE 9.0
Then i boot in twrp.img in fastboot
Then zip TWRP.zip and after that i install MAGISK 17.1 And it works ! Thanks for posts !!!:good::laugh::laugh::laugh:
Secure Startup Password
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G6-Moto-G6-Plus-Moto-G6/G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
roomfool said:
First off thank you segra246x for making this. I had no problem following the instructions and got TWRP installed with no issue. I have also been able to successfully flash a bunch of different Pie GSIs (phhTreble, AOSP Extended) successfully.
I do however have a question that I cannot seem to find the answer too anywhere for the Moto G6 Plus. On past devices (i.e. Moto G5 Plus) I was able to configure the device to require a password or pin or pattern before the device would boot. Similarly TWRP would require this in order to mount /data. Depending on where you are looking online this could be called Secure Boot or Secure Startup. On this device however I cannot find the option when I set the password with any version of Android to require the boot password. This means that all it takes to decrypt and copy my data partition is a hard reset into recovery.
I have done a fair bit of research into this to see if I was just missing a step or a missed step with no luck. I saw some posts from Motorolla / Lenovo that indicate this is no longer an option, I will post links below for the interested. I also saw a Moto G6 post talking about having to format, reboot into recovery, format again to get the decryption to work. I knew that it would be long shot but I gave this a try just in case but it did not help.
Does anyone have any information about this device, TWRP and secure boot? I know that decrypting /data in TWRP can be difficult but if I had to choose I would rather data partition is never mountable by TWRP over mountable with no password. Any information would be greatly appreciated. Thanks.
Motorolla Post indicating that Moto G6 Plus uses direct boot instead of secure boot
https://forums.lenovo.com/t5/Moto-G...G6-Plus-can-t-find-Secure-Startup/m-p/4311477
Motorolla Post indicating this is new encryption method
https://support.motorola.com/uk/en/solution/MS129140
Click to expand...
Click to collapse
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Thanks
randomanonymousname said:
Hi, this has to do with the rom I think. I had LineageOS 15.1 installed and I had to decrypt the data with my password before I could do anything in twrp. I currently have the option to encrypt my phone on HavocOS under the security tab, but it doesn't work for now =))). On LOS15.1 it was enabled by default, so give it a try if this concerns you so much.
Click to expand...
Click to collapse
OK I was not sure if this was more related to the ROM or TWRP, my bad for posting in the wrong place. I have tried the AOSPExtended 9 ROM and all 3 flavors of the phh treble 9 ROM with the same result. Have not had any luck installing Lineage or any of the 8.1 phh treble ROMs. I will keep digging to see if I can't find some info about this. Thanks.
Hi, my backups get stuck at 80-90% sometimes, does anyone have the same issue?
Hi everyone. I have android 9.1.0.132. Trying to root with magisk via twrp, but not working. Anyone did root EMUI 9?
You need to patch your recovery ramdisk image. backup image with twrp or fastboot, patch with magisk manager and flash as recovery (same way you'd flash twrp)
You then need to boot your phone every time via recovery. It'll boot into android as normal but with root.
I don't know how to backup image with fastboot. Im twrp pretoriano80 don't know whitch partition backup. Please some insruction
you need to be bootloader unlocked
here are magisk patched recovery from 9.1.0.134 emui 9 version
next, you need in fastboot "fastboot flash recovery_ramdisk magisk_patched.img" flash it (hope you know how to flash img ??)
then, you need fastboot reboot, remuve usb
this is critical, when you see:
""your device unlocked and cant be trusted
1 pres power to boot
2 pres volume up 3 sec to boot in erecovery
3 dont do anything ... """
when you see this, pres and hold volume up and power button till phone reboot and you see different warning, then relase buttons and wait till phone boots in system
next, instal magisk manager, find in google!
Great dude, awesome, it's working. Sometimes recovery must be flashed again (don't know why is happens). After next restart must flash it again or will be working each time?
THANKS!!!!!!!
Cisuwek said:
Great dude, awesome, it's working. Sometimes recovery must be flashed again (don't know why is happens). After next restart must flash it again or will be working each time?
THANKS!!!!!!!
Click to expand...
Click to collapse
When restarting your phone, make sure you press volume up + power, to boot in recovery. That way you should not have to flash again. If however, you forget to press this combo, your recovery get's replaced with the stock and you'll have to flash it again.
ConsoleHax said:
When restarting your phone, make sure you press volume up + power, to boot in recovery. That way you should not have to flash again. If however, you forget to press this combo, your recovery get's replaced with the stock and you'll have to flash it again.
Click to expand...
Click to collapse
i was thinking that when we use your guide then we do not have twrp installed if we need the stock recovery_ramdisk patched.. so use the erecovery_ramdisk for twrp, also its easyer to enter .. its just to hold the vol+ for 3 sek ... and bum your in twrp..
it works tested it...
ps.
fastboot will not let us flash erecovery_ramdisk so before replacing recovery_ramdisk use twrp to flash the twrp into erecovery_ramdisk ..
then replace recovery_ramdisk with patched img
@brokenworm: could you please explain your ps? I am not really a newbie, but I have no glue, what you talking about?!
oTTo001 said:
@brokenworm: could you please explain your ps? I am not really a newbie, but I have no glue, what you talking about?!
Click to expand...
Click to collapse
Answer is simple ... First fastboot flash recovery_ramdisk TWRP.img .... then enter recovery..
Now from Twrp recovery flash TWRP.img into Erecovery_ramdisk... Now flash the magisk patched recovery_ramdisk either with fastboot or from twrp before exiting into partition recovery_ramdisk.
Erecovery_ramdisk can only be flashed like that becoes fastboot blocks it.
The solution for still having twrp in 9.1 emui roms... Also editing vendor give us the solution to backup and restore a complete nandroid backup. AND this way you do not need to hold a button every time you restart .. from twrp you only need to push reboot recovery to enter the rom ONCE ! AND it will stick .. only "bug" is your phone can not poweroff .. actually good if it gets stolen..
Look here : https://forum.xda-developers.com/hu...w-to-remove-data-encryption-emui-9-1-t3953946
Recovery_ramdisk = vol+ & power.
Erecovery_ramdisk = vol+
Bootloader = vol- & power
This way we dont need to hold a button when rebooting....... twrp fixes that automaticly .. you need to boot in to rom from twrp placed in erecovery_ramdisk by selecting "reboot recovery" instead of "reboot system"... Then it will boot correctly everytime.
And you only have to do this one time.
I have not try but thanks
Hi!
I own an ANE-LX1 device with EMUI9.1
I did everything exactly as described in this or in other threads but I am still unable to root
Just to quickly summarize:
1. my bootloader is unlocked
2. using Magisk app I patched the stock recovery image (recovery_ramdis.img)
3. using fastboot I flashed the patched image
4. now the next step is pretty much unclear for me: reboot the system to what target? all XDA threads (including this one) description at this point sucks! sorry for bad words but this is true
5. anyway tried to reboot to the recovery - this is not possible - I only see exactly the below messages, no matter how long I wait:
Code:
Your device has been unlocked and can't be trusted.
To learn more visit:
http://zh.ui.vmall.com/emotiondownload.php?mod=restore
Your device is booting now...
Tried any possible combination, like disconnect USB cable, keep USB cable, reboot normally, reboot to eRecovery, no matter which one, the result is:
When I check in the Magisk manager app, itt tells: Magisk is not installed.
So please anybody who has successfully rooted, can u make a video showing the whole rooting process, but especially with the step after fastboot flash, i.e. how exactly to reboot, what buttons to press/hold up to the state where the Magisk Manager app shows: Rooted.
I am able to pay for the video! Seriously!!!
PS:
Besides all the description and tutorial it is not clear for me, why should be the system rooted, when we patch only the recovery_ramdisk image/partition. It somehow makes no sense.
I need root for my running EMUI system, and not for the recovery.
Thanks and regards,
Ladislav
Videophile said:
You need to patch your recovery ramdisk image. backup image with twrp or fastboot, patch with magisk manager and flash as recovery (same way you'd flash twrp)
You then need to boot your phone every time via recovery. It'll boot into android as normal but with root.
Click to expand...
Click to collapse
What do you exactly mean by
"You then need to boot your phone every time via recovery."?
Can u pls explain it step by step?
What and how did you do after fastboot flash?
Also see my previous comment...
I have rooted my P20 lite with the steps from this thread. Today my phone notified my that there was a firmware update (from 9.1.0.200 to 9.1.0.208). But I'm stuck in the update process. I can not boot to a recovery to update. Can anyone get me some advice?
Kwakkel said:
I have rooted my P20 lite with the steps from this thread. Today my phone notified my that there was a firmware update (from 9.1.0.200 to 9.1.0.208). But I'm stuck in the update process. I can not boot to a recovery to update. Can anyone get me some advice?
Click to expand...
Click to collapse
With Huawei HiSuite program and the device's fastboot mode you can restore the device.
Once u successfully restored it, can u pls make a video where you show, how did you root your phone and shar it with me?
Kwakkel said:
I have rooted my P20 lite with the steps from this thread. Today my phone notified my that there was a firmware update (from 9.1.0.200 to 9.1.0.208). But I'm stuck in the update process. I can not boot to a recovery to update. Can anyone get me some advice?
Click to expand...
Click to collapse
Before update you need in fastboot flash original recovery, because magisk patched recovery are booting in system with root acces, so you can't update phone while it are rooted
---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------
ladislav.heller said:
With Huawei HiSuite program and the device's fastboot mode you can restore the device.
Once u successfully restored it, can u pls make a video where you show, how did you root your phone and shar it with me?
Click to expand...
Click to collapse
Hei!
Your phone are bootloader locked or unlocked ?
If you have not bootloader code, aka unlocked bootloader, you can't root phone, because we need patch ramdisk.img with magisk manager and flash it in fastboot using fastboot flash recovery_ramdisk magiskpatchedramdiak.img
Arnys said:
Hei!
Your phone are bootloader locked or unlocked ?
If you have not bootloader code, aka unlocked bootloader, you can't root phone, because we need patch ramdisk.img with magisk manager and flash it in fastboot using fastboot flash recovery_ramdisk magiskpatchedramdiak.img
Click to expand...
Click to collapse
Check the post #11 please. I desribed everything there.
Tapatalkkal küldve az én ANE-LX1 eszközömről
ladislav.heller said:
Check the post #11 please. I desribed everything there.
Tapatalkkal küldve az én ANE-LX1 eszközömről
Click to expand...
Click to collapse
when will be next phone software update i will create video, how i update it, how i root, etc. works for you.?
its like ~40 days, i hope update will come sooner than that!!
Da hell, i can try it now , will flash original, then pach it with magisk ,and then, wait video!
lol, 10 min 1gb video file, i will edit it litle bit, convert etc...
okey. Video redy.
Before you patsch recovery_ramdisk with magisk manager, use thease setings, see picture here : Picture, lol
Chek all 3 boxes in advanced setings! then patch recovery_ramdis.img
video here : youtube (not the best quality, sorry, did it in fast)
my files here : magisk_patched.img for root, RECOVERY_RAMDIS208.img original, to update phone, app-release.apk magisk manager i used
Oh, and buttons i presed after fastboot flash recovery_ramdisk magisk_patched.img is volume up and power!
But, there are BUT, if you previous played with root, and did some strange things, your phone can stuck in huawei logo, if thats happens, you need to restore original software with dload method!!
@ladislav.heller
Arnys said:
when will be next phone software update i will create video, how i update it, how i root, etc. works for you.?
its like ~40 days, i hope update will come sooner than that!!
Da hell, i can try it now , will flash original, then pach it with magisk ,and then, wait video!
lol, 10 min 1gb video file, i will edit it litle bit, convert etc...
okey. Video redy.
Before you patsch recovery_ramdisk with magisk manager, use thease setings, see picture here : Picture, lol
video here : youtube (not the best quality, sorry, did it in fast)
my files here : magisk_patched.img for root, RECOVERY_RAMDIS208.img original, to update phone, app-release.apk magisk manager i used
But, there are BUT, if you previous played with root, and did some strange things, your phone can stuck in huawei logo, if thats happens, you need to restore original software with dload method!!
@ladislav.heller
Click to expand...
Click to collapse
Thank you!!!
Tapatalkkal küldve az én ANE-LX1 eszközömről
Arnys said:
when will be next phone software update i will create video, how i update it, how i root, etc. works for you.?
its like ~40 days, i hope update will come sooner than that!!
Da hell, i can try it now , will flash original, then pach it with magisk ,and then, wait video!
lol, 10 min 1gb video file, i will edit it litle bit, convert etc...
okey. Video redy.
Before you patsch recovery_ramdisk with magisk manager, use thease setings, see picture here : Picture, lol
Chek all 3 boxes in advanced setings! then patch recovery_ramdis.img
video here : youtube (not the best quality, sorry, did it in fast)
my files here : magisk_patched.img for root, RECOVERY_RAMDIS208.img original, to update phone, app-release.apk magisk manager i used
Oh, and buttons i presed after fastboot flash recovery_ramdisk magisk_patched.img is volume up and power!
But, there are BUT, if you previous played with root, and did some strange things, your phone can stuck in huawei logo, if thats happens, you need to restore original software with dload method!!
@ladislav.heller
Click to expand...
Click to collapse
I did exactly what you did in video, but I still can't properly reboot.
When I press Volume Up + Power after flash, the device reboots and stucks at the screen after Huawei logo and I see only the well known:
Code:
Your device is booting now...
message but it never starts the system, at least I did wait 10 minutes and nothing happened, while on your video after reboot with key combination your phone booted into normal system after cca. 1 minute.
I'll try to reflash the whole system via dload method and try again from beginning.
OK, so finally I also was able to root my ANE-LX1.
But it worked only after I reflashed the whole system via dload method.
Many thanks, @Arnys for the tips!
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
felloguard123 said:
I unlocked bootloader (critical aswell) today and installed twrp on my A3. The device is NOT rooted
Weird thing is I can't use my wifi anymore, anytime I try to toggle it on it just jumps back.
Anyone knows what caused this and how I can fix it?
Click to expand...
Click to collapse
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
It seems your boot.img corrupted. If you format data and wipe dalvik cache data and flash stock rom you will succeed i think
---------- Post added at 10:22 PM ---------- Previous post was at 10:18 PM ----------
https://c.mi.com/oc/miuidownload/detail?device=1900372
download official xiaomi mi a3 rom here. and flash it via pc and you will have brand new stock rom. Try it if you fail i will help you when i have free time
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
I was stupid and thought I did it without a boot image untill I checked all of my commands again.
I used fastboot flash boot twrp-3.3.1-15-laurel_sprout-mauronofrio.img .
My phone was on V10.3.9.0 EUropean. But that image file is for twrp or is it also a boot.img? Not sure if this caused the problem? I'm very new to all of this so how can I find a stock boot.img of that version and how do I flash it again? I feel kinda lost right now.
Anyone can help me out with this?
felloguard123 said:
Anyone can help me out with this?
Click to expand...
Click to collapse
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
antoine62 said:
This phone has the recovery inside the boot partition, this is why you need to flash the boot partition, you do not need to flash it again normally, you just flash it to the other slot, boot twrp, go back on the original slot, flash twrp using the .zip file, idk where you should get the boot.img file, but lok online for it, maybe you will find it.
EDIT: https://github.com/AndroidDumps/xia...KQ1.190416.001-V10.3.9.0.PFQMIXM-release-keys
Click to expand...
Click to collapse
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
felloguard123 said:
But what was the my fault here? What did I wrong? Was it the .img file of the twrp or did I install it wrongly? I am very new to this and don't understand why there are 2 slots etc. Sorry for the confusion.
Click to expand...
Click to collapse
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
antoine62 said:
You installed it uncorrectly, you need to switch slot (because this device have an A/B partition type), flash twrp, boot it, switch to the og slot, flash twrp using the .zip file (so it modify your current boot.img), and done.
This phone will be my first A/B phone, i cant wait to receive it.
But what you didnt is still correct, just not perfect.
Click to expand...
Click to collapse
So twrp has to be installed on both partitions?
I'm not sure if really twrp installed on only one partition could cause Wifi problems.
I would assume that my .img for twrp was faulty.
a
garylawwd said:
Did you flash any boot.img when installing twrp? Or after you installed twrp?
If you did that is more than likely the problem. Flash original stock boot.img from the same security patch date as your firmware and flash it in twrp and then flash twrp installer afterwards
Click to expand...
Click to collapse
and how to do that:{?
i have same problem as yours and searched too many videos on youtube but then i have decided to remove the twrp from the device and no one yet has told me that how to flash twrp in another partition rather i dont know what is the another partition