I have a fascinate and have successfully rooted it, flashed the cricket info (i got talk and text) and had 3g at one point. All of the sudden 3G went out. I put CYANOGEN on there, latest 7.1 i believe for the fascinate.
Upon trying to revert back to the original ROM so I can get in there with PST and CDMA WS, I encountered a very strange set of problems and now I am just stumped. I tried to ask a couple of other people and no one seems to know what is happening.
Here is what happens, I try to put the original ROM on there, by using ODIN and doing the atlasv2.2 pit file, and the original ROM, froyo, and the other one eclair i think.
When I use odin it gets to the system part, then right after it goes to the part that would take the longest, and I forgot what its called, dataFS? it has FS at the end, and then the phone (while odin is still going) will go to either a blue screen or a green screen with no words. If you look closely, it appears there is a clock at the top right just like if the phone was on.
I have not overclocked this device at all so thats one thing that can be ruled out.
I've tried odin using both battery in and battery out method as different guides have stated different things. When the battery is out, I get a blue screen. When its in, i get a green screen.
The screen appears right after the normal odin screen, with the status bar, but it will dissapear when it comes to the dataFS part (right after system) then it will take about 20 - 45 minutes and I will get an error screen on odin.
Funny thing is i've used odin and that method and it worked the last time. It works fine if I need to flash a clockwork recovery. However, upon booting into recovery, half the time I will get an error that has to do with BUILD.prop and SCH-I500. This is when I try to flash any rom except MIUI. For some reason, MIUI kicks this phone around and its the only rom that works. CM7 wont work, stock won't and every other rom wont.
So, to sum it up, my main problem is ODIN and its funky behavior, and not being able to go back to stock so I can see if my 3g settings are correct. If you have any information, even if its just something to help get my wheels turning, then please post it up, any and all help is greatly appreciated folks, thanks.
I dont know if this would work but if u think the problem is Odin then I would uninstall odin and reinstall the newest version available. Also, make sure the phone driver software get done the same.
Then after that I would try odin again. Phone off, battery out. Open odin. Plug in usb. Make sure phone set usb to debug. Hold vol down button. Odin should see your phone.
Im sure u know all the steps up to this point but try again.
Good luck
Or u can try running odin as Admin on the comp.
Also if the problem persits I saw a user had a similar problem and of turned out to be his usb cable so try a different one if you can't fix it.
Sent from my ADR6350 using Tapatalk
See, thats what I thought too, but I will give it a shot and see. I doubt its the drivers, odin or the program, file or anything else because it does work with clockwork, and i've downloaded it several thousand times, plus it works great when I do anything but flash the original rom, odin will go fine. Drivers seem fine, it communicates and all that perfectly so I also highly doubt that.
I will get another cable and just try it on a whole different PC to see what happens. I was really hoping someone had this happen and had a fix but I might have to do some heavy delving. THANKS GUYS! I will try this and report back.
It was the cables, used a brand new USB cable and it worked, strangest thing that a cable can work but not work and its just a bunch of wires, but almost all my audio cables have to be bent or else you will loose a channel. I guess its just poor quality materials. So thank you, it works now and it was just the USB cables.
Hi guys, I've had a look around for this, but I can only find the solution for bootloaders that are unlocked. I suspect my Ray WASN'T unlocked. I accepted the OTA 2.3.4 update, thinking it would be fine. But the phone now shows the exclamation mark. I can get into both the recovery and fastboot modes (green/blue LED).
None of the recovery solutions are working for me. Is there a way for me to fix this, or will the phone have to go to a Sony Ericsson shop.
The official PC software from SE won't restore it either.
it is wise to go to sony shop , they will fix it
Not sure if this will solve your problem, but it solved mine:
The problem was with the bootloader. So I tried FlashTool_0.2.9.1_FOTAUnbrick which brings a small firmware information to reset the bootloader.
The problem I was having was to be able to correctly connect the phone to the flash tool. My phone's USB connection was constantly going up and down. So I decided to uninstall all the tools and drivers and install them from scratch.
In short, here's what I did.
Installed Update_Service_Setup-2.11.10.7.exe from sony ericcsson in order to get the USB drivers to work.
Followed the instructions of the Update_Service and flashed the latest update available for my phone (2.3.4). This didn't solve the startup problem, just installed the latest update.
I ran the Update_Service again and restarted the process has if I was going to flash again, but after the Update_Service detected the phone I canceled the installation. (I did this just to make sure the phone was connected in FlashBoot)
Then I installed FlashTool_0.2.9.1_FOTAUnbrick.exe, opened the folder of the application and ran X10FlashTool.exe
Hit Flash button and the program opens a Firmware Selection window with a preloaded firmware with two reseting contents (loader.sin, preset.ta). Hit OK button and waited until the program indicated the flash process was finished. The process of flashing takes a few minutes and we need to be patient. It might even seem like it's doing nothing but we just have to wait.
After finishing the flash process the program invited me to disconnect the phone and turn it on. I did so and the phone took probably a minute or so to startup. At first I thought it didn't solve the problem, because it was taking so long to start, but it did solve! So I waited patiently and the Sony Ericsson logo showed up giving me a new hope. After that I had to wait another 4 or 5 minutes for the phone to finish applying the new firmware mentioned in point 2. (There's no visual information of the conclusion process so you might wonder the phone might have hung.) Just waited and everything got back to normal with the benefits of the new firmware 2.3.4 (instead of the previous 2.3.3).
I hope it helps someone having the same issue.
xperia ray said:
it is wise to go to sony shop , they will fix it
Click to expand...
Click to collapse
Might not fall under warranty.
http://forum.xda-developers.com/showthread.php?t=1568792, check my tutorial, there is a guide to unbricking.
Hi guys im not quite new when it comes to android.
last night i was trying to upgrade and flash a CWM on my friends vibrant whe it stopped. i turned off the phone when tries to turn it back on.... the phone quite turns hot and not like my phone when im flashing it.
i got all the files download and read all of the instructions before starting ofcourse.
first the phone doesnt turn on, then i manage to enter the DOWNLOAD MODE again but somehow the Laptop doesnt detect and gives a yellow punctuation mark on the device. i tried to install and flash the rom but it doesnt continue. i tried putting or plugging it to a diff port but still no luck.
can someone help me and answer this question? is this thing hard bricked = im screwed
any help would be gladly appreciated. thanks again guys in advance
Try a different USB cable as well as a different USB port.
http://forum.xda-developers.com/showthread.php?p=30831184
Read that post, then, read the thread from page 1, just so I don't feel like I've had the same conversation twice in 1 day.
Shouldn't take long its only a few posts. See if this applies to your situation.
thanks boss but i tried the cable with my galaxy mini and it worked when i tried to flash and went back to stock rom. changed the port as well but still no luck....
the phone as well doesnt turn on like the way of a soft brick. a picture of a phone wanted to be connected to a pc, black screen it is though but the phone goes to DOWNLOAD MODE
Try reinstalling drivers from AIO toolbox. Open Odin as administrator. What does Odin say exactly? Is there a yellow box, if so what does it say in it?
i tried reinstalling the drivers i have downloaded but still no luck, odin detects the phone and when it doesnt i re-install the driver so the computer would detect the COM port of the phone. the odin doesnt push through and no BLUE bar on the phone it self. such as the indicator for the flashing. i tried as well running odin as the administrator but still no luck. so do you think that this could be a hard brick, i dont think so cause i can still enter the DOWNLOAD mode of it. the phone turns hot when im on the download mode. could this be a hardware problem.
No its probably not a brick. I think its a communication issue. I would still think its possible to fix it. As far as it getting hot, not sure but the fact that it gets to download mode is a beacon of hope.
I've got to go to bed, will be back tomorrow to check on this.
yeah i hope thesame way too man. thanks for the reply.... time for you to take some rest. thanks again. i'll post the reply if ever the phone gets fixed
thanks for everything man, the phone now is resurrected after JTAGGING. but i know that those technicians who charged me 1000php just did the flashing on ODIN. i know the thing i've done wrong why it didnt work the first time. now it is running up again. the firmware that was flashed was for TELUS. it now shows T959D. i'll follow the guide fully on flashing and upgrading this thing
I had the same problem as you this morning. I tried driver, after driver, after driver and nothing worked. Eventually I gave in and used my sister's laptop and that did the trick. Mabuti ayos na ang cp mo. Ingat.
I got a new xperia active st17i yesterday, it was on gingerbread fw.
I used flashtool to unlock the bootloader. I reset the phone but it hung on the sony logo, which was odd. (I have unlocked and flashed around a dozen xperias and this has never happened). I pulled the battery and turned it back on and it boot looped on the sony logo. (left it for several minutes to be sure). Every time it was switched on after that the screen powered on but remained blank.
I flashed the Rage kernel for GB. Turned the phone on and the sony logo came up, went bright, and I got into CWM recovery ;0) all good I thought. I rebooted the phone. It started up, the sony logo came up, went bright, the animation started but then crashed/hung. I left if for a few minutes and nothing, so I pulled the battery. After this, no screen function at all, no back light, completely dead. ;0( When I power on the phone it vibrates and after a few seconds the front led flashes blue and goes out.
Fast boot works, Flash mode works, Flash tool lets me lock and unlock the phone, flash kernels (rage/X-kernel and Lupus) and ftf firmwares ... S1 tool sees my phone, pc companion updates the phone perfectly, but still no screen.
I read the other ST17i bricked threads here and looked at trying the Wotan server method but the phones date code is not covered, its newer than the ones Wotan cover (maybe an issue?).
I have not idea right now, apart from I have hard bricked it somehow. (searching for 'st17i dead screen' gives a few results from Sony's service forum with similar sounding phone activity, with no resolutions). Searching for bricked st17i all relate to soft bricked devices.
As the phone is brand new, I am not sure about the bootloader issue, is it still covered by warranty? The phones current state is locked and fully updated via pc companion, as it was out of the box.
Any advice and help will be greatly appreciated!
Fixed!!! ... (see edit)
I started from 100% scratch. I use an old laptop with winxp to do all my phone work. I did a factory reset on it (begrudgingly) and reinstalled everything*. ADB, flashtool, drivers/kernels etc. (Its now working a lot better I have noticed).
Bear in mind my phones state was factory stock ics 4.1.B.0.587 and locked.
I unlocked the phones bootloader in flastool, it turned on?! Resurrected.
I flashed the ics rage kernel and installed a custom rom, backed up x2 ;0) I AM HAPPY :0D
I honestly tried everything methodically beforehand, hence my post!
*Is it possible to install a corrupt zip? I noticed when downloading files that some were showing as downloaded but were not the correct file size. I only noticed this when grabbing a kernel file, its size was around 6.7mb but the file I had on my desktop was 633kb, it unpacked and came up with the correct size of 6.7mb? (downloaded on my main work laptop with windows 8.1). I had so many bits and pieces on my xp laptop, swapping files from usb pens etc I will assume this could have been my issue!
lol... I must have spent near to 6+ hours reading about tespoint method flashing, TA restoring/backup up, and a whole range of other bricked device issues... I am educated a little bit more now, in more ways heheh...
Update....
The phone worked for about 30 minutes and then a blank screen again. No CWM, because of blank screen. Had fastboot and flashmode still.
So from scratch again, I relocked and flashed with original ftf CE (I have two CE ftf's of different sizes (will need to do homework on these)). The phone was still dead? When plugged into my pc (tried all three USB ports), sometimes when in fastboot/flashmode the device keeps connecting/disconnecting randomly, which is definitely wrong. Possibly my problem is a bad port or maybe the micro usb cable, or loose connection somewhere? Irdk? So now I tried a brand new sony, original, cable and all seems fine again. So, used flashtool to unlock, flash kernel, get to CWM, use my backup and the phone is working again.... but for how long? There's definitely an issue with the ftf files (mabye something to do with my corrupt file size problem? Will go to another place to grab these from and if the phone goes off again will try). odd.
**last edit**
The phone is now running okay. I had a dud battery, which I was using/swapping between several phones that I was returning to stock. It was showing 100% charged but upon disconnecting USB the phone died. Took me the best part of two days to figure that one out... I know! (I'm very busy). So it was possibly the bad battery all along!
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.