I got this problem with my phone, I got it unlocked and rooted and I flashed a rom and it worked. I was rechartging my phone and restarting it everytime it got to 100% to charge it all the way so that I can do a calibrate. Then my phone got into some loop, it would start, flash something once, twice and then start in recovery and It does that all the time when I reboot? What is wrong? and how can fix it?
S4 or s3? Did you flash the boot.IMG? Have you set up android SDK and used adb or fastboot before? In order for you to fix this. Like me, you gotta learn all you can about these kind of things so you can better understand what the problem really is. I learned my lesson. Never mess with your phone without learning it all.
Sent from my HTC One S using xda app-developers app
Related
This is not my phone but my friend's phone. I'm Captivate owner so I'm familiar with the SGS line and I've never heard of a issue like this.
This is a stock phone. No root and no custom roms. Completely stock. We tried to see if we could put the phone into download most via the key combo but no luck. He is going to bring it over later today to try the JIG which is a common thing to do for soft bricks in the Captivate forum.
Anyone else seen a problem like this and have any suggestions? Let me know. Thanks!
**UPDATE**
Now it will Randomly boot up. We tried a master reset but then it goes back into a boot loop. Then sometimes it will randomly boot but is not running well.
Super easy to fix...have you got it out the loop yet
Sent from my SGH-T959V using XDA Premium App
de1packers is right super easy to fix! if u havent fixed it yet im sure he can give a great explanation. oh yeah check your private de1packers
It is still looping... whats the fix?
no suggestions?
Do you have access to a computer..do a search for odin..DL it them get an odexd rom and flash it and you should be back to normal...enjoy
Sent from my SGH-T959V using XDA Premium App
Hey guys I didn't find any useful posts for this device with the same problem.So I started a new thread. Well I was googling and texting and all of a sudden my phone reboots. I thought well it's nothing and put my phone down, 15 minutes later I was hoping for it to be on and ready to be used and all I saw was Dual Core Technology. I rebooted it countless times to see if it'll come alive and no luck. I did root the phone awhile back and never had any problems with it until now.
I did try to go to recovery and all it shows is the android with an exclamation mark. I can get into fast boot and everything but I am a noob with fast boot so I don't exactly know how to wipe the phone by using that.
So I am counting on you guys to help me out. I don't even know if my phone is charging atm I just have it plugged into my power port and all it shows is Dual Core Technology and the battery is dead for letting it sit on that screen for about 30 minutes. I hope you guys can help.
Thanks,
Mike
Have you tried to fxz back to stock using RSD Lite? If not make sure your battery is charged before doing so. That should do the trick. If you have a back up try the recovery. When the Android with the exclamation comes up hit both the up and down volume keys at the same time.
Sent from my MB865 using xda app-developers app
MaTrixJ said:
Hey guys I didn't find any useful posts for this device with the same problem.So I started a new thread. Well I was googling and texting and all of a sudden my phone reboots. I thought well it's nothing and put my phone down, 15 minutes later I was hoping for it to be on and ready to be used and all I saw was Dual Core Technology. I rebooted it countless times to see if it'll come alive and no luck. I did root the phone awhile back and never had any problems with it until now.
I did try to go to recovery and all it shows is the android with an exclamation mark. I can get into fast boot and everything but I am a noob with fast boot so I don't exactly know how to wipe the phone by using that.
So I am counting on you guys to help me out. I don't even know if my phone is charging atm I just have it plugged into my power port and all it shows is Dual Core Technology and the battery is dead for letting it sit on that screen for about 30 minutes. I hope you guys can help.
Thanks,
Mike
Click to expand...
Click to collapse
Couple things we need to know mate. What firmware are you running? 2.3.5? 2.3.6? Or ICS?
These all play into how you are going fix your phone. And frankly your stock recovery is not going to do you any good with this issue. You WILL have to FXZ back, UNLESS you have a backup made in a different recovery system, IE: bootstrap, or bootmenu. Once again all dependent on what firmware you are on. If you can answer those questions, we can help you with the right procedure.
A good thread to start with is this one: Noobs guide to Android and the Atrix 2
It will give you all the info you need on the FXZ and fastboot.
More info and we can fix ya! :highfive:
EDIT: just saw your battery issue. Pull your battery until you are ready to flash in Fasboot. You need to conserve. How much battery do you think you have? Or is it dead? Flashing in FB and having your phone die due to low battery is a SURE way to hard brick your A2.
Fall of Enosis said:
Couple things we need to know mate. What firmware are you running? 2.3.5? 2.3.6? Or ICS?
I am running 2.3.6 stock
These all play into how you are going fix your phone. And frankly your stock recovery is not going to do you any good with this issue. You WILL have to FXZ back, UNLESS you have a backup made in a different recovery system, IE: bootstrap, or bootmenu. Once again all dependent on what firmware you are on. If you can answer those questions, we can help you with the right procedure.
A good thread to start with is this one: Noobs guide to Android and the Atrix 2
It will give you all the info you need on the FXZ and fastboot.
More info and we can fix ya! :highfive:
EDIT: just saw your battery issue. Pull your battery until you are ready to flash in Fasboot. You need to conserve. How much battery do you think you have? Or is it dead? Flashing in FB and having your phone die due to low battery is a SURE way to hard brick your A2
I have a way to charge the battery up without the phone so that's fine ill let it charge tonight and do it in the morning..
Click to expand...
Click to collapse
Axis_Drummer said:
Have you tried to fxz back to stock using RSD Lite? If not make sure your battery is charged before doing so. That should do the trick. If you have a back up try the recovery. When the Android with the exclamation comes up hit both the up and down volume keys at the same time.
I'll definatly try holding both volume keys at the same time next time, thanks!
Sent from my MB865 using xda app-developers app
Click to expand...
Click to collapse
Oh and do you guys know what exactly caused this to happen?
Mike
It could've been caused by a number of things. The A2 is an unpredictable phone. Somethings that happen to one person may not happen to others. From my experience.
Did you make any changes to any system files or anything of the such? I see you was rooted, but did you have a custom ROM or custom recovery? I'm assuming since you tried to get to recovery and got the android on its back, that that you didn't have a custom recovery installed..
If someone knows the exact reason this happened, let us know. This is twice I've come across someone with this problem.
FXZ should work for sure though. All is well.
Sent from my MB865 using xda app-developers app
No I don't think I modified anything except rooting and installing cheesecake but I didn't use it. I don't remember having a recovery installed either.
What I did was use android recovery by pushing vol up and down and I reset it. Works fine now I lost root though so I'm going to reinstall it and reset my server on cheesecake because I can't add a motoblur account right now then uninstall it again Lol.
I really appreciate the help. I almost hate the A2. 2 phones 2 unique problems, like you said some people experience a issue that no one else has.
Sent from my MB865 using xda app-developers app
I install slimroms 4.2.1 stable rom and went to reboot phone and now i cant boot it up. I tried getting into recovery or download mod by holding Home power and volume up or down but nothing happens. The screen just remains off. Is there a way around this or is it done?
Remove then reinstall the battery. Then try again. Cal you get into download mode?
Sent from my Nexus 7 using Tapatalk 2
search for how to fix a hard brick you mightve flashed a rom for a different carrier dude, something like that. if you cant boot into odin than its probably hard bricked. try leaving it for awhile and go back to it later, sometimes technology is weird like that. i doubt it though..
sob372 said:
search for how to fix a hard brick you mightve flashed a rom for a different carrier dude, something like that. if you cant boot into odin than its probably hard bricked. try leaving it for awhile and go back to it later, sometimes technology is weird like that. i doubt it though..
Click to expand...
Click to collapse
Well I'll be honest I looked at SD card and I flashed and i9300 rom on it. I've tried leaving battery and stuff but the phone just won't power on. Screen just remains off. When I plug into computer with battery out a red light comes on and phone tried to install a driver but doesn't install and Odin doesn't see. I have Samsung drivers installed so i don't know what it's trying to install. Am I screwed? Throw phone away? Lol
Google jtag. I don't think there's another way to get your phone fixed. Flashing an international rom is the surest way to hard brick.
Sent from my SCH-I535 using xda app-developers app
bobAbooE said:
Google jtag. I don't think there's another way to get your phone fixed. Flashing an international rom is the surest way to hard brick.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I head jtag doesn't work anymore after 2.3 android or maybe it was the jig I was reading about.
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Hopefully someone will have another way to fix it but I'm pretty sure jtag is the only way.
Sent from my SCH-I535 using xda app-developers app
I looked around and didn't see a solution to my problem. I might have missed it because I'm kind of panicked right now.
My HOXL was dying really fast. Within a few hours, it falls from 80% to 0%. I wanted to factory reset because I heard that it helps the battery life.
So I followed the process I always have (I'm unlocked, rooted, and had pacman's evita ROM installed) and did a factory reset, wiped cache and dalvik cache. Then I re-flashed pacman's ROM and the gapps. When I rebooted though, it went to the HTC screen and in a few seconds it just went black. I think it might have still been on or something, but nothing was happening for like 30 minutes. I tried it over and over again, flashing new ROMs and kernels, but now all that's happening is that it's stuck on that very first HTC screen.
I downloaded the latest JB RUU for evita to try it out. But if I can't get past that first screen, is there a way to connect it? I can still get into TWRP's recovery. My HBoot is 1.09. I'm really starting to feel nervous about having to buy a new phone, yet I feel like there should be a way to fix this. Could flashing the stock kernel be all I need? I tried to download from Viper's hub, but the download just stops at 99% and doesn't finish.
Please, I would really, really appreciate any help!
I would run the 3.18 RUU (which you can do in fastboot).
Try a complete wipe: Factory reset, system, cache and dalvik cache in twrp or if it is not wiping correctly due to twrp version " 2.3......" is best fro our phones, try downloading and installing twrp again or use adb commands to wipe and flash rom again.
I've tried a complete wipe, but I just noticed that my TWRP version is 2.2.0. I tried the wipe like five or more times and it didn't work. My PC isn't reading the HOXL in the adb command window. I rooted a Sero Pro 7 this way, so I think I should have the drivers installed for it... I'm going to try installing the HTC Sync drivers and seeing if I can send adb commands to my HOXL. If this doesn't work, I'm going to try the 3.18 RUU. I heard that some people have bricked their HOXL completely doing this, but I didn't change my SuperCID and s-on (?), so would I be fine? Or would it be safer to just use the latest ICS one (RUU_EVITA_UL_ICS_40_S_Cingular_US_2.20.502.7_Radio _0.19as.32.09.11_2_10.105.32.25L_release_271865_si gned.exe)?
So you have no way to flash boot image separately? I would definitely try to get device recognition so adb can be used before running ruu.
Sent from my HTC One X using xda premium
Yeah, I went through the noob way of unlocking and rooting this phone, so there was no need to use adb commands. I would have liked to try that first before running RUU, but I just want to have a working phone again, even if I have to go through the whole process of unlocking and rooting.
Sent from my Nexus 7 using XDA Premium HD app
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Venomtester said:
I would still try to get a good adb environment. Sometimes panic is not a good thing. Just be careful and make sure you get the proper ruu and do not let the battery die while running it. Let me know if it works.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
This is what I'm worried about:
SERooted wrote: Note to OP: You really should add to the 1st post that it is not wise to flash the 3.18 firmware over super cid and s-on.. its not a good thing for most people to have a qhsb_dload turn their phone into a paper weight before finding out that they shouldn't have used that file to begin with. i had to find out the hard way. i would have flashed the ics firmware on my phone but decided to go with the big JB only to find out that it turns it into a paperweight. I understand this is no fault but my own, however this would greatly help people when choosing which ruu to run.
http://forum.xda-developers.com/showthread.php?t=2191477
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Venomtester said:
I know what you mean lol. I would only do that as a last resort. I would try and get adb working since the phone is not bricked. It just seems to have no Rom or boot image. Have you tried one with an aroma installer?
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Huh...I just tried flashing the UrDroid ROM because of its aroma installer, but it didn't happen in recovery, like I thought it would. It said it was successful, so I rebooted the system. It got past the initial screen with an AT&T boot img and htc one img. Now I'll have to see if it actually loads past this.
EDIT: It worked! I'm going to have to try to see if I can load boot img some other way than just an aroma installer.
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Venomtester said:
You can use Flash GUI from the market to install boot images or get Goo Manager to install a 2.3..... Version of twrp. That may solve your problems.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Second Flash GUI....works like a charm
Hi everyone
I bought an Android phone in used from a friend. It is working fine but don't know there is something wrong. Some games run with lagging and sometimes it doesn't load at all. I wanted to know is there any way to know whether the phone has ever been rooted in past or not? I mean if it ever got rooted in past and then un-rooted. Is there any way to know that?
I am asking this because previously i had another Android phone, and i rooted it and had some problems with phone. When viber was running and call came, the phone got stuck (held) and i had to restart it else there was no solution. Later i un-root it.
That is why i am asking this.
My current phone is Huawei G610-u20.
awaisagha said:
Hi everyone
I bought an Android phone in used from a friend. It is working fine but don't know there is something wrong. Some games run with lagging and sometimes it doesn't load at all. I wanted to know is there any way to know whether the phone has ever been rooted in past or not? I mean if it ever got rooted in past and then un-rooted. Is there any way to know that?
I am asking this because previously i had another Android phone, and i rooted it and had some problems with phone. When viber was running and call came, the phone got stuck (held) and i had to restart it else there was no solution. Later i un-root it.
That is why i am asking this.
My current phone is Huawei G610-u20.
Click to expand...
Click to collapse
You cant.
Hey just flash stock firmware... And forget about past of phone...
Sent from my GT-S7582 using XDA Premium 4 mobile app
Killwish said:
Hey just flash stock firmware... And forget about past of phone...
Sent from my GT-S7582 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
How to flash stock firmware? i just did the hard reset by pressing the volume up button and power button and then cleaning the cache and then deleting all user data and then restarting the device. This is all what i did. Is there anything else to do? or else method.
you can type "adb shell" in teminal or cmd,and than type "su" if the user from $ turn to # it rooted if not it un-root