Related
I experience the same symptoms as this thread, but the proposed solution does not work for me. (the sd_update.log says
Failure: OSBL°æ±¾Æ¥Åäʧ°Ü.
dload_sd_ram_data_proc->(retry >= DLOAD_RETRY) failed!
Click to expand...
Click to collapse
I rooted the phone, and misread the instructions for altering the recovery.img, which is what caused the problem in the fist place.
I have tried flashing with B925, B927 without luck.
I have also tried to use sudo fastboot boot recovery.img with a local recovery.img, and tried flashing fastboot flash recovery recovery.img - but it says
FAILED (remote: Command not allowed)
Click to expand...
Click to collapse
which i presume is because the bootloader is not unlocked.
I also tried fastboot getvar all - but that came out empty.
I also tried http://androidforums.com/huawei-ideos-x5-u8800/593253-unlock-bootloader-huawei-supply-code.html but the model is not listed...
I have an idea that essentially i just have to get in and delete recovery.img and rename recovery.backup.img to recovery.img - but i haven't got a clue about how to do it.
Phone responds to fastboot commands.
I look forward to your input.
Jonas
[SOLVED] patch to enable B919 was the missing link
Solved: www .shadowandy .net/2013/01/huawei-honor-u8860-shendu-rom-flashing-guide.htm the first link (dload_B929rus.rar (MD5 = 7264f7ad3bd7eebd298a8be978823734)) solved the problems, i am now on a B919 chinese rom.
Hello,
This is my first android tablet and i love it, but i have bricked it, i was messing around with it and i think i wiped it all, at this moment the device is stuck at the mediapad logo, fastboot mode is working but i can not get into recovery.
I have downloaded the two official stock roms mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863 but when i try to do
Code:
fastboot update update.zip
i get the below error:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt]
The zip file contain the dload folder and the update.app file, no .txt files in mention. Any solution to this ?
I have also tried to flash a cwm/twrp recovery (tried many variants) into the device but i can not boot into them (nothing happens, still stuck at the mediapad screen).
Code:
fastboot flash recovery recovery.img
At this moment i have only fastboot available, what can i do to unbrick the device ?
Thanks alot
zertux said:
Hello,
This is my first android tablet and i love it, but i have bricked it, i was messing around with it and i think i wiped it all, at this moment the device is stuck at the mediapad logo, fastboot mode is working but i can not get into recovery.
I have downloaded the two official stock roms mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863 but when i try to do
Code:
fastboot update update.zip
i get the below error:
Code:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt]
The zip file contain the dload folder and the update.app file, no .txt files in mention. Any solution to this ?
I have also tried to flash a cwm/twrp recovery (tried many variants) into the device but i can not boot into them (nothing happens, still stuck at the mediapad screen).
Code:
fastboot flash recovery recovery.img
At this moment i have only fastboot available, what can i do to unbrick the device ?
Thanks alot
Click to expand...
Click to collapse
Use the standard ROM flashing method by copying the update.app into dload folder onto an external sdcard and reboot your device. This ought to work. If it doesn't you've truly bricked your device by screwing up the bootloader.
The only other way if you've screwed up the bootloader is to perform a bootloader unlock using the tool on 4PDA.ru. Google Translate is rather spotty though.
joytest said:
Use the standard ROM flashing method by copying the update.app into dload folder onto an external sdcard and reboot your device. This ought to work. If it doesn't you've truly bricked your device by screwing up the bootloader.
The only other way if you've screwed up the bootloader is to perform a bootloader unlock using the tool on 4PDA.ru. Google Translate is rather spotty though.
Click to expand...
Click to collapse
Will the sdcard method work if i can not boot into recovery ? also, can you point me to that tool ? i can not find it there
zertux said:
Will the sdcard method work if i can not boot into recovery ? also, can you point me to that tool ? i can not find it there
Click to expand...
Click to collapse
Sdcard method is the default update method for Huawei. There is no need to mess with any 3-button combo or hardware.
It is the easiest update method I've seen among the major phone companies.
I will post link to the 4pda tool link later as I am at work now.
Sent from my SM-N9005 using Tapatalk
joytest said:
Sdcard method is the default update method for Huawei. There is no need to mess with any 3-button combo or hardware.
It is the easiest update method I've seen among the major phone companies.
I will post link to the 4pda tool link later as I am at work now.
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I have made a little progress i think, using your post https://forum.lowyat.net/index.php?showtopic=3280093&st=840&p=70452069&#entry70452069 i have flashed the CWM recovery and i am able to boot into it (Chinese XD) and i am using the menu you translated to navigate around, i have put the stock zip that i downloaded and tried to flash the zip file but i got some erros that i did not understand (see attached screenshot)
I have noticed that when i plug the device now into the pc it shows the battery charging (something did not appear before). Also, the sdcard update method is not working (nothing happens, stays at the mediapad logo)
What should i do now ?
screenshot:
http://i59.tinypic.com/29xue0p.jpg
It says cannot open the file.
Just use the normal method of the dload folder.
You have taken a very complex route to solve a simple issue.
Sent from my Mediapad X1 7D-501L using Tapatalk HD
joytest said:
It says cannot open the file.
Just use the normal method of the dload folder.
You have taken a very complex route to solve a simple issue.
Sent from my Mediapad X1 7D-501L using Tapatalk HD
Click to expand...
Click to collapse
I have tried the dload method, i have extracted the contents of the zip file "dloadl/update.app" and put them in a 2GB memory, inserted the momeory inside the device and turned it on but nothing happens, it stays on the logo of "mediapad"
zertux said:
I have tried the dload method, i have extracted the contents of the zip file "dloadl/update.app" and put them in a 2GB memory, inserted the momeory inside the device and turned it on but nothing happens, it stays on the logo of "mediapad"
Click to expand...
Click to collapse
Then it is quite possible your download is corrupted. Try downloading again. And I think the recommendation was to use a 4Gb card.
joytest said:
Then it is quite possible your download is corrupted. Try downloading again. And I think the recommendation was to use a 4Gb card.
Click to expand...
Click to collapse
Ok, will re download and try with a 4GB memory stick, what about the bootloader unlocker that you mentioned ? do we still need that ?
zertux said:
Ok, will re download and try with a 4GB memory stick, what about the bootloader unlocker that you mentioned ? do we still need that ?
Click to expand...
Click to collapse
Just to clarify, my device is 7d-501u so i will have to download this http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 right ?
zertux said:
Just to clarify, my device is 7d-501u so i will have to download this http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 right ?
Click to expand...
Click to collapse
Yes you have to download the correct ROM for your device. 501u is the 3G version.
joytest said:
Yes you have to download the correct ROM for your device. 501u is the 3G version.
Click to expand...
Click to collapse
so i have downloaded http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 and it still gives me the same error in the screenshot, how can i get the correct firmware for my device ? (on the back of the device its written 7D-501u )
zertux said:
so i have downloaded http://www.emui.com/nsp/geturl.php?path=7D-501u_EMUI_2.0_V100R001C233B019.zip&rid=560 and it still gives me the same error in the screenshot, how can i get the correct firmware for my device ? (on the back of the device its written 7D-501u )
Click to expand...
Click to collapse
As far as I know, you downloaded the 501u version. Perhaps the last resort is to enable the CWM to allow ABD sideloading?
Or, you can try this "unlock bootloader" from 4PDA
http://4pda.ru/forum/index.php?showtopic=564429&view=findpost&p=34341371
It seems you just need to run the exe file. You can try this since nothing else works for you.
Appreciate if you report on the success.
joytest said:
As far as I know, you downloaded the 501u version. Perhaps the last resort is to enable the CWM to allow ABD sideloading?
Or, you can try this "unlock bootloader" from 4PDA
http://4pda.ru/forum/index.php?showtopic=564429&view=findpost&p=34341371
It seems you just need to run the exe file. You can try this since nothing else works for you.
Appreciate if you report on the success.
Click to expand...
Click to collapse
I will try the bootloader unlocker when i get home, i have tried 4 official roms for the 3G and 4G and i get this error
http://tinypic.com/usermedia.php?uo=adkBqYNLlttp9d8/5vW/a4h4l5k2TGxc
Can you tell me what does it say ? Also hoq can i re install the stock recovery of the device ? Maybe it will work ? I flashed it and installed wcm.
Update: i have downloaded the bootloader unlocker but its all in Chinese! any help is appreciated.
Update2: The bootloader is already unlocked, when i run
Code:
fastboot oem get-bootinfo
it says unlocked. however the device is not taking any rom that i try to install to it (errors in Chinese). i have extracted the system.img, boot.img and recovery.img from the update.app package, i will try to flash them into the device one by one with fastboot.
FIXED!
So for anyone who ran into the same problem, here is how i fixed it:
1. Downloaded the 7D-501u official stock ROM mentioned in this post http://forum.xda-developers.com/hua...rom-official-huawei-mediapad-x1-b007-t2811863
2. Used Huawei update.app extractor tool from http://forum.xda-developers.com/attachment.php?attachmentid=2822142&d=1403960391
3. Flashed boot.img, recovery.img and system.img
Code:
fastboot flash recovery RECOVERY.img
fastboot flash system SYSTEM.img
fastboot flash boot BOOT.img
Rebooted and it worked! the bootloader comes unlocked by default (at least for my model). Special thanks for joytest for his help.
Hello. I'm crazy. I deleted stock recovery original for my 7D-503L 4.2.2 (B008). The problem was install the stock recovery 4.4 kit Kat for error. I installed again the rom B008 and anything. Is impossible to find the stock recovery original and one CWM for my device. Somebody can I help me please? Somebody know where lies the stock recovery? I know is independently of the Rom.
Regards
Soft Brick: Stuck at Huawei logo and unbale to Boot/access Recovery.
=> Install the Universal Android USB Driver from the link below:
http://adbdriver.com/upload/AdbDriverInstaller.exe
=> Download and install ADB and Fast Boot from thebelow link.
http://fs1.d-h.st/download/00103/KIP/adb-setup-1.2.exe
=> Extract the Stock ROM using the Tool "Huawei Update Extractor" in the computer.
=>"HuaweiUpdateExtractor download link:
http://dl.xda-developers.com/attachd....7.9_Setup.zip
=> Copy and paste the Stock/TWRP Recovery and BOOT.img in the "ADB and Fast Boot" folder.
=> Connect the HAM to the computer using the supplied USB cable.
=> Press and hold the Power and Volume Down button.
=> HAM will be recognized as ABD device.
=> Leave the Power and Volume Down button.
=> Double click to open the installed "ADB and Fast Boot" from the Desktop or open the computer prompt to access the "ADB and Fast Boot" folder.
=> In the ADB and Fast Boot prompt:
=> Type: fastboot reboot-bootloader.
=> Type: fastboot flash BOOT BOOT.img
=> Type fastboot flash RECOVERY RECOVERY.img
Fastboot will flash the image and give you a success/failure notification. If successful, you're all set.
Finally, press and hold the Power button. HAM will boot now
fastboot: that's the executable tool
flash: that's the function we want the fastboot tool to perform
recovery: this is the name of the partition we want to flash into. since we are flashing a recovery image, it needs to go to the recovery partition.
recovery.img: this is the name of the actual file to flash. Your file name may be different. Just make sure it matches the actual file name.
@eennap. Ok tomorrow I will to try.
Thanks and Regards
I have a bricked (7D-501L).
1 .
I download a ROM «Huawei_MediaPad_X1_7D-501L_V100R001C170B001_Android_4.2_Russia».
I unzip ROM into root sdcard.
I use Huawei update.app extractor tool, and extract from ROM «boot» and «recovery» partitions.
I flashed a «boot» and «recovery» partitions via fastboot (from it ROM).
After, I use the standard ROM flashing method. The device start flashing, but after a few minutes the device reboot.
ROM not installed, the device not start.
2.
I download a ROM OTA_7D-503LV100R002C208B002.
I extracted this ROM, and flashed a BOOT.img, CACHE.img, CUST.img, RECOVERY.img, SYSTEM.img, USERDATA.img partitions via fastboot.
The device started, but after a few minuts my device reboot to black screen FASTBOOT.
What can i do to unbrick the device ?
P.S.: sorry for bad English
how can i make update.zip from update.app?
my device not flashing standard method.
I can flash it from recovery. I need update.zip
Please, help me
I seemed to have either bricked my 7840 or at the least it is stuck in a bootloop. It will startup with the Intel Inside logo and then just keep restarting over and over again. I can't get the recovery screen or anything. I've tried a few guides to unbricking on here but it doesn't stay on long enough to have files written to it.
Anyone have any advice on what I need to do?
BrettOutlaw said:
I seemed to have either bricked my 7840 or at the least it is stuck in a bootloop. It will startup with the Intel Inside logo and then just keep restarting over and over again. I can't get the recovery screen or anything. I've tried a few guides to unbricking on here but it doesn't stay on long enough to have files written to it.
Anyone have any advice on what I need to do?
Click to expand...
Click to collapse
Check my post.
http://forum.xda-developers.com/dell-venue/general/7840-freezes-tethered-cwm-bricked-t3171803
If you can stay on fastboot mode (power button+volume down), theoretically you can unbrick the device.
I actually did try that yesterday but I'll fiddle with it more over the weekend. Thanks!
bootloop help and reference links for Dell 7840 files
brettOutlaw or Wonglynn2004,
Did you have much success fixing the boot-loop? I was able to get my tablet rooted with social design concepts' droidboot files (1,2,3) and to unlock the bootloader, but managed to screw up my system to the dell boot-loop screen, by either installing busybox or erasing the wrong partition when trying to use Aparted on a 64gb card to get ext4.. At this point I still had access to CWM tethered.
I made it worse after flashing the ..BB.XML file below and I saw the blue USB image briefly, but still have fastboot. Fastboot screen details listed below as well as links to files and thread references. I hope I got all the references & source credit correct.
After using the flash_DDO_BB.xml to reset, and erasing for a clean start I no longer can get CMW tethered to work. The T4 Trigger has some write error / access problem. With fastboot I hope I can get this working again with some minimal help here. I am using an older Toshiba Win8 tablet and not sure about getting ADB fully setup. I used the Minimal ADB -Fastboot installer to fix an older TF700 (old asus transformer).
There were some suggestions for using dd to copy from the SD card to the System partition, but I don't know if ADB will work, or just fastboot commands in the current condition.
Does anyone have time for step by step instructions either using the Phone flash tool, or if I have to setup ADB and use dd to copy the boot.img and system.img?
I have the link at the end for someone with success using DD to copy from SD to the system partition. Thank you for any help or suggestions between the multiple sources below or order for applying Phone flash files.
-mrgardiner
Can someone make a Sticky for boot-loop resources for the Dell Venue 7840?
1. Phone Flash tool and which files to flash
2. social-design-concept and vampirefo for root process and Trigger T4.
3. xBIGREDDx boot.img and system.img files (dd copy vs phone flash tool)
4. Developer files from Dell.
5. anggusss OTA update.zip 5.1
6. Root files Droidboot
7. minimal ADB - Fastboot installer
OTA update.zip for 5.1 from anggusss
venue_8_7840_lollipop_OTA.zip
http://forum.xda-developers.com/showpost.php?p=60632439&postcount=21
Developer edition files from Dell:
http://opensource.dell.com/releases/Venue_8_7840_Moorefield/developer-edition/5.X/
xBIGREDDx system and boot img files
http://forum.datadevelopement.com/showpost.php?p=61173058&postcount=5
system.img: https://mega.co.nz/#!w9AjBCSI!YdQenTLDVVk0M9xx1LJT1OnKq5VhESgiyULA1FVIA8A
boot.img: https://mega.co.nz/#!Fk4FUSza!1gY1RjvnEI_HS0zk17WTHiywXFWc1VOCH-P2V5fVFPI
Someone with success using dd to copy above files:
http://forum.datadevelopement.com/d...-8-7840-developer-files-posted-t3144232/page3
Dell Flashphone tool:
https://01.org/android-ia/downloads/intel-phone-flash-tool-lite
http://forum.xda-developers.com/dell-venue/general/venue-8-7840-developer-files-posted-t3144232
venue_7840_droidboots.zip
https://mega.nz/#!E1oijRRC!U8MK5s8q0TPzWJPNoM9sHxfxjvGcF_sk20SN5YfAqzA
Tethered Temporary Recovery from Social designs vampinfo
https://www.androidfilehost.com/?fid=23991606952604606
Chainfires UPDATE-SuperSU-v2.46.zip
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1
USB drivers from INTEL
https://software.intel.com/android/articles/intel-usb-driver-for-android-devices
Minimal ADB-Fastboot installer:
http://forum.xda-developers.com/showthread.php?p=42407269#post42407269
Current fastboot screen info:
PRODUCT_NAME - BB
Variant - Venue 8 7840
HW_Version - unknown
Bootloader Version - unknown
IFWI Version - E004.F601
Serial Number - XXXXXXXXXX
Signing - unknown
Secure_Boot unknown
Made some progress
1. Went back to the earlier firmware without locked device.
venue_7840_droidboots.zip and used Phone flash tool with this ‘1-502_droidboot_and_firmware.xml’
2. used updated IntelAndroid-FBRL-07-24-2015.7z and got CWM back
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
3. Stuck trying to use ADB or fastboot, or CWM to load the boot.zip or boot.img and system.zip or system.img. CWM didn't recognize external SD after mounting. MIght have to be ext4 format?
mrgardiner said:
Made some progress
1. Went back to the earlier firmware without locked device.
venue_7840_droidboots.zip and used Phone flash tool with this ‘1-502_droidboot_and_firmware.xml’
2. used updated IntelAndroid-FBRL-07-24-2015.7z and got CWM back
http://forum.xda-developers.com/android/development/intel-android-devices-root-temp-cwm-t2975096
3. Stuck trying to use ADB or fastboot, or CWM to load the boot.zip or boot.img and system.zip or system.img. CWM didn't recognize external SD after mounting. MIght have to be ext4 format?
Click to expand...
Click to collapse
Use Minimal ADB-Fastboot installer for boot.img.
I have tested and working.
Thank you,
I am stuck at 5.02. I get the OTA notice, but on reboot it hangs or does not load. After normal rebooting, it will ask to download the OTA again.
I went through a few combinations of droid boot 501, 502 and 5.1. At one point I had
'Encryption failed", but going back to the older droid boot worked. I have the OTA.zip, but I am not sure if it is possible to dd the sys.dat. An older thread said no go.
http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
Have you been able to get to 5.1 from dd an older system.img? I am not sure if I need to do a deeper formatting than enzymeyllw's post.
I see they replied to just flash the OTA in CWM. I will unroot and try that again. I don't remember the exact error code.
mrgardiner said:
Thank you,
I am stuck at 5.02. I get the OTA notice, but on reboot it hangs or does not load. After normal rebooting, it will ask to download the OTA again.
I went through a few combinations of droid boot 501, 502 and 5.1. At one point I had
'Encryption failed", but going back to the older droid boot worked. I have the OTA.zip, but I am not sure if it is possible to dd the sys.dat. An older thread said no go.
http://forum.xda-developers.com/dell-venue/general/7840-succeed-to-unbrick-t3205024
Have you been able to get to 5.1 from dd an older system.img? I am not sure if I need to do a deeper formatting than enzymeyllw's post.
I see they replied to just flash the OTA in CWM. I will unroot and try that again. I don't remember the exact error code.
Click to expand...
Click to collapse
same thing happen to me. I use CWM to flash OTA.zip and end up with error 01.
hello
my device has suddenly got stuck on the Google logo and wont boot normaly, i have no idea what to do.
please help
Nexus 9 WiFi'
** edit: i was trying to install a stock lolipop using Nexus Tool Kit and these are the resault many errors and mainly this error "out of memory"...
i would provide a pic but i cant upload due to the span prevention system in the forum...
Hard to say for sure what happened, but I can say it is always best to stay away from a toolkit as problems like this arise all too frequently
So long as your bootloader is unlocked flashing a factory image is the best choice
https://developers.google.com/android/nexus/images?hl=en
If you need a hand setting this up let me know
Best of luck
hey many thanks for the kind offer to help, i've been trying to flash a new factory image but no luck, i keep getting an erot while flashing [something about too many links or not enough memory], i'll provide a pic soon.
edit: i ran the flash-all script as instructed in the link you gave me, ended up with these errors: [i cant attach a pic since im a new user, system alert]
update package missing "system.img"
"archive does not contain "boot.sig"
"archive does not contain "recovery.sig"
in other case the fastboot froze [on the tablet] and an error popped up in the terminal "out of memory"
Try erasing and flashing partitions separately
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
Now
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
Just unpack the .zip you downloaded and you'll find another zip with all these files
Some more help can be found here
http://forum.xda-developers.com/showthread.php?t=2277112
demkantor said:
Try erasing and flashing partitions separately
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
Now
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
Just unpack the .zip you downloaded and you'll find another zip with all these files
Some more help can be found here
Click to expand...
Click to collapse
thanks, but when i was trying to format i got this error:
FAILED (data transfer failure (too many links))
every fastboot command i run fails for this reason.
when i try again to format the operation crushes.
just found a pic from other tread in this forus so i could add it, i have the same errors.
http://forum.xda-developers.com/attachment.php?attachmentid=2790293&d=1402378385
Shouldn't get that error when erasing, try updating your fastboot binary on PC, maybe also try another USB cable
demkantor said:
Shouldn't get that error when erasing, try updating your fastboot binary on PC, maybe also try another USB cable
Click to expand...
Click to collapse
can you please tell me how to do that? i tired several cables and ports, same error every time.
Guessing you are using windows? If so the best way is to have the android SDK downloaded and update through the available ui
More detailed instructions are available from the fastboot link I sent earlier
But the error you are getting is almost always a bad USB cable or port, at least whenever I have troubleshot that error with others that's what turned out to be the fault
demkantor said:
Guessing you are using windows? If so the best way is to have the android SDK downloaded and update through the available ui
More detailed instructions are available from the fastboot link I sent earlier
But the error you are getting is almost always a bad USB cable or port, at least whenever I have troubleshot that error with others that's what turned out to be the fault
Click to expand...
Click to collapse
Well yes i do use android SDK and its always up to date, i really dont understand the cables and port i have been using are all good since i use them with other devices too, i really dont know what else i should do...
one more thing, when trying to format boot and data i got this error:
formatting is not supported in filesystem type "raw" [something like that]
what does this mean?
edit: i was able to flash the system. boot, cache and recovery but the tablet still stuck on google logo
edit #2: i wasnt flashing correctly, i used the flash all script and it ran flawless, the tablet has booted and its faster then ever! i have another shot to a cable and port i still didnt use
and now its working, i cant thank you enough!
EladC said:
Well yes i do use android SDK and its always up to date, i really dont understand the cables and port i have been using are all good since i use them with other devices too, i really dont know what else i should do...
one more thing, when trying to format boot and data i got this error:
formatting is not supported in filesystem type "raw" [something like that]
what does this mean?
edit: i was able to flash the system. boot, cache and recovery but the tablet still stuck on google logo
edit #2: i wasnt flashing correctly, i used the flash all script and it ran flawless, the tablet has booted and its faster then ever! i have another shot to a cable and port i still didnt use
and now its working, i cant thank you enough!
Click to expand...
Click to collapse
How were you not flashing correctly?
I had the same issue.
Go into fastboot and flash the vendor.img
fastboot flash vendor vendor.img
Flashing the vendor.img actually did it - I followed the explanations above and was still stuck at the Google screen.
Formatting and flashing the following finally did the trick:
fastboot format system
fastboot format cache
fastboot format data
fastboot format recovery
fastboot format boot
(the three above failed due to an unsupported file system which didn't make a difference in my case)
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash data data.img
fastboot flash cache cache.img
fastboot flash vendor vendor.img
I have a Nexus 5X but it was the same issue when trying to flash LineageOS 14 after using Android 8.
I downloaded the vendor image from the official Linage OS thread and that fixed it. Only command I had to run was "fastboot flash vendor vendor.img". I did a factory reset with TWRP before booting though.
Problem already solved. Thanks!
Hi everyone, this is Sarry. I got my new huawei mate 9 pro on Wednesday this week, the version is LON-L29C636, I was trying to flash a custom ROM into the phone, but unfortunately I was too careless, flashed a different version ROM into it and cause immediate start up loop. As I finally boot into fastboot and twrp rec mode, I noticed that the computer won't recognize the USB portal of the device. So I went in eRecovery mode and tried to download an updated version but it failed to find any useful version.
Since mate 9 pro doesn't support SD card, I brought a USB-OTG cable and also usb type-c microSD adapter, when I connected the sd card to the phone, twrp reads the information, but when I tried to flash the update.zip file, it failed. I tried to copy the dload folder with update.app by twrp into phone storage, even if I got successful, the file just disappeared when i refresh the page. So now I don't have any idea on how to unbrick the phone, felt really bad.
Feel free to ask me any question or information needed, I really hope to unbrick the phone, I've been using huawei cellphone for more then 2 years and love it very much. Thanks for the help!!
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
TheShadowMC said:
Hello,
well the situation isn't that hard actually, you may just get the stock image and flash it from fastboot then start the custom rom installation from scratch.
what is the error number or statement?
EDIT: you will need huawei update extractor to pull out the img files and flash them through fastboot
Another Edit:
in the file path choose the update.app
you will need the following partitions:
Boot
System
Recovery
^select these then right click and press `extract selected` and flash them using the following commands:
1- fastboot devices > to check the device
2- fastboot flash boot boot.img
3- fastboot flash recovery recovery.img
4- fastboot flash system system.img
hope this helps you
good luck!
Click to expand...
Click to collapse
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
However what error does it give during flashing system.IMG I would like to know, also as well as twrp custom ROM flashing?
Aquarius_2333 said:
Thank you so much for the help! The fastboot script isn't really working because when I tried to run it in cmd, it shows 'error can't find device', so I tried to flash the img files with twrp, the boot.img and recovery.img works well, but the system.img cannot be flashed, and the error message shows 'E:\cannot flash system.img'. I also tried to download the full version firmware and created dload folder in my SD card, copied UPDATE.APP into the folder, tried the 3 button force update, still nothing worked. Now the seller send me an Email said I can return the product, they are going to charge me for some ROM re installation fee.
Click to expand...
Click to collapse
well brother about the driver issue, sorry about being late, you must have downloaded the fastboot drivers and installed them.