i own a desire s ... i tried to flash the same wit galnet miui stable 2.11.26...after flashing the mobile is stuck with boot up animation itself.. can you guys help me in solving the issue.
http://galnetmiui.co.uk/landing/ics-builds/
please check whether its working for you...
Flash weekly build, then ICS build on top.
In future, do some googling or at least use some common sense and have a look at their forums, its been answered so many times.
Also you don't need to post this about a hundred times through different forums.
1. Download weekly (regular galnet MIUI build).
2. Boot into galnet MIUI build.
3. Shutdown phone, and return to recovery.
4. Flash ICS build.
5. Pursue an optometrist to purchase a pair of glasses.
Sent from my Galaxy Nexus using xda premium
dude FYI already tried tat and ended with the same stuff...but jst now got it working...
via tis forum...
http://www.sammobile.com/forum/showthread.php?t=895
Hello Folks,
I am stuck with Samsung-Infuse Here ...
Previously I was on CatyRom - 2.3.6 on infuse .. but seems it broke the phone capabilities .. I was not able to install most of the applications from the market... even the basic applications like "Facebook" / "Google Apps" wouldn't get installed..."device incompatible" or something like that it would pop in the "Market" itself...
so after a few tries... I have finally reverted back to the Stock ROM...Thanks a ton to gtg for this post.... ) atleast finally the things are working...
http://forum.xda-developers.com/showthread.php?t=1112555
But it's FROYO... ( I'm currently on UCKE3...
I tried getting the OTA version from AT&T ... through manual update .. and *#*#checkin#*#*.... but somehow that was not able to get me the update...
So currently I am trying to flash the ROMS mentioned in this post
http://forum.xda-developers.com/showthread.php?t=1293751
ROM I997UCKK3 [2.3.6]
ROM I997UCKK2 [2.3.6]
[CUSTOM ROM] Compiled CM 7 for Infuse 4G [2.3.7]
I've tried flashing through ODIN .. as well as through "sdcard/update.zip" but none seems to be working out for me...
even tried getting the firmware-update using the "Kies" & "Kies-Mini" especially launched for Infuse customers... but none seems to work ...
Can someone please help me out with this one... ?
Thanks,
/P
there is no official gb. only leaks.the last leak was uckl2.
once on uckl2 you might not be able to root it, you will have to swap Kernels around. might want to flash Zeus instead unless you really want cm7.
you need cwm to flash the roms, most roms don't have an update script that works in stock recovery. fastest way to cwm is to flash a voodoo kernel in sgs kernel flasher or Odin or heimdall. if you have root use kernel flasher.
or you can do it the slow way and replace recovery with a modded version, then use green cwm for the i9000 via update.zip.
I am looking for a snappy ROM which works fast .... not looking specifically for CM7...
I decided on CM7, from the reviews of other folks .. lot's of folks are returning back to CM7 after trying out "Infuse" / sensation .. and "Caty"... so was just wondering what would be the best option ..
I am looking for a stable version; as I do not flash often ... I would stick to a stable version for a little longer then flash all the new updates/leaks that keep coming..
pvaniawala said:
I am looking for a snappy ROM which works fast .... not looking specifically for CM7...
I decided on CM7, from the reviews of other folks .. lot's of folks are returning back to CM7 after trying out "Infuse" / sensation .. and "Caty"... so was just wondering what would be the best option ..
I am looking for a stable version; as I do not flash often ... I would stick to a stable version for a little longer then flash all the new updates/leaks that keep coming..
Click to expand...
Click to collapse
Dani already said what needs to be said. Looks like you missed it. I'll reiterate..
ZEUS
Sent from my SAMSUNG-SGH-I997 using Tapatalk
Hello!
I flashed CM9 RC2 recently and now whatsapp doesn't work. I get warning after installing it saying that custom rom might cause whatsapp not to work properly. After starting whatsapp it simply closes down.
Before CM9 RC2 i used HyperSensation Rom (2.9 i think), and it worked normally without any problems.
Is there anything i can do to get this to work besides reflashing ROM?
Thank you.
Delete the data of the app.. Un-install it and install it again that might help
Sent from my pyramid using blazing fast sonic waves
Tried that several times. Problem still persists.
EDIT: Just to report. Eventually i installed latest AOKP rom from their site (Milestone 6), and it works fine now.
ive had this same problem. I am usuing the CM9 RC2 right from the cyanogen mod website for samsung captivate ATT. if i install the AOKP rom you think it will work. and if i do whats the difference between AOKP build 40 and milestone 6.
edit: ok i installed milestone 6 and still did not work. what the hell
hshaikh said:
ive had this same problem. I am usuing the CM9 RC2 right from the cyanogen mod website for samsung captivate ATT. if i install the AOKP rom you think it will work. and if i do whats the difference between AOKP build 40 and milestone 6.
edit: ok i installed milestone 6 and still did not work. what the hell
Click to expand...
Click to collapse
AOKP builds marked with number (for example: build 40) are something like beta builds and are more likely to have bugs. Milestone builds are more stable releases.
Regarding problem with whatsapp. Seriously i dont know why is this happening. I tried searching net and found couple guys with same problem but nobody offered solution. As i said in my first post, i used hypersensation which was build on one of earlier CM9 releases and it worked fine. So i would suggest to try some earlier releases of AOKP or CM9 or some rom from XDA based on them.
could you please provide me with a link to the rom you used. i will try that one
Here is hypersensation. However i used 2.9 version based on CM9, current version is 3.1. Download is in post 2. In post 3 you can find AOKP roms, but i haven't tried these.
I am using a samsung Captivate. will this rom work for me
My guess is no. You should probably go to Samsung Captivate forum and check there. I don't know anything about Captivate.
UPDATE: After a few additional tweaks to the framework, this rom appears to be working for both green and red lens defy users. I've personally used it as my daily driver for several days this week, and found it to be stable and very usable. The one thing that does not work for me is the GPS, and quite honestly, I haven't had time to look in to it.
Here is a complete, working port of PARANOID ANDROID 1.97a for Defy. It is based on Galaxy S2 PARANOID 1.97 and Epsylon's CM10 1208. This is NOT a simple port using the port tool and includes the Framework changes necessary for the hardware.
I take no responsibility for any consequences from your decision to try this rom, and being based on alpha releases, I'm sure there are other problems, but I've personally used this rom for a prolonged period of time and the only problem I've had was with the GPS not locking.
Few things to note:
1. No offense to anyone, but this thread is not for complete noobs. While I will try to help when I can, I cannot promise any level of support. If you don't know how to flash via CWM, this is not for you.
2. This rom is based on the Froyo kernel and has been confirmed to work on MB525 with green as well as red lens. This is no guarantee that it will work on YOUR phone.
3. I intentionally used 1.97 as that version was very stable on my Galaxy Nexus - much moreso than 1.98 or 1.99
4. I've cleared the PARANOID defaults that most of the other PA roms come with. You can manually change the individual app settings under Paranoid Settings, or via the \system\etc\paranoid\properties.conf file which stores a record for every app including DPI and Layout.
5. After installing this rom, I "supercharged" it using a v6supercharger script (link below) and it did seem to help make the rom smoother and more responsive.
Special thanks to Epsylon3 and Quarx for their work on CM10 for the Defy, and Molesarecoming and D4rKn3sSyS for their work on PARANOID.
Thanks to brajesh.sharma87 for pointing out the bootloop "gottcha" of simply recompiling the framework (for specifics google "framework recompile bootloop" and read the first thread that comes up).
I strongly encourage any/all of you to contribute (make donations) to these developers.
DOWNLOAD ROM (double check MD5 before flashing - 96D409B4692319D9DA63FAA9CE1516A6)
Download latest gapps from here.
Here is the v6 supercharger script that I've been using and is confirmed to work with this rom.
Make sure you're on Froyo kernel. Boot in to CWM recovery. Factory reset, wipe data/cache/dalvik. Install rom, followed by gapps. Wipe data/cache/dalvik again. Reboot (should take about 2-5 minutes). Install and configure the v6 script. Enjoy!
Looks pretty neat man! I might give it a shot soon. Any known bugs for now?
This is only PA rom which I manage to get work on my red lens defy without bootloop..
Cheer mate..:good:
now testing..
hm md5 matches, flashed it several times but it cant pass bootanimation :/
(edit: green lense defy)
here tooo stuck at endless bootanim...
o-liver said:
hm md5 matches, flashed it several times but it cant pass bootanimation :/
(edit: green lense defy)
Click to expand...
Click to collapse
meilbox said:
here tooo stuck at endless bootanim...
Click to expand...
Click to collapse
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
dew.man said:
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
Click to expand...
Click to collapse
bro if kernel was wrong they would have stuck at Moto logo not bootanim...
same with my builds too and the reason y i did not update my thread...
I made paranoid too but never boot... libandroid.runtime has errors as per logs...
and m in no mod to fix it for now...
Sent from my MB526 using xda premium
dew.man said:
Are you guys running Froyo kernels? Did you do a full wipe of data, cache, and dalvik after the install?
Trying flashing the CM7 kernel, this rom, wiping, and booting right away before you install gapps or anything else. And make sure you give it a full 5 minutes as the first boot can take some time.
Also keep an eye on the led by the proximity sensor. Let me know if it flashes red when it loops.
Click to expand...
Click to collapse
did everything what i could, and my led does not flash in red...
nogoodusername said:
bro if kernel was wrong they would have stuck at Moto logo not bootanim...
Click to expand...
Click to collapse
good point.
nogoodusername said:
same with my builds too and the reason y i did not update my thread...
I made paranoid too but never boot... libandroid.runtime has errors as per logs...
and m in no mod to fix it for now...
Click to expand...
Click to collapse
Sorry, didn't even see your thread. Quite honestly, I've only been playing with PA for the last couple of weeks and have posted in rajesh.sharma87 thread as well as the rom porter thread, but nobody over there seems to want to read.
Have you looked at the logs from the devices that loop? Send me one if you have an example. I've tried lots of different combinations in conjunction with the framework-res mods before I got this to boot, but have not had any problems with this version. Interesting...
dew.man said:
good point.
Sorry, didn't even see your thread. Quite honestly, I've only been playing with PA for the last couple of weeks and have posted in rajesh.sharma87 thread as well as the rom porter thread, but nobody over there seems to want to read.
Have you looked at the logs from the devices that loop? Send me one if you have an example. I've tried lots of different combinations in conjunction with the framework-res mods before I got this to boot, but have not had any problems with this version. Interesting...
Click to expand...
Click to collapse
well paranoid jb(gb kernel) no boot for me at all...
havent tried urs m on gb kernel...
i dont have logs m on cm10
i m thinking of setting up git for paranoid... but my internet...:thumbdown:
Sent from my MB526 using xda premium
nogoodusername said:
well paranoid jb(gb kernel) no boot for me at all...
havent tried urs m on gb kernel...
i dont have logs m on cm10
i m thinking of setting up git for paranoid... but my internet...:thumbdown:
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL6 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
dew.man said:
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL7 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
Click to expand...
Click to collapse
How can you be on BL7 and still be able to switch to Froyo kernel?
niksy+ said:
How can you be on BL7 and still be able to switch to Froyo kernel?
Click to expand...
Click to collapse
My bad - it's BL6.
And for those that don't know, there was a leaked Froyo SBF with BL7 (see here).
dew.man said:
If you're on Defy red lens, I'd be curious to have you try this rom. I'm starting to think it may be a difference in the hardware.
I'm on BL6 (flashed GB when first leaked), but have been going back and forth between GB and Froyo kernel roms and found Epsy's to be most stable for my device (which is why I used his as the base).
Click to expand...
Click to collapse
no the kernel has difference...
gb kernel has many missing libs!
Sent from my MB526 using xda premium
Hi dew.man, if u want to continue this, I will close my thread as u know there's no need of having multiple threads for the same work. The intention of the guide and the tool was to let everyone port and use and not polluting the developement thread by posting so many threads. I hope u get my point. If u really wish to take this up I am there with u and will provide u as much help as I can but at the same time we need to respect xda.
Opinion of other users are also welcome so that we can keep the developement thread clean. I've already closed 2 of my threads for the same reason. LewaOS and AOKP JB.
Sent from my MB525 using xda app-developers app
cant acquire logcat, its waiting for the device :/
o-liver said:
cant acquire logcat, its waiting for the device :/
Click to expand...
Click to collapse
dude goto bootmenu-boot-adb enable
press 2nd-init
and logcat...
Sent from my MB526 using xda premium
brajesh.sharma87 said:
Hi dew.man, if u want to continue this, I will close my thread as u know there's no need of having multiple threads for the same work. The intention of the guide and the tool was to let everyone port and use and not polluting the developement thread by posting so many threads. I hope u get my point. If u really wish to take this up I am there with u and will provide u as much help as I can but at the same time we need to respect xda.
Opinion of other users are also welcome so that we can keep the developement thread clean. I've already closed 2 of my threads for the same reason. LewaOS and AOKP JB.
Sent from my MB525 using xda app-developers app
Click to expand...
Click to collapse
First and foremost, thanks for all your help
Perhaps I was not clear enough, but I do not have the free time to take on any kind of support role. Please understand that my sole intention of this thread, was to provide/share a more recent version of PA/CM10 that I have been unable to obtain from anybody else. No offense intended, but I did ask you on several occasions to post a more recent version than the 1.95 you have in your (still existent) thread, and the only response I received was that you didn't have the bandwidth.
I also tried to work through/with kadevil's thread, but he pretty much ignored all the feedback he was getting about the tool not working for PA and JB.
Again, I was looking for a more recent version of PA (1.97+) with a more recent CM10 (8/06+) and was unable to find a working version. I built one that works for me, and wanted to share with anybody else that may be in a similar position...
Well guys i feel that the thread should be merged to brajesh's thread... since his thread has more organized 1st post...
no offence to op but thats wat i felt when i saw it...
peace
-hackergnome
Sent from my MB526 using xda premium
nogoodusername said:
Well guys i feel that the thread should be merged to brajesh's thread... since his thread has more organized 1st post...
no offence to op but thats wat i felt when i saw it...
peace
-hackergnome
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
I'm perfectly fine with that as long as the op/title gets updated with the new version number
Hi
Not sure where to post this. Want as much exposure as i can get for a fast fix.
Basically, I have tried two custom roms:
AOKP JB rom
Paranoid Android
I would have stuck with any of these, but the AOKP rom would switch from Loudspeaker to normal during a phonecall. And the Paranoid Android has too many bugs in it that I cant run it without getting annoyed with the force closes etc.
Im now looking for either:
A FULLY WORKING CUSTOM ROM
or
AN OFFICIAL HTC ONE V STOCK ROM
hope you can point me to the right direction?
Thanks,
Maybe you should post this in the one V specific forum? You'll get way better answers there.
Sent from my One V using xda premium
antwonpjmj said:
Hi
Not sure where to post this. Want as much exposure as i can get for a fast fix.
Basically, I have tried two custom roms:
AOKP JB rom
Paranoid Android
I would have stuck with any of these, but the AOKP rom would switch from Loudspeaker to normal during a phonecall. And the Paranoid Android has too many bugs in it that I cant run it without getting annoyed with the force closes etc.
Im now looking for either:
A FULLY WORKING CUSTOM ROM
or
AN OFFICIAL HTC ONE V STOCK ROM
hope you can point me to the right direction?
Thanks,
Click to expand...
Click to collapse
The best way is to go forum of ur phone. Do a little bit of research in the threads and then install the custom rom of your choice!
You'll also get links of stock rom from the phone's forum...
Search ur phone on top right corner box.. And then see android development section!
Sent from my GT-S5830i using xda app-developers app
antwonpjmj said:
Hi
Not sure where to post this. Want as much exposure as i can get for a fast fix.
Basically, I have tried two custom roms:
AOKP JB rom
Paranoid Android
I would have stuck with any of these, but the AOKP rom would switch from Loudspeaker to normal during a phonecall. And the Paranoid Android has too many bugs in it that I cant run it without getting annoyed with the force closes etc.
Im now looking for either:
A FULLY WORKING CUSTOM ROM
or
AN OFFICIAL HTC ONE V STOCK ROM
hope you can point me to the right direction?
Thanks,
Click to expand...
Click to collapse
Hate to tell you this but custom roms will always have bugs. This is why all roms are considered beta and some even alpha builds.
You have to remember this is a development site where developers try new things to see what breaks. This is not a roms site
Wayne Tech S-III