Database Develop

Can't flash ROM: Wipe all and don't have OS

Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.

zenneka said:
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
Click to expand...
Click to collapse
Try another usb port and/or another usb cable. Also make sure that nothing with kies is runnung in background if you happens to have that installed.
When you connect with adb, also take a look on your phone screen if it asks for authorization to connect.
You got both download and recovery so problem is with connection/drivers.

zenneka said:
Hi there.
I recently flashed the OmniROM to my i8190, but since it got several issues, after two weeks i decided to flash stock ROM.
So i enter TWRP recovery and wipe all data on the smartphone, but then my computer crashed and lost the VM that got Odin and drivers etc. so in a new VM i decided to try to flash, but now i can't.
Odin doesn't recognize my i8190, i thought ADB sideload could do the trick following this guide http://forum.xda-developers.com/showthread.php?t=2559200but all i got was:
error: device not found
Now i ended up with a pretty brick hahaha.
How can i flash a ROM ..ANY to my phone.
I got another i8190 so i installed the drivers from it to the VM, all except the MTP device, that got error.
I also installed SAMSUNG drivers, but nothing, ... i'm kind of losing it now hahaha.
Can someone helpe me flash this thing?
a) I CAN enter TWRP Recovery
b) I CAN enter Download Mode
c) Don't know if Odin doesn't pick it up since USB Debug i presume it's not on, but then again, since no OS is installed, i don't know how to turn it on from recovery or something like it.
Click to expand...
Click to collapse
Try this :
If you have an external sdcard in your s3 mini then :
1. remove it and put it into a other phone
2. download a ROM and move the ROM what you downloaded to your external sdcard
3. Put the external sdcard back to your s3 mini
4. Go to recovery and choose "install from external sdcard"
5. And intstall the ROM
6. Done! You have a OS again.
It's very easy and if you don't have a external sdcard then you have a big problem bro

shelves mmerese
xXPR0T0TYPEXx said:
1. remove it and put it into a other phone
Click to expand...
Click to collapse
If you have an adapter (micro SD to SD) then you should be able to insert the card into a card reader. This will probably be easier than trying to find another phone.

MarisPiper said:
If you have an adapter (micro SD to SD) then you should be able to insert the card into a card reader. This will probably be easier than trying to find another phone.
Click to expand...
Click to collapse
Yeah i did this, but no luck at all.
Finally i change the usb driver, installed Kies again and voilá! Odin picked up the phone and flash were on .
Thanks to all.

Glad you've got it sorted.
I've noticed my PC wants to install drivers for the phone almost constantly. Every small change seems to result in a change of driver. It can be frustrating.

MarisPiper said:
Glad you've got it sorted.
I've noticed my PC wants to install drivers for the phone almost constantly. Every small change seems to result in a change of driver. It can be frustrating.
Click to expand...
Click to collapse
due to windows updates this should be expected that certain third party software like the drivers would need updates
so that leaves two choices
either keep your stuff up to date
or
get left behind and drowned in problems

Messed Up while rooting Ace GT S5830, bootloop

I was trying to root the device with android 4.4.2 but in between i messed up. and my mobile is not booting. i tried to reflash it but then i found that i m unable to open recovery mode. after that i thought to flash it via odin but when i connect the mobile with my laptop it does not recognise my device on download mode and odin cant find my device too... plzz help...
and im also confused which usb driver should i install ( i have rooted my mobile and samsung driver is not working)
javed

javedakhtar said:
I was trying to root the device with android 4.4.2 but in between i messed up. and my mobile is not booting. i tried to reflash it but then i found that i m unable to open recovery mode. after that i thought to flash it via odin but when i connect the mobile with my laptop it does not recognise my device on download mode and odin cant find my device too... plzz help...
and im also confused which usb driver should i install ( i have rooted my mobile and samsung driver is not working)
javed
Click to expand...
Click to collapse
But... Android 4.4.2 is already rooted, isn't? :weird:
Try to uninstall Samsung's drivers and reinstall it
Odin must recognise your device if it's still alive.
Which ROM are you using? and which file did you flash to root your device?

Try adb reboot, or adb reboot recovery

Only use proper root.zip only. Otherwise phone will damage.

[HELP] nokia x2ds rm-1030 dead, flash 2.1.0.12 complete, flash 2.1.0.13 stuck

Hello ned help..
rm-1030 flashing rom 2.1.0.12 complete Done
i have two version
RM1013_059V788_2.1.0.12 and
RM1013_059V786_2.1.0.12 but still dead..
Usb detect as emerency connectivity
when im flash using rom rm1013_2.1.0.13_059V78 always stuck at rm1013_2.1.0.13_user_NON-HLOS.bin
and shown error dialog "failed using firehouse protocol"
need help..
ive try to redownload ROM.. but keep error
im sorry i cant upload picture coz need 10 posts but im using txt file

maybe the firmware you downloaded is corrupted.. where did you downloaded your firmware files? I use navifirm+ but yesterday I'm trying to redownload a rom but navifirm+ seems to be not working any more..

thaks for replay,
iv downloaded from Package Majnager .. and from this seidea.com/tag/rm-1013-2-1-0-13/
its still blank screen and just detect "emerency connecivity

first download nokia-x2-tools.v.1.2.en.exe, from the tool install drivers.. then go to your "C:\ProgramData\Nokia\Packages\Products\RM-XXX" and delete all files or move it somewhere if you don't want to delete.. and replace everything with the files that you downloaded.. and run "Lunch Nokia Care Suite" as administrator.. and flash your firmware..

thaks...
I thinks its hardware problem.. coz i have 5 different firmware and already used maximal method
change folder.. remove.. redownload.. and anythink
and my phone cant detect fastboot or recovery
btw thaks

aw.. that's too bad.. I fixed my completely dead x2 with that method though.. it has no fastboot and undetected adb but I recover it somehow, I think it's just a luck..

I have exactly same problem havent found solution yet.
I have same problem too
arisjb said:
hello ned help..
Rm-1030 flashing rom 2.1.0.12 complete done
i have two version
rm1013_059v788_2.1.0.12 and
rm1013_059v786_2.1.0.12 but still dead..
Usb detect as emerency connectivity
when im flash using rom rm1013_2.1.0.13_059v78 always stuck at rm1013_2.1.0.13_user_non-hlos.bin
and shown error dialog "failed using firehouse protocol"
need help..
Ive try to redownload rom.. But keep error
im sorry i cant upload picture coz need 10 posts but im using txt file
Click to expand...
Click to collapse

Remove battery from device atleast 1min
Insert battery
Start device in bootloop and if not start only connect to PC
Start Nokia care suite >product software > open product> select device and flash

jepr0x1011 said:
aw.. that's too bad.. I fixed my completely dead x2 with that method though.. it has no fastboot and undetected adb but I recover it somehow, I think it's just a luck..
Click to expand...
Click to collapse
My Nokia X2 had also give completely dead. I tried to Flash stock ROM in it via Nokia care suite and which I've even done previously however this time my phone had gone completely blank and does not even go to recovery mode. It has gone completely unresponsive. Please help me on this.

Samsung Galaxy S3 (SC-03E) ADB No longer working

Hello All,
I have mistakenly flash something wrong into recovery and now ADB Mode in my phone no longer working either from Odin or ADB sideload from Recovery mode. I was trying to use some new custom ROM and suddenly I have faced this issue. I tried a lot of solutions here on XDA but none of them worked at the moment.
After flashing wrong thing in the recovery I feel something different running behind the recovery because when I goto recovery mode I actually see two different android logo one is a bit modern which giving me advanced and my original recovery working together which caused adb no longer detected from PC.
Anyone can help me?

Have you tried removing battery and cable for ~1minute?

Yes, I have pulled off the battery and put it back again. But still adb giving no response and my USB cable is working perfectly via Odin. Any suggestion?

Thank God, I have fixed ADB detecting issue myself. Here is what I did:
1- Install CWM recovery using Odin
2- Install the file below. I think its EFS repair file. but after installing below md5 file using Odin it really worked for me.
Thank you!

After Flashing param_bin_i9305.zip my EFS mounting failed issue is also fixed. Right now, I am getting mounting firmware failed in CWM. If this fixes I hope my SAMSUNG SC-03E will start working again.

Alcatel Idol 4 6055K problem with firmware

Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english

Hm.. said:
Hello,
I have a somewhat aged Idol 4 lying here.
This no longer boots or it hangs in the boot loop.
So I tried to install an update via a stock rom from the network via the recovery menu and ADB sideload and always got the error status 7. (Alcatel_Idol_4_6055K_01001_01002_OTA)
Resetting the system didn't help here either.
Then I tried to install TWRP on the device.
But unfortunately both methods that I tried failed.
Once via Sahara & firehose-test and the second was Suger QCT via the download mode.
But both of them got the error message NPRG Error 5002.
I have installed suitable USB drivers.
So my question, does anyone have a tip for me on how I could get the device revived?
And Sorry for my bad english
Click to expand...
Click to collapse
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.

Perdigon55 said:
Hello, I deleted my system from twr without realizing what I was doing, the result is that I stay on the Alcatel logo. My steps were, the installation of sugar, when it starts not to update the application. Choose the 6055 model, since the 6055P model that is mine does not appear in the drop-down. Before starting sugar, turn off the mobile completely and connect it off to the usb of the pc, check if when connecting it the pc does not detect it, use another cable (there are many cables that only serve to charge and not to read on the pc) Now start sugar, choose the model and click on the Udgrade tab. You will surely get several messages saying that the mobile has been modified and that you lose the guarantee, go ahead accepting the message, in a few minutes you will have it ready. Greetings.
Click to expand...
Click to collapse
Hello, thanks for the answer and the download.
I've tried the same way. I still downloaded your file and tried as you described.
Unfortunately I got the same error NPRG Error 5002 again.
Unfortunately I have no idea where the problem could be.

I found out that it could be a memory error.
As if a flash process had failed and there is no longer a correct series of partitions.
So I would need a complete original rom and would have to flash it via fastboot.
I could also try it via twrp, but I don't get this flashed.
And I don't have a complete original rom either.

Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.

Hm.. said:
Hello,
So I have now been able to flash the phone with another PC with Sugar QCT after it suddenly started up after the battery was completely empty and I charged it again.
But unfortunately the boot problem persists after turning off the phone again.
Even after replacing the battery with a new one.
Then I tried to flash TWRP via the Alcatel Flasher.
The flash process was successful but there was no TWRP on it after the reboot.
So the problem could still be somewhere else than just the firmware.
Click to expand...
Click to collapse
Hello, it may be that you are making the same mistake that I made when installing recoveri. When selecting the recovery, note that the twr is the one that weighs about 14 mb and the original one about 24 mb. I think that when you make a copy with the recovery program and then install the twr you select it wrong. In the program, do not make the copy of the recovery, skip that step and go directly to install and select the 14 mb file. You will see that this is the problem. Cheers