Related
Looking for some help. Trying to install new update, but keeps failing with the android logo and a triangle with exclamation mark after attempting to install. Not sure what I hit but when taking battery out got the following screen. I was on 1.57 with gladroot. Had to sbf flash during the original update process some time ago as didnt get run scripts correctly first time through
Flash back to 26, then 57, then 83. Clean and fresh update is what you need.
Sent from WinBorg 4G using XDA Premium App
had a feeling that is what was going to be said.. going to leave it until I have more time, dont feel like sitting and setting my phone back to how I want it.
When the triangle and exclamation appears you don't have to take out the battery. Only touch the right low corner of the screen and the reboot display appears. I had the same problem at first but the information appeared indicated me what was the problem. Once corrected the update ran well.
logichoops said:
had a feeling that is what was going to be said.. going to leave it until I have more time, dont feel like sitting and setting my phone back to how I want it.
Click to expand...
Click to collapse
I've done it so many times myself now, but I like tinkering. The day I got beta I flashed back to 4.1.26 three times while at work before I ended up being successful with everything because I kept making "operator errors"! I planned for this and took my wall charger to work so I could boot into recovery. Took me over an hour each time to get fully updated! lol
Yeah, you have to flash to a clean version. Most likely you have a mod installed on your phone, and you can update with a mod on your phone.
Are either enabling sideloading or adding the tethering apn that gladroot does for you considered a mod? Just curious what I'm in for when I try to go from rooted 1.57 to 1.83 OTA
Ok, so first off, I was interested in the prospect of using the Droid3 camera because I heard it was better and supported high speed video recording (something that I really want on the Atrix) but I heard that you had to be Deodexed. Well, I knew that if I unlocked my bootloader and installed a custom ROM such as Alien or CherryPie, it would work, but I didn't want to unlock my bootloader. I was rooted though.
So then I decided to google how to manually deodex, and I came across the program xUltimate whatever, followed the directions (although it seemed to be intended for the Droid and not the Atrix, I don't think I should've done that) and part of the process through running xUltimate, I got a message saying that I was out of space on my Atrix relating to the process it was in the middle of doing, and was like, oh crap.
My phone didn't start, but I had made a recovery a couple of days earlier in Tenfar's CMW, so I went to restore that. Then when that was restoring, it froze on some process when it was restoring, and I let it try and try for hours, but to no avail, because it had been hours and it was still stuck on the same spot. So I restarted my phone.
Well, then upon my phone starting, everything was gone in terms of my apps, and the stock gingerbread background was there. I thought, well, maybe it's fine and I'll just restore my apps with TiBu, and everything will be fine. That wasn't the case at all because any app that I downloaded from the market with the exception of a few would automatically force close. So I couldn't get TiBu to work, or Superuser, or anything.
So at that point I knew that I had seriously messed up some files on my phone, and I decided I was gonna flash .sbf. So I got the stock 2.3.4 .sbf and flashed it with RSD Lite 5.3.1.
It flashed gingerbread, and when it rebooted, everything looked fine and dandy, but it was exactly the same problem, where apps would force close.
Then as a last hope of solving the problem I tried to use fastboot to recover my phone with the nandroid backup that I had made, but it said that the image file was too large. And that also probably has something to do with the fact that I can't actually use fastboot to do that unless I have an unlocked bootloader, right?
So my question is, how can I fix it? How can I start over fresh (since flashing .sbf didn't wipe everything) so that those system files that I messed with when I was running the deodexing utility are returned to their proper state?
I mean, at the moment, it works as a phone, it receives and makes calls, and I can send texts and take pictures, and use the stock browser, but no other app will open.
And secondly, has anyone gotten the 120fps video recording working with the d3 camera apk?
But of course, more importantly, how do I get out of this rut?
Thank you so much and I'm really sorry for writing so much, I just wanted to give you as much info as possible so that you could come up with the best answer. And I apologize for my stupidity,
Thanks again,
did you try a factory restore after the sbf flash? you have to do that to restore the phone to the orignal state. flashing the.sbf doesn't do it...
Sent from my MB860 using Tapatalk
thank you so much, after doing the factory reset, it works fine now. Now to go mess with it again hehehe.
Sent from my MB860 using XDA App
Glad your sorted as to your fastboot problem. Use moto fastboot as it splits large files for you.
Sent from my MB860 using XDA App
So, I thought I had fixed the problem, but after unlocking the bootloader, I installed Alien, and the radio is all wonky...I'm not getting service 99% of the time, and that's kinda really bad, and, yes I checked the APNs, and there were no problems there (at least I think, I restored default) and I even tried flashing a radio, which made no difference. And I know that flashing using RSD is bad but I didn't know better at the time so I reflashed stock Gingerbread 4.5.91, but the radio problem is still there.
And could someone tell me what I'm doing wrong because I've tried flashing two different roms (Alien and the Star Wars one) and it seems as if its not actually doing everything that it should, for example the star wars one, there is no camera app, or rather it force closes, and the bootanimation and boot image are stock at&t, and the lockscreen is default....and I even checked the build.prop which should have been modified for the d3 camera and it wasn't modified, which led me to think that anything that involved root access didn't work when flashing the rom. Further proof for that idea is that after I flashed either rom, I lost root access and had to re-root my phone.
This is really weird, and it's starting to bug me because now my phone can't even be used as a phone
Thank you for your help.
The phone was working great, other than the noise cancelling mic cancelling out my voice, but I thought since the update was available, I might as well do it. Once I got on ICS I was having quite a few issues: overall slower, delay in the screen turning on, hotter battery, longer time to charge, wallpaper would flash on before the HTC screen when booting up, there were more just can't remember right now.
I hear about the Global update and think it may fix some of the problems I was having, but they got worse. Now I still have everything I did before (except maybe the hot battery) Also have 3 new issues now: the screen doesn't come back on when I take it away from my ear during a call, browser goes white when going to a new page and I have to reload the page, can't post on any forums in the browser.
Here's the process I went through getting the Global (copied from another forum that I was updating as I was going)
I downloaded it from android police, got to step 6 of the directions, looked away from the phone to see what step 7 was. The phone vibrated and is now on the screen with the green down arrow and 2 in a circle around it. Says "Updating Software from Verizon Wireless" with a green progress bar. Hope I did it right.
That went through rebooted to HBOOT, pressed vol. up twice. It checked everything. Rebooted. Pressed. Vol. up to install. Upadated everything. Pressed power to reboot.
Took a little while on the white HTC screen, now says "Andoid is upgrading..." "Optimizing application [some number] of 77." I think I did it right.
Just checked and everything is right. Woo-Hoo! Not that I'll ever use global, I was hoping it may have fixed some of the bugs I was having, but no
Also of note, I didn't pull the battery. My case is hard to get off, so I just turned off fast boot and that worked.
Click to expand...
Click to collapse
What do I do at this point? My phone is getting less usable by the day as I keep noticing all these bugs.
Wipe your phone clean and use the RUU that android police posted today to install the latest patched OTA clean. That's what I'd try anyway.
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
VooDooCC said:
I'll try that in the morning, thanks. Hopefully all goes smoothly. Still learning how to do things (afraid of rooting, but that's another thread)
Click to expand...
Click to collapse
There are plenty of knowledgeable members here to walk you through it if you just shoot someone a pm. It's all very simple.
As for your problem, try the ruu hopefully that works I'm not sure about the mic canceling out your voice that might be a hardware problem let's hope not
Sent from my ADR6425LVW using xda app-developers app
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
VooDooCC said:
Stupid person time (I don't believe there are stupid questions)
By "wipe phone clean" then flash the RUU. I get the flashing part, but what do you mean by wipe clean. Is there another step in there or does it automatically happen when flashing? I've only been in recovery once, so I didn't really study the options. On my D2, there was a wipe option.
Click to expand...
Click to collapse
The RUU should wipe it but you can go into recovery and wipe /data and /system to remove the current rom.
Making sure I got all this right, but won't be trying until tomorrow afternoon. Only at 40% charge and going out of town in the morning and need the phone.
1. Rename the Android Police download to PH98IMG.zip and copy to sd card (don't have to extract anything out like I did on the .1)
2. Boot into recovery (vol. down and power)
3. Let it start flashing (If it starts automatically, how do I get to the wipe /data and /cache options?) I know it should be wiped auto. but I want to do it myself to make sure.
4. Pray to Andy that there's no bugs this time.
You need to boot into bootloader, not recovery, that will happen when you do the battery pull then start it volume down + power. I'm pretty sure the RUU will wipe everything so you should be good.
Problem with newest ICS
The new ICS has a problem with the browser. Links are squirrelly when touched; sometimes
no reaction, sometimes checks every box on the page. Just does not feel right when moving
around on web pages.
Seems ok to me, I'd recommend Chrome over stock unless you need Flash support anyway.
Sorry, I got the terms confused on the terms. I knew it was vol. down and power though
I finally got around to flashing the RUU, all is well so far, will report back if anything changes.
I'm s-off but my bootloader is unlocked. Do I need to relock the bootloader before flashing the RUU.
Sent from my ADR6425LVW using xda app-developers app
There is a tradition on rezounds to always install an RUU two times in a row, then let it boot up normally before installing custom things like hboots, recoveries, or ROMs.
I used to read posts of people saying that it must be done twice to assure everything gets installed right, and to avoid problems.
So, I recommend doing the ruu twice in a row, especially if your phone was not stock beforehand.
Howard
p.s. my favorite browser is opera mobile.
If s-off and unlocked, there is no need to relock to install an RUU.
Turns out I got a little too anxious. I thought stuff was working, but that was just because I was thankful that I installed the RUU right, still new to this. Still having all the same problems though
When you say install twice in a row, should I just try installing it once again tomorrow or twice since I downloaded an app or two?
Also, you say twice, then boot up normally, when I installed this it just booted up after the install was finished. Is there a way to install it again before it boots for the first time?
method
Make sure the Android Police 3.14.605.12 renamed PH98IMG.zip on your sdCard.
Boot up with Volume down, Power to get into hboot. It will ask your permission with a
Volume up and then run the update. I think they mean after 1st boot, answer English,
and get out of setup with No and default until steady. Do a factory reset in Settings,
Storage and boot up again. Then shut her off again and restart as previously to run that
PH98IMG.zip again.
After the next boot up, insert actual information like Google etc. to start Google Play
and fetch your favorite apps. Then you're running 100% stock.
noticed the same thing with in calls. Pull the phone away from your ear and the screen should come back on, but it seems delayed. I usually have to tap the power button twice to get the screen back on.
Running simplistic 3.0 which is based on the newest leak, after flashing the leak.
FWIW I have the issue with the screen not coming back on after pulling the phone away form your ear as well, however I'm on the ICS OTA, not the global.
I never had the problem on the ICS OTA, but I also only had that for a couple of days before getting the global (.1) from Android Police.
In the process of doing the second flash. As per michaels instructions.
I went to Verizon yesterday and tried seeing about exchanging the phone, since it's having all these problems, and was told no. That it's so common and pretty much every phone has the same things, so it's considered to be working and I just have to wait on a patch. He then told me that if I wanted I could void my warranty and s-off it to go back to GB. I found that kind of odd. Then he tried pushing the Razr on me, I said no I like HTC so then he told me that the Droid 4's are having the same problems too.
So I might be the only person on Verizon who has this problem (I've researched all over the place). I have an issue that is driving me mad with this update. Yesterday, while at work, I was able to update to that preliminary update (the 14mb one) without issue. Immediately after the phone rebooted, I was prompted to download the 500+ mb Sense 5 update. Everything seemed to go well. The update downloaded, the phone rebooted, and started installing the update. Then, about a quarter through the update, the Red Triangle of the Stock Recovery appears, cutting off the update. Out of curiosity, I held up the volume-up and power buttons, and the Recovery Menu came up. On the bottom, where it describes the various processes going on, it says:
Verifying Update Package...
Installing Update...
Verifying Current System...
assert failed: apply_patch_check("/system/framework/apache-xml.odex", "ad2209bdf836715d79558f2fe9c0d474e655afb6", "671aa4acd71a88a36aa5774b9d5334e1a9373162")
Installation aborted.
I have tried everything. I wiped Cache, Did a Factory Reset in three different ways (from the actual OS, from the bootloader menu, and from the Recovery, and every time, the same thing seems to happen. I am effectively stuck on that preliminary update, with nowhere to go. Does anybody have any advice? The phone was never rooted, no S-Off, and the bootloader has always been locked. I'd rather not have to send this one in to VZW, as it was a replacement for a phone that had the SIM card error. This one has been fine for months, so I'm hesitant to get it replaced.
Same here
I am having the same issue. The only issue that I am having is with a book.apk file. Hopefully someone will have a solution.
We're either of you rooted to begin with? If so I believe the OTA update will fail.
Make sure you have several gigs of free space on the phone.
Apply update with full battery or mostly full with charger hooked up.
Or backup, root the phone and download one of the stock update images here on xda.
Good luck.
Sent from my HTC6435LVW using xda app-developers app
Stupid spell check correction
Sent from my HTC6435LVW using xda app-developers app
lsmaverick31 said:
So I might be the only person on Verizon who has this problem (I've researched all over the place). I have an issue that is driving me mad with this update. Yesterday, while at work, I was able to update to that preliminary update (the 14mb one) without issue. Immediately after the phone rebooted, I was prompted to download the 500+ mb Sense 5 update. Everything seemed to go well. The update downloaded, the phone rebooted, and started installing the update. Then, about a quarter through the update, the Red Triangle of the Stock Recovery appears, cutting off the update. Out of curiosity, I held up the volume-up and power buttons, and the Recovery Menu came up. On the bottom, where it describes the various processes going on, it says:
Verifying Update Package...
Installing Update...
Verifying Current System...
assert failed: apply_patch_check("/system/framework/apache-xml.odex", "ad2209bdf836715d79558f2fe9c0d474e655afb6", "671aa4acd71a88a36aa5774b9d5334e1a9373162")
Installation aborted.
I have tried everything. I wiped Cache, Did a Factory Reset in three different ways (from the actual OS, from the bootloader menu, and from the Recovery, and every time, the same thing seems to happen. I am effectively stuck on that preliminary update, with nowhere to go. Does anybody have any advice? The phone was never rooted, no S-Off, and the bootloader has always been locked. I'd rather not have to send this one in to VZW, as it was a replacement for a phone that had the SIM card error. This one has been fine for months, so I'm hesitant to get it replaced.
Click to expand...
Click to collapse
Try Running the 3.06 RUU here: http://forum.xda-developers.com/showpost.php?p=38379254&postcount=19
I rooted the phone before the updates. My phone's Software is 2.08.605.1 Android 4.1.1 and Sense 4+. Where can I download the new Android and Sense version for my phone without doing the OTA update?
Just look in the XDA DNA development forum, scroll down a little ways and you will see posts for the download. There are odex, deodexed, and superstock versions. I am running the superstock with no problems.
djautoclinic said:
Just look in the XDA DNA development forum, scroll down a little ways and you will see posts for the download. There are odex, deodexed, and superstock versions. I am running the superstock with no problems.
Click to expand...
Click to collapse
Thanks for the reply. I used "DNA-Super-Stock-Sense 5-3.06.605.4-v1.0" through Rom Manager and it worked like a charm. As far as I can see it will update OTA if Verizon actually sends out kitkat.
Thanks again.
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.