Related
My phone wont boot now.
It stays stuck at the 2nd Samsung during the boot up.
What happen was I updated today to offical ICS from my rooted gingerbread.
I updated via kias today to get official ICS, got it working and I noticed I didn't have cwm install anymore, so I followed this http://forum.xda-developers.com/showthread.php?t=1504218
It is pass it did it reboot thing, and never got past the 2nd "samsung" loading screen.
Anyone know how to get my phone booting again?
Flash the latest ICS kernel
I am not sure how to do that without cwm.
Before I updated to ICS when I press power + up down, it booted into CWM. Now when I do that I boots into Android System Recovery <3e>
EDIT: Good news.
Got CWM through installed though odin and then I restored to my gingerbread backup I made earlier.
Flash your roms via clockwork recovery mod from now on.
Drop the ROM .zip on sd card and then enter recovery. Wipe everything three times each then flash a uclf6 based ROM. Never touch Odin or kies again. Be happy. Ice cream sandwich is way better than ginger bread
Sent from my SAMSUNG-SGH-I717 using xda premium
Had the same exact problem. I "believe" the problem was that the CWM I flashed was perhaps incompatible with the official ICS?
I used Odin to flash cwm 5.5.0.4 as suggested and the fone was shut down with the hanging Samsung screen as you mentioned. I used the DL screen with Odin to the 600mb Team Objection ROM, which at least got me up and running again. I found out that CWM did in fact flash once the ROM was compatible with it. Updated CWM, then to finally get full stability, I had to do a factory reset after clearing both caches, then install the CM9 official.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Update: I installed official ICS again last night, looks like I lost my root and CWM.
I don't want to mess anything up again, so could you tell me exactly what CWM file you used to flash so it doesn't hang at samsung again?
I was having the same problems but I think I was doing it wrong. How are you flashing the root files? I upgraded from Kies, then used Odin to flash cwm touch (5.5.0.4 I think), make sure to let the reboot and that it's actually turned on and you can see your homescreen. Once you do that, THEN flash the superuser 3.0.7 in cwm. Let the phone reboot properly and it should be okay.
I was doing the same without the reboots and that's what caused me to hang at the logo, but after the above it worked well. Give it a try. For anyone who needs to flash the T-Mobile radios also let the phone reboot and then flash it because I was having issues with that which was fixed by letting the phone reboot.
Make nandroids at every step in case it does hang so you can just restore and try again instead of flashing everything all over again.
Sent from my SGH-I717R using xda app-developers app
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
dcdtrax said:
I've also tried rooting my AT&T Galaxy Note I717 which had recently upgraded to ICS via AT&T/Kies and my phone is stuck at the Samsung boot screen. While I'm no expert with rooting phones, I had no problem rooting it when it had GB installed so I figured I wouldn't have any problems rooting it again. Is flashing the ICS kernel the best way to fix this? Where do I get the ICS kernel from and how do I flash it?
Details: After my phone upgraded to ICS 4.0.4 kernel 3.0.8 (IMM76D.UCLF6), I followed some instructions to root it using Odin3-v1.85 and PDA->pda.tar. Other instructions used cwm-touch-i717-120414.tar.md5 and odin_n1717_cwm_recovery_b4.tar and I tried those but to no avail. So I have CWM v5.5.0.4 installed but I don't know what to do next.
Any help is greatly appreciated. Thanks!
Click to expand...
Click to collapse
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Open odin , PDA cwm file, Droid in dl mode, plug in start unplug, reboot, go to cwm recovery mode and backup onto sd card.
Im learning more, as i soft bricked mine last time
dcdtrax said:
Update: I restored my phone back to a non-rooted working Android 4.0.4 by downloading the stock ROM for my phone (I717UCLF6_I717ATTLF6_I717UCLF6_HOME.tar.md5) and uploading it using Odin3-v1.85/PDA. I didn't even lose any of my settings or data. Now I need to figure out how to successfully root it. But at least I'm not worried about getting stuck on the Samsung screen anymore.
Click to expand...
Click to collapse
Odin....to get touch cwm, then download the super user zip and flash it, you will have root....
All can be found in "My links" see it in red...go to GNote page....
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
liftedzuki said:
what about su binaries
Can i put both on my sd card and put it in my phone, cmw recovery and install from there?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1740367
ok look for the green arrow...and use those threads....to root...k
odin for touch cwm
flash super user
your rooted
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Rooted.
erad1 said:
You realize you the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so correct...you nailed it...so many are trying to root with gb kernal....
I hope they go to the page I made and follow the green arrowed how to root ics...it is very super simple process to root the official ics...but ....
This happened to me after misreading a comment.
If you put your phone into download mode, plug it in, run kies, and do an emergency firmware recovery. You'll need the serial number. My phone is stock ICS again. Works fine.
erad1 said:
You realize the reason you were stuck was because you flashed a GB kernel onto an ICS system? It would never boot. As the second post suggested... all you had to do was flash an ICS kernel to get it to boot.
Sent from my Amazon Kindle Fire using xda premium
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
romeojunior said:
so cwm 5.5.0.4 touch is a GB kernel? Because that's all I flashed after the KIES update to ICS and I got the hanging Samsung logo.
I believe some people are trying to get ICS rooted with this cwm and are getting stuck. Of course there are ways out of it, but it'll help the learning process if we can find the problem.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Wait what??!!??!!
you need to read read read read and PLEASE read
Because CMW is not a kernel
Its a recovery
People wouldn't have these issues if they read.
Please refer to the stickies before you really damage your phone.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
The OP had posted that he flashed Da_g's GB kernel trying to get root...your issue if flashing CWM may be different. Hopefully you use the steps outlined by bigjoe in his post.
Sent from my SAMSUNG-SGH-I717 using xda premium
Hello I bought a rooted note 2 and when I go to flash a new rom it always fails. Do I need to unroot go srock and re root?
Sent from my SCH-I605 using xda app-developers app
phatchef1 said:
Hello I bought a rooted note 2 and when I go to flash a new rom it always fails. Do I need to unroot go srock and re root?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Rooting doesn't give you the ability to flash ROMs, you have to have the bootloader unlocked and have a custom recovery such as twrp or cwm.
Thought you needed it unlocked to have a rom on it to start with. It has the cleanrom se1.5 on it now
Sent from my SCH-I605 using xda app-developers app
phatchef1 said:
Thought you needed it unlocked to have a rom on it to start with. It has the cleanrom se1.5 on it now
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
Ok, you didn't say that you only said it was rooted.
What steps are you taking to flash a new ROM?
You said it fails, what's the failure?
Have you tried going into recovery mode? Turn off your phone, press and hold volume up+home button+and power button till u reach the boot animation then release the buttons. You will either be in cwm or twrp. If you reached this step, then you can flash a rom that is built for your specific note 2 version. From the recovery menus you can follow the necessary steps to install. Let us know what you see.
Ps make sure you do a back up just incase
Sent from my SGH-I317 using xda premium
I can get into recovery mode just when I go to install new rom it fails
Sent from my SCH-I605 using xda app-developers app
What recovery are you running?
phatchef1 said:
I can get into recovery mode just when I go to install new rom it fails
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
What error message are you getting and what steps are you taking. Also what recovery are you using?
Sent from my SCH-I605 using Tapatalk 2
update your recovery...most likely your on the original twrp that came with adams first unlock method.
droidstyle said:
update your recovery...most likely your on the original twrp that came with adams first unlock method.
Click to expand...
Click to collapse
To do this get GooManager from the Play Store, and follow the directions in the description. I believe you press menu and then install a script.
phatchef1 said:
Hello I bought a rooted note 2 and when I go to flash a new rom it always fails. Do I need to unroot go srock and re root?
Sent from my SCH-I605 using xda app-developers app
Click to expand...
Click to collapse
I'd clean the phone up and return it to stock. Start from there.
Also, are you using a custom recovery like twrp or cwm? also, is your BL unlocked?
More info is needed to assist you further, broseph.
droidstyle said:
update your recovery...most likely your on the original twrp that came with adams first unlock method.
Click to expand...
Click to collapse
This is most likely your problem.
BennyJr said:
This is most likely your problem.
Click to expand...
Click to collapse
I didn't update twrp until last week. Prior to that I flashed carbon, rootbox, liquid, beans, eclipse, jedi, and cleanrom.
ok im running clean rom 1.5 and for recovery i have twrp. how do i update the recovery?
geoff5093 said:
To do this get GooManager from the Play Store, and follow the directions in the description. I believe you press menu and then install a script.
Click to expand...
Click to collapse
I'll bump this for you
Sent from my SCH-I605 using Tapatalk 2
ok i updated the twrp. wiped the cache and factory reset and then went to flash a rom and it says FAILED e:sigature verification failed and the next lineerror flashing zip
what did i do wrong? i flashed roms on my old s3 that was rooted this phone just doesnt want to flash roms over
phatchef1 said:
ok i updated the twrp. wiped the cache and factory reset and then went to flash a rom and it says FAILED e:sigature verification failed and the next lineerror flashing zip
what did i do wrong? i flashed roms on my old s3 that was rooted this phone just doesnt want to flash roms over
Click to expand...
Click to collapse
Did you check the md5 and what ROM are you flashing?
Sent from my SCH-I605 using Tapatalk 2
how does a person check the md5 and i have tried the beans11 and jedi10 and both have errors and fail
There is an option in TWRP that makes it look for an MD5 match... but unless you have the MD5 accessible to TWRP it will fail and not install.
Make sure the option is not checked when you go to flash.
To manually check the MD5 yourself to verify your downloads... you need an app on your PC that has the ability. Google will point you right.
Then to check the MD5, you have the app analyze the file and compare it to the MD5 provided in the ROM thread.
thanks unchecked the md5 stuff and it works thanks
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Markstache said:
So I had originally had TWRP/Hyperdrive on my phone, and switched to CWM/Cyanogenmod. I noticed now that I seem to have two different recoveries on my phone, because if I hold up+home+power I can go to a different version of CWM Recovery than if I use the Rom Manager app to boot into recovery. How would I rectify this? Would it involve wiping the /boot partition? I don't know where/how recoveries are stored so I don't understand how I can have two.
Doing a fresh install of a ROM has not resolved this by the way. And actually currently, I can't hold the buttons and boot into recovery at all, it gets stuck on the Samsung logo. I can only get into recovery via Rom Manager or Reboot options if I'm in android.
Click to expand...
Click to collapse
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I would just Odin back to stock MDK and start fresh and choose whichever recovery suits you. I had to do the same a while back myself
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I've done that so many times.
Markstache said:
I've done that so many times.
Click to expand...
Click to collapse
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
My fault ...I see where you adressed that in the last part of your post. I'm no expert either on how recoveries are stored and executed.
I would think though that flashing stock mdk would fix this as it did for me. I used ROM manager to install cwm then I flashed Philz and haven't had a problem since. Hope someone else can help you.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Yea that's what I said before too but the op said they've done that many times with no luck...
Sent from my SCH-I545 using Tapatalk
cbmggm said:
The only way to fix is to Odin back to factory image and start over.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
That's what I would have figured would fix it, because I'm pretty sure that's supposed to wipe /boot, but I found out I cannot flash kernels on my phone for some reason and when having to fix softbricks while experimenting with why it doesn't work and flashing different kernels, I had to do that whole process so many times I can go from softbrick back to where I'm at now in about 20 minutes.
Is your device in factory mode when using touchwiz roms?
jamesd1085 said:
Is your device in factory mode when using touchwiz roms?
Click to expand...
Click to collapse
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
jamesd1085 said:
OK...well try something real quick for me...use a root manager and open your efs folder...are the files still there...if not your efs folder has been formatted to the incorrect format... That would explain funky recovery issues and not being able to flash kernels...that's the only things I can think of
Click to expand...
Click to collapse
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
Definitely don't delete your efs folder. Actually it's good practice to back it up
Sent from my SCH-I545 using Tapatalk
Markstache said:
It sure is there and has files in it.
What is that folder? Should I delete the contents?
Click to expand...
Click to collapse
No!!!!...you will lose your number and all data capability...just wanted to make sure everything was still mounting properly... I'm at a loss as to what else could be causing your issues
Markstache said:
I have no idea what you mean, and I'm not using anything touchwiz based anymore.
Click to expand...
Click to collapse
I'd find someone like Philz or a TWRP compiler to ask if u haven't already gone that route. I'm sure one of them will know. Hopefully [emoji41]
Sent from my SCH-I545 using Tapatalk
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Markstache said:
Something just occured to me. When flashing back to stock with odin I always use the nowipe image because it's all I can find. I think that technically means boot was never wiped. Would that explain my phenomena? Also where to find stock that will wipe?
Click to expand...
Click to collapse
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
^^^this should fix you up...but backup everything you can to external SD or computer...when it says full wipe its no joke
Mistertac said:
I've always used this one
http://forum.xda-developers.com/showthread.php?t=2289325
I'm not 100% if its no wipe as it doesn't say. But it you haven't tried this one yet may be worth a shot
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Markstache said:
So I flashed that one via Odin, followed the guide to root and everything step by step, and now that I'm back on stock kernel and want to install CWM Recovery, I downloaded Rom Manager and hit install recovery and it says everything worked but if I boot into recovery it's just the android stock recovery.
EDIT: Another thing I thought of. Could the fact that at one point I used this method to install CWM recovery on my phone have caused there to be two different recoveries running parallel?
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
UPDATE: Using this method I installed the latest version of CWM Recovery Touch but Rom Manager still thinks the normal version is installed, though now if I hit reboot to recovery from the app it actually takes me to the touch instead of a separate one. Is the app dumb or do I still have an issue? Also I cannot install kernels without tripping the count and having my phone tell me I need to go to a verizon store.
http://wiki.cyanogenmod.org/w/Install_CM_for_jfltevzw
Click to expand...
Click to collapse
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Mistertac said:
ROM manager may actually be the issue.
And as far as installing kennels I've never had an issue myself. The last link you posted is about flashing the md2 kernel in order to root the phone. Do you mean that?? Or installing say a KToonsez kernel after you're already rooted and have your custom recovery?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
As in installing a KT kernel after rooting and having a custom recovery and ROM on my phone. Right now I have three 3/22 nightly cyanogen up and running but as soon as I install kt it trips the Verizon security and on have to flash back to stock kernel to use my phone. Booting into Odin and canceling out to restart does not let me get past the yellow triangle
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Extract the boot.img from the ROM zip file, flash ROM, reboot into bootloader and start Fastboot, then flash boot.img via fastboot on a PC, should clear it up...
In the future I would recommend going S-OFF via rumrunner, no more need to worry about flashing boot partitions separately ever again.
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, your good.
Sent from my Nexus 4 using Tapatalk
Just made a backup in TWRP and rebooted and all is well, you're awesome man. Thanks again
Sent from my Rezound on Tachyon using XDA Premium 4 mobile app
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
christianstudebaker said:
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
Click to expand...
Click to collapse
Have actually research what firmware you have and what recovery can be used. You do know that unless you have mdk...you can't use goomanger or twrp or Cwm right?
Sent from my SCH-I545 using Tapatalk
decaturbob said:
Have actually research what firmware you have and what recovery can be used. You do know that unless you have mdk...you can't use goomanger or twrp or Cwm right?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
How many times do you think this same question has been asked and answered?
Sent from my NCC-1701
riker147 said:
How many times do you think this same question has been asked and answered?
Sent from my NCC-1701
Click to expand...
Click to collapse
Countless times....not even 15 mins of reading anything...
Sent from my SCH-I545 using Tapatalk
christianstudebaker said:
Hey guys, I recently got a replacement device from best buy because my old ones screen broke. I successfully rooted the new device using the towelroot method. I just tried to install the loki recovery via goomanager and when I rebooted it just boots into odin mode and says that it "could not do normal boot." I've tried everything I can think of but cant get it to boot. Any help?
Click to expand...
Click to collapse
I believe you are going to have to go with SafeStrap 3.72. You don't have an unlocked bootloader but Safestrap isn't bad. You can still install some really good roms
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
christianstudebaker said:
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
this is a stickie in general forum that all new S4 people should be required to read...I can not imagine how some one ignores a thread when its titled
What you need to know before, during and after modifying your verizon S4
http://forum.xda-developers.com/showthread.php?t=2606501
christianstudebaker said:
The problem is that I can't boot my phone now. It just boots into Odin mode. When I got my phone originally it wasn't mdk so I didn't have to deal with safestrap. So I didn't know there was other options.
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if you can get into download mode and have Odin, flash a full wipe or a no wipe tar and start over.
http://forum.xda-developers.com/showthread.php?t=2735172