Related
Hi guys,
This is all about developing the Focus S, since we are on our own on this one I thought id start the ball moving but it would be great if others can help, my first target is to try and download as much of the device as possible
Can I promise anything at all? nope
Have I achieved anything yet? well id say 1 step above doing nothing at all, if you can call that progress then yes, there is progress
Is it even possible to do anything? i dunno
Could i brick my device? possibly, i honestly don't know
in short, this is me blindly wondering in the dark with absolutely no direction what so ever!
So what have i done, well, i managed to get the Focus S talking to Qualcomms diagnostic utility, QPST and RevSkills CDMA Workshop
I cant get QXDM to install on Win 8 x64 and im not sure we need that one anyway
it is possible to edit stuff on the phone at a very low level, NOT OS level, it should be possible to download the various images on the phone, but ive yet to have any luck with that, it keeps coming up with "Arm9 fatal error"
ive been able to download and backup various phone settings but this is still outside of the OS#
I can play about with the EFS but there are several folders that i cant get in to yet
So far,both the samsung download mode and the ARM9 (?) download mode IS visible and installes as a com port, but there is no response on that port, i can only get a response within windows when i enable USB diag mode....
i decided not to link to the various tools ive mentioned here, i dont know the legalities of it all so use google, they are all easy to find.
Samsung studio 3 drivers
http://downloadcenter.samsung.com/c...813082717640_Samsung_USB_Driver_Installer.exe
Install it with compability for windows vista.
Samsung Focus info (note that most of this doesn't work, its for the older focus but some does)
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
Handy Diagnostic codes
*#7284# - USB Path control (select to change how your phone communicates with your computer)
*#197328640# - The Root Menu (seriously, don't get too cocky, you could bugger up your device)
Samsung USB Download mode
Turn off Device
hold the camera button and the Volume UP
Whilst holding those two push and hold the power button until it vibrates
Samsung Device Hard reset
Turn off Device
hold the camera button and the Volume Down
Whilst holding those two push and hold the power button until it vibrates
Follow on screen instructions
Enable Diagnostic mode and Connect to QPST or other GSM/CDMA software
Download and install the Samsung drivers above
open the diagnostic app and dial code *#7284#
Select Modem,USB Diag
Reboot
When you plug the phone in you should see a COM port install and appear in device manager
load QPST configuration
Click on the Ports Tab then Click add new port
Select your Phone com port
Click OK then select the phone from the list, hit enable
Click on start clients then you can play with a bunch of options
Please note that this is a serious piece of kit, its designed for low level editing, what I mean by that is that it couldn't care less about if it works or not after you finish playing, a couple of other software options to play with are CDMA tools and RevTools both have the potential to paperweight your phone!
NOTE: Zune will not connect and whilst connected to PC you may lose all GSM connectivity whilst connected as well.
Enable FTM (Factory Test Mode)
open Diagnostic app and dial code*#197328640#
select 6 (common)
Select 1 (FTM)
Select 1 (on)
Click return save (it doesn't always persist unless you do)
Hit Back until you back to the main menu then win key to Windows
REBOOT to enable
NOTE: You will lose ability to connect to GSM with this enabled, a reboot is required to enable it after its set and to deactivate it, ive not found a noticeable difference with this on
If im not wrong, WP uses arm v7.
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
tayfelix said:
If im not wrong, WP uses arm v7.
Click to expand...
Click to collapse
yes your right, but that's what it says, it reboots in to some sort of QC download mode, QPST is the waiting for it to talk to it which it doesn't do, it just sits there with this error message.
I have been able to backup the Important bits that make the phone work, and I have access to the EFS, I can change all sorts at a very low level but any time I try and download some of the various "partitions" it reboots to this special download mode. because we don't have any form of ROM I thought the first priority should be to see if we can make a backup of it, outside of MS encrypted zune backup I mean
the software is old so perhaps it doenst work with newer hardware, but then it does with android soooo.....
LudoGris said:
Good luck with this, it would be nice to see a 7.8 ROM on this device before I go buy the ATIV.
Click to expand...
Click to collapse
don't hold your breath, I still don't really know what im doing, consider this playing.....in a mine field
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
tayfelix said:
Hmmm. If this does work. Will it ever work on focus flash/ omnia w? Cuz it got the same spec except different screen sizes
Click to expand...
Click to collapse
That depends what you mean by work, will the focus flash connect to various diagnostic tools? yes probably, will it be possible to download the ROM? maybe, beyond that I haven't got a clue
starting to run out of ideas, I think either the download mode via QPST is disabled or, and more likely, the driver isn't correct, when it enters the arm9 fatal error screen it is still using same driver, the same driver samsungs download mode uses, but both won't talk to QPST unless I enable diagnostic mode within windows phone OS, the prob with that is that it won't then allow access to the file systemSent from my fake Lumia 900 using XDA Windows Phone 7 App
It also have diagnostic tools .
tayfelix said:
It also have diagnostic tools .
Click to expand...
Click to collapse
be careful, you can bugger up your device!i will write a more detailed guide later
First things first, you will need to make sure you have the samsung diagnostic tool install
bring up the phone dialer and dial
##634#
you will now see a diagnostic app on your app list, run it and type in
*#7284#that will enable you to change the USB connection mode,select
Modem USB diag
OPTIONAL - Typing in the following code will bring up the diagnostic root menu
#197328640#you can find a full list Here Many of the codes on that list just run functions found in the root menu
Bare in mind that pissing around with some of the things in there will bring about a swift crappy end to your day!
plugging in your your phone at this point will install a Samsung COM driver
next download and install QPST on your computer, run the config part of that, it will ask you to select your phone, you will need to add a com port, it should then list your phone to connect to it
you can then edit the EFS, service/phone settings, download settings
you will need to know your SPC number, mine was already 0000000, there are ways of working out your number if leaving it all at zeros doesnt work.
use the service editor to read the phone settings, it will ask for your SPC, once loaded,you can save those settings to a file, very important ifyou screw something up
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
tayfelix said:
Cool, I will try it when I'm free. Hmm what's UR focus s BOOTLOADER, firmware version and diagnostic version ?
Click to expand...
Click to collapse
as reported in windows phone about screen, note that the Focus S and Omnia 7, has a firmware update that will stop any interop unlocking, i had it installed but it killed my battery life and my phone reception so i took it off, id suspect the bootldt vs will be different between devices, even though they were released at the same time
bootldr 6.5.16.0
firmware 2103.11.10.1 (not the Samsung update that breaks interop)
diagnostic 0923 (not the Samsung update that breaks interop)
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
tayfelix said:
Er it's focus, focus s , focus flash/omnia w and omnia 7 that are affected by the freakin update. This is my version from the about info
Firmware: 2424.12.04.1
Bootloader: 6.4.4.0
Diagnostic : 1109
Note : I cant interlop unlock my omnia as Samsung fixed the exploit in the new firmware version
How did u remove the firmware ?
Click to expand...
Click to collapse
I made a backup before I installed it
I think we can get an xap of my version of the diagnostic tools, but the firmware update also changes drivers an a few other things, those cant be changed, if we could send custom cabs to the device we are laughing, but we cant, to cab send requires the cab to be signed, and the device would need to have that certificate, which cant be put on whilst its all in use
:S don't think so as diagnostic tool is based on firmware I think.
tayfelix said:
:S don't think so as diagnostic tool is based on firmware I think.
Click to expand...
Click to collapse
try this, remove your existing diagnostic app and install this xap
How can u install a xap..
Is your device still unlocked? The Samsung update will stop you applying the unlock but if you had it already installed it will still work, if it is unlocked then use an cap deployed, my link to the wee guide details how to do it, if it's interop unlocked but you can't install an xap deplorer the use the xap deplorer included with the WP SDK
Sent from my Lumia 900 using XDA Windows Phone 7 App
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
tayfelix said:
it's ok. I will just wait for someone to be able to unlock the device as I already got the exploit for interlop unlock patched
Click to expand...
Click to collapse
well there isn't anyone working on unlocking it as far as I know, so if its going to happen then we need to do it ourselves.
Ive exhausted just about every avenue I can think of getting access to the device, ive been able to dump parts of the RAM but still not the ROM,
EFS is writable but I cant get in to the secure folders. The only way I can think of for getting the ROM is to get it working in one of the two download modes, both will not talk to anything tho, perhaps if I had the commands to copy the ROM I could just send them in the hope it will reply but it sure as hell isn't saying anything to the commands I have sent.
Hmmm. Must there be a exploit? Zzz there's are very little/no hackers having a focus s or a focus flash/omnia w. they all have 1st gen devices I think.
Im trying to root my phone, its an Xperia Z from tele2 in sweden, C6603, android version 4.1.2, version 1.0.11.a.1.253, when im on this part of the tutorial it won't work, it doesn't do anything when im entering display on service test, just flashes some colors, so can you try to help me? im on part 9 but nothing happens when i press the power button to power down the screen many times, i used droidviews.com as the guide, for the toolkit, please help me, i have tried everything possible, changing to msc mode didn't work either
7. You will see the Service Menu of your phone, select “Service tests” from the available options.
8. Now select “Display” (screen will turn white), the toolkit will now start executing some commands.
9. Now press the Power button to turn off the screen, wait for few seconds and press the Power button again in continuation till you hear a beep sound. Keep observing the command prompt for outputs.
10. Then you will see “transfer files to your phone part2“, “installing busybox,su,Superuser,etc…“.
11. Finally, you will see “Cleaning up“ on the screen and then the phone will reboot automatically and when it boots, it should be rooted.
im a complete newbie with rooting, fine, i rooted my old galaxy 5, gt-i5500 using some app named one click root, and another app named z4 root also worked, please help me out here, bootloader is unlocked, according to the service test thing, but it still won't root my phone
That isn't for 253, ready the stickys for the latest methods.
XperienceD said:
That isn't for 253, ready the stickys for the latest methods.
Click to expand...
Click to collapse
which ones? as i said, im completely new to rooting
Serathas said:
which ones? as i said, im completely new to rooting
Click to expand...
Click to collapse
You're not new to reading though are you. General section, start at top, READ thread titles, find appropriate thread, READ it, watch a video even, done.
watch?v=sXbsgYVuRZU im using this video guide on the binary root toolkit (doomlord v4 root) its saying it can't complete cause the file system is set to read only
img35.imageshack.us/img35/2018/rootzd.jpg
Serathas said:
img35.imageshack.us/img35/2018/rootzd.jpg
Click to expand...
Click to collapse
Since you can read and did follow the instructions but it still isn't working, your phone is probably broken.
im trying my best here to fix it, buy its still saying the phone is set to read only or something and i have looked everywhere for how to remove a read only partition from a phone and repartition it to still work, but also become writeable
Oh, and i bought my phone less than a month ago, so i don't think its broken
Or as bricked as these Qualcomm devices CAN be?
Hey all,
The TL;DR is basically where the list starts
I was running Blu's TWRP v45, the latest PureFusion, Blu's latest Custom kernel, had OB15 firmware underneath. I had been SO USED to simply downloading the newest firmware from kamilmirza's AFH page and just flashing it + it being totally fine that I did it without thinking for OB16. I wasn't too worried because about a week ago I had flashed the unofficial Oreo Lineage and it worked just fine! Plus, I just assumed if it died I could just restore a backup or re-flash the older OB. But as soon as I flashed the new firmware/modem by itself this time on an otherwise perfectly running device, I only saw the OnePlus splash screen. No booting, no access to recovery, no NOTHIN.
I tried flashing the beta TWRP version afterward via fastboot but no dice. Also tried temporary booting via fastboot to it, flashing Blu's again, booting to that. Everything the same result. Splash screen & nothing more. I then went to the extent of trying to format all the partitions and flash a boot.img or do a "-w update" or "flashall" command via fastboot. Because everything out in the universe is a recovery-flashable-zip, it seems like there's no way I can flash the necessary OTA stuff to bring it back to life!
My only remaining idea is getting this damn unbrick tool to work (duhh). I can see the Qualcomm HS-USB QDLoader 9008 in device manager after doing the Vol Up (only) and plugging the cable in. BUT the MSMDownloadTool just cannot see the device. Not in bootloader, not in the weird Vol-Up/cable state. [This is with Qualcomm drivers QUD.WIN.1.1 Installer-10037.3 Setup.exe, the official OnePlus drivers, ADB & Fastboot installed.]
Sorry for long explanation. In the end, what I'm left with is:
Blank formatted partitions (I hope... I'm not even positive they wound up formatted from the fastboot commands)
Fastboot is detected, but no ADB devices are found
Can get to bootloader, but nothing else
No recovery access - Flashing beta akhilnarang Oreo recovery does nothing. Flashing stock recovery does nothing. Flashing Blu_Spark recovery does nothing. (The fastboot commands succeed though each time somehow)
So far the only suggestion I've received is trying the MSMDownloadTool/unbrick process on another computer.
Does anyone have ANY ideas? From my experience, it seems like what might help me would be if a folder with the specific partition images existed for the OTAs, like how Google offers. (boot.img, recovery.img, user-data.img, system and so on). Am I wrong in thinking that? OnePlus has told me this simply does not exist and cannot give me anything like that (don't know why, when they already offer all the OTA flashables...)
PS - OnePlus support just absolutely refuses to even let me communicate to a "level 2" representative to ask a couple of the more technical questions about it. I can't understand why. They are insisting I start an RMA and send it for repair. They even initially scheduled a time for me to talk to higher level rep and then thought up a reason to cancel it via email an hour or so later...
Edit: Just in case the thread gets large and people don't read further posts, this is using:
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. Have the watermark bottom right of desktop
It's with the stock DASH cable
Tried multiple ports
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times
Tried starting the tool BEFORE the device is plugged in, as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
HOW IT GOT SOLVED:
At the end of the day, I had to fight and convince OnePlus support to grant me a remote session with Level 2 Support.
(Attached final image) These two password protected RAR files had almost identical tools as the Unbrick tutorial on XDA.
The major difference was that MSMDownloadTool was version 3.0.8 ***does anyone have this version??*** I can't get into these RARs. The 3.0 tool circulating did not work for me. We might need the newer version as time goes on?? Otherwise, the process was identical.
Unfortunately, the image they used was for 7.1.1. I had to unlock the bootloader and after doing that and getting OB15 & the RR build I wanted, etc, I then realized my phone was force-encrypted as well.
The only toolkit that worked for force decrypting once everything else worked was:
OnePlus_3_3T_5_64bit_TOOLKIT_by_Neisor
Finally, something like 3 clean flashes later, we Gucci.
Thanks for the attempted help to those that did! Hopefully this can help someone else.
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
As long as you can turn your phone off and on, it's doable. But you need to do that USB plugging + volume up thing while phone is totally off (you can hear Windows making bling when you connect it while pressing volume up, but phone itself stays screen off). And there shouldn't be anything on the screen before/while MSMtool do its job.
You can try different USB ports too.
Eremitus said:
Which Windows do you have? Have you tried MSMtool in safe mode? Or disabling Driver Signature Verification (any Windows after XP). I have got my phone so messed up that it was showing many lines with red "failed" text nearly on everything. No OS, no recovery, no boot, I think even modem was failed. This screen but I had way more fails https://forums.oneplus.net/attachments/win_20160928_21_31_49_pro-jpg.459494/
Click to expand...
Click to collapse
Hahaha yes...... That's why I made this post though! It SEEMS like it should be possible to recover from this since fastboot commands + bootloader work! It SEEMED like it would be easy to recover from if anything went wrong... But, here I am.
Oh yeah forgot to mention ~
Windows 10 Pro 64-bit
Test mode for the driver signing is enabled. That part of the process went totally fine with BIOS and installing stuff, etc.
Also, shot in the dark but might @Funk Wizard have any ideas? Sorry to call out for this
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
btw, I messed up my phone in nearly similar case, flashing wrong firmware when using leaked H2OS ROM.
Eremitus said:
Hopefully someone knows better how to solve this. For me the MSMtool part is always the hardest part too, usually it finds the phone, but throws some strange "Sahara communication failed" error. I noticed that even different USB cable can be a problem, but since your Windows finds "Qualcomm HS-USB QDLoader 9008" I guess that's not the case. Does it say something after that "Qualcomm 9008" -thing? For me it shows (COM3 or COM4 depending on which port it's in).
Click to expand...
Click to collapse
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
Hmm, ok.
Stock dash cable works, so that part is ok. Also usb3.0 ports should work too, atleast for me. So everything else seems to be ok except the MSMtool itself
Try different cable, bin there done that!!
purplepenguin said:
Yeah sorry again for not being more clear lol
It's with the stock DASH cable
Tried multiple ports (but no USB 2 ports hmm)
Unfortunately it just doesn't show up in MSM at all, even with hitting 'enumerate' button multiple times.
Also tried starting the tool BEFORE device plugged in as well as after
This is what Device Manager shows (attached) but just nothing in MSM all the way up & down
If I find a solution I'll definitely put it in OP for others
Click to expand...
Click to collapse
I hope you find a solution, since my experience sounds similar to yours Ill share it and maybe you can find something to help out.
I was exactly where you are for about 3 hours last night.
Boot would always get stuck at the splash screen. Could boot into Fastboot, tried using the Skipsoft tool to fastboot flash a stock image but it kept failing.
As far as the Unbrick Tutorial goes, I know the first thing I kept messing up was thinking I needed to press the power button while holding the volume up and connecting to the PC
Also when I tried to manually update the driver on "Qualcomm 9088" it said it was already up to date.
Then I just ran the MSMTool it flashed 6.0.1 back on my phone and I was back in business.
Im sure this is the guide you followed: Here
I found another on the oneplus forums that is essentially the same but goes into a little more detail in the steps: Here
Since I was back completely Stock including Recovery I went ahead and sideloaded OB16 to get the firmware and modem then went about rooting, unencrypting etc...
Lost a few days worth of files but I'm back running LunuxOS Oreo right now.
Good luck I know how you feel. :good:
I've got it revived! I'll update OP. Sadly, it required OnePlus's intervention.
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
guilhermeferrari said:
Hi. Trying to do brute force to get the passowrd here, don't you know how many characters that was? It will take days in my machine to search from 3 to 9 characters...
I think it is impossible to you to know, but if you know if they used only letters or something like that, it would be very useful
Click to expand...
Click to collapse
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
purplepenguin said:
Sorry man. The OnePlus guy was ready an hour early before our appointment time. So I didn't have time to set up screen recording or anything
if I had to narrow it down more itd only be like 4-9 chars lol I know that's not much help... Definitely let me know if you get it open though please! It would probably help a lot of us!
Click to expand...
Click to collapse
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
namefaisal said:
Well, I know the password. It's 10 character long. 7+3(7english small latter with 3 Numbers).
L2 Driver password is very very very very very loooooooong. can't even count accurately.
Click to expand...
Click to collapse
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Yeah, I got it open
purplepenguin said:
Jeez so wait you got it open or not?? Confused lol
Got the newer download tool ??
Click to expand...
Click to collapse
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
New Files without Password
namefaisal said:
Yeah it's the new 3.08 msmdownloadtool. OnePlus3T_28_A.57_171012.zip
I know the password and I won't share that but I will upload an UNLOCKED zip on google drive tonight. L2 Drivers too.
Click to expand...
Click to collapse
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
@Sam Nakamura
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
cdorrell12000 said:
This totally worked for me. Yes it put me back on 7.1.1 but I have been having issues trying to flash Oxygen ROMS and getting them to take. Phone is back to bone stock which I wanted for now and is working great. Thank you for sharing,
Click to expand...
Click to collapse
You are most welcome.
Sadly everyone gets unbricked with these files but My device didn't. I have to send the device to the service center now. It seems my case is a hardware issue. Tough luck
namefaisal said:
Latest 3.08 msmdownloadtool re-archived without password from OnePlus3T_28_A.57_171012.zip
https://drive.google.com/file/d/1kp2SBmhAByydol97o0yVlurVue9Ow8Aq/view?usp=sharing
And the L2+ driver.zip re-archived without password
https://drive.google.com/file/d/1JL_sRg86CczUeZ2cfw8GY6rxc43myif8/view?usp=sharing
Click to expand...
Click to collapse
thanks a lot saved my day !!
purplepenguin said:
@Sam Nakamura
Click to expand...
Click to collapse
Sorry, I just saw your mentioning somehow I missed it, happy you got your phone back already, unfortunately not independent for big OP, did you guys already share this new 3.08 MSM-download-tool to the well established threads or did you I missed this too? This information and according files should be shared with the community and easy to find for those poor souls who unintentionally killed their beloved device...
---------
Edit: further sharing isn't necessarily needed, you did already a pretty good job by naming the thread and describing the situation thoroughly, only suggestion could be to link the updated MSM-download-tool download to the first post with some hint, just an idea though...
Cheers
Sent from my OnePlus 3T using XDA Labs
Using Odin files to update a Samsung AT&T model will almost always result in a factory reset being performed, and I've also seen the same thing happen when trying to update via OTA zip in Recovery. I'm providing this package for anyone still using the S5, to be able to update software without needing to do a factory reset. I have personally verified that these files will perform the update without wiping any data. These files will update you to the Build/Baseband ending in QD1, Android 6.0.
My zips are compressed extra small for space and bandwidth savings. The default Windows extractor can't handle it, so you'll need a 3rd party tool like 7zip, WinRAR, etc.
Happy flashing!
https://www.androidfilehost.com/?fid=1899786940962576350
Worked great..Thanks! But....
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
3rdRockfromSun said:
You are theman for this! I have a 900A AT&T and have struggled for days to get it unlocked, upgraded and working without tripping the secure software alert. I started with a 4.X maintenance OS, then rooted, SafeStrapped then pushed this update via ODIN and it worked. Now, the only issue i am having is apps crashing continuously. Started with google play and play services now spreading. I ASSUME this is due to apps not getting updated in the update to 6.X. Correct me if I am wrong. I have updated those via APKs along with others to new versions yet it still happens. Now its also Chrome, File manager etc. Is this maybe a code bug, or am I missing something here? Thanks again
Click to expand...
Click to collapse
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
iBowToAndroid said:
No idea. Can't really diagnose app crashes - too many possibilities.
Also: hopefully you're now aware that you're not rooted any longer and (probably) can't ever root it again
Click to expand...
Click to collapse
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
3rdRockfromSun said:
Yeah I saw that, but thats ok. My biggest objective is to get it unlocked from AT&T so I can use it (this whole venture has just turned into a learning/fun toy to play with now) on my carrier. That is yet TBD. Any thoughts on that?
Click to expand...
Click to collapse
https://www.att.com/deviceunlock/
Thanks in advance for any help, short version at top, details below.
-- Short version:
Please help me recover my data, and phone if possible.
I need the data, esp texts and notes, for both personal (some family members have passed on) and business.
I have a new Galaxy S21 and / or PC Smart Switch ready to receive data backup if we can evacuate it from the S5.
ODIN flash seems to pass but has 'Resizing Data' fail, and phone still won't boot past AT&T logo screen.
All web searches seem to say Factory Reset is my last option, but I don't want to lose the data.
Please share ANY advice on how I can recover the data.
-- More details:
Phone = SM-G900A Samsung Galaxy S5 AT&T
Use = pristine, never rooted, modded, or unfortunately backed up
Status = will not boot, passes screen 1 'Galaxy S5', screen 2 'Samsung script', then stops on screen 3 'AT&T globe logo'
More details = Used clean for ~7 years, then on day x, saw phone automatically complete a system update (green screen, sprockets, "your phone is updating"), which was surprising as it's years after it is no longer supported by AT&T. After that update, I continued to use the phone that day, but it then rebooted automatically and stuck on the AT&T globe logo.
Attempts to fix = soft reset, battery pull, can't get into SAFE MODE, can get into and out of recovery mode, found this firmware (THANKS @iBowToAndroid), used multiple ODIN (Odin3 v3.13.3_3B_PatcheD, Odin3 v3.14.1_3B_PatcheD) to flash it (my first Android flashing experience). On flashing process, ODIN on PC shows 'PASS' and log shows "<OSM> All threads completed. (succeed 1 / failed 0)", but phone shows 'Resizing Data' failed:
"
Supported API: 3
-- Installing package...
Finding update package...
Opening update package...
Verifying update package...
Installing update...
Successfully installed package.
-- Resizing Data...
Can't open dir '/data/user/0/com.sec.knox.bluetooth' (Permission denied)
E:failed the resizing-data
"
PFA screen shots
Martin2019 said:
Thanks in advance for any help, short version at top, details below.
Click to expand...
Click to collapse
Trying the "wipe cache partition" is the only thing I can think of
iBowToAndroid said:
Trying the "wipe cache partition" is the only thing I can think of
Click to expand...
Click to collapse
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
The string seems to indicate a 'user data' permission error?
Is there any way to debug the logic of the firmware or slog through the 'Recovery Logs' to determine and resolve the cause of the permission error?
When the problem began, I had an SD card and SIM card loaded.
I've since removed both in trying to address this, also per 'web advice'.
Any chance putting them back in helps somehow?
Any other options available via apply update from SD card or ADB?
Any way to setup the Android OS as a secondary drive to another machine to pull data out that way?
I've done similar things with Windows OS in PC environment, but I'm not seeing anyone trying that with Android.
If I am really stuck with factory reset, are there any data recovery programs I could try afterward that work with the G900A?
So far I've looked at Dr Fone, Tenorshare, EaseUS, FonePaw, and D-Back, and none seem to work with the AT&T model variant.
Maybe that's just because they don't have access to AT&T firmware available to install, but if I clear the stuck boot via FR, they then might be able to get some of my data back via drive scan - whatever data is not truly overwritten by the FR?
Martin2019 said:
Short version:
THANKS for the quick reply, very much appreciate your help.
Am I really left with only a Factory Reset and then trying to use Data Recovery software to get ‘some’ data back?
I really don't want to give up on the data, so I'm still trying anything I can think of in research and repeated attempts.
More details:
I have tried the recovery mode 'Wipe cache partition' option before and after using ODIN.
I've tried doing it 'twice' per recommendation of some of the web advice I've read in trying to research this.
I've noticed that sometimes the colored highlight of the 'Reboot to bootloader' option then turns background green instead of usual blue, but I don't know why, or if that matters.
Still, the ODIN flash effort always returns the permission error, and the boot always sticks on the AT&T logo.
Click to expand...
Click to collapse
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
iBowToAndroid said:
I own and run a business that performs SIM unlocking and other software-related services for mobile devices, so we see situations like yours quite a bit. And I don't know of anything else that you can do. From reports, we've heard that none of those "recovery services" actually work to recover any data, after a reset
Click to expand...
Click to collapse
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Martin2019 said:
Disappointing to hear bad news, but appreciate your effort and insight in providing it, thanks.
I've learned alot in researching it.
I just wish I'd known it before the problem, which I'm sure you also hear quite a bit.
Please let me know if you think of anything else I can try.
Click to expand...
Click to collapse
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Totally agree, and totally on me for not having a backup.
I was just foolish enough to not know yet how easy it is to back up.
Give me 10 minutes of life again now in this phone, I use Smart Switch to backup, and I'm off to a new phone, or even FR on this one and reload.
Now where did I put my Delorean...
iBowToAndroid said:
You can never trust a mobile device 100%, especially not one that's 7 years old. That's why anything that's that important needs to be backed up at all times
Click to expand...
Click to collapse
Have you ever tried a 'combination key' approach to get data access?
As in...
Smart Switch on PC won't connect, but ODIN does show 'Added'.
I don't understand the granular details, but hoping you might...
Could we use both Smart Switch and ODIN in some combination sequence that would allow Smart Switch to pull the data off to a Smart Switch PC backup that I could then throw onto a new phone?
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
iBowToAndroid said:
When it's in Downloading (firmware flashing) mode, a modem port is used. The modem port is also there when the device is booted up in Normal mode, but that's not useful for extracting any data off of it. I don't know what Smart Switch uses, but I would assume File Transfer (MTP) and/or ADB. And those aren't fully functional until the device fully boots up.
Do you have a screen lock on the device?
Click to expand...
Click to collapse
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Martin2019 said:
No lock on device, just swipe to go from 'lock screen' to home screen, prior to this boot problem obv.
One of the data recovery sw that I tried (EaseUS I think) did reach a screen asking me to enable USB debugging to continue, but I don't think I can do that without booting up.
I 'think' I remember that screen saying something like 'MTP device' connected, when it asked me to do that.
Any way to sneak into MTP mode from that?
Click to expand...
Click to collapse
Any 3rd party software will require ADB to be enabled. Smart Switch is the only one that *might* work just over MTP, but I'm pretty sure MTP doesn't fully load until the device is booted. Even if it did, you would likely need to allow on the popup message. Does the phone show up as a device/drive when it's plugged in while sitting on the AT&T logo?
I think you're asking "does the phone show up as a device/drive" in something like a windows file explorer, and the answer is unfortunately no, or at least not that I've found yet - I've tried several times now, and I'm still trying any combinations I can.
For now...
I can get EaseUS to show 'MTP USB device' per the pic attached in my last, but can't really get it to connect past that point, as it asks for USB Debugging, which it appears I can't do due to stuck in boot loop.
Smart Switch seems to try to connect for awhile, then says it failed to connect, so I think I'm then left with 'Samsung Smart Switch Emergency Software Recovery' (PFA).
Do you have experience using it?
Do you know if it could work to reload the firmware / OS without wiping the data?
AT&T Advanced Technical Support guy says it gives you an option to choose whether or not using it resets the phone (wipes your data), so he thinks (hopes) that would work, but he didn't sound certain at all.
I understand your point on the pop up message user prompt for File Transfer Mode. I used that mode many times in the past, so I'm hoping it might default on the phone so we wouldn't need to answer the pop up prompt to reach that status , but I'm obv not sure about that.
Per the speculation in my last, do you know of any combination approach we might use to get the desired result, like maybe... use ADB somehow to change 1 parm value to reach MTP mode, then use that progress step to enable Smart Switch to connect so we could offload the data?
Thanks again for your help
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
2. But if the phone never shows up as a device/drive (would show up under "Portable Devices" in Windows Dev Man), then it's not loading fully - and it normally doesn't do that until it boots past the carrier splash screen.
3. Even if it did boot fully and showed up as a device/drive, the MTP pop-up prompt shows up every single time you connect the device. There's no way around that. So the device would show as empty, with no files or folders, until you tapped "Allow" on the popup.
4. No, there's nothing else you can do to turn on any other connection modes
iBowToAndroid said:
1. MTP is the same as File Transfer. So when the phone is turning on, it starts loading that connection. You might see "MTP USB Device" or something similar in your Windows Device Manager
Click to expand...
Click to collapse
Device Manager does show an entry for the phone connected via USB cable:
Under 'Disk Drives' as
SAMSUNG MZMTE256HMHP-000MV
Under 'Universal Serial Bus Controllers' as
SAMSUNG Mobile USB Composite Device
Please tell me that helps us somehow?
Hello guys, I'll try to explain what happened giving just a few context that may help give me some right direction to recover the user data that were in the phone.
As this thread got longer than I expected, summarising:
Moto G XT1033 drained battery, got into bootloop, only fastboot was working, couldn't get into recovery mode ("boot up failed"). When I tried to replace battery, after power on it's now bricked (as "qhsusb_bulk" in PC). My main goal, save user data (whatsapp folder mainly), to flash and restore Android.
Whole situation detailed, what happened:
I have a Motorola Moto G 16GB Music Edition Dual SIM XT1033 (Music edition) 2014, sold in Brazil. It was working for all these years fine, avoided upgrading Android KitKat from 4.4 because it just worked fine. In past months I noticed the battery holding less and less charge, but as I intended to buy a new phone soon I didn't care.
Unfortunately, couple days ago I heard the sound of notification "low battery... powering off". Then I plugged the charger cable and waited some time, after that, I thought it would just boot up normally, it showed "M" loading screen, with the animation etc, but it went to black screen and loop to loading screen again and again.
I tried to hold power and volume down, it went to fastboot, and when I tried start "recovery mode" but it would just say "boot up failed".
I searched for threads and people who had issue like mine and in fact, I found someone who described exactly the same problem I had, user named @ravibhat here: https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492
While he didn't say he was able to fully flash his smartphone and get it back working, he said he was able to recover all his user data. I was really trying to follow his steps to at least, recover all user data, BUT, before that, my Moto G got hard bricked.
As I have another Moto G XT 1033, the exact same model as this one, but with a working battery, I thought it would be plausible to replace the battery so I could have more safety when fixing the phone, but it didn't work as that. Instead, after I disconnect and reconnect the battery, the Moto G is now hard bricked, as it doesn't boot up anymore, not even holding power + volume buttons, holding for 60s or 120s, none, nada. Rarely, the LED light blink once, nothing more. I connected to PC and it recognized as "qhsusb_bulk", after disconnecting and connecting the phone back to Windows 7, it automatically tried to install drivers and now it would just show "Qualcomm HS-USB QDLoader...." in device manager .
Now I have two issues, first, make it come back to state where I could open fastboot. Second, try to dump/save all user data, to then make a total flash/factory reset to see if I can get it working again.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) and this (https://forum.xda-developers.com/moto-g/general/guidy-to-unbrick-hard-bricked-moto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
I don't want to just go and try a bunch of (possible danger) commands and guides without having some experienced people giving advices on how to perform actions, or even if it's possible to "make some backup" of current situation, "copying whole partition", etc, before installing and flashing anything.
Device INFO:
Android version was 4.4. No Root. Bootloader is LOCKED. No customizations.
ADB Debugging state is unknown, probably it was just the default value.
What I want:
I want to get a copy of all my internal storage data, eg: WhatsApp folder, etc. Better if I could get whole storage image and just flash OS and boot loader to get back as it was...
Trying to flash it in any way that causes data loss would be my last option, but @ravibhat who had same issue few years ago couldn't even get it back working again.
What @ravibhat found out:
He thought bootloader UNLOCK would wipe all internal memory user data, but he did it and still could get all files using TWRP 2.8.x.x.
"To root the phone, I’ll have to UNLOCK the Bootloader."
"ADB can be used to backup using PUSH, PULL (may or may not require Android USB Debugging enabled)": he couldn't get it to work using adb push/pull.
Please, I would really appreciate any help from anybody, also from following users @ravibhat , @lost101 , @Teddy Lo , @Kamin4ri , @oversleeper , @jdawc7 , @sd_shadow , @SahilTech , @liveroy , @bouba148 , @bejunk , @Wolfcity, @skad00sh, @FabioSan.
After searching for hard brick and "qhsusb_bulk", I found this thread (https://forum.xda-developers.com/mot...oto-g-t2833798) and this (https://forum.xda-developers.com/mot...oto-g-t3875035) that says it will recover from it, but it didn't mention IF IT WILL compromise or delete all user data. Will it?
Click to expand...
Click to collapse
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
oversleeper said:
It should not delete the user data. I'm saying this out of logic though, I've never tested it.
Technically the Motorola qboot utility will ripristinate the bootloader only, without modifying any other area of the memory.
Click to expand...
Click to collapse
Thanks @oversleeper, I was a bit afraid because of the "blank-flash.bat" name.. but as I don't know of any other method of beginning this recovery other than unbricking using this qboot bat script, I will end up giving it a chance.
As I said before, Windows 7 auto installed the "Qualcomm HS-USB QLoader 9008" driver as soon as it recognized the "qhsusb_bulk". Do you think I should try to uninstall it and start from step 1 on this guide (https://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798) installing the "Riff BOX JTAG drivers + Driver Signature Enforcement Overrider"?
Yes, I suggest that you install the driver's as advised in that old thread. Also, you will need to use the right qboot utility, for the right model and version of the bootloader that you have or it won't work. Unfortunately I can't help with that, you will need to search the internet and may luck be with you.