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?
Related
I've seen a few threads about 16GB version phones losing half their storage after flashing.
Here are the steps to fix it:
As dellenrules mentioned in post #48 there appears to be an easier way to fix the problem:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
If for some reason that doesn't work, you can try this method:
First, you'll need fastboot.exe on your computer. If this happened to you, you should have fastboot installed If not, see section A of efrant's "back-to-stock" guide.
Next, You'll want the latest occam image. https://developers.google.com/android/nexus/images#occam
Finally, boot into the bootloader and run these commands...
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz10o.img
fastboot reboot-bootloader
fastboot -w update image-occam-jdq39.zip
Enjoy your 16GB again.
Note #1 If you encounter a boot loop after this procedure boot into stock recovery (use volume up and power to open the recovery menu) then wipe cache and factory reset.
Note #2 erikieperikie tested restoring a Nandroid backup after completing this process. The backup applied successfully and they still had 16GB user space. Details here.
UPDATED 3/13/13 for 4.2.2
not sure if i fall into this category, but my 16gb has only 8.46gb available (out of 12.92gb). I did unlock and root earlier. For the life of me, I can't seem to find the "missing" space. I'll try the above here in a bit.
RussianBear said:
not sure if i fall into this category, but my 16gb has only 8.46gb available (out of 12.92gb). I did unlock and root earlier. For the life of me, I can't seem to find the "missing" space. I'll try the above here in a bit.
Click to expand...
Click to collapse
Did you make any nandroid backups? Those usually won't be reported in storage.
Sent from my Nexus 7 using xda premium
El Daddy said:
Did you make any nandroid backups? Those usually won't be reported in storage.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
sure did. didn't think it would take "that" much space
RussianBear said:
sure did. didn't think it would take "that" much space
Click to expand...
Click to collapse
This guide is to recover the full user space after a bad flash. (Not quite sure what is causing it exactly)
In your situation your user space is fine. The nandroid blob just isn't being reported within the built in utility. If you delete the blob that storage used should be reported again.
Sent from my Nexus 7 using xda premium
El Daddy said:
This guide is to recover the full user space after a bad flash. (Not quite sure what is causing it exactly)
In your situation your user space is fine. The nandroid blob just isn't being reported within the built in utility. If you delete the blob that storage used should be reported again.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
figured it out. /data/media had a folder called "0" that mounts when i plug the phone in, but it also had the nandroid backup in the cwm folder along with some of my files i tried to restore. not sure how they got there, but they were causing the reporting issues.
I've just added this guide to the Nexus 4 Complete Index
Sent from my Nexus 7 using xda premium
RussianBear said:
figured it out. /data/media had a folder called "0" that mounts when i plug the phone in, but it also had the nandroid backup in the cwm folder along with some of my files i tried to restore. not sure how they got there, but they were causing the reporting issues.
Click to expand...
Click to collapse
I am having the same problem and also deleted these files.
Might be a noob like question but,
How do I use the commands listed at the beginning?
gmanb said:
I am having the same problem and also deleted these files.
Might be a noob like question but,
How do I use the commands listed at the beginning?
Click to expand...
Click to collapse
You'll need to download adb for those. Have you restarted after deleting the files?
El Daddy said:
I've seen a few threads about 16GB version phones losing half their storage after flashing.
Here are the steps to fix it.
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz10l
fastboot reboot-bootloader
fastboot -w update image-occam-jop40d
Enjoy your 16GB again.
Click to expand...
Click to collapse
i fail to perform this command fastboot -w update image-occam-jop40d.
it said can not read
robert_gan said:
i fail to perform this command fastboot -w update image-occam-jop40d.
it said can not read
Click to expand...
Click to collapse
I apologize. There should be a .zip at the end of that command. I will update the OP.
El Daddy said:
I apologize. There should be a .zip at the end of that command. I will update the OP.
Click to expand...
Click to collapse
EDITED: Noob in the house. Nevermind. Thanks!
El Daddy said:
I apologize. There should be a .zip at the end of that command. I will update the OP.
Click to expand...
Click to collapse
thanks very much for u reply!!
and sry for the n00b question again, so when i follow u guide,is it means i will flash a new system?
cuz i stuck at X logo soo many times,and every time i need to follow every single steps of back to stock guide exactly,then wipe the cache and factory reset to get pass it.but there is a problem, the storage only shows 5.7G.
once again thank u !!
robert_gan said:
thanks very much for u reply!!
and sry for the n00b question again, so when i follow u guide,is it means i will flash a new system?
cuz i stuck at X logo soo many times,and every time i need to follow every single steps of back to stock guide exactly,then wipe the cache and factory reset to get pass it.but there is a problem, the storage only shows 5.7G.
once again thank u !!
Click to expand...
Click to collapse
I guess I'm not following exactly what you are asking.
Yes it re-flashes the system. If you follow the steps in the original post your phone should show 16GB again if that is the version you have.
Sent from my Nexus 7 using Tapatalk HD
gmanb said:
I am having the same problem and also deleted these files.
Might be a noob like question but,
How do I use the commands listed at the beginning?
Click to expand...
Click to collapse
It wasn't actually a problem
See here
http://forum.xda-developers.com/showthread.php?t=2067293
I keep getting the same error with the last command.
error: failed to load 'image-occam-jop40d.zip': No error
I have directed it to the right place, but still nothing's happening.
Caumen said:
I keep getting the same error with the last command.
error: failed to load 'image-occam-jop40d.zip': No error
I have directed it to the right place, but still nothing's happening.
Click to expand...
Click to collapse
Try rebooting your computer. I had that error once trying to flash recovery on my gnex. Rebooting my PC fixed it.
Sent from my Nexus 4
El Daddy said:
Try rebooting your computer. I had that error once trying to flash recovery on my gnex. Rebooting my PC fixed it.
Sent from my Nexus 4
Click to expand...
Click to collapse
Oh ****, the classic, let's see if it helps.
---------- Post added at 10:22 PM ---------- Previous post was at 09:59 PM ----------
It didn't help rebooting the computer.
What could it be?
I actually own prototype device with 6GB of memory and "NOT FOR SALE" text on the back
Amount of memory does not changed after reflash
But inside occam-jop40d-factory-ca7602f0.tgz i found update for radio hardware which fix WiFi connection issues.
So, in case that your phone see APs but cannot connect to them you may use radio firmware from given archive.
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img
t3h.Dr01d said:
I actually own prototype device with 6GB of memory and "NOT FOR SALE" text on the back
Amount of memory does not changed after reflash
But inside occam-jop40d-factory-ca7602f0.tgz i found update for radio hardware which fix WiFi connection issues.
So, in case that your phone see APs but cannot connect to them you may use radio firmware from given archive.
Code:
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.33.img
Click to expand...
Click to collapse
5.67GB is the formatted size of the 8GB version.
Sent from my Nexus 4
Hey got my nexus 6 yesterday. Unlocked and rooted it. Now i cant install the OTA update. TWRP asks for a password. What is that about. Do i need to relock and reinstall the stock bootloader?
To apply OTA, you need to be completely stock. Not even rooted.
Either go back to stock, or just flash the new system images without wiping user data
Can i flash this system images from the downloads through the OTA?
driskl said:
Can i flash this system images from the downloads through the OTA?
Click to expand...
Click to collapse
Not sure what you meant. You can't flash a system image as an OTA. You can however download the system images and flash them in fastboot (you'll need to unzip it and flash the images one by one - see Method 2 at this Nexus 5 thread about how to flash - the steps are essentially the same. Just remember to enable OEM unlock in developer options before anything)
Note; unless you skip userdata image, your data will get wiped.
jj14 said:
Not sure what you meant. You can't flash a system image as an OTA. You can however download the system images and flash them in fastboot (you'll need to unzip it and flash the images one by one - see Method 2 at this Nexus 5 thread about how to flash - the steps are essentially the same. Just remember to enable OEM unlock in developer options before anything)
Note; unless you skip userdata image, your data will get wiped.
Click to expand...
Click to collapse
Ok thanks, that seems simple enough. Ill search for the files when i get home i guess.
driskl said:
Ok thanks, that seems simple enough. Ill search for the files when i get home i guess.
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/images
jj14 said:
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Haha, Thanks that helps. Its my first nexus device, its never been that easy.
Now is wish my work computer didnt struggle with MTP and ADB.
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).
ad
Ducky10100 said:
Hello guys. I've got a big problem. I rooted my Nexus 6 and installed TeamWin Recovery, but something wasn't installed correctly so I went to factory reset my phone from TeamWin recovery and completely deleted EVERYTHING, including my OS. Now I cannot do anything, my phone just stays at the Google logo. Just to clear things up:
My phone isn't rooted
Bootloader isn't unlocked
I have no OS.
I need help on how to flash android 5.0 back on my Nexus (Yes I've tried using Toolkit, but since my phone doesn't boot it's no use to me). Help would be much appreciated.
Click to expand...
Click to collapse
I dont mean to sound rude, really, but so what? you can download and transfer a ROM to your twrp recovery via regular file transfer, adb sideload, or adb push. so download what you need, choose a method, then transfer it to your phone. you dont have other options, besides for flashing a factory image.
Why did you install a custom recovery if you haven't unlocked your phone?
It seems to me you should start by downloading the appropriate factory image from Google. And flash everything (with the exception of boot loader) from inside your boot loader. Press and hold the power button while it's on, this will set a reboot. While the screen is black, press and hold power and volume down. This will get into boot loader.
Let us know if you need assistance on how to flash the factory images.
brymaster5000 said:
Why did you install a custom recovery if you haven't unlocked your phone?
It seems to me you should start by downloading the appropriate factory image from Google. And flash everything (with the exception of boot loader) from inside your boot loader. Press and hold the power button while it's on, this will set a reboot. While the screen is black, press and hold power and volume down. This will get into boot loader.
Let us know if you need assistance on how to flash the factory images.
Click to expand...
Click to collapse
I had my phone rooted and unlocked, but I reset everything and that's when it happened.
simms22 said:
I dont mean to sound rude, really, but so what? you can download and transfer a ROM to your twrp recovery via regular file transfer, adb sideload, or adb push. so download what you need, choose a method, then transfer it to your phone. you dont have other options, besides for flashing a factory image.
Click to expand...
Click to collapse
Hey dude if you can point me to where I can download one and a tutorial I will, but I've tried almost everything and nothing seems to work.
Ducky10100 said:
Hey dude if you can point me to where I can download one and a tutorial I will, but I've tried almost everything and nothing seems to work.
Click to expand...
Click to collapse
first off, look at your recovery, you should be able to find a mtp and a adb sideload option. mtp would be the regular file transfer. you can google adb sideload twrp, and youll find instructions on that. or you can try googling adb push, and you will find instructions. thats the one i normally would use(but its been a long time), ive deleted my os before as well :angel:
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
here's something I just found about adb sideload http://www.droidviews.com/sideload-roms-mods-using-adb-sideload/
simms22 said:
first off, look at your recovery, you should be able to find a mtp and a adb sideload option. mtp would be the regular file transfer. you can google adb sideload twrp, and youll find instructions on that. or you can try googling adb push, and you will find instructions. thats the one i normally would use(but its been a long time), ive deleted my os before as well :angel:
---------- Post added at 06:35 PM ---------- Previous post was at 06:23 PM ----------
Click to expand...
Click to collapse
Okay thanks man.
reflashing stock via wugs nexus tool as bricked should help.
(this helped me, just read it didnt help you, did you try as bricked/softbricked? (sorry not sure what it is))
rhystagram said:
reflashing stock via wugs nexus tool as bricked should help.
(this helped me, just read it didnt help you, did you try as bricked/softbricked? (sorry not sure what it is))
Click to expand...
Click to collapse
Overkill. You can just put a ROM zip on the sdcard and flash it via TWRP recovery
danarama said:
Overkill. You can just put a ROM zip on the sdcard and flash it via TWRP recovery
Click to expand...
Click to collapse
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
rhystagram said:
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
Click to expand...
Click to collapse
Internal storage is called sdcard. All you need to do is boot TWRP and connect to PC. You should see your internal storage on your PC then. Drag and drop your ROM from PC to internal storage. Flash ROM, profit.
rhystagram said:
sdcard with no sdcard slot & support? lol... you cant put anything on the phone with no internal storage either...
Click to expand...
Click to collapse
/sdcard is a common directory mounted at /data/media/0. TWRP has MTP access so like android, you plug it into the computer and drag files across. You don't need to remove it to do that.
...and indeed you are right, if you delete the "internal storage"/as s it shows up as in MTP mode, you would have to flash stock (though we'd recommend using fastboot not toolkits) however that is not the case here. The user said he deleted " everything" via TWRP. Although there is an option to "wipe" internal storage, this only wipes the /sdcard data - NOT deletes "internal storage" as someone can do on a computer. So yeah, the quickest and best way to recover from "deleted OS" is to put a ROM.zip on the sdcard and flash it.
Will someone please refer me to a download for Android 5.0. I've tried some, but all the sites are block by my internet provider.
Ducky10100 said:
Will someone please refer me to a download for Android 5.0. I've tried some, but all the sites are block by my internet provider.
Click to expand...
Click to collapse
There is only one legitimate site for Google factory images, and it's linked below. I don't understand why any provider would block it...
And why do you want 5.0? That is the original, release version for the Nexus 6? What version are you on, today? If you are on 5.1 or higher, and you decide to downgrade, do not downgrade your bootloader, as it could brick your device.
https://developers.google.com/android/nexus/images
cam30era said:
There is only one legitimate site for Google factory images, and it's linked below. I don't understand why any provider would block it...
And why do you want 5.0? That is the original, release version for the Nexus 6? What version are you on, today? If you are on 5.1 or higher, and you decide to downgrade, do not downgrade your bootloader, as it could brick your device.
Click to expand...
Click to collapse
I've only had my Nexus for around 3 weeks and I've not updated from 5.0 yet.
Ducky10100 said:
I've only had my Nexus for around 3 weeks and I've not updated from 5.0 yet.
Click to expand...
Click to collapse
Doesn't matter. You've got NO OS now, so just flash the latest. If you're wanting to keep TWRP and dead set against flashing a ROM.zip from recovery as I've suggested, just flash the system and boot image from the factory images.
Can we get it done already?
danarama said:
Doesn't matter. You've got NO OS now, so just flash the latest. If you're wanting to keep TWRP and dead set against flashing a ROM.zip from recovery as I've suggested, just flash the system and boot image from the factory images.
Can we get it done already?
Click to expand...
Click to collapse
Yeah I've already done it now.
Ducky10100 said:
Yeah I've already done it now.
Click to expand...
Click to collapse
Awesome
Thanks for everyone's help!
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
evan7899 said:
The system partition was deleted and the phone has TWRP. The mac recognizes the ADB device and the MTP. Tried toggling the MTP, no success. Currently android file transfer fails every time due to a missing MD5 file in the android 6.0.1 zip, although all that is being attempted is a drag and drop. ADB sideload says it has completed but no files appear on the phone to flash, or in the file explorer, and so does ADB push. Tried re-downloading the rom, rebooting the phone and everything else.
Any help is appreciated.
Click to expand...
Click to collapse
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
simms22 said:
flash the factory image, reflash twrp, reflash your ROM and SuperSU.
Click to expand...
Click to collapse
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
evan7899 said:
That is what is being attempted. All data has been wiped from the phone and there is an issue getting the ROM and a new TWRP to the phone. The only available computer is a mac and Android File transfer keeps reporting a MD5 file error whenever the rom is tried to be moved over.
Click to expand...
Click to collapse
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
simms22 said:
thats not how you flash a factory image. you boot into the bootloader, and use fastboot to flash it, via your computer. you dont download it to your phone http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
Click to expand...
Click to collapse
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
evan7899 said:
The factory image is the .TGZ file? Or one in there. I am accustomed to just flashing zip files from TWRP on a OnePlus One but this is a friends Nexus 6 and in a very odd state.
Click to expand...
Click to collapse
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
simms22 said:
yup, its a .tgz file. download it, "unzip" it, then flash each partition separately instead of all together using fastboot. its the only way to get everything back. then you can flash twrp after, and SuperSU.
Click to expand...
Click to collapse
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
evan7899 said:
Sorry this is very simple but everything is going wrong...flashing the system.img exceeded partition limits. Do I rename files or just type them as is. Sorry many guides are contradicting and I'm very confused.
EDIT: The phone isnt being recognized by the computer in fastboot mode.
Click to expand...
Click to collapse
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
simms22 said:
just type in the names, like system.img or boot.img.
and did you install the driver for adb.fastboot?
Click to expand...
Click to collapse
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
evan7899 said:
This is on a mac and ADB was recognizing the device beforehand but fastboot is not. I am not sure if he has the fastboot drivers installed. I will check that
Click to expand...
Click to collapse
honestly, I wouldn't know what you need on a Mac to get it working :angel:
simms22 said:
honestly, I wouldn't know what you need on a Mac to get it working :angel:
Click to expand...
Click to collapse
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
evan7899 said:
Yup thats my same issue. On my PC it could have been done easily but I'll keep trying. Thanks for all of the help!
Click to expand...
Click to collapse
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
You need to run sudo fastboot insertcomand on Mac. good luck.
simms22 said:
maybe this will help? http://htc-one.wonderhowto.com/how-...-mac-os-x-send-commands-your-htc-one-0151178/
Click to expand...
Click to collapse
Thanks but we have tired that. Due to distance this has all had to be over the phone which hasnt helped either. I will update this with how we got it working when we do.