Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
{
"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 try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)
Have you fix it yet? I have the same problem....
b4toons said:
Hi !
I have a problem with my Moto 2gen 2014 LTE (THEA). Firstly I unlock my bootloader using command : #fastboot oem unlock 'code' and install TWRP and custom ROM Lineage OS 14.1. In this ROM my SIM card was not detected and I'm going to lock my bootloader (Command: # fastboot oem lock 'code) and install stock ROM. Now when I turn the phone immediately enter into fastboot mode, and shows me :
Device is LOCKED. Status Code: 2
failed to validate system image
Fastboot Reason: Fall-throught from normal boot mode USB connected.
I try several times to boot the new system, but every time is the same
When i try unlock my bootloader cmd shows me :
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
...
(bootloader) Check 'Allow OEM Unlock' in Developer Options.
FAILED (remote failure)
finished. total time: 0.030s
whether it is still somehow saved? Please, help me.
(Sorry for my bad english)
Click to expand...
Click to collapse
select option 4 ,format device and reflash rom
Hay !!
After you lock your bootloader then flash the Entire ROM and make sure after flashing use those two command
$ fastboot erase userdata
$ fastboot erase cache
then reboot
$ fastboot reboot
Hi, sorry for necroposting. Did you fix it?
Related
{
"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"
}
1. Download this zip file and extract it.
2. Hold Shift and then Right click inside the extracted folder and then click on
"Open Command Window here"
3. Connect your device to PC (Make sure that usb debugging is enabled).
4. In command window type
"adb reboot bootloader" //This will boot your phone into fastboot mode.
5. Then type
"fastboot boot twrp.img" //This will boot the device into TWRP recovery temporarily.
6. In recovery click mount -> check system.
7. Now type
"adb pull /system/build.prop" //This will copy the build.prop in the fastboot folder.
8. Open the build.prop using notepad++ (simple notepad may corrupt the file)
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
10. Now type
"adb push build.prop /system/" //this will push the edited build.prop.
11. Now type
"adb shell"(press enter)
"cd system"(press enter)
"chmod 644 build.prop"(press enter)
"exit" (press enter)
12. Type "adb reboot" //to reboot your device
13. Now go in Developer options in setting and enable Multi-window mode
14. enjoy:laugh:
HIT THANKS IS YOU LIKE THIS GUIDE
Error: Device offline
It shows me this error. What should I do?
error: device offline
check adb driver in device manager windows,up date
[email protected] said:
It shows me this error. What should I do?
error: device offline
Click to expand...
Click to collapse
Help!!!!!
bro i have extreated the fastboot file i didnt see the build prop file..................................so what can i do now................please help
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Nera2600 said:
Do I need an unlocked bootloader for this?
C:\Users\Elias\Desktop\Fastboot\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.312s]
booting...
FAILED (remote failure)
finished. total time: 0.315s
C:\Users\Elias\Desktop\Fastboot\Fastboot>
Click to expand...
Click to collapse
failed for me too
ArvinLam said:
failed for me too
Click to expand...
Click to collapse
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
dsbhai said:
9. Find "ro.build.type=user" and change it to " ro.build.type=userdebug"
Then save it.
Change these lines in system build.prop then reboot goto developer options nd enable it
Click to expand...
Click to collapse
thanks
me too..
you find any solution?
question
working fine in android one thanks....Does it work only on android one or any rooted phone?
error
device not found!!!
fail
C:\Users\William\Desktop\Fastboot>fastboot boot twrp.img
downloading 'boot.img'...
OKAY [ 0.277s]
booting...
FAILED (remote failure)
finished. total time: 0.294s
what to do?
Device ASUS ZENFONE 4_T00I
Last working firmware was Jellybean 4.2.2 (never upgraded)
Problem started: Consistent FC msgs of almost all msgs.
1. Droidboot State
Droidboot Version: 6.6.3.0
Product : WW_ZENFON
Not Rooted. No Custom Recovery
Bootloader : Could never unlock. Tried the app but never success.
2. Device Status: Was on Stock Jelly bean and was contineously giving com.android.phone failure and other FC closure consistently , hence needed to try flasing a new rom or same version.
3. Read the forums and collected following data:
Stock Firmwares:
UL-ASUS_T00I-WW-6.6.3.0_user.zip
UL-ASUS_T00I-WW-7.4.4.0-user.zip
UL-ASUS_T00I-WW-9.9.9.0-user
Raw Firmware:
Zenfone4V4.3.10.raw
4. All the Tools required to flash the firmwares and study of methods to do so. I used WIN-XP and tools installed on the same. All Drivers installed successfully device recognizing and able to use fastboot and adb.
5.Current device status: To flash UL-ASUS_T00I-WW-6.6.3.0_user.zip
I tried following methods :
FW placed on SD Flashing started but failed everytime
Tried Fastboot flash update FW.zip method by cleaning all partitions- Failed "Problem in creating otp update file-error)
Now left with no system, no userdata or no data partitions on device.
Now trying AFT method to flash .raw firmware which I have downloaded.
AFT not at all listing up my device in Droidbot mode.
Final Status: No System on / No firmware on device at all. Can use Droidboot thats all.
Now please help me to give life to the device...
Thank you in advance.
C:\Zenfone>fastboot flash boot boot.img
sending 'boot' (8661 KB)...
OKAY [ 1.375s]
writing 'boot'...
OKAY [ 1.859s]
finished. total time: 3.234s
C:\Zenfone>fastboot flash fastboot droidboot.img
sending 'fastboot' (11253 KB)...
OKAY [ 1.578s]
writing 'fastboot'...
OKAY [ 2.156s]
finished. total time: 3.734s
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-9.9.9.0-user.zip
sending 'update' (825100 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.016s
==================================================
C:\Zenfone>fastboot flash update UL-ASUS_T00I-WW-7.4.4.0-user.zip
sending 'update' (837024 KB)...
OKAY [ 37.469s]
writing 'update'...
FAILED (remote: problem with creating ota update file!)
finished. total time: 37.578s
==================================================
AFT not detecting device and showing this error everytime I connect or disconnect device (in droidboot mode)
{
"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"
}
Maybe you can search this files on google :
1. 6.5.35 system.img.gz file
2. 6.5.35 boot.img file
3. 6.5.35 fastboot img file
Should be the same version, then flash it..
Ok, I will try that.
Although I wanted to know whats d fault and where did I go wrong on procedures? I could not unlock bootloader so will fastboot allow me to flash the mentioned firmware images?
Why AFT dint worked for me and. Lot of questions around.. I AINT NOOB FOR ANDROID but. Dis device does not hv anything similar to axnormal android.
Sorry for behaving noob.
Thnkyou for help
Help me please
the AFT i installed on my pc doesnt detect the raw file i have
i've spend two weeks to solve this still no luck
please give me some advice how do i fixed my zenfone 4 its stuck on ASUS LOGO
Fix it already but got a new problem
Flash image failure(FAILED (remote: ERROR: Image-SKU: 'TW_Zenfone' Device-SKU: 'WW_Zenfone'))
u guys can use this method
http://forum.xda-developers.com/zenfone-4/general/guide-how-to-flash-stock-rom-relock-t3302917
[REDACTED FOR PRIVACY REASONS]
[REDACTED FOR PRIVACY REASONS]
Get unlock key from official Motorola site. You will have to enter it to unlock. Obviously it will void warranty
[REDACTED FOR PRIVACY REASONS]
Same here.
Shows some 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"
}
[REDACTED FOR PRIVACY REASONS]
ava2048 said:
You found a solution buddy?
Let me know when you find something.
Click to expand...
Click to collapse
No.
Tried to unlock many times. No output other than error.
Code:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s/CODE]
I have asked in telegram group.
jamespauljose said:
No.
Tried to unlock many times. No output other than error.
Code:
C:\adb>fastboot oem get_unlock_data
(bootloader) slot-counttas: not found
(bootloader) slot-suffixe: not found
(bootloader) slot-suffi: not found
...
FAILED (remote: unknown command)
finished. total time: 0.001s/CODE]
I have asked in telegram group.[/QUOTE]
i am waiting for the answer of same question. please experts give answer.
Click to expand...
Click to collapse
Same problem here
drvikasjoshi said:
Get unlock key from official Motorola site. You will have to enter it to unlock. Obviously it will void warranty
Click to expand...
Click to collapse
I have the same problem here, the "fastboot oem get_unlock_data" command just hangs. I've tried leaving it for a few minutes, but it still doesn't work. Which is especially strange, considering X number of Youtubers/other users get the key in mere seconds! And yes, my model number matches, settings are correct, etc.
You can just use the computer of Windows XP system inside
Sorry,my English is not standard,but you must be understand
caocanhong said:
You can just use the computer of Windows XP system inside
Sorry,my English is not standard,but you must be understand
Click to expand...
Click to collapse
Windows XP won't support modern USB systems. It won't even run ADB, forget about unlocking anything.
Hi,
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Code:
fastboot.exe oem get-bootinfo
(bootloader) unlocked
OKAY [ 0.006s]
Finished. Total time: 0.009s
fastboot.exe oem get-product-model
(bootloader)
OKAY [ 0.006s]
Finished. Total time: 0.069s
fastboot.exe getvar vendorcountry
vendorcountry: optus/au
Finished. Total time: 0.007s
fastboot.exe oem get-build-number
(bootloader) :
OKAY [ 0.004s]
Finished. Total time: 0.007s
fastboot.exe oem oeminforead-System_Version
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
greyjoy said:
I have been given an old Huawei P9 from a friend who tried to install a custom ROM on it, which apparently didn't go so well. The phone doesn't seem to boot past the bootloader unlocked message. He asked me to try to recover it so he could use it temporarily as his current phone died.
It appears to have TWRP 3.1.1.0 installed, but from what I can tell TWRP can't mount the /data folder, I haven't really looked into that issue much as I was hoping to just reinstall the stock recovery and take it back to stock, but struggling to find/understand instructions. Hope there is someone that can still help, any help would be appreciated.
It is an Australian (carrier: Optus) model EVA-L09, and that's about all I can tell as fastboot doesn't seem to be able to get much else
Click to expand...
Click to collapse
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery
zgfg said:
Are there really no answers (even no "Failed") to some commands - try to execute again and attach also screenshot from PC
Code:
fastboot oem get-bootinfo
PAUSE
fastboot oem get-product-model
PAUSE
fastboot oem get-build-number
PAUSE
fastboot oem oeminforead-SYSTEM_VERSION
PAUSE
fastboot getvar vendorcountry
PAUSE
REM fastboot getvar rescue_enter_recovery
Click to expand...
Click to collapse
No other errors that I can see when I run the oem commands at least, see screenshot
{
"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"
}
greyjoy said:
No other errors that I can see when I run the oem commands at least, see screenshot
Click to expand...
Click to collapse
This is all very strange. Even after custom ROM and/or brick it should know to answer on get-product-model or get-build-number.
Maybe only if some ... deleted all partitions by TWRP or so?!
Just one suggestion. Forget Platform tools and install to the PC very simple and small (only few MB) "Minimal ADB and Fastboot" package and execute from there (you don't need to type "fastboot.exe", just "fastboot" is enough)
Do you know at least, was it Android 6, 7 or 8. Almost certainly not 8, it would be CN, not AU. 6 only if stock was not updated from the beginning
From the TWRP version I would guess it was Nougat, i.e. EMUI 5.
In that case you can install generic/no-check version of Nougat stock recovery:
https://mega.nz/file/09k1wIST#IyMKcRwPq7llKEmnflOAQJSl2B4v8pmz6Myj_ZawxQs
You should also know was it L09 Single SIM or L19 Dual SIM
Searching for custs, Australia might be c636 or c183 but seems that c34 was Australia Optus
Find on FirmwareFinder or from:
https://pro-teammt.ru/firmware-database/?firmware_model=EVA-L09c34
"FullOTA-MF-PV" (only PV are suitable for DLOAD) firmware for e.g. EVA-L09c34, like EVA-L09c34b380 (pkg #93280 from 2017.08.15) and try simple DLOAD method
But if really all partitions were deleted, DLOAD would likely fail. You could try (with your c34, not c432 as in the guide) something like this:
https://forum.xda-developers.com/showpost.php?p=74169408&postcount=7
{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
xdroid-caf ROM is based on CAF sources to increase performance and reliability over stock Android for your device.
Flashing Instructions:
Pre-installation:
TWRP (Download from here)
Magisk 20.0 or newer for root (after first boot) - (Download from here)
Ask to get your bootloader unlocked first! - t.me/NokiaX7
First time installation:
First Time Install / Clean Flash
(All your data including the one in internal storage will be removed, so proceed with a caution! Or a backup )
MAKE SURE TO BE ON THE LATEST FIRMWARE/UPDATE BEFORE FLASHING
Also download vbmeta.img
Use the following command in fastboot to boot TWRP-
Code:
fastboot erase system
fastboot erase userdata
fastboot erase vendor
fastboot erase boot
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
fastboot flash system_a system.img
fastboot flash system_b system.img
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash vendor_a vendor.img
fastboot flash vendor_b vendor.img
fastboot flash boot twrp.img
*Now hold down the Vol+ button and Power button* while at the same time you enter this command-
fastboot reboot
*When the phone vibrates or androidone screen comes for 1-2 sec, leave the buttons*
After phone boots to TWRP, enter the password if encrypted.
Transfer boot.img to phone and flash it to both slots
Flash Magisk(optional)
Format Data
Reboot
Sources:
ROM: https://github.com/xdroid-CAF
Kernel: Prebuilt
Download:
ROM Download
BUGS-
None, you tell
Nokia 8.1/X7 Community Telegram