Database Users

Nexus 7 softbrick(?)

Hi!
I was in recovery, factory reseted the system. I wanted to restart os, but it said "No OS installed", so i booted to bootloader. When i try to reboot to system it says "booting failed". ADB flashing is not working. Please, help me.
Nexus 7
Bootloader version 3.41
I have android sdk installed.

Have you tried using wug's toolkit to revert to stock (and selecting soft-bricked status)? Here's a link if you haven't. http://forum.xda-developers.com/showthread.php?t=1766475
Sent from my Nexus 4 using xda app-developers app

Yep, i tried, theoretically it's fine, but when it says it's finished and device will reboot nothing happens.
OK. Here it is how it now looks: I managed to get recovery working, .zip with rom is on the sdcard. When i try to flash ROM it says "Unable to mount /system"

Update to bootloader version 4.23 then flash the stock factory ROM image.

What command should I use to flash stock .tgz file?

zolcix said:
What command should I use to flash stock .tgz file?
Click to expand...
Click to collapse
None. You can only flash image files.
---------- Post added at 03:57 PM ---------- Previous post was at 03:54 PM ----------
https://dl.google.com/dl/android/aosp/nakasi-jwr66y-factory-1e503532.tgz
Code:
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot flash system system.img
fastboot flash userdata userdata.img
fastboot flash boot boot.img

But this file is a .tgz file... How can i flash it?
I've flashed bootloader successfully

zolcix said:
Where can i get image file of the stock rom? I can't find one
Click to expand...
Click to collapse
https://dl.google.com/dl/android/aosp/nakasi-jwr66y-factory-1e503532.tgz
https://developers.google.com/android/nexus/images

How I can install it?
dude, THANKS, its working now, you are great!!

6.0.1 - How to flash?

I am looking for a clear explanation of how to flash Android 6.0.1 with root and encryption disabled without wiping data. With all the explanations through the forum, all the "if's" and "but's" get confusing and can be clear as mud. Thanks for your help.

i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I

nextelbuddy said:
i'm on 6.0 with a stock kernel with encryption disabled and an unlocked bootloader as well.
As far as i can tell you need 2 things.. Flash the System.IMG manually and then we need to wait for someone to post a modified stock 6.0.1 kernel that has encryption disabled too. you can get away with just flashing system.IMG and stay on your older 6.0 de encrypted kernel but I have seen online that wonky things happen when you dont stay up to date on your kernel sometimes.
I
Click to expand...
Click to collapse
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.

how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img

ShaunWinSC said:
I know there is a new boot.img file that has encryption disabled but I'm not sure how or where to install it properly.
Click to expand...
Click to collapse
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
Ovrclck said:
how_to_flash_update_images_without_wiping_data
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
Click to expand...
Click to collapse
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.

nextelbuddy said:
Where did you find or see this new 6.0.1 modified boot.img that has encryption disabled?
all you need is wugfresh tool kit and go into the Advanced settings and choose to flash individual files. and flash the boot.img to your device.
so flash the 6.0.1 system.img first and then flash the 6.0.1 modified boot.img 2nd.
remember that when you flash anything from fastboot, after the item is finished, the device reboots so you need to watch the device and have your fingers prepared to hold down power and volume down so the device goes back into fastboot and doesnt start booting again on its own.
---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------
that works too!
now just to find the modified 6.0.1 boot.img that has encryption disabled.
Click to expand...
Click to collapse
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?

ShaunWinSC said:
Doughnut643 posted it in Android 6.0.1 thread, post #61.
https://www.dropbox.com/s/la4c6f8o5z...e-new.img?dl=0
It's been my understanding that Wug Fresh Tool Kit has been having some issues.
What about recovery, will it have to re-flashed? And what about root?
Click to expand...
Click to collapse
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.

nextelbuddy said:
your recovery should remain as long as oy only flash the system.img and boot.img. you will need to reroot but I cant help you there unfortunately as I am not rooted myself since I need Androidpay to work.
i h avent had any issues with wugfrsh tool kit but if anything you dont have to use it. you can just go to the wugfresh tool kit folder and run the ADB and manually flash with the flash commands manually.
Click to expand...
Click to collapse
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.

I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
ShaunWinSC said:
So you don't think I will need flash TWRP after flashing everthing.
I am hoping enough people chime in on how to do this so I can make a clear set of instructions.
Click to expand...
Click to collapse
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.

nextelbuddy said:
I will let you know in a few min.
I just finished flashing 6.0.1 system.img, bootloader.img, cache.img, modified boot.img you posted and the device is at the android is upgrading screen.
if its successful, I will reboot into my recovery which had TWRP previously. if thats good i will let you know.
---------- Post added at 12:51 PM ---------- Previous post was at 12:18 PM ----------
so I have one problem now.
when My device fully boots up it now says :
"there's an internal problem with your device"
the only reference I can find to this is in regards to the Nexus 9 and flashing the Vendor.IMG file but nothing for phone devices.
any one know anything about this?
I h ave a feeling its because i flashed the stock 6.0.1 bootloader.IMG over my modified bootloader.IMG and I have TWRP installed AND a modified boot.img...
if i could find a new modified bootloader.img for 6.0.1 that would be awesome.
BTW my TWRP is still installed and launches fine.
Click to expand...
Click to collapse
Have u flashed vendor.img ???
That's probably the problem :silly:

kauemelhado said:
Have u flashed vendor.img ???
That's probably the problem :silly:
Click to expand...
Click to collapse
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol

nextelbuddy said:
I did not. i thought that was only for the nexus 9 since the toolkit had that button disabled unless I set my device to Nexus 9. i flashed vendor.IMG and good to go now thanks lol
Click to expand...
Click to collapse
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message

kauemelhado said:
I saw a yt video today (https://www.youtube.com/watch?v=i6Gpi1ruLgM)
He showed that if you don't flash vendor.img, you'll get this error message
Click to expand...
Click to collapse
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!

I have flashed these three Files via the readme commands(fastboot flashing) and did not have my data partition wiped. and now FC's on ubermallow custom rom.

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
Some people are having this problem with EX kernel. But I guess the kernel is not the problem.
I'll flash the update later on today, then i'll tell you how that work for me hehe

nextelbuddy said:
so now I have a new issue. my device doesnt show LTE anymore. only H (im on ATT). if i go into cellular networks and toggle different APNs then wait a min.. LTE shows.. if i reboot the device its back to H again no matter how long i let it sit. I flashed everything except user.img so I have the latest Radio as well. makes no sense :/
thanks for the video!
Click to expand...
Click to collapse
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61

kauemelhado said:
I flashed all the imgs last night (had some troubles with being dumb installing twrp :silly:
But other than that, everything works perfeclty. LTE is fine. (here in brazil at least)
I'm currently on Stock 6.0.1 + EX Kernel + SuperSu 2.61
Click to expand...
Click to collapse
Nice, how did you made it? Did you leave the recovery.img?

Martini3001 said:
Nice, how did you made it? Did you leave the recovery.img?
Click to expand...
Click to collapse
I flashed stock recovery and later on flashed twrp.
I was getting the android of death when booting into TWRP.
So, I did this:
-fasboot flash recovery *twrp*
-fastboot reboot-bootloader
*on your fone* using the volume buttons search for "RECOVERY"
-boot into recovery
-thank me!
lololol

I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?

MPAI said:
I am facing the same problem. After flashing the files manually as below -
1) fastboot flash bootloader bootloader-angler-angler-02.45.img
2) fastboot flash radio radio-angler-angler-02.50.img
3) fastboot reboot-bootloader
4) fastboot flash boot boot.img
5) fastboot flash cache cache.img
6) fastboot flash system system.img
7) fastboot flash vendor vendor.img
I rebooted the phone into bootloader and flashed TWRP. After flashing I could boot into TWRP, but if I reboot and try to boot into TWRP little android guy appears.
What am I doing wrong?
Click to expand...
Click to collapse
after you flash TWRP, if you reboot, the system will flash the stock recovery back if its not the original
after u flash TWRP, u need to boot into recovery, and then flash the expected SuperSU.zip
the supersu zip script will edit the system and disable the flashing of stock recovery

Losing root after rebooting (6.0.1 with SuperSU 2.61 & 2.62)

I've been trying to get help on this matter. I've followed every step to get this resolved other than a factory restore at this point.

GloriousGlory said:
I've been trying to get help on this matter. I've followed every step to get this resolved other than a factory restore at this point.
Click to expand...
Click to collapse
Tell us more. What ROM are you running? Are you on 6.0 or 6.0.1? If on 6.0.1 tells us how you got there. It's the little things that help.

Mr Patchy Patch said:
Tell us more. What ROM are you running? Are you on 6.0 or 6.0.1? If on 6.0.1 tells us how you got there. It's the little things that help.
Click to expand...
Click to collapse
I'm on Stock 6.01. I flashed everything from fastboot (boot.img, bootloader, cache.img, radio, recovery.img, system.img, twrp.img, and vendor.img) and afterwards I went directly into recovery (twrp) and flashed supersu 2.62.
Process:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Then did fastboot flash recovery twrp.img
Boot directly into recovery, flash supersu 2.62, reboot system (DO NOT INSTALL).
Everything works GREAT, then you reboot (power off) and lose root. have to boot into recovery and reflash supersu every single time.

GloriousGlory said:
I'm on Stock 6.01. I flashed everything from fastboot (boot.img, bootloader, cache.img, radio, recovery.img, system.img, twrp.img, and vendor.img) and afterwards I went directly into recovery (twrp) and flashed supersu 2.62.
Process:
fastboot flash bootloader C:\angler\images\bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\angler\images\radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\angler\images\boot.img
fastboot erase cache
fastboot flash cache C:\angler\images\cache.img
fastboot flash recovery C:\angler\images\recovery.img
fastboot flash system C:\angler\images\system.img
fastboot flash vendor C:\angler\images\vendor.img
Then did fastboot flash recovery twrp.img
Boot directly into recovery, flash supersu 2.62, reboot system (DO NOT INSTALL).
Everything works GREAT, then you reboot (power off) and lose root. have to boot into recovery and reflash supersu every single time.
Click to expand...
Click to collapse
If I'm seeing this correctly, it looks like you didn't flash userdata? So you won't lose data correct?
Maybe you should try flashing this first, http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
then flash 2.61. See what happens.

Mr Patchy Patch said:
If I'm seeing this correctly, it looks like you didn't flash userdata? So you won't lose data correct?
Maybe you should try flashing this first, http://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
then flash 2.61. See what happens.
Click to expand...
Click to collapse
I'll give it a try.
Edit: Didn't work

Ok it's strange, on some reboots its fine on some it unroots.

GloriousGlory said:
Ok it's strange, on some reboots its fine on some it unroots.
Click to expand...
Click to collapse
What's telling you it's not rooted?

Mr Patchy Patch said:
What's telling you it's not rooted?
Click to expand...
Click to collapse
Supersu app "There is no SU binary installed"
Okay so first reboot lost root. second boot good, third boot good, fourth boot lost root, fifth boot good.

I'm seeing the same. After flashing 2.62-3, root is fine on 1st and 2nd boot. After that, "...no SU binary installed". Tried reflashing 2.62-3, same results.

snovvman said:
I'm seeing the same. After flashing 2.62-3, root is fine on 1st and 2nd boot. After that, "...no SU binary installed". Tried reflashing 2.62-3, same results.
Click to expand...
Click to collapse
Same here. On 6.0.1
Sent from my Nexus 6P using Tapatalk

For those who are seeing this issue, what was the disposition of your phone prior to this?
For me, I was on 6.0.0 using traditional root (2.52). I fastbooted to 6.0.1 and used 2.62, then 2.62-3 right on top.
I'm in the process of re-fastbooting boot.img, system.img and flashing 2.62-3 to see if it makes a difference.

You need to run the unroot zip before you use the systemless.

Gytole said:
You need to run the unroot zip before you use the systemless.
Click to expand...
Click to collapse
I thought unroot.zip was used for those that were using traditional (2.52 and pre) root? AFAIK, the zip simply removes the pieces left by system root. If there was nothing written to /system in the first place, what benefit would unroot.zip provide? The OP did flash unroot.zip and it didn't help him.
In this post, the instructions explain that if you're coming from 2.60, you can simply flash newer versions right on top (since nothing was written to /system in the first place). If you're coming from system root, reflashing the image will wipe out all the root modifications and allowing one to go systemless.
I did reflash boot and system, then 2.62-3. Same problem--on the 3rd boot, root goes away.

snovvman said:
I thought unroot.zip was used for those that were using traditional (2.52 and pre) root? AFAIK, the zip simply removes the pieces left by system root. If there was nothing written to /system in the first place, what benefit would unroot.zip provide? The OP did flash unroot.zip and it didn't help him.
In this post, the instructions explain that if you're coming from 2.60, you can simply flash newer versions right on top (since nothing was written to /system in the first place). If you're coming from system root, reflashing the image will wipe out all the root modifications and allowing one to go systemless.
I did reflash boot and system, then 2.62-3. Same problem--on the 3rd boot, root goes away.
Click to expand...
Click to collapse
Didja flash the modified 29M boot img or the stock from factory img...

Gytole said:
Didja flash the modified 29M boot img or the stock from factory img...
Click to expand...
Click to collapse
The purpose of systemless root SuperSU is to patch the factory boot image. A modified boot image is used to allow for system root. This thread is discussing systemless root using SuperSU to patch the factory image. As the OP described, we are flashing the factory image. Don't know what you're asking.

snovvman said:
The purpose of systemless root SuperSU is to patch the factory boot image. A modified boot image is used to allow for system root. This thread is discussing systemless root using SuperSU to patch the factory image. As the OP described, we are flashing the factory image. Don't know what you're asking.
Click to expand...
Click to collapse
I had a problem before flashing the modified for some reason. But never mind.

See my post here. I found the modified kernel to allow for system root. Until the lost of root issue is resolved, system root is a good alternative.
Just fastboot the modified boot, reboot into TWRP (using the phone keys, NOT fastboot reboot), flash SuperSU 2.52, and you should be good to go. Be sure to backup beforehand and wipe cache/dalvik for good measure.

P9 hard bricked

This is my first time posting on XDA, so sorry if the formatting is bad.
I've tried to root my P9 lite installing TWRP and Magisk, everything went fine, until the last reboot that caused a bootloop.
Trying to fix this I mistakenly wiped the System partition (instead of Data), reading online people adviced to flash the update.zip, when i tried it I had "unable to mount /vendor" and "unable to mount /product".
I tried the update.app method and the eRecovery tool, but still nothing.
I read that the problem was probably caused by en error in boot.img or recovery.img, so i extracted those files from the firmware and flashed them using TWRP. By doing so i deleted TWRP itself leaving me unable to flash system.img.
I tried to flash it using fastboot, but every time i try to write a command regarding flashing i get a FAILED (remote: command not allowed).
Now i have a bricked phone, i can access fastboot but it doesnt seem to be working. I cant access adb since i can't access the recovery (at least i dont know how to ).
Any advices?

Do you have bootloader unlock code?

Dino_S said:
Do you have bootloader unlock code?
Click to expand...
Click to collapse
Yes I do.

Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it

Dino_S said:
Unlock bootloader again and in fastboot flash system.img and boot from firmware,I used b370
---------- Post added at 12:46 AM ---------- Previous post was at 12:38 AM ----------
Extract from update.zip file update.app and use huawei update extractor and extract files from that system.img and boot.img and put in fastboot folder and flash it
Click to expand...
Click to collapse
I can't, whenever I try using a fastboot command I get "FAILED (remote: command not allowed)

How much is internal data memory in twrp

Dino_S said:
How much is internal data memory in twrp
Click to expand...
Click to collapse
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img

TinkyWinkyJr said:
Around 10 gb, by the way I can't access twrp anymore, since I flashed recovery.img
Click to expand...
Click to collapse
It is showing in fastboot mode unlocked both

Dino_S said:
It is showing in fastboot mode unlocked both
Click to expand...
Click to collapse
Bootloader unlocked and FPR locked (or is it FRP?)

I have same prob yesterday,and showing me same thing,but i flashed twrp again and format data and system to ext4,and from fastboot flash system and boot img and it booted,it is confusing to undestand yours problem
---------- Post added at 01:15 AM ---------- Previous post was at 01:14 AM ----------
TinkyWinkyJr said:
Bootloader unlocked and FPR locked (or is it FRP?)
Click to expand...
Click to collapse
Mine showing FRP unlocked

hey guys
i have the same problem, had rr marshmallow on my p9 lite and tried to flash the new recovery for nougat by old droid. since then i cant enter nowhere without fastboot. phone unlocked and frp unlocked. does anybody have another idea. flashing stock recovery did not work, flashing twrp did also not work. need more ideas, erecovery and dload method do not work, i have acces to fastboot

Try to flash the correct oem.info.I've had the same problem with my P9(EVA-L09).

Brick (error mode) after update_command: only fastboot works.

Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?

please help I can't buy another phone it's urgent...

p181153 said:
Hello I wanted to install Oreo on my PRA-LX1 following this guide
https://www.haky86.com/2018/05/12/install-emui-8-0-huawei-p8-lite-2017/
I was on official EMUI Nougat firware, I downloaded LX1C432B322 of 2018.04.13 what he said, installed nocheck recovery and then update_command. Reboot, title, nothing works except fastboot. I re-unlocked the phone with oem unlock and after reboot same.
I tried to flash twrp-3.2.1-v3.5-prague.img again to fix but length error with "fastboot flash recovery"
I tried to flash his OreoTWRP.img with "fastboot flash recovery_ramdisk" and it pass, reboot but I can't boot to recovery.
Pressing VolUp + Power does nothing, "phone can't be trusted" screen with the eRecovery option (VolUp for 3 seconds) but eRecovery is dead (error mode)
Maybe this OreoTWRP worked but how to bot to recovery now ?
Click to expand...
Click to collapse
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.

@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?

haky 86 said:
I'm not responsible of bricks caused by people since most of them not follow the steps I wrote.
Click to expand...
Click to collapse
Tell me where I said you are responsible of bricks ? I followed the steps you described, If you don't want to help just don't say anything

neondragon1909 said:
@haky 86 (I'm assuming you were the one who wrote that guide) is the guide for updating from nougat to oreo or updating an Oreo firmware to the latest?
Click to expand...
Click to collapse
This is I want to know. He don't said it but I tried to flash oreotwrp from nougat and it said partition error using recovery_ramdisk. And the nocheck didn't work, so I took another nocheck for this TWRP and put the update_package command and then this

I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.

haky 86 said:
I just update my guide, the sample I wrote it was emui 8.x because I'm already at oreo. but procedure is same the only thing change is recovery, on oreo called Recovery Ramdisk on nougat called just recovery, please check the updated article here the screenshot.
Click to expand...
Click to collapse
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update

p181153 said:
Ok thanks but now I can't do anything on my phone I just have bootloader. How to restore a device which is bricked followed a bad update
Click to expand...
Click to collapse
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater

neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
Thanks any detailled guides for that so I'll not make the things worst ?

neondragon1909 said:
Download the nougat rom you were on before. Extract update.app to get the recovery. Flash it using fastboot. Then try dload method.
Or flash nougat twrp and try flashing the nougat rom via HuRUpdater
Click to expand...
Click to collapse
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead

p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
p181153 said:
I can't flash recovery from update.app of nougat rom. It say partition length error. recovery_ramdisk say partition error...
Can I flash the system.img ? There are fastboot.img in the update.APP. Can I flash recovery after flashing fastboot ?
I need to be sure because if I flash fastboot and lost it my phone will be really dead
Click to expand...
Click to collapse
Use fastboot flash recovery recovery.img not recovery_ramdisk

neondragon1909 said:
Use recovery not recovery_ramdisk
---------- Post added at 07:19 PM ---------- Previous post was at 07:18 PM ----------
Use fastboot flash recovery recovery.img not recovery_ramdisk
Click to expand...
Click to collapse

I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything

p181153 said:
I can't flash recovery how to restore my phone using fastboot please
It's urgent if you don't know how to solve that at least tell who can do that I can't let my phone like that I miss everything
Click to expand...
Click to collapse
Try unlocking bootloader again

neondragon1909 said:
Try unlocking bootloader again
Click to expand...
Click to collapse
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...

p181153 said:
bootloader is unlocked... read first post "re-unlocked" the bootloader... I need serious answers. Actually I download a nougat firmware and try this guide
And this guide tell me to extract 4 img files using Huawei Firmware Extractor. I downloaded 2 full OTA firmware and can't find cust.img files...
I just want to restore my phone...
Click to expand...
Click to collapse
please help me can't restore my phone when I want to flash boot of a nougat firmware it say partition length error.....
when I want to flash recovery same...
I can't do anything I need my phone it's 3 days already I miss important calls...

This forum is called xda-developers but there are no developers or someone who really know how android works. I can't found anyone who can help me even on other forums. I have access to something which can save my phone but NOBODY know how to use it. How disapointing.

why