Database Info

[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [06/24 CM12.1/TWRP 2.8.7.0]

[BOOTLOADER] 2nd-bootloader for Custom ROMs on KFireHD 7" [06/24 CM12.1/TWRP 2.8.7.0]
Introducing: Kindle Fire 2nd-bootloader + TWRP 2.8.x.x for the Kindle Fire HD 7
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
** THESE FILES WILL ONLY WORK ON A KINDLE FIRE HD 7 **
** WHEN MODDING THE KFIRE HD YOU SHOULD HAVE WORKING FASTBOOT DRIVERS/ACCESS ON YOUR PC. **
LOOKS LIKE NOT ALL FASTBOOT CABLES WILL AUTOMATICALLY PLACE YOU IN FASTBOOT MODE ON THE KINDLE FIRE HD 7. DOWNLOAD THE ANDROID SDK AND GO FROM THERE.
http://developer.android.com/sdk/index.html
Here's 1 website you can purchase a FASTBOOT adapter from (works with your normal USB cable)
http://shop.teamblackhat.info/Factory-Adapters-motadapt.htm
** I don't make any commission or fee from the sales of these devices, I just know they have them on stock most of the time and ship in a reasonable time frame unlike the Chinese variants found on ebay.
Q: How do I know if my fastboot works?
A: With the Kindle powered down, type the following command into a cmd/terminal window on your PC (should return with: < waiting for device> ):
fastboot -i 0x1949 getvar product
Then connect your fastboot cable to the Kindle and reboot. It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Tate-XXX-XX (something here)
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
** IF YOU HAVE QUESTIONS, RE-READ THROUGH THE THREAD FOR ANSWERS. WHEN YOU'RE ABSOLUTELY SURE NO ONE HAS ASKED YOUR QUESTION, GO AHEAD AND RE-READ THE THREAD AGAIN AND USE THE SEARCH FEATURE. THEN POST YOUR QUESTION IF YOU STILL CAN'T FIND THE ANSWER **
INSTRUCTIONS FOR INSTALLING A 2ND-BOOTLOADER TO LOAD CUSTOM KERNELS / ROMS / RECOVERY:
*** BE SURE YOU HAVE A GOOD CHARGE ON THE DEVICE ***
STEP 1. Backup your stock partitions to your own HD for later if you need disaster recovery:
Code:
adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/sdcard/boot0block.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot of=/sdcard/stock-boot.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery of=/sdcard/stock-recovery.img"
adb shell su -c "dd if=/dev/block/platform/omap/omap_hsmmc.1/by-name/system of=/sdcard/stock-system.img" # This will take a few minutes
adb pull /sdcard/boot0block.img
adb pull /sdcard/stock-boot.img
adb pull /sdcard/stock-recovery.img
adb pull /sdcard/stock-system.img # This will take a few minutes
Take those files and put them somewhere safe.
**** MAC USERS MAY NEED TO SPARSE THE FILES FOR RE-FLASHING TO THE DEVICE. I NEED A MAC USER TO PROBABLY WORK THROUGH THAT PROCESS AND POST BACKUP COPIES OF THE STOCK PARTITIONS FOR DISASTER RECOVERY ****
STEP 2: Download the files you will need to install 2nd-bootloader, TWRP and CM:
ON THE FOLLOWING DEV-HOST LINKS
USE THE BLUE "DOWNLOAD NOW" BUTTON
-- DO NOT INSTALL AN EXECUTABLE DOWNLOADER TO YOUR SYSTEM! --
I'LL LOOK FOR A BETTER HOST WHEN I GET MORE TIME.
Stack override file:
Mirror 1: Download "stack" from Dev-Host
[12/09] kfhd7-freedom-boot-7.4.6.img (USED ONLY THE FIRST TIME -- .zip files will have their own boot.img's from now on):
Mirror 1: Download "kfhd7-freedom-boot-7.4.6.img" from Dev-Host
md5sum: 1628fc4750d0d49cbce41ab616a9d732
[06/24] TWRP 2.8.7.0 recovery flash Image:
Mirror 1: Download TWRP from Dev-Host
CM-12.1 for the Kindle Fire HD 7 (choose the latest version from):
Mirror 1: Downloads CM
Google Apps from Android File Host:
https://www.androidfilehost.com/?w=files&flid=25361 (Use 5.1 version!)
Download the older 7.2.3 bootloader file and flash to your device via fastboot:
Mirror 1: Download bootloader from Dev-Host
md5sum bb029673d8f186db4dff6d38f4aa28cf
(You SHOULD check the md5sum before using fastboot -- downloads CAN be corrupted)
Place the CM-12.1 ROM and the gapps .zip on your device in the /sdcard area
STEP 3. Install the stack override in /system:
ADB commands entered while booted up into STOCK *rooted* Amazon Kindle OS -- May need to enable ADB debugging in Settings:
[2013-08-21] edited the location where stack is placed on device due to permissions changes
Code:
adb push stack /sdcard/
adb shell su -c "dd if=/sdcard/stack of=/dev/block/platform/omap/omap_hsmmc.1/by-name/system bs=6519488 seek=1"
STEP 4. Stop the auto recovery update script (this file may or may not be present):
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"
STEP 5:
[ With the device powered off: connect your FASTBOOT USB cable to the Kindle which should cause it to power on and enter "FASTBOOT" mode. Issue the following commands into your command/terminal window on your PC 1 at a time. ]
Code:
fastboot -i 0x1949 flash bootloader kfhd7-u-boot-prod-7.2.3.bin
fastboot -i 0x1949 flash boot kfhd7-freedom-boot-7.4.6.img
fastboot -i 0x1949 flash recovery kfhd7-twrp-2.8.7.0-recovery.img
fastboot -i 0x1949 reboot
*DONT RE-FLASH FREEDOM-BOOT.IMG LATER AFTER FLASHING CUSTOM ROMS -- IT'S FOR STOCK AMAZON OS ONLY / FIRST INSTALL ONLY*
** If everything was done correctly your Kindle will reboot and you will at first see the normal Kindle Fire ORANGE logo and then it will fade and come back as a BLUE logo. **
TO ENTER RECOVERY:
Press the left volume button (volume up) while the logo is still YELLOW and keep pressing until the logo turns BLUE. Wait a moment and you should enter recovery.
STEP 6:
CM-12.1 AND GAPPS INSTALLATION:
(OPTIONAL) Make a backup by selecting "Backup" and then slide your finger to the right on the "Swipe to Back Up"
Once complete use the pentagon "Home" icon in the lower left corner of the screen
Now, select "Wipe"
Swipe the "Swipe to Factory Reset"
Use the "Home" icon
Select "Install"
Browse to the location on your device where you saved the CM-12.1 / GAPPS .ZIP files
Select the CM12.1 ZIP file in the list by touching it, then confirm it says the name of the CM-12.1 .ZIP file on the next screen under "File to flash:"
Select "Add More Zips"
Select the GAPPS ZIP file in the list by touching it -- make sure it says the name of the .ZIP again under "File to flash:"
Swipe the "Swipe to Confirm Flash", and wait for it to finish.
If the screen is blank at any time you can hit the power button to "wake up" the device
Once the flash is done, you'll see a "Home" and "Reboot" buttons at the bottom of the screen
Select "Reboot"
CONGRATULATIONS YOU NOW HAVE THE ABILITY TO INSTALL CUSTOM KERNELS / RECOVERY AND ROMS.
FLASHING BACK TO STOCK:
** FIND THE FILES WE BACKED UP IN STEP #1: ** OR Follow this thread's instructions:
http://forum.xda-developers.com/showthread.php?t=1951254
**** MAC USERS MAY NEED TO SPARSE THE FILES FOR RE-FLASHING TO THE DEVICE. I NEED A MAC USER TO PROBABLY WORK THROUGH THAT PROCESS AND POST BACKUP COPIES OF THE STOCK PARTITIONS FOR DISASTER RECOVERY ****
Plug in your fastboot cable and reboot so that you see the fastboot screen. On your computer go into a prompt and change to the directory where your stock backups are and enter the following commands:
Code:
fastboot -i 0x1949 flash boot [B]stock-boot.img[/B]
fastboot -i 0x1949 flash recovery [B]stock-recovery.img[/B]
fastboot -i 0x1949 flash system [B]stock-system.img[/B] # This one will take a few minutes
fastboot -i 0x1949 reboot
THANKS TO:
fattire for finding the original bootloader exploit
verygreen for doing some initial work on the 2nd-bootloader and fixing bugs (and letting me copy some of his bootloader installation instructions)

Changelog: updated 2013-07-08
freedom boot.img (for use w/ stock Amazon OS + 2nd-bootloader):
[07/08] Updated w/ kernel from 7.4.3 release
Amazon OS .zip:
[07/08] Rebuilt on version 7.4.3 from Amazon
TeamWin Recovery (TWRP) 2.6.0.0
[*][07/08] USB Vendor ID / Product ID in recovery now matches stock Amazon OS
[07/08] Fixed long pause before recovery entry
[07/08] Based on 7.4.3 stock kernel
[07/08] Fixed recovery bootloop issue
[07/08] Screen timeout feature currently disabled due to screen blanking bug
[07/08] TWRP 2.6.0.0 update
[07/08] Added "EFS" partition backup option. Normally, don't need to make too many backups of this, but having a backup will enable you to recover HDMI keys, and some other data.

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
Can I use install this and still use stock os?
Sent from my KFTT using XDA Premium HD app

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
Shawnsch said:
Can I use install this and still use stock os?
Sent from my KFTT using XDA Premium HD app
Click to expand...
Click to collapse
Yes, that's how the initial install is setup.
Sent from my DROID RAZR HD using Tapatalk 2

For those using this, for some reason that moment waiting for the device to boot into recovery can seem like eternity. It does take a bit to finally enter recovery but it will eventually do so. You'll see the BLUE logo for a little while so just be patient.

Hashcode said:
Yes, that's how the initial install is setup.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
hashcode, what are the methods to make a kernel ?
and the startup time increase?
your work is increadible, you dont have a 7" but you made this.

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
I am looking into a loaner device so that I can setup the kernel for the HD7. So while this new bootloader may seem useless at the moment, that may change.
I am still very busy, of course so it may take time.
Sent from my DROID RAZR HD using Tapatalk 2

Hashcode said:
I am looking into a loaner device so that I can setup the kernel for the HD7. So while this new bootloader may seem useless at the moment, that may change.
I am still very busy, of course so it may take time.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
start up time of device xD. you are the best rom kernel here. thanks for your beautiful job.
if you need any help or something i can help you with all

I added a missing step where the auto recovery updater runs in the OS on stock boot:
To disable this auto recovery installer do this via adb:
Code:
adb shell su -c "mount -o remount,rw ext4 /system"
adb shell su -c "mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak"
adb shell su -c "mount -o remount,ro ext4 /system"

Safestrap will it remove it

Awesome! I Had 1 small glitch.....
Thanks!! This is awesome. I've been trying to get my Kindle backed up since I got it. I had it rooted the next day and have been toying with it being extra careful not to go too far. Now the fun begins.
One thing....I had to rename kfhd7-twrp-2.3.3.0-recovery.img to get it to flash. I just renamed it to recovery.img
In case anyone else runs into this error
Code:
C:\>fastboot -i 0x1949 flash boot kfhd7-freedom-boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.794s]
writing 'boot'...
OKAY [ 0.681s]
finished. total time: 3.475s
C:\>fastboot -i 0x1949 flash recovery kdh7-twrp-2.3.3.0-recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'kdh7-twrp-2.3.3.0-recovery.img': Unknown error
C:\>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8145 KB)...
OKAY [ 2.804s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 3.475s
C:\>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.010s

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
I cant wait til i get a factory cable thank you to whoever participated in getting this going.
Sent from my KFTT using Tapatalk HD

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
etom: thank you for bringing this up. i fixed the typo.
Sent from my DROID RAZR HD using Tapatalk 2

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
etom said:
Thanks!! This is awesome. I've been trying to get my Kindle backed up since I got it. I had it rooted the next day and have been toying with it being extra careful not to go too far. Now the fun begins.
One thing....I had to rename kfhd7-twrp-2.3.3.0-recovery.img to get it to flash. I just renamed it to recovery.img
In case anyone else runs into this error
Code:
C:\>fastboot -i 0x1949 flash boot kfhd7-freedom-boot.img
target reported max download size of 1006632960 bytes
sending 'boot' (8145 KB)...
OKAY [ 2.794s]
writing 'boot'...
OKAY [ 0.681s]
finished. total time: 3.475s
C:\>fastboot -i 0x1949 flash recovery kdh7-twrp-2.3.3.0-recovery.img
target reported max download size of 1006632960 bytes
error: cannot load 'kdh7-twrp-2.3.3.0-recovery.img': Unknown error
C:\>fastboot -i 0x1949 flash recovery recovery.img
target reported max download size of 1006632960 bytes
sending 'recovery' (8145 KB)...
OKAY [ 2.804s]
writing 'recovery'...
OKAY [ 0.671s]
finished. total time: 3.475s
C:\>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.010s
Click to expand...
Click to collapse
Thank you i soft bricked my kindle trying flash recovery. Once i changed to recovery.img it worked great
Sent from my KFTT using xda app-developers app

worked like a charm thanks for all your hard work hashcode. so with this i can now flash flashable zips right?

Hashcode said:
I am looking into a loaner device so that I can setup the kernel for the HD7. So while this new bootloader may seem useless at the moment, that may change.
I am still very busy, of course so it may take time.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
I'm so happy to hear that you finally decided to work on kfhd 7 too, doesn't matter how long it takes, it's good to know we'll get it after all.
Thanks

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
Hashcode said:
etom: thank you for bringing this up. i fixed the typo.
Sent from my DROID RAZR HD using Tapatalk 2
Click to expand...
Click to collapse
Can i install team win recovery only? I want to flash some files only for now
Sent From My Super Modded KFHD

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
awesome! guess I gotta go get the kfhd from my dad n do some testing. great news for the community. on the old kf1 it all started with a bootloader. the rest is sure to follow!
Sent from my Nexus 4 using xda premium

kindle
i managed to flash the recovery fine in fastboot but now i am stuck in a bootloop and unable to run the stock os is this normal or have i done somthing wrong
Rob:good:
EDIT: okie so i tried from a clean fresh system using the restore images, i have managed to install the recovery bootloader no problem and i can access it, but if i leave the kindle and want to boot stock it goes orange and the texts flashes like normal and just when you think its going to boot it reboots and does the same thing over and over and over only way to get it to boot is wacking in the fastboot usb and then flashing the stock boot.img i also tried flashing revs beta rom and in twrp it always says error status 7 dunno if that is becasue its not the finished thing or not i am bit stuck now

Re: [BOOTLOADER] Install 2nd-bootloader for Custom ROMs on KFireHD 7"
try wiping data/cache? (factory reset)
Sent from my DROID RAZR HD using Tapatalk 2

Requesting assisstance with semi-brick issue.

Hello everyone,
I have unlocked my ASUS TF700T and then attempted to TWRP and a custom ROM. Once I did this, I began having issues. It wouldn't boot. I couldn't restore from TWRP backup. I can't seem to write to the system partition for some reason via fastboot but I seem to be able to do this just fine when in CWM or TWRP. Can anyone suggest what I may try from here? I can only get into recovery via VOL DOWN when booting and then selecting the wipe option. Right now I have two major issues. One is that for the life of me, I have never been able to get fastboot to show the actual serial of the device. It has always shown a single question mark. I have gone as far as building a Linux mint box just to get ADP and FASTBOOT drivers to install correctly on a 32-bit machine with USB 2.0. No luck, save result. My second issue is that I am unable to write to the system partition via fastboot. It gives me a remote () error message on fastboot and a could not process the command error in red on my tablet. I will have the exact error message for you shortly but right now I just wanted to get this posted. Any suggestions?
I can't flash the stock blob via fastboot and I can't seem to install a custom ROM via TWRP or CWM. Please advise.
I suspect me not being able to use ADB is my biggest problem. I can't see a serial number when I use fastboot devices. I have tried endlessly to get this resolved and I can't get it to change, AT ALL. I have installed google drivers, 32-bit fresh Linux OS, and plenty of utilities to auto install. No luck. If anyone can help with this, I'd appreciate it.
Here are my issues in a nutshell.
1.) I am unable to boot into recovery directly. I have to go into fastboot and select wipe, it then reboots and starts up in the recovery kernel. TWRP simply executes a command and then restarts and CWM actually boots and allows me to use it.
2.) No matter what I've tried, I have not been able to get the serial number to come up via fastboot. It simply shows a single questionmark. I have tried many solutions for this, but nothing changes.
3.) I am not sure but I believe the bootloader may be the problem. I can currently use fastboot but adb does not recognize the device.
Any assistance would be greatly appreciated. Thank you! I have tried different version of TWRP and clockwork mod but all seem to have the same result. I also attempted to install another custom rom just for good measure and CWM states that
-Tony

Boy oh boy! Mate, your post is one of the most confusing (and confused) posts I have read in a long time. I think you need to go back to the drawing board, forget everything you think you know and start fresh.
Let's clear some of it up:
1) CWM is a recovery (ClockWorkMod), I think you mean your rom is CM (CyanogenMod)
2) When you boot with Volume Down and Power you are booting into the bootloader, you see the bootloader menu and the tablet is in fastboot mode. The bootloader menu consists of 3 icons (if you are on a 4.2 bootloader):
RCK (recovery),
Android (system),
Wipe Data (stay away - it's a small miracle that you are not hard bricked already if you used this)
Are you saying you don't have those three in the BL menu????
RCK should be flashing and pushing Volume Up should boot you into recovery. There is no way to boot directly into it unless your rom has a modified restart menu.
3) adb and fastboot are two different protocols to connect PC and tablet. You use adb when Android is running, you use fastboot when the tablet is in fastboot mode.
Don't know what you tried to get the correct drivers working, but you probably have to go back to square 1 here too. If you use Windows check in Device Manager if your tablet is recognized at all:
Open Device Manager, boot the tablet int the bootloader and connect it via original USB cable to the PC. Do you see any change in Device Manager?
You left out the most important bits:
What bootloader version are you on?
Which version of TWRP?
How did you install TWRP if you don't have fastboot working?
What CM version are you running?

Thanks for the reply. I'll try and be more concise...
Hello,
First of all, I'd like to say thank you. I am all over the place. I will attempt to be more detailed and concise with my wording. Here are my responses below:
berndblb said:
Boy oh boy! Mate, your post is one of the most confusing (and confused) posts I have read in a long time. I think you need to go back to the drawing board, forget everything you think you know and start fresh.
Let's clear some of it up:
1) CWM is a recovery (ClockWorkMod), I think you mean your rom is CM (CyanogenMod)
Click to expand...
Click to collapse
I am familiar with the difference. I have not used nor flashed CyanogenMod. I have indeed installed CWM on recovery and can still do so. I just can't boot into recovery without using the dreded WIPE option on my bootloader. Once I use this, it restarts in CWM and I can use it (still fails to install anything on system though.)
berndblb said:
2) When you boot with Volume Down and Power you are booting into the bootloader, you see the bootloader menu and the tablet is in fastboot mode. The bootloader menu consists of 3 icons (if you are on a 4.2 bootloader):
RCK (recovery),
Android (system),
Wipe Data (stay away - it's a small miracle that you are not hard bricked already if you used this)
Click to expand...
Click to collapse
I have 2 options for my bootloader when I boot into it, fastboot(USB Icon) and wipe (I think we all know this one.) That's it. This is part of the reason why I can't get to recovery mode without using the WIPE option. (I stayed away from the wipe optoin for weeks until I was convince there was nothing else to try. Once I tried this, I was able to boot into recover with CWM or TWRP. TWRP however ONLY runs some sort of script and then reboots again. CWM allows me to use it. Hope this makes sense. Please let me know if I should clarify further.
berndblb said:
Are you saying you don't have those three in the BL menu????
RCK should be flashing and pushing Volume Up should boot you into recovery. There is no way to boot directly into it unless your rom has a modified restart menu.
Click to expand...
Click to collapse
I do not. Since I first installed TWRP, ran a TWRP backup and installed the custom 4.4.2 (I believe) rom I have not seen any other options.
berndblb said:
3) adb and fastboot are two different protocols to connect PC and tablet. You use adb when Android is running, you use fastboot when the tablet is in fastboot mode.
Don't know what you tried to get the correct drivers working, but you probably have to go back to square 1 here too. If you use Windows check in Device Manager if your tablet is recognized at all:
Open Device Manager, boot the tablet int the bootloader and connect it via original USB cable to the PC. Do you see any change in Device Manager?
Click to expand...
Click to collapse
I have gone over multiple times but I am willing to start again. I show ASUS Android Device in Device Manager for Windows 8.1 64-bit. (I have tried flashing many times on Windows 7 32-bit and Linux 32-bit both on USB 2.0. No luck, same issues, same results.
berndblb said:
You left out the most important bits:
What bootloader version are you on?
Which version of TWRP?
How did you install TWRP if you don't have fastboot working?
What CM version are you running?
Click to expand...
Click to collapse
I have no clue how to check the bootloader version without getting into Android. My bootloader doesn't seem to show it on the upper left hand side. Do you know how I can get it?
I have tried TWRP 3.2.1.0, TWRP 2.6.3.2, CWM 6.0.4.7 and Phil's CWM based recovery for the TF700. So far, none have been able to flash a custom ROM again nor the stock rom when I use recovery GUI for them. Please advise.
Also, it seems I am able to write to any partition with fastboot except for system. When I write to the system partition my tablet shows red text on the screen that states "the command flash:system failed 0x170003 or something similar. Fastboot shows a failed: (remote() error after trying to write to the partition. Someone told me my boot loader was the problem, but I have no idea how to change it without using the 'staging' or 'flash system commands.'
I'm not sure if this matters but I thought I'd post it. When I run fastboot -w it fails saying that the file system is not supported. When I run fastboot erase userdata or cache. It seems to work without any issues. Here is a sample of the output I get:
Code:
c:\adb>fastboot erase userdata
erasing 'userdata'...
OKAY [ 10.093s]
finished. total time: 10.093s
c:\adb>erase cache
Could Not Find c:\adb\cache
c:\adb>fastboot erase cache
erasing 'cache'...
OKAY [ 1.980s]
finished. total time: 1.980s
c:\adb>fastboot -w
erasing 'userdata'...
OKAY [ 10.031s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
erasing 'cache'...
OKAY [ 1.972s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
finished. total time: 12.006s
c:\adb>
When I try to use fastboot to flash the stock firmware using the staging command, I get this on my command prompt:
Code:
c:\adb>fastboot -w flash staging blob
sending 'staging' (800927 KB)...
OKAY [139.757s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 140.900s
c:\adb>
on my tablet it reads in red text failed to process command flash:staging error 0x170003. I have to do a cold boot to get it back up to fastboot mode.
-Tony

qzmicro said:
Hello,
When I try to use fastboot to flash the stock firmware using the staging command, I get this on my command prompt:
Code:
c:\adb>fastboot -w flash staging blob
sending 'staging' (800927 KB)...
OKAY [139.757s]
writing 'staging'...
FAILED (remote: ()
finished. total time: 140.900s
c:\adb>
on my tablet it reads in red text failed to process command flash:staging error 0x170003. I have to do a cold boot to get it back up to fastboot mode.
-Tony
Click to expand...
Click to collapse
Tony try this instead:
Code:
fastboot -i 0x0B05 flash system blob

I have tried it with -i 0x0B05 but it never has different results
sbdags said:
Tony try this instead:
Code:
fastboot -i 0x0B05 flash system blob
Click to expand...
Click to collapse
Exact same results:
Code:
c:\adb>fastboot -i 0x0B05 flash system blob
sending 'system' (800927 KB)...
OKAY [141.843s]
writing 'system'...
FAILED (remote: ()
finished. total time: 143.016s
c:\adb>
Thanks for the advise though.
-Tony

qzmicro said:
I have 2 options for my bootloader when I boot into it, fastboot(USB Icon) and wipe (I think we all know this one.) That's it.
I have no clue how to check the bootloader version without getting into Android. My bootloader doesn't seem to show it on the upper left hand side. Do you know how I can get it?
Click to expand...
Click to collapse
What does your bootloader show? Can you post a photo?
qzmicro said:
I have tried TWRP 3.2.1.0, TWRP 2.6.3.2, CWM 6.0.4.7 and Phil's CWM based recovery for the TF700. So far, none have been able to flash a custom ROM again nor the stock rom when I use recovery GUI for them.
Click to expand...
Click to collapse
So you can still flash different recoveries via fastboot and enter them from the bootloader. That means you should also be able to use "adb shell" to connect to your recovery (when it is running). What does the recovery do when you try to flash a ROM?
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.

Tony - consider yourself lucky since you caught the attention of two of the best people in this business. Do try to get the info _that was asking for.
I am just trying to clarify things:
Do you remember what stock rom you had before you started this adventure?
It sounds as if you were on pre-JB 4.2 stock rom, then flashed some TWRP version and then a KitKat rom?
If you can flash recoveries, you do have fastboot access to the tablet.
@_that, @sbdags Would it be an option for Tony to flash a CWM recovery that "let him use it" and try to flash sbdags' bootloader/TWRP package?
Tony - don't do anything before you get their advice.

OS
Tony I see that your using a windows PC.. I would highly recommend a Linux Mint OS... There are to many bugs in windows when you are working with low level Android/SoC platforms .... Im not going to say it will fix your issues, but I have seen it do just that for lots of users.... Just let me know if this sound like something for you, when and if your ready, the community with be here to help you out....As always thx lj

I am getting my Linux mint 32-bit OS on my laptop with USB 2.0... again.
Hi guys,
I thank you deeply for your time. I have learned so much trying to un-brick this thing, and yet have had no results. I will be putting together my mint box in just an hour or so and then testing/trying your suggestions. Please check back in an hour or two. Cheers.
-Tony

Here is what my bootloader looks like.
_that said:
What does your bootloader show? Can you post a photo?
Click to expand...
Click to collapse
I have attached the screenshot below.
_that said:
So you can still flash different recoveries via fastboot and enter them from the bootloader. That means you should also be able to use "adb shell" to connect to your recovery (when it is running). What does the recovery do when you try to flash a ROM?
Click to expand...
Click to collapse
It usually fails when it tries to write to the system partition. Please refer to the posts above. It tends to show the FAILED (Remote() error after the write command. My tablet also shows an error saying it could not process the command.
_that said:
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Click to expand...
Click to collapse
Giving it a try now, I'll let you known what happens.
-Tony

I do not recall. At the time I knew, but not anymore.
berndblb said:
Tony - consider yourself lucky since you caught the attention of two of the best people in this business. Do try to get the info _that was asking for.
I am just trying to clarify things:
Do you remember what stock rom you had before you started this adventure?
It sounds as if you were on pre-JB 4.2 stock rom, then flashed some TWRP version and then a KitKat rom?
If you can flash recoveries, you do have fastboot access to the tablet.
@_that, @sbdags Would it be an option for Tony to flash a CWM recovery that "let him use it" and try to flash sbdags' bootloader/TWRP package?
Tony - don't do anything before you get their advice.
Click to expand...
Click to collapse
I do not recall the stock ROM but I DO KNOW I updated to the latest firmware right after I opened it (Big mistake I know... now.) So, I had no choice but to factory unlcok it with the ASUS TOOL. This was for X-Mas two months ago, so I should be the latest I'd immagine.
I did indeed install a kit kat rom on my first attempt and someone told me I forgot to put the proper bootloader prior and that is why I bricked it. So, I think you are dead on about that but can't confirm.
I do indeed... only problem is that I always get a damn ? for my serial number. I do not believe it has ever shown anything but.... though I didn't check until after I had this problem. I do not recall checking prior to using TWRP to install the kit kat rom zip files.
I will wait. i am very greatful to have help, especially from the top dawgs. xP Cheers!
-Tony

I'm on mint 32-bit OS.
lj50036 said:
Tony I see that your using a windows PC.. I would highly recommend a Linux Mint OS... There are to many bugs in windows when you are working with low level Android/SoC platforms .... Im not going to say it will fix your issues, but I have seen it do just that for lots of users.... Just let me know if this sound like something for you, when and if your ready, the community with be here to help you out....As always thx lj
Click to expand...
Click to collapse
I'm on it. I installed mint on my laptop and am using a USB 2.0 interface. I am willing and able to try whatever you might suggest. Cheers.
-Tony

I get a permissions error when using adb shell in CWM recovery...
_that said:
If adb shell to your recovery works, exit it again and run these commands to assess your situation:
adb shell ls -l /dev/block > devblock.txt
adb shell dmesg > dmesg.txt
adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
and post the resulting files.
Click to expand...
Click to collapse
After the first command I received:
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
This is the error I get when running the first command you asked for _that. Please advise, thank you! Is this something we can fix? Thanks.
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
Tonys-Mint antonio # adb shell dmesg > dmesg.txt
error: insufficient permissions for device
Tonys-Mint antonio # adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
error: insufficient permissions for device
Tonys-Mint antonio #
They all basically told me I have no permissions to my device. Any thoughts? If anyone can/wants to assist outside these forums, please just let me know. I can't offer to pay but I can offer a free pizza at your house no matter where you live! LOL. Cheers fellas!
-Tony

qzmicro said:
I do not recall the stock ROM but I DO KNOW I updated to the latest firmware right after I opened it
Click to expand...
Click to collapse
Your photos show a 9.4.5.x bootloader (and I'm 100% sure about this), which is strange because normally the bootloader is updated together with the stock firmware - so if you updated to the latest firmware, you should also have the latest bootloader (10.6.1.14.x).
qzmicro said:
After the first command I received:
Code:
Tonys-Mint antonio # adb shell ls -l /dev/block > devblock.txt
error: insufficient permissions for device
This is the error I get when running the first command you asked for _that. Please advise, thank you! Is this something we can fix? Thanks.
Click to expand...
Click to collapse
What did the tablet screen show while you ran these commands? The recovery's menu? Which recovery (and version) do you currently have installed?

_that said:
Your photos show a 9.4.5.x bootloader (and I'm 100% sure about this), which is strange because normally the bootloader is updated together with the stock firmware - so if you updated to the latest firmware, you should also have the latest bootloader (10.6.1.14.x).
What did the tablet screen show while you ran these commands? The recovery's menu? Which recovery (and version) do you currently have installed?
Click to expand...
Click to collapse
It just sits there on the main screen as if nothing has happened. Here is a screenie...
-Tony

qzmicro said:
It just sits there on the main screen as if nothing has happened. Here is a screenie...
Click to expand...
Click to collapse
hmm... ok. Try running these commands:
Code:
adb kill-server
adb devices
and post the output.

For the first time EVER, I see the serial number!
_that said:
hmm... ok. Try running these commands:
Code:
adb kill-server
adb devices
and post the output.
Click to expand...
Click to collapse
Here is the output:
Code:
Tonys-Mint antonio # adb kill-server
Tonys-Mint antonio # adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d2a50692c0a08 recovery
Tonys-Mint antonio #
Please note that this is the first time the device has EVER shown it's serial number since this all started. Usually it just shows a single question mark. Good sign?! Please advise.
-Tony :fingers-crossed:

qzmicro said:
Here is the output:
Code:
Tonys-Mint antonio # adb kill-server
Tonys-Mint antonio # adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
015d2a50692c0a08 recovery
Tonys-Mint antonio #
Click to expand...
Click to collapse
That looks good so far. Try
Code:
adb shell
and see if you get a shell prompt from the tablet. If you do, type "exit" to get out again, then run the 3 commands I posted earlier.

_that said:
That looks good so far. Try
Code:
adb shell
and see if you get a shell prompt from the tablet. If you do, type "exit" to get out again, then run the 3 commands I posted earlier.
Click to expand...
Click to collapse
Hello, this is what I get...
Code:
Tonys-Mint antonio # adb shell
~ # adb shell ls -l /dev/block > devblock.txt
/sbin/sh: adb: not found
~ # adb shell dmesg > dmesg.txt
/sbin/sh: adb: not found
~ # adb shell hexdump -C /dev/block/mmcblk0p3 -n 64 > mmcblk0p3.txt
/sbin/sh: adb: not found
~ #
I am getting excited, I had not made any leway in over 4 weeks. Those commands seem to have failed though. I kindly await your response. Cheers.
-Tony :cyclops:

qzmicro said:
I am getting excited, I had not made any leway in over 4 weeks. Those commands seem to have failed though. I kindly await your response. Cheers.
Click to expand...
Click to collapse
You forgot to type "exit". But adb shell is working now, that is good. Type "exit" now, then run the 3 commands again, then post the 3 resulting files.

[Q] TF300T TWRP bootloop. Return to stock?

Any help would be greatly appreciated. I recently flashed the new TRWP using fastboot. Went fine. I then tried to wipe and flash the newest version of KatKiss. I thought it also went fine but after reboot, it bootloops TWRP. I can tell the tablet to boot Android, but it just hangs. Then when I try to boot back into TWRP, it starts the bootloop all over again. Here is what it's doing during bootloop.
Running OpenRecoveryScript
E:Could not mount /data and unable to find crypto footer.
E:Unable to mount '/data'
E:Unable to recreate /data/media folder.
Updating partition details...
E:Unable to mount '/data'
...done
E:Unable to mount storage.
E:Unable to mount /data/media during GUI startup.
Full SELinux support is present.
E:Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
Processing AOSP recovery commands...
E:Unable to mount '/data'
-- Wiping DATA Partition...
Formatting Cache using make_ext4fs function.
After about 1 minute it will follow with...
E:Unable to mount '/data'
-- Data Partition Wipe Complete!
Done processing script file
It will then reboot within 3 seconds after displaying the last line, and begin it all over again.
I'm hoping someone can tell me what options I have at this point. Would I be able to return to stock using fastboot and ASUS's blob from their website? Again, any help is greatly appreciated!

Solved.
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.

Recreate the partition
anim0sity said:
I had already figured on buying a new tablet regardless, so I figured I'd go ahead and try to recover using fastboot. It did work. I noticed this post had a few views, and on the chance there were other people having the same issue, I'll post how I did it. I recommend using Windows 7 for this.
Download the appropriate firmware from ASUS's website. (WW, US, CN, JP etc...) Unzip the file twice until you have the META-INF folder and blob file. I placed both of these into a folder named "TF300t" directly on the C drive.
Install your device drivers, I used the Google SDK drivers.
Boot into fastboot.
Run these commands...
fastboot erase system
fastboot erase recovery
fastboot erase userdata
fastboot erase boot
fastboot erase misc
fastboot erase cache
fastboot -i 0x0B05 flash system c:\TF300t\blob (Again, this is where I saved my blob file.)
You should see something along these lines, when flashing your system...
C:\>fastboot -i 0x0B05 flash system c:\TF300t\blob
erasing 'system'...
OKAY [ 1.665s]
sending 'system' (800931 KB)...
OKAY [142.128s]
writing 'system'...
OKAY [155.462s]
finished. total time: 299.255s
When it's finished, run the last command...
fastboot -i 0x0B05 reboot
From this point, you should be booted back into stock.
Click to expand...
Click to collapse
anim0sity
What happened if you dont have the blob???
I had a tab, i complete erase all the partition and i cannot install any app, always had error 963
How i can recreate all the partition of my tablet?
It running android 5 lollipop
Regards,

Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app

anim0sity said:
Shouldn't be any reason you don't have the blob file. You can download it straight from ASUS's website. When you download it, it comes in a zip file. You have to extract it twice. So unzip the original zip file downloaded, then unzip the file you get from unzipping the original. From there, you should have the blob file needed to flash your tablet back to stock using fast boot / sdk tools.
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app
Click to expand...
Click to collapse
Hi Anim0sity
I downloaded the package and starting doit the process
H:\android-sdk\platform-tools>fastboot devices
015d15b4fc481208 fastboot
H:\android-sdk\platform-tools>fastboot erase system
_
Now is hanging here what i can do it??
Thanks

successful
Hi
After many tries and plug the usb cable in the back of my tower i successful install the firmware
Regards,

HI to rstore to stock using twrp, is it as simple as downloading the file to the tablet, unziping once then flashing the resulting file, or is it a bit more difficult than that?

Bootloop and can't access to TWRP

Hello !
Well, after long research and testing some solutions, I create this post because I'm stuck at one point.
So, after a wipe in the fasboot mode, my TF700 get stuck into a bootloop with no access to recovery (The more I can have is 5 second with the TWRP splashscreen before rebooting). The ROM that was installed on my tablet is Cromi-kk.
I followed this help thread : http://forum.xda-developers.com/transformer-tf300t/help/guide-t2854495 and I'm stuck at the last point
Code:
fastboot -i 0x0B05 flash system boot.blob
Here is what it said on my computer :
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system boot.blob
erasing 'system'...
OKAY [ 2.355s]
sending 'system' (800927 KB)...
but nothing is moving on the computer, and the tablet is still displaying the fastboot screen...
So I really don't know what to do now, I hope one of you can have a solution
Thank you in advance !

Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....

I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...

Maybe you can try the BUSTER99 way to access your bootloader.
http://forum.xda-developers.com/showthread.php?t=2179759&page=6
This was ones the sollution for my TF700T.
Good luck.
Scenic-3

nhibel said:
I don't think it's because of that. On the help thread it is said to rename the blob file into boot.blob, what I've did ^^
I tried again with renaming the file to blob, but it's the same, nothing is happening :/
Code:
[email protected]:~$ sudo fastboot -i 0x0B05 flash system blob
[sudo] Mot de passe de camille*:
erasing 'system'...
OKAY [ 2.431s]
sending 'system' (800927 KB)...
Click to expand...
Click to collapse
Show me a screenshot of your fastboot folder with "show extensions" enabled and make sure the blob is not named blob.blob.
I probably would start from scratch: Delete all blobs from the fastboot directory, extract the blob from Asus firmware, drag it "as is" into fastboot directory and use the fastboot flash system blob command

Here is some good news !
At first, I was trying to flash the blob from a Linux computer, but it wasn't working. So I tried again from another computer, which running on Windows 10. Again, it didn't work, exactly the same than on the Linux computer.
Finally, I tried something else. When I was looking for solutions at the beggining of my problem, I've dowloaded a twrp.blob, but I was unable to flash it at this time. I just tried again, and thank of the help of the help thread, I finally succeeded to flash TWRP (I had to try 2 times before the flash succeeded), and I should be able now to flash a rom !
Well, I lost everything that was on my device, but it works !
Thank you so much for spending some time to help me !

berndblb said:
Heck! I cannot believe this went undetected for so long!!! @lj50036
Hey Josh, have a look at this and make the edit! LMAO
@nhibel: Assuming you are trying to flash the stock blob in fastboot and you extracted the stock rom zip twice and put the file called just "blob" into your fastboot folder, the command to flash the stock blob is
Code:
fastboot -i 0x0B05 flash system blob
Nothing is happening because fastboot cannot find a file named boot.blob. Which makes sense since it does not exist. Unless you unpacked the blob.....
Click to expand...
Click to collapse
I am confused ??
Thx Josh

So was I. Never mind. Didn't realise you instructed to rename the blob... @[email protected]
Sent from my K00C using Tapatalk

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