Related
So, I have spent the last 4 hours trying to find information and trying to fix things and I have yet to get nowhere.
I tried to install SkyDragon (http://forum.xda-developers.com/showthread.php?t=2400161) on my HTC One. Having gotten an insurance replacement in the last month, I forgot that I hadn't gotten around to getting S-OFF on this replacement device. (I had S-OFF on my old one). Due to this, everything got messed up.
It was trying to boot, went to HTC screen, then tried to reboot to recovery. Clockwork mod would boot, but as soon as any graphics came on the screen, it would reboot back to the HTC screen. This looped.
I managed to flash TWRP on it, but the same thing was happening.
After using fastboot to clear the cache, I got into TWRP. Awesome. Now I just need to get a ROM on this sucker.
adb keeps telling me "adb server is out of date. killing..." In regards to this, I have gone to the Android SDK and installed the latest version. I also tried updating to the latest drivers on my computer as well.
To my understanding, you can't push whole .zip files with fastboot, but I tried to use the "fastboot update rom.zip" command, which won't work due to "archive does not contain 'android-info.txt'" and "archive does not contain 'android-product.txt'".
I tried to go into TWRP and mount the storage, but lo-and-behold it crashes and doesn't mount crap so I can't copy this rom over to flash it with TWRP.
Please. Does anyone have any suggestions? I am not the MOST android savvy, but I have tried everything I could think of. One last resort is I'm gonna try to flash clockwork and see if I can get it to mount. Please help me?
EDIT: Clockwork didn't work, and sideload won't work because "adb server is out of date. killing..."
EDIT 2: I've got an M7_UL with S-ON, HBOOT 1.44.0000. Fastboot works like a charm, adb tries to connect but fails every time.
What is your PC Operating system?
You may wish to try a Linux Live CD.
BenPope said:
What is your PC Operating system?
You may wish to try a Linux Live CD.
Click to expand...
Click to collapse
Both of my PCs are running Windows 7.
Using my roommates computer, I downloaded the Android SDK and I am now able to adb push. Here's to hoping just pushing a ROM and booting into recovery to flash it will work.
starlitjessi said:
Using my roommates computer, I downloaded the Android SDK and I am now able to adb push. Here's to hoping just pushing a ROM and booting into recovery to flash it will work.
Click to expand...
Click to collapse
It works now. I was able to push a stable ROM from my roommate's computer and got it running just fine. Thanks anyway!
I've found myself in a situation where my phone is entirely wiped without a backup, and no operating system on the phone. I'm trying to sideload it, but I cannot access ADB. However, I can use Fastboot. How does this make sense? Does anyone have any advice so I can use ADB to sideload?
Yes I have some advice. But before that. Have you searched this and general forum? What did you learn?
sent from my mobile device
SaHiLzZ said:
Yes I have some advice. But before that. Have you searched this and general forum? What did you learn?
sent from my mobile device
Click to expand...
Click to collapse
I've been all over the place on here for the last few hours. I have TWRP installed with no .zip on the SD card of my phone. I'm able to access fastboot, but attempting 'fastboot flash zip ____.zip' results in an error for me ("FALED (remote: not allowed)"). I've been trying to sideload the .zip, but my computer does not recognize the presence of my phone. I was having some trouble with the HTC drivers on Windows 7 earlier - is that a known issue by any means? Were this any other phone but the HTC One I would have just taken the SD card out by now and put the .zip on there through other means, but I feel so stuck right now all because ADB is not functioning properly.
I have S-ON, and have not been able to find a reliable source for a RUU or firmware for my T-Mobile phone to try and go back to pure stock. And even then, I think, if ADB isn't working, what is there to do?
Any and all help would be thoroughly appreciated.
I had the same problem but with a diferent result.
With the help of xda i got it working. Check the thread and see if it helps in your case.
http://forum.xda-developers.com/showthread.php?t=2660939
your output of fastboot getvar all ?
Okay, I have the Nexus 6 (T-Mobile), rooted stock. I also have the Nexus 10. On both, I tried to sideload the 5.0.1 OTA update... and it failed in the exact same manner.
Obviously, I'm doing something wrong, but I have no idea what.
I did the Nexus 10 on a Windows 7 box, and I'm trying the Nexus 6 on a Linux machine. Same. Exact. Problem.
What I'm doing is this:
adb reboot bootloader
Arrow up to recovery, hit the power button to select
Hold down the power button and press the up button
Select "Sideload from ADB" (can't remember the exact wording, but basically, that)
adb sideload <verylongfilename.zip>
The update starts... and gets to 48% on my computer, and then ends. (I don't mean that it pauses or hangs, I mean it "finishes" -- it's done and back at the prompt). On the phone, at that time, it says "system has been remounted r/w; reflash device to reenable ota updates"
So that's where I'm at. On my Nexus 10, I ended up wiping it and just doing the full stock image install to get 5.0.1 -- that worked fine. On my phone, though, I really don't want to lose my entire setup just to get the bump from 5.0 to 5.0.1.
Can anyone tell me what the heck I'm doing wrong? It has to be something I'm doing or something I have configured wrong or ... I don't know. But the process clearly works for many, many people, and the fact that I have the same problem with two different devices on two different computers... it has to be my process, or something I've done to my devices.
Both devices are rooted stock, with stock recovery.
Any help you guys can provide would be greatly appreciated!!
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
simms22 said:
you cant update it via your phone. you need to flash the update via fastboot, while you are in your bootloader.
Click to expand...
Click to collapse
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
commonplace said:
Right, I'm not trying to do it from my phone, I'm doing it from my computer. What am I doing wrong with my adb sideload process?
Click to expand...
Click to collapse
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
simms22 said:
then why are you trying to sideload it???
download it via your computer, extract the files from the zip, boot your phone into the bootloader, connect it to your computer, run fastboot devices(to make sure that the computer sees your device, then run the flash-all script.
Click to expand...
Click to collapse
I was following directions found elsewhere (AndroidCentral and another site). I see now that adb sideload is not the answer, and that fastboot flash IS.
Phone = upgraded. Thanks for steering me in the right direction!
I had rooted 5.0 and read on Google+ that update over the air would not work. I used this guide to update to 5.0.1 and lost no data, nor had to reinstall anything.
http://forum.xda-developers.com/nexus-6/help/help-5-01-wipe-t2970924
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
mikeos89 said:
I heard of cyanogen mod and was eager to have a play around and try to install it.
I followed a guide on youtube to root my device and things went wrong.
It was running on the latest version of marshmallow, i did all the steps on the video and at the end it said "your device is corrupt it can't be trusted" and then the phone turns off.
I can only get as far as team win recovery project and i've messed up because i've stupidly formatted the data so there are no files or operating system at all on my device.
I'm not being lazy, i've searched these forums and have been trying to sort it out for the last 5 hours.
I'm using a mac too, most of guides are for windows.
I'm really stuck and I'm not clued up with all the terminology used on here.
Can anyone help me in layman's terms? I'm really desperate as now I'm stuck without a phone.
Please don't take the mickey out of me, I know I shouldn't have messed around with these things if I'm not fully aware what I'm doing. I expected it to be straight forward like jailbreaking an iPad.
Click to expand...
Click to collapse
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
mikeprius said:
I don't know how you went about the processes but based on what you are saying, I'm guessing you used a "toolkit". You situation isn't that big of a deal. If you can get into fastboot, I suggest you get into fastboot and use adb commands to "push" commands to push a custom ROM into your /sdcard then flash it via TWRP.
adb push <source-path> <target-path>
adb devices
adb push filename /sdcard/
Once you boot back into TWRP, flash and you are good to go.
Click to expand...
Click to collapse
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Can't you just drag and drop a ROM and gapps while in twrp... Ive.done it before...good luck
Not likely as the phone plugged into the computer may not read it as a "USB" drive. I have windows and I have no idea what the command prompts are for Mac. Also if your understanding is virtually nothing, you need at least understand the basics of fastboot and custom recovery in order to fix your situation.
The good news is that your phone isn't messed up. The bad news is you need to roll up your sleeves and learn the basics of how the commands work so you can reboot the phone back. Everyone here can describe to you what to do but since you don't know the fundamentals it won't mean anything until you do. Sorry.
Btw, jailbreaking isn't the Apple version of "root". They are 2 completely different things.
What I would do is fastboot erase TWRP and re-flash it as it sounds like you are having problems, then adb pull a custom ROM into your internal storage. Reboot into TWRP and flash it. That's what you need to do.
mikeos89 said:
I appreciate the help, but imagine you are talking to an idiot who doesn't have the foggiest, I'm clueless with command prompts unless it's something I'm copying directly.
I want to learn this stuff, but I really need all the info stripped down to the bare basics at the moment.
I'm panicking a bit too which isn't helping.
Click to expand...
Click to collapse
I don't know anything about flashing a phone from a Mac but if you can boot your phone into bootloader mode and get fastboot to work on the Mac I would follow the steps under Step 5, Method 2 at http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008. I use that method to upgrade my phone every time a new ROM comes out and it works great.
Note:
1. You this will get you back to stock, you'll still have to flash your custom ROM after you get your phone working.
2. The .img files can be downloaded from https://developers.google.com/android/nexus/images#shamu.
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
bushako said:
Provided you have custom recovery such as TWRP. Get a USB otg card reader or microusb stick, download a Rom and transfer it onto the OTG, go to twrp, navigate to the USB OTG memory and flash the Rom. Simple.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
This, easiest way for you probably. I've done it this way before too. I suppose you could ask someone to TeamView your pc, but you should probably try the usb otg method first.
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