I have an FUT device as well, and I was told those will not work with the unlock tool. Devs got the code through other avenues.
[TWRP] for KIW-L24, L22, L21 (kiwi)
- Thread starter deadman96385
- Start date
I have an FUT device as well, and I was told those will not work with the unlock tool. Devs got the code through other avenues.
On Grabbing stock ROM is it possible to escape bootloop during recovery flashing ???
Last edited:
People act like there are 127 pages to this thread and they forgot every thread has a search function....If you are wondering if something is supported, feel free to search the thread for "supported" or "l22" and there is your answer....
Sent from my KIW-L24 using Tapatalk
Sent from my KIW-L24 using Tapatalk
Link is dead and my Avast antivirus says a threat has been detected. Yeah nice one. Good going you guys. Really great.
Hahahaha....yeah alright...4 lead devs for 4 big roms, working with huawei, is gonna do some shady stuff to ya....Well played...
Sent from my KIW-L24 using Tapatalk
Although touch/swipe had issues in TWRP I am rooted now. Not sure what caused it but with some patience it works enough to Make a Backup and Flash needed files.I wonder what is different in my case than from the ones who had no lag in TWRP. Very strange.
I experienced similar issues with TWRP even after several flashes. Mine was not so much lag but seemingly phantom/ghost touches. It seemed if I was able to tap the area of the screen fast enough before a another input overrode my selection then I could get it to work. Interestingly enough if I tilted the device in various directions it would scroll up and down the menus.
In the end I was able to get it to work, getting the slider all the way across the screen was certainly a challenge!
b130 on L24 is the firmware version and device that deadman and myself has tested on without issue....b141 has been told has buggy issues with twrp by Huawei...b140 was also verified by Huawei as working smoothly...just a heads up
Sent from my KIW-L24 using Tapatalk
Sent from my KIW-L24 using Tapatalk
Looks like I am on the same: KIW-L24C567B130... At least I was ultimately able to get it to work in some fashion, maybe I'll try reflashing TWRP a time or two again and see if anything ever changes. Thanks for the heads up!
We are testing an official twrp from @Dees_Troy right now...will update when tested enough..Seems to be flawless from my side....Official support from twrp will be coming soon as well
For what it's worth I tried installing Xposed multiple times using the ZIP in TWRP before I realized that Xposed doesn't work with EMUI. In no case did I have any problems getting back into TWRP and reflashing a system backup. So in my case the "You'll have to reinstall TWRP" part did not seem to be true even after several attempts to install and boot with Xposed.
Separate question: Is it possible to encrypt the device (data partition) after installing TWRP and root? When I try it just hangs at the logo screen and doesn't do anything. If I force reboot it it boots up normally but is not encrypted.
Thanks!
It seems that there are a few of us having the same problem. I am also on L24 and B130. Curious to know what the deal is.
Encryption breaks boot...took us a minute to realize that was interfering with a few things...its still early everybody but we are really working at stuff, I promise
Sent from my KIW-L24 using Tapatalk
I had no trouble getting back into TWRP after the error either. Or throwing a restore.
I think you'll find that if you look at the recovery log you'll find all manner of errors introduced that don't exist otherwise - and it's all stuff you don't want if you're going to rely on your recovery. And from testing, it's definitely repeatable, not something that's one-off.
You do as you think best, but if I were you, I'd replace TWRP with a fresh copy.
Seems I'm the only one getting this error when trying to request the unlock code (step2)
Sorry, the server is busy ......
We're sorry but the server is busy ...
Server Busy (6).If you have time .......Please send me screenshots moderators.Please provide a connection which appear on this page in one click.Click on the following link to view other content on the site*(*www.emui.com*):
Back to Home
Anyone else see that?
Sorry, the server is busy ......
We're sorry but the server is busy ...
Server Busy (6).If you have time .......Please send me screenshots moderators.Please provide a connection which appear on this page in one click.Click on the following link to view other content on the site*(*www.emui.com*):
Back to Home
Anyone else see that?
When you go to login make a new account using Facebook. I had the same exact issue and using Facebook fixed it.
I was experiencing the same issue, and if creating an account via Facebook does not work for you, here is what I found...
After initially creating and activating my account in step 1 through email registration, whenever I would click the posted link from step 2, I would receive the same "Server Busy" error... Instead of following the link directly from step two, I just returned to the original login page from step 1 (http://goo.gl/OlsI8a) and logged in using my username and password. From there it takes you to the "Unlock Agreement" page (which is where the link in step 2 takes you) and after accepting the form I no longer received the "Server Busy" error. However none of it is in English so using chrome with translation got me through the rest.
First guess may be an adblocker...but that's speculation
Sent from my KIW-L24 using Tapatalk
Similar threads
- Locked
Top Liked Posts
-
There are no posts matching your filters.
-
78Code:
/* * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed. Please * do some research if you have any concerns before doing it! YOU are choosing * to make these modifications, and if you point the finger at us for messing up * your device, we will laugh at you. * */
Step 1
Make a Huawei ID at the following
http://goo.gl/OlsI8a
Step 2
Log in and fill out the details needed
https://goo.gl/VEKvXY
How to get the product identification code ?
In the phone's dial-up interface, enter * # * # 1357946 # * # *
What you will need:
Step 3
Now that you have your unlock code go to about phone in settings and click the build number until it tells you that you are a developer. Then go back once and select developer options and look for usb debugging and turn it on.
Step 4
Enable Developer settings by going to Settings > about phone and click build number until it says you are a developer.
Once that is done go back to the main settings and go to developer settings and enable OEM unlock.
Step 5
I am going to assume you have adb and fastboot installed on your computer, but if not go to this thread to install it.
http://xdaforums.com/showthread.php?p=48915118
Step 6
Plug your device into the computer and authorize your device key so adb will work, then type the following commands:
Once it boots into the bootloader do the following commandCode:adb reboot bootloader
Where numbers are put what you got from the website keep in mind it will wipe your data so if you have any personal data back it up first.Code:fastboot oem unlock 2062712452147427
Step 7
Boot up the phone and set it up
Step 8
Download the twrp recovery image
https://goo.gl/53xai9
Step 9
Boot back into the bootloader by typing the following
Code:adb reboot bootloader
Step 10
Flash the recovery with the following command:
Code:fastboot flash recovery twrp_kiwi.img
Step 11
Once it finishes type the following
Code:fastboot reboot
If you want root unhide this and follow the steps:
Thanks to all of the following for getting this working:
SHM
@Dees_Troy
Ncrypt3d
@InkSlinger420
@EarlyMon
19Warning!
Don't try to install xposed on your stock rooted EMUI rom.
It won't work
The system won't boot
You'll have to recover from a nandroid backup
You'll have to reinstall TWRP
That is NOT TWRP's fault
My personal, unverified, guess is that Huawei is writing to recovery in an attempt to, well, recover, when it detects a system fault13New version of TWRP has been released few weeks ago, most notable changes in 3.1.0 include:
- support new Android 7.x xattrs for backup and restore to fix loss of data after a restore (Dees_Troy)
- try mounting both ext4 and f2fs during decrypt (jcadduono and Dees_Troy)
- support new Android 7.x log command (Dees_Troy)
- adb backup to stream a backup directly to or from your PC, see documentation here (bigbiff)
missing f2fs and decryption support.
Now, the good news is i have made a version with logd, f2fs and decryption working in my 3.1.0 image, all built on lineageos 14.1 and using the same kernel as the official LineageOS, available in the official 14..1 thread.
I am still testing, and tweaking some things before i post new image (old broken images from me should be removed to avoid confusion). Lookie below and stay tuned!13Patience, folks, the image will be updated soon! Send big thank you's to @crpalmer for backporting properly the f2fs patches! (and correcting my commit mess).
And no i will not be creating new topics or release new images once it's official, no need to duplicate what TeamWin already does while maintaining the twrp releases, a good job thank you! @bigbiff13TWRP 3.0.2.0 with decryption
Hi there. I have created test build of TWRP with decryption feature. I am using CM13 and recovery decrypts data partition successfully. Please test it and check if it works correctly. Any feedback appreciated.
Screenshots: https://imgur.com/a/oXaSU
Download: https://drive.google.com/file/d/0ByhhV-Ab8exKTlFFVUFhTTZ0bEk/view
Btw, it's based on CM13 tree and kernel. If everything works well I will clean up source code and upload it to github! Thanks.
