Hello, ive just had a Custom MoonRom installed on my Galaxy s Plus (i9001) and i recovered to the stockrom, but the keyboard sound from the old CUSTOM Rom is there after i flashed it. It seems very wierd, i have formatted, reflashed, done a full reset, but nothing seems to work...
So i just want to now if there is a way to removed the old keyboard sound, or just make sure that all things from the old rom is gone.
What i did:
i download and flashed the ROM via ClockworkMod over the i9001XXKQB sofware. now i have reflashed the old XXKQB back (warranty reasons), and i have lost 3G connection and i am left with the all the sounds from the MoonRom v 4.0
I have:
- Reflashed a billion times...
- done a full reset many times
- formated data and system via ClockWorkMod
But still these sounds from MoonRom v 4.0 is still there. WHY?
I have formatted and everything. still the sounds and my 3g connection is lost thanks to this and these sounds. I am very confused.
So how do i remove these sounds from the old ROM, or make sure to completely delete the old ROM.
-Thanks guys
Please stop posting the same question all over the forums. If anyone can answer then they will. If you keep doing this then you may miss someone answering you because either you'll have so many different threads to look in, or someone (me) will report your spamming to the mods and they'll delete most of it.
Turn off keyboard sounds until you resolve the problem - settings > language and input > select settings for whatever keyboard you are using.
Ok sorry, i am just so confused about the problem...
Related
Hi All,
Just a quick question.
I noticed today that my ROM and Manila version under Settings have reverted back to 1.66 despite the fact that ROM version under on the o2 boot screen is still 1.72.
How can this happen? Is it something to do with restoring a backup?
Any ideas?
Thanks in advance.
EDIT: Sorry Mods, I thought I was back in the HD2 General thread. Please move it.
what did you use to restore a backup it could have saved some registry bits and changed them in the phone,
Im sure you restored a full backup after changing the ROM Dont do this !!! Seriously you get many problems with that. Just restore your contacts, messages etc. and install everything clean again...
possibly, my bad....
elburna said:
Im sure you restored a full backup after changing the ROM Dont do this !!! Seriously you get many problems with that. Just restore your contacts, messages etc. and install everything clean again...
Click to expand...
Click to collapse
I changed my ROM ages ago and checked the version under Settings straight afterwards and it was fine Im sure ( I think LOL). I need do a restore today after the HTC Messaging Client 2015 update didnt work and just happened to notice the inconsistency.
Anyway I reckon the ROM version displayed in settings is simply reading from a registry setting (I found the wrong manila version number in the registry also) , as the boot screen displays the correct version.
PS. I use SPBbackup in ROM upgrade mode when moving to a new ROM and and this is the first time I have experienced this. Bearing in mind that I have gone from 1.43 O2 to 1.66 stock to 1.72 O2 and this is the first time I noticing this, 2 months after last upgrade.
Strange...I havent noticed any issues, so I will probably just fix at the point of the next upgrade (assuming there will be one).
Thanks for input so far.
I created this thread to help those who have made a rookie mistake like me. I have the latest Amon Recovery 2.3 and was not aware that the system wipe setting would do just what it says. I used this wipe a few times before the problems started. I flash ROMS as fast as they come out. So here is what happened, I was using MIUI latest ROM at the time 1.2.19 ... and I am on cricKet so I was having problems with a few things on there and I thought the ROM was to blame, so I kept trying to get it to work, (which I finally did)
but....
what I did was a system wipe which I don't recommend unless you plan to put your phone back to stock. I had no idea what I did and I lost my 3G, my phone was now locked and it reverted back to stock for most of my settings.
After trying to figure out what I did wrong, I got to the point where I almost re-did my whole phone back to stock and started from scratch, which is not very fun especially when it has been over a year since I rooted and unlocked my phone. Who took my stickies!! .. lol
SO HERE'S THE FIX....
I posted this link to make things easier, as you can see I didn't write this part but I wanted to make things easier for anyone who has made the same mistake.
http://forum.xda-developers.com/showthread.php?t=704161
A BIG THANKS GOES OUT TO killac93 for re-posting this as I was having a hard time finding my stickies.. lol
This will fix your EVO or other cricKet or Metro phones who have lost their settings or for anyone trying to get their settings right so your phone will work.
UPDATE:
It has come to my attention .. it was the MIUI ROM 1.2.19 .. it wasn't my fault after all ... the ROM wiped all my data .. almost .. it put my phone back to the stock lock code and reverted my custom settings ... BEWARE!!! Don't use 1.2.19 it has bugs
Actually MIUI just doesn't like kernals with HAVS .. so any version will do this.
***3/21/2011 UPDATE ***
The reason it reboots is b/c the ROM doesn't like HAVS .. therefore you need to change wifi settings to never sleep .. that should fix the problem
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
Hi all!! I'm new in this forum.. I found it because I had lots of problems with 2.3.6 gingerbread.. so I needed to downgrade to 2.3.5.
So I flashed a full 2.3.4 then upgraded to 2.3.5 kpn, then cw root..
Then I found 3.7 frankestain mod.. everything went good...
Now I see you uploaded 3.8.. and wifi new drivers...
how to upgrade to new mod?
just copy to sdcard and install from recoverymode? or I've to go back to some old firmware?
and I guess I need a wipe before, right?
thanks
I can answer myself
I wiped to factory default and installed 3.8 from sd.
Mod is nice and fluid.
I'm testing a bit. Since this night it reeboted by itself once. I wonder if it could be caused from wifi?!
And seems I've another little bug. I've the app crash when I try to personalize tones from address book, and I cannot change from settings/tones too.
the only tones that work are the only files included in system-media.
Any hint?
However, good job!!
thanks
Hey there XDA,
I have a weird problem when using a Samsung Captivate (ATT i897)
I was running CM9 and i wanted to flash Paranoid Android JB rom, so i followed the instructions to the letter(factory reset, and format cache, etc) and a weird problem occurred, everything works perfectly except:
1) i have no lock screen (even though it is check on (slide))
2) no notifications arrive, (i hear the ringtone and all, but it doesnt tell me anything)
3) i hold the home button and no recent menu comes)
i flashed back to cm9 and the problem came with me.
So i OdIn back to stock and followed this link (http://forum.xda-developers.com/show....php?t=1350266 ) to get root and CWR and went to CM9, it works.
Fast forward one month and i decided to flash Lanight V6.5DD Jelly bean Rom.
The Same exact problem happened, i went back to CM9 and it followed me.
So i want to format everything on my phone using CWR (including /BOOT) and then going in to download mode and using the same method as above as a fresh start ( i have GB boot-loader from Kf1, and two ATT flashes come up whenever i boot my phone up)
maybe if i flash the ginger bread boot-loader again and cleanly (clean format of /boot) then install it will fix it.
.
(QUICK Q: if i format the /boot in CWR can i go into download mode????????)
Hopefully that will fix the problem
i would like to see what is your opinion and expert help.
Sincerely,
Thatguy2007