Database Info

[Q] [solved] Reverted from EOS to stock, now unable to update to 3.1 (green bot of !)

Hello,
I have the MZ601 (Xoom UK 3G) and had EOS Everest JB stable on it.
Now I wanted to go back to stock. I downloaded the original firmware from Motorola, flashed the img files with adb and everything was fine (I did not relock the bootloader). The first OTA went fine too, now I am on Android 3.0.1 (H.6.1.-38-1).
It now detects the next OTA (about 44 MB, 63.5.25.en.EU), downloads it, tries to install it but at about 1/3 of progress the green bot of ! appears. I reflashed the stock firmware several times now, same result.
Then I googled, flashed Tiamat CWM recovery, rooted the device and then did:
adb remount (got message: succeeded)
adb shell rm /system/recovery-from-boot.p (message: no such file or directory)
adb shell rm /system/etc/install-recovery.sh (no message, so guess it worked)
Now I have no idea what else to try. I'd like to get back to stock ICS.
edit: reflashed back to stock once more. This time I entered recovery mode before I applied the very first OTA and the green bot of ! already appears, what's wrong here?

Hi,
It looks like your problem is not big deal. Just try flashing again all the files and principally DON'T FORGET TO FLASH RECOVERY! And I don't see why wouldn't you lock bootloader , if you really wants it unlocked and go to stock ICS I'd recommend you to flash stock, lock bootloader and then you update, after you get to the version you want unlock again :thumbup:
Wish you the best luck
Any problems please give me an up!

​Thanks for your reply!
I think I flashed recovery with the specific adb command (see below), not sure, not really an expert. :/ I even wiped dalvik cache and factory reset in cwm recovery before flashing back to stock.
Here's what I did in detail when reverting to stock:
I downloaded MZ601_H.6.1-38-1_Retail_Europe.zip from the official Motorola website, extracted all files and used these commands in adb:
Code:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Also, I noticed the green bot of ! appears after reboot when I enter recovery mode even before I flash the very first OTA (so just after flashing the stock files and reboot). Looks like recovery is somewhat broken or so?
I didn't want to relock the bootloader simply because I might want to root the device once I am back on stock ICS. Basically, I just wanted to get away from a custom ROM (Team EOS).
Would locking the bootloader make a difference for my success? According to google it doesn't but I am no expert to judge it right.

Yea, it looks like something is going wrong there...
Try downloading the files again, and then flash recovery. If you have no success try locking your BL, maybe it can works. The two times I went back to Stock I relocked my BL and had no problems to update via OTA. Then you relock your BL and use LordAIOTool to root again, which can easy your work...
Also you should try erasing system, recovery, cache and data before flashing, but it looks like what you did is fine.
Good luck

Thanks! I will give that a shot and post the result here.
By the way, that is one thing I read about and didn't dare to try yet: formatting system.
From what I read, after formatting /system the tablet will no longer be able to boot into android. In that case, how can I perform adb commands still? Afaik USB debugging has to be on but I will not be able to get into settings (due to lack of boot) and turn it on (and it will be off after reflashing afaik).

When you format system you can't boot in Android, but you can still flash things via fastboot, which uses a different protocol from adb. There was one time I had to format system to fix a cellphone, but if you don't want to try that, no worries , it may turn out without risking

I believe in order to upgrade you need to lock the BL. Once you update you can unlock it again.

Okay, downloaded the image again, this time via XDA. Suprisingly, all files were flashed in less than a min each (sometimes flasing system.img took half an hour or longer). Same result though. Since I forgot to lock the bootloader I flashed everything again after reboot:
Code:
>adb reboot bootloader
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 49.293s]
writing 'boot'... OKAY [ 2.155s]
finished. total time: 51.477s
>fastboot flash system system.img
sending 'system' (262144 KB)... FAILED (remote: (00120003))
finished. total time: 1196.176s
Not sure why it failed here, worked dozens of times. So I simply decided to reflash system.img once more in the same run:
Code:
>fastboot flash system system.img
sending 'system' (262144 KB)... OKAY [ 25.391s]
writing 'system'... OKAY [ 14.744s]
finished. total time: 40.136s
Worked fine apparently, then continued from there as normal:
Code:
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
fastboot oem lock
All went well this time, no error messages on the latest full reflash or locking bootloader. Then rebooted, and now it is stuck at the Motorola boot screen:
Code:
Failed to boot LNX 0x0004
Starting RSD mode 2
(charger information bla bla here)
Not sure why this happened and what this actually means? It won't boot up and since the bootloader is locked I can't enter recovery or anything. What do I need to do now?

Man... You forgot to flash the kernel (boot.img)!!! And it's probably appearing because of this small mistake!!! Now that you're on RSD Mode 2 you have to fix it another way... I never went to it (only went twice to mode 3), so sorry, I can't help you this time , I will search a little and see what I can do for you.

My mistake on posting, I did flash boot.img before that, corrected my previous posting.
Now I am stranded. And I can't even turn off the device on boot screen.
edit: rescued it, thanks to this posting:
Pushed power + vol up for reboot, waited 5 sec, then held vol down until fastboot appeared (kept pressing the button for about 17 sec until fastboot showed up).
Once there, I unlocked bootloader successfully again to flash all stock files. Xoom booted up bravely afterwards, phew.

Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.

Landorin said:
Another good news. This time it also applied the 2nd OTA successfully finally! I don't know why it worked this time. Either it's because I (somehow badly) locked the bootloader and unlocked it again OR because I did the flashing this time from my laptop. On the previous attempts I had the Xoom connected via front USB on my desktop computer, maybe that wasn't a good idea after all (flashing on the laptop connection went even faster, too, about 20 sec the most for each file). In the past I used to flash from my laptop as well and never ran into issues either - should have sticked to it maybe.
I guess I won't go for custom ROMs again anytime soon, I've really had it, especially not the one I used to use. Simply not worth the hassle, considering the Xoom wasn't even faster and didn't work with virtual phone providers anymore.
Click to expand...
Click to collapse
Glad you made it
Congrats!!

Bricked for life? Partition error?

Hello!
I have a small problem. A week ago died my phone when i unlocked the lockscreen one evening. Thought that the battery was empty, i put it on the charger and started up the phone a few hours later and the only thing that happens is that Google logo is displayed, then it starts over again. I can go into recovery and fastboot, but it does not matter what i do there. Managed to get it to be connected as a USB drive so I got out the pictures from it. But if you make a complete factory reset including data and restarts there everything left! Tried to run "fastboot format cashe" but it only return "FAILED (remote: flash write failure) "
The phone is rooted and bootloader is unlocked, i had a custom rom installed, and it had worked since beginning of summer.

Have you already tried to reflash stock rom with fastboot? Maybe that will help to get your partitions working properly...

i followed a guide on androidrootz dot com, "how-to-unroot-nexus-5-complete-stock" but directly when i try to flash bootloader i get a error message.

Does the bootloader remain unlocked? What error are you getting when flashing stock?

audit13 said:
Does the bootloader remain unlocked? What error are you getting when flashing stock?
Click to expand...
Click to collapse
Yes! It remains unlocked! Heres the "print screen"
C:\UnrootNexus5>fastboot flash bootloader-hammerhead-HHZ11d.img
unknown partition 'bootloader-hammerhead-HHZ11d.img'
error: cannot determine image filename for 'bootloader-hammerhead-HHZ11d.img'

You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.

g90814 said:
You could try Wug's Nexus Root Toolkit and get it back to working. If you can get to fastboot screen, then it can get you up and running again.
You'll have to google it, for some reason I got set back to a new user, even though I've been posting on this forum for quite awhile.
Click to expand...
Click to collapse
I Have tried that also, here is the print from that:
Connectivity Status: Fastboot Device Connected
Flashing bootloader-hammerhead-HHZ11d.img to BOOTLOADER partition...
fastboot flash bootloader "C:\UnrootNexus5\bootloader-hammerhead-HHZ11d.img"
Rebooting your device into bootloader mode...
fastboot reboot-bootloader
But when it boots up again its still unlocked...

fastboot flash bootloader bootloader.img

Oh! I missed one word. Will try it tonight!

Nope.... Doesnt work either....
C:\UnrootNexus5>fastboot flash bootloader bootloader-hammerhead-HHZ11d.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.256s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.457s

Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.

i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything

audit13 said:
Looks like the onboard memory chip is damaged or has failed.
My N5's bootloader would always relock on reboot so I could never flash a stock ROM.
Click to expand...
Click to collapse
Damn! thats what im afraid of....
ChocholateMaster said:
i don't think you have unlocked bootloader , maybe there is some errors try with "fastboot oem unlock" and then try to flash everything
Click to expand...
Click to collapse
The telephone is unlocked, the lock is open when i reboot the phone.
C:\UnrootNexus5>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s

what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv

I don't know how it got damaged. One day, ti started bootlooping and the bootloader had re-locked on its own even though I unlocked it straight out of the box. I booted into fastboot, unlocked the bootloader, and it only too a few seconds to erase everything. I immediately rebooted in fastboot and the bootloader was locked again. This unlock/relock happened over and over.
I booted into recovery and tried a factory reset but recovery could not mount cache or data to perform the erase.
My phone just kept getting stuck at the Google logo or bootlooping.

ChocholateMaster said:
what if you try "fastboot oem lock" and then again unlock it maybe will work
and @audit13 to get chip damaged? i'm not saying that is not possible but it's only few percent
oh and can you enter in recovery mode? if as you said yes firstly try to flash this http://d-h.st/VcCv
Click to expand...
Click to collapse
I have tried that also, when im just type "FASTBOOT OEM LOCK" it lookes like this:
C:\UnrootNexus5>fastboot oem lock
...
OKAY [ 0.054s]
finished. total time: 0.054s
PERFECT!?!? But when i reboot its still unlocked.... if i do first lock, then unlock without rebooting, i get a new meny on the phone where i have to chose if i want to unlock my device. and if i chose yes it will reboot and its the same again....
How do i download that file??? I just got an EXE file, and i dont want to run that!

If it's not sticking on a reboot, that means the memory is most likely gone bad. I guess you could try using the diagnostic tool, which would confirm if the memory is bad.
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301

maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
---------- Post added at 03:41 PM ---------- Previous post was at 03:39 PM ----------
ChocholateMaster said:
maybe it's just corupted bootloader @kardanmannen go to http://d-h.st/VcCv and press download now you should get .zip file which you can flash in recovery using adb sideload
Click to expand...
Click to collapse
after flashing it can take up to 15 mins to turn on because of first boot

@kardanmannen any news?

I'm getting more and more sure that the memorymodule is faulty in the phone. If you reboot in Recovery and select filemanager, for example you remove a directory with files, if you restart the phone, the directory is there again! And when you start it up in recovery and connect it to the computer, theres a few directorys you can write/delete/. Similarly, if you run "fastboot oem lock" and reboot it, its locked the first time it is started up and then the second time it is unlocked again.
Lost hope a little there and went off and ordered a Nexus 6P, hoping it will arrive on Wednesday.

Hard bricked? Can't get into recovery, can't unlock bootloader

Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!

How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.

sticktornado said:
How many system images do you need to flash? Sometimes there can be more than 6, sometimes there can be fewer.
Click to expand...
Click to collapse
I know, I flashed the correct number of system images that were in the zip file.
Thanks,

rent0n said:
Hello,
I think my XT1541 (16GB/2GB Retail GB) with locked bootloader might be hard-bricked.
I was running the stock 5.11 firmware when I did the 6.0 update and since then my phone is stuck in a bootloop.
Motorola won't repair it because I had to replace the screen and the phone is out of warranty.
I can access the bootloader but if I select recovery mode the phone just keeps bootlooping and I can't get into recovery.
I followed the instructions here to flash a stock firmware using fastboot. All the steps complete successfully but after rebooting, the phone is still stuck in a bootloop and I can't get into recovery.
I wanted to install a custom recovery but I'm unable to unlock my bootloader because of this error:
Code:
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
Obviously I can't check that option as the phone won't boot.
So, is it hard bricked? Is there anything I can do to get my phone to work again?
Thanks a lot for your help!
Click to expand...
Click to collapse
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

prasi.ram10 said:
If u are bootlooping when trying to enter recovery , then prolly the recovery is the issue. I'd suggest flash the recovery.IMG again and then proceed with flashing the rest of the .IMG files.
Click to expand...
Click to collapse
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?

rent0n said:
So basically:
Code:
fastboot flash recovery recovery.img
fastboot reboot
and then check if I can access recovery? Or issue that command and then all the other fastboot commands in the guide?
Click to expand...
Click to collapse
I tried that and it didn't work. When I try to go into recovery mode the phone keeps bootlooping.
One thing I noticed is that when I try to format cache or userdata I get this error:
Code:
$ fastboot format cache
formatting 'cache' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.013s
I think there might be something wrong with the file system in my partitions. How can I manually format my partitions?
Thanks,

man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there

therealduff1 said:
man , if you really need recovery, type fastboot boot recovery.img . It will temporaily boot you into stock recovery. Wipe cache and data there
Click to expand...
Click to collapse
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...

rent0n said:
Thanks, but this is what I get when I try do do that:
Code:
$ fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.736s]
booting...
FAILED (remote failure)
finished. total time: 0.746s
There must be a way to restore this phone to a working state! I can't believe it's so messed up after an official update...
Click to expand...
Click to collapse
What os were you running when the phone screwed up ?

therealduff1 said:
What os were you running when the phone screwed up ?
Click to expand...
Click to collapse
I was running 5.1.1 when I got the notification for the 6.0 update.
I've noticed that trying to flash 5.1.1 firmware with fastboot gives me errors (preflash validation failed) while the 6.0 work "fine" (i.e.: I get OKAY after every step but then the phone is always stuck in a bootloop).
Thanks!

DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..

therealduff1 said:
DO NOT ATTEMPT TO DOWNGRADE BOOTLOADER.IMG OR GPT.IMG !!!!!!! DONT FLASH LOLLIPOP VERSION OF THOSE FILES ON A DEVICE RUNNING 6.0
plz tell me u didnt flash those files..
Click to expand...
Click to collapse
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.

rent0n said:
Well I wasn't sure what version I was running to be honest so I think I tried to flash the gpt.img from 5.1.1 at some point but it failed with the preflash validation failure. I've always only flashed the 6.0 firmware files.
Click to expand...
Click to collapse
Have you gave this a try?

heavy_metal_man said:
Have you gave this a try?
Click to expand...
Click to collapse
Yes, no luck unfortunately.
I think I might have flashed the 5.1.1 bootloader after all - is there any way to recover from there?
Thanks,

Bump!
Does anyone have any other suggestion please?
Thanks,

Last bump
I'm going to sell this on eBay as non-working then unless someone comes up with a clever solution?
Thanks for your help!

Try flashing once more starting with the gpt.bin (that should hopefully take care of raw partition error) and skipping the bootloader altogether. Also, may be worthwhile to try mfastboot.exe instead of fastboot.exe.

I have this same issue, but I haven't flash 5.1.1 Files, I Only tried with 6.0 Brazil Retail.
I also tried to flash gpt to get rid of the "raw" partition, everything goes ok but still displaying that error. Anyone can help?

I got the same problem with my Moto E 2015... If I find a solution I will reply it in this topic..

Honor View10 is stuck at 'Your device is booting now', cannot enter recovery.

My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @shashank1320 @oreopie
All this perhaps happened because I tried changing the file system of data and system from twrp.

ankan1993 said:
My Honor View10 is stuck at 'Your device is booting now', cannot enter recovery. I tried rectifying my twrp that couldn't unmount anything and wiped up almost everything, but ended up with a boot loop.
Now my device is stuck at 'Your device has been unlocked and can't be trusted. Your device is booting now' screen. I tried using the dload method to restore everything back but the device won't go past this screen.
I tried flashing it using fastboot mode by flashing system, ramdisk and what not, did get a success every time, still, the device won't go past this.
I need genuine help on this, please. Anyone? @2WildFirE? @Einwod? @[email protected]
All this perhaps happened because I tried changing the file system of data and system from twrp.
Click to expand...
Click to collapse
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there

2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
Because custom recovery wouldn't mount anything.
Had no idea that twrp isn't ready for pie.
For both stock and ereccovery, do I use ramdisk_recovery command?

2WildFirE said:
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
How exactly would one go about this?
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img for example only results in FAILED (remote: 'Command not allowed').
Bootloader is unlocked.

If I'm right, try fastboot flash erecovery erecovery.img

2WildFirE said:
If I'm right, try fastboot flash erecovery erecovery.img
Click to expand...
Click to collapse
Sadly there is no erecovery.img and if i try to flash either of the many erecovery files into what i assume would be their respective partitions i get the same error.
Which i thought was a good sign because that might have meant that i couldn't have ****ed them up. But maybe it isn't.

OK try erecovery ramdisk and erecovery kernel to flash

PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.

2WildFirE said:
Why you tried changing filesystem on data?
Twrp isn't ready for pie ? atm
Flash stock recovery and erecovery, then boot to erecovery and restore from there
Click to expand...
Click to collapse
UPDATE: When I reboot the smartphone it displays "Data partition was damaged seriously! and you are recommended to format it to recover your phone".
Smartphone works, but even after a factory reset it still displays that message when it boots up it gets stuck at 'Booting up'.
What can I do @2WildFirE?

180190 said:
PHP:
fastboot flash erecovery_kernel ERECOVERY_kerne.img
Sending 'erecovery_kernel' (24576 KB) OKAY [ 0.587s]
Writing 'erecovery_kernel' FAILED (remote: 'Command not allowed')
Finished. Total time: 0.614s
for example, the result is always the same.
Click to expand...
Click to collapse
Because this is not the right command to give. I am not sure what the right command would be though.

Okay, so I have recovered my phone after spending a sleepless night working on it.
Tried several combinations to see this resolved.
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device. Once it came back, it took me to erecovery.
From there, I started downloading the file from the recovery and did a reboot after the installation.
My Honor is working fine now.

ankan1993 said:
But, what really worked out for me was that I discharged my device twice and kept trying flashing stock rom and several relative recoveries.
After flashing stock recovery I discharged my device.
Click to expand...
Click to collapse
What exactly have you done?

Sinerty said:
What exactly have you done?
Click to expand...
Click to collapse
Flashed the 9.0 full ota files several times, flashed full otas of 8.0. Flashed a random recovery from an older ota. I then discharged my device as I was totally out of options. When I put it on charge it turned back on and after few minutes took me to erecovery.
And now I cannot root my device as twrp isn't there for pie yet. Honor sucks.

Thread closed since it's a duplicate.
Please read here: https://forum.xda-developers.com/honor-view-10/help/honor-view10-stuck-device-booting-enter-t3889376

Stuck in fastboot no recovery

Hello guys I need some help. I'm stuck in fastboot mode with no recovery or OS too l, let me retrace my steps.
I had my px3 rooted on stock but I was bored with stock and tried to flash bootleggers rom and followed instructions to wipe "everything" but internal storage, so I did including storage under internal storage and flashed the ROM and twrp with it. After it just rebooted back to recovery every time I tried normal boot. (I'm assuming I F'd up by wiping storage). So I googled what to do about looping recovery and one suggestion was to factory reset so I did; I can no longer access recovery. I've tried flashing factory image, flashing the twrp zip, trying to boot straight to twrp, I can't get to adb sideload and it says "no valid slot to boot" on fastboot screen any suggestions?
Got another on fastboot, "error booting boot.img"

Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.

fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start

wergrun said:
Yes it does and I've got everything from twrp .zip and .IMG, factory images and ota zip.
I did make progress just now and switched to slot B and got TWRP to show up:laugh: might just sideload OTA and pretend this never happened
Update, adb sideload taking too long to start
Click to expand...
Click to collapse
You need to get back to fastboot, and run the flash all bat file from the full factory image.

TonikJDK said:
You need to get back to fastboot, and run the flash all bat file from the full factory image.
Click to expand...
Click to collapse
I tried that but I keeps giving me an error, I'll post it when I get the chance

Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"

fury683 said:
Does your PC recognize the phone in Fastboot mode? I would try flashing the full factory image again. Ensure you have the latest platform tools and the correct firmware for your device.
Click to expand...
Click to collapse
I have the same issue, except my computer will not recognize the device in fastboot. I tried two different computers, Windows 10 and laptop running Linux.

wergrun said:
Problem SOLVED! used video by MaowDroid "Pixel 2 (XL): Un-root and return to stock using factory images"
Click to expand...
Click to collapse
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....

SS823 said:
Followed the video, but I get an error:
'FAILED (remote: Failed to write to partition Not Found)'
I've tried: bootloader, bootloader_a, bootloader_b and bootloader_other and get the same error.
I'm stuck....
Click to expand...
Click to collapse
I did get that too but it was because I forgot to put a space after "bootloader_a ", are you Stuck at around the 9 minute steps?

Yes, right around the end at 9 minutes. Everything works fine - bootloader, radio, etc. When I get to the end of the img zip file I get this message:
checking product...
OKAY [ 0.060s]
checking partition-exists...
FAILED (remote: variable not found)
finished. total time: 0.360s
I am at a loss.