WiFi Hotspot Error - Nexus 5 Q&A, Help & Troubleshooting

So I'm sure many of you are aware of this issue. I've encountered it twice on my Nexus 5 on both 4.4.2 and 4.4.3. Basically, if you enable/disable WiFi and WiFi Hotspot in a certain order, it breaks the tethering option and says error where it should say turning hotspot on after you click the box. Now, the only way I've been able to fix it is by doing a clean install of the factory images. Even writing the factory system, boot etc. does not fix it. Has anybody encountered this issue and found a way to fix it without wiping your phone?

GTI6speed said:
So I'm sure many of you are aware of this issue. I've encountered it twice on my Nexus 5 on both 4.4.2 and 4.4.3. Basically, if you enable/disable WiFi and WiFi Hotspot in a certain order, it breaks the tethering option and says error where it should say turning hotspot on after you click the box. Now, the only way I've been able to fix it is by doing a clean install of the factory images. Even writing the factory system, boot etc. does not fix it. Has anybody encountered this issue and found a way to fix it without wiping your phone?
Click to expand...
Click to collapse
I ran into this same exact problem on my N5 after I flashed the bootloader, radio, system and boot from the 4.4.3 factory image. It would say "error" under the WiFi Hotspot option when trying to activate it, even though it was working perfectly fine on 4.4.2. It was driving me crazy trying to figure out what it was happening. I'm not aware of any fixes. I ended up just backing up my stuff and flashing the whole factory image (including userdata.img). Then I edited the database file just like I did in 4.4.2, and now it works perfectly once again. It was all kind of a pain though.
Sent from my Nexus 5 using XDA Free mobile app

charesa39 said:
I ran into this same exact problem on my N5 after I flashed the bootloader, radio, system and boot from the 4.4.3 factory image. It would say "error" under the WiFi Hotspot option when trying to activate it, even though it was working perfectly fine on 4.4.2. It was driving me crazy trying to figure out what it was happening. I'm not aware of any fixes. I ended up just backing up my stuff and flashing the whole factory image (including userdata.img). Then I edited the database file just like I did in 4.4.2, and now it works perfectly once again. It was all kind of a pain though.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Experianced exact the same thing. Love the new dailer so I don't want to rollback, but I really need my hotspot at work.
Someone any ideas?
/best regards, Carl-Marcus

CamaloConsulting said:
Experianced exact the same thing. Love the new dailer so I don't want to rollback, but I really need my hotspot at work.
Someone any ideas?
/best regards, Carl-Marcus
Click to expand...
Click to collapse
Oh. My bad. It looks like I didn't explain as best I could. When I said "...flashing the whole factory image (including userdata.img)...," I meant I flashed the factory image for 4.4.3. Then, I edited the database file like I did back when I was on 4.4.2. So I actually am on 4.4.3, and the hotspot feature is working perfectly (like it was on 4.4.2).

I too had this. Switched to CM, as i was thinking of it and its gone. Have flashed a stock ro m and it was OK
# 47386

Related

Portable Wifi Hotspot Error after 4.4.2 update

Anyone else have an error enabling Portable Wifi Hotspot after updating to 4.4.2? When I was on 4.4 everything was working correctly until the update.
I havent tried tethering prior to the 4.4.2 update but today an instance came up to use it and it just gives me an error. Thought it might be carrier blocking but nope. Just did a google search and found this thread so just wanted to say i have the same issue. All on stock rom and kernel btw.
EDIT: ok so i decided to go and flash faux kernel (dec 7 release). Lo and behold, tethering is back and working. I guess theres a bug in the stock kernel.
Just chiming in that I am also getting an error with 4.4.2 on the wifi tether.
Worked on 4.4 without an issue though.
Sent from my Nexus 5 using Tapatalk
If you have root, delete folder "/data/misc/wifi" and reboot will fix it. Tested on stock 4.4.2.
Works great for me. Thanks.
Couldn't figure out what my issue was after restoring a Nandroid of an earlier version of Mahdi ROM. This worked perfectly. Thanks!
Didn't work for me
______ said:
If you have root, delete folder "/data/misc/wifi" and reboot will fix it. Tested on stock 4.4.2.
Click to expand...
Click to collapse
I actually don't even have that folder, is there anything else anyone can think of?
I have also got this error after restoring from nandroid backup. before that, tethering worked perfectly (on 4.4.2). unfortunately, deleting /data/misc/wifi and rebooting does not work for me, the error is still there. any ideas?
Wifi Hotspot Nexus 5 error 4.2.2
qot said:
I have also got this error after restoring from nandroid backup. before that, tethering worked perfectly (on 4.4.2). unfortunately, deleting /data/misc/wifi and rebooting does not work for me, the error is still there. any ideas?
Click to expand...
Click to collapse
Did you restore from a USB or Internally? Having the same issue, thought it was my kernel, and yes I tried the solution of deleting the data/misc/wifi file and reboot but as soon as you throw on Hotspot, it has an error and wifi stops working too-Please Help!
Have had the error a couple times with the device. The folder delete trick never worked for me. One time I had to restore a nandroid to correct the issue. The other time I had to reflash the ROM (running stock, xposed, and GB )
Sent from my manta
After doing some testing I think the issue is from the restoring through TWRP, I just installed a freshly new rooted stock 4.2.2 and so far no issues, if you guys have any ideas-please comment away
I had this problem. In the end I switched to cm 11.
From the wonders of mobile telephony.
Worked for me on both my Nexus 4 & 7 that are using cm 11. Cheers
______ said:
If you have root, delete folder "/data/misc/wifi" and reboot will fix it. Tested on stock 4.4.2.
Click to expand...
Click to collapse
CoreyWat said:
After doing some testing I think the issue is from the restoring through TWRP, I just installed a freshly new rooted stock 4.2.2 and so far no issues, if you guys have any ideas-please comment away
Click to expand...
Click to collapse
You're probably right. I today installed the fresh 4.4.3 factory image (wiping enabled). I then installed twrp. Then tried to tether on the fresh system and it worked.
After that I used twrp to do a backup, which I immediately restored. Tethering then was broken again.
Can someone else confirm this?
r4pp3l said:
You're probably right. I today installed the fresh 4.4.3 factory image (wiping enabled). I then installed twrp. Then tried to tether on the fresh system and it worked.
After that I used twrp to do a backup, which I immediately restored. Tethering then was broken again.
Can someone else confirm this?
Click to expand...
Click to collapse
I can't confirm the TWRP backup, however it didn't work ever since I installed the 4.4.3 factory image with wipe.
This worked on the v4.4.2 tmobile NX5 to get the hotspot working properly [ I do over 200g a month with this method]
http://pocketnow.com/2014/01/20/kitkat-broke-t-mobile-tethering
Seems tho theres a new or they replaced the same file in the v4.4.3 ota?
Im holding off on doing the v4.4.3 update due to the fact this is my only internet...cant screw up my device and then not be able to fix it!
Can someone confirm this still works on v4.4.3?
Thanks
Okay, I solved mine. I had flashed franco kernel without checking which version of Android it was supporting, must've been 4.4.2. I flashed the stock kernel again found at - http://bit.ly/SCFUfJ
torcellite said:
I can't confirm the TWRP backup, however it didn't work ever since I installed the 4.4.3 factory image with wipe.
Click to expand...
Click to collapse
r4pp3l said:
You're probably right. I today installed the fresh 4.4.3 factory image (wiping enabled). I then installed twrp. Then tried to tether on the fresh system and it worked.
After that I used twrp to do a backup, which I immediately restored. Tethering then was broken again.
Can someone else confirm this?
Click to expand...
Click to collapse
Tried again myself. Could no longer reproduce twrp breaking it.
I was getting the WiFi Hotspot error as well after updating to 4.4.3 from 4.4.2, when it was working perfectly fine on 4.4.2 before the update. I was running stock/rooted 4.4.2, with stock kernel, and a few Xposed Mods like Gravity Box, using Philz Recovery as my custom recovery. To update, I fastboot flashed the bootloader, radio, system and boot images from the 4.4.3 factory image (and wiping cache and dalvik). I thought I would get somewhat of a clean start by doing this. Afterwards, I was getting the Hotspot error, and it would disable my WiFi until I rebooted, which was very annoying. After trying to figure it out to no avail, I decided to just back up my stuff and fully flash the 4.4.3 factory image to REALLY get a clean slate. After restoring all my data, and applying the fix to the database file using the SQLite Editor app like I did on 4.4.2, I can confirm that it is working perfectly again. Not sure what happened, or what caused the error in the first place.
works perfectly for me
I flashed all the factory images to get 4.4.3 into a clean state. I did the following:
*Executed the following command since I don't have root: adb shell content insert --uri content://settings/global --bind name:s:tether_dun_required --bind value:i:0 in the platform-tools SDK directory
* Changed the APN settings to use IPv4
* Disabled IPv6 from Windows, only keeping IPv4
Rebooted phone, works perfectly. Used over 200GB since 4.4.3 and no issues.

Wifi unable to reconnect when coming back in range

I have this rather annoying problem with my OPO: When I'm on WiFi and go out of range and get within range of another WiFi (eg leaving from home in the morning and getting on the train where there's also WiFi) my OPO will not connect.
I've tried switching WiFi off and back on, tried forgetting network and connecting again but the network just displays as "Saved". Only thing that works is a reboot. Funny thing is that it actually detects open WiFi's and displays the question mark in the notification bar.
I've read that themes can cause WiFi problems so I haven't changed that. I'm using the Apex launcher with no visual changes.
I've rooted my phone but left the bootloader locked.
Any advice?
I'm rooted with the TWRP custom recovery installed. I had the same thing happen to me. If you toggle airplane mode on/off, it will reconnect. But, as for a solution, my fix was to restore a previous TWRP backup of my phone. I also had heard that the problem could be coming from a theme. What themes have you used? I bought the Flux theme and have been using its style and fonts. I was running the stock CM11s when this happend just a few days after getting my OPO. I would try a factory reset first. If that does not work, there is a thread in the OPO forums about flashing a factory image and getting back to 100% stock.
I have switched to the CM11 nightlies as of a couple of days ago. I will probably refrain from messing around with the theme packs for now.
kevinga said:
If you toggle airplane mode on/off, it will reconnect...
Click to expand...
Click to collapse
Works for me too
kevinga said:
What themes have you used?
Click to expand...
Click to collapse
None as I've read reports about themes causing WiFi problems.
kevinga said:
I would try a factory reset first.
Click to expand...
Click to collapse
Will probably unlock the bootloader. Then a factory reset should be taken care of I guess...
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
GoTexan20 said:
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
Click to expand...
Click to collapse
Have you taken the OTA update yet?
kevinga said:
Have you taken the OTA update yet?
Click to expand...
Click to collapse
I'm now on KTU84P and the problem is still there
Yesterday I failed to flash MAHDI and ended up clearing everything from my phone. I had to follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
to get back to pre-KTU84P (can't remember the build number).
So I guess it's safe to say that my phone has had all sorts of memory cleared. And the problem is still there...
kroogar said:
I'm now on KTU84P and the problem is still there
Yesterday I failed to flash MAHDI and ended up clearing everything from my phone. I had to follow this guide:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
to get back to pre-KTU84P (can't remember the build number).
So I guess it's safe to say that my phone has had all sorts of memory cleared. And the problem is still there...
Click to expand...
Click to collapse
I really hate to hear that you are still having the wifi issue. One would think that if you flashed all partitions with a factory image that it would solve the problem. You might want to have a look at this thread. This guy was unsuccessful in fixing his efs and bluetooth problems until he flashed Color OS and then went back to CM. Have a read: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Keep us posted.
kevinga said:
Keep us posted.
Click to expand...
Click to collapse
Will have a look at the ColorOS thread. But I think I'll give Mahdi another go first to see what that brings me.
Thanks for the link.
Flashed Mahdir ROM yesterday and though the rom works just fine my WiFi reconnect issue has not been resolved
I find flashing yet another rom (ColorOS) sounds a bit drastic. Really no way of debugging what's wrong?
GoTexan20 said:
Anyone have a solution to this? My OPO is having this problem too and it is rather annoying...
Click to expand...
Click to collapse
Have you been able to fix your wifi problem?
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
kroogar said:
Flashed Mahdir ROM yesterday and though the rom works just fine my WiFi reconnect issue has not been resolved
I find flashing yet another rom (ColorOS) sounds a bit drastic. Really no way of debugging what's wrong?
Click to expand...
Click to collapse
Although is sounds drastic I think it would be worth trying.
kevinga said:
Have you been able to fix your wifi problem?
No. I'm waiting for the update to hit my phone and install it to see if that solves it. In the meantime though, I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
GoTexan20 said:
kevinga said:
Have you been able to fix your wifi problem?
No. I'm waiting for the update to hit my phone and install it to see if that solves it. In the meantime though, I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
Thanks for sharing. I think there are two things that can produce a major restore/fix to a phone - a nandroid restore and a major rom update. I hope it fixes yours. The nandroid restore is what saved mine.
Click to expand...
Click to collapse
kevinga said:
Although is sounds drastic I think it would be worth trying.
Click to expand...
Click to collapse
Been there. Done that. Read the book. Got the t-shirt.
Flashed ColorOS.
Factory reset.
Booted and got through into ColorOS (skipped account setup).
Booted into recovery.
Factory reset.
Restore backup of CM11S.
No dice :'-(
What are my options now?
A couple of days ago I completely wiped my OPO - radio, modem, everything and flashed a new stock image. Nothing has helped.
I really find it hard to believe this to be a hardware issue.
GoTexan20 said:
kevinga said:
I installed an app called Smart WiFi Locker that seems to keep the issue solved (for now)
Click to expand...
Click to collapse
Could it be Smart WiFi Toggler?
Click to expand...
Click to collapse
kroogar said:
Been there. Done that. Read the book. Got the t-shirt.
Flashed ColorOS.
Factory reset.
Booted and got through into ColorOS (skipped account setup).
Booted into recovery.
Factory reset.
Restore backup of CM11S.
No dice :'-(
What are my options now?
A couple of days ago I completely wiped my OPO - radio, modem, everything and flashed a new stock image. Nothing has helped.
I really find it hard to believe this to be a hardware issue.
Click to expand...
Click to collapse
Just for clarification - after flashing Color OS, did you turn on wifi and use it to see if the problem was still there while in Color OS?
If your WiFi 2.4 or 5GHZ?
Sent from my A0001 using Tapatalk
kevinga said:
Just for clarification - after flashing Color OS, did you turn on wifi and use it to see if the problem was still there while in Color OS?
Click to expand...
Click to collapse
Eh... nopes - should I have...?
fr4c said:
If your WiFi 2.4 or 5GHZ?
Click to expand...
Click to collapse
My phone is set to auto but I have tried setting it to 2.4 and 5 GHz respectively. Nothing works.
kroogar said:
Eh... nopes - should I have...?
Click to expand...
Click to collapse
Yes. I would recommend you consider doing that. If it works then I would flash a fresh Cm11s rom, not a nandroid backup. Flash the Color OS and do a full check of the Wifi.
Sent from my A0001 using XDA Free mobile app
kroogar said:
My phone is set to auto but I have tried setting it to 2.4 and 5 GHz respectively. Nothing works.
Click to expand...
Click to collapse
I was having the same issue, but here's what I did and it seems to have resolved my issue.
1) Updated firmware on my ASUS AC68 router
2) Boot into recovery mode (volume down+power), wipe cache and media, then factory wipe
3) When setting up phone, did not apply CM theme on the options after logging into CM account.
It seems like WiFi might drop when you get to homescreen, just reboot phone and Wifi should reconnect. Make sure to go into your WiFi settings and remove any networks that was saved, and re-add.
Still not ideal (since it seems like themes might be killing WiFi for some users), so hopefully a new OTA update will solve this problem.

[Q] Lollipop- Bluetooth not working

Just flashed lollipop and everything works perfect except for Bluetooth. Phone simply says there are no other Bluetooth devices in range, and those devices can't see the nexus. I tried rebooting, factory reset, re-flashing stock lollipop using flash-all batch and even Wug toolkit just to cover all my options but still no work around. Anyone else experience this problem or can think of a way to fix it? Anything would help.
Wipe Cache
TheRoice said:
Just flashed lollipop and everything works perfect except for Bluetooth. Phone simply says there are no other Bluetooth devices in range, and those devices can't see the nexus. I tried rebooting, factory reset, re-flashing stock lollipop using flash-all batch and even Wug toolkit just to cover all my options but still no work around. Anyone else experience this problem or can think of a way to fix it? Anything would help.
Click to expand...
Click to collapse
Hi, one of my friend faced similar issue and wiping the cache from recovery helped solve the issue.
Try wiping cache and reboot.
pppp6071 said:
Hi, one of my friend faced similar issue and wiping the cache from recovery helped solve the issue.
Try wiping cache and reboot.
Click to expand...
Click to collapse
Just tried the wipe and reboot but the issue is still persistent. I'm still looking around for a solution but nothing has come up yet. Thanks for the input though!
lollipop im nexus5 bluetooth unstable
I just downloaded the lollipop today on my NX5 and i have a bluetooth SENA smh10 for my helmet and it was working very fine before the update, now its unstable, iv to start the music app first on phone while connecting the bluetooth inorder to be able to control it via the bluetooth device, also for calls, i recieved a call and i opened but no sound was there, i tried to call, same happened, so i had to disconnect the device, make the call and then i connected again..after a while it worked and i made a call... Theres some bug in the bluetooth i guess as my smh was working fine before. Also iv a problem in some wedges not responding like the data on off one. Oh yes..and battery empties SO Fast
TheRoice said:
Just tried the wipe and reboot but the issue is still persistent. I'm still looking around for a solution but nothing has come up yet. Thanks for the input though!
Click to expand...
Click to collapse
So I solved the issue. Re-flashed 5.0 to the device, rebooted, and wiped cache. It still didn't pick up bluetooth as of last night but it worked this morning. Also, for any android wear users (or at least moto 360) the phone wouldn't pick up the watch until I did factory reset on the watch and opened android wear on the phone itself in order to accept terms and conditions.
@TheRoice
thanks, has worked for me :good:

[Android 5.1] no service

My phone has suddenly stopped having any service whatsoever, I have tried everything, factory reset, format data, but have still been unable to get anything. I tried playing around with the radio settings and the APN but that hasn't worked either. If anyone has some ideas, they would be welcome.
Did you try putting the sim card into another phone?
JoJostar said:
My phone has suddenly stopped having any service whatsoever, I have tried everything, factory reset, format data, but have still been unable to get anything. I tried playing around with the radio settings and the APN but that hasn't worked either. If anyone has some ideas, they would be welcome.
Click to expand...
Click to collapse
Try to flash Android 5.01 radio. My radio/service was very bad in 5.1.
JoJostar said:
My phone has suddenly stopped having any service whatsoever, I have tried everything, factory reset, format data, but have still been unable to get anything. I tried playing around with the radio settings and the APN but that hasn't worked either. If anyone has some ideas, they would be welcome.
Click to expand...
Click to collapse
Pay the bill
Does the SIM status screen show your phone number and IMEI? I had a Galaxy Nexus once that quit working, and those were blank (or maybe it said unknown) in the status screen. I figure possibly the EFS partition developed a fault or got corrupted.
I flashed the 5.0.1 radio and was able to get service again and can now text but I'm still unable to call anyone.Whenever i try to dial the number it simply goes silent, loses service and ends the call. I am also still unable to receive calls as well,all calls people attempt seem to cause me to lose service and only get a voice mail afterwards.
I haven't checked the sim status screen yet and I am unsure as to how.
JoJostar said:
I haven't checked the sim status screen yet and I am unsure as to how.
Click to expand...
Click to collapse
Settings/About phone/Status/SIM status
I can see the IMEI and my phone number but the mobile network state fluctuates from connected to disconnected.
JoJostar said:
I can see the IMEI and my phone number but the mobile network state fluctuates from connected to disconnected.
Click to expand...
Click to collapse
Maybe try pulling the SIM and re-inserting it? Couldn't hurt.
I have done so with no effect afterwards to be seen.
JoJostar said:
I have done so with no effect afterwards to be seen.
Click to expand...
Click to collapse
If it was me, I'd try flashing the radio from Factory 5.0.1 (LRX22C)
It is baseband M8974A-2.0.50.2.22
Extract the radio from the .tgz
Here
You can always flash back if their is no improvement
Thanks for the suggestion but I have already done so and I have observed no improvement. am beginning t suspect that it may be an issue with the EFS but I'm not sure what steps to take to verify this.
JoJostar said:
Thanks for the suggestion but I have already done so and I have observed no improvement. am beginning t suspect that it may be an issue with the EFS but I'm not sure what steps to take to verify this.
Click to expand...
Click to collapse
After flashing 5.01 radio, did you try to wipe cache and dalvik cache? Maybe the phone process still has bad cache (if possible). Just a try! I hope it works. Otherwise there is some big problem
Thanks for the advice. I am considering filing an RMA with google although I'm unsure if I'll be covered since I live in Canada
JoJostar said:
Thanks for the suggestion but I have already done so and I have observed no improvement. am beginning t suspect that it may be an issue with the EFS but I'm not sure what steps to take to verify this.
Click to expand...
Click to collapse
If you suspect EFS corruption, try restoring any TWRP backup you made prior to the problem.
The EFS partition will be present in the backup, unless you unchecked if you checked that partition in TWRP Backup.
joegestes said:
If you suspect EFS corruption, try restoring any TWRP backup you made prior to the problem.
The EFS partition will be present in the backup, unless you unchecked that partition in TWRP Backup.
Click to expand...
Click to collapse
Efs is not backed up by default. You have to choose it.
Sent from my Nexus 9 using XDA Free mobile app
I have a similar issue. After I updated to 5.1 my mobile data doesn't work. I tried everything listed before in this thread with no result. I don't know what is happening. The first one I updated using 5.1 factory image. Reverted to 5.0 Factory image and it worked again. So, I update by OTA to 5.01 and then to 5.1, same results. This drives me crazy! I want 5.1 on my Nexus
BTW I have D821 model. Any suggestion?
jd1639 said:
Efs is not backed up by default. You have to choose it.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Your right.
Thanks for correcting me:good:
There is another topic on this matter (i.e. common problem): http://forum.xda-developers.com/google-nexus-5/help/sim-card-recognized-upgrade-to-nexus-5-t3054267
For me it helped, ejecting and reinserting the SIM card. But I had also flashed other ROMS and cleaned the SMS/call/contacts database. So not sure why it worked.
I also notice that my System UI frequently stops. Does anyone have a stock System UI for me? Many thanks!
I am having similar issue and SIM status shows Radio off, how do I turn on?
Thanks.

Recovered from boot loop but constant crashes with older ROM

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.

Categories

Resources