Related
As a disclaimer, I have already searched and found some people with the same issue. What I haven't found is someone that arrived at this problem in the same way I did. I am scared ****less of bricking my phone (and hope I haven't already). So at this point, I am looking for some help to figure out my best course of action.
I recently updated to JF1.5 using his updater app, and everything worked. Today when I received my new SDcard, I started the process to get apps on my SD following this tutorial: http://forum.xda-developers.com/showthread.php?t=512743
I got as far as partitioning my card using the Apps2SD application as described, doing everything the tutorial says. I began the partition on my phone, and let it sit.....and sit, and sit. It sat frozen on the partitioning screen (the one with the slider to select the size) for almost an hour before i pulled the battery. I selected 1444mb for the ext2 after reading that it was not a good idea to go higher than 1500mb.
Now, as stated the phone boots to the G1 splash and goes nowhere. I am however still able to boot in recovery mode using Home+Power. Interestingly, it says at the top:
"Android system recovery utility
Build: JFv1.42"
Not sure if this means that 1.5 didn't install correctly or what, but that's what it says.
I have no idea what to do at this point, and am scared to go on without some candid advice. Sorry for the noobishness of my description - if there is anything else needed to give accurate advice please let me know. Also thanks in advance for any help I can get!
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
meoshe said:
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
Click to expand...
Click to collapse
Thanks for the response. I'll have to find a way to get that image onto my SD card. I just bought a 16BG card and that was the card I was using when I ran into this problem.....oh wait a sec....
I'm assuming that the JF1.51 update.zip will still be on my old 1GB card from when I updated to JF1.51 via his updater app last week? If so then my life will be a lot easier, and I'll just swap back to that card, boot up in Recovery, flash from update.zip, and that should be it?
Just want to make sure before I put that old card back in and try to flash....
try wiping before you update? Also to mount your SDcard (if you need to) press alt-x in recovery (or in adb shell) and type
Code:
echo /dev/blockl/mmdblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
x2 that's what i had to do since my computer stopped reading sd cards.
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
Abolfazl said:
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
Click to expand...
Click to collapse
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
t3mp3st said:
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
Click to expand...
Click to collapse
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Abolfazl said:
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Click to expand...
Click to collapse
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
t3mp3st said:
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
Click to expand...
Click to collapse
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
t3mp3st said:
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
Click to expand...
Click to collapse
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
alritewhadeva said:
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
Click to expand...
Click to collapse
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
t3mp3st said:
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
Click to expand...
Click to collapse
Cool, Best of Luck with the flashing
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Alright...I successfully partitioned my card, flashed with CM 3.4, but now when I try this instruction to install the new recovery, i get this error msg in Terminal:
error writing recovery: Permission denied
Any ideas?
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
meoshe said:
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
I did not enter the su, I will try that now thanks. In the mean time I also performed this step:
13. My /system/sd is read only and/or didn't upgrade to ext3!
Your filesystem is probably corrupt. Boot into recovery and open a console. Run "mount /system" then "/system/bin/e2fsck /dev/block/mmcblk0p2" and fix your filesystem. Reboot.
from: http://forum.xda-developers.com/showthread.php?t=518851
So I hope that didn't hurt anything...ill try with the su now. Thanks!
edit: out of curiosity, what does the "su" stand for? I feel if I know this it may help me to remember to enter it before any commands.
edit #2: does it stand for "Super User" to allow super user permissions? I gathered this after entering SU prompted me to allow superuser access
New recovery.img successfully installed! Thanks again to everyone that helped me with this.
I know I can transfer apps to SD easily from recovery now, but is there also a similar way to do it from the phone (or do they install to the SDcard by default now?)
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
dynamisoz said:
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
Click to expand...
Click to collapse
Hey there, with the help from everyone in this thread, along with the partitioning instructions using Ubuntu (if you still need to partition your card) from tubaking182 found here: http://forum.xda-developers.com/showthread.php?t=523648, It was great.
I just finished flashing with that ROM and then installing CM's recovery image (which is AWESOME...trackball selection, Apps2SD in one click)
I HIGHLY recommend it. If you have any problems, I'm sure you'll find most of the answers in this thread. If not, try PMing one of the helpful respondents, or I may be of SOME help with some minor questions or assurances.
I managed to wipe data/factory reset but on dalvik-cache and SD: ext partition, it says theres an error and I have to run both of them via adb. This is my first time actually wiping and the only video I could find was for a mytouch3g. Any help would be grateful.
Does anyone know? Im trying to get his wiped and install a custom ROM asap because Ive already had my phone out of commission for a few hours now.
a bidet may help.
actually I read on these forums that even though you get the error on dalvik that it wiped successfully completed. don't know about the other.
Sent from my HERO200 using the XDA mobile application powered by Tapatalk
flash a new recovery image
works everytime
PawkChop said:
Having trouble wiping
Click to expand...
Click to collapse
Sounds like a personal problem.
Just kidding, try flashing another one like was already suggested.
Im currently on version 1.5.2 and I got it from a guide I followed earlier to root my phone. I dont know where I'd get another one from though
The guide for rooting in the sticky is the exact one I followed and that brings the version I have. Unless Im not looking in the right place. Im sorry that Im a total noob at this, just trying to finally use some custom stuff on my phone.
http://rapidshare.com/files/360288584/recovery-RA-heroc-v1.6.2.img
Thank you very much. Now this is where its get even noobier. Where exactly do I put the file. Ive never flashed a ROM or a recovery image unless that guide involved it so Im kinda at a loss here.
I sent you a PM
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
PawkChop said:
If anyone else could help, when I run the code in the terminal in order to flash the newer recovery image, it says that there isnt a recovery partition.
Click to expand...
Click to collapse
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
HeroMeng said:
This is how you do it. Put the recovery on the root of your SD (name it recovery.img for easiness and laziness) then eject the phone and run these commands:
Code:
adb shell
cd /sdcard
flash_image recovery recovery.img
reboot recovery
Done.
Also, if you're having trouble wiping, check this out: http://www.youtube.com/watch?v=PZeJZs2fdYo
Click to expand...
Click to collapse
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
PawkChop said:
Haha I will check out those wipes...
Anyways, im sorry for being a complete noob, but where do I input those commands. In command propmt? cause if so it doesnt work
Click to expand...
Click to collapse
In ADB. If it shows a $ sign after you type adb shell, then type su. That might be your problem.
I have been trying for a week now to restore a nook color back to stock with no avail. When I started there was no boot image or stock recovery and it would only boot from a CWR sd card but not mount or read the sd card to install any zip files Now i have it booting with the stock boot image but only to the "n" screen and no further. I have tried the factory recovery and reset but get nothing. I have a PC with a working ADB install but am unable to "push" the system.img to the sd card or anywhere for that matter and then dd it to the correct block on the internal memory. I am also unable to boot CM7 from the sd card because it freezes during the install. So basically what I'm asking for, is help fixing this darn thing cause I'm tired of it kicking my ass. thank you in advance for the info.
Sounds like your emmc partitions are messed up. Go to my partition repair thread linked in my signature. But if you cannot flash any zips, my repairs will not work. Try using my CWM bootable card from my tips thread also linked in my signature. Put the repair zips on the boot card before you boot.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
leapinlar said:
Sounds like your emmc partitions are messed up. Go to my partition repair thread linked in my signature. But if you cannot flash any zips, my repairs will not work. Try using my CWM bootable card from my tips thread also linked in my signature. Put the repair zips on the boot card before you boot.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
I will try both when i get home from work and let you know how it works. Thanks.
steve_o2291 said:
I will try both when i get home from work and let you know how it works. Thanks.
Click to expand...
Click to collapse
ok so after reading your links i have tried both of those methods already and neither of them works. I am beginning to wonder if i don't just have a group of six bad sd cards. They will boot CWR and begin the install of CM7 but thats as far as they get. I have tried everything I can find on forums and nothing works so far. If i could just get the system.img pushed with adb then i think that would get it but it just won't work.
I have also read about the system not loading if the serial number is not on it but I have done some file searching and found that it is in place so i don't think thats the prob. If you could think of anything different that would be awesome but I think I'm about to the point of having to bring it to B&N for service or just replace it.
Is there a place i could put the system image for the factory reset to take care of the install on its own.
steve_o2291 said:
Is there a place i could put the system image for the factory reset to take care of the install on its own.
Click to expand...
Click to collapse
Go to my tips thread and I have a new section about 8 failed boots. But you need the stock recovery on /boot for it to work. I know you cannot flash my stock recovery zip, but you could open the zip and extract the uRecImg and uRecRam and push them with adb to /boot (mount /dev/block/mmcblk0p1 as /boot first). Then follow my guide on how to do the 8 failed boots. That should wipe your device (including media) and install the original stock on your system.
leapinlar said:
Go to my tips thread and I have a new section about 8 failed boots. But you need the stock recovery on /boot for it to work. I know you cannot flash my stock recovery zip, but you could open the zip and extract the uRecImg and uRecRam and push them with adb to /boot (mount /dev/block/mmcblk0p1 as /boot first). Then follow my guide on how to do the 8 failed boots. That should wipe your device (including media) and install the original stock on your system.
Click to expand...
Click to collapse
Ive already got the stock recovery on /boot but 8 failed boots still does nothing because i have system.img for it to recover. I have all the partitions formatted the way they are supposed to be with fdisk but i still can't push the system.img to sdcard because it can't find it and if i try to put it on the nook i either get a protocol error or not enough room on the device error.
steve_o2291 said:
Ive already got the stock recovery on /boot but 8 failed boots still does nothing because i have system.img for it to recover.
Click to expand...
Click to collapse
I don't understand what you mean, you 'have system.img for it to recover'. The 8 failed boot uses factory.zip in partition 3 and if it enters the process (via stock recovery), it clears data and flashes that.
leapinlar said:
I don't understand what you mean, you 'have system.img for it to recover'. The 8 failed boot uses factory.zip in partition 3 and if it enters the process (via stock recovery), it clears data and flashes that.
Click to expand...
Click to collapse
I didn't realize i had to have facotry.zip on p3. I am going to try to dd it there and see what it does from there
Ok just tried like that and still get the install failed screen.
steve_o2291 said:
I didn't realize i had to have facotry.zip on p3. I am going to try to dd it there and see what it does from there
Ok just tried like that and still get the install failed screen.
Click to expand...
Click to collapse
Where did you get your factory.zip? Did you just rename a stock zip? It looks the same but I'm not sure everything is. When it says install failed, did the recovery start and fail or did it say that right off? Are you sure the recovery you used is the real stock recovery? You cannot just remove kernel-recovery and ramdisk-recovery from the stock zip and push those as uRecImg and uRecRam. Those get patched as the rom installs. Take the ones from my zip and push them. They are the patched versions.
You say you dd it but I hope you mean push to the mounted partition.
leapinlar said:
Where did you get your factory.zip? Did you just rename a stock zip? It looks the same but I'm not sure everything is. When it says install failed, did the recovery start and fail or did it say that right off? Are you sure the recovery you used is the real stock recovery? You cannot just remove kernel-recovery and ramdisk-recovery from the stock zip and push those as uRecImg and uRecRam. Those get patched as the rom installs. Take the ones from my zip and push them. They are the patched versions.
You say you dd it but I hope you mean push to the mounted partition.
Click to expand...
Click to collapse
I am unable to mount /dev/block/mmcblk0p1 in shell with a /boot directory. gives me a "Device or resource busy". so i just pushed the recovery files to /boot with
"adb push XXXX /boot"
and yes the recovery starts to load then fails
If i do
adb mount /boot
I get the help menu for a wrong entry
and i used the files from your download for the factory recovery
steve_o2291 said:
I am unable to mount /dev/block/mmcblk0p1 in shell with a /boot directory. gives me a "Device or resource busy". so i just pushed the recovery files to /boot with
"adb push XXXX /boot"
and yes the recovery starts to load then fails
If i do
adb mount /boot
I get the help menu for a wrong entry
Click to expand...
Click to collapse
Boot must already be mounted by CWM.
Just do an 'adb mount' command and it will tell you the things already mounted.
As for dd'ing the system.img to p5, can't you just dd it with adb from your PC?
And the factory.zip? You pushed that to p3?
leapinlar said:
Boot must already be mounted by CWM.
Just do an 'adb mount' command and it will tell you the things already mounted.
As for dd'ing the system.img to p5, can't you just dd it with adb from your PC?
And the factory.zip? You pushed that to p3?
Click to expand...
Click to collapse
yes i pushed factory.zip to p3
as for dd'ing system.img to p5 with adb i have to do dd with a shell command and i errors out when i try to push it data so i can't dd it to p5
this would be a lot easier if the damn sd card would work. I have no clue why it isn't because it worked fine until it crashed
Try formatting the SD with an SD formatting program (in a USB card reader, not your PC's internal slot). Sometimes SDs formatted with PCs are not readable in the nook. Search the net for one.
leapinlar said:
Try formatting the SD with an SD formatting program (in a USB card reader, not your PC's internal slot). Sometimes SDs formatted with PCs are not readable in the nook. Search the net for one.
Click to expand...
Click to collapse
Already did that several times with multiple cards on different machines. One with windows the other a mac
One final suggestion. Use my CWM SD (version 5.5.0.4) since it has the option of flashing things from internal memory.
Do an 'adb mount' to verify that p8 is mounted. If it isn't, mount it. Then push the zips that you want to flash there. Then the new CWM can flash from there.
Tried that just now and 5.5.0.4 tells me no zip found. I guess this is something that'll have to be done by a professional. After a week of trying and trying again I don't think Im going to be able to do it because I've tried everything i can find on the net and nothing works except for get the factory boot image back in place and getting the factory recovery to start but won't install anything. The factory reset also starts and erases all data but won't still only boots to the "n" screen. thanks for the help
So I downloaded new kernels and CM10 for my newly rooted N4. I did a backup before flashing the kernel and didn't pay attention to the error message saying cache was not found or whatever. But the kernel flashed fine and it booted up, nothing out of the whack. When I went back to flash CM10 it said the MD5 sum didn't match so the flashing processes didn't finish. Since my backup was ****ed up and the MD5 didn't match I couldn't restore the system either. Device will boot and will go into fastboot and recovery. Currently using CWM. If I turn on the device normally it will stay on the GOOGLE screen and it will not go into the boot screen. What do?
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
El Daddy said:
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
Click to expand...
Click to collapse
The CM10 zip itself is bad. How can I get another one on the phone? Or can I flash the CM zip without the file being on the phone? Thanks
Also, the error message popped up when flashing the CM zip was set_perm: some changes failed
E: Error in /sdcard/0/cmblahblahc zip
(status 7)
installation aborted
Should I turn off the signature verification anyway?
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
El Daddy said:
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
3 years of rooting and flashing stuff on 3 of my previous phones, there wasn't a time when I had to do this, or had to ask for help. Damn it.
Could you be a little more detailed in how do I go about doing so? As you can see my post count I am a bit of a noob Despite those 3 years. I just don't wanna mess up again, you know?
Thanks for everything dude
What screen should my phone be on? Just type that into the command prompt and it should work?
_thunderchild_ said:
What screen should my phone be on? Just type that into the command prompt and it should work?
Click to expand...
Click to collapse
Sorry I was out and about the past few hours.
You want to be in recovery. Custom recoveries allow you to use adb.
Rename the ROM something easy like CMrom.zip
Then put the CMrom.zip in the same location as adb on your computer.
Open the command window from that directory. (hold shift and right click; then choose open command window here)
Type the command: adb push CMrom.zip /sdcard/
It will push the file to the root of /sdcard/
Then you can flash it.
If that fails, use toolkit to download factory image and flash it through fastboot.
Oh man you guys saved my life. I cannot thank you guys enough. You won't believe how happy I was when I saw the bootscreen. Glad that was dealt with. Again thanks guys
Hey everyone I don't know if this is the right place to be posting this but I had the same problem as OP a few hours ago. I flashed LiquidROM and it got stuck on a boot loop. Needless to say, I panicked and used the adb push method since I decided to delete my AOKP ROM from my folder. Anyway, while panicking what I did was is before flashing, I backed up my entire SD card onto my laptop as ADB backup wasn't working and I pushed the entire folder using "adb push sdcard /sdcard/. Next thing I'm in recovery (CWM) and when I go through the flash from sdcard option, usually there were 3 options name 0/ and 2 others, however since I pushed the sdcard folder to /sdcard/ I get a 0/ at the top of the list which is where I would usually go but then underneath that I get all the folders I pushed! Is there any way to sort this out? I could attach pictures at some point for those of you who find it hard to picture what I'm describing Thanks in advance for any help!
Edit: just to add a couple of other things, my NANdroid had a checksum error so I cannot revert to stock without having to manually flash it which I cannot do at the moment due to a lack of WiFi, is there any way to sort this out? And the other thing was that for some reason sdcard cannot be unmounted at all in cwm, is it meant to be like that or am I missing something? Afaik its supposed to toggle.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
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!