yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario ROM Development] zabardast_1:
Download WST Tool run and apply the button marked "CID Action" to verify the CID locked/unlocked status,if it reports 'locked' reread the guide again or check out this excellent guide to use lokiwiz02b method correctly:-

http://xdaforums.com/showthread.php?t=285435

Cheers :)
[8125, K-JAM, P4300, MDA Vario ROM Development] DiCham:
@zabardast_1 : I downloaded the lokiwiz02b but still get the error: "path not found"! :(

Please tell me where can I download the WST Tool (I tried to search but couldnot find).

Now I will re-run progress again... May get result within 1 hour... hope it's OK!

I will report later...
[8125, K-JAM, P4300, MDA Vario ROM Development] DiCham:
OK now... I found the bug:

For anyone meet the same error (path not found), right click at lokiwiz.bat to edit (default with NotePad) and add "\" infront of commands

\Utils\pdocread.exe -n 1 0x000000 0x10000 -b 0x4000 lock_backup.bin

\Utils\wizardunlock.exe lock_backup.bin -nolock -w unlocked.bin

\Utils\pdocwrite.exe -n 1 -b 0x4000 unlocked.bin 0x000000 0x010000

\Utils\preboot.exe

of each part "C", "U", "L". Just to tell Windows knows exactly where to find executeable file. This is a DOS batch command, a very old command of MicroSoft! :)

Now I'm upgrading ROM to T-Mobi 2.26 as instruction.... Thanks all!

For newbie (as me): if you do it right, your command windows should be like this

But what version of WM6 is the best for me? Many WM6 ROM out there and I read wiki but cannot mae decision what version should I use... Can anyone please tell me...
[8125, K-JAM, P4300, MDA Vario ROM Development] mestrini:
Are you sure you CID unlocked your phone? Be careful!!

I believe i saw you mentioning IPL/SPL 2.21 and with that values you can't CID unlock the phone...
[8125, K-JAM, P4300, MDA Vario ROM Development] DiCham:
Eh... I really dont know exactly my phone unlocked or not, but after run Lokiwiz.bat (in fact it's run 4 .exe file with parameter), I got that window result. Now I'm in WM6 TNT (as in my signature) and the phone working after upgraded.

When I opened this Help topic, draven187 and zabardast_1 advised me to re-do from the beginning and I did it carefuly followed "How to .... little tutorial": downgraded to 1.xx, upgraded to T-Mobi 2.26, unlocked phone and unlocked CID (that DOS window), upgraded to WM6 TNT.

But it's seems there's something wrong now: the phone booting procedure is very very slow (4-5min stop on Windows welcome screen), may be caused by installed Resco File Explorer 5 and SpbPlus. But when it booted, phone running fast. I think I should try the TNT 5.0....
[Android Software/Hacking General [Developers Only]] ma777:
Hey XDA,

Finally took the leap and started doing a little developing. I have successfully setup Linux, a build environment, and compiled a custom CWM recovery for my device. I noticed some things along the way that made me very weary of actually flashing it.

Here is some of my output:

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.2.2

CM_VERSION=10.1-20160720-UNOFFICIAL-q80

TARGET_PRODUCT=cm_q80

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-4.4.0-28-generic-x86_64-with-debian-stretch-sid

HOST_BUILD_TYPE=release

BUILD_ID=JDQ39E

OUT_DIR=/home/lin/cm-10.1/out

============================================

Platform version = Android Version right? This is building for Kit-Kat so I cant use this on my device.? My Target_ARCH_Variant is armv7-a-neon is this okay to use with Krait?

Here is my target device specs:

MSM8974 Krait ARMv7

Android 6.0.1

ADB rooted, I’m having issue getting SU to work properly on the device.

Build Number says dev-keys at the end what does this mean?

I attempted to re-flash my clean stock recovery pulled from the device as a test run and can’t even get that to work. Since my build says dev-keys does that mean that the keys are located somewhere on the device so I can sign an update.zip that will flash through the stock recovery? AFAIK there is no ODIN-like tool or download mode I can get into. I have the flash_image binary on the device. When I run flash_image recovery /sdcard/recovery.img I get this message:

“Error scanning partitions: No such file or directory”

Are there any other options to flash my recovery.img? My recovery partition is located at mmcblk0p20. I have been out of the loop for a while now. Is CMW recovery dead these days? (Yes)The guides I'm using are probably pretty old as well. Been having a lot of fun so far but I seem to have hit a wall. Any help would be appreciated.

EDIT: I think i found a way to flash the recovery image back to the device. I put the phone into a mode where it enumerates as a Qualcomm MMC device and a bunch of drives. On my computer i went into root@me:/dev and noticed a partition named sdc20. I did a DD and then cmp -b sdc20.img recovery.img. It returned no differences between the two files.

Update: After looking at the two files in a hex editor I went ahead and flashed it. To my surprise it booted CWM recovery. Only problem is that I can't mount any partitions. After a reboot, recovery-from-boot.p did it's job and flashed back my stock recovery. Now I don't have to worry about damaging anything. I guess CWM won't work properly on newer devices...Off to building TWRP it is:good:

Thanks!
[Sprint Samsung Galaxy S6] crazynapkinman:
Is there a working xposed configuration for our device?
[Sprint Samsung Galaxy S6] koop1955:
What [MENTION=5241571]Saafir[/MENTION] said and we are Arm64.
[Sprint Samsung Galaxy S6] DrakeLyon:
I didn't know we needed some sort of unofficial version of Xposed for the Sprint S6. A couple of weeks ago all I had to do was download the latest Xposed and flash it with TWRP and it worked like a charm.

EDIT: lol gosh, nevermind. I chose the latest "wanam" version, that's why it worked.
[Sprint Samsung Galaxy S6] crazynapkinman:
Thanks for the inout from everyone!

Now, what modules are you all running? I have taken youtube adaway. Nit sure what else to get. Lookibg for battery life and UI mods.

Also, wheb i try to reboot via framework, it gives me a busybox error. Should I try to install busybox from the app store and then try?
[Xposed General] Recognized Noob:
Log:

07-20 18:37:37.225 I/Xposed ( 367): -----------------

07-20 18:37:37.225 I/Xposed ( 367): Starting Xposed version 86, compiled for SDK 22

07-20 18:37:37.225 I/Xposed ( 367): Device: MI 3W (Xiaomi), Android version 5.1.1 (SDK 22)

07-20 18:37:37.225 I/Xposed ( 367): ROM: omni_cancro-userdebug 5.1.1 LYZ28E eng.rooque.20150628.013117 test-keys

07-20 18:37:37.225 I/Xposed ( 367): Build fingerprint: n/a

07-20 18:37:37.225 I/Xposed ( 367): Platform: armeabi-v7a, 32-bit binary, system server: yes

07-20 18:37:37.225 I/Xposed ( 367): SELinux enabled: yes, enforcing: no

07-20 18:37:37.225 D/XposedStartupMarker( 367): Current time: 1469020057, PID: 367

07-20 18:37:37.225 I/Xposed ( 367): -----------------

07-20 18:37:37.225 I/Xposed ( 367): Starting Xposed version 86, compiled for SDK 22

07-20 18:37:37.225 I/Xposed ( 367): Device: MI 3W (Xiaomi), Android version 5.1.1 (SDK 22)

07-20 18:37:37.225 I/Xposed ( 367): ROM: omni_cancro-userdebug 5.1.1 LYZ28E eng.rooque.20150628.013117 test-keys

07-20 18:37:37.225 I/Xposed ( 367): Build fingerprint: n/a

07-20 18:37:37.225 I/Xposed ( 367): Platform: armeabi-v7a, 32-bit binary, system server: yes

07-20 18:37:37.225 I/Xposed ( 367): SELinux enabled: yes, enforcing: no

07-20 18:37:40.345 E/Xposed ( 367): Found /data/data/de.robv.android.xposed.installer/conf/disabled, not loading Xposed
[Xposed General] venereo:
Delete /data/data/de.robv.android.xposed.installer/conf/disabled
[Xperia Z Q&A, Help & Troubleshooting] petmix:
Hello,

it would be verry appreciated, if someone could help me with answering the following question.

I've read on this forum, that the Xperia Z has a sharp LS050T1SX01 or an AX450AKN-7 lcd.

I have an original broken LS050T1SX01 lcd, which I want to replace. The cheapest soruce would be buying an xperia replacement lcd on ebay. But looking at the pictures of the lcd assembly, the cabling is very different from the original LS050T1SX01 cabling.

So the question is: does the xperia lcd has a different cable (and socket) then the original LS050T1SX01 ?:confused:

(based on the pictures yes, but it is also possible, that the original cable is connected to an extender, which can be seen in the pictures).

Thank you
[Moto G 2015 Q&A, Help & Troubleshooting] amarc78:
I ported a 6.0.1 Moto G3 stock ROM to the Moto E 2015. Everything works amazingly great except the camera at the moment. My only other problem is no matter what I change in the build.prop I can't get the model name changed from Moto G 3 to Moto E 2015. Normally it is simply the line ro.product.model=XXX but it must be reading it from somewhere else. If anyone could tell me I would be very greatful.
[Miscellaneous Android Development] Nayeem Hossain:
Hi every whats up??

today am going to share saome klitkat based custom rom for Micromax A092,Symphony W70Q and Mito A310

I dont know all the rom developers who those roms.If you see my post please infrom me :)

So lets do it :D

You will need custom recovery install in your phone

I will provite Twrp recovery because it is best of all

TWRP Recovery

https://drive.google.com/file/d/0B5FI_PeZ3xaEeWZIMk5lQW9Tejg/view?usp=sharing

1.W70Q KITKAT UPDATE

https://docs.google.com/uc?id=0B5FI_PeZ3xaEQ2NEYzZDS1E0LVk&export=download

2.Crdorid

https://docs.google.com/uc?id=0B5FI_PeZ3xaEdUhldC1hbV9xZGs&export=download

3.Carbon

https://docs.google.com/uc?id=0B5FI_PeZ3xaEa3RmRG1YRWpfeXc&export=download

4.Pacman

https://docs.google.com/uc?id=0B5FI_PeZ3xaEYnZtZlFnUkhRWnc&export=download

5.Ehndroix

https://docs.google.com/uc?id=0B5FI_PeZ3xaEcFdUWU5JbzVxV3c&export=download

6.Mokee

https://docs.google.com/uc?id=0B5FI_PeZ3xaEbFpQblFIUEt5ejA&export=download

7.FIUI

https://docs.google.com/uc?id=0B5FI_PeZ3xaEVGdORGxlbklMRG8&export=download

8.CM 11

https://docs.google.com/uc?id=0B5FI_PeZ3xaEdEkwYVNTQzdPcWM&export=download

Note Storage bug is fixed

INSTRUCTION TO FLASH ROM AND UPGRADE:

1.You must have a custom recovery on Your device

2.If you have already flashed custom recovery, then only proceed

3.Wipe data/factory reset in recovery

4.Flash ROM from Kitakat Update from sdcard

5.For cm based rom do the same

6.Reboot and enjoy

INSTRUCTION TO DOWNGRADE:

1.Dewnload Any 4.3 badsed rom

2.Reboot To recovery

3.Go to wipe>advance wipe

4.wipe system,data

5.Falash 4.3 base rom and you will in 4.3 :D

Thanks for your support

And also them who ported and fixes those roms

Thaks myself for fixes some roms hahaha
[Miscellaneous Android Development] Amol1:
Excellent

Thnx for the roms.I just wanna request you if you can make micromax themed boot logo for this model as i've flashed kitkat (cm11) and boot logo is by default mito.

I just want it back to micromax........

I had flashed many boot logo but none of them worked.....

Also,custom boot animations would be cherry on top.;). (CM based if u can make them,tried to flash them too but nothing happened)

Appreciate your work.......:good:
[G4 Q&A, Help & Troubleshooting] strekib:
Hi, what version do you have on H818P EUR region? Is any update from V20D 6.0.1 stock? Thanks.
[MeMO Pad 7 General] NahuelMS:
Didn't like it, tablet still frezzeng and masive drain battery, kitkat is a lot better in every sense!
[MeMO Pad 7 General] thegreatn_:
This tablet is piece of sh*t, none of any rom can't help him
[MeMO Pad 7 General] NahuelMS:
Never going to buy nothing Asus again! The tablet have good specs but the software Asus made is the ****ty ever.

Said that, with Kitkat it is running good for the momment!

Thanks!
[MeMO Pad 7 General] NahuelMS:
I want to help here. I made the process a little bit diferent. To connecting the tablet to the pc i enter fastbot mode. Press power+Vol down until the robot appear.

Then launch 4- not 3-.

In the same way launched every step that the tablet needed to be connected to pc, like 7-.

In step 9- pressed Vol up+ power to enter droidboot then do 10, were it sais launch cmd you have to launch debrick-flashall-FW-no_wipe.cmd in the new location.

The tablet works excelent, very happy here, thanks!!

---------- Post added at 08:09 AM ---------- Previous post was at 08:00 AM ----------

Ok, it was not easy to root .201, stuck in demo mode like 3 times. This is the correct way:

-Download this version of root zenfone:https://cloudup.com/files/ivrnLUAwMDS/download

-Download supersu from the playstore and install it.

-Install and open root zenfone, let the app run and don't put OK when it enter demo mode. Let it run for 15 seconds and just restart the tablet without pressing anything.

-If everything is ok you will be rooted.

-In case things go wrong and you enter demo mode, you have to press back button for 10 seconds, then it will ask you for a code, put 741603 and confirm. It will factory reset your tablet and demo will be gone. In case it not enter factory reset you will need to do it manually, after puting de code.

For me google play service bug dissapear when disabled google as device administrator of the device.

This tablet work 10 times better with Kitkat, it doesn't restart, it is stable, a lot better ram manager. The only problem i figure out ia battery stats, it's very buggie. I can use the tablet 1 hour with 1% of the battery, it happen to me with this tablet in all version since i buy it, maybe my battery is wrong...
[MeMO Pad 7 General] f35suarezj:
Please. I lost the stock ESP and recovery. can someone upload the two files here? I have me176c ww version. I do not want to suffer more random reboots. :(
[MeMO Pad 7 General] Beaver_XT:
HELP!

I did all that and it stuck in the bootloop. Can't get in to fastboot or boot menu either.

OK... The only thing seems to be working is droidboot. When I try to go in to recovery then it will show belly up droid.

-------------------------------------

Edit: Alrighty mighty... I did it.

I consider my self and Android idiot cuz I've managed to f*ed up 2 devices beyond repair and even I am able to do this.

My K013 was latest Lollipop update .36, rooted, exposed, striped off system apps to bare minimum.

Here's what I did, step by step.

0. Pre-flight check.

Install ASUS_Android_USB_drivers_for_Windows downloaded from here> https://www.asus.com/support/Download/39/1/0/6/32/

Once you got the zip, unzip it then go to extracted folder > Windows_XP_VISTA_7_8_8.1 > Android, right click on android_winusb and click Install.

Install Intel USB Driver for Android downloaded from here> https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices

This one is install shell, easy.

1. Turn off the tablet.

2. Hold volume down and power until you see Asus logo, now you can release power button but sill hold the volume down button. This will get you in to fastboot.

3. Plug in the USB cable.

4. Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip then do #4 in tutorial.

5. When finished, unplug the USB and let it boot. Go and check as step 5.

6. Turn on developer mode by go to Settings > About > Software Information and rapidly tap "Build number" until you see the message "You are now a developer!".

7. Go to Developer options and turn on USB debugging. Then plug in the USB cable.

8. Do step 6 and 7.

9. When finished, unplug the USB cable and turn off the tablet.

From here on are what I find tricky-----------------------------------

10. Unpack WW-ME176C-3.2.23.201-release-user-20150115-signed then copy debrick-flashall-FW-no_wipe.cmd from from FWI_to_UEFI_ME176C folder and put it in the extracted folder.

11. Hold volume up and power buttons until you see Asus logo then release both buttons. It will enter droidboot like in this picture.

12. Plug in USB cable, run debrick-flashall-FW-no_wipe.cmd from WW-ME176C-3.2.23.201-release-user-20150115-signed folder.

13. When it reach this part

Do not close this window yet. You have to go in to droidboot again (otherwise it will go in to bootloop just as mine did).

What I did was unplug it, turn it off and repeat my step 11. Then plug in the USB and it will resume installing new.... old.... I mean 4.4.2. This will take some time, just don't let you PC go in to sleep or accidentally disconnect the USB.

Once it finish, unplug the USB cable and let it boot up. Now, go enjoy your K013 running 4.4.2.
[MeMO Pad 7 General] hjterry:
Thanks

Thanks dude, this helped a lot! Now I don't have to use sluggish Lollipop ;)
[MeMO Pad 7 General] f35suarezj:
Are really necesary the stock esp and recovery? I missed that.
[MeMO Pad 7 General] f35suarezj:
Ok. I take the esp.img and recovery.img from WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip and flash this like in the bootloader unlock tutorial.

---------- Post added at 04:32 PM ---------- Previous post was at 04:28 PM ----------

This works for me. Thanks!!! :D:D:D

*in step 11. is Hold volume up... ;)
[MeMO Pad 7 General] Beaver_XT:
Oops. Thanks for correction.
[MeMO Pad 7 General] Saarge:
at step 7 (flash_ME176C_IFWI.cmd) i can't go further, error 123 when trying to start demon, but i have usb debogging activated, what am i missing (i am on windows 10 anniversary update , i have disactivated drivers signature verification but i can't download intel drivers, the url can't seem to allow me the download).
[MeMO Pad 7 General] idoetzchen:
I had this error too.... You must copy the extracted folders on a other place! On the Desktop works for me... I think theres read/write restrictions from the system....

I flashed succesfully with windows 10....
[MeMO Pad 7 General] Saarge:
thought so but wasn't sure, i tried from the download folder in a folder with russian caracters on a french windows 10 x64, so i was thinking it was a name issue, will retry from another folder on root and use a simpler folder name.
[MeMO Pad 7 General] Saarge:
moving and renaming the folder did the trick, my me176cx just did it's first 4.4.2 boot in a while.
[MeMO Pad 7 General] Saarge:
A way easyer (and definitive) solution to root the tab is to use the tethered recovery and flash supersu, worked for me
[MeMO Pad 7 General] Saarge:
Well new problem, i don't remember how to properly install xposed on kitkat on this tab. Tried the official installer but the settings in gravity box for kitkat are ignored.
[MeMO Pad 7 General] daspex:
[MENTION=7290976]Saarge[/MENTION]

Hi,

i use the 2.7 experimental version but gravity box won't work but hk theme engine works good for changing icons and other theme stuff but it doesn't change the homescreen/settings screen backgrounds for this i use holo background themer.

To change the softbar buttons i use another theme engine mod.So with this three modules one can customize the tab pretty well.But i didn't found a mod to change the quick menu settings yet.
[MeMO Pad 7 General] Kennii:
can i do this for the android 5.1.1 version? quote me so i know someone replied to me
[MeMO Pad 7 General] NahuelMS:
There is no 5.1.1 for this tablet. Last firmware is 5.0.1 lollipop .36 and you can rollback to kitkay in any lollipop version.
[MeMO Pad 7 General] jfmjef:
Hello,

Thanks for your great post !

I have a problem after step 4, my tablet reboot but after ASUS LOGO, my screen still black !
[MeMO Pad 7 General] fosco_:
Thanks, i did it in my Linux box, everything worked fine. Now the tablet is usable again!
[MeMO Pad 7 General] soma35:
black screen

im getting black screen after step 4 :(
[MeMO Pad 7 General] castaway1:
hello all im about to try this metod as my tablet is unusable slow. Previous i did root it using AsusIntelRootKit

https://www.youtube.com/watch?v=Mmd-HxRRie8

it worked but im not sure what it did to my tablet. I dont know if my bootloader is locked or not or if i have stock recovery but it seems like it see screenshot

is it safe to continue and rollback with this guide?

EDIT: ok i did come to step 12 my tablet is showing asus logo and i dont closed cmd screen saying waiting for device but its about 15min now and tablet seems to rebooting constantly can anyone help me please? i dont know what to do now its still rebooting seems like it cant go into droidboot again itself

EDIT2: it works! thank you so much guys!

THANKS!
[MeMO Pad 7 General] sgunther:
I went through the steps to rollback to KitKat and found that my partition table is not set correctly. I wanted to re-partition but any attempts to

fastboot oem partition /tmp/partition.tbl

fail with a GPT error. Under the IFWI droidboot i am trying to

fastboot boot droidboot.img

but receive an error indicating "boot command stubbed on this platform". I can still boot into CWM or TWRP using tethered recovery. Does anyone know how I can actually re-partition in my situation before installing .182?
[MeMO Pad 7 General] djangoboy:
it works!!

Thank you guys, the procedure is perfect and now I have again a good tablet and not that kind of brick with Lollipop.

What do you suggest me now? How can I root my tablet in a safe way?

Thanks :D:D
[MeMO Pad 7 General] Nexive:
You can root it by flashing supersu with tethered twrp

Sent from my MeMO Pad 7
[MeMO Pad 7 General] Sangean:
Does this procedure work also for an UNROOTED, untouched tablet?
[MeMO Pad 7 General] thegreatn_:
nope.
[MeMO Pad 7 General] Sangean:
Could you give a link how to root Me176CX latest Lollipop version?
[MeMO Pad 7 General] thegreatn_:
link
[MeMO Pad 7 General] spookmeister101:
I'm confused, I do as you say, and I'm at fastboot screen on the tablet, I plug in the usb cable, it doesn't show on the computer and adb shell doesn't work. I can start twrp tethered recovery, but there's no way I can see to do step 4 or anything else? Some more clarification for us newbies would be much appreciated please.

Thanks.
[MeMO Pad 7 General] Beaver_XT:
Have you tried running .cmd with administrator permission?

Sorry, I don't remember much what I did.
[MeMO Pad 7 General] Saarge:
Since i have rollbacked, my tab hangs when charging while off (the battery animation freezes or don't show at all, and the tab is hard to wake up), any hint on a fix?

Btw if the tab give you an error in the first steps (data and cache may be corrupt) and become bricked, use tethered recovery, go in advanced wipe, change the file system (from ext4 to ext3 for example) swipe, then go back to previous file system (ext4) for both cache and data, then let the tab reboot, it should start correctly under the userdebug rom then.
[MeMO Pad 7 General] xXSantyXx:
I'm getting bootloop at step 4. My tablet was not rooted and my bootloader was locked. What can i do?

Edit: Never mind, i've done it again and i got it right .

Thanks to thegreatn_ and Beaver_XT .
[MeMO Pad 7 General] Shadeclan:
Noob Question

Will this method work for all ME176c devices? I have a refurbished tablet. It's basically an ME176ce in an ME176cx case.
[MeMO Pad 7 General] Delichi:
Thank you soooooooo much for your answer... Your experience really helped me! :laugh:
[MeMO Pad 7 General] Treklof:
I followed this guild and got an Error after Nr. 4:

UEFI: ME176C.106.05.Cap

target reported max download size of 536870912 bytes

sending 'capsule' (6368 KB)...

OKAY [ 0.233s]

writing 'capsule'...

FAILED (remote: check version error )

finished. total time: 0.300s

"flash capsule FAILED, EXIT!"

Drücken Sie eine beliebige Taste . . .

I just went on and finished the procedure.

Everyhtingh seems fine. Rom works. Got the old Droidboot (fastboot) back und the old recovery too.

What is this "capsule"? Why do we need it? I allways thought that it would be the "securitykey" that allows to flash firmware or droidboot and recovery Partitions. Right? Wrong?
[MeMO Pad 7 General] Sangean:
Before rooting and rollingback to KitKat...

- Does it make sense to make some kind of backup to resurrect the tablet in case something goes wrong? If yes, which tool should be used with instructions?

- Or it is not necessary because there are methods to unbrick the tablet even without making some level of backup before hand?