So I was following all the steps from this thread: http://forum.xda-developers.com/showthread.php?t=2010312
and I did flash the stock 4.2 img. Now, after unlocking the boot loader, i didnt exit the fastboot mode and stayed in. And continued the steps of section D (all of it). Then I did a fastboot reboot , and Google appeared and below it unlocked lock and then the jellybean logo. It's been almost 20 min and it hasn't passed that screen yet. The rainbow colour X.
What do I do to fix this?? I can go back to fastboot mode, but not sure what to do. I did the fastboot erase cache before rebooting my phone!
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
El Daddy said:
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
I did this though: 13) Erase the cache partition: fastboot erase cache
14) Reboot: fastboot reboot
Okay, and I will try to do that now.
El Daddy said:
Look at the notes of section D.
You have to reboot into recovery, clear cache and factory reset.
Sent from my Nexus 4
Click to expand...
Click to collapse
I booted myself into recovery via fastboot and it shows android laying down with a red triangle and inside that its " ! "
What now?
Press volume up and power at the same time. It will open the menu.
Sent from my Nexus 4
LimitsX said:
I booted myself into recovery via fastboot and it shows android laying down with a red triangle and inside that its " ! "
What now?
Click to expand...
Click to collapse
Flash it again using fastboot and the official Google image. Recent nexus devices are strange, i never had problems before but softbricked both nex4 and 7 just like that. If you can enter fastboot mode all is well though.
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
El Daddy said:
Press volume up and power at the same time. It will open the menu.
Sent from my Nexus 4
Click to expand...
Click to collapse
Do I do that on that screen? I did, and it went into completely black screen.
molesarecoming said:
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
Click to expand...
Click to collapse
Okay, im gonna go and do that! Thanks!
I was trying to mount the sdcard with nexus 4 but it wont do that with CWM and TWRP.
okay I think I just lost access to everything on my phone :|. I am still on TWRP, is there anything I can do with that?
I accidentally wiped the system files ugh. So I lost bootloader which means my phone is empty and useless and im still active on TWRP.
This is what I did in TWRP:
went to WIPE menu and did the following:
1)Wipe Cache
2)Dalvik Cache
3)Factory Reset
4)Wipe System
5)Wipe External storage ( didn't work - failed)
6)Wipe Internal storage (deleted)
So I have a boot loader still ?? or is that gone too? I am still active in TWRP. What are my options to fix this mess I've gotten myself into =\.
molesarecoming said:
Ps. That tutorial, that was the longest one I've seen in my life. Are you aware that Google images contain clickme.bat files? You literally click it and it's done. Just make sure you have fastboot and adb installed. You can extract them from nexus toolkit as well.
If you do wanna make it by hand, also no problem. Download the image from here:https://developers.google.com/android/nexus/images
And type:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip
Exchange the correct names of course. And make sure you're in fast boot mode.
Click to expand...
Click to collapse
Yeah the thread is verbose, but its more of a tutorial than a "fix my fone nao!!!" Thread.
Efrant wrote it like that so users understand what they are doing.
Sent from my Nexus 4
so basically I have a dead phone?! =\. Anyone..help or point me in the right direction?
Nevermind. I figured it out and fixed it :victory: !!
El Daddy said:
Yeah the thread is verbose, but its more of a tutorial than a "fix my fone nao!!!" Thread.
Efrant wrote it like that so users understand what they are doing.
Sent from my Nexus 4
Click to expand...
Click to collapse
sure, didnt want to apply its not good or anything. its nice to know that google gives you some sort of emergency option, i've used it countless of times.
LimitsX said:
okay I think I just lost access to everything on my phone :|. I am still on TWRP, is there anything I can do with that?
I accidentally wiped the system files ugh. So I lost bootloader which means my phone is empty and useless and im still active on TWRP.
This is what I did in TWRP:
went to WIPE menu and did the following:
1)Wipe Cache
2)Dalvik Cache
3)Factory Reset
4)Wipe System
5)Wipe External storage ( didn't work - failed)
6)Wipe Internal storage (deleted)
So I have a boot loader still ?? or is that gone too? I am still active in TWRP. What are my options to fix this mess I've gotten myself into =\.
Click to expand...
Click to collapse
for the next time, you better learn what all this stuff is and means which you are flashing. i cant help but thinking its dangerous what you're doing there. if you are in twrp you're free to install any rom, your phone is pretty much safe if you can access it. wiping system wont kill your bootloader, system is a partition, your rom gets installed in there. you can wipe it, most roms even do it by default in the installation script. if your bootloader is gone you'll know.
Related
Ok thanks a head of time my tab is stuck on booting primary image kernel it had flex rom 4.0.4 and skrilaz cz v8 boot loader and when I search I don't find anything that really helps me . I had bricked it trying to figure it out but got it back to the stuck in boot loader stage my tab it can go to apx mode and I can use the recovery and it charges and I have tried 3 ICS roms and i'm still on the screen .
MODFAST said:
Ok thanks a head of time my tab is stuck on booting primary image kernel it had flex rom 4.0.4 and skrilaz cz v8 boot loader and when I search I don't find anything that really helps me . I had bricked it trying to figure it out but got it back to the stuck in boot loader stage my tab it can go to apx mode and I can use the recovery and it charges and I have tried 3 ICS roms and i'm still on the screen .
Click to expand...
Click to collapse
Make sure you are running the most recent CWM (1.7.2 or 1.7.3)
Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media. NOTE: This will wipe your tab clean of fotos, music, etc. Everything.
Then do your wipes and formats.
MD
Moscow Desire said:
Make sure you are running the most recent CWM (1.7.2 or 1.7.3)
Boot to recovery, and this time, do all your wipes
Wipes Menu
a. wipe Data/factory reset
b. wipe cache
c. wipe Dalvik
Go to Mounts and storage
a. Format system
b. Format Flexrom
Install rom, and make sure it's a rom with an ICS kernel.
As a last chance if the above normal things don;t work,
you may have corrupted data somewhere, and in this case, go to Backup and Restore and toggle Data Media. NOTE: This will wipe your tab clean of fotos, music, etc. Everything.
Then do your wipes and formats.
MD
Click to expand...
Click to collapse
I have tried the suggested and I'm still on boot loader.
ROMS I used
FLEXREAPER-ReliX-GT_Rev1 ANDROID 4.0.3
RE-FLEXxx-ShellSHOCKRev1.1
Acer_AV041_A500_1.054.00_WW_GEN1-DEODEXED-FULLROOT
Also on CWM1.7.3 latest
Wiped everything twice and didn't see any change so should I try a stock Rom and just revert to non root ?
You can also wipe userdata from fastboot: "fastboot erase userdata". You may try using adb after a while and do logcat, from where you can see what's the issue.
Skrilax_CZ said:
You can also wipe userdata from fastboot: "fastboot erase userdata". You may try using adb after a while and do logcat, from where you can see what's the issue.
Click to expand...
Click to collapse
OK I can't seem to get my tab on fastboot mode and I haven't used adb to get a logcat so is there a thread that talks bout how to do that.
MODFAST said:
OK I can't seem to get my tab on fastboot mode and I haven't used adb to get a logcat so is there a thread that talks bout how to do that.
Click to expand...
Click to collapse
I'd try flashing the bl again, sounds strange u can't get to fastboot mode??
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
I'd try flashing the bl again, sounds strange u can't get to fastboot mode??
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
I must have messed up but now I have gotten on fastboot mode but don't see the setting to erase userdata
you type in command from PC.
open cmd prompt from where u have fastboot.exe
type: fastboot devices
u should see a ?
then type: fastboot erase userdata
it should then tell u userdata erased.
u can also flash recovery.img with fastboot and get yr cpuid....very useful
Sent from my GT-I9300 using Tapatalk 2
dibb_nz said:
you type in command from PC.
open cmd prompt from where u have fastboot.exe
type: fastboot devices
u should see a ?
then type: fastboot erase userdata
it should then tell u userdata erased.
u can also flash recovery.img with fastboot and get yr cpuid....very useful
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Okay I don't have fastboot.exe file where do I download that at ? I tried to find my device with cmd and looked for fastboot.exe and looked it up and only file I do have is fastboot from my root 3.2.1 folder.Thank for all the help
Sent my laptop [/QUOTE]
MODFAST said:
Okay I don't have fastboot.exe file where do I download that at ? I tried to find my device with cmd and looked for fastboot.exe and looked it up and only file I do have is fastboot from my root 3.2.1 folder.Thank for all the help
Sent my laptop
Click to expand...
Click to collapse
You have to have the Android SDK installed on your PC.
Then you will find it in Program Files (or Program Files (x86))/Android/Android-SDK/Platform-Tools/ There you will find fastboot.exe
MD
Moscow Desire said:
You have to have the Android SDK installed on your PC.
Then you will find it in Program Files (or Program Files (x86))/Android/Android-SDK/Platform-Tools/ There you will find fastboot.exe
MD
Click to expand...
Click to collapse
Okay I downloaded the SDK and got the fastboot.exe and downloaded the adb file to get it to run but, when I got to cmd I don't understand why it keeps say can't find pacific file or external command ..ect .I have my acer in fastboot mode and its reconized as a fastboot device on my laptop.
MODFAST said:
Okay I downloaded the SDK and got the fastboot.exe and downloaded the adb file to get it to run but, when I got to cmd I don't understand why it keeps say can't find pacific file or external command ..ect .I have my acer in fastboot mode and its reconized as a fastboot device on my laptop.
Click to expand...
Click to collapse
You probably got "java' is not recognized as an internal or external command."
You still need to install the Java dev kit. Go to Oracle, and get the Java Jdk7 and install it. (remember, android uses Java)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Then, after install, view this video to set the PATH, then do the same for CLASSPATH
http://www.youtube.com/watch?v=D13ZSPA1Ff0
You won't get that error anymore.
MD
Moscow Desire said:
You probably got "java' is not recognized as an internal or external command."
You still need to install the Java dev kit. Go to Oracle, and get the Java Jdk7 and install it. (remember, android uses Java)
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Then, after install, view this video to set the PATH, then do the same for CLASSPATH
http://www.youtube.com/watch?v=D13ZSPA1Ff0
You won't get that error anymore.
MD
Click to expand...
Click to collapse
Okay I downloaded the java 7 and followed the process but still got errors so i went to sdk folder and did it over
I went by this video and it worked "http://www.youtube.com/watch?v=oaNM-lt_aHw"
After I got commands to work i typed fastboot erase userdata and i got on my tab "erasing uda partition then it said Done.
I used the cmd to reboot table to recovery and download a new ics rom.
It didnt work it went back to its ussal stuck on v8bootloader self. What do I do now ?
I'm in the exact same position right now. On ICS v8 bootloader, flashed latest re-flexxx rom, tablet was sluggish. Turned it off in order to restart it. Upon restart tablet froze @ "booting primary kernel." I tried everything I could as far as doing things in CWM (flashing different roms, none would get past booting primary kernel | tablet won't go into APX Mode) Tried flashing TWRP via CWM, now I can't even boot the recovery kernel.
Booted into fastboot, erased userdate. Sent fastboot flash recovery recovery.img (CWM). Said flashed SOS Partition successfully on tablet. Tried rebooting into recovery, same thing; freezes at booting primary kernel. I'm pretty sure this is the end of my A500 lol.
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Cantacid said:
Hi guys
I was trying to update to 4.3 using fastboot and after finishing i got stuck with the google on the screen. So i went on to try it again, this time installing each .img in the zip manually. While i was sending the System.img the usb connection broke and i tried again to no avail. So i was like lets do this again. So i went i started all over again with erasing boot, now the terminal is stuck on that and not going forward. Im out of options. Really need help, im helpless here. Please.
Thank You
Click to expand...
Click to collapse
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
kzoodroid said:
Is that a Mac? There is another thread with a guy having issues flashing system.img using a Mac. Not sure if he was able to fix it or not. He was able to flash all the other images just not system.img.
For reference from Efrant's thread on flashing image files if your phone hangs during first boot try this:
Note that some users indicate that they can't get past the X on boot. If this happens to you, reboot into the bootloader and select recovery. Then, when you see the Android with the red exclamation mark, hold power and press volume up to take you to the menu. Wipe cache. If that still doesn't work, boot back into recovery and do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2010312
I had the boot issue when I first flashed the images and just formatting the cache fixed it for me. I later had to do a factory reset as the phone was reporting the wrong storage size, 8 GB instead of 16 GB and the reset fixed it.
Here is the other guys Mac thread, not sure it will help you or not.
http://forum.xda-developers.com/showthread.php?t=2377647
Click to expand...
Click to collapse
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Cantacid said:
And the thing about cleaning caches is locking and unlocking bootloader does the same. Tried, i cant install recovery and system .img for some reason.
Thank you for the quick reply, seems the like the guy is having the same issue. Will post it there as well.
The issue is to fastboot the system.img
Click to expand...
Click to collapse
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
kzoodroid said:
I see you are in the other thread too but I will post this here also.
According to this thread when using a Mac you don't flash the system or kernel (boot) images.
http://forum.xda-developers.com/showthread.php?t=2377691
Click to expand...
Click to collapse
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
sn0warmy said:
Yeah you do. I just did this on my Mac for my Nexus 4 and Nexus 7 last night with absolutely no issues.
The procedure I used is as follows...
1.1) Download the factory image and ensure all .img files are extracted to the "platform-tools" folder
1.2) Boot phone into fastboot mode by powering it down then holding volume down/power at the same time until the fastboot screen appears
2) Plug the phone into the computer via USB cable
3) Open terminal and type: fastboot devices (if it recognizes your phone's serial number you are ready to move forward)
4) Reboot by typing: fastboot reboot-bootloader (I do this just to test the connection but it's not 100% necessary)
5) Flash the bootloader: fastboot flash bootloader /Users/kevin/Desktop/Android/sdk/platform-tools/bootloader.img
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio /Users/kevin/Desktop/Android/sdk/platform-tools/radio.img
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system /Users/kevin/Desktop/Android/sdk/platform-tools/system.img
10) Flash the data partition: fastboot flash userdata /Users/kevin/Desktop/Android/sdk/platform-tools/system.img (Note: this command will wipe your device)
11) Flash the kernel/ramdisk: fastboot flash boot /Users/kevin/Desktop/Android/sdk/platform-tools/boot.img
12) Flash the recovery partition: fastboot flash recovery /Users/kevin/Desktop/Android/sdk/platform-tools/recovery.img
13) Erase the cache partition: either a) fastboot erase cache OR b) fastboot format cache <<== (the second option seems to work better for most people and it's what I used)
14) Reboot: fastboot reboot
After completing step 14 your phone should reboot to the initial setup screen. If you follow those steps vigorously you won't have any issues. If it doesn't work you did something wrong and should start over. If it doesn't work on a second try then I'd re-download the system image from HERE again just to be sure the .img files you are ultimately trying to use aren't corrupt somehow.
Click to expand...
Click to collapse
In the other walk through flash system image and boot image is replaced by "./fastboot update image-occam-jwr66v.zip". This could help those who are having problems flashing the system image file. I've also seen this method used for windows in that all you flash is the bootloader image then the update image and your done.
-w is to clear the userdata, but the problem is its not pushing the system.img on the phone! Tried without -w and yet the same issue! I have restored my previous rom and madea nandroid for 4.2.2 stock! Might go back to that and try updating ota! Can somebody confirm if i have to lock bootloader and lose root to get an update!
I have no clue why the same steps work for 4.2.2 but not 4.3 image files!
Sent from my Nexus 4 using Tapatalk 4 Beta
One thing I don't think anyone has mentioned (which may actually be the core solution to this problem for everyone) is that you need to update your SDK Platform from 17 to 18 and you need to install "Android Support Repository" in order for 4.3 to properly flash. To do this open terminal and paste the path to the "android" executable file found under sdk/tools. My path was:
/Users/kevin/Desktop/Android/sdk/tools/android
After pasting the appropriate path into terminal hit enter. This will open the SDK Manager. Once SDK Manager is open it will ask to update outdated drivers. One of the drivers being updated is SDK Platform. Before hitting the update button scroll down to the 'Extras' folder and check the box next to "Android Support Repository". Now hit the update button.
After doing this, reboot the computer (may or may not be necessary) and try flashing again by following the steps I provided in post #5. Let me know if that solved it.
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Cantacid said:
Well, i may try that! But as if now, went to bootcamp, installed drivers and sideloaded 4.3. I may still try updating sdk, just in case i may neeed to do this again!
Where is this sdk/tools?
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
sdk/tools is located wherever you extracted the .zip file to. In my case I just put it all in a parent folder on the desktop called "Android".
Hello gents,
After messing around with the fastboot yesterday i got back to stock Android and realised i have only a 5GB partition....
I formatted the phone and installed again the stock Rom but that didn't work.
Anybody as any idea on how to solve this problem? thanks:good:
Anyone?
Fix for 16GB N4 showing as 8GB
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip
jsteg94 said:
I just experienced the same exact problem, and wasn't able to find a solution until I followed this guide: http://forum.xda-developers.com/showthread.php?t=2033692
Make sure you have the latest occam image https://developers.google.com/android/nexus/images#occam
Use 7-Zip to extract the files from within the .tgz file, and then the .tar file.
Shift + Right Click in the folder to Open a Command Prompt, and run the following commands:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-mako-makoz20i.img
fastboot reboot-bootloader
fastboot -w update image-occam-jwr66y.zip
Click to expand...
Click to collapse
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread
kzoodroid said:
Its a common error after flashing the factory images and all you usually have to do is this:
-Boot into STOCK RECOVERY (If you are running a custom recovery you must flash to stock)
-Clear cache
-Factory reset
which is right at the top of el daddy's thread
Click to expand...
Click to collapse
Thanks, kzoodroid. I didn't realize that you had to be in Stock Recovery. Every time I followed the above steps on el daddy's thread, I was using TWRP, which never solved the problem.
Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did
hp420 said:
I've had this issue come up more times than I can count, and just the other day I wasn't able to get back to the full storage allotment after several attempts following the steps to erase all the partitions and reflash. I did exactly what you did by flashing the factory images, re-locking the bootloader, then unlocking it again, and my storage was back to normal. I'm not exactly sure what happened, but I discovered this works, just as you did
Click to expand...
Click to collapse
Cool! :laugh:
SWEagle said:
Well i´ve been trying and trying... its simple to follow the guide but wen i get to this step fastboot -w update image-occam-jdq39.zip the CMD crashes all the time...
I´ve restarted the computer and everything but it crashes always...
And also i can´t get into stock recovery... The droid with the triangle come up the i press power and then vol up but nothing happends...
Click to expand...
Click to collapse
With my phone I have to press power and volume+ a bunch of times to get it to finally go into stock recovery it never does it on the first few tries and can take a few minutes of playing to hit them perfectly to get it to open.
SWEagle said:
Yeah, i think i just found a easy way to go around this problem!
Very simple:
1. After flashing the stock rom use Nexus Root Toolkit to do a OEM Lock
2. Run CMD fastboot and use this command: fastboot oem unlock. You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept.
3 Restart and that's it! Your back to 13GB again
Thanks to all for your help. I will share this info on El Daddy thread.
Click to expand...
Click to collapse
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.
jsteg94 said:
Wow, that's actually a lot easier. Thanks for finding a simpler way, SWEagle! I'll try that next time.
Click to expand...
Click to collapse
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock
kzoodroid said:
Instead of using the toolkit you probably could just use fastboot to lock the device too.
fastboot oem lock
Click to expand...
Click to collapse
I thought about that too. It might work. If it does it's even easier
Issue solved by using the following commands in fastboot via this link http://forum.xda-developers.com/showpost.php?p=34552123&postcount=1, For anyone who has a similiar problem do the following.
1) Make sure your computer recognizes your device by typing: fastboot devices
2) Unlock your bootloader (if you have not already done so): fastboot oem unlock
3) You will see a prompt on your device. This will wipe your entire device (including the /sdcard folder). Accept. Note: you use the volume keys to change the option and the power button to accept. You cannot use the touch screen.
4) Reboot by typing: fastboot reboot-bootloader
5) Flash the bootloader: fastboot flash bootloader bootloader-mako-makoz10o.img (or whatever the name of the bootloader image that you downloaded).
6) Reboot: fastboot reboot-bootloader
7) Flash the radio: fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1700.48.img (or whatever the name is of the radio image that you downloaded).
8) Reboot: fastboot reboot-bootloader
9) Flash the system partition: fastboot flash system system.img
Flash the factory images with the toolkit then flash a custom recovery and root
Sent from my Nexus 4 using Tapatalk
Boot your device into fastboot mode and then you can manually flash back to stock.
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Zehlek said:
Flash the factory images with the toolkit then flash a custom recovery and root
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
audit13 said:
Boot your device into fastboot mode and then you can manually flash back to stock.
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
Thanks, is there a way to backup my sd card before flashing back to stock?
tarroyo said:
Thanks, is there a way to backup my sd card before flashing back to stock?
Click to expand...
Click to collapse
Flash the system.img file only.
Sent with my Nexus® 10 minus 3
Problem solved!
I get remote : partition table doesn't exist.
I have been working on this all night. WIn Drivers for ADB, Fast boot, naked drivers, and on and on. Tried to push a ROM for CWM and round and round I go. Nothing works. The phone for lack of any other words seems to be dead except I can get flashboot to talk to it. ANy idea? Please?
williamsck said:
I get remote : partition table doesn't exist.
I have been working on this all night. WIn Drivers for ADB, Fast boot, naked drivers, and on and on. Tried to push a ROM for CWM and round and round I go. Nothing works. The phone for lack of any other words seems to be dead except I can get flashboot to talk to it. ANy idea? Please?
Click to expand...
Click to collapse
I got it!
First of all, I know that there are many people asking same thing. I have checked those threads and I guess I am just a little bit more clueless. Last time I was able to use my Nexus 10 was 3 months ago. Since then I tried to solve it many times, but no luck so far. I will try to explain some of the issues I'm experiencing, but I'm afraid I'm not too good with all the expressions people are using on this forum.
1. ADB vs Fastboot
I see this mentioned often and I don't know what exactly it means. It's amazing to me that I can't google it, I'm usually good with googling. I can see that my N10 is sometimes listed under ADB and sometimes under Fastboot devices but I have no idea what I did to change that. I do know that whatever I try to do at certain point, it's always in "wrong" mode, waiting for adb etc. So if someone can point me to a thorough explanation, a wiki or something, that would be very nice.
2. The Loop
I managed to get ClockworkMod v6.0.4.3 installed and it's this loop that device is now inside. I've tried pretty much all possible combinations, wiped both caches, did factory reset, rebooted to system/bootloader/recovery... nothing. Always ends up on same CM menu.
3. Android Toolkit
I have installed this on my computer and tried so many things that I forgot about all details. I tried flashing the big 400 MB stock image to the device, but haven't been successful (says waiting for ADB, even if the device WAS listed as ADB device before I started the procedure). I am also expecting to see the N10 as another "drive" from my desktop, if you know what I mean, so that I could copy files to it. However I don't see it that way, I only see it registered as a Nexus 10 device, like a mouse or any other non-drive device. Is this normal?
So what to do? Can anyone tell me in a simple way, because I am obviously stupid enough to find threads I've seen so far not clear enough. And I would actually think that my computer literacy level is rather high, I think that this Nexus 10 is the only thing that brought me to my knees in last 20 years of working with computers.
And when I say "simple wiki style" I'm thinking of something like this:
Ok. no links allowed, great. It's a redmondpie article named
/how-to-set-up-android-adb-and-fastboot-on-windows-tutorial/
This is easy enough for me... but do I assume correctly that all this has already been done with me installing Android Toolkit? If so, it uses a different path structure and I don't see all those folders...
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Sent from my Nexus 10 using Tapatalk
newellj79 said:
So u do have cmw installed, when u try to flash a ROM it just boots to recovery?
Click to expand...
Click to collapse
You mean flashing ROM only with CWM, not through android toolkit? Through CWM menu I have tried (many times):
- wipe data / factory reset
- wipe cache partition
- wipe dalwik cache
I don't see way to do anything with:
- install zip
- backup and restore
- mounts and storage
Rebooting menu items do following:
- Reboot system --> reboots to same CWM recovery menu
- Reboot to bootloader --> reboots to the stock bootloader "menu" where I can choose between Start, Power Off, Recovery mode (picking this will reboot to CWM recovery menu) and Restart bootloader (picking this will reboot to this same menu)
- Reboot recovery --> reboots to same CWM recovery menu
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
1 adb works only in os and recovery, fastboot works only in bootloader
2 it looks like your recovery is screwed up, flash this with fastboot
http://techerrata.com/file/twrp2/manta/openrecovery-twrp-2.6.3.1-manta.img
fastboot erase recovery
fastboot flash recovery nameofrecovery.img
3try not to use toolkits, you have a nexus, toolkits are more complicated than manual methods and you won't learn anything from it
Once you have recovery
Wipe all, then you will will need to use adb sideload to flash ROM as you have no ROM on emulated sdcard
Go to advanced menu
adb sideload
adb sideload nameofROM.zip
adb sideload gapps.zip
For more info on fastboot
http://forum.xda-developers.com/showthread.php?t=2277112
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The first part worked ok. The second part doesn't.
ADB sideload - I went there in the Nexus menu
adb sideload kitkat2501.zip
returns this:
* failed to write data 'protocol fault (no status)' *
If I do it without starting adb sideload on nexus, then it just says "error: closed", so it does recognize the change.
I downloaded the latest sdk tool, 64-bit, and the stock nexus 10 rom from 25th Janaury.
Let's do this, grab the latest stock for manta from here
https://developers.google.com/android/nexus/images
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
demkantor said:
Let's do this, grab the latest stock for manta from here
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
And extract and run the flashall.bat
This should bring you to the latest official software/firmware. Then with you up and running we can root and give you custom recovery,ROM,whatever
If you have an issues at all please copy and paste all input/output from cmd/terminal here
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You are a wizard. I got it all ok now and I added CWM to it, it was easy to root it from there.