Hi all,
My nexus 7 has flashed with PA 3.65.
Now, I want to back to stock 4.2.2 ROM. I use the two tool kits-- Nexus 7 Toolkit and Nexus Root Toolkit
But my device is like locked, I use all kinds of commands to erase/flash it, my device is still run as PA version.
Go into TWRP and factory reset, the PA system still exist...
Use the Toolkit to flash, the PA system still exist...
Use adb/fastboot command to flash recovery image from TWRP 2.5.0.0 to 2.6, it always run as TWRP 2.5.0.0.
I feel my nexus 7's partition is locked, I can NOT add/delete anything. For example, if I delete a file in internal storage, the file will appear at the next reboot. If I add a file in internal storage, it will disappear at the next reboot time.
Anyone can help me? I have no idea to solve it.:crying:
Download the Nexus 7 4.2.2 factory package and unzip the contents to your ADB/Fastboot directory then reboot your device into Bootloader. Start > Run > CMD > cd (your directory) e.g. "cd c:/platform-tools" > "flash-all.bat" will your erase all current partitions and replace them with the factory images including the recovery, system, boot, data, etc.
Username invalid said:
Download the Nexus 7 4.2.2 factory package and unzip the contents to your ADB/Fastboot directory then reboot your device into Bootloader. Start > Run > CMD > cd (your directory) e.g. "cd c:/platform-tools" > "flash-all.bat" will your erase all current partitions and replace them with the factory images including the recovery, system, boot, data, etc.
Click to expand...
Click to collapse
thanks.
This way I has used and failed to recovery my nexus 7 to stock ROM. No error messages, all fastboot commands run successfully.
But the PA system is still exist...
Here are my logs, everything in fine...no error message.
But, reboot into the system, it still PA ROM, not stock ROM...
LMlatform-tools liming1$ ./fastboot oem unlock
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
LMlatform-tools liming1$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.022s]
finished. total time: 0.022s
LMlatform-tools liming1$ ./fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.033s]
finished. total time: 0.033s
LMlatform-tools liming1$ ./fastboot flash bootloader ~/Downloads/bootloader-grouper-4.18.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.300s]
writing 'bootloader'...
OKAY [ 0.594s]
finished. total time: 0.894s
LMlatform-tools liming1$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
LMlatform-tools liming1$ ./fastboot -w update ~/Downloads/nakasi-jdq39/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........: 015d2994xxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.023s]
sending 'boot' (4944 KB)...
OKAY [ 0.612s]
writing 'boot'...
OKAY [ 0.171s]
sending 'recovery' (5446 KB)...
OKAY [ 0.668s]
writing 'recovery'...
OKAY [ 0.188s]
erasing 'system'...
OKAY [ 0.024s]
sending 'system' (471804 KB)...
OKAY [ 56.425s]
writing 'system'...
OKAY [ 20.828s]
erasing 'userdata'...
OKAY [ 0.027s]
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 [ 23.105s]
erasing 'cache'...
OKAY [ 0.003s]
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.584s]
rebooting...
finished. total time: 103.851s
LMlatform-tools liming1$
Click to expand...
Click to collapse
The package includes the stock recovery, not a custom one. You can also flash stock images individually such as the system and data, which will restore the stock OS.
Username invalid said:
Download the Nexus 7 4.2.2 factory package and unzip the contents to your ADB/Fastboot directory then reboot your device into Bootloader. Start > Run > CMD > cd (your directory) e.g. "cd c:/platform-tools" > "flash-all.bat" will your erase all current partitions and replace them with the factory images including the recovery, system, boot, data, etc.
Click to expand...
Click to collapse
Username invalid said:
The package includes the stock recovery, not a custom one. You can also flash stock images individually such as the system and data, which will restore the stock OS.
Click to expand...
Click to collapse
Yes, I know the package included the stock recovery. I flashed it, but it didn't restore my nexus 7 to stock OS. My nexus 7 always running in PA ROM even I flashed all stock images.
thanks!
limingg said:
Yes, I know the package included the stock recovery. I flashed it, but it didn't restore my nexus 7 to stock OS. My nexus 7 always running in PA ROM even I flashed all stock images.
thanks!
Click to expand...
Click to collapse
Did you notice the problem immediately after install the new ROM or did it happen suddenly?
Username invalid said:
Did you notice the problem immediately after install the new ROM or did it happen suddenly?
Click to expand...
Click to collapse
I am not sure, I upgrade PA to 3.65 from 3.6 and flash franco r65 kernel yesterday.
Today I found some app FC and I delete my google account in setting, the magic happen, I reboot system and the google account come back...I try many times, even I delete a file and it will restore after reboot system.
So I feel my partition locked, I ca't flash anything or modify system. It is like that my nexus 7 freeze at a time. The PA ROM always exist, I can't flash( destory ) it.:crying::crying::crying:
Hi guys.
I have one Nexus 6p, SKU: H1511 and I have faced some persistent problem with boot loop problem stock in the Google screen logo (white) letters , I have rich the success to unlock bootloader, without system and the phone can be opened in the fastboot screen, but no recovery mode screen can be open, no restart, no BP tool,no Factory… only bootloader screen and working, I have try flash TWRP recovery but don’t work, I can start recovery mode, but in the flash, process says success (twrp3.1.1.4Cores), also I have flashed the (N2G48B_4Cores) and download many factory images and nothing… every time I have tried flash I get the info below in the picture..
OKAY [ 0.022s]
finished. total time: 0.023s
< waiting for any device >
target reported max download size of 494927872 bytes
sending 'radio' (48728 KB)...
OKAY [ 1.638s]
writing 'radio'...
OKAY [ 2.181s]
finished. total time: 3.819s
rebooting into bootloader...
OKAY [ 0.023s]
finished. total time: 0.023s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (12 MB) to disk... took 0.057s
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 (17 MB) to disk... took 0.070s
archive does not contain 'recovery.sig'
extracting system.img (2691 MB) to disk... took 99.269s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (194 MB) to disk... took 3.560s
archive does not contain 'vendor.sig'
wiping userdata...
CreateProcess failed: O sistema não pode encontrar o arquivo especificado. (2)
error: Cannot generate image for userdata
Press any key to exit...
I need a technical help about that.
Thanks and best regards
Have you tried flashing the manual way with fastboot commands? You can get all the commands and steps in the returning to stock threads.
Hi there
I've got an old Nexus 10 that recently got stuck in a bootloop, so I booted into recovery and did a factory reset. After a few boots and updates everything seemed ok, but then it just died and went into a bootloop again.
I've flashed TWRP recovery, but no partitions are mounted or mountable and attempts to repair file system make the screen go squiggly (corrupted/interference) and then the tablet reboots into bootloader.
Is this likely to be a hardware issue or is there more I can try?
Slainte
mmidders
P.S. also tried flashing the stock ROM using flash-all.sh, output appended:
erasing 'boot'...
OKAY [ 0.022s]
finished. total time: 0.023s
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.097s]
finished. total time: 0.097s
erasing 'recovery'...
OKAY [ 0.029s]
finished. total time: 0.029s
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.150s]
finished. total time: 0.150s
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.373s]
finished. total time: 0.373s
target didn't report max-download-size
sending 'bootloader' (1280 KB)...
OKAY [ 0.192s]
writing 'bootloader'...
OKAY [ 0.115s]
finished. total time: 0.307s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.454s
< waiting for any device >
extracting android-info.txt (0 MB)...
extracting boot.img (4 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB)...
archive does not contain 'recovery.sig'
extracting system.img (641 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-poiJRI: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
mke2fs failed: 1
error: Cannot generate image for userdata
Update:
I updated adb and fastboot and ran the flash-all.sh script again with the following output (now waiting for first boot):
Erasing 'boot' OKAY [ 0.022s]
Finished. Total time: 0.025s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'cache' OKAY [ 0.093s]
Finished. Total time: 0.095s
Erasing 'recovery' OKAY [ 0.025s]
Finished. Total time: 0.027s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'system' OKAY [ 0.150s]
Finished. Total time: 0.153s
******** Did you mean to fastboot format this ext4 partition?
Erasing 'userdata' OKAY [ 0.372s]
Finished. Total time: 0.375s
Sending 'bootloader' (1280 KB) OKAY [ 0.194s]
Writing 'bootloader' OKAY [ 0.132s]
Finished. Total time: 0.330s
Rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.453s
< waiting for any device >
--------------------------------------------
Bootloader Version...: MANTAMF01
Baseband Version.....: no modem
Serial Number........: R32F200S5XR
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' OKAY [ 0.001s]
extracting boot.img (4 MB) to disk... took 0.018s
archive does not contain 'boot.sig'
Sending 'boot' (4966 KB) OKAY [ 0.745s]
Writing 'boot' OKAY [ 0.118s]
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB) to disk... took 0.028s
archive does not contain 'recovery.sig'
Sending 'recovery' (5532 KB) OKAY [ 0.851s]
Writing 'recovery' OKAY [ 0.121s]
archive does not contain 'vbmeta.img'
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (641 MB) to disk... took 6.544s
archive does not contain 'system.sig'
Sending 'system' (657130 KB) OKAY [ 96.291s]
Writing 'system' OKAY [ 15.845s]
archive does not contain 'system_ext.img'
archive does not contain 'vendor.img'
Erasing 'userdata' OKAY [ 0.371s]
mke2fs 1.44.1 (24-Mar-2018)
/tmp/TemporaryFile-3eTxBH: Unimplemented ext2 library function while setting up superblock
/usr/lib/android-sdk/platform-tools/mke2fs failed with status 1
fastboot: error: Cannot generate image for userdata
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
I got a Pixel 4 today, and attempted to root it and royally messed it up. I seem to be soft bricked at the bootloader screen, recovery and factory reset do nothing, and flash-all.bat from the google factory files does not work also. I have been trying to fix it, running various commands from around the internet all day to no avail. I am not really sure what to do other than taking it in to a shop and seeing if they can do anything.
My biggest mistake was flashing a magisk modified .img file to the phone, which I wrongfully downloaded the oldest version for android 10, and once I flashed to my A13 phone it hasnt worked since. Just locked at the bootloader. I get a corrupted data warning also when booting
This is my log when trying to use flash-all.bat
When I attempt to flash them one by one from the contained zip file in the factory software, I get a similar sparse file error. I'm not too familiar with TWRP but I have tried multiple resets, repairs and other things with the storage on the phone. I'm not sure if TWRP will even boot anymore as it was having issues earlier
All I want to do now is just reset it to the stock version but I'm not sure if its even possible.
Any help would be really greatly appreciated
Sending 'bootloader_a' (8853 KB) OKAY [ 0.379s]
Writing 'bootloader_a' (bootloader) Flashing Pack version c2f2-0.5-8906123
(bootloader) Flashing partition table for Lun = 0
(bootloader) Flashing partition table for Lun = 1
(bootloader) Flashing partition table for Lun = 2
(bootloader) Flashing partition table for Lun = 4
(bootloader) Flashing partition table for Lun = 5
(bootloader) Flashing partition xbl_a
(bootloader) Flashing partition xbl_config_a
(bootloader) Flashing partition aop_a
(bootloader) Flashing partition tz_a
(bootloader) Flashing partition hyp_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition keymaster_a
(bootloader) Flashing partition devcfg_a
(bootloader) Flashing partition qupfw_a
(bootloader) Flashing partition uefisecapp_a
(bootloader) Flashing partition msadp_a
(bootloader) Flashing partition logfs
OKAY [ 0.259s]
Finished. Total time: 0.902s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.051s
Sending 'radio_a' (82724 KB) OKAY [ 2.319s]
Writing 'radio_a' (bootloader) Flashing Pack version SSD:g8150-00123-220708-B-8810441
(bootloader) Flashing partition modem_a
OKAY [ 0.654s]
Finished. Total time: 3.237s
Rebooting into bootloader OKAY [ 0.049s]
Finished. Total time: 0.050s
--------------------------------------------
Bootloader Version...: c2f2-0.5-8906123
Baseband Version.....: g8150-00123-220708-B-8810441
Serial Number........: 9B111FFAZ0047T
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.058s]
Checking 'version-bootloader' OKAY [ 0.067s]
Checking 'version-baseband' OKAY [ 0.066s]
Setting current slot to 'a' OKAY [ 0.079s]
extracting boot.img (64 MB) to disk... took 0.189s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 1.839s]
Writing 'boot_a' OKAY [ 0.460s]
archive does not contain 'init_boot.img'
extracting dtbo.img (8 MB) to disk... took 0.017s
archive does not contain 'dtbo.sig'
Sending 'dtbo_a' (8192 KB) OKAY [ 0.299s]
Writing 'dtbo_a' OKAY [ 0.130s]
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_a' (8 KB) OKAY [ 0.139s]
Writing 'vbmeta_a' OKAY [ 0.075s]
extracting vbmeta_system.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system_a' (4 KB) OKAY [ 0.139s]
Writing 'vbmeta_system_a' OKAY [ 0.076s]
archive does not contain 'vbmeta_vendor.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'vendor_kernel_boot.img'
extracting super_empty.img (0 MB) to disk... took 0.000s
extracting product.img (2440 MB) to disk... took 9.712s
extracting system.img (821 MB) to disk... took 3.327s
extracting system_ext.img (298 MB) to disk... took 1.156s
extracting system_other.img (23 MB) to disk... took 0.104s
extracting vendor.img (824 MB) to disk... took 3.368s
archive does not contain 'vendor_other.img'
Sending sparse 'super' 1/1 (4194303 KB) FAILED (Sparse file is too large or invalid)
fastboot: error: Command failed
Press any key to exit...
No help from this forum, fixed from going to platform tools 33.0 instead of the current 34.0
powertools1234 said:
No help from this forum, fixed from going to platform tools 33.0 instead of the current 34.0
Click to expand...
Click to collapse
GitHub - awake558/adb-win: adb.exe fastboot.exe
adb.exe fastboot.exe. Contribute to awake558/adb-win development by creating an account on GitHub.
github.com
C:\Users\Admin\Desktop\platform-tools_r33.0.3-windows\platform-tools
Copy all files to C:\Windows\System32 and C:\Windows\SysWOW64
Enter fastboot mode again, restart the machine, press the power button once, and then long press the mute button to enter fastboot mode.
PS: Windwos 10 and my device for Google Pixel 7.
powertools1234 said:
No help from this forum, fixed from going to platform tools 33.0 instead of the current 34.0
Click to expand...
Click to collapse
You saved my phone Thank you very much.