Database Develop

Are we really 100% Unlocked?????

I know this may not be the thread for this but I can't post in the development thread yet so I'm hoping to get some help here. I am rooted and "unlocked" or so my phone says I am in the fastboot screen but I can't for the life of me wipe the system or the recovery partition no matter what fastboot tool I use or command combination. I downloaded the fastboot tool from matt and type " fastboot erase system" gives me permission denied!! I type "fastboot erase system -w" same thing permission denied!! tried "fastboot -w erase system" permission denied and I am running terminal as administrator and get same results. I even tried moving fastboot and adb root and the associated dl's to the system32 directory and get same results.I even tried the "mfastboot tool" I downloaded not long ago that is supposed to be for the HD's, same result... I tried using linux... same thing permission denied!! and with adb I typed " adb root" and I get "adb cannot run as root in production builds" But the strange thing is I was able to install custom recovery through fastboot. It will let me write to the recovery and sytem partition but won't let me erase!! Very frustrating! I was so excited when we got unlocked but now I am feeling that I am not all the way unlocked.
I read a few post of different people having the same issue, why do some have full unlock and some don't? I unlocked using windows 7, updated drivers, rooted and I got no errors when unlocking... Please help!! could it be that Motorola has already began to patch the exploit????

It's fully unlocked. Your doing something wrong.

It is fully unlocked.
Sent from my YP-G70 using xda app-developers app

The bootloader still restricts some commands. Nothing to do with it being "unlocked" though, which it is.

mattlgroff said:
The bootloader still restricts some commands. Nothing to do with it being "unlocked" though, which it is.
Click to expand...
Click to collapse
same tought here.....
why we can not erase recovery img????/

Can you tell me what I'm doing wrong? I was pretty thorough of the steps I took. I hope your right because then I know it can be done. Are you able to erase partitions? If so what steps did you take?
Sent from my MB886 using xda app-developers app

Thanks Matt! Really enjoy your work! Are you able to erase partitions? I know with my Atrix I can erase anything I want. Run adb root. Complete freedom! Why don't we have that with this phone if its unlocked. To me its still not much different from we had already. Will we be able to flash custom system.img's?? Only thing about if we can, will flashing another IMG on top of another without wiping affect stability? Excuse me for all the questions but I'm fairly new to this and just trying to learn.
Sent from my MB886 using xda app-developers app

jkm43 said:
Thanks Matt! Really enjoy your work! Are you able to erase partitions? I know with my Atrix I can erase anything I want. Run adb root. Complete freedom! Why don't we have that with this phone if its unlocked. To me its still not much different from we had already. Will we be able to flash custom system.img's?? Only thing about if we can, will flashing another IMG on top of another without wiping affect stability? Excuse me for all the questions but I'm fairly new to this and just trying to learn.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Its annoying, but you can boot into CWM and wipe /system over adb then reboot into fastboot and flash a system image.
Basic steps here
That said, I've flashed 4 or 5 system images without wiping and haven't ran into any problems because of it. Your results may vary.

You don't have to erase the old partitions in my experience with Moto... Just flash the new one.
Sent from my Galaxy Nexus using Tapatalk 2

I'm having some trouble with this too... I can't seem to flash anything in recovery. I can wipe fine, though. I haven't tried adb. Is there any way that the unlock process could go wrong but still show "unlocked" in fastboot?

I got denial messages whenever fastboot erase any partition but I have no problem installing CWM or flash back and forth between ICS and JB so I just ignore the messages for now
Sent from my XT925 using Tapatalk

I'm thinking its something to do with cwm or ROMs not being made for cwm to flash I can only flash cm10 it seems like everything else just boot loops
Sent from my XT925 using xda app-developers app

[RESOLVED] Bricked m7ul

Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!

mymonkeyballs said:
Hello guys, I really messed up my phone.
I was trying to relock, and unroot my phone but it didnt go as planned.
Long story short, I cannot flash ANYTHING through CWM or TWRP (latest versions) and none of my files shows up in either of these recoveries. When i push a file through adb i get an error code on both. I believe that CWM said it cannot mount E:/SD Card.
I also have nothing to bootup to (bootloop)
I really need my phone and any help would be greatly appreciated!
There will be a cash reward for the person to help me get this working. (paypal)
Click to expand...
Click to collapse
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.

That sucks balls MyMonkeyBalls..
Yeah, has happened to me too, I had to send in to get fixed, been 3 weeks so far.
Have a read over the forums for mine and others same issue, there are tips on how to fix but this is becoming very common at the moment, I can not offer any suggestions because everything i did did not work
Good luck

Tw1tchy said:
Just calm down buddy... This is the second thread you've made so far. Now I'm going to help you and I dont want any of your money. I just want you to agree on one term and that is to not make another thread about this.
Click to expand...
Click to collapse
Sorry bro , just freaking out. Agreed.

twerg said:
That sucks balls MyMonkeyBalls..
Click to expand...
Click to collapse
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?

Tw1tchy said:
LOL!!
anyways...
what build of CM10.2 was it (example: cm-10.2-20130809-UNOFFICIAL-m7ul.zip)?
Kernel?
Firmware? (or Hboot#)
Do you have nandroid?
have you tried to go to stock?
S-OFF?
locked/relocked/unlocked?
logcats? (twrp or cwm)
ATT, TMO, Sprint, GPE, etc?
Any other info?
Click to expand...
Click to collapse
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
I believe it all started going crazy when i tried to go back to stock and wipe the data (i did a factory reset from hboot as well as cwm)

mymonkeyballs said:
cm-10.2-20130815-UNOFFICIAL-m7ul_doubleTap.zip
Kernel that came with the ROM
1.44.0000
I dont believe I have a nandroid anymore, if i do it would be TWRP's.
I cant get back to stock
S-On
Unlocked
No
Bell (unlocked)
Nothing is showing up in Twrp or CWM its like i have nothing installed on my device. I have a constant bootloop with the cm10.2 boot animation.
Click to expand...
Click to collapse
Before LC's CM10.2 were you running a 4.1.2 rom?

Tw1tchy said:
Before LC's CM10.2 were you running a 4.1.2 rom?
Click to expand...
Click to collapse
No. 4.2.2

mymonkeyballs said:
No. 4.2.2
Click to expand...
Click to collapse
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery

Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app

Tw1tchy said:
Okay well that rules out the simple.
Now lets see if i understand the situation correctly. If you try to boot into system all you get is a CM bootloop and custom recovery's show an empty sdcard? You say adb commands dont work but have you tried fastboot commands in fastboot mode yet?
Try:
fastboot devices
fastboot erase cache
fastboot reboot-recovery
Click to expand...
Click to collapse
Yes. Fastboot commands work but doesnt resolve my issue.

thejosh86 said:
Dude - he's done a factory reset from the bootloader which has wiped his virtual sd card. You basically need to format it back into a fat32 partition so the adb side load will work.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So what do I have to do sorry

I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.

thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Click to expand...
Click to collapse
I would highly appreciate that. Thanks bro

thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
Thanks ! Testing it now. Will update.

thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
HALLELUJAH !! She is working ! Words cannot describe how happy i am ! i thought i was done! THANK YOU!

hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!

We saved mymonkeyballs =D
Sent from my One using xda app-developers app

thejosh86 said:
I've done this before a long time ago now myself and was able to fix it because I could still boot into my rom and windows would offer to format it for me.
There used to be a guide in the One XL forum with a step by step even a youtube how to fix it - just trying to find it now.
Edit: Okay found it - full props to XsMagical for this fix.
Youtube is here: http://www.youtube.com/watch?v=H-vf5eHV3_s&feature=youtu.be
Original XDA Post here: http://forum.xda-developers.com/showthread.php?t=1942605
It's for a One XL but the principle is the same as they both use Virtual SD Cards.
Make sure you're in the bootloader go into fastboot
Download the stock recovery from this link: https://www.dropbox.com/s/v7byetxqc2ogzqq/recovery144.img
Make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery144.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into recovery and try sideloading a rom and then flashing it.
Click to expand...
Click to collapse
thejosh86 said:
hahaha no worries mate, it's all part of the learning process.
Now just remember when you've got a custom recovery you don't need to use the factory reset in bootloader!
Click to expand...
Click to collapse
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!

mymonkeyballs said:
Haha, that was kinda stupid now that i look back on it. I cannot say thank you enough!
Click to expand...
Click to collapse
Hey dude, don't forget to put [Resolved] in the thread title.

Still no OTA but you want KitKat AND keep your data?

Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
UPDATE:
I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors.
Once again: I am sorry and I hope nobody got stuck due to my mistakes!!!

Some errors here.
random hero said:
fastboot flash bootloader bootloader-mako-makoz10o.img
Click to expand...
Click to collapse
Should be
fastboot flash bootloader bootloader-mako-makoz20i.img
random hero said:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
Click to expand...
Click to collapse
Should be
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.84
random hero said:
fastboot flash recovery recovery.img
Click to expand...
Click to collapse
Skip this if you dont want your custom recovery to be stock again. :good:

random hero said:
Hello friends!
I want to share some information for the beginners here:
While there is the Nexus 4 factory image for KitKat available, there still are non known OTA urls.
But you can flash KitKat anyway AND keep your data (as long as you have an unlocked bootloader):
1. Download the factory image from here:
https://developers.google.com/android/nexus/images?hl=de#occamkrt16o
2. extract ALL the files contained into the same directory where your fastboot.exe is saved, for unpacking I recommend using 7zip
3. boot your phone into bootloader
4. type in the following commands:
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot reboot
You're done, KitKat on your Nexus 4, your apps and data still available!
Note: Your phone has to be full stock!!!!
Click to expand...
Click to collapse
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142

vanmarek said:
If you're making a guide, make sure you give people the correct commands (the numbers of the bootloader and radio are wrong). Not to mention there already is a guide where flashing the update without losing data is explained.
http://forum.xda-developers.com/showthread.php?t=2527142
Click to expand...
Click to collapse
The numbers of radio & bootloader in Factory image itself are wrong

I am sorry for the two "spelling errors". I corrected them, should be all fine now.
I did not notice that the other guide contains information about flashing KitKat without losing all your data...
sometimes it can be hard to keep an eye on all the threads in every detail...

fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10

Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot

Onknight said:
Don't really want go threw all that ..
dose somebuy just have image I can flash without having to use the above
I want down load the Image
Boot into Recovery and Flash the Image with Team win Project
Then Reboot
Click to expand...
Click to collapse
there are some stock images with root on android develop or orig android develop.
edit: can use dd command to flash images if u have root.
do dd if=/block of/img
like dd if=/dev/block/platform/by-name/system /data/media/0/download/images/zipextracted/system.img

opssemnik said:
fastboot flash bootloader bootloader-mako-makoz10i.img still wrong should be 20 instead of 10
Click to expand...
Click to collapse
Again sorry for that... updated. Thank you!

"I'm really sorry for the mistakes I made in this thread.
I corrected them all by now, I think.
To make it more easy for you: You can rename the radio and the bootloader files let's say to radio.img and bootloader.img. Then use the fastboot commands with these new names. So you're a bit more safe not to make spelling errors."
I thought it was excellent! Anyone who knows what they are doing in the Command Prompt/Terminal understands that they can hit the Tab key to auto-complete the filename. Its up to them to make sure they are accessing their correct folder/file name, not yours!

good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is free, winrar is not.

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
In my opinion 7Zip looks slightly better and it doesn't spam you with that your trial is over every time you open it.

what to do with a custom rom?
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!

maverickronny said:
good work, although i have a different question, why is it that everyone always recommends 7zip for extraction of factory image, i have always been using winrar, i googled this and got nothin, so plz do tell anyone who knows the reason
Click to expand...
Click to collapse
7zip is far more friendly towards archives other than rar and zip formats. it's also the only archive app I've found that will allow you to open a flashable zip or apk and replace files inside (like an icon's image file, for example) without having to actually decompile/recompile either the zip or apk (assuming you don't change too much with either file-type)
mad_zack said:
I have PA on my N4 and was wondering what to do to get KitKat? is the procedure similar or different?
Thanks a lot!
Click to expand...
Click to collapse
whether it's a custom or stock rom does not matter. the procedure will be the same either way

Upgrading 4.2>4.3>4.4 was always a piece of cake with Wug toolkit and never had to reinstall any application.
Keeping my settings and applications was important for me.
Sent from my NookColor using Tapatalk 4

how is this method different from if i just removed the -w wipe parameter?

maverickronny said:
how is this method different from if i just removed the -w wipe parameter?
Click to expand...
Click to collapse
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.

Confused as to why people take all these steps when its just unlock>flash recovery>Flash update rom of your choice and done. All these threads on the same thing makes no sense and lets be honest its not that hard to keep up with threads if you search extensively prior to making up a thread which at week three of KitKat you should of thought would be up already.
Not flaming anyone just trying to understand the thought process. Mistakes happen I get it but we got to do better especially with so many people destroying their phones over simple things.... Jus Sayin'

hp420 said:
the method you refer to will still install the userdata.img file, which will wipe your rom's userdata, as well as anything on your storage partition. The method mentioned in this thread's OP omits the userdata.img file and relies on the user manually wiping the rom data in n custom recovery, therefore wiping only rom data while leaving the storage partition untouched.
Click to expand...
Click to collapse
I updated from 4.3 to KRT16O (and later, KRT16S) by omitting the "-w" from the batch file, and I didn't lose a byte of userdata. My bootloader is unlocked, but everything else is stock.
It was so painless, I wonder why I ever bothered waiting for OTAs in the first place.

[Q] Can't unlock bootloader as there is no OS installed

Hi everyone,
I was in the process of installing the stock Android factory 5.1 image from Chroma -- During this process I wiped everything (System data, user data, cache, etc) in TWRP and then went to fastboot to start the factory image flashing process. However, I accidently relocked my bootloader by executing my commands in the wrong order. I am now in the position where I can't unlock my phone's bootloader, as I need to enable "Allow OEM Unlock" in the developer settings, however, I can't do that as my phone currently has no OS installed.
I am at a gridlock currently, not sure how to proceed. Any ideas as to how I can fix this?
Any help would be much appreciated, as at this point, I am totally locked out of my device

Format cache and userdata via fastboot.
Edit: TWRP for the win
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ

DebianDog said:
See @rootSU a tool might have saved him
Click to expand...
Click to collapse
@DebianDog, I never need saving

DebianDog said:
Format cache and userdata via fastboot. If that doesn't work, nothing you can do.
Edit: no OS? Yeah....
Sorry bro RMA
Never relock your bootloader. See @rootSU a tool might have saved him
Sent from my Benzo'd Google N6 on VZ
Click to expand...
Click to collapse
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3

Ooohhh Nice! Nothing like having a backup Good job!
Sent from my Benzo'd Google N6 on VZ

curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?

BladeRunner said:
curious as to how one relocks the bootloader by "accident" Isn't the only way by issuing the "Fastboot OEM LOCK" command?
Click to expand...
Click to collapse
Cutting and pasting while not paying attention is what I figured.
Not something I've done on my phone but at work once or twice....
Sent from my Benzo'd Google N6 on VZ

Glad it's all sorted.
Just noticed the avatar, very appropriate

rootSU said:
Glad it's all sorted.
Just noticed the avatar, very appropriate
Click to expand...
Click to collapse
I was thinking the same thing actually haha

No TWRP backup...
p011uX said:
Formatting the cache and userdata with "fastboot -w" fixed my TWRP bootloop issue. At this point I was not able to write data to /data/media to try and restore one of my backups. So I ran a backup in TWRP, which worked, and also formatted the data partition, as I can now write to /data/media from my computer while in TWRP.
From here, I was able to copy a TWRP backup I had on my computer, and restore it. I was then able to boot into Android once again, Allow OEM unlock, and then successfully unlocked my bootloader.
Wow, what a headache. But all is working now -- I was unaware of the new low level security features with Android 5.1
If anyone wants me to clarify my fix for this, feel free to ask.
Thanks everyone for the help! <3
Click to expand...
Click to collapse
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?

NDAMT said:
First time poster, please be gentle
I'm in the same position, however I do not have a TWRP back-up on my computer to overwrite the one I just created. Is there anyway to get a standard system copy of a backup just to allow installation of OS and subsequent re-unlocking of the bootloader and at that point re-wipe and start from scratch?
Click to expand...
Click to collapse
Do you have TWRP recovery installed?

rootSU said:
Do you have TWRP recovery installed?
Click to expand...
Click to collapse
Yes. Luckily. :good:

NDAMT said:
Yes. Luckily. :good:
Click to expand...
Click to collapse
Just download a stock rom.zip and put it on your sdcard.

rootSU said:
Just download a stock rom.zip and put it on your sdcard.
Click to expand...
Click to collapse
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "

NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
Where did you get that? Got a link?

NDAMT said:
I tried that, but I keep getting a failed message: " Error flashing zip '/sdcard/image-shamu-lmy47e.zip' "
Click to expand...
Click to collapse
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk

rootSU said:
Where did you get that? Got a link?
Click to expand...
Click to collapse
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
zephiK said:
I don't think that's a flashable zip. View the contents of the zip.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"

NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
No you need a flashable rom.zip from XDA.

NDAMT said:
I used the download from the official Google Nexus Factory Images page. The forum wont let me post an external link yet.
From there I decompressed the .tar, and copied the resulting files onto the Nexus 6 internal SD.
What should I be looking for in particular?
"bootloader-shamu-moto-apq8084-7108"
"flash-all"
"flash-all.sh"
"flash-base.sh"
"image-shamu-lmy47e"
--> contains: android.info, boot, cache, recovery, system, userdata
"radio-shamu-d4.0-9625.02.98"
Click to expand...
Click to collapse
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Sent from my Nexus 6 using Tapatalk

rootSU said:
No you need a flashable rom.zip from XDA.
Click to expand...
Click to collapse
zephiK said:
That's not a flashable zip. Those are fastboot images meant to be flashed in bootloader mode, not in recovery mode.
Click to expand...
Click to collapse
OK, at this point treat me like a noob. What rom.zip would you recommend for someone who is trying to get their phone back to factory?

Nexus 6 stuck at google screen , Need Assistance.

So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you

I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app

faraz90 said:
So i tried flashing the factory image onto my rooted nexus 6 device manually , but while doing so i couldnt get the system.img to load as it kept saying "unable to allocate byte 1176........bytes" something like that. So i read about this error on some forums and they suggested to erase system , cache , userdata and then try flashing the stock image. Upon doing so it gave the same error and unable to load sys.img file.
Now , im stuck at the splash screen with stock recovery and bootloader working fine.
Im aware that my phone is bricked please advise what can i do to fix this issue.???
Thank you
Click to expand...
Click to collapse
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.

Evolution_Tech said:
First thing, do NOT lock your bootloader. Are you trying to use flash all? If so, do not. Flash the images separately.
Click to expand...
Click to collapse
gee2012 said:
I take it you placed the system.img in the platform-tools folder an you typed fastboot flash system system.img in cmd.
Sent from my Nexus 10 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.

faraz90 said:
Thanks for the quick reply.
Yes i did place is it under the platform tools folder and tried flashing separately as per the instructions given to flash manually.
I know that i should not lock the bootloader.
Im currently trying to flash using the toolkit "flash stock + unroot" and chose the current status "Softbricked/ bootloop in the bootloader mode.
Is this the right option or should i stop it ?
Thanks again for assistance.
Click to expand...
Click to collapse
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.

simms22 said:
the right option would be to flash the factory image the right way, via fastboot, and while in your bootloader.
Click to expand...
Click to collapse
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
If your Android SDK is more than 6 months old, you may need to update it. Google updated fastboot to allow flashing these very large files.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
Click to expand...
Click to collapse
No, by using fastboot commands.. The location of the images you flash is irrelevant.
faraz90 said:
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
Either there is a problem with the system.img (redownload) or there is a problem with the flash memory on your device.
You could flash a custom recovery and use that to flash a zipped ROM to see.if that makes any difference.

faraz90 said:
you mean it flashing it manually by placing the factory image in the platform tools folder ?
I tried that multiple times but it gave me the "could not allocate 721539744 bytes error: cannot load 'system.img" error :/
Click to expand...
Click to collapse
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.

Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.

simms22 said:
if you are using the flash-all, dont, as that gives many people problems as of lately. instead, you want to unzip and flash each partition separately.
Click to expand...
Click to collapse
gee2012 said:
Here is a detailled guide http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 for how to flash a image, use method 2. Its the same for the N6 as for the N5.
Click to expand...
Click to collapse
I think he has already used fast boot to flash the system.img

rootSU said:
I think he has already used fast boot to flash the system.img
Click to expand...
Click to collapse
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem

I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052

gee2012 said:
Maybe he used the wrong command like: fastboot flash system.img or something similar. If the img`s are in the correct folder and the commands are good it shouldn`t be a problem
Click to expand...
Click to collapse
Nope. He used the correct commands. There is no correct folder.

Evolution_Tech said:
I agree with @rootSU flash TWRP, flash factory zip from here:
http://forum.xda-developers.com/showthread.php?t=3066052
Click to expand...
Click to collapse
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks

faraz90 said:
thanks a bunch. I have a few questions which could be noobish yet i would like to know.
- how can i flash the custom recovery when i cant place the files under the internal storage as my phone doesn't show when i connect it to the PC ?
- just like that im downloading the zip file but i would like to first access the internal storage to place the files under the root or is there a way around to do this ?
Thanks
Click to expand...
Click to collapse
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.

Evolution_Tech said:
Flash TWRP, reboot to bootloader, select recovery mode, enter TWRP, mount MTP.
Click to expand...
Click to collapse
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!

faraz90 said:
You Sir, are a lifesaver. It worked!
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
Thanks all for the help!
Click to expand...
Click to collapse
*ahem*

rootSU said:
*ahem*
Click to expand...
Click to collapse
haha ofcourse thanks alot to you for suggesting that idea

faraz90 said:
Although for the sake of better understanding why do you think I wasn't able to flash the system image manually via fastboot ? having tried multiple times with correct fastboot commands :S
!
Click to expand...
Click to collapse
Possibly because your Android SDK tools are out of date(specifically fastboot).