So I have been running the AOKP nightlies in Goo and Ktoons kernel. This has been a very trouble free combo. However, out of nowhere I go to reboot in recovery and it takes a dump. Mind you its been running fine all weekend. It will get right to the Teamwin splash and start boot looping. All I did was reboot. Recovery is now broken, so I odin CWM on and that gets me back to a recovery, but when I try to flash TWRP again same issue. So I put CWM back on, factory reset, reflash, wipe everything, sticks on boot splash on every build. Finally, I gave up flashed back to stock, and re-rooted....lost all my stuff on the internal card but I was able to re-install TWRP and restore my backup.
This is so very random and frustrating...it just randomly for no reason stopped booting to recovery. Is this a common thread with TWRP? Maybe I should go back to CWM...anyone had this same experience?
I had that problem too. It lead to me getting bricked because I can't get Odin to work. Could you view over the post and confirm similar problems? I think some of my issue is with TWRP. I made dumb with my ROM, but the recovery shouldn't have messed up... Anyway here's the post. Let me know if you think the problems (with TWRP) are similar. If they are, there might be something wrong with TWRP
Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse
Related
I am not new to the concept of rooting and loading a custom rom. This is the 3rd android phone that I have bothered with. However it is the first one I have had to use Odin to root or push files to.
I have used CarpeNoctem's writeup on how to root and utkanos' CWMR port writeup. Ofter verifying I had root, I decided I would try out Carpe's OsiMood. No problem right? Here is where I am wondering what if anything went wrong on the previous steps.
I made a back up ofter finally getting it to recovery mode, and when I tried flashing the new rom, it would not complete the process.
As it sits, when I choose recovery from CWM it reboots to the android with triangle screen(see attached video). What concerns me is the lack of fluidity into the recovery, the fact that it loads in only after the battery is removed and the phone is turned back on and lastly that I cannot flash a new rom.
It appears as though I need more posts to add my link for youtube.
Please add standard youtube weblink before this to watch the video.
/watch?v=qpQyQB1aozs
What would you recommend my first action be?
Thanks,
Steve
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Thanks for your insight. I tried volume down and power before but when I saw the samsung logo pop up I figured it wouldn't work.
I will try flashing again and report back. Thanks again.
-Steve
Tried flashing again, worked great. If only the glide had more support. Lol.
Currently running OsiMood.
Sent from my SAMSUNG-SGH-I927R using Tapatalk
gabby131 said:
This also quite unfortunate for ROM manager, "somewhat", not working fully for the Glide (yet). I can't really go into 3e/CWM recovery with the app, but manually (volume down + power/lock button) has no problems. This also happens on my Captivate (SGH-I896/7), I need to restart the device for a second time to boot into recovery. As per your flashing issues, you might need to mount /system manually and then flash the ROM, when it fails, try and try again, always happens to me from stock rogers ROM. Also, if you have Titanium Backup, it now supports reboot device features (recovery and hard reboot)
Click to expand...
Click to collapse
My glide does not boot. I can get into Download Mode. I can NOT get into de recovery mode. I think my NAND is corrupted.
How can I mount the /system partition? Because I flashed too many roms with ODIN, but nothing, still not booting, I get stuck in the samsung logo.
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Kodiack99 said:
Use Odin to reflash recovery,you backups should still be there unless like you say maybe they got corrupted as well,but its worth a shot.
Here is a link to the latest,with instructions:
http://forum.xda-developers.com/showthread.php?p=34479219#post34479219
Click to expand...
Click to collapse
I've already flashed the stock recovery, the CWM, a lot of kernels, even I tried to flash the kernel and bootloader of the Galaxy S II, but nothing.
I'm starting to think that maybe is a hardware problem. Hope not, but I'm not moving foward.
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
I had a boot loop once ,had me stumped and it turned out to be my sd card was poached and caused the loop.
Kodiack99 said:
If you havent already,pull out the sim and sd card.
Reboot your pc and download a fresh up to date Odin.
So when you flash it says it successful and then just doesnt boot?
Click to expand...
Click to collapse
Exactly... It goes all over the process bar, says succesfull, the phone turns off, and nothing. The phone not even restart itself, I have to remove the battery, put it back again, and then it turns on, but just to show me the samsung logo.
I've used the ODIN version 1.85 and the new one 3.04. But nothing. This is so frustating.
---------- Post added at 04:23 AM ---------- Previous post was at 04:04 AM ----------
I've opened a thread with all the symptoms of my bricked phone:
http://forum.xda-developers.com/showthread.php?t=2035742
Please, tell me there is a solution...
There are one alternative to boot
1. Shut down and then restart phone in recovery mode. For the Samsung Captivate Glide, this required pressing the power, volume down and home keys all at the same time.
2. The initial screen which appears gives you a choice of loading a replacement OS (volume up) or entering recovery mode (volume down). Note you have to hold the volume down key for several seconds before the recovery mode menu appears.
NOTE: This device is not mine, it belongs to my girlfriend and I am the one troubleshooting for her.
here goes:
Yesterday, while a friend of my girlfriend's was playing with her Galaxy Nexus (my GF's), it suddenly rebooted itself without warning.
From what I understand, Nexus bootloops that are caused by faulty flashing usually loops at the "Google" logo (correct me if I'm wrong). Her's is a different story, her Galaxy Nexus is pure stock, locked bootloader, un-rooted and definitely nothing custom on in; literally pure stock. Instead of looping at the "Google" logo, her GNexus loops at the "X" logo, my assumption is that there is something, maybe a rogue app, that is causing her device to bootloop upon reaching startup phase.
I know this isn't a software/ROM level issue since we were able to get to her lockscreen a few times and then the phone reboots after a few seconds. I've tried wiping cache but didn't work, and she won't let me try wipe data/factory reset because she has a lot of important files on her phone. So odin flashing and wipe data/factory reset is out of the question.
so here are some details that might be of interest:
1.) Her phone is not rooted and is pure stock android 4.1.2
2.) does not have custom recovery
3.) does not have usb debugging enabled (not sure, but I assume it's not enabled)
4.) can still boot to fastboot/recovery/download mode
5.) reboots at the X logo
So the basic troubleshooting methods are out, now I'm thinking of using adb pull to extract files from her phone via adb, but problem is, usb debugging is off! Is there any way of recovering her files at least without booting to the ROM itself so I can flash another version of android on it (via odin)?
I've also read about "safe mode" that boots the device without starting up 3rd party apps, only the core essentials. I'd like to go down that route if possible, but we've tried most of the guides on how to boot into safe mode but to no avail. There was one time though that the device booted up and she managed to: open power menu > hold power off > reboot to safe mode, but nothing happened, it just rebooted only to get stuck at the X again.
I may be overthinking this, so I've turned to XDA for help. I know you guys don't like people asking n00bish queries but I've exhausted everything I can think of and I'd like to try everything before I go down the route where I can possibly do even more damage.
I really need help with this, anyone have any ideas? We'd really appreciate it!
Unlock, flash custom recovery, wipe system, data, cache, dalvik cache and flash 4.3 factory image. Problem solved.
Other than being rooted my N7105 was stock before I decided to install CM via the Windows Installer. It failed once so I restarted the device and computer on the programs suggestion. Second time it seemed to be installing fine getting past the installing recovery step before I left the room. On my return it had failed again and suggested I try a different USB port or computer and the install would pick up right where it left off.
Except it hasn't.
The Installer isn't even detecting my device anymore. I'm stuck with a little blue fellow on my screen. Rebooting just brings me back to the same screen and when I remove the battery the phone reboots as soon as I replace it. I can boot into download mode but trying to boot into recovery just brings me back to the blue dude.
I'm not really sure what to do. I've tried using a Toolkit but get stuck at the "Waiting for USB debugging to be turned on" part. I've looked at Heimdall but aren't really sure where to start or if it could even help.
Any suggestions?
kimbies88 said:
Other than being rooted my N7105 was stock before I decided to install CM via the Windows Installer. It failed once so I restarted the device and computer on the programs suggestion. Second time it seemed to be installing fine getting past the installing recovery step before I left the room. On my return it had failed again and suggested I try a different USB port or computer and the install would pick up right where it left off.
Except it hasn't.
The Installer isn't even detecting my device anymore. I'm stuck with a little blue fellow on my screen. Rebooting just brings me back to the same screen and when I remove the battery the phone reboots as soon as I replace it. I can boot into download mode but trying to boot into recovery just brings me back to the blue dude.
I'm not really sure what to do. I've tried using a Toolkit but get stuck at the "Waiting for USB debugging to be turned on" part. I've looked at Heimdall but aren't really sure where to start or if it could even help.
Any suggestions?
Click to expand...
Click to collapse
try to flash stock ROM using Odin, you might have to try different versions.
Just enter download mode, connect usb and flash
I'm not entirely sure if this is where I should post this, but I am having a problem with my Fire Phone and I really hope you guys can help.
So, story time. I was thinking that I wanted to install a new ROM on my phone just to try some new things. I decided on the SlimKat android 4.4.x ROM and I installed it with GAPPS using SafeStrap 4.01. However, the new ROM was not working correctly so I thought I installed it wrong. So, I read up a little bit more on this and it said that I had to do a factory restore beforehand so I did it with high hopes that it would work. However, it sill did not work. What happens is that I power it on, it asks whether I want to go into SafeStrap or not, it continues if I say no, and they it starts with SlimKat. After about 20 seconds, it stops the starting animation and starts its boot loop.
Since I factory restore it, I had no back ups or and ROMs that I could install on my device. I try to plug it into my computer but it is unrecognizable even if it is the recovery. I also tried going into download mode, doing it multiple ways, but with not luck. It still goes into the boot loop. I factory reset it multiple times but still with no luck. Within SafeStrap, I tried to wipe it, but it is unable to wipe the Dalvik Cache or Data. If there is any way that I can move the stock ROM onto my phone, it would solve all my problems. If any of you have any ideas, please let me know.
I having same problem. Unable to go to recovery mode in normal way, but I could managed to go to recovery by attaching it to computer with usb cable and keeping pressing power + Vol up key for few seconds.
Then I tried Factory restore, Adb Sideload original file downloaded from amazon, but the problem still not solved.
My phone is keep flashing amazon logo in loop.
If any one have idea please help.
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
rfgamaral said:
My phone was a bit erratic and I decided to reboot it. Before that I installed a new Magisk Manager version, updated a module and uninstalled another (I should've had done one step a time, I never learn). After all this I rebooted and my phone no longer booted. the HTC logo shows up and then the screen becomes blank and nothing shows up.
I can reboot it pressing the Power + Volume Down buttons for 10-15 seconds, I can boot to bootloader, dowload mode and and recovery. The phone charges just fine in recovery or powered down. If I let it try to boot for a while and attempt "adb devices", nothing shows up, so I can't invoke "adb logcat" and see if it's in a boot loop or something. It's hard to debug and understand what's wrong.
Flashed Magisk Uninstaller, still doesn't boot. Another mistake is that I don't have a backup, yes, I'm an idiot. I don't understand why I keep living on the edge like this...
I use MaximusHD ROM and I'm now thinking of reinstalling this on top of my current installation to see if it fixes anything, as a last resort because I can't think of anything else. Thoughts?
Click to expand...
Click to collapse
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Tarima said:
I can't speak to your specific issue with Magisk but you should easily be able to return to stock by flashing Maximus, or by running an RUU from your sdcard. The ruu will wipe your phone completely
Click to expand...
Click to collapse
Tried to reflash Maximus, didn't work, still didn't boot. Backed up everything I could and wiped everything, I'm now on Lineage OS 16.0. Thanks for your reply.