Problem solved
I saw a threads from oneplus for unlock bootloader, I tried that and hope can use dual sim on my T-Mobile phone.
https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-%28t-mobile-version%29"]https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-%28t-mobile-version%29
I follow those steps unlocked bootloader but dual sim function is not available, so I found another threads shows dual sim is ready to use.
So I just follow his steps then ...... Phone always go recovery mode first, then reboot to initial welcome screen. It automatically turn off less than three sec.
I have no idea hoe fix that. If I just need official Rom in future, how can I fix that?
https://forums.oneplus.com/threads/no-longer-waiting-for-t-mobile-updates.942145/"]https://forums.oneplus.com/threads/no-longer-waiting-for-t-mobile-updates.942145/
{
"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"
}
This is what shows on CMD
I also tried wipe data, format devise in recovery, it not works
C:\>cd fastboot
C:\FASTBOOT>flash-all.bat
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.293s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.044s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2860 MB) to disk... took 21.514s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 9.014s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 28835840 4k blocks and 7223040 inodes
Filesystem UUID: 50d507d8-9c77-11e9-857c-a19626331dd2
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: f5f0ba62
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot_a' (65536 KB)...
OKAY [ 1.886s]
writing 'boot_a'...
OKAY [ 0.287s]
sending 'dtbo' (8192 KB)...
OKAY [ 0.239s]
writing 'dtbo'...
OKAY [ 0.106s]
erasing 'system_a'...
OKAY [ 0.143s]
sending sparse 'system_a' 1/6 (524284 KB)...
OKAY [ 15.506s]
writing 'system_a' 1/6...
OKAY [ 0.003s]
sending sparse 'system_a' 2/6 (499286 KB)...
OKAY [ 17.704s]
writing 'system_a' 2/6...
OKAY [ 0.003s]
sending sparse 'system_a' 3/6 (519680 KB)...
OKAY [ 17.003s]
writing 'system_a' 3/6...
OKAY [ 0.004s]
sending sparse 'system_a' 4/6 (513053 KB)...
OKAY [ 17.302s]
writing 'system_a' 4/6...
OKAY [ 0.002s]
sending sparse 'system_a' 5/6 (522296 KB)...
OKAY [ 17.746s]
writing 'system_a' 5/6...
OKAY [ 0.004s]
sending sparse 'system_a' 6/6 (220472 KB)...
OKAY [ 8.681s]
writing 'system_a' 6/6...
OKAY [ 0.004s]
sending 'vbmeta' (4 KB)...
OKAY [ 6.543s]
writing 'vbmeta'...
OKAY [ 0.004s]
sending sparse 'vendor' 1/2 (523043 KB)...
OKAY [ 15.642s]
writing 'vendor' 1/2...
OKAY [ 0.004s]
sending sparse 'vendor' 2/2 (290984 KB)...
OKAY [ 11.753s]
writing 'vendor' 2/2...
OKAY [ 0.004s]
Setting current slot to 'a'...
OKAY [ 17.400s]
erasing 'userdata'...
OKAY [ 0.722s]
sending 'userdata' (5273 KB)...
OKAY [ 0.156s]
writing 'userdata'...
OKAY [ 0.004s]
rebooting...
finished. total time: 148.965s
Press any key to exit...
Don't use Fastboot, use Qualcomm Snapdragon processor tool instead.
Fastbooted image don't wipe the modem firmware properly, instead you have bricked the modem. I found out why - the exact same thing happened to me, shuts down immediately after it gets to the welcome screen so I reflashed the phone with Qualcomm Snapdragon processor tool (it's in a thread covering the conversion of T-Mobile phone to international - https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 ), with a modified flasher software (which bypasses the checks on the phone). On the Pixel Experience ROM before I nuked the SSD with the Qualcomm Snapdragon processor tool from OnePlus, I found out why when I was struggling to fix it; wiped IMEI ID so SIM wasn't detected at all (my own fault, I wiped the /system without realizing that it would brick the modem).
Sent from my ONEPLUS 6T using Tapatalk
Dr. Mario said:
Don't use Fastboot, use Qualcomm Snapdragon processor tool instead.
Fastbooted image don't wipe the modem firmware properly, instead you have bricked the modem. I found out why - the exact same thing happened to me, shuts down immediately after it gets to the welcome screen so I reflashed the phone with Qualcomm Snapdragon processor tool (it's in a thread covering the conversion of T-Mobile phone to international - https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 ), with a modified flasher software (which bypasses the checks on the phone). On the Pixel Experience ROM before I nuked the SSD with the Qualcomm Snapdragon processor tool from OnePlus, I found out why when I was struggling to fix it; wiped IMEI ID so SIM wasn't detected at all (my own fault, I wiped the /system without realizing that it would brick the modem).
Sent from my ONEPLUS 6T using Tapatalk
Click to expand...
Click to collapse
It's back to normal and able show dual sim now.
Thanks, I spent more than 12 hrs for that, finally its back and even better.
Good, I am glad you got it fixed.
Sent from my ONEPLUS 6T using Tapatalk
Related
I manage to relock my XT925 Bootloader.
Process is very simple
THIS IS FOR WINDOWS ONLY!!!! Thanks @skeevydude
Warning!!!
The process will delete User Data so backup First.
Please do not attempt on XT926
Requirement
1. Original SBF/XML (latest recommended if available) get it here
2. Motorola Fastboot Get it here (taken from Moto G forum) Credit to the Owner
3. Motorola Device Manager (for drivers)
4. For Boot Logo Fix Please refer here
5. Flash script (Attached Below)
FASTBOOT STATUS WILL CHANGE FROM
Device is Unlocked Status Code: 3 To Device is Locked Status Code: 2
Steps
1. Download and extract the original SBF/XML
2. Download and extract the Motorola Fastboot.
3. Download and extract the Flash Script
4. Copy all the files from original SBF/XML to fastboot folder and also copy the flash script to fastboot folder
5. Put the phone into AP Fastboot Mode then execute the flash script "XT925_erase_userdata"
6. Wait until the flash process finish.
7. Now your bootloader is locked.
For Boot Logo Fix Please refer here
Please feel free to Edit/Delete the thread
Screenshot
{
"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"
}
Sent from my C6802 using Tapatalk
kumeipark said:
I manage to relock my XT925 Bootloader.
Process is very simple
Warning!!!
The process will delete User Data so backup First.
Please do not attempt on XT926
Requirement
1. Original SBF/XML (latest recommended if available) get it here
2. Motorola Fastboot Get it here (taken from Moto G forum) Credit to the Owner
3. Motorola Device Manager (for drivers)
4. For Boot Logo Fix Please refer here
5. Flash script (Attached Below)
FASTBOOT STATUS WILL CHANGE FROM
Device is Unlocked Status Code: 3 To Device is Locked Status Code: 2
Steps
1. Download and extract the original SBF/XML
2. Download and extract the Motorola Fastboot.
3. Download and extract the Flash Script
4. Copy all the files from original SBF/XML to fastboot folder and also copy the flash script to fastboot folder
5. Put the phone into AP Fastboot Mode then execute the flash script "XT925_erase_userdata"
6. Wait until the flash process finish.
7. Now your bootloader is locked.
For Boot Logo Fix Please refer here
Click to expand...
Click to collapse
so all that's necessary to type "mfastboot oem lock", or is the flash back to stock for safety reasons....listing steps isn't that helpful if the reasons aren't posted.
and have you tested "mfastboot oem unlock" or does the exploit need to be ran again to unlock the bootloader?
....shouldn't post about locking the bootloader without saying if it can be unlocked again or not.
EDIT:
And label or mention that this is for Windows Only
Check the flash script with notepad and I hope you will understand.
Please feel free to edit
Thanks
Sent from my C6802 using Tapatalk
kumeipark said:
Check the flash script with notepad and I hope you will understand.
Please feel free to edit
Thanks
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
Other than oem lock begin, it doesn't look that different than any other automated flashing setup. Basically, are those signed partitions necessary to lock the bootloader on this phone (Nexus 4 can fastboot oem lock while running CM), or would a fastbooted factory reset good enough to lock the phone running a custom rom? And can the phone be unlocked, exploit, fastboot, or other, after doing this -- I think that's the most important question.
Not trying to nitpick or whatever, but some of my questions are important to know before doing something like intentionally locking the bootloader w/o knowing if it can unlock again or not (I assume it can, but still, it would be nice to have that confirmed before doing this...not that I am, I don't even have a 925...but I do get asked a lot of questions about every single 8960 phone...it's what happens when you're a helpful RC)
skeevydude said:
Other than oem lock begin, it doesn't look that different than any other automated flashing setup. Basically, are those signed partitions necessary to lock the bootloader on this phone (Nexus 4 can fastboot oem lock while running CM), or would a fastbooted factory reset good enough to lock the phone running a custom rom? And can the phone be unlocked, exploit, fastboot, or other, after doing this -- I think that's the most important question.
Not trying to nitpick or whatever, but some of my questions are important to know before doing something like intentionally locking the bootloader w/o knowing if it can unlock again or not (I assume it can, but still, it would be nice to have that confirmed before doing this...not that I am, I don't even have a 925...but I do get asked a lot of questions about every single 8960 phone...it's what happens when you're a helpful RC)
Click to expand...
Click to collapse
Yes you're right!
the only difference is the oem lock begin and oem lock.
You need those signed partitions
By the way you can unlock the bootloader again from motorola website.
Thanks for correcting me.
kumeipark said:
Yes you're right!
the only difference is the oem lock begin and oem lock.
You need those signed partitions
By the way you can unlock the bootloader again from motorola website.
Thanks for correcting me.
Click to expand...
Click to collapse
So basically this method should only be done by phones that can officially be unlocked by Motorola? Personally, I don't want to be the one that finds out a hack unlocked phone can't go from status 2 to status 3...but that's what random idiots who flash anything they see are for...(un)fortunately for us, there's a lot of them...
Seeing as how a ton of us are running hacked unlocked phones, including myself, and how not everyone here actually has a RAZR HD, including myself...anything discussing bootloaders and locking them needs to be well documented, if only to cover your ass when some dipcrap does this and screws their self. Though it does say XT925 in the thread title and don't do this on a 926 in the thread...
To clear all doubts I took the liberty to unlock my bootloader after relocking it
Code:
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>mfastboot oem get_unlock_data
...
(bootloader) 3A24528415225372#54413234303032
(bootloader) 49523300000000000000000000#2144
(bootloader) 9FCE87F32A6179FAAA0D23AD8BCCF85
(bootloader) E5675#1660910902000100000011110
(bootloader) 0000000
OKAY [ 0.272s]
finished. total time: 0.273s
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>mfastboot oem unlock VZJUGTAYKHYZA5KXXXXX
...
(bootloader) Unlock completed! Wait to reboot
Now relocking again!
Code:
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>XT925_erase_userdata.bat
Flashing bootloader images ...
So as to use latest flash capabilities
...
(bootloader) Ready to flash signed images
OKAY [ 0.273s]
finished. total time: 0.274s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'partition' (32 KB)...
OKAY [ 0.012s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
OKAY [ 0.349s]
finished. total time: 0.364s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl1' (101 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.482s]
finished. total time: 0.500s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl2' (127 KB)...
OKAY [ 0.019s]
writing 'sbl2'...
OKAY [ 0.892s]
finished. total time: 0.913s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'sbl3' (512 KB)...
OKAY [ 0.046s]
writing 'sbl3'...
OKAY [ 1.076s]
finished. total time: 1.124s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'rpm' (140 KB)...
OKAY [ 0.023s]
writing 'rpm'...
OKAY [ 0.472s]
finished. total time: 0.496s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'tz' (192 KB)...
OKAY [ 0.024s]
writing 'tz'...
OKAY [ 0.495s]
finished. total time: 0.521s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'aboot' (256 KB)...
OKAY [ 0.029s]
writing 'aboot'...
OKAY [ 0.773s]
finished. total time: 0.804s
Flashing modem SW...
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'modem' (30720 KB)...
OKAY [ 2.278s]
writing 'modem'...
OKAY [ 1.160s]
sending 'modem' (17412 KB)...
OKAY [ 4.233s]
writing 'modem'...
OKAY [ 1.190s]
finished. total time: 8.865s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'fsg' (2852 KB)...
OKAY [ 0.218s]
writing 'fsg'...
OKAY [ 1.371s]
finished. total time: 1.591s
erasing 'modemst1'...
OKAY [ 0.770s]
finished. total time: 0.770s
erasing 'modemst2'...
OKAY [ 0.749s]
finished. total time: 0.750s
Flashing AP Images...
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'logo' (1709 KB)...
OKAY [ 0.134s]
writing 'logo'...
OKAY [ 1.429s]
finished. total time: 1.565s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.515s]
finished. total time: 0.564s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'boot' (10240 KB)...
OKAY [ 0.762s]
writing 'boot'...
OKAY [ 4.136s]
finished. total time: 4.900s
(bootloader) Variable not supported!
target max-download-size: 30MB
sending 'recovery' (10240 KB)...
OKAY [ 0.762s]
writing 'recovery'...
OKAY [ 3.165s]
finished. total time: 3.928s
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'system' (30720 KB)...
OKAY [ 2.275s]
writing 'system'...
OKAY [ 3.718s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.225s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.257s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.249s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.250s]
writing 'system'...
OKAY [ 1.359s]
sending 'system' (30720 KB)...
OKAY [ 5.235s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.227s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.246s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.256s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.240s]
writing 'system'...
OKAY [ 1.365s]
sending 'system' (30720 KB)...
OKAY [ 5.085s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.210s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.245s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.230s]
writing 'system'...
OKAY [ 1.359s]
sending 'system' (30720 KB)...
OKAY [ 5.238s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.241s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.259s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.247s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.234s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.248s]
writing 'system'...
OKAY [ 1.361s]
sending 'system' (30720 KB)...
OKAY [ 5.240s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.249s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.250s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (30720 KB)...
OKAY [ 5.219s]
writing 'system'...
OKAY [ 1.360s]
sending 'system' (4659 KB)...
OKAY [ 3.300s]
writing 'system'...
OKAY [ 0.641s]
finished. total time: 174.838s
(bootloader) Variable not supported!
target max-download-size: 30MB
Multi-Flash is enabled!
sending 'cdrom' (30720 KB)...
OKAY [ 2.274s]
writing 'cdrom'...
OKAY [ 3.178s]
sending 'cdrom' (22538 KB)...
OKAY [ 4.625s]
writing 'cdrom'...
OKAY [ 2.594s]
finished. total time: 12.675s
erasing 'tombstones'...
OKAY [ 0.905s]
finished. total time: 0.906s
erasing 'cache'...
OKAY [ 1.223s]
finished. total time: 1.224s
Erasing userdata...
erasing 'userdata'...
OKAY [ 4.437s]
finished. total time: 4.438s
Locking Bootloader...
...
FAILED (status read failed (Too many links))
finished. total time: 21.883s
All images flashed. Check logs for errors!
Press any key to continue . . .
C:\Users\xxxxx\Desktop\New folder\RAZR HD Fastboot>
While relocking bootloader it says
Code:
Locking Bootloader...
...
FAILED (status read failed (Too many links))
But the device will locked
Please note: Some text are altered for privacy concern
I thought the status code for locked was 0?
Sent from my RAZR HD using XDA Free mobile app
peladoro said:
I thought the status code for locked was 0?
Sent from my RAZR HD using XDA Free mobile app
Click to expand...
Click to collapse
Yes, I read in another forum about an user has "discovered this re-lock method", and asked in Motorola's forum about the status code and the meanings and the answer was something like this
Status code 0 =locked with warranty
Status code 3 = unlocked without warranty
Status code 2= relocked but also without warranty
And I don't remember very well if status code 1 is for developers edition phones and it means relocked but with warranty..
Enviado desde mi RAZR HD mediante Tapatalk
Thanks!
Thanks, man!
The outcome of the procedure was perfect! Thanks a lot!
I have only one question: After travarmos the device, we can update via OTA?
Hugs!
No issue on OTA with Locked or unlocked bootloader.
If rooted there's issue
Sent from my C6802 using Tapatalk
joaomanobrown said:
Thanks, man!
The outcome of the procedure was perfect! Thanks a lot!
I have only one question: After travarmos the device, we can update via OTA?
Hugs!
Click to expand...
Click to collapse
kumeipark said:
No issue on OTA with Locked or unlocked bootloader.
If rooted there's issue
Sent from my C6802 using Tapatalk
Click to expand...
Click to collapse
Yup, as @kumeipark stated, no issue with taking OTA just because you are unlocked.
Just remember, rooting is a software change on your phone, so that will mess up taking OTAs as you've modified the /system directory.
In the case of unlocking the bootloader, that is a physical change in the phone firmware itself. It does not modify the OS software in any way, hence the OTA will take since you didn't modify the OS in any way.
The reason the OTA's check for modification is to prevent bricking a device that may have modified the OS software in some way which could result in a device that boot loops. This way, they know for a fact that the software is either completely stock or it's been modified which means that the OTA cannot patch the software correctly, especially if some system files have been modified or removed altogether (or bloat apps as well).
Thanks!
Thank's guy's!
nice
Please, how do I unlock again ... at the motorola site was unable
HugoTJB said:
Please, how do I unlock again ... at the motorola site was unable
Click to expand...
Click to collapse
Previously how you unlock your BL??
Is your model XT925??
iBolski said:
Yup, as @kumeipark stated, no issue with taking OTA just because you are unlocked.
Just remember, rooting is a software change on your phone, so that will mess up taking OTAs as you've modified the /system directory.
In the case of unlocking the bootloader, that is a physical change in the phone firmware itself. It does not modify the OS software in any way, hence the OTA will take since you didn't modify the OS in any way.
The reason the OTA's check for modification is to prevent bricking a device that may have modified the OS software in some way which could result in a device that boot loops. This way, they know for a fact that the software is either completely stock or it's been modified which means that the OTA cannot patch the software correctly, especially if some system files have been modified or removed altogether (or bloat apps as well).
Click to expand...
Click to collapse
I read your post months ago before having my phone updated, and I read it now after having updated On The Air.
What do you mean with "will mess up taking OTA" exactly?
It goes without saying you can't get OTA updates if you're running on modified version of OS; but if you have an unlocked bootloader as mine and you are on an official motorola build, you can still get OTA and update them without problems.
Here's the story:
- bought my xt925 last year and it mounted the build 4.1.2 the one with the camera shutter always (and forced) on, by the grace of American lawmakers (I am in Italy);
- since the 4.1.2 is slow as hell, I unlocked the bootloader early in january this year and put on the cyanogen something;
- I tried the cyanogen mod for two months then I flashed back this one: Android 4.1.2
Blur_Version.98.21.26002.XT925.Orange.en.GB
- on october 7th I got the OTA message to uptade to kitkat 4.4.2, then I updated the phone and now I am working on 4.4.2.
There are a couple of things I don't get: how do I relock bootloader without flashing 4.1.2 and what happens if I do a factory reset from recovery.
Graf Schmidt said:
I read your post months ago before having my phone updated, and I read it now after having updated On The Air.
What do you mean with "will mess up taking OTA" exactly?
It goes without saying you can't get OTA updates if you're running on modified version of OS; but if you have an unlocked bootloader as mine and you are on an official motorola build, you can still get OTA and update them without problems.
Here's the story:
- bought my xt925 last year and it mounted the build 4.1.2 the one with the camera shutter always (and forced) on, by the grace of American lawmakers (I am in Italy);
- since the 4.1.2 is slow as hell, I unlocked the bootloader early in january this year and put on the cyanogen something;
- I tried the cyanogen mod for two months then I flashed back this one: Android 4.1.2
Blur_Version.98.21.26002.XT925.Orange.en.GB
- on october 7th I got the OTA message to uptade to kitkat 4.4.2, then I updated the phone and now I am working on 4.4.2.
There are a couple of things I don't get: how do I relock bootloader without flashing 4.1.2 and what happens if I do a factory reset from recovery.
Click to expand...
Click to collapse
Uh, reflashing doesn't lock the boot loader. Also, I never said you can't take an OTA with an unlocked bootloader. I said you won't be able to take an OTA if you are rooted, since that messes with the system files.
As you know, you unlock the XT925 via the Moto tools. As for relocking it, I have no idea. I do know with the Nexus 7, flashing a new image doesn't relock it. I have to actually do it via the ADB command, so I believe it's the same thing with the XT925. You get an unlock code from Motorola and you use that to unlock the bootloader and have to use the command to relock it.
Doing a factory reset won't relock it.
Looks like mfastboot check patitions checksum/size with GPT partition (patition_signed)
Sent from my XT925 using Tapatalk
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
as far as i can see,you have flashed system.img and he work,now try again to flash via adb only system.img,wen is done,run command fastboot reboot an remove usb cable from phone and press and hold on volume button up to enter in recovery mod,once in recovery wipe data factory reset and wipe cache,it wiil delete all your memory phone,but it my work,so good luck
Hello Cristi,
Thank you for reply, i will try to flash only with system.img and then reboot.
Then I'll come back with the result.
There any other method to flash full memory ? (e.g. with SP_Flash_Tool ) Delete all data and then complete installation with full fw?
Bad News,
After I flash adb only with system.img and then reboot, push volume + & power, only light red light flashing slower.
Is possible that the bottom Volume UP, may not work
Do you have a NAND backup through TWRP?
What FW are you trying to flash?
What happened so that it shows this?
Try to flash with other version ... try to flash with b170
@ - Hello oziboy;
I don`t have a backup and i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common));
I don`t know the history .... the device has got to me so broken
@ - Hello VladHD;
i will try , thk for info.
Hi....
try first to flash with fastboot firmware b049 or b052,
when finished flashing then factory reset and wipe....
then local update 171 or 170....
ingerul_danutz said:
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
Click to expand...
Click to collapse
you can try here http://forum.xda-developers.com/p8lite/general/guide-debranding-converting-single-sim-t3305977
I did get another motherboard, and now the phone is total functional.
K
Sent from my ALE-L21 using XDA-Developers mobile app
ingerul_danutz said:
Hello to all,
I have Huawei P8 Lite ALE-L21 device, for that i don`t know his history, but the present like that:
When i press power bottom, only red light flashing.
When i plug into charger or computer, the huawei logo appear, red light flashing and then restart;
The bootload was locked, but with your help (thank you vvvery much) from here, I succeeded to unlock;
Build number: ALE-L21C432B171;
Until now, i tray to flash with files from (ALE-L21C432B171(Single-SIM eu common))
Code:
G:\b171>fastboot devices
QLF7N15908016412 fastboot
G:\b171>fastboot flash boot boot.img
target reported max download size of 471859200 bytes
sending 'boot' (22796 KB)...
OKAY [ 0.507s]
writing 'boot'...
OKAY [ 0.668s]
finished. total time: 1.177s
G:\b171>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (31630 KB)...
OKAY [ 0.722s]
writing 'recovery'...
OKAY [ 0.919s]
finished. total time: 1.641s
G:\b171>fastboot flash cust cust.img
target reported max download size of 471859200 bytes
sending 'cust' (244905 KB)...
OKAY [ 5.429s]
writing 'cust'...
OKAY [ 4.171s]
finished. total time: 9.602s
G:\b171>fastboot flash system system.img
error: cannot load 'system.img'
G:\b171>mfastboot flash system system.img
target max-download-size: 450MB
Sparse-Flash is enabled!
sending sparse 'system' (460798 KB)...
OKAY [ 20.512s]
writing 'system'...
OKAY [ 7.788s]
sending sparse 'system' (459817 KB)...
OKAY [ 16.610s]
writing 'system'...
OKAY [ 7.650s]
sending sparse 'system' (455971 KB)...
OKAY [ 16.108s]
writing 'system'...
OKAY [ 7.608s]
sending sparse 'system' (444362 KB)...
OKAY [ 15.639s]
writing 'system'...
OKAY [ 7.452s]
sending sparse 'system' (460302 KB)...
OKAY [ 15.998s]
writing 'system'...
OKAY [ 7.751s]
sending sparse 'system' (49397 KB)...
OKAY [ 1.733s]
writing 'system'...
OKAY [ 0.837s]
finished. total time: 125.740s
G:\b171>fastboot reboot
rebooting...
finished. total time: 0.022s
But after restart nothing happened, red light is flashing.
I put on sd-card//dload/update.app, and push simultaneous Volume + / - / power, the red flash flashing slower, and the screen is black.
Any ideas ?
Click to expand...
Click to collapse
My p8lite phone also soft bricked can you tell how did you unlocked your boot loader?
I use this method:
- Open Huawei Product ID Generator, then complete:
Product Model: U8815,
Product IMEI: imei from sim1;
and now you have Product ID generated;
now, Connect your phone via data cable to PC;
Switch it off and then by pressing volume down and power together make it in fastboot mode (in this mode you will see "Phone locked" in green color at bottom of screen)
- enter https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail login with ID facebook or create an account; and then complete with:
Product Model: U8815 - like Huawei Product ID Generator;
Product Serial Number: 16 characters ; will be found on the box of device or type command "fastboot devices", when you connect the phone in fastboot mode (volume down + power botton);
Product IMEI: imei from sim1 ;
Product ID: the code generated from Huawei Product ID Generator program;
Verification code: characters from picture;
and then submit; if everything is OK, the code will be generated;
type command: "fastboot oem unlock **************** "
where ************** is code generated on emui.huawei.com;
Good luck
ingerul_danutz said:
I did get another motherboard, and now the phone is total functional.
Click to expand...
Click to collapse
Where did you buy new motherboard?
I went to restore the Recovery OS Image so i can update to the latest OS version (i couldn't update since I was rooted). Everything went well until i was flashing the system.img file.
target reported max download s
erasing 'system'...
OKAY [ 0.758s]
sending sparse 'system' (62437
OKAY [ 1.775s]
writing 'system'...
OKAY [ 2.737s]
sending sparse 'system' (62993
OKAY [ 1.812s]
writing 'system'...
OKAY [ 2.660s]
sending sparse 'system' (65443
OKAY [ 1.996s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (65512
OKAY [ 1.854s]
writing 'system'...
OKAY [ 2.726s]
sending sparse 'system' (65532
OKAY [ 1.869s]
writing 'system'...
OKAY [ 2.654s]
sending sparse 'system' (63893
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.712s]
sending sparse 'system' (58260
OKAY [ 1.637s]
writing 'system'...
OKAY [ 2.377s]
sending sparse 'system' (59088
OKAY [ 1.683s]
writing 'system'...
OKAY [ 2.434s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.756s]
sending sparse 'system' (64176
OKAY [ 1.818s]
writing 'system'...
OKAY [ 2.560s]
sending sparse 'system' (58956
OKAY [ 1.674s]
writing 'system'...
OKAY [ 2.405s]
sending sparse 'system' (65532
OKAY [ 1.833s]
writing 'system'...
OKAY [ 2.613s]
sending sparse 'system' (60898
OKAY [ 1.752s]
writing 'system'...
OKAY [ 2.700s]
sending sparse 'system' (62455
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.767s]
sending sparse 'system' (65532
OKAY [ 1.865s]
writing 'system'...
OKAY [ 2.727s]
sending sparse 'system' (65532
OKAY [ 1.858s]
writing 'system'...
OKAY [ 2.699s]
sending sparse 'system' (61848
OKAY [ 1.764s]
writing 'system'...
OKAY [ 2.664s]
sending sparse 'system' (61428
OKAY [ 1.746s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (65532
OKAY [ 1.853s]
writing 'system'...
OKAY [ 2.764s]
sending sparse 'system' (65533
OKAY [ 1.881s]
writing 'system'...
OKAY [ 2.707s]
sending sparse 'system' (63217
OKAY [ 1.817s]
writing 'system'...
OKAY [ 2.680s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.786s]
sending sparse 'system' (65053
OKAY [ 1.914s]
writing 'system'...
OKAY [ 2.983s]
sending sparse 'system' (65538
FAILED (remote: data too large
finished. total time: 104.455s
How can this fail if it's an official method? Anybody have any idea?
I managed to get my device back to 5.1 by installing with twrp the zip from this post https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
the script will have errors but it will boot the system afterwards. It also fails in updating to 5.2.
same issue here nvidia is really pissing me off
You need to limit the chunk size like so:
Code:
fastboot -S 50M flash system system.img
rodalpho said:
You need to limit the chunk size like so:
Code:
fastboot -S 50M flash system system.img
Click to expand...
Click to collapse
For me that works by limiting chunk size. But after flashing and reboot I get "No command" or gets stuck on Logo Screen NVIDIA
Did you flash vendor.img afterwards? I try re-flashing the entire series from flash-all.sh in sequence. To get back to fastboot mode, try Nvidia's hardware instructions here.
http://developer.download.nvidia.co...ATV_2017/5.0.0/HowTo-Flash-Recovery-Image.txt
pendragon666 said:
I went to restore the Recovery OS Image so i can update to the latest OS version (i couldn't update since I was rooted). Everything went well until i was flashing the system.img file.
target reported max download s
erasing 'system'...
OKAY [ 0.758s]
sending sparse 'system' (62437
OKAY [ 1.775s]
writing 'system'...
OKAY [ 2.737s]
sending sparse 'system' (62993
OKAY [ 1.812s]
writing 'system'...
OKAY [ 2.660s]
sending sparse 'system' (65443
OKAY [ 1.996s]
writing 'system'...
OKAY [ 3.211s]
sending sparse 'system' (65512
OKAY [ 1.854s]
writing 'system'...
OKAY [ 2.726s]
sending sparse 'system' (65532
OKAY [ 1.869s]
writing 'system'...
OKAY [ 2.654s]
sending sparse 'system' (63893
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.712s]
sending sparse 'system' (58260
OKAY [ 1.637s]
writing 'system'...
OKAY [ 2.377s]
sending sparse 'system' (59088
OKAY [ 1.683s]
writing 'system'...
OKAY [ 2.434s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.756s]
sending sparse 'system' (64176
OKAY [ 1.818s]
writing 'system'...
OKAY [ 2.560s]
sending sparse 'system' (58956
OKAY [ 1.674s]
writing 'system'...
OKAY [ 2.405s]
sending sparse 'system' (65532
OKAY [ 1.833s]
writing 'system'...
OKAY [ 2.613s]
sending sparse 'system' (60898
OKAY [ 1.752s]
writing 'system'...
OKAY [ 2.700s]
sending sparse 'system' (62455
OKAY [ 1.814s]
writing 'system'...
OKAY [ 2.767s]
sending sparse 'system' (65532
OKAY [ 1.865s]
writing 'system'...
OKAY [ 2.727s]
sending sparse 'system' (65532
OKAY [ 1.858s]
writing 'system'...
OKAY [ 2.699s]
sending sparse 'system' (61848
OKAY [ 1.764s]
writing 'system'...
OKAY [ 2.664s]
sending sparse 'system' (61428
OKAY [ 1.746s]
writing 'system'...
OKAY [ 2.472s]
sending sparse 'system' (65532
OKAY [ 1.853s]
writing 'system'...
OKAY [ 2.764s]
sending sparse 'system' (65533
OKAY [ 1.881s]
writing 'system'...
OKAY [ 2.707s]
sending sparse 'system' (63217
OKAY [ 1.817s]
writing 'system'...
OKAY [ 2.680s]
sending sparse 'system' (65533
OKAY [ 1.872s]
writing 'system'...
OKAY [ 2.786s]
sending sparse 'system' (65053
OKAY [ 1.914s]
writing 'system'...
OKAY [ 2.983s]
sending sparse 'system' (65538
FAILED (remote: data too large
finished. total time: 104.455s
How can this fail if it's an official method? Anybody have any idea?
I managed to get my device back to 5.1 by installing with twrp the zip from this post https://forum.xda-developers.com/shield-tv/general/shield-tv-2015-ota-5-1-feb-17-zip-file-t3559062
the script will have errors but it will boot the system afterwards. It also fails in updating to 5.2.
Click to expand...
Click to collapse
I would advise you to quickly download DRM Info from the PlayStore, If you can, and verify you still have Widevine L1 Status. It might not be a big deal if you don't use Netflix, or Amazon. But other outfits like NBC which is free, also use this to protect their Content, and will prevent you from viewing such if your not in compliance.
I know this as I myself got into the same but of trouble between Experience 3.x, and 5.x on my Pro. I managed to get a different Device, and have since made a backup of first few Partitions of my SSHD on my Shield to cover my ass in the eventual case that it should ever happen again.
Though I'm not sure how that's going to be relevant info for a 16Gb eMMC user though.
The flashing worked with chunk limiting.
I think my updating failed after i flashed that zip i mentioned in the first post because of wrong keys. When i flashed the update with twrp it said something along those lines and failed.
Everything back to normal now.
Thanks for the solution.
I had to sparse system and vendor images with -S 50M to get it to work.
So i've tried pretty much every tutorial out there and tried baking my phone and hitting it with a heat gun, 4core boot img,
my bootloader is unlocked and im able to flash any factory image onto the device but the outcome is the same where its stuck on the google screen.
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.107s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.310s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.031s
< waiting for any device >
target reported max download size of 494927872 bytes
sending 'radio' (48472 KB)...
OKAY [ 1.156s]
writing 'radio'...
OKAY [ 2.156s]
finished. total time: 3.312s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.063s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (12 MB) to disk... took 0.047s
archive does not contain 'recovery.sig'
extracting system.img (1923 MB) to disk... took 14.723s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (180 MB) to disk... took 1.453s
archive does not contain 'vendor.sig'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: 15015e2a-3b5f-11e8-a195-95614c87b792
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
wiping cache...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: angler-02.45
Baseband Version.....: angler-02.50
Serial Number........: 84B5T15C05003502
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (12045 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (12981 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.406s]
sending sparse 'system' 1/5 (463062 KB)...
OKAY [ 10.660s]
writing 'system' 1/5...
OKAY [ 6.468s]
sending sparse 'system' 2/5 (466961 KB)...
OKAY [ 10.882s]
writing 'system' 2/5...
OKAY [ 6.759s]
sending sparse 'system' 3/5 (479253 KB)...
OKAY [ 11.297s]
writing 'system' 3/5...
OKAY [ 7.418s]
sending sparse 'system' 4/5 (481623 KB)...
OKAY [ 11.191s]
writing 'system' 4/5...
OKAY [ 6.764s]
sending sparse 'system' 5/5 (79148 KB)...
OKAY [ 1.902s]
writing 'system' 5/5...
OKAY [ 1.134s]
sending 'vendor' (185129 KB)...
OKAY [ 4.012s]
writing 'vendor'...
OKAY [ 2.973s]
erasing 'userdata'...
OKAY [ 0.313s]
sending 'userdata' (4412 KB)...
OKAY [ 0.141s]
writing 'userdata'...
OKAY [ 0.094s]
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (96 KB)...
OKAY [ 0.016s]
writing 'cache'...
OKAY [ 0.016s]
rebooting...
finished. total time: 84.571s
Press any key to exit...
fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-02.50
(bootloader) version-bootloader:angler-02.45
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15C05003502
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.187s
any suggestions would be appreciated.
onikii said:
So i've tried pretty much every tutorial out there and tried baking my phone and hitting it with a heat gun, 4core boot img,
my bootloader is unlocked and im able to flash any factory image onto the device but the outcome is the same where its stuck on the google screen.
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.107s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.310s
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.031s
< waiting for any device >
target reported max download size of 494927872 bytes
sending 'radio' (48472 KB)...
OKAY [ 1.156s]
writing 'radio'...
OKAY [ 2.156s]
finished. total time: 3.312s
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (11 MB) to disk... took 0.063s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (12 MB) to disk... took 0.047s
archive does not contain 'recovery.sig'
extracting system.img (1923 MB) to disk... took 14.723s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (180 MB) to disk... took 1.453s
archive does not contain 'vendor.sig'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: 15015e2a-3b5f-11e8-a195-95614c87b792
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
wiping cache...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...: angler-02.45
Baseband Version.....: angler-02.50
Serial Number........: 84B5T15C05003502
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
checking version-baseband...
OKAY [ 0.016s]
sending 'boot' (12045 KB)...
OKAY [ 0.297s]
writing 'boot'...
OKAY [ 0.172s]
sending 'recovery' (12981 KB)...
OKAY [ 0.297s]
writing 'recovery'...
OKAY [ 0.203s]
erasing 'system'...
OKAY [ 0.406s]
sending sparse 'system' 1/5 (463062 KB)...
OKAY [ 10.660s]
writing 'system' 1/5...
OKAY [ 6.468s]
sending sparse 'system' 2/5 (466961 KB)...
OKAY [ 10.882s]
writing 'system' 2/5...
OKAY [ 6.759s]
sending sparse 'system' 3/5 (479253 KB)...
OKAY [ 11.297s]
writing 'system' 3/5...
OKAY [ 7.418s]
sending sparse 'system' 4/5 (481623 KB)...
OKAY [ 11.191s]
writing 'system' 4/5...
OKAY [ 6.764s]
sending sparse 'system' 5/5 (79148 KB)...
OKAY [ 1.902s]
writing 'system' 5/5...
OKAY [ 1.134s]
sending 'vendor' (185129 KB)...
OKAY [ 4.012s]
writing 'vendor'...
OKAY [ 2.973s]
erasing 'userdata'...
OKAY [ 0.313s]
sending 'userdata' (4412 KB)...
OKAY [ 0.141s]
writing 'userdata'...
OKAY [ 0.094s]
erasing 'cache'...
OKAY [ 0.031s]
sending 'cache' (96 KB)...
OKAY [ 0.016s]
writing 'cache'...
OKAY [ 0.016s]
rebooting...
finished. total time: 84.571s
Press any key to exit...
fastboot getvar all
(bootloader) version:0.01
(bootloader) unlocked:yes
(bootloader) hardware-revision:ANGLER-VN2
(bootloader) version-baseband:angler-02.50
(bootloader) version-bootloader:angler-02.45
(bootloader) display-panel:
(bootloader) charger-screen-enabled:0
(bootloader) max-download-size: 0x1d800000
(bootloader) partition-type:cache:ext4
(bootloader) partition-size:cache: 0x6400000
(bootloader) partition-type:userdata:ext4
(bootloader) partition-size:userdata: 0x66257ee00
(bootloader) partition-type:system:ext4
(bootloader) partition-size:system: 0xc0000000
(bootloader) serialno:84B5T15C05003502
(bootloader) kernel:lk
(bootloader) product:angler
all:
finished. total time: 0.187s
any suggestions would be appreciated.
Click to expand...
Click to collapse
Did you flash the special kernel that shuts off half of the CPU cores. If you were bootloop was because of the hardware issue then that is your only fix
Sent from my Nexus 6P using Tapatalk
funnel71 said:
Did you flash the special kernel that shuts off half of the CPU cores. If you were bootloop was because of the hardware issue then that is your only fix
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I flashed 7.1.2 angler-n2g48b factory image to the nexus then I flashed the 4 core boot img fix along with twrp 4 core as well.
I'm unable to get into recovery and the boot fix did not work as its still stuck at the google screen for the last 2 hours.
onikii said:
I flashed 7.1.2 angler-n2g48b factory image to the nexus then I flashed the 4 core boot img fix along with twrp 4 core as well.
I'm unable to get into recovery and the boot fix did not work as its still stuck at the google screen for the last 2 hours.
Click to expand...
Click to collapse
I am having the same issues and also tried the steps in this post with no luck.
https://forum.xda-developers.com/showpost.php?p=75774448&postcount=2289
{
"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"
}
We are very excited to announce Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* You tell us
Requirements
Make sure you've latest platform tools for Android.
Download
You can always get our builds from our website Paranoid Android website
Note: Custom kernels are NOT supported the kernel says it supports PA and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Paranoid Android Topaz released
Instructions
Unlock your bootloader, and in bootloader mode follow the next command
fastboot update aospa-topaz-alpha-*-image.zip
After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)
Kernel source.
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!
Reserved
Reserved
hell yeah
Thanks a lot for your hard work and to all those who contributed!
herna said:
View attachment 5735149
We are very excited to announce the alpha of Paranoid Android Topaz, based on Android 13.
On the first launch, you’ll notice a clean setup with beautiful wallpapers from Hampus Olsson, who teamed up with us again to create several beautiful pieces of artwork. Hampus is a multi-disciplinary artist whose design stands for itself and we’re glad to have him onboard. We also added further UI touches that we believe enhance the overall user experience. You can find all of the Paranoid Android wallpapers and many more in the Abstruct app from the PlayStore.
Our builds are based on the Code Linaro Organization Android base, which is optimized for Qualcomm platforms and has a higher degree of performance, battery life, and functionality compared to the Android Open Source Project platform. The Paranoid Android team and contributors are focusing on squashing existing bugs, and implementing and improving features, performance, and stability. We are dedicated to providing a user experience with the stability that you can expect from stock ROMs with best-in-class performance and features to help you get the most out of your device.
Notice
We kindly ask all of you that are in a position to donate anything, to help and support us so we can provide better and faster build releases, as well as increase the download speed of our servers, all looking for your enjoyment.
You can donate on the link below:
Donate
Device-specific issues
* Some carriers might indicate 4G on the status bar when it's actually 5G.
* LDAC playback is broken.
* Some HDR videos might lag after a few seconds of playing.
* Small freeze at bootanimation.
Requirements
Make sure you've latest stable firmware flashed on both slots before flashing the ROM.
Download
You can always get our Alpha builds from our website Paranoid Android website
Note: Custom kernels are NOT supported the kernel says it supports PA and GMS is included!
Changelogs
Keep an eye on our Twitter account, @paranoidaospa, as we will be posting about new features getting included in the release builds, as well as links to betas for those devices that will get them. For more detailed information please have a look at the second post of this thread of each build changelog on the website.
Paranoid Android Topaz released
Instructions
Unlock your bootloader, and in bootloader mode follow the next command
fastboot update aospa-topaz-alpha-*-image.zip
After the reboot, factory reset the device (only required for the first time you flash Paranoid Android)
Important / Useful links
Paranoid Android Twitter
Paranoid Android Channel (Telegram)
Paranoid Android Download Channel (Telegram)
Paranoid Android Community (Telegram)
Cheers and #StayParanoid!
Click to expand...
Click to collapse
After a try, "archive does not contain android-info.txt"
The long awaited release. Can't wait to flash it after work
AntoXik72 said:
After a try, "archive does not contain android-info.txt"
Click to expand...
Click to collapse
You need to flash the file that ends in -image.zip
Search for fastboot button on the website, or download -image.zip from Telegram or mirror.
herna said:
You need to flash the file that ends in -image.zip
Search for fastboot button on the website, or download -image.zip from Telegram or mirror.
Click to expand...
Click to collapse
Gotcha, flashed it, perfectly working, thanks again
Flash day, easy step
Will feedback soon
Thanks for the job PA Team, first custom rom for the Nothing 1, congratulation
Code:
c:\Android>fastboot update aospa-topaz-alpha-1-phone1-20221015-image.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 8xxxxxxx
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.003s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (96 MB) to disk... took 0.510s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 2.764s]
Writing 'boot_a' OKAY [ 0.189s]
extracting dtbo.img (24 MB) to disk... took 0.066s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.653s]
Writing 'dtbo' OKAY [ 0.044s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.002s]
Writing 'vbmeta_system' OKAY [ 0.001s]
archive does not contain 'vbmeta_vendor.img'
extracting vendor_boot.img (96 MB) to disk... took 0.236s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot' (98304 KB) OKAY [ 2.632s]
Writing 'vendor_boot' OKAY [ 0.224s]
extracting super_empty.img (0 MB) to disk... took 0.001s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.018s]
Resizing 'odm_a' OKAY [ 0.004s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.005s]
Resizing 'system_ext_a' OKAY [ 0.005s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
extracting odm.img (1 MB) to disk... took 0.015s
archive does not contain 'odm.sig'
Resizing 'odm_a' OKAY [ 0.005s]
Sending 'odm_a' (1568 KB) OKAY [ 0.046s]
Writing 'odm_a' OKAY [ 0.100s]
archive does not contain 'odm_dlkm.img'
extracting product.img (1786 MB) to disk... took 10.701s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.004s]
Sending sparse 'product_a' 1/7 (262116 KB) OKAY [ 7.639s]
Writing 'product_a' OKAY [ 0.457s]
Sending sparse 'product_a' 2/7 (262124 KB) OKAY [ 7.709s]
Writing 'product_a' OKAY [ 0.370s]
Sending sparse 'product_a' 3/7 (262124 KB) OKAY [ 7.737s]
Writing 'product_a' OKAY [ 0.359s]
Sending sparse 'product_a' 4/7 (262128 KB) OKAY [ 7.720s]
Writing 'product_a' OKAY [ 0.353s]
Sending sparse 'product_a' 5/7 (262116 KB) OKAY [ 7.702s]
Writing 'product_a' OKAY [ 0.378s]
Sending sparse 'product_a' 6/7 (262140 KB) OKAY [ 7.732s]
Writing 'product_a' OKAY [ 0.425s]
Sending sparse 'product_a' 7/7 (250948 KB) OKAY [ 7.396s]
Writing 'product_a' OKAY [ 0.459s]
extracting system.img (930 MB) to disk... took 8.265s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.005s]
Sending sparse 'system_a' 1/4 (262108 KB) OKAY [ 7.615s]
Writing 'system_a' OKAY [ 0.446s]
Sending sparse 'system_a' 2/4 (262124 KB) OKAY [ 7.719s]
Writing 'system_a' OKAY [ 0.437s]
Sending sparse 'system_a' 3/4 (262108 KB) OKAY [ 7.675s]
Writing 'system_a' OKAY [ 0.449s]
Sending sparse 'system_a' 4/4 (163116 KB) OKAY [ 4.804s]
Writing 'system_a' OKAY [ 0.341s]
extracting system_ext.img (565 MB) to disk... took 4.734s
Invalid sparse file format at header magic
archive does not contain 'system_ext.sig'
Resizing 'system_ext_a' OKAY [ 0.004s]
Sending sparse 'system_ext_a' 1/3 (262116 KB) OKAY [ 7.693s]
Writing 'system_ext_a' OKAY [ 0.466s]
Sending sparse 'system_ext_a' 2/3 (262140 KB) OKAY [ 7.501s]
Writing 'system_ext_a' OKAY [ 0.458s]
Sending sparse 'system_ext_a' 3/3 (53124 KB) OKAY [ 1.586s]
Writing 'system_ext_a' OKAY [ 0.247s]
archive does not contain 'system_other.img'
extracting vendor.img (840 MB) to disk... took 7.566s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.004s]
Sending sparse 'vendor_a' 1/4 (262096 KB) OKAY [ 7.724s]
Writing 'vendor_a' OKAY [ 0.462s]
Sending sparse 'vendor_a' 2/4 (262124 KB) OKAY [ 7.716s]
Writing 'vendor_a' OKAY [ 0.437s]
Sending sparse 'vendor_a' 3/4 (262140 KB) OKAY [ 7.718s]
Writing 'vendor_a' OKAY [ 0.439s]
Sending sparse 'vendor_a' 4/4 (71624 KB) OKAY [ 2.118s]
Writing 'vendor_a' OKAY [ 0.226s]
archive does not contain 'vendor_dlkm.img'
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 0.000s]
Finished. Total time: 189.064s
c:\Android>
PA 13 ON ^^
Yes Baby
Want to flash this as I've been looking forward to this for a while. But it's my single use device so I am telling myself to wait till it's out of alpha
@herna
Thanks a lot for Paranoid Android A13
Support for german users
Dashboard - LOS-Legacy®Deine Android Community
How can I use "fastboot erase system" for clean system partition?
Some Screenshots for curious people
1st Feedback, especialy for users want keep N1P Stack Features / Apps, READ BEFORE :
Good points :
+ A13
+ Smooth, really a true Android Pure experience
+ Pixel Lovers you will be happy
+ Beautiful AoD
+ Bluetooth, Dual SIM, Geolocalisation+ working fine
+ NOTHING Camera Working perfectly (but only the v12.0.00.98.03 (first release)]
Bad points :
- No LDAC Audio but also no APTX and others, using apparently AAC by default (don't care in my case, my headset don't using)
- No Glyth for Ringtones/Notifications (Only settings for charging/Battery level)
- Some random visual Glitch / Artifact
- Camera is complete but really basical, there a lot features missing in comparaison N1P Camera Stock (BUT Read in Good points, NOTHING Camera can be installed!)
How to make sure that i have latest firmware on both slots?
xtcislove said:
How to make sure that i have latest firmware on both slots?
Click to expand...
Click to collapse
You don't have to, I flashed this on 1.1.3 update, working fine.
Dunno if it's a bug or not but fastboot button on website downloads non -image.zip version. Downloaded from telegram and it's all good. Thanks!
Awesome build. But far from complete guys. Only flashed it because of A13
fastboot update aospa-topaz-alpha-1-phone1-20221015-image.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 32c1a920
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.003s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (96 MB) to disk... took 0.272s
archive does not contain 'boot.sig'
Sending 'boot_a' (98304 KB) OKAY [ 3.159s]
Writing 'boot_a' OKAY [ 0.187s]
extracting dtbo.img (24 MB) to disk... took 0.036s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.780s]
Writing 'dtbo' OKAY [ 0.037s]
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.002s]
Writing 'vbmeta' OKAY [ 0.007s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.007s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Sending 'super' (4 KB) OKAY [ 0.001s]
Updating super partition OKAY [ 0.019s]
Resizing 'odm_a' OKAY [ 0.004s]
Resizing 'product_a' OKAY [ 0.004s]
Resizing 'system_a' OKAY [ 0.004s]
Resizing 'system_b' OKAY [ 0.004s]
Resizing 'vendor_a' OKAY [ 0.004s]
Resizing 'vendor_b' OKAY [ 0.004s]
archive does not contain 'boot_other.img'
extracting odm.img (1 MB) to disk... took 0.006s
archive does not contain 'odm.sig'
Resizing 'odm_a' OKAY [ 0.005s]
Sending 'odm_a' (1568 KB) OKAY [ 0.044s]
Writing 'odm_a' OKAY [ 0.103s]
extracting product.img (1786 MB) to disk... took 5.427s
Invalid sparse file format at header magic
archive does not contain 'product.sig'
Resizing 'product_a' OKAY [ 0.005s]
Sending sparse 'product_a' 1/7 (262116 KB) OKAY [ 8.959s]
Writing 'product_a' OKAY [ 0.457s]
Sending sparse 'product_a' 2/7 (262124 KB) OKAY [ 8.286s]
Writing 'product_a' OKAY [ 0.430s]
Sending sparse 'product_a' 3/7 (262124 KB) OKAY [ 8.747s]
Writing 'product_a' OKAY [ 0.440s]
Sending sparse 'product_a' 4/7 (262128 KB) OKAY [ 8.190s]
Writing 'product_a' OKAY [ 0.438s]
Sending sparse 'product_a' 5/7 (262116 KB) OKAY [ 8.791s]
Writing 'product_a' OKAY [ 0.441s]
Sending sparse 'product_a' 6/7 (262140 KB) OKAY [ 8.600s]
Writing 'product_a' OKAY [ 0.440s]
Sending sparse 'product_a' 7/7 (250948 KB) OKAY [ 8.109s]
Writing 'product_a' OKAY [ 0.419s]
archive does not contain 'product_services.img'
extracting system.img (930 MB) to disk... took 2.976s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Resizing 'system_a' OKAY [ 0.003s]
Sending sparse 'system_a' 1/4 (262108 KB) OKAY [ 8.350s]
Writing 'system_a' OKAY [ 0.456s]
Sending sparse 'system_a' 2/4 (262124 KB) OKAY [ 8.074s]
Writing 'system_a' OKAY [ 0.438s]
Sending sparse 'system_a' 3/4 (262108 KB) OKAY [ 8.665s]
Writing 'system_a' OKAY [ 0.455s]
Sending sparse 'system_a' 4/4 (163116 KB) OKAY [ 5.349s]
Writing 'system_a' OKAY [ 0.331s]
archive does not contain 'system_other.img'
extracting vendor.img (840 MB) to disk... took 2.663s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Resizing 'vendor_a' OKAY [ 0.005s]
Sending sparse 'vendor_a' 1/4 (262096 KB) OKAY [ 8.631s]
Writing 'vendor_a' OKAY [ 0.451s]
Sending sparse 'vendor_a' 2/4 (262124 KB) OKAY [ 8.849s]
Writing 'vendor_a' OKAY [ 0.434s]
Sending sparse 'vendor_a' 3/4 (262140 KB) OKAY [ 8.708s]
Writing 'vendor_a' OKAY [ 0.412s]
Sending sparse 'vendor_a' 4/4 (71624 KB) OKAY [ 2.444s]
Writing 'vendor_a' OKAY [ 0.152s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 0.000s]
Finished. Total time: 158.629s
reboot to fastboot mode
can someone help me
Looks pretty awesome, great work