I had upgraded my omnia to mango successfully...but i wanted to my sideload my apps so had to downgrade to nodo. When i restored it back to NODO by zune it kept restarting so i thought screw it ill start from scratch and flash my omnia to pre-nodo cause i didnt see anyway out...anyway long story short i tried flashing and its stuck at the samsung omnia 7 boot
this is flash log
Detect COM5 Port
[Channel 0] Confirm Model Name
[Channel 0] FLASH UNLOCK
[Channel 0] FLASH UNLOCK Success!!!
[Channel 0] Send Partition Table
[Channel 0] Partition Table is correct
[Channel 0] Erase MIBIB Region
[Channel 0] Write MIBIB Data
[Channel 0] MIBIB Download Success!!
[Channel 0] Erase FSBL Region
[Channel 0] Write FSBL Data
[Channel 0] FSBL Download Success!!
[Channel 0] Erase OSBL Region
[Channel 0] Write OSBL Data
[Channel 0] OSBL Download Success!!
[Channel 0] Erase AMSS Region
[Channel 0] Write AMSS Data
[Channel 0] AMSS Download Success!!
[Channel 0] Erase DSP1 Region
[Channel 0] Write DSP1 Data
[Channel 0] DSP1 Download Success!!
[Channel 0] Erase APPSBL Region
[Channel 0] Write APPSBL Data
[Channel 0] APPSBL Download Success!!
[Channel 0] Erase CSC Region
[Channel 0] Write CSC Data
[Channel 0] CSC Download Success!!
[Channel 0] Erase PDA Region
[Channel 0] Write PDA Data
[Channel 0] PDA Download Success!!
[Channel 0] FLASH LOCK
Can anyone please help me why am i getting the FLASH LOCK ? is it the .CSC file if so which is the proper one to use ?
Nobody has a slightest idea why this is happening ?! i am at my wits end....if anyone has the smallest idea what i could try please please please reply.
So far i have tried:
flashing numerous firmwares from pre-NODO to NODO
Using Windows Support tool
Using Samsung Device Update Support Tool
Using Zune to restore
and nothing seems to be working...
Go to download mode and reflash stock unbranded ROM with proper CSC?
Tried flashing I8700 XEN I8700XENJK1 has signed_CSC_Cetus_Europe_I8700XENJK1.csc
everything goes fine then back to boot loop.
Have you tried doing hardreset right after flash?
yup. I have. Nothing.
it happens to me also.
use the tool from samsung website to enable updates... the link is http://www.samsung.com/uk/consumer/...H3G/index.idx?pagetype=prd_detail&tab=support
How did you guys go with this in the end? I'm having the same problem and I can't seem to fix it.
I've used the samsung tool and forced the phone into computer connection mode to try and restore from zune but everytime zune reboots the device it just gets sits on the omnia boot screen and won't continue. I've also tried flashing a few different roms but get the same problem as described by the original poster.
the same problem, now i don't know how to fix it
I use a lot of roms but the same result
Anyone helps?
Wow, this thread is hopeless!
I'll think twice before getting the official Mango update now, I'd hate to restore to NODO and brick this thing.
Any updates guys ? i am still sitting here with my bricked phone...The country i am in still doesn't have the official support for omnia 7 so essentially its an expensive paper weight right now.
huzz said:
Any updates guys ? i am still sitting here with my bricked phone...The country i am in still doesn't have the official support for omnia 7 so essentially its an expensive paper weight right now.
Click to expand...
Click to collapse
Did you try this
http://www.winrumors.com/got-a-bricked-samsung-omnia-7-windows-phone-heres-the-fix/
Hello guys ! I am very happy that I found you ! I am apologize for my poor english, but you are my last hope of help. . .
My Moto X 2014 2nd was Flawless and perfect before the last OTA update in 2015.... After I installed, my phone don`t reboot anymore and freezing with the first white logo image about 20 sec and after appear a black screen with the "dead" android robot with red exclamation on it said "NO COMAND". The injured android logo just repeatedly flashes on for an instant and then disappears. Nothing happens when I hold the power button and press volume up. Anything I choose from bootloader is giving me the same result. I read all the pages from here and I am still stuck...
-I install everything: adb (it recognize the device - TA99303EV4) but every comand failed with a "REMOTE FAILURE" message. Fastboot or mfastboot - the same..... I try the CODE that i receive from Motorola ( for unlock the bootloader) but it failed again: "check Enable OEM Unlock in Developer Option". Yeah, right - but I can`t do it now with this black screen
-The RDS Lite doesn`t recognize my device (many restarts, different USB ports and computers, nothing works...)
-Motorola Device Manager said: "No updates for your phone. Current Version: 23.16.3.victara.retes.retesall.en.eu"
-In the Device manager (win 7 32bit) it appears ok: Motorola ADB Interface
My Bootloader screen looks like this:
AP Fastboot Flash Mode (S)
60.16 (sha-496ce05, 2015-04-02 10:55:00)
CPU: MSM8974AC ES1.1
eMMC: 16 Gb Sandisk RV=07 PV=01 TY=57
DRAM: 2048 MB Elpida S8 SDRAM DIE=4Gb
Battery OK (Charging)
Device is LOCKED. Status Code: 0
Software status: Official
Transfer Mode: USB Conected
Dates extracted from adb (fastboot get var all) screen:
date:11-19-2014
sku:XT1092
ro.build.fingerprint: motorola/victara_retes/victara:5.1/LPE23.32-25.3/3:user/release-keys
ro.build.version.full:Blur_Version.23.16.3.victara _retes.retesall.en.EU
sdi.git: git=MBM-NG-V60.16-0-g582b967
The firmware that I trying to flash is:
BUILD REQUEST INFO:
SW Version: victara_retes-user 5.1 LPE23.32-25.3 3, RMBM Version: 60.16
System Version: 23.16.3.victara_retes.retesall.en.EU, Model number: Moto XAndroid Version: 5.1
Baseband Version: MSM8974BP_4235210.110.09.13R, Build Number: LPE23.32-25.3
Build Date: Tue Aug 18 04:30:10 CDT 2015
Blur Version: Blur_Version.23.16.3.victara_retes.retesall.en.EU
Please, help me... In my country there is nobody who can repair my beloved phone, I went 4 times to diferent service centers and nothing... Maybe with your help, my beloved MOTO X will be back to life again. If, OMG, IF i knew before to check/enable that option in the developer option - USB debbuging......
I wish you all the best for all and thank you so much for every posible answer !
Please corect me if I am wrong:
I thing that once OTA was upgraded the partition table, then I can`t never go back. Maybe the bootloader (motoboot.img) (also system) would ONLY work with the correct partition table. Meaning that I can't mix and match at all.
I think that means that I am currently stuck with the latest GPT from the last OTA i received. Somehow maybe the bootloader was downgraded and won't work for flashing other partitions ?! ...
That means that if I flash the new bootloader version and reboot, maybe it will be back to life. So guys, what version do you thing I must try to flash ?
Please respond me, I don`t know where to ask anymore... If I only could pass that "Device is LOCKED . Status Code 0" will be so. . . blissful
I have so much expectations from the MASTERS of this forum and nobody give me a chance. . . an ideea. . . I simply don`t believe: Am I the only one who has this stupid problem ?!?!
So, because of your complete silence (and only views) I understand that I have to throw my phone on the trash because:
- nobody told me that I have to enable this stupid USB debugging option on the first day when I bought the phone.
- nobody told me that I have to unlock this bootloader on the second day when I bought this phone.
- nobody told me that I should NEVER trust the OTA updates that destroyed my phone who works flawless before. . .
I will still wait, maybe someone, SOMEONE will find a solution for this idiot situation.
With all my great respect,
Matrix.
Hi,
You should be able to flash stock images without USB debugging enabled.
Can you explain a bit more how you tried to flash the image ?
Hope we'll find a solution,
Best regards.
I use the common way like usual - mfastboot, fastboot, Android SDK Slim, the image package is in the same folder. . .
fastboot devices - returns my serial number so my phone is conected and recognized.
After I tried all this comands like usuals:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
fastboot erase userdata
fastboot erase cache
but after EVERY comand, the messages is sending...OK, writing and this stupid lines:
Preflash validation failed
FAILED (remote control)
finished. Total time .....followed by some seconds.
I tried also the mfastboot command instead of fastboot - the same result. . .
like this:
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s"
On and on, the same message . . . .
Matrix_MotoX_2nd said:
I use the common way like usual - mfastboot, fastboot, Android SDK Slim, the image package is in the same folder. . .
fastboot devices - returns my serial number so my phone is conected and recognized.
After I tried all this comands like usuals:
fastboot flash motoboot motoboot.img
fastboot reboot-bootloader
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.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 system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot reboot
fastboot erase userdata
fastboot erase cache
but after EVERY comand, the messages is sending...OK, writing and this stupid lines:
Preflash validation failed
FAILED (remote control)
finished. Total time .....followed by some seconds.
I tried also the mfastboot command instead of fastboot - the same result. . .
like this:
erasing 'userdata'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s
erasing 'cache'...
(bootloader) Failed to erase partition
FAILED (remote failure)
finished. total time: 10.000s"
On and on, the same message . . . .
Click to expand...
Click to collapse
Make sure your battery is fully charged before trying to flash anything. Sometimes a low battery can be the reason for the failure messages.
My battery is fully charged. . . I even let it over night. . .
I found these on several sites:
1) "If you're flashing your variant's factory image, you can flash it without unlocking the bootloader. You would only need to unlock the bootloader if you want to flash another variant's image or a custom ROM." So I try with victara_retes-user 5.1 LPE23.32-25.3 3 (Blur_Version.23.16.3.victara_retes.retesall.en.EUVersion) and is NOT working. Same failure message. . .
2)"Google has added a check box under Developer Options that enables the OEM unlock command to work. If that box isn’t checked, then you will see an error during the bootloader unlock process. So without the option checked in Developer settings to allow OEM Unlock, users can't modify the system partition"
Which variant should I choose to be true ?. . .
Matrix_MotoX_2nd said:
My battery is fully charged. . . I even let it over night. . .
I found these on several sites:
1) "If you're flashing your variant's factory image, you can flash it without unlocking the bootloader. You would only need to unlock the bootloader if you want to flash another variant's image or a custom ROM." So I try with victara_retes-user 5.1 LPE23.32-25.3 3 (Blur_Version.23.16.3.victara_retes.retesall.en.EUVersion) and is NOT working. Same failure message. . .
2)"Google has added a check box under Developer Options that enables the OEM unlock command to work. If that box isn’t checked, then you will see an error during the bootloader unlock process. So without the option checked in Developer settings to allow OEM Unlock, users can't modify the system partition"
Which variant should I choose to be true ?. . .
Click to expand...
Click to collapse
You need the xt1092 reteu 5.1 firmware.
Sent from my XT1095 using Tapatalk
Thank you so much for your answers ! All of you !
Can you give me a correct link ? There is so many xt 1092 reteu 5.1 firmware, and I want to be 100% sure that I`ll do it like you told me.
Can I look here for the corect one ?
http://firmware.center/firmware/Motorola/Moto X (2nd gen-2014)/Stock/XT1092/
I will try today again with this xt1092 reteu 5.1 firmware. But if the phone blocked every attempt to flash or erase its partitions, does it matter which firmware I send it to flash ?. . .
I`ll post the result as soon as I`ll arrive at home. Hope you are right, so much !
I really don`t understand why the Motorola official site who send me the unlock bootloader code special for my phone doesn`t work . . . It was so simple if it works. . .:crying:
Youre bootloader isn,t unlocked because off status zero.
Follow this guide.
https://www.youtube.com/watch?v=nLNja2M6zc0
With all my respect sir, you didn`t read my posts. . . .
I already past this stupid step, like I said:
"I try the CODE that i receive from Motorola ( for unlock the bootloader) but it failed again: "check Enable OEM Unlock in Developer Option". . . . . . I already attach the image that proves what I am talking about and about. . .
So. . .bad news. Is the same error message, over and over again, with this firmware xt1092 reteu 5.1 . . . The phone simple don`t want to be flashed, don`t wanna accept any comand . Is there any way to flash SOMETHING on this phone ? I should try another program to flash, or something like TWRP recovery, or . . . another firmware ?
I don`t know, SOMETHING, SOMEHOW ?
I am sad. Very sad.
I attached a picture.
p.s the firmware that I tried was from here: http://forum.xda-developers.com/moto-x-2014/general/ota-t3132045.
and a little movie, trying every combination of pressing. . .
https://www.youtube.com/watch?v=vDTSncEvscM
wherever I tried to flash the RETES or RETEU 5.1 firmware, the phone respond with " invalid PIV signed system image". I am choose the wrong variants ?!?
Nobody can help me ? . . .
Matrix_MotoX_2nd said:
Nobody can help me ? . . .
Click to expand...
Click to collapse
Why dont you try flashing KITKAT Bootloader and image... It'll remove that silly option of OEM Unlocking in Developer Options... And maybe you will have luck with this... If the phone is already sort of dead, its worth a shot...
---------- Post added at 12:53 PM ---------- Previous post was at 12:46 PM ----------
Also I wonder why don't you go back to MOTO Care, if your bootloader isn't yet unlocked they may help you with it..
I really wish I could help, but since I haven't posted enough, can't provide the links, so I'll do my best to give you exact google search terms to use.
I managed to softbrick my phone the day I got it. Engabling USB debugging doesn't matter in fastboot, which is where you'll be doing all the recovery/fixing at. I can't assure you that this will work for you, different problems can make for different results, however this tool was the only successful way I was able to recover my device.
Tool I used: House of Moto [4.3] SamuriHL's House of Moto - DroidRzr
It shows up as the second link in a google search for me.
The place I got the factory ROM from was: Downloads for Motorola Moto X 2014 by Motorola-Firmware-Team | AndroidFileHost | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers
This one is a bit more difficult, any of the results will be fine, but on the page, on the right side toward the bottom, select your phone, then the exact model.
This will do a full factory flash, you don't need the bootloader unlocked to do this. Alternatively, if you have better luck than me with using RSD Lite, that tool should work, too (it's never worked for any of my phones on any of the five computers I've tried it with, so I regard that software as hopelessly useless, but everyone has different results).
@hamzaalijoiyah
"Why dont you try flashing KITKAT Bootloader and image"
I`ve tried with the same silly message - Failed (remote failure).... !!!!!
@Kayjay0x
Thank you for this new idea/trying to resurect my beloved Moto X xt1092. At first glance, there`s another adb and fastboot based programs, but I`ll give it a try again.
Kayjay0x said:
I really wish I could help, but since I haven't posted enough, can't provide the links, so I'll do my best to give you exact google search terms to use.
I managed to softbrick my phone the day I got it. Engabling USB debugging doesn't matter in fastboot, which is where you'll be doing all the recovery/fixing at. I can't assure you that this will work for you, different problems can make for different results, however this tool was the only successful way I was able to recover my device.
Tool I used: House of Moto [4.3] SamuriHL's House of Moto - DroidRzr
It shows up as the second link in a google search for me.
The place I got the factory ROM from was: Downloads for Motorola Moto X 2014 by Motorola-Firmware-Team | AndroidFileHost | Download GApps, PA GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers
This one is a bit more difficult, any of the results will be fine, but on the page, on the right side toward the bottom, select your phone, then the exact model.
This will do a full factory flash, you don't need the bootloader unlocked to do this. Alternatively, if you have better luck than me with using RSD Lite, that tool should work, too (it's never worked for any of my phones on any of the five computers I've tried it with, so I regard that software as hopelessly useless, but everyone has different results).
Click to expand...
Click to collapse
Bro you saved my day, I tried your method and it worked ! I updated the thread I started
Ufff.... the same story even with this House of Moto . . .
Please, someone can tell me what version image file do i have to download and try to flash - 100% corect ? Always I found this message: "invalid image file" from the screeen (fastboot or house of moto). . .
my getvar screen is attached on the post.
I tried till now and EVERY time said: invalid image file. . . :
VICTARA_RETES_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml
RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml
VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml
RETEUALL_XT1092_4.4.4_KXE21.187-45_cid7_CFC.xml
YassGo said:
Bro you saved my day, I tried your method and it worked ! I updated the thread I started
Click to expand...
Click to collapse
Glad to hear it worked out for you like it did for me!
Matrix_MotoX_2nd said:
Ufff.... the same story even with this House of Moto . . .
Please, someone can tell me what version image file do i have to download and try to flash - 100% corect ? Always I found this message: "invalid image file" from the screeen (fastboot or house of moto). . .
my getvar screen is attached on the post.
I tried till now and EVERY time said: invalid image file. . . :
VICTARA_RETES_XT1092_5.1_LPE23.32-25.3_cid7_CFC.xml
RETEUALL_XT1092_5.0_LXE22.46-19_cid7_CFC.xml
VICTARA_RETEU_XT1092__5.1_LPE23.32-25.1_cid7_CFC.xml
RETEUALL_XT1092_4.4.4_KXE21.187-45_cid7_CFC.xml
Click to expand...
Click to collapse
I don't know what to suggest other than trying your luck with a non EU rom? Can't promise that'll work though.
Hey everyone,
I know this is the wrong thread but there is not forum or thread for the Moto E5 Plus, please help
Im rooting a Moto E5 Plus and after I installed the rom I get Error: Failed to load kernel!
I get this message below
Start Up Failed:
Your device didnn't start up successfully
Use the Software Repair Assistant on computer
to repair your device
Connect your device to your computer to get the software repair assistant
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
Error: failed to load kernel!
Boot up failed
Its basically stuck in the bootloader besides being able to go into the twrp recovery.
rmercer said:
Hey everyone,
I know this is the wrong thread but there is not forum or thread for the Moto E5 Plus, please help
Im rooting a Moto E5 Plus and after I installed the rom I get Error: Failed to load kernel!
I get this message below
Start Up Failed:
Your device didnn't start up successfully
Use the Software Repair Assistant on computer
to repair your device
Connect your device to your computer to get the software repair assistant
AP Fastboot Flash Mode (Secure)
Fastboot Reason: UTAG *bootmode* configured as fastboot
Error: failed to load kernel!
Boot up failed
Its basically stuck in the bootloader besides being able to go into the twrp recovery.
Click to expand...
Click to collapse
Looks like the E5 forum handles E5+ too (their TWRP says for E5+) and I see your post there. I'm not familiar with your phone but did you try a factory reset? Another option might be to fastboot flash the boot.img from your model's firmware on lolinet - see here - which should restore your stock kernel. Either option will delete your personal data though but sometimes no other choice. See what they say over there & maybe post in the TWRP thread where OP looks to know his stuff.
I have the stock firmware but I keep getting invalid zip file. How do I fastboot flash the boot.img??
rmercer said:
I have the stock firmware but I keep getting invalid zip file. How do I fastboot flash the boot.img??
Click to expand...
Click to collapse
Make sure it's the correct official firmware version for your software channel &/or vendor. You need to unzip the firmware into a temp directory on a computer, then you'll see boot.img among many files, copy it into your fastboot folder, connect the phone (do a 'fastboot devices' to make sure it's working), then type 'fastboot flash boot boot.img' and when it's done reboot. Also try a factory reset first if you can.