General [ROM][Restore][Unbrick] Nothing OS v1.5.3(HotFix) Global/EEA Fastboot ROM(Full ROM) & boot.img & QFIL ROM (EDL)

Search This thread
Update! : 2023/03/23 4:46 (UTC+9:00)
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.5.3(HotFix) is available.
Sorry for my poor English, I'm Japanese...

News: The DSU has been restored in this version. It seems to be usable as long as it is non-root.🎉

The content of this site has been changed because Global and EEA have merged. (Global)" section is for Global only.
I think v1.5.1 or later can be used for all types.

I selfishly want the EEA version.(White..!)
I'd like to do some verification and such.


Attention!
This fastboot ROM requires 'fastboot flashing unlock' and 'fastboot flashing unlock_critical'(Option)!

2023/02/13 0:44 (UTC+9:00)
Add QFIL ROM (⚠EDL Command or EDL Cable V1/V2 Required)

I haven't tried it myself; there is Firehose, so you can use it however you like.
 
Last edited:

pankspoo

Senior Member
Jun 27, 2013
1,871
987
in front of ENCHILADA
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.7 is available. Sorry for my poor English, I'm Japanese...

Warning: There is a problem with this version that makes the DSU Loader unusable.
GSI users should avoid this version.

Thx! AVB Delenda Est
Does falshing script is available inside the zip
 

JazonX

Senior Member
Dec 16, 2009
2,296
893
Xiaomi Mi 11 Ultra
Bat file fails because it has a ./ command in front of the image name, Probably meant for linux.
Just remove it and run it. I merged both files and flashed both slots along with the Delta patched boot image.

Also, stock fastboot file cannot flash the big super image - it fails at 7/9



Edit - Used a short cable to flash super.img and it worked.

ROM works and boots fine. Everything good here.
 
Last edited:
Bat file fails because it has a ./ command in front of the image name, Probably meant for linux.
Just remove it and run it. I merged both files and flashed both slots along with the Delta patched boot image.

Also, stock fastboot file cannot flash the big super image - it fails at 7/9



Edit - Used a short cable to flash super.img and it worked.

ROM works and boots fine. Everything good here.
I didn't prepare a script for Linux and there was a problem with the command description... Sorry.
How about super.img Flash with fastbootd? I have already compressed it with simg.
 
日本語で悪い。
DSUが使えない問題があったりしたんで今まで自分がFastboot ROMを作る方法をPastebinに記しておいた。バックアップにはMagiskでのroot環境かSUが入ったGSIが必要になる。
Magiskの方法は、Magiskのパッチをしていないboot.imgが必要になるのでGSIの方法が簡単だったりする。この方法はimgが存在しない機種にも使えたりする。
この日本語の文章が読めた人は参考にやって見て欲しい。
 
日本語で悪い。
DSUが使えない問題があったりしたんで今まで自分がFastboot ROMを作る方法をPastebinに記しておいた。バックアップにはMagiskでのroot環境かSUが入ったGSIが必要になる。
Magiskの方法は、Magiskのパッチをしていないboot.imgが必要になるのでGSIの方法が簡単だったりする。この方法はimgが存在しない機種にも使えたりする。
この日本語の文章が読めた人は参考にやって見て欲しい。
因みにimgをFlashするbatファイルはこれ。参考にして欲しい。
必要なimgもそれを参考にすれば多分大丈夫。
super.imgはimg2simgでスパースイメージにしておくと処理が早くなります。容量も少し減るので時間があったらしておくと良いと思う。
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Thanks for the operation report.
    I have dared to separate the a slot from the b slot because it seems that the ROM will not start unless it is in a certain slot.

    Hello, i flashed 1.5.2 via fastbootd (command: adb reboot bootloader to get to fastbootd)
    flashing slot b works flawless and
    i can flash crictical paritions without unlocking critical paritions !
    (thanks to @TheNewHEROBRINE for the idea which i tested and worked for me flawless first try)

    What's still not working is to flash slot a where i get bootloop to bootloader. I need to manually changed the active slot to b again to properly start the phone again, if slot b was already flashed).

    Best Regard's

    Alex1911
    1
    Hello, i flashed 1.5.2 via fastbootd (command: adb reboot bootloader to get to fastbootd)
    flashing slot b works flawless and
    i can flash crictical paritions without unlocking critical paritions !
    (thanks to @TheNewHEROBRINE for the idea which i tested and worked for me flawless first try)

    What's still not working is to flash slot a where i get bootloop to bootloader. I need to manually changed the active slot to b again to properly start the phone again, if slot b was already flashed).

    Best Regard's

    Alex1911
    As fair as I know, you can get at most one slot to be bootable at a time. I don't know exactly why however.
    1
    +1

    Hi Alex1911 - can you pls clarify a few things:

    1) Firstly you went to fastbootd mode (bootloader) and not the regular fastboot mode (download) Right?

    2) Your active slot was a (checked through fastboot getvar current-slot) right?

    3) You flashed in slot b (which was inactive) and then rebooted and it worked?

    4) Or you had to make slob b active (using fastboot set_active b) ?

    Confused as you wrote that "manually changed the active slot to b again"

    Many thanks
    Hello ^^

    1. I rebooted to fastbootd, via the command "adb reboot fastboot" (when your phone is booted in Nothing OS connect via USB to your Pc with ADB (Enable USB-Debugging)

    2. i did not check the slot, it would not let me check it in normal fastboot (commands locked?). use "flash-slot-b.bat" only
    a-slot is somehow not flashable even if its there.

    3. i can't clarify if it was "the inactive slot" but it worked.

    4. sorry i can't remember. I think you can change slots via fastbootd which should happen after flash.

    I hope i could clarify it for you, if not, i'm wiling to help you out.
    I try to remind how exactly i did the procedure.

    Best Regard's

    Alex1911
    1
    Thanks @Alex1911 for your reply.

    Is your phone bootloader unlocked?

    In my case, my phone has bootloader unlocked, I can flash to slot a without issues hence was wondering how you did the same to slot b?

    I also read that never flash to inactive slot (b in my case) without making it active else it will lead to bootloop and hence want to be sure.

    Hence asking again...

    Also what you mean, when you said "manually changed the active slot to b again"

    Thanks again for your time..

    My phones bootloader is unlocked but critical partitions is still locked -> no need to unlock

    command to change slots: fastboot set_active a or fastboot set_active b
    EDIT: Switching slots via fastbootd did not work for my

    So if you get a bootloop try to switch slot via normal fastboot, this is what i did after flashing a slot where i got a bootloop from, so you maybe can do the opposite.

    For short: if you use a fastboot rom flashed via fastboot or fastbootd it always should boot up, if not there could be a bigger Problem or you then need another solution for example: EDL.

    Best Regard's

    Alex1911
    1
    Finally was able to update to 1.5.2 via fastboot method

    In my case, previously has 1.5.1 beta hotfix and all updater methods were failing with Error 20

    I booted to fastboot and checked for active slot using fastboot getvar current-slot and found that slot a is active.

    So I went and flashed the fastboot package to slot b (inactive one) and then rebooted. The rom flashed well and it successfully booted.

    Rebooted back to fastboota and when I typed fastboot getvar current-slot found that slot b was active now.

    So the learning is that - for updates, ideally we need to flash to inactive slot and then it should be activated automatically.
  • 11
    Update! : 2023/03/23 4:46 (UTC+9:00)
    Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.5.3(HotFix) is available.
    Sorry for my poor English, I'm Japanese...

    News: The DSU has been restored in this version. It seems to be usable as long as it is non-root.🎉

    The content of this site has been changed because Global and EEA have merged. (Global)" section is for Global only.
    I think v1.5.1 or later can be used for all types.

    I selfishly want the EEA version.(White..!)
    I'd like to do some verification and such.


    Attention!
    This fastboot ROM requires 'fastboot flashing unlock' and 'fastboot flashing unlock_critical'(Option)!

    2023/02/13 0:44 (UTC+9:00)
    Add QFIL ROM (⚠EDL Command or EDL Cable V1/V2 Required)

    I haven't tried it myself; there is Firehose, so you can use it however you like.
    4
    A friendly reminder to all regarding XDA Rule #4:

    4. Use the English language.

    We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.

    Thank you for your cooperation.

    -Badger50
    3
    release v1.5.2 fastboot ROM & boot.img
    2
    Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.7 is available. Sorry for my poor English, I'm Japanese...

    Thx! AVB Delenda Est

    You should detail the version, only global, no EEA.
    Thanks for your work ;)
    2
    You were integrating.
    Well, I'll change it so that we can use it in common later.