Related
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Devilicus said:
I was hoping to try out one of the 4.2 builds tonight, but every time I try to flash one through TWRP it just says "Failed"; I've tried CM10.1 and Eclipse ROM and they both had the same result. Also tried redownloading ROMs and re-copying them to my SD card, still no change. Can anyone tell me what I'm doing wrong here? I've never had a problem flashing any ROM before.
Click to expand...
Click to collapse
What version of TWRP are you running?
If you haven't done it lately, I would suggest updating your twrp to the latest and trying again.
I'm running the newest TWRP (I think), version 2.4.1.0
Devilicus said:
I'm running the newest TWRP (I think), version 2.4.1.0
Click to expand...
Click to collapse
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Relentless D said:
Weird. I am on that same version and have been flashing 4.2 roms for the last few weeks without any issues.
A few things I would try:
-Double check the md5 of the rom you are flashing
-Make sure it is a d2vzw rom
-Wipe caches, delete user data and wipe system
-Put the rom on the internal sdcard before flashing.
Other than that, I got nothing
Click to expand...
Click to collapse
Damn, yeah I can't figure it out; all the ones I've tried were Verizon ones, made sure to wipe everything as usual, tried putting it on the internal SD card and the external, won't work on either one. Very frustrating. But thanks for the help anyway
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Try carbon ROM.
First to work for me.
Sent from my SCH-I535 using xda app-developers app
Devilicus said:
Ok, I think I figured out the problem (won't be sure until I try it), but I think what happened is I edited my build.prop to the Sprint GS3 to get Google Wallet to work, forgot to change it back, and updated TWRP (which installed the Sprint version, not Verizon), and that's why the flashes are failing. So if any other people are having the same problem, that might be why. Yes I'm an idiot lol. Hopefully this fixes it
Click to expand...
Click to collapse
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
JohnAreBee said:
What baseband [modem] do you have installed? ...and some more info if build prop wasn't the issue. Would also be interested if, "but I think what happened is I edited my build.prop", was the issue and you fixed it. Let us know. Goodluck
Click to expand...
Click to collapse
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Devilicus said:
Yeah it turns out that was the problem. I edited my build.prop to match the Sprint GS3, so I could download Google Wallet from the Play Store and use it. I just never bothered to change the build.prop back. And when I updated TWRP through GooManager, it assumed I had a Sprint GS3 and installed the wrong recovery. When I flashed the correct Verizon version of TWRP everything worked fine. Thanks for the suggestions everyone
Click to expand...
Click to collapse
Good call. Might be worth mentioning over in the wallet thread. It could save someone the headache you just experienced. Congrats on getting it working.
Sent from my SCH-I535 using Tapatalk 2
About 30 minutes ago my phone was working fine, the last thing I remember doing was sending a text. A few minutes later I look down at my phone and notice it is in recovery. At this point I'm confused wondering how it got there, but figure it's whatever and reboot into system. It reboots back into recovery and at this point I'm kinda freaking out. I do a backup, wipe, and restore from a backup ~2 weeks ago. Again, rebooting just causes my phone to go into recovery.
Earlier today there was a notification on my phone about an update but I just ignored it as I didn't have time to deal with it. I assume that it automatically was applied and that is what caused this problem.
edit: If you have this problem, try this: http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
nest75068 said:
Same thing just happened to me.
I turned off OTA from earlier today and also removed the notification using AppOps and now I can't boot to anything but TWRP
Click to expand...
Click to collapse
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
elguy said:
I'm about to try this, http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508, if it works I'll let you know.
Click to expand...
Click to collapse
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
nest75068 said:
Was coming here to say this worked - I was already doing this.
I'm back up and running again.
Not sure wtf caused the issue - I didn't take the OTA and have been fine on the phone all day until just now
Click to expand...
Click to collapse
Yeah, worked me too. Not sure what happened either, phone says its still on KVT49L.D85010d.
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I was the same - the zip file fixed my issue - didn't have to start over
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
esoteric1311 said:
Gotta love XDA.. i was getting ready for bed.. saw a bright light, it was my phone. Same thing as mentioned. only rooted and bumped. Have been denying the OTA. Even did the hidden menu trick, but still got notifications for some reason. Flashing the ZIP showed success; trying to restore my back up now.
Click to expand...
Click to collapse
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
nest75068 said:
Once you flash the zip you shouldn't need to restore. I just clicked on reboot system and was back in
Click to expand...
Click to collapse
Well i had to restore the newest back up, because I restored an old back up to see of it would reboot correctly. All works fine now. Still very weird.
gpgon said:
Rooted, bumed TWRP. All of the above applies to me. Recovered, but back to stock. Annoyed that I have to start all over
Click to expand...
Click to collapse
I mean I still have Root and TWRP, I might have factory reset in my panic last night before finding the fix above. Probably the cause of losing all my apps and data
ATTT Forced UPDATE
It would appear after cruising the forums this morning that ATT forced an update to all users last night. It happened to me and many others like yourself. even people that had turned off updates in the hidden menu. It is total crap and not to happy about it obviously. good thing it sent me into a boot loop, and @autoprime zip fixed me up, even though i was back up on stock rooted, I took this opportunity to move over to the PoweruserV1 international rom to attempt to keep this from happening again. Luckily our DEVS are getting development moving and soon this will be a thing of the past....
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
KennyG123 said:
I froze Software Update with TB and did not get auto updated last night and have not gotten any new nags today. I did try to update yesterday and got the stuck in TWRP thing and flashed the fix to get back working.
Click to expand...
Click to collapse
whats the name of the apk to freeze? Thanks
Just adding to this, that it was 'forced' onto me as well, and also sent me to soft brick loop (TWRP), so I'm having to use the get out of jail thread. THANKS LG!! YOU GUYS ROCK!!! (#[email protected]%&*!!!!) This is the LAST time I trust another corporate BS liar's announcement that they care about the 'community' and are going to try and be nice 'from here on out'. Moving forward, it will be NEXUS and nothing else for me.
esoteric1311 said:
whats the name of the apk to freeze? Thanks
Click to expand...
Click to collapse
It is called Software Update in TB. I only have it frozen since last night so hopefully this does the trick...it also removes update option from settings FYI.
Anyone else have this happen again last night? Phone was fine at 5am, woke up at 8:30 to recovery. Flashed the same zip and now it's all fine again.
Freeze software update with titanium backup so your phone doesn't try to install the update agian
wow att and their updates f*** with everything, currently having a locked s4 with old firm of mf3. i plan on upgrading my device but on the fence with all this lock down bs. switching to tmobile seems like a decent option...... so confused and undecided
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.
Dear All,
I don't know if I have posted it at the right place if I have not please guide me.
I tried my best to find a solution but couldn't that's why I am posting this.
So here I begin,
I am using OnePlus One from last 2 years and it is still working fine.
I have spent most of the time on Sultan's Rom which ran without any issues.
Recently I flashed [ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0] Rom and it worked well too.
But all of a sudden I started experiencing LTE signal drop.
I always do Nandroid backups so I restored to Sultan Rom but the problem was still there.
I have tried flashing modems with no luck.
Now I have started experiencing intermittent 3G signal too.
I have even tried restoring old KK backups but that doesn't resolve the problem.
This is so frustrating, Please help.
Let me know if more information is needed.
iamvashisht said:
Dear All,
I don't know if I have posted it at the right place if I have not please guide me.
I tried my best to find a solution but couldn't that's why I am posting this.
So here I begin,
I am using OnePlus One from last 2 years and it is still working fine.
I have spent most of the time on Sultan's Rom which ran without any issues.
Recently I flashed [ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0] Rom and it worked well too.
But all of a sudden I started experiencing LTE signal drop.
I always do Nandroid backups so I restored to Sultan Rom but the problem was still there.
I have tried flashing modems with no luck.
Now I have started experiencing intermittent 3G signal too.
I have even tried restoring old KK backups but that doesn't resolve the problem.
This is so frustrating, Please help.
Let me know if more information is needed.
Click to expand...
Click to collapse
I'd do a complete clean restore of last official stock. If the issue still persists, it must be a hardware issue or an issue with your carrier.
If your device is wiped clean and stock software restored, there's no way it can be a software issue.
Good luck!
iamvashisht said:
Dear All,
I don't know if I have posted it at the right place if I have not please guide me.
I tried my best to find a solution but couldn't that's why I am posting this.
So here I begin,
I am using OnePlus One from last 2 years and it is still working fine.
I have spent most of the time on Sultan's Rom which ran without any issues.
Recently I flashed [ROM][OFFICIAL][7.1.1_r9][BACON][OPTIMIZED]RESURRECTION REMIX [5.8.0] Rom and it worked well too.
But all of a sudden I started experiencing LTE signal drop.
I always do Nandroid backups so I restored to Sultan Rom but the problem was still there.
I have tried flashing modems with no luck.
Now I have started experiencing intermittent 3G signal too.
I have even tried restoring old KK backups but that doesn't resolve the problem.
This is so frustrating, Please help.
Let me know if more information is needed.
Click to expand...
Click to collapse
if clean flash through fastboot don't work out,try changing network antenna.
I don't think it's a carrier issue because it was perfect before.
The problem in network antenna must've been due to sudden drops or heavy impact.
Mr.Ak said:
if clean flash through fastboot don't work out,try changing network antenna.
I don't think it's a carrier issue because it was perfect before.
The problem in network antenna must've been due to sudden drops or heavy impact.
Click to expand...
Click to collapse
Hi, thank you for replying.. Flashing stock ROM from fastboot is different than flashing it from twrp recovery?
Please let me know if it is.
I will certainly give it a try then.
Darth said:
I'd do a complete clean restore of last official stock. If the issue still persists, it must be a hardware issue or an issue with your carrier.
If your device is wiped clean and stock software restored, there's no way it can be a software issue.
Good luck!
Click to expand...
Click to collapse
Hi, thanks for replying... I will do a clean install, does it need to be done via fastboot or just recovery?
And do I need to wipe internal storage too?
Since fresh installs via recovery couldn't resolve the problem..
iamvashisht said:
Hi, thanks for replying... I will do a clean install, does it need to be done via fastboot or just recovery?
And do I need to wipe internal storage too?
Since fresh installs via recovery couldn't resolve the problem..
Click to expand...
Click to collapse
Flash stock Cos13 through fastboot,it will wipe your internal storage so take a backup.
Refer to guide "Bring your device back to stock Cos by Eddy".
Mr.Ak said:
Flash stock Cos13 through fastboot,it will wipe your internal storage so take a backup.
Refer to guide "Bring your device back to stock Cos by Eddy".
Click to expand...
Click to collapse
Thanks man... Gonna give it a try...
iamvashisht said:
Thanks man... Gonna give it a try...
Click to expand...
Click to collapse
I did a clean install via fastboot, that unfortunately didn't resolve the problem.
iamvashisht said:
I did a clean install via fastboot, that unfortunately didn't resolve the problem.
Click to expand...
Click to collapse
Do you have 'unknown' baseband?? I was stuck on 3g due to that..
Issue Resolved
I dont know what happened, I had flashed stock cm13.1 via fastboot.
I checked and that didnt resolve the problem, so I had accepted the way things were and started using my 3g.
All of a sudden the 4g signal came this morning and now I can use LTE well.
I dont know how long it will stay but seems like phone decided to bring back 4g.
iamvashisht said:
I dont know what happened, I had flashed stock cm13.1 via fastboot.
I checked and that didnt resolve the problem, so I had accepted the way things were and started using my 3g.
All of a sudden the 4g signal came this morning and now I can use LTE well.
I dont know how long it will stay but seems like phone decided to bring back 4g.
Click to expand...
Click to collapse
Bro, I am facing the exact same issue man. My LTE still doesn't work. I tried installing various modems. Still no use. I hope it does soon. :/
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
Im facing the excat same issue. Did everything and nothing worked. Somebody please help. :/
Bro try flashing stock cm13 via fastboot... That will wipe your internal storage but eventually bring back 4G
I am also facing network drop issue for last few weeks.at first i thought it may be rom's problem,because generally i try a new rom in every 2/3 weeks,but now i notice that ,i am facing the issue in all roms,i read all the comments in this threads and see that cm13.1 can solve my issue.but can i solve my issue within any nougat rom?
I too am having the issue. Occasionally my 3/4g data just cuts out but it is still enabled in settings. It seems to be when I come off of WiFi most of the time. I'm on CM13.1 by jgcaap.
I'm going to flash back to full stock and then reinstall TWRP, then the ROM. I have a few issues and I figured it was time for a fresh flash.
Sent from my A0001 using XDA-Developers Legacy app
iamvashisht said:
Bro try flashing stock cm13 via fastboot... That will wipe your internal storage but eventually bring back 4G
Click to expand...
Click to collapse
Are you talking about CyanogenMod 13?
I clean installed COS 13.1.2 via fast boot. It even removed TWRP and brought back Cyanogen recovery. The problem didn't resolve.
Can I install CyanogenMod 13 via fastboot now? or should I unlock bootloader, install TWRP and then install CyanogenMod 13 via fastboot? Please help. I'm a beginner.
In my opinion you should unlock bootloader and then reinstall via fastboot...
iamvashisht said:
In my opinion you should unlock bootloader and then reinstall via fastboot...
Click to expand...
Click to collapse
I'm right now on COS 13.1.2.
Lets say I install CM 13 via fastboot and my LTE works. Can I again revert back to COS 13.1.2 using fastboot without affecting LTE again?
Thanks for the help. I will try that this Sunday and Will tell you if it works.
Andy928 said:
I'm right now on COS 13.1.2.
Lets say I install CM 13 via fastboot and my LTE works. Can I again revert back to COS 13.1.2 using fastboot without affecting LTE again?
Thanks for the help. I will try that this Sunday and Will tell you if it works.
Click to expand...
Click to collapse
The latest official build is 13.1.2.
You can flash that via fastboot
iamvashisht said:
The latest official build is 13.1.2.
You can flash that via fastboot
Click to expand...
Click to collapse
Hi Brother. Thank you so much for your help.
My LTE is working now. I unlocked bootloader using fastboot. I installed CM 13 tugapower ROM using TWRP provided by Tugapower. Its all back to normal. I'm so glad. i'm not going to change a damn thing now. ha ha.
Lot of tries and finally its working. Can Push this baby for another year now.
---------- Post added at 07:02 AM ---------- Previous post was at 06:59 AM ----------
donk165 said:
I too am having the issue. Occasionally my 3/4g data just cuts out but it is still enabled in settings. It seems to be when I come off of WiFi most of the time. I'm on CM13.1 by jgcaap.
I'm going to flash back to full stock and then reinstall TWRP, then the ROM. I have a few issues and I figured it was time for a fresh flash.
Sent from my A0001 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Try Installing Tugapower TWRP and his CM13 ROM. My LTE is working and everything's back to normal!
Congrats man..happy for you...
And yeah we can push this phone for another year...
?
Good day everyone. So I recently started to experience weird freezes and crashes of most of the apps. Like facebook, instagram, some games. Not all of the apps do this. It all started about a month ago. I tryed using multiple diffrent ROM's. Although that ROM did work correctly for another month before these errors came up. Now I am using Global Elite rom: https://forum.xda-developers.com/galaxy-s6/development/sm-g920f-sm-g925f-griffin-t3435461
I always do a clean flash. Rooted with magisk, even though I was using SuperSU for other roms. Any help will be aprecieted. I am suspecting hardware failure (anyway to test that?). Thanks in advance.
Bumping this thread. Things getting worse... Please anyone. I am desperate...
Why don't you revert to your initial ROM, the one that never caused any issues?
RossTeagan said:
Why don't you revert to your initial ROM, the one that never caused any issues?
Click to expand...
Click to collapse
Problem is that every rom I've tried do same things. What is left to try is stock official firmware. But I will have to try it later as I am currently on the go.
Try to do a factory reset and see if the problem persists.