It's been a long time since I tinkered with flashing my phone and the only reason I started today was to [attempt to] fix my sudden wi-fi death issue: https://forum.xda-developers.com/sprint-one-m9/help/wi-fi-dead-bluetooth-functional-t3589792
Alas, now I've managed to wipe my M9 and fail to install any ROM, such as attempting to install 3.41.651.4 Full Signed Firmware then Bad Boyz (which after resolving mounting issues claimed success multiple times).
Download mode:
LK-1.0.0.0000
[email protected]
OpenDSP-v29.2.6-00492-M8994_0514
OS-2.6.651.11
Jun 26, 2015 13:48:09(556164)
Bootloader:
Software status: Modified
Unlocked
S-ON
TWRP 2.8.7
Problems ranging from unmount of /system volume to rom seems to install successfully, but reboot goes straight to bootloader, no OS.
slmclarengt said:
It's been a long time since I tinkered with flashing my phone and the only reason I started today was to [attempt to] fix my sudden wi-fi death issue: https://forum.xda-developers.com/sprint-one-m9/help/wi-fi-dead-bluetooth-functional-t3589792
Alas, now I've managed to wipe my M9 and fail to install any ROM, such as attempting to install 3.41.651.4 Full Signed Firmware then Bad Boyz (which after resolving mounting issues claimed success multiple times).
Download mode:
LK-1.0.0.0000
[email protected]
OpenDSP-v29.2.6-00492-M8994_0514
OS-2.6.651.11
Jun 26, 2015 13:48:09(556164)
Bootloader:
Software status: Modified
Unlocked
S-ON
TWRP 2.8.7
Problems ranging from unmount of /system volume to rom seems to install successfully, but reboot goes straight to bootloader, no OS.
Click to expand...
Click to collapse
So you can boot to TWRP but you can't install an OS? Can you restore a back up to see if it will boot?
Not gonna lie; didn't do a proper backup besides a data dump from root directory manually to my computer. I know better, but here I am anyway :\.
slmclarengt said:
Not gonna lie; didn't do a proper backup besides a data dump from root directory manually to my computer. I know better, but here I am anyway :\.
Click to expand...
Click to collapse
Bruh.....the only thing I can think of is RUU nougat .-.
I got Bad Boyz to work through a very convoluted and unclean process. I shouldn't have bothered trying to flash a ROM because Wi-fi is still broken (probably dead hardware) and the phone is outright dysfunctional now. I can't even make a call without it failing and crashing.
This explains my new problem... https://androidforums.com/threads/problems-with-dolby-audio-on-htc-one-m9.1110892/
Safe mode audio test via DIAG suggested even worse problems as it did not succeed.
Uh :\
slmclarengt said:
This explains my new problem... https://androidforums.com/threads/problems-with-dolby-audio-on-htc-one-m9.1110892/
Safe mode audio test via DIAG suggested even worse problems as it did not succeed.
Uh :\
Click to expand...
Click to collapse
Damn son so hardware related issues not software? Or do you think some might still be software related?
6th_Hokage said:
Damn son so hardware related issues not software? Or do you think some might still be software related?
Click to expand...
Click to collapse
Not sure, but I'm done with it and got a new phone.
Thanks for all your help!
slmclarengt said:
Not sure, but I'm done with it and got a new phone.
Thanks for all your help!
Click to expand...
Click to collapse
Upgrade or same but new?
6th_Hokage said:
Upgrade or same but new?
Click to expand...
Click to collapse
Upgraded; the time was right.
slmclarengt said:
Upgraded; the time was right.
Click to expand...
Click to collapse
Ahh I see well hope you enjoy the new phone
Related
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
JayRolla said:
Unlock bootloader, install Android Revolution thats been updated with latest release and you are good to go. No reason to wait till they let it work for yea when you can do it yourself.
Click to expand...
Click to collapse
Thanks for the advice, but others are getting the update OTA, without root or downloading Android Rev.
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
redpoint73 said:
Some M8 owners may see a delay in getting the OTA, as it rolls out sequentially, by some means (I've seen AT&T suggest its by IMEI number). A minority of folks will never get it, just by some random fluke or other (as happens on any OTA).
If you don't want to wait, the RUU is already posted. You can download to a PC, and run it with your phone connected. But it will wipe user data.
http://forum.xda-developers.com/showthread.php?t=2757462
Click to expand...
Click to collapse
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Also, has everyone that attempted to download things manually received the update?
I would really appreciate the responses
Click to expand...
Click to collapse
How did it not work? As long as you are completely stock with cid cws__001 it should work.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
sassij said:
Hi All,
I have been trying to get the FW update with extreme save mode for almost a week now.
I check for software updates daily and I get the NO UPDATE found message.
Called At&t and tech support is as useful as my 3 years old kid.
Does anyone have the same problem? Solutions?
Thanks
Click to expand...
Click to collapse
download ota package from here http://www.androidfilehost.com/?fid=23487008491963146
put it on your micro sd card
boot to recovery "vol up and power 10 sec, vol down and power until boot loader comes up and navigate to recovery"
once in recovery its either vol up and power or vol down and power for a few seconds for advanced options
choose install update from external sd.
sassij said:
Thanks for the tip, I tried that and it wouldn't work. Do I need root or s-off?
Click to expand...
Click to collapse
No, the phone does not need to be modded to run the RUU. Its a "official" update/recovery tool provided by HTC. If you phone is stock, it should work, as the above response also indicated.
If it "wouldn't work" it would be more helpful to give details, if you want proper help. Not just say it didn't work. What step did it fail at , any error message, etc. Also, the current state of your phone (root, unlocked bootloader, etc.), as we can only assume based on your comment about root, etc.
RUU failing on a stock device is usually a USB connectivity issue on the part of your computer (not a problem on the phone's side). Install or re-install the HTC drives, try a different USB port, or a different computer (if available). If on Windows 8.1, that version is a known issue and will not work with the HTC drivers. You can also try re-downloading the RUU to make sure it wasn't damaged/corrupted during download.
So frustrated!
#1 was regular attempt w/device as is
#2 w/factory reset
#3 unrooted
#4 rooted and changed some system files (that I remember that had been modified....a camera mod, volume mod etc)..i thought Factory reset would have done that.
All 4 Failed
At a loss at this point.
Any help appreciated!
I have had a problem with FOTA twice as well. I also unrooted, and did a factory reset. Changed BBS back to a user app before unroot. Both times I got the FOTA it begins to install, gets to maybe 10% (guessing here) and then the Andy with the red triangle pops up with "ERROR!" beneath it. After that I have to boot into recovery and manually reboot.
Hopefully this doesn't hijack your thread, but when I tried to install the update with ADB, it tries to load the update, then ADB cannot see the device anymore.
rockky said:
So frustrated!
#1 was regular attempt w/device as is
#2 w/factory reset
#3 unrooted
#4 rooted and changed some system files (that I remember that had been modified....a camera mod, volume mod etc)..i thought Factory reset would have done that.
All 4 Failed
At a loss at this point.
Any help appreciated!
Click to expand...
Click to collapse
I also am having the same issue. I tried once with root, once without, reset device and even tried removing my sd card. And it still fails. I have never done anything but root my device so im also very confused.
str33tprintz said:
I also am having the same issue. I tried once with root, once without, reset device and even tried removing my sd card. And it still fails. I have never done anything but root my device so im also very confused.
Click to expand...
Click to collapse
The only way may be to revert all the way back to 4.4.2 and start a fresh (watch out for all your data - back it up as this will wipe it probably)
blueether said:
The only way may be to revert all the way back to 4.4.2 and start a fresh (watch out for all your data - back it up as this will wipe it probably)
Click to expand...
Click to collapse
I started to install 4.4.2 with adb in recovery following Doomlord's guide but as soon as I give the install command adb suddenly cannot see my device ?
Adb commands work fine up until that point, I'm throughly confused now. Do I need to unlock my bootloader to do that? I was under the impression that root and unlocked BL were not necessary for that.
I used towelroot to root my phone about a month ago. I read somewhere that the OTA update to Lolipop won't take unless it is absolutely stock. I am nopt the most knowledgeable about these things, so what exactly did using towelroot do that made it impossible to update to Lolipo OTA? How to I fix it so that Lolipop can be flashed to my phone? Thanks!
There's a 4.4.2 flashable zip I saw.
Can that not be flashed from the sdcard?
rockky said:
There's a 4.4.2 flashable zip I saw.
Can that not be flashed from the sdcard?
Click to expand...
Click to collapse
I did read about going back to 4.4.2, but was unable to cohesively follow it. I think that people were having trouble downgrading. Also, would that make my phone totally, absolutely stock? Kind of hijacking the thread, but it is still relevant to the OP's issue. I don't mind spending time on something if I know the outcome will get me to where I want to be. Thanks!
jeraldjunkmail said:
I did read about going back to 4.4.2, but was unable to cohesively follow it. I think that people were having trouble downgrading. Also, would that make my phone totally, absolutely stock? Kind of hijacking the thread, but it is still relevant to the OP's issue. I don't mind spending time on something if I know the outcome will get me to where I want to be. Thanks!
Click to expand...
Click to collapse
Try http://forum.xda-developers.com/showpost.php?p=57338156&postcount=97
Dear all,
I am asking for the solutions to solve this issue.
The device goes into bootloop after updating to 5.0.2.
It was known that the device has not enable OEM Unlock through development options. (and cannot get into setting page at this moment.)
Therefore, i cannot unlock the device by using
"fastboot oem unlock" in the fastboot mode of the device.
I have tried wipe data and perform factory reset in recovery mode.
but the device still get into bootloop.
May i ask for any possible solution for flashing back stock rom?
I'm in the same situation. I believe the only solution is to return the device for "repair".
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
GrillMouster said:
Go to recovery, wipe cache, making sure to give it a full hour to finish. Then reboot. You'll probably still be on 5.0.1.
Click to expand...
Click to collapse
I am having the same problem. I tried wiping the cache from recovery as well as doing a full reset, and still stuck. HTC is suggesting sending them the device.
FWIW, I am locked/unrooted and running stock.
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
penguinolog said:
Have the same problem. Recovery said, that update has been installed, errors reported on tzdata read.
Additional problem: bougth from Amazon and use at russia… Delivery cost is ~insane.
Click to expand...
Click to collapse
Were you able to fix it? I'm having the same problem, I just can't believe it's not possible to unlock the bootloader any other way.
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
cobyman7035 said:
if im stock 5.01 and i try to do an OTA update to 5.1.1, will that make a bootloop? or its only via 'bad flashing' in adb that causes loop?
i don't want to void my warranty untill im sure im going to keep my n9 LTE
thx
Click to expand...
Click to collapse
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
cam30era said:
It appears from feedback from other users, that sometimes the OTA can just "go wrong". So it's best to unlock your bootloader prior to installing the OTA. That way, if something does go wrong, you can easily recover from it.
Click to expand...
Click to collapse
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
That's good news. Glad to hear it.
cobyman7035 said:
i had NO troubles with OTA stock update... open n9 , it was 5.01, updated to 5.02, then did the 5.1.1 no troubles ...all stock
Click to expand...
Click to collapse
Simply switching "Enable OEM unlock" doesn't void your warranty, and it covers your butt in case something happens.
I'd like to start off by saying that I have NEVER rooted this device and have been 100% stock since day 1.
The only thing I did was enable developer options to unlock the bootloader so I could sideload OTA updates in the event they take too long to hit my device... No custom recoveries, no custom roms, no custom kernels, no exposed framework... NOTHING.. pure stock.
I started getting the 5.0.2 upgrade notification yesterday. Everytime I download and install, about 30% of the way through the installation I get the android icon showing ERROR. When I open the last recovery log it mentions not being able to open /cache/update.zip with a status 7 error. .. All I can do it reboot and return back to 5.0.1
I did some reading and it was recommended to wipe / format the CACHE partition. So I went into the stock recovery and tried this but to no avail.
I REALLY don't want to factory reset (or flash a factor image) and lose all the progress on the various games I have been playing.
Is there anything else I can try ??
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Thanks for the feedback... I can try this but IMO it's more of a workaround than a solution.
What I'm trying to get at is..... How in the heck would Google or HTC expect the average consumer to resolve such an issue.
Needing to have a PC, have special drivers installed, etc.., is understandable for those who want to step away from STOCK but what about the average consumer who just purchased the tablet to use as is, continues to receive a notification that an update is available, but fails every time it is applied ? Surely there is something that can be done so allow the update to take without having to factory reset or RMA the device...
y2whisper said:
you can try sideloading the update, grabbing the factory image and manually flashing the partitions (except userdata). you can try the factory image and just edit the flash-all.bat file to not wipe the device (sometimes the flash all file gave me an issue forcing me to do the partitions manually)
Click to expand...
Click to collapse
From the sounds of it there is an issue with the OTA file. But I agree you shouldn't be having to do this. I worry about the non xda'ers of the world when this stuff happens
Mine is doing the same crap. Also unmodified Nexus 9. This is nonsense.
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
kurtis.austin2 said:
Same issue here. Error every time I hit Restart & Install after downloading the update. Have to long press the power bottom to get it to boot back again. Tried a factory reset, didn't work. Still getting same error.
Click to expand...
Click to collapse
the.teejster said:
Thanks for sharing that you tried a factory reset. I am trying to avoid this for reasons mentioned in my 1st post.
I have tried numerous times now wiping cache and waiting for the upgrade to reappear but it continues to error out that the same place during the upgrade each time. Fortunately it's not bricking the device but IF this update is required as a stepping stone for subsequent updates then it will be extremely disappointing if Google doesn't address this issue.
I still cannot imagine google / htc not being able to resolve this WITHOUT having to make a user connect to a PC and manually flash imagess (or worse.. RMA the device). Hoping someone on XDA comes up with a magical sequence to allow the OTA to prcess properly.
In addition to wiping cache through recovery I have also ensured that I didn't have any apps / process or services disabled.
This is also being reported in google support forums:
https://productforums.google.com/fo...ter#!category-topic/nexus/nexus-9/MzHmJu4glkQ
I still haven't tried sideloading the OTA but at this point I don't think it would make a difference as the OTA does download properly and says it was verified.
Click to expand...
Click to collapse
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
adstro said:
I found this -> http://www.telekom-presse.at/apps/n...sht_update_auf_version_5-1_fehlt.id.33675.htm. There is a comment claiming to have fixed the issue by sideloading the OTA. I have yet to try it myself though.
Click to expand...
Click to collapse
the.teejster said:
On a side note,
Google has apparently finally released 5.1.1 for our device so it should be making it's way out soon.. HOPEFULLY we can go straight from 5.0.1 to 5.1.1 without having to worry about 5.0.2.
Click to expand...
Click to collapse
Have you seen any evidence of this unicorn? Just curious...
Reported on the official Google+ page :
https://plus.google.com/+Nexus/posts/2hB9k5r2Z7T
But I can't find any reports of anyone actually receiving it yet. IF 5.0.2 needs to act as a stepping stone then maybe they delayed to get the 5.0.2 issue resolved 1st.. It seems to be getting more and more attention out there now.
cam30era said:
Have you seen any evidence of this unicorn? Just curious...
Click to expand...
Click to collapse
FWIW.
I went into recovery, wiped cache and tried to side load the 5.0.2 OTA update manually and got the same error. The error displayed approx. 40% into the upload process from the PC.
I'm getting frustrated I can't get 5.0.2 to install. This is ridiculous
When I get the error, Power/Vol+ switches to the recovery log - there is a warning about (from memory) a partition having been mounted R/W, and a suggestion to re-flash the device first.
All I can remember changing from stock is permitting bootloader-unlock from dev options (never got round to unlocking, so far as I remember).
Not too worried, will hang on for the next major update (or 6.x if there is a preview, maybe) - however, it seems 5.0.2 is a fix to allow 5.1.1 to download (from comments on the G+ thread)
My error is an SHA mismatch on /dev/block/platform/sdhci-tegra.3/by-name/APP. I have
47e96f7e7daa360947b456eca9dc5a8e45573b30
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
How do I do this? Need adb from a computer?
kurtis.austin2 said:
How do I do this? Need adb from a computer?
Click to expand...
Click to collapse
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
cam30era said:
Yes you need ADB and Fastboot. Follow this guide and don't hesitate to ask questions > http://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
Click to expand...
Click to collapse
Thank you ? very kind of you
kurtis.austin2 said:
Thank you ? very kind of you
Click to expand...
Click to collapse
Welcome
Please read the OP.
cam30era said:
@the.teejster, @kurtis.austin2, @tshoulihane
Given that 5.0.2 is a significant improvement. Why don't you give up on trying to sideload the OTA, and fastboot flash the factory image? You won't get these errors.
Click to expand...
Click to collapse
Hello there,
I recently did a software update - not having done anything mod-ish things or anything to my phone, I didn't expect anything to happen.
My phone worked like usual after the update. After a restart of the phone, I end up in the Recovery Mode now and can't get out of it.
The error I'm getting is "Can't load Android System". The reason described at the bottom of the phone is "Reboot Recovery Cause is init:1" and "Reason is fs_mgr_mount_all:"
I'm able to get the phone into regular recovery mode and download mode - but nothing else.
Spoiler: EDIT with infos that are likely not relevant
I read some logs and it claims that the kernel on my phone is not made for production use, and that the user reads this message and is not debugging, then the vendor should be contacted. Not really applicable here but I wanted to mention it.
I was thinking about manually reinstalling the latest update, but I don't know if that's a good idea; how to do it properly without data loss (if even possible); and I don't know my CSC code. The download mode method & going via Samsung Support did not work. I only got the overall region, which is EUB - but I don't know the exact code.
How should I proceed from here on? Is manually installing the update a good idea, and does anyone have a good guide for me?
Or is there any reputable software that can fix this system error or can export some of my data for a reinstall.
Samsung Support was not a big help, as they only fix devices with data loss and they claimed that the symptoms I'm getting point to a voided warranty.
EDIT 2: Also, what can go wrong when installing an update with the wrong CSC?
EDIT 3: Also spoke to realbbb in this thread about this: https://forum.xda-developers.com/t/patched-odin-3-13-1.3762572/post-87516547
Best regards,
Gab
GabHM said:
EDIT 2: Also, what can go wrong when installing an update with the wrong CSC?
Click to expand...
Click to collapse
Usually it's just enough to flash any CSC from your country since they tend to have everything you need there.
And no, you won't have any negative impact if you flash the wrong CSC
There should be plenty of tutorials on YouTube on how to flash stock with Odin.
ShaDisNX255 said:
Usually it's just enough to flash any CSC from your country since they tend to have everything you need there.
And no, you won't have any negative impact if you flash the wrong CSC
There should be plenty of tutorials on YouTube on how to flash stock with Odin.
Click to expand...
Click to collapse
Do you know, by any chance, of a reputable source for a tutorial?
Bump, flashed my phone using Odin and the latest firmware and I still can't boot. I still need help here.
Also, the phone showed the android figure and "Erasing..." right after flashing even though I flashed with HOME_CSC. Is my data gone now or is this normal?
EDIT: I read something regarding slot changing or similar, how would I achieve this/is this something I could or should do in my case? Or am I already boned because I wiped my data
EDIT 2: Regular recovery mode gives me "Error updating for slotselect"
EDIT 3: The error that shows up is English now instead of German (what it was before), did I make it worse?
EDIT 4: Thinking about downgrading, is this a good idea?
EDIT 5: Tried downgrading to Security Patch levels 3 & 6 months ago and also tried going down to Android 11. Won't work. Still need help.
GabHM said:
EDIT 5: Tried downgrading to Security Patch levels 3 & 6 months ago and also tried going down to Android 11. Won't work. Still need help.
Click to expand...
Click to collapse
Bump
Also view my post above
GabHM said:
Bump
Also view my post above
Click to expand...
Click to collapse
bump I guess
There's a possibility that your motherboard may be damaged if flashing stock doesn't work.
Last resort is just flash full CSC to completely wipe data.
ShaDisNX255 said:
There's a possibility that your motherboard may be damaged if flashing stock doesn't work.
Last resort is just flash full CSC to completely wipe data.
Click to expand...
Click to collapse
I'm just so confused because my data was intact and everything was fine. After a reboot everything was broken. Is there any way I can get that phone repaired or anything similar without getting it wiped? I'm out of options with Samsung themselves because they're always wiping even with screen repairs (what they told me).
I wouldn't rule out board damage as I've been facing WiFi and Flashlight issues previously. I would pay for the repair even if it's still in warranty but I just want that data.
I know it's my fault for not backupping but I'd love to get that data back for paying.
Wish I could give you an answer but I've never really tried retrieving data. I always just format data and move it.
ShaDisNX255 said:
Wish I could give you an answer but I've never really tried retrieving data. I always just format data and move it.
Click to expand...
Click to collapse
Yeap. Redundantly and regularly backup critical data.
Rule#1- if a OS is fast, stable and fulfilling its mission... let it be!!!
Firmware upgrades and updates can and do break devices.
A data recovery specialist may be able to retrieve the data.
blackhawk said:
Yeap. Redundantly and regularly backup critical data.
Rule#1- if a OS is fast, stable and fulfilling its mission... let it be!!!
Firmware upgrades and updates can and do break devices.
A data recovery specialist may be able to retrieve the data.
Click to expand...
Click to collapse
Thank you for responding. Rule #1 is what I went by for like half a year but I ended up updating because of the explained WiFi & flashlight issues D:
Does it sound like to you that a data recovery specialist could realistically get back files or is this something you don't know about?
GabHM said:
Thank you for responding. Rule #1 is what I went by for like half a year but I ended up updating because of the explained WiFi & flashlight issues D:
Click to expand...
Click to collapse
Been running Pie for over 3 years. You find work arounds or fixes as you will have to do that with any firmware anyway.
GabHM said:
Does it sound like to you that a data recovery specialist could realistically get back files or is this something you don't know about?
Click to expand...
Click to collapse
No idea. That's your best shot though. It's worked for at least some. I personally would have written it off but I have most of my critical data backed up so it's more of an inconvenience rather than a disaster.
I'm sorry to read this and I often do.
Your problem has been going on for months.
Every manufacturer has its peculiarities and Samsung is peculiar.
With encrypted data your best help is to get the system running again.
Actually, your best help is to have nothing irreplaceable on a portable device.
Unfortunately, that's no consolation.
If you have a working recovery maybe at this point you should just do a check whether the /data partition has been wiped.
You won't be able to read it (probably?) but you can see if it's all cleared.
I'm with @blackhawk. If a truck ran over one my devices I wouldn't be that upset.
Unless said device was in my pocket at the time.
Renate said:
I'm sorry to read this and I often do.
Your problem has been going on for months.
Every manufacturer has its peculiarities and Samsung is peculiar.
With encrypted data your best help is to get the system running again.
Actually, your best help is to have nothing irreplaceable on a portable device.
Unfortunately, that's no consolation.
If you have a working recovery maybe at this point you should just do a check whether the /data partition has been wiped.
You won't be able to read it (probably?) but you can see if it's all cleared.
I'm with @blackhawk. If a truck ran over one my devices I wouldn't be that upset.
Unless said device was in my pocket at the time.
Click to expand...
Click to collapse
Thank you for your response, I expected to hear this but I didn't want to leave contacting y'all untried.
How would I check if the /data partition has been wiped? I've been careful to not wipe it with Odin and so far I only have wiped the cache and well, tried to change android versions.
If your recovery has ADB and it's rooted you can try my zerostat
Code:
C:\>adb push zerostat /somewhere/
C:\>adb shell
# chmod 755 /somewhere/zerostat
# /somewhere/zerostat
# Name Size Filled Zeroed Used Type
-- ----------- ------------ --------- --------- ------ -----
1 xbl 3670016 2461 1123 68.7% elf64
2 xblbak 3670016 2461 1123 68.7% elf64
3 tz 4194304 1294 2802 31.6% elf64
...
Use /cache or wherever you can.
It will attempt to read all the partitions and tell you what percentage zeroes it has.
You can specify partition number if some lower numbers makes it crash.
Code:
# zerostat 23
Renate said:
If your recovery has ADB and it's rooted you can try my zerostat
Code:
C:\>adb push zerostat /somewhere/
C:\>adb shell
# chmod 755 /somewhere/zerostat
# /somewhere/zerostat
# Name Size Filled Zeroed Used Type
-- ----------- ------------ --------- --------- ------ -----
1 xbl 3670016 2461 1123 68.7% elf64
2 xblbak 3670016 2461 1123 68.7% elf64
3 tz 4194304 1294 2802 31.6% elf64
...
Use /cache or wherever you can.
It will attempt to read all the partitions and tell you what percentage zeroes it has.
You can specify partition number if some lower numbers makes it crash.
Code:
# zerostat 23
Click to expand...
Click to collapse
Thank you for the recommendation, not rooted unfortunately.
GabHM said:
Thank you for the recommendation, not rooted unfortunately.
Click to expand...
Click to collapse
It's a good thing to have a rooted, permissive ADB in recovery before failure hits.
You could still install one now if you can find one.
GabHM said:
(...)
I'm able to get the phone into regular recovery mode and download mode - but nothing else.
(...)
Click to expand...
Click to collapse
There may be a solution, but you didn't even provide information about the name of the firmware you can read in recovery mode, or the link to the firmware you downloaded for odin, or the odin version you used.
ze7zez said:
There may be a solution, but you didn't even provide information about the name of the firmware you can read in recovery mode, or the link to the firmware you downloaded for odin, or the odin version you used.
Click to expand...
Click to collapse
Fair, I used Odin v3.14.1_3B_PatcheD and the following firmware:
Samfw: SM-A528B_DBT_A528BXXS1BVC2_fac
Samfw: SM-A528B_DBT_A528BXXS1CVD1_fac
Bifrost: SM-A528B_2_20220901174940_wfjk9aepw6_fac_A528BXXU1CVH6_A528BOXM1CVH6_A528BXXU1CVG8_A528BXXU1CVH6_DBT
I haven't turned on the phone since so I couldn't tell you the firmware I can see in recovery mode, but the current firmware should be the Bifrost one.
Renate said:
It's a good thing to have a rooted, permissive ADB in recovery before failure hits.
You could still install one now if you can find one.
Click to expand...
Click to collapse
That is still possible? I thought you needed to enable OEM unlocking in a functional OS before being able to root