Database Develop

Boot Loop

Please Help I installed a custum ROM and now I am stuck in a loop a skull comes up and droid and it continues till the battery is dies. I have tried to factory reset and nothing the only way to turn it off is to remove the battery can someone please Help

If the ROM is what's causing the problem, doing a factory reset won't change anything; it'll stil keep the same ROM in place. What you might want to do is download a more popular ROM, like a CM7 nightly, put it on your microSD card (using another phone or a microSD adapter, of course) and boot into recovery and flash that.
If that doesn't work, I dunno then. I got a bootloop the other day after using ROM Manager to flash a new kernel. Turns out it was the kernel because after a factory reset, it booted up fine. So I just chose another kernel and it's all good now.
You just might have a screwy ROM. Try reflashing it if you can. What was the custom ROM, btw?

Yeah I'd agree with the above; install another ROM and make sure to wipe cache and dalvik and if it still doesn't work wipe data as well. Note that wiping data will wipe pretty-much everything on your phones memory (SMS messages, contacts, accounts etc)

when it is cm7 than you should take an other kernel
Please, if you are experiencing random reboots (that involve the M logo) or prolonged screen freezes, you should revert to an older beta kernel that is free of the DSI errors. To do so, replace the boot.img in the update-cm-7...zip package with this one (from 0.04 version): http://code.google.com/p/cyanogenmod4milestone/downloads/detail?name=bootimg0.04.zip
Click to expand...
Click to collapse

Stole that from another Thread:
_Flash with any rom you have
_Milestone will auto reboot after flash done and loop
_Don't worry about that, remove battery in 5s and re-plugin
_Turn on your milestone: hold X and POWER to access Recovery. Select Wipe and reboot

Do you have a Droid or a Milestone? If you have a Milestone, which country is the device from?
I had a boot loop issue too on my UK Milestone when I tried to install CM6.1.2, version 28.01.2011 0.07-11.01.28. (http://android.doshaska.net/cm6)
This is what I did to fix the problem...
- Flashed UK 2.1 SBF file
- Flashed Vulnerability Recovery
- Rooted the phone
- Installed and booted into OpenRecovery
- Installed 15.01.2011 0.06-11.01.15 version (phone booted fine)
- Rebooted into OpenRecovery > Wiped Dalvik Cache
- Applied 28.01.2011 0.07-11.01.28 version
One more thing, you may need to update and/or change your baseband files.
I hope this helps.

Thx for the help guys I,m back up an running. Greatly appreciated
Sent from my Droid using XDA App

[Q] Is my phone unable to run ICS?

Since about a week I'm having the following problems:
It is extremely difficult to get my phone running ICS. I tried like 10 different ROMs, the only one currently working is Dark Knight. In between I managed to run CM9 Nighlty (2 days) and Infinitum 2.2 (3 days)
Why is it so difficult? Well - I believe, I'm doing all the correct steps: Flashing JVZ with Odin, rebooting, flashing CF Root, rebooting. Enter CWM, wipe data, cache, dalvik, format system -> Install any ICS rom
Currently, CM9 doens't work at all, I get boot loops after the initial reboot and can't enter recovery
Well, when I finally manage to install any rom (method: install Dark Knight - 5.5 atm - install any rom afterwards - my phone boots up correctly and is perfectly usable
But: Whenever I reboot, I keep getting boot loops with no chance of entering recovery. None of the usual methods work.
Stupid thing: I don't need to reboot. But every other day the phone tends to reboot itself (at least that is what I experienced and sorta guess)
Result: I take it out of my pocket or look at it on my desk and see boot loops after 2 or 3 days
What can I do, why is that? I don't want to run Gingerbread
I am not a noob - I have been running any rom before for one and a half years without problems and flashed mostly without any problems
Believe me - I have tried everything for several days. Flashing the recovery fix with Odin doens't help either. Afterwards I am a able to boot intro recovery but can't install any rom due to build.prop errors. However, I can flash a kernel... Result: boot loop. Solution: Start over with Gingerbread and Odin
The more I think about it, the more I belive there could be an underlying hardware problem. Maybe something with the internal NAND?
I am greatful for any help or new ideas which I haven't tried so far... Thanks a lot in advance!

I know it's a long shot, but maybe you have issues with datadata folder? Use root explorer and see how much free space you have there...
Maybe try this:
After Odin, When in CWM, flash first a new kernel (try devil.072). Make sure to mount folders with CWM before. After flushing, go to advanced and reboot recovery. Now you have a new version of CWM (which supports screen tuch...). Now, from mounts and storage, format everything. Now flush the rom you want - in this case, I recommend Slim 3.4. Don't install anything yet - just let it run after flushing. Just login to your google account.
See if it works.. hope it helps

Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop

Hmmm u have a interesting problem. Do u wipe everything and have u tried starting from a different stock gb
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

Yes, I wipe everything and tried JVZ and JVU as a starting point. Are there any other recommendations?

which firmware are you odining? maybe bad download?

Bara2 said:
Thanks a lot! Unfortunately, it didn't work.
I tried your method which didn't even end up in a bootloop but in recovery after every flash/try to reboot.
/edit: Speaking of reboots - I tried to install CM9 afterwards/instead -> boot loop
Click to expand...
Click to collapse
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!

shaharofir said:
which firmware are you odining? maybe bad download?
Click to expand...
Click to collapse
I agree many try a firmware from stock firmware from xda
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

swent said:
Just try it again but do NOT select reboot recovery. It is a common bug that you won't be able to leave recovery again. Just reboot the phone and be sure to quickly press 3 button combo again to get into recovery again. You should then be able to format / reflash and so on. Just make sure you never select reboot recovery when you just came the long way from odin. In doubt just do as I stated: normal reboot and press 3 button combo quickly.
Good luck!
Click to expand...
Click to collapse
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
/Edit2: I'm going to stay on Gingerbread for the day. I need my phone and intend to enjoy the fantastic weather for the rest of the day... Will be back this evening. I am glad for further feedback and ideas

Bara2 said:
Ok, That shall be my next try Btw: Another strange effect: I flashed Dark Knight 5.5, did nothing but click through the setup assistant rebooted - and voilà - boot loop.
Will report back in a few minutes Thanks a lot, guys!
/Edit: Well - a litte success... I was able to boot into the system. First thing I did was change lcd density and rebooted - everything was fine. As I didn't have wifi or data connection I wanted to flash another kernel (devil) and hit reboot recovery from the power menu.
--> Boot loop again.
To the other guys: I tried JVU and JVZ with different downloads and two different laptops. Which starting base should I try next?
Click to expand...
Click to collapse
Umm well I use jvu and have no problems. This might sound stupid but when I had a similar prob (I flashed a kernel on dark knight 4 and got into a bootloop and couldn't enter recovery) I did a factory restset after backing up my SD card data and flashing jvu, then I reflashed jvu. Rooted, wiped rebooted recovery, wiped again, rebooted recovery again, then I flashed dk 3 then dk 4 without a wipe, the restored my apps and copyed my SD data back - I hadn't been able to flash a rom since the bootloop I got it working with dk 3 but then I got no boot animation and I just stopped there, the above process worked for me I know u on dk 5.5 but try dk 3 you should find the link in the dk thread around April 12-16 this year.
If you like my posts hit thanks
Rom: Dark knight 4
Kernel: Devil Kernel
Keep it ANDROID!!!!!!!!

You may flash the new kernel right away after flashing the desired rom. Maybe that would stabilize everything... can't make any more sense of it right now, sorry :/ Maybe you could try to use the ultimate kernel cleaning script AFTER flashing the rom and BEFORE flashing the new kernel (with no reboot in between).
Script is somewhere out there, I'm gonna search it right now...
/EDIT: Wasn't really hard to find after all, there you go: Ultimate Kernel Cleaning Script

try this firmware for odin:
https://www.sugarsync.com/pf/D6246658_3937073_82911

Motorola Milestone A853 Major Issue!!!!

Hi all, my name is Daniel.
I am using a motorola Milestone A853 for the past one year and never faced any issue while rooting or installing custom roms right upto cm10.
from last two months the milestone has not been working properly. It so happened i had installed CM 9.0.1d and everything worked fine. but once the battery died the phone did not boot up and was stuck on moto boot logo and kept restarting from there. I tried to go into open recovery (fufu minimod) using the X+power key and it goes into recovery but after loading recovery it did not display any options and the other text was red in color and it showed the error failed to load menu.init. I replaced the update.zip file along with the open recovery folder, but still nothing worked. I then tried another open recovery but still open recovery never loaded. Then i SBF'ed the device and went back to stock and was able to use my phone again. But then when i try to root the device again i am not able to root using vulnerable SBF as it does not install though RSDLite shows pass. Then i used superoneclick to root and that did the trick. But still open recovery never installed or load. Luckily androidiani recovery which displayed an error cannot mount but still created the menu and i was able to install custom OS but only cm 7.2.4e and not cm9 nor cm10. I cannot reboot the phone as the phone never starts up. only after clearing dalvik and wiping cache phone boots up. After a certain time now i still cannot install cm7.2.4e as it does not load and gets stuck on custom bootscreen, so i installed MIUI rom which works and starts up but i still can never reboot my phone.
Errors Seen E: cant mount /cache/recovery/command
Kindly help as the phone is just barely working.

Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.

Tried Everything
Erovia said:
Your phone has some serious issues...
How stable it is with stock rom? Maybe You should flash a stock 2.2 and see if you have any issues.
If not, then flash vulnerable recovery and so on, step-by-step.
Maybe it will be easier to locate the source of the problem this way.
Click to expand...
Click to collapse
Thank you for your reply. I have tried flashing stock 2.2 and still I cannot reboot the phone without wiping cache and using the reset factory option in stock recovery. Using superoneclick I can root it and install androidiani recovery but I cannot use cm10 or cm 9. after installing cm9 the phone just restarts after cm9 boot screen and after installing cm10 the phone shows the stock android boot screen. cm 7.2.4e installs as well as miui but if battery dies or if I have to restart the phone if it gets sluggish and slow then I cannot...everytime for the phone to boot I have to wipe dalvik and cache for custom roms and for stock roms I have to wipe cache and factory reset.
SO basically I am stuck...have tried changing the sd card, repartitioning the sd card, but nothing worked
Open recovery cannot be used only andoidiani works after popping up some errors.
Kindly help.

[Q] Razr i - no possibility to flash custom rom or stock - bricked?

Hallo together,
I seem to have done something wrong while trying to flash the rom "RazRi_JB_X-2014-Jul-16".
Here is what i did:
- Unlocked to bootloader using official Motorola homepage
- Flashed CWM (non-touch) recovery using "Recovery Flasher by LeBobo v1.7", USB-Debugging was on
- Rebooted into bootloader and flashed "RAZRiRoot2" to prevent Stock-ROM from overwriting the recovery
- Tried to install the Custom ROM using CWM, but it fails to wipe cache (stuck on line "Formatting /cache")
Because it didn't work, i tried to reset everything as it was before to be able to try again - flashed stock-recovery using the Recovery Flasher by LeBobo, booted into bootloader and selected "Factory". The cell is now just showing the "Warning bootloader unlocked" warning and nothing else happens.
When i try to select the recovery in the bootloader menu, an image of a Android laying on its back with an opened hatch and a red warning symbol showing a "!" appears and nothing else happens.
I seem to have bricked my device, because i cant't really do anything now - is there any solution?
I read through different topics but could not find a real solution to this particular problem...
Thank you so much in advance for your help!

It's not bricked
At the moment u enter stock recovery with that android and red warning sy,bol, u need to press bot volume up + downp. Than it will enter stock recovery mode.
Those are the following things u can do to get custom rom,
1. Flash another recovery, cwm touch, cwm non-touch, twrp. They all work a little different.
2. Flash the custom rom and wipe everything, The wip can take some time. sometimes it will be seconds, sometimes it will take a couple of minutes. Every recovery behaves different, and every flash/wipe too.
3. enjoy
If u really want to go back to stock, flash your stock JB firmware by RSD-Lite.

Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?

StarGeneral said:
Thank you very much for your answer. I restored the stock rom using RSD Lite and did a clean install of TWRP.
Then I did a Factory Reset and started to install the custom ROM.
The TWRP is now stuck at "Flashing File 1 of 1 /external_sd/RazRi_JB_X-2014-Jul-16.zip".
Is it normal that it takes more than five minutes or is something going wrong here? Is there something i forgot?
Click to expand...
Click to collapse
5 minutes is a bit too much. But that's the problem with this device. Every device behaves different and we haven't found out a solution too it.
At the moment i can't do much for you. I can only say try to wipe the partitions mannualy. Wipe system, data and cache. and mount system. And then try to install it. Maybe if that doesnt do the trick try again another recovery.
This from KTR-ROM
Code:
- Enter in TWRP or CWM
- Wipes required: data, system, cache y dalvik
*In CWM mount system must format before (Mount and storage -> Mount system)

Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!

StarGeneral said:
Thanks again - that was it.
For some reason, TWRP did not automatically wipe the system-partition. It had to be mounted + wiped manually.
Not the custom ROM is up and running well. Installation took 35 minutes for some reason though...
Thank you so much for your help!
Click to expand...
Click to collapse
nice, glad that it worked

Every ROM install boot loops

I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?

monkeny said:
I have had several roms, over several devices, over several years. I have never had issues before.
I have Note 4 T-Mobile running 4.4.4. I rooted, installed TWRP and am trying to install cm-12.1-20150509-UNOFFICIAL-temasek-trltetmo
I tried installing a different ROM last night and the same things happen.
When I wipe Cache it removes the TWRP
I install TWRP app, then install TWRP 1.8.6 or whatever using the TWRP app
Reboot into recovery
Flash the ROM and Gapps
Wipe, wipe again just to be safe
Reboot
It goes through the CM logo to where it initializes apps, goes through them all, reboots and does it all again. 2 different ROMs did exactly the same thing. I dont know what im doing wrong. I tried installing TWRP With ADB but it hangs on "waiting for device" When I adb devices my hone shows and I have USB debug turned on. After I finally quit and pulled the battery It said no OS available so I had to DL and reflash stock image.
I am beyond frustrated now,
Any ideas? What info do you need from me?
Click to expand...
Click to collapse
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off

BACARDILIMON said:
You've got a nightmare. Head back to stock with Odin. Start fresh something with your base is off. Either wrong baseband orkernel but something off
Click to expand...
Click to collapse
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.

monkeny said:
I just flashed stock, used kies to update to latest and ill try re-rooting and re installing TWRP and doing it all again. this blows.
Click to expand...
Click to collapse
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit

monkeny said:
updated to 5.0.1
Odin flashed CF Auto Rooter
Flashify the TWRP
Rebooted Flashed the above posted ROM and GAPPS
Wiped Data
Rebooted
Stuck in the damn initializing apps boot loop again.
I have no idea what could be the issue. I quit
Click to expand...
Click to collapse
Which rom u trying

few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.

nosympathy said:
few thoughts.
First verify the MD5 of your download of the rom. make sure it wasn't corrupt. Second. Flash just the rom only and boot, then flash gapps and boot.
Click to expand...
Click to collapse
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.

monkeny said:
I think flashing just the ROM and then gapps did the trick. Seems to be up and stable. Man Ive never had so many issues before blah.
Click to expand...
Click to collapse
I have not messed with CM since I had the Note 2, which was until the Note 3 came out. Was a different carrier too. Generally the rule was flash CM then boot then reboot and flash GAPPS. I haven't looked but I would assume it is still the same.
Glad it worked