General [ROM][Restore][Unbrick] Nothing OS v1.5.3(HotFix) Global/EEA Fastboot ROM(Full ROM) & boot.img & QFIL ROM (EDL)
- Thread starter ot_inc
- Start date
I recommend the package from here:
Release v1.0.6 · K3V1991/ADB-and-FastbootPlusPlus
Updated ADB Files Changelog: adb: * Don't retry adb root if first attempt failed. * Fix track-devices duplicate entry. * Add receive windowing (increase throughput on high-latency connections). * M...
github.com
@ot_inc
I have a wish for your lovely fastboot images.
Is it possible if you can make your system images with writable rights?
So, currently, there are read-only and mounting as rw fails.
That prevents me to use vanced youtube and things like that.
No i didn't, i thought flash slot a and b would do that first hand. So i should take boot and vendor_boot from 1.51 beta 2 and flash it in bootloader before flashing slot a and b?
flash boot, vendor, run slot a, run slot b, set active slot a, set active slot b... nothing. If i flash boot and vendor and try to boot to fastboot (failed to boot into userspace fastboot). This "unbrick" "restore" isn´t working. The one thing i dont understand is that flashing Paranoid rom is easy and it boots easilly. What is wrong with my phone.
Hello, I am on 1.5.0 EEA, root, bootloader unlocked, not critical.
Can someone confirm if i can update to 1.5.1 Global and after that 1.5.1 Beta 2 Hotfix Global, and use boot.img global for root?
Thanks in advance
Can someone confirm if i can update to 1.5.1 Global and after that 1.5.1 Beta 2 Hotfix Global, and use boot.img global for root?
Thanks in advance
Animesh Singh
Senior Member
Hi, i used this and now i cannot go to recovery . stuck on Bootloader. even if i choose to go to recovery, i instantly get booted back to bootloader. what should i do?
I successfully flash my phone to 1.5.1, thanks!
So when I can't do OTA and local update on 1.1.6(also from fastboot ROM 1.1.6), I use this to get to 1.5.1(beta). And now I still can't locally update 1.5.1 beta(hotfix) which results in showing error 20.
My process is:
1. fastboot flash boot boot.img
2. flash slot a & b
3. download incremental pkg from 1.5.1 , use *#*#682#*#*, finally error 20.
So I was wondering which step might be related to this result. after all it's quite scary to do these whole process for each updates.
So when I can't do OTA and local update on 1.1.6(also from fastboot ROM 1.1.6), I use this to get to 1.5.1(beta). And now I still can't locally update 1.5.1 beta(hotfix) which results in showing error 20.
My process is:
1. fastboot flash boot boot.img
2. flash slot a & b
3. download incremental pkg from 1.5.1 , use *#*#682#*#*, finally error 20.
So I was wondering which step might be related to this result. after all it's quite scary to do these whole process for each updates.
same issue i facing with global version 1.1.7 cant update to 1.1.8 or 1.5 beta error 20 tried all process like adb sideload, local and ota
HI Guys, I may need your help on this one. I installed android beta for phone 1 latest version, via ADB...(i'mm Mac user).
everything working fine now. (phone 1 is rooted)
I'd like to install magisk on phone. however I need to get the boot.img. how do I do that. (first time) where do I downloaded? can I downloaded directly from the phone? is there any guide?
everything working fine now. (phone 1 is rooted)
I'd like to install magisk on phone. however I need to get the boot.img. how do I do that. (first time) where do I downloaded? can I downloaded directly from the phone? is there any guide?
Hi, first, it's better to always build Magisk Patched Boot yourself for a full compatibility and future updates.
So :
1/ Take the Stock Boot img depending your actual version (i think 1.5.1 Beta + Hotfix)
2/ Copy / Past Stock boot on your device storage where you want
3/ In Magisk do : Install > "Select and Patch a File" > Select your Stock Boot > Apply
4/ Magisk have create the Magisk Patched Boot for your device in "Downloads" folder with a name like
Code:
magisk_patched-25xxx_xxXxX.img6/ Enter your device in Fastboot mode / Bootloader
7/ Boot just once (instead directly flash, more safe) with your Magisk Patched Boot, this boot have Root right,
use with this command (replace by your Magisk Patched Boot name) :
Code:
fastboot boot magisk_patched-25xxx_xxXxX.img9/ Device boot normally, just back in Magisk for apply root definitively at your original boot (because actually you have only "boot" with the Patched Boot).
Code:
Magisk > Install > Direct Install (Recommanded) > Apply & RebootAnd voila ! I advise after that install Safetynet Module kdrag0n 2.4.0 if you want use Wallet and have a certified device from Google.
Hi thanks.
prioblem is I open magisk app on the phone. select the image. (currently I'm latest beta 2). however last complete file is beta 1 hot fix as you said.
i select it...but the unpacking fails... I'm stuck on step one of your instruction.
prioblem is I open magisk app on the phone. select the image. (currently I'm latest beta 2). however last complete file is beta 1 hot fix as you said.
i select it...but the unpacking fails... I'm stuck on step one of your instruction.
i was taking the file from here https://www.xda-developers.com/nothing-phone-1-nothing-os-update-tracker/ maybe wrong one.
Magic return error invalid file format when truing to unpack ...
Magic return error invalid file format when truing to unpack ...
Last edited:
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
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
Alex19111
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
Alex19111Finally 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.1
My issue got resolved after updating in 1.5.3. yesterday I updated it and after 24 hrs it's working fine without any Restart.1 -
11Update! : 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.42
