Hello ... Any ideas on recovering IMEI after successful root of Note9 ?
IMEI currently unknown (both), TWRP shows empty EFS folder (should i see these files?), Software Baseband is UNKNOWN too.
Software factory wipe done with no effect, OEM unlock is unlocked (and not greyed out).
Thanks
Just wondering if anyone has recovered from this ?
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
bober10113 said:
did you read all of dr ketans thread on root?
Click to expand...
Click to collapse
do let us know the tread link
bober10113 said:
did you read all of dr ketans thread on root?
go to general discussion section / dr ketan oem fix and root and simply do a search in that thread for imei
edit
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143
basicaly you flash back stock firmware and try again.
Click to expand...
Click to collapse
nrah said:
do let us know the tread link
Click to expand...
Click to collapse
added link
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
nrah said:
Thanks for the link
I have been plowing through - i still can't work out how to backup the EFS before TWRP is installed.
Should the backup take place after TWRP is installed, before the first reboot (and before running the Dr's script) ??
Click to expand...
Click to collapse
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
bober10113 said:
restore back to stock and be sure everything works.
then flash twrp with odin and dont let phone reboot.
manualy reboot to recovery. using an external sd card backup EFS partition.
go to wipe menu and format data.
go to reboot menu and reboot back to recovery.
go to wipe menu and do a factory wipe, the default swipe right option.
now you have 2 choices:
either flash dr ketan method 1 root oem fix zip and stay on stock firmware.
or
flash dr ketan method 1 zip and then flash a custom rom.
then reboot. if no signal restore the backup of efs you made earlier.
Click to expand...
Click to collapse
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
nrah said:
I have been doing this, except for the additional step on the factory wipe that you pointed out - thanks.
But after three full rounds of rooting and trying to restore the EFS, i still have "unkown" and no Baseband information when i get to the end. When i return to the stock image, both Baseband & IMEI's are present.
I have backed up EFS/Baseband/Carrier configs/carrier images successfully and restored all 4 partitions. But IMEI does not return.
Click to expand...
Click to collapse
are you on pie or oreo?
bober10113 said:
are you on pie or oreo?
Click to expand...
Click to collapse
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
nrah said:
8.1, Oreo .. was thinking of grabbing a ver9 image and giving it a go
Click to expand...
Click to collapse
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
bober10113 said:
did you try method 2 in dr ketans oem fix root hread?
also maybe try flashing a custom rom instead of being on stock and see if that works out for you.
but to think of it, believe your issue is kernel related. i think i remember reading something about it.
so after twrp and data format , reboot back to twrp and oem fix, dont reboot to OS yet. try flashing endurance kernel or tgp kernel. just be sure to take the appropriate oreo or pie version depending on what android os version you go on.
Click to expand...
Click to collapse
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
nrah said:
:good:
I have not tried method 2 yet .. I did flash OREO and when i tried to run to flash TWRP, the console echoed "Only official released binaries are allowed to be flashed(Recovery)". So i will need to roll back to an earlier image on 8.1
Forgive my lack of knowledge - where would i find the endurance kernel ? Thanks.
Click to expand...
Click to collapse
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
if i dont do the manual software update check thing after a binaries issue, i would get stuck.
also unrelated:
when you flash stock, you flash all 5 files right?( in odin csc slot you put csc.md5 and not the home csc.md5 and all the other slots only have 1 appropriate file so you cant go wrong there)
endurance:
https://forum.xda-developers.com/galaxy-note-9/development/kernel-endurance-kernel-v1-1-7-t3883862/
v2.xxxx is pie
v1.xxxx is oreo
after flashing kernel.zip you MUST flash magisk or you wont have anyways to manage root and give permissions.
so also flash right after kernel:
https://github.com/topjohnwu/Magisk/releases/download/v19.3/Magisk-v19.3.zip will eventualy be not the latest( check last link below dor mire up to date)
then if and when phone boots up you can install the magisk manager app:
https://github.com/topjohnwu/Magisk/releases/download/manager-v7.1.2/MagiskManager-v7.1.2.apk
both can be found here are up to date :
https://github.com/topjohnwu/Magisk/releases
bober10113 said:
that binaries issue you had should have been fixed by ketans oem fix root.( method 1)
when you flash back stock to correct the issue. go to system settings and go down to software update and make if manualy find updates. it will then pop up "device registered". then to go to software and tap "build" a few times to make developer options appear.
then go check in dev options oem unlock should say already unlocked."
Click to expand...
Click to collapse
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
nrah said:
In developer mode, it was set for USB debug correctly. The OEM lock option was not present on this OREO version.
Currently bumping back to 8.1
And yes, I select all 4 files in Odin.
Click to expand...
Click to collapse
well thats one of your problems. if oem unlock has not appeared you either need to wait for 7 days or try the method i described by visiting system/software update/manual update and wait for a pop up message that says device registered. then go back to dev options to see of OEM unlock has appeard and says that it is unlocked
Waititng 7 days sure....
That doesn't work imho. Just download an older 8.1 stock rom and flash . u will find OEM to be unlocked there.
The fix in the end was to use the Root_for_OEM_issue_devices_v5 script. I had been using the v3 script. I had followed Max's vid from high on Android, where he's got the earlier script version on his site.
Issue also, once rooted, was that Magisk was out of sync - Magisk was ahead of the manager, so i down graded the manager (once I worked out the release pairs), and magisk was stable again. I did note that the Magisk did not always maintain root for some reason, when the version were out of sync. Possible connection, not sure.
Must admit you learn a lot about these phones when you have a root problem - a lot more compared to someone just following someone else's good work and wanting the %100 it will work path !
Thanks bober10113 for chipping in along the way.
Related
Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
curtricias said:
Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
Click to expand...
Click to collapse
If you were installing MR v4, didn't you read also the OP post #3 about HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
zgfg said:
If you were installing MR v4, didn't you read also the OP post #3 with HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Click to expand...
Click to collapse
Forgot to mention. Yes. I tried that but software install failed.
curtricias said:
Forgot to mention. Yes. I tried that but software install failed.
Click to expand...
Click to collapse
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
zgfg said:
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Already tried this to. Script ended with more than one device emulator.
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
Click to expand...
Click to collapse
And tried this also. Software installation failed.
I tried to install magic rainbow 4 again and it worked!
First I flashed TWRP from the MR4 topic.
But...
still various apps are missing. When I want to enter developer settings I automatically go back to home screen.
What can I do from there.
@Tecalote I'm gonna quote you here. Maybe you have an idea?
FYI
I managed to solve the problem!
Started over again.
In TWRP full wiped.
Tried HuRUpdater again. Flashed successfully the latest stock EMUi (C432-B505).
Factory reset in stock recovery.
Complete setup.
Rooted with latest Magisk (patched boot.img)
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
VortexHD said:
Hello,
I am new to Samsung devices and have tried to install twrp on my note 9.
Firstly I enabled OEM Unlock in dev options and let the phone reset.
I then went into download mode and went to odin3 and selected the correct twrp file in AP and clicked Flash.
It passed and the phone rebooted to the system.
I then tried to get into twrp but it just took me to the stock recovery so I tried reflashing it and now I get the following error:
"Only official released binaries are allowed to be flashed(recovery)"
I have tried going back to dev options to make sure OEM unlock is enabled but it has completely disappeared!!!
I have tried completely reflashing the stock ROM using Odin with no luck!
Does anyone know what I'm doing wrong? This is getting super frustrating because I have never had this issue on any other android phone.
Any help is Very Appreciated Thank You.
Click to expand...
Click to collapse
ARE YOU EXYNOS OR SNAPDRAGON ?? Below guide is for EXYNOS!!
Did you follow this guide --> https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143 ??
And did you do step 3 ? 3.Download and copy N9_S9_Root_for_OEM_issue_devices_V*.zip to Ext SD card ??i haven't rooted my Note 9 yet but i think that's where you messed up!
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
rana14301 said:
Same problem I tray flash twrp say Only official released binaries are allowed to be flashed(recovery)
I flash FIRMWARE UK...and Germany...but not result...my drives N960f
Click to expand...
Click to collapse
read dr ketans guide in the general discussion thread.
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.
There maybe a number of reasons to go back to the stock ROM. We do not discuss them here
But what to do if you flashed something, wanting to go back to stock, and did not brick your Realme X2 yet? Here is super quick howto guide. There are other possible ways and sequences to perform the task, but the one listed below is tested.
The same procedure applys for a case when you want to downgrade you phone (when its bootloader unlocked). Say, current custom ROMs are based on ColorOS 6.1/Android 9 vendor contents but you have realmeUI/Android 10 already. In order to try one of those custom ROMs you should downgrade to the latest Android 9 stock firmware first.
The essential part of the customized phone is custom recovery. Currently Realme OZIP file does not contain stock recovery inside. It is being generated as explained below, in the post #2, see EDIT3. It means you need to find somewere PROPER stock recovery corresponding to your ROM to put it back. See Realme X2 stock recovery links below, post #2, EDIT4.
Which stock recovery to use? The one for your model and which version is not newer than the ROM version you are flashing. For example, you need A.17 stock ROM for CN model (RMX1991). Then any recovery of A.12, A.14, A.16, A.17 for RMX1991 will work for you.
Download and unzip the stock recovery partition image from the next post, this will be a file like rmx1991-sde20-stock_recovery.img.
Download stock ROM ozip file (for example, from here). Put it to a SD card with a filesystem which supports files more than 2GB (ext4 works fine. Stock recovery, but not ColorOS, supports it). Put the SD card into the phone.
Start (reboot) phone into fastboot mode
From a computer perform fastboot flash recovery rmx1991-sde20-stock_recovery.img
From the fastboot mode by means of volume buttons select 'Recovery mode' and push Power button
From the stock recovery select language needed (there are three only), then 'Install from storage device', then 'From SD card', tap the OZIP file with your ROM
When the update process is done, phone reboots. Most likely, it will not be able to boot normally because you need to wipe out data. Either help the phone with keeping Vol Down button pressed during reboot, or it will boot recovery by itself. Now wipe data (confirm by entering random 4-digit code), select 'Format data'. Phone will reboot
Here it is. Enjoy (or sell your Realme X2 with its shiny stock experience...
If you want to lock bootloader after all above mentioned steps (you have to make them all unless you wanna get a brick ), boot fastboot mode, perform fastboot flashing lock. This will wipe your data again. Then optionally lock 'OEM Unlock' option in 'Developer Options'. Even further, you can install In-DepthTest.apk and sign out from In-Depth Test program.
2022-12-25 EDIT: For downgrade from Android 11 to 10 read this post
I have found out that in fact stock recovery does not exist as a prebuilt file It is being created by the script /system/bin/install-recovery.sh on a basis of stock boot partition and a patch file /system/recovery-from-boot.p
It means in theory you can recreate stock recovery having only Realme ozip file.
EDIT1 The command to do it in Linux shell is
Code:
bspatch boot.img selfmade_stock_recovery.img recovery-from-boot.p
Cool! Tested.
EDIT2. For the current moment when unlocked bootloader breaks fingerprint sensor: as soon as the bootloader is locked again, fingerprint starts functioning as it should.
EDIT3 Becomes clear that each ROM release has its own stock recovery which is generated automatically on the basis of boot.img and recovery-from-boot.p . Not only boot.img is being changed each release, but recovery-from-boot.p is changing as well. If the wrong stock recovery is installed, you might not be able to decrypt data and connect to WiFi from within recovery. Seemingly it may bring you serious problems if locking back bootloader (thus bricking the device). Good thing (as I understood, but not checked yet) is that after flashing stock ROM with a help of a stock recovery next reboot should replace your stock recovery with an up-to-date version of it. So to be on a safe side make sure that you rebooted to system and that your recovery reflashed by the system before you lock bootloader.
EDIT4 In order to combine everything in one place:
Stock recoveries for RMX1991 (China version): here
Stock recoveries for RMX1992 (India version): here
Stock recoveries for RMX1993 (Euro version): here
EDIT5 In later ROM releases patch and script files are relocated into vendor partition, they are /bin/oppo-install-recovery.sh and /recovery-from-boot.p there.
EDIT6 Please note that the method above is working with officially downloaded ROMs from realme support site (read here why).
So this method works if you brick your phone trying to install a global rom to china variant..
Hi,
does only works with SDcard insert.
Because the internal storage is decrypted.
And it does not work on X2.
But why?
Installation failed?
This method will bring back my FP working again right?
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
SkyeJace said:
This method will bring back my FP working again right?
Click to expand...
Click to collapse
You have to lock bootloader for this. See the very last part of the howto, post #1
AldRezaine said:
Can you please confirm this method https://boycracked.com/2019/10/26/official-realme-x2-rmx1991-stock-rom/
Click to expand...
Click to collapse
The site provides generalized instructions for everything
As for Realme X2, there are two methods claimed, one is for ozip file, another for ofp file; last one is not yet publicly available somewhere (the link is replaced by the Coming soon promise).
If you find there something certain regarding ozip procedure for Realme X2, give me the link, please. I couldn't
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
hammerheading said:
hello guys, how can i get the 1993ex stock recovery? i screwd up big time !
Click to expand...
Click to collapse
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
BaDuc said:
why I back to stock rom, apps i uninstalled it is don't auto reinstall?
Click to expand...
Click to collapse
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
yakovpol said:
Read the post #2 in this thread, it contains ample info needed for this. If you are requesting ready-to-flash stock recovery file, you should tell the version of the ROM you are going to flash and powerful word please to it
Click to expand...
Click to collapse
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
yakovpol said:
I am not 100% sure I understand you right. If you are about some stock apps missing after wiping the userdata partition, this is true: some of the apps were preinstalled onto data space (some of them are Weather app, One-Tap Lockscreen). I could find only some of them in a form of apk files.
Click to expand...
Click to collapse
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
hammerheading said:
Thanks a lot for the attention. I tryed to recreate the recovery but with no success because i dont know the proper method, it's a bit over my android skills as i can only root unlock bl and do some minor stuff and GSI is a new thing for me. AS for the version it is the a17 of the 1993ex(eu).
Click to expand...
Click to collapse
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
BaDuc said:
yes, right my mind, including my Breeno is faulty, and now I can't click to setting Breeno in the settings, do you have apk of app, can you send me?
Click to expand...
Click to collapse
Those I have are uploaded to here.
yakovpol said:
Those I have are uploaded to here.
Click to expand...
Click to collapse
thanks you very much
yakovpol said:
For the moment I have one for the EU A.16 version only, look here. Eventually A.17 will be added there too.
Click to expand...
Click to collapse
Thank you so much, that did the trick!! i was able to flash the a17 and the phone is working fine now . But i'm not trully satisfied, i can't find a away to flash a GSI rom successfully, but that's another topic ... Thank you again and keep up the good work !
can u plsss provide stock recovery for realme x2 rmx1992, i bricked my phone trying to install stock os since 2 days, cant find a way..if some has the recovery pls provide it. im able to boot to twrp, bootloader is unloced and with the other recoveries im not able to intsall the stock rom.pls help.
Can send me 1992 stcok recovery file ozip please.
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
this is what the screen says when i try to flash
no content in your post
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time
i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com