Hi,
I am flashing a factory image using RSD lite i was get error "SP space is not enough " what is that mean ? but finally no problem to my device .
Any help appriciating
Thnks
Mahesh
Mahesh8348 said:
Hi,
I am flashing a factory image using RSD lite i was get error "SP space is not enough " what is that mean ? but finally no problem to my device .
Any help appriciating
Thnks
Mahesh
Click to expand...
Click to collapse
Known error after you use twrp to wipe data. It shouldn't cause any problems..
samwathegreat said:
Known error after you use twrp to wipe data. It shouldn't cause any problems..
Click to expand...
Click to collapse
Can I try "fastboot erase system" before flashing system partition?
I'm afraid though the phone will not boot if flash fails after system erase.
ks73417 said:
Can I try "fastboot erase system" before flashing system partition?
I'm afraid though the phone will not boot if flash fails after system erase.
Click to expand...
Click to collapse
flashing anything should be proceeded by a system wipe anyway. No matter how you wipe it.
There's always risk in this hobby. Luckily, most problems are fixable.
Did you take a Nandroid backup before doing anything? That's always a good habit. Then you can restore if things go wrong.
---------- Post added at 01:24 PM ---------- Previous post was at 01:22 PM ----------
Oh, RSDLite will erase your backups anyway.
Either way, most problems can be fixed. Still need to wipe.
You can flash with Fastboot also.
I have taken a backup in TWRP and have restored that without any problem too. I would just go ahead and try copying the whole SDCARD to my computer just in case.
After that, if I do "fastboot erase system" before flashing stock system.img, do you think that will get rid of this "space is not enough" message?
I know I should not be worried about this, but, my stock camera is messed up and it continues to give me error even after return to stock. I have a feeling that this error message is leaving bad stuff on system partition that's causing this camera error.
Camera used to work find a couple of weeks back and I have not dropped the phone or anything for it to be broken now. Is there a diagnostic app that can tell me if my camera is physically broken? I have tried google camera too, it gives "can't connect to the camera" error.
It's likely an app that has taken the camera hostage, or its hardware. A fresh firmware install will prove which.
And yes, wiping system is important when you have issues like that. So do what you feel good about backing up and flash your firmware.
If you continue to get the Space error, I can't help....never encountered that one. Hopefully that's not hardware too....and related to the camera issue.
Good luck!
Can't erase system partition from fastboot, getting the following error:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
ks73417 said:
Can't erase system partition from fastboot, getting the following error:
erasing 'system'...
(bootloader) Permission denied
FAILED (remote failure)
Click to expand...
Click to collapse
Well, you can try this guide from @KidJoe from step one and see how it goes.
http://mark.cdmaforums.com/MotoX-ReturnToStock.html
Other than that, not sure what else you can try. You have tried RSD Lite also??
And have you ever downgraded?? That could cause any number of issues.
Sorry, but out of ideas myself.
ks73417 said:
Can I try "fastboot erase system" before flashing system partition?
I'm afraid though the phone will not boot if flash fails after system erase.
Click to expand...
Click to collapse
First off, when working with SYSTEM, always use mFastboot. System on Moto phones is bigger than the stock fastboot can deal with.
Next, I've never seen anyone mention ERASING /system before. I've seen some posts by some who accidentally WIPED/Formatted /system from TWRP and had a heck of a time getting back to a working phone.
If you're trying to get rid of an error, its always safest to backup your data to a PC (connect the phone to PC via USB cable and copy the /SDcard contents to the PC's drive). NOTE: this doesn't keep game data, app data, etc. Just pix, video, music, downloads, etc. Then from mfastboot erase USERDATA and CACHE. You then need to re-install all your apps, and copy any data back.
If that doesn't fix the error, try using RSDLite or mFastboot to re-flash the STOCK SBF file for your phone, making sure it again erases userdata and cache. Standard warning: once on 4.4.2 or higher, NEVER DOWNGRADE the ROM on your phone!!! as you have the risks of bricking your phone!!!
Thank you KJ for your detailed response.
Turns out I have a defective phone, Motorola is sending me a replacement. It's very strange, if I pressed around the Camera thingy on the back, Camera will start working, then will go out after some time. I definitely think it's faulty hardware. I bought this Nov 2013 if that matters.
Has anybody else have had this issue with the Camera? everything else is flawless otherwise.
Next question I have is, when I do get my replacement phone tomorrow, what version of Android will it have? Will I be able to use sunshine on it just like I did on my current Moto Maker phone?
Thanks.
ks73417 said:
Thank you KJ for your detailed response.
Turns out I have a defective phone, Motorola is sending me a replacement. It's very strange, if I pressed around the Camera thingy on the back, Camera will start working, then will go out after some time. I definitely think it's faulty hardware. I bought this Nov 2013 if that matters.
Has anybody else have had this issue with the Camera? everything else is flawless otherwise.
Next question I have is, when I do get my replacement phone tomorrow, what version of Android will it have? Will I be able to use sunshine on it just like I did on my current Moto Maker phone?
Thanks.
Click to expand...
Click to collapse
Hopefully it's not 4.4.4. That's the only version I think you may have no luck with Sunshine on. Sunshine needs temporary root... And 4.4.4 can't be rooted this way. But definitely try sunshine anyway.
Hopefully you get a lower version... Or you get your device back.
---------- Post added at 03:48 PM ---------- Previous post was at 03:47 PM ----------
Also... You realize you may have a problem if Motorola realizes your current phone is unlocked? ?
I'm getting the replacement delivered tomorrow and will ship my current one on Thursday. what problem can I have potentially? they have already RMAed the current device for hardware problems, does it really matter to them if the bootloader is unlocked?
The bigger problem for them should be seemingly soft back of the phone that would make camera unusable after a little pressure !
ks73417 said:
I'm getting the replacement delivered tomorrow and will ship my current one on Thursday. what problem can I have potentially? they have already RMAed the current device for hardware problems, does it really matter to them if the bootloader is unlocked?
The bigger problem for them should be seemingly soft back of the phone that would make camera unusable after a little pressure !
Click to expand...
Click to collapse
Many have had no problems with warranty and unlocked devices.... Just technically unlocking bootloader voids the warranty on any X except the Dev Edition. Even if it's hardware related.
Just a heads up. ? cause just cause they are sending you a replacement, doesn't guarantee they don't inspect the device and decide to charge you for the replacement.
Tho when it's a completely obvious hardware issue... I'm sure someone would have to be in a very bad mood that day to do that.
Would be nice for others to hear how it works out for you. ?
I will keep you posted. Is there a way to lock the bootloader once I have used Sunshine to unlock it? I'm guessing there is not else you would have suggested that.
Believe I would have... I just did all that on my M8. But no, on the X you can relock the bootloader, but it's status will be " relocked". It won't return to "locked" status. So probably not worth relocking.
So, my worst fears are realised, the new phone has 4.4.4.
What are my options? Is there anyway to root? All I care about is Moto X tether using XPosed as I have UDP .
You can't root on locked 4.4.4.
Sunshine won't work cause it needs temp root first, which it can't do on 4.4.4.
Your only hope would be the China middleman. But it seems only January to May 2014 models (manufactured dates... See China middleman thread in general about it) can get codes from.
samwathegreat said:
Known error after you use twrp to wipe data. It shouldn't cause any problems..
Click to expand...
Click to collapse
Will it affect taking ota?? I got the same message on bootloader screen but phone booted up fine. I'm a little worried....
Thanks in advance.
Related
So, I imported and gifted this device to my GF and will describe what happened as she did. She was downloading a torrent and suddenly the screen just went black. After holding the power button for awhile, the phone came back on but, would get stuck on the boot logo(welcome message) screen and in a boot loop. I know that it is a SIM unlocked Moto X(XT 1053?)
So far, I've tried getting into the bootloader and am able to. The only problem is when I get to the recovery, I don't see the little dead Android dude. The phone ends up dying. Now I have it charging and I'm on the bootloader screen, but I still can't get into recovery. I just get a blank screen when I try.
It will be hard, time consuming and maybe a little expensive RMAing the device, as I'd probably have to send it back to the US for the warranty.
I'm thinking maybe I just try and unlock the bootloader and see if the subsequent factory reset helps. But I don't know if this will work.
I have tried fastboot erase cache but it didn't help.
I think somehow my recovery is gone. I've tried flashing a recovery.img but it errors out. (failed to hab check for recovery)
Any ideas?
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
KidJoe said:
Did you root the XT1053 before you sent it to her? If so, how?
Next, do you know what ROM was on there before it got stuck in this state? the failed hab check when flashing recovery makes me question if there is a missmatch somewhere... i.e. attempt to down grade from 4.4.3 or 4.4.2 to lower... or the stock recovery you are trying to flash doesn't match the rom version on the phone.
Click to expand...
Click to collapse
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
deejaylobo said:
No, it was not rooted, completely stock and the bootloader was locked. Something just got borked I guess. It was on 4.4.3. It was like there was no recovery and I attempted to access it a bunch of time.
So, my solution was to just void my warranty and unlock the bootloader. This worked. But, on reboot it went to the dead Android logo, and I could suddenly access recovery again(WTF?!). I did a factory reset and now it seems to be working fine!
Now, for the fun bit. I'm going to use your guide to make my face her boot logo! :cyclops:
Click to expand...
Click to collapse
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
KidJoe said:
Funny. I've read of another having a similar issue... locked, not-rooted, and had the phone just "brick." Warranty replacement was needed. So keep an eye on that.
Since you factory reset already, you could consider re-flashing the firmware to the phone, just in case.. To be safe, make sure you are flashing the EXACT same rom, do not attempt to downgrade. I would consider using mFastboot rather than RSDLite... and follow option 5 at -> http://mark.cdmaforums.com/MotoX-ReturnToStock.html (and yes, there are a couple of lines repeated in that sequence, its intentional).
As for using your face for her bootlogo.. hmm... you sure she is ok with that? then again, the X doesn't need to be rebooted often, so she wont see it
Click to expand...
Click to collapse
I only found one person with a similar issue, and you're right, he did end up getting a replacement. That's just not an option for me. It's too much of a pain sending it back to the US.
Yeah, I think I will reflash a ROM. Can you point me towards figuring out which is the correct ROM? My System Version is 212.44.21.ghost_row.Retail.en.US. So, I just grab the corresponding SBF, yeah? I flashed the logo with mfastboot, so I'm okay with that. EDIT: No worries. Foudn the right file. Sorted. Everything seems to be working fine. Thanks!
The face thing, is just to prank her. I previously had a custom message set up for her through the Moto Maker. I think she'll be rebooting her phone more often now.
So I recently bought a moto x developer edition off of craigslist and I was updating my phone to kitkat, when I tried to install it took me to the Team Win Recovery Project page. I did not realize someone had already tried to root the phone. Anyway, I accidentally wiped the system rather than factory resetting the phone and now my phone is stuck on the "warning bootloader unlocked page". Just wondering If there is a way to go back to the stock OS. I should mention that know the bare minimum when it comes to this so any help is really appreciated. I really only bought the phone out of necessity!
Use this guide, look for returning to stock section. You can only flash the same or higher Android version that was on it before. Downgrading can end up in a brick.
http://forum.xda-developers.com/showthread.php?t=2603358
yayayesi said:
So I recently bought a moto x developer edition off of craigslist and I was updating my phone to kitkat, when I tried to install it took me to the Team Win Recovery Project page. I did not realize someone had already tried to root the phone. Anyway, I accidentally wiped the system rather than factory resetting the phone and now my phone is stuck on the "warning bootloader unlocked page". Just wondering If there is a way to go back to the stock OS. I should mention that know the bare minimum when it comes to this so any help is really appreciated. I really only bought the phone out of necessity!
Click to expand...
Click to collapse
Come on Vzw users! A twrp system.img! There could be one posted somewhere. BTW any rooted phone even w/o an unlocked boot can generate one using Online Backup in play!
http://forum.xda-developers.com/moto...ready-t2762382
aviwdoowks said:
Come on Vzw users! A twrp system.img! There could be one posted somewhere. BTW any rooted phone even w/o an unlocked boot can generate one using Online Backup in play!
http://forum.xda-developers.com/moto...ready-t2762382
Click to expand...
Click to collapse
Well..I'd like to help out, I too own a XT1060..but have not updated, (purposely) to KK..still on Jelly Bean..
sorry I can't help..
Sent from my 4.4.4_21.11.56_peregrine
(Unlocked) XT1045 Moto G 4G LTE #1
http://waynekent.com/page6.html
"Praise Jah" YOU people.!
KJ said:
Use this guide, look for returning to stock section. You can only flash the same or higher Android version that was on it before. Downgrading can end up in a brick.
http://forum.xda-developers.com/showthread.php?t=2603358
Click to expand...
Click to collapse
Hopefully this is my last question! I seem to finally have everything downloaded and in the right folder. I even reinstalled the drivers. I'm currently on the cmd prompt and input the first line.
and received a "<bootloader> Variable not supported" message, sending 'partition' okay but writing 'partition' failed <remote failure> I currently have the device on the "AP Fastboot Flashmode" (S) screen.
Not really sure whats wrong at this point
Does "fastboot devices" return your serial number?
If all you wiped was system, perhaps try just flashing the system.img with mfastboot.
You definitely have the same firmware you were on? Or was it a custom ROM?
Thing is, we have no idea what was previously done to the phone.
You may be better served using rsdlite for a fresh start.
yayayesi said:
Hopefully this is my last question! I seem to finally have everything downloaded and in the right folder. I even reinstalled the drivers. I'm currently on the cmd prompt and input the first line.
and received a "<bootloader> Variable not supported" message, sending 'partition' okay but writing 'partition' failed <remote failure> I currently have the device on the "AP Fastboot Flashmode" (S) screen.
Not really sure whats wrong at this point
Click to expand...
Click to collapse
Is that the getvar? Do not flash it.
You are better off just editing it out of the XML & use RSD-Lite
KJ said:
Does "fastboot devices" return your serial number?
If all you wiped was system, perhaps try just flashing the system.img with mfastboot.
You definitely have the same firmware you were on? Or was it a custom ROM?
Thing is, we have no idea what was previously done to the phone.
You may be better served using rsdlite for a fresh start.
Click to expand...
Click to collapse
Yes it does return a serial number. T0620060PD
I don't think it was custom I think it was just 4.2 and when I tried to do a system update to 4.4, that's when I wiped the system.
So I could flash rsdlite instead of 4.4? Is there a link for that?
aviwdoowks said:
Is that the getvar? Do not flash it.
You are better off just editing it out of the XML & use RSD-Lite
Click to expand...
Click to collapse
yes I believe so. Thats the reading I get on the device anyway.
It seems both of you recommend rsdlite. Either you know of a guide page with instructions on how to do that?
This is my first time messing with anything this in depth.
Thanks!!
yayayesi said:
yes I believe so. Thats the reading I get on the device anyway.
It seems both of you recommend rsdlite. Either you know of a guide page with instructions on how to do that?
This is my first time messing with anything this in depth.
Thanks!!
Click to expand...
Click to collapse
found this link, do you think it could work?
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
yayayesi said:
found this link, do you think it could work?
http://forum.xda-developers.com/moto-x/general/guide-moto-x-return-to-100-stock-using-t2446515
Click to expand...
Click to collapse
Yup
KJ said:
Yup
Click to expand...
Click to collapse
Failed flashing process. 2/1i7 flash partition "gpt.bin"
The device says:
downgraded security version.
update gpt_main version failed.
preflash validation failed for GPT
....do I just have the wrong firmware downloaded or is this thing already bricked
Ive got it! Thank you so much for all the help it was much appreciated! I don't feel like quite the noob now seeing as the phone still lives, but I definitely won't be trying that again any time soon! haha.
Oh, and for reference it seemed that all I needed to do was 4.4.4 rather than just 4.4.
Thanks again!
Hi all, total newb here. (Sorry I know you probably hate these kinds of threads).
I apologize in advanced if this is a very simple case / has been discussed in the forums.
I've literally read everything I can in regards to this topic but being such a total newbie at this, I'm still not 100% sure if I got this right.
So basically my phone is XT1095 - which I didn't root or unlock boatlader (simply because I don't know why), that suddenly got into a boot loop.
So on that AP Fastboot screen.
So all options (including normal powerup, recovery and factory reset) produces
'failed to validate system image.
boot up failed'.
What should I do at this point? I've read on jcase's thread that this is a simple matter of "easily fixed by flashing proper boot.img".
Where can I find the "stock boot.img"?
I know graffixnyc has KXE21.187-42 files on his website which can be flashed. Is it pre-rooted though?
Or can I just easily use bhp090808's Multi Tool to fix this?
Can it be used while the phone is still in this bricked / bootlooped condition?
Honestly I dont mind being rooted if it means getting my phone fix. But if I can get it done without rooting it then it would be 'great' since if I fail in any way I won't void my warranty.
Sorry for asking a lot of things. As you can notice, I'm totally new at this. I've successfully rooted and install a custom ROM once in my old S3 but it was only because there was a thorough step to step process.
Again, thanks in advance and I really appreciate anyone's help
Cheers.
anyone?
koflok1234 said:
anyone?
Click to expand...
Click to collapse
I wouldn't unlock or root!!! You could lose your warranty. You can try a factory reset, else return your phone for warranty
godutch said:
I wouldn't unlock or root!!! You could lose your warranty. You can try a factory reset, else return your phone for warranty
Click to expand...
Click to collapse
Not a response I expect would found from XDA
I tried factory reset but it's stuck on that screen. Fail to validate image. I think the recovery.img is corrupted?
koflok1234 said:
Not a response I expect would found from XDA
I tried factory reset but it's stuck on that screen. Fail to validate image. I think the recovery.img is corrupted?
Click to expand...
Click to collapse
I doesn't make sense to void warranty to try to fix a problem that is covered under warranty. Maybe your emmc is defective or something like that, don't make matters worse.... You unlock your device when you have verified that everything is working, not when things start failing
I am under warranty but I am currently overseas so sending the phone and process the return is a bit of a hassle. So 'other' options is to do a local repair outside warranty here but that costs a bit.
So if I can fix it myself with a simple procedure then it might be the best way.
I'm having the same issue as well if anyone has figured out how to fix this I would be extremely grateful. I am still under warranty, but I'm nervous they will send me a replacement in worse shape than my current device.
My pure edition was stuck at the splash screen and I didn't previously unlock my bootloader. I also didn't have USB debugging checked so I couldn't find my phone using ADB. Unlocking a pure edition bootloader DOES NOT VOID warranty!!! So I unlocked my bootloader and flashed the factory files and restored the use of my phone. I then updated to lollipop, rooted my phone and checked USB debugging. That way I have full control of my phone and can fix it myself if something comes up. There is the thread saying the warranty won't be void after unlock.
https://forums.motorola.com/posts/677736c888?page=2
The problem now is that it is impossible to root or do anything else with me phone that doesn't involve fastboot
sianaka said:
The problem now is that it is impossible to root or do anything else with me phone that doesn't involve fastboot
Click to expand...
Click to collapse
same here. anybody solved the issue? can we recover through fastboot? anything we can try?
this happend after trying to root the device (step 7 in multi-too to be specific
You should be able to recover via fastboot if you have the factory image, there are some floating around here.
If it's an official one you don't even need to unlock your phone because the image is signed by Moto.
Here is a link to an official guide on how to flash.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/recovery-images
pwvandeursen said:
same here. anybody solved the issue? can we recover through fastboot? anything we can try?
this happend after trying to root the device (step 7 in multi-too to be specific
Click to expand...
Click to collapse
solved.
used fastboot to flash the files from multi-tool (recovery, system boot) booted back up, only pushed root (not TWRP), an d now fully functional again
pwvandeursen said:
solved.
used fastboot to flash the files from multi-tool (recovery, system boot) booted back up, only pushed root (not TWRP), an d now fully functional again
Click to expand...
Click to collapse
Can you possibly explain this step by step? Sorry I'm kind of new to this.
Also, will I be able to do this if my battery is low?
koflok1234 said:
Hi all, total newb here. (Sorry I know you probably hate these kinds of threads).
I apologize in advanced if this is a very simple case / has been discussed in the forums.
I've literally read everything I can in regards to this topic but being such a total newbie at this, I'm still not 100% sure if I got this right.
So basically my phone is XT1095 - which I didn't root or unlock boatlader (simply because I don't know why), that suddenly got into a boot loop.
So on that AP Fastboot screen.
So all options (including normal powerup, recovery and factory reset) produces
'failed to validate system image.
boot up failed'.
What should I do at this point? I've read on jcase's thread that this is a simple matter of "easily fixed by flashing proper boot.img".
Where can I find the "stock boot.img"?
I know graffixnyc has KXE21.187-42 files on his website which can be flashed. Is it pre-rooted though?
Or can I just easily use bhp090808's Multi Tool to fix this?
Can it be used while the phone is still in this bricked / bootlooped condition?
Honestly I dont mind being rooted if it means getting my phone fix. But if I can get it done without rooting it then it would be 'great' since if I fail in any way I won't void my warranty.
Sorry for asking a lot of things. As you can notice, I'm totally new at this. I've successfully rooted and install a custom ROM once in my old S3 but it was only because there was a thorough step to step process.
Again, thanks in advance and I really appreciate anyone's help
Cheers.
Click to expand...
Click to collapse
Well i booted his file, now my device is in a bootloop. i requested the original img file from the motorola site. Search it up in google. I will try it right now. Hope it works!!!
Hello guys! So I bought a 64gb version of Nexus 6 just before new years eve and it started having issues in february. It got fully replaced by the service company for a new one. Yesterday my phone started complaining that I have insufficient storage. I checked how much memory I had and it said "32gb". So I'm using now a 32gb instead of a 64gb version which I was supposed to get from warranty. Nobody told me about the switch and the store where I bought it from said there has happened a mistake.
The thing that makes this tricky is that I've dropped the phone and the top layer of the screen is cracked. The screen itself works 100%, no color issues or issue tracking finger. It's just the top layer of protective glass that's bricked http://i.imgur.com/g6Se9dd.jpg They should contact on moday to me about this but what are really my options? If there never would had been a failure from their side, I would be living hapily with a 64gb bricked screen nexus 6 and have no issues. Do you think there are going to be more expenses for me due to their mistake?
Checked all papers over the issue. In the document over the repair, it states that they give me a new 64gb model of the phone.
One thing I started wondering about this morning. As me and my friend rooted my N6, we installed his stock image on it due to mine bugging out. He has a 32gb of N6. Could this affect it also? Both android system and disc checker app says I have left 23.03gb, aka. 32gb model.
FiresStream said:
Hello guys! So I bought a 64gb version of Nexus 6 just before new years eve and it started having issues in february. It got fully replaced by the service company for a new one. Yesterday my phone started complaining that I have insufficient storage. I checked how much memory I had and it said "32gb". So I'm using now a 32gb instead of a 64gb version which I was supposed to get from warranty. Nobody told me about the switch and the store where I bought it from said there has happened a mistake.
The thing that makes this tricky is that I've dropped the phone and the top layer of the screen is cracked. The screen itself works 100%, no color issues or issue tracking finger. It's just the top layer of protective glass that's bricked http://i.imgur.com/g6Se9dd.jpg They should contact on moday to me about this but what are really my options? If there never would had been a failure from their side, I would be living hapily with a 64gb bricked screen nexus 6 and have no issues. Do you think there are going to be more expenses for me due to their mistake?
Checked all papers over the issue. In the document over the repair, it states that they give me a new 64gb model of the phone.
One thing I started wondering about this morning. As me and my friend rooted my N6, we installed his stock image on it due to mine bugging out. He has a 32gb of N6. Could this affect it also? Both android system and disc checker app says I have left 23.03gb, aka. 32gb model.
Click to expand...
Click to collapse
Fastboot flashing the factory image will do this. To get your full 64gb of memory back, from bootloader do >
fastboot format userdata
NOTE: this will wipe the contents of your SDcard, so back it up on your PC first.
Yeah to echo the above, its quite common on the nexus to accidentally appear you have the smaller version after a flash...reflashing stock should fix it.
Doesn't it say which version you have in the bootloader?
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
FiresStream said:
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
Click to expand...
Click to collapse
No, there's no such thing as a wrong stock image. They're not storage-exclusive. Just a bad flash, it happens sometimes.
FiresStream said:
Apparently emmc 64gb. Darn... Musta have flashed wrong stock image...
Click to expand...
Click to collapse
No, you didn't. This happens with the 64gb versions. Factory reset after flashing factory image usually prevents it.
So I guess, nandroid backup and then reinstall. The backup should get everything back so I don't need to spend 4 hours to set up my phone accounts/settings etc?
FiresStream said:
So I guess, nandroid backup and then reinstall. The backup should get everything back so I don't need to spend 4 hours to set up my phone accounts/settings etc?
Click to expand...
Click to collapse
Not sure. Try it and see. Be sure to save it to your PC, as "fastboot format userdata" will wipe your SDcard.
****...
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
FiresStream said:
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
Click to expand...
Click to collapse
the toolkit is where you made the mistake. you have to flash the factory image via fastboot while you are hooked up to a computer while you're in the bootloader. if you have no idea what you are doing, toolkits wont help you out. read how to do it right, thete are a few threads here explaining for you, in detail.
---------- Post added at 05:09 PM ---------- Previous post was at 05:02 PM ----------
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
FiresStream said:
Tried to reinstall the phone but I'm now stuck in a situation where I can only access Fastboot and Recovery. Tried several times Nexus RootKit Stock flash but it doesn't seem to help either. Also wiped system/cache etc. for bad files. I really feel like this is a brick now...
Devicde is LOCKED. Status Code: 2
Any ideas how to proceed?
Click to expand...
Click to collapse
What happens when you try to reboot to Android? Your bootloader is locked so there isn't much you can do if you can't boot Android.
Do you have stock recovery or TWRP?
Tried quite a few options already in the Nexus Root Toolkit but without any results...
Anything specific I should give a try to hopefully let me sleep this night in peace?
Bootloop, just nothing... It just displays "Google" logo and does nothing further.
FiresStream said:
Bootloop, just nothing... It just displays "Google" logo and does nothing further.
Click to expand...
Click to collapse
try this via fastboot, and see if itll boot up. you have to be in the bootloader to use fastboot..
fastboot format cache
fastboot format userdata
then try booting up and enabling oem unlock.
simms22 said:
try this via fastboot, and see if itll boot up. you have to be in the bootloader to use fastboot..
fastboot format cache
fastboot format userdata
then try booting up and enabling oem unlock.
Click to expand...
Click to collapse
Got android studio installed from some time ago, just need to find out how to push the commands from cmd...
FiresStream said:
Got android studio installed from some time ago, just need to find out how to push the commands from cmd...
Click to expand...
Click to collapse
and hows android studio gonna help? you arent building an app.. you need to use fastboot.
simms22 said:
and hows android studio gonna help? you arent building an app.. you need to use fastboot.
Click to expand...
Click to collapse
Gotta say I'm hopeless in my situation... Got fastboot and abd drivers installed now, now I just need to find out how to use them...
FiresStream said:
Gotta say I'm hopeless in my situation... Got fastboot and abd drivers installed now, now I just need to find out how to use them...
Click to expand...
Click to collapse
thats ok, i was useless with fastboot at one time as well. at the very beginning, is when its the hardest, just because you are clueless. once you do it one time, its much easier every time after.
simms22 said:
thats ok, i was useless with fastboot at one time as well. at the very beginning, is when its the hardest, just because you are clueless. once you fo it one time, its much easier every time after.
Click to expand...
Click to collapse
Got the commands done which you suggested, how should I proceed?
FiresStream said:
Got the commands done which you suggested, how should I proceed?
Click to expand...
Click to collapse
try booting up. if you boot up, enable developer options, then go into them and enable oem unlocking. then you can unlock the bootloader and flash a factory image.
btw, i found this thread about using fastboot. its an older thread but.. http://forum.xda-developers.com/showthread.php?t=2277112
So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin
kickenwing13 said:
So here's the deal. I use WUGS and don't manually do stuff.. Yes this makes me a weak individual and I bow to the people who can manually flash and their omniscient power. I bought a 64gb google version Nexus 6 about a month ago when the price dropped. I had issues with it just shutting off every once in a while, but tried rooting and romming and no matter what the rom was, about a day in it would just force shutdown... In the early days I could access TWRP and even if I restored to a stock back up, only one time did it just restore and boot up, the rest of the time it would just not boot up..... I called about an RMA and put it back to complete stock, unlocked, trying to get it working, just thought maybe it was something I did and if so, I wanted to try stock. I flashed it, a few times I even made it to the set up screen on the initial boot, but after failing it didn't matter if I navigated to stock recovery and wiped or anything. Only thing I can do is access stock recovery and bootloader and all that and try to power it on but it just says google for a few seconds then shuts down. . Last night I got worried and relocked the bootloader so I could send it back and not have Moto void me on that... Was this always just a faulty phone or is it more likely something i did? I appreciate any intelligent thougts.
Dustin
Click to expand...
Click to collapse
There is honestly no way to tell. We would be guessing. You cannot unlock the bootloader now either, so we can't even get you to manually flash stock to test.
You can try a "fastboot format userdata" and "fastboot format cache" to see if that helps you boot, otherwise, nothing you can do.
We do recommend that you only use toolkits if you know what they are doing in the background. It really isn't difficult. In fact, I wrote a very simple thread to explain in in General > Sticky roll-up. None of this has anything to do with omniscience. Though, that particular skill would be helpful to us to answer your actual question.
Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..
kickenwing13 said:
Lol thanks dude. I'll try anything. I figured out how to run simple commands, but when it comes to putting the files in the correct directory I think so that it reads it... But, you're saying now that I'm locked, stock, and not loading up, I could try to do fastboot and format data and cache? Is this a more in depth wipe than just wiping in stock recovery does ? I assume now that I locked, I can't flash firmwares without voiding my warranty or? I was actually on chroma and it shutdown, so I went to stock, started typing gmail log in on initial set up and it shut down.. .So as far as I know. I'm stock... and locked..
Click to expand...
Click to collapse
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still
danarama said:
Format is not a wipe. It will wipe, but unlike a wipe, it will recreate the file system. A corrupt file system can prevent boot so worth trying.
If the BL is locked and won't unlock, that's about all you can try.
Boot.to recovery just incase you have TWRP recovery still
Click to expand...
Click to collapse
tried and the process failed... I have it back to status 2 and not rooted and it died after flashing stock so I assume sending it back is okay.. my replacement is here today. I'm unlocking and rooting as we speak
I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.
openbook said:
I erased everything on my Nexus 6 and then tried using the flash-all.bat from image-shamu-lmy48i.zip.
It failed saying could not allocate so many bytes.
Accidentally i did lock my bootloader using fastboot oem lock.
Now cant load anything and my phone doesn't boot.
When i try fastboot oem unlock it says enable that option under developer options.
I am now with a brick Nexus 6 please help me out of this situation.
Click to expand...
Click to collapse
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.
Evolution_Tech said:
No matter how many times this question is asked, unfortunately, the answer is still, there is no fix.
This has been happening since the nexus 6 went to 5.1 and has been documented numerous times. A bit of reading beforehand is all that is needed to avoid this situation.
RMA is the only option.
Click to expand...
Click to collapse
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?
openbook said:
I did unlock before and rooted the phone and i was using it.
Does it mean my warranty is also void and no more support?
Is any devs working on fixing this problem?
Click to expand...
Click to collapse
It's a security feature since 5.1. You cannot.unlock the bootloader without first setting "enable oem unlock". If you unlocked before 5.1, then you most likely didn't do this as it wasn't needed. So now you're locked and there is no way to unlock it.
Some devs may be looking into it, but if they are, they have been looking into it for a long time. It's extremely unlikely there will be a solution for this that doesn't come from Motorola. It could be an easy fix if Moto Wanted. They could provide a stock recovery flash able fully signed, rom.zip. This wouldn't bypass security either because you would still need your unlock code / google password to boot the device. But so far, we've heard nothing
Send it in to them. If you haven't got TWRP installed, there is nothing you can do. There's no reason for them to void warranty