Related
*READ BELOW FOR A GUIDE TO FIX*
I've had my note for over a year now and i have had it rooted pretty much the entire time. Never any problems with it up until recently it started doing this thing where it would keep restarting. It would boot up and less than a minute later just restart. Off and on for a few days it was doing this. I was still running 2.3.6 at that point. So i decided to push 4.0.4 via odin since kies didnt support the firmware. Everything was working fine for a few hours then all of the sudden "the ring of death" showing me no service. Went through the phone and noticed it was saying there is no sim inserted. Tested sim on another phone. Works fine. Since then ive figured out via kies i can recovery and update firmware. Tried that. No Bueno. Now im to the point where im on 4.0.4 with no service. I've scoured through forums trying all kinds of different things, pushing different roms and modems via odin and cwm. Still no bueno.
Baseband version
Unknown
Kernel Version
3.0.8
Build Number
IMM76D.UCLF6
If anyone can give me ideas im willing to try them out.
Thanks.
I got it working so heres a direction for anyone else who has this issue!
Replaced Sim&SD card reader-No fix
After flashing all kinds of roms & modems still same issue saying no sim inserted.
Do a hard reset through your settings.
Flash cwm and put the radio from this link on your sd card. Use cwm to flash the radio.
Flash rom http://forum.xda-developers.com/showthread.php?t=2261598 via odin.
The first try i got an error during flash and got stuck on the software download error screen.
Reflashed the JB rom.
After its flashed flash clockwork recovery.
Enter cwm and do a factory reset. Clear cache. Clear dalvik cache. Reboot system.
If you get service, turn off phone. enter cwm and do a backup.
Reboot system.
It should be working.
If not restart and make sure to do a factory reset through your settings in the phone before reflashing rom.
Got the Phone up and running for about 30 mins.
After battery removed it reverted back to no sim card inserted.
Kept reflashing rom until it worked again.
Flashed cwm.(ClockworK recovery mod)
Deleted cache, dalvik cache
Backed up via cwm
If it reverts back to no sim after that restore using the cwm backup.-it worked for me
Now for the tricky part, my phone was getting crappy service...
So heres what i did to fix it.
Settings-more settings-mobile networks-access point names-click on the apn.
Name-
ATT Phone
APN-
Phone
Proxy-
Not set
Port
Not set
User Name-
Not set
Password-
Not set
Server-
Not set
MMSC-
http://mmsc.mobile.att.net
MMS Proxy-
proxy.mobile.att.net
MMS Port-
80
MCC-
310
MNC-
410
Authentication type-
None
APN type-
default,admin,fota,mms,supl,hipri,internet
APN protocol-
IPv4
Enable/disable APN-
(check mark)
Bearer-
Unspecified
Hope this helps anyone else having this issue.
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
440bro said:
I believe I've read something like this before. I think they fixed it by starting over from scratch. Try returning to stock thru Odin. Then root and flash rom of choice.
Click to expand...
Click to collapse
I Started from scratch via "kies emergency recovery".
No luck.
dweeezy said:
I Started from scratch via "kies emergency recovery".
No luck.
Click to expand...
Click to collapse
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Stuck power button. Your pants are too tight.
Theoriginalgiga said:
did you try rolling back to GB? it could be a bad port on your phone. that was my problem.
Click to expand...
Click to collapse
i ordered a new sim port to see if that works. what is gb?
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
dweeezy said:
i ordered a new sim port to see if that works. what is gb?
Click to expand...
Click to collapse
GB stands for Gingerbread which was the first version of the OS that came with the phone. I believe the number was 2.3.6 (you can take a look in the about section in the settings and it'll tell you what you're currently running). ICS is Ice Cream Sandwhich which for our phone was 4.0.4 i believe. Jelly bean just came out today which you can use Kies to upgrade to and that I believe is 4.1.2. The numbers don't really mean a think, just the classification of what the OS is so if your phone reads something else (say 2.3.4) assume your phone is right and I'm wrong. I can't remember OS versions to save my life haha.
But you can use Kies to do an emergency recovery and I THINK it'll install Gingerbread. that's where I'd start, then test it, and then move to ICS and test, and then move to JB and test. I know long tedious process, but sometimes it's necessary. Imagine how fun I am to talk to on the phone while troubleshooting a computer :laugh:
redman9 said:
Same situation...finally went to ATT and had a "new" phone sent under warranty. Of course NOW I'm pulling my hair out trying to migrate everything over to the new phone. I rooted and every ROM I try and install aborts. **** me. I don't even know where to start anymore
Click to expand...
Click to collapse
what I use to migrate, and I between roms at least once a week with a full wipe because I rely on my phone being stable.
SMS and call logs: SMS Backup + (saves your call logs and sms to your gmail account. Makes a label for it and everything, pretty sweet. You can also restore from it. it takes about an hour for me to restore at 7000+ text messages).
pictures/media: stored on SD card
apps: if rooted and rommed I use titanium backup and run 2 sets. those which I want to keep my data like sms backup + to make restore easier and those I don't care about the data like google voice. If you're stock, just remember to check the little box in the beginning saying backup this phone to google (or something like that) and the next time you have to restore tick the box that says restore from google (or something like that) and it'll reinstall your apps. Mind you not the info, but it'll give you a head start.
As with your issue with installing roms. If you're using CWM i highly recommend switching to TWRP, not saying it's better in fact I like CWM better, but TWRP is the best for our roms and phone. If you have no clue what I mean by CWM or TWRP, read the all info sticky about how to rom thy phone.
I hope that helps.
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
redman9 said:
Thanks OG. Yes, I know CMW and TWRP. I used to switch ROMs a lot. Finally stuck with Collective's latest (the orange one) pretty happy with it except that it's major glitch seems to be reboots whenever an app updates. So I figured unchecking auto update in Gstore should handle that.
You're saying I should try rooting w Odin again, install Superuser, then use TWRP to flash with? I'll be happy to read another 4 hrs of posts/stickies if that'll get me sorted out. I don't expect people like yourself to spend your day helping me. I'm very thankful for your tips here.
I've poured thru the "All things Gnote" threads and Noob Guides. They can be confusing as they always link out to many different threads. There is hardly ever a "Here are the steps 1. 2. 3. 4. 5.
Thanks again OG.
Click to expand...
Click to collapse
No problem always happy to help. since you're used to this sorta thing you don't need to use odin again and reroot. What you can do is either install TWRP through CWM using this file here:
http://goo.im/devs/OpenRecovery/sgh-i717/openrecovery-twrp-2.5.0.0-quincyatt.zip
Or you can install Goo manager, click settings and select Install OpenRecoveryScript (though that's only 2.4.4.0 the link above is 2.5.0.0)
That should change you over to TWRP. and like always do a nandroid backup and then flash to your heart's content!
fixed!
dweeezy said:
fixed!
Click to expand...
Click to collapse
How ?
galinha said:
How ?
Click to expand...
Click to collapse
i have the same issue.....i kn0w its n0t an hardware issue....my ph0ne is fairly new never dr0pped and this started happening 3 days after i p0rted black star jb alpha
I have this same issues ive tried flashing everything ive tried a new sim and replaced the card reader.
What works consistently for me if to flash the latest modem everytime i have to reboot or boot the note. Its my daughters phone now and she drains the battery regularly if it boots after charging or it needs to be rebooted for whatever reason it will come up with the no sim card error. If i flash the modem thru recovery it will work for that boot but only as long as I dont reboot or shut the phone off, then i will have to flash the modem again.
Not fixed
All. This is not fixed. I am having the same issue and if you follow the guide, it works for a day maybe regardless of what rom is loaded or what modems. Has anyone found a real solution to this yet??
i717 running stock GB or ICS or JB roms...
Thanks!
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Kraize said:
I have the exact same issue. Replaced the sim/sd card slot and still no dice ): Flashed to stock and back. Nope. Still won't work
Click to expand...
Click to collapse
I'm having the same problem. There seems to be no set way to get it back to working. Basically any reboot of the phone produces a no sim card error. I have tried flashing the modem through recovery as it was mentioned that will fix the problem. That did not work for me. What does work, sometimes, is one of the following:
1. Full wipe and reinstall
2. Restore backup from Recovery
3. Fix permissions
I just keep doing one of the above listed and eventually it works. However if the phone reboots then it's back to the carousel of trying these options to get it back to working.
I'm running Padawan JB V2
I honestly have no idea what's causing it. I haven't tried to fix permissions before to fix this issue, but if I go into recovery and install the modem again and reboot, it works fine for a while (and by a while, I mean like a few hours at max).
Just started having this issue, myself...after flashing Tmo_SGH-T989_VKL1_radio_ATTNOTE.zip modem on my phone...restoring from a prior backup...
Restoring a backup will not change your modem.
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Heatshiver said:
First, make a NANDROID if it is working perfect on the stock ROM. This is my first step after root and recovery so that I can always fall back on something to check if there is a hardware problem, or just some sort of (system) file problem. Plus, it'll save you time if you have to go back.
Not sure that it matters, but is the stock ROM odexed, or deodexed?
The calling thing reminds me of when you use the phone overseas but it has yet to be unlocked. When you root, do you check with Root Checker? Do you have SuperSU installed? How about BusyBox? I know some items require BusyBox in order to work, but SuperSU should be installed.
As far as SuperSU, do you update it before switching back to the original kernel? One thing I noted is to be absolutely sure you do so in order to not lose your root when completing the rooting steps. I imagine this could cause other problems too.
I also suggest not using TWRP 2.6, which many people will tell you is quite buggy. Best to use the previous version.
The only other things I can suggest is ALWAYS doing a full wipe of everything before adding a new ROM. I used to do this to be sure I incurred no problems on my SGS3, because if I didn't there would always be something buggy happening.
Hope this helps.
Click to expand...
Click to collapse
Thank you, Heatshiver!
I always do a full wipe unless I'm doing a dirty flash for a ROM update. I will try reverting back to TWRP 2.5.0.2 (Whichever version that happens to be, I think it's .0.2) tonight and report my results. Also, just to clarify, I always make sure I have the most updated SuperSU/Superuser (Usually the former) and BusyBox.
I appreciate the suggestion.
-Travis
teemunknee said:
Hi all,
Long time lurker of XDA and Android user/modder since before Gingerbread. I want to apologize in advance if this post is either in the wrong section, and/or if something similar has already been answered/solved in another thread. I did multiple searches with nothing coming up as a direct hit, or even close for that matter.
I recently purchased an S4 from VZW (Mid-Late July). I rooted and installed TWRP 5.2.0.2 (Forgive me if that's not the exact version...) and flashed AOSP ROMs here and there. After a month or so, I started coming across an issue within all ROMs where I couldn't receive or make calls without my phone either freezing or rebooting. Anything I flashed, or modded, failed to remedy this. I tried different GApps packages, 4.2.2 and 4.3 ROMs, different kernels, and both radios, and absolutely NOTHING solved this. I searched everywhere (Even rootzwiki, forgive me fellow XDA members!), and could not find anyone with the same issue.
I attempted upgrading to TWRP 2.6.0.0 and even tried CWM, and that didn't help either. Eventually, things got so bad that I couldn't boot into ANY ROM, 4.2.2 or 4.3. After nearly 10 hours of trying to unbrick my phone, I finally managed to install Beanstalk 4.3, and while it was working incredibly buggy (Not Beanstalk's fault, the developer is a great developer!) nor could I make calls, I could still send texts and emails. I was able to FINALLY get the Odin3 application to work when I got home from work, and was able to flash the stock MDK image. From there I followed the steps to properly root and install TWRP 2.6.0.0. I installed Slim's Beta 5 4.3 ROM and GApps and everything was working properly! Calling, everything! However, when I made a reboot, it froze. Stuck in the "Samsung Unlocked" screen for over an hour. I pulled the battery, booted into recovery and did a factory reset/cache and dalvik wipe. It still didn't boot. From there I did a full wipe, and data format, installed Beanstalks newest 4.3 ROM and GApps, and everything loaded properly. Then I couldn't make or receive calls without the same issue. I then did the superwipe/format and installed PAC's newest nightly and GApps package, and was able to make calls, but then got stuck when rebooting, even after factory resets and cache/dalvik wipes. After multiple attempts, I gave up and reflashed the stock MDK Samsung image in Odin3 and am leaving it as is until someone here can help me.
I know this post was incredibly wordy, and I apologize for that, but I wanted to give you guys as much information as possible and explain where this all started, as it may lead to why I'm having these problems. I appreciate any and all responses and I will answer any question any of you have to the best of my ability. Please someone save me from the horror that is TouchWiz!
-Travis
Click to expand...
Click to collapse
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
As much as I love AOSP, I would have to agree with the poster above. I know TW is a pain but there are some pretty good ROMs in that flavor that you shouldn't have any problems with. I've had the no call issue on AOSP, and even though they are nice and free up quite a bit of room it's not worth missing calls over or constantly flashing. Maybe once our bootloader is unlocked things will become different but I'd stick with TW until that happens. I can confirm that TWRP 2.6 is very buggy...you'll have to download the 2.5 version and flash it instead of goomanager they install they latest version everytime I believe.
andybones said:
sorry for your troubles, but I am always baffled the way people just toss that word "brick" round
Your phone was no anywhere NEAR being a brick...
You simply are playing with fire flashing AOSP ROMs and not knowing how to fix the issues.
AOSP ROMs aren't technically "made" for our phones, the developers do a great job at making it seem like they are, though.
On the SG3 we had an EFS backup that Synergy discovered incase you flash an AOSP and get stuck in roaming which was quite often at first with AOSP, that was easy to fix, but with this phone I would be careful with AOSP ROMs, even myself, with a locked bootloader wouldn't flash anything besides TW, although I am biased as AOSP is my flavor.
I am sorry if this post comes off harsh or any other bad word. It's not meant for that..
Just to kindly ask you to do some research on what a "bricked phone" truly is.
it's a brick.. meaning won't power on, won't get a light when charging, nothing, your phone is just that, a $600 brick. and the only way to bring back to life IIRC is Jtagging the phone.. which requires taking the phone apart and jtagging the motherboard.
I hope you the best my friend.
Click to expand...
Click to collapse
Next time, I'll just say "Soft-bricked". Thank you for your reply.
-Travis
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
slim6596 said:
You also may want to try CWM recovery if everything else fails. I like TWRP but I kept having the exact problem you have. I switched and haven't had a problem since.
Sent from my SCH-I545
Click to expand...
Click to collapse
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
I also forgot to mention that I haven't been able to connect to 4G radios since before I started having issues with AOSP ROMs. Currently I'm on Eclipse's TW (With AOSP Styling) ROM. Everything appears to be working fine, other than 4G.
I've tried the SIM pull and reset, and nothing. I've tried manually setting it to LTE only, at least when I was able to do so when AOSP ROMs would boot for me, and nothing. I have a Galaxy Nexus that I booted up with this SIM in and I get 4G signal. Any Ideas?
Also, when I was on the stock image (MDK) I didn't have 4G either.
Has anyone else run across this issue? (MODS: Let a me know if I should create another thread, or search more intensively. I haven't seen a thread with this exact same situation. Plenty of 4G issue threads, but none with the same issues I've previously had, and I think it may have something to do with my past modding.)
-Travis
teemunknee said:
Would you mind telling me which version of CWM you're using? I haven't gone back to CWM since I went back to stock two nights ago.
Thank you for the idea!
-Travis
Click to expand...
Click to collapse
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks! I installed CWM 6.0.3.6 Touch and flashed Eclipse's TW/AOSP ROM and everything works well, but it's still no AOSP ROM.
-Travis
Hi all,
I'd like to thank everyone for the suggestions.
An update: Currently I'm on Eclipse's TW v2.0 ROM (TW, with AOSP Styling) and everything works properly. My current recovery is CWM 6.0.3.6 Touch, and I'm not experiencing any booting or calling issues. 4G is the only thing I don't have working.
I'm hoping that someone with my same problem can give me another idea so I can get an AOSP ROM working, preferably with 4G. I'm sure some, if not most, understand my dislike of TouchWiz and strong preference towards stock Android/stock Android based ROMs. Slim6596 said that he uses Philz Modded CWM Recovery and has no issues anymore. Could that really be my solution?
Again, thank you all for your help and ideas. I love XDA for this reason.
-Travis
slim6596 said:
Philz touch modded CWM. Don't have a link though. Sorry.
Sent from my SCH-I545
Click to expand...
Click to collapse
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
teemunknee said:
Hi Slim,
Sorry to bother, but I was curious if you were specifically using the LOKI patched version, or just the regular version?
-Travis
Click to expand...
Click to collapse
Loki patched, I believe.
Sent from my SCH-I545
slim6596 said:
Loki patched, I believe.
Sent from my SCH-I545
Click to expand...
Click to collapse
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I have stuck to TW ROMs. Pretty soon I'm probably not going to be flashing anything. Switching to Motorola and giving Vz my MDK S4 back. (Reception and dropped call issues.)
Sent from my SCH-I545 using Tapatalk 2
teemunknee said:
Thanks!! I installed the Loki-Patched version last night.
I tried flashing two AOSP ROMs, but have no radio signal at all. I'll experiment.
-Travis
Click to expand...
Click to collapse
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
egore93 said:
I believe you have to do the extended phone function. Its a code on the dial pad and select cdma. I have read this but don't recall where.
Sent from my SCH-I545 using Tapatalk 4
Click to expand...
Click to collapse
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
teemunknee said:
Are you referring to the *#*#4636#*#* dialer code? I didn't even try that because in my settings, everything was set to CDMA, but that's something I can try. I have everything backed up, so I can just wipe, install, and try that. If it doesn't work, I can always revert back.
Thanks for the suggestion!
-Travis
Click to expand...
Click to collapse
Yes that's it give it a go.
Sent from my SCH-I545 using Tapatalk 4
I don't know what happened. Or why it won't work.
When Safestrap was originally finished, I installed Hyperdrive without a problem. An update came, I downloaded and installed. It made it so I couldn't use HotSpot anymore. So, I figured it was the Rom, and I installed Jellybean Rom. I didn't like it. I tried to install the original Hyperdrive I had, and once its installed and reboots, the lights come on for one second and shut off. Downloaded the newest Hyperdrive, same issue.
The instructions say wait for 10 minutes. I did, and longer. (Range usually 20-40 minutes)
Last night I wanted to try again, (downloaded newest hyperdrive. I have sloooooow internet. Took 5 hours to finish). So, I tried installing today following the instructions, same issue. It installs and says everything is fine, reboot, safestrap pops up, loads normally through that, and the lights are on after like it starts with Stock, lights shut off, phone stops working.
When this happens, the phone does not respond to anything. Power does nothing. I waited 45 minutes the 3rd time trying to reboot after install. The phone will not turn on, respond, or anything unless I pop the battery out and put it back in. I can get back into Safestrap that way.
I really want to use Hyperdrive, but it just won't reboot for my phone.
I do have the Verizon i545 version, ME7, Safestrap, Rooted, and newest Hyperdrive Rom. Used the Safestrap Kernel, but the phone locks up.
I've tried default settings, different Rom settings, (2gb and 3gb), removing almost everything from install, adding what I want, adding what I like, etc. No combination of settings will let me phone boot into Hyperdrive.
Any thoughts?
Are you completely removing then re-creating the slot when trying all these flashes?
Are you flashing the ME7 kernel module.zip ?
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
I redo the rom slot each time and act like it's the first time.
And i can't install the module... Tried multiple times but it fails almost instantly through ss.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Have you tried to re-download the module? Preferably on the computer then transfer to your ExtSDCard with the ROM.
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Excessumcarcer said:
So... The one I downloaded to my computer failed, but the one I did with my phone worked.
Still the same issue. Won't boot past the SS message.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
While you were trying to install did you notice if zip signature was checked if so uncheck when you install and uncheck when you install module other than that don't know what else to say. When i first started i found that to be my problem.
The zip signatures were not checked. : /
Sent from my SCH-I545 using xda app-developers app
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Excessumcarcer said:
And I've tried the older version Hyperdrive with the new ME7 Modules, still won't work. I can't understand because everything says it was successful and ready to go, but it just doesn't.
Also double checked my i545 version, it is still ME7 and not the new one. The new update is pushy and wants to be installed more aggressively than the ME7 did. Highly annoying...
Click to expand...
Click to collapse
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
!Led*Eyes! said:
Get off 3.62 and go back to 3.6 if you can. use root uninstaller to get rid of the current SS and shut down normally. ( all in stock rom ) reboot to stock recovery and factory reset. put the 3.0 SS back on and install twrp through that and reboot fully. then you can go into SS and reboot to recovery and you should be good
EDIT: go back to 3.6 SS not 3.0 haha
EDIT 2: always wipe even after you just created the slot and flash the modules with HD10 and advanced wip the dalvik and the cache only. and chill for 10 and boot her up..... and make sure you didnt accdentally get the dreadful OTA!!!
Click to expand...
Click to collapse
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
!Led*Eyes! said:
FINAL EDIT!!! always pick the safestrap kernel during the Aroma install
If I helped at all, shoot me a Thanks and happy flashing!!
Click to expand...
Click to collapse
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Excessumcarcer said:
I promise you this makes no sense....and I think there was something wrong with the stock rom...only thing I can conclude. I did a factory reset and bricked my phone. I can't even get into Safestrap now...whatever the issue was with the custom rom is now the issue with the stock rom. So, i'm just going to wipe my phone and start over from scratch as that is the only available step. Ill let you know if it fixed the issue or not.
Click to expand...
Click to collapse
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
!Led*Eyes! said:
Did you have 3.62? my buddy did and his phone wouldnt let him delete it! crazy. i dont like 3.62 but i was running HDrls10 like a champ. not a single issue. With the me7 base i want to say i didnt even flash the modules over it but i cant remember. but basically ( by what i wrote down) you were going to start from scratch anyway.. there is a better root out now anyway. use the dialer codes and get a REAL factory reset!! There are a lot of people that arent digging the 3.62..... it was causing bootloops for a while but there are def still some lingering issues i think.
Click to expand...
Click to collapse
Well...nothing has worked.
Update for everyone, I was using the older SS, 3.60.
I killed everything, put the original Verizon ME7 Rom on the phone, re-rooted, put 3.62 SS on, (Done like it), installed the HDrls10, Installed the module, (both successful), restarted, exact same thing. Right after Safestrap Enabled pops up, the phone goes dark and the battery needs to be removed and put back in for it to turn on again.
So, I tried something crazy and for whatever reason it worked as far as HD is concerned...but...I went outside of the instructions.
I have the HD rls9 Final. I installed it through SS, used the modded Kernel, (non SS), and restarted. It popped right up in about 45 seconds. (Wasnt working before I reset everything and started over)
I tried HD rls10 Final that way, and nothing.
I will be redownloading it tonight to make sure it isn't the download. (I have slow internet, itll take all night likely.) : /
If anyone is looking to actually uninstall SS (which you need to do to roll back a version) you need to use the commands hashcode has provided. Using Terminal Emulator on the stock side will accomplish that. Read up on hashcode's SS OP.
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Excessumcarcer said:
My phone will not accept HDrls 10....no matter what I try. It accepted HDrls9 without issue, minus the hotspot not working. But it will not accept HDrls10...
Im out of ideas...
EDIT: I downloaded the HDrls 10 rom from two locations, tried both, both failed this morning.
Click to expand...
Click to collapse
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
lazer9 said:
All I can think of is somehow you are getting bad downloads. Have you checked the MD5s to match per the download sites listing?
Click to expand...
Click to collapse
I just double checked the MD5. It matches the download. How frustrating. Double checked the build, double checked the MD5, double checked install procedure, etc. It flat doesn't work on my phone, and there is no logical reason to it. I tried from a fresh build twice now, doing the rooting and SS install from stock everything.
It locks up right after SS, still.
Electronics hate me, it has been determined before. This is just further proof.
: /
So, I've done pretty much everything feasible. Guess Ill have to stick with an older HD or different rom. : (
Also, hotspot doesn't work HD 9 for me, (nor Jellybeans). I installed the module when I did the rom, but there is no hotspot for one. And two, when I download and use FoxFi, which I paid for to use on the Stock Rom before SS, it will try to turn it on and then it freezes and crashes.
All I want is a non-Verizon Rom with working Hotspot!!!! AHHHHH!!!! Looks like that aint happening.
Well played Verizon...well played. Perahps I should get an international phone and go to another company. Expensive, but tempting.
So, the final verdict for those following -
Hyperdrive 10 - Does not work on my i545 no matter what I tried.
Hyperdrive 9 - Works but the hotspot is glitched and froze no matter what I tried.
Jellybean - Works the same as HD 9
Synergy - Works. Everything on it works, hotspot, install, etc.
Not sure why the others did not work. But, for whatever reason Synergy works flawlessly for my i545. Installed and downloaded the same ways as the others, yet it worked.
: /
I was planning on trying a few others first, but Synergy claims to block Samsung from logging information from my phone. I realize this doesn't stop every company from doing it, but its the thought that counts. lol. So, Im trying this Rom out now. It's no hyperdrive, but it works.
After a BUNCH of tries I finally got it to work!!
I have a Verizon i545 with ME7. I basically started as if I'd never installed HD 9.1 in the first place.
Here's what I did.
1. Double check that your device is rooted. I used Root Checker Basic. I actually re-rooted my device just to be sure (I venture to guess it might have been unnecessary) and it worked.
2. I used a 4GB SD formatted to ex-fat and put the HD RLS10 AND the ME7 modules .zip file on it (Both on the SD)
3. I then booted into recovery.
4. Make a new ROM slot.
5. Name it whatever you like.
6. When you go to flash HD, hit the add zip button and select the ME7 modules.zip
7. When HD gets done flashing UNCHECK the "Reboot" box up top and then hit the reboot tab at the bottom right.
8. It will automatically flash the ME7 modules next. When it says 'Successful', then reboot.
9. Give it a few seconds and hopefully it will work for you as well. Good luck.
Latest installable version for Me7?
What is the latest installable version of HD for verizon locked Me7 bootloader, i currently have rls10.0 installed and ive tried 10.1, 10.2, and now 12 and none of them boot up.
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software. I ended up giving up and just kept pushing the OTA off. It got so bad that I decided last night to install a recovery and then flash an unofficial CWM rom. So this morning it was working fine and then all of the sudden, I lost VZW data. Couldn't get any signal. So I decided to try to flash the Official Cyanogenmod 11. That blew up during the setup and gave me an error that it could not find any cellular service. I wiped the phone and tried to restore the backup I made of my stock rom with the recovery on it. I made the backup the second the recovery was finished. It's giving me an MD5 error?? I've tried this multiple times with the same result. So, I then decide to flash one of the two roms (unofficial & official) back to see if I can get the phone working again. No such luck.... It keeps trying to set up my "cellular service" and just runs. Nothing ever finishes. I'm really worried at this point. I would be perfectly fine to flash a Verizon image and go back to stock. But I can't seem to find out how to do this or where to find the file. Please help me.. I'm getting desperate.
Edit: I tired to flash the Unofficial Rom again and this time it seems to be working. I would still rather just go back to stock though. If anyone can point me to the correct place I'd be very appreciative.
Thanks
Dave
Click to expand...
Click to collapse
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
startswithPendswithOOH said:
Here is a link to flash back to stock: http://forum.xda-developers.com/verizon-lg-g3/general/guide-flash-to-stock-10b-kdz-method-t2928140
I know you wanted to take the OTA, but why not download one of the stock based 11c ROM's, like Jasmine 3.0? That way you'll still get the latest version(11c) but you won't lose root and recovery. The OTA patches root, so no recovery either. Here's a link for Jasmine 3.0 stock based 11c if you want to try it: http://forum.xda-developers.com/verizon-lg-g3/development/rom-jasminerom-v1-0-t2904641
Also, there has been issues with data on the CM builds. It seems pretty common right now. Check the CM threads for more info on that. I believe there is a command people have been entering(killall rild in terminal emulator) to get data back, but it seems 50/50 that it'll work.
Click to expand...
Click to collapse
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
dbow32 said:
Hey thanks a lot for your reply. I understand what you're saying with going back to stock. My issues with flashing custom Roms is that I have to have my phone work 100%. I've been flashing since the original Droid Incredible. And I've NEVER found a Rom that didn't have minor glitches and issues. Usually those issues affect my daily routine. I'll give Jasmine3.0 a shot and if it works I might just keep it. If not i'll just suffer through VZW's BS! Anyway, really appreciate your input.
Dave
Click to expand...
Click to collapse
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
dbow32 said:
Ok, I was stock rooted to allow for wifi hotspot. Once I started getting the latest OTA from VZW I decided to try to go back to stock to accept the OTA. I went through all the YouTube video's and loaded the LG software but my phone would never sync to the LG suite software.
Click to expand...
Click to collapse
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
BladeRunner said:
Which drivers were you using? I had trouble with the Unified Drivers linked in some posts and had to use the Verizon specific drivers. I also had to usually reinstall the drivers each time I tried to use the flash tool to get it to recognize my phone.
Click to expand...
Click to collapse
To be honest, I'm not sure what drivers I was using. I did a Google search for LG suite and found the closest version I could find. They didn't have the VS985, Only P985. So that might have had something to do with it.
startswithPendswithOOH said:
Glad to help. I'm with you on the 100% functionality too, so that is why I'm on Jasmine 3.0. Don't get me wrong, I love custom ROMs and all the work the devs do, but until all the kinks are worked out I'd rather be stock.
Also, I'm not trying to advertise anything, but flashing the skydragon kernel into Jasmine has helped the speed/lag and battery life as well. Its worth a try - but it only works on stock/non-AOSP based ROMs. If you try it though, also download the stock 11c kernel that the OP put in the thread just in case you have issues. I don't have the link handy, but the kernel is located in the "original android development" thread. Peace
Click to expand...
Click to collapse
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
dbow32 said:
I have a question, what is the "Modem" for? BTW, this Rom is VERY nice. Thanks
Click to expand...
Click to collapse
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
startswithPendswithOOH said:
Modem is the radio. Some people reported better signal strength on the 11c modem versus the 10b modem, but I didn't notice too much of a difference myself.
And glad you like the ROM, but all thanks go to hsbadr who came up with it
Click to expand...
Click to collapse
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
dbow32 said:
You know, it's really odd but the last few weeks my phone's signal has dropped. I listen to Sirius through my phone during the day at work. And I've always received 1 to 2 bars of 4g. But the last few weeks, It's dropped to about 2 to 3 bars of 3G. I thought maybe VZW was secretly throttling me. But maybe it's the updated Radio?
Click to expand...
Click to collapse
It's possible the modem could've been causing problems. Is 11c better or worse for you? And its also possible big red was throttling you too. That seems like something they'd do.
If you use/like xposed framework G3 tweaksbox is a good app to get for customizing your phone a little bit. And greenify and amplify are good xposed apps that help your battery life a whole lot. They are worth checking out in the play store.
I have had stability issues on marshmallow. I flashed the 35B bootstack and upgraded to the Azadi marshmallow variant. It was working fine, but there had been more updates to the rom, so I flashed those as well (without flashing 35B again). I was getting occasional system reboots, so I switched to the stock 47A firmware (debloated using joshua70448 zip generator). I am still having the same issue - the system randomly reboots, sometimes twice in a row. Also sometimes when I power down, the phone will not power up again until I remove the battery.
I really cannot relate this to any particular situation - it seems to happen at completely random times.
Any help is greatly appreciated.
Did you try what I suggested at the bottom of the reply I sent in the other thread?
http://forum.xda-developers.com/showthread.php?p=66842422
roirraW "edor" ehT said:
Did you try what I suggested at the bottom of the reply I sent in the other thread?
http://forum.xda-developers.com/showthread.php?p=66842422
Click to expand...
Click to collapse
No. Somehow I lost that last sentence in your sig.
So wipe, flash TOT, flash 35B, flash ROM, ???, profit?
B00M! said:
No. Somehow I lost that last sentence in your sig.
So wipe, flash TOT, flash 35B, flash ROM, ???, profit?
Click to expand...
Click to collapse
Flash the 10B TOT, root using the Stump app, use TWRP Manager from the Play Store to install TWRP, wipe Cache, Dalvik/ART and Data, flash the 35B bootstack if you're going to flash a 35B or higher ROM, then flash the ROM.
If you're going to flash a ROM that had a lower version of Android, flash the corresponding Bootstack.
Ok. I will let you know how it turns out.
Is this going to repartition my device?
B00M! said:
Ok. I will let you know how it turns out.
Is this going to repartition my device?
Click to expand...
Click to collapse
I'm not sure what you mean by repartition. It will wipe everything including internal storage. It won't wipe external MicroSD. You'll be back on completely stock 10B, which is easiest to root and put TWRP on.
I thought I read somewhere that one of the updates changed some of the partition sizes, but I guess if that were true, you would know
I was mostly concerned about whether or not my internal storage would be wiped in the process.
Out of curiosity, why do you recommend TOT instead of KDZ method?
B00M! said:
I thought I read somewhere that one of the updates changed some of the partition sizes, but I guess if that were true, you would know
Click to expand...
Click to collapse
Maybe they did, I wouldn't necessarily have noticed.
Out of curiosity, why do you recommend TOT instead of KDZ method?
Click to expand...
Click to collapse
That's answered in my original reply to you in the other thread. Again, just the part at the bottom of my reply.
For anyone who follows this thread:
roirraW "edor" ehT said:
Doubtful, if it's the way you describe it. The only reason I tell people this is because some people ask for help determining when they can get away with not flashing the bootstack again.
It's far simpler to just flash whichever the appropriate bootstack is every time you flash a ROM or restore a TWRP backup. There's just no reason to avoid flashing the right one every time.
If you're experienced enough that you know you don't have to flash it again, then don't. If you're mistaken, you could end up with a temporary brick depending on the exact situation, but it's still not caused by the bootstack.
Also, the wrong bootstack doesn't cause stability issues or reboots. It can cause no signal, not being able to use Advanced/HD Calling and not being able to encrypt your SD card.
....
I recommend flashing the 10B TOT. TOTs flash more partitions than KDZs, as @xdabbeb taught me and I verified. I had a weird problem months ago that wouldn't go away no matter what ROM or KDZ I flashed until I flashed the TOT.
Click to expand...
Click to collapse
This unfortunately did not work. I think I have traced the initial problem to a particular situation. The first crash seems to always happen when I launch navigation. The phone will suddenly turn off and then reboot twice. After this inciting event, the system seems to become unstable and will reboot at random times when I am using it. Is there a way to track what is causing the crash using logcat or something? Any other ideas? I might just have to go back to LP, as I don't think I was having a problem running it.
B00M! said:
This unfortunately did not work. I think I have traced the initial problem to a particular situation. The first crash seems to always happen when I launch navigation. The phone will suddenly turn off and then reboot twice. After this inciting event, the system seems to become unstable and will reboot at random times when I am using it. Is there a way to track what is causing the crash using logcat or something? Any other ideas? I might just have to go back to LP, as I don't think I was having a problem running it.
Click to expand...
Click to collapse
What exactly do you mean by "launch navigation"? If you're on Azadi right now, I haven't used it so I can't particularly advise, although I'm curious if you'd have the problem on a less modified stock ROM, and also curious if you would be able to replicate the problem if you were completely stock unrooted.
Sounds very strange. I haven't had this issue among the ROMs I've used. Currently @xdabbeb 's stock 47A firmware (fully debloated). Previously his VS985 v2.0 (35B) ROM, and previous to that, several versions of JasmineROM up through 9.1 (35B).
I really have no experience with logcats so I can't advise you there.
It's possibly your battery is going bad, as that's been known to cause all sorts of weird issues.
By launch navigation, I mean start a new navigation in google maps. I get to the map just fine, searches just fine, but when I start the navigation, the phone goes black and reboots.
I have had this issue on Azadi as well as the stock 47A version (with debloating as I described in the other thread) both before and after the TOT install. I saved a stock rooted 47A TWRP version during this process, so I could unroot it and see if the problem persists. There does appear to be some relation to the battery, as it will crash and reboot and lose about 10% of the battery in the process. After I plug it in, the battery returns to its "precrash" level. Drain does not seem to be greatly different than before I transitioned to MM.
Again, I really appreciate your help and ideas.
B00M! said:
By launch navigation, I mean start a new navigation in google maps. I get to the map just fine, searches just fine, but when I start the navigation, the phone goes black and reboots.
I have had this issue on Azadi as well as the stock 47A version (with debloating as I described in the other thread) both before and after the TOT install. I saved a stock rooted 47A TWRP version during this process, so I could unroot it and see if the problem persists. There does appear to be some relation to the battery, as it will crash and reboot and lose about 10% of the battery in the process. After I plug it in, the battery returns to its "precrash" level. Drain does not seem to be greatly different than before I transitioned to MM.
Again, I really appreciate your help and ideas.
Click to expand...
Click to collapse
Unrooting a backed up version of 47A wouldn't be the same as actually running the full stock unrooted 47A, not unless you went to a tremendous amount of effort (meaning it's far simpler to flash a KDZ).
I use Maps all the time on stock fully debloated 47A and have done so recently without issue. I'm only saying this because I don't think the ROM is the issue.
I would definitely proceed further with the battery route. Unless there's some tiny piece of detail that I don't know, it's either that or just general hardware failure, but I doubt that.
Just for the heck of it, eject your MicroSD card and leave it out, reboot the phone and do what you can do to replicate the issue while the card's ejected. I hope you eventually solve this, sooner rather than later and hopefully not too much more paintfully.
Alright. Yeah. It has been a PITA trying to get back to a stable setup. I too do not think it is the ROM based on what has happend so far.
The only bit that I haven't mentioned is that the commands are set up through tasker (switches on Bluetooth, launches the apps and starts the navigation). I may try to run the stock, debloated, rooted, 47A rom without tasker next to see if the problem still occurs. This too does not seem like the issue, because sometimes tasker launches everything and it runs well without any crashes. I don't see that anyone is reporting a similar issue in the tasker Google group.
I will keep this thread updated to any progress.
After extensive testing, I am convinced this is a battery issue. New battery is on the way.
No issues after replacing the battery. Life is good again