Database Info

[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

@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...

LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
Fixed let me know if you see anymore ..
Thx @LetMeKnow

LetMeKnow said:
@lj50036
A typo on your very first command: adb device?
Edit: What would you recommend if the userdata is corrupted and have only fastboot/adb? fastboot format data-partition? Thanks...
Click to expand...
Click to collapse
I am going to get to this once you have fastboot back and you can boot with hardware buttons then its just like @Buster99's
guide but there is one very important command that he leaves out ..
I will post the rest of the guide after bit ...
Thx Josh

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

_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 _that I did update the OP with the correct bootit.ko ...

lj50036 said:
Thx _that I did update the OP with the correct bootit.ko ...
Click to expand...
Click to collapse
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...

I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..

lvrijn said:
I tried to follow this but i get this output:
After pushing bootit.ko to the root and insmod, the transformer reboots directly in the bootloader.
When try fastboot devices, nothing happens just the next line to fill in a command.
Also, when trying then to fastboot erase misc, it hangs with 'waiting for devices'..
Click to expand...
Click to collapse
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.

berndblb said:
Did you have a working fastboot driver on your PC before you got into this pickle?
Give us a detailed description on why you tried this procedure.
Click to expand...
Click to collapse
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !

lvrijn said:
Thanks for the advice.
It was not the driver, if was my fastboot and adb .exe, i think an old version?
I now downloaded from here http://forum.xda-developers.com/showthread.php?t=2588979
And these are working!
So if someone ever have problems command doesn't recognize fastboot commands, its not always the driver! It can also be the fastboot.exe
This transformer is working again !
Click to expand...
Click to collapse
Great to see you up and running...:good:
I did add a Troubleshooting post number 3
The Josh

berndblb said:
Great stuff! Thanks for this thread Josh!
Now , if I understand this correctly, the insmod command injects a command into the kernel to boot straight to the bootloader before checking misc to break that 'forced reboot to recovery' cycle.
Kinda correct?
In another thread @_that stated once that
Code:
fastboot getvar all
does not return misc as a supported partiton and that
Code:
fastboot erase misc
only "theoretically" erases misc partition. Is that confirmed now?
You guys are great! So much fun to learn this...
Click to expand...
Click to collapse
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
The bootit.ko module comes from the source of the kernel code..
Also the /misc partition is a full partition as shown here ..
Code:
mmcblk0p3
Offset: 1292369920 (0x4d080000)
Size: 2097152 (0x200000)
File system size: 512 * 4096 = 2097152 (fully occupies partition)
Linux rev 1.0 ext3 filesystem
Not mounted
Permissions: GID system can manipulate
Contains: Empty file system
Purpose: Recovery /misc
Referenced by: /system/lib/libandroid_runtime.so recovery ramdisk: /etc/recovery.fstab
Note: File system is referenced in recovery as emmc, not ext3!
Thx Josh

lj50036 said:
No, I dont think it injects anything into the kernel as there may not even be one in the LNX partition ..
Click to expand...
Click to collapse
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.

_that said:
I think berndblb meant that insmod injects something into the *currently running* kernel, which it does. It's used for loading additional kernel modules, usually drivers. When a module is loaded, its "init" function is called by the kernel so that it can hook its functionality into the proper kernel subsystems. My bootit.ko's init function simply reboots the tablet - without properly terminating processes, unmounting filesystems, etc. - so it should only be loaded when no partitions are mounted.
Click to expand...
Click to collapse
Nothing like _that to put you in your place....

lj50036 said:
Nothing like _that to put you in your place....
Click to expand...
Click to collapse
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!

awilson77584 said:
I'm trying to get back to a working recovery. Now I get a cycle of TWRP splash screens. This method looks promising because it appears to rebuild all of the partitions. I can use the Vol Down + Power keys to get to the bootloader (us_epad-10.6.1.14.10-20130801 A03. Can I skip to the fastboot steps? I had Crombi-kk running with rom2sd before I broke something trying to upgrade to zombie-x.
Thanks!
Click to expand...
Click to collapse
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:

LetMeKnow said:
You can skip all the way down to the command "fastboot erase misc". It should kick you out of twrp cycling...good luck..:fingers-crossed:
Click to expand...
Click to collapse
Thx!

Back up and running! Thanks!!!

OPO Wont load !

Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Device not rooted.

ashishk2 said:
Need Help: OPO will reboot after boot animation, when on CM set language page( Initial Setup page)
How do I re install 38R again ?
I have access to CM recovery & Fastboot by pressing Power & Volume keys.
Click to expand...
Click to collapse
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/

LaNsLyDe said:
I have the same exact issue. I restored all the same images and still the same thing. Trying something different now. You need to download the factory image from the bottom of this page : https://cyngn.com/products/oneplusone/
Click to expand...
Click to collapse
Hope it works bud ! So need the phone back and running.
Keep me posted

Will do, do you know where the thread went for the 38R flashable zip?
also when you download the fastboot zip extract it into where you have fastbooto n your pc and do these commands. will most likely wipe data and you can replace the recovery it flashed with a custom one:
Start the fastboot tool and run the following in the command line (that means, windows+r, type cmd, press enter), in sequence:
fastboot flash boot boot.img
fastboot flash userdata userdata_64g.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot reboot
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
ashishk2 said:
Hope it works bud ! So need the phone back and running.
Keep me posted
Click to expand...
Click to collapse
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.

LaNsLyDe said:
---------- Post added at 12:17 PM ---------- Previous post was at 12:01 PM ----------
[/COLOR]
i found the fix!
Do this it worked for me :
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on the XDA Developers forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Once everything is over, the OnePlus One should be restored without any data loss. We still don't know what causes the partition to get corrupted in the first place, but at least we all now know what to do if it does.
Click to expand...
Click to collapse
I'm not rooted or custom recovery ! What do I do ?

Thread closed ! "corrupt persist.img"
Thank you 
 @justinblaine23 for posting the link.
 @markbencze for proving detailed instruction for the fix.
 @other who posted solutions.
The issues for caused bcoz of corrupt persist.img. If anyone faces the same issue reboot after boot animation or 0Mb in recovery kindly following the instruction on this link
Caution: Dont press and hold the power button to rest the phone, this caused the error on my OPO.

System dump HTC U11+

Hi
I am searchin for a System dump for HTC U11+.
Can someone help me please?
Thank you and regards

damigor said:
Hi
I am searchin for a System dump for HTC U11+.
Can someone help me please?
Thank you and regards
Click to expand...
Click to collapse
You can decrypt RUUs using HTC RUU/ROM Decryption Tool to obtain the system.img and other .img files.

goodman_east said:
You can decrypt RUUs using HTC RUU/ROM Decryption Tool to obtain the system.img and other .img files.
Click to expand...
Click to collapse
Thank you very much. I guess you helped me a lot but I have no Idea how to make this stepsl So I will read instructions and try to understand them
Can I ask you for further information if I need some help?

damigor said:
Thank you very much. I guess you helped me a lot but I have no Idea how to make this stepsl So I will read instructions and try to understand them
Can I ask you for further information if I need some help?
Click to expand...
Click to collapse
Of course.

Hi
as supposed it has not work. See Log. :-/ Do you have any idea?

d to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_23.zip' (res=247)
Decrypting (25/25) 'zip_24.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
failed to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_24.zip' (res=247)
DecryptZIPs took 6.433 seconds.
Restoring '2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.01.709.3_Radio_8998-002772-1710131105_release_514337_combined_signed_2_4.zip' to normal folder
Removing unneeded work folders
Overall process completion time: 3 minutes 48.735 seconds.
Finished: Tool has finished but there was an error, please
check the console output and your OUT folder
'C:/adb/OUT'

goodman_east said:
Of course.
Click to expand...
Click to collapse
What do you think?

damigor said:
d to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_23.zip' (res=247)
Decrypting (25/25) 'zip_24.zip'
Encrypted zip detected, running ruuveal...
ruuveal
-------
failed to open keydata file: C:/adb/OUT/tmp/use_keyfile.bin
ERROR: could not decrypt file 'zip_24.zip' (res=247)
DecryptZIPs took 6.433 seconds.
Restoring '2Q4DIMG_OCEAN_M_DUGL_O80_SENSE90GP_hTC_Asia_TW_1.01.709.3_Radio_8998-002772-1710131105_release_514337_combined_signed_2_4.zip' to normal folder
Removing unneeded work folders
Overall process completion time: 3 minutes 48.735 seconds.
Finished: Tool has finished but there was an error, please
check the console output and your OUT folder
'C:/adb/OUT'
Click to expand...
Click to collapse
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.

goodman_east said:
Of course.
Click to expand...
Click to collapse
goodman_east said:
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
Click to expand...
Click to collapse
thank you very much. Where I have to put this Keyfile?

goodman_east said:
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
Click to expand...
Click to collapse
Ok. I got it.
Thank you very much. I have right now just Boot.img and system.img. I have flash a Boot.img but when I tra to flash System.img I recieve this error:
C:\adb>fastboot -w flash system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
target reported max download size of 2392800000 bytes
Invalid sparse file format at header magi
Creating filesystem with parameters:
Size: 121274105856
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29607936
Block groups: 904
Reserved block group size: 1024
Created filesystem with 11/7405568 inodes and 512922/29607936 blocks
Creating filesystem with parameters:
Size: 234881024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 57344
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/14336 inodes and 1961/57344 blocks
erasing 'system'...
OKAY [ 0.192s]
sending sparse 'system' (2325171 KB)...
FAILED ()
finished. total time: 1.370s
C:\adb>

damigor said:
Ok. I got it.
Thank you very much. I have right now just Boot.img and system.img. I have flash a Boot.img but when I tra to flash System.img I recieve this error:
C:\adb>fastboot -w flash system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
target reported max download size of 2392800000 bytes
Invalid sparse file format at header magi
Creating filesystem with parameters:
Size: 121274105856
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29607936
Block groups: 904
Reserved block group size: 1024
Created filesystem with 11/7405568 inodes and 512922/29607936 blocks
Creating filesystem with parameters:
Size: 234881024
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 57344
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/14336 inodes and 1961/57344 blocks
erasing 'system'...
OKAY [ 0.192s]
sending sparse 'system' (2325171 KB)...
FAILED ()
finished. total time: 1.370s
C:\adb>
Click to expand...
Click to collapse
command
Code:
fastboot flash -S 1G system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
fastboot flash boot C:\adb\OUT_2Q4D_1.01.709.3\system\boot.img

goodman_east said:
You need a keyfile or hosd.img to decrypt a RUU.
Here is the keyfile you need.
Click to expand...
Click to collapse
nenebear said:
command
Code:
fastboot flash -S 1G system C:\adb\OUT_2Q4D_1.01.709.3\system\system.img
fastboot flash boot C:\adb\OUT_2Q4D_1.01.709.3\system\boot.img
Click to expand...
Click to collapse
Thank you very much! This has worked but now I am in bootloop :-/

damigor said:
Thank you very much! This has worked but now I am in bootloop :-/
Click to expand...
Click to collapse
Are your device is htc_ocmdugl ?

nenebear said:
Are your device is htc_ocmdugl ?
Click to expand...
Click to collapse
Yes I am. Still having Bootloop :-/

damigor said:
Yes I am.
Click to expand...
Click to collapse
Plz upload the download mode photo of your U11 plus

goodman_east said:
Plz upload the download mode photo of your U11 plus
Click to expand...
Click to collapse
Here you go. Thanks guy for your support

damigor said:
Here you go. Thanks guy for your support
Click to expand...
Click to collapse
you can flash ruu 1.01.709.3, or 1.03.1405.1 after mid and cid changed

goodman_east said:
you can flash ruu 1.01.709.3, or 1.03.1405.1 after mid and cid changed
Click to expand...
Click to collapse
sorry, I need some more informaion. :-/

damigor said:
Here you go. Thanks guy for your support
Click to expand...
Click to collapse
cidnum: HTC__034 -- HTC Europe
OS-0.81.709.10 -- HTC TW
Change cidnum: 11111111 than flash RUU_1.01.709.3
flash HTC RUU use this tool -- adb tool
download mode
Code:
fastboot oem writecid 11111111
fastboot oem rebootRUU
flash flash zip RUU_name.zip
fastboot reboot

goodman_east said:
you can flash ruu 1.01.709.3, or 1.03.1405.1 after mid and cid changed
Click to expand...
Click to collapse
nenebear said:
cidnum: HTC__034 -- HTC Europe
OS-0.81.709.10 -- HTC TW
Change cidnum: 11111111 than flash RUU_1.01.709.3
flash HTC RUU use this tool -- adb tool
download mode
Code:
fastboot oem writecid 11111111
fastboot oem rebootRUU
flash flash zip RUU_name.zip
fastboot reboot
Click to expand...
Click to collapse
Thank you very much. This has worked but I am still in Bootloop

Help with a fastboot soft brick?

I had PixelDust running on my phone and realized that somehow I unlocked it and installed the custom ROM without installing TWRP, which I needed for Magisk which I needed for Google Pay. (Y'all can see where this is going...) In the process of trying to get TWRP installed I soft-bricked the Pixel 3, and it's now in a Fastboot bootloop. Is there a guide or thread like this one but for the Pixel 3 with Android 10, or can someone advise me on how to restore the phone to functionality?
On the phone, the Fastboot mode screen shows Device State: unlocked; boot slot: a; and Enter reason: error booting boot.img. My Win10 PC can see the phone when I run "fastboot devices" - it shows the phone's serial number.
Happy to provide more info if needed. Thank you!

big in japan said:
I had PixelDust running on my phone and realized that somehow I unlocked it and installed the custom ROM without installing TWRP, which I needed for Magisk which I needed for Google Pay. (Y'all can see where this is going...) In the process of trying to get TWRP installed I soft-bricked the Pixel 3, and it's now in a Fastboot bootloop. Is there a guide or thread like this one but for the Pixel 3 with Android 10, or can someone advise me on how to restore the phone to functionality?
On the phone, the Fastboot mode screen shows Device State: unlocked; boot slot: a; and Enter reason: error booting boot.img. My Win10 PC can see the phone when I run "fastboot devices" - it shows the phone's serial number.
Happy to provide more info if needed. Thank you!
Click to expand...
Click to collapse
There is no TWRP yet for Pixel 3 Android 10. There might be a bootable TWRP image.
In fastboot, reboot bootloader. Error message hopefully will be gone. I would then flash stock firmware.

Tulsadiver said:
There is no TWRP yet for Pixel 3 Android 10. There might be a bootable TWRP image.
In fastboot, reboot bootloader. Error message hopefully will be gone. I would then flash stock firmware.
Click to expand...
Click to collapse
Thanks. I was trying to install the temp TWRP boot image and failed (although I can't find the specific link to it now... ruh-roh.)
So, "reboot bootloader" did clear the error message, thanks again! But when I try to flash stock firmware ("fastboot flash recovery blueline-qq3a.200605.001-factory-80a32a4a.zip" - that's correct, right?) I get a lengthy error:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 1542731992 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1274300632 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1005869272 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 737437912 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 469006552 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 206682328 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/7 (262140 KB) error: write_sparse_skip_chunk: don't care size 1542731992 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1542731992 is not a multiple of the block size 4096
OKAY [ 6.049s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed​
Am I doing this wrong?

big in japan said:
Thanks. I was trying to install the temp TWRP boot image and failed (although I can't find the specific link to it now... ruh-roh.)
So, "reboot bootloader" did clear the error message, thanks again! But when I try to flash stock firmware ("fastboot flash recovery blueline-qq3a.200605.001-factory-80a32a4a.zip" - that's correct, right?) I get a lengthy error:
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 1542731992 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1274300632 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1005869272 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 737437912 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 469006552 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 206682328 is not a multiple of the block size 4096
Sending sparse 'recovery' 1/7 (262140 KB) error: write_sparse_skip_chunk: don't care size 1542731992 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1542731992 is not a multiple of the block size 4096
OKAY [ 6.049s]
Writing 'recovery' FAILED (remote: 'Not allowed to flash (recovery)')
fastboot: error: Command failed​
Am I doing this wrong?
Click to expand...
Click to collapse
You are supposed to unzip that zip and run the bat file that is inside it. Unless you want your phone wiped, you need to edit the bat file first by opening and removing the -w.

Tulsadiver said:
You are supposed to unzip that zip and run the bat file that is inside it. Unless you want your phone wiped, you need to edit the bat file first by opening and removing the -w.
Click to expand...
Click to collapse
Ah! Thank you! That worked, and almost everything is restored. Although the wi-fi will turn on and can "see" networks, it isn't able to connect to any of them. (Yes, the PWs are correct.) Any thoughts on what might be wrong or how to fix it?

Bumping - can any one help me diagnose the Wi-Fi issue? Since I was running PixelDust when I screwed things up, and the Wi-Fi problem showed up only after I flashed stock Android 10, should I re-flash PixelDust? I've gone through all the usual Wi-Fi fixing solutions to no avail, and I can't find anyone struggling with a similar issue. Hoping to not compound my problems again...

big in japan said:
Bumping - can any one help me diagnose the Wi-Fi issue? Since I was running PixelDust when I screwed things up, and the Wi-Fi problem showed up only after I flashed stock Android 10, should I re-flash PixelDust? I've gone through all the usual Wi-Fi fixing solutions to no avail, and I can't find anyone struggling with a similar issue. Hoping to not compound my problems again...
Click to expand...
Click to collapse
It might take a data wipe/factory reset.

Tulsadiver said:
It might take a data wipe/factory reset.
Click to expand...
Click to collapse
That was it - I wiped, then installed PD. Thanks for all the help!!

How To Guide [CLOSED] Deleted

Here was a Guide. Someone said people don't care about Me or My Work so...​

there is no Xperia 5 III or even the Xperia 1 III at the Sony Website

I Think you can use xperia 5 II. For xperia 5 II was Xperia 5 the right option before Xperia 5 II was listed

Not one notice that this nulls your warranty........

riahc3 said:
Not one notice that this nulls your warranty........
Click to expand...
Click to collapse
You get this Info from SONY, and it just makes Sense... You don't have trouble if You can relock Your Device. So stop spreading random Infos like "nulls Your Warranty". No One here complains about that...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Flash Firmware with newflasher ends in bootloop and "your device is corrupt"....
How can i fix it?
Edit: I Fixed it with set_active:a

which file i need from there for A 11
Generic System Image releases | Platform | Android Developers
developer.android.com

DanielMode said:
which file i need from there for A 11
Generic System Image releases | Platform | Android Developers
developer.android.com
Click to expand...
Click to collapse
Basic knowledge for all Tech around the World before You continue with anything of this:
ARM = Mobile Chips
ARM64 = Mobile Chips with 64Bit Support
X86 = Desktop Chips like from AMD or Intel
X86_64 = You guessed it? Desktop 64Bit Chips...
GMS = Google Services or Google Apps
You want to use an Xperia Mobile Device with GMS?
ARM64 GMS... No GMS no Play Store...

i don't get it where i have to look for this sin file
3. Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)

DanielMode said:
i don't get it where i have to look for this sin file
3. Extract the File boot_********.sin with the Unsin Exe (Drag and drop the Image on the Exe)
Click to expand...
Click to collapse
Before Modding Your Device...
Download the Firmware for Your Model with Xperifirm. It will include everything that's needed. Including Your Way back to a working Device if You screw something...
I will edit the Threads soon with a hint for this. Sorry for the trouble!

already found it at patched too but was confusing buddy
to find at the main folder of downloaded FW from XperFirm

DanielMode said:
already found it at patched too but was confusing buddy
to find at the main folder of downloaded FW from XperFirm
Click to expand...
Click to collapse
To be honest with everyone, I don't have much time usually but I do my best to help out if I can! I have many Projects running and writing Guides isn't my Top Priority. But I will rework them ones more! Thank You for pointing out that part of the Guide!

so far so good, but now i'm getting nervis
after flashing patched boot.img i'm at this step now
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 39.720s]
formatting 'userdata' partition...
how long it takes to formating 'userdata' ??
i wait 30min already

looks like i messed it up
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 38.658s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type f2fs not supported.
OKAY [ 0.009s]
erasing 'cache'...
FAILED (remote: No such partition.)
finished. total time: 38.698s
PS C:\platform-tools>
how can i revive it now.??

k started all over again and now at this step again and waiting
formatting 'userdata' partition...
will see if its done when i get up tomorrow

6 hours later and still
formatting 'userdata' partition...

erasing and/or formating isn't finishing anymore
after flashing patched boot.img

finaly i could flash latest FW with newflasher
but root wasn't there so
i flashed patched boot.img with fastboot again and i got root acces
was a bit of'n struggel but now its rooted
now i was trying die relock the bootloader...u said wipe userdata again and i did and got stuck there now
PS C:\platform-tools> fastboot -w
erasing 'userdata'...
OKAY [ 41.602s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 107809730560
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 26320735
Block groups: 804
Reserved block group size: 1024
Created filesystem with 11/6586368 inodes and 461507/26320735 blocks
sending 'userdata' (144159 KB)...
writing 'userdata'...

Can i Lock the Bootloader with Root Access?

Hi @Miustone ,
At the GSI flashing stage, I am getting an error.
fastboot flash system_a system.img
Click to expand...
Click to collapse
returns FAILED (remote: 'No such partition.')
Click to expand...
Click to collapse
I tried dropping the _a but that didn't help.
My eventual goal is to replace the MBN files following :https://forums.oneplus.com/threads/...ell-volte-and-vowifi-calling-working.1284987/
When I try to access su from adb shell, I just get a cursor that doesn't seem to execute commands. But doesn't give the error from before rooting. So I'm semi rooted?