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
Hey I am new to this so I had a T-989 running on 4.1.2 or something and so I installed CWM and rooted it using the T-989 toolkit. Afterwards I forgot to wipe and installed CM10. I was stuck on the booting screen for 40 mins and when I tried to go back to CWM it didnt work. So using the same toolkit I flashed the stock ROM. The stock seems to be gingerbread 2.3.6 and now the toolkit will not recognize it. Please help. I want it to run on CM10
Forget the toolkit and do it manually. First do you still have root? Try installing twrp recovery , you will have much less problems. Or try cwm again and make sure you follow the steps provided. Usually it's wipe/format, then format system, flash rom, wipe dalvick, wipe cache partition, fix permissions, reboot.
badaphooko01 said:
Forget the toolkit and do it manually. First do you still have root? Try installing twrp recovery , you will have much less problems. Or try cwm again and make sure you follow the steps provided. Usually it's wipe/format, then format system, flash rom, wipe dalvick, wipe cache partition, fix permissions, reboot.
Click to expand...
Click to collapse
Thanks for the info I was able to flash a 2.3.6 Gingerbread ROM onto my S2 using the toolkit and then from there on I had to reinstall the CWM and root and then using another guide I used the DarkSide wipe and reinstalled everything manually. Solved. Thank you.
Howdy y'all!
I'm currently running a 4.1.1 ROM, and would like to get on to MMuzzy's 4.2, but there are a ton of things I think I need to flash and want to make sure I get the order right. Your help will be much appreciated!
I am already using the latest version of TWRP.
I would like to flash the latest JB bootloader, and latest JB radios, but have never flashed either. Should I do these before flashing the ROM, or after? Should I do these before formatting cache? Should I format system or factory reset before flashing these, too?
I am planning to do factory reset, format cache and dalvik before flashing ROM, gapps and kernel. Do I need to do anything else to prep for flashing the ROM? Also, is it okay to flash all three at once, or should I do rom and gapps, let everything boot and restore from market, and only then flash kernel?
My main concern is the differences in file system between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
I wouldn't bother with the bootloader, but if you insist then you can flash the bootloader and the radios before or after. Doesn't matter.. Other than that, you do them ROM, gapps, kernel and I've done all three at once. Mmuzzy's is a good ROM. Enjoy.
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
jrbedford said:
My main concern is the differences in file system tree between 4.1 and 4.2. I'm aware of the /0 subdirectory thing already, but I'd there anything else?
Thanks much!
Jamie
Click to expand...
Click to collapse
Just a small correction; file system change would mean switching from ext4 to f2fs, for example. That's not the case.
MartianCeo said:
First make a backup in TWRP
Factory reset
Wipe both caches
Install ROM, gapps, then kernel and reboot. (All at the sometime in that order)
I have heard its better to flash the kernel with the new ROM so just do it all in one flash.
Set everything up and let your phone sit for 15 minutes untouched and go for it.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Watch out with restoring backups. Don't restore app/system data. OP is switching major versions.
sent from my Google Galaxy Nexus
I am new to rooting and rom'ing. I was able to root my Hercules using clockwork 6.0 and was in the process of installing cm10 and it froze up, and after i rebooted it got stuck in a boot loop. I did do a back up of my stock rom and have gotten it to factory reset back to astock rooted rom, not sure if it is my backup stock rom. The process that I read to rom it is to install darkside wipe, then cm10, then gapps. I have wiped data, cache and davlik cache, i am trying to get it to install cm10, but it doesn't seem to want to install. what should i do to get it to start over and get cm10 rom on?
I would only use the Darkside wipe scripts on CWM 5.X. Use Odin to reflash the recovery of your choice and then format system, factory reset, and then flash CM10.
Sent from my Nexus 4 using xda premium
Thanks, I didn't know that, guess the instruction i found were a little outdated. I'll try your suggestion. What do mean by formattin it? (I thought the factory reset does that?) Also how long should it take for cm10 to install?
heath.bse said:
Thanks, I didn't know that, guess the instruction i found were a little outdated. I'll try your suggestion. What do mean by formattin it? (I thought the factory reset does that?) Also how long should it take for cm10 to install?
Click to expand...
Click to collapse
Formatting the system only formats the /system partition and wipe data formats the /data partition.
What do you mean?
Sent from my Nexus 4 using xda premium
I would have made a backup of the stock rom then from the stock rom downloaded goomanager from play store then flash newest twrp recovery, then wiped and installed a appropriate ROM
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 06:33 AM ---------- Previous post was at 06:27 AM ----------
Of course your stock rom would have then needed to be rooted
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
heath.bse said:
I am new to rooting and rom'ing. I was able to root my Hercules using clockwork 6.0 and was in the process of installing cm10 and it froze up, and after i rebooted it got stuck in a boot loop. I did do a back up of my stock rom and have gotten it to factory reset back to astock rooted rom, not sure if it is my backup stock rom. The process that I read to rom it is to install darkside wipe, then cm10, then gapps. I have wiped data, cache and davlik cache, i am trying to get it to install cm10, but it doesn't seem to want to install. what should i do to get it to start over and get cm10 rom on?
Click to expand...
Click to collapse
You missed /System as well [hence why the stock ROM booted again otherwise if you actually formatted where the ROM was there is no backup ROM.
You should move to Jellybean [I have used ParanoidAndroid as a daily druver for months now and it is newer [Android 4.1.2].,
No matter which ROM you choose, first boot phone
download ROM Manager [Free is fine]
Open it, grant Super User
Tap top-most option to install Clockwork Recovery and it will walk you through getting etiher the non-touch for free or paying $2 for touch recovery [unless you flashed that via Odin then skip], but need to be sure you have newest CWM and not an old one from a rooting guide that been around.
Boot to recovery wi[e cache
tap advanced wipe dalvick
go back one menu
go to mounts and storage tap to wipe system, and data
go back one menu to main
tap install zip from SDCard
Tap internatl or external wherver you saved it and find the CM 10 you downloaded and tap and flash it
do the same but find where you saved the gapps pack
now restart device and enjoy
continual boot loop...tried everything here.
RealPariah said:
You missed /System as well [hence why the stock ROM booted again otherwise if you actually formatted where the ROM was there is no backup ROM.
You should move to Jellybean [I have used ParanoidAndroid as a daily druver for months now and it is newer [Android 4.1.2].,
No matter which ROM you choose, first boot phone
download ROM Manager [Free is fine]
Open it, grant Super User
Tap top-most option to install Clockwork Recovery and it will walk you through getting etiher the non-touch for free or paying $2 for touch recovery [unless you flashed that via Odin then skip], but need to be sure you have newest CWM and not an old one from a rooting guide that been around.
Boot to recovery wi[e cache
tap advanced wipe dalvick
go back one menu
go to mounts and storage tap to wipe system, and data
go back one menu to main
tap install zip from SDCard
Tap internatl or external wherver you saved it and find the CM 10 you downloaded and tap and flash it
do the same but find where you saved the gapps pack
now restart device and enjoy
Click to expand...
Click to collapse
I got cm10 on for about 20 minutes then CWM updated to 6.x. I flashed a nightly and it's been in a bootloop ever since. However, when I was on CM10 those few brief minutes I could not hear or he heard on a call.
No idea what to do now. I'm stuck on 2.3.6 unless there's some other trick I can do to get this thing to boot...
Why not just try a different rom? Lots of options out there.
Also, watch the dates on the how to's you read. A lot can be outdated.
Sent from my cell phone telephone....
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
dallinrigby said:
Hello:
So I rooted my phone today and I downloaded the app, "ROM Manager," and downloaded a ROM from it, which I read that I'm not supposed to do, afterwards. Now, whenever I turn my phone on, it only shows the Cyanogenmod boot animation. I read in another thread that I should clear the cache, which I did, but it did not help. Should I try and flash it to the stock? Please help! I am inexperienced with this and I don't know what to do. Thanks in advance!
Click to expand...
Click to collapse
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
I have already tried to clear the cache and the dalvik and then did a reboot but it didn't change anything.
shortydoggg said:
Your phone will get stuck if you did not clear the dalvik as well as the cache. I would recommend first clearing cache again and also dalvik before rebooting back into the operating system or doing something else which may not be necessary.
Click to expand...
Click to collapse
ChinDaChin said:
Alright. First off: what OS were you running before you went to cyanogenmod? was it 4.0.4? 4.1.x? 4.2.x? or 4.3.x?
Second, give us more information about the phone.
Third, you might have to go into recovery mode, wipe your phone (theres two options in the main menu, and one in the advanced called wipe dalvik). Then youll have to reinstall Cyanogenmod.
Click to expand...
Click to collapse
I was running the stock jellybean before I installed cryogenmod...my phone is a galaxy s3 it47 (AT&T) network unlocked phone. Also, at the bottom in recovery mode it says
ClockworkMod Recovery v6. 0. 4. 5
I'm not sure whether or not this is important but it is the only thing that I can think of to tell you about my phone.
I don't care whether we keep my data, I just want it to be able to turn on! Can I just restore it using Odin somehow? I tried the wipe user memory option in recovery mode and that didn't help...
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
shortydoggg said:
Personally, I hate both ROM manager and clockworkmod.
It sounds like you just need to wipe data (or factory reset), cache and dalvik, and then reboot. If that doesn't work, then you might have flashed a version of cyanogenmod that may not be compatible with your bootloader, and may have to manually try another ROM.
Click to expand...
Click to collapse
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
dallinrigby said:
I tried to do a factory reset, it didn't help as far as I know. How do i manually try another rom?
Click to expand...
Click to collapse
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Go to http://download.cyanogenmod.org/?device=d2att&type=
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Go here and download 10.2: http://wiki.cyanogenmod.org/w/Google_Apps and put it on your SD card with the above .zip.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
ChinDaChin said:
Can you tell us what version of touchwiz you were running before you tried rooting it? It's important if it's past 4.3.x, or before 4.3.x. Do the following if you were running 4.3.x before you rooted.
Choose the one named: cm-10.2.0-d2att.zip
Download it and save it to your SD Card.
Once thats done, power off your phone. Go into recovery mode (volume up + home + power).
Wipe Data/Factory Reset
Wipe Cache partition
Advanced -> wipe Dalvik Cache
Go back, and choose Install Zip
Choose zip from /storage/sdcard (find your cm10.2 zip, run it. then run the gapps)
After you "installed" both zips, go back to the main menu and reboot system now
This will be a clean install of 10.2.
FYI: Clockworkmod Recovery is v6.0.4.5, so you have the most up to date.
Click to expand...
Click to collapse
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
It says on that second link to download Torrent or via It Vends, is this the right place, and if so what do I pick?
Thanks by the way, also is there a way I could do this with Odin?
dallinrigby said:
I don't know what version I had. Is there a way for me to tell? I just had whatever I bought it with, I never downloaded anything else.
Click to expand...
Click to collapse
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
ChinDaChin said:
I used Goo.im. It's a funky looking website, but it's legitimate. I didn't do this with Odin, I used Cyanogenmod Installer :silly:
If you follow what I posted before, it will update everything, and you will run cyanogenmod 10.2. (What I'm running on my s3). HOWEVER, it will update your phone to 4.3. This means you cannot downgrade it, or it will be bricked. By downgrade, I mean you will not be able to run anything before 4.3. (So you can ONLY install roms that are 4.3, or jellybean).
I'm pretty sure you already updated everything since its stuck in the boot loop.
Any chance you did a nandroid backup(before you did the root)? If not, you've got nothing to lose and might as well go through with CM 10.2 (in my honest opinion).
Click to expand...
Click to collapse
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Do i need to unzip it?
dallinrigby said:
Okay, so now it says Android system recovery <3e> at the top and at the bottom is this:
#MANUAL MODE#
--Applied Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
Then when I pushed install from sdcard it said E:failed to verify whole file signature
Click to expand...
Click to collapse
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
ChinDaChin said:
Don't lose hope, but every site/page I check, it says the error is with you flashing through Rom Manager. It's okay though, there has to be a solution.
I'm going to continue looking for the solution. If you could try and remember what version of the OS you were running before you tried to root, it would help out SO MUCH!
LOL., I forgot to hit post on this.
And no, don't unzip it. The phone can read it fine.
Anyway, after some quick reading, a few people are saying its either your rom that is corrupted, or you don't have the proper recovery. It can't be the rom, because the rom was downloaded from the source. So chances are its your recovery. I'm not sure if you can download the CWM recovery, and flash it from recovery. (if that makes sense?)
Click to expand...
Click to collapse
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
Where do i get TWRP? It doesn't say that I have Clockwork anymore, since I factory reset it
dallinrigby said:
I don't really understand this stuff very much, and also I am pretty sure my android version before was 4.1.2, that's jelly bean right? is that what you meant?
Click to expand...
Click to collapse
Sorry.
I'm kind of conflicted on what's going on with your phone. It is partially a problem with going through Rom Manager to flash cyanogenmod.
audit13 said:
If it's CWM that is the problem, you can download TWRP and flash it via Odin if you can get into download mode. Then, you can use TWRP to flash a custom ROM.
Click to expand...
Click to collapse
I guess you can try TWRP. I haven't used TWRP so I can't comment on it. I'll try finding an explanatory video that is simple to follow. (Don't throw out Cm10.2, or the gapps. You will need those to get Cyanogenmod on your phone!)