Hello,
I have a problem while flashing a GSI on my Cubot X18 Plus.
The Phone is Android 8.0 from stock, Treble Check and Community are saying it is treble compatible.
As far as I can say, it is A-partition only, had no seamless updates and stuff.
It has a Mediatek MT6750T and I already unlocked the bootloader and flashed a (unofficial) TWRP recovery.
According to the few "how tos" and how I know from my past flashings (not treble) I tried to flash the GSI, but everytime TWRP says there is no OS installed just before reboot and after telling me the image flash was succesfull.
Now I found another site with a how to about flashing the GSI just with fastboot (fastboot -u flash system image.img).
Now I have a running OS and it seems to work just as supposed.
Quite a while ago I tried this before and had a phone that wasn't receiving any calls...
So my primary question is: Is flshing the IMG with fastboot the same as with twrp?
My secondary: Why the hell is twrp not working? I posted a summary of my steps over here: https://forum.xda-developers.com/an...us-mt6750t-t3806752/post79644287#post79644287
Fastboot is better.....I even have these results on an xperia X
Same happened to me with TWRP, "no OS installed" but it booted to system.
In my opinion, and after flash IMGs with Fastboot and TWRP, I would say it's the same.
Try to reboot even after the "No OS" message and see if it works, if it doesn't boot, just manually reboot to TWRP.
Related
Dear people,
My phone keeps booting in to fastboot mode.
I installed TWRP 3.1.1-0 crackling recovery and unlocked bootloader. So far everything worked fine.
When i wanted to install lineage OS i found trouble. The ROM could not install because there was no /system/ file.
Still no problem, just wipe everything but the external SD and everything should work fine.
Now i can install roms, but everytime i installed a ROM it will go straight into fastboot.
What i have tried:
Lower TWRP to 3.1.0-0
tried original rom fastboot flash boot boot.img & fastboot flash system system.img
Tried another rom: Kenzo's. (TWRP says its corrupted.)
adb sideload rom.
I'm not a i cant get it to work so ill post it person, but i'm really out of ideas.
BTW, i have had many phones in my career and never had issues. SO NO BACKUP (Idiot me.)
I hope you can help me!
Try downgrading to CyangenMod, then install Lineage, see posts #155 / #156 in thread 'Nightly 14.1 lineageOS Rom For Crackling'.
After trying to install a custom ROM (PixelExperience for OnePlus 7T [hotdogb]) via fastboot, the installation flashing ended with errors with "no such partition" for odm, product and system I tried everything to get out of the fastboot screen loop. After finding a bat file with IMG files which got me on the Android 11 Beta 1. build (still no WiFi)
What can I do to fix the partition error to get on the Pixel Experience ROM or even get back to the stable build - I did try MSM but it isn't listing the phone even after pressing ENUM.
Please help...
Context (can skip): The latest stable build OOS for my 7T had issues with the microphone not working and so I decided to do a factory reset which resulted in having a clean install but now, WiFi doesn't connect for some reason. After trying some fixes I decided to install a custom ROM.
U need to flash stock recovery (fastboot flash recovery recovery.img) as twrp prevents fastbootD entry. Then type fastboot reboot fastboot to enter fastbootD. Then flash your rom. Personally, I just flash roms via Chinese twrp or 3.5.10 twrp
HueyT said:
U need to flash stock recovery (fastboot flash recovery recovery.img) as twrp prevents fastbootD entry. Then type fastboot reboot fastboot to enter fastbootD. Then flash your rom. Personally, I just flash roms via Chinese twrp or 3.5.10 twrp
Click to expand...
Click to collapse
that was my process for the first try - entered fastbootD for the flashing process which ended with the mentioned partition error and the fastboot loop. I realised that TWRP version I got from TOOL ALL IN ONE wasn't going to work as it couldn't access data no matter what.
No twrp can decrypt oos or a11 custom roms data. Chinese twrp can access data only on a10 custom roms if u remove screen lock before booting into twrp for backup
What do you reckon I try this time then?
itssata said:
What do you reckon I try this time then?
Click to expand...
Click to collapse
[OP7T][OOS 11.0.5.1 HD65AA/BA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
This is my first thread, I apologize for any mistakes or core aspects left out.
Intro/Formatting KeyBefore I start, I want to give a quick thanks to those contributing to these forums/threads, as it got me through my first custom ROM install ever! Knowing too much information is better than too little, and my want to not waste anyone's time, I'm going to share most of my experience installing the custom recovery and ROM. I will explain what I mean by custom recovery dying at The Dead Recovery. Italics will be used as commands entered in SDK tools. Bold will be used as outputs from cmd.
Phone SpecsPhone: Oneplus 7T HD1905 running Android 11 OOS
Custom Recovery: Chinese TWRP from this youtube video
Custom ROM: Derpfest R for hotdogb found here
My Install ProcessBesides needing to turning off driver signature reinforcement, the bootloader unlock was a normal process. Issues started occurring when I wanted to flash the custom recovery. fastboot reboot fastboot would not give me any feedback on the cmd prompt as it would say <waiting for devices> even though my phone was in fastbootd mode. After reading another thread, I hail married the flash using fastboot flash recovery twrp_best.img. All was great! My phone booted into TWRP, wiped the old stuff, flashed Derpfest, and rebooted. Derpfest works pretty well! (a little buggy but what do you expect from a beta build?).
The Dead RecoveryI notice the safety net with this ROM was broken, so I wanted to install Magisk to fix that issue (I wanted to use Gpay). I download the apk, do my renames for .zip and unintall.zip, and attempt to boot to recovery, but I just get a black screen! Using PWR+VOLUP allows me to reboot into the ROM just fine at least, so I didn't brick my phone. From here, I don't know what I should do to mitigate this issue. Here are my main concerns/questions.
Questions/Concerns1. Will flashing a new recovery allow me to still boot into my phone?
2. Should I use a different image?
3. Should I maybe use flashboot flash recovery_a twrp_best.img flashboot flash recovery_b twrp_best.img to flash the recovery?
Thank you in advance!
I have a google Pixel 2 XL bootloader unlocked via unlock and unlock_critical that I want to use LOS 17.1 with MicroG built in on. It successfully flashes but boots to the bootloader when I boot. I've tried both ROMs I've compiled and the official MicroG builds, same issue. Same issue with 17.x or 18.x versions.
I can successfully flash LOS 18.x official and run it via instructions in that thread (below), which is the same way I am trying to flash LOS w. MicroG.
Anyone know the solution to this ?
Flashing as per below, normally using TWRP 3.3.0.0 also tried latest 3.5.2_9-0. One thing instructions don't mention is whether to swipe to allow changes when you first enter TWRP, I've tried it both with and without that, same results.
Wipe userdata (fastboot format userdata)
Fastboot into TWRP recovery (fastboot boot twrp.img)
Flash the latest build of Lineage OS
Reboot to bootloader and fastboot TWRP again
Reboot to system and don't install the TWRP app
in case it helps others, this was due to the lack of vendor proprietary libs that I thought i was including but wasn't. So apparently that builds flashes but sends you straight to bootloader.
generalnod said:
I have a google Pixel 2 XL bootloader unlocked via unlock and unlock_critical that I want to use LOS 17.1 with MicroG built in on. It successfully flashes but boots to the bootloader when I boot. I've tried both ROMs I've compiled and the official MicroG builds, same issue. Same issue with 17.x or 18.x versions.
I can successfully flash LOS 18.x official and run it via instructions in that thread (below), which is the same way I am trying to flash LOS w. MicroG.
Anyone know the solution to this ?
Flashing as per below, normally using TWRP 3.3.0.0 also tried latest 3.5.2_9-0. One thing instructions don't mention is whether to swipe to allow changes when you first enter TWRP, I've tried it both with and without that, same results.
Wipe userdata (fastboot format userdata)
Fastboot into TWRP recovery (fastboot boot twrp.img)
Flash the latest build of Lineage OS
Reboot to bootloader and fastboot TWRP again
Reboot to system and don't install the TWRP app
Click to expand...
Click to collapse
do you flash disable encrypt,
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
shim80 said:
Hello,
Just after unlocked the bootloader, I flashed Orange Fox recovery and tried to install the last Pixel Experience, but I was stuck on boot animation.
Same for previous Pixel Experience rom.
Then, I tried LineageOS 19.1, and successfully booter on it. But, I got screen that said "Your data may be corrupter" and can't do anything but reboot into recovery.
I'm out of option, now... Did I forgot something ?
PS: I also tried to flash Chikori Kernel but I got error "New image is larger than targeted partition"
Click to expand...
Click to collapse
Try to flash V12.5.3.0.QFLCNXM with Twrp/O.f (TWRP is newer than this OF.)
then
reboot Twrp/O.F
Wipe/format data type yes
reboot Twrp/O.F
Flash rom
Sometimes the flashing of the recovery ROM does not work with the Twrp/O.F in this case use Miflash with a fastboot rom.
If you're still trying to figure this one out, I think I know how to solve your issue installing LOS.
You most likely used TWRP v3.70, am I right?
You should use TWRP v3.61 coz that was the last stable version that worked, the only thing is that you might need to find another custom recovery other than the official TWRP after installing an Android 12 custom ROM like LOS 19.1.
Lineage OS has their own recovery so you'd probably need to use that if you want to update it.
Same issue with me. yesterday. Though mine is fixed.
My workaround was: I installed the official 12.5.3 MIUI using OrangeFox. After boot, I tried installing PixelExperience using Pixel recovery. There I got successfully installed a custom ROM. Alhough I am not sure if the mounting/encryption of Internal SD is the cause.