Related
What it says in the title. I got the phone from a guy, who I assume got it from aliexpress (because it had gifts with it) or imported some other way. The phone came in fully packed up, in all kinds of stickers and protective thingies and in it's box, with all the equipment packaged. Even has the protective thing (can't remember the eng word) over the screen still, so I'm pretty sure the phone is new and not used.
Anyway, if I'm not wrong the bootloader shows its already unlocked. Now my first goal is to root it, and I saw a lot of guides, and decided to follow these here but theres separate guides for officially unlocked and unofficially. My phone came like this so I don't know which is it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So questions:
1. How can I know whether its officially unlocked or unofficially?
2. Did I decide to follow the right guide or is there better ones?
3. My MTP and other drivers isn't working. I have Windows 7 Ultimate. EDIT: After installing a bunch of drivers I found, including the Mi PC Suite, universal adb drivers, and what not, MTP appears to be working, I can access the phone just fine and theres no exclamation mark over it like in "Devices and Printers". But I have some exclamation marks in device manager, as seen on screenshot. I'm not sure if "Unknown Device" is related. It could have been there before the phone, but ADB is new.
4. Are these exclamation marks an issue for following the guides to root and flash? The fastboot commands from screenshots work fine.
Phone Info:
- Android Version 5.1.1
- MIUI Version MIUI Global 7.3 | Stable
Sorry for the long post.
ChrisBunny said:
What it says in the title. I got the phone from a guy, who I assume got it from aliexpress (because it had gifts with it) or imported some other way. The phone came in fully packed up, in all kinds of stickers and protective thingies and in it's box, with all the equipment packaged. Even has the protective thing (can't remember the eng word) over the screen still, so I'm pretty sure the phone is new and not used.
Anyway, if I'm not wrong the bootloader shows its already unlocked. Now my first goal is to root it, and I saw a lot of guides, and decided to follow these here but theres separate guides for officially unlocked and unofficially. My phone came like this so I don't know which is it.
So questions:
1. How can I know whether its officially unlocked or unofficially?
2. Did I decide to follow the right guide or is there better ones?
3. My MTP and other drivers isn't working. I have Windows 7 Ultimate. EDIT: After installing a bunch of drivers I found, including the PCSuite, universal adb drivers, and what not, MTP appears to be working, I can access the phone just fine and theres no exclamation mark over it like in "Devices and Printers". But I have some exclamation marks in device manager, as seen on screenshot. I'm not sure if "Unknown Device" is related. It could have been there before the phone, but ADB is new.
4. Are these exclamation marks an issue for following the guides to root and flash? The fastboot commands from screenshots work fine.
Phone Info:
- Android Version 5.1.1
- MIUI Version MIUI Global 7.3 | Stable
Sorry for the long post.
Click to expand...
Click to collapse
1. If you buy it new the boot loader should be LOCKED , according to your screenshot it has been unlocked either by the seller or who knows but it's unlocked.
2. that guide is for installing twrp (custom recovery) not unlocking- but yeah to root you need to install twrp then supersu
https://download.chainfire.eu/969/SuperSU/
3. to get the correct drivers install MI PC Suite it has mostly everything you need for this device.
4. you shouldn't have any exclamation marks, try installing Mi Pc Suite.
otyg said:
1. If you buy it new the boot loader should be LOCKED , according to your screenshot it has been unlocked either by the seller or who knows but it's unlocked.
2. that guide is for installing twrp (custom recovery) not unlocking- but yeah to root you need to install twrp then supersu
https://download.chainfire.eu/969/SuperSU/
3. to get the correct drivers install MI PC Suite it has mostly everything you need for this device.
4. you shouldn't have any exclamation marks, try installing Mi Pc Suite.
Click to expand...
Click to collapse
1. Yes but the problem is I don't know whether its officially unlocked or unofficially unlocked, and its important because the guides for rooting and flashing twrp are different. That's what I'd like to know, but don't know how.
2. Yep. Like I said I'd like to root it, and later probably flash a CM rom, but I need TWRP first.
3. Already installed Mi PC Suite (forgot to write "Mi" in the Mi PC Suite, I'll correct that), and its working. Kind of. I can't make a backup, and sometimes it tells me theres an update when I plug the phone in (I'm reluctant to update atm), but when I press the "Update" it says the firmware is up to date. The rest of the functions seem to be working, like screencast or viewing the storage.
4. The exclamation mark is related to ADB, I don't know if Mi PC Suite should be installing that too, but anyway its there.
@ChrisBunny
There is no way to tell what method was used to unlock your phone. More than likely it is unofficial.
Your getting exclamation marks because some drivers haven't been installed properly, you may have to uninstall and reinstall to get the right versions installed.
What is the reported MIUI version in settings about phone? If your not getting something with four numbers (X.X.X.X). You could possibly have a vendor rom. Which may have spyware etc and you won't get updates.
corkiejp said:
@ChrisBunny
There is no way to tell what method was used to unlock your phone. More than likely it is unofficial.
Your getting exclamation marks because some drivers haven't been installed properly, you may have to uninstall and reinstall to get the right versions installed.
What is the reported MIUI version in settings about phone? If your not getting something with four numbers (X.X.X.X). You could possibly have a vendor rom. Which may have spyware etc and you won't get updates.
Click to expand...
Click to collapse
I'm assuming its unofficial too. If its from aliexpress I doubt they wait for official unlock for each phone they ship.
Also it came with Google Apps and MIUI apps. Didn't see chinese kanji on any apps or menu.
The MIUI version is "MIUI Global 7.3 | Stable" and under it says "7.3.6.0.0(LHOCNDD)".
Most aliexpress redmi note 3 pro pages say something like "we will open the original box to check the phone and install Multi-language ROM and Google play store,If you have special requests about the original box,please leave us a message" and also "And Many Multi-language ROM not support OTA Update" whatever OTA Update is. Over-the-air I assume. Which means the built in "Update" app shouldn't work. Which is fine, my old phone LG Optimus L7 II Prime didn't support OTA either. I didn't tap it yet in case it started updating right away, and I don't want to change anything without first backing up the entire rom, just in case, but don't know how to do that yet.
ChrisBunny said:
The MIUI version is "MIUI Global 7.3 | Stable" and under it says "7.3.6.0.0(LHOCNDD)".
Click to expand...
Click to collapse
That is definitely a Vendor Rom.
https://www.reddit.com/r/Xiaomi/wiki/roms/unofficial
Sort out your drivers first.
Then flash an official global developer rom, which might re-lock your bootloader and then unlock officially.
https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
I assume you don't have the mediatek version of RN3?.
corkiejp said:
That is definitely a Vendor Rom.
https://www.reddit.com/r/Xiaomi/wiki/roms/unofficial
Sort out your drivers first.
Then flash an official global developer rom, which might re-lock your bootloader and then unlock officially.
https://www.reddit.com/r/Xiaomi/wiki/roms/flashofficial
I assume you don't have the mediatek version of RN3?.
Click to expand...
Click to collapse
"also adware and bloatware, which are annoying and slow the phone down. This ROM is also buggy and unoptimised, so some things might not work (e.g. battery showing negative percentage or the rear LED not working at all), you might encounter issues and inconsistencies (e.g. freezing, lagging)" funny I'm not experiencing any of that. No bloatware except a couple Mi stuff and usual system apps you'd find on the phone like Calendar and explorer and what not. The only new thing I didn't see on other phones is "Security" app. It appears to be a very clean vendor rom then. Its super fast and smooth I'm impressed.
Yes the phone is Pro version, with Snapdragon. Are the pictures I posted not visible?
If its already unlocked unofficially, should I be relocking it and then applying for an unlock? Isn't it simpler to just follow the unofficial guide for flashing?
ChrisBunny said:
Yes the phone is Pro version, with Snapdragon. Are the pictures I posted not visible?
If its already unlocked unofficially, should I be relocking it and then applying for an unlock? Isn't it simpler to just follow the unofficial guide for flashing?
Click to expand...
Click to collapse
I didn't notice the third image posted.
DO NOT lock it while on a vendor rom.
Is it up to yourself, if you want it unlocked officially or not. You just need to be careful when flashing.
I still get rid of the vendor rom. If you want future updates and to avoid unknown/unseen future bugs.
corkiejp said:
I didn't notice the third image posted.
DO NOT lock it while on a vendor rom.
Is it up to yourself, if you want it unlocked officially or not. You just need to be careful when flashing.
I still get rid of the vendor rom. If you want future updates and to avoid unknown/unseen future bugs.
Click to expand...
Click to collapse
Yeah but is there any disadvantages to having an unofficial unlock over official? If not then I guess I'll just be careful following the unofficial guide for flashing. If there is disadvantages then I'll apply for official unlock and just wait.
I do want to get rid of this rom at some point and try CM if theres a fully functional one, but for now I'd just like TWRP and root on it.
ChrisBunny said:
Yeah but is there any disadvantages to having an unofficial unlock over official? If not then I guess I'll just be careful following the unofficial guide for flashing. If there is disadvantages then I'll apply for official unlock and just wait.
I do want to get rid of this rom at some point and try CM if theres a fully functional one, but for now I'd just like TWRP and root on it.
Click to expand...
Click to collapse
With unofficial unlock you have to be very precautious while flashing MIUI based rom else hard brick later is not the case for official unlock
This is the Honor View 10 's TOOL ALL IN ONE Discussion Thread more info and download go to the Original Thread
TOOL ALL IN ONE
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ADVANCED OPTIONS
FUNCTIONS
Install Drivers
Unlock Bootloader
Lock Bootloader (use carefully)
Flash TWRP Recovery
Flash Stock Recovery
Flash Stock Factory Image
Install APKs
Uninstall APKs
Take a Screenshot
Flash Partitions
Erase All Data (This function can decrypt the phone)
Reboot Phone
Update the Tool to latest version
Update Adb and Fastboot to latest version
Set Adb and Fastboot priviliges in system wide
Install Zip directly from PC (Required TWRP on phone)(These functions work perfectly on my pc but i have perfect adb drivers on my pc and perfect TWRP on my phone)
Flash Fastboot ROM
Delete downloaded files
ADB File Manager
DEVICE LIST
If you want you can send a request to add a new device here:
New Device Request Form
Device List
DOWNLOAD
Original Thread
DONATE LINK
If you want to support the project please consider making a donation, thanks.
I used this on 5T and it did work super.
But i am wondering if this is working for view10 or not... V10 requires a unique code to unlock BL, where do we provide that code here?
Also rooting v10 requires an img to be flashed. Is this tool working?
Anyone tested all these features on View10??
venreddy said:
I used this on 5T and it did work super.
But i am wondering if this is working for view10 or not... V10 requires a unique code to unlock BL, where do we provide that code here?
Also rooting v10 requires an img to be flashed. Is this tool working?
Anyone tested all these features on View10??
Click to expand...
Click to collapse
I have tested it on my honor view 10, to unlock your bootloader you still need of huawei unlock codes, always remember this tool automate process not bypass it (except it is not specified). This tool can't root the phone directly
EDIT: there is a little bug when you try to unlock the bootloader and your phone is in powered on and recognized in adb mode, i'm releasing a new version to fix it at this moment
EDIT 2: update released
mauronofrio said:
I have tested it on my honor view 10, to unlock your bootloader you still need of huawei unlock codes, always remember this tool automate process not bypass it (except it is not specified). This tool can't root the phone directly
EDIT: there is a little bug when you try to unlock the bootloader and your phone is in powered on and recognized in adb mode, i'm releasing a new version to fix it at this moment
EDIT 2: update released
Click to expand...
Click to collapse
Hi
Thanks for excellent tool. I have installed it and watched the videos you posted for OnePlus. You have used SuperSu in case of OnePlus. But for Honor View 10 I want to use Magisk. Can you please let me know the step?
vku369 said:
Hi
Thanks for excellent tool. I have installed it and watched the videos you posted for OnePlus. You have used SuperSu in case of OnePlus. But for Honor View 10 I want to use Magisk. Can you please let me know the step?
Click to expand...
Click to collapse
The videos are not made by me, i found it on youtube and i added the link to tool description. To root your device you need to see this guide: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
mauronofrio said:
The videos are not made by me, i found it on youtube and i added the link to tool description. To root your device you need to see this guide: https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280
Click to expand...
Click to collapse
Thanks for response. So far I unlocked the boot loader (really easy with your tool one click only thanks for it). For root
how to install Magisk Manager using your tool. Which button to use
1. Recovery flasher
2. Recovery Zip flasher
Bear with me if it sounds naïve this is first time I am trying to root
vku369 said:
Thanks for response. So far I unlocked the boot loader (really easy with your tool one click only thanks for it). For root
how to install Magisk Manager using your tool. Which button to use
1. Recovery flasher
2. Recovery Zip flasher
Bear with me if it sounds naïve this is first time I am trying to root
Click to expand...
Click to collapse
You can't root your phone with this tool, you need to follow that guide
You can installa magisk manager through "apk installer"
Just for info, Files are available for V10 now on firmware finder.
shashank1320 said:
Just for info, Files are available for V10 now on firmware finder.
Click to expand...
Click to collapse
link?
mauronofrio said:
link?
Click to expand...
Click to collapse
On app here it is. Can give you link if want
shashank1320 said:
On app here it is. Can give you link if want
Click to expand...
Click to collapse
The problem is i have the bkl-l04 version and for it there are not stock firmware available so i can't test it for now
just 2 questions - does it work for Honor 10 (not v10)? can I do recovery backup here?
PeterMarkoff said:
just 2 questions - does it work for Honor 10 (not v10)? can I do recovery backup here?
Click to expand...
Click to collapse
Honor 10 is not supported officially, you cant do a recovery backup with this tool
Hi guys.
I'm looking forward for Honor View 10 or Honor 10, and as I'm with Samsung S8, I'm trying to understand if these Honor devices can receive a recovery consol or be rooted in a way that can be restored to stock without being noticed from official assistance in case I'll need to go for an assistance in warranty.
Second, as I'm with Samsung since years, I've always seen to need a recovery consol and a root package to flash (as standard classic methods) for having complete access to phone, while here I read about unlocking and unlocking cuts from Honor (that I'm reading now it seams that they stopped to release easily the code needed), recovery, bootloader and other things that I'm completely lost in reading
I'm not speaking of the strict interest in flashing alternative roms, but at least to have the possibility to clean the phone deeply once in a while manually with SD-Maid, RootExplorer and other apps (maybe you know of more professional...) so for it not to get fat and more fat in time, with the possibility to clean corps and old unused system files without the need of a wipe, so to have a slim internal sd-card as much as I can (specially if I'll go for the Honor 10)
So please explain me a bit of what is this Honor world as I'm really willing to they one even tomorrow!!
Thanks to allall.
Sent from my SM-G950F using Tapatalk
Work this for mate 9...?
PIRATA! said:
Hi guys.
I'm looking forward for Honor View 10 or Honor 10, and as I'm with Samsung S8, I'm trying to understand if these Honor devices can receive a recovery consol or be rooted in a way that can be restored to stock without being noticed from official assistance in case I'll need to go for an assistance in warranty.
Second, as I'm with Samsung since years, I've always seen to need a recovery consol and a root package to flash (as standard classic methods) for having complete access to phone, while here I read about unlocking and unlocking cuts from Honor (that I'm reading now it seams that they stopped to release easily the code needed), recovery, bootloader and other things that I'm completely lost in reading
I'm not speaking of the strict interest in flashing alternative roms, but at least to have the possibility to clean the phone deeply once in a while manually with SD-Maid, RootExplorer and other apps (maybe you know of more professional...) so for it not to get fat and more fat in time, with the possibility to clean corps and old unused system files without the need of a wipe, so to have a slim internal sd-card as much as I can (specially if I'll go for the Honor 10)
So please explain me a bit of what is this Honor world as I'm really willing to they one even tomorrow!!
Thanks to allall.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
Honor and huawei devices can be unlocked, there are available twrps and you can do what you want. They can be restored to stock.
mataflakitas said:
Work this for mate 9...?
Click to expand...
Click to collapse
Mate 9 is not officially supported, if it has kirin 970 you can try to select honor view 10 and use the tool
Hey buddy, thanks for this amazing tool. I need to know, if there's need of the Bootloader Code for unlocking it on a Honor V10?
Also, if I need to add a phone that's in similar state as this phone (LG Stylus 2 Plus, currently not supported by LG for unlocking with their tool), can I send everything that you may need for making the tool compatible with it?
Thanks in advance!
i tried today on my honor view 10 to unlock bootloader, cant work
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Welcome to Team OpenKirin AOSP Project. Our goal is to provide
a overall stable AOSP experience across all Huawei/Honor phones
utilizing a Kirin SoC and EMUI 8.0 - either updated or shipped.
So far most of the bugs have been fixed and the ROMs are fully usable
as daily driver - and fully Kirin optimized.
This is the device support section for: Huawei Mate 8.
Any bugs found on this device(s) can be reported here, please include proper logs if you encounter any issues.
We support 4 ROMs in total as of now - LineageOS (Unofficial), CarbonROM (Official), ResurrectionRemix OS (Official from Beta 2+), OmniRom
You can find all needed guides/roms on our official website: https://openkirin.net
Requirements: basically full stock EMUI 8.0, with stock recovery/ramdisk
Support: Telegram - https://t.me/joinchat/EeDpi02ekfeJSBeaV4eqOw
XDA:DevDB Information
OpenKirin Treble ROMs, ROM for the Huawei Mate 8
Contributors
OldDroid, XePeleato, rcstar6696, surdu_petru
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: EMUI 8.0
Based On: LineageOS, CarbonROM, ResurrectionRemix OS, OmniRom
Version Information
Status: Beta
Created 2018-08-13
Last Updated 2018-08-13
Thanks @OldDroid for all the efforts.
I have used all 4 and all are working awesome, especially RR beta 2.
Awesome work....
What about the deep sleep issue on 950?
Will it be fixt in the future?
Hey guys, I have a spare mate 8 which is actually on build 829. Followed the instructions to the letter on Openkirin website, on RR beta 2right now,. But each time I reboot it, it says that decryption is unsuccessful and to reset the device. Is this normal?
malekowsky said:
Hey guys, I have a spare mate 8 which is actually on build 829. Followed the instructions to the letter on Openkirin website, on RR beta 2right now,. But each time I reboot it, it says that decryption is unsuccessful and to reset the device. Is this normal?
Click to expand...
Click to collapse
Yes, decryption problem remains with OK ROMs. You need to either decrypt with twrp or with fstab through adb shell. Once done, you won't get it again till you flash stock room again.
apat26 said:
Yes, decryption problem remains with OK ROMs. You need to either decrypt with twrp or with fstab through adb shell. Once done, you won't get it again till you flash stock room again.
Click to expand...
Click to collapse
Thank you buddy, basically same issue I ran in to when I tested AOSP a while ago except that ROMS are now more elaborated and functioning smoothly.
I try rr beta 2 and omnirom but i have only one sim (sim 2) sim 1 does not exist.Nice sim 2 does not work with all operators. For the idea?
For everyone else who has been struggling with the decryption issue, I finally figured out how to get OpenKirin's LineageOS image to boot without first encrypting. You lose FDE in the process (a tradeoff I'm willing to make to get a working phone).
1. Start with stock EMUI 8 and a stock recovery. You can get EMUI 8 using the HWOTA packages. If, anywhere in the process you make a mistake, you can restore EMUI by flashing the HuRUpdater zip.
1a. Boot into EMUI 8 to make sure it is intact. You may need to run a factory reset from the recovery (the complete, stock recovery which you can reach by holding Power + VolUp. Do not reset from eRecovery.) Once you see the language select screen you can be satisfied that it works.
2. Boot into fastboot (power off, hold VolDown and plug into USB).
3. Flash your OpenKirin ROM of choice:
Code:
fastboot flash system openkirin_ROMNAME.zip
4. Exit fastboot and immediately perform a factory reset from stock recovery, just like the OpenKirin instructions tell you to. Do not boot into the OS first. For me, the factory reset appears to fail. I ran it anyway just to be sure, and it does seem to make a difference even if it fails.
5. Once the reset is done, return to fastboot.
6. Flash this version of TWRP (originally for Mate 9):
Code:
fastboot flash recovery_ramdisk twrp_mate9_0.1.img
7. Boot into TWRP recovery: run
Code:
fastboot reboot
, unplug the phone, and hold down VolUp until the logo appears. (You have to be quick.)
8. Once in TWRP, load up an adb shell and remount /vendor with write perms:
Code:
mount -o remount,rw /dev/block/bootdevice/by-name/vendor /vendor
If your devices differ, use
Code:
df -h .
to see what the device name is.
9. Alter the following files, removing any boot flags that say "avb" or "forceencrypt":
Code:
/vendor/etc/fstab.f2fs.hi3650
/vendor/etc/fstab.ext4.hi3650
Make sure the comma-separated lists stay valid.
10. Save your files, and tell TWRP to reboot to system.
Georgian51 said:
I try rr beta 2 and omnirom but i have only one sim (sim 2) sim 1 does not exist.Nice sim 2 does not work with all operators. For the idea?
Click to expand...
Click to collapse
I also had that problem, a developer told me its because of the cdma modem, which is in the AL10 variant. Max connection i got was Edge.
So im back to stock an wait till they fix that problem.
Are these projects working for mate 8? I see that the rom has not been updated
Georgian51 said:
Are these projects working for mate 8? I see that the rom has not been updated
Click to expand...
Click to collapse
yup this is for Mate 8..there are few peoples already tested it but seems like there are still got few bugs like signal and etc. i'm waiting for a new build and will test it.
I'm another that has tested LOS, RR, and OR, and all have the issue with not getting any SIM card signal. Obviously I can't use, as a smartphone without the phone, isn't that smart.
Keenly hoping this gets resolved, as I certainly like the look of these ROMs.
lindsaytheflint said:
I'm another that has tested LOS, RR, and OR, and all have the issue with not getting any SIM card signal. Obviously I can't use, as a smartphone without the phone, isn't that smart.
Keenly hoping this gets resolved, as I certainly like the look of these ROMs.
Click to expand...
Click to collapse
What version did you test?
On AL10 I tried and I had the same problems. I went to
* DL00 and no problems
Georgian51 said:
What version did you test?
On AL10 I tried and I had the same problems. I went to
* DL00 and no problems
Click to expand...
Click to collapse
I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.
Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?
If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?
lindsaytheflint said:
I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.
Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?
If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?
Click to expand...
Click to collapse
I made a rebrend at DL00. Try the variant you say, maybe it works
lindsaytheflint said:
I've tried from NXT-AL10 b829 stock ROM, then loaded each of the OpenKirin system images with the same result.
Are you saying if I flash DL00 stock ROM (b829?) first, then the cellular signal should work?
If so, I think DL00 uses the same base except for a different "cust" partition. Perhaps I just need to flash the DL00 cust partition?
Click to expand...
Click to collapse
Did you flashed cust after upgraded to B596?if you noticed that you don't have signal or no service at that time?
ceriqdesign said:
Did you flashed cust after upgraded to B596?if you noticed that you don't have signal or no service at that time?
Click to expand...
Click to collapse
Yes, and signal was fine at B596. Signal is also fine on either stock b829 or KangVIP b828/829.
Firmware Finder's been offline, but looks like it's coming back online soon, so I'll try installing DL00 b829 stock ROM, then OpenKirin, to see if that helps.
(I tried flashing just DL00 b829 Cust.img yesterday, but it didn't seem to make a difference.)
For those that do have working signal on OpenKirin, what full base stock ROM did you come from? i.e. b829, DL00, AL10 etc, and which country region C00, C92, C17, etc?
Hi, looks like I am having the same signal issues as every one else on NXT-AL10. Have flashed back to stock EMUI 8 for now after hard bricking my device and using Dc-Phoenix to recover by shortinng out the testpoints.
Like every one else have been looking in to possible solutions. After booting in to open kirin roms and looking in to phone info in setting I noticed my IMEI was blank. At this point flashed back to stock after hard bricking and loaded in to HCU-client to repair fortunately this was not the case and IMEI was intact.
So digging around other Huawei boards I fond this maybe a possible solution to signal issue. Don't have time to try just now will let you know how it goes.
Honor 6X [GUIDE] Update to EMUI 8
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
found in instruction on first post
Bugs Fixing:
Unknown or invalid IMEI:Use any root file manager and go to cust/all/cn/prop/local.prop and edit local.prop change the line full network support: true to false
sounds like the problem we are all having with our devices.
If anyone tries this before me can you let us all know
Brokendroid994 said:
Hi, looks like I am having the same signal issues as every one else on NXT-AL10. Have flashed back to stock EMUI 8 for now after hard bricking my device and using Dc-Phoenix to recover by shortinng out the testpoints.
Like every one else have been looking in to possible solutions. After booting in to open kirin roms and looking in to phone info in setting I noticed my IMEI was blank. At this point flashed back to stock after hard bricking and loaded in to HCU-client to repair fortunately this was not the case and IMEI was intact.
So digging around other Huawei boards I fond this maybe a possible solution to signal issue. Don't have time to try just now will let you know how it goes.
Honor 6X [GUIDE] Update to EMUI 8
https://forum.xda-developers.com/honor-6x/how-to/guide-update-to-emui-8-t3807806
found in instruction on first post
Bugs Fixing:
Unknown or invalid IMEI:Use any root file manager and go to cust/all/cn/prop/local.prop and edit local.prop change the line full network support: true to false
sounds like the problem we are all having with our devices.
If anyone tries this before me can you let us all know
Click to expand...
Click to collapse
Tried this, and confirmed that my IMEI is also missing from OpenKirin, but after changing the local.prop file and rebooting, it was worse. Rather than the SIM being detected, but having no signal, the SIM was no longer being detected at all (slot showing as empty). Tried OpenKirin RR.
deja_wu said:
For everyone else who has been struggling with the decryption issue, I finally figured out how to get OpenKirin's LineageOS image to boot without first encrypting. You lose FDE in the process (a tradeoff I'm willing to make to get a working phone).
9. Alter the following files, removing any boot flags that say "avb" or "forceencrypt":
Code:
/vendor/etc/fstab.f2fs.hi3650
/vendor/etc/fstab.ext4.hi3650
10. Save your files, and tell TWRP to reboot to system.
Click to expand...
Click to collapse
Hello . I modded this files .
remove "avb" flags and change "forceencrypt" to "encryptable" . work fine (Resurrection Remix OS Beta 3
Released September 27, 2018 - 575.05MB , NXT-L29 (dual sim) changed to NXT-DL00)
View attachment hi3650.rar
Team Win Recovery Project 3.5.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
How to install:
Coming From Stock:
1. Download This TWRP Release and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
2. Under Developer Options, Tick OEM Unlock. It will tell you to factory reset. Do it.
3. After the phone shuts down, press Vol + & - button and at the same time, insert a usb cable to phone connected to a PC.
4. Check KG Status. If it is Prenormal, reboot the phone and follow this guide : (1) How to bypass KG State and/or RMM state prenormal | XDA Developers Forums (xda-developers.com)
5. Zip the TWRP recovery image to tar format and put in the AP slot of Samsung Odin.
6. Flash and after the phone screen turns off, press vol+ and power button.
7. If there is "Set Warrenty Bit : recovery" text on the top left, success!
8. Format data, flash zip downloaded from above.
9. To boot stock rom, install magisk.
From Other Recovery:
Reboot to recovery and flash this TWRP image as recovery and reboot recovery.
ChangeLog:
2021/3/2 Inital Release
Sources:
Kernel : Junak/android_kernel_custom_a6plte (github.com)
Device Tree: roynatech2544/TWRP_device_samsung_a6plte (github.com)
Recovery Source : TeamWin (github.com)
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
NOTE :
I was developing custom roms for A6+ despite of my computer specs. But my phone's LCD went out and I can't test anymore... And it takes 1 day to build in i5-5200U (2C/4T) CPU and 8GB RAM.. Now I can only build TWRP.
where is the twrp file ?
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
CRDhani said:
where is the twrp file ?
Click to expand...
Click to collapse
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
little_beppo said:
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
Click to expand...
Click to collapse
yes it works.
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Hello
Is this recovery for android 10?
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
abhisekh010 said:
Hello
Is this recovery for android 10?
Click to expand...
Click to collapse
Yes it is compiled in android 10 tree but recovery doesn't depend on android version..
Naddi2Niic3 said:
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
Click to expand...
Click to collapse
PM me
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
okwhateverok said:
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
Click to expand...
Click to collapse
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Thanks, ill hope there will be some users which ow the Galaxy A6 and not using this device as their main phone to be willing to test.
As a IT specialist myself i did try anything to at least help testing for this version of TWRP for our device. I did try to take several rom dumps with professional fabric software and hardware like software dongles but it was impossible to make a full rom dump.
With this said and knowing that a complete data wipe within TWRP is necessary to make the recovery find the internal storage makes it impossible for me to test no matter the fact that the biggest part of this recovery already exist and confirmed working.
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
nqnxev said:
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
Click to expand...
Click to collapse
I could help with the OEM unlock button. What a waist of time these lost 10 days and still no OEM unlock button while the solution is easy...
Follow guide with screenshots: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
And for those who could test on the A600 the recovery image is already uploaded within this thread thanks to Royna
I've tried that many times (no only that, but many similar guides) - and still nothing. From what I read, Samsung just fixed that "date & time" trick and I have to wait.
Ok that is strange, im on android 10 with One UI version 2.0 and got it working. If im allowed to post this link then the rom could be found here: https://www.sammobile.com/samsung/galaxy-a6/firmware/SM-A600FN/PHN/#SM-A600FN
You should do a clean flash without having the phone connected to the internet, not even once because it will do some synchronization. After the flash just follow the guide which could be found on the xda forum..
Thank you for a hint. Because of that I'm waiting so long already I'll wait till end of week and if things still will be the same then I'll try rom you've proposed. Thanks again.
Royna said:
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Click to expand...
Click to collapse
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Adam7336 said:
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Click to expand...
Click to collapse
Well because i don't own that device, it is highly experimental. I will try again.
Hi, does anyone know how I can flash the base, curt and preload of the p20 lite ane-lx3?
I got them with hisuite proxy but they give me an error when verifying update.
I need it because I can only go back to emui 8 from hi suite emui 9 does not appear, I had downloaded it to unlock the bootloader. I already unlocked them but I want to go back to the most updated emui or at least more than 9.1.0.142 since it still has the app drawer button.
I have seen that the multi tool 8 can be used to flash but I don't understand how to do it.
antonyx2016 said:
how I can flash the base, curt and preload of the p20 lite ane-lx3?
Click to expand...
Click to collapse
this can be done via modified TWRP, HuRupdater 0.4 or Multi-tool if you are running EMUI 9.1.
But these methods are risky when upgrading from 8.0 to 9.1 and are not recommended.
You can safely manually upgrade to 9.1 only by installing the service ROM using the dload method from the SD card.
What is your full build number? (settings > About phone).
Also check your vendor/country information via the Project Menu (*#*#2846579#*#*) and post the result.
Thank you for taking the time to respond, here I leave what you asked for. I would appreciate it if you could explain a little more how to do the process.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
-Alf- said:
I thought you were currently on 8.0, sorry. So you can try the methods in my previous post.
For HuRupdater method use TWRP 3.2.1 "Gaguga edition".
Rename all three archives:
base -> update.zip
preload -> update_data_public.zip
cust -> update_all_hw.zip
It works on the P20 Pro, it should also work on the P20 Lite. Be aware that these methods are risky, especially when it comes to choosing the right firmware for your phone!
Personally, I prefer an update via eRecovery & wi-fi, or installing a service ROM via dload.
You can download Service ROM for your phone
Here
The dload process will erase all your data and lock your BL again!
Click to expand...
Click to collapse
Good brief update: I tried all the stock roms of ane-l23 all with the same result in the case of emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046 so far everything is fine after reading several forums here I have found one to see the files with root everything is fine up to here I enter /cust/hw and find two folders (la or latam) and normal. and in special cust only after all the props are fine, that is, it is 5.0.0.20.
Then looking for more information to see where the 8.0.0.046 was, I found it in version.prop. Additionally, enter splash2/cust.log and throw a lot of errors in the following post or answer. I leave you the images to see if we can solve something because the problem that bothers me is not being in emui 8 or 9 but that it is not so stable all that works if when installing any firm again the huawei id does not work first playstore and update hsm core after that everything works either themes etc etc.
but it lags a lot in emui 8 and in emui 9 google maps doesn't work so I don't care if I stay in emui 8 or 9 honestly but I do want the equipment to work correctly. Thank you very much for your willingness and willingness to help.
antonyx2016 said:
emui 9 it stays at 9.1.0.046 and in emui 8 8.0.0.046
Click to expand...
Click to collapse
It means wrong or incomplete FW. As I said before,
-Alf- said:
service ROM via dload.
You can download Service ROM for your phone
Click to expand...
Click to collapse
-Alf- said:
Here
Click to expand...
Click to collapse
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
antonyx2016 said:
I tried all the stock roms of ane-l23
Click to expand...
Click to collapse
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
-Alf- said:
It means wrong or incomplete FW. As I said before,
Maybe you are doing something wrong...Follow instructions in ReleaseDoc folder.
you can only install the service ROM for your region (hw/la)!
But it is possible that with your current build number 9.1.0.046 you will not be able to flash via dload or eRecovery.
Click to expand...
Click to collapse
Yes I understand that, but what I wanted to say is that I already tried all the c605 firmware that there is, whether it is emui 8 and emui 9, they all install without error but apparently they do not install at all, I don't know if it is cust the oem partition or something like that but whatever the method, it always ends in .046 the only thing I know for sure is that it started to be like that a year ago when I used hisuite to go back and from there I could no longer update after what happened with hisuite I bought the code in dc to unlock the bootloader but I still can't remove the .046 in a few words hisuite screwed my phone xD because it was never rooted or unlocked until after what I told you
Okay, I don't know what the problem is, two last tips from me:
A) follow this method
https://ministryofsolutions.com/202...re-stock-rom-emui9-1-unlocked-bootloader.html
(reliable source)
B) rebrand to global version C432. But this requires downgrading to Oreo, and this is only possible through HiSuite (because there are no files needed for HuRupdater). It could help to get a fully working phone.
It could happen that before using hisuite you had a different region, not hw/la (claro/la etc.) hisuite couldn't recognize it and downgraded your phone to hw/la. Maybe you should try flashing oeminfo C605.
In fastboot mode run commands :
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the result.
If you decide to rebrand, I will give you instructions.
-Alf- said:
If you decide to rebrand, I will give you instructions.
Click to expand...
Click to collapse
If that helps me, ok, I tried option a) it was installed but it is incomplete with the pink background. If doing a rebrand will help me, ok
antonyx2016 said:
with the pink background
Click to expand...
Click to collapse
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
-Alf- said:
Now try to flash Service ROM.
Also try enter eRecovery and use option "Download latest version...".
As for rebrand, I can't give you any guarantee.
Click to expand...
Click to collapse
I think I achieved it in a while I'll tell you what happened but I'm hopeful something changed with the hisuite proxy
Ok, let me tell you, I managed to install firmware 9.1.0.355. I know it's not the latest and it didn't free me from system component 9.1.0.040 either, but at least now everything works correctly.
I'll tell you what I did in case it helps someone else:
1- I did the point a) that you sent me
2- I kept the pink wallpaper and I went to the proxy hisuite and downloaded the cust, preload and base .355
3- it marked an error when installing in the 1% of hisuite the proxy already warned me that it was going to fail and to cancel
4- cancel it and deactivate the 3 checks of point, cust and preload
5-I put in developer mode and look for the update in hisuite
6- This time I no longer throw any errors and it was completely flashed. I imagine that because of step a) the cust was updated and that is why it allowed the .355 to be installed
7-it was still half incomplete but I went into settings and updated and I got the same .355 version and it was installed correctly in quotes as I said I still have the .40 system but everything works now I imagine that if you keep messing around a bit that way it will I could install the .390 but I'm satisfied with the .355