Related
Hi to all,
Been here for a while and every time i log here in XDA (O3D forum), I always see new people bricking their newly bought O3D (stuck on LG Screen..., rebooting only to cwm recovery.., etc..etc..). If you got into a situation just do the search thing before posting a new topic which is already been posted because our forum (O3D Community) is still small so searching wouldn’t be a problem and there’s no need for a dig yet when reading all the topics posted here. All i can say is for all the people who just bought O3D always remember this "If it aint broke then don’t fix it" you will just end up voiding your warranty,
if there’s an update don’t try to push it on your warranted device, try to check first if the update is applicable to your device (country or region) because we all know that LG only released O3D in Europe so if you are in that place and check that your devices have an update, go grab it, but when it fails always call LG Europe (because you have a warranted device and they will assist you) and explain to them that you are experiencing difficulties in updating your unit, and for everyone else who is not in Europe (like me were my unit is not warranted)be very careful if you want to forcefully push that update to your unit (v10b, v10d or even cwm 4.0.0.9) because me i already bricked my device 3 times were i end up booting only in LG and nothing follows, the other is booting only to CWM again and again, and the last one is after unbricking the device and setting everything then when rebooting the unit it will end up stuck at the LG original android recovery system <3e>menu.
Note: Do this procedure at your own risk, i repeat "AT YOUR OWN RISK", its your unit so its your responsibility, you've been warned, i myself grab that risk and now I’m happy with my unbricked O3D (v10d July, 8, 2011 with fully working CWM 4.0.0.9), all the tools we need are here at XDA so there will be no problem getting those tools.
Ok enough about nonsense(hahaha), lets go down to business. As what the Title says, here we go.
Requirements:
This method will only work in WINDOWS XP MACHINE, i have tried it in Vista and Windows 7 but it will just hung.
I assume that all the necessary drivers are already installed from your machine because without them you can’t bricked your O3D. If by any means you don’t have it, just grab it from http://www.lg.com/uk/support/mc-support/mobile-phone-support.jsp and click the download link save it then run it after installing, it will run automatically, then do the following:
1. Go to Customer Support ---> Application, Manual & USB Driver Download.
2. Enter you IMEI then click the Search button.
3. After Searching, it will list two files form the File List, double click any of those file (me, i choose the file with divX converter)
4. After downloading, it will extract its content to C:\LGP920
5. Go to this directory C:\LGP920\USB_Driver, and double click LGUnitedMobileDriver_S4981MAN33AP22_ML_WHQL_Ver_3.3
6. Let it finish then if it ask to restart your pc, do it.
7. Optionally you can install the LGPCSuite, it can be found in c:\LGP920\LGPCSuite\, just double click the LG_PCSuiteIV_Setup.exe and follow the instruction.
Now that we have installed the drivers for O3D, we can move on to the next instruction.
Make sure to follow the instruction carefully and proceed if you know what your doing.
I have edited nikhil4186 and victortangocharlie post (Original thread: http://forum.xda-developers.com/showthread.php?t=1060121)
1. Detach all other peripherals from your PC. Exit all running applications on your PC especially other PC suites if any. Also exit running programs from the notification bar on the desktop. (Also uninstall Nokia or other phone drivers & microsoft visual ++ runtime environments - not an essential step.)
2. [IMPORTANT] Disable 'LGE Virtual Modem' in PC's Device Manager. (In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.).
3. Remove the Micro SD from your O3D.
4. Download the KDZ rom v10b_00 posted by Fab985 : http://forum.xda-developers.com/showthread.php?t=1155874
(v10d_00 is already available but this method is only tested with the v10b_00 rom, so if you wanna try your luck, its up to you)
5. Download the KDZ updater - http://forum.xda-developers.com/showpost.php?p=8651505&postcount=1
6. Extract it, then run the msxml.msi
7. Now the next step will be crucial because you need a full battery (for safety of course if you don’t want your unit to die while in the middle of the unbricking process) and you will put your unit in emergency mode (by pressing the power button and the volume up button), here’s how you will do it.
Case A. (This is my Case)
If your O3D can boot but only in CWM, charge it (me, i charge mine for 3hours in cwm), you wont see a charging status but you will feel your battery getting warmer.
Case B. (Never happen to me)
If your unit is just stuck at LG logo, try to charge it too and see if your battery is getting warmer, if not, better find another way to charge your battery or a friend who has O3D and borrow the battery.
Once everything is ok proceed to step 8.
8. Open Device Manager and under Modems check if you really disable the LGE Virtual Modem, if it is already disabled don’t close Device Manager, we will need it on the next step. Make sure you can see your Device Manager window and your modems devices are expanded (were you can see the disabled LGE Virtual Modem)
(THIS IS THE TRICKY PART AND YOUR O3D WILL JUST STAY BLACK SCREEN)
9. Plug your USB cable to your pc and then plug it to your phone then enter Emergency MODE (power button plus volume up button) This step is very tricky (me, i tried it several times before it detect my O3D as LG USB modem).
First when your pc detects your O3D, it will detect as OMAP4 then it will look for its drivers, just cancel it, then another device will be detected, if you successfully entered Emergency mode, your O3D will be detected as LG USB Modem, this modem should stay, if it disappear then you failed to enter the emergency mode correctly, try it again before continuing to the next step.
10. Run KDZ_FW_UPD.exe from the extracted folder.
11. Put the following settings:
Type : 3GQCT PhoneMode : DIAG
12. Under the KDZ File, choose the KDZ file you've downloaded from Fab985 post (v10b_00)
13. Press the Launch software update. (this part will take time because it will extract the kdz file into cab file, it took me 15 to 20 mins before it proceed to the updating process)
14. Once updating has started you will encounter this message:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
This message will come out from 1 to 100 counts:
CDMA: wPrama = 2004, IParam = 1
Model Dll Msg Not Found(2004, 1)
CDMA: wPrama = 2004, IParam = 2
Model Dll Msg Not Found(2004, 2)
And so on till:
CDMA: wPrama = 2004, IParam = 100
Model Dll Msg Not Found(2004, 100)
(Note: This message is case to case because i experienced diff counts then the LG USB MODEM disappear from the device manager list, first attempt count 64 then LG USB Modem disappear from the list, the kdz flasher stops from count 64, waited up to 10 minutes but nothing happens so tried it again from the enter emergency mode step, second attempt count 76 LG USB modem disappear but after a while kdz flasher still continues up to 100 counts then it stop there, waited for 5 minutes nothing happens so decided to remove my device and turn it on and viola it booted to LG original Android system recovery <3e>)
15. After you reach the 100 counts, the process is done, the LG USB modem from the Device manager will be gone, but don’t remove yet your phone to reboot it, try to wait up to 5 minutes before disconnecting your phone.
16. Turn on your O3D, if it boots in LG original android recovery, just choose the wipe data/factory reset, then reboot system now. Then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 17.
17. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition then reboot system now.
18. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not proceed to step 19.
19. If it comes back again to recovery after booting then wipe data/factory reset, wipe cache partition, and lastly wipe nv dynamic partition then reboot system now. (this part resolve my rebooting issue)
20. Turn on your O3D, then if it is successfully booted to android continue to setup your device but after the initial setup, don’t install or do anything yet, reboot your device again then see if it will reboot back to android, if yes, you’re done, your O3D is again alive and don’t bricked it again, if not I guess it’s the end of the line for now.
Sorry for this very long instruction. If it helps you I don’t have a beer fund because I’m not a dev. but a simple hit with thanks will do.....
TIPS NOT RELATED TO UNBRICKING:
Rooting:
Run SuperOneClick as Administrator, before clicking Root, click first the Driver Check and if no problem has been detected, no more settings is required just click the Root button then wait until it says done or finish.
ClockWorkMod:
After rooting, download rom manager from the market, after the install run it and tap Flash ClockworkMod Recovery (4.0.0.9), once successful you may now backup your current rom before you mess again with it, since I installed cwm in my O3D I never use the buttons to boot with it(power button plus volume down button), I always use the menu's with the rom manager to boot into or backup or restore or flash in CWM.
Upgrading:
For safety purposes, if you have a warranted device and then an update pops out, always do a fresh start, what I mean is if you already rooted your device and installed CWM, better removed it first before updating your O3D so when things goes wrong from your update process you can always call LG for it to be fix eliminating the needs to post something like “Help I brick my O3D and I can’t bring it to LG because I installed CWM blah blah blah etc.. etc…”, got the point so be responsible.
For the Mod: Sir if my post will violate something feel free to removed this post. more power XDA!!!!!
Many thanks to the following:
Aremcee
Renegade_Rules
Fab985
ik911
nikhil4186
victortangocharlie
and everyone here at XDA....
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
wuper said:
thanks for the info but does not work with clockwork installed and update over phone and stuck at firmware updating screen people.. waiting for a solution still
Click to expand...
Click to collapse
Did you follow the whole step, I know its a long process and it work with me, just follow everything and when you are in step 9 were you need to enter emergency mode,its a tricky step,make sure LG Mobile update is not running completely,open your pc device manager and expand the modems,try to remove the battery then press volume up and power button, put the usb cable then put back the battery,it will vibrate then your xp machine will detect it as omap4 device just cancel it but don't de-press the volume up and power button,then after a while it will vibrate again check if you see LG usb modem in the device manager,once you saw it and it stays,it means you successfully entered emergency mode then that will be the time you will run the kdz flasher and follow the succeeding steps.
Sent from my unbricked LG-P920 using XDA Premium App
bro I tried it with lg mobile modem disabled lg virtual modem disabled both are not disabled both are disabled but none of them make sense. Model Dll Msg Not Found(2001, 0)
is written and lg mobile driver gone but the phone does not reboot both 10d and 10b tried I restarted manually and it opens with fw update screen
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
wuper said:
I also get a "Get Chip Type error" when kdz reads phone information
Renegade_Rulez, you have the same problem did u try these methods?
Click to expand...
Click to collapse
I have bricked my phone numerous times, and in many imaginative ways. The above instructions are pretty much what I do whenever it gets stuck in some non-functional mode.
I tried this way like 30 times during the last week, I just got back from holiday and I just tried it on a Win XP machine and it's always the same it flashes and it never reboots, V10B/D doesn't matter... After flashing I manually power it on, and only get the Firmware update screen and it hangs there forever... I called LG today waiting for a replacement.
@aremcee
Sir thanks for confirming that this method really works.
@wuper @renegade_rulez
Are you doing it in xp machine, if you run it in Windows 7 the process will just fail. Only disable the LG virtual modem from your pc device manager and completely exit LG PcSuite and LG Mobile update. Make sure your xp machine detects your O3D as LG USB MODEM and not omap4 device, the detected LG usb modem should stay in your device manager under modem and it should be enable then you can now start kdz flasher. Will try to investigate what causing your O3D not to flash using the kdz flasher and if I have time will upload a video on how to properly enter emergency mode.
@all
Thanks for reading this, if you have a question just post it here and will try to answer it back as knowledgeable as I can.
Sent from my unbricked LG-P920 using XDA Premium App
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
wuper said:
if you can try this and make the phone work that means we are doing sth wrong:
1) install clockwork via rom manager
2) install update via settings telephone software update
3) after installing this update the phone stuck at clockwork recovery and all reboot is turning to this screen
4) flash 10b or 10d through kdz or lg mobile, it will stuck at firmware update screen as picture shown as attached
we try as u said on xp machine several times and device manager opened lg usb modem was there till the process finished after that it get lost and I waited 5 minutes and exit kdz and start manually, nothing..
(the attachment picture is turkish, it is written firmware is updating above and the phone will restart after finishing firmware update below)
PS_U_A_John stated in other topic he can flash a phone that is clockwork installed, that shows clockwork is not the problem, I think clockwork and our installed phone update and after flashed kdz rom are colliding each other and phone could not restart.
Click to expand...
Click to collapse
Hi wuper,
Can you try after flashing then turn on your device to recovery by pressing volume down + power button, or remove your battery then put it back while pressing those buttons, will it go to android recovery system <3e>?, if yes try to wipe everything then reboot. let me know. thanks.
Like wuper just told, mine is the same... It's not fixable in that way. Again this morning I tried on my XP pc and it's always the same. Just called LG again they will replace it within 24h we will see
update:
You cannot get into the recovery system, holding power + volume down the phone will power on and off again, releasing power when it boots and keeping volume down pressed gets the Firmware update screen.
same for me cannot enter recovery
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
Hi Zirowe,
Hmm thats strange, you and dnardz have the same problem, wiping the nv dynamic partition solved my rebooting issues and didnt experience this battery not charging problem, try to root your phone and install clockwork recovery 4.0.0.9 then reboot to cwm and full wipe your O3D including the battery stats, then charge your phone again and see if it is charging(maybe two hours), if it still doesn't work, download the v101d cmw rom by PUAJohn and restore it. Let me know
Zirowe said:
Hi, I had a bricked optimus 3d, after the installing the cwm recovery I couldn't turn it on, it would always go into the cwm recovery, no mater how I turned it on.
So I followed your "how to" on an xp pc, and I was able to flash the v10b fw.
Everything went like you described it: the counter reached the 100, I waited about 6minutes after that to turn it on, after that it would go straight to the android factory recovery (the one with the blue letters), and to phone won't boot up.
So I made a factory reset, than reboot, but nothint happened, then factory reset and wipe cache partition, than reboot, but I was still getting the recovery.
Then I made a factory reset, wipe cache partition and wipe nv dynamic partition, and then reboot, but the phone instead of rebooting turned itself off.
I turned it on, but it said, that the battery was almost empty, and needs a recharge (strange, because it was fully charged).
I pluged it on the charger, and the sign of a totaly empty battery was showed.
I left it for a couple of hours and the hole night, but the empty battery sign was still there.
I tried to turn on the phone, it booted up normaly, everything was ok, the phone was working again, but the battery was completely empty.
I bought 2 original replacement batterys, but the result is still the same.
So, can someone help me what went wrong, why does any battery work?
Why won't they charge?
I think that it has something to do with the last item I wiped, the nv dynamic partition, because after that the phone hasn't rebooted, but turned off.
What sould I do?
And no, unfortunately I don't have warranty on my phone.
Click to expand...
Click to collapse
try deleting batterystats.bin then rebooting.
Thank you, I will try it.
Will try it too..thanks Johnance17.
hefonthefjords said:
try deleting batterystats.bin then rebooting.
Click to expand...
Click to collapse
I've tried, but no luck, unfortunately, everything is the same..
hi,
It's strange what happens to you.
Have you tried this?
-Turn device off
-Take out batery
-Wait 5 min
-Re-insert battery
-do a hard-reset
-boot up device completly
-Turn device off
-plug-in charger (NOT USB-PC)
-Wait 1 hour
sorry I do not see much solution
It didn't work on mine also...restoring 10d and erasing battery stats..
Ok guys, long story short, here are the symptoms:
1) Still shows charging status.
2) Can enter download mode ONLY after being charged and the charging status is shown even for a short duration. Else, it will not react to any button I push.
3) Cannot enter recovery mode.
4) Somehow I can boot up to the SGT-2 logo which is rare. (I tried to start more than hundred times).
5) While in download mode, my PC wont discover the tab. In other PC, it simply says "device descriptor request failed". Which is code 43.
What I've tried:
1) Heimdall
2) Changing USB (3 times)
3) Different PC (2 times)
4) Removed the battery and put it back
5) Kies and drivers of all sorts I found on forums.
6) Swearing and threatening to kill the tab (numerous times)
I really need assistance. I maybe need to bring it to the service centre, however it will be very costing I presume. So does anyone have ever encountered the same problem as mine or know how to solve it? Please and thanks.
try odin ...
kukuru said:
Ok guys, long story short, here are the symptoms:
1) Still shows charging status.
2) Can enter download mode ONLY after being charged and the charging status is shown even for a short duration. Else, it will not react to any button I push.
3) Cannot enter recovery mode.
4) Somehow I can boot up to the SGT-2 logo which is rare. (I tried to start more than hundred times).
5) While in download mode, my PC wont discover the tab. In other PC, it simply says "device descriptor request failed". Which is code 43.
What I've tried:
1) Heimdall
2) Changing USB (3 times)
3) Different PC (2 times)
4) Removed the battery and put it back
5) Kies and drivers of all sorts I found on forums.
6) Swearing and threatening to kill the tab (numerous times)
I really need assistance. I maybe need to bring it to the service centre, however it will be very costing I presume. So does anyone have ever encountered the same problem as mine or know how to solve it? Please and thanks.
Click to expand...
Click to collapse
if u cannot go to recovery ,well it may be a problem which you need to show in service centre.
the problem you have occurs often if you messed up with the bootloader or the kernel.
so if u want to solve this problem in your device the only way is flashing the md5 file for your device aka the flashing of stock Rom without using recovery.
so the following are the steps you need to do .
1.go to sam mobile site(this only my 3rd post so i cannot add link)
in that site search for your device and download the md5 file.
2. install odin in your pc .(it is an application for windows,search on google or xda you can get the link.
3. you are lucky that you can go to the download mode. So you can charge your device and and go into the download mode.
4. now in odin app in your pc you should open the app.
5.connect your device to your pc
6. dont cahnge anything except you just click on pda in the app and select the md5 file you downloaded before.
and click start.
7.it will take some time .
HURRAY! YOU HAVE SUCCESFULLY SOLVED THE PROBLEM OF YOUR DEVICE.
If you are stuck in the samsung boot logo after this process try going to recovery mode and do a factory reset.
if this does not work please ask me.
Disclamer: Okay. This is my first XDA post so, it might be a bit shabby.
I am writing this post because it caused me a day of my life in reviving my dead Lenovo A369i. I broke my galaxy S5 so had to use this old buddy. Well, it got jacked while flashing it through the SF Tool as it accidentally (or as my hand was paining and i shook the USB cable to place in on the table - accidentally though) disconnected the phone while it was in the middle of an ongoing flash.
So, there it went, whole day of blood boil and headache.
Anyway, cutting to the point, if you have the following issues:
Bricked your phone while flashing via the SF Tool or bricked it doing something else.
Lost your IMEI [INVALID IMEI] after flashing or lost it anyway.
Your phone is showing no signs of life, even when connecting to the charger.
SF Tool gives Error 4032. Failed to read DRAM.
[/LIST
...then this is the solution you can try. At least one solution, the one that worked with me.
THIS SECTION IS FOR UNBRICK-ING YOUR PHONE IN CASE ITS DEAD. TO SOLVE IMEI, SCROLL BELOW
Things you should have before proceeding:
A Lenovo a369i phone (or any MTK devices that has the described issue).
Compatible MTK drivers.
Charged phone. Charge it for at least an hour. Your don't want to mess this up. I kinda did. It isn't mandatory but why the extra risk?
The stock ROM. Now, this is the most crucial requirement. With me, i had to download a bunch of ROMs before i got the one that matched my phone. There are two variants of A369i: The 'lite' and the non-lite (i don't know how else to put it). I had the lite variant and i didn't knew that. It took me 6 hours to understand the difference. Anyway, you should check yours and proceed. This is the lite 4.2.2 stock ROM.
Once you have all the things ready, follow ahead:
Extract the ROM somewhere. Navigate to the 'flash_tool.exe'. Run it.
Select the 'Scatter-loading' option, go to target_bin folder or wherever you have extracted the firmware and select the 'MTXXXX_Android_scatter.txt'. This will load all the files for flashing.
Now, here is where it gets a li'l tricky. I prefer to format clean the phone before flashing the rom. This helps avoid any interruptions. But it also wipes the user data. This is not mandatory but you should do it in this way.
Click the 'Format' button. Turn your phone off if it isn't. Squeeze the volume UP and Volume Down keys together and connect the USB to your computer. Your phone will get detected and your will see the bar at the bottom of the flash tool turning red and then green notifying that the format is complete. If you have any issue like the phone isn't detected, then you need to reinstall the drivers. This step is mandatory. If your drivers aren't installing properly, turn off the DIGITAL SIGNATURE ENFORCEMENT (you can search google how to) and install the drivers.
Once the format is done, remove the battery. Wait for a few sec. Fidget with the power button if you like, because i do. Then put the battery right back in and repeat the same steps as before but click the 'Download' button instead.
Then squeeze volume up and down >> Connect the USB to the phone. And wait till the tool completes flashing. And do take care you don't disconnect it. If you do, you might have to come back here again. LOL
Once its complete, you will be notified by a green notification. You can go ahead, disconnect your phone, remove the battery, fidget again, put it back up and boot your phone. Luckily, it might start.
IMEI INVALID SOLUTION
If you are as lucky as me, you might get this issue. Well, do not worry. You are not alone. And this might be just the solution for you.
You need to download a bunch of files and do a few steps. Here's what you need:
You need to root your phone. Framaroot worked for me.
If this doesn't work, you can try KingRoot app for rooting.
MTK DROID Tools for replacing your IMEI back to what is was. androidmtk.com/download-mtk-droid-tool"
The steps:
BEFORE YOU START, REMOVE YOUR BATTERY AND COPY BOTH YOUR IMEI SOMEWHERE. YOU WILL NEED THEM.
Root your phone. Open Framaroot and select any from the two options. You should get a success message if rooted. If not, install KingRoot application. You will need internet connection to root with KingRoot.
Once rooted, you need to open the MTK DROID Tool. Before connecting your phone to your computer, you need to enable 'USB Debugging' from the developers option. To do that go to Settings>>About>>Status>>Click Build Number for a few time>>go back>>Developers Option>>Enable it>>USB Debugging. Now connect your phone.
At the bottom right corner, you will find a ROOT option. Click it. It allows the tool to gain root access to your phone. It will pop up to install some app like supersu, mobileuncle tools and root explorer. You should install them. Also, you can backup your phone (This is optional).
Now click the IMEI/NVRAM type both your IMEI and click 'Replace IMEI.' Restart your phone. And that's it.
You have successfully revived your dead phone/Replaced your original IMEIs/Conquered the WORLD (well, for the moment ).
Cheers. :good:
done.
Leagoo T5c stuck at "Powered by Android" after "failed" attempt to install Android 11
Hi everyone,
I'm ready to say a thousand times "Mea culpa", but as I explained over and over in this very forum, I'm a noob when it comes to Android.
Android 11 was released yesterday, and yes, I downloaded an image for my phone, or what I thought would be a suitable image for my phone (got the arm64-v7a version), yes, I used TWRP to install it (as system image, not boot or any of the other options, because it seemed like the logical choice at the time), and yes, when the phone restarted, I was (and still am) stuck at the "Powered by Android" screen, and nothing happens.
(I didn't get any error message when in TWRP while installing the Android 11 image, though, no warning whatsoever.)
Even booting in recovery mode by pressing the Power, Volume Up and Volume Down buttons simultaneously won't work. The phone just restarts.
I thought I could save the day by flashing a stock ROM with the flashing tool provided by Leagoo, but since the phone won't shutdown, just restart over and over, the flashing tool is useless.
I juggled with the Windows drivers for the phone, hopping from one (ADB bootloader, etc...) to the next, no effect.
I wish I could open the phone and remove the battery, then put if back in, but that's impossible, because I don't have the tools it requires, so that option is out the window.
I'm open to suggestions that won't entail using this phone as a paperweight or a projectile to keep the demons at bay, though at the moment, I really don't see what purpose it could serve other than that.
Battery life isn't stellar on this device, so I suppose I could wait until it dies on me, then try to flash a stock ROM, but isn't there another way to revive the phone and start from scratch.
***I promise I won't try to upgrade Android again on this phone!***
I'd just rooted the phone, last Sunday, and everything was going fine.
I feel stupid like you wouldn't believe, but right now, I really need your help.
SOLVED: I somehow (and miraculously) managed to flash a stock ROM on the phone and I'm now in the process of setting it up as new.
A few pointers:
- On this phone, pressing Power/Volume Up/Volume Down will reboot the device; if you want to shut it down, you have to press Power and Volume Down only, and then sometimes it'll reboot anyway...
- I had to download and install either the generic USB drivers from here, or the Unisoc drivers from here to get Windows to recognize the phone. Maybe it was a problem with my phone, and the generic Google drivers will suffice in other people's phones.
You must use the UPGRADEDOWNLOAD_R17.17.2001 tool (the latest version available from here, at least), load the .pac you'll have downloaded prior to using the tool (unzip/unrar it as it'll most probably come in a compressed format) while the phone is unplugged and preferably turned off.
Load the .pac file in the flashing tool, plug your phone in the USB port, and click on the Download button. As soon as the tool clears the "Boot" stage in the Steps column, you're good to go, as it's the bootloader that causes the issues here.
The rest of the ROM install should proceed without a hitch. It should take about 10 to 15 minutes in all, then your phone will be turned off. First boot after a ROM flashing can take several minutes, but as soon as you see the Leagoo logo on-screen, it means you're home-free.
hi,
this is a guide for real helpless people, that got a V20 H918 T-Mobile out of the box and have no idea
what to do, to get TWRP and root. and since on this phone its a REAL hard odyssee if youre not a pro,
and you dont want to spend days and weeks to pick up countless small puzzlepieces to finally get all together up and running, i decided to write this guide. im no pro myself, but with countless hours of reading and try and error, misery, headaches and brainpain, i managed to get this thing running all right with working downloadmode,
newest TWRP-version and 20H oreo 8.0
so far, everything seems working good. ill play around with this version and if i encounter some crap, i will edit this guide later. sadly most "newbie-guides" here, are from pros for advanced users with decent knowledge. so when u start from zero, you dont understand half of what is written. thats why i will keep this guide as simple as possible, with some side explanations. its a lot to read and a lot to do, but this way works!
what we have before starting:
a V20 H918 t-mobile 20H oreo 8.0 with bootloader locked. simply a crippled standard phone.
what we will have after this guide:
a V20 H918 t-mobile 20H oreo 8.0 rooted, with unlocked bootloader, working downloadmode,
and newest TWRP-version.
with twrp u can backup your whole system "as it is", means u fukk up your phone, simply go to twrp-recovery, restore your backup and you have your phone up and running 100% as before all went down the drain. simply and easy. just like a new installation of win10, but in 5 minutes. u can flash custom roms, kernels etc., install all kind of stuff, no need to pay for apps anymore, get rid of obnoxious bloatware, just 100% freedom and the full potential with the V20 (which is the last phone of its kind with exchangable battery, which is why i got myself 3pcs of it )
sidenote: get yourself some extra protection foils so u can change from time to time.
also get yourself 1 or 2 10000mah powerbatterys from aliexpress (perfine) with protective rubbercase, of course, they dont have the printed-on mah, but at least a considerable amount, so that your phone will last at least 3-6 days. my V10 lastet 11 days normal usage with zerolemon powerbattery. unfortunately, these retards refuse to send to europe, and as far as i know, theyre not producing for LG phones anymore, so aliexpress/perfine is whats left.
the rubbercase gives the phone a superior protection, adds a serious amount of weight and will stick in your hand like glue. it is by far less likely to drop out of your hand like these glass-phones for imbeciles. and if it drops, the rubbercase grants excellent protection. my V10 dropped countless times, still working perfect.
but lets get to the guide now.
at first, we will unlock the bootloader. without it, you wont be able to do anything.
unfortunately, LG produces great phones (with great audio!) but terrorizes the users with their strict anti-root attitude. it seems it gets harder everytime to root and unlock the bootloader. i remember back in the days old samsung devices, had been rooted in no time. this one here cost me about 2 weeks.
on this phone, u simply cant hook it up to the pc, and unlock the bootloader with adb. it will be recognized by the pc, but as soon as u enter fastboot, nothing will happen, no command works.
the solution is a FWUL (forget windows use linux) usb-bootstick, with that u boot your
pc into a custom linux (i think) only here u have full access to your phone via fastboot and can unlock the bootloader in no time. it will not work on win10 !
- first, get rufus, a win10 tool, with that u can create boot-usb-sticks.
https://rufus.akeo.ie/
- then get the linux FWUL image (only 15GB version is still up)
https://androidfilehost.com/?w=files&flid=214529
- unzip the linux image to your c drive or your desktop.
- start rufus and select your usb-stick (it should be 30gb+ in size)
be carefull not to chose any other drive or stick (it will get erased completely), better double check.
- select the image you just unziped. (i use 7zip for unzipping)
- leave all other options as they are, press start. when dialog-box pops up, chose DD-mode !
- now waste some time, as it takes a long time to create the bootstick (in my case about 30min)
- when the stick is ready, in my case it couldnt be recognized anymore in win10, its just a raw-drive, that cant be
opened. thats allright. dont worry
- now close down all applications running and insert the created bootstick. (at this time u might consider using a
separate laptop, so you can follow this guide here at pc and use the laptop with linux running, thats what i did)
restart your pc, hit F2 or F8 oder DEL or whatever to enter bios.
select the created stick as bootpriority nr1. so that the system will use this stick as
the first bootmedium to boot from.
- u get to a screen with 9 bootoptions to chose from. chose the first one. it should now boot into linux.
when password request pops up, enter: linux
- u reach the "desktop"
connect your LG V20 H918 20H via usb-c to the pc, which has linux running, make sure that
developer options are unlocked, OEM-unlock and USB-debugging is enabled and u chose picture transfer protocol
(PTP) as transfer-protocol (also in developer options). if PTP doesnt work, try media transfer protocol.
watch your V20, at some point it will ask for confirmation of connection , click OK.
in linux, click on the up-arrow in the most downleft corner and chose "terminal emulator", which is
a pendant to windows shell/command-line.
- here you can execute the adb commands.
first, check if your V20 has been recognized by your pc with linux running.
type: adb devices
it should appear a message like:
* daemon started successfully *
LGH9182bfblablabla device
that means, that your V20 has been recognized correctly. now you can reboot it in fastboot mode.
type: adb reboot bootloader
your V20 screen goes black and seconds after, it restarts in bootloader mode ready for unlocking.
you might get a red warning that your warranty is void if bootloader is unlocked. cool.
type: fastboot oem unlock
wait for response, your bootloader is now unlocked.
u can check by typing: fastboot getvar unlocked
it should say: yes.
the bootloader is now unlocked.
now we will replace the standard recovery with twrp on the phone.
this step will be a little confusing and complicate, just follow the steps, and it will work.
since we cant flash twrp with adb, we have to use the linux bootstick again.
but before, we have to downgrade the 20H version to 10P, bcuz the next stepp will not work with 20H !
so you get the following:
DOWNLOAD H91810P KDZ FILE
https://androidfilehost.com/?w=files&flid=282709
after that, download LGUP (the LG tool for downgrading from 20H to 10P)
and uppercut (dont know what uppercut is for, i just used it instead of running LGUP directly and it worked. its supposed to recognize the phone/driver automatically)
http://downloads.codefi.re/autoprime...sh_Tools/LGUP/
and download the recent LG-usb drivers.
http://tool.cdn.gdms.lge.com/dn/down...=UW00120120425
install LGUP, uppercut and usb-drivers.
connect ur phone to pc in download mode.
turn of phone, press and hold vol.UP button and connect usb cable, small message appears, phone is now in download-mode and waiting.
now run uppercut and hope, that ur phone will be recognized. if not, think about, what kind of restrictions u did to ur system, like OnO-shutup or xpantispy (both great programs to keep win10 from calling home to scum gates) or whatever. in my case, it ONLY worked, after i reset the OnOshutup settings to recommended. so the phone get recognized correctly in LGUP (if not, try laptop or different pc), select upgrade and select the downloaded 10p KDZ file. press start or go, and wait until the procedure is finished.
now your phone is downgraded to 10p.
now we go back to linux, we connect the phone in downloadmode with the pc/laptop where linux is running,
(turn phone off, hold volUP, connect usb-c-cable with linux-pc/laptop, phone will start in download-mode.)
make sure, your laptop/pc has internetaccess.
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode. why? i dont know, thats the way it worked for me.
we dont want twrp onto downloadmode, since twrp is a recovery. so the next step is, to flash the newest twrp version for H918 to recovery. at first, we will gather all neccessary downloads, after that, we will flash them one by one. that way, you dont have to get your micro-sd card out of your phone again and again. we put all together on the card, put the card in your phone and we are almost done. for now, have your micro-sdcard connected
with your pc and download the following:
twrp-3.4.0-1-h918.img
from
https://dl.twrp.me/h918/twrp-3.4.0-1-h918.img.html
and put this .img file on micro-sd card.
then download (and put on sd-card):
MAGISK ZIP DOWNLOAD (for root)
https://github.com/topjohnwu/Magisk/...gisk-v16.0.zip
then download original 20H firmware(and put on sd-card)
H918 20H
https://androidfilehost.com/?fid=11410963190603864639
you remember, we have now twrp on downloadmode
for restoring download-mode, download (keep on desktop or c):
H91820h_00_1115.kdz
https://lg-firmwares.com/downloads-file/17076/H91820h_00_1115
then download the firmware extractor:
https://forum.xda-developers.com/attachment.php?attachmentid=3975633&d=1482337024
ok, lets see what we have now:
we have the phone bootloader unlocked and twrp on downloadmode. we can access twrp when we start the phone in downloadmode (hold volUP, and connect usbcable, phone will start now in twrp.)
we dont want twrp on downloadmode, we want twrp as recovery. and we want to restore the original downloadmode. for that we do the following:
unfortunately, the neccessary file for flashing orignal downloadmode is not online anymore, so we have to extract it from the 20H firmware with the firmware extractor (thanks to logical gamer for his guide)
https://forum.xda-developers.com/v20/how-to/guide-h918-restore-laf-partition-t3804728
Extract WindowsLGFirmwareExtract vx.x.x.x. to your desktop, and open it up (preferably in it's own folder).
u might have to install framework 3.5 for it to run.
Select Open across from KDZ/TOT file, and browse to your KDZ (H91820h_00_1115.kdz)
you download previously and double click.
After it loads the kdz check H91820h00.dz, and click Extract KDZ.
Close and re open the program this time Click open across from DZ File in the folder where you placed WindowsLGFirmwareExtract you should see a file called H91820h00.dz Double click to open it.
Check laf_6.bin then click Extract DZ.
put this laf_6.bin on your micro-sdcard. thats your original downloadmode we will flash now.
ok, now we have our micro-sdcard with twrp, magisk, laf_6.bin and H91820h.zip.
put this mirco-sdcard in your phone. start the phone in downloadmode.
it will start in an older twrp-version. in twrp, go to install and select install img
select the twrp 3.4.0.1. img and on the following screen select "recovery"
swipe
this will flash the 3.4.0.1 version of twrp onto recovery.
then go to reboot into recovery. it will now boot into the newly flashed recovery.
then go to wipe, advanced, and select everything EXCEPT micro-sdcard!
this will totally wipe your phone (except twrp), so u can flash the 20H firmware onto a clean phone.
then, go to install, select H91820h.zip. this will flash your original oreo 8.0 firmware.
after that, go to reboot into recovery.
go to install, select magisk. install.
this will root your phone.
after that, reboot into recovery, go to install, select install img, select the laf_6.bin, and select "download"
now the original downloadmode has been restored.
now you can reboot into system, your phone will start as on day1, with new twrp on recovery and root.
i did a complete backup in twrp, so i can get back to a day0 clean install whenever needed. i will do a second backup with twrp with all the stuff installed and working ok and place this on my sd-card. so when things go bad, i always can go back to this state in no time.
congrats, your done. and me too . gonna get a cold one now.
hope this guide will help someone. in case, just drop a like/thanks/or just a short note.
its a long guide, and im no pro, if i made some mistake pls. tell here and i will correct.
thx to all the pro-guys for helping the helpless.
Hi
Im on v20 H918 firmware 10p with bootloader unlocked.
I tried with dirty cow but not works with lafsploit i have a Problem with rufus for create a bootable Linux.
Pendrive is 32 GB i followed your setting but my PC boot only in windows 7.
I succesfully unlocked a h990ds with dirty santa but for this model is not supported.
Can you help me
hi
i tried with dirtycow also, didnt work.
thats why i eventually came to the method i described.
teling by your short description, your next step would be to create a bootable linux-usb-stick, and to find a pc where it will boot correctly. the stick didnt boot on my main pc ( i dont know why, it just canceled with an error),
thats why i had to use the laptop where it worked.
Thanks for the guide man! Very funny and fun to read. I can't wait to turn mine into a 4-day brick like yours. #lastphonewithbatteryrevolution
Sadly I got the dreaded encrypted error at the end though when booting. Everything else worked fine.
After the encrypted error though I formatted and flashed LineageOS 17.1 and then magisk and still keep getting error 1. Even tried Lineage recovery and still same. I think maybe a problem with Magisk 16 itself.
Anyway it works fine just no root.
Edit: Had to flash Magisk 21 and it worked
Thanks for this tutorial. I was able to get my V20 rooted with minimal trouble. The only major trouble was finding a computer that will fully boot into Linux and the only minor issue was locating the UPPERCUT but I was able to find it. Link below.
It's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
UPPERCUT link: UPPERCUT: Add Any LG Device to LGUP for TOT/KDZ Flashing (G4|G5|G6|V10|V20|MORE???) | XDA Developers Forums (xda-developers.com)
MAGISK link: Releases · topjohnwu/Magisk · GitHub
cool, glad this guide helped at least a little bit. my v20 still works great, no issues so far. as a side phone for unwanted persons, i still use my v10 with powerakku and rubbercase "brickstyle" every time i hold a regular phone from other people, it feels weird since these phones weigh like nothing, and i have to focus not to slip it out of my hand. i love my bricks
and by now, about 4 month later, reading this whole guide, to me its still strange and hard to follow. there is no way to get through this without reading everything possible about it and become familiar with all the technical terms.
I have a h918 with an unlocked bootloader and it's downgraded to 10p. The shell script fails everytime to a hash check. I've run it 4 separate times with the hashes being the same every time. So it looks like the file has been updated but the hash hasn't.
I'm coming late to the game and it seems most of the guides are out of date. I'd appreciate any help I can get.
Update: It works fine. This is by far the easiest guide to follow that I've found. Many thanks! I did have to follow xstahsie's tip.
xstahsieIt's probably worth mentioning that I had to rename laf_6.bin to laf_6.img in order to flash it in TWRP. Also, at the time of writing, the latest version of Magisk is 22.0 but I used Magisk v21.4 instead because it had a zip file (Magisk-v21.4.zip) available for download so that I can flash it via TWRP. Link below.
I followed the guide after I rooted and installed Lineage OS 18.1. I had to remove LineageOS because it was bad with response, couldn't see hidden wifi, and just ran hot. So I followed your guide and I am in a logo bootloop and get the reminder to lock the bootloader everytime it starts. Any suggestions for getting past the bootloop?
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
memnon79 said:
I fixed problem by installing LAF you referenced and then LGUP to 10p kdz. However I noticed two things.
1) Whenever I boot up I have the nag message to my bootloader. Any way to address this?
Click to expand...
Click to collapse
You're stuck with it, it's just the way it will be from now on.
memnon79 said:
2) If I try to follow steps above to install 20h, I get a decrypt message in TWRP after I flash 20h and before Magisk. Anyone see this? I didn't encrypt my storage before hand.
Click to expand...
Click to collapse
I don't remember seeing that. I probably didn't care if it did show up since it was a new install from scratch anyway.
Does encrypting the phone work after following this guide?
hey there, cant help u with the encryption thing cuz thats far beyond my knowledge. some weeks ago my phone dropped, and a tiny crack on the edge appeared. what i didnt know was that this crack is the beginning of the end of the V20. heres the story short: small crack over time leads to a bigger crack, bigger crack multiplies and u have some more cracks covering the whole screen. also the screen can pop off and hanging loose a little. in my case 4-6 weeks and i have to get out phone 2/3 which i am setting up using this guide now. fortunately i left myself a huge pyle of information on how to do this when starting at 0. over time u forget EVERYTHING u have done, so having these infos is hammering.
lucky me did i save my internal memory of phone 1/3 bcuz 30min later the screen was totally fuqqed up, no access no chance of backupping internal memory.
so heres my recommendation:
DONT drop your phone. even in my case with rubber battery case from aliexpress
(perfine "10000"mah) a 50cm drop cracked the edge of the screen. if that happens, backup your internal memory !!! (just do this on a regular base)
when ur screen gets damaged and u cant enter information or cant see anything anymore on the screen ur internal data is lost. so always have ur internal memory backuped!
and great job LG for producing such a huge pyle of ****. one small drop, screen cracked, bravo, last time i ever bought anything from lg. my V10 dropped like a 1000times, nothing, still up and running. v20, drop, 6weeks later, dead. thanks LG the customers all over the world couldnt wait to use these bull**** crackable glass-screens. great job, -1 customer.
I've tried this on two different computers with two different cables in every USB port on the machines but can't get by the Windows portion. I am using UPPERCUT as the windows box/LGUP reports no device found without it...
Of course UPPERCUT drives windows security mad as it's reported as doing bad things but as I'm using an extra win laptop that will be wiped I disable all of that....
I have three different sourced KDZ files as the one linked wasn't initially reporting any mirrors. Eventually a mirror did pop up for it but by then I had downloaded two others -- all were the same size and one of the three reported from LGUP was bad. Every attempt with the other two failed. Invalid Command response came up a few times... sometimes it just failed at around 80+ percent from the PC side which was 99% on the phone's downloader mode progress bar.
It's very frustrating.... I would like to blame windows but there seem to me plenty here with success... any other ideas?
Also... since it got so far, rebooting at this point just goes to the download mode so I might be hosed... I can force it to the fastboot mode and it is still unlocked so I've been trying to install TWRP onto recovery using the linux/android machine but when I type
fastboot flash recovery twrp.img from the directory where twrp was downloaded I get this:
sending recovery --- okay
writing recovery --- failed remote: unknown command
So... any thoughts?
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
dikkbutt said:
aloha, at which step are u stuck exactly? did u make your phone being recognized by the win10 pc?
one thing to regard is, that a usb-CHARGING cable possibly wont work, u need a designated media/data-cable.
i had this situation before, where using many different usb cables drove me insane bcuz i simply couldnt establish a proper data connection with phone/pc, it just didnt work. it took me many hours until i realized, that all of the cables i tried were charging cables!
for me the most difficult step was having the phone being recognized by the win-pc, the rest went relatively easy.
Click to expand...
Click to collapse
The phone is recognized by the PC, no problem. I do have to use UPPERCUT to get LGUP to recognize it though. The step I'm stuck at is applying the downgrade. It gets to various percentages of done-ness and fails. It got far enough that now my only options on the phone are Download mode or fastboot mode. Problem is, I can't seem to get anything to push to recovery so I assume that it's still not properly downgraded.
I've tried a few different cables and keep in mind the cable I used in the linux adb bootloader step worked fine. I don't entirely know what difference there is between a charging and data cable but I do know the main differences in the steps are a> Windows and b> size of transfer.
weird. since im no pro myself, my ideas are limited on this one. there might be some kind of loose contact at the charging port,
that when the phone is moved just a little it looses connection for a second and reconnects again, had that in the past, so try not to touch the phone at all. did u use the 10p kdz file mentioned before? did u make sure it has been downloaded correctly?
if an error occured and there are some % missing... its like faulty ram, hard to detect.
assuming, u did or did not downgrade to 10p, did u try to continue with the linux-step? ---->
---------------------------
on the linux-desktop, click on the LG folder, inside, click on LGLAF runningnaked.
a terminal-window opens.
type: git pull
type: git checkout h918-miscwrte
type: ./step1.sh
now we have flashed twrp onto downloadmode
-----------------------------
maybe uppercut/lgup displayed an error message for no reason, and the downgrade itself went through without a problem in the background.
pcs sometimes do weird things.
if nothing works, try setting up win10 and try on a virgin system. in my case, OnOshutup prevented win10 from recognizing the phone,
or try using a 3rd pc from a friend.
i was able to setup my phone 2/3 using this guide in 30min, no problems at all. (i hope i wrote down, how i solved that simlock issue.....)
no matter what causes the problemin ur case , id be interested to hear what it was.
Thanks! Rooted and Unlocked thanks to this guide!
I tried following other guides using UPPERCUT and it fails to downgrade due to Anti Roll Back. How does this relate to this guide since the last thing I want is for (by design) for it to brick the phone. I have yet to find anything specific saying an unlocked bootloader will bypass the anti rollback check.
Hi As a noob does this keep VoLTE? I have followed this guide and backgrade to 10p was perfect! VoLTE working on a phone that was "new" from china. VoLTE did not work on the 20p rom it had. Also does anyone prefer Phoenix591's h918-20g-prerooted rom to the stock one? I have read a lot but am somewhat confused by varying instruction threads. I want to use this as a daily driver. Thanks