Black screen on boot...flarg - Verizon Samsung Galaxy S III

Hey all,
Working to get Wallet going on my Verizon S3 and I am running into a snag. I booted into recovery using latest CWM Recovery and realize I had the zip file in the wrong spot so I restarted. After the Samsung logo and Galaxy logo display the screen goes black and does nothing. I can pull the battery and boot it again but it just does the same thing. The only thing I have changed, file wise, is the build.prop but this has never been an issue when booting on any of my other phones. Any ideas? Is this phone hosed?
Rooted stock rom

goinovr said:
Hey all,
Working to get Wallet going on my Verizon S3 and I am running into a snag. I booted into recovery using latest CWM Recovery and realize I had the zip file in the wrong spot so I restarted. After the Samsung logo and Galaxy logo display the screen goes black and does nothing. I can pull the battery and boot it again but it just does the same thing. The only thing I have changed, file wise, is the build.prop but this has never been an issue when booting on any of my other phones. Any ideas? Is this phone hosed?
Rooted stock rom
Click to expand...
Click to collapse
I had the same issue, rooted/debloated stock ROM. Your problem was that you adb pulled/pushed the build.prop file without changing the permissions. Restore a nandroid or reflash stock if you don't have one. The best thing you do if you don't know what you're doing with permissions is just to rename the file, copy it, and change it all in Root Explorer. It'll keep permissions that way. It's really easy to fix, don't worry.

Thanks. Going to flash to stock. I backed up through rom manager but not through nandroid. Wasn't expecting this one. Haha
Sent from my DROID RAZR using xda app-developers app

goinovr said:
Thanks. Going to flash to stock. I backed up through rom manager but not through nandroid. Wasn't expecting this one. Haha
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
It's easy to fix, just take a nandroid next time before you change build.prop to save some headaches. Also, make sure you don't update to the new version of Wallet because it broke my Wallet (not the SE, just the installation) for the time being.

Related

Stuck on white splash screen after disabling su permissions and Superwiping

My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Kurdt Kobain said:
My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Click to expand...
Click to collapse
Hi,
Yes,Superwipe will clear your phone.
This includes the ROM.
Re-flash the ROM,and this will return your ROM,and SU.
Kurdt Kobain said:
My phone is stuck on the white splash screen that displays the HTC logo.
It happened because I’ve been trying to get an app working that requires me not to be rooted. I had tried a few of the “ hide your root” apps from the Market but none worked.
I eventually found a way to get it working by going into system/xbin and disabling all the su permissions.
However after disabling the su permissions I found I was unable to allow the permissions again when attempting to reverse the same procedure.
This morning I tried doing an ARHD Superwipe. I thought this would be similar to doing a factory reset (didn’t realise 4EXT had it’s own factory reset).
After doing Superwipe 4EXT told me I was now ready to flash my ROM. I still haven’t flashed the ROM, instead the phone attempted to boot up but got stuck on the white / HTC screen.
Is it normal procedure that Superwipe will completely wipe the ROM off my phone – hence the reason why it’s now stuck like this (until I flash the ROM again)?
I’m at work right now and don’t currently have the ROM on my SD card.
If I reflash the ROM when I get home will that fix everything?
I’m worried that I might have messed my phone up disabling these su permissions?
I can still get into recovery OK what it matters.
Please help if you can as I am panicking a bit here.
Click to expand...
Click to collapse
I had a similar issue once when i removed superuser accidentally. I flashed a recovery and it fixed the problem and returned me to root. Did you do a backup?
Sent from my HTC Sensation using xda premium
evetsno1 said:
I had a similar issue once when i removed superuser accidentally. I flashed a recovery and it fixed the problem and returned me to root. Did you do a backup?
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
Cheers guys I was hoping it would be as simple as that. I just had a bit of a panic this morning I guess! I've never used Superwipe with previous Androids.
Yeah I did make a backup of my stock ROM before flashing.
So in future is there a more easier way to restore the permisions in su?
Kurdt Kobain said:
Cheers guys I was hoping it would be as simple as that. I just had a bit of a panic this morning I guess! I've never used Superwipe with previous Androids.
Yeah I did make a backup of my stock ROM before flashing.
So in future is there a more easier way to restore the permisions in su?
Click to expand...
Click to collapse
4ext fix permissions in tools menue I believe. You can also hold down on the apk till the menue comes up then go to properties and manually fix them if you know what to set them to.
Sent from my HTC Sensation using xda premium
evetsno1 said:
4ext fix permissions in tools menue I believe. You can also hold down on the apk till the menue comes up then go to properties and manually fix them if you know what to set them to.
Sent from my HTC Sensation using xda premium
Click to expand...
Click to collapse
I found that when I first went to disable them the various permission boxes all showed up no problem but when I went back to restore them the boxes would no longer display anymore.
That's good to know that I should be able to do it via 4EXT. Would also like to know if its possible via the phone itself too as my gf's Android doesn't have 4EXT.
Would it work if I copied the system/xbin/su file before disabling them, maybe store it on my PC, and copy it back again afterwards when I want the root reactivating? I'm thinking no because r/rw is turned off right?
Or if I just reflashed the root again from the PC to phone. Would that work?
Kurdt Kobain said:
I found that when I first went to disable them the various permission boxes all showed up no problem but when I went back to restore them the boxes would no longer display anymore.
That's good to know that I should be able to do it via 4EXT. Would also like to know if its possible via the phone itself too as my gf's Android doesn't have 4EXT.
Would it work if I copied the system/xbin/su file before disabling them, maybe store it on my PC, and copy it back again afterwards when I want the root reactivating? I'm thinking no because r/rw is turned off right?
Or if I just reflashed the root again from the PC to phone. Would that work?
Click to expand...
Click to collapse
I dont think you can get root back by fixing permissions. It is my understanding that root is a two part system. First is a binary and second is a program that interacts with the binary such as superuser or supersu. If you remove either part you lose root.
When I lost root I only lost it because I lost supersu. After losing supersu oil checked for root with root checker and it was lost. I tried replacing it but it didnt work. I had to flash a recovery that had root to get it back or re-root my phone. That is about the extent of my knowledge of it.
Sent from my HTC Sensation 4G using xda premium

[Q] Help with recovery after failed ROM installation

So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Can you check your file system and see if your CWM folder has a backup? It should be Sdcard/CWM or extsdcard/CWM. If not, do you mind flashing another rom or that same rom?
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
2 questions: Which factory image did you use to restore (link to thread)? Did you change the default backup location in CWM (ie, did you backup to the external sd or the internal - internal is default)?
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Didn't unlock bootloader?
I don't know for sure. I unzipped SU plus bootloader file exactly as specified in forums/video. Had no problems until I tried installing that ROM through ROM manager. And forgive me for trying that. I hadn't rooted in over a year. But main problem now is just that I want to recover how my phone was ie settings and set up if possible.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
There is a file in both extsdcard and sdcard with clock work mod back up. I did manage to factory reset and re root, so phone is functional again, just with none of my apps or settings. I have a feeling I'm going to need to un root in order to re receive my JB update too?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
How big are those 2 folders?
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
One is 4.82 gb...so I'd think there has to be a file in there.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That sounds about the right size for a backup. When you go into CWM and do the restore (or restore from external - which ever has that folder, you didn't say) it doesn't show a backup?
What version of CWM are you running?
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
JoeS8705 said:
It's version CWM6023touchvzw.tar.md5. And it's on the external. But no matter which option of restore I choose in the recovery boot, it says file not found.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Maybe after all that flashing and Odin-ing your recovery install got wanked, somehow.
Let's try this: it will re-install the latest CWM, clean and then let's see if it'll recognize your backups.
http://www.clockworkmod.com/rommanager/
download the touch image for the d2vzw (or just click here)
put that in the root of your internal sd card.
Open up terminal emulator on your phone and type the following:
Code:
su
dd if=/sdcard/recovery-clockwork-touch-6.0.2.3-d2vzw.img of=/dev/block/mmcblk0p18
reboot recovery
(partition 18 is your recovery partition)
That'll push the known good CWM to your recovery partition and boot you into it. It won't mess with any sort of data anywhere else on the phone.
Alright, thanks. I'll give this a try after I get back home from work.
Sent from my SCH-I535 using xda app-developers app
recovery
JoeS8705 said:
So after 6 months of perfectly working NON rooted phone, I decided to root my Verizon Galaxy S3. I previously owned a Moto Droid 2 and rooted and had no problems ever. Unfortunately, within hours of a successful root, I made the mistake of downloading ROM manager (since it worked fine on my Droid 2) and tried installing the first listed AOKP custom ROM. It rebooted and did everything that was expected, until it just hung on the boot up screen for over an hour. I then decided to (for better or worse) pull the battery and just boot into recovery. Unfortunately, this brought me to a message from Verizon saying "you are doing bad things, bring your phone to Verizon" (more or less anyway). So I fixed that much by getting the factory image/reboot and installing via Odin. My problem now is it constantly keeps failing/closing android process every minute or so. I can't navigate it long enough to do anything before it fails again and takes me back to lock screen followed by home screen. When I boot to recovery, it says I have no files to restore either, but I KNOWWW for a fact I did a backup through CWM before I did ANYTHING involving any custom ROMs. PLEASE help me! Ask any and all related questions that will help you and I'll do my best to answer them.
Click to expand...
Click to collapse
COuld you possibly link the file you used to get back to stock? i resently tried to root my device and it won't start.
No problem. Once again, I'm at work. I'll post it when I get home though.
Sent from my SCH-I535 using xda app-developers app

Problem (well kind of) after restoring a back up

Here's what's going on. I flashed an aosp rom(all I ever use). Didn't like it and restored a previous rom I had backed up(I do this all the time). After the restore was done or so i thought the phone just rebooted and wouldn't load anything past the Samsung screen just black and then reboot followed by the same thing. I pulled the battery loaded up recovery manually and tried another backup I had and same thing. I finally ended up going back into recovery manually again and loaded up a rom. It worked but now the phone won't wipe I forget what it says when I try to wipe. Iv since loaded up several roms with the same wipe errors and all seems good. Just weird. I'm using twrp btw. Any ideas on what happened?
Sent from my Galaxy Nexus using Tapatalk 2
djj624 said:
Here's what's going on. I flashed an aosp rom(all I ever use). Didn't like it and restored a previous rom I had backed up(I do this all the time). After the restore was done or so i thought the phone just rebooted and wouldn't load anything past the Samsung screen just black and then reboot followed by the same thing. I pulled the battery loaded up recovery manually and tried another backup I had and same thing. I finally ended up going back into recovery manually again and loaded up a rom. It worked but now the phone won't wipe I forget what it says when I try to wipe. Iv since loaded up several roms with the same wipe errors and all seems good. Just weird. I'm using twrp btw. Any ideas on what happened?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Well, if you're GS3 is running then I wouldn't worry too much. However it couldn't hurt to make a nandroid, restore back to stock, and redo the STOCK>root>unlock>flash recovery>flash rom process. You may have messed something up along the way. Either way, happy flashing. PS: you should try out paranoidkangdroid if you love the AOSP experience. CM base with a ton of tweakability.
Anybody else ever experience anything like this?
Sent from my SCH-I535 using Tapatalk 2
A thought.... I flashed a wrong kernel once, I would see the boot animation, then black screen. Maybe you have a wrong kernel?
Sent from my PACmaned SCH-I535

odd black screen after every boot/reboot ?

i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !

[Q] Help, I deleted my stock rom by accident

This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
poppers162 said:
Uhhhmmmm would flashing the modems help? (directed towards the more knowledged users)
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
It might. It depends on what modem they are currently on
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
apcake said:
This is my first post and I'm not sure where to put it but I hope this is right.
I'm kinda new to flashing ROMs and was trying to flash one using safestrap on my GS3. I couldn't find one that worked and went back to my stock ROM. In the stock ROM cell service completely died and wouldn't work, to combat this problem I removed all ROMs, ROM slots, and wiped the stock ROM cache. Nothing. So then I restored to my nandroid backup I made yesterday and that deleted my OS. Now when I boot it just gets stuck at the second Samsung boot logo (there the first one that just says "Samsung" and "unlocked", then the second on says "Galaxy SIII" or something) now I have no OS and I'm not sure how to fix this, can I get some help please?
Okay, I got the stock firmware installed but I still have no service anywhere. Any ideas?
Click to expand...
Click to collapse
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
BadUsername said:
First thing I would do is make sure your imei is still present in the about phone section. If it is, move on to the next step.
I would go completely back to stock, Odin flash either the stock 4.3 or 4.4 image depending on which you were on. If you're unsure, post what it says in download mode.
If you do that and you still have no service, then go to verizon and get a new sim card. Flashing a new modem wouldn't fix this situation.
Click to expand...
Click to collapse
it appears as though the sim was wiped
apcake said:
it appears as though the sim was wiped
Click to expand...
Click to collapse
Grab a new sim card.

Categories

Resources