Has anyone tried russian flyme twrp roms? There are 3 Roms in their link, but i don't know how to install it.
any link please ?
I can't put links because i have less than 10 post.
I'm sorry.
Write emmaus.pro in google. There are twrp for mx4 and custom roms, flyme and cm12.
I have Flyme 4.5.7i on my MX4 flashed by TWRP recovery.
(original my mx4 was A edition, and I was unlock bootloader and flash custom recovery with instructions found on xda forum)
Instructions How To Edit Official Flyme Rom to be flashed with TWRP:
---------------------------------------------------------------------------------------
1. Unzip update.zip in empty folder
2. Go in folder with unpacking files and delete uboot.img and logo.img
3. Go in META-INF folder and from here delete imei.dat and machine_match
4. Go in COM/GOOGLE/ANDROID folder and edit updater.script
Remove this :
getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "M460A" || abort("This package is for "mx4" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("META-INF/machine_match", "/tmp/machine_match");
set_perm(0, 0, 0755, "/tmp/machine_match");
package_extract_file("META-INF/imei.dat", "/tmp/imei.dat");
if (run_program("/tmp/machine_match", "/tmp/imei.dat") != "0") then
ui_print("machine not match");
delete(/tmp/imei.dat);
abort();
endif;
delete(/tmp/imei.dat);
And remove this :
assert(package_extract_file("logo.img", "/tmp/logo.img"),
write_raw_image("/tmp/logo.img", "logo"),
delete("/tmp/logo.img"));
assert(package_extract_file("uboot.img", "/tmp/uboot.img"),
write_raw_image("/tmp/uboot.img", "uboot"),
delete("/tmp/uboot.img"));
Save edited file.
5. Pack again files in .zip arhive (any name except update.zip)
6. Remove or rename any update.zip original file from root sd card
Now you can flash rom with twrp recovery and now you have latest Flyme rom but still have unlocked bootloader and twrp recovery.
I find this instructions on russian forums, and I try it and everything works fine.
You can try it on your responsibility.
Ok, thanks. Where have you downloaded twrp recovery?
Now i have philz 6 recovery, if i flash modded flyme ROM, can i flash it with philz?
I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file
TWRP (uncompiled and recompiled by myself to change splash screen (it now fit the screen) http://www.mediafire.com/download/26b963db1k489db/new-recovery.img
Can i flash it trough flashify app?
I was flash twrp with fastboot
You can via flashify but fastboot is safer
PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"
Are the russian flyme roms modded to can flash it vía twrp?
yes you can flash them Russians have ported this TWRP and are making some good stuff on flyme rom
Ok, i will try those Roms. Thankyou so much.
furious.builder said:
I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file
Click to expand...
Click to collapse
I can't understand you. If is already tried that you can flash modded flyme Roma from twrp, why you say that flyme will reinstall stock recovery?
Are you sure?
I'm talking about stock Flyme not modded Flyme Stock flyme contains scripts like recovery-from-boot.p and install-recovery.sh in system.new.dat which reinstall stock recovery, it's what it does to my MX4, but modded flyme certainly don't have these scripts
Understood. Thanks!
furious.builder said:
PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"
Click to expand...
Click to collapse
Is there any risk of brick flashing twrp vía fastboot?
I have seen many mx4 bricked flashing custom recovery with flashify.
Via fastboot there is nearly no risks because if it's flashed it will boot, and if there is something wrong during unlock fastboot has not been unlock so it will not flash, but don't use the one from my link, there is a newer from emmaus.pro
Related
New build is available to download.
Download link http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.0_community_build/
for those who stuck in boot, flash this recovery through fastboot . https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img Credits: pwseo
For getting to fastboot menu, 1) press power button untill phone has been powered off.
2) first press volume up button then power button until fastboot mode is shown.
3)Use the following command to flash the recovery. (Note:adb and fastboot should be installed first. get it here:http://forum.xda-developers.com/showthread.php?t=2317790)
fastboot flash recovery opx_oos3_recovery.img
Click to expand...
Click to collapse
source https://forums.oneplus.net/threads/oxygenos-3-1-0-marshmallow-community-build-for-oneplus-x.460857/
I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks
I read the thread, i think need to flash stock Recovery before flashing
motherninja said:
I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks
Click to expand...
Click to collapse
You can flash it thorough official twrp or stock recovery
You can also keep your recovery, but you have to slightly modify your package.
1. Unzip package.
2. Go to META-INF\com\google\android\
3. Edit updater-script with notepad++, or just with any text editor.
You should see "getprop("ro.build.product") == "OnePlus" || abort("This package is for \"OnePlus\" devices; this is a \"" + getprop("ro.build.product") + "\".");"
4. You can delete this line or change getprop("ro.build.product") == "OnePlus" to getprop("ro.build.product") == "One". In my case I had to change it into getprop("ro.build.product") == "onyx".
5. Save it and zip whole package.
6. Flash it and enjoy
My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?
Still waiting for a solution. :/
Waiting for opinions before flash hehe
motherninja said:
My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?
Click to expand...
Click to collapse
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
hotlinksxz said:
Waiting for opinions before flash hehe
Click to expand...
Click to collapse
Same here ...till some one compile the ROM which can be flash through TWRP
maybe i will wait for bug fix before flash..this is the first oos 3 for opx so it will be buggy
Sent from my ONE E1003 using XDA-Developers mobile app
kethsawant said:
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Same here ...till some one compile the ROM which can be flash through TWRP
Click to expand...
Click to collapse
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.
Any update on VOLTE?
Root
With Kingroot YouTube can get root, maybe with flashfire you can install twrp?
Edit: Can't install twrp but can install xposed.
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Danish66 said:
Any update on VOLTE?
Click to expand...
Click to collapse
+1
Yes Guys..Can someone share any info here on this topic in the latest Oxygen OS build ??
motherninja said:
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.
Click to expand...
Click to collapse
hmm same here,cant get into recovery,twrp needs to be updated by the devs i think
also directly booting into twrp fails too,"dtb " not found
gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
How u did it?
Mind sharing step by step?
Thanks in advance.
gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
With twrp? How?
If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!
gahehe said:
If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!
Click to expand...
Click to collapse
But you won't be able to boot back into twrp, so it's kinda useless. Better to have stock recovery than not being able to boot back into twrp=p
Unless you were able to flash supersu with twrp before booting the rom and not being able to boot back into twrp. Was that the case?
Hello, I'm bringing the Official Marshmallow ROM for desire 816 (dual sim) a5_dug and it's pre-rooted and (all credits goes to (xXminiWHOOPERxX)) and how to intall the OTA updates after flashing the ROM
Rom Information:
Code:
Android OS : 6.0
Kernel : Stock
Sense Version : 7.0
Release Keys : 3.12.401.2 release-keys
Download Link: Mega.nz
How to Install the flashable zip using TWRP recovery:
1. place the flashable zip (Sense7-MarshMallow.3.12.401.2_DualDesire816.zip) on the sd card.
2. wipe the cache, dalvik cache, system, data and internal storage (if you don't have any data on your phone).
3. install Sense7-MarshMallow.3.12.401.2_DualDesire816.zip through the install option in TWRP Recovery.
4. reboot the phone when the installer finishes and everything should be fine.
Now you can't install the OTA update with the custom recovery, and even if you reverted back to stock recovery it won't work, so you have to follow the following instructions to install the OTA update on your custom recovery.
How to Install the OTA update
1. download the OTA update from your phone from
Code:
Settings > About > Software Update
, after it finishes the flashable zip of the update should be located in
Code:
data/data/com.htc.updater/cache/
or
Code:
data/data/com.htc.updater/files/
2. it should be something similar to
Code:
OTA_A5_DUG_M60_DESIRE_SENSE70_MR_HTC_Region_3.21.xxx.x_R-3.12.401.2_release_479056hu4q3r1wkhz4b5n3
3. copy it to your pc and extract the zip file.
4. navigate to
Code:
/META-INF/com/google/android
5. you should find a file named
Code:
update-script
, open it with notepad or sublime text or any code editor you use.
6. from line 4 to 9 you should see the following code
Code:
getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys" ||
getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys" ||
abort("Package expects build fingerprint of htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys or htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "htc_a5dug" || abort("This package is for \"htc_a5dug\" devices; this is a \"" + getprop("ro.product.device") + "\".");
replace it with the following:
Code:
#getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys" ||
# getprop("ro.build.fingerprint") == "htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys" ||
# abort("Package expects build fingerprint of htc/htc_europe/htc_a5dug:6.0/MRA58K/698282.2:user/release-keys or htc/htc_europe/htc_a5dug:6.0/MRA58K/748385.1:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
getprop("ro.product.device") == "a5" || abort("This package is for \"a5\" devices; this is a \"" + getprop("ro.product.device") + "\".");
7. save the file with no extension as it is and re-zip the archive using winzip or whatever tool you use to compress as (zip).
8. flash the OTA zip file you made using TWRP or any custom recovery.
Click to expand...
Click to collapse
I've uploaded the modified update-script file just in case you couldn't do this steps so you just have to replace the modified update-script with the original one in the OTA zip file.
Download: update-script
thank you sooo much !!!
but what is ota update and what it use for ?!
Echtar said:
thank you sooo much !!!
but what is ota update and what it use for ?!
Click to expand...
Click to collapse
OTA updates are the software updates you recieve from the phone manufacturer, typically you can't install an OTA update while your phone is rooted so this is the only way to install it.
can you upload OTA + script here?
file get error
i m getting error to flash the ota update file... ?
"/system/bin/app_procss32" has unexpected contents.
the ota wont install. it's still reporting expected device error.
i mean "this is meant for ....."
thanks
guys pelase help my htc 816 dug
wifi not working it on off and i can get it on !!
Echtar said:
guys pelase help my htc 816 dug
wifi not working it on off and i can get it on !!
Click to expand...
Click to collapse
We are on the same boat bro! Did u update to MM from Kitkat? This update is for lollipop users apparently. We are having driver issues..
rohinraj said:
We are on the same boat bro! Did u update to MM from Kitkat? This update is for lollipop users apparently. We are having driver issues..
Click to expand...
Click to collapse
I went back to kitkat 4.4.2. Try this https://forum.xda-developers.com/desire-816/development/26-nov-svhd-v1-0-0-t2953661
this ROM worked for me. And its great!! Wifi works and everything is back to normal.
omartek0 said:
Hello, I'm bringing the Official Marshmallow ROM for desire 816 (dual sim) a5_dug and it's pre-rooted and (all credits goes to (xXminiWHOOPERxX)) and how to intall the OTA updates after flashing the ROM
Rom Information:
Code:
Android OS : 6.0
Kernel : Stock
Sense Version : 7.0
Release Keys : 3.12.401.2 release-keys
Download Link: Mega.nz
I've uploaded the modified update-script file just in case you couldn't do this steps so you just have to replace the modified update-script with the original one in the OTA zip file.
Download: update-script
Click to expand...
Click to collapse
i have made all steps but when i replace update-script and rezip ota folder and put it back on sdcard to flash it
and when i click install zip on cwm it says installation aborted
i tried with TWRP but also not working !!
i am on cm13 can i flash this rom ? from twrp like normal ?
me too on cm13 how can i install this rom pls help
Hi
First thank you
I did all what you said but when i chose to flash Rom zip file from sd
Its stars checking and its begins then gives me install
aborted i dont know why??, can you help me with it to go to the next level to update ota??
I have a question
I bought a cell phone in the US a few years ago, it was blocked by the SPRINT operator, I stayed a long time without using it, and now I decided that I would pack it to use it. I unlocked the bootloader and also the root, put a custom rom but the device is still blocked.
Is there any way to unlock this?
(I'm in Brazil)
.....................
after install cant update ota say mound read-only
what must do?
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
You can request unlock .img again
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
ShaktiSW said:
The way I got it working was by
1. Flashing deodexed TWRP flashable ZUI 4.0.233 rom and then set it up along with magisk.
2. Flashed factory2vendor.zip
3. Flashed TWRP by z2_plus_treble-TWRP-3.2.2_kubersharma_v2.img available in his thread.
4. Clean Flashed AEX 5.8
5. After setup again in TWRP clean flashed a Beta version of AEX v6.0
6. Again after that clean flashed the Official version of AEX v6.0.
You can skip step 4 & 5. I followed those steps to avoid any Blue Screen issue recently reported by some users. I didn't face any Bootloader problem.
*Remember to use Kubersharma TWRP in step 3. I don't know why, but Treble TWRP compiled by Davide is not reading internal storage when flashed after ZUI deodexed.
*And I am not responsible for anything that happens during your adventures.
Click to expand...
Click to collapse
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
satyen_ said:
Didn't you every flashed a 3.1+ zui via qpst before?
Because as far as i know the deodexed zui 4.0. 233 doesn't updates the bootloader
Click to expand...
Click to collapse
I never needed to. And AEX 6.0 run pretty much smooth without blue screen issue. I just followed the above mentioned procedures.
Deleted.
senthamizhan said:
If you afraid to flash qpst rom, here a method which will update your baseband/bootloader without qpst tool.
1) flash vendor to factory ( if you already flashed factory to vendor )
2) flash zui 3.5.389 full ota which has firmware included ( not the deodexed one by hendibudi )
Link :https://drive.google.com/file/d/1knkZxUyLNZO7uS8u_CK7j4j5-UqqGs5l/view (don't reboot
3) flash hendibudi's twrp for zui and reboot to rom
( The step 2 will lock your bootloader/ update your firmware/ bootloader. So we need to unlock bootloader again. To avoid wiping of internal storage we use twrp recovery which will only wipe /data
4)unlock your bootloader by following this
https://forum.xda-developers.com/lenovo-zuk-z2/how-to/how-bootloader-zuk-z2-pro-t3415392
( You can use your old unlock image )
5) clean flash any nontreble rom( needed)
Reboot to rom.
6)Reboot to recovery, flash factory to vendor zip.
( Don't reboot )
7) install latest twrp from twrpbuilder.org for our device ( install--image -- select -- recovery-swipe to flash )
8) reboot to recovery
9) clean flash your fav 4.4. kernel ROMs.
Note:
I am not tested new twrp by twrpbuilder.org instead of hendibudi twrp at step 3.
If it doesn't encrypt internal storage, there is no need of step 5&7
I followed this and worked. Don't miss any steps
Click to expand...
Click to collapse
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
renatohm said:
First of all, kudos for the great job! I'm anxious to test it.
But please forgive my stupidity.
Which hendibudi TWRP build you mean? I could only find a 3.2.1 but I'm not sure it can handle Treble.
Click to expand...
Click to collapse
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
senthamizhan said:
Yes it doest support treble partition. But we need that twtp to avoid internal storage encryption problem.
So we can flash any non treble ROM, reboot yo ROM, reboot to recovery , flash factory to vendor zip, flash latest treble twrp, reboot to twrp then flash 4.4 ROMs.
My entire point is flashing vendor to factory and and full ota 3.5.389 zip will update bootloader, firmware ( it will work just as qfil flash )
My guide can be followed if someone having trouble with qfil . ( tested by at least 2 people )
Other steps are just to avoid encryption and internal storage wipe problems that may come after flash.
Hope it'll remove doubts
Click to expand...
Click to collapse
Thanks for your kindness!
Alright then, I'm next on line to test! I'll just backup (it sucks...) then I'll flash!
Out of luck, flashing via Mi Tool now...
renatohm said:
Out of luck, flashing via Mi Tool now...
Click to expand...
Click to collapse
What happened
senthamizhan said:
What happened
Click to expand...
Click to collapse
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
renatohm said:
Blue screen. I'm stuck on Qfil too, it also resulted in blue screen. Starting from scratch.
Click to expand...
Click to collapse
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
satyen_ said:
There is baseband zip file of 3.5 zui (in guides and discussion section) you can flash that if you don't want to go through the long process of Qfil, I flash that zip and i am able to use 4.4 kernels
This will not lock your bootloader and can be flashed by official TWRP
Click to expand...
Click to collapse
Yes, that's the reason I tried this in the first place, but it didn't work for me.
Qfil did work, and I'm now on Bootleggers.
sandruman said:
I've Lost my unclocked bootloader file. There is a way to extract It from my Zuk? Thanks?
Inviato dal mio Z2 Plus utilizzando Tapatalk
Click to expand...
Click to collapse
Bro,if u had used your email address try checking in your inbox again for image, just search bootloader .
I've changed my mail with a Gmail one and it work. Now I've my unl files
Inviato dal mio Z2 Plus utilizzando Tapatalk
flash vendor to factory ( if you already flashed factory to vendor ) "
explain this line
In these forums there was a file for updating baseband to 1.70. I flashed it promptly and my phone also went into soft brick. Because accidentally my bootloader got locked and got revised also. By using certain key combinations I succeeded in again unlocking my bootloader without formatting my inner storage . now I am able to flash 4.4 ROMs. Without going through all the hassles of backup, formatting and again flashing twrp.
Your guide didn't work for me (but step 2 using your file didn't lock my bootloader). It would be nice if you gave direct link to items in your steps (for i.e factory to vendor.zip, twrp...). I guess I'll try using qfil unless someone has some tips... BTW I can't find a good qfil guide for 4.4 kernel roms, could anyone give me a link to a helpful thread for it if I can't get it working using this method?
I recently bought an unlocked OnePlus 5 128GB and decided I wanted to root it and install another ROM. So, I did the standard flash of TWRP 3.2.3 for Cheeseburger and also successfully installed Magisk and Substratum. I found myself in an infinite boot screen after applying a Substratum theme so decided to factory reset the phone and start from scratch.
However, I stupidly managed to wipe the phone's OS as well as everything on it when going to factory reset, so now I'm just stuck in TWRP. I cannot install the stock OP5 ROM from the official OnePlus website and have also tried several others such as LineageOS. I've tried all the instructions on this thread to get back to stock but I always receive the dreaded:
Code:
Updater process ended with ERROR: 7
I get this even with the STOCK OnePlus 5 ROM, so there are no "assert" lines in the "updater-script" file like in LineageOS's ROM:
Code:
assert(getprop("ro.product.device") == "cheeseburger" || getprop("ro.build.product") == "cheeseburger" ||
getprop("ro.product.device") == "OnePlus5" || getprop("ro.build.product") == "OnePlus5" ||
getprop("ro.product.device") == "oneplus5" || getprop("ro.build.product") == "oneplus5" || abort("E3004: This package is for device: cheeseburger,OnePlus5,oneplus5; this device is " + getprop("ro.product.device") + "."););
assert(oneplus.file_exists("/dev/block/bootdevice/by-name/vendor") == "1" || abort("Error: Vendor partition doesn't exist!"););
assert(oneplus.verify_modem("2018-11-06 18:11:36") == "1" || abort("Error: This package requires firmware version 5.1.7 or newer. Please upgrade firmware and retry!"););
I've spent the last 4 hours looking for fixes, but they usually tell me to do the following, none of which has worked:
- Update TWRP (I have the latest version)
- Remove "assert" lines from "updater-script" file (Which invalidates the .zip files in non-stock ROMS)
- Use Blu_Spark (Can only find zip downloads, not .img files like everywhere tells me to use; they don't install as recovery menus when fastbooted, it just stays on the OnePlus logo when rebooting into it)
I'm completely stumped and am left with a softbricked OnePlus 5 that's only functionality is booting into fastboot or recovery/TWRP. Can anyone help here?
VampMarcie said:
I recently bought an unlocked OnePlus 5 128GB and decided I wanted to root it and install another ROM. So, I did the standard flash of TWRP 3.2.3 for Cheeseburger and also successfully installed Magisk and Substratum. I found myself in an infinite boot screen after applying a Substratum theme so decided to factory reset the phone and start from scratch.
However, I stupidly managed to wipe the phone's OS as well as everything on it when going to factory reset, so now I'm just stuck in TWRP. I cannot install the stock OP5 ROM from the official OnePlus website and have also tried several others such as LineageOS. I've tried all the instructions on this thread to get back to stock but I always receive the dreaded:
I get this even with the STOCK OnePlus 5 ROM, so there are no "assert" lines in the "updater-script" file like in LineageOS's ROM:
I've spent the last 4 hours looking for fixes, but they usually tell me to do the following, none of which has worked:
- Update TWRP (I have the latest version)
- Remove "assert" lines from "updater-script" file (Which invalidates the .zip files in non-stock ROMS)
- Use Blu_Spark (Can only find zip downloads, not .img files like everywhere tells me to use; they don't install as recovery menus when fastbooted, it just stays on the OnePlus logo when rebooting into it)
I'm completely stumped and am left with a softbricked OnePlus 5 that's only functionality is booting into fastboot or recovery/TWRP. Can anyone help here?
Click to expand...
Click to collapse
Error 7 identifies a corrupt os file. Download 5.1.4 and 5.1.7 again without any download manager and remove compatibilit.zip with 7zip on PC.
Use this recovery by flashing it with your current one https://forum.xda-developers.com/on...rdstuck-bootloop-please-t3896101/post78818108
Then follow this instructions https://forum.xda-developers.com/on...rdstuck-bootloop-please-t3896101/post78818624
Report detailed back :good:
remove compatibilit.zip with 7zip on PC
Click to expand...
Click to collapse
I've looked into the files in the 5.1.4 update for the OP5 including the "system.new.dat" file but can't find any "compatibilit.zip" in it. It also won't install as it is.
I flashed the recovery "boot.img" file using fastboot but all I get is a static light blue LED and a black screen. Using "adb devices" doesn't show anything connected.
VampMarcie said:
I've looked into the files in the 5.1.4 update for the OP5 including the "system.new.dat" file but can't find any "compatibilit.zip" in it. It also won't install as it is.
I flashed the recovery "boot.img" file using fastboot but all I get is a static light blue LED and a black screen. Using "adb devices" doesn't show anything connected.
Click to expand...
Click to collapse
Ah, my bad, too fast. The removal of the compatibility.zip is only necessary on Pie builds!
Which boot.img did you flashed? The linked one codeworkx twrp?you wrote you're able to boot your current twrp so you can flash the other twrp with it.
I flashed this one you linked in your comment -- is this the right one?
VampMarcie said:
I flashed this one you linked in your comment -- is this the right one?
Click to expand...
Click to collapse
Sorry, use this one please https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
The other one was the kernel...
strongst said:
Sorry, use this one please https://drive.google.com/file/d/1UlTftbe6wooAs4Fp0cjwXlOKmfQHgdfL/view?usp=drivesdk
The other one was the kernel...
Click to expand...
Click to collapse
I can't get into fastboot to install the recovery software now because I installed that kernel as the recovery...what now?
EDIT: Managed to install TWRP but it flashed the TWRP logo then went back to the OnePlus logo screen.
EDIT #2: In TWRP and installing 5.1.4 is working!
EDIT #3: Phone is booting, will give it some time and update later.
SUCCESS! In summary, here's what I did:
1) Boot into fastboot (POWER + VOL UP)
2) fastboot flash recovery twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
3) fastboot boot twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
4) Wipe system, data & cache using TWRP
5) Install 5.1.4, then Magisk, then format internal storage
6) Boot OS
Thank you so much; you're a lifesaver, strongst!
VampMarcie said:
SUCCESS! In summary, here's what I did:
1) Boot into fastboot (POWER + VOL UP)
2) fastboot flash recovery twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
3) fastboot boot twrp-3.2.3-0-20181031-codeworkx-cheeseburger.img
4) Wipe system, data & cache using TWRP
5) Install 5.1.4, then Magisk, then format internal storage
6) Boot OS
Thank you so much; you're a lifesaver, strongst!
Click to expand...
Click to collapse
Glad to help you
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
cris2d2 said:
I just finished reading a thread on another Redmi forum, here on XDA, about rooting a Redmi S2 without permanent TWRP flash.
Do you think it's possible to successfully apply the same steps on MIUI 11 Global Stable Redmi 7A (using the proper boot.img)?
Things needed :
- Unlocked Bootloader
- PC with ADB and Fastboot installed
- boot.img of your miui rom. You can grab it (open with winRar) from fastboot firmware (.tgz) xiaomi redmi S2. Download the firmware file in xiaomi site or in this section thread. The version are reccomended to be the same as your current miui version.
- Magisk Manager.apk
1. Open Magisk Manager
2. Press Install > Install > Patch Boot Image File, and select your boot.img file
3. Magisk Manager will now patch your boot image, and store it in Internal Storage/Download/patched_boot.img
4. Copy the patched boot image to your PC. Place it in Minimal ADB & Fastboot directory.
5. Flash the patched boot image to your device. Here is the command :
fastboot flash boot boot.img
6. If adb say "Okay" twice, mean it succesfully.
Type : fastboot reboot
7. Wait your phone to reboot.
From here:
https://forum.xda-developers.com/redmi-s2/how-to/magisk-root-custom-recovery-t3863402
Click to expand...
Click to collapse
but what would that help you with? having the normal recovery?
mike500005 said:
but what would that help you with? having the normal recovery?
Click to expand...
Click to collapse
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
yes i understand but what would be the goal? what you dont like or are afraid that you dont want the recovery is it because OTA updates? or??? you can try to root it and then reflash the stock recovery.img and apply a patched boot image could work idnk cause i have already done a lot to get mine working with latest update and i don't really want to go threw all the backups again
cris2d2 said:
I just want Root capabilities, I don't want to replace stock Global Stable MIUI.
Click to expand...
Click to collapse
custom recovey doesn't replace rom
indeed what you descripe is the official and recommended root method. TWRP is just for nandroid backup (not really needed since Migrate Backup and Magisk Modules can flash straight from android without TWRP at all), therefore the Magisk.zip is just for traditional reasons. Many devices don't even have TWRP (or with no working encryption support)
Installation
The Magic Mask for Android
topjohnwu.github.io
We no longer recommend installing Magisk through custom recoveries on modern devices. The custom recovery installation method exists mostly for legacy support
Click to expand...
Click to collapse