My RAZR MAXX has been working just fine, even after travel to Germany (connected to Vodaphone just fine). I have the phone in the Bahamas and it has a Batelco SIM in it. It handled voice calls as expected. Yesterday, I bought a data access package as my original package had expire. Installing the package required having a Batelco rep enter the needed APN data. After that, the phone worked well for 24+ hours with the data and voice networks. The wheels fell off when I powered down the phone.
On powering the phone back up, it does the opening red Motorola logo, the opening animatation with full audio, and then goes into the "dancing sparks" animation. And that's where it stays. It's been running in this mode for over 30 minutes since I last tried to power the phone down to pull the SIM and SD card ([/shug] might as well try that). Actually, at this point, the phone seems to be reluctant to power down (holding the upper button down may or may not lead to powering down and even if that happens, the phone just starts to reboot instead of staying dark). Soft reset only stops the "sparky" animation and then the phone reverts to the "M" logo and animation again and again and again and...
The OS is an OTA Jelly Bean supplied by Verizon (can read the detail rev numbers of course). The only recent changes I can point to are some pushed app updates (Firefox, Facebook, and I forget the third) and the entry of the Batelco APN.
So the question is this: is there any way to give the phone a good swift kick to break this cycle. If not, how do I get the OEM ROM for this thing?
Please keep in mind that I'm in the Bahamas, where surface mail can take 4-5 weeks to arrive. Plan B is to have stuff air freighted in (costs are astonomical and Bahamian customs may want a piece of the action). Bottom line: external hardware is almost impossible here.
In doing more reading on the problem, I found out about getting into the boot menu (power down, hold power, vol up, and vol down). I can get to the menu. I selected recovery and... nada. After a while the phone just boots yet again. Either I don't know how to enforce the recovery choice or the phone is really boogered. BTW, the phone does accept charging. That is, it was dead (blank screen) after looping overnight. Plug in the charger and back to looping, which continues with the charger not plugged in.
Nevermind - I got to recover mode. Helps to read the instructions fully...
You can try using this: http://www.droidrzr.com/index.php/t...ndows-mac-linux-all-in-one/page-9#entry251858
But that would delete all your apps and stuff. but it also might fix your problem.
The fun just won't stop. I wiped the cache and rebooted. No change. I went for the full FDR and rebooted. No change. This is one sick puppy...
Gus194 said:
You can try using this [deleted]
But that would delete all your apps and stuff. but it also might fix your problem.
Click to expand...
Click to collapse
Went there, tried that, and couldn't down load the file to successfully. I tried two mirrors and nothing (7zip said "not archives"). I also tried the file from RootJunk's download page (I'd post the URL but it's being blocked while I'm a noob).
That tanked, too.
I keep seeing references to an ADB Motorola JB ROM but can't seem to find it via Google. The idea is to just stuff the proper ROM in and get on with it. since all the user data was smoked in trying to reset the phone, losing user data is the least of my concerns.
Suggestions on this avenue of approach?
Have you tried downloading here? http://batakang.com/dr_utility.php
Gus194 said:
Have you tried downloading here? http://batakang.com/dr_utility.php
Click to expand...
Click to collapse
Thanks - I'll check it out. I finally(!!!) successfully downloaded DROID_RAZR_Utility_Jellybean_XT912_WinMacLin from RootJunky and will be trying it ASAP.
Great! Tell me how it goes?
Gus194 said:
Great! Tell me how it goes?
Click to expand...
Click to collapse
So far, it goes down the tubes. I successfully expanded the file onto the admin desktop. The next step is to get the correct ADB drivers installed. That tanks with an error message, from the installer, about a network failure to read the .msi file with the updates. Network failure??? The file's on the machine and I'm in admin, not user, space. ARGHHH!!!
Try getting the Drivers from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Gus194 said:
Try getting the Drivers from here: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
I got past the driver problem by using the installer to remove the existing drivers (no clues as to their rev. number but they went away) and then install the new drivers. I've actually gotten to the point reloading the phone but... now the darn thing says I have no SIM installed. In fact I have two, a Batelco SIM and a VZW SIM. I tried both and all the darn phone says is "I can find no SIM". In fact, I used the Batelcom SIM in a RAZR flip phone to verify all is well with the SIM. And it is. But the RAZR MAXX won't see it. GNGHHH!!!
RBEmerson said:
So far, it goes down the tubes. I successfully expanded the file onto the admin desktop. The next step is to get the correct ADB drivers installed. That tanks with an error message, from the installer, about a network failure to read the .msi file with the updates. Network failure??? The file's on the machine and I'm in admin, not user, space. ARGHHH!!!
Click to expand...
Click to collapse
The driver issue was fixed by removing the existing driver (no idea which rev. was present in the PC but it went away as it should) and installing the new driver. Why the network message showed up is unclear but it didn't happen after removing the existing driver.
DROID_RAZR_Utility_Jellybean_XT912_WinMacLin took two tries to run properly but it did run. The boot loop is stopped at last. But...
Now the phone reports it can't find the SIM. I have two SIM's - a VZW SIM (worked in the US and Germany) and a Batelco SIM. The Batelco SIM worked prior to the failure and it still works in a RAZR flip phone.
The boot process runs as expected and ends in the starting screen for the setup process. At this point the battery and signal (none - of course) icons show up. A couple of seconds later, the SIM icon shows up with a slashed red circle on it. Advancing to the next screen gives a "SIM not found" and the only option is to power down.
Popping the SIM out and in does nothing. Trying to boot to safe mode does nothing. ARGHHH!!!
Try going into recovery and factory reset.
Or I could try taking my head out of my a**. The SIM was in the wrong side up. Something I cleverly repeated over and over. [/ rolled eyes]
At this point I'm back to what appears to be a factory original RAZR MAXX with JB.
Great thanks for all the help on this project!!
Good to hear!
At the moment I'm using EasyTether to connect with the interwebs and post this note. Case closed, I'd say. )
Related
Hey all,
I did my searching for the last several hours, and am feeling pretty weak. I know there are several other posts with this error - but please let me explain my situation.
Phone was running 2.3.6. I am unsure how it was originally unlocked (carrier unlocked) and bought it used. To my knowledge it did not have root access... (though the advert said it did - running SU in Terminal to show if it had access failed)
I tried doing a factory reset on the phone because it kept acting weird. Just rebooting 10 times a day, and wifi not working either.
Since the reset the phone has not made it past the M Dual Core screen.
Edit as I type: As I type this, I FINALLY got into recovery mode. It took a long time... is that normal? I mean.. loongggg. Now i see other posts state I just need to click the bottom right corner above the search key and I should be on the way to recovering the device...
This however is not working...
I will keep the phone plugged in over night and see if it just needed more time I suppose. Can you guys recommend anything?
I am on win7 - should have the device drivers installed (though, Windows doesn't seem to recognize this with a notification bubble). I know the phone was not on USB Debug Mode when I clicked 'factory reset'.. would it have retained this?
I will update as i have more information.. otherwise if I am missing something please let me know.
Thanks again,
-k
Try booting into recovery mode by holding volume down while turning on. When the menu appears keep pressing volume down until it says android recovery and then press volume up to select it. If an android Guy with a warning sign shows up, press volume down and up. A menu should appear soon. Try to do a data wipe and factory reset from there.
Sent from my MB860 using XDA App
Hi ar31791, thank you for the reply.
That worked to put me into a recovery mode - very nice. Is the button combo different depending on the version of android your'e running, or just phone dependent? I appreciate that.
Couple follow up questions if you guys don't mind and can help
- after the factory reset - my boot time is incredibly slow.... like 30 minutes to boot kinda thing. I tried to factory reset several times since, and its the same issue.
- my data is not working on the phone. I used the apn suggestions from all sites I've found, rebooted (took a while) tried data roaming, etc, but it just doesn't work. I have a decent idea that the apn's are correct because the mms apn worked fine with a test picture message.
My main concern is the incredible lengthy boot time and the data no longer working. The issue with wifi still showing 'error' when enabling it was not resolved by the reset (I didn't think it would - I was reading other posts where it is suspected as a hardware issue).
Thanks again for the reads, and replies. I appreciate the help!
-kenny
You need romracers or cwm. Unless yer going to stay stock.
Sent from my MB860 using xda premium
Is this an att or a rogers/international phone? Best bet would be to flash pudding and than cwm + custom roms
hey again- thank you for the replies.. seriously. much appreciated.
phalanx, i dont mind staying stock but would that not allow the data connection to work correctly? i found a few posts based on the romracer. i lack the hands on experience, but it looks like i just need to follow the steps for an adb push and then install eh?
you mention staying stock, is that an option? info on my setup below
crnkoj, i am running a bell phone on a fido network in canada. bought on ebay pre unlocked. i do not bekieve it is rooted. phone, mms and text work fine, it seems to be a problem finding a data network at this moment.
thanks again guys, ill be taking a look into the tutorials for romracer and cwm, and giver a shot. lemme know if you have any further ideas, questions or anything you think i might need to know.
edit.. also, whats the deal with the crazyyyyy long boot up time?
kenny
(send from a mobile.. please excuse any typos or punctuation errors)
No its just that with an unlocked bootloader you can flash a new.recovery and that makes it easier to flash roms and also kernels and radios. Kernels and radios can affect your ability to connect with data and can even affect the speeds.
Sent from my MB860 using xda premium
I had a similar situation. So, i did a full wipe installed the rom did another full wipe then installed the appropriate kernel and booted it up. I believe you nedd to install the right kernel per the instructions. It will mot boot if the kernel is not correct.
Sent from my MB860 using xda premium
Thanks again guys,
Man it's a funny issue. I am always able to get in and factory wipe the device, but it seems that sometimes that damn M screen will sit forever. I left it over the course of a movie and a half (probably 3 hours) and that screen was still just sitting there.
I get into the fastboot menu easy enough before that screen hangs, and sometimes i can get into the Boot Android (without BP) (I believe it's called) and sometimes it hangs, and sometimes it works.
Other times, like right now, it boots just fine and kinda fast.
I am having an issue with the RSDLite application recognizing my phone. It did once - then hung at 94% flash of the pudding tutorial. I didn't realize the tutorial says to keep the phone plugged in for 10 minutes even after a fail to see if it actually completes. I havent been able to have the software recognize the phone since- I've installed and reinstalled the motorola drivers, set the phone to usb debugging, and was able to try 2 computers, and 2 different cables. I'll giver another shot though.
I am pretty sure my boot loader was unlocked (as I said I had this all done from an ebay purchase) so I think I can just proceed to the flashing, but if there is a way to confirm that it is indeed locked, I'll take the advice.
The more I read though, it looks like I might just need to send this beast in for a service call with Motorola, because of that damn wifi "error" error. I'd hate to go through all this and realize it still will not work.
Thanks for the replies, I'll always take more suggestions, and if you guys think I'm on the wrong path, let me know. I'll keep searchin dem' forums
If your bootloader is unlocked it will say unlocked in white letters on that M boot logo screen. Did you run "fastboot oem unlock" after the rsd flash?
Sent from my MB860 using XDA App
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.
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
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
AddictedToGlass said:
Welp,
I've gone & done it again. My 2nd z3v came from Amazon a few days ago, refurbished, like new. Got the 200GB card for it, went to Verizon & got the SIM, swapped it with my work phone (iPhone 4s) line.
(Now I have 2. But the 1st one was replaced for being in this same situation.)
Got home, swapped the phones back cause I really still wasn't sure I wanted to mess up this z3v with my job (landscaping = lots of dirt).
It had 4.4.4, and I let it update to the latest two part Lollipop to see what the hubbub was about (nothing).
Decided I wanted to make it basically a clone of my primary z3v, so I rooted from the update directly using GigaSPXs guide.
Successful rooted 509 achieved, but with one problem; it kept telling me I had no space left, even though the internal SD had 21 GB left. Peculiar.
Made a recovery file on my #1 z3v's SD. Copied everything from #1 SD to #2 SD, and attempted to "clone" #2 z3v by installing that latest zip copied from z3v #1, but Recovery kept saying "No File Found".
Checked all 5 recovery points I had on there, and each said the same thing. Checked other things on the SD card, and it showed them, but when I tried to open them, it said "No File Found".
Mounting problem? Made sure everything was mounted, etc. Still, same problem.
Tried wiping Dalvik 3 times, but also accidentally wiped System Cache.
Now it sticks at the SONY Xperia logo. I can get to the Sony Recovery options, but Factory Reset doesn't do anything.
Was it System Cache wipe that killed it, and can anything be done?
This time, I took some notes as I went. I was confident, but I've done this before (bricked), so I decided to list what I did as I went along. I highly recommend everyone take notes for when they screw up. LOL!
Click to expand...
Click to collapse
Use Flashtool to flash it back to 4.4.4. After that, don't try to do your attempt again. They're two separate devices and they are both uniquely different internally.
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
AddictedToGlass said:
OK, how do I use flashtool? The PC doesn't recognize the phone as anything hooked up to it. Flashtool doesn't recognize it's there.
Click to expand...
Click to collapse
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
GigaSPX said:
IIRC, hold down the down (or up) button and hook the phone to the computer. I think it should trigger recognition from there.
Click to expand...
Click to collapse
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Komet1 said:
If that doesn't work and you have connected your phone to your computer before try removing all related Sony drivers from the computer. If you are OK with registry edits you could look for any instances of your phone there too.
Click to expand...
Click to collapse
Don't I need the drivers installed?
Yes,, reinstall them preferably from outside your computer. You are wanting the drivers on your computer to be overwritten by fresh drivers, even if they have the same version numbers. You want the computer to "think" this is the first time the phone has ever been connected to it.
Where do I get th drivers for re-installation?
AddictedToGlass said:
Where do I get th drivers for re-installation?
Click to expand...
Click to collapse
Try this. If you do take this route don't be discouraged if it doesn't work the first time. I have had something similar happen and on occasion it has taken a few tries. Windows doesn't like to let go of drivers that are already installed.
Xperia Z3 drivers
"Phone driver for Xperia Z3 (D6603, D6616, D6653, D6643, SOL26, D6708, SO-01G, and 401SO) (Microsoft Windows™ XP 32bit/64bit and later). Use drivers for debugging, or when erased from phone."
DLed the replacement drivers, but Flashtool isn't recognizing the z3v. I know I'm doing something wrong because it isn't recognizing my other (functioning) z3v, either.
So I Googled driver installation on Windows 8.1 because I remembered that it won't allow unsigned drivers without manual installation, and I needed a refresher course for all the steps. I am uncertain I successfully removed all of the previous ones, though. What I did find out, but did not know, was that putting 8.1 into that mode (where it'll install unsigned drivers) is a temporary situation. According to a poster on a blog (for whatever that's worth...), once the PC is restarted, it comes out of that "test mode", and unsigned drivers no longer work again. I usually keep the PC on, but it has restarted since I last messed with Flashtool.
Obviously I need to figure out where I'm going wrong on this to even begin work on the phone. (I miss XP.)
Details about the z3v behavior:
The screen is stuck on the SONY XPERIA logo.
Pressing the power button by itself has no effect, no matter how long I hold it.
Pressing the power button with the volume down will power it off, but it just powers back on by itself.
Pressing the power button and holding both the power button and the volume down while it cycles back on gets me into the Android Recovery menu.
From Recovery;
Selecting "Power Down" USUALLY powers it down, but sometimes it immediately restarts.
Selecting "Factory Reset" cycles it through the logo and into an attempt (Droid animation with blue bar rolling) for about 5-6 seconds, and then it restarts into the SONY XPERIA logo again.
Selecting "Safe Mode" simply restarts it the same way.
Selecting "Continue Power Up" obviously does the same.
All that is while not tethered to the PC. NO color LED comes on, except for an occasional orange while it's hooked to the PC.
Got a couple of suggestions about the PC connection:
Try a different USB cable.
Have you looked in Device Manager and removed any reference to the Sony there as well?
Here is a blog post about an Xperia S that wouldn't connect, the steps should be the same:
Connect the phone via USB and go to the Device manager on the computer. Check if you can locate the phone or any Unknown/New device that could be the phone or if you perhaps see the phone as a device. Right click it and select to uninstall.
Still in Device manager open the list for USB controllers (Universal Serial Bus Controllers) and right click each one of these controllers and select to uninstall.
When all of this is done reboot your computer and before connecting your phone again repeat step 2.
You should of course not have to do this every time you connect your phone to your computer but hopefully this could remove any error causing your phone not to connect properly.
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things.
Komet1, your suggestion of trying a different cable struck me as desperate, but when I looked at what I had been using, I realized it was the cheap cable Amazon sent with the phone (It didn't come with a Sony charger and cable, just a crappy generic set).
I swapped cables and viola!, I now have 4.4.4 back.
I'll not be making the stupid mistake of swapping restores from one phone to another again.
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
AddictedToGlass said:
I'M BACK!!!
And here's a lesson from one noob to all others; Never overlook the simplest things...
Thanks all!
Important lessons for beginners...
Take notes. I'm glad I did this time because last time I bricked I couldn't remember what I had done to brick it, or what I had tried to unbrick it. It helps when you can provide detailed info, otherwise it becomes too frustrating for those who can help. It can also help keep you from panicking and going in circles.
Click to expand...
Click to collapse
Awesome! Been there, done that with the bricking. It's a wonderful feeling when you watch the phone respond and realize you just solved the problem.
Sure is!
DOH!!!!