Related
Just plugged the Gpad in to charge and this popped up. Hoping it's 5.0.
It's just sitting on 0% for the longest time.
I will update the status when I have something to report.
#fingerscrossed
-----------------------------
Updated on post:
Nothing. False alarm. I don't know how or why my tablet ended up on the update recovery screen because it was already powered on when I plugged it in, but no update.
That mode is only to update via lgflashtools....
My cousin's v410 is dead and I plugged it in to a USB wall charger. Some conductive trash must have been in the plug, I guess, because it rebooted to firmware update mode on me, instantly and from any state. If you see this mode unplug your tablet, hold down power to restart, and try a different cord or blow/clean the trash out of the plug.
Update to Lollipop lg G pad 7.0 lte v410 AT&T if you got a root issue
I had rooted my lg G pad and could not update to lollipop update this is how I got it to work. I removed the SD card and Sim card then I unrooted the tablet and restarted it. I also performed a hard reset from the settings menu. Make sure you unselected the data backup and automatic restore before resetting, now reset tablet. When it restarts just log into the WiFi and nothing else. Now go to settings and go to update center to find the firmware update download it and install it.
jlvvela84 said:
I had rooted my lg G pad and could not update to lollipop update this is how I got it to work. I removed the SD card and Sim card then I unrooted the tablet and restarted it. I also performed a hard reset from the settings menu. Make sure you unselected the data backup and automatic restore before resetting, now reset tablet. When it restarts just log into the WiFi and nothing else. Now go to settings and go to update center to find the firmware update download it and install it.
Click to expand...
Click to collapse
I'm too waiting for the same update, did you get any new link for that, mine is on 4.4.2 v41010d
No the update I got it through the settings menu on the tablet go to about tablet and then to check for updates that's how I got it.
Does anyone have any KDZ files?
I had a corrupted Stock ROM on a G Tab 7 Tablet due to applications that were installed by the previous owner; no matter what I did, Addware apps would always install on there own; I mean, even after restoring factory settings via the settings, or via the hardware combinations keys to reset to factory settings, It would reset the device but it would still install all the annoying apps as if they were Factory installed; weird, I had never seen something like this in any device I've worked on.
Anyways, since Factory Reset wouldn't help I had to Flash the Tablet.
I found the V41007h_0.kdz file which I was able to flash using the the LG Flash tool.
But now there is a a watermark in red "userdebug 4.20.17(42001700)" in the Home Screen.
So I'm hoping at the very least I can find a KDZ file to go back to the firmware version that the Tablet had which was V41010d.
Does anyone have any links to point me in the right direction?
If you can't post it in public, please Private message the links.
Thanks in advance for your help.
RaudelJr said:
Does anyone have any KDZ files?
I had a corrupted Stock ROM on a G Tab 7 Tablet due to applications that were installed by the previous owner; no matter what I did, Addware apps would always install on there own; I mean, even after restoring factory settings via the settings, or via the hardware combinations keys to reset to factory settings, It would reset the device but it would still install all the annoying apps as if they were Factory installed; weird, I had never seen something like this in any device I've worked on.
Anyways, since Factory Reset wouldn't help I had to Flash the Tablet.
I found the V41007h_0.kdz file which I was able to flash using the the LG Flash tool.
But now there is a a watermark in red "userdebug 4.20.17(42001700)" in the Home Screen.
So I'm hoping at the very least I can find a KDZ file to go back to the firmware version that the Tablet had which was V41010d.
Does anyone have any links to point me in the right direction?
If you can't post it in public, please Private message the links.
Thanks in advance for your help.
Click to expand...
Click to collapse
You've flashed a KDZ that contained a test build. If you follow the steps in my thread here http://forum.xda-developers.com/g-pad-10/general/tutorial-lg-gpad-v410-5-1-to-4-4-t3232150 then you can recover the lost space of your internal SD card and run custom ROMs. Unfortunately I don't think there is currently a way to go back to stock 5.0.2 from this point. If there is, it has not been documented in this form (to my knowledge).
Please post in my thread if you need help with that process.
jlvvela84 said:
No the update I got it through the settings menu on the tablet go to about tablet and then to check for updates that's how I got it.
Click to expand...
Click to collapse
I could not get it through SIM card because i don't have an AT&T SIM neither i live in the US nor AT&T has any services nearby, so i definitely need a zip file that might be an OTA or something that can be installed via ADB or system recovery. please share somethings for me.
Update LG Gpad 7.0
talvigi said:
I'm too waiting for the same update, did you get any new link for that, mine is on 4.4.2 v41010d
Click to expand...
Click to collapse
I was trying to update my GPad 7.0 to 5.0.2 or 5.1.0 from 4.4.2 and no OTA updates no matter what I do.
I'm on Android 4.4.2 with software version v41010d. Hardware says LG-V410 in "about tablet" section.
What's the quickest easiest way. I'm concerned that this is an older tablet and isn't updateable or has some update problems so that is the reason for my question. Maybe I'll keep it on 4.4.2 but wanted to run latest Kodi which won't work with anything but 5.0 or greater.
cejack said:
I was trying to update my GPad 7.0 to 5.0.2 or 5.1.0 from 4.4.2 and no OTA updates no matter what I do.
I'm on Android 4.4.2 with software version v41010d. Hardware says LG-V410 in "about tablet" section.
What's the quickest easiest way. I'm concerned that this is an older tablet and isn't updateable or has some update problems so that is the reason for my question. Maybe I'll keep it on 4.4.2 but wanted to run latest Kodi which won't work with anything but 5.0 or greater.
Click to expand...
Click to collapse
I never saw the OTA captured or a 5.X stock rom posted here, sorry. AT&T is notorious for blocking the release of firmware packages for their branded devices, so you won't find a V410 kdz from LG support either. If you can't get the System Update to work from the Settings menu, you might be stuck as far as stock goes. There wasn't much interest in updating stock in the community here because stock 5.0 patched the vulnerability that let us sign our own boot images. That effectively blocked TWRP and custom roms since the bootloader can't be unlocked. You could try the old take your sim out, reboot and check for the update trick. Some people say that doesn't work, and others swear by it.
There are plenty of 5.X and higher custom rom options, if you want to update the system that way. Tesla, Tipsy, and Validus were all 5.1 roms and they're still on androidfilehost.com. LOS and Candy have been updated up to 7.1. I keep Tesla on my V410 and it works great. All the custom roms rely on being on the 4.4 stock bootloader and radios since the kitkat bootloader was the only one vulnerable to the Bump exploit, so you're in a good place to start from.
jason2678 said:
I never saw the OTA captured or a 5.X stock rom posted here, sorry. AT&T is notorious for blocking the release of firmware packages for their branded devices, so you won't find a V410 kdz from LG support either. If you can't get the System Update to work from the Settings menu, you might be stuck as far as stock goes. There wasn't much interest in updating stock in the community here because stock 5.0 patched the vulnerability that let us sign our own boot images. That effectively blocked TWRP and custom roms since the bootloader can't be unlocked. You could try the old take your sim out, reboot and check for the update trick. Some people say that doesn't work, and others swear by it.
There are plenty of 5.X and higher custom rom options, if you want to update the system that way. Tesla, Tipsy, and Validus were all 5.1 roms and they're still on androidfilehost.com. LOS and Candy have been updated up to 7.1. I keep Tesla on my V410 and it works great. All the custom roms rely on being on the 4.4 stock bootloader and radios since the kitkat bootloader was the only one vulnerable to the Bump exploit, so you're in a good place to start from.
Click to expand...
Click to collapse
I find it strange that there isn't a separate device category on XDA for GPad 7.0. I guess there must be a reason - but it's probably too geeked out for a common humanoid like me to understand.
cejack said:
I find it strange that there isn't a separate device category on XDA for GPad 7.0. I guess there must be a reason - but it's probably too geeked out for a common humanoid like me to understand.
Click to expand...
Click to collapse
You aren't the first person to wonder about that. We requested a different forum for the V400/410 early on and it never happened. I don't know why. It does get confusing. You'll find the V400, V410, V480, V700 and probably a few more devices discussed here. A large majority of the development is for the V400/410, though.
Fastboot loop problem. pls help me.
Hi Dear Friends ( sorry my bad eng.)
I will tell you what I do.
1. My Device V410 AT&T version v41010b
2. İ setup my computer lg drivers & lg flash tool & lg one root and V41007h_0.kdz
3. i used one click root and successful.
4. i did my tablet download mode ( volume + and plug usb cable )
5. Start lg flash tool / select v41007h_0.kdz / and click CSE Flash button ( CDMA & DİAG )
6. Start Korean and Engilsh
7. Process pc screen %7 and tablet screen %6. and froze. i go to sleep early morning after 6 hours later. ı look process remain the same.
8. ı closed tablet unplug usb cable.
9. open tablet but only fastboot screen. ı try restart button after fastboot screen / i try restart bootloader select but only black screen.
10. power of and try open only fastboot screen.
what do I have to do now ? Please Help me.
Trane46 said:
Hi Dear Friends ( sorry my bad eng.)
I will tell you what I do.
1. My Device V410 AT&T version v41010b
2. İ setup my computer lg drivers & lg flash tool & lg one root and V41007h_0.kdz
3. i used one click root and successful.
4. i did my tablet download mode ( volume + and plug usb cable )
5. Start lg flash tool / select v41007h_0.kdz / and click CSE Flash button ( CDMA & DİAG )
6. Start Korean and Engilsh
7. Process pc screen %7 and tablet screen %6. and froze. i go to sleep early morning after 6 hours later. ı look process remain the same.
8. ı closed tablet unplug usb cable.
9. open tablet but only fastboot screen. ı try restart button after fastboot screen / i try restart bootloader select but only black screen.
10. power of and try open only fastboot screen.
what do I have to do now ? Please Help me.
Click to expand...
Click to collapse
Download twrp for the V410 to a computer, then connect the tablet to the computer and try using this command with fastboot:
Code:
fastboot boot twrp.img
That should boot you into TWRP without actually flashing it. If it works, from there you should be able to try to wipe and flash some roms. Sorry, but I'm not convinced it will work in the state your tablet is in. If your device is falling back to fastboot, your laf partition is blank or damaged and very possibly some other partitions are missing or damaged too, and that might prevent TWRP or roms from working right.
If that fails, you can use fastboot to restore the laf partition and hope that brings back download mode so you can try the kdz again:
Code:
fastboot flash laf laf.img
I've restored my laf this way; I actually intentionally nuked laf to enable fastboot. I can provide laf.img if you decide to try this.
Hi,
I've a big problem with my ZenFone GPS, it's very slow to fix and accuracy is very bad. It's totally unusable for car navigation. For example my moto G first gen 2013 have better accuracy (11 meters) and fix in 5s max versus 30/40s with bad accuracy (40meters).
I've try to upgrade to latest firmware, factory reset my phone but problem still here.
I google a little about my problem and I found i'm not alone to have this GPS issues.
Does someone found something to fix this problem ?
Math43 said:
Hi,
I've a big problem with my ZenFone GPS, it's very slow to fix and accuracy is very bad. It's totally unusable for car navigation. For example my moto G first gen 2013 have better accuracy (11 meters) and fix in 5s max versus 30/40s with bad accuracy (40meters).
I've try to upgrade to latest firmware, factory reset my phone but problem still here.
I google a little about my problem and I found i'm not alone to have this GPS issues.
Does someone found something to fix this problem ?
Click to expand...
Click to collapse
You're not the only one with this problem, bro. I also have a problem with GPS on my ZE500KL (by the way, i also had Moto G 2013 before and GPS works good on it)
AndroiTS GPS Test shows that GPS doesn't see any sattelites. The best result was connection with 2 sattelites, and the accuracy of GPS on Google Maps was very low in anyway.
I have tried factory reset, to downgrade to WW_12.8.5.118 Firmware & wipe cache partition, then tried also install WW_12.8.5.172 and WW_12.8.5.222 firmware and the result is the same - GPS not working.
The only thing I didn't tried yet is editing the "gps.conf" file, but I need root for this, and I don't want to lose the warranty
As I see on ASUS official forum, they know about the issue and they trying to resolve the problem (since november or something). :good:
Same for me
Gps position updates once a minute and accuracy is real ****. Had a road accident because of navigation problems
same problem for me...good phone, but GPS work badly
gps on my ze550kl keeps turning around and accuracy is very bad hope they will fix that in MM
I tried to post this message on the Asus Zentalk forum, but the site seems broken, it won't let me post anything.
I had a similar problem with my Moto G, I resolved this way (solution found in this forum, posted back to CM forum):
To make integrated GPS working you need to reboot in bootloader mode (hold volume down while turning on the phone), then attach the phone to the pc with the USB cable, and from the command prompt use fastboot to erase modemst1 and 2:
Code:
fastboot erase modemst1
fastboot erase modemst2
It will not erase anything tangible for the user (apparently).
Click to expand...
Click to collapse
I know that this is a different phone (I should get it soon btw, I hope I will not regret my choice) and that the commands probably won't work even with some modification, but it could give a hint to those trying to solve this problem.
BubuXP said:
I tried to post this message on the Asus Zentalk forum, but the site seems broken, it won't let me post anything.
I had a similar problem with my Moto G, I resolved this way (solution found in this forum, posted back to CM forum):
I know that this is a different phone (I should get it soon btw, I hope I will not regret my choice) and that the commands probably won't work even with some modification, but it could give a hint to those trying to solve this problem.
Click to expand...
Click to collapse
i tried the code but her is what happened... see screenshot
postimg.org/image/jxx5n1sxl
hoping for a response...
rozene05 said:
i tried the code but her is what happened... see screenshot
postimg.org/image/jxx5n1sxl
hoping for a response...
Click to expand...
Click to collapse
Have you run the command prompt as Administrator?
Have you installed the latest or official ADB drivers?
Have you unlocked the bootloader? (I don't know if necessary, try the above first)
I also tried running as admin as well as downloaded the latest adb and drivers, same result
I have not yet unlocked my bootloader since there is no complete backup here at xda, and it is not possible to re lock the bootloader,
I will just be waiting if someone will try to it.
rozene05 said:
I also tried running as admin as well as downloaded the latest adb and drivers, same result
I have not yet unlocked my bootloader since there is no complete backup here at xda, and it is not possible to re lock the bootloader,
I will just be waiting if someone will try to it.
Click to expand...
Click to collapse
I'm investigating what happens in detail when these two partitions are erased.
I found two discussions that look interesting (specially the second):
http://forum.xda-developers.com/zenfone2/general/investigation-efs-t3153154
http://forum.xda-developers.com/showthread.php?t=2617276
In brief: these two partitions holds important information of the phone, like the IMEI. Erasing them cause the system to recreate them using the information backed-up in other partitions. But in some cases these backup partitions are empty and erasing the modemst partitions cause the phone radio to stop working (no more calls, 2G/3G/4G data and GPS) because the system cannot retrieve the serial numbers needed to make the radio work anywhere.
So it's better to do a manual backup of these partitions before erasing them (better a full backup with TWRP, that will backup all partitions including these).
Reading the second discussion linked above suggests me that the sudden bootloop problems that people are experiencing, are also connected to the corruption of these modemst partitions (corruption possibly caused by some firmware update or by some system app gone mad).
The fact that Asus after 2+ months still hasn't fixed the GPS problem, could mean IMO:
- that the problem isn't related to the above partitions and is more complicated than it seems (probable);
- that the problem is caused by the corruption of the partitions but it cannot be fixed with an OTA firmware update, but only manually with a technical intervention (full flash and/or terminal bashing) that regular users aren't capable of;
- that the problem can be fixed with a firmware update but Asus developers still haven't find that (improbable).
I should get the ZE500KL in a couple of days, then my theory could be tested directly and described in detail (if I get the same GPS problems after updates).
Thanks for your input regarding this, i would just use my bluetooth gps in order to navigate properly..
rozene05 said:
Thanks for your input regarding this, i would just use my bluetooth gps in order to navigate properly..
Click to expand...
Click to collapse
Yesterday I received the phone, I booted it to check if it works, then I immediately upgraded the firmware to the latest version, without OTA updates but downloading directly the latest full firmware from the Asus download site.
Then I booted the phone, played a little with it, did a full reset and re-flash the firmware.
Then I thought about GPS problems and I tested it with AndoiTS GPS Test and it seems to work fine, or at least I suppose this from the attached screenshot (I couldn't test it on the streets yet).
I don't have root permission or bootloader unlocked [yet], so you and everybody could try the same things I did:
- Factory data reset (from Settings > Backup and reset menu);
- wipe data/factory reset (boot into recovery by pressing Volume Down button while turning on the phone);
- full firmware flash (from recovery, you can copy the firmware zip file in a microSD or upload it via adb sideload).
Then after rebooting the phone complete the welcome procedure and repeat the three steps above another time.
I hope this will works for everybody.
Here is my screen shot using asus zenfone 2
Screenshot from asus zenfone 2 ze500kl
Merely 2 satellites
And here is the screenshot using xperia sp c5303,
I also updated using the zip in asus site and flashed it,
Btw, my asus has been rooted, but i see no difference after rooting it, same scenario 2 or less satellites, some times 5 but no fix
BubuXP said:
Yesterday I received the phone, I booted it to check if it works, then I immediately upgraded the firmware to the latest version, without OTA updates but downloading directly the latest full firmware from the Asus download site.
Then I booted the phone, played a little with it, did a full reset and re-flash the firmware.
Then I thought about GPS problems and I tested it with AndoiTS GPS Test and it seems to work fine, or at least I suppose this from the attached screenshot (I couldn't test it on the streets yet).
I don't have root permission or bootloader unlocked [yet], so you and everybody could try the same things I did:
- Factory data reset (from Settings > Backup and reset menu);
- wipe data/factory reset (boot into recovery by pressing Volume Down button while turning on the phone);
- full firmware flash (from recovery, you can copy the firmware zip file in a microSD or upload it via adb sideload).
Then after rebooting the phone complete the welcome procedure and repeat the three steps above another time.
I hope this will works for everybody.
Click to expand...
Click to collapse
Another question what firmware version are you using, as far as my experience, the latest ww.12.8.5.222 firmware gives me this problem so i decided to do a full downgrade to the stock fw that comes with my phone, which is ww.12.8.5.118, for that fw works before
rozene05 said:
Another question what firmware version are you using, as far as my experience, the latest ww.12.8.5.222 firmware gives me this problem so i decided to do a full downgrade to the stock fw that comes with my phone, which is ww.12.8.5.118, for that fw works before
Click to expand...
Click to collapse
I used the latest firmware, the .222
The trick could be resetting and flashing, two times, but it's only an assumption.
BTW, into geolocation settings, I enabled the only GPS option when doing the test.
In your screenshot, it looks like AGPS is enabled, that is not GPS. Try setting only GPS in the geolocation settings and see what happens (maybe with screenshot).
Here it is without agps, i even left my phone in the open for about an hour, screen on, hoping it will fix even with one satellite, now even one satellite wont show up
rozene05 said:
Here it is without agps, i even left my phone in the open for about an hour, screen on, hoping it will fix even with one satellite, now even one satellite wont show upView attachment 3688327
Click to expand...
Click to collapse
Ok, it looks like the same exact problem as the Moto G, and the solution should be the same too.
But with the bootloader locked (and no way to unlock it at the moment), the only thing we can do is using the terminal with root privileges to backup and erase the partitions (with the dd command or something similar).
I'll study how to do this...
Just to update
rozene05 said:
Just to update
View attachment 3689322
Click to expand...
Click to collapse
so what did you do to solve it?
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Wellfare11 said:
I have had a moto g6 plus for some time now, but nowadays I am not able to detect SIM cards and wifi does not turn on, what is happening?
Click to expand...
Click to collapse
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
weazie said:
Can you tell us more?
How did it start?
Did something happen to it, or did you just notice it is not connecting?
The most easy things first, is your sim card correctly in place?
Which ROM are you on and have you reflashed it?
Click to expand...
Click to collapse
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Wellfare11 said:
The phone started with problems since I upgraded to Android Pie, I have taken care of it very well but I do not know if it is a hardware failure, but note that in baseband turns out to be unknown, I installed several stock roms from fastboot without any success, also I thought it would be a problem of the EFS partition, but everything is fine I even took a backup in case the doubts, what could happen?
Click to expand...
Click to collapse
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
weazie said:
Did you originally update via OTA, meaning, was it the official update?
Then when you noticed it's not working, you tried to flash several stock ROMs?
One possible problem that comes to mind, is that for some reason, you have the wrong radio/modem firmware. That can happen for example, if you have flashed a ROM, which is not meant for your region.
Click to expand...
Click to collapse
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Wellfare11 said:
Yes, upgrade to Android pie via OTA
I already put a stock rom of the same region, following each fastboot command one by one, but everything continues the same, I even installed RROS 7, to see if at least it turned on the wifi, and it is in bootloop.
Click to expand...
Click to collapse
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I already tried, I installed the rom corresponding to the model of the cell phone and the wifi still does not work, the base band is still unknown, I also checked if the sim card was correctly placed, and everything is fine
weazie said:
Go with the modding guide index: how to restore stock ROM etc., and flash a stock ROM that you know will work. Flash the radio/modem file too, and make sure it's the correct one.
Just to say, I had connection problems too, and in the end they were because the sim card did not latch correctly in place i.e. was not correctly in place.
Click to expand...
Click to collapse
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Wellfare11 said:
I have an idea, but I need someone to help with a backup of the files, Radio, Modem, and Persist to flash in twrp
Click to expand...
Click to collapse
Great that you have an idea. ?
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea. ?
weazie said:
Great that you have an idea.
Here's an idea: take a backup of your current config in twrp, move it to the computer, take a copy. Replace the files in that copy with the ones that you want to flash.
Did you mean this? You are aware that you can try different radio/modem files through fastboot, not having to flash everything else every time? That said, go with your idea.
Click to expand...
Click to collapse
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Wellfare11 said:
I already tried and still does not give results curiously I have noticed that even in bootloader shows, Baseband not fund
Click to expand...
Click to collapse
Does the phone ask for a pin code at any point?
weazie said:
Does the phone ask for a pin code at any point?
Click to expand...
Click to collapse
does not request any code at any time
Wellfare11 said:
does not request any code at any time
Click to expand...
Click to collapse
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. ?*
weazie said:
Ok, but WiFi should work even if there is no mobile data available.
I probably can't help at this point, apologies! My suggestion is to flash a stock ROM, lock the bootloader and send the phone for repairs. There could be a solution to this, but I'm out of ideas. *
Click to expand...
Click to collapse
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Wellfare11 said:
from what I see, if there is no baseband it does not detect the sim card and it does not turn on the wifi, I will try to force an OTA retail update
it did not work
Click to expand...
Click to collapse
Hello, colud you solve the problem? Because I am havig a very similar one...
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
I have the exact same problem, I wasn't able to repair it so I sent it to service and tomorrow they will try to fix it for $35. The problem with goign back to previous versions is that you loose the IMEI and MAC . The problem with the pie version I believe is the baseband. If the service is able to fix it I will post the solution here for you to fix it .
bitstuff said:
I have a similar issue after flashing the latest firmware. SIM goes to "SIM locked" every ten seconds or so, and Wifi drops at the same tie. It's like networking is being reset every 10 seconds. No network settings I've tried change that.
I've flashed several stock ROMs; the one I had previously, newest, oldest, both for RETEU and retail. I used Lenovo restore to upgrade but that resulted in soft brick, after that I flashed the latest firmware via Fastboot and that's when the problem started.
With Oreo, wifi and cellular don't work at all, nothing detected. With Pie they're connected and dropped in a loop. I can't help thinking that the Lenovo restore broke this somehow, but modem files have been reflashed several times after that with no change. I'm not getting the baseband error.
Click to expand...
Click to collapse
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
caradobeco said:
Hello group friends, I'm new here. I have a similar problem, I was using the Havoc 2.4 rom, when upgrading to 2.6 I no longer recognize my SIM card and the wi-fi does not connect, I can not install another rom anymore, nor rom stock, recovery TRWP has been replaced by the Havoc and the Wipe System function does not work, and for a few days you can not stay in recovery mode anymore, it restarts every 3 seconds, not the time to click the options. Can someone help me. I'm without a cell phone, and I need it.
Click to expand...
Click to collapse
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
juampapo546 said:
Service couldn't fix it. Being honest they were quite incompetent, when I explained the problem he said "we should hire you" ( I am 16 years old) . Anyway, could you fix it? Because I am not even close
---------- Post added at 03:00 AM ---------- Previous post was at 02:54 AM ----------
Sorry I answer so late, I didn's see the message before.
I believe you already tried puting it into bootloader mode. If that's the case, I had a similar problem recently an it solved alone, I let it loop for a while and suddenly fell, into dtock recovey, i factory reset (with stock recovery) and somehow stock was booted ( i believe it was because it was in inactive slot).
Hope this helps you
Click to expand...
Click to collapse
I am still working on this, I actually did this to a work phone (I had permission to root/unroot). Something that has helped me so far is just getting familiar with the whole flashing process - https://android.gadgethacks.com/how...actory-images-android-using-fastboot-0175277/. I think from this article the problem lies in the modem/radio rom. That *should* be the only thing you need to flash on. However, I have noticed with a lot of roms on here, a modem rom is not included on the stock firmware. But that needs to match well to your phone from what I understand. I have tried a few modem roms already, unfortunately, but no luck.
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
I was going to follow the instructions in this post and install the F800K10e.kdz but the lg-firmwares.com website is limiting me to 2 files per 24h so I decided to give the H91510e_00_VTR_CA_OP_1205.kdz another go. It wouldn't boot again until I formatted the data, it seems to be working so far.
I'm sure this is some noobie knowledge but most posts/guides didn't say to do that and I am indeed a beginner. I will update this thread with information on what I do next if relevant and if I can get my mobile data working somehow.
Edit : SMS work, 4G works but the sim card crashes when I call or get called.
Unfortunately I didn't even try my sim card when I got the phone so maybe it was the same onthe H91010l. Looks like I'll have to redo the unlocking procedure and continue fixing this mess.
Edit 2 : Notifications don't work properly either like on the custom roms... For example skype messages.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Darnrain1 said:
If you did not make a dump backup there is not much you can do that I know of. You can try and delete the modemst1 and modemst2 and see if that fixes your no signal issue.
hold vol down plug phone into computer USB cable.
fastboot erase modemst1
fastboot erase modemst2
fastboot reboot
restart phone into os see if that fixes the issue.
If so make a backup of you EFS in twrp and save it.
Your EFS got corrupted when you flashed the stock KDZ to root the H910 happen to me also. This would explain why your phone is crashing and no signal.
Click to expand...
Click to collapse
I didn't flash any kdz to root initially. I just started flashing stuff once I lost my bootloader and TWRP. I managed to have the H91510e working that's where I'm at currently as per the second post. I will try and root it again following this procedure soon. I have to look into why I can't call or get called first. We'll see what happens, but according to this thread I will lose mobile network when I root the H915 version. I'll see when I get there.
Xanvast said:
Hi, I have to say I didn't expect that this would be such a ride when I got into this. I am now simply trying to have a working phone again.
I will briefly sum up what I've done so far :
So I got a brand new V20 a few weeks ago with the intention to root it and install a custom rom. It came as a H91010l with a security patch from dec 2016.
I got everything ready it took a while but then went ahead and followed this guide [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151
A few minor hicups on the way but I got the bootloader unlocked, twrp installed and then LOS 18.1. I thought everything would be fine and I didn't make a backup... It worked well except that I had no mobile data (French carrier SFR), only sms worked and also some notification issues.
After a break and looking for solutions I tried another OS tonight (/e/) and the same issues were present. No mobile network.
It's not to do with the APN (which I made sure was configured properly) but likely some incompatibility after tweaking the system with the root procedure. Maybe something to do with US996 files being used.
So I decide that I needed to go back to stock since I wouldn't find a solution from there and I did a wipe before flashing a stock US996 firmware in TWRP taken in this thread, the US99610f - SPL 2016-12-01
Result : I lost the fast boot and TWRP, the phone is stuck on the LG logo.
Only one thing works at this point, firmware update download mode, so I did a full partition dl flash of the following H91510e_00_VTR_CA_OP_1205 kdz which according to many posts should be fine. Nope, it doesn't boot it's stuck on the LG logo.
I have tried a second one that is old, US99610f_00_1205 kdz which should work too. It boots and I get into setup but it reboots within a minute/30s on top of being really slow.
So what I'm looking for right now is a solution to go back to stock. I have no backup and no root. I can only use LGUP. And it seems that my model is pretty non cooperative. What can I do ?
Thank you.
Click to expand...
Click to collapse
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Darnrain1 said:
I know what's wrong. You cant use lineageos to make calls on AT&T network. You can get internet but no VoLTE. So your going to have to use a deblaoted Stock Oreo rom if you want a rooted phone with phone calls.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
Click to expand...
Click to collapse
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Edit : I just installed the h91010r with having wiped + formatted before and formatted after, it still goes into secure boot...
Xanvast said:
Thanks for your reply. I am using SFR, a French carrier. Is it the same issue ?
There has been developments since my last post. I started from the H91510e like I said and followed the [ROOT] HOWTO: AT&T H910 up to v20g (FULLY TESTED) guide by runningnak3d supported by a video from NewTechBegins. It went well until the flashing from TWRP.
I think it was my mistake to do like the video and flash h910-10r.rar followed by Magisk-v19.0. This resulted in not being able to boot, I kept getting the secure boot with password even after formatting. And after a couple of times it turned into a green screen crash. I couldn't get to recovery either for some reason even though I'm sure it was still there. The corruption warning message would appear almost instantly at boot and not allow me to do the volume down + power shortcut, and fastboot reboot recovery would not work either.
Reflashing the H91510e with LGUP worked but the system was particularly slow at first, it seemed to do better after a few minutes. Going over everything again, the part where we boot into recovery for the first time ended up the same with a green screen crash.
What seems to have solved it is to flash boot1.img from the root package in this [LS997|VS995|H910|F800L] DirtySanta Bootloader unlock and Root guide by me2151, which is different from the boot without extension of the other guide. I also reflashed the recovery several times, it didn't change anything until this.
I will continue updating this thread with the results of what follows next. I just have to install the h91010r now and manage to get to setup.
Click to expand...
Click to collapse
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Darnrain1 said:
I would flash Auto_Debloat you get Oreo Debloat rom.
Custom Stock Oreo Rom Debloated & DeGoogled for the H910 & Most Lgv20 phones. VoLTE and WiFi-Calling working.
But to answer your question a lot of cell carriers are going to VoLTE only and LOS does not have that on the H910.
I made Auto_Debloat so if you need help just let me know.
Click to expand...
Click to collapse
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Xanvast said:
I added an edit at the bottom of my post, it displays the warning really quick and goes into secure boot everytime. Could it be that the h910-10r.rar package you shared at the end of the thread is not identical to the original post ? It simply won't boot into setup for me. Any ideas ?
I will try installing something quick tonight to have a working system with recovery I'm done messing around for the day. I will look into your custom rom in the coming days thanks for your help !
Click to expand...
Click to collapse
Yes your data partition is encrypted still. You need to format it in twrp.
Darnrain1 said:
Yes your data partition is encrypted still. You need to format it in twrp.
Click to expand...
Click to collapse
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Darnrain1 said:
Yes you need a kernel. Your still running stock kernel that's why your getting the green screen.
Click to expand...
Click to collapse
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Xanvast said:
That's the thing, it still goes into secure boot after formatting it.
So I flashed the boot1 again and twrp to be safe, it now doesn't display the warning anymore but goes into the green screen crash after a minute or so.
I'm now back to twrp, I'll just wipe everything and install LOS to try. If at least it has mobile data that would be more than before.
Click to expand...
Click to collapse
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Darnrain1 said:
It's complicated,
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Xanvast said:
That's the first thing I've done, I entered the APN settings from this page (3), and the results reported are from after. So do you know about other OS like /e/, any that would not behave the same ? Or anything I can flash on top to fix it ?
Have a good evening.
Click to expand...
Click to collapse
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Darnrain1 said:
I am in the USA so it's in the afternoon for me.
You may want to try and flash you EFS from fastboot mode.
Manually reinstall your EFS on the Lgv20.
You need to find your Original DUMP of the rom your Lgv20 phone was on, before you downgraded your firmware for rooting.
Note: COM21 is what ever com port you were using at the time.
Reboot into fastboot mode
With the phone powered off hold the down vol and plug in usb to computer.
Info on what the files are
/fsg
A backup of your modemst1 and modemst2 files. So if you erase modemst1 and modemst2 /fsg should restore the partitions automatically. But if /fsg is corrupted then it will not restore them.
/misc
This partition contains miscellaneous system settings.
/modemst1 /modemst2
Modemst1 and modemst2 store information like IMEI.
fastboot flash fsg fsg_COM21
fastboot flash misc misc_COM21
fastboot flash modemst1 modemst1_COM21
fastboot flash modemst2 modemst2_COM21
fastboot reboot
Click to expand...
Click to collapse
Unfortunately as stated in my first post, I have no backup of the state of the phone when I got it as a H91010l. I didn't do one either while on the H91510e because I didn't see the point, it was already modified and calling didn't work.
Thank you for the explanation.
Something I'd like to mention for other readers is that there is one main visible difference between the first root (from H91010l with the old guide) and second one (H91510e with newer guide). The first time the warning message with the red triangle during boot was very distorted and duplicated. It was unreadable. Now it is clear. I don't know enough to say what was causing it or point at what made 4G work in the second case but this was something worth noting.
Alright, going into this de-Googling trip I did not know that many apps relied on Google Play Services to work and the Google cloud services, Firebase cloud etc... to send their notifications. I had no idea that Google was managing the notifications for most of the world and so much more. That only reinforces my desire to get away from it.
So these apps like Discord, Skype and others that don't send notifications it's directly because of the lack of Google Play Services. I noticed today that MicroG has a Cloud Messaging option but I will not enable it.
Signal works fine without any of it. I also found Skype Lite to send notifications so that's what I'll use from now on. Discord is going into the trash. I've read that Telegram is supposed to work too. So another problem solved. I have no issues making concessions on my convenience to be freer.
A website I came across which references how apps behave without Google : https://plexus.techlore.tech/
Darnrain1 said:
It's complicated,
Xanvast said:
Oh I see now, so it's indeed not the same package. That is why you had to flash H910_BTTF-mk2000.zip
Thanks for your time and patience.
I installed LOS 18.1 and it works fine with 4G this time (before reading your reply). Unsurprisingly calls in and out make the phone kernel crash with a black screen. I really like LOS and android 11, is there something I can do to make calls work ? Like flashing another kernel ? Does /e/OS have the same issue ?
If not I can absolutely live without calls for the moment, no problem.
Edit : I'm not getting notified of messages for Discord/Skype and not getting the call if the app is not open actively. Seems like it's not running the services in the background.
Click to expand...
Click to collapse
Yep your welcome, no problem. You may just need to setup LOS with your network provider. Do a google search for APN carrier settings for your cell provider. Take care.
Click to expand...
Click to collapse
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Xanvast said:
I took photos of my Kernel crashes, now it doesn't just happen with calls, which I could live with but also while using Skype Lite and looking out of the app for example, when I'm doing something taxing for the device or sometimes the phone would just reboot. Several times a day.
It seems to be very similar to what is mentioned in this post. Do you or anybody think that I should do the same and flash h915freedommobilemodem.img ? How do I go about it if so ? Is that something you do in fastboot ?
Also what are the risks if it goes bad ? I'm tired of dealing with repairing the mess and I'd like to avoid more problems.
Thanks.
Click to expand...
Click to collapse
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Darnrain1 said:
If I am not mistaken your running LineageOS. I would ask in that post for help. I run Stock Oreo on my H910 because everything works.
[OFFICIAL] LineageOS 18.1 for the LG V20
Click to expand...
Click to collapse
Yes the post is in that thread. I didn't have this problem the first time I used LOS 3 weeks ago so I assume it has to do with the green screen crash caused by the kernel I didn't flash after the h910-10r.rar. So it's still unaddressed in my opinion. Should I go ahead and flash that missing kernel or the H915 modem ? I don't know what's the difference and both seem plausible.
It's fine if you aren't sure and I will end up asking there.
Hi.
First of all, I want to let you know I'm just new to this page, so I'm so sorry if I make any mistakes within creating the post.
As you've read in the title, I can't fix the OS of this phone. I bought it used, and apparently it didn't have any OS (I thought it was because there was a flashing attempt, which went wrong). One day, I just looked for Android 9 and I installed it. The phone started working, and so I started using it. There were some problems with the phone though. First of all, at random moments, it started lagging and just re-starting. The other problem I had was the bootloader message, saying that I didn't have an official OS.
Today, I tried to uninstall all of /system. I read a lot of information, I watched a lot of videos and I started doing so. Basically, what I wanted to do is delete all in /system so I could install a clean ROM from my computer. Problem is, I have "flashing_locked" flag. I also downgraded it to Android 8, and I think it made it worse. Now, I don't even have internet connection (or what is called /persist), which also means I'm stuck in the setup screen. There's no way I have now to enter developer mode, nor activating usb debugging. Just wondering, is there any tips I could get from you guys to fix all this problem?
Thanks a lot.
Edit: I also think there's some "residual" data from those flashing attempts, Android 8 and also Android 9. I'm not sure if that has something to do.
Edit 2: I also requested a Unique Key from the Motorola official page, which didn't lead me to anywhere. Although I used "fastboot oem unlock <key>", it didn't work to me.
s9kii_ said:
Problem is, I have "flashing_locked" flag.
Click to expand...
Click to collapse
I'm wondering how you managed to downgrade the device from Android 9 to 8 with a locked bootloader?? that's very strange... To fix the known issue of broken wifi/mobile connection (as a result of the downgrade) it's recommended to revert back to Android 9.
So, you did the downgrade from 9 to 8. But now you can't finish the setup wizard to activate OEM unlocking? Please tell me, at which point it has been deactivated?? It doesn't make any sense...
Try the Lenovo Motorola Smart Assistant tool. It'll fix the issue.
s9kii_ said:
I also think there's some "residual" data
Click to expand...
Click to collapse
I think not. Flashing a firmware means copying image files to a specific partition. Each image file got its own partition table. There will be no data left.