Related
I have been searching for the stock USA rom to put my Defy back to stock and I can't find it, I need to send it back to do a warranty exchange...please help, thank you
http://and-developers.com/sbf:defy
go to the above link..u will find all kinds of sbf
arpith.fbi said:
http://and-developers.com/sbf:defy
go to the above link..u will find all kinds of sbf
Click to expand...
Click to collapse
Great, how do I flash one of this to my phone?
Und3r6r0und said:
Great, how do I flash one of this to my phone?
Click to expand...
Click to collapse
Via RSD Lite. You can download it from here: http://forum.xda-developers.com/showthread.php?t=1100585 ( drivers are embedded in the zip )
Download and install Motorola Defy driver
- Download and install RSD Lite
- Open RSD Lite
- Enter Bootloader Mode on you phone (Power+VolUp)
- Connect phone to you PC (USB)
- Open RSD - Lite
- Flash new SBF
arpith.fbi said:
http://and-developers.com/sbf:defy
go to the above link..u will find all kinds of sbf
Click to expand...
Click to collapse
every time I try to unzip it says is corrupted, I have downloaded it twice...no luck so far =(
http://forum.xda-developers.com/showthread.php?p=11588065#post11588065
this link is from this forum..hope this will work
it keeps failing.... I downloaded another rsdlite and I still have the same issues, I wonder what the problem is.
There are a few things you can try to resolve that issue.
-Try different versions of RSD lite. Usually the latest 5.0 works.
-Try admin mode and/or compatibility mode.
-Try US eclair and froyo sbfs.
-If you have another PC try both xp and 7. one will work.
Remember - depending on how you installed your custom Rom you may not be able to "downgrade" back to the official Rom that you require. So if you have installed a 2.2. Rom and didn't use the fixed sbf method then you will not be able to flash back to the official 2.1 Rom. Likewise if you flashed the leaked 2.3 Rom without using the fixed sbf method then you can't go back to a 2.2 Rom.
capnkillem said:
There are a few things you can try to resolve that issue.
-Try different versions of RSD lite. Usually the latest 5.0 works.
-Try admin mode and/or compatibility mode.
-Try US eclair and froyo sbfs.
-If you have another PC try both xp and 7. one will work.
Click to expand...
Click to collapse
Another computer worked like a charm, same OS Win7, weird.
Thank you everybody for helping out.
You are welcome sir! I have gone though this alot. Just sent my defy in I had to get back to stock. I practically completely bricked it. Desktop win7 wouldn't flash sbf but laptop win7 would. Was getting stuck at flashing group 33 at 3%.
Sent from my MB525 using XDA App
Thank U Arpith.fbi!
I had to unroot and reclaim my sh**ty stock apps to install the recent US froyo update and found this thread. First time using RSD Lite, worked flawless. Thanks for the link to the sbf's. Tried #26 first and upon reboot it stuck my phone in an "m" screen loop. removed the batt, sim, and sd,... replaced... then phone wouldn't even show a sign of life. Got the white LED upon usb connection and that was it. RSD Lite still managed to flash it with sbf #25 and I was booted back to my defy with all my data except unrooted and all those crappy apps back. Installing official froyo update now and no more exclamation point!!! Gonna root again with superoneclick, hoping this will be my last update battle on the defy. Thanks again
Super long story short. Didn't backup EFS.. I can't wipe phone with KDZ not sure whyvalwya sfails
Anyway no matter what ROM I use modem sucks keeps dropping signal and freezes a bit. I have tried flashing c/m/r/b modems and either they don't work or random disconnected
I need this fixed....and last time I flashed stock B that did work modem was as fast as 3G
quick question with kdz are you plugging the usb cable in a USB 3.0 connection? I know that causes issues
vel0city said:
quick question with kdz are you plugging the usb cable in a USB 3.0 connection? I know that causes issues
Click to expand...
Click to collapse
i have onboard usb3 and a front card reader section which i believe has USB2
But this docent explain every rom not being able to stay connected to the network
enzodad said:
i have onboard usb3 and a front card reader section which i believe has USB2
But this docent explain every rom not being able to stay connected to the network
Click to expand...
Click to collapse
Yeah I am just wondering since you said KDZ failed for you. Switching to the usb 2.0 might fix your KDZ fails. KDZ with the 20b to stock lollipop, then root it and get twrp. Then flash Blisspop and that should fix your modem issues where you don't get 4g lte or 4g lte is not sticking. From there you can flash what ever rom you want. So after a successful KDZ flash just follow my instructions here:
http://forum.xda-developers.com/tmobile-lg-g3/help/lte-lollipop-issue-fix-t3075637
I'll try your method is there a Linux way to KDZ? I tried KDZ on every USB port two different windows 7 installations. Tot works never KDZ
Also I super appreciate you helping me lol I'm about to run over phone with suv
enzodad said:
I'll try your method is there a Linux way to KDZ? I tried KDZ on every USB port two different windows 7 installations. Tot works never KDZ
Also I super appreciate you helping me lol I'm about to run over phone with suv
Click to expand...
Click to collapse
Unfortunately I do not know a Linux version for KDZ. When you are using the LG flash tool you did install the drivers correctly and have usb debugging on and all that? Plus make sure your computer recognizes your phone and you are able to access it via mtp, where you are able to access the internal sd and your external sd card from your computer. If that works, then shut down phone, hold the volume up button while plugging in the usb cable to a 2.0 port. Once in download mode your computer should be installing another driver too access the phone via download mode. That is my experience with the LG flash tool and it works every time, and since I experience that LTE issue I used the KDZ method a lot of times and never failed. By the way, what is the error message you get on the LG Flash tool when you flash KDZ?
FYI.
If you want since you already have TWRP and Root just flash the Blisspop rom and flash the stock 20b stock image from my thread. Just ignore the KDZ or use TOT first then root it and get TWRP and flash blisspop, but either way try to flash the Blisspop 2.3 rom from April 4, 2015 and see if that works
vel0city said:
Unfortunately I do not know a Linux version for KDZ. When you are using the LG flash tool you did install the drivers correctly and have usb debugging on and all that? Plus make sure your computer recognizes your phone and you are able to access it via mtp, where you are able to access the internal sd and your external sd card from your computer. If that works, then shut down phone, hold the volume up button while plugging in the usb cable to a 2.0 port. Once in download mode your computer should be installing another driver too access the phone via download mode. That is my experience with the LG flash tool and it works every time, and since I experience that LTE issue I used the KDZ method a lot of times and never failed. By the way, what is the error message you get on the LG Flash tool when you flash KDZ?
FYI.
If you want since you already have TWRP and Root just flash the Blisspop rom and flash the stock 20b stock image from my thread. Just ignore the KDZ or use TOT first then root it and get TWRP and flash blisspop, but either way try to flash the Blisspop 2.3 rom from April 4, 2015 and see if that works
Click to expand...
Click to collapse
OKay im doing that now, I have all drivers i think im missing the one for download mode, that has to be it. i plugged phone in and switched between all settings make sure all drivers are on. Ill try get DL mode one on and flash Bliss and let you know here.
Thanks again for patience and help
enzodad said:
OKay im doing that now, I have all drivers i think im missing the one for download mode, that has to be it. i plugged phone in and switched between all settings make sure all drivers are on. Ill try get DL mode one on and flash Bliss and let you know here.
Thanks again for patience and help
Click to expand...
Click to collapse
Well the download mode should install the drivers automatically there is no extra drivers, but flash the Blisspop 2.3 rom and I really hope that should solve the issue
vel0city said:
Well the download mode should install the drivers automatically there is no extra drivers, but flash the Blisspop 2.3 rom and I really hope that should solve the issue
Click to expand...
Click to collapse
flashing now, one probloem my cheap ass has no internet just tether lol and when i put in DL mode i noticed ~!~ was there so no proper driver lol wtf-
enzodad said:
flashing now, one probloem my cheap ass has no internet just tether lol and when i put in DL mode i noticed ~!~ was there so no proper driver lol wtf-
Click to expand...
Click to collapse
Yup that would cause the issue with KDZ then
vel0city said:
Yup that would cause the issue with KDZ then
Click to expand...
Click to collapse
plugged in phone- not showing ! anymore but didnt install driver, installed Bliss the one you said to and on first boot crashed pulled batter crashed again said CM account or something stopped working can even turn screen on unless pull battery- cheateed and diddnt unlock phone just pulled down- had to change APN or wouldnt connect but now trying reboot then flash stock B see if work(follow insturctios)
enzodad said:
plugged in phone- not showing ! anymore but didnt install driver, installed Bliss the one you said to and on first boot crashed pulled batter crashed again said CM account or something stopped working can even turn screen on unless pull battery- cheateed and diddnt unlock phone just pulled down- had to change APN or wouldnt connect but now trying reboot then flash stock B see if work(follow insturctios)
Click to expand...
Click to collapse
Hmm that is wierd flashing the Blisspop rom and have it crash. Never came across anyone with that issue yet. When you flash Blisspop did you wipe everything beside the external SD card in Twrp before installing the rom?
vel0city said:
Hmm that is wierd flashing the Blisspop rom and have it crash. Never came across anyone with that issue yet. When you flash Blisspop did you wipe everything beside the external SD card in Twrp before installing the rom?
Click to expand...
Click to collapse
yes ill try one more time, NOOB question if it works im going to flash Stock B~ should i full wipe again or dirty over Bliss, and i know bliss hates me, i installed a version 4 days ago and it worked for 20 min or so then deceided it wanted to optimize apps over and over and over lol i
ANd im trying KDZ again i forgot no EX SD card but good news KDZ is working now so ill do that twrp su install Bliss and get back to you im a tard sometimes
enzodad said:
yes ill try one more time, NOOB question if it works im going to flash Stock B~ should i full wipe again or dirty over Bliss, and i know bliss hates me, i installed a version 4 days ago and it worked for 20 min or so then deceided it wanted to optimize apps over and over and over lol i
ANd im trying KDZ again i forgot no EX SD card but good news KDZ is working now so ill do that twrp su install Bliss and get back to you im a tard sometimes
Click to expand...
Click to collapse
You can wipe it if you want.
vel0city said:
You can wipe it if you want.
Click to expand...
Click to collapse
So i KDZ R back on because B was **** lol any way no network but after 3/4 restarts from rooting it was on, then off lol so i set to 2g changed APN and now seems working great
so far zero drops or freezes, Flashed Prime Tether and will test through the night.
I beleive flashing the bliss pop did the trick
Are you getting LTE service on R? I could not get LTE back on R once I went to 20b but never rooted or flashed Blisspop.
enzodad said:
So i KDZ R back on because B was **** lol any way no network but after 3/4 restarts from rooting it was on, then off lol so i set to 2g changed APN and now seems working great
so far zero drops or freezes, Flashed Prime Tether and will test through the night.
I beleive flashing the bliss pop did the trick
Click to expand...
Click to collapse
Good news man, hope it continues to work for you man
huntnyc said:
Are you getting LTE service on R? I could not get LTE back on R once I went to 20b but never rooted or flashed Blisspop.
Click to expand...
Click to collapse
Yup i do and not one hiccup. It took a few min but it was worth it. Stable 4glte fast tether
huntnyc said:
Are you getting LTE service on R? I could not get LTE back on R once I went to 20b but never rooted or flashed Blisspop.
Click to expand...
Click to collapse
Flash the blisspop rom and it should fix the lte issue. Just remember to back up your current rom via twrp. Then flash the blisspop rom, once confirmed 4g lte is stable restore backup and you should be good to go with no hassle of setting up new phone.
vel0city said:
Flash the blisspop rom and it should fix the lte issue. Just remember to back up your current rom via twrp. Then flash the blisspop rom, once confirmed 4g lte is stable restore backup and you should be good to go with no hassle of setting up new phone.
Click to expand...
Click to collapse
Thanks will try if needed but I had no LTE problems after KDZ 20b without root for now.
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
what varient do u have
Click to expand...
Click to collapse
My computer recognizes the phone, that's not the problem. It's purely the program, I can't run it. It doesn't open.
i see try older versions of the program try googling lg flash tool do you have the megalock.dll
---------- Post added at 03:45 PM ---------- Previous post was at 03:42 PM ----------
im sorry i just really read in full i had the issue to when i upgraded to win 10 i ended up going back to win 7 too things just wernt going well with 10 also had trouble with flash tool always failing never restoreing i was a pain i thought i messed my phone up and it ended up bein win 10 my pc has the secure boot and crap on it it even makes it a pain to dual boot ubuntu up so i just run 2 machines on my tv
A Possible Solution
alwaysdiving said:
I rooted my G3 using iRoot while having Lollipop 5.0 installed. I have just received my update from LG for Marshmallow. When I tried to do the update it told me that my phone was rooted so I can't get it. I un-rooted my phone, and tried to put everything back to the way it was, but no go. They still said my phone is rooted. The problem is that I can't do a hard factory reset. I get a message "secure booting error ...".
So after reading up on it a bit, I realized I needed to flash a stock ROM through my computer. I downloaded all that I needed, and installed LG Flashing Tool 1.8.1.1023 on my Windows 10 computer, following all the directions exactly (including replacing MegaLock.dll). The program installed, but when I wanted to run it, it told me that it couldn't find MegaLock.dll, and then asked for an ID and Password. I uninstalled it and reinstalled it many times using slightly different versions, but I had the exact same problem each time. Then I decided to try and install it on a Windows 7 machine, and it worked. So it seems that something is keeping it from working on the Windows 10 computer. Can anyone help me with this, or maybe there is another way? Maybe the dll file has to be placed somewhere else? Maybe a different MegaLock.dllis needed that is compatible with Win10? Maybe a different program? I have no idea. Any and all help would be appreciated.
Thank you.
Click to expand...
Click to collapse
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Abort said:
I had problems with LG Flashing Tool the first time I tried to flash stock after upgrading my system OS to Windows 10. I finally got it to work by changing the compatibility mode for application file to Windows 8. I successfully flashed back to D85510L_00.KDZ after making the change I just mentioned.
Click to expand...
Click to collapse
Thanks, but I tried that already. Didn't work. In the end I transferred everything to my wife's Windows 7 computer and and did the flashing there. Everything ran as smooth as can be.
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Shipoftheline said:
Delete the cache in recovery if all else fails it should fix whatever the conflict is
Click to expand...
Click to collapse
I can't enter to recocery after flashing android 13
Kirya27 said:
Hi all.
Maybe someone came across.
I update by ota to Android 13, the phone starts to reboot or gets stuck in the bootloop, stops entering the recovery and fastbootd. The bootloader from 13 is flashed on both slots, the full factory image does not get up due to the inability to boot into fastbootd. And even if the firmware still succeeds, the phone either boots into the firmware for 5 minutes and goes into reboot, or even hangs on the Google logo.
Moreover, if after that you flash it via fastboot to the 12.1 developer for the new bootloader, the phone loads and works completely properly, enters all partitions, does not reboot.
If i run Android 13 using DSU through the 12.1 developer, everything also works fine, without any problems
I tried all options of flashing android 13. And the full image, and ota by air, and ota through sideload recovery - always the same result.
What could be the reason, has anyone encountered and how can this problem be solved?
Click to expand...
Click to collapse
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Lughnasadh said:
First make sure you don't have any other/older versions of adb/fastboot tools on your computer, just the latest Platform Tools. Also try using an A to C cable using USB 2.0 port. Then try flashing the factory image again or using Android Flash Tool.
Click to expand...
Click to collapse
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Kirya27 said:
How is a bad cable connected or an old version platform-tools with the fact that after flashing the bootloader and some more files of the 13th version, my recovery, fastbootd and system stops loading and constantly reloading?
Click to expand...
Click to collapse
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Lughnasadh said:
You need the latest Platform Tools to properly flash everything. Many people have found that when having problems flashing that switching to an A to C cable using USB 2.0 solved their problems.
Click to expand...
Click to collapse
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Kirya27 said:
This doesn't solve my problem. I always use the latest version of platform-tools or flash through Android FlashTool. I tried different cables, and think logically how this could be the case if Android 12.1 installed and working without any problems?
Click to expand...
Click to collapse
Well, you didn't mention you were using the latest Platform Tools, so I suggested it as that's one of the 1st steps of troubleshooting in these situations. You also didn't specifically mention using Android Flash Tool, so I suggested that as well.
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
This sounds interesting. I'll try it today when I get home and post the results here.
Gytole said:
Are you flashing BOTH SLOTS with the flash tool? Use Pixel Flasher and force flash both slots SEPARATELY don't choose the "both slots" button, it usually bricks for me. But see if thay fixes your problem. I couldn't use the android flash tool since about February of this year.
And since you did the OTA it might be a good time to bite the bullet and wipe if you haven't.
Click to expand...
Click to collapse
I tried the method that you described and indeed, for some time the phone worked on Android 13 (however, when it was turned on, it wrote that this device was suddenly damaged due to something, photo below). True, after 15-20 minutes of use, phone rebooted into the bootloop, just for no reason at all. I flashed exactly as you said, separately in each slot ...
I have had this screen when I soft bricked after flashing lineage os. I fixed it with flashtool. My exact setup is windows 11, flashtool through Microsoft edge with the options to force flash and wipe device checked in flashtool. Flashtool has rescued my p6pro many times with this setup.
fil3s said:
У меня был этот экран, когда я завис после прошивки Lineage OS. Починил флештулом. Моя точная настройка — это Windows 11, flashtool через Microsoft Edge с параметрами принудительной прошивки и очистки устройства, отмеченными во flashtool. С помощью этой настройки Flashtool много раз выручал мой p6pro.
Click to expand...
Click to collapse
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Kirya27 said:
I've tried this method many times. Exactly the same as you described. Either the phone simply did not start, or it loaded, but rebooted into an eternal reboot after 15 minutes
Click to expand...
Click to collapse
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
fil3s said:
If it happened to me. Idk. I think I'd fastboot -w in fastboot then try while still in fastboot
Click to expand...
Click to collapse
I tired fastboot -w many times
Kirya27 said:
I tired fastboot -w many times
Click to expand...
Click to collapse
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
fil3s said:
Sorry if it sounds stupid.. but have you tried flashing a custom rom? Fastboot -w, fastboot update "customrom.zip" to see if they boot? Try paranoid android
Click to expand...
Click to collapse
Tried. It turns out the same as on the stock firmware
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
apis903 said:
I have faced this issue and the only solution is by sending it to the service center. They said it is the system issue and they replaced mainboard with a new one. And yeah. They said it is not related to android 13 update
Click to expand...
Click to collapse
They clearly designed these phones to fail. They implied they would be usable for 6 years, but like all previous google phones, it will brick itself within 2. This 6 Pro is definitely the last product I buy from Google. I've had 3 other Nexus/pixel phones, none of which lasted. My sister is still using my hand-me-down iPhone 7 that I dropped off a cliff.
I can't do iphones though, and I don't want to support slave labor.. so my options are extremely limited. I'm only going to buy smartphones produced in the USA. It's dangerously cheap to produce phones using the less strict labor and material laws of foreign countries, phones are being treated as disposable, which is unacceptable. My modified Nexus 5X is perfectly usable despite having half the CPU disabled and being a 7 year old phone, thanks to overclocking. Companies should not release a new device unless it is a worthy upgrade over the previous one. It should happen every 3 years, not every year.
I just hope other nerds wake up and stop supporting Google. We have to boycott Google until they create desirable products. Pixel is so undesirable that they spend their ad money on woke bull**** that no one cares about except the sheep, but they like iPhones. Google is just burning our money and ignoring our needs.
Edit: I'm just salty that I got scammed by Google. They lost all of their people who cared. Google is full of corrupt people who want to make a buck. Pixel 7 is essentially the exact same as Pixel 6. The lack of a pro mode in the camera app perfectly represents Google's priorities. It would take one developer a couple days to add such a feature to the app. Google is not doing ANYTHING good.
Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!
Slim2none4u said:
Ptxel 2xl. Stock. I can root and i can flash stock firmware. I have used productpartition-pixel2xl-extended.zip. I have changed cables and insured the google drivers are installed. On the same PC i can flash custom roms on my 3xl 4a5G 6Pro and 7Pro.
I have flashed the latest stock to both slots and done a factory reset to bith slots. I just can not get a rom to flash. I can flash partitions individually like vbmeta and boot and system. Can't get a rom to go.
I have tried all the recoveries that come with the roms and also i have tried several versions of twrp and PBRP to no availl.
Any ideas would be great. Not a noob but this has me stumped. I wil even mail it to someone that thinks they can get it flashed with a custom rom! lol
Ideas?
And.........GO!
Click to expand...
Click to collapse
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.
I know you've already tried, but these two things are practically always the problem:
1) Using a new USB port on the computer. USB-C is particularly problematic.
2) Wrong drivers. The PC can use different drivers depending on whether the phone is in normal, bootloader or recovery mode. So you need to check your drivers while the phone is in recovery.
Arealhooman said:
Doubt I can help you here, but mailing it would not be a good idea, using remote control software could be smarter.
Click to expand...
Click to collapse
Yeah not sure i really would mail it although it just a $50 toy and thats why i bought it...kind of a google fan boy and want the box set lol
Remote software would work and i would be willing as there is no sensative data on this PC.
But who would be willing?
Have you tried PixelFlasher
Arealhooman said:
Have you tried PixelFlasher
Click to expand...
Click to collapse
Only to flash stock and to root. Most roms are a sideload updates and i can't figure out how to use PF to do custom roms.
I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.
zpunout said:
I had the same issue in recovery mode. I resolved it by buying a USB hub and connecting the phone through that.
Click to expand...
Click to collapse
I have a hub...may give that a try. Haven't touched the phone for a while now.