Related
Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.
I recently installed the nightly build of ICS on my samsung vibrant. Today the phone had a error that said encryption cannot be completed phone must be erased. I let it do a factory reset . Then I got stuck in a endless boot cycle showing the vibrant logo and then the cynogen guy for a few seconds then reboot. I could still access the recovery menu but it refused to flash any roms I threw at it. I downloaded and ran odin 1 click recovery and it changed my tmobile phone to a att phone. And it lost the recovery mode. It just shows att screen first then samsung vibrant second and just reboots. I can still get into download mode and flash roms using odin 3 but no matter what rom I select or if I choose repartion or not the flash will go through successfully but then the phone reboots into same problem as before. I suspect the recovery files are gone since no button combination anymore gets me into recovery. Is there anything else I can do?
Man I am having the exact same problem. I really hope someone can figure something out soon. Did yours randomly get that error? Or did you actually try to encrypt your phone?
Sounds like you used the wrong Odin 1 Click. If it installed Captivate bootloaders, that would cause a problem.
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
It just happened
It happened on its own. Was working fine all day walked in my house as as soon as it hit wifi it started going crazy. I had the data plan turned off months ago. Maybe theres something to it connecting up to the net. I have found out if you install your sim you get a reduced menu of recovery options but without sim it just constantly reboots. it only gives option of reboot, reinstall packages,delete all user data, delete cache data. If you try reinstalling the packages theres nothing there. Deleting caches made no differance. ADB does work and responds while in this lesser form of recovery is there a easy way to use adb to force a full system flash?
Thanks
That link was perfect had a link to eugenes no brick froyo rom which fixed my problem. Dloaded that used its pit and tar files and repartioned and im back to stock. Going back to team whiskeys mod. If all ICS roms has bugs like that is unusable.
bfranklin1986 said:
This is your best shot I think
http://forum.xda-developers.com/showthread.php?p=24418319
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
Do you have access to BOTH your internal and external SD cards? The Encryption Bug is totally and completely random and does not discriminate. There is currently no known reason or solution. Several of us across a few different devices have been working on this for months.
Consider yourself luck if you have access to both SDs as you are the 2nd person to get in and out today. Many, many others have not been as fortunate.
If you could please pull up this thread and put as much information in there as possible, it would be greatly appreciated. Are you unlocked, what happened right before, what bootloaders are you on, what ROM were you trying to flash, what ROM did you end up getting booted,....those types of things. As much detail as you can muster together, after you catch your breath and relax a minute.
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Update
I think I might have pulled the trigger to quick. While the link above did give me Eugenes rom which at least got me out of the boot cycle both internal and external sd shows 0 and I am unable to load anything on either card. I have tried differant microsd cards all of them show the same thing. So eugenes rom got me working kind of but cant store anything at all. That sucks loved my vibrant and its almost out of contract and planned on using on prepay.
Agreed 100 %
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Moped_Ryder said:
Guys DO NOT run ICS unless you have read up on the Encryption Unsuccessful bug and except the possible consequences! Every ICS T959 rom should have a warning IMO.
There is no known fix > just a work around. Odin / Heimdall / Jtag = useless
Click to expand...
Click to collapse
chickenmon said:
Had I of known would of stuck around on my team whiskey rom which never gave me any problems. Does this ICS bug affect amazon kindles? Ive put cynogen9 on 2 of them and am wondering if I shouldnt take it off before they turn into paper weights.
Click to expand...
Click to collapse
I got tagged on a Nook Color with it. BUT, since the Nook Color has a feature that no others I think do (you can boot a ROM straight from an SD card and not mess with the oringinal OS at all), I was able to just pull my Microsd out and reformat it and then put CM7 on it for my wife.
So far from what I have seen and been working on:
Vibrant, Captivate, My wife's Nook Color, A few Transformers, SGSII,...
Anything I can do?
Anything I can do to get my partions right again? I can flash the twm 5.2.2 but none of the roms i throw at it including ics passion stays in a boot cycle. Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
chickenmon said:
... Only rom that works is eugenes froyo that does not brick and it doesnt allow internal or external mem to be seen.
Click to expand...
Click to collapse
You may want to bring up this issue directly in Merio90's thread. I believe Alex9090 went thru possibly similar issues and may be able to help you in that thread (unless she happens to pop in here).
I'm assuming you were trying to mount sdcard and emmc within recovery first (storage and mounts)? If you do have access to recovery again and can mount the external sdcard, maybe try repartitioning the card within recovery (using the parameters in Merio90's instructions)? Then transfer your rom zip and re-flash.
People have actually flashed Eugene's Froyo post-EU ... but without an ext sdcard. Quite an oddity. It's the only one (AFAIK) that'll fully boot up (even after losing int sdcard access due to EU) yet without an external sdcard in place.
Your assumptions are correct. I cannot mount emmc. I cannot flash any rom via 2.5 or 5.2 recovery only through odin and only eugenes rom still allows phone to boot but no mounting of internal or external sds. Ive spent about 3 days on this. There must be some hardcore adb commands to force a true factory reset partioning and all. Very annoying. Thanks for the help if I find any ways to fix it I will repost it here.
Might be bricked?
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Not related at all to my original problem.
tenantrep said:
Ok, i will admit up front that I probably did something stupid and now am sending out a cry for help. Until yesterday I had ICS 4.0.3 successfully installed. I believe it was Euphoria flavor. But, I constantly had shortage of memory problems with the new force close language on apps running in bg - was laggy. Here is where it all went wrong - Decided to dl and install CM9 nightly to fix my laggy install. Recovery went fine, but rom failed, rebooted and sent error to cm. Tried new tactic - dl and installed Slim ICS - wrong, got stuck in boot loop - but could still get into download mode. Ran Odin to restore to stock. Ran fine but Failed - no explanation, just failed. Since it would not respond, finally turned it off - OFF has now become permanent! Power button does nothing. Charging does not light up screen. No download or recovery mode! Really fearful that this IS bad. Help, help, help!!
Open to suggestion. . .
JIM in FLA
Click to expand...
Click to collapse
First of all, not to sound like a ****; but it's rude to hijack someone elses thread. You should've created your own thread for this.
Second; you might have fried your bootloader which in turn, yeah, that's bad and you might have bricked your phone.
Did you try to boot into recovery via the battery pull method. If not, try that and see how it works. I would link you to the instructions but I'm too lazy and tired right now to search for it and again, this is someone else's thread. Just do a search for it and you should find it.
If you need more help or guidance, create your own thread and start there.
Noticed your running Ice Cream Zenwich rc1.3. How do you like it. Ive installed slim 3 times today and twice I have gotten the encryption error within a hour. Needless to say not impressed major pain in the ass to have to do a million and half tricks with awm, adb, popping sd cards in and out etc.
Update
Also the current build of ics slim does not allow the imei information to be retrieved from sim for tmobile requiring a reflash of the modem. You have to download and install a new modem. I used csm5. The guide on the link in this post dow work but its a real pain and requires lots of trial and error. Wondering if google intentionally bricking these things knowing we all got gadget lust for the sIII now.
chickenmon said:
Noticed your running Ice Cream Zenwich rc1.3. How do you like it ...
Click to expand...
Click to collapse
ICZen_rc1.8.3 (AOKP #39, ICS 4.0.4) + subZero #144 (New Test Kernel just released in mr_pyscho's RootzWiki kernel thread) is Linaro infused ... and I've got to say the combo is THE fastest rom experience I've ever had on my Vibe. Whatever MP did in his new test kernel just blows the doors off the previous performance limits.
Btw .. you keep encountering EU again. Really odd unless possibly your external card wasn't partitioned correctly. Not a knock directly on you, but it is a common occurrence lately. FYI, I repartitioned mine directly from recovery.
Also ... Br1cK'd (ICZen) and mr_psycho (subZero) are aware of the EU situation and try to include safeguards in their builds. However, until we know the exact root cause of EU, we're all just shooting in the dark. Imo, it's at least comforting to use a rom & kernel where the dev's are at least mindful of EU.
Hi all
ok so i'm a bit nervous writing this expecting all manner of attack in that i may be posting something that's been posted before lol, i've been working on this phone from start to finish about 9 hours, over two days..... i've googled just about every combination of words to do with the title and everything in between but nothing seems to come close to what i actually need to do as nothing works
i have an LG Optimus 2x / p990, it had ICS on it but was far too slow to handle this, it needs something a bit less hardware intensive to run smoothly, so i went ahead an found cyanogenmod stable ...... 7.2 i installed sdk after an hour of finding out how it works i finally got adb and fastboot working, i then needed this, that, this, that, etc etc etc.....
to cut a 9 hour story short, i've managed to get myself to the point where i wiped the phone of everything but CWM partioned for ics via the AIO software but CWM will not let me install any ROM onto the phone. to be more precise it says i have installed CM 7.2 successfully! (i've tried this via the CWM via external SD card and sideload) i reboot the phone it's as if i've never done a thing, no trace or suggestion i've even attempted it on the internal card... nothing
i'm at the point now where i'm quite happy to just have my phone back now and install ICS 404 but can't use the LG kdz install software as the pc doesn't see the phone as an LG p990 because it's recovery and i can only get it to come up as internal and external memory cards
i'm not really a noob when it comes to tech stuff but this little phone has me stumped.... please, i'm begging you, help me any operating system that can get my phone working will do, preferably the CM 7.2 if not back to ICS 404?
and i know, i know i should have backed up but i had no idea it could be so complicated just to put an OS on a tiny computer
ETA i've tried that exitrecovery.zip thing and it did nothing :/
It's quite simple
Try to reset and unroot/re-lock the phone then unlock and root, then what you need to do is get ROM Manager and get the Clockwork Recovery and the version that supports your device, although you might need to hook up your phone to your computer for the process to work.
Also put back in ICS 4.0.4 when unrooted and re-locked again like stock and make sure it's the stock file for your phone.
And after you got ROM Manger and the Clockwork Recovery
Then just in Clockwork wipe out all data on the device and don't do a factory reset in Android just with clockwork and delete everything that was made on that phone then install CyanogenMod.
After that it will seem to take a long time or just a while to boot up and then it boots faster then the original ROM.
If you have Clockwork Recovery just wipe out all the data while it's still in there and you should be set.
When it was my first time putting in CyanogenMod it was 10.1 RC1 on my Nexus 7 and it didn't work and forever bootlooped, and that was because i forgot to wipe the device. Then after going into Recovery with Clockwork I deleted all the data of my tablet and it worked but took 5 mins. to boot up which is nomal.
And if Clockwork doesn't work, do the same with TWRP (Team Win Recovery Project) and download that which can be found here teamw.in/project/twrp
If you don't want to get ROM Manager or that one isn't working then try this website to get Clockwork because it has the whole list of devices and I recommend downloading from the website instead of their app. clockworkmod.com/rommanager
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
twelfty said:
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
Click to expand...
Click to collapse
TWRP has a completely touch driven interface that is 100% themeable, while CWM has a touch version and non-touch version. Also TWRP has a built in file manger and terminal emulator where as CWM does not. A lot of people like TWRP because it provides a lot of good features with a simple and straightforward yet powerful user interface. I would recommend taking a look at this guide if you want more information on the differences between the two http://www.droidiser.com/2013/04/twrp-vs-clockworkmod-recovery.html?m=1.
Sent from my SCH-I535 using xda premium
ok i managed to do it i can't remember exactly how but some good links and info for anyone who stumbles across this in need of help
i went for cyanogenmod 10.1 to make this work i used this AIO tool - http://forum.xda-developers.com/showthread.php?t=2020737
repartioned with OLD partion layout and BL
installed TWRP (included in the aio)
if you need to reinstall the google play store make sure you have right version if you flash it and get "unfortunately setup wizard has stopped" repeatedly you have the wrong version see this link for which one you need http://wiki.cyanogenmod.org/w/Gapps
obviously make sure you have adb and fastboot setup and drivers too.... it's a long process installing the entire sdk, personally for flashing this once and most definately not inclined to do it again i'd go with just the adb and fastboot rather than the whole sdk
also i found a keyboard error with 10.1 where i'd type 1,2 or 3 characters and the keyboard would minmise not sure if there's a proper fix (i found one thing where you disable the autocorrect but didn't want to do that) so i decided to download and install hackers keyboad which is based on the gingerbread keyboad and is much better and comes with full features and integrates nicely
coupled with the info above from YoyoscratchMC and you should be in the field
good luck to all i was ready to jump out my window with my phone first so i could land as hard as possible on it last night but i got there in the end lol
Hi guys, firstly I'd just like to say I have followed all the protocol that is required on here and been reading and researching/ applying fixes for the past few days now. I have tried to help myself as far as i possibly can but i am still having no luck and i don't think too many people have had the exact similar issue after reading all the other threads that are similar to my issue.
with some of the fixes it is my first time using them as i have never needed to in the past, so bare with me if my level of understanding isn't as great in some departments.
Now onto the issue:
I own a galaxy s3 i9300 and it has been rooted on stock rom since day 1 about a year ago. A few days ago my phone battery died, and when connnected to the charger it had this grey icon with a circle. It wouldn't boot up either so after searching on the net i thought i would listen to the advice of clearing the cache etc etc but this didn't work and neither did the wipe data/dalvik in CWM.
So i reflashed a stock jellybean rom and it worked fine.
It was then at this stage i thought i might as well upgade to a custom rom as every galaxy i had owned before i had done it on, and my current Note tablet is also running custom rom.
I first loaded a stock 4.3 rom and then flashed the slimbean 4.3 with gapps ...and it worked perfectly. I found a couple of issues with the browser which i use a lot so i downgraded to a 4.2.2 version of slimbean with gapps and this made the browser really fast again and all was perfect.
I had been using this for two days or so and everything was smooth, including charging etc until one night it had that same grey battery icon again with the circle and would get stuck booting at the samsung logo.
So as this had happened before i thought i would just flash a stock rom....this is where it all started going mad
Bearing in mind, every flash i always did it properly and wiped cache/dalvik cache and wiped data three times for each one just to make sure as i didnt have anything of value so wanted a fresh wipe each time and didnt need to back anything up.
now before i get flamed i realise i made a huge stupid error in not backing up my efs folder before hand as i had done with every previous phone but because i was under pressure to get it working it skipped my mind totally.
So i flashed a stock jellybean 4.2.2 rom and still bootloop with the EFS not found invalid argument error
i flashed a 4.3
i flashed a 4.1
i flashed a different 4.1
i flashed a different 4.2
i tried loads but nothing worked
so after reading that this would not help as it doesnt touch the efs i looked into fixes that others had done
i tried to follow this http://forum.xda-developers.com/showthread.php?t=2197515
So i downloaded efs professional / adb tool
i downloaded busybox
and cwm was already on the phone but i downloaded philz cm incase i needed that too
now as the phone doesn't turn boot up i can't access anything, i can only access download mode and CWM.
When i open efs professional it says current device offline, turn on allow usb debugging to confirm your phones RSA fingerprint and click ok.
I have no idea what to do about that because i can't get into the phone.
Regarding busybox i have no idea how to get that to install on the phone, i have tried writing some stuff to push it in the adb shell (but because its my first time using adb shell and command prompt i have no idea if i am doing it correctly). Can you install it with odin?
also regarding adb shell i followed the guide http://forum.xda-developers.com/showthread.php?t=2197515 and got into [email protected] and SU....and then when on the phone in cwm i clicked mount efs...and obviously it failed. I went into the log as said and /dev/block/mmcblk0p3 was the file it failed to mount
the thing is everything after that step doesnt work, as i can't create an image of mmcblk0p3 as it says it can't find it as if it doesnt exist.
So im screwed as it effectively is saying i don't even have that file or efs folder i think?
The thing is i never had any issue with losing imei or anything like that at all and this just happpened out of the blue without me doing anything as such
any ideas?.....would be HUGELY appreciative for anyone willing to take the time out and help me with this as i'm not sure i can explore any more avenues on my own with my limited knowledge and at the same time don't want to give up.
PS. I also have access to a galaxy s3 i9305 ....and can possibly try and source another i9300 from a family member IF this helps in any way or makes life easier?
Stickied faqs and guides .
No IME/ EFS
service centre repair is your best choice if you have read and tried the stickied fixes .
Reads like efs partition corrupted and your phone was already suffering with nand memory issues.
There is no substitute for an efs backup, you cannot recreate the unique information it contained.
Take it to a reputable repair centre, they will be able to get it back to normal, but you are still left with why it keeps corrupting -which may require a new motherboard.
Sent from my GT-I9300 using Tapatalk
Mod Edit
Please refer to ,and post in the stickies in the General section.
Thread closed
malybru
Forum Moderator
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.