I was recently updating to JF's 1.5 update using the JF app. I installed the radio update prior to updating to the 1.5 firmware, and now my phone is stuck on the blue shining "android" logo. I have pulled the battery, and i have also tried two wipes, all with the same outcome...please help.
*update*
With lots of help, the issue was corrected through a system wipe and some coding
**will be psoting very soon what i did** (simply, i believe i just updated in recovery mode to a dev phone.)
i am having the same exact problem i already had v 1.5 formware and i triend to just flash witht he dude verison now im stuck at the second boot screen
both using apps-to-sd?
jashsu said:
both using apps-to-sd?
Click to expand...
Click to collapse
I havent even began to use the cupcake firmware. I just updated from RC 33 JF1.42 to JF1.5 (cupcake) ADP (i believe thats what the JF app said).
butter620 said:
*update*
With lots of help, the issue was corrected through a system wipe and some coding
Click to expand...
Click to collapse
You don't happen to have a worklog of what you did ? I have a similar problem and could use some help.
butter620 said:
I was recently updating to JF's 1.5 update using the JF app. I installed the radio update prior to updating to the 1.5 firmware, and now my phone is stuck on the blue shining "android" logo. I have pulled the battery, and i have also tried two wipes, all with the same outcome...please help.
*update*
With lots of help, the issue was corrected through a system wipe and some coding
Click to expand...
Click to collapse
How did you get it to work Ive had the same issue and was asking questions here
http://forum.xda-developers.com/showthread.php?t=511709
Jairomeo, I had the same issue, and here's my thread with some updates:
http://forum.xda-developers.com/showthread.php?p=3731336#post3731336
lacostej said:
Jairomeo, I had the same issue, and here's my thread with some updates:
http://forum.xda-developers.com/showthread.php?p=3731336#post3731336
Click to expand...
Click to collapse
Thanks, but my problem is, I can wipe and perform the update and use JF ADP1.5 but once I reboot I go into an endless loop. In the thread I posted above I actually have the output from adb
butter620 said:
I was recently updating to JF's 1.5 update using the JF app. I installed the radio update prior to updating to the 1.5 firmware, and now my phone is stuck on the blue shining "android" logo. I have pulled the battery, and i have also tried two wipes, all with the same outcome...please help.
*update*
With lots of help, the issue was corrected through a system wipe and some coding
**will be psoting very soon what i did** (simply, i believe i just updated in recovery mode to a dev phone.)
Click to expand...
Click to collapse
Hey what did you do because I'm having the same exact issue now. It's just getting stuck in an endless loop on the blue android screen
this happens after u update from rc33 jf w.e u have just take the battery out and do a whipe by hitting home+bak button while u start up and do a whipe and then restart your phone mayb take a min or 2 but it will fix the loop and after u should be able to start up regularly =] hope i helped
charmartist said:
Hey what did you do because I'm having the same exact issue now. It's just getting stuck in an endless loop on the blue android screen
Click to expand...
Click to collapse
I dont know if you fixed your issue, mine turned out to be an issue form the Apps to SD. In the link I gave before from my thread I discussed what the cause was. And NOT wiping turned out to be the solution for me.
I had a similar issue looping on the blue android screen, first time i wipe but it repeated itself, though it was a app2sd problem but it wasn't, it was open home beta. Try that, maybe it will resolve your problem.
I had a similar problem when attempting to install JF 1.5. Im stuck on the G1 screen and can only access recovery and stock SPL..... any ideas? Do i need to re install test_keys.img....? Did wipe 3 times... no luck
Related
Okay I installed it by renaming to update then I installed the Radio by renaming it to update then the chip comes up and I reboot and when it comes to the home scrren I try to make a call but I get an error message saying core.process.google. Force Close? So thats a huge problem any fixes for this guys?
Had the same problem after my first boot. The next boot didn't have the error. No problems after that.
ok doing right now.......... and still the same message.... :[
any thing else thanks for that though :]
davidhooper4 said:
ok doing right now.......... and still the same message.... :[
any thing else thanks for that though :]
Click to expand...
Click to collapse
I would reboot into recovery mode, perform a wipe, and then re-flash the RC33 update.
Updating Android is a lot like #2. Wipe every time, no ifs and/or buts.
jashsu said:
Updating Android is a lot like #2. Wipe every time, no ifs and/or buts.
Click to expand...
Click to collapse
Okay its on the recovery i wiped and its flashing the RC33 just have to wait a lil bit.
Yup thanks guys i have to do a wipe JF should put it up just in case someone runs into this again. Mods please lock and thanks
i installed everything and i never wiped.
How to check the radio version you have, to be sure it's a new one?
davidhooper4 said:
Okay its on the recovery i wiped and its flashing the RC33 just have to wait a lil bit.
Click to expand...
Click to collapse
i didn't wipe, but i recommend flashing to RC30 if you have any themes.
Anyone else?
Fully stock? Do a factory reset from stock recovery.. Should fix it. If you're on a custom rom, do a clean flash. (wiping everything except data)
- Sent from an IceCold Hammerhead!
Thx for the advice.
But was wondering if anyone else is getting them.
I'm trying a few things to fix it as I never had a reboot since I owned the phone in November last year, until 4.4.3
At the moment I'm trying an older radio, but it's hard to pin since my last try of using a 4.4.2 kernel kept me up for 35 hours before it happened again.
got an rma replacement.. still happening
meangreenie said:
got an rma replacement.. still happening
Click to expand...
Click to collapse
Did you restore a nandroid on it or anything?
rootSU said:
Did you restore a nandroid on it or anything?
Click to expand...
Click to collapse
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
meangreenie said:
no, is completely fresh
tried everything under the sun over the last month.. factory image installs, running safe mode, no apps installed, new Google account... ect ect
can't stop a soft reboot occurring every 2 or 3 days.. I use to have 'up times' of over a month on 4.4
Click to expand...
Click to collapse
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
vin4yak said:
Upgrade to 4.4.4 and see if it sorts out?? You get random reboots even when the phone is in safe mode?
Click to expand...
Click to collapse
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
meangreenie said:
I'm on 4.4.4.. op was posted when 4.4.3 was out.
I know it's weird, i was very surprised to see my new replacement do it too a little a while a go
.. shrugs
Click to expand...
Click to collapse
Perform a factory reset and see if it sorts things out??
I'm assuming you're stock, unrooted??
still suffering from this
i have noticed that if location is not set to off, it's much better, where it can run for over a week at time
as soon as i turn location off, I'm lucky to get much over 30 hours before it soft reboots
going back to 4.4 it is completely stable as it always was
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Jst flash a newer modem in recovery
mugoftee said:
I am helping a friend to get his One Plus One 64GB to work again after an OTA update broke it.
Initial Problem
Two days ago she started an OTA update which made the phone reboot constantly before even android started. Basically it showed the logo for about 6s then vibrated and restarted again. I later found /o/Android/data/com.cyngn.fota/cache/cm-12.0-YNG1TAS17L-bacon-signed.zip so I assume that this was what was installed.
The phone is completely untouched otherwise. She has no computer knowledge whatsoever and says she didn't give it to anyone.
My attempt
I was able to install cm-11.0-XNPH33R-bacon-signed.zip and cm-11.0-XNPH22R-bacon-signed.zip via sideloading. The phone started ok but was crashing all the time. I am not able to get into settings to activate developer settings (adb) because the crash notifications hinder navigation and after about 10s the whole gui crashes and I see the black screen with the hexagon loading logo. The latter firmware is worse meaning it crashes at a higher frequency.
The Problem
She didn't expect any problems and does not have a backup of her data. Thus I can't do a factory reset or use fastboot.
Question
Did I use the wrong ROM? There seem to be many variants. I haven't found any information which explains the differences.
Could I maybe flash a minimal ROM that would not crash to backup the data and than do a factory reset?
Is there any way to activate adb access without having to navigate to settings?
Click to expand...
Click to collapse
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
PivotMasterNM said:
I've experienced your issues as well when helping another friend out, try using a newer version of cm11s, something like 44S /44R (i dont remember what it is) or 05Q, those should not have the issue and everything should work fine
Click to expand...
Click to collapse
That won't help, flashing an older build than what was previously installed without wiping properly will cause problems.
KURDKiNG said:
Jst flash a newer modem in recovery
Click to expand...
Click to collapse
Modem has nothing to do with this.
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
KURDKiNG said:
Well mines did like it was at lockscreen and wen i tried to unlock it rebooted so i jst flash a modem and booted fine
Click to expand...
Click to collapse
Most likely pure coincidence.
Thanks your reply!
Heisenberg said:
The problem here is that you flashed an older build, going backwards like that is what's causing the crashes. Grab the latest build from here:
https://www.androidfilehost.com/?fid=24052804347802356
Flash that and hopefully you'll be ok.
Click to expand...
Click to collapse
Actually this is what I did in the very first beginning but I encountered the same rebooting symptoms like after the OTA update. Since it didn't seem to change anything I didn't mention it. I used cm-12.1-YOG4PAS1N0-bacon-signed.
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
mugoftee said:
Any other ideas? I am about to unlock it with fastboot but really would prefer not to delete all user data.
Click to expand...
Click to collapse
I don't think you have any other option unfortunately.
Hi everybody,
I'm back with a new problem in my Honor 8 (FRD-L04)... I was one of the user who installed the faulty version 15.0 of the Magisk update, so as you can imagine my phone went into bootloop and had to go all over from a backup I did the past September. I was running the firmware version B385, and because I lost many important things for no backing up lately, I decided I would just update to the firmware version B389. My phone was rooted, so I had to flash a stock recovery and do a full package download for the update. Everything went smooth and the update worked well. I had to do a full wipe because after the update the bootloader locked and I unlocked it to root the phone once again. This happened 2 days ago, and today I tried to use the camera and this is were everything started going down. The camera simply doesn't load, if I clear the data and cache of the app and reopen the app, it shows the initial screen where you need to swipe it to start using the camera but after that it goes in some kind of opening closing loop, until finally it closes. When I try to open it again, it stays in a black screen until it closes. I have restarted the phone and cleared the dalvik/cache in TWRP but the problem persists. I don't know if this is important, but after starting the camera app and failing launching it, the flashlight stops working too. If i restart the phone, and start the flashlight it works well. I have been thinking in reinstalling the camera app, but I can't find the apk for it.
Hope somebody can help me with this small issue, so thanks in advanced
Rommco05 said:
Try to downgrade to an older version
Click to expand...
Click to collapse
Thanks for replying Rommco05... You mean to downgrade to the B385 update? or rollback to B381?
I have found the update.zip file for the B389 upgrade here http://gsmtube.com/android-tips-tri...89-android-7-0-nougat-update-europe-9747.html but the links appear to be broken..
Rommco05, can you help me how to downgrade? I'm a noob at this and your help would be greatly appreciated! thanks
So anyone else having random restart issues no matter what firmware you are running?
I am having this issue even after updating the firmware (yes I managed to get it updated lol didn't realize need to do it in increments rather straight to the latest).
I found a work around sort of but it requires having my hotspot on and another device connected at all times to keep the phone from restarting randomly.
Has anyone else ran into this issue and have a fix? Could it be a battery optimization setting?
Thanks
i got it when i update the rog 5 to latest version so i factory reset it then worked well
messhary said:
i got it when i update the rog 5 to latest version so i factory reset it then worked well
Click to expand...
Click to collapse
Ok thank you for replying, I just finished backing up with Migrate and going to do a factory wipe and then restore all my apps. Hopefully that solves my issues.
I have the same problem for last two firmware updates, for each update I need to do a full factory reset in order to let it work again!