Database Info

I installed a 3g rom on wifi

Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks

Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk

nawialkair said:
Hi
I made a very stupid mistake
I used the tool to root my xoom wifi model
I used the tool in this thread
http://forum.xda-developers.com/showthread.php?t=1011196
I tried to post this issue in the thread but I did not have the permissions.
by mistake I used the root of the 3G model
I followed the steps and everything was ok
I tried the unroot and here is the deadly (hopefully not) mistake
the xoom stops and first screen and refuses to boot
Did I brick my device??
Is there a way to resolve this problem??
Thanks
Click to expand...
Click to collapse
what does the first screen say? failed boot image?

BeagleBoy said:
Yes, you have bricked it. Fastboot won't work at this point, so your only option is probably to return it.
-Jim (who's on his 2nd xoom)
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
That's the thing I did not want to hear but expected it.
============================================
znfrazier said:
what does the first screen say? failed boot image?
Click to expand...
Click to collapse
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support

nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.

nawialkair said:
That's the thing I did not want to hear but expected it.
============================================
No
I am stuck at the motorola logo and the word dual core technology
When I press Volume up or down (fanrkly I could not get into that menu again) I get a list
it includes the following:
Fast Boot
If I choose it I get
Starting Fastboot protocol support
Click to expand...
Click to collapse
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.

znfrazier said:
Can you see the xoom in /fastboot devices? See if you can access you xoom from the computer. I actually did the same thing and got mine in working order.
Click to expand...
Click to collapse
Yes I can see it
Thank you
stevenege said:
Try doing this real quick, the best that can happen is that you can turn this around. You may NOT in fact be bricked. I made the mistake of doing this also, but I figured it is just like when I was using the Danger SPL on the G1 and I had to at least find a way.
So, do this real quick if you know how.
1. Power on and press Vol - at the same time
2. Open a command prompt to your ADB file and type in fastboot oem unlock
3. If this lets you in (it may not) go through the regular procedure of pressing Vol -+-+
4. It will format and you should know if it is in fact bricked or not because it won't boot up.
5. ******
6. Profit???
Let us know how it goes.
Click to expand...
Click to collapse
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks

root using the instructions in this thread it should fix your problem
http://forum.xda-developers.com/showthread.php?t=1010568

nawialkair said:
Yes I can see it
Thank you
I did that
and it started the format
After the boot, it stopped at the same place
Motorola's Logo and Dual Core
What's next??
thanks
Click to expand...
Click to collapse
you should try flashing the boot.img used to root i believe its tiamat 1.1.6 and the system.img for wifi. i have the stock system.img if you need it. hopefully that would git ya to boot atleast. MAKE SURE THAT IT IS WIFI ONLY.

Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least

stevenege said:
Go here and follow the second post I posted. This will help you do this without downloading the files because they are already there.
Give it a shot at least
Click to expand...
Click to collapse
did they fix the boot prob with the one click? i haven't tried it.

znfrazier said:
did they fix the boot prob with the one click? i haven't tried it.
Click to expand...
Click to collapse
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.

stevenege said:
Yes, it has all been fixed. There still seems to be an issue with SU rights until you download BusyBox and no clue why.
I have been testing the WiFi one constantly and have not had any major hickups.
Click to expand...
Click to collapse
good good. ill have to check it out. i still need to try out the pimp my xoom. ill post over there haha. gotta stay on topic.

Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface

nawialkair said:
Thanks ALL
I flashed Tiamat 1.1.6 boot.img
the problem is that when using this command:
adb remount
I get
error: device not found
The xoom is defined in the device manager as
Android adb Interface
Click to expand...
Click to collapse
Sounds like you are probably bricked :-/

Can I get the stock boot image
I just want to try that last option

I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much

nawialkair said:
I flashed the stock img and system img
It works fine
Yaaaaa
Thanks very much
Thanks very much
Click to expand...
Click to collapse
Told ya haha, save those files on your computer for next time. I keep them in close reach just incase something happens. if you have any other problems give me a holla. glad everything is working again.

I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.

jarretf said:
I think I'm more screwed than OP because I was already unlocked and rooted. Then locked my wifi xoom with the 3g one click tool. Yes I know that was very stupid but I was wondering what are my options?
Take it back to Amazon?
Use the following method in this thread?
Wait for SBF?
Thank you your time and sorry if I hijacked this thread.
Click to expand...
Click to collapse
It relocked? Yikes... I don't trust those 1-click things. I need to know what's going on step by step. My first Xoom got bricked when I thought I had untainted OEM image files and relocked it. There's really no reason to relock a Wifi Xoom right now.
Anyway, if it relocked, you might have been in the same boat I was where the computer wouldn't recognize the Xoom in Fastboot mode or RSD mode. And I went and got it exchanged at that point.
Oh, if RSD Lite can't see your Xoom in RSD mode, you might be out of luck. SBF won't help if RSD Lite can't see your Xoom. BUT, if it does see it, it sounds like you can flash the 3G/4G SBF from Motorola/Verizon and to get sorta running, then use Fastboot to overwrite the boot and system partitions.

[GUIDE] How to fix the «Wifi Error»

Greetings Everyone !
Flashing a ROM can bring you problems. One of these's problems is the «Wifi Error» or the «Data Error» where you can't enable wifi or access to Data because it's written Error or you don't have mobile data.
Major Problem 1 -> S-ON ROM flash without 4ext SmartFlash Enabled
People who are flashing ROM while being S-ON needs to enabled SmartFlash [GUIDE] Flashing roms with S-ON and 1.27+ HBOOT
You only need to do this ONCE, once you have flashed your first custom ROM and enabled permanent smartflash, you don't need to this any more!
Major Problem 2 ->RIL/Radio Match
RIL/Radio Match is not required if you want internet to work. When you have the «Wifi Error» the problem can be from an RIL/Radio bad match. You need to have the good RIL/Radiofor you. Here's a list of RIL/Radio A better match = Better result (wifi speed, etc.) You can use this app, GETRIL to find if your RIL/Radio match.
Major Problem 3 ->Kernel
T-Macgnolia said:
Let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
How to Flash boot.img:
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot
ganeshp said:
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
Click to expand...
Click to collapse
Other Issues:
Try this App :WiFix
Then go to recovery and wipe cache\dalvic cache\cache+dalvic,Wifi should be Fixed. If it doesn't find any network, delete the file /data/misc/wifi/wpa_supplicant.
For Viper S ROM user having problem:
deadfire19 said:
I made a nifty fix .zip if anyone else has the WiFi issue with instructions on how to fix.
http://www.mediafire.com/download.php?5brepoeyx1nn4sh
Click to expand...
Click to collapse
If you are getting very poor or no WiFi signal, you might take the back case off, and check the little golden pins above the camera. They may have gotten bent.
realsis said:
The antennas are the copper colored prongs on the inside of the phone case, and the inside of the phone. You can google it to get a better picture . Some say to CAREFULLY and SLIGHTLY lift the antennas to help with better reception but they are very fragile and the last thing you want to do is break them off so if you decide to do this, just do it slightly and very softly. You don't want to move them too much. I tired this myself to see if it would help with better reception, but honestly didn't see much difference. But it's worth a try. Just be very careful. I do hope you get your Wi-Fi problem solved. What you can do is take the device to a local cell phone repair shop. Perhaps they can fix the problem. And usually the local shops are quite reasonable in price. This might be a better option for you. This way the shop can trouble shoot and fix the problem with your Wi-Fi. It's another option.. hope this is helpful. Best of luck.
Click to expand...
Click to collapse
Sent from my HTC Sensation Z710e using xda premium
NOTE: I'm not responsible for bricked devices, etc.

It´s possible kernel mistmatch with S-OFF? or simply will change of Kernel have any effect?
my Kernel is [email protected]# 1 on 3.33.401.6
Core version 3.0.16-g31a4fc7
THX

Fr3nc said:
It´s possible kernel mistmatch with S-OFF? or simply will change of Kernel have any effect?
my Kernel is [email protected]# 1 on 3.33.401.6
Core version 3.0.16-g31a4fc7
THX
Click to expand...
Click to collapse
Yes..! Is it the stock kernel? You should not have problem but you can try an other kernel, it should work on s-off
Sent from my HTC Sensation using xda premium

These aren't working with my problem , i've changed radio & tried to flash to different rom :/
OP , Which method have you done to fix your wifi on your 4G ? Or have you tried them all to get it to work ?

ZXHunterx7 said:
These aren't working with my problem , i've changed radio & tried to flash to different rom :/
OP , Which method have you done to fix your wifi on your 4G ? Or have you tried them all to get it to work ?
Click to expand...
Click to collapse
Same here none of these worked for me

srjgrg1 said:
Same here none of these worked for me
Click to expand...
Click to collapse
try this
go to internal storage
data>misc>wifi and delete the wpa_supplicant.conf file
first copy it to the sdcard just in case

rzr86 said:
try this
go to internal storage
data>misc>wifi and delete the wpa_supplicant.conf file
first copy it to the sdcard just in case
Click to expand...
Click to collapse
Nope it didn't work and i have already tried this several times

srjgrg1 said:
Nope it didn't work and i have already tried this several times
Click to expand...
Click to collapse
use then a ruu.exe to return to stock
after that if wifi still doesn't work then probably it is a hardware issue

rzr86 said:
use then a ruu.exe to return to stock
after that if wifi still doesn't work then probably it is a hardware issue
Click to expand...
Click to collapse
I already run the ruu and went back to stuck but it also didn't fixed the wifi issue...and i tried different rom but nothing worked and i flashed cm10 at first wifi wasn't working but surprisingly wifi worked for few days so i thought to install viper rom cause i was having issue with cm10. After i installed viper sometimes wifi used to work and sometimes not and now it doesn't work with the cm10 either. I'm not sure if this is a hardware issue cause when i got my phone wifi was working but suddenly after few days it stopped.

srjgrg1 said:
I already run the ruu and went back to stuck but it also didn't fixed the wifi issue...and i tried different rom but nothing worked and i flashed cm10 at first wifi wasn't working but surprisingly wifi worked for few days so i thought to install viper rom cause i was having issue with cm10. After i installed viper sometimes wifi used to work and sometimes not and now it doesn't work with the cm10 either. I'm not sure if this is a hardware issue cause when i got my phone wifi was working but suddenly after few days it stopped.
Click to expand...
Click to collapse
i am out of ideas

rzr86 said:
i am out of ideas
Click to expand...
Click to collapse
Its alrite bro thanks for your concern though.

Hello, i cant turn an me Wifi "failed to load driver" a have Wifix installed no Run i have Rom changed no Run i have new Radio Flashen No Run i Wifi Location changed no Run..
i have no Ideas

fabian_screta said:
Hello, i cant turn an me Wifi "failed to load driver" a have Wifix installed no Run i have Rom changed no Run i have new Radio Flashen No Run i Wifi Location changed no Run..
i have no Ideas
Click to expand...
Click to collapse
run a ruu.exe
it returns the device into complete stock condition as you bought it
see here
http://forum.xda-developers.com/showthread.php?t=1672425

rzr86 said:
run a ruu.exe
it returns the device into complete stock condition as you bought it
see here
http://forum.xda-developers.com/showthread.php?t=1672425
Click to expand...
Click to collapse
i have Flash the "RUU_PYRAMID_ICS_HTC_Europe_3.33.401.53_Radio_11.76A.3504.00U_11.24A.3504.31_M_release_280871_signed.exe" wlan does not RUN!

I have no more ideas what i can do that wifi works! Anyone have a idea?

rioadorl subsequent
i have fix it!
i have Delete the FOLDER: /data/misc/wifi/
and not Only the File /data/misc/wifi/wpa_supplicant.conf!
After Delete Reboot and wlan Works!

fabian_screta said:
i have fix it!
i have Delete the FOLDER: /data/misc/wifi/
and not Only the File /data/misc/wifi/wpa_supplicant.conf!
After Delete Reboot and wlan Works!
Click to expand...
Click to collapse
That is good to know
Deleting the whole folder:good:
Sent from my HTC Sensation using xda premium

OP if you want put this solution in your guide (post #10)
it will hepl a lot of people
http://forum.xda-developers.com/showthread.php?p=42651435#post42651435

Wifi hotspot or wifi tether not broadcasting signal

I am not sure what caused this. Yesterday during the day, i was using my wireless tether app just fine. Then lastnight I tried to connect to my computer, and my Android wifi network is not listed on my computer as an available network to connect to. I have rebooted the phone and computer about 5 times. I have tried a different computer, and an ipod, nothing is seeing my wireless tether network.
I also tried using the stock wifi hotspot app that came with the phone, and it will not start up or broadcast a signal.
So for whatever reason, my phone stopped broadcasting out a wifi signal. I can still connect to wifi from my phone to another router, I am just not able to use my phone as a hotspot anymore.
Has anyone else had this problem or seen a discussion on this issue anywhere? I have the stock ROM, but I am rooted. I did not change anything from the time that it was working, to the time when it stopped. I have tried uninstalling and reinstalling, but I know thats not the problem anyhow.

Same thing.
The same thing happened to me, the only way I could fix it was to restore a nandroid from when it worked and update my apps from titanium backups. Still don't know what happened or why.

Ok, yeah I am kind of assuming I am going to have to do a reset or load a custom ROM or something. Thanks for the info.
If anyone else has any suggestions, let me know please.

whitelightnin3006 said:
Ok, yeah I am kind of assuming I am going to have to do a reset or load a custom ROM or something. Thanks for the info.
If anyone else has any suggestions, let me know please.
Click to expand...
Click to collapse
Yes I am also having this issue, It was working last night Now it will not show up at all. I did nothing.. I did get a update on my Super user

Can't root (SU) or use FoxFi after Sprint ASA-14 update
So I never rooted my phone and made the mistake of allowing Spring to do an OTA update to ASA-14. Now all the root exploits don't work and FoxFI doesn't work. Since I can't root I can't use Wifi Tether either.
I desperately need someway to let my phone do a WIFI Hotspot with sprint ASA-14 update on my phone! HELP!

Why can't you just unlock the bootloader and root?

arrrghhh said:
Why can't you just unlock the bootloader and root?
Click to expand...
Click to collapse
I have unlocked the bootloader, but with the ASA 14 update I am unable to root via the moto2fail method. I was able to root with ASA 10 using the same method but when I try to downgrade I get a security error on the stock bootloader.

vjdave said:
I have unlocked the bootloader, but with the ASA 14 update I am unable to root via the moto2fail method. I was able to root with ASA 10 using the same method but when I try to downgrade I get a security error on the stock bootloader.
Click to expand...
Click to collapse
Motofail2go is broke with the ASA14 firmware. If you are unlocked, flash the TWRP recovery available in this sub-forum and it will root your phone for you..
Get your TWRP image here: http://forum.xda-developers.com/showthread.php?t=1887070

I use method from HERE. It's easier to gain root.

huatz84 said:
I use method from HERE. It's easier to gain root.
Click to expand...
Click to collapse
The new TWRP automatically roots the device... flash TWRP and when you reboot TWRP it will detect you are not rooted and root the device for you.... so I'm not sure how that thread is easier lol.
Either way, you will get root and custom recovery. So either method is fine.

arrrghhh said:
The new TWRP automatically roots the device... flash TWRP and when you reboot TWRP it will detect you are not rooted and root the device for you.... so I'm not sure how that thread is easier lol.
Either way, you will get root and custom recovery. So either method is fine.
Click to expand...
Click to collapse
Yeah..actually I rooted by flashing cwm and then the superSU.zip. After that,I flashed TWRP. I'm getting used to TWRP since using SS3 on my D4.
Sent from my XT897 using Tapatalk 2

Success!
Thanks for your help! I got TWRP installed and then installed the SU.zip and now I have root with ASA 14.
FoxFI still doesn't work but I was able to get "WiFi Tether" to work since I am now rooted.

I rooted and now the WIFI tether app will not work/.. ANY IDEAS

just FTR, my photon q with some version of CWM and supersu as the root program was able to use "wifi tether" (no longer available on the market!?). this was just last night.
the only problem is that it can only broadcast an ad-hoc network. this isn't picked up by a lot of devices, namely tablets. my win7 laptop can see it and connect just fine, however.
i tried changing the "setup method" to the only other of the two available (some ad-hoc method and "native framework tether") and the device crashed. when it rebooted, it was selected, but it didn't work.
food for thought.

Angry Black Man said:
just FTR, my photon q with some version of CWM and supersu as the root program was able to use "wifi tether" (no longer available on the market!?). this was just last night.
the only problem is that it can only broadcast an ad-hoc network. this isn't picked up by a lot of devices, namely tablets. my win7 laptop can see it and connect just fine, however.
i tried changing the "setup method" to the only other of the two available (some ad-hoc method and "native framework tether") and the device crashed. when it rebooted, it was selected, but it didn't work.
food for thought.
Click to expand...
Click to collapse
Not to hijack but can anyone recommend an app to hide the tethering usage from the carrier? Like a proxy app? Thanks in advance.

[Q] HELPP!

the rom i'm running doesn't have a radio... i have the PG861IMG.zip and i put it in the root of my sdcard.. go to bootloader and it says parsing... but stops and finds nothing. ??

svisser89 said:
the rom i'm running doesn't have a radio... i have the PG861IMG.zip and i put it in the root of my sdcard.. go to bootloader and it says parsing... but stops and finds nothing. ??
Click to expand...
Click to collapse
HY, if the rom doesnt support radio it means it isnt built to cope with it,but you can install internet radio like tune in! Please press thanks if i helped

svisser89 said:
the rom i'm running doesn't have a radio... i have the PG861IMG.zip and i put it in the root of my sdcard.. go to bootloader and it says parsing... but stops and finds nothing. ??
Click to expand...
Click to collapse
its like a common issue with jb4.2.2 roms
speacialy custom one

Pranto Roy said:
its like a common issue with jb4.2.2 roms
speacialy custom one
Click to expand...
Click to collapse
I updated my evo lte to sense 5 android 4.3 so it looks exactly like the HTC ONE.. however. when i openn my superuser app it tells me i need to update my binaries, i choose to do so and my phone reboots and when i reopen the superuser app.. same thing. are you able to help me or can you refer me to someone who can? I'm new to XDA.

svisser89 said:
I updated my evo lte to sense 5 android 4.3 so it looks exactly like the HTC ONE.. however. when i openn my superuser app it tells me i need to update my binaries, i choose to do so and my phone reboots and when i reopen the superuser app.. same thing. are you able to help me or can you refer me to someone who can? I'm new to XDA.
Click to expand...
Click to collapse
Try Flashing it via Recovery
http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip

Yes I ran into the same problem, some roms will not work, try another rom.

evo lte no rom
My evo lte is still s-on, and honestly i'm having so many problems with it. i'd like s-off but i'd have to do dirty racun and I don't have Ubuntu... anyways. right now i am having NO luck finding a rom that will work, i've tried charmeleon, mean rom, and a few others flashed them in recovery, flashed their boot.img in fastboot and I can't even see the boot image half the time. I did notice when the charmeleon rom was trying to install that it stopped when it said installing kernel and rebooted itself and I haven't been able to get past there. i'm not picky, at this point I want ANY rom that will actually work so i can have a phone again, please help
ps. I don't have a backup. I had several but somewhere in trying to figure things out, i wiped the entire sd card so i've just been installing roms and trying them via usb mount from recovery
nash211 said:
Yes I ran into the same problem, some roms will not work, try another rom.
Click to expand...
Click to collapse

try one of these
http://forum.xda-developers.com/wiki/HTC_Evo/ROMs
svisser89 said:
My evo lte is still s-on, and honestly i'm having so many problems with it. i'd like s-off but i'd have to do dirty racun and I don't have Ubuntu... anyways. right now i am having NO luck finding a rom that will work, i've tried charmeleon, mean rom, and a few others flashed them in recovery, flashed their boot.img in fastboot and I can't even see the boot image half the time. I did notice when the charmeleon rom was trying to install that it stopped when it said installing kernel and rebooted itself and I haven't been able to get past there. i'm not picky, at this point I want ANY rom that will actually work so i can have a phone again, please help
ps. I don't have a backup. I had several but somewhere in trying to figure things out, i wiped the entire sd card so i've just been installing roms and trying them via usb mount from recovery
Click to expand...
Click to collapse

thanks for the reply! I tried almost all of those roms and the download files have been deleted . can you possibly send me a direct link to a rom? also since i'm s-on... i heard HTC dumlock is a good alternative to flash kernels cause i've been using fastboot and they successfully flash but if i by chance get to the lock screen i can't pull the ring up to open the phone, it's completely unresponsive.
nash211 said:
try one of these
http://forum.xda-developers.com/wiki/HTC_Evo/ROMs
Click to expand...
Click to collapse

hello
I flashed that update but I still get the same thing. binaries are out of date, and then superuser closes. when i hit the normal install it fails and i also have the option to update the binaries through recovery... maybe a stupid question. is there a zip that just has up to date binaries alone? right now i'm on sense five android 4.1.2
Pranto Roy said:
Try Flashing it via Recovery
http://download.chainfire.eu/342/SuperSU/UPDATE-SuperSU-v1.43.zip
Click to expand...
Click to collapse

sent you a pm
svisser89 said:
thanks for the reply! I tried almost all of those roms and the download files have been deleted . can you possibly send me a direct link to a rom? also since i'm s-on... i heard HTC dumlock is a good alternative to flash kernels cause i've been using fastboot and they successfully flash but if i by chance get to the lock screen i can't pull the ring up to open the phone, it's completely unresponsive.
Click to expand...
Click to collapse

i didn't get the private message..
nash211 said:
sent you a pm
Click to expand...
Click to collapse

just try another radio app from google market, or search in rom thread about radio fix

Try these web sites themikmik.com theunlockr.com needrom.com
I had allot of difficulty findimg somethng that worked well with my HTC one s, I googled allot till I found one that worked
I used TWRP for flashing my roms, worked great

I cannot send private messages for some reason svisser89 so try this web site for your issue
http://www.android.gs/how-to-change-fonts-on-any-android-device/

svisser89 said:
I flashed that update but I still get the same thing. binaries are out of date, and then superuser closes. when i hit the normal install it fails and i also have the option to update the binaries through recovery... maybe a stupid question. is there a zip that just has up to date binaries alone? right now i'm on sense five android 4.1.2
Click to expand...
Click to collapse
that file contains them

[Q] How to take OTA update after Sunshine

Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!

Andyw2100 said:
Please forgive me for having to ask what I'm sure sounds like a stupid question, but I have no idea how to accept the OTA update Verizon is attempting to send me to version 4.4.4 on my HTC One M8 now that I have used Sunshine to attain S-Off and have TWRP and SuperSU installed.
I have used ADB, but am not very familiar with it at all.
I saw threads talking about flashing ROMS, but for the most part it really seems like Greek to me.
I had only gone down the Sunshine road because I wanted root access mainly for one app--Lightflow. In retrospect I'm feeling like I opened a can of worms. But the can is open, and the worms are out there, so now I need to learn how to handle them.
I know I am supposed to keep S-off, no matter what I do. I think perhaps I'm supposed to revert back somehow to a "stock" bootloader (instead of TWRP--is that right?) but I don't have any idea how to do that (though I expect ADB is involved), and I also don't know what effect that would have on SuperSu, as I vaguely recall TWRP may have been required for SuperSU to work.
I'm really lost.
Any help, in very easy to understand terms (pretend you're trying to explain this to your grandmother) would be appreciated.
Thanks!
Click to expand...
Click to collapse
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!

Andyw2100 said:
Thanks for the response.
So the question is how do I go back to my stock recovery instead of TWRP?
And then after taking the update, what do I need to do to reinstall TWRP and then flash the latest SuperSU.zip file?
I realize I should know this stuff, but I had help from the Sunshine folks last time, so I really don't remember everything that went on, or exactly what I did vs. what they did, etc.
Thanks again!
Click to expand...
Click to collapse
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.

The Stig 04 said:
Taking the OTA is simple, you'll need your stock 4.4.3 recovery installed not TWRP. If you try to take it as you are right now it will fail everytime because of TWRP. I'm going to assume you haven't modified your stock ROM in anyway so accept the OTA and let it install. You will not lose S-OFF so rooting is simple. Reinstall TWRP and flash the latest SuperSU zip file.
Click to expand...
Click to collapse
berndblb said:
You don't need to do any of that.
Download the exe from this thread: http://forum.xda-developers.com/showthread.php?p=56211035
run it and you will be on stock 4.4.4.
To get TWRP back you have to flash it fastboot (lots of tutorials all over the forum for that) and with the recovery installed you can just flash SuperSU in recovery to gain root again.
Click to expand...
Click to collapse
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!

Andyw2100 said:
Thanks. That thread says that using that .exe is going to wipe my phone, which would then mean I need to restore it from a backup. I think I'd really just rather take the OTA update to 4.4.4, since in the future I'm going to want to take other OTA updates as well. So if I can learn how to return to my stock recovery now, and the rest of it for this OTA update, I should be good to go for future OTA updates.
Thanks, though.
So my questions above remain about how to revert to the stock recovery, and then how to reinstall TWRP and SuperSU.
Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it. Though you should already have this on your computer or SD Card.
Edit: I believe there is an even easier way, just have never done it/tried it so I don't wanna lie and act like I know what to do.

The Stig 04 said:
http://forum.xda-developers.com/showthread.php?t=2723159
Download the file "Stock Recovery 4.4.3" from the thread above. Flash that using ADB, once you take the OTA and are on 4.4.4 Flash TWRP using ADB again.
http://forum.xda-developers.com/showthread.php?t=1538053
Download SuperSu from the thread above and place that in your SD Card. Boot into recovery and install it.
Click to expand...
Click to collapse
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...

Thanks to both of you.
I don't believe I removed any bloatware, so I think the OTA update should work.
How do I flash the stock recovery in fastboot?
Again, many thanks!

I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!

berndblb said:
You have to flash the stock recovery in fastboot - not ADB. And you gotta make sure all the bloatware that comes with the original stock rom is in place or the OTA will fail (it does a "system integrity check" prior to applying the OTA). That can be a headache if you do not have a backup of apps you may have removed...
Each future update will be available within days of release here on XDA, either as a standalone firmware update or stock rooted rom or both. I would not take OTAs - ever.
Develop a solid backup routine and restoring your device is a 20 minute exercise...
Click to expand...
Click to collapse
Sorry I thought fastboot and ADB was kinda that same thing seeing as it was refereed to as "fastboot/adb directory"? If not my bad! Also this is the method I always use to take OTA's and have never ever had a problem.

Andyw2100 said:
I just checked my ADB folder, and see a fastboot.exe there, so I imagine it's just a command like ADB. I'll give this a shot later. Again, many thanks to both of you for the assistance. I will post again with, hopefully, my good results, or with additional questions.
Thanks!
Click to expand...
Click to collapse
Put the recovery image into the same folder with your fastboot.exe
Open a command prompt from that folder (shift + right click > open cmd window here)
check connection with
Code:
fastboot devices
if successful
Code:
fastboot flash recovery <name of recovery>.img

Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app

mumbles202 said:
Would you need to remove root before taking the OTA? Just curious.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
No. You will lose root after the ota so it doesn't matter but you can always get it back as long as you are S-OFF by flashing a custom recovery like TWRP and then flashing SuperSu.

Well, I have run into a snag right off the bat.
While the command "ADB Devices" sees the phone, "Fastboot Devices" does not.
Any ideas as to how to rectify this?
Thanks!

I did some googling, and this problem I solved on my own.
I had to use adb to get into fastboot USB mode or something with adb reboot bootloader, and then fastboot devices worked.
I'm now continuing on.

Well, so much for this being easy.
I believe I successfully flashed my stock recovery.
But apparently I no longer have the OTA update ready to install, as at some point I tried to run it again just to get TWRP up, and now it's not showing as available. And when I try to check for updates in Settings/Software update/Check new I get an error message that says Download Unsuccessful. We were not able to download this update.
For now I guess I'll wait and see if Verizon tries to send me the update again, or if it works if I check for it myself some other time. (Or if anyone here has any suggestions.)
Also, I still seem to have root access. I thought that I wouldn't, since I believe I have replaced TWRP with the stock recovery.

I'm also now getting a constant error message about Google Play Services having stopped. And my wi-fi doesn't seem to be connecting properly.
I'm really wondering just what the heck I've done.

Well, for anyone still following my saga...
Things are somewhat better, but not totally resolved.
I kept checking, and eventually I was able to download the OTA update to 4.4.4. I did, I updated, and all went smoothly. I then was able to flash TWRP and then install Super SU and I have root access again. So on that front, all is well.
The problems that remain, though, are that I still am having issues with Google Play Services quitting and my Wi Fi not connecting. Could these things be related somehow? I've tried clearing the cache and then actually all data from Google Play services, but that has not helped. I have deleted my networks, and then tried reconnecting to them, but that also has not helped. It shows my networks in range as "saved" or "disabled" but won't connect to any of them.
Any ideas for me?
Thanks.
And thanks for the help in getting the 4.4.4 OTA update. At least that worked!

I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!

Andyw2100 said:
I realize I am basically having a conversation with myself at this point, but just to wrap things up, in case anyone does come along and read any of this...
I have solved all my issues.
The Google Play Services issue must have been related to the Wi-Fi not connecting, and the Wi-Fi not connecting was due to my main network actually having an issue and the fact that I had never authorized the phone on the other networks. I guess this is what happens after being up almost 24 hours. At least I think everything is OK now.
Again, thanks to those that helped!
Click to expand...
Click to collapse
Not sure why I stopped receiving notifications from your thread. But at least you got your phone in working order! lol