Database Info

[Q] Boot Loop after Cyanogen Mod install. Help me please.

Hey folks,
I could desperately use some help here...
I rooted my Droid Incredible using UnRevoked, which was painless and easy. After that, I downloaded Rom Manager, then backed up my current Rom.
Then I downloaded Titanium, and backed up all apps and system data.
Using Rom Manager, I downloaded Cyanogen mod 7.0.2, checked google apps, DID NOT check wipe data or cache, and then clicked OK to let it work it's magic.
The system turned on and off a bit, and then the CyanogenMod boot screen came on, ran the arrow around the droidbot a few times, then the droidbot dissapeared, came back across the screen, and the arrow resumed circling. This happened about 20 times, before I gave up and powered off by removing the battery.
Then I loaded Hboot, and attempted to access items in Clockworkmod, but even though I could click on an item, it would show the top hat with no change in status for many minutes. I eventually tried almost all options.
My Hboot screen shows:
HBOOT - 0.92.0000
Radio- 2.15.00.07.28
I am unable to click on Fastboot, Recovery leads me to busted Clockwork menu, Clear Storage causes restart into looped Cyanogen Mod screen, haven't tried Simlock, and Factory Reset also goes to broken Clockwork Menu.
I downloaded the RUU file from Doug, changed the title as directed, and put it on the SD Card. It gave me the option to Update, which when restarted afterwards continued to loop in Cyanogen Mod screen. Or, if I went to Clockwork Mod screen, the font was now Green instead of Orange. Also, when I click an item in the Clockwork Mod menu, it simply goes to a black screen until I hit the power button to bring me back to the menu,
I'd love to just get the phone to a factory state, so I can possibly use it for it's purpose of calling and sexting (just kidding.)
Please help, any advice would be greatly appreciated.

Oftentimes, ClockworkMod Recovery has an error at the bottom stating:
E:Invalid command argument
I have to go to bed for a bit, but will be back on around 10:30am EST. Thanks for any and all help!

In ClockworkMod, I can now access and start an operation by selecting it with the volume buttons, and then hitting the joystick button. This wasn't working previously. So, I've tried some of the obvious options such as Factory Reset but it's not doing anything. I've tried multiple solutions, which means I've probably messed it up on many levels. Is there any way I can just start from scratch or get a system restore done?

After utilizing that update from Doug, and then going into Clockwork Mod, clearing all caches and system data, and then trying to restore to a previous flash for the 7th time... I think it might be working!
Thanks to anyone who looked at this.

HTC one V bricked?

Last night, I messed up with my android. I am not able to figure out what went wrong
So here is exactly what I had been doing:
1. My phone is already unlocked.
2. I had root my phone by installing "r1-primo-superboot" ( I had used the gsm version)
3. Next, I had flashed a recovery image using fastboot.
4. Installed "Blue Sense". Everything was going well. MADE A NANDROID BACKUP.
5. After an hour, tried to install CM10. Didn't work. Get's stuck in the logo screen of CM10.
6. So flashed "hellboy.img"
7. Now, CM10 gets installed. But gets error notifications like "your phone has stopped". There is no option for text or call or settings.
8. Now I try to go back to "Blue sense" through RECOVERY but, it doesn't work. I'm stuck.
IS THE PROBLEM DUE TO FLASHING OF TWO DIFFERENT .IMG FILES? Please help. I am a noob.

abhilekh619 said:
Last night, I messed up with my android. I am not able to figure out what went wrong
So here is exactly what I had been doing:
1. My phone is already unlocked.
2. I had root my phone by installing "r1-primo-superboot" ( I had used the gsm version)
3. Next, I had flashed a recovery image using fastboot.
4. Installed "Blue Sense". Everything was going well. MADE A NANDROID BACKUP.
5. After an hour, tried to install CM10. Didn't work. Get's stuck in the logo screen of CM10.
6. So flashed "hellboy.img"
7. Now, CM10 gets installed. But gets error notifications like "your phone has stopped". There is no option for text or call or settings.
8. Now I try to go back to "Blue sense" through RECOVERY but, it doesn't work. I'm stuck.
IS THE PROBLEM DUE TO FLASHING OF TWO DIFFERENT .IMG FILES? Please help. I am a noob.
Click to expand...
Click to collapse
Here is solution , don't forgot to hit thanks
:: youtube . com/watch?v=nHzmGny6mLA

abhilekh619 said:
Last night, I messed up with my android. I am not able to figure out what went wrong
So here is exactly what I had been doing:
1. My phone is already unlocked.
2. I had root my phone by installing "r1-primo-superboot" ( I had used the gsm version)
3. Next, I had flashed a recovery image using fastboot.
4. Installed "Blue Sense". Everything was going well. MADE A NANDROID BACKUP.
5. After an hour, tried to install CM10. Didn't work. Get's stuck in the logo screen of CM10.
6. So flashed "hellboy.img"
7. Now, CM10 gets installed. But gets error notifications like "your phone has stopped". There is no option for text or call or settings.
8. Now I try to go back to "Blue sense" through RECOVERY but, it doesn't work. I'm stuck.
IS THE PROBLEM DUE TO FLASHING OF TWO DIFFERENT .IMG FILES? Please help. I am a noob.
Click to expand...
Click to collapse
i am having same exact problem in almost same scenario, what did you do to restore your phone back to normal ?

Stuck in a loop, need help

Hi all
I’m a complete noob at this and it seems like I have got myself into a bit of a pickle. Sorry for the massive description but I thought it would make it easier to get a good answer.
My Phone:
Samsung Galaxy S4 GT 19505 LTE
PDA I9505XXUEMK8
CSC I9505BTUEMK5
MODEM I9505XXUEMK8
I successfully rooted my phone using Odin. In Odin I added the "CF-Auto-Root-jflte-jfltexx-gti9505.tar.md5" file to the PDA field then rebooted the device. Then I added the "openrecovery-twrp-2.6.3.1-jfltexx" file to the PDA field, rebooted the device and the phone automatically opened in TWRP recovery. In recovery mode I wiped the cache, system and dalvik cache. I then went to install, browsed to the "I9505 Official_Google_Edition_4.3_by_Jamal2367_Finaly_v2.0" file on my SD card, rebooted the device and the Google logo came up on the screen for a few minutes and all was good. Got my new ROM, ran a root checker and all was good.
After some research I decided I wanted to use the Pacman ROM as it seemed to a lot more customisable. Using the same method I went to TWRP recovery wiped the cache, system, and dalvik cache. I then went to Install, browsed for the pacman ROM and the Gapps file on my SD card and everything installed ok, the phone restarted and the pacman logo came up everything was fine. Although I did notice on start up that I got this message.(and have had this error message ever since)
kernel is not seandriod enforcing
set warranty bit : kernel
After using the Pacman ROM for a day I noticed a lot of bugs like my apps would disappear, I couldn't use my banking apps and my phone was generally performing very badly. So I decided to remove the ROM and use CyanogenMod ROM under the recommendation of a friend. So again I pressed home+power+vol up to enter recovery mode but this time it didn’t enter the TWRP recovery it entered the stock recovery mode. This was slightly concerning but I proceeded to use the list menu and cleared the cache etc, browsed the SD card and went to the CyanogenMod 10.2 ROM I previously downloaded. It began to install but in red I got the error message stating that I didn’t have the right permission or signature. The phone rebooted back to the Pacman ROM. I tried the above three times and it still continued to boot back into Pacman ROM sometimes I struggled to even get back into recovery mode.
Soooooo I decided to try and go back to the Google Edition 4.3 ROM and play it safe, using the method from my first paragraph. But when it installed through TWRP I got an error message saying cant find MD5 file. The device rebooted and the Google edition logo came up on the screen but it seems to be locked in a loop. The Google logo wont go away and the phone vibrates once then three times quickly every 10 seconds.
I can still enter both TWRP recover and Download Mode. But I don’t want to mess around with it anymore without getting some advice. Any help would be much appreciated as I really need my phone working.
Thanks again
Aiden

Did you create a backup while on your first run with google edition? If so wipe cache, system, and dalvik and restore to your backup. Should put you back to where you began.
Sent from my LGMS769 using XDA Premium 4 mobile app

I know I should, but I didnt. Is it still fixable ?

*Update*
Couldnt help myself had to have a tinker around. Managed to get Cyanogenmod 10 working with Gapps. Gonna see how I get on with this. Although still would like to know I have been having all these problems.

Sometimes things just dont go as planned: p I have easily soft bricked my phone around 10 times and always able to fix it. You really should have made a stock backup before flashing anything. I recommend doing it now so you at least have a known working configuation backed up for future use. Trust me backups are your friends!
Sent from my LGMS769 using XDA Premium 4 mobile app

Thanks for your replies.
Ye gonna that right now Cyan Mod so far is running very smooth without any problems.
Regards
Aiden

Phone just crashed and now having problems booting up

So I'm here at work.. working with my phone plugged in, charging, doing it's thing which shouldn't be much when I look over at it there's a bunch of "application x has crashed" and then reboots. Except it only sort of reboots. It sometimes hangs on the reboot, and if I reboot it 3-4 times it might come up into the OS but then all those messages appear again and it'll reboot itself.
I don't think I've installed anything crazy recently and blocked updates a long time ago when I got it, and am rooted with TeamWin recovery on it. I go into recovery and do a fix permissions and permissions and I get a bunch of errors to the effect of "e: xml error parsing file"
I do see that I have a nandroid backup from about 3 months ago that I might just have to try restore, but it's just weird that it seems like the phone just crashed itself. Can anyone think of any options I can try before I do that?
Also I don't think the phone has ever been updated since I got it as I froze/killed that process. Should I try upgrading to the latest? Are there big fixes/security issues that I should be concerned with that would make me want to upgrade?
Thanks for the help.

natboy said:
So I'm here at work.. working with my phone plugged in, charging, doing it's thing which shouldn't be much when I look over at it there's a bunch of "application x has crashed" and then reboots. Except it only sort of reboots. It sometimes hangs on the reboot, and if I reboot it 3-4 times it might come up into the OS but then all those messages appear again and it'll reboot itself.
I don't think I've installed anything crazy recently and blocked updates a long time ago when I got it, and am rooted with TeamWin recovery on it. I go into recovery and do a fix permissions and permissions and I get a bunch of errors to the effect of "e: xml error parsing file"
I do see that I have a nandroid backup from about 3 months ago that I might just have to try restore, but it's just weird that it seems like the phone just crashed itself. Can anyone think of any options I can try before I do that?
Also I don't think the phone has ever been updated since I got it as I froze/killed that process. Should I try upgrading to the latest? Are there big fixes/security issues that I should be concerned with that would make me want to upgrade?
Thanks for the help.
Click to expand...
Click to collapse
1. What did you do to that x applications? Did you just disable like location in the privacy guard?
2. Well, try to wipe the x application's data in settings -> app menu. If you can't navigate to there, try wipe all your data via recovery
3. Try to dirty flash your rom
4. Change into another rom

After a bunch of reboots, I was able to get the phone up but half my applications were deleted including Google Play store and most other Google apps including Inbox, Gmail, Hangouts. I might be paranoid, but maybe it was a Stagefright virus, but I have no proof that was it.
In the end I restored my nandroid from 4 months ago and it's now stable. But seriously I wasn't touching it when it started and then proceeded to destroy itself. Very strange behavior.

A handful of problems after performing a factory reset

Hi.
I installed some dodgy app which required root access to operate (but it didn't even though I allowed it in SuperSu) and this is where my problems started.
First of all, I noticed each and every app I tried to run would immediately crash. That included system apps, such as the Settings app. At that stage I was left with only the launcher working and attempts to uninstall apps would also cause a crash. Even the shutdown menu was broken and the phone hung up so I was forced to reboot it by holding the power button for 10 seconds.
After that, the phone would no longer be able to boot, it was stuck in a boot loop, but recovery still worked (TWRP for that matter) so firstly I wiped the cache partitions (including dalvik cache) but that didn't help, as the phone still wouldn't boot. In this case there was only one thing left for me to try and that was the factory reset capability of TWRP which claimed to not even touch internal storage so I was fine with that and did the wipe.
Thankfully, the phone booted afterwards and it welcomed me with the first startup guide (the language selection dialog was really buggy but that's Huawei's fault) and the phone was seemingly ok, except that the whole internal storage had been wiped out but not only that - the external microsd card was empty as well! Could you believe that? I couldn't. TWRP promised not to touch internal storage and the external memory card wasn't even mentioned but why would it wipe it anyway?
That's for the story behind it, now for the actual problems I'm facing right now:
The stock remote app is gone
The boot animation has changed to a different one (now it's a silver "android" logo instead of the "honor" logo)
Battery usage stats are not available (see: http://i.cubeupload.com/BXCknW.png)
Sound quality from the built-in speaker seems noticeably worse
Hereby, I'm asking you guys to help me out with all of this.
The "remote app missing" problem could be solved by someone sharing their apk file with me, that's probably the simplest one to fix.
As for the boot animation, I have no clue as I don't even know what files are responsible for that.
The same for the battery stats problem, I'm already through a couple of full-charge-to-discharge cycles as well as wiping the cache partition, but the problem remains.
The sound quality probably has to do with the DTS sound enhancer. The config file for that is either "/cust/unicom/cn/xml/dolby_config.xml" or "/cust/unicomelectric/cn/xml/dolby_config.xml" and I'm asking you to upload these files somewhere so I can compare them with mine to see if anything is different.
The device I'm using is the H60-L02 variant running the B532 ROM.

Does the 3 buttons method erase internal storage as well? I've already set up quite some apps and having to do it again wouldn't be the most pleasant surprise. But at least in this case I could make some backups and whatnot...
Also, would it work if I flashed B535 straight away or does the 3 buttons method expect the same version which is already installed, in this case B532?

pudup said:
It will wipe internal storage. You can flash any *full* ROM as long as you're not moving up or down from kitkat-lolipop/marshmallow.
Click to expand...
Click to collapse
Okay, so I decided I'd do the whole thing today. I downloaded the full B535 ROM on my PC, backed up all the stuff I care about from the phone to the PC as well, and also I downloaded the MultiTool.
Though the MultiTool thread says this in bold red:
VirusPlus said:
EMUI 3.1 WARNING! Update over rooted or system modded in EMUI 3.1 gives a BRICK.
You have to restore system and REMOVE root before every update in EMUI 3.1 for now.
Click to expand...
Click to collapse
So I also fired up Titanium Backup in order to defrost all the frozen apps, which went fine, and then I wanted to unroot the phone but I've been unable to do so so far.
To unroot, I launch the SuperSU app, navigate to the "Settings" tab and select "Full unroot". The problem being, it just gets stuck on the screen saying "Uninstalling, please wait...". I don't know how long it usually takes to complete, so far I've waited for maybe 10 minutes and nothing seems to change. Should I care about that? Is that warning about updating rooted/modified EMUI 3.1 resulting in a brick still true?
Can I skip this step and just flash the stock recovery followed by the 3 buttons method?
EDIT:
After some trial and error with the multi tool and different recoveries, I was able to finally unroot. Next, I flashed the stock recovery for B532 and attempted to do the 3 buttons method, but it would say "Install failed. The update package does not exist" (could be because I'm doing the update from a USB flash drive as I don't have an micro sd card big enough to fit the package). So I rebooted the phone into system and used the Updater to perfrom a local update where it would let me pick the USB drive. It completed without errors and then rebooted into some kind of updater (black background and some bluish emui colors) where it also took some time to finish thankfully successfully. I can right now see the phone booting and for what it's worth, the boot animation is once again the good old "honor" logo and not that ugly silvery "android" one
And now it's "Optimizing system...". I really hope it finsishes successfully as it's already a bit late here and I wouldn't like the phone to be unusable tomorrow :laugh:
36% ready...
46% it's kind of fun to watch this, and now 49%
I'd like to thank @pudup once more for helping out, I'm not really that much into flashing recoveries, roms and all that myself. Without your help I would probably be too scared to try doing something on my own :crying:
86%, 89%, 95% and 100%. Aww, what a relief Good old stock lock screen and wallpaper.