Lets start posting them here.
This belongs in the themes and apps section honestly.
jpwhre said:
Lets start posting them here.
Click to expand...
Click to collapse
These work BUT YOU MUST:
http://forum.xda-developers.com/one-m9/themes-apps/mod-splash-screen-collection-htc-one-m9-t3075126
Replace the android txt file with this one (For the sprint phone)
http://forum.xda-developers.com/attachment.php?attachmentid=3279463&d=1429882543
Flash from bootloader must be S-OFF
fastboot oem rebootRUU
fastboot flash zip splashfilename.zip
fastboot reboot
Question. How do I convert a .img to an nb0 file?
Sent from my 0PJA2 using Tapatalk
---------- Post added at 01:50 AM ---------- Previous post was at 01:32 AM ----------
Tried renaming a .img to nb0 and fastboot flashing but I got...
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner\Desktop\Root+Sprint+HTC+One+M9\Root HTC One M9>f
astboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Documents and Settings\Owner\Desktop\Root+Sprint+HTC+One+M9\Root HTC One M9>f
astboot flash zip supergirl.zip
target reported max download size of 800000000 bytes
sending 'zip' (1209 KB)...
OKAY [ 1.063s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: no required image fo
(bootloader) und in ZIP file
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 13
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 13
(bootloader) [email protected]
FAILED (remote: 13: fail to flash via downloadzip)
finished. total time: 3.125s
C:\Documents and Settings\Owner\Desktop\Root+Sprint+HTC+One+M9\Root HTC One M9>
Sent from my 0PJA2 using Tapatalk
motoelliot said:
Question. How do I convert a .img to an nb0 file?
Sent from my 0PJA2 using Tapatalk
---------- Post added at 01:50 AM ---------- Previous post was at 01:32 AM ----------
Tried renaming a .img to nb0 and fastboot flashing but I got...
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Owner\Desktop\Root+Sprint+HTC+One+M9\Root HTC One M9>f
astboot oem rebootRUU
...
OKAY [ 0.031s]
finished. total time: 0.031s
C:\Documents and Settings\Owner\Desktop\Root+Sprint+HTC+One+M9\Root HTC One M9>f
astboot flash zip supergirl.zip
target reported max download size of 800000000 bytes
sending 'zip' (1209 KB)...
OKAY [ 1.063s]
writing 'zip'...
(bootloader) HOSD CL#506785
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: no required image fo
(bootloader) und in ZIP file
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 13
(bootloader) ERR Update zip file failed.
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 13
(bootloader) [email protected]
FAILED (remote: 13: fail to flash via downloadzip)
finished. total time: 3.125s
C:\Documents and Settings\Owner\Desktop\Root+Sprint+HTC+One+M9\Root HTC One M9>
Sent from my 0PJA2 using Tapatalk
Click to expand...
Click to collapse
Make sure the image file inside the zip is named Splash1.nb0
Yes it is, but I'm asking how do I take a .img file and convert it to a .nb0 file...?
After making my first splash screen, I love this little tweak. And the process is incredibly easy once you acquire all the resources.
motoelliot said:
Yes it is, but I'm asking how do I take a .img file and convert it to a .nb0 file...?
Click to expand...
Click to collapse
After you have the .img file, you just change the extension to .nb0
Make sure it's titled splash1.nb0, then you're golden
Moved Tutorial to its own thread...
http://forum.xda-developers.com/sprint-one-m9/themes-apps/guide-create-splash-screens-t3110943
Some splash screens for the Sprint Group...
MOVED... My splash screens...
http://forum.xda-developers.com/sprint-one-m9/general/guide-create-splash-screens-t3110943
I have the working Android-info.txt for sprint, I didn't know Benny's converter worked yet... Thanks for the info!
Sent from my 0PJA2 using Tapatalk
predator1584 said:
More Customization Information
I have unlocked bootloader and S-OFF. (The attached android-info.txt is for the Sprint Variant only)
per usual, not responsible for bone-headed ness
You will need:
benny3's Image Converter (extracted) (http://forum.xda-developers.com/showthread.php?t=2316060)
an image in the dimensions of 1080x1920 (can be .png, .jpg, .bmp)
latest android-info.txt (link at bottom)
**optionally** Photoshop, GIMP, Paint (I guess this could work. eek)
Steps to make your HTC One not blind you upon a restart...
Edit photo to liking
MAKE SURE IMAGE IS THE CORRECT SIZE
Open benny3's converter FOLDER, copy image to the 'place-image-here' folder
Run CLICK-HERE.BAT
Convert .jpg (.bmp, .png) to .img, close upon completion
copy custom.img(from place-image-here folder) to Project Folder, rename file to splash1.nb0
copy android-info.txt to same Project Folder
Zip/Archive these two files (I use winRAR), archive format MUST be .zip
Copy ProjectFolder.zip to sdk directory (wherever your fastboot command is located)
Reboot into Download Mode
type: fastboot devices (make sure device is attached)
type:
Code:
fastboot oem rebootRUU
fastboot flash zip ProjectFolder.zip
fastboot reboot
Enjoy
Thanks to @schmeggy929, @SoLdieR9312 @benny3 for the tool and the community for the information :good::good:
Click to expand...
Click to collapse
Thanks for double posting this boss. I'm sure not everyone has found the other thread since it's not on the Sprint section.
I'm subscribed to both just in case.
Edit: for those interested there is more info here http://forum.xda-developers.com/one-m9/themes-apps/mod-splash-screen-collection-htc-one-m9-t3075126 but you will need the above info text posted above. There has been a recovery flashible tool posted in that thread and it doesn't work, I've tested both versions still no solution so fastboot it remains.
I used to make them for the Galaxy S3 on Boost Mobile now to start making them for the One M9
Related
Hello to all users xda! I have a question to experts create custom rom. I have a rom.zip taken from RUU_Legend_Froyo_S_HTC_WWE_3.15.405.6_Radio_47.51.35.17_7.13.35.05_release_222317_signed.exe. Installed it's Rom on my legend and rooted, added; Superuser,ROM Manager. Then pulled system.img and boot.img. Now I want to replace the files in the original rom.zip: system.img, boot.img, recovery.img and radio.img. I do not know how to make such an archive. Tried to pack through dsixda's Android Kitchen in HBOOT not flashing. And when i'm try via to command flash fastboot i get an error:
Code:
C:\fly380>fastboot oem rebootRUU
... OKAY
C:\fly380>fastboot flash zip LEGEIMG.zip
sending 'zip' (143800 KB)... OKAY
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
FAILED (remote: 99 unknown fail)
Tell me how to collect the same in structure, as the original rom.zip archive. To flash without ClockworkMod or other fake Recovery, using a flashing through HBOOT?
Immediately thank for the help and Sorry for my english.
This RUU rom was extraced directly from RUU_M7_UL_JB_50_Cingular.exe and I've verified it successfully restored my previous One on my Mac before exchanging it at AT&T.
https://mega.co.nz/#!yNQlFJKb!aTXDHQRG0mcv3htWOHjnYxpExjB5dT7HdkuNxCtSVyo
Please note, you must have the original 1.44 HBOOT flashed before running this RUU found here:
https://mega.co.nz/#!XhRlXBhB!V8In4VJhp5MXwj9r9gyleTCFiUIbKWxDFmcmn8v3zIU
Thanks Clownzer!
RebootRUU. Then fastboot flash zip I assume?
gunnyman said:
RebootRUU. Then fastboot flash zip I assume?
Click to expand...
Click to collapse
Yessir
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
acquiredhate said:
Yessir
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Click to expand...
Click to collapse
Gracias
@acquiredhate looks like your zip may be corrupt. I've tried downloading it twice. Same result.
Hmm, I'll re-upload it tonight, thanks for checking into that for me!
acquiredhate said:
Yessir
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Click to expand...
Click to collapse
Does fastboot flash zip rom.zip actually have to be entered twice?
Yes it does. It fails the first time.
gunnyman said:
Yes it does. It fails the first time.
Click to expand...
Click to collapse
do you have to relock for this?
apatcas said:
do you have to relock for this?
Click to expand...
Click to collapse
if you're S-off, no
acquiredhate said:
Yessir
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip
fastboot reboot
Click to expand...
Click to collapse
Anyone willing to give me a layman's set of instructions on this. I need to restore to stock, but this is meaningless to me. Yes, I am aware that I am exposing myself to ridicule and the third circle of XDA inferno.
I am coming from a GE edition and I keep getting this error:
C:\>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.046s
C:\>fastboot.exe flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1029872 KB)...
OKAY [ 45.620s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 51.098s
When I try to use the windows RUU I get an error 155
Can anyone elaborate on these instructions for MAC users.
Getting same error as this user. I am using 4.2.2 android rev HD.
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 144.627s
Clownzer said:
I am coming from a GE edition and I keep getting this error:
C:\>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.043s]
finished. total time: 0.046s
C:\>fastboot.exe flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1029872 KB)...
OKAY [ 45.620s]
writing 'zip'...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (status read failed (Too many links))
finished. total time: 51.098s
Click to expand...
Click to collapse
jadsru1 said:
Getting same error as this user. I am using 4.2.2 android rev HD.
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 144.627s
Click to expand...
Click to collapse
I found the answer to this issue... here is my quote from another thread:
Clownzer said:
So after two days of not having a phone, I solved the issue.
It seems the RUU would not run with the newer version of HBOOT found in the GE version of the rom. So I reflashed HBOOT 1.44 (see attached) and BOOM RUU worked and back to stock!
Hope this helps someone
https://mega.co.nz/#!XhRlXBhB!V8In4VJhp5MXwj9r9gyleTCFiUIbKWxDFmcmn8v3zIU
Click to expand...
Click to collapse
Clownzer said:
I found the answer to this issue... here is my quote from another thread:
Click to expand...
Click to collapse
Hey guys, sorry, I've been away for a while and just now checked in on this thread. The downgrade of the HBOOT to 1.44 is necessary. Thank you for adding in this crucial piece of the puzzle I left out. I will add this to my original post!
Link is dead .please check Rom link
I cannot get my HTC one back to stock, I've downloaded multiple RUU's, both .exe and .zip. The .exe will open on my PC, then say "Not Responding" then completely terminate the program. The .zip file says
C:\Users\home\Desktop\Fastboot>fastboot flash zip RUU.zip
sending 'zip' (1180768 KB)...
OKAY [ 42.626s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 42.882s
I'm running the .zip file in: fastboot oem rebootRUU
then I run : fastboot flash zip RUU.zip
I just want to get it to stock.
I mean't RUU will NOT run on my PC
you cant do it that way. has to be placed on your phones storage and done from within Stock recovery. may be able to side load not certain
Hey Guys i need help
I want to go back to the original OS from GrapheneOS. But whenever I want to flash the Google Stock Image via Fastboot, an error appears. The online flash tool from Google also breaks off when flashing.
Fastboot Error:
FAILED (remote: failed to flash partition (system_b))
Why did you flash a custom rom if you have no clue on what you are doing? Ask the rom developer your question.
Always research and read about what modding you are interested in.
Lesson learned!
"Biffer"??
What kind of adb tools are you using?
vandyman said:
Why did you flash a custom rom if you have no clue on what you are doing? Ask the rom developer your question.
Always research and read about what modding you are interested in.
Lesson learned!
Click to expand...
Click to collapse
The device was from ebay with custom rom installed. That's why I wanted to go back.
ExodusCrowley said:
Hey Guys i need help
I want to go back to the original OS from GrapheneOS. But whenever I want to flash the Google Stock Image via Fastboot, an error appears. The online flash tool from Google also breaks off when flashing.
Fastboot Error:
FAILED (remote: failed to flash partition (system_b))
Click to expand...
Click to collapse
Are you using the latest Platform Tools?
ExodusCrowley said:
The device was from ebay with custom rom installed. That's why I wanted to go back.
Click to expand...
Click to collapse
Ah I see.
Download the Pixel factoy image. Unzip it. Run flash-all.bat. There are a few how to guides on this. Or just follow the Google developers guide.
Android platform - tools versions 32 or 33 will work on your PC for adb/fastboot commands.
Make sure you install the official Google usb driver on your PC or the platform tools will not work right.
Lughnasadh said:
Are you using the latest Platform Tools?
Click to expand...
Click to collapse
yes
target reported max download size of 261095424 bytes
sending 'bootloader_b' (10862 KB)...
OKAY [ 0.343s]
writing 'bootloader_b'...
(bootloader) Flashing pack version slider-1.0-8062051
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_b
(bootloader) Flashing partition pbl_b
(bootloader) Flashing partition bl2_b
(bootloader) Flashing partition abl_b
(bootloader) Flashing partition bl31_b
(bootloader) Flashing partition tzsw_b
(bootloader) Flashing partition gsa_b
(bootloader) Flashing partition ldfw_b
(bootloader) Loading sideload ufsfwupdate
OKAY [ 2.954s]
finished. total time: 3.298s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.018s
target reported max download size of 261095424 bytes
sending 'radio_b' (80220 KB)...
OKAY [ 3.111s]
writing 'radio_b'...
(bootloader) Flashing pack version g5123b-93368-211225-M-8029609
(bootloader) Flashing partition modem_b
OKAY [ 0.316s]
finished. total time: 3.436s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.009s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 1.270s
target reported max download size of 261095424 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (16 MB) to disk... took 0.142s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (849 MB) to disk... took 62.433s
archive does not contain 'system.sig'
extracting system_other.img (22 MB) to disk... took 0.400s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took -0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (459 MB) to disk... took 31.867s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
--------------------------------------------
Bootloader Version...: slider-1.0-8062051
Baseband Version.....: g5123b-93368-211225-B-8029609
Serial Number........: 1C231FDF6002U5
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.009s]
checking version-baseband...
OKAY [ 0.009s]
sending 'boot_b' (65536 KB)...
OKAY [ 1.999s]
writing 'boot_b'...
OKAY [ 0.279s]
sending 'dtbo_b' (16384 KB)...
OKAY [ 0.567s]
writing 'dtbo_b'...
OKAY [ 0.077s]
sending sparse 'system_b' 1/4 (254972 KB)...
OKAY [ 9.461s]
writing 'system_b' 1/4...
(bootloader) image size (894066688) biffer than partition size (0)
FAILED (remote: failed to flash partition (system_b))
finished. total time: 12.578s
Press any key to exit...
Click to expand...
Click to collapse
Complete flash log
Platform Tools and Android USB drivers are up to date
After flashing via Linux it worked.
ExodusCrowley said:
Complete flash log
Platform Tools and Android USB drivers are up to date
Click to expand...
Click to collapse
Something is not updated right in your Pc.
alin919 said:
Something is not updated right in your Pc.
Click to expand...
Click to collapse
I have no idea where the error was. It worked with Linux.
I have flashed (fastboot method) twrp.img to my locked device and now I'm stuck at boot. At first I was getting boot loop and "corrupt" message (g.co/ABH). Luckily, I could still access fastboot mode. By looking around, I managed to remedy that a bit by:
Code:
$ wget https://dlcdnets.asus.com/pub/ASUS/ZenFone/AI2202/UL-ASUS_AI2202-ASUS-33.0804.2060.100-1.1.1-2302-user.zip
$ unzip *zip
$ payload_dumper payload.bin
$ for i in boot dtbo vendor_boot vbmeta vbmeta_system
do
fastboot flash $i output/$i.img
done
$ fastboot reboot fastboot
# these will fail due to resizing partitions on a locked device
$ for i in system system_ext product odm vendor
do
fastboot flash $i output/$i.img
done
Resizing partition ... (Can't in locked state)
Now I get bootloader, fastbootd, and stock recovery. Wiping/resetting in recovery mode almost succeeds:
Code:
misc_vab_msg.version: 0x2
misc_vab_msg.magic: ...
misc_vag_msg.merge_status: 0x0
misc_vag_msg.source_slot: 0x1
-- Wiping data...
E:Open failed: /metadata/ota: No such file or directory
-- Clean boot sound files...
Formatting /data...
Formatting /metadata...
-- Data wipe complete.
At this point, restarting the system results in the device turning itself off a few seconds after the ASUS logo.
My phone is on stock firmware 33.0804.2060.100 (android 13). Could someone kindly help me and tell me what to do next?
Here's all the info I can get now:
Code:
$ fastboot oem device-info
(bootloader) Verity mode: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Device authorized: false
(bootloader) Device authorized2: false
(bootloader) WaterMask unlock: N
(bootloader) XBL:
(bootloader) ABL: 0.0.029.0-WW-user
(bootloader) SSN: ...
(bootloader) ISN: ...
(bootloader) IMEI: ...
(bootloader) IMEI2: ...
(bootloader) CID: ASUS
(bootloader) COUNTRY: EU
(bootloader) Project: DAVINCI
(bootloader) DT ID: 66
(bootloader) SB: Y
(bootloader) SBNR: Y
(bootloader) DDR Manufacturer ID: 1
(bootloader) DDR Device Type: 8
(bootloader) TotalDMCounter: 0
(bootloader) DMCounter: 0
(bootloader) SlotARetryCounter: 0
(bootloader) SlotAUnbootableCounter: 0
(bootloader) SlotBRetryCounter: 0
(bootloader) SlotBUnbootableCounter: 0
(bootloader) BOOT_COUNT: 0
(bootloader) LOCK_COUNT: 0
(bootloader) Check_APDP: 1
(bootloader) rawdump_en: false
(bootloader) force start logcat-asdf: false
(bootloader) Current Slot: a
(bootloader) Slot_a bootable: Bootable
(bootloader) AVB Verity: Enable
(bootloader) Verify vbmeta ret: 0
(bootloader) ABL_FTM: FALSE
(bootloader) UART-ON Status: false
I have a feeling that I'm not using the right image for this purpose. I don't know how to get my hands on a RAW image. I keep reading about some android beta page, but just can't find a link for Zenfone 9.
You dont need any raw fw, flash stock recovery and reboot:
fastboot flash recovery recovery.img
Download Data package from February 25th.
Size of the data package: 100 MB. Free transfer of up to 6 GB of photos, videos and documents. Send large files via email or a link to share. No registration, no ads, just simple file sharing!
filetransfer.io
Recovery from UL-ASUS_AI2202-ASUS-33.0804.2060.100
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
lordbit said:
@NisseGurra thanks for your input. I checked the md5sum of your recovery image and the one I extracted from the payload.bin. They are indeed the same. I have flashed it alright:
Code:
$ fastboot flash recovery recovery.img
Sending 'recovery' (102400 KB) OKAY [ 3.396s]
Writing 'recovery' OKAY [ 0.162s]
Finished. Total time: 3.570s
Now, what should I do? reboot to bootloader -> recovery? then what?
Because still letting the device boot normally will lead to its shutdown in 20 seconds.
Click to expand...
Click to collapse
Seems something got messed up.
You have some options: find an recovery that have adb sideload support: flash the stock fw from it,
adb sideload xxx.zip
Option 2
Repack the stock fw (use payload dumper to extract all img), create an folder with all extracted img and add adb.exe, fastboot.exe, AdbWinApi.dll, AdbWinUsbApi.dll and install.bat (attached, rename to .bat)
Connect phone, enter fastboot and click on the bat file, it should install full rom.
Thanks! I will try it.
I tried your second method. Most of the images got flashed alright, except these ones:
Code:
Sending 'odm' (1248 KB) OKAY [ 0.055s]
Writing 'odm' FAILED (remote: '(odm_a) No such partition')
fastboot: error: Command failed
Sending sparse 'product' 1/4 (524236 KB) OKAY [ 19.285s]
Writing 'product' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending sparse 'system' 1/7 (524232 KB) OKAY [ 19.632s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'system_ext' (386600 KB) OKAY [ 14.180s]
Writing 'system_ext' FAILED (remote: '(system_ext_a) No such partition')
fastboot: error: Command failed
Sending sparse 'vendor' 1/3 (524176 KB) OKAY [ 18.675s]
Writing 'vendor' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Sending 'vendor_dlkm' (73448 KB) OKAY [ 2.577s]
Writing 'vendor_dlkm' FAILED (remote: '(vendor_dlkm_a) No such partition')
fastboot: error: Command failed
I think those should be flashed after a
Code:
fastboot reboot fastboot
But in that case, the "flash" command will try to resize the partitions and I get an error that says "Resizing in a locked state of the device is not possible". I am paraphrasing here.
Option 3, install https://forum.xda-developers.com/t/paranoid-android-topaz-alpha-1-asus-zenfone-9.4557631/
Use the suggested image way. It install new recovery, if i rember correct it has adb support
Reboot recovery and use option2
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
lordbit said:
@NisseGurra sorry if my question seems dumb. But I have not unlocked my bootloader (when I had the chance). Do these recovery.img methods with adb work for me?
Click to expand...
Click to collapse
If you bootloader is locked so you cant flash anything not signed by Asus, no twrp etc, So strange it got messed up
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Darkmasterhk said:
Yeah it's weird that you could flash anything at all, that isn't signed
anyway, it seems like you where able to flash the asus recovery?
can you boot it?
If so try booting it and tipe "adb reboot sideload" if everything goes well it should reboot and allow you to sideload unmodified (asus signed) .zips, do this
Also consider data wipe from recovery
Click to expand...
Click to collapse
1. I pressed power button + vol-up, ended up in "bootloader" menu.
2. Chose "Recovery mode"
3. At this point, on my laptop, I executed "adb reboot sideload" as you suggested.
However, I am prompted with an error that this device is unauthorized.
Code:
adb devices
List of devices attached
N...P unauthorized
How can I "authorize" this? When I had access to fully-booted system, I just needed to confirm some dialogue. Here there is no question.
Aww that's bad, I don't know how to allow a device from recovery, sorry.
Usually, if it worked under Android itself, it works in recovery as well.
Just to make sure, it worked under Android, right?
I assume u use a Linux system and I somehow had trouble under Linux, with adb and authorization
Yes, "adb" did work between my Linux system and phone before it gets stuck in this mode.
I managed to fix the problem by using a RAW image from romdevelopers. Extracted the content of the zip file and executed "flashall_AFT.cmd" on a Windows machine with the right drivers installed.
For the record, these posts [1][2] are pretty close to what I did.
Thank you both for your support.
EDIT:
I converted the "flashall_AFT.cmd' to "flashall_AFT.sh", so I could be able to achieve the same on a Linux system. USE IT AT YOUR OWN RISK.