Hey, so I have the infuse 4g on JB 4.2.2, and I want to get it back to a stock 2.3.5. I have looked at every forums, but I want to know if it's possible to do so without a computer. Is there a .zip package that I can just flash as a normal rom to make it go back to normal?? Thanks!!
You have to have a computer to return to stock because ICS and newer use different partitions for everything than gingerbread. Flashing with Odin on a computer includes a file that tells the phone the old partitions and allowing it to run gingerbread.
Sent from my MB300 using xda app-developers app
I am running my phone with the 1.275 release of the Beanstalk. Last month I forgot my phone in my pocket when going in the sea (I believe this is a common problem among people recently). After it got wet, it didn't work at all for over 12 hours. I took it apart and made sure I dried everything. I cleaned all connections with alcohol and put it back together. It booted and it took a while to settle. I didn't expect it to go without issues. All works great except two things:
1. It takes a long time to wake up when pushing the power button. Sometimes I miss calls because the screen stays dark too long and by the time it wakes up, I have already missed the call.
2. When a USB cable is plugged in, it is not responsive. I found a way around it - right before plugging it I wake it up and hold my finger on the screen. Then connect it with the cable and luckily it stays awake during the whole time.
I decided to upgrade to a newer release of Beanstalk and did that by flashing 1.275. I was hoping that this will fix it. Unfortunately everything stayed the same.
Next idea - return to stock and make my way to the Beanstalk again. Well, I can't make it go in Download Mode and two computers couldn't recognize it. I used different cables including the original one, but without any luck. Then I installed a reboot widget from the play store and was hoping that it will reboot in download mode, but no luck again.
Does anyone have any other suggestions? At this point I am not certain if this is just a software issue. It could be a hardware problem as well.
Any help will be greatly appreciated.
Related
I'm scared that I may have lost one
I rooted with z4root, which seemed to go well. I downloaded rom manager (paid version) and flashed cwm. I had some trouble booting into cwm so i did a little investigating and ended up downloading bootstrapper as well. After enabling boot strapper I was able to get into CWM and do a nandroid backup.
I downloaded and flashed to newest CM nightly (8 I believe), and my phone seemed to be happy (it did want to power cycle when I was signing on to my google account at first, but after skipping the step in the set up wizard of the phone and just adding the account after it worked fine.).
I went to bed and did not plug the phone in. I woke up and saw that it was on still and proceeded to play a video game. I heard it beep across the room an hour later (no one around it) and figured it was getting low on battery since it had not been charged. When I picked it up to check the time, it would not start up. I have pulled the battery several times, tried to boot into cwm to flash my back up (could only get into the factory recovery), and I seem to be getting less and less response as time progresses. My power button doesn't seem to be producing any effect now and I can only get the screen to come up and display the big moto "m" if I plug the phone into a charging dock. I did charge my battery in my brothers OG droid since I heard that it wont charge the battery if it doesn't start up.
I'm by no means an expert, but I've had very successful rooting experiences with my Dinc (even soft bricked my Dinc, had a heart attack, then brought it back from the brink with help from this web site), a Thunderbolt, and a couple of fascinates. Never imagined a nightmare like this. Best part is this D2 is a loaner from my boss while I wait for my Charge to come in the mail!
Any help would be immensely appreciated.
ps. The only oddball variable that I can think of in this mix is that I'm using my micro SD card from my Dinc which had at least one nandroid left on it (which I deleted in Rom manager). I wonder if rom manager (or me... most likely me) got confused and possibly tried to flash cm7 for the Dinc from my SD card. User error, the story of my life.
try plugging the phone into a wall charger and leave it for a while. the charge window will come up
Yeah, battery power seems to be the simple answer to my power button not being responsive. I hijacked my brother's battery and my D2 powered up to the "M" screen and froze with just the power button press, or will boot into stock recovery (holding X on the keyboard while depressing the power after a battery pull), though I don't seem to be able to do anything effective from there. My battery is currently in my brothers droid charging as I continue to look for a solution/hope for more leads from this thread. Being able to consistently get a response from the phone is a step in the right direction though.
Have you tried powering up the phone into bootloader? That'd be a quick way to know if your data is corrupt. I went through that whole process last week. Only thing is that your battery can't charge in bootloader so make sure your battery isn't low.
Sent from my DROID2 using XDA App
If you're talking about holding the X key and power, then yes. This will bring me to the stock recovery menu. If there's an action that can be preformed from the stock recovery that will help me, I'm unaware of it. I know from cwm I would have the option to restore from a back up that I made (I have a stock back up and a back up from as soon as I got the phone up and running with a cm nightly rom).
I'm hoping that when I plug the phone into my computer it will be recognized. I read the instructions on how to run rsdlite here and aside from being able to navigate my phone menus to put it into usb mode, I should be able to take care of everything else. So now my real questions are; If my computer sees my device, is running the rsdlite program my best solution, and what's the next step if my computer does not see my phone?
try this
your phone will gharge if you put it in bootloader mode i know because ive done it now if you phones rom is jacked then flash it back to stock with rsd lite you can get the a955 stock rom from here this web site or my droid world also it will work there is noting wrong with your phone take care chris
Hello all.
I was helping my buddy with putting on a custom ROM onto his Galaxy S. I did everything required and got the phone to run CM9 just fine. The issue is that his Volume Down button is always being pressed. It's not a physical press, the phone will always just assume it's being held down. This makes the ROM boot up in Safe Mode every time.
This is an issue the phone seems to have had before I did anything to it. I guess it wasn't important enough to tell me until I asked him about it...
So what I would like to do is either
A) Install a ROM that does not do this. I am not sure which ROMs I could use, but I assume anything built using CM9 will do this.
B) Put the phone back to stock. He is still within his T-Mobile warranty so it would be preferable for him to have a fully functioning phone anyway. The issue I have run into while trying to use the One Click restore is that when I power the phone on with the two buttons and the USB cable being plugged in, it freezes on the "It is not recommended to install another OS" or whatever screen. When the PC detects the USB connection, it reports it as being an non-functioning USB device (tried a few computers and different USB ports. same thing). I also tried installing the required Stock version of a kernel and the CWM version of the stock ROM but it comes back with an error before it can install through CWM.
Any recommendations? I'm not really sure what to do at this point so I figured I would ask before I do something that would brick it.
Take the phone apart and clean the volume rocker. That advice stands whether you have a Vibrant or the SGS4G. Next look under the battery and see what your model number is. If it's not SGH-T959V do not flash anything here. Good luck.
It is the SGH-959V.
Is there a guide on how to disassemble the phone?
Here's a decent guide
http://www.ifixit.com/Teardown/Samsung+Galaxy+S+4G+Teardown/4977/1
Sent from my SGH-T959V using xda app-developers app
I had my power button stuck yesterday. The darn thing just won't pop out. So I took some kitchen decreaser and sprayed on a towel to wipe the area around it. And whoa la, it is as good as new. Remove the back cover when u do this. Let the decreaser soak around the button just a bit. Use a toothpick to get the dirt and oil out around the button. Also clean the area in the back cover where the button is.
Hit the thanks button if it helps. It's my motivator to be more helpful.
Hello all, I have an HTC Arrive running LEAD's 7.8 8858 ROM. I've been running this rom since January with very little issues. However, within the last couple of weeks I have been noticing strange things going on with my phone. Some mornings I have woken up and left for work and notice my phone is almost dead, even though I remember plugging it in the night before. Also, as of this week, after a reboot of my phone, the Call button shows Home Service instead of Sprint, but eventually changes over to Sprint. At times I will go to use my phone and see it has put itself in Airplane mode or has a locked sim card logo displayed instead of signal bars. In this case I have to reconnect to the network to regain functionality.
Now as of last night my phone is constantly rebooting while charging. I plugged it in last night and kept hearing a buzz (I keep it on vibrate), looked at the phone and it would be booting up. It fully boots to the Start screen and I can go ahead and begin doing something, but no matter what I'm doing it just shuts completely off without even saying Goodbye (literally). It continues to do this until I unplug it, and it ONLY reboots when plugged in. I've tried a battery pull a couple of times but to no avail. Its getting very annoying because it takes much longer to actually charge, and I also don't imagine this is very good for the phone itself.
I was planning on flashing LEAD's latest release to see if it fixes it, but I'm not sure if the phone will react this way plugged into the PC as well. I haven't plugged in to the computer yet to find out, hopefully it won't do this, else I won't be able to flash it.
Any ideas or suggestions? Has anyone else had this issue?
well i plugged into the pc and it still reboots however, when in the tricolor bootloader it does not reboot! so with this discovery i now know that its a bug in the OS causing the reboots. also, because its not rebooting in the bootloader, i should be able to reflash without issues, correct?
as a side note, the phone got VERY hot last night while left in to charge, so i will just charge my wifes phone and swap the batteries so that i wont damage my phone.
no one else has reported this issue with this ROM as far as i can see, only random reboots.
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
leadpoizon said:
Sorry to hear about all those problems. Have you tried the latest ROM after the 8858 release? I suspect there could be some sort of corruption in the OS. If you haven't, I recommend biting the bullet and just restoring the phone. I also recommend flashing the latest ROM, since it has the latest OS version. If the phone isn't having problem when in boot-loader mode (tri-color screen), you should be OK to flash it.
Click to expand...
Click to collapse
thanks for the reply lead! i am going to flash you latest release now. i am going to look for an alternative way to backup pictures outside of Zune and the PC, but i dont think any exist.
i will post back when its up and running.
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
x_orange90_x said:
i flashed the 8862 ROM and its been plugged in for about an hour with no reboots
plus, this ROM feels snappier than the 8858. an issue i used to have with IE, that is gone in this build is it would open Google every time i click the IE tile.
thanks for the help leadpoizon
Click to expand...
Click to collapse
No problem. Glad your issue is fixed now.
Ok so I am no longer having the charging or battery issues anymore, but now my Marketplace is basically broken. When I can manage to begin a download it immediately goes to Attention Required, and upon clicking i get error code 8000ffff. So no apps will install/download from Marketplace. Also, on almost every game and app, it says this app is not available for your device, even ones i used to use on 8858. Some i have even manually installed and they work fine. Also when trying to even view many of the games in the Marketplace, I get error 805a0194. So far I haven't managed to install anything from the Marketplace aside from the Bank of America app.
I have tried resyncing with Live, rebooting the phone, tried changing Marketplaces and settings with the Marketplace Config app. Nothing fixes it
Any suggestions?
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
x_orange90_x said:
No one?
I'm beginning to think 8862 is to blame. I keep getting service unavailable errors from MP, or everything is not available for my device. I don't want to hard reset, but it looks like this isn't going away on its own. :/
Click to expand...
Click to collapse
Sorry, I've moved on from this device, so I can't test anything now. I never had any issues like this on my device and I used it extensively for a long time after flashing that ROM.
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
UPDATE 12/23/2013:
1. I was able to get into Recovery by quickly pressing reboot and reboot into recovery. From here I could get into Download Mode.
2. I first cleared my Dalvik & Cache and reflashed JellyBeans v19, then cleared Dalvik & Cache again. This did no solve any problems.
3. Next I flashed the Stock VRBMF1 Firmware through Odin, which also did not solve any problems.
4. Now I am downloading Root66 and following Hero's guide to unbricking a soft-bricked device.
usatf1290 said:
At the gym the other day i looked down at my phone, and it seemed to be turned off for some reason. This is the state its in now:
1. The phone is not responsive on battery, and the battery is fully charged.
2. Upon plugging the phone in to power, it has the charging animation.
3. When trying to go in to either dowbload or recovery modes, the respective preliminary screens show up, then the phone bootloops.
4. When booting normally (under power), everything seems normal and it can get to the lock screen. Then sometimes i can pull down the notification bar and go to settings, but other times it randomly bootloops. If i pull out the power, it turns off.
5. This is a replacement phone from verizon about two weeks ago. The last one had bad screen burn in.
Im rooted and unlocked and i was running jellybeans v19 ROM.
Im in Germany right now on a Vodafone prepaid SIM. When putting the Verizon SIM back in, the same things happen.
Click to expand...
Click to collapse
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
BadUsername said:
Weird...
My first guess is something software related, I'd start by going back to stock mf1 or mb1 in this case and seeing if you can reproduce the problems. Just don't take the 4.3 update or you'll lock your bootloader.
If that doesn't work, then something is wrong with the phone, and it almost sounds like a bad power button but with some weird other symptoms. I'd send it back to Verizon to get another one of its still acting up.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the response!
I would try to flash stock packages through Odin, but i cant get to download mode. Usb debugging is enabled.
Ill probably send it Verizon when i get back to the states, but I was wondering if i could do anything in the mean time.
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
ShrinkWrap561 said:
Hello,
My phone was running a stock ROM, it was not rooted.
On Tuesday morning i received notification on my phone that I had an update for 4.2.2. I applied the update and it appeared that everything went fine. Unfortunately, the phone immediately began re-booting every two to three minutes.
I have re-set the phone to factory defaults - no change.
I have used different batteries - no change.
I have put the phone into safe mode - no change.
If I put the phone in download mode - it does not re-boot.
I have tried to revert back to an older ROM but ODIN errors out.
Does AT&T have the ability to re-push the update OTA or even roll back to an older version?
Of course my contract is 5 months away from being fulfilled so I believe that I would be forced to pay full price for a new phone should I not be able to resolve this.
Any suggestions?
Thanks.
Click to expand...
Click to collapse
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
bweN diorD said:
your phone likely is not broken physically, it just needs to be re-flashed. the problem with that is, the flash files dont always get released or leaked right when the ota comes out.
unless someone has a better idea, your best option is probably to keep an eye on your phone specific forum for someone to post the flash file for this new update.
it really doesnt matter if they could push the update again, it would fail on verifying the current install.
if the device was unlocked, it could be rolled back to an older version. i wouldnt hold my breath waiting for them to do that for you.
you could check the forums and see if there is a way to unlock it yourself. some can be unlocked, a lot cant.
Click to expand...
Click to collapse
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
ShrinkWrap561 said:
Update...I went to a SAMSUNG experience (or whatever they are called) in a Best Buy and I re-flashed the phone with 4.4.2...no improvement.
I have tried to root the phone with Towel Root and CyanogenMod but neither worked.
In additional attempts to figure this out, My son noticed that if the phone was connected to a computer, it did not re-boot. He though that it was related to it being connected to a power source so he plugged it into a charger, the phone would still re-boot.
So what we have determined is the phone needs to think that it is connected media device. The phone then works as it should.
Any ideas on how to resolve this? If the phone's battery dies and we are not near a useable computer, the phone is then again a paper weight.
Click to expand...
Click to collapse
you have got me on this one. it acts like a classic software issue. now that that has been eliminated.
you performed a factory reset after the flash im assuming?
i don't know what else to tell you, if the software is clean, it has to be hardware damage.
sorry