[Q] Stuck on HTC boot screen after sudden restart

[Q] Stuck on HTC boot screen after sudden restart - HTC Desire S

Hello Everyone,
My Desire S was running Fallout 4.0 ROM. I had a couple sudden restarts in the last week and a half, but they seem to have been graphic related and because I didn't have the time to re-install, I just lived with it (not a big deal) for the time being.
However, yesterday when I picked up my phone I have noticed that it is stuck on the HTC boot screen. I thought that this is just another one of those restarts, but when the boot operation didn't progress I figured that something is wrong. I booted into recovery (CWM 5.0.2.0) and then got the infamous errors of can't mount Cache/System/Data.
This when my troubles have began because I cannot seem to be able to solve this issue.
1) From within the "mounts and storage" menu I cannot mount nor format the partitions (I get an error such as "Error mounting /cache!" and "Error formatting /cache! The latter takes also a long while in which the format is being attempted but in the end the error appears)
2) When I choose the wipe option (restore factory defaults) it takes a very long time (30-40 minutes) to wipe the data and cache partitions. Sometimes it gives an error message and some time it says complete, but with not effect whatsoever from what I can tell.
3) Attempt to restore my Nandroid backup fails (both of the original stick ROM that came with the phone and the more recent Fallout backup). An error message says that it cannot be completed.
4) I tried to flash several ROMs. The first two failed (including the original Fallout ROM that I have used). I think that I have managed to flash CM7 and RunnyDroid. I say think, because the process seem to be completed without an error, but nothing has changed otherwise, the system doesn't boot.
5) I checked my eMMC by booting into Fastboot and running the command
Code:
adb shell
dmesg | grep mmc0
from adb.
The output is
Code:
dmesg | grep mmc0
<3>[6.953796] mmc0: No card detect facilities available
<6>[6.954345] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,
<6>[6.954589] mmc0: Platform slot type: MMC
<6>[6.954711] mmc0: 4 bit data mode disabled
<6>[6.954925] mmc0: 8 bit data mode enabled
<6>[6.955078] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000
<6>[6.955291] mmc0: Slot eject status = 0
<6>[6.955413] mmc0: Power save feature enable = 1
<6>[6.955566] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c
<6>[6.955780] mmc0: DM cmd busaddr 0x0c36e000, cmdptr busaddr 0x0c3
<6>[7.109436] mmc0: new high speed MMC card at address 0001
<6>[7.111297] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
~ #
To my best understanding it means that the eMMC is not necessarily fried.
4) Because I cannot boot into the system I tried to re-flash recovery (actually 4EXT) via fastboot and adb, but it fails with the error
FAILED (remote: not allowed)
Click to expand...
Click to collapse
. The same happened when I tried to flash the boot.img from a ROM.
5. I read about installing a RUU. well, I think that I have found a version that fits my phone but all the download links are broken and a web search didn't find the version that I (think that I) need elsewhere. Also, those are EXE file, that to my best of understanding requires the Android system to be booted up in order the installation process to work, which I cannot accomplish at this point.
General details of my phone as appear in the HBOOT screen:
SAGA PVT SHIP S-OFF RL
HBOOT-0.98.0000
RADIO-38.03.02.15_M
eMMC-boot
Mar 10 2011.14:58:38
Click to expand...
Click to collapse
Genreal details as received from running the commend
Code:
fastboot getvar all
in adb:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 0.98.0000
(bootloader) version-baseband: 38.03.02.15_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.401.1
(bootloader) serialno: HTXXXXXXXX
(bootloader) imei: XXXXXXXXXX
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG88*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.033s
Additional notes:
1) I took caution not to pull the battery, I know that it can have very negative effects. When I had to, before pulling the battery I have used the Volume up and down + Power combination to restart the phone and pulled the battery in that 2-3 seconds window before it restarts. I also didn't reconnect the battery immediately but waited about a minute.
3) I formatted my memory card (8GB) to FAT32, just in case the file system is corrupt (I have backed up everything first). This doesn't seem to have an effect.
4) I didn't root or S-OFF the phone myself. At the time of buying it I wasn't even aware of all of this and didn't plan to replace ROMs, etc., so I don't have much information about how the S-OFF and Root were achieved, this is how the phone was provided to me.
I would appreciate any input and advice. Is it a faulty eMMC? Is there anything else that I can do (I am far from being an expert in this field)?
Thank you very much.

Please try to be simple. I don't think that all these informations are necessary. This is a question Doesn't Have to be so long. The responders will ask you for additional info if needed.

Thank you for your reply, but I don't see the point in posting a vague and general question that will then require people to ask for information and suggest measures that one might already has taken.
From my experience in other forums (in which I'm more on the "helping" side) it is very frustrating to read vague and general questions and repeatedly ask for the same basic information over and over (and over) again just to get started. It is a waste of time and energy for all parties involved. In my opinion posting the relevant technical information, issue summary and steps already taken with their results is the way to go.
Update: I contacted the lab of the store from which I purchased the device. They tested it and told me that the board is (most probably) faulty, something to do with the electrical components. Because the device is still under warranty they will send it to be replaced.
Hopefully, the fact that I have flashed a custom ROM in the past won't be an obstacle in light of the nature of the fault.
Thank you.

You're right about the information. It does help to just provide it all and the information given is useful. Hope it all works out mate
Sent from my Desire S using Tapatalk 2

Related

[Q]stuck in bootloader,no recovery

Hi to everybody,my friend has a problem with his desire S.
his phone is turned off itself vibrating.now he can boot only in bootloader mode,and the recovery is gone.
here some spec.
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
radio-3805.06.02.03_M
eMMC-boot
Mar 10 2011,14:58:38
( bootloader ) version: 0.5
(bootloader) version-bootloader: 6.98.1002
(bootloader) [email protected] baseband : 3805.06.02.03_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.47.401.4
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: HTC__405
(bootloader) battery-status: good
(bootloader) battery-voltage: 3653mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 361a7ba6
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
He also tried to flash the eng hboot to run a RUU,but seems he can't flash the hboot (hangs on "writing hboot").
thanks for any help.

Did your friend happen to pull his battery anytime before all this started?
Recovery doesn't just "disappear" - he must have done something prior to that...
Anyway, the first thing is to rule out (or in) a fried eMMC
So do this:
Set up adb/fastboot and connect your phone (link in my sig)
Then connect your device to the PC, enter recovery, open cmd (command prompt) on the PC and type:
adb shell
dmesg | grep mmc0
For further details, consult this excellent guide by amidabuddha:
http://forum.xda-developers.com/showthread.php?t=1284196

thanks for the quick reply.when I have the output of the dmesg | grep mmc0 ,I'll post here.I haven't the phone with me,so I have to wait for my friend.

the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?

NeTvAmPiRe70 said:
the phone,does not appear to be recognized by adb
C:\android-sdk-windows\platform-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but through fastboot devices the output is mb139tj10369 fastboot.
any ideas?
Click to expand...
Click to collapse
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery

enigmaamit said:
Well, since you can get to fastboot, try this anyway.
Also, see if flashing recovery again gets you up and running.
Boot into fastboot on the phone, and using the cmd terminal, push a new recovery to the phone. I'm attaching 4EXT recovery. Just download it, extract recovery.img from the zip file, put it into your adb/fastboot folder and issue the following command:
fastboot flash recovery recovery.img
Then try to boot into recovery and tell me what you see...
DOWNLOAD : 4EXT Recovery
Click to expand...
Click to collapse
...no luck hangs on "writing recovery".

NeTvAmPiRe70 said:
...no luck hangs on "writing recovery".
Click to expand...
Click to collapse
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE

enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
Click to expand...
Click to collapse
this is not the same thing but with a different recovery?
however,I'll give it a try.
NeTvAmPiRe70 said:
tried this http://forum.xda-developers.com/showthread.php?t=1488672 but no luck.when starts to flash the recovery,the vertical progress bar stops and the phone begins to vibrate.
Click to expand...
Click to collapse

NeTvAmPiRe70 said:
this is not the same thing but with a different recovery?
however,I'll give it a try.
Click to expand...
Click to collapse
I don't know what was there in that file... so i sent you mine.
But if fastboot wasn't working, the possibility of an eMMC brick is looming larger...
Just try the commands i asked you to type in my first post... I mean boot into bootloader, then see if these commands cough up a report... if it doesn't work, boot into fastboot and try again. You must have some kind of recovery man...
Also, you didn't say what happens when you select Recovery option from the bootloader... what happens?

enigmaamit said:
Okay, i'm attaching 4EXT recovery in PG88IMG.zip format. Just place this on your sd card root, and boot into bootloader... it will try to flash this recovery on its own the moment it detects it. Let's see what happens...
DOWNLOAD HERE
Click to expand...
Click to collapse
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.

NeTvAmPiRe70 said:
...same as before,when starts to flash the recovery,the vertical progress bar stops and the phone hangs on "do not power off the device".
tried the dmesg | grep mmc0 both from bootloader and from fastboot but the phone,does not appear to be recognized by adb.
when he select recovery from the bootloader,appears the white screen with the htc logo,then the phone turns off itself vibrating.
Click to expand...
Click to collapse
Then i think your friend might have fried his eMMC.
Last resort is to call in the expert : Send a PM to amidabuddha, the guy whose guide i linked in my first post. I haven't found anyone more knowledgeable in these matters. If anyone can help you, its him.
I hope you can salvage the device...but its not looking very good....

thanks for your help,I'lll contact the expert

...and the expert has decreed:fried eMMC

NeTvAmPiRe70 said:
...and the expert has decreed:fried eMMC
Click to expand...
Click to collapse
That's what i thought too... just didn't want to mouth off such a grave judgement without being doubly sure.
Very sorry - unable to help any further. Hope your friend takes the news well, and wish him/her better luck for the next device!

Desire-S Bricked ?

I'm totally new here so I don't really understand all the stuff , now my problem was I tried to install an update on my htc desire s and it got an error midway on the installation since then when I go to recovery it says
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And I can't install a custom ROM (error Status 1) and it hangs on the htc white splash screen
I looked up the problem and found many explanations but none did it for me .
Tried wipe data/factory reset , wipe cache , wipe dalvik cache but still the same
In the end I ended up flashing PB31IMG.zip to try and return to stock but now I cant even go to bootloader (volume down + power) nor recovery . In adb it still recognizes my device when I type adb devices .
So can you please help me and tell me what to do now ?
My eMMc is not fried I typed :
Code:
adb shell
dmesg | grep mmc0
And its okay
Any info you need pls tell me so I can write it for you ,
I currently know this :
Code:
Revolutionary
Saga PVT SHIP S-OFF RL
HBOOT 6.98.1002
RADIO-3805.06.02.03_M
eMMc-BOOT
MAR 10 2011 , 14:58:38
And that was before i flashed it with PB31IMG.zip since then I cant even go to bootloader ... It's 4 am here and I am going to sleep right now , will reply when I wake up ... please help

You cannot install RUU over Revolutionary hboot. You must flash the ENG hboot over it first. Please look in rhe index thread in the Dev section for ENG hboot.
Try to remove buttery for a while and then to boot into bootloader by pressing vol "-" and power buttons.
Also the name of the RUU zip should be different, PG88IMG.zip.
Sent from my HTC Desire S

Imp0stoR said:
I'm totally new here so I don't really understand all the stuff , now my problem was I tried to install an update on my htc desire s and it got an error midway on the installation since then when I go to recovery it says
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
And I can't install a custom ROM (error Status 1) and it hangs on the htc white splash screen
I looked up the problem and found many explanations but none did it for me .
Tried wipe data/factory reset , wipe cache , wipe dalvik cache but still the same
In the end I ended up flashing PB31IMG.zip to try and return to stock but now I cant even go to bootloader (volume down + power) nor recovery . In adb it still recognizes my device when I type adb devices .
So can you please help me and tell me what to do now ?
My eMMc is not fried I typed :
Code:
adb shell
dmesg | grep mmc0
And its okay
Any info you need pls tell me so I can write it for you ,
I currently know this :
Code:
Revolutionary
Saga PVT SHIP S-OFF RL
HBOOT 6.98.1002
RADIO-3805.06.02.03_M
eMMc-BOOT
MAR 10 2011 , 14:58:38
And that was before i flashed it with PB31IMG.zip since then I cant even go to bootloader ... It's 4 am here and I am going to sleep right now , will reply when I wake up ... please help
Click to expand...
Click to collapse
You need to install a custom recovery to do anything regarding installing a ROM. I suggest you flash 4ext recovery using fastboot and then format your device partitions before attempting to install a new ROM.
Beamed from the Dark Side using xda premium.

Okay I tried flashing HBOOT ENG 0.98.2000
This one :
HTML:
http://forum.xda-developers.com/showthread.php?t=1113820
But when I try and flash with bootloader it says
Cannot rollback HBOOT version
About the recovery I have clockworkmod , how do I replace it with 4EXT ?

Imp0stoR said:
Okay I tried flashing HBOOT ENG 0.98.2000
This one :
HTML:
http://forum.xda-developers.com/showthread.php?t=1113820
But when I try and flash with bootloader it says
Cannot rollback HBOOT version
About the recovery I have clockworkmod , how do I replace it with 4EXT ?
Click to expand...
Click to collapse
Why are you trying to change your hboot? You have the Revolutionary hboot, which is fine. You need to flash a custom recovery using fastboot. Download the attached file, and after setting up fastboot on your computer (Link to guide is in my signature below), extract the recovery.img file from the .zip i have attached, and place it in your adb/fastboot folder on the computer. Then boot into fastboot on your phone and issue the following command :
fastboot flash recovery recovery.img
Once done, reboot into recovery to confirm that you have 4EXT Recovery installed, then select the Wipe data/Format option, and select Format all partitions (except sd card). Now choose install from sd card, and flash whichever ROM you want to flash (I recommend Reaper ROM for testing purposes... it is light and fast)

Okay , working adb with fastboot
Downloaded recovery.img
and when i type
Code:
fastboot flash recovery recovery.img
sending 'recovery' <5624 KB>... OKAY [ 0.952s ]
writing 'recovery' ...
And it just hangs there ... for like 20 minutes for now
Should it be so long ? What's wrong , and what are my alternatives ?
I'm in FASTBOOT USB

Imp0stoR said:
Okay , working adb with fastboot
Downloaded recovery.img
and when i type
Code:
fastboot flash recovery recovery.img
sending 'recovery' <5624 KB>... OKAY [ 0.952s ]
writing 'recovery' ...
And it just hangs there ... for like 10 minutes for now
Should it be so long ? What's wrong , and what are my alternatives ?
I'm in FASTBOOT USB
Click to expand...
Click to collapse
The other alternative for you is to use android flasher. http://forum.xda-developers.com/showthread.php?t=794638
Use it to flash the recovery when the phone is booted into fastboot mode.

Meanwhile, i suggest you post the result of the
adb shell
dmesg | grep mmc0
just wanted to look through the output.

Android flasher hangs too... but it doesn't freeze the fastboot like cmd did
also when I'm in fastboot or bootloader adb says error : device not found , only when I power it off and then connect with usb it says
Code:
adb devices
list of devices attached
HT13GTJ18877 recovery
as for
adb shell
dmesg | grep mmc0
<3>[ 7.008239] mmc0: No card detect facilities available
<6>[ 7.008758] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.009002] mmc0: Platform slot type: MMC
<6>[ 7.009124] mmc0: 4 bit data mode disabled
<6>[ 7.009246] mmc0: 8 bit data mode enabled
<6>[ 7.009490] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.009613] mmc0: Slot eject status = 0
<6>[ 7.009857] mmc0: Power save feature enable = 1
<6>[ 7.009979] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c042000
<6>[ 7.010223] mmc0: DM cmd busaddr 0x0c042000, cmdptr busaddr 0x0c042300
<6>[ 7.163421] mmc0: new high speed MMC card at address 0001
<6>[ 7.165039] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB

Imp0stoR said:
Android flasher hangs too... but it doesn't freeze the fastboot like cmd did
also when I'm in fastboot or bootloader adb says error : device not found , only when I power it off and then connect with usb it says
Code:
adb devices
list of devices attached
HT13GTJ18877 recovery
as for
adb shell
dmesg | grep mmc0
<3>[ 7.008239] mmc0: No card detect facilities available
<6>[ 7.008758] mmc0: Qualcomm MSM SDCC at 0x00000000a0500000 irq 98,0 dma 7
<6>[ 7.009002] mmc0: Platform slot type: MMC
<6>[ 7.009124] mmc0: 4 bit data mode disabled
<6>[ 7.009246] mmc0: 8 bit data mode enabled
<6>[ 7.009490] mmc0: MMC clock 144000 -> 50000000 Hz, PCLK 96000000 Hz
<6>[ 7.009613] mmc0: Slot eject status = 0
<6>[ 7.009857] mmc0: Power save feature enable = 1
<6>[ 7.009979] mmc0: DM non-cached buffer at ffa0f000, dma_addr 0x0c042000
<6>[ 7.010223] mmc0: DM cmd busaddr 0x0c042000, cmdptr busaddr 0x0c042300
<6>[ 7.163421] mmc0: new high speed MMC card at address 0001
<6>[ 7.165039] mmcblk0: mmc0:0001 M4G2DE 2.10 GiB
Click to expand...
Click to collapse
Hmmm... wierd. Your eMMC looks fine, but apparently you don't have an effectively working fastboot.
Maybe you now need to flash an RUU of your region...? Before doing that, please follow the steps from the post linked below and see where that takes you.
http://forum.xda-developers.com/showthread.php?t=1284196
Also, paste a result of the following command from fastboot :
fastboot getvar all
Blot out your imei and serial no before posting, if you want to.

Thanks for sticking with me
I have to go to work but when I return I will try the steps in the link you given me
and I'll give you feedback then
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 6.98.1002
INFOversion-baseband: 3805.06.02.03_M
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 10.47.401.4
INFOserialno: HT13GT******
INFOimei: 355067040******
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG88*****
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.008s

Imp0stoR said:
Thanks for sticking with me
I have to go to work but when I return I will try the steps in the link you given me
and I'll give you feedback then
Code:
fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 6.98.1002
INFOversion-baseband: 3805.06.02.03_M
INFOversion-cpld: None
INFOversion-microp: None
[B][COLOR="red"]INFOversion-main: 10.47.401.4[/COLOR][/B]
INFOserialno: HT13GT******
INFOimei: 355067040******
INFOproduct: saga
INFOplatform: HBOOT-7230
INFOmodelid: PG88*****
[B][COLOR="Red"]INFOcidnum: 11111111[/COLOR][/B]
INFObattery-status: good
INFObattery-voltage: 4182mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: 361a7ba6
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.008s
Click to expand...
Click to collapse
You have a SuperCID!
Wow...! That makes things easier for running an RUU... Just find an RUU that you want (preferably from your country) and connect your phone to pc in fastboot more, then run the RUU. You'll be back to stock S-on, but then you can S-off using Revolutionary, or just use HTCDev Unlock.
P.S. You may need to (I recommend it) change your misc version to a lower one before running the RUU. Instructions can be found here :
http://forum.xda-developers.com/showthread.php?t=1399331

Something's irritating me with your problem...
You say you have a device stuck on fastboot, and your eMMC chip doesn't look fried, but you said you try to flash PB31IMG.zip to return to stock.
Could you share this PB31IMG.zip file ?
I think that is the problem source, because the standard Desire S flash zip is PG88IMG.zip and not PB31IMG.zip. I don't know where you got this zip file but please share it, you must have flashed images that isn't for the Desire S.
EDIT : PB31IMG belongs to Incredible. You flashed a flash zip for Incredible. Please either share it or list the content of that zip.
For your problem, maybe a wrongly flashed file causes this, but you are lucky enough to be in fast boot mode. Try run a RUU, preferably of your country as enigmaamit said.

So I just have to type
Code:
adb shell /data/local/tmp/misc_version -s 1.27.405.6
and then run RUU from fastboot ?
I found a RUU but its .exe and requires my phone to be on
Code:
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed
I am confused about these RUU and which one should I take and how to apply them , there are several from Europe , but I choose the one with the newest radio ...

This is the PB31IMG.zip , but the error I got was way before that , I dont think this plays a role
http://postimage.org/image/iv6uyuhsh/

Imp0stoR said:
So I just have to type
Code:
adb shell /data/local/tmp/misc_version -s 1.27.405.6
and then run RUU from fastboot ?
I found a RUU but its .exe and requires my phone to be on
Code:
RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed
I am confused about these RUU and which one should I take and how to apply them , there are several from Europe , but I choose the one with the newest radio ...
Click to expand...
Click to collapse
Just follow the instructions on that thread...

When I type
Code:
adb shell chmod 777 /data/local/tmp/zergRush
It says
Code:
chmod: /data/local/tmp/zergrush: Not a directory
Does the same for misc_version ... Help?
I'm doing it while phone is off , because when its in bootloader adb devices shows no devices and when its off it shows a device in recovery

Still stuck at
Code:
chmod: /data/local/tmp/zergrush: Not a directory
Don't know how to bypass that

I tried installing RUU to revert to stock recovery but it hangs at rebooting to bootloader and the phone freezes , is this whole thing anyhow solvable ?

Imp0stoR said:
I tried installing RUU to revert to stock recovery but it hangs at rebooting to bootloader and the phone freezes , is this whole thing anyhow solvable ?
Click to expand...
Click to collapse
Hi... sorry i could't attend to you earlier... What error do you get when using the RUU?

One Mini s-ON, trying to get s-OFF

Hey guys, I have a problem with this phone HTC one mini, in fact I'm trying to unlock it with Sieempi method, but for this I need the device to be s-off. I unlocked the bootloader, the device be rooted, and when I try to use Rumrunner i got this error message.
Code:
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (19/120)
Waiting
Test 2: Booting device
Waiting for ADB (55/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
Waiting for ADB (55/120)
must ferment longer...
chilling..................
it's a little stinky here, hmm....
bottles are packed, here we go, shhhhhh....
hmm, cap is on tighter than I expected........
hell, that damn cap is on REALLY tight.......
unfortunately this isn't going to work out with your configuration. you have 2 options:
1.) flash an unsecure kernel that's compatible with your ROM and retry rumrunner (preferred and most reliable method).
2.) flash a different rom.
NOTE: No amount of messing around with su binaries and apk's is going to fix this issue for you!!!.
Better luck next time!!!!bye
Press ENTER to exit
Then i find this theard
http://forum.xda-developers.com/showthread.php?t=2573479
And download this two files, but then I stuck.
I'm not sure how to do the rest, but I tried it this way and I have failed.
I unpacked JmzM4_Kernel-09-4-13.zip file, and copied the boot.img file in the SDK folder from where I started CMD. In the CMD I typed "fastboot flash boot boot.img" and I got the message OK.
Then I went into recovery and found JmzM4_Kernel-09-4-13.zip file on the internal memory of a cell phone and I tried to install it (so I read) a zip file, and then I got the error MD5 file check, something like that.
I then reboot to recovery again and tried to install "JmzM4StockRootedOdex-WWE 1.22.401.1" also a zip file, and again the same error MD5 file check.
Then the phone in fastboot mode remained and could not boot the system. So I had to do a restore of backup I in which they made before I got into flash kernel, and roma.
Here is also my fastboot getvar all the info.
Code:
C:\ADB>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 2.22.0000
INFOversion-baseband: 1.28.40e.00.24
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.14.401.1
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid:
INFOproduct: m4_ul
INFOplatform: HBOOT-8930
INFOmodelid: PO5820000
INFOcidnum: HTC__032
INFObattery-status: good
INFObattery-voltage: 4316mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-0e1af350
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.124s
C:\ADB>
Can someone tell me what is the solution for my problem, I just want my device S-off to try Sieempi method of unlocking, to see if it works. Thx!

Nothing? I try a couple thing more. I think its problem in the file I downloaded, and download a MD5 checker, and says thats ok. Then I save a md5 file from Md5 checker @ the same folder like zip file, and run again from recovery, and now got another error, you can see image.
IMG]http://tapatalk.imageshack.com/v2/14/10/08/624d91145625043f190be1d67997e6a2.jpg[/IMG]
Revone method doesnt work i got error -2. And boot intro the bootloader and stil s-on.

Please lock theard, phone was smashed. I lost nerves!

Hi Errornt
pardon if i only post today!
had your same situation and now i've solved! the solution? just flash a new kernel! i've used xXminiWHOOPERxX Kernel and now.... i'm s-off
so, unlock bootloader, install custom recovery and root, flash an insecure kernel with fastboot method and run rumrunner
that's all
i'm sorry for your smashed phone
br
ss

The Story of my lost and recovery IMEI = 0 into GOOD

FIRST AT ALL, BE SURE WHAT YOU DO, I AM NOT RESPONSIBLE FOR ANY DAMAGE, ETC... AT YOUR OWN RISK, THIS IS MY EXPERIENCE, IT CAN BUT IT MUST NOT WORK ON YOUR PHONE, YOU HAVE BEEN WARNED BERFORE DOING ANY ACTION
Guys, this is a story of a 3 year odyssey to get my IMEI on this phone back and at the end, YES!!! it works again. 100% full signal came back.
Now let's get into in....
First, tools you need to recovery your IMEI again.
- phone must be unlocked
- phone must be root
- phone should be on original stock 5.1
- TWRP Recovery ROM (use twrp-3.0.2-0-xt1032)
- from PlayStore download "Partitions Backup"
- from PlayStore download "Root Browser"
- XPOSED Framework and XPOSED Installer
- IMEI CHANGER (XPOSED MODULE)
- .IMG (use attached)
The story:
A friend of mine bought 2013 a Moto G (1st Gen) and wanted to root by himself. Root doesen't work, so he kept up. He decided to put an other rom on his phone, what he doesen't know, he erased all with command everything before (DICKHEAD): Fastboot erase all and Fastboot erase recovery <-- KILLER
From this moment.. after rebooting his phone the was no signal anymore. Serveral ROM and MODEMS tried out. Nothing just WIFI works. He gave the phone to me. 3 years later i wanted to re-awake this wonderful phone back to life.
Now, here comes the steps, you should do, to re-gain your phone...
01. choose and use a stock 5.1 rom of your country and flash it by fastboot command as always...
02. after rom installation and after reboot, install TWRP recovery rom with fastboot
03. reboot into recovery and install root in TWRP (use: UPDATE-SuperSU-v2.46)
04. reboot and download from PlayStore "Partitions Backup" and "Root Browser" and "IMEI Changer"
05. download XPOSED Framework (zip) and XPOSED Installer (apk)
06. reboot into TWRP install XPOSED Framework
07. reboot and install the XPOSED Installer APK with Root Browser and install IMEI Changer Module in XPOSED
08. reboot system, go into IMEI Changer and change your IMEI (under the back cover of your phone)
09. reboot and type in phone *#06#, you should see right now your IMEI, but the signal is already lost right? Okay, let's go ahead...
10. now return into Root Browser and see if there is a folder on your SDCARD "PartitionsBackups", if not, start the App and return
11. copy all three .img (attached) into it, start the App "Partitions Backup" again. Navigate to 3 dotted menu and and check "Restore a Partition"
12. navigate with "Root Browser" to the folder "PartitionsBackups" on SDCARD and use the first one, if successful, restore also the both other partitions. Forget the dd commands in terminal or cmd (doesent work), use the APP on top.
13. if it's done, reboot and pray... GOOD LUCK
14. Congrats, your signal should be back.
15. use Partitions Backup to backup all your partitions (as .img) and store them elsewhere.
16. set IMEI Changer as inactive and reboot, check with *#06#, otherwise let it active
17. !!! GIVE ME A THANKS, IF YOU ARE HAPPY WITH THIS !!!

NOTE!
YOUR IMEI WILL NOT SHOWN IN FASTBOOT!
(bootloader) version: 0.5
(bootloader) version-bootloader: 411A
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Toshiba REV=06 PRV=01 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA8900FI4F
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 28F911020F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Wed Aug 19 23:46:25 UTC 2015"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_retde/falcon_umts:
(bootloader) ro.build.fingerprint[1]: 5.1/LPB23.13-56/56:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.full[0]: Blur_Version.221.21.56.falcon_umt
(bootloader) ro.build.version.full[1]: s.Retail.en.DE
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.045
(bootloader) version-baseband: MSM8626BP_1032.3116.98.00y EMEA_CUST
(bootloader) kernel.version[0]: Linux version 3.4.42-g89906d6 ([email protected]
(bootloader) kernel.version[1]: ilclbld34) (gcc version 4.8 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Mon Aug 17 19:06:25 CDT 2015
(bootloader) sdi.git: git=MBM-NG-V41.1A-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.1A-0-g199f3c5
(bootloader) rpm.git: git=MBM-NG-V41.1A-0-g8b7736e
(bootloader) tz.git: git=MBM-NG-V41.1A-0-g99c1a7c
(bootloader) aboot.git: git=MBM-NG-V41.1A-0-g80481ae
(bootloader) qe: qe 1/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.104s

Reserved #2

Reserved #3

Can it work on Moto E dual sim 2014 indian version
Jerome-X said:
FIRST AT ALL, BE SURE WHAT YOU DO, I AM NOT RESPONSIBLE FOR ANY DAMAGE, ETC... AT YOUR OWN RISK, THIS IS MY EXPERIENCE, IT CAN BUT IT MUST NOT WORK ON YOUR PHONE, YOU HAVE BEEN WARNED BERFORE DOING ANY ACTION
Guys, this is a story of a 3 year odyssey to get my IMEI on this phone back and at the end, YES!!! it works again. 100% full signal came back.
Now let's get into in....
First, tools you need to recovery your IMEI again.
- phone must be unlocked
- phone must be root
- phone should be on original stock 5.1
- TWRP Recovery ROM (use twrp-3.0.2-0-xt1032)
- from PlayStore download "Partitions Backup"
- from PlayStore download "Root Browser"
- XPOSED Framework and XPOSED Installer
- IMEI CHANGER (XPOSED MODULE)
- .IMG (use attached)
The story:
A friend of mine bought 2013 a Moto G (1st Gen) and wanted to root by himself. Root doesen't work, so he kept up. He decided to put an other rom on his phone, what he doesen't know, he erased all with command everything before (DICKHEAD): Fastboot erase all and Fastboot erase recovery <-- KILLER
From this moment.. after rebooting his phone the was no signal anymore. Serveral ROM and MODEMS tried out. Nothing just WIFI works. He gave the phone to me. 3 years later i wanted to re-awake this wonderful phone back to life.
Now, here comes the steps, you should do, to re-gain your phone...
01. choose and use a stock 5.1 rom of your country and flash it by fastboot command as always...
02. after rom installation and after reboot, install TWRP recovery rom with fastboot
03. reboot into recovery and install root in TWRP (use: UPDATE-SuperSU-v2.46)
04. reboot and download from PlayStore "Partitions Backup" and "Root Browser" and "IMEI Changer"
05. download XPOSED Framework (zip) and XPOSED Installer (apk)
06. reboot into TWRP install XPOSED Framework
07. reboot and install the XPOSED Installer APK with Root Browser and install IMEI Changer Module in XPOSED
08. reboot system, go into IMEI Changer and change your IMEI (under the back cover of your phone)
09. reboot and type in phone *#06#, you should see right now your IMEI, but the signal is already lost right? Okay, let's go ahead...
10. now return into Root Browser and see if there is a folder on your SDCARD "PartitionsBackups", if not, start the App and return
11. copy all three .img (attached) into it, start the App "Partitions Backup" again. Navigate to 3 dotted menu and and check "Restore a Partition"
12. navigate with "Root Browser" to the folder "PartitionsBackups" on SDCARD and use the first one, if successful, restore also the both other partitions. Forget the dd commands in terminal or cmd (doesent work), use the APP on top.
13. if it's done, reboot and pray... GOOD LUCK
14. Congrats, your signal should be back.
15. use Partitions Backup to backup all your partitions (as .img) and store them elsewhere.
16. set IMEI Changer as inactive and reboot, check with *#06#, otherwise let it active
17. !!! GIVE ME A THANKS, IF YOU ARE HAPPY WITH THIS !!!
Click to expand...
Click to collapse
Bro, I also lost my imei number for moto e, it shows imei: 0, but in fastboot getvarall, it shows imei number.I think the img file you have attached will be different for moto e. I am ready to do anything, please guide. Thanks and regards

Im not an expert, but this method seems dangerous. The partitions you have attached are unique to your device, and flashing them on another device could cause serious permanent problems. I would suggest you remove these instructions until it is known what is contained within the hob, dhob and fsc partitions, unless someone can correct me.

Its up to the user to doing any action. This is my story, and my very own solution here, i wrote.
Gesendet von meinem SM-A310F mit Tapatalk

Professor Gibbins said:
Im not an expert, but this method seems dangerous. The partitions you have attached are unique to your device, and flashing them on another device could cause serious permanent problems. I would suggest you remove these instructions until it is known what is contained within the hob, dhob and fsc partitions, unless someone can correct me.
Click to expand...
Click to collapse
What problems? Even if they are the same IMEI still there is little chance that 2 users to be in the same country same network and same city. Anyway there are a lot of people who used the command and are screwed so it's great tutorial to revive the device
Sent from Samsung Galaxy S7

Jerome-X said:
Its up to the user to doing any action. This is my story, and my very own solution here, i wrote.
Click to expand...
Click to collapse
Exactly, this could mean that an inexperienced user might follow these instructions without understanding the implications. And when you say this is your very own solution, it's literal. This solution only applies to your specific device.
Eurofighter_ty said:
What problems? Even if they are the same IMEI still there is little chance that 2 users to be in the same country same network and same city. Anyway there are a lot of people who used the command and are screwed so it's great tutorial to revive the device
Click to expand...
Click to collapse
The IMEI duplication was only an example. There could be many other irreversible issues that the user doesn't even immediately realise.
Essentially, these partitions should never be overwritten without first taking a backup.

Yes of course, u re right
Gesendet von meinem SM-A310F mit Tapatalk

Haha, I'm not fussed with being right - just wanting to point out/give my opinion on the possible risks.
By all means keep your tutorial, but could I suggest adding a step where the 3 partitions are backed up before they are overwritten, just in case they need those partitions in the future.

Thank you so much for this really useful guide, I was hopeless and finally after 3 years was able to make my phone work.

[SOLVED] [TWRP] Restore data of a damaged and encrypted Nexus5 (to a new Nexus5)

update: SOLVED - thread can be closed
Hi!
My phone got physically damaged while it was at a shop getting its display changed.
My setting was (as I reconstructed from my last backup):
TWRP 2.8.7.1 (or maybe 3.0.0.0)
Cyanogenmod cm-13.0-20160214-NIGHTLY-hammerhead-recovery (or maybe higher)
encrypted
I am trying to access the phone information and had it examined from a data recovery expert.
This is all the data I got on a USB:
data.emmc.win
system.ext4.win
system.ext4.win.md5
system.info
I don't know if the information stored in those file containers is still encrypted as I provided the data recovery expert with my encryption key.
My idea was to get a new Nexus5, install TWRP and try to restore the partitions. I would then have been able to use the new phone as a 1:1 replacement of the old one.
Unfortunately it didn't work (out of the box).
Maybe this would work? [TUTORIAL] Create Flashable Zip From CWM/TWRP Backup (MTK)
My other idea is to access the different files directly, but that failed too (I renamed system.ext4.win to system.ext4 and unzipped it with 7-Zip on Windows10). When opening the unzipped folder every files content is: "50 RHT.security.selinux=ubject_r:system_file:s0"
So, I do really need help.
Do you have any ideas?

fivel_ said:
Hi!
My phone got physically damaged while it was at a shop getting its display changed.
My setting was (as I reconstructed from my last backup):
TWRP 2.8.7.1 (or maybe 3.0.0.0)
Cyanogenmod cm-13.0-20160214-NIGHTLY-hammerhead-recovery (or maybe higher)
encrypted
I am trying to access the phone information and had it examined from a data recovery expert.
This is all the data I got on a USB:
data.emmc.win
system.ext4.win
system.ext4.win.md5
system.info
I don't know if the information stored in those file containers is still encrypted as I provided the data recovery expert with my encryption key.
My idea was to get a new Nexus5, install TWRP and try to restore the partitions. I would then have been able to use the new phone as a 1:1 replacement of the old one.
Unfortunately it didn't work (out of the box).
Maybe this would work? [TUTORIAL] Create Flashable Zip From CWM/TWRP Backup (MTK)
My other idea is to access the different files directly, but that failed too (I renamed system.ext4.win to system.ext4 and unzipped it with 7-Zip on Windows10). When opening the unzipped folder every files content is: "50 RHT.security.selinux=ubject_r:system_file:s0"
So, I do really need help.
Do you have any ideas?
Click to expand...
Click to collapse
These are partition dumps (at least I think they are, maybe they are empty and just appeared on the USB flash drive out of thin air), not zip files.
In theory you should be able to flash them to another phone (using dd) and be ready to go, however the N5 might use the quallcomm hardware key storage method in which case the only way to access your data seems to be decrypting it on the device. What part of your device is damaged? Maybe you can still access the recovery via adb and then decrypt it even iff your screen is destroyed.

Thanks a lot!
My old phone is rendered unusable without any chance of using it again.
So I bought an used Nexus5 and am looking for ways to recreate the partitions etc exactly the same way they were on the old phone.
I stored the files
data.emmc.win
system.ext4.win
system.ext4.win.md5
system.info
on the new Nexus5 and accessed the folder via TWRP and told it to use it as recovery/restore from backup. Unfortunately this didn't work (at the first time).
Whats next??

fivel_ said:
Thanks a lot!
My old phone is rendered unusable without any chance of using it again.
So I bought an used Nexus5 and am looking for ways to recreate the partitions etc exactly the same way they were on the old phone.
I stored the files
data.emmc.win
system.ext4.win
system.ext4.win.md5
system.info
on the new Nexus5 and accessed the folder via TWRP and told it to use it as recovery/restore from backup. Unfortunately this didn't work (at the first time).
Whats next??
Click to expand...
Click to collapse
@nailyk helped me a lot this github thread Issue 863. Thanks!

hi @fivel_
How goes your experiments? Where you able to restore the dump of the broken device?
Does the broken device start into fastboot mode?

hi @nailyk!
I think what I have from my old phone is the image of the two major partititions - system and data (I don’t know where the others like boot or recovery are - maybe they are sub-partititions or something like that in the big data partition (13GiB)?).
edit: the partitions of a regular nexus5 can be seen here:
guide-repartition-nexus5
i think a regular „fastboot flash parition“ would not work. But I don’t know what can work and I do not exactly know where and what to search. so I am still left in the dark - did not know that there was so much to know regarding phone storage and partition.
ps: my old broken phone was not able to be recognized from windows. I will try again after making sure it is completeley charged.

If you have the same rom on your new device, that on the old one, and the data dump isn't broken, fastboot flash userdata -S 512M <your dump> should work.

okay, so the correct would be to
1. restore new phone from backup (in order to get the old rom on the new phone)
2. flash userdata.
right?

ok, I managed to connect to the old device via fastboot:
Is it maybe not as dead after all? The screen is not working, sadly
what can I do next?
Code:
C:\Users\fivel\Documents\Android\platform-tools-latest-windows\platform-tools>fastboot getvar all
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.28
(bootloader) version-bootloader: HHZ11k
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D821(E) 16GB
(bootloader) serialno: 065f8e4100746380
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 3321fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4
all:
finished. total time: 0.211s
And I managed to go to recovery-mode, blindly, and get ADB working. Does the result look damaged?
Code:
~ # [6nls
boot res
cache root
charger sbin
data sdcard
default.prop seapp_contexts
dev selinux_version
etc sepolicy
file_contexts service_contexts
firmware sideload
fstab.hammerhead supersu
init sys
init.rc system
init.recovery.hammerhead.rc tmp
init.recovery.usb.rc twres
license ueventd.hammerhead.rc
persist ueventd.rc
proc usb-otg
property_contexts vendor
recovery

fivel_ said:
ok, I managed to connect to the old device via fastboot:
Is it maybe not as dead after all? The screen is not working, sadly
what can I do next?
Code:
C:\Users\fivel\Documents\Android\platform-tools-latest-windows\platform-tools>fastboot getvar all
(bootloader) version-hardware: rev_11
(bootloader) version-baseband: M8974A-2.0.50.2.28
(bootloader) version-bootloader: HHZ11k
(bootloader) version-cdma: N/A
(bootloader) variant: hammerhead D821(E) 16GB
(bootloader) serialno: 065f8e4100746380
(bootloader) carrier: None
(bootloader) secure-boot: yes
(bootloader) unlocked: yes
(bootloader) product: hammerhead
(bootloader) partition-size:aboot: 80000
(bootloader) partition-type:aboot: emmc
(bootloader) partition-size:boot: 1600000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:recovery: 1600000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:system: 40000000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:userdata: 3321fa800
(bootloader) partition-type:userdata: ext4
(bootloader) partition-size:cache: 2bc00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:persist: 1000000
(bootloader) partition-type:persist: ext4
all:
finished. total time: 0.211s
And I managed to go to recovery-mode, blindly, and get ADB working. Does the result look damaged?
Code:
~ # [6nls
boot res
cache root
charger sbin
data sdcard
default.prop seapp_contexts
dev selinux_version
etc sepolicy
file_contexts service_contexts
firmware sideload
fstab.hammerhead supersu
init sys
init.rc system
init.recovery.hammerhead.rc tmp
init.recovery.usb.rc twres
license ueventd.hammerhead.rc
persist ueventd.rc
proc usb-otg
property_contexts vendor
recovery
Click to expand...
Click to collapse
Perfect. You are where I would bring you
For the next time: download your twrp, go into fastbootmode and fastboot boot twrp.img
It will download and boot into twrp.
Then you should be able to decrypt with twrp decrypt <your password>
Maybe <your password> need to be typed in hexa.
fivel_ said:
okay, so the correct would be to
1. restore new phone from backup (in order to get the old rom on the new phone)
2. flash userdata.
right?
Click to expand...
Click to collapse
Exactly, use the same rom, flash your userdata reboot.
Now you have two way to get your data back. Good luck

nailyk said:
Perfect. You are where I would bring you
Click to expand...
Click to collapse
Great thanks!!
For the next time: download your twrp, go into fastbootmode and fastboot boot twrp.img
Click to expand...
Click to collapse
ok, done!
Code:
C:\Users\fivel\Documents\Android\platform-tools-latest-windows\platform-tools>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.748s]
booting...
OKAY [ 0.114s]
finished. total time: 0.868s
It will download and boot into twrp.
Then you should be able to decrypt with twrp decrypt <your password>
Maybe <your password> need to be typed in hexa.
Click to expand...
Click to collapse
ok, how do I perform this command?
twrp decrypt - in ADB, in Fastboot, else?

ok, one more step:
1. i got to adb in recovery mode again.
2. i startet a shell via adb shell
3. decrypt:
~ # twrp decrypt ********
Attempting to decrypt data partition via command line.
Data successfully decrypted, new block device: '/dev/block/dm-0'
Click to expand...
Click to collapse
and now?
edit:
now I performed,
4. adb pull /dev/block/dm-0 /data.img
and it is running... we will see what is inside

so, now I have the data.img on my pc.
do I first need it to transfer to the new phone, or can I just type:
fastboot flash userdata -S 512M data.img
thanks a lot for all your help @nailyk!

fivel_ said:
ok, one more step:
1. i got to adb in recovery mode again.
2. i startet a shell via adb shell
3. decrypt:
and now?
edit:
now I performed,
4. adb pull /dev/block/dm-0 /data.img
and it is running... we will see what is inside
Click to expand...
Click to collapse
o0 Data successfully decrypted
So the data.img you catch is the full filesystem without encryption
you can mount loop it in any linux
fivel_ said:
so, now I have the data.img on my pc.
do I first need it to transfer to the new phone, or can I just type:
fastboot flash userdata -S 512M data.img
Click to expand...
Click to collapse
yes this will put your data (unencrypted it seems) into your old device
thanks a lot for all your help @nailyk!
Click to expand...
Click to collapse
No pbm Glad you solve it.

hi!
I had not got the time to apply your advice to my phone... today I did.
when I type: fastboot flash userdata -S 512M e:mypathtolocation/data.img
i get: Invalid sparse file format at header magi
I guess this is a small error, as I was able to open the image and it looks like the userdata.
the folders inside the image are: adb, anr, app, app-asec, app-lib, app-private, backup, bootchart, dalvik-cache, data, dontpanic, drm, local, lost+found, media, etc.
What do I do now? @nailyk your help and advice is always appreciated!

fivel_ said:
hi!
I had not got the time to apply your advice to my phone... today I did.
when I type: fastboot flash userdata -S 512M e:mypathtolocation/data.img
i get: Invalid sparse file format at header magi
I guess this is a small error, as I was able to open the image and it looks like the userdata.
the folders inside the image are: adb, anr, app, app-asec, app-lib, app-private, backup, bootchart, dalvik-cache, data, dontpanic, drm, local, lost+found, media, etc.
What do I do now? @nailyk your help and advice is always appreciated!
Click to expand...
Click to collapse
Reboot ?
Also if your new dump isn't encrypted anymore you can mount loop it into any linux distro. If you don't have one, look for FWUL into my signature.
Glad your problem is now solved

thanks again, I have recovered ALL the lost data

Glad it worked
When there is a shell, there is a way
P.S.: please change title of first post to mark it as solved. Then asks Moderators for closing.

Database Info

welcome