Hi there! So, I unlocked my bootloader yesterday and I've been trying to install a custom rom, no luck at all, it doesn't boot. It just stays in a bootloop. I think that's because I wiped the system and data instead of just wiping data then performing a factory reset, how it told me in the installation guide. Now, I have a european EVA-L09 with a unlocked bootloader and TWRP installed. What can i do to get it boot up? Thanks in advance
Try with HWOTA by installing the same stock ROM you had before messing up
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Btw, Huawei portal for Bootloader codes was down for days - was it up now again or you paid for DC Unlocker
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
zgfg said:
Try with HWOTA by installing the same stock ROM you had before messing up
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Btw, Huawei portal for Bootloader codes was down for days - was it up now again or you paid for DC Unlocker
Click to expand...
Click to collapse
I paid for DC Unlocker. I'll try it out. Ummm, I bought mine from UK, what version should I get? I had the latest EMUI 5.0.1 (Naugat 7.0) Stock ROM. It was my mistake that I didn't backed it up, had no storage left on my SD Card... Stupid me
fler_tb said:
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
Click to expand...
Click to collapse
Hi there! I'll try it out!
fler_tb said:
If u can boot device to fastboot, you can flash boot.img, recovery.img system.img and cust.img trough command prompt to boot up phone. Previously extract those 4 files from update.app with Huawei Update Extractor.
Click to expand...
Click to collapse
Code:
C:\Users\Whiskey\Desktop>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (449861 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 20.379s
well, this is what happens...
BlazedMC said:
Code:
C:\Users\Whiskey\Desktop>fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' (449861 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 20.379s
well, this is what happens...
Click to expand...
Click to collapse
Sorry for late answer. Maybe your bootloader is locked so you can't direct flash it trough fastboot...?!
fler_tb said:
Sorry for late answer. Maybe your bootloader is locked so you can't direct flash it trough fastboot...?!
Click to expand...
Click to collapse
I solved it a long time ago, the same day. Thanks anyway!
BlazedMC said:
I solved it a long time ago, the same day. Thanks anyway!
Click to expand...
Click to collapse
How did you??
Related
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S:
L10-B602
L00-B607
L07-B607
L10-B609
L10-B613
L10-B621
L10-B805
L10-B813
L10-B815
L10-B817
L10-B830
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Thanks for sharing man. I appreciate it!
Ziolek67 said:
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S (B602, B607, B609, B613, B621, B805, B813, B815).
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Click to expand...
Click to collapse
Thanks Ziolek. Any possibility to have the B8xx stock update.app?
v11lemans said:
Thanks Ziolek. Any possibility to have the B8xx stock update.app?
Click to expand...
Click to collapse
And the B8xx stock flashable file? :victory:
And so we can flash any recovery of the B609 to get the stock recovery? Right?
Ziolek67 said:
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S (B602, B607, B609, B613, B621, B805, B813, B815).
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Click to expand...
Click to collapse
Dude, you have to check your files.... I am trying to flash the B813 and B805 recovery but both dont boot at all.... Led flashing red and blue and then i get the white boot failed screen
Flashed with flashify and rashr
I used that files. Everything was ok. But I don't us flashify. Only fastboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Ziolek67 said:
I used that files. Everything was ok. But I don't us flashify. Only fastboot.
Sent from my HUAWEI P7-L10 using Tapatalk
Click to expand...
Click to collapse
Hmm weird... Maybe flashify and rashr dont work on lollipop... Have to get to a pc nearby to flash.
Sent from my HTC One using XDA Free mobile app
its the peanut said:
Hmm weird... Maybe flashify and rashr dont work on lollipop... Have to get to a pc nearby to flash.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
I have tested B813 kernel and recovery now and it is working properly.
I Flashed it by fastboot and system booting.
I haven't now possibility to checking B805 files because I am on B813 system now.
Maybe try to re-downloading package.
Does anyone have any idea if it's possible to flash a recovery without fastboot even when you can't boot into the os? Right now I can't do anything with my phone...
My pc doesn't recognise my phone in fastboot mode but, it does recognise adb but, only when I try to flash something (hold vol-+ and put in usb cable). If anyone is able to help me please say it...I've got a thread named phone bricked good somewhere on this forum (ascend p7 general).
Thanks in advance and sorry for the trouble
sincerly,
Jules
Ziolek67 said:
Here you are most of EMUI 3.0 and 3.1 recoverys and kernels extracted from appropriate ROM'S (B602, B607, B609, B613, B621, B805, B813, B815).
In some folder there is more than one RECOVERY.IMG (differently named) because it was backed up by thirst party applications (f.e. Rash.apk or Flashify.apk).
Click to expand...
Click to collapse
Do you have recovery stock of b830?
Updated
target reported max download size of 536870912 bytes
sending 'boot' (8026 KB)...
OKAY [ 0.319s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.329s
whats problem here
abumaha said:
target reported max download size of 536870912 bytes
sending 'boot' (8026 KB)...
OKAY [ 0.319s]
writing 'boot'...
FAILED (remote: Command not allowed)
finished. total time: 0.329s
whats problem here
Click to expand...
Click to collapse
Google it
Hi all,
I'm trying to understand what did I do wrong.
I bought my device with an unlocked bootloader miui V8 (global rom).
I tried to flash TWRP recovey and MIUI PRO rom. I follow the steps that are mentioned here
and got soft brick - the device got stuck on the mi logo (with the unlock sign), even when I wait in patience the device just turned off.
- At the beginning I flashed the TWRP recovery by xuefer, boot into it and flashed the dm-verity disabler (as mentioned in the guide) and got error 1.
I reboot the device and it didn't boot.
- I boot to the recovery again and wipe the data - didn't boot.
Boot to recovery again and wipe to factory
-I flashed the MIUI PRO rom and the device still didn't boot.
I tired to flash the TWRP recovery by iscle - now the dm-verity disabler succeed but the device still didn't boot.
made the wiping steps as above again - and the device still got stuck at the mi logo.
At any step I manged to boot into the TWRP recovery and fastboot mode.
My lest option was to go back to the global stock rom using MiFlash
Now I'm on Global MIUI 9 with locked bootloadr
What did I do wrong?
I want to unlock the bootloader and to get back my control on my device.
Please advice
Thanks
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Thank you all for your answers!
Thank you all for your answers!
ekin_strops said:
Download the latest TWRP on this forum. Flash it. After, go to twrp, wipe data, cache, flash MIUI PRO rom, and after flash also flash the latest SuperSU zip. Then try again and see if it's gonna boot up.
Click to expand...
Click to collapse
This is exectly what I've done. and I't didn't worked.
Can you please point me to exact TWRP that you meant?
What about the dm-verity disabler ? it isn't necessary?
ondoy1943 said:
how sure were you that the device had an unlocked bootloader when you purchased it? if it was brand new, certainly its bootloader is locked.
Click to expand...
Click to collapse
I've checked the bootloader status in the Dev menu and with fastboot (fastboot oem device-info).
In addtion to all I had the open padlock sign when the turned on the device.
lightman33 said:
Do you have an open padlock when your phone is booting ?
Remember to boot to twrp just after flashing and before booting to the rom.
Click to expand...
Click to collapse
I had the open padlock sign.
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
I want to know the mistake I've done - so I don't fail with it again after I'll get the approval to open my bootloader.
Thanks
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
lightman33 said:
no mistake, they are three batches files in the rom zip. One of them is relocking the bootloader.
Flash_all with without erase data
Flash_all with wipe data
Flash_all with relock bootloader
I don't know miflash interface but you unfortunately choose the third choice. You need now to unlock your bootloader again (maybe by creating a new xiaomi account, not sure of this).
Click to expand...
Click to collapse
I'm sorry if you miss understood me, but I meant to the mistake I've made with the TWERP and rom flashing.
I can't figured out what I've did wrong.
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
lightman33 said:
Sorry if was not clear but the problem could be here :
Now unfortunately I flashed with MiFlash the global rom and my bootloader is locked.
II think you choose in Mi Flash tool an option to flash with re-lock the bootloader (don"t know how it's designed in the app because I flashed my phone manually, using one of the 3 batch files).
Hope it will help you.
Click to expand...
Click to collapse
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
I took the TWRP from this forum, this is my md5 if you want to check yours :
f52ff052971b67df097d4cfa8a2ec162 twrp-3.2.0-0-oxygen.img
And this is my howto :
$ sudo fastboot flash recovery twrp-3.2.0-0-oxygen.img
target reported max download size of 536870912 bytes
sending 'recovery' (16196 KB)...
OKAY [ 0.504s]
writing 'recovery'...
OKAY [ 0.095s]
finished. total time: 0.600s
$ sudo fastboot boot twrp-3.2.0-0-oxygen.img
downloading 'boot.img'...
OKAY [ 0.487s]
booting...
OKAY [ 0.576s]
finished. total time: 1.063s
For the ROM, I took file here : http://bigota.d.miui.com/7.12.8/oxy....8_20171208.0000.00_7.1_global_93a8045184.tgz
Filename : oxygen_global_images_7.12.8_20171208.0000.00_7.1_global_93a8045184
From forum : http://en.miui.com/thread-1273027-1-1.html
and the command to flash was (after unzip the file) :
$ sudo ./flash_all_except_storage.sh
Beginning of the log :
product: oxygen
erasing 'boot'...
OKAY [ 0.027s]
finished. total time: 0.027s
erasing 'sec'...
OKAY [ 0.021s]
finished. total time: 0.021s
target reported max download size of 536870912 bytes
sending 'crclist' (0 KB)...
OKAY [ 0.040s]
writing 'crclist'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'sparsecrclist' (0 KB)...
OKAY [ 0.040s]
writing 'sparsecrclist'...
Hope it will help you...
ymca said:
Thank you for your answer.
I will open my bootloader,
I'm just trying to understand which TWRP version to flash for the miui pro rom (or any other)
And what is the process (or "the correct steps") to :
* Flash the TWRP recovery
* And to flash any other different rom from the miui stock.
Thanks
Click to expand...
Click to collapse
Hi! As others have already told you,
What I would do is to completely format the phone with Mi Flash (download the latest global stable fastboot version from http://en.miui.com/a-234.html), then flash it to the phone using the Flash All option, then flash my recovery or the one from xuefer (the one you prefer, both work), if you are flashing miui pro I think there is no need to flash the dm-verity file, so just wipe system + data + cache and flash miuipro.zip
Thank you all for your replais !
I will try and update right after I'll get the bootloader unlock approval.
Meanwhile you all have a great day !
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
virusdunil said:
Do you still have access to ADB/Fastboot ?
if yes then maybe try flashing main img files like kernel ect.
if no fastboot,i really dunno mate
Click to expand...
Click to collapse
I can have the phone in fastboot and run adb reboot bootloader and it says no devices found although the huawei HiSuite can detect the device being plugged in as it loads up when I plug the phone in
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
virusdunil said:
Try that...extract KERNEL from update.app....
in fastboot mode,adb : fastboot flash kernel KERNEL.img
se if this work...
Click to expand...
Click to collapse
Not going to lie I am slightly out of my depth here, could you explain that further? I'm assuming I need to download an update.app but I have no idea where from or extracting the kernel from it
thanks
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
virusdunil said:
well,you have to dload the same firmware you have on your device...
is it the Oreo from the debrand/rebrand thread ?
if not ,go on teammt and dload your firmware...keep it somewhere safe
open update.zip and extract it...theres an update.app in there.
get the Huawei upade.app extractor here on XDA just type it in search bar or google it...
open the extractor you just dloaded and clik on settings tab...untick the Veryfy the checksum box and save...
click on extract tab and at far right of Update file box,clik on the .. box to search for your update.app you unzipped
if everything done correctly,all files will apperar...
now just right clik on KERNEL.img and select Extract selected.....................................or you can extract all and save them somewhere safe.
after you extracted the image, you have to put the KERNEL.img in your ADB folder in order to flash it
hope it helps
Click to expand...
Click to collapse
That Didn't work i just got:
C:\Users\jamie\Desktop\platform-tools>fastboot flash recovery KERNEL.img
target reported max download size of 471859200 bytes
sending 'recovery' (24576 KB)...
OKAY [ 0.528s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.537s
im assuming its due to the bootloader not being unlocked. and in the meantime im running a deepscan on my hard drive to see if I can recover my unlock code which was lost when cloning to a new ssd. It has a few hour left though
you have it wrong...
its fastboot flash kernel KERNEL.img
virusdunil said:
you have it wrong...
its fastboot flash kernel KERNEL.img
Click to expand...
Click to collapse
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
virusdunil said:
well......
last try would be to install android studio and sdk tool here
i couldnt flash SYSTEM.img with normal adb... but succeeded with the sdk tool so.....
be patient,its long to install...
Click to expand...
Click to collapse
I have android studio, how do I flash the img with it?
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
virusdunil said:
mine got installed in c/user/you/appdata/local/android/sdk/platform tools/
adb should be there...put your .img file there and open comand window ...like other adb
Click to expand...
Click to collapse
exactly the same :
C:\Users\jamie\AppData\Local\Android\Sdk\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.533s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.542s
Is it maybe worth seeing if I can get the serial number product emei and product id without the os?
Jyndon said:
same thing happened anyway:
C:\Users\jamie\Desktop\platform-tools>fastboot flash kernel KERNEL.img
target reported max download size of 471859200 bytes
sending 'kernel' (24576 KB)...
OKAY [ 0.526s]
writing 'kernel'...
FAILED (remote: Command not allowed)
finished. total time: 0.534s
Click to expand...
Click to collapse
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
kwaichang said:
I would say, you did something wrong, maybe false folder, false command or what ever.
If you get access via adb it should work.
Click to expand...
Click to collapse
I don't know that I do have access though as the device doesn't appear in adb devices list and the bootlaoder is locked.
Although I think I may have found a way of flashing a new bios without bootloader by using the huawei recovery installation.
The default one that uses wifi obviously doent work because its crap but while the device is off I can hold vol+ vol- and power and it loads into an installation screen that shows installation failed but i found that it maybe possible to flash the bios this way by putting the update.app onto the sd card. However the problem I'm having is that windows says the file is too big to copy and unzipping it inside of the sd card doesnt work either. Any ideas as to how I might be able to do it like this? (similar to this: https://android.stackexchange.com/q...are-installation-failed-error-when-booting-up and this too https://forum.xda-developers.com/p9-plus/help/software-install-failed-updating-p9-t3587676)
SOLVED
I managed to get most of the information to unlock the bootloader from the box which I luckily kept, then for the product ID I used https://imei24.com/warranty_info/Huawei/865545034273084/ and it worked perfectly!
Bootloader unlocked and then I used the common HWOTA to rebrand it back to its original firmware.
Thanks to those who helped.
Jyndon said:
So I was trying to restore my rooted p10, I first tried using a twrp restore which didn't work then nothing would boot, so then I decided to reflash the ROM but the software I tried using relocks the bootloader then unlocks it again. So now what I have is my p10 with no custom recovery, a locked booloader and no working os installed. And as I cant boot the phone I cant get the information to get the code to unlock the bootloader. Any one have any ideas that doesn't involve paying for DC unlocker.
thanks
SOLVED: I found the imei on the box and unlocked the bootloader with that info.
Click to expand...
Click to collapse
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
AjSri110 said:
bro how did you unlock locked bootloader after factory reset and soft bricked after twrp and unrooted , erecovery loop just by using imei code ???
Click to expand...
Click to collapse
I know this is late but none the less, using the emei code I was able to request my code to unlock the bootloader through hwota. You cannot request this code anymore a way so you have to pay for dc unlocker which can rip the unlock code from the device.
petr.hybler said:
any update guys? I have the same situation ... erecovery loop with fastboot/adb not available (no device) ...
Click to expand...
Click to collapse
Is your bootloader unlocked?
If not you have your bootloader unlock code?
If not then you will need to pay for some software to get that code.
From there you can unlock the bootloader and use adb/fastboot again
Hi all,
I have an incorrect firmware installed for my P10 and lots of things are not working (oreo 8.0). I want to re-flash or rollback to other firmwares but problem is I can't get into TWRP anymore. flashing it doesn't work and although I see in fastboot Phone Unlocked and FRP unlock i have the idea it has to do with the OEM unlock not working properly. It's also not available in the developer options. What;s exactly the link to huawei's page where you can request your phone unlock ID ?
Thanks
Whats not working ?
What is it saying when flashing something through fastboot ?
virusdunil said:
Whats not working ?
What is it saying when flashing something through fastboot ?
Click to expand...
Click to collapse
When I go into the bootloader and want to flash TWRP I get following message:
target reported max download size of 471859200 bytes
sending 'recovery_ramdisk' (16494 KB)...
OKAY [ 0.552s]
writing 'recovery_ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.566s
What is the ADB command youre using ?
virusdunil said:
What is the ADB command youre using ?
Click to expand...
Click to collapse
fastboot flash recovery_ramdisk twrporeo.img
and my twrp oreo name is twrporeo.img
Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img
virusdunil said:
Thats why its not working...
TRY....... fastboot flash ramdisk twrporeo.img
Click to expand...
Click to collapse
Same problem...:
C:\Android>fastboot flash ramdisk twrporeo.img
target reported max download size of 471859200 bytes
sending 'ramdisk' (16494 KB)...
OKAY [ 0.532s]
writing 'ramdisk'...
FAILED (remote: Command not allowed)
finished. total time: 0.546s
i did a mistake...its really recovery_ramdisk
Look Here...
TWRP
virusdunil said:
i did a mistake...its really recovery_ramdisk
Look Here...
TWRP
Click to expand...
Click to collapse
I already tried that but no success. Did a factory reset and now the bootloader is locked again. How can I unlock the bootloader again?
Thanks
1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?
virusdunil said:
1-is your phone working now ?
for bootloader unlock,do what you did first time... fastboot oem unlock yourcode123
how did you get the last update ?....firmware finder ?
Click to expand...
Click to collapse
First of all, I've tried to update from Nougat to Orea via Blackballs method in this thread https://forum.xda-developers.com/p10-plus/development/oreo-update-thread-l29c432-t3729907 with the firmware mentioned there
What is not working:
I've managed to do the first part (oreo install), but:
- SImcard has 'No service
- Can't flash TWRP
- Bootloader / phone locked in Fastboot
- I can't remember how I unlocked the P10 last year (I have a P10 L09-VTR, rebranded to L29-VTR and now 'working' on a VKY P10 plus rom)
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
I need help :'(
I had that.
Phone was completely dead, needed a new board.
chrissyyyw said:
I had that.
Phone was completely dead, needed a new board.
Click to expand...
Click to collapse
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
benkiller47 said:
Are you sure of it ? did you buy it ?
You succefuly booted to twrp and tried to flash ROM ?
Because i used ADB command PUSH and managed to get ROM into /data/ folder in my phone , so i'm trying to flash them but it's not working at the end i reboot to fastboot
DId that happen to you too ?
Click to expand...
Click to collapse
I booted into fastboot, flashed the individual firmware files and it kept failing on the vendor.
I had a black screen with a red flashing LED on reboot. I claimed on my insurance and they replaced the board on the phone.
I checked on here and online for a resolution and it generally points to a hard brick.
benkiller47 said:
Hi guys , i was running AOSIP PIE rooted and bootloader unlocked. I did an update of Magisk. And then i couldn't flash twrp it was not working , i could still boot phone normally and phone run smooth. Someone told me to flash TWRP with flashify and i did. Here the problems started , i started having error , can't boot anywhere etc...
I followed this tutorial https://forum.xda-developers.com/hua...g-to-t3932203/ for last solution .
But unfortunatly i can't flash VENDOR.img in fastboot , i can flash all except VENDOR.img it says
C:\ADB>fastboot flash vendor VENDOR.img
target reported max download size of 471859200 bytes
sending sparse 'vendor' 1/2 (460796 KB)...
OKAY [ 10.697s]
writing 'vendor' 1/2...
FAILED (remote: Command not allowed)
finished. total time: 10.711s
I have flashed with success TWRP twrp-3.3.1-0-charlotte , i can get to it but there is no files inside the phone and it's not supporting SD cards to i don't have any ROM to flash ...
Do you guys have any idea about what to do ?
Thank you very much
Click to expand...
Click to collapse
You must use OTG! Probably Flashify borked a partition,but i don't think it borked vendor.
However, you should still be able to flash a FullOTA with TWRP + NoCheck combo.
If you can't manage that, hit me on Telegram,i'm @Pretoriano80 in there!
You can flash EMUI based FW using an OTA method. It should work. But it will lock your bootloader and you will have to unlock it again.
benkiller47 said:
Hi
Click to expand...
Click to collapse
Are you flashing the same or later firmware??