Okay so a little while back my phone had a huge freak out and I had to restore everything to stock in order for it to even turn on anymore. Well I was trying to reroot it the other day and when I installed twrp, my phone would show the twrp screen and then boot loop over and over to that screen while I was trying to get into the recovery. Does anyone know why this could be happening or even better. I fix for my problem.
I'd try to re-flash twrp. Then from twrp, wipe everything multiple times and factory reset. But it could be something with the phone is bad and not repairable
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Did you try restoring to stock using Odin and official Samsung update .tar? And also restoring to stock recovery beforehand? Try that, run the Rom for bit and see if it has any hiccups. If so, I'd say hardware issue. If not, try flashing twrp .tar file from sticky thread on how to root.
Sent from my SGH-I727 using xda premium
Related
I was trying to flash a eaglebloods ginger bread on my g2x... however every time the phone boots up it immediately goes into Clockworkmod Recovery and doesn't boot the OS. I've tried formatting and reinstalling the rom but i still get the same problem of the phone going directly into recovery instead of booting. Please help!
have you ever dropped the phone? Maybe the hardware button (volume down is stuck)is failing? I've never heard it automatically rebooting to recovery unless selected from the recovery to do so.
no i haven't dropped it or anything... the last thing i remember doing to the phone before it started doing this was clearing the cache and davilk cache...then it goes immediately to recovery...i just got the phone too, i hope i didn't brick it or something
you didn't "brick" it look up what that means in Urban Dictionary, before using it. If anything reflash the recovery with NVflasher or try a different rom.
tried reflashing clockwork and still have the same problem
tried a new rom? maybe use the clean up tool from in the dev section.
Re nvflash cwm. This has happened to me several times. Do not try to flash anything else until you nvflash cwm again. If that don't work use the rom for recovery in nvflash that is in the dev section.
Sent from my Galaxy Nexus using xda premium
kwes1020 said:
Re nvflash cwm. This has happened to me several times. Do not try to flash anything else until you nvflash cwm again. If that don't work use the rom for recovery in nvflash that is in the dev section.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Two post above yours he said he re-nvlashed.
Sent from my LG-P999 using xda premium
Im going to try to reflash a different version of CWR and hope that works... crossing my fingers
MAN.... i flashed the latest touch cwm and still no luck... tried new rom (hellfires gb) no luck...!!! just got this phone man! any suggestions welcomed
Try using this NVFLASH technique. It should restore your ROM & recovery to stock.
mt3g said:
Two post above yours he said he re-nvlashed.
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
But the question is did any part of the flash fail. Just like flashing a rom. You can get bad flashes. Happens to me lots of times.
Bottom line flash the rom for recovery through nvflash and it will solve it. I've softbricked myself wayyyy too many times and got it back the same way. If it turns on and shows any graphic its not hard bricked.
andrewNY said:
Try using this NVFLASH technique. It should restore your ROM & recovery to stock.
Click to expand...
Click to collapse
This will resurrect it unless its not actually a g2x.
Sent from my Galaxy Nexus using xda premium
Thank you! this helped a lot!
andrewNY said:
Try using this NVFLASH technique. It should restore your ROM & recovery to stock.
Click to expand...
Click to collapse
you sir, are a gentleman and a scholar! THANK YOU!!!
djmeistro said:
no i haven't dropped it or anything... the last thing i remember doing to the phone before it started doing this was clearing the cache and davilk cache...then it goes immediately to recovery...i just got the phone too, i hope i didn't brick it or something
Click to expand...
Click to collapse
Make sure when you flash you wipe everything too, not just cache and dalvik cache
Sent from Narnia
Ok, here's what I did.
I have had my s3 rooted and running custom ROM's. I stupidly and accidently flashed google wallet as my recovery using ezrecovery. Now the phone only boots into odin mode. Is there a way to get recovery back onto the device so I don't have to wipe it and start over (possibly losing everything on my internal SD card)?
Thanks in advance.
Silly Noob.
I don't think you'll be able to get recovery back. You'll probably need to flash stock with Odin.
Sent from my SCH-I535 using xda app-developers app
I ended up with the same result after flashing a custom recovery incompatible with Imo's Lean Kernel/Kexec.
I used ODIN to flash the Root_66 ROM, and all of my internal SD contents remained intact. After the clean install, I flashed CWM 6.0.1 through EZ-Recovery and successfully restored a backup.
The only thing that didn't restore was the kernel.
Awesome. Lesson learned. Think twice before clicking! Odin'd to route 66 and now have recovery of my back up. Thanks guys!
Actually, I in case anyone does something similar the phone booted rooted just how I left it minus the custom rom. I re flashed the rom and I am back where I was without even having to flash a recovery. Thanks again!
Sent from my SCH-I535 using Tapatalk 2
PLEASE HELP!! I have successfully rooted the device and was doing ok after flashing CWmod recovery 6.0.1 through E-Z recovery app and running Liquid Rom. I managed to be dumb enough to flash CWMod version 5.8.4.9 through Rom manager and when I rebooted my phone it got stuck in boot loop. I am able to get into CWMod 5.8.4.9 but I cannot restore my backup anymore. I can also data wipe and install a new rom, but it all just keeps going into bootloop and I cannot get past the samsung custom unlock screen. It first flashed that, then the android man pops up on the next screen like its loading something and then just keeps looping through the process. I did not use ODIN for any of this process and I dont know how to get myself back tothe point where I can reboot. Any help would be tremendously appreciated, because I'm dead stuck and in a panic. Thanks in advance for any assistance.
Happend to me last night...
I made the same mistake... DO NOT download any recoveries from ROM manager. I found out the hard way... So the problem now is your phone is stuck using the recovery you downloaded. I am not sure of a quick way using that recovery if you can revert back but... My solution got me where I needed to be in order to get going again.
I had to use Odin to root to stock ROM. Yes when you wipe it will destroy your data but not your pictures, downloaded files, and other files you put on there. When I re-rooted with stock all my stuff for CM10, gapps, and the kexec CWM was there.
So use this guide...
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Section 1!!!!! And follow the steps EXACTLY the way it says to.
This is why i have never liked rom manager...
The best solution for us to flash recoveries is ez recovery free from the market. I would use this going forward once you Odin back to stock
Sent from my SCH-I535 using xda premium
Same **** happened to me.
Odin. I lost my pics and internal memory though...
Sent from my SCH-I535 using Tapatalk 2
Everything was fine with the root however I used a font app installer that got the phone stuck in a boot loop (on the rainbow screen). How do I get back to rooted JB?
Did you do a back up of your original rom? You need to get back into recovery...
Sent from my SCH-I535 using xda app-developers app
No I didn't. I didn't see that in the instructions or I missed it. Any thoughts on how to get back to rooted JB?
Well if the font app got you into the boot loop then I don't think you lost root, I would get back into recovery wipe cache and hit reboot... See if that works... Good luck
Sent from my SCH-I535 using xda app-developers app
Unfortunately, I tried that. I think I did an accidental factory reset too but nothing has brought it back from the boot rainbow screen.
Did you unlock using EZ Unlock v1.2? You only mentioned that you rooted.
Sent from my SCH-I535 using xda app-developers app
No, I didn't use that. I followed the instructions to root found here (worked no problem until I met that $&#^%#& app) http://forum.xda-developers.com/showthread.php?t=2046439 I think I can reset using Odin I just don't know what to use
Aight, well did you unlock the bootloader? Your response dictates the suggested route to resolve this.
Sent from my SCH-I535 using xda app-developers app
I did follow the instructions to unlock the bootloader
If that's the case then you just need to boot into recovery and flash a rom. If you were running just stock rooted & unlocked VRBLK3, it's easier to just flash a rooted stock rom like the official VRBLK3 leak here: http://forum.xda-developers.com/showthread.php?t=2034118
Try just flashing that, without wiping, then boot into the rom.
or
If you were on a custom rom, just reflash that rom via recovery and you'll be fine. Unfortunately you lose all your settings of you wipe data in recovery so try reflashing either option without wiping if you absolutely need to try recovering whatever data already exists in your current rom. If this doesn't work, format data, wipe cache then flash the rom.
Sent from my SCH-I535 using xda app-developers app
I will give it a shot and let you know. Thanks so much! I was on stock ROM btw.
Cool, this should work
Sent from my SCH-I535 using xda app-developers app
Ok, this is a zip file. Does it have to be on the phone? If so, how do I put it there?
nctiger said:
Ok, this is a zip file. Does it have to be on the phone? If so, how do I put it there?
Click to expand...
Click to collapse
Yes it does need to be there. If you have an sdcard just drag and drop onto it directly then flash in your custom recovery. Conversely, you should be able to boot into recovery and try connecting your phone to the laptop then dragging the zip over.
The longer method will be to Odin flash VRBLK3 and start all over from there.
Sent from my SCH-I535 using xda app-developers app
I am in Clockwork Mod recovery and my comp is not recognizing my phone as it did earlier.
nctiger said:
I am in Clockwork Mod recovery and my comp is not recognizing my phone as it did earlier.
Click to expand...
Click to collapse
I don't use CWM but did you go to Mounts and Storage and select "Mount /sdcard"? Does it connect now?
Sent from my SCH-I535 using xda app-developers app
I went there but it didn't seem to do anything when I selected mount sdcard and conversely didn't connect either
nctiger said:
I went there but it didn't seem to do anything when I selected mount sdcard and conversely didn't connect either
Click to expand...
Click to collapse
Aight well since that failed, you have to do this the long way: Odin flash the VRBLK3 rooted image from your laptop onto your phone. Choose one of the two images for VRBLK3 and follow the directions.
http://forum.xda-developers.com/showthread.php?t=1984436
Edit: I realize I didn't ask but do you have an sd card?
Sent from my SCH-I535 using xda app-developers app
That worked! Thanks so much. Now, what is the best practice for backing things up so that I don't have this problem again? Should I root first then backup? Do I still have to unlock bootloader? Just wanting to handle this properly from this point forward.
It should be rooted already if you installed the Odin files from MrRobinson thread. It should come with either SuperSU or SuperUser correct? You also should still be unlocked but you can re-unlock using EZ Unlock v.1.2 from the following thread and you're undeniably unlocked. You'll hear a brief audio message if it worked.
http://rootzwiki.com/topic/32456-app-920-ez-unlock-14-easiest-way-to-unlock-your-bootloader/
Also, please perform a nandroid back in CWM so you have something stable to return to if something goes awry in the future. That backup would have cut all this down to one simple step. You don't need to be unlocked to perform a nandroid however you do need to be rooted with a custom recovery.
Lastly, perform an IMEI backup using the "Comprehensive IMEI Backup" thread in the dev section. Do this and save the resulting Synergy zip from backup methods A and B in more than one place not on your phone. This is more so a precaution because flashing things in recovery can and may result in a complete loss of connection with Verizon.
Sent from my SCH-I535 using xda app-developers app
My One has been acting up lately. It started out that I couldn't turn off WiFi. I would turn it off but it would turn itself back on shortly thereafter. It has nothing to do with WiFi optimization or anything like that...I've fiddled with all those settings. Anyway, I updated to 38R thinking it might fix things, but no such luck. So I fire up titanium backup in preparation for a full wipe and find out that my device is no longer rooted. On top of that, TWRP is gone as well. No big deal, reflash TWRP and re-root. Nope. ADB says that TWRP flashes successfully, but when I boot into recovery I get the standard Cyanogen recovery instead of TWRP. Any thoughts?
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Admeisterz said:
Have you tried flashing stock and starting from scratch?
Did you remember to uncheck the option for updating fastboot with system update as well?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Unfortunately I missed the fastboot update bit. Did I **** myself with that?
If you could access CWM do a factory reset, and hopefully that clears up your problems, if not go back to stock via: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
the only reason why i could think that it'd say flashing is successful is it's flashing to the wrong partition (which doesn't make any sense), or the bootloaders locked, which it isn't since from your post it says you had TWRP installed, but try going back to stock fully via fastboot, then installing twrp and such.