finally i found twrp that work perfect for emui 9.1 firmware
download link and password for extract on this site
{Mod edit: Link removed. Not suitable iaw. rule no. 11 of the forum rules. Oswald Boelcke}
Credits where due (though I can't 100% confirm this, given all downloads on the website give me error 404)
{Mod edit: Link removed. References to 4pda are not accepted on XDA! Oswald Boelcke}
EDIT: I really don't know what I may have linked here, but let's pretend it was this https://github.com/rxuglr/android_device_huawei_leland-recovery
Since this is unofficial, how can I know if it is safe?
Alex46165 said:
Since this is unofficial, how can I know if it is safe?
Click to expand...
Click to collapse
Here you go
I get this error on EVERY TWRP:
FAILED: (remote: partition lengh get error)
Is there no possibility with the EMUI 9.1?
layalala said:
I get this error on EVERY TWRP:
FAILED: (remote: partition lengh get error)
Is there no possibility with the EMUI 9.1?
Click to expand...
Click to collapse
You are doing something wrong...
@-Alf-
and what could be wrong?
The device is unlocked, in fastboot mode and is listed as fastboot device.
'sudo fastboot flash recovery TWR9.img'
layalala said:
what could be wrong?
Click to expand...
Click to collapse
The command.
For emui 9.1 use
fastboot flash recovery_ramdisk xxxx.img
-Alf- said:
You are doing something wrong...
Click to expand...
Click to collapse
and what could be wrong?
The device is unlocked, in fastboot mode and is listed as fastboot device.
'sudo fastboot flash recovery TWR9.img'
-Alf- said:
The command.
For emui 9.1 use
fastboot flash recovery_ramdisk xxxx.img
Click to expand...
Click to collapse
THANKS A LOT!!!
Just did not read it on the page... stupid
Related
Hello everybody,
I was trying to reinstall the factory image on my Nexus 6 with a script and everything went wrong. Now when I reboot in recovery I have a menu (restart bootloader, recovery.....) but I can't see with my phone on my computer (ubuntu). I tried every mode on the phone menu : bootloader, recovery, factory mode, bar codes, bptools....but the phone doesn't mount on the computer.
So I'm not able to do anything on it. Any clues ?
Thanks.
Martin
Well, I made some progress. I found this and the command ''adb sideload''. But now, I'm stuck with ''you need adb 1.0.32 or newer'' to install a recovery on my Nexus.
Can't find an easy way to install a ''newer'' adb tools on my Ubuntu...
Now, i managed to update the adb version to 1.0.32. But I got the message when I ''adb sideload'' twrp-2.8.7.1-shamu.img:
E:footer is wrong
E:Signature verification failed
Installation aborted
Didn't have time to work on this for a while but still no anwser from anyone. Does someone know another forum where I could try to find any clues?
mchenier said:
Didn't have time to work on this for a while but still no anwser from anyone. Does someone know another forum where I could try to find any clues?
Click to expand...
Click to collapse
your answer..
thats not your recovery that youre booting into, thats your bootloader. and the only thing that works in the bootloader is fastboot. adb does not work in the bootloader. and you need to use fastboot to flash a factory image, not adb.
Ok, thanks. I just figure that out couple of minutes ago. I'm almost there. I was able to install TWRP on my Nexus 6. The problem now is when i tried to install ''image-shamu-mmb29q.zip'' with TWRP, it failed even if I wipe the cache and Dalvik cache before. And I don't know why.
It's says ''Error flashing zip
Ok, I have done it. Find that web page to help me: http://9to5google.com/2015/10/05/ho...nexus-5-nexus-6-nexus-7-nexus-9-nexus-player/
I thought I had to install the zip file with TWRP. The right action was that:
First, flash the bootloader and the radio, and then reboot the bootloader (radio only applies to some devices):
fastboot flash bootloader <bootloader file name here>.img fastboot flash radio <radio file name here>.img
fastboot reboot-bootloader
Flash the recovery, boot, system, and vendor images (vendor only applies to some devices):
fastboot flash recovery recovery.img fastboot flash boot boot.img fastboot flash system system.img fastboot flash vendor vendor.img
Recommended: For a full wipe, flash cache and userdata as well (userdata only applies to some devices):
fastboot flash cache cache.img fastboot flash userdata userdata.img
Reboot your device:
fastboot reboot
Thanks. I'm done.
sweet:
but all that information is here, on XDA, in the stickies. didn't you look?
simms22 said:
sweet:
but all that information is here, on XDA, in the stickies. didn't you look?
Click to expand...
Click to collapse
Don't know what the stickies are.
mchenier said:
Don't know what the stickies are.
Click to expand...
Click to collapse
this is a helpful sticky from the general thread http://forum.xda-developers.com/nexus-6/general/nexus-6-sticky-roll-thread-t3061066
they are important threads stuck, or stickied, to the top of the general section
Ok, thanks. I'll keep it for future references.
mchenier said:
Ok, thanks. I'll keep it for future references.
Click to expand...
Click to collapse
also, if your stuck somewhere, pm me. i would be happy to help.
simms22 said:
also, if your stuck somewhere, pm me. i would be happy to help.
Click to expand...
Click to collapse
Eh! thanks a lot.
I just installed Cyanogenmod on a Nexus 4. I have a collection to work with. Someday I might be good at it
I realize that our device have the source code on Asus website and the unlock tool haven't been released by Asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame Asus for that! But, I could stop thinking and doing this and (BAM!) the bootloader unlocked and I'm able to boot patched boot.img with Magisk Manager app.
READ THIS FIRST!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
PLEASE READ CAREFULLY!
1. Reboot to Bootloader by pressing power + vol up
2. Type fastboot command below:
echo > key.txt
fastboot oem get_unlock_key key.txt
fastboot reboot-bootloader
Click to expand...
Click to collapse
3. Enjoy the freedom of Android experience with annoying verifiedboot caution on the start ( Blame Google for that) but it's not a big problem.
To relock bootloader type this in fastboot (Thanks to @shakalaca for telling that in this thread)
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
Click to expand...
Click to collapse
REMEMBER! DO WITH YOUR OWN RISK! I'M NOT RESPONSIBLE FOR WHAT HAPPENS TO YOUR DEVICE AND YOUR LIFE FOR DOING THIS! GOOD LUCK!
PS: I dont have any device to take a shot from my device because this Zenfone was my only device that I have.
To do list:
- Get rid of the caution at startup that reminds our bootloader state
NOTE: This method works only for version below 215. If you're updated to latest firmware. It won't work since Asus update the bootloader. And the bootloader just temporarily unlocked with this method. If device restarted, the bootloader get locked automatically
Не работает
Here's what happens:
C:\adb>fastboot oem get_unlock_key
...
(bootloader) @!
OKAY [ 0.004s]
finished. total time: 0.005s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: unknown command)
finished. total time: 0.004s
aaaaaaziskurnia said:
i realize that our device have the source code on asus website and the unlock tool haven't been released by asus. That's maybe a chance for unlocking bootloader and play guessing that our device is just using similarly same method with nexus or other legacy bootloader locking mechanism. Thanks, and blame asus for that! But, i could stop thinking and doing this and (bam!) the bootloader unlocked and i'm able to boot patched boot.img with magisk manager app.
Read this first!
Before you all do this, it's recommended to do factory reset before unlocking bootloader because our device is using force encryption by default. If you didn't reset your device, you will get locked from the start and cannot doing anything even you type password or pin correctly.
Please read carefully!
1. Reboot to bootloader by pressing power + vol up
2. Type fastboot command "fastboot oem get_unlock_key" then press enter key
3. After that type "fastboot oem unlock-go"then hit enter again
4. Check the bootloader status by rebooting to bootloader back using command "fastboot reboot-bootloader"
5. Enjoy the freedom of android experience with annoying verifiedboot caution on the start ( blame google for that) but it's not a big problem.
Remember! Do with your own risk! I'm not responsible for what happens to your device and your life for doing this! Good luck!
Ps: I dont have any device to take a shot from my device because this zenfone was my only device that i have.
To do list:
- find a hack to relock again the bootloader
- get rid of the caution at startup that reminds our bootloader state
Click to expand...
Click to collapse
you have 2/16 or 3/32 ???
Johann Richter said:
you have 2/16 or 3/32 ???
Click to expand...
Click to collapse
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls
aaaaaaziskurnia said:
Actually not the size of the rom and ram. But the SOC, I have the msm8937. Check yours pls
Click to expand...
Click to collapse
I have 8917, no options with this?
Johann Richter said:
I have 8917, no options with this?
Click to expand...
Click to collapse
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.
aaaaaaziskurnia said:
Try this methods. Because asus share same project named ZC554KL in the source code I've inspected, It's worth to try.
Click to expand...
Click to collapse
After much suffering, 15 times to unlock the bootloader. Thank you!!!
Johann Richter said:
After much suffering, 15 times to unlock the bootloader. Thank you!!!
Click to expand...
Click to collapse
I've suffering same thing as you in the first but it's unlocked. Good luck and enjoy development
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..
shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
It works on my TW sku ..
Click to expand...
Click to collapse
Thanks shalaca, I'll include it to the first Page :good::laugh:
shakalaca said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
Code:
echo > key.txt
fastboot oem reset_unlock_key key.txt
fastboot erase config
fastboot flashing lock
fastboot reboot-bootloader
It works on my TW sku ..
Click to expand...
Click to collapse
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?
Johann Richter said:
Phone should be unlocked once you've done "fastboot oem get_unlock_key" , you can then verify after "fastboot reboot-bootloader" with on-screen-message.
To lock the phone again:
thanks a lot, very useful information
---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
On our device there is TWRP?
Click to expand...
Click to collapse
Just wait for TWRP. I've got built TWRP but still messed up. Stil investigating.
tks for your guide
can you root with supersu?? or can you send a custom recovery to flash zip file?
Mr Foot said:
can you root with supersu?? or can you send a custom recovery to flash zip file?
Click to expand...
Click to collapse
I suggest using Magisk. Since the stock rom protected /system by selinux. If you doing any modifications in /system , it will result hangs or unbootable device and you should clean flash again.
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
so is he a worker?
Johann Richter said:
so is he a worker?
Click to expand...
Click to collapse
who ? me ?
shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Thanks, it works
shakalaca said:
If someone is interested in building TWRP here's the source: https://github.com/shakalaca/android_device_asus_X00I
I've already built one https://www.androidfilehost.com/?fid=673791459329051335
And currently I don't have the phone on my hand so feel tree to fork/build/test/fix/release TWRP ..
Click to expand...
Click to collapse
I'm already have a device tree written two weeks ago.
https://github.cm/aaaaaaziskurnia/twrp_device_asus_X00ID
But messed up many times so I freshly uploads all the device tree.
I'm still new but I can sure that I'm fast learner. Should we collab?
shakalaca said:
who ? me ?
Click to expand...
Click to collapse
Good day, which firmware do you use?
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
kadirc5 said:
Hi guys
I want to install android 8 (emuı or custom rom) but the oreo twrp doesnt installing, ı tried every time and show an error, how to fix this thing?
Click to expand...
Click to collapse
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
CarlosAG10 said:
You must give more info so that anyone can understand your problem. Which steps did you follow, which error is it...??? BTW better post it in its right thread (Oreo flashing guide)
Click to expand...
Click to collapse
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
kadirc5 said:
First part, is the twrp installation on the fastboot mode. I wrote this code > fastboot flash recovery_ramdisk recovery_ramdisk.img and pressed enter
Sending... Ok
Writing...
FAİLED
Click to expand...
Click to collapse
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
CarlosAG10 said:
Try sending command "fastboot devices". Does a number appear? In that case, check your recovery_ramdisk img and directory
Click to expand...
Click to collapse
Yes, shows a number
How can ı check?
kadirc5 said:
Yes, shows a number
How can ı check?
Click to expand...
Click to collapse
Download the files again and make sure you are correctly using fastboot
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Striike said:
since you rebranded the device, you should unlock the bootloader again. fastboot doesn't allow running command with a locked bootloader
fastboot oem unlock yourcodehere
Click to expand...
Click to collapse
Im gonna try at the weekend thanks
Hy guys!
How can I reflash to Stock Recovery from TWRP?
I tried to root my phone and now its bricked (stuck at Android logo)
I want to reflash the stock android but with OST I cant..
In download mode the fastboot is working but the adb not..
szilard0933 said:
Hy guys!
How can I reflash to Stock Recovery from TWRP?
I tried to root my phone and now its bricked (stuck at Android logo)
I want to reflash the stock android but with OST I cant..
In download mode the fastboot is working but the adb not..
Click to expand...
Click to collapse
Get the boot.img correct to the version of security Patch on your phone. Than in download mode check the current slot which is on use by typing :
fastboot getvar current-slot
When you know your slot, type:
fastboot flash boot_yourslot path_to_correct_boot.img
And reboot.
czupyt said:
Get the boot.img correct to the version of security Patch on your phone. Than in download mode check the current slot which is on use by typing :
fastboot getvar current-slot
When you know your slot, type:
fastboot flash boot_yourslot path_to_correct_boot.img
And reboot.
Click to expand...
Click to collapse
current-slot: b
But where can I find the correct boot.img? I tried in google but nothing.. I think I need the october security patch.
And if I download how can I send to phone? (SD card??)
szilard0933 said:
current-slot: b
But where can I find the correct boot.img? I tried in google but nothing.. I think I need the october security patch.
And if I download how can I send to phone? (SD card??)
Click to expand...
Click to collapse
Username @Trissi puted it here: https://cloud.vault81.de/s/fnoizKwi8kNF3Rg
Based on info you provided, download the stock one of October, rename it to boot.img and type in CMD in download mode:
fastboot flash boot_b path on your PC to boot.img
and than reboot. Of course you will loose TWRP (by the way, how can you have TWRP on October Patch) and root, if you have.
czupyt said:
Username @Trissi puted it here:
Based on info you provided, download the stock one of October, rename it to boot.img and type in CMD in download mode:
fastboot flash boot_b path on your PC to boot.img
and than reboot. Of course you will loose TWRP (by the way, how can you have TWRP on October Patch) and root, if you have.
Click to expand...
Click to collapse
Thanks for your help.
I made this now the phone is starting in Download mode. With OST I can flash it now? Beacuse how I read with TWRP Recovery its not possible to flash via OST.
szilard0933 said:
Thanks for your help.
I made this now the phone is starting in Download mode. With OST I can flash it now? Beacuse how I read with TWRP Recovery its not possible to flash via OST.
Click to expand...
Click to collapse
As far as I know, TWRP works only until you are on August Security Patch. If you had TWRP, you had to be maximum on August Patch. Maybe you used wrong boot.img. To use OST I think you have to be unlocked critical, but maybe someone smarter will correct me.
You're right, to use Ost tool u have to unlock critical!
2WildFirE said:
You're right, to use Ost tool u have to unlock critical!
Click to expand...
Click to collapse
FAILED (remote: 'Flashing Unlock is not allowed')
Any ideas?
szilard0933 said:
FAILED (remote: 'Flashing Unlock is not allowed')
Any ideas?
Click to expand...
Click to collapse
Have you tried to switch slot to A?
czupyt said:
Have you tried to switch slot to A?
Click to expand...
Click to collapse
Now I switched to slot A, critical unlocked. With OST I flashed NB1-4390-0-00WW-B01.nb0 successfully but now its stuck on Nokia logo..
I tried to install newer frimware:
NB1-484A-0-00WW-B03.nb0
NB1-488B-0-00WW-B04.nb0
But its stopped on "Checking device status..."
I tried a factory reset in recovery and now its wooooorking
I just try to root it...
szilard0933 said:
Now I switched to slot A, critical unlocked. With OST I flashed NB1-4390-0-00WW-B01.nb0 successfully but now its stuck on Nokia logo..
I tried to install newer frimware:
NB1-484A-0-00WW-B03.nb0
NB1-488B-0-00WW-B04.nb0
But its stopped on "Checking device status..."
I tried a factory reset in recovery and now its wooooorking
I just try to root it...
Click to expand...
Click to collapse
For the future, for OST LA 6.0.4 and Oreo SW (which is NB1-488B-0-00WW-B04.nb0) use the following workaround:
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
czupyt said:
For the future, for OST LA 6.0.4 and Oreo SW (which is NB1-488B-0-00WW-B04.nb0) use the following workaround:
https://forum.xda-developers.com/nokia-7-plus/how-to/workaround-flashing-oreo-firmware-t3793791
Click to expand...
Click to collapse
Thanks GUYS!
Now its working pretty well
And a last question, how can I update the security patches because now I got update failed for 2018-07.
I found this
STEPS_TO_UPDATE:
1. Go into Magisk Manager -> Uninstall -> Restore Images
2. Apply Update, DO NOT REBOOT YET
3. When step to finished and it promts you to reboot go into Magisk Manager -> Install -> Install to inactive Slot
But after downloading update I got install problem..
What failed for you
czupyt said:
What failed for you
Click to expand...
Click to collapse
I tried to install but install failed and after that I didnt had wireless.
I reflashed with OST after that :
fastboot flash boot_a stock_boot_nb01_488_sp04_sep.img
same thing..
szilard0933 said:
I tried to install but install failed and after that I didnt had wireless.
I reflashed with OST after that :
fastboot flash boot_a stock_boot_nb01_488_sp04_sep.img
same thing..
Click to expand...
Click to collapse
There is a little bit chaos in your words. You wrote once that all is fine now, after that you said update had not worked for you, and you showed steps to OTA update with Magisk with A/B partition scheme. After that you said you reflashed with OST, but you entered fastboot flash command. You also mentioned that your critical unlock bootloader status is true.
Could you run phone in download mode and use fastboot getvar all command and paste here the results?
I had installed LOS 8.1 on my phone with some chinese recovery few years back (may be 2018)......... working great.
Now i uninstalled Magisk ..............
Now I have Pretoria https://forum.xda-developers.com/t/...e-unofficial-twrp-3-2-1-0-12-05-2018.3789306/ installed .......... which is stuck on very first page.
i Want to reinstall MAgisk which needs TWRP
I have tried to flash new twrp in fastboot ........ but every time.......... error shows ............. command not allowed.
so guide me
kdark said:
command not allowed.
Click to expand...
Click to collapse
make sure you have both FRP and bootloader unlocked
-Alf- said:
make sure you have both FRP and bootloader unlocked
Click to expand...
Click to collapse
FRP is locked
how to revert to stock rom?
kdark said:
how to revert to stock rom?
Click to expand...
Click to collapse
A. Use eRecovery
B. Flash full stock FW using dload method
-Alf- said:
A. Use eRecovery
B. Flash full stock FW using dload method
Click to expand...
Click to collapse
i dont think erecovery is working bcoz twrp is flashed
kdark said:
twrp is flashed
Click to expand...
Click to collapse
How did you install it? Over Recovery or over eRecovery?
-Alf- said:
How did you install it? Over Recovery or over eRecovery?
Click to expand...
Click to collapse
dont remember coz it was in 2018........ but in erecovery ...... it only show reboot option
kdark said:
. it only show reboot option
Click to expand...
Click to collapse
I'm not sure I fully understand you... There is no Recovery or eRecovery which shows only one option.
-Alf- said:
I'm not sure I fully understand you... There is no Recovery or eRecovery which shows only one option.
Click to expand...
Click to collapse
if i boot to recovery from phone ........... it goes to TWRP {which is stuck} ........ otherwise erecovery shows only reboot option
-Alf- said:
I'm not sure I fully understand you... There is no Recovery or eRecovery which shows only one option.
Click to expand...
Click to collapse
give me fastboot commands to flash both twrp and erecovery
kdark said:
give me fastboot commands to flash both twrp and erecovery
Click to expand...
Click to collapse
maybe you meant to say "give me please"...
Google it.
-Alf- said:
maybe you meant to say "give me please"...
Google it.
Click to expand...
Click to collapse
plz
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
-Alf- said:
in fastboot mode run commands :
fastboot oem get-build-number
fastboot oem get-product-model
fastboot getvar vendorcountry
fastboot oem oeminforead-CUSTOM_VERSION
fastboot oem oeminforead-SYSTEM_VERSION
and post the results.
Some might fail, so don't worry about it.
Click to expand...
Click to collapse
LLD-AL10 8.0.0.160(C675)
(bootloader) LLD-AL10
vendorcountry: hw/in
FAILED (remote: 'The reason of failed input oem_nv_item error!')
fastboot: error: Command failed
(bootloader) :LLD-AL10 8.0.0.160(C675CUSTC675D2)
FRP still locked?
Try to perform factory reset in fastboot mode, run command
fastboot erase userdata
Then try reboot TWRP and flash this file:
https://mega.nz/file/Q1dzQAqK#VGEZOvTalbDWow8epmN6ht7XNc9VH-4rapKtqU_3Y3A
FRP status will change to Unlock.