Database Develop

[Q] Fire HD with only TWRP installed

Hi all, I've been searching online and I haven't found anything that helps or even directly applies, so I broke down and decided to ask for help.
I was working off the guide to root my kindle, install TWRP and then a ROM, first time doing this.
SO let me break down where I'm at:
-rooted
-TWRP installed
-there's no .zip that I can find to stall from (checked sdcard folder and all others)
-can't load into original OS, logo goes from orange to blue on its own, and hangs there
-when plugged into PC, it is recognized but says no drivers are installed for it (no matter how many times i try reinstalling it.)
- I can get it into fastboot mode, but can't seem to load anything (I've read that fastboot doesn't work with twrp)
- adb sideload doesn't seem to work, it cannot find device
So how can I get a .zip file loaded to twrp, or restore the device, without adb seeing the device?
Is there a specific way to install the drives, or a way to get the .zip loaded through fastboot that I'm not aware of?
I'm sorry if this has been addressed before, I haven't seen this exact issue, and the fixes that seem close haven't worked :
thanks guys!

G_G_L said:
Hi all, I've been searching online and I haven't found anything that helps or even directly applies, so I broke down and decided to ask for help.
I was working off the guide to root my kindle, install TWRP and then a ROM, first time doing this.
SO let me break down where I'm at:
-rooted
-TWRP installed
-there's no .zip that I can find to stall from (checked sdcard folder and all others)
-can't load into original OS, logo goes from orange to blue on its own, and hangs there
-when plugged into PC, it is recognized but says no drivers are installed for it (no matter how many times i try reinstalling it.)
- I can get it into fastboot mode, but can't seem to load anything (I've read that fastboot doesn't work with twrp)
- adb sideload doesn't seem to work, it cannot find device
So how can I get a .zip file loaded to twrp, or restore the device, without adb seeing the device?
Is there a specific way to install the drives, or a way to get the .zip loaded through fastboot that I'm not aware of?
I'm sorry if this has been addressed before, I haven't seen this exact issue, and the fixes that seem close haven't worked :
thanks guys!
Click to expand...
Click to collapse
Without a working ADB connection, you can't get a file to your device in TWRP. You can restore your system, recovery, and boot images with fastboot, but your device must be in fastboot mode first. If you decide to do that, you'll have to restore your stock system, recovery and boot images, saved from the 2nd bootloader install instructions, then start the whole process all over again.

soupmagnet said:
Without a working ADB connection, you can't get a file to your device in TWRP. You can restore your system, recovery, and boot images with fastboot, but your device must be in fastboot mode first. If you decide to do that, you'll have to restore your stock system, recovery and boot images, saved from the 2nd bootloader install instructions, then start the whole process all over again.
Click to expand...
Click to collapse
Cheers! Excellent advise! I got it restored to stock!
I used the img files from here: http://forum.xda-developers.com/showthread.php?t=1951254
and followed the fastboot directions here: http://forum.xda-developers.com/showthread.php?t=2277105
now try it again! (and hopefully succeed!)

Nexus 7 2012 hspa soft brick on 4.4 ota need my files accessed

Hey everyone, so tonight I got the 4.4 ota on my N7, I am unlocked and rooted but stock everything including recovery.
After updating, my N7 keeps going to stalk recovery and that's it.
I know I can just reflash everything but I have a few very important files. Is there a way to reflash 4.3 without losing data or accessing the data partition while soft bricked so I can recovery my files?

I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.

chrisinsocalif said:
I may be wrong, but can't you reflash your phone as long as you don't replace the userdata.img through fastboot to retain the same information? I could be wrong.
Click to expand...
Click to collapse
I'm not sure. I'd like to have this confirmed before I do anything. It's not urgent as the due date on my prgect isn't for another couple of weeks. But thanks. I'll look at that as a last resort.

Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.

chrisinsocalif said:
Is it one file or multiple files you are trying to access? Have you tried to pull them using adb to your pc? I do not know how to do it, but I am sure there is a guide somewhere. Or try a phone backup using fastboot then unpack it on your desktop and get the files you need. Again, I am not good with phones, just throwing out idea's.
Click to expand...
Click to collapse
ADB or Wugs root kit don't see my Nexus 7 as it keeps rebooting to the dead droid and I know I don't have it set for debugging. Guess I'm screwed.

When you say "dead droid", you're referring to fastboot mode, right? (Android icon with a bunch of text below it, starting with "Fastboot Mode" in red.)
If you have fastboot, you can flash TWRP Recovery 2.6.3.0. Download it from Team Win's site (Google it). Then:
fastboot flash recovery openrecovery-twrp-2.6.3.0-grouper.img
fastboot reboot-bootloader
Use the Volume keys to select "Recovery Mode" and hit Power. Once you see the TWRP menu, you should have adb root access automatically. Connect tablet to USB, and use adb pull to download the contents of /sdcard:
adb pull /sdcard /dumphere
Replace "dumphere" with whatever directory you want to dump to. I'm sure there's better guides and explanations for this, but this is the quick version.
I guess you could reflash stock recovery afterwards, but I can't think of a reason why you'd want to. It's not like it's that useful.
As a rule of thumb, you should at least know how to get around a command line, and use adb and fastboot before mucking around with your tablet.
-XCN-
P.S. I could be mistaken, but I don't think internal storage (which is /sdcard, or /data/media) is overwritten when you flash a ROM. Obviously, backup first before trying.

[Q] Bricked and bootlooping through the night after Revolution HD 6.1 GE

My One (M7) won't stop restarting and keeps boot looping repeatedly since I went from Renovate to Revolution HD 6.1 GE yesterday evening. I am able to get into the recovery, wipe data, erase cache, dalvik, etc. But no matter how many times I have freshly installed the zip file, wiped cache and dalvik, it keeps booting up only till the 'Welcome' Screen (of Google) and restarts itself without my even touching the phone.
I tried to even force shut the phone but it just won't shut down and automatically restarts itself with that familiar buzz of the One.
I know this phone has been bricked but never had this big of an issue switching between ROMs in the past, given the process of doing it is very straightforward (zip file download--erase/wipe data--cache--dalvik cache--restart).
For my phone's safety and not 'burn it out' by repeatedly restarting itself, I have currently kept the phone on the CWM recovery screen as I write.
I forgot to add that I even did factory reset three times
Any help or suggestions?

sdg1980 said:
My One (M7) won't stop restarting and keeps boot looping repeatedly
Click to expand...
Click to collapse
Install TWRP 2.6.3.3 or 2.6.3.4, and reflash the custom rom..

sdg1980 said:
My One (M7) won't stop restarting and keeps boot looping repeatedly since I went from Renovate to Revolution HD 6.1 GE yesterday evening. I am able to get into the recovery, wipe data, erase cache, dalvik, etc. But no matter how many times I have freshly installed the zip file, wiped cache and dalvik, it keeps booting up only till the 'Welcome' Screen (of Google) and restarts itself without my even touching the phone.
I tried to even force shut the phone but it just won't shut down and automatically restarts itself with that familiar buzz of the One.
I know this phone has been bricked but never had this big of an issue switching between ROMs in the past, given the process of doing it is very straightforward (zip file download--erase/wipe data--cache--dalvik cache--restart).
For my phone's safety and not 'burn it out' by repeatedly restarting itself, I have currently kept the phone on the CWM recovery screen as I write.
I forgot to add that I even did factory reset three times
Any help or suggestions?
Click to expand...
Click to collapse
SaHiLzZ said:
Install TWRP 2.6.3.3 or 2.6.3.4, and reflash the custom rom..
Click to expand...
Click to collapse
You need s-off to use that rom

clsA said:
You need s-off to use that rom
Click to expand...
Click to collapse
If you say soo... but.. from OP http://forum.xda-developers.com/showthread.php?t=2356654..
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
Click to expand...
Click to collapse

clsA said:
You need s-off to use that rom
Click to expand...
Click to collapse
How do I install TWRP in my phone at this point of time? My computer is not recognizing the fast boot mode (USB driver not recognized, and Windows malfunctioned')

sdg1980 said:
How do I install TWRP in my phone at this point of time? My computer is not recognizing the fast boot mode (USB driver not recognized, and Windows malfunctioned')
Click to expand...
Click to collapse
Fix. Your. Driver. Issues.

SaHiLzZ said:
If you say soo... but.. from OP http://forum.xda-developers.com/showthread.php?t=2356654..
Click to expand...
Click to collapse
and further down the page
Android Revolution HD 6.1
Google Edition
You need S-OFF, otherwise you'll experience boot-loop!
You can't use ART with deodexed custom ROM
You need TRWP 2.6.3.3 custom recovery!
Click to expand...
Click to collapse
@sdg1980 - flash this in you current recovery and reboot recovery
https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip

clsA said:
and further down the page
Click to expand...
Click to collapse
lol.. well that answers that.

SaHiLzZ said:
lol.. well that answers that.
Click to expand...
Click to collapse
lol, yeah it gets the point across ..lmao

clsA said:
and further down the page
@sdg1980 - flash this in you current recovery and reboot recovery
https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
Click to expand...
Click to collapse
@clsA; Thanks for the link for TWRP. My issue right now is I cannot access the virtual SD and don't know how to transfer the TWRP zip from the comp to the One without having the computer recognizing it as USB. Does that make sense?
My system is Windows 8.1, and I tried reading up the forums here for the correct HTC driver for 8.1 without much insight into the correct driver.
@ Sahil: I appreciate your attempt at helping me, but sometimes seniors forget that they were juniors at some point. Saying something with emphasis doesn't exactly get the point across. I know I have to "Fix. driver. issues" but it's easier said than done when you are in a catch-22 where both recovery and the bootloader are accessible, but you cannot have the computer recognize your phone because...well, the driver is being recognized and yet not recognized. Let me explain. When I connect the phone to the computer, it briefly shows up as removable storage (with the "10 gb out of 25.2 available" page) but since it is constantly bootlooping, it doesn't stay long enough on the page for me to access it. To compound my frustration, in the boot loader, clicking on 'fastboot' immediately flashes the message that I mentioned previously (USB not recognized...). In short, I KNOW that my phone is in working condition, but I am stuck in a continuity of hurdles.
I am desperately trying to read right now and find the correct drivers for my HTC One (with Windows 8.1 compatibility)

sdg1980 said:
@clsA; Thanks for the link for TWRP. My issue right now is I cannot access the virtual SD and don't know how to transfer the TWRP zip from the comp to the One without having the computer recognizing it as USB. Does that make sense?
My system is Windows 8.1, and I tried reading up the forums here for the correct HTC driver for 8.1 without much insight into the correct driver.
@ Sahil: I appreciate your attempt at helping me, but sometimes seniors forget that they were juniors at some point. Saying something with emphasis doesn't exactly get the point across. I know I have to "Fix. driver. issues" but it's easier said than done when you are in a catch-22 where both recovery and the bootloader are accessible, but you cannot have the computer recognize your phone because...well, the driver is being recognized and yet not recognized. Let me explain. When I connect the phone to the computer, it briefly shows up as removable storage (with the "10 gb out of 25.2 available" page) but since it is constantly bootlooping, it doesn't stay long enough on the page for me to access it. To compound my frustration, in the boot loader, clicking on 'fastboot' immediately flashes the message that I mentioned previously (USB not recognized...). In short, I KNOW that my phone is in working condition, but I am stuck in a continuity of hurdles.
I am desperately trying to read right now and find the correct drivers for my HTC One (with Windows 8.1 compatibility)
Click to expand...
Click to collapse
windows 8.1 only has problems with the old 1.54 and 1.44 hboot .. the drivers work fine with hboot 1.55 and up.
Have you actually shut the phone off yet ?
hold the phone under a lamp and hold the power button and vol down and count to 60. let go of the power button and continue to hold vol down till you get to the bootloader. quickly hit power and volume down to shut off and hit power.
leave it off for a couple min then bootup again holding vol down.

sdg1980 said:
How do I install TWRP in my phone at this point of time? My computer is not recognizing the fast boot mode (USB driver not recognized, and Windows malfunctioned')
Click to expand...
Click to collapse
boot phone in your actual recovery (cwm) with the twrp.zip file in your adb/fastboot folder, open a command prompt
Code:
adb push TWRP_2.6.3.3_m7.zip /sdcard/
then flash twrp.zip from cwm, clear cache and reboot the phone to twrp
then you'll be able to boot in twrp recovery and adb push and flash newer sense roms (i.e sense ARHD)

alray said:
boot phone in your actual recovery (cwm) with the twrp.zip file in your adb/fastboot folder, open a command prompt
Code:
adb push TWRP_2.6.3.3_m7.zip /sdcard/
then flash twrp.zip from cwm, clear cache and reboot the phone to twrp
then you'll be able to boot in twrp recovery and adb push and flash newer sense roms (i.e sense ARHD)
Click to expand...
Click to collapse
@ alray
I understand here that you are asking me to boot into the CWM recovery, correct? I can definitely do that. The next part of your instruction is a bit harder for me to follow. I sincerely apologize if I sound idiotic. I am trying to learn here so that if it happens again (or anyone suffers the same fate), I would know what to do or say. Kindly walk me through here.
I have the TRWP zip file. If I place/put it in the adb/fastboot folder, how do I run the command prompt without the computer flashing the USB message?
So, here is what I am gathering from your directions
a) Boot into recovery (?)
b) Connect the computer via cable and run the command prompt and the script (?) [Here won't the computer flash USB not recognized?)
Again, I am sorry again I am asking what might perhaps be stupid questions to you or other senior members. I appreciate everyone's efforts in helping me out here.

alray said:
boot phone in your actual recovery (cwm) with the twrp.zip file in your adb/fastboot folder, open a command prompt
Code:
adb push TWRP_2.6.3.3_m7.zip /sdcard/
then flash twrp.zip from cwm, clear cache and reboot the phone to twrp
then you'll be able to boot in twrp recovery and adb push and flash newer sense roms (i.e sense ARHD)
Click to expand...
Click to collapse
I have HBOOT 1.44. Feel lost here. Not sure how to fix this problem.

sdg1980 said:
I have HBOOT 1.44. Feel lost here. Not sure how to fix this problem.
Click to expand...
Click to collapse
windows 8.1 driver fix
HTML Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
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
http://forum.xda-developers.com/attachment.php?attachmentid=2500592&d=1389122072
http://forum.xda-developers.com/showthread.php?p=49131915
Or you can use a Ubuntu live CD (32bit)
http://forum.xda-developers.com/showthread.php?t=2606577
http://www.ubuntu.com/start-download?distro=desktop&bits=32&release=latest
http://www.ubuntu.com/download/desktop/create-a-usb-stick-on-windows

sdg1980 said:
I understand here that you are asking me to boot into the CWM recovery, correct?
Click to expand...
Click to collapse
Yes
I have the TRWP zip file. If I place/put it in the adb/fastboot folder, how do I run the command prompt without the computer flashing the USB message?
Click to expand...
Click to collapse
Windows 8.1 doesn't play nice with hboot 1.44 and 1.54 for FASTBOOT connection (phone in bootloader mode). It should work fine using ADB (when your phone is booted in custom recovery or in the OS)
so you could try to fix your drivers with the info cIsA gave you and flash your recovery the ''standard'' way via fastboot
Code:
fastboot flash recovery recovery[B][COLOR="Red"].img[/COLOR][/B]
fastboot erase cache
fastboot reboot-bootloader
or
get rid of windows 8.1 and use a good OS (imo) like Windows 7, XP, Linux, or MacOs so you can connect your phone to you computer without issues
or
flash the recovery.zip from recovery. in this case you must copy the recovery.zip to your internal memory (/sdcard) using ADB:
open the folder where you have ADB/FASTBOOT in, hold left shift + right click a blank space in that folder, select ''start command prompt here''
then in the command prompt enter this command:
Code:
adb push TWRP_2.6.3.3_m7[B][COLOR="Red"].zip[/COLOR][/B] /sdcard/
then hit ''enter'' and wait for the file to transfer
when the transfer is completed, flash the zip file using cwm, erase cache and reboot in your new recovery, push a rom that doesn't require s-off (i.e arhd 71.1) using the same method:
Code:
adb push name_of_rom.zip /sdcard/
then flash the rom and enjoy your phone

To make stuff easier download minimal adb and fastboot from the net. Copy the zip into the folder and do what the gut above said
Sent from my HTC One using XDA Premium 4 mobile app

alray said:
Yes
Windows 8.1 doesn't play nice with hboot 1.44 and 1.54 for FASTBOOT connection (phone in bootloader mode). It should work fine using ADB (when your phone is booted in custom recovery or in the OS)
so you could try to fix your drivers with the info cIsA gave you and flash your recovery the ''standard'' way via fastboot
Code:
fastboot flash recovery recovery[B][COLOR="Red"].img[/COLOR][/B]
fastboot erase cache
fastboot reboot-bootloader
or
get rid of windows 8.1 and use a good OS (imo) like Windows 7, XP, Linux, or MacOs so you can connect your phone to you computer without issues
or
flash the recovery.zip from recovery. in this case you must copy the recovery.zip to your internal memory (/sdcard) using ADB:
open the folder where you have ADB/FASTBOOT in, hold left shift + right click a blank space in that folder, select ''start command prompt here''
then in the command prompt enter this command:
Code:
adb push TWRP_2.6.3.3_m7[B][COLOR="Red"].zip[/COLOR][/B] /sdcard/
then hit ''enter'' and wait for the file to transfer
when the transfer is completed, flash the zip file using cwm, erase cache and reboot in your new recovery, push a rom that doesn't require s-off (i.e arhd 71.1) using the same method:
Code:
adb push name_of_rom.zip /sdcard/
then flash the rom and enjoy your phone
Click to expand...
Click to collapse
So, I installed the TWRP using the method you mentioned, rebooted, deleted cache, and then again, 'push Android_Revolution_HD-One_71.1.zip /sdcard/'
How long was/is this supposed to take, being a gig file? In the cmd window, the cursor just blinks and nothing is happening (unlike installing TWRP when it installed in few seconds)

sdg1980 said:
So, I installed the TWRP using the method you mentioned, rebooted, deleted cache, and then again, 'push Android_Revolution_HD-One_71.1.zip /sdcard/'
How long was/is this supposed to take, being a gig file? In the cmd window, the cursor just blinks and nothing is happening (unlike installing TWRP when it installed in few seconds)
Click to expand...
Click to collapse
Should take between 5-10 min
Sent from my HTC One using XDA Free mobile app

alray said:
Should take between 5-10 min
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Firstly, I would like to thank EACH and EVERY senior member to itsber here who helped me through this crisis. It has been an eye opener for me, being a junior member. I managed to follow the steps outlined and restore my phone to its working condition with ARHD 71.1. THANKS A LOT!!!
Also, for those who are thinking of flashing ARHD 6.1 GPE on their One, make sure that your phone has S-off. That might have one reason why my phone went into a tailspin of automatic bootup and restarts. There might have been something else going on with that ROM as well. I am not sure. Repeated cleanup of cache and factory resets didn't help the cause earlier.
Anyways, I would like to make a small donation via Paypal to our community (especially for helping me out and showing us the ropes). If you can put up the link here, that would be nice.
Cheers everyone and happy flashing!:good::good::good:

Connection issues between computer and Nexus6

I bought a Nexus6 about a month ago. I wasn't planning on rooting it, but I have rooted a number of devices in the past so am reasonably comfortable doing that. I bought the phone from Amazon but I am on T-mobile's network.
After I fired up the phone and used it for a while, I got a message asking me to update to software version 5.1. When I go to the about on my phone, it says it has 5.1.1 but it says the build number is LRX22C which when I looked that up indicates that it is actually running 5.0. I told the phone to update, but it fails every time (android guy with the red exclamation mark over his belly). I did a factory reset and repartition and still the same thing. At this point, I figured I would just root and and force it to 6.0.
After installing drivers, ADB-tools, etc. my computer recognizes the phone. When I connect by a USB cable and the phone is on, it shows under devices. However, when I boot into fastboot mode, my laptop no longer recognizes the Nexus. The fastboot screen shows that the phone is unlocked, and it recognizes that it is getting power from the laptop. However, it says to connect via usb. Running the command prompt and using SDK-Windows, when I type fastboot devices it shows nothing.
Interestingly, I see that Superuser is on the phone and working. I don't think I rooted my phone at any point in the process of trying a lot of different things, although anything is possible. I have been thrashing around a bit trying to get this to get the phone on 6.0 so might have rooted accidentally although I doubt it. My suspicion is that I was given a previously used phone that someone rooted and returned.
Any suggestions/help out there?

When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?

RMarkwald said:
When in Fastboot Mode, what does Device Manager show? Does it see the device correctly, or is it showing a yellow triangle w/ exclamation point over the device?
Click to expand...
Click to collapse
It shows Other Devices > Fastboot Shamu S with the yellow triangle and exclamation point. I have motorolla device manager installed and I thought that had my drivers covered but perhaps not?

These devices do have driver issues. Try downloading the correct drivers and it should fix it, a lot of people have had similar issues.

@LSquared
Download Wugfresh Nexus Root Toolkit. It has a long button on the top right "Install and test drivers" - a really helpful guide in clearing out any old drivers and installing and testing the new ones.
It can also perform many other functions, but after a lot of persuasion(!) in these forums I decided that learning to do everything manually is not only simple but safer, because you know at exactly which point an error occurs. The driver setup part of NRT is a brilliant help in setting your PC up once to get you started.
If you don't have anything valuable on your device yet, install the MMB29S factory image, then TWRP, and from there install SuperSU v2.66, and you're as up to date as you can possibly be.

Spend a few hours doing research and you will be fine. Just stay away from root kits. They only make things worse and lessen the experience of owning a nexus. As well as stops any help you may get in the forums as no one will help those that use the root kits.

Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.

LSquared said:
Thanks for all the help/suggestions. After a lot of poking around, I realized that I had the right driver hiding in a folder (inside SDK I think) and had to just manually point to them and that got rid of the connection issue. Now I seem to be stuck on flashing the latest stock OS. I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
How are you trying to push the files, I assume Fastboot, are you getting an error? Is your Android SDK up-to-date?

LSquared said:
I have been trying to flash via Minimal ADB and Fastboot but it isn't pushing the image there correctly. I don't want a custom rom, just stock 6.0.
Click to expand...
Click to collapse
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.

cam30era said:
Google updated fastboot a little over a year ago to allow flashing the very large system.img files. Minimal ADB & Fastboot does not have this update (I believe). Download the latest Android SDK and you'll be good to go.
Click to expand...
Click to collapse
I just downloaded Android SDK so it has the latest files (I believe). Android SDK doesn't connect to the phone, it just keeps an updated set of firmwear, right? If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using? It seemed a lot easier on my older phones that had a micro SD card because I could just drop the new Rom on there and install that from the bootloader.

LSquared said:
If I am not using minimal ADB and fastboot to push files from my computer to the phone, what program should I be using?
Click to expand...
Click to collapse
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.

cam30era said:
Use the ADB and fastboot that are included with the Android SDK that you downloaded. They are in the Platform-Tools folder.
Click to expand...
Click to collapse
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?

LSquared said:
If I click on either of those to run the application, it flashes a box for a split second and then nothing. I guess I am missing a step?
Click to expand...
Click to collapse
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot

cam30era said:
I would suggest reading and following this guide >http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot
Click to expand...
Click to collapse
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?

LSquared said:
That guide is great and helped me get the bootloader unlocked and the phone rooted. I downloaded the image file just fine, but when I go to run root-windows.bat I get the message "fastboot is not recognized as an internal or external command." I am guessing I don't have some file in the right location?
Click to expand...
Click to collapse
The flash_all scripts don't work. Flash each img file individually, after you've extracted them all from the ,zip.

Yup, flash the .img files individually, the batch command doesn't work.

Here's the guide I always use: How to manually flash img files to your Nexus device
Basically, with phone connected to computer and booted to the bootloader, open Command Prompt window, change directories to where your sdk/platform-tools directory is with your Shamu files, then:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Code:
fastboot flash bootloader "name of bootloader"
fastboot reboot-bootloader
Code:
fastboot flash radio "name of radio"
fastboot reboot-bootloader
NOTE: You'll have to extract the files from the image-shamu-mmb29s.zip file in this case to flash MMB29S.
Code:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Code:
fastboot reboot
I'm aware, it may be overkill, but I've never had any issues performing all of these steps to get back to 100% stock so if it "isn't broken, don't fix it". Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.

Good summary!
RMarkwald said:
Also this will wipe your internal SD area, so any files you want to save you should save them prior to starting this.
Click to expand...
Click to collapse
To avoid wiping your internal user storage, just skip the step that flashes userdata img (and the step at the beginning that erases usedata)

OnePlus 3T full wiped, not able to flash a new ROM via ADB

I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....

You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.

knijntjes said:
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
Click to expand...
Click to collapse
At the moment I am trying to find a way to install TWRP without an OS installed and OEM locked. In research I recognized this as the easiest way to install a new ROM. The only thing I need TWRP now.

If I were you, I'd flash the phone using the unbrick method and unlock the bootloader, so you won't lock yourself out in the future

TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
This might help:
http://www.oneplusbbs.com/thread-3203158-1-1.html
I can translate this for you if you need.

You need to flash a special build of Oreo beta to be a more to downgrade to Nougat according to the thread here below.
https://forums.oneplus.net/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
But since you've deleted everything your best bet now is the Qualcomm factory restore recover method.
https://www.google.se/amp/s/forum.x...ick-unbrick-tutorial-oneplus-3t-t3515306/amp/

TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
Some things you've missed:
1. Your first screenshot shows that ADB connects successfully to your phone because it shows the device ID. So drivers and ADB are ok.
2. ADB reads files from the directory it is invoked in. Your command shell is starting in c:/windows/system, so that's the directory ADB is looking in for OP.zip. you can either cd to the correct directory or specify the full path of the OP.zip file.
So, if you reboot your phone into recovery and select install from ADB then start ADB and verify its connected then run the sideload command pointing to the correct director it should flash the ROM successfully.
Sent from my OnePlus3T using XDA Labs