Related
New user yay
So here's the dealio guys, I've been researching about rooting and custom ROMs and such since I got my S2 (i777) a few months ago. I really don't like Touchwiz, and the stock ICS look is just better. So I found a nice-looking ROM (the AOKP ROM), rooted my phone with no problems using Siyah/Odin, and went ahead and put the ROM in an external SD card that I bought just for this purpose. So I boot into recovery mode (with ROM Manager), and then... nothing. I try to boot up my phone but it just flashes the start screen showing my model number, then just turns right back off. I've tried taking out my battery, still no dice. BUT, I can still get into download mode (but not recovery). So is there any way to restore the backup I made before installing the ROM using the download mode?
Thanks!
JakeAuditore said:
New user yay
So here's the dealio guys, I've been researching about rooting and custom ROMs and such since I got my S2 (i777) a few months ago. I really don't like Touchwiz, and the stock ICS look is just better. So I found a nice-looking ROM (the AOKP ROM), rooted my phone with no problems using Siyah/Odin, and went ahead and put the ROM in an external SD card that I bought just for this purpose. So I boot into recovery mode (with ROM Manager), and then... nothing. I try to boot up my phone but it just flashes the start screen showing my model number, then just turns right back off. I've tried taking out my battery, still no dice. BUT, I can still get into download mode (but not recovery). So is there any way to restore the backup I made before installing the ROM using the download mode?
Thanks!
Click to expand...
Click to collapse
Plug phone in odin and try again
JakeAuditore said:
New user yay
So here's the dealio guys, I've been researching about rooting and custom ROMs and such since I got my S2 (i777) a few months ago. I really don't like Touchwiz, and the stock ICS look is just better. So I found a nice-looking ROM (the AOKP ROM), rooted my phone with no problems using Siyah/Odin, and went ahead and put the ROM in an external SD card that I bought just for this purpose. So I boot into recovery mode (with ROM Manager), and then... nothing. I try to boot up my phone but it just flashes the start screen showing my model number, then just turns right back off. I've tried taking out my battery, still no dice. BUT, I can still get into download mode (but not recovery). So is there any way to restore the backup I made before installing the ROM using the download mode?
Thanks!
Click to expand...
Click to collapse
1. Never use ROM manager.
2. reflash i777 kernal with Odin.
3. get to recovery the correct way. ROM Manager is a joke.
killman2659 said:
Plug phone in odin and try again
Click to expand...
Click to collapse
Alright, reinstalled Siyah, and it said successful, but now it's not getting past the battery indicator screen when charging. Still no dice.
MotoMudder77 said:
1. Never use ROM manager.
2. reflash i777 kernal with Odin.
3. get to recovery the correct way. ROM Manager is a joke.
Click to expand...
Click to collapse
killman2659 said:
Plug phone in odin and try again
Click to expand...
Click to collapse
Is there any way I can just factory restore vanilla ICS with Odin? Like, unroot it?
JakeAuditore said:
Is there any way I can just factory restore vanilla ICS with Odin? Like, unroot it?
Click to expand...
Click to collapse
vanilla android is google, or AOSP.
This device has samsungs ****ty touchjizz.
Yes you can get a stock file from the download repository and flash a crappy build onto your phone.
MotoMudder77 said:
vanilla android is google, or AOSP.
This device has samsungs ****ty touchjizz.
Yes you can get a stock file from the download repository and flash a crappy build onto your phone.
Click to expand...
Click to collapse
Yeah, I hate Touchwiz. I found an unroot file, flashed it, and now I'm back to Gingerbread 2.3.4. I'm going to probably update to ICS again, then try once more to put that ROM on here. I won't use ROM Manager this time, hopefully it'll go alright.
JakeAuditore said:
Yeah, I hate Touchwiz. I found an unroot file, flashed it, and now I'm back to Gingerbread 2.3.4. I'm going to probably update to ICS again, then try once more to put that ROM on here. I won't use ROM Manager this time, hopefully it'll go alright.
Click to expand...
Click to collapse
iF you just want a custom ROM, just flash a custom kernel with odin, boot into recovery and flash said ROM. no need to go back to stock, update, flash another ROM, then root.....yada yada yada. waste of time and space on computer
MotoMudder77 said:
iF you just want a custom ROM, just flash a custom kernel with odin, boot into recovery and flash said ROM. no need to go back to stock, update, flash another ROM, then root.....yada yada yada. waste of time and space on computer
Click to expand...
Click to collapse
So I can do all this from Gingerbread? It was an ICS ROM that basically is just like the stock Google version. That's what I have been wanting since the beginning.
JakeAuditore said:
So I can do all this from Gingerbread? It was an ICS ROM that basically is just like the stock Google version. That's what I have been wanting since the beginning.
Click to expand...
Click to collapse
yea, in order to flash a custom ROM, you need custom recovery, ahh hell, been so long i forgot about having a rooted system required or not.
think you do, so should be able to get a rooted package, flash that, enter recovery and flash the ROM that you like.
Maybe someone will chime in and refresh my memory on the rooted system requirement.
U can flash a custom kernel .tar with Odin. There are some siyah tar files floating around. Or u could make a .tar yourself if u really wanted to. Once flashed it'll have cwm built in and u can flash whatever u want.
Sent from my SGH-I777 using Tapatalk 2
MotoMudder77 said:
yea, in order to flash a custom ROM, you need custom recovery, ahh hell, been so long i forgot about having a rooted system required or not.
think you do, so should be able to get a rooted package, flash that, enter recovery and flash the ROM that you like.
Maybe someone will chime in and refresh my memory on the rooted system requirement.
Click to expand...
Click to collapse
You only need root to install and use the Mobile Odin app, which is used for installing a custom kernel without tripping the flash counter. Once you've got Mobile Odin, download the custom kernel (e.g. Siyah) you want (ICS kernel if you're gonna install an ICS rom, same for GB), extract the zImage to your phone, and use Mobile Odin to install it. Note that if you're currently running GB and flash an ICS kernel, your phone won't boot but you can still get into CWM, which is all that matters because then you can flash the ICS rom of your choice and then your phone will boot.
Alternatively, you can do what Phalanx said and flash a custom kernel using PC version of Odin. Only difference between this and using Mobile Odin is you trip the flash counter, which can be fixed in any ICS rom by using the TriangleAway app.
The custom kernel will include CWM, which can then be used to flash any ROM/mod; in fact CWM is the ONLY safe method of flashing/wiping/restoring/backing up anything from that point forward.
karate104 said:
You only need root to install and use the Mobile Odin app, which is used for installing a custom kernel without tripping the flash counter. Once you've got Mobile Odin, download the custom kernel (e.g. Siyah) you want (ICS kernel if you're gonna install an ICS rom, same for GB), extract the zImage to your phone, and use Mobile Odin to install it. Note that if you're currently running GB and flash an ICS kernel, your phone won't boot but you can still get into CWM, which is all that matters because then you can flash the ICS rom of your choice and then your phone will boot.
Alternatively, you can do what Phalanx said and flash a custom kernel using PC version of Odin. Only difference between this and using Mobile Odin is you trip the flash counter, which can be fixed in any ICS rom by using the TriangleAway app.
The custom kernel will include CWM, which can then be used to flash any ROM/mod; in fact CWM is the ONLY safe method of flashing/wiping/restoring/backing up anything from that point forward.
Click to expand...
Click to collapse
This may not be the place to ask but how can I reset the flash counter that pops up in download mode
Sent from my SGH-I777
As long as you're running ICS, just download TriangleAway from the Play Store. That'll reset the flash counter to 0 and get rid of the yellow triangle that appears on start up.
Sent from my SGH-I777
karate104 said:
As long as you're running ICS, just download TriangleAway from the Play Store. That'll reset the flash counter to 0 and get rid of the yellow triangle that appears on start up.
Sent from my SGH-I777
Click to expand...
Click to collapse
Oh epic thought it only got rid of the triangle! Thanks!
Sent from my SGH-I777
122ninjas said:
Oh epic thought it only got rid of the triangle! Thanks!
Sent from my SGH-I777
Click to expand...
Click to collapse
It does. It does BOTH.
Sent from my SGH-I777 using Tapatalk 2
Bricked S2 too!
I finally bricked my first phone.Its been a long ride but it caught up to me. I have had three different android phones within about 4 years and have successfully rooted all three myself and have successfully flashed them over and over close to 1000 times between all three phones including modems, kernals, gapps, themes etc. So what gives? Why today? To be honest I don't know. But here is what happened...
The past few days I have been going back and forth between different kernals for this device to try to get something that won't freeze up. ( I liked browsing on this phone but I would get freeze ups and therefore would flash something new to try and resolve it.) Today my phone froze so I tried a simple reboot. The boot then did a freeze on the kernal's "intro" picture. It wasn't a bootloop it just frooze. (I was on XWLPT with Skyfire Kernal). I decided to reboot into recovery and flash a different kernel. I flashed NEAK The flash went halfway then stuck and froze. I rebooted to try to get back to the phone's main screen. This time it would not boot. I couldn't tell if it was in bootloop or was froze. I went back into recovery. Here I should of wiped everything but in the back of my mind I thought I could just do it in odin if I lost recovery. So I tried flashing Siyah for sammy roms. This is when I lost everything. It froze in cmw on the flash again but this time when I tried going back into recovery it stayed on the Galaxy SII screen. So I put the phone in download mode and started Odin up. When trying to flash anything in Odin I got stuck on nand write start! I never heard of this. I thought Odin would work as this is how I rooted the phone when I first got it. Last thing I did was install kies which couldn't even connect to the phone. So all I am left with is download mode and taking way more caution when flashing. I think it may have been a case of the brickbug. Even though I was on a I9100 rom and using "safe" kernels I believe something happened to lock me out from writing anything to the phone.
As long as you don't mind overwriting any data on the device you can use Kies for a complete restore. Download the latest version from Samsung, then click on the Tools selection, then "Firmware Upgrade and Initalization." You'll need your devices model number and serial number from underneath the battery. Follow the directions to put the device in download mode and proceed. You'll end up with a new factory-fresh reload.
zancro said:
As long as you don't mind overwriting any data on the device you can use Kies for a complete restore. Download the latest version from Samsung, then click on the Tools selection, then "Firmware Upgrade and Initalization." You'll need your devices model number and serial number from underneath the battery. Follow the directions to put the device in download mode and proceed. You'll end up with a new factory-fresh reload.
Click to expand...
Click to collapse
Now this i didn't know. My SII has been acting really weird ever since I unrooted. It won't let me update my firmware past 2.3.4 for some reason. So if I did this, it will most likely fix that problem?
Alright, I connected my phone to Kies, and went to Tools>Firmware Upgrade and Initialization, and it says my device does not support initialization. It also says this right under my device info:
Your device does not support software upgrading via Kies
--------------------------------------------------------------------------------------------
Current firmware version: PDA:KH7 / PHONE:LE5 / CSC:KH7 (ATT)
Ugh, really getting tired of this. Why is my phone being retarded? I don't think I want to bother rooting anymore, it seems like more of a hassle than a good thing. I really don't want to have to break my phone to get a replacement with my warranty. How do I fix this, guys?!
Noob here, thanks in advance for any help. I have a rooted vzw note 2 through Odin root66, I've tried unsuccessfully to flash a new rom, always get the dreaded yellow triangle from big brother. I need to unlock the bootloader but am still a bit timid in exploiting things. I've tried flashing with clockwork mod and goo, with the same result, and manage to return to root using Odin root66 etc... I wonder if I can use casual since I'm already rooted? I'm on stock Os 4.1.1, so close and yet so far away from flashing... any help appreciated, thanks
avatarzan said:
Noob here, thanks in advance for any help. I have a rooted vzw note 2 through Odin root66, I've tried unsuccessfully to flash a new rom, always get the dreaded yellow triangle from big brother. I need to unlock the bootloader but am still a bit timid in exploiting things. I've tried flashing with clockwork mod and goo, with the same result, and manage to return to root using Odin root66 etc... I wonder if I can use casual since I'm already rooted? I'm on stock Os 4.1.1, so close and yet so far away from flashing... any help appreciated, thanks
Click to expand...
Click to collapse
You have to use Causal if you want to flash a rom. Rooting just gives you root access, to flash a rom your bootloader has to be unlocked and you have to have a custom recovery installed. Thats what Casual does, it unlocks your bootloader and installs you first custom recovery for you. Once that is done you will be able to flash roms, not before.
How did you miss that? Its written in all the guides.
Sent from my SCH-I605 using XDA Premium HD app
missed it
shangrila500 said:
You have to use Causal if you want to flash a rom. Rooting just gives you root access, to flash a rom your bootloader has to be unlocked and you have to have a custom recovery installed. Thats what Casual does, it unlocks your bootloader and installs you first custom recovery for you. Once that is done you will be able to flash roms, not before.
How did you miss that? Its written in all the guides.
Sent from my SCH-I605 using XDA Premium HD app
Click to expand...
Click to collapse
I rooted before I ever found this forum...so I missed it....until now. My question is can I use Casual now that I'm rooted? I don't want to brick....I'm running stock rom and rooted and what I've read doesn't address my situation...or I totally missed it if it does...
Mahalo for your reply
avatarzan said:
I rooted before I ever found this forum...so I missed it....until now. My question is can I use Casual now that I'm rooted? I don't want to brick....I'm running stock rom and rooted and what I've read doesn't address my situation...or I totally missed it if it does...
Mahalo for your reply
Click to expand...
Click to collapse
I wish you could. I didn't see the Casual One Click until 5 minutes after I rooted. When you try casual, it will check your bootloader and give you a long message saying a lot of things that basically call you dumb for not reading. I'm currently trying to return to stock but I can't extract an .xz file to get it back to stock because it fails at sboot.bin. Sorry man
Yogurt HBI said:
I wish you could. I didn't see the Casual One Click until 5 minutes after I rooted. When you try casual, it will check your bootloader and give you a long message saying a lot of things that basically call you dumb for not reading. I'm currently trying to return to stock but I can't extract an .xz file to get it back to stock because it fails at sboot.bin. Sorry man
Click to expand...
Click to collapse
It sounds like I am in that boat. There has to be some sort of fix for this right? It has been a long week for me this time rooting, wow.
Yogurt HBI said:
I wish you could. I didn't see the Casual One Click until 5 minutes after I rooted. When you try casual, it will check your bootloader and give you a long message saying a lot of things that basically call you dumb for not reading. I'm currently trying to return to stock but I can't extract an .xz file to get it back to stock because it fails at sboot.bin. Sorry man
Click to expand...
Click to collapse
If it fails at sboot.bin use the alternative recovery ROM in droidstyles guide and flash it in Odin.
As far as I knew you can use CASUAL to unlock, you just have to use the newest version.
Sent from my SCH-I605 using XDA Premium HD app
Same problem
I brought this VZW Note 2 off of craigslist and it was already rooted. I was wanting to flash jelly beans v19 and tried to install TWRP but CWM was already installed and I really forgot what I did its been 10 hours already following guides and the only thing that works is odin, pit and root66 but anything else I try after getting the phone back up fails and root66 would not pass the last several times but this last time it did. I suspect the bootloader is locked but I'm rooted. I want to clear everything and install a fresh rom since I don't know the history and the phone was freezing and glitchy but I did not check see what rom the previous owner had installed and by the way Im a total newb but really have been seaching threads to solve this before posting but with no luck. Any help much appreciated
jmc71 said:
I brought this VZW Note 2 off of craigslist and it was already rooted. I was wanting to flash jelly beans v19 and tried to install TWRP but CWM was already installed and I really forgot what I did its been 10 hours already following guides and the only thing that works is odin, pit and root66 but anything else I try after getting the phone back up fails and root66 would not pass the last several times but this last time it did. I suspect the bootloader is locked but I'm rooted. I want to clear everything and install a fresh rom since I don't know the history and the phone was freezing and glitchy but I did not check see what rom the previous owner had installed and by the way Im a total newb but really have been seaching threads to solve this before posting but with no luck. Any help much appreciated
Click to expand...
Click to collapse
Flash Root66 or the alternative restore with the NAND erase box in Odin checked. If it won't flash just the ROM in Odin try flashing the ROM + the PIT by following the instructions in droidstyles guide in Android Development.
You would do better to make your own thread too.
Sent from my SCH-I605 using XDA Premium HD app
I was originally trying to just go to the new kitkat rom, i believe that was CM11 or something of the sort. But for some reason i cannot do anything with my phone when it comes to installing or changing the recovery. Odin fails every time. One-Click-Root fails every time (which i think is what i used from the beginning to root). I even upgraded ROM manager to pro so i could try the touch based recovery and it will not successfully install a recovery that i can boot into even though it says that it has and shows(ed) the current recovery being the most up-to-date version. And now since ive tried several different today, i have lost root somehow...even thought i just had it and didnt change anything with the root process...just trying to regain even the stock recovery. Basically what happens if i try to boot into recovery mode is it tries for half a second then boots to ODIN mode and in the top left corner it says failed normal boot or something of the sort.
Can someone point me in the right direction? would a factory reset within the android OS help anything? every thing is backed up, so that wont be an issue as far as apps/data and important files goes.
The phone still boots to my "rooted" 4.3 that i have installed, just dont have root privelages any longer...the phone still works as normal...just cant do anything root based...like run titanium backup or supersu, and even ROM manager is NOW giving me an error when trying to install a custom recovery.
I would like to restore to stock MDK so i can start from scratch and install the CM11 KitKat Rom if at all possible...
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
decaturbob said:
So you were mdk and loki'd correct...
safestrap powered Hyperdrive 12
Click to expand...
Click to collapse
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
MURD3RD said:
MDK yes, the loki part im not sure of...but i did try to do that again since having this problem...with no success...
Click to expand...
Click to collapse
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
decaturbob said:
you would have to to use the loki process to gain root and install the custom recovery at the time. I really can't help as I got into the S4 with ME7 base and been using safestrap.
Click to expand...
Click to collapse
you got a link to a good working Loki tutorial?
Here's a link to the stock mdk tar file. This will totally wipe your phone. http://www.sxtpdevelopers.com/showthread.php?t=237
Ryno77 said:
Here's a link to the stock mdk tar file. This will totally wipe your phone.
Click to expand...
Click to collapse
i did find that link before and am currently downloading it...but it is taking forever...everything else i download is blazing fast (50Mb D/L speed here at my buddies apartment) but yet this file is only downloading at 50KB/s...and is showing over 9-10 hours for the download to be complete...does anybody have a faster download source?
i know my connection is phenomenal since i downloaded a 9 gig file last night from a different source and it took under an hour...this .tar is less than 2 gigs...shouldnt take that damn long...
i also tried flashing the recovery .tar.md5 from that link...same exact result...
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
kennyglass123 said:
Questions and Help issues go in Q&A and Help section
Thread moved
Thanks
FNSM
Click to expand...
Click to collapse
THANKS!!!
I knew i hadn't put it in the right place...hopefully it'll get more view here...and i can get this thing sorted out
so right now the screen shows (phone)--(yellow triangle)--(computer) and says "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
this is after trying to install the stock restore .tar files in the link mentioned above...the device will NO LONGER boot the os and goes to this screen every time. I can still get it into download (Odin) mode though.
MURD3RD said:
i also tried following this link
http://forum.xda-developers.com/showthread.php?t=2290798
and it doesnt get past the first ODIN step and gets a fail
attached are some snips of the ODIN screen when it fails
Click to expand...
Click to collapse
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
k1mu said:
The "fail (auth)" means that you're likely no longer running an MDK bootloader. It's refusing to load the MD2 that's used by Loki.
Do you get the same failure when you try to flash the stock MDK ROM image? What text shows up on your phone when you try to flash the stock?
Since you're stuck at the "Firmware upgrade encountered an issue." it indicates that the bootloader rejected a flash, which means you may have somehow updated to MI1 or later. The message on the phone when the flash fails will tell for sure.
Click to expand...
Click to collapse
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
MURD3RD said:
i can't remember what exactly the messages were right now...but currently Kies is trying a recovery "upgrade and initialization"...hopefully this works and my phone can at least be usable again...and THEN ill get back at trying to get the new KitKat, lol
Click to expand...
Click to collapse
You won't be on MDK, so no KitKat.
k1mu said:
You won't be on MDK, so no KitKat.
Click to expand...
Click to collapse
but i have had no problem flashing back to get rooted when i first got the device...even though several threads said it couldnt be done...all i need is to get back to stock and start from scratch...at least i hope this is the case. If it goes ahead and installs the newest 4.3 update...and i truly cant change it due to no exploits yet...then i guess ill have to wait...lol, it could be worse, haha
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
MURD3RD said:
so kies just finished doing its thing and the phone booted up and is now running 4.3 MK2
Click to expand...
Click to collapse
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
EDIT: well nevermind...i think i was just crazy to think something different...i am definitely running the latest release of 4.3 from vzw...fml...well at least it can still be rooted. Is there any development for KitKat on the new MK2 software? Ill do some searching around...
i do remember, however, doing something that a tutorial said specifically not to do...and it worked anyway...even though several people responding to the thread said not to do or it would brick the phone...o well i guess...if i find the link ill post it up...
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
would you happen to have a link to the safestrap tutorial? i cant seem to locate it...im gunna do some more searching, but if you had a link at the ready, that'd be awesome!!!
EDIT: Found it...no worries
gnubian said:
That means you lost the mdk bootloader and can only use Safestrap to boot custom rooms :/ you will need to root via saferoot in the development thread first. Then load Safestrap which only has one ROM that currently works (hyper drive 12).
Click to expand...
Click to collapse
so i found the thread for this ROM and it doesnt say anything about being able to run on MK2 build...can anyone shed some light on this? it only says MJ7...
Brand new Samsung S4, had successful root (checked via Root Checker). I had previously installed Clockworkmod but after some difficulty with flashing Cyanogenmod 10.2 I downloaded GooManager and installed it's preferred recovery, then re-downloaded the CM 10.2 and directed GooManager to install the .zip, and it popped up the "Downloading... Do not turn off target!!" The script in the top left says as follows
"Could not do normal boot.
ODIN MODE
Product Name: SSCH-1545
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled"
It has been on this downloading screen with no changes for 2 hours. After researching other threads, I tried to reboot into recovery, only for this exact screen to pop up immediately, and again with no change for prolonged periods of time.
Any help would be greatly appreciated! I am fairly new to this as well, so the more user-friendly the better.
What software version are you running?
Sent from my SCH-I545 using Tapatalk
joshuabg said:
What software version are you running?
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I can't remember off the top of my head... 4.2.3 pops in to mind, I'll research and post as soon as I find.
You can't ****ing use goomanager, god dammit read alittle before you **** up your phone. Just boot holding power, home, and volume down, and when prompted press no
I managed to get back to stock with root; I used Goo Manager -because- I did some reading, but obviously I read the wrong things. If someone could assist with the best structure to use (which recovery, best method for flashing, etc.) I would greatly appreciate it.
ziggums said:
I managed to get back to stock with root; I used Goo Manager -because- I did some reading, but obviously I read the wrong things. If someone could assist with the best structure to use (which recovery, best method for flashing, etc.) I would greatly appreciate it.
Click to expand...
Click to collapse
Search in android development. Factory Firmware is there. You'll need to Odin at this point. Whatever came on your phone stock. The firmware version matters here. Can't Odin a previous version. Only what's on it or a newer version. After that a reroot and find the safestrap thread in android development. Read up. This will be your recovery. No aosp. No custom kernels just touch wiz ROMs.
Sent from my SCH-I545 using XDA Premium 4 mobile app
ziggums said:
Brand new Samsung S4, had successful root (checked via Root Checker). I had previously installed Clockworkmod but after some difficulty with flashing Cyanogenmod 10.2 I downloaded GooManager and installed it's preferred recovery, then re-downloaded the CM 10.2 and directed GooManager to install the .zip, and it popped up the "Downloading... Do not turn off target!!" The script in the top left says as follows
"Could not do normal boot.
ODIN MODE
Product Name: SSCH-1545
Current Binary: Samsung Official
System Status: Custom
Knox Kernel Lock: 0x0
Knox Warranty Void: 0x0
CSB-CONFIG-LSB: 0x30
Write Protection: Enable
eMMC BURST MODE enabled"
It has been on this downloading screen with no changes for 2 hours. After researching other threads, I tried to reboot into recovery, only for this exact screen to pop up immediately, and again with no change for prolonged periods of time.
Any help would be greatly appreciated! I am fairly new to this as well, so the more user-friendly the better.
Click to expand...
Click to collapse
you have soft bricked your phone by not understanding what you can and can't do with it. Better learn about odin process
Mightycaptain said:
Search in android development. Factory Firmware is there. You'll need to Odin at this point. Whatever came on your phone stock. The firmware version matters here. Can't Odin a previous version. Only what's on it or a newer version. After that a reroot and find the safestrap thread in android development. Read up. This will be your recovery. No aosp. No custom kernels just touch wiz ROMs.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I found several guides about flashing to original, but none of them match my build (I am MK2). The phone is behaving exactly as before except when I try to boot into recovery mode it sends me back to the "Downloading.... Do not turn off target!!" screen, and I have to go through the process to get back to "normal" behavior. Could I simply just flash a different recovery, or do I need to try to find MK2 to go back to original first?
I appreciate all the help so far!
ziggums said:
I found several guides about flashing to original, but none of them match my build (I am MK2). The phone is behaving exactly as before except when I try to boot into recovery mode it sends me back to the "Downloading.... Do not turn off target!!" screen, and I have to go through the process to get back to "normal" behavior. Could I simply just flash a different recovery, or do I need to try to find MK2 to go back to original first?
I appreciate all the help so far!
Click to expand...
Click to collapse
You CAN'T flash a recovery on your build. That's the whole problem. You need to Odin back to your stock build. There is an MK2 file in the development section.
Sent from my NCC 1701 using Tapatalk 4
riker147 said:
You CAN'T flash a recovery on your build. That's the whole problem. You need to Odin back to your stock build. There is an MK2 file in the development section.
Sent from my NCC 1701 using Tapatalk 4
Click to expand...
Click to collapse
Could you link me to it? I can't find anything that deals with soft-brick reversing for MK2.
ziggums said:
Could you link me to it? I can't find anything that deals with soft-brick reversing for MK2.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2578209
douger1957 said:
http://forum.xda-developers.com/showthread.php?t=2578209
Click to expand...
Click to collapse
Thanks! I assume I would need to do the full-wipe process rather than the no-wipe process?
ziggums said:
Thanks! I assume I would need to do the full-wipe process rather than the no-wipe process?
Click to expand...
Click to collapse
I think in the long run a full wipe is always the best route.
douger1957 said:
I think in the long run a full wipe is always the best route.
Click to expand...
Click to collapse
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
ziggums said:
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
Click to expand...
Click to collapse
Being on MK2 your ONLY option is Safestrap. No Cm, no AOSP.....Just TW. You have a lot of research to do. Start here: http://forum.xda-developers.com/showthread.php?t=2606501
ziggums said:
The link was exactly what I needed! The video link they had was especially helpful, I returned to stock. I do have a question moving on from here though... Can I use Odin to try to flash CM10.2 (the one that was unsuccessful previously)? And what recovery do you recommend? The other posters mentioned something about Safe... I'm really just trying to get a smooth, stable ROM so I don't have to deal with the bloatware and can customize a bit more for what I need. Sorry if I'm annoying, but I appreciate all the help!
Click to expand...
Click to collapse
Please do some research...you can't install cm or asop base roms or custom recovery like cwm or twrp...your only option is safestrap.
Sent from my SCH-I545 using XDA Premium 4 mobile app
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Chad52 said:
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Click to expand...
Click to collapse
I am far from an expert but I think you are on the right track with having to do Odin.
I haven't used loki-doki before but after doing some reading the requirement is a working custom recovery.
This may be a dumb question but did you try to re-install something like CWM?
(CM11 jflte MDK baseband)
Chad52 said:
OK, made a dumb mistake. Not a frequent poster so I had to post here rather than in the thread where it belongs:
http://forum.xda-developers.com/showthread.php?t=2643031&page=266
[ROM]KOT49H【4.4.4】AOSP Official Google Edition 【Verizon!】06-25-2014
Basically, I didn't re-flash loki-doki. I had 4.4.2 running and had re-flashed 4.4.3 but somehow thought that I could reboot and then re-enter recovery to re-flash loki rather than doing it all at once. Dumb move. So now I have a perfectly good 4.4.3 load, but I can't enter recovery to do anything else. I want to flash the 4.4.4 image, but anytime I try to get into recovery I get the "System software not authorized by Verizon Wireless / Yellow Triangle" message.
I know I can Odin back to a stock image, but is there an easy way to force into recovery to flash loki-doki? Tried Flashify per another users post but that doesn't get me anywhere. Have not tried Triangle Away, because I didn't think that would cure my issue. The answer may be to re-flash, but I wanted to see if there was an easy way first. Running MDK btw....
Chad
Click to expand...
Click to collapse
Try unzipping whatever recovery it is you want to use and then use Flashify to " flash recovery image " and locate the Recovery. IMG you got from unzipping earlier.
Also I would run Tri Angle Away too.
If using that method to get you're recovery back doesn't help... Then yes Odin it is.
Sent from my SCH-I545 using Tapatalk
Thanks all. I use twrp, and have tried reflashing it, but nothing let's me reboot into recovery without the situation described above. My fault, so looks like back to square one I go...
Sent from my GT-I9505G using Tapatalk
Chad52 said:
Thanks all. I use twrp, and have tried reflashing it, but nothing let's me reboot into recovery without the situation described above. My fault, so looks like back to square one I go...
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
Are you just trying to get into recovery from the ROM? Or from a battery pull and phone off? Sometimes getting into it from the ROM can get borked but the other method works in which case flashing the ROM again should fix that. Again I'd also use Tri Angle Away
Sent from my SCH-I545 using Tapatalk
Trying from inside the ROM. I've got a fully functioning 4.4.3, but I'm locked out of getting into Recovery....
Chad
Flashify can't even get me into Recovery...
Thanks all, I ODIN'd back to stock and worked it all the way back forward to 4.4.4. Appreciate the help.
Chad
I hate digging up old threads especially when Hijacking them. But I wanted to say thanks for the information you provided. It helped a lot and got me back into recovery (TWRP 2.8.1.1). Now the real fun begins. I have not had this phone in my possession for quite some time (November 2013). Anyway, I was tasked with bringing it up to date and I might need some further assistance. If so, I'll start my own topic in this sub forum.
Thanks again @Mistertac.
Mistertac said:
Try unzipping whatever recovery it is you want to use and then use Flashify to " flash recovery image " and locate the Recovery. IMG you got from unzipping earlier.
Also I would run Tri Angle Away too.
If using that method to get you're recovery back doesn't help... Then yes Odin it is.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse