Related
Hey guys hope someone can help me out here. I just updated my phone to the latest OTA Rooted ROM and everything was working fine. Then I used Rom Manager to download the latest Fresh 3.0.?? ROM. When it downloaded it asked if I wanted to backup ROM and wipe data. I checked both on. Then phone rebooted and it wont get past white HTC Evo4G screen. I did vol down and power and I go to Recovey and again it freezes on this screen. I cant access my sd card to put any recovery stuff on the phone. How do I get past this?? This sucks
rgvsdigitalpimp said:
Hey guys hope someone can help me out here. I just updated my phone to the latest OTA Rooted ROM and everything was working fine. Then I used Rom Manager to download the latest Fresh 3.0.?? ROM. When it downloaded it asked if I wanted to backup ROM and wipe data. I checked both on. Then phone rebooted and it wont get past white HTC Evo4G screen. I did vol down and power and I go to Recovey and again it freezes on this screen. I cant access my sd card to put any recovery stuff on the phone. How do I get past this?? This sucks
Click to expand...
Click to collapse
I had the same issue this morning loading the new Fresh Rom. "Stuck at White HTC EVO" screen. Just do a battery pull to restart your phone and let it boot up normally. It should be able to load after that.
Thanks a lot fuzion. I could have sworn I tried that last night but I guess I didn't. So I guess no Fresh ROM ?? Anyway to get it on ?
You could try loading one of the PC36IMG zips on your sd using an adapter to go back to stock and start over
Well I got my phone back on and working with the 2.2 OTA rooted back the way it was. I go into ROM manager and I made sure to do the ClockworkMod Recovery install. When I turn on the phone with vol down + power I select Recovery it just freezes on the Evo 4g screen. Never takes me to the recovery menu like I used to have. Anyone have any idea why??
Let's do a checklist:
1. Full root including NAND unlock (i.e. NOT Unrevoked)?
2. Installed and re-installed latest ROM Manager, and then latest CWM?
3. Copied Fresh 3.1.0.1 to root of SD card?
4. Booted into recovery using either CWM option or power+volume up?
5. You don't have an old PC36IMG.zip on your SD card, do you?
6. If you can get into recovery, do all your flashing from there, and DON'T FORGET to do data, cache, and dalvik wipes.
7. If all else fails, maybe use CWM to flash Amon RA instead and try that way.
8. If all THAT fails, go back to toast's guides and re-root everything.
Other long shots: Install Titanium Backup and use that to install BusyBox. I have no idea if this would help, maybe it's totally unrelated. Also, you could use an app called Quick Boot to reboot into recovery, but if selecting the reboot option from CWM doesn't work, I don't know why QB would.
And one more thing: Don't be throwing the term "bricked" around when you're clearly not even close to bricked.
so i just ran LGNPST to get to ZV7, then i updated to ZV8
once i was on ZV8, i rooted and unlocked bootloader successfully using GAIO v1.50
i'm having problems booting into my custom recovery TWRP, after i install the custom recovery using GAIO
i try to shutdown the phone and boot into recovery, but every time i try i get a quick screen of the lg logo then it goes black and it doesn't load the os.
i cant even get to fast boot, so what i've done from here (the past 5 times) is i run LGNPST again and start all over again.
i tried the FreeGee method of installing the custom recovery but the results are the same..
any ideas?
avpmusic said:
so i just ran LGNPST to get to ZV7, then i updated to ZV8
once i was on ZV8, i rooted and unlocked bootloader successfully using GAIO v1.50
i'm having problems booting into my custom recovery TWRP, after i install the custom recovery using GAIO
i try to shutdown the phone and boot into recovery, but every time i try i get a quick screen of the lg logo then it goes black and it doesn't load the os.
i cant even get to fast boot, so what i've done from here (the past 5 times) is i run LGNPST again and start all over again.
i tried the FreeGee method of installing the custom recovery but the results are the same..
any ideas?
Click to expand...
Click to collapse
the same thing happened to me a while ago. if i remember correctly, what i did was after lgnst, i rerooted my phone, install cloworkrecovery from the play store. use the app to boot into recovery, then wipe cache and dalvik cache or whatever its called. hope this helps!
javskies said:
the same thing happened to me a while ago. if i remember correctly, what i did was after lgnst, i rerooted my phone, install cloworkrecovery from the play store. use the app to boot into recovery, then wipe cache and dalvik cache or whatever its called. hope this helps!
Click to expand...
Click to collapse
I downloaded rom manager from play store and it says my phone was unsupported
Any ideas?
avpmusic said:
I downloaded rom manager from play store and it says my phone was unsupported
Any ideas?
Click to expand...
Click to collapse
If it says your phone is unsupported then you are trying to load cwm on your phone which shouldn't be needed as free gee should load it on your device(if I remember correctly. Been a while since I unlocked). He is saying that he used it to boot into recovery not load cwm.
I assume that's what he is saying and you are doing if I'm wrong feel free to correct.
You could also install ROM toolbox scroll to the very bottom of the first page click Rebooter and click reboot recovery. That should hopefully take you to cwm where you can flash recovery.
Sent from my LG-LS970 using xda app-developers app
AOKPBrownNoser said:
If it says your phone is unsupported then you are trying to load cwm on your phone which shouldn't be needed as free gee should load it on your device(if I remember correctly. Been a while since I unlocked). He is saying that he used it to boot into recovery not load cwm.
I assume that's what he is saying and you are doing if I'm wrong feel free to correct.
You could also install ROM toolbox scroll to the very bottom of the first page click Rebooter and click reboot recovery. That should hopefully take you to cwm where you can flash recovery.
Sent from my LG-LS970 using xda app-developers app
Click to expand...
Click to collapse
i tried using rom manager to kick me into recovery (chosing trwp recovery before hand with freegee) before and it did the same thing,
rebooted, showed lg logo for a split second, then black screen. i just did the whole process again of using LGNPST to get to ZV7, then i updated to ZV8 then free gee to give me twrp then rom toolbox to kick me into recovery and its the same thing! black screen!
i also tried BEFORE doing freegee to go into recovery after the LGNPST to see what happens, and it just took me to normal recovery.
so my issue has to be with freegee..
should i LGNPST again to get me back up and running and THEN uninstall freegee, reinstall it, and choose clockworkmod as my reovery?
maybe is trwp just failing to load? what are you guys using?
{guide} soft-brick fix
Happened to myself as well. Follow these steps from AdriVelazquez.
Fixed it in a jiffy!
Accessing Recovery Screen (First Step if you have bricked your phone)
This is our initial step for any problems that might arise. If you can access recovery, usually you're in a perfectly fine situation.
1. Power off your phone by holding Volume down & power at the same time.
2. When the screen shuts off, switch to entering fastboot by holding Volume Up & Power. Release immediately once you see a black screen with some text on the bottom.
3. You should see a black screen with some text at the bottom.
4. Press volume down 2x and then the power button.
5. You should see either TWRP or CWM recovery.
6. Wipe Cache, Dalvic Cache, and Factory Wipe
7. Flash new stock zip. Wipe caches again.
8. Restart.
My issue is after I use freegee to unlock the bootloader and to put on twrp recovery
At that moment when I restart my phone won't boot into the android os or fast boot
When I try to enter fast boot by holding power and volume up I never see any text at the bottom of screen it just shows the lg logo then a compete black screen
at this point I'm unable to even enter the OS. So the only thing I can access thankfully is Download mode.
I had the same problem. The way I fixed it was to lgnpst back. Root the phone and then run freegee. Then when I entered the bootloader it did the same lg symbol black screen thing. I held the volume up and down along with power while it was at the black back lit screen for about 20 seconds till it was completely off. Then I plugged it into my computer or you can use a charger to. Wait a few seconds and a battery animation should show up. Leave it on charge for a few minutes and then take it off and turn it on and you should be good to go. I can't guarantee it is going to work but it worked for me and I found it just by trying different things. I also read about someone else mentioning what I did in another soft brick post. I also read that shelnut2 has a special freegee version that you can only get from him. You can try him in irc. I read he dose not want it posted because it could permanently brick the phone.
-Frank
yeah... this is exact same problem that I had before..
You nees to go optimus g IRC channel and talk to shelnutt2 that you are having problem with unlocking bootloader. He will help you nicely cause he is super nice!
irc: http://webchat.freenode.net
channel: #lg-optimus-g
He told me it is very rare issue but I can tell there are several people having this issue now..
Sent from my LG-LS970 using xda app-developers app
issue resolved!
Shellnutt2 helped me out, i had to flash a special freegee to get everything working!
I have a Samsung Galaxy S3 SGH-I747 (AT&T) that I updated OTA to 4.1.1 a while back. I just decided to root the phone using Odin3 V3.04 and clockworkmod.tar. I tried using clockworkmod at first but couldn't get the phone to go into CWM recovery mode. It just went into stock recovery instead. Reading further, I was told that I need to flash fixboot.tar first, then clockworkmod.tar, then flash CWM_SuperUser_3.0.7.zip file in recovery mode. When I used odin to flash fixboot.tar and rebooted, it boots the Galaxy S3 logo, at&t chime, then goes black with Amber light. It will not boot fully. I then used Odin to flash clockworkmod.tar, rebooted and it also went to blackscreen.I was then able to go into recovery mode and flash the Superuser zip file and reboot but I'm still getting the black screen. What did the fixboot.tar file do to my phone?? Can I reverse this without flashing a whole new rom? I have search the forum for severalhours now with no luck. Any help would be great.
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
xBeerdroiDx said:
where did you get your initial information and tar? as well as the fixboot info and tar?
check out this rooting thread here on xda. the purpose is to flash cwm recovery onto your device. you then boot into the custom recovery you just installed and root from there. instructions are on the thread.
recovery mode is: vol up + home + power. release just the power button when your device vibrates
Click to expand...
Click to collapse
I got it from this link - http://rootgalaxys3iii.com/root-at-t-galaxy-s3/
I am aware of the process you mentioned, but it would not work. It just kept going into standard recovery mode instead of custom recovery so I could never root from there. Thats when I came across this link and thought I needed to flash fixboot.tar first as it states. It did work! I was able to flash clockworkmod.tar and then root the phone, but what good does that do now that my phone is hosed at the blackscreen...There were two sites that said to use this fixboot method. I should have known better...
I just read your thred. Looks like my problem was letting the phone reboot. Is there any way to reverse the fixboot.tar I used? Maybe there is a 4.1.1 boot.tar that can put things back as they were?
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
xBeerdroiDx said:
via the link i provided, in odin, were you unticking the "auto reboot" box?
i've used that thread method on several S3's with no problems. if you were getting a PASS message then it actually worked.
can you get into recovery now? if so, wipe data/factory reset and wipe cache. reboot.
Click to expand...
Click to collapse
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
OpusxXx said:
I used that method from another site and I was getting a pass. It looks like my issue was letting it reboot. When it didn't go into CWM recovery,I used the fixboot.tar and thats when my phone would not boot past the boot screen. I still have some unsaved material and don't want to wipe the phone. I can get into CWM recovery now. Will doing a data/factory reset wipe everything? If so, is that my only option at this point? I don't want to go to factory and lose everything unless I have to.
Click to expand...
Click to collapse
Well, since I got no response, I did what you said and deleted everything. I still have the same problem. Phone boots to Samsung logo, does jingle and geos to blackscreen with blue light.
Back to my original question. I used the fixboot.tar and it jacked my phone where it only boots to blackscreen with blue light. Is there a fix for this???
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.
Hello,
I have a SGH-T989. I recently rooted it and installed cyanogenmod, with gapps and a custom kernel (AOSP UBER KERNEL). I think the kernel is the problem but i dont know how to attack it. Anyways, my phone is stuck on the cyanogenmod boot screen ( Teh one with the circle and cyanogenmod on the inside) and its not frozen, but wont go past that screen. So i tried booting into CWM Recovery, however, when i would i would get that screen as is i didnt have CWM ( the one with the warning about custom software, where u use volume up to continue and then install cwm with odin). So i just opened odin and installed cwm again, but now when i get into cwm, i see all the options,such as reboot system now, install zip from sd, wipe data, wipe ccache, backup, etc. However, i see it for about 5 seconds, then the screen goes black, then cwm comes up again and then repeat. I can go down like one option and then it goes black, then shows the same cwm screen again. Please help! Im a mad noob btw.
muneer123456 said:
Hello,
I have a SGH-T989. I recently rooted it and installed cyanogenmod, with gapps and a custom kernel (AOSP UBER KERNEL). I think the kernel is the problem but i dont know how to attack it. Anyways, my phone is stuck on the cyanogenmod boot screen ( Teh one with the circle and cyanogenmod on the inside) and its not frozen, but wont go past that screen. So i tried booting into CWM Recovery, however, when i would i would get that screen as is i didnt have CWM ( the one with the warning about custom software, where u use volume up to continue and then install cwm with odin). So i just opened odin and installed cwm again, but now when i get into cwm, i see all the options,such as reboot system now, install zip from sd, wipe data, wipe ccache, backup, etc. However, i see it for about 5 seconds, then the screen goes black, then cwm comes up again and then repeat. I can go down like one option and then it goes black, then shows the same cwm screen again. Please help! Im a mad noob btw.
Click to expand...
Click to collapse
I'd suggest to use odin and flash TWRP 2.6.1.0 in download mode, reboot and go into TWRP and do a full advanced wipe, dont wipe preload or it will fail, if you really want to wipe preload, then go into settings and change it to use rm -rf instead of format, shouldnt really need it tho, after wiping just reflash rom/gapps, wipe cache/davilk and reboot.
Thanks for the response. Im sorry but, how do I do that? is download mode the screen you get to when you hold the power button and volume buttons, and then let go of the power button? That screen is CWM for me, and I cant do anything in that mode due to every 5 seconds it stopping and restarting (CWM itself, not the entire phone). Thanks.
muneer123456 said:
Thanks for the response. Im sorry but, how do I do that? is download mode the screen you get to when you hold the power button and volume buttons, and then let go of the power button? That screen is CWM for me, and I cant do anything in that mode due to every 5 seconds it stopping and restarting (CWM itself, not the entire phone). Thanks.
Click to expand...
Click to collapse
Nope that's recovery, to get into download mode and flash TWRP recovery, make sure you have Odin3-v1.85 and the latest Samsung USB Drivers (Win 7/8/XP) and follow the instructions here, just ignore the part about rooting, get TWRP 2.6.1.0 flashed and then follow above posts suggestions.
Almite said:
Nope that's recovery, to get into download mode and flash TWRP recovery, make sure you have Odin3-v1.85 and the latest Samsung USB Drivers (Win 7/8/XP) and follow the instructions here, just ignore the part about rooting, get TWRP 2.6.1.0 flashed and then follow above posts suggestions.
Click to expand...
Click to collapse
Okay so, i flashed TWRP successfully, but now what do i do? in advanced wipe i wiped cache/dalvik, but now what do i do? is there any way i can go back to stock from here? or get cyanogenmod to work? I... oh sh*t, whilst typing this my phone worked, it just needed a minute for the firstboot of cyanoggin, THANK YOU SO MUCH, I LOVE YOU. Its people like you that make this world a better place. :highfive:
And one more thing buddy, i just wiped the dalvik/cache, i didnt reflash anything, play store seems to be working fine so, i believe i am good to go, let me know if i am missing anything.
muneer123456 said:
And one more thing buddy, i just wiped the dalvik/cache, i didnt reflash anything, play store seems to be working fine so, i believe i am good to go, let me know if i am missing anything.
Click to expand...
Click to collapse
You should be good, just make sure you didn't lose root access, I saw a post in the dev section with someone saying they lost root after flashing UBER kernel, but that might of just been something they did wrong on their end, not sure.