Hey sorry guys for being such a newbie here....need some help.
1. Ran the Nexus 6 1 click unroot kit
2. Somehow I screwed it up and now can't get past the teamwin blue screen just keeps popping back up.
3. I have a mac and have watched countless videos on reflashing factory image and nothing seems to be working.
Any ideas?
nickb2005 said:
Hey sorry guys for being such a newbie here....need some help.
1. Ran the Nexus 6 1 click unroot kit
2. Somehow I screwed it up and now can't get past the teamwin blue screen just keeps popping back up.
3. I have a mac and have watched countless videos on reflashing factory image and nothing seems to be working.
Any ideas?
Click to expand...
Click to collapse
Are you familiar with fastboot? If not, go here:
http://forum.xda-developers.com/showthread.php?t=3006500
I don't use Mac so I'm not sure exactly how the commands get typed but you should try:
fastboot format cache
fastboot format userdata
Evolution_Freak said:
Are you familiar with fastboot? If not, go here:
http://forum.xda-developers.com/showthread.php?t=3006500
I don't use Mac so I'm not sure exactly how the commands get typed but you should try:
fastboot format cache
fastboot format userdata
Click to expand...
Click to collapse
So, I tried doing it...on a mac you need to put ./then your fastboot
Here's what I get....
AdminisatorsAir:~ Nick$ ./fastboot format cache
-bash: ./fastboot: No such file or directory
nickb2005 said:
So, I tried doing it...on a mac you need to put ./then your fastboot
Here's what I get....
AdminisatorsAir:~ Nick$ ./fastboot format cache
-bash: ./fastboot: No such file or directory
Click to expand...
Click to collapse
Do you have the Android SDK installed or minimal fastboot tools?
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
Does your device serial number come up when you type fastboot devices?
Evolution_Freak said:
Do you have the Android SDK installed or minimal fastboot tools?
Click to expand...
Click to collapse
So, I had the SDK installed or thought I did...went to tools and then android clicked that and it keeps telling me java runtime environment isn't installed and to please install. I did it 3 times and still nothing when click android to try to get the sdk.
nickb2005 said:
So, I had the SDK installed or thought I did...went to tools and then android clicked that and it keeps telling me java runtime environment isn't installed and to please install. I did it 3 times and still nothing when click android to try to get the sdk.
Click to expand...
Click to collapse
Navigate to the platform-tools folder and open a command window there. Also, if that doesn't work, in the fastboot thread I linked, is a method to install fastboot and ADB system wide. Is that an option?
Well while evolution_freak helps you out, I'd like to chime in and say that I always stayed away from any 1-click anything, as well as any auto ROM/recovery updater.
You never know if you downloaded the wrong file
and then I just imagined hundreds of lines of code pouring into my poor little phone and how it would be screaming inside ):
I've seen lots of hard bricks happen from 1-click packages, learning how to do things the dirty way is more fun anyway!
Evolution_Freak said:
Navigate to the platform-tools folder and open a command window there. Also, if that doesn't work, in the fastboot thread I linked, is a method to install fastboot and ADB system wide. Is that an option?
Click to expand...
Click to collapse
This is my "tools" folder from the SDK I downloaded.
nickb2005 said:
This is my "tools" folder from the SDK I downloaded.
Click to expand...
Click to collapse
Now here's what happens when I click the android, I assume I want to install all 16 packages here? My question is where do I go from this step?
nickb2005 said:
Now here's what happens when I click the android, I assume I want to install all 16 packages here? My question is where do I go from this step?
Click to expand...
Click to collapse
Forgot the image...
nickb2005 said:
Forgot the image...
Click to expand...
Click to collapse
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Evolution_Freak said:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
Click to expand...
Click to collapse
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
nickb2005 said:
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
Click to expand...
Click to collapse
I tried another guide to get adb and fastboot working. However, now it's showing my device isn't attached although it 100% is.
nickb2005 said:
Thanks, maybe you can explain to me. In the image I attached it asks for password, but it won't let me type my computer password at all. Anyway to actually type it so it doesn't keep telling me incorrect password?
Click to expand...
Click to collapse
I've never encountered this, again I don't have Mac. I'm guessing you couldn't get the simple ADB and fastboot tool to install, from the other thread?
I haven't had my morning coffee yet, so bare with me.
Evolution_Freak said:
I've never encountered this, again I don't have Mac. I'm guessing you couldn't get the simple ADB and fastboot tool to install, from the other thread?
I haven't had my morning coffee yet, so bare with me.
Click to expand...
Click to collapse
I know, it's early :/ im going on like 5 hours trying to fix this thing. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1917237
I got adb and fastboot in the folder, but whenever I type ./adb devices it shows nothing is connected yet I am connected via USB and the phone shows me that.
nickb2005 said:
I know, it's early :/ im going on like 5 hours trying to fix this thing. I followed this guide: http://forum.xda-developers.com/showthread.php?t=1917237
I got adb and fastboot in the folder, but whenever I type ./adb devices it shows nothing is connected yet I am connected via USB and the phone shows me that.
Click to expand...
Click to collapse
Did you install the drivers?
Evolution_Freak said:
Did you install the drivers?
Click to expand...
Click to collapse
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
nickb2005 said:
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
Click to expand...
Click to collapse
Again, I'm sorry for my lack of knowledge with Mac.
Evolution_Freak said:
Again, I'm sorry for my lack of knowledge with Mac.
Click to expand...
Click to collapse
Oh no problem at all..I know your trying to help me. I shouldn't of been trying to do this and now I don't have a phone at all.
nickb2005 said:
On a mac you don't need to install the drivers it said that was windows only when I tried clicking it in the SDK manager. Weirdly enough last night when I first tried this it actually showed something connected. So I am not sure what happened between then and now.
Click to expand...
Click to collapse
Try this, power off your nexus and manually boot it to bootloader. Hold power down and press volume up. Once it boots to bootloader, connect to your computer.
---------- Post added at 08:05 AM ---------- Previous post was at 08:04 AM ----------
See if it is detected then and try the command: fastboot devices
Related
Phone doesn't get recognized when plugged into my Mac. Can't get into my phone because it's stuck in "flash mode" and "recovery mode" I think.. These are the only 2 screens I can get to. Cannot get into my phone at all. http://img.wonderhowto.com/img/27/60/63506305015628/0/unlock-your-bootloader-root-your-htc-one-install-custom-recovery-using-twrp.w654.jpg and http://img.wonderhowto.com/img/88/14/63506304904836/0/unlock-your-bootloader-root-your-htc-one-install-custom-recovery-using-twrp.w654.jpg
TynanV said:
Okay, followed this tutorial today (can't post the link but it's called "How to Root HTC One! [Mac, Linux, Windows Tutorial]" and no matter what I do I can't seem to get back to the actual phone (i.e., being able to access the main screen where everything is, if you know what I mean). I've tried going to the recovery screen and hitting reboot but it just takes me back to this TWRP page that has a bunch of options like "Install, Wipe, Backup, Restore, Mount, Setting, etc. I really hope I haven't screwed up my phone permanently. Please help me :crying:
Click to expand...
Click to collapse
how far into the tutorial did you get ?
did you fastboot erase cache after flashing twrp ?
clsA said:
how far into the tutorial did you get ?
did you fastboot erase cache after flashing twrp ?
Click to expand...
Click to collapse
I'm completely new at this and literally just started today, What does flashing twrp mean? I got to the end of the tutorial i believe. Everything worked great until step 28 I think.
TynanV said:
I'm completely new at this and literally just started today, What does flashing twrp mean? I got to the end of the tutorial i believe. Everything worked great until step 28 I think.
Click to expand...
Click to collapse
when you were in the command prompt and run the fastboot commands
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot-bootloader
did you do these, or use an all in one app
clsA said:
how far into the tutorial did you get ?
did you fastboot erase cache after flashing twrp ?
Click to expand...
Click to collapse
clsA said:
when you were in the command prompt and run the fastboot commands
fastboot flash recovery TWRP.img
fastboot erase cache
fastboot reboot-bootloader
did you do these, or use an all in one app
Click to expand...
Click to collapse
I have one in the terminal (I think that's the command prompt on a PC?) called this -
./fastboot-mac flash recovery openrecovery-twrp-2.6.3.0 m7.img
not sure about the other two.
TynanV said:
I have one in the terminal (I think that's the command prompt on a PC?) called this -
./fastboot-mac flash recovery openrecovery-twrp-2.6.3.0 m7.img
not sure about the other two.
Click to expand...
Click to collapse
are you on Sprint ? their is newer recovery for GSM phones
http://techerrata.com/browse/twrp2/m7 - 2.6.3.3 is recommended
make sure you do all 3 commands
clsA said:
are you on Sprint ? their is newer recovery for GSM phones
http://techerrata.com/browse/twrp2/m7 - 2.6.3.3 is recommended
make sure you do all 3 commands
Click to expand...
Click to collapse
I'm with Telus in Canada.
TynanV said:
I'm with Telus in Canada.
Click to expand...
Click to collapse
use TWRP 2.6.3.3 and don't skip any steps
clsA said:
use TWRP 2.6.3.3 and don't skip any steps
Click to expand...
Click to collapse
Thanks, I looked up how to do this though and the 2nd step says, "run fastboot flash recovery twrp-2.6.3.3-m7.img" how do I do this?
TynanV said:
Thanks, I looked up how to do this though and the 2nd step says, "run fastboot flash recovery twrp-2.6.3.3-m7.img" how do I do this?
Click to expand...
Click to collapse
in terminal the same as you did above with version 2.6.3.0
clsA said:
in terminal the same as you did above with version 2.6.3.0
Click to expand...
Click to collapse
Do I need my phone plugged into my Mac? (sorry for all the stupid questions i've just never really done this before).
TynanV said:
Do I need my phone plugged into my Mac? (sorry for all the stupid questions i've just never really done this before).
Click to expand...
Click to collapse
well if you have this many questions .. I think you should stop and read the guides before you do something to the phone that can't be reversed.
start here (go to post 2 Guides) >> http://forum.xda-developers.com/showthread.php?t=2438026
this is the MAC thread >> http://forum.xda-developers.com/showthread.php?t=2245782
Read this >> http://forum.xda-developers.com/showthread.php?t=2273376
once you have a handle on all the steps required to unlock - install recovery - get Root - and Flash Roms then you can start
clsA said:
well if you have this many questions .. I think you should stop and read the guides before you do something to the phone that can't be reversed.
start here (go to post 2 Guides) >> http://forum.xda-developers.com/showthread.php?t=2438026
this is the MAC thread >> http://forum.xda-developers.com/showthread.php?t=2245782
Read this >> http://forum.xda-developers.com/showthread.php?t=2273376
once you have a handle on all the steps required to unlock - install recovery - get Root - and Flash Roms then you can start
Click to expand...
Click to collapse
The problem is I can't transfer any files into the HTC Sync Manager to be able to apply them to my phone because I can't get to the main screen, therefore it does not recognize my phone when it's plugged into my computer..
TynanV said:
The problem is I can't transfer any files into the HTC Sync Manager to be able to apply them to my phone because I can't get to the main screen, therefore it does not recognize my phone when it's plugged into my computer..
Click to expand...
Click to collapse
like i said go do some reading
and uninstall HTC SYNC it's useless
the only tools you'll be using are Terminal / fastboot and ADB
clsA said:
like i said go do some reading
and uninstall HTC SYNC it's useless
the only tools you'll be using are Terminal / fastboot and ADB
Click to expand...
Click to collapse
Okay thanks dude. Gonna head to bed and read up on all that stuff tomorrow morning. If I run into any furthur problems could I PM you for help?
TynanV said:
Okay thanks dude. Gonna head to bed and read up on all that stuff tomorrow morning. If I run into any furthur problems could I PM you for help?
Click to expand...
Click to collapse
just quote me here I'll be with you ...your phone is not dead
you just need more info to get through everything to get back up and running
Okay... After reading a bunch of stuff, I still have no idea what I'm looking for/what I need to actually do. I'm trying to get my HTC One back to stock, and all the guides I'm seeing require the phone to actually be working (mine isn't, it's stock on the TWRP/recovery thing therefore I can't access any of my apps and whatnot). This is getting really frustrating.
Okay, I found a pic online of the part I'm stuck at. Here it is - http://www.tech-recipes.com/wp-content/uploads/2013/05/twrp-recovery-294x500.jpg I can only get to that screen and this one too - http://img.wonderhowto.com/img/88/1...e-install-custom-recovery-using-twrp.w654.jpg I cannot get back to my actual phone's screen, like this one I mean - http://img.wonderhowto.com/img/56/8...sense-style-home-screen-your-htc-one.w654.jpg
TynanV said:
Okay, I found a pic online of the part I'm stuck at. Here it is - http://www.tech-recipes.com/wp-content/uploads/2013/05/twrp-recovery-294x500.jpg I can only get to that screen and this one too - http://img.wonderhowto.com/img/88/1...e-install-custom-recovery-using-twrp.w654.jpg I cannot get back to my actual phone's screen, like this one I mean - http://img.wonderhowto.com/img/56/8...sense-style-home-screen-your-htc-one.w654.jpg
Click to expand...
Click to collapse
lol ok well that's very visual
did you find and read the parts about using fastboot and adb ? on your MAC ?
you should be close
boot to the bootloader (your 2nd screen shot) fastboot usb with phone plugged into you mac
open terminal and type
fastboot erase cache
then
fastboot reboot
does you phone start up now ?
TynanV said:
Okay, followed this tutorial today (can't post the link but it's called "How to Root HTC One! [Mac, Linux, Windows Tutorial]" and no matter what I do I can't seem to get back to the actual phone (i.e., being able to access the main screen where everything is, if you know what I mean). I've tried going to the recovery screen and hitting reboot but it just takes me back to this TWRP page that has a bunch of options like "Install, Wipe, Backup, Restore, Mount, Setting, etc. I really hope I haven't screwed up my phone permanently. Please help me :crying:
Click to expand...
Click to collapse
Try watching tutorial videos on youtube it will help you.
It helped me..
And read things again and agian till you dont get them right. Try to google some things when you are stuck in them.
Sent from my HTC Desire X using XDA Premium 4 mobile app
I just bought a Nexus 6... Unlocked the bootloader and rooted the phone.... after realizing there were some issues with the phone I decided I would try and download the PURE rom for the phone... I installed TWRP recovery and tried to flash the image. When the phone booted back up it said that the data was corrupt, and to enter a password. Entering anything seemed to work and I would then reset the phone... but the same thing would come back up.
So I decided to try and wipe the phone again and re-install the ROM... after that it wouldn't load at all, came back with some kind of error.
Then I decided to do a full wipe of the phone and try and re-install the factory image... Problem is... I haven't tried to do anything with a phone in like 2 years and well... i'm having trouble on trying to figure out how I can restore the factory image. I have the SDK tools installed, the phone drivers are also obviously installed, but can someone help me try to reset to the factory image.
I only have like 3 hours to try and accomplish this from now because after this I have to get on a plane and won't be around and will also leave me without a phone... Can someone please help me as soon as possible? Thank you so much!! I could use somewhat detailed instructions but not crazy
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Try nexus toolkit by wugfresh can't go wrong. If you get error missing system.img while flashing go to options then flash then click force flash. The toolkit will download all needed steps and flash without a problem
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Nexus device can almost never be bricked, I say almost never because of the people variable, but if you can get it into bootloader mode it is easy to bring back. just follow the instructions above.
I agree that even though wugfresh tools is the best out there. I have used it before. You learn nothing about what needs to be completed.
I could never get the drivers to work for me in most cases. I use ubuntu and it always works running the manual commands.
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
jwleonhart said:
Ok so I have tried to run the flash-all.bat file and it says in the command prompt it is an unrecognized command...
I'm assuming I must be missing part of the ADB tools? Ugh help!
Click to expand...
Click to collapse
first thing to do in adb is run the command "adb devices" to make sure that adb sees your device, does adb see your device?
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
jwleonhart said:
It says list of devices attached and then nothing....
Can someone give me a short step by step on what I need to do here? I'm really running low on time, this is really bad....
Click to expand...
Click to collapse
wait.. you are flashing the factory img, you do not use adb for that. you boot into the bootloader then use fastboot for that. adb doesnt work in the bootloader anyways, use fastboot while youre in the bootloader, and type fastboot devices to make sure fastboot sees your device.
@simms22 is correct, tool kits make you learn nothing, and you get posts like this.
However if you are time contained. As much as it pains me to say this. Use the tool kit. And learn on a time when you can.
Download Wugs toolskit and flash back to stock images. And you'll be fine.
Update your SDK if u haven't already.
Unzip factory images and place in platform tools folder of SDK. (Unless you have environmental variables set correctly)
Open a command prompt from that directory (place cursor in empty space, hold shift and right click on mouse)
Boot into bootloader
fastboot flash boot boot.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot reboot
Sent from my Nexus 6
simms22 said:
dont use a toolkit. you are guaranteed to learn nothing, and doing it the right way is just as fast(and easy). plus, root toolkits mess up often. dong it right never messes anything up.
Click to expand...
Click to collapse
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
dparrothead1 said:
Different strokes for different folks!!!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
jwleonhart said:
doing the following command in command prompt:
fastboot devices
it shows the following device:
ZX1G2224G5
I'm assuming that is the nexus 6...
So whats next on the list then?
I unzipped the factory image and using the flash-all.bat script it says fastboot is not a recognied command.
Click to expand...
Click to collapse
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
simms22 said:
not really.
if you know anything about what you are doing, its one thing, use a toolkit, enjoy yourself. if you have no idea what you are doing, the root toolkit is by far the wrong way to go. as you will still know absolutely nothing, and will learn nothing. and pretty soon, when you have some simple maintenance to do, and you have no idea how, you start thread about having your device bricked. and im sure that you personally have not helped out hundreds that have started threads about having their device "bricked" after using a root toolkit. i have.
---------- Post added at 02:06 PM ---------- Previous post was at 02:05 PM ----------
you probably have to unzip it twice, if there is another zip within that one zip. and you can try not using the word fastboot, as i also have ran into fastboot programs where it wasnt needed.
Click to expand...
Click to collapse
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
dparrothead1 said:
Friend, I'm way too old to get into an internet pissing contest!!! I realize I don't have 27,000+ post, but if you look at my thanks total, you will see that I've helped my share of members!!!! So don't tell me that I dont try to share my knowledge......have a good day and please don't respond to any more of my post!!!! Peace out!!
Sent from my SM-T310 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
with a silly post like "Different strokes for different folks!!!!" you definitely arent posting like someone your age, as thats what a child would say. im not young myself. anywho, you can not tell me not to respond, lol. ill respond to anyone who posts as silly as you. i have nothing against you, nor are trying to get at you, im simply responding to your silliness.
OP... The password was a numerical representation of your pattern unlock since you were still encrypted. The key is in the first post of the TWRP thread.
Now...extract the factory image until you have boot.img radio.img system.img and recovery.img if there is a bootloader img flash that first.
Flash bootloader with fastboot flash bootloader bootloader.img
Reboot with fastboot reboot-bootloader
Flash boot system and radio respectively with fastboot flash boot/radio/system boot.img/radio.img/system.img one at a time.
Finish with fastboot reboot and you sgould be all set.
op got it flashed, and ended up flashing his rom as well. so, he was successful
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
jiv101 said:
I hope saying use a toolkit didn't start an argument, only said to use it because he had a time restraint..
Click to expand...
Click to collapse
no, it didnt start an argument. but he ended up doing it the right way, then flashed his rom. then flashed a different rom because his rom was so so. but really, even if theres a time restraint, if your driver is installed properly, it takes about 3-4 minutes to flash the boot.img
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
See if you can flash a rom from your sd. hopefully you have something on there. Also see if you can see anything on fastboot since adb is not seeing anything
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
htcoveblue said:
I cannot get into Recovery to flash an old ROM. I get the android on his back with the red triangle. Fastboot does seem to work even though adb does not.
Click to expand...
Click to collapse
Update your android SDK. Then try again.
htcoveblue said:
I was trying to update to the Android M Preview following instructions on Phandroid. I successfully performed an "adb reboot bootloader". I got part way thru and the Flash-all.bat wouldn't work. So I started to manually flashboot the individual .img files. That was working until I tried to "fastboot flash system system.img". Then I got:
load_file: could not allocat 1979559444 bytes
error: cannot load 'system.img': Not enough space
I read around online and tried restarting my computer. After I did, I tried "adb devices" and nothing was listed. I tried to restart phone, but it won't boot because I didn't finish the process. I've tried upgrading to the latest Nexus 6 Google USB drivers. I've tried "adb kill-server", "adb start-server" but my device never shows up under "adb devices".
Any help getting it to show up? Any idea how to finish the system.img install if I can get it to show up? I'm feeling very sad without my phone working. :crying:
Click to expand...
Click to collapse
I read the story, then at the end is your problem. well, part of it. you weren't using adb in the bootloader, it doesnt work there, ever. you were using fastboot, and you should've fastboot devices
That's encouraging. Any idea how to get past the system.img file is too large error?
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
Is your SDK updated?
My drivers are updated using the Google USB Drivers from this link: http://developer.android.com/sdk/win-usb.html
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
htcoveblue said:
That's encouraging. Any idea how to get past the system.img file is too large error?
Click to expand...
Click to collapse
There is a different fast boot that you have to use called mfastboot.
http://highonandroid.com/android-sm...re-error-could-not-allocate-1778070480-bytes/
The fastboot not being recognized can sometimes be a driver error. Is it recognized look through device manager and try uninstall then unplug USB and plug back in.
Also the android naked drivers might help. Give them a try. http://forum.xda-developers.com/galaxy-nexus/development/adb-fb-apx-driver-universal-naked-t1379875
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Sent from my Nexus 6 using Tapatalk
htcoveblue said:
I was able to flash TWRP over to it but it appears my SDCARD has been wiped. I have a TWRP Backup saved on my computer but I can't figure out how to get it on the phone without using "adb push".
Click to expand...
Click to collapse
Can you not use MTP from TWRP?
Jnewell05 said:
Have you tried adb sideload from twrp? You can install roms from the computer rather then filling up your internal memory. Here is a guide/how to. http://forum.xda-developers.com/showthread.php?t=2559200
Click to expand...
Click to collapse
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
htcoveblue said:
This! I was able to sideload my current ROM and GAPPS. That allowed me to fully boot and copy over my TWRP backup. Thank you!
I'd still love to install the M preview build, but now I'm a little scared. Maybe I'll wait until there's a flashable ROM....
Click to expand...
Click to collapse
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Evolution_Tech said:
Ummmm like this?
http://forum.xda-developers.com/showthread.php?t=3121053
Click to expand...
Click to collapse
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
htcoveblue said:
I didn't know there was a flashable ROM out there yet. I thought they were all sideloads. Thanks!
Click to expand...
Click to collapse
No problem. I've run this and as long as you follow the installation instructions precisely, it is very stable and capable of being a daily driver.
---------- Post added at 07:16 AM ---------- Previous post was at 07:14 AM ----------
There's another flashable here:
http://forum.xda-developers.com/showthread.php?t=3066052
I haven't run this one but it seems to be getting good reviews.
Morning everyone. I'm having some troubling problems with my bootloader. I've had it soft bricked before and was fairly easy to fix. But something is drastically different now. It seems every time I try to restore one of my saved backups, it freezes after a certain point, and sends me back in the boot loader loop. Every time I try to wipe system/data/cache it freezes and back to the bootloader loop. I tried opening a command prompt in adb, but it just says device isn't connected. I can still get into twrp and into the bootloader selection modes. It's just when I do certain things it freezes. For my backup I was able to get it to 36% completed before it froze. My phone is a Moto X 2nd Gen xt1097, and I am running a nightly CyanogenMod on it. Updated it last time about 2 days ago. I just cant find anything on how to fix this. Any help will be much appreciated!! Thanks!
Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?
USA1791 said:
Okay so I've been able to accomplish one thing. I used the android SDK tools, and was able to fully wipe the phone using command prompt adb. So now the phone has nothing on it anymore, not even my saved backups. I have it in twrp recovery at the moment, and its plugged into my computer and I can see it recognizes it, but it dosent show any internal hardrive for me to put a custom rom on it. Any idea on this?
Click to expand...
Click to collapse
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?
Gus Ghanem said:
I think you should flash the latest stock firmware, in case you have corrupt partitions, then start over again.
Your phone is accepting commands, so you must have installed the USB drivers. Which XT1097 do you have?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
Do you know how to flash stock firmware?
Click to expand...
Click to collapse
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.
USA1791 said:
Thanks for your reply! Its an AT&T XT1097, if thats what you mean. I'm not entirely sure, or if I even can. Internal storage wont show up, and every time I try to reboot the phone it goes from bootloader to OpenRecoveryScript, back and forth between those two. I can stop it by holding the power and volume and going into twrp recovery. On the adb I opened command prompt and typed in adb devices, and mine comes up so it does recognize it. If internal storage would show up I think I could do this, but since its not I'm completely lost.
Click to expand...
Click to collapse
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have
Gus Ghanem said:
You should download this firmware:
XT1097_VICTARA_ATT_5.1_LPES23.32-21.9-3_cid1_CFC.xml.zip
Did you install these USB drivers?
https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Type:
fastboot getvar all
to check exactly what hardware you have
Click to expand...
Click to collapse
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.
USA1791 said:
How would I install that firmware? I cant find a way to get anything on it. I typed that in and it's just saying waiting for device. Do I need to do something else to get that to work?
Oh, and yes I did install those drivers.
Click to expand...
Click to collapse
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.
Gus Ghanem said:
I should have specified typing commands in Bootloader Mode, are you able to get into Bootloader Mode?
Firmware can be flashed with fastboot in bootloader mode, the commnads are in the flashfile.xml file.
Click to expand...
Click to collapse
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?
USA1791 said:
Yes I can get into bootloader mode. Flashfile.xml file? And for the firmware you listed above, I found a site with it but it was all in chinese, is that the correct one?
Click to expand...
Click to collapse
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?
Gus Ghanem said:
No, get it from here:
https://mega.nz/#F!ow8igZRL!Z7vmN8GOpez2bVMYDvEKkg!IkEVHRxS
or here:
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1097/
But you have to be sure fastboot is sending commands to the phone. Have you ever used RSDLite?
Did you have stock Lollipop 5.1 before you put CM on it?
Click to expand...
Click to collapse
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.
USA1791 said:
Okay downloading it now. And I've never used it, but I read somewhere about it earlier today and I have it installed on my computer. And yes, I did have the Lollipop 5.1 before I put the CM on it.
Click to expand...
Click to collapse
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working
Gus Ghanem said:
You should boot into bootloader mode, then connect the usb cable, and check if the phone says "connected"
Then type
fastboot getvar all
To make sure fastboot is actually working
Click to expand...
Click to collapse
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.
USA1791 said:
Okay I did that and a bunch of stuff came up. I've attached two snapshots of what came up.
Click to expand...
Click to collapse
Yes it looks like fastboot is working, you should delete those screenshots now.
Gus Ghanem said:
Yes it looks like fastboot is working, you should delete those screenshots now.
Click to expand...
Click to collapse
Oh. Okay got them deleted. Didnt think they'd show anything personal?
After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 0 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
USA1791 said:
Oh. Okay got them deleted. Didnt think they'd show anything personal?
Click to expand...
Click to collapse
Sort of, unique to your own phone, like IEMI, Serial Number, etc.
Gus Ghanem said:
After the firmware is done downloading, extract it and check how many system.img_sparsechunk files you have, like 0 - 9? 0 - 8? 9 - 7?
Put the 4 ADB/Fastboot files in the folder with the firmware files:
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
Sort of, unique to your own phone, like IEMI, Serial Number, etc.
Click to expand...
Click to collapse
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!
USA1791 said:
How do I check how many of the system.img sparsechunk files? And these ADB/Fastboot files? So I'd just move those 4 to the same folder where I extract the android firmware? (Sorry, a little confusing to me still). Ah gotcha, thanks for letting me know!
Click to expand...
Click to collapse
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2
New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?
Gus Ghanem said:
Those files look dated (2014?)
Unzip the firmware file and look at the files.
Here are the latest ADB/Fastboot 24 rc2
Click to expand...
Click to collapse
Oh thanks, I guess they are dated lol.
USA1791 said:
New thing just happened. I went into recovery from the bootloader, and now it shows my internal storage. Would putting CM on it from there work? Or would I need to also put super su as well? Or neither and just wait for the android firmware to download?
Click to expand...
Click to collapse
No don't flash supersu, it causes problems
Yes try copying the CM and Gapps zips to you phone, and try flashing them with TWRP...
which version TWRP you have on the phone?
1st problem. My windows 10 PC can only see my phone when its set to PTP mode and file transfer/android auto will not work to move the patched boot images back and forth.
2nd problem. To try and get around the 1st problem I downloaded the patched boot image from a thread. Now when I try and flash the modified boot image I get and "partition not found" error.
This is getting me pissed. even if I fixed the storage issue and flashed the boot image i'd still have the partition issues
bigmatt503 said:
1st problem. My windows 10 PC can only see my phone when its set to PTP mode and file transfer/android auto will not work to move the patched boot images back and forth.
2nd problem. To try and get around the 1st problem I downloaded the patched boot image from a thread. Now when I try and flash the modified boot image I get and "partition not found" error.
This is getting me pissed. even if I fixed the storage issue and flashed the boot image i'd still have the partition issues
Click to expand...
Click to collapse
What is weird is there are alot of people having issues similar to yours but I haven't at all and I'm rooted with magisk and running clean slate kernel, I will say this I had to use a patched A11 boot image of someone else's because when I was patching the boot image on my windows 10 laptop it kept spitting out patched boot images that where to small and corrupted so if you want to try the boot image I used I'll link it with gdrive for you here https://drive.google.com/file/d/1ZSIERVIHxqZNP_WCd7LX71mYOgNMTpE4/view?usp=drivesdk
Good luck hope it works and let me know if it does!
jmac052002 said:
What is weird is there are alot of people having issues similar to yours but I haven't at all and I'm rooted with magisk and running clean slate kernel, I will say this I had to use a patched A11 boot image of someone else's because when I was patching the boot image on my windows 10 laptop it kept spitting out patched boot images that where to small and corrupted so if you want to try the boot image I used I'll link it with gdrive for you here https://drive.google.com/file/d/1ZSIERVIHxqZNP_WCd7LX71mYOgNMTpE4/view?usp=drivesdk
Good luck hope it works and let me know if it does!
Click to expand...
Click to collapse
Going to try in a few minutes. I hate not having root
jmac052002 said:
What is weird is there are alot of people having issues similar to yours but I haven't at all and I'm rooted with magisk and running clean slate kernel, I will say this I had to use a patched A11 boot image of someone else's because when I was patching the boot image on my windows 10 laptop it kept spitting out patched boot images that where to small and corrupted so if you want to try the boot image I used I'll link it with gdrive for you here https://drive.google.com/file/d/1ZSIERVIHxqZNP_WCd7LX71mYOgNMTpE4/view?usp=drivesdk
Good luck hope it works and let me know if it does!
Click to expand...
Click to collapse
I appreciate you sharing your link.... Still no go. Still getting that no partition error. I'm at a loss about it. I always can figure this out, but I feel defeated tonight and I'll pick back up tomorrow
bigmatt503 said:
I appreciate you sharing your link.... Still no go. Still getting that no partition error. I'm at a loss about it. I always can figure this out, but I feel defeated tonight and I'll pick back up tomorrow
Click to expand...
Click to collapse
Are you using minimal adb or are you going to your platform tools folder and typing cmd in the address bar and using the actual command prompt because I had that issue too and had to type CMD in the file manager spacebar while inside platform tools and use the actual command prompt not minimal ADB or the PowerShell either they can be finicky
jmac052002 said:
Are you using minimal adb or are you going to your platform tools folder and typing cmd in the address bar and using the actual command prompt because I had that issue too and had to type CMD in the file manager spacebar while inside platform tools and use the actual command prompt not minimal ADB or the PowerShell either they can be finicky
Click to expand...
Click to collapse
This is exactly what I've been doing. I'll try cmd tomorrow. Thanks for the info
jmac052002 said:
Are you using minimal adb or are you going to your platform tools folder and typing cmd in the address bar and using the actual command prompt because I had that issue too and had to type CMD in the file manager spacebar while inside platform tools and use the actual command prompt not minimal ADB or the PowerShell either they can be finicky
Click to expand...
Click to collapse
When you say "file manager" are you talking about the bottom left search bar? I've never heard the term f"file manager " when it comes to adb /platform tools
bigmatt503 said:
This is exactly what I've been doing. I'll try cmd tomorrow. Thanks for the info
Click to expand...
Click to collapse
Let me know how it goes.
jmac052002 said:
Let me know how it goes.
Click to expand...
Click to collapse
Still getting the partition not found error. Thanks for the idea...
bigmatt503 said:
Still getting the partition not found error. Thanks for the idea...
Click to expand...
Click to collapse
Damn sorry brother I tried that bugs the **** out of me let me see if I can figure this **** out...hey there is a thread around here that is specifically people talking about the very issue of rooting Android 11 stable and having issues.
jmac052002 said:
Damn sorry brother I tried that bugs the **** out of me let me see if I can figure this **** out...hey there is a thread around here that is specifically people talking about the very issue of rooting Android 11 stable and having issues.
Click to expand...
Click to collapse
It's so annoying. I'm still confused on why my pc cannot see my pixel as portable storage. I really want to figure out how to get root running again
bigmatt503 said:
It's so annoying. I'm still confused on why my pc cannot see my pixel as portable storage. I really want to figure out how to get root running again
Click to expand...
Click to collapse
Maybe try these 2 things:
1. Plug in phone to computer and reboot computer while the phone is still plugged in.
2. Turn on bluetooth on your computer and see if it recognizes your phone after that.
Of course trying different cables, ports, etc. as well.
Lughnasadh said:
Maybe try these 2 things:
1. Plug in phone to computer and reboot computer while the phone is still plugged in.
2. Turn on bluetooth on your computer and see if it recognizes your phone after that.
Of course trying different cables, ports, etc. as well.
Click to expand...
Click to collapse
The patched img was trying to go to slot b. I needed slot a. Problem solved.
Thanks for the ideas
jmac052002 said:
Damn sorry brother I tried that bugs the **** out of me let me see if I can figure this **** out...hey there is a thread around here that is specifically people talking about the very issue of rooting Android 11 stable and having issues.
Click to expand...
Click to collapse
The patched img was going to the wrong slot... I have root now. Thanks for everything
bigmatt503 said:
The patched img was going to the wrong slot... I have root now. Thanks for everything
Click to expand...
Click to collapse
Great news... I believe I had that same problem back in the past
removed my suggestions . just saw that you fixed the issue.