Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
valvze said:
Hi amigos,
Recently while in school, my phone randomly glitched out so I rebooted it. When rebooting, the phone would read "Android is starting". Then I tried wiping caches in TWRP but that didn't fix the problem. After I got home, I decided to dirty flash my ROM again (HalogenOS). Same problem. Then I tried a clean flash, and that resulted in the same problem. So then, after trying to restore multiple backups and flash many ROM's I got it to boot onto AOSP Oreo. So the phone is working fine, however, does anyone have a good reason behind this? I even wiped the entire phone but that didn't do anything either. I think it happens whenever I try a Lineage based ROM because Omni also booted fine. Any ideas? I want those sweet blobs in XOS
Click to expand...
Click to collapse
Isn't "Android is starting" a normal process? Or was it just stuck there?
Which twrp you're using?
Did you flashed just the ROM or also the gapps?
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Try flashing without gapps.
valvze said:
It's stuck there. I'm using 3.1TWRP an yes I used gapps.
Click to expand...
Click to collapse
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Mr.Ak said:
Try flashing without gapps.
Click to expand...
Click to collapse
Ok I'll try that, thanks
sethu surya teja said:
Maybe you could try fastbooting cyanogen os and then try to flash twrp and lineage rooms again.
Click to expand...
Click to collapse
Ok I'll try that as well, thanks
Related
Hello all
I am facing a strange issue of phone when I took it I out of pocket it started I use multirom was on secondary rom slimkat latest when this happened. When I took it from the pocket it was on my internal rom PA latest beta2 and lost my baseband to unknown and wifi also not working so I went to twrp to flash the radio zip went fine flashing it but when rebooted there was no baseband so tried again for few times but no luck.
So I decided to start clean by removing all secondary roms and did a factory reset of the internal rom and flashed the PA 4.6 beta2 and gapps to start clean but after that the issue started happening it boots till the welcome screen to select language from there it rebooting again into a endless times tried for times to flash the rom again but still it rebooting from that screen . My phone is unusable now.
Can someone guide me how to start clean from here and to boot a rom properly.
Really hoping someone here can help me out on this. Thanks in advance.
Really need some help to get my device back up and running. Right now my phone is on endless reboot loop from the welcome screen of the rom with multirom twrp recovery.
Fingers crossed and waiting. :/
Why don't you start from scratch aka cm11s
-Tunasty
AhmedFaiz said:
Hello all
I am facing a strange issue of phone when I took it I out of pocket it started I use multirom was on secondary rom slimkat latest when this happened. When I took it from the pocket it was on my internal rom PA latest beta2 and lost my baseband to unknown and wifi also not working so I went to twrp to flash the radio zip went fine flashing it but when rebooted there was no baseband so tried again for few times but no luck.
So I decided to start clean by removing all secondary roms and did a factory reset of the internal rom and flashed the PA 4.6 beta2 and gapps to start clean but after that the issue started happening it boots till the welcome screen to select language from there it rebooting again into a endless times tried for times to flash the rom again but still it rebooting from that screen . My phone is unusable now.
Can someone guide me how to start clean from here and to boot a rom properly.
Really hoping someone here can help me out on this. Thanks in advance.
Really need some help to get my device back up and running. Right now my phone is on endless reboot loop from the welcome screen of the rom with multirom twrp recovery.
Fingers crossed and waiting. :/
Click to expand...
Click to collapse
If you read the OP for the PA 4.6 it says not to use the latest gapps as it doesn't work so try out the one that the OP recommends
Sent from my A0001 using Tapatalk
Tunasty said:
Why don't you start from scratch aka cm11s
-Tunasty
Click to expand...
Click to collapse
I think I need to do that. I am at work now need to download the cm11s from the official link. Can you link me to a good guide to start from scratch. Will try clean later today. So I need to go to fastboot manually by pressing vol up button and power button to enter?
Is it a known issue or are there others with the same issue. Please link me there too.
Thanks for the advice.
jojohnson250 said:
If you read the OP for the PA 4.6 it says not to use the latest gapps as it doesn't work so try out the one that the OP recommends
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Used the old micro gapps I don't think that is the issue here. All this started after losing my radio and wifi not working after that strange reboot from my pocket. When I connect to android file transfer it shows no files in the phone and can't move anything to the device also.
Started from scratch and back on stock cm11s. Gone stay pure stock for a while before I start rooting again.
Flashed official cm11s rom through fastboot mode.?
SI have revert from the CM13 to Resurrection Remix (which is also a CM) however Im wanting to change to a predated ROM or even a different ROM and it isnt allowing me. In both CWM and TWRP it says the it installed just fine but when I boot up its still Resurrection and yes I have done all the wipes that should be done and still same thing happens.
How can I fix this?
OK
johneflik said:
Jut use advanced wipe in TWRP then wipe everything except the external SD. I guarantee no thing will boot again unless you flash it.
Click to expand...
Click to collapse
That did the trick, was able to flash again and put back on the ROM before it got stuck on RR. Idk what went wrong in that ROM change, had to edit Updater-Script and got CM13 going again
I run CM 13 and want to back to color os because it is not run so smooth. I format and then flash stock recovery image (then recovery) via twrp and reboot to stock recovery.
In stock recovery i wipe data and cache. That's problem come. Before finish, the screen goes black. I try to power on the device, back to wipe data then the screen goes to black again. I try to boot to recovery and fastboot but it remain the same, back to wipe data and then the screen goes to black..
I try repair it using msm tool but because my comp not recognize the device, i use QFIL. And then i can use the fastboot to boot stock recovery. Suceed. But no os inside. Try and error many times, i can power on the device at the end.
But now the other problem comes. My wifi and bluetooth not work. And message nv backup appear.
Flash project spectrum. Wifi and bluetooth work. I flash back to stock os. Wifi and bluetooth not work again..
May someone help me to solve the problem (make bluetooth and wifi work again)?
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
uyab.com said:
I run CM 13 and want to back to color os because it is not run so smooth.
Click to expand...
Click to collapse
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
kishd said:
To get back to ColorOS from spectrum flash this rom from internal storage.
http://community.oppo.com/en/forum.php?mod=viewthread&tid=41945
Sent from my R7plusf using XDA-Developers mobile app
Click to expand...
Click to collapse
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
celoxocis said:
I think your initial problem was that you didn't flash open Gapps right after you flashed CM13.
Most users who are new to custom roms don't know that they have to flash Google apps separately.
Click to expand...
Click to collapse
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
uyab.com said:
I flashed pico after flash CM. Pico TTS unfortunately has stopped. I use browser, unfortunately stopped. Facebook stopped. Camera stopped. That's the beginning of all the problem because after that i format the phone.
Click to expand...
Click to collapse
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
celoxocis said:
Did you boot into CM after flashing CM? and then installed Gapps later on? This could explain corrupted cache.
Always follow these steps on custom roms. (first time install not upgrade)
Boot into TWRP, select wipe/factory reset.
1. Install CM Rom
after that select the next zip (or add more zips to flash)
2. install Gapps.
Let it boot and setup your phone.
If you follow this you will never have a problem in CM.
Especially the R7 series. Every change to the code is closely tripled (even quadruple) checked by devs.
Because the R5, R7, R7Plus, R7S all share the same base and its tested in on every phone.
Click to expand...
Click to collapse
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
uyab.com said:
Of course not. I flash CM and after that i flash pico right away. Not yet boot into CM. After CM and pico install then wipe dalvik then reboot.
Click to expand...
Click to collapse
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
celoxocis said:
But did you wipe factory reset before flashing all the above? Coming from ColorOS. Else those errors can't be explained.
Click to expand...
Click to collapse
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
uyab.com said:
Yes. I wipe all but not the internal storage. Is it the cause? I do not know why twrp cannot read otg. So i put CM file on internal storage.
Click to expand...
Click to collapse
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
celoxocis said:
I don't know about the R7Plus TWRP. I don't maintain that TWRP. I know that my R7S TWRP works with OTG.
Internal storage should have been fine. I think it will stay a mystery why you received those errors.
Click to expand...
Click to collapse
wish me luck. I will try your suggestion.
uyab.com said:
I use color os now. Have no problem bout back to color from spectrum. The problem occures after that. Wifi and bluetooth do not work.
Click to expand...
Click to collapse
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
kishd said:
Once back on ColorOs from Spectrum. Flash this older version of ColorOs and then CM everything including bluetooth should work fine.
https://www.dropbox.com/s/xmh77xyinz2iero/R7plusfEX_11_OTA_012_all_201512251816.zip?dl=0
Click to expand...
Click to collapse
Oya.. Let me try it..
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
Which method fixed the issue in the end?
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
uyab.com said:
Solved. WiFi and Bluetooth work fine. Run smooth in CM.
Click to expand...
Click to collapse
hi sir im having the same problem with my R7 plus can you help me
i already flash my phone using QFIL with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is only OPPO Logo
flash the phone with Msm8x38 with Oppo_R7_Plusf_EX_11_A.15_160612_By(GsmTechSupport)
result is phone will boot normal but the problem is same with your problem with WIFI and Bluetooth also appear something with NV partion but can be manage with *#268# but with wifi and bluetooth i cant solve
please help me.
thank you in advance
I'm so sorry. I just log in after a long time and read your problem. Have you solved the problem?
same problem for me, no wifi and no bluetooth after flashing stock rom.
Any idea?
uyab.com said:
Maybe bad repaired or bad flashing. Persist folder is empty. Thats why i can not install CM and unvailable wifi and bluetooth address. So flashing persist.img after remove the old one.
Click to expand...
Click to collapse
hello,
please ask me where to find persist.img and the method for flashing it.
thanks in advance
I ran into a bit of a problem recently. My phone suddenly froze, and didn't want to wake. This happens occasionally, so I did what I always do: hard reboot the phone. Hard rebooting resulted in a bootloop, I got stuck in the bootanimation. So at this point, I figured wiping the phone and reflashing would do the trick. Guess what? It didn't. I thought this was a bit odd, so I started to (clean) reflash earlier builds of TugaPower, but nothing seemed to help; every build resulted in a bootloop, except for TugaPower N5. So I decided to just run N5, new N8 build was released though, so I tried flashing that build, still stuck in bootloop.
At this point I lost all hope in TugaPower and decided to flash the official CM14.1 build; no dice, resulted in a bootloop. At this point I tried resetting everything, wiping my complete phone, but nothing helped. Then I tried flashing kwoktopus/updateing AOSP build, which did boot fine! I really want to run CM14.1/TugaPower though, but my phone just refuses to boot on both. Any ideas?
It is worth noting that I've tried almost everything (in TWRP) recovery at this point. From formatting system all the way to running adb to fix the persist partition. Nothing seemed to help. CM14.1 builds don't boot, but AOSP boots fine. WHAT IS WRONG WITH ME? MY PHONE?
Useful info about the phone:
I'm not running multirom;
I am using latest TWRP recovery;
I wasn't deliberately using F2FS or EXT4 memory, partition, whatever (I didn't know what they both did)
TugaPower N5 build ran fine, after that build everything bootlooped
CM13 boots, CM14.1 bootloops
Kwoktopus/updateing AOSP 7.1 build boots fine
Try checking if your /cache partition is formatted to f2fs, it sometimes automatically does that
f41lbl0g said:
Try checking if your /cache partition is formatted to f2fs, it sometimes automatically does that
Click to expand...
Click to collapse
It wasn't, it was in EXT4 format...
Which gapps?
giaur said:
Which gapps?
Click to expand...
Click to collapse
Open Gapps Pico, 7.1 of course. But I quit flashing it after a while, figured I'd keep that out of the equation when I was triangulating the source of what caused the bootloop. It definitely isn't because of Gapps.
Maybe you need to flash a different firmware?
Thepromodder said:
Maybe you need to flash a different firmware?
Click to expand...
Click to collapse
How would I need to do that? I (re)flashed the latest firmware for the TugaPower rom, but I figured that flashing a (new) firmware for the CM14.1 builds wasn't necessary.
Managed to fix it using this link: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
I don't know what causes this to happen, but now you guys know how to fix it.
Had some time custom rom.
Yesterday flashed stock
Everythong was fine. Decided to go back to custom
Unlocked bootloader
Formatted data
Recovery reboot
Factory Reset
Flashed RROS
Step by step with instructions
So it isn't even show a bootanimation
Just stuck with black screen
What to do? I know i can go back to stock with dload, but i want custom
LOL
Just UPD
Installed for fun unstable AOSP 8.0 and it is worked
Strange
Installed RROS above and caught bootloop
All in all animation appeared
Rommco05 said:
maybe you should be before in emui and after again install RROS
Click to expand...
Click to collapse
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom
lofik said:
nothing like this worked
Tried lot of times
Solved this problem by flashing vendor.zip from LOS Rom
Click to expand...
Click to collapse
The Reason Why You Had The Problem Is Because You Installed RROS 5.8.4 Instead Of 5.8.3. You Needed To Install RROS 5.8.3 First And THAN Flash RROS, 5.8.4.
I Had The Same Issue On RROS By Flashing 5.8.4 First.