Hi guys,
It's been the hole day now struggling trying to solve my bootloop. Could someone help me?
This morning I had 170B with root and I decided to put the new 330B.
So I flashed with ADB the files extracted from the original 121B package: BOOT.IMG, CUST.IMG, RECOVERY.IMG, CACHE.IMG AND SYSTEM.IMG.
Everything fine with the exception of SYSTEM.IMG: - error: cannot load 'system.img' -
So I tried with the version 100B but same problem.
I cannot more go inside the bootloader even if I flash the TWRP back. I tried running cmd as administrator and I also tried to add -S 512M when flashing.
I searched in the hole WWW but coulnt find anything that solves my problem...
Thanks for the attention
Fuserr
EDIT: solved
Related
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
maybe you should tell more info about your device, brand,chipset, etc ?
so people can be more easy to help.
just newbie suggestion, ignore this if its no help xD
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
lolet said:
Looks like your system image file is corrupted cause its not mounted after loading kernel. What kind of filesystem the image is using?
Click to expand...
Click to collapse
The system image is not corrupted, because I can safely flash it using Clockworkmod. The filesystem is yaff2, and I have tried opening it using some software and my file is there. I think the problem lies on fastboot who failed flashing properly.
simple
yokowasis said:
Hi,
I have flash system.img file by using
Code:
D:\ADB\Android>fastboot flash system d:\backup\flash\system.img
sending 'system' (116302 KB)...
OKAY [114.524s]
writing 'system'...
OKAY [ 47.582s]
finished. total time: 162.108s
It seems normal to me, but the problem arise when I restart the the phone. The phone unable to boot, and when I try
Code:
ADB Shell
It says somethings like "sh" is not found. So I do reboot recovery go to the shell and mount /system. Shockingly there is nothing in there.
I have checked the contents of system.img, and there is a lot of things in there, including the "sh". But it seems fastboot failed to flash the system partition.
Anyone can help me ?
Click to expand...
Click to collapse
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
I stuck with my Mate 9 Error mode numbers 11 and 2
MEGHSHAH said:
ur work is simple...just plug in ur phone in fastboot mode...keep a boot.img file in the same folder that that of the fastboot folder....boot.img can be taken from ur STOCK ROM
and type ==
fastboot devices
then ur device will be shown.....
then type
fastboot flash boot boot.img
n its done!
Click to expand...
Click to collapse
I would like to tell you my problem, I have a Mate 9 MHA-L09C605B111 which I did a rebrand a while ago and I'm with CUST 432 and installed the version of Oreo 8.0.0.368, a few weeks ago I received the update 369 via OTA. It was interesting to try; the problem is that I had open bootloader, TWRP Pretorian 3.2.0 and Root, take a terrible decision to do a relock of the bootloader.
After several attempts and letting the battery drain I could enter Fastboot mode, I have the FRP unlocked and I could unlock the bootloader again, the problem is that I can not enter either the TWRP, or to recovery mode, try flashing again the same TWRP I had installed it well but still when I want to enter after passing the Huawei logo it remains on the white screen of ERROR MODE, Func NO: 11 (recovery image) Error NO: (image Failed!) Reading other forums and looking I have been told a lot by Internet that it is necessary to make the Dload method try it but it did not work, I understand that it does not work in this model but I still try it.
I also did a flash with all the files as I found in a tutorial
"When you have system extracted, flash it in fastboot using fastboot flash system system.img.
Do the same with KERNEL, extract and flash to fastboot flash kernel KERNEL.IMG
(BOOT is now split into RAMDISK and KERNEL)
Recovery was split to recovery_ramdisk, recovery_vendor and recovery_vbmeta
Boot was split into ramdisk and kernel
Recovery2 (erecovery) was split into erecovery_ramdisk, erecovery_kernel, erecovery_vendor and erecovery_vbmeta
fastboot flash ramdisk ramdisk.img. Kernel flashed as fastboot flash kernel kernel.img.
Recovery ramdisk as fastboot flash recovery_ramdisk recovery_ramdisk.img "
I'm still stuck on the same screen with error 11 and 2 I made the flash of the recovery that I used when I put version 368 are two MHA_RECOVERY_NoCheck.img and MHA_RECOVERY2_NoCheck.img both give Failed using the command Fastboot flash recovery_ramdisk RECOVERY_XXXX with both the same without using the _ramdisk command is equal I'm still stuck in the same state.
Does anyone have an idea that another method I can try?
I will thank you very much.
You can flash all * .img through ADB and in this case there is a specific order to do it, check several threads but I did not get an answer and search but I could not find anything, it is worth noting that when I flash files I mentioned before all OKAY but on power up it goes back to error 11 and 2 I have been told that it is a partition problem but I could not find something to recover them, there is some method that is missing or maybe an error in the steps I am doing ? I still can not access the TWRP but I can access without problems by ADB.
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.
I recently tried extracting my samsung stratosphere 2's stock recovery but it seems as if it is corrupt. This is odd because i can easily boot into recovery mode, but i cant extract a working recovery. There are no problems when I enter the command to grab it. It comes out as exactly 10 mb and so does my boot.img. The recovery is located in
mmcblk0p18. I found this info here: https://github.com/ameer1234567890/OnlineNandroid/wiki/Supported-Devices . I tried making it into a zip file also by entering
#cat /dev/block/mmcblk0p18 > /sdcard/recovery.zip but I cant successfully open or extract the archive.
I'm wondering maybe their info is incorrect, im extracting the wrong block, or if im entering the wrong commands? Yes I am rooted and am using su permissions.
Here are the files
recovery.img https://dl.dropboxusercontent.com/u/71816133/recovery.img
recovery.zip https://dl.dropboxusercontent.com/u/71816133/recovery.zip
and the block information is in the attatchments
Any help is much appreciated!
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.
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Flash stock rom lenovo k5
try turning off your internet connection and flash sorry for my inglis I'm using google translate
Nox.BG said:
Hello!
Posting here because the model doesn't have its forum.
My phone is currently unlocked with phh-trebmble android 9 and the rom has rather crucial problems - apps crashing, no auto brightness, unable to connect to networks with hidden SSID and some more.
Unfortunately I cannot find a guide showing a working method [atleast for my case] to flash the stock rom.
I got the stock rom from firmwarex .net and tried flashing it with QFIL. At first the program couldn't locate a usable file for the "programmer path". After seeing multiple guides for the program I saw that everyone is using the same file "prog_emmc_firehose_8936.mbn" so I got the file, placed it in the rom folder and selected it from the QFIL. When i start the download proccess it returns Sahara error so I am unable to complite the recovery.
As it is somewhat scuffed method with spare parts from here and there could anyone point me to somthing that I am missing or doing wrong.
P.S. Phone is in download mode when I'm trying to flash trough QFIL, QFIL is seeng the phone on the port.
Click to expand...
Click to collapse
I'm stuck on the "fire hose" file. QFIL seems to not detected the phone.
Did you managed to solve the problem?
Lenovo K5 Pro ROM
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
ShmuelCohen said:
After flashing IMG file (using TWRP 3.3.1) the phone (Lenovo k5 pro) always starts in bootloader mode. Everyone can help?
Click to expand...
Click to collapse
Did you get any solution, I have the same problem.
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
help me what is the correct file to download to flash android 10 on lenovo k5 pro. Gapps and custom rom please help. Im stock the google pixel logo boot screen for almost an hour.
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.
shisho585 said:
Thank you so much for this post.
After many many many attempts to repair my device through qfil without success, I tried what you wrote in the post and thank God I finally succeeded so thank you very much.
However for some reason I can not update the system version because he thinks I have root, no matter what I did I could not fix it.
Any ideas?
I also wanted to ask, for what should a userdata partition be flashed? It is always built on its own. I'm wrong?
Click to expand...
Click to collapse
.
iugleafar said:
Resuscitated my K5 Pro, thank you very much your comment saved me!:victory::victory:
Click to expand...
Click to collapse
anonym34 said:
Instead of using qpst I solved this by using a qfil unsparse tool which made a single raw image file of system.img, vendor.img and userdata.img and I then used img2simg to make sparse images of the newly created files that I flashed using the command:
fastboot flash system system.img
and so on with vendor.img, boot.img, cache.img and userdata.img (in my case i had overwritten vendor files) from platform-tools.
Click to expand...
Click to collapse
.