I was running Jellybeans 4.1.2 did a factory reset, flashed this 4.3 ML modem, rebooted into the recovery and flashed the Alliance zip. When I I try to start the phone it gets stuck loading the samsung screen and rebooting, I can still boot into recovery by holding the power, home, and volume up and already tried to reflash but I'm still having the same issue.
Should I try an older build or different setting when I set up the rom. The whole set up process works and it seems to install just fine until I try to actually boot the phone.
notaneggspert said:
I was running Jellybeans 4.1.2 did a factory reset, flashed this 4.3 ML modem, rebooted into the recovery and flashed the Alliance zip. When I I try to start the phone it gets stuck loading the samsung screen and rebooting, I can still boot into recovery by holding the power, home, and volume up and already tried to reflash but I'm still having the same issue.
Should I try an older build or different setting when I set up the rom. The whole set up process works and it seems to install just fine until I try to actually boot the phone.
Click to expand...
Click to collapse
Try wiping data and caches in recovery. Then reboot.
Root Wizard said:
Try wiping data and caches in recovery. Then reboot.
Click to expand...
Click to collapse
Tried that twice with no luck, trying to load a different kernal from the set up options and getting stuck at extract:/system/framework/ext.jar for the past 2 hours. If I do anything from here I brick the phone?
Hm, im not sure. But what device are you running?
Sent from my SCH-I535 using Tapatalk
Root Wizard said:
Hm, im not sure. But what device are you running?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Samsung Galaxy SIII SCH-I535 on Verizon.
Can you
enter odin mode?
Sent from my SCH-I535 using xda app-developers app
Root Wizard said:
Can you
enter odin mode?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I can try it I'm just afraid of bricking it.
Well, you can use it to reflash stock JB and stock kernel though....and i know a debrick method that has worked for me when i was bricked.
Sent from my SCH-I535 using Tapatalk
Root Wizard said:
Well, you can use it to reflash stock JB and stock kernel though....and i know a debrick method that has worked for me when i was bricked.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yeah, I can't enter recovery I'll probably have to pull the battery which as I understand will likely brick the phone since I'm stuck 50% into the flash.
Ok try that and tell me what happens.
Sent from my SCH-I535 using Tapatalk
Root Wizard said:
Ok try that and tell me what happens.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Pulled the battery and booted into recovery no problem. Can I got back to Jellybeans 19 or 20 with the ML1 modem, I was on the original modem when I was running that rom.
Ok, good to know!
Sent from my SCH-I535 using Tapatalk
notaneggspert said:
Pulled the battery and booted into recovery no problem. Can I got back to Jellybeans 19 or 20 with the ML1 modem, I was on the original modem when I was running that rom.
Click to expand...
Click to collapse
Yes. You can run any modem with any ROM. Apparently LTE data does not work correctly on the latest 4.3 base unless you have the ML1 modem, though.
I don't see why Alliance ROM isn't booting for you. Was it in an actual bootloop or just stuck on Samsung logo? I know that the first boot after flashing a 4.3 ROM takes extra long. Also a simple battery pull when it's stuck on Samsung logo sometimes works.
If it was in a boot loop you might have had a bad download. Try re-downloading the Alliance ROM zip and re-flashing!
Wait, how are you getting to recovery on an S3 Verizon 4.3?
Sent from my SCH-I535 using Tapatalk
BattsNotIncld said:
Yes. You can run any modem with any ROM. Apparently LTE data does not work correctly on the latest 4.3 base unless you have the ML1 modem, though.
I don't see why Alliance ROM isn't booting for you. Was it in an actual bootloop or just stuck on Samsung logo? I know that the first boot after flashing a 4.3 ROM takes extra long. Also a simple battery pull when it's stuck on Samsung logo sometimes works.
If it was in a boot loop you might have had a bad download. Try re-downloading the Alliance ROM zip and re-flashing!
Click to expand...
Click to collapse
I'm honestly not sure the difference between a bootloop and the samsung logo. The phone vibrates as part of the boot, Samsung logo comes up, vibrate, black screen and repeat.
I'll download the zip again and start over. Should I try the build 21 first for any reasons?
Try an sd card with written boot to it
Sent from my SCH-I535 using Tapatalk
notaneggspert said:
I'm honestly not sure the difference between a bootloop and the samsung logo. The phone vibrates as part of the boot, Samsung logo comes up, vibrate, black screen and repeat.
I'll download the zip again and start over. Should I try the build 21 first for any reasons?
Click to expand...
Click to collapse
The build number does not matter. You should be able to flash anything. What you are describing is definitely a boot loop. I would try to re-download the build 22 zip. What recovery are you on?
BattsNotIncld said:
The build number does not matter. You should be able to flash anything. What you are describing is definitely a boot loop. I would try to re-download the build 22 zip. What recovery are you on?
Click to expand...
Click to collapse
ClockworkMod Recovery v6.0.4.5
Or try downloading a soft brick debricking software on your cpu
Sent from my SCH-I535 using Tapatalk
notaneggspert said:
ClockworkMod Recovery v6.0.4.5
Click to expand...
Click to collapse
That's the latest recovery so you should be good. The only thing I can suggest is to re-download the zip and try again. Make sure you back up your data and factory reset before flashing (wipe data, cache, dalvik).
If that doesn't work you should be able to flash back to your old 4.1.2 build. Did you make a nandroid?
Related
I tried searching, but the search is down?
I have spent several hours looking.
I used odin (phone went into download mode without issue) to put my phone back to stock so I could get the ota update.
Went back into download mode with Odin to install CWM, this "passed" and after a restart my phone went into samsung recovery, not CWM.
Now my phone will not go into download mode? I tried different cable, ports, etc.
any help?
so what is it doing since it's not going into download mode.
it wouldn't do anything, I finally reinstalled the drivers and after holding down the power and volume - let go... nothing! push the volume - twice and it went into download mode. Odin recognizes it and goes through the motion, but the phone has a AX_timeout in red at the top left corner of the screen?
Odin continues and say's passed, but when I try to reboot into CWM it hangs on the samsung logo.
It will not boot into recovery, but it will start the phone and everything seems to work.
im using odin 1.83 / windows 7 64bit.
Remove the battery, put the phone in download mode, put the battery back in, and flash CWM. Before you fully boot the OS, flash a custom kernel. If you don't flash a custom kernel, the default kernel will overwrite CWM with the default recovery.
Morrisme said:
it wouldn't do anything, I finally reinstalled the drivers and after holding down the power and volume - let go... nothing! push the volume - twice and it went into download mode. Odin recognizes it and goes through the motion, but the phone has a AX_timeout in red at the top left corner of the screen?
Odin continues and say's passed, but when I try to reboot into CWM it hangs on the samsung logo.
It will not boot into recovery, but it will start the phone and everything seems to work.
im using odin 1.83 / windows 7 64bit.
Click to expand...
Click to collapse
I would try using odin v1.82... My experience with this tool has told me that our charge doesnt always "play nice" with other versions... Also try redownloading the latest CWM, you could of had a bad download.
Sent from my SCH-I510 using XDA
Cilraaz said:
Remove the battery, put the phone in download mode, put the battery back in, and flash CWM. Before you fully boot the OS, flash a custom kernel. If you don't flash a custom kernel, the default kernel will overwrite CWM with the default recovery.
Click to expand...
Click to collapse
Also in my experience I have had CWM recovery with the stock kernel... So something seems funny, stock kernel must not always overwrite custom cwm... Hmmmm. Who can help us here....????
Sent from my SCH-I510 using XDA
stebomurkn420 said:
Also in my experience I have had CWM recovery with the stock kernel... So something seems funny, stock kernel must not always overwrite custom cwm... Hmmmm. Who can help us here....????
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
If you happen to flash a ROM that doesn't include the script that the kernel calls for the overwrite, then you could have ended up with CWM on a stock kernel.
stebomurkn420 said:
Also in my experience I have had CWM recovery with the stock kernel... So something seems funny, stock kernel must not always overwrite custom cwm... Hmmmm. Who can help us here....????
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
There's a script, can't remember where it's at, that is run at boot to replace the recovery. If that script is not there, it doesn't get replaced. All custom roms have it removed.
shrike1978 said:
There's a script, can't remember where it's at, that is run at boot to replace the recovery. If that script is not there, it doesn't get replaced. All custom roms have it removed.
Click to expand...
Click to collapse
/system/etc/install-recovery.sh
Hmmm... So your saying there basically wasnt a way for me to have cwm with stock rom/kernel with root... I could have swore I had that setup at some point...
Sent from my SCH-I510 using XDA
stebomurkn420 said:
Hmmm... So your saying there basically wasnt a way for me to have cwm with stock rom/kernel with root... I could have swore I had that setup at some point...
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
There is, root, boot up, delete the script power off, re root and you're good
Sent from my DROID RAZR using xda app-developers app
stebomurkn420 said:
Hmmm... So your saying there basically wasnt a way for me to have cwm with stock rom/kernel with root... I could have swore I had that setup at some point...
Sent from my SCH-I510 using XDA
Click to expand...
Click to collapse
There is. You can download the Superuser CWM to your phone, flash CWM, boot immediately to CWM (don't let it boot normally), flash Superuser, and reboot.
At that point, if you desire, you can delete /system/etc/install-recovery.sh and reflash CWM if you want to keep it.
shrike1978 said:
There is. You can download the Superuser CWM to your phone, flash CWM, boot immediately to CWM (don't let it boot normally), flash Superuser, and reboot.
At that point, if you desire, you can delete /system/etc/install-recovery.sh and reflash CWM if you want to keep it.
Click to expand...
Click to collapse
You think this would work on the nexus... Seems its kind of a universal method...?
Sent from my SCH-I510 using XDA
Sorry if this is in the wrong thread, not sure where to put it,
I own a NATPC M009s x2.
I rooted it today and was hoping to install the cwm.
I had to install the driver manually so i tried to install it through the recovery mode
However after I did this the device wouldnt boot up past the boot logo and im not too sure what to do.
Mohan211 said:
Sorry if this is in the wrong thread, not sure where to put it,
I own a NATPC M009s x2.
I rooted it today and was hoping to install the cwm.
I had to install the driver manually so i tried to install it through the recovery mode
However after I did this the device wouldnt boot up past the boot logo and im not too sure what to do.
Click to expand...
Click to collapse
wiping cache shall be helped you.
re-try to re-flash the cwm..maybe you do it wrong.
H.Style86 said:
re-try to re-flash the cwm..maybe you do it wrong.
Click to expand...
Click to collapse
But i didnt try to flash it in the first place, i was just trying to download the android driver for my device
Mohan211 said:
But i didnt try to flash it in the first place, i was just trying to download the android driver for my device
Click to expand...
Click to collapse
What android driver?
Sent from my SCH-I500 using Tapatalk 2
Nevermind I fixed it. Not too sure how but it worked.
Thanks anyway guys!
ndaryruro feudal
Sometimes it's just enough to take out the battery and put it in again
Stuck at boot logo
Hi Friends ,
I was on Slim bean 4.2.1 beta rom but due to some problem i tried to switch back to Stock Roms 4.0.4 using odin but my galaxy r stuck at boot image .Please help
SumitBishnoi said:
Hi Friends ,
I was on Slim bean 4.2.1 beta rom but due to some problem i tried to switch back to Stock Roms 4.0.4 using odin but my galaxy r stuck at boot image .Please help
Click to expand...
Click to collapse
Did you repartician?
Sent from my SCH-I500 using Tapatalk 2
bbrad said:
Did you repartician?
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
No ,Only Auto Reboot and F. Reset Time were checked
SumitBishnoi said:
No ,Only Auto Reboot and F. Reset Time were checked
Click to expand...
Click to collapse
Dude when your coming from a custom ROM you have to check repartician or you have a possibility of permanently messing up your phone lol just out it back in download mode hook it up to Odin and make sure you put the right .pit file in there and the stock files and click rapartician and start
Sent from my SCH-I500 using Tapatalk 2
Stuck at boot logo
bbrad said:
Dude when your coming from a custom ROM you have to check repartician or you have a possibility of permanently messing up your phone lol just out it back in download mode hook it up to Odin and make sure you put the right .pit file in there and the stock files and click rapartician and start
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot . I just flashed back after clearing cache and it worked fine. You people rocks.
Hey guys. For some odd reason I'm having issues with my AT&T HOX. I was running the Sense 5 rom and everything was running great. I was going to flash a battery % mod so, I held the power button down to get to the reboot menu to go into recovery. Well I accidently tapped the power off button instead of reboot. Crap! No problem, I thought. When I powered the phone back up again, the phone just sat on the HTC Quiet Brilliantly screen and wouldn't go any further. So, I held down the power button to force it to shut down, held the volume down key to go to the bootloader and then into TWRP. I couldn't get into TWRP. The phone would get to the TWRP splash screen and then reboot. But then it wouldn't even go back into android. It would just stay at the HTC screen. The only way I could get it into android was to RUU the phone. I flashed TWRP 2.3.3.0 on it via adb but now I still can't get into TWRP. The phone goes into a boot loop on the TWRP splash screen. I tried to do a fastboot wipe cache but that didn't help at all. Any suggestions?
You flashed recovery with adb..? You need to flash it with fastboot. Always check the md5 of your files to make sure they're good
Sent from my HTC One X using xda app-developers app
Haha, sorry, I meant fastboot. I flashed it with fastboot. When it didn't work the first time. I re-downloaded twrp and flashed it again. Same results.
Sent from my HTC One X using Tapatalk 2
Did you run the RUU? Which one? Running a RUU will restore stock recovery.
Also, the command is fastboot erase cache. Is that what you did?
Yes, I ran the AT&T 3.18 ruu. Don't worry I have s-off. The phone booted up fine after I ran the AT&T ruu. I then wanted to flash TWRP so I could install a different rom. I went to the bootloader and flashed TWRP 2.3.3.0. I flashed it with the OneX toolkit. I also did a fastboot erase cache when it didn't want to boot into TWRP. When I try to get into TWRP, it gets to the splash screen of TWRP, then the screen flashes for a second and it won't go any further. It keeps doing that until I force the phone to shut down. I am using the phone now but on 3.18 and I can't root it. I am stock. EWW!
Sent from my HTC One X using Tapatalk 2
I'm not a big fan of toolkits. They let you skip over learning things you really need to know.
Try downloading the twrp image, check the md5 to be sure it downloaded correctly, and flash in fastboot manually.
It's possible something isn't working right with the toolkit.
iElvis said:
I'm not a big fan of toolkits. They let you skip over learning things you really need to know.
Try downloading the twrp image, check the md5 to be sure it downloaded correctly, and flash in fastboot manually.
It's possible something isn't working right with the toolkit.
Click to expand...
Click to collapse
Just a few minutes ago, I re-downloaded TWRP again and flashed it with fastboot flash recovery. It said it was successful but, it is still doing the same thing. TWRP acts like it wants to boot but it won't. It gets to the splash screen and then it will just blink on and off, on and off until I force the phone to shut off.
Dang I've never seen anyone have that problem so far... That's weird.. You're doing everything correct and you sound knowledgeable.... Have you tried different twrp versions? Maybe try goo manager...
And I'm not questioning your intelligence and mean no disrespect, but are you 100% its the Evita version of twrp?
Sent from my One X using Tapatalk 2
InflatedTitan said:
Dang I've never seen anyone have that problem so far... That's weird.. You're doing everything correct and you sound knowledgeable.... Have you tried different twrp versions? Maybe try goo manager...
And I'm not questioning your intelligence and mean no disrespect, but are you 100% its the Evita version of twrp?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks man, haha, yeah I am 1000% sure it is an evita recovery. I thought about trying CWM just to see if the situation changes. Before I do that, I may try goo manager.
Yay!! I was able to flash CWM, get into it and flash SuperSU. I don't really care for CWM but at least i got SOMETHING to work. I may try TWRP again just to see if it will work.
Egrier said:
Yay!! I was able to flash CWM, get into it and flash SuperSU. I don't really care for CWM but at least i got SOMETHING to work. I may try TWRP again just to see if it will work.
Click to expand...
Click to collapse
Now that recovery is working again, you should be able to switch using goo manager.
iElvis said:
Now that recovery is working again, you should be able to switch using goo manager.
Click to expand...
Click to collapse
I tried re-downloading from a different source and flashing TWRP 2.3.3.1 again....Fail. It does the same thing. Flashed CWM again, works like a charm. What the heck is going on??
Egrier said:
I tried re-downloading from a different source and flashing TWRP 2.3.3.1 again....Fail. It does the same thing. Flashed CWM again, works like a charm. What the heck is going on??
Click to expand...
Click to collapse
Try fastboot erase cache again
Did you use Goo Manager?
iElvis said:
Try fastboot erase cache again
Did you use Goo Manager?
Click to expand...
Click to collapse
I will try fastboot erase cache. No, I flashed it with fastboot flash recovery.
Edit: Still a no go with TWRP :/ I guess I'm sticking with CWM for now.
Egrier said:
Hey guys. For some odd reason I'm having issues with my AT&T HOX. I was running the Sense 5 rom and everything was running great. I was going to flash a battery % mod so, I held the power button down to get to the reboot menu to go into recovery. Well I accidently tapped the power off button instead of reboot. Crap! No problem, I thought. When I powered the phone back up again, the phone just sat on the HTC Quiet Brilliantly screen and wouldn't go any further. So, I held down the power button to force it to shut down, held the volume down key to go to the bootloader and then into TWRP. I couldn't get into TWRP. The phone would get to the TWRP splash screen and then reboot. But then it wouldn't even go back into android. It would just stay at the HTC screen. The only way I could get it into android was to RUU the phone. I flashed TWRP 2.3.3.0 on it via adb but now I still can't get into TWRP. The phone goes into a boot loop on the TWRP splash screen. I tried to do a fastboot wipe cache but that didn't help at all. Any suggestions?
Click to expand...
Click to collapse
What about erasing cache?
Sent from my HTC One XL using xda app-developers app
Megadoug13 said:
What about erasing cache?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
I have erased it. Doesn't work.:banghead:
Sent from my HTC One X using Tapatalk 2
Egrier said:
I have erased it. Doesn't work.:banghead:
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
I would try Goo Manager, then give up if it doesn't work. CWM is okay for this phone now.
iElvis said:
I would try Goo Manager, then give up if it doesn't work. CWM is okay for this phone now.
Click to expand...
Click to collapse
Been there did that. Still won't work. Going to forget it and stick with CWM for now.
I just rooted my Verizon Galaxy SIII (MF1) via Casual and flashed CM 10.1.2. Only problem is I can't reinstall any of my apps. I've tried pushing apps from my PC to my phone. Downloading while online from the phone itself. I used titanium backup and backed up everything before the flash, but I can't figure out how to access the data I backed up. Sorry, I'm a noob, but I searched for hours and couldn't find a solution to this specific problem.
(Also, my camera hasn't worked since the flash)
Did you flash the gapps package after flashing the rom?
Sent from the future via Tapatalk 4
edfunkycold said:
Did you flash the gapps package after flashing the rom?
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Yes, and now I just get a message that says "Unfortunately, Setup Wizard has stopped." As soon as I press OK it pops up again instantly ad infinitum. And now my phone won't boot into recovery!
Go into recovery wipe cache and dalvik reflash the rom and gapps.
Edit: sorry missed the can't get into recovery. Do you have goo manager or rom Manager depending on which recovery you use and reflash recovery via app. If not as next user pointed out Odin is your friend.
Sent from the future via Tapatalk 4
edfunkycold said:
Go into recovery wipe cache and dalvik reflash the rom and gapps.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
They just said that they can't get into recovery am I right? try using Odin or something similar to flash the latest version of cwm recovery then try wat edfunkycold suggested :thumbup: goodluck
Sent from my One X using xda app-developers app
edfunkycold said:
Go into recovery wipe cache and dalvik reflash the rom and gapps.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
That's what I'm trying to do...unfortunately my phone will not boot into recovery. Holding down proper buttons does not work. And since I'm stuck on this error message I can't get to terminal app to reboot. And when I hold power button the "boot in recovery" option is not there.
windom--earle said:
That's what I'm trying to do...unfortunately my phone will not boot into recovery. Holding down proper buttons does not work. And since I'm stuck on this error message I can't get to terminal app to reboot. And when I hold power button the "boot in recovery" option is not there.
Click to expand...
Click to collapse
Turn the phone off. Then press HOME>POWER>VOLUME UP at the same time this will boot you into recovery.
Sent from the future via Tapatalk 4
lolz maybe they were using the wrong button combo all along
Sent from my One X using xda app-developers app
edfunkycold said:
Turn the phone off. Then press HOME>POWER>VOLUME UP at the same time this will boot you into recovery.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Ok, I got it to boot in recovery mode. I wiped dalvik and cache and then reflashed ROM and gapps. Still getting exact same error message.
windom--earle said:
Ok, I got it to boot in recovery mode. I wiped dalvik and cache and then reflashed ROM and gapps. Still getting exact same error message.
Click to expand...
Click to collapse
Then the only suggestion i have is to flash stock rooted rom or any TW rom and see if the phone works properly. Then we can proceed fresh again. If you run into issues on TW rom then a full odin to stock might be required.
Sent from the future via Tapatalk 4
all eaeuni
edfunkycold said:
Then the only suggestion i have is to flash stock rooted rom or any TW rom and see if the phone works properly. Then we can proceed fresh again. If you run into issues on TW rom then a full odin to stock might be required.
Sent from the future via Tapatalk 4
Click to expand...
Click to collapse
Ok I just flashed my stock rooted rom and everything seems to be working just fine. I think I'm going to hold off on flashing a custom rom again. Want to do some more research first. Thanks for everyone's help!
My phone has been soft bricked after trying to flash the latest dkp kernel. I was using philz touch recovery and I tried to flash dkp kernel 3-20 build, and I got an error during flashing saying that it couldn't decompress the ramdisk. So I tried to flash the older version of dkp that I was using, and it failed to flash! I have never had problems like this before. So now my phone will not boot to system or go back to recovery. I can only access download mode. I was using CM11 with the ML1 modem and dkp kernel before my phone got bricked. It really frustrates me that my phone just randomly decided to freak out and brick itself, because I've been doing the same thing forever and never had any problems flashing a kernel. Please tell me how I can fix my phone. Thank you.
jonny30bass said:
My phone has been soft bricked after trying to flash the latest dkp kernel. I was using philz touch recovery and I tried to flash dkp kernel 3-20 build, and I got an error during flashing saying that it couldn't decompress the ramdisk. So I tried to flash the older version of dkp that I was using, and it failed to flash! I have never had problems like this before. So now my phone will not boot to system or go back to recovery. I can only access download mode. I was using CM11 with the ML1 modem and dkp kernel before my phone got bricked. It really frustrates me that my phone just randomly decided to freak out and brick itself, because I've been doing the same thing forever and never had any problems flashing a kernel. Please tell me how I can fix my phone. Thank you.
Click to expand...
Click to collapse
This how i did back to stock.
http://forum.xda-developers.com/showthread.php?t=1867253
Will help u on soft brick.
Odin enter download mode flash stock image. After that's all done. Dnt let ur fone install the ota. And root using CASUAL root and ur back to business
Sent from my SCH-I535 using Tapatalk
twistedillutions said:
This how i did back to stock.
http://forum.xda-developers.com/showthread.php?t=1867253
Will help u on soft brick.
Odin enter download mode flash stock image. After that's all done. Dnt let ur fone install the ota. And root using CASUAL root and ur back to business
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I did an ODIN back to stock MF1. In ODIN it says "Pass!" above the com port, and it also says <OSM> All threads completed. (succeed 1 / failed 0). However, my phone has been stuck on the 4G LTE screen with the colorful rings for around 15 minutes and it doesn't seem to be doing anything. What should I do?
Pull battery out and reboot.. Thats mentioned on instructions.
Post wat odin tells u
Sent from my SCH-I535 using Tapatalk
twistedillutions said:
Pull battery out and reboot.. Thats mentioned on instructions.
Post wat odin tells u
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Well when I pulled the battery and tried to reboot a samsung logo with an unlocked symbol was underneath it and it still gets stuck on the 4g LTE screen. Also, it won't allow me to enter the recovery.
So I went back to download mode on my screen and i noticed that it still says "System Status: Custom"
jonny30bass said:
Well when I pulled the battery and tried to reboot a samsung logo with an unlocked symbol was underneath it and it still gets stuck on the 4g LTE screen. Also, it won't allow me to enter the recovery.
Click to expand...
Click to collapse
Boot into recovery, factory reset, then reboot.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Boot into recovery, factory reset, then reboot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Like I said, it won't go into recovery mode. It seems like it is going to and then it just has a black screen.
BadUsername said:
Boot into recovery, factory reset, then reboot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
You have to be able to boot into recovery, make sure you hold the volume up + home for an extended period of time.
If you can't, you need to Odin the stock rom and try again.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
You have to be able to boot into recovery, make sure you hold the volume up + home for an extended period of time.
If you can't, you need to Odin the stock rom and try again.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ODIN to stock did not work correctly. Maybe I need a different MF1 tar file. Can someone point me to a link for it? I have searched an can't find a completely stock MF1 file.
jonny30bass said:
The ODIN to stock did not work correctly. Maybe I need a different MF1 tar file. Can someone point me to a link for it? I have searched an can't find a completely stock MF1 file.
Click to expand...
Click to collapse
http://www.androidfilehost.com/?fid=23134718111254196
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
http://www.androidfilehost.com/?fid=23134718111254196
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
That's the exact one that I just used. It didn't seem to restore to stock with that.
jonny30bass said:
That's the exact one that I just used. It didn't seem to restore to stock with that.
Click to expand...
Click to collapse
Don't know what else to tell you, it's a completely stock file.
Recovery, system, kernel, and bootloader.
If you can't boot into recovery it must've not flashed perfectly or something else is wrong, like your hardware.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Don't know what else to tell you, it's a completely stock file.
Recovery, system, kernel, and bootloader.
If you can't boot into recovery it must've not flashed perfectly or something else is wrong, like your hardware.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I highly doubt that it is a hardware issue. I just tried to ODIN again and I'm in the same situation. One thing that I have noticed is that it tries to reinstall the MTP driver after using ODIN and it fails to install.
EDIT: Nevermind. I was able to enter recovery this time. I just did a factory reset. Hopefully it boots now. I will report back with results.
UPDATE: Ok. Everything seems fine now. Used casual to root and unlock bootloader again. Then installed PhilZ Touch Recovery. Now I am making a backup, and I am going to flash a Kit Kat Rom.