Installation Android M failed - Rollback stuck with transition package - Honor 7 Q&A, Help & Troubleshooting

Hi,
I installed the upgrade to Android 6 C432B330, after ca. 70 % it said failed. Afterwards the phone booted and the version information said Android 6.
As I didn't know whether everything worked I decided to use the rollback package(hihonor.com/de/support/details/?DOC_ID=77723)
I followed instructions and tried to install firmware(B180) after the rollback package (also tried B121). But it got stuck after 5% every time I tried. Luckily nothing really happened and I can still use my phone.
Now I don't now what to do. I think I'm still on the transition package(my phone is on B300) which explicitly states "must not be used as a normal version" .
What should I do now? Is it safe to try to force upgrade to 6 again?
Thank you for your help!

I took a leap of faith and force upgraded to B330. It did work!

Related

Cannot upgrade or downgrade my unbranded Hero (EU)

Hi,
I really, really hope someone can help me with this: I have an unbranded europeans GSm hero on the Dutch Telfort network. I was really looking forward to the official 2.1 update, but I can't even install the preparing OTA-update (including the YouTube update). I'd be really grateful if someone can help me out!!!!!!
Firmware: 1.5
Build: 2.73.405.5 146733 CL#61267 release-keys
Software: 1.0.0.A62888
My computer: Windows 7 (64), HTC Sync and drivers installed
OTA update
About two weeks ago I received the preliminary update notification on my phone (4.6mb or somehting like that). I downloaded it and in the next window I chose to install it. The phone rebooted, but remained stuck in de HERO screen forever. I removed the battery, rebooted it, changed the date, received the OTA again, but same thing happened. Apparently, the update cannot install.
I figured it might have something to do with my current build not allowing the update, so I tried installing the original RUU from HTC. But that didnt work either: it kept saying "waiting for bootloader..." and eventually gave some USB-error message (error 171). So it seems it cannot connect to my phone. Other RUU's don't work either. Downgrading therefore seems impossible too.
Recovery image
It appeared to me that perhaps my recovery image is broken as I once unsuccessfully tried to root my Hero (Tell me, is this related? i really dont know). I used the flashrec method back then, but it didnt seem to work. Afterwards, other flashing attempts using Flashrec or abd via the terminal didnt work either.
Flashrec gave "backup failed: remote not allow" or "backup failed: image invalid" or somehting like that.Adb says "device not found" or "remote failed" or "somethign similar" Somehow I have the idea the recovery image is corrupted, but the flashrec requires you to back it up before writing the new image. As it wont backup, it doesnt allow to install the new image.
I asked HTC for help, but they were of no avail: they advised me to do a factory reset. That worked, but the problem remains and the OTA update still won't install. I e-mailed them again, but they are not very guick at replying.
Does anyone have an idea how to solve this and has anyone had similar problems? I'd really like to know. To be able to install the official 2.1 would be great, a stable custom 2.1/2.2 rom would be fine too.
Please be very clear in any steps you might describe cause some of the walkthroughs are not really clear to me.
I am even willing to give the person who is able to help me a voucher for some webshop, cause I'm getting really annoyed with my phone now.
There you go http://forum.xda-developers.com/showthread.php?t=647353
I eventually got it to work: I used a computer with winXP instead of my Windows 7 (64bit), which at least helped me install to wipe the phone, install a working RUU and eventually, the OTA update worked.
That was months ago... now I'm trying the 2.2 Sense port for my Hero and it seems to be giving less problems than the official update LOL

[Q] Update to Android 4.4 doesn't work

Hi,
an hour ago I was able to install Android 4.4 on my Nexus 4 via the automatic update.
The Phone turned off, the installation process started. There was a warning, telling me that something is wrong with the certification but I ignored it. After Android 4.4 was installed there was a warning, that I will loose root access. I choose "Fix it". Since then there is an animation on the screen with 4 points flying arround. I tried to restart the Phone, but the animation came up again.
Does somebody know whats wrong with my phone?
thx
Maxi

Note 4 problems with freezing/crashing

I have a sprint note 4. I don't have it activated currently and use it as a tablet of sorts. Recently it's been giving me problems and I've wanted to break it. I got it about 2 years ago, and since then I rooted it, then installed twrp recovery, then flashed custom software. The software I used was called Dr.Ketans I believe, it combined the note 5 and s6 edge plus softwares. It started to crash occasionally so I installed cyanogenmod onto it. It worked for a bit, but now when Turing the device on, it takes like 10-15 minutes to boot up. And it only stays on for 5 minutes before it crashes and freezes. When it does that, the only way I can boot it up again is take the batter out and put it back in a few times because sometimes I get an error message. The error message barely happens but it says something along the line of "cant boot up". If I use twrp, my phone doesn't freeze. I've tried reinstalling the software, I've tried formatting the entire phone and refreshing. Nothing seems to work. I've even tried changing my kernel but I'm not entirely sure what it is, and how it affects the phone. I'm not the smartest with phones, but I'm good with following directions and googling. If anybody can help me I'd greatly appreciate it cause I've been dealing with this issue for 3 months.
Reinstall the original firmware and make sure it doesn't freeze / crash with it and then you can reinstall the custom software. Make sure that you have the required recovery, bootloader, and baseband version to run the newer custom roms. The requirements should be located in the OP.
I appreciate the response. I will try this as soon as possible. Should i use odin to flash or would it be possible to use twrp recovery? Also, what do you mean when you say the requirements are in the OP?
You should use Odin to recover to make sure you have a fresh start.
The requirements of the rom you pick afterwards should be in the OP.

Moto G3 - rooted unsuccessfully, want to return totally to stock.

HI folks.
I'm the owner of a Moto G3 that I tried (unsuccessfully) to root. I managed to reflash the correct firmware to the phone so that it at least worked. I'm currently running Android 5.1, but I'd like to install Android 6 which was installed. Unfortunately, everytime I try to do the update, it downloads and starts the install, reboots (or tries to, it goes to the bootloader screen on reboot every time) several times, and ultimately says update failed. I'm assuming the two issues (booting to Bootloader screen and refusing the update) are related - but I don't know how to fix either of them!! Id like to be able to return the phone back to completely stock with Android 6 running, and with the bootloader unlocked so I can have another bash at rooting at another time.
Help please!!!

EMUI 9 update and eRecovery

Hello, I write from Italy, where I bought an Honor 9 in December 2017.
I never tampered with this phone: no root, nor flashing, nor whatever fancy trick, as in fact I'm not really exactly good with smartphones.
The night between the 20th and the 21st of April 2019, after being prompted by my phone to install the new EMUI 9 update [ STF-L09 9.0.1.162(C432E2R1P5) ], I accepted and let it install overnight (note that the update was downloaded, probably automatically, 1 or 2 days before, but I didn't accept the prompt to install it yet, because I needed my phone for a 15-hours long car trip, and so I figured I wouldn't risk it by installing the update just before my trip - LUCKILY apparently, because otherwise I would have had to stay with this eRecovery thing the whole day without a computer).
I woke up this morning (21st of April) to find it was on eRecovery, giving me the following choices:
(some message I don't remember, probably "Serious problems occurred when the device boot etc. etc.")
Download latest version and recovery
Wipe data/factory reset
Reboot
Shutdown
I did the "Download latest version and recovery" option at first: after clicking it, it searches for WiFi around, and after writing my router password and connecting it to my router, it downloaded the 3941 MB (if I recall correctly) update; however, I left my phone downloading only to find it like this (I was away while it was downloading because I have a bit of a slow internet, so I don't exactly know what happens after it finishes downloading):
(some message I don't remember, probably "Serious problems occurred when the device boot etc. etc.")
Wipe data/factory reset
Shutdown
So I did "Shutdown" and I restarted the phone shortly after, and it restarted itself twice (one was my restart, but after that it restarted itself automatically), then always finishing on the eRecovery with 4 options like I wrote before. I did the "Download latest version and recovery" option again, and I had the same result.
What should I do? I really wish NOT to delete all my internal data, even because after reading some other threads I understood it might even be useless. Do you have any counsel?
Thanks in advance guys, I'm really going crazy and have no idea whatsoever about what to do, please help me!
P.S. I believe I found some other people with my same problem (or atleast similar) on the Huawei UK community site (I'm not allowed to post links yet as I just created this account).
The only way to recover this is download the update completely with pc in install to memory in dload folder after it finishes then boot to download mode and hopefully should work again it sounds like you have faulty update hope this helps
Try to update with HiSuite, if it doesn't work just grab your files with HiSuite and update using dload. If it still doesn't work, warranty claim.

Categories

Resources