urukdroid 1.5 help - Gen8, Gen9, Gen10 Q&A, Help & Troubleshooting

okay so here is my issue i flash 1.5 and ill get lots of FC's at the begging get past that try to install the Fix but it will not recognize the OC kernel or the fix
i put them in the place designated /.upgrade/directory and /data/UrukUpdate and i just bootloop everytime i put them in their how do i fix this? any ideas? ive did this thru open SSH and USB and neither are working any advice is appreciated thanks guys hope we can get this figured out

Franzferdinan51 said:
okay so here is my issue i flash 1.5 and ill get lots of FC's at the begging get past that try to install the Fix but it will not recognize the OC kernel or the fix
i put them in the place designated /.upgrade/directory and /data/UrukUpdate and i just bootloop everytime i put them in their how do i fix this? any ideas? ive did this thru open SSH and USB and neither are working any advice is appreciated thanks guys hope we can get this figured out
Click to expand...
Click to collapse
don't know what to tell ya about the FCs, mines been rock solid thus far. Extract the kernel files from the OC package and flash them directly using the Archos SDE menu. That's what I had to do as it would not install via the methods you tried either.

Wouldn't that make it re install uruk droid I fixed the force close problem by starting at 1.0 then just using the update but most of my apps don't work and force close almost immediately
Sent from my A101IT using Tapatalk

Franzferdinan51 said:
Wouldn't that make it re install uruk droid I fixed the force close problem by starting at 1.0 then just using the update but most of my apps don't work and force close almost immediately
Sent from my A101IT using Tapatalk
Click to expand...
Click to collapse
If you are flashing the OC kernel no it wont reinstall UD because its the actual kernel you are flashing not a setup routine. If you are still getting FCs id recommend redownloading the 1.5 install package again, do a fresh install, then flash the OC kernel directly afterwards once you verify everything is stable.

I sugest to do reinstall wit EasyInstall - it will fix rootfs without touching /data
http://code.google.com/p/urukdroid/wiki/EasyInstall#ReInstall_UrukDroid

Related

[Q] CM7 - Problems mounting cache, loading gapps

I can't seem to mount or clear my cache via cwm4 after flashing CM7. I'm also having issues loading gapps with CM7. They install successfully, but don't show up in my app drawer. I'm assuming the problems are related. Any help would be greatly appreciated. <3
I believe I've seen this issue before. How are you booting into recovery? Using the 3 finger method or power menu > reboot > recovery? Once you have cm7 installed only the power menu method should be used.
Sent from my SCH-I500 using XDA App
Okay so here is my issue. When I use the 3 finger method I get ClockworkMod Recorvery v4.0.1.0, but I from ROM Manager I get 3.0.0.8. Whats up with that? Also I get the same cache errors and gapps issue that the person above is having. Where did I go wrong?
I am having the exact same problems. I tried to verify the GAPPS zip and it said it couldn't verify it. Is that normal?
thejanitor36 said:
Okay so here is my issue. When I use the 3 finger method I get ClockworkMod Recorvery v4.0.1.0, but I from ROM Manager I get 3.0.0.8. Whats up with that? Also I get the same cache errors and gapps issue that the person above is having. Where did I go wrong?
Click to expand...
Click to collapse
thats just how it shows up in rom manager... As far as the other issue, Im not sure man, alot of guys are having problems installing cm7,, while others have no trouble. I had it installed and running great with glitch, but decided to try a different leakage and got bootlooped. Now cm7 will absolutely not install on my device. I have tried odining back to stock ed05, pwgb, evil fascination...It keeps coming up error cant mount datadata. Even reformatted my sdcard still no love...quite frustrating, hopefully you get your issue worked out. Good luck!
Okay I reflashed and used this guide: http://forum.xda-developers.com/showthread.php?t=1212239
No more errors and GAPPS successfully installed.... but the market is all messed up. It downloaded my old apps, but now I cannot download any new apps because it says my internal memory is full.
Avalanch3 said:
Okay I reflashed and used this guide: http://forum.xda-developers.com/showthread.php?t=1212239
No more errors and GAPPS successfully installed.... but the market is all messed up. It downloaded my old apps, but now I cannot download any new apps because it says my internal memory is full.
Click to expand...
Click to collapse
Try rebooting. Fixed it for me

[Help] Still Experiencing Disappearing Widgets w/ Faux's Newest Kernel (0.1.9)

Title practically says it all.
I'm running Nottach's Darkside v1.3, 1.97 radio, and v0.1.9 of Faux's kernel.
I was informed that the disappearing widgets was almost solely kernel related, as well as that v0.1.9 fixed such issue.
Any ideas? Was I simply misinformed?
Delete widgets, open Rom Manager, fix permissions, reboot, set widgets, should be fine. Works for me.
Assimilated via WinBorg 4G
CaelanT said:
Delete widgets, open Rom Manager, fix permissions, reboot, set widgets, should be fine. Works for me.
Assimilated via WinBorg 4G
Click to expand...
Click to collapse
Thanks. I'll give it a try.
Oddly enough, I ended up fixing my permissions a couple times today (for an unrelated reason), but that was after I had my widgets set up. Maybe it takes doing it before I throw stuff on my home screen.
Thanks again.
_______________________________
Alright- fixed permissions and re-placed my widgets. Fingies crossed
Faux claims that it's a ROM issue, so i guess we dunno who the culprit is.
i do know that some people have luck using fastboot to clear their data/cache/dalvik, and other people have luck fixing permissions.
i've never had a problem with disappearing widgets, but i do have a problem with my widgets taking a while to load up. they'll be there, and none of their settings or features will work for a few minutes after random reboots. using CM7 on 0.1.9, i just take it as a small price to pay for having such an awesome kernel and ROM.
Alcapone263 said:
i do know that some people have luck using fastboot to clear their data/cache/dalvik, and other people have luck fixing permissions.
QUOTE]
This is a point worth noting. I always fastboot -w before installing a new ROM. I have found that this is the best way for me to have a clean flash with no issues after. Maybe this coupled with fixing permissions is the best way to go. I do believe it works better using fix permissions through Rom Manager than through CWM also. I don't know what the differences are if any, but there has been feedback to indicate one works better than the other for the widget problem.
Click to expand...
Click to collapse
I got no love with anything.
Heard it was out down to possibly being launcher pro.
I had to do a radical revamp.
Swyped from "Mount" Olympus
Its not Launcher Pro, I use Go Launcher and have the exact same issue.
What I have is:
Brazilian Atrix - d00
nCrust 0.7
faux 0.1.9 oc kernel (working great at 1.3GHz and UV, ROCK STABLE)
Trying the fix permissions thing now, will post the results.
Good luck,
Well I will say that when I was using faux's kernel I had the issue, but now since installing Alien 4 and using the stock kernel, I have not had the issue (knock on wood). I still kringe every time I reboot because I use a few small widgets and it is a pain setting them up especially when you are on the go.
But my point is that it may have something to do with the kernel mod. I will Nandroid and install faux's latest and see what happens. If they disappear the kernel may be the culprit.
Alcapone263 said:
but there has been feedback to indicate one works better than the other for the widget problem.
Click to expand...
Click to collapse
Yes, I love the Romracer CWM but the fix permissions in it did nothing to fix the widget problems for me on other Faux kernels. The Rom Manager that was bundled with the Aura ROM fixed it first time (I tried everything else other than fastboot).
rpolansky said:
Yes, I love the Romracer CWM but the fix permissions in it did nothing to fix the widget problems for me on other Faux kernels. The Rom Manager that was bundled with the Aura ROM fixed it first time (I tried everything else other than fastboot).
Click to expand...
Click to collapse
I tried everything as well...for me apparently it was the way I unlocked the bootloader. I used the Pudding files to unlock my BL and when I tried using KP's unlock sbf it fixed my widget issues with all the faux kernel's.
See the details from this post http://forum.xda-developers.com/showpost.php?p=16508191&postcount=6 it's the only thing that worked for me. I did all the suggestions...flash stock sbf, fix permissions, wipe cache before installing the kernel in all possible method. If it was suggested I tried it and this is the only thing that worked for me.
Hopefully this helps.
gpagador said:
I tried everything as well...for me apparently it was the way I unlocked the bootloader. I used the Pudding files to unlock my BL and when I tried using KP's unlock sbf it fixed my widget issues with all the faux kernel's.
See the details from this post http://forum.xda-developers.com/showpost.php?p=16508191&postcount=6 it's the only thing that worked for me. I did all the suggestions...flash stock sbf, fix permissions, wipe cache before installing the kernel in all possible method. If it was suggested I tried it and this is the only thing that worked for me.
Hopefully this helps.
Click to expand...
Click to collapse
I guess it depends on which ROM one is on. I tried the reunlock above and no joy. It wasn't until I fixed permissions using ROM manager that it worked. 15 hrs and multiple reboots no loss of widgets or errors.
rpolansky said:
I guess it depends on which ROM one is on. I tried the reunlock above and no joy. It wasn't until I fixed permissions using ROM manager that it worked. 15 hrs and multiple reboots no loss of widgets or errors.
Click to expand...
Click to collapse
Hmm...this may be my problem. I've been using Romracer's recovery, but if people are saying it does nothing in terms of properly fixing the permissions, then I may have to try a different recovery.
Also, CaelanT, the -w command...is that done on the phone after you power up/hold volume down (to access the menu) or is it done through ADB or some other command interface?
Also, how deep does it wipe?
I'm glad to see people coming together and looking for solutions here.
Alcapone263 said:
Faux claims that it's a ROM issue, so i guess we dunno who the culprit is.
i do know that some people have luck using fastboot to clear their data/cache/dalvik, and other people have luck fixing permissions.
i've never had a problem with disappearing widgets, but i do have a problem with my widgets taking a while to load up. they'll be there, and none of their settings or features will work for a few minutes after random reboots. using CM7 on 0.1.9, i just take it as a small price to pay for having such an awesome kernel and ROM.
Click to expand...
Click to collapse
i'm almost positive it's his kernel. im running the stock rom, on his previous kernels (i haven't tried 1.9 yet because of this issue) i had this problem. when i switched to kholks kernel or the stock kernel i no longer had the issue despite being on the same rom.
xyrovice said:
Hmm...this may be my problem. I've been using Romracer's recovery, but if people are saying it does nothing in terms of properly fixing the permissions, then I may have to try a different recovery.
Also, CaelanT, the -w command...is that done on the phone after you power up/hold volume down (to access the menu) or is it done through ADB or some other command interface?
Also, how deep does it wipe?
I'm glad to see people coming together and looking for solutions here.
Click to expand...
Click to collapse
Use Rom Manager to fix permissions. Romracers doesn't fix the widget problem.
You will need moto-fastboot on your PC. Download here - http://forum.xda-developers.com/showthread.php?t=1138092 and unzip to the root of your C drive. Should be in C:\moto-fastboot.
For moto-fastboot -w, boot holding down volume, then press up volume when you see fastboot on your phone.
Connect phone to PC via USB.
Open a cmd prompt on your PC and type cd C:\moto-fastboot
Type moto-fastboot devices (Your phone should show up if you are connected).
Type moto-fastboot -w (Your phone will be wiped like a data/factory reset wipe, but it appears to be a deeper wipe. Internal SDCard and ext-SDCard should not be touched).
Type moto-fastboot reboot (Phone will reboot).
Note where there are spaces in the commands above!
legion21 said:
i'm almost positive it's his kernel. im running the stock rom, on his previous kernels (i haven't tried 1.9 yet because of this issue) i had this problem. when i switched to kholks kernel or the stock kernel i no longer had the issue despite being on the same rom.
Click to expand...
Click to collapse
I think so too because I did a fruitcake gbread reload and no problems with stock. I then loaded the Faux 1.3OC kernel and widget problems again.
Using fastboot for the deep clean makes a lot of sense. Next time I switch roms this is what I am going to do.
Hi there again,
Well, I just confirmed that the Rom Manager - Fix Permissions method works, at least for my combination of hw, Kernel and Rom.
Tried fixing via CWM without results, downloaded Rom Manager from the Market, Fixed the permissions using it, re-added my widgets and 3 boots aftear they are all there.
Again, I have the following:
Brazilian Atrix - d00 Tegrapart
nCrust 0.7 ROM
faux Kernel 0.1.9 (working rock solid at 1.3GHz AND undervolted).
Hope it helps.
sandro.bertini said:
Hi there again,
Well, I just confirmed that the Rom Manager - Fix Permissions method works, at least for my combination of hw, Kernel and Rom.
Tried fixing via CWM without results, downloaded Rom Manager from the Market, Fixed the permissions using it, re-added my widgets and 3 boots aftear they are all there.
Again, I have the following:
Brazilian Atrix - d00 Tegrapart
nCrust 0.7 ROM
faux Kernel 0.1.9 (working rock solid at 1.3GHz AND undervolted).
Hope it helps.
Click to expand...
Click to collapse
the fix permissions didnt work for me on the older versions of his kernel, but im not using it now anyway so i can't say about the current version
Im having this same disappearing widget problem despite fixing the permissions via rim manager... im on fauz1.7 tho running alien... I can't seem to find 1.9 tho iv looked everywhere ... can anyone post the link for faux 1.9...??
DrunkFuX666 said:
Im having this same disappearing widget problem despite fixing the permissions via rim manager... im on fauz1.7 tho running alien... I can't seem to find 1.9 tho iv looked everywhere ... can anyone post the link for faux 1.9...??
Click to expand...
Click to collapse
http://rootzwiki.com/showthread.php...Unified-v0.1.9)OC-1.3GHz-SLQB-BFQ-EXT4-Aug-27
Alright so despite fixing permissions and the whole shenanigans faux 1.9 just isn't working for me... on alien v4... and its definitely a kernel related issue not anything else... 1.7 works fine but at times gets moody and goes crazy... hope this issue is fixed soon...
Sent from my Motorola Atrix

Getting WLODs with PSX4Droid

I installed PSX4Droid 3.0.5 on my X10 and configured it. Then I loaded the Digimon World 2003 ROM.
After successfully playing the game for ~40min. I decided to install the 3.0.6 version, but then the game wouldn't load and I started getting WLODs.
I tried going back to the previous version of the app but the problem persisted.
I even went to xRecovery to make a Restore and then installed the app again, but I still get those damn WLODs every time I try to load the ROM -.-
Does anyone know what might be causing this and how to solve it?
AX10i said:
I installed PSX4Droid 3.0.5 on my X10 and configured it. Then I loaded the Digimon World 2003 ROM.
After successfully playing the game for ~40min. I decided to install the 3.0.6 version, but then the game wouldn't load and I started getting WLODs.
I tried going back to the previous version of the app but the problem persisted.
I even went to xRecovery to make a Restore and then installed the app again, but I still get those damn WLODs every time I try to load the ROM -.-
Does anyone know what might be causing this and how to solve it?
Click to expand...
Click to collapse
Which kernel are you on?
Any overclock/undervolt?
Also which governor do you use?
WLOD indicates kernel panic.
DoomKernel 4b
No overclock, nor undervolt.
I use smartass v2.
Sent from my X10i
AX10i said:
DoomKernel 4b
No overclock, nor undervolt.
I use smartass v2.
Sent from my X10i
Click to expand...
Click to collapse
Try another governor, like ondemand or interactive. You could also briefly go back to stock kernel just to check if the problem is solved!
Did all that but still it didn't solve the problem. :/
It was working fine at first. I don't get what went wrong :s
Sent from my X10i
AX10i said:
Did all that but still it didn't solve the problem. :/
It was working fine at first. I don't get what went wrong :s
Sent from my X10i
Click to expand...
Click to collapse
Even going back to stock kernel didn't solve it?
No. And I even went to stock firmware.
Sent from my X10i
Have you tried wipe its data?
(only by this app)
Or even if it doesnt affect it, dalvik-cache. Because it seems to be related with some new configuration.
Yes, I wiped its data as well as dalvik-cache.
Sent from my X10i
Hmmm... Very strange - i cant understand it.
If cache and dalvik is wiped, it is almost as factory reset (have you tried factory reset?).
Last thing you could do is repair via SEUS. If it doesnt help, it means, that your hardware is damaged (possible not caused by software).
Or optionally, enable USB debug and run logcat from your computer -> cause WLOD and post here log.
Are u tried another bios file?
Sent from my xperia "z10i"
Yes, I did try replacing the BIOS file as well as the game .bin & .cue files.
Earlier I deleted the data again and ran it without configuring. Surprisingly, it worked. Then, while in-game, I went to the Settings and configured it. When I got out of the Settings it was still working and I kept on playing with my configurations. I saved the game state, exited the app and ran it again. It was still working.
Then I rebooted my X10, but when I tried running the game again... WLOD -.-
Sent from my X10I
HeliumX10 said:
Or optionally, enable USB debug and run logcat from your computer -> cause WLOD and post here log.
Click to expand...
Click to collapse
It's attached.
I'm sorry if it's longer than it should be, but I didn't want to risk deleting important lines.

[Q] error trying to install ICS Passion v13

Hi ,
when i try to flash my phone using the rom "ICS Passion v13"
i have these errors :
E:Failed to verifity whole-file signature
E:signature Verification Failed
Installation aborted
Download fresh, try again.
Sent from my SGH-T959 using XDA App
Redmartianducky said:
Download fresh, try again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I did not understand what you say ?
My first inclination would be a bad download, try a different dl location and try again.
Sent from my SGH-T959 using XDA App
Redmartianducky said:
My first inclination would be a bad download, try a different dl location and try again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
i have tryed with another rom , same problem
Where in the process are you getting these errors? There are multiple steps to installing ICS that this could occur. What ROM are you running right now? If stock, is it 2.1 or 2.2? Do you have CWR installed? Is it installed with Update.zip or through ROM Manager? Did you flash CM7 before ICS?
Simply putting that you got this error is not enough information for us to diagnose and help.
Edit::: also please don't spam the other posts with "Good" or "Great to hear that" to get your post count up like was done in Themes and Apps section. There are many threads to that you can post in to get the count up legitimately.
Woodrube said:
Where in the process are you getting these errors? There are multiple steps to installing ICS that this could occur. What ROM are you running right now? If stock, is it 2.1 or 2.2? Do you have CWR installed? Is it installed with Update.zip or through ROM Manager? Did you flash CM7 before ICS?
Simply putting that you got this error is not enough information for us to diagnose and help.
Edit::: also please don't spam the other posts with "Good" or "Great to hear that" to get your post count up like was done in Themes and Apps section. There are many threads to that you can post in to get the count up legitimately.
Click to expand...
Click to collapse
hi ,
i have the stock rom (2.2) CWR is not installed , i have not Flash CM7 before ICS
That is the problem. Go to my guide in the General or in my sign and follow it.
it rooted? you have the right CWM rec on it? im not a pro but i know that might be it
You must install CyanogenMod 7 before install a ICS rom.
it's the best form if you dont wanna have problem with the bootloader and bricked your phone!!
I suggest you start here:
http://forum.xda-developers.com/showthread.php?t=849028
ascallop said:
I suggest you start here:
http://forum.xda-developers.com/showthread.php?t=849028
Click to expand...
Click to collapse
hi ,
i have use your link for installing ICS , i have do it .
but i have a problem :
when i click on any thing i have this : Unfortunatley , The process android.process.media has stopped ?
how i fix this ?
After installing it, did you let it settle for 20 minutes before using the phone?
If you did, try flashing again, or download the rom again.
Sent from my SGH-T959 using XDA App
I happen to me the first time I load the Passion 13. So I delete the passion zip file from where I will load it (download folder in my case), then redownload the passion 13 zip file and copy it to the download folder. It works for me.
Jacendb said:
After installing it, did you let it settle for 20 minutes before using the phone?
If you did, try flashing again, or download the rom again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
hi ,
i didn't wait
so i try to reflash .
paranoxxx said:
hi ,
i didn't wait
so i try to reflash .
Click to expand...
Click to collapse
this is what i did, when helping my friend boot it up,
you have to make sure your rooted
then install ClockWorkMod recovery onto the phone,
then install CM7 after it boots back to recovery
then wipe data and cache
then install ics passion wait for it to boot all the way back to recovery for the last time
install the clean up patch and the phone will work perfect
i had the same problem, thats what i had to do make sure it worked perfect
Jacendb said:
After installing it, did you let it settle for 20 minutes before using the phone?
If you did, try flashing again, or download the rom again.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
what if you didn't let let it settle for 20 minutes? I didn't most of thing seems alright, except that the dial keys seem to be sticky if I hold it a hair too long, like when you try to do quick dial, the key will stay selected and you can't dial other numbers until it unstick.
I'm using Passion 13, not sure if I have kiss 2.2.
A question for everyone: can't Passion 13 or ICS for Vibrant in general let you assign phone number for quick dial? You have to use direct dial widget?
paranoxxx said:
when i click on any thing i have this : Unfortunatley , The process android.process.media has stopped ?
how i fix this ?
Click to expand...
Click to collapse
Usually a boot into recovery, fix permission and wipe cache and dalvik cache will clear this up. But sometimes it is just a bad download too.
Kaptinkrunk said:
this is what i did, when helping my friend boot it up,
you have to make sure your rooted
then install ClockWorkMod recovery onto the phone,
then install CM7 after it boots back to recovery
then wipe data and cache
then install ics passion wait for it to boot all the way back to recovery for the last time
install the clean up patch and the phone will work perfect
i had the same problem, thats what i had to do make sure it worked perfect
Click to expand...
Click to collapse
This is a Guide on putting ICS ROMs on your Vibrant that explains everything.
ciditin said:
what if you didn't let let it settle for 20 minutes?....
I'm using Passion 13, not sure if I have kiss 2.2.
Click to expand...
Click to collapse
It is always a good idea to let the phone go through a "settling" period after you flash it. There are RAM tweaks to finish, media scanning and a host of other things that need to be completed as you just installed a completely new operating system on your phone. Especially don't log into Market or Titanium and start restoring as this can cause problems long term. What is 20 mins compared to problems and hassles for the next few days/weeks.
If you don't know if you have Kiss 2.2 on your phone, then you don't have it b/c you have to flash it. See HERE

[Q] Random reboots in Miracle V4?

Hi guys
I was using Miracle V4 for some weeks but now I switched to MIUI GB.
I flashed Miracle V4 on my gf's galaxy Ace. She loves it but there's a big problem.
Sometimes her Ace reboots - well, not, it doesn't reboot, it just get to the bootanim and then return to the desktop, without asking for a PIN or anything.
It's very ennoying. Do you have an idea about that? I tried to reflash, didn't worked.
She has a lot of games, maybe that's the cause of the problem?
Another rom could solve the problem?
Thanks !
This usually happens to me when I overclock my phone to an unstable frequency.
If its not overclocked try clearin ram.
Jean1501 said:
Hi guys
I was using Miracle V4 for some weeks but now I switched to MIUI GB.
I flashed Miracle V4 on my gf's galaxy Ace. She loves it but there's a big problem.
Sometimes her Ace reboots - well, not, it doesn't reboot, it just get to the bootanim and then return to the desktop, without asking for a PIN or anything.
It's very ennoying. Do you have an idea about that? I tried to reflash, didn't worked.
She has a lot of games, maybe that's the cause of the problem?
Another rom could solve the problem?
Thanks !
Click to expand...
Click to collapse
Try flashing TheAceKernel BETA 4 Non OC. I used to have the same problem when using the kernel which is included in the package. Then I switched to OC version of TheAceKernel, I didn't OC but problem was still persist. So I switched to non OC TheAceKernel and the problem has gone!
Sent from my WAREZ impulses.
Have you partitioned the sd card?
I had the problem
If the sd card speed is not sufficient the phone will reboot
Be Kind everyone you meet is fighting a hard battle
yeowwwai said:
Try flashing TheAceKernel BETA 4 Non OC. I used to have the same problem when using the kernel which is included in the package. Then I switched to OC version of TheAceKernel, I didn't OC but problem was still persist. So I switched to non OC TheAceKernel and the problem has gone!
Sent from my WAREZ impulses.
Click to expand...
Click to collapse
Just flashed it, waited for about 30mn and it just did the same. Wasn't OC'd at all...
Should I underclock?
That's really ennoying guys. What other CM-based rom should I try?
ive been with v4 for almost a month..but havent exprienced any random reboots..try doing a full clean flash..
full wipe then flash a fw package through odin and then flash any rom u like..kinda hussle..but works for me evrytime..
Sent from my GT-S5830 using XDA
Ok guys, still experiencing the same problem, reflashed a stock rom via ODIN, formated SD card (class 4 actually) in FAT32, reflashed Miracle V4, restored some apps via TITANIUM Backup, waited for around 1h, was watching TV without touching the phone and... rebooted. Now it's stuck on bootanim, with or without SD card, still the same.
It did the same with Official CM7.2 (last nightly), with or without OC kernel.
I didn't overclocked at all.
Maybe an app is the cause of the problem?
Or maybe the gorvernor, SmartassV2, I really dont know.
Please heeelp
Hmmmm very strange the problem persists even after flashing via Odin
Check your apps and see delete some which you never use and error check sd card in computer ^sd card drive ^properties
Try to start from scratch
Flash your rom and personalize it manually like installing each app from market
Idk any other solution wait for a better one
EDIT : Does this happen to every rom?
If not then you might as well use a different one
Be Kind everyone you meet is fighting a hard battle
jumbobombo said:
Hmmmm very strange the problem persists even after flashing via Odin
Check your apps and see delete some which you never use and error check sd card in computer ^sd card drive ^properties
Try to start from scratch
Flash your rom and personalize it manually like installing each app from market
Idk any other solution wait for a better one
EDIT : Does this happen to every rom?
If not then you might as well use a different one
Be Kind everyone you meet is fighting a hard battle
Click to expand...
Click to collapse
It happened on 3 or 4 CM-based rom, now trying a stock one.
I'll try to reinstall everything from market and I'll see if it works.
Errors checked on SD card, nothing found.
Ah and, I restored from a backup of 05/05/12 via CWM, it seems to work now (FrozenAceTeam CM7), let's wait.
I deleted all useless apps and games. W8 and see...
Ok guys, now after formating SD, reflashing stock via Odin, reflashing Miracle V4, reinstalling everything manually, the problem persists. That's really ennoying.
It just happened twice right now. No new ideas?
EDIT : Something new! now it reboots, shows "process com.android.phone closed etc..." during a half a sec, and reboot again... What about it?
im using a few weeks and not have trouble its amazing rom
alefpiro said:
im using a few weeks and not have trouble its amazing rom
Click to expand...
Click to collapse
I think we're finally all OK to say that the ROM isn't the cause of the problem in my case.
does it reboot when u use stock fw?
Sent from my GT-S5830 using XDA
das.dian24 said:
does it reboot when u use stock fw?
Sent from my GT-S5830 using XDA
Click to expand...
Click to collapse
I think it doesn't. Never happened while using one in the last 2 days.

Categories

Resources