I took it from the telegram group, and I'm just posting it here.
Made for Android 11, if you use it on android 12 you will have many unexpected bugs.
Download
Important note: I didn't make this twrp, I just took it from the group and posted it here, if you and the created please create a more appropriate post here on xda and I'll delete this one.
Hi,
I changed the tag from Development to Guide, because Development tag is only for original developer (as you are the developer and you are posting it yourself).
Thanks.
Hello. I ported another twrp.
There is a bug. When restoring userdata, the system does not boot
These are the twrp sources from the telegram https://github.com/pjgowtham/recove...mmit/48560f736d92610fbc299a7d86f3f731496f9b42
And these sources are from the ported twrp that I posted
GitHub - TeamWin/android_device_oneplus_lemonadep
Contribute to TeamWin/android_device_oneplus_lemonadep development by creating an account on GitHub.
github.com
AllexBast said:
Hello. I ported another twrp.
There is a bug. When restoring userdata, the system does not boot
Click to expand...
Click to collapse
this backup bug is common, but does everything else work?
SrCDA said:
this backup bug is common, but does everything else work?
Click to expand...
Click to collapse
I solved the problem with userdata, but did not solve it. Probably you need to collect twrp from source. I added system_root symlinks to twrp, they were in the stock boot.img. You can mount all partitions in twrp that I added and see all files. They are displayed correctly.
Partition backup and restore is also correct except for userdata.
system, system_ext,product, vendor is not restored backup. write protection.
The transition between firmware can be done by restoring the super.img backup with a subsequent wipe. So I switched from Indian firmware to Kenyan
Do not try to lock the bootloader, the consequences can be irreversible
These are the latest versions of TWRP ports
You can additionally flash sections with images
system
system_ext
vendor
product
my_region - to remove programs
I can’t flash gsi.img through system_root yet because of the write protection of the partitions that I listed earlier
AllexBast said:
These are the latest versions of TWRP ports
You can additionally flash sections with images
system
system_ext
vendor
product
my_region - to remove programs
I can’t flash gsi.img through system_root yet because of the write protection of the partitions that I listed earlier
Click to expand...
Click to collapse
Allex why don't you create a post, here more detailed, and always updating and with changelogs?
SrCDA said:
Allex why don't you create a post, here more detailed, and always updating and with changelogs?
Click to expand...
Click to collapse
I won't do porting anymore. These were the latest versions. Who will collect from the source, he will lay out.
This is a ported twrp for rui3 india. It works only after the first installation of rui3. As soon as we format the data section, the section will be inaccessible.
As it turned out, with the help of TWRP, you can flash any OTA firmware, regardless of the region.
For a clean installation, flash the firmware into the slot where the system is and make the date format
To update, flash the firmware into the opposite slot where the system is without wipes and date format
How do I use the twrp i can't even access bootloader
And can anyone give me scatter file for realme 9se
How to root this device?
SrCDA said:
I took it from the telegram group, and I'm just posting it here.
Made for Android 11, if you use it on android 12 you will have many unexpected bugs.
Download
Important note: I didn't make this twrp, I just took it from the group and posted it here, if you and the created please create a more appropriate post here on xda and I'll delete this one.
Click to expand...
Click to collapse
Can anyone please tell me how to unlock bootloader of this phone??
Search telegram for realme 9 5g se. We found a way to unlock the bootloader of the Chinese and Indian versions of rmx3461 on 4pda
Related
Unfortunatelly I haven't found any support for this watch (system img, or saved full Twrp backup, factory img...) to repair the softbrick. I have found the ota.zip file, but I can't use it because of the system7 error. I have a Twrp on my watch, but I can't find any way to restart my wach. I'm so sad because I can't use my watch.
me too. I stuck with the smaller model because I thought that it looked much better with my Nemesis leather cuff band than the larger model. But no one seems to have the original system image or a recovery I could use for it since I bricked mine. I've gone back to my Misfit Shine, which is not even close to being a smartwatch
Take a look to my thread, I uploaded a twrp backup, but for WI501Q (system+boot)
TWRP BACKUP
https://www.dropbox.com/s/6d51x7mkub6e5ag/TWRP-2016-03-08.zip?dl=0
matze19999 said:
Take a look to my thread, I uploaded a twrp backup (system+boot)
---------- Post added at 21:25 ---------- Previous post was at 21:16 ----------
TWRP BACKUP
https://www.dropbox.com/s/2dcjdeen58kz0qy/asus2.zip?dl=0
Click to expand...
Click to collapse
I downloaded the file and unzipped it. I booted to twrp recovery and used ADB PUSH to send the files to /sdcard/ on the watch. I then used Install in twrp to install the recovery and boot img files (there is no option in twrp to install system.img). After all of this I still cannot boot the watch, it goes to CSC Fastboot.
Am I doing something wrong?
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
matze19999 said:
Yeah, its a twrp backup file. Create a random backup ( for example only Boot.IMG ) in twrp. It will create a folder in /sdcard/twrp/ which is named XXXX-XXXX. Its different from device to device. In this folder you can move my twrp backup folder. Then reboot again to twrp. Now you will find a backup item in restore tab. Thats my backup
Click to expand...
Click to collapse
Thank you for all the steps.
I tried the steps and I noticed that when I selected the restore option only BOOT was able to restore. So I looked at the backup that twrp made and the filenames were actually boot.emmc.win, recovery.emmc.win, and system.emmc.win. So I took your three files and renamed the img extensions to emmc.win extensions and moved them directly to the backup folder that twrp created. This allowed me to be able to select all three options for restore (boot, recovery and system). The restore completed without errors. However when I reboot the watch it continues to quickly show "Recovery Mode!" and go to "CSC Fastboot Mode!"
Am I still doing this wrong?
download the backup file again and test it
matze19999 said:
download the backup file again and test it
Click to expand...
Click to collapse
I downloaded it again using the same method I described earlier, but I get the same result.
I have the wren device WI502Q.
Backup file is only for sparrow
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Welp i'll just buy a new watch. My CAVS just won!!!! Wooooo!!!!!!
cland216 said:
I guess this thread really does prove there is no support for wren, as the title states. Too bad..
Click to expand...
Click to collapse
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
matze19999 said:
https://r3---sn-h0j7snel.gvt1.com/p...9A6B905E737F34D1021CDEC6AED82CB6617A&key=cms1
stock rom for small version
Click to expand...
Click to collapse
I get an Error 7:
"this device has omni_wren wren:6.0.1/MHC19J"
I updated the watch to MM before I bricked it. Where can I find MHC19J image?
I have a stock Wren on mm, you still need a backup?
couchlock said:
I have a stock Wren on mm, you still need a backup?
Click to expand...
Click to collapse
I am thinking of rooting and would really appreciate a backup just in case. I really would appreciate it and I know others would appreciate it as well.
I'll be off in a couple days. I'll post a link from my mega account when I get it.
https://forum.xda-developers.com/zenwatch-2/general/wi502q-how-unbricked-watch-twrp-backup-t3521916
Unbrick guide I made.
So what do you need a back up of and how do I make the backup. Sorry so long but I finally have time. And a PC again
Haven't seen anyone else discussing this particular solution yet so figured I'd share that we can boot multiple roms using dual boot patcher by @chenxiaolong.
*The only things I'd recommend are the following:
*MAKING A BACKUP FIRST IN RECOVERY. Especially if you've never used the app, this helps in case you misunderstood something or didn't read enough or didn't think enough or the dog ate your homework.
*I recommend using TWRP version 3.0.3-0 which can be found here - https://dl.twrp.me/angler/
* I have not tried this with f2fs only ext4 so naturally I'd only recommend using ext4 partitioning on your device.
* If your device is encrypted in any way booting multiple roms will not work, which should be obvious but I'll state that anyways. Thanks @JKforUA for helping us figure this out.
*If you want to boot more than just two roms, that you use the data slot options for your roms which can be named anything you'd like and they will be stored on the phones internal storage.
* Make sure you're on the latest Radio and Bootloader for the nexus 6p, I flashed this and it works fine and is backwards compatible with Marshmallow roms.
Radio & Bootloader link -
https://forum.xda-developers.com/nexus-6p/general/nexus-6p-radio-bootloader-recovery-t3433637
* Use the patcher app to update the ramdisk and set your primary rom's kernel as Primary before patching or flashing anything.
*If you use the fingerprint scanner you'll have to delete the file /data/system/locksettings.db in each multi boot directory, this disables getting an incorrect pin error when switching roms.
*If using a marshmallow and nougat rom you'll need to flash the appropriate vendor image in recovery before boot.
*Vendor images should not be patched.
This process is fairly simple to me because I've been using it for years but if you have any questions feel free to ask in this thread and hit thanks if I helped ya.
* Before reporting errors I would suggest you try the following steps-
1. Make sure you're using this version of the patcher app because it is the one I have been using without issue -
Version 9.1.0r80-
https://dbp.noobdev.io/files/9.1.0....atcherAndroid-9.1.0.r80.gd5920b2-snapshot.apk
2. Make sure you have enough free space to have two of the zips you want to use because that is what you will have after you patch.
3. Make sure your path to the zip is correct when browsing for the zip, go through internal storage to the directory where the zip is.
4. If you get any error patching, uninstall the patcher app, re-download it, and reinstall it.
5. There is also a Windows version you can try if you prefer.
*If you are still having issues we can discuss it here, and if nobody can seem to come up with a fix in this thread then errors can further be reported by following instructions here - https://dbp.noobdev.io/downloads/
Credits - @chenxiaolong for the patcher app!
Links :
Dual boot patcher (All versions) - https://dbp.noobdev.io
Original forum - https://forum.xda-developers.com/showthread.php?t=2447534
* Screen shots of my current setup attached below for additional guidance if desired.
Status - sharing, using, in some cases testing, always learning (^_-)...
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Thanks for sharing. Used this on my further G4. Didn't know that our device is supported. So no need to wait until multirom is working on 7.1.1. Gonna play around now.
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
DaringDomino3s said:
Thanks for sharing, I've never heard of this before. A few questions;
How similar/dissimilar to multirom is this?
Do I need a specific kernel, or will it with with any kernel?
I briefly read through the original thread, am I creating a zip that flashes two Roms, or is the zip something that flashes alongside the ROM I currently have?
Click to expand...
Click to collapse
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
OmegaBlaze said:
Where do we report errors? I was about to patch several files and the app crashed. I have a couple log files.
Click to expand...
Click to collapse
Hmmm I found this
https://forum.xda-developers.com/showpost.php?p=64727670&postcount=8259
I would try re-downloading the app because I haven't had it crash in any roms I've used yet, I just grabbed the latest build, installed, opened, granted root when prompted, updated the ramdisk if needed which is indicated the app, rebooted when prompted, set kernel, and done.
If it's still crashing for you there's the usual force closing the app from your roms settings and clearing the apps cache and data but you probably already tried that?
t83wood said:
I actually prefer it because it's what I'm used to, you can patch whatever kernel you choose and flash it in recovery, reboot into that rom, open the patcher app, set kernel, profit.
Basically you patch the rom zip you want to flash as secondary, or in my case data slot, naming them 2 and 3 because the Multislot options won't flash anything for me but using data slots works fine. Patch rom, patch gapps, patch whatever kernel, flash all in the whatever succession recommended by the rom op, and you'll automatically boot into the newly flashed rom when you reboot.
Click to expand...
Click to collapse
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
DaringDomino3s said:
I'm gonna play with this over the weekend, I like new stuff!
So whatever fkashable zip I patch will be designated during the flash as secondary (or whatever) and won't overwrite my current ROM allowing it to exist along side it?
Click to expand...
Click to collapse
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
t83wood said:
Correct, so long as you don't patch it as Primary. It will tell you where it's flashing to in recovery. You can also use the dual boot patcher recovery zip for things like switching roms from recovery and wiping roms, wiping multiboot files will get rid of a rom in its entirety if you wanted to replace it with something else. I've always installed the patcher app in my other roms after first boot and used it to set the kernel for that rom too.
Click to expand...
Click to collapse
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
DaringDomino3s said:
If I'm patching for the data partition, am I correct in making all zips (ROM, Gapps, and su) to the same name? (Ex. I named the ROM zip slot "rom2", and then used the same name for the other zips)
Click to expand...
Click to collapse
Yep looks good!
t83wood said:
Yep looks good!
Click to expand...
Click to collapse
Awesome, thanks, I'll see what happens :good:
Edit: it worked! It's a little more involved than multirom, but it seems to be fine! Easier than I thought.
I've not yet switched between the two, but the app on the secondary (data slot) recognizes the primary
Wow great. Running great on data-slot. Even magisk is supported. Good to have a new playground. Happy to have the 128 GB variant. Gonna do some test with Viper.
How do I switch roms
All perfect. Viper running with magisk. Every rom i tried booting without any problem. So atm the perfect tool to test other rom!
---------- Post added at 11:45 AM ---------- Previous post was at 11:43 AM ----------
DEVILOPS 007 said:
How do I switch roms
Click to expand...
Click to collapse
Install dualpatcher app and choose rom in 'ROMs'. Then reboot. Or run utulities in twrp (install).
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Donric13 said:
Cortex also flashes the vendor. Maybe this gives the error because in dualboot all roms use the same vendor partition (could be a problem to flash vendor through dualpatcher...). All other roms i tried vendor was not included to flash (only rom und gapps separately). I am just trying cortex too (just ready to flash). Gonna report, if i succeed.
Click to expand...
Click to collapse
Okay thanks Bro, I might try out lineage. Also open gaps failed for me bit do I need the rom first or do I need to use dynamic gaps? I appreciate the help!
DEVILOPS 007 said:
What do I do? It says failed error code - 1 tried doing cortex rom and selecting data. Is there something I need to do?
Click to expand...
Click to collapse
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Donric13 said:
Cortex rom running fine on multiboot on my device. So no problem with vendor in multiboot. I can also switch back to another rom. As gapps i suggest you to use only dynamic gapps (banks gapps). I always use mini dynamic gapps. Opengapps give many problems.... On primary i got rr oms-release from 12.01. ATM running with 3 different rom all on internal sd card. Just pay attention to give always the same name when patching a zip file in dualpatcher.
Click to expand...
Click to collapse
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
DEVILOPS 007 said:
What do you mean by same name? I am on pimps rr oms and whenever I flash any rom it says error code - 1. Any idea what I can do?
Click to expand...
Click to collapse
Did you flash in twrp (3.0.3.0)? I only use twrp to flash a new multiboot rom. Before flashing a new rom just make sure, you patch all necessary zip files (rom, gapps, etc.). Same name means u choose where (on angler i always choose Data slot - this is internal sd card). Then you give the name (no capital letters) and choose the directory to save the patched file. This you do with every zip file for the rom u gonna flash. The new zip file have the original name and the text "....._data-slot-namegiven.zip" (example for data-slot). The part "data-slot-namegiven" should appeir in every name of the patched zip file. I think with our device it's goot to use the data-slot if you have enough space on your internal sd-card. Using Multi Slot could lead to space problems on system partition of the device. Then just flash the patched files one after another in twrp. Don't forget to flash also patched supersu.zip oder magisk.zip to get root (if it's not in the rom included). You need to patch gapps and supersu or magisk for each slot separately. The name of the patched file just says the path for the multiboot rom. So twrp flashes the patched zip to the right place. Sorry if i wrote to much. Hope it's gonna give you some help. More information you find in the original thread of multiboot.
Sometimes Huawei releases an update package without approving it. For instance, my device (VIE-L29C636) is getting a B382 update, but the update isn't approved for installation. Here's how to update to those update packages.
NOTE: Using this method, you can also safely upgrade your device even if it is rooted, or has some files system partitions altered. (Of course after finished this process, your device will become unrooted and any alteration to the system partitions mentioned below will revert).
Prerequisites:
Your device is already running EMUI 5 (do not attempt this procedure on EMUI 4 ROM, as the partition layout may differ, and the various firmware (modem, sensor hub, etc.) may not compatible.
Unlocked Bootloader AND FRP.
Latest TWRP from OpenKirin (more on that, including download link, click here).
Huawei Update Extractor, for extracting UPDATE.APP.
imgtool, to convert the sparse android image into an ext4 raw image file.
Method:
Download your preferred update package from Firmware Finder app (Make sure to select the one which has 'FullOTA' designation on it. The package doesn't have to be a 'PV' package). Choose 'update.zip' and the other zip that has your region name on it (for instance, on my C636, look for the zip which has 'spcseas' on it's name). I will refer this 2nd zip as 'regional zip'.
Extract the 'UPDATE.APP' from both zip archive.
Using the Update Extractor on a Windows PC, Extract BOOT, SYSTEM, PRODUCT and VENDOR partitions from UPDATE.APP retrieved from 'update.zip', and extract CUST and VERSION from UPDATE.APP retrieved from your regional zip. You should end up with BOOT.IMG, SYSTEM.IMG, PRODUCT.IMG, VENDOR.IMG, CUST.IMG and VERSION.IMG.
Convert PRODUCT.IMG, VENDOR.IMG and VERSION.IMG to an ext4 image using imgtool, for example:
Code:
imgtool PRODUCT.IMG extract
Beware of overwriting the converted image. imgtool is hardcoded to output the converted file to 'extracted/image.img' folder. ALWAYS rename the image.img to something like 'product.ext4.img' after conversion.
Reboot your device to bootloader mode. Flash BOOT.IMG, SYSTEM.IMG and CUST.IMG via fastboot. For example:
Code:
fastboot flash boot BOOT.IMG
Reboot your device to recovery mode. Type
Code:
fastboot reboot
and hold the Vol Up button on your device to enter recovery mode.
Upload the *.ext4.img converted earlier to your device (doesn't matter where, but I recommend using a safe place like '/sdcard', or USB OTG or external micro SD card). you can use 'adb push', MTP or OTG to upload/copy the ext4.img files to your device.
for each *.ext4.img files, flash it to the appropriate named partitions in
Code:
/dev/block/platform/hi_mci.0/by-name/*
. You can use adb shell on your PC, and a command line program called dd on your device. For faster transfer, try to adjusting the block size to 8M. Example commands (execute from adb shell):
Code:
dd if=/sdcard/product.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/product
dd if=/sdcard/vendor.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/vendor
dd if=/sdcard/version.ext4.img bs=8M of=/dev/block/platform/hi_mci.0/by-name/version
Exit TWRP (reboot to system), wait for several minutes for the system to build up it's AOT cache, and enjoy your new EMUI 5 with newer security patch, newer kernel and various features and bug fixes .
EDIT: I apologize that IMGTOOL isn't available in binary form for windows. You can try to use Linux virtual machines to run the IMGTOOL. Any modern GNU/Linux distro should be able to run the IMGTOOL.
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
In my case (upgrading from VIE-L29C636B370 to B382), it doesn't erase user data at all. And there is no reason it should erase the data.
But as always, backup your data before performing this procedure, in case something goes wrong.
How to extract product version Vendors use imgtool..
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
I'm sorry, I forgot to mention that IMGTOOL is only available as binary in GNU/Linux OS. I think you have to use a VM running a GNU/Linux distro to extract product.img, version.img and/or vendor.img using the IMGTOOL.
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
syaif fabian said:
How to extract product version Vendors use imgtool..
Click to expand...
Click to collapse
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
jhleo1 said:
Be Alert, by follow this so called "Easy Upgrade", you need to full backup of your data. It is because after upgrade, all data will be reset.
Click to expand...
Click to collapse
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
faakher said:
@jnakoda
Thank you so much my friend. I was in great trouble as my System Update, File Explorer and Huawei ID apps was deleted from phone due to some experiment. I followed your guide and successfully flashed rom again and boom I got all files back.
Now going to experiment this on B382 firmware
And for those who are curious about this, I successfully used this process for 'meafnaf' region on P9 Plus (VIE-L29)
Once again thanks a lot @jnakoda
---------- Post added at 09:15 PM ---------- Previous post was at 09:10 PM ----------
imgtool is for converting .img files to ext4 raw image files.
To extract files, you need to use "Huawei Update Extractor" which is mentioned in OP.
---------- Post added at 09:20 PM ---------- Previous post was at 09:15 PM ----------
I confirm in my case (reflashing VIE-L29C185B380), data was not removed. But its better to backup your data first.
Click to expand...
Click to collapse
Good Evening i had tried the guide but in my VIE-L09 doesn't work. What can i do? Bootloop infinity
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
great post, but as a simple user, i have no idea how to do this steps.
i have a p9 plus c605 b361 and rooted, and i cant update to anything
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
heeey...anyone here ?!!?
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
maahmd said:
Every time I want to update to a newer version do I need to repeat the steps?
Or I can directly install new updates from finder without confirmation?
Click to expand...
Click to collapse
AYahooo said:
For Windows users, you can use https://github.com/KinglyWayne/simg2img_win (works great).
Click to expand...
Click to collapse
what this is ?!
---------- Post added at 06:51 PM ---------- Previous post was at 06:45 PM ----------
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
maahmd said:
What version? EVA L09: eva_l09b391_nocheckrecovery.img, or EVA L19: eva_l19b391_nocheckrecovery.img ??
Click to expand...
Click to collapse
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Steve2016 said:
This is easier: https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
Image works on P9 Plus too. Used it for VIE-L09C432B380.
Click to expand...
Click to collapse
Tecalote said:
If this Recovery by Atarii really work on VIE too - it's logical that you use for VIE-L09 the L09 version of this recovery
Click to expand...
Click to collapse
I know this but I have a version vie-l29c185 So I do not know which version I chose
maahmd said:
I know this but I have a version vie-l29c185 So I do not know which version I chose
Click to expand...
Click to collapse
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Tecalote said:
If you would say earlier which version you have and if you would search a little bit, then you can find L29:
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
Click to expand...
Click to collapse
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
maahmd said:
i well try this or this now https://forum.xda-developers.com/p9-plus/how-to/easy-upgrade-to-unapproved-emui-5-update-t3649532
Click to expand...
Click to collapse
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Tecalote said:
Try it with the Link I give you.
There's no risk. If it works is good, if not, nothing will be changed. (only Recovery, which can be changed after)
Click to expand...
Click to collapse
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
maahmd said:
Ok i will do it now if it does not work ..do you have a download link RECOVRY bised for p9 plus ?
Or I will pull it out of the update file
I'll tell you the result
Click to expand...
Click to collapse
I don't know what you mean now
Download the Nocheck Recovery for L29 from the Link I give you
https://forum.xda-developers.com/showpost.php?p=75234976&postcount=62
and do the instructions from the OP
https://forum.xda-developers.com/p9/development/eva-nocheck-recovery-flash-unapproved-t3705125
But with the RIGHT Firmware for your VIE-L29 device (3 zips from Firmware Finder /FullOTA)
After updating Firmware Bootloader is closed and Root is gone.
You have to open again (Factoryreset low-level wipe - if it doesn't do 100% do it manually from settings /advanced settings /backup restore /Factoryreset with wipe of internal storage - this is important! ) and flash TWRP and Root again
This will be basically the copy of this thread:
https://forum.xda-developers.com/p10-plus/development/downgrade-p10-plus-oreo-to-nougat-t3724382
But it seems to me that I am not the only one who didn't find it first, so I post it here
I am not responsible if you brick your device, or just damage it!
And all credit goes to @mankindtw and @NoMercyWWE
Always make a backup of your important data, and if you rollback, you need to make a factory reset!
I only tested it with L09, but should work with L29 as well
First of all, you need a P10
2. It only works with oreo firmwares
3. Download the three zip files that are required for update, these are:
update.zip
update_data_public.zip
update_all_hw.zip
Click to expand...
Click to collapse
3/b. You can download them with Firmware Finder, or just search on xda. If you want to make a rollback to Nougat, you need rollback firmwares!
3/c. update_data_public and update_all_hw comes with a slightly different name, but rename both files to these names, otherwise the update will fail!
4. Download HWOTA8 from this topic
5. Put the three update files in HWOTA8 dir
5/b. If you want to rollback, but your files in the repack folder, and run repack.bat
6. Create a new folder on your EXTERNAL sd, named HWOTA8
7. Put your three files in it, plus copy MHA_RECOVERY8_NoCheck.img, and hwota8_update.zip
8. Now install P10 Plus twrp_oreo.img, if you havent't yet:
fastboot flash recovery_ramdisk twrp_oreo.img
Click to expand...
Click to collapse
credit to @OldDroid
9. Reboot into recovery, install hwota8_update.zip it replaces your recovery with the Mate 9 one, reboots and updates
10. Done! If you downgraded, or just encounter any problems, go back in recovery, and make a factory reset!
Can I do this without an sdcard?
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
I think it is possible, but you need to rewrite hwota8_update.zip, since the links there are pointing to the external sd. But I dont know what you need to write there instead
Not sure if I did this right but now my phone shows---> Build number System 8.0.0.046(02ZP)
I had showing before---> Build number System 8.0.0.046(01BN)
I don't seem to have it right still
I also have somethong like System 8.0.0.046(02BQ) but .321(C10) installed. And there were some visible updates from the C900log Oreo, eg auto shazam disappeared from the status bar.
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Droiduser67 said:
It's frustrating lol...my old Nexus 5 was so easy compared to this device...I know I updated with something cuz I also see January 1st security patch and other little differences...everything seems to work ok but still got no themes though...how do we get it right?
Click to expand...
Click to collapse
Here he says that you need to install su, and rename three directories, but for me themes are working even without this. As soon as I try it, these steps will be added to the tutorial though.
EDIT: I followed the steps and renamed the directories, but there was no change anywhere.
Yes just tried it myself too and no change...still no themes...had an extra folder in there on mine named "optus"...not sure but the twrp and rooting work awesome but wasn't able to make a nandroid backup to my external storage...it failed
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
---------- Post added at 12:54 AM ---------- Previous post was at 12:51 AM ----------
dmmercado23 said:
Can I do this without an sdcard?
Click to expand...
Click to collapse
Without a SD card it is impossible, with firmware via TWRP, internal memory can be reset and then the firmware will not go to the end. Therefore, the programs are located on the SD.
urn said:
Good day,
with what firmware (please complete naimeninie) you rolled back and what was installed by this method?
Click to expand...
Click to collapse
If this question is for me, I did not test the rollback (I am fine with Oreo), but I would use C432B180. You can check the description of an update in FF to see if it's a rollback one.
Here's the solution : https://youtu.be/WYSVq1TE2kI
OREO
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Nakedchef said:
Can anyone help me android oreo on my Huawei P10
to install?
- OS = Ubuntu 17.10
- Huawei P10 (VTR-L09)
- Bootloader unlocked
- Device rooted
Click to expand...
Click to collapse
Hey, there are many ways of doing it i would recommend https://forum.xda-developers.com/showthread.php?t=3691013
[GUIDE] Huawei P10 Debrand/Rebrand/Update for Nougat&Oreo it works great. Go for the hwota rebrand way, it work like charm for me.
Sent from my [device_name] using XDA-Developers Legacy app
Perfect! I applied the update as described in the OP, then did a factory reset and relocked the bootloader (which did another factory reset). Now, at least I can't tell anymore that the phone has been unlocked and rooted...
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
dukenuken said:
Hello, I have a problem in the rocovery that I flash wota8_update.zip I have E: unknown command [errno]
Updater process ended with ERROR: 9
Error installing zip file '/external_sd/HWOTA8/update.zip
Click to expand...
Click to collapse
Which TWRP are you using?
Welcome to SystemRW by lebigmac
This script removes the read-only lock of all partitions embedded in the super partition of your stock firmware. This allows you to debloat all unnecessary system apps, customize your device to your liking and make MIUI run as smooth as silk!
MIUI 12 is great but it's a little bit bloated and some bugs here and there.
Developed on Xiaomi Poco X3 NFC and works like a charm over here!
Visit project thread
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
can it work for vendor too ?
I really want to flash files that request mount system and vendor
@Abdullah.Csit
Yes the script makes all partitions (system, vendor, product...) that are embedded in your super.img read-write-able and adds extra space to them so you can write data to them later. Then it merges these modified partitions back into a single brand new super_fixed.img and flashes it to your device. Works in both custom recovery and in Android operating system.
User data is not affected.
Now it's possible to modify for example the default.prop or the init.rc and make many more customizations to your device if you know what you're doing. Make sure to always back up an important system file before modifying it. This way you can always restore the original file from recovery and remove the bootloop if something goes wrong.
In the worst case scenario you can always flash a new super.img
placeholder
after 2 days long battle with numerous attempts to install Ubuntu on my windows PC I was finally successful, only to find out:
Spoiler: boring, but it happened
- that RW enabling script can't save super image to my phone sdcard (permission denied)
- that I have to make backup of super partition manually and let the RW enabling script "eat that"
- that my phone super partition is somewhat damaged and RW enabling script ended always with error that it can't resize vendor because it is too big (maybe it wasn't really damaged, but I had already flashed RW vendor provided by another user and it somewhat (probably) collided with the tools used)
- that super.img from fastboot version of MIUI ROM can't be used directly with RW enabling script, because for whatever reason it complained, that that is not an super image
- that I have to flash that clean fresh super.img from fastboot version of MIUI ROM via fastboot to my phone with edited flash script (so it doesn't overwrite my data and recovery partition) and make a backup of it in recovery
- and that backup of clean fresh flashed super.img from fastboot version of MIUI ROM of was finally accepted by RW enabling script, that did it magic, only to find out:
- that final flashing process of fixed super.img to my phone freeze at third section from all seven (now there I was really afraid that my EMMC died because of extensive flashing)
Was that all Mr. Murphy?
- so I had excellent idea that I can obviously use my recovery to flash that fixed super image, easiest thing in the world, right?
- but Ubuntu and Mr. Murphy proved me wrong, because I was able to copy on my phone storage/sdcard anything but that fixed super.img (don't ask me why it didn't even started copying, I'm no Linux user, and that MTP error was pretty alien to me)
- so I had to somehow copy that fixed super.img from newly created Linux space to my Windows space, from where I was so sure I can finally transfer it to my phone internal memory and finally have flashed it where it belongs
- but anything that I writed in Ubuntu to my Windows disks mysteriously disappeared after one click on the file (created on Ubuntu) in Windows ()
- thanks to my rented cloud storage somewhere on the internet I was able to upload that fixed super.img (way faster (thanks to my very fast optic line) than any other solution available to me at that time)
- after reboot to Windows downloaded it and finally was able to upload to my phone from Windows, flash it to super partition via recovery
- and finally re-flashed all need components for my custom ROM and after all that it finally booted into Android
- uff, anyway - it can be done, and it is RW for system, vendor and product
- so thanks @lebigmac for providing possibility
- now we need to persuade TWRP/OFOX maintainers that they can enable again wipe system option (of course it would be only active on RW enabled super partition)
sorry @jeryll that you had to go through so much trouble because I only made Linux only version :/
I am working hard on version 1.15 right now and that should also work for Windows and Mac users as well. I'll try to release it ASAP
To flash the original super.img which you extracted from the Xiaomi fastboot ROM you can simply do:
Code:
fastboot flash super super.img
This should not overwrite your user data.
The good thing about the Poco is it's very forgiving. I must've flashed my super partition at least two dozen times already and it still works like a charm
lebigmac said:
sorry @jeryll that you had to go through so much trouble :/
I am working on version 1.5 right now and that should also work for Windows and Mac users
Click to expand...
Click to collapse
nothing to be sorry for, it was an battle and I won, hopefully new version will be more user friendly + Windows version will be the sweet bonus (for me), thanks again for making this possible
Hey jeryll new universal version available HERE
This should make things easier for the windows and macintosh folks
Today I uploaded the new v1.26 to the project thread
How do you guys like the script so far? Any issues with the Poco X3 NFC? I've only tested it with Android 10 so far but it should also work with Android 11
Hey I recently installed custom rom on my one plus 7t pro(hotdog) . I done it by flashing system, product, boot, etc seperately . When i used your tool it create a super_fixed.bin file . I don't know how to install (I think it is corrupted i tried payload dumper and 7zip to seperate system file from it). What should i do ? Please Help.
Shadirvan said:
Hey I recently install havoc is rom on my one plus 7t pro . I done it by patching system, product, boot, etc seperately . I don't have a super.img how can I convert system to RW without super img
Click to expand...
Click to collapse
I don't have a working twrp for my device
Shadirvan said:
Hey I recently installed custom rom on my one plus 7t pro(hotdog) . I done it by flashing system, product, boot, etc seperately . When i used your tool it create a super_fixed.bin file . I don't know how to install (I think it is corrupted i tried payload dumper and 7zip to seperate system file from it). What should i do ? Please Help.
Click to expand...
Click to collapse
probably experiencing the same thing but whats happening is i cant install anything because for some reason, /system cannot r/w
sorry for bad english
Shadirvan said:
Hey I recently installed custom rom on my one plus 7t pro(hotdog) . I done it by flashing system, product, boot, etc seperately . When i used your tool it create a super_fixed.bin file . I don't know how to install (I think it is corrupted i tried payload dumper and 7zip to seperate system file from it). What should i do ? Please Help.
Click to expand...
Click to collapse
Shadirvan said:
I don't have a working twrp for my device
Click to expand...
Click to collapse
Hi @Shadirvan
It is recommended to always use latest official version of my script (currently v1.32 - new version coming soon!).
Please keep in mind that my SystemRW script was designed for stock firmware and not for custom ROM. Custom ROM's should have r/w capability by default. If your custom ROM doesn't offer this functionality straight out of the box then you should rethink why you even installed it in the first place. Just my 2 ¢
I cannot tell you what you should or shouldn't do but I can tell you what you can do:
You can manually flash super_fixed.bin to your super partition like this:
Bash:
adb reboot bootloader
fastboot flash super super_fixed.bin
Please report back your results. Good luck!
davepayra said:
probably experiencing the same thing but whats happening is i cant install anything because for some reason, /system cannot r/w
sorry for bad english
Click to expand...
Click to collapse
Hello @davepayra
Please tell me more about your device and send me your log files from script folder at
/data/local/tmp/systemrw_1.32/log/
And you can send me some screenshots to better illustrate what you are talking about.
Thanks.
lebigmac said:
Hi @Shadirvan
It is always recommended to use latest version of my script (currently v1.32 - new version coming soon!).
Please keep in mind that my SystemRW script was designed for stock firmware and not for custom ROM. Custom ROM's should have r/w capability by default. If your custom ROM doesn't offer this functionality straight out of the box then you should rethink why you even installed it in the first place. Just my 2 ¢
I cannot tell you what you should or shouldn't do but I can tell you what you can do:
You can manually flash super_fixed.bin to your super partition like this:
Bash:
adb reboot bootloader
fastboot flash super super_fixed.bin
Please report back your results. Good luck!
Hello @davepayra
Please tell me more about your device and send me your log files from script folder at
/data/local/tmp/systemrw_1.32/log/
And you can send me some screenshots to better illustrate what you are talking about.
Thanks.
Click to expand...
Click to collapse
hi, i have a few questions because i did something wrong about installing custom rom
1. is there any way i can flash corvus os again because it says error 1: cant install zip file?
2. is there a possibility that my twrp version prevents me to r/w in system partition?
3. if ever my system partition doesn't have os installed, should i first install vendor image, then proceed to custom recovery to install corvus os (if vendor image enables writing on system partition because ive read a thread that says by reflashing broken firmware, all partitions can return to their normal state and continue r/w in system partition)
davepayra said:
hi, i have a few questions because i did something wrong about installing custom rom
1. is there any way i can flash corvus os again because it says error 1: cant install zip file?
2. is there a possibility that my twrp version prevents me to r/w in system partition?
3. if ever my system partition doesn't have os installed, should i first install vendor image, then proceed to custom recovery to install corvus os (if vendor image enables writing on system partition because ive read a thread that says by reflashing broken firmware, all partitions can return to their normal state and continue r/w in system partition)
Click to expand...
Click to collapse
Hi. I would suggest you install official stock firmware on your device. Check your device subforum here at XDA on how to do this. Then afterwards you can try my script if you want to make your device fully read/write-able. Good luck!
lebigmac said:
Hi. I would suggest you install official stock firmware on your device. Check your device subforum here at XDA on how to do this. Then afterwards you can try my script if you want to make your device fully read/write-able. Good luck!
Click to expand...
Click to collapse
thankyou sir. i will do that. best wishes to me
after doing this sir, do i have to unlock my bootloader again to flash custom rom or there is no other way?
also, will i be able to keep my twrp or should i still flash it again?
What an immaculate, well written and commented script! Easy to know what it does and why.
Worked a treat on my rog 5s pro.
Thread has been closed! The account of the author of this thread has been permanently suspended. Please, I ask everybody not to promote a banned user or his website, blog, work etc on XDA. Thanks very much for your cooperation.
Regards
Oswald Boelcke
Senior Moderator