Related
Hello. This is my first time actually visiting the Optimus One forum although I have had my phone for maybe 2 months. I was not going to root my phone, in case I need warranty, so I was using the stock rom, although it was a little slow.
So I thought MAYBE there is an update on LG website, so I went on there, and found out that I can update by connecting to the computer. So I did download all the files they required (at least I think I did), and I followed the instruction, and started updating. Here comes the first problem encountered: While the phone was n Emergency mode, during the updating was in process, it said Phone and PC has problem communicating or something like that. And there was a restart button. It said disconnect the phone, and remove battery and connect again, and then press restart. So I did. Then now after that the LG software update tool doesn't recognize the phone. It said connect it and press OK or something. I think this is the point where I bricked my phone. A NON rooted phone. So I don't even have a custom recovery to flash anything! I hate LG right now. They are so stupid. I don't know what happened..
I tried the method here:
http://androidforums.com/optimus-one-support-troubleshooting/237642-bricked-lg-optimus-one-help.html
But I couldn't download the right KDZ firmware for my phone, that is available in the link in that link above. I'm in Canada and my phone is from Koodo and the model name is P500H.
So I got a random KDZ file that's for P500 from internet, but the in the KDZ_FW_UPD emulator, that's in the link above, it says my phone is NOT detected! I reconnect the phone and restarted the software so many times. I think they want me to connect the phone while it's Turned ON, and press the "Connect to USB" button. I'm not sure though.
***PLEASE*** Help me! I really need to unbrick this..
Sorry for the long post. And Thank you!
to flash custom recovery follow http://forum.xda-developers.com/showthread.php?t=1318750
Then flash any rom in zip format from custom recovery (according to your baseband)(search development section of p500)
Once you can boot into rom , to revert back to stock condition follow http://forum.xda-developers.com/showthread.php?p=19006040#post19006040 or http://forum.xda-developers.com/showthread.php?t=1324105
mak.3736 said:
to flash custom recovery follow http://forum.xda-developers.com/showthread.php?t=1318750
Then flash any rom in zip format from custom recovery (according to your baseband)(search development section of p500)
Once you can boot into rom , to revert back to stock condition follow http://forum.xda-developers.com/showthread.php?p=19006040#post19006040 or http://forum.xda-developers.com/showthread.php?t=1324105
Click to expand...
Click to collapse
Thank you SO much for your reply. I was searching for HOURS, and Finally found out how to make the KDZ update tool recognize my device. A LOT of people can't get it to work, but I saw someone in this post http://forum.xda-developers.com/showthread.php?t=1015332&page=4
that you need to remove sim card and battery. So I did, and restarted the update, and YES! It worked! I was on Foryo, but I got Gingerbread Rom from
this forum http://mobilesyrup.com/forum/showthread.php?t=21446&page=2
And I'm actually on GB now!
OMG, I have so much homework, but have been doing this for the WHOLE day! Wow..
Thank you so much for your help anyway!
Oh thanks
Sent from my LG-P500 using xda premium
Chapter 1: The Foolishness of the User
Hi, I have the korean version of the optimus one(KU3700). It was on gingerbread(2.3.4) stock. I was trying to root it by downgrading it. I entered "adb reboot recovery" and I'm stuck. I tried to reflash it by going to emergency mode with the button combinations using the KDZ updater with this
"csmg. lgmobile. com:9002/swdata/WEBSW/LGKU3700/AKTFBK/KU370040_00/KU370040_00.kdz"
and it worked without any errors but when it when it came up it was still on recovery mode. Is there any way I can change the phone mode to the regular mode
Chapter 2: Journey to Salvation
For anyone who has this korean optimus one, after days of searching, I've found a web site that gave me hints to solve the problem. I just needed a different kdz file and I got it here:
h t t p://sirospace.tistory.com/category/Android%E2%97%86
popped it in google translate because I'm Filipino and can't read korean.
Downloaded the froyo kdz and flashed. I hope this can help other people stupid enough to play with their phones by typing random commands without knowing what it does, like me, LOL...so happy, now it's time to root
Chapter 3: False Hope
OK so I have successfully unbricked and rooted my KU3700, now The problem I have is installing a custom recovery on this phone, none of the images I try work.
Recovery images I have tried are as follows:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
Every time it finishes and reboots, it gets stuck at the LG logo.
Chapter 4: Wisdom Within
Found the problem. The images above are for the P500.Even if the KU3700 hardware is similar to the P500, flashing firmwares made for the other model will result in errors. The same holds true for custom recoveries.
Chapter 5: The Plea to the Gods
I've contacted drellisdee and submitted the files needed for custom recovery creation for the KU3700.
Just waiting for the flash image now. Thank you everyone
Chapter 6: The Forgotten
It seems drellisdee is busy right now. I'm a windows user and knows nothing about programing. So if anybody can help I'm sure the KU3700 community would be greatful. I've attached the files I think are needed to make a custom recovery.
Chapter 7: Quest for the Custom Recovery
I got tired of waiting. So as a windows user with no experience in programming, I did a lot of copying and pasting, I managed to port clockwork mod using virtualbox following this website:
h t t p://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
So I have got a bootable and flashable custom recovery but nothing works yet. I still need to configure it according to the device.
I have uploaded the image and the build files. Please help me configure it and tell me what's wrong. I really don't know that I'm doing
PS: you can try flashing the custom recovery by doing "fastboot flash recovery /Path to/recovery.img and you can go to recovery by using android terminal and type "boot recovery". It will boot, but that's that LOL. Take out the battery to boot to normal mode.
Chapter 8: The Holy Grail
LOL, I found the answer again. I was so frustrated that I kept squishing the phone in recovery and found out that it was just a button configuration problem. A bit of research and I found out that I can toggle it by pressing volume up and volume down at the same time. WOOHOO!!! Custom Recovery at last
Chapter 9: Invasion of the ROMS
And here at last, the user is retired. But the adventure is far from over. It is foretold that the creation of the Custom Recovery will begin a new era. The key to open the gate has been found. So our hero will await the invasion of the ROMS<background music...> END
you can see at
tinhte.vn/threads/908874
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
vidgen13 said:
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
Click to expand...
Click to collapse
yes i see.but i'm newer android.i only send you link to fix
i hope have a pro android to fix your brick
This is just a shot in the dark because i didn't understand what you did entirely : have you used the combination to actually recover the stock rom after you flashed with KDZ ? (Home+VolDown+Power)
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
vidgen13 said:
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
Click to expand...
Click to collapse
Are you sure you flashed the right rom for your phone? There's an application that downloads the required rom for your phone according to your IMEI/SN, but i don't know if it works with the korean version.
Yes it's the KDZ file, unfortunately it's the only KDZ file out there for ku3700. Shouldn't have settled for this korean version
why you wanna downgrade the latest version?
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
asmOne said:
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
Click to expand...
Click to collapse
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
I dont get it ,p504,p505,p506 are versions of p500??? And why some of our roms work on those phones?? So by logic this stock work on p500???
Sent from my LG-P500 using XDA Premium App
vidgen13 said:
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
Click to expand...
Click to collapse
this method worked for my working KU3700 when I'm using my 1st KU3700 I also was struck as you and finely I realized there are No custom roms for Optimus one Korean edition (KU3700/SU370) and I had to connect my phone to an Octopus box (lg softwere box) via software box installed the official firmware. if this method not working you have to connect to a software box.
connect to the internet your PC and 1st install Driver and 2nd install the LG update tool. after installation connect your phone to computer and wait a five seconds for comport installation. after install your phone Run LG Update application.
it is connect to the server automatically indicating red line and after search for latest firmware.
if you can Update your phone it is shows Update butten.
Driver
http://www.4shared.com/file/C3BSNx9P/lgunitedmobiledriver_s4981man3.html
LG Update Tool
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Thank you all for the quick answers, but I already have a rooted ku3700. All I need now is a working custom recovery. If someone has the same phone, please tell me which image is compatible
you can appear the emergency mood with android logo.
it means you have an Empty phone. your Os was been erased. You have to connect your phone to Octopus software box and box server has you original Os for your IMEI. this is the only solution. if you will able to solve this problem without a Software box please inform me. we can open a New Thread for Korean edition.
(ku3700/su370)
I already got out of the emergency mode without an octobus box. It's really simple, you just need to use a different kdz file. The hard part was looking for the kdz file. I have 3 kdz files. KU370017(froyo), KU370033(gingerbread-rootable), KU370040(latest one from LG, gingerbread-unable to root). Just flash with the KDZ updater. I'm on the second firmware because I can't root the latest firmware. To root it, I used super one click(latest version, use zerg rush option). Now I'm just waiting for a custom recovery from drellisdee so I can use custom roms. When I get it, I'll ask him if I can post it so we all can have uber phones LOL
Updated the thread. Can somebody help?
vidgen13 said:
Updated the thread. Can somebody help?
Click to expand...
Click to collapse
If you have flashed a working clockworkmod you can enter into clockworkmod via ROMManager (search in google play aka market). In ROMManager you have "reboot to recovery" option in case you want to go to recovery to flash something. Also you can try to flash from ROMManager a custom recovery (5.0.2.0 for oldBB or 5.0.2.7 for newBB), try to choose to phone model LGP500 oldBB, try and test if it's working. Wish you luck.
Thanks but I already have a working recovery. I just need some ROM makers now
vidgen13 said:
Thanks but I already have a working recovery. I just need some ROM makers now
Click to expand...
Click to collapse
Have you tried CM7.2? if your phone is very similar with Optimus One i doubt it isn't compatible with your phone.
If your phone use 2.6.35.10 or 2.6.35.14 kernel you can give a shot to try CM7.2 on your phone, but before try this make a backup first.
Check this thread Post Your CyanogenMod 7.2.0-RC1 Nightly Questions HERE!! for CM7 custom rom.
yep, it doesn't work. Is there a tutorial for building cyanogen for unsupported devices? All I can find are tutorials for supported devices. I've already got the source code from LG. The problem is just incorporating it in the cyanogen mod. I wish this phone had more users LOL
Dear Developers and Users
I have moto E xt1021 some time ago. Once it happen that my phone Android crashed then I successfully flashed back new kitkat 4.4.4.
My phone worked fine and even checked if there is any software updates, I think this was my mistake. Then I upgraded to Lollipop 5.0.2.
Also I installed CWM recovery but as a beginner, did not thought of backing up all my data, another mistake because all my data are gone now.
Every thing was fine for about one month. Suddenly, last week my phone starts freezing and not responding to any touch.
Well, the quick solution is re-start. But it never came back again to more than the Moto logo.
Depending on what I was reading since last week, I think my phone is brick now, hopefully soft, because the situation of my phone is as follows
Stops by Moto logo when pressing power on.
I can go to the Bootloader menu.
I can see my CWM-recovery menu. But from here I am not able to flash new ROM, Stock, or even recovery.
My phone is unlocked and rooted as far as I remember, I hope it is still.
and the most important part:
USB debugging mode WAS NOT ENABLED before it crashes and it still not enabled.
I installed on my PC SDK, fastboot and ADB tools, Motorola Drivers.
I have been trying for a week now several tens of threads but unfortunately never succeeded to bring it back working.
I don't care for my data now. Important to get alive.
I am sorry for the long thread. I tried to put all information needed and hope nothing is missing that clarify this problem. BTw, I bought my phone from Germany.
Any help or recommendation what to do would be highly appreciated, Especially with enabling the USB DEBUGGING MODE which I think is the key solution.
Thanks in advance
Sadam.
What about: http://forum.xda-developers.com/showthread.php?t=2755857
If you can boot your phone into fastboot mode you should be fine. Just follow the flashing tutorial.
Alternatively, if you can only get into cwm recovery there is an option in moto e android development to restore to android 5.
am2012 said:
What about: http://forum.xda-developers.com/showthread.php?t=2755857
If you can boot your phone into fastboot mode you should be fine. Just follow the flashing tutorial.
Alternatively, if you can only get into cwm recovery there is an option in moto e android development to restore to android 5.
Click to expand...
Click to collapse
Thanks for your answer am2012
I followed this tutorial and many other similar threads.
It gives me always the same error whenever I ran command with mfastboot.exe (I mean the whole bunch of mfastboot commands). Please check the error.jpg in the attachment. Maybe some one have seen such error and how to solve it.
Could be also something to do with the partition of my device ? If yes, Any suggestions are appreciated!
Thanks
SadamHazaimeh said:
Thanks for your answer am2012
I followed this tutorial and many other similar threads.
It gives me always the same error whenever I ran command with mfastboot.exe (I mean the whole bunch of mfastboot commands). Please check the error.jpg in the attachment. Maybe some one have seen such error and how to solve it.
Could be also something to do with the partition of my device ? If yes, Any suggestions are appreciated!
Thanks
Click to expand...
Click to collapse
So you can actually boot into cwm recovery not just bootloader?
Can you take a picture of your phone in recovery? I might have an idea.
I asked a friend and he said go to bootloader and flash 4.4.4 using adb. http://forum.xda-developers.com/showthread.php?t=2759495 You must flash 4.4.4, not earlier or phone will brick.
am2012 said:
I asked a friend and he said go to bootloader and flash 4.4.4 using adb. http://forum.xda-developers.com/showthread.php?t=2759495 You must flash 4.4.4, not earlier or phone will brick.
Click to expand...
Click to collapse
I tried it and again the same failure as in the first reply
I attached my bootloader menu and Recovery menus as well.
Thanks
SadamHazaimeh said:
I tried it and again the same failure as in the first reply
I attached my bootloader menu and Recovery menus as well.
Thanks
Click to expand...
Click to collapse
It's a little beyond me now. I have found this YouTube video: https://www.youtube.com/watch?v=pYjQePBRzhk
Let me know if it is any good?
If you search for the error codes there are lots of results on google.
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
Hi,
I tried to upgrade my US998 from Oreo to Pie using LGUP patched. The upgrade process went well until the phone restarted and have this error message:
"Your device has failed a routine safety check and will not boot..."
I did try using LG Bridge to fix = not working
I did try fastboot boot laf.img (using extracted laf from H93031a_00_OPEN_EU_OP_1105) not working.
Any other solution?
Thanks
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
JanBoyGamer23 said:
This Post got recommended to me. I am a Samsung user so my answer will probably be very stupid.
If you have fastboot, why don't you flash a recovery and a custom rom? Ik stupid but it's the only thing that comes to my mind since i don't have a LG phone lol
Click to expand...
Click to collapse
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
jaacoozee said:
Installing TWRP or any recovery wont work for me. The bootloader still locked thou.
Click to expand...
Click to collapse
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
JanBoyGamer23 said:
Is that "Download mode" the same as the Samsung one? How do you NORMALLY access it?
Click to expand...
Click to collapse
I'm not sure. Normally I access download mode using volume up and power button. The download mode was there for a sec and then the screen back to
"Your device has failed a routine safety check and will not boot..."
again.
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
JanBoyGamer23 said:
Ah ok so now I understand.
But why don't you unlock your bootloader then if fastboot works? Do you know for sure that TWRP doesn't work?
I really want to help but I don't have a LG phone
Click to expand...
Click to collapse
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
JanBoyGamer23 said:
EDIT: The LG Bootloader unlocking page is "under construction". Guess you have to bring your phone to LG for them to fix this...
Click to expand...
Click to collapse
Unfortunately my LG V30 is US region. The official bootloader site not support my phone. Thanks for your info anyway
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
schwinn8 said:
I'm not sure why a Samsung user was recommended this post. And no offense to the Samsung user, but the process for unlocking, etc is VERY different for Samsung than it is for LG... so I recommend not worrying about that. Believe me, I know, because I'm researching switching to a Samsung in the future, and the process is very different!
That being said, the best resource here is the WTF thread with the post by ChazzMatt. That post has everything you need in one place.
jacoozie, the error you're getting indicates that you had a non-stock phone when you flashed the KDZ on an unlocked phone. For this reason, it's no surprise you got this error - the phone must be COMPLETELY STOCK for a stock KDZ flash. I'm guessing you had TWRP or something else installed, which is causing this problem. Once you unlock, you cannot just flash things willy nilly... and generally you don't flash with KDZ unless you're trying to change models (aka Frankenstein) or on the way to a custom ROM.
It sounds like you've done some unlocking rooting... if so, I recommend you start over with the WTF thread, read it VERY CAREFULLY and ENTIRELY and then reflash as instructed there. I'm guessing you may need to go back to KDZ Nougat and then work your way forward. If you have questions, ask in that thread... but you shouldn't have any questions as the thread is VERY complete (been updated all the time with very detailed information, so everything is in there).
Click to expand...
Click to collapse
Thanks for the reply.
I didnt install TWRP or any recovery tools to my phone. My phone bootloader still locked thou.
I have read the WTF thread but the problem is I cant get into my Download mode.
Ok, what steps are you using to try to get into download mode? Presumably turning off the phone, then holding the volume up button and plugging in the USB cable (other end already connected to a Windows computer), correct? If that doesn't work, can you try other USB cables? Sometimes a bad cable could prevent the phone from going into download mode.