I followed all of the instructions in the Nexus 6 Guide to unlock, root and flash a custom recovery.
I was trying to sideload a rom into my phone and was doing advanced wipe in TWRP. I accidentally choose system thinking it would be fine since I am flashing a new rom anyway.
I think I force shut down the phone and now it just stays and hangs on the google logo. I can only get into the bootloader/fastboot. When I try getting into TWRP recovery it just flashes for a second and then attempts to reboot.
I figure I should try flashing a rom via adb bootloader/fastboot but I attempted a few times and failed. Can someone help walk me through this?
Edit: I can access TWRP recovery now... I tried doing sideload several more times but for some reason I keep getting loading rom.zip cannot read rom.zip
Well i going to geuss you know to to get to recovery though bootloader thought your phone
But your phone is semi Bricked
You can download wugs toolkit
And i will show unroot/flash stock you will click bootloop/ bricked and go though the steps
And it will download the stock software and reovery and go though the steps you will be fine
If you want use the same toolkit and root and install twrp again
Do you use a USB otg drive? If you don't you can send a rom to twrp using some commands.
Try to redownload the ROM that won't work and put it on the phone via a USB otg drive or using your pc and don't forgot gaps.
If you're not, use the WUG toolkit to reflash the stock ROM. Then you can use that to flash your new ROM
Unless im missing somethimg, why not just flash the factory image through fastboot and start over?
Like mentioned above, or just flash TWRP in fastboot. Then boot into TWRP, and flash ROM.
Related
Like an idiot I wiped my System inside TWRP. Using TWRP 2.6.0.2
Earlier tonight my phone starting rebooting. I was inside GooManager and tapped reboot to recovery. When I did that, for some reason my phone lost root. Meaning when I went to reboot inside TWRP it stated that it looks as if my phone is not rooted. I rebooted anyway without installing SuperSU through TWRP. I was already rooted. Afterwards, it would boot up fine but kept constantly rebooting only after a minute or two.
I went back into TWRP and clicked through dalvik wipe and cache wipe. Still got reboots. I was planning on flashing CyanogenMod anyways so I thought I'd go on and wipe everything. I went in to advance wipe and check everything. As I swiped the slider to wipe I realized I checked System too, but it was too late.
Now my phone won't boot past the HTC logo with the red text underneath. I can boot into TWRP however so I hope all is not lost. I am currently at work so I have no way to try anything on the phone at the moment but was hoping for some advice on what to try later when I get home.
I'm thinking maybe I'll be able to use the "Mount" tab in TWRP to load a ROM on and flash and everything will be well again. Would I mistaken to think that? If not, I'll purchase an USB OTG cable and use a USB stick but I really need this up an running as quickly as possible.
Also, does anyone think it would be best just to go back to stock at this point (if I can) and start from scratch?
Much thanks for your help and advice,
dgb1891
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
hayame said:
So, oddly enough I did the same thing, How I managed to recover it so you can adb sideload a rom from TWRP and have access to a "working" phone again was to find your stock recovery.img, then flash it via fastboot, and then from the hboot menu, choose factory reset and let the stock recovery do it's thing, then reflash TWRP (I honestly like CWM doe) and adb sideload a rom (presumably what you were using before). It SHOULD fix your problem and you'll be able to mount files again.
Click to expand...
Click to collapse
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
dgb1891 said:
By stock recovery.img you mean a stock HTC image? - or do you mean a recovery like TWRP or CWM?
Click to expand...
Click to collapse
Literally stock recovery.img, not TWRP or CWM.
hayame said:
Literally stock recovery.img, not TWRP or CWM.
Click to expand...
Click to collapse
K. Thanks. I have a feeling this is going to be a bit more complicated than I first thought...
I followed what you suggested and got the phone back up and working. Thanks again.
First of all sorry for my English...
Yesterday I was trying to install vanir room to my p880 after 10 hours I rooted the phone and unlock the bootloader then installed cwm but after reboot I get stuck on logo so I used kdz and load LGP880AT-00-V20a-262-000-MAR-26-2013+0 with (after 4 hours ) then i try using twrp and finally load the room (vanir_p880_4.4.4.112414.zip) and Gapps after rebooting I started getting crashes ( aosp keyboard, com.google, home and back buttons etc didn't work)
so again kdz then i try other room Paranoid but the same thing..
What I'm doing wrong? I used factory reset, wipe etc but same results
what gapps you flashed?
blansh heretics
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
G0ll0 said:
The ones that are here http://forum.xda-developers.com/showthread.php?t=2439739
But I load another rom without gapps and got same errors, wizard stopped, com.Google stopped. And keyboard.
Click to expand...
Click to collapse
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
LGaljo said:
I don't really know what happened, did you successfully flashed kdz?
Where did you get it from? Here?: http://lg-phone-firmware.com/index.php?id_mod=15
Try to flash one of these (choose correct one for you)
Than you have to install recovery again.
But before that you can try to wipe /system, /data, /cache and then flash CM11 (I know it works without problems)
And I recommend you these Gapps: http://forum.xda-developers.com/showthread.php?t=2397942
Click to expand...
Click to collapse
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
G0ll0 said:
well... yes i think I flashed kdz (LGFlashTool ?) I used kdz to recover my phone to original, I know my phone is Korean version and right now I use P88020A-EUR-XXX original firmware installed with kdz
What is CM11? and how i flash it?
so I have to root and unlock bootloader again and use twrp again right?
Click to expand...
Click to collapse
I think you should try with CWM first, get it: http://download2.clockworkmod.com/recoveries/recovery-clockwork-touch-6.0.4.5-p880.img
you can flash it with this app if you are rooted: https://play.google.com/store/apps/details?id=com.cgollner.flashify
then you can download CM11 from here: http://download.cyanogenmod.org/?device=p880
and gapps from last mine post
and then boot to recovery, do factory reset and wipe /system, then flash rom and gapps.
Hope it helps
Crash After Flash OTA Vanir 5.0
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
BermiePT said:
I had a similar experience. I was installing OTA latest update of Vanir...not realising that it was 5.0...a screen came up telling me that it needed to flash another recovery...not realising why it needed that, I ignored the request to flash. Of course, I then "bricked" the phone. I was able to install the original JB 4.12 (v20c) back onto the phone but now it won't root. I've tried almost every method in this forum to no avail.:
ADB just gives a message "error: closing" when I use the boot.exe method
o4xr method does nothing
all-in-one method also does nothing
ADB does recognise the device. Drivers are installed. Any help is welcome!
Click to expand...
Click to collapse
Have you tried to flash a recovery using fastboot? You won't need to root (if you are going to use a custom ROM) and/or it will be easier with a custom recovery
Soft brick after last update.
Hello,
I seem to have a similar problem. I updated a few days ago using Vanir updater. There were no warnings re updating the recovery, just a warning regarding losing root. I checked restore root. The phone rebooted to the bootloader logo, then to a black screen. Now, I can access Cyanogen recovery, SW update mode, abd fastboot mode using buttons and the recovery options. ADB can see the phone only in recovery mode, but not in fastboot or SW update mode. CM recovery has no option to mount USB storage, so my PC cannot see the phone, and I cannot side load a new recovery and flash a new ROM.
Is there any way to use ADB if it cannot see your phone in fastboot or SW mode? Perhaps modify the settings.secure string to enable ADB? ADB can see the phone in recovery mode.
Otherwise I will try flashing a stock ROM via KDZ or LG firmware update tool, the re-root and proceed - but rooting was a major ordeal the first time, so I would like to avoid doing that again.
Thanks in advance.
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Never trust a recovery installed by a tool kit. Grab the recovery img from the site and flash it manually.
all i have now is stock recovery. whats the best way to manually install twrp
go into fastboot and flash it. you have to be in your bootloader to flash via fastboot. you put the file in the same window as your fastboot program, then type.. fastboot flash recovery recoveryname.img, and that will flash twrp. if you type fastboot boot recovery recoveryname.img then itll only boot into recovery one time, thats what your toolkit did.
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
jdpeck said:
I was having issues and wanted to switch to the systemless SU so I decided to start over fresh. used toolkit to restore stock image and unrooted. tried to install newest twrp using toolkit but it kept coming up with bugdroid with red triangle and exclamation mark. Did some research and few places said you have to go back to lp. so I downloaded factory image and went back to lp unrooted and locked bootloader. unlocked, rooted and installed twrp everything was good. I extracted the newest 6.0.1 factory image and installed each component separately except for the recovery. now I am on 6.0.1 and try to go to recovery and bugdroid with red triangle and using toolkit I cannot get the newest twrp to stick. my sdk is updated.
any ideas on what to do?
thanks
Click to expand...
Click to collapse
Don't use toolkits. I recommend yoiu follow @simms22's solution.
Sent from my Nexus 6 running cyosp using Tapatalk
when you have root, you can always use an app, like flashify, to flash twrp recovery. but you need to have root first.
arcane spade said:
Wugfresh Toolkit works great for me and I used it for 6.0.1
Make sure you flash permrecovery file provided by the toolkit, it prompts this during the steps.
If the copies of factory img or recovery provided by the toolkit are not working one easy way is download your own, the toolkit allows you to use your own files and not the one it obtains.
Click to expand...
Click to collapse
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
jdpeck said:
I have tried with and without perm recovery checked, I had the newest twrp img file so I choose other and selected it, I even used the option for one time recovery boot with twrp and then flashed twrp within it like I was updating twrp and still nothing. I am going to try fast boot itself without the tool kit.
Is there any other part of the stock factory image that would update the recovery? I didn't install it coming from lp but it still went back to stock instead of staying on twrp
Click to expand...
Click to collapse
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
scryan said:
This is why we don't use toolkits.
Boot to bootloader mode
Code:
fastboot flash recovery <recovery filename>
Where <recovery filename> is the path and filename of the twrp image you downloaded
After flashing use the arrow keys to boot into your newly installed recovery
Take a backup of your phone
Use recovery to boot android
Reboot to recovery with custom power menu options, or by opening a console on your phone and typing in reboot recovery
Post here to tell me that I am right, and thank me.
If you don't reboot to recovery from the bootloader, it will likely be restored back to the OEM recovery.
Click to expand...
Click to collapse
well, thats how you should flash recovery. but its not the reason that we dont use toolkits. we dont use toolkits for several reasons.. 1. they mess up 2. doing it properly is just as fast if not faster 3. newbs think that toolkits are made for them to use. well, they are wrong. toolkits teach you absolutely nothing, which is the worst for beginners.
simms22 said:
no. but when you flash the full factory image, stock recovery will replace twrp. if you just want to update, flashing the system.umg and boot.img will work, and youll keep twrp.
Click to expand...
Click to collapse
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
jdpeck said:
thats why after going to lp and getting twrp working I flashed system, boot, and newest radio independently and skipped over recovery but for some reason it reverted back.
just using fastboot by itself worked great thanks for the help
Click to expand...
Click to collapse
if you skipped the recovery.img, your recovery should have stayed.. oh, never mind, i just remembered a file that you need to remove after the first boot, or itll install the stock recovery after the first reboot. its called recovery-from-boot.bak. if you remove that on first boot, youll be fine
I need help, I was trying to root my Oneplus 3T, with stock OOS 4.0.2. After following all the steps, I flashed the dm-verity to keep with the steps, and that worked. But after formatting data, as it was suggested, it gave me an error. It showed like everything was encrypted which shouldn't due to the flash of the dm-verity and now I'm stucked in not a bootloop because the phone actually boots but I cant do anything because the encryption error takes me back to the recovery, which shows an error etc. Is there any tutorial to fully recover the phone from this point? Thank you very much in advance.
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Anova's Origin said:
Did you try flashing SuperSU after flashing dm-verity? If the zip isn't on your phone at this point, you can go into bootloader mode and use adb to push the SuperSU zip on and flash it that way.
You can use the toolkit to push the files if you want, it'll be easier that way: https://forum.xda-developers.com/oneplus-3t/development/toolkit-oneplus-3t-toolkit-unlock-t3507729
If all else fails, flashing a clean rom always works.
Click to expand...
Click to collapse
Now I'm stuck in a bootloop after reflashing stock recovery. If i reflash the boot.img via fastboot from the .zip of the official OOS 4.0.1, will it work? Thank you very much
Not sure why flashing recovery would cause a bootloop. Might be safer just to sideload a fresh ROM. If you're worried about losing files, you can use adb to pull whatever you need first from sdcard prior to flashing.
What I did in a similar situation was to reflash the stock recovery first using the unbrick-toolkit. When booting into recovery then, there is an option "forget password" when it asks you to enter the password. If you select that, it will simply wipe your phone completely and you can start over again.
Hi,
I'm having a bit of trouble. I had a brand new Redmi 4X, and I was advised to install TWRP, root it, and install the Xiaomi.eu rom until LineageOS is released. I unlocked the bootloader, flashed TWRP, managed to get into it once and now I can't do it again. When TWRP loaded it asked me for a password for decryption but it let me just skip it it seems (not sure if that is the problem) but now I can't boot normally, I can't boot into recovery, but fastboot seems to work okay. How do I go about fixing this?
I've tried reflashing TWRP but I still can't get to it, and I don't really know enough about this stuff to know where I've gone wrong.
UPDATE - I think this is to do with dm-verity and having the stock kernel installed. Now it's too late to undo what I've already done, so I hope to god that someone knows how to fix this.
UPDATE - Right, the problem is solved I think. I had to do an awful lot of googling, and I'm not entirely sure what it was specifically that fixed it. But I found a guide that taught me the fastboot command "fastboot boot twrp.img" which saved the day. Even when my phone wouldn't let me into recovery, it allowed me to flash a no-verity.zip which i think is what allowed me to boot, and it allowed me to flash superSU.zip and then the ROM I was aiming for. And now I've booted into the ROM successfully and hopefully I am rooted and all is well. Plus I can access TWRP as normal now.
Any help would be greatly appreciated
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
brljak83 said:
Can you boot into TWRP by pressing the buttons so that you boot directly to TWRP??
Have you tried Command Prompt to boot with commands in to recovery??
And if you get into TWRP you should have everything on the SDCard and then just
format all things except SDCard and then flash from SDCard everything
That is what I would try..and yes it ask for a password but just skip it to get to it
If you can get into TWRP to flash from SDCard then you good to go..if not
Google all the commands for CMD..and plug your phone to the PC and flash everything with the
commands.....
Let us know what is working and what not and what steps exectly you are doing
EDIT
Turn off your device > Press and hold “Power” and “Volume +” buttons at the same time.
After short vibration signal release the power button and wait for TWRP to start.
To boot in stock recovery open “Update” app.
In the setting select “Boot in recovery”.
Click to expand...
Click to collapse
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
brokemyG2 said:
Thanks for the reply. I can't get into TWRP. Even if I could get into TWRP how would I get files on the phone to flash them?
Is it possible to flash any rom from the pc directly and if it is will this possibly help? I think it's not booting because the kernel is still stock.
I'm not sure what you mean in the edit, how do I boot into stock recovery without being able to boot the phone (and when I have already flashed TWRP)?
Click to expand...
Click to collapse
Hii
I just have been reading about this bootloop
Go over here and read all of the 6 pages..will not take much time but could help you out much
https://forum.xda-developers.com/xiaomi-redmi-4x/development/official-twrp-3-2-1-0-xiaomi-redmi-4x-t3718217
Hey, I have exactly the same problem. Latest stock rom, flashed twrp in fastboot and got into the boot loop. Nothing works. I can only enter fastboot. What exactly did you do then? What is this no-verity.zip? I can't find anything about it.
I had a problem
I unlocked bootloader then installed redwolf recovery and took a nandroid backup. After that i rebooted to system but stuck into bootloop, could not boot to recovery, could not boot into system, So the only thing worked was that i flashed fastboot rom with mi flasher. And syccessfully rebooted to system with bootloader locked and stock recovery. So, if anyone have same problem you can do the same. How do i install recovery safely again? Should i use TWRP only? Should i flash v3.1.0 with lazy flasher or v3.2 directly without lazy flasher? I don't want to stuck into bootloader again, have to get all data deleted.