Related
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
Thanks in advance,
Federico
Click to expand...
Click to collapse
This Should Help You.
https://forum.xda-developers.com/honor-8/how-to/to-emui5-custom-roms-tested-openkirin-t3638445
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
I assume since you rolled back you have a locked bootloader atm.
Now i know these guides are somewhere but now that you mention it they do seem somewhat hard to find. ( on the app anyways)
But as for rolling back and then updating again via dload ( not TWRP) you need the rollback package and official firmware for your phone model.
Google and/or the guides section here should help you find those.
It should give you two zips containing an UPDATE.APP file each.
You need to put these on a folder named dload (one file at a time)on your sdcard( internal storage should do, too but no guarantees).
Create the folder if it doesn't exist.
Put in the rollback update.app in first.
Then power down and hold vol up+ vol down while powering up and it should flash the file.
Let it finish, boot up, put in the update.app from the firmware in the dload folder ( remove the old file) and repeat the process.
That should be it.
Also, you might be able to sinply dload the actual firmware from the test key build without rolling back but i haven't tried ( i think )
Should the dload process fail, you most likely have the wrong file in your dload folder, or multiple files.
I should mention that the rollback file actually brings you to a test.keys build. It's necessary to flash to full firmware afterwards and dloading the rollback file has always worked for me.
Personally i found that keeping the rollback update.app file for the rollback in the dload folder at all times is a good security measure. (besides the usual backups)
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
can you tell me what rollback package to use? i tried "(FRD-L19&L09, from Android 7.0, EMUI 5.0 to Android 6.0 EMUI 4.1, C900B300, Western Europe)" and didn't work
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
SharxX8 said:
If you have an L09/19 it should work. Just make sure to flash the rollback package first.
Otherwise since you are on a test key build already, you might want to try to dload MM directly or if that doesn't work, try a stock nougat firmware via dload.
You could also try updating with Firmware Finder via proxy
Sent from my OnePlus5 using XDA Labs
Click to expand...
Click to collapse
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Federico Cervelli said:
i'm at 4.1 b131, now should i update via updater (ver. L09C432B380 2,36GB) or it's test keys?
Click to expand...
Click to collapse
If you are on a regular version of MM, as I understand it, you can update normally, yes
SharxX8 said:
If you are on a regular version of MM, as I understand it, you can update normally, yes
Click to expand...
Click to collapse
but last time i did it it brang me to test keys .-.
EDIT: i tried and it's all working, Thanks!
Federico Cervelli said:
I have read about this problem on another thread but the problem was poorly explained and i couldn't follow to the processes explained on the replies, so i have created another new thread regarding this problem, because, in addition to being very useful for me, it might be even more useful for people that are searching for a solution.
I will explain briefly the scenario before talking about the problem itself.
I recently (1d ago) got my telephone blocked because of a Hard Brick that i managed to overcome using
DC Phoenix, from which i installed Emui 4.1 and then automatically updated via the built-in updater to Emui 5.0
As before my hard brick i was on a more recent build, Emui 5.1 (B394), i searched on the internet and understood that my current Firmware, "NRD90M test-keys" is a test build (or something like that) which can't be updated with the built-in updater.
So, i want to ask, in order to avoid getting bricked again, if there is a way i can update to the latest Emui available for my device, as in the current state the build, in addition to being obsolete, is also unstable and reports some compatibility errors, E.G. error retrieving microphone service when sending audio messages on WhatsApp, ecc.
i have heard of a method consisting of rolling-back the device to 4.1 again and installing 5.1 via Dload, but can you tell me how to do it more in detail?
EDIT:
Problem solved by rolling back to 4.1 b131 and then updated from internal updater app
Thanks in advance,
Federico
Click to expand...
Click to collapse
I am in a very similar situation and unable to solve this. Could some one help in this?
I had unlocked bootload, TWRP and Root. I decided to unroot and lock the bootloader. So, by following the steps mentioned in a different thread, I could successfully flash Marshmallow B130 through Force Update.
Steps followed:
1. Flash Rollback package
2. Flash Full OTA (Marshmallow on B130) from Huawei website which flashed
Now, the real problem started while trying to upgrade to Nougat.
I tried downloading B350 firmware from Firmware Finder. After slow download, it installs fine. But, after reboot I face below problems.
1. The OS is very sluggish and crashes so often
2. The build number says NRD***-test keys
3. No keyboard installed, so not able to login to Google as well.
4. At this point, Factory Reset, Wipe Cache Partition, rollback everything fails.
I had to unlock the bootloader and again force update Rollback Package and then to Marshmallow B130.
Now, I am stuck with B130. I tried downloading B340 and B361 thru Firmware Finder. Both of them installed but with the same result. I mean No keyboard, Test-keys build, Crashes
My Honor 8 model: FRD-L02
What should I do upgrade to Nougat? I have no confidence in Firmware Finder method. Any help appreciated
It's EMUI 5.0.1 not 5.1, I think.
Hello.
I've read through the forums but am still quite unsure if i can restore my honor 6x from soft brick. It boots up but i get stuck in rescue mode if i have it charged Or it will just boot-loop if its not plugged in.
Im unable to use the DLOAD method. If i enter fastboot and use the three button method. I get put to the rescue screen. However i may be using the wrong firnware? Possibly.
Its a China version. PE-UL00 given to me from a friend, he said he had restored it to factory settings. So i wanted to upgrade the android kit kat to lollipop version. It was running emui 3. Kitkat 4.42. I believe updated the wrong firmware file through the local update method I download from firmware finder.
Basically from what ive read through the forums would i need to unlock the bootloader and flash stock firmware? . I have the information to acquire the bootloader key i believe and. I have downloaded honor multi tool and huawei multi tool, as well as adb drivers
I get confused as to which stock rom or. Firmware i should download or use. And i cant access the phone to see the build number. All i know is that it's. A China version. PINE-UL00. HONOR 6X. I do remember seeing
UL00_V100R001CHNC00B200 or similar when i was able to access the phone. But it also had custom at the bottom so i wasn't sure if it was a custom rom.
Any suggestions for a noob. Thankyou.
Pabloh14 said:
Hello.
I've read through the forums but am still quite unsure if i can restore my honor 6x from soft brick. It boots up but i get stuck in rescue mode if i have it charged Or it will just boot-loop if its not plugged in.
Im unable to use the DLOAD method. If i enter fastboot and use the three button method. I get put to the rescue screen. However i may be using the wrong firnware? Possibly.
Its a China version. PE-UL00 given to me from a friend, he said he had restored it to factory settings. So i wanted to upgrade the android kit kat to lollipop version. It was running emui 3. Kitkat 4.42. I believe updated the wrong firmware file through the local update method I download from firmware finder.
Basically from what ive read through the forums would i need to unlock the bootloader and flash stock firmware? . I have the information to acquire the bootloader key i believe and. I have downloaded honor multi tool and huawei multi tool, as well as adb drivers
I get confused as to which stock rom or. Firmware i should download or use. And i cant access the phone to see the build number. All i know is that it's. A China version. PINE-UL00. HONOR 6X. I do remember seeing
UL00_V100R001CHNC00B200 or similar when i was able to access the phone. But it also had custom at the bottom so i wasn't sure if it was a custom rom.
Any suggestions for a noob. Thankyou.
Click to expand...
Click to collapse
I downloaded dc unlocker, but it doesn't support the boot loader id for PE-UL00 honor 6x. Im still waiting on huawei for the bootloader code. I think k have to log in for 14 days consecutively? I keep getting that message when I try to unlock.
Also the firmware I tried to update it was PE-UL00C00361 OTA-MF from firmware finder.
I downloaded dc phoenix unlocker. Found the correct stock firmware to the best of my knowledge and the phone back to normal. After I was able to update to marshmallow through system updates.
Thank you anyway
Hello all,
I got a ZTE Grand X view 2 (K81) tablet from virgin Mobile in Toronto, Canada and I have the sim locked to my imei number. I would like to root this tablet so I can remove unnecessary applications. It is slow as it has <1gb and the internal memory is 8gb. So far the one click root apps I have tried (kingroot, iroot) don't work. What are other options I have for this device?
It is running Android 7.1.1 with the June 1, 2017 security patches
Thanks Karl
binholz said:
Hello all,
I got a ZTE Grand X view 2 (K81) tablet from virgin Mobile in Toronto, Canada and I have the sim locked to my imei number. I would like to root this tablet so I can remove unnecessary applications. It is slow as it has <1gb and the internal memory is 8gb. So far the one click root apps I have tried (kingroot, iroot) don't work. What are other options I have for this device?
It is running Android 7.1.1 with the June 1, 2017 security patches
Thanks Karl
Click to expand...
Click to collapse
One-click root apps won't work. You either go the Magisk patched boot way or Custom recovery + Magisk / SuperSU zip.
What's your phone's chipset?
Hovatek said:
One-click root apps won't work. You either go the Magisk patched boot way or Custom recovery + Magisk / SuperSU zip.
What's your phone's chipset?
Click to expand...
Click to collapse
Honestly I don't really know what the chipset is. From CPU-X, here are some more details:
Cpu: cortex-a7 snapdragon 210, 1.1ghz x 4
Board: Helen
Hardware: qcom
Model: K81
Brand/manufacturer: zte
Bootloader: unknown
binholz said:
Honestly I don't really know what the chipset is. From CPU-X, here are some more details:
Cpu: cortex-a7 snapdragon 210, 1.1ghz x 4
Board: Helen
Hardware: qcom
Model: K81
Brand/manufacturer: zte
Bootloader: unknown
Click to expand...
Click to collapse
Its Qualcomm. To root, you'll need either stock boot.img or recovery.img. Do you have the firmware for your model?
Hovatek said:
Its Qualcomm. To root, you'll need either stock boot.img or recovery.img. Do you have the firmware for your model?
Click to expand...
Click to collapse
I don't have that yet, I will need to search for that. My SD card is currently set as an internal, not portable, is that a problem? Is there a way to copy the current boot.img or recovery.img from a running system? I have installed magisk manager, I just need to get a hold of the boot or recovery files
binholz said:
I don't have that yet, I will need to search for that. My SD card is currently set as an internal, not portable, is that a problem? Is there a way to copy the current boot.img or recovery.img from a running system? I have installed magisk manager, I just need to get a hold of the boot or recovery files
Click to expand...
Click to collapse
Have you had any luck finding firmware for this device.... i need to frp bypass mine as i bought it online and am left in a predicament now... The keyboard doesn't allow to access any settings so getting through the FRP part is an issue... no way to downgrade the firmware either because it is running 7.1 . I also can't find custom recoveries anywhere i look online.... if you have some insight or a solution please let me know.
thanks
wallyradburn said:
Have you had any luck finding firmware for this device.... i need to frp bypass mine as i bought it online and am left in a predicament now... The keyboard doesn't allow to access any settings so getting through the FRP part is an issue... no way to downgrade the firmware either because it is running 7.1 . I also can't find custom recoveries anywhere i look online.... if you have some insight or a solution please let me know.
thanks
Click to expand...
Click to collapse
Not yet, I switched my SD card back to portable and tried to look around the system using adb shell without any luck. The system is locked down tight and I don't have permission to view most directories. I also contacted ZTE for the recovery img, they thought I was talking about backing up photos
I have same tablet from virgin mobile Canada. I have solid explorer, and it allows me to have root file access out of the box. I deleted bloat apks, was gtg. Not sure if it's normal behavior. I was shocked to see root file system out of the box. P.S any developers that a full system dump would help, I can probably do. After more poking around, I don't have full root access, but I do have read/write to system folder with build.prop etc
jonjadot said:
I have same tablet from virgin mobile Canada. I have solid explorer, and it allows me to have root file access out of the box. I deleted bloat apks, was gtg. Not sure if it's normal behavior. I was shocked to see root file system out of the box. P.S any developers that a full system dump would help, I can probably do. After more poking around, I don't have full root access, but I do have read/write to system folder with build.prop etc
Click to expand...
Click to collapse
I just downloaded and installed solid explorer and the classic versions. Not luck viewing the / file system. If you can get the boot file and post a link to it that would be helpful for the magisk rooting method.
-I was able to use a google account manager app and downloaded/installed qucik_shortcut_2.4.0 this allows you access the launcher and partially use this device... I was able to set the username of the device but to no avail i am unable to use that combo to strip out the previous user's information. there's a method online to show you how to use the talkback settings to get to this point and i used my knowledge of frp bypassing samsung devices to get a little further. the developer options setting is still locked because it doesn't recognize me as the primary user. Its very frustrating. I'm able to sign into chrome with my credentials and access gmail through the browser but as far as getting my account onto this device its been days of trying and my girlfriend is just disgusted with my persistence. I don't know if or when an oreo update will be made available that this will help solve the problem, but i can't believe zte doesn't have the stock firmware anywhere online.
any of you fellow nerds out there that can help please do... I use an S3 for my daily use because well, they're so amazing to customize but the battery is crap because its so old. One thing i have found is with this zte you can at least play the "catch the cat" easter egg game, which is a complete waste of time but fun at the same time.
I'm not sure if this will help but i might as well. I'm also stuck with a zteK81 i'd REALLY love to root. I never had to go really deep into android stuff so tbh ... i've read alot ... but beside knowing i can't root it yet after a couple diff. method... im a bit confuse in all that. Up here i read ppls about looking for the Firmwire and someone else searching for the root. I have pull some pretty deep layer files in mine that may .. may not help you guys. I can't read that correctly. Here's 3 images and i have a little 7z with the actual files and 3-4 more if someone request it. Thanks.
hxxps://i.imgur.com/NVNpLpfh.png ---- Treeview
hxxps://imgur.com/8GLP2xJ ----- surfacelay.XML
hxxps://imgur.com/kcnDAY9 ----- surfacelay. XML
hxxps://imgur.com/oqIaDeR ----- lib. of a dna_file??
EDIT: Firmwire file --> hxxp://download.ztedevices.com/device/global/support/opensource/mobilephones/open_source_notice.html#id45
i found a download for this device's kernel source
hxxp://download.ztedevices.com/device/global/support/opensource/2/20170823_01/P890R81_USCCV1.0.0B08_kernel.tar.gz
im working on getting a stock system image of this tablet from ZTE. im not sure exactly whats needed to get an official twrp and rom going for this tablet but ill help in any way i can
Stock Rom
Online Gravy said:
im working on getting a stock system image of this tablet from ZTE. im not sure exactly whats needed to get an official twrp and rom going for this tablet but ill help in any way i can
Click to expand...
Click to collapse
I have a copy of the stock ROM. Who knows how to use it to develop a custom recovery for the K81?
Continued Interest
Is there any interest in rooting the ZTE K81?
Currently, I have a copy of the stock ROM and am trying to modify update.zip using Magisk to mod the boot.img file. I heed help with the signing of the modified update.zip package.
Any Suggestions?
There's no way of flashing an unsigned rom?
Sent from my Nexus 6P using Tapatalk
binholz said:
There's no way of flashing an unsigned rom?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Sadly, no.
Difficulties
To date I have found no way to even perform the OEM Unlock on this device and none of the available rooting schemas are of any use.
If I cannot determine how the sing the modified update.zip file, I am out of ideas.
I have a copy of the ZTE stock rom for the K81 and, if there is a more experienced person willing to take a shot at this, I will happily make the rom available to them.
ritzar12 said:
To date I have found no way to even perform the OEM Unlock on this device and none of the available rooting schemas are of any use.
If I cannot determine how the sing the modified update.zip file, I am out of ideas.
I have a copy of the ZTE stock rom for the K81 and, if there is a more experienced person willing to take a shot at this, I will happily make the rom available to them.
Click to expand...
Click to collapse
Hello, so it is common that ZTE's don't have any form of fastboot. So your only way is to flash via QPST with a firehose. But today is your lucky day. I was able to extract the k81's firehose from the Rogers ZTE firmware flashing tool. I have also downloaded the full QPST firmware fire and included the firehose with it. As well as a separate download in case someone already has it. I will also be ordering the device shortly. If you have newer firmware, or one designed for a variant other the rogers would be great if you can share it.
Rogers B05 Firmware
https://www.androidfilehost.com/?fid=1395089523397891291
Separate Firehose download
https://www.androidfilehost.com/?fid=1395089523397891292
Rogers ZTE FIrmware flashing tool (Not really useful just linking because its how I got the firehose)
https://www.androidfilehost.com/?fid=1395089523397891290
ZTE Kernel source mirror (We are codenamed Helen)
https://www.androidfilehost.com/?fid=1395089523397891289
Frustration intensifies...
deadman96385 said:
Hello, so it is common that ZTE's don't have any form of fastboot. So your only way is to flash via QPST with a firehose. But today is your lucky day. I was able to extract the k81's firehose from the Rogers ZTE firmware flashing tool. I have also downloaded the full QPST firmware fire and included the firehose with it. As well as a separate download in case someone already has it. I will also be ordering the device shortly. If you have newer firmware, or one designed for a variant other the rogers would be great if you can share it.
Rogers B05 Firmware
https://www.androidfilehost.com/?fid=1395089523397891291
Separate Firehose download
https://www.androidfilehost.com/?fid=1395089523397891292
Rogers ZTE FIrmware flashing tool (Not really useful just linking because its how I got the firehose)
https://www.androidfilehost.com/?fid=1395089523397891290
ZTE Kernel source mirror (We are codenamed Helen)
https://www.androidfilehost.com/?fid=1395089523397891289
Click to expand...
Click to collapse
Where do you get or how do you create the rawprogram0.xml file. Presumably the directory structure information is available somewhere in the kernel or the ROM but, methods to extract the information into an XML evade me.
Hello dev's !
So I am surfing alot of threads here lately and I finally have this chance to post my problem & hopefully get some help regarding my problem.
Device Info - MHA-L29C185... (Middle East Version - Dual SIM). Don't remember which stock rom I was on but it was oreo so maybe somewhere close to 374 or earlier version.
Problem :
Firstly, I rooted following one of the threads from here and it was successful. However, I messed up when I downloaded an app which modifies framework or something and it bricked me and pushed me out.
But luckily I had some help and I used Chimera Tool to flash the International Version which brought my phone back to life but a lot of features like WiFi, Fingerprint Scanner didn't work.
So I decided to re-flash my firmware ie; C185B374 (Middle East Version) hoping it would solve the problem. It did solve the Fingerprint and WiFi problem but gave new problems like Gallery App (System APP) not working and Bluetooth not working.
:crying:
Note : I tried downloading firmware files from Firmware Finder & and flashing all 3 files using twrp and it fails as there is some mess in the Partition which isn't resolving. :crying:
I tried flashing using firmware finder app in the phone. It downloads the firmware and everything but doesn't flash. :crying:
Now, when I try to rebrand also which seemed a possible solution, I get stuck on the step where oeminfo files has to be replaced from the twrp backups. The script just doesn't respond.
Well, I am still living with the phone but alot of features don't work.
Help Required is :
1. Need solution to get stock firmware working properly as I am currently running my regions version but features don't work.
2. Lock back bootloader if possible. ( ADB Method & Team MT Multi Tool have been tried with no success)
3. Possibly get everything back to orignal. That's all I want !
Can anybody provide a possible solution to this ?
Nobody ?
My thought:
Download the firmware images you want to install.
Follow the instructions for using HuRupdater (search, I don't have the link handy for it); basically: put hurupdater and your update zips in the same folder on microsd, flash hurupdater with TWRP.
For relocking, you should be able to use "fastboot oem relock", though the phone will show that status. If that's fine, go for it.
Hi, I received a Huawei MT7-TL10 from a Chinese friend but it comes without Google Services as I expected, so I decided to follow a guide to unlocking the bootloader in order to install custom ROMs.
Because Huawei stopped providing unlocking codes, the technique requires a root with a version lower than Android 6.0. After countless tries of downloading different transition packages and firmware, it didn't work. More specifically, it would show me an error at 5% saying that software install failed.
I am assuming that this comes from the fact that I am using a wrong build version to rollback, however, I could never find my specific version on the internet : MT7-TL10C00B577.
For reference, I used this thread to try and download different firmware for TL10: https://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
I tried both SDcard and internal memory. Creating a dload folder on root and pushing UPDATE.APP file inside.
Can someone point me in the right direction to downgrade from Marshmallow to Lolipop? Thank you
I am having the same problem. Did u figure out a way?