Database Users

Root&Recovery4Xperia Z2 Tablet MM Stock ROM Locked Bootloader (.575 .291) in 2 steps!

Root&Recovery4Xperia Z2 Tablet MM Stock ROM Locked Bootloader (.575 .291) in 2 steps!
--- [ introduction ]
this script is a recovery installer (TWRP) for Sony Xperia Z2 Tablet with Marshmallow Stock Rom (23.5.x) and works with locked bootloader.
the only requirement to the script work is to have a .575 kernel in the time of installation, you can flash another kernel later (.291 by example).
--- [ how to ]
step 1) flash Kernel 23.5.A.0.575 for TWRP boot [if you already have a listed .575 kernel, jump this step]
Kernel SGP511 23.5.A.0.575 (Customized UK) **SGP512 users reported that SGP511 kernel works flawlessy, offsets were checked and they match.
Kernel SGP521 23.5.A.0.575 (Customized UK)
Kernel SGP551 23.5.A.0.575 (Claro BR)
step 2) grab View attachment 3898241 and run install.bat to boot TWRP:Recovery & Root for Marshmallow
now install SuperSU (by the time of this post SR1-SuperSU-v2.78-SR1-20160915123031.zip) and if you want other stuffs like Xposed sdk 23 and enable Multi-Window
after all of this, you can flashback Kernel 23.5.A.1.291 back
Kernel 23.5.A.1.291 (Generic BR) (Mirror)
Enjoy! Cheers! :good::highfive:
--- [ complimentary ]
-Flashtool by @Androxyde
-SuperSU by @Chainfire's
______
--- [ .575 kernels iovyroot added ]
SGP511 Generic UK
SGP512 Generic UK TW
SGP521 Generic UK
SGP551 Claro BR
--- [ versions ]
TWRP 3.0.2-0
Installation Script: beta release 0.4
--- [ credits & thanks ]
@shoey63 for Recovery & Root for MM .575/.291 LB infos
@zxz0O0 for iovyroot
@gustavo_v for iovyroot offset explanation
@Nut for XZDualRecovery and TWRP's mods
@simply_proto, @XenTeckz, @anandfr for Z2 Tablet SGP521 SGP512 UK TW 23.5.A.0.575 kernel and test
@casouzaj for suggesting TWRP update
______
--- [ FAQ ]
Q: I have official Xperia 23.5.A.1.291, Can I flash 23.5.A.0.575 kernel over it?
A: Yes
Q: I have flashed 23.5.A.0.575 kernel and I like to flash back 23.5.A.1.291, Is it possible?
A: Yes
Q: I cannot find 23.5.A.0.575 kernel for my model, Is it possible to use an older kernel?
A: Yes probably, with a high success chance. It will require to modify iovyroot, just follow the instructions to request.
Q: I have LL and I'd like to root it, is it possible?
A: Yes, just follow the instructions to request iovyroot modification.
Q: Will I lose TA partition?
A: No, that's why it works with a locked bootloader
______
--- [ requesting your model ]
please upload and post your kernel firmware ftf (must be .575) file and version
to retrieve your kernel version run: adb shell cat /proc/version
(it must be similar to Linux version 3.4.0-perf-g43ea728 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Apr 22 17:27:56 2016)
______
--- [ download ]
View attachment 3898241
crc32: A6FA85E6
md5: ACBEAF8EAD78D8883D86925062FC0C6A
sha256: 8282DCD3E952A50A3080FB0BCE7F4EA810FE13705D314ED44232E3A30789BAB1

After 4 months of looking for root this works 100%

I can confirm it works on my Z2 tablet as well. Thank you very much! No longer will i have to be pulling my hair out.

Fantastic everything works. Well thank you.

hey guys,
I cant flash the kernel for my spg521 with flashtool, i got this error:
8/042/2016 22:42:42 - INFO - Now plug your device in Fastboot Mode
18/042/2016 22:42:48 - INFO - Selected kernel (boot.img or kernel.sin): C:\Users\hosnf\Documents\newFLASH2016\z2 TABLET\kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
18/042/2016 22:42:48 - INFO - HotBooting selected kernel
18/042/2016 22:42:49 - INFO - FASTBOOT Output:
creating boot image...
creating boot image - 11577344 bytes
downloading 'boot.img'...
OKAY [ 0.358s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.408s
this error from your bat.file:
kdir: '/data/local/tmp/mm_twrp_recovery_install': File exists
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
[100%] /data/local/tmp/mm_twrp_recovery_install
chmod: /data/local/tmp/mm_twrp_recovery_install/busybox: Not a directory
chmod: /data/local/tmp/mm_twrp_recovery_install/install_twrp_recovery.sh: Not a directory
chmod: /data/local/tmp/mm_twrp_recovery_install/iovyroot: Not a directory
chmod: /data/local/tmp/mm_twrp_recovery_install/modulecrcpatch: Not a directory
/system/bin/sh: /data/local/tmp/mm_twrp_recovery_install/iovyroot: not found
Finished!
Click to expand...
Click to collapse
hopefully, you can help me!
thx

Hi, I am on SGP512 23.5.A.0.575 stock.
How can I extract it, so I can go back to it, after rooting? Or maybe you have 512 version of custom kernel?
Thanks

And I am getting this:
sending 'boot' (11303 KB)...
OKAY [ 0.378s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.381s

wrong kernel?
rybaryba33 said:
And I am getting this:
sending 'boot' (11303 KB)...
OKAY [ 0.378s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.381s
Click to expand...
Click to collapse
yep, i got same error!
I tried to replace the original kernel with this kernel in the firmware ftf-file and to install it with the flashtool about flashmode ... but its not working, when reboot in system the original kernel will not change with adb about cmd, i got this error: kernel cant upload
Maybee someone can explain how to flash the kernel or is the wrong kernel uploaded?
Thank you

Yeah got the same error I think I'll just downgrade it do it that way.

peterge said:
Fantastic everything works. Well thank you.
Click to expand...
Click to collapse
How you are installed the kernel? I think the uploeded kernel for the 521 is wrong? !?

smoschi said:
How you are installed the kernel? I think the uploeded kernel for the 521 is wrong? !?
Click to expand...
Click to collapse
I'm proceeded follows:
1) open XperiaFirm (from Flashtool), download and flash your desired MM.
download and flash http://forum.xda-developers.com/xperia-z2-tablet/general/ftf-vmo-ru-ua-kz-t3382673
2)Wait until you boot this ROM, enable USB debugging and start point 3
3) now grab the script and run install.bat (pop up message, which confirmed) to boot TWRP: Recovery & Root for Marshmallow
4)On the SD card you have downloaded or TWRP connect - mount SD card and Copy
now install SuperSU (by the time of this post UPDATE-SuperSU-v2.76-20160630161323.zip) and other stuffs like Xposed sdk 23 and enable Multi-Window
5)flash http://forum.xda-developers.com/xpe...gp521-vmo-ruuakz-flashable-prerooted-t3437936
Note: Of course I did everything Full Wipe and then settings and apk installed from the beginning.

Delete

danalec said:
Xperia Z2 Tablet Marshmallow Working ROOT for Stock ROM with Locked Bootloader
:laugh:
--- [ requirements ]
-Flashtool by @Androxyde
-SuperSU by @Chainfire's
-Recovery & Root for Marshmallow by me
--- [ .575 kernels iovyroot added ]
SGP511 Generic UK
SGP521 Generic UK
SGP551 Claro BR
--- [ versions ]
TWRP 3.0.2.0
Installation Script: beta release 0.2
--- [ how to ]
1) open XperiaFirm (from Flashtool), download and flash your desired MM.
2) you must flash Kernel 23.5.A.0.575 temporary for TWRP boot
Kernel SGP511 23.5.A.0.575 (Customized UK)
Kernel SGP521 23.5.A.0.575 (Customized UK)
Kernel SGP551 23.5.A.0.575 (Claro BR) (Mirror)
3) now grab the script and run install.bat to boot TWRP: Recovery & Root for Marshmallow (Mirror)
4) now install SuperSU (by the time of this post UPDATE-SuperSU-v2.76-20160630161323.zip) and other stuffs like Xposed sdk 23 and enable Multi-Window
5) OPTIONAL: flashback Kernel 23.5.A.1.291 back
Kernel 23.5.A.1.291 (Generic BR) (Mirror)
Enjoy! Cheers! :good::highfive:
--- [ credits & thanks ]
@shoey63 for Recovery & Root for MM .575/.291 LB infos
@zxz0O0 for iovyroot
@gustavo_v for iovyroot offset explanation
@Nut for XZDualRecovery and TWRP's mods
@simply_proto and @XenTeckz for Z2 Tablet SGP521 UK 23.5.A.0.575 kernel and test
@casouzaj for suggesting TWRP update
--- [ requesting your model ]
please upload and post your kernel firmware ftf (must be .575) file and version
to retrieve your kernel version run: adb shell cat /proc/version
(it must be similar to Linux version 3.4.0-perf-g43ea728 ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Fri Apr 22 17:27:56 2016)
--- [ todo ]
visual guide and more explanation like how to activate USB debug mode etc.
--- [ FAQ ]
Q: I have official Xperia 23.5.A.1.291, Can I flash 23.5.A.0.575 kernel over it?
A: Yes
Q: I have flashed 23.5.A.0.575 kernel and I like to flash back 23.5.A.1.291, Is it possible?
A: Yes
Q: I cannot find 23.5.A.0.575 kernel for my model, Is it possible to use an older kernel?
A: Yes probably, high success chance. Obviously it will require to modify iovyroot, just follow the instructions to request it.
View attachment 3839766
View attachment 3840696
Click to expand...
Click to collapse
Sorry if this question is noob.
I have MM already updated in my SGP511 via OTA. I want root and xposed framework. I know how to use flashtool. I just want to confirm my steps are correct or not?
STEPS
1. Since i already have MM, i just need to use flashtool to flash kernel .275 for TWRP boot via flashmode? Is this recovery temporary only? How to have a perm recovery installed? After flashing...i go to step 2 or do i reboot before running script?
2. grab the script and run install.bat to boot TWRP: Recovery & Root for Marshmallow
---------- Post added at 11:20 AM ---------- Previous post was at 11:12 AM ----------
Another question, using Flashtoool, do i fastboot to Doomlord "flash kernel" to flash the .275 kernel?
using Flashmode, it can't detect this file: kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.sin

ataraxist said:
1. Since i already have MM, i just need to use flashtool to flash kernel .275 for TWRP boot via flashmode?
Click to expand...
Click to collapse
.291, please read the entire post again.
ataraxist said:
Is this recovery temporary only? How to have a perm recovery installed? After flashing...i go to step 2 or do i reboot before running script?
Click to expand...
Click to collapse
It depends what are you going to flash after installing recovery.
Most of users would install an entire full rom over the previous stock rom.

I'm having an issue with this. I've flashed 291 for SGP511 and it boots fine.
I then flash the. 575 kernel, it comes back with a failed command error. I then use the bat file, but it does not boot me in to twrp recovery.
Any idea what I am doing wrong?
Sent from my SM-G928F using Tapatalk

guys, post error log
if it appears the "file exists", just remove it in your tmp folder

danalec said:
guys, post error log
if it appears the "file exists", just remove it in your tmp folder
Click to expand...
Click to collapse
@danalec, @shoey63 edited the recovery script in his last two updates, in the Z3 thread, that deletes the directory prior to actually pushing the files to the device. Perhaps you could edit yours too, in order to avoid unnecessary complaints. BR!

Could somebody advise how I can get the kernel to flash and how I can get it to then boot in to TWRP Recovery?
Thanks

I'm also having issues to flash 575 kernel.
Flashtool output:
07/012/2016 21:12:15 - INFO - Selected kernel (boot.img or kernel.sin): D:\Sony\flashtool home\x\kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
07/012/2016 21:12:15 - INFO - Flashing selected kernel
07/012/2016 21:12:15 - INFO - sending 'boot' (11287 KB)...
07/012/2016 21:12:15 - INFO - OKAY [ 0.356s]
07/012/2016 21:12:15 - INFO - writing 'boot'...
07/012/2016 21:12:15 - INFO - FAILED (remote: image is not a boot image)
07/012/2016 21:12:15 - INFO - finished. total time: 0.359s
07/012/2016 21:12:15 - INFO - FASTBOOT Output:
sending 'boot' (11287 KB)...
OKAY [ 0.356s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.359s

veepee78 said:
I'm also having issues to flash 575 kernel.
Flashtool output:
07/012/2016 21:12:15 - INFO - Selected kernel (boot.img or kernel.sin): D:\Sony\flashtool home\x\kernel_S1-SW-LIVE-9C84-PID1-0006-MMC.sin
07/012/2016 21:12:15 - INFO - Flashing selected kernel
07/012/2016 21:12:15 - INFO - sending 'boot' (11287 KB)...
07/012/2016 21:12:15 - INFO - OKAY [ 0.356s]
07/012/2016 21:12:15 - INFO - writing 'boot'...
07/012/2016 21:12:15 - INFO - FAILED (remote: image is not a boot image)
07/012/2016 21:12:15 - INFO - finished. total time: 0.359s
07/012/2016 21:12:15 - INFO - FASTBOOT Output:
sending 'boot' (11287 KB)...
OKAY [ 0.356s]
writing 'boot'...
FAILED (remote: image is not a boot image)
finished. total time: 0.359s
Click to expand...
Click to collapse
If your bootloader is locked, you cannot use fastboot. Select flashmode, instead.

Nexus 6P BOOTLOOP AND FLASH PROBLEMS

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.

Writing partition failed flashing raw file

Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?

rexendz said:
Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?
Click to expand...
Click to collapse

Error mode - Func 11 and 2

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

How To Guide How to unbrick Nothing Phone 1 fastboot bootloop

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