Related
Guys please help me.. I have a query.
I just unlocked bootloader and want to follow the following procedure, please tell me if I'm doing anything wrong
Flash twrp using fastboot command
Flash lazy flasher using twrp
Flash magisk(for root purpose) using twrp
Reflash stock recovery img using fastboot command
If i follow the above procedure will there be any problem and also will I be able to install system updates using updater app??
why do u even want to reflash ur stock recovery TWRP is much better stay onit.!!! and first flash magisk and then lazy flasher and everything will be fine
The only reason I want to flash stock recovery is OTA updates..
Don't worry about OTA u can always manually download the update and flash it using TWRP
leo_pard2331 said:
Don't worry about OTA u can always manually download the update and flash it using TWRP
Click to expand...
Click to collapse
You mean I can install the update package without the need to download entire 1.5gb package every time?
night_mare said:
You mean I can install the update package without the need to download entire 1.5gb package every time?
Click to expand...
Click to collapse
You need full package everytime.
sachin n said:
You need full package everytime.
Click to expand...
Click to collapse
So for every update I have to flash the entire rom + magisk + lazy flasher? And Is clean flash necessary every time?
night_mare said:
So for every update I have to flash the entire rom + magisk + lazy flasher? And Is clean flash necessary every time?
Click to expand...
Click to collapse
Most likely!
Ive no idea about MIUI Roms tho. But I believe the same ^
Clean install via twrp everytime, would be good to go.
night_mare said:
So for every update I have to flash the entire rom + magisk + lazy flasher? And Is clean flash necessary every time?
Click to expand...
Click to collapse
You can dirty flash new update
No need of clean flashing
And also you dont need to flash magisk and lazyflasher after flashing the update
Just the update zip thats all
leo_pard2331 said:
You can dirty flash new update
No need of clean flashing
And also you dont need to flash magisk and lazyflasher after flashing the update
Just the update zip thats all
Click to expand...
Click to collapse
But flashing update zip restores stock recovery right?
night_mare said:
But flashing update zip restores stock recovery right?
Click to expand...
Click to collapse
Yup
But after flashing the update zip file flash the twrp.img file
That should fix it
i have nearly the same problem i just wanna flash dolby thats all n dont wanna break ota updates. so i just wanna know
if i unlock bootloader n boot into twrp recovery("fastboot boot recovery.img" this command will not wipe stock recovery) and flash dolby then im able to receive n install ota updates(incremental and full package) or not? what u say guys?
arjitkumarsingh said:
i have nearly the same problem i just wanna flash dolby thats all n dont wanna break ota updates. so i just wanna know
if i unlock bootloader n boot into twrp recovery("fastboot boot recovery.img" this command will not wipe stock recovery) and flash dolby then im able to receive n install ota updates(incremental and full package) or not? what u say guys?
Click to expand...
Click to collapse
You cannot flash dolby using stock recovery bro.. first you have to flash TWRP recovery. The fastboot command loads whatever recovery your phone contains. It will not flash TWRP
night_mare said:
You cannot flash dolby using stock recovery bro.. first you have to flash TWRP recovery. The fastboot command loads whatever recovery your phone contains. It will not flash TWRP
Click to expand...
Click to collapse
no bro this command will boot temporarily into custom recovery. search on google. so what u say now is it possible ?
---------- Post added at 04:31 PM ---------- Previous post was at 04:24 PM ----------
arjitkumarsingh said:
no bro this command will boot temporarily into custom recovery. search on google. so what u say now is it possible ?
Click to expand...
Click to collapse
im assuming if it is possible then i may not b able to install incremental updates while full packege will wipe dolby atmos in the process of installation.
m i right?
Return to Un-modded Stock:
Bootloader unlocked and TWRP and Root included
The file is 4gb compressed to 2gb. Depending on your connection it will probably take 20 to 45 minutes to download.
Be Advised
Do your research before flashing anything, I am not responsible for any damage caused to your device, due to impatience and missed steps. However, rest assured this recovery is solid and will absolutely return your X720 or X727 to stock 5.8.21s (with the bootloader already unlocked, TWRP installed and rooted)
I was asked by several people if I would be willing to share a link to my Stock X727 recovery, I created this thread to provide the 5.8.21s recovery for anyone who is experiencing dire issues or is simply wanting to restore the last official x727 recovery, as a daily driver or as a means to troubleshoot their issues by returning to the fully stock rom, stock partitions and ready to start over.
Attached is my full stock TWRP Recovery for my Le Eco Pro 3, version: 5.8.21s (X727)
It is a clean TWRP backup recovery that I did not mod in any way other than unlocking the bootloader.
The link is to my Google Drive account. https://drive.google.com/open?id=19dtLHmE5bsx5mdtEXOns4Z5drpeY79Em
The file is compressed
Ensure that you perform a full wipe before applying this recovery, and that you know what you are doing before attempting to install.
Please note that any changes that you make to your device is done at your own risk.
Please use caution and make sure that you have TWRP recovery installed.
Be in the habit of booting back to recovery before booting to system....This is a good practice for ensuring TWRP stays installed
You must unpack the downloaded 7zip file, before it will be useable.
As long as you can boot into TWRP and have root access you will have the full permissions needed to install anything , and reverse any actions that do not workout as planned.
Personally, I make a backup of my existing installation prior to making any changes. I recommend that you do the same. If you buy an OTG adapter and a USB 3.0 drive it takes 5 minutes.
The steps provided on the following link can be used to install my recovery file. https://forum.xda-developers.com/le-pro3/how-to/guide-return-to-stock-lock-bootloader-t3539513
When clicking the link, Google will attempt to scan. Click download to see the file, and then choose download if wanted.
Flash the appropriate files below for which ever device you own. ( X727 - Not needed, I provided the files anyway just in case.)
Firmware - X720
https://mega.nz/#F!kDgFQJ6R!MDhxCFw5KjfB0CfxAWwr9w
Firmware - X727
https://drive.google.com/open?id=136-4UpUUsj3exNsTc3d5n2iQuYUxr00H
Modems
X720: https://mega.nz/#F!pZ4WGARZ
Key : !2oG3Z2LS_wP8BzcWUQjfHg
X727: https://mega.nz/#F!NJ5VHS7Z
Key : !p0iO7bDiZ4kXny03EiAlWw
Build Prop Fix Device ID Tool ( Credit to @Ascertion )
https://mega.nz/#F!oAZ3yC4b
Key: !MDwbHXNTRdrpgMvQ42yviw
EFS:
Warning : Use this only if you have unrepairable IMEI Issues! Otherwise its not needed, and you could forever lose your original IMEI info.
https://drive.google.com/open?id=10n2VjwBYHmrq_PllcWmTaGUtMIeYynZ7
[B ]Just for Fun[/B] - Boot Screens and Boot Animations -
https://mega.nz/#F!JB51zbwR
Key: !sG_wXTPqyKpugg5QIZFo9w
These splash-screens and animations came from various sources. If you created them contact me so i can give you credit.
The Red Splash came from the Couco modified EUI : version 5.9.028s VR4
Other Helpful Hints and Tips More to Come!
Unlock Bootloader and Flash Roms, Gapps and Magisk https://forum.xda-developers.com/showpost.php?p=75009966&postcount=692 ( If using original Stock
Viper Settings : https://forum.xda-developers.com/showpost.php?p=75449097
Installing Viper and Dolby: https://forum.xda-developers.com/showpost.php?p=76362493&postcount=19
Edit
October 8, 2018:
I uploaded the Leeco Full Stock Rom 5.8.26s to my MegaDrive.
If you are selling your phone and want it to have stock without TWRP and without root , just flash this Rom and your stock radio driver "firmware" for your device
Link for EUI 21S : https://mega.nz/#!FRhh1ArL
Key: V5ua3oj91kFtgvLYBhl1X6Oq3bsScyDFruN3UptkWN0
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Soul0Reaper said:
A late reply to my issue but I just got around to restoring my Pro3. This worked while the last backup did not! Thanks!
Click to expand...
Click to collapse
Thats Awesome! I am glad that it helped you.
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
dunas2331 said:
Great work just what I needed only one problem for me after I flash rom reboot system and then go back into TWRP there seems to be encryption on it and I can't install or backup or do much. Is there a password or way around this TWRP encryption?
Click to expand...
Click to collapse
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
tsongming said:
Sorry, I didn't get a notification for your message. The encryption is your storage.
Follow the instructions here to resolve: https://www.google.com/amp/s/forum....return-to-stock-lock-bootloader-t3539513/amp/
The link has instructions for getting past and removing encryption.
Click to expand...
Click to collapse
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Hi tsongming, you know if can work on a x720?
thanks
Toni Moon said:
Hi tsongming, you know if can work on a x720?
thanks
Click to expand...
Click to collapse
Yes x720 and x727 are practically identical phones.
Sent from my LEX720 using XDA Labs
Scruffdog1978 said:
Can you elaborate on what to do here I keep getting encryption password too and can't do anything in twrp
Click to expand...
Click to collapse
I don't have time at the moment to provide lengthy instructions. With respect, I am providing a working, clean unlocked recovery file and pointing the way to instructions already that exist all throughout the LeEco forums.
But here's a quick answer
First use TWRP to reset your phone with a clean wipe, like you would for any ROM. Set developer options to the standard settings.
Next, your storage is encrypted. So it needs to be formatted. Use TWRP format the storage only. Then reboot to recovery.
****Important****
Don't ever format the storage without ensuring that you have a TWRP recovery. Always check the boxes to check if TWRP is installed before swiping. If you don't have a recovery you have a soft brick.
For you information, TWRP recovery is installed on it's on it very own partition. Formatting the storage does not affect the TWRP partition. Nonetheless, if you see the check box option, make sure they are checked.
I would suggest that you install the all in one tool : https://www.google.com/amp/s/forum....pment/tool-tool-one-mauronofrio-t3580611/amp/
This tool helps a lot and makes this stuff easier if are new to flashing custom Roms.. The all in one tool will update the Google driver and ADB installation on your computer.
After you format your drive you will have to flash the recovery from the PC. The links provided show all of the steps, or you can use the all for one tool. When your storage is encrypted you have no choice but to format.
If you use the all in one tool , see their page for instructions.
Read the instructions, then read them again. when learning something new it's a good idea to take notes.
Do not deviate from those steps or you could brick your phone.
There have been many people that have messaged me by PM who successfully returned to stock using my recovery, so it will work as long as you are careful and follow the instructions verbatim and you will be fine. Plus, It's a great idea to create your own working recovery before you begin.
Reminder, you are restoring to stock under you own discretion, I am not responsible if you miss a key step, have a power outage, use faulty cables or brick your device.
One final suggestion, when you install the recovery make sure your phone is fully charged. Unplug all unneeded external peripherals from your desktop computer.
Temporarily, disable antivirus, insert USB cable into the back of your desktop PC. Those outlets provide more power.
Please look past any typos, I typed this on little keys.
One last suggestion
Read this
http://www.androidtipsz.com/top-5-things-to-do-before-installing-a-custom-rom-on-your-android-device
Sent from my LEX720 using XDA Labs
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
meh4life321 said:
Will I keep twrp after restore? Thanks
Click to expand...
Click to collapse
Also, could I just restore the system?
Could I just flash this in TWRP and keep twrp as my recovery?
meh4life321 said:
Will I keep twrp after restore? Thanks
---------- Post added at 03:29 PM ---------- Previous post was at 02:53 PM ----------
Also, could I just restore the system?
Click to expand...
Click to collapse
No it will not keep twrp. follow the instructions in the link I provided above, there was no reason to duplicate the instructions on my post.
The difference is that my backup will restore your phone to Eui 5.8.21s with bootloader unlocked. You will need to reflash Twrp and root the phone with Magisk if you want to keep Twrp recovery ( that is what I would do) You will not be able to get OTA updates. But that doesn't matter because there probably not be any more OTA updates for the x727
Thank you, sir! This is great work. I was able to restore back to stock.
On the strange side of thing, my TWRP was saved. Previously, I was running AICP, but having multiple sound issues with it.
Here are the steps I followed to restore:
1) Move the file to OTG flash drive
2) Restore through TWRP via Restore
For my 727, it just reboot on logo, and doesn't go past it.
rob_z11 said:
For my 727, it just reboot on logo, and doesn't go past it.
Click to expand...
Click to collapse
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
tsongming said:
It takes a while.
For me, I had the quickest experience by flashing Magisk afterwards. The stock Rom , Rooted, and with Xposed is actually pretty sweet.
Click to expand...
Click to collapse
Will try again. How long is while? ?
rob_z11 said:
Will try again. How long is while?
Click to expand...
Click to collapse
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
tsongming said:
It should not take more than 10 minutes, and will usually startup in 5. I just now restored one of my X727's with this recovery, using the OTG method that the last person used and viola in worked so there's no doubt. I have always used ADB until now.
However, unlike the other poster, I did lose Twrp and had to reinstall it.
Always, Always Ensure Twrp is permanently installed
Make sure that you are on the latest version of Twrp : https://twrp.me/leeco/leecolepro3.html
Run Magisk, install Rom, Install Magisk again
Personally, I use the latest version of Magisk : https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
You want a fully clean install before you flash.
Instructions are redundant of XDA: if you want something other than what you have read already: Click on my account history to find detailed instructions, ( I type too much, too often) Under most thanked, you can quickly find detailed instructions for installing , Roms, Rooting, Installing Twrp, How to wipe to avoid any issues.
Finally, if for some reason it still doesn't work, the file may have been corrupted.
Worst Case scenario : there are other recoveries available on XDA. Beware of the edited versions, they do not work as well as an unadulterated recovery.
Click to expand...
Click to collapse
It actually worked for second time without any issues. Just can't get the root, but will follow your instructions.
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
blanktape said:
Hi just wondering does this rom pass safetynet out of the box?
what is the date of the security patch of this rom?
thanks
Click to expand...
Click to collapse
This recovery is stock EUI 5.8.21s. The exception is that the bootloader is unlocked, and it has TWRP Recovery instead of EUI Recovery. I do not remember which version of Magisk I Installed. I would advise that you flash the newest version of Magisk and you will not have any safety net issues.
If you are wanting a complete return to stock, you should instead reflash the stock Full Rom, which will reinstall EUI recovery and lockdown the bootloader.
Hi guys I was able to root my P10 using magisk and the new treble project on oreo very easily.
All credit goes to @topjohnwu as he's the creator of Magisk and this method all i'm doing is sharing his work and adding the boot image for the P10
Requirements:
Your PC
P10 ON OREO B360 (this only works on oreo if you try to do it on nougat you could easely brick your device)
Bootloader Unlocked (?)
ADB & Fastboot
I actually don't know if you need to have your bootloader unlocked as it's using the treble project to update the boot partition.
I had mine unlocked when i did this.
Step 1:
Get your boot image from update files (huawei update extractor > settings > uncheck the first 3 checkboxes) here i have the boot image from my VTR-L29C432B360
Install the latest Magisk Manager apk from here.
Step 2:
Open Magisk Manager, go to Settings > Update Channel > Custom Update channel with this link http://goo.gl/jefZKH
after that check if the latest magisk update is v15.4 (as the time of posting this guide)
if it says Invalid Update Channel you probably misspelled the link
Step 3:
Copy your boot image to your internal storage/sd card
Go on Magisk Manager > Install > Patch boot image file > Select the boot image on your internal storage/sd card
when it finishes go on your pc and pull the patched boot image to your desktop or desired folder. it will be stored on your internal memory/MagiskManager/patched-boot.img
Step 4:
Open cmd on the same folder as your patched boot image
Go to fastboot (Power-off then Vol+ and Power)
now on cmd type
Code:
fastboot devices
should come as response a serial number and fastboot
this means your device is connected to you pc and on fastboot
after that type
Code:
fastboot flash ramdisk patched_boot.img
it will flash the patched boot image
when it's done just reboot
and you're set!!
You'll have root with Magisk and pass safety net without a problem.
Friend, thanks for the information. Sorry you know how to install viper4android in B360
DarkPJV said:
Friend, thanks for the information. Sorry you know how to install viper4android in B360
Click to expand...
Click to collapse
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
D4XT3R said:
i wish i knew... i'm also looking for how to install it. if i get it to work i'll post a guide too
Click to expand...
Click to collapse
It would be fantastic.friend
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
smashedup said:
Thank you very much for this guide, worked like a charm.
I even have full SafetyNet back, incl. CTS. What I didn't have before I flashed the patched bootimage.
I'm just wondering why you suggest to modify the update channel? I got an error message anyway (and I didn't misspell it), so I changed it back to 'Stable' and had not problems.
Click to expand...
Click to collapse
well the modified channel update is one that @topjohnwu modified for huawei's treble enabled phones like the P10 so that we wouldn't have any problem with safety net or flashing the boot partition but if it worked for you it might work for others too
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
samy0x said:
Hello i just upgraded from nougat to oreo and bootloader is locked again i tried to flash the recovery img without success any solution to root that phone?
Click to expand...
Click to collapse
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
D4XT3R said:
do you have oem unlocking enabled on your phone? if after enabling this option it still fails to flash the patched boot image unlock the boot loader, I know a pain in the ass, but you'll pass safety net without a problem
Click to expand...
Click to collapse
Yes
Phone Locked
FRP Unlock
have you tried it again and worked? if not it only works with unlocked bootloader
D4XT3R said:
have you tried it again and worked? if not it only works with unlocked bootloader
Click to expand...
Click to collapse
Yes i tried again no solution i'll wait for sometime if no solution i'll unlock bootloader
I'm exploring that solution maybe : https://forum.xda-developers.com/mate-10/how-to/guide-mate-10-root-preserve-user-data-t3716547
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
How did you do that
samy0x said:
How did you do that
Click to expand...
Click to collapse
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Jannomag said:
I opened the Magisk Manager app and it prompted me that v16 is available for install. Then I pressed "Install", rebooted and that was it.
Click to expand...
Click to collapse
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
urbanboymne said:
What about working Xposed and Magisk like on Nouget EMUI 5.1? I'm always stock in boot-look when i try to flash BETA3 Xposed v90 SDK 26 amr64
---------- Post added at 07:59 PM ---------- Previous post was at 07:58 PM ----------
Yes me to, but first you need 15.4 magisk version and than you can update to v16 in MagiskManager app
Click to expand...
Click to collapse
Oh, of course. Sorry, I meant with "not flashing with TWRP" that I didn't need to flash the zip for v16 manually, just install it within the app. But of course you need to install 15.4 first.
meh , cant extract ramdisk.img from update.zip...
About magisk...is the root gone away finally fixed ?
on my old nova plus,when rooted whit magisk,we had to flash that darn patched boot img every 1-2 weeks in order to re have root again
is that finally fixed ?
Jannomag said:
I can confirm that Magisk v16 works for me on VTR-L29C432B360. Installed with the Magisk Manager without flashing in TWRP.
Click to expand...
Click to collapse
Exactly the same for me... and passes safety net
---------- Post added at 02:04 PM ---------- Previous post was at 01:57 PM ----------
Can we flash TWRP 3.1.1 after rooting with Magisk ?
Big thankyou it worked like a charm
Hey!
A few months ago I rooted my Mate 10 Pro (UK version on Three) using that all-in-one tool. It installed TWRP and Magisk.
I've been having a pending OTA update for months and it fails when trying to install rebooting onto TWRP.
Is there a safe way to go back to stock recovery, let the phone update and then root back? (without wiping the whole thing?) If so, could you please guide me giving some very specific steps? Many thanks!
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
My question is how can you flash to the lastest OTA EMUI 9.0 if twrp doesn't support emui 9.0.
durc12 said:
Use hrupdater 0.4 and twrp, but read well how to do it, if you are on a xloader2 version, you can't install xloader1 version. First read well all threads you can and then if you know what are you doing, update and root again. If you only want to update and you don't mind about root, install the stock recovery and unroot and update via OTA.
Huawei is a diificult smartphone for rooting in my view, be carefull and do all by your own risk, there are many people that have bricked this smartphone due to the lack of knowledge of what they were doing (and others due to bad luck of the downgrade of xloader)
Click to expand...
Click to collapse
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
hungrymr2 said:
I just wanted to continue to expand on this. All the info I gathered is pulled from the link below.
Xloader checker
https://forum.xda-developers.com/mate-10/how-to/beware-bla-l29c432b147-t3817241
HuRUpdater
https://forum.xda-developers.com/honor-9/development/tool-flash-official-firmware-recovery-t3769279
If you are rooted can also dump your own xloader if you want to see what you're currently on.
Download Terminal Emulator from the play store and open it
Type the following
Code:
su
dd if=/dev/block/sda of=/sdcard/xloader.img
Click to expand...
Click to collapse
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
93starletgt said:
Thank you so much for taking the time to help me out. However, I clicked on that link and I don't understand anything!
My goal is to install the update and keep my phone rooted (a must!). So I downloaded terminal emulator and followed your instructions, now I have an "xloader.img" on my SD card and I don't know what to use to open it or do next. Please have some patience and help me out?
Click to expand...
Click to collapse
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
Click to expand...
Click to collapse
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
hungrymr2 said:
"You can now transfer /sdcard/xloader.img to your computer and check it manually using, for example, HxD.
The first affected offset is at 1A8, its either 01 or 02."
I'm a little confused too.
---------- Post added at 10:14 PM ---------- Previous post was at 09:35 PM ----------
I just did an OTA update with HiSuite 9.0.2.304, it was ridiculously easy. I simply clicked update. There's a chance you might lose root.
Click to expand...
Click to collapse
Thanks for the tip. Were you rooted before the update? If so, was it Magisk or SuperSu? Also, did you have TWRP installed?
I was not rooted when I installed the ota
hungrymr2 said:
I was not rooted when I installed the ota
Click to expand...
Click to collapse
Right, that's my main problem. If I wasn't rooted I could do the normal update through HiSuite or OTA. I'll click on those links you sent and read thoroughly. Thanks.
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
ante0 said:
First restore stock recovery, flash this script in TWRP to do that https://mega.nz/#!8Swx3QaC!3JQ9imU70E9O1BxgO53Z754lGCZxCbKGgSHqvTEcXsQ
(assuming you haven't modified eRecovery as it will copy its ramdisk to recovery).
Secondly you can go to menu in System Updater and Download Latest full. That one will not fail to install. OTA can fail if you have modified ramdisk, kernel, system, vendor, product, cust (but not all are checked/patched in all OTA).
Full will not wipe data.
Click to expand...
Click to collapse
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
93starletgt said:
I just noticed your reply! So, if I understand correctly, that Mega script is a flashable Zip through TWRP that will restore the stock recovery?
Click to expand...
Click to collapse
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
ante0 said:
Yes. It will write eRecovery_ramdisk to recovery_ramdisk (these partitions are exactly the same, only different entrypoints).
So as long as you have not modified eRecovery_ramdisk by flashing TWRP to it, it will restore your stock recovery.
Click to expand...
Click to collapse
Thank you very much! I booted into TWRP, uninstalled Magisk (by flashing Magisk Uninstall Zip), flashed the stock recovery through TWRP (using the file on the link you gave me: https://mega.nz/#!8Swx3QaC!3JQ9imU70...bKGgSHqvTEcXsQ), rebooted and phone was stock again! I appreciate your help!
I have unlocked, disabled encryption and rooted Pocophone using Magisk , then flashed a custom kernel.
If a new update comes in for Pocophone, I know that I cannot directly go flash the OTA update because it will cause bootloop or brick my device. What to do before updating from previous to latest with custom kernel and root? (e.g. MIUI 9 > MIUI 10)
https://forum.xda-developers.com/po...-f1-unlock-bootloader-custom-t3839405/page245
If rooted and with TWRP, I would never recommend flashing via updater app.
I suggest you follow these steps to update the same way I did. I did this from 10.0.6 (oreo) to 10.1.3 (android pie)
1. DOWNLOAD THE ROM (either via updater or from xiaomi.eu, but if using updater, click install later, just let the zip download.
2. disable all MAGISK MODULES
3. reboot to recovery and flash the latest ROM
4. wipe cache and dalvik
5. FLASH latest FED from this post
6. Flash latest Magisk. Reboot
Again, make sure to follow these steps exactly so as not to mess anything up. Careful and
mecoromeo said:
https://forum.xda-developers.com/po...-f1-unlock-bootloader-custom-t3839405/page245
If rooted and with TWRP, I would never recommend flashing via updater app.
I suggest you follow these steps to update the same way I did. I did this from 10.0.6 (oreo) to 10.1.3 (android pie)
1. DOWNLOAD THE ROM (either via updater or from xiaomi.eu, but if using updater, click install later, just let the zip download.
2. disable all MAGISK MODULES
3. reboot to recovery and flash the latest ROM
4. wipe cache and dalvik
5. FLASH latest FED from this post
6. Flash latest Magisk. Reboot
Again, make sure to follow these steps exactly so as not to mess anything up. Careful and
Click to expand...
Click to collapse
Found a custom recovery which is a TWRP based, Orangefox, can I use this? They say it can be used for OTA updates for MIUI
mecoromeo said:
https://forum.xda-developers.com/po...-f1-unlock-bootloader-custom-t3839405/page245
If rooted and with TWRP, I would never recommend flashing via updater app.
I suggest you follow these steps to update the same way I did. I did this from 10.0.6 (oreo) to 10.1.3 (android pie)
1. DOWNLOAD THE ROM (either via updater or from xiaomi.eu, but if using updater, click install later, just let the zip download.
2. disable all MAGISK MODULES
3. reboot to recovery and flash the latest ROM
4. wipe cache and dalvik
5. FLASH latest FED from this post
6. Flash latest Magisk. Reboot
Again, make sure to follow these steps exactly so as not to mess anything up. Careful and
Click to expand...
Click to collapse
Does this way OTA update works when i modified system partition?? I'm getting error 7 in TWRP. Any idea?
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
mecoromeo said:
https://forum.xda-developers.com/po...-f1-unlock-bootloader-custom-t3839405/page245
If rooted and with TWRP, I would never recommend flashing via updater app.
I suggest you follow these steps to update the same way I did. I did this from 10.0.6 (oreo) to 10.1.3 (android pie)
1. DOWNLOAD THE ROM (either via updater or from xiaomi.eu, but if using updater, click install later, just let the zip download.
2. disable all MAGISK MODULES
3. reboot to recovery and flash the latest ROM
4. wipe cache and dalvik
5. FLASH latest FED from this post
6. Flash latest Magisk. Reboot
Again, make sure to follow these steps exactly so as not to mess anything up. Careful and
Click to expand...
Click to collapse
Darklouis said:
Found a custom recovery which is a TWRP based, Orangefox, can I use this? They say it can be used for OTA updates for MIUI
Click to expand...
Click to collapse
You tried Orangefox? Been able to upgrade?
nilg0lap said:
Does this way OTA update works when i modified system partition?? I'm getting error 7 in TWRP. Any idea?
---------- Post added at 12:02 PM ---------- Previous post was at 12:01 PM ----------
You tried Orangefox? Been able to upgrade?
Click to expand...
Click to collapse
About to try it.. I have to download the stock rom firmware before trying the ota update.. Here's the link https://forum.xda-developers.com/po...orangefox-recovery-project-beta-t3853233/amp/
I flashed the custom recovery and no problem at all.. But still haven't to try ota update via the Orangefox. I will update you later if it was a success..
Darklouis said:
About to try it.. I have to download the stock rom firmware before trying the ota update.. Here's the link https://forum.xda-developers.com/po...orangefox-recovery-project-beta-t3853233/amp/
I flashed the custom recovery and no problem at all.. But still haven't to try ota update via the Orangefox. I will update you later if it was a success..
Click to expand...
Click to collapse
Please let me know! I'm thinking about flashing 8.11.29 then download ota via updater then flash it through OrangrFox to 8.12.7. What do you think?
im on custom rom, with TWRP recovery and unlocked.
I want to return to stock stable pie MIUI rom. can I just download the rom and flash it using TWRP (i want to keep the custom rom )? any specific steps i need to follow. kind of confused
nilg0lap said:
Please let me know! I'm thinking about flashing 8.11.29 then download ota via updater then flash it through OrangrFox to 8.12.7. What do you think?
Click to expand...
Click to collapse
Damn it. I have a honest mistake. I accidentally wiped system instead only data and dalvik cache. Now im trying to download the stock firmware to restore the system partition. Sorry for the delay. I may post the update tomorrow.
nilg0lap said:
Please let me know! I'm thinking about flashing 8.11.29 then download ota via updater then flash it through OrangrFox to 8.12.7. What do you think?
Click to expand...
Click to collapse
Damn it. I made a honest mistake. I accidentally wiped system instead only data and dalvik cache. Now im trying to download the stock firmware to restore the system partition. Sorry for the delay. I may post the update tomorrow.
denraisr said:
im on custom rom, with TWRP recovery and unlocked.
I want to return to stock stable pie MIUI rom. can I just download the rom and flash it using TWRP (i want to keep the custom rom )? any specific steps i need to follow. kind of confused
Click to expand...
Click to collapse
Please refer to this guide. But first, flash OrangeFox recovery via fastboot or direct flash it on your current recovery
https://forum.xda-developers.com/po...cial-orangefox-recovery-project-beta-t3853233
Darklouis said:
Please refer to this guide. But first, flash OrangeFox recovery via fastboot or direct flash it on your current recovery
https://forum.xda-developers.com/po...cial-orangefox-recovery-project-beta-t3853233
Click to expand...
Click to collapse
why does it need to be OrangeFOX?
denraisr said:
why does it need to be OrangeFOX?
Click to expand...
Click to collapse
Because it is the only custom recovery (I think) for poco f1 to support ota updates...
Darklouis said:
Damn it. I made a honest mistake. I accidentally wiped system instead only data and dalvik cache. Now im trying to download the stock firmware to restore the system partition. Sorry for the delay. I may post the update tomorrow.
Click to expand...
Click to collapse
Let me know by then!! Thanks!
Sent from my POCOPHONE F1 using XDA Labs
nilg0lap said:
Let me know by then!! Thanks!
Sent from my POCOPHONE F1 using XDA Labs
Click to expand...
Click to collapse
Guys some little bad news, I downloaded beta full rom instead of stable rom, it is currently working fine. Now im downloading the weekly update and will try flash it via OrangeFox twrp if it worked.
I will try stable rom next time.. Sorry for the bad news.
Edit: How to upload pictures here?
Darklouis said:
Guys some little bad news, I downloaded beta full rom instead of stable rom, it is currently working fine. Now im downloading the weekly update and will try flash it via OrangeFox twrp if it worked.
I will try stable rom next time.. Sorry for the bad news.
Edit: How to upload pictures here?
Click to expand...
Click to collapse
I will upload screenshot of the OrangeFox recovery log during the ota update
Darklouis said:
Guys some little bad news, I downloaded beta full rom instead of stable rom, it is currently working fine. Now im downloading the weekly update and will try flash it via OrangeFox twrp if it worked.
I will try stable rom next time.. Sorry for the bad news.
Edit: How to upload pictures here?
Click to expand...
Click to collapse
Okay with beta ROM! Did it flash the update successfully?
Sent from my POCOPHONE F1 using XDA Labs
nilg0lap said:
Okay with beta ROM! Did it flash the update successfully?
Sent from my POCOPHONE F1 using XDA Labs
Click to expand...
Click to collapse
Flashed ota failed. It showed an error in the middle of the flashing. I didn't took a screenshot because it instantly reboot the system then continuous bootloop happend... I don't know why but I'm going to make sure what was going on.
I disabled the force encryption, enabled ota survival, etc. damn..
I will try the stable since the beta failed. Just wait for hours for the update. Sorry guys..
Darklouis said:
Flashed ota failed. It showed an error in the middle of the flashing. I didn't took a screenshot because it instantly reboot the system then continuous bootloop happend... I don't know why but I'm going to make sure what was going on.
I disabled the force encryption, enabled ota survival, etc. damn..
I will try the stable since the beta failed. Just wait for hours for the update. Sorry guys..
Click to expand...
Click to collapse
Is it error 7?? I know you did but are u sure had followed steps from the orangefox recovery thread for setting up miui? I dont think stable or beta wont make a difference!!
Sent from my POCOPHONE F1 using XDA Labs
nilg0lap said:
Is it error 7?? I know you did but are u sure had followed steps from the orangefox recovery thread for setting up miui? I dont think stable or beta wont make a difference!!
Sent from my POCOPHONE F1 using XDA Labs
Click to expand...
Click to collapse
Omg yes! It was Error 7.. If stable rom shows same results. Time to plan B.
Plan B is to try another custom recovery that supports ota updates, ota survival, and disables the force encryption to the data partition.
Darklouis said:
Omg yes! It was Error 7.. If stable rom shows same results. Time to plan B.
Plan B is to try another custom recovery that supports ota updates, ota survival, and disables the force encryption to the data partition.
Click to expand...
Click to collapse
Before moving to plan B can u try this??
https://forum.xda-developers.com/showthread.php?t=2522762
P.S: you wont get "assert" command in the updater script, but u can erase "get prop" command and try this.
You will find the update zip file in "Downloaded_rom" folder in internal storage
Sent from my POCOPHONE F1 using XDA Labs