Related
Hi!
I was trying to upgrade my Galaxy Captivate following the instructions on this thread http://forum.xda-developers.com/showthread.php?t=783403
First I tried the KIES option, but ended in the phone stuck on a black screen after 2 minutes of the S logo on it.
So, I then tried with ODIN using both package, first with the original, but ended getting an error "E:Can't mount /dev/block/stL10 (Invaild argument)"
And then with Richthofen's integrated package which seems like fixed that issue. indeed did it, but not fixed the original issue, after this one I ended in the same stage than with the KIES upgrade.
I can enter on recovery mode and move using the volume up and down button, however, the "power" button to select any of the option do nothing.
I tried to connect with adb and indeed see it (when is on recovery mode)
adb devices
List of devices attached
10004cb6cc04 recovery
But can't do anything on the phone, not even reboot it with adb, the process get's stuck and the phone is not rebooted.
Anyone have any idea of what I can do now? send it to Samsung is not an option since I bought this phone in USA and I live in Argentina, this phone is not available in the country yet.
Thanks in advance.
Thread moved to Captivate Q&A.
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
http://forum.xda-developers.com/showthread.php?t=731989 saved my life! I was so angry with me for being such an idiot!. I lost all the contents on the phone, but at least got my phone working again.
By the way, to put it in download mode what I did was, remove the battery, put it back, press volume up + down and plug the phone to USB.
Thanks a lot Tazman171
No problem, just passing on info that was passed to me by helpful people at this sight. And yep, the way you did it was right, I was thinking of the recovery menu and selecting reinstall packages option, I actually was able to do it with the way I described above.
tazman171 said:
You used a rom with a kernel for Samsung Galaxy I-9000, I went through this also. The I-9000 has a "hard" home key and the kernel is telling your phone that it does also. Are you sensors acting backwards; up/down = left/right?; if so you need to flash back to stock with Odin 3 http://forum.xda-developers.com/showthread.php?t=731989
I was able to get into download mode by using the vol key like it says but I repeatedly tapped "menu" and "Home" when the little triangle kept popping up (I mean really fast tapping) and it worked. It's really hard to brick these, thought I did more than once myself.
Follow the instructions, it works great. I've had too use it more than once.
Lesson here, don't use any package that's based on a kernel for different hardware; especially the I-9000; unless specifically stated that it has been modified specifically for your phone.
Click to expand...
Click to collapse
Hey right now my phone is "bricked" because of a botched JPC Froyo ROM install and I have no way of getting it into download mode. None of the methods on the "One-Click Stock ROM" work, and a few other ones suggested don't either. I'm curious as to how you did it with tapping menu and home, etc. Would you mind posting up some instructions?
Sorry about the late reply, it was recovery mode that I got into, not download mode. You might have one of the phones that won't support the 3/2 button methods of getting to the download/recovery menus. It worked for me because my phone does support that method, it was just the I-9000 had switched my buttons around.
Hey All,
So I'm in the process of helping a friend with his Galaxy Ace from Koodo. As it turns out the phone looks like it's semi-bricked but we may be mistaken all together so here goes:
My buddy tried using SuperOneClick to root his device however half way through the process, it froze and when he restarted his device, it hangs at the Samsung logo during the startup boot sequence.
1. When using a combination of UP Arrow + Home button + Power, he receives a message stating:
"RAMDUMP Mode
(ARM9 mode)"
In this mode he cannot do very much however his PC does recognize the device. Odin does not work in this mode.
2. When using a combination of DOWN arrow + Home button + Power, he received 2 different screens. The first is a bright pink colored screen that states:
"Warning!
A custom OS can cause critical problem in phone and installed applications. If you want to download a custom OS, press Volume UP key. Otherwise, press Volume DOWN key to cancel."
Pressing the down arrow brings him back to the frozen Samsung logo on startup however when pressing the UP arrow, the phone goes into "Downloading..." mode. In this mode, Odin DOES work.
-----------------------------------------------------------------------------
Now for the troubleshooting we've done. We managed to find a few articles online that asked us to use the Odin tool. We downloaded a few different sets of the files needs (Cooper.ops, CODE, MODEM, CSC & BOOT). Odin then detects the phone in 'Downloading..." mode and proceeds to installing the rom. It completes successfully however it does not reboot. The screen simply flashes with the Samsung logo again.
The original firmware build before the device stopped working ended with TLKI4.
-----------------------------------------------------------------------------
1. Can anyone suggest anything else we can try?
2. Do you know if the bootloader needs to be flashed first and if so, how?
Note: We can not take the device back to Koodo as it was purchased on Kijiji and no receipt was provided. It's the GT-S5830D.
Thanks in advance,
1- boot into recovery and try to wipe data and cache. u can enter recovery mode by pressing home+power.
2- it doesnt matter, u already flashed new bootloader by flashing the phone via odin.
btw does the "D" in "GT-S5830D" bring any different in hardware with international regular GT-S5830 that most of us here use?
if its different by somehow, u shouldnt flash generic international GT-S5830 rom into it. i know for sure that galaxy ace korean version cannot use generic rom from international galaxy ace.
yep there are some 5830D specific roms on sammobile.. try them instead of generic ace
madman_amit said:
yep there are some 5830D specific roms on sammobile.. try them instead of generic ace
Click to expand...
Click to collapse
Can you point me to a certain rom/boot loader to download from sammobile? I was there earlier this morning however I didn't see any mention of Canada anywhere and I left before I messed things up further.
Even if you could just tell me which one it is I have to download, I'll do the rest myself.
Thanks a bunch!
an0nym0us_ said:
1- boot into recovery and try to wipe data and cache. u can enter recovery mode by pressing home+power.
2- it doesnt matter, u already flashed new bootloader by flashing the phone via odin.
btw does the "D" in "GT-S5830D" bring any different in hardware with international regular GT-S5830 that most of us here use?
if its different by somehow, u shouldnt flash generic international GT-S5830 rom into it. i know for sure that galaxy ace korean version cannot use generic rom from international galaxy ace.
Click to expand...
Click to collapse
There is no option to wipe the device. In fact, I have had other Galaxy S models and I'm pretty familiar with the screen however the Ace does not load into that recovery. Either it goes to "Downloading.." or "RAMDUMP (Arm9 mode)".
Thanks
well seems like sammobile haven't got for 5830L
but not to worry alternative site has one specifically rare rom of "D"
download it from this link
http://hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
which you originally were using.. no other things for D
password : sampro.pl
Happy Flashing
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
merrybob said:
There is no option to wipe the device. In fact, I have had other Galaxy S models and I'm pretty familiar with the screen however the Ace does not load into that recovery. Either it goes to "Downloading.." or "RAMDUMP (Arm9 mode)".
Thanks
Click to expand...
Click to collapse
he was talking about recovery menu which can be accessed pressing down home button while booting.. if device is in bootloop then try to wipe data from recovery first as that might help
madman_amit said:
well seems like sammobile haven't got for 5830L
but not to worry alternative site has one specifically rare rom of "D"
download it from this link
http://hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
which you originally were using.. no other things for D
password : sampro.pl
Happy Flashing
---------- Post added at 12:10 AM ---------- Previous post was at 12:09 AM ----------
he was talking about recovery menu which can be accessed pressing down home button while booting.. if device is in bootloop then try to wipe data from recovery first as that might help
Click to expand...
Click to collapse
Thanks buddy! I tried that exact ROM however it didn't seem to work either. I used the 'Coopers_V1.0.ops" file under the "OPS" option in Odin and the "S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4_HOME.tar.md5" file under the "One Package" option. Like I said before, the flash went through in "Downloading..." mode, and Odin said "PASS" however, when it came time for the phone to reboot itself, the screen started flashing and did nothing new. Same Samsung logo appears and it seems to hang right there.
Also I dont think the device has a same recovery menu anymore because even though I hold down the Home + Power buttons, it does nothing. It simply flases the screen at the Samsung logo screen.
Any other tips for me to try? Thanks again!
wierd that u cannot enter recovery mode while u can enter download mode and successfully flash it using odin.
even if u messed up recovery when u first use superoneclick earlier, flashing via odin should also flash it with new fresh recovery. so how long did u hold the home+power? i'm asking just to be sure. maybe u not hold it long enough for recovery mode to kick in.
an0nym0us_ said:
wierd that u cannot enter recovery mode while u can enter download mode and successfully flash it using odin.
even if u messed up recovery when u first use superoneclick earlier, flashing via odin should also flash it with new fresh recovery. so how long did u hold the home+power? i'm asking just to be sure. maybe u not hold it long enough for recovery mode to kick in.
Click to expand...
Click to collapse
I held it down for more than a minute just to make sure. As soon as I put the battery back in and try and restart the phone, it goes into an infinite loop at the Samsung screen.
Even I find it odd that the phone will go into Downloading mode but not recovery.
Any other suggestions?
try to install qtadb (google for it). connect the phone with pc via usb, launch qtadb and boot the phone. qtadb should display some logcat. paste the logcat output here. maybe we might have a clue whats wrong by looking into the logcat
but even if phone still stuck, just wait a few moment. if qtadb had access to the phone system via its native filemanger, it means u can use adb. use adb to reboot phone into recovery
an0nym0us_ said:
try to install qtadb (google for it). connect the phone with pc via usb, launch qtadb and boot the phone. qtadb should display some logcat. paste the logcat output here. maybe we might have a clue whats wrong by looking into the logcat
but even if phone still stuck, just wait a few moment. if qtadb had access to the phone system via its native filemanger, it means u can use adb. use adb to reboot phone into recovery
Click to expand...
Click to collapse
As far as I can tell QtADB isn't even detecting the phone. I have tried to complete the procedure over and over however no show. I may not have installed ADB correctly though so I'll give it a shot again a little later.
Thanks!
edited due to same soloution already posted.
tengo uno en las misma ay solucion
Oden tells me that I have successfully installed ClockWorkRecovery on my phone but I am unable to get it to boot into Recovery Mode. I have looked at the YouTube videos and read all of the threads in the forum that seemed to apply but nothing, so far, has been on point. When I simultaneously push the Home and Power buttons the phone powers up but is stuck in the Samsung splash screen. I have left the phone running for over an hour (while doing something else) only to come back to find the phone in the same condition. I am however able to boot normally and use the phone. Any advice, suggestions, even insulting ones, will be gratefully appreciated.
Well, revert to stock via odin, from there read on http://theunlockr.com/2012/06/09/how-to-install-clockworkmod-recovery-on-galaxy-mini/
yindee said:
Oden tells me that I have successfully installed ClockWorkRecovery on my phone but I am unable to get it to boot into Recovery Mode. I have looked at the YouTube videos and read all of the threads in the forum that seemed to apply but nothing, so far, has been on point. When I simultaneously push the Home and Power buttons the phone powers up but is stuck in the Samsung splash screen. I have left the phone running for over an hour (while doing something else) only to come back to find the phone in the same condition. I am however able to boot normally and use the phone. Any advice, suggestions, even insulting ones, will be gratefully appreciated.
Click to expand...
Click to collapse
have you been sure that you used the right cwn which compatible with galmin?:cyclops:
Just flashing stockrom again with odin n use compatible CWM for Mini.. CMIWW..
Sent from my GT-S5570 using xda premium
yindee said:
Oden tells me that I have successfully installed ClockWorkRecovery on my phone but I am unable to get it to boot into Recovery Mode. I have looked at the YouTube videos and read all of the threads in the forum that seemed to apply but nothing, so far, has been on point. When I simultaneously push the Home and Power buttons the phone powers up but is stuck in the Samsung splash screen. I have left the phone running for over an hour (while doing something else) only to come back to find the phone in the same condition. I am however able to boot normally and use the phone. Any advice, suggestions, even insulting ones, will be gratefully appreciated.
Click to expand...
Click to collapse
try this, work very well for me
http://forum.xda-developers.com/showthread.php?t=1342190
RipstR99CZ said:
try this, work very well for me
http://forum.xda-developers.com/showthread.php?t=1342190
Click to expand...
Click to collapse
The thread was dead for over a year. And now you revive it for no reason.
Hello everyone!!! Noob here! So, I'm having a really bad problem... My SGH-T599N (or Samsung Galaxy Exhibit from MetroPCS) has been bricked. Long story short, after finding out nothing works and stumbling upon Odin3 v3.07, I plugged my phone in (in Download Mode) and loaded a [.tar] folder in the[PDA] criteria, pressed start, and all that was shown was...
View attachment 2946077
Nothing else happened, so I unplugged my phone, pressed power button, but only the Black Screen of Death shows (says "Firmware Upgrade Encountered An Issue. Please Select Recovery Mode In Kies & Try Again"). Now, I downloaded Kies, but the problem with this phone is... THERE IS NO SERIAL NUMBER! I looked on the back in the phone, not there. I looked on the battery, and there it is! But.... It doesn't work (either that or it's not it, though it has "S/N:" and the numbers by it, but it still doesn't work). No now, I'm just in a terrible place. Plus, if I press Down Volume + Home + Power, I can still go into Download Mode, but I still have no idea where to go from here and what to do. Somebody please help me!!!
TerrBear94 said:
Hello everyone!!! Noob here! So, I'm having a really bad problem... My SGH-T599N (or Samsung Galaxy Exhibit from MetroPCS) has been bricked. Long story short, after finding out nothing works and stumbling upon Odin3 v3.07, I plugged my phone in (in Download Mode) and loaded a [.tar] folder in the[PDA] criteria, pressed start, and all that was shown was...
View attachment 2946077
Nothing else happened, so I unplugged my phone, pressed power button, but only the Black Screen of Death shows (says "Firmware Upgrade Encountered An Issue. Please Select Recovery Mode In Kies & Try Again"). Now, I downloaded Kies, but the problem with this phone is... THERE IS NO SERIAL NUMBER! I looked on the back in the phone, not there. I looked on the battery, and there it is! But.... It doesn't work (either that or it's not it, though it has "S/N:" and the numbers by it, but it still doesn't work). No now, I'm just in a terrible place. Plus, if I press Down Volume + Home + Power, I can still go into Download Mode, but I still have no idea where to go from here and what to do. Somebody please help me!!!
Click to expand...
Click to collapse
I will recommend you to search in here: http://forum.xda-developers.com/exhibit-4g
You can try and flash a stock firmware via odin, since you are able to get in download mode. Firmwares for your specific phone may be found here: www.sammobile.com
TerrBear94 said:
Hello everyone!!! Noob here! So, I'm having a really bad problem... My SGH-T599N (or Samsung Galaxy Exhibit from MetroPCS) has been bricked. Long story short, after finding out nothing works and stumbling upon Odin3 v3.07, I plugged my phone in (in Download Mode) and loaded a [.tar] folder in the[PDA] criteria, pressed start, and all that was shown was...
View attachment 2946077
Nothing else happened, so I unplugged my phone, pressed power button, but only the Black Screen of Death shows (says "Firmware Upgrade Encountered An Issue. Please Select Recovery Mode In Kies & Try Again"). Now, I downloaded Kies, but the problem with this phone is... THERE IS NO SERIAL NUMBER! I looked on the back in the phone, not there. I looked on the battery, and there it is! But.... It doesn't work (either that or it's not it, though it has "S/N:" and the numbers by it, but it still doesn't work). No now, I'm just in a terrible place. Plus, if I press Down Volume + Home + Power, I can still go into Download Mode, but I still have no idea where to go from here and what to do. Somebody please help me!!!
Click to expand...
Click to collapse
Don't know if you still need help but assuming you never replied to the other person's post eh I'm assuming you figured it out. If you didn't though I should first say that the galaxy exhibit 4g and the galaxy exhibit are two different phones. Also the official stock firmware for our phone hasn't been released by samsung for some reason so there's no way to go back to complete stock unless you make a backup. Here's a link for a pre-rooted stock rom though that you can flash through odin http://forum.xda-developers.com/showthread.php?t=2489238
Same Problem here but I am not sure how to use ODIN ?
Mr. Clown said:
I will recommend you to search in here: http://forum.xda-developers.com/exhibit-4g
You can try and flash a stock firmware via odin, since you are able to get in download mode. Firmwares for your specific phone may be found here: www.sammobile.com
Click to expand...
Click to collapse
I am having such a hard time getting My SGH-T599N to activate and I need the stock Rom Because I wiped my Android all ready. It can reach Download and even recovery but I think that it Needs the stock Firmware. I wonder if you have found the Solution yet?
[email protected]......... thank you so much
Wolf.eagle1957 said:
I am having such a hard time getting My SGH-T599N to activate and I need the stock Rom Because I wiped my Android all ready. It can reach Download and even recovery but I think that it Needs the stock Firmware. I wonder if you have found the Solution yet?
[email protected]......... thank you so much
Click to expand...
Click to collapse
Have you searched in the links above?
Hello
I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815) when it rebooted and it got stuck in download mode but as if I had initiated a new upload. No matter what I do, it doesn't reboot to anything else I have tried flashing various stock roms (even MM) ODIN sees it starts to upload but fails I dont know where to get a .PIT file to try and repartition. I have also tried pressing multiple button combinations to no avail Only by pressing Power and Volume down it instantly reboots to the same screen
Any ideas before I have to resort to official service (and be financially skinned)? All help will be greatly appreciated
Thank you
MarketElf said:
Hello
I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815) when it rebooted and it got stuck in download mode but as if I had initiated a new upload. No matter what I do, it doesn't reboot to anything else I have tried flashing various stock roms (even MM) ODIN sees it starts to upload but fails I dont know where to get a .PIT file to try and repartition. I have also tried pressing multiple button combinations to no avail Only by pressing Power and Volume down it instantly reboots to the same screen
Any ideas before I have to resort to official service (and be financially skinned)? All help will be greatly appreciated
Thank you
Click to expand...
Click to collapse
Remove the USB cable. Press and hold the Home, Vol Down and Power buttons for about ten seconds. The tablet should power off.
lewmur said:
Remove the USB cable. Press and hold the Home, Vol Down and Power buttons for about ten seconds. The tablet should power off.
Click to expand...
Click to collapse
It did THANK YOU VERY MUCH
Problem is when I try to power it on, it doesnt boot normally. If I try to reflash a ROM (by pressing Home+Power+Vol) it shuts off (it seems that battery is at or near at 0%?)When I try to charge it, it boots instantly and goes to that screen again Have I bricked it somehow?
Thank you
UPDATE Somehow I managed to get it into "normal" download mode and ODINflash a stock ROM With 4% battery!!!! Anyhow now it seems to work fine When it'll be fully charged I shall make a full control
Any ideas what this incident was? Should I post the incident somewhere for future reference to any who might face the same situation?
Thank you
PS Is, by any chance, there a way to untrip KNOXX counter that I have missed?
MarketElf said:
UPDATE Somehow I managed to get it into "normal" download mode and ODINflash a stock ROM With 4% battery!!!! Anyhow now it seems to work fine When it'll be fully charged I shall make a full control
Any ideas what this incident was? Should I post the incident somewhere for future reference to any who might face the same situation?
Thank you
PS Is, by any chance, there a way to untrip KNOXX counter that I have missed?
Click to expand...
Click to collapse
There is a BIG difference between "autoboot" and "autoroot". The app you tried to install attempted to ROOT your tablet. Had you used the Power, Vol Down and Home buttons BEFORE trying to download what were apparently the WRONG ROMs for your tablet, there might not have been a problem. But there is no telling what the cf-autoroot app did. (Except trip your Knoxx flag.)
If flashing the CORRECT stock ROM didn't restore Knoxx, then nothing will. But if you tell Sansung you "accidentally" entered the download mode and didn't know how to get out of it without attempting to download something, then they might honor your warrantee anyway. Just make sure you tell them you WERE NOT trying to root your tablet or install a custom ROM.
lewmur said:
There is a BIG difference between "autoboot" and "autoroot". The app you tried to install attempted to ROOT your tablet. Had you used the Power, Vol Down and Home buttons BEFORE trying to download what were apparently the WRONG ROMs for your tablet, there might not have been a problem. But there is no telling what the cf-autoroot app did. (Except trip your Knoxx flag.)
If flashing the CORRECT stock ROM didn't restore Knoxx, then nothing will. But if you tell Sansung you "accidentally" entered the download mode and didn't know how to get out of it without attempting to download something, then they might honor your warrantee anyway. Just make sure you tell them you WERE NOT trying to root your tablet or install a custom ROM.
Click to expand...
Click to collapse
No it did not I had installed https://play.google.com/store/apps/details?id=simple.reboot.com Which requires preexisting root And NO I did NOT try the wrong ROMs I might be a noob but NOT THAT much of one
The Download "mode" that this bugger of an app got my S2 in is NOT true download mode after all...
Knox has NOTHING to do with the incident Was tripped when I firstly rooted the tablet some months ago Just asked if there is a way of untripping it that I had missed
Thanks so much for your effort to help, anyway.
PS Tablet now running with rooted MM and everything (but Knox ofc) looks fine
MarketElf said:
No it did not I had installed https://play.google.com/store/apps/details?id=simple.reboot.com Which requires preexisting root And NO I did NOT try the wrong ROMs I might be a noob but NOT THAT much of one
The Download "mode" that this bugger of an app got my S2 in is NOT true download mode after all...
Knox has NOTHING to do with the incident Was tripped when I firstly rooted the tablet some months ago Just asked if there is a way of untripping it that I had missed
Thanks so much for your effort to help, anyway.
PS Tablet now running with rooted MM and everything (but Knox ofc) looks fine
Click to expand...
Click to collapse
Well forgive me for misinterpreting your OP which stated "I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815)". That does say "cf-autoroot" doesn't it? My interpretation of that sentence was that the "reboot app" you were "testing" was actually "cf-autoroot". Can you possibly see how someone could make that mistake?
So what actually took place was that you installed an "autoboot" app on your rooted Tab S2, which was rooted via cf-autoroot, and when you tested, using the new autoboot app, it booted to a non-working download mode. When you then tried to flash a legitimate ROM via Odin from this bogus download mode, it simi-bricked you tablet. Is this correct? I have seen this happen when a multi-boot app tries to boot the stock recovery download mode when you have TWRP installed. Stock recovery download mode no longer works once you have flashed TWRP. The Power, Vol-, Home key combination will exit from the non-functional stock download mode.
lewmur said:
Well forgive me for misinterpreting your OP which stated "I was testing an auto reboot app in my tablet (cf-autoroot rooted Tab S2 T815)". That does say "cf-autoroot" doesn't it? My interpretation of that sentence was that the "reboot app" you were "testing" was actually "cf-autoroot". Can you possibly see how someone could make that mistake?
So what actually took place was that you installed an "autoboot" app on your rooted Tab S2, which was rooted via cf-autoroot, and when you tested, using the new autoboot app, it booted to a non-working download mode. When you then tried to flash a legitimate ROM via Odin from this bogus download mode, it simi-bricked you tablet. Is this correct? I have seen this happen when a multi-boot app tries to boot the stock recovery download mode when you have TWRP installed. Stock recovery download mode no longer works once you have flashed TWRP. The Power, Vol-, Home key combination will exit from the non-functional stock download mode.
Click to expand...
Click to collapse
Well "cf-autoroot rooted Tab S2 T815" was in brackets and AFTER "my tablet" wasnt it? Anyhow, I can understand misreading, no worries
Pretty much what you describe, yes. Differences: A. I had never installed TWRP B. Still dont know how exactly I managed to get it to "normal" download mode! I had managed to shut it down with the button combo you suggested only to find out that it was almost out of battery Trying to find a way to charge it, it started rebooting even after pressing "your button combo" In the effort to stop that I got in "normal" dnload mode again Without losing a second flashed the first stock ROM I've found on my HD and, voila, it was up and running After I had it charged I flashed MM(it's blazing fast Way faster than Lolli) and rooted it with cf-autoroot Everything seems to go smoothly now
I'd like to come to the bottom of this and post problem and solution to the appropriate thread as I havent found any other references and it might occur to somebody else (that app has over 100K of downloads)
I thank you once more
Most of what I've read was user error.
You obviously selected to boot to download mode from the app.
Nothing wrong with that as that is exactly what it did. Nothing bogus about it.
The problem started when you panicked and ended up half flashing something with a flat battery.
All you really needed to do was hold POWER + VOL DOWN to exit down load mode.
You would have rebooted just fine. Your OS would have still been intact.
You eventually got to 'Real' (as you call it) download mode by pressing the right button combo after at least getting some charge in the device.