Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
leandronb said:
Flash PA again but do not flash the kernel. looks like PA is using jss build and maybe the kernel you are flashing is using jwr build.
PA is having some problems now with root, i suggest you to stay in 4.2.2 or use another 4.3 rom.
Click to expand...
Click to collapse
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
andyabc said:
Did you flash the Android 4.3 baseband and radio?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Nigeldg said:
Yep, you have to wipe data since you're switching between Android versions.
Sent from my Nexus 4
Click to expand...
Click to collapse
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
12ian34 said:
But I only installed the PA rom corresponding to JB 4.3, I never updated to stock 4.3 or anything beforehand, it was just a mistaken update to PA 3.92 which I think is for JB 4.3 only. Anyway I think I'm clutching at straws here, so if I do have to wipe, 1) how can I make the fullest backup possible of everything on my phone and, 2) how do I go about wiping and finally, 3) after I wipe, what exactly do I do??
Thanks so much to you three for taking an interest in my problem so far!
Click to expand...
Click to collapse
I had exactly the same issue you had at first boot, it remained at Google logo forever when i first flashed PA 3.92. This issue came because i was flashing PA 3.02 with Franco nightly 165, franco nightly 165 is for 4.2.2m and if you were in 4.2.2 then you will never know new releases as that one was the last 4.2.2 kernel. I suggest you flash PA 3.92 + gapps from 0802, without Franco, it will boot fine. Also, as explained in big letters in PA download, first step is to download radio and bootloader for the update, i did not have to wipe my memory for the upgrade.
I don't recommend downloading Franco 175 for 4.3, as it has conflicting issues with PA, so use PA with the stock kernel and you should be good meanwhile this gets solved.
12ian34 said:
Yeah, I do intend to say in 4.2.2, do you think I should try an older PA? I think 3.69 is for 4.2.2, which is the one I've flashed, several times. OK, I'll try flashing the rom, then gapps but not Franco Kernel as you suggest, but I think I may have tried that already and it didn't work.
No, I don't even know what radio is, all I did was try to flash the PA 3.92 update zip, on it's own (plus gapps and franco kernel)
Click to expand...
Click to collapse
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Sent from my Nexus 4 using Tapatalk 4
andyabc said:
Go here and flash the baseband and radio and flash it before flashing the rom and make sure it is wiped clean: http://forum.xda-developers.com/showthread.php?t=2147194
Click to expand...
Click to collapse
But how do I go about backing it up before I wipe it give that I can only access fastboot and recovery (CWM) ?!?!
OK, I've found a way to do it using
./adb-mac pull /sdcard/0/ sdcardbackup
do I need to backup anything else?
Also, I've downloaded the link you sent me, just to be clear, first, I wipe data, factory reset, then I send the radio and baseband to my phone using adb, then flash them in recovery and then flash PA 3.69, GApps, Franco Kernel r165 then wipe cache, dalvik cache, then reboot, then go about restoring all my data. Is this correct?
Mee too
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
jsmonu said:
I just wiped my Nexus 4, flashed the new jb 4.3 bootloader and radio, and flashed PA 3.94 to check out the experience.. Except for the time taken by boot logo to start up the first time, I was happy using it for a couple of hours.. Only till the time I rebooted it.. Since then, it's just stuck at the PA animation / logo and NOT MOVING AHEAD !! Please help!!
Click to expand...
Click to collapse
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
molesarecoming said:
just do what is written on the xda page, do not deviate from that.
get up to date, that means get the latest TWRP and make sure you are running googles newest radios
1. factory reset, perhaps format partitions: system, data, cache, dalvik
2. install the latest PA, thats 3.94
3. install the latest PA gapps, thats 0805a
4. wipe caches, reboot
5. do no mess around with things like titanium backup - at least dont restore system apps
6. if you make a clean install root will work out of the box.
when developing i must go through that process hundreds of times, i can vouch that it will work.
Click to expand...
Click to collapse
Moles! Help me! I refer you to my first post in this thread, I want to stay on 4.2.2 and PA 3.69 for the moment, and preferably not wipe everything. I accidentally updated to PA 3.92 and then stuck at the PA logo on boot forever. Now I've tried to go back to 3.69 many times and still get stuck at PA logo. currently using adb pull to get all my important stuff off phone.
Is there a shortcut for me, which doesn't involve wiping??
EDIT:
... OK, I just downloaded the 4.3 radio and bootloader, pa 3.94, gapps and sent them to my phone, flashed each one in turn and then wiped caches, reboot. I skipped the wipe, and now my phone is working for the first time in three days - [optimising apps]. Let's see if this works....
Yep, phone works absolutely fine, didn't have to wipe and now have 4.3 and PA 3.94, which wasnt my original intention, but it had to happen sometime! Thanks for all the help people, I think we can consider this one solved
12ian34 said:
Hi, I'm just another android semi-noob who made a silly mistake, and has now spent the whole day in the library researching my problem, as I don't have internet at my new flat yet.
Here's what happened, as concisely as possible:
I have a Nexus 4, on 4.2.2, running a version of PA 3+, with Franco Kernel. I felt like another PA nightly update, after having not updated for a couple of weeks, so I chose the latest one, which was PA 3.92. Did the usual - recovery, install rom, install gapps, install kernel, wipe cache, wipe dalvik cache.
Then, the phone wouldn't boot, was stuck on the Google logo. I went to bed. Today, I realised (although I could still be wrong) that the 3.92 PA update was for Jelly Bean 4.3. Is this even correct? Well, assuming it was, I managed to connect phone to my mac, go into terminal, use adb-mac, which I had downloaded months ago when I first rooted, and send the PA 3.69 zip to the phone. Installed that, then gapps then kernel, wiped cache and dalvik cache, and rebooted. I've now done this a few times and each time, I get stuck at the Paranoid Android boot logo.
Most of the other threads I see suggest wiping data. I really don't want to wipe my data, is there a solution?
If I do, really, have to wipe my data to get any further, how would I go about backing EVERYTHING up beforehand, given that I only have access to fastboot and recovery? Would I need to follow this tutorial (which doesn't backup SMS...) - http://forum.xda-developers.com/showthread.php?t=1420351 ? Also, when I've backed up, how exactly do I go about wiping data and then getting back to exactly where I was before all of this?
Was I correct in thinking that PA 3.92 is only for JB 4.3 and that PA 3.69 is for 4.2.2? Was I correct in thinking that this is why my phone got stuck?
Please, please help me, it will be much appreciated, my laptop is almost out of battery now so I'm going home, then coming back to the library in an hour as I haven't eaten all day
Depressed noob.
Click to expand...
Click to collapse
Download the nexus 4 toolkit and flash stock rom from it
Performed a full clear and freshly installed the latest nightly and I'm not getting any cell service. any ideas? in about phone it says UNKNOWN on baseband
details
Dadealus said:
Performed a full clear and freshly installed the latest nightly and I'm not getting any cell service. any ideas? in about phone it says UNKNOWN on baseband
Click to expand...
Click to collapse
Let me guess. You have TWRP and when you went into recovery you did more than just swipe to flash. You found a wipe data that prompted you to confirm yes or no and you tapped "yes".
How close am I?
fukenbiker said:
Let me guess. You have TWRP and when you went into recovery you did more than just swipe to flash. You found a wipe data that prompted you to confirm yes or no and you tapped "yes".
How close am I?
Click to expand...
Click to collapse
I have PhilZ touch 5 recovery
To perform a fresh install I chose
wipe data/factory reset> clean to install a new rom
from there I installed the 10.2 nightly and then the 10.2 compatible Gapps
after reboot everything except cell service and camera.
I just now gave up on 10.2, returned to the last 10.1 nighty by performing the same steps
wipe data/factory reset> clean to install a new rom
from there I installed the 10.1 last nightly and then the 10.1 compatible Gapps
after reboot everything works just dandy.
Dadealus said:
I have PhilZ touch 5 recovery
To perform a fresh install I chose
wipe data/factory reset> clean to install a new rom
from there I installed the 10.2 nightly and then the 10.2 compatible Gapps
after reboot everything except cell service and camera.
I just now gave up on 10.2, returned to the last 10.1 nighty by performing the same steps
wipe data/factory reset> clean to install a new rom
from there I installed the 10.1 last nightly and then the 10.1 compatible Gapps
after reboot everything works just dandy.
Click to expand...
Click to collapse
Thank you for the report.
fukenbiker said:
Thank you for the report.
Click to expand...
Click to collapse
Did I do something wrong? that caused the cell modem to stop working? I'd still like to use 10.2 but I'm not sure what I did wrong
Dadealus said:
Did I do something wrong? that caused the cell modem to stop working? I'd still like to use 10.2 but I'm not sure what I did wrong
Click to expand...
Click to collapse
I am learning right along with you, thank you for testing CM 10.2 as I've always liked cyanogenmod but I am sticking with GoldenEye for now because of reports like yours.
It has been seen with a few others using PhilZ and flashing 4.3. Please change recoveries, or update to PhilZ 5.11.0
Ol' Dirty Bastard said:
It has been seen with a few others using PhilZ and flashing 4.3. Please change recoveries, or update to PhilZ 5.11.0
Click to expand...
Click to collapse
I will give this a try and report back
doesnt appear to be a 5.11 for the ATT version
anyone know or have 5.11 loki'd for the ATT s4? This is the only recovery i can find that supports exFAT.
Hey, I had CM10.2 which for some reason caused me a lot of troubles with battery and wifi so I Decided to revert to stock 4.4. I downloaded the stock from google and I installed it with the fastboot through the command prompt. But for some reason, the phone just won't turn on, it goes into the KitKat boot animation and just gets stuck there forever. What should I do?
I already tried wiping cache and it didnt really help...
Thanks!
Try a factory reset from the stock recovery.
All of the images flashed successfully without any problems?
Sent using xda-developers app
Chromium_ said:
Try a factory reset from the stock recovery.
All of the images flashed successfully without any problems?
Sent using xda-developers app
Click to expand...
Click to collapse
All of the images were flashed successfully, but if I do a factory reset, what will it exactly do? won't it erase litterally anything I Have and then I will stay out of options? I have never done a factory reset so I dont really know. If I have a CM 10.2 flashable ZIP on my storage, will it stay there after the Factory reset? Because every time I have a problem with a certain rom I just flash back to the CM 10.2
PriStol said:
All of the images were flashed successfully, but if I do a factory reset, what will it exactly do? won't it erase litterally anything I Have and then I will stay out of options? I have never done a factory reset so I dont really know. If I have a CM 10.2 flashable ZIP on my storage, will it stay there after the Factory reset? Because every time I have a problem with a certain rom I just flash back to the CM 10.2
Click to expand...
Click to collapse
It will wipe all user data including the internal storage. Basically the phone will be exactly how it was from the factory. So yes, the cm10.2 that you have will be gone after the factory reset.
But I'm pretty confident that doing a factory reset will get the phone to boot.
Sent using xda-developers app
PriStol said:
All of the images were flashed successfully, but if I do a factory reset, what will it exactly do? won't it erase litterally anything I Have and then I will stay out of options? I have never done a factory reset so I dont really know. If I have a CM 10.2 flashable ZIP on my storage, will it stay there after the Factory reset? Because every time I have a problem with a certain rom I just flash back to the CM 10.2
Click to expand...
Click to collapse
A factory reset does indeed wipe everything on your phone. You're learning the hard way why it is a good idea to periodically back up your phone.
The best thing about doing a factory image reset is that you start from a know good point. If the ROM you want to use is based on 4.4, then use the 4.4 factory image. Likewise if the ROM is based on 4.4.2 then use that factory image.
Sent from my Nexus 4 using Tapatalk
Maybe you've got the same issue that I just described here : http://forum.xda-developers.com/showthread.php?t=2595057
edit : apparently nothing to do with the radio afterall
Guys Thanks you so much I did a factory reset and my phone is now working all good with 4.4.2
Just a question, Is my phone still rooted after a factory reset?
PriStol said:
Guys Thanks you so much I did a factory reset and my phone is now working all good with 4.4.2
Just a question, Is my phone still rooted after a factory reset?
Click to expand...
Click to collapse
No. It was no longer rooted after flashing the stock images.
But getting root back isn't that hard. Just install a custom recovery and flash the latest supersu.
Sent using xda-developers app
Chromium_ said:
No. It was no longer rooted after flashing the stock images.
But getting root back isn't that hard. Just install a custom recovery and flash the latest supersu.
Sent using xda-developers app
Click to expand...
Click to collapse
Ok thanks
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
matthewclso said:
I recently installed CyanogenMod 10.2 on my Sprint Nexus S 4G, but after realizing it was Android 4.2, not 4.4, I installed OmniROM 4.4.2 on my phone. However, it's now stuck in this annoying bootloop. I removed the battery and went into recovery (CWM recovery). I tried reinstalling the ROM, doing a factory reset, wiping my cache, wiping my dalvik cache, but it's still in the bootloop when I rebooted. Is it because I installed CM 10.2 before? How can I get it to reboot correctly? Can I restore to the original OS?
Thanks
Click to expand...
Click to collapse
you can...try this!
@halfdevil said:
you can...try this!
Click to expand...
Click to collapse
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
FIXED
Turns out that I just had to flash the boot image through fastboot, works great now! Thanks
matthewclso said:
I actually figured out how to mount my USB storage to my computer and managed to return it back to CM 10.1 and get it out of bootloop. However, I would still love to have Android 4.4 on my phone, and I can't seem to get OmniROM working. I'm also looking into Avatar ROM 5.0.3, but the link seems to be broken. Any ideas?
Also, the link to return to stock doesn't work.
Click to expand...
Click to collapse
well you can try AOSP too, just remember all these projects are discontinued, so any support in case you break anything support won't be there..so always backup.
for AOSP!