Related
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.
Thanks I'll check there.
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium
New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...
bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2
matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.
Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.
Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Try flashing the stock tar in odin if nothing else works.
DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok
I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol
fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha
Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Boot in recovery now tgat you flashed stock rom. To boot in recovery press
Volume up+home button+on/off.
When samsung logo appears release the power button.
When it will boot in stock android recovery select wipe cache and wipe whole system (can't recall how it is written). Then select reboot now. That should do it.
Sent from my GT-N7100 using xda premium
mariosraptor said:
Volume up+home button+on/off.
Click to expand...
Click to collapse
That did not quite do it but I feel like a fool right now since this is the first time I realised that I mixed up Volume up and Volume down. But you gave me an option for that factory reset and after flashing CWM on top of that with ODIN it works again. One night wasted on nothing but my own lack of sleep and stupidity.
Thanks!
Good that it is working
Sent from my GT-N7100 using xda premium
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
SenK9 said:
I don't think Perseus supports CM10 at this time.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Anyway, glad it ended well for you OP!
Androssama said:
AFAIK:
Perseus: Samsung based ROMs.
RedPill: Samsung and AOSP.
N.E.A.K. Note2: Samsung and AOPS (AOPS support is only available for the N7100).
Note2Core: Samsung.
Click to expand...
Click to collapse
Thanks! I haven't experimented much with custom kernels and my first try in combination with CM 10 didn't end that well. This gives me something to go from. Also I had a HTC Desire before and just got the Note 2 a few weeks ago, so there is another thing I have to get to know better.
Dude, please note that, for those kernels above which support both Touchwiz/Samsung and AOSP/Cyanogenmod based ROMS, there will be a separate version of the kernel for each.
hdr32 said:
Hello everyone,
As the title says I have a problem with my Galaxy Note II N7105 Lte (Vodafone, Germany)
I flashed the new cyanogenmod nightly one the phone and that was all well and good but then I made the mistake of flashing the Note2Core Kernel on top of if rendering my phone dead. My first Idea was to flash another Kernel on top, as I had some issues with the newest Note2Core Kernel (v3.06 OC) when I was still on my stock rom. I used the Perseus Kernel from this thread: http://forum.xda-developers.com/showthread.php?t=1927852 (I used the correct one for the N7105, so I think that is not the problem.)
What I then did was search the internet for an answer and most of the time I found something like "go enter cwm" but that just wont work and I have no idea why. I can only get into the normal "Download" mode. I tried pushing the 3 buttons from the start and just holding them, waiting for the first samsung logo with the device name and then pressing them and also pressing them and then letting go of the power button as one tutorial suggested. At the end it means I can't go into cwm, which would have been the easy way out.
What I did then was trying to flash the stock rom (from samsung-updates.com) on top of it with odin to get rid of the whole mess but that got me nowhere too. When I start up the phone the samsung logo is back but it is stuck... I left it like that for about an hour just to see if it would work eventually but I am stuck at the logo.
Trying to find out what is going on I entered the "Download" mode again and that confused me a bit there as it says binary SAMSUNG official BUT System custom. Just to see what would happen I flashed the auto root on top of it but that just gave my the notice that my binary was also custom so I went and flashed the official samsung rom on top again to no effect.
I spend the whole night yesterday to find a solution but this is all I got. I assume that cyanogenmod 10 is just not working with another kernel and found that out the hard way.
I would really appreciate help on this matter as I am out of options right now.
Click to expand...
Click to collapse
As long as you can enter DOWNLOAD mode, your phone is NOT bricked. When you **** up your bootloader and stuff, then we can talk...
Hopefully this has taught you how important it is ti actually read up on something before you do it. Not only are the note2core and perseus kernels for samsung based roms only, other kernels such as redpill and neak only support the n7100 for their aosp/cm kernels.
As far as I know there is currently no other cm kernel for the n7105, although there is a neak cm kernel for the n7105 currently in beta testing.
Sent from my GT-N7100 using xda premium
No worries... learned my lesson... Sometimes I just need that smack in the face to get it.
And before I break my bootloader or some similar disaster occurs... I'll read first.
Sent from my GT-N7105 using xda app-developers app
Think we need a sticky with good instructions how to install and make a nandroid backup.
As well as sticky for EFS backup and why its so important to do it first and properly.
I know I had a lot of problems finding this info and implementing it proper,
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
hulslanderam said:
I tried to install a ROM that must have not downloaded properly now my Nexus does not boot at all. It doesn't even go to the Google screen, it's just plainly black. The worst part is that it happened last week and I thought the phone had just broken so I got a hardware swap at Best Buy but now I realize it must have been the ROM. I don't want to go back to Best Buy this quickly (not even 24 hours later...) Does anyone know how I might fix it?
Click to expand...
Click to collapse
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
FIXED
sensation lover said:
If it was a faulty download the rom wouldn't have installed properly, what steps did you take in installing the from. Are you able to boot into recovery?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Awesome!
hulslanderam said:
I installed a kernel too, both from CWM. Maybe it was the kernel. and no, I couldn't get to recovery but I managed to fix it. I can't post links because I'm a new user but it involved installing omap drivers and running a batch file of some sort that made it bootable. Even though the screen was totally black I guess the computer could still detect it with some work.
Click to expand...
Click to collapse
Congrats! That's gotta feel good to resurrect a "dead" phone!
I've tried to use the OMAP flash to fix mine, but I still can't get into Odin mode (even tho the drivers and bat file seem to install successfully). If you have any tips, then please let me know.
Well I've been running cm11 builds for t0lte on my t0lteatt (technically t0ltecan but same thing) for months with no issues. Until the dreaded March 4th nightly dropped. There were over a hundred commits that night, and something broke compatibility with my device. It keeps getting signal, then phone force closes and signal is lost. Then it gets signal, etcetera in an eternal loop. I'm wondering what I could do about this? Could a modem fix this issue? Is there anybody else out there who has been running this ROM on a t0lteatt?
I'm only asking because my device isn't supported by CM11, so I was very happy to find I could run the international build just fine. Now what do I do for CM love??? Aaaagh! Help would be awesome guys, who knows a possible solution?
Sent from my thumbs to your face.
mertin said:
Well I've been running cm11 builds for t0lte on my t0lteatt (technically t0ltecan but same thing) for months with no issues. Until the dreaded March 4th nightly dropped. There were over a hundred commits that night, and something broke compatibility with my device. It keeps getting signal, then phone force closes and signal is lost. Then it gets signal, etcetera in an eternal loop. I'm wondering what I could do about this? Could a modem fix this issue? Is there anybody else out there who has been running this ROM on a t0lteatt?
I'm only asking because my device isn't supported by CM11, so I was very happy to find I could run the international build just fine. Now what do I do for CM love??? Aaaagh! Help would be awesome guys, who knows a possible solution?
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Have you tried flashing the latest drop? cm-11-20140306-NIGHTLY-t0lte.zip
Maybe stuff is unscrewed now. Nightly's are crap shoots.
Only stable releases I see are 10.X. There's a reason for that......
Have you tried any of the hybrid ROMs, like OmniROM or Dirty Unicorns. You can't swing a dead cat without hitting a killer option on those.
Yes I've tried all the newer nightlies too. It is working fine for t0lte users (which makes sense, because it's made for them) which leads me to believe it's just people like me running it on a variant device who are missing out. It works as intended on the proper device, so I don't see why they would change it back. Other ROMs just don't seem as polished and I'm OCD so rough edges are a dealbreaker. Cm11 has bugs, but none that affect my personal usage so that's why it is my daily driver. Thanks for the tip tho I'm still investigating!
Sent from my thumbs to your face.
mertin said:
Yes I've tried all the newer nightlies too. It is working fine for t0lte users (which makes sense, because it's made for them) which leads me to believe it's just people like me running it on a variant device who are missing out. It works as intended on the proper device, so I don't see why they would change it back. Other ROMs just don't seem as polished and I'm OCD so rough edges are a dealbreaker. Cm11 has bugs, but none that affect my personal usage so that's why it is my daily driver. Thanks for the tip tho I'm still investigating!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Well, it's not really different.....
[Q] difference between t0lte and t0lteatt
http://forum.xda-developers.com/showpost.php?p=42038043&postcount=5
Credit T-Macgnolia
dicksteele said:
Well, it's not really different.....
[Q] difference between t0lte and t0lteatt
http://forum.xda-developers.com/showpost.php?p=42038043&postcount=5
Credit T-Macgnolia
Click to expand...
Click to collapse
I also have a t0lteatt running the CM11 nightly for t0lte. I also installed the nightly that resulted in not being able to boot, to solve it I rebooted my phone manually to recovery and installed the previous days back over the top and I fixed it. Then I wait a couple days and tried the next nightly which worked. I am currently running yesterdays (030632014) without issue.
TDLR: the nightly from the 4th left me broken, none of the nightly's before that point ever broke my phone, also none since then have broken my phone.
Good Luck!
Mazamuda said:
I also have a t0lteatt running the CM11 nightly for t0lte. I also installed the nightly that resulted in not being able to boot, to solve it I rebooted my phone manually to recovery and installed the previous days back over the top and I fixed it. Then I wait a couple days and tried the next nightly which worked. I am currently running yesterdays (030632014) without issue.
TDLR: the nightly from the 4th left me broken, none of the nightly's before that point ever broke my phone, also none since then have broken my phone.
Good Luck!
Click to expand...
Click to collapse
Thanks for the help, but it's still broken on my end. (Just tried the same nightly) This is getting really weird. It's happening right away, clean install. Can't get the popup to go away long enough to do anything. Any suggestions what I could try? It's making me mental!
Sent from my thumbs to your face.
mertin said:
Thanks for the help, but it's still broken on my end. (Just tried the same nightly) This is getting really weird. It's happening right away, clean install. Can't get the popup to go away long enough to do anything. Any suggestions what I could try? It's making me mental!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
I am not sure I understand the symptoms, are you saying that it boots up just fine but the phone keeps getting and losing signal? Or is it booting up just fine then rebooting after the phone gets and loses signal?
Welll no matter I would take a full backup of your system and then wipe it clean and install the known working 10.2, just to see if it is indeed a hardware problem. If 10.2 works then maybe take a nother backup of that you can at least swap back and forth while you work on the issue.
Mazamuda said:
I am not sure I understand the symptoms, are you saying that it boots up just fine but the phone keeps getting and losing signal? Or is it booting up just fine then rebooting after the phone gets and loses signal?
Welll no matter I would take a full backup of your system and then wipe it clean and install the known working 10.2, just to see if it is indeed a hardware problem. If 10.2 works then maybe take a nother backup of that you can at least swap back and forth while you work on the issue.
Click to expand...
Click to collapse
Hey thanks for working through this with me, I really appreciate it! What's happening is it boots just fine. But I get the error popup "com.android.phone has stopped". When I hit okay it immediately comes up again. Forever. I also just had a scary missing imei problem happen just now and spent the last couple hours getting THAT sorted out. But now I'm back on the march 1 nightly and everything is just fine. I just can't run anything newer than that and I don't get why.
Sent from my thumbs to your face.
They just posted an M4, maybe that will work?
Sent from my GT-N7105 using xda app-developers app
Mazamuda said:
They just posted an M4, maybe that will work?
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
They did? I don't see it on get.cm?
Sent from my thumbs to your face.
Its on the cyanogenmod.org blog.
Sent from my GT-N7105 using xda app-developers app
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
mertin said:
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Excellent.
Was it TWRP 2.6.3.1 ?? I think that's the one that works with newer ROM builds. At least for me.....
Or ....... Was it the March 8th build ...... Did you flash that in TWRP ?
Also, keep a copy of each on your phone. If one doesn't work just flash the other, then you can reboot to recovery to the other one.
mertin said:
Wooooooo I got today's nightly running (march 8th)!! I had a sudden urge to try a different recovery just to make sure I had tried everything. Installed philz touch, then installed CM. This time it finally worked! I wonder if it was twrp giving me problems all this time. Just so bizarre I had zero issues updating every day for months and then suddenly just couldn't get it working at all.
In any case it seems good for now. Thanks for all the advice!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
That was going to be my next question. I have heard lots of reports of people running CM11 and having problems with TWRP, I use CWM and it has always been rock solid.
Glad your back up and running, enjoy the crack-flashing!
dicksteele said:
Excellent.
Was it TWRP 2.6.3.1 ?? I think that's the one that works with newer ROM builds. At least for me.....
Or ....... Was it the March 8th build ...... Did you flash that in TWRP ?
Also, keep a copy of each on your phone. If one doesn't work just flash the other, then you can reboot to recovery to the other one.
Click to expand...
Click to collapse
It was 2.6.3.1 and I even tried the newer 2.6.3.7 for t0lte and it didn't work. But all good with cwm. There must have been some tiny change that twrp wasn't flashing properly. Whatever it was, just glad to have that behind me!
Sent from my thumbs to your face.
mertin said:
It was 2.6.3.1 and I even tried the newer 2.6.3.7 for t0lte and it didn't work. But all good with cwm. There must have been some tiny change that twrp wasn't flashing properly. Whatever it was, just glad to have that behind me!
Sent from my thumbs to your face.
Click to expand...
Click to collapse
Most excellent. Congrats