- So I was updating to Quarx's 5th Nov build (2ndboot) and in the middle the flash my phone turned off and decided not to start up. (The battery WAS NOT drained)
- I started with this guide in order to get it back to life:
http://forum.xda-developers.com/showthread.php?t=1807899(I used the exact same files, even the sbf. I live in India and I couldn't find India's sbf in this list: http://sbf.droid-developers.org/umts_jordan/list.php)
- Everything went as excepted and I was back on 2.2.2, so I tried to flash Quarx's build again. (I installed gapps, and cleared everything twice, thrice). However, the phone stuck on a bootloop:
red Motorola logo -> blue led -> greend led -> blank screen -> repeat.I cleared the cache's, factory reset, etc etc. No use.
- So i followed the original method again to get back to 2.2.2 and then flashed ICS from Cyano's website. It worked! So I tried again to flash a CM10 release, but this time a PRE-2ndboot build - 24th Sep.
It didn't work either. So JellyBean is the evident problem, but it doesn't make any sense, right?
- I started agin and tried to flash a different sbf, I got to this thread:http://forum.xda-developers.com/showthread.php?t=1093352 and tried the sbf provided (they claim it to be the one for SEA, including India). However, even after doing a factory reset from the stock recovery and flashing this sbf, I got a brick. The phone won't start whatsoever. No bootloader, no recovery - zilch. Dead.
- I again went back to my original method and got back to ICS...Flashed JB -> Same bootloop as before.
- Somethings I have noticed:
1. On flashing, the internal memory shrinks to only 128MB. I tried a factory reset from within the phone, from custom recovery and from the stock recovery. The memory was still 128MB with about 40MB free.
2. When I return to stock, the phone is somehow pre-rooted. On running superOneClick it shows that it;s already rooted but I continue nonetheless.
3. I think MAYBE the low internal storage might be at fault since JB Gappa require a lot of space.. I have tried it with minimal gapps too.
4. I have flashed every sbf available for Asian countries...but the only one that works is the one from the first link provided.
5. The only thing I can do right now is get to 2.2.2 or ICS...So if someone can help me out, that's my current status.
PS - I have been at it for 3 straight days, so yea, I have tried just about everything and read every thread regarding this. I even had to jump start by battery once as it ran out in the middle of a sbf flash.
There s a chance you didn't installed JB the right way. Also you ca install it without Gaaps. Does 2nd boot got enabled in Bootmenu? Did you flashed the kernel accordingly?
if you have bl4 try one of my fixed sbf with 2ndboot
ex. 28.11JB.Quarx+jellyX.kernel
than make a data and cache format fom bootmenu
bootmenu/ CPU settings/ system tools/ format data and cache to ext3
reboot
hve the link in my signature
I think you need bl. 4 from an 2.3.4 sbf for defy
In my country there was as an official update to GB
Users posted prblems with bootloader 3 and 7 @ quarx cm10 2ndboot roms
MB525 red lense
Hi,
You can take one more try (if you wanna ) to flash 12.09 JB build - it shall work
If so then flash Nordic retail 2.2.2 or WE retail (U3_3.4.2-177 or 179 from here)and try again 2ndboot builds (for some sbfs the last pre 2ndboot, 24/09 was the first not working)
Flash then 5/12 and jb gapps, wipe dalvik cache and cache after flashing.
Concerning 128 MB free memory - I suppose you are talking about data partition, not a system. Of course it is too small - the same as prerooted phone - try another sbf
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
vinu.shukl said:
Okay, just to clear the air - I was running Quarx's 28th Nov build before this happened.
I solved the 128MB problem. I'm currently on ICS 4.0.4 on the 16/07 CM9 build. It now shows 1.7GB internal available.
The kernel version shows 2.6.32.9-gb08c3c8xxxx..xxx.
I'm going to try and flash the 5/11 CM10 build (2ndboot). But before that I would to confirm the procedure:
1. Custom recovery
2. Data/Factory Reset
3. Clear cahce, Dalvik cache
4. Flash 05-11
5. Flash gapps (?) gapps-jb-20121011-signed.zip?
6. Clear cache, dalvik
7. Reboot
Should I go ahead with this?
PS. I reached my current state by flashing the sbf and firmware provided in this post: http://forum.xda-developers.com/showthread.php?t=1807899
I'll wait till someone approves of this, I don't want to brick it again.
Click to expand...
Click to collapse
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Click to expand...
Click to collapse
These are the sbf's I found pertaining tp your specifications:
http://i.imgur.com/muQdT.jpg
EDIT: But they are all in the DEFY-PLUS repository...can I flash them?
So I can use anyone of them?
Also, I don't know much about BL versions...So should I just download one of the above sbf's and flash it using RSD? Do I need a nandroid backup to go with it too?
The procedure I would follow would be:
1. Factory reset, clear cache's
2. Go into bootloader menu
3. Flash above sbf using RSD
4. Reboot ??
Should that suffice?
First: if you are red lense it is ok to flash BL6
If you are green lense, to have your camera working, you will need 2ndboot builds (CM9, 10 or 7)
You will probably need red lens battery fix to show correct percentage, no matter you have green or red lense then.
You can flash it even later, after flashing CM10 and gapps and checking how it works
I would choose Nordic retail
Sometimes you can have problems with rooting with SuperOneClick (version 2.3) - force close Motorola Portal before rooting and it shall work ok then
And nandroid backup is not very useful when changing BL version, at least you will not be able to restore all
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
vinu.shukl said:
I have a green lens MB525.
So I'm downloading Nordic Retail for MB526 and will flash it using RSD.
After that, I can straight away flash any cm10 build right? (like the latest 5th Nov)
Click to expand...
Click to collapse
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
corrinti said:
Yes, just normal procedure with rooting and 2ndinit installation, then flashing CM10 and jb 4.1 gapps with all proper wipings
And as mentioned above probably battery fix will be required for proper percentage - you will see
Click to expand...
Click to collapse
Okay!
Gonna flash it tonight...Finger's crossed. =D
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
vinu.shukl said:
UPDATE: Flashed the Nordic Retail successfully. On stock 2.3.6 right now. Going to flash CM10-20121205-NIGHTLY-mb526.zip
UPDATE: I tried rooting it using SuoerOneClick v2.3.3.0 and even killed Moto Helper from PC and chose 'None' from the USB connection menu on the device. This is what I got:
http://i.imgur.com/cokl3.jpg and after reboot http://i.imgur.com/arZzd.jpg
SuperOneClick stopped responding after that. I waited 10 mins but nothing happened...No input requested from the device. tried it again but with the same results.
What should I do? Try z4root?
Click to expand...
Click to collapse
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
corrinti said:
You can try z4root, though I rooted it with SOC 2.3.1 without problem. It seems that rooting didn't even start. Try choose zergRush instead of Auto
Note that USB is changing to Motorola Portal every several seconds if you do not kill it from a phone and it stops the process. Go to app settings, choose all apps, force close Motorola Portal (or freeze it - do not remember if such option is available)
Have you choosed USB debug mode?
Eventually try factory reset from settings before rooting
Click to expand...
Click to collapse
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
vinu.shukl said:
Okay...I rebooted the phone and the PC and re-installed the Moto drivers...success!
Installing SndInitDefy_2.3.apk
UPDATE: Booted into custom recovery. Factory/data wipe. Cache, Dalvik wipe. Installing CM10-20121205-NIGHTLY-mb526.
Click to expand...
Click to collapse
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
corrinti said:
You are lucky :laugh: - for many users (probably depends on sbf flashed) SndInit 2.3 does not work, I still use 1.4.2
You can also flash this zip - it changes the ramdisk to the older version and helps in battery life
Click to expand...
Click to collapse
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
vinu.shukl said:
I guess I had some luck coming my way after a week of real hard times...
I'm currently restoring all my apps... Do I install this like any other zip i.e. clear cache + dalvik -> flash -> clear cache + dalvik ?
Also, since we are on the topic of performance, what are the optimum CPU settings?
I'm currently using:
1200,900,600,300 - 62,47,32,17
Interactive CPU Governor
SIO I/O Scheduler
No changes in the Memory Managment options (i.e. zRam, purginf of assests and kernel samepage merging - all are turned off)
16bit transparency turned off.
Click to expand...
Click to collapse
The ramdisk zip is to be installed in a standard way, like any other zip, probably doesn't require wiping caches, but probably
I usually use zRam (18%) - I didn't notice any bigger battery drain.
KSM off
WiFi - change to never when screen is off - you can have wifi on all the time without special battery drain
And choose proper baseband for you region
And CPU settings are ok as above
Defy on BL6
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
---------- Post added at 06:03 PM ---------- Previous post was at 05:48 PM ----------
corrinti said:
Ok, so you flashed JORDN_U3_97.21.51, which means 24/09 and 2ndboot builds will not work.
They could work before when you had 2.2.2 on board.
You need another full sbf, and as you flashed BL5 it means you cannot go back to froyo. You shall find working BL5 sbf or go to BL6 one like U3_4.5.1-134_DFP137 or 139
And procedure above is correct
Ps. Method from post given by you was found out a long time ago, when some ppl flashed first gingerbread and then needed to go back to froyo. It is not a proper one for all defy users with still valid warranty in most of regions
Click to expand...
Click to collapse
Ok guys I give up. I read and tried pretty much all the options net offered. Here is the problem:
I have green lens MB525. I bought it second hand in INDIA, it was running ICS. I switched to CM7 and it was working flawlessly for good 6 months. I did a reset and then it got stuck at recovery and showered error in some directories. So i triedro redo the CM7 procedure and loaded zip on root of SDcard. It didn;t changed anything. I did flashing and wiping the dalvik cache and memory, tried again, and again it was the same story.
Then i tried trying different SBF and it always used to get stuck at logo, i didn't bothered reading more about issue and stupid me flashed JORDN_U3_97.21.51. After that it started showing error in bootloader. It shows bootloader 09.10, Err: A5,69,35,00,27. I tried to use previous SBF and it then completely bricked it, only white light and black screen. Only when i again flashed it with JORDN_U3_97.21.51 it showed white motorola logo and bootloader version and error. I read this thread and tried the two firmwares using BL5 and BL6 in that order and its logo had changed to RED Motorola logo, but again the same bootloader menu with its version and error.
I had battery issues too, since i have been thinking and trying on it for past 10 days. Since i have battery charger, i used to charge the battery separately and plug it back in before flashing using RDSlite 5.6.
As of now i am stuck with a paperweight which i can only flash. I tried pressing down volume button to get into recovery but no matter what button i press it always ends up in bootloader. All help will be appreciated.
Vycas
@Vycas
The problems might be several, unfortunately even hd problem, but try this:
- try different USB cable, different computer, different USB socket - the problem can arise when signal transmission is poor. Sometimes reinstalling of motorola drivers also helps
- if above does not help try Linux computer instead of Windows one
Regarding sbf - well, as you received error after each sbf flashing there could be a hope that you still may have BL4 (but also you may have BL6) - start your above mentioned trials with BL4 sbf, which will give you camera also with CM7
Could someone be so kind and explain to me what have happened? At the moment I'm confused and I would like to understand it, to not to step into such a problem again.
I use multibooted CM9 and stock 2.2.2 (3.4.2_179-002) Froyo (the one in NAND). A few days ago I have used CM9's ROM Updater 2.08 to update my CM9 from 2012-08-16 to the latest version. The operation went fine and I was able to run my CM9 as usual, as 2nd-system. I have checked CM9's version to confirm that it has been updated.
A day or two later I've started Froyo, as I was in a need for working Wi-Fi tether. Surprisingly my Defy's screen remain black. Only keys were backlit.
At the point I've performed CWM NAND backup and have tried to restore every single partition (with exception of the data) from my previous CWM NAND backups. It did not help.
I've flashed stock 2.2.2 using RSDLite. It didn't change anything. So I've cleared data with stock recovery. It helped - Froyo started.
I've rooted it (SuperOneClick-2.3.3), installed Defy's 2nd-init v2.3 and multiboot. I don't remember which version of multiboot I've installed first, but I have tried a few. I guess in the order like this: 0.6.1, 0.8, 0.5.5. I haven't had started with multiboot 0.8 as it is bundled with an older (2.0beta) bootmenu, and I have had 2.1beta. As I don't know if these two differ significantly in functionality I have tried to preserve the newer one.
Somewhere at this point I lost an ability to multiboot my CM9 (the same black screen). So I've decided to give CM10 a try. I have downloaded 2nd-boot CM10 2013-01-10, installed it and wiped data. CM10 started fine, I have installed MultiBootManager 1.40a, 1.30, then Vibhinnia. Older MBM showed my CM9 is healthy, newer ones showed them to be corrupted. I have installed multiboot 0.61 and then 0.5.5 and in any case wasn't able to multiboot (2nd-system, 2nd-boot) my CM9, so give 0.8 a try. It turned out to be very bad idea at that point - my Defy stuck at red Moto logo, so I must have used RSDLite to bring it back to work. I guess I wiped data too.
After rooting, installing 2ndinit v2.3, MBM 1.30 and multiboot 0.8, I once again became able to boot an old copy of my CM9 (2012-08-16 version). I have replaced it's data.img with the one from the copy that, didn't want to work and CM9 started fine, bringing it back to the last good state.
Ok, I thought that the same trick should work for my Froyo, so I have replaced it's data using custom recovery (wiped, then restored it's data partition to the state when it all started).
Unluckily it render my NAND system inoperable once again. Just black screen. I have used custom and stock recoveries to wipe data, and tried with various older data backups. None of them have helped.
I do not understand why, as all of them were fine.
I would like to understand what have had happen. My goal is to have CM10 as NAND and my stock Froyo and CM9 as multibooted systems. The step I have to do right now is to restore my stock Froyo's data and make it's nandroid backup, but to do it I must make it work properly and for reason unknown to me I fail.
Hi. I have installed CM10.1 build 2013-04-13 (Last with CWM I think) and I want to downgrade to stock ROM to sell the phone, but if possible, I would like to do it without flashing SBF, so please tell me if this instructions are correct:
1) Restore Stock Nandroid
2) Download another superuser app
3) Uninstall /system built in superuser app
4) Uninstall the "another" superuser app (first un-freeze some Motoblur and de-AdAway) (no more root signs on the phone)
5) Enter Bootmenu, go to tools and uninstall bootmenu (I'm kinda scared on that one, I haven't seen anybody try on the forums, may leave it)
6) Factory Reset
I know it will probably leave things like SU binaries, cache files and things like that (I don't care) the rest will be fine? Is uninstall bootmenu safe? Which is the best way to get rid of SU apps, if it's not mine?
Thank you.
Clean install
I have a slightly different requirement.
I had Froyo two years ago, after which I upgraded to the nightlies from Quarx. I am about 1 or 2 nightlies older than the latest.
However my phone is extremely slow at most times and I would like to start from scratch.
I can backup my data and install all my apps from the playstore.
So, my question is what is the best way to go back to do a clean install of the latest 10.1 (4.1.x perhaps, since 4.2 is still experimental)?
I am using green lens defy (2 years old) and in need of a new battery as well. Current battery lasts 2 days with just a few phone calls and nothing else.
BUUUUMP
BUMP! Please someone answer
It's fine, though I would rather leave the boot menu alone and also would convert data to ext3 before restoring nandroid
To the other guy I would recommend flashing an sbf or wiping system+data+ cache from twrp recovery(if applicable) and then flash cm10
Sent from my MB526 using Tapatalk 2
Hey folks. I recently revived my 2012 Nexus 7 wifi. I thought it was toast, but I guess it just needed a nap. It was having Gapps problems last time I tried to flash, and this time around, I'm having the same issues. I've attempted to flash a few versions as well as flashing a few different roms. The roms flash fine, and they run very smooth, but Gapps constantly either fails to flash due to space concerns or even though it claims success, it doesn't load the services and I end up with a ton of errors and can't really work with the tablet. The computer itself obviously runs great, but I'm missing something, or need to take it back a step or something.
I was hoping someone could explain to me how to purge everything and install the most appropriate Rom & Gapps pairing. I'm using CWM, btw.
JavaMac said:
Hey folks. I recently revived my 2012 Nexus 7 wifi. I thought it was toast, but I guess it just needed a nap. It was having Gapps problems last time I tried to flash, and this time around, I'm having the same issues. I've attempted to flash a few versions as well as flashing a few different roms. The roms flash fine, and they run very smooth, but Gapps constantly either fails to flash due to space concerns or even though it claims success, it doesn't load the services and I end up with a ton of errors and can't really work with the tablet. The computer itself obviously runs great, but I'm missing something, or need to take it back a step or something.
I was hoping someone could explain to me how to purge everything and install the most appropriate Rom & Gapps pairing. I'm using CWM, btw.
Click to expand...
Click to collapse
First of all CWM is ancient...
I do this when I feel like starting over.
(First flash TWRP, via fastboot if possible)
Format the partition /system, /data, /cache and Internal Storage (yes even that)
Then connect it to the computer, get on XDA and download CM13 or a ROM you like (I like CM13) and flash opengapps (pico, just google it)
I would suggest following the suggestions that the developer of the CM13 port to the Nexus 7 gave to fix the eMMC speed.
Installing Trimmer and setting it to daily is enough.
Good luck!
Hello,
First of all, let me state that I've read much of the FAQ and it is greatly written. However, some of the links are old and not working and I did not understand what I need to do at my stage. Therefore I would really appreciate it if you would kindly direct me to the proper steps and maybe explain some things if I'm stuck along the way. I'm not afraid of learning.
So, I have the following phone which I received from a family member who tried to install something on it but probably did not know what he was doing.
Samsung Galaxy S
MODEL: GT-I9000
SSN:I9000GSMH
- The phone CAN enter the Download state (volume down + home + start) and it shows a yellow Android Icon with a shovel and the word "download" (I think).
- The phone CAN enter the recovery mode (where you can install from zip).
At start, the phone is stuck at loading screen of Samsung and Cyanogen mod.
Unfortunately
-I DO NOT KNOW if the phone is rooted.
-I DO NOT KNOW what is the android/kernal/firmware versions.
So what do I need to know and do in order to:
1. Get the phone back to working order.
2. Root it if so needed.
3. Install the appropriate cyanogen ROM or any other recommended ROM.
a. I want to use the phone for the app XCSOAR. Which is a great flight computer for soaring pilots. Therefore, I don't care much about effects. I do want the phone to be light on battery as possible
(Sometimes for this app to work up to 3-4 hours) and the screen to be bright (so I can see it under the sun).
As mentioned above, I'm willing to learn and would really appreciate your help.
Ramiv
Boot into recovery, do a wipe data/factory reset, wipe cache, Download this ROM , place it on SD card or internal storage and flash it in recovery.. (that's latest and best working KitKat ROM with latest security patches), also download Open Gapps ( ARM, 4.4, nano) and flash it right after flashing the ROM. Wipe cache again, and then reboot system, wait for it to boot, that's it.
.
After further reading I managed to recover the phone to the original local ROM (created by the distributer). I was much helped by a post in this forum regarding a "dbdata" error (cannot mount E).
Now I'll try to flash your new ROM onto my phone.
Thank you very much for your reply. I'll update.
Ramiv
MobileTechArena said:
Boot into recovery, do a wipe data/factory reset, wipe cache, Download this ROM , place it on SD card or internal storage and flash it in recovery.. (that's latest and best working KitKat ROM with latest security patches), also download Open Gapps ( ARM, 4.4, nano) and flash it right after flashing the ROM. Wipe cache again, and then reboot system, wait for it to boot, that's it
.
Click to expand...
Click to collapse
I did just what you recommended and it works fine, so thanks!!
However, when it runs XCSOAR (glider pilot free flight computer) the phone gets very hot unlike in the original distributor's ROM.
Do you have suggestion for a different ROM or settings? Or should I revert back to stock samsung GB ROM?
Thanks again,
Rami
ramiv said:
I did just what you recommended and it works fine, so thanks!!
However, when it runs XCSOAR (glider pilot free flight computer) the phone gets very hot unlike in the original distributor's ROM.
Do you have suggestion for a different ROM or settings? Or should I revert back to stock samsung GB ROM?
Thanks again,
Rami
Click to expand...
Click to collapse
You can try reverting back to stock GB. This is an old phone so its not very good for heavier apps. Google or HERE maps won't even work for me on any ROM i tried, it's too slow.
MobileTechArena said:
You can try reverting back to stock GB. This is an old phone so its not very good for heavier apps. Google or HERE maps won't even work for me on any ROM i tried, it's too slow.
Click to expand...
Click to collapse
Actually it works. It is a nice and probebly not heavy app since it has a version for older PDA computers.
Anyway, I will try and install a stock ROM from this thread.
Thanks again,
Rami