I need some help with flashing a GSI Image on BV9500 pro. I managed to flash it one time, and then due a nandroid restore, I had to flash the stock rom.
Now, whenever I try to reflash the LineageOs 17 GSI image or the AOSP, the phone is always stuck at the Blackview logo. I tried everything, wiping the partitons before flashing, using the decrypt, OEM and bootloader unlocked. Nothing works.
Fixing the contents doesn't do anything either.
I have TWRP installed and can access it without any problems.
Any ideas or suggestions?
denis9rafael said:
I need some help with flashing a GSI Image on BV9500 pro. I managed to flash it one time, and then due a nandroid restore, I had to flash the stock rom.
Now, whenever I try to reflash the LineageOs 17 GSI image or the AOSP, the phone is always stuck at the Blackview logo. I tried everything, wiping the partitons before flashing, using the decrypt, OEM and bootloader unlocked. Nothing works.
Fixing the contents doesn't do anything either.
I have TWRP installed and can access it without any problems.
Any ideas or suggestions?
Click to expand...
Click to collapse
I'm using the same phone and most of the gsi roms doesn't boot up.. I only had success with resurrection remix and havoc os but they were too buggy. I think we can't set selinux to permissive that's the huge problem with this phone...
Related
I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now
Hello guys.
I'm having trouble here with a friend's device.
the device simply reboots the twrp.
I already realized the flash of several rons, I also tried with the stock.
installs everything correctly, but at the time of doing the reenicialization in the system returns to twrp again.
I have already tested several versions of twrp and also did not succeed.
Has anyone ever had this problem? I'm finding it very strange, because I've been with rom for a long time and I've never had any problems like this.
What do you think it could be? and how can I resolve and re-restart correctly again?
Thank you in advance.
You flashed the stock ROM and you still have TWRP? Then something is wrong. Usually when that happens you did something wrong. So this is a good thing you are stuck in TWRP. Usually a factory reset will make it boot again. You can pull data off from TWRP before doing this (like pictures and such).
What exactly have you tried to flash (order too), and what version of TWRP are you using. The factory ROM may not have worked as well if you tried to flash the latest, without having the treble partition setup, or did not have a version of TWRP that keeps the vendor partition mounted.
We really need a few more details on what you tried to help.
If you just want to get it booting, I would try wiping everything in BluSpark's TWRP, and flash 5.1.5 OOS.
Hey everyone. Tried to flash a custom ROM for the first (and maybe last time) on the Mi5s from China Stable V10.2 to Lineage OS16. I think i did everything correctly at first
Unlocked the bootloader with Mi Unlock, put the SDK tools into ADB folder, flashed TWRP with command prompt, made a backup, wiped data, disabled force encryption, MAGISK root, flashed Mi5s firmware (although I could only find Oreo), LOS16 (Pie), and OpenGApps
I did all of that and got stuck on the LOS boot animation. Then I wiped data + cache partitions and tried again (didn't work). I quit trying with LOS but instead tried to flash the MIUI Global Stable recovery ROM with TWRP, also only made it to the boot animation. I then did a factory wipe on TWRP and tried to restore my backup but now it would only boot to the fastboot (not even trying to load the ROM)....... I can still access TWRP so maybe I'm not so screwed but what do I do? I just want a functioning device and don't mind if I go back to China Stable although advice on trying to flash a custom ROM would be appreciated. Thanks!
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
bob_bricoleur said:
Hi, earlier, I wanted to change the rom of my mi 5s. I've got an error 7 on twrp during the flash. I tried many things: edit the installation script, format all the data, update and downgrade TWRP, and finally perform a fastboot flash using mi flash and the last one worked. But I am not longer able to flash a custom rom without getting error 7 after the "Patching system image unconditionally" message. I've tested lineage, havoc, pixel experience, miui, even 8.1 rom but same result. I'm stuck with fastboot global miui 10
Btw, I think that after the error the partition are corrupted since I can't repair them with TWRP.
I don't know what I can do more.
edit: I tried to lock and relock bootlander, still geting the same error. I'm stuck on Oreo
Click to expand...
Click to collapse
I think that i figured out something, I am able to flash system.img file using fastboot but I can't flash zip rom using recovery.
As anyone encounter this ?
Did you try reflash twrp latest version?
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.