Hello:
I need help because of obstinacy. A year ago bought a Chinese mobile dual sim Sensation XL. On power failure gave me the 2 imei.
I put the features:
Chip: MT6573
Board: ratech73_gb
Kernel: 2.6.35.7
Android Version: 4.0.2
Sw Version: g20h_s4x_b1_alpsgbfdd2mpv3_v9520120327
I have tried doing Root. I've tried with these programs
2.3 SuperonClick
Unlook root
Shuame
Doomlord_V2/Doomlord v4
FlashBoot 9.8
TPSparkyRoot
SP MDT v2.1125.00. Knew not use this
ZP100 zopo 4.0ROOT by008
mobileuncle root 6575 4.0
Ultimate Toolbox Pro Android
x10flasher_lib
XLMultiTool.v2.1
None of these programs have been successful.
Also tried and tried to flash it, to change the kernel, rom, etc ... But the result is always the same, I can not.
The process is always the same, I include the kernels, images, roms flashing in the program, but the phone does not start in flash mode.
I press the volume up and power button and get a triangle with android within construction.
I tried in windows 7, windows xp.
Please Help!!
AbelZgz said:
Hello:
I need help because of obstinacy. A year ago bought a Chinese mobile dual sim Sensation XL. On power failure gave me the 2 imei.
I put the features:
Chip: MT6573
Board: ratech73_gb
Kernel: 2.6.35.7
Android Version: 4.0.2
Sw Version: g20h_s4x_b1_alpsgbfdd2mpv3_v9520120327
I have tried doing Root. I've tried with these programs
2.3 SuperonClick
Unlook root
Shuame
Doomlord_V2/Doomlord v4
FlashBoot 9.8
TPSparkyRoot
SP MDT v2.1125.00. Knew not use this
ZP100 zopo 4.0ROOT by008
mobileuncle root 6575 4.0
Ultimate Toolbox Pro Android
x10flasher_lib
XLMultiTool.v2.1
None of these programs have been successful.
Also tried and tried to flash it, to change the kernel, rom, etc ... But the result is always the same, I can not.
The process is always the same, I include the kernels, images, roms flashing in the program, but the phone does not start in flash mode.
I press the volume up and power button and get a triangle with android within construction.
I tried in windows 7, windows xp.
Please Help!!
Click to expand...
Click to collapse
Umm, you have a dual-sim fake Sensation XL, so probably none of the tools here will work on you, at best you can do all the things by yourself, dev things for it...
What I can do?
Lexmazter said:
Umm, you have a dual-sim fake Sensation XL, so probably none of the tools here will work on you, at best you can do all the things by yourself, dev things for it...
Click to expand...
Click to collapse
add that the phone has another active menu is pressed power and volume keys below:
** Factory mode
***** Full Test
***** test Item
***** test Report
***** clear flash
**** version
**** reboot
But when I enter so I can not flash from FlashTool or other programs.
What I can do,please?
AbelZgz said:
What I can do,please?
Click to expand...
Click to collapse
By searching root tools, roms, recovery etc to your phone which isnt related to htc anyhow...
Look from these: http://forum.xda-developers.com/showthread.php?t=1594998
http://forum.xda-developers.com/showthread.php?t=1825722
http://forum.xda-developers.com/sitesearch.php?q=MTK6577
http://forum.xda-developers.com/sitesearch.php?q=MT6573
AlluXX said:
By searching root tools, roms, recovery etc to your phone which isnt related to htc anyhow...
Look from these: http://forum.xda-developers.com/showthread.php?t=1594998
http://forum.xda-developers.com/showthread.php?t=1825722
http://forum.xda-developers.com/sitesearch.php?q=MTK6577
http://forum.xda-developers.com/sitesearch.php?q=MT6573
Click to expand...
Click to collapse
Thank you.
I could change with this program imeis http://www.mobilepoint.us/2012/12/mtk-droid-root-tools.html thanks to the first link you put http://forum.xda-developers.com/showthread. php? t = 1594998.
But I still can be root or unlocking the Bootloader
Any idea?
AbelZgz said:
Thank you.
I could change with this program imeis http://www.mobilepoint.us/2012/12/mtk-droid-root-tools.html thanks to the first link you put http://forum.xda-developers.com/showthread. php? t = 1594998.
But I still can be root or unlocking the Bootloader
Any idea?
Click to expand...
Click to collapse
Fakes usually have unlocked bootloaders and you most probably can root it using some generic rooting methods, for other device i mean, check any root script for ICS on other devices and try it for yourself, rooting is achievable on fakes.
Hi there
I am encountering an issue with my Sony Xperia T (FW: 9.1.A.1.141) which I am certain can be resolved with the correct tools and knowhow, but having spent the last week following what feels like every related link on the internet, I am no further forward - sleeping badly as a result - and very much in need of some help.
I'd prefer to avoid a torrent of potential fixes that I may already have tried at length so please forgive me if I go into too much detail. I just want to be very clear exactly where I am and what I have done so far to try and fix the issue. My PC is running Windows 7 64-bit (no issues).
This is my first proper smartphone so after a few months getting to grips with the underlying nature of the Android OS, I decided it was now time to root the phone and try out different ROMs etc. After reading what I could about the process, I finally used DooMLoRD's Easy Rooting Toolkit 17 (For Sony Xperia Devices) and was amazed by how easy it was to unroot my device. After installing Titanium Backup and fully backing up my files, I then installed ClockWorkMod Recovery 6.0.4.6 (For Sony Xperia Devices), and was able to boot into the recovery environment without issue (I also made an additional backup of the system at this point). So far, so good.
I then copied two ROMS to my SD card - Android 4.4.2 (KitKat) For Sony Xperia T (AOKP Build) & CyanogenMod 11.20140127 (Nightly) For Sony Xperia T - and tried to flash the CyanogenMod ROM from within the ClockWorkMod Recovery Environment, however I received a Status 7 Error, preventing me from flashing the ROM, then tried the same with Android 4.4.2 (KitKat) ROM, but again I received a Status 7 Error. As I attempted to leave the recovery environment to research the Status 7 Error, the program flashed a popup saying the phone was not rooted and would I like to root it. At this point, I assumed I had lost root as a result of the Status 7 Error, but didn't want to make any more changes, so chose no to the root option and restarted my Xperia T.
At this point the Sony logo went into a loop and despite restarting the phone using power and volume up many times, I was unable to boot back into the ClockWorkMod Recovery Environment nor connect the phone to my PC, although I could see the drivers appear for a few seconds in Windows before disappearing. It took me a good couple of days to realise that I had to fully charge my phone, so when I began the operation again with a fully charged phone I was able to update the driver in Device Manager from Sony Ericsson Seehcri Control Device (yellow exclamation mark) to Sony ADB Device (although the Sony Ericsson Seehcri Control Device with exclamation mark later returned so I am unable to assess how successful this actually was).
From here, I tried to update the phone using the already installed and up to date PC Companion, but the phone will not connect in flash mode, so it is not possible to connect the phone. I also tried the latest Sony Update Service (2.13.4.16), then Sony Emma Flash Tool (For Sony Xperia Devices), but none of these recognise the phone because I cannot get the phone into flash mode. Using the Android Flash Tool 0.9.13.0 (For Sony Xperia Devices), I am able to connect to the phone in fastboot mode, but when I try to install a stock kernel or any other variant, the Flash Tool states that I can't make any changes because the phone is not rooted.
Thinking I could root my phone again with DooMLoRD's Easy Rooting Toolkit 17, this time it no longer works, I assume because my phone cannot enter flash mode, even though it is recognised in Android Flash Tool 0.9.13.0 in fastboot mode (blue light).
Now, it is conceivable since my phone is no longer rooted that I may well be able to have my phone fixed under warranty and returned to me, however I would thereafter be scared to try and install a custom ROM, and would never really feel comfortable with the phone again, so I would much prefer to learn how to fix the problem myself. I am convinced the phone is salvageable because I have no issue recharging the phone, the screen is lighting up to display the Sony logo without issue and I am able to connect to my PC so that Sony ADB Device is recognised in Device Manager and via the Android Flash Tool 0.9.13.0, but can make no other changes.
My suspicion is that it has something to do with the ADB drivers, (which I linked to my Android Developer Tools Bundle 20131030 64-bit via the Windows Environment Variables), since no devices are recognised when I connect the phone and run the ADB Devices command in the Windows Command Prompt even when Windows is otherwise able to identify the device in Device Manager.
If anyone would be willing to talk me through this, I would be most grateful and would follow up all advice up so this information might be useful to others in the future as I can't see this being an isolated case. Likewise, if I am simply wasting my time and need to get the phone replaced or repaired, at least it would be good to know that I have exhausted all other options.
FYI Prior to the soft brick, I had USB debugging enabled and was in Mass Storage Mode (since this was more stable than Media Transfer Mode).
Hi. I don't see any mention of bootloader status. Did you go through the process of unlocking your bootloader? Or have you checked to see if your phone is "bootloader unlock allowed: yes"? The reason I ask is because the 2 roms you want to try seem to be AOSP-based / Cyanogen, which run on custom kernels. If your bootloader is locked, you are not allowed to flash custom kernels. That might explain the failure code you say in CWM - or it might not (since my bootloader cannot be unlocked, I don't have much experience with those kinds of ROMs).
Moving on to the recovery you flashed - Which recovery did you install? I have been reading that Clockworkmod recovery (v9) is quite buggy. You can get v8 in this thread: http://forum.xda-developers.com/showthread.php?t=2609997
The peeps in this forum are pretty good problem solvers (and creators ;D) - we'll get you going again hopefully!
is your bootloader unlocked dude?i mean if you have a locked bootlader you are not supposed to install custom roms. and if your boot loader is unlocked sony update engine and pc companion wont solve the issue. you have to try with flashtool .firstly you gotta install the flashtool drivers fot xt .and then run flashtool x64. hold the vol down button and connect it using usb. i had this problem many times. and that above procedure may solve your issue
Hi there
First of all thank you so much for replying. These forums are quite daunting at times and it is good to know someone with some clout is listening. Apologies again for going into yet more detail, but it should help me reach a resolution sooner rather than later.
As re the bootloader, I was under the impression that DooMLoRD's Easy Rooting Toolkit 17 would root my stock Xperia T while leaving the bootloader untouched - that is to say locked (as far as I am aware) - should I wish to revert the rooting process at a later date. Now, I obviously lost root somewhere along the line, but has the bootloader also been changed to unlocked? I don't know, but I wouldn't imagine so, so I can only assume it is still locked.
I have recharged my phone ready to make some fresh attempts at this, but to confirm the current state of my Windows 7 connection, I can only connect to the PC in fastboot (with the blue light turned on after connecting to the machine while pressing volume down). There is definitely an issue with some aspect of the drivers since the Sony ADB Device is recognised as working in Device Manager as soon as I connect the phone, however the bothersome Sony Ericsson Seehcri Control Device is also present with a yellow exclamation mark indicating a problem.
Now, whether this is actually affecting my use of the Android Flash Tool 0.9.13.0 and the other flash tools, I can't actually say. When I open the Android Flash Tool with the phone connected, the two options available to me are flashmode or fast boot mode. When I try to use the flashmode with the (as far as I am aware) Xperia T stock firmware LT30P_9.1.A.1.141_PL.ftf, I simply cannot connect in flashmode when prompted. I am asked to remove the phone then reattach it, but no green light ever shows indicating flashmode, only the blue light indicating fast boot mode. When I try to use fast boot mode on the other hand, firstly I am not sure which of the various methods to use - I have of course tried them all, and also I should say both the 32-bit and 64-bit versions of the Flash Tool - but when I do, I am always told that the device needs to be rooted first.
Now, this may have something to do with the kernels/firmware/ROMs that I am using (there's no question all the variations confuse me a little) as I assumed it simply wasn't possible to flash via fastboot yet further reading suggests that it should be possible to flash a stock kernel without root access. The kernels/firmware I have tried are: stock-7.0.A.3.223-twrp-2.3.3.0.elf; 15102012.img; Sony Xperia T Kernel (Stock) With CWM602; Sony Xperia T Kernel (Stock) With TWRP2500. So perhaps I am not using the correct firmware or kernel (I would like to try the LT30P_9.1.A.1.141_PL.ftf, but cannot see an option to do so via fast boot mode). If this is the case and I am able to identify the correct kernel, then perhaps this "device must be rooted first" notification would no longer happen and the state of the ADB drivers would be largely irrelevant.
On the other hand if the flash tool in fast boot mode is always going to ask me to root first, wouldn't it make more sense to focus my attention on being able to connect to DooMLoRD's Easy Rooting Toolkit 17 in order to root the device so I can then use the Flash Tool in fast boot mode without any further issues. But that being the case, perhaps I should focus on working out what is happening with the problem Sony Ericsson Seehcri Control Device in Device Manager. Perhaps when that is resolved I will be able to connect to any of the available flash tools.
As far as ROMs and Recovery Environments are concerned, I truly appreciate your advice - and believe me when I resolve this problem I will be sure to run through my rooting plans BEFORE executing them on these very forums - but for now I need to focus on flashing the phone back to stock or somehow connecting the phone to one of the Sony Flash Tools.
Thanks again for your patience and assistance so far and I look forward any more ideas now I have provided a bit more detail.
My sanity hangs in the balance!
BTW, I imagine you are both quite right about what went went wrong in the first instance - I did not appreciate you couldn't flash any ROM once the Xperia T had been rooted. Again, when I resolve this issue, I will describe my exact plans before proceeding. Thanks for clearing that up. I'm learning all the time.
pfhastie said:
BTW, I imagine you are both quite right about what went went wrong in the first instance - I did not appreciate you couldn't flash any ROM once the Xperia T had been rooted. Again, when I resolve this issue, I will describe my exact plans before proceeding. Thanks for clearing that up. I'm learning all the time.
Click to expand...
Click to collapse
Try unlocking bootloader, fastboot flashing boot.img of the rom you want. (before hand get the rom you want on sd or something) And then you should flash without error.
First of all thank you so much for replying. These forums are quite daunting at times and it is good to know someone with some clout is listening. Apologies again for going into yet more detail, but it should help me reach a resolution sooner rather than later.
Click to expand...
Click to collapse
Detail is always good - much better than a "i rooted my phone and now it doesn't work" post. I agree, information is in many different places - very easy for that to happen.
As re the bootloader, I was under the impression that DooMLoRD's Easy Rooting Toolkit 17 would root my stock Xperia T while leaving the bootloader untouched - that is to say locked (as far as I am aware)
Click to expand...
Click to collapse
Yes - that is, if your bootloader was Locked when you started this whole adventure.
Now, I obviously lost root somewhere along the line
Click to expand...
Click to collapse
- Maybe but maybe not!,
but has the bootloader also been changed to unlocked? I don't know, but I wouldn't imagine so, so I can only assume it is still locked.
Click to expand...
Click to collapse
No - the bootloader unlock is a whole process in itself. DoomLord's (fantastic) root kit will root your phone - meaning, it will root your phone's current system, to allow read/write access to the system's files. When you unlock the bootloader, that allows you to write to partitions (kernel aka boot, radio/baseband? etc.)
I have recharged my phone ready to make some fresh attempts at this, but to confirm the current state of my Windows 7 connection, I can only connect to the PC in fastboot (with the blue light turned on after connecting to the machine while pressing volume down). There is definitely an issue with some aspect of the drivers since the Sony ADB Device is recognised as working in Device Manager as soon as I connect the phone, however the bothersome Sony Ericsson Seehcri Control Device is also present with a yellow exclamation mark indicating a problem.
Click to expand...
Click to collapse
Since right now, what you need to be able to do is flash a stock FTF (to get your phone working again), make sure your phone is disconnected from the PC. Drivers --- all you should need is Sony PC Companion installed (which installs base drivers for the phone), and Flashtool (http://forum.xda-developers.com/showthread.php?t=1943886). After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** i dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again. You will need them!!
Now, whether this is actually affecting my use of the Android Flash Tool 0.9.13.0 and the other flash tools, I can't actually say. When I open the Android Flash Tool with the phone connected, the two options available to me are flashmode or fast boot mode.
Click to expand...
Click to collapse
Stop here for a second - For the purpose of flashing an FTF (i.e. getting your phone back to working state), do not connect the phone yet.
When I try to use the flashmode with the (as far as I am aware) Xperia T stock firmware LT30P_9.1.A.1.141_PL.ftf, I simply cannot connect in flashmode when prompted. I am asked to remove the phone then reattach it, but no green light ever shows indicating flashmode, only the blue light indicating fast boot mode.
Click to expand...
Click to collapse
When using Flashmode, don't connect the phone at all - Choose flashmode, then choose the FTF, then wait for it to process the files, then it will pop up to tell you when to connect the phone. And this is very important - make sure the phone is fully OFF, then, hold the VOLDOWN button, then plug the usb cable in - when you see Flashmode start moving along, you can let go of the VOLDOWN button... and put the phone down gently .. you dont want to distrub this delicate process .
When I try to use fast boot mode on the other hand, firstly I am not sure which of the various methods to use - I have of course tried them all, and also I should say both the 32-bit and 64-bit versions of the Flash Tool - but when I do, I am always told that the device needs to be rooted first.
Click to expand...
Click to collapse
This may all depend on your bootloader - if your bootloader is locked, you likely cannot get the phone into Fastboot mode.
Now, this may have something to do with the kernels/firmware/ROMs that I am using (there's no question all the variations confuse me a little) as I assumed it simply wasn't possible to flash via fastboot yet further reading suggests that it should be possible to flash a stock kernel without root access.
Click to expand...
Click to collapse
Right - flashing via fastboot may not be possible right now if your bootloader is locked.
The kernels/firmware I have tried are: stock-7.0.A.3.223-twrp-2.3.3.0.elf; 15102012.img; Sony Xperia T Kernel (Stock) With CWM602; Sony Xperia T Kernel (Stock) With TWRP2500. So perhaps I am not using the correct firmware or kernel (I would like to try the LT30P_9.1.A.1.141_PL.ftf, but cannot see an option to do so via fast boot mode). If this is the case and I am able to identify the correct kernel, then perhaps this "device must be rooted first" notification would no longer happen and the state of the ADB drivers would be largely irrelevant.
Click to expand...
Click to collapse
Yes - let's skip the kernels for now - and get you flashing a fresh FTF so you can start over. I suggest that once the FTF is flashed, and the phone can boot normally, you dial the Service Menu number and look to see if your phone has "Bootloader Unlock Allowed: Yes" or "Bootloader Unlock Allowed: No". -If it says NO, it means NO! There is currently (as of Feb3/2014) no way to get around this. This means your bootloader cannot be unlocked, which means no custom kernels, and no fastboot! Custom ROMS can still be flashed - just those that are Locked Bootloader-friendly (meaning, the custom rom operates just fine/is based on the Stock kernel - whatever version is preferred will be mentioned in the dev's first post of the thread). There are a few.. like XperimenT and T-Hybrid. I like those.
I'm going to be safe and assume yours says No (like mine, because everyone should suffer with me!! ) You can then ROOT the system like you did, then install CWM Recovery for locked bootloaders (v8!! dont use v9 for now), then you can flash a rom or do whatever. If the custom rom you're installing is based on a stock kernel whose version number is different from your phone's base, then you may be able to find kernel zips that are flashable via CWM - since they are stock kernels, the flash will be allowed because they are signed or whatever. Example: Since you're going for LT30p .141 FTF, you're on the 141 kernel. If the rom you're installing says it recommends the .145 kernel, find the LT30P .145 kernel zip. You can flash that right after flashing the ROM. I think that the 141/145 kernels are similar to each other so in this case, you may not even have to flash from 141 to 145. But you will - because you will become addicted to flashing like the rest of us and you will want to observe/compare how the ROM behaves on each.
On the other hand if the flash tool in fast boot mode is always going to ask me to root first, wouldn't it make more sense to focus my attention on being able to connect to DooMLoRD's Easy Rooting Toolkit 17 in order to root the device so I can then use the Flash Tool in fast boot mode without any further issues.
Click to expand...
Click to collapse
I think what it's really asking you is to Unlock Your Bootloader. Unlocking the bootloader is kind of considered a global root (because it allows writing to any partition on the phone.
But that being the case, perhaps I should focus on working out what is happening with the problem Sony Ericsson Seehcri Control Device in Device Manager. Perhaps when that is resolved I will be able to connect to any of the available flash tools.
Click to expand...
Click to collapse
Yes - hopefully above we have tackled that.
As far as ROMs and Recovery Environments are concerned, I truly appreciate your advice - and believe me when I resolve this problem I will be sure to run through my rooting plans BEFORE executing them on these very forums - but for now I need to focus on flashing the phone back to stock or somehow connecting the phone to one of the Sony Flash Tools.
Thanks again for your patience and assistance so far and I look forward any more ideas now I have provided a bit more detail.
My sanity hangs in the balance!
Click to expand...
Click to collapse
Agreed!! Good luck!
Thanks for the considered responses. hhamzah49, I have tried to use the bootloader unlock in the flash tool, but it simply waits for me to connect in flash mode, which is what I am unable to do. There is not even an opportunity of using a SD card since I cannot start the phone either normally or in a recovery environment.
LaZiODROID, you're the man for going into so much detail, and yes I am looking forward to trying out loads of ROMs if possible, however I can't consider such luxuries until I've flashed the phone back to stock! It seems the bootloader probably has a lot to do with it, and I wish I could confirm one way or another if it is locked or not, but I don't see a way to do that in the phone's current state. I bought it from Amazon UK in October or thereabouts, so perhaps that might give you a clue - I would assume it is locked for now, but happy to try the process working on the assumption that it is unlocked if that is likely to help.
I am already using the Flash Tool you suggested and have OKed the drivers signature on Windows 7. I understand about not connecting the phone prior to preparing the flash tool (in flashmode) - and making sure it is fully off by pressing power and volume down until I feel the three vibrations indicating the phone is fully off - but all this seems to be immaterial as I am never able to connect in flash mode. Only the blue light ever appears, never the green one.
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked, however I am ONLY able to connect in fast boot mode so if I am not able to flash via fast boot, I am not sure what other course of action to take.
I think I understand now about the unlocked bootloader and having to source suitable ROMs when the time comes, but not quite there yet.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Anyway, my comatose phone and I remain on standby ready to try whatever it takes.
LaZiODROID said:
Detail is always good - much better than a "i rooted my phone and now it doesn't work" post. I agree, information is in many different places - very easy for that to happen.
Yes - that is, if your bootloader was Locked when you started this whole adventure. - Maybe but maybe not!, No - the bootloader unlock is a whole process in itself. DoomLord's (fantastic) root kit will root your phone - meaning, it will root your phone's current system, to allow read/write access to the system's files. When you unlock the bootloader, that allows you to write to partitions (kernel aka boot, radio/baseband? etc.)
Since right now, what you need to be able to do is flash a stock FTF (to get your phone working again), make sure your phone is disconnected from the PC. Drivers --- all you should need is Sony PC Companion installed (which installs base drivers for the phone), and Flashtool (http://forum.xda-developers.com/showthread.php?t=1943886). After you install Flashtool, you will need to go into its folder - inside of there is a "drivers" folder. go in there and run the EXE. On the left side, make sure to click/check the driver for your phone (xperia T or TL or LT30p or whatever), plus the Fastboot driver, plus the Flashmode driver. Let it do the install. **NOTE** i dont know if Win7 has "driver signature enforcement" - if you notice the drivers are failing to install, that could be why. Look into how to temporarily disable driver signature enforcement and try these 3 drivers again. You will need them!!
Stop here for a second - For the purpose of flashing an FTF (i.e. getting your phone back to working state), do not connect the phone yet.
When using Flashmode, don't connect the phone at all - Choose flashmode, then choose the FTF, then wait for it to process the files, then it will pop up to tell you when to connect the phone. And this is very important - make sure the phone is fully OFF, then, hold the VOLDOWN button, then plug the usb cable in - when you see Flashmode start moving along, you can let go of the VOLDOWN button... and put the phone down gently .. you dont want to distrub this delicate process .
This may all depend on your bootloader - if your bootloader is locked, you likely cannot get the phone into Fastboot mode.
Right - flashing via fastboot may not be possible right now if your bootloader is locked.
Yes - let's skip the kernels for now - and get you flashing a fresh FTF so you can start over. I suggest that once the FTF is flashed, and the phone can boot normally, you dial the Service Menu number and look to see if your phone has "Bootloader Unlock Allowed: Yes" or "Bootloader Unlock Allowed: No". -If it says NO, it means NO! There is currently (as of Feb3/2014) no way to get around this. This means your bootloader cannot be unlocked, which means no custom kernels, and no fastboot! Custom ROMS can still be flashed - just those that are Locked Bootloader-friendly (meaning, the custom rom operates just fine/is based on the Stock kernel - whatever version is preferred will be mentioned in the dev's first post of the thread). There are a few.. like XperimenT and T-Hybrid. I like those.
I'm going to be safe and assume yours says No (like mine, because everyone should suffer with me!! ) You can then ROOT the system like you did, then install CWM Recovery for locked bootloaders (v8!! dont use v9 for now), then you can flash a rom or do whatever. If the custom rom you're installing is based on a stock kernel whose version number is different from your phone's base, then you may be able to find kernel zips that are flashable via CWM - since they are stock kernels, the flash will be allowed because they are signed or whatever. Example: Since you're going for LT30p .141 FTF, you're on the 141 kernel. If the rom you're installing says it recommends the .145 kernel, find the LT30P .145 kernel zip. You can flash that right after flashing the ROM. I think that the 141/145 kernels are similar to each other so in this case, you may not even have to flash from 141 to 145. But you will - because you will become addicted to flashing like the rest of us and you will want to observe/compare how the ROM behaves on each.
I think what it's really asking you is to Unlock Your Bootloader. Unlocking the bootloader is kind of considered a global root (because it allows writing to any partition on the phone.
Yes - hopefully above we have tackled that.
Agreed!! Good luck!
Click to expand...
Click to collapse
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
pfhastie said:
Thanks for the considered responses. hhamzah49, I have tried to use the bootloader unlock in the flash tool, but it simply waits for me to connect in flash mode, which is what I am unable to do. There is not even an opportunity of using a SD card since I cannot start the phone either normally or in a recovery environment.
LaZiODROID, you're the man for going into so much detail, and yes I am looking forward to trying out loads of ROMs if possible, however I can't consider such luxuries until I've flashed the phone back to stock! It seems the bootloader probably has a lot to do with it, and I wish I could confirm one way or another if it is locked or not, but I don't see a way to do that in the phone's current state. I bought it from Amazon UK in October or thereabouts, so perhaps that might give you a clue - I would assume it is locked for now, but happy to try the process working on the assumption that it is unlocked if that is likely to help.
I am already using the Flash Tool you suggested and have OKed the drivers signature on Windows 7. I understand about not connecting the phone prior to preparing the flash tool (in flashmode) - and making sure it is fully off by pressing power and volume down until I feel the three vibrations indicating the phone is fully off - but all this seems to be immaterial as I am never able to connect in flash mode. Only the blue light ever appears, never the green one.
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked, however I am ONLY able to connect in fast boot mode so if I am not able to flash via fast boot, I am not sure what other course of action to take.
I think I understand now about the unlocked bootloader and having to source suitable ROMs when the time comes, but not quite there yet.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Anyway, my comatose phone and I remain on standby ready to try whatever it takes.
Click to expand...
Click to collapse
bro we got two buttons vol up and vol down. while connecting to flashtool ,holding the vol up key enters fastboot mode, and holding vol down key enters flashmode. if even holding vol down key makes u enter fastboot mode!!! try vol up key. i m just not sure about it. just give it a shot
rough map
romeoofair said:
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
Click to expand...
Click to collapse
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
pfhastie said:
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
Click to expand...
Click to collapse
anyway flashtool is the best sol for your issue bro. hope your device gets back on track soon. sorry i was too lazy to write a long post. so i gave it roughly
pfhastie said:
Pretty much. You can tell it's doing my head in surely ("Don't call me Shirley").
Anyway, the devil is in the details. I am convinced this can be done once all the parameters are crystal clear.
Click to expand...
Click to collapse
try to do a hard reset; (while NOT connected via usb or something) hold power+vol up, it will vibrate 1 time, and then 3 times quick. After that try to connect the usb (NOT while pressing any buttons) and press vol down+power
That should connect it into flashmode.
romeoofair said:
man . you got some real patience to write all those. its just what i wrote in twoo lines :silly:
---------- Post added at 01:48 AM ---------- Previous post was at 01:41 AM ----------
bro we got two buttons vol up and vol down. while connecting to flashtool ,holding the vol up key enters fastboot mode, and holding vol down key enters flashmode. if even holding vol down key makes u enter fastboot mode!!! try vol up key. i m just not sure about it. just give it a shot
Click to expand...
Click to collapse
OK, I'm totally aware that this seems to be the main clincher, if I can somehow get it into flash mode (with green light), but I have tried connecting it pressing every combination of button I can think of, but it only ever connects in fast boot (with blue light). I'm just gonna grab a bite just now, but will try this some more right after and let you know (turning the phone off with one vibration, then three, up and down buttons etc). Thanks again for now.
romeoofair said:
man . you got some real patience to write all those.
Click to expand...
Click to collapse
Thank you. A patient attitude and thorough reply from others is what has kept me coming back to this forum.
its just what i wrote in twoo lines :silly:
Click to expand...
Click to collapse
I disagree.
pfhastie said:
You say it is likely that I will not be able to connect the phone in fast boot mode because my bootloader is locked,
Click to expand...
Click to collapse
I believe I said "if", not "because". The status was unknown to me. I couldn't say anything certain about your device.
I have uploaded several images of my current connection via Command Prompt, Device Manager, Android Flash Tool 0.9.13.0 & DooMLoRD's Easy Rooting Toolkit 17. I also noticed that when I start DooMLoRD's Easy Rooting Toolkit 17 with no ADB drivers running in Windows Task Manager Processes, two instances of the ADB driver appear, each leading back to DooMLoRD's Easy Rooting Toolkit 17 and each a slightly different size. When I try to run the Rooting Toolkit, the command prompt simply says "daemon started successfully", but nothing happens after this. If I kill one of the two ADB processes, this seems to start the program off, but to no avail since "device not found" is displayed repeatedly.
Click to expand...
Click to collapse
Since your phone doesn't boot into a system, I'm not sure if DoomLord's rooting kit will help you. What is there to root? There's no Android system running yet for it to root (right?).
Great news
You beautiful, beautiful people!
I managed to get the phone into flash mode by following your exact instructions to turn the phone fully off when disconnected from the PC (by pressing power & volume up until I felt three vibrations following a single vibration), then connected the phone again WITHOUT pressing the volume down button (as I had always been doing before), then, after the red light came on and the Sony logo appeared, pressing power & volume up again until suddenly the beautiful green light lit up and I was able to flash the phone back to stock firmware (LT30P_9.1.A.1.141_PL.ftf). I lost flashmode the first time because I was so shocked, and there doesn't seem to be time to hang around, but the second time I connected it again the firmware flashed immediately, fairly quickly and without any issues and I am now looking at my freshly started phone and the virgin Sony Android screen.
I have to say this process is unquestionably difficult to explain over the internet, probably because there is no universal implementation of the buttons, but at least once you know how, you are sorted for future problems (of this type at least).
I swear to god, I feel about a stone lighter as this was really hanging over me - not only am I too skint to be worrying about dead phones and warranty issues, but now I feel more secure testing things out, and might even be able to help others in the same predicament in future. I'm not sure if all the excessive detail was warranted, but better to err on the side of caution as a general principle I believe.
My sincere thanks to everyone for helping me out! You have given me a great introduction to the site and I look forward to any and all future communications.
Sadly, I have a pile of crap to attend to, now I know the phone is working, so I will regather my strength for a fresh attempt at rooting the phone (with DooMLoRD Easy Rooting Toolkit 18 For Sony Xperia Devices), installing a recovery environment (CWM v8 as opposed to v9), then flashing a suitable ROM tomorrow evening. I checked my service menu and it states, "Rooting status: Bootloader unlock allowed: Yes," which I trust opens my options a bit more. The two ROMs I am initially wishing to try are CyanogenMod and KitKat, but would be nice to know I could try others without more problems. I am now also aware to backup the TA Partition via the Android Flash Tool 0.9.13.0 before rooting the phone and assume I should hold off reinstalling my Titanium Backups until I am happy with a particular ROM.
I expect this isn't the place to go over these things (although I am quite happy to do so), so I will start a new thread tomorrow to go over my best plan of action.
Thanks again, and I hope this helps out someone else in the same position!
Wicked! Happy flashing. I'm jealous of your unlockable bootloader!
LaZiODROID said:
Wicked! Happy flashing. I'm jealous of your unlockable bootloader!
Click to expand...
Click to collapse
Thank you, LaZiODROID. You've been more than helpful so I trust you don't mind my quickly confirming what I now understand about the bootloader now you have so succinctly brought it to my attention.
I previously hadn't taken into account the state of the bootloader when I tried to flash a ROM, so my failure (Status 7 Error) probably suggests that the bootloader must currently be locked, although it is possible to unlock it on my particular handset (but not yours), is that correct?
All I knew when I used Doomlord's Rooting Kit was that the bootloader would not be affected thus preserving my warranty status, however it would be advisable for me to unlock the bootloader using the Android Flash Tool 0.9.13.0 so I can install custom ROMs without having to worry about special packages like XperimenT & T-Hybrid, is that also correct?
The only final query I have is, if I do unlock the bootloader (using the Android Flash Tool) in order to flash custom ROMs, can I then lock it again for the purposes of my warranty?
I shall assume the bootloader should be unlocked AFTER rooting the device, but BEFORE installing the CWM Recovery Environment.
Thanks again! I will rest easier tonight.
I think hhamzah49 is the hero who got you going with that nice trick (to get you into flashmode)! I guess it turned out that you didn't have driver issues after all.
pfhastie said:
I previously hadn't taken into account the state of the bootloader when I tried to flash a ROM, so my failure (Status 7 Error) probably suggests that the bootloader must currently be locked, although it is possible to unlock it on my particular handset (but not yours), is that correct?
Click to expand...
Click to collapse
Yes. If you're gonna do it, read up (re: backing up your TA, etc.) I have read with bootloader unlocking, you also lose DRM apps like TrackID and the Bravia engine? If you dont use those then you probably won't mind.
All I knew when I used Doomlord's Rooting Kit was that the bootloader would not be affected thus preserving my warranty status
Click to expand...
Click to collapse
Right.
however it would be advisable for me to unlock the bootloader using the Android Flash Tool 0.9.13.0 so I can install custom ROMs without having to worry about special packages like XperimenT & T-Hybrid, is that also correct?
Click to expand...
Click to collapse
There is also the official Sony method of unlocking your bootloader (see the all-in-one thread). Re: ROMS... I guess it's not so much "worrying" about roms like XperimenT/T-Hybrid - they are good roms and they install via CWM recovery just like any other custom ROM, and they will run on an unlocked bootloader. You just have more ROM selection with an unlocked bootloader because you can use the kernels that ROMS like Cyaongen needs.
The only final query I have is, if I do unlock the bootloader (using the Android Flash Tool) in order to flash custom ROMs, can I then lock it again for the purposes of my warranty?
Click to expand...
Click to collapse
Read up to be sure - but I see in Flashtool that there is an FTF for bootloader re-locking (but more importantly it is linked in the all-in-one thread also)... so it sounds like it won't be too hard to re-lock if you need to.
I shall assume the bootloader should be unlocked AFTER rooting the device,
Click to expand...
Click to collapse
Yes so you can back up your TA after rooting?
but BEFORE installing the CWM Recovery Environment.
Click to expand...
Click to collapse
That I'm not certain of. I think that recovery can be installed whether your bootloader is locked or unlocked. For unlocked bootloaders, there are kernels that have recovery built in so you can just fastboot flash one of them.
pfhastie said:
You beautiful, beautiful people!
I managed to get the phone into flash mode by following your exact instructions to turn the phone fully off when disconnected from the PC (by pressing power & volume up until I felt three vibrations following a single vibration), then connected the phone again WITHOUT pressing the volume down button (as I had always been doing before), then, after the red light came on and the Sony logo appeared, pressing power & volume up again until suddenly the beautiful green light lit up and I was able to flash the phone back to stock firmware (LT30P_9.1.A.1.141_PL.ftf). I lost flashmode the first time because I was so shocked, and there doesn't seem to be time to hang around, but the second time I connected it again the firmware flashed immediately, fairly quickly and without any issues and I am now looking at my freshly started phone and the virgin Sony Android screen.
I have to say this process is unquestionably difficult to explain over the internet, probably because there is no universal implementation of the buttons, but at least once you know how, you are sorted for future problems (of this type at least).
I swear to god, I feel about a stone lighter as this was really hanging over me - not only am I too skint to be worrying about dead phones and warranty issues, but now I feel more secure testing things out, and might even be able to help others in the same predicament in future. I'm not sure if all the excessive detail was warranted, but better to err on the side of caution as a general principle I believe.
My sincere thanks to everyone for helping me out! You have given me a great introduction to the site and I look forward to any and all future communications.
Sadly, I have a pile of crap to attend to, now I know the phone is working, so I will regather my strength for a fresh attempt at rooting the phone (with DooMLoRD Easy Rooting Toolkit 18 For Sony Xperia Devices), installing a recovery environment (CWM v8 as opposed to v9), then flashing a suitable ROM tomorrow evening. I checked my service menu and it states, "Rooting status: Bootloader unlock allowed: Yes," which I trust opens my options a bit more. The two ROMs I am initially wishing to try are CyanogenMod and KitKat, but would be nice to know I could try others without more problems. I am now also aware to backup the TA Partition via the Android Flash Tool 0.9.13.0 before rooting the phone and assume I should hold off reinstalling my Titanium Backups until I am happy with a particular ROM.
I expect this isn't the place to go over these things (although I am quite happy to do so), so I will start a new thread tomorrow to go over my best plan of action.
Thanks again, and I hope this helps out someone else in the same position!
Click to expand...
Click to collapse
so my idea about vol up button instead of vol down button worked !!!!!!!! . its usually for entering fastboot mode. i just gave a try :silly:
LaZiODROID said:
I think hhamzah49 is the hero who got you going with that nice trick (to get you into flashmode)! I guess it turned out that you didn't have driver issues after all.
Yes. If you're gonna do it, read up (re: backing up your TA, etc.) I have read with bootloader unlocking, you also lose DRM apps like TrackID and the Bravia engine? If you dont use those then you probably won't mind.
Right. There is also the official Sony method of unlocking your bootloader (see the all-in-one thread). Re: ROMS... I guess it's not so much "worrying" about roms like XperimenT/T-Hybrid - they are good roms and they install via CWM recovery just like any other custom ROM, and they will run on an unlocked bootloader. You just have more ROM selection with an unlocked bootloader because you can use the kernels that ROMS like Cyaongen needs.
Read up to be sure - but I see in Flashtool that there is an FTF for bootloader re-locking (but more importantly it is linked in the all-in-one thread also)... so it sounds like it won't be too hard to re-lock if you need to.
Yes so you can back up your TA after rooting? That I'm not certain of. I think that recovery can be installed whether your bootloader is locked or unlocked. For unlocked bootloaders, there are kernels that have recovery built in so you can just fastboot flash one of them.
Click to expand...
Click to collapse
i feel awesome! Good luck trying roms and stuff!
Hello friends, I hope you can help me on this, I'm Venezuelan so I translated this into google, I have an Xperia ZR, the problem is that it does not accept the firmware that put him just begins to reiniciciarse again and again, the one who accepts is the version 4.1.2 but it does not work the phone nor WiFI, also recognizes the Sim Card and placed in the nuemérico keypad * # 06 # not show the IMEI. There will be some solution for this? Is Xperia ZR C5502, they hope can help me.
Eduardo3107 said:
Hello friends, I hope you can help me on this, I'm Venezuelan so I translated this into google, I have an Xperia ZR, the problem is that it does not accept the firmware that put him just begins to reiniciciarse again and again, the one who accepts is the version 4.1.2 but it does not work the phone nor WiFI, also recognizes the Sim Card and placed in the nuemérico keypad * # 06 # not show the IMEI. There will be some solution for this? Is Xperia ZR C5502, they hope can help me.
Click to expand...
Click to collapse
Have you tried repairing your ZR using Sony PC companion? Have you unlocked bootloadter by official or unofficial method without backing up DRM keys and TA partitions?
sourabhp said:
Have you tried repairing your ZR using Sony PC companion? Have you unlocked bootloadter by official or unofficial method without backing up DRM keys and TA partitions?
Click to expand...
Click to collapse
Hello friend, sorry for the time to respond, never try to unlock your bootloader and you try to repair the PC Companion, there will be some form of recueperar my IMEI and thus fix my Xperia ZR ?? Or some way to repair the TA carpetetas? I hope you can help me
Eduardo3107 said:
Hello friend, sorry for the time to respond, never try to unlock your bootloader and you try to repair the PC Companion, there will be some form of recueperar my IMEI and thus fix my Xperia ZR ?? Or some way to repair the TA carpetetas? I hope you can help me
Click to expand...
Click to collapse
I am not able to understand the words like carpetetas or recueperar? you can take your phone to local service center and ask them to see what is wrong. First take backup of your phone like contacts, sms whatsapp data etc. then visit service center. If everything is okay ( DRM Keys and TA partitions ) they will flash latest 4.4.4
If yiu didnvt unlocked the bootloader then try to install arom for ur region but if u unblocked bootloader i think you have lost ta partition so the imei doesn't show up when u call *06#
I think so too. May be you have unlocked bootloader without backing up TA partition and DRM keys thats why you are not able to upgrade your phone to version 4.3 or 4.4.2 or 4.4.4.
There was same question some time back. Someone unlocked bootloader without backing up and now stuck on 4.1.2. Sony refused to help as he lost warranty of the phone by unlocking. He had no knowledge about unlocking and warranty.
sourabhp said:
I think so too. May be you have unlocked bootloader without backing up TA partition and DRM keys thats why you are not able to upgrade your phone to version 4.3 or 4.4.2 or 4.4.4.
There was same question some time back. Someone unlocked bootloader without backing up and now stuck on 4.1.2. Sony refused to help as he lost warranty of the phone by unlocking. He had no knowledge about unlocking and warranty.
Click to expand...
Click to collapse
Greetings from new friend, well I got the phone when using it a while and I andubo pretty well until I skip the update to Android 4.2.2 and in doing so by PC Companion problems began not recnocia the operator sim card and alli what flashee with flashtools but not the phone began to reboot every time. Now the phone will not funcionala network sim card is not detected, does not turn on WiFi, no funcioan the Bluetooth, does not display the IMEI and also in Settings-About Phone, Says Baseband Version Unknown. It will be a logic board problem ???, I substitute another ???
Eduardo3107 said:
Greetings from new friend, well I got the phone when using it a while and I andubo pretty well until I skip the update to Android 4.2.2 and in doing so by PC Companion problems began not recnocia the operator sim card and alli what flashee with flashtools but not the phone began to reboot every time. Now the phone will not funcionala network sim card is not detected, does not turn on WiFi, no funcioan the Bluetooth, does not display the IMEI and also in Settings-About Phone, Says Baseband Version Unknown. It will be a logic board problem ???, I substitute another ???
Click to expand...
Click to collapse
Frankly speaking, I do not understand non-English words that frequently appears in your posts. Having that said, I can pretty much grasp the gist from your posts, although that may not be 100% what you intend to mean. Combined with answers by previous forum members, i offer you suggestions to your problems point by point.
Okay enough of this bull****. First I want to say that if you are unfamiliar with things here on XDA, read the guidelines before you do anything. You probably unlocked the bootloader of your phone, but did not backup anything. In that case, you HAVE to install a kernel everytime you try to switch rom (including a stock-based, or stock for that matter). Your numerous problems above suggests a kernel problem to me. What you do now is to follow UB way to flash a AOSP or whatever rom (not stock) and report if it solved your problems
paulson881 said:
Frankly speaking, I do not understand non-English words that frequently appears in your posts. Having that said, I can pretty much grasp the gist from your posts, although that may not be 100% what you intend to mean. Combined with answers by previous forum members, i offer you suggestions to your problems point by point.
Okay enough of this bull****. First I want to say that if you are unfamiliar with things here on XDA, read the guidelines before you do anything. You probably unlocked the bootloader of your phone, but did not backup anything. In that case, you HAVE to install a kernel every time you try to switch rom (including a stock-based, or stock for that matter). Your numerous problems above suggests a kernel problem to me. What you do now is to follow UB way to flash a AOSP or whatever rom (not stock) and report if it solved your problems
Click to expand...
Click to collapse
He is using google translate to convert his question for us to understand. but google is getting better of him by throwing such smart n hard words at him.
paulson881 said:
Frankly speaking, I do not understand non-English words that frequently appears in your posts. Having that said, I can pretty much grasp the gist from your posts, although that may not be 100% what you intend to mean. Combined with answers by previous forum members, i offer you suggestions to your problems point by point.
Okay enough of this bull****. First I want to say that if you are unfamiliar with things here on XDA, read the guidelines before you do anything. You probably unlocked the bootloader of your phone, but did not backup anything. In that case, you HAVE to install a kernel everytime you try to switch rom (including a stock-based, or stock for that matter). Your numerous problems above suggests a kernel problem to me. What you do now is to follow UB way to flash a AOSP or whatever rom (not stock) and report if it solved your problems
Click to expand...
Click to collapse
Friend regret that I can not understand what I write, I apologize, also thanks for your help, I'll do what you recommended me, be installing a kernel or room cooked AOSP, I have installed the root in the only version that works on my ZR which is 4.1.2, then be installing the Recovery to test a kernel or room. Could you tell me which room should I install? You can give me the links? Thanks in advance for your help
Eduardo3107 said:
Friend regret that I can not understand what I write, I apologize, also thanks for your help, I'll do what you recommended me, be installing a kernel or room cooked AOSP, I have installed the root in the only version that works on my ZR which is 4.1.2, then be installing the Recovery to test a kernel or room. Could you tell me which room should I install? You can give me the links? Thanks in advance for your help
Click to expand...
Click to collapse
CM11 or AOSP based rom, check development section for ZR
sourabhp said:
CM11 or AOSP based rom, check development section for ZR
Click to expand...
Click to collapse
Amigo antes de flashear una room CM11 o Aosp debo abrir el Bootloader?
I searched high and low for solution of my problem but i couldnt find the right solution to my problem that's why I'm starting this thread.
Phone- Xperia Sp C5302
Stock Kernel
Rooted
Philz Touch recovery installed
Nandroid backup made using TWRP
Tried to unlock bootloader- Problem starts from here........
Initially phone rebooted normally but couldn't detect sim and signal.
Then phone started rebooting after few minutes . Stay on for a while then reboot again till battery died.
Now battery not charging, phone showing no life, no led, no vol up+power, vol- power , vol up+vol down+power work
Tried everything I know plz help and plz explain slowly and calmly.
THANKS IN ADVANCE.
EDIT:
Used wall charger 2amp for charging left overnight no red led or anything as described in other posts
Connected to laptop left for about 4 hours no nothing.
Tried to connect in fast boot not detected.
Any more ideas guys at least give some pointer for what to do or is my Sp is actually dead ? And I can't restore my backup? Plz guys help
EDIT: Pressed the small button at the back and the phone came back to life YESSSSS........
Now the phone isn't showing imei no. or sim or network. But when restarted it imei and network came back magically. So I thought the problem is solved to confirm it I switched phone off again then switched on then imei and network gone again and also baseband isn't showing too (I'm sorry if it is the same thing I'm a newb to this stuff)
Then again I restarted the phone number it came again. I don't know what to do in this situation. I just wanted to unlock bootloader and install xenon hd rom in my Xperia Sp.
Zeemanv2 said:
Now the phone isn't showing imei no. or sim or network. But when restarted it imei and network came back magically. So I thought the problem is solved to confirm it I switched phone off again then switched on then imei and network gone again and also baseband isn't showing too (I'm sorry if it is the same thing I'm a newb to this stuff)
Then again I restarted the phone number it came again. I don't know what to do in this situation. I just wanted to unlock bootloader and install xenon hd rom in my Xperia Sp.
Click to expand...
Click to collapse
Try flashing stock ftf with Flashtool.
If the problem gets solved, then start with the new ROM.
Zeemanv2 said:
Now the phone isn't showing imei no. or sim or network. But when restarted it imei and network came back magically. So I thought the problem is solved to confirm it I switched phone off again then switched on then imei and network gone again and also baseband isn't showing too (I'm sorry if it is the same thing I'm a newb to this stuff)
Then again I restarted the phone number it came again. I don't know what to do in this situation. I just wanted to unlock bootloader and install xenon hd rom in my Xperia Sp.
Click to expand...
Click to collapse
Use the method answered by the previous post. But I will add into that
You can use the flashtool to flashing everything stock but please dont flash System and Kernel. If you flashed a custom recovery and want it to stay untick Fotakernel as well.
This should fix your problem without having to deal with the stock ROM.
But if problem persists then I would suggest a complete stock ROM flash.
Huge chance that the process of unlocking your bootloader is faulty. Are you sure that it went without errors? Anyway you might also wanto to try to relock and then unlock the bootloader again
@Zenith I left the phone idle for sometime now it's OK ish . I've made a nandroid backup but can u tell me plz which folder contains imei and other important stuff so I can make a backup of it too.
BTW I think my bootloader is not correctly unlocked coz pc companion is detecting my phone bravia engine is there gracenote is working. But in service menu under configuration I found: Bootloader unlocked: Yes.
Previously it was Bootloader unlock: Yes. So is it unlocked or not if not then how to unlock?
I've followed sony's official unlocking method.
Zeemanv2 said:
@Zenith I left the phone idle for sometime now it's OK ish . I've made a nandroid backup but can u tell me plz which folder contains imei and other important stuff so I can make a backup of it too.
BTW I think my bootloader is not correctly unlocked coz pc companion is detecting my phone bravia engine is there gracenote is working. But in service menu under configuration I found: Bootloader unlocked: Yes.
Previously it was Bootloader unlock: Yes. So is it unlocked or not if not then how to unlock?
I've followed sony's official unlocking method.
Click to expand...
Click to collapse
You don't need to backup imei. It will stay the same no matter what ROM you use.
and You can use Titanium Backup to backup all your important apps and data. But do not backup/restore system apps.
and in the service menu;
"Bootloader Unlock allowed - Yes" means that your Bootloader is Locked, and you can unlock it.
"Bootloader Unlocked - Yes" means that your Bootloader is unlocked.
Bravia engine shouldn't work if your BL is unlocked, so something must have gone wrong in the process.
Follow what's said in post #4.
@Zenith Thank you for your wonderful suggestion i will do as u say. bt one big noob ques- Do i have to dload a ftf file to flash to stock cant i use my backup or someyhing from it to restore?
@TechnoSparks yeah i think you are right about my bootloader bt isnt there something to check if BL is unlocked correctly. Btw when i requested to unlock BL in fastboot nothing really happened apart from
<Bootloader > Unlock phone requested
OKAY [15.725s]
finished. total time: 15.725
Then restared approx every 10 min or so till battry went flat and phone being dead untill i reseted it via pin
Zeemanv2 said:
@Zenith Thank you for your wonderful suggestion i will do as u say. bt one big noob ques- Do i have to dload a ftf file to flash to stock cant i use my backup or someyhing from it to restore?
Click to expand...
Click to collapse
Yes, you have to download the ftf file.
Use this one.
and don't use the latest version of Flashtool, use the "0.9.18.5" version.
@Zenith Thanks bro bt my model is C5302 will it be compatible?
And i just dloded 0.9.18.6 version. its not latest 0.9.19.0 ver is latest.
So do i have to dload again? (connection limited bandwith n slow speed)
@Zenith Sorry bro for bugging you again n again bt u r the only person who showed some intrest in this post and helping me.
Btw ive founded this"https://drive.google.com/file/d/0B-mh6JO-ztBfaGZ6UE1QanFzRTg/edit?usp=sharing" C5302 Indian generic 12.1.A.1.201 [FTF] Is it better?
Zeemanv2 said:
@Zenith Thanks bro bt my model is C5302 will it be compatible?
And i just dloded 0.9.18.6 version. its not latest 0.9.19.0 ver is latest.
So do i have to dload again? (connection limited bandwith n slow speed)
Click to expand...
Click to collapse
You should flash ftf specified for C5302 then.
Download the C5302 variant that you prefer from here.
And try flashing with the Flashtool you have. If it doesn't work properly, then uninstall it, and install the 0.9.18.5 version.
Some members including me faced some problems on the next 2 versions of flashtool. So yeah..
---------- Post added at 01:26 AM ---------- Previous post was at 01:24 AM ----------
Zeemanv2 said:
@Zenith Sorry bro for bugging you again n again bt u r the only person who showed some intrest in this post and helping me.
Btw ive founded this"https://drive.google.com/file/d/0B-mh6JO-ztBfaGZ6UE1QanFzRTg/edit?usp=sharing" C5302 Indian generic 12.1.A.1.201 [FTF] Is it better?
Click to expand...
Click to collapse
It's okay
And as I have a different model, I can't actually assure you that it works or not.
So try and see what happens.
Thanks bro will surely let u know.
Zeemanv2 said:
@Zenith Sorry bro for bugging you again n again bt u r the only person who showed some intrest in this post and helping me.
Btw ive founded this"https://drive.google.com/file/d/0B-mh6JO-ztBfaGZ6UE1QanFzRTg/edit?usp=sharing" C5302 Indian generic 12.1.A.1.201 [FTF] Is it better?
Click to expand...
Click to collapse
Even you can flash C5303 ftf on C5302. I personally use Singapore variant .207. It has got least bugs and it is fast and much bloatware free.
P.S. Dont flash .201 it has got a lot of bugs.