Related
Guys i have managed to brick my device while trying to flash cm11 i need help ASAP please i have tried to sideload a rom using TC One Toolkit [M8] - v1.1 OTA which i found on xda i have added link below. Every time i sideload a rom it fails but i can locate the sideload zip in the file manager on twrp and I can atempt to flash it but it keeps failing all the time.
link to xda tool.[TOOL] HTC One Toolkit [M8] - v1.1 OTA - xda-developers
I appreciate all help.
my phone is the uk version locked to ee
Never mind guys got my self out of the hole I think i was doing something wrong.
So happy i got my phone un bricked.
Why would you want to sideload a ROM? I thought you could only sideload apps.
Nowhere in the install instructions does it say to sideload.
Reboot into recovery and install the CM11 zip file as normal, do not sideload, follow the instructions on the first post to install correctly.
Root Newb said:
my phone is the uk version locked to ee
Click to expand...
Click to collapse
Don't use side load. First clear cache, go to boot loader
fastboot erase cache
load twrp and don't do anything. on your computer
adb push rom.zip /sdcard/
This will push the rom to your phone. After initiating the command wait for the prompt to come back up so you know the full rom transferred. It takes a while. 400+ seconds for 1.5 gigs. Once prompt is back up, go to wipe and click on advanced, choose dalvik, cache, system, data. Do not select internal storage. Wipe. Go to install and choose the rom you pushed over. Let me know your outcome.
---------- Post added at 07:37 PM ---------- Previous post was at 07:37 PM ----------
allen175 said:
Why would you want to sideload a ROM? I thought you could only sideload apps.
Nowhere in the install instructions does it say to sideload.
Reboot into recovery and install the CM11 zip file as normal, do not sideload, follow the instructions on the first post to install correctly.
Click to expand...
Click to collapse
You can side load anything.
---------- Post added at 07:40 PM ---------- Previous post was at 07:37 PM ----------
Root Newb said:
Never mind guys got my self out of the hole I think i was doing something wrong.
So happy i got my phone un bricked.
Click to expand...
Click to collapse
3 posts in 10 min and you fixed it? You should get rid of the toolkit and learn a couple adb/fastboot commands. They are very simple to use and once you understand them, you can get your phone out of almost any so called brick.
So you can boot into twrp? If so it's not bricked. The toolkit probably isn't doing the full transfer for some reason. Just go into twrp advanced settings and select adb sideload. Then use adb to sideload the rom. First place the ROM zip in you abd folder on the computer. Then you choose the sideload option in recovery and connect the phone to the computer. Now type in adb devices to make sure it's connected. Once it shows as connected type adb sideload filename.zip
Replace filename with the actual name of the zip file when sideloading the file. Once it's completed the file will be on the root of your internal storage. Now flash the zip and hopefully all goes well
Sent from my HTC One_M8 using XDA Free mobile app
otariq said:
So you can boot into twrp? If so it's not bricked. The toolkit probably isn't doing the full transfer for some reason. Just go into twrp advanced settings and select adb sideload. Then use adb to sideload the rom. First place the ROM zip in you abd folder on the computer. Then you choose the sideload option in recovery and connect the phone to the computer. Now type in adb devices to make sure it's connected. Once it shows as connected type adb sideload filename.zip
Replace filename with the actual name of the zip file when sideloading the file. Once it's completed the file will be on the root of your internal storage. Now flash the zip and hopefully all goes well
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
Yeh got it working i think it was not doing a full transfer.
So, I have read several threads and feel that a solution is there, but I just can't seem to find the detailed instructions on how to fix it. Apologies if I have missed it and you can direct me to that one.
I have tried the xperia companion software recovery and the software update two different times. Both times they said it was successful. However, the watch would still get stuck on the 4 symbols or dots.
I tried doing the factory reset on the watch itself, but that did not help the booting process.
When I press the recovery, I get the android guy laying down with a red exclamation mark in a red triangle.
It appears that fixing it can not be done on win 10, but I do have access to a pc with ubuntu/linux that I have used.
Since I'm getting the red triangle, I'm guessing the OS is corrupt.
Any detailed instructions or pointing me to a proper thread would be appreciated.
That's a bootloop.
In recovery: swipe the guy away (from top to bottom works best). Then you should see the menu.
ranf said:
That's a bootloop.
In recovery: swipe the guy away (from top to bottom works best). Then you should see the menu.
Click to expand...
Click to collapse
Hey, thanks. So, I see the menu. I did the wipe data factory refresh and still nothing except the 4 symbols grinding away.
So, is see a "mount" option. I'm guessing that is where the watch is then mounted as a drive to a pc where where one could have files transferred from the pc to the watch. Would that be the next step or do I need to perform the partition option on the watch?
Sorry, I just am trying to get detailed instructions. BTW, I did notice that the OS is 6.0.1. I have read that many have downgraded to 5.1.1 as it may have been better for gps and battery life. Also, that is when this watch crashed was during the update.
Any detailed instructions from here would be greatly appreciated...again. Thanks
When a factory reset doesn't help it, the easiest way is the "repair" option in Xperia Companion. Basically it downloads the complete firmware (200-250MB) and flashes all the partitions. Very much like a factory image for a Nexus.
I don't know what mount actually does.
ranf said:
When a factory reset doesn't help it, the easiest way is the "repair" option in Xperia Companion. Basically it downloads the complete firmware (200-250MB) and flashes all the partitions. Very much like a factory image for a Nexus.
I don't know what mount actually does.
Click to expand...
Click to collapse
Thanks. As mentioned in the original post, that was tried...now three times to no avail. I did both options in the repair area of xperia. So, I'm guessing there is a more serious hardware issue or I need to somehow use something other than the xperia companion to remedy the situation. I had also tried the update again and it said it was successful, but there was not difference in the behavior of the watch...just the 4 dots/symbols going on forever.
I'm willing to root the device, but I just have not seen or probably better stated, understood how to do it. I am sort of a newbie and thus need detailed instructions. If the watch is bricked after that, then so be it. It is not doing any good right now anyways. Can some even point me to such a thing or help in writing it down?
Perhaps a stupid question, but after doing the repair thru xperia, I let it sit and grind for a good 20 minutes. I presume that is ample time for it to repair itself. Is that reasonable?
Repair is not the same as update in XC.
ranf said:
Repair is not the same as update in XC.
Click to expand...
Click to collapse
Thanks. Agree which is why I mentioned both the repair and the update were done on the watch and of course separately on XC.
So, basically, I have tried every option in xperian companion (repair and update) and the factory reset, clear cache and the partition option that come up on the watch itself. So, my next thougt was the to root it and try either downgrading the os or repairing in thru the root process. If someone could provide either a link or help with very detailed directions (for the complete idiot) on how to root it with that idea of replacing or repairing the os, that would be very much appreciated.
golfnut22 said:
Thanks. Agree which is why I mentioned both the repair and the update were done on the watch and of course separately on XC.
Click to expand...
Click to collapse
That wasn't so clear for me.
golfnut22 said:
So, basically, I have tried every option in xperian companion (repair and update) and the factory reset, clear cache and the partition option that come up on the watch itself. So, my next thougt was the to root it and try either downgrading the os or repairing in thru the root process. If someone could provide either a link or help with very detailed directions (for the complete idiot) on how to root it with that idea of replacing or repairing the os, that would be very much appreciated.
Click to expand...
Click to collapse
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
golfnut22 said:
Since I'm getting the red triangle, I'm guessing the OS is corrupt.
Click to expand...
Click to collapse
Can you post a photo of that?
ranf said:
That wasn't so clear for me.
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
Thank you. And, sorry for the senior memory moment. I could not remember if it was recovery or repair in XC. Anyway, I think it is fair to say that I have tried every "canned" option in either XC or on the watch for recovery, repair and update to no avail.
Nice and thanks for the coding. I will also take a hard look at the links to see if I can proceed. When I fixed my HP Touchpad, there was a nice little toolbox that one could use to easily do a complete data reset, then load the three files and it would do the rest. That was all done in Ubuntu.
I'll report back once I get going.
Is it fair to say that as long as you do not mess with the bootloader, that you cannot brick the watch? After reading 12 or 13 threads, that seemed to be one of the comments. I did look at all the thread titles...17 pages to try and find things that were similar and they pointed to what we have already discussed in using XC, etc. So, I'll try another way that is outlined above.
I have attached the picture of the android guy with exclamation mark. Hopefully you will be able to see it.
golfnut22 said:
Thank you. And, sorry for the senior memory moment. I could not remember if it was recovery or repair in XC. Anyway, I think it is fair to say that I have tried every "canned" option in either XC or on the watch for recovery, repair and update to no avail.
Nice and thanks for the coding. I will also take a hard look at the links to see if I can proceed. When I fixed my HP Touchpad, there was a nice little toolbox that one could use to easily do a complete data reset, then load the three files and it would do the rest. That was all done in Ubuntu.
I'll report back once I get going.
Click to expand...
Click to collapse
Yes please do so.
golfnut22 said:
Is it fair to say that as long as you do not mess with the bootloader, that you cannot brick the watch?
Click to expand...
Click to collapse
You can play a lot with the watch without bricking. Doesn't mean it's impossible.
golfnut22 said:
After reading 12 or 13 threads, that seemed to be one of the comments. I did look at all the thread titles...17 pages to try and find things that were similar and they pointed to what we have already discussed in using XC, etc. So, I'll try another way that is outlined above.
I have attached the picture of the android guy with exclamation mark. Hopefully you will be able to see it.
Click to expand...
Click to collapse
A bit small but that's just the recovery droid?
To me that means more like "proceed with caution" than denoting a serious error condition.
ranf said:
That wasn't so clear for me.
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
Ok, so I downloaded 4 files. 2 of them were for two different cores: one was for 2 core and the other for 4 cores. Which one is proper or what's the difference for this watch?
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
Yes, got it and that was easy.
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
I tried the first command on the link two different times and I get vim: command not found. So I continued on.
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
If this procedure is done on the watch by holding the power button until you get the "insert usb" connection screen, then quickly tapping the power button twice to bring up the next four screens possible screens by pressing the power button 1 time to move to the next screen (fastboot, recovery, normal boot, factory reset), I went into the recovery screen and did the wipe cache partition first and then the wipe data/factory refresh.
However, if those steps above are to be done on the ubuntu, then I'm lost already.
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
If this is to see fastboot on the watch as one of the 4 screens noted above, that is easy. If it is to double press the power button while on the fastboot screen, I did that, but don't know what you mean by the next step..."check connection"
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
So assuming that I can eventually get thru step 4, how and do I get the watch to recognize or get the 3 files (assuming I do not need both the 2 and 4 core files)?
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
So, in the "previewing of my response or comments based on the instructions, it looks like I did not do the "multi-quote" correctly. I hope you can decipher what I said, as I have commented on the steps so far in your comment back to me and what I was able to do and not do at this point. I would appreciate any help you can further offer.
I went thru the whole process again or at least starting with the command "sudo -s". I got thru it all except when I tried to install the rom file with the signature check box checked, it failed. The first time I did it, I did not check the box, but when rebooting as noted above is just cycled thru twice then went to the android recovery guy.
"vim" is an editor. You can use any other (like nano or even gedit).
with "fastboot devices -l" you either get "offline" which means the udev rule doesn't work,
or you get an output starting with fastboot.
Most likely much easier:
Code:
sudo -s
fastboot devices -l
fastboot format cache
fastboot format userdata
fastboot reboot
exit
ranf said:
"vim" is an editor. You can use any other (like nano or even gedit).
with "fastboot devices -l" you either get "offline" which means the udev rule doesn't work,
or you get an output starting with fastboot.
Most likely much easier:
Code:
sudo -s
fastboot devices -l
fastboot format cache
fastboot format userdata
fastboot reboot
exit
Click to expand...
Click to collapse
OK, so not sure what the editor comment fix is, but I'll look into that later.
So, as mentioned I was able to get fastboot on the pc. However, the first time I entered "fastboot devices -1", it said waiting for device.
This morning when I read your new message, I did the sudo command to get fastboot again on the pc (I had already got the watch "running fastboot" per its screen), then entered "fastboot devices -1", and I get "invalid option -- '1'.
Also, after entering the first command "sudo -s", the next command line changed with the first word "root" and the end on the command line changed from ":~$" to ":~#".
golfnut22 said:
OK, so not sure what the editor comment fix is, but I'll look into that later.
So, as mentioned I was able to get fastboot on the pc. However, the first time I entered "fastboot devices -1", it said waiting for device.
This morning when I read your new message, I did the sudo command to get fastboot again on the pc (I had already got the watch "running fastboot" per its screen), then entered "fastboot devices -1", and I get "invalid option -- '1'.
Click to expand...
Click to collapse
That's a lowercase L (for longer output).
ranf said:
That's a lowercase L (for longer output).
Click to expand...
Click to collapse
I got vim working or at least loaded.
Yep, was using number 1 instead of small letter l. Thanks.
I ran thru the commands and on the writing cache at the end, it said "Failed (remote: Device locked)" . The same failure message was on the userdata command at the end. What should I do next
Edit: I found where you have to start with command "fastboot oem unlock" and enter it twice. Now I was able to wipe cache and userdata.
After performing the above fastboot commands and disconnecting watch. I powered up the watch and it is still cycling thru or stuck on the 4 dots or symbols. Sooooo,
I hate to keep asking, but is it correct to say I now need to repair/replace/update the OS? And if so, I'm not sure exactly how to do that. Can you advse?
Here I think are the next steps: (this was copied from your link above for MM)
Quote:
Installation:
Put ROM to your virtual SDCard
I don't know how to do this first step. Can you advise?
Boot into TWRP recovery
I don't know how to put TWRP on the watch unless it is part of the first step. Can you advise?
Select "Install", and choose ROM zip file
This appears easy after the step 1 and 2 above are complete.
After installation completed- reboot watch
If necessary - make full wipe
Quote:
Downloads
MWD49B
How would I know this is my watch? I have seen several different ones for the SW3.
I have downloaded all of the below files, but there are two that are similar. One is 4 cores and the other is for 2 cores. Do you know which one I should use or what the differences would be?
SWR50_6.0.1_MWD49B.zip v3
MEC24H
SWR50_6.0.1_MEC24H v2 (4 cores version)
SWR50_6.0.1_MEC24H v2 (2 cores version)
Recovery
TWRP recovery
1. boot TWRP: if it is a .zip unzip it. If it already is an .img file proceed.
2. sudo fastboot boot twrp.img
We don't install, only boot into it temporarily.
3. I usually see a new Nautilus (ubu filemanager) window pop up on my Ubuntu box (because MTP is enabled in TWRP)
4. you could now drag and drop the ROM.zip you want into that window.
5. now on the watch in TWRP select install
MWDxx MECxx are the build numbers. MWDxx being the newest.
2 or 4 cores doesn't make much of difference. The stock Sony kernel disables 2 cores (for powersaving reasons I suppose).
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
golfnut22 said:
Also, after entering the first command "sudo -s", the next command line changed with the first word "root" and the end on the command line changed from ":~$" to ":~#".
Click to expand...
Click to collapse
You ran a root shell. The prompt shows this with a #.
ranf said:
That wasn't so clear for me.
You can install this (Lollipop):
http://forum.xda-developers.com/smartwatch-3/orig-development/rom-sony-smartwatch-3-rom-t3367728
or this (Marshmallow):
http://forum.xda-developers.com/sma...sony-smartwatch-3-marshmallow-mec24h-t3382450
In Ubuntu you install fastboot this way:
Code:
sudo apt-get install android-tools-fastboot
You may want to create an udev rule, so that a normal user can access the watch in fastboot mode:
https://ranf.wordpress.com/2015/02/21/ubuntu-udev-rule-for-sony-smartwatch-3-swr50/
Otherwise you have to run fastboot with sudo.
I'd start with formatting cache and userdata:
1. get into recovery
2. from there get into fastboot (maybe it is called bootloader here, can't remember)
3. check connection
Code:
fastboot devices -l
4. format
Code:
fastboot format cache
fastboot format userdata
fastboot reboot
---------- Post added at 06:10 PM ---------- Previous post was at 06:07 PM ----------
Can you post a photo of that?
Click to expand...
Click to collapse
ranf said:
1. boot TWRP: if it is a .zip unzip it. If it already is an .img file proceed.
2. sudo fastboot boot twrp.img
We don't install, only boot into it temporarily.
3. I usually see a new Nautilus (ubu filemanager) window pop up on my Ubuntu box (because MTP is enabled in TWRP)
4. you could now drag and drop the ROM.zip you want into that window.
5. now on the watch in TWRP select install
MWDxx MECxx are the build numbers. MWDxx being the newest.
2 or 4 cores doesn't make much of difference. The stock Sony kernel disables 2 cores (for powersaving reasons I suppose).
---------- Post added at 04:21 PM ---------- Previous post was at 04:18 PM ----------
You ran a root shell. The prompt shows this with a #.
Click to expand...
Click to collapse
Again, thank you for being very patient with some very basic questions. Ok, so I think I'm getting close. However, here are more basic questions before proceeding.
1. The watch has been disconnected since the previous steps where I wiped cache and userdata and exited fastboot. I also used XC to see if it would repair and update. To my surprise, now both of those functions failed. Do I need to start all over with the "sudo -s" command and proceed to make sure? If not, where would I start?
2. What status is the watch in when I do your #2 instruction? Is it in the connect usb screen or in fastboot. I'm guessing fastboot.
3. The file I have downloaded is the img file. On your #2 instruction, in Ubuntu, where should the img file be located when I enter "sudo fastboot boot twrp.img". I'm guessing the desktop, but wanted to make sure.
4. After your step #4 of dragging the file, do I need to exit out of Linux fastboot, then disconnect the watch, then power down then up the watch to see "install" in TWRP?
2. yes "fastboot running"
3. my Downloads land in ~/Downloads.
just run
Code:
cd
cd Downloads
to go there and fastboot boot from there. If it's in ~/Desktop well then go there.
4. stay in TWRP
Twrp screen is on the watch.
However,on the pc, I did not get the new file manager to place the new rom zip file. So, I'm not sure where or how to get the zipped file in the "install" folder. Any ideas? Thanks.
With TWRP visibly on the watch now, at the same time, can I use the command in ubuntu "sudo adb sideload <rom.zip>? I've been trying to find ways to get the rom.zip file in the watch...although I have not tried anything yet.
golfnut22 said:
Twrp screen is on the watch.
However,on the pc, I did not get the new file manager to place the new rom zip file. So, I'm not sure where or how to get the zipped file in the "install" folder. Any ideas? Thanks.
Click to expand...
Click to collapse
Ideas? Always.
AFAIK you can adb into a running TWRP.
Try this:
Code:
sudo apt-get install android-tools-adb
adb devices -l
# if you "see" your watch
adb push ROMfilename.zip /sdcard/
Oh BTW: what's your Ubuntu version?
Code:
lsb_release -a
is telling you that.
SOLVED
I can't boot into recovery (op logo displayed for about 10 seconds, then the screen became black)
ore boot the system (op logo is displayed for about 0.1 seconds, then the screen became black)
i've already tried to follow the steps in Mega Unbrick Guide, but i can't "Make the device show as Qualcomm 9008" also after have followed the
appropriate guide)
please help me!
if someone succeeds to solve the problem i'll pay him/her via paypal
Thaks!!
Go to Oneplus website and download oxygen os version 3.2.4 OTA and flash that via adb sideload , also as a sidenote use your PC to boot into fastboot mode and try flashing the firmware that way if the first method doesn't work....
how?
Xceeder said:
Go to Oneplus website and download oxygen os version 3.2.4 OTA and flash that via adb sideload , also as a sidenote use your PC to boot into fastboot mode and try flashing the firmware that way if the first method doesn't work....
Click to expand...
Click to collapse
i can't flash via adb sideload because i have can't boot into recovery.
How can i flash into fastboot mode? what have i to tipe?
Plug phone into PC and type - adb reboot bootloader , this should enter fastboot mode then use the adb commands to flash the firmware which should be adb sideload oxygenos.zip just obviously rename the OTA zip file to oxygenos before running the command... Hope this helps buddy.
What were you doing actually? And is your bootloader unlocked?
Xceeder said:
Plug phone into PC and type - adb reboot bootloader , this should enter fastboot mode then use the adb commands to flash the firmware which should be adb sideload oxygenos.zip just obviously rename the OTA zip file to oxygenos before running the command... Hope this helps buddy.
Click to expand...
Click to collapse
I've tried, but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
cannot read oxigenos.zip
zTweaked said:
What were you doing actually? And is your bootloader unlocked?
Click to expand...
Click to collapse
yes, my bootloader is unlocked,
i've tried to flash via adb but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
"cannot read oxigenos.zip"
i've put the renamed zip on desktop and in "c\program files (x86)\minimal adb and fastboot" directory
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
TheReverend98 said:
yes, my bootloader is unlocked,
i've tried to flash via adb but after imput "adb sideload oxygenos.zip" command
appear this phrase "loading oxigenos.zip" and then an error:
"cannot read oxigenos.zip"
i've put the renamed zip on desktop and in "c\program files (x86)\minimal adb and fastboot" directory
Click to expand...
Click to collapse
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
[email protected] said:
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
Click to expand...
Click to collapse
yes, i'm running the command window from that folder where adb is,
but i've tiped
:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update oxigenos.zip
archive does not contain 'android-info.txt'
error: update package 'oxigenos.zip' has no android-info.txt
because i can operate only in fastboot mode
Are you sure you are typing it right because you keep typing oxigenos instead of oxygenos ...
Xceeder said:
Are you sure you are typing it right because you keep typing oxigenos instead of oxygenos ...
Click to expand...
Click to collapse
oh..sorry! sometimes when i write in english i do some errors with the letters
anyway, this wasn't the problem, 'cause i had renamed the rom's zip in the same way
now i'm booting cm, hope it works all right!
Go to blusparks kernel thread from there download the latest recovery. Boot your phone into fastboot, then flash that recovery. Boot into recovery then flash whatever you wish!
Here is the recovery:
http://forum.xda-developers.com/devdb/project/dl/?id=21065
TheReverend98 said:
oh..sorry! sometimes when i write in english i do some errors with the letters
anyway, this wasn't the problem, 'cause i had renamed the rom's zip in the same way
now i'm booting cm, hope it works all right!
Click to expand...
Click to collapse
Did it work??
Also I just wanted to ask. Were you on the Oxygen OS Community Builds when this happened?
AJay27 said:
Did it work??
Also I just wanted to ask. Were you on the Oxygen OS Community Builds when this happened?
Click to expand...
Click to collapse
yes, anyway, i solved the problem
how did you solved the problem? could you please explain? so that we can solve it if anyone of us faces this problem...
solving
sahed01 said:
how did you solved the problem? could you please explain? so that we can solve it if anyone of us faces this problem...
Click to expand...
Click to collapse
I've installed this tool: http://forum.xda-developers.com/showthread.php?t=2317790
then manually booted the phone into fastboot mode
in the directory of Minimal ADB and Fastboot i've put the twrp-3.0.2-22-oneplus3.img and renamed the file into twrp
then i've flashed the file with this command: fastboot flash recovery twrp.img
once booted into recovery i've paste the cyanogenmod rom file into the phone and installed by the classic way (WIPE cache, sys, data, davilk//INSTALL cm file// OPTIONAL INSTALL gapps, kernel, su)
restart the phone, done!
TheReverend98 said:
I've installed this tool: http://forum.xda-developers.com/showthread.php?t=2317790
then manually booted the phone into fastboot mode
in the directory of Minimal ADB and Fastboot i've put the twrp-3.0.2-22-oneplus3.img and renamed the file into twrp
then i've flashed the file with this command: fastboot flash recovery twrp.img
once booted into recovery i've paste the cyanogenmod rom file into the phone and installed by the classic way (WIPE cache, sys, data, davilk//INSTALL cm file// OPTIONAL INSTALL gapps, kernel, su)
restart the phone, done!
Click to expand...
Click to collapse
.
thank you for sharing this! ?
[email protected] said:
Hi, if you hold down volume up and power button for at least 20 seconds and release, make sure you have downloaded universal adb drivers and op3 drivers also, when you have these run the tool, the tool I originally downloaded was corrupt, the unbrick tool must have the system.img, recovery img etc.... For it to work, you will know when it's connect as one line in the programme will change. I can send you the files needed if you send me your email address.
---------- Post added at 01:41 PM ---------- Previous post was at 01:37 PM ----------
Hi,
Are you running the command window from that folder where adb is? Push tab and right click mouse button or right on laptop to access run command option
Click to expand...
Click to collapse
Hi Gary can you send me the files to email [email protected] because I'm having the same issues. Thanks
" SOLVED - System was using 19.99 gb's required user data format. " Cant flash any of 3 factory images ? Anyone have a clue why ? I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space " I flashed images just fine a couple weeks ago on both my Nexus 6 and my Nexus 9 but for some reason I keep getting this problem.
I have tried using flash-all.bat and that is what I get. I never have had any luck using flash-all.bat in the past with my Nexus 6 & 9 so I would use the manual method which I"am listing below but there are a lot more things to flash on these pixel XL. So hopefully someone can list how to manually flash an image on the pixel XL because its totally different. Hopefully someone can tell me what is the problem ?
Run fastboot commands
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Add next step for Nexus 9
fastboot flash vendor vendor.img
I have also tried the following steps and on the last step flashing the image I still get " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Steps I tried are:
fastboot flash bootloader bootloader-marlin-8996-012001-1608281716.img
fastboot reboot-bootloader
fastboot flash radio radio-marlin-8996-012511-1609150631.img
fastboot reboot-bootloader
fastboot -w update image-marlin-nde63l.zip
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
M9guy said:
I just checked my setting and I have 19.99 gb's used by the system. That seems way too much. Could that be the problem ?
Click to expand...
Click to collapse
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
M9guy said:
I have a verizon pixel Xl with unlocked bootloader rooted with the newest supersu and every time I try to flash any of the three factory images for pixel XL my adb tools gives me the error " error: failed to load 'image-marlin-nde63l.zip': Not enough space "
Click to expand...
Click to collapse
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I was in bootloader fastboot mode and i saw same issue.
rootSr. said:
I was in bootloader fastboot mode and i saw same issue.
Click to expand...
Click to collapse
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
cam30era said:
You don't use ADB to flash factory image. You use fastboot, from your bootloader...
Click to expand...
Click to collapse
I put phone in bootloader mode and held down shift button and righted clicked on my folder with my adb tool that I extracted all files to.
http://androiding.how/flash-firmware-factory-image-google-pixel/
jaythenut said:
Yeah sounds like it to me might have to wipe userdata that will wipe your phone completely
Click to expand...
Click to collapse
The method at the link below I had tried it previously and it did format my data but now each time I boot the phone I get " There"s an internal problem with your device. Contact your manufacturer for details. "
http://androiding.how/flash-firmware-factory-image-google-pixel/
zaksimmermon said:
When I flash the images I use the flash-all.sh.
This works for me "sudo sh flash-all.sh"
Click to expand...
Click to collapse
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
rootSr. said:
I had same issue. I have sideloaded the update zip temporarily. I still wonder what's wrong in flashing zip file. I dont think its the issue with size because i had almost 90GB space left.
Click to expand...
Click to collapse
I have the update downloaded to the phone it just wont install it think because I was rooted, even after formatting user data starting over it still would not install the update with no supersu installed.
Do you remember where the update was downloaded to on your phone what folder, or did you download the update somewhere else to your computer ?
cam30era said:
Just to confirm, you unzipped the factory image and did: fastboot flash system system.img?
If so, you might need to update your Android SDK...
Click to expand...
Click to collapse
It makes sense, I will update and verify. Thanks for quick reply Cam
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
I just tried updating my Minimal ADB and Fastboot [10-22-16] and still same error. I thought I had already updated but I tried again anyway and still no go, and that was updated on 10-22-16
http://forum.xda-developers.com/showthread.php?t=2317790
M9guy said:
I have windows 10, which for windows your supposed to use flash-all.bat which that gave me the same error on the last step flashing the system image.
Click to expand...
Click to collapse
What version is your pixel running now? I'm on NDE63P.
zaksimmermon said:
What version is your pixel running now? I'm on NDE63P.
Click to expand...
Click to collapse
I"am on NDE63L
You need to try updating the SDK through the SDK manager. It'll have a box to check of to update SDK 25.
Sent from my Pixel XL using Tapatalk
rootSr. said:
It makes sense, I will update and verify. Thanks for quick reply Cam
Click to expand...
Click to collapse
It did work without any issues. I have cleared old SDK and downloaded new. Worked flawless. Thanks. :good:
II am attempting to get back to full stock on my Pixel XL and I am okay with wiping it. I am coming from Rooted, TWRP, custom Kernel, and WETA Rom. I was having some issues with it acting up, and I want now to return to the full factory image. In order to do so, I attempted to run the flash-all.bat script from the Google page, and it seems as if all is going well, then, when it tries to flash the system.img, it fails and throws an error which says "FAILED (Remote: Partition [bootb] does not exist)" I have also tried flashing the factory image in pieces and get the same issue, and also when I try to do it through TWRP. I just want to go back to the way the phone came so I can start fresh. Any input on how to do so would be greatly appreciated. Note: the same error goes when I try to flash-all on slot a.
What version of adb are you running?
Make sure you have 1.0.36. Ref post http://forum.xda-developers.com/showthread.php?t=2932160
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
harmohn said:
What version of adb are you running?
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
The latest minimal adb fastboot
gettingerr said:
The latest minimal adb fastboot
Click to expand...
Click to collapse
Okay, just to be sure can you type "adb version" and then "fastboot --version" (without quotes) in a command line console. What were the outputs?
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Zavon said:
Try manually flashing to partition _a or _b. Such as fastboot flash system_a system.img.
I ran into the same issue and was able to flash everything to slot a manually by adding _a to the commands
Click to expand...
Click to collapse
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
gettingerr said:
Android Debug Bridge version 1.0.35
Revision fc2a139a55f5-android
fastboot version fc2a139a55f5-android
Click to expand...
Click to collapse
Right, you need to be on 1.0.36 for fastboot to "see" the partitions correctly. Refer to my initial comment for a download link.
gettingerr said:
I think that worked! Do I need to flash anything besides boot, system, and vendor? There are a lot of .img files in this folder from google. Do I do them all or just these three? Also, do I need to flash the radio?
Odd that Google wouldn't update their flash-all script to deal with the two slot setup..
Click to expand...
Click to collapse
I didn't flash any of the other stuff. Only boot, system, and vendor.
Not sure what causes the mismatch in names of the partitions.
Download the free Unified Toolkit. It works across a large number of Android devices. It takes the hassle out of a lot of ****, including this. It will flash the entire factory package by itself. I had to do this to fix my phone from a recovery bootloop after flash-all.bat failed me too.