Related
I was using Odin to install [KERNEL] stock+Voodoo stable 5.x for Vibrant and something went wrong, I'm not sure what but now I am stuck with the phone ! pc screen.
Odin will not recognize that there is a phone there if I just start a download Odin tells me <OSM> All threads completed. (succeed 0 / failed 0)
In another thread (whose fix didn't help me out) I read
masterotaku said:
Because..... "Phone ! PC" is not a hard brick. I've "Phone ! PC" bricked my Vibrant dozens of times.
Glad you've recovered though. It can be a scary screen if you're not used to seeing it!
Click to expand...
Click to collapse
Are there other recovery techniques?
Did you get where it says Download Mode? If not, take the battery out, put it back but don't turn on the phone. Then open Odin load the pit files and pda. The next step with the phone off, hold the volume up and down the same time and plug the usb cable while holding up and down buttons and voila....you will have COM # showing up in your Odin and ready to flash again
Check here :http://forum.xda-developers.com/showthread.php?t=810130&highlight=odin
dany865, following your instructions Odin did recognize that there was a phone attached. 0:[COM5] and I'm flashing the PIT and PDA from the thread you linked me to now. It's a slow moving process!
So slow that I swear it was frozen so I took and chance and closed ODIN, after all what was the worst that could happen I was already staring at a brick, and rebooted the phone. PRESTO, it was back to JI6.
I went straight to MiniKies and put 2.2 on that phone, then spent a bunch of time reinstalling applications and configuring ADWlauncher.
So far all I know for sure that was lost was my finely tuned setup, root access, and a month of SMS messages that were not backed up.
Thank you!
I you are gonna root I would highly recommend to get "Titanium backup pro". It makes the setting up process 10x's faster and has a tin of other great features.
Received a OTA update yesterday on my Rooted, Samsung Fascinate. After the update phone hangs on boot screen. Powering the device while holding the volume buttons gives me the Android System Recovery <3e> Screen. On this screen I have a bunch of E: Failed to open Recovery, cache, data kernal etc. (I can give all specifics if needed)
If I press the home button I get what looks like a screen to update the phone (Android Character with Triangle) From here I tried the instructions from the "How to recover from any brick" thread. Neither method is working. Any ideas?
From the boot screen I am also not able to scroll up or down to select a wipe apply update from SD Card etc.
Any help would be appreciated.
Thanks
I don't know how to fix it (don't get discouraged I don't know a lot in this area) but it seems to me if you play your cards right you might be able to complain to verizon and get an early upgrade out of it. A galaxy nexus would look mighty fine in your pocket.
probably a conflict with being rooted when it updated. Odin back to stock and update completely and then re-root.
Sent from my icecream fast
1. Download this file to your PC get you to a rooted ROM with the proper recovery: http://www.mediafire.com/?d0wha8lc1hjxxdf/geewiz-2.3-fullwipe-11302011.tar.md5 (this is the EH03 GeeWiz Odin Package ROM by djp952)
2. Boot phone in download mode by powering phone off, hold down vol button on phone, connect cable to PC (there is no need to remove battery)
3. Open Odin and Place the GeeWiz file you just downloaded into the PDA slot, click Start
4. Your phone should now be on the EH03 GeeWiz ROM
5. If you want to flash a different ROM, download the zip file for the ROM of your choice onto your phone (use the phone to download it), reboot into Recovery (what you booted into before is the stock Samsung recovery, not the Clockwork Recovery you need), choose "install zip from sd card", select "choose zip from sd card", choose the Download folder (the folder in which your zip file should appear), choose that zip file, and install.
6. Profit.
Has anyone seen John Connor?
I gave this a shot, and I am thinking either my phone is not in "Download Mode" if that's possible or its a driver issue. Here is the response I get from Odin V1.83
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> geewiz-2.3-fullwipe-11302011.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> All threads completed. (succeed 0 / failed 0)
I have multiple Samsung Cables (I tried all of them) but it is possible I am not using the one that came with this phone (Could this be an issue?)
I am using windows 7 64 X64 The phone shows up in the in the device manager as LibUsb>Samsung Andriod
On the recovery screen I have noticed if I push the home button it flips between the Android and the Triangle to a screen that shows all the files the boot loader cannot find. Does it matter what screen I am on when I try the upload?
Thanks in advance for any advice for a n00b!
You need to download the Samsung USB drivers for your PC, as it appears to be not recognizing your phone properly. You should be able to find what you need on Samsung's website. Hope this works.
Has anyone seen John Connor?
Ok So I have removed / Re-Installed the drivers on 2 different machines (One Win 7 64 Bit other is Win Vista 64 bit. I get the same results on both machines. Any other ideas?
Have you tried Heimdall? For some screwed up reason odin will not recognize my phone but Heimdall will.
mentose457 said:
Have you tried Heimdall? For some screwed up reason odin will not recognize my phone but Heimdall will.
Click to expand...
Click to collapse
I gave this a second try. The "Driver" portion of the software detected the Samsung_Device and I was able to install the driver. However when I try the front end I get an error "Failed to Detect Compatible Device"
Im getting really close to jumping ship on this one and going out and getting a new phone.
I appreciate all the help!
Found a few threads on Verizon forums. Sounds like there have been a few people run into the same issues. Anyone tried returning a rooted phone to Verizon? If so and they caught it what were the repercussions?
ascottn said:
I gave this a second try. The "Driver" portion of the software detected the Samsung_Device and I was able to install the driver. However when I try the front end I get an error "Failed to Detect Compatible Device"
Im getting really close to jumping ship on this one and going out and getting a new phone.
I appreciate all the help!
Click to expand...
Click to collapse
Just to be clear, you are putting the phone in download mode then installing the drivers via zadig right? That should work.
loading drivers in windowz is the most retarded thing in the world. You dont happen to have access to a computer running linux do you? Heimdall works flawlessly in linux.
Good Questions
1- Yes I am installing the windows drivers as you describe
2- As for download mode how do I go about doing that? All I can seem to do is to boot to the <3e> bootloader. I cannot scroll up or down through the options. However I can press the home button and it goes to a picture of an Androind with a triangle around it (Green Droid, White Triange, Orange !)
3 -I didn't realize that heimdall worked in linux. I just downloaded it and gave it a spin in Ubuntu. I am getting the same error "Cannot Detect Download mode Device"
ascottn said:
Good Questions
1- Yes I am installing the windows drivers as you describe
2- As for download mode how do I go about doing that? All I can seem to do is to boot to the <3e> bootloader. I cannot scroll up or down through the options. However I can press the home button and it goes to a picture of an Androind with a triangle around it (Green Droid, White Triange, Orange !)
3 -I didn't realize that heimdall worked in linux. I just downloaded it and gave it a spin in Ubuntu. I am getting the same error "Cannot Detect Download mode Device"
Click to expand...
Click to collapse
To enter download mode power off your phone, pull the battery, hold the volume down button while plugging in your phone. The screen should show a yellow triangle with the Android guy in the middle.
Sent from my SCH-I500 using XDA App
I have been digging around and I stumbled onto the correct procedure for getting to download mode. I don't know how I missed this *FACEPALM*
I want to say thanks to everyone. I am back up and running. Thanks to all for the help!
Excellent! I was starting to think you had a hardware problem as in a faulty micro USB port on the phone...
Has anyone seen John Connor?
Would just like to add that the 2.3 OTA soft bricked my fathers stock phone. I am now hunting the non rooted file in another thread to odin or heimdal back to 2.2 to alow me to try again.
Verizon LVL 2 says he checked and I am the first customer to report a bricked phone from the OTA to 2.3. Yea... right.
Here is the guide I followed to get my phone back to stock (It includes download links for stock roms.
This is the one part missing from this tutorial. Probably because it assumes that these steps are known if someone has bricked a phone
make sure u have your samsung usb cable plugged into the pc but not into the phone (not yet at least) and make sure u remove your battery.
step 1. hold down the volume down button and continue holding
step 2. whille still holding down the volume down button, plug your phone into the usb cable
step 3. while still holding down the volume down button, pop your battery in.
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Sounds like the flash memory may have failed in some manner. Two words: Warranty replacement. Getting a replacement through Verizon is usually fairly simple once they realize they can't try and fix it by pressing factory reset in the settings. Did you try Verizon first or go straight to Samsung?
Edit: Nevermind, I just realized it says you are "Custom." My reading skills suck tonight. Maybe you can convince someone at Verizon that you tried some stuff on the internet to fix it and then it said custom. I don't know if a JTAG would help or not in this case. Maybe someone can chime in on that...
FreaKaDroidXYZ said:
I need some major help.
My Verizon Note 3 was rooted but nothing else special. Recently, it started locking up when I turn it on in the morning, had to remove the battery and restart. Sometimes the power button would stop responding. And finally, after a phone call, it restarted itself and gave me a message "Could not do normal boot." Please see pictures.
It would not go into the recovery mode, but would always go to the Fastboot mode (Download mode). I tried Odin but no success. I talked to Samsung and the rep said that's what happens when you root (standard BS), but still allowed me to send it in. I got it back a week later, not fixed, but with paperwork saying Warranty Void due to Root.
I've been searching everywhere to see if I can find some information on how to recover from this, to no avail. I've installed the correct USB drivers many times, but neither ADB Devices nor Fastboot Devices commands will find anything attached. Odin continues to fail, sometimes with a message saying "Erasing Userdata partition" or something like that. It wouldn't show when I was taking pictures to post here.
Any suggestions or ideas? Again, no access to Recovery. Odin failes with or without the PIT file.
Thank you in advance.
Click to expand...
Click to collapse
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
az_biker said:
Have you tried factory reset from Android Recovery (vol up, home, pow)?
I haven't run into anyone yet who couldn't undo soft brick from Odin... My only suggestion would be to start from scratch and follow the link in my sig...
I know you said you d/l sammie usb drivers a few times, try uninstalling ANYTHING on your pc from control panel>uninstall programs that says Samsung... THEN download and install newest drivers...
If following the guide in my sig doesn't bring you back, you'll be the first! Best of luck!
Click to expand...
Click to collapse
Unfortunately it did not work. Same message on the phone "MMC: mmc_read fail", and in ODIN:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I also tried it with and without the PIT file and both the same result. Do you think this may be an actual hardware flash memory failure? Is there a way to format around the bad portion of the flash memory? I wish I could try some adb or fastboot commands but it does not show in either.
Any other thoughts or suggestions would be very much welcomed and appreciated. There's gotta be a way...
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I'll try those things. I cannot go into recovery unfortunately. It just says "Recovery Booting" to get my hopes up, and then says "Could not do normal boot." Next line "ddi : mmc_read failed". Then goes into the ODIN Mode.
I'll report back after I try your suggestions... Thank you.
Click to expand...
Click to collapse
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
No success...
az_biker said:
Pull battery in between attempts, and try diff usb ports on pc too
Notorious 3
Click to expand...
Click to collapse
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
not sure it would help but will it safe boot
power plus hit the menu button
Thank you for your inputs. I wish Samsung would've done a bit more than to just reject it with a Fail Description as "Device Rooted." I've been a loyal Samsung fan til now.
az_biker said:
If you can't even get to odin without mmc read, maybe it is your memory. Sorry I couldn't help, can't beat hardware failures. .Best of luck
Notorious 3
Click to expand...
Click to collapse
Unfortunately it goes straight into the Download mode no matter what I try...
NinCaptain said:
not sure it would help but will it safe boot
power plus hit the menu button
Click to expand...
Click to collapse
try the pit file by itself??
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
PS - don't bother with fastboot, this device does not have fastboot enabled, only Odin. You're not gonna get a response that way regardless.
Yes. Tried that. There's only 1 Verizon PIT file I found anywhere. Would a different PIT file work?
oneandroidnut said:
try the pit file by itself??
Click to expand...
Click to collapse
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
siciliano777 said:
lol @ Samsung. That's NOT what usually happens when you're rooted. There's quite a large percentage of us that are rooted with zero issues...shame on them for not replacing it.
Anyway, are you sure you were *only* rooted? You didn't try to flash a ROM or mess with partitions?
And it's vol down + home + power for recovery. Did you pull the battery first before going into recovery?
Click to expand...
Click to collapse
FreaKaDroidXYZ said:
I know, I've been rooting for years, many Samsung S3, S4, Note 2 and 3's. But I wasn't gonna argue with the low-tech rep when she was gonna let me send it in. I was hoping for a motherboard replacement but that did not happen.
Yes, I "only" rooted. I was just about to do some more because of other issues (like the power button and the locking up first thing in the morning) when this happened. I never expected anything I couldn't undo via recovery or ODIN or something I can find on XDA...
I've tried VolUp+Home+Power, VolDown+Home+Power, VolUpDown+Home+Power, just about all combinations, always with a battery pull. It always goes to the Download mode... I cannot get into Recovery. Tried all 4 of my USB ports with a few different USB cables. Tried my Windows 7 laptop and my iMac.
Click to expand...
Click to collapse
Looks like you've done everything I would do. Maybe list it on Craigslist or swappa as 'dev project' or 'for parts' and get something out of it? Sorry to see you stuck like this.
Notorious 3
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
---------- Post added at 10:45 AM ---------- Previous post was at 10:41 AM ----------
2swizzle said:
I had the same issue, try the steps below:
If your able to go into recovery factory wipe everything (if not go to the next step)
Flash the pit file by itself,
After flash is successful reboot and go straight into recovery, wipe everything
go into download and flash the stock firmware
If this doesn't work also re-download the firmware and pit using a windows PC, I've had issues with Macs download the correct file... Hope this helps, I had the same issues as you, in the end I had to re-download the software and follow the steps above, took me two days to fix the problem but it ended up positive.
Click to expand...
Click to collapse
Also delete and reinstall your drivers, from time to time they get screwed up on PC. If you want feel free to send me your phone and I will test for you, I've been around the android world for a long time and have f up my phones/tablets many times but never had a hard brick.
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Kies 3 is telling me that the device is not supported. It looked so hopeful for a little bit. Trying to find a workaround but haven't found one yet.
ryanbg said:
Have you tried restoring using Samsung Kies? If you are in stuck in Download mode, this may work. Give it a shot.
Click to expand...
Click to collapse
I attempted to root my phone using Chainfire's method. Evidently, before I started I failed to check for two things, one to make sure usb debugging was properly set. The second thing that I failed to do was insure that I unchecked block reactivation in security options. Now I can't do anything with the phone. It will go into the flash rom mode (down vol. home and power). When I run Odin I get a message saying that the process failed (using cf-autoroot). Then if I try to reboot my phone with the power button, or with (vol.up, home and power) I get a message stating "firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Of course the phone won't connect to Kies. I am hoping this doesn't mean I have bricked my phone!
Can anyone offer a suggestion please? I am desperate.
Thanks for any and all help!!
Ignoring instructions can have consequences. You've probably got some messed system files now. But you can recover with Odin.
Backup your photos and anything else of importance. Then do a factory data reset (in the Settings menu), followed by using Odin to flash the full stock firmware image for your device /carrier.
That will take you back to a stable, stock system. To make rooting easier you would do well to choose a S5 4.4.2 firmware image with a build date before June 3rd.
.
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.