Hi all. I just got my factory warranty back and I attempted to root it. Everything went as it should, until just after the install finished. Instead of rebooting normally, it now will only reboot into TWRP. Once there, when I try to flash a custom ROM (in this case, Bliss, but I don't think it matters, I get an error message that says the zip file is corrupt. Then, while still in recovery, when I tried to wipe everything except the sd card, it says mkfs.fat process ended with error. I then powered down and attempted the factory reset. I scrolled down on both screens and it did not say anything about any errors, so I assumed it took. However, it reboots right back into TWRP recovery. It also boots right to TWRP recovery when I try to boot normally. Of course, adb does not recognize the phone in any mode that I can get into (fastboot/recovery/download), so, I can't use LG Bridge to reflash the original firmware. Does anybody have any ideas for a fix? I know that this replacement phone had 6.0 on it. I thought I did everything to a t? TIA...
OK, not sure how I got there, but when I attempt to reboot from TWRP it says No OS Installed! Are you sure you want to reboot? That at least says what the problem is. Does anybody know how to fix this?
you have the latest twrp recovery? Just make sure you have 3.0 or higher and then try flashing again. And IMO the blissrom isnt worth using unless you dont mind smaller screen, no second screen, wonky Bluetooth and no camera.
AwesomeFabe said:
you have the latest twrp recovery? Just make sure you have 3.0 or higher and then try flashing again. And IMO the blissrom isnt worth using unless you dont mind smaller screen, no second screen, wonky Bluetooth and no camera.
Click to expand...
Click to collapse
Hey, I actually just fixed it. I finally was able to get back into download mode and I then used LG Bridge. Restoring now. Yeah, I actually picked it for some reason I cannot remember when I was faced with having to put in a custom rom as my option. I agree. When I had 5.1.1 everything worked after I got the bloatware out. Not going to get too fancy, I had a bit of a scare.
Related
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.
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click "format data" under the "wipe" section this will wipe EVERYTHING so make sure you have the latest twrp then on your computer save a rom. Wipe the phone via twrp and then plug the phone it and wait for either Adb sideload or mtp. Personally I feel that mtp is the best just because you can move anything to your phone. Then just move the rom you want to the root of the sdcard (Every folder will be gone). Then flash it and hope that fixes it but if it dosent you may need to use the lg flash tool (windows) and flash the zv4 files. This will make you back on zv4 meaning restump root reflash twrp. The whole nine yards, just try the twrp thing first and if that dosen't work then do the flash tool. I am not responsible if you listen to me and your device breaks
bucketachicken said:
I'm using an LS990 that I've had since about when they came out. When Stumproot came out I rooted it, and I had installed the original TWRP Bump when that came out, but I've been running the rom it came with (ZV4 I believe, though I cannot check). Nothing had been unusual until today, when I put the phone in my pocket after using it for normal daily stuff, then when I later took it out it seemed to be in TWRP. I had almost never even booted into it on the G3 other than a very few times when I first installed it (I had been waiting for a CM12 that was stable enough for my liking).
No matter what I do, it seems to be stuck in recovery. I've updated to the latest TWRP (2.8.4.0) and that seemed to take just fine. However, when I try flashing a rom, it just flashes like normal, log says it's great, then....reboot takes me back into recovery. I tried the ZV4 base at first, then the ZV6 base, both with and without wiping all the appropriate partitions, but nothing seems to change. I am getting ready to try non-stock roms, but I thought I'd ask here first to see if anyone has any ideas? Any help much appreciated!
(not worried about my data, I had daily TB backups running which uploaded to Dropbox, so it's all saved, willing to wipe anything and everything)
Click to expand...
Click to collapse
Have you tried this?
http://forum.xda-developers.com/lg-...trying-ota-t2907508/post56061720#post56061720
Thanks, I did get it working. I have no idea how, but my data was all still there, despite wiping several times....but the recovery fix is what worked. I also got that lg flash tool setup so hopefully that will be helpful if I run into future problems. I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again!
I honestly think after all that mess I may try the CM12 roms now, even if they still have some daily bugs, cause I was almost sad to see it boot back up into the LG stock rom...
Thanks again![/QUOTE]
Here is a cm12 rom that is almost perfic: http://forum.xda-developers.com/sprint-lg-g3/orig-development/cyanogenmod-12-beta-ls990-t2958197
It's the one I use everyday and I have seen almost no bugs
I think I'm screwed here. My tablet locked up and I force-powered it down. When it restarted, it went into a soft bootloop and won't load the OS. I'm able to get to my custom recovery and attempted to restore a backup I made in TWRP, but every time I try to restore it displays the screen shown in attached Pic 1, gets to 20% and reboots the tablet. I tried installing a custom ROM and got pretty much the same error (see Pic 2). I can't even wipe the device for some odd reason. All it does is reboot the system. I can get to the screen shown in Pic 3, but I'm not quite sure what my options are. Do I need to factory reset, or do I have a paperweight. I'll sideload if I have to, but I'm not sure of the best way to do this. I'm throwing myself on everyone's mercy here! AAAAAAAGH!
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
jd1639 said:
When all else fails, flashing the factory image with fastboot usually will solve the problems.
Sent from my SM-T820 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Joe_6pak said:
I tried flashing the factory image and it appears to have crapped out. See attached image. I think I got a real problem here .
Click to expand...
Click to collapse
Think this is a better screencap.
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
jd1639 said:
Interesting that bootloader and recovery flash but then nothing else. Try downloading the factory image again. I have seen downloads being corrupted before.
Click to expand...
Click to collapse
Think I should stick with Nougat or download the original factory image (5.0, LRX21Q) that it shipped with? I've also heard rumors that it may be a faulty USP port or cable. Thoughts?
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
jd1639 said:
It should not matter which version of the factory image. It possibly could be a bad cable. Also, use the usb ports in the back of the computer, not the front, if you're using a pc. I haven't seen this being a problem with nexus devices but it has been on some samsung devices and odin.
Click to expand...
Click to collapse
Okay. I used the back USB port and a different cable and I tried flashing the latest Nougat image. Went through without a hitch and it started up but hung on the splash screen and kept rebooting. Flashed the original image and the tablet started up but I got the dreaded "Enter your password" screen. Had NO idea what my password was, so I entered the first PIN that I thought I may have used. Well, that wasn't it, so it took me to a Factory Reset screen because it said I had corrupt data. After a lengthy "erasing" screen, the tablet fired up and I'm back where I started on Day 1. I have no idea if I am still rooted or if my custom recovery survived, but I'm kinda glad the thing at least got started again. My bootloader is still unlocked, and I made sure the "Enable OEM Unlock" box was checked in developer options. Since I just use this for games, email, video watching and an occasional Facebook glance, I'm really not concerned if I'm rooted or not. Obviously I'd like to be, but I'd rather make sure the tabled is updated by a download from Google first. I think my use of Flashfire is what screwed me up in the first place.
Long story short, I'm back up and running, but its 2014 all over again. Will I be able to take the factory update from Google with an unlocked bootloader, and will it be to the latest version of Android? Do you think my custom recovery survived, and is it worth the bother to root and flash it for a (mostly) gaming device? The only thing I can think of that I would want root for is Stickmount (to transfer files) and to get Google Assistant (which I'm pretty sure that I could back-door through Nova Launcher). Oh, yeah, and the adblocking. Let me know what you think. I TRULY appreciate the help, and I'm glad this resource is out there for noobs like me to make it through the Google menagerie.
By the way, does anyone think that going from system to systemless root is what may have caused this?
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
jd1639 said:
I'm glad you're up and running. System or systemless should not have made a difference. I'm sure you no longer have a custom recovery or are rooted. I'm guessing you will get an OTA update from Google
Click to expand...
Click to collapse
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Joe_6pak said:
It took the update just fine. No Google Assistant, but I'll keep trying. Thanks a bunch. REALLY couldn't have done it without your help!
Click to expand...
Click to collapse
Google removed Assistant support from tablets
Hello,
I tried flashing a custom ROM on my samsung galaxy S7 (by the way I've already done this successfully, although I clearly don't know as much as I should).
Firstly I was getting the Error 7 and "your device is ." I did fix that by deleting lines in the updater-script of the ROM. It seems that this has worked, but I couldn't get out of twrp to test it. At first I thought it was an error with my ROM, so I just tried loading the backup I'd made before, but I still couldn't get out of twrp. And there I am, I can't go in download mode, or even power off, it just puts me back in twrp.
I tried updating twrp from a .img but it just didn't work and I'm still in 3.3.1-0. Very strange.
I don't know much of the science behind this, please explain me, I don't want to brick my phone...
Thanks to anyone who tries to help.
Nevermind ?, I just did an adb reboot, got out of recovery, and my backup was applied so... I guess I won't install that custom ROM. I don't know why I had this problem, but I solved it anyway.
While trying to load a rom, I got a failed message, damn cat ran across the desk and it rebooted, I was to the point I should of flashed the overlay, did NOT make it that far. It boots up to the welcome screen, but I have no access to hit "start" as my touch screen is not working. Is it done for? I cant see it any longer in adb devices, so I cant continue where I left off. Linux cant see it at all. Windows knows its there. So it did not make a complete fash, it tried to reboot into stock i assume, looks stock. What can I do at this point? Any help would be great.
deleted
I got in. I can not enter fastbootd, and do not know where its saved. Can some one help me get my recovery back? I flashed a recovery backup, but it comes up witht he little dead andriod and no command error. I need to get to fastbootd. Any help would be wonderful.
If you can get into fastboot, isn't there a tool, LMSA rescue to bring back bricked device? wipes all data though.
Were you trying a custom ROM or stock? try booting to fastboot mode, power + vol-down, and fastboot flash the stock boot.img, can be found here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
hope this helps. I just got the phone yesterday, soft bricked trying to flash magisk, flashed stock boot and was back in business. I was not using any type of custom rom though.
I was able to find stock boot and recovery images, which allowed me to just start over. Here is an screen shot of what would happen when flashing any ROM.
That's two different attempts. With two different errors.
On a crazy note, I ordered and got in the exact same phone off eBay, has lineage os, magisk, twrp. Now from what I've read, twrp can't be used to install ROMs yet. I've actually tried it on the problem phone we are working on here, but can't swipe with it. The screen is not correctly responsive. Yet this eBay phone, works great... Not sure how he did it. Id love to figure this out, I can't let it beat me.
klloyd said:
I was able to find stock boot and recovery images, which allowed me to just start over. Here is an screen shot of what would happen when flashing any ROM.
That's two different attempts. With two different errors.
On a crazy note, I ordered and got in the exact same phone off eBay, has lineage os, magisk, twrp. Now from what I've read, twrp can't be used to install ROMs yet. I've actually tried it on the problem phone we are working on here, but can't swipe with it. The screen is not correctly responsive. Yet this eBay phone, works great... Not sure how he did it. Id love to figure this out, I can't let it beat me.
Click to expand...
Click to collapse
I would try this next: https://support.lenovo.com/us/en/downloads/ds101291-rescue-and-smart-assistant-lmsa