Related
Hi guys, I have found a workaround for those having trouble with installing drivers for fastboot in Windows7. This process requires you to do things in the right order and to be quite fast during some steps, so it may take a couple of goes to understand what you are doing before you nail it. First let me explain what seems to be the problem, to help you understand the method I about about to share with you:
It seems that if the drivers aren't installed in Windows7, the Xperia S will disconnect from fastboot mode, and go back to charging. What we need to do is install drivers in this small time period it does connect to your computer.
The solution to this problem will involve being quick at two stages of this process and I will note where these times are as best I can.
Both these stages are when we connect the phone to the computer in Fastboot mode.
Steps to install drivers:
1. Open device manager
2. Connect you phone in fastboot as normal
3. As soon as you plug your device in, ignore any messages stating the driver did not install and look in device manager for the new device 'S1Boot Fastboot' . Right click this and click 'update driver'. This is the first stage you need to be quick at. As soon as you click this and the update driver window pops up you can relax! You can let go of the volume up button now also, as the device will disconnect in the background anyway! You can also unplug the phone now too.
[NOTE: If windows is still trying to install this device, you won't see update driver until it stops/fails. This is when you have a few seconds to click update driver, so be quick!]
4. Click 'Browse my computer for driver software'
5. Click 'Let me pick from a list of device drivers on my computer'
6. Click next with 'Show All Devices' highlighted
7. Click 'Have disk'
8. Click 'Browse'
9. Go to the the .inf file and open it
10. Click 'ok'
11. You will now have a list of three models. Select 'Android Bootloader Interface'. (It is easy to miss this step out and accidently choose the default model so make sure to select it correctly!)
12. BEFORE you click next, we need to get the phone connection ready again, this is the second stage where quick actions are required.
Disconnect you phone if you already haven't. Connect the phone once more in Fastboot mode. As soon as it is connected click next on the window to install drivers
13. If you followed this right you will have installed drivers before the phone had time to disconnet
14. Now that the drivers are installed for the Xperia S, it will no longer disconnect from fastboot mode and work as it should!
Now contiune to follow Sony's guide
I hope this helps you fellow Xperia S users that have problems!
The solution has already been found and posted. I know you mean well, but use search
http://forum.xda-developers.com/showthread.php?t=1527159
For Win7 x64, the Arc drivers are needed otherwise it appears the drivers aren't read properly.
For Arc drivers see last page as the first post isn't updated yet.
Thanks! Was looking for this
Sent from my LT26i using XDA
Also, for 64bit system, make sure in the android_winusb.inf you have the following entry under [Google.NTamd64].
; SonyEricsson
%SingleAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
%CompositeAdbInterface% = USB_Install, USB\VID_0FCE&PID_0DDE&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0FCE&PID_0DDE
Apparently some versions of the inf only have that under [Google.NTx86].
You can copy and paste it in the same format as the rest of the entries.
shmoejoe said:
The solution has already been found and posted. I know you mean well, but use search
http://forum.xda-developers.com/showthread.php?t=1527159
For Win7 x64, the Arc drivers are needed otherwise it appears the drivers aren't read properly.
For Arc drivers see last page as the first post isn't updated yet.
Click to expand...
Click to collapse
Sorry. I don't need to use search as I already read (and just re-read) this post and still had problems.
And seeing as this is a different solution, and quite detailed for those not too familiar with Windows, it may help.
Even means users can use the files all from the official sites. If users search for this in the future, member posted files may be deleted, like I have found on numerous occasions.
Next time, I'll keep it to myself
No reason not to share it. it is a bit easier to read through than dooms instructions, just don't open threads when it could have been easily put in the existing thread
Sent from my LT26i using XDA
I see
I guess I should have stated, but I couldn't reply to the thread as it is in the dev section and I have less than 10 posts
I would usually help more, but usually with the amount of time I have to browse the forums and after searching, someone already has a solution! I guess this is only a good thing!
Maybe it could be added or linked to if necessary
Thank you footyfanatic:
Do you mind if I translate your solution and I post it in HTCMania? a user of that forum is having problems to install his phone's drivers.
Yes this will be fine
Not work for me..phone continue to disconnect on my eeebox (work percect and bootloader unlock on my main PC) WHY ,_;
On eeebox Win 7 home premium 32 bit
On main Win 7 ultimate 64 bit
EDIT UPDATE
Worked for me if I select Android ADB interface and not Android Bootloader Interface
You saved my life! Many thanks!
Thanks a lot! been trying for days and i dont have any XP machine,
Regards! ^_^
Evil_Sephiroth said:
Not work for me..phone continue to disconnect on my eeebox (work percect and bootloader unlock on my main PC) WHY ,_;
On eeebox Win 7 home premium 32 bit
On main Win 7 ultimate 64 bit
EDIT UPDATE
Worked for me if I select Android ADB interface and not Android Bootloader Interface
Click to expand...
Click to collapse
Yes sir! you are right! ADB interface worked
Best Answer
I have searched for this answer all over the net and no one has answered this problem to install fastboot better than this person.
Thanks a lot.
I can't seem to get it. Under what category in device manager does it appear on when you plug it in?
Small Info
I followed all the steps and I thought the drivers installed properly but after getting the key and trying to get into fastboot mode, I faced same problem it went into charging. then I tried repeating the same steps but with one change.
I selected Android ADB interface and not Android Bootloader Interface and it worked like a charm.
Sorry if this is dumb (probably is as others have had no problem) but I am attempting this and am stuck on step 9. When I click browse, the System32 folder opens and I dont know which .inf to open. Is there a specific location and filename.
footyfanatic said:
7. Click 'Have disk'
8. Click 'Browse'
9. Go to the the .inf file and open it
10. Click 'ok'
Click to expand...
Click to collapse
Griggs88 said:
Sorry if this is dumb (probably is as others have had no problem) but I am attempting this and am stuck on step 9. When I click browse, the System32 folder opens and I dont know which .inf to open. Is there a specific location and filename.
Click to expand...
Click to collapse
Before you got to my walk through, you would have been following this guide from Sony: http://unlockbootloader.sonymobile.com/instructions
It is at step 10 which mentions the .inf file
I guess I should have made it more clear and told you to refer back to the Sony guide and where you have that file stored
it really works, I really thank you
I'm having a problem here. Mine is x64
Whichever option I select it says Windows cannot find the file specified, what do I do?
This is the hardest damn thing I have ever done.... trying to root the DNA. It is insane how hard it is, can someone PLEASE do a step by step on how to install Sense 5? Every walkthrough is just not helpful at all and doesn't make any sense.
Theres like 10000 steps and each step has 100 problems and I google the problems and get stuck at every step... I have rooted the S3 so easily w/ in 1 hour but this is just insane....
I know I need to 1) Unlock Bootloader 2) Root 3) S-off
I have tried every one of the above steps and am stuck at one point or another in every point.... Unlocking the bootloader I am stuck because my computer cant recognize my device in bootloader mode. When I type "fastboot oem readcid" it just gets stuck at "waiting for device" I have tried everything and it still doesnt recognize the device....Theres so many people with this problem but no solution.
Is there anyone around San Francisco that will upgrade me to Sense 5 for $20?
ok so first off does you phone have the OTA sofware.. settings>about>software... if your software has 2.04 in it then you won't be able to root at this time..
if your not on the OTA then you should be able to unlock>root>s-off
your obviously having driver issues.. what version of windows are you using?
here are the drivers that I use, i would uninstall all HTC Sync stuff and reboot (basically try and clean out any drivers that could be conflicting)
then try the drivers in this zip file.. I put the phone in bootloader mode first then attach to computer and when i asks about drivers point it to where you unziped the drivers below..
http://db.tt/kr11CT4d
check out the thread I wrote up on how to do this. You can follow all those steps and just use the Sense 5 ROM instead of the ViperDNA ROM I cite. You might have to flash the cubed kernel separately first if it's not packaged with the ROM, but that's not hard to do.
The "waiting for device" means you don't have adb setup correctly. 9 times out of 10 it's because you don't have the drivers. If you have the OTA update you can't unlock the bootloader yet.
Hi Guys,
I do not have the OTA Update, I am running Straight talk and got my phone like 4 months ago, never updated.
I am running Windows 8 on a Samsung Series 9.
I tried the drivers you linked above but I get the same error....see attached photo
I will try your walk though now. I like it a lot... I was about to give up.... nothing is worth this much trouble...Its like problem after problem after problem. lol
Thanks for the help..
irockthebear said:
Hi Guys,
I do not have the OTA Update, I am running Straight talk and got my phone like 4 months ago, never updated.
I am running Windows 8 on a Samsung Series 9.
I tried the drivers you linked above but I get the same error....see attached photo
I will try your walk though now. I like it a lot... I was about to give up.... nothing is worth this much trouble...Its like problem after problem after problem. lol
Thanks for the help..
Click to expand...
Click to collapse
I'm running windows 8 and just had to use a different USB port, 2.0 I think. Do you know how to boot in fastboot? Then did you download adb? There are a few simple commands to get id token, then copy, goto htcdev (google) paste your idtoken after you register. That's step one, unlock the bootloader, in the 1.15 FW
if you need help email me [email protected] Ill check in 5 minutes
SHANENATAS said:
I'm running windows 8 and just had to use a different USB port, 2.0 I think. Do you know how to boot in fastboot? Then did you download adb? There are a few simple commands to get id token, then copy, goto htcdev (google) paste your idtoken after you register. That's step one, unlock the bootloader, in the 1.15 FW
if you need help email me [email protected] Ill check in 5 minutes
Click to expand...
Click to collapse
See attached.
This isnt working.... it says FASTBOOT USB on my phone but on my computer it doesnt recognize the device, I tried every USB port and when I plug it in it just fails and lags at installing device...
irockthebear said:
This isnt working.... it says FASTBOOT USB on my phone but on my computer it doesnt recognize the device, I tried every USB port and when I plug it in it just fails and lags at installing device...
Click to expand...
Click to collapse
1. jump on a windows 7 computer 32 or 64 bit the same as the windows 8 computer
2. download this the htc drivers HTCDriver install them
3. go to C:\Program Files (x86)\HTC\HTC Driver copy the files and put them on the windows 8 computer
4. windows key + r to open the device manager then look under the other devices right click htc than update driver
5. click browse my computer for driver software then browser and find the drivers from the windows 7 computer
6. it well install and work fine
http://forum.xda-developers.com/showthread.php?t=1775870
Try that. I'm going to keep checking this until you get it.
I have to tell ya, if you're on 1.15FW get those drivers to work and unlock the bootloader, then root, and S-off if you like. You will be much happier.
SHANENATAS said:
1. jump on a windows 7 computer 32 or 64 bit the same as the windows 8 computer
2. download this the htc drivers HTCDriver install them
3. go to C:\Program Files (x86)\HTC\HTC Driver copy the files and put them on the windows 8 computer
4. windows key + r to open the device manager then look under the other devices right click htc than update driver
5. click browse my computer for driver software then browser and find the drivers from the windows 7 computer
6. it well install and work fine
http://forum.xda-developers.com/showthread.php?t=1775870
Try that. I'm going to keep checking this until you get it.
I have to tell ya, if you're on 1.15FW get those drivers to work and unlock the bootloader, then root, and S-off if you like. You will be much happier.
Click to expand...
Click to collapse
OMG IT WORKED THX, I will probably get stuck in like 20 seconds on the next step.
Sweet, I'll keep checking here to see if you get stuck or have questions. I'll help if I can, glad you got it!
irockthebear said:
OMG IT WORKED THX, I will probably get stuck in like 20 seconds on the next step.
Click to expand...
Click to collapse
Now I get this....
irockthebear said:
OMG IT WORKED THX, I will probably get stuck in like 20 seconds on the next step.
Click to expand...
Click to collapse
Here are some commands I use. There are great "how to" videos here if you search.
cd c:\fastboot
fastboot oem readcid
fastboot flash recovery recovery.img
adb reboot bootloader
fastboot boot boot.img
fastboot oem lock
fastboot oem get_identifier_token <--------------------- you want this AND
fastboot flash unlocktoken Unlock_code.bin <----------this after you register @htcdev and enter your token
fastboot reboot
irockthebear said:
Now I get this....
Click to expand...
Click to collapse
Im going to try to do this on my HP Envy 4T Windows 7 Device
irockthebear said:
Now I get this....
Click to expand...
Click to collapse
Try switching USB ports, I have only 3 on this laptop, the 2 on the left wont work, but the one on the right does. This is new laptop it has todo with usb version or speed
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
irockthebear said:
Now I get this....
Click to expand...
Click to collapse
Do the same thing on your Envy for the drivers and maybe restart if you get the code 10 again, it might be that simple
http://pcsupport.about.com/od/findbyerrormessage/a/code-10-error.htm
SHANENATAS said:
Try switching USB ports, I have only 3 on this laptop, the 2 on the left wont work, but the one on the right does. This is new laptop it has todo with usb version or speed
---------- Post added at 05:31 PM ---------- Previous post was at 05:28 PM ----------
Do the same thing on your Envy for the drivers and maybe restart if you get the code 10 again, it might be that simple
http://pcsupport.about.com/od/findbyerrormessage/a/code-10-error.htm
Click to expand...
Click to collapse
FML I unlocked the bootloader took like 20 seconds on Windows 7, its because it was windows 8 that everything was buggin out.... wth
Sweet, I'm happy and jealous. Hope everything else goes smooth. For your recovery I like CWMR-6.0.2.8. But to each his own. I'll check here in a little bit, I'm hoping someone figures out a way to unlock the bootloader or downgrade soon so I can be rooted once again.
irockthebear said:
FML I unlocked the bootloader took like 20 seconds on Windows 7, its because it was windows 8 that everything was buggin out.... wth
Click to expand...
Click to collapse
Edit- NM figured it out. Thanks.. wow
irockthebear said:
Hey Guys,
So now when I type the "fastboot flash recovery recovery.img"
It keeps saying "error cannot load 'recovery.img': Unknown error
Click to expand...
Click to collapse
did you put the recovery in the right folder? if the img you're going to use ins't named recovery.img you need to change the name or vise versa in cmd. Get what I'm saying?
Following the TUT is great, but sometimes when we download what we need it might be named different. Like mine is DNA.CWR6.img, so first I put that file in my adb folder, second in the cmd window I type "fastboot flash DNA.CWR6.img" OR do it how you are doing it but rename DNA.CWR6.img to recovery.img
SHANENATAS said:
did you put the recovery in the right folder? if the img you're going to use ins't named recovery.img you need to change the name or vise versa in cmd. Get what I'm saying?
Following the TUT is great, but sometimes when we download what we need it might be named different. Like mine is DNA.CWR6.img, so first I put that file in my adb folder, second in the cmd window I type "fastboot flash DNA.CWR6.img" OR do it how you are doing it but rename DNA.CWR6.img to recovery.img
Click to expand...
Click to collapse
Hi Guys,
Thanks so much for your help in getting me up and running esp you SHANENATAS. I love Sense 5, everything seems to work except MMS. I hope a port comes out for you guys soon!
I honestly think Sense 5 is by far the best rom I have used, it was actually the only one other than cyonogenmod 10 stock android that I considered going to.
The backgrounds are not included, but you can download those easily!
AWSOME upgrade! Funny thing is my windows 7 computer doesn't recognize the DNA now lol... oh well I already did what I had to so I dont need to use fastboot anymore. So in total it took about 30 hours to get this for a total non programmer! Tip to anyone attempting this is to do it on Windows 7, a lot less issues.
Lol havent eaten since 10am it is now 8pm because I have been working non stop on this; going to get dinner now. My girlfriend was wicked pissed off because I was supposed to buy ingredients to make chili with her but I never left the house.
Also guys please note if you are attempting this please install this version of Sense 5 http://forum.xda-developers.com/showthread.php?t=2184706
The previous versions would just crash when connected to wifi....
Thanks Everyone! Awsome walkthrough too, drumz0rz!!
Funny, my Windows 8 Sony Vaio has no problems in Fastboot, ADB etc. All the drivers loaded right up. Glad to hear you got everything going. Me, I'm waiting patiently for an unlock exploit for the OTA 2.04 fw. My replacement phone has the update.
Hi, I think I am in deep trouble now. My p780 8gb is completely dead after trying to flash a TWRP recovery in to it using a flash tool. Not sure what went wrong I fiddled with some settings in flash tool like 'firmware upgrade' and 'download' and at last saw a Dram failed message. I was using the latest s226 Kitkat ROW. Now all I can see is a red led charging light glowing while connecting it to a computer. The device is not getting recognized by VCOM drivers so no use with flash tool any more. Tried to reboot in to recovery and meta mode but the phone simply does not turn on. Anyone knows how to unbrick this, kindly help.
xperimen said:
Hi, I think I am in deep trouble now. My p780 8gb is completely dead after trying to flash a TWRP recovery in to it using a flash tool. Not sure what went wrong I fiddled with some settings in flash tool like 'firmware upgrade' and 'download' and at last saw a Dram failed message. I was using the latest s226 Kitkat ROW. Now all I can see is a red led charging light glowing while connecting it to a computer. The device is not getting recognized by VCOM drivers so no use with flash tool any more. Tried to reboot in to recovery and meta mode but the phone simply does not turn on. Anyone knows how to unbrick this, kindly help.
Click to expand...
Click to collapse
Hi. Please tell me if your phone is made in 2014. From what i see all phones made in 2014 must be flashed with another preloader. The simptoms you are described here seems that way. Waiting fro reply...
2014 vesrsion
stympy said:
Hi. Please tell me if your phone is made in 2014. From what i see all phones made in 2014 must be flashed with another preloader. The simptoms you are described here seems that way. Waiting fro reply...
Click to expand...
Click to collapse
Hi stympy,
Yes it is a 2014 January version. But to be honest I was using a ROM with 2013 version preloader but never faced any problem, Today purposefully changed it to the new 121kb 2014 preloader and everything was fine till I used the v5 flashtool to flash the twrp and I think I selected the upgrade option in it and flashed the twrp> found the ROM and preloaders from needrom.com from the uploader xxxsadistxxx .It worked flawlessly and then after first booting I configured the wi-fi settings again turned it off and tried to install the custom recovery. Now completely helpless because the phone is not getting detected by VCOM drivers.
xperimen said:
Hi stympy,
Yes it is a 2014 January version. But to be honest I was using a ROM with 2013 version preloader but never faced any problem, Today purposefully changed it to the new 121kb 2014 preloader and everything was fine till I used the v5 flashtool to flash the twrp and I think I selected the upgrade option in it and flashed the twrp> found the ROM and preloaders from needrom.com from the uploader xxxsadistxxx .It worked flawlessly and then after first booting I configured the wi-fi settings again turned it off and tried to install the custom recovery. Now completely helpless because the phone is not getting detected by VCOM drivers.
Click to expand...
Click to collapse
Look what you have to do!
Hi. The think was someting like this:
0. Unzip/Unrar those 2 archives.
1. First i install the .exe file from archive LenovoUsbDriver_autorun_1.0.10.zip. Reboot PC.
2. Plug the phone to your PC and new hardware wizard has appeared. Install the drivers by pressing automaticaly search the drivers.
3. Now power off the phone, and open the Device Manager, in Ports section.
4. With the Device Manager open, plug the phone this time powered off.
5. At this time in Device Manager/ Ports section, appeared for a second or two not in USB area something with.. MTK65...
6. Double Click fast on it because that will desapear very fast . If you missed the click for the first time unplug and replug the phone after about 5 seconds.
7. After you clicked on it all you have to do is update driver from MTK_USB__Driver_GOOOOODDD.rar archive, and voila you have drivers installed and now all you have to do is to flash you ROM.
Hope this will help you.
Tell me iff something goes wrong.
Good luck.
help
stympy said:
Look what you have to do!
Hi. The think was someting like this:
1. First i install the .exe file from archive LenovoUsbDriver_autorun_1.0.10.zip. Reboot PC.
2. Plug the phone to your PC and new hardware wizard has appeared. Install the drivers by pressing automaticaly search the drivers.
3. Now power off the phone.
4. Again plug the phone this time powered off.
5. At this time in Device Manager appeared for a second or two not in USB area something with.. MTK65...
6. Click very fast on it because that will desapear fast.
7. After you clicked on it all you have to do is update driver from MTK_USB__Driver_GOOOOODDD.rar archive, and voila you have drivers installed and now all you have to do is to flash you ROM.
Hope this will help you.
Tell me iff something goes wrong.
Good luck.
Click to expand...
Click to collapse
1) Hi, thanks for the troubleshooting steps but for the 3rd and 4th step, the phone is always in a switched off mode only. It simply doesn't get turn on in any mode.
2) I am using Windows 8.1 OS and Lenovo Usb Driver1.0.10 and VCOM drivers are already installed in it after turning off the digital signature check in win 8x OS and now nothing is happening after clicking on install option of LenovoUsbDriver_autorun_1.0.10.exe Is it a problem or in other OS also it wont prompt to click next or something like in a regular driver installation.
3) Phone is not getting detected in device manager after connecting it, so cant update drivers
Please suggest me what to do next.
xperimen said:
1) Hi, thanks for the troubleshooting steps but for the 3rd and 4th step, the phone is always in a switched off mode only. It simply doesn't get turn on in any mode.
2) I am using Windows 8.1 OS and Lenovo Usb Driver1.0.10 and VCOM drivers are already installed in it after turning off the digital signature check in win 8x OS and now nothing is happening after clicking on install option of LenovoUsbDriver_autorun_1.0.10.exe Is it a problem or in other OS also it wont prompt to click next or something like in a regular driver installation.
3) Phone is not getting detected in device manager after connecting it, so cant update drivers
Please suggest me what to do next.
Click to expand...
Click to collapse
Ok. Try this:
1. Open the back case of your phone.
1.1 Open the device manager on your PC.
2. You will find there an small red button.
3. Now plug your phone to your PC.
4. After you plugged the phone press the red button for 20 secconds.not optional
5. Release the button and see what is going on in your device manager.
6. Iff your preloader is messed up something should going on.
7. Should appear something like new hardware detected, that is the point when you update the drivers, and your phone will be detected by your PC
8. Try this and tell me if something goes wrong.
Good luck.
Sent from my Lenovo P780
TWRP magic
stympy said:
Ok. Try this:
1. Open the back case of your phone.
1.1 Open the device manager on your PC.
2. You will find there an small red button.
3. Now plug your phone to your PC.
4. After you plugged the phone press the red button for 20 secconds.not optional
5. Release the button and see what is going on in your device manager.
6. Iff your preloader is messed up something should going on.
7. Should appear something like new hardware detected, that is the point when you update the drivers, and your phone will be detected by your PC
8. Try this and tell me if something goes wrong.
Good luck.
Sent from my Lenovo P780
Click to expand...
Click to collapse
Hi thanks a lot stympy. I am glad that you were spending the time and effort to help me. I saw that red button trouble shooting post in your TWRP thread and luckily for me after clicking on different options in device manager while setting a complete format in sp flashtool the device suddenly got detected and format was done. After the format the device has lost its imei number, BT code and Wlan codes. That was going to be a hectic job to reinstall imei with imei repairing tools and usage of Hexa editor for BT and wi-fi codes just because some drivers were not getting installed properly.. But to my sheer luck I had a "Data' back up in TWRP with my previous version prerooted rom . I was not that confident to get a restore of imei , BT and wlan codes because it is just a 'data' back up not full ROM. I ticked the md5 checksum and voila after installing the back up 'Data' everything , absolutely every single code in my p780 got reinstalled automatically .LONG LIVE TWRP DEVELOPERS......... May be even after formatting the complete flash drive of the phone it still keeps the imei and other codes in factory mode. I am not sure. Now phone is in perfect condition and I am ready for another go. Stympy please create a 2.7.1 twrp for 2014 preloader p780 8gb. thanks again for all your help
xperimen said:
Hi thanks a lot stympy. I am glad that you were spending the time and effort to help me. I saw that red button trouble shooting post in your TWRP thread and luckily for me after clicking on different options in device manager while setting a complete format in sp flashtool the device suddenly got detected and format was done. After the format the device has lost its imei number, BT code and Wlan codes. That was going to be a hectic job to reinstall imei with imei repairing tools and usage of Hexa editor for BT and wi-fi codes just because some drivers were not getting installed properly.. But to my sheer luck I had a "Data' back up in TWRP with my previous version prerooted rom . I was not that confident to get a restore of imei , BT and wlan codes because it is just a 'data' back up not full ROM. I ticked the md5 checksum and voila after installing the back up 'Data' everything , absolutely every single code in my p780 got reinstalled automatically .LONG LIVE TWRP DEVELOPERS......... May be even after formatting the complete flash drive of the phone it still keeps the imei and other codes in factory mode. I am not sure. Now phone is in perfect condition and I am ready for another go. Stympy please create a 2.7.1 twrp for 2014 preloader p780 8gb. thanks again for all your help
Click to expand...
Click to collapse
WARRNING This are only for 8GB PHONES.
Here you are.
Try to flash with scatter files one by one till works.
Use only SP Flash Tool 5.
After flashing TWRP do not reboot the phone, start the phone with Power button Vol + and Vol - pressed. NOT OPTIONAL
Be carrefoul to select Download not Firmware Upgrade.
Good Luck.
Thank you stympy master
stympy said:
WARRNING This are only for 8GB PHONES.
Here you are.
Try to flash with scatter files one by one till works.
Use only SP Flash Tool 5.
After flashing TWRP do not reboot the phone, start the phone with Power button Vol + and Vol - pressed. NOT OPTIONAL
Be carrefoul to select Download not Firmware Upgrade.
Good Luck.
Click to expand...
Click to collapse
whoaa...that worked.. the 1st scatter file just worked..thanks a lot Sir stympy. Thank you very much
xperimen said:
whoaa...that worked.. the 1st scatter file just worked..thanks a lot Sir stympy. Thank you very much
Click to expand...
Click to collapse
You are wellcome. Glad to help
stympy said:
You are wellcome. Glad to help
Click to expand...
Click to collapse
Hey Stympy, you seem to know quite a lot about this! I have the same problem with my p780 4GB. After flashing everything seemed ok, as I got a green circle in SPFlash tools. However now I am not able to boot anymore. When connecting my phone to my computer the red light goes on and Device Manager shows a new MTK USB Port. When pushing the red button it immediately disappears. Does not matter if I push it for 20 seconds, as soon as I let go its bak in device manager.
When trying to reflash using SPFlash, it seems to recognize my phone, but when trying to format or Upgrade or Download, the red bar only loads up to 141776 Bytes and stops. Sometimes I have to push the red button for the phone to get recognized.
Any help would be greatly appreciated!
ps: CMIIT ID on the battery says 2013xxxxxxx so I guess its a 2013 model?
jeerome88 said:
Hey Stympy, you seem to know quite a lot about this! I have the same problem with my p780 4GB. After flashing everything seemed ok, as I got a green circle in SPFlash tools. However now I am not able to boot anymore. When connecting my phone to my computer the red light goes on and Device Manager shows a new MTK USB Port. When pushing the red button it immediately disappears. Does not matter if I push it for 20 seconds, as soon as I let go its bak in device manager.
When trying to reflash using SPFlash, it seems to recognize my phone, but when trying to format or Upgrade or Download, the red bar only loads up to 141776 Bytes and stops. Sometimes I have to push the red button for the phone to get recognized.
Any help would be greatly appreciated!
ps: CMIIT ID on the battery says 2013xxxxxxx so I guess its a 2013 model?
Click to expand...
Click to collapse
Hi. Can you tell me what firmware did you have ?
From what you described your phone seems to be from 2014. This are the simptoms when the preloader is messed up.
Look what you should try:
Download from here the preloader: http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161
Replace your Curent ROM preloader with the one you downloaded.
Drivers from here: http://forum.xda-developers.com/len...ial-kitkat-t2835605/post55587780#post55587780
Try this one and tell me if somethin goes wrong.
Waiting for Reply.
stympy said:
Hi. Can you tell me what firmware did you have ?
From what you described your phone seems to be from 2014. This are the simptoms when the preloader is messed up.
Look what you should try:
Download from here the preloader: http://forum.xda-developers.com/lenovo-p780/help/lenovo-p780-chineese-speed-version-t2874161
Replace your Curent ROM preloader with the one you downloaded.
Drivers from here: http://forum.xda-developers.com/len...ial-kitkat-t2835605/post55587780#post55587780
Try this one and tell me if somethin goes wrong.
Waiting for Reply.
Click to expand...
Click to collapse
Excellent! Did exactly what you said, works like a charm. You made my day Sir! Thank you very much!
jeerome88 said:
Excellent! Did exactly what you said, works like a charm. You made my day Sir! Thank you very much!
Click to expand...
Click to collapse
You are wellcome!
Friend HELP me also
xperimen said:
Hi, I think I am in deep trouble now. My p780 8gb is completely dead after trying to flash a TWRP recovery in to it using a flash tool. Not sure what went wrong I fiddled with some settings in flash tool like 'firmware upgrade' and 'download' and at last saw a Dram failed message. I was using the latest s226 Kitkat ROW. Now all I can see is a red led charging light glowing while connecting it to a computer. The device is not getting recognized by VCOM drivers so no use with flash tool any more. Tried to reboot in to recovery and meta mode but the phone simply does not turn on. Anyone knows how to unbrick this, kindly help.
Click to expand...
Click to collapse
I also want get rid of this bricked p780 8gb updated to kitkat 4.2.2 . Kindly, help me also with step by step procedure I'm totally new to this world. My phone is stuck at Lenovo logo... that it.... Please help me... ;(
apsaujla08 said:
I also want get rid of this bricked p780 8gb updated to kitkat 4.2.2 . Kindly, help me also with step by step procedure I'm totally new to this world. My phone is stuck at Lenovo logo... that it.... Please help me... ;(
Click to expand...
Click to collapse
Hi. Download the rom you need for your phone from here !
Download SP Flash Tool 5 from here!
Download drivers from here and here !
BE CAREFUL USE ONLY WINDOWS 7 ! THIS IS NOT OPTIONAL! IF YOU DONT HAVE WINDOWS 7 LOOK FOR VMWARE AND INSTAL THERE A VIRTUAL MACHINE !
Install first the drivers!
Open SP Flash Tool with admin rights!
Use this tutorial! If you dont manage PM me !
Good Luck!
help me too
jeerome88 said:
Excellent! Did exactly what you said, works like a charm. You made my day Sir! Thank you very much!
Click to expand...
Click to collapse
@stympy your statistics are impressive 1 greeting / 2 posts.
I've hope that I'll be more than just grateful. I've problem with modem in P780 "SIM ME locked, do you want to unlock" after unbricking.
It ask me about SIM pin and after no signal.
Regards
ungbar said:
@stympy your statistics are impressive 1 greeting / 2 posts.
I've hope that I'll be more than just grateful. I've problem with modem in P780 "SIM ME locked, do you want to unlock" after unbricking.
It ask me about SIM pin and after no signal.
Regards
Click to expand...
Click to collapse
Hi. Please tell me what rom do you have in this moment. How did you soft brick your phone?
Sent from my Lenovo P780
stympy said:
Hi. Please tell me what rom do you have in this moment. How did you soft brick your phone?
Sent from my Lenovo P780
Click to expand...
Click to collapse
Fool me. I've tried to run CN on russian LiFE ROW with TWRP. You can laugh very loud.
1. unbricked with P780_S136_140306_Lang
cleared IMEI
2. IMEI recovered with Droid Tools
after reboting no gsm signal
3. NVRAM recovered from backup
No success.
SIM cards works fine on other mobile, 911 cal also work on this phone
now running on:
ROM: P780_S226_Life_XVIBE_by_Xakep
Baseband: P780.V23
Last idea is clone p780 (colleague has one) with IMEI change, mac address and sn. Now with which tool it'll be easier?
success
ungbar said:
Fool me. I've tried to run CN on russian LiFE ROW with TWRP. You can laugh very loud.
...
Last idea is clone p780 (colleague has one) with IMEI change, mac address and sn. Now with which tool it'll be easier?
Click to expand...
Click to collapse
Last idea also faild.
And I have done it again.
1. Full format
2. Download Rom P780_S136_140306_Lang
3. Change IMEI
And it works.
Hello Awesome People!
I've read and I've tried a lot to unbrick my Xiaomi Redmi Note 4 on Snapdragon 625.
What happened?
After software actualization my phone stuck on Mi logo for 36+hours.
What has been tried?
I manually unblocked bootloader and I tried several ROMs. Every time I had this error in MiFlash critical partition flashing is not allowed or partition flashing is not allowed. I tried to edit in TextEditor some files but with no success after all.
1. One thing I didn't do was disabling driver signature enforcements in windows. What is this needed for?
2. Is this kind of malfunction can be reported during warranty period? Who is responsible for making my phone unusable?
3. Which ROM would you recommend to stick with during my following flashing tryouts?
4. I am going to check all the USB cables. Might it help when I've got the "critical partition flashing is not allowed" error?
5. What causes this "critical partition flashing is not allowed" error?
6. I've got no deep flash cable and I'm at the end of the world, so it's very difficult to get one of these here. Should I start trying to get one anyway? Someone had the same issue and could resolve it this way?
7. What to do now guys? Any ideas? -> For now I'll be checking all the usb cables I can get my hands on.
I know that some of the answers can overlap, but I chose the questions intentionally. I've been researching and checking solutions for over a week now. I would like to have deeper understanding of what the heck is going on with my phone and its software. There are no service centers here which can help me (their workers have less knowledge than I have, a sad lol), so I am dependent on your knowledge and your good will.
Best Regards
PatchMe said:
Hello Awesome People!
I've read and I've tried a lot to unbrick my Xiaomi Redmi Note 4 on Snapdragon 625.
What happened?
After software actualization my phone stuck on Mi logo for 36+hours.
What has been tried?
I manually unblocked bootloader and I tried several ROMs. Every time I had this error in MiFlash critical partition flashing is not allowed or partition flashing is not allowed. I tried to edit in TextEditor some files but with no success after all.
1. One thing I didn't do was disabling driver signature enforcements in windows. What is this needed for?
2. Is this kind of malfunction can be reported during warranty period? Who is responsible for making my phone unusable?
3. Which ROM would you recommend to stick with during my following flashing tryouts?
4. I am going to check all the USB cables. Might it help when I've got the "critical partition flashing is not allowed" error?
5. What causes this "critical partition flashing is not allowed" error?
6. I've got no deep flash cable and I'm at the end of the world, so it's very difficult to get one of these here. Should I start trying to get one anyway? Someone had the same issue and could resolve it this way?
7. What to do now guys? Any ideas? -> For now I'll be checking all the usb cables I can get my hands on.
I know that some of the answers can overlap, but I chose the questions intentionally. I've been researching and checking solutions for over a week now. I would like to have deeper understanding of what the heck is going on with my phone and its software. There are no service centers here which can help me (their workers have less knowledge than I have, a sad lol), so I am dependent on your knowledge and your good will.
Best Regards
Click to expand...
Click to collapse
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
1. Driver verification has to be disabled because mi flash has to install some drivers for mido.
2. Warranty isn't going to be valid here somehow.
3. Miui. Latest miui 9.5 fastboot rom.
4. Up and until your device is being recognised you don't need to change usb cable.
5. Probably driver verification?
6. No. It isn't required as of now.
7. For now perform disabling driver verification and try again.
MyNameIsRage said:
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
1. Driver verification has to be disabled because mi flash has to install some drivers for mido.
2. Warranty isn't going to be valid here somehow.
3. Miui. Latest miui 9.5 fastboot rom.
4. Up and until your device is being recognised you don't need to change usb cable.
5. Probably driver verification?
6. No. It isn't required as of now.
7. For now perform disabling driver verification and try again.
Click to expand...
Click to collapse
Thanks for advice!
Sorry for late reply. Lack of laptop, time and internet connection is a harsh hybrid
I've disabled driver verification and went on to minimal adb and fastboot. Command "adb devices" doesn't show any devices. And "adb reboot boatloader" gives error: no devices/emulaters found.
I've tried it on 3 different laptops including one with iOS. When I plug in my Redmi Note 4 SD every laptop beeps and only MiFlash detects a device. Tried out 4 different USB cables and 3 of 4 detected my Note 4.
Check the screenshots:
dropbox.com/s/u7xoewalgho9kh5/adb%20reboot%20boatloader.png?dl=0
dropbox.com/s/a782soi5aub2puf/ios%20device%20oem%20locked.png?dl=0
Sorry for cutting the link but couldn't post whole.
What do you mean my manually unlocked the bootloader? Did you perform steps other than those in official guide?
Click to expand...
Click to collapse
I tried the TEST POINT approach.
en.miui.com/thread-729246-1-1.html
What do you think MyNameIsRage?
Cheers
Hello all,
Anyone having the same problem was able to overcome it?
I'm still wishing to unblock my phone. Will the deep flash cable be of any help in this case?
Cheers!
PatchMe said:
Thanks for advice!
Sorry for late reply. Lack of laptop, time and internet connection is a harsh hybrid
I've disabled driver verification and went on to minimal adb and fastboot. Command "adb devices" doesn't show any devices. And "adb reboot boatloader" gives error: no devices/emulaters found.
I've tried it on 3 different laptops including one with iOS. When I plug in my Redmi Note 4 SD every laptop beeps and only MiFlash detects a device. Tried out 4 different USB cables and 3 of 4 detected my Note 4.
Check the screenshots:
dropbox.com/s/u7xoewalgho9kh5/adb%20reboot%20boatloader.png?dl=0
dropbox.com/s/a782soi5aub2puf/ios%20device%20oem%20locked.png?dl=0
Sorry for cutting the link but couldn't post whole.
I tried the TEST POINT approach.
en.miui.com/thread-729246-1-1.html
What do you think MyNameIsRage?
Cheers
Click to expand...
Click to collapse
Sorry for replying late. I see what you did there, and to be honest that wasn't really the correct steps.
First of all, in order to flash the rom, you should try to make sure that fastboot works. Boot into fastboot and check if device shows up. To do that execute
"fastboot devices" and if it returns some data then you are good to go for flashing fastboot rom. We'll go step wise. Try performing fastboot check and report if it works. Also if you have telegram you can contact me at @MyNameIsRage
MyNameIsRage said:
First of all, in order to flash the rom, you should try to make sure that fastboot works. Boot into fastboot and check if device shows up. To do that execute
"fastboot devices" and if it returns some data then you are good to go for flashing fastboot rom. We'll go step wise. Try performing fastboot check and report if it works. Also if you have telegram you can contact me at @MyNameIsRage
Click to expand...
Click to collapse
Ok, thanks!
I did "fast boot devices" and it shows the device.
dropbox.com/s/9qqpjdev31ssuw3/Zrzut%20ekranu%202018-09-29%20o%2014.40.00.png?dl=0
but still adb devices doesn't give any numbers back and flashing is impossible.
What now?
PatchMe said:
Ok, thanks!
I did "fast boot devices" and it shows the device.
dropbox.com/s/9qqpjdev31ssuw3/Zrzut%20ekranu%202018-09-29%20o%2014.40.00.png?dl=0
but still adb devices doesn't give any numbers back and flashing is impossible.
What now?
Click to expand...
Click to collapse
Now you should try mi flash. And possibly on a windows machine.
http://en.miui.com/thread-565784-1-1.html
MyNameIsRage said:
Now you should try mi flash. And possibly on a windows machine.
http://en.miui.com/thread-565784-1-1.html
Click to expand...
Click to collapse
My phone is in a bootloop. Can't do this.
2. Enable Developer options:- Go to About phone > tap MIUI version at least 7 times to activate the Developer options.
and neither installing VPN.
PatchMe said:
My phone is in a bootloop. Can't do this.
2. Enable Developer options:- Go to About phone > tap MIUI version at least 7 times to activate the Developer options.
and neither installing VPN.
Click to expand...
Click to collapse
Skip that part. Try as it is. Mi flash should detect your device. Jump straight to the part of flashing.
MyNameIsRage said:
Skip that part. Try as it is. Mi flash should detect your device. Jump straight to the part of flashing.
Click to expand...
Click to collapse
I did it on Mac (lack of windows laptop atm) and it said again "device oem locked". As in the screenshot I uploaded before.
PatchMe said:
I did it on Mac (lack of windows laptop atm) and it said again "device oem locked". As in the screenshot I uploaded before.
Click to expand...
Click to collapse
afaik mac won't work. You'll need a windows machine and mi flash tool.
MyNameIsRage said:
afaik mac won't work. You'll need a windows machine and mi flash tool.
Click to expand...
Click to collapse
Ok
Will do that in the next 24h and will report back.
Tried it all!
I tried to unlock boot loader via MiUnlock. Failed to "couldn't verify device" - unknown error (-1)
Same problem with trying to install ROM on windows as on MacBook.
I positively performed PIN TEST but couldn't install ROM. I am struggling with putting the device into fast boot mode after positively connecting it to windows pc with PIN TEST.
Any suggestions?
PS. I've sent info to xiaomi support as well.
Finally done it!
Hey guys!
I'm glad to tell you that after million tries with different ROMs and different approaches to PIN forcing i was able to reinstall my ROM. The working ROM for me was mido_global_images_V9.6.2.0.NCFMIFD_20180716.0000.00_7.0_global_228dc638d1
THANK YOU so much for help. You kept me going and finally i was able to overcome the obstacle
I hope I can be of help when you need it.
Take care,
Cheers
Edit: PS. I've done it on Mac
Hope someone can help me.
My Redmi Note 5 is stucked n Mi-Recovery 3.0 screen with 3 options: Reboot - Wipe data - Connect with MiAssistant. and continue to go in loop until the battery will be zero.
I was try everything to get connected, and flash again the firmware but no result, first and I think main problem is that my PC cannot see the phone, then with all SW I'm sure I can try to re-install everything and recover back my phone. Data is not a problem since I have all backup in MI account and Google account. I hope some one expert can help me to solve this unpleasant situation.
Is already out of warranty and send to MI service cost 36 EURO just for checking and then more than 90 EURO for repairing, is not worthing the cost.
P.S. I downloaded and try with ADB; Flash; MI Tool, USB debug etc..
I'm desperate mother of two kids and I need this phone, now I'm using a very old one.
Thank you
You try mi flash tool, but the phone can not recognized? Fastboot mode working? When yes, maybe Windows install the wrong driver. Look in the device manager and install it when it the wrong one manual
Hi Joke, thank you for your interest in my problem.
You can see the screenshot I just made it and I was trying to connect the phone, I installed any diver as possible but the PC is not recognize it.
joke19 said:
You try mi flash tool, but the phone can not recognized? Fastboot mode working? When yes, maybe Windows install the wrong driver. Look in the device manager and install it when it the wrong one manual
Click to expand...
Click to collapse
matsalleh said:
Hi Joke, thank you for your interest in my problem.
You can see the screenshot I just made it and I was trying to connect the phone, I installed any diver as possible but the PC is not recognize it.
Click to expand...
Click to collapse
And what's with the windows device manager? U look inside
I have an update, now I can flash the Rom using Xiaomi MI tool V2. Then after finish message say that installation was successfully, but when I restart the phone is going back again on same position with Mi-Recovery 3.0. I noted that if I use MI Phone Assistant in certain conditions I can see the phone as "HD" in my PC. There is anything I can do to revive my phone?
I hope someone can help me. Thanks