Instal Blackberry priv Non US Carrier autoloader on AT&T

Instal Blackberry priv Non US Carrier autoloader on AT&T - BlackBerry Priv

Hey
Is it possible to install Non US Carrier autoloader on AT&T to get rid of AT&T bloatware and to getting latest update via OTA?
Because I am live outs the US and did not have AT&T SIM.
Sent from my STV100-1 using Tapatalk

Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.

Thank you.
Sent from my iPad using Tapatalk

I did it today. It is woks perfectly. Thank you a lot :good:

I had a typo in my post regarding how to avoid wiping data while flashing. The 2nd command to comment out should be "flash userdata %IMG%\userdata.img".

Hey Kraml, your solution has a lot of interested folks over at Crackberry. Can you post some more detailed instructions?
Better yet, if you have an autoloader that's Marshmellow based already set up and share it with the community you'd become an instant rock star!
Here's the thread I started:
forums dot crackberry dot com/blackberry-priv-f440/potential-solution-our-vzw-att-friends-older-roms-1085292/#post12578681
replace dots with periods to get the link!

Does this convert AT&T to factory unlock??

zed011 said:
Does this convert AT&T to factory unlock??
Click to expand...
Click to collapse
No. It removes ATT software only.

kraml said:
I had a typo in my post regarding how to avoid wiping data while flashing. The 2nd command to comment out should be "flash userdata %IMG%\userdata.img".
Click to expand...
Click to collapse
Hey i have tried as you said and removed both the lines "fastboot.exe oem securewipe" "flash userdata %IMG%\userdata.img" from flashall.bat But i am getting the following error.
I am using AT and T unlocked device and i have tried the AT and T version AAG202 an i am getting the following error
Could you please help me out
BY INSTALLING THE SOFTWARE, YOU ARE AGREEING TO BE BOUND BY THE BlackBerry
Solution License Agreement which can be reviewed at www.blackberry.com/leg-
al/bbsla. IF YOU HAVE ANY QUESTIONS OR CONCERNS ABOUT THE TERMS OF THIS AG-
REEMENT, PLEASE CONTACT blackberry AT [email protected]. PLEASE READ
THIS DOCUMENT CAREFULLY BEFORE INSTALLING OR USING THE SOFTWARE.
***************************************************************************
Note:If device is not in fastboot mode
Please switch to fastboot mode by holding the power and volume down key for 30s
This script will wipe off all user data. Do you want to continue? [y/n]:y
'.\host\windows-x86\bin' is not recognized as an internal or external command,
operable program or batch file.
"It may take 5 to 15 minutes to securely wipe the device"
target reported max download size of 536870912 bytes
sending 'tz' (560 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.015s
target reported max download size of 536870912 bytes
sending 'hyp' (92 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'sdi' (27 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.019s
target reported max download size of 536870912 bytes
sending 'pmic' (32 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.018s
target reported max download size of 536870912 bytes
sending 'rpm' (187 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.027s
target reported max download size of 536870912 bytes
sending 'sbl1' (495 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.032s
target reported max download size of 536870912 bytes
sending 'aboot' (1453 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.027s
target reported max download size of 536870912 bytes
sending 'bootsig' (0 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.020s
target reported max download size of 536870912 bytes
sending 'recoverysig' (0 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'boot' (17908 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.016s
target reported max download size of 536870912 bytes
sending 'recovery' (17908 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.021s
target reported max download size of 536870912 bytes
erasing 'cache'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.021s
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing
partitions
flashing unlock unlocks the device. Allows user to
flash any partition except the ones
that are related to bootloader
flashing lock_critical Prevents flashing bootloader related
partitions
flashing unlock_critical Enables flashing bootloader related
partitions
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce
flashing unlock_bootloader <request> Issue unlock bootloader using request
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
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 [bootloader] reboot device, optionally into bootloader
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.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
target reported max download size of 536870912 bytes
sending 'modem' (68433 KB)...
FAILED (remote: authboot command permission denied)
finished. total time: 0.014s
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.016s
target reported max download size of 536870912 bytes
erasing 'oem'...
FAILED (remote: authboot command permission denied)
finished. total time: 0.015s
rebooting...
finished. total time: 0.008s
Press any key to close this window

its because your phone has password protection. simply remove password / pin or pattern lock screen

Could someone make a file the that is the AT&T update package minus the bloatwear and without the wipe. I would gladly donate for it working.
Sent from my STV100-1 using Tapatalk
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
Dilini said:
its because your phone has password protection. simply remove password / pin or pattern lock screen
Click to expand...
Click to collapse
Could someone make the file for our AT&T Priv, minus the firmware and where it doesn't wipe the device. I would gladly pay for it!
Sent from my STV100-1 using Tapatalk

Ew, buddy I've done for myself with the instruction pretty easy except PIN password part.
I've pack whole files as a size 1.6GB 7z file, based on my carrier upload limit it's too big to uploading it, estimate more than an hour, so I packed the "Patch"
part for u, which means u still need to access the official site to download AT&T part and decompress it http://global.blackberry.com/content/blackberry-com/en/support/smartphones/Android-OS-Reload.html
Then download my "Patch" part https://drive.google.com/open?id=0B-qpp_ciC37MUEVmSDYzR3c2OXc
Decompress it any where u like then copy it to the folder where your AT&T files decompressed, confirm overwrite the same name files.
Then just run the flashall.bat
And yes I only modified Windows version
theusername said:
Could someone make a file the that is the AT&T update package minus the bloatwear and without the wipe. I would gladly donate for it working.
Sent from my STV100-1 using Tapatalk
---------- Post added at 11:28 PM ---------- Previous post was at 11:25 PM ----------
Could someone make the file for our AT&T Priv, minus the firmware and where it doesn't wipe the device. I would gladly pay for it!
Sent from my STV100-1 using Tapatalk
Click to expand...
Click to collapse

Good morning, I have a question, recently bought the BlackBerry priv AT & T unlocked, I wonder if I can put Android's own BlackBerry 6 clean without losing the unlock? or I have to put the AT & T it? I run the risk of having a locked phone? Excuse my English.

Do we know if this is an error which can be ignored safely or there is fix for this?
error: cannot load '.\img\cache.img.\host\windows-x86\bin\fastboot.exe'
target reported max download size of 536870912 bytes

Hello!
May i ask a question does your patch can work with new version AAG873?
Thanks for your kind reply
loachh said:
Ew, buddy I've done for myself with the instruction pretty easy except PIN password part.
I've pack whole files as a size 1.6GB 7z file, based on my carrier upload limit it's too big to uploading it, estimate more than an hour, so I packed the "Patch"
part for u, which means u still need to access the official site to download AT&T part and decompress it http://global.blackberry.com/content/blackberry-com/en/support/smartphones/Android-OS-Reload.html
Then download my "Patch" part https://drive.google.com/open?id=0B-qpp_ciC37MUEVmSDYzR3c2OXc
Decompress it any where u like then copy it to the folder where your AT&T files decompressed, confirm overwrite the same name files.
Then just run the flashall.bat
And yes I only modified Windows version
Click to expand...
Click to collapse

And also: Could you do a Mac Version as well?
Greetings from Germany

Did anyone else that did this get an OTA update notification today? I'm actually surprised I would get something considering I'm not using an AT&T simcard.
Update:
Looks like this is the reason why I received the OTA update. Blackberry is starting to support the unlocked AT&T phones. http://www.techtimes.com/articles/1...receives-updates-directly-from-blackberry.htm

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
I just did this on the Verizon variant, which i'm using on T-Mobile in the US, and it is insane how much better it's running. I'm pretty sure everyone should do this if they don't have the factory unlocked model

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Run flashall script in AT&T autoloader to flash your phone as usual, you will be upgraded to the latest AT&T ROM without those AT&T bloatware.
Bonus:
If you would like to preserve data when flashing autoloaders, i.e. upgrade without reset your phone to factory default, follow this:
Open flashall script and comment out two lines that run below commands:
fastboot.exe oem securewipe
flash userdata %IMG%\userdata.img
Then run flashall script as usual.
Above are all tested on my phone without problem.
Click to expand...
Click to collapse
Do you know if this will work on a verizon branded model? I am looking at a VZ model for cheap but will be using it on Tmo, on a side note anyone know if the VZ model supports wifi calling on Tmo? Thanks.

kraml said:
Here is what I have done with my AT&T Priv.
1. Download both AT&T and common non-US carrier autoloader archives from BB website and extract them to separate folders. Make sure to download the closest versions of the two autoloaders.
2. Replace img/oem.img file in AT&T autoloader with the one from common autoloader.
Click to expand...
Click to collapse
I have additionally also replaced system.img with the one from the common autoloader. Otherwise the "System update" wouldn't do anything. Now I get the normal Android update screen, the not dreaded "AT&T Software update". I hope that it'll actually update.
Stefan

Related

[Request]Stock 4.1.2 Firware for Aus xt905

Recently I attempted to flash a custom rom after root and unlocking my bootloader on my Australia xt905. Unfortunately I made the rookie mistake no backup stock rom to fallback on. After a frustrating soft brick I finally got it on but now its running on xt907 firmware. Best I could do. In an effort to get some functionality back I have tried custom roms which have worked and am currently runnning the xt907 carbon rom on 4.2.2 But still cannot get the cellular to work. I have looked for a stock 4.1.2 but am unable to find it anywhere. Is there anyone that has a copy?

TheSpecificOcean said:
Recently I attempted to flash a custom rom after root and unlocking my bootloader on my Australia xt905. Unfortunately I made the rookie mistake no backup stock rom to fallback on. After a frustrating soft brick I finally got it on but now its running on xt907 firmware. Best I could do. In an effort to get some functionality back I have tried custom roms which have worked and am currently runnning the xt907 carbon rom on 4.2.2 But still cannot get the cellular to work. I have looked for a stock 4.1.2 but am unable to find it anywhere. Is there anyone that has a copy?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2169220&highlight=xt905

aviwdoowks said:
http://forum.xda-developers.com/showthread.php?t=2169220&highlight=xt905
Click to expand...
Click to collapse
Yes I have this file now thanks but am having trouble flashing installation is aborted error in cwm whenever I try

TheSpecificOcean said:
Yes I have this file now thanks but am having trouble flashing installation is aborted error in cwm whenever I try
Click to expand...
Click to collapse
Post all the details!!
---------- Post added at 04:57 PM ---------- Previous post was at 04:54 PM ----------
Use this http://forum.xda-developers.com/showthread.php?t=2246081
The original not my vzw workaround.

aviwdoowks said:
Post all the details!!
Click to expand...
Click to collapse
After clearing cache and dalvik cache then factory reset i run the retail version of the zip from the link earlier using cwm recovery and it says
installing 9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_1FF_fb.xml.zip
finding update package...
opening update package...
installing update...
installation aborted...
And thats it nothing else comes up. I wanting to try using rds lite 6.1.4 but my device is refusing to show up and i have all the neccessary drivers.

TheSpecificOcean said:
After clearing cache and dalvik cache then factory reset i run the retail version of the zip from the link earlier using cwm recovery and it says
installing 9.8.2Q_SMUIRD-7_SEMEAUnlk_USAXT90501TLSTRAE1019.0R_SMJBLTEAURETAIL_P008_A014_1FF_fb.xml.zip
finding update package...
opening update package...
installing update...
installation aborted...
And thats it nothing else comes up. I wanting to try using rds lite 6.1.4 but my device is refusing to show up and i have all the neccessary drivers.
Click to expand...
Click to collapse
The xml needs rsd. What is your computer?
Mac needs parallels desktop.
Try ap fastboot mode from the bootloader screen.

aviwdoowks said:
The xml needs rsd. What is your computer?
Mac needs parallels desktop.
Try ap fastboot mode from the bootloader screen.
Click to expand...
Click to collapse
I'm running a custom built PC running win 8 pro build 9600 and I'll try this when I get back currently away for Christmas holidays.

TheSpecificOcean said:
I'm running a custom built PC running win 8 pro build 9600 and I'll try this when I get back currently away for Christmas holidays.
Click to expand...
Click to collapse
Get rsd 615.

aviwdoowks said:
Get rsd 615.
Click to expand...
Click to collapse
Couldn't get rdslite 6.1.5 to show device either but did manage to get the fastboot.bat to work. Unfortunately this failed as well was getting variable not supported errors above each stage and then would get fastboot.exe has stopped working errors mid flash but the command would continue after closing program. Have been reading that win 8 may be the cause of this will try on a win xp computer and if i can get my hands on a win7 if that doesn't work

TheSpecificOcean said:
Couldn't get rdslite 6.1.5 to show device either but did manage to get the fastboot.bat to work. Unfortunately this failed as well was getting variable not supported errors above each stage and then would get fastboot.exe has stopped working errors mid flash but the command would continue after closing program. Have been reading that win 8 may be the cause of this will try on a win xp computer and if i can get my hands on a win7 if that doesn't work
Click to expand...
Click to collapse
I use w7.

aviwdoowks said:
I use w7.
Click to expand...
Click to collapse
just tried xp was a no go but am going away again tomorrow till the 5/1. Will try again then got it back to the stock xt907 firmware. I guess that will have to do for now. Is there any xt905 compatible roms by any chance. I have managed to get both the carbon xt907 and unofficial xt905 of akop but neither were getting reception or less than one bar on the odd occasion. Would a gsm fix this? As i have been unable to get my hands on one every link seems to be broken

TheSpecificOcean said:
just tried xp was a no go but am going away again tomorrow till the 5/1. Will try again then got it back to the stock xt907 firmware. I guess that will have to do for now. Is there any xt905 compatible roms by any chance. I have managed to get both the carbon xt907 and unofficial xt905 of akop but neither were getting reception or less than one bar on the odd occasion. Would a gsm fix this? As i have been unable to get my hands on one every link seems to be broken
Click to expand...
Click to collapse
Did you try this http://forum.xda-developers.com/showthread.php?t=2246081
St.Noigel knows a lot about gsm.

aviwdoowks said:
Did you try this http://forum.xda-developers.com/showthread.php?t=2246081
St.Noigel knows a lot about gsm.
Click to expand...
Click to collapse
no i haven't i am going to try the ose 4.3 with a 4.3 gsm fix and if that fails i will try that one it will respond with results maybe if i have time
EDIT: OSE didn't work gonna try the link u posted
Edit: Finally got the rom u posted above to work but no improvement the service didnt improve however i noticed i was unable to select any other band types from the mobile networks menu

I'm a bit off topic after all this but what i'm effectively looking for is a backup that can be flashed via CWM or installed via zip. I cannot for the life of me get fastboot or rdslite to work. The files from the http://forum.xda-developers.com/show...ighlight=xt905 are all fastboot files and can't be installed by CWM from zip. Or alternatively a working xt905 rom because at the moment all unofficial or official versions with gsm fixes are unable to find any cellular in Australia. I'm currently with Telstra through ALDImobile at the moment if it helps, not looking for lte just h+ or 3g if possible. At the moment i'm stuck with a glorified mp3 player.

I thought i might post the log from the fastboot attempts when im using the fastboot that comes with the retail stock firmware. I noticed some that looked out of place and have searched them but found nothing that helped main culprits being
(bootloader) Variable not supported!
(bootloader) Preflash validation failed
Invalid sparse file format at header magi
Code:
Flashing bootloader images ...
So as to use latest flash capabilities
< waiting for device >
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'partition' (32 KB)...
OKAY [ 0.012s]
writing 'partition'...
FAILED (remote failure)
finished. total time: 0.284s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl1' (101 KB)...
OKAY [ 0.018s]
writing 'sbl1'...
OKAY [ 0.559s]
finished. total time: 0.578s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl2' (126 KB)...
OKAY [ 0.019s]
writing 'sbl2'...
OKAY [ 0.929s]
finished. total time: 0.948s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'sbl3' (512 KB)...
OKAY [ 0.049s]
writing 'sbl3'...
OKAY [ 1.111s]
finished. total time: 1.160s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'rpm' (140 KB)...
OKAY [ 0.017s]
writing 'rpm'...
OKAY [ 0.552s]
finished. total time: 0.570s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'tz' (192 KB)...
OKAY [ 0.023s]
writing 'tz'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.319s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'aboot' (256 KB)...
OKAY [ 0.025s]
writing 'aboot'...
OKAY [ 0.827s]
finished. total time: 0.853s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.008s
Flashing modem SW...
error: < waiting for device >
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'fsg' (2825 KB)...
OKAY [ 0.221s]
writing 'fsg'...
OKAY [ 1.169s]
finished. total time: 1.391s
(bootloader) Variable not supported!
erasing 'modemst1'...
OKAY [ 0.617s]
finished. total time: 0.618s
(bootloader) Variable not supported!
erasing 'modemst2'...
OKAY [ 0.613s]
finished. total time: 0.613s
Flashing AP Images...
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'logo' (854 KB)...
OKAY [ 0.071s]
writing 'logo'...
OKAY [ 1.120s]
finished. total time: 1.190s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'devtree' (512 KB)...
OKAY [ 0.047s]
writing 'devtree'...
OKAY [ 0.348s]
finished. total time: 0.395s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'boot' (10240 KB)...
OKAY [ 0.789s]
writing 'boot'...
OKAY [ 2.806s]
finished. total time: 3.595s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
sending 'recovery' (10240 KB)...
OKAY [ 0.790s]
writing 'recovery'...
OKAY [ 2.002s]
finished. total time: 2.794s
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
(bootloader) Variable not supported!
target reported max download size of 31457280 bytes
Invalid sparse file format at header magi
(bootloader) Variable not supported!
erasing 'tombstones'...
OKAY [ 0.801s]
finished. total time: 0.801s
(bootloader) Variable not supported!
erasing 'cache'...
OKAY [ 1.045s]
finished. total time: 1.045s
Erasing userdata...
(bootloader) Variable not supported!
erasing 'userdata'...
OKAY [ 4.423s]
finished. total time: 4.423s
All images flashed. Check logs for errors!
Press any key to continue . . .

http://forum.xda-developers.com/showthread.php?t=2169220&page=2 just found this which solves half my problem any ideas on getting rdslite to work is it a win 8 issue maybe

FIXED i finally got it to flash using fastboot. The errors were occuring because there wasn't a fastboot.exe in the files with the firmware. I read on another post that they needed to copy a fastboot across. After trying this it fixed.

TheSpecificOcean said:
FIXED i finally got it to flash using fastboot. The errors were occuring because there wasn't a fastboot.exe in the files with the firmware. I read on another post that they needed to copy a fastboot across. After trying this it fixed.
Click to expand...
Click to collapse
Would you post a screen shot of the bottom half of your about phone page?

aviwdoowks said:
Would you post a screen shot of the bottom half of your about phone page?
Click to expand...
Click to collapse
yeah sure

reflash factory image, remove twrp

I'm trying to reflash factory image to my Nexus player. Everything I've tried ends in an error. I have flashed alot of things (Nvidia Shield, Nexus player, Adt-1, Fire tv, Phones) so I'm not a total newbie but this has me scratching my head. It has TWRP installed and lineage 15.1 nightly flashed to it. I'm selling it so want to go back to factory. Any help would be appreciated. Thanks in advance.

Ok I can flash Lineage Os no problem. II can flash Pure Nexus no problem. When I try to flash a factory image it always errors. Here is what shows in Minimal adb.
C:\Program Files (x86)\Minimal ADB and Fastboot>flash-all.bat
target reported max download size of 536870912 bytes
sending 'bootloader' (12260 KB)...
OKAY [ 1.588s]
writing 'bootloader'...
OKAY [ 4.586s]
finished. total time: 6.185s
rebooting into bootloader...
OKAY [ 0.576s]
finished. total time: 0.590s
< waiting for any device >
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (7 MB) to disk... took 0.033s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (9 MB) to disk... took 0.053s
archive does not contain 'recovery.sig'
extracting system.img (972 MB) to disk... took 5.153s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
CreateProcess failed: The system cannot find the file specified. (2)
error: Cannot generate image for userdata
Press any key to exit...

I had the same issue. TWRP was still there, so I wiped System and Cache and formatted Data from TWRP (not sure if this is needed). I unzipped the archive that has the factory images on my laptop and rebooted into the bootloader and and ran:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Worked perfectly. Note that this erases everything and the device will boot to the setup screen, just like new.

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

Magisk Pixel4 Failed to write to partition Bad Buffer Size

Receiving the following error.. bootp is my patched image.
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot C:\Users\Scott\Pictures\bootp.img
target reported max download size of 268435456 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.656s]
writing 'boot_a'...
(bootloader) Image missing cmdline or OS version
FAILED (remote: Failed to write to partition Bad Buffer Size)
finished. total time: 2.954s

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

Database Users

welcome