So i have the korean variant of the LG G2 (F320K)
I installed CWM which went fine. I then did an OTA update and it screwed up my phone. Basically my phone no longer boots into Android. It keeps going into CWM recovery. I cannot get into download mode at all. The phone no longer charges when turned off (It boots into CWM whenever i plug in the USB cable). So basically i'm stuck in CWM.
Tried factory reset etc... but nothing works. Tried flashing a different ROM but that doesn't work.
Can anyone help?
One thing i noticed is that under mounts, System is unmounted and every time i mount it and reboot i go straight to CWM again and system is unmounted again.
Related
So I was flashing a new rom on my phone (Liquid Smooth) and did a normal clean-flash. Booted in fine, set everything up, restored apps w/ Titanium and got the phone running. Set my DPI and restarted the phone. It got stuck at the splash screen for Liquid Smooth. Restarted, same thing. Went in recovery (TWRP 2.5.x) and cleared cache/dalvik but same thing. Did a clean flash and the phone booted up again.
Weird.
This time I just restarted it after I set up the phone and it did the same thing again. Now I had no idea what was going on. So I backed up all my data, went in recovery and did a complete format. Tried flashing Liquid and Omni, but TWRP kept giving me a "can't mount /data/user". Tried to mount it manually in the recovery, and it kept saying "Can't mount /data". Now I couldn't flash anything, and my phone wouldn't boot past the S4 logo. I have the MDL odin files saved alrady, so I flashed stock ATT FW back on, rooted again using CASUAL and I'm good to go.
Flashed Liquid again, and everything seems good, I've restarted the phone a couple times and it's been okay. However: is this any indication of faulty flash memory? Or was it just some sort of partition messup which happens from time to time?
Hi guys
(SM-N9005)
So yesterday I had liquid smooth rom installed for the past month or so (I have been trying a variety of roms for the last year or so) and I was getting some bugs occuring and decided to put a new rom on.
I booted into recovery, did the normal backup, factory restore, clear cache and dalvik, installed the rom and restarted my phone. It then went into a boot loop.
At this point I assumed it was no biggy, so I just went back to recovery and chose to restore with the backup... except it wouldnt. it couldnt recognise the file it had just made.
So I then coppied some previous backups to the external micro sd, stuck the micro sd card in, booted in recovery and tried to recover with them... couldnt recognise them.
I also noticed that when trying to reboot, it came up saying that I didn't have root access... even though I certainly have for the past year.
I tried flashing an updated version of superuser as that was the suggested method on some forum - didnt help the situation.
Now when my phone boot loops, it goes straight to android system recovery <3e> and nolonger have access to CWM
No idea what to do, and my uni work greatly depends on me having access to my phone :/
Any help would be greatly appreciated
my baseband version is LRX21V.N9005XXUGBOB6
i got some problem ... it freak me oute but i founnd how to back my stock firmware backk
you shoud find your firmware ... it can be downloaded from sammobile.
and flash tar.md5 file via ONDIN.
good luck!
I was trying to upgrade from CM11 to CM12, which went smooth except for GAPPS closing constantly. I read online that this was caused by an old version of the recovery, so I tried to update TWRP to 2.8.4.0. I first tried using the TWRP app from the Play Store (after recovering my Nandroid backup), which locked the phone where it would only try booting into recovery, but couldn't get there. Holding the power button to turn it off would result in a reboot right back into recovery, which of course never went anywhere. Now I am trying to re-install TWRP using ODIN but It fails every time [Complete(Write) operation failed.] I have an early S4 from AT&T and it has never had an official update. I can't remember which firmware it is using, but it is the original so I shouldn't have any problems there. Can anybody help me get this thing up and running with either TWRP or CWM and CM12 please?!
Update: I have been able to get the phone to boot by first booting into Download mode, then hitting the Volume Down button to cancel. This has twice booted it back into the OS. Still no recovery though.
Solved
I was able to install TWRP 2.8.4.0 from the app after getting the device to boot. It worked correctly this time and all appears to be well. Odd that ODIN didn't work though.
Sprint LS980 in an odd state after trying to flash CyanogenMod 12.1
Ok... so I got two of these Sprint LG G2's. I was able to successfully flash the first one with a minimum amount of problems considering I was just learning how to do it.
This second one is a problem though. Here's what I did:
I tried to root but it could not due to the version of the Sprint firmware on the phone. I did the TOT stock flash to get it back to stock. That worked fine.
Then I was able to root it via ioroot. Once rooted, I installed FreeGee and tried to install TWRP, that didn't seem to work, so I installed CWM Recovery. I did option two on this thread to try to get the loki stuff installed using openrecovery-twrp-2.6.3.4-ls980. That "installed" and I was able to boot into it. I installed cm-12.1-20151125-NIGHTLY-ls980 (same one I used on the other phone). That would not install via CWM and gave an error about not being able to lokify (or something like that).
So I said, OK, I must have done something wrong, so I tried to redo stock flash again. That acts like everything works fine LGFlash does it's thing (using LS980ZVA_01.TOT), but the phone boots up and does not seem to finish the install process. The LG logo comes up and not the Sprint screen that I would expect. I can do this over and over again and the results are the same whether I let it sit for an hour or 10 minutes after flashing. So now, the phone boots, but I can't do anything with the touch screen, and will then go into a reboot loop (getting into the OS but rebooting shortly after). I CAN get into CWM where I can wipe data/factory reset and wipe cache partition. After I do that, the phone will boot and will let me interact with it, but after a short time (a few minutes I think), it will reboot again and be in the same state it was before I went into CWM. I tried to do a factory reset in settings. It would say that two reboots would occur, but then nothing happens.
I'm at a bit of a loss as to where to go from here. I don't think that it's an unrecoverable brick, but heck if I know how to fix it.
In between reboots, ADB does see the device in ADB Devices, but shows that it's offline, so I can push an APK to it.
Here are the options that I get in recovery mode:
Reboot System Now
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Any assistance is greatly appreciated!
Ok.. well.. I downloaded and flashed ZVE and it seems to have greatly stabilized the phone. However, it seems that I have lost the ability to do download mode and recovery mode. I can still get into the device through ADB, but ioroot no longer is able to root the device, so I can't install any recovery. There is a system update available to install, but didn't want to do that unless I'm good an stuck in this mode.
I also don't seem to be able to enable the cellular service. I don't know if the update it wants to install would fix that or not.
Edit: I can still do ADB reboot recovery and get into recovery mode with these options:
Apply Update From External SD Card
Apply Update From Cache
Apply Update from ADB
Wipe data/factory reset
Wipe cache partition
Edit2: I was able to root with Stump. FreeGee won't run on ZVE, so not sure what to do from here. The phone does not work at all. None of the phone info is listed in About Phone. No IMEI or anything.
Edit3: I have been able to get TWRP installed and can boot into it. I have also verified that I can get into download mode now. I'm very concerned about my EFS info though. I did back it up, but not to the PC, so effectively I have no EFS backup and no way to recover the IMEI information. Not cool...
Hello,
I have an i9505 LTE International version (jflte) for about 4,5 years, working perfectly with the latest LineageOS until yesterday when my phone suddenly shut off itself (as like as I removed the battery). I tried then to turn it on again but restarted itself after the LineageOS logo appeared. I thought there was something wrong with the OS, so I've booted to recovery TWRP to flash the same OS again. The strange thing is that TWRP stopped flashing at +/- 20% freezing itself. After that I was not able to boot to recovery anymore.
I removed the battery, SIM card and microSD for about three hours. Tried again only with the battery and was able to install LineageOS again. After booting with the fresh installed LineageOS (I formatted the /system /data /cache partitions) the system was very unstable and slow. After 10 seconds the screen went completely pink and it shut off again and never came up (showing me the boot logo and rebooting - bootloop).
I removed the battery again and tried to flash, after one day, with odin the stock firmware. I had no issues while flashing but the OS won't boot. Therefore I flashed the TWRP to the recovery partition and it doesn't work. After 10 minutes without the battery I am able to boot TWRP but when I try to, for example, copy the logs to /data TWRP freezes and I cannot do anything else but hard reboot.
Someone knows what's going on here? Could the eMMC be seriously damaged/corrupted?
The strange thing is that, without the battery for 10 minutes plugged in, I am able to boot to TWRP and navigate through the menu - although after trying to format the /data and /cache partitions TWRP freezes. After a reboot I cannot boot to recovery anymore (it remains stuck on the samsung logo screen with the RECOVERY BOOTING and Set Warranty Bit: recovery headings.
My fathers old S4 has a similar issue, https://forum.xda-developers.com/galaxy-s4/help/s4-i9505-wont-past-screen-boots-t3810088
It seems so strange, I'm currently trying to get the files left on the phone safely of but it crashed when trying to do so and now I can't enter recovery.
But I'm trying to troubleshoot it as good as possible without risking loosing the files, and the strange this is that many S4s seems to have problems with the fact that it is a random restart and then goes into bootloop. But the thing that worries me the most is the fact that you were running Lineage while my father was running stock TouchWiz based on 5.0.1. That leads me to believe that this is a hardware issue, I'm considering unscrewing it and try to troubleshoot it. Going to get my hands on my fathers old extra batteries for his S4 tommorow, will see if that makes a difference.
Did you wipe the /data partition after flashing the stock rom? I had the same issue... After flashing LOS, my phone is bootlooping randomly and i tried to flash stock rom. ODIN does not wipe the data partition after flashing the original stock samsung firmware so the OS can`t boot due incompatible data( The lineage os data with android 7.1.2 is not compatible with lollipop). Try to flash the stock rom again, wait until your device restarts to the robot and hold the vol up+home+on/off to get into stock recovery. Perform a factory reset and then restart. You have to wait a bit (maybe 10 min)