Related
Hi all,
prior to any comment, yes, i know there are already posts on this issue, however looking through them didn't help at all unfortunately.
I have a Moto Milestone, origin is Israel.
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
Tried already to reflash the phone without luck using RSD Lite (downloaded the SBF through http://and-developers.com/sbf:milestone - the 'official' Cellcom IL SBF that was there...)
anyway - i can still access the bootloader which tells me the phone is not fully bricked, however i can't seem to find any proper SBF so it'll reflash itself back to an operative state.
One major problem here - the phone won't get into recovery mode (i've tried all the combinations i know and that have worked before)
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
one last resort i've tried - trying to split the SBF and reconstructing it - still no joy.
does anyone here have any advice or solution o this issue? what kind of SBF do i need? how to manually reconstruct the SBF with proper files? etc.
Thanks in advance,
Tomer
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Caz666 said:
Have you tried loooking into fastboot?
Sometimes a phone wont respond to to adb commands and the recovery is corrupted, but you can still flash partitions using fastboot. I "saved" a Moto dext in this fashion once. Cant remember the exact commands, but it was similar to the adb flash commands. I reflashed the recovery partition and then used recovery to flash a ROM in update.zip format. For some reason RSD lite was failing on this phone.
Just something you may want to look into if you are desperate about saving your MS.
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
vladstercr said:
are you sure your drivers for the phone are installed properly? what RSD lite version are you using? What system? windows 32 or 64 bits?
Click to expand...
Click to collapse
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
barvaz_t said:
I'm quite sure they're installed properly as i managed to upgrade my bootloader version using the RSDlite.
my system is 32 bits and the drivers are the ones i installed throught the Motorola website. I've first used RSDlite 4.6 but after reading a bit I understood there are some differences between versions hence upgraded to 4.9.
Click to expand...
Click to collapse
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
vladstercr said:
Try the 90.78ch bootloader from http://and-developers.com/sbf:milestone ...
"XT702 variant of the 90.78 bootloader (notes from 90.78 apply here too).
It's reported to work on the A853 too. "
You've got nothing to loose on trying this. Let me know!
Click to expand...
Click to collapse
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Already tried the website, the mirror there is no leading to the bootloader itself but to a wiki site.
i've tried searching almost anywhere i know, but this bootloader is non available to download.
if there's another mirror site such as rapidshare or megaupload - i'd be happy to be pointed towards it..
Hi barvaz_t!
barvaz_t said:
...
somewhere along the way i've updated the bootloader to 90.78 and since then - the phone is stuck in the notorious loop and cannot restart the OS.
...
Click to expand...
Click to collapse
Why did you upgrade the bootloader
barvaz_t said:
...
i've also read about wiping the cache and user data however - as far as i know, this can only be done by entering the recovery mode, right?
...
Click to expand...
Click to collapse
Right, is it possible to boot into recovery on your device by holding 'X' button?
barvaz_t said:
*** [update]
I'm now on 90.78ch and see no difference whatsoever.
I've now started investigating how to re-compile an older SBF file so it'll contain the new RAMDL
(I want to flash the Brazilian version however it contains only 90.74 RAMDL)
I've compiled a new file, however the checksum is incorrect.
How it is possible to recompile this properly?
Click to expand...
Click to collapse
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
scholbert said:
Hi barvaz_t!
Why did you upgrade the bootloader
Right, is it possible to boot into recovery on your device by holding 'X' button?
You locked yourself out by upgrading the bootloader to the latest one.
Neither downgrade of bootloader would be possible, nor flashing older firmware SBF's.
Apart from that the milestone uses signature check on certain parts of the firmware. I really doubt that it's possible to tweak/recompile a complete SBF.
Something worth to try, is to flash vulnerable recovery SBF from within bootloader mode using RSDlite.
Here's the link to gitorious: http://gitorious.org/droid/openrecovery/blobs/master/zips/SHOLS/vulnerable_recovery.sbf
If the link does not work for you, there are also some mirrors of this file floating around. Just search!
I guess this should work, because the recovery SBF is using RAMLDR 90.78 (do know about the sign check during flash, but i guess checksum should be O.K.).
With vulnerable recovery properly installed, you might then use OpenRecovery to check your system and restore to some working state.
Good luck!
scholbert
Click to expand...
Click to collapse
Thanks Scholbert for the detailed answer.
the link you gave directs to an image the RSDlite cannot flash (=error validating image).
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
Well, thanks again for trying to help, I think I'm officially out of suggestions or options here unless anyone can give further advice...
barvaz_t said:
...
If your interntion was that I'm supposed to flash the vulnerable recovery only, than bad news - It's already 'installed' on my device (and it shows no error whatsoever during this installation..)
...
Click to expand...
Click to collapse
So can you still enter recovery?
Regards,
scholbert
No, never did (since the upgrade)
If I had access to the recovery i would have at least managed to install OpenRecovery or something and manage to reflash the device
barvaz_t said:
Hi Caz666,
well, thought this might actually work, but had no luck.
when i try to flash my phone it does nothing other than showing me 'downloading boot.img' and thats it.
is there anything else to do in order to save my phone? i really like it
I'm also willing to donate through PayPal to anyone who can describe any working method or that can point me to any valid working process...
thanks again.
Click to expand...
Click to collapse
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Caz666 said:
Did you try to fastboot flash only the boot.img? What about recovery? I seem to remember flashing a recovery.img on the dext...but this was last year. I may be wrong but i believe i flashed only a recovery image and then was able to access the recovery (which would allow all sorts of additional goodies).
I find it strange that fastboot reports only downloading. I seem to remember some error messages and timeouts?
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
Nope.
trying to flash the recovery / boot images only results in the message 'downloading...' and nothing (waited for like 3 hours..)
when I terminate the action by Ctrl+C and then trying again - the message is instantly 'FAILED..' along with specification that the action of sending the command has failed.
I'm literaly out of ideas, don't know what to do..
Sent from my Milestone using XDA App
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Caz666 said:
I am starting to think that there is something wrong with your device (like broken hardware).
In all my experimenting with rsd/fastboot, i did not once get a "hang". I would get checksum/signature errors, size errors, etc...but i always got some type of error code or status.
This is on 3 different Mot devices that run Android.
Sorry
Sent from my Milestone using XDA App
Click to expand...
Click to collapse
The device was working fine before upgrading the bootloader, so it seems that this is not a hardware issue.
Either way - guess i'll be taking it to a lab and let them figure this out..
idea
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
streetracer89101 said:
is the milestone n droid from usa same sbf file used if so i have the right sbf file i found i had couple times i had to reinstall to stock if u want to try it i can email it it work for me saved me from bricks its rooted phone just fyi
Click to expand...
Click to collapse
@streetracer89101 - no, as far as i know Droid and Milestone use different firmware so it won't help unfortunately. Not that it would matter if I did flash my device - it's not like I can use it anyway..
Thanks again for trying to help out
Tomer
90.78ch bootloader
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
300zxtt said:
Hello, I really need the bootloader 90.78ch maybe you can me it someone give Many Thanks
Click to expand...
Click to collapse
Attached. Enjoy
"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!!
Just want to know if anyone else's phone read "Modified" after using Mofoverify. I haven't even used Mofo on my phone yet because I don't have $20 right now and I don't get paid til next Wednesday. I just found it a little odd that it says this after using Mofoverify is all. (See picture below)
GreaterLesser said:
Just want to know if anyone else's phone read "Modified" after using Mofoverify. I haven't even used Mofo on my phone yet because I don't have $20 right now and I don't get paid til next Wednesday. I just found it a little old that it says this after using Mofoverify is all. (See picture below)
Click to expand...
Click to collapse
mine does. i was thinking of flashing the RJ stock image to see if it changes it back to unmodified
Official for me
GreaterLesser said:
Just want to know if anyone else's phone read "Modified" after using Mofoverify. I haven't even used Mofo on my phone yet because I don't have $20 right now and I don't get paid til next Wednesday. I just found it a little old that it says this after using Mofoverify is all. (See picture below)
Click to expand...
Click to collapse
Hmm, I ran Mofoverify but not Mofo, just like you, and my status didn't change. That's curious for sure.
johnbravado said:
mine does. i was thinking of flashing the RJ stock image to see if it changes it back to unmodified
Click to expand...
Click to collapse
Okay I just wanted to make sure my phone isn't messed up or anything. My nexus 6 still hasn't arrived yet.
cenobite138 said:
Hmm, I ran Mofoverify but not Mofo, just like you, and my status didn't change. That's curious for sure.
Click to expand...
Click to collapse
And now I'm worried again.
johnbravado said:
mine does. i was thinking of flashing the RJ stock image to see if it changes it back to unmodified
Click to expand...
Click to collapse
If you flash it back to stock reboot a couple of times, reboot fastboot a couple of times and let us know if it changed back.
Nope stays: Modified.
Harry44 said:
If you flash it back to stock reboot a couple of times, reboot fastboot a couple of times and let us know if it changed back.
Nope stays: Modified.
Click to expand...
Click to collapse
Did you flash all partitions or just a specific partition?
GreaterLesser said:
Did you flash all partitions or just a specific partition?
Click to expand...
Click to collapse
In system status is says official in bootloader software status is custom
All:
boot
bootloader
gpt.bin
logo.bin
radio
recovery
all the system images.
:crying:
I downgraded to the stock release firmware. Im wondering if O update via the OTA to latest if it will change.
Finally got it back but recovery says qe 0/1
Mine does not say modified after running mofoverify. Nor did it matter whether I entered the bootloader from button-press or adb.
Harry44 said:
In system status is says official in bootloader software status is custom
All:
boot
bootloader
gpt.bin
logo.bin
radio
recovery
all the system images.
:crying:
I downgraded to the stock release firmware. Im wondering if O update via the OTA to latest if it will change.
Finally got it back but recovery says qe 0/1
Click to expand...
Click to collapse
I was worried about that...
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.
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.