Okay. I am tired of constantly bricking and reinstalling my stock rom onto my Cubot. If not for Titanium Backup i would be so frustrated. So i have decided to ask for help with flashing the Phhusson ROM.
The problem i have is that i do not know the proper steps to install the ROM.
I have unlocked bootloader, installed TWRP, cleared cache, data, vendor, dalvik and installed system.img and magisk for root, but no luck.
I keep getting NO OS installed.
Anyone who successfully installed a CUSTOM ROM for their Cubot X18 Plus please give a tutorial here. Preferably a video tutorial. :good:
Also, if you have any pointers for restoring base band (i have tried flashing stock, copying emmc to root, having driver issues with magic box) i would love help on that but you can private message me if you wanna help (ill pay if you want to be paid, but not much)
You don have to whipe vendor because this is the base folder of the phone its like the kernel but in treble.
You habe to search a pre tested rom on cubot x18 pluss Like AOSP 9.0 from PHHUSSON on GitHub
i wish you good luck, im going to install it to in my cubot, and sorry for my english because im Chilean.
kene200 said:
Okay. I am tired of constantly bricking and reinstalling my stock rom onto my Cubot. If not for Titanium Backup i would be so frustrated. So i have decided to ask for help with flashing the Phhusson ROM.
The problem i have is that i do not know the proper steps to install the ROM.
I have unlocked bootloader, installed TWRP, cleared cache, data, vendor, dalvik and installed system.img and magisk for root, but no luck.
I keep getting NO OS installed.
Anyone who successfully installed a CUSTOM ROM for their Cubot X18 Plus please give a tutorial here. Preferably a video tutorial. :good:
Also, if you have any pointers for restoring base band (i have tried flashing stock, copying emmc to root, having driver issues with magic box) i would love help on that but you can private message me if you wanna help (ill pay if you want to be paid, but not much)
Click to expand...
Click to collapse
Hi, I was able to useflash phh GSI (works just great btw). This is how I ended up doing it:
1. Flash TWRP.
2. In TWRP you'll see errors due to the encryption of the partitions. To resolve this you have to format the userdata partition either with fastboot either with TWRP
3. After fixing the encryption problems in TWRP mount and transfer Magisk to the phone and flash it using TWRP.
4. Transfer the GSI image (A only) and flash it using TWRP. At this stage you could flash it with fastboot as well if you reboot to the bootloader, but don't boot into the system yet. As I said before I used PHH AOSP 9 GSI image.
5. Wipe using TWRP and reboot to system.
The first time I tried to flash it I used the stock recovery wipe function which wipes out the IMEI and stuff, this forced me to reinstall stock rom to set the IMEI with the MTK engineering tools and restart the whole process.
Related
I try to install Lineage 14.1 but I can't because It says wrong bootloader, and that my bootloader is unknown. I installed lollipop by flashing the system.img image and the boot.img image because I had no ROM installed because my internal storage and SD card got corrupt or something. Can anyone help me by supplying a Lineage 14.1 backup or a LineageOS system.img and boot.img file? Thanks in advance...
Wrong bootloader . . .?????
I think the issue you are having is what I was having, and that is that you are not COMPLETELY wiping the previous operating system. Use TWRP's advanced features to make sure you do a complete wipe.
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Billc47 said:
Can someone tell me if you use the advance wipe and wipe the system if that solved the bootloader error, I am concerned because once you wipe the system you have nothing to go back to if it doesnt work
Click to expand...
Click to collapse
I was getting the same error the user above was until I used TWRP's advanced wipe and got rid of everything. Of course make sure you do a backup of whatever you currently have working just in case, but once I did an advance wipe I was able to installed Cyanogen. I however still cannot get Lineage 14.1 to work, it simply gets into an install loop. But since your question was about the boot loader, once I did the complete wipe the error message you are referring to went away for me.
thank you for your reply
hi i am from india and huge fan of huawei i got this phone from usa(mt2-l03) i rooted the phone using some one click root tool and tried to flash twrp which ended in saying recovery image failed,please update to the authorized images.however as there was was root i changed the dpi(think 420) now the phone screen is blank(only in the system ui not the boot image or vendor image(huawei)) i am having the imei and s/n at the battery but i dont have the product id so is there any way i can get the product id and unlock the bootloader of my phone or is there any way to repair my phone
In the general area, in the stickies there are many options you might try. This one https://forum.xda-developers.com/as...to-fix-soft-bricked-phone-using-twrp-t2886630. Seems like it might be the way out for you but I'm not a dev or an expert, just someone who's screwed up his phone alot and found fixes in that section
Sent from my MT2L03 using XDA-Developers Legacy app
Hej everyone,
I flashed a custom rom from mi-globe a few months. It was working great. Then I had the not so incredible idea of updating with latest miui eu 12, because the weekly update from the update menu was not working. It kinda worked, but it got too buggy. So I wanted to come back to a xiaomiEU Stable Rom.
It is now that problems begin. When I flashed miui eu 12, I got recovery loop. Lost all my data trying to fix, but I was able to flash the stock rom via the amazing XiaomiADBFastbootTools in my GNU/Linux distro. It worked! But the main issue is can not flash the custom rom again. I download the custom rom in the internal storage, flash the twrp via fastboot, enter recovery, create full backup, wipe to factory reset and flash the custom rom. Everything seems successful, but then I get a recovery loop again and when I try to restore the backup, the data folder is filled with folders and files with random chars in the names. Apparently the data folder becomes read-only for some reason as well. Then I have to flash the stock rom and tried everything again. I have done it at least 5 times now. I have searched a lot for some solution and nothing works
I have tried the OrangeFox recovery and the mi-globe rom, same issue. I really want a custom rom :fingers-crossed:, but I have no idea what to do anymore. If I could at least restore my backed up stock rom, it would help a lot.
Please help me out and sorry I posted in the wrong section.
Hello
I was at RUI C07 stock firmware.
I've managed to unlock the bootloader and to install TWRP 3.4.0. Then I've tried to flash derpfest (android 10), LineageOS and RevengeOS.
All of them seems to have flashed successfully, but TWRP always warns that there is no OS installed when I try to reboot. When I do reboot, it tries to load something, fails and goes back to TWRP.
What is the problem? Should I try to flash vbmeta? Where can I find it? I'm completely lost.
Thanks in advance
I've just followed the "unbrick guide" and there was little developement...Now the phone boots to fastboot/bootloader by default. I can boot to recovery if I request it. But if I just turn on the system or if I request system, it stops at the bootloader.
What a roller coaster ride!
What seems to have worked for me was to flash yet another ROM (crDroid). But this time I made sure that I've formatted DATA, and then I've wiped vendor, system, caches, internal disk.
I may have forgotten to format the data partition before, which might have been the cause for so much trouble.
If you are reading this, don't forget to format the data partition before flashing a custom ROM, at east when coming from the stock rom.
Hello, I now have 8 days note 10 lite today I unlocked bootloader, installed TWRP via adb after that I installed lineage os and wiping data etc. After that I faced a bootloop and lineageos bootscreen doesnt go away after 15 minutes.
So I tried to reflash the rom again, but twrp isnt able to reinstall the rom. I then used miflash to get original rom again.
Started all over installed twrp, flashed lineage os after this install after reboot I get everytime back into TWRP and looked on my pc and all files suddenly are encrypted on my phone and cant get lineage os rom again on my phone..
So I used miflash again and decided to ask here first. Does anybody know if I maybe use a wrong TWRP or missed a step?
I really dont understand it, I tried it for a 3th time. Here is exactly what I did.
- installed TWRP through ADB (TWRP-3.4.0-0_Android11_Roms_AndroidHQ254)
- In TWRP put rom on my internal storage
- Wipe Dalvik, data and cache
- Install rom (TWRP-3.4.0-0_Android11_Roms_AndroidHQ254)
- data wipe (where I had to type yes to confirm)
- Reboot to system and then it doesnt do anything and goes back into TWRP where I cant do anything, and I have to flash original rom back through MiFlash.
I run now MIUI 12.0.2
Android 10
Try using orangefox recovery. And i think you have to wipe data before installing rom, not after it.
ApexPrime said:
Try using orangefox recovery. And i think you have to wipe data before installing rom, not after it.
Click to expand...
Click to collapse
Thank you, I was able to do it with Orangefox.
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original