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 everybody,
I'm new to all this stuff (I've never rooted or flashed my device before) so I would be really glad if someone could take their time to explain some things to me
About a month ago I decided to, after some time of consideration, upgrade the firmware of my Xperia Z1 to Lollipop (I previously had KitKat 4.4.4 installed). I upgraded solely because I wanted to be able to move apps (not just pictures and videos) to my SD card, which was, as we all know, something we couldn't easily do in KitKat without rooting. Even though I disliked basically everything else about Lollipop (including the new all-too-bright UI design, the unnecessarily large app icons and the lockscreen notifications) I decided to update to Lollipop, just to get the additional SD card functionality. I thought: "Oh well, I'll get used to it" and "It's probably something I can adapt to."
So I updated the firmware to Lollipop - and what a big mistake! HAHA, it's ludicrous! My device has become awful as its battery is draining super fast (from doing nothing but the regular stuff I've always done on my phone - and sometimes - from doing basically nothing at all), and as the device gets overheated all the time (again, from just doing the normal stuff - and sometimes - from doing absolutely nothing). Very soon I decided to do a factory reset, hoping it would change things. It didn't. I'm still experiencing annoying power draining issues and ridiculous overheating issues on my Z1.....
So, lately I've been reading and watching a lot about stuff like rooting, flashing and custom ROMs - things I barely knew anything about before. And what I'm currently thinking about is to flash my Z1 with the KitKat firmware I had prior to updating, so I can make things the way they were before (in other words: I want to downgrade the firmware). And then I think I'll install a custom ROM like SlimKat or iHackers to make my Z1 perform even better than before, and to get all those other benefits you get from rooting (like all those added features and settings, yay!)
Alright, so that was a bit about the background and the reason I want to do this...and here comes the questions I have right now:
Do I need an unlocked bootloader in order to flash my Xperia Z1 C6903? Sony's webpage about flashtools says that I need a unlocked bootloader in order to flash, but I've read on threads here on the XDA Xperia Z1 forum that I don't...what is right?
What are the right tools to flash my device and where do I find them?
Does it matter what/which build version I choose to flash to? I'm currently running Android 5.0.2 (14.5.A.0.270) and I want to downgrade to Android 4.4.4 and, if it matters, the version I had before upgrading to Lollipop. I think it was 14.4.A.0.157 but it might as well have been 14.4.A.0.108 or something else.
I'm asking all these things is because I really want to minimize the risk of bricking my device or causing any damage to the device that could have been avoided whatsoever. I've read many threads here on XDA, watched videos on YouTube among other things, but I'm still not sure about the things I asked above. Thanks in advance for being helpful! :good:
Best regards,
Andee23
no you don't need to unlock your bootloader for downgrading, actually don't play with bootloader if you will stay on stock(drm stuff)
you need right ftf file and flashtool, you need to see some user experiences for best build. there is no risk of bricking when you are flashing ftf(with right model number though).
http://www.flashtool.net/downloads.php just download flashtool from here
find the best suitable ftf for you from here http://forum.xda-developers.com/showthread.php?t=2469191
shut down your phone, open flashtool press on lightning symbol, choose flashmode, find the ftf you downloaded. press flash. wait for it to prepare files. when it asks for you to connect it, connect the usb cable while you are pressing volume down button. the process will start automatically. when it finishes. remove the usb cable open the device. press reply button above for further questions. thanks
cimihendriks said:
no you don't need to unlock your bootloader for downgrading, actually don't play with bootloader if you will stay on stock(drm stuff)
you need right ftf file and flashtool, you need to see some user experiences for best build. there is no risk of bricking when you are flashing ftf(with right model number though).
http://www.flashtool.net/downloads.php just download flashtool from here
find the best suitable ftf for you from here http://forum.xda-developers.com/showthread.php?t=2469191
shut down your phone, open flashtool press on lightning symbol, choose flashmode, find the ftf you downloaded. press flash. wait for it to prepare files. when it asks for you to connect it, connect the usb cable while you are pressing volume down button. the process will start automatically. when it finishes. remove the usb cable open the device. press reply button above for further questions. thanks
Click to expand...
Click to collapse
OK so I just downloaded flashtool via your link. But a message comes up telling me that the file is malicious and that Chrome has blocked it. What should I do?
Also, I checked the forum link you sent me. Found this link for my model (C6903). The newest ftf file I can download from there is 14.4.A.0.108. But after googling I found that this site can provide me the .157 (14.4.A.0.157) version. Would you recommend me to download that build version instead?
By the way, do I need to remove the SD card before I flash (and later on root) my Xperia Z1?
Best regards,
Andee23
Andee23 said:
OK so I just downloaded flashtool via your link. But a message comes up telling me that the file is malicious and that Chrome has blocked it. What should I do?
Also, I checked the forum link you sent me. Found this link for my model (C6903). The newest ftf file I can download from there is 14.4.A.0.108. But after googling I found that this site can provide me the .157 (14.4.A.0.157) version. Would you recommend me to download that build version instead?
By the way, do I need to remove the SD card before I flash (and later on root) my Xperia Z1?
Best regards,
Andee23
Click to expand...
Click to collapse
That is a chrome secutiy thingy, you can disable it somewhere in settings.
You can download any build version you want i don't know which is best for z1 actually. You may want to backup your internal storage. External should be fine.
cimihendriks said:
That is a chrome secutiy thingy, you can disable it somewhere in settings.
You can download any build version you want i don't know which is best for z1 actually. You may want to backup your internal storage. External should be fine.
Click to expand...
Click to collapse
Alright. So do you know why Chrome says it's malicious?
And one last question before I'm ready: By saying "you may want to backup your internal storage" do you mean I should backup the entire stock ROM or just personal files I want to keep?
Best regards,
Andee23
Andee23 said:
Alright. So do you know why Chrome says it's malicious?
And one last question before I'm ready: By saying "you may want to backup your internal storage" do you mean I should backup the entire stock ROM or just personal files I want to keep?
Best regards,
Andee23
Click to expand...
Click to collapse
chrome doesn't even control it, so don't be afraid. it only tells it with some kind of filetypes without looking the file(exe,zip etc)
no, just personal files, it won't be deleted, but caution is important
cimihendriks said:
chrome doesn't even control it, so don't be afraid. it only tells it with some kind of filetypes without looking the file(exe,zip etc)
no, just personal files, it won't be deleted, but caution is important
Click to expand...
Click to collapse
Hello again! I've tried three times now...the flashing doesn't work. I changed some details every time I tried but I still got the same error messages. Here's (part of) one of the logs...what does this mean and how do I solve it?
24/014/2015 20:14:22 - INFO - Selected Bundle for Sony Xperia Z1 (C6903). FW release : 14.4.A.0.157. Customization : BAL
24/014/2015 20:14:22 - INFO - Preparing files for flashing
24/015/2015 20:15:50 - INFO - Please connect your device into flashmode.
24/016/2015 20:16:02 - INFO - Device disconnected
24/016/2015 20:16:37 - INFO - Device connected in flash mode
24/016/2015 20:16:37 - INFO - Opening device for R/W
24/016/2015 20:16:38 - INFO - Start Flashing
24/016/2015 20:16:38 - INFO - Processing loader.sin
24/016/2015 20:16:38 - INFO - Checking header
24/016/2015 20:16:38 - ERROR - Processing of loader.sin finished with errors.
24/016/2015 20:16:38 - INFO - Ending flash session
24/016/2015 20:16:38 - ERROR -
24/016/2015 20:16:38 - ERROR - Error flashing. Aborted
24/016/2015 20:16:38 - INFO - Device connected in flash mode
24/017/2015 20:17:09 - INFO - Device disconnected
have you installed flashtool drivers seperate from flashtool itself?
http://forum.xda-developers.com/showthread.php?t=2635830
cimihendriks said:
have you installed flashtool drivers seperate from flashtool itself?
http://forum.xda-developers.com/showthread.php?t=2635830
Click to expand...
Click to collapse
No, I haven't. I installed the drivers needed from the installer program that was found in the "drivers" folder in the flashtool program folder.
Andee23 said:
No, I haven't. I installed the drivers needed from the installer program that was found in the "drivers" folder in the flashtool program folder.
Click to expand...
Click to collapse
install from here, you should choose first two, and your device when installing.
try again after that
cimihendriks said:
install from here, you should choose first two, and your device when installing.
try again after that
Click to expand...
Click to collapse
I'm still stuck with the error message "Processing of loader.sin finished with errors". After googling it I can see that message has showed up to a lot of people. And unfortunately neither I nor people on the google results can find a clear fix to the error...
Yee-haw! I'm happy to announce that I have successfully flashed KitKat 4.4.4 my lovely Xperia Z1!
I even managed to succeed on my first attempt today! It was very easy to solve the problem: I deleted the ftf file from my computer and then I re-downloaded it
I think that the fact that I downloaded it from Mega instead of Google Drive might have played an important role, too
Wow, I've really missed KitKat - everything is so good-looking and it works like a charm! And the battery draining and temperature problems are gone!
@cimihendriks
Thanks a lot for your help!! You're awesome
One more thing: after that the flashing had finished and I was told to unplug the device there was a line in the Flashtool log saying "For flashtool, Unknown Sources and Debugging must be checked in phone settings". I didn't check those settings in my phone before I started the flashing procedure - should I be worried?
Glad it worked out for you! no, flashtool doesn't do stuff in android. flashmode and fastboot modes are seperate from system. don't get worried. Enjoy!
that's easy
i already do that ! 2day i have no prob i downgrade from 5.0.2 to 4.4.4 than to 4.3 than i back to 5.0.2 again
but i stay get no IMEI / NULL
i can't fix thaty
benniche farid said:
i already do that ! 2day i have no prob i downgrade from 5.0.2 to 4.4.4 than to 4.3 than i back to 5.0.2 again
but i stay get no IMEI / NULL
i can't fix thaty
Click to expand...
Click to collapse
does your network work?
cimihendriks said:
does your network work?
Click to expand...
Click to collapse
yeah i solve the prob & i make video about to help others
https://www.youtube.com/watch?v=wo4rF7KENAA
Hi,
I always found it saddening to notice EZCast5G (the "original") is updated at first and their knock offs are updated way later (as of writing this, there is 16602000 for EZCast5G, 16403000 for MiraScreen5G).
The update tool let's you easily analyze the update process. And if you fake the reply from this URL with (for example) miniweb to always dish out latest EZCast5G firmware then your knock off will become an original.
These are the requests made for a legit EZCast5G and a MiraScreen5G:
Code:
[COLOR="Purple"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"ezcast5g\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16602000\"}"[/COLOR]
[COLOR="Blue"]curl http://www.iezvu.com/upgrade/ota_rx.php -d "{\"version\":1,\"vendor\":\"am8252_nand_mirascreen\",\"mac_address\":\"authorshxj\",\"softap_ssid\":\"000000-00000000\",\"firmware_version\":\"16403000\"}"[/COLOR]
These are the official replys where you need to always dish out the first one and the update tool will do the rest:
Code:
[COLOR="Purple"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}[/COLOR]
[COLOR="Blue"]{"ota_conf_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/am8252_nand_mirascreen/am8252_nand_mirascreen-16403000.gz","ota_enforce":true}[/COLOR]
When I opened mine it even read "5G EZCAST V1.4" on it - so I was pretty sure it should work. And it did. So for $17 one year ago I got myself a neat working EZCast5G. The MiraScreen5G gets into bootloader mode by pressing the one and only button right when you plug it into USB - no need to shorten pin 19 and 20 of the AM8252.
Thank you.
Some questions.
How to use this curl command with miniWeb?
Hi,
BUMP
No honestly, could you elaborate how this works ? Have 2 MiraScreen5G dongles...
Ender
Hi,
with some help from Chatty and another forum i got it done !
First i needed to add a line to my hosts file:
(On windows its found in C:\Windows\System32\drivers\etc)
Code:
127.0.0.1 www.iezvu.com
Then i downloaded miniweb and created a file containing the desired server answer.
Miniwebs web root resides in the "htdocs" folder by default, so i created a folder named "upgrade" and in that folder a file named "ota_rx.php.
I edited that file to contain this text:
Code:
{"ota_conf_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.conf","ota_fw_file":"http://cdn.iezvu.com/upgrade/ezcast5g/ezcast5g-16602000.gz","ota_enforce":true}
I fired up miniweb with the parameter "-p 80" to listen on the stabdard web port.
THEN i started the EZ Updater app, connected my dongle in Flash mode and VOILA it detected the version i wanted it to detect.
So it flashed (took forever with several loops) my MiraScreen5G to a EZCast5G !!!!
After that initial update the dongle detected a newer version and updated okay.
Please note that AFTER the update you cannot get into flash mode by simply pressing the key. I assume that key is not considered existing anymore since the EZCast5G has none as well
So for further flash-fun we need to short the Pin like its descived by Chatty !
THANKS Chatty & all,
Ender
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
SweenWolf said:
Hey Guys,
If someone knows, please share the knowledge.
Few Months ago when I was updating the firmware, my Dongle died due to power cut.
after reconnecting my PC couldn't read the version of my dongle. Today I wanted to revive my Dongle But have no to little experience on the Windows Debugging. I know my Dongle is not dead and it has no firmware, I also know that EZCast Repair tool can Flash the Firmware to it, I can download the firmware using the OP, I can also see that The App has options for Manually flashing the Firmware.
But I don't know how and what to do to access the areas shown in the Screenshot.
anyone please help me and point me to right direction.
Thanks in Advance.
Click to expand...
Click to collapse
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
dLightas said:
Have you found any help? I have updated to EzCast firmware but now my dongle doesn't appear on wifi list and on TV only shows EzCast logo..
Click to expand...
Click to collapse
No I found no help.
All I need is access the flashing area.
I had 2 tools laying around (think i deleted those)
One was older and directly opened the firmware flashing page, but that doesn't have the partition table of My Dongle.
And the other tool which have the partition table, opens on main page (which is automated and does nothing)
If somehow i could access the firmware flashing area on the newer tool then I could revive my dongle.
If your dongle contained older chip of Action Electronics (earlier than 52) then the older tool can flash your dongle.
nostupidthing said:
Just opened a K6 mirascreen and found these
nanya nt5cb64m16fp-dh 128mb ddr3 ram
am8272
samsung k9f1g08u0d 16mb flash
the pcb reads S?-EZCAST-8271-V2F
im unable to find a suitable firmware for it and no idea how to enter download mode....
---------- Post added at 06:02 PM ---------- Previous post was at 05:35 PM ----------
the firmware says 1.3707.11 btw
Click to expand...
Click to collapse
Today there was a firmware upgrade available and after updating it's dead any help
Edit: OK I was able to flash using this tool (https://mirascreen.com/pages/repair-tool-for-chip-8272-products) but still nothing comes up...
Edit 2: The new firmware is 1.10505.52
MiraScreen G9 Plus
=================
[Name Model] , [Vendor String] , [Supported of the "MiraScreen G9 Plus"]
(EZCast5G) - ezcast5g - Not supported
(MiraScreen5G) - am8252_nand_mirascreen - Not supported
(EZCast 2H) - am_8270_ezcast4k-dongle_ezcast2h - Not supported
(EZCast TX) - am_8270_ezcast-tx_nand-std - Not supported
(EZCast 2) - am8271_ezcast2K - Not supported
(EZCast 4K) - ezcastduo - Not supported
(EZCast Band1) - am_8271_ezcast2-dongle_b1 - Not supported
(EZCast Ultra) - am_8275_ezcast-dongle_ultra - Not supported
(AnyCast M100) - sage_8272_mirascreen-dongle_anycast - Supported
(MiraScreen K6) - am_8272_mirascreen-dongle_std - Supported
Check Firmware over http api:
https://api.ezcast.com/api/firmware...mirascreen-dongle_std&firmware_version=1.10.3
https://www.ezcast.com/service/ota/..._8272_mirascreen-dongle_std&rx_version=1.10.3
Current official firmware version for the "Mirascreen G9 Plus": 1.10505.61
Do you know others? I would for the model "Mirascreen G9 Plus"?
"Mirascreen G9 plus" supports alternative Firmware (Firmware tested on the "MiraScreen G9 Plus"):
FW v1.13610.47: http://cdn.iezcast.com/upgrade/am_8...dongle_std_official-1.13610.47-0x99A7C4FD.img
Flash Tool: https://cdn.shopify.com/s/files/1/0017/6553/9884/files/MiraScreen_8272_Repair_Tool.rar
FW v1.10505.3: http://cdn.iezcast.com/upgrade/sage...gle_anycast_official-1.10505.3-0x937AC2AD.img
Flash Tool: https://cdn.shopify.com/s/files/1/2427/2515/files/AnyCast_M100Repair_Tool.zip
Small modification of Wi-Fi antenna:
https://forum.xda-developers.com/t/mirascreen-g9-plus-hw-fw-mods.4391225/
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Anton TNT said:
Hi to all, can anyone help me please with my EZ mira app and dongle device associated with it (miracast).
I have tried to upgrade software for my miracast device thru EZmira app, but suddenly Commercials pop up and my upgrade has been stuck at 10% and won't go further , worse after disconnect or reset there is no signal at all anymore it does not start /boot nor emmit wifi signal. What to do (because of stupid commercial)??
I tried to reset device several times but nothing, tried reseting thru PC but it does not load or Windows does not recognoze device to upgrade it thru web tools.
Please can anyone get that firmware back in my device and restore it .
Much appriciated and thanks in advance!
Click to expand...
Click to collapse
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
renda-l said:
Do you have a specific device?
Manufacturing publishes tools to restore some firmware here:
EZCast: https://www.ezcast.com/repair
MiraScreen:
https://mirascreen.com/pages/repair-tool-for-chip-8268-8252-products
https://mirascreen.com/pages/repair-tool-for-chip-8272-products
AnyCast:
https://any-cast.com/pages/repair-tool-for-chip-8268-8258-products
https://any-cast.com/pages/repair-tool-for-chip-8272-products
Click to expand...
Click to collapse
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Anton TNT said:
I have trided this solution , but no prevail, like device is dead, nothing just blank screen after failed update
Click to expand...
Click to collapse
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
renda-l said:
This procedure works 100%, completely restores the firmware. If only an incorrect update occurred.
Click to expand...
Click to collapse
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Anton TNT said:
I'm not shure maybe I'm doing something wrong, but even windows doesn't recognize device
Click to expand...
Click to collapse
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
renda-l said:
Yes, of course, if the firmware is faulty, the device is not recognized and does not work. You must follow the Firmware Recovery Procedure. The device will most likely be repaired. Unfortunately, unless you specify a specific type, you can't be specifically advised on how to proceed.
Click to expand...
Click to collapse
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Anton TNT said:
It is MIRACAST, I dont know chip number but it is dongle type round shaped eith EZmira app controlled
Click to expand...
Click to collapse
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
renda-l said:
Set your device to Recovery mode according to the procedure and use the tool for chip 8268/8252 or 8272. If the response is "device connected", it is a given chip set.
Click to expand...
Click to collapse
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Anton TNT said:
on which side is pin 7 and 8 ? Chip on my board is square shaped and got pins on all sides. Just to be sure not to fry anything, which side is NAND memory
Click to expand...
Click to collapse
If your device has a button, first try to enter recovery mode, press the button and connect USB.
In the procedure is a photo of the MCU and these pins are shown.