Database Users

Rogers and their mandatory ROM - Let's give them what they ask for ?

So Rogers is blocking internet for those who don't update to their crappy software, they check this most probably by asking our devices what version number they are using.
So why don't we just give them the version number they want? Isn't it easy to just modify a file somewhere and change the version number to match that of their latest rom ?
I'm not rom builder so I really don't know if what I'm suggestion is easy to achieve, but it sounds quite simple.
Can we do this?

That is essentially what cursordroid did in his rom

No cursordroid based his rom on the Rogers rom, what I'm suggesting is you take any 32a rom and change the version info to match that of the Rogers rom.

Naatan said:
So Rogers is blocking internet for those who don't update to their crappy software, they check this most probably by asking our devices what version number they are using.
So why don't we just give them the version number they want? Isn't it easy to just modify a file somewhere and change the version number to match that of their latest rom ?
I'm not rom builder so I really don't know if what I'm suggestion is easy to achieve, but it sounds quite simple.
Can we do this?
Click to expand...
Click to collapse
My suggestion is to just update your device! My Rogers HTC Magic (32A) was rooted prior to the installation of the new update. I ran into one problem while updating but if wasnt anything that was hard to fix. Basically what happens is that your SPL and Radio get wiped completely and then they are updated with the new Rogers HTC Magic SPL and Radio. There is no way for them to know what you are running because the update takes place in fastboot.

completely not necessary to update.
make a call to rogers, tell them you updated, but the 3g won't come back on, they'll tell you to take out the battery as they reset it for you.

cartar said:
completely not necessary to update.
make a call to rogers, tell them you updated, but the 3g won't come back on, they'll tell you to take out the battery as they reset it for you.
Click to expand...
Click to collapse
And your point being what.

FoTwoZero said:
And your point being what.
Click to expand...
Click to collapse
The 3G being enabled again..

Not sure if just getting the reset done will let you keep your data enabled as current belief is that they will continue scanning and blocking for the next while.
If you are already running a ROM with the 911 fix and want to keep it the following "seems" to work... I did this yesterday morning at still have data 24 hours later...
It is based on bcrook's work... I have seen reports that just changing out build.prop wholesale causes issues with the market so this is a smaller set of changes.
adb shell reboot recovery
***Wait for Magic to boot into recovery***
adb shell mount -a
adb shell
cd system
ls
***look for your build file, will be build.prop or build.sapphire.prop most likely***
CTRL-D ***to quit the shell***
adb pull /system/build.prop ***or whatever it was called***
***make a backup copy and edit the file***
adb push build.prop /system/build.prop
adb shell reboot
The actual changes you need to make to the file are:
ro.build.description=3.05.631.7 CL#118917 release-keys
ro.build.changelist=118917
ro.product.ua=
ro.build.fingerprint=rogers/htc_magic/sapphire/sapphire:1.5/CUPCAKE/118917:user/release-keys
ro.build.display.id=DRC92 3.05.631.7
Once you reboot your Magic, you should see the changes in Settings->About Phone under "Build Number".
Call into Rogers and get then to reset your network and you should be good.

http://www.rogers.com/HTCwaiver

[TUTORIAL] Rooting ALL Non-Sprint CDMA Heros Stuck On 1.5 From Sprint's 2.1 RUU

Before I even begin the tutorial I need to point out something:
THIS WILL VOID YOUR WARRANTY AND YOU MAY LOSE SUPPORT FROM YOUR CARRIER. THIS ALSO HAS THE POTENTIAL TO BREAK YOUR ABILITY TO UPGRADE TO YOUR CARRIERS OFFICIAL 2.1 UPDATE WHEN RELEASED
What is an RUU?
RUU (or radio unit update) is a factory restore update which will wipe your handset and re-program it. Sometimes this is done as a troubleshooting step to fix a corrupt operating system, sometimes it is done as a clean update.
How can a Sprint RUU break your ability to update to 2.1 from your carrier?
Most RUU updates include updates for the bootloader (HBOOT). HBOOT does NOT take kindly to being downgraded. If you run an RUU from Sprint then find out that the RUU from your carrier for 2.1 has an older version of HBOOT then your official RUU will fail with an error of "Main version is older!"
Why does using a Sprint RUU void my warranty or remove my carrier support?
You are removing the software which was tailored specifically for your carrier. This can have undesirable results and potentially break things. You can't expect your carrier's technical support to help you with Sprint software or with bugs because of a custom ROM from the XDA community.
Anytime you mess with your phones operating system and firmware you also have the potential to cause serious problems. DO NOT attempt this process unless you are certain you know what you are doing!
THIS SHOULD WORK ON ALL HTC HERO PHONES CURRENTLY RUNNING OS 1.5 (CUPCAKE)​
LINK IS FINALLY UP! CLICK HERE FOR THE ZIP FILE
Documents in the linked ZIP file (in the order you should use them)
Android - Setting Up ADB Access
HTC Hero - Installing Sync and Drivers
Android - Creating a GoldCard
HTC Hero - Flashing RUU from microSDHC
Android - Flashing Custom Recovery Image
HTC Hero - Flashing 2.1 ROM
Files in the linked ZIP file
HERCIMG.zip (RUU rom.zip from Sprint's latest 2.1 test build)
flash_image
recovery-RA-heroc-v1.6.2.img
READ ALL OF THE INSTRUCTIONS BEFORE YOU GET STARTED!​
DO YOU REALLY WANT A $500 PAPERWEIGHT BECAUSE YOU WERE TOO IMPATIENT TO SPEND 10 MINUTES READING?​
GETTING STARTED
There are THREE things you must have to proceed:
A CDMA HTC Hero (not a GSM version)
The ZIP file linked to above
Your MSL code*
*The MSL code is a six digit code used to access your phones programming. Some carriers use a generic 000000 or one code for all of their devices. Other carriers have an MSL which is device specific. I am NOT going to help you find your MSL code! If you don't know it, contact your carrier and ask for it or search the forum for other means of obtaining it.
Basic Setup
Complete the steps in the following guides (which are in attached zip)
Android - Setting Up ADB Access.docx
HTC Hero - Installing Sync and Drivers.docx
Before you begin following the rest of the guides in the attached ZIP file you will need to backup your PRL. PRL is the preferred roaming list and tells your phone which carriers/towers it can use. If this file is incorrect you could end up with poor service or potentially roaming charges.
WHEN YOU USE A SPRINT RUU YOU WILL END UP WITH A SPRINT PRL! YOU MUST BACKUP YOUR PRL BEFORE GETTING STARTED SO YOU CAN RESTORE IT AFTER THE RUU.
PRL Backup
(the following instructions are adapted from THIS link)
1. Download and install the latest version of QPST from HERE
2. Dial ##3424# on your Hero to put it into diagnosic mode and connect to your computer via USB
3. Open QPST Configuration and go to the PORTS tab
4. Click on "Add New Port".
5. Select the port listed as USB/QC Diagnostics (may vary, just don't use the data modem one)
6. Go to Start Clients Dropdown and select Service Programming
7. From Service Programming your phone should be selected - Click OK
8. Click "Read from Phone" and Enter MSL. Various fields should populate, don't worry about what tab you are one
9. Click "Save to File" and save to wherever you want (just remember where)
The prl will be located in the directory you saved the file in and labeled as <yourphoneesn>_sp.rl0
Advanced Tasks
Complete the steps in the following guides (which are in attached zip)
Android - Creating a GoldCard.docx
HTC Hero - Flashing RUU from microSDHC.docx
Android - Flashing Custom Recovery Image.docx
HTC Hero - Flashing 2.1 ROM.docx
EDIT:
Because the RUU file updates HBOOT before it goes on to update the system it's possible that this will invalidate your current goldcard. DON'T FREAK OUT IF THE RUU FAILS AFTER THE FIRST TWO STEPS! Just pull the battery to reboot and redo the goldcard from scratch again. You should find that this time the RUU will complete.
PRL Restore
Copy the PRL file to the root of your microSD card
Dial ##775# on the handset and enter the MSL code when prompted for password
Tap on Update PRL
If it read your microSD card correctly your PRL file should be listed in the bottom half of the screen to select
Select your PRL and click OK
Press the MENU button and tap on Commit Modifications (which will reboot the phone)

Here's a simple clean-up script attached to remove what I consider to be useless applications. I've copied the script into this thread so you can see what it will remove before you run it. If there's anything you want to keep just right click the batch file, select EDIT, then remove the line deleting the program you want to keep.
adb remount
adb shell rm /system/app/LiveWallpapers.apk
adb shell rm /system/app/LiveWallpapersPicker.apk
adb shell rm /system/app/Sprint_Core.apk
adb shell rm /system/app/Sprint_TVWidget.apk
adb shell rm /system/app/Sprint_TV.apk
adb shell rm /system/app/Sprint_Nscar.apk
adb shell rm /system/app/Sprint_Navigation.apk
adb shell rm /system/app/Sprint_NFL.apk
adb shell rm /system/app/SDSA.apk
adb shell rm /system/app/sfl-prod-release.apk
adb shell rm /system/app/Flickr.apk
adb shell rm /system/app/com.htc.MusicWidget.apk
adb shell rm /system/app/com.htc.TwitterWidget.apk
adb shell rm /system/app/HtcTwitter.apk
adb shell rm /system/app/IM.apk
adb shell rm /system/app/OMADM.apk
adb shell rm /system/app/Facebook.apk
adb shell rm /system/app/HtcFacebook.apk
adb shell rm /system/app/IQRD.apk
adb shell rm /system/app/Launcher2.apk
adb shell rm /system/app/com.htc.StockWidget.apk
adb shell rm /system/app/Stock.apk

I just threw this together this morning so it might have some errors. If you find anything that needs to be corrected please post here or PM me and I'll get to it as soon as I can.

is there a way around the htc sync / sdk conflict?

cyanfrost said:
is there a way around the htc sync / sdk conflict?
Click to expand...
Click to collapse
I've never been able to get them to play nice on the same PC. If you're planning on sticking with Android phones for a while keep the SDK on your PC and instead of using the HTC Sync application use Missing Sync.

Nevermind, I figured out the answers to my questions on my own.

Thanks for the guide. This worked perfectly. ACS wireless here. Use the attatched PRL and you can skip the qpst backup step. This should in theory work for converting a gci hero to acs, but i have not tested that.
UPDATED: Now attached is the official radio update from the ACS RUU that dropped today. Version is 2.42.01.04.23

Got it to work on my hero on GCI/AK Digitel.
I ran into a couple of problems but I was able to get around it.
The first problem I ran into was hercimg.zip wouldn't install. It installed initially and updated my hboot and radio but it would just go back to the hboot menu every time it would extract and check. I finally got it to install after removing my battery during the green htc logo then going into hboot. I tried re-creating the gold card and formatting my sdcard but I couldn't get it to work until the battery got pulled on the htc logo which I did on accident.
The second problem I had was when I was installing the custom recovery image. I tried both methods in the tutorial but it wouldn't work in the end I had to follow the How-To repair your bootloader after using the 2.1 RUU tutorial at androidcentral and it work out great
But now I am rooted and running fresh 2.1.1 so everything is great!!!
Thanks for the tutorial!!!

Thanks
Thanks for all the hard work on this, but it would be nice if you posted document files that do not require office 2007 or better as I do not have it or want it. Plain old text works great and is quite cross platform and document viewer compatible.

Damn! Wish this was here before I rooted a month ago! lol.

Thank you very much for the work you put into this awesome post!!! After reading it over and over I am ROOT!!!!! I really want to thank YOU, ipfreelytech, and d-shade for the help you guys gave me. Now I'm off to flash!
Thanks guys!!!!!!

was looking for this tutorial, thanks!

These can be opened in pages on a mac, or in openoffice on linux or windows. you could also download a viewer. Seems like a really stupid complaint as he put A LOT of effort into this and you can't download a viewer?
webfeind said:
Thanks for all the hard work on this, but it would be nice if you posted document files that do not require office 2007 or better as I do not have it or want it. Plain old text works great and is quite cross platform and document viewer compatible.
Click to expand...
Click to collapse

I wish I found this before giving up a week ago!

sorry for being a noob but if i rooted a long time ago using a sprint ruu (i think it was like 1.5 something) (also im on cellular south) and have successfully been rooted for awhile can i update to 2.1 by following this guide?

if you already have root, just flash a 2.1 rom from your recovery console. I'd reccommend flashing a newer recovery image if you haven't done so. but there is no reason to go through all this BS if you have root. to get updated baseband you can flash my radio update i pulled from the ACG RUU or you can flash the signed sprint radio update thats floating around here.

A very important step is missing here....Backup before installing the new ROM (as the phones comes from your company)... specially since this post is targeted to Non-Sprint CDMA and there is no way to RUU back to Non-Sprint; no RUU available, right?

I don't understand what your saying here. you CANNOT backup the stock 1.5 rom, there is simply no way. you can use mybackup to backup system settings and apps on a non rooted phone.
Now that there are 2.1 ruu for non sprint carriers; if for some reason you wanted to take it back to stock and screw yourself out of root for as long as you have the phone you can just flash the RUU from your carrier. The ACG ruu is many versions newer than the sprint ruu so overwrite is not a problem. once again i don't know why anyone would do this.
bicione said:
A very important step is missing here....Backup before installing the new ROM (as the phones comes from your company)... specially since this post is targeted to Non-Sprint CDMA and there is no way to RUU back to Non-Sprint; no RUU available, right?
Click to expand...
Click to collapse

ipfreelytech said:
I don't understand what your saying here. you CANNOT backup the stock 1.5 rom, there is simply no way. you can use mybackup to backup system settings and apps on a non rooted phone.
Now that there are 2.1 ruu for non sprint carriers; if for some reason you wanted to take it back to stock and screw yourself out of root for as long as you have the phone you can just flash the RUU from your carrier. The ACG ruu is many versions newer than the sprint ruu so overwrite is not a problem. once again i don't know why anyone would do this.
Click to expand...
Click to collapse
Thanks for pointing out that in no way you can return back. Non-Sprint Heros users using those ROMs that are all over here, suffer from lack of voicemail notifications.
If your Non-Sprint company has no RUU, THEN DO NOT ROOT your phone if you want to keep voicemail notifications. No backup possible, point of no return! Good advice? ...or Non-Sprint Heros can get voicemail notifications in particular ROM? ...or using an app?
Answering your question about why would you want to go back... To get back your voicemail notifications... or otherwise, keep calling your voicemail, lest say, every 30 minutes.. just to know if you have voicemail.

voice-mail notification is only broken on roms that are based of the sprint RUU. the zen (tmobile mytouch 3gslide port) has working voice mail notification. as do the AOSP based roms such as buufed.
you cannot get a voicemail without a missed call unless your phone is off. so you only would need to check after a missed call.
at one point i was trying to make a rom from the 2.1 update that was used by a bunch of carriers including mine, nothing special just add superuser, but it didn't go well and haven't figured out what went wrong, and lost interest because I started using buufed. The rom booted but didn't have a proper version in the about software. also the mobile radio didn't work nor did wifi.
bicione said:
Thanks for pointing out that in no way you can return back. Non-Sprint Heros users using those ROMs that are all over here, suffer from lack of voicemail notifications.
If your Non-Sprint company has no RUU, THEN DO NOT ROOT your phone if you want to keep voicemail notifications. No backup possible, point of no return! Good advice? ...or Non-Sprint Heros can get voicemail notifications in particular ROM? ...or using an app?
Answering your question about why would you want to go back... To get back your voicemail notifications... or otherwise, keep calling your voicemail, lest say, every 30 minutes.. just to know if you have voicemail.
Click to expand...
Click to collapse

[Q] "Android SDK Platform-tools, revision 1"

Hi im new, i wanted to root my new g2 i got last week. I thought i could do it in a day but with going with the gfree process i realized i need to study somethings first. So today im just going to install the android sdk on my computer. In the cyanogenmod wiki it says when launching the sdk manager only get this package "Android SDK Platform-tools, revision 1". The only one i see closest to it says "Android SDK Platform-tools, revision 2". So in seeing that i stopped there & came here.
Can i use this "revision 2"? Another question: I also saw that its telling me to downgrade the firmware to 1.34.707.3. In Settings>> About phone it says my build number is 1.22.531.8 cl277427. this means i don't have to downgrade the firmware correct? (i'm a little confused why my phones build # is lower. i got it last week. shoudn't be higher?)
any help is appreciated

You no longer need to mess with the SDK or using ADB to root. You can do it all by putting the proper files on your SD card and using Terminal Emulator on your phone to run the commands. Look it up in the wiki and development forum, but many people are using THIS method to root without ADB, though theoretically you could use the other root methods as well without ADB.
For this application of just perm-rooting, all ADB is doing is placing the files in the correct locations and running the commands. You can easily manually put the files in the correct locations via mounting the SD card to your computer, then run these commands from the phone. I'd recommend doing it this way to save you some time and confusion, unless of course you plan on using the SDK later on for further development.
Downgrading your firmware pertains to the Desire Z (Euro version of the G2). No downgrading is necessary for the G2. All you need to do is make sure that you use the appropriate '.ko' file depending on if you have the OTA update on your phone or not. At this point I'd be surprised if you didn't but be sure to check.

A small weight has been lifted of my shoulders...thanks

daddydise said:
A small weight has been lifted of my shoulders...thanks
Click to expand...
Click to collapse
Yep. Good luck.

[H815] V20a-SEA-XX KDZ

Stock KDZ retrieved from LG Bridge cache. If you're not sure if this is the right version for your device, then it probably isn't. Bricks are bad.
Flash using LG Up from here: http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803
Android version: 6.0
Kernel: 3.10.84
Baseband: MPSS.BO.2.5.c3-00101-M8992FAAAANAZM-1.31581.1
Build number: MRA58K
Filename: H81520a_00_1202.kdz.zip
Model: LG-H815
Model Region: SEA (South-East Asia)
MD5 (H81520a_00_1202.kdz) = 4f3243c301fb7177baa923918d9805da
MD5 (H81520a_00_1202.kdz.zip) = e55039fa1dea8ecc3135ccf29bce3fb5
DOWNLOAD: https://drive.google.com/file/d/0B1qI_SMCg6P9bUJkbWN3SjNidGs/view?usp=sharing
No idea what performance is like relative to previous versions.
If anyone can mirror this to somewhere other than Google drive, please let me know and I'll add a link.

saw this on my lg bridge but not installing due to xposed. can anyone create deodex version like @paratox did here?
http://forum.xda-developers.com/g4/themes-apps/h815-mm-v20b-deodexed-apps-xposed-t3258980

Used this KDZ from the OP to update my G4 H815 (SEA) via LG UP. It worked without a hitch. Thanks.

thx for the links
what do u guys think about trying this on H815L ???

willy792003 said:
saw this on my lg bridge but not installing due to xposed. can anyone create deodex version like @paratox did here?
http://forum.xda-developers.com/g4/themes-apps/h815-mm-v20b-deodexed-apps-xposed-t3258980
Click to expand...
Click to collapse
LG Bridge do not show me a new update. Any idea why?

i have an h815 SEA, but i didn't upgrade yet because the root, somebody has update and rooting? can i unlock the bootloader if update to MM? i have the unlock.bin from lg to ublock it but i didn't do it yet

I selected Upgrade in LGUP not Refurbish. No wipe to my data was made. Working great with the KDZ posted by OP.

manojsuper said:
Is knock code included in this update?
Click to expand...
Click to collapse
Yup. See SS.

Anyone having significant battery drain? It has been great except for that.
Edit: Factory reset seems to have fixed the drain.

Carl24 said:
LG Bridge do not show me a new update. Any idea why?
Click to expand...
Click to collapse
See the following thread here - https://m.reddit.com/r/lgg4/comments/3xags1/solution_to_use_mac_lg_bridge_update_mm_for_lg_g4/. Basically, the update isn't showing in the current version of LG Bridge for PC but is for OS X. However, you have to rename the update file before it will update successfully under OS X.

atm1991 said:
See the following thread here - https://m.reddit.com/r/lgg4/comments/3xags1/solution_to_use_mac_lg_bridge_update_mm_for_lg_g4/. Basically, the update isn't showing in the current version of LG Bridge for PC but is for OS X. However, you have to rename the update file before it will update successfully under OS X.
Click to expand...
Click to collapse
Already updated via kdz posted by op.

atm1991 said:
See the following thread here - https://m.reddit.com/r/lgg4/comments/3xags1/solution_to_use_mac_lg_bridge_update_mm_for_lg_g4/. Basically, the update isn't showing in the current version of LG Bridge for PC but is for OS X. However, you have to rename the update file before it will update successfully under OS X.
Click to expand...
Click to collapse
Tried the shell steps:
sudo su
find /private/var/folders -name 'com.lge.LG-Bridge' -print
# /private/var/folders/rb/4p3g8l0s4hdcmdqzzf315zmr0000gn/T/com.lge.LG-Bridge
cd /private/var/folders/rb/4p3g8l0s4hdcmdqzzf315zmr0000gn/T/com.lge.LG-Bridge
cd temp
ls
# H81520a_00_1202.kdz&e=1450509232&h=7dd3f68c07e...
# H81520a_00_1202.kdz&e=1450531124&h=5e804bfab3e...
# H81520a_00_1202.kdz&e=1450531828&h=afc4d98d95d...
# LGUP_8994.dylib
mv H81520a_00_1202.kdz&e=1450531828&h=afc4d98d95d... H81520a_00_1202.kdz
But after used the mv command, i get this error:
bash-3.2# mv H81520a_00_1202.kdz&e=1451218153&h=fb25b649393559b6a554eafd7214155e H81520a_00_1202.kdz
[1] 873
bash: amp: command not found
usage: mv [-f | -i | -n] [-v] source target
mv [-f | -i | -n] [-v] source ... directory
[2] 875
bash: amp: command not found
[1] Exit 64 mv H81520a_00_1202.kdz
[2] Done e=1451218153
bash: H81520a_00_1202.kdz: command not found
Any hints?
Edit: Fixed with the open . command

@willy792003: Go for it and then install Genisys Rom. Working Xposed included - just saying. Working fine.

Updated to this ROM on Starhub LG G4 H815 singapore with LGUP. Was very unresponsive and laggy. Was not able to receive any calls.
Took backup and did a factory reset. Now its fine. So i guess clean install is the way to go
Although i feel touch responsiveness is somewhat worse in MM when compared to LP ROM.

You done the update with LG Bridge? Still no update seen for Singtel set.
Anyone knows how to change the CSC on the G4 like we can do so on the Samsung phones through the service menu? Can't seems to find the option in the G4 service menu.

FWIW - I did a dirty upgrade and have had no issues, battery life is roughly the same as pre-upgrade and all is stable.

I got the update today for V20b via OTA.

Carl24 said:
I got the update today for V20b via OTA.
Click to expand...
Click to collapse
wow how did you get it? I just check haven't received it yet

snaketooth2007 said:
wow how did you get it? I just check haven't received it yet
Click to expand...
Click to collapse
I also received it today; Just go to about phone, update center, software update and check for update.

reiko09 said:
I also received it today; Just go to about phone, update center, software update and check for update.
Click to expand...
Click to collapse
I don't know I been trying that but it said I'm still up to date. I'm also fully stock no modification at all.

US Model (x727): need dmesg / logcat and other stuff, root not necessary

Thanks guys, I have what I needed!
Hi, I'm wondering if someone with a Le Pro3 US model (x727) could please provide me with the output for dmesg, logcat and some other things.
Pre-requisites:
have adb installed and working for your device
Make sure adb debugging is on for your device, and your computer recognizes your device, and is authenticated for your device. (I don't know EUI, I've only ever dealt with western AOSP/CAF style roms, you'll have to understand and manage this all yourself).
PLEASE don't type the commands from memory, they have case sensitive options. Please copy and paste them. Thank you.
The following commands need to be executed shortly after fresh reboots. Please don't run them if the device has been on longer than a minute. In fact, please don't stray far from the procedure... please.
Reboot device
Once booted run "adb shell dmesg > dmesg.txt"
Run "adb shell cat /proc/partitions > partitions.txt"
Run "adb shell df > df.txt"
Run "adb shell mount > mount.txt"
Reboot the device and perform the next adb step once it's started to boot
run "adb logcat > logcat.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Reboot the device and run the following once it's started booting back up
run "adb logcat -b radio > logcat-radio.txt"
Press "CTRL-C" to stop logging about 30 seconds after the device has settled and connected itself to the cellular network
Now, the following will likely fail without root, but we'll try for them anyway. Who knows, this might work out:
Run "adb shell ls -la /dev/block/bootdevice/by-name > by-name.txt"
Run "adb shell ls -la /dev/block/bootdevice/by-num > by-num.txt"
Note: None of these commands will produce empty files. If you get empty files, something went wrong. If only a few are empty and you can't seem to get them working properly, just send me what you do get.
Once you've done these things, zip up the files and send them to me in a private message. You don't want these posted here unless you want people knowing your phone number. The text files, especially for the logcat and radio output will be large, but they should compress down to something quite reasonable. Also, please make sure to include your model number so I know which I'm working with. Thanks much.
Thanks.

I can do this for you a bit later today.

Guys, anything? You people want development but can't take time to answer questions....

dr4stic said:
Guys, anything? You people want development but can't take time to answer questions....
Click to expand...
Click to collapse
Don't have my phone yet. If you don't get it by Tuesday I'll gladly help you from that point on. Unfortunately I'm 5 days from the west coast shipping wise.

dr4stic said:
Guys, anything? You people want development but can't take time to answer questions....
Click to expand...
Click to collapse
I have the x720 (chinese) and not the x727 (US) version.
If you are still interested in the data, I will be more than happy to send it to you.
In the meantime, if you are interested in the partition layouts, I've already posted some details about it here: [REF] LEX720 - 64GB - Partition infos
[edit1]
I just sent you a PM.
[/edit1]

I think LeEco has disabled adb service as well. adb is not detecting the device. I installed terminal emulator and the device and checked for adbd process, but could not find it running even after enabling USB debug. Looks like the device is completely locked out

I can only speak for the chinese version (x720), but my device came with an unlocked bootloader and adb and fastboot are working perfectly fine here.

Yeah, chinese version is unlocked. I was talking about the US version that I got yesterday. It was a complete disappointment

Thanks guys, I appreciate the help!

androcheck said:
I have the x720 (chinese) and not the x727 (US) version.
If you are still interested in the data, I will be more than happy to send it to you.
In the meantime, if you are interested in the partition layouts, I've already posted some details about it here: [REF] LEX720 - 64GB - Partition infos
[edit1]
I just sent you a PM.
[/edit1]
Click to expand...
Click to collapse
How does using the Chinese version work out for you in the US. I'm thinking about returning my US version and getting a Chinese one so I can unlocked BL. Looks like the Chinese one supported all of the same LTE bands in the US, but I could be wrong.

benjmiester said:
How does using the Chinese version work out for you in the US. I'm thinking about returning my US version and getting a Chinese one so I can unlocked BL. Looks like the Chinese one supported all of the same LTE bands in the US, but I could be wrong.
Click to expand...
Click to collapse
I am not located in the US, but in Austria (Europe) and it works perfectly fine here. (Also supports LTE band 20/800 MHz, which is used here in Europe and often missing in phones made for the chinese market, so I'm perfectly happy with it.)

androcheck said:
I am not located in the US, but in Austria (Europe) and it works perfectly fine here. (Also supports LTE band 20/800 MHz, which is used here in Europe and often missing in phones made for the chinese market, so I'm perfectly happy with it.)
Click to expand...
Click to collapse
Same in Spain.
Enviado desde mi LEX720 mediante Tapatalk

androcheck said:
I am not located in the US, but in Austria (Europe) and it works perfectly fine here. (Also supports LTE band 20/800 MHz, which is used here in Europe and often missing in phones made for the chinese market, so I'm perfectly happy with it.)
Click to expand...
Click to collapse
Oh sorry, thought you were since you had the US one too.

benjmiester said:
Oh sorry, thought you were since you had the US one too.
Click to expand...
Click to collapse
No problem. But I also never had the US version..