Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
ledoktre said:
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
Click to expand...
Click to collapse
did you install the moto drivers? if you're unlocked be sure to flash 2.3.4 not 2.3.5
Good afternoon,
I have installed the moto drivers. I am on Windows 7 64 bit (dual boot with Linux Mint Debian 64). I installed "MotoHelper_2.1.40_Driver_5.5.0.exe", and was using RSDLite5.6.
As far as I know, the phone was locked. Rooted, but locked. Some say it will actually say on the screen 'unlocked', mine does not say anything like that.
Thanks,
Just to make sure it's not a battery issue, there is free battery swap if you can run by a USCC store. But I think you're right, it's probably not that. Wish I could help you more, but it stumps me.
ledoktre said:
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
Click to expand...
Click to collapse
From the phone completely off, hold vol-down and power. When the screen lights up, release power ONLY. Keep holding vol-down until some text shows up then release. Click vol-down to scroll through options until Recovery shows up. Click vol-up to select. Once recovery starts, navigate using vol-up/vol-down and power to select. /data will be wiped if you do a factory reset.
Hope this helps.
Related
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
texnote said:
I received a G Tablet which had been used for development work for a few months. The person giving it to me (not the dev who has left) said the tablet was working fine, but had just become frozen at a reboot after he had tried to erase personal data from the tablet. I asked him if he had erased the sd card and he said "maybe" but that he couldn't remember. I powered the tablet on and sure enough it displayed two lines on a black background, one of which said something like loading kernel.
Now, these tablets were all rooted, and had Android 2.3 on them, via one of the ROMs discussed here. I don't know which one however.
So, I tried using NVflash to flash the tablet back to a stock ROM. Tablet then got stuck in a boot loop; I would see the Viewsonic logo, then the G Tablet logo, and then this would go on forever.
So I shut it down and tried again. This time Nvflash failed almost at the last step after having written most of the image.
And so here I am now, with a totally dead tablet. I cannot power it on. No combination of power or volume up/down buttons work. The only sign of life is when I plug it into its charger, and see the charging light come on.
I confirmed again with the person who gave me the tablet that the device was working just fine before it froze at a reboot after his erasing attempts.
Is there a way out of this? I hope so. Please help!
Thanks very much
Paul
Click to expand...
Click to collapse
I would try popping it open and unplugging the internal battery then plugging it back in. Also hit the internal reset button while you're in there. It's pretty hard to actually kill one of these tablets. PM me if you need any other help.
help
Started my own thread, didnt mean to hijack. =)
Thanks, I will try removing the battery and let you know.
As for NVflash, I believe the latest version is here:
http://www.slatedroid.com/topic/171...-using-either-11-or-12-based-images-g-tablet/
However in my case I have no idea whether I have 1.1 or 1.2 and there is no way to determine this. Which one should I choose?
Paul
Doesn't matter for NVFlash, just download all of the flash files again because it might be that you have a bad download. Also make sure you have the right drivers installed since the drivers that automatically install when you plug it in sometimes don't work.
I'm pretty sure that if it boots past the birds, the hardware is working okay, so you should run the FORMAT version for NVFlash and then I'd run just a CWM flash setup and see if you can get into CWM and delete the partitions from within that.
The best thing to flash as far as ROMs would be Bekit's 1105 which is stock OTB with a few key changes. If you can't get the 1105 to play nice, you might really have some hardware problems.
I would go with the 1.2 BL, it will give you access to the newer roms as it appears that dev for the 1.1 BL seems to be dwindeling. I upgraded mine to 1.2 the other day and it worked great.
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
elead1 said:
I have little hope for this, but thought I'd post it up anyway before buying a new phone. I have been using the JellyBomb ROM for about two weeks now, and until today it was working fine. Then (seemingly) randomly, while I was browsing a webpage in Firefox, the phone locked up.
"Okay, I'll just force a hard reboot." So I held down the power button and it turned off. When I turned it back on, it got stuck at the HTC screen (I let it sit for about 15 minutes). So I did another hard reboot and booted into bootloader (power + vol down), which came up fine. I went into recovery (TWRP 2.3), which took about 5-10 minutes to move past the TEAMWIN splash screen into the menu.
Once in the menu, I went to reflash the ROM, but no files showed up in either the internal or external storage which I found strange. I then went to reboot from the menu, at which point TWRP informed me that I had no OS installed. At that point, TWRP froze up, so I did a hard power off again and tried to boot it back into recovery but nothing happened. The soft buttons didn't even flash like usual.
Once I had access to my computer, I plugged it in, hoping that something would change with it connected to a PC. At that point, the Windows driver manager reported failure at installing a driver. I checked device manager to see that I had a QHUSB-DLOAD device connected. After some Googling, I attempted Unlimited.IO's fix tool (using a Linux live CD, obviously). I had little hope, however, because my device was S-ON. And sure enough, although the tool reported completion there was no change to the phone.
So, now that that long-winded (and hopefully sufficiently detailed) story is complete, does anyone have any suggestions/advice/instructions for me?
Thanks!
Click to expand...
Click to collapse
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
VeNuM said:
Hey elead got your pm and I'm sorry this has occurred to you. I'm not familiar with the unlimited IO. But I will suggest that you allow your phone to charge tonight while its off... The reason for this is I believe the battery has fallen to a level such that will not allow the boot process to work... Having said that allow it to charge the night... Then see if it will boot into bootloader in the morning. If it does this you should be able to flash an ruu. I realize this is a stressful time, I've been in your shoes before and actually bricked. BUT, I believe your phone is salvalgeable and with a proper charge you be able to fix the issue... Please report back in the morning and let me know... Ok??
Click to expand...
Click to collapse
I will post back with results. Not like I've got much else to do with it right now, eh? :laugh:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
Damn. Well I've been there done that too...
send it to htc.
elead1 said:
No change. I'm thinking maybe I'll take it to the Sprint store and play dumb to see if they'll just give me a new one (it's worked before!).
Click to expand...
Click to collapse
i had the same problem but my situation was that i downgraded the radio while s-on. I was in the same situation that you are right now. i did everything i could but nothing worked so my last hope was sending it to HTC and say that i lefted updating the software while sleeping and when i woke up it was like that. i sended they didnt even ask, i got it back like new . :laugh:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
anticlotto_ said:
Before the incident, I had root, no unlocked bootloader, stock JB, v20h.
What had happened was I was trying the Font Installer app in th Play Store because of the added customization that would have been nice.
I found a cool font, and I backed up my current fonts and then pressed install. SuperSU asked for permissions like normal and then my phone restarted.
Then it was so that my phone was stuck at the T-Mobile boot animation after the LG Logo. For about 15 minutes. This is where I believed something was starting to go very wrong. After contemplating for a few extra minutes, I decided to just take out the battery and restart. Same outcome. I thought of all the things that were on the phone thus far because I had just gotten it recently, and decided that it wouldn't hurt me to just do a hard reset by pressing home + vol down + power. Everything went smoothly. Except for the fact that even after I did that, it was leaving me at the T-Mobile screen.
I decided to look on the forums for development and tried to do the unbrick method, to no avail after about 3 hours now. I used the LG User Support Tool and since I hadn't updated to V20f, I decided to do that to see if it would solve my problem. It still didn't, and I'll be honest, I'm a little upset just typing this right now.
I also tried the Upgrade Recovery option and it warmed my heart to see that the process was actually starting. But right at the screen where it says that it is supposed to be downloading something, it freezes up and nothing happens no matter how long I wait. I saw somewhere that it should be a glowing red bar, but I do not see that anywhere, it is just frozen, saying Time Elapsed: 00:12. And before anyone asks, yes, I ran absolutely everything as an administrator.
Is there any possible way to bring this phone back? Any help would be immensely appreciated. Thank you in advanced.
Click to expand...
Click to collapse
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
CROSSFREEZE said:
did you hard reset? then turn off your phone disconnect the battery, connect to the pc holding the volume up button? then try the Update Recovery?
i would just go through that process over and over until it works, theres not really a way to brick this phone i've heard...
Click to expand...
Click to collapse
Thank you for your reply! I have tried hard resetting multiple times, but I had removed some bloatware apps (I will quarantine them next time instead because I don't wanna go through this ever again) and I have tried the kdz method to only be stuck at 15% every time when I followed instructions to the pixel. I have tried to do it on windows 7 and windows 8. I have also tried the fastboot method by lelus, and that manages to "work" but I am still stuck at the tmobile boot screen afterwards. I have gotten the hang of the process of getting into the fastboot, but what do I do from there? I chose to flash ics xloader and uboot, but the process goes by so fast, I'm not even sure it is doing anything. The LG Tool has really gotten me nowhere, it just gives me a lovely error and then cannot continue the upgrade recovery process.
It said somewhere that after I flash through the fastboot I then have to try the kdz method, so I am going to do that now and see if it works. I don't know if there would be a difference between flashing a jb kdz or an ics kdz, but I will just do ics to be on the safe side.
I am quite happy to say that flashing the ics kdz was successful, and my phone is now up and running.
My p769BK is stuck on the LG screen. /: months
Sent from my LG-MS770 using xda app-developers app
im terrible with fastboot, i used the unlock the bootloader for noobs with an offline flash.
heres what i did to get out of bootloops....
alright, this is all from memory but the offline flash didnt work as well for me when stuck in weird bootloops.
Step one-going back to online flash---->
A---
the easiest way i found was to go to C:/windows/system32/drivers/ect/hosts
right click>open with notepad
there should be two lines at the bottom
"127.0.0.1 csmg.lgmobile.com
127.0.0.1 csmgdl.lgmobile.com"
i would cut them out and paste them in a text doc in the same folder for reference later...
but either way you should remove them from the hosts file and save
B----
Make sure your small server is closed! once you minimize it it should go down to your status bar (shttps)
Step two-LGMS---->
make sure you have LG mobile support installed or install it.
open lg mobile support
install needed drivers for your phone
power your phone off/remove the battery
put battery back in
connect it to your computer holding down the volume up button
S/W UPDATE mode should pop up, if it doesn't preform and hardreset and try again til it works (it will)
then in the top right corner there should be a button or two click them both until you see
"restore update" or Update restore or something to that effect
select that
and let it ride man
i got my phone ****ed many times and just had to keep redoing this until it worked. if your bootloader is truely unlocked you can probably go through all that again and get CM10 working, i did but im still working through kinks.....
GOOD LUCK feel free to ask any more Q's about this process if you run into any problems
Okay, I want to start by saying I am truly sorry if this has already been looked at. I truly spent 20 minutes searching and could not find anything that address this problem.
Im going to give you the long story because, I am actually really in need of help.
My friends owns a droid x2, ?.?.5 (sorry I cant honestly remember but, its the gingerbread ending in .5)
Her husband decided to root her phone for her, and it was in Chinese and only had a partial root. Frustrated she brought it to me because, well I have a working knowledge of google, this forum, and have flashed and rooted many phones.
I managed to change the language, and root the phone (using DX2_batchroot), I installed a custom recovery (its an apk ), I also think I installed the Recovery BSR (that will make sense in a second)
I booted into custom recovery, I made a backup. Then I went about wiping caches so I could install a custom rom. I wiped all the caches, I formatted the internal memory, and then I accidentally hit "boot now".
The phone gets the the "M" and says "Failed to boot 1"
If I try holding the power and down button it just flips off completly.
I cant scroll thru the menu, I cant get the computer to acknowledge its on.
It has been plugged in the hole time.
So what do I do, and what DID I do, so I never do it again.
Thank yo
Update
Since this happened I have left it on the wall charger and checked it out occasionally.
Well it still won't boot into recovery but... It is now willing to play ball when I press volume down and then plug in to the computer. Sadly it then tells me that the battery is too low.
Now, I *guess* it could be, except after rooting and before rebooting into recovery to make my first backup I had the phone off andplugg ed into a wall charger for 2 hours.
Again, any help you can offer
Often if ROM won't boot, charging does not work either.
Will need a charged battery, or a TBH factory cable adaptor.
See my low battery options in my list.
sd_shadow's (themib) [Collection] of Links for Droid X2
Sent from my Amazon Kindle Fire using Tapatalk
Hey guys. A friend of mine gave me a Motorola Droid RAZR XT912 which woudln't work with GSM networks to make it work. So I went here and used DROID RAZR Utility XT912 Jellybean to gain root. After that I installed Safestrap 3.73 and flashed CM11 M9 into the Slot1. The phone was working completely fine without a single hitch.
Today my friend called me to ask about the phone and I said it's working only it has two systems (lots of not really good used memory). He said to me to remove one of them and I went back into Safestrap recovery and activated Stock. Then I wiped Dalvik cache, cache, system, android secure. After that I switched to Slot1 (CM11) and it said it was active. I thought it would work since there is still that CM11 in Slot1, right? I tapped reboot -> system and since then the phone won't boot. When I press and hold the Power button for about 7-8 seconds, Motorola logo is shown and after that only a black screen (phone turned off). I tried holding Power+VOLDN but sadly same results. I know I should have read more about removing stock, but I did it anyway. Everything was going so smoothly so I thought there wouldn't be any problems. I think I should point out that when I connect the phone to my laptop, I can see "Mot Composited ADB Interface". Does this mean the phone is not dead?
Is there a way to unbrick the phone without some special cables and/or equipment?
Thanks.
Use Matt's utility to restore things to stock:
http://forum.xda-developers.com/showthread.php?t=2192467
@mikeoswego Thanks. I actually managed to get it working a little before this post using that amazing piece of software.
The state of the phone was like this: I hold the Power button, Motorola logo pops up and then the phone turns off. I hold Power+VOLDN same thing happens (Logo is shown and then it turns off). I couldn't even get it to fast boot. It just turned off. I searched a bit here and found the solution. When the logo is shown, press and hold VOLUP+VOLDN and don't let go. The menu will be shown where you can select fastboot. After that I just connected the phone to my laptop, used matts program and resurrected the phone
I lost root, so I rooted again, installed safestrap, wiped Stock and in it's place installed CM11. Rom1 was still occupied by old CM11 install so I deleted that. Installed the GSM patch and now the phone works as a charm.
So many thanks to this great community. I usually don't post at all. I use the search function and just follow the steps, but I panicked a bit today. Sorry.
Thread can be closed.
CyberBully said:
So many thanks to this great community. I usually don't post at all. I use the search function and just follow the steps, but I panicked a bit today.
Click to expand...
Click to collapse
Thanks for letting us know that you got things working. Someone else in the future will see this thread and be helped by it!