Related
Hi guys. I have been trying to fix this problem for like 10 hours but I could never get it right.
Device status: Rooted, unlocked bootloader.
Currently my problem is that whenever I factory reset my device it goes back to CWM recovery. I tried using mskip toolkit and Wug toolkit to flash back to stock rom but it didn't work. The thing I realized is that I could never mount my sdcard from the CWM recovery.
Besides that, whenever I push some files into my sdcard through Windows and reboot my Nexus 7, the file gone missing. I also tried to install and uninstall app and it seems to be working at first, but it goes back to the default state after rebooting it.
By the way, I am able to fastboot it and enter CWM recovery and boot like normal, but could never edit anything on it, not even flashing.
Things I have done:
-Flash stock rom(full zip file) using mskip and wug toolkit.
-Flash stock rom part by part(boot,recovery,system,userdata)
-Boot image using TWRP and wipe data.
-Flash custom rom using toolkit(Bugless Beast).
-Downloaded twice for the stock rom and checked with md5sum.
Things going on now:
-Back to same state no matter what I do to the device.
Sorry for my English.
Anyone help please?
Hmm that is kind of weird, what system are u using? Windows Mac or Linux?
Try using Nexus 7 Toolkit 2.0, it works great in my case :s Restore to stock rom using it. Also check the console if there are any bug report.
Btw you could try to lock/unlock your bootloader as it wipe all user data at the same time
Good luck!
Sent from my Nexus 7 using xda premium
jamesst20 said:
Hmm that is kind of weird, what system are u using? Windows Mac or Linux?
Try using Nexus 7 Toolkit 2.0, it works great in my case :s Restore to stock rom using it. Also check the console if there are any bug report.
Btw you could try to lock/unlock your bootloader as it wipe all user data at the same time
Good luck!
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thanks for the reply! I have tried both mskip and Wug toolkit and it doesn't work.
The data inside the device is basically uneditable right now! No matter I delete or add in new files and reboot, files that deleted will be back while the files that I added in will be removed. Seriously I need some help, I'm unable to flash rom or do anything with it since I have unlocked the bootloader(and unable to lock it back) and warranty is voided.
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
StefanoRedi said:
Hi everybody!! I have a BIG issue: my nexus 4 is unlocked, with the CWM recovery and CyanogenMod 10.1 installed. Due to some technical problems, I decided to flash the factory rom again (following this guide http://forum.xda-developers.com/showthread.php?t=2010312) but I can't do it!! Indeed when I try to flash the factory rom the prompt says
file:could not allocate 544035848 bytes
error:cannot load system.img :not enough space
And when i checked the system capacity the result is that my system partition doesn't exist (as you can see on the pic attached)!
I wish to send my phone back to google with the RMA (it was delivered 7 days ago) but I'm not sure that the warranty is still valid (what do you think about that?). Indeed there is no OS now, and everything is unlocked.
Anybody could help me?
Thanks a lot!!
Click to expand...
Click to collapse
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
EvoXOhio said:
use the fastboot commands to erase system, boot, and data. then use flashboot to flash bootloader, then stock recovery, then stock system.
Click to expand...
Click to collapse
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
That sounds right but Fiona search to be safe. No reboots needed.
StefanoRedi said:
Thanks!! Just a couple of questions: 1. the prompt commands are "fastboot erase system" "fastboot erase boot" and "fastboot erase data", right? 2. Have I to reboot the system between every erase and every flash?
Click to expand...
Click to collapse
I tryed to do it without results. I attach the screen.
Have you some other advises? I really don't know what i can do it with my phone. If i send it back to google, do you think that they will check if my phone is locked/unlocked, with/without os, ecc? Because I'm afraid to have wasted my money!
Have you tried booting into recovery and wiping everything before flashing system? Also you're sure you have the right system.img? Maybe re-download the files from google and try again?
---------- Post added at 09:23 AM ---------- Previous post was at 09:22 AM ----------
also, do you have any nandroids or downloaded ROMs on the phone? If so, you could try flashing CWM, and then booting into it and restoring the nandroid or installing a ROM.
R: Cannot flash system.img, df shows no system partition
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
squalluca said:
We tried wiping everything trough fast boot, he does not have any nandroid backup and I think he tried to flash another ROM (cm) with no luck.
We downloaded the right images, we tried both 4.2.1 and JOP40D from the Google site and from the mirror that we found in some thread here on xda.
(I'm his friend and I was helping him via Skype, that's why I know these informations)
I think now we'll try to flash cwm and wipe everything trough it and install a stock ROM or a custom one.
Ty for the help.
Sent from my Nexus 4
Click to expand...
Click to collapse
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
R: Cannot flash system.img, df shows no system partition
That's what I think too... this error appeared before we tried any wipe/erase command trough fastboot... hope someone can help us in recrate the mount point for the system partition...
Sent from my Nexus 4
EvoXOhio said:
It really sounds like someone made a mistake and ran the wrong command and actually remove the /system partition. Not erased or formatted, but actually removed the mount point. I'm sure there is a way to recreate it, but I have no idea how.
Click to expand...
Click to collapse
Thanks guys! I really hope that someone knows how to recreate it and, if it's possibile, very soon, because the RMA expiration day is coming!!
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
USSENTERNCC1701E said:
This is generally to be avoided, but I think this may actually be a last resort situation. Download the full factory image extract down a few levels until you have flash-all.bat extracted, at that point you'll also see the radio, bootloader, an image zip, and some linux scripts. Make sure you've actually extracted them and that you aren't just looking in the zip. Run flash-all.bat Don't touch anything until it's done, if you disrupt the write to bootloader or possibly radio, you brick.
By the way, the factory image is here and you may need to use 7zip to extract it. 7zip will have shell integration, so just right click what you want, drop down to 7zip and extract to.
Also, you may be able to accomplish the same thing with:
Code:
fastboot -w update image-occam-jop40c.zip
so maybe try that first.
Click to expand...
Click to collapse
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
StefanoRedi said:
Fine, I will try when I come back home. Just a question: what do you think about the warranty? Do you think that google will check if the phone is unlocked and without os? It is better for me risk with the last suggested process and (maybe) brick the phone or send it back as it is now? It's because I'm just a beginner with mod, scripts, prompts, ecc..sorry!
Click to expand...
Click to collapse
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
EvoXOhio said:
The phone was damaged from user error. It is unethical and probably illegal to RMA it. Try to fix it yourself, and if you can't, man up and buy a new phone. RMAs are for faulty products, not products ruined by an inexperienced user doing something wrong.
Click to expand...
Click to collapse
You are completely right. I wrote that just because I messed up the phone (following guides, using toolkit, using cmd in a proper way) trying to fix it (from the first day it was impossible to call due to microphone/speaker software problem). And sometimes, while a was doing the same stuff that everybody do with good results, the phone didn't do what it was supposed to do. Consequently I wanted to RMA it because i think it's my fault (I know it and I admit it) but not completely. I really don't want to cheat anyone.
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
Make sure flash stock recovery and relock the device before sending it in.
EvoXOhio said:
Make sure flash stock recovery and relock the device before sending it in.
Click to expand...
Click to collapse
Of course! In theory it will not be a problem if there is the CWM recovery and if the phone it's unlucked (at least, I read that for Google and LG is not a problem), but I flashed the stock recovery and then I lucked the phone again. Thanks for your advises.
system.img cannot load, not enough space error
StefanoRedi said:
Well, I fixed it. I don't know the reason but the day after everything was fine (maybe it's because I erased everything from CWM; i wiped everything and then i wen on Mount and I erased everything). Btw, the day after I reflashed everything from prompt with the phone in fastboot and i flashed also system (the partition was "avaible" again); the .img flashed was the factory rom 4.2.0. Then I reboot it but the problem with microphone/speacker wasn't fixed; i updated to 4.2.1 and it still didn't work. Today I will call google to RMA it because now (just now) the phone is not working properly but not due to my errors. Thanks to everybody!!!! :laugh:
Click to expand...
Click to collapse
hey can anyone help me i have this error when i flash Stock 5.0.1 Lollipop, Kitkat flashing is working!
So I unlocked bootloader and flashed TWRP. Now I'm in TWRP but I don't see how to copy files from computer to device (internal SD or whatever)...?
Advanced > ADB Sideload
Then you use the "adb sideload" command from the computer to push a zip that gets automatically saved as sideload.zip and it gets installed.
It takes a bit for sideloading to start working, maybe 1 min or so, adb will say "device not found" but it will eventually work if wait long enough.
If you are not familiar with adb, you need to start reading about it.
Very good question, I've been having trouble with that myself as well. I managed to push it using adb commands but I guess there's an easier way.
But since I can't mount sd-card twrp nor Cwm, this seems like the only option.
Command is: adb push (name of file).zip (or any other file extension) /sdcard/(name if file).zip
Sent from my Nexus 4 using xda app-developers app
kwibis said:
Very good question, I've been having trouble with that myself as well. I managed to push it using adb commands but I guess there's an easier way.
But since I can't mount sd-card twrp nor Cwm, this seems like the only option.
Command is: adb push (name of file).zip (or any other file extension) /sdcard/(name if file).zip
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
I have an elementary grasp of adb now from unlocking the bootloader and flashing TWRP. Jesus christ though, I thought pure Google would be the most user friendly device to mod, but this is just silly...
Push sounds more friendly than sideload... So just to be clear, I can wipe (factory reset, cache, dalvik, system, internal), then push ROM + gapps to /sdcard/ while still in TWRP?
Thanks for your help.
.psd said:
I have an elementary grasp of adb now from unlocking the bootloader and flashing TWRP. Jesus christ though, I thought pure Google would be the most user friendly device to mod, but this is just silly...
Push sounds more friendly than sideload... So just to be clear, I can wipe (factory reset, cache, dalvik, system, internal), then push ROM + gapps to /sdcard/ while still in TWRP?
Thanks for your help.
Click to expand...
Click to collapse
Yeah, it's a bit weird. I hope someone that knows the solution will reply on this thread, or maybe I'll ask one day in the TWRP thread.
Before you wipe everything, see if the push command works when you're in twrp. For me it did. If it works, wipe your phone and push the rom and gapps to /sdcard/(name).zip yes. Make sure your path of the command window is in the folder where you've located the zip-files.
after a quick search I found out it's normal apparently. The nexus devices do not have an SD-card, only a folder called that way making it impossible to mount. Had the same issue with the Asus tablets.
http://forum.xda-developers.com/showthread.php?t=1916108&highlight=recovery+mount+sdcard
I guess I'm comfortable continuing to do it that way. I was able to push (and subsequently flash) a ROM and gapps last night. But Google should know how amazingly silly and frustrating it is that they haven't managed to make the internal mountable from recovery...
Bye bye external SD. You never know what you've got until it's gone...
The Nexus range is raw Android, so you need to know adb/fastboot inside out. Once you do it's easy but even easier is to make sure the files are on the phone BEFORE you go into recovery in the first place
kwibis said:
Very good question, I've been having trouble with that myself as well. I managed to push it using adb commands but I guess there's an easier way.
But since I can't mount sd-card twrp nor Cwm, this seems like the only option.
Command is: adb push (name of file).zip (or any other file extension) /sdcard/(name if file).zip
Click to expand...
Click to collapse
adb push/pull only work if the ROM is booted up. If for whatever reason your phone doesn't boot, e.g. you wiped System, you need to "adb sideload" a ROM while in TWRP. It's good to read ahead about "adb sideload" in case disaster strikes. Better yet, keep a handy ROM always somewhere under /sdcard, say a rooted stock ROM or any other favorite ROM. If you can't boot your phone, you can always go to TWRP, flash said backup ROM from /sdcard and you can be up and running in no time, at least you can make phone calls, etc.
The other thing that's good to get familiar with is nandroid backups from TWRP. Customize the ROM the way you like and when you are relatively happy take a backup and save it, it can be your go to image in case you mess up.
That or the factory Google image to flash via fastboot...
sirxdroid said:
adb push/pull only work if the ROM is booted up. If for whatever reason your phone doesn't boot, e.g. you wiped System, you need to "adb sideload" a ROM while in TWRP. It's good to read ahead about "adb sideload" in case disaster strikes. Better yet, keep a handy ROM always somewhere under /sdcard, say a rooted stock ROM or any other favorite ROM. If you can't boot your phone, you can always go to TWRP, flash said backup ROM from /sdcard and you can be up and running in no time, at least you can make phone calls, etc.
The other thing that's good to get familiar with is nandroid backups from TWRP. Customize the ROM the way you like and when you are relatively happy take a backup and save it, it can be your go to image in case you mess up.
Click to expand...
Click to collapse
No need for sideload, as soon as you enter twrp or cwm, the computer recognizes it as an adb device and thus things can be pushed to sd-card. Sideload is another possibility, however I've not used it as it takes a long time.
Also nandroids are nice when they are ON your sd-card, but if you decide to cleanwipe your phone including that partition it's not there anymore, hence this thread.
---------- Post added at 06:39 PM ---------- Previous post was at 06:38 PM ----------
EddyOS said:
That or the factory Google image to flash via fastboot...
Click to expand...
Click to collapse
Yes exactly, that's the last way out if you screw everything else up lol.
kwibis said:
No need for sideload, as soon as you enter twrp or cwm, the computer recognizes it as an adb device and thus things can be pushed to sd-card.
Click to expand...
Click to collapse
Wow, it does work, thanks for the tip! It never worked for me on an HTC phone so I thought it was not supposed to work.
I was gladly surprised as well when I found out
EddyOS said:
The Nexus range is raw Android, so you need to know adb/fastboot inside out. Once you do it's easy but even easier is to make sure the files are on the phone BEFORE you go into recovery in the first place
Click to expand...
Click to collapse
Well no offense to Google or people with the time to make thousands of posts in this forum, but some of us aren't interested in learning "adb/fastboot inside and out", lol...
And ya, the basic commands are relatively "easy" (once you read a hundred different newb guides and power through your inevitable mistakes). But like kwibis was saying, the purpose of this thread stems from the fact that files stored on the device are wiped in recovery immediately before installing a new ROM (factory reset, wipe cache, dalvik, system, internal)...
EDIT: unless you don't need to wipe the internal storage...? In which case you're right about copying files before booting recovery, and this whole thread is null. :|
Don't wipe internal, no need to when switching ROMs.
In fact, factory reset wipes your caches too, and ROMs typically wipe system, so factory reset is all you need. It's all I've used since reading that and I've never had a problem. It would be a rare case that you would actually have to wipe internal.
Sent from an N4 blessed with AOKP and sanctified by Faux123!
JaylanPHNX said:
In fact, factory reset wipes your caches too, and ROMs typically wipe system, so factory reset is all you need. It's all I've used since reading that and I've never had a problem.
Click to expand...
Click to collapse
Great tip!
Yes that is true, however I remember from the Crespo that wiping sd-card would sometimes remove some bugs. Have not had it on the mako though.
Sent from my Nexus 4 using xda app-developers app
kwibis said:
Yes that is true, however I remember from the Crespo that wiping sd-card would sometimes remove some bugs. Have not had it on the mako though.
Click to expand...
Click to collapse
Even so, you don't need to delete everything from the sdcard, e.g. music, photos, backups, etc. You can select which folders you want deleted, e.g Android, other (dot) folders, etc. Keeping your media should not affect any apps.
kwibis said:
I was gladly surprised as well when I found out
Click to expand...
Click to collapse
I am unhappily not surprised that I cannot get adb to work when the recovery loads and it only works when the rom is booted up. Perhaps you need an insecure boot?
Hi everyone,
So I have never ran across this issue before. I haven't had any problems with my device and yesterday I wanted to test out the new Jelly Bam update rom from their site. The rom would not boot pasted the "Google" spash screen so I rebooted in to recovery and did a full wipe and restored via backup to my previous rom just like normal. Well then I noticed that normally when I connect my phone to my computer I see my internal memory drive pop up which I am able to click on and then access my files, but this time when I accessed it I have a hand full or folders like 0, twrp, android, etc and I had to double click on o folder to access my memory with all my files. I thought that was weird so I went on about my day. Later I tried to do a fresh install of my current rom PACman but even after doing a fresh install the phone will not boot passed the Google spash screen, and now twrp doesn't even see my backup file because its being directed to this new partition with all the folders I was talking about. I even tried using the file manager in twrp to move the backup to that twrp folder but twrp doesn't even see it.
So as of right now I can get in to twrp but I can not boot my device pasted the google splash screen. I also can't access my memory through my pc since nexus does not allow it with twrp. What do I do? My thoughts are that something got screwed up with the partitions when I flashed the Jelly Bam rom so I will need to go back to stock, does that sound about right? I was thinking of following these instructions to go back to stock and then move on from there, any thoughts or alternatives? http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Thank you
Trying this method to return to stock: http://www.wugfresh.com/nrt/
If no one has any input I will assume I am following the right path.
I flashed factory images a couple weeks ago and in order for TWRP to see the nandroids I copied back to my phone I put them in the following path: /sdcard/TWRP/BACKUPS/stringofrandomnumbersandletters/
Are your TWRP backups in a similar location?
If you've decided to go back to stock, I'd suggest using the following guide by efrant... http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda app-developers app
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
It looks like twrp is now looking at my twrp folder in my sd card 1 not sd card 0 where I have had my backups and all my files. After trying again, I moved the TWRP backup to the sd card 1 twrp folder, twrp recognized it and I restored from backup....but when I reboot I am still stuck on the Google screen. Not sure what to do.
Underground_XI said:
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Since I can't move anything to my memory, any suggestions?
If you've got adb and the proper drivers installed on your PC you could try:
Code:
adb push ROM.zip /sdcard/ROM.zip
from the command prompt. Obviously use the name of the actual ROM.
Edit: ignore that, just read the post where you managed to restore! D'oh!
Have you tried clearing both caches?
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
synergeticink said:
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
Click to expand...
Click to collapse
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that's were I am stuck right now. I am not a pro at using adb commands, never used it till I got my nexus 4. Right now when I launch the cmd it shows "C:\Users\My User Name\Desktop>", not sure where to go next. I guess I am not sure what I should be pushing at this point either.
Oops...it seems I was editing my post at the same time you were responding to it...take a look at my previous response again
I'm fairly new around here but I can help with the adb commands if you need. Hang in there
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I tried wiping cache/dalvik/system/factory reset and then both restoring from backup or flashing the latest PACman rom which is in my sd card. Right now I am reading the http://forum.xda-developers.com/showthread.php?t=2018179 guide to see if I can use adb to flash my rom or another recovery. Makes sense if its the recovery not letting me flash anything, but i'm not a dev. At least I am able to get in to recovery to begin with, good sign I guess.
If you can boot into bootloader and recovery there are many options to help get you up and running again. That guide by Jubakuba is really good but if wiping and restoring your backup from within TWRP didn't work I would highly suggest reading efrant's guide on returning to stock...I posted the link in an earlier reply.
Sent from my Nexus 4 using xda app-developers app
I was able to flash cwm using adb, now trying to do a fresh install
Nope, doing a fresh install didn't work. Now its time to restore to stock. ......
One problem:
"
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;"
UPDATE; Got it, instructions were not clear.
synergeticink said:
UPDATE; Got it, instructions were not clear.
Click to expand...
Click to collapse
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its weird adb will not work on the computer unless the files are in the platform-tools folder in androi sdk. trial and error, just finished flashing system....
should I do this command, I really don't want to lose my stuff:
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Well, I didn't and finished the process...did a reboot when I was done...now its on the Google screen...just waiting....I'm seeing a Nexus X splash screen!!!...
Update: Its taking a very long time, hopefully it works...going to give it another 10 mins
And we have BOOT... thank you everyone! Now I have to root this sucker!
Hopefully this helps people in my situation.
So on the first day of having my nexus 7 i found a way to have no OS and 0MB internal storage showing in TWRP. Yah i suck.
I tried tons of things but knew a system image was needed.
HOW: I was about to flash the superuser root for 4.3 newly released and forgot to put it on nexus so i then proceeded to exit TWRP, however upon exiting TWRP the recovery detected i havent installed supersu and asked do i want to install superuser? I though why the hell not!
I confirmed to install superuser and then tried to reboot but for 20 minutes device could not boot. TWRP showed 0MB internal storage and pushing adb files in this state yielded nothing as there was no directory
This is how i managed to have a working tablet again
1. FORMAT DATA in TWRP - after doing this your internal storage should be back and not show 0MB
2. reboot to the bootloader
3. On your computer download this file kindly given to us by phuduong and uploaded by Nburnes
https://mega.co.nz/#!PBIiEbBJ!bKpdHxegOVlde12nsu_ulEyRq7UsANLLQab1IZjLIGc
Credit to Nburnes http://forum.xda-developers.com/member.php?u=2918596[/QUOTE]
4. Once downloaded move that system.img file to your adb directory
5. With you nexus 7 in the bootloader, adb open, and file downloaded copy and paste this command into adb terminal
fastboot flash system system.img
6. Now you have an OS but it still would loop and wouldnt start
7. Boot into recovery and Format Data again, because for me 0MB interal storage was back again
8. Then Factory Reset
FINALLY YOUR DEVICE SHOULD BE BACK TO ITS ORIGINAL STATE!!!!!
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
plbelanger said:
Is that the factory image? Have you tried going from unlocked bootloader & rooted back to factory using that image?
Click to expand...
Click to collapse
Google has yet to release the official factory image for the new N7. However, a kind user was gracious enough to make their own. It is likely to be almost identical to what Google will eventually release and should work the same way.
Thank you! Thank you!
good stuff OP. glad you got it working again
You all are life savers! 1000X Thanks!
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
petersellers said:
I tried running through this, but it didn't work for me. I think my situation is different though because I tried to install a factory image for the 2012 nexus, and during part of that process I ran the "flash-all" script which starts by deleting boot, cache, recovery, userdata, and system.
I think deleting boot screwed me up, because even though I can go into recovery now after reinstalling twrp and I can restore my system using system.img, I still can't boot (get stuck on the google logo). Any way to fix that?
Click to expand...
Click to collapse
So you first tried to restore the OLD nexus 7 factory image? Probably gonna have to wait for factory image or exchange yours
Sent from my Nexus 7 using xda app-developers app
jporter396 said:
So you first tried to restore from the OLD Nexus 7 Image?????
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
THANK YOU!!!
This worked perfectly! I had a wiped system folder (no ROM), and obviously no USB debugging enabled. And with the lack of a factory image, I've been counting seconds to seeing somebody post this!
Just follow the instructions carefully. Thank you guys!
petersellers said:
Yes, I tried to restore from the old image. Obviously fastboot wont let you install the old image, but I didn't realize that until boot, system, cache, etc. were deleted
Click to expand...
Click to collapse
You can flash old and new image through fastboot. I did 2 times ^_^
This is boot.img for who need
BOOT.IMG HERE
It gives me a fail when I try to wipe data.
Edit: never mind
jarjar124 said:
It gives me a fail when I try to wipe data.
Edit: never mind
Click to expand...
Click to collapse
How did you fix it? I still cant wipe data.
Balsta said:
How did you fix it? I still cant wipe data.
Click to expand...
Click to collapse
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
jporter396 said:
Have you formatted first?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can't, get an error with that too
Sent from my SCH-I545 using Tapatalk 4 Beta
OP and nburnes saved my butt!
I did this and now it seems my device is booting and it shows up as N7 when I attach it to my PC. But the display shows nothing at all. It just goes blank after the Google screen. Any ideas?
After flashing everything I could think of and banging my head and the device against the wall for two hours, I finally got it to work. Not sure how exactly but the last thing I did was reflashing bootloader. So if anyone has the same problem, try that.
Thank you.
Note:
Give step 6 a little time be patient.
All main JSS15J .IMGS here: http://forum.xda-developers.com/showthread.php?t=2381438
Glad this helped some of you guys!