Database Develop

stuck on bootscreen (Serial v2. 08/USB v2. 08)

Hi to all,
My device is stuck on bootscreen:
- Serial v2. 08 (outside of cradle)
- USB v2. 08 (inside cradle)
I' ve tried the solution:
-use Mitty, when stuck on bootscreen
(http://forum.xda-developers.com/showpost.php?p=934239&postcount=12)
but without success.
I See again:
- Serial v2. 08 (outside of cradle)
- USB v2. 08 (inside cradle)
Before of this I've used:
-xdadev_all_unlock-v1.5 (with success);
-after I've copied EnterBL.exe to my device and execute it for stupid purpose only
and now my device stuck as mentioned before.
I cannot connect it through ActiveSync 4.2 and simply stuck
I've read a lot of thing and suggestion on this forum and I've tried various solution but the device stuck and I'm too.
I'm a newbie and really I don't know if this is a bl mode or something else.
Someone can help me Please?
Thanks
My device:
Vodafone VPX v1620
Model PH2OB2
Language:UK

Have you tried a soft reset?

you just need to find a different ROM and flash it using the file i attached. you are also going to have the change the htcruu files to ruu files. all u have to do is a simple renaming. try that and ur phone should be back to normal again soon.

Take care to mtty version 1.16 rather than 1.42
Hi and thanks to all,
the problem was the version of mtty.
the version 1.16 works fine
the 1,42 doesent
so now I've done the step
please look the attached image
and now my device work again
but without radio
on the screen on boot I read:
NO GSM
D 1.40 ETC ETC

mtty 1.16 link for download
I don't know if I can however I post the link for all that need the newer version of mtty
http://buzzdev.net/index.php?option=com_phorum&Itemid=125&phorum_query=file,40,file=186
HAVE A LOT OF FUN!

Stuck on bootscreen (Serial v2.06/USB v2.06)
Hi All,
thanks a lot for the great help,
I Have I-mate PDA2k with WM2003SE
I have ROM ver. 1.40.00
I tried to reflash my PDA2k as I found that the sound is no longer work as well as the SD card is no longer been recognized by the OS
Now I am stuck on bootloader (Serial v2.06/USB v2.06) screen after unsuccessful flashing my PDA due to power failure in my home electricity
I used MTTY V1.42, set 14 0, task 28 and task 0 commands and successfully the OS worked again, then I found new ROMs for WM2005, So I used XDAIII Ext. ROM unlock tool, after that the machine started to HANG so I made a Hard reset then it return to hang on BOOT splash screen again
so I used mtty again to reprepare the Disk On Chip to return to a clean OS
all above three commands executed successfully and after soft reset the PDA2k stuck in the boot screen, I tried hard reset as well but with no hope
I tried to use MaUpgradeUt_noID.exe to reflash the Rom nothing happen, I tried to use another official roms from I-mate but nothing happen I stuck in the bad bootloader screen, I tried to use d2s command to make a backup of my ROM but when the command is executed the USB v2.06 message disappers from screen
after all this, is there anyone can help me with a new idea on how to fix it.
Thanks alot on advance.

hi
I have the same problem, could you help me?
secur said:
Hi to all,
My device is stuck on bootscreen:
- Serial v2. 08 (outside of cradle)
- USB v2. 08 (inside cradle)
I' ve tried the solution:
-use Mitty, when stuck on bootscreen
(http://forum.xda-developers.com/showpost.php?p=934239&postcount=12)
but without success.
I See again:
- Serial v2. 08 (outside of cradle)
- USB v2. 08 (inside cradle)
Before of this I've used:
-xdadev_all_unlock-v1.5 (with success);
-after I've copied EnterBL.exe to my device and execute it for stupid purpose only
and now my device stuck as mentioned before.
I cannot connect it through ActiveSync 4.2 and simply stuck
I've read a lot of thing and suggestion on this forum and I've tried various solution but the device stuck and I'm too.
I'm a newbie and really I don't know if this is a bl mode or something else.
Someone can help me Please?
Thanks
My device:
Vodafone VPX v1620
Model PH2OB2
Language:UK
Click to expand...
Click to collapse

secur said:
I've read a lot of thing and suggestion on this forum and I've tried various solution but the device stuck and I'm too.
I'm a newbie and really I don't know if this is a bl mode or something else.
Someone can help me Please?
Thanks
My device:
Vodafone VPX v1620
Model PH2OB2
Language:UK
Click to expand...
Click to collapse
OK i know you are new.. and maybe, just maybe a bit nervous because you have a device you cant use..
READ THE DAMN WIKI ALREADY!
There are so many ways to upgrade a rom, or extract it,
Let me give you a little hint.. Use that really bright shiny search button up there.. (ok so its not bright and shiny, but it is there!)
Press the down arrow, choose advanced search,
then type in what you need help with,
then make sure that the forum is BlueAngel (on the right!)
then hit search...
That will bring all the posts with the words that you looked for in the BlueAngle section of the forum.
Multiple posting is stoopid.. This is the 6th post i have seen from you regarding your device that you could have solved using your own head, and searching for the answer istead of sitting on your backside waiting for someone to post the link to solve all your problems.
I know this sounds harsh, and scarcastic, and a tad evil... EVERYTHING I HAVE LEARNED ABOUT A HTC DEVICE, I HAVE LEARNED FROM THIS SITE,
and reading the wiki, and google, and all kinds of other services...
there is no shame in asking for help.. just exhaust all other options first!
@ jbodaa
please read above and take note as well!

1. Download Romupdate v1.11a
2. Stop ActiveSync, by Task Manager (press Ctrl + Alt + Delete) kill two processes rapimgr.exe and wcescomm.exe
3. put your device into Bootloader Mode by pressing Power + Record Button and Soft Reset.
4. Run Romupdate v1.11a (from downloaded)
5. from left top corner drop down menu Port: Choose WCEUSBSH001 (If you only see COM 1 and COM1 try unplugging the USB and replugging it)
6. press OK button
7. type "set 14 0" without the quotes in blank window that showed up to tell bootloader to boot the OS after reset.
8.press enter to execute
9. on next line you will see:
HTCST ÚÈÒHTCEUSB>
10.type "task 28" (no quotes) right after > sign to get your device formatted
11.press enter to execute, you gonna see:
DOC_format_HW+
DOCInfoTableinitHW+
Binary0:dwSize=80000
BINFS0:dwSize=0
FAT0:dwSize=1000000
FAT1:dwSize=2BA0000
All:dwSize=3C20000
USB>
12. type "task 0" (no quotes) right atfter > sign to ask your device reboot
13.press enter to execute the command
14. take the device out of the cradle, and manually reset it if it does not do that already.
good luck.

stuck on bootscreen USB v2. 07
hi 2 all.i i have i-mate_PDA2k ppc.
i downloaded i-mate_PDA2k_Arabic_13100_112_10600_SHIP to my pc and clicked on it and got stuck on boot screen USB v2. 07.i tried soft reset & hard reset i tried Romupdate v1.11a and mtty1.42 i tried every thing i would whan to bring it back to factory setting can some one help me.thanx a million thanx in advance
----------------------------------------------------------------------------
Learn 2 live & live 2 learn.learn 2 listen & listen 2 learn.Live 2 love & love 2 live.
We live 2 die & we die living.
life is what u make of it

[G1 doesn't work but is alive] Help me XDA

Hello everyone,
This is the last time I try to do something to bring back vitality to my G1.
I have a T-Mobile G1 (DREA100 PVT, Radio: 1.22.12.29) I can boot into bootloader mode and recovery mode. I have no root.
I tried to downgrade the device with the RC29 and RC30, but always without success. When the downgrade end, instead of OK signal to each component, returns the heading "Installation Fail."
Before creating the GoldCard which with DREADIAG.nbh helped me to start it in recovery mode, the phone started only in bootloader mode.
Now I can do a full analysis of the phone with the DREADIAG, but not found anything abnormal.
If I turn on the phone without pressing extra keys, is on the word "T-Mobile G1".
Please if you have any alternative idea to "try a downgrade RC29" do your thing, I'm using it damn phone.
Thank you everyone.
P.S.: Sorry for my Eng.

I had a hard time understanding exactly what you're trying to say, but i'll give it my best shot.
If you're able to access the bootloader, then you're not bricked. If you have the default, original, stock bootloader (spl) you shouldn't have a problem downgrading using the dreaimg.nbh rc29 file. (if you do, then i have no idea...) If you have any other spl, hard/danger-death, then you should be able to get into fastboot and flash a rooted recovery image (cyan 1.4, amon_ra 1.5.2) - there are guides within the forums describing how to do this.
Once you have a modified recovery image and an spl that will enable you to flash custom rom's , just flash as normal

I have original SPL and have a problem to downgrade using DREAIMG.nbh (RC29) file. Every time (with many many different downloaded files) INSTALLATION FAIL.
I can't use fastboot because my phone isn't recognized by adb.
Help...

_tony_ said:
I can't use fastboot because my phone isn't recognized by adb.
Click to expand...
Click to collapse
Last time I checked, adb won't work unless the phone's OS is on. However, fastboot will work when in bootloader mode without adb. Just turn the phone off, hold camera and turn it on. Plug your USB cable in then hit the back key, it should read "FASTBOOT USB". You're in.

Try re-downloading the DREAIMG.NBH, maybe yours got corrupted.

jayshah said:
Last time I checked, adb won't work unless the phone's OS is on. However, fastboot will work when in bootloader mode without adb. Just turn the phone off, hold camera and turn it on. Plug your USB cable in then hit the back key, it should read "FASTBOOT USB". You're in.
Click to expand...
Click to collapse
No man, when I'm in Bootloader mode and plug-in the USB cable, the phone say me "Serial 0".

_tony_ said:
No man, when I'm in Bootloader mode and plug-in the USB cable, the phone say me "Serial 0".
Click to expand...
Click to collapse
If it says Serial 0, it's telling you that something is wrong with your SDCARD.
Format the card again and choose the FAT32 file system.

I have a sd card that would not work properly...found it out the hard way with similar issues to yours! It worked fine in the phone for storage, but not for loading roms or updates. Went to another card after thinking my phone was screwed up and it worked fine.

But I tried to flash the ROM with 3 different SDCard, the last is now a GoldCard (without which I could not use the dreadiag.nbh) and also one of those 3 has already root dream of a friend ...
P.s.: On my Dream has never been turned on "debug usb"

Are you sure the SDCARD is formatted to FAT32? Also, when you used the other Cards, did it also say Serial 0?

Bavilo said:
Are you sure the SDCARD is formatted to FAT32? Also, when you used the other Cards, did it also say Serial 0?
Click to expand...
Click to collapse
Yes, I'm sure! I've tried many times the procedure
- FORMAT in FAT32
- DOWNLOAD RC29
- EXTRACT DREAIMG.nbh in / (of sdcard)
- INSTALL
but everytime this fail.
Yes, with any sdcard the phone say me "Serial 0"

Re-format your card. Format it for FAT32. Change the allocation unit size to 4096 bytes. That should help. Let us know.

_tony_ said:
Yes, I'm sure! I've tried many times the procedure
- FORMAT in FAT32
- DOWNLOAD RC29
- EXTRACT DREAIMG.nbh in / (of sdcard)
- INSTALL
but everytime this fail.
Yes, with any sdcard the phone say me "Serial 0"
Click to expand...
Click to collapse
Yes, I'm sure! I've tried many times the procedure
Right way of writing it:
Yes i'm sure! I've tried the procedure many times.
but everytime this fail.
right way of writing it:
but it fails everytime.
...sorry OCD -.-

Ty Macrophage001 for your lesson...but this is a English or Phone/PDA forum???
I'm Italian and my English is not good, it's a problem for you? Others have understood what I meant...so if you don't understand is not a problem, but ridicule me is really stupid. -_-'
Thank you again...

[Q] HTC Touch Diamond 2, not flashing

Dear Honorable Seniors, I am so obsessed to get some troubles with my htc (Touch Diamond 2).
I want to get rid off from my ROM that is already available on it (I dont how to find it is official or cooked and which is that version or name). I try to download many cooked ROMs to flash but tried two:
1-energy
2-mozart
but everytime flashing process stopped at 0% percent and after 6-7mint it display a window for recovery. I do restart my system and got the prior windows version, no flashing at all.
I thought there may be Hard-SPL issue (although I dont know what is it). I download its compatible version and try to flash Hard-SPL it also stuck at 0% and not moving upwards.
Help will be appreciated in their respect.
Sorry if my english not comprehendable I am not english speaking person.
regards,
Muqaddas Shahzad
[email protected]
+923222000048

1. Install HSPL. Follow instructions in the thread.
2. Install custom ROM.
You cannot install a ROM until you have installed HSPL first.

I think Muqaddas has already tried HSPL as he described in the post, but the progress stuck @ 0%.
Muqaddas, may be you can try below:
- Disable antivirus software, temporarily, on your PC
- Do HSPL (1.83 and update to 2.51)
- Use Advance ROM Update Utility to do a Task 29.
- Upgrade to latest Radio ROM, if not latest.
- Flash the ROM you wanted.
Hope this will help you .
Thanks.

dear prabhat thank to reply me dear:
1-during Hard spl I found my version is already about 2.16.415.3 and the version I got from Hard-spl link (your given) is showing 1.83.OliNex, yet I tried with this but again stuck at 0% (error code---262)......Can yoy please tell me how Can I check That my cell is already did hard-spl on it-----and how to know it is CID-Unlocked...............
2-by using Advance ROM Update utility, it also not being flashed and giving the same error 0% (code-262)
may this because of my PC operating system which is Windows 7?
but I have flashed HTC Touch Diamond in the same system.....
please help me, my already OS disturbing me alot.
i-windows (send-don't error)

muqaddas_dunyatv said:
please help me, my already OS disturbing me alot.
i-windows (send-don't error)
Click to expand...
Click to collapse
WIN7 could be your issue, it is best to use XP. Also it is important to install the enablenewrapi.cab
You can check your SPL level by entering bootloader mode (holding Volume Down as device reboots until you get to the tri-colored screen)to verify that your SPL: version has "Olinex" as a suffix.
How to flash?
RUU.exe method;
1. Download enablenewrapi.cab, copy to your device with ActiveSync (WMDC) and execute the cab.
2. Download Topaz_CustomRUU_v1.1.zip and both the 1.83 and 2.51 HSPL files.
3. Place the CustomRUU.exe and the RUU_Signed.nbh file from the 1.83 version into the same folder on your PC.
4. With your device sync'd, run the CustomRUU.exe and follow the prompts on your PC.
5. If successful, the progress bar will go to 100% and you can enter bootloader mode (holding Volume Down as device reboots until you get to the tri-colored screen)to verify that your SPL: version has "Olinex" as a sufffix.
If so, you've successfully flashed HSPL.
Repeat steps 3-5 for 2.51
If unsuccessful....
SD Card Method;
1. Rename the RUU_Signed.nbh to TOPAIMG.nbh and place on the root of your FAT32 formatted SD card.
2. Enter bootloader mode and it should initiate the flash. You may get an error of "No Image Found" or you get progress bar stuck at 0%. This would be a failed flash, just soft reset and you'll be back to stock.
If still unsuccessful....
Try the HardSPL_V5_00R5_183HSPL.zip

my respectable serniors please help me out, I tried to change the PC which has Windows XP, and followed all the procedures you all honored but still stock on 0%.....
dear I try to flash PHOTON ROM through storage card by renaming it and placing it into the root of SD card but not being flashed................
please help

HI Muqaddas,
The issue seems to be somewhere in HSPL and the device is not ready for any custom ROM yet. I dont think PC OS has anything to do here unless the "Antivirus S/W is disabled".
Once you device is CID unlocked you should able to install any ROM .
But as you are telling you can see "1.83.OliNex" in the Bootloader... so Can you try to update that to 2.51 and see if that work?
Also try searching the "error code---262" in the HSPL thread, whihc may give you some idea...
EDIT:
ERROR [262] : UPDATE ERROR
This error occurs during the CE ROM code upgrade process.
Solution: If this happens, you can just soft-reset the device and run RUU again. The update process will then continue.
Note: At this stage, the Wince is destroyed; instead, it is in upgrade mode.
As you said you can see the OliNex in bootloader your device is CID unlocked.
Can you try below and see if that work:
1) Upgrade your HSPL to 2.51.
2) Start Windows Mobile Device Center
3) Start your device in TriColor boot loader mode.
3) Connect you USB to PC and and make sure your device bootloader white screen say "USB"
4) Now start flashing from PC using RUU.
See if this work else try "SD Card Method" suggested by Bruce.
Hope this will help...
Thanks.

On Ur phone go to Settings-> Connections -> USB to PC & "uncheck" the option Enable faster data synchronization & then try ...worked for me

I am sorry to be desperate but after following all the precedures suggested in this place I am not successful...
I was hopefull that I might flash my TOPAZ after getting 512mb card and after many struggles I arranged it for flashing .....
but after bootloader it stuched at
loading.....
please help if someone can

Try restoring your bootloader to the stock, flash a Windows stock ROM, then come back with HSPL and custom ROM.

Hey, May be you can go to service center near to you and ask them to install new ROM so that they will install new ROM and may be try to unlock the phone if it is with them...
Once they install new ROM then I think you can continue HSPL here and have fun .
Thanks.

Dear Hamsn, Where I can get Windows stock ROM, Please any link or description......

You can get that from HTC website of your region.
Goto: http://www.htc.com/uk/selectcountry.aspx
Select your country -> Click Support -> Select your device and download the latest ROM update.
Of you can grab from here: http://shipped-roms.com/index.php?category=windows mobile&model=Topaz
(File: RUU_Topaz_S2_HTC_WWE_2.53.405.5_Radio_Signed_Topaz_61.44etc.25.35_4.49.25.91_Ship.exe)
Just sync your device in PC and run the above file and all should get updated .
Cheers!!!

Moto g 2 gen's display shut downs after locking the phone or after 'screen time out'

I have Moto g 2nd Gen Indian edition phone
I have been experiencing a strange issue with my phone from past week, when I lock down my phone via power button or closing the cover of magnetic flip-shell or whether it locks it down itself after 'screen time out' automatically the display just shut downs.
The phone is actually working in background as I can see LED notification sometimes. And when I connect my phone to PC via USB it even shows the Internal storage folder. I can even feel vibration on Powering off the device.
When I try to reboot the device, it boots up normally with Motorola logo animation and everything works fine until device gets lock down and this scenario continues as I reboot it again.
Sometime I can feel the bottom speaker grill getting hotter until I 'Power Off' the device forcefully.
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
I want to clarify that my phone isn't under warranty and also I have not even tempered my phone's software it is completely stock with android version 5.0.2 (recently updated via OTA).
I'm not allowed to post the image as a new user that's why I have written some software specific detail as below.
System version: 22.56.3.titan_retaildsds.retaildsdsall.en.03 retin
Build No: LXB22.99-16.3
Base band version: MSM8626BP_1032.3112.96.00R EMEA_DSDS_CUST
Kernel version: 3.4.42-g0bea67a
[email protected] #1
Wed Aug 26 00:26:33 CDT 2015
I don't think the 'Power Button' can be faulty as it's working as intended properly and almost all the time I use the official Motorola 'Magnetic flip-shells' so I rarely use the power button.
I suspect that this issue may have been caused by some virus or malware as I had visited some torrent hosting and too much ad hosting sites before the issue started.
I contacted Motorola support via chat session and they asked me to get it to the service center, but I have read very bad reviews about service center near my location and I'm afraid to go there.
Although I'm a software developer but in the area of 'Android development' I'm totally noob so joined the XDA to solve the issue with the help of experts.
Can I have some suggestion, solution on this issue? Any help of yours is appreciated.
Also I want to know that if 'Hard reset' can't solve the issue, does that mean the software of device has corrupted?

Try a hard reset first
If not solved use an easy installer

vaisakmct said:
Try a hard reset first
If not solved use an easy installer
Click to expand...
Click to collapse
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.

smartandcool3 said:
Well Hello sir thanks for the prompt reply, as I said earlier:
So far I have tried fast booting the phone it boots up normally but issue is still there.
I even tried to run the phone in the safe mode but the issue persist even in safe mode.
I even wiped cache partition and also performed 'Factory Reset' via hard reset and soft reset but nothing is working.
So hard reset is not working for me which I have performed 2-3 times, I guess I have to go through your another suggestion.
Ok, so by 'easy installer' did you mean this method described in below link?
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612
I think method in #Post 1 is for my phone.
Does anyone have other solution or advise? Your guidance will be appreciated.
Click to expand...
Click to collapse
ya this one will be best for u

vaisakmct said:
ya this one will be best for u
Click to expand...
Click to collapse
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?

Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader

vaisakmct said:
Thats not a pblm get in just fastboot mode click installer and select option for locked boot loader
Click to expand...
Click to collapse
but as suggested by @reefuge in post #13 and #post16 in link below
http://forum.xda-developers.com/moto-g-2014/general/official-stock-firmware-5-0-2-lxb22-46-t3019612/page2
that 'Phone must have USB debugging enabled and RSA key Allowed, Usb cable plugged in and in normal use mode'
1. I have USB debugging enabled. If I plug in my Moto G a icon appears in the Notification-Center which says "USB debugging activated please click to disable"
2. if I go into the Device Manager I can see Android Device
3. I changed my USB-Setting to PTP
but nothing works.

smartandcool3 said:
Thank you,
The Easy installer method requires 'USB debugging enabled and RSA key Allowed', so I have enabled 'USB debugging' but I never get the 'RSA key allowed' dialogue.
I tried to attach cable to the different USB ports but I never get the 'RSA Key allowed' dialogue, How can I overcome this issue?
Click to expand...
Click to collapse
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here

reefuge said:
no it does NOT require USB debugging anymore (that was version 1) You must be able to put phone manually into AP FASTBOOT mode by correct key combo
read instruction in zip file and attached here
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated

smartandcool3 said:
Thank you @reefuge sir for the reply.
Does that mean I don't need Phone with 'USB debugging with RSA key allowed'?
All I have to do is to run the 'Magical batch file' of yours and watch the magic show in PC?
Ok one more question, I don't want to irritate you but I'm helpless and confused,
I wanted to ask you that after following this step in sequence:
1] ALL needed files are in the zip file you downloaded TO PC (not phone) including stock ROM files
2] Install Motorola device manager 2.5.4.exe for correct Usb drivers (choose repair if already installed) and install minimal ADB /fastboot v 1.31.exe
3] plug in Usb cable and PUT phone into AP Fastboot Flash mode
4] by holding power and volume down ( - ) until phone powers off to blank screen (may vibrate)
5] still holding both buttons count 1,2,3,4,5 and release both same time
6] Hopefully you should be in AP Fastboot Flash mode with USb cable plugged in?
7] if No go back to step [3] if YES continue
8] do not select anything on phone or press any more phone buttons - All done via pc no
9] Now run the EASY INSTALLER.bat file and watch both pc screen and phone screen
I assume that your program will show me following different menu options:
1)Flash stock ROM --- will flash stock rom / Logo / boot & recovery.img / modem files and bootloader -- this DOES NOT wipe phone so can upgrade / dirty flash keeping settings
2)Lock bootloader --- as above but locks boot loader --- tbh always better to use option 1)
3)Flash Fixed Logo -- Fixes the unlocked Boot Loader Warning EVEN if unlocked still
4)Reboot Phone -- Reboots phone --
5)Factory Reset --- wipes DATA and CACHE --- IF phone hangs at BOOT LOGO, do this Action. ALWAYS use if DOWNGRADING or Coming from A CUSTOM ROM
6)Exit --- Closes command prompt window and exits
from above 6 menu options, which options do I have to follow(related to my phone's condition) in sequence to revive my phone?
I have moto g which is unrooted, stock and with locked bootloader.
You valuable reply is appreciated
Click to expand...
Click to collapse
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run easyinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new

reefuge said:
FORGET USB debugging and developer options, NOT required - thats NO - IGNORE , not needed
simply install mdm 2.54.exe and ADB v1.31
get phone into Fastboot mode with usb cable plugged in
run eastinstaller.bat
from menu
fmenu options choose [1] and reboot phone [4] to upgrade keeping settings
or [1], [5] and [4] to FULLY wipe and reset phone as new
Click to expand...
Click to collapse
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?

smartandcool3 said:
Thank you @reefuge sir for the prompt reply and for your guidance, which actually makes the task easier for me many thanks to you sir.
I will try step '[1], [5] and [4] to FULLY wipe and reset phone as new' as mentioned, and pray to god that my days of misery gets over, to revive my phone.
Do I have to place the 'extracted folder' in my PC's root folder(which is C: drive) or I can place that 'extracted folder' anywhere on PC and execute the 'eastinstaller.bat' from there?
Click to expand...
Click to collapse
anywhere as it includes (in extracted folder) ALL the files required to make it work

reefuge said:
anywhere as it includes (in extracted folder) ALL the files required to make it work
Click to expand...
Click to collapse
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.

smartandcool3 said:
Thank you @reefuge sir for the reply, and I will try this 'Easy Method' and I will keep you posted on its progress.
Once again thank you very much @reefuge sir and @vaisakmct sir as your replies helped me a lot, I hope this issue get resolved soon.
Click to expand...
Click to collapse
Ok, Guys I was able to run the 'EasyInstaller' and it worked perfectly and magically as it should supposed to be.
Unfortunately I was not able to resolve my problem so It might be something else.
@reefuge sir your 'EasyInstaller' was awesome, and I will highly recommend it to everyone for 1-step solution in need, please keep making these kind of awesome tools.
Thank you @reefuge sir and @vaisakmct once again for all your help. If you have anymore suggestion or solution regarding my problem please let me know.

ZUK Brick... (totally)

The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me

gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
EDIT: Sorry, I post on the wrong section. If someone can move this post on the right section ...

gaara19 said:
The thing started when I had problem to charging the zuk.
Then, just before travel to SF, my mobile phone didn't charge anymore.
At the beginning, I thought it was a software issue so I started to do many manipulations in the TWRP recovery during the plane to SF.
At the end, I totally brick the phone and delete the OS(delete all the data).
So when I came back( yesterday), I tried to flash with fastbootmode and it works. But when ou have the message :"updating app 1 on 82, 2 on 82 and so on", you have at the end (starting app) and the phone restarted everytime. I tried to flash different official COS update but the result was the same.
So, in my last breath, I tried to relock the bootloader..... And reflash COS.... Big mistakes . I have no OS anymore because when i try to flash, at every step, ( recovery,system, modem and so on) a message is prompt: (impossible to flash, BOOTLOADER lock (something like that))
So i tried to unlock the bootloader but now I have this message : Impossible to do it OEM no allowed that (or something like that)....
To summarize:
- My zuk is dead
- No OS install
- No data on the phone
- Impossible to flash a new rom because the bootloader is lock
- Impossible to unlock the bootloader
But i have the Cyanogen recovery access and the fastboot mode. But only that....
If someone can help me
Click to expand...
Click to collapse
try to use QPST (Qfil) method. This is final method can bring back your phone. If fail, congratulation ! :silly:

I success with QFIL Zui works but it's awful
Unfortunately, I try to install stock cos but I have the same issue.... Bootloop after "App update message".
I don't know why

Try flashing Cyanogen Os using fastboot

I did that...
I flash with the tool via fastboot. But bootloop result...
I also tried to flash CM13 via TWRP but I have an error message...
Do you have any other solutions?

I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice

Here u go, QFIL CM 12 ROM: https://mega.nz/#!RFUw2CbZ!GXS6KeOy_8n2y_rOBJUS5WJSP5kchODcGUF0U1TxYO8

So with the ham version is the same as the QFIL version?

gaara19 said:
I don't know why, Zui works well but i can't install any other roms:
- COS crash after the first boot.
- Other roms are impossible to install via TWRP...
I don't know if it's because I have an hardware issue( Fingerprint doesn't work) so the mobile crash.
I changed the partition system type but now I think that evrything is ok : System is ext4
If you can help me, it could be very nice
Click to expand...
Click to collapse
READ THIS( use google translate)
BTW, what are the fastboot commands that you are using?