Database Users

[Q] "K1" Factory Recovery

Is it possible to restore back to the factory ROM on the K1?
I ran through the "Rooted Lenovo TOOL -Lenovo IdeaPad K1 ONLY!-" from the Dev forum. I tried a ROM recovery with the update.zip/update.xml in the download folder. Can't seem to get into the recovery rom and once the system boots the update files are removed from the download folder.
Can someone be kind enough to point me in the right direction.
Thanks
I watch the video and yes I'm a n00b!

If all you care about is getting it to some "stock" version, and are okay with it being rooted. Try the nvflash method from khanning. There's a thread on rootzwiki.

K1 to stock 14_14
I currently have the K1 rooted with the 13_13 update.
I have the recovery app installed, and I am trying to install the 14_14 OTA I downloaded from Lenovo. However, the ROM I flashed with has the K1 as a Xoom tablet in system>About Tablet.
When I use the recovery app and navigate to install update.zip it fails because it is recognizing the wrong device and fails.
How do I flash the 14_14 to my Lenovo K1?
Thanks

Just posted it the other day.
If you want 14_14_120109 stock not rooted
http://forum.xda-developers.com/showthread.php?t=1560441
If you want 14_14_120109 rooted with CWM
http://forum.xda-developers.com/showthread.php?t=1564002
If you don't want to reflash everything because your trying to keep all your data intact then:
**This would remove root and recovery but your data will be kept**
1. Open the update.zip that you downloaded from Lenovo. K1_A301_14_14_120109_US.zip
2. Go to META-INF/com/google/android/ and open updater-script
3. Delete these lines from the top:
Code:
assert(!less_than_int(1326090640, getprop("ro.build.date.utc")));
assert(getprop("ro.product.device") == "K1" ||
getprop("ro.build.product") == "K1");
4. Save the file and flash via recovery
Before you flash the zip in recovery make sure you toggle signature verification

Nitehawk68 said:
I currently have the K1 rooted with the 13_13 update.
I have the recovery app installed, and I am trying to install the 14_14 OTA I downloaded from Lenovo. However, the ROM I flashed with has the K1 as a Xoom tablet in system>About Tablet.
When I use the recovery app and navigate to install update.zip it fails because it is recognizing the wrong device and fails.
How do I flash the 14_14 to my Lenovo K1?
Thanks
Click to expand...
Click to collapse
Dude...im having the same issue.

i need only exe file because cant get in pattern lock or to much password forget a medion lifetab same as lenovo k1

[GUIDE]Upgrade TF300t to Jellybean 4.1 or 4.2, root, recovery & remove bloatware

Dear Asus Transformer TF300T users,
Asus released the 4.2 Jellybean update. Since there are some people with fastboot problems or don't know how to install recovery or root, here is a guide which will let you:
- Install recovery and give you root acces on latest 4.2 update
- [Optional] Remove bloatware from your tablet
== Part 1 - Preparation ==
Before we start with this guide I can tell you guys it will work for:
- All 4.1 firmwares
- All 4.2 firmwares
So what do you need to do as a preparation of rooting and installing recovery:
1. Upgrade your tablet to the desired firmware: 4.1 or 4.2
2. Be sure the correct drivers for your tablet are installed!!
3. Download the updated rooting toolkit: Updated Motochopper rooting toolkit
4. Download TWRP for your firmware version:
- 4.1: TWRP 2.5.0.0 for Jellyeban 4.1
- 4.2: TWRP 2.5.0.0 for Jellybean 4.2​
5. Rename the downloaded TWRP blob file to twrp.blob and copy it to the root of your sdcard
5. Extract the rooting toolkit to a place you like.
== Part 2 - Rooting ==
1. Open up the folder where you placed the rooting toolkit.
2. Open the run file and follow the instructions
After installation the tablet should reboot and you should be rooted.
== Part 3 - Latest TWRP recovery ==
Be sure you have twrp.blob on your removable sdcard or it won't work!
1. Open up CMD in the folder were you have your adb files (Shift + Right Mouse Click => Open CMD here) and use the following commands to install TWRP:
adb shell
su
dd if=/Removable/MicroSD/twrp.blob of=/dev/block/mmcblk0p4​
2. After this you need to reboot your tablet to let it install the recovery

MOD EDIT: This Method ONLY applies to JB 4.1. Do Not Use on JB 4.2
Dear Asus Transformer TF300T users,
Asus released the Jellybean update in the United States. Here is a guide which will let you:
- Prepare your tablet for the Jellybean update
- Update your tablet to Jellybean software
- Install recovery and give you root acces
- [Optional] Remove bloatware from your tablet
- [Optional] Speed up your tablet using tweaks
== Part 1 - Prepare the tablet ==
First we need to install the 9.4.3.30 US update to be able to upgrade to the Jellybean software, then we will do the actual upgrade to Jellybean.
1) Download the US 9.4.4.3.30 update: Asus support site
2) Put the file on your tablets internal storage
3) Got to recovery and make a backup
4) In recovery do to a factory reset and wipe dalvik cache
- TWRP recovery: Wipe => Dalvik Cache and Wipe => Factory reset
- CWM recovery: Factory reset and Advanced => Wipe Dalvik Cache
5) Flash the US_epad-user-9.4.3.30.zip file
Don't install a custom recovery after doing this step. The Jellybean update will only be automatically launched with stock recovery
6) Reboot into your tablet and enable "USB-debugging" and "Unknown Sources" in settings
7) Connect your tablet to your pc and download this file: Automated Rooting Toolkit
8) Extract the rooting toolkit and follow the instructions to root your tablet.
9) Once you finished the rooting process you are ready to continue to the upgrade process
== Part 2 - Upgrade to Jellybean ==
This will upgrade your tablet to Jellybean (Android 4.1.1)
1) Download the necessary files:
- dlpkgfile: Jellybean OTA update Rename this file to dlpkgfile
- command: command.zip (Extract this zip before copying to your tablet)
2) Copy both files to your MicroSD card or internal storage
3) Open root explorer or another file explorer with root acces
4) Copy dlpkgfile to /cache folder and the file command to /cache/recovery
5) Now you need to reboot your tablet, this will start the installation of the Jellybean update
6) Wait untill the update is finished and now you have Jellybean on your tablet
== Part 3 - Install recovery and rooting ==
Let's start with installing the recovery
1) Download these 2 files:
- Jellybean recovery with fastboot files: Fastboot files + JB recovery
- Root files: Root Files
- You can also download the new CWM Touch recovery if you don't like TWRP: CWM Touch recovery thread
2) Extract the recovery with fastboot files zip and open a command prompt in the same folder of the adb and fastboot files (Shift + Right mouse)
3) Reboot into the bootloader of your tablet, type: adb reboot bootloader
4) When your tablet has reached the bootloader navigate with volume down to the usb icon and press volume up to confirm.
5) To flash the recovery type:
- TWRP: fastboot -i 0x0b05 flash recovery tf300t-jb.blob
- CWM: fastboot -i 0x0b05 flash recovery CWM-Touch.blob
6) A blue bar will appear and the recovery will be installed, when the blue bar is filled press volume up + power button to reboot into the tablet.
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
== credits ==
- eyeballer for TWRP recovery
- untermensch for CWM recovery
- sparkym3 for his automated rooting toolkit
- Redefined301 for his guide
== Part 4 - Remove the Bloatware ==
The bloatware that can be removed is listed here, I listed it in categories
== Live Wallpapers ==
Code:
Black Hole (wallpaper or live)[B][INDENT]- Galaxy4.apk
- Galaxy4.odex[/INDENT][/B]
Android Live Wallpapers[B][INDENT]- LiveWallpapers.apk
- LiveWallpapers.odex[/INDENT][/B]
Backgound Picker[B][INDENT]- LiveWallpapersPicker.apk
- LiveWallpapersPicker.odex[/INDENT][/B]
HoloSpiralWallpaper Wallpaper[B][INDENT]- HoloSpiralWallpaper.apk
- HoloSpiralWallpaper.odex[/INDENT] [/B]
Asus Water Live Wallpapers[B][INDENT]- MyWater.apk
- MyWater.odex
- MyWater2.apk
- MyWater2.odex[/INDENT][/B]
== Face Unlock Feature==
Code:
- All files in /system/vendor/pitpat
- /system/lib/libfacelock_jni.so
- Facelock.apk
== Widgets==
Code:
Battery widget[B][INDENT]- BatteryWidget.apk
- BatteryWidget.odex[/INDENT][/B]
Deskclock[B][INDENT]- DeskClock.apk
- DeskClock.odex[/INDENT][/B]
Email widget[B][INDENT]- EmailWidget.apk
- EmailWidget.odex[/INDENT][/B]
My Zine[B][INDENT]- MyZine.apk
- MyZine.odex[/INDENT][/B]
Weather[B][INDENT]- Weather.apk
- Weather.odex[/INDENT][/B]
== Google bloatware==
Code:
Books app[B][INDENT]- Books.apk[/INDENT][/B]
Google Chrome[B][INDENT]- Chrome.apk[/INDENT][/B]
Google Market Feedback[B][INDENT]- GoogleFeedback.apk[/INDENT][/B]
Google Maps & Streetview[B][INDENT]- GMS_Maps.apk
- Street.apk[/INDENT][/B]
Google Gallery[B][INDENT]- Galery2.apk
- Gallery2.odex[/INDENT][/B]
Google Plus[B][INDENT]- PlusOne.apk[/INDENT][/B]
Google Talk[B][INDENT]- Talk.apk[/INDENT][/B]
Google Search[B][INDENT]- QuickSearch.apk
- Velvet.apk[/INDENT][/B]
Google Video[B][INDENT]- Videos.apk[/INDENT][/B]
Youtube[B][INDENT]- Youtube.apk
- YoutubeSearch.apk
- YoutubeSearch.odex[/INDENT][/B]
== Asus & 3rd Party bloatware==
Code:
Asus reader[B][INDENT]- AsusReader.apk
- AsusReader.odex[/INDENT][/B]
Dictionary[B][INDENT]- Dictionary.apk
- Dictionary.odex[/INDENT][/B]
Facebook Poster[B][INDENT]- FacebookPoster.apk
- FacebookPoster.odex[/INDENT][/B]
Asus File Manager[B][INDENT]- FileManager2.apk
- FileManager2.odex[/INDENT][/B]
Asus PC Sync[B][INDENT]- FDHttpd30.apk
- PCSyncLauncher.apk
- PCSyncLauncher.odex[/INDENT][/B]
Kindle app[B][INDENT]- Kindle-OEM.apk[/INDENT][/B]
MMS/SMS app[B][INDENT]- MMS.apk
- MMS.odex[/INDENT][/B]
Asus My Cloud & My Net[B][INDENT]- MyCloud.apk
- MyCloud.odex
- MyNet.apk
- MyNet.odex[/INDENT][/B]
Netflix app[B][INDENT]- Netflix.apk[/INDENT][/B]
Sound Recorder[B][INDENT]- SoundRecorder.apk
- SoundRecorder.odex[/INDENT][/B]
Asus Vibe app[B][INDENT]- Vibe_CN.apk[/INDENT][/B]
Video Editor[B][INDENT]- VideoEditor.apk
- VideoEditor.odex[/INDENT][/B]
Maybe more to be added later
== Part 5 - Speed up the tablet ==
Tweaks will come here

Thanks.:fingers-crossed:

Added my own link to dlpkgfile (OTA update file)
I hope this helps a lot of people
There are a lot of threads here, but not one that's really easy to follow for people that don't know everything about adb and that stuff

is rooting ONLY for unlocked device?

neo_u said:
is rooting ONLY for unlocked device?
Click to expand...
Click to collapse
Well I'm not long into the Asus development I'm a Sony Xperia dev
I don't know if you can root with locked bootloader. If you can install the recovery with locked bootloader then you can also root

krabappel2548 said:
Well I'm not long into the Asus development I'm a Sony Xperia dev
I don't know if you can root with locked bootloader. If you can install the recovery with locked bootloader then you can also root
Click to expand...
Click to collapse
Yeah. I can try to install, but, can my TF become a brick?

krabappel2548 said:
1) Download the necessary files:
dlpkgfile: Jellybean OTA updatehttps://docs.google.com/file/d/0B6LWCm-r4bHtYjBkS29yeFVSN2c/edit
command: command.zip (Extract this zip before copying to your tablet)
Click to expand...
Click to collapse
First off, thanks for this!
Some questions.
Your link for the dlpkgfile currently seems to point to "GoogleDrive" and makes me login to mine and send a request to be able to download it, which I did. Not sure if you are aware of it working like that?
2nd and most importantly in my case:
I am currently running the Seanscreams Hydro ICS Rom and am considering going this or whatever path is necessary to upgrade to JB. Any tips or alternative suggestions to follow in a case such as mine since I'm not already coming from stock? Obviously I have unlocked and have root. Is there anyway to keep my current setup without having to wipe OR do I need to rely solely on TIBU in order to get back all my apps?
Thanks!
PS: Oh, one more question. Is there a current working recovery to allow for creating/saving a backup once on JB? The answer to this question may very well be my deciding factor on if to wait things out a bit longer or proceed to JB now.

neo_u said:
Yeah. I can try to install, but, can my TF become a brick?
Click to expand...
Click to collapse
If you think you'll brick your device, then it's best not to try it.
lazer9 said:
First off, thanks for this!
Some questions.
Your link for the dlpkgfile currently seems to point to "GoogleDrive" and makes me login to mine and send a request to be able to download it, which I did. Not sure if you are aware of it working like that?
2nd and most importantly in my case:
I am currently running the Seanscreams Hydro ICS Rom and am considering going this or whatever path is necessary to upgrade to JB. Any tips or alternative suggestions to follow in a case such as mine since I'm not already coming from stock? Obviously I have unlocked and have root. Is there anyway to keep my current setup without having to wipe OR do I need to rely solely on TIBU in order to get back all my apps?
Thanks!
PS: Oh, one more question. Is there a current working recovery to allow for creating/saving a backup once on JB? The answer to this question may very well be my deciding factor on if to wait things out a bit longer or proceed to JB now.
Click to expand...
Click to collapse
Oops, forgot to set the file as public Now everyone should be able to download it
There is a JB recovery it's TWRP recovery. It's in my tutorial in this part:
1) Download these 2 files:
Jellybean recovery with fastboot files: Fastboot files + JB recovery
Root files: Root Files
Click to expand...
Click to collapse

krabappel2548 said:
Oops, forgot to set the file as public Now everyone should be able to download it
There is a JB recovery it's TWRP recovery. It's in my tutorial in this part:
Click to expand...
Click to collapse
Thanks. I did get the GoogleDrive dl permission and started to dl the file. Unfortunately, it seems this is going to give me the same fits as some hosts such as goo, ect... from my work wifi as it seems to be hanging at 9% :silly:
I was just going to ask which recovery we are actually getting with your method and as per the "quoted" above, I see you mention it's TWRP. As to my understanding following some other threads, this still as of now doesn't allow for an actual "backup" - "restore". Is that correct?

lazer9 said:
Thanks. I did get the GoogleDrive dl permission and started to dl the file. Unfortunately, it seems this is going to give me the same fits as some hosts such as goo, ect... from my work wifi as it seems to be hanging at 9% :silly:
I was just going to ask which recovery we are actually getting with your method and as per the "quoted" above, I see you mention it's TWRP. As to my understanding following some other threads, this still as of now doesn't allow for an actual "backup" - "restore". Is that correct?
Click to expand...
Click to collapse
It surely does have an actual backup and restore. It's only slightly broken. It can't back up or restore /boot, but that can be fixed by flashing the ROM after restoring your backup.

I'm working on AROMA installer with working touch to remove bloatware

Does the downloaded dlpkgfile need its name changed when placed in /cache? When you download it, its a ridiculouslyLongName.bin ?

dlpkgfile is the file name. If you change this, you have to change the command.

The command says /cache/dlpkgfile . Ive changed the name several times. Im just trying to figure out why my update keeps crashing at 25%.

Where do you wipe the dalvik cache?
Sent from my ASUS Transformer Pad TF300T using xda premium

Tried the instructions at least 20 times and it won't work. Sure it's user error
Sent from my SGH-T989 using xda app-developers app

is this CWM recoery or TWRP ?

anyone know how to find out why the update is failing?
placed dlpkgfile into /cache/ and placed "command" file in /cache/recovery and the install failed.
pretty sure i "thawed" all my apps, and have the stock build.prop.....if i add apps to system/app will that cause a failed install? i just remembered as i typed this that i modded an app and placed it in system/app because it wasn't signed.

I haven't deciphered an answer for this question as of yet:
Does this work on an unlocked, rooted tablet running a custom ROM?
TIA

Has anyone tried yo install russian flyme Roms with integrated TWRP?

Has anyone tried russian flyme twrp roms? There are 3 Roms in their link, but i don't know how to install it.

any link please ?

I can't put links because i have less than 10 post.
I'm sorry.

Write emmaus.pro in google. There are twrp for mx4 and custom roms, flyme and cm12.

I have Flyme 4.5.7i on my MX4 flashed by TWRP recovery.
(original my mx4 was A edition, and I was unlock bootloader and flash custom recovery with instructions found on xda forum)
Instructions How To Edit Official Flyme Rom to be flashed with TWRP:
---------------------------------------------------------------------------------------
1. Unzip update.zip in empty folder
2. Go in folder with unpacking files and delete uboot.img and logo.img
3. Go in META-INF folder and from here delete imei.dat and machine_match
4. Go in COM/GOOGLE/ANDROID folder and edit updater.script
Remove this :
getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "mx4" || getprop("ro.product.device") == "M460A" || abort("This package is for "mx4" devices; this is a "" + getprop("ro.product.device") + "".");
package_extract_file("META-INF/machine_match", "/tmp/machine_match");
set_perm(0, 0, 0755, "/tmp/machine_match");
package_extract_file("META-INF/imei.dat", "/tmp/imei.dat");
if (run_program("/tmp/machine_match", "/tmp/imei.dat") != "0") then
ui_print("machine not match");
delete(/tmp/imei.dat);
abort();
endif;
delete(/tmp/imei.dat);
And remove this :
assert(package_extract_file("logo.img", "/tmp/logo.img"),
write_raw_image("/tmp/logo.img", "logo"),
delete("/tmp/logo.img"));
assert(package_extract_file("uboot.img", "/tmp/uboot.img"),
write_raw_image("/tmp/uboot.img", "uboot"),
delete("/tmp/uboot.img"));
Save edited file.
5. Pack again files in .zip arhive (any name except update.zip)
6. Remove or rename any update.zip original file from root sd card
Now you can flash rom with twrp recovery and now you have latest Flyme rom but still have unlocked bootloader and twrp recovery.
I find this instructions on russian forums, and I try it and everything works fine.
You can try it on your responsibility.

Ok, thanks. Where have you downloaded twrp recovery?
Now i have philz 6 recovery, if i flash modded flyme ROM, can i flash it with philz?

I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file

TWRP (uncompiled and recompiled by myself to change splash screen (it now fit the screen) http://www.mediafire.com/download/26b963db1k489db/new-recovery.img

Can i flash it trough flashify app?

I was flash twrp with fastboot

You can via flashify but fastboot is safer

PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"

Are the russian flyme roms modded to can flash it vía twrp?

yes you can flash them Russians have ported this TWRP and are making some good stuff on flyme rom

Ok, i will try those Roms. Thankyou so much.

furious.builder said:
I'm pretty sure that if you do a clean install (formating /system /data and /cache) Flyme will reinstall stock recovery. You need to delete recovery-from-boot.p and all install-recovery.sh and install-recovery-original.sh from system file
Click to expand...
Click to collapse
I can't understand you. If is already tried that you can flash modded flyme Roma from twrp, why you say that flyme will reinstall stock recovery?
Are you sure?

I'm talking about stock Flyme not modded Flyme Stock flyme contains scripts like recovery-from-boot.p and install-recovery.sh in system.new.dat which reinstall stock recovery, it's what it does to my MX4, but modded flyme certainly don't have these scripts

Understood. Thanks!

furious.builder said:
PERFECT ! I worked hard to make it graphically perfect : http://www.mediafire.com/download/z3ssqo6lnyvwki7/TWRPr4.img
Just flash it with "fastboot flash recovery TWRPr4.img"
Click to expand...
Click to collapse
Is there any risk of brick flashing twrp vía fastboot?
I have seen many mx4 bricked flashing custom recovery with flashify.

Via fastboot there is nearly no risks because if it's flashed it will boot, and if there is something wrong during unlock fastboot has not been unlock so it will not flash, but don't use the one from my link, there is a newer from emmaus.pro

OxygenOS 3.1.0 (Marshmallow) Community Build for OnePlus X

New build is available to download.
Download link http://downloads.oneplus.net/oneplus-x/oneplus_x_oxygenos_3.1.0_community_build/
for those who stuck in boot, flash this recovery through fastboot . https://dl.dropboxusercontent.com/u/10404978/t/opx_oos3_recovery.img Credits: pwseo
For getting to fastboot menu, 1) press power button untill phone has been powered off.
2) first press volume up button then power button until fastboot mode is shown.
3)Use the following command to flash the recovery. (Note:adb and fastboot should be installed first. get it here:http://forum.xda-developers.com/showthread.php?t=2317790)
fastboot flash recovery opx_oos3_recovery.img
Click to expand...
Click to collapse
source https://forums.oneplus.net/threads/oxygenos-3-1-0-marshmallow-community-build-for-oneplus-x.460857/

I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks

I read the thread, i think need to flash stock Recovery before flashing

motherninja said:
I can't install it through BluSpark TWRP v.37.
The error is something like this: This package is for "OnePlus" devices; this is a "ONE".
Anybody know how to fix this without replacing TWRP with stock OP Recovery? Thanks
Click to expand...
Click to collapse
You can flash it thorough official twrp or stock recovery

You can also keep your recovery, but you have to slightly modify your package.
1. Unzip package.
2. Go to META-INF\com\google\android\
3. Edit updater-script with notepad++, or just with any text editor.
You should see "getprop("ro.build.product") == "OnePlus" || abort("This package is for \"OnePlus\" devices; this is a \"" + getprop("ro.build.product") + "\".");"
4. You can delete this line or change getprop("ro.build.product") == "OnePlus" to getprop("ro.build.product") == "One". In my case I had to change it into getprop("ro.build.product") == "onyx".
5. Save it and zip whole package.
6. Flash it and enjoy

My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?

Still waiting for a solution. :/

Waiting for opinions before flash hehe

motherninja said:
My advice is, DO NOT flash this update yet...
Now I cannot back to TWRP anymore... Anyone have a workaround for this?
Click to expand...
Click to collapse
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
hotlinksxz said:
Waiting for opinions before flash hehe
Click to expand...
Click to collapse
Same here ...till some one compile the ROM which can be flash through TWRP

maybe i will wait for bug fix before flash..this is the first oos 3 for opx so it will be buggy
Sent from my ONE E1003 using XDA-Developers mobile app

kethsawant said:
U need to flash TWRP from ADB from PC, Think this is the only way now
---------- Post added at 01:38 PM ---------- Previous post was at 01:36 PM ----------
Same here ...till some one compile the ROM which can be flash through TWRP
Click to expand...
Click to collapse
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.

Any update on VOLTE?

Root
With Kingroot YouTube can get root, maybe with flashfire you can install twrp?
Edit: Can't install twrp but can install xposed.

Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.

Danish66 said:
Any update on VOLTE?
Click to expand...
Click to collapse
+1
Yes Guys..Can someone share any info here on this topic in the latest Oxygen OS build ??

motherninja said:
No, you cannot simply do that anymore. Look at the OPX forums at forums.oneplus.net, as advised by @pwseo, you need to follow the Mega Unbrick Guide first to fully restore your OPX to its original Lolipop FW, after that you are free to install TWRP again.
Click to expand...
Click to collapse
hmm same here,cant get into recovery,twrp needs to be updated by the devs i think
also directly booting into twrp fails too,"dtb " not found

gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
How u did it?
Mind sharing step by step?
Thanks in advance.

gahehe said:
Flashed OxygenOS 3.1.0 using TWRP. Everything is soooo smooth. Antutu benchmark give 57195 points, so greattt.
Click to expand...
Click to collapse
With twrp? How?

If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!

gahehe said:
If you're using stock recovery, just wipe data & cache and flash it.
If you're using TWRP, please do a Factory Reset then wipe system, data, cache, ART cache (very important, you will have many bugs on your device such as not recognize SIM card, Wifi not working... if you don't clean install). Then flash this ROM and reboot twice.
If you encountered error "This package is for "OnePlus" devices; this is a "ONE"." after select the ZIP, please extract the ROM, open the file META-INF/com/google/android/updater-script then remove the first line:
Code:
getprop("ro.build.product") == "OnePlus" || abort("This package is for "OnePlus" devices; this is a "" + getprop("ro.build.product") + "".");
Save the file, re-ZIP the ROM and flash it. Ta-da!
Click to expand...
Click to collapse
But you won't be able to boot back into twrp, so it's kinda useless. Better to have stock recovery than not being able to boot back into twrp=p
Unless you were able to flash supersu with twrp before booting the rom and not being able to boot back into twrp. Was that the case?

Post Your Current or Last Boot Issues here (READ BEFORE POSTING PLEASE)

Hi A7 users,
Let's start this off be saying, bare with me English is not my primary language.....
OK now, the reason for this Thread is to find a definite solution for current users and future users who have run into boot issues cuz they were trying to :
A- Go back to Un-rooted and lock bootloader state.
B- Started Playing with root tools and make a huge mistake
C- Started playing with twrp not knowing what they were doing
D- All the above + started flashing images files and got worts.
E- Any other type of situation.
I Know we make mistakes and we learn from them and well here today we are going to try or rather say Find a permanent /define solution to all this issues with your help, so PLEASE ONLY POST IF YOU HAVE RUN INTO ANY OF THIS ISSUES AND HOW YOU GOT INTO THE ENCHILADA ( MESS ) .
If you have the solution to your previous boot problems send me a PM and I'll keep this Thread updated for everyone to see with your solution and of course credit to the user/s.​
NOTE : Please mention which Axon 7 you are using e.g. :
- A2017 (Chinese Variant)
- A2017U (USA Variant)
-A2017G (UK/Europe/International Variant)

reserve 1

reserve 2

reserve 3

reserve solution 4

reserve solution 5

Anyone this issues please post you issue, how to got into the problem, device model and if you got it fix let us know.

https://www.youtube.com/shared?ci=05LD4Ja-h3k
You'd think with all the other posts about problems there'd be something here by now.
Always thank those who are helpful...and just ignore those who aren't.

Mine happened when I wiped Internal storage from twrp. This caused the phone to only see 4gb of internal storage. Came to xda and it was suggested to flash back original boot.img. once that was done 4gb issue was fixed and the radio was gone.
I did indeed try every solution offered (thanks again for all the effort, DrakenFX and others). But, I've come to the conclusion that this is not going to get fixed until XTE releases US images. For other people's sake I hope I am wrong, but I myself decided to proceed with the exchange where I bought it, as I was right at the end of my 14 days (newegg doesn't seem to give the 30 days that xte does). I may be out of an Axon 7 for a while, so for now I am on my amazon ads, Blu R1 HD (with ads defeated

Is there a guide to go back to stock for the A2017G?
i'm on B02 with root and the bootloader still locked.
Like to go back to stock now that ZTE is working on an update to give the A2017G an unlocked bootloader.

Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!

aPexalpha said:
Hi all,
I am currently experiencing a bootloop on my Chinese Axon 7. Some of you regulars may have seen me asking in other threads because I've tried to fix it myself, but I've kind of run out of options. Sincerely hoping one of you can help me out!!! I'll buy the winner a beer or 2, haha!
Back story:
Was on B07 with root (tenfar's tool) with locked bootloader and had some issues with the ROM. Like vibrating when I opened the camera and battery drops. So I decided to upgrade to B09. Placed the OTA on SD card and went to: Settings -> update. Worked fine. So I connected it to my PC and made a dump (tenfar's dump tool) of my recovery and boot and stored them. Then I ran the Tenfar's tool, the B09 version and it went like the last one. But when I booted I didn't have wifi, and other issues came up. So I thought: did I make a mistake? So I read it again, checked the COM port again... all checked out. And used Tenfar's tool again. After that it didn't even boot anymore! It plays the nice boot animation and then gets stuck on the end screen with all the pictures.
So after that I restored my dumped recovery.img and boot.img. This is when I knew something was wrong: it still didn't boot! I reset data/cache in the stock recovery: no boot. Still stuck at the end of the boot animation.
What I've tried:
- Flashing the stock B09 update.zip with TWRP.
- Flashing the stock B09 update.zip without updater-script 'assert' and 'get-prop' line. TWRP says 'update.zip is corrupt'. Doesn't install.
- The I put it on SD card and internal memory and tried updating it with stock recovery: 'sorry you cant sdcard upgrade'. That's all it says.
- ADB sideload stock recovery: 'cannot load update.zip'.
I tried different ADB versions, Windows and Mac, different drivers... I tried formatting SD card as FAT32.. Tried different SD card.. Doesn't make a difference.
TWRP log says it can't pass the Zip verification when I try that. If I turn that off it says re.product.name is wrong. But I checked build.prop and updater-script. It's the same! But somehow TWRP comes up with a different one. Also tried removing getprop and assert lines from updater-script. But then it says: ZIP file is corrupt.
TWRP log after trying original, stock B09 flash:
http://pastebin.com/cJivE2TK
Build.prop: moved from /system with TWRP:
http://pastebin.com/b6rryc2n
Build.prop: ro.product.name=P996A03
Updater-script:
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A03");
But TWRP log: ro.product.name=cm_ailsa_ii
So, yeah, I've been trying on and off for the past couple of days in between work and travelling. Got a back-up phone so it's not that bad. But I really like this phone! It's just been such a pain in the ass the past few days...
I tried researching online and reading all the XDA posts. It is my fault this has happened and feel such a newb for not being able to fix it myself
Many thanks in advance!
Click to expand...
Click to collapse
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++

I am was rooting my axon a2017 on b10 chinnese version without any backup after rooting got password screen after boot then i was do factory reset and format data and all looking good but after that i saw that i dont have google play app so i installed macro gapps 6.0 after flashing phone stuck on axon screen (after zte logo) for long time i been wait up to 30 minutes and nothing was done..also i have the message on twrp about the modification(dont understand why i have this message all the time) i saw in xda forum that need to install supersu so i search on internet and was flash super su 2.65 and then when i am was boot device go to zte logo screen and then turning off when i connect the device as mtp device named as a2017u (whats worng with it??? I was flashed b10 root boot.img)
I regret about this root and want to back all to stock without any problems need help from someone
I need stock b10 boot.img if someone can upload
Many thanks!
---------- Post added at 04:23 AM ---------- Previous post was at 04:11 AM ----------
DrakenFX said:
PM I'll help you create a flashable zip base on B10 (Full update release), just make sure to have the following apps:
- 7Zip
- Notepad++
Click to expand...
Click to collapse
Its will help me too i think

Dear All,
ZTE Axon 7 A2017 (Chinese version) Stuck on Bootloader mode.
Device after power on will Stuck on ZTE logo even power button press longer also will Off and came back to square one and the only way to power off is via selection on bootloader page via volume button which consists of Recovery mode, Power Off, Bootloader and some other mode which I can't recall.
History of this issue. Please bear with long story.
Manage to install MM ROM with B13 via sd card installation via update software in phone setting. follow by Unlocked bootloader and Install TWRP 3.1.1.0 then try few different ROM until one day when I use Xiaomi flashtool my PC crash half way through during flashing resulting in device with Pure Chinese ROM and TWRP also got corrupted, when I said corrupted because I install TWRP 3.1.1.0 but when I go to Recovery mode it shows TWRP 3.0 something. with this corrupted TWRP when I try to install ROM it will show loading but end result is NIL meaning same ROM nothing change.
Until this stage I never did a TWRP backup because all this while the ROM is Not my type of ROM from this junction when I boot back to TWRP and I did Advance Wipe most of it except external sd card thinking that I may be able to install fresh TWRP but my Recovery TWRP is residing in phone storage resulting in No more TWRP recovery software. next thing I did was I connect phone to PC and ran adb fastboot tool to detect device and managed to detect device in recovery mode and I make decision to Locked back the bootloader and did just that and Locked bootloader is Succes and it also Erased everything during the process.
To cut short the story after Locked back bootloader only Bootloader mode is accessible and when I connect to PC and enable Recovery mode (Black screen) and EDL mode (Black screen) from Windows PC Device Manager COM port able to see Qualcomm 9008 for this 2 mode.
I must admit after few days of trying to resolve this Stuck Bootloader issue I almost give up.
Then I remember this Woodo magic by jcadduno which recommends XM flashtool version 2016.08.30.0 but unable to flash after trying few version Xiaomi flashtool and the very latest and I mean from Xiaomi Flashtool webpage http://xiaomiflashtool.com/
version 20170425 that break the ice and finally able to load A2017U ROM because this US ROM my phone No Network detected.
From here onwards I unlocked bootloader and install back TWRP (Installation of TWRP via Axon7toolkit) because of Network issue since I got TWRP I install back A2017 ROM but still Not satisfied because Chinese ROM certain Apps having issue because of Google services and I chance upon this Conversion A2017 to A2017U ROM (Hybrid ROM caused ROM is US and Modem from Chinese Modem)
that I'm stay put right now and my phone now is A2017U model.
I hope this experience can help others with similar Stuck bootloader and those who wish to convert A2017 to A2017U ROM.
below is the link that I described Woodo magic.
https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
Straight forward Axon7toolkit, please don't use Chrome browser cause Chrome will Automatically Delete it after complete download for my case I used Microsoft Edge.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
below is the link to Hybrid ROM for A2017U
https://androidfilehost.com/?fid=457095661767154458 by Michael Warner After flash install No verity patch for the bootloader.
Cheers.

I am stuck in a position where I can restore my nandroid backups but get Error 7
when trying to reinstall any Rom on a2017u I was able to fix the unlocked bootloop
by the EDL method. The Rom's are the same as the backups. I think I tried to role back to B29 Causing the bootloop) and have had problems ever since.
Should I try flashing A2017Uv1.1.0B32_Bootstack_by_DrakenFX since the Rooms are all B32?
The B15 and B19 Nandroid's still Restore fine.

Hello all,
i don't get onto forums very often but i thought this was a nice one to add to. i've rooted a few motorolas, a few ztes, a cat; i've also bricked those ztes, cat & a few samsungs. i'm dealing with two Axon7U's; one is factory MM-b29, the other is N-b35.
while screwing around with TWRP, i bricked the b35 (the b29 has been bricked for a month at this time) after i had it almost perfected. by perfected i mean a custom recovery & root user access fully acquired. with DrakenFX's {YOURS; thanks so much. i'm learning to get along with linux} extensive files created to save people from themselves i was able to unbrick the b35. albeit its CELLULAR DATA became unhinged; that's something i could've lived with except it was a loaner and had NO CAMERA! it's camera (along with the ability to push both volume buttons at once for say EDL mode...) was damaged having been beaten across a steering wheel several times. so with my newfound unbricking superpowers i decided to take another crack at the b29. managed to get it unbricked but couldn't get it setup with both TWRP & SuperSU without losing one, the other or, both. at times it didn't even boot up. i was doing pretty much everything cited above for reasons 'why'. best way to learn is by trial & error (if one can afford it).
the b29 is rooted right at this moment; i'm working on it as soon as i leave this posting. i used Axon7_EDL_Tool. i used Axon7root. i used MiFlash. i used Fastboot. I used ADB App Controller software too. back & forth i fought for three days mostly due to downloading glitches and i prevailed. i manipulated a stock OTA full system update.zip by happenstance and it Auto_Updated over itself. in other words it already had the same ROM installed. i don't know what it tested to realize it needed to update to what it already had. it didn't have CELLULAR DATA either. just like the b35, it broke somehow while flashing TWRP or SuperSU. funny thing is it still wanted to update that same ROM after it did. while perusing the system update setting(s) i noticed it had downloaded N-b15 and it wanted to update b29 AGAIN! i opted for the Nougat update. it did alright and appears to have fixed it's CELLULAR DATA too. i haven't looked at it since but i'm confident i can gain root user access with a minimal amount of effort.
The main problem i've had with dealing with bricked devices is the age of the file downloads. most of them are simply GONE!, expired links and whatnot. if i'd had a clear path say from a custom recovery and rooted boot image of my factory version or the path that leads to it, i'd have been fixed up long ago. i've found partial 'paths' if you will that almost get me there but no quite all the way. flashing images & zips through fastboot are different from their counterparts entered through TWRP or Emergency Download Mode which of course are both different too. three different ways to get into one's phone makes it almost impossible to keep them perfected.
i'm not sure i did what i'm supposed to regarding this thread. Thank you DrakenFX for your time & knowledge; you've saved my old Axon7!

Hello all update;
b35 Nougat phone is retired. b29 managed to update itself to b35 7.1.1. however, its CELLULAR DATA is still broken. i haven't managed to figure out how or where it's broken so i cannot fix it.
what i'm trying to do now is flash Magisk instead of SuperSU and using a TWRP version 3.0.3-1. heck i've used all of TWRP's versions in my efforts to reacquire CELLULAR DATA.
crazy part is the phone knows its CELLULAR DATA carrier and freely displays all of its hookup info. this is very frustrating.