Related
[Q] i747 (AT&T) Galaxy S3. No Rom, No recovery. Odin not recognized by Win7. Screwed?
THREAD CLOSED:Final update made
Solution: JTAG. I have updated the main page for anyone who comes across this in their troubles. Try the advice in this thread. It's good advice. I just couldn't be helped. These guys are smart as ****. Take their advice. Good luck, and good night.
Original post
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
Recap
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
What I tried
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 2 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Info
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Conclusion:
Windows GS3Toolkit fails to see it
Windows Kies fails to see it
Windows 7 OS fails to recognize it
Windows adb fails to see it
Linux adb fails to see it
Mac OS X heimdall fails to see it
Mac OS X adb fails to see it
My conclusion: For some reason, my phone is reporting itself incorrectly, with a potentially damaged usb port on the phone.
Solution A: Try to JTAG myself. (NOT RECOMMENDED) Pros: Learning. Cons: Too much to buy and ugh. F that noise.
Solution B: (Chosen path) Send to someone to JTAG it for me. Pros: Fast, easy (for me) Cons: $60
Solution C: Sell the phone. Pros: Potentially less cost (through loss) Cons: Time to sell and buy, jockey for prices, potentially lose my ass.
Solution D: Do nothing. Pros: No more loss, no more work, maybe something will come through. Cons: bricked phone
Kilo__ said:
Alright, I'll give as much info as possible. If anyone can save me from having a $250 paperweight, I would... Well, probably whatever they asked me to. Here it is in a nutshell. I was on AOKP with TWRP recovery. I jump ROMS everyday it seems, so why would today be any different? I boot into TWRP, make a backup, wipe cache, factory reset (data and cache), delvik cache, and then system (here was my mistake). Then I was going to install another ROM when I was suddenly needed by family. In my infinite genius I decided "Oh I'll just shut down without a ROM installed, that'll go well!" and shut the phone down through TWRP options (/facepalm).
Finally, I come back to it and decide "Ok, I'd like to install a ROM now". I boot it up (holding up, home, power), but accidentally let go of home and power instead of just power so it tries to boot. No prob, I just do it again. Now I hold it this time and the trusty "teamwin" splash comes up. But something isn't right. It restarts instead of giving me options. "ok...." I think, and I try it again. Same thing. F**k, I have no recovery... So I go to my last resort. Odin mode. I get into Odin Mode, grab my USB cable and plug in (to my computer with drivers already on it from the toolkit) and! TADA! USB not recognized. That's right. USB. NOT. RECOGNIZED.
So lets recap:
No ROM
No recovery
Drivers from Toolkit installed
Odin Mode = USB not Recognized in Windows
Here is what I have tried (in no particular order)
New USB cable. 3 to be exact.
Different ports. All of them on all of the computers.
Different computers. 2 laptops, 1 desktop. All Win 7 64-bit.
Going into recovery (it bootloops)
Letting it boot. (Does nothing)
Uninstalling and reinstalling drivers
Installing Kies
Installing nothing
"adb devices" (doesn't show up)
Using toolkit (no devices seen)
Manually chosing every driver from "Samsung electronics LTD" that my computer has installed.
Plugging in before starting Odin
Plugging in after starting Odin.
Every combination of "Power cycle, Odin Mode, connect to computer" I can think of
Actually praying to Odin
Crying
Giving up
Gaining Second Wind
Searching Google, XDA and numerous forums extensively.
Making a new thread myself
I would really, REALLY appreciate it if someone, somewhere has ANY idea on how I can flash something ANYTHING to my phone again. Thank you SO much for your time. Honestly. I mean it, thank you. Let me buy you a beer. I'm serious.
Extra Information: The pop up is always the "USB not Recognized" balloon. Device manager comes up with an "Unknown Device" and yellow [!] triangle. Sometimes, under details, I'll see "Code 10: Device could not start". To reiterate, the phone WILL go into Odin Mode. Thanks again.
Click to expand...
Click to collapse
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Kilo__ said:
Followed this to the letter. Didn't work. Thanks though! Can I send you money for a beer?
Click to expand...
Click to collapse
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
I'll talk with you no doubt.
Kilo__ said:
I'm not sure how this applies. I think this is a good solution except that I can't get it to connect to my computer at all. ADB, ODIN, nor Windows 7 will recognize the device in Odin Mode and I have no ROM or recovery installed, and I can't install anything without getting it to connect. I'll keep this in case I can get something to connect and Odin doesn't work, so thank you!
I'll talk with you no doubt.
Click to expand...
Click to collapse
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
Well that's the thing. It does not show up in devices. ADB will not recognize the device. I'm fairly knowledgeable with using adb and I have 3 versions on my computer. None of the three (adb.exe adb-toolkit.exe or SOCadb.exe) will view it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
Kilo__ said:
No I haven't. I can try to do that too. And I have the cable that came with the phone (but I bought it used). I'll try it tomorrow at work
Click to expand...
Click to collapse
Tried it. Unrecognized still. I think I may just be f***ed
Kilo__ said:
Tried it. Unrecognized still. I think I may just be f***ed
Click to expand...
Click to collapse
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
No, I don't get any options. "Teamwin" for about 30 seconds. Then black... 5 seconds. Then vibrate twice and then reboot. I think I wiped system, and then TWRP borked as you say. I have used many cords for this.
And yes, the phone goes into Odin mode, but the Odin program doesn't pick it up, neither will ADB and windows says "USB not recognized"
DirtyOldMan said:
Uninstall Kies
Uninstall the Samsung USB Drivers
Run CCleaner
Reboot
Install The Samsung USB Drivers
Go into Download Mode
Open ODIN
Hook up, and see if drivers install and ODIN sees the phone
Click to expand...
Click to collapse
Gage_Hero said:
You could do some research into putting twrp on via adb.....or cwm depending on your preference..... if I remeber correctly you need to download the android sdk... I am sure it tells you on the trwp page though....... I know I have adb'd myself out of some tight spots with my transformer and also my old htc hero... haven't commited to changing the s3 yet though... concept is the same....
http://www.teamw.in/project/twrp2/104
Download - Recovery Image Method (using dd):
--------------------------------------------------------------------------------
Select the latest .img file from here
Download the above file. Using adb shell or terminal emulator:
su
dd if=/sdcard/recoveryfilename.img of=/dev/block/mmcblk0p18
Make certain that you get this command right. Typing the wrong number could result in a brick!
After the SU on the PC i copy paste the command.....
Click to expand...
Click to collapse
DirtyOldMan said:
It's cool man... If you want me to look at it, PM me, I can probably fix it...
Click to expand...
Click to collapse
Gage_Hero said:
to you start a command prompt, open the directory where adb.exe is. Press and hold shift while right clicking in the window, select open command prompt here...... manytimes if you don't do this ... adb isn't going to work for you.....
Once you do this then type devices if you get your device showing up then you can install twrp or cwm.....
When the instructions say to enter a command, highlight it on the webpage and copy then in your command window right click and paste (control V does not work here)
If you use adb to install anything, that file MUST be in the same directory as the adb.exe
Click to expand...
Click to collapse
aybarrap1 said:
Have you tried using another computer that has no trace of android drivers or anything else and installed ODIN and drivers from scratch? Also make sure you are using the stock usb cable. Just wondering if you might potentially have conflicting drivers you are not aware of.
Click to expand...
Click to collapse
hednik said:
So when you get into recovery mode (or attempt to) it just reboots after a few seconds ?
You have the teamwin spleash screen and then it doesn't give you time to select any options ? There's really no harm in formating system because it will just boot into twrp without a recovery. You might have a borked recovery but it seems like more. Samsung cords are crap and like to die randomly so another cord is really worth a shot of course make sure it has data.
When you say odin mode I assume you mean download mode and odin just doesn't light up with a com port showing a device ?
Click to expand...
Click to collapse
I just wanted to say thank you all for the help on this situation. Nothing has turned up with the phone but I'm 99% sure this isn't a driver thing now. I'm gonna face the music and try to find either a Jtag kit somewhere or possibly someone to buy it from me. If anyone has any ideas on this and wants to weigh in, I'll of course attempt their solution, but I am going to try other solutions now. Once the device has been either sold or fixed, I will close this thread and edit my first thread with the solution for others to see. Again, each and every one of you, thank you. Hopefully, I can return the favor some day
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
mrhaley30705 said:
Jtag is a little harsh at this point. That's typically reserved for devices that show absolutely zero signs of life.
Click to expand...
Click to collapse
Yea, yea it is but I don't know what else to try. I've browsed forum after forum after forum. Of all the people that have received help this problem (Odin is the only choice and isn't recognized), a total of 0 have had something work for them and most threads die unsuccessful. I partially blame the OPs for their lack of through information and replies, but also to the fact that I believe this is just a case of Bad Luck Brian. To have me mess up with the ROM, TWRP take a nose dive, and ODIN play enigma all at the same time seems like a very unlucky scenario.
It has been 8 days now that I've had no phone. Now, I'm not an important person, but I'd at least like to have the phone number I'm paying for, be usable to me. I am really grateful for all of the help and I don't feel slighted or let down in any way, it's just plain and simple that I want a working phone back. If something comes up here before I remedy the situation myself, I'll be sure to let y'all know how it goes, but I'm at the point where I want a usable phone. Again, thank you all for help you have provided and the time you've put into my issue.
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
mrhaley30705 said:
Do you have a friend/colleague that also had an s3? Try their computer if you do. They should have the proper drivers installed, so Odin should work. This is the last idea I have. Also, check your pm.
Click to expand...
Click to collapse
Ah, yes. Actually, one of my posts (probably the main one) I bring up 2 laptops and 1 desktop being used, one of the laptops was his. He has an S3 (he's actually the one that pushed me towards getting one). It was the first one with this problem, as I was at his house when it all happened.
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
mrhaley30705 said:
I saw that all of your attempted solutions were with a win 7 machine. Have you given using a Linux environment any thought? No drivers to worry about, and if adb will recognize it you can push a recovery, as mentioned earlier
Click to expand...
Click to collapse
I haven't. Is there an easy guide on how to do this or how to get adb on linux?
Recently after trying to upgrade my LG G4 to android 6.0 by flashing the zips in recovery, I encountered a boot loop. I have tried many thing like using the LG Flash Tool, I also tried booting into recovery and restoring a backup I made, but none of this made any difference. Please I need help.
LG G4 H815 android 5.1.1 or 6.0 (not sure) I'm not sure because I tried to flash the zips fro android 6.0 via recovery and didn't work, then I restored my phone and tried to boot up but that failed to work as well.
Try to use the LG bridge tool.
Start lg bridge.
Connect your device while off with your usb cable.
It will start - nevermind, just keep it going.
Use the "solve update issue" option in the bottom right corner of the software update screen in lg bridge.
It will reinstall 6.0 without data loss.
TheReino said:
Try to use the LG bridge tool.
Start lg bridge.
Connect your device while off with your usb cable.
It will start - nevermind, just keep it going.
Use the "solve update issue" option in the bottom right corner of the software update screen in lg bridge.
It will reinstall 6.0 without data loss.
Click to expand...
Click to collapse
It does not detect that the device is connected, even when it is.
Takes some time to detect. Worked for me an hour ago...
TheReino said:
Takes some time to detect. Worked for me an hour ago...
Click to expand...
Click to collapse
I might have fixed it using a different method.
Wich method?
I have the same issue.. I send my phone to the repair center of amazon. Let´s look what they can do.
Not necessary, in bootloop, just connect usb and start lgup, when it detect it, (and it will as unknown mode device) tap com port it was found on and ui will open, then click on phone info, it will connect and establish a valid usb connection to phone and open new prompt with phone info...... Then start adb command prompt and enter 'adb reboot recovery' and bingo you're in recovery.... Solves every bootloop!
spoonymoon said:
Not necessary, in bootloop, just connect usb and start lgup, when it detect it, (and it will as unknown mode device) tap com port it was found on and ui will open, then click on phone info, it will connect and establish a valid usb connection to phone and open new prompt with phone info...... Then start adb command prompt and enter 'adb reboot recovery' and bingo you're in recovery.... Solves every bootloop!
Click to expand...
Click to collapse
If the phone in bootloop, such phone does not see any one program
This phone can be started only in the DM
spoonymoon said:
Not necessary, in bootloop, just connect usb and start lgup, when it detect it, (and it will as unknown mode device) tap com port it was found on and ui will open, then click on phone info, it will connect and establish a valid usb connection to phone and open new prompt with phone info...... Then start adb command prompt and enter 'adb reboot recovery' and bingo you're in recovery.... Solves every bootloop!
Click to expand...
Click to collapse
How do you mean ?
tap com port it was found on
Click to expand...
Click to collapse
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Dulu93 said:
Hello my dear xda community,
today my zenfone 2 ze551ml 2,3ghz 4gb WW just died.
heres the story:
i plugged it in to charge, then i unplugged it for about 10 minutes and plugged it in again but it didnt charge.
so i tried to reboot and then strange bootloops occured. after a few tries i managed to boot again. after the next reboot it got stuck in bootloop completely.
next i tried to boot into fastboot. sometimes it works sometimes it doesnt. when i want to boot into recovery a dead blinking bot appears and i cannot enter the options.
also sometimes my fastboot shows the serialnumber "0123456789abcdef" and sometimes it shows it correct. another thing is that when im in fastboot mode my pc does not recognize my phone.. no connection sound nothing. not on windows (yes drivers are installed) and not on linux.
only thing i managed was to establish a connection when i restored my bootloader with xfstk downloader. (did not change a thing)
so now when i boot there are 3 things that can happen:
1. dead bot blinking
2. asus boot screen (stuck)
3. bootloop
im having this problem for about 6 hours now and i have no further ideas how to possibly reflash stock firmware without being able to use fastboot (i can enter it but pc wont recognize) and without being able to properly start recovery mode (dead bot BLINKING)
yes my phone was rooted
and no i did not do any updates it just happened
EDIT: forgot to tell you.. when all this started i was able to boot a few times into my os (stock os just debloated) but was not able to charge or connect to pc. also when my phone is turned off and i connect it via usb to the charger or pc, the phone all of a sudden tries to boot
thanks in advance
cheers
Click to expand...
Click to collapse
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
k0rax said:
hard bricked my phone recently and have the same 123456etc serial. This happened when I flashed boot.img without doing Androidboot.img first. It was a long recovery process,but I did get it recovered; however, I don't think I can fast boot from the bootloader anymore. If you want details for that route I can give them. Basically just search for hard brick. I wouldn't recommend it unless you're desperate. My phone is up and rooted again tho, so I'm happy.
Click to expand...
Click to collapse
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
kenbo111 said:
Sounds like you might need a new cable too
Sent from my ASUS_Z00A using Tapatalk
Click to expand...
Click to collapse
i dont think so.. tried a few different cables
Dulu93 said:
yeah would be nice if you would guide me how to "recover" my phone again.
i tried flashing an os image via xfstk downloader but it failed probably due to the lack of proper files.
Click to expand...
Click to collapse
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
k0rax said:
What I did was found a raw image that was supposed to flash the whole phone. With Asus flash tool. You need the x.14 version. I couldn't get it to flash my phone but I could see it repartitioning . I pulled the cable after that. Don't reboot. Then flash all the .IMG files from the temp folder. After that, it was stock and took some work getting it unlocked then rooted. After that and having twrp I just reloaded my last saved image.
Click to expand...
Click to collapse
i can only find die x.15 version but i think it should be enough. the problem is that ze2 is not reacting to pc commands when in bootloader.. so i can not operate in with fastboot commands and asus flash tool requires fastboot mode
maybe my last option is to flash my phone via intel phone flash tool which operates via the soc. but i dont have the necessary files. as i remember i would need some flash.xml and image
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Dulu93 said:
maybe there is someone who is able to provide files i would need for the intel phone flash tool. i searched but i only could find the flash.xml file for other zenfone models then zenfone 2
Click to expand...
Click to collapse
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Dulu93 said:
tried to flash a raw file via intel phone flash tool but it says that automatic reboot is not supported on this devices and failed to reboot.
any solutions?
Click to expand...
Click to collapse
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
---------- Post added at 06:29 AM ---------- Previous post was at 06:21 AM ----------
k0rax said:
Unfortunately that didn't resolve my phone dialing, crashing the phone problem. :L
Click to expand...
Click to collapse
This did:
Make sure you go to settings-->apps-->default apps and select the dialer as your default application to make calls.
k0rax said:
OK, I think I've figured it out. Realized my phone was crashing when I went to make a call. RessurectionRemix formatted my SD card and wasn't readable anymore, so frustrated I said f**k it, let's start over.
1) it's 4 zeros, not 5.
You'll notice when you're flashing with xFSTK Downloader it attempts to flash twice. It appears the first flash is for the bootloader, and the second is for OS. It needs to flash both. I could not get it to flash both until I updated the GP Flag Override Value to 0x80000807. Then it went without a hitch.
2) install fastboot and adb with the driver package.
It's on the site here. Once I did that the ASUS Flash tool did its thing. For those wondering if it's doing something or not - the answer is, if the phone looks like it's not doing anything - it's not doing anything. After I installed adb and fastboot, along with the drivers, it took about 5 minutes to flash end to end without a hitch.
So the takeaway is - if it's flashing the first portion, you have connectivity to the phone - but that does NOT mean adb/fastboot will have connectivity like it should. That takes the special google drivers. Also, it needs to flash TWICE for xFSTK. If it doesn't do both, things will be broken.
I found a raw image that was quite old 2.15.40.13 on asus-zenfone.com. password for zip is asus-zenfone.com. I've flashed that, and about to update to 2.19.40.20 to do the unlock. Rooting with one click root worked fine, but unlock I don't know did. So I'm getting the specific version it says it works for. I'll post an update when that's done.
Cheers
Click to expand...
Click to collapse
thank you very much for your help.
the first point chaning it to 4 zeros did the trick. i was able to reinstall the bootloader.
but i still dont have connectivity via fastboot. im sure all drivers are installed and even on linux i cant see my phone. what is that special google driver?
k0rax said:
When using xfstk did it confirm it was able to write the bootloader? Also, what version of Windows? I have 10 and it took booting the Os into a recovery mode and accepting the drivers even though they weren't signed. In the offset or write settings in xfstk I had five zeroes. I heard someone use 4, but the majority said 5. I used 5. Are you able to see the boot screen as a 4 color box?
Click to expand...
Click to collapse
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Dulu93 said:
with 5 zeros it only loaded the firmware but skipped the os. with 4 zeros it loaded both. and yes i was able to see the colorbox.
im using windows 10 and what drivers do you mean? i installed the 15s driver package from xda
Click to expand...
Click to collapse
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
k0rax said:
This did it for me:
http://forum.xda-developers.com/showthread.php?p=48915118
After installing that, Asus flash tool worked for me
Also I found it will sometimes stall during flash. After partition and before flashing. If it doesn't show anything changing on the phone for 2-3 minutes, (except when it's flashing system), cose the app, make sure fastboot, fastboot2, and adb are all closed, and try again. Make sure to launch AFT as administrator.
Don't forget to catch the first boot before it loads the OS - AFT reboots once complete - and run unlock tool right then. if you miss it you have to start over.
Click to expand...
Click to collapse
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
Dulu93 said:
installed this package but still no luck.. even tried with freshly installed win7 but no luck. my fastboot mode is not being recognized
Click to expand...
Click to collapse
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
k0rax said:
Try a different USB port. On the back of the computer. For whatever reason that made a difference for me. I couldn't use the front ones.
---------- Post added at 09:16 PM ---------- Previous post was at 09:05 PM ----------
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
1.1 - Install IntelSocUSB
-First, Please disconnect the machine Zenfone your 2.
-Download Driver IntelSocUSB here:
http://drive.google.com/file/d/0B2oM...ew?usp=sharing
If you're using Windows 7:
Right-click the file -Click iSocUSB-Driver-Setup-1.2.0 choose "Run as Administrator".
-Make The installation steps as usual until you see a small window "Windows Security" requires authentication settings then click on the "install this driver software anyway"
-After This step, the driver installation is finished, continue to section 1.2 for connecting IntelSoc regime
Also iV you're using a virtualized environment I've heard people have had trouble. Try native if you can. The second part of the flash is fastboot. I don't remember the version I used. I'll check when I get home
Click to expand...
Click to collapse
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
You can leave flash tool and xfstk open same time. I flashed with xfstk, waited some time and moves between the bootloader options. Make sure no residual adb or fastboot exes are running. Then unplug the phone and plug it back in. Then it will show up. Select the option you have and click start. See if the bootloader shows any life or incoming partitioning happening . If that doesn't work reboot to bootloader scroll around in it to make sure it's loaded , it brings in the correct serial intermittently. But I don't think it's necessary.
---------- Post added at 12:42 AM ---------- Previous post was at 12:37 AM ----------
So xfstk reboots
Xfstk round two no reboot scroll around
AFT
Unplug USB from phone and reconnect
Should show up .
Then click start. Did it give an error with that X?
Look at processes and see if it's launched adb or fastboot
Dulu93 said:
ok.. lets summarize what i did:
1. installed adb/fastboot driver package
2. installed intel dnx driver (with isocusbdriver iwasnt able to open xfstk)
3. installed asus flash tool
4. installed xfstk downloader
5. loaded fw + os with xfstk downloader (successful)
-----
6. while in bootloader i connected my phone to the pc and tried to use asus flash tool (as admin) - not listing devices
i tried every usb port i have and several different cables, nothing helps
im slowly giving up... in the attachments you have snapshots how it looks like when im connected and in fastboot mode. to make sure no dead drivers are in my way im on a freshly installed win10
EDIT: now something happened. i flashed bootloader via xfstk, then i powered off my phone and connected it again. then for a second AFT showed my serial number, but the state was a red X
after i restore my bootloader via xfstk. what do i have to do so AFT can see my phone? what you can see in the attachments is all i get from AFT.. but i dont know how to stay connected
Click to expand...
Click to collapse
I think you're close - it's flashing what's needed, and recognized the phone, although it did for me also but fastboot didn't work until the drivers with adb and fastboot. The last things I would think is reinstall the Google adb fastboot drivers with the phone connected to the USB port that got you this far, and if there is some serial no verification, look for .14 version of AFT.
Hey everyone hopefully someone has an idea what is wrong with this phone.
I cannot enter the bootloader it keeps blinking and eventually just goes to the official recovery.
Tried going into xfstk (which i have used before), cant connect get usb drive has malfunctioned on computer.
Inside the OS (6.0) when i plug it in to the computer i get cant connect get usb drive has malfunctioned on computer.
I tried replacing the usb board same thing.
Also quick charge doesnt work anymore (im guess all related).
Is it a mobo problem, or any other things i can try?
Have you tried ? , update from sd card --putting the firmware you are on or the next updated version ,on ext sd before booting into recovery and updating ,
i have tried this method recently , hope it works for you ?
sharkie545 said:
Hey everyone hopefully someone has an idea what is wrong with this phone.
I cannot enter the bootloader it keeps blinking and eventually just goes to the official recovery.
Tried going into xfstk (which i have used before), cant connect get usb drive has malfunctioned on computer.
Inside the OS (6.0) when i plug it in to the computer i get cant connect get usb drive has malfunctioned on computer.
I tried replacing the usb board same thing.
Also quick charge doesnt work anymore (im guess all related).
Is it a mobo problem, or any other things i can try?
Click to expand...
Click to collapse
here are few things you can try.
1. enable usb debugging and connect your phone to PC.
now assuming you already got adb and fastboot driver on pc..
run command adb reboot-bootloader
if this does not work. try other method.
2. download droidboot.img firmware image and place in in root of your phone
download turminal on phone. now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/droidboot.img of=/dev/block/mmcblk0p13
# reboot bootloader
third you can try updating firmwware via recovery as timbernot suggested. if it fails as well. then xfstk is needed.
there may be chance your fastboot partition is wasted. i have never tried to erase in via adb. i will try to erase it via adb and tell you if got success
timbernot said:
Have you tried ? , update from sd card --putting the firmware you are on or the next updated version ,on ext sd before booting into recovery and updating ,
i have tried this method recently , hope it works for you ?
Click to expand...
Click to collapse
I tried to apply update via recovery. Same problem.
sukhwant717 said:
here are few things you can try.
1. enable usb debugging and connect your phone to PC.
now assuming you already got adb and fastboot driver on pc..
run command adb reboot-bootloader
if this does not work. try other method.
2. download droidboot.img firmware image and place in in root of your phone
download turminal on phone. now run terminal emulator and run the following commands one by one. wait for little time after every command.
$ su
# dd if=/sdcard/droidboot.img of=/dev/block/mmcblk0p13
# reboot bootloader
third you can try updating firmwware via recovery as timbernot suggested. if it fails as well. then xfstk is needed.
there may be chance your fastboot partition is wasted. i have never tried to erase in via adb. i will try to erase it via adb and tell you if got success
Click to expand...
Click to collapse
I'm not rooted, so with su? Nothing happens.
Xfstk was my first choice, but when I plug my phone into computer I can never get the phone to connect (get USB drive has malfunctioned). I have used it successfully before.
I can't enable USB debugging either for some reason. Once it says developer options enabled. I cannot find developer options.
Tapping build number numerous times ?
Nothing ?
---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------
sharkie545 said:
[/HIDE]
I tried to apply update via recovery. Same problem.
[/HIDE]
I'm not rooted, so with su? Nothing happens.
Xfstk was my first choice, but when I plug my phone into computer I can never get the phone to connect (get USB drive has malfunctioned). I have used it successfully before.
I can't enable USB debugging either for some reason. Once it says developer options enabled. I cannot find developer options.
Click to expand...
Click to collapse
re update from sd , firmware UL- blah blah , put another .zip on the end , so should read as user.zip.zip
Wipe data first cache too and try again
timbernot said:
Tapping build number numerous times ?
Nothing ?
---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------
re update from sd , firmware UL- blah blah , put another .zip on the end , so should read as user.zip.zip
Wipe data first cache too and try again
Click to expand...
Click to collapse
Ill try reflashing again, as i said reflashing works but still same problems. - didnt wipe data though - so will give that a try.
USB developers showed this time oddly enough, but still get A request for the USB device descriptor failed. on computer when i plug it in. (two diff computers - drivers installed - different cords - windows 7 and 10)
sharkie545 said:
Ill but still get A request for the USB device descriptor failed. on computer when i plug it in)
Click to expand...
Click to collapse
You have to tick the box on screen of phone to allow it to make contact with the pc , maybe your phone screen timed out and you missed the pop up on phone? , set phone screen to time out for a couple of mins and attempt again
:good:
Ps the wipe data , can take a while
sharkie545 said:
Ill try reflashing again, as i said reflashing works but still same problems. - didnt wipe data though - so will give that a try.
USB developers showed this time oddly enough, but still get A request for the USB device descriptor failed. on computer when i plug it in. (two diff computers - drivers installed - different cords - windows 7 and 10)
Click to expand...
Click to collapse
well seems like you have broken partition. need to flash xfstk. as it is booting properly you will not get it detected as moorefield. but even though install soc driver. then run xfstk. load files and click begin download. now connect your phone to pc in switch off mode and turn on
timbernot said:
You have to tick the box on screen of phone to allow it to make contact with the pc , maybe your phone screen timed out and you missed the pop up on phone? , set phone screen to time out for a couple of mins and attempt again
:good:
Ps the wipe data , can take a while
Click to expand...
Click to collapse
Unfortunately, still same problem yea it does take a long time lol never understood why. - wiped, clean install same problem. No popsups on phone ever just goes device has malfunctioned on computer.
sukhwant717 said:
well seems like you have broken partition. need to flash xfstk. as it is booting properly you will not get it detected as moorefield. but even though install soc driver. then run xfstk. load files and click begin download. now connect your phone to pc in switch off mode and turn on
Click to expand...
Click to collapse
Unfortunately i have tried that a dozen times, i know its supposed to from a off phone when you turn it on theres a delay from your phone actually turning on till when you see the asus logo, this is when xfstk takes over - but even then i get device malfunctioned on computer - (begin download mode is on).
sharkie545 said:
[/HIDE]
Unfortunately, still same problem yea it does take a long time lol never understood why. - wiped, clean install same problem. No popsups on phone ever just goes device has malfunctioned on computer.
[/HIDE]
Unfortunately i have tried that a dozen times, i know its supposed to from a off phone when you turn it on theres a delay from your phone actually turning on till when you see the asus logo, this is when xfstk takes over - but even then i get device malfunctioned on computer - (begin download mode is on).
Click to expand...
Click to collapse
Can you confirm build /date info ?
timbernot said:
Can you confirm build /date info ?
Click to expand...
Click to collapse
Build Number: MMB29P.WW-ASUS_Z00A-4.21.40.184_0577_user
Kernel: 3.10.72-x86_64_moor-gcb00463
sharkie545 said:
Build Number: MMB29P.WW-ASUS_Z00A-4.21.40.184_0577_user
Kernel: 3.10.72-x86_64_moor-gcb00463
Click to expand...
Click to collapse
edit my mistake you are on 6.0 already
Out of ideas , cannot help but think its something simple , even tho developers options is ticked , is USB debugging ticked lower down ? Going back to home screen - swipe down and flick thru different options, camera- charge only- file transfer ?
Driver issue but doesnt explain it happening on other pc`s so seems more like ^^^
Then again if a USB hardware issue on phone, usb charge board -- i havent witnessed it so not able to comment.
If i come up with any ideas i will post - goodluck
I am going to try something on my own fone first before i let you know
I am going to attempt the official downgrade version of LP WW-52.20.40.196 from .144 M - via sd card and update from sd in recovery , with the view of updating/downgrading droidboot in the process- i have just managed the downgrade from .184 M to .144 via same method which is nice to learn
@sharkie545
Success -- Downgrade of MM to LP works with the downgrade firmware above works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , detected .134 and ..144 and .184 MM update packages
timbernot said:
edit my mistake you are on 6.0 already
Out of ideas , cannot help but think its something simple , even tho developers options is ticked , is USB debugging ticked lower down ? Going back to home screen - swipe down and flick thru different options, camera- charge only- file transfer ?
Driver issue but doesnt explain it happening on other pc`s so seems more like ^^^
Then again if a USB hardware issue on phone, usb charge board -- i havent witnessed it so not able to comment.
If i come up with any ideas i will post - goodluck
I am going to try something on my own fone first before i let you know
I am going to attempt the official downgrade version of LP WW-52.20.40.196 from .144 M - via sd card and update from sd in recovery , with the view of updating/downgrading droidboot in the process- i have just managed the downgrade from .184 M to .144 via same method which is nice to learn
@sharkie545
Success -- Downgrade of MM to LP works with the downgrade firmware above works via update from sd in MM recovery ------- Marvelous
Stays on` updating IFWI ` for approx 8 mins but after that - bingo !
It also erases data after which it didnt updating in same OS
Also , i set it up -- after a reboot , detected .134 and ..144 and .184 MM update packages
Click to expand...
Click to collapse
Im going to try a few things first, i believe it has to do with the chip, or ribbon cable or IC chip. So im going to try to purchase a broken asus zenfone 2 (lcd problem) and swap some parts see if it fixes it. If it does well i know thats the problem. As i believe this is hardware related.
sharkie545 said:
[/HIDE]
Im going to try a few things first.
Click to expand...
Click to collapse
Wow just wow !!!!!!!!
timbernot said:
Wow just wow !!!!!!!!
Click to expand...
Click to collapse
Hehehe I appreciate the help. I have reformated many times lol. But since xfstk cannot be detected either (moorfield USB drive has malfunctioned) leads me to believe it has to be hardware related. Since moorfield is irrelevant of software/bootloader. It's kinda like the ultimate savour. Saved me out of some hetic problems before. (Leading me to wipe me imei #s lol which I had to than learn how to reprogram back lol)
Thank you again.
As the saying goes 'nothing ventured ......'
At least for all my hard work I found a way to downgrade from MM to LP with no PC , which obviously rewrites boot loader
Thank you
And you are two minutes away from finding out , should you decide to gamble like me
Although I have many phones to fall back on
Hey all,
I just got a OnePlus 5T and because I needed a specific system language I decided to flash a custom ROM. I unlocked the bootloader, flashed Derpfest on it and it was all good until I made a mistake. From the Developers options I unchecked "OEM Unlocking" and then when I restarted into the bootloader I did a fastboot oem lock
Now the phone says it's corrupted and it won't boot. Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Emo113 said:
Hey all,
Since it's bootloader is locked I can't unlock it, I can't go into recovery and I can't start the phone. Is there anything else I can do to get it back? I don't care about wiping everything at this point, I'm just trying to get it back to a working state.
I want to add I did try the Unbrick tool https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012 but I am getting stuck at the drivers. Windows won't see QHUSB_BULK in device manager and I don't see anywhere else where the driver for the phone might be. I do see the device when doing fastboot devices but again, can't see what drivers is using.
Thanks!
Click to expand...
Click to collapse
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
sn809 said:
The unbrick tool is your best bet, what you need to do is follow the instructions. If its windows 10, you can go to device manager and update drivers from there. Make sure you are logged in as admin. Also some antivirus don't like the MSM tool so you may need to disable that.
Ensure the sequence is right. Connect usb wire to computer, press volume up, connect usb c to phone. Some ppl have tried pressing both volume up and down at the same time to make it work (same way as resolving Sahara error). If it boots first thing you need to do is back up efs.
Second you need to run these commands
adb shell
su
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
exit.
It will save the persist.img on your phone internal memory. Save this as well as efs somewhere safe. Also share the persist.img with me cause I need it for the OPlus 5t for my phone.
Hope it helps
Click to expand...
Click to collapse
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Emo113 said:
Thanks for the help! I ended up finding a different Windows PC with no memory of the drivers for this phone so I was able to install them in the correct order and then run the MSM tool to get the phone back to stock Oreo. From there I unlocked the bootloader again to install TWRP and then my custom ROM.
Click to expand...
Click to collapse
That is superb. If you could do the other bit I would really appreciate it.
Thanks
sn809 said:
That is superb. If you could do the other bit I would really appreciate it.
Thanks
Click to expand...
Click to collapse
Hey there, sorry I totally mis-read the last part of your original post as something that I should do and I didn't see that you need that. Since I used the MDM tool I didn't bother to try your way first and since the phone wasn't mine to keep I already gave it to the owner so I don't have access to it anymore.
Again, very sorry about that.
No dramas. I also got it from some one else who was kind enough to lend it to me and let me root it and wipe it clean and then get the file and start using his phone again.
Thanks