I attempted to use this ROM: [4.2.2][OFFICIAL] LiquidSmooth v2.3 - d2vzw|d2usc - 05|04|13
http://forum.xda-developers.com/showthread.php?t=2148261
Summary:
The android phone process crashed whenever I would try to make a phone call.
The Wifi Tether did not work. It would fail to start the Access Point (AP).
Specifics:
com.android.phone process kept crashing while making calls. It would ring, crash, then disconnect the call.
Wifi tether would not work with the Wifi Tether TrevE Mod - WifiTether-TrevE_Mod_11_22_2012_driverReload2
http://forum.xda-developers.com/showthread.php?t=1988735
My wifi tether settings were:
Galaxy S3 - Netd-ndc with driver reload
-Device-Profile: Leave this on auto (default)
-Netdndc Max Client Cmd: Required for GS3ish devices. If not enabled you will likely get an AP but cannot connect.
-MSS clamping: on (default)
-Routing fix: on (default)
The wifi tether application would fail to start the Access Point (AP). I was indeed using SuperSU which I had to install manually since LiquidSmooth comes with SuperUser by default.
I recently updated my modem and rpm to:
Baseband version: I535VRMBM1
This modem update was done after checking to see if the Wifi Tether would work but before I had tested the phone calling function.
If there is anymore information that would be useful let me know and I will update.
Thanks everyone!
I have a Motorola Droid X2 with MyMobiler. However, when I connect it to the computer w/ via Wifi, it just gives me a black screen with something that goes like "Press Ctrl+Space" and "Change Keyboard (F4). I have tried all possible solutions: Android - [Setup Device] - [Display] - [Display] - [1. or 2. or 3.]
AND
Android - [Setup Device] - [Display] - [Page]
AND
Android - [Setup Device] - [display] - [display] - [3. Other]
And when I use USB, it does not even detect the phone, even when the phone is ready and connected to the computer.
Somebody please help!
Hello,
I've flashed my Xperia L once or twice some time ago, now I just wanted to try out some of the new goodies, not just stay on the cursed 4.2.2. I have it all set up correctly software-wise, yet whenever I run Flashtool (version 9.19.8( and try to Volume-Down connect my phone, it get's problematic. Yeah, the phone does connect in flash mode, yet after a couple dozen seconds it simply disconnects as if I had manually unplugged it. Phone restarts and gets connected to PC the standard-way.
Now, is it that Flashtool automatically cuts off the connection after some time, or my cable or socket(s) are faulty? I thought it had something to do with having moved cable a tiny bit and connection being lost but now, I have tried again, ensuring no movement will be involved and it just disconnected again. I did also check all my laptop's USB ports, also bought a USB HUB and checked it. Did check two different cables, one for some Nokia, I think, no results.
Here's flashtool log.
Code:
18/043/2017 15:43:31 - INFO - Device connected in flash mode
18/044/2017 15:44:32 - INFO - Device disconnected
18/045/2017 15:45:22 - INFO - Device connected with USB debugging on
18/045/2017 15:45:22 - ERROR - root : this bundle is not valid
18/045/2017 15:45:23 - INFO - Connected device : Sony Xperia L
18/045/2017 15:45:23 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
18/045/2017 15:45:23 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-g74b701b-00054-gde56c65-dirty / Build number : 15.3.A.1.17
18/045/2017 15:45:23 - INFO - Checking root access
18/046/2017 15:46:04 - INFO - Root Access Allowed
18/046/2017 15:46:04 - INFO - Stopping ric service
18/046/2017 15:46:20 - INFO - ric service stopped successfully
Any ideas?
Renagrds,
Greg
Gregoric said:
Hello,
I've flashed my Xperia L once or twice some time ago, now I just wanted to try out some of the new goodies, not just stay on the cursed 4.2.2. I have it all set up correctly software-wise, yet whenever I run Flashtool (version 9.19.8( and try to Volume-Down connect my phone, it get's problematic. Yeah, the phone does connect in flash mode, yet after a couple dozen seconds it simply disconnects as if I had manually unplugged it. Phone restarts and gets connected to PC the standard-way.
Now, is it that Flashtool automatically cuts off the connection after some time, or my cable or socket(s) are faulty? I thought it had something to do with having moved cable a tiny bit and connection being lost but now, I have tried again, ensuring no movement will be involved and it just disconnected again. I did also check all my laptop's USB ports, also bought a USB HUB and checked it. Did check two different cables, one for some Nokia, I think, no results.
Here's flashtool log.
Code:
18/043/2017 15:43:31 - INFO - Device connected in flash mode
18/044/2017 15:44:32 - INFO - Device disconnected
18/045/2017 15:45:22 - INFO - Device connected with USB debugging on
18/045/2017 15:45:22 - ERROR - root : this bundle is not valid
18/045/2017 15:45:23 - INFO - Connected device : Sony Xperia L
18/045/2017 15:45:23 - INFO - Installed version of busybox : BusyBox v1.20.2-jb static (2012-11-25 17:47 +0100) multi-call binary.
18/045/2017 15:45:23 - INFO - Android version : 4.2.2 / kernel version : 3.4.0-g74b701b-00054-gde56c65-dirty / Build number : 15.3.A.1.17
18/045/2017 15:45:23 - INFO - Checking root access
18/046/2017 15:46:04 - INFO - Root Access Allowed
18/046/2017 15:46:04 - INFO - Stopping ric service
18/046/2017 15:46:20 - INFO - ric service stopped successfully
Any ideas?
Renagrds,
Greg
Click to expand...
Click to collapse
First of all, you should check this thread:
https://forum.xda-developers.com/showpost.php?p=70833785&postcount=304
There, I've said that you should just use older versions of flashtool for XL, like v0.9.18.4 !
If it doesn't solve your problem, then you should flash the ROM , right after you connect the phone to pc, as fast as you can!
And note that if it disconnects again, do nothing, just unplug the phone and wait untill the progress bar is completed and rom is prepared for flashing, then it again asks to connect the phone, and you connect it and wait untill it Finnishes
It happened for me too, and with this method, I've flashed the ROM successfully!
WIFI BONDING FIX (r5x)
Description :
By default, Realme devices provided an ini file to control the wifi behavior. For (r5x) it appears that Realme somehow messed up a driver flag in WCNSS_qcom_cfg.ini causing 40 MHz channel in either 2.4Ghz/5Ghz unsupported.
However after tinkering with WCNSS_qcom_cfg.ini I fixed the flag and with my testings, I have successfully run both 2.4Ghz/5Ghz at 40Mhz.
Info :
- Fixes Slow WiFi Network
- For r5x (5/5i/5s/NFC)
Notes :
- A Must Flash Item For r5x (All ROM's)
How To Use :
- Hit Recovery
- Mount System Vendor
- Flash Reboot
Download
Credits :
- Me For The Fix
- @shygos_strn for covering up my lazyness
is realme 5 pro included? I've tried it and still getting 65mbps on realme 5 pro, it's not working
Hi,
No phone, but router So i have a GL-MiFi router, which has lost its flash IC (that was a long journey).
The main problem is
- The router had a W25Q128FVS... flash
- Now i have W25Q128JV-xM , which is different (does not work) - and a 8MB W25Q64 , which is too small
- The Openwrt image is only 5,2MB
- I can flash U-Boot to the 8MB flash. It boots.
- But as soon as i save the environment or flash an Openwrt , the content turns into garbage (the U-Boot is working, but the environment turns into barbage and Openwrt cannot be started from flash - however, Openwrt works from TFTP.
...does anyone know, how to
- build U-Boot for a device with W25Q128JV-xM support?
- build it fro SD card support (the router has SD card)
- or define the partitions for the smaller flash?
- or where i can ask these?
Thanks in advance for all replies