So I was running a stable CM12 ROM on my D800, but I decided to try MIUI 6. And I love it. After initially flashing it, I lost SIM connectivity, but after scouring for a fix, I was able to fix it by flashing a JB Bootloader and KK baseband. Everything was working great. Until I realized that I lost my recovery. Completely. Every time I try to boot into recovery, it just hangs at the LG Logo. I can't even factory reset. I try to reset from Settings menu, phone freezes. I try to hard reset through button combination and recovery, boots to LG logo and freezes. I try to boot to recovery through MIUI Updater app, same thing. I try to install zips through MIUI Updater, same thing. The thing that absolutely astounds me is that I can't even factory reset through system settings. The phone will boot, has data, wifi, bluetooth, the whole nine yards. But i cannot for the life of me get a working recovery. I have tried flashing Philz, TWRP, and CWM, all to no avail. I can use Rom Manager, and flash ClockworkMod Recovery, and it will say successful, but when I try to reboot to recovery, it just gets stuck at LG. Someone out there has to have a fix without flashing back to stock and starting over.
TWRP was working to flash the Bootloader and Baseband. After SIM started working, recovery was gone.
Related
I have a Nexus S 4g with ICS. Phone was rooted last year. Ran stock ICS for the past month (Sprint OTA update). Last week it rebooted when downloading an app. After the reboot all of my apps were "closing unexpectedly", not force closing. After about 10 minutes it tried to reboot and got stuck on the boot animation.
-Tried doing factory wipe/reset through the OS, TWRP, CWM and Fastboot. When it reboots, nothing has been wiped.
-Flashed Stock ICS and Gingerbread images. ICS will start and get the app close cascade, then get stuck on the splashscreen. Gingerbread hangs on the google screen/does not boot.
-Cannot write to sdcard but can copy everything off the phone to my PC. Toggling USB Debugging does not help.
Flashed stock rom using odin. It said that everything was successful but it booted up to the same problem.
disifer said:
I have a Nexus S 4g with ICS. Phone was rooted last year. Ran stock ICS for the past month (Sprint OTA update). Last week it rebooted when downloading an app. After the reboot all of my apps were "closing unexpectedly", not force closing. After about 10 minutes it tried to reboot and got stuck on the boot animation.
-Tried doing factory wipe/reset through the OS, TWRP, CWM and Fastboot. When it reboots, nothing has been wiped.
-Flashed Stock ICS and Gingerbread images. ICS will start and get the app close cascade, then get stuck on the splashscreen. Gingerbread hangs on the google screen/does not boot.
-Cannot write to sdcard but can copy everything off the phone to my PC. Toggling USB Debugging does not help.
I am out of ideas. I tried using Odin but could not find the PIT file for my phone.
Click to expand...
Click to collapse
if u have installed stock rom go to recovery and do a factory reset and clear cache
clear caches
I have done factory reset from the ICS UI, stock recovery (ICS and GB), CWM, and TWRP. I've cleared the regular cache, Dalvik cache, sdcard and everything that is clearable or wipeable in in CWM, TWRP, stock recovery. I've cleared the cache in fastboot and did "fastboot -w" (don't know exactly what that wipes) with no effect. I even had Windows try to format the phone. I have done any and all combinations at least three to four times apiece.
I tried Reflashing a viper one s rom (dirty flash) aroma got stuck at 90% trying to "restore stock sense camera". So i did an adb reboot. After that My recovery got bugged. I would go into a bootloop if I tried an adb reboot into recovery, stuck at the htc developer only warning screen.
If i try to manually go into recovery through the bootloader. It starts up but I can't flash anything. If i try flashing/fixing permissions/clearing cache, recovery just reboots itself or crashes and again goes into the bootloop. I tried reflashing twrp/stock recovery/cwm through fastboot. all of them have the same issue.
I'm now trying to use the Soft Brick fix, but after pressing clear storage I'm in stock recovery and the progress bar doesn't move. Please Help me someone
I've got a T-Mobile phone with stock updated to the last version, with TWRP 2.6.3.0 and root. Everything worked fine for a couple of months.
A month ago the phone started to boot loop with no apparent reason. I've wiped everything, re installed stock, rooted and used the phone again. I've thought it might be an app updated that screwed something.
Anyway, I've only got the basic apps on the phone and today it happened again. I've read that I need to boot into bootloader and selecr "CLEAR STORAGE", I've tried that but it goes into recovery and there I can only wipe the data. I've did that and rebooted and it didn't help.
Any other ways to fix this without re installing the rom?
I think that if you use the clear storage option, you will have to reinstall the rom. I believe it wipes the system partition as well.
If you want to do this, you should flash the stock recovery (get it here)
Go into the bootloader and select the clear storage option.
Then you can flash CWM or TWRP recovery again and install the ROM.
Let me start form the beginning.:-
My bootloader was locked and I was on stock 4.4.4 . I faced no problems at that time. I saw OTA notification for lollipop 5.0.2 update, downloaded it, installed it, device gets restarted, I saw new bootlogo and then bootanimation. Just after the bootanimation, the screen goes blank(back-light is still on). I waited for about 40-50 minutes, but the screen is still blank with backlight on. Tried rebooting 3-4 times but stuck after bootanimation. 1 time it booted successfully and I was presented with the lockscreen. I swiped unlock the screen but suddenly services was stopping one by one and various applications also getting force closes, even the launcher also got force closed. So I rebooted again, and again got stuck after bootanimation, getting only a blank screen with backlight on.
Now I booted my phone into recovery, factory reset it(also wiped cache manually) and then booted into system, still no good. I was getting the same blank screen after bootanimation. I tried rebooting 4-5 times and at one time, it got past the bootanimation. There I saw that the device didn't get factory reset(wallpaper, home screen icons were at that place only where it was before). Now again service got stopped and apps got force closed.
Now, I downloaded stock firmware images from here on xda and flashed it from bootloader. I was still getting blank sceen after bootanimation and occasionally it got booted and everything force closes again.
After trying everything, I unlocked my bootloader and tried flashing a custom recovery (so that i can try installing custom roms). But after successfully flashing custom recovery, I booted into recovery and find that it didn't got flashed (I was still on stock recovery). I tried flashing different custom recoveries 7-8 times, but the stock recovery persists!.
So, now the bootloader is unlocked, stock recovery is persisting after flashing any custom recovery, even the user data is persisting after factory reset, and I am unable to boot to system properly. I don't know what to do after this. Please let me know if this all means that some part of the hardware is failing in my moto g or if it can ever be come back to life.
Edit:- I have just booted into twrp Recovery(not flashed, only booted) and found that I am unable to wipe internal storage. Everything else like, dalvik cache, data, cache and system do not give error on wiping. Also, I am unable to delete any file or folder using twrp file manager
Thank you.
Hi, so short story is.
1. I had a backup of my stock rom that i did using twrp.
2. I flashed Franco Kernel for COS 13 downloaded from his website (https://kernels.franco-lnx.net/OnePlusOne/6.0.1/anyKernel/)
3. When i flashed i performed a Wipe dalvik cache from recovery
4. Reboted phone, and started optimizing apps but suddenly it rebooted.
5. Started optimizing apps but when it showed optimizing app 1 of 103 the phone keept restarting.
6. I decided to restore my backup made from TWRP, but then phone got stuck and restated everytime from the CYANOGENOS logo.
7. Since it was not booting, i decided to install from fastboot a clean CM13.
8. Flashed, finished and then the phone restarted, but heeey, again stuck in the CYANOGENOS Logo and restarting when the logo shows up.
9. I freak out and I don't know what to do.
So far:
fastboot is working
Cyanogen Recovery is Working ( tried the wipe from that, but still no luck)
When I plug the device directly to my PC, it shows "QHSUSB_BULK", but as i say: fastboot and COS recovery are working.
Can you guys help me, please
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
leokook said:
First of all, I let the phone charge till 100% on screen (yes, the charger indicator was working aswell)
Well, since my device was able to boot into both Recovery and Fastboot modes, I decided to flash a custom recovery one more time to replace the COS recovery. I flashed CWM 6 (because before TWRP was not helping) and performed a "backup" of the whole rom, just to see if it worked, and it did. After that, i wiped /factory reset from CWM.
Rebooted the device, and voilá I guess. The phone was able to boot into CM 13, now I'm happy to see that I was able to recover from this issue.
Still have no clue about why the FrancoKernel ended in a bootloop. Was the cache wiping a bad idea ?
Click to expand...
Click to collapse
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Mr.Ak said:
Yes,that's where it all went wrong.You should never wipe anything while flashing a custom kernel.
Click to expand...
Click to collapse
Lesson learned.