Related
Hey guys, I'm in need of some help with my prime. Just got it a few days ago and rooted it just fine using vipermod. The used OTA root keeper to save root for ICS. After installing ICS, I restored root and everything was fine. Then I noticed that my prime would loose wifi signal ever 2 minutes. I did a factory reset thinking that would fix it (and it did) but now a few things are beyond messed up and i can't figure it out! For one, I cannot access the notifications area (when i tap it, nothing comes up) the home button also does not work at all. so i tried to install cwm so i can re flash the ROM from scratch but now ADB does not see my device AT ALL. i tried everything. i have all the drivers installed and all. I'm at a loss and extremely frustrated. does anyone know whats going on here? how can i get adb to see my prime so i can flash cwm? or is there an alternative way to completely flash the rom? (i also tried the method on asus' website by downloading ICS and placing it on the root of the SD, and still nothing)
You won't be able to install CWM without unlocking the bootloader (and voiding your warranty first). After that, you can no longer flash a ROM from Asus without bricking your device. There is the latest updated ROM in the dev section though.
Good luck!
I did that as well and still nothing :-/
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
scook9 said:
For ADB to work you need to have usb debugging enabled on the tablet....probably a silly thing to ask but always have to check...
Click to expand...
Click to collapse
yup thats enabled as well. when i first got it with 3.2 on it, i plugged it in and drivers installed automatically and adb recognized it right away. now that ics is on it, adb cant see it. i have never ran into this with any android device ever.
Mine did that once and I also had to disable ASUS Sync in settings. After that ADB worked fine.
Update the drivers on your PC
http://forum.xda-developers.com/showthread.php?t=1426502
If you do it right, it will work.
BUT YOU DONT EVEN NEED ADB, LOOK BELOW (I am not advocating not knowing how to adb but lets just fix your prime)
Since you have unlocked your bootloader you can install CWM and just install the latest Virtuous Rom:
If you dont have CWM download Rom Manager from the market, run it, select "Flash recovery" at the top. (btw rom manager just released this today)
*Note that the 'reboot into recovery' option within RM will not reboot into recovery, you must do it manually.. See below
-Backup your apps with Titanium Backup if you want
-Download Virtuous S
-Boot into recovery (directions beneath)
---Power off
---Hold Vol Down (-) and Power until you see spash screen with white text at the top THEN HIT VOL UP (+) within 5 seconds. this will boot into recovery
-if you are coming from stock then: select "wipe data/factory reset"
-Install zip from sdcard, browse for the rom
-Profit?
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Nissan350 said:
Guys, thanks a million for all the replies! After uninstalling the drivers and re-installing them then moving my ADB directory to the root of my C drive, it now recognizes my Prime and I was able to flash CWM. I'm now running Virtuous Prime and loving it! Thanks again!
Click to expand...
Click to collapse
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
mtotho said:
I would still recommend that you go download Rom Manager and flash the new recovery.
The one in the thread in the dev section is an unofficial port. The one is the Rom Manager is official and works a little better.
Additionally, if you plan to use ADB in the future, there is a simple thing you can do to make it so that within command prompt you can type 'adb' commands ANYWHERE, and not just in the folder that your adb files are..
Right click on Computer--> Properties-->Advanced-->Environmental Variables
Click edit on PATH in the top box if it exists already, add ';' to the end of the previous path and enter the path to your ADB, mine is like
Code:
C:\Users\Mike\Downloads\android-sdk_r16-windows\android-sdk-windows\platform-tools\;
and if it PATH doesnt already exist just create it.
Hope I helped
Click to expand...
Click to collapse
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Nissan350 said:
Will do! Thanks for the PATH tip! Wish I knew about it earlier lmao.
Click to expand...
Click to collapse
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
mtotho said:
yup lol, makes it so you can do it from any directory.. absolutely necessary if you use adb frequently
Click to expand...
Click to collapse
Awsome, thanks again man
Hello All,
I posted this on the post for Android Revolution and seem to have run out of interest. This was my post.
Hello,
I messed up and flashed the boot file before I installed the rom file in the internal storage. Now the phone wont boot at all. Can you help me fix this please.
I've tried to search for answers but cant find anything.
I can get into fastboot mode and into CMW mode. So I am able to enter sideload mode but cant get the phone to take the sideload.
I'm afraid I may have formatted the storage too.
Can anyone help me please?
Steve the noob.
Right now I am completely bricked. Tried everything, reinstalled SDK, tried sideloading in a couple of ways, stuck in bootloader or CMW. Try to load and sticks on white HTC page.
PLEASE HELP. I followed all of the directions except for loading the boot first.
Is there a factory reset like the old Oden system that could save me?
Can you get into fastboot?
If so you need to then flash the boot.img via fastboot.
Type fastboot flash (name of file).img in command prompt and you should be good to go!
which boot image?
Looks like you took the wrong version for your phone. You have an AT&T / Telus phone. You can not take an International ROM for your phone.
Only AT&T / TELUS ROMs will work on your phone.
I forgot, you can not bricked your phone since our HTC ONE X+ are S-ON, you just missed something to have it going.
stevespens said:
which boot image?
Click to expand...
Click to collapse
Which CWM are you on? Lloir or the other guys? VERIFY YOU HAVE THE PROPER RECOVERY INSTALLED. IF YOU ARE ON THE AT&T MODEL USE THE AT&T RECOVERY
You can run an RUU (verify proper carrier and model) while at the fastboot screen, or install TWRP and try to sideload using that from the SDK PLATFORM TOOLS FOLDER. You mentioned you have the SDK installed but I need to stress DO NOT USE THE TOOL KIT IT IS WORTHLESS. Make sure you have the official HTC drivers installed that come with HTC SYNC using generic drivers from the tool kit usually yields worthless resutls.
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
stevespens said:
I cant get the rom on the phone. It's completely stuck in a boot loop. Only thing I can do is go into bootloader or CWM. I need to sideload a rom. But it wont let me.
Click to expand...
Click to collapse
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Kraizk said:
I looked at your android revolution thread. STOP USING THE TOOL KIT. It is a POS.
Click to expand...
Click to collapse
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
stevespens said:
OK. Gotcha. Thanks for the help.
Now what do I do? I am bricked.
Click to expand...
Click to collapse
Read my previous post I gave you instructions. http://forum.xda-developers.com/showpost.php?p=39261003&postcount=5
OK...
Let's start with the correct Recovery for your phone, download link -> Click me!
N.B. -> Rename this file like this -> TWRP2recovery
Put this file in your platform-tools of SDK folder.
Put your phone in bootloader (fastboot USB)
Type this : fasboot devices (Enter... you should have your serial in return)
Then type : fastboot flash recovery TWRP2recovery.img (Enter)
Again type : fastboot erase cache (Enter)
Unplug your USB cable and hit Power button one time
Select Recovery
Hit Power button one time to reboot in Recovery
Try to sideload an ATT&T / TELUS ROM ONLY
Go for Elegancia AT&T/TELUS ROM for this time. (Choose one of your choice in the Download section here)
What are the results?
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
stevespens said:
Well, thanks for all your efforts, but it's a lost cause. I tried the last posters suggestions and it wont let me flash the recovery at all. It's done. I have insurance so I'm just going to smash it and file a claim. I give up. I wont do that again.
Click to expand...
Click to collapse
Have you tried just running the RUU? People say it takes a few times. Your phone is not bricked if you can get into fastboot.
Sent from my HTC One X+ using xda premium
thanks for coming back.
Lets give this a try.
Lucky Thirteen said:
Which error you have when you try to flash the recovery? Is your phone recognized at least when you are typing : adb devices ?
Click to expand...
Click to collapse
I got this when I typed "fastboot devices",,,
Then when I typed fastboot recovery to load the file, it showed this
just tried a dif file path and got this
Oh, by the way, my bootloader has been relocked. Can I fix this through bootloader?
First let's install your SDK folder correctly then you will see, it will work flawlessly.
Have a look at my screenshot, see how mine look simple compare to yours.... Yes, I have two devices plugged.
Install your SDK tool like it is explained in this thread.
The version numbers are different but the installation stay the same.
EDIT : What is your computer OS? I will point you to the good htc drivers.
So I should not be doing this on so little sleep, obviously. I have a Verizon HTC Droid DNA, Moonshine S-off, TWRP, and I had CarbonROM on it, but I was having issues so after some fumbling around and trying different things, I was at a loss. So I wiped all data and formatted. Well, before this, for some damn reason, I think I turned USB Debug off. Now I can't get into Fastboot USB. Am I totally screwed? My PC won't communicate with the phone.
HELP!
Actually its difficult to be "totally screwed" you can always hold the power + volume down until the phone boots into HBoot. Once your in HBoot again fastboot should work if it doesn't then that generally a driver issue. Once your back in HBoot you can select fastboot and that will give you the option to boot back into recovery. Once you get into recovery again I would select sideload and flash the ROM using "adb sideload <rom name>" making sure your in the adb directory and so is the ROM. Hope this helps.
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Kevin5377 said:
Yeah, I can still get into fastboot (just not fastboot usb) and recovery, but my PC and phone aren't talking when they were before I started screwing around.
Sent from my Nexus 7 - Carbon Rom
Click to expand...
Click to collapse
PC driver issue, go into device manager and load new driver
I'll take a look
Sent from my Nexus 7 - Carbon Rom
Yeah, I'm not even getting the Windows sound like I connected anything. Usually it'll tell you no drivers or unsuccessful installation or something!
Holy crap... well you were right... it was a driver issue. I reinstalled the HTC drivers and I got FASTBOOT USB now... thank goodness!
I feel like my brain isn't working. How do I now get my .zip on my device using fastboot so I can then get into recovery and flash it?
Nevermind... booted to recovery, used adb to push my .zip to device
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
trickster2369 said:
Glad you got it figured out.
It's always fun to watch people talk to themselves. :laugh:
Click to expand...
Click to collapse
Even more fun when they answer themselves
hawkstwelve said:
I think I did the exact as you. Tried to get fancy with things too early in the morning and ended up formatting data. I was wondering how you pushed the zip for the ROM onto your device using adb? I can get adb to discover my device as long as its in recovery but I'm not sure of the commands it takes to push a file like that onto your sdcard in order to reflash it in recovery.
Any help greatly appreciated.
Click to expand...
Click to collapse
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Enjoy
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Thanks that worked! Back to loving viper.
I Have a similar problem
Kevin5377 said:
First, make sure your .zip is in the same folder as your adb. Then in your cmd window, (assuming you're in the correct directory) type "adb push ROM.zip /sdcard/ROM.zip" replacing ROM with the EXACT name of the ROM file and including the .zip piece on both ends.
And yes, I know first hand how amusing it is, and somewhat gratifying watching someone figure it out on their own. I could not, however, have done it without you guys. I assumed since my phone was communicating not 10 minutes earlier with my PC, it wasn't a driver issue. But in the end, that's exactly what it was.
Click to expand...
Click to collapse
Hey i'm new to this and i also formated my phone when installing a new rom i can still get into twrp and when i plug in the phone to the computer fastboot usb shows up and it makes the sound on the computer however when i type adb devices in the cmd its blank could someone please walk me through the adb stuff sorry for being a noob
I also have a OTG cable but i tried to plug in a 16GB FAT32 flash drive but twrp didnt recognize it. it says unable to mount
Thanks a bunch
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Kevin5377 said:
Adb commands are done with the phone booted into recovery. Fastboot commands are done with the phone booted to, well, Fastboot.
Sent from my ViperDNA
Click to expand...
Click to collapse
Thanks a bunch but i plugged in a bunch of flash drives until one was recognized and then was able to restore my old ROM... WHEW
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
vectorer said:
I tried following the upgrade to ViperX+2.0.1 and after flashing recovery and boot.img I seem to be stuck in a loop. Now I'm stuck on HTC splash screen and can't do anything. I go to recovery TWRP and none of my backups are there!
I cannot reboot. Computer won't recognise phone on USB.
Please Help!!!
Click to expand...
Click to collapse
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
superbay said:
How do you locate your backup in TWRP? Is it from the restore menu or from file manager menu? I never see my backups in file manager but if you choose restore menu, they are normally there.
Click to expand...
Click to collapse
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
vectorer said:
Restore menu, but there is nothing there! I cannot find anything in the file manager or install zip and I know there are zip files!
Am I bricked? Any hope?
Click to expand...
Click to collapse
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
superbay said:
afaik as long as you can go to bootloader, your device is not bricked. You can still push the zip file or ruu. What indicates that your computer doesnt recognize the device?
Click to expand...
Click to collapse
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
vectorer said:
when I connect it the MTP driver won't install, I had thought to at least salvage some pictures etc. but the phone doesn't show in windows.
I was running ViperX+ 2.0.0, I've now got the 2.0.1 zip file so I'm going to try to sideload that, following directions from here http://forum.xda-developers.com/showthread.php?t=2318497, since I'm really new at this and need spoon feeding. I admit that if it works I am worried about the boot.img file but such is life. fingers crossed
okay, I just tried to flash the boot.img file using VenomKernelFlasher.exe and it won't do it because the device isn't connected!!
this driver is killing me
Click to expand...
Click to collapse
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
superbay said:
Never mind about the MTP driver, mate. It is not always an indication that the computer doesn't recognize the phone. I have installed the same driver in several computers with similar OS and about half of them shows that MTP driver failed to install. HTC sync even always says no device connected. However, the computer still recognize the phone to be used for rooting or doing anything using hassoon's tool.
Before continuing, do you own HTC One or One X+? The link you refered shows that it's HTC One thread.
For HTC One X+ you can read in the 4th post in this thread http://forum.xda-developers.com/showthread.php?t=2066390
Click to expand...
Click to collapse
Thanks. It's HTC One X+, I got there from a Google search for sideload as I know zero about it. As it turns out it didn't work, got to 22% then failed every time. I'll check out that link now.
Thanks again.
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
vectorer said:
Ran Hasssoon and got
adb server is out of date. killing...
* daemon started successfully *
* failed to write data 'protocol fault (no status)' *
C:\Hassoon\One_X+_All-In-One_Kit_v\data>
Next idea please
Where can I find an RUU for this phone........ HTC One X+ EvitaRE
Click to expand...
Click to collapse
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
Click to expand...
Click to collapse
how would i do this operation??
now no matter what i try i get
error: closed
vectorer said:
been absent for a few days.
yes it was sideload, i'll try the data thing now
also i've had viper for a while and like it, but if you think another rom would work better in this case please let me know
i appreciate all your help. i'm using my old sensation 4G right now..... i like it but have gotten used to the OneX+ so i really hope to be up and running again
Click to expand...
Click to collapse
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
vectorer said:
how would i do this operation??
Click to expand...
Click to collapse
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
vectorer said:
now no matter what i try i get
error: closed
Click to expand...
Click to collapse
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
superbay said:
Helping anyone in need whenever possible is how people give back to this community
I occassionally had the same case with you and surely would want yo see yours running up again like mine. The difference is i had several rom zips in my hox+ at that time but everytime i flashed any of them and no matter how many times i wipe and flash boot.img, it ended up in bootloop.
In hassoon toolkit there is a folder named 'data' just put your zip file there and choose the file from there when sideloading. Sometimes problem occurs from such minor thing where any file you need (rom, recovery, kernel) needs to be put in the adb folder.
If i were you,i would start fresh from another computer just to make sure that it is not your computer causing that and to see if it makes any difference. However I still believe that the computer recognizes the device,otherwise the command prompt will say 'waiting for device' if adb doesn't recognize the device. If such problem still persists, then i think it is the time for you to ruu.
Well i expect any help from others since the beginning. This thread has been viewed more than 500 times but there are you and me only mate. Just dont stop trying anyway. That's where your learning is from and how you prevail
Click to expand...
Click to collapse
thanks I'll keep trying this weekend
vectorer said:
thanks I'll keep trying this weekend
Click to expand...
Click to collapse
Just keep posting here to see how far your effort is with it. Good luck
superbay said:
Did you get that after choosing sideload option? try putting the zip file in the data folder in hassoon toolkit.
For ruu you can try look at q18 in the firsy post of this thread forum.xda-developers.com/showthread.php?t=2179337
My last post in that thread might help too. However, check your device radio version first to see which one suits yours.
or maybe this thread might help as well since it's for Telus version forum.xda-developers.com/showthread.php?t=2051032
Click to expand...
Click to collapse
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
vectorer said:
mine may not be a telus version
my radio version is "RADIO-SSD:2.14.55.11"
the closest i can find to this version is Cingular!
http://www.androidruu.com/getdownlo....55.01_18.21.95.55L_release_310178_signed.exe
version is 2.14.55.01
the Telus one version is 1.09.55.17
I'm guessing the Cingular would be best??
thanks
Click to expand...
Click to collapse
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
superbay said:
Well it should say the exact same radio version if you dont want to meet any problem. Can you search for the one as same as yours?
Or if you need further detail about the version, you can type 'fastboot getvar version-main' in the adb
Click to expand...
Click to collapse
Well nothing is working.
I guess my device is a paperweight even if I can get into recovery.
Can't flash anything, not even the RUU, can't sideload........nothing.
Tried Hassoon's instructions for the RUU but it won't reconise that a device is attached to go into Bootlaoder, sideloading ALWAYS fails at 22%. Others seem to overcome this but I cannot. It's frustrating reading how many problems are solved when nothing works for me.
I would like to know how to upgrade to a new ROM (Lollipop or better) on my Verizon HTC One Max with the option to return to stock. Software Information: 4.4.2, Sense 6.0, 3.09.605.3, 6.20, 4.60_002, 15432, 5
I was told to use (and did) Sunshine and then downloaded SuperSU from Google Store (per very detailed instructions and was told to not choose TWRP when the question popped up to choose one or the other (common/normal?)).
My phone is now UNLOCK and S-OFF as well as Rooted (but I'm having a lot of problems with blank screens, etc. and even had the black screen with the red ! in a red triangle (and I don’t know how I got it to boot up again (pushed pwr buttons, vol +/-, etc.)). However, that is as far as I’ve gotten. Confused am I.
I don’t know how to flash; however, I’ve been trying to figure it out, but I’m lost.
I’ve downloaded a lot of files from other threads, but the instructions, while detailed, didn’t say HOW to flash or add TWRP where I (a NEWBORN NEWBIE/NOOBIE) could understand, etc. Is there a place where all this is together?
Am I out of luck or would someone PLEASE help me fix and upgrade it with the option to return to stock if needed? I would love to have Sense 7.0, if possible. I apologize for such a long post/thread.
THANK YOU SO VERY MUCH!!!!!
P. S. My phone is now Prepaid Verizon (was Postpaid). Don't know if that matters. I have pics of the files I downloaded from one of your great guys, but they are on my computer. Not sure how to upload. I AM GLAD THAT I FOUND YOUR SITE!!!!!
@LoveSpock I am going to make this short and simple...
First off the Verizon Max software only goes up to 4.4.2. If you want to upgrade you'll need a custom rom which is why you S-OFF and unlocked...
You will need to get familiar with fastboot commands. Google is your friend on how to use if you don't know how to. Here is the link to the TWRP image for your device. http://flyhalf205.com/recoveries/openrecovery-twrp-2.8.7.1-t6univ.img Once you get fastboot setup you will type in the command fastboot flash recovery openrecovery-twrp-2.8.7.1-t6univ.img Make sure you have everything in the same directory when executing the command.
From there you are free to wipe then flash anything you would like. Wiping will delete your data so text, contacts that are stored on local phone(not sim or google) will be deleted.
@Flyhalf205
Thank you for your response and instructions. Does this mean I don't need to do anything to the SUPERSU that is already on the phone (and what it did)?.... Following your instructions will wipe everything?
I'll definitely need to take out my sd card. I've saved a ton of stuff on it. ...and backup my contacts and text messages.
I have some more googling and try to learn what you wrote for me to learn. I'll also have to find out what ROM to use....
Your Padawan thanks you.
LoveSpock said:
@Flyhalf205
Thank you for your response and instructions. Does this mean I don't need to do anything to the SUPERSU that is already on the phone (and what it did)?.... Following your instructions will wipe everything?
I'll definitely need to take out my sd card. I've saved a ton of stuff on it. ...and backup my contacts and text messages.
I have some more googling and try to learn what you wrote for me to learn. I'll also have to find out what ROM to use....
Your Padawan thanks you.
Click to expand...
Click to collapse
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
If you use twrp no need to take your SD card out just go to setting and unchecked SD card and like lovespoke said make sure to dl the right file you can dl right fastboot files here on xda just search it
Hey! Don't mean to hijack the thread but I'm in the same boat. I've never rooted and I'm looking to root my Verizon HTC one max. I'd also like to maybe install a custom Rom but I'm a noob so I'm not quite sure what I'm doing. Ok so it's my understanding that sunshine will root, s-off, AND unlock my boot loader? Btw I have no idea what those terms mean. Anyway, if someone could please confirm that about sunshine, it would really help me out. I've already downloaded and installed sunshine on my phone but I haven't paid the $25 yet.
Xx Moe, I strongly suggest you READ the various threads on XDA about unlocking bootloaders, gaining S-OFF and rooting. You can easily brick a device and there's much less support for the Max now than there was when it came out more than two years ago.
I don't believe Verizon HTC One Max's can be rooted without unlocking bootloader/gaining S-OFF and the exclusive method for that is Sunshine (unless you know someone with a Java card). Once you're bootloader unlocked and S-OFF, you can then "flash" any partition on the device and that's how to brick the device.
Once you are bootloader unlocked and S-OFF, you start by flashing a 'recovery', which is usually the latest version of TWRP for the HTC One Max. Don't flash a recovery for a different device. (Google "Team Win Recovery Project"). Once you have a custom recovery you can "wipe" your device and flash a new ROM.
Wiping deletes all data, or some data, depending upon how you wipe, and there are not very many Verizon HTC One Max ROMs out there that are fully functional. Check the threads, one sticky thread has a listing of ROMs.
Finally, I don't believe anyone has gotten Marshmallow going on a Max, so expect the "best" you'll be able to do is a Lollipop ROM or a Cyanogen Mod equivalent.
Awesome! Thanks for the super quick reply. So yes, sunshine will s-off and unlock boot loader. That seemed to be the million dollar question since (like you said) the one max doesn't have very much support anymore. I'm definitely going to keep reading the forums because I don't want to brick my phone. I've also been watching some tutorials on YouTube. Everything (so far) seems pretty straight forward now, but you can never be too careful. Thanks for your help hgoldner!
Flyhalf205 said:
@LoveSpock I am going to make this short and simple...
First off the Verizon Max software only goes up to 4.4.2. If you want to upgrade you'll need a custom rom which is why you S-OFF and unlocked...
You will need to get familiar with fastboot commands. Google is your friend on how to use if you don't know how to. Here is the link to the TWRP image for your device. http://flyhalf205.com/recoveries/openrecovery-twrp-2.8.7.1-t6univ.img Once you get fastboot setup you will type in the command fastboot flash recovery openrecovery-twrp-2.8.7.1-t6univ.img Make sure you have everything in the same directory when executing the command.
From there you are free to wipe then flash anything you would like. Wiping will delete your data so text, contacts that are stored on local phone(not sim or google) will be deleted.
Click to expand...
Click to collapse
Hey flyhalf, is there a thread on here on how to learn about adb fastboot, and flash the custom recovery for noobs? I cant seem to find it. I'm trying to install a custom rom on my htc one max but this is my first time ever rooting/unlocking an android. Ive searched the site but i cant find a tutorial on how to install the custom recovery or learn about adb yet. I have sunshine already on my phone but i havent used it yet because i want to know exactly what im doing before i pay the $25. Any help is appreciated. I already know how to get into the bootloader by pressing the power and volume down buttom at the same time while the phone is turned off.
Xx MOE said:
Hey flyhalf, is there a thread on here on how to learn about adb fastboot, and flash the custom recovery for noobs? I cant seem to find it. I'm trying to install a custom rom on my htc one max but this is my first time ever rooting/unlocking an android. Ive searched the site but i cant find a tutorial on how to install the custom recovery or learn about adb yet. I have sunshine already on my phone but i havent used it yet because i want to know exactly what im doing before i pay the $25. Any help is appreciated. I already know how to get into the bootloader by pressing the power and volume down buttom at the same time while the phone is turned off.
Click to expand...
Click to collapse
I'm heading to bed now. If I get time tomorrow I'll try to explain. If not we can setup team viewer and I can just set your computer up for you.
Sent from my Nexus 9 using Tapatalk
Flyhalf205 said:
I'm heading to bed now. If I get time tomorrow I'll try to explain. If not we can setup team viewer and I can just set your computer up for you.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
That would be awesome, but i think i found something from google. https://twrp.me/devices/htconemaxverizon.html
I downloaded the sdk and corresponding java that the site recommended. I attached a screenshot of my pc to show where im at in that process.
Xx MOE said:
That would be awesome, but i think i found something from google. https://twrp.me/devices/htconemaxverizon.html
I downloaded the sdk and corresponding java that the site recommended. I attached a screenshot of my pc to show where im at in that process.
Click to expand...
Click to collapse
I also downloaded the android-sdk_r24.4.1-windows.zip file but i moved it out of my downloads file, so it didn't show up on my screenshot
Xx MOE said:
I also downloaded the android-sdk_r24.4.1-windows.zip file but i moved it out of my downloads file, so it didn't show up on my screenshot
Click to expand...
Click to collapse
Download the platform tools and the android usb driver. Don't need anything else.
But basically if your s-off yet. Boot into HBOOT. Power off phone and hold down both power button and the volume down button. Select fastboot using the power button. Your computer should hopefully automatically pick up drivers and call the device "My HTC" in the device manager. If not you'll need to go in and manually assign the downloaded driver using the link above to the Android device in device manager.
Download twrp image file into the same directory as the platform tools downloaded to. In windows, right click while holding down shift anywhere on the white blank area in platform tools and click on "open command window here".. From there you will type in the command fastboot flash recovery recoveryFileName.img
If it says waiting for device. Check device manager and make sure the driver is installed right.
Flyhalf205 said:
Download the platform tools and the android usb driver. Don't need anything else.
But basically if your s-off yet. Boot into HBOOT. Power off phone and hold down both power button and the volume down button. Select fastboot using the power button. Your computer should hopefully automatically pick up drivers and call the device "My HTC" in the device manager. If not you'll need to go in and manually assign the downloaded driver using the link above to the Android device in device manager.
Download twrp image file into the same directory as the platform tools downloaded to. In windows, right click while holding down shift anywhere on the white blank area in platform tools and click on "open command window here".. From there you will type in the command fastboot flash recovery recoveryFileName.img
If it says waiting for device. Check device manager and make sure the driver is installed right.
Click to expand...
Click to collapse
Ok, so if im doing this correctly, the twrp img should be in the platform tools folder and my computer should recognize my phone as "my htc" as shown in my attached screenshot...
Xx MOE said:
Ok, so if im doing this correctly, the twrp img should be in the platform tools folder and my computer should recognize my phone as "my htc" as shown in my attached screenshot...
Click to expand...
Click to collapse
Yes. That is correct so far.
Flyhalf205 said:
Yes. That is correct so far.
Click to expand...
Click to collapse
Perfect! Thank you so much! now all i have to do is use sunshine to s-off/unlock bootloader and follow this thread: http://forum.xda-developers.com/showthread.php?t=2498746 to install custom recovery and i should now be able to flash custom roms! Thanks for your help! A donation will be coming your way soon! :good::good::good::highfive:
Almost Ready....
Flyhalf205 said:
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
Click to expand...
Click to collapse
I've been out of commission... Sorry about the long wait.
I'm sure you've been very busy.
I found the fastboot.exe file and placed it and your twrp file into a folder on my desktop. Before I run fastboot and add your twrp img file, what would the next step be? .... I don't have have a ROM yet to add to the phone. Should I have that first? Would you please direct me to the right one for me? I noted in one of your replies to another member that there isn't a Marshmallow one, yet.
Do I need the ADB file?
Thank you,
Your Padawan.
Flyhalf205 said:
Yes. That is correct so far.
Click to expand...
Click to collapse
Would you recommend uninstalling the HTC program that automatically picks up the phone?
LoveSpock said:
I've been out of commission... Sorry about the long wait.
I'm sure you've been very busy.
I found the fastboot.exe file and placed it and your twrp file into a folder on my desktop. Before I run fastboot and add your twrp img file, what would the next step be? .... I don't have have a ROM yet to add to the phone. Should I have that first? Would you please direct me to the right one for me? I noted in one of your replies to another member that there isn't a Marshmallow one, yet.
Do I need the ADB file?
Thank you,
Your Padawan.
Click to expand...
Click to collapse
I forget if you were s-off or s-on but you will need to be s-off or your bootloader will need to be unlocked.. You don't need a rom just yet. You could flash recovery and flash root for starters. But once you get it flashed we can start on what to do next.
Update...
Flyhalf205 said:
Shouldn't worry about supersu. Most custom ROMs are going to have that prebuilt into it. Once you get TWRP we will go further into detail about how stuff works.
Click to expand...
Click to collapse
Flyhalf205 said:
I forget if you were s-off or s-on but you will need to be s-off or your bootloader will need to be unlocked.. You don't need a rom just yet. You could flash recovery and flash root for starters. But once you get it flashed we can start on what to do next.
Click to expand...
Click to collapse
Sorry... I started the thread back in January. I've been out of commission and starting over.
I had used Sunshine to S-off and Unlock. I used SU to root. I knew nothing about flashing or fastboot and am still learning. One of your original responses to my original post said that google was my friend, so I googled per your advice and found some information on fastboot.
I don't know what flash root means in your response above.
You had also gave me the link to the TWRP image for my phone. You also wrote "Make sure you have everything in the same directory when executing the command." I've added 2 of the pics again as well as one of your img file in the directory I created when I loaded Android Studio.
The Android Studio I downloaded is the latest. Does that make a difference? I did find info on this site about a minimal adb and fastboot. Would that have been better?
I'm imagining my phone will be out of commission until the new ROM is installed, right? (See how I'm still such a Newbie/Noobie!)
Thank you!
Your Padawan