I had my Coolpad 8676-i02 flashed with AOSPExtended v4.3 and when rebooted the system became unstable rendering no access to any App as they were all closing down on touch. Post booting updates did not complete as well compelling me to Backup & Reset that resulted in booting into TWRP recovery mode without boot image present.
Now, I have again successfully flashed AOSPExtended v.4.3 + Beans Gapp Full 7.1.x but when I reboot mobile, the system is yet booting into TWRP Recovery mode.
Can someone suggest me how to launch my mobile system working normally again.
Wipe everything and format data also then try to install ROM again.
If that's not working,
Flash the stock ROM and then install twrp and ROM it'll work fine.
If that's not working,
Go to the ROM thread and search for how to flash and some special thing to take care .
If that's not working,
Try to contact the developer ie AEX ROM's people
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
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'.
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
UKWZ7 said:
I wiped the phone clean and tried to flash the new version of AEX But, it showed Error 7.
Tried looking for fix for Error 7 on internet, it didn't work for AEX5.6, 5.5, 5.4.
5.3 installs normally.
But felt like needed something new.
Went on the forums to find Xtended ROM. Flashed it.
After flashing it tried flashing Nano GAPPS.. Didn't work.
Tried to system reboot and thought I can later work it out.
ROM is all fine... But, later when I got to recovery mode.
(Problem begins)
I realised I lost TWRP.
And the recovery that's there wouldn't allow me to flash anything.
It looks more like CWM recovery but with less options.
It doesn't even have a advanced wipe!
Now I'm stuck with a non rooted phone, without Google bare minimum functionalities.
Am I alone? Help me out!
Click to expand...
Click to collapse
For aex issue did you flash factory2vendor zip before flashing rom?
You will have to install twrp image using PC. Like the first time you did when you were unlocking bootloader
Flash zui using qfil or miflash.
If bootloader is unlocked still. You can directly flash twrp.
If not first unlock your bootloader and then flash twrp.
For treble rom like aex5.5 you need to flash factory2vendor.zip and then flash twrp with treble support.
For info on flashing and link visit aex5.5 rom page.
I tried bliss rom pie on realme2pro.Here is some screenshot link-
https://imgur.com/rBKNRQQ
https://imgur.com/Q7g68mR
https://imgur.com/bEKYvS8
https://imgur.com/nDkrhiH
https://imgur.com/mddj5yk
https://imgur.com/xfN23Yp
Anyone tried yet?please try and let me know is it suitable for our realme2pro or not.
bliss rom gsi pie arm64 a only
link- https://www.xda-developers.com/bliss-roms-android-pie-gsi-project-treble-release/
it booted fine
Is fp working in this and the gcam??
No brother,fp not working
I tried A only using TWRP (latest version), but it just hangs at the realme logo then reboots back to recovery.
Note: even though I flashed the img to the system partition it complained no OS was installed.
Prior to that I had done a factory wipe and then a system wipe.
https://forum.xda-developers.com/pr.../rom-blissroms-9-0-official-4-4-2019-t3918303
11.7 A-Only Build with Gapps built in
11.8 A-Only Build Stock (without Gapps)
Both versions failed!
Many a times brother due to vendoe problem this loop happens. When this loop happens try to boot to recovery and flash vendor.img and you will be able to boot to rom
Step For Flashing-
1.latest twrp or r2x2 recovery
2.then backup
3.wipe system,vendor.userdata,cache,delvik cache for clean install
4.flash vendor zip first link- https://androidfilehost.com/?fid=1395089523397931146
5.unpack sytem image flash to system link- https://androidfilehost.com/?fid=1395089523397933944
6.wipe cache and delvik cache
7.Swipe to reboot
8.wait for few minutes it booted to bliss rom
caution-
latest system color os a.17 build vendor not worked
flash only linked vendor zip from above
then you good to go
best of luck
galibalmasanick said:
Step For Flashing-
1.latest twrp or r2x2 recovery
2.then backup
3.wipe system,vendor.userdata,cache,delvik cache for clean install
4.flash vendor zip first link- https://androidfilehost.com/?fid=1395089523397931146
5.unpack sytem image flash to system link- https://androidfilehost.com/?fid=1395089523397933944
6.wipe cache and delvik cache
7.Swipe to reboot
8.wait for few minutes it booted to bliss rom
caution-
latest system color os a.17 build vendor not worked
flash only linked vendor zip from above
then you good to go
best of luck
Click to expand...
Click to collapse
The same problem persists. It loads the REALME logo, and immediately reboots into the Bootloader.
Is vendor.zip flashed using TWRP Install? Or does it have to be flashed to "boot"?
vendor only flashable from twrp recovery
batflashholmes said:
The same problem persists. It loads the REALME logo, and immediately reboots into the Bootloader.
Click to expand...
Click to collapse
whats the variants phone are you using?
4/64 or 128ufs
indian or others
are you flashing inside any mode?
just flash vendor zip & bliss img to system and reboot,wait some time
Got it to work after flashing vendor.img
Does this require a device specific kernel to already be installed from a previous ROM? When I checked the kernel in my Realme 2 Pro it was the same kernel as what is used by device specific ROMs: 4.4.78-perf+
Can I flash a different kernel from here?
https://github.com/BlissRoms-Kernels
i am not responsible for that,you may try but recommend-no,thanks a lot
galibalmasanick said:
whats the variants phone are you using?
4/64 or 128ufs
indian or others
are you flashing inside any mode?
just flash vendor zip & bliss img to system and reboot,wait some time
Click to expand...
Click to collapse
I use a 4/64 model. Indian itself.
I did not flash inside any mode (that I know of at least).
I ended up bricking my phone completely somehow. It would show the RealMe logo, and then boot up into a blank white screen with an input bar, and keyboard. But nothing else. It refused to boot into the bootloader as well, saying that there was some error.
Also, I had tried flashing the vendor zip first, and then the bliss img. Whenever I did that though, it would show "No OS installed. Do you want to continue?"
Thanks for trying it but this isn't working on your device & I am also sorry, plz try stable rom from xda or stock rom that can be best for you,best of luck ?
So I tried to clean flash and install RR on my RealMe X.Everything went fine aprt from the fact that phone isn't booing into the new rom.It just boots back to the recovery.
I tried flashing vbmeta but its the same.Anybody knows what is going on?
thanks in advance
Edit - Changed the recovery from 3.4.0.0 to 3.3.1.1 and the problem is gone
And formatted data after installing the rom