everythings work normally before i flash to lollipop using flashfire and it fails..
-try every driver version
-try change the usb module
-try on different computers / OS
its still cannot recognize my s4 active
last works phone its on NH3.. then root it using kingroot.. and replace with superSU..
then install flashfire.. flash the zip (from muniz) and it stuck at at&t logo
cant flash using stock rom lollipop via stock recovery cause its always says "status error 7" (seems like its cause by the system has been rooted), cause when it get boot its show "samsung custom" with padlock open
cant using odin.. cause cant recognize the device it self.. try change the usb module.. still cant recognize..
is it the motherboard problem?
can someone help me please
*sorry for my bad english
someone please? i can enter the stock recovery.. but i cant flash update OTA cause my phone rootedd.. always get error 7, e:signature problem
Related
Hi everyone
So here it is : No program is able to recognize/detect my Galaxy S i9000M (Bell Vibrant) when it's in download mode, so I can't flash any ROM. My phone is currently fully bricked and unusable. I cannot access to the recovery mode with the three-button thingy or by "adb reboot recovery"
I bricked using Odin 1.8, trying to flash a 2.2 froyo stock ROM from Samfirmware. The flashing went ok, but it failed to reboot. Actually, the screen was turned off and nothing was happening. I figured out it was fully bricked so I made a USB JIG, it worked. I can access my download mode.
I connected the phone to my Windows 7 computer and used Odin to flash back to 2.1 Eclair, with a stock ROM from Samfirmware. It failed (I don't remember the error message, it was a couple days ago...).
I tried with Heimdall Frontened. It had a problem uploading the .pit file, so the flashing didn't work.
Now each time i connect the phone to my computer, Windows (and Heimdall frontened and Odin) doesn't detect it,which means that I can't flash anything on it even though it is in download mode.
I have tried reinstalling like every driver on earth, still not responding.
I tried on another Windows 7 machine and on Ubuntu, the device is not detected.
I tried with different USB cables, nothing happens.
This is my hypothesis (maybe silly) : Could the problem be the Download mode being corrupted?
Whatever... I could use some help from you guys.
Thank you,
Sam
I had/have the same problem.
I installed the Samsung Kies and now my computer recognize my phone again.
But I have still no idea what I need to flash to make my phone working.
goldsage said:
I had/have the same problem.
I installed the Samsung Kies and now my computer recognize my phone again.
But I have still no idea what I need to flash to make my phone working.
Click to expand...
Click to collapse
That is strange... I tried installing Kies and it didn't detect the phone. And you could just flash any 2.3 stock ROM with Odin I guess.
Hello!
Here I am, floating through the Samsung waters
I've stuck on one part, of course; my phone is bricked, computer reads it only half way and ODIN doesn't even show any signs of life and I have no possibility to rewrite firmware up there.
What is it all about?
I've flashed the ICS up there through stock recovery before I saw on xda that new cwm or some other new recovery should be written. First, it gives me the tpm/sideload error every time I try to install new recovery, I can't even do the factory reset, anything. I can enter the recovery normally, it's just that I can't install anything. I've tried with several roms, some of them pass through normally, but the device doesn't want to boot, and when it is turning on, it just shows samsung logo and nothing else.
When I enter the recovery, it shows me this error:
Appling Muti-CSC
E: failed to mount /system (invalid argument)
and when I try to install something from that recovery it shows me this:
E: error in /tpm/sideload/package.zip
I must remark that the packages I downloaded are 100% valid, the card is regularly formated.
After that, I've tried with ODIN. I enter the download mode, but my device is recognized as modem mode. I've installed the drivers, I have good cable, I've done every little thing they mention on xda. So, let's say that my device is properly installed. But it is in modem mode only when I turn on download mode.
When I turn it to recovery mode, then it recognizes this:
-samsung usb CDC composite device (that is under the USB controllers and it is normally installed.)
-CDC abstract control model (ACM)
-CDC ACM data
-CDC Obex data
-CDC object exchange
These last ones are not properly installed, but when I send it to look for it in folder where the drivers of the device are unpacked, it says they are not found.
Is there a possibility that my computer did not manage to install all the drivers, considering that I installed them after bricking, and not before?
Is there a possibility that I manage to manually force it to recognize drivers and install them?
Is there any way that I can make it to connect with ODIN and write him official GB ROM?
Please help me, I wouldn't want to take it to service!
Using what version of cwm
Sent from my GT-S5570 using XDA
AndroidUser99 said:
Using what version of cwm
Sent from my GT-S5570 using XDA
Click to expand...
Click to collapse
none. big problem is that before I upgraded to new recovery i made mistake and i flash new custom ROM.
I really dont know what is happening with my phone, after i flash a custom rom it just didn't boot propely and then just keep rebooting itself. If i try to enter in recovery it just keep rebooting, same thing if i try to start normally, actually i can access to download mode but my computer doesn't detect my device, even in offline charge mode. I already tried to install the usb drivers but it showns an error after the installation process finish, also my computer doesn't show any USB device connected. Any suggestion? i got access to download mode but cannot flash an stock rom because my pc doesn't want to install the drivers (at least in my opinion), any help please?
same problem here..... i dont know what do too
have you tried to connect via odin & flash stock rom? which custom rom were you trying to install, have you installed other custom roms before?
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.
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