Q&A for [STOCK ROM][5.0] OA6 Android L Deodexed
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [STOCK ROM][5.0] OA6 Android L Deodexed. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Wifi
I flashed as directed, and it is running. The issue I have is wifi keeps disconnecting and reconnecting. I was running MOAR and it was great, but it would not roam, it was stuck on CDMA. Now this will not stay connected to wifi.
tedmales said:
I flashed as directed, and it is running. The issue I have is wifi keeps disconnecting and reconnecting. I was running MOAR and it was great, but it would not roam, it was stuck on CDMA. Now this will not stay connected to wifi.
Click to expand...
Click to collapse
Not sure. Did you also flash the wifi calling fix and toggles addon in Post #2?
Just wondering if that had anything to do with it.
You can try reflashing the full stock tar and see if its doing it there. Then try reflashing the deodexed rom without the wifi calling fix, test it again and then flash with wifi calling fix at the very end to see if that's what is giving you the problem.
---------- Post added at 01:36 PM ---------- Previous post was at 01:18 PM ----------
@tedmales
I've added a stock features.xml flashable to Post #2 of the home thread. Flash that first to see if it resolves any of your issues. If it doesn't, follow the other directions I posted. Not sure what else to try.
Cheers - TD
Is it possible to flash the 4.4.2 kernel and use towel root with Knox at 0x0 and flash back?
I was able to do this on 4.4.4
Sent from my SM-G900P using XDA Free mobile app
tdunham said:
Not sure. Did you also flash the wifi calling fix and toggles addon in Post #2?
Just wondering if that had anything to do with it.
You can try reflashing the full stock tar and see if its doing it there. Then try reflashing the deodexed rom without the wifi calling fix, test it again and then flash with wifi calling fix at the very end to see if that's what is giving you the problem.
---------- Post added at 01:36 PM ---------- Previous post was at 01:18 PM ----------
@tedmales
I've added a stock features.xml flashable to Post #2 of the home thread. Flash that first to see if it resolves any of your issues. If it doesn't, follow the other directions I posted. Not sure what else to try.
Cheers - TD
Click to expand...
Click to collapse
Thanks for the quick reply. In a fit of rage about 330 last night I wiped and flashed my way back to moar 2.2. Only issue there is I noticed the OA6 modem is still on it and I tried to phone and it works. I will leave as is for the day and try again tonight using your advice.
Thanks
Ted
tedmales said:
Thanks for the quick reply. In a fit of rage about 330 last night I wiped and flashed my way back to moar 2.2. Only issue there is I noticed the OA6 modem is still on it and I tried to phone and it works. I will leave as is for the day and try again tonight using your advice.
Thanks
Ted
Click to expand...
Click to collapse
Hey Ted, someone in the main thread with the same issue with wifi said he turned off Smart network switching or something in advanced wifi settings and that fixed it for him. Myself, I always uncheck all the boxes in there...
[STOCK ROM][5.0] OA6 Android L Deodexed is the best!
Loving this ROM. It has everything I need except for a wireless charging notification toggle. Would NKD New Stuff Rev. 1.3 run on OA6?
tdunham said:
Hey Ted, someone in the main thread with the same issue with wifi said he turned off Smart network switching or something in advanced wifi settings and that fixed it for him. Myself, I always uncheck all the boxes in there...
Click to expand...
Click to collapse
I had the issue with constantly losing Wifi connection when standing less than 10 feet from my router. I turned off Smart Network Switching and the problem went away. Battery life improved drastically as well since my phone was no longer trying to pull all its data from the network.
Debloat seems to remove Pro Audio functionallity
Hey tdunham!
I finally got a chance to try out your OA6 ROM, and I'm really enjoying it! I just wanted to follow up on the pro audio functionality I had posted about in the MOAR 5.0 thread, or what might be another cause.
So I followed all the instructions, wiped, odined stock and recovery, flashed the ROM, flashed the debloat package, booted up, everything worked fine. First thing I did was download the galaxy store so I could try the pro audio application amplitube and soundcamp, same issues I had in MOAR, force closes on Soundcamp, no audio input through the mic.
Just to make sure it wasn't firmware, I flashed back to stock, everything with the pro audio apps worked well. Then I wiped and reflashed your ROM without the debloat package, and low and behold, the pro audio functionality worked fine. So whatever it is that cripples it is in what gets removed from the bloat I'm guessing, something that wasn't removed in the International BOA3 based ROM either. I'm fine living with all of the sprint apps, just a few more boxes to un-tick and things to hide in the launcher, but just thought I'd mention it in case anyone else runs into these issues.
Thanks again for all the great work!
hugantic said:
Hey tdunham!
I finally got a chance to try out your OA6 ROM, and I'm really enjoying it! I just wanted to follow up on the pro audio functionality I had posted about in the MOAR 5.0 thread, or what might be another cause.
So I followed all the instructions, wiped, odined stock and recovery, flashed the ROM, flashed the debloat package, booted up, everything worked fine. First thing I did was download the galaxy store so I could try the pro audio application amplitube and soundcamp, same issues I had in MOAR, force closes on Soundcamp, no audio input through the mic.
Just to make sure it wasn't firmware, I flashed back to stock, everything with the pro audio apps worked well. Then I wiped and reflashed your ROM without the debloat package, and low and behold, the pro audio functionality worked fine. So whatever it is that cripples it is in what gets removed from the bloat I'm guessing, something that wasn't removed in the International BOA3 based ROM either. I'm fine living with all of the sprint apps, just a few more boxes to un-tick and things to hide in the launcher, but just thought I'd mention it in case anyone else runs into these issues.
Thanks again for all the great work!
Click to expand...
Click to collapse
Just wondering, did you install v1.1 of the deodexed rom?
And below is the list of what gets deleted in the debloat tool, see anything that sticks out?
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
My guess would be the Samsung Billing being removed as was stated by the other person after installing the Samsung App it still fc'd. Just a guess though
Sent from my SM-G900P using Tapatalk
no sprint yellow boot screen missing?
I had this issue awhile back on the first ROM that was released when the phone came out. The yellow boot screen is still included. along with pretty much every carriers custom boot animation. The problem is that csc file was rewritten to XAS, you want it to be SPR. This is the app I used to changed mine when it got changed. The downfall is that it wipes your phone and you have to start over, it could work with a backup but I usually just start from scratch anyway. Most of my data is cloud based so once I log into the apps I use nothing has changed. It also says it doesn't work with custom roms but it did work for me, on a dioxide custom rom. I cannot verify it works on 5.0 and I'm currently working on testing it if it can, unless you can get it completed yourself faster then I can.
https://play.google.com/store/apps/details?id=com.manniakk.cscselector&hl=en
---------- Post added at 06:39 PM ---------- Previous post was at 06:29 PM ----------
I currently cannot download this rom as androidfilehost is down so I will figure out a way to test on boa6 stock with cf-auto root in the mean time.
On stock 5.0 BOA6 with root via cf-autoroot, I was able to rewrite the CSC from SPR to XAS/BST and back to SPR. It does indeed wipe your device so make sure to back up before use, or be prepared to start from scratch clean install of rom
deoxed boot animation fix
Ok a separate post for what I did. I flashed the BOA6 deoxed with CWM, flashing debloated and stock boot animation right after and before first boot. I let the device boot (10-15) minutes then did a basic setup to install CSC changer from the play store. I changed from XAS to SPR and let the app complete its processes, this included a reboot to a special recovery. The phone then rebooted with the sprint boot animation and continued to first set up where I then set my phone up as I wanted. I do not think a recovery will work as the XAS CSC would be in a back up before using CSC changer. however the app does do its job as far as getting the sprint boot animation back.
Hope this helps
ADB Shell does not work
I recently installed this ROM and am having issues getting the shell to cooperate. Whenever i attempt to run any command in the shell I am given a response of "Aborted". Any ideas?
tdunham said:
Code:
delete_recursive("/system/app/Blurb");
delete_recursive("/system/app/Books");
delete_recursive("/system/app/Drive");
delete_recursive("/system/app/DriveLink");
delete_recursive("/system/app/DriveLinkRemote");
delete_recursive("/system/app/Flipboard");
delete_recursive("/system/app/GeoLookout");
delete_recursive("/system/app/Headlines");
delete_recursive("/system/app/Music2");
delete_recursive("/system/app/Newsstand");
delete_recursive("/system/app/PlayGames");
delete_recursive("/system/app/SamsungAppsWidget_Phone_Carrier");
delete_recursive("/system/app/SecKidsModeInstaller");
delete_recursive("/system/app/Videos");
delete_recursive("/system/priv-app/ConnectionManager");
delete_recursive("/system/priv-app/ID");
delete_recursive("/system/priv-app/SamsungApps_K");
delete_recursive("/system/priv-app/SamsungBilling");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/SNS");
delete_recursive("/system/priv-app/Zone");
Click to expand...
Click to collapse
Yeup, running version 1.1, which is really nice and smooth by the way.
Unfortunately nothing in there looks significant in terms of this functionality, so I have no idea what the professional audio system is associated with that keeps getting broken. Just to check though I made a nandroid backup after I set up the phone this time, then flashed the debloat (v1.2) tool...it was strange, it seemed like it worked for a minute, but then after not using it for a while the professional audio related apps started glitching again. Restarted, still glitched, restored to before I flashed the debloat package and it all worked again. It's been about a day or so and haven't had a problem since.
unable to install apps error 491 after installing this rom
I can't install anything since installing this rom.. All i get is an unable to install error 491.... Any ideas?
hugantic said:
Yeup, running version 1.1, which is really nice and smooth by the way.
Unfortunately nothing in there looks significant in terms of this functionality, so I have no idea what the professional audio system is associated with that keeps getting broken. Just to check though I made a nandroid backup after I set up the phone this time, then flashed the debloat (v1.2) tool...it was strange, it seemed like it worked for a minute, but then after not using it for a while the professional audio related apps started glitching again. Restarted, still glitched, restored to before I flashed the debloat package and it all worked again. It's been about a day or so and haven't had a problem since.
Click to expand...
Click to collapse
My guess would be the Samsung Billing being removed as you stated you only installed just the Samsung App. There is also a SamsungBilling App that gets removed also. If its a paid app its probably trying to check on something to verify its not a pirated app. Just a guess though [emoji780]
Sent from my SM-G900P using Tapatalk
Internal Storage Double COunted
I'm having a problem whereas I'm getting notices that I'm running out of space and I know that I'm not.
I'm seeing a "/storage/emulated/legacy " path and a "/storage/SD Card" path. Is it possible that both are being counted against my total space count?
Is it possible to fix this? I'm backed up so formatting it or some other way that may erase just the contents of the internal card isn't a problem.
Everything else seems to be working fine. I haven't seen any of the reported issues.
battery drain?
Is anybody experiencing a high amount of battery drain. I flashed fresh last night and used ktoonez updated kernel to fix the 491 play store error... i dropped 30% battery in 1.5 hours this morning..
F22loader said:
I'm having a problem whereas I'm getting notices that I'm running out of space and I know that I'm not.
I'm seeing a "/storage/emulated/legacy " path and a "/storage/SD Card" path. Is it possible that both are being counted against my total space count?
Is it possible to fix this? I'm backed up so formatting it or some other way that may erase just the contents of the internal card isn't a problem.
Everything else seems to be working fine. I haven't seen any of the reported issues.
Click to expand...
Click to collapse
Something may have gone wrong in the flash continuum. For me, I didn't OTA at all. I Odin-ed the tarball and everything is fine except for showing I am "Custom".
7.04 Gb still available....even after the flash of TDunham's Deodex.
---------- Post added at 01:17 AM ---------- Previous post was at 01:12 AM ----------
exodusprime1337 said:
Is anybody experiencing a high amount of battery drain. I flashed fresh last night and used ktoonez updated kernel to fix the 491 play store error... i dropped 30% battery in 1.5 hours this morning..
Click to expand...
Click to collapse
Unless heavy web surfing/app using, that's a little heavy. I'm not sure what your settings are, but I did find that the Ktoonservative setting doesn't do for Lollipop what it used to on KitKat. I am set to 2475 over 300, Conservative @ bfq, No overclocking and no undervolting. GPU turned up full blast. KThermal only and Thermald enabled.
I go about 18-20 hours. I CAN get more, but I never turn data/GPS off. We wanted Lollipop and we got it. Ya gotta pay to play. It drains juice.
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
elwood said:
My guess would be the Samsung Billing being removed as you stated you only installed just the Samsung App. There is also a SamsungBilling App that gets removed also. If its a paid app its probably trying to check on something to verify its not a pirated app. Just a guess though [emoji780]
Sent from my SM-G900P using Tapatalk
Click to expand...
Click to collapse
This is just ONE idea(and it may not work for everyone).
I had the old backup from TiBu. I restored it(app only) and it stuck. I can do everything in Samsung's app store.
Related
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Is this issue solved?
Is this issue solved?
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files on this page:
http://forum.xda-developers.com/showpost.php?p=30347369&postcount=5
Stock recovery and system: odin_gingerbread.ucla4_recovery_stock_system_stock _no_root.tar.md5
ClockworkRecovery 6.0.1.1 and No-Bloatware and Root: odin_gingerbread.ucla4_recovery_cwr_6011_system_no _bloat.tar.md5.gz
and my WiFi is not working. When I go to Wireless and Networks - Wi Fi Settings -
Says: Error next to the check mark to turn wifi on or off. :crying:
Everything else seems to work including sound.
Baseband: I847UCLH4
Gingerbread 2.3.6
Build Number: GINGERBREAD.UCLH4
Kernel version: 2.6.35.7
WiFi MAC address: Unavailable
Bluetooth address: works!!
Does anyone have any idea what could be the problem?
thanks you
Click to expand...
Click to collapse
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
broadways said:
You could flash back to stock firmware and try again. If the error persists then the files are probably not right for your phone.
Click to expand...
Click to collapse
The files the OP pulled are for his phone based on the baseband shown. It looks like it may be related to the OTA update that came through recently.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
---------- Post added at 08:40 AM ---------- Previous post was at 08:37 AM ----------
VoiceArtistUSA said:
I have a Samsung Rugby Smart ( AT&T ).
I used the last two files [edit] [and] my WiFi is not working
Baseband: I847UCLH4
Does anyone have any idea what could be the problem?
Click to expand...
Click to collapse
Did you install the OTA update that AT&T pushed recently before flashing the ODIN images?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
kemonine96 said:
Did you successfully apply the ota update that came through for the rugby?
Click to expand...
Click to collapse
VoiceArtistUSA said:
Yes, before any root or flash of course.
Click to expand...
Click to collapse
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
YEEEEE HAAAAWWWWW
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Can't imagine why not a "Full fix".
Thank You !!!!
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Also I'm getting ...
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
kemonine96 said:
That explains it, the OTA update includes a slightly changed kernel (based on what I saw in the diffs) that is likely causing your WiFi issue. Can you try applying motorhead's kernel from here and see if WiFi starts working? I know it is not a full fix, but it should get your wifi back to working while motorhead and I coordinate on getting a stock kernel that can be flashed from CWR put together.
Click to expand...
Click to collapse
VoiceArtistUSA said:
I got some WIFI !!!!
Camera, BT and sound, seems like everything works.
Click to expand...
Click to collapse
I'm glad to hear it's working again for you.
VoiceArtistUSA said:
Can't imagine why not a "Full fix".
Click to expand...
Click to collapse
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
VoiceArtistUSA said:
Says there is an OTA update, after it downloads, I get tossed into CWM bootloader 6.1.1 and the update doesn't get applied.
All I do is choose 'reboot system'.
Click to expand...
Click to collapse
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
VoiceArtistUSA said:
"[ AT&T Address Book] Checking Subscriber Information"
when I touch contacts.
I am not an AT&T customer, I use STLK the BYOP program.
Click to expand...
Click to collapse
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
VoiceArtistUSA said:
We really need a custom ROM for this great device, no bloat, no AT&T updates, no AT&T bloatwares, No CIQ, No City ID.
I would be HAPPY to PAY for a custom ROM and have it delivered two weeks from last Thursday. Jellybean?
Click to expand...
Click to collapse
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
VoiceArtistUSA said:
Someone like me who chooses a rugged phone may not be into all the bells and whistles, so a basic stripped down
ROM would be great.
Click to expand...
Click to collapse
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
VoiceArtistUSA said:
and yes, I am getting lag coming out of deep sleep. may have to hit power button twice to unlock.
Can't wait to try Motorheads soon to be released power kernel...
Click to expand...
Click to collapse
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
kemonine96 said:
I'm glad to hear it's working again for you.
Because I assumed you wanted to roll back all the way to stock . If I knew you were good with non-stock kernel I'd have said full fix .
There is an updater app you can freeze to prevent this from running. Nicedream06 and motorhead1991 have it disabled w/o ill effects.
No ideas on this one. I'm an ATT subscriber and I don't remember that firing off, but I bought the phone the month it was released...
Working on it with a few others "right now". We have stable boot in ICS (CM9 and AOSP builds) but the modem is dead. No cell service at all. There are other problems but we are focused on getting the antenna up and going.
Check the super thread. I have an ODIN image that is pretty stripped down and it includes the 6.x version of CWR. I left a few things in "just in case" but they can easily be stripped out using any of the various root tools for removing system apps.
If you can post over in motorhead's thread that you are experiencing the problem it will help out to know that it is common. He mentioned he was looking into it. I'm sure something will be ready soonish.
Click to expand...
Click to collapse
The lag is a noted issue, along with the WiFi shutting off randomly and intermittently. I'm researching these issues as much as I can to find a fix, but I can only do so much so fast .
I was going to start a new thread but then I found this. I too had the issue with I the wifi turning off and the screen lag. After reflashing the no bloat Odin image and the 1.1 kernel my wifi turns on, but does not find any networks. It just searches then shuts off? Any ideas? I wonder if the stock kernel being worked on would fix this or if there is something else wrong. Any help would be greatly appreciated.
Sent from my SAMSUNG-SGH-I847 using xda premium
I sent the rugby smart to SAM to have it completely reloaded. when it comes back, i will try to make a back up much like i make an image of a hard drive...if that's possible.
For my PC, I have an image of this existing hard drive. If i pull it out and put in a BLANK hard drive, I can write the image to the new disk with all my apps installed...I use that feature often with my pc's and others...for mine, I frequently make a new updated image and delete the oldest one.
Once I change the bootloader, is it possible to get it back if I backed up with with Kies?
You guys are in luck. Kernel1.2 should be out shortly with the lag and wifi fixed . I'm waiting to hear back from another tester, but so far ut's proven stable. I've only had one error pop up, and that was after running pretty hard.
Motorhead1991, Is this for the Samsung Rugby Smart?
How much of, if any, overclocking??
Can you also tweak a non-overclocked version without "City ID" app, "Carrier IQ" app and possibly no AT&T bloatware??
You rock for everything thus far
No overclocking just yet, but I'm giving it hell. On the bright side, Kemonine and myself are currently treading in uncharted territory for this device (see if anyone gets my reference)
And to answer your question, yes it'll be for the Rugby.
iam not sure
thats a good question
Motorhead1991 said:
And to answer your question, yes it'll be for
the Rugby.
Click to expand...
Click to collapse
After a day of use, it seems very stable and even more efficient.
That is great news! Can't wait to test
Sent from my SAMSUNG-SGH-I847 using xda premium
alan2424m said:
thats a good question
Click to expand...
Click to collapse
Yeah, it actually did hurt to ask that one.
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
ESPFreak said:
So after flashing the following new odin images
•Stock boot / kernel:
•Stock Boot + Stock Recovery + Stock System:
•Stock Boot + CWR 6.0.1.2 + No Bloat System:
My WiFi still turns on, searches for a while, finds nothing and turns back off! I have no idea what to do next. Any ideas?
Click to expand...
Click to collapse
When you flashed via ODIN did it show it was flashing the boot area? In the status window it should tell you which images are being flashed to the device. Can you re-try the stock boot/kernel ODIN image and confirm it did flash the boot image?
That is the only thing that booted. As soon as I selected the image I got a "MD5 checksum failed" prompt. The "start" button changed to the same message but it let me click it and it loads the boot.img. Does that help at all?
Sent from my SAMSUNG-SGH-I847 using xda premium
Here's the odin tar for the new jellybean release
http://hotfile.com/dl/204016374/8aa...m-SGH-T699-TMB-T699UVBMC5-1363439562.zip.html
I should have a tethering fix and a flashable modem (for people on cyanogenmod) out by tomorrow
nice... anybody unlocked with the trick that wants to be the guinea pig and flash this and report if it locks it back or not?
Braccoz said:
nice... anybody unlocked with the trick that wants to be the guinea pig and flash this and report if it locks it back or not?
Click to expand...
Click to collapse
I can confirm it works. I unlocked my phone under the previous stock ROM for use on Wind, and it remained unlocked through the upgrade. I didn't need to unlock it again.
Jax184 said:
I can confirm it works. I unlocked my phone under the previous stock ROM for use on Wind, and it remained unlocked through the upgrade. I didn't need to unlock it again.
Click to expand...
Click to collapse
awesome, i'll wait for the tethering fix then
I have the stock ROM, and have just applied the update to my phone. Anyone know what the flashing red box around the screen is for?
I've been using the new JB ROM for a few hours now and have found a quirk or two.
When manually adjusting the brightness, sometimes the screen takes on a blue tint. Like, things that should be a dark blue become much brighter. This goes away if I tweak the brightness back and forth a few times.
I rooted the ROM using the CWM+flashable root file from previous ROMs. It worked, though last night I kept getting "radio is requesting superuser access" until I restarted the phone. I don't know what that was about. Hopefully it doesn't happen again.
The compass is STILL misconfigured. Every time you boot the phone, it needs to be recalibrated before it has any idea which way is up or north.
burbs said:
I have the stock ROM, and have just applied the update to my phone. Anyone know what the flashing red box around the screen is for?
Click to expand...
Click to collapse
No idea what you mean. Got a picture?
---------- Post added at 12:48 PM ---------- Previous post was at 12:12 PM ----------
Okay, so we may have something a little deeper here. Today I'm seeing the "radio is requesting Superuser permissions" dialog again and again. I'm unsure what this means, but as a wild-ass guess, it may be the ROM checking to see if the phone has been rooted. This could be bad for people out there who still have their warranties.
I can't seem to get a screen shot, but it's like what you'd expect the hard drive LED to do when accessing data. I've looked up different "solutions" through Google, and it seems to be a developer's mode attribute, but I turned it off. One person says to uncheck the strict mode setting, which hasn't worked.
Well, whatever it was, it's done doing its thing now. As the day went on, the red flashing border appeared with less frequency. Throughout this morning I didn't experience it at all. Maybe it was some type of optimization thing going on?
Tethering
So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.
conspirator.of.crisis said:
So Jax184 are you tethering on the JB ROM on Wind somehow or are you waiting for the tethering fix like Braccoz? I am on Wind as well and want to keep running the JB ROM but need to be able to tether on pretty much a constant basis.
Click to expand...
Click to collapse
I'm waiting on tethering as well.
Jax184 said:
I'm waiting on tethering as well.
Click to expand...
Click to collapse
Thanks - I just wanted to make sure I wasn't missing something - guess that means I'm going back down to LJ1 until we get tethering!
---------- Post added at 09:47 PM ---------- Previous post was at 09:30 PM ----------
Now I'm in trouble - I got distracted while trying to go back to LJ1 and ended up applying the LJ1 tethering fix to the JB ROM. Phone rebooted and got stuck on the screen with SAMSUNG with the pulsating blue background and just wouldn't go further. Got back in through ODIN and flashed back down to the LJ1 ROM but again when the phone reboots it is still stuck on the same screen. Did I just brick it? Anyone got any suggestions as to how I can get back up and running on *ANY* ROM?
Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).
The only reason to downgrade though for me is that I need to tether. Hence faced with this problem I started going through all the Wifi Tether apps (that I tried before the tethering patch was out for the previous versions and none worked) and discovered the FoxFi works. It seems to override the T-Mobile tethering restriction in that when it is active the normal Mobile Hotspot icon appears (as well as the FoxFi icon) in the notification bar and when you pull it up it shows as On with the devices connected listed. Using FoxFi isn't as elegant as just using the built-in software hence I'll hobble along with the new image and FoxFi but still hopes that someone is kind enough and smart enough to figure out a tethering fix for this image.
Anyone got any comments or suggestions?
Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.
If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.
sent while running with scissors
gee one said:
Does anyone have the OTA update from TMO? I was going to make a flashable stock jelly bean rom, and the updater script is useful.
If you received the update and didn't apply it, it should be in the cache partition. PM me if you need help pulling it out.
sent while running with scissors
Click to expand...
Click to collapse
Wouldn't this help?
http://forum.xda-developers.com/showthread.php?p=40591848#post40591848
That is the full rom, I was looking for the actual OTA update because I wanted to look at the updater-script.
Here it is:
http://rapidshare.com/files/1683651545/update_mc5_7bda365f.zip
7bda365f9db8d24235b22787ed0c560c update_mc5_7bda365f.zip
Does GPS work on the new stock rom for you guys?
conspirator.of.crisis said:
Alright so it turns out that I didn't screw it up - the problem is that I just can't seem to downgrade. If I clear the cache in recovery and then flash the BMC5 (ie JB) image the phone will come back up running 4.1.2. However when I clear the cache and flash any other image (LJ1, LH1, etc) the phone just gets stuck on the SAMSUNG screen (and I've left it sit there for as long as 10 minutes to make sure it isn't actually doing anything).
Click to expand...
Click to collapse
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.
I'm having some gps issues and radio is requesting superuser access. This is on rooted,debloated jb with the jb radio.
Let me know if you need logs, data, or want me to flash something.
sent while running with scissors
JB downgrade to ICS + GPS
Thanks for the info Nardholio! I guess that means I'm staying at JB then. Overall I'm happy with it and having no problems perse. However to address your specific comment about GPS, although I haven't had any issues with it I have noticed that it has taken up to 5 minutes to fully sync and get a position lock now. I hadn't attributed that to the upgrade necessarily though as this happens from time to time as being way up here in Calgary Alberta sometimes satellites aren't as easily visible as they could be and this happens occassionally with all of my GPS receivers. My old G2 used to have quite a lot of problems that way. Haven't noticed anything about root requests though as Gee One indicated.
Nardholio said:
You need to wipe everything, data, system, cache in order to downgrade from JB to ICS. Also wifi is likely to be broken due to the new JB over writing the persist partition. Someone who is still on ICS and who is rooted should probably keep a copy of that.
Click to expand...
Click to collapse
does making a cwm backup cover that, and all other stuff needed too?
The Problem/Symptoms: I've been running a version of last CM10.2 for the past year. On February 20th, I was able to send a single SMS and then subsequent texts failed. I could still receive SMS, send/receive MMS, send/receive calls and send/receive data. If I toggle airplane mode/reboot I can send another SMS and then subsequent sms are undeliverable.
What wont work: Flashing to CM11 does not change the issue.
Disabling Voice+ does not change the issue
Factory Reset does not change the issue
Workarounds: Toggle Airplane mode
Switching Mobile Network to CDMA only (not permanent)
Change your number to a different area code
Going back to a Touchwiz based ROM
The Solution
net-cat said:
Alright. I think I've refined my process and it results in having a newer radio as well as not having to ODIN things or do dd commands.
NOTE: This isn't fully tested. When I did this, my phone wasn't showing the issue. I did this after doing my original procedure, but the GPS stopped working after I updated the radio from VRALF2 to VRBMB1. You shouldn't need to do the original procedure for this to work, but I haven't tested that. At the very least, the original procedure still works and this one can be used afterward if you need the newer radio. (GSM support...)
Ideally, we'll want to get to a procedure that doesn't use ODIN or dd. Hopefully this is a step in that direction.
Requirements:
A rooted stock ROM of the VRUCML1/4.3 vintage. I used Scott's Stock Rooted Knox Free VRUCML1 - 4.3 - DeOdex - V2. (Thread here.)
VRBMB1 AIO Flash, available here. (Thread here.)
I'm going to assume you know how to boot into and use recovery.
NOTE: Do NOT let the stock ROM install any updates.
Starting with my CM11 M3 install, I did a nandroid backup. (Recovery is CWM Touch 6.0.4.5, but I doubt that matters.)
Flash the VRBMB1 AIO.
Wipe data and cache.
Flash the stock ROM.
Boot into the stock ROM.
The reprovisioning seems to happen as a part of ROM's initial boot up.
Send a few text messages to test. (I sent them to Twitter.)
Launch the Maps application, turn on your GPS and let it get a lock. If you don't, when you boot back into your ROM, you probably won't have working GPS.
This would be a good time to back up your IMEI if you haven't already done so.
Reboot into your recovery, wipe data/cache and restore your nandroid backup.
At this point, you'll be running your preferred ROM with a less archaic radio than my previous post.
DO NOT UPGRADE YOUR RADIO. The moment I upgraded my radio, the problem came back!
CM11 M3 will work just fine with the old radio. I've rebooted several times over the last few hours and it still works fine. (Time will tell if it's a long term fix or not.)
Click to expand...
Click to collapse
buffal0b1ll said:
I put a MB1 aoi zip in my dropbox for you. It's from invisblek.org which isn't working now for some reason https://www.dropbox.com/s/7b1aqspo40fxl00/VRBMB1.aio.zip
Click to expand...
Click to collapse
Notes: There are threads for the S4 with this identical problem. All updated information I have seen is listed above. If anyone knows more please post as I am going to keep this updated. If this does/doesn't work for you please post and let the community know. Feel free to hit the thanks button if it works for you.
This exact thing happened to me. I tried many fixes with no luck. After hours of hacking around in settings, I found a ROM of verizon's 4.3 OTA update and flashed that through ODIN. My texts are working just fine again. Kind of a cheap method of fixing my problem. I wish I could have taken more time to find a fix, but I needed to be able to communicate with people that day.
Stock 4.3 is kind of lame:
-4.3 is killing my battery faster than ever. CM11 had me going for days without charging and now I've needed to charge everyday.
-Stock 4.3 is laggier/slower than CM11. It tends to stutter for me.
-4.3 came with a new boot loader which no developers have exploited to install custom ROMs yet. This leaves you stuck with Verizon bloat. I hate all these damn apps. Going to try to safe root & see if I can't do some cleanup work.
Enough ranting. Just wanted to let you know you are not alone with this problem. Hopefully someone will figure it out. Missing my cyanogen mod already
It seems this problem has happened on other phones also running Cyanogenmod. I found this thread http://forum.xda-developers.com/showthread.php?t=2654822
It looks like the symptoms have all showed up at the same time approximately. (February 19th, 2014). Still looking for a better answer than going back to stock TW...
Edit: And another thread http://forum.xda-developers.com/showthread.php?t=2659280 This one suggests its all AOSP roms. But it seems many people are unaffected... I don't understand why/how.
edit2: and another thread http://forum.xda-developers.com/showthread.php?p=50627899
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Dex954 said:
Just looking for more info
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
SO this is the current status that I know.
The problem happens for everyone with a 570/717 area codes + on verizon + running Cyanogenmod (possibly any AOSP) + while connected to LTE which started on Feb 20th (the day before KitKat came out offically).
Current Workarounds:
Switch to TouchWiz based Roms
Switch your radios to be CDMA only
Call verizon and switch your number to a different area code
I know the workarounds all suck but that all I know for now. Switching SIM cards won't work. If I anyone knows anything more please feel free to let me know.
I'm 717
Sent from my SCH-I535 using Tapatalk
I have still be unable to find a solution for this issue. I think I have to give up on CM and go back to a TW based. If I hear anything new I'll update the post but I don't have the time to be wasting on my phone at the moment. If someone finds or hears of a fix or if it magically goes away as it started, please post it.
And spread the word if there are any other ROMs that this is occurring on. It seems the pool of those affected is just too small.
I have already had to give up. Been running slows tw. I take it Verizon didn't get back to you?
Sent from my SCH-I535 using Tapatalk
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
DreamFX said:
Here is my thread guys. Same issue. I am gonna get on the fog horn with some Verizon buddies I have http://forum.xda-developers.com/showthread.php?t=2662658
Click to expand...
Click to collapse
Godspeed my friend.
Anyone try aosp to see if fixed yet?
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
capt730 said:
Nope. Still having issues. Tried gummy and cm. TW based roms are fine. In 717.
Click to expand...
Click to collapse
I try every other day. 717 for me. Remaining hopeful it's fixed... One day...
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
capt730 said:
What gapps are you using? I have been using the PA 0Day gapps. Going to try the gapps package from invisblek and see if that makes a difference.
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It won't. It isn't software dependent. People who had already flashed builds prior to the 20th magically had issues starting on that date, so it isn't a problem with new builds, and it only happens to those in the 717-570 areas so it isn't a problem with AOSP code. It has to be a Verizon network issue, I just have no idea how.
Sent from my SCH-I535 using XDA Premium 4 mobile app
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
capt730 said:
I have run TW base roms almost 100% of the time. Prior to the 20th, I had flashed cm11 3 or 4 times to see if camera worked and was never on it more than a day. I also had issues where music in my sd card wasn't being found but it was fine on TW. Could it be the unified build causing an issue? I have no issues on Clean Rom 8, wicked sensations or old and slows stock based roms.
*Edit* I have installed Gummy and CM 11 with PA Mini Modular apps and the CM Gapps from Invisiblek, let it set up. I then shut it down, removed battery and sim and then put everything back in and still the same issue. 1st text message goes through, then the rest after that just fail. I tried regular message app, Hangouts and Verizon messaging. All same results. I go back to my CR8 backup and all is fine. It's bizarre because everything else seems to be working fine and is very fast & smooth.
Click to expand...
Click to collapse
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
I'm ok with using CR8, Beans or other stock roms. Can't see paying for LTE and not using it lol. Was curious to see how aosp has been coming along and sms was really the only issue I was having.
Obaterista93 said:
It can't be an issue with the unified builds because going back and flashing an older build yields the same results. If you're willing to make the trade-off, you can set your phone to CDMA only. Texts will send, but you'll have no 3G or 4G.
Click to expand...
Click to collapse
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Whisk_33 said:
I was using masta's 10.2 build for over 6 months without even thinking about flashing new builds. The 20th is when the problem started for me. Upgrading to CM11 didn't change it. I just installed Hyperdrive and everything is back to normal.
I wish I could go back to CM but it just doesn't work in this area. And I don't know what I can do about it,
Click to expand...
Click to collapse
Basically. I've talked to a few friends who have worked for carriers and stuff, and everyone is stumped as to how something like this can even happen. Luckily I'm pretty much always in WiFi so I can survive on CDMA only.
I am currently on beanstalk build 275 (android KK), but when I try to reboot into recovery via the power menu, it doesn't work. I am in no way blaming this on the ROM. Instead I am looking for insight. This problem has existed for me since I installed ICS I believe. If I remember correctly, it was working on gingerbread ROMs just fine. Anyway, what happens is the phone proceeds to reboot, but instead of going to recovery after the samsung screen, it proceeds to the boot animation. I have searched around on xda for solutions for rebooting into recovery via the power menu and it seems that in the ICS days, the only way to fix it on ROMs that had this issue was to flash the SGS kernel if I remember correctly in order to get the right recovery and also regain the ability to get into it via all methods. The only problem is that I know that most newer ROMs use scott's modified kernel if I am not mistaken since there wasn't much development for our phone in terms of kernels after ICS. This means that if I take another ROM's boot.img (which I know contains our recovery), it will not change anything since I am basically installing the same kernel. So my question is would I have to go back to ICS in order to fix the problem there first then proceed to flash JB and KK? Thanks for any help or info you guys can provide :good: I hope I can resolve this soon since I find it convenient not having to power off then doing the three finger salute all the time
P.S.: Already asked in beanstalk Q&A also, but I did not get an answer and also I do not believe this problem is ROM related anyway as I said at the start of my paragraph
sorry misread, wrong answer
---------- Post added at 11:43 AM ---------- Previous post was at 11:23 AM ----------
did you download the ROM Manager app from Google Play and try to boot from there?
if it's not working then
I think I would:
put the 255 build and 275 build and Gapps of your choice into SDcard1
then wipe everything on the phone + format the 4 options in advance + format SDcard0
flash 255 + Gapps as per instruction
flash 275 + Gapps per instruction
---------- Post added at 11:48 AM ---------- Previous post was at 11:43 AM ----------
if that's not even working, then I put use the "SGH_I997 Entropy 4_4_2012-One-Click-Heimdall.jar" way
but lets not think of that much trouble - maybe you don't have the right recovery - my version is v6.0.4.7
Go to Developers Options and click on Advanced Reboot.
Sent from my SM-T310 using xda app-developers app
dparrothead1 said:
Go to Developers Options and click on Advanced Reboot.
Sent from my SM-T310 using xda app-developers app
Click to expand...
Click to collapse
The advanced reboot menu is already enabled, what I'm saying is that when i click reboot to recovery, it simply passes the splash screen and proceeds to boot
up normally...
g-noob said:
did you download the ROM Manager app from Google Play and try to boot from there?
if it's not working then
I think I would:
put the 255 build and 275 build and Gapps of your choice into SDcard1
then wipe everything on the phone + format the 4 options in advance + format SDcard0
flash 255 + Gapps as per instruction
flash 275 + Gapps per instruction
---------- Post added at 11:48 AM ---------- Previous post was at 11:43 AM ----------
if that's not even working, then I put use the "SGH_I997 Entropy 4_4_2012-One-Click-Heimdall.jar" way
but lets not think of that much trouble - maybe you don't have the right recovery - my version is v6.0.4.7
Click to expand...
Click to collapse
I'll try the rom manager part and reflashing the different ROMs when i get time and I'll let you know. I already have 6.0.4.7 by the way.
DE52 said:
I am currently on beanstalk build 275 (android KK), but when I try to reboot into recovery via the power menu, it doesn't work. I am in no way blaming this on the ROM. Instead I am looking for insight. This problem has existed for me since I installed ICS I believe. If I remember correctly, it was working on gingerbread ROMs just fine. Anyway, what happens is the phone proceeds to reboot, but instead of going to recovery after the samsung screen, it proceeds to the boot animation. I have searched around on xda for solutions for rebooting into recovery via the power menu and it seems that in the ICS days, the only way to fix it on ROMs that had this issue was to flash the SGS kernel if I remember correctly in order to get the right recovery and also regain the ability to get into it via all methods. The only problem is that I know that most newer ROMs use scott's modified kernel if I am not mistaken since there wasn't much development for our phone in terms of kernels after ICS. This means that if I take another ROM's boot.img (which I know contains our recovery), it will not change anything since I am basically installing the same kernel. So my question is would I have to go back to ICS in order to fix the problem there first then proceed to flash JB and KK? Thanks for any help or info you guys can provide :good: I hope I can resolve this soon since I find it convenient not having to power off then doing the three finger salute all the time
P.S.: Already asked in beanstalk Q&A also, but I did not get an answer and also I do not believe this problem is ROM related anyway as I said at the start of my paragraph
Click to expand...
Click to collapse
I use goo manager app to boot into recovery, always works and is good to go IMO
Judge Joseph Dredd said:
I use goo manager app to boot into recovery, always works and is good to go IMO
Click to expand...
Click to collapse
Ok so I've tried goo manager and also rom manager and neither worked. All that's left is to reflash the ROMs I guess or flash the heimdall package g-noob was talking about although I'm guessing that is a package made for ICS, so I shouldn't flash it with KK. I'll probably just flash back to stock and come back up to really check when the problem occurs as in which android version it starts in. Thanks for your suggestions though I'll report back later this week (probably on the weekend).
DE52 said:
Ok so I've tried goo manager and also rom manager and neither worked. All that's left is to reflash the ROMs I guess or flash the heimdall package g-noob was talking about although I'm guessing that is a package made for ICS, so I shouldn't flash it with KK. I'll probably just flash back to stock and come back up to really check when the problem occurs as in which android version it starts in. Thanks for your suggestions though I'll report back later this week (probably on the weekend).
Click to expand...
Click to collapse
Try Recovery Tools first. Grab it in playstore thats what I use. Give it a shot
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
eZdubzitmk4 said:
Try Recovery Tools first. Grab it in playstore thats what I use. Give it a shot
Sent from my lightning fast Note II running MeanBean 2.0 SuperCharged
Click to expand...
Click to collapse
I installed it and tried the reboot to recovery option which didn't work either in this app. Thanks for suggestion also
Flashing back has worked so far
I flashed back to GB as I said earlier. So far all ROMs have indeed booted into recovery. I guess on my way up the other times, I hadn't followed instructions in detail since I have not experienced any issues that I used to get so far. Hope it keeps going that way anyway once again thanks to everyone for your help! If I have any problems, I'll let you know (currently on Helly Bean 4.2.2 which I just flashed). The real test will come when I flash JB 4.3 and KK which is where I used to have problems booting from power menu.
EDIT: Ok so basically my problems start occurring on jb 4.3. I noticed that going from 4.2.2 to 4.3, the recovery reports a status 7 error. I already know that means the recovery is "old", but the thing is, it allows you to do an install anyway which I usually do in order for it to convert the file system and install the newer recovery which it does. The only thing though is I guess it doesn't repartition correctly due to that status 7 error. So I guess my question would be how I should proceed to get a 4.3 recovery without flashing a ROM or if there's a way to proceed that I am not aware of? Do you happen to have any links @eZdubzitmk4 or @Judge Joseph Dredd or @g-noob ?
sorry, I can't help you as I encountered error 7 so many times and getting to CWM was just sheer luck on my part
maybe you should try flashing CWM community kernel (I am not sure what it does, but it makes me believe that my infuse is unbreakable
http://forum.xda-developers.com/showthread.php?t=1119598
and I did flash everything twice or more than that to make sure everything stick
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
good luck man,
g-noob said:
sorry, I can't help you as I encountered error 7 so many times and getting to CWM was just sheer luck on my part
maybe you should try flashing CWM community kernel (I am not sure what it does, but it makes me believe that my infuse is unbreakable
http://forum.xda-developers.com/showthread.php?t=1119598
and I did flash everything twice or more than that to make sure everything stick
---------- Post added at 09:33 AM ---------- Previous post was at 09:32 AM ----------
good luck man,
Click to expand...
Click to collapse
Haha thanks, it's not so bad anyway. At least I can get into recovery through the manual way (3 buttons) and at least the ROMs install like you said. I was just checking if there was a way to avoid the status 7 which is caused by incompatible partition layout (which is why you flash twice by the way;the second time it ignores the layout and just proceeds). I'll give the link a try by the way.
A whole list of problems
Hi guys,
I was wondering what could be wrong with my phone:
Basically, I noticed that my battery life starting to decrease. I went ahead and invested in Anker batteries (comes with two of them) so I could basically improve my battery life.
I also had installed an app called Smart Wifi (an app that would detect the wifi's in my home and switch to the strongest/turn off when none detected) in that time period.
Now the current issues I have about a week later:
1. My wifi won't turn on. It's stuck on "turning on" but never does. I think Bluetooth is doing something similar
2. I will have a fully charged battery inside and the phone will eventually go black. I think it's still on because the phone stays warm. I can't seem to revive it. To fix it, I have to remove the battery and re-insert it.
I tried doing a factory reset and that fixed some of the slowing down problems. The black screen and wifi problem is still there. I'm not too good at this stuff, so any insight would be appreciated. I was considering rooting my phone and seeing if I could solve anything after installing a custom ROM but I wanted another pair of opinions first.
Thanks!
datguruguy said:
Hi guys,
I was wondering what could be wrong with my phone:
Basically, I noticed that my battery life starting to decrease. I went ahead and invested in Anker batteries (comes with two of them) so I could basically improve my battery life.
I also had installed an app called Smart Wifi (an app that would detect the wifi's in my home and switch to the strongest/turn off when none detected) in that time period.
Now the current issues I have about a week later:
1. My wifi won't turn on. It's stuck on "turning on" but never does. I think Bluetooth is doing something similar
2. I will have a fully charged battery inside and the phone will eventually go black. I think it's still on because the phone stays warm. I can't seem to revive it. To fix it, I have to remove the battery and re-insert it.
I tried doing a factory reset and that fixed some of the slowing down problems. The black screen and wifi problem is still there. I'm not too good at this stuff, so any insight would be appreciated. I was considering rooting my phone and seeing if I could solve anything after installing a custom ROM but I wanted another pair of opinions first.
Thanks!
Click to expand...
Click to collapse
I have the same problem today.
Factory reset and installing orginal rom don't fix problem :/
datguruguy said:
Hi guys,
I was wondering what could be wrong with my phone:
Basically, I noticed that my battery life starting to decrease. I went ahead and invested in Anker batteries (comes with two of them) so I could basically improve my battery life.
I also had installed an app called Smart Wifi (an app that would detect the wifi's in my home and switch to the strongest/turn off when none detected) in that time period.
Now the current issues I have about a week later:
1. My wifi won't turn on. It's stuck on "turning on" but never does. I think Bluetooth is doing something similar
2. I will have a fully charged battery inside and the phone will eventually go black. I think it's still on because the phone stays warm. I can't seem to revive it. To fix it, I have to remove the battery and re-insert it.
I tried doing a factory reset and that fixed some of the slowing down problems. The black screen and wifi problem is still there. I'm not too good at this stuff, so any insight would be appreciated. I was considering rooting my phone and seeing if I could solve anything after installing a custom ROM but I wanted another pair of opinions first.
Thanks!
Click to expand...
Click to collapse
i hv the same problem in my Lg g3 D855. Sometimes when i restart my phone, the wifi is working.. but the phone will shut down itself suddenly..... guys please help
.I also have this issue. Anyone found any solution
Same problem here. Reset factory and flashing don't help. My battery is draining by Android OS proccess.
For all of the posters on this thread. I may have a solution. I have a zip toolkit that has everything you need to do a complete restore of your d850. It will replace every bit of code that sometimes flashing a new rom doesnt. Now it will have to wait because there is one bug in the instructions that I accidently left out when i helped another guy, so iv contacted him so he could tell me what it was that I missed. But the process ill post here very soon should fix your problems.
---------- Post added at 08:27 AM ---------- Previous post was at 08:15 AM ----------
Here is the link for the file to download. This zip has everything you need to restore your g3 d850 to complete stock (better than factory reset). And has what you need for root.
https://drive.google.com/file/d/0B4FtiSFGCyvHaUlJSGREYm5RRnc/view?usp=drivesdk
********READ QUICK INFO BELOW******
Theres a bit of instruction missing from the included guide so here it is to save yall a confusing headache.
" You have to check mark the "board" box, not SW update...we are downgrading, not upgrading. If you check mark the SW upgrade box, you will end up in a factory reset 2 screen. If that happens just reflash again."
So my problem happened downgrading from marshmallow to kk using lgup. After i used flashtool i didnt get a mini os screen like i always have before it just bootloops but if i keep the battery out long enough it does boot and shows att logo then restarts and bootloops again. The only thing that works is using lollipop kdz from d850pr but i dont get wifi bluetooth or hotspot and the battery drains fast. I wish there was a tot for lollipop i know that would fix it. I did root the d850pr and tried flashing a rooted 20f stock rom but i get boot srcurity and i have to flash all over again. I really dont know why its bootlooping
---------- Post added at 06:40 PM ---------- Previous post was at 06:33 PM ----------
Shadow Assassin said:
For all of the posters on this thread. I may have a solution. I have a zip toolkit that has everything you need to do a complete restore of your d850. It will replace every bit of code that sometimes flashing a new rom doesnt. Now it will have to wait because there is one bug in the instructions that I accidently left out when i helped another guy, so iv contacted him so he could tell me what it was that I missed. But the process ill post here very soon should fix your problems.
---------- Post added at 08:27 AM ---------- Previous post was at 08:15 AM ----------
Here is the link for the file to download. This zip has everything you need to restore your g3 d850 to complete stock (better than factory reset). And has what you need for root.
https://drive.google.com/file/d/0B4FtiSFGCyvHaUlJSGREYm5RRnc/view?usp=drivesdk
********READ QUICK INFO BELOW******
Theres a bit of instruction missing from the included guide so here it is to save yall a confusing headache.
" You have to check mark the "board" box, not SW update...we are downgrading, not upgrading. If you check mark the SW upgrade box, you will end up in a factory reset 2 screen. If that happens just reflash again."
Click to expand...
Click to collapse
Ive tried your instructions a few hundred times lol samething. Bootloops
lingo2012 said:
So my problem happened downgrading from marshmallow to kk using lgup. After i used flashtool i didnt get a mini os screen like i always have before it just bootloops but if i keep the battery out long enough it does boot and shows att logo then restarts and bootloops again. The only thing that works is using lollipop kdz from d850pr but i dont get wifi bluetooth or hotspot and the battery drains fast. I wish there was a tot for lollipop i know that would fix it. I did root the d850pr and tried flashing a rooted 20f stock rom but i get boot srcurity and i have to flash all over again. I really dont know why its bootlooping
---------- Post added at 06:40 PM ---------- Previous post was at 06:33 PM ----------
Ive tried your instructions a few hundred times lol samething. Bootloops
Click to expand...
Click to collapse
Well that sucks, it had worked for someone els so it maybe a fluke. An unfortunate one... So one thing to try now is this---
1. Download LG PC Suite here. Don’t worry about USB drivers, this program will automatically install them.
2. Turn your LG G3 off.
3. Connect your LG G3 to your computer and hold the Volume Up button.
4. This will put your phone into Download Mode.
5. After a few seconds in Download mode,
Open LG PC Suite.
6. Tap on the Repair button and follow the steps that the program provides.
7. Wait for the program to fix your LG G3.
Hope this works. If not, ill keep looking for a fix. Im sorry your having these problems. It worked for me and another guy so idk why your bootlooping but I have heard that it can happen even when everything is done right. So lets see what happen. Let me know how the bootloop fix i provided works out.
Shadow Assassin said:
Well that sucks, it had worked for someone els so it maybe a fluke. An unfortunate one... So one thing to try now is this---
1. Download LG PC Suite here. Don’t worry about USB drivers, this program will automatically install them.
2. Turn your LG G3 off.
3. Connect your LG G3 to your computer and hold the Volume Up button.
4. This will put your phone into Download Mode.
5. After a few seconds in Download mode,
Open LG PC Suite.
6. Tap on the Repair button and follow the steps that the program provides.
7. Wait for the program to fix your LG G3.
Hope this works. If not, ill keep looking for a fix. Im sorry your having these problems. It worked for me and another guy so idk why your bootlooping but I have heard that it can happen even when everything is done right. So lets see what happen. Let me know how the bootloop fix i provided works out.
Click to expand...
Click to collapse
Fluke indeed lol its weird but ill try pc suite ill let you know thank you
lingo2012 said:
Fluke indeed lol its weird but ill try pc suite ill let you know thank you
Click to expand...
Click to collapse
So pc suite didnt work so i downloaded 10f tot and everythings working now except wifi and bluetooth. Bluetooth turns now but it doesnt find anything. So atleast its working ill read around about the bluettoth and wifi. Thank you for your help even if it didnt work it was worth a try
lingo2012 said:
So pc suite didnt work so i downloaded 10f tot and everythings working now except wifi and bluetooth. Bluetooth turns now but it doesnt find anything. So atleast its working ill read around about the bluettoth and wifi. Thank you for your help even if it didnt work it was worth a try
Click to expand...
Click to collapse
You have a completely new system so... Theres a chance its a hardware problem. It shouldnt since they are built into the SOC but your phone may have broken antennas. Ill keep looking to see what i can find. One thing to try is flash the nwest radio.
Shadow Assassin said:
You have a completely new system so... Theres a chance its a hardware problem. It shouldnt since they are built into the SOC but your phone may have broken antennas. Ill keep looking to see what i can find. One thing to try is flash the nwest radio.
Click to expand...
Click to collapse
Its weird everything was working until i downgraded from mm to kk. I flashed the newest radio its still not working. Im gonna keep looking around theres gotta be something and thank you again
---------- Post added at 06:11 AM ---------- Previous post was at 05:28 AM ----------
Shadow Assassin said:
You have a completely new system so... Theres a chance its a hardware problem. It shouldnt since they are built into the SOC but your phone may have broken antennas. Ill keep looking to see what i can find. One thing to try is flash the nwest radio.
Click to expand...
Click to collapse
Ok so i flashed Crdroid and my wifi is working now
lingo2012 said:
Its weird everything was working until i downgraded from mm to kk. I flashed the newest radio its still not working. Im gonna keep looking around theres gotta be something and thank you again
---------- Post added at 06:11 AM ---------- Previous post was at 05:28 AM ----------
Ok so i flashed Crdroid and my wifi is working now
Click to expand...
Click to collapse
That was weird, so everything is working ok now?
Shadow Assassin said:
That was weird, so everything is working ok now?
Click to expand...
Click to collapse
Yeah its crazy and when i go back to stock wifi and bluetooth dont work
lingo2012 said:
Yeah its crazy and when i go back to stock wifi and bluetooth dont work
Click to expand...
Click to collapse
Its probably a corrupt file. Since its working on the rom you just flashed, then ill bet the stock rom file is corrupt. It happens. But glad to see everything it working. Im running CloudyG3 its stock based and it works wonders for me.
Shadow Assassin said:
Its probably a corrupt file. Since its working on the rom you just flashed, then ill bet the stock rom file is corrupt. It happens. But glad to see everything it working. Im running CloudyG3 its stock based and it works wonders for me.
Click to expand...
Click to collapse
I ran cloudy g3 i love it im gonna give that a try and see
datguruguy said:
Hi guys,
I was wondering what could be wrong with my phone:
Basically, I noticed that my battery life starting to decrease. I went ahead and invested in Anker batteries (comes with two of them) so I could basically improve my battery life.
I also had installed an app called Smart Wifi (an app that would detect the wifi's in my home and switch to the strongest/turn off when none detected) in that time period.
Now the current issues I have about a week later:
1. My wifi won't turn on. It's stuck on "turning on" but never does. I think Bluetooth is doing something similar
2. I will have a fully charged battery inside and the phone will eventually go black. I think it's still on because the phone stays warm. I can't seem to revive it. To fix it, I have to remove the battery and re-insert it.
I tried doing a factory reset and that fixed some of the slowing down problems. The black screen and wifi problem is still there. I'm not too good at this stuff, so any insight would be appreciated. I was considering rooting my phone and seeing if I could solve anything after installing a custom ROM but I wanted another pair of opinions first.
Thanks!
Click to expand...
Click to collapse
i have D850 and believe me i have had every issue with including the one you are talking about the best fix that kinda worked for me was :
1)open up the phone just remove the phiilip screws
2)besides the camera there is a connecting chip
3)place 2 small square pieces of paper on it covering it
4)close it up and see if it is fixed
if not just increase the number of papers
for a visual guide just watch it in youtube