Hello guys... today i power my s4 mini and nothing commands worked...
The odin did not install anything and on the cell phone the blue bar did not appear and neither the Philz touch recovery did not work ...Here below I will put prints of the odin and my screen ... If someone sober how to fix please contact me ... urgently ... (already tried recovery by kies also and the same problem occurs)...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hvee said:
Hello guys... today i power my s4 mini and nothing commands worked...
The odin did not install anything and on the cell phone the blue bar did not appear and neither the Philz touch recovery did not work ...
Click to expand...
Click to collapse
I would guess memory is broke or corrupted. (so it's brick) Did it shut itself down when battery went flat? Did it turn off normally?
But normally (if your phone is still able to boot normally) when stuck at "initialization" it's a communication issue, so try use another usb cord, usb port, different version of Odin (older or newer).
Try shut PC & phone down, pull battery reinsert after a minute and try again.
[ didn't newer version of Odin have problem flashing Philz? I'd recommend TWRP from neozone thread anyhow].
But normally (if your phone is still able to boot normally) when stuck at "initialization" it's a communication issue, so try use another usb cord, usb port, different
Yes, in fact it connects normal but a little before spoiling the philz was running, however, it started installing the AOSP rom and in the middle the screen erased, I suspect it is the hd ... Now it just turns on the Odin and the screen Vibrate and black fics in Recovery mode (no signal). I tried the recovery with 3 different computers and 2 different cables ... several stockroms and several versions of Odin .. but nothing worked.
Related
Hi guys, I've been scouring Google for 3 days now and can't come up with an answer, everything says use Odin for this and use Odin for that... well I can't.
A few days ago I downloaded an app from the Google store Linuxonandriod or something like that, it's pretty much an installer to place Ubuntu on your phone side by side with Android, the instructions began with rooting the phone, I began that process and believe I accidently loaded the incorrect pda to the phone (I have so many files now on my comp, I have no clue which one I selected). Odin rebooted the phone and that's that.
If I try to turn on the phone it goes to the first screen that just says SAMSUNG then turns off, never getting to the Samsung Galaxy III screen. The USB on the phone seems to have been botched, none of my computers will recognize it (Windows or Linux), the phone will not even charge. I can however get into both recovery and download modes without problem.
Naturally, download mode does no good because the USB is useless and I do not have clockwork mod installed on the phone to bypass the verification error.
I tried to simply install clockwork via recovery in hopes that would do something, but I get a verification error with that.
Is there anyway around this using the SD card or am I holding a $300 paperweight?
Thanks
Maybe try this-http://forum.xda-developers.com/showthread.php?t=2369125
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bilgerryan said:
Maybe try this-http://forum.xda-developers.com/showthread.php?t=2369125
Click to expand...
Click to collapse
Thanks, for the link. I did check it out, but couldn't figure out what the poster was talking about with drive letters and such. That dmesg | tail told me nothing about my sd. I unzipped everything to the card by a different method but my the computer still wouldn't recognize the phone, so booting back into windows did nothing.
Sorry for the delay in response, I've been extremely busy with work.
I'm still at a total loss on this.
Hey guys,
I was just doing the process to flash the pre rooted update, I used the AFTV Utility.
The steps:
1 - Unlocked bootlader OK
2 - Changed the bootloader OK
3 - Change recovery PROBLEM
After I changed the recovery, it restarted and now hangs at white logo in startup. Tried the print screen/sys but nothing happened, the funny thing it's that it seems not to be powering USB connection since the keyboard just doesn't even light up or any of the leds when connected (like the num lock led).
Thanks in advance for any help.
The same thing happened to me with I used the AFTV utility,
Yeah I think it's bricked. I returned it for a replacement then manually rooted/unlocked/rboxed following the AFTVnews guide and and it all worked.
gabsporto said:
Hey guys,
I was just doing the process to flash the pre rooted update, I used the AFTV Utility.
The steps:
1 - Unlocked bootlader OK
2 - Changed the bootloader OK
3 - Change recovery PROBLEM
After I changed the recovery, it restarted and now hangs at white logo in startup. Tried the print screen/sys but nothing happened, the funny thing it's that it seems not to be powering USB connection since the keyboard just doesn't even light up or any of the leds when connected (like the num lock led).
Thanks in advance for any help.
Click to expand...
Click to collapse
can you post a screen shot?
Rugged96 said:
can you post a screen shot?
Click to expand...
Click to collapse
Hi Rugged, here it is:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I turn it on and it hangs at this white logo. Thanks for helping me.
Snap to the above.
Tried following the method outlined here: http://forum.xda-developers.com/showthread.php?t=2799779
However I'm not getting any power via the USB at all so can't use a keyboard.
Any ideas?
Can you guys who've bricked plug a USB device in and have it powered?
Cheers
[HELP] G532M Can't upload firmware via "DOWNLOAD MODE" since it gets stuck at half!
Hello everybody, first thread on XDA.
I will tell you about my problem since it seems to be unusual.
I have a J2 Prime G532M that one day suddenly when I woke up and I turn on my phone a blue screen with the following message appeared "this phone has been flashed with unauthorized software [...]" this made me confused because my phone had the OFFICIAL ROM and I've never rooted it.
So I downloaded the official rom from Sammobile and I tried to flash it via Odin. The weird issue here is that when I try to flash it it stucks at half of the process. Sometimes at 12% exactly when it arrives at 360mb/3.75gb uploaded to the device. I downloaded two differente roms bc I thought that the first was corrupted, but both of the roms makes the same.
Also, when the phone is in Download Mode after disconnecting and reconnecting the phone to the computer Windows shows me:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
"The last USB device you connected to this computer malfunctioned, and Windows does not recognize it".
When I first connect the phone everything its OK. After a while (10 seconds approx) the phone stop receiving data from Odin and when I
reconnect it Windows shows that.
What my problem could be? i'm reading all the comments. Thanks in advanced.
Try using another usb cable. Maybe it's because of your usb cable. Because my phone is J2 PRIME SM G532G Variant I was FRP locked by google but then when I try to flash my stock rom via Odin it stucks and stops halfway of the process. So what I did is just changed my USB Cable and it worked for me. Hope it works for you too. There are a lot of options changing your usb cable. Or so I could analyze the real problem here include the logs of your Odin here when it stopped halfway. Copy your Log and paste it here.
It is difficult to explain what happened. It was quite irresponsible of me. I didn’t research it properly before wiping my phone. Now my zuk folders are not showing up on my pc, and I can't format it using TWRP. I was on a Custom Rom with Android 10 and went to another with Android 8.1, just to test it. I didn't like it and was about to install one with Android 9. When the problem happened.
I tried to install the drivers for the zuk z2 plus on the pc. My pc recognizes the phone only as a Media Player and does not even allow to create a folder.
I tried to use adb fastboot with qfill but it is not possible to activate usb debugging, so I cannot install a factory stock rom.
It seems I'm just too late?
First power the phone off by unplugging the battery. You can then short-circuit the test points on the mainboard of Z2 (Plus) before plugging USB cable, to enter Qualcomm EDL mode (9008), then you will be able to export data with QFIL's partition manager, or just flash the stock ROM.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This works for me. It works even if the "deep flash cable" (USB cable with its D+/GND pins short-circuited) can't work (because the detection of such deep flash cable is done by SBL in the PBL->SBL->aboot->Linux kernel boot chain).
However, use it at your own risk.
linuxnoobbbb said:
It seems I'm just too late?
First power the phone down by unplugging the battery. You can then short-circuit the test points on the mainboard of Z2 (Plus) before plugging USB cable, to enter Qualcomm EDL mode (9008), then you will be able to export data with QFIL's partition manager, or just flash the stock ROM.
This works for me. It works even if the "deep flash cable" (USB cable with its D+/GND pins short-circuited) can't work (because the detection of such deep flash cable is done by SBL in the PBL->SBL->aboot->Linux kernel boot chain).
However, use it at your own risk.
Click to expand...
Click to collapse
Ty for helping but i fixed my phone. The problem was the TWRP. My last custom rom downgraded my twrp. I used fastboot and was able to flash the latest twrp and voila. Problem solved. Never gonna try to install android 8 again, just gonna stay with 10 before i got myself in more problems.
EDIT: RESOLVED
I was in TWRP and decided to format-all (checked all the boxes).
Then, for some reason I decided to switch to the other side (Boot_B) and do the same there.
But the TWRP on that side was broken.
And now I'm stuck with no OS installed.
And my PC won't recognize my phone when I plug it in.
I've tried all three of my known-working cables and both of my computers.
Windows Device Manager doesn't see anything being plugged in.
It's not even coming up as an unrecognized device. Windows pretends like I haven't plugged anything in.
So, no ADB device, no Fastboot device, no Qualcomm device, no unrecognized device.... simply NOTHING.
Now the phone just boots to "The bootloader is unlocked" or to the broken (frozen) TWRP where even a USB-OTG mouse won't work.
With phone plugged in:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FINALLY got it to boot into fastboot mode!
First, power it all the way off.
Wait a minute then press & hold all three buttons.... Volume (+) & (-) and Power-button until you see fastboot.
And finally my computer sees it.
Cool, and I was able to do a "fastboot set-active a" and then reboot to the properly-working TWRP.
I should be good to go now!
EDIT:
Actually, I still can't get into MSM (nothing in device manager).
And ADB sideload or ROM install from TWRP ends in “kInstallDeviceOpenError”
EDIT 2:
I remembered that TWRP has a "reboot to EDL" option, so I used that and I'm now MSM'ing just fine.
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
EtherealRemnant said:
Don't use TWRP on these devices. Even on A11 it doesn't work right. ROM devs post a recovery that's meant to be used with their ROMs, use that.
Click to expand...
Click to collapse
I use TWRP for full ROM backup & restore purposes.
And it works fine as long as I don't try to get too fancy.