Hello,
I've only yesterday rooted my phone for the very first time and followed a guide on how to flash PA. In the guide it told me to flash a radio and boot loader, which apparently I wasn't supposed to flash because I was on 4.3 already. So I didn't have service, someone told me to reflash 4.3 which I did using the stock rom downloaded from android dev page. But It won't flash the system it returns an error regarding the usb port. I flashed 4.2.2 which did flash the system but is apparently stuck on the loading screen (nexus X) for about 20 mins or so. Any help on how to reflash stock 4.3 and then reflash just PA 3.99 and Gapps?
cheers
RabbeV said:
Hello,
I've only yesterday rooted my phone for the very first time and followed a guide on how to flash PA. In the guide it told me to flash a radio and boot loader, which apparently I wasn't supposed to flash because I was on 4.3 already. So I didn't have service, someone told me to reflash 4.3 which I did using the stock rom downloaded from android dev page. But It won't flash the system it returns an error regarding the usb port. I flashed 4.2.2 which did flash the system but is apparently stuck on the loading screen (nexus X) for about 20 mins or so. Any help on how to reflash stock 4.3 and then reflash just PA 3.99 and Gapps?
cheers
Click to expand...
Click to collapse
Go into recovery and do factory reset, that should get u past the nexus X... Then just flash pa and gapps your done, flashing a radio and bootloader shouldn't have hurt anything unless u flashed wrong ones, recheck your versions on the files. U should be on a radio that ends in 84 (it works on 4 2.2 so dont worry... U dont need to be on 4.3 to flash pa, just factory reset first
drawde40599 said:
Go into recovery and do factory reset, that should get u past the nexus X... Then just flash pa and gapps your done, flashing a radio and bootloader shouldn't have hurt anything unless u flashed wrong ones, recheck your versions on the files. U should be on a radio that ends in 84 (it works on 4 2.2 so dont worry... U dont need to be on 4.3 to flash pa, just factory reset first
Click to expand...
Click to collapse
I wanted to do that but my sd had been wiped, but it's been solved
Related
Hey,
Today in between flashing a new ROM i went back to 4.2.2 cm10.1.2, just to check some things out before flashing a 4.3 ROM that i was intending to do in the first place.
However after having reverted to 4.2.2 when i went and install the 4.3 ROM i noticed i had no signal, since then i've tried flashing the radio and boot from 4.3 Factory Image via fastboot, tried installing a different 4.3 ROM, all with no success.
What can I do?
Btw i still get signal in 4.2.2
Thanks.
Mottz said:
Hey,
Today in between flashing a new ROM i went back to 4.2.2 cm10.1.2, just to check some things out before flashing a 4.3 ROM that i was intending to do in the first place.
However after having reverted to 4.2.2 when i went and install the 4.3 ROM i noticed i had no signal, since then i've tried flashing the radio and boot from 4.3 Factory Image via fastboot, tried installing a different 4.3 ROM, all with no success.
What can I do?
Btw i still get signal in 4.2.2
Thanks.
Click to expand...
Click to collapse
Check APN settings?
How do I do that?
Also the phone app just crashes totally when I try to do anything with it, even entering airplane mode triggers that.
Sent from my Nexus 4 using Tapatalk 4
You should do a clean wipe before you flash 4.3 from an older version, do a factory reset and wipe the system partition, then flash 4.3 rom.
via xda app
It might have to do with TWRP.
http://forum.xda-developers.com/showthread.php?p=45323439
Try flashing TWRP 2.6.0.0 then proceed from there to flash your rom.
I guess i forgot to mention, i did a clean install, i factory reset before reverting.
And i have TWRP installed, I've tried several ROMs and in all of 4.3 ROMs i dont have signal and the Phone app FCs when i try to use it.
On that note, does TWRP Factory Reset wipes System Partition?
Factory reset does wipe system partition except /data/media.
Flash TWRP 2.6.0.0 (this version)
Factory reset
Flash Rom
Flash Gapps
Flash Modem
Flash Kernel
Flash Supersu
Wipe caches
Reboot
Btw, here is some insight on what to wipe in TWRP:
http://teamw.in/whattowipe
Oh I just saw your previous post, didn't understand it at first but now that I think about it I do actually have 2.6.1.0.
Ill try what you said and report back.
Thanks.
Sent from my Nexus 4 using Tapatalk 4
It worked, thanks alot!
Guys I know there are a ton of threads with this problem but no matter what I try, i'm still stuck on a boot loop.
So basically I had PA Rom 3.99 RC2 on my nexus and everything was fine. I then tried to flash PA AOSP kit kat build
but my phone would not boot so I went with a factory image occam 4.3 Phone booted and all was good. I was liking the
stock experience and then about 4 days later after a reboot, phone got stuck on the boot animation X. It would not get out of it
so I decided to flash PA Rom 3.99 rc2 again via ADB push zip. factory reset, installed the rom and gapps, wiped caches and thought i was good to go. Well the phone again would not get past the boot animation of PA.
i then decided to go with the Factory image occam 4.3 via fastboot and installed it and everything. Again stuck on the X. So then I tried PSX rom 4.3 again via adb push, did my factory reset and flashed the rom and gapps and superSu. Also got stuck on the boot animation. Left it for over 2 hours bootlooping and nothing.
Going crazy I went and fastboot the 4.2.2 JDQ39 img and downgraded bootloader, baseband. Installed it and again, stuck on the X animation. just hangs there.
Any help? i don't know what else to try, currently using my HD2 and it is sooo slow :cyclops:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
badboy47 said:
Make sure to use latest cwm recovery. Avoid using twrp recovery. Use the toolkit and flash stock image. It will wipe everything in the phone but it will fix it.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thanks for the suggestion but still nothing. Updated CWMR to 6.0.4.3 and tried the 4.3 stock image. Still hangs on bootup. android file transfer recognizes the device is plugged in via usb but just gives me the error "could not connect to device"
Oh man I don't know what's wrong with my nexus
bump bump
I'm having this same issue, and it happened just like you. I flashed CM 10.2 nightly 20131114 this morning and I tested it to make sure everything was working. I decided to reboot the phone, and after that I keep getting stuck at the boot animation no matter what I did. To no avail, I reflashed a working zip, restored a backup, restored another backup, flashed the 4.4 factory image (wiping the entire phone), the 4.3 factory image, and then I read that the 4.2 baseband can fix it, so I flashed the 4.2 factory image. That 4.2 image gets it to boot, but without baseband. Right now I'm trying different radios just to see if I can get service again. If it matters, I was running the hybrid 33/84 radio for T-Mobile's LTE when this happened. Very, very peculiar situation here. I've never had anything like this happen, and especially remain an issue after wiping the entire device. I'm hoping it's not a sudden hardware issue.
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Hmmy 4444 said:
i jst flash factory image of 4.4 n nw my phone is stuck o the boot animation screen plz help
Click to expand...
Click to collapse
just re-flash 4.2, it'll work. I've been doing that since Monday. but I want kitkat too!!
my device is stuck on the boot animation too. is there a way to reinstall the default 4.3 recovery and just rerun the update or something basic like that? my device was almost at stock before running the update. the only two things: twrp and rooted via recovery. so i thought everything will work fine and now there is no backup...
badboy47 said:
Avoid using twrp recovery.
Click to expand...
Click to collapse
Why?
Just fastboot flash all the image files (boot.img,recovery.img....) from the factory image.
Hi all,
For the past few days I've been trying to flash new ROMs. I'm a noon but have previously flashed probably 100 times with no problems at all.
Ive stuck with psx for about 3 months and live it, but as updates for the ROM have become a hasstke to get, I thought I'd try something else, but this time move on to KitKat custom ROMs instead of 4.3.
Now here's the problem. I'm doing everything the same as I usually would, d/l ROM, appropriate gapps, use latest twrp, factory reset, flash and then..... FAILED update : ( : ( Now I am a noobso am I missing something big time???, do I need to completely wipe phone when flashing from 4.3 to KitKat??, pls help, I'm sick to death of going through the fail/restore process
Thanks in advance : )
Are you updating the bootloader and radio when moving from 4.3 to 4.4? Did you try formatting the system before installing?
I transitioned from jellybean to KitKat too yesterday and had that same problem. From what i remember, what I did was when I got that failed update message in twrp, i first clicked home, then click reboot, then select to recovery. It should then warn you're about to reboot w/out a ROM/system. I swiped yes. Then it should prompt u to install supersu. Go ahead and swipe yes. It should then reboot u back to recovery and u can proceed to do your normal install routine. Now I'm adjusting myself to KitKat life!
Sent from my Nexus 4 using Tapatalk
I had that problem flashing ROMs with TWRP as well. I had to unmount the system, then everything flashed successfully!
Use cwrm instead , brotha from another motha twrp has issues with kitkat
Sent from my Nexus 4 using Tapatalk 4
You need a custom boot image for kitkat
I just got a N7. It came with stock 4.4.2 but I unlocked and flashed a few 4.4 ROMs to try out (Liquid, CM, OMNI). Anyway, I figured I might want to try a 4.3 ROM so I flashed one. It didn't boot. Went back and installed the 4.4 ROM and all was good. I thought maybe I needed to flash a 4.3 factory image first, so I did. I fastbooted (verb) everything in the JWR66Y directory and OMG it booted. Great, time to flash a ROM, right? Nope. Flashed CWM touch 6.0.4.3 again and it booted using the stock ROM/kernel but after I flashed a custom ROM, it just sits at the boot screen. The obvious answer here would be to have patience and wait. I have waited for 35+ minutes at the bootanimation screen with no sign of booting. This is on any 4.3 ROM I try. However, it will boot right up if I flash the stock JWR66Y system and boot images. What do you think, kernel related or am I missing something more obvious?
On flashing a Custom Rom, my phone gets stucked with continous FC ("Unfortunately Phone Crashed","Press OK") just after the phone boots.
I had faced the same problem earlier so someone on XDA suggested to use twrp recovery. Then i flashed the purity rom and it worked fine, but then as you may know now, as PA is out, so flashed it and again i'm getting continuous fc error....
currently i'm using purity rom, stock kernel and twrp recovery (2.6.3.3)
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
audit13 said:
I would flash back to a stock 4.2.2 and start over. I find that this is the only way I can install certain roms.
Click to expand...
Click to collapse
I already did this and again i'm facing the same problem
htrapy said:
I already did this and again i'm facing the same problem
Click to expand...
Click to collapse
Strange. Are you updating the bootloader and radio before flashing a 4.4 rom?
Are you doing a factory reset???? And flashing a proper gapps after ROM? You should always do this when going from one ROM to another. Sometimes a manual format of /system is necessary also.
no i am not updating my bootloader and radio before flashing (rather didn't know if i had to update them,fyi i bought my nexus 4 this september)....and yes i'm doing a factory reset (using the wipe option in twrp recovery which warns clearing of data, cache and dalvik memory)