I was on stock F240L20D, 4.4.2 Kitkat, rooted, PhilZ Touch 6 installed. I've tried some ROMs before but reverted back to this one. So, basically, I've been to the recovery several times, but only used the ADB method to access it, and I've made several backups too.
However, one thing that happened today has frustrated me completely. Long story short, I thought about making a backup again, although this time, I used the power keys to get to the recovery instead of the ADB method, backup completes successfully, nothing wrong just yet, but just as I tap on 'Reboot System Now', it boots back in to recovery.
I've tried everything, tried using all the ADB commands, even going through all the options in the recovery, but it always seems to boot back in to the recovery. Really can't figure out what's happening. Any help would be extremely appreciated.
UPDATE: So I've flashed a KDZ, the Lollipop one using the LG Flash Tool. It's taking a bit too long to start, currently stuck at the U+ Lte logo. I hope it gets fixed.
UPDATE 2: It says Android is upgrading, YES YES!!!!! This is so exciting, but I'm still not convinced.
With most of cwm version after 6.4.7, any time you use power + volume up to access the recovery, you will get the boot loop. Go here and down load the zip file from the first post. Flash the zip and you should be go to go.
http://forum.xda-developers.com/showthread.php?t=2619403
Related
Hey guys,
I went to flash a new stable build of Froyo on my Desire this morning.
And i backed up using Clockwork, and then the ROM all installed fine. But once the phone had booted up, it stayed on the custom boot logo, despite the keypad lighting up, the green charge LED coming on and me being able to lock and unlock the phone.
So i figured that this was a problem and went to back to restore my old ROM and carry on like i have done many times before. However once i have booted into Clockwork, and gone to the recovery section, i select my most recent backup and the device then says "No Files Found" in the recovery zip.
And when i try to install update.zip from my SDCard the device just flashes up with installation text for about 2 seconds then vanishes and goes back to the clockwork menu having done nothing
What can i do?
i wouldnt worry about it too much
your phone completely works and youre not restricted of any access
seeing that clockwork is not finding any files have you tried making a new backup?
have you tampered with the recovery lately?
if recovery is not finding any files then maybe there is a problem with it, and if i were you i'd reroot my phone with unrevoked to re-install recovery.
if your recovery actually just does not work it could mean that the recovery image is corrupt, this can be fixed by installing a RUU (note that this will unroot your phone but re-install the recovery image).
if this is not the case then im sure im soon to be corrected by someone more knowledgeable than me
Well, i wiped the Cache and Data and now the phone boots up and functions fine, however both mobile internet and Wi-Fi both dont work, but i figure this is just the rom i am using.
So i'm just gonna reroot, sideload clockwork and what not and then try putting the Desire HD rom on it haha.
Thanks for the help
So here is a little back history.
I just recently purchased a GNexus from Sprint
Unlocking Bootloader and flashing Twrp went Great.
Backing up original stock rom went great!
My First Issue
My problem started when I flashed a JB rom. I notice that the phone was taking extremely long to boat up. Stuck at JB Boot Screen for about 45mins. I immediately thought that okay. .maybe im missing some type of requirement or twrp needs to be updated. So I battery pulled my phone.Attempted to go back into recovery and restore my old stock backup. WIth that being said i found that TWRP is corrupted. I did another battery pull and tried once more (same results)
I did another battery pull and booted to the bootloader when I selected recovery this time a screen popped up that allowed you to a factory reset (It was not the original TWRP Screen) My idiotic mistake was that I choose yes which then deleted my nand backup. As you now see I have a nexus that does not have a rom installed
I have been able to successfully adb push twrp back to my phone and TWRP comes up when I boot into recovery.
Here comes my second issue.
When I adb push a rom to the sdcard it transfer fine. I have been told to reboot recovery when you adb push a file to it. Therefore I reboot the phone and boot back into recovery to find out that the rom is gone. I have even tried to just directly flash the rom when I transfer the rom to the phone via adb push. TWRP states that the rom installed successfully so i reboot and the phone is still at a softbrick stage where I just have the google logo and the unlock bootloader at the bottom. When I boot back into recovery the rom.zip is no where to be found.
I have tried recovering by using ODIN and successfully followed each step for the GNEXUS CDMA\LTE version. Once again upon reboot I still receive the google bootloop of death.
Can anyone help me get my phone back to normal I will truly appreciate. I don't believe I truly bricked my phone because of that fact that I can still boot into bootloader, recovery and ODIN mode.
Specs of my phone: (From Bootloader Screen)
Product Name - tuna
Variant - toro 23GB
HW Version - 14
Bootloader Version - PRIMELD02
Baseband Version - L700.FD02 CDMA - L700.FD02
Carrier info - None
Serial Number - (Do I have to list this?)
Signing - Production
Lock State - Unlock
Once again any help is truly appreciated. I only had this phone for one day.. lol only made 2 calls on it before I screwed it up :laugh: (On stock rom)
After you ODIN stock it will bootloop. You don't have a custom recovery anymore, but if you remove the battery and then do "powers and both volume keys and select recovery" In recovery you will see a android with a red X. Press "power and both volume keys again" This time you have android system recovery that's in blue. Choose "wipe data/factory reset" and "wipe cache partition" . Then "reboot system now" after all that's done. You phone will boot up to factory in 3-5 min.
Reread everything you said... First thing first get back on stock. I used Odin method. Then follow steps above as it will bootloop.
dallastx said:
After you ODIN stock it will bootloop. You don't have a custom recovery anymore, but if you remove the battery and then do "powers and both volume keys and select recovery" In recovery you will see a android with a red X. Press "power and both volume keys again" This time you have android system recovery that's in blue. Choose "wipe data/factory reset" and "wipe cache partition" . Then "reboot system now" after all that's done. You phone will boot up to factory in 3-5 min.
Reread everything you said... First thing first get back on stock. I used Odin method. Then follow steps above as it will bootloop.
Click to expand...
Click to collapse
ok, i will try this.
Thanks
After trying what you stated above i was able to successfully return to stock.
Thanks again for your help.. It's funny how something so small can lead to hours of debugging and searching for the answers.
Hey look on the bright side....you won't make the same mistake again!
I made the mistake of flashing the Touch CWM last week and accidentally wiped my SD instead of System as I was trying to flash a new rom with a full wipe....I wasn't impressed!
So now I'm back to the non touch screen recovery which I'm used to and harder to make a mistake on.
Sent from my Galaxy Nexus using Tapatalk 2
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
christanya99 said:
I'm trying to install CM11 to my Ouya. ADB recognizes it as a device but when I "adb reboot boot loader" the device reboots, screen goes black for several minutes and then it just boots right to Ouya OS.
I had the device rooted a while back and I think CWM was installed. I did a factory reset though a few months ago. Could I have bricked this thing?
I have also tried a usb keyboard and hitting alt+print+i but get the same result.
Click to expand...
Click to collapse
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
newbyp said:
I had similar issues a rooted ouya with CWM Recovery on but I could not boot into recovery, I got the black screen and if I hit the home key I just got the standard android recovery not CWM. I read that this could be due to an OUYA update. As hard as I tried I could not reload CWM. I finally fixed my issue by reloading Superuser. For some reason I was then able to run one click recovery and it reloaded CWM Recovery for me. Since then I have upgraded recovery and loaded CM11. Only issue I have is now I don't get the boot menu just straight to CM11.
I am just a user not a programmer but I believe the issue may be that your recovery was overwritten by the ouya update and then you are unable to load CWM because permission issues.
Try hitting the home key when you have the blank screen, if you get Andriod Recovery then you seem to be where I was.
Good Luck.
Click to expand...
Click to collapse
Thanks for the advice.
I managed to make it into stock recovery but can't seem to get to CWM still. I reloaded Superusuer and the tried Oneclickrecovery. ADB shows success and say's I should be in CWM but I just get a blank screen.
Today I received my GT-N7105 back from the repairers after having the screen replaced, or maybe the whole phone replaced as for some reason my phone was un-rooted! God knows why they would have to do that to replace the screen.
So I've just rooted again and installed ROM Manager and attempted to flash CWM recovery, according to the app it went fine, but when trying to boot to recovery using the ROM Manager app and the volume up + home + power method I'm met with the stock recovery.
I have tried using Odin to install CWM recovery but the device freezes on the boot screen every time I try, and freezes there when I take the battery out and attempt to boot the phone again. So I have to root again just to get the device to turn on.
Its been years since I flashed a custom recovery so tried following a couple guides, but no luck.
I want to flash CyanogenMod to the device but cant do this without CWM (I've never attempted to use TWRP, better the devil you know!)
I have noticed Knox has appeared on my device, but I have not activated it as I hear this causes issues with rooting, and the reason I think this is a different device altogether is the flash counter was at 0 when first rooted this one, but I must have pushed this p to at least 15 before it went in for the repair.
Am I missing something? Please don't make me have to use the bloated to the heavens stock Android!
Thanks in advance and will be thanking any help.
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Saaber said:
I just upgraded my rooted and bootloader unlocked Robin to Nougat last night by installing the official upgrade files from the Razer Community forum. I've tried installing TWRP several times through fastboot, and each time I can get the phone into recovery, but the phone will never boot into the system. It hangs on the black "Nextbit by Robin" screen, and never goes past it. If I turn off the phone by holding down the power and volume down buttons, and then turn it back on, it still won't get past that screen. I can always get into TWRP, though, but no matter what I do, the phone won't boot. I've been using TWRP 3.1.0. Is there a different version that's required for Nougat?
Click to expand...
Click to collapse
My guess is you messed up the boot.img, or worse you corrupted some partition. If it's the boot.img, go get the latest factory image, unzip it, and move the file 'boot.Img' onto where your adb and fastboot files are located. Then go into fastboot on your Robin, and run this command on your PC:
Fastboot flash boot boot.img
If you corrupted something, you basically need to go into fastboot and use the flash-all.bat in the already unzipped Robin_nougat_88 folder to bring your phone back bone stock.
Hope that helped
Had this issue with my phone at first, but eventually just fixed it anyway by flashing the decrypted boot.img.
I ended up fixing it the same way you did. No matter how many times I took it back to stock by flashing the files in the Robin_nougat_88 folder and then flashing TWRP, no matter which version of TWRP I used, it would never boot. I finally flashed TWRP, then booted back into recovery, wiped the phone, loaded and flashed the decrypted boot image and SuperSU, and then the phone booted fine. I should have just done that in the first place since it was always my intention to unencrpyt it and rooted it again, anyway.