Can't Update to JB. 0x13e Error when installing. - AT&T LG Optimus G

As the title states, I get the 0x13e error when updating via the OTA update.
It will download, reboot the phone, begin installing. When it gets to about 4 or 5%, it will display 0x13e.
The most likely culprit is that I have CMW installed. I am also rooted and on stock E97011c. I have done the Fast Dormancy mod in the past as well, although I have done a full wipe after that.
I've searched Google and the forums with no definitive answer.
Any workarounds or will I have to wait for a .ZIP to flash?

It's because you're using a custom recovery (in this case, CWM)
If you can, relock and try again, or wait as you suggest.
I say "if you can" because your phone might now say that you're up to date, even though you're not

shrike said:
It's because you're using a custom recovery (in this case, CWM)
If you can, relock and try again, or wait as you suggest.
I say "if you can" because your phone might now say that you're up to date, even though you're not
Click to expand...
Click to collapse
even if it says you are up to date and to check back in 24 hours you can just go to applications>all>com.lge.omadmclient and force stop/clear data. After that it will reset the timer and you can check again right away. I LGNPSTed back to 11c and had to do this a couple times before it found the update.

I would wait, don't relock or anything. A flashable zip will be available soon, I'm sure.

StriderMage said:
even if it says you are up to date and to check back in 24 hours you can just go to applications>all>com.lge.omadmclient and force stop/clear data. After that it will reset the timer and you can check again right away. I LGNPSTed back to 11c and had to do this a couple times before it found the update.
Click to expand...
Click to collapse
Not necessarily. 11c has been out for months any my phone only just decided to let me know that it was available this sunday just gone (I've been on 10o since December, and have checked for updates a couple of times a week since). After the 11c update failed (same issue - I have a custom recovery), it's gone back to saying I'm up to date, no matter how many times I clear the data for com.lge.omadmclient and recheck.
And pro-tip: No need to force stop it, just clear the data.

It still shows that I can re-download the update if need be. I think I'm just going to wait for a flashable .Zip to become available. Shouldn't be too long anyway. If a week or so passes and no one has made one, I'll either A)Figure out how to do it myself or B)Revert to stock recovery, if I can, and install.
Thanks all!

Related

[Q] ****SOLVED**** Error updating to OTA?

So, im trying to install an update that i received a notification for...i believe its the one that helps with 3g connectivity and what-not. But while trying to install it, I rebooted to a black screen with a ! inside a triangle and the little android standing next to it...what does that mean?
I let it sit for a GOOD long while, yet nothing happened. Does this mean i can never update?
***This has been solved. My last post in the thread says what i did.***
If you are rooted and you tried to do the OTA then you'll brick your phone.
i was rooted with stock. the OTA came up while i was texting and normally i hit reject, but i accidently hit ok while texting and now every time i start up, it says "Powering Down..."
Any OTA flashed over a rooted device will brick it, I believe.
Edit: Well I found this. May help.
http://www.thunderboltforums.com/fo...-get-rid-ota-forced-reboots-rooted-phone.html
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Superthrust said:
got it...
i had to boot to recovery (i could stil get into clockwork, odd i know...)
wipe cache, and wipe dalvik...hour, and no issues.
Click to expand...
Click to collapse
Glad to hear you're good to go!
Don't flash OTAs when you're rooted next time!
^_^_^

[q] is there a stock recovery mode???

I just bought a new Prime a couple days ago and installed the offical ICS update.
Today it's been going into a bootloop rage LOL.Is there a stock recovery that I could clear caches if that even exists..Any advice will be graciously welcome!Thanks
Not until ASUS unlocks the bootloader.
Dougfresh said:
I just bought a new Prime a couple days ago and installed the offical ICS update.
Today it's been going into a bootloop rage LOL.Is there a stock recovery that I could clear caches if that even exists..Any advice will be graciously welcome!Thanks
Click to expand...
Click to collapse
Yes there is a stock recovery, but it will not help you in any way. From it, you can do absolutely nothing. Sorry to be the bearer of bad news but that's just the way it is at the moment.
To get to it you need to switch off the device, then once it is off, hold (volume down + power) this will bring you to a screen saying push 'vol up' for RCK. You may get lucky and clear whatever it is that's misbehaving, but it will only look at what is in it's own recovery partition, which for most is "Jack Sh#t"!
The other options after the countdown are factory reset (which clears only user data and has no relevance to the /System partition), or "cold boot linux" which is self explanatory.
I wish you luck in your endeavours.
Bro this thing reboots every 10 minutes! When on the power cable,it stabilizes.
Before I bought, I read on all the issues but took the dive in but this is ridiculous!
I read theres an update next week to fix this issue but the last update was to do the same fix Oh well.I'm waiting for the update and if it doesn't resolve this then Imma gonna give bestbuy a little visit
Dougfresh said:
Bro this thing reboots every 10 minutes! When on the power cable,it stabilizes.
Before I bought, I read on all the issues but took the dive in but this is ridiculous!
I read theres an update next week to fix this issue but the last update was to do the same fix Oh well.I'm waiting for the update and if it doesn't resolve this then Imma gonna give bestbuy a little visit
Click to expand...
Click to collapse
I misunderstood and assumed that you were simply in a boot-loop. Whatever software version you are currently on, .11 or .13 you could try the actual update procedure from the sdcard. But only if you can boot into the system properly.
All you do is download the relevant zip, then unzip it. You will now have a new zip that you put on the root of your sdcard and start the device up. This will re-flash your current software version and possibly sort out your issues, it has helped several people in the past.
I for one would just back up any photos, videos etc... then do a factory reset followed ny this flash technique. Do not use titanium backup to restore apps, just restore them one by one from the market.
This method eliminates any possibility of bad user data causing problems, then you will know that it is the device causing the issue.
I'm still from the old school where most computer problems are user related and not actually software related. ASUS are slowly making me re-think that though.
Im on build # 9.4.2.13 from like two days ago.I don't want to root it just yet, the instructions you gave me seems for root and custom recovery right?Thanks Doktaphex
Dougfresh said:
Im on build # 9.4.2.13 from like two days ago.I don't want to root it just yet, the instructions you gave me seems for root and custom recovery right?Thanks Doktaphex
Click to expand...
Click to collapse
Nope, for straight up standard ASUS non-rooted vanilla loveliness. Just go to ASUS website, find the download area for the Prime, download the .13 US firmware, unzip. Do not unzip the zip, that the unzipped zip gives you (I hope that bit makes sense ). Then put that onto your sdcard root directory (ie. do not put in a folder, just put it on the card) then stick it in the Prime, fire it up and the Prime should see it as a firmware update, you choose this and voila. Profit.
Ok dl'd to my ex-sd fired it up and nothing copied it to internal sd and nothing...
EDIT: I dl'd the Taiwan update instead(stupid).DL'd the US update and ran it to no improvement.Factory wiped and reinstalled and still getting reboots constantly.Does anyone think I should regress to .11 and then manually install .13 again...I'm thinking there's no benefit till the supposed new update next week
Dougfresh said:
Ok dl'd to my ex-sd fired it up and nothing copied it to internal sd and nothing...
EDIT: I dl'd the Taiwan update instead(stupid).DL'd the US update and ran it to no improvement.Factory wiped and reinstalled and still getting reboots constantly.Does anyone think I should regress to .11 and then manually install .13 again...I'm thinking there's no benefit till the supposed new update next week
Click to expand...
Click to collapse
You cannot downgrade to .11 unfortunately. I hope it gets fixed up soon though.
Honestly man I wouldn't wait if you you got it retail I would just go for an exchange if you can stock seems to be loosening up......who knows if the update will work or come on time and I'm a firm believer in once something starts showing signs of problems it rarely gets better it usually continues or gets worse
Sent from my PG86100 using xda premium
pbg225 said:
Honestly man I wouldn't wait if you you got it retail I would just go for an exchange if you can stock seems to be loosening up......who knows if the update will work or come on time and I'm a firm believer in once something starts showing signs of problems it rarely gets better it usually continues or gets worse
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
Agreed! I have one on hold at bb for Monday. Imma leave it on HC if it's not pre loaded with ics...I'll check back afterwards thanks gentlemen!!!

Can't update stock rom, "Communication Failed" from Software Update

I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
I'm not sure if I'm the only one who is having this problem but I've searched around and can't fix the issue. I recently had CM9 but went back to complete stock, on 2.3.4 (which isn't up to date). When I go to update from the settings menu, I get a communication failed text box, which then in turn makes me wait 24 hours before checking again.
I've done multiple battery pulls and stopped the running process for the software update to no avail. Can anyone help me with this?
Remember, I'm on the stock AT&T rom.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
Are you rooted? And why update to 2.3.6 uckk6? Its got a few really bad bugs.
Sent from my SGH-I777 using XDA App
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
myownwitness said:
Not rooted. I just want to get my phone up to date so when the ICS update rolls out I'll be able to get it.
Sent from my SAMSUNG-SGH-I777 using XDA
Click to expand...
Click to collapse
If*
Sent from my SGH-I777 using XDA App
Thank you for your helpful information.
Sent from my SAMSUNG-SGH-I777 using XDA
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
jcracken said:
I think others were having trouble updating as well... I'd suggest flashing a custom rom, or if you want to stay with stock, using Entropy's Back to Stock packages (I'm not going to link that for you cause I'm too lazy and you should be able to find it.)
Click to expand...
Click to collapse
Might give it a try. Trouble is, not having a rooted phone and going back to stock means I lose all applications and data with them. Eh. Thanks
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Phalanx7621 said:
Download stock rom (if u can get a tar file it most likely has everything u need, do some Googling just make sure its for the i777). Get mobile odin pro. Use mobile odin pro to flash the .tar and it gives u the option to root right there within the app before u flash. Profit. Just giving my two cents and what worked for me . If u do this though and don't remove any system apps it should allow u to ota upgrade. Haven't tried myself but that sounds like it'd work fine.
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
I already did this except for rooting about 3 weeks ago. From what you're saying, if I root my phone from its current state I should be able to receive OTA updates? I'm willing to root just to see but I don't see how that would fix the "communication failed" errors for updates.
Sent from my SAMSUNG-SGH-I777 using XDA
FYI I have a rooted stock ROM, and I'm having difficulty doing an OTA update also. Different error (mine is "interrupted" after reboot). I posted it here because it seemed more related to that thread and I had other Q's about the process.
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
LiLChris06 said:
You guys are in panic mode, wait till we actually get an ANNOUNCEMENT for ICS from AT&T, then try to go back to stock using the methods we have.
No reason to do so right now, since AT&T will probably take a long time before pushing it.
We have a possible sources dropping on March 15th from i9100 but you will be required to be rooted to flash the possible ICS Roms that will be available after that date.
Click to expand...
Click to collapse
I don't think you understand. First of all, in no way am I in panic mode. Secondly, my phone is a few updates behind since I just recently brought it back to stock from CM7. All I am trying to do is bring it up to date.
Sent from my SAMSUNG-SGH-I777 using XDA
ota issue
You might want to check the (Guide)How to flash custom binaries.....on this forum. Creepycrawly has posted a reply towards the end of the thread that might be helpful. Believe its on one of the last two pages.
As has been said many times in other threads, even on a stock ROM if you have rooted and removed even one item of bloatware or made any other mods you will not be able to download an OTA update.
I have not rooted my phone. And as I said earlier, I restored my phone to complete stock meaning no bloatware has been removed. I'm still at a loss for what to do
Sent from my SAMSUNG-SGH-I777 using XDA
You were on CM9 (in a later post you say CM7), but you went back to stock UCKH7. Now you are unable to update over the air to UCKK6. You are mainly interested in having the phone ready to receive the update over the air to ICS, whenever that occurs. You have not rooted the phone since you returned to stock but you are willing to try root if it will help the update happen. You were also concerned about loosing apps and their data since you are not rooted. I recapped all this because on stock you should be able to run the update. To help you solve the problem, need to know all the facts.
I've done the following, although it has been several months ago, about a week or two after UCKK6 first released. From running a custom rom, I did a wipe data/factory reset, flashed stock UCKH7 plus root, and ran the over the air update to UCKK6 successfully, retaining root on UCKK6. I just did this to test it out, so after completing the test, I used my nandroid backup to return to the custom rom I was on.
I would assume that you did a wipe data/factory reset either before or after you flashed back to stock? If not, there could be traces left over that could interfere with the update process. I'm not sure if there could be traces left even after a wipe data/factory reset, but the Cyanogen Mod file structure is so very different than stock that it wouldn't be inconceivable.
Next, I would wonder how soon after flashing back to stock you tried to run the update, and if not immediately, what action could have possibly placed or removed files that would intefere with the process.
I'm pretty certain that if you were to wipe data/factory reset with a format and then flash stock again, and then try to run the update immediately, it would succeed. So there has to be something in the file system preventing it. You may not find it easy to correct that something manually. You may just have to do a wipe data/factory reset, and maybe a format, and then start all over with a fresh install.
Of course, that is the reason for rooting first. Root, then back up everything with titanium backup, SMS backup, export contacts, etc. and save all that to your computer. Then you can restore stuff after.
Thanks creepy,
I'm in the process of doing what you said. I rooted my phone, backed up everything I thought needs to be backed up and flashed the stock rom (2.3.4 kernel version 2.6.35.7 baseband version I777UCKH7). I still need to do a factory format in order to see if that will fix the update problem.
Question. Is the firmware version(s) above the latest AT&T software? According to Kies, it is. But I am reading other places that the latest software is android 2.3.6.
Did exactly as creepy stated. Brought the phone back to stock software and did a factory reset. Without ANY customization and as soon as the phone booted up, I did the software update and had the same thing, "Communication failed" (says there is an update available but servers are busy).
I give up.
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
creepyncrawly said:
Well, I don't have any new ideas. Maybe if I get some time in the next few days I'll try it on my phone to see what happens. It has been a while since I tried it. Maybe the server behaves differently now?
Click to expand...
Click to collapse
From what I've been reading on AT&T forums (http://forums.att.com/t5/Samsung/Sa...2-3-6-OTA-update-now-live/td-p/2996495/page/3) I don't think so. I've been trying every combination I can think of to make this thing work but I honestly have no idea. I was extremely surprised when I brought the phone back to complete stock and no root and still couldn't get the update.
If ICS ever comes to AT&T GS2, I'll wait a month or so to keep trying then I might resort to going to an AT&T store to get a replacement. Who knows

Huawei Ascend P2 probems

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.

[RESOLVED] Recovery not sticking

I previously had root/recovery through my unlocked bootloader with knox tripped on 4.4.2. deciding to update, i flashed a stock rom and tried to get the lollipop update via OTA or KIES, but neither worked. it kept lying and saying i had the latest update. i took my phone back to the tmo store and they ran a diagnostic that said i needed a firmware update. once i got that update, it made it so that my baseband matched the build number (the build never updated when i flashed stock or some bs). from there, i was able to OTA to lollipop.
that completed, i tried to odin many varations of custom recoveries. tar.md5s and tars. TWRP and CWM. in all cases, the first boot worked and let me into the recovery. in all cases, when i rebooted and ONLY WHEN I ALLOWED THE ROM TO LOAD after that reboot, i lost the custom recovery.
how do i make the recovery stick? one item that i've noticed is that when im flashing the recovery tars, if "auto reboot" is checked, the phone reboots BEFORE i get pass. the ONLY way to get the recoveries to work for the FIRST time is to turn "auto reboot" off. when i flash, it always takes like 10 minutes from the time i upload the file to the time it will say "pass". this is contrary to EVERY tutorial that i've watched. in all of those, reboot is there, but pass happens before the device reboots.
well, it must be this:
http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
so i'll root first and then go from there.
worked perfectly.
hooray for self help
Great tutorial.
But you need to calm down.
Pp. Lofl.
PanchoPlanet said:
Great tutorial.
But you need to calm down.
Pp. Lofl.
Click to expand...
Click to collapse
heh, kid, if you think this isn't calm, wait till you graduate from HS and see the real world..
Angry Black Man said:
heh, kid, if you think this isn't calm, wait till you graduate from HS and see the real world..
Click to expand...
Click to collapse
Lol. I graduated from HS in 1976, thanks for the "kid" part.
The real world is what you make of it.
Pp.

Categories

Resources