Database Develop

[Q] help!! vivid may be bricked?

ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:

gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.

camo_flage said:
So you flashed the rom and it wont boot up now? or you flashed the recovery and it wont boot up now.
Click to expand...
Click to collapse
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on

gabriel1946 said:
ok been dealing with this for the past hour no results.. i recently flashed the twrp recovery just to check it out and wanted to flash a rom on it went to do so and now that i reboot phone it stays on the htc start up screen turns off than back on.. only thing working on it is the hboot, no recovery. although occasionally ill see the twrp start up screen than it turns off and goes white htc... any help is appreciated.. thinking i may have to relock and find the stock at&t ruu??:crying:
Click to expand...
Click to collapse
Fastboot erase cache command will fix this problem. Boot to your bootloader select fastboot usb and run that command.

haha im not too good with computers more of a mobile only tech haha can u explain that please?

gabriel1946 said:
haha im not too good with computers more of a mobile only tech haha can u explain that please?
Click to expand...
Click to collapse
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
---------- Post added at 06:07 PM ---------- Previous post was at 05:54 PM ----------
gabriel1946 said:
the recovery was working i was using jb pacman rom than flashed to i think it was element rom by shadow slayer but once i did that it keeps turning on and off if i try to choose recovery from the hboot it shows the recovery screen for a second than goes to htc screen and turns off and back on
Click to expand...
Click to collapse
Last time this happened there was a script that was running that corrupted the cache partition. That is why erasing cache fixes it.

esloan said:
I assume you are using windows...? Do you have adb installed/working? If the answer to both of these is yes. Reboot your phone to the bootloader (hboot) select fastboot usb in hboot. Open a cmd Window cd to the dir where adb is located. Then run the command in the above post.
Click to expand...
Click to collapse
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start

gabriel1946 said:
adb u mean adbfastbootrecovery? i installed in not sure how to get it working, the command imputing is where im getting lost sorry for my noobness lol appreciate ur help i have my phone on hboot fastboot now connected to my computer ive seen that command imput is shift and right click but i dont get any command window i get normal options.. ive only use command in the run app under start
Click to expand...
Click to collapse
Okay where is your adb file? Ex mine is in a C:/Android. By default if you installed the android SDK the adb files would be in the SDK folders. Any way if you were fast boot flashing a recovery your going to do the same thing just use fastboot erase cache as the command instead of the recovery command. If none of this makes since PM me.

Resolved via PM

HELPPP deleted my internal storage

Ok guys I went to wipe my htc one using twrp and I accidently wiped my internal storage so there nothing on my device to boot up I can get into twrp but I dont have any zips on there to flash I also tried to sideload but adb wont recognize my device which is weird because fastboot works fine I went to bestbuy Walmart radioshack to by an otg cable and try it with flash drive but no one has one so I ordered one from ebay but it will take a week to get it can someone please help with any other sugestions please pleasee I need my phone back

You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.

SaHiLzZ said:
You may have to switch recoveries to TWRP 2.6.3.3 OR 2.6.3.0, and use a windows 7 machine.
Click to expand...
Click to collapse
What will switching recoverys do?

Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?

Novasunshine said:
Did you try "adb push rom.zip /sdcard/rom.zip" while you were on the home screen of the recovery?
Click to expand...
Click to collapse
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4

maxtcee said:
No I tried it while in bootloader mode also I just check I am running twrp 2.6.3.4
Click to expand...
Click to collapse
Try it in recovery and also check to see if the device is being detached while in recovery by typing in "adb devices" in the command prompt.

Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing

maxtcee said:
Nope
If I use htc one toolkit while in bootloader and I fastboot I get my device show up but when I do adb I get nothing
Click to expand...
Click to collapse
So when you type in "adb devices" while in recovery it shows nothing? No device attached? Also what version of windows are you on?

Yea it shows nothing I'm using windows vista

maxtcee said:
Yea it shows nothing I'm using windows vista
Click to expand...
Click to collapse
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still

Novasunshine said:
So no adb in recovery, but fastboot working hmm. So adb devices shows nothing?
Your device is obviously being detected to have fastboot working.
Try adb kill-server to reset adb and then check if it's detectable in recovery, also make sure to mount the data.
Use a different computer if available
Make sure you don't have any tethers installed that would ruin adb like easy tether
Try downloading and reinstalling the adb universal set up drivers.
Try running a RUU if you can
Sorry if i'm not much help I'm still noobish to all this still
Click to expand...
Click to collapse
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude

maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
Click to expand...
Click to collapse
Takes about 1 - 5 minutes depending on rom size also adb wont say anything till its finished
---------- Post added at 05:21 AM ---------- Previous post was at 05:16 AM ----------
maxtcee said:
ok so i updated my adb drivers and i can get adb to recognize i used htc toolkit and adb pushed the the on my revocery but not sure how long it takes for the zip to transfer cause i tried to flash the rom and it says fail cannot open zip
do you know how long it takes to push a rom onto phone?
nevermind i got it flashing rom as we speak thanks for all your help dude
Click to expand...
Click to collapse
Your welcome glad its working finally

[Q] Rooting HTC One M7 with windows 8?

Hey, everyone I'm just wondering if anyone knows if there's a rooting method for htc one m7 with windows 8. i spoke with someone on oneclickroot website or something like that and they told me that there are none so i just wanna confirm or deny that. So if you know can u please share wether htc one m7 can be rooted on windows 8 or not?
thanks

randomlegend10 said:
Hey, everyone I'm just wondering if anyone knows if there's a rooting method for htc one m7 with windows 8. i spoke with someone on oneclickroot website or something like that and they told me that there are none so i just wanna confirm or deny that. So if you know can u please share wether htc one m7 can be rooted on windows 8 or not?
thanks
Click to expand...
Click to collapse
windows 8.1 has a driver problem on a really old hboot 1.44
and it was only a problem for a very few. The phone was updated to hboot 1.54 just weeks after the release of windows 8.1 and it works fine.
If you are on hboot 1.44 and you only have use of a windows 8.1 PC their is a driver hack that will work and get your phone working long enough to update the hboot.
File > http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
Instructions
I repeat this is a REALLY DIRTY solution that may harm your system, personal data, hardware and/or cat.
Here are the steps:
0. Have a Linux or Windows LiveCD just in case something goes wrong
1. Download and extract files from attachment
2. Navigate to the folder corresponding to your system version (x86 = 32-bit, x64 = 64 bit)
3. Right-click franken-usb.bat and click "Run as Administrator"
5. Wait for it to finish and reboot the system. If everything went fine, you will boot your system successfully
6. Install ADB/Fastboot drivers just like on Windows 8
7. Connect your phone in Fastboot mode to your USB 2.0 port and check if it works
8. Enjoy and wait for official fix
How does it work:
It's not any kind of magic - it just replaces Windows 8.1's usbhub.sys and usbport.sys with Windows 8's ones.
Old files don't check for BOS descriptor so Fastboot can work.
Script updated - it should now actually copy the files but please double check if files were copied to C:\Windows\system32\Drivers!
Hope it helps you!
Regards!
Click to expand...
Click to collapse
Everything else is the same
unlock bootloader @ HTCDEV.com
Flash custom recovery
Flash SuperSU for root
flash custom rom for fun

CMD says file is too big when Flashbooting... Help?
First, forgive title error, I know it's Fastboot lol... Wow so I am so close, yet so far away. I have successfully unlocked boot loader. I have downloaded all the necessary files. I have followed You-Tube guides to the word... Yet when I get down to the final steps, errors! I am stuck at this point... On CMD screen, when doing the "fastboot flash recovery twrp.img" it will not work. Kicks back an error that basically says twrp.img is too big and my phone is rejecting the download. Went and found a smaller file that should be small enough, yet still the same error. Please help me! I am so frustrated after hours of working on this. Thanks!!

missmyraj said:
Wow so I am so close, yet so far away. I have successfully unlocked boot loader. I have downloaded all the necessary files. I have followed You-Tube guides to the word... Yet when I get down to the final steps, errors! I am stuck at this point... On CMD screen, when doing the "flashboot flash recovery twrp.img" it will not work. Kicks back an error that basically says twrp.img is too big and my phone is rejecting the download. Went and found a smaller file that should be small enough, yet still the same error. Please help me! I am so frustrated after hours of working on this. Thanks!!
Click to expand...
Click to collapse
can you post the output from fastboot getvar all (minus the serial no. and IMEI)
What recovery did you download and try ...it's critical you get the right file

Thank you!!! Screenshots attached...
clsA said:
can you post the output from fastboot getvar all (minus the serial no. and IMEI)
What recovery did you download and try ...it's critical you get the right file
Click to expand...
Click to collapse
Thank you!!! Screenshots attached...

missmyraj said:
Thank you!!! Screenshots attached...
Click to expand...
Click to collapse
OK you have a t-mobile phone that's a good thing
Boot the phone to the bootloader by shutting it down then holding volume down and hit power
now with the phone in fastboot USB / hooked to the PC
type fastboot devices
you should see your phones serial no displayed
now just type fastboot flash recovery with a space at the end
now just drag TWRP 2.6.3.3 into the command window and hit enter. this will flash twrp
now type fastboot erase cache
followed by fastboot reboot-bootloader
now you can enter recovery and use adb to push or sideload a rom to your phone
Instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
You should note that you windows is not showing the file extensions of your files in the sdk folder that's why you get the error when you rename files twrp.img is actually trwp.img.img
you just can't see it so be careful when renaming files and adding the extensions, their already their just hidden

Thanks!
Thanks so much for your time!! I will give it a shot tomorrow. ?
---------- Post added at 05:45 AM ---------- Previous post was at 05:10 AM ----------
Had to at least give it one more shot before bed, and it worked!! You just rocked my little world, clsA. Thank you so much! Take care.

missmyraj said:
Thanks so much for your time!! I will give it a shot tomorrow. ?
---------- Post added at 05:45 AM ---------- Previous post was at 05:10 AM ----------
Had to at least give it one more shot before bed, and it worked!! You just rocked my little world, clsA. Thank you so much! Take care.
Click to expand...
Click to collapse
Great !! Enjoy your phone

[Q] Nexus 6 stuck in bootloop

Hey sorry guys for being such a newbie here....need some help.
1. Ran the Nexus 6 1 click unroot kit
2. Somehow I screwed it up and now can't get past the teamwin blue screen just keeps popping back up.
3. I have a mac and have watched countless videos on reflashing factory image and nothing seems to be working.
Any ideas?

nickb2005 said:
Hey sorry guys for being such a newbie here....need some help.
1. Ran the Nexus 6 1 click unroot kit
2. Somehow I screwed it up and now can't get past the teamwin blue screen just keeps popping back up.
3. I have a mac and have watched countless videos on reflashing factory image and nothing seems to be working.
Any ideas?
Click to expand...
Click to collapse
Are you familiar with fastboot? If not, go here:
http://forum.xda-developers.com/showthread.php?t=3006500
I don't use Mac so I'm not sure exactly how the commands get typed but you should try:
fastboot format cache
fastboot format userdata

Evolution_Freak said:
Are you familiar with fastboot? If not, go here:
http://forum.xda-developers.com/showthread.php?t=3006500
I don't use Mac so I'm not sure exactly how the commands get typed but you should try:
fastboot format cache
fastboot format userdata
Click to expand...
Click to collapse
So, I tried doing it...on a mac you need to put ./then your fastboot
Here's what I get....
AdminisatorsAir:~ Nick$ ./fastboot format cache
-bash: ./fastboot: No such file or directory

nickb2005 said:
So, I tried doing it...on a mac you need to put ./then your fastboot
Here's what I get....
AdminisatorsAir:~ Nick$ ./fastboot format cache
-bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Do you have the Android SDK installed or minimal fastboot tools?
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Does your device serial number come up when you type fastboot devices?

Evolution_Freak said:
Do you have the Android SDK installed or minimal fastboot tools?
Click to expand...
Click to collapse
So, I had the SDK installed or thought I did...went to tools and then android clicked that and it keeps telling me java runtime environment isn't installed and to please install. I did it 3 times and still nothing when click android to try to get the sdk.

nickb2005 said:
So, I had the SDK installed or thought I did...went to tools and then android clicked that and it keeps telling me java runtime environment isn't installed and to please install. I did it 3 times and still nothing when click android to try to get the sdk.
Click to expand...
Click to collapse
Navigate to the platform-tools folder and open a command window there. Also, if that doesn't work, in the fastboot thread I linked, is a method to install fastboot and ADB system wide. Is that an option?

Well while evolution_freak helps you out, I'd like to chime in and say that I always stayed away from any 1-click anything, as well as any auto ROM/recovery updater.
You never know if you downloaded the wrong file
and then I just imagined hundreds of lines of code pouring into my poor little phone and how it would be screaming inside ):
I've seen lots of hard bricks happen from 1-click packages, learning how to do things the dirty way is more fun anyway!

Evolution_Freak said:
Navigate to the platform-tools folder and open a command window there. Also, if that doesn't work, in the fastboot thread I linked, is a method to install fastboot and ADB system wide. Is that an option?
Click to expand...
Click to collapse
This is my "tools" folder from the SDK I downloaded.

nickb2005 said:
This is my "tools" folder from the SDK I downloaded.
Click to expand...
Click to collapse
Now here's what happens when I click the android, I assume I want to install all 16 packages here? My question is where do I go from this step?

nickb2005 said:
Now here's what happens when I click the android, I assume I want to install all 16 packages here? My question is where do I go from this step?
Click to expand...
Click to collapse
Forgot the image...

nickb2005 said:
Forgot the image...
Click to expand...
Click to collapse
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378

Evolution_Freak said:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?

nickb2005 said:
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
Click to expand...
Click to collapse
I tried another guide to get adb and fastboot working. However, now it's showing my device isn't attached although it 100% is.

nickb2005 said:
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
Click to expand...
Click to collapse
I've never encountered this, again I don't have Mac. I'm guessing you couldn't get the simple ADB and fastboot tool to install, from the other thread?
I haven't had my morning coffee yet, so bare with me.

Evolution_Freak said:
I've never encountered this, again I don't have Mac. I'm guessing you couldn't get the simple ADB and fastboot tool to install, from the other thread?
I haven't had my morning coffee yet, so bare with me.
Click to expand...
Click to collapse
I know, it's early :/ im going on like 5 hours trying to fix this thing. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1917237
I got adb and fastboot in the folder, but whenever I type ./adb devices it shows nothing is connected yet I am connected via USB and the phone shows me that.

nickb2005 said:
I know, it's early :/ im going on like 5 hours trying to fix this thing. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1917237
I got adb and fastboot in the folder, but whenever I type ./adb devices it shows nothing is connected yet I am connected via USB and the phone shows me that.
Click to expand...
Click to collapse
Did you install the drivers?

Evolution_Freak said:
Did you install the drivers?
Click to expand...
Click to collapse
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.

nickb2005 said:
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
Click to expand...
Click to collapse
Again, I'm sorry for my lack of knowledge with Mac.

Evolution_Freak said:
Again, I'm sorry for my lack of knowledge with Mac.
Click to expand...
Click to collapse
Oh no problem at all..I know your trying to help me. I shouldn't of been trying to do this and now I don't have a phone at all.

nickb2005 said:
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
Click to expand...
Click to collapse
Try this, power off your nexus and manually boot it to bootloader. Hold power down and press volume up. Once it boots to bootloader, connect to your computer.
---------- Post added at 08:05 AM ---------- Previous post was at 08:04 AM ----------
See if it is detected then and try the command: fastboot devices

Soft bricked - Not showing in ADB Devices

I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:

htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
See if you can flash a rom from your sd. hopefully you have something on there. Also see if you can see anything on fastboot since adb is not seeing anything

I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.

htcoveblue said:
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
Click to expand...
Click to collapse
Update your android SDK. Then try again.

htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
I read the story, then at the end is your problem. well, part of it. you weren't using adb in the bootloader, it doesnt work there, ever. you were using fastboot, and you should've fastboot devices

That's encouraging. Any idea how to get past the system.img file is too large error?

htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
Is your SDK updated?

My drivers are updated using the Google USB Drivers from this link: http://developer.android.com/sdk/win-usb.html

I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".

htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
There is a different fast boot that you have to use called mfastboot.
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
The fastboot not being recognized can sometimes be a driver error. Is it recognized look through device manager and try uninstall then unplug USB and plug back in.
Also the android naked drivers might help. Give them a try. http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Sent from my Nexus 6 using Tapatalk

htcoveblue said:
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
Click to expand...
Click to collapse
Can you not use MTP from TWRP?

Jnewell05 said:
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....

htcoveblue said:
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
Click to expand...
Click to collapse
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053

Evolution_Tech said:
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Click to expand...
Click to collapse
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!

htcoveblue said:
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
Click to expand...
Click to collapse
No problem. I've run this and as long as you follow the installation instructions precisely, it is very stable and capable of being a daily driver.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
There's another flashable here:
http://forum.xda-developers.com/showthread.php?t=3066052
I haven't run this one but it seems to be getting good reviews.