Database Info

[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!

[Q] Stuck on HTC boot screen after sudden restart

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

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

Up Volume button not working when trying to unlock Bootloader

I am able to connect my phone (BLU STUDIO 6.0 HD) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. :crying: I would appreciate any help.

volume up not working in bootloader
I am able to connect my phone (lenovo vibe c2 k10a40) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. I would appreciate any help.
I'm sorry for my English, I'm brazilian

same here im on a figo gravity x55l i sent in a ticket to figo support and they just ignored it but anyway
i tried
fastboot oem unlock
fastboot oem unlock-go
and also activating oem unlock in dev settings and doing fastboot methods again...nothing
i looked up that a phone unlocks its bootloader by enableing oem unlock in dev settings and doing a format and still nothing
---------- Post added at 03:15 PM ---------- Previous post was at 02:56 PM ----------
has anyone tried with a headset with volume buttons? i know it is crazy but i dont have a pair to try lol

GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click like if this helped to get the word out...I think that's how it works

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
I'm new to mediatek and I have the same problem volume up won't unlock bootloader. I had the same idea you did and hopefully you can help.
First off I'm not sure I have the right firmware I have a Blu studio m5 plus is what the box says. The stock recovery calls it Blu dash xl when I look up firmware for Blu studio m5 plus it has one from need rom and you need to pay for an account to download. If you look up the dash xl firmware I was able to find it free and its specs match my phone I think it's the right firmware. If I patch the boot img from magisk. I need help with flashing with sp flash tool. Did you replace the actual boot img from the firmware with the new patched boot img or did you just load the new boot img from another folder. See I don't know what the Android scatter file really does. Does the boot img have to be in the same folder as firmware to flash because the scatter file finds that folder or not? And help with the checksum gen I'm unfamiliar how do I use it? What does it do? How do I use it to verify?

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
You need to try twrp porter from hovatek YouTube channel you can flash twrp without unlocking the bootloader.
https://forum.hovatek.com/thread-21839.html
I first made a backup with Wwr tool from hovatek without having root or unlocking bootloader then I patched my bootimg with magisk. Copied the boot img and scater file that Wwr tool also makes into a folder flashed the patched boot Img with S P flash tool rebooted was rooted with magisk. Then I used twrp booter and it takes like 3 minutes to make you a twrp out of your backup you get from Wwr tool. Without any work I just hit 6 enter puts out twrp recovery and I flashed that with s p flash tool rebooted directly into twrp recovery from phone off and it works great. With a locked bootloader.

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
Thank you so much for this guide, really worked like a charm. Been having troubles with flashing from fastboot mode due to button trouble.
Many thanks!!!

This method is interesting, does it really work? I am trying to get ROOT on this BLU Studio 6.0 HD D651 terminal, but it is useless, I cannot pass the bootloader security sector, I CANNOT flash the Recovery Partition, I am also trying to create the TWRP for a BLU Studio 6.0 HD D651 with this Hovatek program, but I can't conclude the flashing of this file
"ERROR in partition size", read Fastboot mode with Advenger Box and everything is fine, except the protected sector of the computer, bootloader locked ON. I leave here the Registry to see if you can help me. I also tried SP Flash Tools and it is the same, the Flash concludes well (GOOD / OK) but I restart in Recovery and it is the same Recovery Stock.
I also asked the people of Hovatek and they say that it is necessary to unlock the bootloader of the terminal, so what the partner says above I do not understand how I manage to circumvent security!
Posd. On the TWRP Team page the file “TWRP Custom Recovery 2.8 for BLU Studio 6.0 HD” was deleted! (Can anyone share it?)
Fastboot Reading phone info Avengers Box 0.6.2
max-download-size: 134217728
partition-size: userdata: 32000000
partition-type: userdata: ext4
partition-size: cache: 7e00000
partition-type: cache: ext4
partition-size: system: 3e800000
partition-type: system: ext4
partition-size: expdb: a00000
partition-type: expdb: raw data
partition-size: logo: 300000
partition-type: logo: raw data
partition-size: misc: 80000
partition-type: misc: raw data
partition-size: sec_ro: 600000
partition-type: sec_ro: ext4
partition-size: recovery: 1000000
partition-type: recovery: raw data
partition-size: boot: 1000000
partition-type: boot: raw data
partition-size: uboot: 60000
partition-type: uboot: raw data
partition-size: seccfg: 20000
partition-type: seccfg: raw data
partition-size: protect_s : a00000
partition-type: protect_s : ext4
partition-size: protect_f: a00000
partition-type: protect_f: ext4
partition-size: nvram: 500000
partition-type: nvram: raw data
partition-size: pro_info: 300000
partition-type: pro_info: raw data
partition-size: ebr1: 80000
partition-type: ebr1: raw data
partition-size: mbr: 80000
partition-type: mbr: raw data
partition-size: preloader: 1400000
partition-type: preloader: raw data
off-mode-charge: 1
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: J805B_BLU
version: 0.5
Capture CMD ERROR:

EngelP said:
This method is interesting, does it really work? I am trying to get ROOT on this BLU Studio 6.0 HD D651 terminal, but it is useless, I cannot pass the bootloader security sector, I CANNOT flash the Recovery Partition, I am also trying to create the TWRP for a BLU Studio 6.0 HD D651 with this Hovatek program, but I can't conclude the flashing of this file
"ERROR in partition size", read Fastboot mode with Advenger Box and everything is fine, except the protected sector of the computer, bootloader locked ON. I leave here the Registry to see if you can help me. I also tried SP Flash Tools and it is the same, the Flash concludes well (GOOD / OK) but I restart in Recovery and it is the same Recovery Stock.
I also asked the people of Hovatek and they say that it is necessary to unlock the bootloader of the terminal, so what the partner says above I do not understand how I manage to circumvent security!
Posd. On the TWRP Team page the file “TWRP Custom Recovery 2.8 for BLU Studio 6.0 HD” was deleted! (Can anyone share it?)
Fastboot Reading phone info Avengers Box 0.6.2
max-download-size: 134217728
partition-size: userdata: 32000000
partition-type: userdata: ext4
partition-size: cache: 7e00000
partition-type: cache: ext4
partition-size: system: 3e800000
partition-type: system: ext4
partition-size: expdb: a00000
partition-type: expdb: raw data
partition-size: logo: 300000
partition-type: logo: raw data
partition-size: misc: 80000
partition-type: misc: raw data
partition-size: sec_ro: 600000
partition-type: sec_ro: ext4
partition-size: recovery: 1000000
partition-type: recovery: raw data
partition-size: boot: 1000000
partition-type: boot: raw data
partition-size: uboot: 60000
partition-type: uboot: raw data
partition-size: seccfg: 20000
partition-type: seccfg: raw data
partition-size: protect_s : a00000
partition-type: protect_s : ext4
partition-size: protect_f: a00000
partition-type: protect_f: ext4
partition-size: nvram: 500000
partition-type: nvram: raw data
partition-size: pro_info: 300000
partition-type: pro_info: raw data
partition-size: ebr1: 80000
partition-type: ebr1: raw data
partition-size: mbr: 80000
partition-type: mbr: raw data
partition-size: preloader: 1400000
partition-type: preloader: raw data
off-mode-charge: 1
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: J805B_BLU
version: 0.5
Capture CMD ERROR:
Click to expand...
Click to collapse
Yeah it works try it but remember your bootloader is still locked so installing twrp might softbrick your device...find a way to unlock your bootloader

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
I tried this and it worked !
I've been trying to Flash-Root MTK 6580 Blu studio G2 HD,
Volume Up wasn't working to Unlock Bootloader . (I had to unlock it)
Flashed the patched boot.img with Spflash and it worked, i rooted my phone without unlocking bootloader.
Someone in the above comments said to Unlock Bootloader somehow, Flashing anything with TWRP or anyother software may brick phone.
(I think you shouldn't unlock bootloader unless you absolutely need it)

Volume up button
I was having the same trouble.
Check if you have any software update .
Update them and try again i hope it will work.
It works for me samsung a10s

Techguy777 said:
You need to try twrp porter from hovatek YouTube channel you can flash twrp without unlocking the bootloader.
https://forum.hovatek.com/thread-21839.html
I first made a backup with Wwr tool from hovatek without having root or unlocking bootloader then I patched my bootimg with magisk. Copied the boot img and scater file that Wwr tool also makes into a folder flashed the patched boot Img with S P flash tool rebooted was rooted with magisk. Then I used twrp booter and it takes like 3 minutes to make you a twrp out of your backup you get from Wwr tool. Without any work I just hit 6 enter puts out twrp recovery and I flashed that with s p flash tool rebooted directly into twrp recovery from phone off and it works great. With a locked bootloader.
Click to expand...
Click to collapse
Thanks SO much Techguy777!! I can absolutely confirm that after MANY, MANY days day of trying to get my MTK6582 device rooted , this process worked perfectly without unlocking the bootloader. I already had the Magisk patched boot image file and all the SP Flash tool set but didn't know how to use them correctly. I followed the step-by-step guide here:
SP Flash Tool - Basic User Guide
Install Mediatek Drivers Extract the Mediatek_USB_Driver_Auto-Installer zip file. Run the installer file that is extracted from zip by right clicking the .exe file and click on "Run as Administrator". ( the exe file that comes out of zip = Mediatek_Driver_Auto-Installer.exe ) Click on "Install"...
gpdcentral.com
Enjoy!

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
Thank you. This really works to get magisk so easily installed without having to unlock bootloader. No need to even install TWRP recovery.

SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click like if this helped to get the word out...I think that's how it works
Click to expand...
Click to collapse
What is Checksum_gen file? I can't find it in firmware folder

lyehengfoo said:
Thank you. This really works to get magisk so easily installed without having to unlock bootloader. No need to even install TWRP recovery.
Click to expand...
Click to collapse
Please guide me too. What is Checksum_gen file? I can't find it in firmware folder

[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:
~ # ls
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:
~ # ls
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.