Updated from OOS 3.1.3 to 3.1.4 from the OTA Update App that's built in in OOS 3.1.3. Hit install from the app itself. Succesful boot to 3.1.4 but TWRP BluSpark seems to have disappeared and I'm unable to flash it back. Hence I cant root the phone. Please help. Need to root urgently. Thanks in advance.
EDIT: fixed by erasing the recovery partition and then flashing TWRP BSv41 through bootloader.
Same Problem
TWRP gets flashed but does not boot. Please Help. Thank you.
rishveed_s said:
TWRP gets flashed but does not boot. Please Help. Thank you.
Click to expand...
Click to collapse
Dont worry.
http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
Make sure you have the latest build from above link in your fastboot folder on you computer and rename it to twrp.img and simply follow the below steps:
1) Reboot device to bootloader.
2) type in ' fastboot erase recovery ' and hit enter. This will wipe the recovery partition.
3) type in ' fastboot flash recovery twrp.img ' This will flash the new TWRP recovery into the boot partition.
4) (optional) type in ' fastboot boot twrp.img ' to directly boot into recovery.
[email protected]!C said:
Dont worry.
http://forum.xda-developers.com/oneplus-x/development/unofficial-twrp-3-0-2-0-recovery-onyx-t3471584
Make sure you have the latest build from above link in your fastboot folder on you computer and rename it to twrp.img and simply follow the below steps:
1) Reboot device to bootloader.
2) type in ' fastboot erase recovery ' and hit enter. This will wipe the recovery partition.
3) type in ' fastboot flash recovery twrp.img ' This will flash the new TWRP recovery into the boot partition.
4) (optional) type in ' fastboot boot twrp.img ' to directly boot into recovery.
Click to expand...
Click to collapse
after this I installed this, phone stuck on bootlogo.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page3
Plz help
Hi,
i wasn't able to flash TWRP after i update my phone to 3.1.4. Dunno if it's november security patch or something else. So i just downgraded to 3.1.3 and it works. Hope it can help someone
Nishblueweapon said:
after this I installed this, phone stuck on bootlogo.
http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/page3
Plz help
Click to expand...
Click to collapse
You're supposed to flash Super SU systemless. Attaching the File below. Flash it with the TWRP.
i also got the same problem latest verison of twrp recovery didn't flashed. It always show remote dtb not found.
lokking for a solution
aa_vi said:
i also got the same problem latest verison of twrp recovery didn't flashed. It always show remote dtb not found.
lokking for a solution
Click to expand...
Click to collapse
You could always dirty flash 3.1.3, get twrp installed then install 3.1.4 from twrp. Just please do a complete backup first.
[email protected]!C said:
You're supposed to flash Super SU systemless. Attaching the File below. Flash it with the TWRP.
Click to expand...
Click to collapse
Yes, figured it.
Got working xposed fw for 3.1.4?
Nishblueweapon said:
Yes, figured it.
Got working xposed fw for 3.1.4?
Click to expand...
Click to collapse
Here :
http://dl-xda.xposed.info/framework/sdk23/arm/xposed-v87-sdk23-arm-test1.zip
@keno I think this is the test build. Few ppl got bootloop on this one. Have u tried this one? Unable to quote on xda. Problems with lab.
Related
hey guy i have a big problem with my redmi 3, i unlocked the bootloader and then flashed twrp recovery, but it don't work properly, during the operation of flashing rom or nandroidbackup it reboot always, i've tried to reflash the recovery via adb and fastboot but the problem is not solved, can you help me?thank you sorry for bad english
SOLVED:i downgraded to 7.1.3 version via fastboot and then flash cofface version of twrp
robonudo said:
hey guy i have a big problem with my redmi 3, i unlocked the bootloader and then flashed twrp recovery, but it don't work properly, during the operation of flashing rom or nandroidbackup it reboot always, i've tried to reflash the recovery via adb and fastboot but the problem is not solved, can you help me?thank you sorry for bad english
Click to expand...
Click to collapse
No one has a solution? Advance some idea of problem if you want
robonudo said:
No one has a solution? Advance some idea of problem if you want
Click to expand...
Click to collapse
for me, you only have flash incorrect version of twrp.
i have got same problem.. then i have change twrp version (download coffage twrp) and i have solve it..
only one problem i have now: i must boot coffage twrp from pc.
Kayl88 said:
for me, you only have flash incorrect version of twrp.
i have got same problem.. then i have change twrp version (download coffage twrp) and i have solve it..
only one problem i have now: i must boot coffage twrp from pc.
Click to expand...
Click to collapse
Thank you for the help, but I tried such as 4 type of twrp but the result was the same, can you send me a PM with link of the version that work for you? For your problem has you press volume + and - power button for several second?
Kayl88 said:
for me, you only have flash incorrect version of twrp.
i have got same problem.. then i have change twrp version (download coffage twrp) and i have solve it..
only one problem i have now: i must boot coffage twrp from pc.
Click to expand...
Click to collapse
have you tried booting your phone with vol up + vol down + power buttons?
robonudo said:
Thank you for the help, but I tried such as 4 type of twrp but the result was the same, can you send me a PM with link of the version that work for you? For your problem has you press volume + and - power button for several second?
Click to expand...
Click to collapse
i'm back. in a minute i contact you via pm.
usblaidas said:
have you tried booting your phone with vol up + vol down + power buttons?
Click to expand...
Click to collapse
the problem is not enter into recovery.
the first time i have flash wrong twrp. when i enter in recovery, by hardware procedure, in the bottom of screen i read version of twrp.. and is version twrp 3.0.0r2. this is a wrong version!
then.. i do flash from pc, flash operation success.. and ONLY with command "fastboot boot XXXXX.img" , where xxxx.img is name of recovery i have flash before, i can enter in correct twrp.
i don't know why, but i think i can't flash and fix the correct version of twrp. bhooooooooooo!
edit:
problem solved..
i have rename twrp img file in "recovery.img" and i have flash it in fastboot mode by pc..
i have try to enter in recovery with adbo command (adb reboot recovery) and phone reboot in correct twrp version;
then i have try to enter in recovery with hardware procedure (poweroff, volume up + power and release power when appear Mi logo, tap on "recovery") and it work;
and, in the end, i have try to nter in recovery mode by app "updater"
all works perfectly now!
Kayl88 said:
i'm back. in a minute i contact you via pm.
the problem is not enter into recovery.
the first time i have flash wrong twrp. when i enter in recovery, by hardware procedure, in the bottom of screen i read version of twrp.. and is version twrp 3.0.0r2. this is a wrong version!
then.. i do flash from pc, flash operation success.. and ONLY with command "fastboot boot XXXXX.img" , where xxxx.img is name of recovery i have flash before, i can enter in correct twrp.
i don't know why, but i think i can't flash and fix the correct version of twrp. bhooooooooooo!
edit:
problem solved..
i have rename twrp img file in "recovery.img" and i have flash it in fastboot mode by pc..
i have try to enter in recovery with adbo command (adb reboot recovery) and phone reboot in correct twrp version;
then i have try to enter in recovery with hardware procedure (poweroff, volume up + power and release power when appear Mi logo, tap on "recovery") and it work;
and, in the end, i have try to nter in recovery mode by app "updater"
all works perfectly now!
Click to expand...
Click to collapse
Hi,, i've successfully unlocked my redmi 3 bootloader, and now there's root permission option in security app. I tapped it and confirmation prompt to get root acces appear, i click ok, then my device download something (my assume its root file), and reboot by it self after. Now i have rooted redmi 3 with unlocked bootloader but no superSU installed.
I want to install twrp recovery which is official now for redmi 3, i've read about dm-verity thing in our redmi 3 and still confused about it.
Can i just install twrp recovery thru twrp manager app from play store? If yes, can i go into twrp recovery via updater app.?
Thanks in advance.
you can install twrp by fastboot!
and then yes, you can enter in twrp by updater app
bucks_26 said:
Hi,, i've successfully unlocked my redmi 3 bootloader, and now there's root permission option in security app. I tapped it and confirmation prompt to get root acces appear, i click ok, then my device download something (my assume its root file), and reboot by it self after. Now i have rooted redmi 3 with unlocked bootloader but no superSU installed.
I want to install twrp recovery which is official now for redmi 3, i've read about dm-verity thing in our redmi 3 and still confused about it.
Can i just install twrp recovery thru twrp manager app from play store? If yes, can i go into twrp recovery via updater app.?
Thanks in advance.
Click to expand...
Click to collapse
Congratulations you just followed the official method of getting root access successfully, root access is not from SuperSU but from MIUI itself, it's in the Security app.
You can, but the phone won't boot anymore then, because of the dm-verity thingy. So in another word, you have to disable it by flashing a modified boot image, I'm not sure but some custom ROM might have come with the modified image already, but MIUI ROM definitely doesn't, it is certain you'd get a boot loop after flashed TWRP and try to boot into Android again. That's the simple explanation. And yes you can go to TWRP from updater app, it's the same thing as writing 'reboot recovery'.
Dikirim dari Redmi 3 saya menggunakan Tapatalk
i tried to root my oneplus x ,even after flashing the twrp recovery it is still loading to stock recovery.
Is there a way to boot to twrp recovery ??
I suspect your bootloader is locked. Thats why.
Exoplain what you are doing exactly :
Bootloader state? Which rom, version, version of TWRP. ?.How do you flash?
I suspect the TWRP BS V41 special OOS3 . After fastboot flash, you need to reboot with hardware button directly to Recovery. If not, recovery is overwritten on the first boot.
krischya said:
i tried to root my oneplus x ,even after flashing the twrp recovery it is still loading to stock recovery.
Is there a way to boot to twrp recovery ??
Click to expand...
Click to collapse
Go to fastboot mode flash twrp recovery using thiz cmd "fastboot flash recovery recovery.img" then enter "fastboot boot recovery.img". After flasing boot to it directly which ll overwrite ur stock recovery... Recovery.img is ur twrp recovery img file name
cva_kabil said:
Go to fastboot mode flash twrp recovery using thiz cmd "fastboot flash recovery recovery.img" then enter "fastboot boot recovery.img". After flasing boot to it directly which ll overwrite ur stock recovery... Recovery.img is ur twrp recovery img file name
Click to expand...
Click to collapse
There is error "failed <remote: dtb not found>"
I am using - OOS 3.1.3
-Android 6.0.1
-twrp-3.0.2-0-onyx
Suggest me any custom recovery that is working
krischya said:
There is error "failed <remote: dtb not found>"
I am using - OOS 3.1.3
-Android 6.0.1
-twrp-3.0.2-0-onyx
Suggest me any custom recovery that is working
Click to expand...
Click to collapse
Use this recovery
twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img from the following link
http://forum.xda-developers.com/devdb/project/dl/?id=20236
cva_kabil said:
Use this recovery
twrp-3.0.2-2_blu_spark.v41-onyx_by-engstk.img from the following link
http://forum.xda-developers.com/devdb/project/dl/?id=20236
Click to expand...
Click to collapse
It's working
krischya said:
It's working
Click to expand...
Click to collapse
Good to hear :fingers-crossed::good:
I try to install .img file in recovery, but after install this, my phone shutdown in software brick....
AyalaE96 said:
I try to install .img file in recovery, but after install this, my phone shutdown in software brick....
Click to expand...
Click to collapse
Don't use install img option on twrp it may not work always
Instead of that you can flash recovery using fastboot with "fastboot flash recovery (the name of recovery).img) command
raminta said:
Don't use install img option on twrp it may not work always
Instead of that you can flash recovery using fastboot with "fastboot flash recovery (the name of recovery).img) command
Click to expand...
Click to collapse
I tried, and it didnt work...
AyalaE96 said:
I tried, and it didnt work...
Click to expand...
Click to collapse
Do you have unlocked bootloader???
raminta said:
Do you have unlocked bootloader???
Click to expand...
Click to collapse
yep
raminta said:
Do you have unlocked bootloader???
Click to expand...
Click to collapse
I solved it, I first must install Repack boot with "fastboot flash boot ...img"
After install recovery with "Fastboot flash recovery ...img"
My error Because I should read this first...
Dees_Troy said:
Note that the Z2, like most other Sony devices does not have a proper bootable recovery. As such you have to install a kernel that includes a recovery with it. For a time I will try to continue to supply updated stock kernels repacked with TWRP in them. If you are running one of my kernels or have a custom ROM like OmniROM installed, you can install TWRP in the FOTAKernel partition to stay on the latest version of TWRP.
Device page on our website
Mirror 1
Mirror 2
To install a stock kernel, boot the device into fastboot mode and then from your computer: fastboot flash boot path/to/filename.img
Click to expand...
Click to collapse
However is it true? With latest updates there was bootloader update which brings (or at least should as Sony said) /recovery partition (or more gives access to it, coz partitions was probably always there).
However how it exactly works? I always thought that onee flashed update with newest bootloader will leave new bootloader and this partition forever. But I got Z2 with .291, downgraded it to 4.4.2 for Root and TA backup and than tried to flash recovery to recovery partition, but got error: FAILED (data transfer failure (Unknown error)).
Does it mean that only on latest update(s) there is possibility to use this partition?
Never tried it on my ZU before. I just started form latest 5.1.1.
EDIT: OK, so what i assumed was right - on 6.0.1 I was able to flash the recovery to it's partition.
Now the problem is with booting into it. How? With Power + Vol- it still stright to boots to OS...
EDIT2: adb reboot recovery boots to different bootloader screen (Power+Vol- gives SONY screen and adb gives SONY + XPERIA screen.
However it still boots strght to Android...
Any idea what I'm doing wrong? I have 23.5.A.1.291 + unlocked bootloader + TWRP 3.0.2-0 (official) flashed with fastboot flash recovery img.
I'm 100% sure that SONY screen (w/o XPERIA) is the right one as I have identical one on my ZU when booting into bootloader-recovery mode. But why here it don't boot TWRP, but OS?
HELPPPP
Pleaseeeee tell me how did you flash twrp 3.0? I have tried almost everything it now seems impossible for me... Pleaseee helpp me T_T ... Thankk youuu
Hello,
some weeks ago I installed LinegeOS on my Redmi Note 4. I unlocked bootloader and tried flash TWRB but when i reboot my phone to recovery, MI recovery appear. So I somewhere in XDA found that it is normal and I must boot to recovery via terminal using fastboot. So I booted to recovery using this command
Code:
fastboot boot twrp.img
and flashed LineageOS.
Now when I open Settings->Updates (or something like this) and click on Install updates, it just prepare updates, reboot (probably try reboot to recovery) and nothing happen. I found that I can update it manually but I cannot found downloaded updates in my phone and also I am worried that I loose all my data using this way.
So my question is: How can I update my phone without resetting and loosing all data? My current version of LineageOS is 14.01-NIGHTLY. I have Redmi note 4 global version, Snapdragon.
Just go to lineage official downloads site and dwnld latest nightly and then flash manually ...i think open recovery script that alloow automatic flash isn't stable ...so do it manually ....
try erasing the recovery and reflash it.
fastboot erase recovery
fastboot flash recovery recovery(choosen by you or redwolf).img
fastboot erase cache
fastboot reboot
Sectorian said:
try erasing the recovery and reflash it.
fastboot erase recovery
fastboot flash recovery recovery(choosen by you or redwolf).img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I have done it but now I got Error 7 when I try to flash update.
Thanks for reply!
achjaj said:
I have done it but now I got Error 7 when I try to flash update.
Thanks for reply!
Click to expand...
Click to collapse
Update your TWRP (3.2.1.0) and update your firmware. There's a thread with different firmwares in the development section
Noter2017 said:
Update your TWRP (3.2.1.0) and update your firmware. There's a thread with different firmwares in the development section
Click to expand...
Click to collapse
I updated TWRP and flashed firmware from: https://forum.xda-developers.com/redmi-note-4/xiaomi-redmi-note-4-snapdragon-roms-kernels-recoveries--other-development/firmware-firmwares-mido-global-beta-t3746333(stable global) but I still got error 7.
achjaj said:
I updated TWRP and flashed firmware from: https://forum.xda-developers.com/redmi-note-4/xiaomi-redmi-note-4-snapdragon-roms-kernels-recoveries--other-development/firmware-firmwares-mido-global-beta-t3746333(stable global) but I still got error 7.
Click to expand...
Click to collapse
Use redwolf recovery.
achjaj said:
I updated TWRP and flashed firmware from: https://forum.xda-developers.com/re...re-firmwares-mido-global-beta-t3746333(stable global) but I still got error 7.
Click to expand...
Click to collapse
Please share the file names of your ROM zip file and TWRP .img file.
I have a problem that i never make it into recovery again. I am used to adb/fastboot, this is my 5th device and i happily used different custom roms as lineage, havoc, crdroid for about 7 years and thus am familiar with the concepts of a/b, recovery, adb/fastboot and so on.
Now, when i "flash_all" with stock from here (V10.3.17.0.PFQEUXM) on my a3, i suppose both slots a and b are overwritten with stock. interestingly this stock rom only boots in a-slot, not in b-slot.
when i now just "fastboot flash recovery twrp...." with 3.3.1.2 and hit the manual enter to recovery (power + vol up), i just get a "no command" error - no twrp in sight.
i also tried this with flash_all V11.0.2.0.QFQEUXM rom (a10) and fastboot flash recovery twrp 3.3.1-17 Q from mauronofrio - same result.
anyone knows what i did wrong?
basically i didnt enter team win recovery for some good amount of tries which slightly terrifies me at this point. (help)
Should i use the global versions instead of the europe ones? Do i need to use "fastboot flash BOOT twrp.." instead of "fastboot flash recovery twrp.."?
I am also happy for suggestions where i could pose this issue more appropriate.
//update: i am now in stock rom and could root it with flashing a magisked boot.img but still cannot enter twrp recovery (-> "no command").
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
thanks @garylawwd
garylawwd said:
Ya you entered the wrong command it's
Code:
fastboot flash boot twrp.img
Click to expand...
Click to collapse
So to be sure: i have stock 11.0.3.0 europe from here installed and i am in slot a now and i cannot go into twrp because it says "no command".
i go to fastboot now, then
Code:
fastboot flash boot twrp.img
with a recent twrp that can run android 10 from here and then power + vol up without switching slots.
garylawwd said:
When you boot to twrp make sure to flash stock boot.img of the firmware which you are currently running and then flash twrp installer.zip flash both of these in twrp and do not reboot between flashes
Click to expand...
Click to collapse
how can i flash a boot.img from twrp? i thought, i can only flash .zips from twrp? Also do i need to take spacial measures to be able to read internal memory in twrp?
//edit: i tried to flash named twrp but it wouldnt boot up into recovery, instead went straight into fastboot. so i flashed boot with stock boot again. no solution in sight.
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
_mysiak_ said:
Just FYI - "no command" is default welcome page of stock recovery. If you see it, you don't have TWRP installed.
Click to expand...
Click to collapse
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
tutankpusch said:
Thank you. Still i would expect twrp to open.
Am i using a/b wrong? When i am on slot a and go into fastboot anf fastboot flash boot twrp.img, then i expect twrp to be installed in a, is that correct? Or is it always installed in the inactive slot and thus i had to switch to slot b before i install twrp to have it on a?
Click to expand...
Click to collapse
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
_mysiak_ said:
No idea with TWRP, never used it on this phone, Magisk is enough for me. But I would follow one of the available guides if you need to have TWRP installed.
Click to expand...
Click to collapse
Thanks @mysiak_d
I used for example this method with this recovery bc it should work with android 10.
straight into fastboot instead recovery :/