Hi everyone!
As you can see (according to the title), I'm newbie for this.
Is there a way to get rid of/remove/hide this message?
{
"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 was Samsung user for ages, this is my first Huawei device... i hope there is someone who can help & explain 'how to' step by step.
2 .app files downgrade + fastboot oem relock (code) didn't help
Sorry, english is not my native language, thx in advance.
As far as I know, this is how it works! There's no way to remove this message. Cheers!
roottree said:
As far as I know, this is how it works! There's no way to remove this message. Cheers!
Click to expand...
Click to collapse
Yup, I thought so... I expected such an answer, but I still wanted to be 100% sure that could not be undone afterwards. Thank you!
The first time I successfully re-locked it, there was just "Phone: Relocked" message in fastboot mode, but warning still appeared.
I played a bit more with my P9, trying to enable an OEM unlock option at last (wich is ofc unavailable/grayed out).
Now I can not even activate the command for some reason, it says this:
Well, i can live with this if there is no solution. Everything else works fine.
>> trying to enable an OEM unlock option at last (wich is ofc unavailable/grayed out).
Try the following: by Vol+ and Pow boot to eRecovery and take Hard reset with wiping Internal data.
Also, from Settings, Advanced, Backup and reset, Factory reset with Internal memory.
Before, remove password/pin/fingerprint
You can go back to stock and fully relock your bootloader. But for that you have to "rollback" to Android 6 and after you did that you can update normally trough EMUI to the latest version. Your bootloader will be locked again and the message will disappear.
Relocking the bootloader with modifications like root installed is not possible as far as I know.
Rollback will do it for sure but it takes longer (and user did not report which exact stock ROM, cust, etc he has, all that must be taken care when rolling back)
Btw, rollback implicitely includes Factory reset and wiping Internal memory
IMO, Factory reset with wiping Internal memory, directly from Nougat (without rolling back to MM), might be enough to get OEM Onlock button back functional.
After that, relocking Bootloader must work.
Note: If user wants to have Bootloader unlocked, then must live with the Warning on boot.
Unlocked Bootloader (as long as no root nor TWRP) does not prevent OTA.
It is just a warning on boot, nothing more.
Also, locking or relocking Bootloader automatically forces Hard reset
zgfg said:
IMO, Factory reset with wiping Internal memory, directly from Nougat (without rolling back to MM), might be enough to get OEM Onlock button back functional.
Click to expand...
Click to collapse
Nope, i wiped it... i will try to rollback to C900B300 -> C432B210. Thx!
I know that OEM switch is active even with M6 & unlocked Bootloader combined, but I want it active with N7 even with locked BL since i am done with playing, stock rom works smooth, and fast enough.
I will try to relock it again from M6 + OEM unlocked and let you know guys!
EDIT:
C900B300 (android 7) -> fastboot oem relock (code) didn't help, now flashing M6
__________
There is another problem with android 6:
OEM Switch works just fine, but can't relock bootloader. Fastboot command is accepted, but wiping data always fails at 7%
Prolly there is something that I am doing wrong. Not sure if it is flashing or something else.
Can you try wiping with the recovery before? First try TWRP and if it doesn't work then stock recovery.
christopherpfister said:
Can you try wiping with the recovery before? First try TWRP and if it doesn't work then stock recovery.
Click to expand...
Click to collapse
Sorry, could you be more specific? I am still newbie for this.
If You mean:
1. flash twrp recovery => wipe all
2. flash stock from B210 and retry
One more question. I am not sure how to flash full stock firmware?
a: Unzip "update.zip" to sd/dload and VOL+/- & ON combination
b: Flash .APP via fastboot?
What are cust package and public data for? Never flashed 'em to my device.
Even if reset/wiping on relock failed, did you reboot to system and check if OEM Unlock button is now workable (no more grayed)?
danilo0230 said:
Sorry, could you be more specific? I am still newbie for this.
If You mean:
1. flash twrp recovery => wipe all
2. flash stock from B210 and retry
One more question. I am not sure how to flash full stock firmware?
a: Unzip "update.zip" to sd/dload and VOL+/- & ON combination
b: Flash .APP via fastboot?
What are cust package and public data for? Never flashed 'em to my device.
Click to expand...
Click to collapse
That's what I meant. No success?
You have to extract the contents of the zip file into the folder called "dload". The folder has to be on the root of your *external* sdcard.
You need to do that with all available zips, not just the main one!
Otherwise you will be missing some data including huawei applications like the keyboard.
zgfg said:
Even if reset/wiping on relock failed, did you reboot to system and check if OEM Unlock button is now workable (no more grayed)?
Click to expand...
Click to collapse
OEM Button works fine since i am on android 6MM, but to get it work on Nougat i suppose that i have to relock bootloader, atm it's mission impossible to me
christopherpfister said:
That's what I meant. No success?
You have to extract the contents of the zip file into the folder called "dload". The folder has to be on the root of your *external* sdcard.
You need to do that with all available zips, not just the main one!
Otherwise you will be missing some data including huawei applications like the keyboard.
Click to expand...
Click to collapse
Didn't try to mess up with recoveries yet, i guess that i flashed it wrong and that's what causing stock-recovery unable to wipe data.
I will retry to flash it as you said (all files merged in dload) before re-flashing recovery. Thx!
danilo0230 said:
Didn't try to mess up with recoveries yet, i guess that i flashed it wrong and that's what causing stock-recovery unable to wipe data.
I will retry to flash it as you said (all files merged in dload) before re-flashing recovery. Thx!
Click to expand...
Click to collapse
Don't merge the files. I believe they have the same names so that wouldn't work. Do one after another. You can switch the files from your computer while TWRP is running after each flash.
If you are on b182, you should be receiving OTA for Nougat, you don't need to DLOAD Nougat installation
If OEM Unlocking button is functional now, it will stay so when you update to Nougat
I never relocked, I have no problem with the unlocked Bootloader and its warning - but you may try to 'lock' and then 'unlock' again
And double-check iare you using proper code - in other threads people used to report that relocking works
christopherpfister said:
Don't merge the files. I believe they have the same names so that wouldn't work. Do one after another. You can switch the files from your computer while TWRP is running after each flash.
Click to expand...
Click to collapse
Yup, there are same named files. I know that only TWRP can flash .zip -s, but isn't stock firmware without TWRP? Is there any sequence, which file comes first?
zgfg said:
If you are on b182, you should be receiving OTA for Nougat, you don't need to DLOAD Nougat installation
If OEM Unlocking button is functional now, it will stay so when you update to Nougat
I never relocked, I have no problem with the unlocked Bootloader and its warning - but you may try to 'lock' and then 'unlock' again
And double-check iare you using proper code - in other threads people used to report that relocking works
Click to expand...
Click to collapse
Ok then, updating it via OTA with OEM enabled ---> trying to relock again. I Will let you know if i succeeded
__________
Well... i tried to reduce battery drain, that's the main reason why i unlocked it.
Afterwards I found out i am shooting in the dark, it's a common hardware problem for P9 devices.
Code is 100% correct 'coz i am using copy/paste from calculation, thx for support guys!
danilo0230 said:
Ok then, updating it via OTA with OEM enabled ---> trying to relock again. I Will let you know if i succeeded
__________
Well... i tried to reduce battery drain, that's the main reason why i unlocked it.
!
Click to expand...
Click to collapse
If you are concerned about battery,
update up to b397 and install then Magic Rainbow v4
https://forum.xda-developers.com/p9/development/rom-huawei-p9-magicrainbow-v4-t3759292
It's based on stock ROM but cleaned from bloatware, prerooted with Magisk, etc
Edit: Maybe OTA will stop yoy with b392 or b394.
Use HWOTA methods to update up to L19 c432 b397
https://forum.xda-developers.com/showpost.php?p=74913874&postcount=3
For that, of course, you need unlocked Bootloaderr and TWRP for Nougat
https://forum.xda-developers.com/p9/development/twrp-t3565703
zgfg said:
you may try to 'lock' and then 'unlock' again
Click to expand...
Click to collapse
Yes, but actually nope...
1. OTA automatically updated B210 => B386
2. fastboot relock worked as you said (wiped 100% this time)
3. OEM button still unavailable
4. Checked fastboot: Phone: unlocked; FRP: unlocked;
Damn! Never understood this
I don't understabd what do you really want, if Fastboot shows Phone unlocked, FRP unlocked then you are ready for TWRP, no matter how OEM Unlocking button shows (grayed out but isn't now in ON position?)
Or, you can do once again Rolling back and forth by OYA to Nougat, if you really want locked Bootloader.
zgfg said:
I don't understabd what do you really want
Click to expand...
Click to collapse
I want bootloader locked without any warning message at startup & working OEM button with Nougat if it's even possible in my case?
zgfg said:
if Fastboot shows Phone unlocked, FRP unlocked then you are ready for TWRP, no matter how OEM Unlocking button shows (grayed out but isn't now in ON position?)
Click to expand...
Click to collapse
Yup i know that I can and how to flash TWRP... but do i even need TWRP for that? If yes, how (step by step)?
zgfg said:
Or, you can do once again Rolling back and forth by OYA to Nougat, if you really want locked Bootloader.
Click to expand...
Click to collapse
I'm done with playing with customs, rooting etc, just wanna restore completely clean factory firmware (without warnins, greyed out buttons etc.)
Related
----------------------------------------------------
I'm kinda busy at my life and won't be able to answer your questions...you can still ask here and hope someone else will reply, or post at the other similar thread - MEGA-THREAD ALE-L21, ALE-L23, ALE-L02, Converting, Root, Unbrick, Updating, Xposed
----------------------------------------------------
Debranding is easy once you find infos how to do it...sadly there's nothing in english. I used a combination of Google Translate + some spanish/italian/polish sites and howto's for other Huawei models to convert my branded single sim ALE-L21 from C150B130 to dual sim C432B188.
Here's how i did it...proceed at your own risk. Don't forget to make a backup because you'll lose your data. Also, your warranty will be void.
Please look at the Q&A section at end of the post; feel free to ask me if something isn't answered, but be prepared for an answer like "flash it again" because that's my first Huawei phone and i own it just for a week...i'm more of a Google Nexus guy.
----------------------------------------------------
Part 1: Unlocking bootloader
Stuff you'll need:
- Model number inside "Settings > About phone"
- Serial number inside "Settings > About phone > Status"
- IMEI inside "Settings > About phone > Status" (write down the first one if you have two of them)
- Product ID by opening dialer and typing *#*#1357946#*#*
- "Updated Step by Step guide to Root P8 lite.pdf" file - http://forum.xda-developers.com/p8lite/general/step-step-guide-to-unlock-bootloader-t3150616
- Minimal ADB and Fastboot from unlocking bootloader pdf
First you'll need to get your bootloader unlocking code:
1. Go to http://emui.huawei.com/en/plugin.php?id=hwdownload&mod=list and click "Unlock Bootloader"
2. Register a Huawei ID account, repeat step 1, login and click "Unlock Bootloader" again; accept the terms and click Next
3. Enter your phone data and Press Submit; wait a little for the code to show up and save it somewhere safe in case you'll need it someday
Then you'll need to unlock your bootloader:
1. Open "Updated Step by Step guide to Root P8 lite.pdf" and do just step B
Like i said many times in replies/pm's - if you didn't do anything of this, your bootloader is still locked. Doesn't matter if it says unlocked.
-----------------------------------------
Want to go back from 6.0 to 5.01? Read Q&A first, there's a special procedure for that. If you do it directly, you'll lose your imei!
Part 2: Flashing the unbranded firmware
Stuff you'll need:
- Minimal ADB and Fastboot from last part
- C432B132 Europe dual sim firmware - http://carbontesla.com/2015/09/download-huawei-p8-lite-b132-firmware-dual-sim
- Huawei Update Extractor - http://forum.xda-developers.com/showthread.php?t=2433454
First we need to get img files out of Huawei's update.app:
1. Extract the firmware; you should have a folder with dload and CUSTOM
2. Open Huawei Update Extractor as administrator (otherwise you won't be able to extract directly into adb folder), browse (button with two dots) to dload folder from step 1 and open UPDATE.APP
3. Hold Ctrl and select BOOT.IMG, CUST.IMG, RECOVERY.IMG and SYSTEM.IMG; release Ctrl, right click on any marked file, click "Extract Selected" and find your ADB folder (should be "C:\Program Files (x86)\Minimal ADB and Fastboot" or "C:\Program Files\Minimal ADB and Fastboot")
Now the most fun and...ehm...most "dangerous" thing - flashing the files:
1. Do B 2, 3, 4, 5, 6 and 7 from unlocking bootloader pdf file (to boot your phone into fastboot mode and get a cmd window with the right starting location)
2. Type:
Code:
fastboot flash system system.img
press enter and wait until finish...it will take some time
Code:
fastboot flash recovery recovery.img
press enter and wait
Code:
fastboot flash boot boot.img
enter and wait again
Code:
fastboot flash cust cust.img
enter and wait
Code:
fastboot reboot
and enter to reboot your phone
You may think that's the end...let me tell you - it's not. Your phone booted into an ugly version of EMUI with funny icons and "Settings > About phone" Build number says BalongC**B*** instead of the flashed ALE-L21C432B132. Let's fix that.
Fixing balong "bug" - this will cause a factory reset...i hope you made a backup:
1. Remember CUSTOM folder from extracted firmware? Copy it on your phone's internal storage or sdcard
2. Rename CUSTOM to dload
3. Run the Updater app, tap Menu, select "Local update", tap UPDATE.APP and wait until it finishes it's work and reboots
4. Go to "Settings > About phone" and check if it says the right build number (should be ALE-L21C432B132); if it's not, repeat the img file flashing process
-----------------------------------------
DON'T OTA if you're rooted!
Part 3: Getting the latest firmware update (B200) via OTA and (optionally) manually updating to MM B560
a. Getting the latest firmware:
1. Open Updater app, tap Check for updates and install it
2. Repeat step 1 until it says No updates; now you should be on B200
b. Update to MM (6.0):
1. Download C432B560
2. Extract it and copy the dload folder on your phone's internal memory or sd card.
3. Run the Updater app, tap Menu, select "Local update", tap UPDATE.APP and wait until it finishes it's work and reboots.
4. Go to "Settings > About phone" and check if it says the right build number (ALE-L21C432B560)
----------------------------------------------------
Q&A:
Q: I have a ALE-L04 or something else. Can i still do what you wrote?
A: Don't even try because you'll brick your phone. ALE-L04 for example got a totally different chipset (Qualcomm Snapdragon 615) than ALE-L21 (HiSilicon Kirin 620).
Q: What's the difference between ALE-L21 and ALE-L02? Will there be any benefits or disadvantages after changing from L02 to L21?
A: L02 doesn't support some LTE frequencies and NFC; detailed specs: ALE-L02, ALE-L21. There will be no benefits or disadvantages after flashing a L21 rom; everything will be the same, except a different model and build number.
Q: Are there any other uses for this, except for debranding and converting to dual sim?
A: Yes, you can basically use it for everything from upgrading and downgrading firmwares, fixing your bricked phone (if you still can access Fastboot mode) and more.
Q: I don't want dual sim. Why should i flash it?
A: Because why not? You get a bonus functionality and you won't lose anything even if you never intend to use it - you can still use just one sim and a sdcard without any problems. Huawei also planned P8lite to be a dual sim phone, so it's possible you'll get updates faster than people with the single sim variant.
Q: I don't live in Europe. Why should i flash that firmware?
A: Well, you can always find an appropriate firmware on carbontesla website, but be prepared you won't be able to fix the balong bug. Only a few firmware packs include the vendor patch (CUSTOM folder).
Q: Huawei Update Extractor gives me errors why i try to extract img's. What should i do?
A: You didn't listen and didn't run it as administrator. One workaround would be extracting the img's somewhere else (for example new folder on desktop) and then copy/paste them into adb folder. Do as you wish.
Q: I get errors when i type "fastboot flash xxxxx xxxxx.img". What should i do?
A: First look if you typed it correctly, then check if you have the right files - BOOT.IMG, CUST.IMG, SYSTEM.IMG and RECOVERY.IMG (there are multiple RECOVERY files, make sure you get the one without any numbers in it's name) and repeat the command. The last resort would be running "fastboot reboot-bootloader" and retrying the command that gives you errors. By the way - if you can't run fastboot at all, then try opening cmd as administrator. If you used KingRoot, read the next question too.
Q: I unlocked the bootloader via KingRoot and i can't flash anything, help?
A: No, you didn't. Do everything from part 1 and you will be able to flash.
Q: I don't like 6.0, how can i go back to 5.01?
A: Read this. After doing everything it said, repeat part 2 and 3a of this guide to get back on B200.
Q: You broke my phone, i will beat/curse/sue you!
A: Ok, that's not a question. Anyways, not my fault, i said you proceed at your own risk.
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
pmp said:
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
Click to expand...
Click to collapse
Fixing balong "bug":
fixed or no ? please answer
Fixed.
Sent from my ALE-L21 using XDA Free mobile app
please Possible steps to resolve the problem balong "bug"
1. Extract the firmware; you should have a folder with dload and CUSTOM
I do not understand What CUSTOM
Extract the firmware produces a single file dload no custom
please help
pmp said:
Hi,
Thanks for this guide. I've followed it successfully but I need to make a small remark/alert: When correcting the Balong error, the local update caused a factory reset and my data was lost.
Nothing that a local restore can't solve but it might happen to others as well.
Paulo
Click to expand...
Click to collapse
Thanks for your input. I'll put it into first post...better to be safe than sorry.
darklove0 said:
1. Extract the firmware; you should have a folder with dload and CUSTOM
I do not understand What CUSTOM
Extract the firmware produces a single file dload no custom
please help
Click to expand...
Click to collapse
I already replied to your pm and will repeat it here because it will be maybe useful for others too.
Did you download C432B132? When you extract it, there should be something like this:
{
"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"
}
If you downloaded any other version, then it's like i said in Q&A...most of the firmwares don't have the vendor patch (CUSTOM folder).
dennyn said:
I already replied to your pm and will repeat it here because it will be maybe useful for others too.
Did you download C432B132? When you extract it, there should be something like this:
If you downloaded any other version, then it's like i said in Q&A...most of the firmwares don't have the vendor patch (CUSTOM folder).
Click to expand...
Click to collapse
thnx answer
i dawnload Huawei_P8_Lite_ALE-L21_V100R001C432B170_Europe but not folder (CUSTOM or vendor)
i have update for this 6.0
http://forum.xda-developers.com/p8li...allow-t3305550
Can I flash using fastboot a zip containing the dolby atmos app?
rareshutzu said:
Can I flash using fastboot a zip containing the dolby atmos app?
Click to expand...
Click to collapse
No, fastboot can only flash whole partitions. You'll need a custom recovery (twrp) to flash your thing.
dennyn said:
No, fastboot can only flash whole partitions. You'll need a custom recovery (twrp) to flash your thing.
Click to expand...
Click to collapse
I was afraid of that. Thank you for your answer.
Great threads (and for the p8 lite this thread's was the only one )with real instructions, good and easy to understand.
Thanks for the explanation and for the time you have past for sharing this with the p8 comunity .
after enabling dual sim support on the UK variant, I was expecting to see the phone returning two unique IMEI numbers when dialing *#06#. However, it only returned one IMEI. Is this correct? Is there a way to make sure two IMEIs are returned?
ken218 said:
after enabling dual sim support on the UK variant, I was expecting to see the phone returning two unique IMEI numbers when dialing *#06#. However, it only returned one IMEI. Is this correct? Is there a way to make sure two IMEIs are returned?
Click to expand...
Click to collapse
It (always) shows just one imei after converting from single to dualsim. There shouldn't be any problems while using both sims because the phone is "dualsim standby".
Hello, just for help, I have downgrade my two p8 lite from 6.0 to the latest version B190 5.0.1, and I have full wipe and format all (dalvik, cache, system, data, internal storage) with twrp before and like this no need to flash any fix for balong. just B052, B170 and B190 without any trouble.
I did everything like you said but...
My phone does not read the sim card...
How can i soluve this ???
bjkhami said:
I did everything like you said but...
My phone does not read the sim card...
How can i soluve this ???
Click to expand...
Click to collapse
Sim1 or sim2? Anyways, try repeating part 2 with B170 (link is inside Q&A section) and then OTA to B188 because sometimes you lose your baseband when flashing older firmwares and OTA usually fixes it.
FAILED (remote: Command not allowed)
When I try to run the command fastboot flash...... I always get the error "FAILED (remote: Command not allowed)" The phone has bootloader unlocked and appears listed when I enter "fastboot devices". Do you know why could I be receiving this error or what can I do to flash manually using fastboot? I had the phone rooted with KingRoot but I unrooted it back. Any help would be very appreciated.
pelukin said:
When I try to run the command fastboot flash...... I always get the error "FAILED (remote: Command not allowed)" The phone has bootloader unlocked and appears listed when I enter "fastboot devices". Do you know why could I be receiving this error or what can I do to flash manually using fastboot? I had the phone rooted with KingRoot but I unrooted it back. Any help would be very appreciated.
Click to expand...
Click to collapse
Did you run cmd as administrator? Try relocking and unlocking bootloader again, also try a factory reset.
That error usually appears if you try to flash any locked partition...it shouldnt happen with system, recovery, boot and cust. Let's hope you don't have any hardware problems.
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment recovery_twrp.zip
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
{
"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"
}
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
---reserved---
before you ask...
yes, of course, i have already tried to flash supersu, but unfortunately I had no luck so far. The script always aborts because it fails patching sepolicy of boot.img.
so if anyone knows a solution for this, feel free to help!
edit:
found another way to root, look here
Amazing! I never thought yb would have twrp. I've been looking for a way to install gapps since I bought yb. After my final I will definitely have a try.
Was it stable when you flashed some zip?
AndyVerne said:
Was it stable when you flashed some zip?
Click to expand...
Click to collapse
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
All right, I wil try to install supersu after take my final exam ,too .
I believe there will be a way to solve it .
(oh ,god , the root seems to have sloved , nice job!)
danjac said:
did backup 2 times and restored all partitions a several times which worked well.
only tried to install supersu, which in general went well although su couldn't patch boot.img (but has nothing to do with twrp I think)
Click to expand...
Click to collapse
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
Code:
fastboot flashing lock
if you are not sure, try to search xda for more information about relocking.
danjac said:
to lock the bootloader you must have stock recovery...hopefully you din't flash twrp.
I do not really know, whether locking the bootloader will work flawlessly due to the changes made by root
when you lock the bootloader it will once more wipe all data - so back it up before, normally root should stay (although I don't know for sure)
to lock the bootloader just use the following command in terminal:
if you are not sure, try to search xda for more information about relocking.
Click to expand...
Click to collapse
Oh, I gave it up... Thanks
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
danjac said:
managed to get twrp working on YB1-X90L (Yoga Book - Android - LTE)
it's my very first try to create sth. like that, so I have absolutely no idea if everything works as it should. (took the twrp from yoga tab 3 pro root thread and changed it to fit my device mainly using this guide and some minor changes on my own)
if you want to try, you do it on your own risk. if sth. breaks, please don't blame me!
I strongly suggest not to flash it, but just boot it via fastboot:
1. download recovery
2. make sure adb is working
3. put the recovery into your adb folder
4. unlock bootloader (attention: unlocking the bootloader does a factory reset. so back up your data before) see here how to unlock bootloader
5. boot into bootloader (either: 'press power + volume up' or use adb typing 'adb reboot bootloader' in terminal
6. open terminal and naviagte to your adb folder (with recovery.img in it) then type: 'fastboot boot recovery_twrp.img' (adapt file name in case you changed it)
7. tablet should reboot and boot twrp
this method does not flash twrp permanently. your stock recovery remains untouched!
!!!BEFORE YOU USE TWRP TO CHANGE ANYTHING, PLEASE MAKE A FULL BACKUP!!!
download: View attachment 3994659
as always... I mainly relied on other people's work. so all credits go to them, e.g. twrp team, joesnose (twrp yoga tab 3pro) and HostZero
screenshots:
View attachment 3994696
View attachment 3994697
View attachment 3994698
as i said, it is a beginner's job. so here is what i noticed so far:
twrp freezes after a certain time when not used - I guess it is when twrp goes to 'standby', normally you wake it up again by sliding a button but it doesn't work here.
Click to expand...
Click to collapse
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
AndyVerne said:
I have one question, after I unlock the bootloader, it occurs the "intel ....untrusted,will boot in 5 seconds ", I wanna know how to lock the bootloader again.
Click to expand...
Click to collapse
hajkan said:
Do not get me wrong but you say make a full back up with twrp before doing anything but based on your description twrp cant be installed without unlocking the bootloader which in return erases the device.
Is this catch22 or am I missing something here?
---------- Post added at 09:33 PM ---------- Previous post was at 09:30 PM ----------
So this process messed up your system? Not sure if I understand what is going on there.
Click to expand...
Click to collapse
to your first question:
1. well, here we are not talking about backing up your user data but your rom (stock rom so to speak). if anything goes wrong you can always go back to stock.
2. if you want to peform ota update you can't do it with modified system (ota will fail), so normally you must go back to stock, update, root again
to your second question:
it's just a warning that your bootloader is unlocked, nothing more. it shows with every boot and after 5secs just boots normally.
you can easily find out about the advantages and disadvantages of an unlocked bootloader e.g. here on xda.
I can't thank you enough for this. I live in China and was only able to buy the Chinese version of the Yoga Book, which doesn't come with Google Services installed. However, using this TWRP recovery I was able to flash Google Services (and get root) which makes my Yoga Book so much more useful! Thanks so much!
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
zamzenos said:
Have got as far as flashing TWRP, but find that any attempt to backup - to internal storage or sdcard - is cancelled. Have checked on googz but cannot find any specific info. Any help would be appreciated
Click to expand...
Click to collapse
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
danjac said:
which yoga book version?
did you flash it or booted it?
how about a log (--> advanced --> copy to sdcard)?
is 'mount read-only' in 'mount' deactivated?
Click to expand...
Click to collapse
Left it overnight and tried again today. It's OK this time. I fiddled with settings, mainly to deselect the read-only system option. Each stage of this process has been pretty frustrating (I'm used to hacking sammy devices - this is first and last time with a lenny). Stuck now trying to get root - it will probably take until tomorrow! btw, ver is YB1 X90F (Europe/UK).
But thanks for taking the trouble to reply. And thanks for giving us the opportunity to hack the YB.
Worked on the wifi version too.
You may not be a developer but you are a pretty smart guy to be able to figure this out on your own, my hat is off to you. I rooted my wifi version of Yoga Book using your instruction and the only notable issue I ran into in the process was that i had to install new Android usb drivers in Windows to get the reboot-bootloader command to work, other than that little hiccup it worked like a charm. One other issue I ran into that was of my own making was that Titanium backup encouraged me to upgrade super user which led to a soft brick, thankfully I'd backed my book up and was able to restore it.
Thanks for taking the time to share this with us because rooting made this device a much better experience.
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
kakit78 said:
hi all, Im reslly happy to see the yb can really root. but all i want is to have the google app work on my yb china version.
am not a techy, hence most of the insturction mention here is very strange to me.
if anyone can help to write down the step by step on how to flash twrp and install google app to yb will be great thanks..
please...
Click to expand...
Click to collapse
If you just want to install gapps, there is no need to root.
1. download gapps from opengapps.org. select x86_64 6.0 version. select nano or micro version if only want google play to be worked.
2. put the gapps zip file into your root of your YB.
3. just follow the instructions of this post to boot into TWRP
4. In TWRP, select install zip file from SD, then select the gapps to install
5. after finish, reboot to the system.
6. Done!
---------- Post added at 08:48 AM ---------- Previous post was at 08:44 AM ----------
The problem is that I fail to OTA updated after booting into TWRP and install gapps. Anyone can helps?
@danjac Hi, did you keep the boot to bios option in the reboot menu?
Hello everyone!
This is my first thread here at XDA and I hope you can help me fix a few things with my phone. Three days ago I purchased the Huawei P8 lite 2017 [PRA-LX1] PRA-LX1C02B142 and without knowing about all the problems other users are having with rooting this device, I did exactly that. I rooted my device and installed TWRP. As you can guess, I facing a few problems and a little bit of lagging. I want to fully restore my device. To restore the EMUI 5, unroot my device and, of course, lock the bootloader again.
Is that possible? To install the officical ROM and fully restore my device as it was when I brought it? If not, what's the best I can do? My device is fully working but I can't change themes, sometimes lags etc.
I'm a newbie, so any help will be much appreciated!
Get your latest firmware
Use the Huawei update extractor to extract the update.app
Extract
system.img
Boot.img
Recovery.img
And use fastboot to flash them...
and then do a factory reset from the stock recovery menu (optional but recommended)
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
Get your latest firmware
Use the Huawei update extractor to extract the update.app
Extract
system.img
Boot.img
Recovery.img
And use fastboot to flash them...
and then do a factory reset from the stock recovery menu (optional but recommended)
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
I've download the Huawei Update Extractor and installed it on my PC. I extracted the update.app I found on a website and now I don't know in what order to extract the system.img, boot.img and recovery.img. Do I flash them one by one in an exact order?
meymigrou said:
I've download the Huawei Update Extractor and installed it on my PC. I extracted the update.app I found on a website and now I don't know in what order to extract the system.img, boot.img and recovery.img. Do I flash them one by one in an exact order?
Click to expand...
Click to collapse
Just flah them i don't think that the order changes anything
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
Just flah them i don't think that the order changes anything
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
I've tried to flash the files into my device but they were corrupted. I am trying to find where to download the stock rom and I can't find it anywhere. Any ideas?
meymigrou said:
I've tried to flash the files into my device but they were corrupted. I am trying to find where to download the stock rom and I can't find it anywhere. Any ideas?
Click to expand...
Click to collapse
Here you can download full stock ROM that you need.. Download First one, FullOTA-MF, Extract and flash Boot.img, Recovery.img and System.img via fastboot. You can leave bootloader unlocked.
MobileTechArena said:
Here you can download full stock ROM that you need.. Download First one, FullOTA-MF, Extract and flash Boot.img, Recovery.img and System.img via fastboot. You can leave bootloader unlocked.
Click to expand...
Click to collapse
Thank you for your reply! I downloaded the FullOTA-MF file and extracted it. I tried to flash the files onto my device but I am getting this error: FAILED (remote: Command not allowed).
I've searched and they say that I have to enable the USB Debugging mode and the OEM Unlocking from the settings of my device. I have enabled the USB Debugging but I can't enable the OEM Unblocking as it stays grey and doesn't give me the option to enable it. What should I do?
{
"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"
}
meymigrou said:
Thank you for your reply! I downloaded the FullOTA-MF file and extracted it. I tried to flash the files onto my device but I am getting this error: FAILED (remote: Command not allowed).
I've searched and they say that I have to enable the USB Debugging mode and the OEM Unlocking from the settings of my device. I have enabled the USB Debugging but I can't enable the OEM Unblocking as it stays grey and doesn't give me the option to enable it. What should I do?
Click to expand...
Click to collapse
Try to repeat unlocking bootloader in fastboot first - "fastboot oem unlock <Unlock Password>". Then power on device and enable that.
EDIT: But if your phone is in working condition maybe there's easier/safer way to remove root. As i had the same situation any my phone bricked after i flashed boot, recovery and system. It took me 3 days to restore it from bricking.
MobileTechArena said:
Try to repeat unlocking bootloader in fastboot first - "fastboot oem unlock <Unlock Password>". Then power on device and enable that.
EDIT: But if your phone is in working condition maybe there's easier/safer way to remove root. As i had the same situation any my phone bricked after i flashed boot, recovery and system. It took me 3 days to restore it from bricking.
Click to expand...
Click to collapse
My phone is in working condition but it's not just about the root. It's the whole firmware thing. After I rooted my device a lot changed. I just want to easily fully restore it back to normal.
MobileTechArena said:
Try to repeat unlocking bootloader in fastboot first - "fastboot oem unlock <Unlock Password>". Then power on device and enable that.
EDIT: But if your phone is in working condition maybe there's easier/safer way to remove root. As i had the same situation any my phone bricked after i flashed boot, recovery and system. It took me 3 days to restore it from bricking.
Click to expand...
Click to collapse
I've tried the "fastboot oem unlock" but it didn't work. It gives me the same error. Any other ideas?
meymigrou said:
I've tried the "fastboot oem unlock" but it didn't work. It gives me the same error. Any other ideas?
Click to expand...
Click to collapse
I had the same problem, That's FRP lock, when you go to bootloader what you see under FRP.
I used DC-Phoenix tool to flash those images (it's a paid tool, 15€ for 72h of work). It lets you flash images when FRP is locked.
.
MobileTechArena said:
I had the same problem, That's FRP lock, when you go to bootloader what you see under FRP.
I used DC-Phoenix tool to flash those images (it's a paid tool, 15€ for 72h of work). It lets you flash images when FRP is locked.
.
Click to expand...
Click to collapse
Yes! It says that the FRP is locked. Unfortunately I can't afford to purchase the tool as I am totally broke thanks to my brother's college expenses, is there any other tool that could do the same? Or any other way?
meymigrou said:
Yes! It says that the FRP is locked. Unfortunately I can't afford to purchase the tool as I am totally broke thanks to my brother's college expenses, is there any other tool that could do the same? Or any other way?
Click to expand...
Click to collapse
You can try REDLOTUS tool from P10 forum. Just follow instructions on Github, but i didn't test if it works in fastboot or just when phone is already working.
Hi guys, does anyone know if I do the erecovery this will unroot my phone as well?
thanks a lot
I had the same problem...all you have to do is relocking your bootloader...but first of all you need to have the stock recovery(very important).
If you don't have the stock recovery you can't relock your bootloader
If you have root permission you can flash stock recovery using dd command or flashify
So...this is how it goes...boot to the stock recovery
Do a factory reset
Go to bootloader and use fastboot for this command
Fastboot oem relock xxxxxxxxxxxxxxxx
X's are your bootloader unlock code
Then the phone will ask you to do a factory reset
Agree and boot...
Go to deveoper options and enable OEM unlocking
Re unlock your device.
Sent from my PRA-LA1 using Tapatalk
hamzio7 said:
I had the same problem...all you have to do is relocking your bootloader...but first of all you need to have the stock recovery(very important).
If you don't have the stock recovery you can't relock your bootloader
If you have root permission you can flash stock recovery using dd command or flashify
So...this is how it goes...boot to the stock recovery
Do a factory reset
Go to bootloader and use fastboot for this command
Fastboot oem relock xxxxxxxxxxxxxxxx
X's are your bootloader unlock code
Then the phone will ask you to do a factory reset
Agree and boot...
Go to deveoper options and enable OEM unlocking
Re unlock your device.
Sent from my PRA-LA1 using Tapatalk
Click to expand...
Click to collapse
What is your build my friend? I have PRA-LA1C185B212. can you send me link where i can download boot.img recovery.img and system.img with this build. Or do you have backup of your system. Can you please send it to me. I have a problem with my gapps and i want to revert it back to stock rom with that build rom. Thanks in advance.
Hi All, I need a big help. :crying:
I've a bricked my Honor 9 Lite (LLD-L21)
Yesterday i did a restore rom from twrp backup and successfully to restore it. After it i did a format factory in TWRP, done and reboot to reboot system, I thought this would be fine, but what happened was my phone just stuck at Huawei eRecovery with EMUI logo and three option (Download latest and recovery, Reboot and Shutdown).
And now i can't access to TWRP mode. just stock recovery mode with option "Reboot system, Wipe data/factory, Wipe cache) but while i try to Wipe data/factory i got it error after 40% and stopped self.
In my situation, i tried to :
**Using Huawei eRecovery : i only get a message "Getting Package info failed",
**Trying to update with dload folder (UPDATE.APP) vol + - and power button : Stuck at 5% and then "Software install failed",
**Flashing .IMG file trought fastboot mode "FAILED (remote: Command not allowed)"
**Unlock bootloader again that show: "Necessary to unlock FRP! Navigate to Developer option, and enable OEM unlock"
This my Honor 9 Lite in current state :
Firmware: LLD-L21 8.0.0.122(C636)
Device name: LLD-L21
Oeminfo: hw/spcseas
Bootloader state: RELOCKED (unlocked)
FRP state: LOCKED
*Stuck at Huawei eRecovery
*Bootloader mode with Locked state
*Just have Stock Recovery (Reboot system, Wipe data/factory, Wipe cache) not TWRP.
Is there anywhere an Option to repair it?
Thanks in advance. :highfive:
{
"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"
}
SeenThings said:
Hi All, I need a big help. :crying:
I've a bricked my Honor 9 Lite (LLD-L21)
Yesterday i did a restore rom from twrp backup and successfully to restore it. After it i did a format factory in TWRP, done and reboot to reboot system, I thought this would be fine, but what happened was my phone just stuck at Huawei eRecovery with EMUI logo and three option (Download latest and recovery, Reboot and Shutdown).
And now i can't access to TWRP mode. just stock recovery mode with option "Reboot system, Wipe data/factory, Wipe cache) but while i try to Wipe data/factory i got it error after 40% and stopped self.
In my situation, i tried to :
**Using Huawei eRecovery : i only get a message "Getting Package info failed",
**Trying to update with dload folder (UPDATE.APP) vol + - and power button : Stuck at 5% and then "Software install failed",
**Flashing .IMG file trought fastboot mode "FAILED (remote: Command not allowed)"
**Unlock bootloader again that show: "Necessary to unlock FRP! Navigate to Developer option, and enable OEM unlock"
This my Honor 9 Lite in current state :
Firmware: LLD-L21 8.0.0.122(C636)
Device name: LLD-L21
Oeminfo: hw/spcseas
Bootloader state: RELOCKED (unlocked)
FRP state: LOCKED
*Stuck at Huawei eRecovery
*Bootloader mode with Locked state
*Just have Stock Recovery (Reboot system, Wipe data/factory, Wipe cache) not TWRP.
Is there anywhere an Option to repair it?
Thanks in advance. :highfive:
Click to expand...
Click to collapse
Did your backup had the stock recovery in it?
If it didn't then you can access the TWRP by selecting factory reset from the erecovery, it'll just boot to TWRP.
But if you did restore the stock recovery, well you might be in a tight corner.
Whats causing the bootloop is the factory reset you did in TWRP. EMUI have files in the data partition, who knows what, that are necessary to use the phone. But TWRP factory resets like other phones so that means the necessary files are gone now. I've personally experienced this but luckily had an unlocked bootloader.
Try pressing factory reset from e recovery. If you didn't restore stock recovery, you'll boot to TWRP.
And why did you relock the bootloader without checking if the phone boots or not? And don't ever factory reset from TWRP.
Fredin_ said:
Did your backup had the stock recovery in it?
If it didn't then you can access the TWRP by selecting factory reset from the erecovery, it'll just boot to TWRP.
But if you did restore the stock recovery, well you might be in a tight corner.
Whats causing the bootloop is the factory reset you did in TWRP. EMUI have files in the data partition, who knows what, that are necessary to use the phone. But TWRP factory resets like other phones so that means the necessary files are gone now. I've personally experienced this but luckily had an unlocked bootloader.
Try pressing factory reset from e recovery. If you didn't restore stock recovery, you'll boot to TWRP.
And why did you relock the bootloader without checking if the phone boots or not? And don't ever factory reset from TWRP.
Click to expand...
Click to collapse
Thank you sir, I just want to original again.
after the first restore the phone runs normally, but I don't turn on the OEM unlock again, then I reboot into the bootloader (still unlock) I tried to relock the bootloader. after rebooting instead bootloop and can't go to TWRP, TWRP is gone. return to stock recovery.
Are there EDL methods like xia*mi ? there can force flash with this method without unlocking BL.
SeenThings said:
Thank you sir, I just want to original again.
after the first restore the phone runs normally, but I don't turn on the OEM unlock again, then I reboot into the bootloader (still unlock) I tried to relock the bootloader. after rebooting instead bootloop and can't go to TWRP, TWRP is gone. return to stock recovery.
Are there EDL methods like xia*mi ? there can force flash with this method without unlocking BL.
Click to expand...
Click to collapse
Im not sure but try this:https://forum.xda-developers.com/9-lite/how-to/guide-unlock-frp-phone-bootlooping-t3808650
If it works you'll probably have an unlocked device and you can flash stock rom with HuRupdater later on
Fredin_ said:
Im not sure but try this:https://forum.xda-developers.com/9-lite/how-to/guide-unlock-frp-phone-bootlooping-t3808650
If it works you'll probably have an unlocked device and you can flash stock rom with HuRupdater later on
Click to expand...
Click to collapse
Yes, I have read that, but thank you for your attention. :good:
with DC-Phoenix it's amazing, but it's not free. ha ha
well, I have to sacrifice my money to buy DC-Phoenix.
whether DC-Phoenix could serve bitcoin payments?
SeenThings said:
Thank you sir, I just want to original again.
after the first restore the phone runs normally, but I don't turn on the OEM unlock again, then I reboot into the bootloader (still unlock) I tried to relock the bootloader. after rebooting instead bootloop and can't go to TWRP, TWRP is gone. return to stock recovery.
Are there EDL methods like xia*mi ? there can force flash with this method without unlocking BL.
Click to expand...
Click to collapse
None that I know of ?. Are you still bricked?
Fredin_ said:
None that I know of . Are you still bricked?
Click to expand...
Click to collapse
Yes bro. waiting $.
When done, i'll update this thread to solved.
SeenThings said:
Yes bro. waiting $.
When done, i'll update this thread to solved.
Click to expand...
Click to collapse
Be aware that depending on the ROM you have flashed to your H9L, DC Unlocker/ Phoenix and HCU may not work.
None of them support the later firmwares and fail trying to read the necessary data from device.
You may be OK with 122 as, AFAIK it is pre July/August 2018.
Also are you using proper DLoad firmware ?
Normal OTAs will not work with DLoad, instead search here for correct ROm and try it :-
https://androidhost.ru/search.html
Sparkrite said:
Be aware that depending on the ROM you have flashed to your H9L, DC Unlocker/ Phoenix and HCU may not work.
None of them support the later firmwares and fail trying to read the necessary data from device.
You may be OK with 122 as, AFAIK it is pre July/August 2018.
Also are you using proper DLoad firmware ?
Normal OTAs will not work with DLoad, instead search here for correct ROm and try it :-
https://androidhost.ru/search.html
Click to expand...
Click to collapse
Ok thanks sir, but i search the "LLd-L21 8.0.0.122 (C636)" is'nt found. just one a site to having this ROM LLd-L21 8.0.0.122 (C636) but there isn't free again. must paying it before downloading
I have an original .img for full ROM my H9L after unboxing and rooted, but don't know what to do now. haha
SeenThings said:
Ok thanks sir, but i search the "LLd-L21 8.0.0.122 (C636)" is'nt found. just one a site to having this ROM LLd-L21 8.0.0.122 (C636) but there isn't free again. must paying it before downloading
I have an original .img for full ROM my H9L after unboxing and rooted, but don't know what to do now. haha
Click to expand...
Click to collapse
http://huawei-firmware.com/download...ndL21AC636B125 800125LLDL21C636B125 800125&c=
https://blogthetech.com/flash-file-...sP0VLlWyn1gFtkC0HdEeXhGWK3tjj2tCHsizDRFe/hqU=
http://update.hicloud.com:8180/TDS/d...ull/update.zip
All for the LLd-L21 C636 but are Full OTAs (not service ROMs), but maybe worth a try after extracting UPDATE.APP.
If all fails then I would try a service ROM from androidhost.ru
Sparkrite said:
http://huawei-firmware.com/download...ndL21AC636B125 800125LLDL21C636B125 800125&c=
https://blogthetech.com/flash-file-...sP0VLlWyn1gFtkC0HdEeXhGWK3tjj2tCHsizDRFe/hqU=
http://update.hicloud.com:8180/TDS/d...ull/update.zip
All for the LLd-L21 C636 but are Full OTAs (not service ROMs), but maybe worth a try after extracting UPDATE.APP.
If all fails then I would try a service ROM from androidhost.ru
Click to expand...
Click to collapse
i've tried all LLD-L21 version 124-132 rom but FAIL. sir. also i use firmware finder hw multi tool 8. :crying:
this my prop backup :
ro.build.display.id=LLD-L21 8.0.0.122(C636)
ro.build.version.incremental=122(C636)
ro.build.description=LLD-L21-user 8.0.0 HONORLLD-L21 122(C636) release-keys
ro.build.fingerprint=HONOR/LLD-L21/HWLLD-H:8.0.0/HONORLLD-L21/122(C636):user/release-keys
ro.vendor.build.fingerprint=HONOR/LLD-L21/HWLLD-H:8.0.0/HONORLLD-L21/122(C636):user/release-keys
i search for 122 not found except easy-firmware*com but there its not free :crying:
@SeenThings
Ok, as a start you can always email Huawei support and ask for your FRP key.
At least then we will be able to flash some custom recovery to rescue the phone.
Done. This a good night for me. "Desaster Solved"
My Honor 9 Lite has been living normally again, also the BL & FRP has been Unlocked again.
Thank You so much for big help to @hackintosh5 @OldDroid & ぁ て .
:highfive::good::good::good:
Follow this method for unlock your bootloader ;
https://forum.xda-developers.com/9-lite/how-to/unlock-bootloader-code-t3859685,
SeenThings said:
Done. This a good night for me. "Desaster Solved"
My Honor 9 Lite has been living normally again, also the BL & FRP has been Unlocked again.
Thank You so much for big help to @hackintosh5 @OldDroid & ぁ て .
:highfive::good::good::good:
Follow this method for unlock your bootloader ;
https://forum.xda-developers.com/9-lite/how-to/unlock-bootloader-code-t3859685,
Click to expand...
Click to collapse
@SeenThings
Ah great!
I understood you already had your BL code as you had re-locked it.
Any chance you might share what you had to do, please?
Sparkrite said:
@SeenThings
Ah great!
I understood you already had your BL code as you had re-locked it.
Any chance you might share what you had to do, please?
Click to expand...
Click to collapse
Yes sir, i've the bl code from june ago.
hmm, im just following the instruction from @hackintosh5, he and team help me like on thread.
SeenThings said:
Yes sir, i've the bl code from june ago.
hmm, im just following the instruction from @hackintosh5, he and team help me like on thread.
Click to expand...
Click to collapse
I'm sorry, I don't understand.
You already had your BL code and the thread linked to is how to unlock BL without code.
So how did that help?
What I'm trying to ascertain, is what firmware did you flash to get your phone running again and how ?
TIA
Sparkrite said:
I'm sorry, I don't understand.
You already had your BL code and the thread linked to is how to unlock BL without code.
So how did that help?
What I'm trying to ascertain, is what firmware did you flash to get your phone running again and how ?
TIA
Click to expand...
Click to collapse
well, that time i can't flash anything firmware version without twrp coz im not have twrp and in fastboot can't to do anything .
so that method is flashing a slock file for unlock the BL for with a moment, a slock file can be obtained from the phone at fastboot mode. Then flash twrp and here i can flash any firmw with different version also diffrent country code and phone will work normally again but if flash diferen firm country, maybe phone got loss the imei id.
You can ask @hackintosh5 for detailed tutorial.
SeenThings said:
well, that time i can't flash anything firmware version without twrp coz im not have twrp and in fastboot can't to do anything .
so that method is flashing a slock file for unlock the BL for with a moment, a slock file can be obtained from the phone at fastboot mode. Then flash twrp and here i can flash any firmw with different version also diffrent country code and phone will work normally again but if flash diferen firm country, maybe phone got loss the imei id.
You can ask @hackintosh5 for detailed tutorial.
Click to expand...
Click to collapse
I know about @hackintosh5 exploit using slock to unlock the BL.
But what I am having trouble trying to understand is, why go through all that when you already have the code to unlock your BL ??
Sparkrite said:
I know about @hackintosh5 exploit using slock to unlock the BL.
But what I am having trouble trying to understand is, why go through all that when you already have the code to unlock your BL ??
Click to expand...
Click to collapse
I think he lost the code. Either that or a security patch changed it (yes that does happen!)
Edit: just reread the OP, his FRP is locked! That means he can't use the code.
hackintosh5 said:
I think he lost the code. Either that or a security patch changed it (yes that does happen!)
Edit: just reread the OP, his FRP is locked! That means he can't use the code.
Click to expand...
Click to collapse
Jesus, what am I like?? Of course he can't.
Cheers @hackintosh5.
Samsung releases security updates every month, and i think they are the culprit, since i just cant flash TWRP with Odin on My Galaxy Note 8. It says failed. Ive tried 3.3.1and even latest 3.5.0 and both fail.
Its the Exynos CPU which can be rooted. At least i know this for sure
Do you know of any solutions to this
{
"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"
}
therock003 said:
Samsung releases security updates every month, and i think they are the culprit, since i just cant flash TWRP with Odin on My Galaxy Note 8. It says failed. Ive tried 3.3.1and even latest 3.5.0 and both fail.
Its the Exynos CPU which can be rooted. At least i know this for sure
Do you know of any solutions to this
Click to expand...
Click to collapse
I recently flashed the latest filmware and managed to flash TWRP 3.5 after so it's not Samsung blocking it. What Odin version are you using? I'm using 3.13.3. I had to install 15 second Adb for it to work though which can be found in the link below. You enabled the OEM toggle?
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
Whats the OEM toggle.
Are you sure that adb install is legit cause it looks like a 2013 post. Anyway i even tried the latest 3.14.1 odin and also that adb package you posted. It still fails
therock003 said:
Whats the OEM toggle.
Are you sure that adb install is legit cause it looks like a 2013 post. Anyway i even tried the latest 3.14.1 odin and also that adb package you posted. It still fails
Click to expand...
Click to collapse
You have to enable the OEM toggle in the development settings (settings/about phone/software information/the click on the build number 7 times will enable dev setting) for TWRP to be able to flash. This is probably why it's not flashing for you. If you don't know about the OEM toggle, do you know that as soon as you flash TWRP that it trips Knox and Samsung Pay will never work again unless you get a motherboard replacement?
Yes the 15 second adb is legit. Used it for a long time.
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
therock003 said:
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
Click to expand...
Click to collapse
I did not mention auto update...
therock003 said:
If you mean the auto update on deleveper iptions i turned it off after you said so. But still same thing. Apparently theres this frp lock happening
Click to expand...
Click to collapse
I have not said anything about auto update. In the dev setting you should see "OEM unlocking" toggle, like in the screenshot I added. If you don't see this option let me know and I will see if I can find the thread that might help you get the toggle.
FRP lock is Factory Reset Protection. So if your phone is lost or stolen that person can't just flash stock firmware to use your phone it makes it so they have to login to your account to be able to use the phone, although this only works on the stock rom without root as it needs encryption.
No you were right. didnt notice the oem unlocking toggle. Read another page that told me to turn off auto updates and this was misleading
Does Odin Unlock Bootloader? - codekomusic.com
What happens if I unlock bootloader? A device with a locked bootloader will only boot the operating system currently on it. You can’t install a custom operating system – the bootloader will refuse to load it. If your device’s bootloader is unlocked, you will see an unlocked padlock icon on the...
codekomusic.com
How do I turn off OEM lock?
Open developer options (in the Settings app itself), and find the option called ‘Auto update system’. Use the toggle button to disable it.
Click to expand...
Click to collapse
Anyway i got TWRP running now, and im off to install magisk and the rest of the steps. Thanx man for helping me
therock003 said:
No you were right. didnt notice the oem unlocking toggle. Read another page that told me to turn off auto updates and this was misleading
Does Odin Unlock Bootloader? - codekomusic.com
What happens if I unlock bootloader? A device with a locked bootloader will only boot the operating system currently on it. You can’t install a custom operating system – the bootloader will refuse to load it. If your device’s bootloader is unlocked, you will see an unlocked padlock icon on the...
codekomusic.com
Anyway i got TWRP running now, and im off to install magisk and the rest of the steps. Thanx man for helping me
Click to expand...
Click to collapse
Glad to hear! Happy flashing.
Oh man now I get a verirication failed. Followed this guide and flashed magisk , no verity opt and rmm state. After that it says reboot your mobile
Root Samsung Galaxy Note 8 SM-N950F Pie 9.0 using TWRP and Install Magisk
After Samsung released One UI Pie 9.0 version, most of the users who blame Samsung's Custom skin OS, Praising Samsung. It may not be best like OnePlus
www.androidinfotech.com
And it has a footnote. "Oh we didnt actually mean that. We meant reboot into recovery otherwise youll have to reflash your firmware."
I mean cmon how stupid csn these guides get. So what now hoe do i reflash the stock firmware
Seriously i need some help cause thst guide inposted previously is the worst. I refladhed stock firmware and redid the procedure. Based on thst guide you must first flash twrp. After you boot into TWRP you install magisc no verity and smm and reboot. I do all that and end up eith no firmware. Whats going wrong here
therock003 said:
Seriously i need some help cause thst guide inposted previously is the worst. I refladhed stock firmware and redid the procedure. Based on thst guide you must first flash twrp. After you boot into TWRP you install magisc no verity and smm and reboot. I do all that and end up eith no firmware. Whats going wrong here
Click to expand...
Click to collapse
You must have wiped "system" in TWRP for that to happen. You only need to format data where you have to type "yes" to confirm, then you can flash Magisk.
Make sure to backup your EFS folder with TWRP too! So important to do this
Wait doni need to format or something, cause i was under the impression that i get to keep.my files. I havent wiped anyrhing besides cache. I only do advanced wipe and select cache each time i installed anyrging. I never did a full wipe. Do i need to?
So here is what i do in detail step by step.
I flash TWRP on AP on odin and then boot in TWRP. I select full permission and not read only and go to instal.
I install magisc 20.3.zip then go advances wipe and wipe cache.
Then repeat with the rest. Install thst opt verity then clear chache. Instal smm state then clear cach and finally i reboot.
What did i not do here
therock003 said:
Wait doni need to format or something, cause i was under the impression that i get to keep.my files. I havent wiped anyrhing besides cache. I only do advanced wipe and select cache each time i installed anyrging. I never did a full wipe. Do i need to?
So here is what i do in detail step by step.
I flash TWRP on AP on odin and then boot in TWRP. I select full permission and not read only and go to instal.
I install magisc 20.3.zip then go advances wipe and wipe cache.
Then repeat with the rest. Install thst opt verity then clear chache. Instal smm state then clear cach and finally i reboot.
What did i not do here
Click to expand...
Click to collapse
I'm not sure as I have never flashed the RMM and Verity, I just flash a custom Rom which has all that patched already.
I thought we had to format data to be able to flash anything in TWRP, I didn't think keeping all data was possible.
Then i guess ill have to spend all day to backup all apps and files and try to fully erase memory