Maybe I am asking my questions in the wrong forum so I will ask here.
I have flashed the phone sm-891a and as you can see in the photo i posted that it is sw rev 8.
It boots to the blue att logo that looks like a ball and restarts.
Any help is welcome
Can I install twrp in odin and maybe it will help?
Still no luck. I am able to flash ot but it wont load up. Nothing past the att logo
Finally I see my problem.
FRP MODE is on.
I need a combination file for binary 6
Please.
Related
I was trying to flash my phone (AT&T SGS3) back to stock today using this thread
http://forum.xda-developers.com/showthread.php?t=1739426
While I was downloading, I accidentally kicked the usb cable out of the phone.
I immediately pulled the battery and restarted the process.
Odin said it succeeded but when I boot I get stuck on a screen where it just says samsung. Like the first screen you see on boot but it happens a second time after the galaxy s logo and the at&t logo.
I don't know how to fix this. Can someone please help?
Also I was going to try the not rooted stock roms from this thread.
http://forum.xda-developers.com/showthread.php?t=1737848
But the downloads don't seem to be working. Anyone know where I can download the stock roms?
dmobbjr said:
I was trying to flash my phone (AT&T SGS3) back to stock today using this thread
http://forum.xda-developers.com/showthread.php?t=1739426
While I was downloading, I accidentally kicked the usb cable out of the phone.
I immediately pulled the battery and restarted the process.
Odin said it succeeded but when I boot I get stuck on a screen where it just says samsung. Like the first screen you see on boot but it happens a second time after the galaxy s logo and the at&t logo.
I don't know how to fix this. Can someone please help?
Also I was going to try the not rooted stock roms from this thread.
http://forum.xda-developers.com/showthread.php?t=1737848
But the downloads don't seem to be working. Anyone know where I can download the stock roms?
Click to expand...
Click to collapse
'
Maybe try going into recovery mode and do a factory wipe there.
That worked. Thank you, you just saved me in a big way
Glad it worked. Happened to me too. From what I learned when changing ROM types tw-> aosp you need to wipe data.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Hello! this is my first thread on this forum, which im making because I ran out of options, and don't know what to do...
It looked like my Galaxy S4 mini (GT-I9190) died last weekend (april 29) I was watching a video on youtube and suddendly it ''ran out of memory'' (the screen froze) and it turned completely black, the audio was still playing and I decided to force it to shut down (holding the power buttom)
The audio stopped, and I tried to boot it back but it wouldn't answer at all, so I removed the battery, put it back on, still nothing after many attempts (also trying download mode and recovery mode, none of them worked).
So I decided to plug it into the computer, and that's how I found it wasn't ''completely dead''
My computer detected the device as ''QHSUSB_DLOAD'' which was a good sign, meaning I wouldn't have to put my s4 mini to sleep forever.
So after some research, coming across people using 300 kohm resistors to force a bricked phone to dl mode, people using weird hardwares, Jtags and whatnot (all of these methods involved extra hardware) I found this:
http://forum.xda-developers.com/showthread.php?t=2625628 and this http://forum.xda-developers.com/showthread.php?t=2660566
The .img in the scard method, links up there.
So I gave it a try and guess what, it actually worked, my phone actually responded after placing back the sdcard and the battery, I didn't even had to press the power buttom.
My phone booted, but displaying this screen:
Boot recovery mode
Check boot partitions
Copy from T-Flash
Boot recovery. .
Write 139008 sectors. .
Flash write failure
Ddi : mmc_read dailed
ODIN MODE
Product name: GT-I9190
Current binary: Samsung official
System Status: Custom
Knox kernel lock: 0x0
Know warranty void: 0x1
csb-config-lsb: 0x30
Bootloader Rp swrev: 2
Write protection: Enabled
Click to expand...
Click to collapse
after this point, It wouldn't go further
I tried download mode at least 10 times, I't didn't work, the phone booted back to that screen again.
So I switched the vol- for vol+ to see what happen (I was doing download mode: power vol- and home)
And It worked, my phone went to the ''Galaxy S4 mini GT-I9190'' Screen, the first screen you see when it actually boots.
but after this point, It bootlooped turning off and back on to this screen and so.
when the phone turned off, I tried download mode once again and IT FINALLY WORKED.
At this point I believed that everything was over, I would connect it into odin a flash a stock firmware.
But it just started... (here comes the interesting part)
I tried to flash a stock firmware with odin, yeah, the blue progress bar and everything, my phone rebooted, but nothing, the same bootloop again. Here comes an important question: Do I need to flash a specific region firmware? or any region should work? First, I flashed an argentina region firmware (ARO was the code), results: Bootloop
After that, I tried the Russian firmware (I dont know if the region of my phone is Rusia, but I believe so because after doing a factory reset, the default language was russian, please answer this as well) and BOOTLOOP again...
So basically, The main problem is a bootloop, but I dont know what is causing this
After this point, I'm stuck, and not knowing what to try...
I'm looking for answers, what should I do? what can I try?
If you can answer any of these questions please do it...
Do I need a specific region firmware? (I already tried argentina(ARO), and Rusia (SR)) oh yeah, I tried Rusia SR, should I try XE? XE seems to be a multi-region format (?) I don't have a clue actually... I really need the opinion of someone who knows about this
If the default language when doing a factory reset is russian, this means my phone's region is Rusia?
Is there a way to know the region of my phone, when hard bricked? I dont have the box, manuals, nothing...
What was that weird screen my phoned displayed after booting with the .img sdcard? (read the quotes higher in this post)
Is there a posibility that the bootloader is corrupted, and is causing the bootloop?
I want to try everything before a JTAG service, what are these hardwares? What do they do?
Oh here is an important question:
I read that the baseband of unbrick.img has to match the baseband of my phone... is this completely true? if so, what can I do? where can I get a specific baseband .img file, and what can I do since I already used another .img (I dont know if the baseband was the same) and im already stuck on a bootloop? If a use a correct baseband .img file will the phone stop the bootloop?
Im looking forward to see your posts...
If you need any aditional information feel free to ask...
If you don't have a clue, just like me, please send this thread link to someone who could help...
Thanks in advance!
EDIT: Also recovery mode NOT working, when trying to enter this mode, the galaxy s4 mini gti9190 screen displays ''entering recovery mode'' on the upper left screen, and after that it turns off and the bootloop continues
Still with the same problem and i cannot flash any Recovery like CWM or TWRP, cuz it does Pit File partition table error
Try a NAND-Erase, I dont suggest it but it could fix your problem. Goodluck
As mentioned in the title of the thread, my Zenfone 2 is stuck at the Asus logo screen. I tried installing an OTA update with the phone being rooted.
To solve this initial problem, i flashed Temp CWM with the help of my computer. I successfully got to the recovery menu and attempted to wipe all of the phone's data. I don't know if it did or not, because it got stuck on this process for 10 minutes, apparently not doing anything. So I did something that may have completely f****d the phone. I restarted it during the 'wipe'.
So here came the second problem: I cannot access the Fastboot screen anymore, therefore I cannot flash anything, and it still won't open. :crying:
Desperately, I even tried using the Asus Flash Tool to flash its original firmware, while at the logo screen. It won't move.
So, in case someone actually knows how to solve this, or there's someone with the same problem of mine alongside which I can mourn my dead phone, I'll leave this thread here. I also have an additional question: is the warranty valid in this situation?
Thank you.
Saphiron122 said:
As mentioned in the title of the thread, my Zenfone 2 is stuck at the Asus logo screen. I tried installing an OTA update with the phone being rooted.
To solve this initial problem, i flashed Temp CWM with the help of my computer. I successfully got to the recovery menu and attempted to wipe all of the phone's data. I don't know if it did or not, because it got stuck on this process for 10 minutes, apparently not doing anything. So I did something that may have completely f****d the phone. I restarted it during the 'wipe'.
So here came the second problem: I cannot access the Fastboot screen anymore, therefore I cannot flash anything, and it still won't open. :crying:
Desperately, I even tried using the Asus Flash Tool to flash its original firmware, while at the logo screen. It won't move.
So, in case someone actually knows how to solve this, or there's someone with the same problem of mine alongside which I can mourn my dead phone, I'll leave this thread here. I also have an additional question: is the warranty valid in this situation?
Thank you.
Click to expand...
Click to collapse
Try using xFSTK. Search for it on the xda, read the whole thread before proceeding.
Note: If the moorefield device disconnects, press vol down and power at the same time
Hello and sorry if this is the wrong category...
It's my first time making a thread on xda.
I've been looking for an answer for the past 2 hours, but I still have a bricked phone... As the title says, I can't enter the recovery mode anymore. I tried to do a factory reset (when I could enter the recovery mode) and the phone got stuck at erasing. Now I can't enter the recovery mode anymore. I downloaded a new firmware from sammobile for the SM-G925F. The firmware works since I used it on an other phone and everything worked just fine. The problem is, when I open Odin and add the .tar file to AP, it gets stuck at nand write and sometimes on boot.img. The phone isn't showing that it's downloading anything (it has no progress bar). At this point I have no idea what to do...
Some extra info that could be helpful:
The phone was bootlooping when I got to fix it;
I work in a kind of phone repair store where customers bring their phones for hardware and software repair. I do the software;
I've installed new firmwares on multiple phones and I never had something like this... Normally some time with google and xda could help me to find a working way to fix the problem, but as I said... I've been looking for 2 hours and the problem is still here;
I'm not a pro with Android and phones. I just like to learn new things and I'm still learning.
Could it be a hardware problem?
Can you show me your phone's download mode image to see where could be the problem?
Also, make sure you are flashing latest firmware, if you are downgrading it - than you will get such boot errors.
*Update*
I found out what was wrong. The eMMC chip was broken.
hi guys please help here im so stuck..
The phone keeps rebooting to downloading mode and stays in downloading mode ! each time i try recovery ive wiped cache also did factory reset from there when it reloads it goes straight to downloading again.
the weird part is in downloading theres nothing written in top left.
the phone does not show samsung logo in reboot and goes to odin mode.
heres what it looks like: phone is samsung s9 sm-g960w snapdragon
my images are jpeg not loading here..
i have flashed it with odin 3.12
All latest BL,AP,CP and CSC files os10 android 10 version from sammobile
odin showed pass and success in like 5 seconds and everything seemed normal and good BUT phone does not load back and no samsung logo and automaticly goes to odin mode no matter what i try.
Can a pro help please.
Bunzei said:
hi guys please help here im so stuck..
The phone keeps rebooting to downloading mode and stays in downloading mode ! each time i try recovery ive wiped cache also did factory reset from there when it reloads it goes straight to downloading again.
the weird part is in downloading theres nothing written in top left.
the phone does not show samsung logo in reboot and goes to odin mode.
heres what it looks like: phone is samsung s9 sm-g960w snapdragon
my images are jpeg not loading here..
i have flashed it with odin 3.12
All latest BL,AP,CP and CSC files os10 android 10 version from sammobile
odin showed pass and success in like 5 seconds and everything seemed normal and good BUT phone does not load back and no samsung logo and automaticly goes to odin mode no matter what i try.
Can a pro help please.
Click to expand...
Click to collapse
theres only a few things that you actually can do. a: fresh download of firmware to reflash b: try a different cable (yes, i know youre not getting a failure message, just do it anyways) c: different computer d: new download of Odin. Not much else the average layperson can do without very specific tools. I had something similar with my desktop and did it on my laptop and it worked just fine. I didnt investigate any further as to why because, well... lazy but i used the came cable on both computers, so my issue wasnt the cable. Anyways, those are really your only options. Good luck! Oh, where did you get your firmware from? Some people also are getting janky AF stuff from weird places. sammobile.com/firmwares is pretty much the only place i trust. Samfirm is an awesome tool for downloadinf the firmware (literally) 5x faster than from sammobile directly.