Related
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Did u try connecting to adb?
Sent from my U9200 using XDA Premium 4 mobile app
some help
onetree said:
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Click to expand...
Click to collapse
you can try it whith a linux pc (ubuntu)
i have the same problem
good luck!
onetree said:
Hi guys,
I would really appreciate any help getting out of this pickle (my first time trying to install a ROM).
Here's the situation:
- Running a Huawei P6-C00 Chinese phone
- Was interested in trying a custom ROM (e.g. CleanRom by @surdu_petru) in order to enable Google Apps
- Updated normally to B120 CN as instructed
- Rooted (using Root Wizard)
- Installed customer recovery (TWRP 2.6.3.3)
- Started flash process including advanced wipe in TWRP... wiped system, cache, davlik, etc... :crying:
- Realized that I didn't have the ROM .zip copied to the phone yet
Currently, I'm able to boot into TWRP but cannot connect using adb for sideload (TWRP just says starting sideload but never connects). What do you guys recommend? I don't have a backup of any working ROM or the stock image.
Is there a way to initiate a "standard" restore since I wiped all the caches? ...
Are there some tricks to getting ADB running so I can try to sideload the ROM again? ...
P6-C00 does not have an SD card, but is it possible to load the ROM onto a USB and read it from TWRP?
Thanks for any help!
Click to expand...
Click to collapse
Did you try it with fastboot?
Gesendet von meinem P6-U06 mit Tapatalk
ext4
taaeem said:
Did you try it with fastboot?
Gesendet von meinem P6-U06 mit Tapatalk
Click to expand...
Click to collapse
i know that he must use a linux pc that for the drivers
ext4 If say it right...
taaeem said:
Did you try it with fastboot?
Click to expand...
Click to collapse
Hi Taaeem,
Thanks for the hint. I read some posts on fastboot and tried the following, but could not get into fastboot mode.
Methods I tried
- Power off phone and then power on while holding vol-down button
- Select Reboot -> System option from TWRP, while holding volume down
- Select Reboot -> Bootloader option from TWRP
From what I understand, fastboot mode should be run from the /boot partition, which I didn't wipe. So any ideas how I can get into fastboot mode?
Thanks again!
Okay, I confirmed that I have at least some kind of fastboot access because I tried "fastboot reboot-bootloader" from command prompt on my PC, and it rebooted the phone (but the phone stayed on boot logo).
- Next time I get fastboot, should I run "fastboot flash [partition] [ROM-file.zip]"?
- If so, what partition should I specify? I'm confused about where this command will send the ROM file, and if so how do I find it from TWRP later on in order to install it?
Thank you!
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
Click to expand...
Click to collapse
fastboot mode on the P6 doesn't have any kind of ui for fastboot, so it stays on the boot logo, fastboot should work fine.
You could always find an USB OTG cable and connect a FAT32 partitioned mem stick with the .zip on it, TWRP allows flashing from USB memory as far as I know
You are definetely not out of hope, but im not sure about the compability of P6-U06 roms with the C00 variant.
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Click to expand...
Click to collapse
Obviously you can't flash the whole zip file to every partition, infact you can't flash a .zip at all, atleast not in fastboot mode, .img extension is used. So don't try flashing the rom manually via fastboot, since you have a high risk of actually bricking the device, if not in the right hands.
Also when booted into TWRP, try "adb devices" in the cmd see if anything shows up.
onetree said:
One more update:
- Even though I'm stuck at boot logo when I try to enter fastboot mode, it looks like there is a somewhat working fastboot connection. I tried running "fastboot flash [partition] ROM.zip" but it fails after 16s ("remote: flash write failure" or "remote: partition does not exist"). I tried flashing to cache / data / system
Should I try @N!ELS huawei p6 suggestion of accessing by Linux? (I don't have one nearby) or am I using fastboot wrong?
Thanks!!
Also:
- I noticed that when I boot into TWRP the device shows as "..." in my system tray USB devices list.
- When I try to boot into fastboot mode, the device shows as "Android Sooner Single ADB Interface" (but phone is still stuck on boot logo)
- However I'm still not able to connect using ADB .. shows "error: device not found" in all cases)
- Finally, after powering off the phone does show the stock charging animation, which gives me hope that this can still be saved :crying:
Click to expand...
Click to collapse
Okay that's good when you are stuck at the logo and you can see your device at your PC you are in fastboot mode, from here you can work with fastboot commands NOT with ADB that will not work. Anyway isn't there a option in TWRP where you can mount your device to USB when that work you can just copy the files on your phone without to go with fastboot. When that don't work you must try to extract the .zip from the ROM you want to install and flash every image with fastboot I think that should work.
Gesendet von meinem P6-U06 mit Tapatalk
tauio111 said:
fastboot mode on the P6 doesn't have any kind of ui for fastboot, so it stays on the boot logo, fastboot should work fine.
You could always find an USB OTG cable and connect a FAT32 partitioned mem stick with the .zip on it, TWRP allows flashing from USB memory as far as I know
You are definetely not out of hope, but im not sure about the compability of P6-U06 roms with the C00 variant.
Obviously you can't flash the whole zip file to every partition, infact you can't flash a .zip at all, atleast not in fastboot mode, .img extension is used. So don't try flashing the rom manually via fastboot, since you have a high risk of actually bricking the device, if not in the right hands.
Also when booted into TWRP, try "adb devices" in the cmd see if anything shows up.
Click to expand...
Click to collapse
Okay so now I'm a bit paranoid about hard-bricking the device, and would rather not try my luck on a ROM that isn't approved for the P6-C00, haha...
At this point I just want to get a working OS installed (restore to the default for P6-C00 phone, even), and then maybe try to safely enable Google Apps. Any suggestions on how I can get this restored?
- I think the device came with a USB cable that is OTG.
- Seems like fastboot is also working, even though "fastboot getvar xxx" returns nothing useful
- ADB does not work while booted into TWRP (can't run shell, sideload, or list devices)
onetree said:
Okay so now I'm a bit paranoid about hard-bricking the device, and would rather not try my luck on a ROM that isn't approved for the P6-C00, haha...
At this point I just want to get a working OS installed (restore to the default for P6-C00 phone, even), and then maybe try to safely enable Google Apps. Any suggestions on how I can get this restored?
- I think the device came with a USB cable that is OTG.
- Seems like fastboot is also working, even though "fastboot getvar xxx" returns nothing useful
- ADB does not work while booted into TWRP (can't run shell, sideload, or list devices)
Click to expand...
Click to collapse
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Thank you! I will try this tonight after work
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Thanks, tauio111! That worked and I now have a working phone again :victory:
I'm going to be a bit more careful about how to enable Google Apps... this is too much stress during the workweek haha.
Later on what do you think my best option would be?
- Wait for a confirmed easy to install ROM for P6-C00 that supports Google Apps
- Some other way to enable Google Apps with the standard firmware, since I am rooted?
Thanks :laugh:
onetree said:
Thanks, tauio111! That worked and I now have a working phone again :victory:
I'm going to be a bit more careful about how to enable Google Apps... this is too much stress during the workweek haha.
Later on what do you think my best option would be?
- Wait for a confirmed easy to install ROM for P6-C00 that supports Google Apps
- Some other way to enable Google Apps with the standard firmware, since I am rooted?
Thanks :laugh:
Click to expand...
Click to collapse
Easy, flash this via TWRP
tauio111 said:
Easy, flash this via TWRP
Click to expand...
Click to collapse
Thanks @tauio111 and everyone else who helped debug this.
I flashed stock recovery, updated official firmware to B120, re-flashed TWRP, flashed gapps, and now have a working phone with Gmail and Play Store!! :silly:
tauio111 said:
Download this rom for example https://disk.yandex.com/public/?hash=bhDlIAc5AqKh4RAB2IdatPdEfYVI9FH/Zky/UTGcH3M=
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
I have the same problem and i do the same but nothing..
I tried to delete xposed installer and my phone stuck..
What can i do?
Edit:It s opened but i can t touch my screen.I try to put my password and i can t..
tauio111 said:
Download this rom for example (Removed to allow posting - faye2thesky)
Extract the .z7 and run the flash_all.bat, this scripts flashes the rom via fastboot and you should get your device back up and running again. And from there you can update to a newer firmware version without problems.
If the bat doesn't work try this:
boot to fastboot
fastboot flash system system.img
fastboot flash cust cust.img
fastboot reboot recovery
Wipe cache and dalvik cache in twrp
Click to expand...
Click to collapse
Heya Tauio111, I'm having the same problem as onetree and I've been frying my mind over this for the past 4 days before I came across your solution. I found that your link is no longer working, may I ask what that ROM is and where else I may find it? Thanks!
faye2thesky said:
Heya Tauio111, I'm having the same problem as onetree and I've been frying my mind over this for the past 4 days before I came across your solution. I found that your link is no longer working, may I ask what that ROM is and where else I may find it? Thanks!
Click to expand...
Click to collapse
A way that may help (i've done it with boot&recovery images). Using this tool http://forum.xda-developers.com/showthread.php?t=2433454 , might give you the *.img files necesary for flashing the stock rom through fast boot. All you need is to follow the instructions on the tool and have a stock rom (update.app file type), and some knowledge on how to use the fastboot.
Hi Guys,
I kinda did the same thing here.
I accidently wiped my system with TWRP v2.6.3.7
I also have a huawei ascend p6 u06
I didn't realize i never copied a rom to my device so i don't know how to install.
I can't seem to be able to use adb or fastboot and my device is not picked up by windows (8.1), it just says removable disk in my computer.
and under device manager it says P6-U06 under unknown devices.
I have tried to install a bunch of different drivers to attempt something but no luck.
Please help me.
HW_Version -
Bootloader Version - unknown
IFWI Version - 0094 - 1069
Serial Number - my #
Signing - ?
Secure_boot - ?
RESULT: FAILD (remote: flash_cmds error!)
Thats what my bootloader looks like. What happened was I tried to update from Stock .184 to the new MM build. I downloaded the file and got prompted the update in my phone. It installed or did something and when it rebooted I was stuck in a bootloop with no screen.
I ended up using xFSTK Downloader everything went fine, my phone turned on with 4 colored bars and brought me in to the bootloader. I proceed to use Asus Flash Tool to flash the raw file of .194 and that's where my problem started.
It was taking soo long so I took my dog out for a good 15-20 min walk came back and the flash tool was still doing its thing and the green bar was still moving and on my phone it said RESULT OKAY.
I ended up closing the Flash Tool because it was taking soo long. I rebooted my phone then it goes in a bootloop with the 4 colored bars on the screen. Then I just keep repeating these steps and can't get anywhere.
When I am able to get in the bootloader after using xFSTK Downloader I cant use some flashboot commands. I cant flash twrp because I get FAILD (remote: flash_cmds error!) .
I was going by this guide here. http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
EDIT: I just noticed that my phone doesnt come up as MOOREFIELD in device manager. when it turns on and goes in to the bootloader it shows for a second and goes away.
I'm very thankful for anyone that responds. Thx for reading.
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
kenbo111 said:
Just so you know why it happened. You HAVE to be at version 194 before you update to MM! Otherwise... Boom
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
I wish they said that in the steps for updating on their site
Chrodechild said:
I just had this problem after a bad flash~
The instructions of unbricking the phone was lacking some infos.
So I tried a lot of experiments just to unbrick this piece of crap XD
If you are successful on xFSTK procedure you'll end up on "fastboot" mode.
Then you'll proceed with the flashing tool. According to your description everything is just normal my mate~
Now this is the REAL DEAL.
You may notice an ENDLESS "Flash Image" on your flash tool.
Now look on your phone in the Fastboot mode. If you see that the "RESULT: OKAY" seems got stuck, its ok my friend its normal (it will take about 10-30mins depending on your PC).
• Unplug your phone, re-plug it in
• Close AFT
• End process "a500cgfastboot.exe" in the task manager"
Then do the FASTBOOT commands:
• fastboot flash splashimage splashimage.img
• fastboot fastboot flash droidboot.img
• fastboot flash boot boot.img
• fastboot flash recovery recovery.img
AND! you can now proceed on your recovery menu.
You may ADB Sideload the stock firmware by doing
• adb sideload UL-Z00A-WW-X.XX.XX.XX-user.zip (replace the "X" of what file version you want to flash)
And wait for it to reboot. I really hope this helps you mate~
#cheers!
Click to expand...
Click to collapse
im gonna get some breakfest in my belly and have another go at it.. couldnt use have my phone at all yesterday and I tried fixing it for atleast 8-10 hour.. it sucks lol.
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
Ill watch you video and see if it helps. the instructions on the unbrick I was using was kinda hard to understand for the most part.
timbernot said:
This is not so, I sideloaded MM fine straight on .184
No problem sideloading
Click to expand...
Click to collapse
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
So now it seems I can use xFSTK and now im in the bootloader with the 4 color bars. But when I goto flash using the Flash tool my phone just sits on FASTBOOT CMD WAITING and the flash tool fails with FLASH IMAGE Failure[FAILED[wrong image format]]
I need some serious help :[
quarterbreed said:
After a long day yesterday and the flsah process getting stuck, I uninstalled everything and reinstalled everything required for this process. When I finish with xfstk then move on to the flash tool it starts to flash then it stops says Flash image failure[FAILD [wrong image format]]
Im getting so fusturated with this phone its crazy.. I just got in a month ago too.
Click to expand...
Click to collapse
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
sukhwant717 said:
well lot of people facing problem. as you told that you are able to get into fastboot after xFSTK process. and you are unable to flash raw firmware file!!!! well perform xFSTK again. get into fastboot and perform following steps:
very first of all. rename .raw firmware file to .zip file and extract all files in there.. now place all files in adb and fastboot folder. open command window here. ( where you places files from raw firmware and adb and fast boot tool folder) perform the following commands
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem erase_token
4. fastboot oem start_partitioning
5. fastboot flash /tmp/partition.tbl partition.tbl
6. fastboot oem partition /tmp/partition.tbl
7. fastboot erase system
8. fastboot erase cache
9. fastboot erase data
10. fastboot erase APD
11. fastboot erase ADF
12. fastboot oem wipe splashscreen
13. fastboot oem stop_partitioning
14. fastboot flash fastboot droidboot_sign.bin
15. fastboot flash token PROD_BOM_Full.bin
16. fastboot flash ifwi ifwi-prod.bin
17. fastboot flash splashscreen splash_sign.bin
18. fastboot flash boot boot_sign.bin
19. fastboot flash recovery recovery_sign.bin
20. fastboot flash APD APD.img
21. fastboot flash system system.img
22. fastboot reboot
hope it will work fine. hit thanks if helped. if any further question please post.
Click to expand...
Click to collapse
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
quarterbreed said:
Thx for the detailed post.. I got in to my phone finally after messing with it all day yesterday and I close to throwing it against the wall lol. It worked like a charm.. I wonder why the flash tool wouldnt work.
Now how would I go about side loading .194 and installing a recovery like twrp again so I can back this thing up once i get to mm.
Click to expand...
Click to collapse
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
sukhwant717 said:
you can side load 194... works well... after 194 you can also install latest official marshmallow. but do not install custom recovery if you want to install lates MM. first install 194 then latest MM. then custom recovery
Click to expand...
Click to collapse
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
sukhwant717 said:
posting new thread. do not update to official MM if you have custom recovery or you have rooted phone. though after install MM you can install custom Recovery afterwards. not tried but i think will not cause any issue
yes cause of brick is custom recovery
Click to expand...
Click to collapse
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Is it ok to put the MM build on my internal storage and apply the system update from there?
quarterbreed said:
opps my bad. what you helped me with put .194 on my phone already. I ment am I able to download the MM rom and do the system update with it again. Or should I side load it? Im not sure how to side load. After I do get MM on what recovery do you recommend. I did have the latest TRWP before all this happend, Is that what caused this brick? because when it flashed mm before I think it brought me into trwp.
Click to expand...
Click to collapse
quarterbreed said:
I have no recovery installed I tried to get to bootloader with adb and it showed the android guy with a error. How do I go about flashing the new MM build. I really dont want to mess up my phone again lol. Only thing I have on its is .194 atm.
Click to expand...
Click to collapse
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
I didnt do a factory restore after installing .194 I'll do that now.
sukhwant717 said:
can you post screenshot.
hope you performed factory restore after installing Z00A-WW-2.20.40.194-
try adb reboot recovery
Click to expand...
Click to collapse
Im sure what you mean sorry. I have .194 on my phone with the help of your steps in fastboot. It booted and im in my phone and its updating all my apps and stuff..
Do you mean factory restore in bootloader? If so I tried adb reboot recovery the phone restarts and goes to a screen with https://i.ytimg.com/vi/wuixmZ11Kyc/maxresdefault.jpg Im guessing if i cant get in to recovery I cant do a factory restore?
in fastboot my bootloader doesnt have a version number it just says unknown
EDIT when the picture above showed up I held the power button and vol + to get into recovery and its performing a factory reset atm.
Anyone else bricked ?
Unbrick and into system with correct serial and imei numbers in 20 mins ..see my signature for zubes ..
PS, save yourself days of pain , after xfstk , flash an earlier raw ..
PMSL
---------- Post added at 08:22 AM ---------- Previous post was at 08:18 AM ----------
timbernot said:
Reflash in xfstk, press dload ...power plus vol + together till phone recycles and flash begins , check my signature below for tutorial, read whole thread and watch video.
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
Click to expand...
Click to collapse
You may need to flash an earlier raw too from which the ifwi and fwr dnx and pos bin are made.
hey
when my phone boots shows that my device is not verified by google , what to do?
Jwtiyar said:
hey
when my phone boots shows that my device is not verified by google , what to do?
Click to expand...
Click to collapse
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
sukhwant717 said:
you might have unlocked bootloader with unofficial method. nothing to worry about its just a warning devices are far more insecure. if you are worried about privacy things. believe there is nothing like secure when using digital devices. and there is not even single service provider which do not collect data. hence enjoy your unlocked device and play around
Click to expand...
Click to collapse
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Jwtiyar said:
Thank you bro, the problem is now its not booting (bootlooping)after upgrading bootloader, flashing twrp then flashing RBR ROM, IDK if this is ROM related or bootloader related
Click to expand...
Click to collapse
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
sukhwant717 said:
flash boot, fastboot, recovery image for the same firmware u had working last time. if still do not boots. flash bom token, dnx, ifwi for the same firmware. flash boot, recovery and fastboot again while u flash dnx and ifwi.
Click to expand...
Click to collapse
You made it really complex bro i dont understand what to do.
Jwtiyar said:
You made it really complex bro i dont understand what to do.
Click to expand...
Click to collapse
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
sukhwant717 said:
the last working firmware. whichever was installed last time. (assume you were on latest MM ww4.21.40.233... extract it and get the files (boot.img, recovery.img, droidboot.img, splashscreen.img) in the same firmware there will be ifwi.zip extract that too and get the files (bom token, dnx , ifwi)... now copy the extracted files to adb fastboot tool folder. and then in same folder move cursor to and empty place and hold shift and right click on mouse. you will get option open command windows here.
now reboot your phone in fastboot mode and connect to PC.. now run the following commands
fastboot devices ( to see if device is recognized by pc and fastboot tool)
fastboot flash splashscreen splashscreen.img
fastboot flash token " bom token file name" (without commas )
fastboot flash dnx "dnx file name"
fastboot flash ifwi "ifwi file name"
fastboot erase boot
fastboot flash boot boot.img
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot erase fastboot
fastboot flash fastboot droidboot.img
fastboot reboot
keep in mind extract files from the same firmware you were on the last time when your device was working.
Click to expand...
Click to collapse
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Jwtiyar said:
Thank you very much bro,but the last working firmware i dont know which one was but it was 5.1.1, which firmware is that android version?
Click to expand...
Click to collapse
device model ze551ml oe ze550ml?
sukhwant717 said:
device model ze551ml oe ze550ml?
Click to expand...
Click to collapse
ze551
Jwtiyar said:
ze551
Click to expand...
Click to collapse
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
sukhwant717 said:
download the following file extract it. now reboot your phone in fastboot mode and connect to pc. wait till pc recognize it and make detection sound.
now it extracted folder double click to run the file update bootloader.bat
all done
report back if device boots or gives any error in cmd
wait it has an error
Click to expand...
Click to collapse
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Jwtiyar said:
before this problem happen i upgraded boorloader to MM then flash TWRP and installed MM ROM so now it has MM Custom ROM.
i did your solution and installed successfully but in adb commands as i saw give that boot.img not found then rebooted and now directly will go to installing system update and give the error (android robot with red warning icon ) .
Click to expand...
Click to collapse
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
I installed RBR ROM which based on MM , now the error gone after flashing boot.img but the will boot to asus logo and will reboot again it seems its bootloop .
sukhwant717 said:
when there at that error screen press and hold volume button you will enter into recovery mode. there go to option reboot bootloader phone will boot in fastboot mode
now in the extracted folder at empty place shift and right click.. then open cmd here and run command
fastboot flash boot boot.img
fastboot reboot
which mm rom you installed?
btw i have corrected the boot.img not found error. you can download and rung the bat file
https://drive.google.com/open?id=0B72QQTXqZSRwSVpwSG9iWS0tbUk
Click to expand...
Click to collapse
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Jwtiyar said:
this is the output now after flashing coorected .zip file you provided:
http://paste.ubuntu.com/24395746/
Click to expand...
Click to collapse
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
sukhwant717 said:
it is bootlooping because of incorrect system
now tell me do u want to flash custom rom or official marshmallow?
Click to expand...
Click to collapse
custom MM
Jwtiyar said:
custom MM
Click to expand...
Click to collapse
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
sukhwant717 said:
as you already downloaded that rom.. and also the recovery needed for that rom..
first of all same as earlier flash MM bootloader. ther reboot bootloader once then flash twrp. the exactly mentioned in the RBR rom thread. then go to advanced in twrp and click adb sidelaod. tick wipe dalvik cache and cache. swipe to sideload ... now run command adb sideload "rom file name"
if bootloops after flashing firmware. do a factory reset and reboot. going to sleep now 1.15 AM here. will answer tomorrow if any other question
Click to expand...
Click to collapse
thank you very much now its booted successfully
Jwtiyar said:
thank you very much now its booted successfully
Click to expand...
Click to collapse
great good to know your device is alive again
sukhwant717 said:
great good to know your device is alive again
Click to expand...
Click to collapse
Thank you bro
Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.
mumith3 said:
Hi,
I own an Honor 7X (BND-L21) European variant. I was on Oreo Beta firmware BND-L21C432B302(432log) version.
I wanted to update to stable oreo firmware following this guide by @mrmazak
But unfortunately while in twrp, it wasn't responding to my volume down button click & auto aborted (as stated in the linked thread)
So I reboot the phone & suddenly it went into stock recovery & started to update. But at 5% it failed & from then, I'm unable to flash anything.
Tried rebooting & booting into TWRP, but TWRP doesn't exist anymore & boots into erecovery or stock recovery.
Phone doesn't goes beyond Huawei logo.
Tried flashing Oreo TWRP but it fails. tried flashing stock OREO recovery from update.zip, fails.
Tried both fastboot flash recovery & fastboot flash recovery-ramdisk command
My device detail is as below
fastboot oem get-product-model : BND-L21
fastboot getvar vendorcountry : hw/eu
fastboot oem get-build-number : BND-L21 8.0.0.302(C432log)
fastboot getvar rescue_enter_recovery : getvar:rescue_enter_recovery FAILED (remote: FAIL:need all image flashed!)
fastboot oem oeminforead-SYSTEM_VERSION : BND-L21C432B102CUSTC432D001
The firmware I tried was BND-L21C432B330CUSTC432D2
Any kind of help is appreciated.
Cheers.
Click to expand...
Click to collapse
Re failing at 5% suggests to me that one of the three file was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is you bootloader unlocked. Still?
mrmazak said:
Re failing at 5% suggests to me that one of the three files was not found.
Not able to fastboot flash never happened to me.
The not booting happened to me after flashing different region firmware. And factory resetting with recovery including format cache got it to boot.
Is your bootloader unlocked? Still?
Click to expand...
Click to collapse
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?
mumith3 said:
all 3 files were perfectly there in "HWOTA8" folder in external SD
Bootloader & FRP both unlocked still.
Firmware region is same. I matched it thoroughly.
I don't know why fastboot can't flash recovery anymore
right now, I tried to fastboot flash system with aosp GSI img. it worked... then again extracted system.img from update.app .... again bootloop.
but still the same problem with fastboot flash recovery.... can't flash recovery.
Any advice?
Click to expand...
Click to collapse
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img
mrmazak said:
What command Are you using to flash recovery?
Code:
fastboot flash recovery_ramdisk twrp-filename.img
Click to expand...
Click to collapse
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?
mumith3 said:
Sir, I tried with the RECOVERY_RAMDIS.img in your AFH .... It worked !!!! how???
Edit
Funnily, fastboot flash recovery-ramdisk works in powershell.... doesn't work with CMD..... !!!! What in the world is happening?
edit
Sir @mrmazak can not boot into fastboot anymore.... doesn't get past after stock recovery !!! any advices?
Click to expand...
Click to collapse
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash
mrmazak said:
Really don't know what you are doing, it is not recovery-ramdisk It is recovery_ramdisk
Under score not dash
Click to expand...
Click to collapse
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable
mumith3 said:
it was a typo in forum.... !!! :cyclops: got into fastboot.
Sir, when I install hwota8_update-auto-rename, I need to press volume down at the end of the script, roght? but my volume down button press is not being detected.... should I try the commands from directly inside TWRP terminal?
& if you don't mind, can I have your whatsapp/telegram nmbr in PM? I'm really trying to fix my phone :crying:
Current situation,
TWRP installed,
Fastboot accessible
doesn't go past huawei splash logo/twrp
Edit
Manual Flashing through TWRP terminal worked.... currently on OREO Stable
Click to expand...
Click to collapse
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)
mrmazak said:
I need to look at that code I'm using, that looks for the buttons. It works sometimes and not others.
Manual reboot to recovery should have worked also. Bit good that you are back going again
edit:
updated the hwota8_update-auto-rename.zip , removed the volume button check and leave it for the user to do a reboot recovery from menu. (made this way , to be able to cancel the update for whatever reason , might arise.)
Click to expand...
Click to collapse
Thanks for all the help Sir ?
P.S. Oreo stable is pretty damn good so far.
Stuck on splash screen "Your device has been unlocked and can't be trusted."
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
gabrce said:
Hello, first I apologize for my English.
After a factory reset of my Honor 7X ((BND-L21), and a failed flashing of TWRP, my device stuck on "Your device has been unlocked and can't be trusted...Your device is booting now..." at every boot.
I tried to re-flash TWRP recovery through fastboot (PHONE Unlocked, FRP Unlock). At every time the process on the command window works but when I want to boot into TWRP, nothing appears, the device reboot and got stuck on the same splash screen.
I can't boot into eRecovery (I think I deleted it...).
I can't use dload method (I tried but when I hold both volume buttons + power, nothing happens, it reboots into the same screen as usual.
I tried to unbrick the device with Huawei Multi-Tool, the process works but nothing new on the device.
I tried to drain the battery, without results.
If you want any precisions in order to help me, don't hesitate.
Thank you all very much, any help will be really appreciated.
Click to expand...
Click to collapse
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
mrmazak said:
There must be more to the story of what goes on to the device.
You only say factory reset and failed twrp install.
But also say the fastboot screen show successful flash of twrp.
So how did you flash it? What command?
Also say you cannot boot erecovery , think it erased. How, when?
I think maybe you flashed wrong partition, but need your input as to what command you used.
Click to expand...
Click to collapse
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
gabrce said:
Thank you for your answer.
I flashed TWRP with the command "fastboot flash recovery_ramdisk twrp_7x.img".
Yes, at the beginning I would like to install a custom rom, but it failed so I did a factory reset with twrp. After that I tried to install the original firmware and unbrick the device with Huawei Multi-Tool (by following an other thread).
Everything goes well on Huawei MT screen, but not on the device (bootloop after rebooting).
I tried to force original firmware installation using Fastboot commands (fastboot erase name of partition and fastboot flash name of the partition file.img). I flashed system.img, cust.img, product.img, vendor.img, ramdisk.img.
Click to expand...
Click to collapse
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
mrmazak said:
Oooooh. Sounds like it's possible you have mixed Oreo and nougat partitions somehow
This I have seen before when using multi tool. When not correctly setup
Try from fastboot to get the prop file.
"Fastboot get prop"
I think is correct command.
I will check in my notes, when I can to see.
Interested in seeing what build number is shown if any .
And if possible to get a partition layout, but I don't think you can from fastboot alone.
Click to expand...
Click to collapse
Thank you but "fastboot get prop" is not the right command. If anybody has a solution it will be awesome.
Download the latest full ota package for your device (around 2gb)
Extract the contents of the update. App using huawei firmware extractor and
Flash
kernel
Ramdisk
Recover ramdisk
System and cust images using fastboot
After that flash the correct version of twrp for your device and then install images of version and vendor(found in update. App file) partitions using twrp.
.
This method worked for me
It didn't worked for me... Do you know any other method?
I tried many TWRP versions but the phone doesn't boot into TWRP...