Related
Ok , So I finally was able to unlock my bootloader after getting that 50 % error, I thought that I'd flash miui 8 , so I downloaded the rom from official mi website and flashed it with twrp but for some reason I got stuck in a bootloop. I dont want to download fastboot rom as it takes a lot of time due to slow internet, so could anyone tell me how can i successfully flash a rom from twrp. I've got bot miui 8 chinese developer rom and global beta rom downloaded.
You need patched boot for normal twrp or u must use cofface twrp to flash the rom.
You cant flash stock rom via twrp without patched boot.img
And if you are flashing marshmallow rom u must know that the bootloader will lock itself again.
Why not just flash the miui.eu version? No boot image mess..
s-u-f-f-e-r said:
You need patched boot for normal twrp or u must use cofface twrp to flash the rom.
You cant flash stock rom via twrp without patched boot.img
And if you are flashing marshmallow rom u must know that the bootloader will lock itself again.
Click to expand...
Click to collapse
Edit : The recovery worked. Thanx.
where can I find a patched boot.img for latest chinese developer rom.Thanx for the fast reply.
Just use cofface recovery for stock roms:
http://forum.xda-developers.com/redmi-note-3/development/recovery-kenzotwrp-cafface-3-0-0-t3369341
I think that the Alca recovery do the same, but I haven't test it yet
s-u-f-f-e-r said:
Just use cofface recovery for stock roms:
http://forum.xda-developers.com/redmi-note-3/development/recovery-kenzotwrp-cafface-3-0-0-t3369341
I think that the Alca recovery do the same, but I haven't test it yet
Click to expand...
Click to collapse
Thanks. Problem solved.
All is in the title. My bootloader is officialy unlocked but I can't find a way to install a custom recovery and to root the last Marshmallow Beta rom. Any help?
ybregeon2016 said:
All is in the title. My bootloader is officialy unlocked but I can't find a way to install a custom recovery and to root the last Marshmallow Beta rom. Any help?
Click to expand...
Click to collapse
If you flash the fastboot rom with miflash , you can do everything like before. Otherwise, this is the guide-
http://en.miui.com/thread-344450-1-1.html
@ybregeon2016 were you successful on rooting and twrp? What method did uou use and which twrp did you install? Thr number of different versions and the overly complicated methods are too confusing...
Thanks in advance
@candiesdoodle
Flashing miui8 6.9.9 MM relocked my bootloader,so i suggest to check whether your bootloader got relocked again or not.
If its locked unlock it via mi unlock tool.
I am using alka twrp , and rooted my rom by flashing supersu zip from twrp.
To install twrp i used fastboot commands.
hello,
my current situation: i am on oos 2.2.3, not rooted, twrp 3.0.1-0 running.
i want to install a 3.x.x oos, version, i wanted to install 3.1.2 first, cause oneplus site i can install that directly form 2.2.3 (no such info on 3.1.3 and 3.1.4)
when i try to install with twrp, it says "this package is for "Oneplus" devices, this is a "ONE"
i think i am using the wrong twrp version. tried to install the newest (3.0.3-0), but this one doenst work, can not boot into it.
please help
Best is to fastboot flash old OOS 2 recovery
Then, with it, flash the 2.2.3. Reboot. then Flash 3.1.4. with the recovery
First you need to flash official oxygen os recovery for android 5.1 lollipop https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img Now you will be able to boot the phone. Now download and copy oxygen os 3.1.4 to internal memory http://downloads.oneplus.net/devices/oneplus-x/ Reboot into recovery and flash the rom.
Aftrr successful flash of oos3 boot into fastboot and flash latest twrp from twrp website.. This time it should work.
thanks, it work with the costum recovery.
on 3.1.4 i installed a slightly older twrp form sparkfire (3.0.2 i think), rooting and installing xposed worked fine though.
is it important to have the latest twrp?
and another question. at some point in my hours long struggel with updating my opx i softbricked it. i guess my bootloader was locked and i tried to install another recovery. i expected it to be still unlocked from my first rooting months ago. when does the bootloader lock?
dooglrig said:
thanks, it work with the costum recovery.
on 3.1.4 i installed a slightly older twrp form sparkfire (3.0.2 i think), rooting and installing xposed worked fine though.
is it important to have the latest twrp?
and another question. at some point in my hours long struggel with updating my opx i softbricked it. i guess my bootloader was locked and i tried to install another recovery. i expected it to be still unlocked from my first rooting months ago. when does the bootloader lock?
Click to expand...
Click to collapse
It is always recommended to use latest (bugs free)
You can use this one https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img latest as of now. And no u didn't brick ur phone. U flashed a new twrp for old bootloader version. Thts y u got stuck with oneplus logo. Its all oneplus things. Its always preferred to use stock recovery for updating bootloader which is safe. Check your bootloader state by giving this cmds "fastboot oem device-info"
cva_kabil said:
It is always recommended to use latest (bugs free)
You can use this one https://dl.twrp.me/onyx/twrp-3.0.3-0-onyx.img latest as of now. And no u didn't brick ur phone. U flashed a new twrp for old bootloader version. Thts y u got stuck with oneplus logo. Its all oneplus things. Its always preferred to use stock recovery for updating bootloader which is safe. Check your bootloader state by giving this cmds "fastboot oem device-info"
Click to expand...
Click to collapse
Hmm isnt that for new BL as well ?
NielDK said:
Hmm isnt that for new BL as well ?
Click to expand...
Click to collapse
Yes it is. OP said that he's on OOS 3.1.3, so already on the new BL.
Bought phone in summer 2016, OFFICIALLY unlocked Lollipop (?) bootloader (though not sure if I relocked and unofficially unlocked it since then, most likely not and still using officially unlocked bootloader from 2016, since this was backup phone) with officially supplied MIUI, now years later and many more ROMs I don't remember what's exact state of firmware or bootloader unlock if it's official or unofficial.
I am running this according system:
Nitrogen build kenzo-8.1.0-OPM5.171019.019
android security patch level april 1, 2018
baseband 976_GEN_PACK-1.103654.1.105572.1
kernel 3.10.108 (gcc version 4.9.x 20150123 (prerelease) (GCC) [email protected] #1 Apr 3 2018
SELinux permissive
Redwolf recovery 3.2.1 build 24
What are my options to upgrade to some Pie ROM like Nitrogen or RR? I just remember that at some point Nitrogen OS must switched tree, firmware or something and newer builds end up with bootloops so I am stuck on that April 2018 build. How would I proceed to install some of those Pie ROMs? I guess they require some newer bootloader/firmware. I don't want definitely relock and unlock bootloader and deal with MiFlash, I remember it's major PITA.
PeterMarkoff said:
Bought phone in summer 2016, OFFICIALLY unlocked Lollipop (?) bootloader (though not sure if I relocked and unofficially unlocked it since then, most likely not and still using officially unlocked bootloader from 2016, since this was backup phone) with officially supplied MIUI, now years later and many more ROMs I don't remember what's exact state of firmware or bootloader unlock if it's official or unofficial.
I am running this according system:
Nitrogen build kenzo-8.1.0-OPM5.171019.019
android security patch level april 1, 2018
baseband 976_GEN_PACK-1.103654.1.105572.1
kernel 3.10.108 (gcc version 4.9.x 20150123 (prerelease) (GCC) [email protected] #1 Apr 3 2018
SELinux permissive
Redwolf recovery 3.2.1 build 24
What are my options to upgrade to some Pie ROM like Nitrogen or RR? I just remember that at some point Nitrogen OS must switched tree, firmware or something and newer builds end up with bootloops so I am stuck on that April 2018 build. How would I proceed to install some of those Pie ROMs? I guess they require some newer bootloader/firmware. I don't want definitely relock and unlock bootloader and deal with MiFlash, I remember it's major PITA.
Click to expand...
Click to collapse
U need latest bootloader to boot pie roms.
Lollipop bootloader wont work.
So if u r official unlock then u need firmware to update bootloader.
If u r unofficial unlock then flash latest fastboot rom to update bootloader.
Black_Stark said:
U need latest bootloader to boot pie roms.
Lollipop bootloader wont work.
So if u r official unlock then u need firmware to update bootloader.
If u r unofficial unlock then flash latest fastboot rom to update bootloader.
Click to expand...
Click to collapse
so if i am officially unlocked i could just flash firmware file through TWRP and then flash new Pie ROM without ending relocking bootlader or bricking device?
PeterMarkoff said:
so if i am officially unlocked i could just flash firmware file through TWRP and then flash new Pie ROM without ending relocking bootlader or bricking device?
Click to expand...
Click to collapse
Yes.
Official unlocking got advantages. U can update ur all critical partitions just by flashing firmware zip in twrp.
If u official unlocked then U can update ur bootloader by flashing 10.2 firmware zip which contains emmc appboot file.
This emmc file will update ur bootloader.
But if u r unofficially unlocked and if u try to attempt to flash same firmware which has emmc appboot file then it will brick or bootloop ur device. It will relock ur bootloader and erase ur twrp.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
So flash latest fastboot rom if u unofficial unlocked.
For kenzo
http://bigota.d.miui.com/V10.2.1.0....XM_20190114.0000.00_6.0_global_8a48e54fe3.tgz
Or if u official unlocked
Then flash this firmware for kenzo using twrp
https://mirrors.tuna.tsinghua.edu.c...roGlobal_V10.2.1.0.MHOMIXM_36c0f5ded3_6.0.zip
thanks a lot for help
so if I have officially unlocked Lollipop bootloader, I can still flash new firmware over such old bootloader/firmware? I've found some file in PC, it seem I flashed this firmware most recently - "miui_HMNote3ProGlobal_7.12.21_Firmware" (though not completely sure about it)
So in worst case if I could accidentally flash new firmware over unofficially unlocked bootloader I just need to flash latest fastboot ROM through miflash/fastboot and end up with regular locked bootloader with MIUI and stock recovery? I mean it is not that big deal compared to hard bricking device
will try then just new firmware, hopefully I remember correctly I didn't mess with BL in those years and it is still officially unlocked
btw. can I still flash it with that old red wolf recovery? btw. it's 2GB/16GB configuration if it makes any difference because the recovery file was named "RedWolf-024-kenzo-2GB_RAM" so not sure if there is some difference in recovery between 2GB and 3GB version
PeterMarkoff said:
thanks a lot for help
so if I have officially unlocked Lollipop bootloader, I can still flash new firmware over such old bootloader/firmware? I've found some file in PC, it seem I flashed this firmware most recently - "miui_HMNote3ProGlobal_7.12.21_Firmware" (though not completely sure about it)
So in worst case if I could accidentally flash new firmware over unofficially unlocked bootloader I just need to flash latest fastboot ROM through miflash/fastboot and end up with regular locked bootloader with MIUI and stock recovery? I mean it is not that big deal compared to hard bricking device
will try then just new firmware, hopefully I remember correctly I didn't mess with BL in those years and it is still officially unlocked
btw. can I still flash it with that old red wolf recovery? btw. it's 2GB/16GB configuration if it makes any difference because the recovery file was named "RedWolf-024-kenzo-2GB_RAM" so not sure if there is some difference in recovery between 2GB and 3GB version
Click to expand...
Click to collapse
Use official twrp. 3.2.3
Redwolf recovery has some serious lockscreen bug with unofficial bootloader.
Black_Stark said:
Use official twrp. 3.2.3
Redwolf recovery has some serious lockscreen bug with unofficial bootloader.
Click to expand...
Click to collapse
so I successfully flash TWRP 3.2.3, no problem to get inside there, then I flashed from there your recommended firmware (seemed successful in TWRP) but then wehn restarted phone won't boot or get into recovery, if i press power button or power button + vol UP, I just see boot logo for half second and then it will switch off, no problem to get into fastboot where I can see the device
so does it mean there was some problem with bootloader and now it is relocked with wiped TWRP and I have to flash that official fastboot ROM?
EDIT: so i guess bootloader is locked and it is back to MIUI via Miflash, right?
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
OKAY [ 0.016s]
finished. total time: 0.016s
Click to expand...
Click to collapse
or could I flash fastboot rom without miflash just with ADB/fastboot?
PeterMarkoff said:
so I successfully flash TWRP 3.2.3, no problem to get inside there, then I flashed from there your recommended firmware (seemed successful in TWRP) but then wehn restarted phone won't boot or get into recovery, if i press power button or power button + vol UP, I just see boot logo for half second and then it will switch off, no problem to get into fastboot where I can see the device
so does it mean there was some problem with bootloader and now it is relocked with wiped TWRP and I have to flash that official fastboot ROM?
Click to expand...
Click to collapse
That means u have unofficially unlocked ur phone.
Aint u paying attention to my last post ? :laugh:
So what I did in the end:
1. Installed MiFlash and then through EDL flashed ZCX TWRP from this thread over my relocked old NOS with new firmware
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778
2. took this FW which relocked me before and took away emmc plus modified script and flash it again through ZCX
https://mirrors.tuna.tsinghua.edu.c...roGlobal_V10.2.1.0.MHOMIXM_36c0f5ded3_6.0.zip
3. flash newest Nitrogen OS Pie, where I removed device check from script, since it was giving me error 7 that my device ain't kenzo but "." from here
https://forum.xda-developers.com/redmi-note-3/development/rom-nitrogen-os-beta-t3864016
and to my surprise it booted after like 2-3 minutes
PeterMarkoff said:
So what I did in the end:
1. Installed MiFlash and then through EDL flashed ZCX TWRP from this thread over my relocked old NOS with new firmware
https://forum.xda-developers.com/redmi-note-3/how-to/unlock-unofficially-install-zcx-twrp-t3586778
2. took this FW which relocked me before and took away emmc plus modified script and flash it again through ZCX
https://mirrors.tuna.tsinghua.edu.c...roGlobal_V10.2.1.0.MHOMIXM_36c0f5ded3_6.0.zip
3. flash newest Nitrogen OS Pie, where I removed device check from script, since it was giving me error 7 that my device ain't kenzo but "." from here
https://forum.xda-developers.com/redmi-note-3/development/rom-nitrogen-os-beta-t3864016
and to my surprise it booted after like 2-3 minutes
Click to expand...
Click to collapse
Update recovery to latest official 3.2.3.
Black_Stark said:
Update recovery to latest official 3.2.3.
Click to expand...
Click to collapse
won't it cause bootloop if flash over zcx twrp? also same with root, can I normally flash magisk?
PeterMarkoff said:
won't it cause bootloop if flash over zcx twrp? also same with root, can I normally flash magisk?
Click to expand...
Click to collapse
No bootloop. Just flash it and reboot to new recovery.
Bootloop will happens if u flash miui firnware.
Format data
Factory reset
Flash rom
Flash gapps
Flash 18.1 magisk.
Reboot
Black_Stark said:
No bootloop. Just flash it and reboot to new recovery.
Bootloop will happens if u flash miui firnware.
Format data
Factory reset
Flash rom
Flash gapps
Flash 18.1 magisk.
Reboot
Click to expand...
Click to collapse
can't flash on locked bootloader
Code:
target reported max download size of 536870912 bytes
sending 'recovery' (18580 KB)...
OKAY [ 0.594s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.609s
I just have ZCX recovery with locked bootloader and running Nitrogen Pie on top of that with new firmware you linked, I mean I don't care about future ROM updates (though I guess removing device check from update will solve this), I am fine sitting on this, but would like to have root, though I guess impossible with locked bootloader
PeterMarkoff said:
can't flash on locked bootloader
I just have ZCX recovery with locked bootloader and running Nitrogen Pie on top of that with new firmware you linked, I mean I don't care about future ROM updates, I am fine sitting on this, but would like to have root, though I guess impossible with locked bootloader
Click to expand...
Click to collapse
Lmao.
U need to Flash it using current recovery.
Black_Stark said:
Lmao.
U need to Flash it using current recovery.
Click to expand...
Click to collapse
you mean magisk or TWRP? if I flash magisk won't I end up with bootloop, can I flash newest one or need to use some older version?
PeterMarkoff said:
you mean magisk or TWRP? if I flash magisk won't I end up with bootloop, can I flash newest one or need to use some older version?
Click to expand...
Click to collapse
Join me and chat
https://t.me/Black_Stark
Black_Stark said:
Join me and chat
https://t.me/Black_Stark
Click to expand...
Click to collapse
don't have telegram, only signal and whatsapp
PeterMarkoff said:
don't have telegram, only signal and whatsapp
Click to expand...
Click to collapse
Use playstore to install . or u can use desktop telegram app.
Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q?
visit: h t t p s : / / twrp.me/site/update/2019/10/23/twrp-and-android-10.html
As, if now you cannot. For Android Q, it's still in research.
------------------------------------------------------------------------
Never tried but: ClockworkMod Recovery – a past alternative to TWRP custom recovery.
h t t p s : / / en.wikipedia.org/wiki/ClockworkMod#ClockworkMod_Recovery
Research over it & let me know if anything worked for you-!
I successfully roote Q with this ?
https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389
I just flash TWRP, format and flash custom rom. Rooted.
First of all. What device do you have and what exactly have you tried? Include references.
Remember first step is to search before asking.
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
StonebridgeGr said:
Guys need to re root my device on android 10 cuz i had it root under android 9 and cannot use s health
Need to root to chanfe the build prop command to use s health
Also missing the heart monitor pressure
Please help me
G965f
Click to expand...
Click to collapse
I would recommend you flashing custom firmware, like the one in my signature. Everything is working, including Security Folder.
Rooting S9 +
sarjarim said:
I just flash TWRP, format and flash custom rom. Rooted.
Click to expand...
Click to collapse
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
xectis said:
Which TWRP version you used and how did you install TWRP on a non-rooted phone? Do you not have to use Magisk to root the phone first?
Click to expand...
Click to collapse
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
sarjarim said:
I just used the 3.3.1.1 from the TWRP site.
Flash TWRP is to root, so I did it b4 root.
1. OEM unlock
2. Flash TWRP with odin then boot to TWRP, samsung will restore if u normal boot.
3. Backup EFS
4. Format data wipe all
5. Dm verity, search newest from dr ketan
6. Flash custom ROM.
Magisk usually comes with the custom ROM.
Click to expand...
Click to collapse
Magic! Thanks bro.
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
hi im new to this but what do you mean by Q??
i have sprint s9+ sm-g965u1, can i root my phone now ?
Devilix said:
For Android 10 U9 bootloader, is not more possible flash custom binaries... even twrp!
G965FXXU9ETF5
Click to expand...
Click to collapse
This isn't true I flashed Twrp 3.5.091 via Odin, S9+ exynos android 10, then flashed Magisk 21.4.
When I got phone it was android 10 June 2020 security update. It then updated again to 21/02/2021 ota.. I was able to flash recovery twrp and root/debloat. Only problem I did find is that I cannot flash lineage 18.1 or any custom roms.
Regards
JeyKul said:
Hello, I updated to Q and can't get it rooted.
It bootlooped.
How can I root Android Q? No root method root android Q.
Click to expand...
Click to collapse
hey ,
1.install magisk manager on your phone
2.download the firmware from samfirmware for your model of phone to pc
3.download 7zip with lz4
4. use 7zip lz4 to extract boot img from AP(firmware)
5. send the xtracted boot.img to phone sdcard and use magisk manager to patch said image .
6. send the patched img to pc and use 7zip to create archive as boot.tar file
7. one you install the firmware as normal via odin (disable auto reboot ) go back and disconnect/reconnect usb from phone so it appears as added in odin once more.
8. add the boot.tar file to AP in odin and flash the phone , reboot system and install magisk manager again , go into magisk and it will reboot again to fix the root.
there is a video somwhere on youtube showing you better than ive tried to here.
this is by far he best way as you can still take ota updates because stock recovery is still present .
regards