Database Info

[GUIDE] One Click How to Root the Aria with Unrevoked 3.21

I first want to thank everyone at UnrEVOked for what they've done. I'm posting this because there aren't any really detailed instructions. Its an easy enough root, but I know I've been there before and even the simplest things can be tough if things aren't laid out. So here's a step by step tutorial.
Due to some bugs, Unrevoked 3.2 was taken down shortly after being released, but the updated version is now LIVE! So obviously we're going to bring you a video tutorial on how to do it! Thanks to the guys at Unrevoked for giving us this simple solution to rooting the HTC Aria.
LINK TO VIDEO WALKTHROUGH FOR HOW TO ROOT THE ARIA
◄●REQUIRED DOWNLOADS●►
EVERYONE: Unrevoked3. Download the version for your OS.
WINDOWS USERS: unrEVOked modified USB driver
◄●How to Install HBOOT Drivers (Windows Users ONLY)●►
If you're using Windows, you're going to have to install the HBOOT drivers first. You can follow this video tutorial:
How to Install HBOOT Drivers
and follow along with these written instructions provided by the Unrevoked team:
Download the unrEVOked modified USB driver and expand it somewhere you will remember.
Turn off your phone, then boot it into the HBOOT menu by holding power and volume down.
On your phone, you will have to select HBOOT USB at that menu by pressing volume down four times, then power. Wait until the screen flashes through an “SD Checking” message before pressing buttons; otherwise, the phone will ignore keypresses.
Connect the phone to your Windows machine with a USB cable and wait for the phone to say HBOOT USB PLUG on screen.
Open Device Manager.
Click Start, then right click on Computer, then click Properties, then click Device Manager.
Under Other devices, you should now see the Android 1.0 device.
Right click on Android 1.0 and click Update Driver Software:
Click on Browse my computer for driver software.
Click on Browse and select the Android USB Driver folder on on your computer, click ok, then click next.
You should get a status bar indicating that the driver is installing. If you get any warnings, just click Ok.
Your driver should install.
Click Close and make sure Android Bootloader Interface is listed under Android Phone.
◄●Instructions●►
Make sure you downloaded Unrevoked3 for your OS.
If you're on Windows, make sure you "uninstall HTC Sync or any other program that might talk to the phone over USB (doubletwist, etc). They will cause problems" (Unrevoked.com).
Plug your phone into your computer with USB.
Drag down from the notification bar on your phone and select "Charge Only" and "Remember this"
Make sure your phone has USB Debugging turned on by going to Menu>>Settings>>Applications>>Development and checking USB debugging.
Run the Reflash application that you downloaded.
Unrevoked will run its processes. Follow the few instructions it gives and thats it!
You're now rooted!
kopimi said:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
Click to expand...
Click to collapse

Great guide, would have really helped me last night while I was pulling my hair out haha. One thing you may want to add to the OP:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.

kopimi said:
Great guide, would have really helped me last night while I was pulling my hair out haha. One thing you may want to add to the OP:
If you're stuck on "Waiting for Device", INSTALL HTC Sync, but do NOT run it.
HTC Sync will load the necessary ADB drivers onto your computer, but so long as you do not let the process run while you are trying to run unrEVOked3, it will NOT interfere. Knowing this would have saved me quite a lot of time, so hopefully someone else reads this and they can salvage their sanity
Also, if you're stuck on "Waiting for Root", go ahead and restart your Android while its connected to the USB. It took me one reboot for the root to go into effect, and right after that, unrEVOked3 finished.
Click to expand...
Click to collapse
Thanks man Added to the OP

PS - Others have asked elsewhere if it flashes a custom recovery. Yes, it flashes Clockwork

I rooted my girlfriend's Aria with this and I see SuperUser Permissions (as you would with a root) but when I go to Android SDK and type "adb shell" I get a $ back instead of a 2. I also typed su and got back a permissions denied. I am also unable to do "adb remount" due to permissions. Is there any way around this?
Thanks
-Mike

LTD36 said:
I rooted my girlfriend's Aria with this and I see SuperUser Permissions (as you would with a root) but when I go to Android SDK and type "adb shell" I get a $ back instead of a 2. I also typed su and got back a permissions denied. I am also unable to do "adb remount" due to permissions. Is there any way around this?
Thanks
-Mike
Click to expand...
Click to collapse
You need to give the adb shell SuperUser permission, too. Load the SuperUser app and then make a adb shell connection while the SuperUser screen is up. Then when you type su at the $ prompt, the SuperUser app will give you the Allow/Deny prompt.
Regards,
Tom

tpbklake said:
You need to give the adb shell SuperUser permission, too. Load the SuperUser app and then make a adb shell connection while the SuperUser screen is up. Then when you type su at the $ prompt, the SuperUser app will give you the Allow/Deny prompt.
Regards,
Tom
Click to expand...
Click to collapse
Thanks for helping out and replying to that. I've been swamped with other stuff lately.

I just tried this and can't seem to get it to work. Can anybody help me out? I'm sure that I've done something wrong. I finally got unrEVOked to recognize my Aria, however when I clicked "Ok" (to root it when the message popped up) it said "Failed to push recovery. Terminating." What did I forget to do??

Nevermind... I got it to work finally.

Still shows S-ON

Freak said:
Still shows S-ON
Click to expand...
Click to collapse
Unrevoked 3.21 does not turn S-OFF on the Aria; that is only for a few CDMA phones like the EVO, Incredible, Hero and CDMA Desire.
Regards,
Tom

tpbklake said:
Unrevoked 3.21 does not turn S-OFF on the Aria; that is only for a few CDMA phones like the EVO, Incredible, Hero and CDMA Desire.
Regards,
Tom
Click to expand...
Click to collapse
Yeah don't worry about not having S-OFF, its not something necessary for a rooted phone. As long as you've got Superuser, you're set and rooted.

Sorry for my noobiness on the Aria, but what does using unrevoked to root it do for the Aria?
Sent from my HTC Liberty using XDA App

Still unable to install applications with the phone rooted
Hi, I followed the instructions, after I got the "done" message, i went to nandroid option made a backup, when it was finished i restarted the phone.
I´m trying to use Astro to install Sygic on the phone but I always get the same message.... you phone is blocked.
I see the little ninja in apps... what else is missing? what is wrong?
Thanks for your help...
I´m about to give up and sell this phone
The day i got the phone I upgraded it to the latest firmware available in HTC web page, is that the ugly part of the story?
-------------------------------------------------------
I solved this issue by istalling a custom image.
Last night I istalled the liberated_aria_ddx_R012_signed, I have to say that everythign is going perfect, no problems so far.
But everytime I plug the cable and the phone is off, it starts in recovery mode, so i have to select reboot.
Before flashing the image, I formated the SD card, wiped data, cache and dalvik cache.
If I turn on the phone it starts normally, It´s just happening when I plug the usb cable or the charger.
I also made other test, I plugged the phone when it was on, then I turned it off (with the cable plugged), when it finished the turning off process it automatically started again in the clockwork recovery mode.
Could you please tell me how to solve this?... this is my first Android phone, I donñt want it to start in recovery mode when I just want to charge it.
Thanks in advance

Phone needs to be on while charging. You no longer have to turn equipment off to get a full charge. If you charge while it's off it will go into recovery mode.

echodun said:
Phone needs to be on while charging. You no longer have to turn equipment off to get a full charge. If you charge while it's off it will go into recovery mode.
Click to expand...
Click to collapse
Thanks for your prompt answer.
Is there any way to change it?, i´d like it to work as usual, you plug it you get the green battery charging... that way it is impossible to make misstakes, for the next time i need to get in to recovery mode i would push pwer + volume-.
maybe by applying a mod.zip using clockwork?

0ptimus82 said:
Thanks for your prompt answer.
Is there any way to change it?, i´d like it to work as usual, you plug it you get the green battery charging... that way it is impossible to make misstakes, for the next time i need to get in to recovery mode i would push pwer + volume-.
maybe by applying a mod.zip using clockwork?
Click to expand...
Click to collapse
No way that I know of. It's on my Cyangenmod ROM too. Maybe a product of using the Unrevoked method of rooting. When I plug mine in to the computer charging cable I get a red light for charging and then screen goes off in about 10 secs. Not a big deal to me although it through me for a loop at first too.

echodun said:
No way that I know of. It's on my Cyangenmod ROM too. Maybe a product of using the Unrevoked method of rooting. When I plug mine in to the computer charging cable I get a red light for charging and then screen goes off in about 10 secs. Not a big deal to me although it through me for a loop at first too.
Click to expand...
Click to collapse
I know... it´s not a problem, it´s just that it´s not the way it happened for some years ago since i´ve had a cell phone .
So, the only way to avoid it is to uninstall clockwork recovery?

Cracked my screen on my rooted aria after my camera stopped working and I had filed for a warranty replacement. Was so happy with the original phone that I took the $300 hit they would apply if I sent the bad phone back with physical damage...I decided to keep the new phone and ATT will allow me to pay them in several installments with my monthly bill..
I promptly used your instructions to root this new phone. Took me all of 5 minutes.
Great job.

You can replace the glass on an Aria for a lot less than $300.

I bricked my phone!!!!!!

HELP! I was trying to frehsly install a rom..
so i used odin to "master clear" everything
it deleted everything!
hoping that in recovery mode, it'll let me "mount storage" so i can transfer my new rom into the phone, that didnt happen!!!
so, then i tried to go with odin 1 click to install i896 stock...
and it doesnt work , so i unplugged phone, and now i get that mobile phone error..
please help, the only thing i can do successfully do is put my phone in download mode! D:
PLEASE! PLEASE!
THANK YOU!

Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Sent from my SAMSUNG-SGH-I897 using XDA App

Read carefully.....
ags on board said:
Open Odin, turn off your phone, hold the volume buttons, and plug it in to get it in download mode. Then use Odin to get stock rom on, then go from there.
Click to expand...
Click to collapse
+1
Go into the ODIN thread and read extensively. Since you can get into download mode, make sure that once you connect your phone you get the COM notification in ODIN. Mine always appears in the small box in the upper left portion of ODIN one-click (if you don't get this, reinstall the samsung drivers found in the ODIN thread and reboot. If you're running Win7, make sure you run ODIN as admin).
Master Clear does exactly what it says...it wipes all of your data. MC is only supposed to be used when your phone is on and fully booted up with USB debugging on.
Flashing back to stock should only take ~5 minutes max - if it halts unplug, pull your battery, wait a few seconds, and restart. If it continues to fail, try a different USB port. If using a PC, use the back USB ports. If it still fails, try a different system. (I had this issue this weekend and finally got it on the first run on my friend's laptop - not sure what happened, had flashed 5-6 times on mine previously).
Hope this helps. Once you're back to stock, be sure to thank designgears for his killer dev work!
EDIT:
PS It's pretty tough to brick a cappy - read extensively in the ODIN thread and you'll see what I mean.

Its always good practice to back everything up and know the step by step procedures before you ever do anything. Good luck!

Connexxions "how to" videos are VERY detailed and shows you step by step how to do just about everything on this phone. I highly recommend them.

don't panic, ur lucky that u can still get into download mode. that is just soft brick I think..
Sent from my SAMSUNG-SGH-I897 using XDA App

Bricked, need help.

So, I bricked my Infuse last night at work when I tried installing MIUI from ROM Manager. I've been trying to unbrick using gtg's Ultimate Unbrick method, but no luck. I believe it's something to do with the Samsung Drivers since my phone is not recognized in Odin. Tried to redownload the Drivers from Samsung's website, but still doesn't work.
Any ideas?
BTW, running Windows 7 32bit

why would you install a rom that's for a different phone?
can you boot into recovery mode? did you try the "jig"?

Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.

the reason other roms pop up in rom manager is because you are using the galaxy recovery. unless it says "for infuse" (there is only one, gtg's rom) it wont work. bummer dude. im all out of ideas, never had this happen. hopefully someone who's been through this can chime in and provide some info that will help you.
on a side note, why cant you take it to an att branch and have them exchange it for you?

Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
I hope u have USB debugging turned on. If yes, u cud try this:
1. Download and install android SDK (search google for this if don't know how to).
2. Open a command prompt
3. Type in "adb reboot recovery" without quotes, and don't hit enter
4. Connect phone to PC
5. Turn the phone on
6. Wait for "samsung" to appear, and hit enter in command prompt
7. If it says "device not found", use the up arrow to get the command from history, and hit enter again. At some point, it should issue the command to the device.
8. If u can get to recovery, well, u have a way to now try to flash any other ROM.
Don't give up. Samsung has strong phones that could be got out of soft bricks most of the time.

Delete/reinstall the drivers.
Infuse 4G

Just tried Diablo's method, and it tells me command not recognized...

Download Kies on your pc to have it recognize ur phone. Run odin. Put ur phone in download mode (pull out battery, put it back in, hold both volume buttons down, plug in ur usb) and use gtg's unbrick.
Sent from my SAMSUNG-SGH-I997 using XDA App

Tried Kies before and it would never recognize the Infuse. Should I pick Galaxy?

UPDATE!!
Redownloaded Kies and installed the drivers (for the 500th or so time) and now Odin is recognizing a device. It's showing [COM3] instead of COM## but I'm letting Odin do its thing. Seems to be working... Crossing my fingers!
EDIT::
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
****in A! Thanks for the help guys!

Pat713 said:
Didn't think there would be a listed ROM in the manager if it wasn't for the phone...
Won't boot into recovery at all, Samsung pops up, then it goes blank, and Samsung pops up again. It loops like that until I pull the battery.
Was hoping to avoid having to buy something then waiting for it to arrive, as I need the phone working asap.
Click to expand...
Click to collapse
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251

Misterjunky said:
You need to buy a jig, that will solve the problem.
The jig is less than $10 bucks shipped if you buy it on ebay.
Here is the link:
http://cgi.ebay.com/Samsung-Galaxy-...0563626533?pt=Cell_Phones&hash=item20ba3eba25
Easy to use.. all U do is pull the battery, plug the jig into usb port on the fone replace battery and you will see the big triangle saying "Download" then unplug the jig and load odin.
Setup the pda/phone/pit/csc files in odin3. Then plug in the usb cable from computer to the phone making sure that where odin says "com" that it is highlighted yellow. Then click start in Odin and wait til it says "reboot" after that you will have a working phone with stock froyo 2.2 . Don't change any default setting in odin.
Use the "Ultimate Unbrick" rom - Here is the link:
http://forum.xda-developers.com/showthread.php?t=1116251
Click to expand...
Click to collapse
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D

Pat713 said:
Just tried Diablo's method, and it tells me command not recognized...
Click to expand...
Click to collapse
That means u do not have android toolkit installed on ur system. You should install it first for the adb commands to work.
I would recommend downloading and learning the basics of adb. This could be a life saver in many no-so-happy situations.

Pat713 said:
I got it unbricked now, problem was the drivers wouldn't correctly install on Win7.
But, now I have a new problem. Just put 3e recovery on and flashed CWM, only to get bricked again (no problems unbricking this time, taking longer to type this than it took to unbrick...). Also, sometimes apps refuse to download from the Market. I tap "INSTALL" and the notification pops up saying downloading, but then it disappears and nothing happens, its like I hit cancel. I'm going to call it for today and get some sleep. At least the phone is usable now! :-D
Click to expand...
Click to collapse
Had this same problem and it turned out to be a hardware problem. There was no gix for it. Also youll notice that gtgs recovery includes a preroot. If you need to send your phonr back like i did youll need to get that off. It was tricky for me because the hardware was so screwey. I got it off after a few reboots of the phone and a couple of trys with superoneclick.
Sent from my SAMSUNG-SGH-I997 using XDA App

Semi Brick, STUCK ON DOWNLOAD MODE. HELP

Hello everyone, I totally pulled a noob earlier, with all the excitement going around with the official ICS update going around, accidentally I pushed a 19100 ROM into my sgs2 by sprint; and now my device is semi brick, neither Kies, Odin nor SimpleDownloaderTool for SPH-D710 recognizes the device, after downloading the correct drivers into my computer.. now what do I do?

If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.

sgs4g SGH-T959V always reboot into download mode, even after successful oneclick
lumin30 said:
If you have a Galaxy S 4G SGH-T959V follow the second link in my signature, read thoroughly and follow directions.
Click to expand...
Click to collapse
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.

Pro tip: Open a new thread if you need to ask a question or need help. Don't "hi-jack" other threads. (considering that the original thread is from 2012)
But it's done...
teevoo said:
Hi, I used OneClick. Things seems to work. The flash was successful. If I do a reboot using the phone's power button or if I pull its battery, the phone always boot back into download mode, thus negating the flash and I have to start over. When the phone is in this state, I am not able to connect via adb or reboot into recovery mode.
Click to expand...
Click to collapse
Did you follow @lumin30's guide?
teevoo said:
One strange thing is if the reboot is done via 'adb reboot', via the OneClick process, or via the reboot option in recovery mode, it boots normally. So esstentially it means after a successful flash, the phone has to remain on forever, with an occasional adb reboot.
Click to expand...
Click to collapse
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
teevoo said:
Is there anything I can do to restore this phone? Or as a consolation prize, force a normal restart on a one off basis via my computer somehow.
P.S. I'm new to the forum. Please let me know if this is not the right place to post this. Thank you.
Click to expand...
Click to collapse
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.

bhundven said:
Did you follow @lumin30's guide?
Click to expand...
Click to collapse
Yes. Oh and I made several posts (not hijack ) regarding this issue elsewhere in the forum but got no response. One thing I forgot to mention in this version is that originally, the download mode on phone was triggered physically somehow. My uncle accidentally dropped the phone in water. He then blew it dry with a strong fan and must have turned it back on too early. Since then the phone's been in download mode.
bhundven said:
The phone is in download mode. The phone isn't being reset by adb, it's being reset by heimdall/odin. I think this sounds like a USB issue.
Click to expand...
Click to collapse
I'm now wondering if there is a program that can do a reset like heimdall/odin without going through the whole reflashing process. Assuming the phone's memory components haven't been physically damage, at least this would mean I can restart the phone to normal mode quickly.
bhundven said:
I've seen this problem a few times, and usually I found it was a bad cable or a bad USB port.
Also make sure the usb port is clean of any lint/objects/dirt.
I had a dell laptop once, where none of the usb ports worked with heimdall or odin. I tried the same one-click on my apple mac, and on another HP laptop. I found that I also had a bad cable. I replaced the cable and everything worked on my Mac and HP, but still nothing on my dell. Same setup - debian linux - on each laptop. The one-click looks like everything flashes, but if you pull the battery and turn it on, it's back at the download mode screen.
Click to expand...
Click to collapse
Ok, I'll try to find a different computer to do this with, although right now I'm thinking USB is not the case as I have successfully performed the same flash on a different sgs4g and it works just fine (the difference was that phone was never stuck in download mode to begin with). For the problem phone, I have tried a couple of ports and 2 different cables on my Mac. From what you just told me, perhaps the phone's usb port is the culprit.
Thanks for your reply, and thanks for all the programming work you've contributed to this forum :good:

Phone Bricked After Installing OTA Update

I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.

adrunkenmess1 said:
I recently purchased an Oneplus 7 pro from Ebay and the phone was working fine. It's locked to T-Mobile and it prompted me to take an update, I believe the update was for November 2019 and was almost 2 gb in size. I rebooted the phone when it said to reboot to install the new features, and the phone never came back on after that. I tried charging it for hours, tried holding the power button + volume up/down buttons to get it to reboot, and none of this has done anything for the phone. There's no sign of life, the phone was working great prior to the update.
Is there any suggestions for fixing this?
Thanks.
Click to expand...
Click to collapse
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.

MrSteelX said:
go here https://forum.xda-developers.com/oneplus-7-pro/how-to/guide-mega-unbrick-guide-hard-bricked-t3934659 and use the global version. that will allow you bootloader unlock phone when done.
Click to expand...
Click to collapse
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.

adrunkenmess1 said:
Thanks for the link, I downloaded everything and disabled driver enforcement but my phone is still not showing up in Device Manager. The computer makes a noise as I connect it to the USB port, but other than that it isn't doing anything.
Click to expand...
Click to collapse
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.

MrSteelX said:
with the phone off, hold vol up and plug usb cable in. It should boot to edi mode then.
Click to expand...
Click to collapse
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"

Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
adrunkenmess1 said:
I think it was the cable I was using that was causing it....used a better usb cable and it recognized in the Device Manager.
I can't flash it though as it gives error "param preload device not match image"
Click to expand...
Click to collapse

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I was able to get it to flash successfully. I used the files from the tmobile to international conversion since it required a hacked MSM tool. I'm a complete Noob at phone flashing and really spent a LOT of time reading tonight to figure it out. Phone flashed successfully but said the battery was now too low to turn on. At least it says something!
I'm charging it up now and hopefully it works after this!

amirage said:
Hi,
I'm assuming you are trying to revive the phone using MSM tool. If so, the only successful way to do this is to connect the phone to a USB 2.0 port using the official cable. This will make the phone appear on the tool and then you can proceed.
Click to expand...
Click to collapse
I use a USB 3.0 and USB c port on my computer and no issues

OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?

jamescable said:
I use a USB 3.0 and USB c port on my computer and no issues
Click to expand...
Click to collapse
Really, I couldn't get the phone to come up on the MSM tool in the Qualcomm mode on USB 3 port. But when I connected the cable to the USB port, it appeared there.

adrunkenmess1 said:
OK so I manage to get the phone flashed to the international version using the MSM tool. I then downloaded the DP 3 developer file like suggested. I put it in the root for my phone, went to system settings, system update, and got to install it locally. It installed 100% and then asked me to reboot for the changes to take effect.
I reboot the phone and then nothing, it's black and unresponsive the way it was when this whole thing started.
I'm sure I can just reflash the international file with MSM to get it working, but is there any reason why updating my phone in this manner always fails and a way for me to fix it?
Click to expand...
Click to collapse
MSM phone, unlock bootloader and flash twrp. Use twrp to flash system update and see if it works