Database Users

FAILED (remote image update error) now offering money for a solution!

As it says above THIS is why i cant boot up hero roms or any other that doesnt use cupcake/donut boot does ANYBODY have ANY IDEAS!!??!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Also tried using adb shell to flash the boot but get error writing on block xxxxxxxxxx

I used RA_dream-v1.2.2 today threw ADB. Placed .img on root of sd,
Dont use mount -a, mount /system, or mount /sdcard
Just use
# mount
# flash_image recovery /sdcard/recovery-RA-dream-v1.2.2.img
http://forum.xda-developers.com/showthread.php?t=566669

Its the boot img that wpnt flash not the recovery but thanks anyhow

bumping this thread as i am pretty stuck.Not being able to write the boot.img means even my nandroid wont work

can you get a different boot.img to try it might be curupt
found this
http://forum.xda-developers.com/showthread.php?t=509248
use adb shell
also i see you deleted recovery installed new recovery removed system then you tried to install boot
did you try to install system first before both recovery and boot
i'm no expert lol
found some other stuff
How to restore from your backup file
1. Download one of the above signed SPL updates and rename it to update.zip
2. Copy update.zip to the root of your SD-card
3. Copy the Nandroid backup files data.img, system.img, and boot.img from your SD card to the folder C:\Android.
4. booting your Magic into recovery model
5. select [Alt + S] – Apply sdcard:update.zip
6. select [Home + Back] – reboot system now
7. After reboot it will update upgrade/downgrade your SPL version, then power off your Magic again
8. Push “Back” + “Power” to HBOOT model
9. double check your SPL version is upgrate/downgrate
10. Plug the USB cord back into your phone. The screen on your phone should say fastboot.
12. Press start, go to run and type cmd (If you are on Vista just type cmd in the search box and hit enter). The command prompt will pop up.
13. Type cd C:\android
11. then enter the following commands C:\android >
fastboot erase system -w
fastboot erase boot
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot reboot
12. After reboot your Magic, it need about 2-5 min to restore
13. then a band new original Android 1.5 is restored

Yes i have tried that, The problem is the boot.img. I cant flash it! Nandroid restore fails due to boot.img (cannot be flushed!) Thanks for the speed yresponse but still no joy

bonesy said:
Yes i have tried that, The problem is the boot.img. I cant flash it! Nandroid restore fails due to boot.img (cannot be flushed!) Thanks for the speed yresponse but still no joy
Click to expand...
Click to collapse
Did you follow ALL steps while rooting your 32B?
I'm almost 100% sure that you are using your 32B with a 32A radio and rom, right? Complete the rooting by following the "Revert to 32B Radio and ROM" exactly to the letter in this thread. Do not try to do something else or you'll brick it.

i followed all steps apart from using the gold card as i couldnt make one and reverted back to 32B using your steps. I also did it all again but using flashrec.apk?

try this flashrec.
worked for my 32A
http://zenthought.org/content/project/flashrec

Done the flashrec thing, Quite a few times now i have a feeling as it was repaired by htc and sent back they have made it so the boot.img cannot be written in any way, If i use a friends nandbackup of hero it fails (not that it says so) and just keeps on the splash screen untill the phone becomes so hot it switches off! Giving up on this, Gone back to standard (rooted) rom and will await the sense update (fingers crossed)

Stil lthe same problem...although it WILL let me flash sapphire boot just not a modified boot see here....
First flashed boot.img is the google ion boot off of the htc site
Second is the tattoo boot.img modified for the sapphire. Any ideas?
Anyone know where i can get the Google Ion hboot from? just wanna try one more thing before i give up!

Have you posted this in Dream Q&A? That forum is way more active and there is alot more knowlege on things like this. Maybe send David1077 a PM. I feel bad because I have looked at your post for quite a few weeks now with little help. Good luck

i would but am afraid of a ban for posting in wrong forums,ive already done that lots!

somprogress
seems lile i can fastboot boot the img but it just loops at the boot screen?as i say donut roms work fine but ANY sense ui fail at line 92
Right im now offering £25 if anyone can get sense ui working on my phone.any info they need i will give!

bonesy said:
Stil lthe same problem...although it WILL let me flash sapphire boot just not a modified boot see here....
First flashed boot.img is the google ion boot off of the htc site
Second is the tattoo boot.img modified for the sapphire. Any ideas?
Anyone know where i can get the Google Ion hboot from? just wanna try one more thing before i give up!
Click to expand...
Click to collapse
http://www.4shared.com/file/143324302/e942c9d8/boot.html
not to sure what your asking for but this is a boot.img from my signed-google_ion-img-14721
have you looked here iknow you would of but just in-case
http://developer.htc.com/google-io-device.html
my original boot.img
http://www.4shared.com/file/143325952/211edf2e/_2__boot.html
this one is from inside the MLIGN-MagicV1.0-FINAL rom
http://www.4shared.com/file/143326459/aca13a1b/_3__boot.html

the problem is i cant write the boot img in any way.Only original boot.img files not any that are modified.
Its the HBOOT i need to try, But thanks

bonesy said:
the problem is i cant write the boot img in any way.Only original boot.img files not any that are modified.
Its the HBOOT i need to try, But thanks
Click to expand...
Click to collapse
so what is the hboot?
what are you excactly asking for

The hboot is the spl, im asking for the dev one as its naturally enabled for fastboot therefore im trying to trick my phone to make it think its the dev phone (Google ion) hopefully bypassing the "REMOTE: image update error'' when writing boot.img

have you tried the one i'm on Engineering SPL 1.33.2004 by Crios
Engineering SPL 1.33.2004 by Crios is actually a hex-edit of SPL 1.33.2005 to fool updates.

Cannot flash bootloader, recovery factory reset

My a500 cannot perform factory reset or flash rom, and reflash recovery doesn't update the recovery, even i tried to flash bootloader using apxflasher it stuck at stage 2...
here is the situation.
im using teamwin recovery, recently i couldnt flash any rom, nor wipe all partition.
every times i flash rom or wipe partition, reboot, my tablet will back a previous state, is like every times i reboot my tab, it will restore to a "backup"
i called it restore is because all the changes i made after reboot will gone.
i tried to flash other recovery using the fasboot, it doesnt replace the teamwin recovery.
i tried use apxflasher to flash bootloader again, i get stucked in stage 2 uploading image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
finally i tried flash the euus, but i got N/A for the new image version and stuck at there.
Anyone can help me with this?

chinseng85 said:
My a500 cannot perform factory reset or flash rom, and reflash recovery doesn't update the recovery, even i tried to flash bootloader using apxflasher it stuck at stage 2...
here is the situation.
im using teamwin recovery, recently i couldnt flash any rom, nor wipe all partition.
every times i flash rom or wipe partition, reboot, my tablet will back a previous state, is like every times i reboot my tab, it will restore to a "backup"
i called it restore is because all the changes i made after reboot will gone.
i tried to flash other recovery using the fasboot, it doesnt replace the teamwin recovery.
i tried use apxflasher to flash bootloader again, i get stucked in stage 2 uploading image
finally i tried flash the euus, but i got N/A for the new image version and stuck at there.
Anyone can help me with this?
Click to expand...
Click to collapse
When you tried the EUUS did you follow the flowchart in the second post of this thread? http://forum.xda-developers.com/showthread.php?t=1816560
I just ran a EUUS fine following the flowchart - But had a result similar to yours when I didn't unzip the EXE and fill in the CPUID.txt file.

I'm in the same situation, no way to get the v8 UNL BL, stops at stage 2 (BT's apxflashtool) and "3/4 recovery" with AfterOTA TOOL.
I shall try the EUUS flashing (will delete your internal memory), but now I'm very busy so I renounced..
The EUSS file flashing should help

Wedee said:
When you tried the EUUS did you follow the flowchart in the second post of this thread? http://forum.xda-developers.com/showthread.php?t=1816560
I just ran a EUUS fine following the flowchart - But had a result similar to yours when I didn't unzip the EXE and fill in the CPUID.txt file.
Click to expand...
Click to collapse
yes i did unzip it to a folder, and put in my cpuid. i got my cpuid from dmesg dump
MadMav88 said:
I'm in the same situation, no way to get the v8 UNL BL, stops at stage 2 (BT's apxflashtool) and "3/4 recovery" with AfterOTA TOOL.
I shall try the EUUS flashing (will delete your internal memory), but now I'm very busy so I renounced..
The EUSS file flashing should help
Click to expand...
Click to collapse
im not sure why i cant get the new image version. tried on winxp and win7

chinseng85 said:
yes i did unzip it to a folder, and put in my cpuid. i got my cpuid from dmesg dump
im not sure why i cant get the new image version. tried on winxp and win7
Click to expand...
Click to collapse
Couple of ideas to try...
Make sure that when that screen comes up there is not a second window it spawned hiding behind it... For me when it got to that screen I saw another window pop, and it was hidden behind the main, the popup window walks you thru the next steps of setting APX mode, plug in cable, hit ok......
Another thing to try is Right click the PBJ20upgrade.exe and choose "Run as Administrator"
Finally download a new copy... when you unzip it you should end up with Several files and then two folders /Image and /usbpcdriver. The /Image folder has all the img files it needs to install. In the root there is a file called version.cfg that when I view inside it seems to have the info that the program uses to tell what version it is going to install... Hazzard a guess that if that file is missing it might not know what its going to install.

[Q] [Fastboot] Can't flash Stock ROM

Hello there!
I have a Nexus 7 Device, I rooted it using a toolkit, everything was working great, then I messed up a little and I need to restore it using a Factory Image (a.k.a Stock ROM)...
The problem is, when I try to flash the .zip, it gives me the following error:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
According to some tutorials, you type the following commands to flash a ROM:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update ROM.zip
Click to expand...
Click to collapse
Because I'm afraid of something going wrong, I didn't erased any partition, so if for some reason the flashing procedure stops, I have the old data/partitions working because I didn't erased any, I just used the following command:
fastboot -w update ROM.zip
Click to expand...
Click to collapse
So, the questions are:
Do I need to erase the partitions first before trying to flash the Stock ROM?
Should I try flash each .img separately?
Additional Information:
Android is working, I'm able to boot with success.
Bootloader unlocked.
I didn't flashed any custom Bootloader/Recovery/ROM, everything is from Factory/Stock.
I have tested flashing the ROM under Windows and Linux (Ubuntu), it gives me the exact error.
The .zip I'm using isn't corrupted. (And it's directly from developers.google.com)
If flashing without erasing the partitions worked, I would erase them (To delete ALL data/trash) and flash it again...
P.S: First post!

I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hello!
Thanks for the answer, I tried to flash system.img and it worked, fastboot automatically erases the system partition.
I have now a clean system, thanks!
For other people with the same problem as me:
1 - Enter Fastboot Mode
2 - Extract system.img
3 - Run "fastboot flash system system.img"
4 - Enter Recovery Mode and do a "Factory Reset" (Optional, I guess)
5 - Enjoy!

Spenzert said:
fastboot automatically erases the system partition.
Click to expand...
Click to collapse
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers

bftb0 said:
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
Click to expand...
Click to collapse
I believe fastboot really erased the partition, there's no "SuperSU" anymore and I have attached a screenshot of fastboot erasing the partition.
Cheers!

I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?

bftb0 said:
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
Click to expand...
Click to collapse
Android SDK Manager says "Rev. 16.0.1" (Platform-tools), maybe fastboot erased the partition first because I used "fastboot flash" instead of "fastboot update"...
A little off-topic:
I tried to root manually my Nexus and it's really easy, I might make an updated tutorial soon on how to root it manually
Have a good day!
Edit: I tried to flash TWRP (Recovery) and it didn't erased the partition first.

No OS installed mate 9

Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...

scrutnizing said:
Hello everybody, i was handed a mate 9 handset from a friend in as is condition.
I don't know what have it been through.
The phone's back shows it is MHA-l29
Trying with buttons:-either i can enter erecovery connect to wifi. and the recovery will fail.
I can enter an interface called TRWP.
There is no OS installed on the handset apparently.
I don't know where to start, please help me. I'm willing to grasp concepts quickly, and a step by step guide will be appreciated ! thx.
Edit: i did download an "update.zip" and copied it through computed, tried to install it but got a command error...
Click to expand...
Click to collapse
Do you have adb/fastboot drivers installed? If not: https://forum.xda-developers.com/showthread.php?t=2317790
When you have that installed, boot into TWRP then tap on the Reboot button and then on the Bootloader button.
Plug in USB and open a command prompt, type the following command:
fastboot oem get-build-number
Post the result here

i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.

scrutnizing said:
i solved this issue just today, i didn't get lucky with stock rom kept boot looping. What i did is get fromfuture mate 9 custom rom, place the zip in twrp folder and install zip from there.
The update.zip wouldn't install this way. At least my phone is working now.
Thanks
Edit: I also tried to flash update.app image components after extraction, using fastboot. It didn't work, I don't recommend this method.
The custom rom is life saving.
Click to expand...
Click to collapse
Ah, then you're on Nougat.
The reason I asked about fastboot was to find out what build/fw you were on, then go from there to install stock firmware.
You could update to Oreo using: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108

hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.

scrutnizing said:
hey thanks!
The reason why im statisfied with this is that when flashing stock rom, it worked the first time (no bootloop), but the camera was not working, neither developper mode. Thats why i wiped, reflashed and got stuck in bootloop, no idea why. Also i could only flash a few of the images in update.app, very few. So it was not ideal, other images would yield an error in fastboot when flashing (command failed), i read online and figured this is perhaps due to a bad unlocking in the bootloader (if i understood correctly) at this point i felt that i could no longer process and learn info in android world, after all it was only one day that i'm into android and i felt tired, so i took the ladt chancd and decided to try the custom rom, im now satisfied with results, but many question marks are still in my head.
Click to expand...
Click to collapse
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/

ante0 said:
It's because you can't flash everything from fastboot with just phone unlocked.
You can flash: System, vendor, boot (ramdisk and kernel for oreo), recovery (recovery_ramdisk, recovery_vendor, recovery_vbmeta for oreo), cache, userdata. (I think those are it)
Flashing anything else requires you to unlock bootloader, but it needs a special code which none of us normal people have. :/
Click to expand...
Click to collapse
@ante0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can you give a hand, please ?
I unlocked the bootloader and flashed the recovery, the system booted successfully.
I tried to flash a ROM after that, it showed errors and didn't complete the flashing. since that time the phone has bootloop.
Unlocked bootloader and FRP
fastboot oem get-build-number : MHA-L29 8.0.0.374(C185)
I can access the TWRP recovery and erecovery and bootloader&fastboot
what I have already tried :
1-Fastboot flash ramdisk and kernel .
2-Tried to flash the stock firmware via TWRP.
3-Tried HurUpdater0.3
4- Extract update.app & HOWTA
5-Flash ramdisk and kernel from inside TWRP

is possible unbrik Mate9 Oreo , using only fastboot method ?
can help umbrik only commands fastboot?

phone keeps booting into essentail logo after flashing

i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz

dumberthandumb said:
i tried to follow every guide but no help. tried flashing back to factory still nothing. first when booting from twrp it would say no OS. i finally got that to go away but now it just keeps booting into android power loop. tried erasing all data nothing helps. it also tells me software is corrupted. can someone help plzzz
Click to expand...
Click to collapse
go into fastboot mode and do.... fastboot -w

Tech_Savvy said:
go into fastboot mode and do.... fastboot -w
Click to expand...
Click to collapse
I did that and it didn’t work

dumberthandumb said:
I did that and it didn’t work
Click to expand...
Click to collapse
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.

Nick80835 said:
Make sure you have unlocked the bootloader AND unlocked critical partitions, then flash the latest factory image found on essentials support page. DO NOT flash TWRP or anything like that.
Click to expand...
Click to collapse
How do I unlock critical partitions? Also I have already flashed TWRP. If I try to push the factory image without TWRP it tells me not enough space.

I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!

nstirton said:
I suspect you need to change the slot that's loading... I had a similar thing recently. .. Try going into fastboot and typing "fastboot --set-active=slot" where slot is "a" or "b", depending on where you flashed TWRP (you need to load the opposite slot).
If that doesn't work, flash the original boot file in fastboot and keep everything crossed...!
Click to expand...
Click to collapse
My slot b has been fleshed with TWRP and a with the original os. I still can’t get it to boot. Is there anyways that I can just flash everything back to factory setting? I don’t care about personal data. I even tried flashing both slots with the os and still no luck

flash OTA via adb sideload , it will fix your issue

Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.

galakanokis said:
Just do the fastboot flashall from the Essential download page and start over. I flashed the october update the other day and my phone has been running so much better since then.
Click to expand...
Click to collapse
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped

dumberthandumb said:
Flash all? How do I get to that? I have tried doing a side load through TWRP but nothing helped
Click to expand...
Click to collapse
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.

You NEED to unlock critical partitions to flash all of them.

galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
Flash all? How do I do this?

dumberthandumb said:
Flash all? How do I do this?
Click to expand...
Click to collapse
https://www.essential.com/developer/current-builds

galakanokis said:
Instructions are on the Essential website where you can grab the downloads. Basically download the fastboot image, unzip it and run the flashall script inside the unzip. Easier if your fastboot path is setup properly. It will flash stock to both slots and away you go.
Click to expand...
Click to collapse
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command

dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.

dumberthandumb said:
I tried doing that it flashes and everything but it till wont boot up, its still stuck on the essential logo.
when i try to go into recovery mode it says no command
Click to expand...
Click to collapse
Seems you don't know how to boot into recovery,when you see this Android guy you need to press volume up and power.

Hi, can someone help me with this problem?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

galakanokis said:
You can see it flash both slots and all the images? Should be able to get a screen grab of it.
If your environment is setup correctly and you say it flashes I can't be of much help unfortunately.
Click to expand...
Click to collapse
Thank you I finally got it to work, Apparently only my boot loader was unlocked and I did not have critical partitions unlocked, ones I unlocked critical partitions the flash I was able to go through
Thank you everyone for your help

nibera said:
Hi, can someone help me with this problem?
View attachment 4612857
Click to expand...
Click to collapse
Do you have creitical partitions unlocked ?