Idk what to do I flashed the wrong bootloader on my S7 (snapdragon) through flashfire and now I get a black screen with a blue LED with a green LED slowly blinking behind it. How to recover? Right now I'm just letting it die. Can't hard reset either.
rifek4 said:
Do a download mode is working for you?
Click to expand...
Click to collapse
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..
savagevegeta said:
Nope. Sadly. I get no response from the phone whatsoever. I heard a USB jig can fix this but i need to make sure before i buy..
Click to expand...
Click to collapse
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7
*Detection* said:
USB jig doesn't work on the S7, got one here
Probably gonna have to take it somewhere for repair unless there is a program similar to SP Flash Tool (Smart Phone Flash Tool) which can flash a seemingly dead device, for the S7
Click to expand...
Click to collapse
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?
savagevegeta said:
Even a completely dead one? I don't want to have to buy a replacement motherboard, but it looks like i HAVE to. I was counting on the usb jig working, but i guess not. Not even my PC can recognize it. When i plug it it, nothing happens. Do you know of anyway i can revive it?
Click to expand...
Click to collapse
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
I am open to suggestions on what tools i may use. Im trying the flash tool as soon as i get home.
I tried to downgrade using flashfire after rooting the device but it failed and thats why it's dead.
At first it was just a blue light with a green one blinking behind it, but i let it die over night in hopes of being able to recover it in the morning. Now, there isnt even the light.
The battery isnt dead according to my multimeter.
While the bootloader is locked, it HAD engineerboot so maybe that allows something. :/
I would have taken it to a repair shop but the closest one knows nothing about software issues and only suggest hardware repairs, hence me wanting to replace the motherboard.
I'm going to search how to fix it with linux since i have a linux machine, i just have no experience with it at all. At least pushing the bootloader will help an awful lot. If you have any knowledge on any of these, even the slightest, do share. Ill do some research meanwhile and if i find a fix, I'll post it. This phone was so good and i miss it dearly, which is why i need all the help and research i can get.
Apparently no one has ever bricked the snapdragon version of this phone, given the lack of any google results similar to this situation on this phone. ;-;
*Detection* said:
It's not dead, you just can't boot it because of whatever you did to it, hardware is still OK more than likely
That flash tool I was talking about just needs the device to have power, not sure exactly how it works but it can flash without being in any download mode for the devices it was designed for
If I knew of a way for you to revive it I would have suggested it in my first reply
Possibly a Linux machine and some shell commands could push a new BL to it, but that's above my knowledge
Basically you managed to kill it with software, so in theory it should be repairable without replacing hardware, but you're gonna need the right tools, and likely only a repair shop would have them
EDIT - And I just realised it's the Snapdragon S7, so the bootloader is locked, making it even more difficult
Click to expand...
Click to collapse
Its in QUSB_BULK now. At least the computer SEES it
savagevegeta said:
Its in QUSB_BULK now. At least the computer SEES it
Click to expand...
Click to collapse
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
---------- Post added at 22:51 ---------- Previous post was at 22:25 ----------
Not sure how to enable the bootloader update function, if it will enable once you load firmware into the sections on the right, but try ODIN 3.12.10
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 22:53 ---------- Previous post was at 22:51 ----------
https://forum.xda-developers.com/showthread.php?t=2711451
*Detection* said:
Yea seems to be as suspected, here is a different device with same QUSB ID, and the fix is as I suggested using adb and different flash tools to push the correct files to the device
https://xiaomi.eu/community/threads/sudden-death-or-hardbrick.36285/#post-334687
http://www.androidbrick.com/xiaomi-mi5-how-to-flash-global-multilanguage-rom-unbrick-guide/
This is not for the S7 though, so don't copy it or use their tools, but it will give you a general idea of what the process would be if you had the correct files and flash tools available
Click to expand...
Click to collapse
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5
savagevegeta said:
Thanks for researching this. It did give me an idea, but it sucks that there is no tools for samsung devices stuck in QHSUSB_BULK mode. I found a guide that allows me to flash a PIT file and the bootloader file onto an SD card, and then insert it into the bricked S7, but that process requires a second S7 to flash the files onto. I tried flashing the boot.img and recovery.img onto the SD and hoping for the best, but still no luck. I'm looking for other methods. I saw on youtube that some guy used a program to flash an unbrick.img onto an SD, and that got it to go into download mode, but the tool he used was S5 specific and the video was a guide for the S5
Click to expand...
Click to collapse
Yea I know about the one for the S5, that was my phone before the S7, maybe PM that dev (He's from XDA) on the S5 forums and see if he could help you out?
Related
I haven't disappeared -- I am working on a way to root Nougat for people that took the OTA or flashed the KDZ.
I need someone that has done that to do a test.
Need to see if the Nougat ROM still has EDL. If someone could try:
adb reboot EDL
and then hook your phone up to a Windows box and see if it shows up as 9008 HS-USB qdloader. This will not brick your phone, but this IS the mode that bricked phones go into.
Once you have checked, you can pull your battery, and your phone will reboot.
Once I know for certain that aboot on Nougat still has EDL, I can keep going.
-- Brian
Nope. Tried on a Linux box, and a Windows 10 one too. All it does is just reboot the phone straight back into Android, and shows up as a normal "V10" device.
and then hook your phone up to a Windows box
So, I dont understand what Windows box is. Can you explain it more clearly. I can give it a try
@arrisbutter Well that is disappointing. Thank you very much for verifying so I don't waste any more time going down that route.
-- Brian
huy chuong said:
and then hook your phone up to a Windows box
So, I dont understand what Windows box is. Can you explain it more clearly. I can give it a try
Click to expand...
Click to collapse
Windows box = Any Windows Computer
@runningnak3d.
Upgraded via LG Bridge can confirm EDP just reboots phone.
Sent from my LG-H901 using Tapatalk
Well, I found a method that works, but it is risky -- requires a leap of faith, and bricking your phone.
The basics are:
* Put your phone into download mode
* Start flashing the Nougat KDZ
* At 15% -- pull the USB cable. Yep, you read that right.
* Download the image that I will post once I am sure this procedure is at least a LITTLE safer.
* Write image to SD card
* Pull battery
* Insert SD card
* reinsert battery
* Watch phone boot into Marshmallow
* adb reboot recovery
* Flash the zip that I will be posting along with the SDcard image.
I am REAL hesitant to post the files needed to do this, because I would feel awful if someones phone bricked, and stayed bricked.
I have tested this myself, and it works. However, the fact that there are people having power issues, while others aren't. Some people are having performance problems, while others aren't -- really makes me leery.
There seem to be too many variations of hardware out there. What works for me, may not work for someone else.
I am going to do some more testing tonight (never deliberately bricked my phone so many times in one day ), and I will decide tomorrow.
The good news is -- it IS possible to root if you took the OTA / flashed the KDZ / used LG Bridge / etc....
runningnak3d said:
I haven't disappeared -- I am working on a way to root Nougat for people that took the OTA or flashed the KDZ.
I need someone that has done that to do a test.
Need to see if the Nougat ROM still has EDL. If someone could try:
adb reboot EDL
and then hook your phone up to a Windows box and see if it shows up as 9008 HS-USB qdloader. This will not brick your phone, but this IS the mode that bricked phones go into.
Once you have checked, you can pull your battery, and your phone will reboot.
Once I know for certain that aboot on Nougat still has EDL, I can keep going.
-- Brian
Click to expand...
Click to collapse
i know the reboot edl command does not work, it just reboots the device as i have tried BUT you can force it into edl through the test points on the motherboard im sure you a aware.i tried flashing mm through qfil after putting my device into edl but i just got a sahara error.
You already found a way ? lol that's crazy! personally if this method ends up bricking my phone for good,i wouldnt care as im not using it because nougat has blocked me from doing anything.
Yea, forcing EDL via the testpoints is (IMHO) riskier than interrupting a flash to get EDL. The testpoint route, you run the risk of physically damaging your phone.
All Qualcomm chips (up to the 820) will boot from the SD card as long as the boot loader is unlocked. Unfortunately Qualcomm decided to be super ***** when they made the 820 and above. The eMMC isn't just one block device with multiple partitions. It is presented as several physical block devices. Unfortunately -- even if it would boot from the SD card, a normal PC sees an SD card as a single block device, so it would be impossible to image it.
I am just rambling now, because none of that applies to the 808. As long as you have a little patience, it is impossible to brick any Android phone with the 808. Well, you also need to be able to unlock the bootloader -- as is the case with the H901.
-- Brian
runningnak3d said:
Yea, forcing EDL via the testpoints is (IMHO) riskier than interrupting a flash to get EDL. The testpoint route, you run the risk of physically damaging your phone.
All Qualcomm chips (up to the 820) will boot from the SD card as long as the boot loader is unlocked. Unfortunately Qualcomm decided to be super ***** when they made the 820 and above. The eMMC isn't just one block device with multiple partitions. It is presented as several physical block devices. Unfortunately -- even if it would boot from the SD card, a normal PC sees an SD card as a single block device, so it would be impossible to image it.
I am just rambling now, because none of that applies to the 808. As long as you have a little patience, it is impossible to brick any Android phone with the 808. Well, you also need to be able to unlock the bootloader -- as is the case with the H901.
-- Brian
Click to expand...
Click to collapse
you are right about potentially physically damaging your phone.i was shorting the test points and there was a little spark once.i thought the phone was fried but somehow i was still working lol.you mentioned that you need to be on a unlocked bootloader to begin with correct?i updated through kdz and my bootloader is unlocked.would really like to get back to mm.
@jass65 Once you are booted from the SD card, you can flash whatever you want. I will have to pull the partitions out of the MM KDZ, but I can make you a zip that will get you back to stock MM with TWRP -- you would just need to root then.
Getting to EDL is the key, it doesn't matter what method that you use. You can either use my "deliberately brick your phone" method, or the testpin method.
I will see how my evening goes. Hopefully I will have something for you tomorrow. I definitely have more time now that I know at least ONE method works.
-- Brian
runningnak3d said:
@jass65 Once you are booted from the SD card, you can flash whatever you want. I will have to pull the partitions out of the MM KDZ, but I can make you a zip that will get you back to stock MM with TWRP -- you would just need to root then.
Getting to EDL is the key, it doesn't matter what method that you use. You can either use my "deliberately brick your phone" method, or the testpin method.
I will see how my evening goes. Hopefully I will have something for you tomorrow. I definitely have more time now that I know at least ONE method works.
-- Brian
Click to expand...
Click to collapse
ok, guess im intentionally bricking it cause i just installed a new thermal pad and dont wanna open it up again lol.Thanks ! :good:
runningnak3d said:
@jass65 Once you are booted from the SD card, you can flash whatever you want. I will have to pull the partitions out of the MM KDZ, but I can make you a zip that will get you back to stock MM with TWRP -- you would just need to root then.
Getting to EDL is the key, it doesn't matter what method that you use. You can either use my "deliberately brick your phone" method, or the testpin method.
I will see how my evening goes. Hopefully I will have something for you tomorrow. I definitely have more time now that I know at least ONE method works.
-- Brian
Click to expand...
Click to collapse
Awesome news! I'l be looking forward getting back MM with TWRP as well.
runningnak3d said:
Well, I found a method that works, but it is risky -- requires a leap of faith, and bricking your phone.
The basics are:
* Put your phone into download mode
* Start flashing the Nougat KDZ
* At 15% -- pull the USB cable. Yep, you read that right.
* Download the image that I will post once I am sure this procedure is at least a LITTLE safer.
* Write image to SD card
* Pull battery
* Insert SD card
* reinsert battery
* Watch phone boot into Marshmallow
* adb reboot recovery
* Flash the zip that I will be posting along with the SDcard image.
I am REAL hesitant to post the files needed to do this, because I would feel awful if someones phone bricked, and stayed bricked.
I have tested this myself, and it works. However, the fact that there are people having power issues, while others aren't. Some people are having performance problems, while others aren't -- really makes me leery.
There seem to be too many variations of hardware out there. What works for me, may not work for someone else.
I am going to do some more testing tonight (never deliberately bricked my phone so many times in one day ), and I will decide tomorrow.
The good news is -- it IS possible to root if you took the OTA / flashed the KDZ / used LG Bridge / etc....
Click to expand...
Click to collapse
Go ahead, I am willing to try it. I have no power issues or other probs and if it bricks I have my MM H900 to fall back on.[emoji4]
Sent from my LG-H901 using Tapatalk
This is interesting. I've put my phone on edl mode so many times until I can't count it in my quest to bring my v10 back to H901. It was H901 lollipop but bricked after I flash MM on it, it has F600L code on the pcb and now running fine on F600L nougat.
I'd be gladly try it, probably I can get back to H901 and get rooted.
@runningnak3d
Have just checked dev options and 'oem unlock is off and greyed out' on my H90130b.
The phone still shows the unlocked warning when restarted. Could this be why EDL cannot be accessed via adb?
Sent from my LG-H901 using Tapatalk
Stransky said:
@runningnak3d
Have just checked dev options and 'oem unlock is off and greyed out' on my H90130b.
The phone still shows the unlocked warning when restarted. Could this be why EDL cannot be accessed via adb?
Sent from my LG-H901 using Tapatalk
Click to expand...
Click to collapse
no as far as i know the only to access edl on v10 is with test point or hardbrick.The reboot edl command is not in the boot so it doesnt work.i had tried that command on 6.0 rooted unlocked and 7.0. it does not work since the command is not even in boot.
@Stransky If you are getting the warning on boot, then you have an unlocked boot loader. The "Enable OEM Unlock" in developer options just allows you to unlock, in fastboot. Once you are unlocked, that should be turned back off, so you are fine. The fact that it is grayed out is kind of disturbing though.
jass65 said:
no as far as i know the only to access edl on v10 is with test point or hardbrick.The reboot edl command is not in the boot so it doesnt work.i had tried that command on 6.0 rooted unlocked and 7.0. it does not work since the command is not even in boot.
Click to expand...
Click to collapse
Thanks for your input. Screenshot attached.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my LG-H901 using Tapatalk
My phone is on h901 mm. How could I help
I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time
Hello have you tried a hard reset so far ?
-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk
-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.
Hi everyone, first post in a long time here. Just bought an unlocked Tmobile Oneplus 8 off Ebay. When it arrived the back of the phone has the model# IN2013 on the phone but there's also a sticker that says model IN2017. Everything looks fine with the phone but it has a floating number bar on the bottom. Does anyone know how to remove this floating number bar?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Why are you covering the numbers? Is it the serial or IMEI number?
Using the ebay seller's photo as my screenshots aren't showing up here with the Insert Image tool. The floating numbers are different than the IMEI and Serial # showing in Setting >> About phone >> Status
Hey! I have the same thing as you and am wondering exactly what you are wondering. The difference is I have a verizon variant and the model number is IN2019. Did you notice a strange app called NXP Device Test Application? I did a factory reset and it's still there. I'll attach pic. I'm thinking that these are demo store versions and just need to flash to stock, but would prefer to know more about them before I do it.
mateonexus4ever said:
Hey! I have the same thing as you and am wondering exactly what you are wondering. The difference is I have a verizon variant and the model number is IN2019. Did you notice a strange app called NXP Device Test Application? I did a factory reset and it's still there. I'll attach pic. I'm thinking that these are demo store versions and just need to flash to stock, but would prefer to know more about them before I do it.
Click to expand...
Click to collapse
interesting, and thanks for sharing! I'll note that flashing to stock may be a thing to try. I don't see a NXP Device Test Application in the app drawer though
AFAIK OnePlus internal ROMs display this bar showing the phone's IMEI to avoid leaks. All prototype and internal (secret_mea_X) ROMs have that line at bottom.
---------- Post added at 07:02 AM ---------- Previous post was at 07:00 AM ----------
If you're interested in backuping the ROM before you flash to stock, please do that. Also check your ROM version if it starts with secret_mea
Thanks a lot for the information. This bar isn't the IMEI though... or the serial or matching any other information that I can find in the phone.
I think I'll back up in case in flashing somerhing goes wrong or isn't compatible. Now the flashing question. Can verizon variant, which mine appears to be, be flashed? I looked at the firmware on OPO official site and only see 10.5.12.IN21AA. Can this be flashed on top of whatever I have? This I assume is the unbranded firmware.
I'm currently running 10.5.IN67CD. Software version IN2019_12_200213.
Any good HOW TO's for flashing back to stock for verizon variant?
Thanks for all the insight thus far.
lulujyc said:
AFAIK OnePlus internal ROMs display this bar showing the phone's IMEI to avoid leaks. All prototype and internal (secret_mea_X) ROMs have that line at bottom.
---------- Post added at 07:02 AM ---------- Previous post was at 07:00 AM ----------
If you're interested in backuping the ROM before you flash to stock, please do that. Also check your ROM version if it starts with secret_mea
Click to expand...
Click to collapse
mateonexus4ever said:
Thanks a lot for the information. This bar isn't the IMEI though... or the serial or matching any other information that I can find in the phone.
I think I'll back up in case in flashing somerhing goes wrong or isn't compatible. Now the flashing question. Can verizon variant, which mine appears to be, be flashed? I looked at the firmware on OPO official site and only see 10.5.12.IN21AA. Can this be flashed on top of whatever I have? This I assume is the unbranded firmware.
I'm currently running 10.5.IN67CD. Software version IN2019_12_200213.
Any good HOW TO's for flashing back to stock for verizon variant?
Thanks for all the insight thus far.
Click to expand...
Click to collapse
Sorry I'm not sure about the Verizon variant. I'm currently using the global model.
Is it possible to use this tool from https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 to flash to stock?
I was always taught to stay away from ALL IN ONE TOOLS.... and I imagine it would depend on your variant. As far as I can tell I can't flash verizon variant.
10kd said:
Is it possible to use this tool from https://forum.xda-developers.com/android/software/tool-tool-one-driversunlocktwrpfactory-t3358711 to flash to stock?
Click to expand...
Click to collapse
Any luck on trying to flash stock firmware?
Found this on the OnePlus Alpha build bug report page.
https://forums.oneplus.com/threads/alpha-build-ui-suggestions.1274484/#post-21954586
The floating number is the PCBA number. Dialer code *#888#
Okay folks, here's the solution!
The firmware zip files already have the MSM tool zipped up in it.
Make sure to download and install the OnePlus USB device drivers and install in addition to the Qualcomm drivers from the linked site
For T-Mobile
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
For Global
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877/
No more PCB watermark. Make sure to backup any data you want to keep as this makes the phone factory fresh.
does this still work?
I've sent you a message OP, I had the same issue
supergroverthm said:
Okay folks, here's the solution!
The firmware zip files already have the MSM tool zipped up in it.
Make sure to download and install the OnePlus USB device drivers and install in addition to the Qualcomm drivers from the linked site
For T-Mobile
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4093043
For Global
https://forum.xda-developers.com/oneplus-8/how-to/op8-unbrick-tool-to-restore-device-to-t4085877/
No more PCB watermark. Make sure to backup any data you want to keep as this makes the phone factory fresh.
Click to expand...
Click to collapse
Thank you so much for this solution! I’m in the same boat and only bought this phone because I came across this post before buying.
Do you have any tips for a noob on how I can get this phone into EDL mode as per the instructions you linked? Tried via the volume buttons and via adb with no luck.
The phone screen just turns black when I try to do it via adb and it can only be turned back on by holding the volume up and power buttons. Holding the power button by itself won’t turn the phone back on.
I’m trying to do this right out of the box, haven’t even connected the phone to wifi or anything, not sure if that matters. I’m pretty new to this and have been getting more into phones lately so I thought I’d try to fix this OP 8.
Just in case, sorry for replying to such an old comment, not sure if that goes against etiquette here, I just created this account. Would appreciate any help you can offer!
Shoresy said:
Thank you so much for this solution! I’m in the same boat and only bought this phone because I came across this post before buying.
Do you have any tips for a noob on how I can get this phone into EDL mode as per the instructions you linked? Tried via the volume buttons and via adb with no luck.
The phone screen just turns black when I try to do it via adb and it can only be turned back on by holding the volume up and power buttons. Holding the power button by itself won’t turn the phone back on.
I’m trying to do this right out of the box, haven’t even connected the phone to wifi or anything, not sure if that matters. I’m pretty new to this and have been getting more into phones lately so I thought I’d try to fix this OP 8.
Just in case, sorry for replying to such an old comment, not sure if that goes against etiquette here, I just created this account. Would appreciate any help you can offer!
Click to expand...
Click to collapse
I wish I can be of more help. My phone went into EDL mode with the buttons. If I remember right, the EDL mode looked like the phone was still off and I think I had to plug it into a USB 2.0 port on my computer. Anyways, try all the different USB ports then try different computers.
Traded that OnePlus 8 for a Galaxy S21 several months ago with T-Mobile.
supergroverthm said:
I wish I can be of more help. My phone went into EDL mode with the buttons. If I remember right, the EDL mode looked like the phone was still off and I think I had to plug it into a USB 2.0 port on my computer. Anyways, try all the different USB ports then try different computers.
Traded that OnePlus 8 for a Galaxy S21 several months ago with T-Mobile.
Click to expand...
Click to collapse
Thank you for the reply! I couldn't figure out if EDL mode looked any different since the guide I saw online seemed to suggest that there would be some indicator on the screen.
I noticed that a USB 3 port wouldn't even register the phone on my PC but a USB 2 port seemed to do the trick. My other PC has malfunctioning ram but at the worst case I'll have to wait until I get that fixed.
My plan is also to trade it in, assuming I can get it to work. Thanks again!
Shoresy said:
Thank you for the reply! I couldn't figure out if EDL mode looked any different since the guide I saw online seemed to suggest that there would be some indicator on the screen.
I noticed that a USB 3 port wouldn't even register the phone on my PC but a USB 2 port seemed to do the trick. My other PC has malfunctioning ram but at the worst case I'll have to wait until I get that fixed.
My plan is also to trade it in, assuming I can get it to work. Thanks again!
Click to expand...
Click to collapse
OK...I'm an idiot, never read the end of the guide, figuring everything was in order and I wouldn't need that information until later. My phone was showing up as QHUSB_BULK instead of QDLOADER 9008 in Device Manager and for some reason the drivers I downloaded were being seen as incompatible with the phone.
After running Windows update, the drivers were successfully updated and on the very next attempt, I was able to get the phone into EDL mode and it was picked up by the MSM tool. Just figured I'd leave an update in case anyone is having the same issue and wondering how to move forward.
Hi everyone,
Recently I purchased and Samsung A11. I wanted to root it and unlocked the bootloader first. Than I used Odin to install TRWP recovery. Odin showed "PASS" and I was supposed to press certain buttons which didn't work. Phone kept coming back to "Download Mode" although I pressed those buttons. So I was stuck. The only option was to cancel the download mode, so I pressed volume down + power button for more than 7 seconds. That was the end Now the phone turns on until I see the Samsung logo, there's a small vibration but it can't go forward. It resets back and now stuck in a loop. None of the buttons work including Volume Down+Power combination. Don't know what I am supposed to do now. Can anybody help?
Thanks...
1. Add Samsung A11 to this thread's title thus mainly owners of such a phone get addressed
2. My recommendation: Re-flash STOCK ROM to get rid off of all mods you applied.
jwoegerbauer said:
Re-flash STOCK ROM to get rid off of all mods you applied.
Click to expand...
Click to collapse
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
gokund said:
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
Click to expand...
Click to collapse
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
Click to expand...
Click to collapse
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
gokund said:
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
Click to expand...
Click to collapse
it wouldn't ... usually the cause of bootloop is certain corrupted partition and as long as that partition is corrupted it would keep bootlooping.
if you doesn't know what your doing your best bet is Take it to authorized service center and let them fix it. like what @jwoubeir said
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
sammiev said:
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
Click to expand...
Click to collapse
great tip work on ADB too anyway OP is provably using sp flashtool since his phone is samsung so this method would be rather tricky
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told and I tried flashing another TRWP file thinking that might have caused the problem but nothing has changed. Same loop again ! So I flashed the original ROM back using Odin and it's back live again Thanks for the help guys. But to be honest, I am still curious. What might be the problem in not getting TRWP flashing going right?
gokund said:
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told
Click to expand...
Click to collapse
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
sammiev said:
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
Click to expand...
Click to collapse
I tried again from scratch with a new TRWP file and the result is the same. Odin shows "PASS" but the "Download Mode" screen gives the error as in the photo:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone model is A115F and I downloaded the TRWP file from this link:
Downloads for : Samsung Galaxy A11 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The version I used is "twrp-3.5.0_10-3_afaneh92-a11q.tar"
I also tried rooting with Magisk without the need of TRWP installation. That was also unsuccesfull. Odin was PASS but I got bootloader screen saying Secure Check Fail : vbmeta
Here's the screenshot of Magisk fail in "Download Mode"
Can't figure out what's wrong ...
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Deleted
sammiev said:
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Click to expand...
Click to collapse
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
gokund said:
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
Click to expand...
Click to collapse
Usually the latest TWRP with the latest firmware.
Check my profile, your KG stated is ****ed. There is nothing you can do about it, there is abosulutly no way to fix this without unsoldering the eMMC and resetting it entirely. Some people on 4PDA had the same problem and found no fix. I was hopping to develop a custom rom but I cant as my kg state is prenormal. This mexican dude on youtube fixes devices with KG and FRP issues, but yeah this aint something that you can do at home. At least I learned not to buy any samsung devices in the future https://www.youtube.com/c/TeamOcmineMMCBootRepair
edit: nvm your oem is unlocked, you can just flash the vbmeta reset script via odia and everything should flash fine.
Here is a toolkit of several tools ive collected and put together for the A12 in a single pack to help see through all the clutter and chaos of this forum, i have an A125U (converterd to a-125w) so thats all i can confirm working 100% but im 99% sure the methods will work for any mediatek version of this phone just make sure to use your correct firmware
the tools included will allow you to :
Enable OEM Unlock +Unlock the Bootloader
Create Scatter Firmware
Unbrick your device if stuck in Brom/Da mode
Root Your Device / Install TWRP
Enter Brom Mode
and more
All instructions are included inside the main folder of tools, seriously... and i mean seriously...please read the 3 or 4 different guides/methods to see which ones you actually need to do. Some are not needed depending on your end goal. I spent a month making every error possible and testing things so you dont have to so save yourself the trouble and read through
Ill do my best to answer any questions or issues you might have but please...please use your eyeballs and google.. i really dont want to have to answer questions like "how flash magisk" etc. Google is there.. it is your friend , use it. XD
A12 Toolkit.zip | by Privyetcyka for Galaxy A12 Nacho
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Thank you, I hope I can figure it out with the translator, I went to try ..
fackstrot said:
Thank you, I hope I can figure it out with the translator, I went to try ..
Click to expand...
Click to collapse
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
PrivyetCyka said:
No problem. What exactly are you trying to do, just unbrick the phone and flash stock firmware? I can make the instructions more easy to translate for you
Click to expand...
Click to collapse
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
fackstrot said:
I did something with it when I reset Frp and now it does not start, it is defined simply as the mtk port...does not enter into any of the modes (recovery or loading) does not respond to charging
yes i just want to run it on stock firmware
Click to expand...
Click to collapse
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
PrivyetCyka said:
Just follow the Unbrick directions that will get your phone back working stock. If you don't have scatter firmware for your device youll need to make that also, tools are included
Click to expand...
Click to collapse
I followed the steps, I was inattentive myself) but still ran into a problem
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error
well, if I put it from SM-A125W, then the rollback error
Will that work for the Samsung Galaxy A13
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Ansemseekerofdarkness said:
Apologies for the stupid question, but this part:
**Follow the instructions Provided by A125U Root bit 3 by FixMX file to actually unlock the bootloader and root the device**
don't seem to be included in the zip file, unless I'm a buffoon and didn't notice them.
Is a FixMX a user who already wrote a guide for this? I just need to unlock the bootloader and then I can follow basic directions from there to get what I need.
Click to expand...
Click to collapse
I have no idea which directions your directions your talking about the only ones I wrote are the ones in the main folder , probably with a bunch of exclamations. I can't remember and don't have the file with me right now but as far as unlocking the bootloader you just need to get the phone to accept different firmware. Try flashing Sm-a125w Canadian version XAS
fackstrot said:
when you enter Samsung Enable Brom by PGPT, nothing happens to the phone...
Click to expand...
Click to collapse
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
PrivyetCyka said:
Nothing will happen. Once your in brom mode you need to use another tool to unlock the bootloader and disable secureboot everything is included
Click to expand...
Click to collapse
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
fackstrot said:
Nothing happened .. I got upset and put the phone on the shelf, told the owner to pick it up and carry it to the service center, but they didn’t take it to the service center
Click to expand...
Click to collapse
Nothing is supposed to happen if nothing happens that is good . Just leave the phone connected how it is and use a mediatek unlocking tool
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
ronnieshane1 said:
When i get to the oart in your instructions that says to open the MTKMETATOOL file i just get a message informing me that it has expired and to see the developer. Is there another link to open the tool somewhere else? Ive looked at the other option to get a windows tool from github that you included but i can admit that im not as savvy as i would like to believe and all ive ever used is windows so i have no idea what to do with all of that on github. I hate having to bother you guys but i really would appreciate the help. Thanks in advance and you guys are just awesome!
Click to expand...
Click to collapse
Change date to 25 may 2022 to get working
Ok... im trying to repair mi phone and failed i follow exactly as i seen in the readme instructions on the unbrick folder and nothing... i got 2 errors in relation of super.img (im trying to flash the last android 11 firmware on the phone A125MUBS3BVF1) if i uncheck the super the phone flash correctly but doesn't boot so what next...?
fackstrot said:
Through such a bypass, I was able to see at least some kind of response from the flash tool, but the error View attachment 5664401
Click to expand...
Click to collapse
And now i had this error i think using the format all + download relocks the bootloader sp flash tool is asking me to download signed images i can't exit from that so i give up and buy another mainboard
My last reply...
I uploaded some images to get BROM working on A125M this zip includes
Preloader and PGPT files from 4 firmwares
Android 10 Binary 1 (AUC1)
Android 11 Binary 1 (BUF9)
Android 11 Binary 3 (BVF1)
Android 12 Binary 3 (CVH3)
Plus i will modify this post because im uploading CVH3 firmware for SP Flash tool flash (Includes the scatter) pls disable the auth using mtkmeta or the python coded program (used 3.7.9 and worked using the shell)
PGPT and Preloader images