Hi guys, muy English is not so good, but here we go:
I had a problem after rooting my P10, my phone is a VTR-L09c605 and I rebranded it to VTR-L29c432 successfully and after that I updated it to Oreo (b360) using the hwota.bat successfully again.
I flashed twrp for oreo and I installed magisk v16 without problems, it worked so fine until I decided to debloat a bit the phone, I remember that I uninstaled all the Gapps (using a Fx file explorer directly from system partition) and other app that I can't remember, after that I rebooted the phone and was stuck at bootloop, I saw the huawei bootanimation normarly (the bubbles with blue background) and the phone restarted again and again... In that moment I rebooted into twrp and wipe cache partition, I flashed this stock ramdisk https://forum.xda-developers.com/p10-plus/development/magisk-p10-p10plus-t3752482 and no luck (I don't know why I did it).
After that, I tried to flash the full ota using the hwota.bat but i was stuck at "your device has been unlocked and cannot be trusted, the phone is booting now" that message appears always when I tried to enter into twrp or erecovery but now it was stuck in that message and I rebooted it manually into fastboot, maybe the problem was that whem I tried to flash again the oreo full ota, I used the same files (contained in the recovery folder (twrp and recovery nocheck) from nougat.
Please guys, help me, I still can boot into fastboot, but can't boot into twrp(even flashing it via fastboot recovery_ramdisk) or erecovery, maybe the hwota.bat needs to be edited, but I don't know what lines I need to change, if someone knows how to repair the phone, please, help me.
Thanks in advanced
If you deleted some system app or system file by mistake it wont probably boot, try to flash ramdisk, original recovery_ramdisk, original kernel, and original system.img to see if it boots again, I would just try the first ramdisk(to get rid of root) recocery_ramdisk and original kernel.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
If you deleted some system app or system file by mistake it wont probably boot, try to flash ramdisk, original recovery_ramdisk, original kernel, and original system.img to see if it boots again, I would just try the first ramdisk(to get rid of root) recocery_ramdisk and original kernel.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I flashed some of them using fastboot, I extract them from the update.zip from the oreo's full ota (update.app) and using the huawei extractor, but there's a lot of recovery files, how to know which is the correct?
You just need recovery_ramdis.img it's written wrong in there and also ramdisk.img you also need kernel.img try with those only I have those file on my PC but I'm not home I could upload them and share you the link but it would be later.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
You just need recovery_ramdis.img it's written wrong in there and also ramdisk.img you also need kernel.img try with those only I have those file on my PC but I'm not home I could upload them and share you the link but it would be later.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
No success my friend, I'm still getting the error mode: please update system again, and can't boot into recpvery (I flashed it)
The files that tou have are for oreo? I'm on L29c432b360
I'm a bit desperate, hope it can be fixed :/
Yes I have that same build and model, done worry u had the same issue before and it took me awhile to recover it , for sure it has a fix. Remember i flashed some other file last time but don't remember which since they are in my PC, do you have frp unlocked and phone unlocked ? Do you have access to you unlocked key? I would try to relock now that you are on the stock recovery and try to factory reset once it enters erecovery after it gets lock it performs a factory wipe
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Also try to press the volume up and down at the same time to enter update mode
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
sfoot13 said:
No success my friend, I'm still getting the error mode: please update system again, and can't boot into recpvery (I flashed it)
The files that tou have are for oreo? I'm on L29c432b360
I'm a bit desperate, hope it can be fixed :/
Click to expand...
Click to collapse
Yes I had a similar issues same thing try to relock it and just make sure to be in stock recovery and ramdisk also and stock kernel. Once you relocked it I should do a factory reset try if that works.
Sent from my [device_name] using XDA-Developers Legacy app
lil_kujo said:
Yes I have that same build and model, done worry u had the same issue before and it took me awhile to recover it , for sure it has a fix. Remember i flashed some other file last time but don't remember which since they are in my PC, do you have frp unlocked and phone unlocked ? Do you have access to you unlocked key? I would try to relock now that you are on the stock recovery and try to factory reset once it enters erecovery after it gets lock it performs a factory wipe
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:06 PM ---------- Previous post was at 08:05 PM ----------
Also try to press the volume up and down at the same time to enter update mode
Sent from my [device_name] using XDA-Developers Legacy app
---------- Post added at 08:07 PM ---------- Previous post was at 08:06 PM ----------
Yes I had a similar issues same thing try to relock it and just make sure to be in stock recovery and ramdisk also and stock kernel. Once you relocked it I should do a factory reset try if that works.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes, I have frp and phone unlocked and I have my unlock key (saved as screenshot and .txt file).
So, if I relock my bootloader, it will do a low level format but actually I can't access to erecovery and update mode, because it fails to enter in that mode and I always get the error mode message.
But, there's a possibility to lock the bootloader and doing that, that action unlocks the access to erecovery? (sounds like a mess )
I'm not at home now, I'll try what you said me, and I'll wait until you can upload the files
Thank you so much for your help, I really appreciate it
Any success? I have the same problem. Im about ready to cough up 20 euros but im hopefully waiting for a solution.
I have same problem... Did you fix your phone? Some metohds for other guys work but not for me
We need a good tuto on that...Im stuck too now after trying some mods in build.prop
whats the adb command to flash erecovery-kernel/ramdisk ect.
---------- Post added at 03:32 PM ---------- Previous post was at 03:16 PM ----------
Cant extract Update.app in huawei update extractor...got error
Recovery_ramdisk.img Invalid header crc - Expected:22935 got 52610
really need help here hehehe
here are the results.. same as other guy,on that 432..
first of all.huawei update extractor wont open the update.pp from the HWOTA_VTRC432B360-Oreo package giving ramdisk error.....
have access to fastboot..
unlocked frp/bootloader
on stock recovery and cant flash any recovery---- twrp..it give some some partition error
successfully flashed :
kernel with erecovery_kernel_a.img
kernel with kernel_a.img
ramdisk with ramdisk_a.img
FAILED to flash:
erecovery_ramdisk_a with fastboot flash ramdisk erecovery_ramdisk_a.img (is it the good command ? )
recovery_ramdisk_a.img with fastboot flash ramdisk and recovery
so,whats next
please
all that cuz of frikkin build.prop MODIF.
i did re lock with low level reset...
i re unlock for another low level reset...
just wont boot anymore
when booting normally it takes me directly to firmware dload screen and fail to dload of course....
virusdunil said:
here are the results.. same as other guy,on that 432..
first of all.huawei update extractor wont open the update.pp from the HWOTA_VTRC432B360-Oreo package giving ramdisk error.....
have access to fastboot..
unlocked frp/bootloader
on stock recovery and cant flash any recovery---- twrp..it give some some partition error
successfully flashed :
kernel with erecovery_kernel_a.img
kernel with kernel_a.img
ramdisk with ramdisk_a.img
FAILED to flash:
erecovery_ramdisk_a with fastboot flash ramdisk erecovery_ramdisk_a.img (is it the good command ? )
recovery_ramdisk_a.img with fastboot flash ramdisk and recovery
so,whats next
please
all that cuz of frikkin build.prop MODIF.
i did re lock with low level reset...
i re unlock for another low level reset...
just wont boot anymore
when booting normally it takes me directly to firmware dload screen and fail to dload of course....
Click to expand...
Click to collapse
Same to me. Also i can flash CUST and some TWRPs but doesnt want to boot in recovery
I have fixed mine this morning by extracting KERNEL.img from update.app
fastboot flash kernel KERNEL.img
my p10 got back to life after trying all flashable things for maybe 6 hours yesterday
:silly:
I was stuck in error mode and managed to get out of it. I reached this gloriously by trying to flash Magisk V15.4 zip and then the oreoupgrade (from Jannomag), which failed..
First I tried the Multi-Tool method. Didn't work for me. Flashing was succesful, but no change in boot status.
So I slept over it and today I tried DC Phoenix. Selected the UPDATE.APP from update.zip and the UPDATE.APP from update_full_hw.zip. I cross my fingers and waited. It took a long time^^ When finished, it didn't reboot automatically. So I removed the cable and shut it down by pressing Power Button for some seconds. It booted then into eRecovery and I was confused.. It tried to download firmware via WiFi etc, but failed then with some ID error or smth, idk. I rebooted ....
aaaaaand voila: Booted without problems, all data still there!! :victory:
I sent it to tech service, tomorrow I'll know if they fixed my phone.
I think that I hard bricked it, because I relocked the bootloader, so the phone stuck at huawei's logo, no fastboot mode, no recovery, nothing, so guys, NEVER RELOCK THE BOOTLOADER if you get an error like that, it's the worst IDEA that you can have.
I'm a bit confused with this phone, looks like the system is very sensitive if you make modifications, like debloating or add or remove some lines in build.prop, things like tha.
Sadly, there's no much development for this phone :/
@Fenryl93 Happy to know that you fixed your phone bro!
@virusdunil you were using Oreo or Nougat? I was on Oreo, so I think that I'll not install Oreo until it becomes official :/
..
sfoot13 said:
@virusdunil you were using Oreo or Nougat? I was on Oreo, so I think that I'll not install Oreo until it becomes official :/
Click to expand...
Click to collapse
I was on nougat....VTR-L09 then rebranded it
Finally, the tech service repaired my phone, they changed the electronic board, well, that's what they wrote in the report.
So, I have my phone back, I'll try to be more careful this time.
Related
Anyone know why fingerprint sensor isn't working after i flash recovery of b145?
Same
I bricked my Mate S so extracted the img files from the stock B145 Europe full file, and flashed:
boot
recovery
system
cache
userdata
I have the same problem, fingerprint sensor doent work, there are no options in settings for the fingerprint sensor.
Also im unable to set any security, and also i cant uninstall any apps as the phone reboots everytime i do..
I did root the phone to see what was going on and the keystore is missing along with a whole bunch of errors.
I know it doesnt help, sorry
Arola1982 said:
I bricked my Mate S so extracted the img files from the stock B145 Europe full file, and flashed:
boot
recovery
system
cache
userdata
I have the same problem, fingerprint sensor doent work, there are no options in settings for the fingerprint sensor.
Also im unable to set any security, and also i cant uninstall any apps as the phone reboots everytime i do..
I did root the phone to see what was going on and the keystore is missing along with a whole bunch of errors.
I know it doesnt help, sorry
Click to expand...
Click to collapse
If you are both talking about flashing those files whilst on B303 or B321 it's just not possible at the moment..you'll need to restore a TWRP backup u made whilst on MM Beta to get security options back.
You just can't get back to 5.1.1 from MM Beta at the moment
Okay so ive tried to manually update. Won't work. Should i try to flash the images of b321 mabye?
Basicly stupid me doesn't have backup :/
Sent from my HUAWEI CRR-L09 using XDA-Developers mobile app
The same happened to me - semi-bricked my phone whilst I was on b321; wanted to root it and it didn't work. Now I'm back on b145 because I have no TWRP backup of b321 (stupid me). So, could anyone make a (clean) TWRP backup of CRR-L09C432B321? That would be awesome!
Thanks in advance - fbs
ask to dcunlocker in the support chat...huaweiphonewriterv4.exe to flash recovery update in fastboot mode and then reflash full firmware with same tool..i have save my device.
frisko76 said:
ask to dcunlocker in the support chat...huaweiphonewriterv4.exe to flash recovery update in fastboot mode and then reflash full firmware with same tool..i have save my device.
Click to expand...
Click to collapse
Well, my phone is not bricked. It's just a really dirty version of b145 (security options and automatic screen brightness and stuff like that is not working). But thanks, I will try it
edit: where can I find the support chat? Here on XDA? Sorry for this dumb question :S
edit: where can I find the support chat? Here on XDA? Sorry for this dumb question :S[/QUOTE]
On web site of dcunlocker in the tab contact live chat..describe your problem in the tecnichal support..
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
You not have stock recovery..you have twrp and not is possible flash original firmware....is possible to flash boot.img and recovery.img on the fastboot mode,but if you have frp lock this is not possible...only with tool of dcunlocker is possible to install recovery and boot original..after your install full firmware with same tool..
On web site of dcunlocker in the tab contact live chat..describe your problem in the tecnichal support..
Click to expand...
Click to collapse
Hi Frisko76
I have try to contact support DCunlocker chat , but there is nobody to help me today.
Can you send me a link for download huaweiphonewriterv4.exe?
frisko76 said:
edit: where can I find the support chat? Here on XDA? Sorry for this dumb question :S
On web site of dcunlocker in the tab contact live chat..describe your problem in the tecnichal support..
---------- Post added at 03:40 PM ---------- Previous post was at 03:34 PM ----------
You not have stock recovery..you have twrp and not is possible flash original firmware....is possible to flash boot.img and recovery.img on the fastboot mode,but if you have frp lock this is not possible...only with tool of dcunlocker is possible to install recovery and boot original..after your install full firmware with same tool..
Click to expand...
Click to collapse
Thanks for the input, but I guess this is not my problem. I'm able to flash via fastboot and my FRP is unlocked.
I tried flashing the files from all versions - b145, b303 and b321 (eg. system.img, recovery.img, cush.img and such), but I couldn't get b303 or b321 working again. I end everytime in a boot loop.
Maybe I did something wrong, but that's the reason I restored an old b145 twrp backup.
fbsfelony said:
Thanks for the input, but I guess this is not my problem. I'm able to flash via fastboot and my FRP is unlocked.
I tried flashing the files from all versions - b145, b303 and b321 (eg. system.img, recovery.img, cush.img and such), but I couldn't get b303 or b321 working again. I end everytime in a boot loop.
Maybe I did something wrong, but that's the reason I restored an old b145 twrp backup.
Click to expand...
Click to collapse
Have you tried factory reset then putting a full version of B145 in the /dload/ folder and doing a update through the settings..update..local update
Yes..after you have flashed the file via fastboot write command fastboot reboot..put the full firmware in the folder of dload of internal sd card....press with usb connect of your pc volume up + power and enter in huawei erecovery..press shutdown....disconnect usb...press volume +,volume- and power and release only power after huawei logo..you enter in the upgrade firmware...if flashing block at 90℅ for several minute flashing not is correct..and you need this tool huaweiphonewriterv4 with usb connect to pc for flashing full firmware without error...you have need after flashing via fastboot recovery and boot the wipe data factory reset...try before with wipe data e factory reset in the recovery ..enter in this mode without usb press volume up + power..
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
Check control in device manager of pc..in fastboot mode you have displayed in the samsung android interface driver driver name ADB BOOTLOADER INTERFACE..IS CORRECT DRIVER..in recovery you have driver ANDROID ADB INTERFACE...check the driver correct..is very important for this...not is displayed ANDROID SOONER SINGLE ANDROID INTERFACE..not work correct this driver...check you.
brumgav said:
Have you tried factory reset then putting a full version of B145 in the /dload/ folder and doing a update through the settings..update..local update
Click to expand...
Click to collapse
I tried that, yes. But with no luck; through the settings I can't make a factory reset (it fails after a few seconds), same with the stock recovery. I haven't tried it with TWRP yet, maybe this will work.
And also the method with the dload folder fails - no matter if I do it via the phones settings or when I boot directly into the setup with volume-down and volume-up (where it stops at 90%).
Maybe a full version of b303 or b321 would work, but for now we don't have that yet.
frisko76 said:
Yes..after you have flashed the file via fastboot write command fastboot reboot..put the full firmware in the folder of dload of internal sd card....press with usb connect of your pc volume up + power and enter in huawei erecovery..press shutdown....disconnect usb...press volume +,volume- and power and release only power after huawei logo..you enter in the upgrade firmware...if flashing block at 90℅ for several minute flashing not is correct..and you need this tool huaweiphonewriterv4 with usb connect to pc for flashing full firmware without error...you have need after flashing via fastboot recovery and boot the wipe data factory reset...try before with wipe data e factory reset in the recovery ..enter in this mode without usb press volume up + power..
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
Check control in device manager of pc..in fastboot mode you have displayed in the samsung android interface driver driver name ADB BOOTLOADER INTERFACE..IS CORRECT DRIVER..in recovery you have driver ANDROID ADB INTERFACE...check the driver correct..is very important for this...not is displayed ANDROID SOONER SINGLE ANDROID INTERFACE..not work correct this driver...check you.
Click to expand...
Click to collapse
I guess that's somehow the case - As mentioned above, I already tried to upgrade the firmware with volume-up and volume-down, but it stops at 90%. But I will try it again in the order you said, thanks!
My drivers are all fine, working with them for a while now with a lot of phones and never had problems using fastboot or adb commands (I'm using the ones of the android-sdk) - but you're right, in fastboot it is called "Android Sooner Single ADB Interface". In stock recovery my phone isn't displayed in the device manager of my computer. When I boot up normally with USB-Debugging enabled it is called "Android Adapter ADB Interface".
Honestly I'm a bit concerned about using the said software "huaweiphonewriterv4" - it doesn't seem very
reliable to me
With tool of dcunlocker i have save my device...android sooner single adb interface is not correct driver in fastboot mode...right key mouse in the pc driver device manager,update driver,manually search and toggle compatible driver..list of driver is down of samsung driver..driver correct is adb bootloader interface version with data driver..most recent..accept message of windows driver is not compatible version..install driver..are his the driver correct!!100℅ work...your problem is twrp ..you not have flash right recovery stock..twrp already installed on your device..you must cancel twrp with recovery stock..
---------- Post added at 09:23 AM ---------- Previous post was at 09:14 AM ----------
If twrp start you not have flashedrecovery stock correct....try to flash boot e recovery in fastboot and userdata of the firmware you have in the device before you in bootloop...with correct driver..and after reboot in recovery stock and wipe data factory reset,reboot and try to install firmware in dload..excuse for my english!!
frisko76 said:
With tool of dcunlocker i have save my device...android sooner single adb interface is not correct driver in fastboot mode...right key mouse in the pc driver device manager,update driver,manually search and toggle compatible driver..list of driver is down of samsung driver..driver correct is adb bootloader interface version with data driver..most recent..accept message of windows driver is not compatible version..install driver..are his the driver correct!!100℅ work...your problem is twrp ..you not have flash right recovery stock..twrp already installed on your device..you must cancel twrp with recovery stock..
---------- Post added at 09:23 AM ---------- Previous post was at 09:14 AM ----------
If twrp start you not have flashedrecovery stock correct....try to flash boot e recovery in fastboot and userdata of the firmware you have in the device before you in bootloop...with correct driver..and after reboot in recovery stock and wipe data factory reset,reboot and try to install firmware in dload..excuse for my english!!
Click to expand...
Click to collapse
Ok, I'll try a driver update, thanks
The thing with the recovery - right now I'm on the b145 recovery, but I've tried the b303 and the b321 recovery as well as the TWRP recovery. I just switched between each versions. But I will try the steps you provided, thank you very much!
It's just that I can't make a proper factory reset - it fails after a few seconds, but my phone is then reset. I will try it again with the files (everything I'm able to flash) of the last working firmware - in my case it was b321 before I ****ed up. Again, thanks
You have to access the update menu without a USB cable connected to update via Update file in dload. If you Reboot into Update Mode with a cable connected, your device will go into USB flashmode und will stop at 90%.
Keep pressing vol up + vol down + Power without a cable connected and Release the power button after the Vibration.
frisko76 said:
Yes..after you have flashed the file via fastboot write command fastboot reboot..put the full firmware in the folder of dload of internal sd card....press with usb connect of your pc volume up + power and enter in huawei erecovery..press shutdown....disconnect usb...press volume +,volume- and power and release only power after huawei logo..you enter in the upgrade firmware...if flashing block at 90℅ for several minute flashing not is correct..and you need this tool huaweiphonewriterv4 with usb connect to pc for flashing full firmware without error...you have need after flashing via fastboot recovery and boot the wipe data factory reset...try before with wipe data e factory reset in the recovery ..enter in this mode without usb press volume up + power..
Click to expand...
Click to collapse
If you do it this way, make sure there is no USB Logo in the circle.
yes..is correct..but if you had a b321 before crash you need to download full 321 and extract boot and recovery of 321 with huaweiexctrator tool and flash it in fast boot mode..then upgrade full firmware in recovery..
I have the same issue, i have mate s with tim brand, i change my brand to no brand, i have installed the firmware b114 (first b110) nex b145, and i try to instal mm beta, but installation fail, i try to flash b145 and fingerprint doesn't work. Next i contacted dc forum with live chat, they help me to return at b114, when finished the finger print It has worked well for 15 min and then gave me problems again.
They told me that They do not yet have a solution for people that have upgrate the mate to MM, and must be wait for the official firmware MM for solve that because the beta of MM is not full version
Guys, I did it
I just found a bigger OTA update which allows you to upgrade directly from b145 to b321.
b145 to b321 OTA
I loaded the recovery.img and boot.img of b145 via fastboot on the phone, after that I just put the downloaded zip on my external sd-card in the dload folder, made the update via settings and et voilà, done!
Just quick tested a few things, but everything seems to work.
Defaultuser88 said:
I have the same issue, i have mate s with tim brand, i change my brand to no brand, i have installed the firmware b114 (first b110) nex b145, and i try to instal mm beta, but installation fail, i try to flash b145 and fingerprint doesn't work. Next i contacted dc forum with live chat, they help me to return at b114, when finished the finger print It has worked well for 15 min and then gave me problems again.
They told me that They do not yet have a solution for people that have upgrate the mate to MM, and must be wait for the official firmware MM for solve that because the beta of MM is not full version
Click to expand...
Click to collapse
Maybe you can try to upgrade your phone with the full version of b145, and after that upgrade from b145 to b321.
Thanks everyone!
did you put the complete zip or only update file?
now i'm in b114 but have same feature like multiwindows of next version, i try to flash the full version of 145, first flash recovery and boot but can't install, the phone give me error :/ can't upgrade from b114 to b145
i have followed directions to the best of my knowledge, i had twrp already installed but i wanted to update to 20V i was running 20Q, so i used lgup and did a refurbished option. I am running windows 10, i installed minimal adb, adb recognizes my phone, my phone was unlocked and after doing lg up it stayed unlocked, so i proceed to booting into twrp from fastboot, it does boot into twrp i even installed su V279 and updated it thru google play, my problem is when i go to do fastboot flash recovery xxx.img i get writing recovery failed, even if i flashify it does not install twrp i do get root permission according to su. I havent been able to past that, when i try to reboot into twrp with buttons or application phone shuts down and instead of going to twrp lg logo blinks for a second and then phone restarts to normal operation, what am i doing wrong? i been playing on this for days now, thanks in advance
ps, i even installed the rooted 20V from here still same result, unable to flash twrp
weird but i downloaded twrp for 811-815 thru the phone ap, twrp app and i flashed it with same app and it worked, i have no clue what went on, but i tried different downloads and all fail til just now, thank God!
ok please dont do what i did, twrp did flash but it is for 815, i installed it cause app said it was for both, and it wont let me flash h811 files, will continue to work on it, starting from scratch
beto669 said:
ok please dont do what i did, twrp did flash but it is for 815, i installed it cause app said it was for both, and it wont let me flash h811 files, will continue to work on it, starting from scratch
Click to expand...
Click to collapse
use this one works for both h815-h811 thats waht am using right now..
https://forum.xda-developers.com/showpost.php?p=72468882&postcount=422
as for the recovery.. missing not sure .. but i would KDZ it again and start from scratch using the twrp i gave you in link.
---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------
UPDATE
i just notice your command is worng to send twrp it should be
fastboot boot twrp.img
not
fastboot flash recovery xxx.img
---------- Post added at 09:47 PM ---------- Previous post was at 09:47 PM ----------
UPDATE
i just notice your command is worng to send twrp it should be
fastboot boot twrp.img
not
fastboot flash recovery xxx.img
Thank you for your suggestion i will try after work. I was able to use fastboot boot twrp.img and it load as it should, but my issues is i want permanent twrp, thats why i did the flash recovery
Sent from my LG-H811 using XDA-Developers Legacy app
problem solved, i tried your twrp and had same issue, it will boot but was not writing to phone, i read somewhere, after unlocking the bootloader to save twrp on the phone and then after booting into twrp with fastboot boot twr.img to use twrp file manager and copy from phone to external sd card, i tried that and it worked! now i have permanent twrp. I believe something happens when i tried to copy the file from my computer to my external sd, either my sd card is not working properly and doesnt write everything or some files just dont get transferred cause i copy and paste using file manager app from phone to sd and didnt work. I'm glad i have twrp back in my phone! Thank you raptorddd for helping
beto669 said:
problem solved, i tried your twrp and had same issue, it will boot but was not writing to phone, i read somewhere, after unlocking the bootloader to save twrp on the phone and then after booting into twrp with fastboot boot twr.img to use twrp file manager and copy from phone to external sd card, i tried that and it worked! now i have permanent twrp. I believe something happens when i tried to copy the file from my computer to my external sd, either my sd card is not working properly and doesnt write everything or some files just dont get transferred cause i copy and paste using file manager app from phone to sd and didnt work. I'm glad i have twrp back in my phone! Thank you raptorddd for helping
Click to expand...
Click to collapse
yes you need to have both files i use minimal adb so i place one in that folder and other in external sd .. or internal. then selecting install and lower it says image. then it ask you to select. then select recovery and flash install. and youll have permanent twrp.
could it be that you use USB 3.0 or win10.? i know that for KDZ and LGUP it has problems.. your welcomed you should try G5 port rom from astrako.:good:
the h811 vaariant.
I could have been usb3 as you said I was using Windows 10, I had no problems with lg up though. And sure I will try the g5 port as soon as I get a chance, thank you again!
Sent from my LG-H811 using XDA-Developers Legacy app
Hello guys,
this is my first thread and I have a serious problem:
First, I unlock the bootloader and flash TWRP on it. It seems working, because every time it's booting there comes a message, that I can't trust this device, cause it's unlocked.
The problem is, when i go in fastboot mode, it says "FRP locked") and in the dev-options I can't change the setting (oem unlock). Now when its connected with PC (fastboot Mode), and I try everytime to flash Data there is this error: "FAILED (remote: Command not allowed)"
So...I format all data with TWRP (no OS anymore). Now I know there is no custom ROM for this device out. I was totally fckd up.
I download the update.zip (Stock Rom update) from another Thread and unpack boot.img, recovery.img and system.img from update.app (cause I don't know how to flash it otherwise).
I tried to flash every 3 img. data with TWRP - only the boot.img and recovery.img was installed. Now my device is Bricked because of Im stupid.
So I can only try to flash data with holding vol+ and vol- and power. I also tried eRecovery, but everytime, I tells me that there was a problem by downloading the package.
The fastboot mode is useless, cause there is this bug (read above).
Can you tell me, is there a method to flash update.zip, or another way, or is this device totally broken?
Thanks!!:crying:
Which firmware you had before brick?
MobileTechArena said:
Which firmware you had before brick?
Click to expand...
Click to collapse
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
70X1C said:
I think it was the EMUI 5.0.1 Version (newest) with Android 7.0
Click to expand...
Click to collapse
PRA-LX1?
MobileTechArena said:
PRA-LX1?
Click to expand...
Click to collapse
Exacly
70X1C said:
Exacly
Click to expand...
Click to collapse
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Then try to put UPDATE.APP into dload and do Force update.
70X1C said:
The problem is, that I flash the stock recovery on the device (I have no TWRP anymore)
And there is this problem with fastboot..(read above)
Click to expand...
Click to collapse
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
MobileTechArena said:
Is you FRP locked? Try to unlock bootloader again, fastboot oem unlock "your unlock code". Then try to flash TWRP again. Don't bother with Dload and forced update as that doesn't work.
Click to expand...
Click to collapse
I have no idea of the cause, but dload never worked for me too.
This only works if you can boot to Android and Developer Options menu opens for you (if they don't you'll end up with bricked device).
Boot into the Fastboot mode and relock your device (Command: "fastboot oem relock (unlock code)" ).
Then you'll be able to unlock the OEM Lock from the Developer Options menu. (And after it you can go back to Fastboot and unlock the bootloader again to reinstall the TWRP).
You still need help?
MobileTechArena said:
Download here rescue system file, restore that in TWRP. Then flash stock.boot.img via fastboot flash boot boot.stock.img command , then you can update to B110 OTA.
---------- Post added at 04:18 PM ---------- Previous post was at 04:15 PM ----------
To make TWRP to find rescue files, first backup recovery or something in TWRP, then TWRP will make new folder with backup files that you can raplace with files from rescue system.
Click to expand...
Click to collapse
Where exactly is the rescue system file? I can't seem to find it
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
Looks like they removed it from that site. If i find it somewhere i will share it.
.
MobileTechArena said:
Looks like they removed it from that site. If i find it somewhere i will share it.
.
Click to expand...
Click to collapse
Thanks a lot
theholycutu said:
Where exactly is the rescue system file? I can't seem to find it
Click to expand...
Click to collapse
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
ChinHon said:
https://mega.nz/#!k0MzQL5T!yHj-2n9DuGvb-ZdsemOgw4k3vQTMy7CJXIGFAhJlplo
Sorry I have seen the thread just before.
Please let me know when you downloaded it. I'll take it out again.
Click to expand...
Click to collapse
I downloaded it thanks a lot
:good:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
EXE bahotin said:
please help me. i also have a bricked p8 lite 2017. but i can boot into. TWRP,fastboot,system upgrade
---------- Post added at 10:15 PM ---------- Previous post was at 10:08 PM ----------
man i also have a bricked p8 lite 2017, did you solve your problem? help me please
Click to expand...
Click to collapse
I get ERROR: 255 and I have tried a lot of options and still haven't got to any solutions.. still attempting to solve it, too
MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
hw to install
Waleedaligomaa said:
hw to install
Click to expand...
Click to collapse
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Where L09 ..??
Sent from my MHA-L09 using XDA-Developers Legacy app
ante0 said:
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
That was some journey to the dark side. Welcome back.
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload. Then rebrand back to L29C432 using Hwota. It's currently the only free way of rolling back to Nougat.
ante0 said:
You need to rebrand to AL00C00 to rollback.
In other words, flash AL00 oeminfo.bin, use AL00 dload.
Click to expand...
Click to collapse
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
albertobom said:
I've change some things in system. It's there a problem to use dload if I have change system?
Also I've to have dload on external sdcard right?
So the steps are:
Flash oeminfo.bin info
Then use erecovery and dload right
Click to expand...
Click to collapse
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
ante0 said:
It doesn't check system or any other partition so it will install.
Yes, ext sd:/dload/files from AL00C00(B115 is what I used) dload rar.
Extract dload rar, place all files on external SD in dload folder.
Flash AL00C00 oeminfo.bin. use vol up+vol down+power to boot, make sure USB is unplugged else it will stuck on 5%.
After you will have to rebrand back to L29C432 using HWOTA.
Click to expand...
Click to collapse
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
albertobom said:
So with this Builds I can rollback from Oreo to naught? But my phone isn't listed... European MHA-L29C432
Click to expand...
Click to collapse
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
jaimeguate said:
Why to rollback?
Enviado desde mi MHA-L29 mediante Tapatalk
Click to expand...
Click to collapse
Nothing special really just want to know if I can go back if I have to. ?
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
Oeminfo in this thread: https://forum.xda-developers.com/mate-9/how-to/guide-rebrand-chinese-al00-mate9-to-t3554656 can be restored as a backup. That's probably the easiest way.
Alternative, copy and flash using dd.
cp /external_sd/MHA-AL00C00. bin /tmp/oeminfo.bin
dd if=/tmp/oeminfo.bin of=/dev/block/sdd5
5[Strogino said:
;74268268]MHA-AL00C00B125 - https://mega.nz/#!1853WCAQ!uuCgvn4a7JXHSmEmlBzdMsOOC9vQFJ3WSuMUQI9NDVM
MHA-AL00C00B115 - https://mega.nz/#!88RmjJjA!gGmuc0gL-_sPHOQ0VAXZgTJ3lXmlRRmBqXIYNEyw9XY
MHA-L29C185B186 - http://androidhost.ru/KR
MHA-L29C636B181 - https://forum.xda-developers.com/mate-9/help/bricked-mate-9-help-t3664727/post73988779
MHA-L29C636B122 -
https://drive.google.com/file/d/0BxUuiDq_FRA_cHlHc3BTWEFOUlU/view?usp=sharing
LON-AL00C00B229 - http://androidhost.ru/KZ
LON-L29C432B225 - http://androidhost.ru/L0
LON-L29C185B225 - http://androidhost.ru/L3
LON-L29C636B225 - http://androidhost.ru/L2
LON-L29C721B186 - http://androidhost.ru/L1
Please, make mirror or copy your region ROM to own archive to avoid situation if main source is not available or deleted.
Click to expand...
Click to collapse
Hi bro can you send me oeminfo of chinese version of p8 lite 2017/honor 8 lite????
I want to rebrand my phone
ante0 said:
You extract zip, put contents in external_sd/dload/
then boot using vol up + vol down + power. It's useful if you manage to brick or want to rebrand.
Or want to rollback from Oreo to Nougat.
---------- Post added at 10:54 PM ---------- Previous post was at 10:23 PM ----------
Phew. Thanks to these dload images...
I was going to update to Oreo again to try some stuff to get Magisk running.
I downloaded Oreo Beta from pro-teammt.ru using Linux. Little did I know the update.zip was corrupt (Later I tried downloading multiple times using both browser and wget, different MD5 each time so something is up with my computer).
So I updated like usual using HWOTA. It started installing, I don't know how long it got to, but I was presented with a screen that said PLEASE REDOWNLOAD PACKAGE USING RECOVERY.
So I rebooted. ERROR MODE. Now I'm scared... I googled "Mate 10 release date" just in case, lol.
I rebooted to fastboot mode, thankfully it still worked. I had to unlock bootloader again. Now I tried flashing stock B197 recovery, FAILED: (remote: partition length get error).
I tried the same with boot. Same result.
Then I figured out it probably had the new Oreo partition names for boot and recovery, and thankfully those flashed fine.
So flashed TWRP for Oreo, flashed oeminfo for AL00C00 using dd. Flashed ERECOVERY partitions using dd as well, just in case.
Back to bootloader to unlock again after flashing oeminfo, then flashed back stock recovery_ramdisk.
Then placed dload folder on external sd and booted up using vol up+down+power
Now my Mate 9 is booting up again!
Click to expand...
Click to collapse
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
seniga1 said:
Hi, I'm having a similiar issue. I can't flash any recovery using fastboot (FAILED: (remote: partition length get error). , I'm on emui 5.0.1 android 7.0 (phone works perfectly fine), is possible to flash TWRP recovery using DD? if so, how? it's my first time doing this with a huawei phone and I want to try oreo beta
UPDATE:
Bricked it, can't flash recovery, only fastboot, can't force update neither, any idea?
Click to expand...
Click to collapse
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
flash recovery_ramdisk twrp.img
That did the trick, really appreciated, you'r my new hero :highfive:
Oreo updates
albertobom said:
Thanks my dear friend I'm at beta oreo and it's running amazing but I think I'll have to go back to N so I can make new updates since Oreo doesn't have patched recovery yet.
---------- Post added at 10:41 PM ---------- Previous post was at 10:05 PM ----------
@ante0 where or how do I flash oeminfo.bin? Via twrp? With a flashable zip?
Click to expand...
Click to collapse
You should be able to get updates if you are on the Oreo beta, update checks for stock recovery and won't update if you are on a custom or patched recovery, system update would just see you as updating from beta to release version, beta and release versions are both official ROMs so I don't think you would have any issues with updating as long as the device brand is the same.
plz help sir
ante0 said:
recovery is named recovery_ramdisk on Oreo.
So fastboot flash recovery_ramdisk twrp.img
Make sure you flash twrp from the oreo thread.
If you're on Nougat recovery partition is named recovery, so:
Fastboot flash recovery twrp.img
Twrp is in the regular twrp thread.
You can only use dd in twrp, not using fastboot.
If you tried updating to Oreo I would try both recovery and recovery_ramdisk.
Click to expand...
Click to collapse
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
jaldi said:
I did what you have described above ... flashed oreo twrp successfully but when tried to boot into TWRP it never boots into TWRP ( only a screen appears having three options : 1. Reboot system now 2. Wipe data/factory reset 3. Wipe cache partition.
I'm neither able to perform wipe data/factory reset nor able to wipe cache( it goes to 40% and gives error)
Struck here for more than 15 days...any help will be highly appreciated.
Click to expand...
Click to collapse
You do have Oreo, right?
TWRP should fail to install if you don't have Oreo (unless you're flashing it to recovery and not recovery_ramdisk).
But it sounds to me like it's not installing at all, since you're ending up in stock recovery.
Make sure you use "fastboot flash" , not "fastboot boot"
I have a xiaomi mi 9 but it does not pass the logo of home, it stays there, I do not have the bootloader unlocked so I wanted to know another way to flash it
If flashing is no option for you, you might have to send it in for warranty.
Try XiaoMiTool v2
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
futiless said:
Same problem here; and this tool says fastboot unbrick is not supported yet ... So even though I can flash different twrp builds, it wont get out of reboot to fastboot and no recovery works
Click to expand...
Click to collapse
Did you've tried this lr team twrp:
http://files.mi-room.ru/files/twrp/cepheus/3.3.1-0601/recovery.img
And after flashing twrp, directly with volume up and power reboot in twrp?
Search for vbmeta.img file for mi 9 and flash it
What worked is cepheus_global_images_9.6.27_20190627.0000.00_9.0_global_d1aa19c208 ; then MANUAL usage of flash_all.bat ; then I was able to boot... I think (and don't take my word for it !!) what this is, is encryption lockout. Most XiaomiFlash offical tools were practically useless for the Mi 9 and only finding that exact build (which I figured out wasn't an upgrade like the others with no flash_all.bat, actually ran and it flashed stock and booted me to pincode decryption. After than I was able to use twrp-3.3.1-35-cepheus.img, and get TWRP ... granted it wiped everything. But I booting twrp-3.3.1-35-cepheus also asked for my decrypt key. I think the other TWRP's that don't ask for this while I am encrypted actually corrupted this data... (again maybe i'm wrong) but all in all ... I had a couple hours of slowly building up stress.. cause every recovery I flashed rebooted direct to fastboot. And i'm still not sure why..
Everyone needs to make sure that you can see your full file directory tree before utilizing TWRP commands as if the TWRP install doesn't detect decryption it doesn't discriminate and just overwright and corrupts files... THIS IS WHAT IT SEEMS AT LEAST ...
ALSO big word of warning Global users have to play it safe as it seems our variants is not the one the devs are releasing for ATM. and most things you attempt to flash will cause problems. (AGAIN just my 2 cents not to be taken as fact.) Just a warning... that is it...
---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ----------
emprazol said:
Search for vbmeta.img file for mi 9 and flash it
Click to expand...
Click to collapse
OK what is that file updating over ?
link to the rom you used to fix fastboot brick?? please
I have 9008, can you help me?