Related
So by today (22.09.2014) is your phone oficialy renamed from "ZTE Red Bull V5" to "ZTE V5"
POSTING A PROBLEM
If you have some sort of problem with your device please please get us this info, so we could help you:
1-what rom/firmware are you using
2-what recovery
3-if you have rooted your device
4-what caused the problem
5-step by step description what you did before the problem shows up.
Hi i just made this thread to make a base for everyone who bought this (form me) superb phone.
So far we got root, custom recovery, and many chinese roms (based on Nubia UI, Color OS, LEWA OS, FROG OS...).
There are Mokee AOSP 4.4.4. rom in develpoment and CM11 in development, CM12 also.
2015.02.13 - Latest firmware is 1.17 (andorid 4.4.2, nubia UI2.5.1)!!!
Changelog(google translation from chineese):
-optimize the signal problem
-solving open U disk mode or restart the phone, ringtones revert to the default issue
into the video again, this video from one schedule to start playing the video
-update time management software, to solve the problem of the shutdown alarm clock does not ring
-media library interface, Pictures Pictures folder appear as a blank
-to use the gallery under OTG open unsupported file error
-switching to the media library interface, multiple exposure, suggesting that language View screenshot untranslated
-save the video recording status suspended again after recording, the Pause button to display the error
-optimization manually Focus
-video recording in the recording pause again, long display of detailed information is incorrect
-horizontal screen - portrait - horizontal screen operation, not full screen
-video player interface to open the USB mass storage press the return key error
here is link to my google drive. It contains stock roms from 0.50 to 1.12, GAPPS ect. Also contains tools to root and flash custom recovery.
MY GOOGLE DRIVE ZTE V9180 FOLDER
In my Google Drive there is also two custom recovery CWM and TWRP (thanx a lot to FAZERGOO from 4PDA.ru, here on XDA it is fazerg, so please thank him for his work)..the script in my root+recovery folder is updated, so you have option to flash CWM (6.0.5.1) or TWRP (2.8.0.0.)
here is list of commands you can dial in dialer and get some hidden menu and settings:
*#06# - displays IMEI
##36 - update server settings for OTA
*#*#4636#*#* - display phone information, battery information, battery history, usage statistics, WiFi information
*#406# - touch screen calibration
--proximity sensor calibration--
*#777# - no cover of proximity sensor
*#776# - cover proximity sensor with hand 2-5 cm above..so the bar is in the green
*# 405# - MHL test
to go to recovery you have to poweroff the phone and hold "vol+" and "power" for 2 sec
to go to safe mode....???
best resources for ROMS (chinese sites):
bbs.anzhi.com
www.tdbeta.cn
www.ztehn.com
And of course our friends from Russia thread:
www.4pda.ru
proDOOMmans mega drive where you can find all Mokee, CM11, PAC roms:
HERE! and dont forget to hit THANKS button for everyone who develop and help us to use this device!!!!
TIPS & TRICKS
-HOW TO CHANGE LCD DENSITY and switch to phablet UI!!! Beware, the camera app is little bit smaller then the screen, becaouse of the density, but still works well.
-HOW TO ADD ONE HAND FEATURE
-did you know that when holding home button on locked screen lights a flashlight?
-when you double tap home button on locked screen the time changes to media player controls?
-when you tap several times on any home screen your glas will broke?
-when you zoom out with two fingers on any home screen you will get into screen manager?
-in alarm clock app there is setting "power of alarm", when turned on, you can turn off your phone at night and the phone turns on by itself in the alarmclock time and wakes you up?
complete guide by navin_n
People always asking again and again on flashing ROMs, Recovery, GApps, Root etc. So, I have made detailed step by step guide for this. Hope now it will be clear to everyone for these processes:
BEFORE YOU DO ANYTHING FROM FOLLOWING, PLEASE MAKE ANANDROID BACKUP, BEST WITH TWRP!!!BECAUSE TWRP CAN MAKE BACKUP INCLUDING PRESIST AND MODEMST PARTITIONS!!![/CENTER]
GUIDE TO FLASH STOCK ROM:
NOTE:
1. Be sure to backup all important data (contacts, messages, call records, etc.) before proceeding
2. Ensure that Phone Battery is at least 40%.
3. Downloaded required STOCK ROM.
4. Phone with Stock Recovery.
STEPS:
1. Copy the downloaded zipped STOCK ROM to the root directory of External SD card or Internal SD card.
2. Power-off the phone.
3. Put the phone in the Recovery Mode and for this you need to press Vol+ and Power button at the same time for few secs and then release the Power Button.
4. In the Stock Recovery, perform wipe data/factory reset and wipe cache partition (In the menu, use +/- volume keys to scroll up/down & power button for confirmation).
5. Depending on which SD card you have copied the zipped STOCK ROM, choose "Apply update from /sdcard" or "Apply update from external /sdcard" accordingly.
6. Select the zipped STOCK ROM to flash.
7. Wait until you get the confirmation of successful flashing.
8. Reboot the phone by selecting "reboot system now".
9. DONE. (Initial boot may take some time so have patience.)
GUIDE TO INSTALL CUSTOM RECOVERY + CUSTOM ROM:
AS FOR CERTAIN REPORTS IT IS STRONGLY RECOMMENDED TO FLASH CWM RECOVERY IF YOU HAVE 1/8 VERSION
REQUIREMENTS:
1. Be sure to backup all important data (contacts, messages, call records, etc.) before proceeding.
2. Working Windows PC with ADB Drivers installed - without proper installation of drivers the process will not be successful.
3. Ensure that Phone Battery is at least 40%.
STEPS: (If you need only Custom Recovery, then follow the steps from 2 to 7, other steps you can skip)
1. Download the required zipped Custom ROM and copy it to the root directory of External SD card or Internal SD card.
2. Download the Recovery Tool zip file. (Link to download the Tool) . Make sure to download whole files. After that copy the zipped file to the root directory of C:\ or any place you prefer and then unzip the downloaded file.
3. Enable USB debuging mode. ("Menu Button" >> System settings(Settings) >> About phone(On the phone) >> Tap 6 times on Build number>>"Back button">> More >> Developer options >> Enable USB Debugging)
4. Connect the phone to the PC.
5. Go to the folder where you have unzipped the Recovery Tool file, and then execute the batch file "run.bat".
6. In PC, new window will open. Input your choice of Custom Recovery accordingly.
7. Follow the steps on-screen until all completes.
8. After completion, in the Fastboot menu, select "Boot recovery".
9. If the Custom Recovery was flashed succesfully, you will get CWM or TWRP recovery menu.
10. Perform wipe data/factory reset and wipe cache partition.
11. To flash the firmware: Select "Install ZIP" >> "choose zip from sdcard0 or sdcard1" depending on which SD card you have copied the ROM, external or internal >> Select Custom ROM >> Click Yes to flash selected ROM.
12. Wait until you get the confirmation of successful flashing.
13. Reboot the phone by selecting "reboot system now".
14. DONE. (Initial boot may take some time so have patience.)
GUIDE TO INSTALL GAPPs & ROOT:
REQUIREMENTS:
1. Backup all important data (contacts, messages, call records, etc.) before proceeding, if necessary.
2. Requires CUSTOM RECOVERY.(Mandatory)
STEPS:
1. Download appropriate flashable zipped GAPPS & ROOT files and copy it to the root directory of External SD card or Internal SD card.
2. Power-off the phone.
3. Put the phone in the CWM or TWRP Recovery Mode and for this you need to press Vol+ and Power button at the same time for few secs and then release the Power Button.
4. Flash the zipped files (one at a time): Select "Install ZIP" >> "choose zip from sdcard0 or sdcard1" depending on which SD card you have copied the file, external or internal >> Select Zipped File >> Click Yes to flash selected file.
(No need to do wipe data/factory reset and wipe cache partition)
5. After successful flashing, reboot the phone by selecting "reboot system now". If it ask to fix the permission when you reboot, select Yes.
7. Wait until you get the confirmation of successful flashing.
8. DONE. (Your phone will have GApps and Root Permission)
and don´t forget to hit thanx button to @navin_n, @fazerg and me maybe @DallasCZ
APPS taht can be remover (thanx navin_n)
If you have already Rooted your device then you can easily uninstall the system apps using "Root Uninstallers" available in Google Play.
However, for me , i prefer to use Root Explorer and delete the apps from system folder. The following apps are safe to delete but still i advise you to backup the files before deleting. If you use Root Explorer, make sure to change attribute of the system folder from Read Only (R/O) to Read Write (R/W) when deleting.
Be ware you make it on your own!! If there is also odex file, delete them too!!!
APPs that can be deleted:
folder --> /system/app
nubia_account.apk - only if you log in in nubia account (maybe you need this to use themes)
nubia_Calculator_v1.2.1.apk - calculator app (i dont like it so i installe another one and delete this)
nubia_Calendar_v1.0.apk - nubia calendar app
nubia_ClockWidget.apk - clock widget
nubia_Music.apk - nubia music player
nubia_myfile.apk - nubia file manager
nubia_NBSecurity.apk - nubia antivirus and system cleaner
nubia_NotePad_v1.1.5.apk - nubia notepad
nubia_zbiglauncher_v2.0.apk - nubia launcher for old people (everything is biiig)
NubiaPlatLogo_V1.0.0.apk - nubia lanim showing when you tap on NUBIA version in "about phone"
ZAppDataBackup.apk - nubia main app for backup your phone
ZDataBackup.apk - nubia backup app
ZQuickSearchBox.apk - nubia quick search box (if you install GAPPS it contains original google search box)
ZVideo.apk - very basic media player
If you dont use Live Wallpapers you cen delete the main app:
LiveWallpapersPicker.apk
and of course all livepaper apks
BasicDreams.apk
HoloSpiralWallpaper.apk
LiveWallpapers.apk
MagicSmokeWallpapers.apk
NoiseField.apk
PhaseBeam.apk
folder --> /system/preset_apps
TP_360AppStore_1.9.203.apk
TP_360Video_1.2.0_Nubia.apk
TP_BaiduInput_1000541a.apk
TP_baidumap_6.2.0.apk
TP_baiduvideo_5.3.0.apk
TP_gowhere_1044_131118_150501.apk
TP_iReader_2013122410.apk
TP_JdAndroid_2.6.0.apk
TP_QQ_4.2.apk
TP_QRCodeScaner_v1.0.apk
TP_tieba_5.5.2.apk
TP_Weibo_4.0.0_602.apk
TP_weixin_502.apk
Hi, I'm interested in buying this phone.. Could you tell me your first impressions?
It seems very good but I can't see any support for it, even if it has a Snapdragon 400..
Sent from my VOTO X2
DallasCZ said:
ROOT
the only way to root it so far is to run an Chinese exe, which will root your phone and install superuser (chinese one). Then you need to uninstall the superuser and install one from google play.
CWM
so far there is only chinese CWM 6.0.4.6..looking for someone who can make it english.
Click to expand...
Click to collapse
Hi, can you please provide me the exe file to root and explain me the process to root? I would be really grateful for your help! Thanks
I have WCDMA/GSM V5 3G 9180
ROOT CWM
Hello,
i made a simple bat file, which will root your phone, install custom recovery or original recovery.
here is the link: Dallas Google Drive.
you made everything on your own ..i am not responsible for any phone software/hardware damage.
jday17 said:
Hi, I'm interested in buying this phone.. Could you tell me your first impressions?
It seems very good but I can't see any support for it, even if it has a Snapdragon 400..
Sent from my VOTO X2
Click to expand...
Click to collapse
Hi,
there ar ea lot of Chinese phones, this phone is ment to be sell china only.
There are many forums but in Chinese.
I wrote a little review on gizchina.cz (is in Czech language,so use google translator)
TIP
For new users i recommend do this:
-boot your phone and see vhich version of formware you have (latest at this time is 0.50).
-If you have 0.44, then go to dialer and dial ##36. You get to the menu where you can select which server will be used for updates (at this time is 0.50 only for few people for feedback). then go to ybout phone and tap serach for updates and you get the update.
-after update is installed, go to about phone and tap 5times "build number" line , go back and go to "more" and "developer option" and turn on usb debugging.
-launch my root.bat, select root your phone and th ephone will reboot to bootloader and will be rooted.
-now you can install custom recovery (from my bat.file) it is bilangual CWM 6.0.4.9 recovery. Everything works fine as i used it.
-now after root and cwm recovery installed, make backup of your 0.50 rom and then you can proceed to delete bloatware (a lot of bloatware).
for rotted phones with CWM recovery:
if you want to make update from ZTE OTA, you have to load original recovery, the one in my package is not functional with update to 0.50 and above, so you have to flash from CWM recovery this package, then reboot and get the proper stock recovery, which will be functional with the update 0.44-0.50 and later.
DallasCZ said:
For new users i recommend do this:
-boot your phone and see vhich version of formware you have (latest at this time is 0.50).
-If you have 0.44, then go to dialer and dial ##36. You get to the menu where you can select which server will be used for updates (at this time is 0.50 only for few people for feedback). then go to ybout phone and tap serach for updates and you get the update.
-after update is installed, go to about phone and tap 5times "build number" line , go back and go to "more" and "developer option" and turn on usb debugging.
-launch my root.bat, select root your phone and th ephone will reboot to bootloader and will be rooted.
-now you can install custom recovery (from my bat.file) it is bilangual CWM 6.0.4.9 recovery. Everything works fine as i used it.
-now after root and cwm recovery installed, make backup of your 0.50 rom and then you can proceed to delete bloatware (a lot of bloatware).
for rotted phones with CWM recovery:
if you want to make update from ZTE OTA, you have to load original recovery, the one in my package is not functional with update to 0.50 and above, so you have to flash from CWM recovery , then reboot and get the proper stock recovery, which will be functional with the update 0.44-0.50 and later.
Click to expand...
Click to collapse
Thanks for the info! I'm currently updating to 0.5 and will let you know if I manage to root it too.
I`ve read the review and mine phone too has the squeaky back cover. It started squeaky after just few back panel removals. This is not a concern for me, but I wanted to ask you something else: How is you call quality? When I do calls the other side can hear me perfectly but the sound through my ear speaker is muffled and not very clear. Increasing the volume make it even worse. Do you experience such an issue?
-the back cover is really squeaky (i allready ordered another one)
-I am very happy vith the call quality. I had a nexus s whos volume vas up to 100%. Now i am about 60% and everything is loud and clear as i can hear
root and installing cwm is like a charm..i made it in the las 2 weeks (as i own the phone) about 10times
one Question: If you reboot the device do you also have the message "android is upgrading" every time no matter what you do or not do with the system?
DallasCZ said:
-the back cover is really squeaky (i allready ordered another one)
-I am very happy vith the call quality. I had a nexus s whos volume vas up to 100%. Now i am about 60% and everything is loud and clear as i can hear
root and installing cwm is like a charm..i made it in the las 2 weeks (as i own the phone) about 10times
one Question: If you reboot the device do you also have the message "android is upgrading" every time no matter what you do or not do with the system?
Click to expand...
Click to collapse
- I tried updating to 0.5 both through FOTA and with direclty downloaded update from the chinese official site to the sd card, but I always get some error (forgot what it was), will try tomorrow once again.
- My apps are upgrade after each reboot too. I was hoping that 0.5 will fix this issue, but It seems this is not the case.
- I'm on the hunt for a new back cover too, but I will wait for the official blue ones Share your thoughts on the one you purchased after a few days of usage
My only problem with the phone I experience is the bad incoming sound quality during calls. I will have try another sim card.
ps: boy this phone is a beauty
HuKuTo said:
- I tried updating to 0.5 both through FOTA and with direclty downloaded update from the chinese official site to the sd card, but I always get some error (forgot what it was), will try tomorrow once again.
- My apps are upgrade after each reboot too. I was hoping that 0.5 will fix this issue, but It seems this is not the case.
- I'm on the hunt for a new back cover too, but I will wait for the official blue ones Share your thoughts on the one you purchased after a few days of usage
My only problem with the phone I experience is the bad incoming sound quality during calls. I will have try another sim card.
ps: boy this phone is a beauty
Click to expand...
Click to collapse
Hi, can you please tell the name of chinese official site for our phone? thanks!
SITES IN cHINESE LANGUAGE
Hello,
so there are many sites. To see attachments you have to register to the sites, which is a little bit tricky due to instatnt need of translation in the registration process, but it can be done.
official with a lot of new information also from ZTE service:ztehn.com
the best for custom ROM and Recovery (development):anzhi.com
to see anzhi.com you need to add two adress in your windows hosts file see here
also some good information can be found here on myzte.cn
another tip
-If you get the "android is upgrading" on every boot, then you have to uninstall titanium backup, reboot, wait 3 minutes and let the system settle down, then install titanium again, reboot, and its done.
-if you want to restore WIFI access point and passwords form Titanium Backup, use backup from tar file, not from XML!!!
Waiting on a custom rom
Hello everyone,
I used the method I found at needrom.
It did the trick; the device was rooted, gapps installed, an multilangual.
But I didn't manage to install the latest update (50). I thought it was because the device was rooted, so I removed root, whitout succes, I am still not able to install the update.
Also I think the contact manager is buggy; newly added contacts dissapear after rebooting the device, it doesn't matter if I sync the device. I have to import my contacts from my SD card every time this happens.
So, I hope there comes a good custom rom for this device with this excellent hardware! I have Miui unofficiall on my Xiaomi Mi2s, it works like a charm. I hope soon this device appears on the list one of these days
update
-if you installed the ROm from needrom, i think you cannot upgrade to 0.50.
-on www.ztehn.com you can download the full 0.50 rom (only english and chinese language) this rom you can flash.
-contacts: If you are in contacts, press "more" and "advanced" and check the "default storage" it must be set to your google account. Then go back and check "display settings" and check which accounts are to show in contact list.
I had same problem and the problem was, that all new contact automaticly save to local storage and i have the local storage unchecked to display..so i havent seen my newly added contacts!!!
I have same issue
I have same isse. I dont hear anyone. But everyone hear me. i think that built in speaker doesnt work.
ZTE v5 DualSIM v1.06 beta released (4.4.2 + Nubia UI 2.0, package contains new recovery, H106 update package and G050 restore package)
http://pan.baidu.com/share/link?shareid=2878143782&uk=2436317143 Pass: [COLOR=#0640]j7cb
MD5:[/COLOR][COLOR=#0640]3C318AE402AC5424444F5862B540AF2D
[COLOR=#0640]Uploaded to my MEGA acc: link (1.06 unzipped too)
[COLOR=#0640]BETA release [COLOR=#0640]but seems stable (according to chinese forum feedbacks) I will try thi[COLOR=#0640]s next week, when i receive my v9180 2/8G. [/COLOR][/COLOR][/COLOR]
[/COLOR][/COLOR]
I sucessfully installed 1.06 and its looking good so far. The problem Im facing is the "No connection to google servers" error when I try to add my google account. There is no playstore and I tried to manually install it trhough .apk but again no luck. Have you guys managed to run the playstore with this new firmware?
install my gapps package trough cwm recovery.
Oi guys!
So for now i might be alone on this, but i am certain that some few of you have wondered on how to get Viper4Android to work on the Moto Z without flaws. I am here to give you a small guide, because i figured out how to fairly easy add V4A.
There are 3 simple steps, but they can (in case you haven't done the first one yet) take some time.
If you have already Unlocked your Bootloader, disabled Force_Encrypt (either by manually editing the boot.img or flashing @janjan his ROM), installed a RECOVERY like TWRP and ROOTED your device, then you can skip right ahead to STEP 3.
Also, before you go ahead, do a BACKUP of all your important data, as it will CERTAINLY be lost when unlocking the bootloader (this does not count for inserted microSD cards, but just to be safe, remove the microSD or backup your data somewhere else, like your PC or a cloud service).
One more heads-up: You NEED a USB-C Cable that you can connect to your PC, otherwise this guide will be useless for you. Also, all my commands listed in the upcomming guide are listed with " ", but ignore these when entering the commands in the Command Prompts.
STEP 1:
1: As for every Android phone, you need an Unlocked Bootloader and TWRP (and also ROOT, etc).
-1.1: Download the Motorola USB Drivers HERE, and the ADB Fastboot Driver/Tool HERE.
-1.2: Install the Motorola USB Drivers first, then install the ADB All-In-One Tool after that (When installing the ADB AIO, choose yes for all options).
-1.3: On your Moto Z, enable Developer Options by going into the Phone Settings, then the last "About Phone" option, and then scroll to the bottom where it says "Build Number". Tap that "bar" 7 times until it says that you unlocked the Developer Options menu.
-1.4: Go back into the Main Settings Menu of your Phone, and then right above the "About Phone", should be an option called "{ } Developer Options". Go in there, and right in the beginning is an option called "OEM unlocking". Enable that option (when it asks you for your PIN/Password/Pattern, just enter it).
-1.5: Scroll just a little further down in the Developer Options menu, and you will see a section called "Debugging", in which the first option is called "USB debugging". Enable that option as well.
-1.6: Now put your Moto Z into Fastboot Mode. You can do this either by connecting your Moto Z to the PC, then open a Command Prompt (look in Windows for CMD), and type "adb reboot bootloader", OR by turning your Moto Z completely off, and then turning it back on WHILE holding BOTH the Volume Down and Power Button (if your Moto Z turns off all the time, the second the Phone vibrates, let go off the buttons).
-1.7: Now that your Phone is in Fastboot Mode, you will have to connect it to your PC by a USB-C cable. If you have done that, open a Command Prompt in Windows (again, by typing CMD in the Windows Start Search), and type this: "fastboot oem get_unlock_data"
-1.8: You will end up getting a result that will look a little like this (the numbers do NOT work for you, don't try them for steps required later on):
$ fastboot oem get_unlock_data
(bootloader) 0A40040192024205#4C4D3556313230
(bootloader) 30373731363031303332323239#BD00
(bootloader) 8A672BA4746C2CE02328A2AC0C39F95
(bootloader) 1A3E5#1F53280002000000000000000
(bootloader) 0000000
-1.9: Copy the entire string you just got from the Command Prompt, and put it into any kind of Text Field or Text Editor. Remove the bootloader part, and also everything else, like [Info] or the likes, and same goes for empty spaces. The only thing you should be left with looks like this: 0A40040192024205#4C4D355631323030373731363031303332323239#BD008A672BA4746C2CE02328A2AC0C39F951A3E5#1F532800020000000000000000000000
-1.10: Now you go to THIS website to get the Unlock Code for your Phone (You will have to register at Motorola to be able to get the Unlock Code. It is easier if you just use Google+, it is much faster and you can skip the entire register process). There will be instructions there as well to guide you for how to enter the code, just in case you misunderstood my guide.
-1.11: Once you registered and entered the code, click the blue button below called "Can my device be unlocked?". Once Motorola confirms that your Moto Z can be unlocked, you click the "I agree" option, and then the "Request unlock key" button.
-1.12: You will get a pop-up telling you about it voiding your warranty, click "OK" on that one as well.
-1.13: Now, Motorola will tell you that they sent you the unlock code for your device to the E-Mail you registered with, so go and check your E-Mail account for that code.
-1.14: Copy the unlock code, go back to that Command Prompt (in case you closed it, open a new one), and enter this: "fastboot oem unlock UNLOCK_CODE_HERE" <<<< Where the UNLOCK_CODE_HERE means that you will have to replace this with the unlock key from your E-Mail.
-1.15: Now click ENTER, and your device will be Unlocked. After this, your device SHOULD reboot automatically, but if not, pick the REBOOT option in the Fastboot Mode Menu, and click the Power Button to confirm. From now on, every time you start your Phone, you will be greeted with the Unlocked Warning screen, but that is ok, nothing stopping your Phone from working or the likes.
-1.16: Let your Moto Z fully boot up, and when you have done that, shut it down again, and go back into Fastboot Mode using the above mentioned button combination.
-1.17: At this you will have to download the TWRP Recovery Image. You can find this for the Moto Z HERE, or HERE.
-1.18: Rename the downloaded file to just twrp.img, then go back to your Command Prompt (or open a new one), and enter this: "fastboot flash recovery twrp.img"
-1.19: Now let the RECOVERY be flashed, and then in the Fastboot Menu on your Moto Z, use the Volume Keys to navigate up and down, and navigate to "RECOVERY". Use the Power Button to confirm that option, and let it boot into the TWRP RECOVERY. Once you have done that, in TWRP, pick the Reboot option, and click the "System" button, so that the RECOVERY boots into the normal Android OS.
Congratulations, that was step 1 (and all its detailed sub-steps).
Now to STEP 2:
2: As the Moto Z has its entire storage and OS fully force-encrypted, we have to fix that. There are two ways, but as of now, i recommend the best one, as the other one is a bit hard to do unless you are a bit more tech-savvy.
-2.1: You will have to download the currently only actual ROM for the Moto Z from XDA user @janjan . You can find the download HERE. Download the corresponding US or EU version, depending on where you bought your device.
-2.2: I will have to mention here shortly, that the ROM you are about to install currently has one issue, which its severity depends on how much you currently need that "feature". The developer @janjan is working hard to fix, so you might want to wait in case you are disturbed by that "feature" not working. What is that feature you ask? Moto Mods. Some work, some don't, and the Incipio Battery Pack is one of those that do not work. If you can live with this issue until it is fixed, there is nothing stopping you from installing this ROM, but if you feel that you absolutely cannot live without it, then you might want to stop at this point and return when the issue has been fixed.
-2.3: So if you have decided to continue, then congratulations. To continue, you will have to enter the TWRP RECOVERY. Do NOT set up your Phone, as everything will be Wiped once more. So just enter the RECOVERY through the Bootloader (Fastboot). Shut down the Phone, hold the Volume Down and Power Button, wait for the Fastboot Menu to come up, navigate with the Volume Down Key to the RECOVERY option and confirm with the Power Button.
-2.4: Now connect your Phone to your PC with the USB-C Cable, and then go into the "Mount" menu. There it will let you open your Phone storage like on normal Android through MTP. Find the ROM .zip file you downloaded earlier, and put it somewhere in your Phones storage, like the Download folder, or create a new Folder you can easily recognize.
-2.5: If you have transferred the ROM .zip to your Phone, go back to the Main Menu, and pick the "Wipe" option (upper right). Now just Swipe the blue button to the right to do a full Factory Reset.
-2.6: Once it is done with the Factory Reset, go back to the Main Menu, and pick the "Install" (upper left, first option) option. Now navigate to where you uploaded your ROM .zip file, and then click that file once you have found it. Swipe to the right again to Flash the ROM.
-2.7: When it has finished flashing the ROM, Reboot the device, and you do that either by clicking "Reboot" (button to the lower right) right after the ROM has been flashed, or going back to the Main Menu and using the Reboot option.
-2.8: The Phone WILL take a good while to boot, so give it at least 10-15 minutes. If nothing happens by then, hold the Power Button to turn your Phone off and check the steps again and see if you did something wrong. If it did boot successfully, then take the time to setup your Phone, Language, Login Methods, etc.
And congratulations again, this was step 2. At this point you are done with all the time consuming things.
This is the last step, STEP 3:
3: I recommend that you install XPOSED BEFORE installing Viper4Android, as i found problems doing it the other way around. In case you thought about installing the XPOSED Framework, do that FIRST, NOT after having installed V4A.
-3.1: The only working version of Viper4Android i found is the ViperAtmos Universal Edition. You can download it directly HERE, or check the thread HERE (downloads are in the bottom. Remember to download the "ViPERAtmos 4.8 Sony Beats Universal Edition" .zip file).
-3.2: You will also have to download the SELinuxModeChanger app, with the direct link HERE, or the thread HERE.
-3.3: Now you push/transfer the downloaded files to your Moto Z, either by Cable or Wireless, the way you do it is up to you, but put it somewhere where you will find the files easily, like the Downloads folder.
-3.4: Now on your Moto Z download any file manager, go to the directory you pushed the files in, and install the SELinuxModeChanger.apk file. Open the app, give it full ROOT permissions, and then pick the "Permissive" option. Now reboot your device once, and it will automatically set SELinux to Permissive every time you boot your Moto Z (you can choose to let it notify you when it changes the mode).
-3.5: Reboot your Moto Z into the RECOVERY (steps found above). Here you go directly to the "Install" option, navigate to where you put your ViperAtmos .zip file, and install it by Swiping to the right. Do NOT pick the option to clear cache and dalvik/ART, i had problems with this the last time, and V4A wouldn't work (if you feel for it, then you can try clearing cache and dalvik/ART, but i found out that it works just fine not doing any of that).
-3.6: Reboot your Moto Z into the normal Android OS, and now you are done. Remember to check in the SELinuxModeChanger if the mode is set to Permissive, because if it is not, then Viper4Android (ViperAtmos) will crash your Phone, so make sure that is set.
Now you are done installing Viper4Android using the Universal Edition from ViperAtmos, well done!
If you have found any spelling mistakes in my guide and are absolutely annoyed by it/them, then tell me please!
Ok, have a good one everyone!
Really a GREAT guide...
yanniclord said:
oi guys!
so for now i might be alone on this, but i am certain that some few of you have wondered on how to get viper4android to work on the moto z without flaws. I am here to give you a small guide, because i figured out how to fairly easy add v4a.
There are 3 simple steps, but they can (in case you haven't done the first one yet) take some time.
If you have already unlocked your bootloader, disabled force_encrypt (either by manually editing the boot.img or flashing @janjan his rom), installed a recovery like twrp and rooted your device, then you can skip right ahead to step 3.
Also, before you go ahead, do a backup of all your important data, as it will certainly be lost when unlocking the bootloader (this does not count for inserted microsd cards, but just to be safe, remove the microsd or backup your data somewhere else, like your pc or a cloud service).
One more heads-up: you need a usb-c cable that you can connect to your pc, otherwise this guide will be useless for you. Also, all my commands listed in the upcomming guide are listed with " ", but ignore these when entering the commands in the command prompts.
step 1:
1: As for every android phone, you need an unlocked bootloader and twrp (and also root, etc).
-1.1: Download the motorola usb drivers here, and the adb fastboot driver/tool here.
-1.2: Install the motorola usb drivers first, then install the adb all-in-one tool after that (when installing the adb aio, choose yes for all options).
-1.3: On your moto z, enable developer options by going into the phone settings, then the last "about phone" option, and then scroll to the bottom where it says "build number". Tap that "bar" 7 times until it says that you unlocked the developer options menu.
-1.4: Go back into the main settings menu of your phone, and then right above the "about phone", should be an option called "{ } developer options". Go in there, and right in the beginning is an option called "oem unlocking". Enable that option (when it asks you for your pin/password/pattern, just enter it).
-1.5: Scroll just a little further down in the developer options menu, and you will see a section called "debugging", in which the first option is called "usb debugging". Enable that option as well.
-1.6: Now put your moto z into fastboot mode. You can do this either by connecting your moto z to the pc, then open a command prompt (look in windows for cmd), and type "adb reboot bootloader", or by turning your moto z completely off, and then turning it back on while holding both the volume down and power button (if your moto z turns off all the time, the second the phone vibrates, let go off the buttons).
-1.7: Now that your phone is in fastboot mode, you will have to connect it to your pc by a usb-c cable. If you have done that, open a command prompt in windows (again, by typing cmd in the windows start search), and type this: "fastboot oem get_unlock_data"
-1.8: You will end up getting a result that will look a little like this (the numbers do not work for you, don't try them for steps required later on):
$ fastboot oem get_unlock_data
(bootloader) 0a40040192024205#4c4d3556313230
(bootloader) 30373731363031303332323239#bd00
(bootloader) 8a672ba4746c2ce02328a2ac0c39f95
(bootloader) 1a3e5#1f53280002000000000000000
(bootloader) 0000000
-1.9: Copy the entire string you just got from the command prompt, and put it into any kind of text field or text editor. Remove the bootloader part, and also everything else, like [info] or the likes, and same goes for empty spaces. The only thing you should be left with looks like this: 0a40040192024205#4c4d355631323030373731363031303332323239#bd008a672ba4746c2ce02328a2ac0c39f951a3e5#1f532800020000000000000000000000
-1.10: Now you go to this website to get the unlock code for your phone (you will have to register at motorola to be able to get the unlock code. It is easier if you just use google+, it is much faster and you can skip the entire register process). There will be instructions there as well to guide you for how to enter the code, just in case you misunderstood my guide.
-1.11: Once you registered and entered the code, click the blue button below called "can my device be unlocked?". Once motorola confirms that your moto z can be unlocked, you click the "i agree" option, and then the "request unlock key" button.
-1.12: You will get a pop-up telling you about it voiding your warranty, click "ok" on that one as well.
-1.13: Now, motorola will tell you that they sent you the unlock code for your device to the e-mail you registered with, so go and check your e-mail account for that code.
-1.14: Copy the unlock code, go back to that command prompt (in case you closed it, open a new one), and enter this: "fastboot oem unlock unlock_code_here" <<<< where the unlock_code_here means that you will have to replace this with the unlock key from your e-mail.
-1.15: Now click enter, and your device will be unlocked. After this, your device should reboot automatically, but if not, pick the reboot option in the fastboot mode menu, and click the power button to confirm. From now on, every time you start your phone, you will be greeted with the unlocked warning screen, but that is ok, nothing stopping your phone from working or the likes.
-1.16: Let your moto z fully boot up, and when you have done that, shut it down again, and go back into fastboot mode using the above mentioned button combination.
-1.17: At this you will have to download the twrp recovery image. You can find this for the moto z here, or here.
-1.18: Rename the downloaded file to just twrp.img, then go back to your command prompt (or open a new one), and enter this: "fastboot flash recovery twrp.img"
-1.19: Now let the recovery be flashed, and then in the fastboot menu on your moto z, use the volume keys to navigate up and down, and navigate to "recovery". Use the power button to confirm that option, and let it boot into the twrp recovery. Once you have done that, in twrp, pick the reboot option, and click the "system" button, so that the recovery boots into the normal android os.
Congratulations, that was step 1 (and all its detailed sub-steps).
now to step 2:
2: As the moto z has its entire storage and os fully force-encrypted, so we have to fix that. There are two ways, but as of now, i recommend the best one, as the other one is a bit hard to do unless you are a bit more tech-savvy.
-2.1: You will have to download the currently only actual rom for the moto z from xda user @janjan . You can find the download here. Download the corresponding us or eu version, depending on where you bought your device.
-2.2: I will have to mention here shortly, that the rom you are about to install currently has one issue, which its severity depends on how much you currently need that "feature". The developer @janjan is working hard to fix, so you might want to wait in case you are disturbed by that "feature" not working. What is that feature you ask? Moto mods. Some work, some don't, and the incipio battery pack is one of those that do not work. If you can live with this issue until it is fixed, there is nothing stopping you from installing this rom, but if you feel that you absolutely cannot live without it, then you might want to stop at this point and return when the issue has been fixed.
-2.3: So if you have decided to continue, then congratulations. To continue, you will have to enter the twrp recovery. Do not set up your phone, as everything will be wiped once more. So just enter the recovery through the bootloader (fastboot). Shut down the phone, hold the volume down and power button, wait for the fastboot menu to come up, navigate with the volume down key to the recovery option and confirm with the power button.
-2.4: Now connect your phone to your pc with the usb-c cable, and then go into the "mount" menu. There it will let you open your phone storage like on normal android through mtp. Find the rom .zip file you downloaded earlier, and put it somewhere in your phones storage, like the download folder, or create a new folder you can easily recognize.
-2.5: If you have transferred the rom .zip to your phone, go back to the main menu, and pick the "wipe" option (upper right). Now just swipe the blue button to the right to do a full factory reset.
-2.6: Once it is done with the factory reset, go back to the main menu, and pick the "install" (upper left, first option) option. Now navigate to where you uploaded your rom .zip file, and then click that file once you have found it. Swipe to the right again to flash the rom.
-2.7: When it has finished flashing the rom, reboot the device, and you do that either by clicking "reboot" (button to the lower right) right after the rom has been flashed, or going back to the main menu and using the reboot option.
-2.8: The phone will take a good while to boot, so give it at least 10-15 minutes. If nothing happens by then, hold the power button to turn your phone off and check the steps again and see if you did something wrong. If it did boot successfully, then take the time to setup your phone, language, login methods, etc.
And congratulations again, this was step 2. At this point you are done with all the time consuming things.
this is the last step, step 3:
3: I recommend that you install xposed before installing viper4android, as i found problems doing it the other way around. In case you thought about installing the xposed framework, do that first, not after having installed v4a.
-3.1: The only working version of viper4android i found is the viperatmos universal edition. You can download it directly here, or check the thread here (downloads are in the bottom. Remember to download the "viperatmos 4.8 sony beats universal edition" .zip file).
-3.2: You will also have to download the selinuxmodechanger app, with the direct link here, or the thread here.
-3.3: Now you push/transfer the downloaded files to your moto z, either by cable or wireless, the way you do it is up to you, but put it somewhere where you will find the files easily, like the downloads folder.
-3.4: Now on your moto z download any file manager, go to the directory you pushed the files in, and install the selinuxmodechanger.apk file. Open the app, give it full root permissions, and then pick the "permissive" option. Now reboot your device once, and it will automatically set selinux to permissive every time you boot your moto z (you can choose to let it notify you when it changes the mode).
-3.5: Reboot your moto z into the recovery (steps found above). Here you go directly to the "install" option, navigate to where you put your viperatmos .zip file, and install it by swiping to the right. Do not pick the option to clear cache and dalvik/art, i had problems with this the last time, and v4a wouldn't work (if you feel for it, then you can try clearing cache and dalvik/art, but i found out that it works just fine not doing any of that).
-3.6: Reboot your moto z into the normal android os, and now you are done. Remember to check in the selinuxmodechanger if the mode is set to permissive, because if it is not, then viper4android (viperatmos) will crash your phone, so make sure that is set.
Now you are done installing viper4android using the universal edition from viperatmos, well done!
If you have found any spelling mistakes in my guide and are absolutely annoyed by it/them, then tell me please!
Ok, have a good one everyone!
Click to expand...
Click to collapse
thanks very good detailed guide
OK so wait...did I just read a guide on how to get root on the moto z? I've been up all day and am pulling an all nighter at work so I may be delirious, I just want to make sure...lol
Avengeme said:
OK so wait...did I just read a guide on how to get root on the moto z? I've been up all day and am pulling an all nighter at work so I may be delirious, I just want to make sure...lol
Click to expand...
Click to collapse
Yes, there are some better around now but... you are right!
Overview- Disclaimer -
- Tested on -
- Deep Cleaning -
- How to flash TWRP and enable Root with SuperSU -
- Download sources -
- Combos explained -
- Unlock bootloader and enable USB-debugging -
DISCLAIMERI AM NOT RESPONSIBLE IF YOU DAMAGE OR BRICK YOUR PHONE. THIS IS THE METHOD OF HOW I ROOTED MY S7 EDGE AND I WANTED TO SHARE THIS METHOD WITH YOU.
THE FOLLOWING GUIDE IS SUPPOSSED TO WORK FOR S7 PHONES WITH EXYNOS CHIP, ONLY!
IF NECESSARY: MAKE A BACKUP OF YOUR APPS/PICTURES/VIDEOS BEFORE YOU PROCEED.
Tested on[Device model] Galaxy s7 edge SM-G935F
[Codename] hero2lte
[Buildnumber] NRD90M.G935FXXS1DQHM (2017-08-30)
[Buildnumber] NRD90M.G935FXXU1DQJ1 (2017-11-15)
[Android] Android 7.0
[TWRP version] 3.1.1.0 (twrp-3.1.1-0-hero2lte.img.tar)
[SuperSu version] 2.82 (SR5-SuperSU-v2.82-SR5-20171001224502.zip)
[Not Required] In case you need a Deep Cleaning (WATCH OUT! MIGHT BE RISKY!)1. Download "Firmware" dedicated for your phone (unpack zip file!)
2. Connect phone to PC via USB cable
3. Enable "Auto Reboot", "Nand Erase" and "F. Reset Time"
4. Put BL/AP/CP/CSC firmware files to the right places without choosing "HOME_CSC..."
5. Press "Start"
Flashing TWRP and enable Root with SuperSU[PC]
A. Download No-Verity-Opt-Encrypt zip file (=NVOE)
>> Place it to your phone's internal/external driveB. Download SuperSu zip file
>> Place it to your phone's internal/external drive[Phone]
Developer Options that have to be enabled before flashing anything:
C. OEM unlocking
D. USB debugging
[Phone]
1. Start "Download Mode"
>> Connect phone to PC via USB connector cable[PC]
2. Run Odin3 as Administrator (by right-click on it)
>> Untick "Auto Reboot"
>> Let "F. Reset Time" be enabled3. Load proper TWRP file into "AP"
4. Press "Start"
5. Wait until "PASS!" is appearing and progress bar on phone seems finished.
[Phone]
6. Force phone reboot (screen turns to black) {see "Combos explained"}
7. Once screen turned black immediately enter "Recovery mode"
>> "Keep System Read only?" Screen should appear8. Swipe the arrow button at the bottom of the screen
9. Tap "Wipe" in main menu, tap "Format data". Type "Yes“ on your keyboard (first letter probably needs to be pressed twice or three times)
>> This will delete the data from all apps!10. Tap "Back", "Install" and "Select Storage"
>> Depending on which NVOE/SuperSU file you want to choose you got to tap "Select Storage" (It is set to "Internal Storage" by default). Let's say you wanna have these files from your extermal SDcard being flashed: Select >> [Micro SDcard] entry11. Find the NVOE file on your external SDcard, select it and swipe the arrow button to confirm flashing.
>> Flashing NVOE is required for the phone to boot correctly! 12. Go back to main menu by tapping that house symbol at the navigation bar.
13. Tab "Reboot", "Recovery" and "Do not install"
>> It should reboot back to "Recovery mode" automatically14. [optional] Check "Never show this screen during boot again" and swipe the arrow button
15. Swipe the arrow button
16. Tap "Install", find the SuperSU file and flash it by selecting and swiping the arrow button like you did with the NVOE file.
17. Check "Reboot after installation is complete"
>> It should reboot back to "Recovery mode" automatically18. Tap "Do not install"
Done! Phone should reboot to Android OS after ~2-5 Minutes. Enjoy! :highfive:
Note: USB-Debugging might be disabled again after this procedure.
Download sources (consider downloading the LATEST one!!!)Firmware: https://www.sammobile.com/firmwares/
TWRP: https://twrp.me/Devices/
>> Type your device name and press "Enter"
>> Choose Download location and download latest "img.tar" file
>> Make sure this file has the correct device name. hero2lte = s7 EDGE |||||| herolte = s7No-Verity-Opt-Encrypt: https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
SuperSu: https://download.chainfire.eu/supersu
Combos explainedEnter Download Mode: "Volume Down" + "Home" + "Power"
Force phone reboot: "Volume Down" + "Power"
Enter Recovery Mode: "Volume Up" + "Home" + "Power"
Developer Options: How to unlock bootloader and enable USB-debugging?1. Launch the Settings app from the app drawer or the notifications shade.
2. Swipe all the way down and tap on "About device" and "Software info".
3. Tap "Build number" till you see a prompt on the display stating "You are now a developer".
5. Now go back to the main Settings page, scroll down once more and tap to "Developer Options".
6. Enable "OEM unlocking" (=Allow the bootloader to be unlocked) and scroll down to enable "USB-Debugging", as well.
-Hope- was the one who helped me rooting my phone with this guide. Thank you for your effort! :good:
https://forum.xda-developers.com/member.php?u=7827499
Feel free to join the unofficial XDA-Developers Live Chat Discord Server:
https://forum.xda-developers.com/general/general/unofficial-xda-developers-unofficial-t3661056
✓ Friendly Chat ✓ Technical Support ✓ Discussing about android latest news ✓ Gathered most used tools in one place ✓ More to come - suggestions are welcomed
I applaud your detailed description of how to do things. I spend hours last month to root my phone until i realized that almost all guides were flawed... One comment. You can optimize the description for easier reading cause there is a lot of excess info but other than that Well Done! This topic should be pinned somewhere
PS: Works fine with Magisk as well btw
Hi, can i use this guide I'm on Nov Security Patch. Please advice because last time I was stuck at Samsung breathing Logo trying to root via CF Auto root method. Thanks in advance.:good:
nickomy said:
Hi, can i use this guide I'm on Nov Security Patch. Please advice because last time I was stuck at Samsung breathing Logo trying to root via CF Auto root method. Thanks in advance.:good:
Click to expand...
Click to collapse
As it happens, I am already on November Security Patch G935FXXU1DQJ1 (2017-11-15) and everything went fine with this guide^^ Please be aware that there is a newer build available for december!!!
ShaMana999 said:
I applaud your detailed description of how to do things. I spend hours last month to root my phone until i realized that almost all guides were flawed... One comment. You can optimize the description for easier reading cause there is a lot of excess info but other than that Well Done! This topic should be pinned somewhere
PS: Works fine with Magisk as well btw
Click to expand...
Click to collapse
Thank you
it worked like charm!
If you dont have full ROM backup from your device or official ROM, dont do anything in terms of modding but to install vcom drivers (in my case they wont work without Virtual Serial Port Drivers) for bootloader, and adb/fastboot drivers, make sure theyre working, install Miracle Box / SPFlashTool (or similar ?) to be able to backup/flash your ROM/partitions from/to your device.
Check if it works for you (ie backup your ROM and try to flash something (cache) back.
Now when people are scared enough I want to tell you that it is almost impossible to kill (brick) your MTK phone, it happens mostly when people flash something that is not suppoused to be flashed (something from another device), the worst case if you flash wrong preloader or erase preloader but even after this there is a chance for resurrection. it takes time and efforts though.
++++++++++++++++++++++++++++++++++++
This is TWRP 3.2.2.0 recovery for Chuwi hi9 Pro.
Partitions available for backup:
boot, recovery, system, vendor, data (not incl. data/media = internal sd), cache and "para" (if you have got "recovery loop" - flash "para")
.img flashable - boot, recovery
look for detailed instructions for coomon things in other treads, like
- how to install bootloader vcom drivers and adb / fastboot drivers
- How to work with adb / fastboot command from your computer cmd window.
- how to use Miracle Box / SPFlashToll
This is detailed instruction how to make SPFlash backup out of your phone though Miracle Box does it in one click (well, almost)
- how to unlock bootloader (fastboot mode)
- how to use toilet paper (manual mode)
- how to install twrp recovery
- how to root
Unlock, Install, Root in one post
++++++++++++++++++++++++++++++++++++++
So, main point of this thread is TWRP, youll need:
- roll of toilet paper
- spflashtool backup (just in case)
- backup of your data (if you care) - your data will be erased during the process.
- unlocked bootloader
- twrp image
If something went wrong (highly unlikely), but "if".
Worst case scenerio: your phone will not boot into system / recovery
Solution: reflash (fastboot or flash tool): boot / recovery / system
Worst case scenerio: flash factory ROM (SPFlashTool)
Steps to do when you have all knowledge and all files ready.
IN YOUR CURRENT SYSTEM
In settings->System->About tablet -> click several times "build number" untill you see message "now you are developer"
In settings->System->Developer options: Enable USB debugging and OEM Unlock, connect cable
REBOOT INTO FASTBOOT
Power off, Power on holding "vol+"
Youll see black screen with 3 strings of menu (very small font):
- recovery
- fastboot
- system
use "vol+" for navigation, use "vol-" to confirm your choice (fastboot)
OR from your pc cmd window (shift+right click on adb folder -> choose "open command window here") type: adb reboot bootloader
press Enter
UNLOCK BOOTLOADER
on your pc (if cmd window is not ooened yet: shift+right click on adb folder -> choose "open command window here") type: fastboot oem unlock
press Enter
watch your phone and pc screen for messages
if you have vision problems, make sure you have a magnifying glass.
INSTALL TWRP
download hi9pro_twrp.img to your /adb folder
from the same cmd window type:
fastboot flash recovery hi9pro_twrp.img
*
Reboot into twrp and flash Magisk
*
Basically this is it
There is no command from fastboot to reboot into recovery (correct me)
You can power of, power on holding "vol+", choose "recovery" from menu
command to reboot into system: fastboot reboot
+++++++++++++++
* NEW *
Infect_Ed has posted TWRP recovery that he has compiled from source. DOWNLOAD FROM HERE
We don't know how to make twrp recovery work with encrypted data partition.
Read next paragraph if you are OK to trade security (encripred userdata) for functionality.
++++++++++
==========
In case you want to have your userdata decrypted (and full functional twrp), use following steps:
*** Please, note all userdata AND internal SD will be wiped during the process***
If you care
Save Internal SD card content to your ext.SD or computer
Make a Titanium backup of user apps (check Enable external data backup in Titanium settings)
If Titanium fails to write to your ext.SD than change Titanium backup folder location to int.SD
and after backup is done copy Titanium backup folder to ext.SD or PC.
Disable any passwords/pins from Settings->Security & Locations
(I know they are stored in /data/.. and will be erased anyway but just in case)
- Reboot into TWRP
- ftom TWRP -> Wipe ->Format userdata -> Confirm with "yes"
do not reboot into system
- flash encryption_prevener_hi9pro.zip to prevent system automatically encrypt userdata (it is used to insert modified fstab.mt6797 into vendor/etc)
- reboot system
- restore your int.SD content and apps
============
Link to official ROM/Firnware
*** Read this if you have Recovery Loop - no matter how you boot (buttons, from twrp recovery or from adb/fastboot shell) your device you always end up in TWRP recovery ***
- download 2018-09-29--para.zip
- unzip it - there is a folder 2018-09-29--para with 3 files inside
- connect your phone in twrp recovery mode to your computer
(you may need to turm "enable mtp" option in TWRP->mount)
- copy that folder into your sd card, the path is : TWRP/Backups/Hi9Pro
- click "Restore" (on the next screen make sure ExtSD is chosen as backup path)
- check checkbox "para", run restore, reboot
explanation: para is a partition contains last issued kernel reboot flag(command), like "reboot to recovery, reboot to system, etc." I think there is one flag that tells to kernel something like "reboot to recovery, do something untill its done", since this "something" never done, device reboots into recovery over and over again. This happend to me when I tried "factory reset" command from android settings, so android have sent my device into recovery mode where that "factory reset" command had to be performed but never done because its now not stock recovery but twrp.
**** If you have following problems:
Unknown Baseband -> Unknown IMEI -> NO sim card -> NO cell network
Look here first
****
***** If you came here from there.*****
and you are following their instructions, please, note, step 7. Unlock bootloader : DO NOT DO command "fastboot flashing unlock", just skip it.
Also, try to avoid "fastboot boot recovery.img" command to reboot into recovery (just use physical buttons for reboot). I'm not sure but something caused "recovery loop" in one case at least.
****** back-to-encr.zip if you want to encrypt your decrypted userdata (original fstab.mt6797 will be flashed, no data loss, you will not be able to mount userdata in TWRP, first boot may take long time due to encryption process - 10-60 min- depends how much data do you have)
******* twrp_recovery_chuwi-hi9pro_infectEd-XL is same Infect_Ed recovery adopted for our screen.
Hello. I made a mistake last week. I flashed accidently twrp with a scatter File from the HI9 Air through the spflashtool on the Hi9 Pro. Now it doesnt turn on etc. Is it hardbricked or can i still get it back to life?
No, its not complitely bricked if flash tool still recognizes your phone in bootloader mode. Most likely youve made same mistake I did. Depends of how you flashed that recovery - recovery only or full sisyem WITH new recovery. most likely you flashed only recovery partition. than, first, try to reflash backed recovery & next to recovery ("para") partition. in "download only mode" therell be an error "pmt has changed" than try "format & download" and "firmvare upgrade" - use scatter file contained only those two partitions. if you didnt make a backup ill put here that "para" partition and you can use hi9pro twrp img. in case this wont work, you may want to reflash the whole rom. We need to find factory rom image (from Chuwi or someone who did a back up prior he entered his credintals - thats another mistake Ive made Ive dumped a rom with all my logins information). if I have time I'll try "factory reset" to make a backup from "clean" system.
again, its almost impossible to brick mtk completely. even if flash tool doesnt recognize you phone (dead battery) there is a jump-pins method.
upd. Just looked @ Air scatter and found that Air recovery partition size is same as Pro (~16mb). now I dont know haw was that possible to overwrite next to recovery partition(s) and I think I used same Air img as you did and I've got size warning message when I flash it. anyway here is archive with scatter for recovery and para. just add twrp hi9 pro recovery (rename recovery.img to recovery.bin) and try to flash.
I didnt made a Backup (stupid me) i flashed the recovery file with a scatter file. When i plug the device in the pc the USB sound comes and its recognized as MEDIATEK USB PORT (COM8), but its removed automatic (USB Sound for disconnecting) The Screen stays black. So i have to wait for a Rom and a scatter File then?
---------- Post added at 19:50 ---------- Previous post was at 19:39 ----------
I tried your idea. I got an error Message: "Status Preloader Invalid" The Preloader File Format is invalid.
you know how to use flash tool , first you have to press "download" THAN connect usb cable.
but this is a good sign (pc recognize something), you may want to google for something like "unbrick mtk 6797 sp flash tool" for more info
this is archive w. 4 1st partitions (incl preloader)
Ive gotta go. Dont smash your tablet its 100% repairable, well 99.999%
thats how it looks
https://photos.app.goo.gl/9EK8vTwcTS3fDf1a7
---------- Post added at 20:21 ---------- Previous post was at 19:58 ----------
Still get an error Message for the PRELOADER. I read some Tutorials and dont find a Problem in my setup or my doing. Sucks :-/ But Thank you very much for your help
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Good Morning.
Bootloader is unlocked, no matter which key combinations ill try the screen stays black. When i have the usb cable at the PC (no matter which Port or cable) it the plugin - plugout sound plays every few seconds/minutes (not the same time in between). It is recognized as "MediaTek USB Port (COM4)" (different PC i tried). When ill try to install the vcom drivers i get the message that the best drivers are already installed and that are the mediatek usb port driver.
Image of the device manager: https://ibb.co/erkW6e
zelipukin said:
is it "MEDIATEK USB PORT (COM8)" appears for a second in the devices tree or "mediatek preloader usb vcom (android) (com8)"
if second, then everything is OK with the connection.
if its exactly MEDIATEK USB PORT (COM8) then there is something wrong
try to connect cable with diff buttons combination, i.e. "vol+" + connect cable .
try different "download agent" (DA_PL.bin ?)
Though I also used AllInOne_DA and flash tool V.5.1728
also, you might find Miracle Box Tool is easier to use
try "read" option first to backup your current rom
View attachment 4598709
I shoul ask this first:
- have you ulocked bootloader ?
- when your press "power" and "vol+" after some wait is anything appears on the screen
(boot menu: fastboot, recovery, regular boot) ?
- when your press "power" and "vol-" after some wait is anything appears on the screen
(chinese written) ?
Click to expand...
Click to collapse
---------- Post added at 07:34 ---------- Previous post was at 07:07 ----------
zelipukin i made a short Video about the behavior. The Device seems to activate when i push vol+ or power, but it looses connection when i stop holding the button or sometimes even when i hold the button.
https://drive.google.com/file/d/1m3YLrH5ZaVLttcSfDxx3RvL0DaXPcxzk/view?usp=sharing
...thinking
Just tried...seems like backups I made(and posted here) from Miracle Box is incompatible with SP Flash.
SP Flash doesn't like this and doesn't like that when tries to restore those backups but Miracle Box restores individual partitions or whole ROM w/o problem.
SP Flash is so inconvenient if you try to make a backup ... its also inconvenient when you try to restore.
Where did I get that Miracle Box for free ?
Let me figure out something...
....
This is something beyond my understanding but let me to describe what I did
- in SP Flash I choose scatter file and recovery.bin (like I sent to you)
- download only - no go
- download+format - no go
- firmware update - warning message about wrong partition size or something like this - Ignored - Flashed
- Bricked again (like yours - black screen - that's it)
- OK, I have several backups. Tried all of them - none of them works... except one
- Flashed that backup with SP Flash - no questions, no warnings, no errors - device came alive
- Flashed only recovery.bin - everything went fine
- Tried to find difference btw different backups - but couldn't find any
- So I tried to flash those files (to try 3.zip) several times and everything went OK, so this is 100% working backup.
Try it and see what happens, then we can go somewhere else. I still suspicious about those MTK Usb Com(8) instead of preloader usb. Also if you used "Firmware upgrade" option once, I beleive you'll need full ROM flash. Keep looking for it @ Needrom.com.
Strange things happen. Couple years ago I lost MTP connection with my MiMax. I tried everything possible but no luck - have to use UMS Enabler so I can read/write ExtSD at least, but MTP works with Chuwi.
I spent numerous hours trying to connect Chuwi in preloader mode until found that solution about Virtual Serial Port drivers.
Thanks for your help so far. Seems like my Device is half dead after 2 Hours of use
I'll tried to change the Drivers for the mediatek, it shows the device now with the preloader, but i think it doesnt work right. when i change the usb port it comes back as MediaTek USB Port (COM4). I made you a 15 Second Clip of the behavior.
https://drive.google.com/file/d/1m7wyIlIYJLN7ikmgUTzHBJtBdbZQrYaa/view?usp=sharing
Really weird. :-/
---------- Post added at 14:55 ---------- Previous post was at 14:40 ----------
and no chuwi hi9 pro rom at needrom yet. :-/
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
i think i used the upgrade one, after download only didnt work.
Ill tried the same method with changing drivers.
I will sit this one out, till you have uploaded the rom
Thanks for helping me out!
zelipukin said:
Sorry, haven't seen there is second page of this thread.
Saw a video where one guy showed how he changed drivers to right ones.
Main idea is in that short period of time when wrong drivers appear click right mouse button and choose "uninstall drivers"
after this in his video in next attempt system found usb vcomm by itself. worth to try
or other videos where guys catch a moment when this port appears in device tree but choose "update drivers"-> "browse my computer..."-> "let me pick from a list of device drivers" -> remove flag from "show only compatible.."->
I cleaned system, removed apps,accounts, etc. and made a backup of a "clean" ROM (well, almost). will put somewhere when/if I get good wifi somewhere (its 3GB.. w/o data partition) I'm on slow & limited mobile network.
but I don't think you need anything but recovery & para if you never used "format" & "firmware upgrade"
Click to expand...
Click to collapse
Just a few questions after using Hi9 Pro for about a week:
1) Where is the microphone ? Is it the small hole under the volume button ? (Strange position)
2) On the back side the two metallic stripes separating the plastic of the metal body are they something like antennas ? (LTE or WiFi or both ? )
3) What is the version of Bluetooth ? (4.0 or 4.1 or 4.2 ? )
4) Is it possible to use some kind of fast charging with a suitable charger or software app (firmware update) ?
MediaTek has a technology called "Pump Express" or something like that...
5) Do you have sudden, unexpected pop-ups of full screen advertisements while you are working with your tablet ?
How do we get rid of them ?
6) How do I find the LTE band the tablet is actually using while it's in use ?
I don't mean the table of supported bands, I mean the active band while using it.
Thanks!
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
2) not sure, but most likely
3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
4) too many different opinions, cant find the truth
5) none so far
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
zelipukin said:
1) looks like and its logical bc its close to mouth than if they put it in the bottom.
Click to expand...
Click to collapse
Yes, it is a very small hole at the bottom right as you hold it, with a size of the edge of a needle!
zelipukin said:
1)3) according to this https://www.manilashaker.com/mediatek-helio-x10-vs-x20-vs-x30-chip-comparison-difference-specs/ its 4.2
Click to expand...
Click to collapse
Thank you.
zelipukin said:
5) none so far
Click to expand...
Click to collapse
But how did you do that ?
Did you add an Ad Block after rooting the tablet ?
The kind of ads I get, is more of suggested apps to install from Google Play.
It is literally bombarding me with an exhaustive rate.
I went to settings to "advertisements" of Google and it says that I can't turn it off.
Could it be some app that I installed that is spamming me this way ?
Can you suggest something to stop it ?
zelipukin said:
6) you can try to find some info from mtk engineering mode *#*#3646633#*#* from you dialer
but its not intuitive and complicated
Click to expand...
Click to collapse
I installed LTE Discovery and although I'm not rooted it seems that it works OK and it's showing me the bands.
The signal strength is lower than a mobile phone at the same position, same time, same provider.
Do you have an equal signal strength like your mobile phone ?
One more question:
7) Is it feasible for a developer to build a custom ROM for this device if he wants to or there are certain restrictions forbidding custom firmware ?
Is there any chance for a custom ROM in the future, because I don't think Chuwi will upgrade to 8.1 or better Android.
Thank you!
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed. I didn't do any system modifications except installing Magisk and modules - ExCard Access Enabler, init.d injector, Magisk SELinux Manager, ViperX (slightly better sound from speaker)
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
zelipukin said:
Regarding ads - I didn't do anything, I looked @ settings->google->ads and I can turn it on and then off w/o problem
Also I culdnt find any junk software so far, the phone came from GearBest factory sealed.
Click to expand...
Click to collapse
Me too, I got a sealed and clean tablet from GearBest but If you look closer to that setting, it says that you can turn on or off the specialized ads for you, but you can't close ads completely.
For example, during web browsing do you see ads inside various sites ?
Or when opening apps on your tablet ?
I think we need an ad-blocker for this.
zelipukin said:
I didn't try the device as a phone, though it fit in a pocket of one of my jeans. I'd like to try but my current phone (miMax) has a micro sim.
Click to expand...
Click to collapse
I meant for mobile 4G data, not as a phone.
In my country we have three bands for LTE:
B3, B7, B20.
When the tablet rotates between 3 and 7, I have poor to zero signal.
But I saw with LTE Discovery that when it switched to 20 then the signal is very good.
So, with the help of MTK Engineering I disabled 3 and 7 bands and everything seems OK now.
I hope B20 to be used everywhere near to me.
zelipukin said:
7) Depends how popular is this device and who (developers) got it. Also, depends if this chipset is used in many other similar models (popular, prefferable) than you don't need to be a real "developer" to port ROM from a similar device and if you find that divice X is updated to 8.1 there is a chance someone will make a port (or you can try to do it yourself). I'm not a big fan of immediate upgrading to a newest version, for me they usually bring more limitations (you cannot let apps to modify files on your own sdcard f.e.) than benefits. I still use >2 y.o. andr. 6.0 custom rom on my MiMax.
Click to expand...
Click to collapse
I'm not familiar with Android internals so much, I am only using a Note II with TWRP and a custom 7.1.2 ROM and I'm missing some simple customizations not available with out Oreo 8.0 stock ROM.
I haven't even tried yet your first post regarding rooting and all the others because I'm not so sure where to find these tools and how to use them.
It could help a lot when you find some time to add more descriptions and links in your first post, if possible like Hi9 Air thread.
Thank you!
I dont know how and why, but I dont have any agressive advertisements. Checked Opera I'm using for webbrowsing - even "block popups" option wasn't checked. Had to download app yesterday (AutoNotification) from gp store and when I started it in a "free mode" there was a message like "to use this app in a free mode you have to agree to see ads", clicked "ok" , then message "downloading..." appeared...and nothing, no ads. I connect my tablet to the internet through my phone but dont think that matter.
Just a few more short questions:
8) Is there any other way to wake up the device instead of pressing the red button ?
For example double tap or maybe using the volume buttons or any other way.
Because I'm afraid of pressing the same button again and again.
9) Does this device have a WiFi 2x2 MIMO ?
I haven't found any particular info on this.
10) What is the kernel of the ROM ?
Is there any GUI compatible like Kernel Aiutor to make changes or take a look at info for the device ?
Thank you!
Everything useful for the Samsung Galaxy J4 Core you find now here.
Infos, Tutorials, Tips, Tricks, Hacks...
Enjoy & Join ?!
In this first post I start off with a STEP BY STEP ROOT GUIDE. It's very detailed & hopefully n00b friendly!
Here it is:
In your phone's about section press build number several times, then developer options are activated,
you can find them in the system section of settings when you exit about section.
enable developer options, it is recommended to disable system auto update there, then enable oem unlocking.
(if you can't find this entry, enter a sim, try again. if you still can't find this entry, set the system date 21-30 days back or forth, then reboot. if the entry is still not there, search here on xda for solutions to this known problem or google it.)
go to your pc, download your exact firmware (the one you have installed on your device- look at build date & region in about section of device).
download 7zip zstandard! -with lz4 extracting support.
extract zip of your firmware. there you have 4 tar files. extract the AP tar file, inside are many files. extract smth like boot.img.lz4 or boot.lz4, then you have boot.img. this is the file you need.
in 7zip mark it & press add to archive, select tar in the screen that pops up. enter the path where you want to create the archive.
now you have a new boot.img.tar or boot.tar file,
that you need for the rooting process.
copy this file to the root of your internal storage of your android phone (/sdcard, /storage/emulated/0, or any folder that suits you best).
download & install latest magisk manager on your android.
open magisk manager, in the start screen you find some options. one of them is: preserve force encryption. uncheck them all.
then choose: install magisk, then: patch file. you will be directed to a file manager, there select your created boot.tar file.
now magisk creates a patched boot.tar file for you & renames it as such.
you will find it in the same directory as your file, or in /sdcard/download.
copy it to your pc. in your pc rename it in boot_.tar!
download odin latest! version.
download latest! samsung usb drivers / latest samsung usb drivers for your specific phone model, install just samsung usb drivers & reboot your pc.
enable usb debugging in developer options of your phone.
turn off your phone.
connect your phone with usb cable to pc.
reboot your phone to download mode: when starting vol up + vol down + power button at the same time.
you come to a light blue warning screen. press power up once again, you entered download mode!
in your pc run odin as administrator.
it should recognize your device. you should see in the window on the left side in odin: added!
on the right side in odin are several buttons. one of them is BL. press that & go to the path of your boot_.tar. select your boot_.tar.
odin checks & in a sec you should see a checkmark next to BL.
now set some options in odin: - check flash reset time! - uncheck auto reboot! let all the other options untouched.
now you will flash your magisk patched boot_.tar to your android device: press start in odin.
you will see the ongoing progress in the upper row & in the log window.
you should see reset in blue color & when you see pass in green color, the flashing process was successful! almost done!
now on your phone: you're still in download mode, see the completed progress bar.
press vol down + power at the same time for 7 sec.
your phone will reboot. on the logo splash screen's upper left corner you will see a yellow entry: set warranty bit: kernel.
now the phone will reboot, reset. now your phone will show you a grey screen with a reset button, if you can't click it, no panic, just turn your screen shortly off & on again & then you can click it. phone will reboot again 2 times. don't panic! let it do its thing.
note that your phone will be reset through this process!
now you boot in your phone & the start menu appears.
you can go through it as usual. you should turn secure boot with lock off, choose just the normal phone lock.
at first turn developer options on & see if oem unlocking is there & enabled. (it usually is.) if not, turn it on again!
if it's not there after root, look here in XDA for solutions or google it. (but this is very rare on this phone, that it's not there after root)
leave oem unlocking & developer options always on! (unless you want to unroot)
turn system auto update off in dev options!
you can reinstall magisk manager & check if magisk is installed.
congrats, you're rooted!
now you can do everything that's neccessary & useful after root!
Guide follows soon!
[important: better safe than sorry: in your phone, right after rooting, enable developer options again & look if oem unlock is ticked on. let it always be ticked on! also leave developer options on! if not so, then do it immediately. otherwise it could be overwritten by security in your phone & you could lose root, your phone could be reset, or in the worst case your phone will be blocked to boot. never turn off oem unlocking!]
I will add some files soon here, to make it easier for you.
but if you follow this guide step by step, you should succeed, normally.
I've tested this procedure several times on my own with this phone, with different firmwares.
I can confirm that this guide is functioning well!
if you need further help just post me!
[please think about the steps you made prior to the rooting process also after root. don't forget your phone has become reset & some settings eg oem unlocking & others need to be re-applied !]
please use your mind! ?
Happy Rooting! ?
credits: to everyone I learned from!
Rooting, Flashing & everything you do on your device, you do on your own risk!
You take responsibility for your own actions!
Please consider before you copy my guides, to give me a thanks & if you wanna use my guides elsewhere, give me credits there, respectively!
This Guide/My Thread will be further improved in form, speech & content.
So much more to come in the future!
Please feel free to post me your thoughts, recommendations & criticism!
You're heartly invited to participate in my thread! ?
I have the root on my j410G following your guide thanks ...:good:
@JhonJC
you're welcome!
fine that you succeeded!
I used this method to root the j7 prime with new binary.
But i flashed boot patched as AP in odin. Works fine.
JohnEdwardMS said:
I used this method to root the j7 prime with new binary.
But i flashed boot patched as AP in odin. Works fine.
Click to expand...
Click to collapse
great to read that! odin normally flashes the whole firmware -including the boot.img- through ap, so pushed your boot.img automatically to the right partition.
but I still recommend flashing through BL. think I've read about it in the magisk documentations, but I will check that again, investigate further. thank you for info.
The method works but if you turn off the phone and turn it on you are greeted by a "this phone has been flashed with unauthorized software & is locked" screen.
zeratos said:
The method works but if you turn off the phone and turn it on you are greeted by a "this phone has been flashed with unauthorized software & is locked" screen.
Click to expand...
Click to collapse
@zeratos I had this too, in the beginning, when I experimented with rooting this phone. have you left developer options + oem unlocking kept on? this is essential for this phone, I've written this before in the above guide. another thing might be, if you boot into the stock recovery, then it detects, that your phone has been modified, refuses to boot + brings you to the screen that you mentioned. don't boot into stock recovery after rooting this phone, don't try to reset your phone through stock recovery or android settings! instead, get twrp or orange fox + flash it through odin. do everything then with your custom recovery, or flash everything through magisk manager!
it is also important to tick off all 3 options in magisk manager start screen and disable all unnecessary security features in your android, such as secure startup.
unfortunately, with the newer (samsung) phones, rooting is not so easy peasy anymore like it was back in the days. they gave us some really annoying hurdles.
I hope I could help.
so thanks for mentioning this, so others with the same problem can find it!
...................................... ~............................................
*can you please speak in your own person? 'you' suggests, that everyone, following my root guide will experience the same as you did. that's not true + I'm bit sensitive about truth + facts being falsified. no offence, thank you.*
the links to the great + genius orange fox + twrp recoveries for samsung galaxy j4 core:
1.) https://forum.xda-developers.com/ga...recovery-orangefox-samsung-galaxy-j4-t4059533
2.) https://forum.xda-developers.com/ga...ecovery-unofficial-twrp-3-1-1-galaxy-t4046189
@zeratos, could you get around your problem?
as I don't know what exactly went on on your phone,
I don't know if I could help you.
I just can try to tell you what can help you.
it's always good to go to magisk settings, magisk section + enable: hide magisk from various forms of detection.
next: it doesn't hurt to disable google services + other google apps until your root is stable.
the same for builtin samsung apps.
that helps preventing to trigger knox.
best is to say bye to google services/google apps at all + go with microg. then you can install custom playstore for microg + make purchases + all. not so easy btw. but if you figured it out, everything works very well.
if you already solved your problem, please tell us how you did it, could help others.
I just can tell, if you don't mind to say bye bye to all that proprietary stuff on your phone, root + everything else works almost perfect on that phone.
plus you have the free memory for all the good tools!
if you want to leave google services & co installed after root, at least flash the magisk module 'universal gms doze' , disable some permissions, run greenify + hibernate some apps strictly.
you get a much better effect with also xposed, (the original magisk xposed). but that's again not so easy at first. but you would already need it for microg, for the licence patch, (assuming you don't do the licence patch from the command line or use smali patcher).
Meu j4 core não aparece a opção do oem o que fazer pfv me ajuda
K.Vitorioso said:
Meu j4 core não aparece a opção do oem o que fazer pfv me ajuda
Click to expand...
Click to collapse
you find it above in my guide, otherwise there are many xda threads/posts to this topic, or google a bit around. good luck!
vous le trouverez ci-dessus dans mon guide, sinon il y a beaucoup de fils xda/posts sur ce sujet, ou bien cherchez un peu sur google. bonne chance !
working great guide!!!!!! thank you
Hello,
Can anyone help me ? I always get error "E1001: failed to update system image" and "updater process ended with error 7" every time I try to flash a custom ROM. Removed assert values fixed error 7 but the first one still exists.
If anyone have working custom ROM for j4 core please give me a link.
Photo of the error
thimprfct said:
In this first post I start off with a STEP BY STEP ROOT GUIDE. It's very detailed & hopefully n00b friendly!
Here it is:
In your phone's about section press build number several times, then developer options are activated,
you can find them in the system section of settings when you exit about section.
enable developer options, it is recommended to disable system auto update there, then enable oem unlocking.
(if you can't find this entry, enter a sim, try again. if you still can't find this entry, set the system date 21-30 days back or forth, then reboot. if the entry is still not there, search here on xda for solutions to this known problem or google it.)
go to your pc, download your exact firmware (the one you have installed on your device- look at build date & region in about section of device).
download 7zip zstandard! -with lz4 extracting support.
extract zip of your firmware. there you have 4 tar files. extract the AP tar file, inside are many files. extract smth like boot.img.lz4 or boot.lz4, then you have boot.img. this is the file you need.
in 7zip mark it & press add to archive, select tar in the screen that pops up. enter the path where you want to create the archive.
now you have a new boot.img.tar or boot.tar file,
that you need for the rooting process.
copy this file to the root of your internal storage of your android phone (/sdcard, /storage/emulated/0, or any folder that suits you best).
download & install latest magisk manager on your android.
open magisk manager, in the start screen you find some options. one of them is: preserve force encryption. uncheck them all.
then choose: install magisk, then: patch file. you will be directed to a file manager, there select your created boot.tar file.
now magisk creates a patched boot.tar file for you & renames it as such.
you will find it in the same directory as your file, or in /sdcard/download.
copy it to your pc. in your pc rename it in boot_.tar!
download odin latest! version.
download latest! samsung usb drivers / latest samsung usb drivers for your specific phone model, install just samsung usb drivers & reboot your pc.
enable usb debugging in developer options of your phone.
turn off your phone.
connect your phone with usb cable to pc.
reboot your phone to download mode: when starting vol up + vol down + power button at the same time.
you come to a light blue warning screen. press power up once again, you entered download mode!
in your pc run odin as administrator.
it should recognize your device. you should see in the window on the left side in odin: added!
on the right side in odin are several buttons. one of them is BL. press that & go to the path of your boot_.tar. select your boot_.tar.
odin checks & in a sec you should see a checkmark next to BL.
now set some options in odin: - check flash reset time! - uncheck auto reboot! let all the other options untouched.
now you will flash your magisk patched boot_.tar to your android device: press start in odin.
you will see the ongoing progress in the upper row & in the log window.
you should see reset in blue color & when you see pass in green color, the flashing process was successful! almost done!
now on your phone: you're still in download mode, see the completed progress bar.
press vol down + power at the same time for 7 sec.
your phone will reboot. on the logo splash screen's upper left corner you will see a yellow entry: set warranty bit: kernel.
now the phone will reboot, reset. now your phone will show you a grey screen with a reset button, if you can't click it, no panic, just turn your screen shortly off & on again & then you can click it. phone will reboot again 2 times. don't panic! let it do its thing.
note that your phone will be reset through this process!
now you boot in your phone & the start menu appears.
you can go through it as usual. you should turn secure boot with lock off, choose just the normal phone lock.
at first turn developer options on & see if oem unlocking is there & enabled. (it usually is.) if not, turn it on again!
if it's not there after root, look here in XDA for solutions or google it. (but this is very rare on this phone, that it's not there after root)
leave oem unlocking & developer options always on! (unless you want to unroot)
turn system auto update off in dev options!
you can reinstall magisk manager & check if magisk is installed.
congrats, you're rooted!
now you can do everything that's neccessary & useful after root!
Guide follows soon!
[important: better safe than sorry: in your phone, right after rooting, enable developer options again & look if oem unlock is ticked on. let it always be ticked on! also leave developer options on! if not so, then do it immediately. otherwise it could be overwritten by security in your phone & you could lose root, your phone could be reset, or in the worst case your phone will be blocked to boot. never turn off oem unlocking!]
I will add some files soon here, to make it easier for you.
but if you follow this guide step by step, you should succeed, normally.
I've tested this procedure several times on my own with this phone, with different firmwares.
I can confirm that this guide is functioning well!
if you need further help just post me!
[please think about the steps you made prior to the rooting process also after root. don't forget your phone has become reset & some settings eg oem unlocking & others need to be re-applied !]
please use your mind! ?
Happy Rooting! ?
credits: to everyone I learned from!
Rooting, Flashing & everything you do on your device, you do on your own risk!
You take responsibility for your own actions!
Please consider before you copy my guides, to give me a thanks & if you wanna use my guides elsewhere, give me credits there, respectively!
This Guide/My Thread will be further improved in form, speech & content.
So much more to come in the future!
Please feel free to post me your thoughts, recommendations & criticism!
You're heartly invited to participate in my thread! ?
Click to expand...
Click to collapse
bro did you know how to enable volte calls ?
i am from india
ZorEl212 said:
Hello,
Can anyone help me ? I always get error "E1001: failed to update system image" and "updater process ended with error 7" every time I try to flash a custom ROM. Removed assert values fixed error 7 but the first one still exists.
If anyone have working custom ROM for j4 core please give me a link.
Photo of the error
Click to expand...
Click to collapse
this should be one that works: https://forum.xda-developers.com/t/rom-oneui-j4-core-litee-j4-port-1-0.4116115/#post-83005025
Hello world!
Last year, I attempted to install a custom ROM into my device (J410F). I have no idea what is the name of the ROM but I know is compatible (from the updater script). But, anytime I tried to install it, Error 1 always appear. What do I have to do? Install Orangefox, chmod it, or just give up?
Edit 1: It's HavocOS. Some of my LineageOS in my SD Card output Error 7, and some output Error 1.
thank you---- thank you----- thank you ------ i could give you a big kissss.. lol.
ive been wanting to root my fone for years now with this guide ive done it 1st time without any problems, now i know what its like to be in controll. your a genius and i wish there were more like you in the world.
thimprfct said:
this should be one that works: https://forum.xda-developers.com/t/rom-oneui-j4-core-litee-j4-port-1-0.4116115/#post-83005025
Click to expand...
Click to collapse
This works. But if you don't care about the laggy experience that it provides (OneUI on 1GB RAM heh) and the broken camera app, then it's good for you.