Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
JeffDenver said:
Some background...Rooted and unlocked. I removed encryption right after I bought it.
I attempted to flash 5.1 the update. I flashed the bootloader and radio first, and rebooted the bootloader. Everything went fine until I tried to flash the system image. I got a lot of "sparse" errors.
When it rebooted it re-encrypted the device. But now nothing works. Phone, NFC ect shows errors. I can get into the bootoader, and I can flash stuff, but the recovery menu is gone,. It's just an error icon with "no connection" now.
Any ideas on how I can salvage this? I already backed everything up before I started. Is there a way I can just wipe everything and go back to stock? Even if it is 5.01?
EDIT - My bootloader is still showing as unlocked. I did not re-lock it.
Click to expand...
Click to collapse
Install factory images using fastboot
https://developers.google.com/android/nexus/images
You might have "soft bricked" it, but if you still have bootloader access you are fine
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
JeffDenver said:
I actually tried that, but it will not recognize it from ADB...I can flash stuff via fastboot, but ADB does not see it.
I did fully update the android SDK before I started. Should'nt that have updated all the drivers needed for ADB?
Click to expand...
Click to collapse
you update via fastboot, while youre in the bootloader. adb has nothing to do with it.
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
JeffDenver said:
When I go to the platform tools folder, and use "adb devices", it tells me nothing after "list of devices attached". As if it does not see the phone.
Click to expand...
Click to collapse
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
SDK is updated. I assumed it updated drivers as well. If not, where do I get those?
I do understand that fastboot only works while in the bootloader. I have not attempted to use it while in Android.
JeffDenver said:
When I attempt to "fastboot -w update image-shamu-lmy47d.zip", a window comes up and scrolls 3 or 4 lines too fast to see, and then exits. Nothing happens.
Click to expand...
Click to collapse
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Evolution_Freak said:
Have you updated the SDK? Drivers installed? Also, read up on how to use fastboot. Fastboot only works from bootloader, not when booted into Android.
Click to expand...
Click to collapse
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Where do I get that from?
JeffDenver said:
Where do I get that from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=56913254
Sent from my Nexus 6 using XDA Free mobile app
---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------
Evolution_Freak said:
Better to learn some basics first then you shall fear no soft brick ever!
http://forum.xda-developers.com/showthread.php?t=2277112
Click to expand...
Click to collapse
Better fear the bootloader downgrade soft brick
Sent from my Nexus 6 using XDA Free mobile app
Konfuzion said:
I'm all for adb, but save yourself a headache and get wugs toolkit and use force flash.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure you know what adb is?
:/
rootSU said:
Are you sure you know what adb is?
:/
Click to expand...
Click to collapse
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
mwalt2 said:
Just extract the .zip and flash the things inside separately using fastboot. You can skip user data I believe (or not if you don't care about erasing your device). Using the -w switch would have erased it anyway. The commands are easy, just "fastboot flash system system.img" and the like. Change "system" and "system.img" for the file you're flashing.
Click to expand...
Click to collapse
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Konfuzion said:
What's it to you? Yeah I'm fine with adb thanks. If you want to discuss something other than helping the OP go ahead and pm me.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
to repeat again, you use fastboot to flash the factory img, while youre in the bootloader. it should take you just several minutes to do, or a little bit longer if you are being very carefull. adb has nothing to do with it.
JeffDenver said:
Ok, I did this. It appeared to work correctly, but...
My phone looks like it did before. In "about" I see it shows 5.1 as the version. I have lost root. Shouldn't I be reset to factory appearance since I overwrote the entire system? Everything looks intact, including nova launcher.
Phone appears to be working normally. I am on the phone on hold as I type this. I am just worried about problems down the road. Do I need to flash anything else? Can I assume the bootloader and radio installed correctly?
Click to expand...
Click to collapse
its probably a good idea to factory reset since you're going up a major version and have already had problems.
rootSU said:
Its just you mentioned a toolkit as an alternative to adb but adb has nothing to do with any of this so if you're going to be helping the OP, I thought I'd better check that you know what you're talking about. ...which I don't think you do... So back to the point, how I'm helping the OP is by telling him to ignore everything you say. THAT'S "what's it" to me. Cheeky chops
@JeffDenver, ignore this guy. Use fastboot. Read general > all in one guide > question 28 for any info you may need, including drivers.
Click to expand...
Click to collapse
The reason I suggested wugs, is the first thing it has you do after installation is walks you through removing old drivers and installing the correct drivers and making sure that the phone is recognized. Then it will download the needed files and check the md5's which would help to avoid further problems.
Sent from my Nexus 6 using XDA Free mobile app
Related
It started here:
http://forum.xda-developers.com/showthread.php?t=2530605
I followed this post.
http://forum.xda-developers.com/showthread.php?t=2509676
Got nowhere because of the puttytel window timeout problem.
Related to this post was this post:
http://forum.xda-developers.com/showthread.php?p=47749358#post47749358
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
bullpen7979 said:
I have an unlocked bootloader on Moto X from sprint. I just need the easiest way to root.
This looked confusing. http://forum.xda-developers.com/showthread.php?t=2536200. Gotta be another way.
Have considered restoring to stock and taking the dang thing back http://atsgadgets.com/how-to-restor...lite-att-t-mobile-sprint-verizon-us-cellular/. So frustrated.
I've offered paypal to those who can do it successfully. I am so burnt out on trying to make this work. This PITA is not worth android. I have a one click jailbroken phone now. And I have successfully rooted and installed custom roms before but this is totally out of hand how complex this is for me. Maybe I'm just remedial but it seems several are having trouble with this model. For open source, this should not be this tough.
/rant. Almost ready to throw in the towel, but still listening.....
Sorry for the multiple posts. Just trying to get some new opinions. HTC Evo 4 g was done in 10 minutes. This has taken 4 days.
:crying:
Click to expand...
Click to collapse
Are you on 4.4 and what computer OS are you using?
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
Here, go into Settings -> About Phone and tell me what your Build Number is (at the very bottom).
Do not put in the cmd window mfastboot, just try fastboot flash recovery twrp 2.6.3.1-ghost-4.4.img. Now also put the recovery image in the same folder as fast boot, I believe its SDK tools folder
Sent on my Moto X
bullpen7979 said:
I am on android version 4.2.2 and windows xp SP 3. thanks for your response, sir.
Click to expand...
Click to collapse
The method that you thought was confusing, is the one you should use. If I have time, I could try helping you with it.
ALU0506, the build number is 13.9.0Q2.X-116-MX-17-57-1. Thanks everyone for your help.
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
I can try helping over gtalk.
bullpen7979 said:
I have downloaded the files mentioned in the thread. Thats as far as i have gotten. If you have time to help, that would be great. I mean like over the top great
Click to expand...
Click to collapse
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
bullpen7979 said:
I will try that as soon as I can and get back to you. I have two computers one at my hotel and one here. I'm not sure I have the ADB tools on my netbook
Sent from my XT1056 using xda app-developers app
Click to expand...
Click to collapse
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
jayboyyyy said:
if you are still looking for help i can help you get this done on gtalk as well. send me a pm with your username. it will take virtually no time at all
Click to expand...
Click to collapse
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
aooga said:
especially since he already unlocked the bootloader. Just flash recovery, then flash supersu.zip.
Click to expand...
Click to collapse
ya during his four days of misery, he could have just read for 1 hour on the stuff so it would seem confusing anymore and then he would have had a rooted phone. But either way, his problem is solvable with a few simple instructions.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
OK Jay/Aooga.
Finally back from work.
Plug in your phone and put it into fastboot by typing adb reboot bootloader then type fastboot devices does it show that you are connected?
open cmd window, typed adb reboot bootloader, and got:
T063202TFL and fastboot, and then a prompt.
Phone is in fastboot mode with white, yellow green text.
Device is unlocked. Status code 3.
Battery OK Charging
Transfer mode USB connected.
It looked as though I had to be able to accept the 4.4 kitkat OTA in order to get this done. but when i went to the usual spot to look for system updates it said there were none available.
Anyhow, I am super grateful for your help. Sorry to be such a remedial doofus
Looks like we can wait till tomorrow. Or today. Or whatever timeline it is.
I managed to borrow a Samsung Satellite laptop, so I could root and unlock my Nexus 6. Laptop is brand new. Everything was great on unlocking and rooting using Wogfresh's Nexus Tool Kit.
Then I decided to stop the forced encryption. Used Wug's Tool Kit again. At the end it says phone will reboot in 15 minutes. I waited over a half hour. Then I tried rebooting the phone. Now it flashed teamwin.
I can get it turned off. And I can still get it into recovery, bootloader mode, etc. I worked on this from 16:30 - 05:30 yesterday. I have been working today for another 3-4 hours.
Wug's Tool, the computer will not recognize the phone. Any help would be greatly appreciated. This is sooooo frustrating! I have uninstalled drivers, updated drivers, usbs too. I did everything Wug's kit said to do.
Sent from my SGH-I337 using Tapatalk
first off, stop using toolkits!
doing it properly is just as easy, and takes about 4-5 minutes, to unlock the bootloader, flash the recovery, flash the supersu zip, and to flash a custom kernel that wont bring on encryption(but you have format data for un-encryption to work).
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Good looking out! Thanks for all the information. I am positive that you must be of Wug's caliber, dev wise, right?
It's a real shame everyone doesn't know everything like you, huh? Also appreciate the directions on doing it your way, in 4-5 minutes.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
simms22 said:
assuming you got the driver installed..
1. while in bootloader.. fastboot oem unlock(this will unlock the bootloader
2. fastboot flash twrp recovery
3. flash the latest supersu with twrp recovery
this will give you root
4. flash any custom kernel(if you want to decrypt).
5. in twrp recovery, format data.
6. reboot and youll be rooted and unencrypted.
thats the basics, for any nexus. root toolkits can be used, if you already know what to do. if you are clueless of the process, youll learn ziltch using a roit toolkit, and will remain without any knowledge. so when you need to do some basic upkeep, you will be clueless, and will feel as your device is bricked. at that point youll start a pointless thread..
Click to expand...
Click to collapse
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
addcancercat said:
Thanks again. Did you read my post?
No I don't have drivers installed.
The computer does not recognize the phone now.
Please spare me anymore help.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
chris6278 said:
Dude lay off! You are forever on here giving ppl **** about the posts they make. Sorry if most ppl arnt as skilled as you and might actually need some help. Just cause your "recognized" doesnt make you a mod. If they have a problem with what someone post let them deal with it.
Click to expand...
Click to collapse
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
simms22 said:
have you went through and installed it yet? here is the page for the android adb driver as well, it should also work http://adbdriver.com/
---------- Post added at 07:45 PM ---------- Previous post was at 07:41 PM ----------
lay off what? with helping him out? no, im not a mod, nor do i want to be a mod(i have said no to xda mod offers before). but, i will always fight against lies and untruth, no matter what, no matter who says it. i dont come here, to xda, to learn. i mostly come here to help people out. if you dont want any help, thats fine, let me know and i wont help you. but if you are just here to give me crap about nothing except me going against what others say, get the fxxk out of here.
Click to expand...
Click to collapse
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
chris6278 said:
Help ppl? All you do is give ppl ****. Ive seen numerous posts where you act like an a55 just cause someone needed some help or putting ppl down for using toolkits. Look i dont come here to start anything with anybody but if i see ppl unfairly treated cause they are new or dont have much experience your gonna get called out on it. As far as "getting the fxxk out of here" nah i think ill stay
Click to expand...
Click to collapse
show me one post where i acted like an ass when someone needed help.
Simms is correct, its much easy to unlock using fastboot rather than a tool kit. When I first started modding it took me >5 minutes to learn how to do this. It always works and can really help you if you mess something up using a tool kit. If the OC doesn't recognize your phone, what screen is it showing (the TWRP logo) have you tried to hold power and volume down to boot into the boot loader? If you can boot into BL then you can flash anything via fastboot and fix this problem easily.
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
addcancercat said:
I am unlocked and rooted. When I tried change the forced encryption is when the phone became useless. I can get it into recovery (factory) and restart bootloader, etc.
But now it justs stay on the black and white Google when your first reboot your phone.
I have downloaded all the tools. I don't know the commands or the proper order.
My computer is not reconizing my phone after the encryption attempt.
Click to expand...
Click to collapse
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
simms22 said:
first thing you need to do is get the driver installed, so that your device would be disabled to your computer to adb/fastboot. you are going to have to flash the factory.img through your bootloader via fastboot. or, you can fastboot oem unlock your bootloader, flash a custom recovery, and adb push/sideload a rom/gapps/supersu to your phone and flash them via your new recovery.
Click to expand...
Click to collapse
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
addcancercat said:
Man you wouldn't know where I might find a more detailed step by step instructions on how exactly to do this. Then I could probably do it.
I have been updating drivers, uninstalling drivers, etc.
The tiol kit was great for unlocking and rooting. Then I tried to undo the forced encryption.
Sent from my SGH-I337 using Tapatalk
Click to expand...
Click to collapse
this should help you out. if you have anything to adk about it, ask there or here. good luck! http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Anyone else having issues getting the new T-Mobile 28k update to work? I have downloaded it from the official Google images site. When I try to flash through nrt it will not boot after its flashed just sits at goolge on the device. I've also tried flashing each file individually through fastboot and still same issue. It's like there isn't a system image being flashed even though I flashed one.. Any suggestions? I'm puzzled
Sent from my Nexus 6 using XDA Free mobile app
I don't use the NRT, so can't comment on it.
When flashing using fastboot, what images did you flash? And were all successful? (If you flashed bootloader and/or radio, did you reboot bootloader after each of those?)
Did you flash cache.img? If not, flash the cache.img and see if that helps
beachbum40 said:
Anyone else having issues getting the new T-Mobile 28k update to work? I have downloaded it from the official Google images site. When I try to flash through nrt it will not boot after its flashed just sits at goolge on the device. I've also tried flashing each file individually through fastboot and still same issue. It's like there isn't a system image being flashed even though I flashed one.. Any suggestions? I'm puzzled
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I just finished flashing my phone to 28K with NRT. I was on 48M, unlocked it and flashed it to 28J and then flashed it to 28K using the image dowloaded from Google. I had the Force Flash option checked.
Sound more like you have a corrupted boot.img since it looping at the splash. Try fastboot a boot.img from a new or custom download. Have seen images corrupted on download.
jj14 said:
I don't use the NRT, so can't comment on it.
When flashing using fastboot, what images did you flash? And were all successful? (If you flashed bootloader and/or radio, did you reboot bootloader after each of those?)
Did you flash cache.img? If not, flash the cache.img and see if that helps
Click to expand...
Click to collapse
Yea I finally got it I don't know what is going on I used fastboot adb and manually flashed about 30 times and still bootloop. I gave up on nrt. I like the tool for time saving but like I said it refused to flash with nrt and manual fastboot then all the sudden it worked. I downloaded the 28K factory images about 30 times as well. If it was corrupted it just finally decided to work. I've never had an issue like this in the past.
Sent from my Nexus 6 using XDA Free mobile app
prdog1 said:
Sound more like you have a corrupted boot.img since it looping at the splash. Try fastboot a boot.img from a new or custom download. Have seen images corrupted on download.
Click to expand...
Click to collapse
Don't want to sound to ignorant but could you explain to me how these boot.img get corrupted? I'm sure that's what it was because when NRT was checking the images and it said to verify the hash mdn and I copied the mdn from Google's official site and pasted it in the dialog box on nrt it said match the first time when I tried to flashed 28K then it failed. Then I tried again and put the same mdn in the dialog box and nrt said mismatch. So I'm confused as hell.
Sent from my Nexus 6 using XDA Free mobile app
beachbum40 said:
Don't want to sound to ignorant but could you explain to me how these boot.img get corrupted? I'm sure that's what it was because when NRT was checking the images and it said to verify the hash mdn and I copied the mdn from Google's official site and pasted it in the dialog box on nrt it said match the first time when I tried to flashed 28K then it failed. Then I tried again and put the same mdn in the dialog box and nrt said mismatch. So I'm confused as hell.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Usually when get a bad download you can't unzip it. When they put these images inside the zip the zip is good but don't mean the image is good. That is why they give you an MD5 with the download. Under normal conditions such as rom download can pretty much tell if download is bad cause can't access the file with 7zip ect. It is different with the zipped images. Any one image can be corrupt. but zip is good. I have had downloads with either/or/and system.img or boot.img was bad and all the others worked. Hope this makes sense. Lol
---------- Post added at 12:07 AM ---------- Previous post was at 12:00 AM ----------
Skip the toolkits till understand how it works with manual fastboot. Will save a lot of head banging when you need to fastboot fix a toolkit fail. I have used toolkit to play with it. Had many fails and used fastboot to fix. If using toolkit never pick the lock bootloader option. Good way to brick the device.
prdog1 said:
Skip the toolkits till understand how it works with manual fastboot.
Click to expand...
Click to collapse
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
NLBeev said:
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
Click to expand...
Click to collapse
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Sent from my Nexus 6 using XDA Free mobile app
NLBeev said:
Allow me to add an argument.
Manual fastboot requires command line input and the 'speed' is controlled by yourself.
Toolkits use scripts and you won't be fast enough to stop when you choose the wrong option.
Click to expand...
Click to collapse
I use adb fastboot and have manually installed plenty times. Tool kits are convenience
Sent from my Nexus 6 using XDA Free mobile app
beachbum40 said:
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Click to expand...
Click to collapse
Same here. Nice to meet you.
beachbum40 said:
I only use tool kit as a time saver I do know my way around adb / fastboot. Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
timesaver toolkits are not, as things are quicker when done the right way. for example, it takes about 3 minutes to root your phone, if done the right way.
i tend to disagree on this one.
if the tool is made properly, all its doing is automating the commands and steps you would be using manually.
its not like its using a whole different method.
the tool could actually be better to use, if made properly, with Mfastboot. most users would use standard fastboot, instead of moto's fastboot, Mfastboot.
beachbum40 said:
I use adb fastboot and have manually installed plenty times. Tool kits are convenience
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Adb and fastboot are two completely different tools.
bweN diorD said:
i tend to disagree on this one.
if the tool is made properly, all its doing is automating the commands and steps you would be using manually.
its not like its using a whole different method.
the tool could actually be better to use, if made properly, with Mfastboot. most users would use standard fastboot, instead of moto's fastboot, Mfastboot.
Click to expand...
Click to collapse
Our point is using tool kits doesn't help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
All I was saying is I use both toolkit and fastboot. That's all. Thank you have a nice day?
Sent from my Nexus 6 using XDA Free mobile app
beachbum40 said:
All I was saying is I use both toolkit and fastboot. That's all. Thank you have a nice day?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I was just correcting you when you said "adb fastboot" as if it was one thing, not two unrelated things.
danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
i should have quoted simms last post.
i dont disagree with what you are saying, but do with the inference that toolkits use some inferior method, which isnt the case.
danarama said:
Adb and fastboot are two completely different tools.
Our point is using tool kits does help the learning process. We mostly believe that people should use fastboot manually to ensure they have a good set up and get accustomed to the commands.. This way, when they get in trouble and we have to help fix it, we don't have to teach them to use fastboot and set up their computer, we can go straight to helping resolve whatever actual issue they have - because tool kits cannot always help them.
Click to expand...
Click to collapse
your first line. toolkits does help the learning process. with that i disagree 1000000%. why? because the tool kits dont go through and explain each process to the user. they tend not to explain anything actually.
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
ok, toolkits.. they do work usually(every once in a while they do mess up). problem is with new users. toolkits dont teach them anything, not even basics, in case they mess up(and they do). by going through the rooting process the first time, properly, instead of toolkit, the user gets to learn the basics of every android process. by knowing thise basics, the yser can fix 99.99% of issues that pop up. with a toolkit, you dont get to learn the basics. so i tell everyone that toolkits are fine, just do thd rooting one time manually, then use the toolkit whenever you want after that.
simms22 said:
your first line. toolkits does help the learning process. with that i disagree 1000000%. why? because the tool kits dont go through and explain each process to the user. they tend not to explain anything actually.
---------- Post added at 03:47 PM ---------- Previous post was at 03:42 PM ----------
ok, toolkits.. they do work usually(every once in a while they do mess up). problem is with new users. toolkits dont teach them anything, not even basics, in case they mess up(and they do). by going through the rooting process the first time, properly, instead of toolkit, the user gets to learn the basics of every android process. by knowing thise basics, the yser can fix 99.99% of issues that pop up. with a toolkit, you dont get to learn the basics. so i tell everyone that toolkits are fine, just do thd rooting one time manually, then use the toolkit whenever you want after that.
Click to expand...
Click to collapse
problem is, as long as there is a toolkit, 99% of people wont listen to you and will use the toolkit. there simply lazy and will never really appreciate any mods they do, because they did nothing more than click a few buttons...
bweN diorD said:
problem is, as long as there is a toolkit, 99% of people wont listen to you and will use the toolkit. there simply lazy and will never really appreciate any mods they do, because they did nothing more than click a few buttons...
Click to expand...
Click to collapse
thats ok, as long as at least one person listens then im not wasting my time. and i know that at the very least that at least one person has listened to my advice
the other 99%, some will think that their phone is bricked, some will go back and learn, some will be successfull with toolkits. and some just wont ever learn a thing
Ok so I have a stock, rooted, unlocked but encrypted Nexus 6. Last night it took a bad fall. The glass only cracked in one spot, however the LCD is cracked in several areas. Turning the phone on resulted in a black display. it flickers a few small bars of convoluted color, then goes black. The phone was still on and with launch everywhere I could still "Ok Google..." to do a few things.
Now, like the total idiot I am, for some damn reason I turned the phone off after getting off the phone with Asurion. And because of encryption and the screen being unresponsive (black display) I can't enter the damn screen pattern to unlock it, so I can't boot it up to drag and drop files or use adb to wipe the phone.
Does anyone have any suggestions to where I can somehow either access my files or at the very least wipe the phone? Most of my info that was on the phone is backed up to Googles servers. The are few items that aren't, that I hope I can get, but if I can't, I need to make sure are wiped. Can I enter fastboot without the pattern unlock? Or should I look into someone to repair the screen to at least get it turned on and functional to do what I need?
Thanks in advance!
Phaded said:
Can I enter fastboot without the pattern unlock?
Click to expand...
Click to collapse
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
jj14 said:
If memory serves me right, you can run fastboot commands without having to enter the pattern/pin.
Click to expand...
Click to collapse
OK thanks. I will try that when I get home and just flash the factory image to wipe. thanks!
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Eh screw it... Just gonna send it into Motorola
Phaded said:
Hmm... from Google support pages:
If your device is running Android 5.1 or higher: Your device is protected to prevent other people from using it if it's been reset to factory settings. To ensure that it's really you doing the reset, you'll need to enter a Google username and password associated with the device after factory reset. If you don't have this information, you won't be able to finish the setup process and use the device at all after factory reset.
Does this mean even if I wipe it, the phone won't be usable for anyone?? they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
simms22 said:
yup, mean even after you wipe it, lets say 100 times, itll still ask you for your password. its security, there would be no point if you could wipe it away. but, there is a way to get rid of it, by flashing the 5.0 or 5.0.1 factory images.
Click to expand...
Click to collapse
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Phaded said:
oh so if i flash an older factory image that didn't have that security feature it'll work? thanks.
Click to expand...
Click to collapse
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Phaded said:
they can't refurbish the phone because the phone will need my google info??
Click to expand...
Click to collapse
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
simms22 said:
yes, as long as your bootloader is unlocked. those images didn't have the security yet.
Click to expand...
Click to collapse
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
jj14 said:
Hate to say this, but that's their problem You can bet that Google/Motorola will know how to get around it
---------- Post added at 01:42 PM ---------- Previous post was at 01:40 PM ----------
Wasn't there some issue with downgrading the bootloader causing problems? Or am I confusing with some other device?
Click to expand...
Click to collapse
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
byrdcfmma said:
It's my understanding, but I am new to the N6 so correct me if I am wrong, you can downgrade the 5.0 or 5.0.1 factory img as long as you don't downgrade to 71.05 bootloader.
Click to expand...
Click to collapse
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
jj14 said:
that sounds about right. Just wanted to make sure op didn't flash all images in the factory image
Click to expand...
Click to collapse
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
byrdcfmma said:
Maybe someone with more exp can give the exact process. I assume you are looking for a img with no bootloader, recovery, and radio like these http://forum.xda-developers.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052 but older img's
I just got my N6 yesterday, and been reading my a$$ off so I don't mess anything up. So far I have unlocked the bootloader, rooted and installed TWRP.
Click to expand...
Click to collapse
One can always go to the google developer images site (developers.google.com/android/nexus/images) and download the image they need. Unzip the downloaded file, and unzip the resulting file. In that, you'll find yet some img files, and yet another zip file that will contain the rest of the img files. Choose which one you want, and flash away
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
I'm currently in the exact same predicament. Let me know how it goes.
Phaded said:
Ok so I was able to get it so the lock screen pattern is gone.
At this point I'm about to do insurance claim.
I want to pull my data (pics etc) off.
I have twrp installed and can get into recovery. Adb devices results in showing my device.
Adb/USB debugging isn't active when booted normally as I flashed new system
Tried using a tool to pull using adb, but no data gets pulled
Anyone have a method for pulling my data off? It's set to charge mode by default so it doesn't show in windows explorer.
Thanks
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Use adb pull from booted into recovery.
danarama said:
Use adb pull from booted into recovery.
Click to expand...
Click to collapse
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
This is the tool I tried to use:
http://forum.xda-developers.com/showthread.php?t=2339530
Sent from my Nexus 6 using XDA Free mobile app
Phaded said:
Do you happen to know what path I would enter to pull from? I have to specify the target correct? I tried using an adb recovery tool, but when it went to /sdcard it said that path didn't exist.
I believe right now I flashed a 5.0 image (pre forced encryption?)
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
danarama said:
Is it lollipop?
You need to mount data or sdcard first.
this should work
Code:
adb shell
mount /data
exit
adb pull /data/media/0/* c:\users\phaded\desktop\mybackup\
I've made some assumptions above.
Click to expand...
Click to collapse
Yes it's lollipop, just an earlier version of it that didn't have the pattern lock (or whatever security) prompt at boot. I think 5.0.1.
I'm not rooted, does that matter for adb shell in recovery?
/data/media/0/ is my whole sd card correct? Is there a command that will show my directory in that path so I can cherry pick the folders to extract?
Sent from my Nexus 6 using XDA Free mobile app
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Download factory image, extract, flash each img file separately except for userdata.
Mostlyhrmlss said:
Full stock LVY48H on Fi . I've been wanting to go Marshmallow, but Google hasn't gotten around to sending me the OTA. I found this thread in the General forum and downloaded the appropriate .ZIP, but the contents don't look a bit like the ROM downloads, so fastboot doesn't appear to be an option. How do I put it on?
Click to expand...
Click to collapse
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
Click to expand...
Click to collapse
RTFM
Tower1972 said:
If your bootloader is unlocked, you can flash it manually in ABD or use that toolkit (for factory image). I did that but it it also wiped my phone, which was fine by me, it needed a good cleaning after flashing updates to another custom 5.1.1 rom over and over again!
Click to expand...
Click to collapse
when youre giving advice to someone, make sure that its correct. you dont flash anything with adb, you use fastboot. fastboot is different than adb.
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Mostlyhrmlss said:
@boomerbubba: FTFY: Here's a guide on how to do that. I prefer civility when applicable; my sympathies for whatever is going on in your life to make you want to answer in such a way.
@simms22: Turns out the advice was correct: "adb sideload [OTA file].zip" is the appropriate command to accomplish what I'm after here.
Some strategic Googling found me the answer while I was awaiting responses, here it is for the benefit of anyone who should have the same question. Prollyshooda done that first.
Click to expand...
Click to collapse
actually, you were incorrect. you said use adb to manually flash. now you said adb for adb sideload. those are two completely different things. all adb sideload does is move a file from your computer to your phone.
edit.. now you are right, i read your response wrong :angel:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Mostlyhrmlss said:
Contrition on the Internet? Whodathunkit! We should get together for a beer, I like your kind of folk.
Click to expand...
Click to collapse
contrition is one of the things that pull me down. but its honesty, and the truth. so i stay with it
Mostlyhrmlss said:
@nhizzat: I was thinking that, but I'd only done a factory load that way and wasn't sure if I could do a full version jump without cats and dogs living together and mass hysteria (i.e. having to reload all the personals), so I was happy to find that OTA thread. Shame they didn't bother with practical matters such as what to do with that information.
@Tower1972: Attached is a screenshot of the contents of the ZIP. How would I go about flashing that with ADB?
Click to expand...
Click to collapse
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
nhizzat said:
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
It doesn't require an unlocked bootloader. Which for the people that haven't done that, it wipes your phone as part of the unlock process.
Also, it is a smaller download if you are on an ISP with limited bandwidth.
Google says....
http://https://developers.google.com/android/nexus/images
That will get you going, but since the included script won't work, you have to unzip the zip package, what you will find inside the parent folder. Happy flashing
nhizzat said:
I don't know what zip file that is, but it's not a factory image from Google. If you download a factory image from Google, you extract every img file and flash using fastboot.
What is everyone's fascination with adb sideload?
Click to expand...
Click to collapse
That ZIP is an OTA downloaded from the thread referenced in my original post. My fascination with adb sideload (now that I know what it is) is that I can accomplish an upgrade with a single command, which suits my advanced case of laziness very well . Seems much easier than unzipping a file, then unzipping a file from that file (more than doubling the storage requirement, I have a rather small SSD) and issuing several fastboot commands with slightly different syntaxes and hoping I didn't miss (or mistype) something.
I already know how to do a full flash, I unlocked the bootloader and did so first thing when I bought it used to make sure it was cleared of the previous owner's data and completely up-to-date. What I wasn't sure of is if it would be safe to do so for a full version jump. I'm much more comfortable with OTAs since I've applied several and it stands to reason that a carrier would never issue one if it might cause an undue number of problems for their support staff to address.
Martend said:
That will get you going, but since the included script won't work...
Click to expand...
Click to collapse
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Mostlyhrmlss said:
That script just burns my biscuits. Why in the name of all that is neat and groovy can't Google fix such a basic problem?
Click to expand...
Click to collapse
because its fixed in the latest version of fastboot, that no one seems to be using..
simms22 said:
because its fixed in the latest version of fastboot, that no one seems to be using..
Click to expand...
Click to collapse
Why break it in the first place? lol It's the first thing you learn here, debug & test before releasing it to the masses
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. The device shows up in the Windows device manager when in bootloader mode, but disappears when I go to recovery mode. What am I doing wrong?
Mostlyhrmlss said:
So, I got the latest ADB and FASTBOOT from here, put the device in ADB update mode through recovery mode (already OEM unlocked and USB debugging enabled), ran 'adb sideload <filename>' as instructed onscreen, and got "error: device (null) not found" from the command. What am I doing wrong?
Click to expand...
Click to collapse
do you have the drivers installed? fastboot wont see your device until then.
I installed the drivers as part of the ADB/FASTBOOT package referenced above, but that's not the problem: the device is not shown at all in the Windows device manager, as if it wasn't plugged in.