General My Moto G Stylus 2021 has a SD 675 despite being advertised as having a SD 678. - Moto G Stylus (2021)

So this is a weird issue. My G Stylus has a Snapdragon 675 even though it's advertised as having a 678. I verified it with CPUZ and Motorolas own help app that comes back with the model SM6150 on the CPU.
Can someone else confirm this?

Working on trying to blankflash my hard bricked unit and noticed some stuff that threw me off while trying to get phone in edl mode via edl points on motherboard. The main thing that stood out is the motherboard is labeled as 2113-1 which i believe is the Moto One 5g. Anyway, I found the edl points and was able to blankflash unit although I am still hard-bricked looking for solutions.
Currently trying to convert firmware files in order to flash them with QPST software. Any suggestions would be greatly appreciated.
*Bricked unit after trying to "Fastboot set_active b" after flashing firmware.

LunaTuna said:
Working on trying to blankflash my hard bricked unit and noticed some stuff that threw me off while trying to get phone in edl mode via edl points on motherboard. The main thing that stood out is the motherboard is labeled as 2113-1 which i believe is the Moto One 5g. Anyway, I found the edl points and was able to blankflash unit although I am still hard-bricked looking for solutions.
Currently trying to convert firmware files in order to flash them with QPST software. Any suggestions would be greatly appreciated.
*Bricked unit after trying to "Fastboot set_active b" after flashing firmware.
Click to expand...
Click to collapse
Are you able to share where the EDL points are loctated on this device?

ezril,
Here are the EDL test point locations to mount as Qualcomm 9008. If you find out how to successfully blankflash this unit please inform me. When I run a blankflash script it appears to be successful but never turns back on, only blinking led.
i've included the firehose programmer and also a script from my successful/unsecessful blankflash.

Chase Whittemore said:
So this is a weird issue. My G Stylus has a Snapdragon 675 even though it's advertised as having a 678. I verified it with CPUZ and Motorolas own help app that comes back with the model SM6150 on the CPU.
Can someone else confirm this?
Click to expand...
Click to collapse
Same for me model minsk_a

...SD678 is SM6150AC. Suffixes are just overclocks.

Related

Help with unbricking a hardbricked H631

Long story short, a kdz flash may have been interrupted. Now I am unable to boot my stylo at all. I can however see it under device manager, where it is labeled "Qualcomm HS-USB QDLoader 9008". Is there anything I can do to fix this?
I bricked mine and used LG Bridge to get to Lollipop and then I took the OTA to Marshmallow
Also, LG UP method can be used as well.
tube517 said:
I bricked mine and used LG Bridge to get to Lollipop and then I took the OTA to Marshmallow
Also, LG UP method can be used as well.
Click to expand...
Click to collapse
I kinda am stuck in this position too. Does LG bridge pick it up in this mode? Did you have that problem? I've been trying and it seems the only thing I can find is QPST using QFIL but then I can't seem to transfer the data and get an error about Sahara not being able to transfer the data over.
MrObvious said:
I kinda am stuck in this position too. Does LG bridge pick it up in this mode? Did you have that problem? I've been trying and it seems the only thing I can find is QPST using QFIL but then I can't seem to transfer the data and get an error about Sahara not being able to transfer the data over.
Click to expand...
Click to collapse
I have the MetroPCS version and totally screwed up messing around with something. I had no recovery. I had to use one of the methods to get it back up and running.
If you have the Tmobile or Metro version, you should be fine.
Did you have the same QDLoader 9008 issue?
LG Bridge doesn't appear to be working for me as it's not even detected.
Try LG Flash tool. That can get you back to Lollipop.
http://androidcreations.weebly.com/lg-g-stylo-update.html
Or LG UP method should work.
http://www.mylgphones.com/t-mobile-lg-g-stylo-h631-how-to-unrick-restore-back-to-stock.html (This is for the Tmobile version)
I can't actually access download mode, meaning neither of those options can detect my phone.
Wonkit said:
I can't actually access download mode, meaning neither of those options can detect my phone.
Click to expand...
Click to collapse
LG UP has an option that does not require download mode
I can't get LG UP to detect my device at all.
MrObvious said:
I can't get LG UP to detect my device at all.
Click to expand...
Click to collapse
Use a different USB cable. That's what happened to me. I had to try every single USB cable in my house, even from other phones.
AFAIK, in order to fix a hard bricked (Qualcomm HS-USB QDLoader 9008) lg stylo we need make something like this (http://forum.xda-developers.com/lg-...nbrick-g-stylo-ls770-qualcomm-hs-usb-t3368269) but for the H631/MS631 variant.
Can some of you look at THIS method used on LG V10 TMO variant for unbricking Qualcomm 9008?
I posted a thread HERE with the instructions from the user that created the backup and method to unbrick.
Hi, have the same qualcomm 9008 issue aftet kdz, so is there any solution?
So the brick is so bricked you can't even get to download mode.
Lg h631 hardbricked
Please any solution yet on this thread? I have had the same issue for a year now.
LGMS631 (MetroPCS LG G Stylo) Root/Unbrick/Recovery
So, I think I've managed to salvage my bricked Stylo, I somehow also managed to root my Fiance's LG G Stylo that's on the 6.0 update...
Since I can't find any ways to fix this problem on the internet I'll post what I did here so hopefully I can get some other people out of deep water with their phone.
Here is the thread I made I don't think it will work for a hardbrick, but it might be worth a shot..
LGMS631 MetroPCS LG G Stylo Backup (Unbrick/Root) Android 6.0
That won't work because your phone still works. You can boot past the 9008 mode.
So basically the phone is useless and can't be brought back to life at this point
I'm in the same position, flashed a lollipop kdz on a marshmallow and it effectively trashed the emmc. Without an insider leaking signed programmer and flasher mbns, flashing via sahara is not possible. For the moment, you need one of those expensive 20pin JTAG boxes and documentation for the ISP points(I can't find this info, it's paywalled). Under the shield facing the back of the phone is a header that may be for JTAG, but I haven't bothered probing as I don't think it's practical for unbricking.

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader

Strangest "Bricked" Oneplus One: No recovery, locked OS, can't unlock bootloader
Hi there, I've come in to the possession of the most stubbornly bricked phone that I've ever seen . Bought a OPO off Craigslist, someone cracked the screen and sold it for cheap instead of fixing it. It had been remote wiped but still has some strange difficult software. Posted this problem to the Oneplus Forum but have had no response, thought XDA would be more qualified!
From what I can tell it's a Oneplus One that was sold through a re-seller that replaced all the software on the phone with a high-security version of Android. It's called EncroChat and from their website (encrochat.network or encrochatsure.com) it looks like it removes the recovery from the phone and replaces it with an EncroChat OS (some kind of Cyanogen) that you can boot to in addition to the Android OS.
Well I assume during the remote wipe something went wrong with the software and the phone no longer really functions. It boots up fine but can't connect to Wifi, cellular, not detected when connected to my PC, and has no real apps to speak of. I think most of the device's drivers are missing. Trying to boot to recovery instead boots to their EncroChat OS which is locked behind a password that neither I nor the person I bought it from knows.
I can get to fastboot and my PC will detect the phone then but running the bootloader unlock command doesn't work, the phone just reboots into the locked EncroChat OS. My idea now is to try and hardbrick the phone and then re-do everything on the phone over again, but I can't figure out how to do that. Does anyone else have any ideas?
Contacting EncroChat
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
evronetwork said:
Had one GOOD soft brick in the past, I've used coloros rom(from the Chinese OnePlus One) and fix my phone ...it deleted all media of course but manage to unbrick the phone. Don't ask me how to, it's been a while, google it
It would fix even the most stubborn soft bricks you'll see. Before that I tried everything that was available at the time, no boot as well only fastboot(not even recovery)
Click to expand...
Click to collapse
broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
For your phone to be recognized in your PC as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008, you need to install proper drivers. follow this guide
http://www.androidbrick.com/ultimat...agons-are-unbrickable-qhsusb_dload_qpst_qfil/
let me know, if I can help you furthermore.
broccolicakes said:
Tried contacting EncroChat via email form, twitter, and reddit. No luck! Still stuck with this. I want to try this unbrick guide: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732 for hardbricks but I can't get my phone to show as QHSUSB_BULK or Qualcomm HS-USB QDLoader 9008. Any idea how I can do that? This guy seems to have done it:
Click to expand...
Click to collapse
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Thanks!
evronetwork said:
Hello dude,
While it was quite some time when I did this unbrick, it was successful ...expect ALL data to be deleted from phone. Google is your friend and I did get all the files from somewhere
You use a special software from the phone, it's coloros software and with provided files it recognise the phone and flash it(2-3 seperate flashes through the software if I remember correctly) - don't worry as long as the phone turns on(mine was turning on but did nothing ...blank, only way to turn it off was to hold power button and hold it(forced turn off))
P.S. The phone wasn't recognised by the OS ...only from this app(cool? ..weird if you ask me - I'm a computer repair tech guy and find this hard to believe if it didn't happen and see it with my own eyes - on the other hand it could be somewhere hidden in the system and recognised like something else so I won't put my hand in fire to verify this )
Click to expand...
Click to collapse
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
I read just the other day that someone needs the 64gb image instead of the 16gb image. You did so well so far, I'm sure you'll figure this one out. Congrats! "Encrochat Beware!"
The mention of the 64gb vs 16gb image is here:
https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
He links to the images here:
http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
help
broccolicakes said:
I figured it out, thanks ! Now I'm stuck with a more minor problem of only having 16gb visible on my 64gb phone. Can't write the userdata_64G image to my phone. Still trying some stuff out and I'll probably just make a new post if I can't get it to work. Thanks again!
Click to expand...
Click to collapse
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
redi.c said:
Hi broccolicakes, cane you please tell me how you figured it out. Because Am at your same position with an Oneplus x ??
please tell me how you did it????
Click to expand...
Click to collapse
Hi there, sorry in advance this might not be very helpful in your situation. I ended up using the ColorOS repair tool for Oneplus One that I mentioned earlier in the post. It turned out I just didn't have the correct drivers so once I sorted those out the tool was able to bypass all the software and replace everything on the phone so that I could then install my own OS.
I guess the trick would be to find a version of this tool for OneplusX. I'm not sure if there is one available, I haven't looked. Maybe make a separate post about that? The ColorOS tool I'm talking about is from here: http://forum.xda-developers.com/showpost.php?p=55024864&postcount=136 and it just looks directly for the Qualcomm chip and writes to that. I'm not sure where that tool came from, if it made its way out of Oneplus directly or if someone created it afterwards...

Getting e5 supra into edl mode.

I finally have managed to get my supra to go into edl mode. I got my phone to finally show up a q9008 device but no im stuck i dont know how to flash anything over i have never brought back from the dead a qualcom device. It seems a little harder than a mediatek device. My question is now how do i get the firmware to flash when there is no firehose script. Any input is greatly appreciated. I will be posting shortly a picture of where i shorted my board and it wasnt on the jtags more up and center on towards the camera.

Question Hard Bricked OnePlus 9 (LE2113) HELP!!

I hard bricked my OnePlus 9 (LE2113) while I was trying to unlock the bootloader. I tried flashing with Global, EU and Indian variants of MSM Tools but none of them worked.
I'm holding Power and Vol Up to reboot, then I hold Up and Down Volume buttons, plug in with USB cable and start MSM Tool. Every time I try to flash with "Use LIte Firehose" unchecked I always get the "Sahara communication" error at exactly 18 seconds. With "Use LIte Firehose" checked however download completes normally but phone is still hard bricked. This happened on every MSM Tool I tried.
I tried this on two laptops (Win 10 with USB 2.0 ports & WIn 11 with USB 3.0 ports) but ended up with the same results. I'm also using official cable. I have Qualcomm drivers installed.
Can anyone help me? Phone is hard bricked. I can't access anything besides EDL.
Just noticed this thread after your comment in the MSM thread.
Please review my reply. In a nutshell, I bricked my OP9 to a point nothing would work, tried everything for days. Thankfully, EtherealRemnant told me about a specific MSMToolkit for Indian OP9Pros that would get my phone up and running and then be able to flash a proper OP9.
I just compressed it and uploaded it for you, in case you haven't grabbed it yet. Its hosted on mega, so the download should be acceptable wherever you reside on this dirty space ball we call home.
IndianOP9-ProMSM aka The Last Hope
And again, good luck, you got this!
applyscience said:
Just noticed this thread after your comment in the MSM thread.
Please review my reply. In a nutshell, I bricked my OP9 to a point nothing would work, tried everything for days. Thankfully, EtherealRemnant told me about a specific MSMToolkit for Indian OP9Pros that would get my phone up and running and then be able to flash a proper OP9.
I just compressed it and uploaded it for you, in case you haven't grabbed it yet. Its hosted on mega, so the download should be acceptable wherever you reside on this dirty space ball we call home.
IndianOP9-ProMSM aka The Last Hope
And again, good luck, you got this!
Click to expand...
Click to collapse
I managed to flash with Lite Firehose but phone is still dead. I had some issues with phone being recognized but it somehow connected. I have also noticed that device under Ports (COM & LPT) is being recognized even after unpluging the phone, weirdly.
deleted because double post sorry
your device is an eu model i would not answer it with the india msm tool or the modded msm tool, you should get it to work with the eu msm tool
I don't know to what extent the modded msm tool has been processed (my concern is that if certain data on the mobile phone is changed from eu to india, I am concerned that the eu msm tool will no longer work with the eu mobile phone afterwards because certain data now identify cell phone as india model)

OnePlus 7 Pro stuck in EDL

Hello . I have OnePlus 7 pro I update it to android 12 and the next day something went wrong and my phone started an error Qualcomm crash dump something... Now it is stuck in EDL . Display none , power key And volume key works but keep booting in EDL even without connecting the USB cable . I flash the firmware with msm tool firmware flashed %100 but it didn't boot still in EDL .can someone guide me how to fix it
Can someone help!
jahanzaiblohani said:
Can someone help!
Click to expand...
Click to collapse
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
darksx said:
Hello,first thing i noticed is that msm tool finished with around 200 sec.i think that's not normal.I often use msm tool and every time finishes around over 300 sec.I see you have correct Qualcomm drivers.i'm not an expert but you must investigate a little bit more.good luck
Click to expand...
Click to collapse
Drivers are correct and I was flashing it with USB 3.0 port .
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
KyRol said:
I would try older stock ROMs first. O+7pro have plenty of them regarding EDL/MSM mode.
Another thing are checksums. Try to check if your download was successfull by counting them from your side and by comparing what you have with provided download. It should match 1:1.
Click to expand...
Click to collapse
I have the old stock ROM which I flashed it in EDL but phone didn't boot when it is completed phone reboot too but not in normal mode in EDL again
Most often people have bad experience with qualcomm drivers. So make sure that you have some released after 2020 year, as oneplus 7 pro was released in 2020 year. Another issue is related to usb 3.x, better avoid that and try USB 2.0 instead, most of people have best results with older interface of that kind. EDL is kind of old solution, so better to stay away with USB 3.x and use USB 2.0.
Have you got any idea your flash is successful in edl tool? Have you got clean results or warnings/errors?
To be honest with you, I have to use EDL too, because I did wrong upgrade. I used custom ROM instead of stock ROM. Now I have not access to fastboot nor adb via USB either.
try different EDL ROMs, I found 2 threads. one is here, second there. As almost nobody anserws our questions, I will let you know what I did if I do it successfully.
Well, I discovered that I'm in pretty bad situation. In my case not only adb and fastboot does not works. It appears that EDL does not work either. Why? because I connected another oneplus phone over USB to PC and EDL mode was detected spot on. In case my o+7pro, well still same error as previously with adb/fastboot over USB. Something messed with USB on my phone at software side.
So I have to get motherboard get cheap. I do not thik that I can desolder flash or eMMC and revert that so easy.
Sorry Man, can not help you any
further. Turns out my issue is signifigantly other than yours.

Categories

Resources