Related
Hi, I just upgraded my note 4 which I bought from Singapore (singtel) to android 6.0.1 recently using OTA.
But just after the update, I got a bunch of issues coming out of it.
First, issue on getting the phone on from screen off state, I mean from standby mode, every time I want to unlock the phone from this state, it hangs for at least 10 seconds, after a few test, I found out that it's the fingerprints unlocking causing the problem, so I change it to pattern unlocking, which solved the problem by 80%, it still having hang issue with the unlocking, but less, not like when using fingerprint unlocking.
Next, most of the apps from before upgrade we're using fine, but after upgrade, those apps seems to take awhile to start up, some time more ten 20 seconds.
I search the forum about this 6.0.1 issue, most of them say that a factory reset should do the trick, which I yet to do it after the upgrade.
Actually after these few days of disappointment with 6.0.1, I'm planning on downgrading to 5.1.1.
Therefore, I need a bit advise here:
Should I do a factory reset first or just direct downgrade to 5.1.1?
If downgrade, the steps are:
1. Root the note 4
2. Install custom recovery
3. Install downgrade version of stock rom
Is it? Or did I miss something here?
Thanks a lot for helping out.
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Same deal here but i bought my 6p from best buy along with geek squad protection plan. Rather than send me another 64gb 6p, they've given me a gift card for the price at the time of purchase. At the moment only 32gb versions are available on best buy dot com. I'm not totally opposed to the 32gb version but I'm not excited about it. It took 3 days from the time I submitted my RMA request to get an email telling me this gift card b.s.
I haven't returned anything yet. Not sure what to do. I really liked that phone.
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps. phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
I wouldn't be. Sounds like you are unlocked and rooted. Just keep a good backup on your PC (including EFS) and enjoy your phone.
puddi said:
i had my first bootloop today. i just did a force restart and it booted normal. should i be concerned ?
ps.
phone is only 2 weeks old, and with stock ota update 7.1.1 (rooted)
Click to expand...
Click to collapse
Rooted or not and having a backup or not won't fix this unfixable bootloop. I have one in my possession I'm trying to restore and nothings working. Random reboots a week prior to it going into this bootloop. I've done a bunch of research and it's not good.
thesparky007 said:
My Nexus 6p was definitely one of the batches that should not have passed QC... soft power button, phone shutting down with plenty of battery left and today all of a sudden, while I was using the phone, phone restarts and get stuck in a bootloop...
Phone is not rooted and the bootloader locked... its out of warranty but I called google support anyway and they directed me to Huawei .. luckily, they will fix it for free..
IF you are having the same problem, call google up and hold them accountable for this bull****
Click to expand...
Click to collapse
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
galakanokis said:
Do you have the Huawei contact info? I have tried to go through the online support but I have yet to hear anything in a number of days. Same problem here, bootloop out of no where.
Click to expand...
Click to collapse
Call them here 1-888-5HUAWEI
thesparky007 said:
Call them here 1-888-5HUAWEI
Click to expand...
Click to collapse
Thanks, much appreciated.
I just went through the same thing. Waiting on the RMA box to arrive so it can be sent back.
Sent from my Nexus 6 using XDA-Developers Legacy app
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Going through the RMA process now, thanks again for the number.
I have heard it mentioned that flashing back to 6.0.1 might work, has anyone tried? I did flash all the way back to 7.0 with no luck.
tried flashing back to 6, 6.01 and 7.0 but it still persists. get it exchanged or repaired
It's now several phones a day... At what point does either Huawei or Google fess up to root cause? The one question I have is are all of these hard bricks on phones running nougat??
Sent from my Nexus 6 using XDA-Developers Legacy app
uzi132 said:
Same here...happened just this morning. I can't get into recovery and I can ONLY boot into bootloader. I am on full stock with a locked bootloader running 7.1.1. I got off the phone with a Huawei rep and she stated it could be due to a Google update and that they will try and downgrade it on their end. Strange cause I was already running the latest 7.1.1 (unless a new update was released his morning).
Here's what I tried to no avail:
-unlocked bootloader and tried to flash stock rom/recovery
-tried flashing custom recovery (twrp)
-tried booting into temp customer recovery (twrp)
-tried flashing 7.0 stock
I have re-locked the bootloader and will have to send it in. What a real bummer, I have managed to get out of a softbrick (unless this device is truly bricked ???) on many, many device since the T-Mobile G1, but I am at wits end with this device.
Click to expand...
Click to collapse
You aren't alone obviously. These phones seem to be little time bombs where the boot loop issue is concerned. Mine goes into bootloops every time I flash an update or new ROM or attempt to restore a backup. I expect to hardbrick this phone at some point. It just hasn't happened yet.
Completely forgot about this thread. Huawei swapped out my motherboard with a 128 Gb (I had sent a 64 Gb). I actually quite happy my phone bricked itself. Haha
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
andrewnelson23 said:
My 6p started rebooting last night and no matter what I did, couldn't get it to boot. Only bl mode worked. This thing has been one problem after another, so I went and got an iPhone this morning. Maybe one day Google will finally start making products that last more than one year, but hasn't happened yet and I'm tired of it.
Click to expand...
Click to collapse
On the same boat. Mine's stuck on bootloop, no recovery. 1 year is pretty good considering I've only had the device for 3 months...
Nexus 6p here in the UK, Got the OTA update yesterday and it caused crashes immediately. Had two crashes when it immediately rebooted and seemed ok. A third one soon followed and got stuck in a boot loop, a few minutes after it fixed it self and seemingly working fine. An hour later i was playing a game and it just locked, screenfroze and a buzzing noise from the speakers before going into a boot loop. Left it for a few hours while at the cinema and nothing.
Bought directly from Google and still under warranty. Interestingly though, i bought my 6p in March 2016, I then had to RMA it a few months later as the USB C port randomly broke I will be doing my second RMA in less than a year. When checking my IMEI the google support operative actually stated I was under warranty till August 2018. So a 30 month warranty. Got a new one coming out so if anyone develops this problem give them a ring.
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Narom88 said:
New phone received, sent old one off. Checked it just before i did, still stuck in boot loop.
Click to expand...
Click to collapse
That's way too common with this phone. Thinking about moving on to something else.
Hello,
I just applied the latest update C432B185 on a 8 pro honor; it remains blocked at restart. Another user reports an identical problem on the FRANDROID site.
Do not apply this update because the problem is blocking; you will no longer be able to use your honor 8 pro.
Solution on hold.
Thank you
I have the exact same problem. I started the update, and put it back in my pocket. I grabbed my phone after a few minutes and blindly touched the fingerprint sensor and pressed where normally the home button is. Instead, I catched a glimpse of a black screen, a triangle and a button. The button was at almost the same spot as where the home button normally is, so I clicked it and my phone restarted. After that, the only thing my phone does right now is show the white Honor logo with a lightblue blackground.
I already tried everything that can be done, I think.
Restarted the phone 20 times, did a 'user reset', cleared the cache 20 times and did a lot of factory resets (sometimes stuck at 99%).
Nothing made my phone work again. I also tried to use eRecovery to 'Download latest version and recovery' but that only resulted in 'Getting package info failed'.
If someone has any clue to what can be done to revive the Honor 8 Pro again (or to see some kind of logs to view what's going on), please... help! :crying:
The topic on Frandroid that Pascal was talking about: forum.frandroid.com/topic/261525-mise-%C3%A0-jour-qui-plante-le-smartphone
Hello,
I have exactly the same problem with my honor 8 pro.
I can't use it anymore, the user reset is staying 99%
If someone has a solution...
Also had the update, tried everything, wanted to flash other rom but i haven't got my product ID to unlock the bootloader.
Worst part of all, there is no care centre in The Netherlands...
so what im suppose to do? not sure at all, eRecovery fails,
using the dload method fails.
nothing seem to work atm...
Thank you for sharing this. It's not released in India yet seems but disabled the auto download update over wifi feature just in case.
Also, I can't connect to the phone with ADB or fastboot. /adb reboot recovery returns error: device unauthorized. This adb server's $ADB_VENDOR_KEYS is not set and ./fastboot getvar all returns FAILED (remote: Command not allowed). HiSuite (never tried before) can't find my phone on OSX and crashes after 5 minutes.
No root, no unlocked bootloader. Also shows FRP is locked.
Same here (france) Factory reset doesn't work, dload method doesn't either and the WIFI update doesn't find anything so I'm stuck with no phone for the moment :'(
Same here (Poland). Phone is bricked, second visit in service within 2 months :/
Oh ,god, i was about to let people know that a new update b185 had just come up until i see this post...I immediatly stopped the downloading process of this Update, so bad news for the ones who already applied the update and who got stuck now...
There might be an ultimate solution for bricked phone by using the DC Phoenix unlock software method...
Same Problem with the Honor 8Pro update
Hi,
Same problem in the Netherlands, Brabant.
Just downloaded the update for the Honor 8Pro.
Tried everything, also the eRecovery, Same problem with the package Failure.
Also E-mailed to HiHonor for an sollution, nothing so far.
Somebody got any tip? Can miss my phone for work..
Greeting from Oss, The Netherlands.
Same problem
Same problem here in The Netherlands. Literally nothing works. Never even rooted this device or anything like that. Also, what is this "download and recovery" in eRecovery even for if nothing downloads? I am very disappointed in this. Have no idea what I should be doing while normally I find a way to work around such problems.
TheVeeeMan said:
Same problem here in The Netherlands. Literally nothing works. Never even rooted this device or anything like that. Also, what is this "download and recovery" in eRecovery even for if nothing downloads? I am very disappointed in this. Have no idea what I should be doing while normally I find a way to work around such problems.
Click to expand...
Click to collapse
Zelfde probleem hier en nu een onbruikbare telefoon...
Nog geen half jaar oud!
Ik heb net Honor gemaild .. even afwachten tot morgen..
Sterkte alvast!
Thank you for the warning!
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
OldDroid said:
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
Click to expand...
Click to collapse
I have explicitly chosen to not root or otherwise mod my phone just yet. Does this void your warranty? Right now, I can send it back to the supplier and they will fix it. Of course if something else is faster (supplier says max. 3 weeks) then I am happy to try, if it does not void my warranty.
EDIT: and also, how can I see which version I need? I don't know how for sure which version I have, and of course I can't get into the UI anymore. As I posted before, ADB and Fastboot don't give me any info.
OldDroid said:
flash a stock rom by -=MoRpH=-.
these are factory firmwares and reset your device back to full stock, yes, even with locked bootloader!
Regards
Click to expand...
Click to collapse
Hello,
that didn't work.
:crying:
Krystal666 said:
Oh ,god, i was about to let people know that a new update b185 had just come up until i see this post...I immediatly stopped the downloading process of this Update, so bad news for the ones who already applied the update and who got stuck now...
There might be an ultimate solution for bricked phone by using the DC Phoenix unlock software method...
Click to expand...
Click to collapse
Thank you.
I have made use of many Huawei phones in recent years (Mate 7, Mate 9, P8 Lite, P9 Lite) and Honor 8 Pro. I quickly realized that this update was blocking; it was common sense to inform users of the Honor 8 Pro in order to limit the number of service returns, unnecessary time wastage, etc.
This is our precious ...
Welcome
Here in Holland this morning the same problem.
Thanks for the Info. No update notice for my phone (in Germany). Hopefully Huawei/Honor will have stopped the update rolling out. Jeez, don't these updates get tested before they're released?
You can use Firmware Finder for PC to send an update for installation via erecovery with changing your routers DNS.
Erecovery is used in customer services to install manually sent updates only. That's why it can't find anything without sending an update to your device.
good morning. i waited 8 days after flash stock rom G950FXXU3CRGH with 1 aug patch. yet isn't present the oem unlock button in developer options. i tried during week to do the trick of back date, with no success.... now this situation. what can i do for solve the problem? is perhaps for my rom impossible to unlock oem?
i restarted phone many times in last day....
the date of system is automatic today but i did the trick....
i hope a help
thanks
Same here
Same here with the S9 Plus SM-G965F.
I don't think I have it for a week since I booted and reseted the device but I'm afraid that the OEM unlock option (RMM prenormal) is not time dependent on the August patch - maybe Samsung blocked it completely and we actively need a workaround to get it back.
Definitely that manual time trick is not working anymore and it's waste of time to even trying it on the August patched devices.
hi there i had the same issue, so actualy this is the samsung security guard you have to wait like 7 days to get OEM Unlock button, i did the same but what i did is, changing the dates like for 20 days then i did the update manually few times then i reboot again and again like 10 times the same steps, but i did not get the oem unlock button, so i did wait like 2 days and i have it .
I have the August security patch and my oem unlock shows in the developer menu.
I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Someone?
up.
costafabiof said:
I have an s8 that I have always used with android 8, magisk and rmm state.
When version 9 came out I tried the same procedure and it worked very well, I installed twrp, etc, after updating all Google app and reboot it presents the message "only official realease binaries are allowed to be flashed" and in download mode it accuses KG Prenormal.
In summary is there a way to have root on the S8 with Android 9?
Well I read almost every post back and I could not reach a consensus.
Click to expand...
Click to collapse
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
I just got it to work. I'm just testing the procedure again to make sure and put it here.
I arranged this item like this.
In Android 9, installing TWRP soon after installing Android no longer works, after installing TWRP, it appears in red "only official realease binaries are allowed to be flashed" and restarting in the download mode appears KG STATE PRENORMAL.
To fix I installed Android 9 again without the TWRP, Magisk, etc, that is, pure. I entered the system and started the updates by Google, when I came back to check in download mode KG STATE was with CHECKING which is normal.
With this I returned everything to normal, I installed TWRP, Magisk, etc. and I continued.
spawnlives said:
Yes you still can. I had RMM state prenormal and kg state prenotmal when ii flashed pie on my S8.
For me to be able to install twrp,root and xposed I had to get the
Kgstate = checking
Rmm state = normal ( in my case disappeared from download mode )
While I didn't use the method provided in the link below but due to work commitments over the last few weeks I haven't had time to re-try the method I used as I like to test a few times first as it may have been a fluke. I have an S9 with the same.issue to try on. The process took me about 15 - 20 minutes to do after a lot of trail and error.
Currently for my region the latest security patch is feb. which is the version I used to root the phone.
The issue with the new kgstate is still being looked at. The link below has more info and a another possible short term work around.
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post78966561
Click to expand...
Click to collapse
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
DSMB said:
Do you mind sharing how you did it?
I had my bootloader unlocked and flashed TWRP successfully while on Android 9.0. My phone had a fit so I flashed stock firmware. Turns out my it was actually my mobile provider who had issues, not my phone. Also had to do a factory reset to get back my full 64 GB storage. Somewhere along the line my RMM_State tripped to prenormal. I think KG_State did too. I was fine to wait 7 days, which I did (over 8 days uptime). RMM_state is still prenormal. KG_State does not appear.
I'm wondering if it has anything to do with the fact that my original firmware was region XSA, and I've ended up on VAU (because I'm with Vodafone, though I bought the phone outright from the shops). So my firmware region is XSA, while my Carrier_ID (in download mode) shows up as XSA. Do these regions have to match?
I'd appreciate any advice on removing the prenormal state, even if it involves waiting. Maybe involving flashing an older bootloader? I've done a tonne of searching, and I'm finding it hard to find information that is relevant or likely to work on Pie. Cheers.
Click to expand...
Click to collapse
Have a look here
https://forum.xda-developers.com/sa...ot-install-twrp-samsung-t3747535/post79745844