I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
FireMedic1234 said:
I am trying to apply an update that was pushed to my Verizon Nexus 6. I was using Nexus Root Toolkit V2.0.5 developed by Wug, to do the unroot and re-lock the boot loader. It went fine no issues, have the correct build of android plugged into the toolkit. Rebooted, and I used root checker to verify that root is gone, and it is not, it is still rooted. I can unroot using supersu, and root checker confirms that root is gone. After locking the bootloader, I go and try to apply the update and it still fails. I am able to restart the phone and use it, but I do not understand what is going on with it. Anybody have any thoughts?
Click to expand...
Click to collapse
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
simms22 said:
for the couple thousandth time it has been mentioned here, you can not apply an update if any stock files have been changed. with you having root at one point, your files have been changed. and to really unroot, you have to flash a factory image. otherwise, even tjough you unrooted, your files are still changed.
Click to expand...
Click to collapse
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
FireMedic1234 said:
Yeah hey thanks hadn't seen that a million times or so. I know updates cannot be flashed while rooted or unlocked. I am trying to unroot by flashing a factory image and it is not taking, no errors come up in the log and it reboots fine.
Click to expand...
Click to collapse
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
simms22 said:
are you using fastboot while you are in your bootloader? oh, and you need an unlocked bootloader as well.
Click to expand...
Click to collapse
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
FireMedic1234 said:
Yes I am. I had locked the bootloader and tired to apply the update and that didn't work. I currently have an unlocked boot but did not root yet, was waiting for feedback from here.
Click to expand...
Click to collapse
ok, boot into the bootloader, connwct via usb to your computer, the type fastboot devices. at that point, it should list your phone via a number. if it does, then its all connected right. then you can flash the factory image, but do not use the flash-all script, flash them all individually.
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
FireMedic1234 said:
Ok thanks, Does it work the same if you do it through Wugs tool, clicking the flash stock + unroot button, and letting it run the scripts?
Click to expand...
Click to collapse
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
I concur. I have used "the" toolkit to see what happens. Have had multiple failures using toolkit and always had to revert to fastboot to fix. Might as well use fastboot up front. Saves a lot of time and headaches.
simms22 said:
ill be honest.. its best to do it the first time manually. that way you learn to do things that can fix your phone in the future, plus tool kits can and fo mess up occasionally, which make things hard to fix. i tell everyone that they can use toolkits, but they wont learn anything and will remain clueless. if you already know what you are doing, then tool kits are fine
Click to expand...
Click to collapse
Gotcha thanks again!
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You can drag and drop or copy/paste the image into the command line.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
are you flashing with flash-all or are you flashing each image individually. dont use flash-all, flash them individually.
Share a screen print of the command prompt, with the command you executed, and the error message?
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
FireMedic1234 said:
was doing the flash-all. is the command "fastboot flash system system.img" minus the quotes? If that doesn't work I will try and drop and drag see if that works
Click to expand...
Click to collapse
Yes.
FireMedic1234 said:
When I try to flash system.img it errors out saying it is not there, but it is. any thoughts?
Click to expand...
Click to collapse
You don't need to put the system.img there. Please do read general > sticky roll-up thread > adb and fastboot...
...some time.
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
FireMedic1234 said:
I guess my issue was in my head. I am so damn concerned that I am going to do something wrong and brick the phone that I am afraid to run the commands. I just flashed the system.img had it write in 4 different parts.... and it worked fine, rebooted and everything.... so far.
Click to expand...
Click to collapse
Yes the flash-all.bat can't break up the image. Has something to do with how it sees the partition. Have heard that fastboot in SDK 23+ has fixed this problem. Have not confirmed as I do each individually anyway depending on what I want to do.
---------- Post added at 12:13 PM ---------- Previous post was at 12:07 PM ----------
Only way you're gonna possibly brick is flash wrong image to wrong partition. Not sure that even that can be corrected with fastboot as long as the one you bork isn't the bootloader.
Related
"FIRMWARE TEAM" Presents:
AT&T ICS 4.0.4
7.7.1Q-144_MB886_MR1-22_SIGNED_CFC.xml.zip
Upload by Skrilax_CZ, Download Coming Soon in http://sbf.droid-developers.org/dinara/list.php
Upload by daywalker04, Download Coming Soon in http://forum.xda-developers.com/showthread.php?t=1853522
Live: http://sbf.droid-developers.org/dinara/list.php
Just got my first Motorola with this phone, but think I borked it by messing with the radio bands. How does one flash these .xml or .sbf files to restore to original stock?
failed flashing process..unknown fastboot comand
I'm grabbing this for my friend, he can't get the update because he needs Wi-Fi and the phone won't connect to our University's Wi-Fi network. This won't break OTA for him though will it?
It's just as same as if you have applied OTA.
what is the update process?
Skrilax_CZ said:
It's just as same as if you have applied OTA.
Click to expand...
Click to collapse
so what exactly is the update procedure?
Here's what my phone is showing me.
system version: 77.1.7.MB886.ATT.en.US
android version: 4.0.3
Will this update change anything with the bootloader or anything like that?
aerohp said:
so what exactly is the update procedure?
Here's what my phone is showing me.
system version: 77.1.7.MB886.ATT.en.US
android version: 4.0.3
Will this update change anything with the bootloader or anything like that?
Click to expand...
Click to collapse
If you got 4.0.3 we need a copy of your OS before you upgrade. 4.0.3 has vulnerabilities that we need to get root. Sorry I don't know the procedure, but I am sure some dev will be more than willing to tell you.
Skrilax_CZ said:
It's just as same as if you have applied OTA.
Click to expand...
Click to collapse
popfan said:
If you got 4.0.3 we need a copy of your OS before you upgrade. 4.0.3 has vulnerabilities that we need to get root. Sorry I don't know the procedure, but I am sure some dev will be more than willing to tell you.
Click to expand...
Click to collapse
are there any specifics to the vulnerabilities?
anyways, if someone lets me know how make a copy of the OS, i'd be more than willing to do so.
aerohp said:
are there any specifics to the vulnerabilities?
anyways, if someone lets me know how make a copy of the OS, i'd be more than willing to do so.
Click to expand...
Click to collapse
Just saw this and need to let you know not to do any soft of fastboot or updating without backing up your files. The worry is you flash a retail bootloader and possibly cannot go back if you use these.
mattlgroff said:
Just saw this and need to let you know not to do any soft of fastboot or updating without backing up your files. The worry is you flash a retail bootloader and possibly cannot go back if you use these.
Click to expand...
Click to collapse
yeah, that's why i'm holding out... battery life sucks on the 4.0.3. it barely gets me 8-9 hours with moderate use. i've noticed there are huge drops in the battery level every now and then. i guess i'll just deal with it until we get the root thing sorted out.
is there a way to just mount the system.img.ext4? i've tried ext2explore and i've tried to mount it with Linux Reader. thanks
mrvirginia said:
is there a way to just mount the system.img.ext4? i've tried ext2explore and i've tried to mount it with Linux Reader. thanks
Click to expand...
Click to collapse
i'm wondering the same thing...i'm not flashing this on my phone but a friend of mine has a retail 4.0.4 and can't get the OTA. i;m not really sure how to flash this. i was hoping for it to be an sbf but thats not the case. can someone point the way please?
aerohp said:
i'm wondering the same thing...i'm not flashing this on my phone but a friend of mine has a retail 4.0.4 and can't get the OTA. i;m not really sure how to flash this. i was hoping for it to be an sbf but thats not the case. can someone point the way please?
Click to expand...
Click to collapse
just use fastboot oem fb_mode_set
then fastboot flash .......
cmvienneau said:
just use fastboot oem fb_mode_set
then fastboot flash .......
Click to expand...
Click to collapse
Flash what exactly? I've been trying this for the past hour and rsdlite won't work, moto-fastboot doesn't give any hints. I've tried MR1-22 and FFW-14.
darknessrise1234 said:
Flash what exactly? I've been trying this for the past hour and rsdlite won't work, moto-fastboot doesn't give any hints. I've tried MR1-22 and FFW-14.
Click to expand...
Click to collapse
Edit the XML file within the ZIP. Remove the two lines that contain "GETVAR". then flash the zip
mandrsn1 said:
Edit the XML file within the ZIP. Remove the two lines that contain "GETVAR". then flash the zip
Click to expand...
Click to collapse
After removing that, the modem lines and the oem_mode_set one... It still fails on the system.img.ext4.
EDIT: Out of thoughts. Stuck with a fastboot loop. Won't even allow me to turn it off.
I installed beats installer and my phone will not reboot. Any Ideas?
tried the same thing, now stuck at the boot animation. I have tried factory reset as well as downloading the firmware and trying to update from the sd card in recovery. No luck. It is now a brick unless someone can help...
Av8tor86 said:
tried the same thing, now stuck at the boot animation. I have tried factory reset as well as downloading the firmware and trying to update from the sd card in recovery. No luck. It is now a brick unless someone can help...
Click to expand...
Click to collapse
This sucks, I have no idea what could have happened. I really hope someone can help!!
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
bd1212 said:
I'm currently rooted and am running only Xposed Mods with a few root apps. How can I unroot my phone and get the stock recovery back onto my Moto X so that I can take OTA's again without wiping all of my data? What files do I need to download/flash and how do I do it? I've searched around, but it just got me even more confused.
Click to expand...
Click to collapse
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
jonnythan said:
You need to use fastboot to push system.img and recovery.img from the version of the OS you're currently running. See here for a list of OS images:
http://sbf.droid-developers.org/ghost_rcica/list.php
See this thread for a link to a fastboot.exe that'll work:
http://forum.xda-developers.com/showthread.php?t=2527287
See this thread for a quick overview and link to more detailed info:
http://forum.xda-developers.com/showthread.php?t=2525495&page=4
Click to expand...
Click to collapse
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
bd1212 said:
Thanks for the info and links. I'm currently downloading the OS that I'm currently running (VZW OTA update in my case), but I have one question: How do I use fastboot? When I double click that .exe nothing happens.
Click to expand...
Click to collapse
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
meant2live218 said:
Someone correct me if I'm wrong, but I believe that flashing the stock system will remove all the changes you've made with root/xposed modules, and flashing the stock recovery should essentially get rid of root (I think).
I don't know precisely where to get all the files, but if you find them around, you can push them using ADB.
If you're like me and are okay with losing everything on the phone, go ahead and use RSDLite (it requires ADB). It's easy-ish to use, and there's even a video tutorial that covers everything after installation of all the files.
Click to expand...
Click to collapse
I was under the impression that we cannot do a factory reset or we won't get the soak test OTA pushed to our phones. That's what the soak test post said atleast. Something along the lines of "DO NOT FACTORY RESET or you will not receive the OTA"... don't want to quote it directly since I'm under an NDA, but it was something like that. Did I misunderstand? If I use the Moto X toolkit or RSDLite to revert back to stock is that different than a factory reset?
jonnythan said:
You need to install the Android SDK and the platform tools, then boot your phone into fastboot mode. You need to run a command line to flash the IMGs. It's explained in the links.
Click to expand...
Click to collapse
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file. I'm still reading all of the links so I might not have gotten to the part where it explains what to do, so forgive me for that.
bd1212 said:
I've got the Android SDK install and ADB is setup. I'm pretty familiar with ADB. I moved the motorola fastboot.exe into platform-tools and I know how to put the phone into fastboot mode. What I don't understand is what I need to do once I've got the system.img file and the recovery.img file.
Click to expand...
Click to collapse
Right from my third link:
Next, you need to put the phone into "fastboot mode" as described above, also make sure usb debugging is enabled in the developer menu settings. Then download the FW for your phone found (follow what i said in regards to the other persons post below), then unzip that, put the system and recovery image in the same directory that your fastboot and adb is in, then run these commands from the cmd prompt
fastboot flash system system.img
fastboot flash recovery recovery.img
then your done, you can type
fastboot reboot
Click to expand...
Click to collapse
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Yep, just got to that part lol. Having some trouble downloading the VZW file. My current download just stopped with a network error and the website that is hosting the files keeps saying service unavailable and to contact the website administrator. Weird. I'm blaming it on my college's ****ty wireless network.
Edit: Yup, for some reason the wifi at the school decided it need me to input my credentials to re-login for the 6th time today to verify who I am and allow me internet access.
Edit 2: The things I'd do to have a stable connection... Once again, the download failed halfway through because the damn connection at this college sucks. This is infuriating.
jonnythan said:
Right from my third link:
Click to expand...
Click to collapse
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
bd1212 said:
Is there anyway you (or someone else) could upload the VZW OTA update file to Google Drive or Dropbox for me? This download is going way to slow to the point where I can't even finish it before my connection craps out. Or can you (or someone else) just upload the system.img and recovery.img files for me?
Click to expand...
Click to collapse
Uploading now, but it'll take a bit. Big file.
jonnythan said:
Uploading now, but it'll take a bit. Big file.
Click to expand...
Click to collapse
Thanks man. You don't even know how much I appreciate this.
Which one of the two is the camera update for vzw?
Where do you get stock recovery?
EDIT: Sorry, Nevermind. I probably extract it from the zip.
Sent from my XT1060 using xda app-developers app
I have been rooted for a few months now and need to get a replacement phone from vzw. I have been searching for the better part of 2 days on how to completly unroot my nexus 6. i used the method used in "[HOW-TO] The Nexus 6 All-In-One Beginner's Guide By xBeerdroiDx" to root it. Which installed TWRP, with any other phone ive rooted i could just go to SuperSU and click full unroot and it would do it. That is not the case now. Can i get a step by step directions from someone on how to unroot my phone please.
Thanks in advance.
djhudjr said:
I have been rooted for a few months now and need to get a replacement phone from vzw. I have been searching for the better part of 2 days on how to completly unroot my nexus 6. i used the method used in "[HOW-TO] The Nexus 6 All-In-One Beginner's Guide By xBeerdroiDx" to root it. Which installed TWRP, with any other phone ive rooted i could just go to SuperSU and click full unroot and it would do it. That is not the case now. Can i get a step by step directions from someone on how to unroot my phone please.
Thanks in advance.
Click to expand...
Click to collapse
sure.. get the factory image from the google site, download it to your computer, unzip it, then flash each part of it individually via fastboot while youre in your bootloader. thats the only real way to "unroot" a device.every othet way removes root but keeps the changed files. so they think that youre still rooted.
simms22 said:
sure.. get the factory image from the google site, download it to your computer, unzip it, then flash each part of it individually via fastboot while youre in your bootloader. thats the only real way to "unroot" a device.every othet way removes root but keeps the changed files. so they think that youre still rooted.
Click to expand...
Click to collapse
So after i flash each part it will be "Unrooted" or do i have to delete anything else?
djhudjr said:
So after i flash each part it will be "Unrooted" or do i have to delete anything else?
Click to expand...
Click to collapse
nope, thats it. but, to finish, you want to make sure that you will boot first, then youll have to relock your bootloader at the very end
djhudjr said:
So after i flash each part it will be "Unrooted" or do i have to delete anything else?
Click to expand...
Click to collapse
if you want the phone clean, you will need to use -w command in fastboot to wipe all the data also.
bweN diorD said:
if you want the phone clean, you will need to use -w command in fastboot to wipe all the data also.
Click to expand...
Click to collapse
ive never wiped before flashing a factory image(i assumed it does it automatically before flashing each partition), but that can be a good idea as well :good:
simms22 said:
ive never wiped before flashing a factory image(i assumed it does it automatically before flashing each partition), but that can be a good idea as well :good:
Click to expand...
Click to collapse
-w only wipes the data partition as far as i know.
i havent dissected the files for this phone, but all past device img's i have, has a wiping command of some sort in there somewhere.
its usually something like "erase userdata" or similar.
the files are .tar and .tgz my computer wont recognize them am i doing something wrong?
djhudjr said:
the files are .tar and .tgz my computer wont recognize them am i doing something wrong?
Click to expand...
Click to collapse
you need software to open the archives. i think win rar may do it, but im not positive.
simms22 said:
sure.. get the factory image from the google site, download it to your computer, unzip it, then flash each part of it individually via fastboot while youre in your bootloader. thats the only real way to "unroot" a device.every othet way removes root but keeps the changed files. so they think that youre still rooted.
Click to expand...
Click to collapse
ok so noob it down because i cant seem to figure out how to flash it from my pc to my phone. it isnt showing up
djhudjr said:
ok so noob it down because i cant seem to figure out how to flash it from my pc to my phone. it isnt showing up
Click to expand...
Click to collapse
you need fastboot(and adb for other things). you can get that from google or you can search google for a smaller download. its in the sdk( i believe), but that download is huge. i installed a fastboot for dummies version a few years back, with adb as well, and ot turned out to be only 35mb.
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
i think fastboot is in this zip too, let me know if its not.
http://www.mediafire.com/download/2845j2d8tqzi6at/adb.rar
---------- Post added at 08:13 PM ---------- Previous post was at 08:10 PM ----------
heres the proper mfastboot if you want that
http://www.mediafire.com/download/abfnoae9hdeyh5k/mfastboot-v2.zip
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
ChiefEli said:
so here is what happened, i was rooted with an unlocked boot loader running chroma rom. i then tried to unroot my device to return completely back to stock. After the process was done, i formatted and wiped everything then did a reboot. when android started up chroma rom was still on there and i can't access developer settings to unlock my boot loader to flash stock image. so now i am stuck with a locked boot loader and a bootloop device. i have tried adb sideload and got back 2 errors that the footer is wrong and the signature. i don't know what to do now. so Please Help! thank you in advance.
another thing i should add, i only have access to stock recovery
Click to expand...
Click to collapse
do you have twrp recovery, or the stock recovery?
i have stock recovery
linezero said:
i think this toolkit got a boot loop fix although i have never tried it
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
Click to expand...
Click to collapse
ChiefEli said:
i have stock recovery
Click to expand...
Click to collapse
The only option is try and fastboot format userdata and fastboot format cache.
If they don't work, there is no fix. Nothing a toolkit can do.
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
simms22 said:
yup, @danarama has the right explanation. problem is that with stock recovery it most likey will not work. sorry
Click to expand...
Click to collapse
damn, well i will try it using the toolkit and let you know how it goes.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
good luck!
at the very least, it might help you fix the bootloop.
ChiefEli said:
damn, well i will try it using the toolkit and let you know how it goes.
Click to expand...
Click to collapse
Has to have unlocked bootloader for that toolkit option to work.
prdog1 said:
Has to have unlocked bootloader for that toolkit option to work.
Click to expand...
Click to collapse
simms22 said:
Click to expand...
Click to collapse
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
prdog1 said:
Here is the option. Direct from Wug's FAQ. "If you device is bootlooping or can’t boot up, use “Flash Stock + Unroot” with the “Soft-Bricked/Bootloop” option and follow the onscreen instructions for manually booting your device into bootloader mode and restoring your device."
Can't use flash stock option without an unlocked bootloader.
Click to expand...
Click to collapse
oh well, another "brick"..
simms22 said:
oh well, another "brick"..
Click to expand...
Click to collapse
Pretty much. I have to concur.
prdog1 said:
Pretty much. I have to concur.
Click to expand...
Click to collapse
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
simms22 said:
its sad really. but this happens so often that i dont feel as bad about it anymore. now thats sad
Click to expand...
Click to collapse
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
We don't know but this sucker likes to bootloop. Never relock the device till after it boots and running. Concerning relocking non-stock have seen it bork TWRP and kernel.
byrdcfmma said:
Why is this happening so often. Sorry but getting late to the party, I just bought my N6 from Best Buy and have been trying to get caught up on all the reading before it gets here. Is it user error or something else?
BTW, from what I see he can probably break it down and sell the parts on ebay then get close to a new one for $350.
Click to expand...
Click to collapse
because many people dont read and educate themselves beforehand.
I don't understand why people are re-locking their boot loader. Unless you are returning the device, what is the purpose of re-locking it? I don't get, in this particular thread, why or how the boot loader got locked?
BladeRunner said:
I don't get, in this particular thread, why or how the boot loader got locked?
Click to expand...
Click to collapse
And that is a key question.
I was trying to get ready to turn in my nexus 6 and so I flashed a stock rom (apparently minus the recovery) and relocked my device. I now have twrp but stock 5.1 installed. twrp boots okay but internal storage is 0mb and it appears unable to format partitions. any ideas on a resolution? very comfortable with fastboot (bootloader loads normally) but can't seem to get anything working otherwise.
Can you flash ROMs without root?
What twrp version is best for this device? Thanks
Tmobilefan906 said:
Can you flash ROMs without root?
Click to expand...
Click to collapse
Yes. You do have to have your bootloader unlocked though. Most custom ROMs come rooted once you flash them.
Tmobilefan906 said:
What twrp version is best for this device? Thanks
Click to expand...
Click to collapse
I'm using 2.8.7.0 and haven't had any issues.
coal686 said:
Yes. You do have to have your bootloader unlocked though. Most custom ROMs come rooted once you flash them.
I'm using 2.8.7.0 and haven't had any issues.
Click to expand...
Click to collapse
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Tmobilefan906 said:
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
Click to expand...
Click to collapse
And is facepalm still working for s off? I heard they stopped deving for it. Thanks again.
Tmobilefan906 said:
I'm no stranger to this....just making sure. Lol. How can I sideload a ROM? There's no o.s on mine. Do I go to a cmd prompt and type su...then adb push.....? I've always had issues with adb side loading. Thanks.
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
And is facepalm still working for s off? I heard they stopped deving for it. Thanks again.
Click to expand...
Click to collapse
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Sloth said:
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Click to expand...
Click to collapse
OK. Every time I tried that, it kept saying error. All drivers were installed..drivers for while in BL, normal mode and recovery were installed on my PC. Maybe I typed it wrong. After .zip, there is a space then /sdcard/...right?
coal686 said:
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
Click to expand...
Click to collapse
Yea, the phone has 2.6.4 twrp already on it. I bought it with no o.s
coal686 said:
No problem. I moved this conversation into its own Q&A thread.
I've never had to ADB sideload before. If I remember right, the one time I had that issue, I was able to copy the ROM file over through the custom recovery. So, you'd put TWRP on first, boot into it, and then copy it over that way.
Since you have no OS, you could also run the RUU to completely reset the phone back to stock. Then unlock the bootloader, flash TWRP, copy the new ROM over, and then wipe and flash in TWRP.
I don't think Facepalm still works. If the phone has an older bootloader, one of the older methods might work, but the only s-off method that works on newer bootloaders is called Sunshine.
Click to expand...
Click to collapse
I hear rumrunner and firewater still work...true?
Tmobilefan906 said:
Yea, the phone has 2.6.4 twrp already on it. I bought it with no o.s
Click to expand...
Click to collapse
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
Tmobilefan906 said:
I hear rumrunner and firewater still work...true?
Click to expand...
Click to collapse
@Sloth might have kept up with this better. AFAIK, those Rumrunner will still work if you are on an older firmware, but I'm not sure.
EDIT: Fixed due to Sloth's answer below.
coal686 said:
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
@Sloth might have kept up with this better. AFAIK, those will still work if you are on an older firmware, but I'm not sure.
Click to expand...
Click to collapse
Update what? My twrp? I was thinking flashing 3.8.7 like u suggested. Its been a while since I tinkered with htcs. I've hacked quite a few in my days. Thanks again!!
coal686 said:
You'll definitely want to update that as I've heard older versions can have issues with newer ROMs. Not sure about that particular one.
@Sloth might have kept up with this better. AFAIK, those will still work if you are on an older firmware, but I'm not sure.
Click to expand...
Click to collapse
RumRunner might work if it is still on one of the earlier updates, Firewater has been discontinued, if RR does not work you will have to use SunShine to s-off.
Tmobilefan906 said:
Update what? My twrp? I was thinking flashing 3.8.7 like u suggested. Its been a while since I tinkered with htcs. I've hacked quite a few in my days. Thanks again!!
Click to expand...
Click to collapse
Yeah, TWRP. 2.6.x is pretty old. Since you've hacked a few HTC devices in the past, this device isn't much different except without an SD card, you can't use a specially named zip (like PGxxxx.zip) to flash firmware. It must be done with fastboot.
coal686 said:
Yeah, TWRP. 2.6.x is pretty old. Since you've hacked a few HTC devices in the past, this device isn't much different except without an SD card, you can't use a specially named zip (like PGxxxx.zip) to flash firmware. It must be done with fastboot.
Click to expand...
Click to collapse
Why is recovery m7lw and roms zips are m7spr?
Sloth said:
You can also adb push a rom while in recovery.
1. Download said rom, place it in your adb/fastboot folder.
2. Open a cmd window from said folder.
3. type adb push RomName.zip /sdcard/
It will take a few minutes to complete so be patient.
4. Wipe data/cache/dal cache/system
5. Flash rom.
6. Profit.
Click to expand...
Click to collapse
It says no such directory
Tmobilefan906 said:
It says no such directory
Click to expand...
Click to collapse
I had to put .zip in the cmd prompt. Thanks.
Tmobilefan906 said:
It says no such directory
Click to expand...
Click to collapse
Ugh. Stuck at 5%
Every time I flash recovery, it won't stick. I've tried button combos, multiple flashing recoveries. I need help
I think my bootloader is locked. Ugh
On my bootloader it says m7wls. Where can I find ROMs for that? I need to adb push it..I tried the RR ROM named m7spr, and it won't work. Please help!! Lol
Tmobilefan906 said:
Why is recovery m7lw and roms zips are m7spr?
Click to expand...
Click to collapse
Does ".zip" have to be in ROM name to flash? This is my first sprint HTC. Ugh.