Database Users

Stuck at G1 Splash (Help Please)

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.

Status 7

I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance

I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.

z1gackly said:
I think you will hopefully get more joy posting in the Q&A section.
I have read that it can be fixed by fastbooting stock and then re-rooting though. If you can make backups first, you should, because this will wipe everything.
Click to expand...
Click to collapse
what ive been doing is not making any backups (nothing important to save) and just using nexus toolkit to flash back stock and starting over and trying new way every time
still nothing though after about the 20th time

No idea then sorry. Stick with rooted stock?

z1gackly said:
No idea then sorry. Stick with rooted stock?
Click to expand...
Click to collapse
i think I might have to, ive never had any issues with custom roms (to speak of)
oh well, at least im happy with stock, i just love miui.
anyone else have answers please chip in, i give thanks!

harecurtis said:
I couldnt find any fix or helpful answers elsewhere on the web
Many of you are aware of the status 7 installation abort when trying to install a new rom
Ive been tinkering since last night trying to get miui 2.10.12 on my nexus 7 and every time I get a "Installation Abort (Status 7)
how do I get it to finish installation?
ive tried with multiple roms, CM10, MIUI, Kang all have same result
I have clockwork mod installed, from rom manager
I made sure I wipe data and cache and also davlik cache
any suggestions?
and i thank everyone in advance
Click to expand...
Click to collapse
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store

joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
give me 5 minutes, while i try your method.

harecurtis said:
give me 5 minutes, while i try your method.
Click to expand...
Click to collapse
joedoe said:
You're using a wrong recovery. Install TWRP recovery using Goo Manager. Get it from Google Play Store
Click to expand...
Click to collapse
its a no go

anyone else wanna help me?
ive tried almost everything:/

download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.

ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"

harecurtis said:
ill try this in just a few minutes as im flashing stock as we speak and "starting fresh"
Click to expand...
Click to collapse
If you're going that route.. you might as well just use fastboot to reflash recovery instead of the app.
Download the same image i linked to earily. While in the bootloader issue this command
Code:
fastboot flash recovery name-of-recovery.img
Make sure you have the Command Prompt in the same directory as the recovery image.
So say its in your downloads folder on your computer open CMD and cd to that directory.
Code:
cd C:\Users\Name\Downloads
Or just open yoru downloads folder and Shift + Right click and select "open command window here" then issue the fastboot command.

ÜBER™ said:
download TWRP for the Nexus 7 (grouper) Here : http://teamw.in/project/twrp2/103
Since your rooted you can use a simple app to flash the Image. Download and install the free app here http://forum.xda-developers.com/showthread.php?t=1790150&highlight=flash+gui
Open the free app and select the option for Recovery Image. Hit Browse and find the recovery image you downloaded and select it.Once finished hit flash image. It will ask you to confirm this image is a recovery image. Hit yes and it'll flash.
Then reboot to recovery, you can do this by using Terminal Emulator from the market issue this command
Code:
su *hit enter*
adb reboot recovery
If that doesnt work.. remove "adb" I forget if you need it or not :S
This should put you into TWRP Recovery.. go ahead and flash your ROM. Make sure you follow the proper procedure. I recommend this
1.Wipe data/Factory Reset
2. Wipe Cache Partition
3.Wipe Dalvik Cache
4. Format /System
then proceed to flash the ROM and Gapps. and Reboot.
Click to expand...
Click to collapse
didnt work(

harecurtis said:
didnt work(
Click to expand...
Click to collapse
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??

ÜBER™ said:
?? Is your bootloader unlocked? You are rooted still correct? I dont see how your even rooting if you dont flash a Superuser package with recovery??
Click to expand...
Click to collapse
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3

harecurtis said:
yes my bootloader is unlocked, and I rooted as well
what Im using is wugfresh nexus root toolkit 1.5.3
Click to expand...
Click to collapse
Stop... dont use that.. -_-. Do it manually..

ÜBER™ said:
Stop... dont use that.. -_-. Do it manually..
Click to expand...
Click to collapse
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!

harecurtis said:
okay, can you send me a lint to a post that I can manually do it?
and thanks so much!
Click to expand...
Click to collapse
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.

ÜBER™ said:
Ill write you up a quick tutorial.
First download this zip it contains adb and its .dll's needed to be executed and fastboot.exe for flashing
http://db.tt/EOwGUAPV
Unzip it and put that TWRP image in the same folder.
Then in that folder Shift + Right click and select open command prompt here.
Then type
Code:
adb reboot bootloader
This will boot you into the bootloader. Once in the bootloader do this command
Code:
fastboot flash recovery name-of-recovery.img
Hopefully your smart enough to realize that means type in the name of the recovery not exactly what that says.. for instance openrecovery-twrp... etc etc.
Then once its finished writing the recovery hit the volume up until the "Start" Says Recovery Mode. Then hit the power button. You should now be booting in the TWRP. Then flash your ROM.
Click to expand...
Click to collapse
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?

harecurtis said:
thanks
ill do that in a few minutes, im in the middle of trying another process, and if it fails ill try your method.
and should i re lock my bootloader before i try your method, or can i just keep it unlocked?
Click to expand...
Click to collapse
Keep it unlocked.... otherwise you'll have to re unlock it...

[Q] Soft Brick

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

[Q] Nexus 4 No OS. Only fastboot [SOLVED]

I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!

How did you wipe system within CWM?
But since you say you wiped internal partitions too, it seems to me that you wiped your internal emulated sdcard... so I think your only option now is to flash stock images again... Read this: http://forum.xda-developers.com/showthread.php?t=2010312

If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/

Thanks guys. Found a solution.
Flashed TWRP and sideloaded the ROM file. And flashed it.
Earlier the same process with CWM was not successful. Now the phone is loaded with PA ROM!
Thanks guys! and can u point me to the google stock images??

njarun said:
Thanks guys! and can u point me to the google stock images??
Click to expand...
Click to collapse
Glad you solved it
Here are the stock OTA and images from google and mirrored http://forum.xda-developers.com/showthread.php?t=1971169

My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?

mrjoeltan said:
My dad said he knew how to fix this, and wiped my system, thats all, and now I can't boot. Any help on this?
Click to expand...
Click to collapse
wiped /system? have you tried simple re-flashing your ROM from the .zip ?

no worry... download the nexus 4 twrp latest img from their site, and flash it to your N4
what you needed:
twrp img file
some n4 rom
adb and fastboot
instructions:
boot to fastboot, vol key down + powerbutton when n4 is off.
on your comp, , dos/terminal - fastboot flash recovery twrp.img
reboot in recovery
select the adb side load from advanced tab in the twrp.
on your comp - adb sideload rom.zip
everything done....reboot phone.
Sent from my Nexus 4 using xda premium

I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.

blackcatvn said:
I have a same problem, but when i try to flash a Rom, it`s fail and said that no partition, how can i fix it? Thanks for read.
Click to expand...
Click to collapse
did you wipe using fastboot erase command? if so, you need to re-format to the android supported file system to access the partitions!
try installing the twrp recovery and perform 'FORMAT DATA' from wipe. then install ROM.

N4 no OS.
njarun said:
I recently tried to flash PA on my nexus.
Installed cwm on my phone. Then downloaded the PA ROM and moved to the device storage.
Rebooted into CWM and performed all the wipes.
I accidentally wiped the system and the internel partitions too.
when i tried to install ROM from sdcard. it says "NO FILES FOUND"
Iam stuck here. Phone wont boot into Android... any suggestions? please help!
Click to expand...
Click to collapse
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel

Axelben said:
I need help, having the same problem you had with my N4. Cant seem to fix it. I had PA 3.69 for 3 weeks when I rebooted my N4 i had no OS on the phone. Just my Bootloader and Twrp 2500 was recently 2600 but cant do anything else. ADB works seems to fail when writing to N4. Im trying to get it back to stock. Any Ideas
Axel
Click to expand...
Click to collapse
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..

Same problem but...
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
El Daddy said:
If you don't want to flash the stock images you can also push a rom to your phone with adb while booted in a custom recovery
adb push nameofrom.zip /sdcard/
Click to expand...
Click to collapse

Got it working
Hi, I got it to work. No worries guys
xXDustinoXx said:
Hi, I'm having the same problem with my Nexus 4 and I have TWRP V 2.6.3.0 but I'm not sure how to push any rom to my phone because it's not showing up under my computer in Windows. How do I push roms to my Nexus 4? I'm stuck at the Google boot screen when I try to boot (Flashed Dalvik Cache, System, Data, Internal Storage, and normal cache) and I of course don't have any roms on my phone after I wiped all of the partitons. Help me plz
Click to expand...
Click to collapse

njarun said:
can u get into recovery? did u check changing your USB Cable? The original nexus usb cable sucks, try another one. If you can access the fastboot/adb then it will be pretty simple..
Click to expand...
Click to collapse
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file

nickboy360 said:
i cannot get the thing to work this bloody adb command does not seems to work on my Windows 8.1
Can u please give a detailed intruction as i have my file in D Drive so where to keep this zip file
Click to expand...
Click to collapse
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!

njarun said:
you got it working? else pm me your mail id. ill send you the necessary files and detailed info, I once composed it for one of my friend!
Click to expand...
Click to collapse
Thanks for asking mate i got it done... :good:

Wiped System and Downloads Folder! Duh!

Hi guys,
I went to update my ROM to the latest PA, which meant wiping the whole phone etc.
I downloaded the files etc to the phones storage and started wiping the phone. For some daft reason I wiped the SD storage as well, Duh!
So now I've got nothing on here to install
Is there anyway I can sort this out? or is it as the saying goes "you've got an expensive paper weight"
Any help is greatly appreciated.
Cheers

You could use adb sideload to get a ROM back on the phone, or use the factory image from Google to go back to stock. Plenty of threads on here on how to do both

EddyOS said:
You could use adb sideload to get a ROM back on the phone, or use the factory image from Google to go back to stock. Plenty of threads on here on how to do both
Click to expand...
Click to collapse
I managed to push a few files back onto my SD card to install them, but when i went through the recovery to do so, it kept saying the files where not existent?
Cheers

You're better off using adb sideload when in CWM to flash a new ROM. Get the ROM.zip in your adb folder (if you don't have adb/fastboot in your system path), boot the phone into CWM, select install using 'install zip using adb sideload' and then type:
adb sideload ROM.zip
It will then flash the ROM and should get you running again

EddyOS said:
You're better off using adb sideload when in CWM to flash a new ROM. Get the ROM.zip in your adb folder (if you don't have adb/fastboot in your system path), boot the phone into CWM, select install using 'install zip using adb sideload' and then type:
adb sideload ROM.zip
It will then flash the ROM and should get you running again
Click to expand...
Click to collapse
Just finished the sideload with the factory image and it came back with this error - E: Can't open /tmp/update.zip (bad)
Any ideas,
Thank you

You don't sideload the factory images, you run them as a standalone script. You can follow the full guide here:
http://forum.xda-developers.com/showthread.php?t=2010312

EddyOS said:
You don't sideload the factory images, you run them as a standalone script. You can follow the full guide here:
http://forum.xda-developers.com/showthread.php?t=2010312
Click to expand...
Click to collapse
Ended up sussing it in the end.
Really appreciate your help mate, cheers!

jayclarke94 said:
Ended up sussing it in the end.
Really appreciate your help mate, cheers!
Click to expand...
Click to collapse
No worries, It's easy once you know!