I semi-bricked my phone and had to flash stock kernel and system via odin. Then texting was broken still so i flashed the DI01 all in one via odin, then updated to the latest OTA, which i think is EA28.
But now im confused about how to root again and which recovery to flash. CWM seemed to be the problem last time, it wouldnt data wipe (said "failed to unmount volume", or something similar), and i couldnt permanently ditch the blue recovery.
Can i still use the rageagainstthecage.bin exploit to root and then just flash the new version of CWM here: http://forum.xda-developers.com/showthread.php?t=1017817 ?
You are looking for the Q and A section.
Related
i just updated my phone to EB01 and lost root, then rerooted my phone but know i can't get clockworkmod recovery running properly. all i get is stock recovery. do i need to rename a file update.zip?
ED01!!! that's what i meant
You could odin the attached file like I did.
i did that but i figured out my problem... flash a custom kernel
i dont know why i wasnt doing that
I am new to modding my vibrant (phone is rooted but that's all) but looking to flash a new ROM. I dl'd rom manager and installed cwr. When I reboot into recovery mode via rommanager or manually doing it,I do not get the prompt to backup. Only options I get are to reboot system, reinstall packages, delete all user data, delete cache data, and format internal sd-card. Anyone know how to fix this? I just updated to 2.2 froyo UVKB5 kernel 2.6.32.9 if that helps.
looks like you have stock recovery.
try reinstall packages, might take a couple times..
or install CWM via replacing update.zip
What he said, yeah.
So just delete the current update.zip file on my phone and replace it with a new one? Any links to download the update.zip file?
Sometimes you have to Reinstall Packages twice for it to go from regular recovery to CWR. If you flash a custom ROM though, most have a custom recovery built in.
If you have to replace the update.zip (which I don't think that you do), this worked for me the first time I rooted.
http://forum.xda-developers.com/showthread.php?t=849028
How to Root.
I am rooted, but I want to back everything up so that way if I do not like the new custom rom I can go back. I tried reinstalling the update.zip file from the link but s till have the same issue. Any other solutions besides going back to stock and going from there? And if I did go back to stock, would I lose everything?
I backed up using Titanium Backup, is that the same as going into recovery mode and backing up?
Re-download recovery using ROM Manager, then repeat. Worked when I had a similar issue.
Tried that several times. I also reuploaded the update file and reinstalled the package several times. Still no luck so I think I might go back to stock using Odin.
Then DL Eugenes froyo don't brick ROM with the 2e recovery update in it, then re-install packages, maybe twice and you'll have the green recovery menu your seeking
Googled Eugene's DL and I do not feel to confident with it. Is it supposed to fix the issue with getting into recovery mode?
So I went back to stock last night using Odin, upgraded to 2.2, and rooted using Superoneclick. Phone's back up and running but faster than the first time I upgraded to 2.2. I still have the issue getting into the proper recover to install the zip file. I've read that deleting Slacker helped some people, assuming it freed up space on the System ROM. My system ROM was full until I started to delete some apps. I now have 20.7 MB free. Could not enough System ROM space be the issue?
I am now also getting a "Fail" attempt when I try and update su saying that it failed to find currently installed su binary. Any advice on fixing this?
TIA!!!
it would probably be easier to just odin back to stock jfd and then flash a deodexed kb5 build thats rooted with SU already in it from here in the forums.
http://forum.xda-developers.com/showthread.php?t=1036193&highlight=deodexed
If you flashed kb5 from kies or odin and don't want to reinstall the rom then you will need to flash a modified 3e recovery because you probably are not quite rooted and won't be able to use CWM until you flash the modified 3e recovery...
http://forum.xda-developers.com/showthread.php?t=833423
You might want to check out the AIO vibrant toolbox (pinned topic in the development thread) it will give you big easy buttons and instructions to flash back to jfd and root and flash a new rom if you need to... It comes with Odin so you can wander into the install folder and fire up Odin to flash the modified 3e recovery if you decide to go that route too.
If I flash a deodexed kb5 will i still be able to flash a custom rom?
Ok so i had ICS passion installed then one day the rom gave me an error telling me encryption unsuccessful. So i followed the instructions to fix it, by putting the partition on the micro sd card (8gb). I then decided to flash back to stock gingerbread with odin. I thought that if I put a galaxy s international rom on the US vibrant it would work, but i was wrong so dont try that. I was stuck on a bootloop and was able to get to download mode. Then i used Odin to flash JFD for vibrant it said i passed but when i booted it did the same. Now im on KB5 and it gave me android system recovery <3e> but i have an error dev/block/mmcblk0p1.
I cannot go to menu, i can access download mode and android system recovery, i also tried to install update zip but it gave me the signature fail.
Please help me back to stock firmware or any stable version. Thank You
http://forum.xda-developers.com/showthread.php?t=1278683 follow the instructions in the thread and remember to flash the bootloaders
You should just Odin back to JFD and go from there. Flashing bootloaders is dangerous, shouldn't be done lightly, but can be done with caution if needed, usually isn't.
try the 1click root method. see if that helps.
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Cwm from rom manager hasn't worked in awhile. Use philz touch if you really want cwm. Or use flashify to get twrp
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
Like Josh said just use Flashify https://play.google.com/store/apps/details?id=com.cgollner.flashify
It's still updated and works great. To many have had issues with ROM manager or Goo.
Sent from my SCH-I545 using Tapatalk
hydeburns said:
So a while back I decided to start my phone fresh. remove root. full factory reset. of course the plan was to re root install a recovery and get back to flashing far too many roms. but ive hit a snag and I cant find my fix.
Starting off, to return to stock I odin flashed the official mdk firmware from back in the day. And then did a factory restore to completely remove everything.
Once done with that I odin flashed the md2 prelease firmware to get root with the motochopper method. updated su binaries and then flashed the mdk kernel back.
And all of that seemed to work fine. Apps requiring root seemed to work fine. But when it came time to flash cwm with rom manager the **** started. after flashing the latest cwm and rebooting into recovery I was greeted with the regular android recovery. So I tried flashing it from rom recovery. That seemed to work. But no roms will flash. Making and restoring a backup kind of worked. But cwn was mainly useless.
So I started over and over with the reverting to stock, factory reseting, and rerooting. ive tried the loki versions of cwm flashing with no luck and have just hit a highly frustrating wall. After near 12 hours trying to figure this out I'm asking for assistance. ive done this before. what the hell is the problem. Help me XDA people. You're my only hope.
Click to expand...
Click to collapse
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
sdsurferbob said:
I was in the same boat all day yesterday - reset to stock using the MDK No wipe tar via Odin, factory restored, flashed MD2, motochopped, flashed MDK, but then could not get any new recoveries to take. Using Flashify I was just able to install CWM 6.0.4.7 (which I had tried doing using ROM Manager, and paid $1.99 for, which didn't work) - halle-frickin-luyah!
Click to expand...
Click to collapse
Thanks guys. I tried all of this with the flashify. Even started off freshly reinstalling stock Mdk and then rerooting with the same method I mentioned earlier. Installing cwm through flashify. And though I can make and restore a backup of my stock rooted Rom. I get the same errors I've been getting trying to flash a custom Rom. I'll try to post a screenshot of the error I get in can when flashing.
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
I check the CWM recovery version on my device and currently I'm running version 6.0.3.2. Could that be the reason I keep getting the error unable to mount the sd card? Does anyone have a current version of CWM recovery that's flashable over ODIN? I'm thinking that's my last resort before attempting to restore the MDK TAR.
Bullhead00 said:
I bought phones for my parents for Christmas. Managed to find two BNIB MDK Verizon GS4s on eBay. I currently have an S4 MDK that I rooted myself with no problems.
I went through using the Odin method to downgrade the kernel to root the device, just like I did on mine. When I downloaded ROM Manager, for some reason it wouldn't allow me to flash CWM, so I used terminal emulator to install it using the Loki method found here:
http://galaxys4root.com/galaxy-s4-r...on-att-or-verizon-galaxy-s4-sgh-i337sch-i545/
After I booted into CWM recovery, I wiped everything (didn't nandroid :/) before installing a stockish debloated ROM - BoneStock 1.1.4 which is what I've been running. When I went to install The ROM zip from my ext sd card, the card wouldn't mount. I can't get my device to mount at all in recovery so I can't even sideload anything.
One thing that I may have done wrong is not flashed the second CWM file to upgrade the recovery to CWM v6.0.4.7.
Currently the phone will not boot passed the Samsung logo. Is there anyway to flash a different version of CWM through recovery? Or would that even fix my problem? I can get into download mode fine. I can still boot into CWM but it's useless at this point.
Could someone PLEASE help me! I feel like I've made a stupid mistake somewhere.
Click to expand...
Click to collapse
MDK TAR sounds like the only way to go. Make sure to get the MDK one though!
Theoretically, there are other ways, such as flashing a new recovery from your current one, but with Loki, that would probably be harder than what its worth.
Does anyone have any clue why I wasn't able to use ROM manager to flash CWM recovery?
ODIN MDK TAR file worked. I still don't know what went wrong and why CWM recovery couldn't mount my SD card so I could flash a ROM.