Hi everybody !
I'm very sorry to post, i know a lot of people have the same problem as me, I have seen a lot of post but every time the only answer of member is : go see the huge 4.2.2 post !
Since yesterday morning I'm trying to update my nexus 7 4.2.1 to 4.2.2.
I know the problem, I have installed stickmount that have problably changed some system files and now every time i want update by anyway I have an error 7 saying that asset check doesnt match etc etc.... apparently a file system/lib/debbugr something like that.
I've wipe all the data, i did a factory reset, always the same problem.
With CWM 6 or TWR I have tried to update with the OTA zip 4.2.2 , with the 4.2.1 too .... Error error error... Even if i uncheck the verification !!!!
I have downloaded this factory image too : nakasi-jdq39-factory-c317339e.tgz
Trying to install it with WugFresh toolkit.... Installation aborded after the check... I had an S1 S2 , i ve unlocked my Nexus 7 , root it etc... But for the first time I'm totally blocked !!!!
Please... I beg you... Help me, I know you will send me probably to an other post but please not a generic one, I'm really turning mad.
Thank you for your help, I'm ready to answer to any question, and to try everything. I have all the tools installed on my computer... Thank you by advance
Here is the full error message :
assert failed: apply_patch_check ("system/bin/debuggerd", "xxxxxxxxxxx"
E:Error in /sdcard/readytoflash/signed-nakasi-jdq39-from-JOP40D
statut 7 etc....
Just tried something and maybe it's gonna work.... fingers crossed....
I download the full factory image of the 4.2.2
launch my nexus 7 in bootloader and after i have exec those commands :
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.18.img
fastboot reboot-bootloader
fastboot -w update image-nakasi-jdq39.zip
Command Prompt for manual input...
------------------------------------------------------------------
Try typing "adb help" or "fastboot help" for a full cmd list and syntax info.
Enjoy...
C:\WugFresh Development\data>fastboot oem
C:\WugFresh Development\data>unlockfastboot
'unlockfastboot' is not recognized as an internal or external command,
operable program or batch file.
C:\WugFresh Development\data>fastboot help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\WugFresh Development\data>fastboot devices
015d2d431d641e0b fastboot
C:\WugFresh Development\data>fastboot oem unlockfastboot
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.021s
C:\WugFresh Development\data>erase
The syntax of the command is incorrect.
C:\WugFresh Development\data>erase bootfastboot
Could Not Find C:\WugFresh Development\data\bootfastboot
C:\WugFresh Development\data>fastboot erase
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\WugFresh Development\data>fastboot erase bootfastboot
erasing 'bootfastboot'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 0.025s
C:\WugFresh Development\data>fastboot erase boot
erasing 'boot'...
OKAY [ 0.139s]
finished. total time: 0.140s
C:\WugFresh Development\data>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.285s]
finished. total time: 0.287s
C:\WugFresh Development\data>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.139s]
finished. total time: 0.140s
C:\WugFresh Development\data>fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.534s]
finished. total time: 0.535s
C:\WugFresh Development\data>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 17.099s]
finished. total time: 17.100s
C:\WugFresh Development\data>fastboot flash bootloader bootloader-grouper-4.18.i
mg
sending 'bootloader' (2096 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
OKAY [ 1.960s]
finished. total time: 2.250s
C:\WugFresh Development\data>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.022s
C:\WugFresh Development\data>fastboot -w update image-nakasi-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d2d431d641e0b
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.022s]
sending 'boot' (4944 KB)...
OKAY [ 0.645s]
writing 'boot'...
OKAY [ 1.877s]
sending 'recovery' (5446 KB)...
OKAY [ 0.702s]
writing 'recovery'...
OKAY [ 0.224s]
erasing 'system'...
OKAY [ 0.112s]
sending 'system' (471804 KB)...
OKAY [ 59.948s]
writing 'system'...
OKAY [ 29.385s]
erasing 'userdata'...
OKAY [ 4.919s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 30080499712
Block size: 4096
Blocks per group: 32768
Inodes per group: 8160
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7343872
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1836000 inodes and 159268/7343872 blocks
sending 'userdata' (139157 KB)...
writing 'userdata'...
OKAY [ 33.302s]
erasing 'cache'...
OKAY [ 0.077s]
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.847s]
rebooting...
finished. total time: 133.304s
Click to expand...
Click to collapse
So....It look likes to work... Speaking alone helped me a lot.. I leave the post here for those who have the same issue.
wiseman-fr said:
So....It look likes to work... Speaking alone helped me a lot.. I leave the post here for those who have the same issue.
Click to expand...
Click to collapse
Heheh, so it seems your imaginary friend helped you out :sly:
Sent from my Nexus 7 using Tapatalk HD
Please guys, help me, I still can boot into fastboot, but can't boot into twrp(even flashing it via fastboot recovery_ramdisk) or erecovery
Successfully repaired ...:good:
I also met
How did you repair your device? I have the same problem, please help!
Sorry for my English language....
Download https://drive.google.com/file/d/1uMrmObOb78_2dp8I6rVEOJ1s9Dg8QJDs/view
extracted zip
Open -- tools_fw -- FW --remove all files
Open -- update-L09 -- remove all files
Open --update-L29 -- remove all files
Open -- Update APP Unpacker --- copy the folder - UPDATE.APP - service ROM - Huawei P10 Lite [ https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097
]
Click ---- UNPACKER_RUN_ME.bat extract update.app ... Finished .... Open - output -- extracted file copy All to - tools_fw - FW....
open --- / tools_fw / - /update-L09 /
or /update-L29/ copy folder - CUST.img , USERDATA.img , VERSION.img
Connect a fastbootmode phone
CLICK 1. revive flasher ... flashed extract file ... Finished ... restart phone
Sending 'cache' (6200 KB) OKAY [ 0.148s]
Writing 'cache' OKAY [ 0.083s]
Finished. Total time: 0.265s
Sending 'crc' (273 KB) OKAY [ 0.009s]
Writing 'crc' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Sending 'bla bla............'
Click to expand...
Click to collapse
IGNORED the Writing FAILED (remote: 'partition length get error')
Everything after this was correctly flashed.
I repaired it successfully
error: FUNC 8 : HIFI Image, Error 1 Security Verify failed
error:FUNC 11
[UNBRICK] P10 VTR-L09/VTR-L29 unbrick XLOADER2 failed downgrades with free tools.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
Ashle said:
Sorry for my English language....
Download https://drive.google.com/file/d/1uMrmObOb78_2dp8I6rVEOJ1s9Dg8QJDs/view
extracted zip
Open -- tools_fw -- FW --remove all files
Open -- update-L09 -- remove all files
Open --update-L29 -- remove all files
Open -- Update APP Unpacker --- copy the folder - UPDATE.APP - service ROM - Huawei P10 Lite [ https://forum.xda-developers.com/p10-lite/help/original-service-rom-huawei-p10-lite-t3688097 ]
Click ---- UNPACKER_RUN_ME.bat extract update.app ... Finished .... Open - output -- extracted file copy All to - tools_fw - FW....
open --- / tools_fw / - /update-L09 /
or /update-L29/ copy folder - CUST.img , USERDATA.img , VERSION.img
Connect a fastbootmode phone
CLICK 1. revive flasher ... flashed extract file ... Finished ... restart phone
IGNORED the Writing FAILED (remote: 'partition length get error')
Everything after this was correctly flashed.
I repaired it successfully
error: FUNC 8 : HIFI Image, Error 1 Security Verify failed
error:FUNC 11
[UNBRICK] P10 VTR-L09/VTR-L29 unbrick XLOADER2 failed downgrades with free tools.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
Click to expand...
Click to collapse
It gives many errors like "command not allowed" and many missing files...
angushev20 said:
It gives many errors like "command not allowed" and many missing files...
Click to expand...
Click to collapse
P10 VTR-L09/VTR-L29 unbrick XLOADER2 failed downgrades with free tools.
https://forum.xda-developers.com/p10/how-to/unbrick-p10-vtr-l09-vtr-l29-unbrick-t3916694
IGNORED - hisee,hisiufs,isp file P10 -- NO P10Lite file stock rom ....
IGNORED- Writing 'crc' FAILED (remote: 'partition length get error')
curver,
IGNORED the Writing FAILED (remote: 'partition length get error')
Everything after this was correctly flashed.
flashed extract file ... Finished ... restart phone
Code:
fastboot: error: cannot load 'fw\vector.img': No such file or directory
fastboot: error: cannot load 'fw\hisee_fs.img': No such file or directory
fastboot: error: cannot load 'fw\hisee_img.img': No such file or directory
fastboot: error: cannot load 'fw\isp_firmware.img': No such file or directory
fastboot: error: cannot load 'fw\HISIUFS_GPT.img': No such file or directory
Sending 'crc' (233 KB) OKAY [ 0.283s]
Writing 'crc' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Sending 'curver' (0 KB) OKAY [ 0.273s]
Writing 'curver' FAILED (remote: 'partition length get error')
Sending 'modem_fw' (98304 KB) FAILED (Write to device failed in SendBuffer() (Too many links))
fastboot: error: Command failed
Sending 'package_type' (0 KB) OKAY [ 0.193s]
Writing 'package_type' FAILED (remote: 'partition length get error')
Sending 'sha256rsa' (0 KB) OKAY [ 0.002s]
Writing 'sha256rsa' FAILED (remote: 'partition length get error')
fastboot: error: Command failed
Welcome to this unbrick tutorial​
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
fastboot devices
Click to expand...
Click to collapse
If a line appears, your phone is correctly connected.
Type the command :
fastboot flash super super.img
Click to expand...
Click to collapse
If it flashed correctly, you should see something like this :
C:\Users\Alex\Desktop\platform-tools>fastboot flash super super.img
Invalid sparse file format at header magic
Sending sparse 'super' 1/9 (786428 KB) OKAY [ 19.574s]
Writing 'super' OKAY [ 0.013s]
Sending sparse 'super' 2/9 (786428 KB) OKAY [ 19.587s]
Writing 'super' OKAY [ 0.018s]
Sending sparse 'super' 3/9 (786428 KB) OKAY [ 19.609s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 4/9 (698716 KB) OKAY [ 17.393s]
Writing 'super' OKAY [ 0.012s]
Sending sparse 'super' 5/9 (765968 KB) OKAY [ 19.103s]
Writing 'super' OKAY [ 0.010s]
Sending sparse 'super' 6/9 (763420 KB) OKAY [ 19.074s]
Writing 'super' OKAY [ 0.017s]
Sending sparse 'super' 7/9 (786097 KB) OKAY [ 19.636s]
Writing 'super' OKAY [ 0.009s]
Sending sparse 'super' 8/9 (786089 KB) OKAY [ 19.745s]
Writing 'super' OKAY [ 0.029s]
Sending sparse 'super' 9/9 (102406 KB) OKAY [ 2.853s]
Writing 'super' OKAY [ 6.798s]
Finished. Total time: 167.087s
Click to expand...
Click to collapse
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.
Download the correct region and version of the firmware.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
fastboot reboot fastboot
Click to expand...
Click to collapse
You should reboot into fastbootd.
Then use :
fastboot getvar all
Click to expand...
Click to collapse
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
fastboot set_active b
Click to expand...
Click to collapse
If you're on a slot, or :
fastboot set_active a
Click to expand...
Click to collapse
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Update :
Here are listed all the Super Partitions available for us to fix our Nothing :
1.1.3 EEA : Link
1.1.4 Global : Link
More to come...
Remember that you have to download the Sh4ttered tool version according to the version you are trying to restore.
Again, feel free to share a backup of yours that is not listed here to help other in need
Reserved 2
i have super img latest 1.14 global
ayed78 said:
i have super img latest 1.14 global
Click to expand...
Click to collapse
Can you upload it and share the link?
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.
Code:
Erasing 'userdata' OKAY [ 0.027s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Wiping data on userspace fastboot works:
Code:
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata' OKAY [ 0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s
There were also problems with flashing to B slot.
Code:
Sending 'odm_b' (1052 KB) OKAY [ 0.024s]
Writing 'odm_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 6.057s]
Writing 'product_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB) OKAY [ 6.077s]
Writing 'system_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 6.133s]
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB) OKAY [ 0.083s]
Writing 'tz_b' OKAY [ 0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 6.079s]
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
arinc9 said:
I've tried this on my Nothing Phone (1) EEA version which bootloops. It doesn't work. Whilst booting from the A slot, there's the 15 seconds of splash screen, then it reboots, same as before.
There were problems with wiping userdata. It only works on userspace fastboot (fastbootd). The flash_all.bat script attempts to wipe userdata on bootloader fastboot.
Code:
Erasing 'userdata' OKAY [ 0.027s]
F2FS-tools: mkfs.f2fs Ver: 1.15.0 (2022-05-20)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Enable Project quota
Error: Sparse mode is only supported for android
G:\Documents\NothingPhone\platform-tools/make_f2fs failed: 4294967295
fastboot: error: Cannot generate image for userdata
Wiping data on userspace fastboot works:
Code:
PS G:\Documents\NothingPhone\platform-tools> ./fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
Finished. Total time: 10.425s
PS G:\Documents\NothingPhone\platform-tools> ./fastboot -w
Erasing 'userdata' OKAY [ 0.035s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Erasing 'metadata' OKAY [ 0.004s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 0.072s
There were also problems with flashing to B slot.
Code:
Sending 'odm_b' (1052 KB) OKAY [ 0.024s]
Writing 'odm_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'product_b' 1/8 (262108 KB) OKAY [ 6.057s]
Writing 'product_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'qupfw_b' (56 KB) OKAY [ 0.002s]
Writing 'qupfw_b' OKAY [ 0.033s]
Finished. Total time: 0.045s
Sending 'shrm_b' (48 KB) OKAY [ 0.002s]
Writing 'shrm_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'system_b' 1/6 (262104 KB) OKAY [ 6.077s]
Writing 'system_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending sparse 'system_ext_b' 1/2 (262116 KB) OKAY [ 6.133s]
Writing 'system_ext_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'tz_b' (3636 KB) OKAY [ 0.083s]
Writing 'tz_b' OKAY [ 0.046s]
Finished. Total time: 0.139s
Sending 'uefisecapp_b' (124 KB) OKAY [ 0.004s]
Writing 'uefisecapp_b' OKAY [ 0.006s]
Finished. Total time: 0.019s
Sending 'vbmeta_b' (8 KB) OKAY [ 0.000s]
Writing 'vbmeta_b' OKAY [ 0.004s]
Finished. Total time: 0.015s
Sending 'vbmeta_system_b' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system_b' OKAY [ 0.005s]
Finished. Total time: 0.016s
Sending sparse 'vendor_b' 1/5 (262104 KB) OKAY [ 6.079s]
Writing 'vendor_b' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Flashing to A slot was completed without any errors. I don't think this super image includes the persist partition. My phone started bootlooping after I erased the persist partition. Can anyone upload their persist partition for the global or EEA version?
Click to expand...
Click to collapse
The Persist partition contains the unique calibration settings for the sensors on your phone. It cannot be recovered. If it's really corrupted, the only way is to send the phone back for warranty for now.
On Xiaomi forum, they solved the issue by flashing the persist partition from a stock fastboot rom, can't tell if it'll work with yours but you Can Always give it a try if you can find a persist partition backup
For the B slot, I think I had errors too, but switching slots fixed mine.
AntoXik72 said:
Can you upload it and share the link?
Click to expand...
Click to collapse
2.98 GB file on MEGA
mega.nz
persist global 1.1.4
5.5 MB file on MEGA
mega.nz
ayed78 said:
persist global 1.1.4
5.5 MB file on MEGA
mega.nz
Click to expand...
Click to collapse
Thank you so much, this fixed it!!! I only know how to backup partitions with TWRP, did you do this with an android app?
arinc9 said:
Thank you so much, this fixed it!!! I only know how to backup partitions with TWRP, did you do this with an android app?
Click to expand...
Click to collapse
yes...
ayed78 said:
yes...
Click to expand...
Click to collapse
What's the name of the app?
arinc9 said:
What's the name of the app?
Click to expand...
Click to collapse
Partitions Backup & Restore - Apps on Google Play
Backup your important partitions to avoid any data or IMEI corruption
play.google.com
This one for example.
ayed78 said:
2.98 GB file on MEGA
mega.nz
Click to expand...
Click to collapse
That's perfect, thanks, i'll update the post tonight
AntoXik72 said:
That's perfect, thanks, i'll update the post tonight
Click to expand...
Click to collapse
AntoXik72 said:
Welcome to this unbrick tutorial​
This tutorial is EEA only at the moment
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
Unlocked bootloader both classic and critical unlock Link
Sh4ttered Tool (the 1.1.3 update!! for now as I don't have a super partition backup for both 1.1.4 or 1.1.3 Global) Link
1.1.3 super partition (EEA Only at the moment, feel free to share a Global one in the comments) Link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
If a line appears, your phone is correctly connected.
Type the command :
If it flashed correctly, you should see something like this :
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, Run the Download.ps1 with powershell and download the 1.1.3 EEA made by Sh4ttered and downloaded earlier.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
You should reboot into fastbootd.
Then use :
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
If you're on a slot, or :
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
very good man, I'm busy rn so it's sooo good that you wrote this for everyone, thanks!
AntoXik72 said:
Welcome to this unbrick tutorial​
NB: I state immediately that i'm not responsible for any damage that occurs on your phone. This process worked for my Nothing Phone on 1.1.3, but maybe not on yours.
I do not suggest following this tutorial if you are on 1.1.4 but since your phone is already out of usage, you can try on your own.
In the next lines we will see how to restore our device to its original factory conditions, after unlocking the Bootloader. Note that all your data will be lost.
You are missing some of the phone partitions? This might solve your issue.
Let's begin!
MATERIAL REQUIRED :
Latest platform tools correctly installed Link
- Unlocked bootloader both classic and critical unlock Link
- Sh4ttered Tool (download the version that matches the version you are trying to restore when you bricked your phone ) Link
- Super partition listed in post #2 and corresponding to your device version and region
- PC with Microsoft Windows 7-8-8.1-10-11
- USB type C cable
- Drivers of Nothing Phone installed
STEP 1 : Prepare everything
Extract the super partition from the zip to the platform tools folder and rename it super.img. Boot your device into Fastboot mode through power + Vol -
Once into fastboot mode, launch a CMD window into your platform tool folder by typing cmd in the search bar of your platform tool folder.
Then, connect your phone to the computer and type the command :
If a line appears, your phone is correctly connected.
Type the command :
If it flashed correctly, you should see something like this :
Once that step is done, your phone has now working super partitions.
STEP 2 : Flash stock firmware
After flashing super.img, you have to flash all the left partitions. For that, with powershell, run the Download.ps1 made by Sh4ttered and downloaded earlier.
Download the correct region and version of the firmware.
Once the Firmware is downloaded, you should see a new fw.zip
Run the flash_all.bat script, it should flash all the partitions without issues.
If something went wrong, tell me in the comment section.
Then, your device should reboot.
STEP 3 : Check your slots
If your device is still not booting, simply change the slot you're on with the following commands :
You should reboot into fastbootd.
Then use :
Look for the line where it says current-slot and it will tell you if it's A slot or B slot
Once you know on wich slot you are, try booting on the other one by running this last command :
If you're on a slot, or :
If you're on b slot.
Reboot your phone after that, and you should boot normally.
If not, let me know your issues in the comments by posting your logs and explaining me where you had an error.
Sorry for my bad english sometimes
Huge thanks to XDA Community, ssut for payload-dumper-go, Sh4ttered and his team for his tool.
Click to expand...
Click to collapse
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
pankspoo said:
Unbrick tool ? if fasboot mode is working you can't tell it as unbrick method.
But anyway good work
Quick question will this helps to downgrade the Device?
Click to expand...
Click to collapse
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.
For the downgrade, I can't tell, try it at your own risks.
AntoXik72 said:
I didn't told it was a tool. It is an unbrick method because in case you didn't encountered the issue before and you don't know what you are talking about, when you do something wrong with the Nothing Phone and you break your super partition, you Can try to flash whatever you want, it will Never boot unless you flash this. For someone who don't understand as good as you how to recover his phone, this Can be helpful.
For the downgrade, I can't tell, try it at your own risks.
Click to expand...
Click to collapse
Actullly the term you use must be revive phone from bootloop like that.
Any way thanks
mine still stuck at fastboot...nothing tool not update....it detect lower version update on mine 1.1.4 global