Database Users

[Q] Liberty3 v2.0gold hates TBH wifi patch?

Ok, here it goes. let me first say that I am just learning alot of this stuff. I'v had my DX for almost a year now and had it Z4rooted and the tether apk applied in no time at all then came the GB update which was actually pushed onto me. So be it.
I have been watching the forums and reading posts off and on since the update, waiting till another reliable tether patch came out. I have the radiocomm app but was always leery of using it with my limited knowledge in this field.
Today after alot of reading I decided to install Liberty3 v2.0 Gold and did so with no problem whatsoever. then I continued reading and then decided to continue on with 3GHotspot.zip and TBH_DX_Tether_Patch_1.0.zip in that order. I did it through the built in ROM mgr. in liberty3 in the rom toolbox. with reboots in between.
I then went into my apps list and clicked on the new 3G wi-fi tether icon and was immediately shot to my boot screen animation. Thinking this was a fluke I attempted it 2 more times with the same result, Reboot. After this I noticed that I was on 3g data and no longer connected to my home wi-fi router I went in and tried to turn that back on but it won't even try. I'm locked out of wi-fi now as well.
I then turned to my friend google and started looking around and found one post and only one posting listing at mydroidworld post# 35944 that had this link "3GHotspot Unpatch --- Download" but that link was broken because of it being a megaupload link (which we all know was seized by the feds)
I have no idea what to do to rectify this situation. I am all for re-flashing the ROM and plan on doing that but I would like some guidance on this before I start messing things up worse than they already are. are there uninstalls for both of thes zips? if so where? have either of these altered my radios NVM authentication strings with these hacks and patches? can they be undone? please help.

Nope, no uninstalls for those zips. At least not to my knowledge.

Ok, I ended up having to SBf back to .602 with RSDLite 5.4.4 and then take the OTA update to .605.
I then re-flashed the Liberty3 v2.0Gold and then through the built in ROM Mgr. I installed the WugPacked GB Tether Patch.zip and everything worked out great. working free Wi-Fi. Thanks to those that both helped and wanted to help but forgot to post anything in the space provided.
Issue solved.

"Can't connect to camera" Error

First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)

Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
the error when booted can be resoled by flashing the latest vendor img, or at least the one relevant to your roms version.
took me about 2 weeks to figure this out because no one would give me the slightest hint when i asked.
the error screen when it first tries to start i havent been able to resolve, and am thinking there may be none.
not sure what your camera issue could be, but i have seen cam issues from the kernel, when the switch to 6.0,1 first began to merge.
maybe test another kernel, other than that i dont know.

Samehere
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
I'm facing exactly the same issue. The camera works fine when I flash a stock based ROM like pure nexus or digitalhigh but as soon as I flash an aosp based ROM or cyanogenmod like chroma,screw'd,benzo. The camera says couldn't connect to camera and nothing seems to work. I've wiped cache, data but still no progress.
I even tried the flashable camera.zip but didn't work.

Problem Solved !!!
Ju43 said:
First of all I know there's another thread about this, but the guy seemed to be able to fix this problem by rebooting his phone so I'm making a new thread.
Today I flashed CM13 on my Nexus6P and it all worked fine until I tried starting the camera, which gave me the error mentioned in the title. Restarting the phone and erasng the app's data didn't work either.
Also everytime I boot my phone it shows me an "your device is corrupted" screen (not the bootloader unlocked screen) and when the phone starts it shows me something like "there's a problem with your phone, it might not work properly".
Is this my fault or is it a CM13 issue and how do I fix it? (I'm using today's official CM13 build with Open Gapps Mini arm64 for android 6.0)
Click to expand...
Click to collapse
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera

wrahul31 said:
Just flash the MBD08M.img via fastboot, then flash CM13 on top of it, restart the phone. The Camera won't work yet, now go to Benzo Rom and use his flashable vendor image for MMB29M via Recovery and Reboot. And it works like charm ! =D
You can also flash him flashable camera.zip, to get the stock camera
Click to expand...
Click to collapse
Thanks, I have reverted to stock ROM but I might try it soon

Can't get Sprint activation to work

Okay so I am currently on MPH24.49-18 and all my stuff is working okay.
However, whenever I try and upgrade my ROM I can never get my cellular radio to work. I tried using TWRP to update the ROM MPH24.107-58-1 located here http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Every time I do though the initial activation always fails and then when I try and go to the cellular settings it gives me the error com.android.phone has stopped working. I tried clearing data and cache of the phone app but that did not work. I also tried flashing a different modem but that has also failed. The ROM I am trying to flash should already come with the modem I need baked in so I don't think it's that.
I did manage to succesfully get my phone activated with Pure Nexus ROM but I didn't like the lack of Moto features. I would just try TruePureX but that one always hangs at "Extracting System" when installing. If I could even get that working then I might be okay.
Does anybody have a suggestion? Any help is much appreciated.
Thanks

wildwill2002 said:
Okay so I am currently on MPH24.49-18 and all my stuff is working okay.
However, whenever I try and upgrade my ROM I can never get my cellular radio to work. I tried using TWRP to update the ROM MPH24.107-58-1 located here http://forum.xda-developers.com/mot...rom-stock-rooted-debloated-x1575-6-0-t3262242
Every time I do though the initial activation always fails and then when I try and go to the cellular settings it gives me the error com.android.phone has stopped working. I tried clearing data and cache of the phone app but that did not work. I also tried flashing a different modem but that has also failed. The ROM I am trying to flash should already come with the modem I need baked in so I don't think it's that.
I did manage to succesfully get my phone activated with Pure Nexus ROM but I didn't like the lack of Moto features. I would just try TruePureX but that one always hangs at "Extracting System" when installing. If I could even get that working then I might be okay.
Does anybody have a suggestion? Any help is much appreciated.
Thanks
Click to expand...
Click to collapse
AICP 7.0 has been great on my Sprint phone.

"Camera error please restart camera"

I am on stock rom and rooted using the Super SU method. The only things I've flashed are the wifi fix, and edited build.prop to unlock tethering. My camera app will not open, and I get this error every single time. Doesn't work in instagram, snapchat, nothing. Anyone know what may be causing this?

Anyone? I would really like to get my camera working again

had the same problem today. restarted the phone and it worked again

ckret said:
had the same problem today. restarted the phone and it worked again
Click to expand...
Click to collapse
I've restarted several times even gone so far as to install a new OS. I'm thinking about undoing the changes just to fix this.

Try booting in Safe mode

ckret said:
Try booting in Safe mode
Click to expand...
Click to collapse
Camera still doesn't work

your cam may be disconnected from the motherboard. try claiming warranty

Wiped and installed the AOKP ROM and that fixed it.. Could've been the ROM or could've been the wipe, although I wiped several times before and it didn't fix it.

did you get the error again?
I had the same problem and I installed AOKP rom which fixed it at the beginning but after less 1 day the error back again.
now I'm on stock rom .35 (rooted with Magisk) and no camera error so far after 4 days

As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..

Mayanknagpal.nm said:
As far as i know, it is due to custom kernel, you may have installed that.. try flashing stock rom without any custom kernel..
Click to expand...
Click to collapse
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?

marcol87 said:
yes, I had custom kernel first time I got the error.
but then I got it also with custom rom.
now I'm on stock rom and stock kernel....but does it mean that I can never flash custom rom/kernel because of that error?
Click to expand...
Click to collapse
Custom roms do not have that error... and on stock rom you can use elementalX 2.0 , it is made for the .67.. so the camera issue is resolved.. i think this will help

I had this error on Stoneware .67 (stock based ROM) and resolved it by dirty flashing Stoneware and Magisk v.13 again.

and I had this error also on AOKP rom

I have been having this problem on the Stock ROM, non-rooted, for quite some time now. I have no idea what's causing this error. When I open it sometimes, it just throws an error. If I close it and open it again, it works as it should. It's very annoying.

I had the same thing, flashing roms didnt fix it so i flashed stock via RSD lite and everything was back to normal.

Same issue here, completely stock unrooted. This is not the first Android device I've had that's struggled to connect to the camera consistently... how hard can it be?

Can people getting this error try to disable the image stabilisation in video mode please? One of the errors I see when downloading a bug report refers to the stabilisation code and I've not had the "please restart camera" message since switching it off. Could be coincidence though as it's not like I get it every time the camera loads...

Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.

the.MindHacker said:
Hello ,
I tried rooting my Moto G5 using Moto G5 toolkit (flashing superSU). t
Then I flashed TWRP and Flashed the WLAN_CUSTOM
Now i get that generic warning screen of unlocked boot loader however My phone is not rooted. and I cant open camera at all , getting error as " Camera Busy - Camera unable to start. If this happens again, please power off your phone and restart."
Can someone help me fix this camera issue? or just help me to revert back as it was previously no root nothing, I guess this TOOLKIT has some bugs in it.
Any help will be appreciated as I am newbie with this android development.
Click to expand...
Click to collapse
I had the same issue as you after using the toolkit, did you fix it?

Android Auto: Something Went Wrong (Google Play Services)

I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.

I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.

GTF696 said:
I got pissed and went back to JUST the stock OTA for testing/verification. With the stock rom there are no issues. Seems like Lineage OS 15.1 on the Nexus 6P has some bugs to work out. A fully functional stock phone is better then being frustrated.
If anyone can confirm I'm not crazy or explain what I missed while troubleshooting that would be awesome.
Click to expand...
Click to collapse
Try magisk as root method insted of su...
Other than that, cant think any other solution

GTF696 said:
I recently acquired a Nexus 6P.
TWRP is properly installed as the Recovery - twrp-3.2.3-0-angler
First thing I did with the device was flash the latest Android 8.1 Oreo version to it - angler-ota-opm7.181205.001-abb36a2f
I then installed Lineage OS 15.1, Open G Apps 8.1 (nano), and SU
From there I've done nothing but struggle with bugs and quirks. The device has been re-imaged several different times, with different variations of the above setup, and one of the main things I need to get working (Android Auto) keeps failing. Does anyone have any idea why Android Auto keeps pulling up the error "Google Play Services doesn't seem to be working right now"
All of the suggestions I've found online have failed. Screenshots have been provided for the version info and error. I've already cleared the data caches and tried to re-install and re-flash the device.
Click to expand...
Click to collapse
I got error when installed lineageos15.0 on twrp 3.2.3 , suddenly automatic restart. Can you help me dude ?