if I'm posted in the wrong spot please move me
wife's phone started acting weird. it's been on 4.1.2 for a long time. it was rooted but no BL unlocked.
so after trying numerous ways to fix it I decided to try and move to KK. so I defrosted all my bloat and the updater then accepted the first OTA. all worked great. then accepted the second OTA and it installed and was halfway through installing when it rebooted and then went to a more dim version of the same screen. open chested droid with spinning item inside. when it finally finished it rebooted to the Red M and will not go any further.
I can get into fastboot and I have pushed a few commands to see if it works but I cannot get it to allow me to do much else. I have RSD but it seems the device but doesn't show any information. tried to flash something via RSD and it says PHONE RETURNED FAIL
is there a way to get this phone back to some workable form? BL is locked.
===================================================
lots of reading.
it appears that with locked bootloader only signed official MOTO system and boot.img can be loaded thus the fails. downloaded official files
running RSD now and it's gone through 15/17 steps, now loading system for last few minutes.
fingers crossed....
Let us know what happens
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Got it working. Then had to redo it because I flashed 182 not 183. Then that meant I had to delete getvar, got it working and it's perfect EXCEPT WiFi sucks. It doesn't see or stay connected to access points that are best in house. Makes me want to Revert just for that.
Sent from my SCH-I535 using Tapatalk
dyskinesia said:
Got it working. Then had to redo it because I flashed 182 not 183. Then that meant I had to delete getvar, got it working and it's perfect EXCEPT WiFi sucks. It doesn't see or stay connected to access points that are best in house. Makes me want to Revert just for that.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
It's pretty easy to downgrade back to jb
Sent from my DROID RAZR M using XDA Premium 4 mobile app
Ultimately phone had h/w issues. So swapped for another just like it still on jb. Rooted and unlocked so golden.
Sent from my SM-G900V using Tapatalk
Related
i guess im going to call verizon with a bs reason i need a new phone. I have tried to update off nan from when i first rooted downloads but wont install dont understand sbfing and zip files wont load need serious help
What exactly is your phone doing right now? Is it stuck on the boot logo or what?
Its operational, I just flashed back to first nan and reloaded fission cause nothing I did the 928 back to stock ect worked, even tried updating without signing into google, unrooted and all that just frustrated it won't work
Sent from my DROIDX using XDA App
Ok, so you are up and running then. The only thing i was going to suggest is flashing SBF to get you back to Stock Android 2.2 and starting the process over again. I had a similar problem and wiped everything clean IOT get what i wanted. SBF'ing is simpler then you think, all you need is 2 files (rsdlite_4.8 and VRZ MB810_2.3.15 sbf). There's lots of articles here on it and I used them when I thought I bricked my phone. I started all over and was able to receive my 2.2.1 update.....finally!!
have you done the ota update? if so use 2.3.32.sbf you can get it by google and search droid x 2.3.32 sbf and its the first result. and dl rdlite 4.8. very easy to flash. several guides on here as stated.
I got it my drivers are up to date but won't find my phone.. And I'm leary all I got to do is that file and update?
Sent from my DROIDX using XDA App
Try running rsdlite as the administrator. (Right click rsdlite)
Now won't find it and I got a toshiba, only a little bit over a year old
Sent from my DROIDX using XDA App
EDIT - finally got rsd lite to recognize but first attempt failed trying again... pray
EDIT #2 - YEs, rebooted with 2.3.320 now to find 2.3.340 n flash it
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Bagel Bear said:
I'm concerned about rooting or modifying my Atrix a second time. My first Atrix that I had rooted stopped working when I tried to update the OS through the wi-fi download of the update. Mid-way through, the Android mascot and the exclamation sign came up and I had to pull the battery. When I rebooted the phone it said the modem failed to start up. I don't know the reason for it but I went to the store and used my insurance to get a fresh one. Since then, I have only sideloaded apps and now with the Gingerbread update I don't have to use a USB cord to install apps anymore. I'm afraid to try to root or modify my Atrix again.
Click to expand...
Click to collapse
Rooting should not have given you that problem. I've rooted numerous A4g's on froyo and they are all running GB fine after the ota. I also re-rooted them all now that they have GB. No issues. Also if your atrix didn't give you a boot error right when you turned it on you could have manually flashed a build and wouldn't have had to use you insurance.
Sent from my MB860 using XDA App
Alright, that eases my mind. Perhaps I just had some hardware failure.
How does rooting affect everything? Like you said, you are able to update via OTA when rooted and everything is fine. I also have a question about how to root exactly. I saw the sticky but it only mentioned the leaked release of Gingerblur and not the OTA version. Does the information still apply?
Its a little more involved if don't have your bootloader unlocked. Follow the post mramirezusa has about automatic unlocked bootloader and root.
Sent from my MB860 using XDA App
Be sure to read the instructions twice, then read it again for good measure!
Also check out the [HOWTO] Root after sbf flash thread in the dev section
Sent from my MB860 using XDA App
So here's the story. Bought a used Droid X from a guy at work. Phone was fine. Never rooted or anything related to root. So I decided to root it. Used ZergRush method I believe. Installed Bootstrap Recovery. Wife used Rom Toolbox to change several notification icons, boot animation and boot logo. Everything was great for awhile, but she got tired of it always booting into recovery. So I was going to un-root and return to stock. Ran the same ZergRush Un-root app. Then removed Bootstrap and all other root apps. Then found out wife accepted an OTA before I un-rooted. Well, at this point the phone still worked, and was un-rooted, but still rebooted into recovery, still had custom boot animation and logo as well. So she then reset phone to factory defaults. After that is when we had problems. Basically it wouldn't load past the boot logo. I just pulled the phone out from its hiding spot after a month or so to try and tackle it again. But now I think the battery is shot because it won't turn on period, whether plugged in or not, and the battery looks like its swollen. Has a huge bulge in the middle.
My question is, do you think the phone is able to work again? Cuz if not, I'm not buying a new battery.
Yeah it sounds like a bad battery now but before would it would just boot to the red m? If so an sbf would probably do the trick
Sent from my ADR6425LVW using Tapatalk 2
Ya before it would boot to the M and stay there, until I pulled the battery. So hopefully new battery and sbf and it will work?
Well yeah an sbf should do you just fine
Just be sure once you do the sbf you boot into stock recovery (vol down+home+power then vol up+down together when you see the !) And do a factory reset or you'll just have another headache
Sent from my ADR6425LVW using Tapatalk 2
Alright cool. Looks like I'll be finding a battery and having a whirl at this. Thanks for the replies
So i sbf'd the shadow 2.3.4 using rsd and it said it was completed and to manually boot the phone. So i did and it still stays at red m logo. Only difference is its now the red m where as before the sbf it was the pink Android my wife installed. So some progress I guess.
Any ideas? Try a different sbf file maybe?
Sent from my R800x using XDA
EDIT: Nvm, tried a different sbf and it works fine now.
I know you say it would boot into the M but could you get it to boot into recovery?
Don't remember if i tried actually lol. Its plain now, no root or bootstrap, but it works
Sent from my R800x using XDA
Kasper DG said:
Its plain now, no root or bootstrap, but it works
Click to expand...
Click to collapse
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Nate2 said:
Strange how DroidX phones eventually become stock and unrooted :^)
Sent from my unrooted DroidX using Tapatalk
Click to expand...
Click to collapse
Very strange indeed. Almost like I got the sbf to work or something
Sent from my R800x using XDA
Got this phone in a stupid trade after the bootloader opportunity had passed. Been running safestrap for awhile but wanted to play around with whatever stock its up to. Used Matts utility. Flashed 4.1.2. Rooted with chopper. Vooded to protect. Got the OTA. Failed. Tried again and used OTA grabber. Copied to computer. Tried to ADB Sideload. Started OK then bam! At least this way I got reason:
assert failed: apply_patch_check ("EMMC:boot:10485760:6c80d1f837bb3a127bc7aabd0164afd09e51475e:10485760:bbc1976c3cf2987f182a4747934ffb8d0f532fd8")
any suggestions?
Mcowan226 said:
Got this phone in a stupid trade after the bootloader opportunity had passed. Been running safestrap for awhile but wanted to play around with whatever stock its up to. Used Matts utility. Flashed 4.1.2. Rooted with chopper. Vooded to protect. Got the OTA. Failed. Tried again and used OTA grabber. Copied to computer. Tried to ADB Sideload. Started OK then bam! At least this way I got reason:
assert failed: apply_patch_check ("EMMC:boot:10485760:6c80d1f837bb3a127bc7aabd0164afd09e51475e:10485760:bbc1976c3cf2987f182a4747934ffb8d0f532fd8")
any suggestions?
Click to expand...
Click to collapse
Woaaahhh.
Premises are kinda wrong here. If you aren't on the latest version of stock, you *should* still be able to unlock. Have you tried to yet?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
Woaaahhh.
Premises are kinda wrong here. If you aren't on the latest version of stock, you *should* still be able to unlock. Have you tried to yet?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I wish it were that simple. Used the utility when I got the phone a couple months back. Screen shot of current system info attached.
Mcowan226 said:
I wish it were that simple. Used the utility when I got the phone a couple months back. Screen shot of current system info attached.
Click to expand...
Click to collapse
That should be unlockable. What was the exact result when you ran the unlocker?
Sent from my Nexus 7 using Tapatalk 4
sloosecannon said:
That should be unlockable. What was the exact result when you ran the unlocker?
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
I apologize for the delay in getting back to this thread Been caught up with other projects I have attempted a few times to unlock the bout loader through the utility however it always fails The inability to update with the ota as bbecome rather annoyin as it keeps asking
What's the date on your fast boot menu... I ask because if it is indeed unlockable I'd hate to say use this and do that and have this and that kill an opportunity for you
Sent from my XT907 using xda app-developers app
Short version: phone won't boot, won't go into download mode, won't properly do a factory reset (tries but doesn't do it), need help.
Finally bricked my phone after tampering with it too much.
I was on the stock KK rom released by LG themselves, no root. Reverted back to the 10c firmware, OTA to 10g, rooted and installed TWRP - flashed a Vodaphone Germany KK ROM for the LG G2 because I heard it had minimal bloatware and no bluetooth wakelock unlike the KK version I was on for T-Mobile (my carrier). It had the touchscreen issue which I never experienced before. Tried multiple times to go back to any T-Mobile LG G2 ROM using the LG Mobile Support Tool - no dice. Uninstalled and reinstalled everything twice. So I figured, oh hey, I probably need to use the Vodaphone Germany JB.kdz file, root that, install TWRP, then flash back to the T-Mobile KK version that I had before. Seemed fool proof in theory. Used the LG Tool to do such, it finished smoothly and now my phone won't boot. It won't do a factory reset (it enters the factory reset mode and it attempts to do one but just reboots). It won't enter download mode either. I think I'm screwed here. Any advice?
I found 2 guides, but to even begin to do the first one I need my phone to enter fastboot mode and I can't find out how to do that anywhere.
you say Won't go into download mode? What happens when you try?
It just shows the first screen as it tries to enter download mode, with the blue dots. The screen that comes after that doesn't happen anymore. It used to switch to it after a few seconds and then the LG Mobile Support Tool could connect to the phone, but it can't anymore.
Sent from my SGH-T989 using xda app-developers app
your phone may be was hard brick, can't do anything
Mine did that once. I complely powered it off and left it alone for 20 minutes and it suddenly worked. Freaked me out
This is what you need http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my LG-D801 using xda app-developers app when I bricked mine I had to get a new 1
I'm nervous to try that. I have no experience with ubuntu. But I'll give it a go tonight
Sent from my SGH-T989 using xda app-developers app
CHlCKEN said:
Sent from my LG-D801 using xda app-developers app when I bricked mine I had to get a new 1
Click to expand...
Click to collapse
would you PLEASE fix your posts so the signature is at the bottom?
The same thing is happening to my ls980. I'm certain it's hard bricked. Download mode shows on the screen but won't boot into firmware upgrade screen. No recovery at all. Os will not completely boot but does show on pc as LG modem. Think it's totally done for. Let me know if you make any progress because we both have the same problem.
Sent from my XT1058 using Tapatalk
Gonna try what offenberg suggested in a few hours. Fingers crossed
Sent from my SGH-T989 using xda app-developers app
uToTMeH8 said:
The same thing is happening to my ls980. I'm certain it's hard bricked. Download mode shows on the screen but won't boot into firmware upgrade screen. No recovery at all. Os will not completely boot but does show on pc as LG modem. Think it's totally done for. Let me know if you make any progress because we both have the same problem.
Sent from my XT1058 using Tapatalk
Click to expand...
Click to collapse
Didn't work for me. Windows and Ubuntu didn't recognize my phone. I actually ended up ****ing up my laptop by overwriting a partition but that's on me.
Decided to take it in to a T-Mobile store and blame it on the Kit Kat OTA. It turns on, doesn't boot, doesn't factory reset, doesn't fully go into download mode - how are they gonna know I ****ed it up? I have basic insurance on my plan because the JUMP program is tied into it. So for a little over $10 a month I just gained access to a warranty exchange of my device which is set to ship overnight. Can't wait. Huge stress reliever. I advise you take your phone into your carrier store and do the same as I did.
Sent from my SGH-T989 using xda app-developers app
ducidni said:
Didn't work for me. Windows and Ubuntu didn't recognize my phone. I actually ended up ****ing up my laptop by overwriting a partition but that's on me.
Decided to take it in to a T-Mobile store and blame it on the Kit Kat OTA. It turns on, doesn't boot, doesn't factory reset, doesn't fully go into download mode - how are they gonna know I ****ed it up? I have basic insurance on my plan because the JUMP program is tied into it. So for a little over a month I just gained access to a warranty exchange of my device which is set to ship overnight. Can't wait. Huge stress reliever. I advise you take your phone into your carrier store and do the same as I did.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
So did they fix it for you under warranty?
or they figure out that you root it and play with it !?
because I'm having the same problem with my f320k and I'm thinking to send it back to Korea
Same is the case with me, my phone is dead for more than 20 days.
here are the details if any one can help?