please forgive me if this has been asked before. i've tried searching but can't seem to find any fix. my phone was working great but i wanted to try a new rom since i was getting bored. my mistake.. anyway i have CWM recovery on my atrix and it worked good. i've flashed roms before.i was flashing between Neutrino ROM V2.9 and V3 trying to see if i could get the CMsettings to work on V3 without crashing. anyway after a while i gave up and decided to full wipe and just flash V2.9. after the ROM flash i reboot the phone but got a boot loop so i pulled the batter and tried to boot into recovery to wipe and flash again but when i select Android Recovery it just hangs at a black screen. what happened? can it be fixed quickly because my battery before the final flash was about 30%
BTW.. i've tried to reflash the recovery through fastboot and my compute the way i did it when i fist unlocked my phone and flashed the recovery but still no luck... still hang at blank screen after selection Android Recovery
never mind i fixed the problem.... had to flashed a different recovery (in this case TWRP) and then flash back to CWM recovery. idk the reason why but it worked and now my phone is back on and just in time with only 5% battery life left after all the trial and error flashing..
ok i figured out what caused my recovery to crash in the first place. its the gapp addon. when i flash that zip and reboot i get a boot loop and my recovery is gone. first i though it was the zip file that was damaged so i re-downloaded the gapp addon from Neutrino ROM V2.9 fourm but now chrome says the zip is infected so ok i went and download the full gapp addon for CM7 rom and that flashes without crashing my recovery but when the phone restarts i can't access half the gapp like market and gmail and a few others. they show that they are installed in Manage Applications but they don't show up in the app drawer.. whats the problem now? i've never had this problem before
Related
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
You can't get in CW recovery or stock recovery?
Sent from my ADR6400L using Tapatalk
Did you try reflashing CW through ROM Manager?
Yep. very strange. I even tried to wipe the phone with factory reset, and just get stuck on white HTC screen. I had deleted rom manager because of something else I read, and can't get it back, But I can't even get to recovery from bootloader.
You can get to recovery through the bootloader by shutting off the phone and turning it back on holding down the volume button and pressing power toggle down to the recovery option and press the power button
Sent from my ADR6400L using XDA App
Orio56 said:
I flashed CM7 last night, loaded GAPPS, and the market was updating my apps, when I noticed none of the apps were updating. updates were all failing. I went into recovery and restored BAMF 1.5 remix. Now I have a problem. I can not download or update anything from the Market, all attempts fail. I cannot access CW recovery, the HTC white screen is as far as I get. I deleted rom manager, and tried to access CW recovery and still failed. I tried to do a factory reset, and still only get white HTC screen. Tbolt is functioning, I just can't fix my issue. Please help. Thanks.
Click to expand...
Click to collapse
Actually I spent a good few hours yesterday trying to help Orio out and we attempted a quite a few things to try and fix the recovery issue, this post should offer a bit more insight to the methods used;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Never once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
Hi all,
Today I wiped all data and cache from my device and installed VillainROM from CWM Recovery Manager. Install looked fine it said that it finished, so I went to reboot.
The device was stuck on the Samsung Galaxy S II logo with the yellow triangle (!) for around 10 minutes. I then turned it off cause I realized it wasn't going to boot.
Anyone have any idea why this happened? I restored a backup of my previous ROM and my phone booted up real fast and it was fine.
Could just be a bad download?
Sent from my GT-I9100 using XDA App
Try flash it again before it boots. IE: Flash from zip, then go back and falsh from zip again.
I've had to do that with CM...
OK will try that, cause the same thing happened to me when I installed Cyanogenmod straight from Rom Manager. Thx
Update: No go, I also made sure Deluxe Settings was uninstalled before I went into recovery. It's stuck at the boot screen.
However, upgrading my previous ROM (WanamLite v4.0) to WanamLite 5.2 worked fine and the device booted. It was exactly the same procedure in recovery mode but a different ZIP file.
Will try another ROM like LiteningRom and see if anything changes. I don't think it's a CRC error because I open up the files before I copy to the device to see if WinRAR pops any CRC errors.
I'd start on the thread a few up from yours.... the one that mentions if you have a boot loop
Sorry, I didn't realize it was a boot loop because it wasn't actually looping, just stuck on the image. Is that considered a boot loop?
I'm running into a weird boot loop problem with my Atrix 4g. My phone is unlocked and I recently flashed to the Neutrino 2.5p GT update from 2.5 GT. I would usually do a clean install by doing Moto-fastboot -w, erase system/boot/preinstall and then install from the zip but this time all I did was install from the zip. After installing 2.5p GT from the zip, the phone booted up without any issues.
Now my problem started when I flashed the add ons. I re-downloaded and flashed the following add ons:
Live wallpaper add on
Sync add on
Theme Chooser add on
Deskclock/Default CM7 Alarm add on
GPS Mod (Pulled the US.zip file and flashed it, didn't flash "GPS Mod.zip")
Right Aligned Clock Mod
Lite gapps
After flashing the add ons my phone reboots itself before it can get past the Motorola dual core spash screen. The weird thing is now when ever I try to fastboot into my phone using rom racers tool, it says it's waiting to connect to the phone even though it's connected to my computer. I also tried to get into the android recovery but it keep freezing and rebooting after I select the recovery option.
Knowing this, what is the best way to go about getting my phone out of this boot loop? Would this be a job for NvFlash? (I'm unfamiliar with NvFlash, so this is just a guess)
Try to do a factory reset in recovery.
That should fix it
My problem is getting into recovery mode to do a factory reset. Right now my phone freezes and then restarts the boot loop process whenever I choose the recovery option. Are there any alternative ways of getting into recovery mode besides holding the power button + vol down and scrolling down to the recovery option?
I ran into the same problem the other day. I used http://forum.xda-developers.com/showthread.php?t=1314607 to reinstall recovery.
Sent from my MB860 using xda premium
Can you get into Fastboot?
Try:
fastboot -w
fastboot reboot
That worked for me when I was stuck in a boot loop(going to stock)
Yeah. There was a boot problem on 2.5p. The problem was quickly fixed, but now there is a new 2.6 version that blows all previous away.
Sent from my MB860 using XDA
ce12373 is right. The new 2.6 is sweet. You might also try pulling the battery, that seems to help a lot of people.
I would get into fastboot and do a full wipe then reflash from what i have read he suggest in the OP of the rom thread to do a full fastboot wipe
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
i'd tried to manualy flash the boot with my current firms boot.img and still no go... the damn touchscreen update screen keeps showing on no matter what....
thanks for everything
i change the firmware and start logo changes too so booting it's changing why the hell the touchscreen update keeps appearing... grrrrr i even installed a chinese firmware and a equivalent screen appeared i'm pretty sure it says: "Touchscreen Firmware Update in Progress Please Wait" but in chinese XD really don't know what to do anymore...
some ideas please?
i just don't know what to do anymore... does anyone knows what makes the phone try to update the touchscreen firm? today i installed the CWM in boot not in recovery just to test if the damn thing would go to the touch updt screen again and it just boot to the CMW like it should (normal because i'd flashed the CMW in the boot place). now i flash a new firmware (that will flash the correct boot.img) and the thing keeps holding on the touch update... i'm really out of ideas now
one other thing it's that if i install the TWRP in boot it won't boot in TWRP like it shoul... it stucks on oppo logo.
well i managed to install the same firm i had and have no touchscreen update... but if i install any other firm the message appear...
When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.