Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
powerkatwedel said:
Hi,
I have a rooted VZW S3 and have been running Jelly Beans build 20 for a while now. Wanting to give a 4.3 rom a try I loaded up MOAR 7.1. Wiped everything, I possibly could without wiping my SD card. Flashed the rom, no problems. Booted it up, no problems. Then if I do a reboot, even after it has sat for a while without me doing anything to it, I get stuck on the Samsung SIII screen. I can do a battery pull and go to TWRP then wipe and get back to my Jelly Beans, but I'd like to give MOAR 7.1 a try. Any help would be appreciated.
Thanks.
Click to expand...
Click to collapse
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Yeah I have the latest build if twrp and I think I already has the correct Mode from a prior rom. I didn't even check to verify guess I got too excited. I'll check and report back. Thanks.
buhohitr said:
Make sure to use the latest TWRP and did you install ML1 modem like instructed so?
Click to expand...
Click to collapse
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
powerkatwedel said:
Well I didn't have the ML1 modem so I wiped everything clean, installed the modem, then the rom. Got the same result.
Click to expand...
Click to collapse
Any other ideas that may be causing this?
powerkatwedel said:
Any other ideas that may be causing this?
Click to expand...
Click to collapse
Here is another user solved the issue, take from the thread:
"What I did was upgrade my recovery with Goo, I removed the SD card, I wiped the internal memory (not sure if this is necessary but what the hell), factory wiped, installed 7.1, once the phone booted up I logged in to gmail, let it sync, didn't install anything else and rebooted just to make sure it reboots fine, and it worked. Then I installed all my apps with TB without data, just the apps. That is what I did. I had the same problem as you for two days and was frustrated but then I read that if you upgrade your recovery it would work fine. I am assuming you are trying to wipe cache and it is telling you that it can't be mounted, that is another problem I was having, so I am assuming that by wiping the internal memory it cleared that problem up. I hope this helps you out. Hopefully someone here can either back up what I am saying or call me crazy and help you out. Good luck."
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Lehocki said:
What kernel are you installing? I had similar problem trying to install with LK. But that is just my phone not playing nice with it unfortunately (nothing wrong with LK) try DKP or KT.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
powerkatwedel said:
I have tried LK and the Stock and was still getting it. I was able to get it to install last night finally and work, but now my WiFi isn't working.
Click to expand...
Click to collapse
I was never able to get the WiFi to work, so I switched roms and was able to get everything working on Wicked. Thanks for all the help.
Related
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
phillyphill39 said:
where did you get cm10 for the vzw phone? I thought it was for all of the other phones but vzw? Try going back to stock non root. try flashing the modems in the thread about this one.
Click to expand...
Click to collapse
if you go to goo app its in his folders of roms i beleive. i have tried that. i switched to my wifes sim card and got same results, so must be something on the phone
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
Flash the stock tar.md5 from here: http://samsung-updates.com/device/?id=scH-i535
Whatever you flashed put a custom kernel on there, and that's why you get that message.
pitmanr2003 said:
I tried to flash cm10 rom and it never would get past starting apps. I used the new recovery that I beleive beans had reated to install cm9. Then when I tried to reboot i got the verizon non authorized software message. I went back and odin back to root66 and could not get network connection. i have tried factory reset and doing over and over again with now luck. does anyone know why its not letting me on network
Click to expand...
Click to collapse
I don't mean to be rude, but development is not for questions
timothydonohue said:
I don't mean to be rude, but development is not for questions
Click to expand...
Click to collapse
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
pitmanr2003 said:
no offense taken, but with only one question and answer section and that for all cell services could make this question a little different
Click to expand...
Click to collapse
I have d2hackers cm10 up and running on my device...click link in sig!
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
pitmanr2003 said:
i have tried new modem and fully stock rom. no luck. I was running dual boot before that if that could of caused issue. I am lost now.
Click to expand...
Click to collapse
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
pitmanr2003 said:
I am lost. i have tried everything and i am now where a beginner when it comes to android. Im afraid that if i take it back they will see it has been rooted.
Click to expand...
Click to collapse
wipe data then odin a factory stock image
droidstyle said:
wipe data then odin a factory stock image
Click to expand...
Click to collapse
tried that still wants to roam.
pitmanr2003 said:
tried that still wants to roam.
Click to expand...
Click to collapse
I have tried to odin stock and then wipe. still showing no data connection, and same thing when I put my wifes sim in. IM thinkiing it has something to do with the dual boot i had set up before. is there a way to repartion the internal sd card or emmc?
This seems to be happening to a lot of people flashing AOSP ROMs....this is why they warn you they are not responsible for what happens to your phone...especially with Betas.
There are many threads on this and several on how to get a workaround until someone figures out how to fix this.
Try doing a search on losing IMEI or roaming after flashing CM10...it is happening a lot...that is why I am just using rooted stock with VZW apps and TW frozen.
this problem I was having with no data or radio in CM10.
I used ODIN to go back to stock rooted (root 66).
When I did that I was boot looping in the puking rainbows 4GLTE boot animation.
I eventually figured out how to fix that by booting into recovery (press volume up, home button, and power button at the same time till phone boots). I then did a wipe data/factory reset.
My phone then booted fine into stock root.
I then proceeded to punch in *2767*3855# into my dialer immediately when I got stock root working. That did some sort of a factory reset / format. It all happened so quick I could barely read what it told me. The phone rebooted after a while.
I then downloaded EZ-Recovery for VZW Galaxy S3 app from the Play store.
I installed the custom recovery from Dhacker's CM10 post over on the droidhive forums using EZ recovery.
I also downloaded the CM10 file to flash and the Jelly Bean Google Apps file.
Rebooted into recovery, Wiped data/cache/dalvik.
Installed the CM10 file.
Installed the Jelly Bean apps.
Reboot.
Profit.
I now have a largely functional CM10 (as far as I can tell there are some camera issues). Data 3G/4G is working, so are calls and text and everything is dandy.
Did the *27 bla bla thing posted above and back to normal. Thanks everyone
Sent from my SCH-I535 using XDA App
I tried to install the latest and greatest version of cyanogenmod this morning but once it got to the activating part, it would not activate. I tried it a couple times, rebooted, wiped, installed and tried again, but nothing was working.
So, I had enough and wiped everything and restored my previous ROM's backup (CleanROM).
But now, even CleanROM can't connect to the mobile network. When I try to do the *228 thing, I first got an error something about a invalid SIM card. So, I rebooted and now the error message says "A Verizon Wireless SIM card has activated your service and updated your phone's roaming capabilities".
What's weird about that is that it doesn't even call, just pops up that message and I still have no network!
Could it be possible that have the wrong radio now? Anyone know what it's supposed to be and where to download the correct one?
Right now: I535VRLG7
What the f happened? What did cyanogenmod do to my phone??? Please help, my phone is dead in the water at this point.
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
NeoMagus said:
Was it 10.1.0.1? I tried flashing it myself and data would not work either, first time ever happened to me since running CM. Apparently others are having issues with it as well reading the thread on the dev section. I restored my backup of 10.1.0 and it was fine again thankfully. Also you aren't supposed to *228 on a 4G phone, might want to do a search but others have said that can mess up your phone as well.
Click to expand...
Click to collapse
Yes, that's the version I was trying to install.
I created a backup of CleanROM that I was running before flashing, but that's not working now either. Network is dead for me.
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Jerniganc said:
I am having the exact same issue. Flashed the newest "stable" build of CM 10 and now the phone won't activate. Flashed CM10 RC5 and phone won't activate. Installed my backup I made before I flashed and it will not make/receive calls either. I tried searching the g+ community but did not see anything.:crying:
Click to expand...
Click to collapse
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
I'm having the same issue. What Baseband are you guys running?
Laxidasical said:
I'm having the same issue. What Baseband are you guys running?
Click to expand...
Click to collapse
I'm on I535VRBMB1, but I was on I535VRLG7 for some reason. Upgrading did not help.
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
I hope I don't have to do that also. I posted in the cm g+ community and I'm waiting on an answer atm. Jumped in irc chat but got no help.
Sent from my Nexus 7 using xda premium
---------- Post added at 06:48 PM ---------- Previous post was at 06:36 PM ----------
ned4spd8874 said:
I've tried a bunch of stuff so far, but no luck fixing this. I'm waiting for some files to copy and I'm going to try again. This sucks. I'll post if I have any luck with a fix.
Click to expand...
Click to collapse
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Jerniganc said:
Found this post on G+. Looks like it is a known issue that a radio didn't make it into the build.
https://plus.google.com/110116306685366816729/posts/2wnDGwd9UtX
Click to expand...
Click to collapse
But I've flashed the radio and it didn't work for me. I tried two different ones and neither worked.
ned4spd8874 said:
Welp, going to have to Odin back to stock. Nothing has worked. It's dead. Time to bring it to stock and have Verizon fix or replace it. Thanks cyanogenmod!
Click to expand...
Click to collapse
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Well an update on this. I flashed MIUIv5 found here http://forum.xda-developers.com/showthread.php?t=2232800 and it booted up and worked like a champ. From there I booted back into CWM and wiped, etc and installed a fresh RC5 and gapps. When the phone booted up the phone would take calls but would force close. From here I booted back into CWM, again wiped and then installed my RC5 backup I made this morning that was working and crossed my fingers. Well when the phone booted up it is working 100%!
I guess my question is what did 10.1.0.1 break that a flash to MIUIv5 fix?
Same issue. I had to wipe everything, format everything (maybe wasn't needed), flashed the newest nightly, latest baseband (something something F1), and gApps of course. I then had to check the "mobile network" settings and change it to SIM card (instead of NV) then reboot, and it worked.
The "stable" builds have been less stable than the nightlies lately, dunno why...
i'm also having this issue guys, I've noticed that my imei is 0. I've tried punching in the codes to get the utility, but can't get anything working...totally lost
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
ned4spd8874 said:
RESOLVED!
It was a PITA, but I got 4G back with CM!
This is how I did it, but be forewarned that your device will be wiped, and it will not be a quick fix.
I first used this post (Section 5) to Odin back to stock.:
http://forum.xda-developers.com/showthread.php?t=1762709
Once I was back to stock, the network was still not working. So I dialed "*2767*3855#", it did something, rebooted and then 4G worked!
After that, I was able to follow the same guide from above (Section 1) to root the device, unlock the bootloader and install a recovery.
Once I was at that point, I installed CM from recovery. I had wanted to install the cm stable version 10.1.0, however I failed to copy that to my SD card before I started this whole process.
I had just moved and don't have many of my "tools" (i.e. sd adapters), so I couldn't even download it on my computer and copy it over. Oh, I also performed a factory wipe at this point as well as format the davlik and system...oops. So, yeah, couldn't simply boot it back up easily to copy the files over...got ahead of myself.
Anyways, I kept my fingers crossed and installed the only one that was on the sd card which was the nightly from 6/29. The good news is that worked!
I have since installed the latest nightly (6/30), because why the heck not? I was already on the previous, so it "shouldn't" hurt, right????
Nope, didn't hurt!
So, now I am running the latest nightly with full network access!
Whew, what a pain! Hope this helps you guys!
Click to expand...
Click to collapse
Yes, this just worked for me..however I look to be roaming completely when still in Stock
luniz7 said:
No need to take your phone back to verizon.....The way to fix it is to Odin back to I535VRALF2. Once stock dial *2767*3855# let it do it's thing when it finishes reboot. After that 4G will be back. Re root and flash CM 10.1.0 NOT 10.1.0.1
Click to expand...
Click to collapse
This worked for me.
Thanks!
I'm on vacation and tried to flash 10.1.0.1 and got hosed on the the radio connection. Nothing would work. Found an old nightly, 6/21 I believe, on my external SD card. Flashed that bad boy and I'm up and running again. Will do more trouble shooting when I get home in a few weeks and have my PC in front of me.
Sent from my SCH-I535 using Tapatalk 2
Back to RC5
I had a similar issue, upgraded to 10.1.01 and lost all data connectivity. Wiped clean and tried to upgrade again, then I could not get past the network activation screen.
Wiped and went back to a backup of RC5 and it restarted with less issues, but I still needed to go and correct the Mobile Network RUIM/SIM settings before I got data back.
RC5 has been solid, so I'm going to stick to it until there's a fix for 10.1.01.
this didnt work for me
So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Shamrock13 said:
So my phone just prompted me to install the latest update. How do I stop that!? I don't want a locked bootloader, no root, and no ability to do anything!
Help quick as you can!
Click to expand...
Click to collapse
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
mentose457 said:
In TiBu freeze the updater app or delete or rename UpdateBlur.apk in system apps.
Click to expand...
Click to collapse
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
MrMeester said:
Do you have to be rooted to freeze apps? I am rooted but jw. I did when 4.2.2 came out. Then changed to 4.2.2 ROM. Just having problems with custom ROMs. Frustrating.
Click to expand...
Click to collapse
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Ya, cm 10.1 has better bat life. I liked liquidsmooths settings better though. Carbon doesn't seem to be as stable atleast for me. But it seems like no one else is having the problems I'm having. I recommend twrp recovery. Run it, see what you think. PM me if you need help.
Shamrock13 said:
The only updater I see is called Update. Is that the one? I'm not sure if that's it.
You can disable apps in settings, but that's only certain ones and not system services like the updating one.
I want to switch to a 4.2.2 ROM ASAP. Is the CM 10.1 stable as a daily driver with minimum bugs and the same battery life?
Click to expand...
Click to collapse
Yes you are right, it is the update one.
Sent from my DROID RAZR HD using Tapatalk 4
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Shamrock13 said:
What about the ROMs? What are the fastest, most stable? I of course would love to be on 4.2.2 or 4.3.
Click to expand...
Click to collapse
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
I took an xt 925 today, but i have some knowledgment from my Razr I, which is + - the same procedure/flash.
I want to install some custom roms, so basically all i have to do is unlock my bl, install a custom recovery and try out?
I'm asking that, because i'm on jelly bean, but its a carrier based firmware, and i dont know if this model got any limitation which break me up.
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Shamrock13 said:
I apparently cannot get any ROM to install properly. I installed CyanogenMod 10.1, and it worked fine. The phone booted fine, but then I installed another ROM, and I CAN'T get past the Warning Bootloader Unlocked screen at all. I've tried a million times to get into recovery and then I finally do. Then I finally get in there, and I mount system, format twice, and I install a ROM.... Doesn't work. I'm still stuck at the bootloader unlocked screen.
What do I do?!
Click to expand...
Click to collapse
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
mentose457 said:
First off, don't mount system. When you flash it will automatically mount it. You need to wipe cache, and dalvic cache. Generally you also need to wipe data as well. You don't need to wipe more than once. Then flash the ROM.
Sent from my DROID RAZR HD using Tapatalk 4
Click to expand...
Click to collapse
The thing is, I couldn't get back into recovery at all. I had to try like 50 times holding down the buttons to finally get it to even boot to the recovery select screen, and even then it wasn't a sure thing if I were going to get it to boot into recovery. I flashed another ROM, and it still didn't work. I read on the Droid forums that you need to mount system first and then flash, so I tried that and my phone booted up right away.
was kicsnia
mentose457 said:
Cant really comment on the best one. I liked Carbon, PAC and CM10.2 when I tried them. I think most of the kinks have been worked out of the AOSP based roms. Though I usually stick with modified stock roms when not using a nexus device. I usually have the best luck, stability wise, with them.
BTW I love your avatar. I watched that movie all the time when I was a kid. :highfive:
Click to expand...
Click to collapse
Yeah, the brave little toaster! Old school and under rated. Ha ha!
Disable Moto Services. No root, no unlocked bootloader needed. You will never see any update nagging. Even when you turn off/on your phone.
Sent from my DROID RAZR HD using xda app-developers app
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
intelligentduck said:
Hi, I just tried flashing cyanogenmod on my us cellular galaxy s3, and I ran into a problem. I followed a great youtube tutorial on how to flash cyanogen, and everything went fine. the tutorial used goomanager, and was done only using the phone, no computer. I flashed the rom after backing everything up through titanium, and everything appeared to be working like it should. After the flash was complete, the cyanogen animation popped up on my screen, but as soon as it finished loading, two messages popped up: setup wizard has stopped and goo.apps has stopped. I would hit okay, but the two messages just kept popping up. I restored my stock rom, but id still like to flash cyanogen and I need to know what I need to do to prevent this from happening again and how to restart the flash process. Any help would be greatly appreciated!
Click to expand...
Click to collapse
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Trozzul said:
before you flashed the rom did you wipe data and cache? you might also be on the nightly version, try looking for the stable version, and if its on 10.1 its on 10.1, theres nothing you can do but wait for it to become stable if it isent already.
Click to expand...
Click to collapse
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
intelligentduck said:
Everything was wiped. what I think happened was when I backed everything up, I didn't set titanium to not restore my app data, causing a bootloop. I could be very wrong about that though. What I need to know is how to reflash it, as I have already tried to but when I do it brings up system recovery instead of reflashing. Is it because I already tried flashing it once? and if that's the case how do I start from scratch? Oh, and I did flash the stable version. it was 10.1.2
Click to expand...
Click to collapse
might want to try flashing a stock rom via odin cause it sounds like you have stock recovery now, i dont know if anyone will pick you up in the q&a section, since yours is us cellular i dont think they have a forum for that specific contractor just only t-mobile at&t and verizon would have one. you can ask them in their q&a but tell them your situation and that your on us cellular. good luck mate. if ya have any questions just ask right here.
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
CoolWolf22 said:
Hi. I recently installed Liquid Smooth (Unofficial) 4.3 onto my Skyrocket. Since install, if I reboot the phone it will get the ever dreaded Black Screen Of Death. The only way I've found to fix this is to clear the data partition in my recovery (TWRP updated to most recent version) and then reflash the ROM and the gapps. Any ideas on how to keep the BSOD from happening again? I've tried everything I can think of. I tried just wiping the dalvek, cache and system and then flashing the ROM again. As I said, the only way I can find to "fix" it is to wipe the data partition and then flash the ROM and gapps again. I would have asked in that specific thread, but since I am a new member I can't until I reach the 10 post requirement.
Click to expand...
Click to collapse
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jondroid2 said:
Try using the latest CWM recovery. Some people are reporting having better luck using this for the BSOD issue.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
CoolWolf22 said:
I will try this and will get back to you. I'd still like to know what's causing the issue in the first place. I've been flashing on Samsung devices since the original Epic 4G launched. Never have had any issues like this before.
Click to expand...
Click to collapse
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
jd1639 said:
I've had the same issue and switching to cwm solved it. It's a real pita though as a prefer twrp and my nandroids are twrp. I switch back and forth between them.
Click to expand...
Click to collapse
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
CoolWolf22 said:
CWM fixed my BSOD. I've had 2 successful reboots so far. I too preferred TWRP over CWM. But oh well. I am in contact with the devs for TWRP to see if they are aware of the issue and can issue a fix for it.
Click to expand...
Click to collapse
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
theesotericone said:
There's an build of TWRP 2.7 that I've been using and haven't had any issues with. The only thing "wrong" with it is it only reads internal storage. Here's the Link
Click to expand...
Click to collapse
Thanks. I'll download that and keep it in reserve for future reference.