Develop Bugs

[Root]Wileyfox Swift

Hi all,
found out how to root this device!
Here the steps:
Make sure you have fastboot installed on your computer: https://wiki.cyanogenmod.org/w/Fastboot
download supersu zip from here
https://download.chainfire.eu/696/supersu/
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
download latest recovery image from here
http://download.cyanogenmod.org/?device=crackling
to boot the custom recovery, on your computer type
Code:
fastboot boot <name_of_recovery>.img
OR
install recovery
Code:
fastboot flash recovery <name_of_recovery>.img
and reboot into recovery manually (remove and reinstall battery, hold volume down and power buttons.
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access

Thanks
I went a step forward and installed the CM nightly.

mermigas said:
Thanks
I went a step forward and installed the CM nightly.
Click to expand...
Click to collapse
Does the camera work? I tried one of the first nightlies but the camera crashed, so this was no option for me.

olli_o said:
Does the camera work? I tried one of the first nightlies but the camera crashed, so this was no option for me.
Click to expand...
Click to collapse
No problem with camera for me.
All works fine and smooth
No bugs nored

olli_o said:
4) reboot directly into recovery. Normal system boot reinstalls stock recovery.
5) install supersu update zip from recovery menu
Click to expand...
Click to collapse
When in recovery I press apply update and sd card, before i've even selected supersu, which returns:
Install failed
Installation aborted
Installation aborted
any ideas?

monethys said:
When in recovery I press apply update and sd card, before i've even selected supersu, which returns:
Install failed
Installation aborted
Installation aborted
any ideas?
Click to expand...
Click to collapse
This is stange. I modified the instructions a little, does it also happen if you follow these steps?

OTA?
Will I be able to update my phone (ota?) after the root?
I'm fine with having to reroot

rebane2001 said:
Will I be able to update my phone (ota?) after the root?
I'm fine with having to reroot
Click to expand...
Click to collapse
Incremental auto-update won't work rooted. But you can manually update. See here

Followed instructions and now have a rooted wileyfox swift thank you

olli_o said:
Hi all,
found out how to root this device!
Here the steps:
download supersu zip from here
save it to your external sdcard
enable developer options (settings - about - click mutliple times on the build number).
enable OEM unlock in the developer options settings on the device.
reboot Wileyfox Swift into fastboot mode: with the device powered down, hold the Volume Up and connect USB
to unlock the boot loader, WARNING!!! This wipes your user data!!!
on your computer type
Code:
fastboot oem unlock
fastboot -i 0x2970 oem unlock-go
fastboot oem unlock-go
download latest recovery image from here
to boot the custom recovery, on your computer type
Code:
fastboot boot <name_of_recovery>.img
install supersu update zip from recovery menu (choose zip from extenal SD)
reboot and enjoy root access
Click to expand...
Click to collapse
In case anyone has a similar issue:
I could unlock. I could install the recovery. But SuperSU was coming up with signature errors and wouldn't install. I discovered that this was because the recovery was being overwritten (I flashed it to the device because "fastboot boot..." was not working).
I could not get the device to flash the recovery then reboot to recovery without it going into normal boot first and rewriting the recovery so that I would not be able to install SU.
The solution I found for this was to take the back of the phone off.
Flash the recovery: fastboot flash recovery "recovery file name".img
Then just pull the battery.
Hold the volume down when you put the battery back in and launch the device still holding volume down.
Remember to release the power button once you see fox logo or you'll reboot again.
Now I installed SuperSU without a hitch and all is good.
Hope that helps anyone who is stuck.
Links removed from quote so as not to trigger spam bot.

Help
olli_o said:
Hi all,
found out how to root this device!
[*]download latest recovery image from here
/download.cyanogenmod.org/?device=crackling[/
[/LIST]
Click to expand...
Click to collapse
All the list from here is a nightly build. Can you give the stable mod? I'm noob so can follow it. it is very hard for me to make it work I'm still working to install the fast boot for mac. I found this:
bash <(curl -s htps:/raw.githubusercontent.com/corbindavenport/nexus-tools/master/install.sh)
It seems to work when i check this command:
adb devices
BUT NOT SURE if this is safe.
Please provide link for recovery or rom which i can follow using your guide. There are many in the link above but which one is stable and i can use that all the of the system functioning.
Thank you in advance.

I hope this will help someone figure things out w/ what i did... LOL
Thanks ALL. Basically the post above helped to root my phone but its been hard for me and as mentioned in my previous post, I'm noob. So here is what i did after the fastboot issue and continue on even though i didn't know if the install is safe since my OS X was able to detect the device/phone as mentioned above.
1. On fastboot, i just use "fastboot devices" to verify my phone is connected. This command did not work "fastboot -i 0x2970 devices"
2. Then use, "fastboot oem unlock-go" and i waited about 20sec as the terminal returned that message and then it was confirmed unlocked. These commands did not work "fastboot oem unlock, fastboot -i 0x2970 oem unlock-go" my terminal just froze and did nothing.
3. Then i use this to check if it is unlocked "fastboot oem device-info"
4. Using the link on downloading the recovery, i just click all of upper part with the picture and found the .img file see below:
Swift
Wileyfox - crackling
Download Latest Nightly (this is .zip file)
Download Latest Nightly Recovery (this is the .img file which i used)
Device Wiki 2016-01-07
5. update: i did erase recovery "fastboot erase recovery"
i use two commands and both works "fastboot flash recovery cm-12.1-20160107-NIGHTLY-crackling-recovery.img"
(here is the terminal msg: target reported max download size of 268435456 bytes
sending 'recovery' (23110 KB)...
OKAY [ 0.727s]
writing 'recovery'...
OKAY [ 0.387s]
finished. total time: 1.114s)
and this "fastboot boot cm-12.1-20160107-NIGHTLY-crackling-recovery.img"
(here is the terminal msg:downloading 'boot.img'...
OKAY [ 0.727s]
booting...
OKAY [ 0.186s]
finished. total time: 0.913s)
(I LEARNED THE HARD WAY THE .img file must be IN THE SAME DIRECTORY of the fastboot - but PLEASE ASK THE EXPERTS and don't copy if i did something wrong)
6. Next should be the auto reboot that suppose to happen but it didn't. So i took " k_web9000" advice and just pull the battery off (i didn't have any choice its not doing anything... heheh).
6. To boot in Recovery - i followed this :With the device powered down, hold the Volume Down and Power buttons.
7. Next should install the SuperSU.zip file (Please make sure to use chrome since my Safari auto unzip the file and wasted so much of my time troubleshooting... i mean hours retracing my steps ...funny) Just update it and locate the sdcard and look for the .zip file
8. Then it just rebooted after the install and on the boot screen i saw 4 files that where updated.
9. Finally, i checked for the root by downloading root checker and it was verified rooted.
Now you have been noobified
A SYSTEM UPDATE POP-UP 12.1 YOG7DAS2FI Incremental about 48MB BUT DIDNT TOUCH IT, What do i need do? Can i update?
PLEASE LET ME KNOW HOW TO UPDATE TO THE LATEST ONE WITHOUT LOSING MY ROOT.
OR HOW TO INSTALL CYANOGENMOD easy way please . i can see CYANOGEN OS 12.1-YOG4PAS33J on my device
PLEASE HELP. THANKS

You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling

How?
mermigas said:
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
]https://wiki.cyanogenmod.org/w/Install_CM_for_crackling]
Click to expand...
Click to collapse
Thanks for the info and link!! Awesome!
" 4. In ClockworkMod Recovery, use the physical volume buttons to move up and down. On most devices, the power button is used to confirm a menu selection, but for some devices a physical home key acts as a selector. Some devices have touch enabled ClockworkMod Recovery, in which case you may be able to swipe to, or touch, menu selections.
5. Optional (Recommended): Select backup and restore to create a backup."
In the link you gave, how did they get the clockworkmod recovery? I downloaded & installed it in the google store but it say can not use due to the device not listed. All icons are grayed and i also tried TWRP same issue.
The link also pointed to the nightly build, is there a stable release, doesn't need much update, i can use daily and without the hiccups.
Lastly, if there is no clockworkmod, how do you get it backup as recommended in the link you gave and as quoted above.
Many thanks in advance.

There is only official CM recovery and back up is not possible. Use Titaniumfor back up. You can also use twrp recovery posted in general section. Nightlies are more than stable.

Something is not right...
mermigas said:
You cannot update whilst you are rooted.
If you want to have the latest then CM Nightly is your best option.
How to
https://wiki.cyanogenmod.org/w/Install_CM_for_crackling
Click to expand...
Click to collapse
i was afraid of updating coz my data might be deleted but it seems the OTA update didn't delete my data. My version now is 13.0-20160127-NIGHTLY-crackling but the downside is the google play is not present anymore. i will try install the gapp again.
i don't know if i did it right, some say you need TWRP but it works just fine w/o TWRP in updating via OTA. I also try to install TWRP but i can't get it to work, so i can backup my phone. Last option is what you suggested the titanium backup.
Please let me know if i did right and the gapp if this always going to be installed again. i will be using the same gapp file and report what happen. thanks
Report:
i tried to install gapp file but i didn't use the previous gappfile since the it needs for 6.0 android and i used arm64 but gave error:70 which is the space issue via emulated option. So i go to cyangenmod recovery>apply update> from sdcard1 and "install failed - installation aborted". I can't even see the files on my sdcard. How do you now fix this?
Also can i have the right TWRP file and instruction for Wileyfox Swift PLEASE? thanks

Something went wrong! Please help
I can't to get the gapp to installed.
I wipe everything using the cm recovery and i also was able to install TWRP recovery and it does always hangs when installing the gapp -arm64-aroma (i can choose what to install). I also reinstall 12.1 and 13 but failed again when installing any gapp even in nano version (please note that i wipe everything). in my last attempt i wipe: dalvik, system, cache, data, internal storage & android secure but nothing works to install the gapp. Btw, when i wipe from the 1st time i always get this error "e: unable to find partition size for '/recovery"
PLEASE HELP

I had a few problems doing this from Ubuntu 15.10.
1. ADB did not see the device although it worked fine on my Nexus 4 showing that adb/fastboot were configured correctly. I had to go to /home/.android and create the document 'adb_usb.ini' (right click, new document) which contains the text '0x2970'.
Once this was done I had to run the following commands
adb kill-server
adb start-server
This allowed ADB to see the device but it said that it was offline.
2. I had to create the file /etc/udev/rules.d/51-android.rules (type into terminal 'sudo nano /etc/udev/rules.d/51-android.rules') and paste in the following line, save it (ctrl+x, y, enter).
SUBSYSTEM=="usb", ATTR{idVendor}=="2970", ATTR{idProduct}=="2282", MODE="0666"
sudo service udev restart
After this ADB and fastboot recognized the device and allowed me to follow the directions posted above or on the cyanogenmod wiki.
Hope that is of some use to someone!!!

Also the Cyanogen Recovery was both unpleasant to use and caused problems trying to install GApps, I had to switch to using the unofficial TWRP recovery which worked first time and is a much better interface.

Hey do we need to unlock a bootloader before installing the custom recovery on this device? Thanks.

NO RPMB (how to install TWRP, a new ROM and using Magisk)

Hello, I have sent my phone to warranty and after that I received a phone with NO RPMB and after many frustrations I found (with help of many users and forums) how to workaround this..
To start:
Download boot image from here
Download twrp from the official website
Change the name to boot.img and twrp.img and put it in the platform-tools folder
Open the terminal there
Download your favourite rom
Enter fastboot mode on your phone
!!!!After this you will loose all of your data!!!!
Paste this to the terminal
fastboot oem unlock
(select yes on your phone)
fastboot flash boot boot.img
fastboot flash recovery twrp.img
fastboot format userdata
fastboot format cache
Reboot to recovery (if it doesn't enter at the first time enter download mode again and restart to recovery)
After that you have twrp and can flash every rom.. yay!!!
Wipe everything.
Copy the rom zip to your phone using MTP
Install your fancy new rom
If you want to install magisk:
Install the magisk manager.
On the app select install and select patch image file. (it will create a new boot image already patched)
After that install the new image (patched_boot.img) using twrp
Do a clean instalation of your ROM (recomended) or a Factory Reset first
Reboot to twrp
Select install
Click in install image
Select patched_boot.img
Select install to boot partition
Reboot.
Install magisk manager and do the sugested setup.
You now have magisk working
Thanks to all the users that helped me!!

I had real trouble getting twrp to work the last time I tried this a few months ago. Followed the steps here and am now on pixel experience with magisk. Thanks!

Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.

sigibian said:
Hello, im in the same situation of NO RPMB. This procedure will permanently lets have bootloader unlocked?
About Magisk, i can install it in usual way once im in the recovery? (I mean download latest stable version for Bullhead and flash via TWRP).
Thanks.
Click to expand...
Click to collapse
My bootloader is still unlocked after following this guide
For Magisk:
-Install your custom ROM and boot it up (without root)
-Then extract the boot.img from the ROM zip file and save it on your phone storage.
-Install the Magisk manager apk
-In Magisk manager, select install Magisk> choose the patch boot image option and -Select the boot.img you previously saved.
Once it's done, reboot into twrp and flash the patched boot.img. When you reboot Magisk will be working.
I've had no issues with my bootloader, even after an ota update for pixel experience.

Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656

sigibian said:
Thank you, i will try it.
Another question. I never tried dowload mode before, as i read in other post i should Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb that's already connected to pc, right?
When in download mode i can fire up fastboot commands like im in bootloader mode?
So then after do last command fastboot format cache i can reboot to recovery from terminal using adb reboot recovery or i can / should do it from device?
About twrp it's ok to use the latest 3.2.3.0 official version or the 3.2.1 4core version from here as someone suggested from Reddit? https://forum.xda-developers.com/nexus-5x/development/recovery-twrp-3-2-1-4-core-t3796656
Click to expand...
Click to collapse
The official twrp works for fine for me, haven't tried the 4 core version but it can't hurt to try if you need it.
Power off your phone then press and hold volume - and power to enter bootloader, then connect to your pc and follow the steps in the OP

So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache

sigibian said:
So i have to enter in bootloader mode? At point 6 of OP there is written to enter in the download mode, this makes me confusing.
Can anyone explain me latest 2 commands why they are needed?
fastboot format userdata
fastboot format cache
Click to expand...
Click to collapse
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.

baddesthad said:
This thread is fairly comprehensive;
https://forum.xda-developers.com/nexus-5x/general/moto-nexus-5x-sticky-roll-t3207487
Holding volume - and power takes you to fastboot mode (download mode essentially), theres also an option to reboot into recovery (selectable using the volume keys.)
Formatting user data and cache is necessary prior to installing a new rom (especially if moving from stock). You lose all data (back up first!) But a clean flash is the best place to start.
Click to expand...
Click to collapse
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.

sigibian said:
Thanks for the explanation but for installing a new ROM usually you can do factory reset directly in TWRP, plus doing all the wipes, this should be enough.
About fastboot mode and download mode, they are completely different, fastboot mode: vol down + power, download mode for LG: Plug USB cable into pc, Hold volume up and power at the same time and plug phone into usb.
My question is what i can do in download mode? As OP says after entering download mode open terminal and use fastboot commands.
Click to expand...
Click to collapse
You need to use vol- and power to go into fastboot mode then connect to the pc. As for userdata and cache, if you don't clean them when coming from stock you will have issues (your data will be encrypted if you're on stock?). As I said this guide worked for me. The op was talking about fastboot mode in the 6th option (also there is much more information in the thread I linked above)

sorry for the confusing i wanted to say fastboot mode..
i knew the thread that you are saying but most people doesn't want to search so I made a little thread only with the needed parts..
I use it myself so I have a place to remember all the steps when I need to change the rom to a new one or when I make experiments and brick my phone XD

If anyone know anything else that should be in here just say, I really want to improve the post

Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?

fhartane said:
Hi. I just went through the whole process several times (I have tried the different modified boot images from the dedicated post) and my device is still locked [emoji24] any suggestions?
Click to expand...
Click to collapse
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not

PedroM.CostaAndrade said:
your device will always be locked this is a workaround to get twrp, new roms and magisk while it stays locked..
with twrp usable it won't matter if you are locked or not
Click to expand...
Click to collapse
Thanks for the answer. You mean that now I have twrp, I can flash custom Roms with my bootloader locked without any issue?
Envoyé de mon ONEPLUS A3003 en utilisant Tapatalk

Yes if you have TWRP you can install custom ROMs, custom Kernel's, magisk, super su, etc..
the locked bootloader only prevents you from using fastboot commands like the one needed for installing custom recovery
Now that you have TWRP you can use it for everything

Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?

Fabiojoker said:
Hello everyone, I also have a nexus 5x with motherboard that has been replaced under warranty and unfortunately I can't keep the bootloader unlocked.
I tried the procedure you have indicated, but at this point there is the problem, because after inserting the boot.img and twrp.img inside the phone, then when I go to do the unlocking procedure with 'fastboot oem unlock (select yes on your phone) 'in practice the memory is deleted on the phone, so I lose the previously uploaded files, and therefore I can no longer continue with the flash procedure of boot.img and twrp.img because they are no longer present in memory.
I hope I made myself understood, maybe I am wrong, or is there a way to solve this problem?
Click to expand...
Click to collapse
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC

Hello, thank you for your information, since I haven't done modding on phones for a long time, I didn't remember exactly the procedure with fastboot and therefore I didn't understand where I had to put the files, but in the end I did it.
Thank you
PedroM.CostaAndrade said:
fastboot is for the files on your PC not your phone
you need to put the files inside of platform-tools and then open cmd inside it and use the fastboot commands
fastboot will take the files of your PC
Click to expand...
Click to collapse

Why is a custom boot image needed? I don't want to root.

TWRP for Realme 3 [Working][Updated:21-Aug-2019]

All Praise and All Thanks To God
Things Required: Unlocked bootloader, TWRP file, Disable_Dm-Verity_ForceEncrypt.zip file, External SD card, adb and fastboot drivers installed in pc
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/guide-bootloader-unlock-guide-realme-3-t3999463
2. Copy Disable_Dm-Verity_ForceEncrypt.zip in your External SD Card. Power off your phone by pressing power button, after your phone is powered off ,hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your external sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6. Install the Disable_Dm-Verity_ForceEncrypt.zip using twrp
7 .Reboot, Done!
---------------------------------------------------------------------------------------------------------------------------------------------------------------
Please Note:
1. There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
2. Don't relock bootloader after flashing twrp, it might brick your device. (Don't use fastboot flashing lock)
3. You cannot restore preloader_a and preloader_b partitions using twrp, only you can backup the two partitions, so always uncheck these two partitions before performing a twrp restore.
4. Please don't use minimal adb and fastboot tool, use Latest ADB and Fastboot Installer tool , link is provided below.
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Links:
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Disable_Dm-Verity_ForceEncrypt.zip: https://zackptg5.com/android.php#disverfe
Latest ADB and Fastboot Installer: https://forum.xda-developers.com/android/general/tool-adb-fastboot-installer-tool-windows-t3999445
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
A. From adb:
adb reboot recovery
adb shell reboot recovery
B. From fastboot mode:
fastboot oem reboot-recovery
C. There is no way to boot to recovery using power + vol down button after unlocking your bootloader. Only above two methods will work. (Don't relock bootloader after flashing twrp, it might brick your device)
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
@osm0sis for his system_root mount support in AK3 which Disable_Dm-Verity_ForceEncrypt.zip uses

Nice Work

I will test soon
---------- Post added at 02:15 PM ---------- Previous post was at 02:13 PM ----------
KSUBROTO said:
It didn't work
Click to expand...
Click to collapse
dont be stupid nova customizer you dont have rm3 phone all developer from realme device they know you scammer !!

Will we still see blank screen after 2 minutes of loading, or anything else?

Sounak Biswas said:
Will we still see blank screen after 2 minutes of loading, or anything else?
Click to expand...
Click to collapse
When twrp boots, it will be blank screen, so don't panic.
you have to wait for atleast 2 minutes before executing the next commands

Has anyone been able to flash supersu.zip through shell yet?

Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Jion This https://t.me/joinchat/HrjmCBBex1F5cy9q0m7cQg

Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Use magisk, https://forum.xda-developers.com/realme-3/how-to/rooting-guide-realme-3-t3927028

Sounak Biswas said:
Has anyone been able to flash supersu.zip through shell yet?
Click to expand...
Click to collapse
Superuser on magisk .

I need scatter file
Make scatter file for realme 3 my rm3 is deadboot

johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
Please Download The Stock Rom inside You Get Scatter File Ok

johncedd said:
Make scatter file for realme 3 my rm3 is deadboot
Click to expand...
Click to collapse
If it's soft brick or bootloop see this guide:
https://forum.xda-developers.com/realme-3/how-to/realme-3-recover-soft-brick-boot-loop-t3920401
if it's hard brick go to service center.
I am not sure how scatter file will help you recover from hard brick.
Here is the scatter file for mt6771 chipset:
https://drive.google.com/file/d/1pjIkb9xuq4WRFVh72V3V6eNfzdhRTk8L/view

Thanks Sir

jeffalaiza said:
Thanks Sir
Click to expand...
Click to collapse
Welcome sir

Work on ROM A.18 sir ?

hi sir, wolud you help me
what step should i do I got HARDBRICK realme 3?
I'm a newbie

Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
CreateProcess failed: the system cannot find the file specified. (2)
error: Cannot generate image for userdata
Click to expand...
Click to collapse
Any advice or solution to rectify this problem?

TwelveMoon said:
Hello. I've recently tried to install TWRP on my RMX1821, and followed all the instructions but hurdled when I tried to format userdata. It says:
Any advice or solution to rectify this problem?
Click to expand...
Click to collapse
Use adb platform tools..

I want to unlock the bootloader but in the application step I have waited more than 1 hour and the server has not shown success.

Can you share a link of video tutorial please.
fawazahmed0 said:
All Praise and All Thanks To God
Features:
1. You can directly flash ota zip from twrp, but you have to decrypt it first using ozipdecrypt from here:
https://github.com/bkerler/oppo_ozip_decrypt
2. Fstab includes all the partitions to backup and restore
Steps to flash TWRP:
Note: This will erase all your data, so please backup important things like photos,contacts etc , before following this procedure
1. Unlock bootloader if not done yet.
see this guide to unlock:
https://forum.xda-developers.com/realme-3/how-to/bootloader-unlock-realme-3guide-t3920394
2. power off your phone by pressing power button, now hold volume down + power button to boot into fastboot mode
3. Commands to execute:
fastboot flash recovery twrp-3.3.1-0-RMX1821.img
fastboot -w
fastboot oem reboot-recovery
4.Touch will not work for 40 seconds, just wait until touch starts to work.
5. Now very Important part, take full twrp backup in your sdcard and keep it safe in your pc (This backup will be helpful in future incase you soft brick your device or have some issues in your phone such as network or volte or some other **** not working)
6a. Copy and install Disable_Dm-Verity_ForceEncrypt_Quota_.zip in your phone using:
adb push Disable_Dm-Verity_ForceEncrypt_Quota_.zip /
adb shell twrp install Disable_Dm-Verity_ForceEncrypt_Quota_.zip
or
b. copy the Disable_Dm-Verity_ForceEncrypt_Quota_.zip in sdcard and install using twrp touch interface, then wipe dalvik, cache, data and format data.
6. Done!
There will be red blinking notification due to flashing Disable_Dm-Verity_ForceEncrypt_Quota_.zip, you can just ignore it. If you don't like the red bliking notification, just restore your nvdata, vendor and system from twrp backup.
Disable_Dm-Verity_ForceEncrypt_Quota_.zip: https://www.androidfilehost.com/?fid=6006931924117924278
or download the latest version from here: https://zackptg5.com/android.php#disverfe
TWRP : https://github.com/fawazahmed0/android_device_Realme3_RMX1821/releases
Device Tree: https://github.com/fawazahmed0/android_device_Realme3_RMX1821
How to boot to recovery:
From adb:
adb reboot recovery
adb shell reboot recovery
From fastboot mode:
fastboot oem reboot-recovery
If you want to boot to recovery using power + vol down button, then you have to lock the bootloader using:
fastboot flashing lock
Warning: if you did not follow the steps properly, either the twrp will be blank or you will be in endless recovery mode bootloop or you will revert back to stock recovery next time you try to boot to twrp.
Contributors:
@chankruze for his device tree and stable twrp:
https://github.com/N00bTree/android_device_realme_spartan
Blackcat: Got to know verity can be disabled by modifying vendor partition
@haditriw: For testing and verifying vendor can be modified in this phone
@ashu7073 for fixing screen issue and for his device tree
@jeffalaiza for making twrp ports
@Zackptg5 for his Disable_Dm-Verity_ForceEncrypt.zip
Click to expand...
Click to collapse
ROM manager shows that TWRP is my current recovery but I can't boot into TWRP recovery, I don't understand the issue.

Development [RECOVERY][OFFICIAL][TWRP-3.7.0_12] TWRP for POCO F4

Code:
*** Disclaimer ***
All flashing is done at your own risk!
While nothing from this thread should break your device,
don't come back here blaming anyone if it does!
Introduction
Team Win Recovery Project 3.x, or twrp3 for short, is a custom recovery built with ease of use and
customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to
mash. The GUI is also fully XML driven and completely theme-able. You can change just about
every aspect of the look and
Click to expand...
Click to collapse
Prerequisites:
Code:
. Unlocked Bootloader
Installation instructions:
Recovery Install Method:
Simply download the TWRP-3.7.0_12-0 from twrp website and boot it using fastboot mode, steps are mentioned below
Fastboot Boot Method:
You will need the platform-tools from the Android SDK on your computer. Download only the platform-tools according to your device to get adb and fastboot binaries.
On your device, go into Settings -> About and find the Build Number and tap on it 7 times to enable developer settings. Press back and go into Developer Options and enable USB debugging. From your computer, open a command prompt and type
Code:
adb reboot bootloader
You should now be in fastboot mode.
Download the twrp boot image from the link given below, and copy twrp.img file into the same folder as your adb and fastboot binaries and type:
Code:
fastboot boot twrp.img
You will be booted to TWRP, from there go to advanced and then click on "Flash Current TWRP"
REMEMBER: if the device waspreviously rooted, then root has been overwritten, you need to flash the magisk zip again to retain root
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Device Changelog
Version:3.7.0_12-0:
Initial Official Release
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads
Official TWRP Website
My Telegram TWRP Support Group:
https://t.me/pocof4_recoveriesCredits:
- TWRP Team
Sources
TWRP: https://github.com/TeamWin/android_bootable_recovery
Device Tree: https://github.com/TeamWin/android_device_xiaomi_munch
Kernel Tree: https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/munch-s-oss
Status: Stable
TWRP: 3.7.0_12

reserved 1

reserved 2

Build will be live on twrp.me soon

Wow nice!

Build is live

Decrypting working? Will working on future Android 13 with decrypting? I know that dev received Android 13 already

Yes decrypting working fine, even on Android 13

When I updated yesterday, I immediately flashed it without losing data. For today's update, why doesn't it turn on, you have to turn on the new data format, is there the same or a solution

Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).

dreamdrake said:
Can I just boot it with fastboot and flash Magisk flashable file in order to root the phone?
I have seen videos on youtube showing exactly that, just wanted to make sure it's doable.
Just want to root the phone, do not intend to flash any rom (yet).
Click to expand...
Click to collapse
If you already have your magisk_patched.img, you can choose which method you want:
1. with Fastboot + TWRP (temporary)
fastboot boot [drag and drop recovery.img]
flash your magisk_patched.img in boot partition + check "Flash to both slots"
reboot to system
2. only Fastboot
fastboot flash boot_a [drag and drop magisk_patched.img]
fastboot flash boot_b [drag and drop magisk_patched.img]
fastboot reboot

What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?

dreamdrake said:
What if I would "fastboot boot TWRP.img" and then flash Magisk flashable version checking "flash to both slots"?
Click to expand...
Click to collapse
When you check "Flash to both slots" TWRP will flash the makisk_patched.img to boot_a and boot_b.
I'm not sure, but if you don't check the box, TWRP will maybe flash to inactive slot and you are NOT rooted.
Edit: You can check which slot is active with adb shell getprop ro.boot.slot_suffix

Is it possible to make a backup of the installed rom with relative restore using this official twrp? If yes, which files to select

ok... i can't access to internal storage via pc. I formated data (type yes), rebooted to recovery again and my pc sees internal storage but there is no info about size and i can't copy files to it. It shows message something like "this device is disconnected". I tried to reinstall adb drivers, tried to restart my pc and it's not working. I used adb sideload to falsh ROM and after i booted to ROM, rebooted to recovery I can access internal storage via TWRP.

Runs super laggy with kernel compiled with gcc which is very strange and annoying.

Can't access storage with PC... Disabled and enabled MTP multiple times...
I had to flash ROM via OTG...

Oppo A83 [CPH1729] TWRP RECOVERY

⚠Warning: This is not official TWRP, use it at your own risk!!!
Data will be erased. Back up if neccessary
This device is kind of weird so to flash twrp you need these things:
1. Prepare materials​
Install driver so as to have access to preloader (Just install automatically and no need to do anything in device manager)
This software to access to preloader -> fastboot (fastboot is somehow not available via adb methods) Enter fastboot
This tool for flashing
2. Unlock bootloader (need testpoint, python, git (optional) - you can search on google)​
Use this tool - go to this section. Follow guides to unlock bootloader (remember to use testpoint not hardware buttons)
3. Enter fastboot mode​
Use latest MTK META Ultility tool
Select Reboot Fastboot Mode in BRom section
Hold volume down button. While holding connect it to your computer
*Now your phone is in fastboot mode​4. Flash​
Open platform-tools folder in Downloads folder
Shift + Right click then "open command window here"
Input these commands into cmd
fastboot flash boot drag twrp file to cmd
fastboot flash recovery drag twrp file to cmd.
fastboot reboot. Swipe to allow modification in twrp (to make sure that stockboot wont replace twrp). After that reboot to recovery to make it installed on your device permanently.
Now your recovery is ready to flash file you can push stock image file to your root folder using adb command: "adb push. Drag the stock image file. /" (Because Decryption right now doesnt work on my device yet)
Enjoy
*Sounds crazy but it is required to make sure twrp is installed correctly​*If successful, when you power on, you will get a red section on top of your device. If you want to recover to stock recovery, flash the recovery.img below.​*Also, if you want to make your own twrp, you can try recovery.img below.​
Also thanks SebaUbuntu and Mofadal El-Tayeb (مُفَضَّل) for awesome apps
​
​​
​

Here is the PBRB version for this device

Hey I'm stuck in the third step.can you please help me?

Sorry for late reply. What problems do you have?

Is this the stock boot image you provided?

SAMIUL ISLAM 0 said:
Is this the stock boot image you provided?
Click to expand...
Click to collapse
Yes it is. I took it from OTA update

Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher

mahmoud2503 said:
Hey friends
I want to upgrade my oppo a 83 fone to a costum rom to upgrade my androide to android 8 or higher
Click to expand...
Click to collapse
Unfortunately, I have no custom roms available for this phone (