Related
Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.
hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
bro do u find solutions for this
I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!
jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.
I was trying to update with LGUP application for firmware update but didn't success, so I removed the USB cable and pressed Volume down and power button to restart. But it went straight into Firmware Update and LGUP application can't find the port.
So, my phone is stucking in Firmware update screen, please help me how to restore the firmware and get out from Firmware Update screen, many thanks and greatly appreciated.
Hold the power button until you get a black screen. Download LG Mobile Support tool and the LG Drivers. Plug USB In and then hold the Power + Volume Up key. On your screen, click Upgrade Recovery. From there, you can do a factory reset through download mode of your phone.
Enter download mode and connect the phone in the PC. Download LG brige and open it. When you are inside the programe you will see a window of Software update enter here and there is an option that is for bad installation otas (to reinstall and correct errors). Use this and I think this will handle.
Another option I think is using LG Up you will see your device in download mode. Try to enter download mode and see if this works also.
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
In older LG phones work LG Flashtool (2014)...Maybe with this you can flash KDZ firmware https://forum.xda-developers.com/showthread.php?t=2797190
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
I have the same issue - I was on Lineage os and flashing the OTA update caused bootloop to recovery. So I wanted to flash back to stock using LGUP and 14A. I did that before without issues.
This time though all installed fine but after reboot the phone immediately goes to fastboot, exactly as described above. I just spend several hours trying to fix it but with no results. The LG Bridge won't recognize the phone no matter what I do in Windows (tried 3 different PCs). On a Mac it will start connecting and will end up saying "you need to enable MTP connection".
From what I garther the stock rom flashed fine - the factory reset works, even shows "erasing data", the LG UP recognizes the phone as 14A (I tried 11A, 13A too - seems to install fine but goes immediately to fastboot after reboot).
The only thing I realized I did different when flashing the stock rom with LGUP was not using the original LG USB cable. But reflashing with original cable makes not difference now - still going to fastboot.
Any help would be greatly appreciated.
Have you guys been able to do the Upgrade recovery in the LG support tool? Did it work? It starts fine for me but after downloading the recovery file I always get and error, see the screenshot.
I was able to grab the kdz file and tried to flash it with LGUP but still the same thing. It seems like it flashes fine but after reboot it immediately goes to fastboot
kloubik said:
Have you guys been able to do the Upgrade recovery in the LG support tool? Did it work? It starts fine for me but after downloading the recovery file I always get and error, see the screenshot.
I was able to grab the kdz file and tried to flash it with LGUP but still the same thing. It seems like it flashes fine but after reboot it immediately goes to fastboot
Click to expand...
Click to collapse
Sadly I'm in the same boat as well. I'll pull some of their error messages I've gotten with LG Flash Tool this afternoon. I've tried 2014 and 2017. Both to no success.
I suspect it may be something with the /misc partition. Im going out on a limb, but I'm guessing that the AOSP and Lineage ROMs may touch misc. That partition may have some key identifiers for the LG tools. And the KDZ doesn't have a misc partition embedded inside it.
I was hoping the kdz file I was able to grab from the Lg Support tool would be different from regular stock rom 14a that is available around the internet but it appears to be exactly the same file (based on the file size). My original hope was that the file would support "Refurbish" option in the LGUP tool but it only works with "Upgrade".
I wonder if the "Refurbish" option would fix this and re-flashed all partitions - if only we could find a kdz file that would work with the refurbish option. So far all files I tried (11a, 13a, 14a) only support the upgrade option.
Thanks for all of your helps, I used LGUP and WondersMobile application on the computer and LGUP can not see the port. I did un-install the WondersMobile and LGUP can see the port and finally upgraded to latest firmware.
gewecht said:
Thanks both - I ran into a similar situation. I pulled down both the 11a and 14a KDZ files, and used UpperCut and LGUP to flash first the 14a and then the 11a image. Unfortunately in both cases after LGUP does its thing, I'm getting the LG logo, followed by fastboot screen.
I cannot reboot to get past it, and I cannot flash recovery (it says the boot loader is locked). I cannot flash the Unlock.bin from LG because apparently the KDZ re-enabled the software lock prohibiting bootloader unlocks.
So I'm suck with a phone that will only boot into fastboot, stock recovery or into download mode, and I cannot figure out how to get back to something functional. I've tried reflashing with LGUP - that doesn't work. And the LG Bridge "Update Error Recovery" option gives an error "Connect your mobile device to the USB Port" even though it is, and the LG USB drivers are installed.
Would appreciate any pointers someone could offer.
Click to expand...
Click to collapse
kloubik said:
I have the same issue - I was on Lineage os and flashing the OTA update caused bootloop to recovery. So I wanted to flash back to stock using LGUP and 14A. I did that before without issues.
This time though all installed fine but after reboot the phone immediately goes to fastboot, exactly as described above. I just spend several hours trying to fix it but with no results. The LG Bridge won't recognize the phone no matter what I do in Windows (tried 3 different PCs). On a Mac it will start connecting and will end up saying "you need to enable MTP connection".
From what I garther the stock rom flashed fine - the factory reset works, even shows "erasing data", the LG UP recognizes the phone as 14A (I tried 11A, 13A too - seems to install fine but goes immediately to fastboot after reboot).
The only thing I realized I did different when flashing the stock rom with LGUP was not using the original LG USB cable. But reflashing with original cable makes not difference now - still going to fastboot.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
I too am having same problem. I've tried all the images from 11A to 14A, all of them flash with no errors on LGUP and every time LGUP detects the phone as having the last version flashed. Unfortunately, the phone also boots to fastboot every time. Nothing else to add to your descriptions at this time I'm afraid...
gewecht said:
Sadly I'm in the same boat as well. I'll pull some of their error messages I've gotten with LG Flash Tool this afternoon. I've tried 2014 and 2017. Both to no success.
I suspect it may be something with the /misc partition. Im going out on a limb, but I'm guessing that the AOSP and Lineage ROMs may touch misc. That partition may have some key identifiers for the LG tools. And the KDZ doesn't have a misc partition embedded inside it.
Click to expand...
Click to collapse
I am absolutely positive my problem is at least in part due to a messed up /misc partition though. @gqo actually described what I did pretty thoroughly in his thread, albeit in a G5. Post #9 has the fix but it didn't work for me.
I've also stumbled upon a menu under the Firmware Update screen that I had never seen before and cannot fin any mention to... Would any of you guys know what it is for? It reads something like:
Code:
** SELECT MENU **
** Select : Power Key(Long) **
** Move : Power Key(Short) **
-> MA-USB(WIFI) DL
POWER OFF
PHONE INFO
BACK
Okay, I figured it out. The menu, at least the first option, appears to be for Wi-Fi firmware update. I wonder what file the phone actually downloads... And if it would be able to fix our phones. The only unprotected network I had in hand was a mobile hotspot in my not-so-LTE Nexus 5, so I got as far the firmware download start but didn't risk it on such a slow and unpredictable network. On top of that my Nexus 5 has also gotten pretty good at bootlooping, that's why I got this G6 in the first place. If anyone out there has a reliable unprotected network and nerves of steel it could be interesting to see if the outcome of this update is different from the LGUP one.
How do you access this menu?
What I started working on yesterday is trying to build a image file for the Qualcomm Flash Image loader and see if I can flash the phone using this tool... But I have never used this tool before, right now it does not detect my phone - I need to work on that + see if I can correctly build the image file from kdz. I found some youtube step by step tutorials so we will see. I will post update on the progress tonight or tomorrow.
kloubik said:
How do you access this menu?
What I started working on yesterday is trying to build a image file for the Qualcomm Flash Image loader and see if I can flash the phone using this tool... But I have never used this tool before, right now it does not detect my phone - I need to work on that + see if I can correctly build the image file from kdz. I found some youtube step by step tutorials so we will see. I will post update on the progress tonight or tomorrow.
Click to expand...
Click to collapse
I'm not sure if there's a better way to do it, but I access it by removing the usb cable after I successfully get in Download Mode. Then I'm not sure if there's any specific key combo, I've been randomly pressing the power and the volume down buttons and at some point I get into that menu. In the menu though, for some reason, I think I can only select an option if I long press both the volume down and power buttons. The "POWER OFF" option has come in handy because so far is the only way I can actually turn my phone off. The "PHONE INFO" hasn't worked for me yet. The menu also reacts when you add/remove the microsd card... I wonder if it can be used for something other than a WiFi firmware upgrade. I haven't had the chance to connect the phone to a computer to see how the device is recognized, if at all.
And that image you're working on sounds like a neat idea, I wish I could help but I'm afraid I wouldn't have the skill. I may be able to test though. Anyway, Godspeed!
Unundra said:
I too am having same problem. I've tried all the images from 11A to 14A, all of them flash with no errors on LGUP and every time LGUP detects the phone as having the last version flashed. Unfortunately, the phone also boots to fastboot every time. Nothing else to add to your descriptions at this time I'm afraid...
I am absolutely positive my problem is at least in part due to a messed up /misc partition though. @gqo actually described what I did pretty thoroughly in his thread, albeit in a G5. Post #9 has the fix but it didn't work for me.
I've also stumbled upon a menu under the Firmware Update screen that I had never seen before and cannot fin any mention to... Would any of you guys know what it is for? It reads something like:
Code:
** SELECT MENU **
** Select : Power Key(Long) **
** Move : Power Key(Short) **
-> MA-USB(WIFI) DL
POWER OFF
PHONE INFO
BACK
Okay, I figured it out. The menu, at least the first option, appears to be for Wi-Fi firmware update. I wonder what file the phone actually downloads... And if it would be able to fix our phones. The only unprotected network I had in hand was a mobile hotspot in my not-so-LTE Nexus 5, so I got as far the firmware download start but didn't risk it on such a slow and unpredictable network. On top of that my Nexus 5 has also gotten pretty good at bootlooping, that's why I got this G6 in the first place. If anyone out there has a reliable unprotected network and nerves of steel it could be interesting to see if the outcome of this update is different from the LGUP one.
Click to expand...
Click to collapse
I'll play around a bit and see if I can land on this menu. At this point I'll try anything. I'm on an iPhone until I get this fixed - so I'm motivated!
I can setup an open guest network off my main wi-fi this evening and see what I can find out.
EDIT Sorry, I tried playing around here, but I couldn't figure out how to get back into the the menu you uncovered. If you could give some instructions on how to do it, I'm happy to give it a shot on my device.
I was able to access the menu today...what worked for me was at the firmware screen unplug the usb cable and then press volume down and power button three times quickly. I tried to connect to a wifi and it does not really do anything. I think it just establishes wifi connection but it does not download anything on it's own - it's waiting for another connection.
Also I got stuck with building the image file from kdz, it has no information on partitions. At this point I decided to ship to LG for a quote and will see how much they will ask for a reflash.
I got as far as selecting a network and getting some sort of a download start screen, but I interrupted it right away so I wasn't sure the download would actually go through... Apparently it does not. If this menu has some sort of flashing capabilities though, it might be worth checking how secure it is. If someone can get it to download and flash a modded file perhaps there could be a chance of flashing a custom recovery or something... I'm thinking about those guys that have an unlockable bootloader (which we ironically also have now).
Anyway, all of this goes well beyond my skill so I followed your example and submitted a repair service request to LG. It'll take quite long but shipping is free, so I figured I'd give it a try. I'm assuming this is an easy fix with the right software tools, so I hope LG doesn't overcharge for it. I'm even half hoping they'll do it under the limited warranty... If I recall correctly unlocking the bootloader doesn't immediately void all warranty, there's room to prove the bootloader was never actually unlocked. And after all LG does say that once unlocked, it cannot be undone and our phones are, in fact, running stock firmware and have a locked bootloader.
Update: My phone was received today by LG. In LG's Track Repair page, the status briefly showed as Undergoing Diagnostic but quickly moved to Repair In Progress, it's current status. Given that LG was supposed to contact me in case the repair was not covered by the limited warranty, meaning that an extra fee would've to be paid, I'm assuming the phone will be fixed (if possible, that is) free of charge. I will update you guys again soon, but if anyone out there is still struggling with this issue I'd recommend considering sending the phone to LG.
I have the exact same problem. Please keep us in the loop of what happens to your phone with LG
My phone has been received by LG for this issue on 9/26. It quickly moved through diagnostic to "repair in progress" on the first day plus showed ETA back to me in 6 business days. Ever since that it's stuck in that mode, no update or contact from LG. I check the status every day - every day it says the same - ETA 6 business days. It's been a week and half now with no update. I kind of expected it's going to take 2-3 weeks but annoyed that they say 6 days ETA and then you don't hear from anyone for almost 2 weeks with no change in status.
Update #2: The status finally moved to Shipped To Customer. I haven't been contacted by LG yet, so I guess the phone could've been shipped fixed as much as it could've been shipped as is for being unfixable. Either way, I wasn't and most likely won't be charged. FedEx hasn't got an ETA for the delivery, but I'll let you guys know as soon as I get my phone back.
Edit: Got an e-mail from LG. It reads something like:
Defect: Software failure
Payment Type: NOT APPLICABLE
Repair Results: S/W upgrade (download)
Repair Cost: $ 0.00
Warranty Status: In Warranty
Tax: $ 0.00
Total: $ 0.00
I guess I got away with it, I hope you guys do too.
Sent from my Nexus 5 using Tapatalk
BIG BREAKTHROUGH (at least for myself) :
So for some time now, I've thought that I had hard-bricked my
dwycoff2013 said:
BIG BREAKTHROUGH (at least for myself) :
So for some time now, I've thought that I had hard-bricked my
Click to expand...
Click to collapse
BIG BREAKTHROUGH (at least for myself) :
So for some time now, I've thought that I had hard-bricked my moto XT1609, and I thought what I needed would be best summarized with the words 'blankflash template'. This sent me on a furious wild goose chase for Qualcomm drivers, deactivating driver signature enforcement on a Windows computer, etc., etc. . . You catch my drift. Well, long story short, I ended up coming across another XT1609 (same variant) and since the charger port and screen were all effed up, I just changed out the motherboards and viola! I had my G⁴ Play back in working order. I rooted with auto-init root, and everything was working fine. I took the battery out after powering down, placed my sim and microSD card, and upon attempting the boot, I panicked. It was doing the same thing the last motherboard was doing: showing the "moto" boot screen, vibrating, then black screen, a flash, and it looped. I couldn't load recovery nor kernel. So, I tried to uninstall the init root, and attempted boot, but to no avail.
I was certain all was lost.
However, after reading the PDF of the essay where the bootloader vulnerability was discovered, I decided to utilise fastboot in hopes of saving the kernel from crashing (i assumed the black screen, and the flash was the bootloader attempting to load the kernel). My commands:
fastboot oem config fsg-id vzw (I have the vzw variant)
fastboot oem config carrier vzw
fastboot continue
And success! I saved the kernel from crashing. I urge anyone else having the same problem I described to try fastboot commands using your carrier's id in lieu 'vzw' and let me know the results, please!
Sent from my resurrected vzw xt1609
P.S. I also just had the same problem with this phone again, however this time I set the carrier id blank (as it were from the factory) and let the fsg-id be set by the auto-init root script..
Anyone (senior/recognized members) have any input on what's actually going on here? I'd love to actually be aware of what I'm changing and how it's affecting the boot.
dwycoff2013 said:
BIG BREAKTHROUGH (at least for myself) :
So for some time now, I've thought that I had hard-bricked my moto XT1609, and I thought what I needed would be best summarized with the words 'blankflash template'. This sent me on a furious wild goose chase for Qualcomm drivers, deactivating driver signature enforcement on a Windows computer, etc., etc. . . You catch my drift. Well, long story short, I ended up coming across another XT1609 (same variant) and since the charger port and screen were all effed up, I just changed out the motherboards and viola! I had my G⁴ Play back in working order. I rooted with auto-init root, and everything was working fine. I took the battery out after powering down, placed my sim and microSD card, and upon attempting the boot, I panicked. It was doing the same thing the last motherboard was doing: showing the "moto" boot screen, vibrating, then black screen, a flash, and it looped. I couldn't load recovery nor kernel. So, I tried to uninstall the init root, and attempted boot, but to no avail.
I was certain all was lost.
However, after reading the PDF of the essay where the bootloader vulnerability was discovered, I decided to utilise fastboot in hopes of saving the kernel from crashing (i assumed the black screen, and the flash was the bootloader attempting to load the kernel). My commands:
fastboot oem config fsg-id vzw (I have the vzw variant)
fastboot oem config carrier vzw
fastboot continue
And success! I saved the kernel from crashing. I urge anyone else having the same problem I described to try fastboot commands using your carrier's id in lieu 'vzw' and let me know the results, please!
Sent from my resurrected vzw xt1609
P.S. I also just had the same problem with this phone again, however this time I set the carrier id blank (as it were from the factory) and let the fsg-id be set by the auto-init root script..
Anyone (senior/recognized members) have any input on what's actually going on here? I'd love to actually be aware of what I'm changing and how it's affecting the boot.
Click to expand...
Click to collapse
Hi, dwycoff2013
I'm trying to resurrect my locked bootloader vzn XT1609, as well. I don't think I have a hardware issue. I upgraded to Android 7.1.1 a month or so ago and it was running fine until a few days ago when it started bootlooping much in the way you've described. The blue splash screen comes up for 5 or 10 seconds then the screen goes black, then the blue screen comes up for 5 or 10 seconds, then it goes black, ad infinitum. Well, sometimes it actually goes farther, gets to the screen with the dancing colored dots before rebooting but this is very rarely. I tried installing the auto-init initroot image on it but it sends back a "Permission denied" error for it. I'm wondering if it's because I have 7.1.1 images installed instead of something older?
Anyway, your fastboot commands don't fix anything for me. It continues to bootloop. What version of Android were you running when you tried this?
Thanks!
I was using the 6.0.1 vzw firmware. Can you get to the bootloader with power and vol- ?
I'm assuming you can, considering you're mention of using the fastboot commands. Well, I'd say to install the QFIL & QPST tools, along with the Qualcomm Bulk HS-USB drivers. Once you get to the bootloader, try 'fastboot reboot edl' and it should put the device into Qualcomm's Emergency Download Mode and your computer should recognise the device as QC HS-USB 9008 DL, I believe. If that doesn't work, perhaps try taking the battery out, holding the vol+ button and inserting your USB cable.
dwycoff2013 said:
I'm assuming you can, considering you're mention of using the fastboot commands. Well, I'd say to install the QFIL & QPST tools, along with the Qualcomm Bulk HS-USB drivers. Once you get to the bootloader, try 'fastboot reboot edl' and it should put the device into Qualcomm's Emergency Download Mode and your computer should recognise the device as QC HS-USB 9008 DL, I believe. If that doesn't work, perhaps try taking the battery out, holding the vol+ button and inserting your USB cable.
Click to expand...
Click to collapse
Hi again, dwycoff2013
Sorry I haven't responded earlier. I had to finish my taxes and get my W10 boot working again. I was using Linux Mint in my previous attempts. I'm going to try and install the Qualcomm stuff you recommended but maybe you can answer a few more questions in the meantime:
1. My goal at this point is to get the stock Moto images running again. It appears that this is what you were able to do, from your description. Will running the Qualcomm utilities allow me to do this or will they only allow me to install Qualcomm images?
2. Do the Qualcomm utilities come with a version of fastboot that understand "reboot edl"?
3. My phone has a locked bootloader. I'm assuming that this is why my previous attempts to reflash failed. Can the Qualcomm utilites work when the phone is locked?
4. Can you point me to the pdf document that you were talking about?
Thanks. I'm sorry to sound like a newbie at this Android stuff, but this is what I am
So, basically I will make this short as possible
Due to some problems I had to sell my G6 Plus (Brazilian -8 model) but it was on a custom rom, and did the most dumb thing that I could do: Reflashing pure stock and locking it, I've used the LMSA tool then relocked in Fastboot, the thing is some files were corrupt and when locked, it doesn't boot up anymore, as i still had hope for it, I tried to LSMA again, but it doesnt recognize anymore, as the lock flag is now "Flashing_Locked", flashing manually via Fastboot gives a error related to the lock flag (also LSMA resets the device, so using my unlock key asks to enable OEM Unlock at settings, a impossible thing when OS is broken) , then searched for some solutions, first it was booting a Boot.img file from the last stock, which was the flashed one, it bootloops, then tried something on the recovery that works, but is the stock one and pretty limited, so the logical thing to do is flashing a OTA file, but only works for old versions that requires one version before the target one, so its a no go. The last thing i tried to do is booting TWRP, but it gets stuck on a red warning that indicates that system is corrupt. Then the last hope was EDL Mode, and thats the point where i want to go, i've bought a EDL Cable that's basically a green and black wire thing used on most Qualcomm based Redmi/Xiaomi devices, but it automatically boots to fastboot, so I need help to get EDL Test Points for this device, im with access to the board, i just need the right Pads to short-circuit it and blankflash it, so i can finally get it to work like normal again.
Schematics (for people who understands): https://androidfilehost.com/?fid=4349826312261726244
Any help is important, I'm sorry for some typos, english isnt my main language considering i didnt use translate
and please don't come with instructions like "have you tried LSMA?, try booting up the device and select oem unlock" because its clear that it doesnt work.
I bought a Motorola Moto C Plus a while ago so I can root it and play around with it. I tried to unlock the bootloader for a while on this phone but I just can't. Every guide I tried didn't work. From mfastboot to MTKClient.
mfastboot just gave "unknown command" when trying to get unlock data, and MTKClient couldn't detect a partition or something when trying to wipe.
Then I tried searching my serial number: ZW2224XFWW, but that gave no results. Not on Google nor on here. Can anybody help. I'm very new to the rooting scene.
EDIT: I have a Moto C Plus with 1GB RAM and 16GB internal storage
MTKClient works, download the live .iso file from https://github.com/bkerler/mtkclient
Boot from it, open a console and type:
pip3 install -r requirements.txt
First just follow the readme to unlock the bootloader and after that root with latest magisk. I just tested all that on a moto C, I don't have the exact model but it was the 8gb/1gb variant.
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
MarkPCExpert said:
Something's going terribly wrong because now it hangs at 43.8% while flashing boot partition and i dont know why
(I'm scared...)
Click to expand...
Click to collapse
After further investigation, this happens also at recovery and maybe also other partitions so now it is soft bricked
EDIT: it seems that the connection stops or something because after it fails flashing, i also cant do other operations. I NEED HELP!!!
EDIT 2: after trying the console instead of the gui, i discovered that it was never unlocked in the first place. It said "unknown seccfg partition header, aborting unlock"
You are going to know you have your bootloader unlocked if you see a white letters on black background message saying that the phone will boot in 5 seconds after turning it on. You can't flash anything with a locked bootlader.
THATS EXACTLY WHAT I'M GETTING!!! But still, i can't flash a single thing. and I dont know why. I tried to flash TWRP recovery to install a lineageos build but TWRP hangs at 88%. And the patched magisk thingy hung at 43.8%
Now the phone is kind of bricked.
EDIT: Maybe the hang is because i use USB 2 or the Live ISO on a not so good USB. I do use an upgraded Dell OptiPlex 3010 as my main machine. Or the hang is bcuz it failed to flash.
Reflash the original firmware and try again. If you did a backup just flash the original boot.bin
Welp. I am screwed. I forgot i was running a live USB so the entire backup is gone.
And the userdata was also empty for the most part.
Try this: https://www.motorola.com/us/rescue-and-smart-assistant/p
If that doesn't work see if you can find a stock firmware and flash with flash tool. https://androidfilehost.com/?fid=889964283620774903
I already tried that one, but when i plug it in, it doesnt do anything and I DONT KNOW WHY!
also im on vacation
UPDATE: im back from vacation and no replies, great...
BUT, ive chosen a mostly aosp based rom for the phone.