Related
I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!
Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?
To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed
Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!
Hi,
After attempting to update my GT540 from 2.1 to 2.3, something has happened to it.
I got to tha part where I clicked launch software update, made sure type and phone mode was correct, it took around 6 mins to finish. Then I kept getting sorry, android dytem is shutting down errors again and again. Turned it off and it does not turn back on again.
Tried pressing home and power, power and camera, not working!
Please help me!
hello, which rom are u using? the 2.1 with fastboot? if yes look at this thread maybe there is something you can use
http://forum.xda-developers.com/showthread.php?t=1224747
read around the back few pages
bs828 said:
hello, which rom are u using? the 2.1 with fastboot? if yes look at this thread maybe there is something you can use
http://forum.xda-developers.com/showthread.php?t=1224747
read around the back few pages
Click to expand...
Click to collapse
I managed to turn it on after taking battery out but errors kept coming. And sometimes it just would not turn on again.
Used fishears instructions as per that thread and managed to do the first part of the french flasing. The kdz.out just doesnt seem to work, can get phone in download mode but the kdz is just 'not responding' and have to close it.
Also noticed, all my apps from sd card arent showing. Link2sd says needs superuser access, but dont get a prompt from superuser allowing it
and all the preinstalled apps that i deleted using titanium are back again and titanium doesnt even show on link2sd, it does show on superuser though but cannot access it!
cookies! said:
I managed to turn it on after taking battery out but errors kept coming. And sometimes it just would not turn on again.
Used fishears instructions as per that thread and managed to do the first part of the french flasing. The kdz.out just doesnt seem to work, can get phone in download mode but the kdz is just 'not responding' and have to close it.
Also noticed, all my apps from sd card arent showing. Link2sd says needs superuser access, but dont get a prompt from superuser allowing it
and all the preinstalled apps that i deleted using titanium are back again and titanium doesnt even show on link2sd, it does show on superuser though but cannot access it!
Click to expand...
Click to collapse
Well, I tried doing everything again, this time my phone looks very different like its a factory reset. so all apps are gone, contancts are on sim but thats ok and i had to create a market account again which is good as market wasn't working properly for me anyway, could never download apps even though i had room
Still 2.1 though, now when i try it, it just says phone not found when i click launch software update!
I think i give up!
try to hold power+vol down then put usb in phone and conect other end of the cable into back ports on PC cause front ones sucks,go to device manager on PC and disable lge modem that shoud do the job
Sent from my GT540 using XDA
Hello All,
I need help regarding the boot loop...I am new to flashing ROMS..Few times i got into the Boot loop..
Sometimes I got into Boot loop for Modding , theming or using some Root application as well...
I just want to know is it possible to find out what is the reason or root cause for boot loop...how can i debug this boot loop problem....
Thanks in Advance...
FemBlack said:
Hello All,
I need help regarding the boot loop...I am new to flashing ROMS..Few times i got into the Boot loop..
Sometimes I got into Boot loop for Modding , theming or using some Root application as well...
I just want to know is it possible to find out what is the reason or root cause for boot loop...how can i debug this boot loop problem....
Thanks in Advance...
Click to expand...
Click to collapse
1. if flashing two different roms, you have to wipe data. if you dont wipe, then youll get a bootloop.
2. bad download of a rom/kernel.
3. the theme/mod isnt compatible or a bad download.
4. rarely, stuff corrupts.
5. root applications with stuff thats not compatible with your rom/kernel.
simms22 said:
1. if flashing two different roms, you have to wipe data. if you dont wipe, then youll get a bootloop.
2. bad download of a rom/kernel.
3. the theme/mod isnt compatible or a bad download.
4. rarely, stuff corrupts.
5. root applications with stuff thats not compatible with your rom/kernel.
Click to expand...
Click to collapse
Thank you for the reply...
I know because of compatibility i am getting the boot loop when i am using the root application....
My question is how to debug or find out where it went wrong... what made that application is not compatible with my ROM/Kernel....
FemBlack said:
Thank you for the reply...
I know because of compatibility i am getting the boot loop when i am using the root application....
My question is how to debug or find out where it went wrong... what made that application is not compatible with my ROM/Kernel....
Click to expand...
Click to collapse
watching a log cat via adb while the device is forced into one of these "bootloops". maybe even a dmseg. btw, are you sure that you have root? can you describe a situation, what you were doing with what root app, in detail how a "bootloop" happens? can you describe the bootloop and how you recover from one?
simms22 said:
watching a log cat via adb while the device is forced into one of these "bootloops". maybe even a dmseg. btw, are you sure that you have root? can you describe a situation, what you were doing with what root app, in detail how a "bootloop" happens? can you describe the bootloop and how you recover from one?
Click to expand...
Click to collapse
When i use Rom toolbox pro font installer to install new fonts or change the status bar using the build in icons...
two times i got into the boot loop problem.....
FemBlack said:
When i use Rom toolbox pro font installer to install new fonts or change the status bar using the icons...
two times i got into the boot loop problem.....
Click to expand...
Click to collapse
those options probably arent compatible due to android version, phone model, or rom(if works on another rom). there could be filesystem differences that make things incompatible. not all hacks/mods work on all devices. this all would cause bootloops, the way you describe it. have someone else with a nexus 4 confirm if they work or cause bootloops.
I already spoke with the developer regrading these boot loop problems... he has provided some solutions for it...
I have try those workarounds and lets see whether it fixes the problem or not....
Hello, this is my first post here and I have searched for a similar post or issue but have been unsuccessful finding anything.
Please forgive me if I have posted in the wrong area, missed a solution somewhere and/or have not explained anything correctly/clearly.
My Nexus 7 (2012) (I installed Cyanogen on it (and updated it once) through their installer and it has run perfectly for months) started rebooting randomly one morning. I turn it on and it seems to be normal, then it will suddenly reboot. The time between reboots varies ranging from 30 seconds to a few minutes. I can not install or update any apps and any settings changed are reset back to what they were previously upon reboot. I have tried a factory reset and while it appears to wipe everything (all caches and data) when I reboot it is the same as before the reset (I also receive this message (after all other processes are complete) during the data wipe "E: unknown volume "/sdcard/.android_secure" "). I am able to turn on developer options but then the random reboot occurs and it is turned off. I have plugged it to my computer and see it listed, but can not access anything on it.
My intention is to wipe it using my computer (fastboot?) but I am at a standstill due to the rebooting and being unable to turn on developer options.
Any ideas or suggestions would be greatly appreciated.
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
kcipopnevets said:
Have you tried flashing another ROM in recovery? Perhaps try to see if you can access the filesystem while in recovery or if the bootloader brings anything up on your computer.
Click to expand...
Click to collapse
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
pdn190 said:
Thanks for the reply. Sorry for my delay in replying. I've been rather frustrated with this.
I flashed the official image (downloaded from the google site) using fastboot and it seemed to work as all messages said complete but when I rebooted, it was back to it's current state. I am at a loss. I also tried adb sideloading but that just hangs when it gets to installing. It does not reboot randomly when it is in recovery.
Click to expand...
Click to collapse
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
kcipopnevets said:
No worries!
So CyanogenMod is still installed? Oh my. Has anything at all changed? If you still have custom recovery installed, why not try a near stock ROM?
Click to expand...
Click to collapse
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
pdn190 said:
Yes. No matter what I do, when I reboot it's still Cyanogen. Being a semi-novice at this, I didn't backup the stock ROM I had before installing Cyanogen. It feels like a virus, but I pretty much installed the exact same apps on both my phone and tablet and the phone has been fine.
I used this image(nakasi kot49h). Should I try a earlier version?
Thank you.
Click to expand...
Click to collapse
You can always try. Also make sure you check md5 before flashing, that may explain why stock didn't flash correctly.
And I still can't get anything to work. Most recently I tried using wugfresh and EVERYTHING works except when it writes bootloader.img at the start. I feel like I am close but then it reboots back to cyanogen. lol
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Added video of issue:
https://www.youtube.com/watch?v=M_mncUueCJ8
Edit: Solved the issue through the most scientific methods; insanity and brute force! The phone would boot sometimes with the lock screen in the rotation, and those boots allowed me a brief window of touch interaction which I used to enable emergency mode, which fixed my immediate problem of being locked out and allowed me into an adb root shell. Hurrah.
Thanks all,
Overkill
OverkillSD said:
I'm on NCG odexed stock, rooted with nova launcher + xposed framework/wanam
Today, I rebooted my phone and was presented with an odd scenario: The phone was looping between my homescreen (black background) and the Galaxy S5 blue geometrical wallpaper (I think I left the TW launcher with the default grassy picture). That's all the phone does - cycle between the two - and I cannot get a screen to stay up long enough to do anything. Of course, I don't have ADB authorized for any of my machines (haven't had the chance to use it yet) and I can't do much of anything. I tried safe mode, emergency call, camera, clear cache via stock recovery, and adb sideload to try and get SOMETHING to run. Unfortunately it seems I'm locked out of my device...does anybody have a suggestion that would allow me to get the data off the internal storage before wiping? >.<
Click to expand...
Click to collapse
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Chopstix9 said:
I would suggest you download the stock tar and odin, pull the battery and put it in download mode and odin back to stock. So long as you can get to download mode you should be fine.
Everything you need can be found here ==> http://forum.xda-developers.com/showthread.php?t=2784880
Click to expand...
Click to collapse
Already in progress But the stock tar also flashes over any user data, correct?
OverkillSD said:
Already in progress But the stock tar also flashes over any user data, correct?
Click to expand...
Click to collapse
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Chopstix9 said:
Absolutely you will be returning to out of the box stock. But it's a good failsafe. Then you can start to play with it all over again
Click to expand...
Click to collapse
Right The problem is, there are files I need to get from the device before I do that!
OverkillSD said:
does anybody have a suggestion that would allow me to get the data off the internal storage before wiping?
Click to expand...
Click to collapse
OverkillSD said:
Right The problem is, there are files I need to get from the device before I do that!
Click to expand...
Click to collapse
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Chopstix9 said:
If the files are on the external sd card you are golden. That doesn't get formatted. If not ... It will take someonen with more expertise than me on the issue.
Click to expand...
Click to collapse
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
OverkillSD said:
Well, I let the phone run for the last 45 minutes and eventually the phone rebooted itself and the system UI immediately crashed. I'm going to wait for the next crash and see if I have any luck with not pressing ok when this happens, and using that opportunity to allow ADB, which would solve my problem In the meantime, assuming that my hopes and dreams will be crushed, if anybody with ninja hacker skills has any suggestions, I'm all ears (or is it eyes?)
Click to expand...
Click to collapse
I wasn't able to do this, presumably because com.android.systemui is responsible for this dialog and when it restarts, the problem restarts with it.
what's strange is that i can see my device on windows but the internal storage doesn't mount when the device shows up >.<
would i be able to flash just the systemui.apk and framwork.res files to stock using odin?
EDIT: Was able to get the device into emergency mode after much spamming of buttons and trial/error; this stops the problem I'm having, and I was able to get into ADB. The problem is most likely with Xposed, I'll be able to troubleshoot from here =) Basically, I had a brief window of laggy but responsive touchscreen interaction once out of every 10 boots which I used to get emergency mode enabled (lots of checkboxes) and this worked. It was either xposed or nova or a combination of the two, but it appears that I'm able to hack at it from here xD