Related
Hey guys, long time lurker and now first time poster. Shame it has to be something very stupid.
So anyways, I wanted to flash the latest CM10.2 Unofficial build so I did the usual and downloaded the zip & gapps to my phone. But upon wiping my phone via TWRP I accidentally left the wipe userdata part checked and ... well now I have no OS installed as well as no zip's :/
I have TWRP installed so I thought why not sideload it, however when I go to advanced -> adb sideload it never starts up. This is the log:
Updating partition details...
Starting ADB sideload feature...
Click to expand...
Click to collapse
And it just stays there
I know that my ADB works as I have S-OFF & unlocked the bootloader and flashed the latest 1.54.0000 hboot so I can definitely use it, I just don't understand why it doesn't let me sideload for some reason.
Either way, I have full access to fastboot & TWRP recovery so i'm hoping this is a pretty simple thing to fix ... right?
Can anybody point me to the right direction?
Details:
No OS installed.
Access to TWRP & fastboot.
S-OFF, Modified Hboot 1.54.0000 (SuperCID) & Unlocked bootloader.
Windows 8 64-bit, drivers all work.
Latest SDK with all the binaries installed.
P.S. when I connect and try and use adb devices it doesn't recognise my device, and the cmd window gives the following when I try the sideload command:
Error: device not found.
Click to expand...
Click to collapse
Sounds like a driver issue to me but it doesn't make sense that the drivers would suddenly stop working ???
Here are screenshots of odd device behaviour when switching from fastboot to recovery (please copy & paste, I don't have enough posts to post images yet):
i.imgur.com/V79DFFA.jpg
i.imgur.com/MKD5C9U.jpg
Bump for help
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
redbull123 said:
I can't seem to get sideload to work in TWRP at the moment either. CWM works fine though, try flashing that and use the sideload feature.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Tried that already, same issue in not detecting the device. I'm downloading these drivers in a hope to fix something.
Thanks for the reply
EDIT:
Finally got sideloading in TWRP to work, it turns out it was a driver issue :/
Anyways, these are the drivers that worked:
androidfiles.org/hasoon2000/getdownload.php?file=HTC%20Drivers/HTCDriver.exe
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
IINexusII said:
why is everyone always wiping their storage these days? just use CWM next time and you wont accidentally do this again..
Click to expand...
Click to collapse
TWRP is much better for people who know what they are doing. There are more options and also a built in file manager. Also, the wipe button in TWRP wipes the 3 main partitions at once (data/cache/dalvik), so he must have actually selected internal sdcard from the advanced menu, and I have no idea why he would do that...
Doing the slider is all anyone needs to do in twrp to wipe yet I read more posts about people wiping with twrp than any other problem in these forums
My apologies if this has already been posted. I've been looking all morning but haven't seen anyone with the same issue.
Unlock bootloader: no problem.
Flash TWRP: I downloaded from http://teamw.in/project/twrp2/275, and I got an error about partition size mismatch, but that's ok, right?
But when I try to enter recovery, all I get is the warning screen that my phone is unlocked. The drivers are certainly installed correctly, and fastboot is working fine. I just can't get into recovery to flash a ROM!
Restoring to 4.4.4 stock worked like a charm.
http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
I've re-enabled USB debugging. Do I dare try to flash a custom recovery again?
Pandae said:
Do I dare try to flash a custom recovery again?
Click to expand...
Click to collapse
You can use Flashify to make a backup of your current recovery and to flash TWRP.img. should work like a charm.
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Pandae said:
But Flashify requires root, I see? The reason I'm trying to flash a custom recovery is so I can root in the first place.
Click to expand...
Click to collapse
You're right. Latest motorola driver and [TOOL]Minimal ADB and Fastboot will do the trick.
Sorry, I should have clarified that when flashing TWRP, I've already been using fastboot.exe from a command line (and administrator level), with the drivers correctly installed. That's how I was able to unlock in the first place.
I did try it with the version of Fastboot you linked to (what I have works peachy for my Nexus 7), still the same thing. I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Pandae said:
I can't boot into recovery and only get stuck at the Motorola unlocked warning.
Click to expand...
Click to collapse
Oh. Sorry. Can you post the output (terminal & device) of
Code:
fastboot devices
fastboot flash recovery NAME_OF_RECOVERY.img
I'd done "fastboot devices" already to verify, and it returns the serial number, though as I said it's clearly working since I was able to unlock as well as flash recovery. I'm flashing "TWRP2801-titan-motog-2014.img" that I downloaded from the TWRP site, and fastboot gives the standard messages about size and success (and my phone gives the size mismatch error).
It's so strange to me. I've flashed a custom recovery dozens of times on both generations of my Nexus 7s, but I've never seen this.
Pandae said:
It's so strange to me.
Click to expand...
Click to collapse
Yeah......have to meditate about that problem....... is your battery low? Fastboot mode of the device gives me all sorts of problems if it detects low battery
I had been using fastboot at 100% (literally finished a full charge) and 84%, but thanks for the continued attempts at explanation.
Oh, did you check the md5 checksum of your download?
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Pandae said:
Ah, good thought! I rarely do, but I did just now...and they're the same. It's crazy, isn't it?
Click to expand...
Click to collapse
If you are willing to risk it, try a fresh download and try again. I've flashed TWRP more than 20 times by now and never recieved an error whatsoever. It basically the easiest thing to do.
Incase you are stuck again, don't reflash the entire stock rom. Just flash the recovery.img from the stock rom files.
OR
Try this:
HOW TO ROOT MOTO G 2014 with Temporary Custom Recovery
Cheers
I've flashed a custom recovery many a time and have helped people through it, though on Nexus 7s.
Now shall I compound the mystery? I didn't think yet to use ADB to make my phone reboot to recovery. I had assumed recovery wasn't working. So here we go, after booting into Android:
adb reboot devices: my phone's there.
adb reboot recovery: TWRP's working?! And now root is complete!
It doesn't make sense to me why I can't get into recovery from the bootloader, but I can get into it with the simple ADB command. But I appreciate all the help, thanks!
Pandae said:
It doesn't make sense to me why I can't get into recovery from the bootloader
Click to expand...
Click to collapse
A little workaround:
Install Android Terminal Emulator
Add "Term shortcut" widget.
In "Arguments" enter
Code:
su -c reboot recovery
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
without enabling oem unlock in the developer options, nope. but you can use the stock recovery to check if a factory reset would help.
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
win465 said:
Factory reset doesn't help. When trying to sideload I keep getting error "system partition has unexpected contents" (Status 7).
Click to expand...
Click to collapse
Had you unencrypted?
Yes, but i flashed backed to stock kernal.
win465 said:
Yes, but i flashed backed to stock kernal.
Click to expand...
Click to collapse
How?
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
win465 said:
Using the nexus tool kit. After that I locked the bootloader to sideload the update.
Click to expand...
Click to collapse
Were you rooted before all of this too?
Nope
Evolution_Tech said:
Were you rooted before all of this too?
Click to expand...
Click to collapse
Nope
win465 said:
Nope
Click to expand...
Click to collapse
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Evolution_Tech said:
Then the toolkit most likely didn't replace the proper kernel, which is why the OTA failed. You'll have to RMA.
Click to expand...
Click to collapse
Thank you for your help
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
Click to expand...
Click to collapse
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Possible idea
Evolution_Tech said:
Not when his bootloader is locked. Unfortunately, the OP has locked his bootloader and can't boot to android to enable OEM unlock.
Click to expand...
Click to collapse
There's some more concrete info in the first couple pages, especially regarding our N6's:
http://forum.xda-developers.com/nexus-9/help/to-toggle-allow-oem-unlock-via-fastboot-t3091119
Hope this helps.
I'll keep my eyes open for anything that seems pertinent.
Best of luck
RedHazy said:
Which toolkit did you use? Try to flash everything in BOOTLOADER with the newest 5.1.1 using ADB and Fastboot commands as opposed to the Toolkits. I'm hoping your successful in your endeavours, I'm working on mine too. Even if you are missing any part of your stock image or basic partitions, you should be able to flash it back to normal via your bootloader. I had a similar issue with my Nexus 5, last week, actually.
EDIT: So, when you sideload or fastboot the system partition, it's stopping you? I may have sleep induced stupidity here and not fully taking in the issue but, I was able to flash 5.1.0 on my Nexus 5 after re-locking it via fastboot commands.
Click to expand...
Click to collapse
I get this error message "system partition has unexpected contents" (Status 7).
win465 said:
I was trying to sideload the new update and something wen wrong and it stopped updating. I tried to boot it up but now its just in a bootloop. I am completly stock and don't have TWRP. Is their a way to force unlock bootloader?
Click to expand...
Click to collapse
Can you fastboot boot twrp recovery? And if that is possible, will twrp flash zips with a locked bootloader?
Edit: I'm almost certain fastboot boot recovery won't work with a locked bootloader. I almost thought I had a good idea.
I am in the same situation. Bootloader locked and no custom recovery nor adb enabled. surprisingly enough, yesterday my phone could boot up but it's stuck now in the configuration process. I cannot access to the settings so I can check usb debugging or oem unlock. I can only access the dialer. my question is: is there anyway to do that with just a dialer code?
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Didgeridoohan said:
Just to clarify: you never need to relock your bootloader! Unless you have some kind of security restrictions from the company you work with or something, just don't!
OTA can be installed even with the bootloader unlocked (normal or sideload). The only prerequisite is that the system is stock (not rooted, stock kernel, stock recovery, and so on).
Click to expand...
Click to collapse
Sorry for the noob question but where can I find these OTAs and how to install one of them? Does it require usb debugging to be enabled?
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Rentom said:
I'm having an issue rooting my Nexus 6. I rooted it easily enough a couple months ago with the NRT. I recently used the Flash stock + Unroot options to upgrade to 6.01. However, when I tried rooting it again I ran into problems. I plugged it up, selected the root option, it tested ADB connectivity, booted into TWRP and that's when I ran into an issue. It told me then that ADB device was not found. I rebooted my phone and though I can boot into it, I now get a "your phone is corrupt" message when I turn it on. I tried again and has the same issue.
I followed the instructions it gave me about checking my drivers and they're fine. Anyone have any idea what's going on and how I can get around it? Also help removing the "your phone is corrupt message"would be cool too, but it's not a priority since it seems harmless and I'm sure I could find it easily enough with a little Googling, the other problem I have not been able to find an answer to though.
Click to expand...
Click to collapse
flash any custom kernel to get rid of that message
simms22 said:
flash any custom kernel to get rid of that message
Click to expand...
Click to collapse
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Rentom said:
Don't really have any desire to use a custom kernel, but I'll keep it in mind. I just don't know why it popped up now when nothing happened, but when I actually rooted the device I never saw that message.
Click to expand...
Click to collapse
because google put it there, it is new.
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
It was rooted with an older version of su. You probably said yes when twrp asked if you wanted to root it. Flash it back to stock, if you use nrt again select the no wipe option to save your data. And make sure your net is current. If you do it by hand skip the user partition.
When you root it male sure you use a newer su. 2.67 is the current version I believe.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
Yeah I let twrp root it when it asked when I did it two months ago. Was that a bad thing? I thought I read that it was if you were rooting 6.0.1, but I was rooting 6.0 so I decided to see what would happen, and it went smoothly.
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
TonikJDK said:
That is what is causing the corrupted message. It was an old version of su and it modified the system.
Sent from my Nexus 6 using XDA Labs
Click to expand...
Click to collapse
I see. Makes sense. Alright, thanks. I already did flash it back to stock to update to 6.0.1, so I'm not sure why you told me to flash it back to stock and then install su 2.67.
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Mongo23ny said:
I am also having this problem. Twrp will not let me flash a kernel or SuperSU. I went back to stock recovery and tried to root using cf auto root. But no luck. Phone runs fine, I upgraded to 6.01 with adb and did not flash user data. Any help would be greatly appreciated.
Click to expand...
Click to collapse
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
simms22 said:
flash twrp again, pick the kernel and SuperSU, then flash in twrp. if you can't pick them, make sure that twrp is mounted. and you DID NOT use adb to boot 6.0.1, you used fastboot, that is different than adb.
Click to expand...
Click to collapse
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Mongo23ny said:
I can pick them both, when I swipe to flash it just goes back to the teamwin start up screen. Tried many, many times.
Click to expand...
Click to collapse
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Tried flashing twrp a couple of times, went back to stock recovery and then twrp. No luck. Also, phone will not boot with custom recovery only with stock. Not sure if I tried 3.0.0.0
simms22 said:
OK, try flashing twrp again, maybe it just errored. flash twrp version 3.0
Click to expand...
Click to collapse
Do I keep system read only in twrp 3.0?
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
no, do not keep system read only, ever.
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
Thanks for all your help, did a clean install, fastboot flashed 6.01. I had gotten that corrupt phone message when I rebooted again but I took some security update and that got rid of the message. I flashed twrp 3.0.0.0 and SuperSU 2.67 and got root back. No worries, thx again.
Mongo23ny said:
Do I keep system read only in twrp 3.0?
Click to expand...
Click to collapse
simms22 said:
no, do not keep system read only, ever.
Click to expand...
Click to collapse
If you are using the systemless root method then yes, you do want to keep system read only.
alryder said:
If you are using the systemless root method then yes, you do want to keep system read only.
Click to expand...
Click to collapse
I kept it in read only, installed SuperSU 2.67 in twrp.
bootloop. & bootloader is locked. And I do not have usb debugging enabled. Any way to get around this?
Depends... You're quite sparse with information about what you've done to get to where you are and about your setup.
A few options come to mind. If you have TWRP you can try flashing a custom rom zip and that could fix it. You could also try the special N preview OTA that google provided to fix phones that got screwed up by an N OTA. http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Yeah sorry about that. While updating to 6.0 the phone died. And is now stuck in a bootloop (stuck at the google logo screen). I was trying to use nexus root toolkit to flash stuck android back onto it, however my bootloader is locked. And I did not have usb debugging enabled either. So I am trying to find a way to unlock my bootloader. If that makes any sense
Use the second method I suggested. Should work.
Can you get in bootloader or recovery mode?
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Try to sideload shamu-ota-npc91k-201dd8d1.zip. (This upgrades to Android N Preview.)
Since the OTA is a complete image, it should restore the device to working condition. Then you should be able to enable USB debugging and OEM unlock so the bootloader can be unlocked through fastboot.
Sorry for the late replies. I am attempting the second method & I am able to boot into recovery mode. However I keep getting "adb server is out of date" so I am trying to work it out at the moment
This worked for me! Locked bootloader, no usb debugging, no custom recovery, stuck in bootloop due to software issues.
Bootloader showing engineering
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Warhammer143 said:
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Click to expand...
Click to collapse
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
simms22 said:
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
Click to expand...
Click to collapse
tried many things but not sure..
Is there any thread where I can find the instructions???
Warhammer143 said:
tried many things but not sure..
Is there any thread where I can find the instructions???
Click to expand...
Click to collapse
well, instructions, probably not. if its a flashable zip, that means that you can use twrp recovery to flash it. fastboot flashing has to be done while youre in the bootloader, using fastboot. the command is.. fastboot flash bootloader zipname.img
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Warhammer143 said:
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Click to expand...
Click to collapse
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
simms22 said:
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
Click to expand...
Click to collapse
Well, I will be searching on google, but thanks a lot!