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
Hi guys,
I recently bought a second hand x10 mini pro from a friend and aside from a few cosmetic issues its running fine. However im now considering rooting the phone and changing the rom to one of the 2.2 ones available.
My dilema as it were is getting it right.... So my plan is as follows:
1.backup contacts etc from phone.
2. Root using one of the methods available from the forums.
3. Again from the forums upgrade/replace the rom on the phone
4. Cry/celebrate as the phone now is bricked/working amazingly well on the new rom.
I guess basically since ive not done something like this since the old xda2s im asking, what should I be wary of and is there anything I should be carefull of during the whole process
Thanks
Jim
Sent from my U20i using XDA App
One of the main concerns for me is making sure you have the correct baseband for the new ROM. You usually have to flash this using 'flashtool' or similar, the baseband ROMs are fairly easy to get hold of if you google the version numbers. 'Flashtool' can usually root the phone as well as install xrecovery and all the fiddly bits, try as I might I couldn't install xrecovery or get root acess no matter what tool I used on the x10 mini pro. 'Flashtool' on the PC did it all with a couple of mouse clicks.
If your phone doesn't work after flashing (I.e. it gets bricked) and you don't feel confident then SEUS will usually resurrect it - just select the option to reinstall despite having latest software. Its rare that the phone will be completely bricked beyond redemption, although it can happen I might add.
When you've installed a new ROM, I recommend cyanocomb 1.3 (just read all the forum posts first as some people have issues - and nobody likes the same questions being asked every third post!), allow your phone 20 mins to build its cache files before leaping into action and installing things as this can cause problems.
Cyanocomb installs CWM in place of xrecovery. It is a much better recovery program in my opinion. However, make sure you use the right ROMs with the right recovery program.
Its a complicated business. Just read the forums and write down the various steps so you've got something to work from and get all the various tools and roms together you might need before you begin. You will be surprised at the lack of insite shown by some people who dive in and bodge their phones, usually asking elementary questions which have already been answered if they could be bothered to read the forum before starting.
I'm not an expert, but I did read the forums and managed to try every ROM in the 'devs' section without the need to badger the developers about 'boot loops', which are clearly user errors not ROM faults. Remember, the developers are doing smashing work and all they ask is some common sense and courtesy shown by other forum members, not to be plagued by incompetance and ignorance.
By posting here before flashing you've shown some wisdom, so I wish you well and hope others can share their experience with you.
(Sent from u20i using D4rKnYsSys/Slade87 Cyanocomb + tapatalk)
thanks for the advice, still reading the forums as you suggested at the moment. once ive got a clear idea in my head of what im doing i will of course let you know how i got on (and hopefully have a working phone to boot!!!)
thanks
Jim
brick wall time i guess. So i have managed to root the phone using as suggested 'flashtool'. phone rooted no problem, xrecovery apparently is installed. however my brick wall so to speak is that despite numerous searches of the x10 forum this evening i cannot for the life of me see how flash the rom on to the phone. im stuck and do not know what to do.
logansfolly said:
brick wall time i guess. So i have managed to root the phone using as suggested 'flashtool'. phone rooted no problem, xrecovery apparently is installed. however my brick wall so to speak is that despite numerous searches of the x10 forum this evening i cannot for the life of me see how flash the rom on to the phone. im stuck and do not know what to do.
Click to expand...
Click to collapse
After installing xrecovery you will probably need to install CWM beacause all new ROMs are created to be flashed with CWM and not Xrecovery. If you are on stock Rom this can help you The easiest way to install CWM on Stock Rom for Mini Pro
After you done this, download any custom ROM you want, place it in your SD card, boot into CWM recovery, choose first wipe user data, then choose advanced and wipe Dalvik cash and baterry stats.
After that choose INSTALL CUSTOM ZIP and find that zip on your SD card and flash it. That should be it.
Oh one more thing.... Make backup before you do any of this (just in case).
Many thanks, shall attempt this tonight and post my results accordingly
Sent from my U20i using XDA App
its been 22 minutes since i installed the rom and im looking at a boot screen still, is this normal? dont want to go to my backup without giving it a fair chance!!!
used this rom btw http://forum.xda-developers.com/showthread.php?t=1051678
appears to have caught itself in a boot loop so am restoring my backup of the original rom that was there so at least the phone is working. if at first you dont succeed try try again.
at least now i have an idea of what it is im doing, many thanks for all the advice.
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?
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
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
muffintastic said:
Hey y'all.
So many threads ago I posted up on how to root a SGS2 I900P, which in the end I did no problems. The ONLY problem I encounted where I'd flash a different ROM and wanted to restore back to my factory loaded Orange UK rom, which when I restored it with no problems it just went through the 'boot loop' phase. I read up that this is caused due to a faulty emmc 'bricking bug' and luckily it was only "soft bricked".
Cut the long story short I managed to re-flash the Orange (UK) carrier firmware (after many USB cable changes and port swaps and fails) via Odin and retain my previously installed apps and so on and had to re-root. Is there a method or some sort of fix for the emmc bug issue for future wipes/restores ?
Something new I learnt in all that process too,
Click to expand...
Click to collapse
To avoid brickbug is by flashing JB 4.1.2. (good alternative!)
But if you really like ICS then i suggest you move back to 4.0.3. There is no avoiding brickbug on 4.0.4.
If you have rooted it, you can check with 'Brickbug check' app on google play, to see if you have sane (or insane) chip (brickbug or not), cause most custom kernels and roms have found a solution to this bug, and use it on their roms/kernels. Which means on those you can safely wipe and restore etc.. (but check brickbug app first on google play)
Yep. Don't wipe a rooted phone running 4.0.4. And if you're really paranoid, don't even wipe a non-rooted phone running 4.0.4 (Entropy mentioned at least one case he knew of where someone borked their phone doing a wipe on a phone running 4.0.4 via stock Android recovery, tho it seems to be very rare).
The TL;DR is don't run rooted stock 4.0.4 if you mess with your phone in any way.
I know that's not a fix, but that's because there isn't one. Some chips aren't susceptible to the bug; there's an app floating around here somewhere/Google Play where you can check which chip you have (seems to be more that are susceptible).
Your 1st paragraph is a load of crap.Bootloop has nothing to do with "brickbug".More like by you not running kernel cleaning script,or not factory resetting before/after flashing a new rom.
As mentioned by others,just dont have 4.0.4 running on your phone.So you are still left with over 100 custom/stock roms to choose from........lol
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Hopper8 said:
Was the backup of JB? Or ICS? OP doesn't say. If it was JB, I'd be willing to bet that the bootloop was due to an attempt to restore the stock rom, but without restoring preload.
Sent from a galaxy far, far away
Click to expand...
Click to collapse
Im not sure Hopper.I am leaning towards the restore would be "cancelled" due to not being complete,rather than it succeeding leading to bootloop.
But hes not said.
And he cant get "factory" rom with a restore as it didnt come with cwm lol.
Sorry to clear things up.. I updated it to 4.1.2 via Kies many months ago. I used PhilZ method to root, no problem. Few months down the line since then I put LiquidSmooth 2.4 (few days ago) then restored a backup from PhilZ recovery and put 4.1.2 and everything back on no problem. Then restarted the phone and it when into a boot loop of the Orange and Samsung logo.
I'm not stupid as I've rooted my own SGS3 and Samsung Galaxy ACEs etc, Just forgotten to put that info in lol and yes I always use the Factory Reset to install a new rom.
And yes when I managed to get it restored from this so called boot loop (by putting 4.1.2 Orange UK firmeware back on via Odin) the EMMC brick bug is present as i've checked via an app via Google Play. My overall goal is to eliminate this problem or temp fix so I can put different roms on and if I don't like them recovery back to the latest restore without issues.
Are we on the same line now ?
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
help me out here please
MistahBungle said:
And as we've said, you can't eliminate the problem. You can avoid the problem by not running 4.0.4 stock roms. It's really quite simple, but like a lot of people here you're trying to make it complex when there's no need to.
Click to expand...
Click to collapse
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
andreshbozo said:
ok its a long story so i better get started... my friend had his phone rooted and installed a jelly bean version of Paranoid android and he wanted to put kitkat on it, he downloaded the cm11 latest nightly and told me to flash it i proceed to flash the phone but it failed and showed me "error status 7" so the phone couldnt get neither into the previous pa nor in the cm11... after some research and messing with the META INF stuff to sol the status 7 thing i found out that the problem was that he wasnt using a kitkat compatible recovery... i installled it and finally got to flash cm11.. that didnt came out as you may thought the phone showed it had -15246384352 % of battery made a freking glitch when the sreen rotated and it wouldnt recognize either of the sd cards (internal memory or external sd card) so i couldnt flash it again, wipe data/cache wouldnt solve the problem either... i turn into our ol friend odin and flashed stock JB wich worked perfectly except that i had the same issue with the memories... used philz to root the phone again, the try to format /system /data /emmc to check if that was the problem annnnd ta da the phone wont boot :silly: odin keeps failing to flash stock again and i dont jknow what to do....
sorry for the long post but i guess that you might need alll the info you could get for helping me...
thanks a lot
Click to expand...
Click to collapse
Here is my situation.
I had 4.1.2 JB. Installed CM11 M8 and CWM_6.0.4.7(coming previously from Siyah) at the end of July. In the beginning of October my phone just shut down. That happened before on the same and previous rom so I wasn't worried. I turned it on and phone was in bootloop. That was strange because the last time that happened I installed Chainfire. So bootloop without any cause..that was strange. I tried making a backup before flashing the ROM. But I got an error. I can't remember but I can dig it somewhere if you want it. I tried then flashing recovery(bad idea) and Odin again reported an error. When I restarted phone I noticed that my Recovery mode was gone. Just gone and with no solution on how to restore it. I tried numerous methods OMAP drivers, heimdall, .pit file method but nothing. So I brought my sgs2 to the store where I bought it and they concluded that it was bad eMMC chip.
Now, your problem reminds me of mine because Odin wouldn't want to flash anything without an error(well, not exactly anything, I managed to flash some partition using Heimdall but it was not sufficient) but it doesn't have to be.
What version of cwm were you using?