Okay..
After a long testing and debugging session with AbduL_PT
This Guy is the only one who can make TWRP work with Rockhip devices. Check his thread and give him some BEER. He Deserve it!:good:
We finally come up with TWRP for our device!!! :victory:
DISCLAIMER: Rooting any Android device or installing a custom ROM firmware will void the warranty of the device and might only be restored by flashing the phone back to stock firmware and uninstalling custom recoveries and such.
I take no responsibility for any malfunctioning or any wrong doing happening to your device(s) by you following this guide. Proceed at your own risk!
Instructions.
Please make sure that you are familiar with RKtools and installing driver from device manager before you proceed on this
For fast booting to flash mode and recovery mode. Please install this app. ROOT required
Bootloader = Press Power + volume (nearest to the powerbutton) for 5 seconds or until Windows detect new device
Recovery = Press power + both volume buttons. One logo show up release power button and keep pressing volume buttons
1. Dowload the zip file to this LINK
includes
RKtool
stock and TWRP recovery
RK29adbdrivers
2. Unzip it and run update
3. Plugin your tablet to you PC .
4. Launch reboot app and choose "Bootloader" or turn off your device do and it manually with buttons
3. Windows will look for drivers and install driver like this guide using the driver I provided
4. Once RKtools detect your device (ii will show Found RKAndroid Loader Rock Usb). hit the "RUN" button and dont press anything else until your device reboot
5. launch reboot app and choose "Recovery" or turn off your device do and it manually with buttons
ENJOY
If you want to go back to stock recovery
launch RKTOOLS again and choose "recovery-stock" image from Recovery folder
I was able to do FULL NANDROID BACKUP and RESTORE successfully using this recovery
Since our device use /data/share as Internal SD card, we have manage the following (credits joe.stone)
Fixed Internal SD handling , now it is correctly /data/share not data/media .
Fixed wipe of Data . Now it does not removes the content of internal SD.
BUGS
1. Data nandroid backup the whole /data partition (includes /data/share which is Internal SD card)
2. Internal SD nandroid back up /data partition as well
3. Default Storage is internal SDcard (it can change to External SD on Mount Menu)
4. If FORMAT Data is chosen on Wipe Menu, reboot to recovery is required
5. For wiping Cust partition, put a tick on "Use rm -rf" on Settings
Credits:
Freaktab.com for all rockchip needs!
joe.stone for allowing us to use his source and provide some changes
and ofcourse..
AbduL_PT and for this TWRP thread for everything... Again this Guy deserves a Thanks and a BEER! LOL!
If you appreciate it , Give those Guys a THANKS and Click that THANKS button below ( dont be so ungrateful [email protected][email protected]#($! )
Reserved
Tried today your beta on my Huawei Mediapad 7 Lite (S7-931u) and seems to me, it is working just fine!
I can only say, great job guys! :good:
Had same issues with Cust partition like in BUGS section of you introduction post, but in the end recovery went OK.
Tried compressing backup and restore and it works.
Didn't try Install option of the recovery, cause i don't know any custom ROMs existing for this tablet, and didn't try Mount option cause don't know what to test.
One minor thing/bug I noticed (if it is even important), when recovery is done and press reboot my tablets screen flips upside down until reboot, afterwards it back to normal.
Anyway, thanks for your effort, now it is time to experiment without reinstall everything from scratch
So what exactly does this do to a device?
TWRP (Team Win Recovery Project) is a custom recovery just like CWM (ClockworkMod).
Custom recovery is used for different OS customization, but mostly is used for installing custom ROMs (like CyanogenMod, CarbonROM, etc.) and full device backup and restore, well at least that is why is mostly known for.
If you are interested in more on TWRP you can follow this links for more: link1, link2
prometej-zg said:
One minor thing/bug I noticed (if it is even important), when recovery is done and press reboot my tablets screen flips upside down until reboot, afterwards it back to normal.
Anyway, thanks for your effort, now it is time to experiment without reinstall everything from scratch
Click to expand...
Click to collapse
yeah.. the first twrp releases created for this device is inverted... Abdul just add some tweak to get the proper orientation for our device
good thing you confirm that nandroid back up works!
are you part of 4pda people?
Yes, nandroid backup works ok, at least on my model.
Didn't have other ROM to test, but I've tested it by "destroying" some parts of stock ROM (apps, settings, etc.) and tried recovery.
Maybe I'll try some RK2918 generic ROM if found something useful.
No, I'm not part of 4PDA people/community, why do you ask?
I'm just a enthusiast who started tinkering around this tablet frustrated with its stock ROM (in)stability.
I've read some 4PDA forum posts and they really have interesting discussions on the subject of Mediapad 7 Lite, but sometimes I'm a bit lost in translation even when using Google Translate. Cyrillic I can read, but speaking/writing Russian sadly no.
prometej-zg said:
Yes, nandroid backup works ok, at least on my model.
Didn't have other ROM to test, but I've tested it by "destroying" some parts of stock ROM (apps, settings, etc.) and tried recovery.
Maybe I'll try some RK2918 generic ROM if found something useful.
No, I'm not part of 4PDA people/community, why do you ask?
I'm just a enthusiast who started tinkering around this tablet frustrated with its stock ROM (in)stability.
I've read some 4PDA forum posts and they really have interesting discussions on the subject of Mediapad 7 Lite, but sometimes I'm a bit lost in translation even when using Google Translate. Cyrillic I can read, but speaking/writing Russian sadly no.
Click to expand...
Click to collapse
Thats nice... anyway i found some generic rk2918 cm10 i will to port one...
Since I am kinda new to this stuff, just to be clear, can I flash a custom ROM and update my Android using this and if yes, where do I get the ROM from and are there any particular instructions for flashing it?
TWRP is not custom ROM, but recovery/install tool that can help you install custom ROMs.
You can flash only custom ROM that is compatible with your device. E.g. MediaPad 7 Lite is based on RK2918 System-on-chip (aka. SoC), and it needs ROM with configuration (settings, drivers, etc.) for that hardware configuration, so it is not easy task to make fully compatible custom ROM, especially if you don't know or don't have source code for you device.
Android platform has very high device "fragmentation", so custom ROM for device with similar hardware specs, can still make your device unusable or bricked at worst if not careful.
As I said before, I didn't find any custom ROM for Mediapad 7 Lite, but I've seen some customization on stock ROM (based on SP19 firmware) on 4PDA forum (but I think it contains only Russian localization - I'm not sure!)
There are some RK2918 custom ROMs (mostly CM10) for some tablets, but don't know it they would be easily customized to this tablet.
Search XDA forum, it has a lot of forum threads on this and similar subjects.
Anyway... if you plan to experiment, you need to be careful, if you don't want your tablet to become "PaperWeight 7 Lite"
Thank you for you're reply. I will for now, keep my device as it is. Thank you for you're time.
just to let any Linux user know I have created a tutorial to flash OP's TWRP here
http://forum.xda-developers.com/hua...tutorial-linux-flash-twrp-mediapad-7-t3002557
OK just tested TWRP sideload with Linux PC that has udev rule set up and adb running
below image is Linux command
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
second image is of result in tablet, zip chosen was Chainfire's supersu
#############################
sorry if next appears negative, I am not an expert just seeking to clarify some things
I have unpacked our TWRP and it appears to be a port of another device.
eg inside build.prop I can see
ro.product.brand=yuandao
....
ro.product.model=n70s
Click to expand...
Click to collapse
secondly inside init.rc there is no line to import the usb rc file instead I only see this import
import /init.recovery.rk30board.rc
Click to expand...
Click to collapse
OOOH there is no usb rc file but I can bodgee one up if you are interested.
altho I have no experience with TWRP I have ported 3 CTRs that show at needrom, so I have some skills....modest too
Did you guys focus on the big picture and forget to update the text files?
Do you mind if I have a go at fixing and either pm you a download link or forum link?
cheers and thanks for reading
Hmmm!?
I am sorry to bring more bad news......but I think I have a found a possible answer to why the id is wrong in TWRP.
EDIT and I am hoping this is the reason why fastboot is not working for me, altho I know not all devices support fastboot. As my udev is right, rebooting and looking for fastboot is currently a fail........but thats one more test I shall have to do in rebuilding our TWRP.
The id is wrong in the stock BOOT image unpacked. That is, our porter may have taken that id as gospel without checking it independently. Also I am aware our device will still have different ids such as for the modem which is often a different manufacturer........I am often wrong.....but this I feel explains the human error in TWRP.
It shows for its init.rc
write /sys/class/android_usb/android0/idVendor 18d1
Click to expand...
Click to collapse
forgive me for pointing out the correct id is 12d1 as showing here
http://www.linux-usb.org/usb.ids
For anyone interested 18d1 is Google.
2) EDIT I was initially planning to have a go at fixing our current TWRP. The time to edit and check stuff is roughly the same time and effort to port a more recent TWRP.
For that reason, if I brick my device, only I have bricked it and all other users are not mislead.......giggles.
I have found that Samsung Galaxy Tab 2 is a 7 inch 600 x 1024 pixels and someone has kindly uploaded TWRP 2.8.4.0 for it at the TWRP site. So fingers crossed I can port that correctly. Later, if device is still alive, I can mod our boot image to correct specs.
cheers and thanks for reading
Go ahead.. Let us know what can you accomplish.. Remember samsung doesnt use Rk flatform.. If you want to go further more.. You can ask Abdul.. He is a very helpful guy
edit
slightly off topic so removed.
Hi
rather than pollute this nice thread about TWRP for our device I have started a new thread on some of my thoughts, feel free to peruse, abuse or comment there. I won't post any more here until I have a proven result or 2 or 6
I hope you understand why I am posting this as well?
cheers
http://forum.xda-developers.com/hua...mediapad-7-lite-s7-931w-online-notes-t3016947
can you please post the link again for the zip file of rk tools and twrp and drivers. it doesnt work anymore. i want to install twrp on my huawei medipad s7 931wd. thanks.
Download link's Down
Related
Hi all, after a great effort and lot of work finally i got cm9 compile from source working in my s7 model 105.
this is a more stable version it still has some bugs that i'm trying to solve, help is welcome.
I used kernel from jotamj from another forum and i use asturel device files to get it started, asturel files is for the slim so i had to made some changes in the files, thanks to them.
For a long time i hope for a update from huawei but notthing came, people at huawei suck, they dont give any suport to there clients, so i and other had to do it in order to have cm9 or cm10 in huawei s7.
this work on:
my s7 model=105, it may work on 104 and in 106, probably will not work on s7 slim
what works:
-wifi
-bluetooth
-audio
-gps
-google play (solve, install gaps file)
-streaming (must install flash player 11)
do not work:
-camera
-usb mount on pc
how to install:
first do a backup, IMPORTANT , backup first ( in case same thing go wrong)
copy file zip to sdcard
boot on cwm and install zip file
reboot and wait 4 to 5 minutes, if anything goes wrong restore from backup.
version 53 (more stable)
link: https://docs.google.com/file/d/0B9OIKoN0knUtSGNfVWpOSjBqNEE/edit?usp=sharing
to solve google play install gaps
link: https://docs.google.com/file/d/0B9OIKoN0knUtUTdSQUpERHhfYTg/edit?usp=sharing
help is welcome,
install on your device, test what work and what does not, google for solutions on the bugs you find, post solution here, i will aplly it to the next version, that way we can have a cm9 working 100% in very little time
in the case you can post, write a message to me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
to do next:
-correct google play (solved)
-camera
test it
hal_2000
Huawei isn't to blame I think. I don't think there are many QSD8250 devices that made it past Gingerbread. Acer (Liquid, Liquid E) and HTC (Desire) left their devices on Froyo. Dell (Streak 5) moved up to Gingerbread.
I have given my S7 away to a family member and won't be changing the firmware, but thanks for putting this together.
That's a weird looking ro.build.fingerprint you have there. Fix in cm.mk for build. Play Store also freaks out if you have a date too far from the present.
xaueious said:
Huawei isn't to blame I think. I don't think there are many QSD8250 devices that made it past Gingerbread. Acer (Liquid, Liquid E) and HTC (Desire) left their devices on Froyo. Dell (Streak 5) moved up to Gingerbread.
I have given my S7 away to a family member and won't be changing the firmware, but thanks for putting this together.
That's a weird looking ro.build.fingerprint you have there. Fix in cm.mk for build. Play Store also freaks out if you have a date too far from the present.
Click to expand...
Click to collapse
Hi xaueious, when i bought my s7 it came with android 2.1, some time after huawei lunch android 2.2 for asia, i had to wait for a suedish user to hack it and lunch it for europe, they could lunch android 2.3 but they where not interest, that why i said huawei suck, other manufactures realeases updates for they clients, but not huawei.
the fingerprint of the build has to do with the system i came up with to test things, i started with asturel base devices files but that is for the slim, so i had to test what option worked or not, it took dozens of test and tries, to get it to work.
i got the google play problem solve, see post 1, and streaming to
I'm close to get a 100% working rom.
test it if you can, and help me solve the bugs if you find any, enjoy.
hal_2000
I installed your rom on my s7-105 but now it's not starting proper anymore. I see the word ANDROID and I can hear a small click every second but nothing more... what's wrong?
---------- Post added at 04:07 PM ---------- Previous post was at 03:53 PM ----------
After a re-boot I get the message "Update failed! Please retry!" No matter which key combination I try (vol+ & power, menue&green&power, oder vol+&vol-&power) this is all that I get!!!!!!! HELP PLEASE!!! What can I do now?????? How can I get back into CWM to reinstall a rom??????
after some try & error I found out that with the key combination back&red key & power I can make the device to boot, I see the words Ideos and later android again but that's all. It's not going on. I have no idea how I can install an older rom now....
grka said:
I installed your rom on my s7-105 but now it's not starting proper anymore. I see the word ANDROID and I can hear a small click every second but nothing more... what's wrong?
---------- Post added at 04:07 PM ---------- Previous post was at 03:53 PM ----------
After a re-boot I get the message "Update failed! Please retry!" No matter which key combination I try (vol+ & power, menue&green&power, oder vol+&vol-&power) this is all that I get!!!!!!! HELP PLEASE!!! What can I do now?????? How can I get back into CWM to reinstall a rom??????
after some try & error I found out that with the key combination back&red key & power I can make the device to boot, I see the words Ideos and later android again but that's all. It's not going on. I have no idea how I can install an older rom now....
Click to expand...
Click to collapse
Sounds like a boot loop. What ROM did you come from? You should be coming from Android 2.2, not 2.1.
Here's a list of stock firmware to use: http://johnnyparanoia.blogspot.co.uk/2012/04/huawei-s7-tablet-firmware-list.html
Install procedure for stock: http://www.androidtablets.net/forum...d-2-2-2-dual-camera-s7-s7v100r001c98b021.html
xaueious said:
Sounds like a boot loop. What ROM did you come from? You should be coming from Android 2.2, not 2.1.
Here's a list of stock firmware to use: http://johnnyparanoia.blogspot.co.uk/2012/04/huawei-s7-tablet-firmware-list.html
Install procedure for stock: http://www.androidtablets.net/forum...d-2-2-2-dual-camera-s7-s7v100r001c98b021.html
Click to expand...
Click to collapse
To be honest, I can't say it for sure which one I had. In the status menue it said "2.1 update 1" Whatever this means. I had problems to install the clockworkmod I finally found this ROM: rom tri_zet. With that I could install clockworkmod and reboot the tablet into recovery mode. Then I installed this rom here and run into the problem.
Last night I finally managed to install the official swedish ROM 2.2.2. With that my tablet is running again.
Do you think with that one I could make another try to install this rom now? How can I install the clockworkmode now? Maybe the tri_zet rom was the cause of the problem...
grka said:
To be honest, I can't say it for sure which one I had. In the status menue it said "2.1 update 1" Whatever this means. I had problems to install the clockworkmod I finally found this ROM: rom tri_zet. With that I could install clockworkmod and reboot the tablet into recovery mode. Then I installed this rom here and run into the problem.
Last night I finally managed to install the official swedish ROM 2.2.2. With that my tablet is running again.
Do you think with that one I could make another try to install this rom now? How can I install the clockworkmode now? Maybe the tri_zet rom was the cause of the problem...
Click to expand...
Click to collapse
Hi grka, i tryed tri_zet but i didnt liked so i used the swedish ROM 2.2.2 until recently.
My advice install cwm 6.0.1, backup and then when install, clear cache and data, then intall my rom it should work
If you get problems again restore from bacup.
1º install the rom, let it boot, after sucessul boot install gaps to make goople play work.
If you need more help ask.
hal_2000
hal_2000 said:
Hi grka, i tryed tri_zet but i didnt liked so i used the swedish ROM 2.2.2 until recently.
My advice install cwm 6.0.1, backup and then when install, clear cache and data, then intall my rom it should work
If you get problems again restore from bacup.
1º install the rom, let it boot, after sucessul boot install gaps to make goople play work.
If you need more help ask.
hal_2000
Click to expand...
Click to collapse
Can you please tell me where to download cwm 6.0.1 and how to install it? I spend some hours with downloading different files and trying to install them without success.
grka said:
Can you please tell me where to download cwm 6.0.1 and how to install it? I spend some hours with downloading different files and trying to install them without success.
Click to expand...
Click to collapse
Hi, follow this steps:
1-boot in fastboot, with device power down, click vol up+home+power , fastboot apears in screen
2-connect s7 to pc
3-extract the zip file
4-in a dos text console inside the dir where are the files execute: "fastboot flash recovery s7-recovery-v601.img"
5-to reboot "fastboot reboot"
to go to cwm, with device power down, menu+call (green key) + power on
this commands work in a windows xp, never tryied in win 7 or 8.
More help ask,
hal_2000
Hal2000 can you provide a fastboot flashable system.img?
Thank you i will test your Rom next week.
threader said:
Hal2000 can you provide a fastboot flashable system.img?
Click to expand...
Click to collapse
Hi threader, i didnt save the img file, so i compile one today with my 53 source files, here is the link: https://docs.google.com/file/d/0B9OIKoN0knUtSXU5Tm9XZUYzYms/edit?usp=sharing
one question. do you know how i can have (make) a system.img file in ext2 format, insted of a yaff2 ?
Hal_2000
I think there is a flag to make the userdata ext4 , but do not make it ext2! It is prone to dataloss if not unmounted properly, it is better to compile in ext3 and 4 support in to the kernel. But i believe if im not mistaken i have seen options to make ext images in the codeaurora sources
Under BoardConfig.mk, TARGET_USERIMAGES_USE_EXT4
Relevant: https://groups.google.com/forum/?fromgroups=#!topic/android-building/wdV3GIe_XC4
The update.zip should be sufficient for most users. Shouldn't need to provide fastboot images.
build/core/Makefile contains the rules to generate the boot, userdata,
and system images. The choice of file system for the two latter is
determined by the setting of the TARGET_USERIMAGES_USE_EXT[234]
variables, so to get ext4 for your system and userdata images you can
say
TARGET_USERIMAGES_USE_EXT4 := true
in e.g. BoardConfig.mk.
Click to expand...
Click to collapse
For the usb mount, I don't really know how to fix this at all, but the is the Acer Liquid similar? https://github.com/thepasto/liquidCM_devicetree/blob/master/acer/liquid/BoardConfig.mk
BOARD_USE_USB_MASS_STORAGE_SWITCH := true
TARGET_USE_CUSTOM_LUN_FILE_PATH := "/sys/devices/platform/msm_hsusb/gadget/lun"
(lun path needs to be fixed to match S7. I remember changing this when I kanged recovery)
xaueious said:
Under BoardConfig.mk, TARGET_USERIMAGES_USE_EXT4
Hi xaueious, thanks for those tips, always learning in this forum.
One question, is there a manual where i can learn about all the options of config files in cm9 or cm7 ?
hal_2000
Click to expand...
Click to collapse
hal_2000 said:
xaueious said:
Under BoardConfig.mk, TARGET_USERIMAGES_USE_EXT4
Hi xaueious, thanks for those tips, always learning in this forum.
One question, is there a manual where i can learn about all the options of config files in cm9 or cm7 ?
hal_2000
Click to expand...
Click to collapse
I'm not an expert at CM. I just worked on building one very specific platform and know where some files are... But from what I know...
For Android platform: http://elinux.org/Android_Build_System and https://android.googlesource.com/platform/build/+/master/core/build-system.html
If you modify specific packages, mm and mmm are nice tools to use. For building, make otapackage does a lot more crap than just making the target images (make bootimage, make systemimage). Enabling CCACHE is supposed to help with build speed too. Also consider stripping the unnecessary languages during development, and stuff builds a lot faster (PRODUCT_LOCALE flag), because a ton of time is spent building together strings.
Originally build options are mostly in /build/. CM has some new options in there, but I am not sure if they add new ones elsewhere. Other things to pay attention to are the .prop options that CM has added. Those things are littered all over and don't have documentation, but at least git commits are easy to follow.
Click to expand...
Click to collapse
Hi, thank you,
Just in case someone else as same question, TARGET_USERIMAGES_USE_EXT4 in cm9 only acepts ext4 no ext2 or ext3, i tryied all tree options.
Great tips, as always thank for taking the time to anser my questions.
hal_2000
Just installed on my S7 107 Australian version. Excellent work hal_2000. I think after install your rom , i hear some times a crackling sound.
Waiting for a fix for camera
kosmasgr said:
Just installed on my S7 107 Australian version. Excellent work hal_2000. I think after install your rom , i hear some times a crackling sound.
Waiting for a fix for camera
Click to expand...
Click to collapse
Hi, kosmasgr, the audio same times gives a click, is a little bug, the device source i used is from asturel and his files are for the slim version, i'm trying to fix the camera its more critical then the audio bug.
enjoy cm9.
hal_2000
The click is a problem from kernel that Huawei provided for 2.2.2. Kernel source is generic for both version fat and slim.
NOTE: this OP subject was originally "[HELP] ZTE nubia Z7 Max (NX505J) stock ROM v3.09 update report";
- for the "Upgrade to paolothlw8's Unofficial CM12.1 Lollipop v5.1.1 V3 report", see post #22.
- for the Stock v3.19 update, see post #4.
I updated my Nubia Z7 Max from BB72's v1.64 custom KitKat 4.4.2 ROM directly to the latest stock Nubia v3.09, with Lollipop 5.0.
I want to leave here a brief account, so others know this can be done and it is not an overly complicated procedure. But, please, pay attention, because this will completely reformat and factory reset your device -- so, if you want to keep anything on the phone, backup before!
For starters, the downloads and instructions I used (mostly ):
Nubia Z7 Max v3.09 (free registration required for download)
http://www.needrom.com/download/nubia-z7-max-v3-09/
Be sure to access *#7678# dialer menu to enable both ports before and after flashing!
Needrom instructions are quite detailed and accurate, so I'll just summarize the main steps:
Install ZTE mobile USB drivers. (I used 'Drivers All In One Tool By Tigreos')
Download and install 'Nubia Tool Updater V2.0.0' in your Windows computer.
Download 'NX505J_CNCommon_V3.09.rar' file on your computer and unpack.
Run the installed 'Nubia Tool Updater V2.0.0' as administrator (right click...) and select the path were you unpacked NX505J_CNCommon_V3.09.rar.
Watch Needrom's pictures carefully to know when you're ready to proceed (summary picture below, you might need a few tries...).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The remaining button is "Open"......
My findings:
- Drivers MUST be updated for this to work, so you'll have to uninstall previous versions;
- The phone must be connected to computer in powered state, before the Updater is run;
- I had two hiccups after installation, because (I thought) the phone didn't boot and got stuck in the Chinese red letters after the boot animation;
- I solved this by connecting phone to computer again, a Chinese message with a counter appeared, and I let it finish (it counted to 21);
- Tigreos tool also provides for TWRP v2.8.6.0 quick installation (reboot required);
- TWRP provides ROOT (reboot required);
- Even after rooting adb doesn't push files (system RO, no ROOT in shell), so I needed an SD card to get GApps on phone;
- This is caused by ROM being a production build (you'll get a message saying thus: "adbd cannot run as root in production builds");
- After you flash GApps via TWRP, setup and get updated busybox from the Play store, as well as [THREAD="1687590"]adbd-insecure[/THREAD] to solve the problem;
- Not all languages are present (I use English) and some features will be presented with Chinese characters -- so, for a smoother experience, some tweaking will be required...
All in all a fast and stable new start for this great phone, which is being let down for the lack of Western locales support.
Bear in mind that various other information sources exist here at the forum, as well as elsewhere; I'll just list a couple here for the benefit of newcomers...
[THREAD="3053880"][Tutorial] [Root] [Upgrade] [4.4-->5.0] ZTE Nubia Z7 Max to Lollipop 5.0[/THREAD]
Very detailed report by user craagz of the upgrade procedure from stock v1.57 (KK 4.4.2) to v2.13 (Lollipop 5.0).
[THREAD="3100542"]Tuto installation rom stock v 3.09 nubia z7 max[/THREAD]
French(!) tutorial by user hayastan06 of installation of the stock ROM v3.09 (Lollipo 5.0)
For further info on the Nubia Z7 Max, search the present Nubia forums (http://forum.xda-developers.com/zte-z7) or check my dedicated index post ([THREAD="2961145"][INDEX] ZTE nubia Z7 Max[/THREAD]).
I thought I'd follow up by posting here some screenshots as well as talking about some of the changes and tweaks I have been doing. So first here are the screen captures of the system details after the upgrade, as well of the AnTuTu benchmark.
System details
AnTuTu Global Score
AnTuTu Comparison Chart
EDIT: list of ROM included mostly Chinese apps I have removed with Titanium Backup without major(!) problems...
Amap.apk
Baidu Map.apk
DianPing.apk
MeiTuan.apk
QQ.apk
Qunar Travel.apk
Sogou Input Method.apk
Sohu TV.apk
Tencent Video.apk
Today's Headline.apk
vip.com.apk
WeChat.apk
Weibo.apk
Mostly Chinese apps I was unable to remove/replace because they caused stuff I need to stop working:
nubia_Music.apk (replaces default Android Music)
nubia_Tms.apk (replaces the default Android browser, but is in fact QQ browser, which I didn't manage to replace with either AOSP or CM default browser).
(!) Be forewarned, though, that there might be unforeseen complications...
Another thing: I seem to have lost the ability to send audio file metadata (filenames, ID3 tags and such) over Bluetooth. If anyone happens to know how to solve, please post. TIA.
Upgrade path to Stock v3.19 successfully completed
As the title implies, I have now upgraded my device to the latest Stock version being offered on Needrom.com.
I lost hours at the beginning because Nubia Upgrade Tool kept giving me the "Internal Modem Error" (see the Italian instructions for solving it here)...
So here's the upgrades list (ATTENTION: serially upgrading appears to be mandatory and you always have to unroot via modded TWRP from v3.15 up):
Stock v3.15 -- http://www.needrom.com/download/nubia-z7-max-v3-15/
Stock v3.17 -- http://www.needrom.com/download/z7-max/
Stock v3.18 -- http://www.needrom.com/download/ota-update-v3-18/
Stock v3.19 -- http://www.needrom.com/download/ota-update-v3-19/
After completion I installed GApps (Pico v5, from first link above) and, for more governors and tweaking options, the NZ7ML kernel v1.3 (the only Lollipop compatible version!).
The final app list (user+system) after GApps installation, updating and debloating (uninstall of every Chinese user app) is at http://pastebin.com/w9DxJMuq.
One of the benefits I am already seeing is improved battery -- only 2% gone after 7 hours, with no screen time...
How do we flash 3.17 over 3.15? The instructions are not clear on Needrom and dont want to end up with a bricked device. Can you please help?
linom said:
How do we flash 3.17 over 3.15? The instructions are not clear on Needrom and dont want to end up with a bricked device. Can you please help?
Click to expand...
Click to collapse
sky walker @ Needrom.com said:
Installation process:
1.-Execute .exe, and install TWRP with option 2.
2.-Unroot phone, this function is in special TWRP.
3.-Flash v3.17
Click to expand...
Click to collapse
There are two downloads: "Official Stock Z7 Max v.3.17" is the OTA ROM update, and "TWRP special OTA", which is a modded TWRP recovery installer that you need to put on the phone before upgrading.
Copy the first package to your phone storage -- remembering where you put it; for easy retrieval, my advice is to put it at the root of the phone's internal storage.
Unpack the second package to a folder on your computer and execute the only executable you'll find inside as administrator; if the phone drivers are installed and an ADB connection is achieved, upon pressing "2" the upgrade to the modded TWRP recovery will be performed.
Reboot to Recovery and you should see the TWRP recovery v2.8.6.0 modded by Stalence (it will ask for language settings, choose English, as I summon you don't understand Chinese).
Touch the "Advanced" button, then "Stalence Tools" and "Unroot" -- it will tell you if it succeeded; re-rooting is just a matter of choosing the appropriate option.
Return to the initial screen (touch "Home" or press back button until you arrive), touch "Install", locate the OTA ROM update package and swipe to flash.
In case any of these steps shows some error, just reboot to recovery and do it again (repeat the step).
After doing all, reboot to system and be very, very patient, because it will take a long time to finish booting... Done! :fingers-crossed:
and you can also download Official Stock Z7 Max v.3.20 from here (853.1 MB) and just flash with any recovery
Any changelog for v3.20?
Directly updated to 3.20
And what is the procedure for updating to 3.20? Does it require 3.19 or it can be directly installed from 3.15?
I flashed 3.20 over 3.15 using TWRP and its directly updated. Working fine as of now. Yet to see the improvements over 3.15. Thanks all!
hi. can someone help me out and upload the drivers in the phone itself somewhere? all the available drivers on the web are incompatible with my z7 max. the only one that worked was the one inside the phone. when i installed cm 12, apparently i lost the driver too. i would really appreciate it if someone could upload the driver from the virtual cd-rom the z7max creates. thanks.
i've attached it to this post. hopefully it takes the attachment.
mszi said:
hi. can someone help me out and upload the drivers in the phone itself somewhere? all the available drivers on the web are incompatible with my z7 max. the only one that worked was the one inside the phone. when i installed cm 12, apparently i lost the driver too. i would really appreciate it if someone could upload the driver from the virtual cd-rom the z7max creates. thanks.
Click to expand...
Click to collapse
Thanks for that tp2droid -- link added to [THREAD="2961145"]Z7 Max Index post[/THREAD]... :good:
Care to mention from which ROM version were these drivers extracted from? And what version do they display?
mszi said:
hi. can someone help me out and upload the drivers in the phone itself somewhere? all the available drivers on the web are incompatible with my z7 max. the only one that worked was the one inside the phone. when i installed cm 12, apparently i lost the driver too. i would really appreciate it if someone could upload the driver from the virtual cd-rom the z7max creates. thanks.
Click to expand...
Click to collapse
Next time, please avoid double-posting like you just did. Better yet, open up a new thread with your request to improve visibility... :angel:
thanks. i apologize for that, i was really frustrated with my phone and in a hurry. i managed to get them after all and installed the new rom (3.15). i just want to highlight something that was mentioned in installation guides, but should be mentioned more than once and with a very big RED FONT!!
disconnect every external hard disk and flash drive from your computer before starting the installation. i almost lost 4 tbs of data on 2 hard disks because i didn't pay attention to this. the app will erase every partition on your external hdd and might create 20-30 partitions on it! and if that happens getting your data back is possible using partition recovery software like testdisk, partition find&mount ...etc.
oops, totally forgot about that. if i'm not mistaken, it was from (NX505J_CNCommon_V2.13) which was the lollipop beta (very unstable).
i have since already updated my phone to v3.15.
v3.15 looks stable so far. from the nubia.cn forums, it seems like anything above 3.15 has been buggy for them (from what my google translate says). so, i have stayed on 3.15.
Amazingly, the best thing so far is that my notifications are all working and battery life does seem to be a bit better. Most of the apps I use also look to be staying resident better and
crashing less.
The built in music player does still seem buggy. Seems to stop/crash quite a bit (especially when I swap over to a game which has music turned off).
pnin said:
Thanks for that tp2droid -- link added to [THREAD="2961145"]Z7 Max Index post[/THREAD]... :good:
Care to mention from which ROM version were these drivers extracted from? And what version do they display?
Next time, please avoid double-posting like you just did. Better yet, open up a new thread with your request to improve visibility... :angel:
Click to expand...
Click to collapse
tp2droid said:
if i'm not mistaken, it was from (NX505J_CNCommon_V2.13) which was the lollipop beta (very unstable).
i have since already updated my phone to v3.15.
Click to expand...
Click to collapse
Thanks for clearing that. :good:
tp2droid said:
v3.15 looks stable so far. from the nubia.cn forums, it seems like anything above 3.15 has been buggy for them (from what my google translate says). so, i have stayed on 3.15.
Amazingly, the best thing so far is that my notifications are all working and battery life does seem to be a bit better. Most of the apps I use also look to be staying resident better and crashing less.
Click to expand...
Click to collapse
As the thread implies, I'm now on v3.19, which I find by far to be the best I have tried (including vanilla stock and BB72 rehashes). Maybe the fact that I run paolothlw8's modded kernel is the key factor here, I don't know.
Now, if only it wasn't bridled with so many Chinese (cr)Apps... :silly:
tp2droid said:
The built in music player does still seem buggy. Seems to stop/crash quite a bit (especially when I swap over to a game which has music turned off).
Click to expand...
Click to collapse
Someone complained of the same at Adroidiani, so I took the precaution of keeping the Nubia Music APK shared as solution -- you can find it at http://mir.cr/PWWLWUYN...
I haven't tested it, since the version in the current ROM is the best ever for me, but you might want to try it...
And please do tell us if you do.
I am on version 3.15 can I update it directly to v.3.19 or I need to go step by step for updating it
Sent from my MI 4W using Tapatalk
---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------
On flashing version 3.09 and 3.15 and after installing gapps from needrom or minimal gapps from xda then after resetting I always stuck at cyanogen like startup screen that allow me to select country screen after Nubia startup finished just before loading homescreen . without gapps I have reset it many times no problem
Please help in need gapps that support v3.09
Sent from my MI 4W using Tapatalk
sandycool123 said:
I am on version 3.15 can I update it directly to v.3.19 or I need to go step by step for updating it
Sent from my MI 4W using Tapatalk
---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------
On flashing version 3.09 and 3.15 and after installing gapps from needrom or minimal gapps from xda then after resetting I always stuck at cyanogen like startup screen that allow me to select country screen after Nubia startup finished just before loading homescreen . without gapps I have reset it many times no problem
Please help in need gapps that support v3.09
Sent from my MI 4W using Tapatalk
Click to expand...
Click to collapse
Sent from my MI 4W using Tapatalk
Is that the nubia setup wizard? I don't remember it having UK as a country to select ... I thought it was just language. Which 309 or 315 did you install? I had no issues install 315 from needrom and then using the paranoidandroid link for gapps. Maybe try it again?
also, you don't need to apply gapps right away. try letting the nubia go through setup wizard first. then go the temporary recovery and install gapps later (if you haven't tried that)
Thanks for this guide and your support.
I used it to go from 1.59 ->1.64 ->3.09 ->3.22
Had some time consuming issues along the way (4-5 hours..) - bootloop when going from 1.59 ->1.64 and loosing IMEI when going from 3.09-> 3.22.
the first issue was finally solved by flashing stock ROM from side load and the second issue was solved by extracting the nv.qcn file from the nubia backup folder under C: and writing it to the phone using QPST tools.
So if anyone hit one of these walls..
Does anyone have any issues with the bluetooth and WiFi?
I'm having an issue with the bluetooth where i can't pair things as it doesn't bring up the popup screen to write the PIN.
The WiFi connection is not stable.
pnin said:
After completion I installed GApps (Pico v5, from first link above) and, for more governors and tweaking options, the NZ7ML kernel v1.3 (the only Lollipop compatible version!).
The final app list (user+system) after GApps installation, updating and debloating (uninstall of every Chinese user app) is at http://pastebin.com/w9DxJMuq.
One of the benefits I am already seeing is improved battery -- only 2% gone after 7 hours, with no screen time...
Click to expand...
Click to collapse
Hi Pnin
which parameters did you put into the kernel? (I'm using Trickster mod)
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's posted below is a work in progress, but it should suffice to unblock efforts to build custom ROMs for this inexpensive tablet. Many thanks to @mehanik6 on 4PDA for blazing the trail.
Notes:
The current process requires you to reset to factory defaults to remove file-based encryption. Remember to backup your data!
Custom kernels are specific to OEM releases, and rely on the latest posted kernel source.
This is unofficial and unsupported, so the usual caveats apply. Since we don't mess with the bootloader, you should be able recover from any problems...but nothing is guaranteed.
Not working:
Support for file-based encryption
Downloads:
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.tar.md5 (Odin tarball)
twrp-3.5.0_9-0-T290XXU3BTI2-20210102.img
Build archives:
Android File Host
Change Log:
v3.5.0_9-0: (2021-01-02)
Updated to T290XXU3BTI2 posted kernel source.
Updated to TWRP 3.5.0 release built from android-9.0 branch.
v3.4.0-1: (2020-12-09)
New custom T290XXS3ATC1 kernel that actually fixes MTP support.
v3.4.0-0: (2020-12-04)
Included legacy aboot and vaultkeeper in tarball to allow Odin flash on Android 10 OEM firmware.
v3.4.0-0: (2020-11-01)
Initial release based on T290XXS3ATC1 OEM kernel
Fixed MTP support
Instructions:
From OEM stock firmware:
Unlock bootloader
Hold Vol Up & Vol Down buttons during restart to enter Download mode
Install TWRP to AP with Odin
Hold Power & Vol Up buttons during restart to enter TWRP recovery
Install latest Multidisabler from TWRP
Wipe->Format Data
Reboot to system
From existing TWRP install: (No need for data wipe.)
Hold Power & Vol Up during restart to enter TWRP recovery
Tap Install->Install Image, select your image (.img) file, pick Recovery partition, and then swipe to install
Reboot to system
What about rooting with Magisk?
These images are not supplied pre-rooted with Magisk, since it's against the terms of use laid out by Magisk's developer, John Wu. To root the TWRP image yourself, simply use Magisk Manager to Select and Patch a File. More details on this process are available from @ianmacd's topic for the Galaxy S10 series here.
Source:
android_device_samsung_gtowifi
Donations:
Your support is always appreciated! Just click here.
After weeks of waiting Samsung has finally provided the Source for the Q update. Is there anyway you can update the Kernel base for the Q source?
Source is here: https://opensource.samsung.com/uploadSearch?searchValue=T290
Thank you!
jimbo77 said:
After weeks of waiting Samsung has finally provided the Source for the Q update. Is there anyway you can update the Kernel base for the Q source?
Source is here: https://opensource.samsung.com/uploadSearch?searchValue=T290
Thank you!
Click to expand...
Click to collapse
Yes, I've been requesting this since I got my SM-T290 in mid-October (when it went on sale for $89 at Costco) and Samsung finally posted it on Monday, along with the SM-T500. I'm actually building the custom kernel right now and should have an update for TWRP and a Nexus Stock custom ROM very soon.
UPDATE: Samsung seems to have changed the bootloader in Android 10 so that it won't support custom recovery even if the bootloader is unlocked and we substitute an empty vbmeta.img. This is another one of those Samsung VaultKeeper "features" that I find infuriating.
UGH!! I own both of these tablets (290 and 500) and just rooted the 500. I was hoping there would be some some custom ROMs coming out early next year for the 500.
Well, at least with the SM-T290 we can roll back to the Android 9 bootloader (minimally aboot and vaultkeeper), but that might not be an option with the SM-T500. We'll find out this weekend when I attempt to build TWRP for that newer tablet, which released with Android 10 and dynamic partitions.
The fact that you've been able to root the SM-T500 is promising, since Majisk modifies the recovery partition to do that.
Does this work with the Kids Edition of the SM-T290?
Really disappointed with this tablet, I figured since it only allows the user less than 32 gigs of space I could use an SD card in order for my daughter to download all the games she wants... only to find out there is no possible way to move any app to the SD whatsoever, actually the option to move apps to sd is not even greyed out it's just gone completely.
Doesn't seem to be many roms for the t290 available, and or if any roms out there could force that option back in.
sal84x said:
Does this work with the Kids Edition of the SM-T290?
Really disappointed with this tablet, I figured since it only allows the user less than 32 gigs of space I could use an SD card in order for my daughter to download all the games she wants... only to find out there is no possible way to move any app to the SD whatsoever, actually the option to move apps to sd is not even greyed out it's just gone completely.
Doesn't seem to be many roms for the t290 available, and or if any roms out there could force that option back in.
Click to expand...
Click to collapse
My Nexus Stock custom ROMs do allow formatting the SD as internal so that you can store apps on it (although there are performance issues with SD vs. EMMC to consider). I've already got this working on Android 9, but was holding out for the Android 10 kernel source to be posted so that we can roll out on the latest OEM firmware. This issue with the Q bootloader is a setback, but I expect that we'll be able to work around it.
The Kid's edition is just a characteristic of the OEM firmware you install, and the hardware is identical, so you should be fine after you upgrade to T290XXU3BTI2. If you really want the Kid's Edition splash screen, I suspect that T290UEU3BTI3 will work with custom ROMs based on T290XXU3BTI2 just fine.
Magendanz said:
My Nexus Stock custom ROMs do allow formatting the SD as internal so that you can store apps on it (although there are performance issues with SD vs. EMMC to consider). I've already got this working on Android 9, but was holding out for the Android 10 kernel source to be posted so that we can roll out on the latest OEM firmware. This issue with the Q bootloader is a setback, but I expect that we'll be able to work around it.
The Kid's edition is just a characteristic of the OEM firmware you install, and the hardware is identical, so you should be fine after you upgrade to T290XXU3BTI2. If you really want the Kid's Edition splash screen, I suspect that T290UEU3BTI3 will work with custom ROMs based on T290XXU3BTI2 just fine.
Click to expand...
Click to collapse
Oh ok thanks for breaking that down for me, I just was worried it wouldn't be compatible.
I would love to have a Nexus like experience on this thing, the more vanilla and pure Android, the better to me.
Would games on the sd card still play? Thats really my biggest reason as my daughter has already maxed out her space on it.
The last rooting/flashing I've done is from years back on an S3 and S5. I wish I could say my memory was good enough to feel confident about doing it.
So it would be unlock oem on developer mode, hook it up to a correct version of odin to put twrp in, then from twrp install magisk and also flash the rom right? I know I'm missing a ton of little details but just wanted to see what I could remember .
Thanks for your help
Quick Note: I just modified the Odin tarball to include legacy aboot and vaultkeeper images so that you can flash this custom recovery on Android 10 OEM firmware releases. The recovery image itself is unchanged.
sal84x said:
The last rooting/flashing I've done is from years back on an S3 and S5. I wish I could say my memory was good enough to feel confident about doing it.
So it would be unlock oem on developer mode, hook it up to a correct version of odin to put twrp in, then from twrp install magisk and also flash the rom right? I know I'm missing a ton of little details but just wanted to see what I could remember.
Click to expand...
Click to collapse
Well, a custom ROM and rooting a ROM are two very different things. You can look at my Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.1 (SM-T510) and see that it's very similar to Pixel Experience custom ROMs. Both are attempts to reproduce the "pure Nexus" experience, but with more modern Pixel boot animations, backgrounds, and Google apps.
Rooting can generally be done for any ROM now using Magisk to allow you to make changes, and there's a pretty good tutorial on that for the Galaxy Tab A7 here. My personal preference is not to root the system partition, but to simply make any changes using the TWRP File Manager where you already have root access.
Magendanz said:
Well, a custom ROM and rooting a ROM are two very different things. You can look at my Nexus Stock custom ROM for the 2019 Galaxy Tab A 10.1 (SM-T510) and see that it's very similar to Pixel Experience custom ROMs. Both are attempts to reproduce the "pure Nexus" experience, but with more modern Pixel boot animations, backgrounds, and Google apps.
Rooting can generally be done for any ROM now using Magisk to allow you to make changes, and there's a pretty good tutorial on that for the Galaxy Tab A7 here. My personal preference is not to root the system partition, but to simply make any changes using the TWRP File Manager where you already have root access.
Click to expand...
Click to collapse
Oh ok, i see.
Your Nexus rom for the SM-T510 looks awesome! Also, that Tab A7 tutorial is great.
On your original post, the first 2 downloads you have, the first one, "twrp-3.4.0-0-T290UES3ATC1-20201204.tar.md5 (Odin tarball)" that puts the custom recovery on the phone via ODIN. The second download, "twrp-3.4.0-0-T290UES3ATC1-20201101.img", is your Nexus Stock Rom for the T290, and is run from the TWRP recovery itself.
Does your T290 feel more responsive - less laggy with your Nexus rom?
sal84x said:
The second download, "twrp-3.4.0-0-T290UES3ATC1-20201101.img", is your Nexus Stock Rom for the T290, and is run from the TWRP recovery itself.
Click to expand...
Click to collapse
Samsung doesn't do flashing via fastboot, so the .img file is really only for incremental updates via TWRP.
sal84x said:
Does your T290 feel more responsive - less laggy with your Nexus rom?
Click to expand...
Click to collapse
I think so, but I might be biased and I haven't had time to run any performance tests. I just posted the first release, though, so you can judge for yourself.
BTW, the $89 Costco deal is back until 12/27.
Quick question, I am having an issue using Smart Switch to make backups for my T500 on my Win10 machine. Seems like it just started and hangs up on applications. Any ideas? Want to install a few Magisk modules but want a back up first.
Magendanz said:
BTW, the $89 Costco deal is back until 12/27.
Click to expand...
Click to collapse
Wow and a free 32GB SD card. Awesome deal! I got mine for $99 from BestBuy with no card.
Would this work on the LTE variants (SM-T295)? I have one of those and I'm kinda tired of the performance issues plaguing One UI on that tablet. :/
TenSeventy7 said:
Would this work on the LTE variants (SM-T295)? I have one of those and I'm kinda tired of the performance issues plaguing One UI on that tablet. :/
Click to expand...
Click to collapse
I've been told that it does, but I haven't confirmed it myself because I don't have an SM-T295.
The links seem to be broken?
TenSeventy7 said:
The links seem to be broken?
Click to expand...
Click to collapse
XDA Forum seems to have lost my last edit. Very strange, but I've tried to recreate it as best I could recall.
Magendanz said:
XDA Forum seems to have lost my last edit. Very strange, but I've tried to recreate it as best I could recall.
Click to expand...
Click to collapse
Okay, apparently the forum now forks a thread if you change the title. Bug or feature?
The new thread for TWRP v3.5.0 on the SM-T290 is here.
Any chance to get a working TWRP for latest stock firmware as of now?
Moto G8 Play was a phone launched in October 2019 and that curiously had few (or none) mods created, and until today, February 2021, no one had managed to at least root this device, with guides that bricked the device(or made it bootloop), or at least did not work, where even with the boot.img patched, the magisk manager could not get root access on the device. Thinking about it and after losing many nights trying to do everything to root my phone, I finally got it, and decided to write this guide for you, with proof of operation and a lot of joy in having made such progress,
but enough with ceremonies, let's go to the guide in fact.
What do I need to do before read this guide?
First of all, backup all your data, you will surely lose it if you don't.
Second, keep in mind that I am not responsible for any errors or damage to the device, keep in mind that this is a mod guide that makes you lose the warranty on your device. What I did worked for me, and theoretically it works for you as long as you do everything correctly.
And lastly and most importantly, unlock the bootloader of your device, if you don't do this, it is possible to brick and transform it into a paper weight for lack of attention. Thinking about it, I wrote a quick guide to unlock bootloader, follow the steps:
1. Go to settings> System> About phone> Build Number and follow the image
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Still in the settings, go to System> Advanced> Developer options and again follow the image:
3. On your computer, download platform-tools here and extract it to any folder you prefer. Also download and install Motorola USB drivers. After extracting and installing, open the platform-tools folder and copy the folder path, then open windows command prompt(cmd) and type the following commands:
in cmd, type cd and paste the path you copied, and hit enter. After that, type "adb devices" with your USB connected device(Remember to authorize USB debugging when connecting your device to the PC), if you did everything right, you will see something like this:
then type "adb reboot bootloader" to reboot your device for the correct mode. Once in bootloader mode, do not close cmd, it will still be useful. Access the motorola bootloader unlock site and follow the instructions provided. If you did everything right, your bootloader will appear with the status of flashing unlocked on the screen.
Ah, I talked about backup at the beginning, right? I'm glad you did the backup, because you just had your phone reset and data deleted. Now that you've installed everything right, let's start the hybridization process of your smartphone ... Let's install the Motorola One Macro ROM, which is basically the same thing as Moto G8 Play, but with more RAM, storage and 64- bit enabled, following this, download the One Macro Stock ROM here and extract it to the same folder as platform-tools:
It will look more or less like the photo above. After that, you will need a script to transform flashfile.xml into an appropriate flashfile.bat, and you can download this script here. Extract the .exe in the same folder as the platform-tools and the one macro rom, after this run and it will generate a flashfile.bat file. If your device is connected to the usb in bootloader mode you can now run the .bat and flash the rom on your device. Always remember to leave the battery with more than 50% charge to avoid problems and brick the device. If you did everything right, your device will start up normally. Configure, then go to settings and activate debugging following the steps at the beginning of the guide. You can notice that virtually your device is now a Motorola One Macro with the hardware of a Moto G8 Play, done that, let's go to the root process.
Copy the boot.img file from the platform-tools folder to any folder on your android. After that, install the magisk manager on the official website and open the app. In the magisk tab, click install and then "Select and Patch a file", select the boot.img file, after that make the selection process again, click the arrow and wait for magisk to finish the patch. After that, open google files and copy magisk_patched_XXXXX.img to your phone's root folder, and copy it to your computer again, in the platform-tools folder. Preferably rename it to an easier name, like magisk.img.
Do the process of opening cmd and pasting the folder path with the command "cd" before it. Then restart to bootloader mode as you learned above, and enter the command "fastboot flash boot_a magisk.img"
after finishing the process, type "fastboot flash boot_b magisk.img" and restart your device. If all goes well the magisk manager will detect the root and your phone will be ready.
This is the guide, I hope I have helped everyone who has gone so long without being able to root their devices. I wasted a night testing and writing this, so please consider giving feedback and if you post as a tutorial, leave the method credits to Daniel Santos (me).
Not works, when i flash the rom and the device restart, it give a message that is corrupt
CÆSAR said:
Not works, when i flash the rom and the device restart, it give a message that is corrupt
Click to expand...
Click to collapse
Did you unlock the bootloader correctly? If so, which version of Macro One did you use? If you want, I can pass the exact same version that I installed here and it works perfectly
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
CÆSAR said:
Yes, i've already unlocked the bootloader and runned a comand in adb to check it, and used the last rom available. One question, installing the one macro firmware can damage the device? Because a 64 bit OS need more resources than the 32 bit software from the g8 play.
Click to expand...
Click to collapse
well, i used the version of the image i sent and it works 100% normal. As for the system, Motorola One Macro and Moto G8 Play have the exact same architecture. They differ only from some sensors, RAM and internal storage. If you want more details of the process, you can send me a dm on twitter (@danadsees) and I can give you the necessary support. I've never tested with the latest version, which uses Android 10, but versions using Android 9 work normally
ok, i will try with that version, and a last question, you tried to play games after install that version?
FInnaly i tried with your version and it works, thx
Does the G8 Play work flawlessly with the One Macro Rom?
RandoMike said:
Does the G8 Play work flawlessly with the One Macro Rom?
Click to expand...
Click to collapse
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
CÆSAR said:
I think so. I didn't test it in depth, but in games performance looks to be better, and it worked normally in this few days that i've using it.
Click to expand...
Click to collapse
That's curious. I'm gonna try to root my phone. I hope not to brick it haha.
RandoMike said:
That's curious. I'm gonna try to root my phone. I hope no to brick it haha.
Click to expand...
Click to collapse
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
RandoMike said:
I ended hard bricking my device . However, I managed to repair it . I dunno what could go wrong xd. I hope this tutorial would make this forum alive again xdxd.
Click to expand...
Click to collapse
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
RandoMike said:
This is my third update. It worked! I can't really believe it!
I would tell all the people who want to do this to be careful. You can hard brick your cellphone, specially if you flash the preloader.bin image. Being that said, thank you, Daniel. Finally I found a tutorial that works haha!
Click to expand...
Click to collapse
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Daniel69cc said:
thank you for your trust. I missed many nights looking for a valid method and I had to develop it myself. this also makes it possible to use custom roms and recoveries from Macro One as well
Click to expand...
Click to collapse
Finally, there is some hope to revive this forum hahaha
Someone tryed with the android 10 version?
CÆSAR said:
Someone tryed with the android 10 version?
Click to expand...
Click to collapse
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
RandoMike said:
In my case, my cellphone just bootlooped. I think I also have to upgrade the fastboot, but I'm afraid it'll just make the phone hard brick. Or maybe I just need to try other Android 10 versions haha.
Click to expand...
Click to collapse
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
RandoMike said:
First update: I tried to restore the stock firmware of my Moto and it hard bricked (what a surprise, huh xD). I had to flash the original fastboot doing some stuff. Maybe we can upgrade to Android 10 doing that hardbrick trick (however, if you are not lucky, you can render the device unbootable), which allows you to reflash either the G8 Play's fastboot or the Macro one (it's weird that the fastboot of the One Macro also works on the G8 Play hahaha).
Second update: The One Macro Rom of Android 10 can't be flashed. It just gives me the error "sparse image size span overflow". I just proceeded to reflash the original Android 10 firmware of the G8 Play (I didn't wanna hardbrick it hahaha). It would be wonderful if anyone managed to solve or try to solve this problem.
Third update: I managed to root my G8 Play with its Stock Android 10 image! hahaha. I just flashed the "boot_a" slot with the original boot.img patched by magisk.
Click to expand...
Click to collapse
the root really works with the g8 play android 10 rom? i'm going to try
CÆSAR said:
the root really works with the g8 play android 10 rom? i'm going to try
Click to expand...
Click to collapse
Yep. I believed I would just get the "no bootable a/b slot" error, but it worked!
This guide is for moto g8 play or moto one macro or both ?
Team Win Recovery Project 3.5.0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Special Notes:
1. DON'T FORGET TO ENABLE "OEM UNLOCK" (located in Developers options).
2. KNOX will be tripped once you flashed custom binaries to your phone.
(Your warranty may be voided. However this may not affect you if your country forces Samsung to provide hardware warranty regardless of software status.)
3. Samsung Firmware OTA (aka System Updates) will no longer work once you flashed custom binaries.
(You can flash custom ROMs if you want to keep the OS up-to-date.)
4. All apps that use KNOX like Samsung pay, Secure Folder and maybe more will no more work
How to install:
Coming From Stock:
1. Download This TWRP Release and Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
2. Under Developer Options, Tick OEM Unlock. It will tell you to factory reset. Do it.
3. After the phone shuts down, press Vol + & - button and at the same time, insert a usb cable to phone connected to a PC.
4. Check KG Status. If it is Prenormal, reboot the phone and follow this guide : (1) How to bypass KG State and/or RMM state prenormal | XDA Developers Forums (xda-developers.com)
5. Zip the TWRP recovery image to tar format and put in the AP slot of Samsung Odin.
6. Flash and after the phone screen turns off, press vol+ and power button.
7. If there is "Set Warrenty Bit : recovery" text on the top left, success!
8. Format data, flash zip downloaded from above.
9. To boot stock rom, install magisk.
From Other Recovery:
Reboot to recovery and flash this TWRP image as recovery and reboot recovery.
ChangeLog:
2021/3/2 Inital Release
Sources:
Kernel : Junak/android_kernel_custom_a6plte (github.com)
Device Tree: roynatech2544/TWRP_device_samsung_a6plte (github.com)
Recovery Source : TeamWin (github.com)
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
NOTE :
I was developing custom roms for A6+ despite of my computer specs. But my phone's LCD went out and I can't test anymore... And it takes 1 day to build in i5-5200U (2C/4T) CPU and 8GB RAM.. Now I can only build TWRP.
where is the twrp file ?
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
CRDhani said:
where is the twrp file ?
Click to expand...
Click to collapse
Release :
Releases · roynatech2544/TWRP_device_samsung_a6plte (github.com)
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
little_beppo said:
Hi,
I'm new here, this method also works with bootloader 6 ? e.g. with the "A605FNXXU6CTH1"
Android 10, UI 2.0, are there any problems with rooting? Magisk or SU?
thanks for your replay
Click to expand...
Click to collapse
yes it works.
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Hello
Is this recovery for android 10?
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
abhisekh010 said:
Hello
Is this recovery for android 10?
Click to expand...
Click to collapse
Yes it is compiled in android 10 tree but recovery doesn't depend on android version..
Naddi2Niic3 said:
Hii, I followed a rooting guide before this one, it bricked my phone I had to flash stock rom.. now its back I still want to root it so that I can adopt my sd card as internal.. Can I please have a very clear step by step guide... Please..
I'm using a605fn
Click to expand...
Click to collapse
PM me
okwhateverok said:
I would like to see the same for the A600FN if possible.
Waiting for this for my device for a long time but keep up the good work for any model phone. thank you
Click to expand...
Click to collapse
I can help with that. I know what it feels like having no TWRP and custom rom. But you still need to test the TWRP. Because I don't have A600FN, and the LCD on my A6+ broke so I don't own a device launched in 2018. OK with testing?
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
okwhateverok said:
Thank you for your offer to help develop a recovery for the a600FN. It is about testing and im willing to help but at the moment my device is being used for daily stuff so i cant risk to much....
Any suggestions? Thank you and i will PM any next message.
Click to expand...
Click to collapse
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Thanks, ill hope there will be some users which ow the Galaxy A6 and not using this device as their main phone to be willing to test.
As a IT specialist myself i did try anything to at least help testing for this version of TWRP for our device. I did try to take several rom dumps with professional fabric software and hardware like software dongles but it was impossible to make a full rom dump.
With this said and knowing that a complete data wipe within TWRP is necessary to make the recovery find the internal storage makes it impossible for me to test no matter the fact that the biggest part of this recovery already exist and confirmed working.
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
nqnxev said:
I have A600FN and I could test that as soon as my OEM unlock button will be visible (above 10 days passed and still nothing...).
Click to expand...
Click to collapse
I could help with the OEM unlock button. What a waist of time these lost 10 days and still no OEM unlock button while the solution is easy...
Follow guide with screenshots: https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
And for those who could test on the A600 the recovery image is already uploaded within this thread thanks to Royna
I've tried that many times (no only that, but many similar guides) - and still nothing. From what I read, Samsung just fixed that "date & time" trick and I have to wait.
Ok that is strange, im on android 10 with One UI version 2.0 and got it working. If im allowed to post this link then the rom could be found here: https://www.sammobile.com/samsung/galaxy-a6/firmware/SM-A600FN/PHN/#SM-A600FN
You should do a clean flash without having the phone connected to the internet, not even once because it will do some synchronization. After the flash just follow the guide which could be found on the xda forum..
Thank you for a hint. Because of that I'm waiting so long already I'll wait till end of week and if things still will be the same then I'll try rom you've proposed. Thanks again.
Royna said:
I think it will work...? Because I will use kernel and dt from here. And it's verifyed working. I'm just building for new version
Can you test this?
Click to expand...
Click to collapse
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Adam7336 said:
i flashed that recovery image on my A600FN which has latest android 10 firmware , it caused a bootloop
Click to expand...
Click to collapse
Well because i don't own that device, it is highly experimental. I will try again.