Related
THIS HAS NOT BEEN TESTED!!! USE AT YOUR OWN PERIL!!! Update: So far i have it working for DJ20 users. Still fighting it with some DL17 users. Make Odin files first!!!
Hey folks,
Jt1134 (awesome Samsung Fascinate dev) and I were discussing the current plight of the Samsung Continuum. Looking over things, it looks like we can make clockwork recovery work for you guys. Please note, I DO NOT have a Samsung Continuum, so I cannot test this procedure. IT IS ESSENTIAL that someone makes ODIN images PRIOR to this! While it should work, lets be safe, folks.
Once again, let me repeat, I do not have a Continuum to test this, so make sure you have proven, tested Odin images at your disposal. I found no kernels for the Continuum made, so I need to baseline for what works.
I made this cwm recovery Odin image for folks to try.
http://adrynalyne.us/files/odin/cont_cwm_recovery_2.tar.md5
This alone WILL NOT give you clockwork recovery. The next step is to download Rom Manager, choose flash clockwork recovery, and from the choices, choose Samsung Fascinate.
This downloads an update.zip to your sdcard. Rebooting from Rom Manager should boot into recovery. Manual booting into recovery takes you to stock recovery. You merely need to install update.zip from the menu for clockwork recovery.
I know bubby is porting something better, but in the meantime, hope this helps.
FOR DL17 users, try putting this on your sdcard and see if clockwork works. (need to Odin this recovery first)
http://dl.dropbox.com/u/2056318/update.zip
Just did this and it worked i got clockwork mod recovery!! Thanks alot
Cant mount vold on di17.
Sent from my SCH-I400 using XDA App
Yeah im on DJ20 maybe thats why it worked with out a problem for me.
whats the difference in the dj20 and di17? how do i know which one mine is?
actually i see that im showing DL17
DL17 is after the update that was just released, Dj20 is before.
Yeah apparently the code needs to be tweaked for DL17 still.
Interesting.... I am officially on DL17, and your clockwork still works wonderfully? At least I think xP it boots into it through cwm, and no errors?
Sent from my SCH-I400 using XDA App
One thing i did notice is that when the phone is off and i go to boot into revocery it goes into the stock recovery, But when i open rom manager on my phone and have it boot into recovery through that it goes into clockwork mod and works good.
Is it suppose to be like that? Any one know?
CrazyKnight122 said:
One thing i did notice is that when the phone is off and i go to boot into revocery it goes into the stock recovery, But when i open rom manager on my phone and have it boot into recovery through that it goes into clockwork mod and works good.
Is it suppose to be like that? Any one know?
Click to expand...
Click to collapse
from stock recovery you have to apply the update.zip manually to boot into cwr
Ahh ok thats what i thought it was just wanted to make sure before i started messing with things.
Updated......
adrynalyne said:
Updated......
Click to expand...
Click to collapse
Thank you adrynalyne for coming back for us It really is appreciated!
I can confirm that this works... Red CWM up and working xD There is a non-important warning saying that it can't find the bitmap, but that isn't neccessary
can anyone give me some pointers on the options when using odin to flash this recovery image?
DL17 version here...
dottat said:
can anyone give me some pointers on the options when using odin to flash this recovery image?
DL17 version here...
Click to expand...
Click to collapse
Follow this: http://goo.gl/oMc7H replacing modem with the file adrynalyne posted
Thanks.. it was the step to use "PDA" instead of phone that ran me aground last time i tried this.
1. Odin this fie, using PDA section:
http://adrynalyne.us/files/odin/cwm_recovery_test4_adryn.tar
2. Download this file and put it on the root of your sdcard:
http://dl.dropbox.com/u/2056318/update.zip
3. Boot to recovery, either from manual three button method (down, up vol +power) or using something like quick boot on the market.
4. Apply update.zip.
5. Profit!
Thanks:
bubby323
imnuts
Logan302
Trailblazer
jt1134 (his update.zip, very awesome)
use at your own risk. I am not responsible for anything you do to your device!
OK I'm in trouble now, I odin the first file and copy the update.zip to the sc card. After I do a manual boot to the boot loader the camera button does not activate anything I can not start the update.zip or reboot. If I pull the battery and reboot it just boot back to the boot loader again. Please advice I need my phone back soon.
Thanks
Update:
if I odin the "cont_cwm_recovery_2.tar.md5" file from the other post the camera button will activate the update.zip but got some error but reboot just fine. I think the odin file made in this post is for device that has the home button on the phone and no camera button map. Still no CWM but at least the phone boots normally now.
kdoweb1 said:
OK I'm in trouble now, I odin the first file and copy the update.zip to the sc card. After I do a manual boot to the boot loader the camera button does not activate anything I can not start the update.zip or reboot. If I pull the battery and reboot it just boot back to the boot loader again. Please advice I need my phone back soon.
Thanks
Update:
if I odin the "cont_cwm_recovery_2.tar.md5" file from the other post the camera button will activate the update.zip but got some error but reboot just fine. I think the odin file made in this post is for device that has the home button on the phone and no camera button map. Still no CWM but at least the phone boots normally now.
Click to expand...
Click to collapse
Lol... Flash the original recovery that is in this post again... Then use the soft key pad (all the way to the left) to make selections... The camera button is no longer used...
Sorry, yes, the key mappings are a bit wonky.
can yyou say HE FREAKED OUT! LOL!! flash orignal VZ image your good if you dont know what your doing unless you can afford a new phone i would research and play with an old phone first..
OK, I odin back the test 4 file and apply the update.zip install the rom manager form the market place and flash CWM 2.5.0.4 but how can boot to CWM?
kdoweb1
Check this post the first link gives step by on how to get CWR installed and the 2nd how to install the ROM.
http://forum.xda-developers.com/showpost.php?p=11188059&postcount=17
odpz said:
kdoweb1
Check this post the first link gives step by on how to get CWR installed and the 2nd how to install the ROM.
http://forum.xda-developers.com/showpost.php?p=11188059&postcount=17
Click to expand...
Click to collapse
Thank you, I'll give it a try when I get home. What is the difference between official version of ClockworkMod Recovery for Samsung Continuum rather than a custom port made by adrynalyne? From what I can gather from the read is that the official will boot directly to CWM everytime rather than having to apply the update.zip to boot it CWM? In any case I'm much more comfortable flashing ROMs and kernel now that I can do backup in CWM.
Thanks again
Ok... I got this to install and I am able to apply the update and get into clockwork recovery. How do I get it only load CWR each time now instead of the factory recovery?
I keep having to use the default recovery to get into CWR...
I love the fact i am finally able to make a solid backup of this damn phone though!
dottat said:
Ok... I got this to install and I am able to apply the update and get into clockwork recovery. How do I get it only load CWR each time now instead of the factory recovery?
I keep having to use the default recovery to get into CWR...
I love the fact i am finally able to make a solid backup of this damn phone though!
Click to expand...
Click to collapse
The only way to get that to happen, is to apply a voodoo kernal.
Sent from my space time Continuum using the XDA App.
I have the voodoo kernel installed.. didn't seem to work...
**edit.. perhaps I need to allow the lag-fix to change the partition data first.. i'll try that and report back.
dottat said:
I have the voodoo kernel installed.. didn't seem to work...
Click to expand...
Click to collapse
When you reboot to recovery, how are you doing it? ROM Manager can not properly boot into CWM on voodoo kernels
I tried to boot it using both volume keys. Now it's stuck in a bootloop saying something like "miscooperation"
dottat said:
I tried to boot it using both volume keys. Now it's stuck in a bootloop saying something like "miscooperation"
Click to expand...
Click to collapse
oops, i hit the thanks button >.< oh well...
Anyway, did you do a battery pull after you activated voodoo? You had to let it convert your whole system! I don't know what else could be wrong.
Yeah.. I let it convert.. it booted up fine when done. I then shut it off and tried to reboot and go into the CWR menu. It then boot looped. I was able to manually get to CWR through the stock menu and am in the process of restoring right now....
dottat said:
Yeah.. I let it convert.. it booted up fine when done. I then shut it off and tried to reboot and go into the CWR menu. It then boot looped. I was able to manually get to CWR through the stock menu and am in the process of restoring right now....
Click to expand...
Click to collapse
oh... Well, that's good at least.
Ok.. got it to flash the voodoo kernel again and now all I get is the Cwm recovery menu. Not sure what i can do to get this thing to load an OS again.
Signature verification fail on update.zip
Edit:
Downloaded update.zip from addictive tips. Booted into the red colored clockwork once. Flashed DL17 Root Deodex etc. Can't boot into that recovery again. Been trying and trying.
AWFUL
So I did everything as instructed and used odin to flash recovery. now I'm trying to get CWM on my device going into boot mood. Error message says signature failed and that "update.zip gone" HELP!!!
jlt8604
I would copy the update.zip again on the root of your sdcard and try the manual recovery procedure.
[MOD] EZ Clockwork 2.5.1.2 Install>Easily flash to 2.5.1.2 to flash old mods/themes
THIS IS FOR THE MT4G/Glacier UPDATED 04/22/2011
The primary use for this mod is to be able to easily switch between CWM Recovery 3.0.2.4, 3.0.0.6, 2.5.1.2 and the MT4G/Glaciers stock recovery.(Thanks to Amac1222 for the idea of adding the stock recovery to this)
In order to flash a rom or mod you must be rooted and running a recovery other than stock. With this zip, you can install CWM 2.5.1.2 so that some of the older scripted mods/themes will work. This zip also still includes CWM 3.0.0.6 and the stock recovery for anyone that wants to run those recoveries for some reason.
Using this Mod/Method you can switch between the latest version of CwM 3.0.2.4, 3.0.0.6, 2.5.1.2 or the stock recovery with the push of a couple buttons(you cant flash things from the stock recovery).
This zip does not modify Rom Manager in any way but only places the both CwM v3.0.0.6, v2.5.1.2 and the stock 2.2.1 recovery image in the correct spot on your sd card and renames it in order for it to be flashed using Rom Manager.
Instructions for use
Make sure you have the newest Rom Manager installed. This is included in most roms but can be found in the market also. The free version works fine..
Download the zip at the bottom of this post and place it on your sd card.
Open Rom Manager and choose "Reboot into Recovery"
From recovery flash/install the zip file you placed on your sdcard.(If you downloaded straight to your phone you will need to go into the download folder first and then) choose "Recovery_2.5.1.2_to_RomManager.zip" and install it. No need to wipe anything.
Now reboot your phone and then go back into Rom Manager and go to "All ClockworkMod Recoveries" This is where you flash the recoveries from.
To flash CwM 2.5.1.2 recovery just choose the option for 2.5.1.4
To flash CwM 3.0.0.6 recovery just choose the option for 3.0.0.5
To flash the stock recovery just choose the option for 2.5.1.3
Rom Manger will not show the correct matching "Current Recovery #" after using this. ie: It will say 2.5.1.4 in Rom Manager but if you boot into recovery it should be 2.5.1.2
You can now boot into recovery. (If you chose the 2.5.1.3 option hold volume up and power button at same from the red triangle screen to enter the stock recovery)
You should now see the new recovery.
CWM 2.5.1.2 Recovery has GREEN text
CWM 3.0.0.6 Recovery has ORANGE text
Stock Recovery has BLUE text
Keep in mind that you can switch recoveries easily in order to do things like flash that quick mod that has a old script. Just dont forget to flash back to the correct recovery when you try to flash a rom again.
Please hit the "THANKS" button if you are using this and want to show your gratitude.
[DOWNLOAD HERE]
MY OTHER THREADS​
MT4G BUTTON MODS___ EZ ADB/FASTBOOT SETUP ___GENIUS BUTTON FOR CM7​
Thanks for staying so on top of keeping this updated Drew! This is definitely the most user-friendly and accessible method for the newbies. You should email the developer of ROM manager to see if they can build in an option for Clockwork 3.
This is exactly what I was going to ask CM7 thread. Die looking for the stock recovery to re-calibrate my battery. BIG THANKS!!!
Phateless said:
Thanks for staying so on top of keeping this updated Drew! This is definitely the most user-friendly and accessible method for the newbies. You should email the developer of ROM manager to see if they can build in an option for Clockwork 3.
Click to expand...
Click to collapse
I dont think it will be added into Rom Manager anytime soon but I could be wrong. Our phone is one of only 4 or 5 phones that require a different recovery to run Gingerbread so most phones dont have this issue. Until most all of the roms require 3.0.0.5 type of recovery to flash, I just dont see it happening. I think Koush is far to busy with other things right now.
Awesome work, Drew, downloading now. I had just received my millionth MT4G replacement (yes, I am searching for the highly elusive perfect MT4G), and was attempting to get it set up for CM7 over the weekend, and although I had used your method before and was able to get it working, this time it wouldn't work, and I finally got it working through procedure 3 on the other thread, I believe, by Phateless. Hitting the thanks button now, and I appreciate your keeping on top of things. Cheers =)
I appreciate the thanks and I'm glad its working again. I just found out the other one had stopped working last night and I couldnt edit the post with the fix since the thread it was in had been closed. At least now if we run into any more issues everyone has a place to post and let me know.
Good luck finding the MT4G for you. I got lucky, mine is as close to flawless as I think I can get. Good screen, can OC to max with no probs. My back button does creek sometimes ever so slightly but I do push it like 20 times more than any other button so I can live with that.
Thanks again for using this mod!!
m00nshake said:
Awesome work, Drew, downloading now. I had just received my millionth MT4G replacement (yes, I am searching for the highly elusive perfect MT4G), and was attempting to get it set up for CM7 over the weekend, and although I had used your method before and was able to get it working, this time it wouldn't work, and I finally got it working through procedure 3 on the other thread, I believe, by Phateless. Hitting the thanks button now, and I appreciate your keeping on top of things. Cheers =)
Click to expand...
Click to collapse
The download link seems to be broken
Sent from my HTC Glacier using XDA App
acureto said:
Will we need to do this method every time we change roms?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You only would need to change the recovery if you want to flash a rom that isnt compatable with the recovery that you are currantly running,
For example if you are running a rom like Ice Glacier and Clockwork recovery 2.5.1.2 and you want to install CM7. You cant do it without flashing ClockworkMod 3.0.0.5 first. Same thing if you are running CM7 and Clockwork recovery 3.0.0.5 and want to install a Froyo Rom you must flash back to 2.5.1.2 before installing the rom.
You can do both of those things from Rom Manager by following the instructions in the first post.
Once you have installed the zip you should not have to install it again. It places the recovery images on your SD card so they shouldnt get erased when you flash a different rom.
just kidding on the download link being broken, awesome job it works great!
acureto said:
The download link seems to be broken
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
Link wasnt broken but Mediafire doesnt play nice if your downloading str8 to your Phone. I replaced the link with a different one so try it now.
Thank you so so so muccch!!!! It worked like a charm. But wow to think I was putting up with ice glacier cuz the process of going to cwm3 just seemed so inconvenient, boy did you make things easy.
And wow cm7 is the ishhh. I can't believe how smooth and fast everything is. And its like customization galore. Again thank you so much.
Sent from my HTC Glacier using XDA App
Great idea putting the stock recovery also - thanks. That makes it much easier to deal with if there is a need to convert back to stock to return a phone under warranty.
I could not see how I had gotten the ROM Manager update however, as I had never seen it coming through a market update. Then I recalled it comes with the newer Builds, so apparently the new Manager one is in them now.
Update - Installed this on another MT4G I got for a Family Plan member ($49.95 with two year extension). I had it flash CMW 2.xxx, went into recovery (green), and then booted back up. Open modified ROM manager, flashed back to "2,5.1.1" and booted back into recovery.
Got the (usually) dreaded red triangle, and then vol up/power button - and there was the old stock recovery in all its blue glory!
Going to leave it that way for now unless I need to flash some more zip files before I ship it off (recipient is 2600 miles away). I don't want to have to deal with the boot-up to recovery when connecting to the charger when device is off issue.
Again - great work
gaww said:
Got the (usually) dreaded red triangle, and then vol up/power button - and there was the old stock recovery in all its blue glory!
Click to expand...
Click to collapse
TrueBlue - I think this note might be useful to add to your guide. As a noob to all of this i didn't know you need to press VOLUME UP and then POWER in order to get into stock recovery the first time i did it. It scared the crap out of me and i thought i bricked my phone!
So it might be helpful for people who are doing it for the first time to know that the phone and hazard sign are expected.
shortskoolbus said:
TrueBlue - I think this note might be useful to add to your guide. As a noob to all of this i didn't know you need to press VOLUME UP and then POWER in order to get into stock recovery the first time i did it. It scared the crap out of me and i thought i bricked my phone!
So it might be helpful for people who are doing it for the first time to know that the phone and hazard sign are expected.
Click to expand...
Click to collapse
Actually it is in the OP right where I tell you to boot into recovery. You must have missed it. Maybe I will make it bold print.
TrueBlue_Drew said:
Actually it is in the OP right where I tell you to boot into recovery. You must have missed it. Maybe I will make it bold print.
Click to expand...
Click to collapse
Yes, sorry you are correct! Bold would be nice for people who can't read like me
Thanks for the help, and great work man.
Drew, THANKS A LOT.
Question: When you flash a new ROM, do you have to reflash the recovery ZIP?
Jaskwith said:
Drew, THANKS A LOT.
Question: When you flash a new ROM, do you have to reflash the recovery ZIP?
Click to expand...
Click to collapse
No, you do not need to reflash this everytime you flash a rom. You should only need to flash it once.
Jaskwith said:
Drew, THANKS A LOT.
Question: When you flash a new ROM, do you have to reflash the recovery ZIP?
Click to expand...
Click to collapse
TrueBlue_Drew said:
No, you do not need to reflash this everytime you flash a rom. You should only need to flash it once.
Click to expand...
Click to collapse
As long as you stay on a Gingerbread ROM you don't need to reflash recovery. If you go back to a Froyo ROM then you need to reflash Clockwork Recovery 2.5.1.2, which can be done through ROM Manager.
Phateless said:
As long as you stay on a Gingerbread ROM you don't need to reflash recovery. If you go back to a Froyo ROM then you need to reflash Clockwork Recovery 2.5.1.2, which can be done through ROM Manager.
Click to expand...
Click to collapse
He asked if he needed to flash the recovery ZIP when he flashes a new rom.The answer to his question is NO. He did not ask if he needs to flash a new recovery. If he wants to flash a different rom then, yes he needs to make sure he is using the correct recovery for the Rom he is flashing.
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Taxmaster said:
Hello all,
Quick background - my wife's T-Mobile S4 went kaput on our honeymoon last night, but I was at least able to save some of her data. The problem now goes to installing a new ROM on her device.
I have wiped EVERYTHING and formatted the data, but when I install ANY ROM (I've tried multiple), I always get the E: Unable to mount '/data" error. Normally, I would just ODIN the stock tar, then install a custom recovery again and then the ROM, but I only have my work computer for the rest of my honeymoon and I don't have administrative access to run ODIN (you might not think it requires it, but if you're only a standard user then you cannot bypass UAC to run it).
Does anyone have any ideas on how to get this to mount? The phone will not boot past the "Samsung Galaxy S4" screen. I've tried going into TWRP and mounting Data but it will not work.
Any help is greatly appreciated! Please keep in mind that I don't have access to ODIN!
- Taxmaster
Click to expand...
Click to collapse
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
elesbb said:
Sounds like a twrp issue. Try grabbing the cwm flash able zip and adb push to the sd card and then use twrp to install it. I've read so many issues about twrp. I recommend staying away from it. Philz touch recovery is really awesome too.
Sent from my SGH-M919 using Tapatalk 2
Click to expand...
Click to collapse
Hello! I actually downloaded Philz touch recovery in both .zip and in .md5, so that is what I intend to go with. The issue is how I push it using adb, as I believe I need to install something in order to do so, but I don't have any administrative privileges! This is what's preventing me from running ODIN in the first place!
Can you confirm that I can push using adb without installing anything?
Thank you! - Taxmaster
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Monkz said:
I had this issue. Odin flashing and then booting into "STOCK RECOVERY" after flashing and then a factory reset in the stock recovery followed by a fresh re-flash from Odin worked to get my phone back up and running again.
I don't know how you are going to be able to fix it by just flashing a recovery. I tried for hours and could not get it to boot from just recovery alone.
Click to expand...
Click to collapse
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Taxmaster said:
What you noted would be my plan if I had admin rights to my computer, but since I cannot get ODIN, I'm screwed at the moment. I'm hoping someone can assist with the "adb" proposal, however I'm not sure one can download/run adb without installation or prompt from UAC
Click to expand...
Click to collapse
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
lordcheeto03 said:
I don't believe admin is required for adb... You could always try it... worst thing that could happen would be nothing.
Click to expand...
Click to collapse
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
elesbb said:
Using ADB does not require admin privelages, however, if your computer does not have the necessary drivers to detect the device in recovery, then you will have to install the drivers, which then yes UAC is required. HOWEVER, if you have another phone or device that supports MicroSD cards, you can just pop in the MicroSD into a working device and transfer the zip that way, then transfer back the sd card and flash
Click to expand...
Click to collapse
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Taxmaster said:
I did exactly what's noted above --> took out the SDcard, put it in another phone, transferred over the .zip, put it back in her phone, went to TWRP, wiped everything on the device, installed the .zip, and rebooted into recovery from TWRP, and then the new recovery booted! I did another wipe/factory reset and then installed a ROM, but when I hit reboot, it didn't reboot past the Samsung Galaxy S4 splash screen , and to make matters worse, when I go to enter recovery pressing home+up+power, it says "Recovery Booting ...." in the top left corner but it won't boot into recovery!!!
Thoughts?
If someone could strip administrative privileges off of a version of ODIN v3 for me, that would be great! I don't see how else to get around this now!
-Taxmaster
Click to expand...
Click to collapse
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
lordcheeto03 said:
Out of curiosity, are you flashing a ROM for the T-Mobile S4? If no, are you using a T-Mobile kernel? I only ask because a kernel for a different device will normally cause you to not be able to pass the initial Galaxy S4 screen... Also, as far as TWRP goes, sometimes it doesn't go right into recovery. If it fails to enter recovery after a reasonable amount of time, just hold power to turn it off and try again. I've had to do it 2-3 times at least just to successfully enter TWRP.
Click to expand...
Click to collapse
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Taxmaster said:
I am installing a T-Mobile S4 ROM that uses a custom kernel. The ROM before was the same ROM just a lower revision, same kernel.
With respect to TWRP, I thought it was all gone now that I installed the CWM touch version. I've tried doing it a million times and cannot get back into either TWRP or CWM. At this point, the only thing I can do is turn on the device to see the "Samsung Galaxy S4" screen, attempt booting into recovery but never make it past the screen saying "Recovery Booting", or enter Download Mode but I cannot use it since I can't run ODIN on my work laptop .... stupid admin privileges!
Click to expand...
Click to collapse
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
elesbb said:
Not sure what happened there.. very strange. But seems as if you have no recovery xD lol Maybe heimdall will work. Never used it not sure if it needs UAC to work. But dont use TWRP anymore
As far as your situation goes, maybe if you have the time and fast enough internet, see if you can download a linux distro (i recommend fedora as it is small and light) then make a bootable USB from that distro (if you have a flash drive) then use Heimdall in linux to flash the tar image.
Or just wait to get home. not sure how long your honeymoon is xD
Click to expand...
Click to collapse
I think I just need to accept that fact that I have been had and that the only thing I can do is wait until I'm home to use ODIN. Absolutely asinine in my opinion, however it seems the only logical conclusion at this point.
If anyone else cares to chime in with suggestions, please let me know!
-Taxmaster
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
coolastar said:
I have had the same problem several times. The only way I have been able to boot up is to completely format data and either restore from backup or reflash a new ROM. If I wipe the dalvik cache after doing so however, it will not boot (hangs at the galaxy s4 screen like you said) and I will have to reflash or restore a 2nd time. (I'm using twrp too, but will switch to cwm if this happens again)
I m curious. Have you run into this problem again? Seems like every time my phone shuts off and tries to boot I have to restore from a backup that is days or weeks old. Super annoying. The first time this happened I restored to stock from Odin and did not use any backups in the hope that it would solve my problem and prevent it from happening again. No such luck.
Click to expand...
Click to collapse
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
Same, TWRP just has too many problems.
CWM is much more reliable.
Sent from my SGH-M919 using xda premium
Taxmaster said:
I ended up having to wait until I got home to use ODIN. I ODIN'd up the stock .tar and then installed Philz touch recovery (CWM-based), then I did a full wipe of everything and installed a ROM. Problem solved.
With that noted, I abandoned TWRP and am now only using CWM on my wife's phone.
Click to expand...
Click to collapse
If you were using TWRP 2.6.0, that could have been the problem. I reverted back to 2.5.0.2 and like many others, have had no issues. If you had a TWRP backup, that might have fixed it early on.
Hi guys, I managed to do something I've never heard of. To be fair, I try to follow directions pretty well, so I don't screw things up too often, and I'm not sure what to do now. Any help or guidance would be appreciated.
The symptom is that the phone will boot witht eh Samsung boot animation, I will see the Clockworkmod icon at the bottom, some Clockworkmod version information, then the phone will reboot. This will happen presumably indefinitely. I have watched it do it 3 times in a row and then pulled the battery. Post Philz, I get Android tablet icons instead of Clockworkmod icon and version info.
I loaded Whompasaurus http://forum.xda-developers.com/showthread.php?t=2039564 to my phone yesterday and I was about to load Venom http://forum.xda-developers.com/showthread.php?t=2121063 to my phone this morning (I had just copied it to the SD card). I told the phone to reboot into recovery by pressing the power button and selecting the option "reboot, recovery". The phone is now stuck rebooting attempting to enter recover and failing, or so it appears. I upgraded the Clockworkmod version to 6.0.4.3 yesterday, and that did act a little weird in my opinion, but since I had never done that before, I wasn't sure what to expect.
When I told it to upgrade in the Clockworkmod app, the phone powered off and I had to remove the battery to turn it back on. I booted to recovery and it said it was now at 6.0.4.3, so I booted normally. Back in the app it said it was 5.something. I kept poking around and it eventually asked for root access, which it hadn't before, and when I told it to upgrade the recovery this time, it actually rebotted the phone rather than turn it off.
I reflashed the CWM 6.0.4.3 recovery with Heimdall per these instructions (why aren't there proper instructions for Odin?!?!?! ermahgerd!!) via this link http://wiki.cyanogenmod.org/w/Install_CM_for_l900
That was successful but did not affect the symptoms.
I upgraded to Philz recovery thinking maybe I had to use a different recovery to reset the "boot to recovery" flag. I used this file and Odin, after resetting the Samsung driver: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900/philz_touch_6.26.6-l900.tar.md5
The process was successful, but did not change the symptoms. Instead of seeing a Clockworkmod icon and version info at the bottom, I see what looks like android icons at the bottom, and then the phone reboots.
What can I do to fix my phone? I can boot to downloader mode fine. I would prefer to use Odin, but it seems I have Heimdall set up and working too.
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Team Win FTW!!! That fixed it!
jlmancuso said:
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there something special about 2.6.x? I saw that there's a 2.7.x available now. 2.6.x doesn't seem to like my 64GB SD card, or maybe something else is going on. I factory reset a few times and will upgrade to the latest TWRP and try to flash that latest Venom ROM now and see what happens.
*Edit* No, there's SDCARD, SDCARD1, and EXTERNAL_SDCARD and I didn't check all of them, that's all. Oy, oy, oy.... But I'm up to 2.7 and installing Venom now....
Are asking for ROM recommendations still a no-no?
Yeah still pretty much a no no. I have used all the roms here and they are all pretty good.
Now I do suggest that you flash philz 6.07.9 for your recovery. First is that it properly flashes 4.4 and TW 4.3 roms. Second it makes proper backups. Twrp still has issues with aosp 4.4 and TW 4.3.
Sent from my SPH-L900 using XDA Premium 4 mobile app