I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Nothing will be lost from a regular OTA Just check around for any bugs or problems that other people are having if any? And update if you like.
rockerduck said:
I have a well working Note 7 with unlocked and rooted 10.3.5.0 Global PFGEUXM (TWRP recovery and magisk).
Today I got the OTA notification to update ROM to 10.3.6.0.
What I will lose if I update?
What's the best way to proceed?
Thank you
Click to expand...
Click to collapse
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
You have to download the full rom then go to twrp and wipe cache and dalvik flash the rom and magisk without reboot to system. After the flash of magisk you can reboot to the system. If you don't flash magisk before rebooting MIUI overwrite the twrp with the stock recovery and you have to reinstall twrp with fastboot
---------- Post added at 02:14 PM ---------- Previous post was at 02:12 PM ----------
If you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
rockerduck said:
Thank you very much darhma.
Should I reflash Disable_Dm-Verity before magisk?
Click to expand...
Click to collapse
You're welcome. I don't think it's needed the disable_dm-verity (but also i don't think that's a bad thing if you reflash it). If you want to thanks somebody in xda forum just press the thanks button (the ok button).
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
wheelnut said:
Hi!
I am new here so please don't be angry for my next questions
I just want root my Redmi Note 7 and keep OTP updates.
I read so many threads and this is my conclusion:
First I must apply for unlocking bootloader. Then flash TWRP recovery from here. After this flash Magisk through TWRP and that is it!
When phone notifies me that there is a new software update, I must download recovery rom from here, put it in internal memory, flash it and flash immediately Magisk again (flashing Magisk is mandatory after every software update to keep root).
Can anybody confirm that this is right way?
Thank You in advance.
Click to expand...
Click to collapse
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
darhma said:
Yes that's the right way.
---------- Post added at 01:34 PM ---------- Previous post was at 01:26 PM ----------
Another thing: if you get a compatibility error when flashing the rom just delete from the rom zip the file compatibility.zip
Click to expand...
Click to collapse
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
wheelnut said:
Can I do that in TWRP or I must unpack rom on computer and pack it as zip again?
Click to expand...
Click to collapse
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
darhma said:
I think that you can do that from twrp but i'm not 100% sure. From computer you don't need to unpack and repack, just open the zip with 7zip or unrar (i'm on linux and don't know which program you use for zip files) and delete the file
Click to expand...
Click to collapse
I'm using Windows and WinRAR. Will try after I download recovery rom (my dl speed is ****ty so it wont be soon)
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
thelastprime said:
I'm getting Error: 7 and am unable to update through TWRP on Redmi Note 7. Anyone else facing this?
Click to expand...
Click to collapse
Are you sure you downloaded the right rom? Error 7 is a mismatch of the firmware
Just come to say that everything went fine.
I didn't need to wait for unlock bootloader. I bought phone 2 weeks ago and using it normally and when I start unlock procedure it unlock without waiting time (I saw that someone must wait 720 hours!!).
I flash twrp and magisk (I had fingerprint lock so after flashing I did data erase) and now I have rooted phone
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
kaplanfa said:
So, I have a my Redmi Note 7 keeps telling me that there is a new update which is V10.3.10.0.PFGMIXM
I didn't want to install it since I was happy with my phone. But now the notification is not going away and it is always there. So I tried to install it from OTA but since my phone is unlocked and has TWRP on it, the update can't be installed.
My questions are:
- Should I download the rom and flash it through TWRP?
- How should I flash it without being have to make a factory reset? Is it posible not to loose any data? And if so, is it bad to flash it just like that?
- There is a kernel which is called EVIRA that I want to flash, too. So the order should be:
Rom + Kernel + Minsk, is that correct?
Thanks in advance.
EDIT: There are 2 versions of the new rom:
Recovery Rom and Fastboor Rom.
https://c.mi.com/thread-2432115-1-0.html
What is the difference? Which one should I download?
Click to expand...
Click to collapse
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Is updating ota with full recovery rom via twrp erase internal data or installed app?
darhma said:
1) download the full recovery rom
2) reboot to twrp
3) wipe dalvik art/cache and cache
4) flash the rom, the kernel and magisk in this order. Don't reboot to system until you have flashed magisk
5) reboot to system
6) enjoy
If you get a compatibility error when flashing the rom just delete the file compatibility.zip from the rom zip
Click to expand...
Click to collapse
Is installed app or data lost?
m.nav7854 said:
Is installed app or data lost?
Click to expand...
Click to collapse
If you do an update there should be no data loss however it is always recommended to have a backup of your data
Related
This is fully a noob helping guide , Am just trying myself to help noobs instead of explaining them each time .
Method 1 :
Make a twrp backup soon after unlocking boot loader .
Am not going to explain how to unlock bootloader and also twrp flashing ,you can search different threads available in the same section .
Soon after unlocking bootloader , Just boot twrp before flashing it .
This can be done this way , Once you unlocked bootloader .
Upon firstboot ,just goto developer options and enable USB debugging and then Open the folder where you had setup minimal fastboot (Mfastboot v2 google for it) . You should have it as you can't unlock bootloader without minimal fastboot .
In any empty space in minimal fastboot exrracted folder , just press shift+right click and select "Open command prompt here" .
Now copy twrp recovery to Mfastboot folder .
Connect your phone to PC.
In command prompt type the below command
adb reboot bootloader
Hit enter ,
Now your phone reboots to bootloader .
Now type this command .
mfastboot.exe boot twrp.img
(Just rename the recovery to twrp.img before flashing )
Now just take a backup and keep it safe somewhere to access when required .
This is easy , but many may loose their twrp backup for some reasons or forgot to take a backup before stepping to custom ROMs , move to Method 2 if your in such group .
Method 2:
Download update.app from official site .
Extract and put dload folder in root of sdcard .
Power off the phone and press vol up+ vol down and power .
It will now fully flash stock ROM with all stock files .
(This method requires stock recovery so keep in mind to flash stock recovery before trying to update as twrp can't perform these tasks )
Method 3:
Its not hard and not easy too but you required to download some tools .
Huawei update extractor tool (google for it)
Once downloaded open the tool and choose the path where you placed update.app in your PC .
Now the tool opens update.app .
Extract system.IMG and boot.IMG from update.app
Put them in the minimal fastboot folder.
Boot your phn to fastboot using command adb reboot bootloader .
Now connecting your phone to PC in bootloader mode , type the below commands
mfastboot.exe flash system system.img
mfastboot.exe flash boot boot.img
mfastboot.exe reboot
That's it you are on stock ROM.
Method 4:
Flash the stock rom flashable zip posted by devs in your device specific threads and flash it .
Fully for noobs : METHOD 5:
Download the twrp backup posted in device specific threads and put it in sdcard and restore it. Its easy though .
Now your device is ready for flashing official updates "if you get them"[emoji14].
i try every method here and i found myself anytime with modaco custom rom in name build its normal ? ( sorry for my bad english )
yddek971 said:
i try every method here and i found myself anytime with modaco custom rom in name build its normal ? ( sorry for my bad english )
Click to expand...
Click to collapse
Cache & Cust partitions need wiping and reflashing. Had the same issue when I reverted a Modaco rom back to stock.
Easiest method for L21 users is to flash this stock ROM: http://www.modaco.com/forums/topic/377002-r3-custom-rom-starter-template-honor-5x-kiw-l21-b130/ then replace TWRP with the stock recovery image from http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
yes, the rom says "custom rom starter template" but it's the stock B130 UK ROM repackaged into a flashable ZIP. Much easier than messing around extracting system images.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
I should mention one thing. If you have gone back to stock after a custom ROM then you may find the internal storage partition is the wrong size. Just do a full factory reset from Settings to resolve this.
flibblesan said:
Cache & Cust partitions need wiping and reflashing. Had the same issue when I reverted a Modaco rom back to stock.
Easiest method for L21 users is to flash this stock ROM: http://www.modaco.com/forums/topic/377002-r3-custom-rom-starter-template-honor-5x-kiw-l21-b130/ then replace TWRP with the stock recovery image from http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
yes, the rom says "custom rom starter template" but it's the stock B130 UK ROM repackaged into a flashable ZIP. Much easier than messing around extracting system images.
---------- Post added at 02:22 PM ---------- Previous post was at 02:21 PM ----------
I should mention one thing. If you have gone back to stock after a custom ROM then you may find the internal storage partition is the wrong size. Just do a full factory reset from Settings to resolve this.
Click to expand...
Click to collapse
oh thanks i see the r3 updated to format partitions rather than delete so i dont need to wipping cust and cashe ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
i just need to flash this rom ?
yddek971 said:
oh thanks i see the r3 updated to format partitions rather than delete so i dont need to wipping cust and cashe ?
---------- Post added at 03:28 PM ---------- Previous post was at 03:15 PM ----------
i just need to flash this rom ?
Click to expand...
Click to collapse
Yes, if you just flash that rom then you'll be fully restored to stock, but with TWRP still in place. If you flash the stock recovery.img after then this will put the phone completely at stock and you should be able to apply future updates as the rom is completely untouched.
flibblesan said:
Yes, if you just flash that rom then you'll be fully restored to stock, but with TWRP still in place. If you flash the stock recovery.img after then this will put the phone completely at stock and you should be able to apply future updates as the rom is completely untouched.
Click to expand...
Click to collapse
thanks a lot !
gopinaidu77 said:
This is fully a noob helping guide , Am just trying myself to help noobs instead of explaining them each time .
.
Click to expand...
Click to collapse
All the TWRP Backups in my Back to stock Guide include stock recovery
And also using the dload/update.app method does not delete your data but it will replace your custom recovery / boot.img and you can take OTA update afterwords
clsA said:
All the TWRP Backups in my Back to stock Guide include stock recovery
And also using the dload/update.app method does not delete your data but it will replace your custom recovery / boot.img and you can take OTA update afterwords
Click to expand...
Click to collapse
Yeah , thats what i mean device specifix threads .
And thanks for your repository , all the stuff in one place :cheers:
Hi Gopi,
Please help me getting back to stock on my L-22.
I am planning to go back to stock of L-24 available as (KIW-L24-B151-Stock (Boot.img - System - System/Priv-App Only)) posted by clsA.
1. Which method to follow????
2. Do I need to go back to stock Recovery???? If yes, then how??? where is stock recovery of L-22 posted?????
Please guide me I can cook it.
3. otherwise B140.debloated version -2. I tried to install through TWRP. NO success but a bootloop. is it ok this way???
Thanks in advance.
@subodhverma21 , L22 already got b150 update and i posted ota link .
Try downloading stock twrp backup posted by me and restore it along with stock recovery and then install ota .
Sent from my KIW-L22 using XDA-Developers mobile app
gopinaidu77 said:
@subodhverma21 , L22 already got b150 update and i posted ota link .
Try downloading stock twrp backup posted by me and restore it along with stock recovery and then install ota .
Sent from my KIW-L22 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks man,
It worked. Now on stock with update 150 installed.
Sent from my KIW-L22 using XDA-Developers mobile app
When I try the dload folder method on the root of my SD card the process fails. Can someone please advise what to do? I am L21
Hello,
I have exactly the same problem on a KIW - L21 . Did you find a solution?
Sorry for my english, I'm french.
Thank you
faisalsiddiqui said:
When I try the dload folder method on the root of my SD card the process fails. Can someone please advise what to do? I am L21
Click to expand...
Click to collapse
newic2001 said:
Hello,
I have exactly the same problem on a KIW - L21 . Did you find a solution?
Sorry for my english, I'm french.
Thank you
Click to expand...
Click to collapse
it's a known issue the L21 update seems to be corrupt their are many posts about it
can you install a rom with TWRP ?
If yes this Rom will get you back to stock >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Hi I went from Cm13 to stock with emui 2.0 by restoring my twrp backup before I flashed my first huawei gr5 custom rom.
Now i am trying to restore back to stock rom to fully use OTA updates. Here's what I Did:
1. Restore twrp backup (emui 2.0 not rooted)
2. Flash system img and boot.img via adb using img file from update.app also by using update extractor.
Now i realized that im still in twrp. Do i need to flash recovery img first? Then can i do updates without problem? Or do i need to use the update.app via dload updating too?
good work bro, helps a lot of ppl @gopinaidu77
---------- Post added at 03:07 PM ---------- Previous post was at 03:05 PM ----------
s4h1k0 said:
Hi I went from Cm13 to stock with emui 2.0 by restoring my twrp backup before I flashed my first huawei gr5 custom rom.
Now i am trying to restore back to stock rom to fully use OTA updates. Here's what I Did:
1. Restore twrp backup (emui 2.0 not rooted)
2. Flash system img and boot.img via adb using img file from update.app also by using update extractor.
Now i realized that im still in twrp. Do i need to flash recovery img first? Then can i do updates without problem? Or do i need to use the update.app via dload updating too?
Click to expand...
Click to collapse
try restoring though twrp
clsA said:
it's a known issue the L21 update seems to be corrupt their are many posts about it
can you install a rom with TWRP ?
If yes this Rom will get you back to stock >> http://loadbalancing.modaco.com/download.php?file=customromtemplate-5x-plk21-b130-r3.zip
Click to expand...
Click to collapse
@gopinaidu77
Hello sir
Does method 3 will have to be done with unlocked bootloader or locked one?
Because nexuse devices need unlocking the bootloader before flashing factroy images
NAROUTO said:
@gopinaidu77
Hello sir
Does method 3 will have to be done with unlocked bootloader or locked one?
Because nexuse devices need unlocking the bootloader before flashing factroy images
Click to expand...
Click to collapse
Of course unlocked one.
gopinaidu77 said:
Of course unlocked one.
Click to expand...
Click to collapse
Bro
I want your help please?
I tried to flash stock rom. I first extracted update.app .then flashed stock recovery via fastboot and tried to flash stock rom from dload folder in my memory card but always fail to install/and stuck with 5% . Then tried fastboot to flash the rom but error cannot load system.img but boot.img and recovery.img flashed successful.
I am stuck now and don't know why flash system partitions from Adb fails and from stock recovery fail @clsA
Help
NAROUTO said:
Bro
I want your help please?
I tried to flash stock rom. I first extracted update.app .then flashed stock recovery via fastboot and tried to flash stock rom from dload folder in my memory card but always fail to install/and stuck with 5% . Then tried fastboot to flash the rom but error cannot load system.img but boot.img and recovery.img flashed successful.
I am stuck now and don't know why flash system partitions from Adb fails and from stock recovery fail @clsA
Help
Click to expand...
Click to collapse
Your update.app fail to flash at 5% right ?
Its easy .. Goto settings/storage and set sdcard as default .
And then try dload method .it will get flashed now
Hello,
Just Wanted To Give A Straight Forward Solution For VoLTE Fix In Android N ROMs.
So, Here U Go.
1. Download This ROM (http://bigota.d.miui.com/6.11.3/miui_HMNote3ProGlobal_6.11.3_233ef61784_6.0.zip)
2. Download This TWRP (https://drive.google.com/open?id=0B6qi9i0uOR-BYnpaendYQ1BBRFE)
3. Download This Firmware (https://www.androidfilehost.com/?fid=385035244224398629)
4. Download This ROM (https://sourceforge.net/projects/re...onRemix-N-v5.8.0-20161126-kenzo.zip/download)
5. Download This ROM Too (https://sourceforge.net/projects/re...N-v5.8.0-20170114-kenzo-Nightly.zip/download)
1. Now, Unlock Your Bootloader, Officially Or Unofficially, I Don't Give A **** For That.
2. Flash TWRP (Step 2) Using Fastboot Or Using Existing TWRP.
3. Wipe Everything Except Ur Internal And External Storage And Flash MiUI 6.11.3 (Step 1) Using Just Flashed TWRP And After Flashing It Go To Install Again And See In Root Directory, There Will Be A Folder Named "Flash_Folder" Go Inside It And Flash Lazy Flasher. Don't Bother For Bootloader Locking, This TWRP Will Knock It Off.
4. Now Start The Device, And When On Setup Screen, See There Will Be VoLTE (That's Normal For MIUI) Be There For 5 Minutes (Complete Setup Or Not, I Don't Give A **** For That Too).
5. Now Switch Off Your Phone, Wipe System, Data, Cache, Dalvik And Flash The Firmware (Step 3).
6. Just After Flashing Firmware, Flash The ROM (Step 4), Its RR 26/11 Version Remember.
7. Start The Device, Voila You Got VoLTE.
8. Now Get Back To TWRP And Dirty Flash Latest RR (Until Now Latest RR Link Is Given On Step 5) Without Wiping Anything.
9. Flash Pico GApps 7.1 arm64 (Cmon U Know Link Of This).
10. Enjoy.
NOTE : You Can Now Wipe Everything And Flash Any Nougat ROM.
Every Resources Belong To Their Original Owner, All Credits Goes To Them.
Kill The Thanks Button If Helped, No Donation Required, I'm Bill Gates Of My Heart xD.
this is for kenzo right?
bro ur links are down
zeon321 said:
this is for kenzo right?
Click to expand...
Click to collapse
what is kenzo??
ak_bagade said:
bro ur links are down
Click to expand...
Click to collapse
Found that links have extra ) in the end.
Remove that.
cyjil said:
what is kenzo??
Click to expand...
Click to collapse
It's the 32gb Snapdragon version of Kenzo
Has this even worked for anyone now on earth? ?
Is it required to mount /cust and /system before falshing the firmware and the ROM?
---------- Post added at 05:56 PM ---------- Previous post was at 05:50 PM ----------
This method is working for sure. Thanks a ton man!
zeon321 said:
It's the 32gb Snapdragon version of Kenzo
Click to expand...
Click to collapse
16 GB snapdragon version too. Okkk
Hi OP & alls. Can i use this for Kate?
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
i am on zui 2.3.045
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
i am on zui 2.3.045 tell me full installation process if possible
Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
hardikkchavda said:
Are you coming from Cos 12.1 ?
Than you need to flash ZUI 2.5 ROM first or cm-13 ROM .
Because even if you flash nogout some problem like sim1 will stay always active and sim2 will be greyed out.
Click to expand...
Click to collapse
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Can i flash in fastboot or install Lineage os recovery?
Mikuzukz1 said:
Can i flash in fastboot or install Lineage os recovery?
Click to expand...
Click to collapse
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
+∆bhijith said:
Just flash in the normal way bro... Use TWRP > Install > then select the zip file.
Click to expand...
Click to collapse
it's showing error that way
Mikuzukz1 said:
it's showing error that way
Click to expand...
Click to collapse
Even now? Even after rebooting to recovery via ADB?
+∆bhijith said:
Even now? Even after rebooting to recovery via ADB?
Click to expand...
Click to collapse
I don't know how to boot via adb ijust wiped all partitions in twrp
got it working finally....installed it over cm13.0 and done
Mikuzukz1 said:
got it working finally....installed it over cm13.0 and done
Click to expand...
Click to collapse
Wonderful ! Good to go for any 7.x.x rom now...
---------- Post added at 03:30 PM ---------- Previous post was at 03:27 PM ----------
+∆bhijith said:
Error 7 is caused by the custom recoveries. It occurs both on CWM and TWRP. Just wipe the whole phone and via ADB boot it to recovery (Command 'adb reboot recovery' -- without quotes.) Then copy the ROM to internal storage and now flash. It will work like a charm.
---------- Post added at 07:36 AM ---------- Previous post was at 07:29 AM ----------
Huh? How will that help? Why do need a 6.0 M ROM before you flash nougat? You can't dirty flash Lineage. It'll end in a boot loop. You have to wipe and flash. So how will the ROM that was installed before influence nougat flash?
Click to expand...
Click to collapse
Because i faced same problems before and searched in XDA and that is the solution available right now.
Mikuzukz1 said:
I was trying to flash official lineage os downloaded from official website through twrp but ended up with an error i can't figure out what to do of. i am uploading screenshot of twrp. help.
Click to expand...
Click to collapse
I think file is not completely downloaded...
Once same happened when I checked I chose wrong file wwhich was half downloaded.. Check it
i'm facing the same problem. i don't know how to use adb boot.
isn't there any other way.
also i checked the file was completely downloaded
and i'm on zui 2.5
I also have problem when flash nuclearom from cm13. I have some zuk devices but got problem with 2
First, it has bootloop
I have to flash China ROM then it works
I can flash CM 13
But up to 14 or 7.x will have bootloop again
Pls help
Good Morning everybody,
so yesterday was a rough day and when it eventually end i recive the october security update on the phone, without thinking i installed it and the phone does not boot up , instead i face my recovery (TWRP 3.1.1-0).
Of course i've made a mess because i was on stock rooted 7.0 on my retEU XT1572 phone with unlocked bootloader and status 3
i've tryed to restore a previous nandroid backup wihtout success, so today i downloaded the new RESURRECTION REMIX v5.8.4 (4 december wich is based on stock android 7) but i have no luck even with that...
Do i miss something?is there any rom to try with now? or i have to make a downgrade of my firmware to make it work again?
thanks in advice!
UPDATE:
phone boot now but always in recovery and after rebooting in bootloader i can reboot system from there.. it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
LAST UPDATE:
boot fixed by using this command in twrp recovery
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work (the rom is the same that you linked page40 post #397 )
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
dzidexx said:
You missed very much.
Here is stock RetEu, before october update:
https://forum.xda-developers.com/moto-x-style/general/stock-xt-1572-reteu-7-0-ddumped-files-t3712521
Wipe all with twrp and flash all. After it you can get OTA's.
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
Here is RR 5.8.5 working on N modem:
https://forum.xda-developers.com/mo...ial-resurrection-remix-v5-8-3-t3637204/page40 post #397
Wipe all with twrp, update twrp to 3.2 and you can flash it right now.
@
---------- Post added at 11:03 AM ---------- Previous post was at 10:59 AM ----------
@Husky34
Click to expand...
Click to collapse
Husky34 said:
oh thanx man! i've already seen that post but i wasn't sure that it can work for me. i have some question befor starting:
1) i need the new twrp 3.2 to flash resurrection-remix? because as i mention before i've already tried to flash it with twrp 3.1 and it doesen't work
2) do i have to flash stock-xt-1572-reteu-7-0-ddumped-files before point 1)?
Click to expand...
Click to collapse
1. I think so. 3.2.x will be needed for future builds.
1a. You flashed RR for MM modem.
2. No, but this is only way to get ota update.
"swearing in italian" it was a twrp bug.. after a backup restore if you hit restart the phone restart in recovery, you need to boot into bootloader and reboot system from there -.-
thanks to all of you guys!!
strange fact, now if i turn off the phone and again on i'm still on recovery, i have to reboot bootloader and system from there.
i think something is pointing at the recovery instead system..
edit: it seems that if you download an update and the install process doesen't go in place every time you restart the device it always try to re-flash it, that's why i'm always in recovery.. i foun a similar post with this solution but i think it need some changes before it will work on our device (but i don't have the knowledge to set it right :S )
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
dzidexx said:
Ota update didn't end.
I think you can try clear data & cache otaupdate app and disable it. Link2sd can help with it. @Husky34
Click to expand...
Click to collapse
just tried but wihout luck.. maybe i can wait someone make the flashable update but i don't think this fix the issue
Flash uploaded stock.
dzidexx said:
Flash uploaded stock.
Click to expand...
Click to collapse
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Husky34 said:
actually i fixed the issue using this command
dd if=/dev/zero of=/dev/block/platform/f9824900.sdhci/by-name/misc
misc file running at the startup redirecting the boot in the recovery, put blank in the file let the system boot up normally
Click to expand...
Click to collapse
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
pshadoww said:
thanks, this command just saved me. but misc file in my XT1575 is under
/dev/block/platform/0/f9824900.sdhci/by-name/misc
but now I can't check system update in the OS anymore, I think flash back factory recovery mine help. Do you know where to download stock 7.0 recovery for 1575?
Edit: found it for 1575 here.
Click to expand...
Click to collapse
you can also use link2sd to disable the update app so it doesn't bother you,
or wait untill someone create a zip of the update and flash it into recovery.
thanks, that worked for me as well.
File was located at /dev/block/platform/soc.0/f9824900.sdhci/by-name/misc
So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
cblock said:
So Ive been trying to install multiple different pie roms and each one gives me error 7 during the install with twrp.
Ive updated twrp to the newest 3.2.3, I read that could be the issue.
I was using nolimits rom but due to no future updates I wanted to try something different.
Im sure its something simple, but I cannot seem to find any resources.
I even tried deleting the assert lines in the rom zip, still same error.
Im at a complete loss.
I just put nolimits back on it so I at least have a working phone.
Any info is appreciated
Click to expand...
Click to collapse
Please post your question only once https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Please answer some questions:
Which twrp (file name)?
Which xXx rom(file name)?
Decrypted or encrypted storage?
Which rom do you want to install (exact steps)?
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
cblock said:
Sorry for the double post, Ive been super frustrated with it.
Right now im running twrp 3.2.3.0 from the twrp website, I have tried codeworkx with no change.
I was trying multiple different roms, but for the sake of troubleshooting I was trying PixelExperience Cheeseburger 9.0
Most of the installs attempted have been through twrp so Im guessing decrypted.
And I was following the steps on the roms thread.
Factory wipe, delvik and data, then attempt the install.
Click to expand...
Click to collapse
Decrypted or encrypted storage? Which rom do you want to install now? Please use latest codeworkx recovery.
Which xXx rom exactly you're coming from(file name)?
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
cblock said:
Ok, I am coming from xXx_NoLimits_12.0_OP5_Oxygen_5.1.3_full and Id love to install OxygenOS Open Beta 22 Full
I can certainly install the codeworkx recovery if needed.
How can I tell if I am encrypted or not? Ive always just left things as default
Btw thanks for your help
Click to expand...
Click to collapse
Just follow instructions in first post for clean installation, make sure you made backups: https://forum.xda-developers.com/oneplus-5/how-to/official-oxygenos-beta-1-android-oreo-t3710003
Encryption means, you cannot access your internal storage without entering a pin when starting twrp or accessing the devices memory from outside.
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
cblock said:
So Ive followed the new install instructions from start to finish, and I cannot get past the OS flash.
Continuing to receive error 7.
Also receiving cannot mount /vendor as well
Click to expand...
Click to collapse
For the error 7 make sure you downloaded the correct files, without download issues(maybe use checksum). have you removed compatibility.zip from the OB22 rom zip with either 7zip or total commander?
For vendor partition error try to mount vendor partition within twrp manually, if there's no checkbox, you need to flash what I suggested you here https://forum.xda-developers.com/oneplus-5/help/updating-to-beta-22-t3879346/post78437012
Earlier open betas created this vendor partion. You can try with OB13.
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
yohouse2 said:
I have same problem, except I tried to fix it by flashing OB19 firmware and radio zip. Now when I boot the recovery I don't get "no vendor partition" and the bootloader unlocked error, but when I try to flash ANY rom (stable 5.1.4 /open beta 19 / PIE ), the system and vendor partitions would patcg unconditionally, but I get no OS error and the device reboots to recovery. Please help.
Ps: I have magisk and TWRP 3.2.3, and tried both clean flashing and dirty flashing. the unlocked bootloader error changed even after restoring the NAND backup. I had already removed the compatibility zip from the Pie zip. I tried blu spark and codeworx versions of twrp 3.2.3
Click to expand...
Click to collapse
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
cblock said:
FINALLY got it all to work.
Apparently I had issues with the firmware, had to go back and install codeworx 15.1 firmware, after that it seems to be good to go.
THANK YOU Strongst.
Click to expand...
Click to collapse
How did you fix it? Can you explain what you mean by codeworx firmware? Could you provide link for file or guide?
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
strongst said:
Same as my answer above. Oneplus published every open beta as an update(even when it's a full rom) of the previous version hence when your last open beta was 10 and you want 22 you missed several in between(this was an example!).
Click to expand...
Click to collapse
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
cblock said:
This is the firmware from Codeworkx
https://sourceforge.net/projects/ch...firmware/firmware_5.1.7_oneplus5.zip/download.
You might have to go to an older version of twrp as well, just to get this installed.
Click to expand...
Click to collapse
Which twrp version and developer? And after this can I flash Pie directly or should I install something before it? Did you dirty flash or did you use clean install? Sorry for too many questions but I tried it many times and am frustrated that it didn't work, but you fixing it gives me hope.
yohouse2 said:
I flashed open beta 13 & 19, and stable 5.1.4, all failed, what should I try?
Click to expand...
Click to collapse
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
I was able to flash pie directly after updating the firmware.
twrp 3.2.3 should work
strongst said:
What exactly means "failed"? Which error? Screenshot maybe? And from which oxygenOS you tried to update?
Also you need to flash magisk after flashing oxygenOS to make twrp sticky. Also a format of internal storage may be necessary to solve a boot problem.
The Unlocked Bootloader Warning screen is normal cause it's a warning when you unlock your bootloader, if it changed, it's due to changes made by oneplus some time ago, they changed it.
Click to expand...
Click to collapse
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
yohouse2 said:
By failed I mean that I would wipe the system partition for clean flash, install the ROM zip, which would run but say patching system and vendor partitions unconditionally, then when I want to reboot it says warning no OS. Continuing to reboot gets me automatically back to recovery.
I tried updating from xXx 5.1.2
Click to expand...
Click to collapse
Did you try the firmware link I posted earlier?
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
Will try in just a minute
---------- Post added at 09:23 PM ---------- Previous post was at 09:05 PM ----------
cblock said:
Did you try the firmware link I posted earlier?
Click to expand...
Click to collapse
still getting system patching unconditionally
Does it get stuck with an error?
Its suppose to say that