After spending hours trying to get the eRecovery working and speaking with incompetant Huawei tech support I discovered how to get the eRecovery to finally download the stock firmware and send the phone into a factory reset:
1. Temporarily set your router's DNS address to 188.225.84.142
2. Create a wifi with no password and connect your phone to it while in the stock recovery. I recommend creating a temporary guest wifi for this.
And just like magic it connected and downloaded a 2.4 GB recovery file. Not sure why the F- Huawei would make this so non-user friendly and counter intuitive but hope this can help anyone who was just as frustrated as me.
As of now the phone has a flashing "Honor" logo on it and it's been there for over a half hour but I'll give it more time if it is indeed restoring factory firmware.
Update: the phone wouldn't complete loading or get past the splash screen but I finally managed to issue a "Factory Reset" from the bootloader menu (don't ask me how I got there) and whala - the phone finally booted.
The first and last time I ever go with a Huawei.
Related
Hi everyone
I'm running out of ideas, maybe someone here will be able to give me a hand.
I have a D855 on stock rom (marshmallow), no root (it used to be rooted on LP, but I guess the update to MM 6 months ago disabled it, right?)
Right after turning the wifi on, my phone rebooted by itself, started ok and I was able to use it normally.
The next day, same thing happened, but this time it couldn't reach the lock screen : I'm stuck in bootloop, right back to the LG Logo after it "optimizes app 52 to 52" and "Android is starting".
The phone is still on warranty, but I'd like to backup my contacts (and maybe texts) before droping the phone there.
(I tought sync with my google account was on, but apparently it's not the case, and I lost the 2 last years of contacts...)
I can access the reset factory mode (not an option for the moment since I'd like to backup)
I can access the download mode : I did a Normal Flash with a MM stock rom through LG Flash Tool 2014, flash succeeded but same bootloop problem at the end.
I can access the phone while in download mode via "LG Mobile Support Tool". I tried the "recovery after error" option, it downloaded the last KDZ (I guess) + flashed the phone, but same bootloop problem occurs at the end.
I guess there is a wifi hardware problem which causes the reboot. Is there any possibility to switch off the wifi module before start up? Maybe if wifi module is off, I will be able to turn it on and do a quick backup...
Or, is it still possible to flash a recovery system so I can do a nandroid backup and try to get the infos I need from that? (thought I think I need to be rooted to do so, and don't think I can since the bootloop problem)
Thanks for reading, and hopefully someone will have an idea
I tried with a new batteur today : still bootlopping...
Okay, So let me start from the beginning so I'm certain I'm being descriptive enough.
The other night my G3's wifi stopped working. When I went to turn it on in settings it would turn itself back off. Which I thought was strange. So, I assumed it was a software issue so I backed up any important items and factory reset my phone last night. That went over fine. Wifi worked again, all was good. Until, it said it needed an Android Software Update. I hit "update" and allowed it to do its thing. About halfway through the update the phone said "error." With an icon of the Android bot with a hazard triangle sticking out from it. I let it be for a bit and nothing happened. So in my impatience I took the battery out and put it back in and tried to restart the phone. This is where the issue occurs. The phone keeps booting to recovery mode. I'm not savvy at all with Android so I don't know if these mean anything but it says "Android System Recovery <3e> LRX21Y" The phone has had zero modifications done to it. I would really appreciate any help or any tutorials that could save the phone until my g6 preorder comes in.
Thanks!
Kyle
Your phone failed the update for some weird reasons and is now stuck. I'm afraid you'll need to restore stock Android using LG Flash tools and KDZ files to your device. It will get your phone working, but you'll lose your data in the process.
You can try mounting the phone from recovery or download mode and see if you can access your data and backup the data. You can also try the recovery option without downloading wnloaing a KDZ first.
You can fins tutorials around the forum, in the general section usually.
Having some serious trouble. I rebooted my phone and it asked for my password once it was done as always but this time it said it was wrong. I'm certain I used the correct password but even tried my other alternatives to be sure and still a no go. This isn't the decryption option password you get when booting but my lockscreen password. I booted into recovery and it asks me for an encryption password that I never set but I know this is a common issue with twrp. Tried to go back into android but wouldn't let me because of the "wrong" password so I used the failsafe and went into recoveries file manager and deleted my lockscreen settings to remove my lockscreen passcode (tried and proven method, done it dozen times before). Got past my lockscreen this time but now it was saying starting android forever. Figured it was something with the passcode being deleted so I just decidd to factory reset from the recovery and take that loss. NOW the problem is upon booting the rom in trying to start the setup, I'm stuck on the "just a sec..." screen that comes up after you click start. What do I do from here? I cant access anything in recovery because the encryption passcode issue so I'm kind of stuck. Also I'm a work right now and we cant connect our phones (or any USB for that matter) to the computers and laptops because theyre government property and on a secured line. Any help PLEASE, Ill be home later and can try more then.
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
loeffler23 said:
Well since you already did a factory reset on the device you mine as well just do a clean install of the OFW then get twrp back and flash your ROM etc back. Would probably be better then to deal with everything going on with the device right now.
Click to expand...
Click to collapse
Hey, I got my phone back working after that and rooted again and flashed same rom. NOW another problem, I rebooted my phone and its not accepting my PIN anymore, nor my fingerprint, and I cant reset through TWRP because of encryption. WTF is the issue, how do I fix this or do I have to flash-all again?
Hi guys, bit of a saga here so bear with me...and also it should be mentioned I have little experience/understanding of tech stuff, so that isn't helpful either lol
I've had a Nexus 5x running 7.1.2 for not quite a week; it came with an unlocked bootloader (strangely). Tried to do the usual install twrp & root as I've done with previous phones (all pre-nougat) but all attempts failed. Couldn't boot into stock recovery from the bootloader at all, it would just boot into the system. OK, next thought was that an OTA upgrade to Oreo might work to restore a recovery - but got the BLOD (naturally lol). I found a fix in a modded 4-core Twrp 3.2.1 -0 fbe img + workaround injector zip from osm0sis & XCnathan32 which by some miracle worked.
So far, so good. Ffwd a few days and google play store keeps crashing on opening; I had the feeling that some glitch happened while it was updating, so I tried all the usual fixes like app cache/data wipes and uninstall updates/renistall google play, delete google account etc which failed. Next I tried a cache & data device wipe through twrp - also unsuccessful. Finally, I thought the only thing left to try would be to restore a backup I made on twrp - this led to the current issue of not booting, stuck on the google logo screen. I even thought what the hell! and attempted a factory reset with twrp - same result, where I am now. Google logo screen, however I still have an unlocked bootloader.
Would anyone be able to suggest where I might go from here? I'm pretty sure the version is N2G48C, if that helps.
Any suggestions very much appreciated...wouldn't mind getting to the 1 week mark with a functioning phone lol
Saga #2
Still no idea what's going on. I realised that I'd backed up and recovered the system and vendor .img files, which according to this thread would be a cause of the issue https://forum.xda-developers.com/nexus-6p/help/stuck-google-logo-twrp-backup-restore-t3320840/page3
So I made another backup without those images, did a full wipe and restored it - still does not boot, still only sitting on the google logo. Tried next to open a cmd terminal to see if I could reflash a stock image, but adb could not connect (maybe because the phone would have been on charging and not file transfer mode?)
Last resort as I saw it was to try the NRT, and see if it would flash stock via the bootloop/softbrick option. Process seemed to be OK, judging by the log - but it did not reboot to the system. Now there is a looping bootloop between the google logo and the unlocked bootloader warning.
Following wugfresh's instructions to factory reset from the recovery (the phone won't turn off via the power button so I just booted straight into the bootloader) Looked for the recovery option, selected....and nothing!!
So there isn't a stock recovery??? How does that work?
And what hope is there for this phone now? (I can't think of anything else )
Anyone have an idea? I've never heard of this before tbh!
Well, my problem has been sorted. In the absence of knowing what the hell I should do lol I managed to get a refund for the phone even though it was a refurb to begin with (something to be said for an honest seller who provides a 3 month warranty!) and I picked up a brand new N5x, which was unboxed on Tuesday. Not even 6 hours into setting it up, the phone started to get progressively hotter and then went into bootloop. Got into the bootloader and tried a factory reset - all seemed OK but halfway through the setup process it bootlooped again. Fortunately it was still within the 2 year warranty, and LG didn't argue about authorising a repair for a phone which didn't get even half a day's use on it lol
Authorised Wednesday, walked into the service centre Thursday and a 1 hour wait later had phone in hand with the PCB/motherboard replaced. Has been working fine (and cool!) ever since. Definitely feel lucky to have hopefully dodged a bullet on this one.
Bonus that they upgraded from 6.0 to 7.2.1 while they were at it; apparently LG considers nougat the "latest" stable version for the 5x.
Recently encountered an issue where I was able to get the watch factory reset and wiped then I was able to start the setup process and it started an update, but now its stuck on the multicolor G logo. I have a feeling I will need to do an update with a hacked up cable and ADB. Anyone else experience this?
I don't have too much experience, but the 4 pins at the top of the Pixel watch are just USB, so you should be able to use a hacked up cable to try flashing the stock firmware via fastboot, that is, if you can get a copy of the stock firmware.
So I found a solution by total accident. I isolated it to after the setup when it updates and restarts it would get caught in that boot loop and never actually boot. I was trying it again for about the 10th time after factory resetting which would allow me to at least get to the setup screen and continue forward. So it was on last step of the setup where it downloads the update and pushes it to the phone when I got up and answered the door because my buddy had called to say he was pulling up. Without knowing I walked away with my phone and it must have lost the connection because when I came back the watch was functional and got through that initial boot that it kept getting caught up on. In the watch app I now had a notification that the watch needed to update with the option to download and install. I was hesitant to do so but it worked.