Database Users

Am I being a little dumb....help please

Hello there, im quite good with the old ADB and FASTBOOT commands but I am stumped, and its probably a silly little thing I have probably forgotten.....
I lost my recovery, after flashing completely going back to stock, got all drivers installed, but couldnt get recovery installed any way.....
so i visited this post : http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 and it worked, and i have twrp 2.7.0 on the phone, but I can remember having 3.0.2.2 on it, so i download the .img file from the site, and flashed that via the images section on twrp recovery, i reboot, and ..... no recovery....... so I have to flash the first aid zip to get 2.8.7.0 twrp installed again....how do I upgrade it.....I have working drivers, access to fastboot, but I am being a bit dumb!!!!!! HELP!

biggary said:
Hello there, im quite good with the old ADB and FASTBOOT commands but I am stumped, and its probably a silly little thing I have probably forgotten.....
I lost my recovery, after flashing completely going back to stock, got all drivers installed, but couldnt get recovery installed any way.....
so i visited this post : http://forum.xda-developers.com/oneplus-2/general/firstaid-zip-revert-h2os-mm-beta-to-lp-t3306967 and it worked, and i have twrp 2.7.0 on the phone, but I can remember having 3.0.2.2 on it, so i download the .img file from the site, and flashed that via the images section on twrp recovery, i reboot, and ..... no recovery....... so I have to flash the first aid zip to get 2.8.7.0 twrp installed again....how do I upgrade it.....I have working drivers, access to fastboot, but I am being a bit dumb!!!!!! HELP!
Click to expand...
Click to collapse
I would suggest that you flash 3.0.2.2 recovery image via fastboot. Remember to reboot to recovery after you flash it for the recovery to stick.

Need an expert
Yousvel said:
I would suggest that you flash 3.0.2.2 recovery image via fastboot. Remember to reboot to recovery after you flash it for the recovery to stick.
Click to expand...
Click to collapse
Im having this problem
you can see the video this is the end of youtube link ===> watch?v=2vrHR5CTZe8
please help!

Need help !

Hey guys I recently restored a nandroid on my 6p from a 7.1.1 rom but I get stuck on boot logo now when j go to recovery(TWRP) all my files are completely gone? and it says something about encryption ...did I brick my device? And if not what steps do I have to do to get back up and running again? Like download rom gapps and SuperSU all over again on my PC etc..? I know my bootloader is unlocked still and I have to be rooted still since I can go to twrp so any help will be appreciated thanks.

Jiggs82 said:
Hey guys I recently restored a nandroid on my 6p from a 7.1.1 rom but I get stuck on boot logo now when j go to recovery(TWRP) all my files are completely gone? and it says something about encryption ...did I brick my device? And if not what steps do I have to do to get back up and running again? Like download rom gapps and SuperSU all over again on my PC etc..? I know my bootloader is unlocked still and I have to be rooted still since I can go to twrp so any help will be appreciated thanks.
Click to expand...
Click to collapse
I am not exactly an expert, but I would recommend to flash back the latest image from Google...go back to completely stock and then if you want root and install TWRP again. Good news is your bootloader is still unlocked, so I don't think you are bricked. Good luck!

Pecata said:
I am not exactly an expert, but I would recommend to flash back the latest image from Google...go back to completely stock and then if you want root and install TWRP again. Good news is your bootloader is still unlocked, so I don't think you are bricked. Good luck!
Click to expand...
Click to collapse
Ok so should I use the Nexus root toolkit and start from scratch again? Yeah my bootloader is unlocked and I can see twrp so I must still be rooted ..just wiped my whole device that all thanks

Try re flashing the Vendor.img sounds like the vendor didn't get restored
Sent from my Pixel XL using Tapatalk

i would but everything (files etc.) are gone from my phone...so i would have to download and flash it thru my pc right? if not ill probably just flash a rom gapps the vendor of course and super su and see if it boots up to the rom

Yup just download the Factory Image and extract the vendor image and flash it with fastboot.
Or flash another ROM /Gapps/ Vendor
Sent from my Pixel XL using Tapatalk

Not clear. The files you had before restore are missing or you miss files from your backup? Twrp backup does not backup your /data/media.
White google logo hanging is a due to bad vendor files.

Bricked, bootloop tried all I can think of

I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P

maddmarkk said:
I was on the last beta n4f26t, and flash TWRP successfully, then went to flash superSU from twrp, this when wrong and everything goes downhill from here. I tried flashing back the last update, in it's entirety following the Heisenberg guide for returning to stock didn't work, tried flashing twrp again still can't get into recovery (just boot loops) I tried a previous update NMF26F and got to the dead android recovery screen but when I tried to flash back the OTA nothing happened and went back to bootloop on reboot. I've used the nexus root kit and still nothing. What can I do to fix this? I've honestly looked up every resource I could think of before posting this here. really hoping I didn't perma brick my 6P
Click to expand...
Click to collapse
Edit I was on NPG47I the lastest beta update not n4f26t

Hello... So now you only have access to the bootloader Or bootloader and stock recovery?
If your bootloader is unlocked, you can try:
fastboot erase cache
fastboot format userdata
Of course it will wipe your internal storage...

maddmarkk said:
Edit I was on NPG47I the lastest beta update not n4f26t
Click to expand...
Click to collapse
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?

v12xke said:
I would concentrate on trying to get a working recovery first. Almost everyone who lost recovery mode never got their phone back- classic BLOD. First try fastboot FORMATTING recovery and then both fastboot flash twrp, and then fastboot boot twrp. If you can get a working recovery there may be hope. If you can never boot to recovery mode, I think you are done. From your bootloader screen, what is your bl version?
Click to expand...
Click to collapse
just updated it to 3.67 from the 7.1.2 beta image

maddmarkk said:
just updated it to 3.67 from the 7.1.2 beta image
Click to expand...
Click to collapse
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?

v12xke said:
Yes, but is that what is shown on your bootloader screen? How did you flash it? With flash-all.bat? Which 7.1.2 image did you flash and how did you do it?
Click to expand...
Click to collapse
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image

I know with older versions of TWRP there was a problem with the EFS partition that contains the IMEI info. What version of twrp are you using??? I thought I bricked my Nexus 6p after restoring a backup but it was actually just me screwing up my EFS partition. The newer versions of twrp (i think 3.0.3 and up) fixed this problem. Still though, if it is that, and you flash a new twrp version it won't fix your problem. If you have the time search through the forum for the EFS partition fix. I don't know the commands off the top of my head but I know this helped a lot of people. Worth a shot.

maddmarkk said:
BL: angler-03.6.7
Baseband: angler-3.81
I see all normal BL options and I flashed it with the nexus root kit and used https://developer.android.com/preview/download-712.html this image
Click to expand...
Click to collapse
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.

same boat
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?

mikeygeer said:
anxious to hear results: I can't get to recovery and am bootlooping - tried a bunch of things using Nexus Root Toolkit . Curiously enough earlier when I was trying to flash an older version or ressurection remix, even my TWRP would bootloop so I couldn't flash anything without it quitting - anyone ever hear of that happening?
Click to expand...
Click to collapse
Hello... Try looking here: https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528

v12xke said:
OK, but when you try to boot to recovery, it bootloops? Never goes to recovery? Try the steps above to successfully flash the recovery partition using fastboot. I suppose you can use NRT, but download the latest version of TWRP and try both flashing and booting the twrp.img.
Click to expand...
Click to collapse
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"

maddmarkk said:
I have flashed TWRP 3.1 and I can not boot into recovery, I flashed it manually with fastboot flash recovery "image"
Click to expand...
Click to collapse
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...

5.1 said:
Hey... Did you try to boot TWRP?
From bootloader: fastboot boot twrp.img
If this fails and you only have access to the bootloader, i think you are SOL.
Good luck...
Click to expand...
Click to collapse
you meant do this in the fastboot CMD right? if so then it just boot loops :'C

maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Yep from bootloader:
fastboot boot TWRP.img
I don't have any other idea sorry...
You can try to contact Google or Huawei. Even being out of warranty, some people have had their device replaced.
Good luck...

maddmarkk said:
you meant do this in the fastboot CMD right? if so then it just boot loops :'C
Click to expand...
Click to collapse
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.

DEVILOPS 007 said:
Are you able to get into recovery and adb sideload a stock OTA from the google developer website? That's always saved me when I've had problems.
Click to expand...
Click to collapse
Guess you didn't read the rest of the the thread...

We don't need more posts about bootloop. There is a main topic that has been discussed for multiple pages:
https://forum.xda-developers.com/nexus-6p/help/boot-loop-death-nexus-6p-t3533528
I personally had the issue and had to RMA the phone. I suggest you do the same.

5.1 said:
Guess you didn't read the rest of the the thread...
Click to expand...
Click to collapse
Yeah honestly I couldn't be bothered to be perfectly truthful

so i'm going thru the same thing as OP.
I need help.

[Topic can be closed] Phone can't find bootloader? and i can't flash TWRP

Hi all,
I got some strange problem:
I did an ODIN reinstall of complete OREO stock samsung ROM.
I swiped in twrp but i didnt want that so i reflashed twrp with odin.
Then i got a red screen while i wanted to enter TWRP. I retried flashing, no luck still a red screen. Also older versions.
I do however seem to be able to boot into samsung recovery mode.
I tried to flash twrp with adb. But my phone will not boot into Bootloader mode? It just restarts?
(as i understand, Bootloader mode is NOT download mode right?)
It is soft brick something?
Any help would be appriciated very much.
Thx!
Mrmoves
EDIT: I just found out im on Bootloader 3.
I have flashed the newest OREO a lot of times now with ODIN. Its works. Going into recovery works as well.
Still not able to boot into bootloader, or install TWRP for some reason?
EDIT2: I fixed it!. i flashed the newest OREO for the 5th time or smhting and for some reason i was also able to get TWRP on it again =)
Now rooted with Magisk all working =)
TOPIC CAN BE CLOSED

twrp gets erased

Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you

Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.

As far as i remember there were 2 files. dm-verity and forced encryption. I never needed them but if you stay on stock you will have to flash those so that twrp doesn't get replaced by stock recovery everytime you reboot. Check the how to root forum you should find more information there about this.

Or you can just root it and twrp won't erase with stock recover.

naikxda18 said:
Hello guys i need an urgent help yesterday i unlocked bootloader on my g5 plus which was running Android 8.1 everything was ok i installed twrp latest version it got installed but when i reeboted to system the twrp gets erased idk how whenever i try to boot into recovery it shows no command sign and then after pressing power button it boots into stock recovery ! Guys can anyone mention me a solution thread or just explain me what to do ! Thank you
Click to expand...
Click to collapse
Do this:
[email protected] said:
Reinstall it, and then boot right into recovery. If I remember, there is a pop up when you go to close twrp and boot to system to keep twrp, or some such nag.
Click to expand...
Click to collapse
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?

Wolfcity said:
Do this:
and flash Disable_Dm-Verity_ForceEncrypt_02.04.2019:
https://yadi.sk/d/HLr5vjnkA8gaqw
Click to expand...
Click to collapse
Thanks but i flashed RR pie soon after flashing twrp now its working fine

[email protected] said:
hmmm, that's strange. I've never flashed that and never lost twrp on any of the phones I've unlocked. Is that new with unlocking Oreo?
Click to expand...
Click to collapse
I didn't either, as you wrote if you boot into TWRP before going to system it should stick or also if you flash magisk before booting the OS.
But there are some devices/ROMs that need the no verity flag to be disabled so flashing this file might help if TWRP won't stick (even when DM verity looks for a tampered system partition in the first case). There are also some terminal commands to do that but I forgot them at the moment.
I mainly used the zip to keep my /data partition decrypted after reformating it. When flashing Nougat magisk did the job for me but when I upgraded to Oreo /data was reencrypted again after flashing magisk and booting into system.
The above zip prevents /data from being encrypted again and may make sure that TWRP sticks.

ahhh, ok I see. Thanks for the explanation.