Related
=====
Update
=====
I'm updating this thread so I don't spam the board.
After trying all kinds of software solutions, resets and all I gave up. It's a hardware problem (as far I can tell) and there is no way to fix it unless you replace one board on the phone.
This is how I found the problem:
I got another shadow from eBay with a broken screen but working wifi.
I swapped the main board and guess what? No wifi. The only thing I could think is that the other board on the phone, the one connected to the screen and circle pad thing was the problem and probably were the wifi part of the phone resides on.
Once I replaced that part the wifi worked with both boards.
If anyone is a hardware expert or just for curiosity want to see some pictures from both working and non-working boards, PM me.
=========
Original Post
=========
Hello guys, I got a T-mobile Shadow and I can't get the wifi to work. On the wireless info says "driver not loaded".
I tried to re-flash it with the original firmware several times (ok... 4 times).
I tried to use the beta version of wm6.1.
I tried to reset and hard-reset the phone over and over.
I tried to put the "wifiinit.lnk" on my startup folder and even run wifiinit.exe.
I tried to mtty it to check for bad nand block but the commands will not work (info 8). This password will work -> BsaD5SeoA
I can't return it to T-mobile because it was a phone with a broken screen that I bought from eBay.
So this is my last resort before I give up on wifi:
Does anyone know anything I could do to try to fix it?
Thanks
This is kind of an expensive solution, and should be used as last resort, you could try getting a WiFi MicroSD card. I'm guessing only the WiFi radio is having problems even though it says it's the driver.
Thanks ND4SPD for the reply.
I also think it's something wrong with the radio part and I guess as long t-mobile don't release an update I will stuck without wifi.
Keep the good work with the 6.1 rom!
I'm using it right now, so long neo interface!
P.S.: If someone find a solution please post it here.
I just looked up some stuff and found that there are quite a few people have had the same problem after updating to tmobiles update. The only two suggestions they had were to hard reset or try the update again.
I have one idea: flash my shadow with the original rom. The only problem is how to get the original rom? I know that there is the raw dump. Is there a way to make it flasheable?
edit:
Just did, I was able to flash it to the first firmware using the files @ ftp.
But still the same thing, no wifi.
I'll keep looking for a solution for this.
Could someone post this reg info from a wifi working shadow?
Code:
[HKEY_LOCAL_MACHINE\Comm\TNETW12511]
"Wireless"=dword:00000001
"ImagePath"="TNETW1251.dll"
"Group"="NDIS"
"DisplayName"="IEEE 802.11b/g Compatible Wi-Fi Adapter"
[HKEY_LOCAL_MACHINE\Comm\TNETW12511\Parms]
"InstanceNumber"=dword:00000000
"PowerSavePowerLevel"=dword:00000000
"defaultPowerLevel"=dword:00000000
"DSCPClassifier03_DTag"="7"
"DSCPClassifier03_CodePoint"="56"
"DSCPClassifier02_DTag"="5"
"DSCPClassifier02_CodePoint"="40"
"DSCPClassifier01_DTag"="1"
"DSCPClassifier01_CodePoint"="8"
"DSCPClassifier00_DTag"="0"
"DSCPClassifier00_CodePoint"="0"
"NumOfCodePoints"="4"
"IPPortClassifier02_DTag"="6"
"IPPortClassifier02_Port"="5003"
"IPPortClassifier02_IPAddress"="0a 03 89 02"
"IPPortClassifier01_DTag"="4"
"IPPortClassifier01_Port"="5002"
"IPPortClassifier01_IPAddress"="0a 03 89 02"
"IPPortClassifier00_DTag"="1"
"IPPortClassifier00_Port"="5001"
"IPPortClassifier00_IPAddress"="0a 03 89 02"
"NumOfDstIPPortClassifiers"="3"
"Clsfr_Type"="1"
"QOS_wmePsModeVO"="0"
"QOS_wmePsModeVI"="0"
"QOS_wmePsModeBK"="0"
"QOS_wmePsModeBE"="0"
"desiredPsMode"="1"
"RatePolicySGRetriesPerRateOfdmA"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRateOfdm"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRatePbcc"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicySGRetriesPerRateCck"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserRetriesPerRateOfdmA"="0,0,0,1,0,0,1,0,0,1,0,0,0"
"RatePolicyUserRetriesPerRateOfdm"="0,0,0,1,0,0,0,1,0,0,1,1,1"
"RatePolicyUserRetriesPerRatePbcc"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserRetriesPerRateCck"="1,1,1,1,1,1,1,1,1,1,1,1,1"
"RatePolicyUserLongRetryLimit"=dword:0000000A
"RatePolicyUserShortRetryLimit"=dword:0000000A
"RateAdaptationTimeout"=dword:0000012C
"FBLongInterval"=dword:000000C8
"FBShortInterval"=dword:00000028
"RateStepUpThreshold"=dword:00000002
"RateContThreshold"=dword:0000000A
"Beacon_IE_Table"="00 01 01 01 32 01 2a 01 03 01 06 01 07 01 20 01 25 01 23 01 30 01 28 01 2e 01 85 01 dd 00 52 f2 02 00 01"
"Beacon_IE_Table_Size"=dword:00000035
"Beacon_IE_Num_Of_Elem"=dword:00000015
"Beacon_Filter_Stored"=dword:00000001
"Beacon_Filter_Desired_State"=dword:00000000
"ArpIp_Addr"="c0 a8 00 5e"
"ArpIp_Filter_ena"=dword:00000000
"DtimListenInterval"=dword:00000001
"BeaconListenInterval"=dword:00000001
"HTCActiveSyncReconnectWorkaround"=dword:00000001
"dot11AuthenticationResponseTimeout"=dword:000001F4
"dot11MaxAuthRetry"=dword:00000002
"dot11DesiredChannel"=dword:0000000B
"AutoPowerModeDozeMode"=dword:00000002
"ShortSlotTime"=dword:00000000
"Mode4x"=dword:00000000
"MixedMode"=dword:00000000
"SpectrumManagement"=dword:00000000
"MultiRegulatoryDomain"=dword:00000000
"WME_Enable"=dword:00000001
"HTCWiFiLogoMICWorkaround"=dword:00000000
"TxPower"=dword:00000001
"PowerMgmtHangOverPeriod"=dword:00000005
"RSNPreAuthentication"=dword:00000001
"RecoveryEnable"=dword:00000000
"HTCAutoOffInterval4NoActivity"=dword:00002710
"HTCAutoOffIfNoActivityEnable"=dword:00000001
"MinimumDurationBetweenOidScans"=dword:00000005
"FirstConnScanEnabled"=dword:00000001
"WPAMixedMode"=dword:00000001
"RxBroadcastInPs"=dword:00000001
"HTCOutputWLANdebugLog"=dword:00000000
"BThWlanCoexistParamssgAntennaType"=dword:00000002
"BThWlanCoexistParamsnumberOfBtPackets"=dword:00000002
"BThWlanCoexistParamsnumberOfWlanPackets"=dword:00000004
"BThWlanCoexistParamssenseDisableTimer"=dword:00000320
"BThWlanCoexistRate"="0,0,1,0,0,1,1,1,0,1,1,1,1"
"BThWlanCoexistEnable"=dword:00000001
"dot11RTSThreshold"=dword:00001000
"dot11FragmentationThreshold"=dword:00001000
"dot11ShortPreambleInvoked"=dword:00000001
"HTCPreloadLEAP"=dword:00000000
"HTCGetIPWorkaround"=dword:00000001
"HTCAutoOffTimeout"=dword:0001D4C0
"HTCAutoOffMode"=dword:00000000
"HTCPowerMode"=dword:00000002
"ResetOnResume"=dword:00000000
"SysIntr"=dword:0000002B
"BusType"=dword:00000000
"BusNumber"=dword:00000000
Thank you
Maybe I can help.
Dump the file bk_02_0005.img as described here
Hey jockyw2001, thank you for the help.
Here is the file you asked: http://www.lgsilva.com/bk_02_0005.rar
It's a hardware problem. The wlan configuration data integrity is fine, TI chip is recognized. Maybe you should open it up and check if the wlan/BT antenna is properly connected.
Thanks jockyw2001 for your help. I'll try to check the phone but the thing is... the BT works fine. I just can't enable the wlan on the comm manager.
See first post for update (bump).
thx for your update!
Have you noticed a little battery on the board u replaced? It's right under a piece of tape. Please measure the voltage. I suspect it ran out of power on the board u replaced.
Jocky and I spent the entire day trying to resolve this wifi problem.
Unfortunately we have completely disproven your method - it is impossible for your mainboard to work with the non-original daughter board / flexcable.
This board contains your wifi components - they communicate with the main board. The main board firmware is married to the mac address of the wifi controller on your daughterboard. Unless you updated your firmware, your board would never work unless using the board that was originally delivered with the mainboard.
We spent alot of time testing this theory as you threw us off with the mis-information you provided. In the end, we needed to update this thread as it is invalid.
We are now working on tools to read the config of the wifi chip and update the firmware to re-create the married set if you ever need to change this board or your firmware gets corrupted.
I had just stopped for 24 hours, because I forgot to remove Whatsapp plus but was stopped 72 hours：哭：：哭：：哭：
And so on. In addition, there is no solution?
at&t d850 <<< new to me but running well the previous 10 days before I added my sim into it
rooted, running CM13 nightly 2016-09-24 (all updates upto 29 have same issue), it started today with the 29 update, I worked backwards to the 24, all the same problem...
Ive reinstalled every daily from 29 back to 24 and it occurs with all versions...
problem;
phone rootboots when using the phone/radio...... dialer is ok, but as soon as you press. >go (or send)<
I thought it was key combo thing, I have to hit 1 to enter into my voicemail, but any time I use the phone it reboots...
thoughts? setting or software conflict?
[Root][Guide] ZTE Spro 2 (wifi) MF97G: SuperSu, Xposed & highest brightness w/o AC
ZTE Spro 2 (wifi) model MF97G - ROOT SUCCESSFUL !
( using KingoRoot -> SuperSu)
enable developer mode by going into settings->about & pressing multiple times on SW version line.
enter developer options -> enable adb debugging.
open adb shell and run a special reboot command, as follows:
Code:
reboot disemmcwp
credit & source: hroark13 from androidforums.com
get KingoRoot, install , open and root ( I suggest you to disable the 3rd party app installation they offer )
AFAIK - it should get stuck at 90% -> wait 30 more sec, and if it's still at 90%, open adb shell and run the same mentioned special reboot command.
after reboot, your device should be rooted - so just open any app that needs root perm and Kingoroot's popup should jump asking you to allow root perm.
want SuperSu instead of kingoroot ?
root your device with KingoRoot as I describe above.
Follow all the steps from HERE - note that your device is running kitkat, most probably.
for the record, I attach a screenshot of that source as pdf, if for any reason that site will go down in the future (View attachment Replace_KingoRoot_with_SuperSU_manually_(no_script).pdf).
Source & credit: evildog2 from androidforums.com
few small notes:
ROOT STAYS AFTER REBOOT with either kingoroot & supersu
I perform it on my ZTE Spro (wifi) model: MF97G ( cell-provider-unbranded, got it from amazon )
I also managed to get XPOSED to work ! use this special manager edition from HERE
( get the upper-most version, NOT the miui version !)
elbastardo1 said:
KingRoot does a "temporary root". It usually goes away when you reboot and you need to re-root once again.
Be sure projector is off when you try to root. For some reason having the projector on prevents root.
Click to expand...
Click to collapse
*** PLEASE DO NOT QUOTE THE WHOLE POST !!!! ***---------------------------------------------------------------------------------------------
Unlocking 200 lumens in battery mode - SOLVED ! a possible solution for the SW limitation
(i.e working with the projector on HIGHEST projecting brightness w/o AC)A. ROOT YOUR DEVICE !
B. open up adb shell and run:
Code:
su
dumpsys battery set ac 1
That was the good news...
The bad are that when running this command, the Android enters battery emulation mode, so any changes to other battery data is statis from that moment, unless manually configured.
RELEX! I Have a solution!
I made a tasker's script/apk (View attachment 200Lumens_Fix.apk) that updates the battery precentage & charging status (effects the led when you really connects AC).
the app allows you to auto-run the fix after reboot - if you choose to in the app's settings.
You MUST have root to use that app!
After its installation open it up to configure & apply the fix.
( I also attach the xml source of the tasker script (View attachment 200Lumens_Fix.prj.xml) | all credit for apk generation goes to "Crafty Apps EU" tasker's dev)
UPDATE: it seems that I apply the fix for the SW limitation( that resides in /system/app/projectorsettings2.apk ) - the Spro 2 got some HW limitation as well for working on the highest projector brightness ( aka 200 lumens ) - SW speaking, my fix allows it... but after ~10-20 secs into projecting in that highest brightness, the projector stops projecting image ( but the fan continue to work as if it was working... odd ).
more research is needed in that area...
---------------------------------------------------------------------------------------------***********************************************************************
DEAR ADMINS, please note: although LP is discussed here - NO DEVELOPER is being harm from the following fix, since no payment-bypass is involved whatsoever:
the suggested "fix" simply allows the projector to run on highest brightness while on battery mode. this feature isn't exist AT ALL out-of-the-box, and it's for sure is NOT available from the manufacturer, zte, in any way - with payment or not.
That same "feature" ( highest brightness ) exist out-of-the-box only when the user connects the projector to an AC.
Lastly, as you probably know, the fix adds another file (odex) and does NOT alter in any way the original APK - so AFAIK, NO copy-write violation happens either.
Nonetheless, if the following discussion is against forums rules - please let me know
***********************************************************************No need to break the head since the 200lumens fix app I made solves it, as the spro 2 think it's connected to AC (although it isn't)
Battery mode + <15% power = projection auto-closes ?? NO MORE ! I FOUND A FIX !
do you use spro 2 without AC and it force-closes projection when battery less then 15% ?
no problem - use LP !
A. save the following code as "com.zte.newprojectsettings.txt" and put it under "/sdcard/android/data/com.android.vending.billing.InAppBillingService.LOCK/files/" and into another folder named LP ( where many other txt files found as well ).
then open LP, and use custom patch to fix the 15% limit.
note that value of "F" that marked in bold bellow is eq to 15 in hex = 15%.
so value of 5 eq less then 5% auto-projection closes... i.e you can juice out 10% more on battery while projecting !
Code:
[BEGIN]
*********************************************
* ZTE Spro 2 (wifi) MF97G *
* Allow to project with <15% battery fix *
*********************************************
[PACKAGE]
[CLASSES]
{"original":"13 04 [B][U]0F[/U][/B] 00 35 41 0C 00 63 04 8B 00 39 04 08 00"}
{"replaced":"13 04 05 00 35 41 0C 00 63 04 8B 00 39 04 08 00"}
[END]
*******************************
Patch successful
*******************************
P.S - I tried to recompile the relevant apk - but it has some protection of some kind and don't allow me to install the recompiled apk, even after the orig apk was removed&deleted.
only through LP I manage to perform fixes to that apk, I guess since it creates odex file instead of modding the apk directly.
EXPERIMENTAL - You don't need to use LP anymore !
A. root your device.
B. Download the attached ODEX zip, extract and copy the odex file to "/system/app/", reboot and the fix should be applied: <5% instead <15% projection auto-close.
( I presume you use latest official OTA update_5.zip ( aka Update (5/5/16) )
Unlock LABB !
explanation: (page 16 in pdf)
"LABB Settings = Enable, disable, or adjust the level of Local Area Brightness
Boost. The projector can adaptively brighten up areas of an image that are dim
to improve overall image quantity"
[BEGIN]
**********************************************
* ZTE Spro 2 (wifi) MF97G 2 *
* UNLOCK LABB = Local Area Brightness Boost *
**********************************************
[PACKAGE]
[CLASSES]
{"original":"38 01 06 00 14 01 08 00 03 7F 28 E6 14 01 07 00"}
{"replaced":"39 01 06 00 14 01 08 00 03 7F 28 E6 14 01 07 00"}
[END]
Click to expand...
Click to collapse
----------------------------------------------------------------------------------------------
If I managed to help you, and you wish to return the favor - you can donate .
i'm a disabled master's student for chemistry, and I worked to combine the above solutions instead of getting a good night sleep :angel:
Reserved for future updates
Reserved for future updates2
Reserved for future updates3
Thanks. Root and xposed was so much needed by me.
BTW, the kernel sources are here:
http://download.ztedevice.com/devic...urce/2/1237/MF97G_Kitkat_Kernel(3.4.x).tar.gz
So maybe a cwm/twrp is possible
Can anyone comment how long does full battery last with 200 lumens enabled?
So, how exactly should we root these things and get the 200 lumen brightness on battery fix? Edit-ok, so root with king root. How do you install the zip?
Can anyone tell me how to root the AT&T version MF97B? I need to find a way to disable HDMI out check so that I can project media from my Spectrum TV streaming app. Also like to share that I'm able to project at 200 lumens by using a rechargeable external Duracell 12V 9ah AGM (Dura12-9F2) battery with a positive/negative wire attached to a compatible connector I purchased from RadioShack. I get about 6 hours of projection time off the battery at 200 lumens, then the internal battery kicks in at 100 lumens for another 2 + hours. The battery size and weight is a bit much but still reasonably portable, but you can purchase one about half the size that's good for 3 hours of 200 lumens that is much more portable.
gps3dx said:
ZTE Spro 2 (wifi) model MF97G - ROOT SUCCESSFUL !
( using KingoRoot -> SuperSu)
enable developer mode by going into settings->about & pressing multiple times on SW version line.
enter developer options -> enable adb debugging.
open adb shell and run a special reboot command, as follows:
Code:
reboot disemmcwp
credit & source: hroark13 from androidforums.com
get KingoRoot, install , open and root ( I suggest you to disable the 3rd party app installation they offer )
AFAIK - it should get stuck at 90% -> wait 30 more sec, and if it's still at 90%, open adb shell and run the same mentioned special reboot command.
after reboot, your device should be rooted - so just open any app that needs root perm and Kingoroot's popup should jump asking you to allow root perm.
want SuperSu instead of kingoroot ?
root your device with KingoRoot as I describe above.
Follow all the steps from HERE - note that your device is running kitkat, most probably.
for the record, I attach a screenshot of that source as pdf, if for any reason that site will go down in the future (View attachment 4058637).
Source & credit: evildog2 from androidforums.com
few small notes:
ROOT STAYS AFTER REBOOT with either kingoroot & supersu
I perform it on my ZTE Spro (wifi) model: MF97G ( cell-provider-unbranded, got it from amazon )
I also managed to get XPOSED to work ! use this special manager edition from HERE
( get the upper-most version, NOT the miui version !)
*** PLEASE DO NOT QUOTE THE WHOLE POST !!!! ***---------------------------------------------------------------------------------------------
Unlocking 200 lumens in battery mode - SOLVED ! a possible solution for the SW limitation
(i.e working with the projector on HIGHEST projecting brightness w/o AC)A. ROOT YOUR DEVICE !
B. open up adb shell and run:
Code:
su
dumpsys battery set ac 1
That was the good news...
The bad are that when running this command, the Android enters battery emulation mode, so any changes to other battery data is statis from that moment, unless manually configured.
RELEX! I Have a solution!
I made a tasker's script/apk (View attachment 4061314) that updates the battery precentage & charging status (effects the led when you really connects AC).
the app allows you to auto-run the fix after reboot - if you choose to in the app's settings.
You MUST have root to use that app!
After its installation open it up to configure & apply the fix.
( I also attach the xml source of the tasker script (View attachment 4061316) | all credit for apk generation goes to "Crafty Apps EU" tasker's dev)
UPDATE: it seems that I apply the fix for the SW limitation( that resides in /system/app/projectorsettings2.apk ) - the Spro 2 got some HW limitation as well for working on the highest projector brightness ( aka 200 lumens ) - SW speaking, my fix allows it... but after ~10-20 secs into projecting in that highest brightness, the projector stops projecting image ( but the fan continue to work as if it was working... odd ).
more research is needed in that area...
---------------------------------------------------------------------------------------------***********************************************************************
DEAR ADMINS, please note: although LP is discussed here - NO DEVELOPER is being harm from the following fix, since no payment-bypass is involved whatsoever:
the suggested "fix" simply allows the projector to run on highest brightness while on battery mode. this feature isn't exist AT ALL out-of-the-box, and it's for sure is NOT available from the manufacturer, zte, in any way - with payment or not.
That same "feature" ( highest brightness ) exist out-of-the-box only when the user connects the projector to an AC.
Lastly, as you probably know, the fix adds another file (odex) and does NOT alter in any way the original APK - so AFAIK, NO copy-write violation happens either.
Nonetheless, if the following discussion is against forums rules - please let me know
***********************************************************************No need to break the head since the 200lumens fix app I made solves it, as the spro 2 think it's connected to AC (although it isn't)
Battery mode + <15% power = projection auto-closes ?? NO MORE ! I FOUND A FIX !
do you use spro 2 without AC and it force-closes projection when battery less then 15% ?
no problem - use LP !
A. save the following code as "com.zte.newprojectsettings.txt" and put it under "/sdcard/android/data/com.android.vending.billing.InAppBillingService.LOCK/files/" and into another folder named LP ( where many other txt files found as well ).
then open LP, and use custom patch to fix the 15% limit.
note that value of "F" that marked in bold bellow is eq to 15 in hex = 15%.
so value of 5 eq less then 5% auto-projection closes... i.e you can juice out 10% more on battery while projecting !
Code:
[BEGIN]
*********************************************
* ZTE Spro 2 (wifi) MF97G *
* Allow to project with <15% battery fix *
*********************************************
[PACKAGE]
[CLASSES]
{"original":"13 04 [B][U]0F[/U][/B] 00 35 41 0C 00 63 04 8B 00 39 04 08 00"}
{"replaced":"13 04 05 00 35 41 0C 00 63 04 8B 00 39 04 08 00"}
[END]
*******************************
Patch successful
*******************************
P.S - I tried to recompile the relevant apk - but it has some protection of some kind and don't allow me to install the recompiled apk, even after the orig apk was removed&deleted.
only through LP I manage to perform fixes to that apk, I guess since it creates odex file instead of modding the apk directly.
EXPERIMENTAL - You don't need to use LP anymore !
A. root your device.
B. Download the attached ODEX zip, extract and copy the odex file to "/system/app/", reboot and the fix should be applied: <5% instead <15% projection auto-close.
( I presume you use latest official OTA update_5.zip ( aka Update (5/5/16) )
Unlock LABB !
explanation: (page 16 in pdf)
"LABB Settings = Enable, disable, or adjust the level of Local Area Brightness
Boost. The projector can adaptively brighten up areas of an image that are dim
to improve overall image quantity"
----------------------------------------------------------------------------------------------
If I managed to help you, and you wish to return the favor - you can donate .
i'm a disabled master's student for chemistry, and I worked to combine the above solutions instead of getting a good night sleep :angel:
Click to expand...
Click to collapse
is that anybody help me to fix my ZTE Spro 2 problem, my projector is not switched on because of the following error "the projector light has been turned off to avoid overheating please contact zte customer service at XXXXXX" the problem is customer service cannot help me because i bought this device thru amazon, and i'm living in Kuwait. for past one year this device is just like this...is there anybody can help me???
Great work gpd3dx.
Followed the guide and successfully rooted the Spro 2 and applied the 200 lumens fix.
It works but the problem is, after reboot only low and medium brightness is available without AC power.
How do I make this 200 lumens fix permanent?
Secondly, the 200 lumens fix APK installs but when I launch it, it asks me to root the Spro2 and opens the XDA page in browser?
Root checker clearly states the Spro2 is rooted.
Confirmed ROOT working AT&T ZTE SPRO2 (MF97B)
I can confirm that the directions listed
(courtesy of member GPS3DX)
outlining ROOT instructions for Verizon's ZTE SPRO2 Projector (MF97G)
DOES INDEED WORK FLAWLESSLY
with AT&T ZTE SPRO2 Projector (MF97B)
No errors to report. Every function remains in full working order including LTE services.
Root access is permanent and does not disappear with reboot when files are replaced (as in post)
In addition, the HIGH POWER setting is now activated and working on Battery (No A/C Adapter!)
a long awaited ROOT for as all owners know ZTE has not or will not support any OS upgrades on this device.
Now we can do a few things ourselves!
*** HUGE THANK YOU TO GPS3DX FOR THIS POSTING ***
GREAT GREAT GREAT WORK!
---------- Post added at 11:38 AM ---------- Previous post was at 11:29 AM ----------
--- QUICK UPDATE: Also confirmed STORAGE now allowed to SAVE all to SDCARD. No more internal storage limits or lockouts with ROOT ACCESS.
This is crucial for as the projector seems to be running 40X faster than previously !
Should be noted that high power on battery is lost once a device reboots.
Please ROOT YOUR DEVICE but it is
Guys, I hope not to bother. But even with a successful root „KingRoot“ ZTE Spro 2 WiFi here in Germany, I get an error when I try to start 200Lumens Fix.
What am I doing wrong? Thanks in advance.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get the same thing when using the 200 lumens APK.
But if you follow the guide in the original post, you'll get 200 lumens output on battery ( without launching the APK ).
Only thing is, once you power off the device you will loose the 200 lumens on battery.
If you want it back, you will need a pc to ADB the fix again.
forcedv said:
I get the same thing when using the 200 lumens APK.
But if you follow the guide in the original post, you'll get 200 lumens output on battery ( without launching the APK ).
Only thing is, once you power off the device you will loose the 200 lumens on battery.
If you want it back, you will need a pc to ADB the fix again.
Click to expand...
Click to collapse
I am having the same problem when I try to launch the APK. I am rooted just fine but I get that exact message. How can we fix this?
Don't think you can.
It's a shame the OP doesn't reply to this thread. Maybe he could help.
It's nice to have 200 lumens on battery but a pain in the ass having to connect to a PC every time after reboot to get the 200 lumens back.
Also, Kingoroot and it's superuser app are a pain in the ass with constant popups and adverts.
I've used Titanium Backup to freeze the above two apps which solve this problem and unfreeze when I need root access.
Is there a way to automatically turn off the projector after the end of, let's say, a movie?
I tend to fall asleep and my android tablet automatically turns off its display after the end of a movie or youtube documentary.
On the good side, there is an option in the projector setting that allows for a shutdown based on a time but you are also forced to set a time for the auto turn on!!!
Recovery console
I received a device that will only boot to the recovery console. This is a Verizon one. Any chance someone has the official firmware (or the update.zip in their cache when they do a system update) that I can put on my SD card and fix it?
I use the AT&T version and I do have the mod for the high bright settings on battery though I do not lose that mod upon reboot I have had no issues with it and it has remained intact for a few months now.
mrbogusbaxter said:
I use the AT&T version and I do have the mod for the high bright settings on battery though I do not lose that mod upon reboot I have had no issues with it and it has remained intact for a few months now.
Click to expand...
Click to collapse
Which guide did you use?
I currently lose the battery mod upon reboot.
Hi you all,
So I have a Samsung Galaxy S6, a time ago the European Union rolled out a protocol that all mobile devices and mp3 players will be restricted to a maximum of 80 dB..
Does anyone know how to bypass this, we got it through a software update, ever since then my sound quality is so bad and low.. i would love a Fix for it to have the volume much higher, atleast higher then 80 dB
even when using headphones with 17 oHm, 112 dB and 17 to 20 Khz it still is to low.. cause it is restricted to 80 dB ( sounds much lower tbh)
In the phone settings there is no three dot settings for the volume output since they removed it..
I hope someone can help me!
Kind Regards,
EchoD