Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
You shouldn't have used the nand erase option, that is an easy way to brick the device when used improperly. I doubt you will be able to repair it with Odin now.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
stefan1301 said:
But, you see, i did it as a last option, because i tried to flash several different roms before that, and at first it didn’t let me flash Oreo and older, just failed in odin, because of Pie binary.
So i flashed official pie ( first time only AP, and second time all files), and it didn’t help either, the phone was still acting the same (the same thinh happens like before all the flashing).
I can’t boot into recovery, it ends up being the same as trying to boot normally, and it won’t let me flash other recovery because of the frp.
Click to expand...
Click to collapse
Sounds to me like the hardware itself is bricked or damaged. If that is the case, the only option is to replace the motherboard.
Sent from my SM-S767VL using Tapatalk
Try to flash latest rom
Here is the solution
stefan1301 said:
Greetings,
I have a certain problem, i have an Samsung J6 Plus which has suddenly rebooted and since then it just turns on the samsung logo, then it turns off the screen, then the screen flashes and finally it reboots again.
I have tried everything, the phone has a pie binary so i could only flash one rom i found.
But even after flashing every part of OS on its own, performing a NAND Erase and re-partitioning with pit file, i still get the same result. The phone restarts after the flash, and then turns off the screen, flashes etc...
Every time the same, no matter what i try.
Has anyone experienced similar problem ?
I have read about 15 of other threads here with similar problems and tried every solution that works for some people but nothing works for me.
Click to expand...
Click to collapse
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
alaanhaliko said:
I'm having the same issue after oreo update for j7 nxt so what i did is easily rooting phone via Magisk!
Ahh,, maybe u have frp lock?
Just google for (Combination rom of your device) then flash it with odin. After that you can go to settings -> about device -> software information -> Build number (click on this option 5-7 times).
Then back to settings you'll see an additiona setting (Developer options) go inside it and click on (OEM unlocking) and cograts you have unlocked frp lock
Note : there is a fairly chance that you won't find this option (OEM unlocking)! So what to do? You just need to trick the phone by changing the date/time for 2014 and restart then check if it's there if still not there just try again with different dates for ex. 2013 and restart (keep doind this and every restart check the developer options section, Just KEEP TRY!! until you find the button there in developer options
After that go flash the stock rom then install TWRP then ROOT via Magisk and you're all done
Click to expand...
Click to collapse
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Droidriven said:
OEM unlock does not "by itself" remove FRP, there is more to the process than just enabling OEM unlock, removing the Google account from the device and disabling MDM(find my device) is what actually "unlocks" FRP.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
alaanhaliko said:
Since he didn't mention about getting this message "only official binaries are allowed to be flashed"
Then itsn't something related to RMM.
Also as what he said he can't flash TWRP as he gets "OEM LOCK" it's also called "FRP LOCK" the type of lock i'm talking about is in (download mode) that doesn't allow to install custom binaries, so the only solution is tirning (OEM lock) option and that's enough to flash custom binaries such as TWRP.
The type you are talking about seems to be RMM lock which could be fixed using Miracle Box but as it's not allowed to dicuss this stuff here in xda + his problem is frp locked and phone doesn't booting, so the only solution we can provide in this situation is Combination rom which will boot even if you bricked your phone, even if you've Rooted and bricked your device's kernel (even if it won't boot anymore).. combination should boot, i faced the exact issue but as i explained in my last post. And hmm it could be 80% the solution.
Thank for your reply.
Your Iraqi friend,
My regards.
Click to expand...
Click to collapse
No, I'm talking specifically of FRP lock.
The point you make about binaries has nothing to do with FRP. Binaries can be blocked on both FRP locked and FRP unlocked devices. The binaries only prevent flashing firmware with a lower binary than the current binary installed on the device. Binary version is related to RMM or KG state, not FRP. FRP is directly related to MDM and only "partially" related to the things you mention and only because there are other "tamper-proof" elements that "can" trigger FRP. Have you ever noticed that a device that does not have a Google account signed in does not encounter FRP issues when the device is factory reset, but if there is a Google account signed in the device, factory reset triggers FRP? If it were as you you seem to be suggesting, FRP would be triggered on devices that have no Google account associated to them when attempting to flash/modify the device, but this is not what happens.
OEM unlock really only applies to unlocking bootloader in order to flash unapproved software or make modifications to the system partition without being blocked.
https://blog.elcomsoft.com/2016/05/understanding-and-bypassing-reset-protection/
Sent from my SM-S767VL using Tapatalk
Related
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076
arys64 said:
This is not for the A5 but I could only find this (hope this help):
"In download mode the "RMM STATE: PRENORMAL" is gone. that line only appeared after the bootloader was unlocked"
On this post:
https://forum.xda-developers.com/showpost.php?p=74045971&postcount=1076
Click to expand...
Click to collapse
Yeah...a few users are testing the 168 hour theory. We will find out what happens in 6 days
carlosmedia said:
So I have been playing with my SM-A520F for a while now.
First I used TWRP and Magisk to root, and as I explained on other post I am now trying to install Magisk directly on the Firmware without using TWRP which trips Knox
So I needed to make a boot.img dump, for which I found a tutorial but I need a UK Firmware. I don't know If this has to do with it but it turned out to be a carrier firmware and I had to delete hidden.img to make it work - The next time I enetred into DL Mode to check if everything was official after flashing, one new item had appeared on the list;
RMM STATERENORMAL
I tried to re-flash my last ROM (was a Russian one) but sadly the 'RMM' didn't disappeared with the UK ROM
I need to know, if it's possible, an explanation of why it appeared (Maybe the firmware? Maybe I flashed to many things on little time?)
When it will will go away. (I heard that you need to have your phone 1 week on without turning it off or rebooting, +168 hours of uptime)
And if after it deactivates I have the risk of it enabling itself back on,
Many questions, but this has literally f*cked my mind up, and a google search hasn't clarified anything, because apparently no body in the world knows what is it for, and Samsung itself will keep its mouth shut about it.
Click to expand...
Click to collapse
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped
carlosmedia said:
I just upgraded my firmware, deactivated Developer options and waited the week.
The RMM security line has disappeared and was replaced by the regular FRP lock. Knox was also tripped
Click to expand...
Click to collapse
Try to flash it with combination firmware, enable OEM Unlock, remove screen lock and Google account.
Finally disable the RMM app called RLC, and modify the build.prop as posted earlier. If your don't do all those, the RMM lock will re-activate as soon as you try to flash a custom recovery.
Unfortunately simply waiting for a week, will not auto-magically solve all you problems, you must disable it manually.
The reason you had to wait, is to able able to flash signed firmware again.
billa said:
Here's the answer to your questions:
The new RMM security is designed to stop the theft of new phones by disabling the OEM-Unlock settings for 168-hours, whenever a non-original/un-signed firmware is flashed.
What you need to do is flash it with a full official stock firmware which was designed specifically for your phone model using Odin v3.13.1 https://forum.xda-developers.com/galaxy-s8+/how-to/guide-flash-oreo-g955fxxu1crb7-using-t3755789, keep it turned on constantly for 168 hours about 7-days (do not restart!), then enable OEM-Unlock. During this waiting period do not touch the phone, do not try to flash anything, just leave it turned on and plugged into the charger.
Finally, flash a custom recovery like TWRP, BUT do not let the system to boot up normally. Immediately after the recovery flash reboot into recovery by holding Vol Up + Home/Bixby + Power, and flash the RMM Disabler zip ( https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22 ) through recovery.
This way when you boot the system, the RMM lock will be already disabled so you won't get locked again.
However, you must redo all these steps again every time you flash a full system firmware, because that enables RMM security again.
Looks like it's only affecting the international Exynos models for now, the US Qualcomm models do not have this RMM yet, but of course Sammy could activate it at anytime with a simple firmware upgrade.
Click to expand...
Click to collapse
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste
carlosmedia said:
Tbh, I will just stop this root sh*t for a while.
My main concern now is:
Now that there is a way to leave RMM disabled, is there a way to untrip knox?
I just want to untrip it and then install an official firmware to not touch my phone's software for a while, I just had enough for now.
I know this is completely unreleated to the main post but I just feel a new post would be much of an space waste
Click to expand...
Click to collapse
Unfortunately there's no way for us mere mortals to "untrip Knox". I'm pretty sure Samsung can do it internally but not us, so you just gonna have to live with it. It's not the end of the world, just a flag to tell Samsung that someone has messed with it.
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
rkevin_arch said:
So, being the stupid person I am I broke my Mate SE one day after purchase ._. I'm posting my entire process just in case anything helps.
I started off by updating to the latest ROM and then unlocking the bootloader, which went fairly well, then flashed TWRP. A lot of versions I found didn't work(Bootloader says Func NO: 11 (recovery image) and Error NO: 2 (load failed!)), but I got a working version here: https://forum.xda-developers.com/honor-7x/development/oreo-twrp-complete-backup-t3764500 .
After that, I installed Magisk, which went well, then Xposed framework inside Magisk, which put my phone in a bootloop. I didn't know what to do, so I went with a factory reset[terrible idea]. Now, my phone has the FRP lock on, and the android setup is stuck on a "just a sec" page, right after selecting language and wifi, so I can't login to my google account to disable the FRP lock.
I tried flashing, but apparently the FRP lock stops me from being able to flash anything inside the bootloader. I do still have my TWRP recovery and a backup of the kernel and ramdisk(sadly nothing else useful, although I do also have dts, dfx, vendor_image, oeminfo and secure_storage) but restoring them or wiping the system again has no effect(still stuck on "just a sec").
After some google searching someone in a thread said that I should use stock recovery to wipe factory data(by restoring the stock recovery in TWRP), and I would be able to get past the "just a sec" problem, but I am reluctant because if it doesn't work, I would permanently lose my TWRP recovery with no way to flash it back(because of that FRP lock). I also tried installing update.app and other stock ROMs from various sources using TWRP, but all of them had a "check_write_data_to_partition, write data error" error. I'm not sure if it's related to FRP.
I think my next course of action is to either a) disable FRP in recovery, b) bypass the setup screen or c) install some ROM on it and somehow bypassing the check_write_data_to_partition error, but I'm not sure how to do any of these. Any ideas or suggestions? Thanks.
Click to expand...
Click to collapse
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
mrmazak said:
There is an unlock frp patch by a dev in another that works with the 7x. It should work for you too.
I will find link when I get off the road
Click to expand...
Click to collapse
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
mrmazak said:
Link to frp unlock
https://mega.nz/#!nw0wAYoA!hYtf78s0AjwRCpPo_NQ2F4LYclngNBNurJNETypSNKQ
Posted many places. But I found it on the bottom of post 2.
Here.
https://forum.xda-developers.com/showpost.php?p=76398556&postcount=2
Click to expand...
Click to collapse
Thanks for the help! It worked, and the bootloader says FRP unlocked. It didn't help the "just a sec" issue, but since I can use fastboot flash, I might be able to flash a new rom in it and just ditch EMUI[probably]. I'll play around with it a bit. Again, thanks a lot for your help!
I got everything working now! Just in case anyone had the same "just a sec" issue: it was fixed by flashing stock recovery then doing a factory reset there(I'm not sure how that's different from wiping dalvik/cache/data/internal storage in twrp, but it makes a difference apparantly). Just flashing custom ROMs didn't solve the problem. After that I installed magisk, and then installed this version of xposed: https://forum.xda-developers.com/showpost.php?p=76582399&postcount=11 . I installed the v90-beta3 version before which caused the bootloop, but it is fixed in the next version. Magisk has some issues so the magisk manager can't start with internet(adb logcat says there's a NullPointerException in com.topjohnwu.magisk.database.RepoDatabaseHelper.removeRepo) but frankly I don't need to open it with internet anyways. Now I have everything I need on my new phone! Thanks to mrmazak for pointing me to the right direction.
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
NoirX said:
Hello
I was on an android 9.0 GSI image.
After disabling developer options in settings the device couldn't boot.
It was showing "custom firmware blocked by FRP lock" error.
I couldn't enter TWRP recovery as well. So I restored stock firmware through odin.
I tried to toggle on OEM unlock in settings with no result, after reboot it remains OEM and FRP locked. I also tried to OEM unlock through combination firmware but the toggle doesn't work.
Does anyone know if there is a solution to this problem ?
Thanks in advance,
Click to expand...
Click to collapse
Probably going to have to wait 7 days
*Detection* said:
Probably going to have to wait 7 days
Click to expand...
Click to collapse
I tried that too but i think the issue is a little bit more complicated. The toggle is there but it does nothing. On stock firmware it goes through a factory reset as expected but the device remains oem locked. On combination firmware the toggle is there too, but it won't switch on. Thank you.
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
*Detection* said:
Why are you using a patched ODIN?
Uncheck "Auto Reboot" in ODIN settings, once TWRP has flashed disconnect USB then power off the phone and immediately boot into recovery, do not let it reboot first
Click to expand...
Click to collapse
I'll try with normal Odin next time. I do suspect this might have been the issue.
AMDPOWERFIST said:
I have a similar issue....
Waited a full week for the OEM Unlock.
Ticked it last night.
Rebooted to download mode > Flashed TWRP > Passed.
Rebooted to TWRP, it showed up, then it presented a bunch of red code errors before quickly resetting and defaulting back to normal Recovery again..... WTF
Looks like ill have to wait another 7 days because in Download mode it now says OEM Mode is Unlocked but its still RMM State: PreNormal mode on... no OEM Unlock setting in my Developer settings.
Anyone else had an issue with TWRP randomly throwing up errors upon first boot and then restarting before you can do anything???
I used the Patched ODIN here: https://forum.xda-developers.com/android/software/patched-odin-3-13-1-t3762572
Combined with TWRP 3.2.3-0 recovery....
Click to expand...
Click to collapse
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
bulky68 said:
@*Detection*, I had the exact same issue as yours tonight when I tried to install TWRP for the first time. Red code errors then an automatic restart and then default back to normal Recovery. As far as I know I used normal Odin and I followed installation instructions to the letter. So back to square one for me. I'll definitely have another crack in 7 days. Interested to know how you went with your second effort. If you had success please post what you did step by step.
And @AMDPOWERFIST, out of interest, how do you power the phone OFF from the Download screen? I know how to restart. Thanks.
Click to expand...
Click to collapse
Just realised that I got the 2 posters mixed up in my previous post. My apologies @*Detection* and @AMDPOWERFIST.
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
chriskay525 said:
hello, i was hoping to get some help with my device not being rootable.
i followed these two guides word for word i cant post links because im new here but i followed the naldotech twrp + root s9 guide and the highonandroid s9 root guide.
tried both reinstalled OS with csc and home-csc twice for each one when my phone was stuck in a loop so i can make sure that its back to factory before i try another method. my phone it either gets stuck at samsung logo or just reboots to recovery never goes to samsung logo my oem unlock button always stays off even though i follow the steps and it says under it that bootloader already unlocked and it never goes blue and oem lock: off in download mode, i did not setup my samsung or google accounts in any of those resets that way no settings get synced.
i really need the help i have been trying this for the past month and a half and i have tried everything i could think off and nothing is working.
current software installed: G960FXXU2CRLI_G960FOXM2CRLI_XSG
Model: SM-G960F/DS
OS: 9.0.0
Click to expand...
Click to collapse
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Akhayev said:
Did u fix it ? Cos I have similar issue but on my phone it says the bootloader is locked and the OEM unlock option never turns on , when I turn it on it does factory reset and reboot the device but the option stays off
Click to expand...
Click to collapse
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
chriskay525 said:
no fix yet and same thing is happening to me the OEM options always stays off and that's even after a clean firmware install i really hope we can find a way to fix this
Click to expand...
Click to collapse
Did u wait for 7 days ?
I have a bricked Redmi Note 5 Pro. Stock firmware, locked bootloader, did literally nothing that would cause this. Just updated firmware (it happened few years ago, just now decided to try and repair it), and after update It's stuck in Mi-Recovery 3.0, with options only for "Reboot", "Wipe Data" and "Connect with MIAssistant", with red text at the bottom "This MIUI version can't be installed on this device" (see photo). Tried everything form this menu, nothing solves the problem. I can boot into fastboot but can't use it as the bootloader is locked and debugging is off. I can go into EDL mode but can't flash as I need to log in into Mi Account, and my sister (this phone was hers) forgot the password and even the account which was connected to this device. I was looking for MiFlash that bypasses authorization but can't find any that is not marked as malware (anyone knows of any that is safe?). At was past the warranty and I've tried to ask few phone-repair shops but the said that is unrepairable.
Any ideas what I can check or try next to solve this problem?
BTW. Does anyone knows why all of this happened? As I already said, never did anything with OS, only updated it which caused brick. My only idea is, as this phone was bought not from official store, that it might be a phone that was bought cheaper in china, then flashed with modified global OS and after update it was replaced with official global OS which bricked the phone. No idea if something like this is possible.
Edit [Sep 19, 2021]: I got somewhere. Used Firehose file to flash whyred global image without authenitcation. Got into system. I can at least go into fastboot and it's detected correctly in windows. Now I'm trying to get root, flash TWRP and any non-stock OS. Couldn't flash directly via fastboot because of anti-rollback check. Tried to do "fastboot boot twrp_rn5pro.img" which resulted in FAIL in console (status read failed - too many links) and "The system has been destroyed - click the power button to shutdown".
Edit2 [Sep 19, 2021]: Looks like my bootloader is still locked and that's why I can't flash custom recovery. But when I look in the phone settings it says that my phone is already unlocked. Checking in fastboot via PC says otherwise. Enabled OEM unlocking, but fastboot still says "FAILED (remote: Token Verify Failed, Reboot the device". Can't unlock it using MiUnlock cause they say that I need to set my account as available to unlock in unlock status on my device, but I can't do it as my device says that it's already unlocked.
Edit3 [Sep 20, 2021]: I've tried other tool: XiaoMiTool V2 (by Francesco Tescari). As the option "My device works normally I want to mod it" didn't work I chose "My device is bricked I want to unbrick it". Selected option without unlocking bootloader (wouldn't work). And it actually auto-detected that it's chinese phone and flashed chinese OS (MIUI 10.3 Stable). At the boot I got a prompt that this device is locked and I need to log into my Mi account (the one I logged in in the last ROM - from first Edit), after logging in it let me go through setup (luckily there was English). But phone still says that it's unlocked while it's still locked in fastboot. So in the end it didn't got me anywhere, but at least I know that orginally it was a chinese phone.
Edit4 [Sep 20, 2021]: Finally solved the problem! Used this tutorial. Did everything like shown on video and at the end I have MIUI 12 with unlocked bootloader (this time it's actually unlocked - checked with fastboot). Managed to flash TWRP using dummy.img and flashing to recovery. Couldn't boot from img, but vol+ + power did the job. With working recovery I can do everything else I wanted to do.
I had the same issue, which I also managed to fix. I thought I'd share what I did here.
My phone was bricked with access to MIUI recovery and Fastboot. My phone was locked, however my phone was not linked to my Mi account, and so I couldn't unlock it using the Mi Unlock tool. The only way to get into EDL mode was via the testpoint method. It's not as scary as people may think.
Many of the YouTube videos on testpoint show that you have to touch the two terminals while pushing the cable into the phone. Several times I was able to activate EDL mode without doing both at the same time - i.e. I could just connect the cable and touch the two terminals (I used a paper clip) and the phone would enter EDL mode. I think it might have had something to do with me pressing the power button. In my case, I had to have the battery disconnected from the circuit to get into EDL mode.
I used the Xiaomi Flash tool. Always remember to select not to relock the bootloader. I think it's stupid that relocking is the default option and that the radio buttons are at the bottom of the program and sometimes not visible on a laptop. That's how I got into this mess in the first place!
One of the things that I think causes the "MIUI version" problem is attempting to install the incorrect stock ROM. The phones may be fussy about which stock ROM they will accept. In my case, I thought the phone was a global version, then worked out that it was probably a Chinese version.
I replaced the firehose files in all the ROMs I attempted flashing with the ones supplied on XDA. The Xiaomi Flash tool reported success several times, but when starting up the phone it would go into recovery with the "MIUI version" message. I tried about six different MIUI ROMs with the testpoint method, both global and Chinese, before stumbling on the one that worked (after replacing the firehose files): whyred_images_V11.0.2.0.PEICNXM_20191023.0000.00_9.0_cn
When I got back into MIUI, I linked the phone to my MI account and then attempted flashing the latest LineageOS (which was what I was trying to do in the first place), using the Lineage recovery. The phone wasn't accepting the Lineage recovery, so I flashed OrangeFox-R11.0-Stable-whyred. I had to boot to Orangefox in order to flash it. You copy the Orangefox zip file to your phone using your computer when you have MIUI up and running, then you enter Fastboot and run the following command from your computer:
fastboot boot recovery.img
From Orangefox, you then select the Orangefox zip file on your phone and swipe to install.
Once that was done, I rebooted to recovery and did a wipe of the phone. It wasn't enough for me to wipe Dalvik/ ART Cache and Cache (as recommended), I had to also wipe System, Vendor and Data. (I tried just the first two and the LOS installation was corrupt, even though it was reported as being successful.) I then copied LOS to a micro SD card, inserted it into the phone and mounted it, before flashing LOS by navigating to the zip file on the SD card, selecting it and selecting wipe to install.
Finally success!
I think the key with the testpoint method is to keep trying ROMs until you stumble on the one that works. If the Xiaomi Flash tool reports success, I think it means you are doing something right. I also wonder if a lot of people who have the "MIUI version" issue have a phone with the Chinese ROM and don't realise it.
Hope this helped someone!
by any chances how do you unlock bootloader if you just bypass the mi account?
yoshukii19 said:
by any chances how do you unlock bootloader if you just bypass the mi account?
Click to expand...
Click to collapse
No hacking ... Why did you bypass mi account???
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
the reason is I got my phone Redmi Note 5 Pro on fb marketplace by swapping my old phone, when I'm using it there's no mi account logged in on my phone then I tried to install the latest MIUI 12 by flashing it on MiFlash but I didn't notice that I didn't change the setting on clean all so it locked my bootloader, after I manage to fix the issue about my phone because it doesn't open and it only boot on recovery with a message "This MIUI...." and make it boot by flashing cn official rom, it says that my phone is locked and I need to logged in the old mi account, I already ask the previous owner but he said he doesn't have an access on that account, even the number and email are already lost
drnightshadow said:
No hacking ... Why did you bypass mi account???
Click to expand...
Click to collapse
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Aurora333 said:
If it's locked and you haven't registered the phone with Mi Account, then you will need to use test point. There are a lot of claims that it's not necessary, but I tried many of them and it wouldn't work. I think they are a load of rubbish to get you to pay money. Test point is not that hard, but you need to pick the right ROM.
Click to expand...
Click to collapse
Why did you quote me?!?