hello newbie here
so i had until now a stock version of mm on my LG G3 D855 (i guess the phone is european because im from israel)
i tried to change the version to cyanogen mod 14.1 cuz lately my battery has been dying pretty quick (and i basically had no idea whatsoever on what i was doing)
so something happen along the way while i was following the tutorial and the phone just would get stuck on the LG screen with nothing happening. i tried a couple of methods (both TOT and KDZ or something like that) to just get back to some sort of functional phone (i really need it for work) with no luck.basically i see a MiniOS screen of some kind every time i boot for a couple of seconds then it goes to a blue screen saying Factory Reset Status 2. I have no idea what to do now and ill really apreciate to get some sort of help.
thank you very much.
Try and boot into recovery then you should be able to drag another rom onto your SD from your computer. Then you can flash a marshmallow build or fulmics easily. Probably I would recommend the most recent fulmics if you are still learning about flashing and what not. They have a good installer which is easy to use and it is near bugless. All Nougat ROMs have some fairly large bugs, so you probably don't want to be using that for work unless you know a bit about working around these problems.
Related
Hey guys I really need your help with something! I recently rooted my LG G3 using stump and downloaded an application that needed to restart my phone so I did and now when i try to turn my phone on all I see is the LG load screen but nothing will happen after that. The LED continues to flash at the load screen, but it wont go anywhere. Also, I have tried to wipe cache, factory reset, and apply updates in the recovery area but nothing seems to work. I have also tried doing a factory data reset but like everything else i can only make it to the load screen. This is the first device i have ever rooted so I am very new at this but I really need some help!
Sounds like the app did something malicious. What app?
I would like to make a suggestion for you and for other noobs planning to root and mod their devices.
Firstly every single person whom ever tweaked their device flashed custom ROMs, Kernels etc either has or will need some help at some point.
The most valuable point that I can stress is this, before you root, find out how to undo it and how to fix or troubleshoot different senarios.
If you see the LG animation then this means you have any number of ways to fix the issue(you're not doomed), check the tutorials, do some reading and search its all here, you managed to find out how to root etc so now do a little more to find out how to fix, good luck.
Can you enter download mode?
Hello I have not been here long but anytime I need help with something pertaining to a phone I come here.
So here it goes. I got an LG G3. I got root then I installed Bump'd as it was released. I then installed a custom rom and all seemed to be good. A few weeks later my phone got stuck on TWRP custom recovery. I managed to get that fixed by finding a thread on this web site. Now I was going to install candy rom from the Sprint LG G3 section but as I wiped Cache and all that other good stuff what ended up happening is that it may have wiped something it should not have . Because now the phone will now only boot to TWRP, and it keeps informing me that "No OS is installed."
Now here's the tricky part. It doesn't seem to want to go into download mode either.
So all I can do it TWRP.
So I have two questions
1. I heard that you could possibly put some sort of file on an SD card and flash it on TWRP to fix it. Is this true ? If so, can someone direct me to how to do so with instructions?
and
2. If #1 does not work... does that mean that my phone is screwed and there is nothing I can do with it at this point ? I have soft bricked phones but never something like this.
Help anyone as I would like to get this fixed ASAP if there is some way to fix it.
Please and thank you!
So I got really cocky with my phone and thought I was a lot more tech savvy than I am... I rooted my LG G3 which went well, I changed a couple of settings in the build.prop to mess around with it, downloaded some mods, etc...
Then it all went down hill when I tried to flash a rom onto it that would get xposed working with Lolipop. The rom immediately bricked my phone, every time I boot it, factory reset, try pretty much anything it just shows a black screen with the words "[###] Fastboot Mode Started" on it. After reading countless forums I've found that I can flash the stock LG G3 D850 firmware onto the phone from the Download Mode/Firmware Update screen plugged into my PC to erase everyhing, but I can't even do that because I changed the model number in build.prop to the Galaxy s6 so a few apps had more up to date features. Now the phone wont accept the LG G3 stock firmware rom because it thinks its a Galaxy s6 but I can't change the build.prop back to D850 because I can't get into a bricked phone. Just wondering if ya'll had any suggestions.
Thanks guys and gals
Same Here. . Almost
So basically I have the same problem . . Well almost, so basically I had been messing with my build.prop and everything was going just fine the whole time through out. So after I was done modding pretty much, well I was testing out different settings I can input to change my Spring LS990 to work with the T-mobile carrier, including having to enter into a "secret menu" through the phone dial, but ended up bricking it. So after I was done therefore, I went and copy-paste the backup I made of the build.prop, straight into /system folder. After applying confirmations and letting it do it's job, I gave it a reboot for the copy to take effect and that's where I ran into the problem of having a boot loop on the LG logo screen and being able only to turn it off by removing the battery. Also I'm able to enter recovery, use ADB (kinda), but keep getting denied access/permission/privileges to use other functions in ADB except the "adb sideload" command, but even that results in mounting failure and signature+foot errors. Yes, I've been to numerous posts and forums, searching everywhere for info on my own repair and ended up here post this. Really appreciate your help, am willing to pay considerable amount for repair if extremely necessary and would also like to end up getting the phone to work with T-mobile if possible.
Thank you,
Blessings,
Dave.
So I've bricked my phone. And I can't make it work. Yesterday I finally had some time to thinker with the phone and decided to install Fulmics Rom 6.0. I had already downloaded it a while ago but first now had the time to install it. I made a post in the Fulmic's thread but with their new 6.5 fulmics just out, so my post got berried so quickly so I got no replies.
I started in TWRP with doing a backup, then a wipe and then started the install.
It seemed install was going fine, I even got the Fulmic's GUI midways and selected appropriate model, D855. I tried to keep things as vanilla as possible and chose to not uninstall anything and keep stock temperature throttle back.
But when the install completed I got one error: set_metadata_recursive: some changes failed
Phone wouldn't boot. I had however made a backup before I started and I was able to restore from backup from within TWRP.
Then phone booted and it seemed all was fine. But as I had my mind set on the Fulmics ROM I had one more go, just ti be sure I didn't mess up and chose something bad in the Fulmic install GUI. Also I did a wipe first, then I wiped the cache/dalvik as I once read that could make install easier. And result same as before. set_metadata_recursive: some changes failed.
Tried to reboot but I get flash screen with LG loge and powered by android on the bottom, and then when screen changes to only LG logo it gets stuck'd. No matter how long I wait, and I tried to wait for hours remembering wiping dalvik/cache makes boot take longer time. Stucked on the boot load. Notification light changes from green to blue. And the Lg logo is there.
Worst part is that now I can't even restore it to my backup from yesterday.
Here is my phone:
Lg G3 D855 16 GB 2 GB RAM
Android 6.0 stock LG update.
TWRP 3
Rooted
For now I would settle for a working phone. That is my main priority. Truth be told I got scared now and I don't know if I will take my chances putting a custom ROM onto the phone. After all my android 6 was working nicely, phone was rooted and adaway was working nicely. I guess I got greedy and wanted more
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
joppy said:
It would be very nice if people could take things very basic, like if I am to do certain things in TWRP don't assume I will understand unless you go into details. Been struggling for hours upon hours now and my mind is mush and concentration was lost a few hours ago. Yet I need to keep at it as I can't be without a working phone tomorrow. For instance in the TWRP under tab advanced > sideload what can I try there to make phone boot?
If I have left out any important for you to help pls just ask and I will reply as fast as possible. Any and all tips and pointers will be much obliged.
Click to expand...
Click to collapse
Downgrade to twrp 2.8 and flash again hope you are good too to go....
For me , if i have problem.
Replace sdcard , format data on twrp and flash .kdz (not after 30x.0426.kdz) , usually LGup can made download mode it self.
If can booting , make temporary root and get twrp.
Ok I had TWRP v2.8.7.0 laying around. I've used it before with success, so I know it works with my Lg G3.
But still not possible to boot.
I will try to read up on the .kdz as I never even heard of that before. Maybe if I am lucky that will save the day.
Hehe what do you know. TWRP v2.8.7.0 worked!
I dismissed it too fast, turned out it didn't get stuck'd on boot, boot just took a while because I had wiped everything.
Now I can see android is upgrading apps, and also when I think back to the first reboot with twrp v2.8 it was fulmics logo on the bottom part of the screen not android I guess my mind did not pay any attention as I was truly expecting to be stuck in boot loop this time too
Fingers crossed it is working now, I guess I didn't pay much attention when I tested twrp v2.8 and pointed to the fulmics ROM 6.0 and it seems it will work whoha
Finally I've got a working phone, and I also got Fulmics 6.0 as I sat out to get.
Don't know what went wrong or what caused the boot loop, but twrp v2.8 seemed to be the working solution.
IT seems everything works except I lost root. Which is fine for now, I will root another day.
Now I just need to use the dang phone
Deleted for your own safety
Btw, as the phone must be rooted to install custom ROM's it does seems strange that phone after installing Fulmics 6.0 appears to NOT have root, according to RootChecker. Could it be that the custom ROM is confusing RootChecker or did root somehow get revoked?
Is there a manual way I can check to see if phone is rooted? Cos there is, terminal
I took the chance tp get the latest KingRoot v4.9.6 over my previous v4.5.6. And run the APK.
Seems there must have been some issues with SuperSU, I had v2.54 and BETA v2.65. None of them kept root after install.
Found the latest stable that was superSU v2.78 and that fixed my issues.
TWRP ver 3.x messed my phone up too. Thought I had a good EFS backup, but when I needed to restore it, it didn't work. I will not be using ver 3.x again for a long time. Ended up losing my IMEI because of it.
I have a D855 with KitKat 4.4.2 (10h). It is rooted and (now) has the latest TWRP (3.3.1.0)
I have never updated from Kitkat because it runs perfectly rock solid. Until now.
I have noticed that a number of apps I use on Play Store can no longer be updated. I think they have stopped supporting KitKat, so I must upgrade to the latest version of Android, to make sure my beloved G3 lives a little longer.
I have updated TWRP to the latest version from the TWRP website. Which was surprisingly hard to achieve, as I was unable to get into Fastboot or Download modes. After several tries, the TWRP app finally flashed successfully.
Also, I finally got the G3 into Download mode (although I had to hold down the power button for about 30 seconds to get back out of Download mode, after disconnecting the USB cable).
I now need to flash a new rooted MM custom ROM, but I seem to remember the partitions changed from KK to LP/MM.
So before jumping and in, and potentially bricking the G3, I just wanted to ask if any one could offer me some advice on upgrading from Kitkat to MM. To ensure I am successful.
Looking at the old threads, people usually did this back in 2017, and things are a little different two years later, so I thought that it would be worth asking the question now, in case there are newer/different options to consider.
I would appreciate some advice. Thanks.
Many thanks for those who had a look at my question.
I was hoping for some advice on RPM/TZ partitions etc. , Modems, Bump! etc but I guess it was naive to expect the forum for a 5 year old phone to be active.
For my part, a good phone is a good phone. And the LG G3 was a good phone.
I came from a Sony Z1 which was a great daily driver, slightly workman-like but rock solid with good vanilla-style OS.
Moving to the G3,the build quality wasn't quite up to Sony's standards but I suddenly discovered how good audio on a phone could be. The screen was great, the OS was rock solid, which is why I stayed on Kitkat for so long. Also, the G3's removable battery allowed me to use a Mugen 6000mah battery, which has provided amazing battery life.
FYI, I considered going back to a Sony but the G3 was so good, I bought a G5. Which is a decision I have always regretted.
The G5 OS was good, like the G3. The bootloader could be unlocked. The audio and screen were as good as the G3. But the hardware was only mostly good. The phone overheats all the time and successive ROM updates have never resolved this issue. Also, battery life is beyond poor, possibly the worst I have ever experienced with a mobile phone.
If I brick my G3, I think I will replace it with a Sony.
I am going to go ahead and flash an MM ROM, Fulmics or CleanROM. I have a Kitkat bootloader so hopefully that will help (now that Autorec has been removed from Playstore).
I will post how things go.
Safest way to do it:
1. Upgrade to LP from KDZ. Root the phone, install TWRP and flash some MM (or newer) ROM.
2. Upgrade to MM (30b or 30f) from KDZ. Root the phone with king root, install twrp and flash some MM (or newer) ROM.
Thanks for the advice, MESA.
Unfortunately, I have already flashed the latest Fulmics for d855.
Did a clean flash. Appears to be working with no issues.
Upgrading does appear to have resolved the various app issues I was having. Looks like some big companies/organisations are no longer supporting KitKat.
But, now, I have no idea which RADIO/MODEM, RPM, TZ or CUST I now have installed. Also, I do not know whether the kernel is set to permissive.
If you have any advice on anything I should do now, please let me know.