Related
i've read almost every single post related on this subject, tried almost everything but no go.
recently, i installed SS-6 to my girlfriend's Vibrant but she didn't like it, so i attempted to revert to my nandroid from the original stock rom.. nandroid gave an MD5 error and did not installed.
at that point, i had already wiped data/cache, prior to nandroid.
i rebooted the phone, and now im stuck on the Vibrant splash.
i have tried to go to recovery mode via hard buttons but no go. i actually tested with another Vibrant and on that one, im able to get into recovery so it is not that i'm missing pressing a button or what not. been trying anxiously to see if im able to go either to download mode or get into cwm and flash cyanogenmod!
tried to use ODIN/ADB in order to boot into cwm to flash another rom, but it doesn't see the phone. ive already installed samsung drivers.
if i connect the charger, the battery indicator doesnt come up. it stays on that lined-circle screen forever, even after taking the USB cable out.
please help!
EDIT: added [Q] and added some more grammar errors.
any help is highly appreciated.
I had this same problem... The only thing that would fix it was this thing I had to buy called a Jig. It was less than $8 (with free shipping) on eBay.
http://www.ebay.com/itm/Fix-Download-Mode-USB-Jig-Samsung-Captivate-Galaxy-S-/140520601309
It delivered in 2 days and my phone is working perfectly now
just ordered one!
thanks!
one more thing, are you able to just install a different ROM through ODIN or ADB without having to do the full wipe? im wanting to save the contents of the internal SD.
thanks again
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
Can you install the Rom "The base .5". I assume so if you can get to cwm. I had this problem when flashing this Rom The first time. It did the same thing with the LG logo then go black. If that happens just reboot to cwm(May take awhile) and reflash "the base" again. That should allow it to boot the phone fully so you can at least use it till you can get all the way back to stock. I hope this helps. I have to crash now tho. I'll check back in the morning to see how it's going.
Sent from my UNLOCKED LG-E970 using xda premium
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Cat Rancher said:
Hey all, this is my first android and I'm not the smartest sometimes. I tried restoring back to factory rom, and watched a bad how to vid. Basically i cleared data, system, cache and now realize i shouldn't have.
I'm not able to connect to the phone through usb. I have the drivers, but I can't see the phone.I can boot into cwm, and that is it. When i start it, it basically pulls up the LG screen, then a black screen.
I have a backup on cwm but get the md5 error.
Is it possible to put the sd card in my computer and download what i need straight to the card? Im also not sure what i need to download, if that does work.
Please let me know if there is any other info I can provide. Like i said im not the smartest sometimes, so dont be afraid to respond like im slow.
Click to expand...
Click to collapse
The recovery won't generate a md5 sum (known bug). You have to generate it yourself. Connect your phone to adb and go to #4 in the FAQ here.http://forum.xda-developers.com/showthread.php?t=2006946
Note that there is no way to tell of the backup is corrupt since you are generating a valid code regardless of integrity.
Sent from my LG-E970 using xda premium
Murasakiii said:
Are you trying to get back to factory settings or just get your phone running with the stock rom?
You should be able to just put the ROM on your sd card via computer if you have an SD card sleeve.
If you wiped your phone, it's my understanding that you're not supposed to when flashing the provided rom in development.
There's a posting in development, I believe, about restoring your phone to stock if you messed it up. LGNST or something.
Click to expand...
Click to collapse
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Cat Rancher said:
I tried re-installing .4 base which is what I had originally used. It let me choose the apps to instal, and made it to the "X" screen, but appeared to be stuck in a boot loop. I am going to try and download and install .5 via the sd card and see if that works. I'm not sure if LGNPST will work since I can't see the phone via usb. I will download it and give it a try though.
I also saw the guide in the general Optimus G forums for unbricking it.
http://forum.xda-developers.com/showthread.php?t=2010624
Since i cant really connect via usb, ill probably have to use a different method. Im hoping the usb issue is due to the computer im using and the original computer i used to root and unlock will work.
Click to expand...
Click to collapse
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
adfurgerson said:
The method in that link is for phones that don't have official firmware to use with lgnspt. If you san get into download mode (power off phone ,connect usb,hold volume down and up plus power ) you should be able to lgnpst back to stock.
Click to expand...
Click to collapse
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other necessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
You need to go to the IRC channel to grab the new version of lgnpst and the correct files.
Sent from my LG-E970 using xda premium
Cat Rancher said:
Alright. I was able to get into download mode. I downloaded lgnpst. Do you have an idea where i would find the other Didnecessary files? Again, total noob. Sorry for all the hand holding. You guys have been great!
Click to expand...
Click to collapse
Did you get your phone straightened out?
adfurgerson said:
Did you get your phone straightened out?
Click to expand...
Click to collapse
I'm traveling for work and on a work computer, so the IRC channel is blocked. Of course. I'm heading home tomorrow so hopefully I can get everything back to normal when i get on my home computer. (not having a phone sucks)
Do you all think it would be worth putting the base .5 on my sd card and flashing that, or do you think that wouldnt work? .4 is on there now from my original flash, but that won't work. Just curious.
Well is your phone up and running?
I would think it wouldn't cause harm to try and flash .5 onto it, your phone shouldn't get bricked from it.
i agree with Murasakiii
should be fine to run .5
DraginMagik said:
i agree with Murasakiii
should be fine to run .5
Click to expand...
Click to collapse
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
i'd say the device started having issues with the USB. unable to see the device when plugged into the computer and the device won't take a charge. don't hear of too many authentic "bricking's" anymore...it can almost always be resurrected. but if the device won't take a charge your time to resolution is rather limited. good luck.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
Before you leave to go to the store hook it up to a set up jumper cables and then attach the other end to your car battery. Then just tell them when you tried to charge it that it started smoking and wont turn on any more.
The only lie you have to tell them is it happened on the stock charger.
Im on the same boat. Tried going back to stock for a warranty return, and i ended up bricking the phone. Im able to get it to download mode and was able to run the lg tool but it keeps failing on me. And when it does complete it still wont load. Im going to try to make my self a powerd usb cable too see if i can get it to work. Have like 2 or 3 days to try to figure it out. Or elese im out 550 bucks.
Sent from my LG-E970 using xda app-developers app
Other option is just telling them you clicked install for the ota update it rebooted and never came back on. They just wipe them at the repair center anyway if they get them to boot up.
Cat Rancher said:
Welp, I think i earned the title of first bricked phone. It was able to get into recovery and download mode a couple days ago, but now it wont charge it seems. So i cant get it into any mode to do anything. Ive had it on the charger, wall and usb for a couple hours and nothing is happening. I wonder if i can take it back to my att store and try get a replacement. It is within my 14 day window, and there are "hardware" warranties. I have a feeling they will ask what happened and while i may not initially divulge everything, i sadly cant lie. And since its all my fault, i may chalk it up to learning.
Click to expand...
Click to collapse
It took 12 hrs to get a clean download of the stock ROM (AT&T internet sucks in my area). The entire time the screen on my phone was on with the LG splash screen displayed. By the time I got the ROM ready for flash, the battery was dead. I was however able to plug in to the USB on my computer and get enough juice to get into download mode. Ran LGNPST (v2.2.3) and the stock ROM installed with no prob. You might try plugging it in then trying to get into download mode.
EDIT: now that I think about it. You need to have it plugged in to the USB before download mode anyway, so you won't be doing anything different than you already did.
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD
So here's the story. I'm kind of terrified right now that my phone might be a goner. So, I was wanting to apply the new update to my galaxy but everytime I tried it would say "error" and wouldn't work. So I removed my root via superSU hoping that might help, with no success. So the nice people on this forum were directing me to flash a stock rom through odin to my phone. I kept trying and trying and my phone would never get recognized by odin so nothing would happen. I tried everything that I could read online to fix it and it never did. So I just decided that I would boot to recovery and do a clean wipe of my phone after I back it up. well the backup didn't work, so I just took my SD card out since it had most of the stuff I wanted to keep. I tried the clean wipe and it was done really quickly. I started up the phone and after I selected my language it said the setup wizard was stopped. Since then, I can't get the phone to boot correctly. It gets past the verizon splash screen(after a way longer wait than normal) and says "com.samsung.(something) has stopped working" and then just reboots itself. It'l almost stuck in this endless cycle. Can anyone help me out? If not, just give me the bad news straight up, do I need to trash this phone? Did I successfully kill it on accident?
GAMECOCK1801 said:
So here's the story. I'm kind of terrified right now that my phone might be a goner. So, I was wanting to apply the new update to my galaxy but everytime I tried it would say "error" and wouldn't work. So I removed my root via superSU hoping that might help, with no success. So the nice people on this forum were directing me to flash a stock rom through odin to my phone. I kept trying and trying and my phone would never get recognized by odin so nothing would happen. I tried everything that I could read online to fix it and it never did. So I just decided that I would boot to recovery and do a clean wipe of my phone after I back it up. well the backup didn't work, so I just took my SD card out since it had most of the stuff I wanted to keep. I tried the clean wipe and it was done really quickly. I started up the phone and after I selected my language it said the setup wizard was stopped. Since then, I can't get the phone to boot correctly. It gets past the verizon splash screen(after a way longer wait than normal) and says "com.samsung.(something) has stopped working" and then just reboots itself. It'l almost stuck in this endless cycle. Can anyone help me out? If not, just give me the bad news straight up, do I need to trash this phone? Did I successfully kill it on accident?
Click to expand...
Click to collapse
Restoring this is going to be fairly easy once you get ODIN working.
First, make sure that Kies isn't running. Kies and ODIN will conflict with each other.
Normally issues with ODIN are fixed by ensuring that the cable is good, trying different USB ports, uninstalling and reinstalling the drivers.
If nothing works and you can't get ODIN to work, you might be able to use the Verizon Recovery Assistant or Kies to restore your phone to factory.
k1mu said:
Restoring this is going to be fairly easy once you get ODIN working.
First, make sure that Kies isn't running. Kies and ODIN will conflict with each other.
Normally issues with ODIN are fixed by ensuring that the cable is good, trying different USB ports, uninstalling and reinstalling the drivers.
If nothing works and you can't get ODIN to work, you might be able to use the Verizon Recovery Assistant or Kies to restore your phone to factory.
Click to expand...
Click to collapse
I'm going to try it on another computer. Hopefully it'll work!
k1mu said:
Restoring this is going to be fairly easy once you get ODIN working.
First, make sure that Kies isn't running. Kies and ODIN will conflict with each other.
Normally issues with ODIN are fixed by ensuring that the cable is good, trying different USB ports, uninstalling and reinstalling the drivers.
If nothing works and you can't get ODIN to work, you might be able to use the Verizon Recovery Assistant or Kies to restore your phone to factory.
Click to expand...
Click to collapse
This seems to have worked! Thank you so much for your suggestion, you really made my whole week now. I seriously appreciate it!
As the topic reads, I've been trying most of the day to unlock the bootloader, I went through the process of obtaining my unlock code and my phone status when typing out a code suggested that it allows unlocking of the bootloader - I'm thinking okay cool, hopefully I'll have Cyanogenmod 12.1 on this thing in no time, right? WRONG! The device needs me to download and install fastboot drivers, which I thought should be an easy process but no matter what I do when I look at my phone through the device manager all I see is 'S1Boot Fastboot' - I even attempted using Flashtool (not Emma) and it too says install failed when trying to download the files needed. I just really need some help getting through this part of the problem, I've downloaded the SDK downloaded the USB drivers, updated them with the file from Sony but the end result remains the same. If it makes any difference (which I'm sure it will) I'm on Windows 10.
Thanks for any and all replies .. Edit // I forgot to mention the model is C833 and I recieved the latest OTA update from Sony for Lollipop 5.1.1
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Klaos3000 said:
Installing the SDK is quite the overkill.
- Install ADB and Fastboot by downloading and running this tiny installer. It'll do the job for you.
- Install Flashtool and be sure that it recognizes your device. The device should be powered on when you open Flashtool the first time.
- Click the "BLU" button and copy/paste the unlock code you received from Sony.
You're done
Be sure to backup important stuff on your phone, in case something goes wrong. Move photos etc. to your SD card or something.
Click to expand...
Click to collapse
I appreciate the reply, and I managed to get the bootloader unlocked (I think) as both ADB and Fastboot are acknowledging my phone now. Problem I have now is while in Cyanogen Recovery, I hit the first option and may have soft bricked this phone - the cyanogen wiki stated I could make a backup by booting back into Android which is what I tried to do. I'm in the process now of repairing it with the PC companion hopefully and then I'll give it another go, this isn't my main phone though so basically I'm just tinkering/trying to learn the basics of installing custom ROMs. Thanks again for the reply, and if you have any other suggestions for me be sure to leave em here. BTW, I never installed the full Android Studio, just the zip file for the ADB and Fastboot files, I attempted that at first but found out you didn't really need em in the first place.
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Klaos3000 said:
The CM Recovery is... pretty crappy, so don't use it if you don't have to. If you soft brick it (i.e end up in a bootloop or something), then just flash or hotboot a kernel with recovery, and you're good to go again, so you don't have to re-flash a ROM.
You can either use fastboot to flash a kernel (if you know how to use a terminal), or you can use Flashtool, QuickIMG etc, so:
Soft brick?
- Download a custom kernel with recovery. Doesn't matter which one if you're planning to flash a ROM straight away. You're planning to flash CM12.1, so you can use a random Ultra kernel like this one.
- Let's say we'll use Flashtool to flash it (since you already have it installed). Open it, hit the lightning bolt, click "fastboot", and then "kernel". Browse and choose the kernel you downloaded. Now disconnect from the computer and remember to press VOL up to enter recovery when it vibrates or the LED lights up.
- You're now in recovery again and you can go ahead and flash CM12.1. Remember to WIPE before or after you've flashed CM12.1. You'll end up with a bootloop if you don't do it. If you do, flash that kernel again and you're back on track.
Click to expand...
Click to collapse
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
D2084 said:
Gonna give all this a shot since the PC companion doesn't seem to be doing anything - I'll post my findings in a few if you're around. Thanks again man, I really appreciate your help.
Edit // Okay, nothing seems to be working now .. Flashtool says that my device has USB Debugging disabled, and whenever I power on the device you see the Sony logo, then a violet led and then the screen stays on and every once in a while it'll show a small battery indicator.
Click to expand...
Click to collapse
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Klaos3000 said:
Hmm, plug in the wall charger and charge it for a bit. I highly doubt that it's hardbricked since that's very very hard to achieve on a Sony device. Just kick it into fastboot by holding VOL UP while you plug it into your computer. The blue LED will light up. Then open Flashtool and flash the kernel, or download QuickIMG and flash the kernel (.img) with it. Be sure that it says "connected" before you do anything. Keep also in mind that you have to be in fastboot.
Click to expand...
Click to collapse
I seem to have a brand new issue now, umm whenever I unplug the device and press VOL UP, I get this distorted screen. It's blue and has what looks to be white wording in the middle, I can't make it out though, this is after I put the kernel you recommended on my device. The kernel is the IMG file, correct?
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
D2084 said:
Just thought I'd give you a bit of an update, I now have Cyanogenmod 12.1 on my Xperia Z Ultra - I flashed the custom recovery that came with the nightly I downloaded and then moved the actual zip to an SD card since like you said Cyanogen Recovery is a bit wonky (I tried sideloading to no avail). I have a couple question though, during the install process I noticed it said something about there 'no such volume' and I was sure I seen two failed prompts too but the ROM is on my phone? Should I look into that at all or is it fine? Most things seem to work .. camera, bluetooth, gonna have to throw my sim in there one of these days and test the cellular radios, but I just wanna say thanks again .. I learned a lot and managed to make something happen even if it's something small like installing a custom rom lol
Click to expand...
Click to collapse
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Klaos3000 said:
Just ignore that error. I've seen that myself a couple of times, and I don't know what it means, but it doesn't seem to affect anything.
There are a couple of things to keep in mind. CM12.1 has had some glitchy WiFi in the past, and I believe some people are still experiencing issues, so if you also experience some WiFi issues, it's a CM issue and not a hardware issue. Also, keep in mind that the Ultra GPe (Togari GPe) exists and is also supported by Cyanogen, so be sure to not flash the wrong version since the partitions are different between those two. I believe the recovery system will stop you from flashing it though.
Since Sony devices do not have a default recovery system, we have to bundle it with the kernel, so all custom ROMs around here, including CM, will have a recovery system added, but if you flash a ROM without a recovery system (like a stock ROM that you flash with Flashtool), you'll have to flash a kernel with a recovery yourself.
It's pretty easy to recover from issues and stuff on a Sony device once you know how things work. It's also a good idea to learn how to use flashboot through a terminal since that will potentially save you a lot of time down the road
Click to expand...
Click to collapse
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
D2084 said:
Everything seems to be working quite well so far, including the wifi but I'll keep what you said in mind. I used the same process to install GApps on it too so now I have the play store and google apps install as well. I have another question though, whenever I plug in a charger to charge the device .. I notice the screen never goes off but stays black and has nothing on display sorta like ambient display, would you know if that's a feature of Cyanogenmod or did I goof somewhere during the install? Thanks in advance for your reply.
Click to expand...
Click to collapse
Could it be Daydream? Go to Settings -> Display -> and disable Daydream. Now check again. If it's not Daydream causing it, then it might be a bug. Do a reboot in case it's a small glitch of some kind. If it's still on when charging, then I'm not sure what it could be (other than a bug, that is).
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
D2084 said:
Sorry for the late reply, but I figured out the reboot issue .. I had to turn off the 'wake up' feature when you plug in your device. I have a whole new issue though, I'm not sure if it can be resolved though - I was on the phone with MetroPCS for about an hour trying to figure out why my phone wouldn't connect to their network. I know Cyanogenmod comes with APN's pre-installed but even after the representative tried helping me set up a new APN .. it was a no go, so I switched back to the current phone I'm using - Alcatel Idol 3 4.7 .. anyways, I'd like to hear your input on what the issue could be as I'd really like to go back to using this phone since the software aspect is far more flexible with a custom ROM like Cyanogenmod.
Click to expand...
Click to collapse
Are you talking about connection to their network altogether, or just data? Do you have reception? Check that data is enabled in Settings -> Data usage.
I can guarantee that this is a software issue, BUT one last question. How old is your SIM card? There have been a few cases when people have been in the same situation as you, got a new SIM, and that fixed the issue. You could do that, or flash another ROM. CM12.1 is beta, so bugs have to be expected, and it's far from a solution if you plan to just flash something and use it for a longer period of time. If you want something very stable and stock, then highly recommend Scrubber's GPe 5.1 port, which is rock solid.
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
D2084 said:
Well my sim card isn't too old, had it for about a year. Once she laced the sim card to the new phone I could make calls and texts but for some reason the Internet wasn't working - she had me go through all the steps to make sure things like data was enabled and airplane mode was off but it still resulted in not being able to establish a connection to the web. So I'm gonna try and flash the GPE rom you're talking about later on tonight once I get home from work and see what happens then - mind leaving me a link to the rom/recovery? Thanks in advance.
Click to expand...
Click to collapse
Sure. Here it is. Remember to download 5.1, and not 5.0. Recovery is included in the ROM, so you don't have to flash anything else.
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
D2084 said:
Quick update, I've flashed the ROM but so far it seems to be stuck in a bootloop, its been stuck on the swaying Google logo for about 10 minutes now. It might be because I sideloaded using a micro SD card because for some odd reason the 'flash the system' option on Flashboot wasn't working for me. So I turned the phone off and will give it another try tomorrow, if you have anymore tips for me I'll be glad to hear em.
Click to expand...
Click to collapse
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Klaos3000 said:
How did you flash it? It must be flashed in recovery on the device and not using Flashtool. Flashtool is strictly for stock Sony ROMs or FTFs. Never use it for anything else besides flashing FTFs and kernels. So:
- Go into recovery
- Remember to wipe! If you don't, you'll get a bootloop
- Install from SD card
- It will probably throw an error at you, but don't touch anything. It's still flashing.
- Reboot
- Wait a couple of minutes.
Click to expand...
Click to collapse
Just did everything you just said, will update you tomorrow with results.
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
D2084 said:
Well I did what you said and left the phone to charge overnight - it was in bootloop when I went to sleep and .. bootloop when I woke up (at least it's charged now lol) I'm gonna try again though. I see that CWM has a sideload option, so I'm gonna wipe everything and try to sideload it from the ADB through the command prompt and see what happens. Feel free to leave any other suggestions though.
Got a question though, when I sideload the zip file should I sideload everything within the zip file or just the system image file? Maybe I'm getting bootloop because I'm installing a kernel on top of another kernel?
Click to expand...
Click to collapse
Sideload/flash the .ZIP. Do not extract it. You should simply just boot into recovery, choose "ScrubberPortRom_GPE5.1_LMY47D.zip", flash and wait for a couple of minutes and then reboot. That's it. The first boot should take around 5 minutes.
- Remember to do a full wipe in recovery before you flash
- Flash ScrubberPortRom_GPE5.1_LMY47D.zip
- Reboot
And do share any error messages if you get any while flashing.