Develop Bugs

[Q] Installing Custom Roms on unlocked and rooted phone

So here is my given situation in hand.
1) I Unlocked and rooted my phone and upgraded to jelly bean from ICS.
2) Then later on installed Cyanogenmod rom (team shogun rufdroid)
3) While trying to upgrade. i screwed up and wiped and reinstalling the rom again and for some reason soft keys were missing so i had to wipe complete data and roll back to jelly bean 4.1.1.
4) Now how do i install custom roms now, coz if i use a g nex tool kit v9.1.it says my phone is already rooted and there seems to be a problem loading a bootloader.
I d appreciate if somebody can help me out with this..im still a novice ..trying to learn.

Damn it, don't use a toolkit.
Sent from my i9250

maddyreddy said:
So here is my given situation in hand.
1) I Unlocked and rooted my phone and upgraded to jelly bean from ICS.
2) Then later on installed Cyanogenmod rom (team shogun rufdroid)
3) While trying to upgrade. i screwed up and wiped and reinstalling the rom again and for some reason soft keys were missing so i had to wipe complete data and roll back to jelly bean 4.1.1.
4) Now how do i install custom roms now, coz if i use a g nex tool kit v9.1.it says my phone is already rooted and there seems to be a problem loading a bootloader.
I d appreciate if somebody can help me out with this..im still a novice ..trying to learn.
Click to expand...
Click to collapse
bk201doesntexist said:
Damn it, don't use a toolkit.
Sent from my i9250
Click to expand...
Click to collapse
QFT.
Use This
|
|
|
v​

OP read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Sent from my i9250

why step 3? if you had an issue with the rom you flashed, why not just wipe data and redownload that rom and flash it again from your recovery. or wipe data and flash a different rom. wiping data doesnt remove your rom, and doesnt take you back to stock, and doesnt remove root access. it just removes user data.
root toolkits are the absolute worst things to use on nexus devices. they prevent you from learning the very easiest basic procedures. without knowing the basic procedures, you should not even consider modifying your device in any way. learn about what you are doing/what you want to do, then root your device.

maddyreddy said:
So here is my given situation in hand.
1) I Unlocked and rooted my phone and upgraded to jelly bean from ICS.
2) Then later on installed Cyanogenmod rom (team shogun rufdroid)
3) While trying to upgrade. i screwed up and wiped and reinstalling the rom again and for some reason soft keys were missing so i had to wipe complete data and roll back to jelly bean 4.1.1.
4) Now how do i install custom roms now, coz if i use a g nex tool kit v9.1.it says my phone is already rooted and there seems to be a problem loading a bootloader.
I d appreciate if somebody can help me out with this..im still a novice ..trying to learn.
Click to expand...
Click to collapse
Don't use a toolkit....download the ROM and GApps onto your phone directly....download a file explorer like Astro or ES and make a folder where you want to keep your stuff or just keep them in the downloads folder.....I prefer twrp but you can use CWM or w/e custom recovery you want...now it depends if your upgrading your current ROM with a newer version of your ROM or not....let's start with a complete clean flash....reboot into recovery and make sure you have a backup of at least your current data....if you do do a factory reset wipe system wipe cache wipe dalvik cache (this is all done in recovery mode)....go to previous menu and then go to install....install the ROM FIRST!!!!!!! then the GApps....(newer ROMs have GApps included so make sure you read everything before you install anything). Once you install the ROM and GApps you can go to restore and restore data only....clear the cache and dalvik again then go to advanced and then fix permissions....hit reboot and then reboot system.....now this is my process others might do it differently and you may as well once you get a little better at it.....now a dirty flash would be something like if you are just upgrading to a newer version of the same ROM..... You would download the ROM and GApps reboot recovery wipe cache and dalvik install newer version of ROM and GApps (if applicable on the GApps portion).....once installed clear cache and dalvik again then advanced and then fix permissions then reboot....for kernels you just have to clear the cache and the dalvik cache and then install the kernel unless otherwise indicated..... Good luck let me know what happens and if you have any problems let me know

Seriously, there's no need to wipe caches, when flashing kernels or roms!
Factory reset, or factory reset+format /system at best. Most roms will wipe /system on their own.
Sent from my i9250

No issues,my device is working fine now..I'm on rufdroid v0.92.
But I still had to use a tool kit to install recovery..I tried doing it on command prompt and it was confusing ..next time I'll try doing it with out these tools ....anyways thanks everybody.
Sent from my Galaxy Nexus using xda app-developers app

[Q] [Xperia S] CM10 Installation problems

Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?

Try doing full wipe and reinstall CM 10 as you did previously
Sent from my Xperia S using xda app-developers app

I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app

dumbl3 said:
I tried that too. Like this you mean
1. Fastboot boot.img
2. Fastboot reboot
3. Enter recovery
4. Factory reset
5. Wipe/format system, cache, data, dalvik
6. Install Rom zip
But then I get error and says installation aborted..
Sent from my LT26i using xda app-developers app
Click to expand...
Click to collapse
I have the same problem My phone not boot in just freexperia logo and cwm5.5.0.4. My /data partition can't mount and format I can't install any rom:crying: Heeeeeelp:crying:

All will be fixed
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
Follow this thread for Kernel and Rom installation; http://forum.xda-developers.com/showthread.php?t=1879982
Follow this other to select your Rom; http://forum.xda-developers.com/showthread.php?t=1642480
And take that cm-10-20130110-UNOFFICIAL is CM 10.2 for such reason look for JB Gapps For Android version 4.1.2
I flashed the Rom very well, also the kernel. my problem were the Gapps. I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Regards,

apsanchezs said:
I see there that you do not have the correct gapp zip for cm-10-20130110-UNOFFICIAL;This is CM 10.2 after installation and you need a 4.1.2 JB Gapps. Try and repeat the process.
Click to expand...
Click to collapse
I do have the correct gapps. This CM is android version 4.1.2. Here I downloaded the latest for CyanogenMod 10.0.x which is for android versions 4.1.x.
Anyway after a whole evening/night of flashing I finally managed to get it working via hei1125 cm10 version:
http://goo.im/devs/hei1125/nozomi
I dont know what I did to make it working again, but it does.. CM10 does look a lot nicer then CM9. Although I heard it has some bugs, which yet I still have to encounter..

FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip fails
dumbl3 said:
Hello.
I was running cm9 for a few months without problems. But since the update from Januari the 13th apps started crashing.. I then tried to completly reinstall (wipe everthing), but got stuck on bootloop. Then I thought lets try cm10, and also I get stock on the booting screen.
These are the steps I did.
Flashed LT26i_6.1.A.2.50_1257-5499_WORLD.ftf to go back to stock rom.
Went trough the wizard and all and let it settle down for a few minutes.
Shutdown.
Fastboot boot.img from FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Fastboot reboot
Enter recovery
Flash rom FXP202-cm-10-20130110-UNOFFICIAL-nozomi.zip
Flash gapps gapps-jb-20121011-signed.zip
Wipe cache
Wipe dalvik
Reboot system
But it never boots, I get stuck on bootscreen (same procedure I did with CM9, but also got stuck on bootscreen),
What am I doing wrong?
Click to expand...
Click to collapse
I'm on the same problem. Use FXP201 instead or wait until 203... The cm10-fxp202 doesn't work on my device too. Same procedure as Yours or update from 201 to 202 - all will fail on (my) nozomi.

Hello!
Hello! orange fix for this rom?if so, I would like to link to it? thank you very much :fingers-crossed:

Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel nozimi and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2

funky0308 said:
Had same problem with fxp202 ans SSpeed rom.
Just try to install another kernel.
I had same problems with rom's above, I installed nova kernel hikari and I have no problems anymore.
Sent from my Xperia S using Tapatalk 2
Click to expand...
Click to collapse
i got same plobrem with You.

Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks

Enable signaturecheck in recovery before install. It worked for me.
Gesendet von meinem Xperia S mit Tapatalk 2

Make sure you flash the good .img before flashing the ROM !

alexdan2302 said:
Hello,
I have a problem updating my nozomi (xperia s) to the newest cm version. I always get error 7 - some symlinks failed and i cant install an update without factory reset / wipe user data. After this step i can install the zip, but without wipeing, always the same error.
When i'm installing updates on my girlfriend's urushi (xperia ray), everything works fine.
Any ideas?
Thanks
Click to expand...
Click to collapse
It's always recommend to wipe all (cache, davlink even system) then flash.
Be sure to mount system and then try.
And of course, check is you zip file o.k (maybe download again)
Even if you updating cm to new version it's best if you wipe.
I know that's lot of work, but only then you'll have good battery life, smooth and fast ROM and stability.
Sent from my LT26i using Tapatalk 2

Reinstalled apps and Data from googleserver after a datawiped update shoudn't be a Problem, or?
Gesendet von meinem Xperia S mit Tapatalk 2

I had just the same problem today. I installed cm10 from recovery and did everything you did!!!!
What i did to solve this prblem is:
- Went into recovery.
- wiped cache and dalvik.
- flashed the latest CM10 (FXP215 to be precise) again!!
- flashed gapps again!!
- after flashing both zips I wiped dalvik and cache again.
- Than reboot.
If you keep getting into bootloops, keep doing these steps. Beliefe me man I had the exect same problam today and this solved it . Just dont panic or do something stupid and have alot of patients! :good:

But this is not a so called clean install. I use factory reset to have a clean install or just wipe data partition. After 1st boot I restore only some of my saved data with titanium backup.
Gesendet von meinem Xperia S mit Tapatalk 2

Cannot install any 4.3 custom rom

Hello, my name is Sebastian. First time I post here. I´ve been reading a lot here in Xda, but no posting before.
I have a little question for you all, experts, and I think its kinda simple but I can´t figure it out.
My N7100 was running fine with a stock rom (Android 4.1) and then flashed a custom rom, I think Phoenix Rom (Android 4.1) and working very fine too..
Now I wanted to flash a newer rom, and I've tried a lot, with no good results:
PHOENIX ROM V15 (ANDROID 4.3)
DR KETAN CUSTOM ROM V6.1 (ANDROID 4.3)
DN3 V3.1 (ANDROID 4.3)
HURRICANE V6.0 (ANDROID 4.3)
I can install them all very fine, but when I restart the phone, it get stuck at the Galaxy Note II N7100 logo.
My CWM is version 6.0.3.7 and I`m using Philz touch 5.15.0 (I've tried Philz touch 6 with the same results).
I tried installing a new radio with Odin, version DDUMJ9 Modem and still the same result, stuck at boot logo.
Its weird cause I can install very fine the custom rom PROBAM 5.0 (Android 4.3) and it don´t get stuck at the boot logo, and the system runs very fine. I also can install custom rom REVOLUTION HD 19.0 (Android 4.1 based).
So, my problem its with Android 4.3 and most of the custom roms based in that system that are holded here in Xda.
What can i do? What I'm doind wrong? What is missing?
I'll be very grateful for any help that you can give me.
Best regards.

you stuck at bootloader..what bootloader you use ?
try flash mj5 bootloader

sora9009 said:
you stuck at bootloader..what bootloader you use ?
try flash mj5 bootloader
Click to expand...
Click to collapse
Ok I will try that and post later...any link to download MJ5 bootloader?
Thank you

Ok I flashed MJ5 bootloader using joeldroid instructions (post found here in Xda) via Odin.
Then went to recovery, wipe cache, wipe full/factory reset and installed Phoenix ROM v15 and....still no luck, I'm stuck at the boot logo.
here its the post from joeldroid:
http:// forum. xda-developers .com/ showpost.php?p=46901976&postcount=741 (without spaces)

melankoly said:
Ok I flashed MJ5 bootloader using joeldroid instructions (post found here in Xda) via Odin.
Then went to recovery, wipe cache, wipe full/factory reset and installed Phoenix ROM v15 and....still no luck, I'm stuck at the boot logo.
here its the post from joeldroid:
http:// forum. xda-developers .com/ showpost.php?p=46901976&postcount=741 (without spaces)
Click to expand...
Click to collapse
Phoenix ROM V15 has some issues installing first time.. try complete wipe (keep installation zip on external SD card and format internal SD card in order to clean every thing) then try couple of times... alos select less apps and mods.. you can download app later..
I was on phoenix and gave me troubles installing but was able to in 2-3 attempts always...

ameyamg said:
Phoenix ROM V15 has some issues installing first time.. try complete wipe (keep installation zip on external SD card and format internal SD card in order to clean every thing) then try couple of times... alos select less apps and mods.. you can download app later..
I was on phoenix and gave me troubles installing but was able to in 2-3 attempts always...
Click to expand...
Click to collapse
Thanks a lot man, but I've tried to install Phoenix ROM like...7 times? And before every installation I do the following:
1. Wipe dalvik cache
2. Wipe cache
3. Wipe cache/full factory reset
4. Wipe and clean to install a new ROM (Philz touch option)
And then I perform the installation. Like I said in my first post this is happening to me with every Android 4.3 custom ROM, not just Phoenix ROM.
Do you have any other idea? Thanks in advance.
Best regards.

from what you said,you only do factory reset before install.
did you do factory reset after install ?

sora9009 said:
from what you said,you only do factory reset before install.
did you do factory reset after install ?
Click to expand...
Click to collapse
Yes I've done factory reset to every installation I've made, and I even done it more than one time several times.
I did a new test, I formatted the internal SD and did all the wipe steps and tried to install Dr Ketan ROM (android 4.3 based) with no luck.
After all the new tests I did, finally decided to go back to Android 4.1 and flashed Revolution HD 19.0 and now my phone is working flawlessly.
What is missing in my phone to be able to run Android 4.3? I've seen other people with the same problem, but none seems to give and straight answer.
Here's is an example of the same problem:
http:// forum.xda-developers.com / showthread.php?t=2556414

melankoly said:
Yes I've done factory reset to every installation I've made, and I even done it more than one time several times.
I did a new test, I formatted the internal SD and did all the wipe steps and tried to install Dr Ketan ROM (android 4.3 based) with no luck.
After all the new tests I did, finally decided to go back to Android 4.1 and flashed Revolution HD 19.0 and now my phone is working flawlessly.
What is missing in my phone to be able to run Android 4.3? I've seen other people with the same problem, but none seems to give and straight answer.
Here's is an example of the same problem:
http:// forum.xda-developers.com / showthread.php?t=2556414
Click to expand...
Click to collapse
hurmm..this is weird..
why don't you try mj5 leak stock rom..since mj5 leak is a stock rom..i don't think you will face any problem..
after done mj5 flashing, apply patch from here then flash custom rom.
if that also not working, i dunno what wrong with your phone.

sora9009 said:
hurmm..this is weird..
why don't you try mj5 leak stock rom..since mj5 leak is a stock rom..i don't think you will face any problem..
after done mj5 flashing, apply patch from here then flash custom rom.
if that also not working, i dunno what wrong with your phone.
Click to expand...
Click to collapse
Ok I will try that and I will comeback to post my results.
I will use this guide from Dr Ketan if anyone need the same as me:
http:// forum.xda-developers.com / showthread.php?t=2500823
Best regards

melankoly said:
Thanks a lot man, but I've tried to install Phoenix ROM like...7 times? And before every installation I do the following:
1. Wipe dalvik cache
2. Wipe cache
3. Wipe cache/full factory reset
4. Wipe and clean to install a new ROM (Philz touch option)
And then I perform the installation. Like I said in my first post this is happening to me with every Android 4.3 custom ROM, not just Phoenix ROM.
Do you have any other idea? Thanks in advance.
Best regards.
Click to expand...
Click to collapse
Have you tried zoot's script mega wipe ?
Android 4.3 I notice there's a change on the usb internal storage folder. If the MJ5 bootloader you have tried already, you can try this megawipe. It will wipe very clean your internal storage. Don't worry, it won't wipe your EFS
I always use this script everytime I want to jump to new Android base, and so far never give me a problem.
Good luck!
Sent from the corner of this rounded earth.

You must use a Super Wipe script before the factory reset when installing a 4.3 Rom for the first time.
sent from somewhere

Agree because they change the partitioning.
Sent from the corner of this rounded earth (N7105 v4.3, powered by LionROM)

You can Flash leaked 4.3 mi6 rom via pc odin and it will automatically wipe your all data and int storage. You still will have old boot loader. After that,you can try any 4.3 custom rom.
Sent from my GT-N7100 using Tapatalk

[Solved] Bootloop after flashing any Touchwiz based rom

Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app

Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr

Full wipe cache and reset in recovery menu, clear everything, you should be up and running.

akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..

I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.

Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...

akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Happy to help you bro

Beta 4.2 20140318 hangs during boot

Hi,
I started using PA on my Galaxy Nexus with a fresh install of 4.0 Beta 6 about 4 weeks ago (unlocked and rooted via nexus root toolkit, recovery is teamwin).
Since then, I installed every update through Paranoid OTA, so I am on current 20140318 now with GAPPS stock 20140318.
Everything was great.
Suddenly, a few hours ago, the phone started rebooting again and again until I decided to take out the battery.
Since then, it hangs during boot at the PA logo.
I tried reinstalling pa_maguro-4.0-BETA6-20140217.zip and pa_gapps-stock-4.4.2-20140217-signed.zip through recovery (after backup of course), but this changed nothing.
Fun thing is... I am moving to a new flat tomorrow and really need my phone to organize things.
So if anybody has an idea what I can look at or how this may be fixed, I would really appreciate it.
Thanks!
Stephan
Edit: wiping cache and dalvik cache did not help...

Factory reset and reinstall

felt0r said:
Hi,
I started using PA on my Galaxy Nexus with a fresh install of 4.0 Beta 6 about 4 weeks ago (unlocked and rooted via nexus root toolkit, recovery is teamwin).
Since then, I installed every update through Paranoid OTA, so I am on current 20140318 now with GAPPS stock 20140318.
Everything was great.
Suddenly, a few hours ago, the phone started rebooting again and again until I decided to take out the battery.
Since then, it hangs during boot at the PA logo.
I tried reinstalling pa_maguro-4.0-BETA6-20140217.zip and pa_gapps-stock-4.4.2-20140217-signed.zip through recovery (after backup of course), but this changed nothing.
Fun thing is... I am moving to a new flat tomorrow and really need my phone to organize things.
So if anybody has an idea what I can look at or how this may be fixed, I would really appreciate it.
Thanks!
Stephan
Edit: wiping cache and dalvik cache did not help...
Click to expand...
Click to collapse
Seems like you got stuck in a bootloop. bootloops can occur pretty easily, it’s mainly caused because system files interfering with each other which causes instability and/or crashes at the boot sequence
Try doing a fresh install (use latest recovery version of your recovery)
- wipe data/factory reset
- wipe cache partition
- format system and data
- wipe dalvik cache and flash the rom and gapss again