Was having issues with an SD card not being recognized on my S7 work phone so I rooted and installed stock MM firmware to see if it was OS related....didn't work.
So I wanted to unroot and go back to a virgin state.
I thought I did this but now I can't get MobileIron ([email protected]) to install due to what I assume is some flag that I've tinkered with the phone.
Is there a foolproof way to take the device back to an out of the box condition like it's never been touched?
Just tried reverting to MM PI3 and doing OTA updates to get back to Nougat....everything is working correctly again.
Except for the unsupported sd card message........command '7 volume partition disk: 179,0 public' failed with '400 7 Command failed'
Related
So I tried to check for a system update and received a message saying that I had made unauthorized changes to the software and would need to try an alternative method to update requiring attaching to a pc. I have never even tried to root this tablet so don't understand why I get this message. Any suggestions?
Remove the SD card, reboot and retry the update. It won't work with some sizes of SD card in the slot.
Try with odin to update your device , search firmware for your country in sammobile
My UK HTC One M9 overnight came up stating my device was encrypted and to enter a password - I entered my usual password and it said although it was correct, my data is corrupted and to do a factory reset. It did not work. I really don't know what happened but my situation is thus:-
- Device is "unlocked" but on S-ON state
- I can access TWRP however I keep getting errors that it could not load partitions, namely data, cache, system, and so on.
- I cannot flash anything over fastboot (because of S-ON), and any ROMs I put onto an SD card and try to install via TWRP fail
- There is no OS on the device
I've tried running the HTC RUU for my device however it spits out that my battery percentage is under 30% despite being fully charged - when I manually ran the fastboot command to check my battery level, it responds blank - I assume this is why the RUU refuses to do anything.
I'm not really sure what left to try, and my device is effectively a rather expensive paperweight right now. Any suggestions would be much appreciated!
Send it to service... I have same issue and i cant solve this
This won't be covered by the warranty though, as the device has previously had a new ROM flashed to fix a problem HTC couldn't.
It is a emmc issue. I cant find any solution to fix this issue. I talked to llabtoofer and he said he couldnt fix this too.
iwmtom said:
My UK HTC One M9 overnight came up stating my device was encrypted and to enter a password - I entered my usual password and it said although it was correct, my data is corrupted and to do a factory reset. It did not work. I really don't know what happened but my situation is thus:-
- Device is "unlocked" but on S-ON state
- I can access TWRP however I keep getting errors that it could not load partitions, namely data, cache, system, and so on.
- I cannot flash anything over fastboot (because of S-ON), and any ROMs I put onto an SD card and try to install via TWRP fail
- There is no OS on the device
I've tried running the HTC RUU for my device however it spits out that my battery percentage is under 30% despite being fully charged - when I manually ran the fastboot command to check my battery level, it responds blank - I assume this is why the RUU refuses to do anything.
I'm not really sure what left to try, and my device is effectively a rather expensive paperweight right now. Any suggestions would be much appreciated!
Click to expand...
Click to collapse
Did u tried to format partitions inside TWRP and only then install a ROM from SD card?
Good luck!
try flashing signe firmware over fastboot/download mode. if that doesn help, as it repartitions the phone, it is bricked and only htc can fix it, or you try to get new mainboard
Hi yesterday I worked on my girlfriends phone. She said it just rebooted and showed this error. But I haven't found a solution here in the board.
It says. It's encrypted. When she puts in a code it says that it was correct but encryption unsuccessful. Data corrupt.After that only reboot in the same screen where to put code.
S on
Locked
Os 6.13.206 ( if I remember correctly)
Germany/ Europe
Stock no modifications
Factory reset not working
Also not by recovery
RUU not working ( restarts in same screen)
OTA not working
FUU not working
Don't see a device on and...
Biggest Problem. The phone is not important but the data. Most options would delete all files There are important family pictures and interviews on it.
t. I tried to connect via mtp but no luck. Is there a way to dd the data to salvage files later or something.
Any suggestions. Thx!
Michael
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Did your phone just reboot in the middle of doing something innocuous then start bootlooping? Were/Are you on total stock with bootloader locked? If both yes, it is probably hardware issue you are encountering.
Regarding sideloading, did you place your Android recovery in sideload mode?
Did you verify adb can "see" your device using "adb devices"?
SomewhatIrked said:
Hi all,
My Nexus 5x (16gb - all stock.) went and soft bricked today. Not sure why - just seemed to start wanting to constantly restart - never making it past the white google text part of the boot process. Not sure if it's an update or hardware. No trauma or dropping of the phone - which makes me think s/w rather than h/w.
I have attempted to install a rescue OTA update (instructions I followed are from technobill - don't have enough posts to add a link). However, when running "adb sideload <file>" I get a "failed to read command" error. Have tired multiple cables/ports however to no avail.
(Recovery screen shows the following build details: 7.0/NBD90W/3239497)
Any ideas?
Thanks.
Somewhat Irked
Click to expand...
Click to collapse
Well luckily I made this post today.
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
SomewhatIrked said:
The more this goes on, the more I believe it to be hardware ...
@sfhub - reasonably innocuous. Had just opened one or 2 apps that morning. Not sure what had updated overnight app/os wise. Not anything interesting as far as I can tell. Once I managed to get it into recovery "adb devices" was returning the phone.
@bardhi92 - I saw that once I got in. However, I couldn't get it to see my phone.
Updated things I have tried and why I've all but thrown in the towel:
After the OTA rescue sideload failed I started trying a few different things. It stopped taking me into recovery mode more frequently, at least it seemed that way - it would just keep bootlooping. My main issue is that I has a locked bootloader, which stopped me whacking TWRP on and loading on a custom rom - just to see if that worked.
I thought it might let me sideload on a factory default img file. Turns out nope.
However I used NRT to "Flash Stock + Unroot" (with "Soft Brick/Bootloop" checked) which for some reason, then allowed me to get back into recovery mode. I had also removed the sim card/tray at this point. May have been either or neither of those that allowed me to get into recovery mode. Can't say for certain.
I cleared /cache and /data and then attempted the OTA rescue update again. This time it failed at 45% (according to my cmd prmpt) with the error: "* failed to read command: No error". I'm not sure text was on the phone at the time. But it did manage to boot into Android. I quickly stepped through the various intro steps (putting in the sim, adding my mail google account details).
I went to get a beer. Only to find it boot looping again.
Not to be deterred, I vowed to try again. Same steps as before (remove sim, nrt voodoo). This time however the OTA rescue worked and fully completed. I went through the intro steps again. This time I quickly turned on dev options, enabled usb debugging and sorted out the OEM bootloader. I thought this would be smart, just in case it hapened again. Once I chose to unlock ("fastboot reboot", selected yes), it decided to start boot looping again.
The main annoyance is: I don't think I have any proof of purchase, even though it's in warranty. That, and I now live in Dubai - so shipping back to the UK where I brought it is going to be killer. But I think it's the path of least resistance at the moment.
Click to expand...
Click to collapse
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
bardhi92 said:
So, you flashed the .TOT file, sideloaded the given OTA within the stock recovery bootloader that comes with the .TOT file, and cleared cache/factory reset?
Please condense it. If you managed to start up the phone, that's a huge success for people who have not been able to yet.
Click to expand...
Click to collapse
In short:
OTA rescue failed during adb sideload,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue claims to have failed at 47% during adb sideload- still booted into android. However briefly. Went back to bootloop,
Tried bullhead-nbd90w-factory-d2f11c5f.zip & removed sim tray - seemed to allow access to recovery mode,
OTA rescue completed via adb sideload,
Turned on dev options (usb debug, oem unlock),
Booted to fastboot - unlocked bootloader. Now back to bootlooping
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
SomewhatIrked said:
@bardhi92 - I could not get the LG utility to detect my phone. Will attempt again tomorrow.
Click to expand...
Click to collapse
IMO you shouldn't flash the TOT file. If you end up bootlooping again, your phone will be stuck in bootloader locked mode with no ability to unlock it.
If you were able to get your phone to boot into android once, there is really nothing the TOT file will do for you that you can't do from TWRP or bootloader, whereas once it locks your bootloader, there are problems you can no longer fix like EFS corruption (which likely isn't your problem).
In the end, you probably do have eMMC that is slowly starting to fail. There is usually error correction on the eMMC that can lock out bad blocks but if it gets to serious, it'll fail. This is why reflashing stuff over and over sometimes works.
Longer story: been using a newer phone for almost two years, but that broke today, so I am now in an emergency "I don't care about tweaks and turns" state, as all I need is my old htc10 back in usage. I dug it up from my storage, got prompted for a new version of lineage OS, which I accepted (old habits die hard ), plugged in my SIM - no go (no service recognized - I am on TMo - always been, but phone was acquired unlocked, and used as such). I tweaked the network parameters (APs, service config, others), to no avail. What is the fastest & safest method to get a ROM (stock, lineage, other + steps) on this guy, to get me to use TMo services ASAP?
Info on phone at this time:
lineage os 14.1, android 7.1.2
in download mode: htc_pmewl pvt s-on
lk-1.0.0
os-2.51.617.21
[email protected]
twrp 3.1.1-0
netfortius said:
Longer story: been using a newer phone for almost two years, but that broke today, so I am now in an emergency "I don't care about tweaks and turns" state, as all I need is my old htc10 back in usage. I dug it up from my storage, got prompted for a new version of lineage OS, which I accepted (old habits die hard ), plugged in my SIM - no go (no service recognized - I am on TMo - always been, but phone was acquired unlocked, and used as such). I tweaked the network parameters (APs, service config, others), to no avail. What is the fastest & safest method to get a ROM (stock, lineage, other + steps) on this guy, to get me to use TMo services ASAP?
Info on phone at this time:
lineage os 14.1, android 7.1.2
in download mode: htc_pmewl pvt s-on
lk-1.0.0
os-2.51.617.21
[email protected]
twrp 3.1.1-0
Click to expand...
Click to collapse
I would say run the 2.51.617 ruu.
Download this bad boy
https://androidfilehost.com/?fid=962021903579491246
Rename it to 2PS6IMG.zip only and copy it to your SD card, then boot to download mode and it will automatically prompt you to flash it. The device will be pure stock nougat after that.
In download mode I get the menu:
<... my phone info ...>
System info
Show barcode
Reboot to bootloader
Reboot to download mode (which is what I keep doing)
Reboot
Power down
...
SD MOUNTED
OTG NOT MOUNTED
File not found
And nothing to do / act on
netfortius said:
In download mode I get the menu:
<... my phone info ...>
System info
Show barcode
Reboot to bootloader
Reboot to download mode (which is what I keep doing)
Reboot
Power down
...
SD MOUNTED
OTG NOT MOUNTED
File not found
And nothing to do / act on
Click to expand...
Click to collapse
Then you renamed the file wrong. You know that only the extension is .zip so don't rename it 2PS6IMG.zip.zip ..... check again, i bet that this is the problem.
Name was ok, but got what it appears to have been a corrupted sd-card (!?!). Plugged it in my MacBook, checked it was exfat, copied the file with the right name, verified it was there, plugged into the phone, no go. Done it twice, same results. Finally decided to copy the previous entire content of sd-card to another place, reformatted it again as exfat, put the zip back on it and **it worked**! Thank you for the original solution and confidence it should work