Related
Hi,
I installed a while ago 4.3 GE (rooted) for OTA updates. Everything seemed fine. Today i got the 4.4 OTA update so OTA does work. I rebooted the phone so it could install. The installation stopped after a while and gives the error: no command. After 30 seconds it reboots and gives this error again. Over and over again
I did not make a backup of my data on the phone. The default recovery mode is not available, this also gives the no command error. Fastboot does work.
I'm S-OFF and LOCKED.
What to do?
Someone got this working with Nexus 7 2012. But i need the OTA 4.4 file and ADB sideload needs to work...
Are you able to unlock bootloader using fastboot oem unlock ?
SaHiLzZ said:
Are you able to unlock bootloader using fastboot oem unlock ?
Click to expand...
Click to collapse
Yes, i used the unlockcode. Created a new one via htcdev. Bootloader is now unlocked. Try to reflash 4.3 recovery, flash is ok but still can't start recovery. I wanted to try to start normal recovery and use adb sideload to transfer files from sd to pc. Also tried to flash twrp and CWM but found no solution to transfer my files?
Try fastboot boot customrecovery.img
Also once you are in recovery, your device will show up under adb devices. Then you can adb push yourromname.zip /data/media/
SaHiLzZ said:
Try fastboot boot customrecovery.img
Also once you are in recovery, your device will show up under adb devices. Then you can adb push yourromname.zip /data/media/
Click to expand...
Click to collapse
Which customrecovery? Can i also transfer my data (pictures?) from sd to pc?
Use CWM if you wish.. http://forum.xda-developers.com/showthread.php?t=2173863
You have to use adb pull /data/media/DCIM/ if your pics are stored in DCIM folder.
This is DEPENDENT on your phone connecting and responding to ADB..
SaHiLzZ said:
Use CWM if you wish.. http://forum.xda-developers.com/showthread.php?t=2173863
You have to use adb pull /data/media/DCIM/ if your pics are stored in DCIM folder.
This is DEPENDENT on your phone connecting and responding to ADB..
Click to expand...
Click to collapse
OK thank you, i will try this tomorrow. I also found how to enable USB debugging through CWM . I think i will need that too.
I wouldn't do that. I have no idea what will it do to your phone. If you are not sure of ADB commands you can get in a bind. Unless you are doing a crash course on ADB&Fastboot tonight?
SaHiLzZ said:
I wouldn't do that. I have no idea what will it do to your phone. If you are not sure of ADB commands you can get in a bind. Unless you are doing a crash course on ADB&Fastboot tonight?
Click to expand...
Click to collapse
Ok, i only will try to do that when ADB not works. I think ADB only works when USB debugging is enabled in Android. But i can't start Android.
What do i have to start in CWM to use ADB?
mderksen said:
Ok, i only will try to do that when ADB not works. I think ADB only works when USB debugging is enabled in Android. But i can't start Android.
What do i have to start in CWM to use ADB?
Click to expand...
Click to collapse
Same trouble here? Have you figured it out yet?
bluestar23 said:
Same trouble here? Have you figured it out yet?
Click to expand...
Click to collapse
ADB was working, but i could not get my files off the phone. Tried to transfer files with ADB but it could not find the directories. So i gave up and i just flashed the 4.4 (non-root) RUU. The phone is working now but i lost my files
mderksen said:
ADB was working, but i could not get my files off the phone. Tried to transfer files with ADB but it could not find the directories. So i gave up and i just flashed the 4.4 (non-root) RUU. The phone is working now but i lost my files
Click to expand...
Click to collapse
You are lucky. I relocked it... So as of now, I cannot even flash TWRP for any rom...
mderksen said:
Hi,
I installed a while ago 4.3 GE (rooted) for OTA updates. Everything seemed fine. Today i got the 4.4 OTA update so OTA does work. I rebooted the phone so it could install. The installation stopped after a while and gives the error: no command. After 30 seconds it reboots and gives this error again. Over and over again
I did not make a backup of my data on the phone. The default recovery mode is not available, this also gives the no command error. Fastboot does work.
I'm S-OFF and LOCKED.
What to do?
Someone got this working with Nexus 7 2012. But i need the OTA 4.4 file and ADB sideload needs to work...
Click to expand...
Click to collapse
Paste your getvar all
I'm sorry to do this, but I don't know where to start. Here's what I did to get to where I'm at:
- previously running SlimBean flashed using TWRP
- Downloaded ROM Manager and it recommended installing CWM Recovery
- Followed prompts
- It installed CWM 6.0.4.8
- Booted back into ROM and used ROM Manager to attempt to flash SlimKat 4.4.2 build 6
- CWM wiped dalvik but then got hung up
- Now it keeps saying Can't mount /cache/recovery/command
I'm completely stuck. Can't figure out what to do next. Please help!!!
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
dougeedug said:
Have you tryed reflashing the recovery to rule out a faulty install of cwm?
I should say, have you tried reflashing cwm *through Fastboot* to rule out a faulty cwm install?
Click to expand...
Click to collapse
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Seanie280672 said:
Use TWRP recovery, preferred is 2.6.3.3 although there are newer versions, enter recovery, wipe - format data, basically for some reason, fastboot erase cache wipes the cache into an un-readable format.
note: this will also erase your internal storage too, so if theres anything important you want on there, make sure you back it up first using the adb pull command.
Click to expand...
Click to collapse
I can't quite risk doing this yet. Only as a last, last resort...
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
I can't quite risk doing this yet. Only as a last, last resort...
Click to expand...
Click to collapse
whilst your phone is in recovery and plugged into your computer, open device manager, is there a yellow ! where its says android devices or myHTC ?
IGNORE THIS, You got it working whilst I was typing this.
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed.
Click to expand...
Click to collapse
Use the command "fastboot devices" from the bootloader with "fastbootUSB" highlighted. You can't use adb commands in the bootloader because adb is to interact with android, which is not running while in bootloader. Let me know if you get output with the "fastboot devices" command.
EDIT: I should specify, if you are trying to flash recovery from anywhere but the bootloader using fastboot commands (it sounds like you may be trying to flash recovery with adb commands), you are just doing it wrong. so lets get that sorted first.
cartisdm said:
I can't get it to recognize my devices in order to use ADB. When connected, I type ADB Devices and I don't see anything listed. Is there a way to check I'm doing this ok?
EDIT: Ok, I got it to recongize my device. I'm going to try flashing TWRP thru ADB....will report back shortly...
Click to expand...
Click to collapse
you flash a custom recovery with fastboot commands not adb commands.
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
cartisdm said:
Got it!!! Thank you everyone for taking the time. I have a flight in a few hours and I was panicking!!!!
I grabbed universal drivers from here: download.clockworkmod.[com]/test/UniversalAdbDriverSetup6.msi (remove the brackets around .com)
Then my computer picked up the device and I was able to install TWRP. Clockworkmod recovery still doesn't work, no matter which version I tried. I'll stick with TWRP for now.
Thanks again!
EDIT: Well eff me, it wiped my internal storage. It must have done it after I flashed because that's where I grabbed the zip in the first place. That sucks...
Click to expand...
Click to collapse
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Seanie280672 said:
did you format data inside twrp recovery, like I said above, that will erase your internal storage too, you will need to push a rom over to your internal storage now using adb and then flash it.
Click to expand...
Click to collapse
I didn't do so intentionally, but it's possible I did it without paying attention. I'm back to my system now so I'll just live with the loss. I flashed an existing ROM that I had in my Downloads folder once I was able to get into TWRP. It's just weird that folder is empty now.
So this is a bit of a comedy of errors on my part...
I took the OTA update to lollipop and (foolishly) followed the same method as on KK to get root, putting myself in a bootloop. I got myself out of it by clearing the userdata and the cache.
I went about sorting everything and achieved root using the chainfire method, that was fine and I then went about reinstalling the xposed modules I had before. Foolishly, I didn't double check the status of xposed on Lollipop and consequently put myself back in a bootloop (idiot). I redid what had worked earlier, clearing the userdata and the cache to no avail.
Obviously, the problem was not the same as before and I needed to disable xposed, but in clearing the userdata I not only removed the xposed_disable.zip file to do this and also turned off adb so I can't push it.
The bootloader is fine and I can use fastboot, but can't push anything across. I hadn't replaced the recovery but can boot into twrp. However, I cannot flash it because I cannot push it over using adb.
I can't work out exactly how far I need to go back/what exactly I need to flash in order to put this all back together again.
I would be very grateful for any help that people can give on this.
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
LiamAtkins90 said:
Oh man.... This post made me giggle.
Right first of all what device do you have?
Anyway to connect a flash drive to the USB or a Micro SD and flash a new ROM in recovery?
Sent From N5
Click to expand...
Click to collapse
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
prasad.adam said:
All you need is ability to enter fastboot. Using Multitool or manual fastboot flash commands, you should be able to go back to stock KK. From there on you can flash stock L. Root it.
Do not have access to Multitool runme.cmd file at the moment to confirm that all you need is ability to issue fastboot command. adb is not needed. But am almost certain that this is the case.
Click to expand...
Click to collapse
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
HamRack said:
It's a 2014 Moto X, the XT1092 (bought straight from Motorola - I think that makes it the pure edition).
I have tried the Multitool (as in here) but it would always throw me errors and never showed up anything on the fastboot console. I expect I probably need to get the stock image from Motorola (I've requested access to this which is the top option from here) and issue the fastboot commands by hand which seems to work. I'm mostly just unsure about what exact commands I need to give to make sure I don't forget to flash a particular part. I haven't gone this far on other phones and have normally worked from CWM but I can't even flash that/TWRP at the moment.
Thanks for your help guys!
Click to expand...
Click to collapse
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
HamRack said:
Would it need to be an SD card or just a usb stick formatted correctly?
This sounds the best idea yet, now just to track down a USB OTG cable...
Click to expand...
Click to collapse
SD card is OK. As USB disk,haven't give a try.
Ok, cheers. I'll get a usb otg cable and give it a go.
HamRack said:
Ok, cheers. I'll get a usb otg cable and give it a go.
Click to expand...
Click to collapse
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed. You should check the directory first, moreover, that file was released for those KK users. I have no idea whether it would take effect on lollipop or destroy your system. Take your own risk.
purejoy said:
Normally Xposed installer would put a copy of Xposed-Disabler-recovery.zip under directory /sdcard after being installed.
Click to expand...
Click to collapse
So I found, but because my first reaction to the second bootloop was to erase userdata (as had fixed the earlier one) I lost that.
purejoy said:
1.Download the latest TWRP recovery. 2.Prepare a SD card with a card reader and format it to ext4,then put Xposed-Disabler-Recovery.zip in it.
3.Boot your phone to ap fastboot mode,then open a cmd prompt and issue: fastboot boot TWRPimgfilename
3.link your phone to the card reader with otg cable and mount the SD card via TWRP advanced menu.
4.Flash the Xposed-Disabler-Recovery.zip via TWRP.
Click to expand...
Click to collapse
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
HamRack said:
Hi,
Tracked down a usbotg cable and have booted into TWRP. When I plug in the sd card using the cable, I don't find anything to mount the sd card in the advanced menu of TWRP, but I do find a 'mount' option on the main menu
(as you can see here). Under there is a tick box for 'USB-OTG' which I have ticked, but I can't find where it actually is in the filemanager/when I select 'install'...
Any suggestions?
Click to expand...
Click to collapse
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
---------- Post added at 01:29 AM ---------- Previous post was at 01:07 AM ----------
HamRack said:
Realised what I had done, managed to flash the xposed_disabler zip, but it didn't work.
However, I was pointed in the direction of this where I downgraded to KK 4.4.4. That seems to have done the trick at getting me back to a working device. Out of curiosity, does anyone know a reason why I shouldn't get have the Lollipop OTA come through again in due course? When I check for updates it says I am up to date - is the only way I will get L by way of sideloading?
Finally, thanks for all your help, you've been very patient with my dangerous level of knowledge - enough to do plenty of damage but not enough to fix it!
Click to expand...
Click to collapse
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Sorry for not reading all the reply's in this thread before posting (i'm in a bit of a rush)
I got a bootloop while applying the OTA on a brand new XT 1092 right after taking out of the box. After some digging around the forums (you can tell i'm new by the post count) i managed to get an OTA zip for my DE version and pushed it via ADB using stock recovery, with a few hickups:
- had to manually install the driver in windows
- first time the install via ADB push failed with some assert failure on something related to moto.odex
- the second try went ok and got the bootloop sorted.
So definitely give ADB a shot
Good luck!
First, try to recover as much as of your data stored on the device .
Then reflash the old ROM. You'll need a specific program for that - and a PC Surely! ☺
After that to get easier Back-Ups - i recommend unblocking the bootloader.
All the best☻.
purejoy said:
You were expected to use the latest TWRP which is 2.8+,at least 2.7. Anyway,that's not important.
Click to expand...
Click to collapse
I used TWRP 2.8.1.0, I downloaded it that day. Not sure what else it could have been...
Did you get an error after issuing "fastboot flash motoboot motoboot.IMG"?
Click to expand...
Click to collapse
Not sure when I was supposed to do that, couldn't see that in your directions...? Not a really a problem either way as its now sorted.
Cuz you succeeded in updating, the OTA has upgraded your bootloader. Although you have downgraded your system, the BL can't be,hence when you try to accept another OTA, there will be a verification error.
Now You need flash a custom OTA pack via a 3rd party recovery. Some verifications must be removed from the official OTA zip.
You can also wait for someone to backup and share the images of the new system.
I think you can have a try to download the .19 OTA zip and put it under /sdcard, then reboot into stock recovery to apply update from SD card or adb sideload. If there's no errors while verifying, you would get lollipop again.
Click to expand...
Click to collapse
Ok, thanks for the info. Any idea how to remove those verifications? Would this do the required thing?
Also, what exactly do you mean by the .19 OTA zip? You mean the OTA zip with the new bootloader in with it? If it has an error while trying this, would it give problems or just stop and return as before?
Thanks
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
purejoy said:
Sorry, i have stayed up too late last night. You know there is time difference.
i dunno the differences between GB version and EU version, since you have a system of EU, maybe you should refer to this thread http://forum.xda-developers.com/moto-x-2014/general/ota-zip-moto-x-2014-xt1092-5-0-t2970818
Hmm,there is a better choice. Seems that moto has released the stock 5.0 firmware for GB xt1092. http://forum.xda-developers.com/showpost.php?p=57591807&postcount=36
Download it and make a full recovery.
BTW: Please backup your data first.
Click to expand...
Click to collapse
I'm not sure of the differences either...
So I'm wanting to make sure I do this correctly this time. I know a couple of ways of backing up but after all the faff recently I want to have an ironclad backup before I piss around with anything else (foolish me for not doing so before). Can you clarify the best way to back up my device and how I would do that? I have a feeling I haven't been doing it correctly/the most ideal way before and it would be good to know.
Also, how would I go about putting that backup you've pointed too (thank you for finding that, I don't think I'd been searching for quite the right thing) on to my device? Would I go through a similar series of steps to how I recovered my phone before (ie here)?
I'm going away for xmas/NY and will probably do this when I get back so I don't risk borking my phone when I need it most. Nonetheless, it would be good to have things ready to roll when I get back.
Thanks for your help, you've been great.
It depends on what you plan to backup and i don't konw what app your are using. If you use Google service, Contacts and some app data are normally synced to Google Cloud Servers. You can get them back in lollipop 5.0 via your Google account. As your pictures and videos,you can also directly copy them on your PC. What you need to backup are private app data and private messages. You can use some 3rd party backup apps like TitaniumBakcup to solve this. If there are not so much user data, you can backup like this.
You can also backup and restore your userdata via TWRP. If you get so many data, you can try this.
As the full stock recovery,you can restore your phone via fastboot utility or RSD lite.
1.Download and Unzip the image.
2.Put your phone in AP Fastboot Mode.
3. $ fastboot flash partition gpt.bin
$ fastboot flash motoboot motoboot.img
$ fastboot reboot-bootloader
$ fastboot flash logo logo.bin
$ fastboot flash boot boot.img
$ fastboot flash recovery recovery.img
$ fastboot flash system system.img
$ fastboot erase modemst1
$ fastboot erase modemst2
$ fastboot flash fsg fsg.mbn
$ fastboot -w (Erase userdata. Optional,maybe unnecessary)
$ fastboot reboot
I would advise you to put off erasing data. If you get any issues while rebooting into new system, then you can erase your data.
Hope these help. Good Luck!
Great, thanks for the tip.
I tend to have minimal important data on my phone that isn't covered by either google or evolvesms/whatsapp. Nonetheless, thanks for the tips. I've been using titanium for a long while and have that backed up to dropbox too.
I tried flashing TWRP after I fixed the clusterbadger that was the last few days, but had no luck. I still don't seem to be able to push the image over using adb nor use adb to issue commands while booted into TWRP through fastboot. Have you experienced that? I guess worst case is that I copy the zip to an sdcard and flash it from usbotg by issuing commands in the TWRP shell they give you...?
Thanks for the tip on the userdata too.
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
evan7899 said:
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
Click to expand...
Click to collapse
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
simms22 said:
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
Click to expand...
Click to collapse
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
evan7899 said:
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
Click to expand...
Click to collapse
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
simms22 said:
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
evan7899 said:
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
Click to expand...
Click to collapse
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
simms22 said:
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
Click to expand...
Click to collapse
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
evan7899 said:
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
Click to expand...
Click to collapse
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
simms22 said:
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
Click to expand...
Click to collapse
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
evan7899 said:
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
Click to expand...
Click to collapse
honestly, I wouldn't know what you need on a Mac to get it working :angel:
simms22 said:
honestly, I wouldn't know what you need on a Mac to get it working :angel:
Click to expand...
Click to collapse
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
evan7899 said:
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
Click to expand...
Click to collapse
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
You need to run sudo fastboot insertcomand on Mac. good luck.
simms22 said:
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
Thanks but we have tired that. Due to distance this has all had to be over the phone which hasnt helped either. I will update this with how we got it working when we do.
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
To clarify:
- I already tried erasing userdata and cache from fastboot
-I already tried flashing recovery images from twrp, stock and bluspark
Thanks in advance guys.
Pavononer23 said:
Hi everyone.
I was trying to flash Nitrogen OS. First I flashed the latest firmware, then the actual rom and then GAPPS. After that my mobile got stuck in Oneplus logo without being able to go into recovery mode.
I tried using fastboot to flash the files in this thread(https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306) which worked once, but even after that I can't surpass the logo screen.
I've been trying to look for information but I can't find anything.
Thanks in advance guys.
Click to expand...
Click to collapse
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
rykanator said:
Which TWRP are you using? Which firmware are you flashing? You can't access recovery at all? I've run into plenty of bricks like this and I'm usually able to get back to recovery by forcing the device off (vol up + power hold) and rebooting back to recovery. and if that doesn't work I can at least get to the bootloader and re-flash a recovery file.
Click to expand...
Click to collapse
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Pavononer23 said:
I was using last bluspark recovery. I was flashing OB21 when everything happened.
There is no way I can access to recovery. I tried reflashing the stock recovery from that unbricking thread with all the other things through fastboot and I can't boot into recovery at all. It is the first time I face this error so I am lost.
Click to expand...
Click to collapse
can you boot into the bootloader/fastboot?
rykanator said:
can you boot into the bootloader/fastboot?
Click to expand...
Click to collapse
Yes I can
Pavononer23 said:
Yes I can
Click to expand...
Click to collapse
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
rykanator said:
okay, well what I would do is boot into the bootloader, and then reflash the blu_spark recovery via adb so you can boot into it. then wipe everything and restart. but this time I would try the OB 20 firmware and not the 21. when I was on NOS I used that one and it worked just fine. I'm not sure if it made a difference, but I flashed the firmware both right before and right after flashing NOS
Click to expand...
Click to collapse
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Pavononer23 said:
It doesnt recognize my device through adb and I don't know why. If that worked I would have tried to sideload some firmware, but when I do adb devices it doesn't appear
Click to expand...
Click to collapse
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
rykanator said:
idk if it'll recognize as an adb device if it's in the bootloader. maybe try fastboot devices? sorry, I'm just spitballin here
Click to expand...
Click to collapse
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Pavononer23 said:
Somehow fastboot devices does send me that my device is there but adb devices no, I will try looking into that to see if that works. Thanks for the help anyway
Click to expand...
Click to collapse
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
rykanator said:
yeah! try fastboot flash recovery "recovery file name".img
make sure that recovery img file is in the platform-tools file (or wherever your adb files are) and see if that works!
Click to expand...
Click to collapse
It is not working, I think I lost my Oneplus 3t...
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
I mean idk if you wanna do this, but you could always try to "format userdata", then flash the stock recovery, and then sideload OOS. but you would lose all of your data in your internal storage, and it's still not a guarantee. there are some posts about doing a full wipe and starting from scratch. I'd look into those. Best of luck reviving your OP3T
Pavononer23 said:
It is not working, I think I lost my Oneplus 3t...
Click to expand...
Click to collapse
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
nicknacknuke said:
just a tip, try posting the output instead of "it's not working",
so the devs here might be able to analyze the problem..
Click to expand...
Click to collapse
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
pitrus- said:
Then just do the Qualcomm restore and unlock, boot to fastboot and flash the latest TWRP. Then boot into TWRP and format cache partitions, system and data and then adb sideload using this option under TWRP advanced to flash firmware zip, NitrogenOS zip and then 8.1 Gapps and try booting to see if same thing happens again. You are using the NitrogenOS stock kernel and not some other?
Click to expand...
Click to collapse
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Pavononer23 said:
What do you mean by the Qualcomm restor and unlock? I already tried the flashing of latest TWRP and it did not work.
I was coming from Validus last beta but did a previous factory reset and that stuff.
Thank you for the answer
Click to expand...
Click to collapse
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
przemcio510 said:
What he meant is probably unbrick tool - https://forum.xda-developers.com/oneplus-3t/how-to/unbrick-unbrick-tutorial-oneplus-3t-t3515306
Try flashing official firmware with it and then try again by flashing TWRP and flashing Nitrogen.
Click to expand...
Click to collapse
I can't install the drivers:
-First, stupid Windows policy saying that its driver is the best one available.
-Second, choosing from a disk to avoid one saying that the driver is not a x64 one.
Pavononer23 said:
I already post a lot of information on the first post:
Mobile not passing the first time Oneplus logo appears.
Only fastboot is working, not adb, not recovery.
I already tried flashing other recoveries and the stock one->Can't pass Oneplus logo anyway
Tried formatting userdata through fastboot and flashing the .img files from my first post->Not working
Click to expand...
Click to collapse
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
redpoint73 said:
None of that answer what he actually asked, which is: what was the output (error message, result, etc.) when you tried to flash TWRP?
Did it flash successfully, but still can't boot to TWRP? Or else, what was the exact error message?
In general, when asking for help and giving status, be specific as possible, and give as many details as possible. Saying you "tried xxx" or "it did not work" is not specific enough.
Seems silly, but I've seen a lot of times where it's as simple as the user not using the correct command or entering the right file name.
Click to expand...
Click to collapse
There were no errors when flashing TWRP. When I tried rebooting using fastboot(fastboot boot recovery.img) it got stuck in the message saying booting up... and the only thing that changed was that my phone left the bootloader screen to a screen with the Oneplus logo and a fastboot mode message under it.
The command I used was fastboot flash recovery recovery.img(Name of the actual recovery file)