Database Users

{One thread} Guide Rooting Redmi note 4 SD twrp/SU (video tutorial)

This vide will guide you how to root REDMI NOTE 4(SNAPDRAGON)
***IMPORTANT***
BACKUPDATA
Make sure you have adb installed and you place the twrp file to adb folder & other files to internal memory
Downloads:
1. TWRP- 3.0.3-0
https://www.androidfilehost.com/?fid=457095661767136323
2. phh's SuperSu
https://superuser.phh.me/superuser.zip
3. no-verity-opt-encrypt
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Steps:
1.unlock bootloader
http://en.miui.com/unlock/
or
Google mi unlock
2.download files
3.enable usb debugging
4.boot to fastboot (volume down+power button)
5.connect to pc run cmd in adb folder .
6.use command (fastboot devices) to check fastboot devices
7.use command (fastboot flash recovery {name of recovery}.img)
8.boot device to recovery (Flash Verity file, su ) ***IMPORTANT***
9.wipe caches
10.reboot
This is not my work all credit to:
XDA:
https://forum.xda-developers.com/re...ecovery-twrp-3-0-3-0-redmi-note-4-sd-t3549970
Video:
https://youtu.be/dV4urAIRKZU

Not working in 8.1.15.0

Unfortunately not working in miui 8.1.15.0.. Eagerly waiting for your response

ashokmor007 said:
This vide will guide you how to root REDMI NOTE 4(SNAPDRAGON)
***IMPORTANT***
BACKUPDATA
Make sure you have adb installed and you place the twrp file to adb folder & other files to internal memory
Downloads:
1. TWRP- 3.0.3-0
https://www.androidfilehost.com/?fid=457095661767136323
2. phh's SuperSu
https://superuser.phh.me/superuser.zip
3. no-verity-opt-encrypt
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip
Steps:
1.unlock bootloader
http://en.miui.com/unlock/
or
Google mi unlock
2.download files
3.enable usb debugging
4.boot to fastboot (volume down+power button)
5.connect to pc run cmd in adb folder .
6.use command (fastboot devices) to check fastboot devices
7.use command (fastboot flash recovery {name of recovery}.img)
8.boot device to recovery (Flash Verity file, su ) ***IMPORTANT***
9.wipe caches
10.reboot
This is not my work all credit to:
XDA:
https://forum.xda-developers.com/re...ecovery-twrp-3-0-3-0-redmi-note-4-sd-t3549970
Video:
https://youtu.be/dV4urAIRKZU
Click to expand...
Click to collapse
twrp titale say its for mtk

amnv said:
Unfortunately not working in miui 8.1.15.0.. Eagerly waiting for your response
Click to expand...
Click to collapse
Wil update you by tmro on the latest version

vikasb32 said:
Not working in 8.1.15.0
Click to expand...
Click to collapse
I did root my device flash custom recovery (TWRP) while running MIUI 8.1.15.0
whats the issue u had? bootloop?

TechRapt said:
I did root my device flash custom recovery (TWRP) while running MIUI 8.1.15.0
whats the issue u had? bootloop?
Click to expand...
Click to collapse
Most of member says this twrp does not work in miui 8.1.15.0, They say after flashing it mi logo flashes for some time and they could not boot into twrp mode
Honestly i haven't flashed it into my device coz most of people facing bugs only in miui 8.1.15.0..
Im miui 8.1.15.0 stable user hope u can help me.
Thank you
Sent from my Redmi Note 4 using Tapatalk

amnv said:
Most of member says this twrp does not work in miui 8.1.15.0, They say after flashing it mi logo flashes for some time and they could not boot into twrp mode
Honestly i haven't flashed it into my device coz most of people facing bugs only in miui 8.1.15.0..
Im miui 8.1.15.0 stable user hope u can help me.
Thank you
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I am not sure if this is the same TWRP i used
I used the TWRP version from LA 14.1 thread.
I did face few issues though like long boot time but never had issues with loading TWRP or when the OS booted up completely
I am on 7.3.9 build now let me roll back to stable 8.1.15.0 build tonight and re-try the same flash recovery and root method will let u know the results

Not able to boot to recovery
All the installation went as expected till recovery installation. It is done but using Volume Up & Power button not able to go to recovery. Just MI logo post that nothing.

Everything OK but sim slot 2 does not work after root

chandrash3khar said:
All the installation went as expected till recovery installation. It is done but using Volume Up & Power button not able to go to recovery. Just MI logo post that nothing.
Click to expand...
Click to collapse
Rename your recovery as "recover.img".
After flashing recovery don't disconnect the phone
In fastboot type
"fastboot boot recovery.img"
Your phone will boot into recovery

I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
:fingers-crossed:
hadiyalkishan said:
twrp titale say its for mtk
Click to expand...
Click to collapse
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help

rajendraDMD said:
:fingers-crossed:
I have redmi note 4 4g 64gb rom 2017 is not unblock.. plz help
Click to expand...
Click to collapse
What do you mean?

Not working on my redmi note 4 sd (stable 8.2.10.0). When i try to flash the img file terminal shows lots of help tips. I installed all drivers carefully, still its happening. Please help..

TWRP and Magisk for EMUI 9.0

Sorry if this has been answered already, but I can't find anything about it. As far as I can see, the only way to have working Magisk now on EMUI 9.0 is to install it to recovery_ramdisk and use that to boot the phone. That is working fine. Is there any way to install TWRP as well, since it can't go in the recovery_ramdisk partition? I tried
Code:
fastboot flash erecovery_ramdisk
to flash it to eRecovery, but that didn't work and gave me this error:
Code:
FAILED (remote: Command not allowed)
Any ideas?
The specific reason I wanted to get into TWRP was to install the HyperPlus custom kernel, and I can't think of another way to do it.

you have unlocked bootloader ?

Where you found TWRP for EMUI9?

I was trying to use the Oreo 3.2.1 TWRP. I'm now realising that might not work...

where magisk img u flash for your phone

Could you let me know your process to flash magisk to EMUI 9? What version stock rom do you have?
Thanks!

stridechicken said:
Sorry if this has been answered already, but I can't find anything about it. As far as I can see, the only way to have working Magisk now on EMUI 9.0 is to install it to recovery_ramdisk and use that to boot the phone. That is working fine. Is there any way to install TWRP as well, since it can't go in the recovery_ramdisk partition? I tried
Code:
fastboot flash erecovery_ramdisk
to flash it to eRecovery, but that didn't work and gave me this error:
Code:
FAILED (remote: Command not allowed)
Any ideas?
The specific reason I wanted to get into TWRP was to install the HyperPlus custom kernel, and I can't think of another way to do it.
Click to expand...
Click to collapse
You have to install TWRP to recovery_ramdisk, then install the TWRP .img to erecovery_ramdisk from inside TWRP. Then you can install the patched magisk .img to recovery_ramdisk via fastboot.

Tristl said:
You have to install TWRP to recovery_ramdisk, then install the TWRP .img to erecovery_ramdisk from inside TWRP. Then you can install the patched magisk .img to recovery_ramdisk via fastboot.
Click to expand...
Click to collapse
where can i get twrp for emui 9.0 or 9.1 ?

daniel11609 said:
where can i get twrp for emui 9.0 or 9.1 ?
Click to expand...
Click to collapse
Sadly, there isn´t any "official" TWRP recovery for Android 9.0 Pie / EMUI 9.0 on P10 Plus available. However I have been using this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3914798 (TWRP for Mate 9, works for P10 Plus because of similar chipset) successfully for emergency tasks like removing failing Magisk modules and getting out of bootloop, accessing the filesystem or writing *.img files. Be careful though, I don´t think it will work for installing zips or system updates.

Tristl said:
Sadly, there isn´t any "official" TWRP recovery for Android 9.0 Pie / EMUI 9.0 on P10 Plus available. However I have been using this one: https://forum.xda-developers.com/mate-9/development/recovery-twrp-3-2-1-0-t3914798 (TWRP for Mate 9, works for P10 Plus because of similar chipset) successfully for emergency tasks like removing failing Magisk modules and getting out of bootloop, accessing the filesystem or writing *.img files. Be careful though, I don´t think it will work for installing zips or system updates.
Click to expand...
Click to collapse
thanks a lot, i really need it rn as well, because i have usb debugging disabled and ran into a bootloop.
---------- Post added at 11:01 PM ---------- Previous post was at 10:56 PM ----------
daniel11609 said:
thanks a lot, i really need it rn as well, because i have usb debugging disabled and ran into a bootloop.
Click to expand...
Click to collapse
im pretty lost right now, i had "oem unlock" disabled, so fastboot shows FRP lock, i cant flash anything. how to get around that when i cant enter my system?
edit: fixed it just booted without root and enabled adb to fix magisk

Tristl said:
You have to install TWRP to recovery_ramdisk, then install the TWRP .img to erecovery_ramdisk from inside TWRP. Then you can install the patched magisk .img to recovery_ramdisk via fastboot.
Click to expand...
Click to collapse
so it would replace the eRecorery? Isnt that quite risky because the erecovery might safe you when i get softbricks / bootloops etc

Sadly, Bricked Almost New Redmi K20...Can Anyone Please Help me Fixing this !!!

Dear Friends,
I have just imported redmi k20 from China. But accidently deleted my EFS Partition. I had not backed it up. I have access to fastboot and TWRP.
Please help me fixing this problem for the sake of my hard earned money.???
I'll be always obliged.
Regards,

mujahidyousaf said:
Dear Friends,
I have just imported redmi k20 from China. But accidently deleted my EFS Partition. I had not backed it up. I have access to fastboot and TWRP.
Please help me fixing this problem for the sake of my hard earned money.???
I'll be always obliged.
Regards,
Click to expand...
Click to collapse
Download your phone firmware and miflash tool, flash via fastboot with this software but DONT re lock the bootloader

i did it 2 times, each time i downloaded the rom from the xiaomi site and transferred it to my phone and flashed with twrp

Pupet_Master said:
Download your phone firmware and miflash tool, flash via fastboot with this software but DONT re lock the bootloader
Click to expand...
Click to collapse
Did that many times brother but it is still stuck in bootloop. The problem is that i have damaged EFS Partition. Ihave tried installing ROM through TWRP and also through fastboot with miflash. When i enter in Mi recovery i get message of " NV data corrupted".

mujahidyousaf said:
Did that many times brother but it is still stuck in bootloop. The problem is that i have damaged EFS Partition. Ihave tried installing ROM through TWRP and also through fastboot with miflash. When i enter in Mi recovery i get message of " NV data corrupted".
Click to expand...
Click to collapse
You need to fix the partitions i think (idk how, but try on TWRP, there is a option to fix partitions) or in last case with fastboot i think its possible

Pupet_Master said:
You need to fix the partitions i think (idk how, but try on TWRP, there is a option to fix partitions) or in last case with fastboot i think its possible
Click to expand...
Click to collapse
I am not sure how to do that. But i have searched a lot on internet but can't find any solution.

this could help
Download stock rom and upack to the C:
copy this files from adb to the rom https://cs5-2.4pda.to/16762384/05.png?bc48fd2c50cba18a8da8778c9cdc19a9
run flash_all.bat
DONT USE FLASH_ALL_LOCK.BAT IF YOU FLASHNING GLOBAL ROM ON K20, THATS BRICKED YOUR PHONE...

If non of the above works than you can try this: https://romprovider.com/2020/03/xiaomi-mi-9t-imei-repair/
I know that i used something very similar when rebuilding EFS on my old Mi A1 and it did work. Though i didnt try it on Mi 9T because i didnt need it yet.

xpxrx said:
this could help
Download stock rom and upack to the C:
copy this files from adb to the rom https://cs5-2.4pda.to/16762384/05.png?bc48fd2c50cba18a8da8778c9cdc19a9
run flash_all.bat
DONT USE FLASH_ALL_LOCK.BAT IF YOU FLASHNING GLOBAL ROM ON K20, THATS BRICKED YOUR PHONE...
Click to expand...
Click to collapse
Ok brother. Let me give it a try.

Hey Bro, don't worry at all! It's because of EFS Corruption and you have to clear the partition and then flash ROM again with fastboot!
Boot into TWRP recovery.
From TWRP’s main screen, select Advanced » then Terminal.
Type the following commands in terminal (one by one):
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
Reboot device.
go to TWRP, Flash ROM

(closed)Fastboot bootloop

Hi gyes, I have redmi k20, when I flash magisk patched recovery image then device stuck at fastboot, so I flash original recovery image for device , then it start in normal mode, so device can't rooted, so pls any one guide me to root device with magisk.
Thanks...

wakram001 said:
Hi gyes, I have redmi k20, when I flash magisk patched recovery image then device stuck at fastboot, so I flash original recovery image for device , then it start in normal mode, so device can't rooted, so pls any one guide me to root device with magisk.
Thanks...
Click to expand...
Click to collapse
You have to patch boot.img and flash the patched img to Boot
Btw, there were two guides in the Guides section about the same (stating exactly the same: extract boot ing, patch and flash).
Guides (in the Redmi K20/Mi 9T section) are old and maybe from the times of A9 MIUI 10 - but the same method still works for A11 / MIUI 12.x
Hence, you can have in parallel both Magisk (in Boot partition) and TWRP (in Recovery partition)
boot.img must be extracted from exactly the same firmware package (recovery/zip or fastboot/tgz) that you have installed to your phone.
Or you can patch boot.emmc.win TWRP backup file of your Boot partition (instead of exteacted boot.img file)
You can flash from Fastboot of from TWRP
If using TWRP, use the latest official twrp-3.5.2_9-0-davinci

My device has no ramdisk.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...

zgfg said:
You have to patch boot.img and flash the patched img to Boot
Btw, there were two guides in the Guides section about the same (stating exactly the same: extract boot ing, patch and flash).
Guides (in the Redmi K20/Mi 9T section) are old and maybe from the times of A9 MIUI 10 - but the same method still works for A11 / MIUI 12.x
Hence, you can have in parallel both Magisk (in Boot partition) and TWRP (in Recovery partition)
boot.img must be extracted from exactly the same firmware package (recovery/zip or fastboot/tgz) that you have installed to your phone.
Or you can patch boot.emmc.win TWRP backup file of your Boot partition (instead of exteacted boot.img file)
You can flash from Fastboot of from TWRP
If using TWRP, use the latest official twrp-3.5.2_9-0-davinci
Click to expand...
Click to collapse
My device has no ramdisk, A 10 miui 12.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...

wakram001 said:
My device has no ramdisk, A 10 miui 12.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...
Click to expand...
Click to collapse
Don't pay attention to what Magisk says (No Ramdisk).
Brw, there is some (albeit small prints) note about 'No Ramdisk' devices in the Magisk guide on the official Magisk Github - saying that on some (not sure does it mention Xoaomi) boot.img must be patched
I use this method since A9/MIUI 10 till now on A11/MIUI 12.6 and never had problems - see also my screenshot (Magisk installed, saying No Ramdisk but I installed Magisk by patching boot img)
Also, if it won't work, just flash the original boot.img

wakram001 said:
My device has no ramdisk, A 10 miui 12.
I have already tried with boot image but magisk patched boot image not flash, it show error.
Thanks for reply...
Click to expand...
Click to collapse
What error?
Command for Fastboot flashing must be:
fastboot flash boot <patched-boot-img>
Try again and post the error screenshot
When patching, you must not tick Recovery option (since you are not patching Recovery)
You can read also discussion about patching boot img
(where the same has been asked and answered many times) for Xiaomi phones in the General Magisk Support thread on XDA
Edit:
You can also only temporarily (one time) boot to the patched boot img by:
fastboot boot <patched boot img>
(Observe that flash command is omitted)
Then if ok, flash it permanently
Btw, always make sure that Fastboot is properly connected:
fastboot devices

Btw, another similar thread - Mi 9T Pro (doesn't matter), MIUI 12, disbelief about patching boot.img (and possible bootloop with the solution, in case of previously installed Magisk modules):
Does patched boot.img Magisk work on MIUI V12.5.1.0? (Edit: Yes it does!)
Just curious if anyone has any insight as to whether I can use the Magisk app to patch the newest boot.img (12.5.1.0 global / Android 11 / mi9t pro) and whether it will go smoothly if I install it via fastboot flash boot patchedmagiskhere.img? I...
forum.xda-developers.com

Magisk patched boot image is working properly. Now I have rooted device.
Thanks.

How To Guide How to Revert back to Nothing OS from custom rom for nothing phone 1

So I was searching for revert back the phone from custom roms to stock nothing OS and i got this simple method to revert back.
Prerequisites:
1) Your phone's bootloader must be unlocked
2)USB debugging must me enabled
3) You have PC with all latest fastboot drivers installed
4) Your phone's fastboot mode must be working.
Note: while data will get wiped so keep full backup before proceeding!
Download:
1) Nothing OS 1.1.3 full package (global)
https://android.googleapis.com/packages/ota-api/package/ee4a8d890091f980aa40142d68f46abb1f08e0c5.zip
Nothing os 1.1.3 full EU region firmware ( you need to extract boot image and vendor_boot image using playload dumper)
Europe_Full_Nothing_OS_1.1.3_update.zip | by Sib64 for Generic Device/Other
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
2)boot image( for nothing os global 1.1.3 only)
boot.img
drive.google.com
3) vendor_boot.img( for nothing os global 1.1.3 only)
vendor_boot.img
drive.google.com
Note: if u have any other Full firmware than nothing os 1.1.3 then u also needs boot and vendor _boot for same firmware.
Don't use vendor and boot given here, you specific on as I said or extract it from full firmwares zip using playload dumper:
- Download Payload Dumper
From here : https://androidfilehost.com/?fid=818070582850510260
-- Extract the older version's payload.bin file and execute the payload dumper and obtain boot.img and vendor_boot.img
Proper guide given by @Sib64
https://forum.xda-developers.com/t/...one-1-update-04-08-2022.4470155/post-87185467
Steps:
1)power off the phone long press vol down+ power button to boot phone in to fastboot mode and connect it to pc
If u r phone is already bootlooped then follow the same step
2) download and place above files in one folder on PC inside platforms tools folder inside C driver or on dextop
3) press shift on keyboard+ right click of mouse and select open command prompt or power shell window here from drop down menu
4) Now first type command
fatsboot flash boot boot.img( or drag file inside cmd window to locate it's location without typing boot.img)
Hit enter
5) Now type
fastboot flash vendor _boot vendor _boot.img
Hit enter
6) now type
fatsboot reboot recovery
7) phone will boot to new stock recovery but if it stucks on Android logo then just press power button and simply single time press volume up.
Now you will see new recovery screen.
In that using volume up+down key's select apply update from adb.
8) keep phone connected to pc and in cmd window again type
adb sideload and drag full firmware file location
Hit enter falshing with progress bar will starts in cmd.
It will may end at 94% don't worry, remove cable and now in recovery select factory reset and press power button to confirm.
Now select reboot to system.
That it's phone boots to stock nothing OS.
After booting please check alll basic things like wifi, Bluetooth, glyph etc are working or not.
After donwgrade you may directly get Nothing OS 1.1.6 (148mb) size update
If you want video tutorial it is here

This only works if you are on 1.1.3 before using a custom Rom? At least i needed the super.img to Go Back to nos from ricedroid.

xtcislove said:
This only works if you are on 1.1.3 before using a custom Rom? At least i needed the super.img to Go Back to nos from ricedroid.
Click to expand...
Click to collapse
No i was on 1.1.5 , then I used paranoid then ricedroid .
Then i directly flashed this and boooooom i am on 1.1.3
No need of super all are inside full firmware zip

pankspoo said:
No i was on 1.1.5 , then I used paranoid then ricedroid .
Then i directly flashed this and boooooom i am on 1.1.3
No need of super all are inside full firmware zip
Click to expand...
Click to collapse
Are you sure you did not change from eea to global or the other way around?
The other people including me needed the super.img to rollback to 1.1.3 no matter if coming from a custom rom or anything above 1.1.3.
At least i can tell you that i exactly used your described method and it did not work, i couldnt sideload the full package. I needed to flash the super.img first. Thats why we have the super.img files, to rollback/unbrick and revert from custom rom.

xtcislove said:
Are you sure you did not change from eea to global or the other way around?
The other people including me needed the super.img to rollback to 1.1.3 no matter if coming from a custom rom or anything above 1.1.3.
At least i can tell you that i exactly used your described method and it did not work, i couldnt sideload the full package. I needed to flash the super.img first. Thats why we have the super.img files, to rollback/unbrick and revert from custom rom
Click to expand...
Click to collapse
xtcislove said:
Are you sure you did not change from eea to global or the other way around?
The other people including me needed the super.img to rollback to 1.1.3 no matter if coming from a custom rom or anything above 1.1.3.
At least i can tell you that i exactly used your described method and it did not work, i couldnt sideload the full package. I needed to flash the super.img first. Thats why we have the super.img files, to rollback/unbrick and revert from custom rom.
Click to expand...
Click to collapse
I am using global device. The firmware, boot and vendor boot given in video description is same as nothing os 1.1.3.
If u r using EEA nothing os firmware then use boot image and vendor same eea, i think you used boot and vendor boot given in this thread actually it's only for global.
No need to flash super nothing it's working as i told

Where is Super image? Cant do anything without it!

Patman86 said:
Where is Super image? Cant do anything without it!
Click to expand...
Click to collapse
Tell me on which firmware you are?
Bootlooped or want to just revert back

pankspoo said:
I am using global device. The firmware, boot and vendor boot given in video description is same as nothing os 1.1.3.
If u r using EEA nothing os firmware then use boot image and vendor same eea, i think you used boot and vendor boot given in this thread actually it's only for global.
No need to flash super nothing it's working as i told
Click to expand...
Click to collapse
I was trying the procedure before you postet your guide.
I downloaded the 1.1.3 EEA Full zip and extracted the payload. I flashed the boot and vendor boot that i extracted and i still could not sideload the package.
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...
forum.xda-developers.com
This tutorial got me back to 1.1.3 EEA - I used the same files i extracted before the only difference was the super.img from the given thread.
In short: I was on 1.1.4 EEA, flashed and tested ricedroid, flashed vendor_boot and boot from 1.1.3 EEA and could NOT sideload 1.1.3 EEA. The super.img was the key.

Patman86 said:
Where is Super image? Cant do anything without it!
Click to expand...
Click to collapse
Follow this 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...
forum.xda-developers.com

xtcislove said:
I was trying the procedure before you postet your guide.
I downloaded the 1.1.3 EEA Full zip and extracted the payload. I flashed the boot and vendor boot that i extracted and i still could not sideload the package.
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...
forum.xda-developers.com
This tutorial got me back to 1.1.3 EEA - I used the same files i extracted before the only difference was the super.img from the given thread.
In short: I was on 1.1.4 EEA, flashed and tested ricedroid, flashed vendor_boot and boot from 1.1.3 EEA and could NOT sideload 1.1.3 EEA. The super.img was the key.
Click to expand...
Click to collapse
Do you tried using my files?
Because it's for global, i don't have eea boot and vendor try with them

xtcislove said:
I was trying the procedure before you postet your guide.
I downloaded the 1.1.3 EEA Full zip and extracted the payload. I flashed the boot and vendor boot that i extracted and i still could not sideload the package.
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...
forum.xda-developers.com
This tutorial got me back to 1.1.3 EEA - I used the same files i extracted before the only difference was the super.img from the given thread.
In short: I was on 1.1.4 EEA, flashed and tested ricedroid, flashed vendor_boot and boot from 1.1.3 EEA and could NOT sideload 1.1.3 EEA. The super.img was the key.
Click to expand...
Click to collapse
U can't able to sideload the package what error u got

pankspoo said:
U can't able to sideload the package what error u got
Click to expand...
Click to collapse
As i said i tried the procedure u describe here 6 days ago.
You can read here, i had to use the super.img from unbrick tutorial.
[𝟏𝟑] RiceDroid Android project Beta 3 - Nothing phone (1)
/* * Your warranty is now void. (Still valid ? LMAO) * I am not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns about...
forum.xda-developers.com
I used the full package from 1.1.3 EEA and extracted vendor_boot and boot from 1.1.3 EEA.
I got the error that you get if you try to downgrade from adb sideload within recovery.

v1.1.6 Global Full ROM&boot.img
[Restore NothingOS & Magisk] Nothing Phone(1) Fastboot ROM(Full ROM) & boot.img Global v1.1.6
Fastboot ROM and boot.img for NothingPhone(1) are now available. v1.1.6 is available. Sorry for my poor English, I'm Japanese. https://reindex-ot.github.io/
forum.xda-developers.com

pankspoo said:
Tell me on which firmware you are?
Bootlooped or want to just revert back
Click to expand...
Click to collapse
It was a reply to your first post in this thread, YOU ARE MISSING super image, if you dont flash super image you cant fastboot 1.1.3 to your device, i have already done this.
I even wrote about it in the first custom rom thread on xda for our phone.
You have not done a return to stock from custom OS before or you forgot about super image.

I
Patman86 said:
It was a reply to your first post in this thread, YOU ARE MISSING super image, if you dont flash super image you cant fastboot 1.1.3 to your device, i have already done this.
I even wrote about it in the first custom rom thread on xda for our phone.
You have not done a return to stock from custom OS before or you forgot about super image.
Click to expand...
Click to collapse
Don't know about your issue but mine phone is global , its on nothing os 1.1.5 but later i flashed paranoid Android.
Later used ricedroid and without using super i just reverted to nothing os
In global nothing os telegram community most of user followed same process

Will i receive updates after flashing this version? Talking about Global