I had the offical 4.2.1 and then unlocked bootloader.
Now i wanted to use AOKP Jellybean Milestone 1 (4.1.2) but the rom makes weird things. Does not reboot (when i click it) and the sim card is not recognized (just "no service", i cannot enter my pincode).
I already flashed some radios.
I have an GSM Galaxy Nexus (free) and use it with a german O2 Sim card.
Can anybody help?
Did you go into recovery and make a full wipe then flash the AOKP ROM? If not, then try it this way
Regarding radios, XXLH1 is very fine with me and it is the latest standard european baseband according to this thread.
ahmadallica said:
Did you go into recovery and make a full wipe then flash the AOKP ROM? If not, then try it this way
Regarding radios, XXLH1 is very fine with me and it is the latest standard european baseband according to this thread.
Click to expand...
Click to collapse
I use cwm and i wiped data/factory reset and wiped cache. Or is there a full wipe option?
I am back on 4.2.1 and reflashed the XXLH1 radio. But this doesn't work on 4.1.2
JonnyZaggi said:
I use cwm and i wiped data/factory reset and wiped cache. Or is there a full wipe option?
I am back on 4.2.1 and reflashed the XXLH1 radio. But this doesn't work on 4.1.2
Click to expand...
Click to collapse
That's correct about wiping and you may even wipe "dalvik cache" as well.
XXLH1 was working fine with me on 4.1.2 as far as I remember.
Since you are now on 4.2.1, then go into recovery (which should be latest TWRP or CWM), wipe data, cache, and dalvik, then install a ROM other than AOKP. There are a lot in the development forum and stable ones. If everything went fine and your radio is working on 4.1.2, then again wipe everything and try the AOKP so at least you already confirmed the radio is working fine on 4.1.2
Related
Hi guys,
When updating a current rom from one build (8/20) to the next (8/25), will I have to do a full wipe/factory reset, wipe cache and wipe dalvik cache, or is it possible to just flash the newest update for this rom?
Thanks!
Kinrit said:
Hi guys,
When updating a current rom from one build (8/20) to the next (8/25), will I have to do a full wipe/factory reset, wipe cache and wipe dalvik cache, or is it possible to just flash the newest update for this rom?
Thanks!
Click to expand...
Click to collapse
Its always the best to do a clean wipe so the new rom doesn't co-exist with the old bugs
Thank you!
One more question, when restoring a previous build, like a stock build or something, is it safe to go ahead and restore that rom, or do you also recommend wiping and going back to stock ICS and then restoring?
Or does wipe/factory reset basically put you back at un-root and stock ICS?
Still trying to understand all the lingo, thanks for the help.
Kinrit said:
Thank you!
One more question, when restoring a previous build, like a stock build or something, is it safe to go ahead and restore that rom, or do you also recommend wiping and going back to stock ICS and then restoring?
Or does wipe/factory reset basically put you back at un-root and stock ICS?
Still trying to understand all the lingo, thanks for the help.
Click to expand...
Click to collapse
If you are updating the same rom you don't have to do a full wipe. Just wipe cache and dalvik. AOKP --> AOKP is fine. CM10 nightly --> CM10 nightly is also fine.
If you are talking about a nandroid, you can restore those whenever you so choose. No prerequisite necessary.
Generally whenever I install a new rom (update or not) I will use the following steps:
download rom / put on sd
Wipe data / factory reset
Wipe dalvik and cache partition
Format System
flash rom
flash gapps
Reboot
This has always worked without fail and in this case it seems to have worked again.
However, I noticed in my settings menu that I no longer have "launcher options" under interface. Has this option been removed from the newest nightly? or has something gone wrong during my flash?
Used:
clockwork-6.0.1.2-d2att
cm-10-20121111-NIGHTLY-d2att
JB-4.2-Gapps-signed.zip
Phone:
Samsung Galaxy S3 SGH 1747
Carrier: Bell
EDIT: Also receiving: Android is upgrading, starting apps on every single reboot. Still loads fine but minor annoyance.
EDIT2: Figured it out, installing the 4.2 gapps was causing all problems. Reverted back to the 4.1.2 gapps and everything is fine. Thread can be closed.
SOLVED!
Could I ask: Did you have to reflash the ROM to fix this? Or just flash an older version of the gapps?
I have the same problem and just got all my apps back ... would rather not have reflash the ROM and then restore everything if I don't have to.
Jalopy
djjohnnyblaze said:
Generally whenever I install a new rom (update or not) I will use the following steps:
download rom / put on sd
Wipe data / factory reset
Wipe dalvik and cache partition
Format System
flash rom
flash gapps
Reboot
This has always worked without fail and in this case it seems to have worked again.
However, I noticed in my settings menu that I no longer have "launcher options" under interface. Has this option been removed from the newest nightly? or has something gone wrong during my flash?
Used:
clockwork-6.0.1.2-d2att
cm-10-20121111-NIGHTLY-d2att
JB-4.2-Gapps-signed.zip
Phone:
Samsung Galaxy S3 SGH 1747
Carrier: Bell
EDIT: Also receiving: Android is upgrading, starting apps on every single reboot. Still loads fine but minor annoyance.
EDIT2: Figured it out, installing the 4.2 gapps was causing all problems. Reverted back to the 4.1.2 gapps and everything is fine. Thread can be closed.
SOLVED!
Click to expand...
Click to collapse
JalopyPilot said:
Could I ask: Did you have to reflash the ROM to fix this? Or just flash an older version of the gapps?
I have the same problem and just got all my apps back ... would rather not have reflash the ROM and then restore everything if I don't have to.
Jalopy
Click to expand...
Click to collapse
You do not have to wipe data if the rom is the same. Just wipe cache/dalvik and then reflash rom/gapps 4.1.2.
Installing home2launcher will also wipe away your option of launcher under settings. Which is unfortunate.
Sent from my SGH-I747 using xda app-developers app
Please someone help me. I need the steps.
Once I have my phone rooted and flashed a CWM.
What next? where can I get CM10 international version phone that works with bell in canada?
what are the steps ? cheers guys
http://get.cm/?device=d2att
Reboot to recovery, factory reset, wipe dalvik, format system, flash cm10, flash gapps.
is format system and factory reset the same thing ???
I am on stock right now.
Also where can I find the correct version of CM10 ? I am on Bell (i believe it's the same as the AT&T in America)
I have a Samsung Galaxy Nexus GSM and have been trying to install the Paranoid Android flavor custom ROM, I had 2.22 installed not long ago but managed to screw it up when I updated it without clearing my security settings (I had a 4x4 pattern swipe which I couldn't enter with the update which restored it to 3x3 pattern) so I wiped and restored to stock 4.2. I'm now trying to re-install with any custom ROM but it's not working.
Whenever I install a ROM it seems to install ok but when I get to the boot screen it just hangs on the nexus/PA logo.
I've tried with:
Goo Manager
TWRP 2.2
TWRP 2.3
CWM 6.0.1.5
and with
PA 2.22
PA 2.99.1
PA 2.99.5
PA 2.99.6
PA 2.99.7
and I always get the same error, I've tried wiping all options within TWRP and CWM and going from there but that doesn't seem to work, the strange thing for me though is that if I re-install a stock Google ROM it works perfectly fine.
I'm fairly new so please be gentle.
flash the latest twrp and move the rom and gapps to your sdcard then follow this..
1. factory reset
2. wipe system
3. wipe cache
4. wipe dalvik
5. flash rom
6. flash gapps
7. reboot
if it still freezes at boot animation pull battery reboot to recovery wipe cache/dalvik and reboot
Thanks for the suggestion but that didn't work.
Any other suggestions?
When you say TWRP 2.3 do you mean 2.3.2.1? http://teamw.in/project/twrp2/90
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
zephiK said:
When you say TWRP 2.3 do you mean 2.3.2.1?
Clockwork 6.0.1.5 is also outdated, newest is 6.0.1.9.
You need to update your recoveries for Android 4.2.X which is what PA 2.99 is based off of.
Click to expand...
Click to collapse
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Using TWRP, wiping cache, dalvik, and system should wipe everything except the sdcard contents. So doing these wipes should make your phone "bare stock" again as you described
Why don't you try downloading another custom ROM or download the same ROM again because maybe it is corrupted or something
osiris231 said:
Yes I did mean 2.3.2.1, I wasn't sure what the whole version number was at the time and I was halfway through resetting up stock on my phone at the time so I didn't bother to check exactly. sorry about that.
Is there a way to completely wipe everything on the phone so that it is bare stock? I was just wondering if I would be able to start from a clean phone if it would make any difference. I'm aware of cache/delvik cache/internal storage/(i think it's called "system partition" or something like that).
Click to expand...
Click to collapse
RANT: huh..... seriously? you couldn't have browsed around, searching for this COMMON issue (which usually comes down to user "error"), read the STICKIES, before posting?
first, internal storage = /data/media aka /storage/sdcard0/ aka /sdcard/
Please read all of this
http://forum.xda-developers.com/showthread.php?t=1626895
Hi,
I got the rooted, deodexed, and debloated version of the latest stock rom.
After I flashed it, I keep getting the error messages "unfotunately the process ... has stopped unexpectedly". I used CWM to flash this rom multiple times. I also wiped data/factory, cache, and dalvik cache. I saw some others are reporting the same error.
I was wondering if there is a solution for this out there.
Thanks
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
gc84245 said:
Did you try infamous superwipe and cache wipe? Check the sticky in the development thread.
Click to expand...
Click to collapse
No I didn't try the infamous superwipe. I will do it. What is cache wipe, is it same as the option in CWM recovery mode?
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
gc84245 said:
I don't know much about how they work, but it's the only way I could get the stock rom to work, so it might work for you too. Just flash them both instead of wiping the normal way. I think one wipes data and one wipes cache, more info in the thread.
Click to expand...
Click to collapse
Ok, BTW, I moved from Juggernaut 5.0 to JB Stock using ODIN and it worked fine. It's the rooted version of the JB Stock that gives me these errors. In fact, the main reason that I tried rooted version is because it supposedly doesn't have bloadware either.
Well using odin removes more than flashing a zip, for example it replaces your recovery. I'm not an expert and don't know much about the details, but that's probably why it worked using odin.