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.
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Djcall11 said:
I was following the steps on the rooting process with twrp and I got twrp to boot but i couldn't boot into the system and now it's just stuck in download mode is there any way to fix it
Click to expand...
Click to collapse
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
iliais347 said:
Download the factory images.
Run flasg_all.bat.
If you dont want your data partition to be formatted, then edit the .bat file and remove the line where it says "erase userdata". You can also remove tge last line that reads "fastboot reboot".
When rooting, i always boot into twrp using the image and flash both twrp zip and magisk zip in one go.
Click to expand...
Click to collapse
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
so... the razer loading green effect is happening but it hasn't passed that it just keeps going
should I just put back the command to delete the user data
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Roxas598 said:
Have you unlocked the critical portion of the bootloader? (First thing I always ask)
If yes then yeah just wipe the whole thing.
Click to expand...
Click to collapse
welp the phone booted but it just stays on the loading screen and when I restart it just goes straight to download mode
I did unlock_critical and it just tells me that the device is already unlocked
I don't really know what else I can do from here
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Roxas598 said:
Of both bootloader portions are unlocked it should just be a case of running the flash all script from the factory images and you're good to go :S only other thing I can suggest to make sure there's nothing bad in there and in fastboot wiping user data again.
Click to expand...
Click to collapse
I ran the script how it was and I just get stuck at the green effect loading I will try some other commands and I'm about to try the 7.1.1 mr3 rom to see if that work
so using the 7.1.1 mr3 worked i finally have my phone back thank guy for the help
Djcall11 said:
i have to edit the bat file and add -i 0x1532 to every command anyway for the command to work
Click to expand...
Click to collapse
Why is that? I didnt have to do that.
What does that command do?
Hi All
Apologies if this already has a thread, noob here.
Okay so I updated to Android 11 about 45 mins ago, Phone restarted seemingly fine and asked for my pin number so I typed it in...
Wrong Pin (definitely typed the right pin)
Okay so I've has this issues before post updating but I couldn't remember how I fixed it so I jumped on Google and searched for a fix. Someone suggested restarting in safe mode. Okay so I hold the power button then hold on restart until it asked me if I want to restart in safe mode. Yes please. Fastboot starts, I get the options to start but everything I select loops me back to fastboot mode along with the following worrying messages:
NOS Production: Error
Device State: Error!
Enter Reason : failed to load/verify boot images
I've seen in another thread the suggestion to leave the battery to drain overnight then to try booting . Can anyone confirm if this is the only solution or if there is alternative option?
Thanks
If I were you, I would download the full factory image for android 11 and do an install from fastboot. It seems the boot partition is corrupted.
Remember to remove the "-w" flag from flash-all.sh so your data is not deleted. Let me know if it works. The fact that you can access fastboot is a good sign!
Push
I got same issue, any solution?!
i have this problem too when i update to android 11 via OTA or flash stock image from fastboot ,
always get back to fastboot with "error setup KM" or "failed or load/verify boot images"
the solution for me is to flash android 10 image via fastboot, so i can't update to android 11
miku1024 said:
i have this problem too when i update to android 11 via OTA or flash stock image from fastboot ,
always get back to fastboot with "error setup KM" or "failed or load/verify boot images"
the solution for me is to flash android 10 image via fastboot, so i can't update to android 11
Click to expand...
Click to collapse
Did you ever figure this out? android 11 seems to have messed up my boot_a and boot_b, boot b seems to work fine I can enter recovery on it, but I can't switch to boot a it says directory not found or something, and when booting up I get fastboot mode: error boot prepare on boot a. how do I just completely reset everything and start clean? or do I gotta go back to android 10?
paradoxiumwind said:
Did you ever figure this out? android 11 seems to have messed up my boot_a and boot_b, boot b seems to work fine I can enter recovery on it, but I can't switch to boot a it says directory not found or something, and when booting up I get fastboot mode: error boot prepare on boot a. how do I just completely reset everything and start clean? or do I gotta go back to android 10?
Click to expand...
Click to collapse
I think this related to emmc defect, because when i ask vendor to replace with new unit the problem gone, there's nothing you can do instead go back to android 10 or try flash android 12 beta and see it can boot
nikhilnangia said:
If I were you, I would download the full factory image for android 11 and do an install from fastboot. It seems the boot partition is corrupted.
Remember to remove the "-w" flag from flash-all.sh so your data is not deleted. Let me know if it works. The fact that you can access fastboot is a good sign!
Click to expand...
Click to collapse
quoting from your answer , is it true that removing -w in the command will not delete existing data?
Is there a way i can recover my data ? I need to recover my kid's graduation pictures. I will pay for help if I need too.
I was rooted and using 11.2.4.4.LE15AA. I uninstalled Magisk then i tried updating to 11.2.5.5 via ota , it kept saying install failed i need to reboot and now I'm stuck in fastboot.
edit: and now it doesn't turn off.
Im a flipping idiot.
Thanks in advance.
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Shooter7889 said:
https://mega.nz/file/7YQj3SIR#5yDfje2mVgPVRdZi-gYrDRvvQE2hx_DYD00vicZH8Fo
This is a zip from one of the top 3 pinned threads on this OP9P forum that has stock and patched boot.img from your 4.4AA build..(if thats what ur phone is still on). U may be able to download the zip, put on ur pc, extract it, then open cmd and fastboot boot (then drag the stock boot.img to the command prompt u typed in) and hit enter.. It may work to get u back booted unrooted...
Click to expand...
Click to collapse
Crap that didn't work. I'm so beyond screwed. I wonder IF and when TWRP comes out if I will be able to decrypt then.
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
craznazn said:
Try flashing 4.4 or 5.5 full OTA via fastboot/fastbootd. If you are gonna try the 5.5 then you gotta use EU/India.
TWRP at this point is a pipe dream. Decrypt doesn't even work for A10 on OP and Android is moving faster than TWRP can keep up.
Click to expand...
Click to collapse
Is that where i flash all the individual .imgs with fastboot? or just system.img
Individual
In case this comes from magisk modules, just try to reboot in safe mode:
Safe Mode
1. Hold power until it goes off
2. Boot and wait for the bootloader warning
3. Hold vol up and down until boot animation
4. Once it's booted just reboot again and you're done
Now on boot all magisk modules are disabled
Other option, have you try to flash your original boot!
craznazn said:
Individual
Click to expand...
Click to collapse
I get this for several of the img files.
FAILED (remote: Flashing is not allowed for Critical Partitions
But I'm able to get to recovery now, with this error
boot reason fs_mgr_mount_all
Fastbootd for critical partitions (not fastboot)
I wiped it.
close the thread.
Oh too bad i had your solution, as ihad the same problem last week.
For anyone else in this situation you have to flash the stock boot img to opposite partition. Then boot to that partition. Get your data off at that point before you do anything else. Then try to re-root