After updating my O1 to Gingerbread two friends complained about receiving just half of the message right and the rest of it with squares/boxes, (at) or Chinese characters, this just happens after x characters, since they get short messages without problems. I think this just happened to them, I'm not sure. Others receive the whole message without any problem. I'm not sure if the problem is the Stock ROM, their cellphones or if I configured my cellphone wrong. Any ideas about what's wrong?
Ps: I'm so sorry about my English, it isn't so good.
hi Phoenix232,
there are seldom any problems like this in a newly updated firmware.
still try master reset.
If that doesn't helps i would recommend updating again.
Good luck.
I'm so sorry to ask this but what are the button combinations I need to press to do the master reset?(It's the same as hard reset I think?) I've been searching but I can't find the right buttons for the P500.
EDIT: Actually, I think I found out how to do it, it's HOME+Vol. Down+Power, but if I do this I get in Recovery Mode.
EDIT 2: Yep, it looks like I need to do this without any recovery installed. I'll try it later. Thanks.
Hello Phoenix232,
I have an O1 myself and I think that I can help you. Please answer my following questions:
1) Did you update to Stock firmware or are you using an CFW?
2) Wich version did you happen to have installed before gingerbread?
3) Which version came pre-installed in your device?
I guess that since you can boot to Recovery mode you are using a CFW, am I right? But if you remove the Recovery, did the Master Reset help?
BR
1) Stock
2)Stock Froyo ROM with Franco Kernel
3) Stock Froyo ROM
I just rooted it, installed recovery and installed franco's kernel. I removed the recovery, did the reset, but it's happening the same thing.
Im currently facing a similar issue, people telling me they simply didnt get my SMS.
Having this issue after installing a new rom.
With me they get half of the message and the other half is just squares or chinese characters.
Dear Phoenix232,
I think that that the best procedure for you is to first go back to original O1 Froyo ROM without mods or root, master reset, them perform the upgrade to official O1 GB and master reset again if you want to use a stock ROM with no mods. Please be warned that this procedure can kill your handset, and since you already rooted and changed kernels you probably voided your warranty so be extra careful with all that.
I haven't already upgraded my O1 since it is my primary work handset, can't risk loosing all my info, but I've done a very similar procedure with a Motorola Milestone and it was all OK (2.1 stock, 2.2 shadowmod, them back to stock 2.1 and finally stock 2.2). You just can't root and change kernels then try to upgrade directly to GB stock without first going 100% back to Froyo stock. (no root, stock kernel etc...). Manufacturers tend to taylor their Android OS upgrades based in the previous version so everything must be exactly the same as it was when you first purchased it for the upgrade to work correctly in the end.
Good Luck!
That makes sense. I'll try it right now and post the result asap. Thanks.
I got back to Fryo and the SMSs are working fine. I'm upgrading to gingerbread now.
Question: Can I root it after doing everything you wrote? Or it'll bug again?
Related
hey
so i bought an optimus one this week and have already noticed the touch lag and stuff.
was always gonna root it, and have done jailbreaking on ipt/iphones but i know nothing about the android equivalent apart from what i have googled since then.
have read http://forum.xda-developers.com/showthread.php?t=901247 and a lot of other stuff and i thought i got it, but obviously i didnt.
basically, phone was on 2.2.2 so i downgraded to 10a 2.2 so i could root. ran z4root, installed custom recovery and then flashed milk_os's fixed kernel onto it.
kept showing "android.process.acore has stopped working" errors on screen, and i thought i could just upgrade back to 2.2.2 without breaking the kernel.
couldn't find a download of the latest firmware (but have since then) so i used pc suite 4 to update.
phone is back in 2.2.2 but root is gone and kernel is back how it was before.
tl;dr what i want to know is the difference between a rom and a kernel, and if it is possible to update the OS without changing the kernel, or root on 2.2 and then update to 2.2.2 without removing root so i can then install the milk_os kernel.
i have a copy of the latest update 2.2.2 from my provider which i can install with recovery if it will stop it overwriting kernel and/or removing root.
alternatively, cm7 is a 2.3.3 rom, is it worth just downgrading, rooting and flashing that? i assume that wont break my root
sorry for noobness, i just want to play angry birds without lag and im a compulsive fiddler/breaker.
PS also, if i go to 2.3 gingerbread am i correct in thinking my class2 microsd card will not work anymore on account of app2sd or whatever?
can someone please just tell me the best option for me, i have tried to google and read myself to find an answer but new to the scene and some things seem to be taken as understood and i don't get them at all.
thanks
terrycurls said:
hey
so i bought an optimus one this week and have already noticed the touch lag and stuff.
was always gonna root it, and have done jailbreaking on ipt/iphones but i know nothing about the android equivalent apart from what i have googled since then.
have read http://forum.xda-developers.com/showthread.php?t=901247 and a lot of other stuff and i thought i got it, but obviously i didnt.
basically, phone was on 2.2.2 so i downgraded to 10a 2.2 so i could root. ran z4root, installed custom recovery and then flashed milk_os's fixed kernel onto it.
kept showing "android.process.acore has stopped working" errors on screen, and i thought i could just upgrade back to 2.2.2 without breaking the kernel.
couldn't find a download of the latest firmware (but have since then) so i used pc suite 4 to update.
phone is back in 2.2.2 but root is gone and kernel is back how it was before.
tl;dr what i want to know is the difference between a rom and a kernel, and if it is possible to update the OS without changing the kernel, or root on 2.2 and then update to 2.2.2 without removing root so i can then install the milk_os kernel.
i have a copy of the latest update 2.2.2 from my provider which i can install with recovery if it will stop it overwriting kernel and/or removing root.
alternatively, cm7 is a 2.3.3 rom, is it worth just downgrading, rooting and flashing that? i assume that wont break my root
sorry for noobness, i just want to play angry birds without lag and im a compulsive fiddler/breaker.
PS also, if i go to 2.3 gingerbread am i correct in thinking my class2 microsd card will not work anymore on account of app2sd or whatever?
can someone please just tell me the best option for me, i have tried to google and read myself to find an answer but new to the scene and some things seem to be taken as understood and i don't get them at all.
thanks
Click to expand...
Click to collapse
a. kernal =/= rom
kernel is something that works beneth the operating system.. its like this
YOU -> Interface -> Operating System (ROM/Android/Linux/JVM) -> Kernel -> Hardware
and back.
I also assume LG's updater flashes both the rom and the kernel. so in simple terms, use Custom Rom to flash a new rom (void/CM7/etc) and use it. There is no trick way of the stuff ur explaining to happen.
b. Android 2.2.2 doesn't do jack ****. downgrade to 2.2 then upgrade to CM7 or whatever. class 2 sd cards SHOULD have a random unmount error. i think void might have fixed it; check plz. flashing cm7 should fix everything u explained, but don't expect much from the ROM; its in dev. FYI touchscreen fix is included in cm7
c. custom roms, including cm7 has root built in.
d. conclusion
i. use cm7 route -> flash custom recovery -> flash CM7 (tricky, be careful) -> touchscreen profit!
ii. use froyo rom route -> flash custom recovery -> flash rom of ur choice (void, megatron) -> flash touchscreen kernel -> reboot -> profit
e. press thanks if ur thankful. i would like some thanks lulz
cheers
There is a Kernel you can flash that helps fix the bug
http://forum.xda-developers.com/showthread.php?t=929941
thanks!!!
awesome, thanks heaps for that.
just one more thing, i assume the custom roms like cm7 and megatron/void all have root built in? or does the custom recovery do something to stop the root being removed when you reflash
once you root the phone, no matter what custom rom you use, it will still be "un-rooted".
Only when you use the kdz updater to put back original firmware, phone is no longer rooted.
thanks
awesome, thanks for that
OK, Heres the scenario, This is a replacement T-959 vibrant, sent from either TMO or Samsung, really not sure! My 1st phone never had any issues with modding, and always cooperated! Until I used KIES to update one day and It bricked, because of primary and SBL corruptions. [I know!!, found out 5 mins too late about using KIES] Anyway, since Ive had this replacement phone its done nothing but fight me from the start, never has acted right I think and I feel there's something wrong HW wise with it. My problem with it now, is it wont accept any other custom ROM I try to install, and only works with either 2.1 or 2.2 stock OEM ROM's. Meaning, Anything else ROM wise, It wont go past the last part of boot sequence, and just keeps looping, and does it over and over again! Ive tried all of Simple Honeys, Toxic 8's Roms, and each time it goes thru the loading successfully, and then starts it boot-up, but every single Flash Ive done, ROM wise, it hangs up and loops at the very last part of booting up. Ive come to realize now, it isn't the ROMS, but the phone " I THINK" Each time I tried a Custom ROM install, I started with stock fresh JFD install, and wiped and cleared out everything before starting another ROM install, but with each attempt that I try to go past anything other than Froyo stock, It does this boot loop problem at the final part!! It seems like who ever sent it to me, did something to the phone to prevent this. Modding it I mean. like right now I'm on Eugenes Froyo, with the 2E RECOVERY, It was working fine, until I upgraded the Eugenes kernel, which is suppose to work with this ROM, technically the phone still runs, but as soon as I did this, I now cant get into the two drives as mass storage to tranfer files, says insert disk, like as if its a CD Rom drive, WTF!! And like I said, this phone wont accept any other ROMS now, past stock Eclair or Froyo OEM and kernels as well. I don't understand what the problem is, My guess is they flashed something to prevent modding or its just a corrupted HW issue, anybody ever seen this before. I wish I had just JTAG'd my first phone with Josh over at Mobile Tech, and saved myself all this heartbreak and frustration, but its too late for that now! So anyway, I need to determine for sure if this phones screwed, HW wise or if there is SW to get this phone straighten out, to where it'll work right like my first one used to, and begin to accept custom ROM's like it should be able to do!! I'm at my last end with this phone, and I'm desperate to get a solid reason/answer for whats happening here, because Ive followed all the instructions and standard procedures to insure that all the attempted installs of the ROMS I mentioned go correctly. And its boiling down to either HW issues or a SW issue they created before they shipped it to me, or last but least hopefully a SW fix here, that can get the HW/phone to act right again, and maybe salvage this phone, otherwise I'm thinking I need to buy another brand new phone and hope for the best. I just don't want to be stuck and limited with Froyo stock, for the rest of my time using this phone, I want my freedom to choose again, like I had before, and also It ran so much better than OEM anyways!
Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data
Sent from my SGH-T959 using XDA App
Quote" Go back to stock using the sticky on the q&a then root using that same methOd and when you flash a custom room make sure you wipe dalvik and cache and delete user data"
If you had picked up on it in my post, have already done this dozens of times!! Oh and BTW, when at JFD = 2.1 Eclair, it wont allow the 2 drives access to in Cabled USB mass storage, and therefore unable to CWM flash with zips, then I must go to 2.2 Froyo next to be able to get past that problem, but again when I go from there to any custom ROM, it fails to boot at the very end, and starts its looping. Again, the 1st phone I had, never ever, behaved like this!! Same phone but, different dates of manufacturing and also this one came from either Samsung or TMO in Plano,TX where that's all, they do is send out phones for replacement, and this one wasn't in a original box, something they worked on, grabbed off the shelf, and sent to me!! Its just a shame that 99% of all the ROMS are in zipped form, instead of TAR files, at least then I could've tried flashing some of them from, Eclair to see if that made a difference, but when they are zipped, you must use CWM recovery to flash, and thus again presents another problem as far as what I'm going thru here!
Got any thing else, Idea wise, that actually hasn't been tried yet, that makes sense??
OK, Ive made some progress, It seems for whatever stupid reason, that unlocking my phone, [jailbreaking] was the culprit of this phones renegade behavior, I simply restored it back to a locked status as a TMO provider, and Wholla, the phones now acting right!! And I have been able to get it to the ROM I wanted and flash a better kernel as well with 0 defects!!! And then I jailbroke it again, and its working flawlessly.
Personally I don't understand why that had a bearing on its behavior, but nun the less it did. And has cause me a few extra wrinkles around my eyes in stress trying to figure this out by myself, especially when all the suggestions and procedures I did was for nothing, until this phone was restored to a locked condition again!!
Go figure Right???? Grrrrrrrrrrrrr!!!! Anyway I hope mentioning this will prevent someone else in losing their hair or sanity!!
hello i think we have the problem, i also have openline my vibrant to be able to use here in our country.. i have 2.1 eclair, i just want to know what 2.2 ROM did you used coz you've said that it's ok to upgrade it to 2.2, but not other ROM, where did you get it.. can you pm me the link
thanks
Mine could be a stupid question, especially since I''ve already downgraded successfully from ICS to GB, but anyway I'd like to have some feedback from anyone who's a bit more experienced than me
I tried stock ICS for Mini and I didn't quite like it (LED issue, too much heating, some app incompatibilities and so on) so I decided to downgrade to my beloved and trusted stock GB. BUT my bootloader is locked, and I had no internet access nor DoomLord's root kit with me either. This meant that, after downgrading to GB, I couldn't have rooted it, so no CWM, no Recovery, no backup restoring, oh well, I didn't feel like going around with a brand new phone for a whole afternoon (I'm an idiot, am I? ).
So here's what I did: I had CWM Recovery installed on stock ICS. I used Flashtool to flash only stock 2.3.4 kernel. Then I booted and when prompted by the brighter screen (no blue LED, damn ICS!) entered CWM Recovery (which, let me repeat that, I had previously installed on ICS) and restored a stock GB backup. I rebooted, and I'm on stock GB now. Great.
Now I'd like to know... even if everything's going just fine, and even if I can't think of a reason why I could get in trouble, I still think that maybe I just don't know something, or I forgot some important information, and this way of restoring a stock GB ROM could just be totally wrong. And here you come, experienced users: did I do something stupid?
Thanks for your attention... I just talk a lot, I know...
EDIT
Also: if I feel like going back to stock ICS, I suppose I can flash stock ICS kernel and then restore a stock ICS backup... right?
Feanor88 said:
Mine could be a stupid question, especially since I''ve already downgraded successfully from ICS to GB, but anyway I'd like to have some feedback from anyone who's a bit more experienced than me
I tried ICS for Mini and I didn't quite like it (LED issue, too much heating, some app incompatibilities and so on) so I decided to downgrade to my beloved and trusted GB. BUT I had no internet access, and I didn't have DoomLord's root kit with me either. This meant that, after downgrading to GB, I couldn't have rooted it, so no CWM, no Recovery, no backup restoring, oh well, I didn't feel like going around with a brand new phone for a whole afternoon (I'm an idiot, am I? ).
So here's what I did: I used Flashtool to flash only 2.3.4 kernel. Then I booted and when prompted by the brighter screen (no blue LED, damn ICS!) entered CWM Recovery (which I had previously installed on ICS) and restored a GB backup. I rebooted, and I'm on GB now. Great.
Now I'd like to know... even if everything's going just fine, and even if I can't think of a reason why I could get in trouble, I still think that maybe I just don't know something, or I forgot some important information, and this way of restoring a GB ROM could just be totally wrong. And here you come, experienced users: did I do something stupid?
Thanks for your attention... I just talk a lot, I know...
EDIT
Also: if I feel like going back to ICS, I suppose I can flash ICS kernel and then restore an ICS backup... right?
Click to expand...
Click to collapse
With an unlocked bootloader getting back / switching between gb an ics is easy.
Use in both ways a prerooted kernel with cwm. Install the kernel via flashtool. After that restore your nandroid and you are done.
That shouldn't take much more than about five minutes. Switching is so an easy way.
Gesendet von meinem WT19i mit Tapatalk 2
I did it with a locked bootloader. It doesn't matter, since CWM is not installed in the kernel (it's in /system, I think, but I'm not sure of it).
If you install CWM Recovery and then flash any stock kernel you can access the recovery even if it's not included in the kernel. That's what I tried, and it worked.
What I was asking is: is there any chance that this method can leave old/unwanted data on the phone? Based on what you said, it should be ok
I did the same but via wotanserver, because I have a belgian azerty mini pro and couldn't find the right firmware on xda.
Didn't have any issues, but you should remove all application data on your sd card to avoid problems.
I did like the complete ICS look, but it was too choppy, and too many bugs to live with.
jvdv360 said:
I did the same but via wotanserver, because I have a belgian azerty mini pro and couldn't find the right firmware on xda.
Didn't have any issues, but you should remove all application data on your sd card to avoid problems.
I did like the complete ICS look, but it was too choppy, and too many bugs to live with.
Click to expand...
Click to collapse
Thanks for your feedback
Hello folks,
new here, but no new to Android, although I am not expert, thus please be patient
I have a 2-yr old Aria, which I rooted as soon as the warranty expired and it also has ClockworkMod Recovery on it, version 2.5.0.1. It is still running the stock 2.1 Eclair ROM, the really old one, with no OTA option.
Few days ago I became a victim of the infamous "download unsuccessful" issue with Market (running on 2.1 my Aria does not have Google Market). It just happened out of the blue, I had not installed any new application or done anything weird as root. After having tried all imaginable fixes, referring to the many Google search hit on the subject, but with no effect, I contacted Google support. Their suggestion: do a FDR....
Now, if I have to wipe my phone and rebuild the system, I'd rather take the plunge and upgrade to Froyo.I am getting a new phone soon, which will have ICS, therefore I am not interested at this time in any alternate ROM, the stock 2.2 from AT&T will do. I downloaded it a while ago but never upgraded.
My questions is: what is the correct procedure to upgrade to stock 2.2 Froyo with no danger of bricking the phone, since I have ClockworkMod on it? Do I just run the upgrade following the instructions on HTC web site because it will wipe CWM anyway or should I use the "apply sdcard:update.zip" or "install zip from sdcard" options in CWM Recovery main menu?
Also, should I decide to just do a FDR and go back to the original 2.1 ROM as Google suggested, the right way of doing it is through the "wipe data/factory reset" option in ClockworkMod Recovery, NOT through the "Factory Data Reset" option under "Settings -> Privacy", correct?
For many of you the answers will be obvious, but as much as I have searched over the internet, I have not found a straight answer, especially to my first question (how to upgrade to stock Froyo if you have ClockworkMod installed)
Thanks in advance for any guidance you may provide.
Batman66 said:
run the upgrade following the instructions on HTC web site because it will wipe CWM anyway
Click to expand...
Click to collapse
This
And factory reset in Android or recovery - doesn't really matter. Might be faster through recovery
WinSuk,
thanks for the speedy reply!! I suppose you mean doing a Factory Data Reset AFTER I run the HTC upgrade to 2.2, right?
And one more question, if I may: I believe I will lose root once I upgrade to stock Froyo, correct? At this time I do not mind, as Froyo should add a couple of missing features in Eclair that made me root in the first place, namely moving apps to SD and clearing the apps Data.
Thanks again! :good:
Batman66 said:
WinSuk,
thanks for the speedy reply!! I suppose you mean doing a Factory Data Reset AFTER I run the HTC upgrade to 2.2, right?
And one more question, if I may: I believe I will lose root once I upgrade to stock Froyo, correct? At this time I do not mind, as Froyo should add a couple of missing features in Eclair that made me root in the first place, namely moving apps to SD and clearing the apps Data.
Thanks again! :good:
Click to expand...
Click to collapse
I meant about your second question..
It will wipe data automatically when updating. And yes, no more root
Oh, I get it now. I misinterpreted the "And" at the beginning of your second sentence. Reading on other forums about people who had upgraded their phones from Ginger Bread to Ice Scream Sandwich, I noticed that many of them had to do a FDR after upgrading to get everything working right. I thought you were referring to something similar, although in this case I see how it wouldn't make much sense, since everything that has to do with Eclair 2.1 will be completely wiped off the phone by the 2.2 install.
Is this possible? The full details are I had my phone stolen, and got a new one with android 4.0.4 on it. I have on my computer a copy of my latest backup of my old cognition gingerbread rom. Can I just use CWM to recover to my old rom, or do i need to first downgrade to a gingerbread rom, and then recover?
Thankyou very much for assistance
Edit: Also, I don't actually want to use the old rom, I just need the contacts it saved, afterwards I'll wipe everything and install a clean ICS mod. In case there's any way of doing this without having to revert
You'll probably need to restore the backup with a version of CWM close to the one the backup was made with, you can often have problems restoring if you're using a CWM version a lot (say 12 mths or more) newer than the one you made the backup with.
So I'd probably go GB/with a rooted GB kernel first, restore the backup & go from there. I mean, it could work first try with an ICS kernel that's running a recent CWM build, but there's a fair chance it won't.
Edit - And be really careful with stock 4.0.4, don't do a wipe while you're running that.
Wow. I just... wow.
Ok, so I did the stupid thing and just tried to restore my old backup without doing proper downgrading first and it ended up soft bricking my machine, couldn't get recovery mode up, but I got into download mode. So I downloaded my country's stock gingerbread rom from samsung's site and flashed it with odin just to see what happens, and somehow my old rom was working again, and I have all my contacts and data. saved everything up to google, upgraded to ICS, import.
Everything went better than expected.
Thanks for the help
Told you Important thing is you managed to fix it yourself without asking silly questions in Q&A. Not many people seem to be able to do that these days.
Well done. I'm glad you got it sorted
Edit -You're welcome