Related
I Had my FDascinate Phone Rooted and tried updating the phone with the OTA update, and of course it failed. and afterward i had problems with my messaging on the phone so i thought i would flash the DI01 Package like i did before but now ODIN gets to the point where it says Sbl.bin and right after that it fails and it shuts the phone off but now i cant even get the phone to boot up, all i get is a icon with a phone and computer with dots inbetween with a explanation point in a triangle.
Any help would be greatly thankful.
Well with a little messing around i got it to work. I tried with battery out and in nothing but i tried again with battery out and it worked.
Hi All,
OK, I am both new and stuck, I have read every page in the unlocking Atrix thread and the one click root thread but I still do not know what is wrong.
I started off by running the one click root listed here, the root went fine and seemed to work, so I proceeded to install ROM Manager but when I tried to back up my phone the process failed.
I googled the error and it turned out that I did not unlock the Boot Loader, so I followed all the instructions that explained how to do it and nothing worked.
Thinking something must have gone wrong I went back to the one click root tool and unrooted my phone, I checked and everything was working and the phone seemed fine.
So then I started down the longer process of unlocking/rooting here , following the steps to the letter and here is where I come unstuck.
I have a UK carrier free phone so after downloading and installing the RSD Lite software I used the SBF_Flash file but when I selected this file the “Start” button remained greyed out.
I researched this issue and found the international flash called intl-fix-try1.sbf, this file looked like it was going to work, the start button became clickable and the process looked ok.
Once I clicked start the flashing started and percentage done went straight up to 98% in a matter of seconds, then as per the instructions the phone reboots but starts to reboot fully, the process % resets and starts from zero going up in increments of 3%, by the time the process is at 65% my phone has fully booted and is sitting at the lock screen, if I leave it there the process will go up to 100% but the status will still say "in progress" until I swipe the lock screen and then it says complete.
I was doubtful that the root had worked but just to make sure I proceeded to move the phone into Fastboot mode and go through the OEM Unlock process but once I have typed in fastbook oem unlock and hit enter the command prompt just comes up with a message waiting for device to respond and nothing more.
Please help as I am really stuck, I followed your guide to rooting my Galaxy tab 10.1 and had it sorted in minutes, my ICS rom installed and everything backed up via ROM Manager so I am not a total dummy.
Any suggestions?
Kind Regards
Chris
when you tried to flash the sbf on rsd lite did you have the phone pluged into the pc and have it put into rsd lite mode
prolly not if you still seen the lock screen
turn phone off then turn on by holding power button down and volume down
when u see fastboot word on the atrix use volume down to scroll to rsd mode then hit volume up and proceed with rsd lite and the sbf
Here might explain it little more..
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
That is exactly what I did, I have just done it again now . . . .
I clicked start
The console/flash starts,
The phones screen goes black,
Then the Red Motorola M appears
The flash progress jumps to 98%
Console Status says something about USB Pass through/phone rebooting
Then reboots and the Red Motorola M appears again
Then progress carries on and goes up and at 16% by now the phone is now fully in its boot process and by 26% it is at the swipe screen
I have the phone in USB debug mode and the usb connection set to mass storage. Could I be using the wrong SBF file?
Thanks
I have tried that method as well as it is uses a different sbf file called zomgunocklite.sbf when I use that file I an error saying sec_exception: febe, 35, 35 I googled that and it came up with a similar issue but it did not help.
So since my first post I have been speaking to ltdanno360 on here, I just wanted to take the time out to say a MASSIVE THANK YOU.
He has taken me through getting my phone back to a usable state and then all the way through fixing up with the latest bits and pieces.
I have taken up a good few hours of his time and I am now a very, very happy Atrix owner.
It is people like ltdanno360 that make this forum and the internet community such an amazing place. Just imagine driving home from work one day and you car breaks down on the freeway, a stranger stops and spends two hours of his day fixing your car before sending you on your way.
Things like that do not happen often in the real world but people like Danno are great examples of what humanity often misses.
Big Thanks Bro
Awesome guy, awesome forum.
I was trying to get my VS980 back to lollipop from CloudyG2 2.2 so that I could put use CloudyG2 3.1. I was completely fine with using 2.2, but after using the phone for a few hours an error would pop up that said "unfortunately, com.android.phone has stopped working" and if I pushed "ok" on that, it would just pop up a second later and take me back to the home screen, until eventually I would just have to shut off my phone and restore from a backup, and them a few hours later the same thing would happen. SO I tried to get back to stock lollipop for CloudyG2 3.1, and I installed all the drivers and got into everything all hooked up to the ADK flash to stock program, and once the green bar on the phone started filling up, I hit "EXIT" on the Flash tool. After that, the phone stayed at 20% on the firmware update screen for a bit, until I eventually turned it off. Now, when I turn it back on it just shows the LG logo for a few seconds and then goes straight to the firmware update screen. Plugging it in from there just has it try to install the MTP driver for a bit until it fails and then it doesnt get recognized by my computer. trying to do the factory reset button combo brings up the white reset screen, but hitting yes just takes me back to the firmware update screen. Sorry for the long post, but I just wanted to be REALLY specifc with my problem.
You know what the funny thing is, though? I never even wanted to root my phone or do any of this stuff. I just had to find a way to get my phone to charge faster, not use so much battery, and not heat up so much like it had been doing since I updated to lollipop.
Thanks in advance for any solutions you have
runninsavvy said:
I was trying to get my VS980 back to lollipop from CloudyG2 2.2 so that I could put use CloudyG2 3.1. I was completely fine with using 2.2, but after using the phone for a few hours an error would pop up that said "unfortunately, com.android.phone has stopped working" and if I pushed "ok" on that, it would just pop up a second later and take me back to the home screen, until eventually I would just have to shut off my phone and restore from a backup, and them a few hours later the same thing would happen. SO I tried to get back to stock lollipop for CloudyG2 3.1, and I installed all the drivers and got into everything all hooked up to the ADK flash to stock program, and once the green bar on the phone started filling up, I hit "EXIT" on the Flash tool. After that, the phone stayed at 20% on the firmware update screen for a bit, until I eventually turned it off. Now, when I turn it back on it just shows the LG logo for a few seconds and then goes straight to the firmware update screen. Plugging it in from there just has it try to install the MTP driver for a bit until it fails and then it doesnt get recognized by my computer. trying to do the factory reset button combo brings up the white reset screen, but hitting yes just takes me back to the firmware update screen. Sorry for the long post, but I just wanted to be REALLY specifc with my problem.
You know what the funny thing is, though? I never even wanted to root my phone or do any of this stuff. I just had to find a way to get my phone to charge faster, not use so much battery, and not heat up so much like it had been doing since I updated to lollipop.
Thanks in advance for any solutions you have
Click to expand...
Click to collapse
Nevermind, I just didn't have the most up-to-date Verizon drivers installed. Boy, do I feel stupid
I have a TMobile/MetroPCS GS4 model SGH-M919N that got stuck in a boot loop last week. I was finally able to find working firmware last night and used Odin to flash. Once it got to PASS my phone automatically rebooted with the blue recovery boot text in the top left, but then it just went back into a boot loop. I tried all other firmwares and none of them got to 100% so now I don't know what else I can do.
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
alesu69 said:
I have the same issue on a GT-i9505. I was using my phone this evening when it randomly rebooted and just keep rebooting until I removed my battery. After that, it was dead . Flashing stock firmwares like shooting a minigun and nothing works. Smells like a hard brick?
Click to expand...
Click to collapse
Have you tried replacing the battery? I figured I would try that but I havent gotten around to it yet
Not yet, i have no spare battery. Looks like when i plug the charger my phone just vibrates, like it's rebooting, and it's not showing anything. I found a similar issue here: http://forum.xda-developers.com/showthread.php?t=2532447
Looks like one guy did solve his problem.
*need to mention that by dead I mean it shows the "Samsung Galaxy S4 GT-I9505" logo and also shows "RECOVERY BOOTING", even though I didn't enter in recovery mode. Looks like now it doesn't shows anymore "RECOVERY BOOTING", but still, it doesn't boot. I was able to flash firmwares via odin and kies, but still no luck.
LE: It start booting by.. magic, i got to samsung boot logo, but that's all, crashed again.
After flash with Odin, immediately boot into recovery, perform a factory wipe, and reboot.
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
alesu69 said:
The problem is it doesn't boot into recovery.
LE: I managed to flash twrp via odin and boot into recovery, but i have an error:
"Unable to mount /data"
Any ideas?
LE2: Everything is useless, i managed to flash the rom, manage to boot into the rom, but then it will still reboot (which it did). Next step will be maybe to disassemble and clean all contacts.
Click to expand...
Click to collapse
How did you manage to get into recovery?
harary said:
How did you manage to get into recovery?
Click to expand...
Click to collapse
Yes, but if I leave my phone in recovery (stock or custom), it just either freezes, either reboots, even though i don't do anything, just let it idle.
I can't manage to boot into the ROM 'cause eventually it will reboot. I couldn't finish the setup wizard.
OK so I don't know if this helps, but I managed to at least get past the "blue recovery boot" part. When the phone vibrated I let go of the power while still holding home + vol up, and I managed to get to the android guy with a blue progress bar below him. My phone shut off as the progress bar got 80-90% but now I know it's not impossible to start recovery.
Well, nothing works. After flashing pit file, an 4.4.2 odin prerooted image from here, cf auto root and then twrp, it will still randomly reboot. I manage to get past the boot logo into setup wizard, but phone just freezes after a couple of minutes, can't finish the setup wizard. Also, if i idle in twrp it will reboot sooner or later, tested already.I left my phone idling in twrp just to recharge my battery.
At least i have no more "unable to mount /data" errors.
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Operation Ivy said:
I finally got it to work, all I had to do is keep flashing twrp and stock firmware back and forth. But it is just one problem after another with this thing, the problem now is every 5 minutes it will freeze and restart, also it tells me there is no sim even though it worked the first time i put it back in.
Click to expand...
Click to collapse
What do you mean with back and forth?
harary said:
What do you mean with back and forth?
Click to expand...
Click to collapse
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend who repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
alesu69 said:
It means he flahsed and reflashed many times until he got lucky and it worked. That's what happened to me also. But i have the same issue, phone reboots or freezez after a couple of minutes, even though everything else is installed properly.
Dude, we have the same issue. Btw, is this happening to you too? Like, now and then when the phone freezes, that the screen is turning to a bright yellowish green?
I know a friend which repairs phone hardwares for a living, i gave it to him, i'll let you know how this went.
Click to expand...
Click to collapse
I got several times into Recovery Mode now, flashed several ROMs. I had no issues with freezing, especially not in TWRP Recovery Mode. But sometimes if i am trying to go into Recovery Mode or i just want to start ROMs, the screen turns into yellow behind the Samsung logo. If i dont take out the battery this wents into a complete white, but nothing happens.
Yes please tell if you got some news..
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Joashrox said:
guys its not hard bricked its a problem wiht your power button
my friend had the same issue and then i killed the battery by letting it keeep bootlooping
then plugged it in and let it charge to around 10% and booted it
just try to press the power button slowly
Click to expand...
Click to collapse
But it is sure that the power button is working because i get this blue "recovery booting". Or am i wrong?
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
alesu69 said:
So.... bad news, the guy whom i gave the phone to said that it's a short on the motherboard and there's nothing he can't do other than changing the motherboard. If you guys found another solution and that guy is mistaking, let me know.
Click to expand...
Click to collapse
Replace power button to new one. I have the same problems with s3 and this works. Try it.
Sent from my GT-I9300 using XDA-Developers mobile app
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
alesu69 said:
My phone is dead, it's not even charging anymore. The guy whom I give it to said it's a short on the motherboard. You guys managed to solve something with your phones? Or still a dead end?
Click to expand...
Click to collapse
If You can't charge phone... Yup, motherboard is died. If You plug the charger and see something this have to be button but if You plug charger and don't see anything this is motherboard.
Hi, so, I got this phone from a friend, and he told me that the phone was working prorperly, but after someone factory resetted it, he wasn't able to set it up. Constant force close pop-ups where showing up while setting it up, and you weren't able to accept terms and conditions (button grayed out). Also, one thing I noticed. The phone got into "Factory Mode". Idk what that is, but it wouldn't let me to enable wifi or bluetooth. That little Factory mode thingy got me really confused. Also, I wanted to boot into recovery mode, and I wasn't able to do so. After turning the phone off, and doing the key combo to boot into recovery, the phone rebooted itself (very showrtly after doing the startup vibration) and after that, it seemd to get into recovery, but it stayed at the android logo with an exclamation sign and after 3 seconds it rebooted itself to system.
After that I said, "well, last thing to try is flashing stock rom again". And I did so. Using the Frija software to download the latest version of android for this phone (and using the corect CSC for this phone (CTI)). I used odin 3.12.7 (wich I knew it works because of previously using it with other phones) to flash the stock rom again. I made sure that only Auto-reboot and F.reset time were checked, and started flashing. After it finished, it got to the samsung logo, but got stuck there. Nothing happened (I left the phone there for like 30 min). I decided to hard-reboot the phone and try to factory-reset it, but after shutting it down, it started to be really hard to make the phone turn on. I had to unplug the battery and wait like 10 mins to try again, and I still wasnt able to boot into recovery mode. It just got stuck at the "Galaxy Core 2" logo.
After that first boot, the phone never got passed the "Galaxy Core 2" logo. Just stuck there. After that, things just begun to get worse. It was also hard to get the phone to get into download mode, most of the time it just stayed at a blackscreen (im not shure if the phone ever turned on, but it never vibrated) and did nothing. I decided to try other versions of odin. Tried with 3.09 and 3.04. Nothing, and after every flash, it got harder and harder to make the phone boot.
At this point, I can hardly get the phone into download mode, and if I do so, sometimes I get the odin complete write operation failed error, wich the only way that I've found to solve it is to reboot again the phone into download mode.
I know that the battery is working, I have another core 2 (same exact model) and battery is ok. At this moment I don't know what else to do. Please, help me to get this brick of a phone back to working conditions, I dont want my friend to buy a new phone just to use it to recive calls and charge it.
Some extra notes:
As i've read, sometimes this can be caused by the replacement of the digitizer/screen. This phone seems to have one or both of them replaced, since I can see glue residues on the corners of the glass, where it touches with the plastic frame.
If there is anything hardware related thing to try, I can try to open the phone. I have some experience doing so.
EDIT: As I continued reading through this forum, I found out that some people had luck with Odin3_v3.13.1_3B_PatcheD, so I decided to try it out and see. Still, nothing changed. As today, I can only use this phone to charge the battery (it dosent actually show the percentage, only the battery icon with a loading icon inside) and boot into download mode
Although, I have to say that after flashing the stock rom with that version of odin made the phone not that hard to start in download mode. I think that it could be something that got corrupted on the eMMC module and it has to repartition it all again...? Does anyone know how to do so?
Regards
Well, tried almost everithing I know. Downloaded rom again with binary nature, tried with odin version 3.12.7, 3.13.1_3b patched and 3.13.3, but nothing. Extracted the PIT file from the CSC file, did repartition, NAND wipe, and nothing changed. I have to say that its certaily easier to get the phone in download mode, but thats almost it. One thing to note, when i select the NAND wipe, it dosent seems to do anything. I mean, in odin Log screen some things appear related to NAND wiping and such, but its really fast and there are only 2 or 3 lines dedicated to that. Is that OK?
Anyway, please, any recoomendation or thing to try would be great, since this phone is now trash, it dosent matters if it starts to get worse, or even unusable (more than it is rn).
Regards