Database Users

XT905 - flashing recovery overwrites system

Hey guys,
I have an stock, unlocked and rooted xt905 lying here with stock recovery right now.
For several times now I tried to flash either cwm or twrp but had no luck.
Thats what I did:
- complete backup
- unlock bootloader
- restore backup
- fastboot flash boot twrp.img
- fastboot reboot
Flashing twrp doesnt throw up any error but as soon as I say reboot, the phone reboots into twrp instead of booting the system.
If I try to reboot to system within twrp, it reboots to twrp again. Booting to recovery from twrp brings me to stock recovery.
Its the same thing with cwm and I dont have any clue why, as other users are saying that twrp is working fine.
Till now I tried several different versions of fastboot, twrp and cwm and none of them worked.
Any ideas?

You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."

RikRong said:
You're using the wrong fastboot command.
By typing "fastboot flash boot twrp.img" you are flashing TWRP in place of the boot.img. You need to type "fastboot flash recovery TWRP.img."
Click to expand...
Click to collapse
OMG....
I am working on this phone since yesterday and couldnt figure it out....till now.
Embarrassing! I flashed about a dozen phones before and never had any problems whatsoever and now this.....
Thanks anyway! I am glad that I didnt brick the phone with flashing the wrong partition.

help! not sure if i hard bricked my phone

Hi everyone i flashed kings marshmallow hydrogen os but i didnt like it so i reverted back to my blisspop via nandroid backup. Unfortunately I am know stuck at the oneplus boot screen with the oneplus logo in the middle and the powered by android logo at the bottom. I am unable to boot into twrp. I was able to boot into fastboot mode and managed to flash twrp recovery however the phone will not load into recovery and goes to the oneplus boot screen. I think i softbriked or hard bricked phone because i went from kings hydrogen os which is marshamllow based to my nandroid backup which is blisspop 5.1. IDK what to do know
Bottom line i can boot into fastboot mode. device manager on my pc recognizes phone as android device- marshall london bootlooder interface any suggestions?

If you can Boot to Fastboot you have a softbrick. Somewhere around here is a thread for the recovery tool with the qualcom drivers. Read carefully and maybe give it a try.

Scherzengel said:
If you can Boot to Fastboot you have a softbrick. Somewhere around here is a thread for the recovery tool with the qualcom drivers. Read carefully and maybe give it a try.
Click to expand...
Click to collapse
Ok i thought that was for hardbrick. I will give it a try anyway

neal425 said:
Ok i thought that was for hardbrick. I will give it a try anyway
Click to expand...
Click to collapse
I installed the qualcom drivers and recovery tool, but the recovery tool doesnt do anything

neal425 said:
Hi everyone i flashed kings marshmallow hydrogen os but i didnt like it so i reverted back to my blisspop via nandroid backup. Unfortunately I am know stuck at the oneplus boot screen with the oneplus logo in the middle and the powered by android logo at the bottom. I am unable to boot into twrp. I was able to boot into fastboot mode and managed to flash twrp recovery however the phone will not load into recovery and goes to the oneplus boot screen. I think i softbriked or hard bricked phone because i went from kings hydrogen os which is marshamllow based to my nandroid backup which is blisspop 5.1. IDK what to do know
Bottom line i can boot into fastboot mode. device manager on my pc recognizes phone as android device- marshall london bootlooder interface any suggestions?
Click to expand...
Click to collapse
Do restore again. Flash 5.1.1 patch youre ok
Do you read OP.. Once you go MM you cannot go back without flashing the patch

lummujaj said:
Do restore again. Flash 5.1.1 patch youre ok
Do you read OP.. Once you go MM you cannot go back without flashing the patch
Click to expand...
Click to collapse
can you please elaborate. I have no way of getting into recovery how am i suppose to flash the patch?

Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup

lummujaj said:
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
Click to expand...
Click to collapse
I have done this already... the recovery will not load

lummujaj said:
Download twrp 3.0.0.0 (since you were MM ) flash it via adb... Reboot to recovery and flash the patch.. After flashin it automaticlly reboot. Than restore backup
Click to expand...
Click to collapse
i flash twrp 3.0 using fastboot flash recovery command.....
just so u know
if i type in adb devices nothing is recognized
if i type in fastboot devices my device is recognized

You cant use adb in fastboot mode.. Wtf
fastboot flash recovery recoveryname.img
fastboot boot recoveryname.img
In recovery flash the patch.. Than restore backup.. So simple. Why you complicate
Post cmd comands and results

lummujaj said:
You cant use adb in fastboot mode.. Wtf
fastboot flash recovery recoveryname.img
fastboot boot recoveryname.img
In recovery flash the patch.. Than restore backup.. So simple. Why you complicate
Post cmd comands and results
Click to expand...
Click to collapse
i did flash via fasboot after i flash it says sending recovery (okay) writing recovery (okay) than i reboot but. but when i try to reboot into recovery it does not reboot into RECOVERY it justs stuck at one plust boot screen.

Stucking 1+ logo is because having unsupported recovery from system... After you did restore did you got any error...
Get both recoveries and try command
fastboot boot recoveryname.img
One of them has to boot. Youre doing something wrong

lummujaj said:
Stucking 1+ logo is because having unsupported recovery from system... After you did restore did you got any error...
Get both recoveries and try command
fastboot boot recoveryname.img
One of them has to boot. Youre doing something wrong
Click to expand...
Click to collapse
after i did restore i did not get an error
ive tried to flash twrp 2.87 and twrp 3.0. i promise u i am flashing the recoveries correctly. each time i flash the recovery it says ok. it just wont boot into recovery after it is flashed

Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img

lummujaj said:
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
Click to expand...
Click to collapse
just tried that for both recoverie says downloading boot img okay. than it next thing it says remote: dtb not found

lummujaj said:
Did you try the coomant to boot automaticlly .. Try both recoveries
fastboot boot recoveryname.img
Click to expand...
Click to collapse
hey man i really appreciate you taking the time to help me out but i dont think its gonna work, im just gonna use the hardbrick method to restore my phone

Hope you will find a solution... Try firstaid from general section. I still insist about having bad recovery. Or go to op supoort site and back all to stock

Lost recovery, cant boot, only fastboot

Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode

You need to run the phone in Qualcomm mode on a PC and run the recovery tool to fix you bootloader.
I did the same and it was a royal ball ache trying to find out how to fix it

Don't do what rosswaa said

Why not?

What you should do is boot your phone into fastboot mode, connect it to your pc. Flash this modified TWRP recovery img to your phone https://www.androidfilehost.com/?fid=24459283995297945. After that you have to flash this modified SuperSU (through the new recovery) https://www.androidfilehost.com/?fid=24459283995297946.
The normal recovery doesn't work in OOS 3.0 (just like in HOS) and it's the SuperSU that gives you the soft brick. A dirty flash of the modified SuperSU should fix it.
I also had your problem and I did what rosswaa said which shouldn't be necessary (I lost all my data and backups).

I didn't lose anything, but I tried doing what you said and my bootloader was screwed so wouldn't take a flashed recovery or anything (yes the modified one)
Wish I hadnt been so excited and just flashed but all sorted now

Hmm okay, if it doesn't work with flashing the new recovery img then do what rosswaa said and after that follow this post https://forums.oneplus.net/threads/installation-instructions-faqs-oxygenos-3-0-0.439108/

Obviously try what green says first, if it works then happy days

first i am really glad that someone give some advices on me. But since i am a noob, how can i flash twrp in fastboot mode? using command? "fastboot flash recovery xxx.img"? thx

SPiCa39's said:
Guys... when i tried to flash oos 3.0 on my op2 through twrp, i first wiped the data to install new rom, then install oos 3.0, it failed. I then flashed the recovery i downloaded from the thread, then restart the recovery
I cant boot into the recovery.
System can't boot
Is it called "brick"?
So i tried to flash stock recovery in pc by command, but it says "remote: device is locked. cannot flash images". any solution to this problem?
I can boot into fastboot mode
Click to expand...
Click to collapse
1 Install official TWRP 3.x via fastboot twrp.me/devices/oneplustwo.html
Reboot to recovery
2 install this modified version of TWRP
forum.xda-developers.com/oneplus-2/development/recovery-teamwin-recovery-project-3-0-0-t3310713
Reboot to recovery
3 install oos3 (And supersu)
Sorry i can't post link

Fu**ed up during first twrp installation, forgot to flash supersu before reboot

On xiaomi 3s during first twrp installation, forgot to flash supersu before reboot now i am stuck on MI logo, can access fastboot but not twrp. tried re-flashing twrp (wich i can do) but the phone still stuck with no twrp acess, tried to flash fastboot (flash boot twrp.img) also does nothing.ùi am quite the noob, please help?

redsjack said:
On xiaomi 3s during first twrp installation, forgot to flash supersu before reboot now i am stuck on MI logo, can access fastboot but not twrp. tried re-flashing twrp (wich i can do) but the phone still stuck with no twrp acess, tried to flash fastboot (flash boot twrp.img) also does nothing.ùi am quite the noob, please help?
Click to expand...
Click to collapse
Boot into TWRP. Goto Advanced --> Disable DM-Verify. Reboot device. Done.

now i installed the supersu but when i reboot the phone it always boots to TWRP i think because i flashed
fastboot flash boot twrp.img (yes i am a idiot)
if i want to boot the system what should i do?

redsjack said:
now i installed the supersu but when i reboot the phone it always boots to TWRP i think because i flashed
fastboot flash boot twrp.img (yes i am a idiot)
if i want to boot the system what should i do?
Click to expand...
Click to collapse
As far as I read this thread you forgot to turn off the DM-Verify option in TWRP after install and rebooted immediately.....
Hate to break it to you but your currently installed OS is now pretty much dead now. Had the same issue when I first tried it.
You need to install a clean MIUI ROM first via fastboot and MIFlash-Tool. Then proceed to install TWRP again. When TWRP is booted the first time it will ask your permission to Modify the System. Swipe to confirm that (needed for most operations TWRP is able to do).
After you allow the system modify part, you are in TWRPs main menu. Tap on "Advanced", then tap on "Disable DM-Verify". Once again swipe to confirm.
After that, you should be able to have TWRP on your device and should be able to boot normally to MIUI... or you go straight ahead and flash a new Custom Rom.

thank you.
So i will need to download a new rom (any suggestion on which one is good? i did install twrp because my vendor rom didn't work with local 3g and LTE) and install it with the miui flash tool. Than repeat the twrp installation but disable dm-verify first, (than reinstall super su?),and at the end reboot.
No need to clear anything?

i flashed the global stable rom from the xiaomi flash tool it say successful and took just a second but i am stuck still on mi logo....

Is your phone unlocked?
In fastboot fastboot oem device-info

i unlocked it just one day before with permission message from xiaomi.

Next time used cofface twrp for redmi 3S: http://en.miui.com/thread-244098-1-1.html
Sent from my Redmi 3S using Tapatalk

Ez. Go to fastboot mode, flash again the whole ROM and flash your TWRP again. Don't forget to disable DM-verify. It stuck at logo not because of you forgot to root your device, is because of you forget to disable DM-verify.

boot loop / stuck after installing TWRP

hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?

shikaji said:
hi,
this forum provided me with a ton of useful info but i still couldn't manage to root my phone (F5321), let alone implement custom recovery. after flashing TWRP i always end up either with a bootloop or the screen stuck on displaying 'sony' (waited +20min). i tried the following procedure (at first just 1 + 3):
1) flash via flashtool/xperifirm [flashmode, stock 34.4.A.2.118, wipe userdata // wipe everything]
2) fastboot flash boot boot.img [genesis kernel 1.09 // modded img from this thread // patched img with rootkernel]
3) fastboot flash recovery twrp.img [TWRP 3.3.1 // 3.3.2]
4) directly start into TWRP, format data (to get rid of encryption), wipe cache and reboot to system
=> every time: boot loop until sony screen or it gets stuck on the sony screen
=> i can still start into TWRP
=> flashing stock without TWRP works just fine
edit: it even bootloops when starting TWRP via fastboot boot twrp.img (no matter if before or after first start of flashed stock)
edit2: system boot works if i use TWRP in read-only mode ... but then i can't root or do anything fun ...
any ideas what i can try next?
Click to expand...
Click to collapse
I had a very difficult time rooting my Xperia X Compact (F5321) using the method you describe above. I had exactly the same problem with bootloop and sticking on the Sony screen. My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
So I opened up ADB and flashed the renamed boot.img file, followed by Twrp. Then I booted into TWRP recovery (power button + volume down) and installed the supersu (or magisk if you prefer) and drmfix.
Then I rebooted to system and after a few minutes it booted normally into the Xperia homescreen.
Regards,
Dave

funkoot said:
My problem was that I did not rename the boot118.img (Modded boot img for 34.4.A.2.118)to boot.img before I flashed it over ADB which resulted in the issues you mentioned. So I'm assuming it's an issue with your boot.img file. Maybe try the original boot118.img?
Click to expand...
Click to collapse
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!

shikaji said:
does the file name of the boot image matter even if i of course change the command accordingly to "fastboot flash boot boot118.img"? i feel like that can't really be but i'll give it a try anyway, thanks!
Click to expand...
Click to collapse
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.

shikaji said:
nope, that wasn't it either.
i also tried now having the boot118.img patched with magsik but same problem occurs. just can't get it to work and i don't know why.
Click to expand...
Click to collapse
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app

Bluestar01 said:
I also had lot of problems with thjis root procedure.
The info i found
in twrp the question if the twrp app should be installed choose do not install
After this i was able to boot correctly and install omni, gaaps, magisk
Everytime in TWRP choose ---do not install twrp app
Click to expand...
Click to collapse
unfortunately i've tried that as well already. same thing - stuck at sony screen or bootloop.

Hello, any updates ? I have the same problem, after flashing my F5321 with Flashtool to update from android 6 to 8...