I'm on redmi note 4 mido, I've installed the latest RR ROM version goes like rr_20180514.zip ( tried all may builds) but installation of ROM and gapps has no issue but can't flash a root like previous RR ROMs.
The SuperSU.zip gets aborted after [sepolicy > failed , aborting] and magisk ends with error 1 ( tried flashing ROM boot.IMG ) no use.
Titanium backup won't work without root and all my data cannot be transfered to may build , anyone with same problem or any solution? Need help
most_curious said:
I'm on redmi note 4 mido, I've installed the latest RR ROM version goes like rr_20180514.zip ( tried all may builds) but installation of ROM and gapps has no issue but can't flash a root like previous RR ROMs.
The SuperSU.zip gets aborted after [sepolicy > failed , aborting] and magisk ends with error 1 ( tried flashing ROM boot.IMG ) no use.
Titanium backup won't work without root and all my data cannot be transfered to may build , anyone with same problem or any solution? Need help
Click to expand...
Click to collapse
You are probably using a Treble ROM, flash Magisk for Treble ROMs. It is linked in your ROM's thread.
SuperSU doesn't work on Treble ROMs
Thanks man, will try
Related
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
am not able to update twrp
twrp-3.1.0-0-onyx.img
twrp-3.0.3-0-onyx.img
twrp-3.0.2-1-onyx.img
when i flashed these files using twrp and rebooted my device i was stuck in one plus logo.
Even i cant flash any of above 3 twrp files using fastboot adb method i am getting an error "remote dtb not found" pls check screenshot
then i reinstalled twrp-3.0.2-0-onyx.img using adb fastboot method , but i cant not install or update version above 3.0.2.0 plz help
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader in diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we are going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using fastboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
Do i need to install stock recovery of stock ROM ? some help would really be appreciated
i can install all twrp upto "twrp3020 " version
but if i try to flash greater version like twrp3021 or twrp3100 m getting same error
i need new twrp because i am not able to flash Android N custome roms i am getting an error code 7 when i am installing ROM
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
CheckYourScreen said:
Follow the mega unbrick guide, then update your bootloader then flash latest twrp.
@Joshwin Aranha
Click to expand...
Click to collapse
thanx for replay but i found solution
Hi guys if anyone facing same problem Read this
PROBLEM
1)Error Code 7 while flashing new ROM (like Nogut ROMS ).
2)Remote dtb not found while updating old twrp to new (eg. twrp 2.8 to twrp 3.1.0.0)
Cause of problem
Users who have already flashed and rooted their phone and using custom ROMs like CM12 CM 13 or any other from past year will likely to face this problem
while updating twrp recovery or while updating to new custom ROM Nogut cm14 .
Because new custom ROMs have bootloader is diffrent partition (something like this) so you wont be able to flash your phone with new ROMs i.e cm14 or nogut or you wont be able to flash new twrp recovery which is 3.1.0.0
Please keep in mind if you are using following twrp version then you should flash your phone with old twrp 2.8.7.0
twrp-3.0.2-0-onyx.img 14.4M 2016-04-04 23:04:23 EDT
twrp-3.0.1-0-onyx.img 14.5M 2016-04-01 04:24:54 EDT
twrp-3.0.0-1-onyx.img 14.5M 2016-02-15 23:17:25 EST
twrp-3.0.0-0-onyx.img 14.4M 2016-02-06 09:18:41 EST
above point is important look at the solution now
Solution
Step
1)flash your phone with old twrp version TWRP 2.8.7.0 using fastboot method(because we aree going to install stock recovery in my case stock recovery of oneplus X lollipop version)
2)after installing stock recovery install 2.14 ver of stock ROM of oneplus X (for oneplus x devices) (for other brands eg samsung look for ur old stock recov and ROM)
3)install old Stock ROM in ur device
4)now again boot into stock recovery and install latest stock ROM (for oneplus X i installed latest oneplus X oxygen OS 3.1.4).
5)after doing above step you can install latest twrp-3.1.0-0-onyx.img without any "remote dte not found error" using fastboot.
6)once you flash twrp-3.1.0-0-onyx.img flash your phone with latest CM14 or any latest android N or nogut ROM without any problem
Note : For error code 7 some people suggested to edit udatescrip file which is not good solution and it is temporary and it wont work for all so do it as i suggested
Comman ERRORS :
1) if you are on twrp 3.x.x.x you will face Remote dte not found while booting your phone in stock recovery using flashboot
so first of all flash your phone with old twrp 2.8.7.0.
2)Do not wipe your internal storage in frustration it will create more problems because you wont be able to transfer files into your phone to flash it (Use OTG cable or SD card if u did it already).P.S you can do it afterwards
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Wagner.B said:
mhmm.. the unbrick guid dosnt help.. followd the guidé - now my bootloader is locked and stuck locked so no 2.8.7.0 flashing.. Ideas? i`m working now 24h this issue..
Click to expand...
Click to collapse
are you on stock recovery right now ?
Finaly the Lv.2 support got it back working via "our" msm unbrick tool (Still got it on my drive =D)
but learned nothing - trying to get lineageOS again.
The recovery is now TWRP v3.1.0-0 for E1003_15_161107 (it works for now on a backup..)
But... i must say - I'm very worried that i cant flash lineage again..
I dont know what the trick is...
Here is the Solution watch this video
https://www.youtube.com/watch?v=kTdKmceC5xU
Yes!!
I ve been looking for a solution the past days since i got stuck in older twrp versions and could only upgrade to android 6.
Thanks man!! You rock!!
Updater process ended with ERROR 7 (happening lots now?)
Never or rarely encountered this before but is happening with lots of Kenzo roms..any ideas as to why?
Same here :x
thiagoserrao said:
Same here :x
Click to expand...
Click to collapse
I got Nitorgen OS on but everything else will not work.
rslatara said:
I got Nitorgen OS on but everything else will not work.
Click to expand...
Click to collapse
I'm using Lineage OS, and i can't update :/
may be firmware problem
Actually this is happening because of the updated modem.. all the roms (lineage, nitrogen os, etc) first checks the required modem number and then proceeds to further installation. To solve this.. either go to the meta data folder of your ROM.ZIP and edit the updater script to delete the (modem checking) line.. or elz flash the previous or old modem.. it will work fine
every recovery i flash gives me ERROR 7 :/
i have a 'kate' and befor i used to flash roms without issue. kenzo roms and flash kate modem done.
but phone crashed. and now im back on miui beta 7.10.19 unlocked bootloader flashed twrp (all the twrp possible btw i tried all i could find) they all dont want to flash a custom i tried 7 different ZIP of custom roms... 4 versions of RR 5.7.4 and 2 of 5.8.4, flashed modem zips still error 7
does anybody know how to fix this.....
reggiexp said:
every recovery i flash gives me ERROR 7 :/
i have a 'kate' and befor i used to flash roms without issue. kenzo roms and flash kate modem done.
but phone crashed. and now im back on miui beta 7.10.19 unlocked bootloader flashed twrp (all the twrp possible btw i tried all i could find) they all dont want to flash a custom i tried 7 different ZIP of custom roms... 4 versions of RR 5.7.4 and 2 of 5.8.4, flashed modem zips still error 7
does anybody know how to fix this.....
Click to expand...
Click to collapse
Use redwolf recovery never had this problem, i have a kate.
And recommend you Nitrogen os 8.1 for kate
I had downloaded latest version of lineage OS from official website and I tried to flash on my REDMI Note 3 Kenzo but I can't here is the screenshot attached of remark.
Pls help
I was just about to post about this. I have the same issue, a work around I found was described in this video: https://www.youtube.com/watch?v=bGVOR0kugZw
However, now that I have it installed, and try to OTA update, I get the same, I have to repeat the steps in the video every time I update, kinda frustrating and unnecessary imho. I had the latest MIUI updated and unlocked with the miui unlocker before the wiping and installing. All I have found its related to the bootloader not supporting android N.
Look at the error and you will see the issue.
Your firmware is too old.
Download one from Lineage thread and flash that before Lineage
update, I installed the firmware from this thread: https://forum.xda-developers.com/redmi-note-3/development/firmware-hmnote3proglobal-t3574361
now update goes thru like its supposed to
every recovery i flash gives me ERROR 7 :/
i have a 'kate' and befor i used to flash roms without issue. kenzo roms and flash kate modem done.
but phone crashed some months ago so i changed but now i want it again. and now im back on did a edl flash miui beta unlocked bootloader flashed twrp (all the twrp possible btw i tried all i could find) they all dont want to flash a custom rom i tried 7 different ZIP of custom roms... i tried to flash 4 diffeeent versions of RR 5.7.4 and 1 RR 5.8.4 all give error 7. flash kate modem. still error, then flashed modem with emmc thing patched nope still wont flash any custom rom
does anybody know how to fix this
You have to erase dalvik cache and DATA it will bring you new setup but still your device would be updated....
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Noter2017 said:
I think all the ROMs you listed are Treble ROMs. They require a special Treble version of Magisk which is usually linked in the ROM threads
Click to expand...
Click to collapse
I tried the treble versions of magisk too. Even tried the beta. No luck.
Figured it out
uncannyjish said:
Unlocked my Bootloader recently.
Flashed almost all the best ROMs available. But can't get root access in any of them except Resurrection Remix. The root access on RR works coz it is prerooted and needs a small addonSU to activate it fully. Coutresy of LineageOS/CyanogenMod.
Magisk would give out "Cannot mount /vendor" "Error:1". I tested it on all the latest builds of all the ROMs(AOSP, AOiSP, dotOS, Cardinal etc..)
Tried flashing Magisk versions out there including the treble version of the beta. Also tried the flashing 'boot.img' trick. Still the same thing shows up.
My device : Redmi Note 4 SD
Recovery : Redwolf/TWRP(tried with both of them)
Has anyone been experiencing the same issue??? Has anyone figured out a solution??
Also, RR also seems to give out the same error when flashing Magisk. When I installed Titanium Backup, it said I have 16 cm-SU installed. Can't find a way to uninstall or remove it either.
Click to expand...
Click to collapse
So it was a problem with the treble implementation of the ROM. I was installing treble ROMs using the stock TWRP/Redwolf recovery. These recoveries install the ROM but don't work or make the /vendor partition. This has led many people to believe that there is something wrong with their phone. Anyway, flashing a custom treble recovery did the job. Although not each one of them is perfect, TWRP_3.2.1-7_mido-treble by @NFound is the best one.
Solved every problem faced by me till now. Custom Magisk for Redmi Note 4 is available and works like a charm.
Magisk-v16.3-mido-treble
It seems no one faced this issue before, anyway this would help the new comers like me.
Thanks.
Couldn't get
I am using RR ROM Oreo since 2 weeks and finding ways to root it
But can't find any way to do it
Addonsu is not working
Treble magisk is not working
I need to change my recovery
But the ROM ended up encrypting my internal storage
So should I clean data to format and remove encryption
Or I can directly install a new recovery ?
Format then wipe everything. With a help of a pc or a laptop download a treble supported recovery or the Firefox recovery(search it).Then try again.
Hi guys I just rooted( as a newbie) my old redmi note 4x using SuperSU. but I came to know that systemless magisk is really better option and has many amazing modules . then I tried to unroot through SuperSU app 's full unroot option . But it said ' uninstallation failed'
then went to twrp (3.2.3) ,wiped data.. then it became unrooted .afterwards tried to flash magisk v18.0 from twrp .but it failed and showed 'updater process ended with error :1'
So what should be my next procedure ??
Thanks in advance.....
Latest twrp is 3.3.1-0 and Magisk is 20.4, try this
Ray Krebs said:
Latest twrp is 3.3.1-0 and Magisk is 20.4, try this
Click to expand...
Click to collapse
Just tried those latest versions but still the same message ' updater process ended with error :1' .
Is it a miui 11 problem?
If you aks google about twrp error 1 by installing magisk, i found following solution.
Extract with 7-zip the boot.img out of the Custom.zip file and copy it also to Smartphone.
Flash with twrp this boot.img to the boot partition and than try to install magisk.
Ray Krebs said:
If you aks google about twrp error 1 by installing magisk, i found following solution.
Extract with 7-zip the boot.img out of the Custom.zip file and copy it also to Smartphone.
Flash with twrp this boot.img to the boot partition and than try to install magisk.
Click to expand...
Click to collapse
I have to download the miui.zip and then extract ??
They talk to extract the boot.img from the Custom Rom that you want to install and copy it on your internal memory or sd card.
https://m.youtube.com/watch?v=gUmqStKhxWA