I tried rooting my phone now it will not get pass the loading screen. I tried to flash the stock ruu but I get errors
I have pictures but not aloud to post yet. But on my phone it says
Software status modified
Unlocked
S-on
.
When I try to flash the ruu zip I get
C:\Users\KJ\Desktop\platform-tools>fastboot flash zip rom.zip
target reported max download size of 800000000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of
the block size 4096
sending sparse 'zip' 1/1 (0 KB)...
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of
the block size 4096
error: write_sparse_skip_chunk: don't care size 2330284468 is not a multiple of
the block size 4096
OKAY [ 1.065s]
writing 'zip' 1/1...
(bootloader) HOSD CL#695981
(bootloader) ERR lzipv1_init : Cannot read header len bytes
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_q
(bootloader) LrXHZ
FAILED (remote: 99 RU_UNKNOWN_FAIL terrible mishap )
finished. total time: 2.142s
Hi,
you could try using the htc_fastboot from here:
https://www.androidfilehost.com/?fid=24421527759880682
----------
(from thread http://forum.xda-developers.com/ver...arshmallow-t3316279/post65365561#post65365561 )
If your current fastboot isn't working/throws errors, please use the HTC fastboot in the zip below:
https://www.androidfilehost.com/?fid=24421527759880682 (htc_fastboot.zip)
Replace existing commands with the HTC_fastboot prefix.
So for example, instead of:
Code:
fastboot flash zip firmware.zip
You would do this instead:
Code:
HTC_fastboot flash zip firmware.zip
You are amazing I just tried and it worked !!!!! You are heavensent.
Now one last question do I have to redo the recovery and everything to get a custom Rom?
I just went through the process of installing the custom Rom again and now my phone constantly boot loops with the message " this build is for development purposes only..." it was the newest version of supersu
Kj_gotem said:
I just went through the process of installing the custom Rom again and now my phone constantly boot loops with the message " this build is for development purposes only..." it was the newest version of supersu
Click to expand...
Click to collapse
I'm glad it worked
You need to look for an older version of SuperSU.... 2.64 or 2.65
edit: I'm pretty sure this one works
Hey Everybody,
I have been a silent person on XDA visiting as a guest but now in need of help!
I downloaded Lineage 14.1 for my M8 from here about 8 months ago, however time has come to move on to something else.
The issue is firstly I wish to update TWRP but every time I do a reboot to enter recovery I don't get that option anymore. Seems like it has disappeared. Can anyone advise me how I can get the latest version of TWRP back on my device please?
m70yab said:
The issue is firstly I wish to update TWRP but every time I do a reboot to enter recovery I don't get that option anymore.
Click to expand...
Click to collapse
Not completely clear what you mean here. Are you booting to bootloader? You should have the option to enter recovery from there. But the choice to select boot recovery missing? If so, that would be strange. Don't think I've seen that before.
Or you can select to boot recovery, and it doesn't go to recovery (reboots, etc.)?
m70yab said:
Can anyone advise me how I can get the latest version of TWRP back on my device please?
Click to expand...
Click to collapse
Flash latest TWRP with fastboot. Or if that fails, tell us if there is an error message, or other description of the issue.
redpoint73 said:
Not completely clear what you mean here. Are you booting to bootloader? You should have the option to enter recovery from there. But the choice to select boot recovery missing? If so, that would be strange. Don't think I've seen that before.
Or you can select to boot recovery, and it doesn't go to recovery (reboots, etc.)?
Flash latest TWRP with fastboot. Or if that fails, tell us if there is an error message, or other description of the issue.
Click to expand...
Click to collapse
I am trying to install TWRP (3.2.1-0-m8) on a HTC One M8 and here is the error message I get:
C:\Users\moham\Desktop\HTC_M8\Last>fastboot flash recovery "C:\Users\moham\Desktop\HTC_M8\Last\twrp-3.2.1-0-m8.img"
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 4012032 is not a multiple of the block size 4096
sending sparse 'recovery' 1/2 (16380 KB)...
error: write_sparse_skip_chunk: don't care size 4012032 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 4012032 is not a multiple of the block size 4096
OKAY [ 1.681s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.691s
Any advice? any help?
Hi, that's my first customisation:
1. Device unlocked:
{
"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"
}
2. TWRP flashed + *zip ready on /sdcard1
3. Install Zip fails
The checksums of all zips are ok, verified on my notebook.
I also can't wipe. And the standard Android 7.1 is recovering itself, if I boot-up.
Please advise, thanks!
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
SECURE BOOT - enabled — Am I root?
kabu83 said:
1. Try unchecking signature verification in TWRP
2. Most likely, you will have to downgrade to CM13.1 first with that mounting error
3. I recommend using the standard LOS zip, it seems you have one with microG embedded
Click to expand...
Click to collapse
Thanks, I did all that and much more, trying to install CM 13.1, crDroid, OrangeFox, SuperSu => nothing installs!
Now I wonder: Am I root at all? I thought so, since I installed TWRP on a naked device?!
The bootloader shows: DEVICE STATE - unlocked
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
TWRP cannot mount /system
kabu83 said:
The Problem is, that TWRP cannot mount /system in the first place.
Have you tried downgrading following these steps: https://forum.xda-developers.com/showpost.php?p=72261104
Click to expand...
Click to collapse
Now, that my holidays are over, I want this Crackling to crack!
Here my efforts to crack it via Fastboot:
Since the vintage Cyanogen fails as well as the state of the art Linage, I suspect that the payload might not be the cause for the failure?!
Code:
# fastboot flash system lineage-16.0-20190826-microG-crackling.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 2794255 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.841s]
sending sparse 'system' 1/3 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 271225615 is not a multiple of the block size 4096
OKAY [ 8.258s]
writing 'system' 1/3...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 16.173s
# fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 1.042s]
finished. total time: 1.043s
# fastboot flash system SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magic
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 350727218 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 82295858 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.831s]
sending sparse 'system' 1/4 (262140 KB)...
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 619158578 is not a multiple of the block size 4096
OKAY [ 8.290s]
writing 'system' 1/4...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 14.176s
# fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.205s]
finished. total time: 0.205s
# fastboot flash recovery twrp-3.3.1-0-crackling.img
target reported max download size of 268435456 bytes
sending 'recovery' (16984 KB)...
OKAY [ 0.563s]
writing 'recovery'...
OKAY [ 1.188s]
finished. total time: 1.751s
# fastboot boot twrp-3.3.1-0-crackling.img
downloading 'boot.img'...
OKAY [ 0.535s]
booting...
OKAY [ 0.672s]
finished. total time: 1.208s
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Bootloader vs BIOS
kabu83 said:
Boot to recovery (TWRP), then touch the bottom right menu button, what does it say in the terminal log? (Similar to the 2nd screenshot you posted.)
Click to expand...
Click to collapse
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
[email protected] said:
At the time of the Cyanogen/Linage installation I had no TWRP installed! Would it help to repeat the process?
In general, I assumed the Bootloader to function similar to the BIOS at a PC? That makes me wonder, why an Android installation-process via Fastboot can't just reformat the entire drive and do a fresh partitioning? (instead of complaining about 'chunks' and 'block-sizes')
Thanks for all your assistance, most appreciated! :good:
Click to expand...
Click to collapse
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currentyl installed?
/system is empty
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Then boot to recovery and check, if TWRP can mount the system Partition.
What OS do you have currently installed?
Click to expand...
Click to collapse
As mentioned, I prefer a clean install. Thus formatted /system with ext4 via Fastboot (it's default). It should be possible to mount an empty /system -- isn't it?
A clean install is needed anyway. It seems just easier to install the OS via TWRP and for future nightly updates anyway.
Heureka!
kabu83 said:
I would recommend installing TWRP, Version 3.2.1-0.
Click to expand...
Click to collapse
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
[email protected] said:
With TWRP 3.2.1-0 I managed to install SW27-WF-CRACKLING-CM-13.1.5-ZNH2KAS7EB-RECOVERY.zip :good:
(I failed though to install "lineage-16.0-20190826-microG-crackling.zip" before.)
What's next? Replacing Cyanogen Bootloader with TWRP 3.2.1-0 again?
Then trying a pure Lineage and later Gapps seperately?
Click to expand...
Click to collapse
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Bingo!
kabu83 said:
Can you boot into CM 13 now?
Has it replaced TWRP as recovery?
Click to expand...
Click to collapse
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
[email protected] said:
I've got Cyanogen Fastboot, Lineage Bootloader, and Lineage Crackling 190801.002 up and running… :good:
With CM 13 installed, TWRP directly installed "lineage-16.0-20190826-microG-crackling.zip" from SD-card.
Thanks again for your advice, it appears that the Android System which Google offers as update to CM13, indeed prevented the alternative OS installation somehow.
Click to expand...
Click to collapse
Happy to help. So you are all set now?
Hi everyone. I've read some about this issue: GSI 11 and 12 roms are bigger than 9 and 10 versions, so when triyng to flash it via fastboot i got this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system C:\Users\thefa\Desktop\Corvus_v17.0-Vanguard-treble_arm64_ab_vndklite-Gapps-17122021-Beta-Official-0000.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/9 (460796 KB)...
OKAY [ 10.906s]
writing 'system' 1/9...
FAILED (remote: sparse flash write failure)
finished. total time: 10.937s
I've noticed that the problem is the small size of device partition (Honor Note 10), that it's project treble compatible, but it can install only android 9 and 10 roms from project treble.
So, any idea of what can i do for increase size of the partition for make a successfully installation of GSI 11 and 12 ?!
Thanks to all for the support!
TheFastGT said:
Hi everyone. I've read some about this issue: GSI 11 and 12 roms are bigger than 9 and 10 versions, so when triyng to flash it via fastboot i got this:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system C:\Users\thefa\Desktop\Corvus_v17.0-Vanguard-treble_arm64_ab_vndklite-Gapps-17122021-Beta-Official-0000.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magic
sending sparse 'system' 1/9 (460796 KB)...
OKAY [ 10.906s]
writing 'system' 1/9...
FAILED (remote: sparse flash write failure)
finished. total time: 10.937s
I've noticed that the problem is the small size of device partition (Honor Note 10), that it's project treble compatible, but it can install only android 9 and 10 roms from project treble.
So, any idea of what can i do for increase size of the partition for make a successfully installation of GSI 11 and 12 ?!
Thanks to all for the support!
Click to expand...
Click to collapse
I suggest you do not do this because my Huawei P-Smart Went to f...u..k Went to **** on this issue
I've recently unlocked an older Pixel 2xl 64Gb for a specific use (Octopi), and I'm looking to install the RevengeOS 4.1 Magisked patched ROM, but got this error:
C:\platform-tools_r33.0.1-windows>fastboot flash boot_a magisk_patched-24300_jd970.img
Warning: skip copying boot_a image avb footer (boot_a partition size: 41943040, boot_a image size: 134217728).
Sending 'boot_a' (131072 KB) OKAY [ 3.184s]
Writing 'boot_a' FAILED (remote: 'Error flashing partition.')
fastboot: error: Command failed
It looks like the partition size available for a ROM is only 42Mb. Am I reading this correctly? How do I correct this?
Your rom goes into the system_a or b partition.
BTW, a quick googling didn't find any RevengeOS 4.1 for Taimen. Are you sure your downloaded a rom for this phone? If yes, check if there is an install guide for the rom - the procedure can vary a bit