Hi I just bought a 2nd hand M8 s-on tampered whenever I go to bootloader then select recovery it just stock on htc logo for a very long time so hard to off even pressing power button.
question is, is it possible to delete the recovery installed? I suspect he deleted the custom recovery installed on that phone.? or can I use flashify to add new TWRP? thanks hope someone will help me
Yes, you can use fastboot to boot or install a new recovery.
First, get a recovery image - either TWRP or CWM. Make sure you download the .img file for your phone. Then, boot into fastboot mode and flash it. This thread covers pretty much everything you need - just skip the bootloader unlock section, as you are already unlocked:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
jshamlet said:
Yes, you can use fastboot to boot or install a new recovery.
First, get a recovery image - either TWRP or CWM. Make sure you download the .img file for your phone. Then, boot into fastboot mode and flash it. This thread covers pretty much everything you need - just skip the bootloader unlock section, as you are already unlocked:
http://forum.xda-developers.com/htc-one-m8/general/vomerguides-m8-bootldr-unlock-s-off-t2800727
Click to expand...
Click to collapse
thanks BTW Im not good on those command Ive tried on my m7 last month i think to use flashify to install a new recovery can I use the same method?
imfuzzyyy said:
thanks BTW Im not good on those command Ive tried on my m7 last month i think to use flashify to install a new recovery can I use the same method?
Click to expand...
Click to collapse
My recommendation would be to learn how to do it with adb/fastboot. Apps like Flashify are a crutch, and won't do you any good if you find yourself in a jam, such as not being able to boot into the OS.
Don't forget to: fastboot erase cache
thanks for your help evryone but i really dont know all of those command but can I use flashify for this method?
imfuzzyyy said:
thanks for your help evryone but i really dont know all of those command but can I use flashify for this method?
Click to expand...
Click to collapse
You won't know the commands either if you don't learn to use them but instead rely on apps like flashify. Why have a custom recovery like TWRP? Are you planning on flashing a custom ROM? What if that custom ROM doesn't boot up and you can't get into the OS, how will you then fix the problem seeing as flashify won't be available to you?
I'm in agreement with Redpoint on this, you should really consider learning the basic commands at least. It will make fixing any problems you might encounter much more simpler. Relying on all-in-one toolkits and apps like flashify won't make matters easier for you if things go "South".
The issue however is not that you don't know it, instead it's your reluctance to want to learn it. Yet when something goes wrong you'd still come on here expecting everyone else to fix the problem for you.
[Guide] How To Setup And Use Fastboot
There you can find some reading materials for fastboot commands.
{Tutorial} (Basics of ADB) For Beginners Part-1
There's some stuff about adb as well.
XDA-University Some great informative threads right here on XDA. Everyone here is more than willing to help someone with problems, no doubt. The least, however, that you can do is also educate yourself on the basics, else it's just insulting to expect others to go through such effort if you yourself can't even make the effort to learn anything. Especially if you are the one(inexperienced) that wants to flash and make changes to his device. :good:
If you're willing to learn some and need help along the way, then ask and anyone here can help and would be more than happy to! :highfive:
All that said, download the recovery you need. Get yourself adb or the mini-sdk from mike1986's site get it set up and start doing things the right way.
After you have it all set up. Connect phone to PC, reboot to bootloader.
Code:
adb reboot bootloader
Flash recovery
Code:
fastboot flash recovery name_of_recovery.img
Clear cache
Code:
fastboot erase cache
Reboot and enjoy.
Code:
fastboot reboot
BerndM14 said:
You won't know the commands either if you don't learn to use them but instead rely on apps like flashify. Why have a custom recovery like TWRP? Are you planning on flashing a custom ROM? What if that custom ROM doesn't boot up and you can't get into the OS, how will you then fix the problem seeing as flashify won't be available to you?
I'm in agreement with Redpoint on this, you should really consider learning the basic commands at least. It will make fixing any problems you might encounter much more simpler. Relying on all-in-one toolkits and apps like flashify won't make matters easier for you if things go "South".
The issue however is not that you don't know it, instead it's your reluctance to want to learn it. Yet when something goes wrong you'd still come on here expecting everyone else to fix the problem for you.
[Guide] How To Setup And Use Fastboot
There you can find some reading materials for fastboot commands.
{Tutorial} (Basics of ADB) For Beginners Part-1
There's some stuff about adb as well.
XDA-University Some great informative threads right here on XDA. Everyone here is more than willing to help someone with problems, no doubt. The least, however, that you can do is also educate yourself on the basics, else it's just insulting to expect others to go through such effort if you yourself can't even make the effort to learn anything. Especially if you are the one(inexperienced) that wants to flash and make changes to his device. :good:
If you're willing to learn some and need help along the way, then ask and anyone here can help and would be more than happy to! :highfive:
All that said, download the recovery you need. Get yourself adb or the mini-sdk from mike1986's site get it set up and start doing things the right way.
After you have it all set up. Connect phone to PC, reboot to bootloader.
Code:
adb reboot bootloader
Flash recovery
Code:
fastboot flash recovery name_of_recovery.img
Clear cache
Code:
fastboot erase cache
Reboot and enjoy.
Code:
fastboot reboot
Click to expand...
Click to collapse
thanks for the help bro., btw where can I install official TWRP for our m8? can you provide some link? really appreciate it thanks
imfuzzyyy said:
thanks for the help bro., btw where can I install official TWRP for our m8? can you provide some link? really appreciate it thanks
Click to expand...
Click to collapse
TWRP 2.8 - HTC One m8 2014 GSM page
Related
I'm not sure why but my recovery mode doesn't work, it just show me a little Android with a red signal and no one letter...
My phone is already rooted but I dont remember if I installed a recovery mode or if it was part of the root process, I need to install a "sound fix" zip, but I can't right now...any ideas??? Can I fix it without lose my data?
I think you don't have a custom recovery yet... Flash one and good to go.
Sent from Google Nexus 4 @ crSimple
Yes, you can install or flash and update recovery without losing data.
If proper USB drivers are installed and you can use ADB with the GNexus while is in developer mode, then you are ready.
Download latest CWM Recovery or TWRP Recovery.
Reboot the phone to bootloader mode. If your ROM has it in power option, you can use that to boot into bootloader.
Otherwise with adb: adb reboot-bootloader
On your computer, put above the recovery .img file in same folder as adb and fastboot executables.
then: fastboot flash recovery name-of-recovery-file.img
You will get an OK, success confirmation if all done properly. Now you can boot to recovery. Done.
Is there a simpler way? I'm not very "acquainted" with ADB :/, something more, ADB for X64 is about 480mb! Is that normal or Am I downloading another thing???
Jerber said:
Is there a simpler way? I'm not very "acquainted" with ADB :/, something more, ADB for X64 is about 480mb! Is that normal or Am I downloading another thing???
Click to expand...
Click to collapse
If you have never used ADB tools or ever attempted bootloader commands, it is probably not recommended for you to change stuff around because there may be a chance something can go wrong and you might not have immediate help to restore your phone. Doing these changes are permanent to your phone, so just keep that in mind if you still want to attempt it (eg you don't know how to return it to stock yet).
Personally, I don't recommend all-in-one tools because of the same reason as above, you don't learn anything if you need to do something command related or mess up.
It sounds like your phone is still bootloader locked to stock version of android but you may have have used SuperSU or some root exploit to get root previously.
All you need are 4 things:
Read and understand the guide @efrant posted for newbies: http://forum.xda-developers.com/showthread.php?t=1812959
Universal Naked Driver
ADB lite - ADB with less stuff, around 2MB
CWM or TWRP recovery img file (previous post)
When you think you are ready just post back.
kaijura said:
If you have never used ADB tools or ever attempted bootloader commands, it is probably not recommended for you to change stuff around because there may be a chance something can go wrong and you might not have immediate help to restore your phone. Doing these changes are permanent to your phone, so just keep that in mind if you still want to attempt it (eg you don't know how to return it to stock yet).
Personally, I don't recommend all-in-one tools because of the same reason as above, you don't learn anything if you need to do something command related or mess up.
It sounds like your phone is still bootloader locked to stock version of android but you may have have used SuperSU or some root exploit to get root previously.
All you need are 4 things:
Read and understand the guide @efrant posted for newbies: http://forum.xda-developers.com/showthread.php?t=1812959
Universal Naked Driver
ADB lite - ADB with less stuff, around 2MB
CWM or TWRP recovery img file (previous post)
When you think you are ready just post back.
Click to expand...
Click to collapse
Thanks, I'm gonna read it now!
My GN is on 4.3, with bootloader unlocked and rooted (of course) my intention with CWM is install a soundfix cuz GN has a VERY low sound and I'm missing some calls and sms all time :/
I used to have a Xperia device and I remember that root process and the installation of CWM are very easy in comparison with my GN, I thought it will be easy too.
Jerber said:
Thanks, I'm gonna read it now!
My GN is on 4.3, with bootloader unlocked and rooted (of course) my intention with CWM is install a soundfix cuz GN has a VERY low sound and I'm missing some calls and sms all time :/
I used to have a Xperia device and I remember that root process and the installation of CWM are very easy in comparison with my GN, I thought it will be easy too.
Click to expand...
Click to collapse
Should be simple for you from what is mentioned above.
After installing the drivers and adb, phone connected via usb, Steps 1-3
1. Set your phone to bootloader mode. 2 ways to do it:
A. Turn phone off, VOL+ and - and power button at same time until you see it.
B. Using PC: after adb is installed, use command terminal and go to folder it is installed in and type adb reboot-bootloader
2. In bootloader mode, flash the CWM recovery.
With your recovery .img file located in the same folder as adb and fastboot executables: in the terminal type fastboot flash recovery recovery-clockwork-6.0.4.3-maguro.img (or the toro or toroplus with the CWM image depending on your Galaxy Nexus type).
3. Boot to recovery.
Hit Vol button a few times until you see recovery on the screen while in bootloader mode, press power button to continue.
Don't forget to make a backup of stuff, including your EFS/radio folder.
Try this www.youtube.com/watch?v=foLQCNxroHw&app=desktop&persist_app=1&hl=en-GB&guid=&client=mv-google&gl=RO it's a complete guide but it's for nexus 10. Same thing with the gnex
Thanks a lot guys! I will try to do it!, something more
*I saw another option but I'm not sure if it work with the GN, some people say that a easy way is just download the app "Rom manager" from the Play Store and install the CWM from the app, what do you think about it?
*I have some little problems with stock 4.3 (for example, my bluetooth is useless :S), Do you recommend me switch to a stable CM rom (like the last official 10.2.0)?
Im not hurry for 4.4 or CM11, but I'm not sure if 10.2.0 has some bugs, anyways seems like a better option than the stock 4.3.
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
avelinosilva said:
After several atempts to update to 6.0.1
Bootloop.....
Instal the TWRP....
adb push system.img /sdcard/ ...i can´t CLOSED
ADB recognized but can´t fash recovery
Please i need some help
Click to expand...
Click to collapse
You are not bricked.
In order to update to the new OTA you need to go back to fully stock LCB43B image. That means flashing stock boot, recovery and system. BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Then reboot to bootloader and flash the stock recovery and boot files.
Next, download the OTA and reboot into stock recovery (not TWRP) in order to update using adb sideboard. Use the guide here: http://forum.xda-developers.com/showthread.php?p=65607393
Hit thanks if this has helped.
bigdave79 said:
BUT unfortunately there's a problem when trying to flash the stock system.img in bootloader. So you have to boot into TWRP, use adb push to get the system.img file onto your internal memory and then flash it using adb shell commands. Use this thread: http://forum.xda-developers.com/showthread.php?p=63173308
Click to expand...
Click to collapse
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
avelinosilva said:
I had instaled Androi Studio and Sdk is any problema to use W10 64 bits.
Please can you help me with the commands to use?
is this one:
adb devices
In Twrp advance select adb sideload
fastboot flash recovery recovery.img
I´m doing something wrong??
If i will send the Wacth to Huawei assistance they can fix it?
Best regards and thank you all for your help.
Click to expand...
Click to collapse
No.
Boot to bootloader and type "fastboot flash system system.img"
You should not be in recovery trying to fastboot flash. It will not work.
Latest SDK is fine on Windows 10. Make sure you use the fastboot and ADB from the latest SDK.
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
/-\
|
|
This
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
avelinosilva said:
Scott you are my hero.....i got my watch alive......:laugh:
Tank you veryyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyymutchhhhhhhhhhhhhhhhhhhhhhhhhhh mate.:good:
Click to expand...
Click to collapse
Good to hear!
Scott said:
/-\
|
|
This
Click to expand...
Click to collapse
I was stuck for last 12 hours and watch was in bootloop. i tried flashin again and agin . Scott i love you :laugh:
i think it was that i was using old adb and fastboot. the latest ones helped. Also there is no need to flash twrp. Even if you get file sparce issue.
Salute to You :good::good::good:
Now i am back to LCB43B will try to update to 1.4 via stock recovery now
Yeah, the ADB / Fastboot changed with Lolipop. Anything pre-lolipop will give issues.
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
kurosen said:
I've never flashed anything onto my watch, but yesterday after recharging the battery after it going dead, I get stuck at the 4 dots boot animation. I'm able to reboot the watch, and even get into the normal fastboot menu, but clearing cache, data, and resetting to default doesn't help. I'm really hoping what you guys are doing will fix the trick for me. I simply want to return the watch to stock, but I'm seeing conflicting reports on how to proceed with this.
I've downloaded the Android SDK, but have never used it before. I keep hearing things about adb, and flashing system.img using the latest fastboot - I don't know where to find either of these or how to use them. Would you awesome people mind doing a little hand holding with me and give me a bit of detail on how to proceed with the solution from C3C076?
EDIT: So I think I figured it out myself, albiet with the wisdom gained from you awesome folk. I used fastboot to push the 6.0.1 boot and system images from this thread, and things seem back to normal. I haven't rebooted the watch yet, since I didn't load the 6.0.1 recovery image (the only part of the watch that had worked since the problem started), and I'm not sure if I'm going to have the problem reoccur once it does reboot. If anyone has insight on how to best proceed given the steps I've taken so far, it'd be greatly appreciated.
Click to expand...
Click to collapse
If fastboot flashing boot and system images went well, you can safely reboot your watch. First boot might take a while but it should boot OK.
@ausi
ausi said:
Maybe this can help you:
** For those of you who are interested in the solutions i arrived at (with the help of some good friends) please read my final post @:
https://www.reddit.com/r/hwatch/comm...e_android_man/
Click to expand...
Click to collapse
@ausi, can you please post again the solution, the link doesn't work anymore!!!
I really need it!!!
Please help!!!
I am in the same ****!!!
My watch doesn't work anymore!!!
Thank's for anyone help!!!
C3C076 said:
Flashing system.img using the latest fastboot from the official Android SDK worked just fine for me.
Click to expand...
Click to collapse
This DUDE RIGHT HERE. Did it. This was the missing piece. My fastboot files simply weren't good enough. x!!
Android SDK Platform Tools did the trick for me.
Hello everyone, i'm pretty new to software modding (started again yesterday) but i have successfully customized my previous Nexus 4 with Cyanogenmod in the past and other things thanks to very easy guides online.
Now that the guarantee is void, i'd like to mod my Xperia Z1 Compact.
After a lot of tears and Boot Loops™ i finally managed to install Cyanogen Recovery and Cyanogenmod.
Now i'd like to switch to TWRP, as it provides Nandroid backups, which CMR does not, but i can't find any reliable source for this.
The device doesn't show up in the devices list on their website, so i'm really unsure what to do as i don't want to brick my phone :laugh:
Also pretty much same situation with rooting, there are tons of various ways to root the device but the only tool i'd trust (Flashtool) doesn't allow me to root my phone.
Again i don't know which source to trust or what to do...
Any help would be highly appreciated!
Regards, Daniel
SinusStudios said:
Hello everyone, i'm pretty new to software modding (started again yesterday) but i have successfully customized my previous Nexus 4 with Cyanogenmod in the past and other things thanks to very easy guides online.
Now that the guarantee is void, i'd like to mod my Xperia Z1 Compact.
After a lot of tears and Boot Loops™ i finally managed to install Cyanogen Recovery and Cyanogenmod.
Now i'd like to switch to TWRP, as it provides Nandroid backups, which CMR does not, but i can't find any reliable source for this.
The device doesn't show up in the devices list on their website, so i'm really unsure what to do as i don't want to brick my phone :laugh:
Also pretty much same situation with rooting, there are tons of various ways to root the device but the only tool i'd trust (Flashtool) doesn't allow me to root my phone.
Again i don't know which source to trust or what to do...
Any help would be highly appreciated!
Regards, Daniel
Click to expand...
Click to collapse
Rooting with unlocked BL is easy with adb/fastboot. Just download twrp IMG and copy it to /adb folder, and download SuperSU zip file and copy to phone. Then connect phone in fastboot mode, (power off, hold volume up, and connect cable, release volume when you see blue led), and use fastboot command 'fastboot flash recovery [name of twrp file].img'. Now you have recovery. Reboot to recovery and flash SuperSU.
Twrp download - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827
SuperSU download - https://www.google.com/url?sa=t&sou...euHCzPuwbF5IscvgA&sig2=3urcTF6yAxkoYwUylGydvA
levone1 said:
Rooting with unlocked BL is easy with adb/fastboot. Just download twrp IMG and copy it to /adb folder, and download SuperSU zip file and copy to phone. Then connect phone in fastboot mode, (power off, hold volume up, and connect cable, release volume when you see blue led), and use fastboot command 'fastboot flash recovery [name of twrp file].img'. Now you have recovery. Reboot to recovery and flash SuperSU.
Twrp download - http://forum.xda-developers.com/sony-xperia-z1-compact/general/twrp-3-0-1-amami-t3350827
SuperSU download - https://www.google.com/url?sa=t&sou...euHCzPuwbF5IscvgA&sig2=3urcTF6yAxkoYwUylGydvA
Click to expand...
Click to collapse
@levone1 Thank you very much! Everything has worked flawlessly =)
Hi guys. I already flashed the twrp on this thread but; how can i flash another recovery? Do i need to just flash it again the same way i flashed the first recovery? Will it overwrite the old one automatically? Thanks for the answer. I'm just new to this so i just want to make sure.
Maximuous said:
Hi guys. I already flashed the twrp on this thread but; how can i flash another recovery? Do i need to just flash it again the same way i flashed the first recovery? Will it overwrite the old one automatically? Thanks for the answer. I'm just new to this so i just want to make sure.
Click to expand...
Click to collapse
yes. you probably want to flash it in flashmode or with flashfire, ive broken my recovery a couple times now and got it to work again. flashing a recovery image will wipe the recovery partition eg the previous rec
So I unlocked my bootloader when running Lolipop and then flashed H81520A_00.kdz using LG UP. Now I have what I think is a stock Marshmallow with no root and no custom recovery. I've been trying to flash TWRP and all the guides say pretty much the same thing. So I use adb to boot into bootloader, then try and flash an image from the TWRP website and everything seems to go well however every time I try to boot into recovery I get the same dead droid with ! in a red triangle. I read on the TWRP website that the images I've been trying to flash require 2.8.4 but I can't find it available for download anywhere.
I've basically being going in circles and repeating pretty much the same actions over and over for hours now. I'm sure I'm making a simple newbie mistake but I can't figure it out. Any assistance would be greatly appreciated.
dave852 said:
So I unlocked my bootloader when running Lolipop and then flashed H81520A_00.kdz using LG UP. Now I have what I think is a stock Marshmallow with no root and no custom recovery. I've been trying to flash TWRP and all the guides say pretty much the same thing. So I use adb to boot into bootloader, then try and flash an image from the TWRP website and everything seems to go well however every time I try to boot into recovery I get the same dead droid with ! in a red triangle. I read on the TWRP website that the images I've been trying to flash require 2.8.4 but I can't find it available for download anywhere.
I've basically being going in circles and repeating pretty much the same actions over and over for hours now. I'm sure I'm making a simple newbie mistake but I can't figure it out. Any assistance would be greatly appreciated.
Click to expand...
Click to collapse
Ensure you have the oem unlock active (see screenshot)
When flashing twrp use the latest one available
1. Boot into bootloader
2. Use
fastboot boot twrp.img
(replace twrp.img with the real file name you downloaded)
3. Then copy the twrp.img to your device while in twrp
4. Flash the twrp.img with twrp to the recovery partition (choose the button at the bottom named image to show the copied image)
5. done
.
Sent from my LG-H815 using XDA Labs
Thanks for this guide. Fastboot loading the image and then flashing the image worked. It's kind of annoying how little this method is publicised although maybe the fault lies with my ability to use Google.
Anyway, thanks again, I know a post just saying that isn't useful and there's a thanks button but I am grateful for your assistance.
dave852 said:
Anyway, thanks again, I know a post just saying that isn't useful and there's a thanks button but I am grateful for your assistance.
Click to expand...
Click to collapse
Saying thanks this way is fully ok
( clicking thanks too )
Glad that I could help you out
.
Sent from my LG-H815 using XDA Labs
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
bdsuser said:
I have a brand new Pixel XL from Verizon that I received today and was successful in unlocking. However, I tried to root and now I am stuck on bootloop. I cannot post in DEVELOPMENT because I haven't posted here in years (haven't had ANDROID in a while). Can anyone help? I am able to access via fastboot (I believe) but I must be flashing the wrong images. I don't want to brick this nice new day-old device. I have been at it for 5 hours via research on my own, but now I am looking for someone that can help me via P.M. or what it may take. I really want to get back to enjoying this device! Thanks in advance!
Click to expand...
Click to collapse
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
1. Download a ROM. A stock version is probably in the forums somewhere if that's what you want.
2. Download TWRP image and zip from the TWRP thread.
3. Download SuperSU from the SuperSU thread.
4. Download a vendor image. There's no "official" vendor image thread AFAIK, but you can grab one from the Pure Nexus rom thread. NMF26V is compatible with all 7.1.1 ROMs & stock.
Now you have two options:
Fast: Put the ROM, TWRP(zip only), SuperSU and vendor image on USB flash drive, then connect the USB 3 to USB C adapter to your flash drive. Don't connect it to the phone yet. An external HDD/SSD should also work if that's all you've got.
Slow: While in TWRP(Instructions below) push the ROM, TWRP(zip only), SuperSU and vendor image files to your phone through ADB with "adb push C:\file_path\ /sdcard/" sans quotes. You will need to do this for each file, or alternatively push a folder containing the four files. adb file transfer is very slow.
5. Boot your phone to the bootloader, and connect it to your computer. This can be achieved by holding volume down and power from an off state.
Note: If your device is still bootlooping you won't be able to get to the bootloader. Hold volume up and power until the device shuts off to get out of the bootloop temporarily, then boot to bootloader.
6. In a command window, "fastboot boot twrp.img"
7. Connect your flash drive to your phone if you chose that option, or push the files through adb if you chose that option
8. Flash TWRP zip, ROM and vendor image. STAY IN TWRP
9. Return to TWRP's home screen > advanced > file manager. Scroll down until you see 'fstab.marlin'(in the root '/' directory). Tap on 'fstab.marlin' and delete it. Skipping this step means SuperSU won't install.
10. Flash SuperSU zip, reboot to system and you're done.
SDK
TonikJDK said:
Read the third post in the thread below to get set up and back to stock. Then we will work on root. If you tried to root and you bootlooped it then you used the wrong SU.
https://forum.xda-developers.com/pixel/help/stupidly-bootloop-help-t3554242
Click to expand...
Click to collapse
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
bdsuser said:
Just thought I'd update you...And I know I sound like I have no idea what I'm doing but traditionally I've never had issues like this But I am trying to get ADB to show the flash-all command. The one I have installed doesn't show that feature so I can't follow the tutorial. If you have a direct link to what I may be missing I would appreciate it otherwise I will update you once I figure it out.
Click to expand...
Click to collapse
The link to the proper adb and fastboot are in the post i pointed you to.
Help with root and TWRP
TonikJDK said:
The link to the proper adb and fastboot are in the post i pointed you to.
Click to expand...
Click to collapse
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
bdsuser said:
Thanks for your assistance. I now have root installed and I think I'm good except for one thing. I keep thinking TWRP is installed but for some reason when I reboot to bootloader, then select reboot recovery mode, it takes me to android recovery. I am used to recovery taking me to TWRP. I know TWRP works but I feel like I'm temporarily flashing it each time or something. I even installed the twrp app and I see I can flash zips that way, etc, but I wanted to know if you knew how to make the phone boot to TWRP in recovery? Or is that necessary?
Click to expand...
Click to collapse
I dont do it that way on this phone. TWRP and SU are modifying the same parts of the phone, and there are cases where it could conflict. Rare, not a big deal, but since i don't need TWRP installed i don't.
To install it ypu first boot to it.
Fastboot boot twrpFilename.
Then from within TWRP you install the TWRP zip.
Make sure it is TWRP RC1
All set
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
TonikJDK said:
You are most welcome. I don't ROM so I don't know what kernels work with what roms for sure. But my understanding is that they are all pretty universal. I run stock with Franco.
Other than that i dont mod much. Ad blocker, black themes and a few adjustments to Franco.
Click to expand...
Click to collapse
Perfect! Thanks yet again. Have a great remainder of the day!
bdsuser said:
Thanks again for your help. I am running pure ROM as I mentioned and I seem to like it. Do you K or if Franco works with Pure or do you have a suggestion on a good rom/kernel? Is there anything else that you can suggest I should be using with the new phone? I remember there used to be tools that you could install that allowed you to customize the system even further but the name escapes me. . Is there anything like that or even a theme tool which is a must have when you are rooted and running custom roms? No big deal if not. Very happy with where I stand now. Really appreciate you getting me back up and running!
Click to expand...
Click to collapse
Im running pure and elementalx with excellent results.
?Tapped from my pure pixelXl?
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
bdsuser said:
have you ever seen an issue where the phone boots to twrp even though everything was working fine? It starts happening if I do a restart. Then no matter what it boots into TWRP unless I wipe again? I believe it's happening after I flash root but I'm going out of my mind with trial and error. Any help would be appreciated.
Click to expand...
Click to collapse
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
noidea24 said:
HELLO!!! I understand any frustrations you may be having, as the pixel devices have changed a good bit for us as far as development. Anyways. I'm just going to throw some knowledge out there, then proceed to help get you up and running!
You couldn't post in the development section because of your post count, but even if you could, it would have been in the wrong section and it would have been removed, or moved to the questions section.
Also, I see someone has pointed it out earlier, but I'll say it again just to make sure everything is clear. The command you were running "fastboot boot TWRP.img" only boots TWRP temporarily. You are suppose to have two files, one IMG file and one zip file. You boot the IMG file, then once you're in TWRP, you flash the zip file, then reboot to recovery and you will have installed TWRP properly.
With root, flashing wrong files or using the outdated root method will cause boot loops. The correct way to root (again already been said) is the get TWRP up and running, delete the fstab file (see earlier post) then flash SuperSU and reboot. Just throwing this out there Incase someone comes across it, if you manage to boot loop your device due to to rooting, you can fastboot flash franco's kernel and it will fix the bootloop (,but you won't have root) this isn't the correct way to fix it, but it will get you back up and running without downloading the large factory image.
***About to edit this post to continue giving more info***
Here is a correct guide and good template to get you running.
start by flashing a clean factory image, then let it boot and get it set up.
Reboot to fastboot, fastboot boot TWRP IMG then flash TWRP zip using the latest versions (RC1 is latest, pm me for more info).
Reboot the phone to recovery to ensure TWRP stuck.
Go-to advanced, file manager in TWRP and find the fstab.marlin file and delete.
Then you can go ahead and flash the latest SuperSU (I use 2.79 sr3) and when it's done reboot to system and verify root.
After rooting you can go ahead and flash a kernel if you want, I use elemental which you can flash in TWRP, but see the kernel instructions prior to flashing.
Reboot and you have a nice stock ROM with root and kernel.
For flashing Roms, kind of follow the same template, most Roms require you to flash part of or the whole latest factory image.
If your on a clean install, go ahead and install TWRP as mentioned above.
Then use TWRP to install whatever ROM you want per ROM developer instructions.
Side note, some Roms replace the TWRP with cwm or stock recovery, so it's always nice to flash the TWRP zip after flashing a ROM.
After flashing ROM, boot to system to make sure all is well, then boot back to recovery and follow instructions above for root/kernel.
As far as the problem you're having now, it usually comes from flashing outdated SuperSU images. Do a search for 2.79 sr3 and use it to root (pm me if you need help)
You might have to start clean one more time, And flash factory image.
Click to expand...
Click to collapse
There is absolutely no need to delete the fstab file anymore. That only needed to be done when TWRP was still alpha 2, and almost three versions of su earlier.
ALL roms replace TWRP with stock recovery unless you are using lineage then you will get Cyanogenmod recovery, so reflashing TWRP before booting into system is a must.
If you are flashing root and or custome kernel and end up in a bootloop, flashing the stock boot.img to both slots via:
'fastboot flash --slot _a boot boot.img'
'fastboot flash --slot _b boot boot.Img'
will fix the issue and you will be able to boot up just fine. Again you will have to reboot into TWRP from the bootloader and reflash the zip. When you are done flashing the boot.img's you might as well just
'Fastboot boot TWRP-file.img'
Then install the zip!