Don't want to waste time maintaining a few threads. I'll group all M developments in the following thread
http://forum.xda-developers.com/showthread.php?t=3234388
I really don't want to repeat again and again. If you don't want to read the above thread.
Please don't post here. I have no choice but ignore it, sorry
Device specific discussions and issues may post here.
Tab Plus know issues:
** On top of those in the main threads. **
1. Please report ...
Thank you very much Daniel, it may sound a bit strange to say it like this..... but you are the gratest. Thanks for supporting this outdated device. I will try it out, as soon as i get my Z2 tablet back from repair...untill then galaxy tab is my daily runner...(running strong on your CM12.1 rom btw). Thanks again.
PThanks a lot man you're a legend your work is incredible... But there's something went wrong with me... After i flashed the rom successfully with twrp i clicked reboot system and twrp asked me (no os installed, are you sure you wish to reboot ) and when i rebooted the device it stuck on the white samsung galaxy tab 7.0 plus logo... I waited around 12 mins but nothing happend... So i returned to omni rom 5.1.1
Root97 said:
PThanks a lot man you're a legend your work is incredible... But there's something went wrong with me... After i flashed the rom successfully with twrp i clicked reboot system and twrp asked me (no os installed, are you sure you wish to reboot ) and when i rebooted the device it stuck on the white samsung galaxy tab 7.0 plus logo... I waited around 12 mins but nothing happend... So i returned to omni rom 5.1.1
Click to expand...
Click to collapse
Your internal storage is probably corrupted.
1. If you can access the sdcard in TWRP, backup your data first.
2. See if you can format the system partition in TWRP.
If yes, do a factory reset and flash ROM again.
If no, you need the PIT file.
You didn't mention your model. You might need the particular PIT file to repartition.
If someone have the PIT for tab-plus, please post it. Otherwise, you have to flash the oldest HC3.2 ROM with Odin first, then TWRP and ROM again.
Next time, don't forget the detail
Good luck!
daniel_hk said:
Your internal storage is probably corrupted.
1. If you can access the sdcard in TWRP, backup your data first.
2. See if you can format the system partition in TWRP.
If yes, do a factory reset and flash ROM again.
If no, you need the PIT file.
You didn't mention your model. You might need the particular PIT file to repartition.
If someone have the PIT for tab-plus, please post it. Otherwise, you have to flash the oldest HC3.2 ROM with Odin first, then TWRP and ROM again.
Next time, don't forget the detail
Good luck!
Click to expand...
Click to collapse
My Tab is Gt-p6200 and yes i can format the system partition in twrp... I did wipe the system and data and cache and factory reset and the rom was flashed successfully but when i press reboot twrp shows the same message again but when i do the same with omni 5.1.1 it works flawlessly without any trouble
Root97 said:
My Tab is Gt-p6200 and yes i can format the system partition in twrp... I did wipe the system and data and cache and factory reset and the rom was flashed successfully but when i press reboot twrp shows the same message again but when i do the same with omni 5.1.1 it works flawlessly without any trouble
Click to expand...
Click to collapse
What version of TWRP? Are you in old version or wrong version? Latest is 2.8.7.1.
Sometimes we easily overlook something. A photo worth a thousand word. I would say you must have missing or overlook something.
Flashing is straight forward, nothing special. With what you provided, I don't think I can help. Sorry.
daniel_hk said:
What version of TWRP? Are you in old version or wrong version? Latest is 2.8.7.1.
Sometimes we easily overlook something. A photo worth a thousand word. I would say you must have missing or overlook something.
Flashing is straight forward, nothing special. With what you provided, I don't think I can help. Sorry.
Click to expand...
Click to collapse
Thanks for the tip it turned out that i have 2.8.7.0 so i updated it to 2.8.7.1 and did a factory reset and flashed the rom and gapps but twrp still asks me the same question (there is no os) and if i reboot all i see samsung galaxy tab 7.0 plus white logo... I'll just go back to lollipop and wait for the next marshmallow build thanks for your support... You've been helpful
http://dl-1.va.us.xda-developers.co....jpg?key=VgBFRc8Qr76wpYuWCa3sdA&ts=1446932934
Root97 said:
Thanks for the tip it turned out that i have 2.8.7.0 so i updated it to 2.8.7.1 and did a factory reset and flashed the rom and gapps but twrp still asks me the same question (there is no os) and if i reboot all i see samsung galaxy tab 7.0 plus white logo... I'll just go back to lollipop and wait for the next marshmallow build thanks for your support... You've been helpful
Click to expand...
Click to collapse
that's the message
Root97 said:
http://dl-1.va.us.xda-developers.co....jpg?key=VgBFRc8Qr76wpYuWCa3sdA&ts=1446932934 that's the message
Click to expand...
Click to collapse
Dump the log of TWRP might have more info.
It might be a bad download of Rom. Test if you can open it and see the content. Or better check the md5 for the file.
If the md5 checksum is correct, try flashing rom only without gapps first.
Good luck
I may be asking too much, but is there any chance that you include p6210 in testing as well?
Gonib said:
I may be asking too much, but is there any chance that you include p6210 in testing as well?
Click to expand...
Click to collapse
You are great!!!!
Dear Daniel,
Thanks for this great job of yours.
I reported my P6200 issue, i already do the instruction without any error.
But with a result:
1. SIM Card undetected
2. Back camera will have a green line in the left
3. Baseband version in About Tablet is "Unknown"
Is any solution?
Big Thanks.
gamalrizaldi said:
Dear Daniel,
Thanks for this great job of yours.
I reported my P6200 issue, i already do the instruction without any error.
But with a result:
1. SIM Card undetected
2. Back camera will have a green line in the left
3. Baseband version in About Tablet is "Unknown"
Big Thanks.
Click to expand...
Click to collapse
Have all the same issues on my P6200 too and even one more: after some times in standby the auto rotate function does not work anymore. Only a reboot brings is back.
gamalrizaldi said:
Dear Daniel,
Thanks for this great job of yours.
I reported my P6200 issue, i already do the instruction without any error.
But with a result:
1. SIM Card undetected
2. Back camera will have a green line in the left
3. Baseband version in About Tablet is "Unknown"
Is any solution?
Big Thanks.
Click to expand...
Click to collapse
uli-hh said:
Have all the same issues on my P6200 too and even one more: after some times in standby the auto rotate function does not work anymore. Only a reboot brings is back.
Click to expand...
Click to collapse
I think I found the problem. I put the wrong link in the blobs.. Sorry...
Flash this View attachment ril7-patch.zip in recovery will fix the SIM issue.
Thanks for your patience...
daniel_hk said:
I think I found the problem. I put the wrong link in the blobs.. Sorry...
Flash this View attachment 3550924 in recovery will fix the SIM issue.
Thanks for your patience...
Click to expand...
Click to collapse
Hi Daniel
Thank you very much for the quick response. I've flashed the fil7-patch.zip but unfortunately it did not work. Baseband-Version is still unknown!:crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
here is the logcat
uli-hh said:
Hi Daniel
Thank you very much for the quick response. I've flashed the fil7-patch.zip but unfortunately it did not work. Baseband-Version is still unknown!:crying:
View attachment 3551333
here is the logcat
Click to expand...
Click to collapse
I've checked your log. It might require a rebuild. Just be patient and wait for the next build.
I was thinking to release CM next but Omni is much more stable. I'll release the latest Omni first. It'll be ready in a few days.
I just checked the Gapps (Delta 1114-1) too. Some default permissions are OFF which cause Setup Wizard to crash. I went to Settings via QS turning them ON and everything seems fine now. It is quite slow via VPN but I can setup google accounts and downloading with Play. No problem with Youtube too.
Gapps service occasionally crash. It happens since they were pulling from other device (Nexus 6, I think) with different resolution.
In that case, I might consider making my own Gapps later.
P.S. If possible, don't use Google drive. I can't access it directly. Just attach the text file (or zipped) in the post would be better.
Thanks again very much for the quick response. I'll be patient and wait for the next build. You are doing such a great work!:victory:
PS: I did not realize that I also can upload txt files here (thought it was for pictures only ).
i'm the only p6200 user whot get a bluetooth bug ?! , http://dl.free.fr/getfile.pl?file=/719KjfLb
betexino said:
i'm the only p6200 user whot get a bluetooth bug ?! , http://dl.free.fr/getfile.pl?file=/719KjfLb
Click to expand...
Click to collapse
Just tried out bluetooth. Can confirm the bug.
View attachment logcat.log
daniel_hk said:
I think I found the problem. I put the wrong link in the blobs.. Sorry...
Flash this View attachment 3550924 in recovery will fix the SIM issue.
Thanks for your patience...
Click to expand...
Click to collapse
Thanks! I'll test the patch now.
Related
Some users are noticing GPS issues after flashing to EC05. The issues include the inability to lock on satellites after extended period of up-time and terrible accuracy. The phone would have to be rebooted to get GPS working again. These issues are affecting users with stock and custom ROMs.
Following these steps will get your phone to a perfectly working EC05, with fully functional, bug free GPS:
1) Flash your phone back to stock DI18 via Odin (the .tar belongs in the PDA slot and your phone must be in download mode)
2) Follow steps 1-8 on this post.
3) Update to EC05 via OTA update or Flash Stock EC05 with Odin.(if you want to stay stock and unrooted, jump to step 7 after this step)
4) Install latest One click Root and Recovery + ClockworkMod v3.0.0.5/6 for EXT4 (optional) (Warning: this will format your NAND to EXT4 the first time you boot to recovery. If you do install this version, you must install an EXT4 ROM after booting to Recovery the first time. The stock ROM will not boot afterward.)
or
4B) Install One Click Root and Recovery + ClockworkMod v2.5.5 for RFS (optional)
5) Perform a backup, in clockworkmod (optional)
6) Install a custom ROM (optional)
7) Install all of your apps and enjoy a fully functional GPS
Calibrate your battery by following this thread (I suggest the second or third option)
I suggest to not restore apps from a previous flash. It might cause some issues. If you do encounter any issues, at least you won't have that to blame for it.
buggerritt said:
Some users are noticing GPS issues after flashing to EC05. The issues include the inability to lock on satellites after extended period of up-time and terrible accuracy. The phone would have to be rebooted to get GPS working again. These issues are affecting users with stock and custom ROMs.
Following these steps will get your phone to a perfectly working EC05, with fully functional, bug free GPS:
1) Flash your phone back to stock DI18 via Odin (the .tar belongs in the PDA slot and your phone must be in download mode)
2) Follow steps 1-8 on this post.
3) Update to EC05 via OTA update or Flash Stock EC05 with Odin.(if you want to stay stock and unrooted, jump to step 7 after this step)
4) Install latest One click Root and Recovery + ClockworkMod v3.0.0.5/6 for EXT4 (optional) (Warning: this will format your NAND to EXT4 the first time you boot to recovery. If you do install this version, you must install an EXT4 ROM after booting to Recovery the first time. The stock ROM will not boot afterward.)
or
4B) Install One Click Root and Recovery + ClockworkMod v2.5.5 for RFS (optional)
5) Perform a backup, in clockworkmod (optional)
6) Install a custom ROM (optional)
7) Install all of your apps and enjoy a fully functional GPS
Calibrate your battery by following this thread (I suggest the second or third option)
I suggest to not restore apps from a previous flash. It might cause some issues. If you do encounter any issues, at least you won't have that to blame for it.
Click to expand...
Click to collapse
Dont take this wrong but you are compelty incorrect. that particluar "old solution" was for the early test versions of eb13 froyo which had other different GPS issues from the cache issue. EB13 was actually fixed and had perfect GPS by the time of its official OTA.
What users (and Sprint advanced device) are seeing is a return of the assistance cache issue. All that flashing etc is obviously clearing the assistance cache which is why you had a problem and don't see it yet.
aero1 said:
Dont take this wrong but you are compelty incorrect. that particluar "old solution" was for the early test versions of eb13 froyo which had other different GPS issues from the cache issue. EB13 was actually fixed and had perfect GPS by the time of its official OTA.
What users (and Sprint advanced device) are seeing is a return of the assistance cache issue. All that flashing etc is obviously clearing the assistance cache which is why you had a problem and don't see it yet.
Click to expand...
Click to collapse
You sir are incorrect. This fix was actually from DK28 (pre EB13). It has fixed my GPS. Perhaps your GPS has had no issues. If so, I am very happy for you. I never had problems with EB13. I did with DK28 and fixed it with this (while many others were still bumbling around and wishing for the official Froyo because they were scared to use a beta). Afterward my DK28 had perfect GPS. I also did with EC05. Others have had issues with EC05, as well. The problems seem to be from the same cache problem that DK28 had. If not, then this would not have solved the issues. I now get lock on satellites all the time and have accuracy of 1-2 meters.
I followed the steps over 4 days ago so, your theory on clearing the assistance cache does not apply.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This was after over 9 hours uptime. The lock took 2 seconds for the first satellite and full lock on all within 10 seconds. Use of wireless networks disabled. This was not possible before following the steps in the OP. Previously, I was unable to get a lock after 3-5hours uptime. I would have had to reboot.
Sent from my SPH-D700 using Tapatalk
buggerritt said:
You sir are incorrect. This fix was actually from DK28 (pre EB13). I.
Click to expand...
Click to collapse
OMG you are posting a copy of my fix from Sept and don;t even realize it!
aero1 said:
OMG you are posting a copy of my fix from Sept and don;t even realize it!
Click to expand...
Click to collapse
Please link me to your original fix. I would love to give you the credit for fixing my GPS, instead of ahmgsk, if yours is the original one. If you are the original poster, I find it very silly for you to deny that it fixes EC05 GPS issues, too. It does, indeed.
But, if you are referring to this thread, where your OP states:
"TESTED AND FUNCTIONING WORKAROUND:
Enter GPS debug/settings application by typing *#1472365#
click "Setup" tab
click "position mode"
Click "starting mode
Enable "Cold Start"
Back out.
Epic GPS will now call on data network for fresh valid ephemeris and almanac at every programing invocation of GPS and aGPS fixes will be very fast (usually less than 10 seconds)."
then, it is not the entire workaround. It doesn't mention anything about locking on satellites in each startup mode. It doesn't mention locking on satellites in any mode, as a matter of fact. It also doesn't mention anything about flashing any updates after the workaround. I hope your upcoming link, to the complete workaround that actually works, will shed some light as to who I truly owe my thanks and appreciation for. If it is you, then I will applaud you with a plethora of golf claps.
Hey there
I wasn't able to find whether the person you asked to do a nandroid restore; after Odin to DI18 steps to fix the GPS issue you were able to clear up.
Just today I have experienced what you describe. I've never had anything more than 4 minutes MAX to lock. I just tested and it didn't lock after 10 minutes.
Anyhow, did they restore or just do everything as stated in the OP??
Thanks!!
Well now that I see results I will forsure have to try now
jdelano said:
Hey there
I wasn't able to find whether the person you asked to do a nandroid restore; after Odin to DI18 steps to fix the GPS issue you were able to clear up.
Just today I have experienced what you describe. I've never had anything more than 4 minutes MAX to lock. I just tested and it didn't lock after 10 minutes.
Anyhow, did they restore or just do everything as stated in the OP??
Thanks!!
Click to expand...
Click to collapse
Here is how the conversation went:
(fnordsnafu replied to what I asked carnivalrejectq)
buggerritt said:
Perhaps, you could do us both and others a favor, then. This would be an experiment. You could create a nandroid backup, perform steps 1-4, flash midNIGHT 5.2, and perform a complete restore and see if that will also fix it. the worst case scenario would be that you are right back where you are, now. It might actually fix it and you could help others with that bit of experience. It's up to you, of course. I know it is a lot to ask, since it takes time and there is no guarantee.
Click to expand...
Click to collapse
(11th April 2011, 11:30 PM)
fnordsnafu said:
I actually just did this. So far so good. I will keep testing to see if I get a lock over the next several hours and then days. Fingers crossed that this worked. Uber tired of the GPS issue.
Click to expand...
Click to collapse
buggerritt said:
Thanks for giving it a go. I hope it does work. There were no promises for it, with restore.
Click to expand...
Click to collapse
(12th April 2011, 09:46 AM)
fnordsnafu said:
So far so good. Got a lock within 2 or so seconds and a full 12/12 within 10 seconds and I'm inside. A definite success so far. Will continue to update.
Click to expand...
Click to collapse
buggerritt said:
If it still works after 8 hours of uptime, I'd say you have a winner
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
buggerritt said:
What are your findings, now, after so many hours of uptime?
Click to expand...
Click to collapse
(12th April 2011, 07:16 PM)
fnordsnafu said:
It's still going strong. Fast, solid fix every time. Very, very happy. Thanks sooooo much!
Click to expand...
Click to collapse
There are still no guarantees but, restore worked for this user.
BTW, mine is still going strong and it has been a week running. I always get lock within 2 seconds and always get 10-12 satellites within 10 seconds. Within 15-20 seconds, accuracy improves to 1 meter. This happens every time, whether I have just swapped my battery or if I've got 18 hours uptime. It makes no difference and I don't have to clear cached GPS data or download GPS assistance data. It just works every time all the time.
Anon9mouz said:
Well now that I see results I will forsure have to try now
Click to expand...
Click to collapse
I hope it works for you, too. Please post your results.
Well like I said in the Midnight thread, I never had an issue with gps other than it taking forever to lock. After doing this I'm locked in in about 5 to 10 seconds at or around 20 to 30 meters. Its only a few seconds after that I'm locked at 9 to 10 meters. This work around has my vote of helping get a faster lock. I can't comment of any other results becuz as I stated my only issue was wait time with locking but now I'm locked in in no more than 15 seconds. That is faster than any. Gps lock I've ever gotten on this phone and I've had it since it came out. Thanks for this one once again.
Sent from my SPH-D700 using Tapatalk
That's good enough for me.
First of all, I appreciate this thread, the OP, and all of the suggestions listed here.
Unfortunately, I just thought I'd mention that I tried this fix [using the restore method], and GPS continued to crap out on me after a day or so--by which I mean it would become completely nonfunctional, without even an icon showing in the notification bar.
I am currently trying the "GPS crash" fix that was added to the following thread yesterday:
http://forum.xda-developers.com/showthread.php?t=1029152
I'm hopeful about this one, as the explanation behind it seems pretty well-reasoned and thought out.
Hopefully the fix in this post will continue to help people, but I'm going on record as saying it didn't work for me.
Cash Machine said:
Hopefully the fix in this post will continue to help people, but I'm going on record as saying it didn't work for me.
Click to expand...
Click to collapse
The two are complementary. The crash fix should be tried first since that's well-investigated problem at this point. If you continue to have GPS issues (icon comes up, but can't find satellites after 5 hours of uptime), it's possible this method may help. We're still not quite certain what it does exactly, likely changes something in the baseband NVRAM, but beyond its only known that it does help some folks.
Also, the restore method is not suggested, it worked for a couple people but, generally restores have a tendency to restore problems, as well as everything else.
Sent from my SPH-D700 using Tapatalk
9 hours of uptime is not long enough for the original problem to show.
just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.
mikeew83 said:
just installed the latest cm 10 nightly from rom manager now when i boot my phone get a screen says system software not authorized by verizon wireless has been found on your phone please turn off your phone and go to the nearest verizon wireless store for help.
Click to expand...
Click to collapse
Did you unlock your bootloader?
yep
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.
Had the same issue setting up my bro's galaxy yesterday. I had to flash back to stock via Odin and then I just redid root and unlock boot loader and haven't had issue since. Running the new d2vzw euroskank right now with no issues.
yea
I figured as much i was downloadin the files had to run out so just switched devices real fast while i fix it figure ill just start from scratch once i odin back to stock.
Marcismo55 said:
I wouldn't run the official nightlies for the time being until the data and MMS fixes get approved and merged. CVPS (Austin Dickenson) posted an Alpha 2 on his G+ with those fixes above so you would be better off running those.
Click to expand...
Click to collapse
sent from my unlocked bootloader Verizon Samsung galaxy s III
mikeew83 said:
I rooted it then i used ezunlock went thru successfully it stated i then backed up my stock rooted and did the rest of of normal wen in to rom manager downloaded did a full wipe dalivk cache data etc and then phone installed and rebooted to that verizon warning screen talk about big brother much.
Click to expand...
Click to collapse
You need to UNLOCK your bootloader not just root. the official CM is a non kexec kernel and you are still running with your locked bootloader
and fixed
just funny to me how far verizon will go to feel like big brother so to speak.
Assuming your bootloader is unlocked. I had the same thing happen the first time. Tried to use CWM, missed the suggestion of flashing TWRP from EZ Recovery. Made all the difference. Watch the video from DroidModd3rX:
Verizon Galaxy S3 Cyanogen Mod 10 Unofficial NONKEXEC Install (I can't post links yet, sorry)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using xda app-developers app
is it suitable for daily use??
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.
I had more then just those issues, apparently my phone was sending doubles text messages, also WiFi struggled to keep a solid signal, data also dropped in and out and last but not least screen would flicker. Did a clean install of the nightly build and alpha build and had the same issues.
Sent from my SCH-I535 using xda app-developers app
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I am happy with it. It has rebooted twice on me, once after an hour and a half phone call with Dell tech support, I was tired of talking to the guy anyway . But jelly bean is nice, if you don't need NFC, MMS, or Flash (can't get my side load to work). Guess it is all in the eye of the beholder, if you don't mind some of those issues is suitable.
Sent from my SCH-I535 using xda app-developers app
Mms is working fine as well as flash. What build are you on?
SGS3 production
zxsix said:
Depends on what you use the phone for. NFC still isn't working, which affects me. I hear NFL Mobile and some of the video apps like netflix aren't working.
Other than that, it's stable and fast.
Click to expand...
Click to collapse
Not quite stable. It suffers from reboots for some during/after calls..... Me for one. The original alpha build never showed that symptom. Also a lot of people are saying that they are having echo problems on calls.
TAPPED in on my (now unlocked bootloader) Verizon S3
Did the same thing
jasembiz said:
is it suitable for daily use??
Click to expand...
Click to collapse
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.
Nice !
same issue
bluetoast said:
I'm hosed. I have been trying to fix it with Odin but I don't know Odin well enough. I ran the stock root rom and then synergy. Last night I locked it by using the CW app instead of the manual method. Dang. How do I return to stock? Anyone? I used Odin to download the rooted rom, and had no issues with TWRP. I should have known better than to use CW recovery app and the CW recovery.
Click to expand...
Click to collapse
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?
rmcneely said:
Hi. I downloaded and installed the nightly CyanogenMod 10 build and on reboot I'm getting the same error: System software not authorized by Verizon. How did you get past this?
Click to expand...
Click to collapse
derp....unlock your bootloader!
droidstyle said:
derp....unlock your bootloader!
Click to expand...
Click to collapse
but how?? can't get past this unauthorized software screen
Hey all,
first of all I would like to say thank you for all for the great job you do in here. It's really awesome I don't have to depend on mobile carrier companies (who always a year late with updates ) and i can take care of my phone myself.
The reason I'm posting here is a problem what I can simply cannot resolve, however i search over the forums.
My problem is lockscreen / screenlock simply not working. Its working on 2.3.6. but not on 4.0.4, I did try I9103XXLQ7 as it is originaly and with flashed over with MAZEL's great rom but no luck. Also i flashed I9103XXLQ9 and tried and after screen lock not worked here either i flashed over BlueBerry ROM 2.1a, but again, no luck. I always do factory reset, wipe cache and dalvik cache still, simply not working.
I did try other locker softwares like holo locker and go locker but I came across a very interesting problem with them, they work fine until my morning alarm would start since somehow the 3rd party locker softwares blocking the alarm clock to start. Simply nothing happening, no wake up sound no light nothing until I touch the phone then suddenly it wakes up. It's not a good way, i get late from work a few times of because of this problem not to mention i miss the snooze option
Can anyone help me please and let me know if this a factory software issue and if it is how to get over it (even with 3rd party software which is not affecting the alarm clock)?
I live in Hungary, got this phone from a friend.
Thanks for everyone and sorry if this was posted elsewhere, i was searching but did not found.
Did you look into Settings->Security->Screen Lock? (I'm not sure if this is that option on stock ICS, but it should be.) Maybe it's set to 'None'. It should not be set to none if you always wipe data.
Adam77Root said:
Did you look into Settings->Security->Screen Lock? (I'm not sure if this is that option on stock ICS, but it should be.) Maybe it's set to 'None'. It should not be set to none if you always wipe data.
Click to expand...
Click to collapse
yeah, i did check there, i can set anything still nothing happens, if i set pin or pattern or even password it will be still nothing asked when closed and opened the phone.
If i set for example PIN and i lock the phone with button and open it again still no pin pass asked (immediatelly goes to home screen) but when i go to settings / security the default setting shown is pin... its like totally ignore anything i set
I did try to set none the reboot then set pin then reboot, same results... also same results with even and pattern security.
应该是软件冲突了。你把锁屏软件的都卸载了。然后在锁屏里从新设置试试。我以前也碰到过,
This guy is saying that "I've come across, this Should be a software conflict. You uninstall software lock screen. Try and set new lock screen."
Maybe..
Go back to Stock GB.
Then reflash your phone to stock ICS??
Tried this??
Sent from my GT-I9103 using xda premium
mj.vikram said:
This guy is saying that "I've come across, this Should be a software conflict. You uninstall software lock screen. Try and set new lock screen."
Click to expand...
Click to collapse
Ty for translate the strange is even a full clean 4.0.4 install has no working screen lock so i dont really know what to uninstall then.
DeepankarS said:
Maybe..
Go back to Stock GB.
Then reflash your phone to stock ICS??
Tried this??
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
yeah, did try, on GB it's working fine...the strange thing is when is reflash GB it starts with the usual welcome screen (flashing GB with odin) set up account etc etc. but when i flash ICS (even after factory reset/cache wipe) it starts the system without the usual start screen... no welcome set you google acc or anything (i flash ICS in Odin too). somehow i got the idea it has something to do with the screen lock.
But is there any cleaner install then flash with ODIN? or should i try other factory FW to flash?
No. Use Odin v1.85
Maybe you should try downloading the STOCK ICS again.
Buddy try XWLP2 POLAND stock rom. As it is one of the latest and most stable stock ics rom with some bugs being corrected.
Our buddy kataria.vikesh has made a thread regarding this too "FROM WHERE TO DOWNLOAD" AND "HOW TO FLASH"
Maybe it will help.
Sent from my GT-I9103 using xda premium
DeepankarS said:
No. Use Odin v1.85
Maybe you should try downloading the STOCK ICS again.
Buddy try XWLP2 POLAND stock rom. As it is one of the latest and most stable stock ics rom with some bugs being corrected.
Our buddy kataria.vikesh has made a thread regarding this too "FROM WHERE TO DOWNLOAD" AND "HOW TO FLASH"
Maybe it will help.
Sent from my GT-I9103 using xda premium
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1983262
[FAQ][GUIDE] "How to Flash" & "From where to Download"
Sent from my GT-I9103 using Tapatalk 2
Thanks for everyone for the tips. I did flash XWLP2 yesterday, the screenlock situation is the same (no mather what i set, not working) however the 3rd party locker apps seems to work now. I did try a few times and it looks the alarm can work together with the locker app so at the moment it looks like the problem is at solved to a level where I can live with it
I do continue to experiment, strange no one came accross this problem. Also interesting and don't know why happening, there is no welcome screen at fresh install at ICS and I think that is part of the problem. It starts and GB and there the lock working fine. On ICS the system just loading like it was loaded before or something.
dodoka313 said:
Thanks for everyone for the tips. I did flash XWLP2 yesterday, the screenlock situation is the same (no mather what i set, not working) however the 3rd party locker apps seems to work now. I did try a few times and it looks the alarm can work together with the locker app so at the moment it looks like the problem is at solved to a level where I can live with it
I do continue to experiment, strange no one came accross this problem. Also interesting and don't know why happening, there is no welcome screen at fresh install at ICS and I think that is part of the problem. It starts and GB and there the lock working fine. On ICS the system just loading like it was loaded before or something.
Click to expand...
Click to collapse
if you can then flash MIUI locker for the same. it has tonnes of themes for locker & has great theme.
Here is mine
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still not working 100% but i'm getting there one thing came to my mind, is there any ICS firmware with .pit and other files? i just use md5 file in pda at Odin, maybe thats causing the problem (which doesn't make sense since the GB software is md5 too but im desperate to find a solution).
I do found flasher+pit file in sammobile, odin 1.87 and a pit file was in the package but not sure I can use .pit and md5 file without the modem and csc...
Lock screen working (go locker now) but still the alarm clock not always working or if it does start few minutes +- as set and snooze not working at 50% of the time..
Buddy pit files are for advanced users who want to play around with their partition table. It could mess up your partitions if you don't know what you are doing. Be careful.
The-Droidster said:
Buddy pit files are for advanced users who want to play around with their partition table. It could mess up your partitions if you don't know what you are doing. Be careful.
Click to expand...
Click to collapse
Yes buddy, I did that with my Samsung Galaxy 3 aka apollo (indian version with i5801 like i9103 for R). I have changed it with Europe's Galaxy 3 ( i5800). Hence my warranty void for life time.
Buddy go to the SSC then.
They will solve this problem for sure
Only if your phone is still under warranty
Sent from my GT-I9103 using xda premium
what is it happen ?
---------- Post added at 12:47 AM ---------- Previous post was at 12:43 AM ----------
what is the slove choice
I just received a notification of a system update for my Galaxy S4 i337M (Bell) running Danvdh's Google Play Edition ROM. It states...
This software will upgrade your Samsung GS4 Google Play Edition to Android 5.1 ( LMY470.S008), which address the security vulnerability. To apply this update you must have at least 500MB free on your device
Click to expand...
Click to collapse
I googled around but have not seen any information regarding the S4 GPE receiving Android 5.1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT:
Do not attempt to install this update, it will soft-brick your device
A working GPE ROM is released, see here
Android 5.1 - Which Address the security vunerability[sic]
I got this update as well. Curious to know if its authentic and if it will have any effect on my ROM if I install?
TheFirstEskimo said:
I got this update as well. Curious to know if its authentic and if it will have any effect on my ROM if I install?
Click to expand...
Click to collapse
I just got this update, too. I actually have the GPE S4, but I'm using SamuraiHL's Lollipop image and I've rooted it to remap a hardware key and install a couple of root-only apps.
Assuming this is legit, which I'm guessing it is at this point, can I install it while I have root?
It seems like installing this on a non-GPE phone would be a bad idea, but I'd wait till a dev weighs in on that question.
I got this too on M-919 on Muniz_ri's gpe rom. I will upload the update..zip once I get some WiFi.
I wanted to ask about how to install this update . I clicked the Restart and Install button and it went to recovery. Do i have to flash the downloaded file? or is that it?
Arslan-Ahmed said:
I wanted to ask about how to install this update . I clicked the Restart and Install button and it went to recovery. Do i have to flash the downloaded file? or is that it?
Click to expand...
Click to collapse
The stock recovery would have installed this automatically. I am not sure if the custom recoveries can do it.
AFAIK after you reboot it will still be the old rom and you might have to manually flash it.
Please upload when you get the chance
violentmagician said:
I got this too on M-919 on Muniz_ri's gpe rom. I will upload the update..zip once I get some WiFi.
Click to expand...
Click to collapse
My s4 is currently stuck on the boot animation. I tried wiping the cache and then wiping data/factory reset and i still have the same problem. Been stuck for hours on the boot animation. Please upload the update so I can try reflashing. Thank you.
Will
---------- Post added at 03:31 PM ---------- Previous post was at 03:18 PM ----------
Or if someone can run aLogcat and view the actual link where they downloaded the OTA file. It should look something like the following:
I/system_update( 2620): [676,200,13946686,<http>android.clients.google.com/packages/ota/global_samsung_i9505g/******************.zip]
blurv89 said:
My s4 is currently stuck on the boot animation. I tried wiping the cache and then wiping data/factory reset and i still have the same problem. Been stuck for hours on the boot animation. Please upload the update so I can try reflashing. Thank you.
Click to expand...
Click to collapse
I am sorry for the delay. I was leaving for work when this update hit. I will upload in a couple of hours at lunch time.
PS. Can someone recommend a good file host for this?
blurv89 said:
My s4 is currently stuck on the boot animation. I tried wiping the cache and then wiping data/factory reset and i still have the same problem. Been stuck for hours on the boot animation. Please upload the update so I can try reflashing. Thank you.
Will
---------- Post added at 03:31 PM ---------- Previous post was at 03:18 PM ----------
Or if someone can run aLogcat and view the actual link where they downloaded the OTA file. It should look something like the following:
I/system_update( 2620): [676,200,13946686,<http>android.clients.google.com/packages/ota/global_samsung_i9505g/******************.zip]
Click to expand...
Click to collapse
This happened to me last night too. The update took almost 30 minutes to apply, and then I was stuck on the flying dots after a reboot. Clearing cache and factory reset did nothing. I eventually resorted to digging up the previous stock image and dropping it back on via Odin. Let me know if a second attempt works for you. Tempted to move on to a custom rom, now that I'm fresh off of a factory reset.
ngeran said:
This happened to me last night too. The update took almost 30 minutes to apply, and then I was stuck on the flying dots after a reboot. Clearing cache and factory reset did nothing. I eventually resorted to digging up the previous stock image and dropping it back on via Odin. Let me know if a second attempt works for you. Tempted to move on to a custom rom, now that I'm fresh off of a factory reset.
Click to expand...
Click to collapse
On what device model?
Five stars on the attempt! :good:
ngeran said:
This happened to me last night too. The update took almost 30 minutes to apply, and then I was stuck on the flying dots after a reboot. Clearing cache and factory reset did nothing. I eventually resorted to digging up the previous stock image and dropping it back on via Odin. Let me know if a second attempt works for you. Tempted to move on to a custom rom, now that I'm fresh off of a factory reset.
Click to expand...
Click to collapse
Anychance you have a link to the stock image?
Goresplasher said:
On what device model?
Five stars on the attempt! :good:
Click to expand...
Click to collapse
GT-I9505G. S4 GPE purchased straight from Google a couple years ago. It had been running nothing but stock, OTA-delivered images until I had to reload last night, so I was really shocked to run into a soft brick with an OTA update.
I may have been running a bit close to the required 500MB free on my device prior to the upgrade. I didn't check, and I figured if I didn't have enough room, it would tell me.
I see on another thread that there's now an Odin-compatible image of the upgrade available, so I may give that a shot myself later, if I have the time. Worst case scenario is I have a repeat of last night, and another long morning of app synchronization.
---------- Post added at 09:01 PM ---------- Previous post was at 08:52 PM ----------
blurv89 said:
Anychance you have a link to the stock image?
Click to expand...
Click to collapse
Disclaimer: I didn't use the image from the forums here. I found it elsewhere, but due to my noob-ness, I can't post the external link. So... I haven't tried either of these, but I have to imagine the 5.0 image is exactly (more or less) what I put back on my phone last night.
5.0 Stock (equivalent to previous OTA image):
http://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-5-0-0-i9505gueudnl3-restore-t2971638
5.1 Stock (equivalent to OTA-pushed image):
http://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-5-1-i9505gueudoh2-restore-t3198093
Odin's interface is a little imposing, but really not difficult if you follow the directions to the letter.
OTA Update.zip link
Sorry for the delay. Here is the link to the update.zip
Sorry cannot post a link directly.
https: //www .dropbox .com /s/52724w0ui3ie4wb /LMY470.S008.zip?dl=0
Has anyone has any luck with the OTA working for them?
Before I go and flash this onto my M-919 (T-Mobile i9500/9505 I'm still not sure which hardware I have under the hood...) Thus I would really like to know if anyone has had any luck with this other than to have their device go into 'Spinning Dots Mode...'
Thanks in advance,
Jeff Means
Was able to reflash via odin the stock image on the i9505g xda thread. I am now running 5.1 on my s4 GPE.
Same Boat
Hey,
I'm in the same situation, but have not proceeded with the install.
Is it recommended to install the update? Or do I wait for the ROM to provide an update (which would presumably perform the same update)?
Thanks.
Failed Update
I tried to do the update by dropping the zip file on my sd card and installing from TWR but the installed failed right away. It looks like I'll just be ignoring this system notification 20 times a day for a while
I just uploaded the upload.zip yesterday. I will experiment with it tonight to try and get it to a working rom since this is my daily driver.
I will post a guide if I manage to get it working for me.
I also receive an error when updating with the OTA update. Also the one uploaded here didn't help.
The error message I receive is "/system/bin/ddexe" has unexpected contents E: Error in /cache/update.zip (Status 7).
Does anyone have any suggestions? Would using ODIN maybe solve the problem?
http: //s16.postimg.org/sns0y03qd/IMG_20150911_225016.jpg
I also have this update nag since yesterday, im running Kangapop V. 2.5 so i have yet to even try installing this.
But also phone keeps saying the "Restart" as it will automatically install? Is this true? Dont want to brick this phone if it can be avoided.
Thanks
I'm trying to determine if a battery issue is a software or hardware issue and I've searched for the correct procedure to Odin to Stock Firmware.
Sammobile.com (as do other Search results) says to only Flash the AP using Odin 3.12.3 - Other sources say to Flash AP, BL, CP and CSC (Searching also provided two different recommendations for which CSC to Flash - CSC and Home_CSC. Home_CSC from Search results indicates that it Home_CSC will not wipe data?).
I'm currently running an AOSP / LOS based Rom.
Thanks
Sent from my SM-N9005 using Tapatalk
Flash everything with ODIN 3.12.3 minimum, choose CSC or HOME_CSC,
CSC will wipe, which will likely be needed coming from custom
HOME_CSC won't wipe
Pretty sure, in fact completely sure all this info is posted here multiple times and easily found with a search
*Detection* said:
Flash everything with ODIN 3.12.3 minimum, choose CSC or HOME_CSC,
CSC will wipe, which will likely be needed coming from custom
HOME_CSC won't wipe
Pretty sure, in fact completely sure all this info is posted here multiple times and easily found with a search
Click to expand...
Click to collapse
Yes Thanks I did Google search and XDA search - The results from XDA include numerous other devices
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And Google search also didn't include only the S7 and most search results were pretty outdated.
I'm also on the latest Bootloader and Modem for my Carrier - Which is in part why I was wondering about Sammobile.com instructions to only Flash AP.
Sent from my SM-N9005 using Tapatalk
shaggyskunk said:
Yes Thanks I did Google search and XDA search - The results from XDA include numerous other devices
View attachment 4153891
And Google search also didn't include only the S7 and most search results were pretty outdated.
I'm also on the latest Bootloader and Modem for my Carrier - Which is in part why I was wondering about Sammobile.com instructions to only Flash AP.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
Hi mate
Not sure what you want to do? is like a factory reset with out doing a factory reset?
AP is your system and apps ( not DATA , where user apps , data and pictures are)
CP modem
BL bootloader
CSC enables carrier specific options (WIFI calling , VoLTE)
you could flash AP alone and should restore system as it was before BUT user apps will still be there and is not a 100% factory reset , this would be similar to what @*Detection* mention almost a factory reset
you are root and have TWRP right?
Make a nandroid and after that make a factory reset and see how it behaves....if is the same you can always restore your back up in a short time.
Another approach to battery problems , is to install an app like BBS
https://forum.xda-developers.com/showthread.php?t=1179809
Let it run for a few hours and check the logs to really see what is going on
MAX 404 said:
Hi mate
Not sure what you want to do? is like a factory reset with out doing a factory reset?
AP is your system and apps ( not DATA , where user apps , data and pictures are)
CP modem
BL bootloader
CSC enables carrier specific options (WIFI calling , VoLTE)
you could flash AP alone and should restore system as it was before BUT user apps will still be there and is not a 100% factory reset , this would be similar to what @*Detection* mention almost a factory reset
you are root and have TWRP right?
Make a nandroid and after that make a factory reset and see how it behaves....if is the same you can always restore your back up in a short time.
Another approach to battery problems , is to install an app like BBS
https://forum.xda-developers.com/showthread.php?t=1179809
Let it run for a few hours and check the logs to really see what is going on
Click to expand...
Click to collapse
Hi MAX - Perfect Clarity as always!
I'm trying to rule out any hardware issues - ie: is the battery or anything related to charging on the device the reason for odd battery behavior - for example the phone was on the charger over night and showed 100% but when I unplugged it the battery drop down to 55% after a reboot it went up to 97%... I've been experiencing this on different AOSP / LineageOS based Roms. Although this behavior isn't consistent...
Yes I'm Rooted with TWRP (Thanks to you & @*Detection* for sorting me out with TWRP on the S7).
I've been using BBS & Wakelock Detector for a long time on my devices and I'm not seeing anything out of the ordinary on the S7 from my apps - I've also tested in Safe Mode and checked the battery charging while in TWRP Recovery (occasionally the S7 doesn't seem to want to charge unless I reboot - but in Safe Mode & Recovery it does which somewhat rules out a hw issue).
Your answer to my question regarding Flashing Odin to Stock is exactly what I was looking for!
The Note Series was a little different and a little more straight forward
Thanks Again!
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
Hi MAX - Perfect Clarity as always!
I'm trying to rule out any hardware issues - ie: is the battery or anything related to charging on the device the reason for odd battery behavior - for example the phone was on the charger over night and showed 100% but when I unplugged it the battery drop down to 55% after a reboot it went up to 97%... I've been experiencing this on different AOSP / LineageOS based Roms. Although this behavior isn't consistent...
Yes I'm Rooted with TWRP (Thanks to you & @*Detection* for sorting me out with TWRP on the S7).
I've been using BBS & Wakelock Detector for a long time on my devices and I'm not seeing anything out of the ordinary on the S7 from my apps - I've also tested in Safe Mode and checked the battery charging while in TWRP Recovery (occasionally the S7 doesn't seem to want to charge unless I reboot - but in Safe Mode & Recovery it does which somewhat rules out a hw issue).
Your answer to my question regarding Flashing Odin to Stock is exactly what I was looking for!
The Note Series was a little different and a little more straight forward
Thanks Again!
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
Mate nothing is straight forward wit Samsung ...there is always a twist somewhere
Now i get what you are trying to , the AP solution is an option also what *Detection* suggested could work .
If the AP approach does not give you the expected results you can flash with Odin AP , CP , BL and home_csc but it has to be the same CSC as you have now in the phone ( check with phoneinfo app) , this will keep your User data but will replace everything else.
A more drastic option would be to use CSC ( not home_csc) and select re partition in Odin ( CSC contains the PIT) this will reformat all partition on the phone.
Let us know how it goes
MAX 404 said:
Mate nothing is straight forward wit Samsung ...there is always a twist somewhere
Now i get what you are trying to , the AP solution is an option also what *Detection* suggested could work .
If the AP approach does not give you the expected results you can flash with Odin AP , CP , BL and home_csc but it has to be the same CSC as you have now in the phone ( check with phoneinfo app) , this will keep your User data but will replace everything else.
A more drastic option would be to use CSC ( not home_csc) and select re partition in Odin ( CSC contains the PIT) this will reformat all partition on the phone.
Let us know how it goes
Click to expand...
Click to collapse
Well this is an update.... It's truly bizarre! I haven't Odin to Stock... AND for some inexplicable reason my battery issues have disappeared... I haven't changed anything on my S7 - Same Apps - Same Everything!
The phone charges normally - I don't have it flicker on and off when the battery percentage is at any level (it used to flicker on and off near 90% +-).
I don't have any explanation for this - But I'm very happy ?
Thanks again @MAX 404!
Sent from my SM-G930W8 using Tapatalk
shaggyskunk said:
Well this is an update.... It's truly bizarre! I haven't Odin to Stock... AND for some inexplicable reason my battery issues have disappeared... I haven't changed anything on my S7 - Same Apps - Same Everything!
The phone charges normally - I don't have it flicker on and off when the battery percentage is at any level (it used to flicker on and off near 90% +-).
I don't have any explanation for this - But I'm very happy
Thanks again @MAX 404!
Sent from my SM-G930W8 using Tapatalk
Click to expand...
Click to collapse
Thanks for letting us know...
But i must say.......odd
Oh well lets hope is gone for good , only time will tell
PS what did i tell about the "Samsung Twist"
MAX 404 said:
Thanks for letting us know...
But i must say.......odd
Oh well lets hope is gone for good , only time will tell
PS what did i tell about the "Samsung Twist"
Click to expand...
Click to collapse
Yes it makes no sense at all... I could see if I Flashed a different Rom - Gapps or Kernel - But I didn't change anything - I probably rebooted the phone a few times but that shouldn't make any difference now since I've rebooted - Wiped Caches - Factory Reset etc previously.....
I just really wanted to avoid taking a device that doesn't turn on in for warranty service / exchange ?
Sent from my SM-N9005 using Tapatalk
shaggyskunk said:
Yes it makes no sense at all... I could see if I Flashed a different Rom - Gapps or Kernel - But I didn't change anything - I probably rebooted the phone a few times but that shouldn't make any difference now since I've rebooted - Wiped Caches - Factory Reset etc previously.....
I just really wanted to avoid taking a device that doesn't turn on in for warranty service / exchange
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I do not thing it will be that bad as you have to take it to service , to me seems as a software issue it does not "feel" like a hardware thing, feels like some orphan file misbehaving .
Last resource before thinking about hardware , flash with Odin , select CSC and select re partition......format all partitions and a totally clean installation.
Before that you can always try to format ( not wipe) your DATA partition......
MAX 404 said:
I do not thing it will be that bad as you have to take it to service , to me seems as a software issue it does not "feel" like a hardware thing, feels like some orphan file misbehaving .
Last resource before thinking about hardware , flash with Odin , select CSC and select re partition......format all partitions and a totally clean installation.
Before that you can always try to format ( not wipe) your DATA partition......
Click to expand...
Click to collapse
For the moment it's behaving properly - and it has been for a couple of days now. I almost always Factory Reset - Advanced in TWRP - Manually Wipe System - Data and Caches before I Flash a Rom - So the System has been Formatted countless times in the last few weeks.... But If it starts to misbehave again I'll follow your advice
Sent from my SM-N9005 using Tapatalk