Hi,
I tried to update to Android 4.2 (from 4.1.2) today, but it failed at the stock recovery saying:
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Screenshot: https://www.dropbox.com/s/b8lk0n147cbcfuv/20121114_121646_4_bestshot.jpg
Using Titanium Backup I used to make Google Books a Userland application and uninstalled it a while ago, because I wanted to remove some bloatware. I installed the backup I had and made it a system-application again, but its still giving me that error. Even factory reset didnt help.
What options do I have? How can I flash the full image?
Kind regards
Alex
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Same problem with apply_patch_check error bij update.
Also try to flash full factory image 4.2 by fastboot.
After install and reboot, Google icon in screen, doesn't startup.
That 5x but no success.
Same install with factory image 4.1.2 and no problem.
Help!
---------- Post added at 01:10 PM ---------- Previous post was at 01:02 PM ----------
Hello Alex,
You said, flashed bij Flash-all.bat.
How does that work? You may have a brief description of how you do it?
Thank you!
In the .zip you downloaded, there is a file called flash-all.bat. For example it does this for the WiFi version:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jop40c.zip
echo Press any key to exit...
pause >nul
exit
Check your version an run it in platform-tools with all content beeing there of course. Its quite easy
You sense about PATH I do not understand.
The rest I have indeed done in cmd
I have indeed PlatformTools and I have all five files in that folder.
Same folder where adb.exe also capable.
I've done in cmd in the platformtools path:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.13.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jop40c.zip
Then start the nexus7 but remains on the startup screen on the google logo.
Am I forgetting something?
whats the output of the fastboot commands from above?
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
simacca said:
I have the same problem but with GooglePinyinime.apk.
Have just worked out how to sideload using adb and am getting stuck on this error.
I did freeze this app using titanium pro, then unfroze it when I upgraded to 4.1.2 ota successfully, so can't understand why its pulling up an error now?
Am a bit of a noob with these commands so would be very grateful for any help.
Am on stock rom, rooted and no custom recovery.
Thanks.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Do you have fastboot installed on your computer? I am not in front of my development computer so I can't give you specific details but I had a several modifications to /system so I didn't bother trying to reverse them and instead flashed the original 4.1.2 system.img.
The (rough) procedure for this is:
1. Backup your current 4.1.2 rom in case you can't live with 4.2
2. Plug the nexus into your computer and boot into the bootloader (up vol + down vol + power)
3. On your computer, download the 4.1.2 factory image from https://dl.google.com/dl/android/aosp/nakasi-jzo54k-factory-973f190e.tgz
4. Unzip the image and then unzip the zip file that was inside the image (I can't remember the name but I believe there is only one)
5. If you unzipped everything correctly you should have a system.img file, open a command window and navigate to the directory that contains the system.img file and type:
Code:
fastboot flash system system.img
Sorry I don't have the specific details. If no one else has filled in the missing file names by the time I get home and you are comfortable with this procedure I will update this with the proper names.
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Nexus root toolkit works
Nexus root toolkit works like a champ for restoring stock if you need it.
Works flawlessly in windows 7 for me.
http://www.wugfresh.com/nrt/
The real issue with the the assert errors is that you changed something you should not have. The 4.2 update hash checks the original system apps for consistency. If you changed any of the System apps outside of an official update you get the assert errors when trying to flash the new update.
Have the same problem...
[..]
assert failed: apply_patch_check("/system/app/Books.apk", ........
Installation aborted.
Anyone manage ti fix it without restoring original rom would be nice....
alex2308 said:
Nevermind, I found the factory image at
https://developers.google.com/android/nexus/images#nakasijop40c
Downloaded it, did a titanium backup, flashed image via flash-all.bat, restored root, restored backup and 4.2 with root is all up and running now.
Click to expand...
Click to collapse
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
everyday_ said:
Hi Alex,
Did flashed factory image returned our Nexus like a new phone or just restoring system files? I want to flash factory image but afraid if it's like a factory reset
Click to expand...
Click to collapse
Its like a full factory reset, everything is gone (also the /sdcard folder with the downloads and stuff). Restoring was pretty easy, I copied the /sdcard stuff via USB to my computer and used titanium backup to backup the apps with settings (and copied that too to my computer). The only thing I had to setup again was WiFi, Homescreen and Email (although you can backup them via Titanium, which I didnt).
Mathijs17 said:
C:\android-sdk-windows\platform-tools>fastboot flash bootloader bootloader-group
er-4.13.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.290s]
writing 'bootloader'...
OKAY [ 1.252s]
finished. total time: 1.548s
C:\android-sdk-windows\platform-tools>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\android-sdk-windows\platform-tools>fastboot -w update image-nakasi-jop40c.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.13
Baseband Version.....: N/A
Serial Number........: 015d2578a3140811
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.018s]
sending 'boot' (4942 KB)...
OKAY [ 0.599s]
writing 'boot'...
OKAY [ 0.405s]
sending 'recovery' (5444 KB)...
OKAY [ 0.660s]
writing 'recovery'...
OKAY [ 0.348s]
erasing 'system'...
OKAY [ 0.155s]
sending 'system' (477136 KB)...
OKAY [ 60.010s]
writing 'system'...
OKAY [ 23.794s]
erasing 'userdata'...
OKAY [ 1.092s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 blocks
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 27.895s]
erasing 'cache'...
OKAY [ 0.119s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.940s]
rebooting...
finished. total time: 117.197s
C:\android-sdk-windows\platform-tools>
Click to expand...
Click to collapse
Did you do a erase or just flash over them?
Phone is staing in bootloader- i cant boot any other function like at normal boot, recovery, qcom, bp tools...nothing. Device is LOCKED!!!'Allow OEM Unlock' in developer options is UNCHEKED!!!
BL: moto-apq8084-71.08 (sha-32g8854, 2014-12-09 14:00:26)
Baseband: D4.0-9625-02.95
Product/Variant: shamu XT1100 64GB P3AO
Code:
c:\adb>Fastboot oem lock begin
...
(bootloader) fastboot oem lock currently disabled!
OKAY [ 0.002s]
finished. total time: 0.002s
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.016s
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.012s
downloading 'boot.img'...
OKAY [ 0.469s]
booting...
FAILED (remote failure)
finished. total time: 0.479s
c:\adb>fastboot format cache
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.026s]
sending 'cache' (6248 KB)...
OKAY [ 0.249s]
writing 'cache'...
OKAY [ 0.141s]
finished. total time: 0.426s
c:\adb>fastboot format userdata
Creating filesystem with parameters:
Size: 59743535104
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14585824
Block groups: 446
Reserved block group size: 1024
Created filesystem with 11/3646496 inodes and 274946/14585824 blocks
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 1.700s]
sending 'userdata' (141063 KB)...
OKAY [ 5.993s]
writing 'userdata'...
OKAY [ 3.731s]
finished. total time: 11.434s
c:\adb>
c:\adb>fastboot flash system system.img
target reported max download size of 536870912 bytes
sending sparse 'system' (522112 KB)...
OKAY [ 24.621s]
writing 'system'...
(bootloader) Invalid signed image
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 24.648s
c:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytessending 'boot' (7681 KB)...
OKAY [ 0.299s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.315s
Seriously, do you guys not search ANYWHERE? There are tons of threads regarding bricked Nexus 6s, there's even an unbricking thread about this in this very section! http://forum.xda-developers.com/showthread.php?t=3059518
brando56894 said:
Seriously, do you guys not search ANYWHERE? There are tons of threads regarding bricked Nexus 6s, there's even an unbricking thread about this in this very section! http://forum.xda-developers.com/showthread.php?t=3059518
Click to expand...
Click to collapse
read carefully- my phone not detect like HS-USB QDLoader it is like adb bootloader interface. This happened after rewrite files into /dev/block/. Backups all those files i have. Question- how to write them back?
Duumon said:
read carefully- my phone not detect like HS-USB QDLoader it is like adb bootloader interface. This happened after rewrite files into /dev/block/. Backups all those files i have. Question- how to write them back?
Click to expand...
Click to collapse
Cannot.
rootSU said:
Cannot.
Click to expand...
Click to collapse
I found the way to connect phone as HS-USB QDloader device. All filles of blank-flash.bat flashed, but phone stil dont turn on
Duumon said:
I found the way to connect phone as HS-USB QDloader device
Click to expand...
Click to collapse
How?
rootSU said:
How?
Click to expand...
Click to collapse
testpoint
Duumon said:
testpoint
Click to expand...
Click to collapse
You created a "testpoint" cable?
That's interesting - @efrant
@Duumon - are you still following this thread? http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
@Duumon - are you still following this thread? http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518
Click to expand...
Click to collapse
yes-all those steps passed, but phone stil in locked bootloader. I think need flash boot and sysstem by qualkomm tool but.....how?
Duumon said:
yes-all those steps passed, but phone stil in locked bootloader. I think need flash boot and sysstem by qualkomm tool but.....how?
Click to expand...
Click to collapse
Did you also read post 94 (and related posts) of that thread?
@randy6644 got it to work.
http://forum.xda-developers.com/nexus-6/general/fix-fix-qhusbbulk-cm12-t3059518/post59650346
What is a testpoint cable?
Doesn't helped. Phone have cid-dead and status unlock-not supported. In photo at attach not full the last log- system and boot .img flashed with error Preflash validation failed
still dead...any ideas?
Duumon said:
I found the way to connect phone as HS-USB QDloader device. All filles of blank-flash.bat flashed, but phone stil dont turn on
Click to expand...
Click to collapse
Same Problem. Can you explain how you create the testpoint cable?
Gesendet von meinem LG-D855 mit Tapatalk
Good morning everyone.
So my phone has been constantly boot looping. It restarted one night by itself and has been stuck restarting at the google logo every time. I did a flash stock soft brick with wugs rootkit and still with no success. Here is what the command prompt is saying during the process. Any assistance would help, thank you.
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
(bootloader) has-slot:bootloader: not found
target reported max download size of 536870912 bytes
sending 'bootloader' (3807 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
(bootloader) Motoboot: Preflash validation for aboot
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.280s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
(bootloader) has-slot:radio: not found
target reported max download size of 536870912 bytes
sending 'radio' (67169 KB)...
OKAY [ 2.308s]
writing 'radio'...
(bootloader) flashing modem ...
(bootloader) flashing mdm1m9kefs1 ...
(bootloader) flashing mdm1m9kefs2 ...
(bootloader) flashing mdm1m9kefs3 ...
(bootloader) flashing versions ...
OKAY [ 0.922s]
finished. total time: 3.233s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.010s
(bootloader) has-slot:boot: not found
target reported max download size of 536870912 bytes
sending 'boot' (7624 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.148s]
finished. total time: 0.477s
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.030s]
sending 'cache' (6248 KB)...
OKAY [ 0.200s]
writing 'cache'...
OKAY [ 0.118s]
finished. total time: 0.369s
(bootloader) has-slot:recovery: not found
target reported max download size of 536870912 bytes
sending 'recovery' (8198 KB)...
OKAY [ 0.262s]
writing 'recovery'...
OKAY [ 0.124s]
finished. total time: 0.402s
(bootloader) has-slot:system: not found
target reported max download size of 536870912 bytes
sending sparse 'system' 1/4 (524140 KB)...
OKAY [ 19.200s]
writing 'system' 1/4...
OKAY [ 7.028s]
sending sparse 'system' 2/4 (508171 KB)...
OKAY [ 19.254s]
writing 'system' 2/4...
OKAY [ 6.791s]
sending sparse 'system' 3/4 (519126 KB)...
OKAY [ 20.194s]
writing 'system' 3/4...
OKAY [ 7.098s]
sending sparse 'system' 4/4 (88808 KB)...
OKAY [ 3.422s]
writing 'system' 4/4...
OKAY [ 1.114s]
finished. total time: 84.283s
Creating filesystem with parameters:
Size: 28474998784
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6951904
Block groups: 213
Reserved block group size: 1024
Created filesystem with 11/1738080 inodes and 153124/6951904 blocks
(bootloader) has-slot:userdata: not found
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.831s]
sending 'userdata' (139061 KB)...
OKAY [ 4.672s]
writing 'userdata'...
OKAY [ 2.600s]
finished. total time: 8.102s
Creating filesystem with parameters:
Size: 268435456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 65536
Block groups: 2
Reserved block group size: 15
Created filesystem with 11/16384 inodes and 2089/65536 blocks
(bootloader) has-slot:cache: not found
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.022s]
sending 'cache' (6248 KB)...
OKAY [ 0.216s]
writing 'cache'...
OKAY [ 0.099s]
finished. total time: 0.338s
rebooting...
finished. total time: 0.016s
Assuming it's a Nexus 6 and Twrp-recovery is installed.
Download a stock lite rom prerooted and copy it to internal memory of the N6. In zip formaT.
Boot in bootloader and choose -recovery
( press power button and volume buttons )
In twrp wipe system, and caches and data.
Choose install.
Navigate to the downloaded zip and flash it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Thank you for responding so quickly!
Unfortunately when I go into the bootloader, when I choose recovery or any of the options, it just continues to bootloop.
NLBeev said:
Assuming it's a Nexus 6 and Twrp-recovery is installed.
Download a stock lite rom prerooted and copy it to internal memory of the N6. In zip formaT.
Boot in bootloader and choose -recovery
( press power button and volume buttons )
In twrp wipe system, and caches and data.
Choose install.
Navigate to the downloaded zip and flash it.
http://forum.xda-developers.com/showthread.php?p=59561445/
Click to expand...
Click to collapse
khanhathan said:
Thank you for responding so quickly!
Unfortunately when I go into the bootloader, when I choose recovery or any of the options, it just continues to bootloop.
Click to expand...
Click to collapse
When boot Twrp-recovery isn't possible, you need to flash with 'fastboot' everything again.
Best is to flash manually bootloader, Twrp-recovery, radio and system.
There are several guides on XDA. You could start here:
http://forum.xda-developers.com/showthread.php?p=41374534/
No luck =[.
NLBeev said:
When boot Twrp-recovery isn't possible, you need to flash with 'fastboot' everything again.
Best is to flash manually bootloader, Twrp-recovery, radio and system.
There are several guides on XDA. You could start here:
http://forum.xda-developers.com/showthread.php?p=41374534/
Click to expand...
Click to collapse
khanhathan said:
No luck =[.
Click to expand...
Click to collapse
When you have ' adb ' and ' fastboot ' dtivers correctly installed on a PC it is possible to reboot in bootloader mode with the bootloader on the PC. You have to learn the basics of adb and fastboot.
http://forum.xda-developers.com/showthread.php?p=42970252/
http://forum.xda-developers.com/showthread.php?p=57607286/
Try without wanting an unencrypted boot. Then it should work. Also read up on flashing with adb/fastboot to get a clear understanding of what is done. Tool kits are great and wugs is awesome. But you still need to know the fundamentals.
Flashing a GSI to redmi note 10 5G KEEPING IT SIMPLE edition.
(I dont take responsibility of you destroying your device or causing the world end by flashing. Take proper precautions before proceeding and do your research about the subject and your device)
(Before you proceed, backup important data from your internal storage, i also assume that you have adb tools and drivers installed for your device and bootloader unlocked. Please do also your own research about your device before proceeding.)
adb reboot bootloader (Booting to fastboot)
fastboot reboot fastboot (Booting from fastboot to fastbootd)
fastboot erase system
fastboot -w (deletes userdata, formats the data partition. running this just to be sure personally)
You migth get an error :
/usr/bin/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata (wich is no cause for concern)
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img (Thanks 1lopes for pointing missing arguments, more information in the first 3 comments)
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.013s]
fastboot fastboot flash system GSIofyourchoice.img
Invalid sparse file format at header magic (no need for concern)
Resizing 'system_a' OKAY [ 0.008s]
Sending sparse 'system_a' 1/7 (262108 KB) OKAY [ 20.939s]
Writing 'system_a' OKAY [ 1.041s]
Sending sparse 'system_a' 2/7 (262120 KB) OKAY [ 21.163s]
Writing 'system_a' OKAY [ 1.217s]
Sending sparse 'system_a' 3/7 (262116 KB) OKAY [ 19.183s]
Writing 'system_a' OKAY [ 1.157s]
Sending sparse 'system_a' 4/7 (262120 KB) OKAY [ 15.908s]
Writing 'system_a' OKAY [ 1.052s]
Sending sparse 'system_a' 5/7 (262088 KB) OKAY [ 19.747s]
Writing 'system_a' OKAY [ 1.045s]
Sending sparse 'system_a' 6/7 (262124 KB) OKAY [ 20.658s]
Writing 'system_a' OKAY [ 1.038s]
Sending sparse 'system_a' 7/7 (166688 KB) OKAY [ 13.939s]
Writing 'system_a' OKAY [ 0.861s]
Finished. Total time: 152.907s
fastboot reboot recovery (Reboots your phone to recovery, do factory reset) (EDITED)
This way, you dont destroy ability to boot to fastboot, fastbootd and you keep your original recovery and bootloader intact. If you boot to recovery after a reboot, do a factory reset from there and try to boot again, should work. IF it dosen't, you can easily try other gsi with the same steps.
vbmeta.img provided in this guide disables Android Verified Boot (AVB), Some devices have problems booting into custom GSI:s it enabled.
EDIT:
I was in stock MIUI13 (bootloader unlocked) , did factory reset, re enabled usb debugging and followed the steps in this guide.
I personally used phusson android 12 gsi
(system-squeak-arm64-ab-vndklite-vanilla-secure)
with the vbmeta.img in this guide.
Origin of vbmeta.img and information. Please use the vbmeta.img provided below. If the drive link does not work, you can find it from the original information source below. :
vbmeta.img
drive.google.com
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
i have a question. from the other guide to flash pe, why cant we do the command
fastboot delete-logical-partition product
?
thanks for the guide btw, might try later on my redmi note 10 5g flashing pe in it, just this question tho
also i think u forgot a very important step, i think you need to disable verity and verification or that could boot up with dm-verity corruption
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
1lopes said:
also i think u forgot a very important step, i think you need to disable verity and verification or that could boot up with dm-verity corruption
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Click to expand...
Click to collapse
Thanks for pointing that out mate ! ill be adding it to op. I did not need the arguments personally tough but it is better to be safe than sorry!
The reason i discourage the wiping of logical partition ''product'' is, it contains the original recovery for example, information for fastboot and fastbootd. It is not needed to wipe product partition at all in order to flash GSI:s and use them.
If you have software to replace the functions with 3rd party ones and you know what you are doing, you can do it but just be aware what changes you are doing for your phone's software.
it contains the crucial pieces i want to keep safe in this quide to make it easyer to go back to stock frimware.
Remember to use the vbmeta.img im pointing to in this guide. Im quoting the reason directly from xda. if the vbmeta.img direct drive link does not work, look it up from the original information source :
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
''
On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)
''
However if this information is wrong, ill admit it and pull it off. This guide contains the steps i followed personally with success and without hassle with this device.
toonTT said:
Thanks for pointing that out mate ! ill be adding it to op. I did not need the arguments personally tough but it is better to be safe than sorry!
The reason i discourage the wiping of logical partition ''product'' is, it contains the original recovery for example, information for fastboot and fastbootd. It is not needed to wipe product partition at all in order to flash GSI:s and use them.
If you have software to replace the functions with 3rd party ones and you know what you are doing, you can do it but just be aware what changes you are doing for your phone's software.
it contains the crucial pieces i want to keep safe in this quide to make it easyer to go back to stock frimware.
Remember to use the vbmeta.img im pointing to in this guide. Im quoting the reason directly from xda. if the vbmeta.img direct drive link does not work, look it up from the original information source :
https://www.xda-developers.com/flash-generic-system-image-project-treble-device/
''
On some devices like the Google Pixel 2/2 XL, Android Verified Boot (AVB) needs to be disabled. You can do so by flashing this image to the vbmeta partition (command: fastboot flash vbmeta name_of_vbmeta.img)
''
However if this information is wrong, ill admit it and pull it off. This guide contains the steps i followed personally with success and without hassle with this device.
Click to expand...
Click to collapse
Thank you so much for the information, especially about deleting the logical partition product.
Maybe that would have had affected the last part of wiping user data in recovery after flashing a GSI? (Unless the fastboot -w already does it) in the other guide. For example, this person couldn't get any GSI booting.
Also, dont you necessarily need to set active a? ( fastboot set_active a )
toonTT said:
I did not need the arguments personally tough but it is be better to be safe than sorry!
Click to expand...
Click to collapse
Didnt mean to make a argument for you, i was just pointing it all!
1lopes said:
Didnt mean to make a argument for you, i was just pointing it all!
Click to expand...
Click to collapse
Oh dear my bad, i wasn't clear enough what i meant by that. did not mean it that way, i was talking about the command arguments what you use with fastboot while flashing vbmeta.img . '' --disable-verity --disable-verification '' i did not personally use them and had not problems.
fastboot -w formats the data partition, where user data is, thats how i understand it.
About the booting problem , that he deleted the logical partition is a red flag for me. Im no expert but thats how i see it.
toonTT said:
Oh dear my bad, i wasn't clear enough what i meant by that. did not mean it that way, i was talking about the command arguments what you use with fastboot while flashing vbmeta.img .
Click to expand...
Click to collapse
Oh! I misunderstood it. I'm sorry. Anyways, lets move on.
toonTT said:
About the booting problem , that he deleted the logical partition is a red flag for me. Im no expert but thats how i see it.
Click to expand...
Click to collapse
Actually, you probably are correct. It basically might delete recovery and fastboot information just like you said, and from here it also refers as it being a system extension, etc. that I really don't understand my self.
toonTT said:
fastboot -w formats the data partition, where user data is, thats how i understand it.
Click to expand...
Click to collapse
Oh, thanks for it, as I was unsure from my last reply. Maybe it's not really necessary, but thanks to you for pointing out that fastboot delete-logical-partition product would delete the original recovery, as for that you don't need to do that command because you only need to do fastboot reboot recovery and then select wipe data and all done.
Again, thank you for pointing the big problem of the logical partition product deleting. I was about to flash PE maybe yesterday or the day before yesterday, and I could, or many more, make this mistake and could go wrong even more than just a soft brick on the phone
delete logical is not necessary. all gsi i have installed go up without do this. if you delete the patition even if uncessary, sure cold cause issues. use your brains and read the guides
Hi friends,
I just tried to flash my Redmi Note 10 5G and my phone freezes on "fastboost" every time it boots.
I tried to flash 2 "Phhusson" files:
- system-squeak-arm64-ab-vndklite-vanilla.img.xz
- system-squeak-arm64-ab-vndklite-gogapps-secure.img.xz
(same fastboot problem on startup with the 2 files)
I tried a "wipe data" in recovery mode.
If you have a solution to find my phone?
Thank you in advance for your help.
Here are the commands I sent:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.976s
fastboot erase system
Erasing 'system_a' OKAY [ 0.085s]
Finished. Total time: 0.116s
fastboot -w
Erasing 'userdata' OKAY [ 2.083s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 227016640 (110847 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 1d000 0 200 at offset 0x00118784
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d601, 0001d602
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118785
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d603, 0001d604
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118786
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0001d600
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 670 (GC reserved = 341)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.000s]
Writing 'userdata' OKAY [ 0.501s]
Erasing 'metadata' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 8192 4k blocks and 8192 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.007s]
Writing 'metadata' OKAY [ 0.000s]
Finished. Total time: 3.717s
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.053s
fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 1/11 (261709 KB) OKAY [ 9.121s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 2/11 (262124 KB) OKAY [ 8.905s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 3/11 (262116 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.024s]
Sending sparse 'system_a' 4/11 (262124 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 5/11 (262128 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 6/11 (262116 KB) OKAY [ 8.820s]
Writing 'system_a' OKAY [ 1.165s]
Sending sparse 'system_a' 7/11 (262124 KB) OKAY [ 8.874s]
Writing 'system_a' OKAY [ 1.187s]
Sending sparse 'system_a' 8/11 (259235 KB) OKAY [ 8.783s]
Writing 'system_a' OKAY [ 1.056s]
Sending sparse 'system_a' 9/11 (260056 KB) OKAY [ 8.767s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 10/11 (258520 KB) OKAY [ 8.635s]
Writing 'system_a' OKAY [ 1.065s]
Sending sparse 'system_a' 11/11 (23178 KB) OKAY [ 0.902s]
Writing 'system_a' OKAY [ 0.254s]
Finished. Total time: 109.991s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Glucksnip said:
Hi friends,
I just tried to flash my Redmi Note 10 5G and my phone freezes on "fastboost" every time it boots.
I tried to flash 2 "Phhusson" files:
- system-squeak-arm64-ab-vndklite-vanilla.img.xz
- system-squeak-arm64-ab-vndklite-gogapps-secure.img.xz
(same fastboot problem on startup with the 2 files)
I tried a "wipe data" in recovery mode.
If you have a solution to find my phone?
Thank you in advance for your help.
Here are the commands I sent:
fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.000s]
< waiting for any device >
Finished. Total time: 12.976s
fastboot erase system
Erasing 'system_a' OKAY [ 0.085s]
Finished. Total time: 0.116s
fastboot -w
Erasing 'userdata' OKAY [ 2.083s]
F2FS-tools: mkfs.f2fs Ver: 1.14.0 (2020-08-24)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 227016640 (110847 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 634] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 668] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1281] Writing root inode (hot node), 1d000 0 200 at offset 0x00118784
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d601, 0001d602
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118785
[f2fs_write_default_quota:1357] Writing quota data, at offset 0001d603, 0001d604
[f2fs_write_qf_inode:1416] Writing quota inode (hot node), 1d000 0 200 at offset 0x00118786
[f2fs_update_nat_root:1470] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1667] Writing default dentry root, at offset 0x0001d600
Info: Overprovision ratio = 0.600%
Info: Overprovision segments = 670 (GC reserved = 341)
[f2fs_write_check_point_pack: 827] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 982] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1009] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1021] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1032] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1040] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1060] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1081] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1100] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1133] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.000s]
Writing 'userdata' OKAY [ 0.501s]
Erasing 'metadata' OKAY [ 0.016s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 8192 4k blocks and 8192 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.007s]
Writing 'metadata' OKAY [ 0.000s]
Finished. Total time: 3.717s
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
Rewriting vbmeta struct at offset: 0
Sending 'vbmeta_a' (4 KB) OKAY [ 0.000s]
Writing 'vbmeta_a' OKAY [ 0.016s]
Finished. Total time: 0.053s
fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img
Invalid sparse file format at header magic
Resizing 'system_a' OKAY [ 0.000s]
Sending sparse 'system_a' 1/11 (261709 KB) OKAY [ 9.121s]
Writing 'system_a' OKAY [ 1.203s]
Sending sparse 'system_a' 2/11 (262124 KB) OKAY [ 8.905s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 3/11 (262116 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.024s]
Sending sparse 'system_a' 4/11 (262124 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.034s]
Sending sparse 'system_a' 5/11 (262128 KB) OKAY [ 8.836s]
Writing 'system_a' OKAY [ 1.002s]
Sending sparse 'system_a' 6/11 (262116 KB) OKAY [ 8.820s]
Writing 'system_a' OKAY [ 1.165s]
Sending sparse 'system_a' 7/11 (262124 KB) OKAY [ 8.874s]
Writing 'system_a' OKAY [ 1.187s]
Sending sparse 'system_a' 8/11 (259235 KB) OKAY [ 8.783s]
Writing 'system_a' OKAY [ 1.056s]
Sending sparse 'system_a' 9/11 (260056 KB) OKAY [ 8.767s]
Writing 'system_a' OKAY [ 1.040s]
Sending sparse 'system_a' 10/11 (258520 KB) OKAY [ 8.635s]
Writing 'system_a' OKAY [ 1.065s]
Sending sparse 'system_a' 11/11 (23178 KB) OKAY [ 0.902s]
Writing 'system_a' OKAY [ 0.254s]
Finished. Total time: 109.991s
fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total time: 0.000s
Click to expand...
Click to collapse
You used vndklite. Thats the problem.
The redmi note 10 5g doesnt has VNDK LITE Treble, only Treble VNDK version 31.0
Check:
{
"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"
}
Please check any ROM carefully that its not "vndklite" after the ROM variant (bgN-vndklite), if theres no variant information, check if it says "arm64-ab" with no vndklite and you are good to go.
Some vndklite systems are only for A slots, others are for a/b, but that doesnt solve the problem as the Redmi doesnt include vndklite treble.
1lopes said:
You used vndklite. Thats the problem.
The redmi note 10 5g doesnt has VNDK LITE Treble, only Treble VNDK version 31.0
Check:View attachment 5668855
Please check any ROM carefully that its not "vndklite" after the ROM variant (bgN-vndklite), if theres no variant information, check if it says "arm64-ab" with no vndklite and you are good to go.
Some vndklite systems are only for A slots, others are for a/b, but that doesnt solve the problem as the Redmi doesnt include vndklite treble.
Click to expand...
Click to collapse
I have unzipped the img file: "fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img"
I chose this file because on the first post of this conversation @toonTT says: "I personally used phusson android 12 gsi (system-squeak-arm64-ab-vndklite-vanilla-secure)"
Glucksnip said:
I have unzipped the img file: "fastboot flash system system-squeak-arm64-ab-vndklite-gapps-secure.img"
I chose this file because on the first post of this conversation @toonTT says: "I personally used phusson android 12 gsi (system-squeak-arm64-ab-vndklite-vanilla-secure)"
Click to expand...
Click to collapse
Thats the problem, Redmi Note 10 5G doesn't support vndklite. Use a ROM that is "arm64-ab" and is not intended for devices with vndklite.
1lopes said:
Thats the problem, Redmi Note 10 5G doesn't support vndklite. Use a ROM that is "arm64-ab" and is not intended for devices with vndklite.
Click to expand...
Click to collapse
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Glucksnip said:
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Click to expand...
Click to collapse
Private message me please, i will try to help you there, and so sorry for the wait and inactivity.
1lopes said:
Private message me please, i will try to help you there, and so sorry for the wait and inactivity.
Click to expand...
Click to collapse
No problem we have a life outside the internet ;-)
It's good I managed to recover my phone using a really cool application "XiaomiTool2" it fixed my phone in a few clicks, too strong !!
it installed miui 13 Global_V13.0.2.0.SKSEUXM
Thanks for the help ;-)
Glucksnip said:
No problem we have a life outside the internet ;-)
It's good I managed to recover my phone using a really cool application "XiaomiTool2" it fixed my phone in a few clicks, too strong !!
it installed miui 13 Global_V13.0.2.0.SKSEUXM
Thanks for the help ;-)
Click to expand...
Click to collapse
Im glad it worked. Sorry that I couldnt help you, but atleast you got it working againIf you need any help you can contact anyone here or me
Glucksnip said:
OK, thanks
Just tested @phhusson's "system-squeak-arm64-ab-gapps.img" and still the damn "fastboot" on boot.
- PixelExperience-Plus_.imgarm64-ab-12.1-20220722-unofficial
- lineage-19.1-20220511-UNOFFICIAL-arm64_bvS-personal.img
each time it is "fastboot" which launches at each start.
I tried to install
"camellian_global_images_V12.5.2.0.RKSMIXM_20211012.0000.00_11.0_global_d1443f45f5.tgz"
The flash is done in 1 second and MiFlash tells me that everything is fine. Inevitably in 1 second it is fastboot which launches.
I don't know what else to test...
Click to expand...
Click to collapse
In my experience, I flash MIUI 12.2 first before flash the GSI and voila it works.
If I flash GSI from MIUI 12.5 or 13, it always boot into fastboot after clear data in recovery mode.
Hope it answer your question
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
ThinkIt12 said:
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
Click to expand...
Click to collapse
Nope, since there's not even a official TWRP (but a unofficial one) for both of the devices here or a guide in this forum. Try checking a youtube video.
ThinkIt12 said:
Sorry out of topic
Is there any tutorial/step to flash GSI Using TWRP on Poco M3 pro 5G?
Click to expand...
Click to collapse
flash without twrp, using fastboot commands.. is easy, safe and better than twrp (actually touch dont work, need otg cable)