Related
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.
Huawei recently shipped update B180.
They advised to unroot the phone first, but I have been stupid and updated with TWRP installed on the second recovery partition (e-recovery?) and the update failed.
My phone now won't boot. I can put it in fastboot/recovery mode and access TWRP, so I guess all I need is a stock ROM.
I cannot find anything useful for Honor 7 with Google, I would like a recent ROM (most recent I found is a B130).
I would also appreciate some advice on how to recover from this boot freeze.
Would flashing a stock ROM with TWRP be enough?
Thank you very much.
I'm kinda pissed since that phone is quite expensive.
You cannot flash a stock rom with TWRP.
You have to flash the stock recovery then a stock rom, using fastboot.
The more recent stock rom available is the B130, unfortunatly.
Have a look at my posts, I have done similar (although I had the normally recovery.img installed) you need to downgrade using the marshmallow downgrade ROM then to the full 121 or 130 ROM after putting the stock recovery back (for the version your phone was on before this happened I assume it was 170 if you were going to 180) once you are back on 130 you can then upgrade up to 180 through the usual process. I have done this a few times and it has been fine whilst experimenting with the device.
The current version of the phone appears to be burned in to it (I think curver.img is doing this inside the UPDATE.APP but I haven't found a way of flashing this file back to the phone to play around with downgrading without the MM downgrade ROM), this I think is what causes it to hang if it has a boot.img and recovery.img that does not match the version the phone thinks it is.
I am in the same boat with @rbuccia.
I can only access fastboot and recovery (twrp).
I also found that I must have something wrong with 3rdmodem because if i wipe form inside twrp I always get an error message on that partition.
Also I have a rom from Kangvip flashable with twrp but veven this has no effect.
I think that we cannot unbrick it without a completely and full stock rom but I think there is no one.
Any idea?
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
james194zt said:
This method should work for the above, first we need to get your device to boot. The following should work... Extract UPDATE.APP from the B180 ROM and then extract boot.img and recovery.img using Huawei Update Extract. Now extract the UPDATE.APP from the full 130 ROM and extract system.img using the Huawei image extractor. Once you have them 3 files, place them in the same folder as your fastboot installation and do the following...
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
This should give you a working bootable phone, it will be a mess half 180 for Kernel etc... and the system itself will be 130 but it should boot. Then place the MM downgrade ROM into the dload folder on your SDCARD and run the update process, it will crash at 95% this is fine the phone will boot back up. Now place the UPDADTE.APP from 130 in the dload folder and run the update again, this should flash and give you a fully functioning normal system running version 130, then follow the update process to get back to 180.
The modem will get flashed as part of the 130 update package so hopefully that will resolve that issue for you as well.
Click to expand...
Click to collapse
Thanks for the tips, but
1. Where can i download the B180 full firmware?
2. I can't access the VOL+ VOL- POWer AKA updater mode, it just bootloops.
Thx :laugh:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
james194zt said:
Its on one of the threads at the top of General all the firmwares are there, no you don't need to do the vol+/- thing, just power power it down and then hold power up whilst plugging in to your PC. If this works the device will load up in fastboot and you should be able to flash what you need, to do the above the bootloader will need to be unlocked but you can do that from fastboot.
If your device is in a boot loop plug it in via USB to your PC and keep holding the volume up and when it reboots eventually it will go in to fastboot.
Click to expand...
Click to collapse
I must be blind, but i can only find the ota updates, not the full stock firmware :/
Thx tho, i'm starting to understand a bit better how it works and how i can fix it.
I'll just try to flash boot and recovery for B100 and B130 untill i cant make it work, for the system.app tho i can't take the B180 as i can't find it.
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
james194zt said:
You need to use the system.img from B130 it is located here https://mega.nz/#!PlpXnLxD!azPTqEscNnwuSdrjpJJKO9zkyCpzAl7d6w3OpYx1se8 once you have this follow the above process and you should end up with a phone thats working and has the correctly matching firmware. Make sure you do it all though, just because it will boot with a mismatched boot loader and system.img doesn't mean you should keep it that way, it could be unstable and will cause issues with future upgrades.
Click to expand...
Click to collapse
Thx for the reply ! But that's what i said earlier, when i flash boot.img, system.img and recovery.img from the B130 update.app, the phone still bootloops.
I have access to the Huawei E-recovery if i do VOL+ POWER while the phone is plugged in the pc
I have access to the fastboot mode if i do VOL- POWER while the phone is plugged in he pc
I DON'T have access to the software mode upgrader if i do VOL+ VOL- POWER, no matter is the phone is plugged in or not
The phone still bootloops, plugged in or not.
:/
You need to flash boot.img and recovery.img from 180 and system.img from 130, sorry if that was not clear above! the boot loop is being caused because the boot.img doesn't match the version your phone thinks its on, if 180 doesn't work try the version before you upgraded i.e. 170 the system.img is just the android OS if you see HONOR glowing then you are booting system.img at that point but if it isn't glowing then you are still in the bootloader at that point so you need to sort out boot.img.
I've never been in 180, and as i said, i can't take the boot and recovery.img from the OTA update, i need a full stock firmware of B180 ! :/
Thx for the help tho.
I already tried to flash boot.img from B100 b121 and B130, and the phone still bootloops :/
http://forum.xda-developers.com/hon...dating-to-b180-fastboot-t3317249#post65420964
This fixed it!
Found this and it worked for me.
Download latest Official Full ROM from EMUI's site, HuaweiUpdateExtractor and adb / fastboot.
2. Unzip ROM and open UPDATE.APP with HuaweiUpdateExtractor.
3. Extract SYSTEM.img and RECOVERY.img (delete .header files that HuaweiUpdateExtractor generates you need only .img files) and put them in adb folder.
4. Boot in fastboot and conect to PC. (You can achieve this from TWRP to boot to bootloader, adb dosent work but fastboot will there is also key combination to get to bootloader/repair mode or what it is).
5. Open cmd.exe from adb folder and type (or copy-paste) the follow commands one by one:
Code:
fastboot devices
Code:
fastboot flash recovery RECOVERY.img
Code:
fastboot flash system SYSTEM.img
And finally where i had some trouble:
If you got no permissions try again or take usb cable off etc. Took me while to get back from same situtation. Few reboots to TWRP and to bootloader and USB replugging while in bootloader.
And for LINUX: i used split_updata.pl-master from github to extract the .APP/Firmware needed to sudo fastboot aswell.
Hiiiii guys
Please help me respected sir and other friends.
Anyone have twrp backup of stock rom ?
Because I want go back to stock rom and I have only twrp not pc please thanks in advance
Hi,
I have bricked my Honor 5x after flashing custom recovery. This these the steps I followed:
1) Unlocked the bootloader
2) Flashed TWRP recovery
3) Flashed root
4) Tried to update OTA
Now the phone is stuck at boot screen. I can enter recovery by pressing volume down and power, but now is stock recovery. And I don't know what to do.
Can someone help me?
OK u can't OTA update with twrp AND U SHOULD try adb flashing twrp through fastboot and maybe restoring a nandroid if u have one if not there's some u can download around here
Hey, my phone is bricked too. How did you manage to flash adb during twrp. How did you restore the backup and where did you get it from?
Or could someone please explain to me how I can get back to stock. I saw one thread with the .app file, but there you had to go the setting or something, which I can't do.
I have twrp installed and I have the L21 version.
Ok, I figured it out. I took the backup and the instructions from this thread: http://forum.xda-developers.com/honor-5x/development/unrooted-stock-rom-t3308902
heinzwilli6 said:
Hey, my phone is bricked too. How did you manage to flash adb during twrp. How did you restore the backup and where did you get it from?
Or could someone please explain to me how I can get back to stock. I saw one thread with the .app file, but there you had to go the setting or something, which I can't do.
I have twrp installed and I have the L21 version.
Click to expand...
Click to collapse
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
Download Huawei Update Extractor
http://d-h.st/wwfQ
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
After that you should be back on stock firmware
I tried to do that too. But the problem was that my adb didn't recognize my phone. Of course I had everything installed.
When I unlocked the bootloader earlier, it worked. But there I had to enable USB debugging. When my phone was broke, I couldn't enable it. Maybe that's why?
However, my phone is working right now, so thanks anyway.
fixed
jperez1132 said:
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
Download Huawei Update Extractor
http://d-h.st/wwfQ
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
After that you should be back on stock firmware
Click to expand...
Click to collapse
I have a practically dead honor 5x, flashed a L-24 firmware on L-22. TWRP doesnt let me do anything, no touch functions work so i cannot restore my back up.
Fastboot commands on format /data and flash cust cust.img fail with the error "Remote: Command not allowed", bootloader is unlocked, pls help.....I need to flash back the default cust.img to get it back to normal
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
nandakalyan said:
I have a practically dead honor 5x, flashed a L-24 firmware on L-22. TWRP doesnt let me do anything, no touch functions work so i cannot restore my back up.
Fastboot commands on format /data and flash cust cust.img fail with the error "Remote: Command not allowed", bootloader is unlocked, pls help.....I need to flash back the default cust.img to get it back to normal
SOLVED: Downloaded the official firmware, placed the "dload" folder which contains the update.app in the root of the sd card, went into download mode on phone (vol up + vol dow + power) and the system installed the firmware automatically.....booted back into the stock system now, next will reflash TWRP and restore back up
Click to expand...
Click to collapse
WORKED: update.app in dload folder WORKED !!! Thanks a lot
narengowda said:
WORKED: update.app in dload folder WORKED !!! Thanks a lot
Click to expand...
Click to collapse
Glad it worked! did you figure out what caused the issue?
jperez1132 said:
I was able to get my phone back to stock using the update.app file and the Huawei Update Extractor
Download stock firmware and extract the update.app file
http://forum.xda-developers.com/honor-5x/development/repository-honor-5x-file-depot-t3328288
Download Huawei Update Extractor
http://d-h.st/wwfQ
Use the Huawei Update Extractor to open the update.app file and extract system.img, Cust.img, boot.img, recovery.img
Copy the extracted files to your adb folder
Connect the phone to the PC in fastboot mode, to do this power off the phone hold Volume down and insert a usb cable connected to the PC
Type these commands on ADB:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot
After that you should be back on stock firmware
Click to expand...
Click to collapse
Is your fingerprint ID working good?
---------- Post added at 09:14 AM ---------- Previous post was at 08:46 AM ----------
fastboot flash cust CUST.img
target max-download-size: 254MB
sending 'cust' (196335 KB)...
OKAY [ 6.493s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.493s
Cant flash cust. How did you do that?
sad1996 said:
Is your fingerprint ID working good?
---------- Post added at 09:14 AM ---------- Previous post was at 08:46 AM ----------
fastboot flash cust CUST.img
target max-download-size: 254MB
sending 'cust' (196335 KB)...
OKAY [ 6.493s]
writing 'cust'...
FAILED (remote: Command not allowed)
finished. total time: 6.493s
Cant flash cust. How did you do that?
Click to expand...
Click to collapse
Yes, it is working perfectly.
Hi, sorry for hijacking a thread but I thought it'd be better than making a new one.
I did pretty much the same as the OP, unlocked the bootloader, flashed TWRP recovery, rooted and then stupidly tried to do an official update on the phone (I believe it was kiw-l21c432b140)
The phone is just now stuck at the boot screen, I can get into fastboot mode but cannot use ADB, says device isn't found no matter what I try. I also tried putting stock firmware on the SD card and going into download mode (EMUI) but it just says software install failed.. Any help appreciated, only got the phone today and have spent longer trying to fix it than I have using it..
Thanks!
tomblast66 said:
Hi, sorry for hijacking a thread but I thought it'd be better than making a new one.
I did pretty much the same as the OP, unlocked the bootloader, flashed TWRP recovery, rooted and then stupidly tried to do an official update on the phone (I believe it was kiw-l21c432b140)
The phone is just now stuck at the boot screen, I can get into fastboot mode but cannot use ADB, says device isn't found no matter what I try. I also tried putting stock firmware on the SD card and going into download mode (EMUI) but it just says software install failed.. Any help appreciated, only got the phone today and have spent longer trying to fix it than I have using it..
Thanks!
Click to expand...
Click to collapse
As long as you are able to boot into fastboot you still have hope
Are you able to get into TWRP? (Power + Vol up) If yes, download the L-21 stock rom in the file repository thread and flash it. In all likelihood, that will solve any corruption of system files. If not, read on.
Did you check if you have installed the ADB drivers? I am assuming it should have been installed considering you flashed TWRP, but better to check and reinstall. Device not found is usually a driver error. Alternatively, you can install HiSync, it refreshes and replaces the drivers needed for Honor 5X. Further to installing that, try adb fastboot commands and flash the stock recovery using the steps in this post:
http://forum.xda-developers.com/showpost.php?p=65659088&postcount=5
nandakalyan said:
As long as you are able to boot into fastboot you still have hope
Are you able to get into TWRP? (Power + Vol up) If yes, download the L-21 stock rom in the file repository thread and flash it. In all likelihood, that will solve any corruption of system files. If not, read on.
Did you check if you have installed the ADB drivers? I am assuming it should have been installed considering you flashed TWRP, but better to check and reinstall. Device not found is usually a driver error. Alternatively, you can install HiSync, it refreshes and replaces the drivers needed for Honor 5X. Further to installing that, try adb fastboot commands and flash the stock recovery using the steps in this post:
http://forum.xda-developers.com/showpost.php?p=65659088&postcount=5
Click to expand...
Click to collapse
When I do power and vol up I get EMUI recovery, not TWRP I put the stock rom on the SD card and tried to install it and it just says "Software install failed" and the only option is to shut the phone down again.
I had all the ADB drivers installed, will reinstall it all and see if it helps. When I run adb now and use the "adb devices" command it just says "List of devices attached" and doesn't show anything..
tomblast66 said:
When I do power and vol up I get EMUI recovery, not TWRP I put the stock rom on the SD card and tried to install it and it just says "Software install failed" and the only option is to shut the phone down again.
I had all the ADB drivers installed, will reinstall it all and see if it helps. When I run adb now and use the "adb devices" command it just says "List of devices attached" and doesn't show anything..
Click to expand...
Click to collapse
Oh then you have stock recovery, are you using the update.app provided by Huawei? Or using any ROMs/images posted here? It is possible that you may have a corrupted download, look up the Huawei site for downloads in the support section for your region and download the official update.app, try with that
nandakalyan said:
Oh then you have stock recovery, are you using the update.app provided by Huawei? Or using any ROMs/images posted here? It is possible that you may have a corrupted download, look up the Huawei site for downloads in the support section for your region and download the official update.app, try with that
Click to expand...
Click to collapse
It wasn't stock recovery before, after the phone updated it went back to stock and wouldn't boot. I downloaded the firmware from http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 and that's what I try to install through recovery and it says there's an error, a load of other texts flashes up before it says error but it's too quick to read. When I have better internet I'll re-download it in case it was corrupt. Thanks for your help, hopefully I can get it fixed as I only just got this to replace my old phone. Would be a shame to spend the money on it and have no use from the device.. Just wish the computer would detect through adb as I can get into fastboot easily enough.
tomblast66 said:
It wasn't stock recovery before, after the phone updated it went back to stock and wouldn't boot. I downloaded the firmware from http://forum.xda-developers.com/honor-5x/development/stock-kiw-l24-l21-t3312684 and that's what I try to install through recovery and it says there's an error, a load of other texts flashes up before it says error but it's too quick to read. When I have better internet I'll re-download it in case it was corrupt. Thanks for your help, hopefully I can get it fixed as I only just got this to replace my old phone. Would be a shame to spend the money on it and have no use from the device.. Just wish the computer would detect through adb as I can get into fastboot easily enough.
Click to expand...
Click to collapse
Sure, we all help each other
BTW, just to be sure, you using the single "Update.app" file, that runs into a couple of gigs or the extracted one? You can't flash extracted Update.app through stock recovery.
HiSync (the official Huawei tool) also provides an option to recover the phone, tried that?
nandakalyan said:
Sure, we all help each other
BTW, just to be sure, you using the single "Update.app" file, that runs into a couple of gigs or the extracted one? You can't flash extracted Update.app through stock recovery.
HiSync (the official Huawei tool) also provides an option to recover the phone, tried that?
Click to expand...
Click to collapse
It's the single one, about 2.66GB I believe, I tried the recovering through the Huawei tool and it says "Your device is not supported for system recovery".
tomblast66 said:
It's the single one, about 2.66GB I believe, I tried the recovering through the Huawei tool and it says "Your device is not supported for system recovery".
Click to expand...
Click to collapse
Oops! I am no techie, so am at the end of my wits, but thing I do suspect is a corrupted download, so if you can try downloading the file again from a stable connection and try is all I can think of. I've had this corrupted file thing quite a few times, so suggesting.
Hey,
I wanted to do a nandroid backup so I did adb reboot recovery to go to TWRP, now I can't boot into system, I'm stuck in twrp, I can't even power off the phone it keeps booting up again and again. Please help i'm really lost. Thanks
I did boot to System but with another key combinaison (volume down + power) , I think it's all messed up and the phone thinks that the recovery is the default boot option.. idk how to change this
Nexx_ said:
I did boot to System but with another key combinaison (volume down + power) , I think it's all messed up and the phone thinks that the recovery is the default boot option.. idk how to change this
Click to expand...
Click to collapse
If you can reach the stock recovery, just put update.app file and install it. If you can't, try to flash boot.img and recovery.img manually. After that, try to install rom again.
memht said:
If you can reach the stock recovery, just put update.app file and install it. If you can't, try to flash boot.img and recovery.img manually. After that, try to install rom again.
Click to expand...
Click to collapse
Okay thank you, I will try flashing them manually because I have twrp
@DigiGoon Please can you help me with it?
You were on which system? Stock or any Custom ROM?
DigiGoon said:
You were on which system? Stock or any Custom ROM?
Click to expand...
Click to collapse
I was on stock b371
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
DigiGoon said:
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
Click to expand...
Click to collapse
Thank you a lot for helping me I'll try to follow the process as soon as I get windows on my Mac
@DigiGoon No need to flash system.img actually Just cust, boot and recovery is enough (i think). I forgot to tell cust but it's not necessary always.
memht said:
@DigiGoon No need to flash system.img actually Just cust, boot and recovery is enough (i think). I forgot to tell cust but it's not necessary always.
Click to expand...
Click to collapse
The way his phone is acting, system is the main thing he needs to flash.
Same kind of problem different dude
DigiGoon said:
Okay follow these step, if you don't understand any step ask again. But follow these:
Download the UPDATE.APP of the Build number you were on before.
Extract system.img, boot.img, recovery.img, cust.img from that UPDATE.APP
Flash all these files via bootloader mode, to boot into bootloader mode, once a loop is over and you see blank screen on your phone, quickly press Vol DOWN button and while pressing it connect your phone to a PC. If this doesn't work and you get into recovery, then in recovery go to option Reboot, in that select Bootloader.
Once in bootloader mode, flash these files by firing these commands from a CMD, make sure files are situated in the same location where you open up the CMD.
Code:
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash cust cust.img
fastboot flash boot boot.img
Now after your phone boots up normally, put the same UPDATE.APP from which these files were extracted in dload folder of your external SDcard.
Now switch off your phone and press all the three buttons(Vol UP + Vol DOWN + Power) simultaneously.
Flashing process will start.
Hope this helps.
Click to expand...
Click to collapse
I'm having similar problem as OP. I get access to TWRP(by holding power+vol up), but not fastboot anymore. My TWRP is in chinese and but I found the reboot menu and the alternatives are: System, Power Off, Recovery and Download. I think i've tried them all and none of them brings me fastboot. I went into loop when I tried to install SuperSu through TWRP on stock rom. Is there hope? Yesterday I managed to get into fastboot, but can't remember what I did. I heard something about draining the battery and then theres hope?
mosoo said:
I'm having similar problem as OP. I get access to TWRP(by holding power+vol up), but not fastboot anymore. My TWRP is in chinese and but I found the reboot menu and the alternatives are: System, Power Off, Recovery and Download. I think i've tried them all and none of them brings me fastboot. I went into loop when I tried to install SuperSu through TWRP on stock rom. Is there hope? Yesterday I managed to get into fastboot, but can't remember what I did. I heard something about draining the battery and then theres hope?
Click to expand...
Click to collapse
Several options you got:
Install older SuperSU. I remember I had the same thing and the only way was to downgrade SuperSU. 2.5x, I think.
Try to access fastboot - turn off phone, keep vol- pressed and power up. Release vol- when you see fastboot screen. Try it with and without USB PC connection.
Try to deplete your battery. It works in other devices as after charging again, boot.img behaves differently. Don't ask me why, but if the phone charges as it is, no harm in trying.
Wipe all partitions - Dalvik, cache, data, internal storage and system. And then install a custom ROM from sdcard or USB-OTG. You can access H7 content from PC, through USB, while in TWRP.
Huawei eRecovery
I got into Huawei eRecovery EMUI, but when I try to "Download latest version and recovery" and connect to wifi it fails:"Getting package info failed". The other options are Reboot and Shutdown. Could this be useful?
Another question how to transfer to sd-card when in twrp. The phone is detected in windows as MTP thingy, but in adb shell no devices is found... I'm too noob for this.
Got into fastboot mode, and flashed all the imgs except system.img where I get error "cannot load"... Got the ADB drivers now, but still adb shell finds no devices. It appears that my TWRP is gone, and instead I get Huawei eRecovery. So my problem now is that I dont get system.img flashed, still stuck at honor-logo, and can't push files with adb, I get "no devices". Any tips?
Got it now, thank you very much! But what's the point in doing the last steps with dload when everything seems to be good?
mosoo said:
I got into Huawei eRecovery EMUI, but when I try to "Download latest version and recovery" and connect to wifi it fails:"Getting package info failed". The other options are Reboot and Shutdown. Could this be useful?
Another question how to transfer to sd-card when in twrp. The phone is detected in windows as MTP thingy, but in adb shell no devices is found... I'm too noob for this.
Got into fastboot mode, and flashed all the imgs except system.img where I get error "cannot load"... Got the ADB drivers now, but still adb shell finds no devices. It appears that my TWRP is gone, and instead I get Huawei eRecovery. So my problem now is that I dont get system.img flashed, still stuck at honor-logo, and can't push files with adb, I get "no devices". Any tips?
Got it now, thank you very much! But what's the point in doing the last steps with dload when everything seems to be good?
Click to expand...
Click to collapse
Please share your solution with others, so that your post can be referred.
Doing a forced updated (dload) gives the absolute assurance you flashed all the partitions correctly with all the *.img compressed files in the update.app file.
mosoo said:
Got it now, thank you very much! But what's the point in doing the last steps with dload when everything seems to be good?
Click to expand...
Click to collapse
When you flash the partitions manually, we are not flashing all of them, only some of them, and some partitions are not in regular img format, so by doing the three button update we can put all the partitions in their respective places.
Another benefit of doing force update is that if you don't know your build number and flashed system.img, cust.img etc of some other build then by doing a force update all the img files of same build are flashed.
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.