Database Info

How to unbrick asus memopad 8 ?

Hello
I am newbie
I have asus memopad 8, someone installed Chairfire 3d on my tablet, so It can't boot anymore, I only saw the loading asus logo.
My tablet is rooted, I tried to install stock rom by using default recovery (Power + Vol up) but: installation aborted.
i.imgur.com/2LNWyQc.jpg
I installed Rockusb devices driver do use rkandroidtool, but rkandroitool didn't detected my device.
i.imgur.com/ShI2BPb.png
I am using Win7 ultimate 32bit
So please help me, I have tried many ways for 3 days but not succeeded
PS: I don't know why the device automatically disconnect from my PC, then I must re-connect the usb cable

who can help me, please

_clonenick_ said:
who can help me, please
Click to expand...
Click to collapse
does fastboot works on your device??

Sakthivel_Subbiah said:
does fastboot works on your device??
Click to expand...
Click to collapse
I plugged cable to my laptop,
I held vol - and power, I installed fastboot driver, But when I opened Minimal ADB and Fastboot, then I typed:
adb shell -> error: device not found
abb devices -> no deivces
I held power and vol+, and Minimal ADB and Fastboot:
adb shell -> error: closed
adb devices -> [serial] siteload
{
"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"
}

_clonenick_ said:
I plugged cable to my laptop,
I held vol - and power, I installed fastboot driver, But when I opened Minimal ADB and Fastboot, then I typed:
adb shell -> error: device not found
abb devices -> no deivces
I held power and vol+, and Minimal ADB and Fastboot:
adb shell -> error: closed
adb devices -> [serial] siteload
View attachment 2657232
Click to expand...
Click to collapse
friend type fastboot devices and see... if there is any device id

Sakthivel_Subbiah said:
friend type fastboot devices and see... if there is any device id
Click to expand...
Click to collapse
Yeah: 0123456789 fastboot
EDIT: And I don't know why my tablet sometime disconnects, I have to reconnect the usb cable and press Vol - and Power

_clonenick_ said:
Yeah: 0123456789 fastboot
EDIT: And I don't know why my tablet sometime disconnects, I have to reconnect the usb cable and press Vol - and Power
Click to expand...
Click to collapse
ya now your device is in fastboot mode.. now copy your boot.img , system.img and recovery.img to folder where minimal adb and fastboot is situated then type
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
thats all :good:

Sakthivel_Subbiah said:
friend type fastboot devices and see... if there is any device id
Click to expand...
Click to collapse
Sakthivel_Subbiah said:
ya now your device is in fastboot mode.. now copy your boot.img , system.img and recovery.img to folder where minimal adb and fastboot is situated then type
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
thats all :good:
Click to expand...
Click to collapse
please friend, this is the first time I've used android tablet, would you like to tell me where boot.img, recovery.img, system.img are ?

_clonenick_ said:
please friend, this is the first time I've used android tablet, would you like to tell me where boot.img, recovery.img, system.img are ?
Click to expand...
Click to collapse
extract your stock rom.zip you fill find all those ...

Sakthivel_Subbiah said:
extract your stock rom.zip you fill find all those ...
Click to expand...
Click to collapse
I only saw boot.img
and of course, it doesn't work

_clonenick_ said:
I only saw boot.img
and of course, it doesn't work
View attachment 2657606
Click to expand...
Click to collapse
make sure that your device is listed in fastboot devices then give a try.. or else try another rom

Sakthivel_Subbiah said:
make sure that your device is listed in fastboot devices then give a try.. or else try another rom
Click to expand...
Click to collapse
Asus memopad 8 has only 1 rom

Try these steps
_clonenick_ said:
Asus memopad 8 has only 1 rom
View attachment 2657622
Click to expand...
Click to collapse
My friend then try installing cwm recovery to your device, follow these steps to install
1. Download CWM recovery for ASUS memopad 8 here.
2. Copy the downloaded recovery to location of minimal ADB and fastboot.
3. Rename the recovery to recovery.img.
4. Boot your device into fastboot mode.
5. Type fastboot flash recovery recovery.img
6. Type fastboot flash misc misc_reboot-recovery.img
7. Type fastboot reboot recovery
8. You should be on CWM based recovery if you did the steps correctly.
In CWM recovery :
1. Go to wipe factory data using volume rockers and perform wipe data
2. Go to wipe cache partition and wipe it
3. Go to advanced and wipe dalvik cache
4. Go back and reboot your device.
5. If your device doesnt boot still then again boot into CWM and choose zip from sd card and flash the stock rom.zip placed in root of your SD.
6. After flashing successfully initial boot will take sometime so wait patiently.
7. Thats all you have recovered your device :good:

Sakthivel_Subbiah said:
My friend then try installing cwm recovery to your device, follow these steps to install
1. Download CWM recovery for ASUS memopad 8 here.
2. Copy the downloaded recovery to location of minimal ADB and fastboot.
3. Rename the recovery to recovery.img.
4. Boot your device into fastboot mode.
5. Type fastboot flash recovery recovery.img
6. Type fastboot flash misc misc_reboot-recovery.img
7. Type fastboot reboot recovery
8. You should be on CWM based recovery if you did the steps correctly.
In CWM recovery :
1. Go to wipe factory data using volume rockers and perform wipe data
2. Go to wipe cache partition and wipe it
3. Go to advanced and wipe dalvik cache
4. Go back and reboot your device.
5. If your device doesnt boot still then again boot into CWM and choose zip from sd card and flash the stock rom.zip placed in root of your SD.
6. After flashing successfully initial boot will take sometime so wait patiently.
7. Thats all you have recovered your device :good:
Click to expand...
Click to collapse
sending 'recovery' (10192 KB)...
OKAY [ 1.773s]
writing 'recovery'...
FAILED (remote: device is locked
finished. total time: 1.788s
I don't know why?

_clonenick_ said:
sending 'recovery' (10192 KB)...
OKAY [ 1.773s]
writing 'recovery'...
FAILED (remote: device is locked
finished. total time: 1.788s
I don't know why?
Click to expand...
Click to collapse
This is because your bootloader is locked do this to unlock and try
Type fastboot oem unlock hit enter
Type flash recovery recovery.img
Continue with above mentioned steps....
Sent from my Micromax A74 using XDA Premium 4 mobile app

Sakthivel_Subbiah said:
This is because your bootloader is locked do this to unlock and try
Type fastboot oem unlock hit enter
Type flash recovery recovery.img
Continue with above mentioned steps....
Sent from my Micromax A74 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
it says
...
ok
but device is still locked

Sakthivel_Subbiah said:
This is because your bootloader is locked do this to unlock and try
Type fastboot oem unlock hit enter
Type flash recovery recovery.img
Continue with above mentioned steps....
Sent from my Micromax A74 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is the bad result:

_clonenick_ said:
This is the bad result:
View attachment 2660326
Click to expand...
Click to collapse
Try this
1. Boot device into fastboot mode
2. fastboot oem unlock
3. Type fastboot reboot bootloader
4. Type fastboot flash recovery recovery.img
5. Rest mentioned above...
Sent from my Micromax A74 using XDA Premium 4 mobile app

Sakthivel_Subbiah said:
Try this
1. Boot device into fastboot mode
2. fastboot oem unlock
3. Type fastboot reboot bootloader
4. Type fastboot flash recovery recovery.img
5. Rest mentioned above...
Sent from my Micromax A74 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yes I did anything you said, but It doesn't still work.

missing command fastboot reboot bootloader
_clonenick_ said:
yes I did anything you said, but It doesn't still work.
View attachment 2660509
Click to expand...
Click to collapse
my friend you didn type fastboot reboot bootloader before trying fastboot flash recovery recovery.img
like this

[Being resolved!] MotoG Bootup Problem - Recovery Mode failed

CURRENT UPDATE 25/6 :
unlocked the bootloader and flashed the O.S (5.0.2) without erasing userdata.
stock recovery mode works now.
booted using custom recoveries : a)TWRP 2.8.X.X b)Philz Touch (will add details later)
data recovery almost done.
NEXT STEP : time to install a CLEAN STOCK ROM
PROBLEM : Not booting up to the Android lock-screen
DEVICE INFO :
Phone Model : Moto G XT 1033 Dual SIM (India)
No Root.Bootloader is LOCKED.No customizations.
ADB Debugging disabled (default).
Moto G XT1033(Black, 16 GB)
Using : Android Lollipop (the latest update done by OTA as part of System Update)
Upgraded : 2-3 weeks after the update was released.
Info from Motorola Media Manager (when connected through USB)
{
"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"
}
What Happened :
Day before : Phone switched off at 0% battery.
Put for recharge the next day (29/5) and I tried to switch it on as it reached 35%.
Didn’t boot.Tried a few more times.
I can access :
Only the bootloader
Problem after Moto Boot Animation
http://imgur.com/l5bUHyq
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3l72ArFhLc1ZThqU3ZoY29hWWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3l72ArFhLc1LWJ2VXI3SmxEQjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B...k50a3VEa1RmZGkwRjJja3E5M0NpSHQzQ3c&authuser=0
Windows Device Mgr:
http://i.imgur.com/lGjFzDR.jpg
What I tried :
http://i.imgur.com/Lq9qHs1.jpg
(suggested on motorola website)Reboot - 10 seconds
(suggested on motorola website)Reboot - 120 seconds power button
Erased cache using fastboot - works.
Recovery mode : I got “bootup failed”
ADB not able to detect the device.Fastboot can.
PC able to detect USB but as a “Falcon Device”
WHAT I WANT :
I want to get a copy of all my internal SD Card data,eg : photos,Contacts,WhatsApp folder,etc.
Flashing it in any way that causes data loss would be my last option.
Besides,i don't have relevant experience and would be asking a friend who has experience with this stuff.
What I found out :
Bootloader UNLOCK will wipe all my internal memory user data.
To root the phone,I’ll have to UNLOCK the Bootloader.
ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
Battery drained to 0% from 75% in one night when i kept the phone in the blank but bright screen mode.
STEPS AHEAD :
Service Centre Visit (Saturday) - Problem Detection -> Won’t be giving the phone since they might damage the data in a situation where it can be recovered.
More Research about such cases and solutions?
Eg : Battery replacement,re-adjustment.
Any way to make it appear as a storage volume on PC?
Any links,suggestions,etc. can
Motorola Support Says :
Service Centre can help
ADB Reqd to recover data
Or use backup software (how can I do this when i am not able to boot :| )
Went to a Service Centre today,they said they will have to "download" software to the phone to check for problems
So my data will be lost.
So I am currently searching for more solutions.
ANY ADVICE,TIP,COMMENT or even a positive post would be really appreciated.THANKS FOR READING

Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup

Thanks for reading and giving your suggestion
I've never rooted,flashed or unlocked my device,no major modifications as well.
So no custom recovery.
I tried what you suggested but it didn't work for now.
Here's what I got :
Maybe because of the LOCKED Bootloader.
ADB doesn't detect my device probably because i don't have debugging enabled.
Thanks Again @lost101
lost101 said:
Do you have a custom recovery installed? If not, try installing TWRP from here: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then use the following ADB command: adb pull /sdcard c:/Motog_backup
Click to expand...
Click to collapse

@ravibhat - Could you unlock the Bootloader? See FAQ for instructions: http://forum.xda-developers.com/showthread.php?t=2537119

@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want

ravibhat said:
@lost101 : I did consider the option using the "fastboot oem lock" option.But it was claimed that it will delete my user data which i don't want
Click to expand...
Click to collapse
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Doing only the above commands will not erase userdata, only reinstall Android.

Hey @lost101,
I'll be using the firmware for XT1033 (Asia-Retail 5.0.2) since the one i have is the dual-sim version.
I came across additional commands in this format:
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo Moto-logo.bin
fastboot flash boot boot.img
<SYSTEM IMAGE FLASH FILES go here - 4 commands like you said here since it's Lollipop>
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
Since I want to save my data i won't be using "oem unlock" and "erase userdata" commands.
So,
a) Can you tell me if there's a specific reason you didn't add them?Will they damage or reset any of my data or affect user partition?
They were also mentioned by a few folks who are trying something similar while trying to protect their data.
I thought they were part of the process.
b) mfastboot or fastboot - will using the normal "fastboot".exe cause any problems?And so you suggest mfastboot?
And thanks a lot for helping me out
lost101 said:
Ah yes, I forgot about that. Good thing you caught it.
XT1032 Retail Asia 5.0.2 Firmware Image: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
mFastboot commands:
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3​
Doing only the above commands will not erase userdata, only reinstall Android.
Click to expand...
Click to collapse

@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.

Hey @lost101!
Man,i tried the commands you mentioned first,didn't work.
Also tried it with the other commands,still no result.
Overall : i didn't get any errors except the ones where i tried to flash a custom recovery.
When i choose the "Recovery" option in the bootloader - I get "booting failed" error for both stock and custom recovery images.
Also,i couldn't directly boot using a custom recovery image file using the "boot" command.
Is it something to do with the files i used or...something else?
Any other tips?
lost101 said:
@ravibhat - the fastboot commands I mentioned are the only ones that should be necessary. Report back what happens, and if needed I will suggest additional commands.
mFastboot is preferred because it was created by Motorola for flashing these files. Traditional fastboot may fail to successfully flash the files, and often does.
Click to expand...
Click to collapse

@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
@deej_roamer @deeplyyoung : thoughts and advise please

ravibhat said:
@lost101 :
Can't boot from stock recovery,however able to flash it (why???)
Can't boot or flash custom recovery (probably because bootloader is locked which i can understand.)
Click to expand...
Click to collapse
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.

Hey @lost101
Sorry for not being clear.
Here's the exact response :
Response on the screen:
The responses upto "boot up failed" in the below image were the ones i got while trying to flash recovery images.
The responses below it are the ones i got for flashing those 4 commands.
After this when I try to bootup - the same problem as mentioned in the main thread - getting stuck after Motorola Logo on a blank but active screen.
VIDEO :
Main problem :
https://drive.google.com/open?id=0B3...WWM&authuser=0
Recovery mode issue:
https://drive.google.com/open?id=0B3...QjA&authuser=0
HD Quality Videos & Images
-> https://drive.google.com/open?id=0B3...Q3c&authuser=0
Anything else you'd like to know that can help
lost101 said:
Please provide a log of what mfastboot responds with when you try to flash a system.img as instructed above. Do not say 'it did not work' - I need to see exactly what is being said by mfastboot.
Click to expand...
Click to collapse

@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)​Has anything changed if you let Android boot?

@lost101 :
ADB can be used but when i searched,USB Debugging Enabled seemed to be a per-requisite in almost all cases on XDA and other forums which I can't do right now since no access to settings.
Push,Pull can be used to backup and restore - tried this on an emulator (Bluestacks on PC) which was detected by it (image below).
My driver is :
I'm not sure if it's the right one or not,no way to test it except testing with "adb devices" in command line but fastboot works so i guess it is.
Fastboot works well in the bootloader,it was able to flash all system images including the ROM.
I am not sure whether this device is hard-bricked since i haven't tried the "fastboot erase userdata command".
No change in the Android boot up process - it's the same issue as before.
It took a little more time (5-10 seconds more to arrive at the blank but lit screen as in the video mentioning the problem) after those 4 commands but that was most likely due to stocking the new firmware.
What bothers me is that i am unable to boot into recovery directly or boot into it after flashing.
It shows "boot up failed" even for the flashed recovery.
lost101 said:
@ravibhat - You mention in OP: ADB can be used to backup using PUSH,PULL (may or may not require Android USB Debugging enabled)
When is it working? While the Android is booting up? If so, you could pull the /sdcard/ during that time.
Regarding your previous post:
Mismatched Partition Size - is a normal error when flashing TWRP and can be ignored. It does not mean flashing has failed.
mfastboot is successfully flashing the Android ROM (system.img)​Has anything changed if you let Android boot?
Click to expand...
Click to collapse

There is another command: adb reboot recovery
I am no longer clear. Can you access stock recovery mode? Power on while holding Vol up?

@lost101 :
adb doesn't work as i mentioned since it doesnt detect the device,probably since ADB debugging wasn't enabled.
And i cannot access stock recovery (like previously mentioned in the OP - same issue ) - it gives "boot up failed" error on the device.
These are the commands i can use right now (since only fastboot works) :
I would really like to save the data but if that's really not possible or practical at this point,i'd go for the second best option.
Unlock the bootloader - try flashing custom/stock images or recovery - take backup or use recovery software.
Any suggestions on unlocking the bootloader?

@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'

@ravibhat
OK so i have understood what problem you got
Now since you wanna save you data here's what you need to do( if it actually works)
As the system boots up, after 2 or 3( not exact) seconds the data partition is mounted ( this is necessary to boot up OS )
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report

@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.

Hey @lost101,
I am able to boot into the bootloader and use fastboot commands.
But when i select "Recovery" on the bootloader as shown in the image in the above post,it says "boot up failed".
I've flashed stock recovery and it was successful but unable to boot directly using "flash boot recovery.img" or even after successful flashing (by choosing Vol down button to navigate and then Vol Up button to select while in the bootloader)
lost101 said:
@ravibhat - I was under the impression accessing recovery from boot was different depending on Bootloader version. With v14.18, you power on while holding 'vol up.' With older Bootloaders - it's 'vol down.'
Click to expand...
Click to collapse
@sjandroiddeveloper
ADB doesn't detect my device.Is USB Debugging required to be enabled to use ADB ?
I don't have USB debugging enabled (it was disabled by default).
sjandroiddeveloper said:
Now can you confirm that adb ( not fastboot) is working while you see the blank screen with backlit active
Report
Click to expand...
Click to collapse
Yes,i saw a lot of posts suggesting this but unfortunately the device doesn't get detected by ADB,also i don't understand the reason why i can boot into Stock Recovery despite being able to successfully flash it,it always says "booting failed".
lost101 said:
@ravibhat - If you can boot into Stock Recovery, you can enable 'ADB Sideloading.' You will then be able to ADB pull /sdcard/ to PC.
Click to expand...
Click to collapse

Relock bootloader of LeEco Le 1S ?

Is it possible to relock the bootloader of LeTV Le 1S ?

er.davinder said:
Is it possible to relock the bootloader of LeTV Le 1S ?
Click to expand...
Click to collapse
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.

vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
Thanks for replying, what if someone with custom recovery/boot image lock the bootloader. It would hard brick the device ?

Use sp tool method to flash stock recovery/boot image and userdata to recover after bricking.

By the way to to unlock bootloader

er.davinder said:
Thanks for replying, what if someone with custom recovery/boot image lock the bootloader. It would hard brick the device ?
Click to expand...
Click to collapse
You can backup necessary partitions and restore them after lock or unlock with SP Flash Tool.

vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
after jumping back to stock recovery and relocking boot loader can we able to download and flash OTA directly?

vishal1286 said:
Yes it is possible.
Make sure you have drivers for your phone and adb and fastboot installed.
Open command prompt in windows and run the following command to reboot into bootloader:
adb reboot bootloader
Now once phone is in bootloader (fastboot) screen run the command in command prompt:
fastboot oem lock
On your phone press the +Volume key
Thats it. Your phone will have bootloader locked.
Click to expand...
Click to collapse
cmd print
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to solve this?

letv le 1s stuck on eui
hello guys
I am sorry to write this random mesage here
I have Letv Le 1s phone tried to root it but messed it up, now my phone stuck on eui logo.
basically my phone was encrypted with password and fingerprint.
now I have downloaded original stock rom but unable to flash that to get my phone back, as when I am in recovery not seeing sd card and no other option.
In flashboot mode it was saying orange lock mode now saying red lock cant unlock it and not sure how to flash stock rom and recover my phone back.
your help will be much appreciated.
many thanks

hjunqq said:
cmd print
...
FAILED (remote: unknown command)
finished. total time: 0.002s
how to solve this?
Click to expand...
Click to collapse
I have the same situation, how to resolve this?
The PC doesn't see the device while its in fastboot mode. When should I press the Volume + key?
{
"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"
}
I want to lock the bootloader to get the stock OTA fw update.
I am still on 5.9.020S
I can only use the local update with update.zip fw file to move to 023S. I earlier switched back to 020S.

[Firmware] 8.1 official Moto Z3 Play [BECKHAM]

{
"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"
}
DISCLAIMER
I am not to be held responsible for any of the damage that occurs to your device during this process. You are yourself responsible for any damage done (if) to your device during this process.
REQUIREMENTS
Make sure your device is charged above 80%.
We recommend creating a backup of all your important files before beginning with this process.
HOW TO INSTALL STOCK ROM IN MOTO Z3 Play
Download Moto Z3 Play Stock Firmware from below (in download section).
Install Motorola Driver and ADB Fastboot Driver on your PC.
Now extract stock firmware in ADB Fastboot folder.
Now, turn off your device and boot into bootloader by pressing volume down button +power button simultaneously.
Now, connect your device to your PC via a USB Cable.
Open a command prompt window and type the following commands:
adb fastboot
fastboot flash partition gpt.bin ( not mandatory )
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system_b system_other.img
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot flash oem oem.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot erase modemst1 ( not mandatory )
fastboot erase modemst2 ( not mandatory )
fastboot reboot
Click to expand...
Click to collapse
Thanks to Motorola firmwares.
Password:
MotorolaFirmwaresLB
BECKHAM_OPW28.70-22_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
-DRIVE
-AFH

Will this work on the Amazon version?

Hello, it should work

I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.

twelfth said:
I would be VERY careful about trying to use the image provided here.
I picked up the Z3 today hoping to be able to build TWRP recovery with this image. Using the kernel from this image resulted in a permanently bricked device. It would no longer turn on. At all.
Second Z3, using the provided image's boot.img and only booting boot.img from fastboot... hung the device.
This tells me the linked image here is very likely to be incompatible with many Z3 Play devices.
The version I've tested it with is the US retus software channel version.
As far as I've been able to tell, this image is for French devices only. DO NOT use this image if you cannot confirm it will work by testing the boot image first.
Extract boot.img from the archive and put your phone into fastboot mode. Test it by typing "fastboot boot boot.img" - If your phone hangs at the motorola logo, this firmware WILL BRICK YOUR PHONE.
The Z3 Play has NO FIRMWARE candidates on https://firmware.center - So, I repeat, the firmware linked here is likely NOT compatible with your device.
Click to expand...
Click to collapse
This firmware is for XT1929-4 and no mention is made in the topic....

GuzXT said:
This firmware is for XT1929-4 and no mention is made in the topic....
Click to expand...
Click to collapse
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.

there is this https://forum.xda-developers.com/moto-z/development/tool-motorola-ota-link-generator-tool-t3537039
we just have to wait for OTA i guess
also there is this if you google beckham_opw28.70-25_subsidy-default_regulatory-default_cfc.xml.zip but they ask for money
https://firmware.gem-flash.com/index.php?a=browse&b=category&id=19944
search for 1929- on https://firmware.gem-flash.com/index.php?a=browse&b=category&id=2634

Here in free access all the same))
https://mirrors.lolinet.com/firmware/moto/beckham/official/

Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.

driverdis said:
Has anyone been able to relock the bootloader in a way that passes safetynet. I noticed that phone boots with verity set at log only which fails CTS and I want to go back to stock until Magisk works properly.
Click to expand...
Click to collapse
magic works quite well if you patch the boot normally, with check marks.

Willy33 said:
magic works quite well if you patch the boot normally, with check marks.
Click to expand...
Click to collapse
Thanks, this did the trick. I was able to download use the boot.img from the lollinet mirror firmware zip. It does require both force encrypt and verity enabled before patching it or it will boot loop.

---REDACTED---

Will this work on the Moto Z3 (XT1929-17)?

wanb1i said:
Will this work on the Moto Z3 (XT1929-17)?
Click to expand...
Click to collapse
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device

darkdaemon32 said:
You need a firmware image for your specific device. Check the websites from this thread and see if you can find one specific to your device. Other images could brick your device.
The steps should be the same for every device as far as fastboot flashing goes. But don't use an image for another device
Click to expand...
Click to collapse
Found the original vzw firmware on Moto's site.
Thanks!

twelfth said:
The XT1929-4 is what I have and the firmware definitely did not work for me. I tried to build TWRP for the Z3 Play as I have for other devices and it definitely wasn't going to happen with these files. Even if you 'fastboot boot boot.img', it's supposed to boot like normal using the rest of the what is stored on your phone. Instead it only hangs.
Click to expand...
Click to collapse
So I have a Verizon Moto Z3 (Brand New XT1929-17, NO XDA Thread yet) I found the firmware off the Motorola site at this link https://androidfilehost.com/?w=files&flid=279604 (last file). I unzipped it, copied the boot.img to my adb folder and executed fastboot boot boot.img and this is the result:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot boot.img
downloading 'boot.img'...
OKAY [ 0.622s]
booting...
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
My goal here is to modify a boot.img so I can root with Magisk without unlocking the bootloader. (Verizon devices don't allow unlocking the bootloader)
Any help would be appreciated.

wanb1i said:
(bootloader) permission denied!
FAILED (remote failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
Your bootloader is locked. Being a Verizon device, it's likely not unlockable.
You have to have an unlocked bootloader before you can boot and flash in fastboot.
This is why people buy unlocked devices.

Xt-1929-4 opw 20.70-31
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Hi, I have the Moto Z3 Play. This is the updated Firmware that I have on my device. I felt I should share it, just in case anyone else needs its. I also added a couple of simple batch files to the folder that I thought everyone might appreciate.
FlashRoot(Service) - Will automatically flash the phone with the patch_boot.img instead of boot.img. This will flash the rooted version of the boot image that was made with Magisk Manager. (Must be in Fastboot)
Flash - Stock --Will automatically flash the regular boot.img also with all the other stock files to the phone. (Must be in Fastboot)
Credit -
Magisk Manager
Google
Android FileHost[https ://drive.google. com/open?id=1KAMijX1W2HQx69mDhZ294tp51vtAoo0E[/URL]

Can someone provide a system dump for Moto Z3 Play..
Edit: Done

Hi, my Z3 play has a Bootloop I tried with hard reset and still not working. It's XT1929-6 dual SIM, can someone help me ? Please

Stuck in fastboot mode

I tried to install LineageOS on my OnePlus Nord following this thread:
[ROM][13][UNOFFICIAL] LineageOS 20 - microG [OnePlus Nord/avicii]
You care a lot about privacy and security? You want an up to date LineageOS build that will not hold you back in regards of user experience? Then LineageOS 20 microG edition is right for you! (Non-microG vanilla LineageOS version also available)...
forum.xda-developers.com
I successfully flashed the recovery.img (provided in the thread), and did a factory reset in recovery. However, I could not find the "Apply Update / Apply from ADB" option, so I though I'll just flash TWRP on there instead. But this bricked my phone. And I got this error message:
{
"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"
}
If I hold vol-down + power button I was also able to reach fastboot mode.
I found MSMDownloadTool and this thread:
[OPNORD][OOS AC01AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
But whatever Firmware image I tried to use the result was always the same: "Device not match image".
(On the box that the phone came in it says "OnePlus Nord AC2003")
I tried different versions of Global, EU and India Firmware files.
I have also tried different versions of Qualcomm drivers (1.00.25 and 1.00.55)
And I have tried different cables, and USB ports.
So I tried to flash stock ROM using this thread:
[ROM][STOCK][FASTBOOT][OPN] Stock Fastboot ROMs for OnePlus Nord
Things are changing with the advent of project treble and seamless updates. OnePlus will no longer release ROMs flashable via recovery (either stock) because is no more needed. The updates will be done on the slot not used for example if you are...
forum.xda-developers.com
It works fine in the beginning, but after the fastboot reboot fastboot step I start getting:
FAILED: Flashing is not allowed for Critical Partitions.
Also, If I do fastboot flashing unlock_critical it says the phone is already unlocked.
I have also tried fastboot boot recovery.img with different .img files (recovery.img provided in the first thread I linked, and also TWRP.img) but this just reboots the phone, and then it gets stuck at Oneplus logo reading "Fastboot Mode" below, until I restart and it gets into fastboot menu again.
I can only reach fastboot mode as shown in picture above, and EDL mode.
I have no clue on how to fix my phone. Any ideas?

Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps

sinkoo1979 said:
Change slots and try again. Had the same problem. now using pronton lock off rom A13. Make sure you are on android 10 or 11. Hope this helps
Click to expand...
Click to collapse
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!

sixtenson1 said:
Thanks a lot for your reply!
You'r reply helps a great deal in getting my faded hope back! However, I am kind of new to all this, so I have a few questions.
What do you mean by change slots?
What is pronton lock off rom A13? Is it something I should use as well?
How would I make sure that I'm on android 10 or 11? Do you mean the Android version file for MSMDownloadTool? Or stock ROM to try and fastboot flash with? Or do you mean the android version that was installed on my phone when it got bricked?
Thanks in advance!
Click to expand...
Click to collapse
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/

sinkoo1979 said:
fastboot --set-active=a. A or B will be the partition. Check which partition you are on first on fastboot.
Custom Rom
Don't know which android version you have
Use this link https://forum.xda-developers.com/t/...stock-fastboot-roms-for-oneplus-nord.4142153/
Click to expand...
Click to collapse
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!

sixtenson1 said:
Thanks for the additional information!
I started by checking what slot was in use:
fastboot getvar all
(bootloader) current-slot:a
I then changed slot to b:
fastboot --set-active=b
And then started following the link you provided.
However, running in to the same problem as before.
When running:
fastboot reboot fastboot
I get the following Error:
Rebooting into fastboot OKAY [ 0.002s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
And when trying to flash abl:
Sending 'abl' (1996 KB) OKAY [ 0.055s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
fastboot flashing unlock
fastboot flashing unlock_critical
both generate the same Error message:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
What could this be?
Thanks in advance!
Click to expand...
Click to collapse
Mine worked with that. Don't really know now. Hope you solve it.

sinkoo1979 said:
Mine worked with that. Don't really know now. Hope you solve it.
Click to expand...
Click to collapse
When I run:
$ fastboot oem device-info
I get the following:
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Device does not seem to be critical unlocked. When I run:
$ fastboot flashing unlock_critical
Output is:
FAILED (remote: ' Device already : unlocked!')
fastboot: error: Command failed
Does the device need to be critical unlocked? And if so, how can I unlock it?

I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204

unbrickmee said:
I have noticed we have the same issue, easy fix !
I fixed it by following this simple guide -
* first step is to download the ROM file with the MsmDownloadTool V4.0(only PC).
* download the QUALCOMM driver(link in the YouTube video description).
* turn your phone off by pressing the power button and the + volume.
* when phone is turned off- press both volume buttons for 10 sec
* connect an original usb cable to your phone and to the 3.0 port on your pc.
* now the device should be recognized in the "device manager" as an qualcom hs-usb qdloader(com4)
* open msm tool and look if the device is recognized (COM4)
* if it is recognized change target to india and click start.
* when it finished it will automatically reboot phone, mine whent staright to recovery mode, but i just pressed reboot and it started correctly
feel free to ask any questions, I know how frustrating it could be.
device used- one plus nord ac2003
ROM + MSM TOOL VERSION- avicii_14_I.13_210204
Click to expand...
Click to collapse
Thanks a lot for your answer!
I followed every of your steps, but I get the same result as I describe in the original post.
In MSMDownloadTool, in the "Status of Last Communication" column it says, in red:
"Device not match image".
Any idea how to fix this?

Try to reinstall correct drivers