I was on the phone earlier for a fair bit, when I hung up I noticed the battery at 4%. Got home little bit later and when I checked my phone again it was off, I hit the power button so it began to power on, and I them plugged it into AC charger right away while booting up. A couple of minutes later and I noticed it was still on the "One" boot screen (on a sense ROM at the moment, ViperXL 2.1.1). Tried holding power to reboot and it did the same thing.
Figured I leave it plugged in for a little bit, maybe battery was just really low. After about 30 minutes or so it was plugged in, still on the same screen (couldn't power it off it would just reboot). Tried to reboot again, and got stuck on the same screen. This time however I noticed the phone was quite hot, though it seems to be cooling down slightly since I've unplugged it, but not 100% sure.
What could be the issue/any ideas? I haven't flashed anything in over a week, last being ViperXL 2.1.1 and BeastMode Kernel 3.0. First time dealing with potential boot issues as I am always very careful when flashing. Any help is appreciated!
Try reading threads before you post. You may have read a thread that said don't post questions in General. There is a Q&A forum for this.
Anyways, try erasing the caches and rebooting.
Myrder said:
Try reading threads before you post. You may have read a thread that said don't post questions in General. There is a Q&A forum for this.
Anyways, try erasing the caches and rebooting.
Click to expand...
Click to collapse
Yeah I was thinking this might not be the right place but wasn't totally sure, I apologize.
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure. After a straight system reboot from recovery did not work, I tried wiping cache's as you said and it booted fine! Much thanks.
Again apologies from rushing to make a thread, just got kind of frustrated with not being able to boot into even the bootloader or just power it down for awhile, for seemingly no reason. Someone can delete this thread if they'd like. Thank you though!
maybe your phone doesnt like the overclock. not all phones can handle high overclocks and some cant work with ANY overclock. i would try letting the phone charge and flashing the stock boot.img
Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
I think you're lost
Songlambr37 said:
Who else in the world still use the manly Dell Venue?
who can help us upgrade it to 4.0?
Click to expand...
Click to collapse
Wtf,.. This is second thread I've seen that in,..
WR
Sent by WR's One XL
Chrysis said:
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure.
Click to expand...
Click to collapse
Almost always a matter of pilot error (as long as you have a charge light coming on, it should go to hboot no problem). Correct way is to hold vol down rocker, don't let it go, then press the power button for 3 seconds or so. Release the power button (but keep holding vol down). Don't let go of vol down until the hboot screen comes up.
If the screen is on, you can do the same as above, with the only change being: holding the power button down for 5 seconds or so until the capacitive buttons flash, then release the power button.
WarRaven said:
Wtf,.. This is second thread I've seen that in,..
WR
Sent by WR's One XL
Click to expand...
Click to collapse
I'm on it.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you choose not to decide, you still have made a choice"
Sent from my Galaxy Note (i717), using XDA Premium.
Chrysis said:
Yeah I was thinking this might not be the right place but wasn't totally sure, I apologize.
I was having trouble getting it to boot into the bootloader as well, forgot to mention that originally, holding volume down and power wasn't working. However after not sure how many attempts I did get it somehow. Perhaps I was holding the buttons down incorrectly, I think I let go of power early the time it worked? Not sure.
Click to expand...
Click to collapse
Future reference to boot into.downloader...
-lock screen like you would be putting phone in pocket
-hold power + vol down unroll screen goes off
-let go of POWER BUTTON ONLY right after screen goes off and continue holding vol down.
You'll boot into downloader just fine.
Sent from my HTC One XL cellular device over clocked to 1.9Ghz
Sorry to resurrect a slightly old thread, but was there any solution to this? My phone just died last night and won't start back up. It just stays stuck on the loading screen. I went into recovery and deleted the caches just in case, but it hasn't fixed anything. I have a nandroid backup from a weeks ago that I can just if I have to, but I'd prefer not to since I'd lose the app data.
Any ideas?
Valohtar said:
Sorry to resurrect a slightly old thread, but was there any solution to this? My phone just died last night and won't start back up. It just stays stuck on the loading screen. I went into recovery and deleted the caches just in case, but it hasn't fixed anything. I have a nandroid backup from a weeks ago that I can just if I have to, but I'd prefer not to since I'd lose the app data.
Any ideas?
Click to expand...
Click to collapse
Reading the thread says wiping caches worked for the OP.
Sent from my One X using xda app-developers app
Ah right missed that. Didn't work for me unfortunately. Would re-flashing the ROM without wiping work?
Valohtar said:
Ah right missed that. Didn't work for me unfortunately. Would re-flashing the ROM without wiping work?
Click to expand...
Click to collapse
That was going to be my next suggestion. Its your best bet if you don't want to lose all of your app data.
Sent from my One X using xda app-developers app
Related
Ok, so I had recently flashed MIUI sense based, I realized it wasn't for me so I restored my backup of TrickDroid 6.1. After doing this I went through and decided to delete some some stuff because my space was getting low (not 5mb low, more like maybe 1/2gb), I went to delete the MIUI v4 2.7.6 file and the phone appeared to go into standby... I tried to wake it up again with no luck. Plugging it into a charger does nothing, no red light; no green light. I'm unable to get into bootloader mode, no matter how long I hold down the "down volume + power" combo or any variation of it.
I need one of the gurus to help please !!!!
maybe post this in general or q&a?
any adb connection? if it's in standby then you may be able to move along to the next step
could just be a SOD (sleep of death)
Sent from my HTC One S using xda premium
calming said:
Ok, so I had recently flashed MIUI sense based, I realized it wasn't for me so I restored my backup of TrickDroid 6.1. After doing this I went through and decided to delete some some stuff because my space was getting low (not 5mb low, more like maybe 1/2gb), I went to delete the MIUI v4 2.7.6 file and the phone appeared to go into standby... I tried to wake it up again with no luck. Plugging it into a charger does nothing, no red light; no green light. I'm unable to get into bootloader mode, no matter how long I hold down the "down volume + power" combo or any variation of it.
I need one of the gurus to help please !!!!
Click to expand...
Click to collapse
Did u try hold the power? It'll reboot?then hold volume down about 10s.it should go to bootloader
2nd Option: use all-in-one tool kit.it has a command to reboot.
And don't post question or help here.read the rule.
Sent from my HTC One S using xda premium
Sorry about posting in this section, I assumed I'd get a quicker response.
I tried the All-In-One Kit thing... doesn't work "error: device not found"
I cannot get the phone to power on at all, no bootloader, no splash screen, nothing recognized by my pc. I get a "QHUSB_DLOAD NO DRIVER FOUND"
Thoughts?
calming said:
Sorry about posting in this section, I assumed I'd get a quicker response.
I tried the All-In-One Kit thing... doesn't work "error: device not found"
I cannot get the phone to power on at all, no bootloader, no splash screen, nothing recognized by my pc. I get a "QHUSB_DLOAD NO DRIVER FOUND"
Thoughts?
Click to expand...
Click to collapse
If it can't boot or use adb command.i think u should contact with HTC for helps,or at least where u buy the mobile. And of couse u still have Warranty.
It may be a hardware problem.We here can only try if it is a software problem.at ur position,the device can't be recognized by Computer/Laptop (before this,it worked well right?),then i think bad luck.
Don't be despair, it'll have some way to solve.
Sent from my HTC One S using xda premium
Sorry to tell you man the same thing just happened to me. I just got a replacement from T-Mobile. You will not get that thing back on. Just call T-Mobile and tell them it won't power on nor will it charge. It's funny because I was adding music to mine when it happened. If it happened the same way mine did then you will notice it was really hot when it shut off. The MDJ kernel overheated the Processor and killed it. Once that happens the device is a useless brick. I'm trading my replacement for another phone because this phone happens to overheat a lot.
Azuske said:
Sorry to tell you man the same thing just happened to me. I just got a replacement from T-Mobile. You will not get that thing back on. Just call T-Mobile and tell them it won't power on nor will it charge. It's funny because I was adding music to mine when it happened. If it happened the same way mine did then you will notice it was really hot when it shut off. The MDJ kernel overheated the Processor and killed it. Once that happens the device is a useless brick. I'm trading my replacement for another phone because this phone happens to overheat a lot.
Click to expand...
Click to collapse
Yup, same here, overheated while using fpse, died suddenly and wouldn't even charge. Tmo overnighted a replacement.
Sent from my HTC VLE_U using Tapatalk 2
Thanks everyone for the help... At least I know what I have going on... Already started re-downloading a buttload of stuff to get back on track. I don't normally backup my Nandroids or my TB files to my PC, maybe I should start.
Going tomorrow to the Tmo store to get the replacement sent overnight.
Thanks again.
Moved To Q&A
Please post in the correct section.
this exact thing happened to me twice. i dont get it. is it overheating or whats going on? it happened twice both times i was deleting a very large file 100 mb plus i have to call tmobile in the morning =/
---------- Post added at 08:29 AM ---------- Previous post was at 08:29 AM ----------
no one else knows of anything that might be able to revive my phone?
just read that it is most likely the processor a couple post up. =/ damn. im going to look into trading this phone for another
this has just happenmed to me to. was fully charged thought battery was low after it switched off managed to reboot see battery was full before crapping out completely. wont charge wont recognize in adb. Really dissappointed in my loss of data. i also imported this phone and had it running on att anyone know how good htc warranty service is bc tmobile is a no go for me
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Use heimdall n hold the volume buttons n enable flash bootlaoders
Sent from my SGH-T959V using xda app-developers app
@karose465 How old is the phone? If less than a year (doubtful), it should still be under warranty. Or you may be eligible for upgrade pricing: Fore example, "Customers with a Classic plan (two-year contract) are eligible for our lowest upgrade price on a new phone when at least 22 months have passed since their last phone upgrade. A new two-year contract is required to take advantage of best upgrade pricing. Of course, you can always upgrade a phone at any time, regardless of how many months have passed since your contract began."
For more info on Heimdall, just Google Heimdall Android.
Anyone with a sidekick contract ends earliest next march..
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
RicAndroid said:
Try Odin...choose repartition and you're golden. This is someone that has bricked his phone many, many times. Odin will give you the original stock Froyo.
Click to expand...
Click to collapse
I think for him and myself, the biggest problem is being unable to get the phone to stay in download mode. For some reason, the battery won't charge and the phone itself continously turns off and on when plugged in. So the charge isn't holding, therefore nothing will stay on/open.
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
gamingwiz said:
Im having the same problem. I have searched everywere and cannot find an answer that will fix it. If anyone can please help us fix this issue.
Sent from my MyTouch 4G using xda premium
Click to expand...
Click to collapse
I did some forum searching and found this. Hope it helps.
http://forum.xda-developers.com/showthread.php?t=1477838
Thanks ill check into that
Sent from my HTC Glacier using xda premium
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
---------- Post added at 04:33 PM ---------- Previous post was at 03:41 PM ----------
karose465 said:
I am not rooted on this phone I am on stock 100% I have done nothing with this phone since purchased.. I did not try to install anything on this phone that could have caused this. But yesterday it just started on this bootloop. The screen just shows the T-mobile sidekick 4g logo then to black and over and over .... I have pulled the battery put it back in and it immediately bootloops. I don't even have to power on . It even bootloops with the charger plugged in the battery symbol bootloops. I tried to put the device into bootloader (pwr vol up/dwn) to do a factory reset. but the bootloader screen just flashes on for a second and then it goes right back into the bootloop.
It appears as if this is bricked but how is that possible on a stock device? I called t-mobile and they could not help. All they wanted to do is sell me a new phone.
Please help
Click to expand...
Click to collapse
Hmm here is a link with for the ODIN and also provides some pretty cool roms that you might like to try.
http://forum.xda-developers.com/showthread.php?t=1538576
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
EpicLordPhone said:
Took the phone apart, put everything back. Still no luck
Sent from my HTC Glacier using xda premium
Click to expand...
Click to collapse
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Power Button Repair relating to Boot Loop
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
my Sidekick 4G is very old and just now went into bootloop... i googled the word and came across this forum.
As quoted above by previous poster that a power button repair was needed... I figured that I had nothing to lose, it being so old, I smashed the crap out of the Sidekick 4G on its power button. Lo and Behold, it booted into the system successfully.
SO... if no one has any qualms about smashing the crap out of their power button... give it a shot. It worked for me.
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
EpicLordPhone said:
Thanks for the info, but is there anyway I could turn it on without the power button?
Sent from my Amazon Kindle Fire2 using xda app-developers app
Click to expand...
Click to collapse
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
immorality said:
I don't believe so ?
You can switch the power button to like the track pad or something but you need to edit the phones ettings somehow
Sent from my SGH-T839 using xda app-developers app
Click to expand...
Click to collapse
Hmmm thanks, I might just try that!
Sent from my Amazon Kindle Fire2 using xda app-developers app
Mines stuck in a boot loop too.
I don't know if my Sidekicks problem is related to this or not. I rooted it and flashed it over to Glorious Overdose v5 on May 22nd this year and it's been running great. At least it was until last Friday, Sep 13. I was having trouble connecting to the WiFi at my house so I rebooted the phone. When it started to come back up a female voice started saying, "VooDoo lagfix has been disabled." "Converting /data and /system partitions." "Conversion time estimated 10 minutes."
I let it do it's thing and that's all it's been doing all weekend. I can get into recovery mode, I've tried restoring the phone from my backup with no success. I've even tried running through the process of setting up GOv5 again and it says it's successful, but the phone never boots up. It just stays in the same blasted bootloop and saying the same things over and over again about VooDoo. I've checked the VooDoo logs and there is an error file for the 13th and the logs following say "conversion." Can someone point me in the right direction as to what I can do to get my phone working again? Everything I've tried to research so far hasn't worked.
v5 hold both volume button, the track button and power button. Should put you into recovery mode. If not, you will have to put phone into download mode. You do this by taking out battery, then pluging into computer. When you reinsert battery hold volume down and power, if I remember correctly, and your download screen should come up. From your cp manually unroot it. Then it should be fixed, and just reroot it. I hope this was helpful
Sent from my SGH-T839 using xda app-developers app
No idea what I'm doing, precisely, but...
MythEdge said:
Dead thread but this is your answer - Your power button is shot. Need to have a new one put on. I know your problem has been fixed / replaced but for others still searching for answers...you need a power button repair.
Click to expand...
Click to collapse
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
LathyrusRoots said:
Hey, MythEdge. I'm not sure if you get notifications here or anything, but I registered to this site specifically to thank you; my phone ( Sidekick 4G, like OP ) bricked, and I smashed it against the table a few times ( you know, delicately... ) and it resurrected.
So thank you, sir; you were precisely correct. It worked on both of my phones, which had the exact same problem.
Just, wow. Thank you.
Click to expand...
Click to collapse
And almost a year later I log in and see this. Your most welcome. I haven't been working on phones for awhile but if I remember right, some models can be powered on by plugging the phone into a power source and when the phone vibrates or has a sign of life unplugging the unit. Some cables don't work and sometimes doing this via a computer can power up a device. Other than that, the other more dangerous way is to short out the pins on the bottom of the unit. I don't remember the pins but you can google a charge port diagram to help. I don't recommend doing this unless you have absolutely no other choice. Incidentally, this is why a phone will power itself on when a battery is put in and no other button is touched. The port is wet and corrosion has caused a link on the power pin and believe its pin 3. A simple cleaning with 90%+ rubbing alcohol solution will fix if cleaned quick enough.
So I am running cleanrom 5.5.1, unlocked bootloader and original first leak radios. I was texting and all the sudden bam. rebooted to a black screen. Can't access download mode or recovery. The Samsung logo pops up followed by the s3 logo, then a dimly lit black screen that never ceases till battery pull. When I try download mode, some blue text pops up in the upper left hand corner, then reboots to logo screens then back to black screen. Also, when I pull battery and put it back in, plug in a charger and the battery icon appers on screen. When it goes dark I can wake it with the menu button and see the battery icon again. Any suggestions? If not fixable, would I be able to get a replacement from verizon? (I bought the phone less than a month ago renewed contract. Any help is much appreciated!
If the blue text is popping up your trying recovery, not download mode. Pull battery put it back in then hold volume down , home, and power until the download mode warning shows up
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
If the blue text is popping up your trying recovery, not download mode. Pull battery put it back in then hold volume down , home, and power until the download mode warning shows up
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
i too just ran into the black screen after flashing an aosp kernel running slim 3.1 and im trying this way of getting into recovery and i hold down volume home and power and it still boots normally. i think i soft bricked my phone because i see the samsung logo but i never get to a bootlogo and only the hardkeys light up. im losing my damn mind and dont know what to do! i know its fixable cause i can see the samsung logo but i dont know what to do because the three finger salute wont work to get into recovery and i know that my bootloader is unlocked. not trying to thread jack just figured itd be pointless to post a new thread when the op is having virtually the same problem -___- lol go figure the first day i have my s3 i do this ****.. good thing i still have my nexus til i get it fixed.
Deltadood24 said:
i too just ran into the black screen after flashing an aosp kernel running slim 3.1 and im trying this way of getting into recovery and i hold down volume home and power and it still boots normally. i think i soft bricked my phone because i see the samsung logo but i never get to a bootlogo and only the hardkeys light up. im losing my damn mind and dont know what to do! i know its fixable cause i can see the samsung logo but i dont know what to do because the three finger salute wont work to get into recovery and i know that my bootloader is unlocked. not trying to thread jack just figured itd be pointless to post a new thread when the op is having virtually the same problem -___- lol go figure the first day i have my s3 i do this ****.. good thing i still have my nexus til i get it fixed.
Click to expand...
Click to collapse
Well you're right. Since you get life it's fixable. I would say pull your battery for a little while. Put it back in then hold volume down, home and while holding them both hold power. Your phone should boot into Odin mode.
Back stock for now....YUCK!
I had exactly what your describing
jndd333 said:
So I am running cleanrom 5.5.1, unlocked bootloader and original first leak radios. I was texting and all the sudden bam. rebooted to a black screen. Can't access download mode or recovery. The Samsung logo pops up followed by the s3 logo, then a dimly lit black screen that never ceases till battery pull. When I try download mode, some blue text pops up in the upper left hand corner, then reboots to logo screens then back to black screen. Also, when I pull battery and put it back in, plug in a charger and the battery icon appers on screen. When it goes dark I can wake it with the menu button and see the battery icon again. Any suggestions? If not fixable, would I be able to get a replacement from verizon? (I bought the phone less than a month ago renewed contract. Any help is much appreciated!
Click to expand...
Click to collapse
I had just rooted and flashed Jellywiz the previous day. The next day at work, I don't know why, but I must have experienced some kind of massive battery drain. The phone would not reboot, I would plug it in and it would just vibrate and flash the battery sign on the display every few moments. I had to put the phone on a charger for about 15 minutes and let the battery charge until I was even able to get the phone to boot. I would not boot while plugged into an AC charger until I let it charge. Very weird, and it hasn't happened again since but I swore that my phone was bricked. Basically the battery was so dead it wouldn't boot the phone, let it charge with out ****ing with it for a while and then try and boot it up.
kintwofan said:
Well you're right. Since you get life it's fixable. I would say pull your battery for a little while. Put it back in then hold volume down, home and while holding them both hold power. Your phone should boot into Odin mode.
Back stock for now....YUCK!
Click to expand...
Click to collapse
I don't know how to use Odin I did the non odin way to root lol I can get into download mode tho so apparently its fixable thank god. I feel like a noob right now I didn't ever do anything like this on my nexus or tbolt and then the first day I do it on my s3 -___- guess I gotta read up on Odin
Sent from my Galaxy Nexus using Tapatalk 2
Deltadood24 said:
I don't know how to use Odin I did the non odin way to root lol I can get into download mode tho so apparently its fixable thank god. I feel like a noob right now I didn't ever do anything like this on my nexus or tbolt and then the first day I do it on my s3 -___- guess I gotta read up on Odin
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Odin is easier then it seems, but make sure you know what you're doing because you can brick your phone with it. However, there is a great guide right here on how to unbrick your phone. Just follow section 5, I did it last night(to just clean up my phone)
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
Odin is easier then it seems, but make sure you know what you're doing because you can brick your phone with it. However, there is a great guide right here on how to unbrick your phone. Just follow section 5, I did it last night(to just clean up my phone)
http://forum.xda-developers.com/showthread.php?p=28530394
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So do I need to do all the steps in section 5 including flashing the radios if I never messed with them prior to rooting?
Sent from my Galaxy Nexus using Tapatalk 2
Deltadood24 said:
So do I need to do all the steps in section 5 including flashing the radios if I never messed with them prior to rooting?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
You may want to double check section 5 it's one file that includes the entire stock ROM including a locked boot loader and the radios that match.
Sent from my SCH-I535 using xda app-developers app
kintwofan said:
You may want to double check section 5 it's one file that includes the entire stock ROM including a locked boot loader and the radios that match.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Oh okay thank you man! Sorry to thread jack op! I'll check it out
Sent from my Galaxy Nexus using Tapatalk 2
thanks guys
The first several times nothing would work not even download mode, my recovery console was gone too. after several tries download mode popped up so I immediately hooked up to odin and reflashed a stock root. all good now. Still wonder why it borked itself in the first place. Seems to be a mystery but I'm not too keen on flashing cleanrom 5.5.1 again...
jndd333 said:
The first several times nothing would work not even download mode, my recovery console was gone too. after several tries download mode popped up so I immediately hooked up to odin and reflashed a stock root. all good now. Still wonder why it borked itself in the first place. Seems to be a mystery but I'm not too keen on flashing cleanrom 5.5.1 again...
Click to expand...
Click to collapse
i couldnt get odin to work on my computer for some reason and after searching through google i found a forum on getting into the stock recovery and figured id try it and my phone decided to cooperate and go back to clockworkmod after all that and now my phone is fixed lol technology..
No worries about jacking thread I'm glad my post lead others to help another with not the same but similar issues. I've been out of the dev circle since g1 days but I think its time to play around and execute some system dumps after a bit of tweaking. definitely like Odin! All in one multi partition flaher! Fashing via adb used to be too cumbersome with the early sdk's!
Sent from my SCH-I535 using xda app-developers app
Yeah I got a lot to learn about programs its crazy how much stuff there is to know and things constantly get added every day lol the android community is very interesting that's for sure
Sent from my SCH-I535 using Tapatalk 2
Hi there,
I have a Rogers Galaxy SGH-i727R. About three weeks ago, the phone started re-starting on it's own. I though maybe it was a sticky power key and had that replaced. The problem persisted. I then noticed that it was primarily upon receiving text messages that the phone would reboot. So it seemed it was a software issue. I am running the stable build of CM9.
Yesterday the phone rebooted and never got off the angry alien screen. I pulled the battery, charged it etc and still could not get it to fully boot up. I left it for over an hour. I finally decided to call it quits and re-flash the phone. Problem is, it will not boot into recovery at all. When I hold down Vol + - and Power, it jsut goes into a loop of vibrating every three seconds until I let go and then it tries a normal boot again. Once, I briefly got a screen saying I was trying to install custom software and to press volume up to do so, but before I could hit volume up, the phone cycled off.
I should also mention that the four buttons on the bottom of the screen do not work. I accidentally sliced the wires on the side of the phone when opening it up. I use a software button saver widget to access their functions. I wonder if that issue is related....
Thanks for any advice. I would like to get into recovery so I can load a new ROM or a stock ROM.
You're going to get blasted for posting this here....
That being said, your power button is borked, common on these phones. Happened to mine, but I was still under warranty so it was replaced.
eagercrow said:
You're going to get blasted for posting this here....
That being said, your power button is borked, common on these phones. Happened to mine, but I was still under warranty so it was replaced.
Click to expand...
Click to collapse
He said his was replaced and the issue continued..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Blast away
Sorry. Where should I be posting this? I am happily corrected. I find the titles of the forums confusing, sorry.
btm fdr said:
He said his was replaced and the issue continued..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Your point? I can't tell you how many times I've been sent "new" or "tested good" parts and they are DOA when installed. Or people who claim to have replaced or fixed a part but really didn't.
tonyrage.stc said:
Sorry. Where should I be posting this? I am happily corrected. I find the titles of the forums confusing, sorry.
Click to expand...
Click to collapse
In the Q/A section is the proper place. I had the exact same issues you are having, fortunately I had the option to trade it in for a new one. Good luck!
Hi there,
I posted this in General first. I think it should be here.
I have a Rogers Galaxy SGH-i727R. About three weeks ago, the phone started re-starting on it's own. I though maybe it was a sticky power key and had that replaced. The problem persisted. I then noticed that it was primarily upon receiving text messages that the phone would reboot. So it seemed it was a software issue. I am running the stable build of CM9.
Yesterday the phone rebooted and never got off the angry alien screen. I pulled the battery, charged it etc and still could not get it to fully boot up. I left it for over an hour. I finally decided to call it quits and re-flash the phone. Problem is, it will not boot into recovery at all. When I hold down Vol + - and Power, it jsut goes into a loop of vibrating every three seconds until I let go and then it tries a normal boot again. Once, I briefly got a screen saying I was trying to install custom software and to press volume up to do so, but before I could hit volume up, the phone cycled off.
I should also mention that the four buttons on the bottom of the screen do not work. I accidentally sliced the wires on the side of the phone when opening it up. I use a software button saver widget to access their functions. I wonder if that issue is related....
Thanks for any advice. I would like to get into recovery so I can load a new ROM or a stock ROM.
Get a new phone
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
Get a new phone
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the constructive reply.
read the sticky "read this b4 posting", btw its what you should of done as the answer is there, its above your post, goto near the end of op and do the test