Dead Devices After using DRM fixes!! - Sony Xperia XZ Premium Questions & Answers

As said in the title... my insurance company has given me several different devices after they keep dying during charge.. I have had several different G1841's and they all seem to die during charge a few days after from applying the DRM fixes and do not turn back on again at all... Has anyone else experienced this issue yet??
I applied all the OTA updates through Sony's official software update then I unlocked the bootloader so I do not believe I am doing anything wrong.. It's just that the devices keep dying every time I obtain root access!! Not sure what to do as this is the 4th time it has happened (happened just today after receiving another device only a few days ago, my insurance company will start to think something is up now...)

Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?

saved-j said:
Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?
Click to expand...
Click to collapse
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?

avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?

avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?

YasuHamed said:
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?
Click to expand...
Click to collapse
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Didgesteve said:
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?
Click to expand...
Click to collapse
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
{
"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"
}

avi312singh said:
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
Click to expand...
Click to collapse
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.

sToRm// said:
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.
Click to expand...
Click to collapse
I believe I used the zips from your 2.0 software.. I sent you a donation through PayPal when you released this, do I get the software or some sort of discount? Student life has hit me hard this year
Well I am getting a completely different device tommorow and will hopefully be able to use your 3.0 fix on it... With regards to the charger, I will use a new wall charger - hopefully can order a new official one from amazon when it arrives and not charge it till then
Before unlocking the bootloader and applying the DRM fixes I experienced no problems such as dead devices.. Let's hope the sixth device is ok!

Update: the culprit of this was the battery charge limit application which requires root privileges and is found on the Google Play store.
I'm not going to link in here but there seems to be a conflict with either the device., rom I don't know - but yeah just making people aware of this

Related

[Q] My atrix 2 is on the edge of dying. please help.

I'm really sorry if this doesn't belong here.
My atrix 2 (MB865 from Singapore) updated by OTA to ICS then rooted successfully and I installed custom roms (scv7 and swifty etc) and even mods (xLoud and Beats) but in CWM (Bootstrap + cwm-on-boot script) it would usually say ''installation aborted'' whenever I tried to flash a custom rom, which is pretty weird since I was using the correct roms for my device.
One day I decided to go back to stock ICS by flashing a ics fzw in RSD Lite 6.0 (I tried flashing 6.7.2_EDEM-18-SEARET_cfc.xml and 6.7.2_EDEM-18-ASIAOPS_cfc.xml) but every time it would stop at step 14/20 ''writing system.img'' but the progress arrows would still keep moving. So after an hour of waiting, I disconnected the phone from the usb cable and I got the black screen with Flashmode (Flash Failure) with ''cannot program'' and ''battery low''. Now the battery died and it won't even charge when I connect it to the wall adapter, it would only boot into the flashmode (flash failure) screen and when I turn it off and try to to it on again it won't. I don't think it's hardbricked because when the battery was still on, I could turn it off and boot back up into fastboot with options like normal boot or go to the stock android recovery.
What do I do now?
Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.
lkrasner said:
Hey, so you have 2 issues here. 1 is that your battery is dead, and you need to charge it.
you can try to find the diy method posted here a while ago, but be careful as you could fry your phone if your not careful. or you can find another phone to charge the battery in (another a2). if neither of those work, you can buy an external charger online to do it.
2 is the issue of why it is not flashing. make sure you are using the exact right fxz for your phone version, there are many available.
Click to expand...
Click to collapse
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance
aligex said:
Thanks alot man, i've stopped stressing, I'll find a way to get the battery charged. But then the problem is in how to escape this damned AP Fastboot Flash Mode "Flash Failure" screen. I mean the fxz I mentioned should work (they match the phone's specifications) but whenever I use FDS Lite 6.0 it always gets stuck at step 14/20 "system.img" for like an hour, is it maybe a drivers problem? Should I try another computer? Should I claim warranty for it even though it's rooted? Thanks in advance
Click to expand...
Click to collapse
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Yes all of these things matter. You will need to do the McGyver method to charge your battery (lkrasner mentioned it as the diy method). It is in this forum, just Search for it.
After you get us the information I asked for above we will be able to better help you.
Also one last thing to check is to see if the MD5sum matches. If not you prolly have a corrupt download and that is why it may not be working as well.
With respect to our developers this will allow you to flash without a battery. It does nothing else useful but does get around the low battery issue
http://forum.xda-developers.com/showthread.php?t=1910027
There are other forms however being in Singapore may limit your options. Remember Google is your friend.
jimbridgman said:
I am going to be totally honest here. You are using the wrong fxz file for your phone. I see you are trying to flash the SEARET fxz, that is for south east asia phones ONLY, and would not work on say an AT&T phone that was purchased someplace else and just being used there.
First off what region/country are you in?
Second does the phone have the AT&T logo at the bottom front of the phone?
Did you get the phone through proper channels in your part of the world, or did you buy it on ebay or something?
Click to expand...
Click to collapse
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
{
"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"
}
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.
matthew5025 said:
To follow up on that, there is a simple way to check if your Atrix 2 is from Singapore. Open the back cover, remove the battery, and look for
If you see that, your phone is indeed a Singapore version, and the SEARET fxz is the correct one to flash.
Click to expand...
Click to collapse
That is great information! Thanks!

Dead Moto G XT1032 after Lollipop downgrade

My Moto G survived the elements for a year now, with abuse, drops, water and a llot of flashing.
Yesterday, i decided to use Lollipop Brazil rom from here. It all went well but after some testing and just checking out new features i downgraded to 4.4.2 rom. Lollipop is imho not very fast compared to latest 4.4.x...
The device worked without problems, until i got the OTA update for 4.4.4. When it was installing in the stock recovery, the screen went dark. Since that moment no life at all! The LED works a few minutes when i charge it, but other than that. I have a nice black -not working- device.
Then I tried this & this without any luck.
I'm booted with driver verification disabled, installed "qhsusb_bulk" driver from Riffbox Jtag. It can see the device but can't flash a new bootloader.
Fastboot don't work, because I can't even power on the device....
I'm fed up, this is my main device and I didn't expect this. After all, I flashed CM12 5.0 builds in the past and reversed to 4.4.x without any hassle!!
Can I do something? I have the right torx screwdrivers.... something... *sigh* It can't be that just a few lines of code f*ck up this device....
{
"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"
}
You should have just installed one of the custom roms instead. As far as I can tell, there's no difference between those and the official rom other than a few extra features. The brazillian rom you installed came with the new bootloader and that makes it likely to hard brick your phone if you try to downgrade back to kitkat.
jman1234 said:
You should have just installed one of the custom roms instead. As far as I can tell, there's no difference between those and the official rom other than a few extra features. The brazillian rom you installed came with the new bootloader and that makes it likely to hard brick your phone if you try to downgrade back to kitkat.
Click to expand...
Click to collapse
I tought the official rom was the most stable one...
So what is plan B?
dwensch said:
I tought the official rom was the most stable one...
So what is plan B?
Click to expand...
Click to collapse
I believe there is a guide to "un" hard brick your phone somewhere around this forum. Try searching [guide] moto g hardbrick or something similar... But since you upgraded the bootloader this most likely will not work. Sorry for the bad news... Wait for new methods or jtag your phone. Or send it in to motorola... Try running the qboot.exe in windows xp sp3 compatibility mode.
skyguy126 said:
I believe there is a guide to "un" hard brick your phone somewhere around this forum. Try searching [guide] moto g hardbrick or something similar... But since you upgraded the bootloader this most likely will not work. Sorry for the bad news... Wait for new methods or jtag your phone. Or send it in to motorola... Try running the qboot.exe in windows xp sp3 compatibility mode.
Click to expand...
Click to collapse
XP SP3 mode didn't work... and I don't think Motorola will fix it for free, since i replaced the screen 2 times already...
Gonna need to save money for new phone now, damnit
Is there a way to extract 5.0 bootloader and force "install" to my device?
dwensch said:
XP SP3 mode didn't work... and I don't think Motorola will fix it for free, since i replaced the screen 2 times already...
Gonna need to save money for new phone now, damnit
Is there a way to extract 5.0 bootloader and force "install" to my device?
Click to expand...
Click to collapse
The bootloader should be in the zip file you got the rom from. It should be called motoboot.img
But you need to be able to blank flash your phone to flash a new bootloader if its hard bricked. Your best bet at this point in time would a jtag. Just be patient and wait a few weeks, theres bound to be a solution soon...
OKay, i will have patience. Still, very anoying.. But i understand it, because the new ART software changes everything... I hope somebody will take the time and make some solution...
dwensch said:
OKay, i will have patience. Still, very anoying.. But i understand it, because the new ART software changes everything... I hope somebody will take the time and make some solution...
Click to expand...
Click to collapse
No it is not because of ART. That doesn't have anything to do with your problem. When you flashed firmware to upgrade to Lollipop you must have also flashed the new bootloader. You might have used a command called "fastboot flash motoboot motoboot.img" When you do this, the updated bootloader will not boot to kernels below android 5.0. So when you tried reflashing 4.4.4 or lower on your device, you must have used a command like "fastboot flash boot boot.img" Since you flashed a kernel that the bootloader does not support your phone became "hard bricked" more or less.
I did the exact same procedures and having the same problem.Someone please help
sauravbiswas said:
I did the exact same procedures and having the same problem.Someone please help
Click to expand...
Click to collapse
The bootloader should be in the zip file you got the rom from. It should be called motoboot.img
But you need to be able to blank flash your phone to flash a new bootloader if its hard bricked. Your best bet at this point in time would a jtag. Just be patient and wait a few weeks, theres bound to be a solution soon...
I'll help you: PM me I'm Dutch also!
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
harshhemnani said:
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
Click to expand...
Click to collapse
My bootloader is'nt working so can't load a custom recovery
He can't do that if the phone does not even turn on...
I just hope to get a working solution fast....coz this is my daily driver and I m screwed
harshhemnani said:
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
Click to expand...
Click to collapse
I wish it was that simple! Did you even read the topic?
I hope somebody can fix mine and others problem. Because i spent allot of money on this phone *sigh*, there is nothing wrong with the hardware.
In the past year i replaced the LCD 2 times, 1 cover and 1 backhousing. So the hardware is functioning perfect now. It makes me sick that just a few lines of code destroy the bootloader software!!!
Why was this not stated in OP from Brazil Lollipop? Yeah, it says it can "brick the phone', but that warning is so generic..... I wish he was more specific?
Im gonna buy a new phone in the coming weeks, because IMHO, this phone is RIP. But if somebody is able to get it working again, i would be very grateful.
Well to be fair, you should have known that flashing an OTA meant for xt1033 on xt1032 would have caused problems.
dwensch said:
I wish it was that simple! Did you even read the topic?
I hope somebody can fix mine and others problem. Because i spent allot of money on this phone *sigh*, there is nothing wrong with the hardware.
In the past year i replaced the LCD 2 times, 1 cover and 1 backhousing. So the hardware is functioning perfect now. It makes me sick that just a few lines of code destroy the bootloader software!!!
Why was this not stated in OP from Brazil Lollipop? Yeah, it says it can "brick the phone', but that warning is so generic..... I wish he was more specific?
Im gonna buy a new phone in the coming weeks, because IMHO, this phone is RIP. But if somebody is able to get it working again, i would be very grateful.
Click to expand...
Click to collapse
jman1234 said:
Well to be fair, you should have known that flashing an OTA meant for xt1033 on xt1032 would have caused problems.
Click to expand...
Click to collapse
No there is no problem with the ota stuff. Its the fact he flashed new boot loader and tried to downgrade. That is the root cause of the problem. As I said be patient and wait a few weeks, there's bound to be a new solution. If you want I can send some partitions from my phone if you want. Lollipop is very new so solutions are scarce.
Exactly, wait a while until the right files are out and you'll be able to revive your phone.
The same problem here, we have to wait for Mbm-ci 5.0 for bootloader 41.18 right?
i installed lollipop to my xt1034 GPE and try to be root, the phone stuck on boot animation and i tried go back to 4.42 and works, but when i update from ota to 4.4.4 some go wrong and my phone death, also i cant enter to bootloader

New Update - QC2

According to the Verizon Galaxy S5 Update Page:
This software update provides the latest Android™ security patches, fixes an email issue and updates the Amazon Shopping app.
Email update:
Fixes an issue that prevented Outlook® 2007 and 2003 users from accessing and downloading email attachments.
Click to expand...
Click to collapse
Please note that if you happen to play Pokemon GO or any game which "GPS Spoofers" take advantage of, the March Security Patch, and this update will prevent GPS Spoofing.
Also, I'm not entirely sure yet as to whether the Samsung Patch for Qualcomm Galaxy S5 bootloaders included in the March Security Patch will affect the ability to have a Developer bootloader anymore:
SVE-2016-7930: Multiple Buffer Overflow in Qualcomm Bootloader
Severity: Critical
Affected versions: Galaxy S5 with Qualcomm AP chipset
Reported on: December 20, 2016
Disclosure status: Privately disclosed.
A buffer overflow vulnerability exist in Qualcomm bootloader.
The patch prevents buffer overflow by removing the problematic source code.
Click to expand...
Click to collapse
I, personally, am not willing to test this, but if anyone does, please post your results. I'll upload an aboot free (Dev Friendly) firmware as soon as possible in case anyone wants to test it.
I'm currently in the process of downloading/uploading the Odin firmwares right now. I'll update this post when they are uploaded.
EDIT:
Stock No-Wipe FW. Will remove Developer Status Bootloader: G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME_No_Aboot.tar.md5.zip
If it breaks something that I warned about, please reply.
If it breaks something that I didn't warn or know about, please share with everyone else.
I'm guessing no replies and no ROMs based on QC2 means noone has tested it yet.
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
I'm gonna try it out when I get a chance this week. Thanks!
Has anybody tried this?
robbyoconnor said:
Has anybody tried this?
Click to expand...
Click to collapse
Not yet I'm gonna download this once I get to a pc definitely
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
Not yet I'm gonna download this once I get to a pc definitely
Click to expand...
Click to collapse
You can use Flaahfire by the way.
Download /installed last night.Havent had time to dig around. Precursor look has only shown latest Android security updates.
Dudash said:
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
Click to expand...
Click to collapse
How we looking, captain?
I recently was pushed the QC2 update with the March 2017 security package. I have noticed a significant decline in performance and battery life. Anyone in the same boat?
It seems like they have pushed a security updated every other month or so for the last 6 months. It is very irritating. I want to go back to root but it is too much of a hassle to figure it out at this point. I feel like they are deliberately doing these updates to make the S5 run worse and feel more outdated so you are more inclined to go buy a new one. Really sick of the whole game that is the telecom industry.
I am going to try doing a factory reset (very annoying) and see if that helps. Hopefully I can hold out long enough for the Pixel 2.
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Noooooo! I flashed the Dev friendly QC2 modem and it seems to have killed my dev bootloader and wiped my phone!
I'll keep messing around and see if it can't be remedied. I could just punch myself for being so ambitious, though.
Edit 1: It was taking forever on the Verizon logo, so I pulled the battery and rebooted to recovery. It wiped TWRP and put in stock. I booted to Download Mode, and it still reads MODE: Developer (which I hope to God means my Dev bootloader is retained).
Edit 2: TWRP sucessfully re-flashed. The "Custom" with unlocked lock icon has reappeared on the boot screen, along with the yellow text at the top (so clearly, I was wrong about losing Dev status. Whew! I just freaked out when I saw a plain boot screen and the dreaded Verizon logo :silly. My installation of Lineage OS is clearly gone, but, peeking through TWRP's file manager appears to indicate my media data (photos, downloads, etc.) may yet have survived. I'll flash Lineage and GApps and see what happens.
Edit 3: Lineage OS booted successfully (made easier with the help of an SD card-- hooray for those things, amirite?), with QC2 baseband intact! Hooray! And my downloads and pictures and everything survived too.
Lesson: Always make a nandroid backup when doing this sort of thing! It takes a while, and it's morbidly annoying, but had I done it, I probably wouldn't've had to start from scratch. But hey, got the new baseband, and still running Lineage, so I call this a win. Cheers, everyone! And thanks to OP for posting updates!
Follow-up: Since it doesn't seem like we can flash only the new basebands by themselves, I've found a tactic that does the trick for those of us on not-stock ROMs. Boot into TWRP and make a backup of Boot, System, and Data (notice there's a Modem option-- leave it unchecked). I imagine it's best to put the backup image on an SD card. Then Odin the dev-friendly firmware update (I used the no-wipe option). Let the phone restart, then Odin the most recent TWRP back on there. Boot into TWRP, do a Factory Reset Wipe, and restore the backup you made. Takes a little while, but it does leave you with your phone as it was, but with the new baseband. :victory:
{
"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"
}
mohammad.afaneh said:
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Click to expand...
Click to collapse
In the process of uploading right now.
Dudash said:
In the process of uploading right now.
Click to expand...
Click to collapse
??? thanks
J-Lindo said:
How we looking, captain?
Click to expand...
Click to collapse
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Dudash said:
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Click to expand...
Click to collapse
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
J-Lindo said:
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
Click to expand...
Click to collapse
I flashed the entire firmware minus the aboot.

Bricked MT6577 SoSoon/Senq X8 Elite 3, NO USB Debug/ADB, Stock Recovry No Roms to D/L

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.

flashed wrong bootloader

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?

Categories

Resources