Database Info

[A510][EXPERIMENTAL][DON'T USE] CWM Recovery 6.0.1.0.

Inspirated by the thread of pawitp (http://forum.xda-developers.com/showthread.php?t=1791165) I just built a CWM 6.0.1.0 /wo touch on http://builder.clockworkmod.com/. (Finished Build: http://jenkins.cyanogenmod.com/job/recovery/2646/)
It starts up but is not usable since the power button is not recognised and therefore not menu entries can be selected. :crying:
I used
Code:
fastboot flash recovery recovery.img
and it works if the recovery is entered by Vol- button. Weird enought it can not be entered by
Code:
adb reboot recovery
which seems to pop up the stock recovery
How is this possible? I am still new to the android infrastructure and learning how everything goes but this is something I have not expected...
If someone could enlighten me with facts to this matter I would be grateful.
I will also try to build a touch versionl. That might work better.
Edit: since also pawitp bricked his device i highly recommend to NOT USE ANY CUSTOM RECOVERY until we have found out what causes this bricks!

mearoth said:
Inspirated by the thread of pawitp (http://forum.xda-developers.com/showthread.php?t=1791165) I just built a CWM 6.0.1.0 /wo touch on http://builder.clockworkmod.com/. (Finished Build: http://jenkins.cyanogenmod.com/job/recovery/2646/)
It starts up but is not usable since the power button is not recognised and therefore not menu entries can be selected. :crying:
I used
Code:
fastboot flash recovery recovery.img
and it works if the recovery is entered by Vol- button. Weird enought it can not be entered by
Code:
adb reboot recovery
which seems to pop up the stock recovery
How is this possible? I am still new to the android infrastructure and learning how everything goes but this is something I have not expected...
If someone could enlighten me with facts to this matter I would be grateful.
I will also try to build a touch versionl. That might work better.
Click to expand...
Click to collapse
Hi mearoth,
My recoveries (see other thread in this forum) are build exactly like that, in my case I used the Dees-Troy fstab file. But... be really, really careful. If you do it this way, backup/restore and format stuff may brick your device. We've had one guy that had a simple FOTA bricking his device, so again... be really really careful...
Regards,
Nika.

just as a comparison :
fstab from dees-troy :
Code:
/system ext4 /dev/block/mmcblk0p3
/data ext4 /dev/block/mmcblk0p10 length=-1048576
/cache ext4 /dev/block/mmcblk0p4
/misc emmc /dev/block/mmcblk0p5
/flexrom ext4 /dev/block/mmcblk0p6
/sdcard vfat /dev/block/sda1 /dev/block/mmcblk1p1
/boot emmc /dev/block/mmcblk0p2
/aboot emmc /dev/block/mmcblk0p8
/recovery emmc /dev/block/mmcblk0p1
/flex ext4 /dev/block/mmcblk0p6
/sdc vfat /dev/block/mmcblk1p1
fstab from the current cwn for a700:
Code:
# mount point fstype device [device2]
/sdcard vfat /dev/block/mmcblk1p1
/emmc datamedia /dev/null
/system ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
/cache ext4 /dev/block/platform/sdhci-tegra.3/by-name/CAC
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-32768 # TODO: verify
/misc emmc /dev/block/platform/sdhci-tegra.3/by-name/MSC
/boot emmc /dev/block/platform/sdhci-tegra.3/by-name/LNX
/recovery emmc /dev/block/platform/sdhci-tegra.3/by-name/SOS
/staging emmc /dev/block/platform/sdhci-tegra.3/by-name/USP
can it be only a problem of partition size that cause the crash of data partition ?
Reminder for comparison (credit nikagl ) :
Code:
/dev/block/platform/sdhci-tegra.3/by-name/SOS /dev/block/mmcblk0p1 /recovery
/dev/block/platform/sdhci-tegra.3/by-name/LNX /dev/block/mmcblk0p2 /boot
/dev/block/platform/sdhci-tegra.3/by-name/APP /dev/block/mmcblk0p3 /system
/dev/block/platform/sdhci-tegra.3/by-name/CAC /dev/block/mmcblk0p4 /cache
/dev/block/platform/sdhci-tegra.3/by-name/MSC /dev/block/mmcblk0p5 /misc
/dev/block/platform/sdhci-tegra.3/by-name/FLX /dev/block/mmcblk0p6 /system/vendor /flexrom /flex
/dev/block/platform/sdhci-tegra.3/by-name/AKB /dev/block/mmcblk0p7 ?
/dev/block/platform/sdhci-tegra.3/by-name/USP /dev/block/mmcblk0p8 /aboot (bootloader.blob)
/dev/block/platform/sdhci-tegra.3/by-name/DE2 /dev/block/mmcblk0p9 ?
/dev/block/platform/sdhci-tegra.3/by-name/UDA /dev/block/mmcblk0p10 /data

BENETNATH said:
just as a comparison :
can it be only a problem of partition size that cause the crash of data partition ?
Click to expand...
Click to collapse
Could be well.
I currently try to build CWM and CM10 on my ubuntu machine and have taken the repositories of pawitp as starting point and have found that A700 and A510 have slightly different partition sizing reguarding the APP partition. But that should not be a matter.
pawtip has also changed the following in his repository from recovery.fstab
Code:
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-1081344
Since partition sizes of /data are the same on A510 and A700 that could do the trink as I think pawtip's recovery is working.

mearoth said:
Could be well.
I currently try to build CWM and CM10 on my ubuntu machine and have taken the repositories of pawitp as starting point and have found that A700 and A510 have slightly different partition sizing reguarding the APP partition. But that should not be a matter.
pawtip has also changed the following in his repository from recovery.fstab
Code:
/data ext4 /dev/block/platform/sdhci-tegra.3/by-name/UDA length=-1081344
Since partition sizes of /data are the same on A510 and A700 that could do the trink as I think pawtip's recovery is working.
Click to expand...
Click to collapse
it might be a good option to ask to pawtip how he found this value then, can you check with him ?

Guys be EXTRA carefull. Pawitp just bricked his A700 flashing a new version of CM10 he was working on !!! It's not the first time he flashes but this time the process hanged, he had to reboot and now his tablet is stuck in APX mode (which is bad).
I suggest we all stop messing around too much much until we know more about those brick issues...

I just heard he also bricked his device
---------- Post added at 10:25 AM ---------- Previous post was at 10:09 AM ----------
paugustin said:
Guys be EXTRA carefull. Pawitp just bricked his A700 flashing a new version of CM10 he was working on !!! It's not the first time he flashes but this time the process hanged, he had to reboot and now his tablet is stuck in APX mode (which is bad).
I suggest we all stop messing around too much much until we know more about those brick issues...
Click to expand...
Click to collapse
Haha.. sorry, using my test account to see whether I can respond to dev-threads which works fine and also now say you already responded...

paugustin said:
I suggest we all stop messing around too much much until we know more about those brick issues...
Click to expand...
Click to collapse
I hear you and I think you are right. I will try digging a bit deeper into the whole flashing issue. Perhaps we can also investigate further in getting the sbk in order to enable us the APX flashing. I will try contacting Acer Europe once more.
Sent from my MB526 using xda developers app

For my knowledge, can you explain me how you get the mength value for the fstab ??
because the recovery you have created was with "length=-32768"

The "length=-32768" was just a value I have taken over by the nexus i think. however.
I just had a deeper look at the raw content of the mmc (dd if=/dev/block/mmcblk0 of=/data/mmcblck0-40000 count=40000) and have found something like a partition table at offset 0x30.00.00 . Since I believe it is not a regular partition table (nothing I know yet to be honest) I have not found out the sizes and offsets of the partitions. What I have found out though, is the fact that there are far more partitions than we know. Here comes the list in the order as they are in the RAW:
BCT <- (EDIT: Boot Config Table - contains HW timings etc. .. first siginficant offset in raw at 0x10 00 00)
PT <- (Partition Table - only a guess but the data is in the second significant offset at 0x30 00 00)
EBT <- EDIT: first Bootloader - when finished -> loads either LNX or SOS to go on in boot chain
EKS
DE1
GP1
-- Then comes the ones we already know:--
SOS
LNX
APP
CAC
MSC
FLX
AKB
USP
DE2
UDA
-- And one more we do not know:
GPT <- This could be a second partition table. this would not be unusual to have the table doubled at beginning and end. but I have not checket yet.
And here comes a possible explanation for the bricks: could it be since we do not have this in our fstab and the lengh value of UDA beeing probably incorrect that at some point when flashing the system overwrites bytes of this partition destroing the PT ? --> brick because bootloader can not determin right partition sizing any more. also this could happen at some point only when bytes are written to the GPT without us knowing. so flashing might work several times until it happens to strike this partition.
What do you think?
I will definitly investigate a bit more on that matter.

thanks for this
might be useful..
we need more gurus on that point, who can we reach to help us ? koush ?

I just got a reply from pawitp via pm:
pawitp said:
My brick is not due to formatting /data (The CWM I built does /data format using rm -rf), and I'm actually not sure why it bricked. The GPT at the end is the one read by linux.
Click to expand...
Click to collapse
So my guess was wrong. -> back to start.
I will nevertheless have a look at those hidden partitions. Some guru might really help but I don't know enought people here due to having been inactive for a long time.

good to know too.. strange

hi, any news for building the new CWM?

Nah. I first want to know what causes all the bricks or have at least a fallback scenario like working APX mode..
Now regarding APX i once more had no luck with acer people to get the sbk... this folk's so unhelpful :thumbdown:
Reguarding bricks pawitp had an idea that the samsung mmc brickbug might be present on our devices and has disabled mmc erase command in the kernel.
Now that is a todo for me for our kernel or i have time to test if our kernels are compatible. Beside this pawitp is not sure if it really IS the mmc bug. But IMHO it is a good guess.
Sent from my A510 using xda app-developers app

mearoth said:
Nah. I first want to know what causes all the bricks or have at least a fallback scenario like working APX mode..
Now regarding APX i once more had no luck with acer people to get the sbk... this folk's so unhelpful :thumbdown:
Reguarding bricks pawitp had an idea that the samsung mmc brickbug might be present on our devices and has disabled mmc erase command in the kernel.
Now that is a todo for me for our kernel or i have time to test if our kernels are compatible. Beside this pawitp is not sure if it really IS the mmc bug. But IMHO it is a good guess.
Sent from my A510 using xda app-developers app
Click to expand...
Click to collapse
Well, my device does still come up with APX mode (regardless of the broken screen), so if I ever need to test anything in APX mode for anyone, let me know. I've tried many different versions of nvflash, but nothing worked so far. Best option was one that authenticated to acer, but without the acer username and password or some way to spoof that, I don't think we'll be able to get this going...

nikagl said:
Well, my device does still come up with APX mode (regardless of the broken screen), so if I ever need to test anything in APX mode for anyone, let me know. I've tried many different versions of nvflash, but nothing worked so far. Best option was one that authenticated to acer, but without the acer username and password or some way to spoof that, I don't think we'll be able to get this going...
Click to expand...
Click to collapse
You are right. I got a version of nvflash running on my ubuntu machine but since our device is in APX secure mode the secure boot key is needed in order to do anything usefull with it. As long as we do not have this key we can really only ask acer to give it. There might even be a chance to get it since i heard the a200 sbk was also released. That's what i am currently on. Finding out whom to contact to get the sbk..
Sent from my A510 using xda developers app

[SOLVED] Possibly Bricked my Phone: Can't unmount/format/wipe the /cache partition

Hi All,
I have been flashing back and forth a bit from CM9 to CM10 to try things out. Today, I attempted to restore back to CM9 and it hung for over an hour, so I hard restarted it. Now, I can't restore anything, because it hangs on the /cache partition. I also receive the message while in recovery mode
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
Click to expand...
Click to collapse
I am able to get adb shell in recovery mode and I have gone through the steps to check for a bad emmc, which did not indicate badness. I have attempted to use umount from the shell on /cache, which just hangs. In recovery mode, over adb shell, I can ls and cat any of the files in /cache without apparent issue.
I have attempted Super Wipe, factory reset, manual formatting, and wipe cache, all to no avail (they all just hang).
I am running CWM 6.0.1.1.
dmesg has a message about an ext4 error, that makes me suspicious, but I don't know what to do about it.
<4>[ 8.431030] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4154: Filesystem error recorded from previous mount: IO failure
<4>[ 8.442413] EXT4-fs warning (device mmcblk0p26): ext4_clear_journal_err:4155: Marking fs in need of filesystem check.
<4>[ 8.462036] EXT4-fs (mmcblk0p26): warning: mounting fs with errors, running e2fsck is recommended
<6>[ 8.475463] EXT4-fs (mmcblk0p26): recovery complete
<6>[ 8.489562] EXT4-fs (mmcblk0p26): mounted filesystem with ordered data mode. Opts:
<6>[ 9.242095] key released
<6>[ 9.243774] key released
<6>[ 9.442749] msmsdcc_runtime_suspend: Enter WIFI suspend
<6>[ 9.542755] fsa9480 5-0025: fsa9480_init_detect
<6>[ 9.547424] fsa9480 5-0025: dev1: 0x0, dev2: 0x0
<2>[ 13.382751] EXT4-fs error (device mmcblk0p26): ext4_init_inode_table:1293: comm ext4lazyinit: Something is wrong with group 0
<2>[ 13.382751] Used itable blocks: 403itable unused count: 0
<2>[ 13.382781]
<3>[ 13.411773] Aborting journal on device mmcblk0p26-8.
<2>[ 13.429321] EXT4-fs (mmcblk0p26): Remounting filesystem read-only
Click to expand...
Click to collapse
Apparently my full dmesg output was too long, so if you need anything else please ask.
Thanks in advance for any help!

I am experiencing the same thing (I think) as the OP.
I had been running alpha2 of TeamChopsticks CM10. I installed the new recovery for the skyrocket (downloaded from teamchopsticks.org). Then rebooted into recovery. formatted /system -> installed alpha3 -> installed gapps -> installed darkside-wipe-cache-only -> rebooted. Then my phone just hung on the boot animation for 10+ minutes.
After rebooting I thought I would try to install alpha2 again. I tried to format /system, and it hung.
So I rebooted again, and tried to restore a backup. That hung on "Restoring .android_secure..."
So, I rebooted again. This time I tried a factory reset. It hung on "Wiping cache..."
After rebooting this time, I selected "show log" in CWM, which shows this (I don't know if this is helpful/related):
Code:
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
I:Can't partition unsafe device: /dev/block/mmcblk1p1
I:Can't format unknown volume: /external_sd
I have also tried Fixing Permissions in CWM, with no apparent change.
Also, any time I perform an action in CWM (show logs, fix permissions, etc.) and select "go back" in the menu, the menu disappears. I am still in recovery (still see the CWM logo in the background, and see the text from my previous action), but buttons do nothing and there is no menu.
Any help would be appreciated.
Josh
---------- Post added at 10:58 AM ---------- Previous post was at 10:20 AM ----------
Another follow up to my previous post:
I have tried to reinstall cm9 and cm10 alpha2.
With each I format /system, then when I select "Go Back" in the CWM menu the menu disappears (as I mentioned before). So, I reboot, then install zip from SD -> select the cm zip and get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cm-9-20120715-EXPERIMENTAL-skyrocket-beta1.zip
And nothing after that. It will just sit there.

Don't use darkside wipe, reflash sk8ers recovery From his thread
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |

vincom said:
Don't use darkside wipe, reflash sk8ers recovery From his thread
Click to expand...
Click to collapse
Interestingly (and perhaps ironically), looks like sk8er may be adding the Darkside Tools option in a forthcoming Recovery....
http://forum.xda-developers.com/showpost.php?p=30639023&postcount=267

That's pretty hilarious, so Darkside Wipe is apparently the way to go, except it doesn't work in my case.

So, I tried installing that recovery but it won't install (just like everything else).
I get this:
Code:
CWM-based Recovery v6.0.1.1
-- Installing: /sdcard/cwm6012touch_v11.zip
Is there a way to install his recovery that I am not aware of?
Thanks,
Josh

Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!

cthrax said:
Fantastic! With some help from the TeamChopsticks IRC channel, particularly sk8erwitskil, I installed CWM Touch 6.0.1.2 and was able to restore a backup of CM9 without an issue. Now that I can do that, I'm going to give CM10 alpha 3 another go.
Please see http://forum.xda-developers.com/showthread.php?t=1777970 for any further help with the recovery.
Cheers!
Click to expand...
Click to collapse
Why could u install the recovery and what was the solution
Posted w/xda app w/ i727R
MY STICKIES
| ROMS | KERNELS | FIRMWARE | RADIOS | HOWTO'S | GUIDES | INFo |
NEWB GUIDES TO: RESTORE TO STOCK | USE ODIN | INSTALL CWM | ROOT |

I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.

cthrax said:
I didn't do anything special to install recovery. I pushed the zip to my external card and installed it via the recovery. I assume the cache was not needed to be overwritten for the recovery install.
Click to expand...
Click to collapse
thats the way its done, i just dont understand why you couldnt do it the first place, and the cache has nothing todo with recovery just the rom

Ah, that's a confusion of terms. The original issue was that I could not restore from a backup. Or install a new rom. Apparently installing a new recovery was not an issue, I just didn't know that installing that would help at the time.

I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).

joshjryan said:
I just wanted to follow up that I was able to get my phone back thanks to help from Meanstreak242 in the IRC channel.
I ended up using an adb shell to dd the recovery image to the recovery partition (I *think* it was partition 22).
Click to expand...
Click to collapse
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!

KillaT21 said:
I'm gonna give this a go as well. Vin, seems you were onto something regarding usage in adb. I've been getting really familiar with it since. And now check out his results. Hopefully this'll work out for me too!!
Click to expand...
Click to collapse
Another no go. Cthrax, can you post or pm me exactly what you did?

KillaT21 said:
Another no go. Cthrax, can you post or pm me exactly what you did?
Click to expand...
Click to collapse
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!

cthrax said:
1. Mount phone as USB device
2. Copy newer version of ClockWorkMod Touch
3. Go back into recovery and "install zip from flash"
4. Reboot and restore backup.
5. Profit!
Click to expand...
Click to collapse
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3

KillaT21 said:
well I didnt have the exact circumstance of doing a restore. I just need to format my partitions so that would hopefully allow me to flash something else. My system basically tries its hardest to stay as Read Only. Even when I mount the system, nothing. I was hoping that with a new recovery I could. It "flashes", but once i reboot, its the same o Clockworkmod Recovery v5.8.1.3
Click to expand...
Click to collapse
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.

Well, joshjryan, I hope youre reading this too.
This caught my attention after a dmesg:
<6>[ 1478.616302] EXT4-fs (mmcblk0p24): mounted filesystem with ordered data mod
e. Opts:
So then I
~ # parted /dev/block/mmcblk0p24
parted /dev/block/mmcblk0p24
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p24
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Generic SD/MMC Storage Card (sd/mmc)
Disk /dev/block/mmcblk0p24: 627MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Could this be the cause??
Number Start End Size File system Flags
1 0.00B 627MB 627MB ext4
(parted)

cthrax said:
Maybe your variant of the problem is closer to what joshjryan did then. He had to use adb shell to manually use dd to copy the bits over. Hopefully he's watching and can chime in with some more comments.
Click to expand...
Click to collapse
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!

joshjryan said:
This does sound similar to what I was seeing.
I also was not able to actually install the new recovery. So I did this:
I extracted cwm0612touch to get recovery.img
Then I mounted my phones SB by USB and copied recovery.img to my sd card
Then in the adb shell to my phone I used dd to copy the image to the appropriate partition
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
Hopefully that does the trick for you!
Click to expand...
Click to collapse
It didnt. It installed to the right partition, but after reboot, cwmtouch5.8.1.3 is there again
Is it something in my reboot/boot that causes that?

[GUIDE][BRICKED] [BOOTS ONLY TO RECOVERY][All ASUS TRANFORMERS]

This is a general users guide to unbrick your Transformer tablet.
This guide will help you if your Asus tablet will only boot into recovery
and the command
Code:
adb reboot-bootloader
does not work to get you booted back to bootloader screen ..
If the above command works then skip to the first fastboot command ..
WHAT YOU NEED
An Asus tablet that will only boot into recovery …
Woking adb and fastboot on your PC
Windows drivers (if using Windows)
A fully charged tablet
Asus data cable
Stock firmware blob (from Asus's web site, make sure you get the right one)
_that's bootit.ko (unzipped and placed with fastboot.exe)
Downloads
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR TRANSFORMER TABLET
click me
_that's bootit.ko----click me
INSTRUCTIONS
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to the same folder as your fastboot.exe or if in linux to your home folder
Unzip the bootit.ko and place it wth the above blob file.
Let start with this command to make sure that your PC can see your table as an ADB device in recovery
Code:
adb devices
OUTPUT
Code:
[email protected] ~ $ adb devices
List of devices attached
015c7d7a445c260c recovery
Then lets push the bootit.ko to the root of the device like this
Code:
adb push bootit.ko /
OUTPUT
Code:
[email protected] ~ $ adb push bootit.ko /
673 KB/s (27690 bytes in 0.040s)
Then lets insmod this .ko file
Code:
adb shell insmod /bootit.ko
This should reboot the tablet into the bootloader menu, lets verifiy.
Once in the bootloader screen lets make sure your PC can see the device in fastboot.
Code:
fastboot devices
OUTPUT
Code:
[email protected] ~ $ fastboot devices
015c7d7a445c260c fastboot
So now its time to erase the misc & cache partitions, as that is most likely the partitions that is making it boot to recovery...
Code:
fastboot erase misc
OUTPUT
Code:
[email protected] ~ $ fastboot erase misc
erasing 'misc'...
OKAY [ 1.021s]
finished. total time: 1.021s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected] ~ $ fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.096s]
finished. total time: 2.096s
Once these two command run with OKAY as the OUTPUT .
It is time to make sure we can reboot into the bootloader with the hardware buttons
So from where you are at in the bootloader screen use the VOL DOWN & POWER buttons to boot the tab back into the bootloader screen ..
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
OUTPUT
Code:
[email protected]:~ > fastboot devices
015d2bbce2501405 fastboot
Code:
fastboot erase system
OUTPUT
Code:
[email protected]:~ > fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
OUTPUT
Code:
[email protected]:~ > fastboot erase recovery
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
OUTPUT
Code:
[email protected]:~ > fastboot -w
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it will either hangs on erasing 'cache'
Or it will give you an error, either way you will need to
reboot the tablet back into fastboot with the hardware buttons
Once that is done continue on the path
Code:
fastboot erase boot
OUTPUT
Code:
[email protected]:~ > fastboot erase boot
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
OUTPUT
Code:
[email protected]:~ > fastboot erase misc
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
OUTPUT
Code:
[email protected]:~ > fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0B05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
OUTPUT
Code:
[email protected]:~ > fastboot -i 0x0B05 reboot
rebooting...
finished. total time: 0.020s
Let it boot into stock ROM ....

Credits
@_that for his bootit.ko
TEAM CROMBi and TEAM ZOMBi-X @sbdags @hardslog

Troubleshooting
Here is some troubleshooting
Check out this thread for fasboot.exe, adb.exe and driver help ...CLICK ME

A message from _that
_that said:
Here is the original thread where the bootit module was tested for the first time -> http://forum.xda-developers.com/showthread.php?t=2291974
The problem was that the installed recovery was too old and incompatible with the bootloader and so could not access the eMMC at all. The bootloader command to boot to recovery is stored in the MSC partition (mmcblk0p3), and the recovery could not clear it. Since the bootloader checks the MSC partition before checking for volume-down, it is impossible to get to fastboot without some additional kick in the butt (aka "bootit.ko").
The correct bootit.ko file to use is the one in "bootit-bootloader.zip": http://forum.xda-developers.com/attachment.php?attachmentid=1985941&d=1369339132 - the older version turned out to be too weak. Note that this is a zipped kernel module, not a recovery-installable ZIP. You need to unzip it on your PC before adb push.
After making it to the bootloader menu and working fastboot, you can fastboot flash a current version of TWRP and install the custom ROM of your choice. No real need for the stock blob, unless you want to make sure you have the current bootloader and a known working ROM.
Here is another thread where bootit.ko didn't help, maybe it was really a hardware problem. But lots of good background info from me. -> http://forum.xda-developers.com/showthread.php?t=2437376
And here is another success story -> http://forum.xda-developers.com/showthread.php?p=47525770
Click to expand...
Click to collapse
Thx for all your help @_that

Great Guide: a happy Transformer Prime User you made of me!
Dear lj50036,
Thanks so much for your excellent guide. I went along with it all the way to the end and it just worked, splendid! You set up the scenario quite clearly and for those guys who are in the same situation this is a very handy guide.
Excellent piece of work!
My congratulations on your great work!
mitsublw

mitsublw said:
Dear lj50036,
Thanks so much for your excellent guide. I went along with it all the way to the end and it just worked, splendid! You set up the scenario quite clearly and for those guys who are in the same situation this is a very handy guide.
Excellent piece of work!
My congratulations on your great work!
mitsublw
Click to expand...
Click to collapse
I am glad to see you up and running ..... :good:
Thx Josh

Do I need a specific blob other than a US blob considering US is my area?

xerotix said:
Do I need a specific blob other than a US blob considering US is my area?
Click to expand...
Click to collapse
The tablet will tell you what the SKU is ....
When on the bootloader screen in the upper left is will tell you the SKU ...
Thx Josh

I just put together a Win 8 64 bit with a quad core i5...to the best of my knowledge I'm having trouble with it recognizing my tf300t. while it's physically connected on my front and/or rear usb ports, as I hear it recognized physically connecting, no visual signs of it connecting in my file explorer in twrp, prior recovery, and off after having all of the drivers and such installed to the best of my knowledge using your link as well...Suggestion?

xerotix said:
I just put together a Win 8 64 bit with a quad core i5...to the best of my knowledge I'm having trouble with it recognizing my tf300t. while it's physically connected on my front and/or rear usb ports, as I hear it recognized physically connecting, no visual signs of it connecting in my file explorer in twrp, prior recovery, and off after having all of the drivers and such installed to the best of my knowledge using your link as well...Suggestion?
Click to expand...
Click to collapse
Dont use windows 8 ..
That is all I can give you, never used it.
Not going to sit here and fill you with BS like I have all the answers.....
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh

lj50036 said:
Dont use windows 8 ..
That is all I can give you, never used it.
Not going to sit here and fill you with BS like I have all the answers.....
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
Click to expand...
Click to collapse
I'm trying to figure out how to install Mint on my computer after I partitioned my hard drive to give me the space to install it...I'm searching google for it but haven't run across anything as of yet.

xerotix said:
I'm trying to figure out how to install Mint on my computer after I partitioned my hard drive to give me the space to install it...I'm searching google for it but haven't run across anything as of yet.
Click to expand...
Click to collapse
Is Mint going to go on its own hdd or are you going to dual boot from a hdd with windows on it ?
Thx Josh

lj50036 said:
Is Mint going to go on its own hdd or are you going to dual boot from a hdd with windows on it ?
Thx Josh
Click to expand...
Click to collapse
Dual boot on 2 tb hdd

xerotix said:
Dual boot on 2 tb hdd
Click to expand...
Click to collapse
You're dual booting with windows, yes ?
http://itsfoss.com/guide-install-linux-mint-16-dual-boot-windows/
There is all kinds of info out there ...
Thx Josh

lj50036 said:
My solution would be to us some kind of a Linux OS .... I prefer Mint but @hardslog hates it .....
He will get a kick out of that ... LOL
Thx Josh
Click to expand...
Click to collapse
Lol, LIES. I don't hate MINT. I just like to give @sbdags a hard time when something goes wrong with it. Any popular Linux distro should work well, and if you don't want to install it on a hard drive you can always install it on a USB and run from that

Thank you. You learn something new everyday...lol. I'm about to go to Full Sail here in Orlando where I live for software development. I was told I will be learning a lot in conjunction with Software Development parallel to Android development(which they teach as well)...I'm loving it.

I have tried everything I can think of...turned safe boot off after going into BIOS and searching more in BIOS, nothing thus far...

I have vista on another hard drive...would it work on vista?

xerotix said:
I have vista on another hard drive...would it work on vista?
Click to expand...
Click to collapse
It may work under vista .....
Thx Josh

lj50036 said:
It may work under vista .....
Thx Josh
Click to expand...
Click to collapse
It's gonna be a PITA to install that hard drive on this computer as I built this computer because of that POS. I'm unsure but hopefully I can figure out a way to connect both hard drives and have some sort of dual boot to use this hard drive with my new processor as opposed to the AMG with 1 gb of ram in the previous one from 5+ years ago. I already gutted it cuz it's of no use to anyone other than parting out. I have windows 7 on an old laptop I don't use anymore but I'm unsure of how to use that hard drive as to whether I can connect that one to that of my new desktop in a way/shape/or form so to speak

bootloader

Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem

kataik95 said:
Hey guys i have an n8010. When samsung released the leak fw for the 8000 I installed it. It worked pretty well. A few months ago an official update came for the 8010 but im using the 8000 bootloader i cannot install it Is that any solution for recovering the old bootloader? I've tried a lot of thing to solve it but none of them was successful. I've tried this method: http://forum.xda-developers.com/galaxy-note-10-1/help/recovering-n8010-leaked-locked-n8000-t2802516 and a lot of custom roms but i always have a same crash after using it for about 2 days. It says System UIDs Inconsistent, UIDs on the system are inconsistent you need to wipe your data partition or your device will be unstable. And if i press "I'm felling lucky" every app crashes touchwiz ,android everything.
Please help me to solve my problem
Click to expand...
Click to collapse
I think your Stuck with the bootloader..
The issue about im feeling lucky thing... I think you have malware on your device... Never heard of or seen nothing like that

hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m

moonbutt74 said:
hi,
this is my backup of the jb bootloader for the n8013 [n801x]
http://d-h.st/users/moonbutt74/?fld_id=39849#files
cwm flashable
m
Click to expand...
Click to collapse
Thanks man i havent tried it yet but i hope it will help
Sent from my SM-G900F using XDA Free mobile app

Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico

FGM 11 said:
Hi, well I have the n8010 model.
and while you install the version of n8000 leak.
so my bootloader remained in n8000.
and then, after much, I put the rom gnabo v6.
and a few days ago, my note I do not step beyond the samsung logo, stayed stagnant.
try putting on the rom again, but not carrying anything.
I made full format from the recovery of the internal sdcard.
did wipes and try to flash the rom, but not!
I went back to install the 4.4 leak of n8000, but nothing.
and I get the error: failed mount / efs (invalid argument)
that I can do? please help.
sorry for my English, I'm from mexico
Click to expand...
Click to collapse
I tried everything but nothing helped. And now i have the same efs problem like you. I hope that somebody can help us

This worked for the galaxy tab 3 10.1
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m

partitions
moonbutt74 said:
okay,
a while back i helped a user with a similar problem. this was my approach HOWEVER, the following conditions
must be met first.
1 you are able to boot into recovery and maintain normal operation including adb root shell access
2 you are able to charge your tab from a powered off state, mostly to see if you charging animation shows.
that means your kernel is intact-ish
3 you can boot into odin mode.
assuming the partion layouts for your respective devices match the red highlighted sections of this output from parted.
Code:
[email protected]:/ # parted /dev/block/mmcblk0
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print all
print all
Model: MMC MAG2GA (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
[COLOR="Red"] 1 4194kB 8389kB 4194kB BOTA0
2 8389kB 12.6MB 4194kB BOTA1
3 12.6MB 33.6MB 21.0MB ext4 EFS
4 33.6MB 41.9MB 8389kB PARAM[/COLOR]
5 41.9MB 50.3MB 8389kB BOOT
6 50.3MB 58.7MB 8389kB RECOVERY
7 58.7MB 92.3MB 33.6MB RADIO
8 92.3MB 931MB 839MB ext4 CACHE
9 931MB 2399MB 1468MB ext4 SYSTEM
10 2399MB 2923MB 524MB ext4 HIDDEN
11 2923MB 2932MB 8389kB OTA
12 2932MB 15.8GB 12.8GB ext4 USERDATA
(parted)
AND provided you can get someone competent with access to the respective models to open a root shell
on device or through adb and run the following command,
Code:
[COLOR="Red"]dd if=/dev/block/mmcblk0 of=/sdcard/fix.img bs=1 count=35221668[/COLOR]
AND zip the output fix.img and post it, again for the respective devices.
THEN you can through adb,
adb push fix.img /sdcard/
or
adb push fix.img /sdcard
or
adb push fix.img /data/media/0/
or
adb push fix.img /data/media/0
you can then navigate TO the directory you pushed the image to and execute the following
dd if=fix.img of=/dev/block/mmcblk0
the above approach worked for me in helping another user with a like device.
you assume the same risk you took previously to achieve the state your device is in now.
NOTE- count=35221668 is a hair under the actual end of /efs . you may need to adjust through param and into boot maybe
half way , but then you can just reflash kernel or then do a proper odin flash of stock. the fix.img will NOT be odin flashable.
m
Click to expand...
Click to collapse
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png

Instructions Matter
kataik95 said:
Well this is how my partitions look like: http://kepfeltoltes.hu/view/140928/partitions2_www.kepfeltoltes.hu_.png
Click to expand...
Click to collapse
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m

moonbutt74 said:
K,
i must stress the need for you to follow instructions, hear me out, I am operating on the assumption that you are
an experienced android user.
1 the archive with the bootloader data i provided was a cwm flashable zip file. to attempt a flashing of that file itself
or the img files contained within in any other fashion has likely made your problem worse. i also stated as per the
name of the file that it is for the n8013. it is good to hear that you have made some progress however instructions
are important because,
2 though you have succeeded in using parted through adb you have provided the wrong information.
instead of
parted /dev/block/mmcblk0p8
please run
parted /dev/block/mmcblk0
then at the (parted) prompt running print all wil return the correct information.
I mean the above in the best way, as well to stress the importance of doing these things correctly
to avoid a true hard-bricking of your device. You will need to go hat in hand and request an experienced/competent
user/developer pull the needed data from their device as stated in my previous post.
it is likely that the data pulled from my device may work, but that your device afterwards will register as an n8013.
please re-execute parted through adb as instructed for the needed information and we can move foward from there.
m
Click to expand...
Click to collapse
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work

kataik95 said:
Thanks for all the help you gave me but I decided to take my tab to a service, they probably make it work
Click to expand...
Click to collapse
Sure, no problem. Hope everything works out. :good:
m

moonbutt74 said:
Sure, no problem. Hope everything works out. :good:
m
Click to expand...
Click to collapse
Imagine after 2 services where the could't fix I took to a 3rd. They could fix it so it works its on 4.0.4 in some kind of factory mode (strange). I can not quit from this mode and odin not works as well. In the recovery it says efs is invaild. What is that fw?

Restore fried partitions - Fastboot flash stock ROM via MiFlash takes forever

Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
EDIT: Finally, I managed to restore my phone. To save you from reading the whole thread, which is full with creative ideas to unbrick the phone you can jump to the last post. There I described my final solution and ruled out, what probably my mistake with the MiFlash Tool was.

Muenzi said:
Hi everyone,
I need some help and currently I am a bit desperate. I tried to flash my Poco X3 as I did already a couple of times, but this time it was unable to mount partitions in recovery and therefore I was not able to flash any ROM. That's why I thought it might be good to use the MIFlash tool and fastboot-flash the stock ROM, hoping the partitions will be fine again. While the progress bar in the tool is full and we reach around one hour flashing time, the process seems still not completed (says still "flashing")
Do you have any ideas what could be wrong?
My configuration is as follows:
Poco X3 NFC Global
Windows 10
MiFlash 2020.3.14.0
Stock ROM used: surya_global_images_V12.0.7.0.QJGMIXM_20201221.0000.00_10.0_global_20d93168ac.tgz
Best regards and thank you all for help.
Muenzi
Click to expand...
Click to collapse
Did you do anything before you noticed your partitions are fried?

jjgvv said:
Did you do anything before you noticed your partitions are fried?
Click to expand...
Click to collapse
Yes I installed OrangeFox as a recovery. From there on, everything get messed up.
If nescessary to know, the BL is unlocked of course. I backuped all data from the phone. So I do not need a safe way to get them back. I am happy when the phone can operate a reliable OS again.

https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.

jjgvv said:
https://github.com/phhusson/treble_experimentations/releases/download/v300.l/system-roar-arm64-aonly-vanilla.img.xz
Ok extract to .img and fastboot flash the above system image and send me the results to see how seriously your system partition is fried.
Click to expand...
Click to collapse
Thank you for your help. Can you tell me please to which partition this has to be flashed? And what will be the outout I can send you (probably a log file?).
So lets say commands instructions like
fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
would be really cool to avoid confussion and mistakes.
Anyway, it is 3 am here and I have to get up in around 4 hours. So I will leave and take a nap. Maybe I can ask you to wait for my reply? And again, thank you so much for your help.
Best regards
Stephan

yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img

Muenzi said:
And what will be the outout I can send you (probably a log file?).
Click to expand...
Click to collapse
I need What happens in the cmd window like:
Code:
Desktop-XCRXAJB > C:\platform tools >
fastboot flash system system-roar-arm64-aonly-vanilla.img
Reported max download size = 2580192068 bytes （ 2.7 GB）
sending 'system' （2070713691 bytes）
OKAY （1576 secs）
writing 'system' （2070713691 bytes）
FAILED （remote : failed to mount 'system' : system partition layout is 'null'）

jjgvv said:
yes yes fastboot flash system system-roar-arm64-aonly-vanilla.img
Click to expand...
Click to collapse
Thats the outout:
Code:
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/3 (786328 KB)...
OKAY [ 21.029s]
writing 'system' 1/3...
FAILED (remote: Partition not found)
finished. total time: 21.031s
So, I have to go now. See you in a couple of hours.

adb shell
parted /dev/block/mmcblk0
print

see you soon

jjgvv said:
adb shell
parted /dev/block/mmcblk0
print
Click to expand...
Click to collapse
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.

Muenzi said:
Too exciting too sleep. But I really have to. :-D
Thats why last question,
Code:
adb shell
in fastboot or in recovery as in fastboot the command tells me that no device/emulator was found.
Click to expand...
Click to collapse
recovery

jjgvv said:
recovery
Click to expand...
Click to collapse
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.

Muenzi said:
Code:
parted /dev/block/mmcblk0
/sbin/sh: parted: inaccessible or not found
Tab completion showed after mmcblk0:
Code:
parted /dev/block/mmcblk0
mmcblk0 mmcblk0p1
So it seems to be existing with one partition.
Click to expand...
Click to collapse
oh so probably Orangefox fried your other partitions

jjgvv said:
oh so probably Orangefox fried your other partitions
Click to expand...
Click to collapse
What happens when flash TWRP

jjgvv said:
What happens when flash TWRP
Click to expand...
Click to collapse
I already did. The problem persists. To clarify, all the last steps were already performed with TWRP as recovery. But the problem occurred first under TWRP.
Is there any chance to recreate the partition table?

maybe but complicated

Hi you may try boot from sd card
[HOW TO] BOOT FROM SD CARD [SUCCESSFULLY] on QMobile Z8 with BRICKED/DEAD eMMC
I'm a mechanical engineer, not an IT guy. I can fix machines, perhaps, but not bricked phones. So try anything at your own extreme risk. This is NOT a step by step guide. DEVICE: QMobile Z8, same as Wikio Ridge 4G, (MSM8916). Running Android...
forum.xda-developers.com

jjgvv said:
maybe but complicated
Click to expand...
Click to collapse
Okay if you have any idea, let me know.

or this https://forum.xda-developers.com/t/...dor-partition-for-pt-gsi-rom-mi3-mi4.3878995/
this is create vendor but should be possible to create all