Related
hi
i have problem in my wifi
i trued to flash Rogers rom by fastboot and when its start its flashed the boot.img and recovery.img only and stop to flash the system.img
after that my WIFI starting give me error and i cant swith it on
so please any one can upload the boot.img for AT&T version so i can able to reflash it again
is that how its called? boot.img?
i can't seem to find such a file (in root explorer)
do you know where can i find it?
Here you go...
I extracted these from the PG09IMG_Puccini_LTE_Cingular_US_1.17.502.3_Radio_1.04.550I.15v2_30.60.550I.10_release_210183_signed ROM file... hope it helps.
boot.img
wifi_htc_bcmMFG248_ag_tx_rx_swap.img
yes you can use it from footballs topic. or the puccini leak topic. extract from the zip file. btw. I cannot flash that whole zip anyhow.
Thanks i have done from the boot. mg from PG09IMG_Puccini_LTE_Cingular_US
I dont know why we cannot download an official RUU for ATT devices. WHY? it will makes thing easier. If your device went wrong, you can easily flash it back to factory state.
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
cx5 said:
Hi, I got this wifi error now,
Is the solution and correct conditions and commend as described in below steps: -
boot into fastboot
connnect USB and it shows the USB word behind fastboot.
then from dos prompt enter commend
fastboot flash wifi_htc_bcmMFG248_ag_tx_rx_swap.img
done?
end?
Thanks.
Click to expand...
Click to collapse
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Thanks finniest, I have performed…Fastboot flash boot boot_signed.img
And solved temporarily. Got wifi not to say error. Allows me to turn on, but then immediately shuts off and display error again.
On another note, i also relocked bootloader. Run RUU, but error 155, means I can't restock.
Currently has TWRP, root, SU, all OK. Able to change custom rom anytime. But wifi error. CWrecovery flashed doomlord's wifi fix but not working.
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Sent from my GT-P1000 using xda app-developers app
cx5 said:
The wifi.img hasn't been tried yet. feels strange to flash wifi.img going into the boot partition. Am I just being paranoia?
Click to expand...
Click to collapse
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
It is good to know that you are familiar with unlocking bootloaders and have a custom recovery. That gives us a lot more options to solve this.
As far as I know the wifi module paired with the kernel by DooMLoRD is incompatible with all other kernels. So if you aren't using that kernel then you will have to use whatever bcm4329.ko file is included with the ROM that you are using. It is easy to forget that his custom wifi module is still in your /system/lib/modules directory when you flash a new kernel.
I suggest trying El-Diablo ROM and the boot.img that comes with it. This is a known working kernel and ROM pair. If you install them then first make certain to format /boot, /system and /data in whatever ways TWRP allows you to.
You should also consider that there might be something wrong with your wifi hardware. This is most likely if you have gotten your tablet wet and/or dropped it.
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
finniest said:
I would give it a try. Beyond wasting five minutes of your time I don't see a downside. You can always flash another /boot image if it doesn't work.
Click to expand...
Click to collapse
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Where to read step by step?
cx5 said:
Hi finniest, you're right about not loosing too much time, I will give it a try now, and if it doesn't work, god bless it's OK I will read up more here, do more homework, then ask again, hahahah. Thanks !!!!!!!
Done, but not because I dare the above.
After realizing kernel + wifi (must be paired), knowing I am no OSIMOND's lightest rom, then I went back to CAREFULLY read his instructions specifically asking for doomlord's kernel v1 then flash the wifi correction ZIP via CWM. Hence I FASTBOOT FLASH BOOT kernelname.img then CWM recovery flash doomlord's wifi ZIP correction, then done. All my own fault for not reading carefully. Thanks still finniest and so many others who replied to various thread.
Click to expand...
Click to collapse
---
Kernel (ZIP) or Kernel as an Kernel Folder (organized like Linux kernel release 2.6.xx). I do not know how to use this last one
BTW, I am stuck whit my WiFi since a few weeks... Accidentally I wiped the System(Original) and other stuff, and happily installed the Diablo Version make my Jetstream to come alive. but never never can make the wifi work again.
I read a lot of Android and lear a bit about it, but I can't find the way to make WiFi works again. So Please... A jetstream whitout WiFi is like a die tablet... I need some help.
I need those links where they say how to, and the link to dowload IMG or ZIP. or a page teaching step by step how to install this Kernel (Organized like folders in a Linux like). thank in advance.
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
It said FAIL...
guru_shastri said:
try downloading this:
https://dl.dropboxusercontent.com/u/5952907/Stock_wifi_modules.zip
and flash it thru the recovery
Click to expand...
Click to collapse
Thanks for Helping.
I reboot into recovery using TWRP and tried to install it from Install Options. it said [FAIL]
Surely I'm just learnig about Android, I should use a commad from bootloader like this?
<fastboot flash recovery Stock_wifi_modules.zip> or
<fastboot flash boot Stock_wifi_modules.zip>
or something like this?
or perhaps use another tool instead TWRP...
flashing thru recovery should have worked. maybe the file is corrupted, I can't really tell
I downloaded and visually inspected the contents of the archive that @guru_shastri provided and everything looks okay. If you want to revert to revert to the stock WiFi module then this appears to be what you need.
Be aware that I have frequently witnessed instances where transfers to internal_sdcard via USB mount caused the file(s) to be corrupted. You should verify that a transfer worked by using MD5, cmp or (at least) a visual inspection.
WiFI OK!, SIM, not!
finniest said:
When using fastboot flash you have to specify a partition to flash, so that command will not work. The correct command is:
Code:
fastboot flash boot wifi_htc_bcmMFG248_ag_tx_rx_swap.img
I am not guaranteeing that it will solve your problem, only that it will actually flash your boot partition. The best outcome is that it fixes your problem. The worst outcome is that your tablet will no longer boot due to mismatched /boot and /system partitions.
If the latter occurs then I recommend that you install a custom ROM. Let us know if it comes to that and someone will guide you.
Don't forget to backup what you have on the tablet before you do anything.
Click to expand...
Click to collapse
Finally.. WiFI Works!... but not exactly with described... I had to read pretty much about all the things that concerns to adb/bootloader/flashing/installig>img>zip/ partition of each thing and so on before being succesfull with WiFi...
Not totally Sure, but the process that worked was:
WIPE all but recovery (using TWRP toosl)...
INSTALL el Diablo (zip) ROM Posted into the forums...(do not reboot)
INSTALL Stock_wifi_modules.zip
reboot into system...
Using USB debbuging reboot into bootloader.
Flash boot_signed.img >[fastboot flash root boot_signed.img]
(in this point the prompt said <waiting for device>, so I reboot into bootloader using Volume and Power buttons...)
Once flashed, reboot...
Now WiFi is working. Happily!
----
BTW... My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
I mean, the Sim Card appear to be reconigzed bye the system, but I don't get signal from the Phone Network (Like if it was from an unreconized carrier.. and my phone is Unlocked). I tried the sim in other phones and works well. What Can I Do at this point?
----- Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Adolyep said:
My SIM is not reconigzed (why???)... I saw it working the first time I istalled "El Diablo", but now... nothing happens.
Click to expand...
Click to collapse
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
Adolyep said:
Soon I gonna move to another country, where I gonna use another SIM, with another carrier... --- Will the SIM work??
Click to expand...
Click to collapse
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Silly me! I did not realize look at this!
finniest said:
Are you sure that you are carrier unlocked and not just bootloader unlocked? The former involves submitting your IMEI and paying a small sum of money, so it is usually easy to remember. They are completely different animals.
Make sure that you have checked Wireless & networks-->Mobile network [x]. If it is enabled then check Mobile networks for information. The SIM Toolkit app can also be a source of information.
Strangely, the lock screen is a source of information for your SIM card, so make sure you have it enabled. It is the only gateway (that I am aware of) to submitting your unlock code.
If your Jetstream is carrier unlocked then probably. The answer is probably because the Jetstream radio does not support every provider available.
Click to expand...
Click to collapse
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Adolyep said:
I just read your answer y I realized that I should carried out this simple step. look for networks in the area. This command "activate" the SIM to perform usual commands like Call or sending codes with * or # and numbers.
At this point my Jetstream is pretty much like it eas before wiping the system. but I can not fix the issue: <<Connection Problem or Invalid MMI Code>> every time that I send an command code (*111#) that is the network commad to access a few services. To perform those commads I have to take the SIM CARD and install it in another phone, Perform the network command, and return the SIM to my JETSTREAM. it is annoying. (but works)
Why in this world the network commands can not be performed by the Jetstream! (any advice?)
Click to expand...
Click to collapse
You will need to enable the MMI Code setting in the build.prop using root explorer. Without that MMI Codes do not work.
Hi all,
I've searched high and low for the answer to this before posting, so I apologize in advance if I simply couldn't find it.
In trying to flash a ROM I managed to seriously mess myself up by wiping literally everything off my phone- my nandroids, my ROM file, everything. I'm running CWM v6.0.2.7 and trying to use adb sideload <rom>, but I keep getting the error "failed to write data 'protocol' no status". I've searched for that specific error and haven't found much about it that was able to help me. I get this message using Hasoon's amazing toolkit or by doing the sideload manually via the command prompt.
Any ideas? My phone's a pretty brick right now, which is entirely my fault- I just hope someone can help me out of this mess I got myself into!
Thank you so much in advance!
[EDIT]
I resolved the issue by switching from CWM and moving to TWRP and tried the sideload a few more times. I would often get the message that my device wasn't connected, but with some patience I got it to work. Good luck to anyone else who encounters this issue!
aladara said:
Hi all,
I've searched high and low for the answer to this before posting, so I apologize in advance if I simply couldn't find it.
In trying to flash a ROM I managed to seriously mess myself up by wiping literally everything off my phone- my nandroids, my ROM file, everything. I'm running CWM v6.0.2.7 and trying to use adb sideload <rom>, but I keep getting the error "failed to write data 'protocol' no status". I've searched for that specific error and haven't found much about it that was able to help me. I get this message using Hasoon's amazing toolkit or by doing the sideload manually via the command prompt.
Any ideas? My phone's a pretty brick right now, which is entirely my fault- I just hope someone can help me out of this mess I got myself into!
Thank you so much in advance!
Click to expand...
Click to collapse
you need to put the phone INTO sideload mode
Lloir said:
you need to put the phone INTO sideload mode
Click to expand...
Click to collapse
I have done that through the recovery and left it on that screen, that is when the errors pop up.
I know i'm a little late, but just in case somebody else goes looking for help on this.
I was stuck and kept getting the same error. everything was up to date and i was in ADB Sideload. Turns out after I wiped everything I never rebooted my phone. I rebooted back into recovery and it gave me the option to install SuperSu and root my phone (although it was previously rooted). Once I did that I was able to go back into ADB sideload and all worked well! Hope this helps somebody out there.
lebnan60 said:
I know i'm a little late, but just in case somebody else goes looking for help on this.
I was stuck and kept getting the same error. everything was up to date and i was in ADB Sideload. Turns out after I wiped everything I never rebooted my phone. I rebooted back into recovery and it gave me the option to install SuperSu and root my phone (although it was previously rooted). Once I did that I was able to go back into ADB sideload and all worked well! Hope this helps somebody out there.
Click to expand...
Click to collapse
But what if you have no rom on your phone ?
cyberusman said:
But what if you have no rom on your phone ?
Click to expand...
Click to collapse
The sideload command is used WHEN you have no rom on your SDcard/phone. If you can boot into your phone (access home screen) you can just activate USB Debugging and connect to PC and just move files normally.
The Sideload protocol is used when you can't access your home screen (When you are in a bootloop) and all you can access is the Recovery. So you activate Sideload from the recovery and on your PC you use adb sideload "rom file" without the quotes and then the ROM installs directly from your computer storage.
There is also a feature in ADB called adb push, you literally push the file to your phone SDCard, its like you copy and paste a file. But since i never used it i don't know if you do it while in the bootloader or recovery or not. But I think you can.
I know this is quite some time later, but I was wiping my Nexus 7 to sell. Tried the TWRP Sideload feature and could sideload a ROM...great! So wiped the entire device clean and attempted sideload....failed! Wasn't a good feeling at all...so looked around and found this tidbit of info. Rebooted (to recovery), prompted for Root, accepted, and then sideload worked perfectly.
Of note, I couldn't sideload the gapps right afterwards, so had to reboot into Recovery again to re initiate Sideload, and got gapps installed too.
Thanks for the tip!
lebnan60 said:
I know i'm a little late, but just in case somebody else goes looking for help on this.
I was stuck and kept getting the same error. everything was up to date and i was in ADB Sideload. Turns out after I wiped everything I never rebooted my phone. I rebooted back into recovery and it gave me the option to install SuperSu and root my phone (although it was previously rooted). Once I did that I was able to go back into ADB sideload and all worked well! Hope this helps somebody out there.
Click to expand...
Click to collapse
Glad it helped! I've been meaning to post an update, also. I've run into the issue where the newest version of TWRP doesn't re-root the device as mentioned initially. I've been using a beta version of TWRP needed for some of the newer Kit Kit roms and had to flash an older version of TWRP to get ADB Sideload working again.
Basically I would flash an older version of TWRP, re-boot (and it would ask to root the device) ADB Sideload an older rom, such as CM 10.1 or another Jellybean rom and from there you can boot up the system and make any changes needed.
Sadly I keep wiping my phone clean and running into these issues. Hopefully I've learned my lesson
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Update: I've finally figured out how to get the TWRP recovery booted. Now working on trying to get my phone to boot up an OS of some sort. Very slowly but surely.
bullmurf said:
Phone: ATT HTC One X +
Hi everyone,
This problem has been beat to death on this site but it's very hard to follow with other phones and trying to find the files and everything needed to fix it. This is my first time to try and root a phone so I tried to piece it together and screwed it up. Still trying to learn.
So far I successfully unlocked the bootloader through the HTCDEV site so I have SDK with fastboot and adb. I found OneXRoot but it just said "waiting for device". So, I found RootBoot-1.14.206.16-O2, ran it from the file I downloaded it to and not the fastboot/adb location (might have been the problem) and it said "waiting for device" so I unplugged my phone and plugged it back in. It was supposed to restart my phone 3 times and root my phone through magic but instead it restarted once and only goes to HTC white screen.
I've looked all through for a solution and the best thing I've come across was this link http://forum.xda-developers.com/showthread.php?p=30863908 . I was going to try this but I don't know my CID and my phone doesn't boot to figure it out. Am I headed in the right direction?
My goal here was to root the phone to get rid of HTC Sense. I'm thinking I should flash the boot.img or do the kernal thing. Not sure though it's very confusing. Right now I need to get it to boot so I can try the root again (the correct way, whatever that might be). Any help would be very appreciated, my phone is a paper weight right now.
http://teamw.in/project/twrp2/131 downloaded the recovery image here and going to try that. It says the batter is too low now so i'm guessing it will work after the battery is recharged. That's direction I am taking atm.
Click to expand...
Click to collapse
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Addicted2xda said:
Press the power down button while turning on your device to see if you can get to boot loader - this will give you the basic information about your device.
Use the original RUU from the following post to flash your device in bootloader mode (I think it should work...):
http://forum.xda-developers.com/showthread.php?t=2140442
Use this to unlock your bootloader / root your device / blah blah blah. Too many people have succeeded in rooting / unlocking their device through this. So, there is a good chance that you will too...
http://forum.xda-developers.com/showthread.php?t=1994961
Click to expand...
Click to collapse
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
bullmurf said:
OK it looks like the OS was wiped before it was backed up with a rom folder to use after rooting. Now I have no OS so I can't get to files to put on a ROM or do much of anything. It's not booting past the HTC screen because there is no OS now ^^. I have no idea what to do about that. Going to try to figure out how to put a new OS on there. Any help would be appreciated.
Click to expand...
Click to collapse
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Addicted2xda said:
If your device is locked - you can get the current RUU of your specific device from the post I have mentioned.
BTW what is your hboot version?
If your device is unlocked - install TWRP using hasoon's toolkit and then use sideload to copy / install a custom ROM...
Click to expand...
Click to collapse
"use sideload to copy / install a custom ROM..." OK I don't know anything about this but it will point me in the right direction. I have the phone unlocked. The HBOOT version is 1.40.0000. I'll see if I can do what you suggested, thanks.
Update: Atempting an adb sideload using TWRP which seems to be the only option for me.
ADB Sideload
What is ADB sideload?
--------------------------------------------------------------------------------
ADB sideload is a new feature that was added to AOSP recovery in Jelly Bean. As of version 2.3, TWRP now supports ADB sideload mode. ADB sideload is a different ADB mode that you can use to push and install a zip using one command from your computer. Most likely ADB sideload won't be very useful for your average recovery user, but ADB sideload can be a huge time-saver for a ROM developer.
How do I use ADB sideload?
--------------------------------------------------------------------------------
1.Have a recovery installed on your device that supports ADB sideload like TWRP 2.3 or higher
2.Have newer ADB binaries installed on your computer. If it's been a while since you installed ADB on your computer, you may need to get the latest ADB binaries in platform-tools from the Android SDK. You will need version 1.0.29 or higher. You can find your current version by typing "adb version" at the command line.
3.Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
4.From the command line, type adb sideload /path/to/rom.zip
The file will be copied to your device to whatever the current storage location is that you have selected in the mount page. It will always be placed in the root of that storage location and named sideload.zip (e.g. /sdcard/sideload.zip) and it will automatically delete / overwrite any existing sideload.zip you may have on your device. As soon as the file is copied to your device, it will automatically be installed. When the install is finished you will be presented with a reboot system button so that you can reboot to test your zip.
Note that sideload mode is a separate ADB mode. While in sideload mode, regular ADB commands will not work. Once the zip has been copied to the device and the install starts (or if you hit the cancel button) regular ADB mode will resume.
Click to expand...
Click to collapse
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
bullmurf said:
I can't link on this board yet so I quoted the sideloading instructions for a .zip from the TWRP website. I have the latest version of SDK and when I try to sideload it gives me a list of commands in the command prompt. I looked through them and didn't see sideload as a command. What's the easiest way to sideload this zip so I can install it in TWRP to get my phone booted? I know you can do "adb install \path.apk) but I don't have an rom in .apk format, only zip.
Click to expand...
Click to collapse
Update: after trying the same thing 100 times it decided to send "sideload". command line was adb sideload name.zip. Installing Viper ROM for HOX+ atm. I'll see if it fixes all of my problems. Thanks for all of the help to this point. I'll type up a guide of what went wrong with my root and how we managed to get it fixed.
Update: Phone is booting to HTC white screen and then shutting off. Now trying to figure that one one out.
Update" Phone is booting to HTC white screen now and staying there. In TWRP under reboot is says "no os installed, do you still wish to reboot". Still digging in the forums to figure this one out and how to fix it. I installed the Viper ROM fine but when it asked to reboot now it just rebooted to HTC white screen. Missing something here? The phone is S-ON, does that make a difference in using the TWRP?
Is there an RUU exe file I can run from my computer? I relocked the phone but the links you gave me are for installing the ap through google play. Not sure how you do that with a phone that wont boot past htc screen.
Update: I've found an RUU application from these boards that is supposed to work for HOX+ so i'm downloading it. It really is taking forever to find the information I need along the way from this board but it's here....somewhere...I think...Will keep plugging away but feel free to throw me a bone ever once in a while! =)
Update: The version that worked for others isn't the same version I have. Going to dig again for 1.19.502.1 version.
Update: Found the version in the last place I thought it would be...HTC website...Downloading it and just hoping its and application I can run on my computer.
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
I would suggest you to use hasoon's all in one toolkit
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
bullmurf said:
I went with another Rom. Honestly I tried the toolkit and ity worried fine at first but later it wouldn't work for me. After doing this for two straight days I learned to do it the hard way. New Rom is great. trying to explore my new freedoms now. I really want to change my lock screen.
Click to expand...
Click to collapse
There is a great lockscreen called CLocker
Addicted2xda said:
There is a great lockscreen called CLocker
Click to expand...
Click to collapse
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
bullmurf said:
looking for it now. Trying to figure out how to replace the ring one from HTC. Is that possible? Probably in the boards somewhere
Click to expand...
Click to collapse
You will find it in the playstore itself
You need to set lockscreen to None
Addicted2xda said:
You will find it in the playstore itself
You need to set lockscreen to None
Click to expand...
Click to collapse
Thanks again man. I got it and the ring is gone \0/ Phone looks freakin amazing now with that lock screen and Elegancia rom. Glad you stopped by to help :good: Still learning my way around the forums and my rooted phone. It's great to not be stressed about bricking it ^^
suppils soars
bullmurf said:
Problem Fixed:
Problem: While trying to root phone I didn't back it up. Unlock was successful but root was not. OS was lost and phone would not boot past HTC white screen.
Solution: Relocked phone using fastboot oem relock. Downloaded manual ROM installation of the same version and intalled it while phone plugged in.
Thanks for the help in pointing me in the right direction. Now to try and root it again to install viper. If it screws up I know how to get back :laugh:
Click to expand...
Click to collapse
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
mrmagoogt said:
Hi there, I'm a noob and got the same problem, by mistake I formatted the system folder of my phone, now I'm stuck in the white HTC screen too, could you please post the links for the tools you used to bring the phone back to life? some instructions would be great to, thanks in advance...
Click to expand...
Click to collapse
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Addicted2xda said:
If you have installed TWRP - go to hasoon's thread, download the toolkit and use the function adb sideload to copy a rom your choice.
Flash the ROM using TWRP. Flash the kernel from hasoon's toolkit.
Click to expand...
Click to collapse
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
mrmagoogt said:
Thanks, phone is rooted but has CWM v6.0.2.7 installed, however, I can see the "install zip from sideload" option, when I choose this option it says "Now send the package you want to apply to the device with "adb sideload <filename>"", I don't know how to do that...
Click to expand...
Click to collapse
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Addicted2xda said:
Flash TWRP man!
If you just browse through the forum - you will see that CWM is discouraged....
Click to expand...
Click to collapse
Thanks, I used a script to charge my battery, relock bootloader and installed ruu file to get back to stock, rooted again using Hasoon2000's all in one kit...
Hi guys, over the past few weeks, I have noticed that many people are having problems rooting their Jetstreams. So because of this, I thought I would put together an all in one guide to help alleviate everyone's problems.
So what this will show you how to do:
Unlock the bootloader
Flash a custom recovery
Grant root access
Prepare the device for S-OFF
Included files:
HTC Drivers
ADB
Fastboot
TWRP 2.4.1.0
SuperSU 1.51
Note: This guide is for windows only
Ok, so lets begin:
Download attached zip
http://www.mediafire.com/download/ao1ykdpx5jn2uni/Root_HTC_Jetstream.zip
Extract the zip to an appropriate place on your computer
Install the HTC drivers
Do so by double clicking the HTCDriver_4.2.0.001.exe from the zip
Run the RUU if needed
I am assuming you are on a completely stock HTC Jetstream with no modifications what so ever. I am also assuming you are on the latest software 1.30.502.1 for AT&T users or 1.26.631.4 for Rodgers users. If you are not, please download and run the latest RUU from the following website:
http://forum.xda-developers.com/showthread.php?t=2094375
Please note that running the RUU will completely WIPE your device of all personal data, so backup accordingly
To run the RUU, make sure the Jetstream is turned on and is fully booted into Android
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Simply attach the Jetstream to your computer with the appropriate USB cord
Double click on the downloaded RUU .exe file to run the program
If for some reason you cannot boot into Android, you can do the following:
With the device turned off, hold the volume down button and simple press the power button for a second or two
The device will boot into the bootloader, from there use the volume buttons to navigate to fastboot and the power button to select
Once in fastboot, connect the device to the computer with the USB cord and then double click the downloaded RUU .exe
Now lets unlock the bootloader
Please note that unlocking the bootloader will also WIPE your device
Go to http://www.htcdev.com/
Create an account if you do not already have one
Click on "Unlock Bootloader" and then "Get Started"
In the drop down box, select "HTC Jetstream"
Agree to all the legal terms
Follow all the instructions to obtain your unlock token
To easily do this:
Make sure "USB Debugging" is enabled under development settings
Make sure "Fastboot" is disabled under power settings
Connect the device to the computer with the USB cable
Navigate to the extracted folder of the attached zip
Hold the shift key and right click in the folder, then select "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following in the command window
Code:
fastboot oem get_identifier_token
Copy the appropriate text according to the website and submit it
You will then be emailed an "Unlock_code.bin" and a link to continue the unlock process
Download the "Unlock_code.bin" and place it in the extracted folder from earlier
Now type the following in the command window
Code:
fastboot flash unlocktoken Unlock_code.bin
On the device you will be prompted to unlock the device, use the volume keys to navigate to "Yes" and use power to select
The device will reboot back into Android
Now lets flash a custom recovery
Connect the device to the computer with the USB cable
In the extracted folder open a command window by holding the shift key, right clicking, and selecting "Open Command Window Here"
Type the following in the command window
Code:
adb reboot bootloader
Once the device has booted into fastboot, type the following into the command window
Code:
fastboot flash recovery htc_jetstream_twrp_recovery_2.4.1.0.img
Once the custom recovery has been successfully flashed, type the following into the command window
Code:
fastboot reboot
The device will then boot back into android
Now lets get root
Connect the device to the computer with the USB cable
Copy the "SuperSU-v1.51.zip' to the root of you SD card
Go to the extracted folder, hold the shift key, right click, and select "Open Command Window Here"
Now type the following into the command window
Code:
adb reboot recovery
While at the recovery main menu, select the wipe option and wipe cache and dalvik cache
Next go back to the main menu and select install
Navigate to the SuperSU zip we placed on the SD card and flash the zip
Once it flashes, go back to the main menu and reboot back into system
The device will boot back into Android and the device will now be rooted!
So what now?
After completing the step above, you device should have an unlocked bootloader, and custom recovery installed, and also have root access. After having all of this you may now go on to install any custom ROMs you may want, however, I would recommend obtaining S-OFF to give yourself full control over your device.
This following link should help to explain what S-OFF is exactly:
http://forum.xda-developers.com/showpost.php?p=42455824&postcount=1
This next link is to the JuopunutBear S-OFF method:
http://forum.xda-developers.com/showthread.php?t=1906353
People I would like to thank:
DoomLoRD - for his initial work with rooting the HTC Jetstream
jmz - for giving us a custom recovery and hosting all the RUUs for us
TeamWin - for TWRP
Chainfire - for his amazing work with Android and SuperSU
Fuses and the rest of Team Unlimited - for giving us an S-OFF method
Disclaimer:
Just to be clear, unlocking and rooting your HTC Jetstream voids your warranty, so anything you do to it is your decision and I am in no way responsible for anything that happens to your device
great work!
@DNarsingh
Windows 8 64 finally can ADB to Jetstream and Sensation XL.
Thanks for driver file HTCDriver_4.2.0.001.exe containing within the zip you attached. The driver within htc_sync_setup_3.3.10.exe couldn't seem to get through.
Did a factory reset on my jetstream, and lost root. When I used CWM for recovery, I tried re-rooting using the guide in this thread. After another factory reset, root was still there, so I handed the jetstream to its new owner. However, the new owner has told me that the pen icon doesn't show up when using the pen. He did another factory reset (which took longer than usual), but still nothing. Anyone know what went wrong?
Notontherugman said:
Did a factory reset on my jetstream, and lost root.
Click to expand...
Click to collapse
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
finniest said:
I've never heard of a factory reset breaking root. The components that enable root usually exist on the /system partition and it is untouched by a factory reset.
The other root method (that I am unfamiliar) with is an insecure kernel. I don't know how this works, but I am pretty sure that a factory reset should not break it.
Click to expand...
Click to collapse
I'm not a dev, and have just been following how-tos on XDA up to now (from back in the days of HTC HD2); therefore, I can't give details since I am inexperienced.
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Notontherugman said:
After the factory reset, Titanium Backup was denied SU, I could not browse the root directories/folders and all the software that needed root to work would not.
Click to expand...
Click to collapse
Did you try to install the superuser app that you were formerly using from the market? My guess is that you lost the /data/app/su.apk that manages superuser, but that the binary is still in your /system/xbin/su directory somewhere. You probably removed the seemingly redundant /system/app/su.apk while using Titanium Backup, but are now left without a copy of it.
Notontherugman said:
My question still stands: the pen icon won't show up. Anyone know what went wrong or what he may be doing wrong? In desperate need for help.
Click to expand...
Click to collapse
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
finniest said:
If you are using Hive ROM then the pen icon will not appear, but the pen will still work with most apps. If you are using a different ROM then I really have no idea why the pen icon is not working. Are you certain that the pen battery still has a charge?
Click to expand...
Click to collapse
Not using any ROMs.
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Now, after the factory reset and the root method above, he tried his Flyer's pen on the Jetstream as well, so the battery is not a problem.
Notontherugman said:
I had removed most of the bloatware when I was using it, but the pen icon was there and I could use it just fine (before the factory reset).
Click to expand...
Click to collapse
Try using logcat to diagnose the problem. I suspect something will show up during boot or when you press where the pen icon should be.
http://www.xda-developers.com/android/help-your-developers-pull-a-logcat-when-issues-arise
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Notontherugman said:
I got the Jetstream back today.
I had managed to make a backup before using Clockwork Mod.
After the above rooting method, CWM is gone, and I can't use the backup files to restore using TWRP.
The link for CWM is gone. This is becoming extremely frustrating.
Click to expand...
Click to collapse
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
DNarsingh said:
I have a copy of the CWM recovery.img. When I get home tonight, I will upload it for you.
I would recommend redoing your backup in TWRP afterward. In my experience, this recovery is a bit more up to date..
Click to expand...
Click to collapse
Definitely.
And thank you!
EDIT: found CWM on an old hard disk. Managed to get ADB working. Restoring should fix most of the problems.
Thanks very much for the post
Sent from my SGH- I317M (Note II) running CM 11 using XDA Mobile App
every thing is ok
my device is fully rooted with twrp recovery and unlocked bootloader
but I have a problem.
I have sim card signal Icon but my device can not confirm simcard
what can I do?
Thanks!
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
GROTEU said:
Since I have rooted my device I can no longer access downloads from the google play store. I constantly get RPC:S-7:AEC-0 or -7 errors. I have tried all the tricks on various
forums but have had no luck. Do you have any fixes related to the jetstream?
Thanks, Mike
Click to expand...
Click to collapse
It doesn't sound related to rooting. I would suggest a backup (there are many means of accomplishing this) and then a factory restore. If that doesn't work then install a custom ROM.
rooting issues
i have been trying to root my jetstream so i can get some lift out of it but when i get to the fast boot the system just hangs there any suggestions please if you know a complete way to root a htc from rogers i would love the support thanks
This is just a mirror to my original thread on superSU
Make sure you have adb installed either via the sdk or adb minimal
Here is a guide for anyone running android wear 6.0.1 on rooting
(from PC)
1.Unlock the bootloader if not already unlocked
(Make sure to boot to system and set up device after unlocking bootloader otherwise broken kernel! )
Code:
adb reboot bootloader
fastboot oem unlock
2.flash THIS TWRP onto the watch MAKE SURE TO USE THIS ONE!(current official cannot mount squashfs system)
Code:
fastboot flash recovery recoveryname.img
3.Download special SuperSU here with busybox YDS included HERE and move it to watch with adb push to /sdcard while TWRP is booted and then install as normal zip
Code:
adb push nameofzip.zip /sdcard/
4.Boot watch to system (ignore TWRP message of no OS installed) Now your root apps from 5.1 should work perfect
REMEMBER squashfs is read only even with root so don't bother trying to modify system files like the build.prop
If you would like to change pixel density perform this command in either adb shell or a terminal emulator:
Code:
wm density <dpi>
Please leave thanks if it helped!
New Update!
updated to superSU 2.79
reverted to previous busybox due to incompatibility
Xmaster24 said:
Feel free to submit links to twrp for squashfs watch with model name, codename and original developer's name
Will add them to this post
I DID NOT CREATE ANY OF THESE BUILDS!
LG G Watch dory(courtesy of @rbox): http://www.mediafire.com/download/apwtscp0tn0y8qd/twrp-3.0.0-0-dory+squashfs.img
Click to expand...
Click to collapse
I read in your other thread that you have your own version of TWRP? The 3.0.0.0 version I got from twrp.me doesn't seem to flash your supersu zip properly. Or at least I don't have a busybox app installed on my watch after flashing the zip.
b1g.p0ppa said:
I read in your other thread that you have your own version of TWRP? The 3.0.0.0 version I got from twrp.me doesn't seem to flash your supersu zip properly. Or at least I don't have a busybox app installed on my watch after flashing the zip.
Click to expand...
Click to collapse
yes see step 2 download the one from post below ie. the one you quoted. The one from twrp.me is outdated and cannot mount the system as it is squashfs. the one in that post can
oh sorry! the way it was situated in your post made me think it was a signature, so I didn't even read it. Thanks!
b1g.p0ppa said:
oh sorry! the way it was situated in your post made me think it was a signature, so I didn't even read it. Thanks!
Click to expand...
Click to collapse
Yes thanks for pointing that out, I have made it more obvious now.
Non-relatedid you notice xda updated this evening? notifications are broken now have to check things manually
I followed the instructions to a T and when I went to reboot in TWRP I have no OS installed what the **** happend?
EDIT: I saved myself when because I used the rootjunky tool to restore 5.1.1 then flahsed twrp on that and then flashed the update 6.0.1 zip from another thread on here. Hopefully I can figure this out. I'm good with android phone... first time messing with android wear.
EDIT: Second time is the charm I guess. Thanks for nobody screaming at me and calling me a nub!
codyedmonson said:
I followed the instructions to a T and when I went to reboot in TWRP I have no OS installed what the **** happend?
EDIT: I saved myself when because I used the rootjunky tool to restore 5.1.1 then flahsed twrp on that and then flashed the update 6.0.1 zip from another thread on here. Hopefully I can figure this out. I'm good with android phone... first time messing with android wear.
EDIT: Second time is the charm I guess. Thanks for nobody screaming at me and calling me a nub!
Click to expand...
Click to collapse
Um probably should have told people but TWRP would say that but you should just ignore it cause your system is there
Xmaster24 said:
Um probably should have told people but TWRP would say that but you should just ignore it cause your system is there
Click to expand...
Click to collapse
Yeahhh I figured that out after a while. My knowledge with rooting android wear is very limited at the moment. I've read as much as I could in one night lol. After figuring everything out with twrp/rooting I know have root and everything is going smoothly. Thanks for the tut!
okay, i used ur tutorial... fastboot flashed the twrp and pushed the supersu via adb to the sd... installed the zip via twrp... on leaving twrp it says "no os installed"... when i try to reboot the system it always just boots straight into twrp
/edit
okay! please add to your tutorial that you have to reboot and pair your watch first, after unlocking the bootloader! thx
cYraXx said:
okay, i used ur tutorial... fastboot flashed the twrp and pushed the supersu via adb to the sd... installed the zip via twrp... on leaving twrp it says "no os installed"... when i try to reboot the system it always just boots straight into twrp
/edit
okay! please add to your tutorial that you have to reboot and pair your watch first, after unlocking the bootloader! thx
Click to expand...
Click to collapse
Thanks was not aware that was a requirement strange that that happens
his thread gets a tad confussing ..is there a clear guide on doing 6.0.1 ? please..
Eggman72 said:
his thread gets a tad confussing ..is there a clear guide on doing 6.0.1 ? please..
Click to expand...
Click to collapse
What's confusing you? It's almost the same as rooting a phone flash twrp install supersu zip
Posters saying this is missing etc...im unsure whether posted tools etc are all there...rooted plenty of phones etc..just never a smartwatch..dont want to end up with a nice paperweight (I know its always a risk) seems some people have had a couple of issues Os missing etc..
Eggman72 said:
Posters saying this is missing etc...im unsure whether posted tools etc are all there...rooted plenty of phones etc..just never a smartwatch..dont want to end up with a nice paperweight (I know its always a risk) seems some people have had a couple of issues Os missing etc..
Click to expand...
Click to collapse
OS missing is just fault of twrp not me besides it's meaningless error it simply cannot write to system so it assumes it those not exist. Everything you need is there apart from adb but just get adb minimal from XDA. With my method there is no risk of a paperweight it only touches recovery and kernel which both can be easily replaced. The only thing that can really kill a phone is a messed up bootloader update/mod. I have taken everything posters said into account and updated accordingly. Originally I just wrote what worked for me but now I updated it for universal use
Thanks for the reply & clarificartion.. you say 1.Unlock the bootloader if not already unlocked
(Make sure to set up device after unlocking bootloader otherwise no boot!) does that mean after unlock it will reboot into OS and you perform language setup & pairing ? or after its done the unlock it go's straight into os for setup ?
Eggman72 said:
Thanks for the reply & clarificartion.. you say 1.Unlock the bootloader if not already unlocked
(Make sure to set up device after unlocking bootloader otherwise no boot!) does that mean after unlock it will reboot into OS and you perform language setup & pairing ? or after its done the unlock it go's straight into os for setup ?
Click to expand...
Click to collapse
After unlocking go straight to OS and setup because rooting with an empty data partition breaks the kernel
Do you reboot or does just go straight in ?
Eggman72 said:
Do you reboot or does just go straight in ?
Click to expand...
Click to collapse
I'm not sure I think it does yes just try it if it thosen't its simple as clicking start on the watch bootloader screen
bootloader unlocked fine..twrp installed fine..pushed files install and i get this error..any clues guys ?busy box installs but no super user... help !!!