Develop Bugs

Any way to save data on a Nexus in a bootloop?

I have a Galaxy Nexus that after updating is stuck in a boot loop just recycling the Google logo. There is no ADB access as a result.
Is there anyway I can save my photos? Thanks!

You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data

Like Eddy said. Via fastboot, boot up CWM, either you have it flashed or not.
From CWM, you can access the phone via adb over USB.
In a "adb shell", you can .tar.gz up the stuff you like (or your entire /sdcard). Afterwards you can "adb pull" that off the phone.
Requires quite a bit off commandline, but it's not hard, just cumbersome. If your data is important enough, it's definitely worth it.

EddyOS said:
You should be able to do is using fastboot to get into CWM - you can then mount the sd card and copy off your data
Click to expand...
Click to collapse
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...

It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?

efrant said:
You can't mount /sdcard on a Galaxy Nexus.
Like josteink said, boot up CWM, open a command prompt on your computer and type: adb pull /sdcard or adb pull /data/media
That's it. This will pull all your data stored in /sdcard (although I believe it will not keep the directory structure in place). As well, keep in mind that file transfers over adb are very slow, so it may take a while if you have a lot of data...
Click to expand...
Click to collapse
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off

Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
Correct. If your bootloader is locked, you're out of luck. Unlocking wipes everything.

EddyOS said:
You can, just not as USB Mass Storage. Mount it in CWM then use ADB to get your data off
Click to expand...
Click to collapse
Once you boot up CWM, you have adb access to the files on your device. Not sure what "mount" you are talking about, but I have never had to do anything to get files off/on the /sdcard directory other than boot up CWM or my ROM.
Sent from my Galaxy Nexus using Tapatalk

Spinstorm said:
It's not had CWM Installed. I assume that the process of unlocking the bootloader to install CWM would wipe the phone so that wont work?
Is that correct or am I mistaken?
Click to expand...
Click to collapse
You are not mistaken. In that case, try booting to the stock recovery and use the adb pull command.
Sent from my Galaxy Nexus using Tapatalk

Boot loop
If you are having difficulty with boot loop, pull the battery. I had the same issue with my N1 didn't wipe dalvik cache after an update. And because of the loop couldn't get the timing for fastboot as the bootloop was not giving an indication of when the keypresses would activate the bootloader.
If you are unrooted and stock then try this:
Put device into the bootloader by holding down Vol Up + Vol Down + Power
use your volume buttons to change options next select (with power button) the fastboot option, after use the ADB instructions from the more knowledgeable members (ADB is somewhat cumbersome.... but it works and has saved my bacon) After wards using the Bootloader you should be able to resore to factory settings and reload your info after.
If you are Rooted with a custom bootloader and rom
same as above to get to bootloader, but then wipe your cache, and dalvik cache. Reflash latest ROM and Gapps. You shouldnt lose anything.
Good luck bud.... your Nexus isn't dead.... only in a Coma.... or a political promise...
J

You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846

danger-rat said:
You can perform a complete backup via adb without root access. You would have to do this from recovery...
http://forum.xda-developers.com/showthread.php?t=1436846
Click to expand...
Click to collapse
Have you tried and gotten that to work in recovery? Although I haven't tried it, I don't think that works in recovery. It is a feature of ICS, so I'm pretty sure you need to be booted into your ROM for it to work.
Sent from my Galaxy Nexus using Tapatalk

sos lge960
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency

bibi019 said:
i have one nexus4 lg e960 enter only in recovery mode or clockrecovery mode
but i can't update my rom in to the internal masse storage
how i mount sd card to performe update rom via zip file
command with adb or via menu of recovery clockworkmode
yours
[email protected]
emergency
Click to expand...
Click to collapse
My guess is this question is more appropriate for the nexus 4 forum
Sent from my Galaxy Nexus

Nooooo, necrobumping is fine, since he has the same issue, and this is the first hit on Google... even though he's on a different device. /s
Sent from my Nexus

Hey, I'm running to a similar problem with this guy.
I stupidly reformated my system files without having a rom on my internal sd.
The question is that I'm reading that I can use the adb to push files in but I'm just new to the whole adb.
How would I get my computer to use the adb?
Sorry for such a noob question -_-;
Edit: So it seems from looking around and reading other forums and faq's that I need to have the phone for the adb to be installed.
Is there away around that so that I can access the adb?
Edit2: Nevermind. Fixed it with a toolkit. Sorry to spam

Mount usb in fastboot/recovery.

Hi guys. I wanted to try a new rom and put a corrupted .zip on it. Anyway long story short. i have a nandroid backup on my computer and I want copy it on the phone but I wiped my rom and cannot get it on. Can I use fastboot to access the sd card? I don't want to flash a stock image as i will lose all my photos etc.

Could you not just connect it to your pc, copy the rom over and run it in CWM?
You can't mount the phone in CWM but if you can boot it you should be able to use MTP to transfer the rom across?

I wiped so no rom to boot into

From the Q&A section: [Q] mount usb on recovery ?
Does flashing the system.img from a factory image really touch the user data?

I didn't think so but I am not 100% sure! If it doesn't adb/fastboot the stock images onto the device.

It does wipe all of the sd card as I have already tried it a while ago. Its bad for your photos. Especially ones of my newborn son.

robt772000 said:
It does wipe all of the sd card as I have already tried it a while ago. Its bad for your photos. Especially ones of my newborn son.
Click to expand...
Click to collapse
That sucks. Thanks for clearing it up.

robt772000 said:
Hi guys. I wanted to try a new rom and put a corrupted .zip on it. Anyway long story short. i have a nandroid backup on my computer and I want copy it on the phone but I wiped my rom and cannot get it on. Can I use fastboot to access the sd card? I don't want to flash a stock image as i will lose all my photos etc.
Click to expand...
Click to collapse
Boot up CWM and then pull the files. Step-by-step:
1) Download CWM, rename it to cwm.img and place it in the same directory as your fastboot executable;
2) Reboot you device into fastboot mode and connect to your computer;
3) Make sure your computer sees your device by typing: fastboot devices
4) Boot CWM by typing: fastboot boot cwm.img
5) Pull all the files from /sdcard by typing: adb pull /data/media
6) Done.
Note: I do not think the directory structure is preserved doing it this way, so all the files will end up in one directory.

Thanks for posting these instructions on booting into CWM. I had my Galaxy Nexus crash and then it was stuck in a boot loop. Everything on the phone is stock 4.0.2 and the bootloader is still locked. So when I do a 'fastboot boot cwm.img' it fails because of the locked bootloader. If I attempt to unlock the bootloader with 'fastboot oem unlock' my understanding is it will wipe my user data. Not good since what I'm after is getting my files off the thing prior to resetting it.
Do you know of a way I can mount the internal storage via adb or other means and get my files off?
Thanks,
Joel

deyoung said:
Thanks for posting these instructions on booting into CWM. I had my Galaxy Nexus crash and then it was stuck in a boot loop. Everything on the phone is stock 4.0.2 and the bootloader is still locked. So when I do a 'fastboot boot cwm.img' it fails because of the locked bootloader. If I attempt to unlock the bootloader with 'fastboot oem unlock' my understanding is it will wipe my user data. Not good since what I'm after is getting my files off the thing prior to resetting it.
Do you know of a way I can mount the internal storage via adb or other means and get my files off?
Thanks,
Joel
Click to expand...
Click to collapse
Unfortunately you are out of luck in that case. This is why I always recommend that you unlock (and leave unlocked) the bootloader right out of the box - even before booting Android for the first time. Make it a habit on any Nexus device you have, and you will never run into these issues.
As for your problem, if you can't boot into Android, and you did not have CWM flashed as your recovery, there is nothing you can do unfortunately.

Thanks for confirming what I suspected. The lesson about unlocking and installing CWM out of the box is one that I learned today.

deyoung said:
Thanks for confirming what I suspected. The lesson about unlocking and installing CWM out of the box is one that I learned today.
Click to expand...
Click to collapse
Just unlocking is important. Flashing CWM, not so much. Even if you do not have CWM installed, you can always boot if from your PC.

U
deyoung said:
Thanks for posting these instructions on booting into CWM. I had my Galaxy Nexus crash and then it was stuck in a boot loop. Everything on the phone is stock 4.0.2 and the bootloader is still locked. So when I do a 'fastboot boot cwm.img' it fails because of the locked bootloader. If I attempt to unlock the bootloader with 'fastboot oem unlock' my understanding is it will wipe my user data. Not good since what I'm after is getting my files off the thing prior to resetting it.
Do you know of a way I can mount the internal storage via adb or other means and get my files off?
Thanks,
Joel
Click to expand...
Click to collapse
You can use adb to pull the content of the sdcard partition. I've done it before. I think I used 'adb pull /mnt/sdcard'. It may just have been 'adb pull /sdcard'. If it doesn't work, try the adb remount command first.

mwalt2 said:
U
You can use adb to pull the content of the sdcard partition. I've done it before. I think I used 'adb pull /mnt/sdcard'. It may just have been 'adb pull /sdcard'. If it doesn't work, try the adb remount command first.
Click to expand...
Click to collapse
That only works if you can boot into Android (or CWM). If your device cannot boot, it's not going to be of much help...
Sent from my Galaxy Nexus using Tapatalk 2

You can't mount internal storage from CWM anyways
Sent from my Sprint Galaxy Nexus CDMA using XDA

AZ FadeOut said:
You can't mount internal storage from CWM anyways
Sent from my Sprint Galaxy Nexus CDMA using XDA
Click to expand...
Click to collapse
What are you referring to? The point is you can easily access /sdcard while booted in CWM so you can copy all the file you want to your PC, but you need to be booted into CWM (or your ROM). The Galaxy Nexus does not support USB Mass Storage at all in any case.
Sent from my Galaxy Nexus using Tapatalk 2

efrant said:
That only works if you can boot into Android (or CWM). If your device cannot boot, it's not going to be of much help...
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ha, didn't realize this thread was bumped from 6 months ago. I saw flashing of a custom rom in the first post and made too many assumptions. Guess I need to read more when using the xda app.

Thanks to everyone who provided helpful info.
Is the nature of format that's performed by the oem unlock simple enough that it would leave the file contents intact, allowing them to be recovered by an undelete utility of some kind?
Frustrating that the files are likely on the storage and not corrupt, but I am unable to get at them.

How to push files in fastboot or Recovery?

Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?

Adb push in a custom recovery or you can reflash your ROM
Sent from my Galaxy Nexus using Tapatalk 2

JB has been known to get stuck at "google" for 10min or so. Did you wait long enough?
good day.

RevengeFNF said:
Hello,
One friend of mine have flashed franco kernel, but problably the kernel was corrupted and now he get stuck at the google logo.
How can he push a new kernel to the phone memory to flash it in the recovery?
Click to expand...
Click to collapse
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
Confirmed working, and a BAZILLION times faster than the chrome browser.

Zector said:
Confirmed working, and a BAZILLION times faster than the chrome browser.
Click to expand...
Click to collapse
??? chrome browser can flash roms?
10chars

Does it work with CWM?
Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
I tried this and it said "insufficient permissions for device" in ADB. My phone randomly rebooted and gets stuck on the boot logo, but everything on my sdcard got deleted. I have a Verizon Galaxy Nexus if that helps

If it's only the kernel causing problems, the easiest would be to run "fastboot flash boot <name of boot.img here>" from fastboot?(the original boot.img from the rom he's using would be found inside the zip file)
But if you screwed something else up in the process, you may need to flash the entire rom again from the recovery. If you are using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer, and if you are using twrp, they have an option to sideload(under advanced), where you can connect you phone to your pc and run "adb sideload <name of rom.zip file here>" and it will install it right away.

mortenmhp said:
using cwm recovery, I believe it allows you to mount storage, so you can just move the rom file from the computer
Click to expand...
Click to collapse
this will not work, not with cwm nor with twrp, at this point; likely, it will never work as we don't have removable storage.

Then just use the sideload, it works quite well for me.

mortenmhp said:
Then just use the sideload, it works quite well for me.
Click to expand...
Click to collapse
Or just 'adb push rom.zip /sdcard/', or if that doesn't work, 'adb push rom.zip /data/media'.
Sent from my i9250

in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave

GruiaNovac said:
in my case TWRP didn't do so good with adb,
I think the recovery devs should have ADB in mind first of all. without ADB ur one foot in the grave
Click to expand...
Click to collapse
adb works fine with TWRP if you have updated adb drivers/adb daemon.
guess fastboot flashing images also eludes you.
so no, you're not in the grave.
*note* thanks for necroing a thread from December.

No, in bootloader its fine.
And apparently (if It wasn't a fluke) I think i booted normally , and having no rom it just stood there, and adb worked.
that saved me
TWRP dissapoints . have to look for replacement

stuck in recovery
so Im stuck in a similar situation
before installing a ROM which instructed to wipe the device, i did so, in fact i over did it.. wiped data/cache/davlik/system and internal storage
the same storage which had the ROM that i was supposed to install after wiping it.
I felt very dumb, but now stuck with the bootloader / fastboot / and TWRP recovery .. the TWRP recovery version i have HAS the adb sideload feature
which i've tried to install the Cyanogen ROM using ./adb sideload filename.zip , which hasnt work for Cyanogen but worked for the GApps after that ( I thought that was kinda weird).
the sideload command goes thru the sending of the entire ROM to the phone, but it never installs correctly..
NOW im stuck
any suggestions or help on how i can do it with what appears to me to be as fastboot / adb side load / and recovery options"??
thank you very much in advance
=====
update
=====
solved my problem... mounting the partition turns on full ADB to push the files onto the drive and install them using the recovery software

Petrovski80 said:
1) boot into bootloader
2) start recovery from bootloader
3) use adb push to copy a ROM to the /sdcard
4) flash it
Click to expand...
Click to collapse
you just saved my life... and my phone

[Q] phone failed while updating TWRP and now i cant access RECOVERY, only HBOOT.

Hey!
So here's the deal:
I'm running LiquidSmooth ROM (KK Version) and I was trying to update the ROM to the newest Lollipop version, but it kept failing. No big deal, i nandroid backed up, and then did a total wipe and tried again. Failed.
Okay, maybe my TWRP recovery was out of date, i tried updating it using the official TWRP app...
then everything went wrong. The install failed and now whenever i ask my phone to go into recovery mode, it sends me into HBoot. I've been trying for 3 days to figure this out, and i cant, so any help would be greatly appreciated.
Im not incredibly well versed at this stuff, so it might have to be a dummy's guide.
in the meantime, here are the details...
When i try to flash ANY custom recovery using ROM Installer app, here is what the error message says:
"COMMAND:
flash image recovery /storage/emulated/legacy/romtoolbox/recoveries/openrecovery-twrp-2.7.1.0-m8.img"
"OUTPUT:
/dev/block/mmcblk0p34: write error: No space left on device
3+0 records in
2+0 records out
1024 bytes transferred in 0.004 secs"
And when i try to reboot into RECOVERY (and it sends me into BOOTLOADER instead), here is the information it gives me:
*** TAMPERED ***
*** UNLOCKED ***
M8_UL_CA PVT SHIP S-ON
HBOOT-3.18.0.0000
RADIO - 1.14.21331931.LA02_2G
OpenDSP - v32.2.2-00542-m8974.0213
OS -
eMMC-boot 2048MB
JUNE 16 2014 18:47:55
FASTBOOT USB
thank you so much in advance. i have NO idea what happened... i know the fact that i have S-On might have something to do with it, but i dont have access to a PC, only MACs and i can't use the Sunshine app because i'm already running a custom rom. What can i do?

The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify

If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.

I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache

Magnum_Enforcer said:
If you can't boot into Android you'll need to fastboot flash your recovery. The one you're using is rather old (I believe 2.8.3.0 is the most recent version). You'll need to download the recovery img file and place it in your ADB/Fastboot folder on your computer. Connect your phone and computer in Fastboot USB mode. Open up a command terminal and type fastboot flash recovery nameofrecovery.img and hit enter (enter the actual recovery file name and not nameofrecovery). The new recovery should then be flashed to your phone, unless you get an error in the terminal on your computer.
As stated above, Flashify works great for flashing recoveries to your phone, but it only works if you can boot into the Android OS.
Click to expand...
Click to collapse
I'll try to flash it from bootloader! Could you tell me how to place the recovery img file into my adb folder? Thank you!!!

nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?

jball said:
The thing I noticed is the block that's indicated is not the right one,if you look at the pic below the recovery block is mmcblk0p43.
I would download the custom recovery you want and manually input it "dd" method
Or
Download the custom recovery img and use an app called Flashify
Click to expand...
Click to collapse
What is DD method? Thank you so much for your help

karmendc said:
Oh damn thank you!!! Is this the exact code/command I'll use in Terminal on Mac OS or does it differ since it's not a PC?
Click to expand...
Click to collapse
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk

nkk71 said:
Don't dd
Don't flashify
Just install mini adb+fastboot for Mac and do the commands mentioned. It's pretty much the same for Windows, Mac and Linux.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)

karmendc said:
What is DD method? Thank you so much for your help
Click to expand...
Click to collapse
dd is a method using a terminal emulator on your device.
The screenshot is from the twrp website and the "dd" method is described as a working method if in fact you can boot to the OS (SuperSU is needed)

jball said:
Why do you think I've mentioned the other methods.
Not everyone understands how to use fastboot like we do.
If he has a bootable OS than Flashify will work just fine (I wouldn't recommend an app that I haven't tried/used myself)
Click to expand...
Click to collapse
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk

nkk71 said:
Because flashify, TWRP manager, ROM manager, etc apps expect the proper device info in build.prop
and will then dd whatever partition it sees fit... In this case, it thinks it's an m7
fastboot flash does not.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)

jball said:
I read what you've stated already.
I agree the sure fire way is fastboot .
Easy for you
Easy for me
But maybe not so easy for some.
As long as the OP gets what he wants is all I'm in here for(not a long drawn out tutorial as those already exist)
Click to expand...
Click to collapse
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk

nkk71 said:
Sorry if my answers are short and not in much detail, I'm typing on the phone... I prefer a full keyboard
But dd is not something I easily recommend (much more difficult than fastboot flash)
and if you check the build.prop of the ROM mentioned by the OP you'd see it's not entirely proper
I've seen enough bricks due to "flashy apps" and one-clicks (no offence intended to any)
fastboot at least does some checking of what is being flashed and where, so that is what I personally recommend.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for the more detailed information.
Small keyboards blow for sure.

@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.

gazzacbr said:
@nkk71 warning is quite valid
dd used correctly, but ideally from a script, is very useful and powerful.
dd is also affectionately know as 'disk destroyer'
just one small typo, or worse getting the input and output reversed, can really make a mess.
it will write more or less anything to anything including your boot sector and data.
just saying.
Click to expand...
Click to collapse
Thank you for the second opinion kind sir.
http://www.youtube.com/watch?v=JUCM_tJaNHU
Here is a short video on how to input the "fastboot flash recovery recovery.img " command once you have drivers correctly installed and the img file in the proper location .
Now this video is from a tablet to my HTC one m8 and not from a
PC/Desktop as it's over obvious.
Just like all other videos I don't show how to "easily" set up the drivers for fastboot (oh that's cause you don't need drivers to adb or fastboot from a tablet to a phone).

nkk71 said:
I would seriously stay away from flashing recovery using apps, they rely on build.prop to identify your device, and if that's not correct the recovery will go to the wrong partition (which seems what's going on in your case because mmcblk0p34 is the recovery partition on the HTC One M7, not HTC One M8 !!!!
just flash it in bootloader (FASTBOOT USB):
Code:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
Click to expand...
Click to collapse
Okay so i finally tried flashing it using Terminal/FASTBOOT... I downloaded the latest TWRP recovery for GSM, placed it in my adb/fastboot folder...and typed in the command and it came up with an error. Here are the screenshots. Help? Im at my wits end.... thank you in advance!

wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.

karmendc said:
wait, i got it! flashed!! I was in the wrong directory, i guess. So now i got into the correct directory, but the phone still wont go into recovery when i reboot. :crying:
Sigh. okay, back to square one.
edit:
and great. i think that "erase cache" command unmounted my internal storage...because now i get no phone signal and my local storage cannot be found.
What. is. happening.
Click to expand...
Click to collapse
1) you're on hboot 3.18 so that would indicate you firmware (the OS- line or version-main from a fastboot getvar all) is still 2.xx.xxx.x version, so yes, you're going to have signal and wifi problems, as mentioned in the various ROM threads you need matching firmware to the ROM you're running.
2) this could also be the reason it's not entering the recovery, you could try an older version of TWRP, and make sure MD5 checks out on your download, a corrupt download could also be the reason
3) the "fastboot erase cache" doesnt affect your internal storage or anything, it just wipes the cache which will get rebuilt as needed
4) missing/not mounted internal storage, is a common issue on Android 5.x (not only HTC, many devices), download a terminal emulator to your phone (or alternatively open an abd shell), and do the following commands:
Code:
su
restorecon -FR /data/media/0

Pixel xl in twrp with no OS installed?

Hello to all. I have just unlocked bootloader, installed twrp and su. After everything booted up properly, I went to install an adblocker zip file, however once it booted into twrp it had no download folder, as well as when I went to reboot system it told me I had no os installed.. I'm a bit confused as to what to do now.. My apologies for clogging the thread if this has been answered before..
Edit: do I adb side load an image file or OS? I'm afraid of bricking this phone as I don't know how to continue from this point..

Which guide did you use to do all of this? I will help us understand where you started

Mrbobrowitz said:
Which guide did you use to do all of this? I will help us understand where you started
Click to expand...
Click to collapse
Hi thanks for the reply. This link right here:
http://www.androidsage.com/2016/11/...timate-guide-root-twrp-and-bootloader-unlock/
Steps I followed:
1 unlocked bootloader
2 Download the below files TWRP and Root files for Google Pixel & Pixel XL
Official TWRP for Pixel phones → Download |
Files: twrp-pixel-installer-sailfish-3.0.2-0-alpha1.zip 7.6M
twrp-3.0.2-0-alpha1-fastboot-sailfish.img 25M
Flash SuperSU 2.78 SRF4 → Download | File: SR4-SuperSU-v2.78-SR4-20161115184928.zip
Twrp install instructions:
Step 1: Download the TWRP recovery and latest SuperSU zip file for your Google Pixel and Pixel XL devices. There are 2 TWRP files with .zip and .img extensions. You will need both. You don’t need to extract the files, just place all the files on your PC as well as your Android phone’s internal storage where you can easily locate it.
Step 2: Make sure that you setup ADB and Fastboot on your PC and gone through all the prerequisites from above.
Step 3: Now plug in the Pixel device to the computer and open a command prompt or terminal on your PC to the window where TWRP.zip file is located. (See above to know how to open cmd)
Step 4: Boot your Android device into the bootloader or Fastboot mode. To do so, issue the following command through cmd or terminal. You can also manually boot into it using the hard key combination like Power+Volume Down while the device is turned off. Meanwhile, use code:
adb reboot-bootloader
Step 5: Now issue the following command in the command prompt to check your device connectivity
fastboot devices
Step 6: Now issue the following command to temporarily boot up the TWRP image.
fastboot boot path/to/twrp.img
Note: If you have installed our recommend quick 15 second ADB & fastboot installer, you do not need to insert the complete file path. Simply go to where the TWRP image file is and issue command “fastboot boot twrp.img” Otherwise, note that “path/to/” is the actual directory for the TWRP image file. Use fastboot boot and not fastboot flash and that the file you are booting is not the zip file.
Simply After that, TWRP will be accessible to you no matter which active partition slots are being used.
Step 7: After that fastboot command, you will be rebooted into a temporary TWRP recovery interface. To make it permanent, use the TWRP interface to navigate to and install the TWRP.zip file. This is just like using TWRP to flash custom ROMS and SuperSU.
Once the installation completes, you can now enjoy your new firmware. Alternatively, while, on Mac OS, you can issue “./fastboot boot path/to/twrp.img” command or on Linux type “sudo fastboot path/to/twrp.img” to flash the TWRP. For detailed tutorial and alternate methods to flash the TWRP recovery, click here.
Now it’s time to root your Google Pixel with latest SuperSU 2.78 SR4.
How to root :
Place the latest SuperSU 2.78 SR4 package onto your device’s internal storage or SDcard.
Boot your device into the custom TWRP recovery and tap install. For that, turn off your device completely and hold volume down and power buttons for a few seconds.
Once into TWRP tap the install button and select the SuperSU file.
Swipe the confirmation action below to start flashing.
Once done. reboot to system.
You can boot into the TWRP recovery by issuing the following command:
adb reboot recovery

There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!

I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device

Smallsmx3 said:
I wouldn't waste your time. Just flash the factory image and start all over. You managed to wipe the Rom off your device
Click to expand...
Click to collapse
Mrbobrowitz said:
There is an alpha 2 for twrp now. I would try installing this and seeing if it works. If not, you can simply flash the latest factory image and "start over". Granted you would lose any data that you might have had not backed up on your device, but youre not out of luck!
Click to expand...
Click to collapse
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?

mazubo said:
Thanks guys, I actually have installed the alpha 2 twrp. I guess my question is how do I proceed? I'm in twrp and my PC does not see the device when typing adb devices.. Within twrp it says no os installed... What do I do here?
So how do I "start over" or "flash factory image" from the state that I'm in?
Click to expand...
Click to collapse
You should be able to boot into fastboot

Smallsmx3 said:
You should be able to boot into fastboot
Click to expand...
Click to collapse
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root

Smallsmx3 said:
I couldn't tell you! I've had it happen to me before a couple times. But yes if you can get into fastboot you should be able to fastboot flash a factory image. Then go and flash TWRP and root
Click to expand...
Click to collapse
Ok thanks. I've been able to reboot to bootloader...

I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!

mazubo said:
Ok, and if that works then flash 7.1.1? Then twrp alpha then root via SuperSU flash?
A side question here is how did I wipe the os/from off the phone? I'm stumped on that one..
Click to expand...
Click to collapse
mazubo said:
I've figured it out via fast boot. The phone is back in action, however not sure how it got wiped initially.. Thanks everyone!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Off the top of my head... Probably selected the wrong "slot" maybe?
Remember on this device there are two locations for the ROM. Slot A and B. If you select the wrong one it will show no OS.
As far as the download folder missing... I know its mute at this point, but that has to do with the FBE (File Based Encryption). Make sure TWRP asks you for your Pattern Password. If you do not have one I would consider setting one. That way you know for fact that the File system will get decrypted properly. Also reports say you may have to reboot TWRP twice to get it to decrypt as well.