Hi Guys,
Yesterday i installed Paranoid Android on my phone ( full wipe data and cahe ) and it started to reboot when making calls.
So i decided to install CM9 RC1 and got the same problem.
I reverted back to stock and now my phone is fine.
Someone has a clue of what's happening ?
I tried different kernels but got the same problem.
Your help is appriciated.
Greetings,
PTiT
Have you formatted /system and fixed permissions?
Inviato dal mio GT-I9100 con Tapatalk 2
PTiTDaV said:
Hi Guys,
Yesterday i installed Paranoid Android on my phone ( full wipe data and cahe ) and it started to reboot when making calls.
So i decided to install CM9 RC1 and got the same problem.
I reverted back to stock and now my phone is fine.
Someone has a clue of what's happening ?
I tried different kernels but got the same problem.
Your help is appriciated.
Greetings,
PTiT
Click to expand...
Click to collapse
If you are doing it through CWM
Try installing after wiping Dalvik cache available in advance.
PTiTDaV said:
Hi Guys,
Yesterday i installed Paranoid Android on my phone ( full wipe data and cahe ) and it started to reboot when making calls.
So i decided to install CM9 RC1 and got the same problem.
I reverted back to stock and now my phone is fine.
Someone has a clue of what's happening ?
I tried different kernels but got the same problem.
Your help is appriciated.
Greetings,
PTiT
Click to expand...
Click to collapse
hi.
Had same kind of issue. Random reboot/shutdown.
I installed 1.6 last night. With full wipe of everything I could find in my kernel to wipe.
then, install paranoid.
then install G-apps.
then WIPE cache again.
then fix permission.
as recommended in the official thread by the dev.
It solved my issue.
good luck.
Same problem here.
Any stock rom (including ICS) works well.
I tried installing paranoidandroid 1.6.
Factory reset
Wipe cache
Wipe dalvik
Install gapps and camerafix.
wipe cache.
Set phone dpi to 184
reboot
And basically, everytime i try to make a phone call, it looks like that the phone screen (the one that displays the contact picture and the close-call red button) is crashing.
I can hear 10 seconds of phone ringing/conversation and then the system reboots, showing me the boot animation.
The only way to fix this, so far, is by installing a stock rom
..probably I am missing something, but I cannot get it working.
I resolved mine by reverting to a GB stock rom and flashing the lastest nightly from there.
box2k2 said:
I resolved mine by reverting to a GB stock rom and flashing the lastest nightly from there.
Click to expand...
Click to collapse
So basically you Installed the latest CM9 nightlies rather then paranoidandroid ?
Hi there, I am new here and I need some help with flashing ROM on my HTC Sensation. Now I have Android_Revolution_HD-Sensation_3.6.7 that work fine, but I try flash ROM to Android_Revolution_HD-Sensation_6.7.2_XE and [ROM] ELEGANCIA™ ◄Sense 3.6|3.1.0|. Both of these doesnt work.. the first flash (Revolution HD) done but reboot is infinite (more than 30min) and the second (Elegancia) flashing done too, bud boot still restarting phone in beatsaudio screen... I clear cache and dalvik, format sdcard but nothing didnt work Everyone it's working except me... Both of these ROMs are stable and tested by many users. What I doing bad? Thanks for help!
Sicco said:
Hi there, I am new here and I need some help with flashing ROM on my HTC Sensation. Now I have Android_Revolution_HD-Sensation_3.6.7 that work fine, but I try flash ROM to Android_Revolution_HD-Sensation_6.7.2_XE and [ROM] ELEGANCIA™ ◄Sense 3.6|3.1.0|. Both of these doesnt work.. the first flash (Revolution HD) done but reboot is infinite (more than 30min) and the second (Elegancia) flashing done too, bud boot still restarting phone in beatsaudio screen... I clear cache and dalvik, format sdcard but nothing didnt work Everyone it's working except me... Both of these ROMs are stable and tested by many users. What I doing bad? Thanks for help!
Click to expand...
Click to collapse
Were you doing clean installs?
What you mean? I buy this phone before one year, it was rooted with Android_Revolution_HD-Sensation_3.6.7 and now I want flash ICS ROM. I try ROM manager and than flash from boot menu where I choose zip file, but no effect..
He means, did you wipe data/factory reset and wipe cache/dalvik prior to flashing? Or did you just flash over your old ROM?
Also (I doubt this is the issue, but it's common over in the One XL forums), are you sure you have a Sensation (not the Sensation XL)? I would assume that Sensation ROMs will not boot on the Sensation XL and visa versa.
Sent from my One X
I have classic Sensation and yes I clear cache and dalvik (do wipe before), but stil no working... meanwhile I have stock ICS ROM...
Are you s-off?
Sent from my One X
of course I have S-off and root
Sicco said:
of course I have S-off and root
Click to expand...
Click to collapse
Format ALL partitions, flash the ROM, wipe dalvik cache then reboot.
OK, I;ve read already the few thread about the Warning message "Camera Failed" but haven't found one that one that would help diagnose before taking more drastic action.
After installing ArchiDroid 1.5 custom rom, everythings works very nicely except the camera which give me a "Warning: camera Failed" message
is there a way to re-install only the Camera application or .pak to see if that is the problem, any other thoughts ?
PS: I did a wipe before installing ArchiDroid. I don't think I've cleared the Dalvik, can it be part of the prob ?
Thanks
PS: My first ROM install so maybe this issue is normally easy to fix for more advance people.
Phone : GS 3 I9300
Best go back, wipe again including system, data and dalvik before flashing again - there is a flashable script that will do the wiping for you, or use Philz recovery which has it built in.
If your rom is based on Samsung stock then camera should work, if aosp then camera can be a problem. If still the same after reflash then ask your rom chef for help.
boomboomer said:
Best go back, wipe again including system, data and dalvik before flashing again - there is a flashable script that will do the wiping for you, or use Philz recovery which has it built in.
If your rom is based on Samsung stock then camera should work, if aosp then camera can be a problem. If still the same after reflash then ask your rom chef for help.
Click to expand...
Click to collapse
Thanks. I did flash again after wiping (still not Dalvik as I couldn't remember how to access such option), but selected the Stock instead of perseus and things are working now .
I searched the internet and threads on XDA for this problem but couldn't really find one!
The problem is- My Galaxy S3 (GT-I9300) doesn't boot any AOSP/AOKP/CM ROMs! It's just the bootanimation and DONE! For hours and hours the bootanimation only! But I can flash any Sammy 4.3 / 4.4 ROMs! They boot! They work properly!
I used to change to AOSP to Sammy and vice versa so many times with no issues. One day I downloaded the UltimaAOSP Valhalla ROM and flashed it. This was the first time my S3 didn't boot. I flashed custom Kernels like boeffla on it but all in vain. It was stuck on the bootanimation. I flashed NeatROM AOSP on top of it, which worked properly. Then it was with the fusion sp ROM that it didn't boot again. Again I flashed NeatROM AOSP on top of it (it's my favorite ROM), which I used just to copy some other ROM from my PC to my phone.
Now, I'm on my Stock ROM which came with my phone since so long! I'm shocked to see now NO AOSP ROMs are booting! I've used C-ROM, NeatROM, Resurrection Remix and SOKP Milestone. I have the ROMs' ZIP files and also a Nandroid Backup which I made when I changed to other ROMs. Not the ZIP files neither the Nandroid Backups are helping! ZIP files get flashed succesfully (I wipe the data & cache & dalvik-cache every time) and the Nandroid Backups get restored successfully! But always the phone gets stuck on the bootanimation!
I always moved to AOSP from Sammy (never Sammy to Sammy) but this time I gave it a shot.
Result : All the Samsung ROMs are flashing, working properly, even the Nandroid restores boot. I flashed my newly downloaded FlashingDroid Sammy 4.4 ROM which also works.
BUT I CAN'T GET THE AOSP ROMs onto my phone!
My thought (it could be wrong) : Is it to do something with the data in a partition other than system, data, and cache? Some partition which has stored files needed to boot Sammy ROMs and is preventing AOSP ROMs to start?
HELP!
:crying:
MORE UPDATED INFO ON POST #6
::ROBLEM SOLVED:::
Wipe system, data, cache and preload partitions manually in mounts and storage in CWM Recovery.
DONE! AOSP Working!
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
boomboomer said:
Suggests something is being left behind that aosp objects to. Try the rescue firmware in general forum, wipe internal sd and preload.
Click to expand...
Click to collapse
Have lots of data on my internal memory! Still I deleted lots of unwanted files. Any other way to wipe the hidden preload partition other than using Philz Recovery? I remember I flashed Philz after which I couldn't restore any of my Nandroid Backups backed up with CWM Recovery..
Sent from my GT-I9300 using XDA Premium 4 mobile app
In cwm mounts and storage wipe preload
Press thanx if i helped you in anyway...
Update - Got More Info
Update : Just noticed that when it's the bootanimation on the screen after flashing an AOSP ROM, pressing any of the buttons on the phone vibrates the phone vigorously 2 times.. why??
Also, I want to ask about the connection between a kernel and a bootanimation without starting a new thread 'cause I think it's the solution to my problem here.. The data which I probably suspect that prevents AOSP ROMs from booting is some different bootanimation file? I mean when I'm on a Sammy ROM, I started to flash different bootanimations after flashing some CWM Custom Bootanimation ZIP file. The bootanimation changes on all Kernels on Sammy ROMs -except 1 that is the boeffla kernel. The strange thing is that the first custom bootanimation I had flashed (after flashing Boeffla's Sammy Kernel) when I switched to Sammy from my last AOSP was the hTC One Bootanimation which worked fine (the bootanimation successfully changed). After that, it never changed. My phone always booted up showing the hTC One Bootanimation no matter how many times I flashed another bootanimation ZIP or the CWM ZIPs which enable/disable Custom bootanimations. But! When I changed to any other kernel (the stock that came with the ROM/GoogyMax 2/AGNi), the bootanimation was the last one flashed by me before changing the kernel. I could change the bootanimations successfuly every time after that. Now, I flashed Android Revolution HD ROM and was on Stock Kernel. As soon as I changed to boeffla kernel (without flashing any other ZIP), the bootanimation changed! (automatically!) And it was again the same old hTC One Bootanimation.
Can someone please tell me WHERE is this bootanimation data and the data that prevents AOSP ROMs to boot is stored? Certainly not in the data or system or cache partition...
Update 2 : Just figured out where the automatic htc bootanimation magic happened. The hTC bootanimation.zip file was found in data/local . However, I always knew the bootanimation directory as system/media.. So now, is it safe for me to delete all files in data/local 'cause it seems it is the problem for AOSP ROMs?
Sent from my GT-I9300 using XDA Premium 4 mobile app
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
jimbobpro87 said:
the main thing i can think of is your trying to go back to jb roms which you cant do as far as i know try flashing kitkat based roms
Click to expand...
Click to collapse
I'm not trying to go back to Jelly Bean! I'm flashing AOSP based ROMs of KitKat 4.4.2 which don't boot!
SOLVED!
Yayy!
I guess I got a solution!
Wiped system, data, cache and preload partitions manually in mounts and storage in my CWM Recovery.
DONE! AOSP Working!
:victory:
THANKS TO ALL WHO HELPED! :angel:
Thank you for your post.
I am having the same problem, phone not booting past boot animations using aosp ROMs. Haven't tried Sammy ROM to test the theory yet but will try soon.
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
alaska_ryder said:
How do you wipe preload? In mounts and storage, I get an error when trying to mount or format preload using CWM 6.0.4.7
I don't see an option to wipe anything other than data, cache, or dalvic.
Click to expand...
Click to collapse
Strange- it happened that day but not now. Even I get an error formatting preload. But! I guess the problem is the system partition! There IS an option to format /system in mounts and storage option on the first screen.
Sent from my GT-I9300 using XDA Premium 4 mobile app
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Eden532 said:
This is really an old post i think.
But, can someone answer me please, ive been searching for This maybe for more than a year. Can someone please help me? @Paresh Kalinani
I have the exact same issue.
My device: Grand Prime (G530FXXU1AOJI baseband)
Stock android: 5.0.2
Recovery: TWRP 3.1.0.0
I have booted many Samsung roms and also ported many of them like J5's 5.1.1 , On7's 5.1.1 rom and many other 5.1.1 and 5.0.2 roms and all of them work perfectly. But when it comes to AOSP ROMS each of them keeps loading at the booting animation screen. Ive tried many roms like RR, AOSP Extended, Cyanogenmod, LINEAGEOS, All of these 5.1.1 , 7.1.1.
It booted for others with the exact Same variant as mine too.
Please help me?
Id been really grateful.
Thanks,
Eden532
Click to expand...
Click to collapse
Have you flashed the rom then factory reset?
Beamed in by telepathy.
shivadow said:
Have you flashed the rom then factory reset?
Beamed in by telepathy.
Click to expand...
Click to collapse
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Eden532 said:
Nope.
I wiped system, data, cache and dalvik cache the flashed the rom and the rebooted?
Do I have to do a factory reset then?
Thanks a lot for the immediate response.
Click to expand...
Click to collapse
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
MigoMujahid said:
Well, what you did was butter than a factory reset.
Factory reset means wiping data, cache and dalvik cache.
I would like you to do something first, try downloading the latest stock firmware for your phone from sammobile, and then flash it with Odin, then try flash AOSP roms again, maybe you have an old bootloader.
Click to expand...
Click to collapse
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Eden532 said:
Im running the latest firmware which id flashed through odin.
AOSP roms still not booting.
I had wiped those partitions before i flashed the rom. I did not wipe after i flashed them.
Click to expand...
Click to collapse
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
MigoMujahid said:
Are you sure it's the latest one?
Did you check Sammobile.com?
The latest one was released in 1st Feb 2017.
Also please check the IMEI of your phone by typing *#06#, because if you've a problem with efs partition you may not be able to flash any AOSP Rom (happened to a friend before..he had sim working without IMEI!!)
Also what is your country code?
Click to expand...
Click to collapse
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
shivadow said:
As stated above, check your imei is still OK then from a working stock state:
Root it.
Flash custom recovery.
Flash the custom rom twice and then wipe data/cache. Do not wipe system!.
If that doesn't work then try the above but instead of wipe data/cache do a factory reset.
Beamed in by telepathy.
Click to expand...
Click to collapse
I did flash the custom rom twice but still no good.
(And also i checked the IMEI via a custom Sammy rom)
Eden532 said:
My country code is XSG but ill try flashing the THL latest version and again report.
I was trying to check my IMEI number it shows UNKNOWN APPLICATION but sim and other modem related stuff works really fine.
Is it something to do with this?
Click to expand...
Click to collapse
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
MigoMujahid said:
This is the latest firmware for United Arab Emirates:
https://androidfilehost.com/?fid=385035244224412750
Flash it and see if the problem solved :good:
Click to expand...
Click to collapse
Thank you so much for sending the link, Its really difficult to download from sammobile.com . Ill check it right away and report. Thanks.
I was using the Blekota Note 4(based on Kitkat) on my i9300 when it one day suddenly it restarted on its own and went into a bootloop and heated up. So I took out the battery and tried starting it again by clearing cache and dalvik cache. But it was still stuck at bootloop. After about 3 hours, somehow it came back on its own, but all the data and settings were lost. The downloaded apps were present, but their settings were lost.
Since I would have to again set up all apps, I wanted to try a new rom, Lollipop based. I downloaded the latest RESURRECTION REMIX (5.5.7) apps and downloaded the OpenGapps micro package. But after trying a clean install, the boot loop problem was still there. I tried with a different Gapp package, from OmniRom thread (all were for Android 5.1) but still no help. Even flashing the ROM alone would be of no help. I remembered I had a similar problem after flashing Boeffla kernel and the solution in that case was flashing a new version of the kernal. I tried that also. But no help.
I changed my recovery from CWM to TWRP as someone in some thread mentioned that it could help. But still No avail. In doing a clean rom, I tried almost 3 roms, cleaned cache, system, dalvik cache and even the internal storage and tried all other combinations. BUT THE SAME BOOT LOOP PROBLEM REMAINED.
As a last resort I had to flash the original 4.3 JellyBean firmware hoping that performing a clean install from that would help. But even after that the boot loop remains. Someone please help me flash a Lollipop based rom. This thing is driving me crazy now.
There's still 1 basic procedure: flash a 3part firmware with PIT-file for repartition.
Pit files should only be considered as a last resort.
Clear data and reflash stock rom and repeat once more. I have had cases where the rom didnt fully clear on a normal single flash.
Dont let it boot to rom. Do the two data wipes from recovery only.
I wish I stole my HTC M9.