Related
Ok guys, im at the end and need your help. I searched for this Problem since yesterday but couldnt find what describes my problems.
I think i did mistake after mistake, and yes im a noob, so feel free to dump on me what you got
Yesterday i wanted to update Sultan's CM ROM on my OPX, so i downloaded it and tried to install it over TWRP what gives me error messages. I made a factory wipe and installed OxygenOS 2.2.3 and then updated my TWRP to Sultan's new one (Version 3.0.2.3). After i flashed the .img, TWRP wasnt booting anymore, it was stuck on the 1+ Screen, but i was able to get to the System. So i get Root access over the SuperSU App and then flashed the TWRP zip over the Rashir App and TWRP worked again, then i flashed the new OxygenOS (3.1.3) what was successful. But now, TWRP wont work again. When i try to boot into recovery, it just show the 1+ Screen and Vibrates for maybe 1 second, but than it skips and boot automatically into System. The SuperSU App says its no SU File installed and can't be installed. Fastboot didnt't work either. When i connect it and type in ADB devices it shows me the ID. But with Fastboot devices nothing happens and im unable to do anything over it. (Drivers are correctly installed, without Signature check by windows etc.)
I know, i probably made some huge mistakes with all that. Do you guys have any solutions to get the Bootloader working again?
Thanks for any helps!
best regards
That recovery was for new BL and you flashed it over Old one.
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Adesh15 said:
That recovery was for new BL and you flashed it over Old one.
Follow this guide http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Click to expand...
Click to collapse
Ok i will do that.
But just to be sure. After ive done this, im updating Oxygen to the newest Version and then install Sultan's newest TWRP and CM ROM?
Like i said, im not a Pro with it and i just dont want to fu** it up again.
Thank you.
Ulman2033 said:
Ok i will do that.
But just to be sure. After ive done this, im updating Oxygen to the newest Version and then install Sultan's newest TWRP and CM ROM?
Like i said, im not a Pro with it and i just dont want to fu** it up again.
Thank you.
Click to expand...
Click to collapse
Yup.
Will work fine.
Hi guys,
Before you say again a topic on a non bricked One Plus X, I would like to let you know that I've checked and try almost all of the tutorial I've seen on xda and one plus forum.
I was on CM14.1 with this ROM : https://forum.xda-developers.com/oneplus-x/orig-development/rom-cyanogenmod-14-onyx-t3452150
Unfortunately, I made the 25-12-2016 update and it totally broke up the phone..
I download the OnePlus X OxygenOS 3.1.4 on the One Plus website. So I flash it on the stock recovery, it tells me "Install success" then I reboot and it stays on the bootlogo.
For information, I can't access the oem unlock menu if needed, but when I ask the oem device info it says unlocked. The phone is detected by the computer sometimes with unknown device and sometimes correctly with the qualcomm drivers..
I have a back up made from TWRP, I can access the device by the fastboot mode, it seems that all the operations written here worked but it doesn't install or even boot on TWRP..
Thanks for your help guys.
Are you using latest TWRP from website think version 3.0.3?
Exodusche said:
Are you using latest TWRP from website think version 3.0.3?
Click to expand...
Click to collapse
I'm not even using TWRP, since I can't boot on it.. But I tried to flash the twrp-3.0.2-2 from blue spark v41, after the installation via Flashboot, it doesn't boot up on the recovery..
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Exodusche said:
So after flashing TWRP you use fastboot boot recovery.img and nothing happens?
Click to expand...
Click to collapse
Exactly, the phone is stuck on the one plus logo..
defqon_1 said:
Exactly, the phone is stuck on the one plus logo..
Click to expand...
Click to collapse
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Divyesh49 said:
If you did not unlocked bootloader properly then also you might face the problem...
to unlock bootloader: https://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
make sure you follow all the step. (If you didn't followed these steps then lock bootloader {fastboot oem lock} and unlock using this mathod, worked for me.)
Falsh this kernal after flashing rom and gapps, https://forum.xda-developers.com/oneplus-x/development/kernel-arsenic-kernel-r2-t3422020
Don't forget to hit :good:
Click to expand...
Click to collapse
Didn't work. I tried to lock and then unlock to be sure but not is stay in false for tempered AND unlocked.
So I don't have any idea on how make android back on my phone.
I just have access to Fastboot mode. No recovery, nothing else..
EDIT : phone is not starting anymore. I try to charge it hoping it just a low battery problem..
You should send it to RMA
Trimis de pe al meu Redmi 3S folosind Tapatalk
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Help Pls
defqon_1 said:
Finally, I resolved the problem I don't know how but for the moment I have stock recovery and stock rom ! :laugh:
I will wait for a stable rom for Nougat. Thanks for the help guys !
PS : how do I close or write resolved at the top of the subject ?
Click to expand...
Click to collapse
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Fix It!
Exodusche said:
Start by seeing if you can fastboot flash stock recovery from any 2.X.X OOS. Then fastboot flash twrp 3.0.2. If your on new bootloader meaning latest ROMs or OOS3 then you need to boot into 3.0.2 and from there you can flash IMG of twrp 3.0.3. Make sure you boot right back into recovery after flashing any twrp or it won't stick. This worked for me when I lost my recovery twice but always remember at your own risk. Not responsible if you make your phone into a paper weight.
Click to expand...
Click to collapse
Done! finally i can reinstall stock rom and recovery with drivers by usb.
UBCM said:
I have the same problem, access to fastboot but no to recovery. How do you resolved it?
Click to expand...
Click to collapse
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Done
defqon_1 said:
I have tried multiple tools that I find on XDA. I put all the zip files like bootloader update and rom on my sdcard. And by a great night, the OOS 3.1.4 finally booted up ! So I don't have a miracle solutions that can help you..
Click to expand...
Click to collapse
Don't worry i have restored my OPX 5 days ago. I used the method of this video: https://youtu.be/R4SVSovw4Jo and files from this thread: https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108 , if it can help someone.
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
I read that Huawei rolled out an update which broke Magisk, does anyone know if the latest update is safe?
How can I tell if an update is safe to use?
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
mtvento said:
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
Click to expand...
Click to collapse
as opposed to version 8.0.0.379?
I currently have magisk and TWRP with no problem, is this problem you describe is new to the latest version?
Do you have a different custom ROM?
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
mtvento said:
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
Click to expand...
Click to collapse
So on EMUI9 there's no option of Root+Custom recovery?
So the options are either root or custom recovery?
Did I understand correctly?
Thank you
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
mtvento said:
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
Click to expand...
Click to collapse
That sucks big time.
What do you mean by "have to boot to recovery each time"? every time I restart the phone or turn it off and back on I must go through recovery?
I think I'll avoid EMUI9 and stick with EMUI8.
For some reason there are not much custom ROMs or honor 9
That is the last time I buy a non root friendly phone like Huawei/Xiaomi
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
buchman said:
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
Click to expand...
Click to collapse
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Clonimus said:
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Click to expand...
Click to collapse
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
buchman said:
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
Click to expand...
Click to collapse
When I do that it gives me 2 options, one is download a zip file (and then I need to install using TWRP, right?)
The other option is patch a boot image, and it lets me look for one. Is this option to patch a downloaded boot image and then I need to flash it? what do I do with this option?
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)
I want to access /data/system/users//settings_ssaid.xml to know what my game unique id is.
But after some research i learned that i have to root to able to get there but i have almost zero knowledge about it.
Are there any guide to root Redmi Note 10 from the scratch? Thanks.
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm on official global ROM 12.5.3.0 RKGMIXM
And i turned on OEM Unlocking in developer mode yesterday (Which is confuse me a little a guide said i have to wait for 7 days for this but mine is nothing it's just switched to on)
OEM Unlocking is only one of the steps, but it does not unlock the bootloader. File a request with Xiaomi.
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
inn0ichi said:
...
i recommend only booting to twrp, not flashing it
...
Click to expand...
Click to collapse
Why do you recommend to only booting to TWRP instead of flashing it?
Pasarireng said:
Why do you recommend to only booting to TWRP instead of flashing it?
Click to expand...
Click to collapse
because the twrp developer instruction is to booting , not flashing
alonsoj636 said:
because the twrp developer instruction is to booting , not flashing
Click to expand...
Click to collapse
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Risk of bootloop
Pasarireng said:
Aside of that instruction, actually is it 'dangerous' if we install the TWRP? What 'bad things' would/may happen if we install it? (Because I see some guides about installing it on RN10, like this one for example, and I was almost followed that guide).
Click to expand...
Click to collapse
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Y
alonsoj636 said:
Risk of bootloop
Risk of bootloop and fastboot loop... because this twrp is modded to be booted and then flashed (you can found the option in advanced)
One time i faced a fastboot loop once i flashed directly the twrp , that's why i recommend booting it first and then , flashing
Click to expand...
Click to collapse
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Pasarireng said:
Y
Yes, I mean that, (booting it first then flashing,.. (the TWRP right?).. I think the guide (which the youtube link I attached above) is also told to do that, right? (Or do I misunderstand this?)
Click to expand...
Click to collapse
Yes , is the correct way
inn0ichi said:
unlock bootloader
i recommend only booting to twrp, not flashing it
flash magisk 23
hide magisk
Click to expand...
Click to collapse
Please confirm these;
*So we can:
Use TWRP only temporarily, only to root the phone (by flashing Magisk v23),
and then,
back to using the stock recovery on our RN10 afterward,
even if the RN10 is already rooted?
**If the answer for my question above is yes, then (in RN10 condition of Unlocked Boot Loader, Rooted, Stock MIUI & Stock Recovery) ;
Would we still get official OTA Update from Xiaomi (and can download and install the update- as how it's like before rooting the phone)?
Thank you in advance
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
StaryMuz said:
It's an unnecessarily complicated procedure. Just flash a modified boot.img for your Miui using fastboot from your PC. If you don't have the ability to modify the boot.img on another rooted phone yourself, request a modified boot.img with the exact update version of your Miui here.
Click to expand...
Click to collapse
Thanks again, (and maybe I will try your suggestion later).. but (sorry)... your reply doesn't answer my questions.
(I think my questions are very clear and probably very easy to be answered by someone who has experience/knowledge about it (like you?).. no?)
Forgive my nooby questions.
But I really want to know as much as I can (especially about the answer for some questions I have inside my head about the matter, like I asked above),.. before executing doing something about my phone.
oops... I'm sorry for double send
In the past I rooted Miui and then continued to get OTA updates. However, this cannot be confirmed for all versions of Miui. Each new update changes the phone software and so what worked before may not work today.
alonsoj636 said:
1- Boot into Custom Recovery
2- Flash Magisk ZIP
3- Install Magisk APK
Done
if you want detailed steps , please tell me on wich ROM you are and if you have your bootloader unlocked
Click to expand...
Click to collapse
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
First of all, I would like to point out that Magisk (root) is a security risk. Without understanding the issues, the phone is more easily exploitable.
To install, just download the magisk file with the ZIP extension. In recovery, select the install option and select this file. Once installed, exit recovery and boot the system. Once the system boots, use magisk and complete the installation it requests.
Lolitary said:
Hi, I'm unlocked my phone and installed the orange fox it's the custom recovery right? Because it say so.
If yes, By Flash Magisk ZIP how to do that? Please explain the detailed steps, Thanks.
Click to expand...
Click to collapse
the answer above is right ... but i would suggest to flash Orange Fox zip and then Magisk zip... to avoid problems
isn't there decrypt.zip for RN10?
How to decrypt this phone?
I usually did that along with rooting with my android phones before this.
Edit:
Update:
It's ok now I understand how, after watching this video.