Hi
I rooted my OPX and installed CM13 and Gapps 6.0 a few months ago.
I usually download new zip files and re-flash my phone every two weeks.
So I downloaded the CM13 and Gapps 6.0 yesterday (version 20161011).
I booted in TWRP 3.0.2-0 and installed the zip files. Reboot . . . . . the phone was stuck in the screen with the One Plus logo forever.
I have everything in my SD card, so I booted in TWRP and wiped data, cache, Dalvik and internal storage, then restalled CM13 and Gapps 6.0. Reboot . . . . stuck in the screen with One Plus logo again.
So I repeated the last step another three times. Nothing changed. :crying::crying:
What I notice is that the usual boot screen has the One Plus logo and the "Powered by Android" near the bottom of the screen. With this issue, on the screen where my phone is stuck, there is no "Powered by Android" wording.
Your help would be much appreciated!
Thank you
SFF_liberte said:
Hi
I rooted my OPX and installed CM13 and Gapps 6.0 a few months ago.
I usually download new zip files and re-flash my phone every two weeks.
So I downloaded the CM13 and Gapps 6.0 yesterday (version 20161011).
I booted in TWRP 3.0.2-0 and installed the zip files. Reboot . . . . . the phone was stuck in the screen with the One Plus logo forever.
I have everything in my SD card, so I booted in TWRP and wiped data, cache, Dalvik and internal storage, then restalled CM13 and Gapps 6.0. Reboot . . . . stuck in the screen with One Plus logo again.
So I repeated the last step another three times. Nothing changed. :crying::crying:
What I notice is that the usual boot screen has the One Plus logo and the "Powered by Android" near the bottom of the screen. With this issue, on the screen where my phone is stuck, there is no "Powered by Android" wording.
Your help would be much appreciated!
Thank you
Click to expand...
Click to collapse
There may be a bug in you last cm version, wipe data and cache flash back to your older version and wait for the next version to get realised
Are you tried another version of CM 13 or any other rom??
SFF_liberte said:
Hi
I rooted my OPX and installed CM13 and Gapps 6.0 a few months ago.
I usually download new zip files and re-flash my phone every two weeks.
So I downloaded the CM13 and Gapps 6.0 yesterday (version 20161011).
I booted in TWRP 3.0.2-0 and installed the zip files. Reboot . . . . . the phone was stuck in the screen with the One Plus logo forever.
I have everything in my SD card, so I booted in TWRP and wiped data, cache, Dalvik and internal storage, then restalled CM13 and Gapps 6.0. Reboot . . . . stuck in the screen with One Plus logo again.
So I repeated the last step another three times. Nothing changed. :crying::crying:
What I notice is that the usual boot screen has the One Plus logo and the "Powered by Android" near the bottom of the screen. With this issue, on the screen where my phone is stuck, there is no "Powered by Android" wording.
Your help would be much appreciated!
Thank you
Click to expand...
Click to collapse
The CM Nightlies have been rebased to the Marshmallow bootloader. You will need to be on OOS3 before flashing it.
Please follow this guide to update.
Even I got the same error..what did u do
Edit: got stuck in oneplus logo screen
Related
Hi Guys!
This is my first time posting here and also my first time using an Android but I'm a bit techie myself. I've jailbroken a lot of iphones but this is my first time rooting. I've read a lot of tutorials about rooting and installing cyanogenmod but it keeps failing. Below are the steps I've done:
1. Root the S3 I9300 (International) using CF-Root.
2. I copied cyanogen mod 9 (stable) and gapps on Internal SD.
3. After going to recovery mode, I've followed every instuctions given, I clicked wipe/factory reset, wipe cache and even wipe dalvik.
4. Then I install/flash cyanogenmod 9. It says insllation complete. then I installed gapps and installation complete.
5. Next step is to reboot, but after rebooting it just gets stuck at Samsung Galaxy S III I9300 boot logo.
I've done that 5 times already and still the same result. I've followed every detail about installing cyanogenmod but I don't know why it doesn't load.
I really need a solution.. Thanks
try format system in recovery before you flash
slaphead20 said:
try format system in recovery before you flash
Click to expand...
Click to collapse
I tried what you said and now every option i choose nothing is happening. Only the robot is showing with a thingie circling around its belly. what do i do now?
flipward said:
I tried what you said and now every option i choose nothing is happening. Only the robot is showing with a thingie circling around its belly. what do i do now?
Click to expand...
Click to collapse
Did you flash cm and gapps after you formatted system?
Hi Guys,
I've rooted my S3, and installed PhilZ Touch 5. Then I clear Data/Factory & Cache along with Delvik. I then proceed to install the custom rom from a zip.
It all installs fine, and says it has done so. But when it reboots, it gets stuck on the GalaxyS3 logo, with a little red Exclimatin mark in the top left corner and stays on that screen until I remove battery or reboot into download or recovery mode...
It seems I just can't load the newley installed roms. I've tried multipul, Archidroid, LiquidSmoot, pureLook HD, etc..
Has anyone run into this problem?
Its an Australian S3, so its the International i9300 btw.
Thanks in advance for any help!
Also, is there a way to completely wipe the phone and start from scratch, as I keep seeing ArchiDroid folders in the SD.
To start completely new you can use mega wipe. It will delete anything but the ext sdcard, hence be careful.
Sent from my Nexus 7 (2013)
Thanks, I'm thinking a MegaWipe would be the best bet, and then start fresh with a custom rom. I need to read more first so I don't screw up the phone..
just to update. the problem was solved with a mega wipe, i installed a new rom, and everything booted normally .
thanksssss
same problem i think except the red exclamation on the corner
Mr. John. i have the same problem now. You removed the battery after being stucked at the logo of samsung right? i wonder, were you able to go back to the home screen after removing the battery? thanks
perseidionix said:
Mr. John. i have the same problem now. You removed the battery after being stucked at the logo of samsung right? i wonder, were you able to go back to the home screen after removing the battery? thanks
Click to expand...
Click to collapse
No, if the phone won't boot after installing a new rom then no amount of battery pulling is going to make it boot.
Flash the super wipe .zip from recovery, assuming you've followed the instructions from your rom chef correctly.
survived the stucked screen
boomboomer said:
No, if the phone won't boot after installing a new rom then no amount of battery pulling is going to make it boot.
Flash the super wipe .zip from recovery, assuming you've followed the instructions from your rom chef correctly.
Click to expand...
Click to collapse
I already escaped the stuck screen. thankfully i have a nandroid back up (and i can still access the recovery mode). i was able to recover my old phone status.
thank you!
I was able to boot into recover & download mode, I was able to flash via odin any custom recovery and boot into it, I was able to wipe the cache/settings & delvik via recovery and then install any rom I liked, I could however not boot into any new/custom rom.
I then ran the MEGAWIPE.Zip in Philz, which I believe wiped some framework or something that was left behind stopping new roms to boot. I then installed a New rom, and it booted right away. No trouble what so ever...
I have twrp installed version 2.8.7. I flashed DU rom and everything went well. Went I reboot the device it just stops on the Google logo indefinitely. In this state it also heats up a lot. Help me please
nyasha1935 said:
I have twrp installed version 2.8.7. I flashed DU rom and everything went well. Went I reboot the device it just stops on the Google logo indefinitely. In this state it also heats up a lot. Help me please
Click to expand...
Click to collapse
Your bootloader is unlocked?
yes
nyasha1935 said:
yes
Click to expand...
Click to collapse
Try these commands in bootloader:
Fastboot format userdata
Fastboot format cache
Note that the 1st command will wipe your SDcard.
Strange, my N9 just started doing the same thing. I wonder if it's a hardware problem (like some bad blocks in the flash memory). I've been running AICP without issues for the past 3 months.
I did notice that I can sometimes press the volume up button on the Google screen, and it will then continue on and boot normally.
(Actually, upon further inspection, it appears that just letting my N9 sit at the Google screen for a few minutes, will sometimes get it to boot).
When I have time, I'm gonna try re-flashing the factory image (LMY48I) and see if that helps.
---Update---
Yup, that fixed it. Fastboot flashed all the .img files, and now my N9 starts normally every time.
Gonna go back to a custom ROM when I get a chance. I'll report back if I see this behavior again.
Sent from my Nexus 9
Hi guys,
I was flashing the latest build of DU and my nexus 9 got stuck at google logo. Since then I tried everything possible i.e. factory reset, flashed the latest factory build, tried using the stock kernel along with the factory image, tried flashing paranoid android. Nothing worked. Can anybody help me fix my device? Should I consider it bricked?
Hello, I have a Xiaomi redmi note 4x. I wanted to install a custom ROM, so I rooted it and flashed twrp. Then I installed nitrogen os and when the device booted it showed me the error that the decryption was unsuccessful and I should do a format to fix the problem. I formatted the phone via twrp but then when it booted in nitrogen os the phone was constantly rebooting. After every reboot I continued from the place I had left. So I thought that this was a ROM problem and I flashed Resurrection Remix ROM. The reboot problem continued, so I flashed lineage ROM, but nothing changed. The device was rebooting every 1 minute. At the end I flashed mido global images for redmi note 4 with XiaoMiFlash tool. The MIUI rom was installed but the reboot problem continues. I haven't manage to set-up my language etc. at the start of installation as the device reboots all the time. Also when I should select a wifi network during the installation, it doesn't even scan for wifi network (it's like the device has not wifi).
Any help please?
Jimmy_979 said:
Hello, I have a Xiaomi redmi note 4x. I wanted to install a custom ROM, so I rooted it and flashed twrp. Then I installed nitrogen os and when the device booted it showed me the error that the decryption was unsuccessful and I should do a format to fix the problem. I formatted the phone via twrp but then when it booted in nitrogen os the phone was constantly rebooting. After every reboot I continued from the place I had left. So I thought that this was a ROM problem and I flashed Resurrection Remix ROM. The reboot problem continued, so I flashed lineage ROM, but nothing changed. The device was rebooting every 1 minute. At the end I flashed mido global images for redmi note 4 with XiaoMiFlash tool. The MIUI rom was installed but the reboot problem continues. I haven't manage to set-up my language etc. at the start of installation as the device reboots all the time. Also when I should select a wifi network during the installation, it doesn't even scan for wifi network (it's like the device has not wifi).
Any help please?
Click to expand...
Click to collapse
Did you try installing miui rom from recovery? Maybe the firmware is bugging out. What exact steps do you take when flashing a rom?
MyNameIsRage said:
Did you try installing miui rom from recovery? Maybe the firmware is bugging out. What exact steps do you take when flashing a rom?
Click to expand...
Click to collapse
I tried and I got an error or the reboot problem didn't stop (I do not remember exactly) . When I was flashing the rom, firstly I did a format in twrp and then installed it. (In twrp I selected to wipe everything except usb-otg and micro sd, which I do not have)
Jimmy_979 said:
I tried and I got an error or the reboot problem didn't stop (I do not remember exactly) . When I was flashing the rom, firstly I did a format in twrp and then installed it. (In twrp I selected to wipe everything except usb-otg and micro sd, which I do not have)
Click to expand...
Click to collapse
ohh man you dont have to wipe everything. just system,data,cache,dalvik.
Ok so, stock twrp does not support miui zips, so you gotta use redwolf recovery. Try flashing the file with redwolf and reply what happens.
Also format data and wipe before you install miui
MyNameIsRage said:
ohh man you dont have to wipe everything. just system,data,cache,dalvik.
Ok so, stock twrp does not support miui zips, so you gotta use redwolf recovery. Try flashing the file with redwolf and reply what happens.
Also format data and wipe before you install miui
Click to expand...
Click to collapse
I installed MIUI but the phone keeps rebooting. I noticed that when it booted the first time it did this: Firstly at the middle of the screen the mi logo showed up and at the bottom it said unlocked (because my phone is unlocked) and after a while where "unlocked" was it started show the loading animation. This was normal, but after a little time the screen blink and it started all over again and then the phone booted. Again I managed to go up to Network set-up (before it rebooted) but no networks was shown (like i have no wifi)
Jimmy_979 said:
I installed MIUI but the phone keeps rebooting. I noticed that when it booted the first time it did this: Firstly at the middle of the screen the mi logo showed up and at the bottom it said unlocked (because my phone is unlocked) and after a while where "unlocked" was it started show the loading animation. This was normal, but after a little time the screen blink and it started all over again and then the phone booted. Again I managed to go up to Network set-up (before it rebooted) but no networks was shown (like i have no wifi)
Click to expand...
Click to collapse
Check this thread out, he had the same problem.
https://forum.xda-developers.com/redmi-note-4/help/help-please-awkward-bootloop-probelm-t3744260
Try messaging him or replying on that thread. I'll try to find more data regarding qfil meanwhile
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Caroline300 said:
Hi,
First I apologise for not having made a back up of my filesystem, I had grown overconfident from previous successful projects ;-/
I have unlocked the phone and installed TWRP recovery. I then used SUPERSU to root the phone under TWRP. After SUPERSU the phone did not boot, it stayed on the WARNING BOOTLOADER UNLOCKED splash for over an hour and did not boot after a reset.
I read through the forums and looked for a kernel to try as I had read that the OS may be damaged, and I wanted to flash a ROM in any case. I read to clean the boot partition before flashing so I did this. The kernel I tried was Squid. This made the phone display "fall through from normal boot mode". So I tried Cyanogen Mod 14, which put the phone on a very rapid bootloop cycle (about every 15 secs), then tried Squid Kernel R22B which put the phone on a long (about 8 minute) bootloop cycle.
Not sure what else I can do. I don't want to give up on the phone as it still mostly works (it has a bootloader, recovery and a file system). I have tried to find a stock ROM to install but proving difficult to track down - links seem to be down)
I apologise if I have got any technical terms wrong. I hope you can help!
Thanks,
Caroline
Click to expand...
Click to collapse
Assuming you've the Lineage 14 zip in your internal storage or micro sd,. Enter TWRP, select wipe, advanced wipe, check system data cache and dalvik, swipe to wipe. Now you've clean wiped your phone.
Then go "install", select the Lineage zip and flash it.
Hi DroidFreak32, thank you for your help. The phone is now booting for the first time since it's "adventure".
Hi,
Unfortunately the phone is still in the boot logo screen. It stayed on the Lineage logo for 2 hours. I have powered off and rebooted once more, and it is still in the boot logo screen now (1 hour later). I'll wipe and install again and post an update.
Hi,
I reflashed Lineage, same problem. I did notice that each time I installed a zip file, SUPERSU asked me to install it prior to reboot to root the phone and I have always hit Yes. On the final flash, I powered off the phone when it prompted me to install SUPERSU, and the phone booted normally. Very nice design on the mod, I like the way the apps are displayed alphabetically. Good work Lineage Team!