Database Users

[Q] Weird things happening with my DZ

My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA

Tone-Fu said:
My DZ has been doing some weird things lately and I'm at a bit of a loss as to what could be causing them.
It's rooted, S-OFF, running MIUI with ClockworkMod 5.0.2.0 installed but the recovery image won't do anything at all any more.
I click on an option and it just goes to the top-hat, circular arrow 'thinking' screen and stays there. It's the same with everything I select; it won't reboot, power off, wipe..nothing.
The problems started with the previous version of ClockworkMod, but are still present with the update.
It worked fine before, I was able to flash ROM's and do all the other usual tinkering, but then it literally just stopped with no instigation.
I've tried wiping the recovery and manually installing a new one via FastBoot but it won't work in FastBoot any more either. I just get the FAILED (remote: not allowed) message for everything I try and do.
I'm baffled.
Any ideas?
TIA
Click to expand...
Click to collapse
The new clockwork 5 has alot of issues. You should try to reflash clockwork mod 3 or 4
Sent from my HTC Vision using XDA Premium App

Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.

Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer

Nipqer said:
Don't use the power button to select stuff in clockwork, that's like a sleep mode.
Use either trackpad or camera button.
-Nipqer
Click to expand...
Click to collapse
This. I think he's using the power button or volume buttons to move and select, which is incorrect.
You have to use the trackpad to scroll and select items.
So why are you trying to flash the new recovery through fastboot? Just pull your battery and boot into MIUI normally, then go to ROM manager and flash CWM 3.0.2.4, it will work. If it doesn't flash properly, go into the settings and select "wipe recovery before flash".

Tone-Fu said:
Thanks for the reply, mate.
The problem is that I can't reflash to any other recovery.
The issues started when I was using the previous version, which was 4.X or something, so I updated to the latest iteration hoping it would fix the problem, but it didn't.
Click to expand...
Click to collapse
I have met the similar problems too.
and I solved it via reflashing the recovery using the ROM manager.
So you can reflash your clockworkmod recovery 5.0.2.0 by ROM Manager, I guess that will work.

Cheers for the replies Nipqer & martonikaj.
The trackpad thing might be the issue but I can't tell because my wife's gone out with the phone! I'm used to using the recovery on my GS2 and DS2, which doesn't have the trackpad etc. so I may well have been using the volume rocker and power key on muscle memory.
Though it is interesting that that method obviously worked in previous iterations of the recovery.
Oh and in answer to your question I was trying to use FastBoot because I perceived the problem to be due to the flash via ROM manager.
@Sunkins - Yeah, I think ROM manager was working just fine. The problem seems to be down to the man in the loop! Cheers for the advice, mate.

I would recommend recovery 3.0.2.4 as it is rock solid, and seems to be the most reliable.

[Q] Can't get into recovery, no matter what I do... (Rooted, running rom...)

Ok, I just started experiencing an issue. I suddenly can't get into recovery. Here is a little back history. My N7 was running CNA 3.6.6 (I know, but...), and I was bored so I decided to try ParanoidAndroid. Well, I have that gotta try something else feeling again, and when I try to get into recovery, it will go to the google screen, then go black for about 10 seconds, then go back to the Google screen and boot up. This happens if I reboot to recovery through the power menu, or getting into recovery from the bootloader. I even tried Quick Boot, in hopes it had some magic I didn't. No luck. The same crap. I even switched from TWRP to clockwork recoveries, and the same crap happens (I tried the same things I did originally).
Also tried through other apps too, like Rom Manager, Rom Toolbox, and TiBu. Everything works, but I am bored with this rom... I have tried turning it off, plugging the N7 into a PC and trying to get into recovery. Again, I can get into the bootloader, but as soon as I select recovery, it goes black, then fully reboots...
Anyone have any ideas? Any help would be greatly appreciated.

Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7

BillGoss said:
Have you tried re-flashing a recovery image, eg TWRP 2.3, from fastboot?
Sent from my Nexus 7
Click to expand...
Click to collapse
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.

MetalWych said:
Thanks for the reply. I will give this a try (gotta wait until after 10pm...or 17 minutes!). Again, thanks, hope this works.
Click to expand...
Click to collapse
Scheiße, I reflashed TWRP in fastboot, and I am getting the same result. I think my N7 forgot it has a recovery!? I will try flashing clockwork through fastboot and see if this works. Thanks for your help...
Edit: Clockwork does not help. There is no recovery for me. I am now at a loss. Hopefully someone will have some suggestions...

Finally got my recovery back...damn latest bootloader!
Yeah, this has sucked. I have spent several hours figuring out what the hell went wrong. It turns out its the latest bootloader. Others are having this issue. So, I had to go back to stock (which will erase EVERYTHING) and then had to re-root. Now that my bootloader is back to JRO03D, I am back up and running.
So, the first time I did this route, I decided to take the update and re-root my N7, and ran into the same issue. I could not get into recovery. So, I had to do it all over, this time not taking the update and not updating the bootloaders, and I am now back and already have a ROM running and everything installed.
If you want to go this route, here are a couple of links that will help...
http://rootzwiki.com/topic/28544-guide-nexus-7-bootloadersrecoveriesrootback-to-stock/#entry764328 and go to the Back To Stock section. The next part is for rooting (if you wish to do this yourself)...
http://www.talkandroid.com/guides/misc/how-to-unlock-and-root-the-nexus-7/
I will post this in case anyone has a need for this info...

Unable to get into Recovery after 4.1.2 upgrade... - xda-developers
Any help?

[Q] Weird Recovery Problems?

So I was originally on MDL. AT&T S4 of course. Rooted it, installed custom ROMs, everything good. But recently it seems to have issues. Seems like Original Android ROMs just refuse to start up, like Beanstalk or ShoStock. Shows the Custom Lock boot screen thing, then just restarts to recovery. One of the few that worked fine and just booted normally was Alpha ROM from Android, now on the Tmobile forum I believe and Miui ROM.
So I gave up and tried restocking. Installed the MDL stock ROM again, motochopper, used ROM Manager to install Clockwork Recovery (Touch.), and then another problem. The recovery showed the android mascot laying down and that small red box. It seems to have defaulted to some Android Recovery thing with limited options. Rebooted and tried Clockwork Recovery normal edition this time. Same thing.
Honestly not sure what's wrong. Did I miss something and should have updated something or...?

gerard0986 said:
So I was originally on MDL. AT&T S4 of course. Rooted it, installed custom ROMs, everything good. But recently it seems to have issues. Seems like Original Android ROMs just refuse to start up like Beanstalk. Shows the Custom Lock boot screen thing, then just restarts to recovery. One of the few that worked fine and just booted normally was Alpha ROM from Android, now on the Tmobile forum I believe and Miui ROM.
So I gave up and tried restocking. Installed the MDL stock ROM again, motochopper, used ROM Manager to install Clockwork Recovery (Touch.), and then another problem. The recovery showed the android mascot laying down and that small red box. It seems to have defaulted to some Android Recovery thing with limited options. Rebooted and tried Clockwork Recovery normal edition this time. Same thing.
Honestly not sure what's wrong. Did I miss something and should have updated something or...?
Click to expand...
Click to collapse
Did you use LOKI?

scott14719 said:
Did you use LOKI?
Click to expand...
Click to collapse
Yeah. Had a recovery with auto loki. But I believe a few of the ROMs I tried were lokied already too. Still didn't work.

I just tried using the stock recovery. Restocked, and went straight to recovery. No motochopper or anything.
Still shows the error droid and under the limited option'd "Android system recovery <3e>", it says, in yellow,
"# Manual Mode #"
"-- Applying Multi-CSC..."
"Applied the CSC-code : ATT"
"Successfully applied multi-CSC."
I'm guessing I broke something somehow...but I REALLY hope this is fixable. This recovery lets me reboot system, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, and apply update from cache.

Restocked again and used the new CASUAL root. TWRP installed fine from it and works fine, but I tried Beanstalk again and still just reboots into recovery. Even flashed loki twice. What am I missing? Stuck at rooted stock for now.

Bumping this up. Still seem unable to install other ROMs.

gerard0986 said:
Bumping this up. Still seem unable to install other ROMs.
Click to expand...
Click to collapse
No ROMs have worked at all? Have you tried installing a different kernel?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app

DeadlySin9 said:
No ROMs have worked at all? Have you tried installing a different kernel?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Seems most I try from the "Original Android" section don't work at all. Starts up, waits at the Custom Lock boot image thing or the stock Samsung logo, and eventually reboots into recovery. Select ones from the "Android" section will work. Alpha I think so far was the only one that I tried and worked fine.
I'll try the kernal thing though, but would that affect the recovery like I mentioned before? Or am I dealing with multiple problems perhaps?

gerard0986 said:
Seems most I try from the "Original Android" section don't work at all. Starts up, waits at the Custom Lock boot image thing or the stock Samsung logo, and eventually reboots into recovery. Select ones from the "Android" section will work. Alpha I think so far was the only one that I tried and worked fine.
I'll try the kernal thing though, but would that affect the recovery like I mentioned before? Or am I dealing with multiple problems perhaps?
Click to expand...
Click to collapse
Kernel shouldn't affect the recovery, just make sure the kernel is patched for loki.

When you are getting back into recovery what recovery is showing? The TWRP recovery or 3e recovery? Kind of sounds like it is defaulting back to the 3e recovery.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337

RockRatt said:
When you are getting back into recovery what recovery is showing? The TWRP recovery or 3e recovery? Kind of sounds like it is defaulting back to the 3e recovery.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
With the old Motochopper it defaulted to 3e recovery (But didn't before all of these problems.). With the new Java based one it loads TWRP normally again.

I switched to Task's AOKP just fine it seems. Maybe it was just the kernel. This problem is solved for now I guess.

Problem is back. I tried to restock and it seems to have worked, but now it just gets stuck at the AT&T globe logo right after the melody. It just freezes and starts to get hot.

[Q] Malladus 1.2.5 stuck at boot.

I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.

Bump I'm having the same problem, I'm on Verizon.

NBushyy said:
Bump I'm having the same problem, I'm on Verizon.
Click to expand...
Click to collapse
Yeah same here. Verizon. Forgot to mention it.

Still a problem. Bumping.

I am in the boat with you. I thought it was just me.

Same Black Screen issue
Did anyone have any luck resolving this? Ive tried with both twrp and cwm and same issue...?

Same problem on my Verizon model. Using twrp 2.6.3.3. Other roms work fine.

How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?

heleos said:
How long have you left it at the black screen? Sometimes a fresh load can take up to 10 minutes.
Also, the rom will work without gapps and lgapps, so try just loading the rom. I know you downloaded twice, but did you check the md5 sum either time?
Click to expand...
Click to collapse
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)

try this
trackstar1414 said:
I left it there for a good 15 minutes. I also had it plugged into my laptop. It kept detecting the phone as plugged in. Seems like it is stuck in a bootloop or something. I also tried installing only the ROM without the gapps and lgapps and had the same result. I also checked the MD5 sum and it matched. (I know I'm kinda hijacking this original post, but I think we are all having the exact same issue)
Click to expand...
Click to collapse
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know

geosnipe said:
Can you restore your nandroid and flash say, CleanROM 1.0 or DigitalDream 2.1? OR try this:
1. Hold the power button until the device is OFF.
2. Download LG drivers to the PC (LG VZW_United_WHQL_v2.11.1) and LG mobile support tool (B2CAppSetup).
3. Install these packages.
4. Plug in you USB cable into the phone but not the computer.
5. Hold volume up and insert the USB cable to the PC- the phone should boot to 'download mode'.
6. Open the support tool and click Options>Upgrade Recovery, follow the prompts.
7. At the first prompt indentify your phone using IMEI/ESN, then click OK
8. Let it do its thing, the phone will reboot and most likely have a bunch of error messages and some FC's. Just hit okay to all messages, the phone will settle after 2 minutes or so.
9. Download freegee from market and reflash recovery of your choice.
10. Make sure you have a ROM saved to the SD to flash
11. Use freegee to reboot to recovery
12. Once in recovery you can reflash the ROM as normal.
13. Reboot and Profit!
*$* Or you could go back to Stock and start fresh!
*$* BEFORE ANY FLASH ALWAYS STOP and MAKE A NANDROID BACKUP!
Good Luck and if you get stuck let me know
Click to expand...
Click to collapse
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.

trackstar1414 said:
I am able to restore my nandroid backup so I'm not completely stuck without a phone. I will try flashing one of the other ROMs and see how it goes now. Thanks for the help so far.
Click to expand...
Click to collapse
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.

trackstar1414, say thanks by using the "Thanks' button like this.. keep me informed, CHEERS!

trackstar1414 said:
I was able to install the digital dream rom without any issue. At this point I think its the sequence I did everything. I did the latest ota before installing any Recovery. I used the loki method to install the recovery. In looking at all the roms, it appears that malladus may not be "loki patched" for people already on 12b? Other roms I have tried mention that so thats why I'm speculating this. I am by no means a developer so I might be out in left field on this one. I guess I'll stick with stock or another ROM for now until his next update.
It also looks like people are discussing this on the main ROM forum as well so hopefully it will work in the future.
Thanks again for the help and suggestions.
Click to expand...
Click to collapse
Wanted to share this if you haven't read it..
http://forum.xda-developers.com/showthread.php?t=2449670

I had issues originally and had to flash back to 1.2.3.
What I ended up doing was switching to CWM 6.0.4.4 ( I was using TWRP 2.6.3.3).
His boot skipped the set up wizard as well, which was odd.
His was also the only ROM I ever got stuck on the fastboot screen while using twrp.
Try ( at your own risk obviously) flashing back to an older malladus (wipe all and boot till you get through the set up wizard),
Then back to recovery, do a wipe, without wiping the system partition, Data Cache and Davlik, and flash back to 1.2.5.
I didn't try it on 1.2.5. But that's how I got into 1.2.4.

Srvisg0d said:
I've heard ranting and raving about Malladus and I decided to flash it yesterday. It won't take the flash no matter what I do.
I've tried: Flashing 1.2.4, downloading both again to make sure it wasn't a download issue, using different gapps package, using a different lg apps package, using CWM, using TWRP, side-loading... ETC
Bottom line: My phone will not take the ROM. It flashes the LG logo and gets stuck at a black screen where the back-light is on but nothing is displayed on the screen.
I am an experienced flasher and I have no idea what is going on. I am backed up and can get into TWRP to restore so I am all good as far as not being bricked goes but I really want to try out this damn rom.
Any help would be much appreciated. Thanks.
Click to expand...
Click to collapse
Are you on 12B OTA? If so, that would be your issue. I took the 12B OTA and tried flashing Malladus and got the same issue you have. You can revert your phone to 11A and that should resolve your issue. http://forum.xda-developers.com/showthread.php?t=2448960 it will erase everything on your phone and go back to unroot.

Constantly rebooting...

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