Related
I am running Windows 7 x64 I have no idea if following this guide on another operating system will work, this is just a step by step of EXACTLY how I did this, Not to say this is the only way. I have tested other methods and I have put in different variables and I have successfully gotten it to work several times in a row doing it this way while following jp4756's guide. I am sure this is not the only way to accomplish root, however this worked for me perfectly. PLEASE don't skimp out on any step. There is no shortcut here just follow the steps and jp4756's guide to the TEE!!!
Step 1.
Uninstall pdanet/htc sync/ any other thing you installed to get all this to work before
Unplug phone from computer usb cables and have phone powered on and in settings menu
Step 2.
download USBDeview(install it) easy to google it
download HTC SYNC(do NOT install it yet) for mytouch slide easy to google it
Step 3.
While in settings menu go to Application
go to Development
and check the box USB debugging
Step 4.
In settings go to Connect to PC
touch Default connection type and choose Sync
At this point you have the phone not plugged in, you have the setting on the phone changed, you have dowloaded usbdeview and installed it, and have htc sync dowloaded
Step 5.
Start USBDeview(some may have to right click the exe and run as administrator) and delete all android drivers and mytouch drivers, anything relating to android
Install HTC SYNC and let it completely install
Step 6.
Plug phone into computer and let the computer auto install drivers etc...
Step 7.
turn the phone off. Power on the Slide into the bootloader by Holding Down ( Volume Down + Power Button ) After it does its little thing your computer will beep and start auto installing drivers and stuff
Step 8.
If everything has gone according to plan in Device Manager it will show Android 1.0 or w/e with a exclamation point. Right click on that and choose Update Driver Software
2 options pop up choose Browse my Computer
then choose Let me Pick from list...
a list will appear giving lots of choices
choose Android Phone should be the first choice that says android....
then 3 options will appear, choose the 3rd one that has Composite in it and choose okay.
Step 9.
Now select Recovery from the bootloader menu
after it is done doing its thing completely 2 things will happen
1) In device manager you will now have something under disk drives
2) USBDeview a new driver will pop up at the end of the list, something like this:
Port_#0004.Hub_#0004 T-Mobile myTouch 3G Slide USB Device Mass Storage Yes No No No E: HT05RPS05696 6/16/2010 4:00:58 PM 6/16/2010 4:07:35 PM 0bb4 0ff9 08 06 50 USBSTOR USB Mass Storage Driver USBSTOR.SYS USB @usbstor.inf,%generic.mfg%;Compatible USB storage device
Step 10.
This new driver to appear shows Yes under the Connection column. This needs to be disabled. Right click on it and choose Disable Selected Device
after about 10 seconds it should no longer say Yes under connection column, if this does not happen then you are not running it under Admin.
Okay so now you are literally almost freaking there.
Step 11.
Now basically all you have to do is follow jp4756's guide starting with step 5. Im going to assume you already understand steps 1-4 in his guide. And you already have the package listed in his guide as well. You have already put those files where they belong
Step 12.
Okay so we are basically following his guide now. first things first
5. run the update.zip it will fail(MUST DO)
6. now in cmd type adb reboot recovery (don’t press enter)
7. in the recovery hit reboot system now( once it starts rebooting run that command rapidly untill back into recovery) <--- Basically while the phone is rebooting you are just hitting up arrow enter up arrow enter up arrow enter up arrow enter in CMD. You will know when you can stop when the CMD freezes for a sex, computer makes beeping noises and the phone reboots basically. It is headed for recovery and we must switch our command now
8.type adb devices(if it says nothing repeat the steps, if it says offline unplug it and then plug it back in, if it says recovery your fine) <---- Basically after you know its headed for recovery you change command to adb devices and you repeat previous procedure, up arrow enter up arrow enter up arrow enter etc.... I did not use loop, i did this all manually.
This may take a few tries, if it does not show offline then go back to step 6 rinse and repeat. You go back and forth just a few times and you will have it. Literally within about 3 tries you should accomplish the annoying goal of having offline stay there.
My job is done, follow guide and continue on your quest for root
There is no guarantee this will work for everyone. I am not claiming that this is 100% Im just giving an explanation as to how i got it and what might have been causing everyones trouble. Results may vary
Thank you to all the devs who made this possible and jp4756 for his wonderful guide
Wow that is just way to much stuff there...
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
Also It just might be your computer so I would try and use a different one if you can.
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
Sorry that we all can't be as cool as you jnight666, but some of us are having real problems with no apparent explanation. I am an IT professional with access to every kind of computer used in the modern world, and trust me, I've tried all the ones that apply. Rubbing it in our faces that it was just so easy for you is just rude.
THE DRIVER MAKES NO DIFFERENCE FOLKS. IF YOU CHANGES DRIVERS AND THEN IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON MANY DIFFERENT DRIVERS.
THE CONNECT TO PC SETTING ON THE PHONE DOES NOT MAKE A DIFFERENCE IN FASTBOOT/RECOVRY FOLKS. IF YOU CHANGED THIS SETTING AND IT WORKED, IT'S PURELY A COINCIDENCE. PEOPLE HAVE GOTTEN THIS TO WORK ON VARIOUS DIFFERENT SETTINGS.
That being said, this didn't solve mine. I still cannot root.
And Yes, my cap locks was on purpose.
Okay, please dont come in here and start telling me how my method is wrong. I already stated there are other ways to accomplish it. I had already stated that this isnt 100%. I am merely offering an exact procedure that i duplicated SEVERAL times, with it working for me every time. If this isnt how you accomplished it then pls, theres no reason for you to be in this thread posting negative comments.
With that said fermunky, did you follow the procedure to the tee? - btw im not assuming anything so please dont take it personal. Im just trying to help ppl : )
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Completely understandable, and definitely no disrespect to you or anyone here
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
jnight666 said:
Wow that is just way to much stuff there... I don't see how anyone has a problem with loop.
I've ran loop on 2 totally different Computers running 2 totally different OS's and running 2 totally different Drivers, I have no problems with either one..
1st: XP sp3 32bit w/ PDANet Drivers <--- Only ones that I could get to load, Forcing drivers wouldn't work in XP... also like I said before, make sure to close the PDANet Program in the Toolbar.. Also make sure to read the directions when installing PDANet...
2nd: Windows 7 64bit w/ Htc Drivers <---PDANet Drivers also work... You have to force the HTC Drivers in Devices Manager..
I think most people are having this problem because they aren't doing the USB Debug thing. But could be Wrong.
Also a side note my phone is running the USB Drive and not SYNC works just fine...
And if anyone want to say anything about this I'll go load up my Pentium III machine and see if it works on that...
Also It just might be your computer so I would try and use a different one if you can.
Click to expand...
Click to collapse
3 different computers 3 different op systems installed uninstalled drivers different programs etc...some phones are hard to root its a ambiguous situation
Yeah sorry I wasn't trying to be rude.
I was just trying to be helpful, sorry if it came out that way...
I also have the loop not working issue but i usually only happens once or twice..
I feel your pain I had trouble with the push Update.zip part of this thing and I was trying it for hours...
I was just trying to tell you what worked for me...
If you tried different computer and still no luck then im guessing its the Phone that is the issue or the USB Cable...
gofizzle said:
When I disable the Mass Storage I see other items in USBDeview that reference the Slide. I end up in a loop after rebooting and rapidly entering adb reboot recovery. I was seeing everything as your instructions explained.
Do you think it is worth a shot to disable all but one item for the Slide? Any suggestions would be greatly appreciated. I work in an IT Escalation Group and this has to be one of the toughest nuts I have tried to crack! LOL
Thanks,
Click to expand...
Click to collapse
You definitely don't want to do that, as one of them is one that you need to be connected once you finally get to see offline stay. Are you rebooting using the method described in jp4756's guide? meaning your rebooting using the recovery option reboot, then in command doing the adb reboot recovery, then once you no the phone is gonna boot into recovery you switch to spamming adb devices? When you say your in a loop it sounds to me maybe your not doing the adb devices after the phone listened to your adb reboot recovery command
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
before plugging your phone into your computer a single time, can you confirm that you started up USBDeview and uninstalled every single driver related to android, or mytouch or htc etc... Also before ever plugging your phone in a single time did you install htc completely?
Code3VW said:
Followed your instructions...
No ! next to anything in device manager. Right clicked on Android Phone > Android ADB Device and went to properties to update the driver. Nothing in the HTC folder would work, they both said that they weren't applicable for the device...(this was in C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64)
Click to expand...
Click to collapse
Right Click Android Phone - Properties - Driver - Update Driver - Browse My Computer - Let me pick from a list of device drivers (click this, don't give it the path in the upper box) - Have Disk - Browse to yours C:\Program Files (x86)\HTC\HTC Driver\Driver Files\Win7_x64 - click androidusb.inf and select Open - OK - Unclick Show compatible hardware - Select "T-Mobile myTouch 3G Slide" - Next - All Done.
after getting some sleep and starting fresh, i tried this method again this morning. on the fourth or fifth try i got my slide to stick in offline mode. so then i unplugged it and plugged it back in to get into recovery. lost it, and now im on my 50th or so try to get it back to offline mode.
i need a stiff drink lol
it seems partially a driver issue and also an adb issue i thinks. it connects 'when it feels like it'
i'll report back if i make any progress.
btw im doing this on XP Pro SP3 fully updated
edit: I also noticed when adb does catch the slide, 2 instances of adb are running, then one closes and loses the phone. maybe this will help solve some of the problems
You've misunderstood that post. Only one instance of ADB will show when the loop is not running. Once you start the loop, another instance of ADB will show up and disappear many times. This is normal. As long as only one instance is showing before loop, you are fine.
fermunky said:
My caps wasn't to be negative. There are too many people claiming the drivers were a key. And I am not saying yours said this, but it also doesn't clearly say it doesn't. That is all.
Click to expand...
Click to collapse
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
mtjnkee said:
I would just like to say that I have followed every method listed in these forums, achieved root the first try (using the updated update.zip). My problem occured when flashing the eng rom, I lost clockwork,root and now the phone runs like sh!t. Yes, superuser was installed and yes my pc no longer recognizes the phone when searching for adb devices after pushing the first 2 files from the eng flash walkthrough.
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
Click to expand...
Click to collapse
maybe your downloads were corrupted. that's really strange...
man, that really sucks! I am truely sorry...
after spending 20 hours or so on rooting, I really feel your pain.
After I reboot into recovery mode and then use adb to check for my device I never get it to show up. Just so I am clear when you say 'spamming your device' you mean after reboot and rapidly entering the reboot recovery command, then looking for device with adb devices command. I never get it to show.
Thanks for the reply!
No devices in adb?
So I had this same problem with my MT3G. Type in "adb devices" kills the last device and it lists connected devices and NONE were listed. Not sure exactly what I did, but did eventually get it working. (I was trying to use the emulator)
Now though I'm having the same problem with my wife's MTS. Any ideas?
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
jfvidalc said:
I was running streakdroid 1.8.1, and was having the wifi/3g problem, and after trying the below suggestion (which was posted in the dev section of the 1.8.1 thread post#367 link=http://forum.xda-developers.com/showpost.php?p=11869560&postcount=367):
--------------------------------------------------------------------------
Originally Posted by strvmarv
This put me on baseband GAUSB1A134031-US and appears to have cleared up the Data that wouldn't enable without a reboot, so far:
1. extracted the decoded ATT 2.2 340 pkg from here...it's the dropbox link BTW! (dropbox link)
2. grabbed the amss.mbn and dsp1.mbn (if you don't want to do step 1 then get the already extracted files here)
3. went into fastboot and flashed both of them
Dumb question, anyone know if it's possible to lose your carrier unlock when doing such things?
--------------------------------------------------------------------------
Now my streak doesn't boot, can't get to fastboot (pwr+camera), or recovery (vol+,vol-, pwr). Sometimes all three led's light up, and stay on and nothing happens, and sometimes the LED's stay off and nothing happens.
I tried using qdltool (vol+, usb connection to PC) , and it timesout after reboot ok message after I click RUN in qdltool. I installed both the qualcomm and dell fastboot drivers as per instructions, and I don't have a yellow ! in device manager.
Would appreciate any suggestions on what I should try next.
Click to expand...
Click to collapse
search for the QDL tool, follow instructions and you will be in business again.
I tried QDL tool, and it fails with a fastboot timeout error:
"wait ADB fastboot mode timeout!"
That means you dont have the fastboot driver loaded right.
First is the qualcom driver which you made through... after the small stuff loads. It then pops over to fastboot driver.
Try another driver or pc
Sent from my Dell Streak using Tapatalk
I download and successfully installed the Dell R288920 drivers.
Is there some other driver that works better?
i would remove fastboot drivers... reboot, use reinstall drivers and use a different usb...
are you running x64 windows by chance?
I have both a 64bit Win7 and a 32bit WinVista. I followed instructions on streakdroid.com to install qdl tool on 64bit, as well as trying it on 32bit, and they both fail in the same place.
Here's the tail end of the qdl tool log file:
Check Secure Boot is enabled
Streaming hello success
Send Security mode success
Download partition table success
#Download DBL success
#Download FSBL success
#Download OSBL success
#Download DT success
#Download backup FSBL success
Erase EFS2 success
Wait for rebooting ....... ok
Wait for modem set up ......
Wait for ADB device .........
ERROR[D2]: wait ADB fastboot mode timeout!
Please check that device is exist and driver is properly installed.
Download Fail! - 2011/03/06 23:34:45
Elapsed Time: 30.55 sec
It may be the drivers or it may be the Streak. I have a Streak that isnt recognized as a USB device when plugged in and will not boot into fastboot mode (black screen) with the camera+power buttons. I have tried on 3 PC's(2 windows 7, 1 linux) and none will talk to it via ADB. However they will talk to my other working Streak so I know it isnt the driver.
I suspect it is corrupt NAND memory and have come to the conclusion that the only way to fix it is to get someone to JTAG reprogram it or swap out the mainboard. I would love it if someone can prove me wrong though...
BTW i bought this Streak in this condition so I dont know for sure how it got in this state.
your missing something.. def a driver issue says so itself.
do you get fastboot to work at all outside the qdl tool? if so can you follow the following guide?
http://forum.pocketables.net/showthread.php?t=8285
That's just it, the streak won't power up (pwr+camera), which would allow me to do fastboot outside of qdl tool.
Before I bricked it, I was able to run fastboot outside of qdltool all the time without any problems.
its not bricked... there is an issue with the timing of the driver kicking in or something driver related.. try another pc.
this is a pc issue.. not a streak issue. This part was always the biggest pain in my ass.. took me hours to get my system working right for this stuff.. the streak.. no issues....
i think the streak is unbrickable like the galaxy s phones.
I've tried both my PC's (desktop Win7 64, laptop WinVista 32), and both get the same error.
I've also tried different usb ports. When I first tried fastboot a couple of months ago, I was able to install the correct driver because I was able to start the streak in fastboot mode which then allowed me to install the driver on the desktop ( called android something if I recall correctly).
The problem I had with the QDL tool was the ADB driver also. The instructions I watched didn't include installing it, but did include downloading the folder that had it. If you are following the visual tutorial from the streakdroid website, go into all the folders you downloaded in the process. Somewhere in there is your specifc ADB driver. I was getting the ADB fail also until I found my driver and it installed. Good luck.
Sent from my Dell Streak using XDA App
I agree with the above post. You havent updated the correct driver. I noticed that when i searched through the recovery folders i notoced that the qcuser driver or whatever it was called, was in multiple folders....i experienced the same ADB error you did but i just kept switching with qcuser driver until i found the correct one. Go have a second look or third look....im sure ull find the right one.
Sent from my Dell Streak using XDA App
I've tried all three qcser,qcusb and qcmdm in the repairtool (qdltool) driver subdirectory for 32bit windows in winvista and wnet, with no luck.
Did any of you have problems putting the streak in fastboot mode independent of the PC, because that's not working for me. It used to work for me by pressing pwr + camera buttons.
I believe the ADB drivers were in the other folder you downloaded per the directions.
Also, I was able to get into fastboot prior to the QDL tool, but I don't believe that matters at all. The QDL tool is halfway there at the point it errors on you. You just need that correct ADB driver. You are so close, don't give up. Try the faq section of streakdroid.com
Furthermore, if you have access to an XP machine use it. You are almost back to Streakville.
Sent from my Dell Streak using XDA App
see if this helps:
http://forum.pocketables.net/showthread.php?t=8214
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
jfvidalc said:
EUREKA!!!!.
Looks like the flashboot image on the streak was corrupt, so I was able to use streakflash to recover it.
Running nandroid restore as I type this. so hopefully I can get back in business.
Thanks to all of you guys for your suggestions.
I'll let you know if the nandroid restore is successful.
Click to expand...
Click to collapse
What is streakflash? a new tool? like QDL?
Krad said:
What is streakflash? a new tool? like QDL?
Click to expand...
Click to collapse
See this page - it is a version of QDLTool that only flashes some files. I believe that it is used to repair the boot.img.
From this page:
Q: I’m trying to flash my Streak with the QDLTool but it keeps coming up with Error D2 ADB Timeout
A: This can be for a number of reasons. Firstly, look at what is displayed on the screen of the Streak:
Nothing / Screen is blank: This could be a sign of a corrupted fastboot image. Download streakflash.zip from the Downloads section and use the version of QDLTool it contains to reinstall the base images. You can then retry using QDLTool from repairtool.zip
Black screen, says “DT is in FASTBOOT_MODE”: This can be the sign of a driver issue – Try reloading the Fastboot/ADB drivers
White screen, says “FASTBOOT_MODE”: Go through the process again, this time using a different USB port.
Click to expand...
Click to collapse
Nandroid restore of streakdroid 1.6.0 successful.
I've been trying to upgrade to the more recent versions, but none of them (at least in my case) are as stable as 1.6.0.
1.6.1 with it's builtin perfmod is unstable.
Both 1.7.x and 1.8.1 are stable, but they suffer from the wifi/3g problem. Both wifi and 3g work, but I usually have to reboot to switch from one to the other, which is a hassle.
Yes, I've tried factory resets on all of them, but eventually, I either have random reboots, or FC's galore.
I know other people have gotten 1.6.1, 1.7.x, and 1.8.x to run stable, but I've had no such luck.
So for now, I'm sticking with 1.6.0 ( I get quadrant scores in the 1600-1700 range, which is pretty good).
Anyway, thanks again for all your help.
I tried the instructions in this video (https://www.youtube.com/watch?v=NGy85rFFhLM) to try and help me install drivers because my bootloader wasnt being detected by fastboot, but at the part where he connects the phone and opens command prompt to type adb devices all i get back is this : http://imgur.com/3Y1N2gr I've been stuck at this step for over a day now, I've tried 4 different places for help not much luck anywhere :/
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Read the whole thing 2-3 times. Understand it. Then do it.
You'll have it working
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link https://www.youtube.com/watch?v=BJPEc1NG_k8&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Linx91 said:
Hello everyone,
I'm writing here, because accidentally i turned my zenfone 2 into a brick, following an indian youtuber on this link
&t=185s&list=FLJXXdfRBIfVwi7iWKHUJJrw&index=1 while trying to update to Nougat 7.1.
The guide is very well done and precise, in fact the fault is totally mine because i accidentally launched by using ADB, the bootloader of the Zenfone 2 ZE550ML then the screen became blank on power up...
So i followed this guide https://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256 stopping before point 2) and at least i reached to get out from the permanent blank screen.
Now i'm in trouble because if i use ASUS flash tools (after installing Intel Driver), i am able to see the phone and trying to install on it the .raw file, but at the end of a while, it says "Flash image Failure (Wrong image format).
Then i tried the way "2", installing it by using fastboot, i unzipped the official ROM for ZE551ML and tried to install one per one as the described in the guide, the various parts of the SO, but each time i send a command (checked many times the sintax), the software starts downloading it on the phone and then stops, saying everytime with every file "Failed".
Thinked also to ADB, but by using "adb devices" it doesn't recognize any device...
So... may the bootloader given by the guide be wrong? or an old one version? What can i do?
If i try to get into recovery mode, it just shows an USB cable forever... i'm costricted to repeat the first part of the operation with xFsTK Downloader.
I thank you for any help or suggestion.
Click to expand...
Click to collapse
same here brother...i am stucked from last night..getting no help nowhere..really upset..plz let me know if you figure out something.
Which raw file version are u using
Hello this is my first post. I have searched the threads and internet for answers but I have not been able to find a solution.
I have been customizing my phones since the days of baked black bean on my galaxy S1, but I am no expert at this stuff. Until about a week ago, I was happily running RR on the OPO (great ROM) but it has gotten a bit slow so I figured it was time to get a OP5.
When I boot into fastboot, my device is recognized with the command fastboot devices. My phone showed the following:
fastboot mode
product_name - QC_Refernce_Phone
VARIANT - MSM UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - c7ccda2
SECURE BOOT - yes
DEVICE STATE - locked
When I ran fastboot oem unlock, CMD prompt shows FAILED, however, the option to unlock the bootloader shows up on the OP5. I go through the process and wipe data. My phone now shows that it is unlocked, and I go into developer options to get advanced reboot/USB debugging/verify OEM unlock is still enabled. When I go back to fastboot, I am unable to flash TWRP. I have now seen a number of errors, usually:
FAILED (remote: Requested download size is more than max allowed) or target did not report max download size, or command write failed (no error). I have tried installing 4 different versions of ADB/fastboot from different sources, and I have tried TWRP cheeseburger 46, 58, and 62. I have also tried two different USB ports and 4 different USB drivers.
Does anyone know what could cause these issues or how to get TWRP installed? Any help would be much appreciated. I really want to get rooted and get substratum running.
hmm
did you type fastboot devices to check that u got connection ? do you have another pc to try ? another usb port
edit: also try disable developer option and aplly it again with oem unlock tapp
EDIT2: if you cant still get it work you can try
Advanced settings -> Backup & reset -> Reset all settings and after that unlock bootloader
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
bro do u find solutions for this
I found an actual fix for this problem. Basically I had to download Large Address Allocation Tool (LAA) which you can find online. I would link to it but I do not have the website handy.
I found this solution after soft bricking my phone by installing Oreo (I don't suggest using VPN to pretend you are in Canada. Just run the beta or wait for the US release).
Essentially, you just need to run this tool on your adb.exe. From what I understand, the issue is just that adb is not using enough RAM. I think you'll need to be running Windows 7 64bit with at least 4GB RAM. I hope this info can help someone else!
jsnell said:
I was able to solve this by using a friend's laptop and installing the drivers and abd. Worked like a charm and I was able to flash magisk for root.
For anyone else having this issue, try another pc if you can. I'm guessing this was either an issue with adb on my machine or a problem with the device drivers.
Click to expand...
Click to collapse
Ever since i ditched windows and went with ubuntu i have not had one single driver issue, not one single hiccup on anything. It's been two months.. I'm never going back. lol. Every time I use adb and or fastboot it always works.