First of all, sorry for publishing an uncomplete guide, im traslating my own full spanish guide and at the same time making it more complete and better, and i decided to do it this way, publishing progressively
/////////////////////////////////////////
SECTION 1: Android argot summary
I put this link here so any new user in the Android rooting/flashing world can learn the classic words used
http://www.talkandroid.com/guides/beginner/android-rom-and-rooting-dictionary-for-beginners/
Note: in bootloader it says that the phone comes locked, which in our case usually is not the case, but anyway you can know if your phone is locked just by trying to get into the fastboot mode, if you can't get into it, its locked.
An Android phone's disk is virtually splitted in several partitions, like a computer, but not exactly the same because even when your phone has a lot of partitions, you will only see one if you didn't rooted your phone, or two if you did, and the partition where you have your photos and the rest of your personal downloaded things is named sdcard (yes, is a legacy of Android, even when we don't have sdcard), or even in some ROMs is called userdata or something like that; another partition is system, where the ROM itself is, is like the installation of Windows; another is data, where the config files of the apps are stored when you start using them; another is cache, where the cache of the apps are (you can think of it like the apps are compressed always, and to run faster they descompress themselves in that partition), and there are two of those partitions: dalvik cache and cache; also bootloader, which is like the BIOS of the computer, is the most basic program that makes possible the phone to boot, and also it is not possible to edit it, it is not writable, it is this way so that you wont never be able to hardbrick your phone (which means that you can literally drop your beautiful phone into the trash, no way of fixing it), like it was in older phones, and also in this partition you also have the fastboot mode, which i'll explain later; and the last one im explaining (there are more but you probably wont never know about them) is recovery, where there is installed the recovery, and what is recovery? is a tool which is by itself an entire operating system, but made specifically for "developing" purposes, mainly for flashing ROMs and making backups of the entire partitions. We have two recoverys for Mi4C, the Mi Recovery, which comes by default with your phone, and is very limited, mainly you can only flash Xiaomi's official ROMs, and the TWRP recovery, which is the absolutely most popular recovery, and strongly suggested to use, no disadvantages at all. Also know that, like in Windows you can't format the very own Windows partition and you must use and external tool, which would be the Windows installation CD program or something like that, here we have the recovery, you can't flash or wipe using Android, you must be in the recovery mode.
So as I said, the bootloader is readable only by security, and it includes the fastboot tool, so you must know to lost the fear of this world, that YOU WON'T BE ABLE TO HARDBRICK YOUR PHONE, you will always have fastboot to reflash a complete Android ROM (which requires a computer and a fastboot ROM, which is different than a flashable ROM. You will use a fastboot ROM in the first flashing tutorial, more bellow)
What is Fastboot? Basically is a tool which acts like a server in the phone, and as a client in the computer, and is made mainly to make basic things to the phone, like flashing partition images (included in the fastboot ROMs, extension of each one is .img) or read the locking status of the bootloader.
What is a locked bootloader? In our phone, is a bootloader that only allows you to flash official xiaomi roms, but as xiaomi don't offer a global version of miui for our phone, the only official rom is the chinese one, which appart than having only english and chinese languages, is very bloated of chinese apps, so is very recommended to unlock the bootloader and flash any other rom of your desire.
How to access fastboot? First, shut down the phone; second, press at the same time the Power and the Vol - buttons for a few seconds, there should appear in the screen a Fastboot logo. Note that the phone may automatically shutdown if no connection is made with a fastboot client in a computer in about 10 seconds after entering fastboot mode
How to access recovery? First, shutdown the phone, then press at the same time power and vol+ for a few seconds
What is ADB? Is a tool that works the same way as fastboot (phone and computer connected), but instead of being in bootloader, it is inside of android, and instead of doing essential work for the phone, it does more practical things like transfer of files, but you will probably not use ADB at any time. Also, for transfering files you wont use ADB, which like Fastboot is a command line tool only, but you will use MTP, which is the media transfer protocol, the graphical way of transfering files, in your computer it will appear like a classical external drive, but in Windows the icon will be like an iPod.
Note before starting the flashing tutorial: go to Settings > (bottom) About phone and look at the MIUI version, MIUI version numeration is supposed to follow a date (the date of release) except the first number which could not be the year, it could be 5, 6 or 7, so a correct numeration would be for example 7.2.1.0 (there is always a 4º number which is always 0 if do remember well). The thing is that when you buy the phone to a reseller, is very usual that they flash their custom MIUI rom which comes with international language, its fine, but it also comes with spyware and adware everywhere. Those roms usually comes with a version numeration of strange repeated numbers, like 77. 87. 55. 99., remember that the first number always must be 5, 6 or 7. In case that you have preinstalled this rom, i suggest you strongly to follow the guide fully, including the clean flashing with fastboot rom
Note 2: you need to have the bootloader unlocked in order to continue, please read the unlock tutorial below
Note 3: this guide supposes you have Windows. If you have Linux or Mac, or you have any problem, please ask here
Note 4: for this guide we are going to use a Drive folder shared with a spanish mi4c community, so file names may contain spanish words but shouldn't be a problem. Sorry for the inconvenience, but it's for ease purposes. Drive link: https://drive.google.com/folderview?id=0B3N1d6szT1RYWkNET0pEbWhud3c#list
SECTION 2: Flashing guide (part 1/2: cleaning)
We are going to flash the 7.1.4.0 fastboot ROM in order to update as much as we can all the firmware (drivers of usb, modem, camera...), clean all from the weird ROM of the reseller and all of that without locking the bootloader.
Please, charge your phone first to at least 50%. Also, this process will erase all your personal data in the phone, backup all you need before.
1. Download the Fastboot 7.1.4.0 ROM (for example, here https://drive.google.com/folderview...RUR3WkE&tid=0B3N1d6szT1RYWkNET0pEbWhud3c#list ) Also download the 2 other files from that link.
2. Go to the root directory of your computer drive, usually C:\ and create a new folder with a simple name without special characters, neither spaces (for example, flash) to avoid problems in the process (at the end of the guide you will be able to delete that folder).
3. Go into that folder and extract the ROM, you must be able to see a folder named images and files together (Note: maybe you could need 7-Zip to extract it)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4. Now Install the other 2 files you downloaded. Then, reboot the computer and poweroff the phone
5. Exec the MiFlash tool, copy the path of the folder (for example, C:\flash) and paste it in the MiFlash tool
6. Now go to advanced
7. Click on Browse for Fastboot Script and choose flash_all.bat (if you are not able to see the file extensions, you should enable the viewing of file extensions (google for it))
8. Now put the phone in Fastboot mode (being it powered off, press power and vol- at the same time for a few seconds until the Fastboot logo appears) Note: to exit this mode, just press power for a few seconds
9. Now connect the phone to the computer with the usb cable (adaptors may give problems) and press on Refresh in the MiFlash tool in order for the phone to appear in it
10. Press on Flash, wait for the green bar to finish (could last minutes, just wait, if error is shown, post it here, if more than 1 hour and nothing changes, maybe is the computer, maybe is the cable, maybe is your bad luck). Done this part of the guide
Credits for this section of the guide
SECTION 3: Flashing guide (part 2/2: Flashing at last!)
1. (Downloading) Enter the Drive folder posted above and download the TWRP zip, the ROM of your desire (see below for reading more of every ROM), the google apps (MIUI already comes with preinstalled google apps, not needed in that case; also, you can download the google apps at opengapps.org and picking ARM64 and 6.0 android (or the version that the ROM you are choosing is, probably 6.0), and picking pico or nano is enough, comparison table here https://github.com/opengapps/opengapps/wiki/Package-Comparison ) and the supersu (only if you want root, anyway you can flash supersu at anytime without needing to wipe or anything, is easy). If you didn't do the part 1/2 and you need the Windows drivers, you can download it from the Drivers Windows folder, install it and reboot the computer.
1.1 (Uncompressing) Unzip the TWRP file in a sort path from the root folder, like for example in C:\TWRP (at the end of the guide you can delete this). You should see a file called recovery.bat (if you can't see extensions, google for enable it), it is for the step 3.
1.2 (Testing MTP) We will need to use MTP while we are in the recovery mode, so first let's test it in Android. While the phone is fully booted in Android and in the launcher screen (if starting for the first time, skip all the tutorial with whatever info), plug the phone to the computer, and in the phone swipe down the notifications bar, you should see a notification saying something of MTP or wired connection, activate MTP. Now in the computer, open My Computer and you should see Mi4C there, open it and try to navigate and create a folder, if all is ok, it works. If you are not able to create a folder o transfer any file from your computer, do not continue until this is fixed.
2. (Fastboot) First, keep the TWRP folder open and the recovery.bat file visible. Unplug the phone and put it in Fastboot mode (power it off, then Power and Vol- for a few seconds)
3. (Recovery flashing) Just execute the recovery.bat file (double click) and press a key if it asks for it (there should appear a green window with text). Done, recovery flashed (read text to see if everything is done). Now with TWRP installed, you won't need anymore (you shouldn't) the computer for using fastboot, now only for transfering the ROM files to the phone to use it from the TWRP.
4. (Wiping) Now let's boot into Recovery mode (TWRP in this case), two ways for it: you can Power and Vol+ while it is powered off, or you can boot Android, go into Settings, About phone, updates and in the 3 dot menu, there is a button for booting into recovery.
Note about the first TWRP start, it should appear this screenshot
Just press on never show again and swipe. Now, in TWRP, enter Wipe, select all partitions and wipe them all, it should appear an error about usb otg, doesn't matter, wipe is done correctly. Now you need to reboot into Recovery mode again, needed when wiping partitions another than cache or dalvik cache (if you don't reboot now, it won't let you flash), so press the mid button in the navigation bar to go to the main menu, and enter in Reboot > reboot recovery. If a message of "no OS installed" or "install supersu" appears, say no or ignore
5. (Flash!) Now, with the phone plugged, MTP should be working, so now you have to transfer the ROM, gapps and supersu files (gapps=google apps; gapps and supersu if needed as i explained in step 1). Now in the phone, press install, select the ROM, then add zip, select the gapps, add zip, supersu, and then swipe, a minute later there should appear a reboot system (android) button and the wipe cache button, first press wipe cache button, do it, and then reboot system.
Congratulations, now you can consider yourself a h4k3r, next step hacking into NSA maybe or something? Wait for the guide
From now on, flashing will usually consist in downloading the rom file from the phone (or from the computer and then transfer to the phone) and with the same gapps and supersu files downloaded above, you can flash, and then wipe cache. This is a dirty flash, only do it if updating a ROM, if going o another type of rom you must clean flash, which is done by first wiping all partitions as done in step 4 (note: all personal data would be lost, backup with titanium backup for example, and transfer all files to computer)
SECTION 4: Summary of ROMs available to our phone
MIUI: the ROM that comes with the phone, made by Xiaomi, full of features, loved by ones, hated by others
-MIUI chinese: the original official Xiaomi one, only in english and chinese languages, and comes with preinstalled chinese apps. Two variations: stable (released like once per month) and weekly
-MIUI .eu: modified version of the chinese, removed preinstalled chinese apps, a lot of languages included. Also comes in stable and weekly versions.
CyanogenMod: is a proyect which purpose is to make the full ROM open sourcered, and include more features than the official Google Android ROM doesn't include.
-CM from Kumajaya: most popular edition for our phone, this guy is doing a very good job with the kernel, making the ROM very stable and battery efficient.
-CM from Team Superluminal (TSL): they were the first to bring us CM, is not open sourcered (or at least is not their main job, as opposed to kuma) but is pretty stable, more recommended for noobies, kuma is more for staying up to date frequently
Resurrection Remix: a ROM that brings together a lot of different ROMs, unifying a lot of features. In Mi4C is a bit unstable for now, but is a matter of time.
Moke
SLIM
And I add here a link for a nice unlocking bootloader guide http://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
Recovery + Official ROM
THREAD REMINDER
akrai said:
First of all, sorry for publishing an uncomplete guide, im traslating my own full spanish guide and at the same time making it more complete and better, and i decided to do it this way, publishing progressively
/////////////////////////////////////////
SECTION 1: Android argot summary
I put this link here so any new user in the Android rooting/flashing world can learn the classic words used
http://www.talkandroid.com/guides/beginner/android-rom-and-rooting-dictionary-for-beginners/
Note: in bootloader it says that the phone comes locked, which in our case usually is not the case, but anyway you can know if your phone is locked just by trying to get into the fastboot mode, if you can't get into it, its locked.
An Android phone's disk is virtually splitted in several partitions, like a computer, but not exactly the same because even when your phone has a lot of partitions, you will only see one if you didn't rooted your phone, or two if you did, and the partition where you have your photos and the rest of your personal downloaded things is named sdcard (yes, is a legacy of Android, even when we don't have sdcard), or even in some ROMs is called userdata or something like that; another partition is system, where the ROM itself is, is like the installation of Windows; another is data, where the config files of the apps are stored when you start using them; another is cache, where the cache of the apps are (you can think of it like the apps are compressed always, and to run faster they descompress themselves in that partition), and there are two of those partitions: dalvik cache and cache; also bootloader, which is like the BIOS of the computer, is the most basic program that makes possible the phone to boot, and also it is not possible to edit it, it is not writable, it is this way so that you wont never be able to hardbrick your phone (which means that you can literally drop your beautiful phone into the trash, no way of fixing it), like it was in older phones, and also in this partition you also have the fastboot mode, which i'll explain later; and the last one im explaining (there are more but you probably wont never know about them) is recovery, where there is installed the recovery, and what is recovery? is a tool which is by itself an entire operating system, but made specifically for "developing" purposes, mainly for flashing ROMs and making backups of the entire partitions. We have two recoverys for Mi4C, the Mi Recovery, which comes by default with your phone, and is very limited, mainly you can only flash Xiaomi's official ROMs, and the TWRP recovery, which is the absolutely most popular recovery, and strongly suggested to use, no disadvantages at all. Also know that, like in Windows you can't format the very own Windows partition and you must use and external tool, which would be the Windows installation CD program or something like that, here we have the recovery, you can't flash or wipe using Android, you must be in the recovery mode.
So as I said, the bootloader is readable only by security, and it includes the fastboot tool, so you must know to lost the fear of this world, that YOU WON'T BE ABLE TO HARDBRICK YOUR PHONE, you will always have fastboot to reflash a complete Android ROM (which requires a computer and a fastboot ROM, which is different than a flashable ROM. You will use a fastboot ROM in the first flashing tutorial, more bellow)
What is Fastboot? Basically is a tool which acts like a server in the phone, and as a client in the computer, and is made mainly to make basic things to the phone, like flashing partition images (included in the fastboot ROMs, extension of each one is .img) or read the locking status of the bootloader.
What is a locked bootloader? In our phone, is a bootloader that only allows you to flash official xiaomi roms, but as xiaomi don't offer a global version of miui for our phone, the only official rom is the chinese one, which appart than having only english and chinese languages, is very bloated of chinese apps, so is very recommended to unlock the bootloader and flash any other rom of your desire.
How to access fastboot? First, shut down the phone; second, press at the same time the Power and the Vol - buttons for a few seconds, there should appear in the screen a Fastboot logo. Note that the phone may automatically shutdown if no connection is made with a fastboot client in a computer in about 10 seconds after entering fastboot mode
How to access recovery? First, shutdown the phone, then press at the same time power and vol+ for a few seconds
What is ADB? Is a tool that works the same way as fastboot (phone and computer connected), but instead of being in bootloader, it is inside of android, and instead of doing essential work for the phone, it does more practical things like transfer of files, but you will probably not use ADB at any time. Also, for transfering files you wont use ADB, which like Fastboot is a command line tool only, but you will use MTP, which is the media transfer protocol, the graphical way of transfering files, in your computer it will appear like a classical external drive, but in Windows the icon will be like an iPod.
Note before starting the flashing tutorial: go to Settings > (bottom) About phone and look at the MIUI version, MIUI version numeration is supposed to follow a date (the date of release) except the first number which could not be the year, it could be 5, 6 or 7, so a correct numeration would be for example 7.2.1.0 (there is always a 4º number which is always 0 if do remember well). The thing is that when you buy the phone to a reseller, is very usual that they flash their custom MIUI rom which comes with international language, its fine, but it also comes with spyware and adware everywhere. Those roms usually comes with a version numeration of strange repeated numbers, like 77. 87. 55. 99., remember that the first number always must be 5, 6 or 7. In case that you have preinstalled this rom, i suggest you strongly to follow the guide fully, including the clean flashing with fastboot rom
Note 2: you need to have the bootloader unlocked in order to continue, please read the unlock tutorial below
Note 3: this guide supposes you have Windows. If you have Linux or Mac, or you have any problem, please ask here
Note 4: for this guide we are going to use a Drive folder shared with a spanish mi4c community, so file names may contain spanish words but shouldn't be a problem. Sorry for the inconvenience, but it's for ease purposes. Drive link: https://drive.google.com/folderview?id=0B3N1d6szT1RYWkNET0pEbWhud3c#list
SECTION 2: Flashing guide (part 1/2: cleaning)
We are going to flash the 7.1.4.0 fastboot ROM in order to update as much as we can all the firmware (drivers of usb, modem, camera...), clean all from the weird ROM of the reseller and all of that without locking the bootloader.
Please, charge your phone first to at least 50%. Also, this process will erase all your personal data in the phone, backup all you need before.
1. Download the Fastboot 7.1.4.0 ROM (for example, here https://drive.google.com/folderview...RUR3WkE&tid=0B3N1d6szT1RYWkNET0pEbWhud3c#list ) Also download the 2 other files from that link.
2. Go to the root directory of your computer drive, usually C:\ and create a new folder with a simple name without special characters, neither spaces (for example, flash) to avoid problems in the process (at the end of the guide you will be able to delete that folder).
3. Go into that folder and extract the ROM, you must be able to see a folder named images and files together (Note: maybe you could need 7-Zip to extract it)
4. Now Install the other 2 files you downloaded. Then, reboot the computer and poweroff the phone
5. Exec the MiFlash tool, copy the path of the folder (for example, C:\flash) and paste it in the MiFlash tool
6. Now go to advanced
7. Click on Browse for Fastboot Script and choose flash_all.bat (if you are not able to see the file extensions, you should enable the viewing of file extensions (google for it))
8. Now put the phone in Fastboot mode (being it powered off, press power and vol- at the same time for a few seconds until the Fastboot logo appears) Note: to exit this mode, just press power for a few seconds
9. Now connect the phone to the computer with the usb cable (adaptors may give problems) and press on Refresh in the MiFlash tool in order for the phone to appear in it
10. Press on Flash, wait for the green bar to finish (could last minutes, just wait, if error is shown, post it here, if more than 1 hour and nothing changes, maybe is the computer, maybe is the cable, maybe is your bad luck). Done this part of the guide
Credits for this section of the guide
SECTION 3: Flashing guide (part 2/2: Flashing at last!)
1. (Downloading) Enter the Drive folder posted above and download the TWRP zip, the ROM of your desire (see below for reading more of every ROM), the google apps (MIUI already comes with preinstalled google apps, not needed in that case; also, you can download the google apps at opengapps.org and picking ARM64 and 6.0 android (or the version that the ROM you are choosing is, probably 6.0), and picking pico or nano is enough, comparison table here https://github.com/opengapps/opengapps/wiki/Package-Comparison ) and the supersu (only if you want root, anyway you can flash supersu at anytime without needing to wipe or anything, is easy). If you didn't do the part 1/2 and you need the Windows drivers, you can download it from the Drivers Windows folder, install it and reboot the computer.
1.1 (Uncompressing) Unzip the TWRP file in a sort path from the root folder, like for example in C:\TWRP (at the end of the guide you can delete this). You should see a file called recovery.bat (if you can't see extensions, google for enable it), it is for the step 3.
1.2 (Testing MTP) We will need to use MTP while we are in the recovery mode, so first let's test it in Android. While the phone is fully booted in Android and in the launcher screen (if starting for the first time, skip all the tutorial with whatever info), plug the phone to the computer, and in the phone swipe down the notifications bar, you should see a notification saying something of MTP or wired connection, activate MTP. Now in the computer, open My Computer and you should see Mi4C there, open it and try to navigate and create a folder, if all is ok, it works. If you are not able to create a folder o transfer any file from your computer, do not continue until this is fixed.
2. (Fastboot) First, keep the TWRP folder open and the recovery.bat file visible. Unplug the phone and put it in Fastboot mode (power it off, then Power and Vol- for a few seconds)
3. (Recovery flashing) Just execute the recovery.bat file (double click) and press a key if it asks for it (there should appear a green window with text). Done, recovery flashed (read text to see if everything is done). Now with TWRP installed, you won't need anymore (you shouldn't) the computer for using fastboot, now only for transfering the ROM files to the phone to use it from the TWRP.
4. (Wiping) Now let's boot into Recovery mode (TWRP in this case), two ways for it: you can Power and Vol+ while it is powered off, or you can boot Android, go into Settings, About phone, updates and in the 3 dot menu, there is a button for booting into recovery.
Note about the first TWRP start, it should appear this screenshot
Just press on never show again and swipe. Now, in TWRP, enter Wipe, select all partitions and wipe them all, it should appear an error about usb otg, doesn't matter, wipe is done correctly. Now you need to reboot into Recovery mode again, needed when wiping partitions another than cache or dalvik cache (if you don't reboot now, it won't let you flash), so press the mid button in the navigation bar to go to the main menu, and enter in Reboot > reboot recovery. If a message of "no OS installed" or "install supersu" appears, say no or ignore
5. (Flash!) Now, with the phone plugged, MTP should be working, so now you have to transfer the ROM, gapps and supersu files (gapps=google apps; gapps and supersu if needed as i explained in step 1). Now in the phone, press install, select the ROM, then add zip, select the gapps, add zip, supersu, and then swipe, a minute later there should appear a reboot system (android) button and the wipe cache button, first press wipe cache button, do it, and then reboot system.
Congratulations, now you can consider yourself a h4k3r, next step hacking into NSA maybe or something? Wait for the guide
From now on, flashing will usually consist in downloading the rom file from the phone (or from the computer and then transfer to the phone) and with the same gapps and supersu files downloaded above, you can flash, and then wipe cache. This is a dirty flash, only do it if updating a ROM, if going o another type of rom you must clean flash, which is done by first wiping all partitions as done in step 4 (note: all personal data would be lost, backup with titanium backup for example, and transfer all files to computer)
SECTION 4: Summary of ROMs available to our phone
MIUI: the ROM that comes with the phone, made by Xiaomi, full of features, loved by ones, hated by others
-MIUI chinese: the original official Xiaomi one, only in english and chinese languages, and comes with preinstalled chinese apps. Two variations: stable (released like once per month) and weekly
-MIUI .eu: modified version of the chinese, removed preinstalled chinese apps, a lot of languages included. Also comes in stable and weekly versions.
CyanogenMod: is a proyect which purpose is to make the full ROM open sourcered, and include more features than the official Google Android ROM doesn't include.
-CM from Kumajaya: most popular edition for our phone, this guy is doing a very good job with the kernel, making the ROM very stable and battery efficient.
-CM from Team Superluminal (TSL): they were the first to bring us CM, is not open sourcered (or at least is not their main job, as opposed to kuma) but is pretty stable, more recommended for noobies, kuma is more for staying up to date frequently
Resurrection Remix: a ROM that brings together a lot of different ROMs, unifying a lot of features. In Mi4C is a bit unstable for now, but is a matter of time.
Moke
SLIM
And I add here a link for a nice unlocking bootloader guide http://forum.xda-developers.com/mi-4c/general/guide-unlocking-mi4c-bl-verification-t3336779
Click to expand...
Click to collapse
Hello Akrai,
First of all, I wanna thank you all your effort and dedication in helping us to fiddle with our smartphones. Thanks to people like you, the rest of us can enjoy greater funcionality and custome options.
On the other hand, I've got a doubt that I'd love you could shed light on. You'll see: not long ago I acquire a Xiaomi Mi4c device & my intention is being able to have added features of development in case I'd feel like trying things. However, I currently just want to have available tools as the recovery flashed and root access without getting to change to an EU version ROM, I mean, keeping the official developer ROM that it's already installed.
So, here my question: can I install the recovery without needing to change at ROM.eu and, therefore, avoiding to reinstall the Oficial developer one again? If I want to keep the aforementioned ROM, is that one which I've got to insert on the root folder of the phone?
Lastly, in the official ROM you can be root through the Security App/permissions. So, ¿Do I need equally to get SuperSU? Because It's not necessary to obtain root by other way running the official developer, right? I unlocked the bootloader and enabled root access already, certainly.
Thank you so much beforehand. I hope that I expressed myself clearly enough and so you can help me.
Greetings!
Lucas ^^.
Thanks a lot!!
Thanks a lot!! This is the first time I am using your post to clean-up a Xiaomi Mi4C of chinese bloatware, unlock and install a custom ROM from your particular google drive links... Am going to bookmark this for further use!!
Thanks a lot, very informative and descriptive...:good:
Can this method still relevant today on MIUI 9.2.2.0?
Hey, I have my Mi4C on MIUI 9.2.2.0 stable china. Can this method work for my phone now?
I have problem with mi flash unlock.
Long ago when I purchased this phone, it used a “reseller” ROM and this method worked just fine.
Anyone?
Sorry wrong thread. I should post in unlocking guide
Related
I have a uk wifi only XOOM on Honeycomb 3.2. I want to root but do I have to unlock the bootloader first? What is the easiest way to unlock the bootloader and root without adb or fastboot commands. I've looked at 'xoot', 'cornea', and the 'Lord AIO tool'. Do all these methods unlock the bootloader and root? Can anyone confirm that they work for this model? Are there any other easy methods that I've missed?
Also, after I have unlocked the bootloader and rooted can I install cwm recovery from rom manager and then even the team eos v1.0.0 ics rom?
Thanks in advance for your help (I did search, but not much info came up about these methods).
wifi-only-xooms should all be the same.
don't know about the root-methods you mentioned, I used one that includes adb/fastboot-commands (an amazing total of 4 commands were used that day). This is a link to the method I used, it will also work for your xoom.
Why do you want to avoid adb/fastboot-commands?
Thanks for reply. I don't feel confident using adb. And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Thanks again.
RiThBo said:
Thanks for reply. I don't feel confident using adb.
Click to expand...
Click to collapse
don't worry, its not exactly a rocket science...
RiThBo said:
And I don'tk now how to use it set it up. Do you know an up to date guide explain how to set it up?
Click to expand...
Click to collapse
no, but this is what you'll need to do:
preparations
disable any anti-virus, anti-adware, firewall software you might have on your computer. Best would be to completely uninstall those. If you're using the windows firewall, disable it. You may re-install/activate it after you are done flashing your device.
download and install JDK
google says that the JDK (Java Development Kit) is needed to run the Android SDK. I am not sure if the JRE (Java Runtime Environment) is sufficient, but to play it safe, we're just gonna install the JDK. (JRE is needed to run Java applications, JDK usually to develop Java applications. However, JRE is a part of the JDK and the JDK wont clog up your computer in an excessive way, so you should be safe just using the JDK)
go here and hit the download button beneath JDK.
under "Java SE Development Kit 7u2" (at time of writing, in the future, the release-number might be higher), click the "Accept License Agreement"-option and find the Download that is right for your version of windows. x86 and i586 are names for 32-bit-versions of windows, if you are using a 64-bit version of windows use the file that reads windows-x64 in its name.
install the file, shouldn't be too hard
download and install motorola drivers
If you are using windows, you will need the motorola USB-driver package for adb and fastboot to work.
download the motorola drivers from the motorola website. Open motorola.com, find the xoom's page, find a link saying "support", on the right column of that page you should find a link named "USB-Drivers" or something like that in the "software updates and drivers" section. You should get a page with a link "Download Motorola USB-Driver v5.4.0 with MotoHelper". Do not download the stuff labled "USB-Charging drivers".
At the time of writing this, this link will lead to this file.
once this file has downloaded, just run it and follow the on-screen instructions.
download, install and set up android SDK
The Android SDK (Software Development Kit) is needed to develop applications for android. It also contains the programs adb and fastboot, which we will need. The program SDK Manager, which we will use, is used to download certain parts of the Android SDK.
go to developer.android.com/sdk/ and download the current SDKs zip file. I know, it recommends the installer, but just don't download that.
the zip will contain one folder called "android-sdk-windows", just have your favorite program extract this folder to C:\. I renamed this folder to android-sdk, this is optional but i will assume you did for the following instructions.
you should now have a program C:\android-sdk\SDK Manager.exe. Run it.
A window will open and the program will download a list of currently available packages. After this list has been refreshed, you should find a "Tools"-folder with "Android SDK Tools" and "Android SDK Platform-tools". Check both and hit the button "Install (2) Packages". You won't need anything else unless you really want to develop apps for android.
the installation will take a bit, afterwards, you will find new folders in C:\android-sdk\: tools and platform-tools. Please check, that the platform-tools-folder contains the programs adb.exe and fastboot.exe
(Optional)add tools and platform-tools to your PATH
If you enter a command in windows' command prompt, it will try to locate this command (essentially a program) in the directorys specified in the current directory. If it can't find the program there, it will search in the directories specified in your PATH-Variable.
This step is only needed, if you want to be able to use the adb or fastboot-commands from any directory, like Desktop, your Users folder, etc.
These instructions apply to Windows 7, they will be similar in other Versions of windows.
As I am currently on a german machine, these instructions are a little unspecific. If any user with an english installation of windows 7 could post the exact names for these links&buttons, that would be greatly appreciated.
hit Start, right-click "My Computer" and hit "Properties"
in the left tab, the 5th link from the top should read something like "Advanced System Settings". Hit that link.
a window "System Properties" opens up. Navigate to the 3rd tab "Advanced" and hit the button on the bottom of this Tab "Environment Variables..."
you will see two tables, in the lower list (entitled "System Variables") you should find the variable named "Path": Click on it and hit the Edit-Button below the table.
a small window will pop up with a long text in the lower field (value of the variable). I can't stress this enough: DO NOT DELETE WHATEVER IS WRITTEN IN THERE!!!. Instead: APPEND ";C:\android-sdk\tools\;C:\android-sdk\platform-tools\" without the "". the first ; MUST be there.
hit OK in all three windows
done
This should basically do it. You can now connect your xoom with your computer. Make sure USB-Debugging on the xoom is enabled, that option should be somwhere in Settings -> Development. The first time you connect your xoom with debugging enabled, Windows should give you a message that it is installing some new drivers, but that should work automatically. Same goes for the first time connecting your xoom in bootloader mode.
You can now open a command prompt (Win+R, enter cmd, hit run) and enter "adb devices", it sould read something like
Code:
C:\>adb devices
List of devices attached
012c3456789f1234 device
, that means it worked. From here on, you can follow the instructions in the thread I mentioned in my previous post.
---------- Post added at 06:15 PM ---------- Previous post was at 05:18 PM ----------
RiThBo said:
UPDATE: I have now set up adb. Please could you give a little more detail on the method you used. Specifically the unlocking the bootloader part and flashing the recovery via fastboot.
Click to expand...
Click to collapse
crap, read that too late. But anyways, since I'm already on it:
preparation
we will need some files in order to get your xoom runnin a custom rom. In this section we will download them and put them into their places.
create a folder on your desktop and name it "xoom"
check this thread for downloads. What you will need is Universial xoom root and ClockWorkMod recovery. But again, please check the named thread for updated files. All credits to these files go to their original posters.
at this point, you might just as well just download your new rom, but I won't go into this at this point.
you need an micro-sd-card for your xoom. You cannot use the internal /sdcard partition for this
place the universial xoom root zip-file onto your sdcard. If you already downloaded your new rom, put that onto the sdcard as well, it should be a flashable .zip-file.
place the ClockWorkMod-File in your Desktop\xoom-folder and rename it to recovery.img .
put the sdcard into your xoom, if it isn't in there already
boot the xoom
enable USB-Debugging (Somewhere in Settings -> Development)
connect your xoom using a good and short USB-cable. Let this cable be a trustworthy cable, one that you barely use and that has not been bent, cut or otherwise abused.
right-click on the xoom-folder on your desktop while holding the shift-button on your keyboard and hit "open Command prompt here" (or sth. like that, again, my windows is german)
enter adb devices to make sure adb is working, if your device shows up in the device list, everything is good:
Code:
C:\Users\llama-power\Desktop\xoom>adb devices
List of devices attached
012c3456789f1234 device
unlock your xoom
unlocking your xoom will enable us to flash new files to your xoom. We want to do this. However, unlocking your xoom will void your warranty and DELETE EVERYTHING you've got on your xoom. To unlock this we're gonna reboot the xoom into the bootloader and have it unlock your xoom
to get into the bootloader, you may now just enter adb reboot bootloader
wait a minute. Your xoom should shut down, and reboot into the bootloader. continue if you see the red M and "Starting Fastboot protocol support." on your xooms display
check if fastboot is set up correctly. Enter fastboot devices , this should list your device, just like when you tested adb
enter fastboot oem unlock , this will start the unlocking process. Follow the instructions on your xoom. Bear in mind, this will really delete everything and void your warranty. You Control this thing using the volume up/down-buttons. volume down changes the selection, volume up selects whatever is on your screen. the xoom will ask you if you want to delete/void your warranty/unlock your xoom and if you say yes, it will ask you, if you really really want to do this and then it will unlock itself and delete everything.
I'm not sure if your xoom will reboot on itself or if you will be back to the bootloader screen. in the latter case, just enter fastboot reboot
Your device is now unlocked and has rebooted into a shiny new Desktop.
installing ClockWorkMod
Clockworkmod is a recovery that gives you a lot more options than the stock recovery. For example, it will enable you to create backups, delecte specific partitions and install non-motorola update.zip-files
to install CWM recovery, we will again need to go to the bootloader. So just enable usb debugging in your xooms settings again (remember, you wiped that when you unlocked it) and enter adb reboot bootloader
wait until you are back in the bootloader and "Starting Fastboot protocol support" appears on your screen
to flash the new recovery, just enter fastboot flash recovery recovery.img
remember, for this to work, you still need to be in your desktop\xoom-folder and the recovery-image must be named recovery.img. If your recovery-image is named differently, just modify this command accordingly (fastboot flash recovery blahblub.img)
watch your xoom's screen, once it says that it has successfully flashed the recovery, you need to reset your xoom. It is important, to know how to boot into the recovery right away, so please read this step thoroughly before starting.
To reset the xoom, press and hold vol-up + power for about two seconds. Your xoom will restart. Once the red M appears, wait 3 seconds and then press vol-down. It should ask you what to do (display --> Android Recovery). You can change the option with von-down, select with vol-up, highlight Android Recovery and select it with vol-up.
if this suceeded, you should be in the ClockworkMod recovery (Your background image should now be a green robot). If not, you have to restart with flashing the recovery. Do not boot into android as, depending on your OS-Version, it will reset the recovery to stock.
backup your system
Why would you want to backup now, this system is as stock as it gets??? Exactly, maybe you will want to revert back to a stock xoom, so keeping a backup of this will be nice
Right now you are in the Clockworkmod-System, controls are: vol-up/down: cursor up/down; power: select
using the vol-down-button on your xoom, navigate to "backup and restore" and hit the power button
make sure "Backup" is highlighted, hit power to start the backup process. It will backup basically everything from your xoom onto your sdcard
after this is done use the "+++++Go Back+++++"-links to go back to CWMs main menu. Do not reboot, as this will probably delete CWM
root your xoom
If you root your xoom, you will be able to do much more on your xoom. The universal xoom root update.zip will also prevent your xoom from deleting the Recovery upon boot.
using vol up/down, navigate to "install zip from sdcard", hit power to select
use "choose zip from sdcard"
pick the Xoom-Universal-Root.zip
find the entry that says "yes"
once that is done, "+++++Go Back+++++" until you find an entry "reboot System now", hit that one
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
All credits go to creators of the downloaded files, I assembled these instructions from their threads or other informations. I have not created a single of these files.
Thank you so much!!!: That was just what I needed. Thanks for all the amazing detail, I will try it in the next couple of days when I built up the courage!
Amazing guide!!! You should set up your own thread or send it to solarnz (the guy who mad the universal root).
UPDATE: In the part where I flash recovery.img , You told me that I should shift+right-click ,then open command window and type adb devices. adb isn't recognised in the desktop - xoom folder, however it works if I run it from C:\android-tools. Do I need to place the recovery in the android-tools folder?
llama-power said:
Your xoom should now be unlocked, rooted and be equipped with a new recovery system. To install a custom rom, reboot into the recovery (reboot the xoom, when the red M appears, wait three seconds, hit vol down, then vol up) and just install the custom roms update.zip. Be sure to follow the roms installation instructions, you might need to wipe certain partitions or manually install more than one package (for example for the google applications)
Click to expand...
Click to collapse
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
TheDifference said:
So, i can just copy the .zip from here (http://forum.xda-developers.com/showthread.php?t=1488075) onto the root of the SD card and then follow your instructions above?
Edit - I've already unlocked and rooted
Click to expand...
Click to collapse
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
llama-power said:
yes, but be sure to pick the right .zip-file for your xoom. AFAIK, the bugless beast is not available for european or us 3g xooms. Using a zip that has been made for another model may permanently damage your xoom (some MZ601 users reported that they were unable to get 3g working again after installing a MZ604-rom, not even after installing official MZ601-rom)
Click to expand...
Click to collapse
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
TheDifference said:
mine is/was an australian Telstra Xoom. does that make it more likely to be euro or US?
Click to expand...
Click to collapse
i THINK it should be comparable to the EU-xoom. What's your model number? It should be printed on your box and, if you haven't flashed any custom rom yet, in your xooms settings. It should read MZ60*.
MZ600 is the US-3g-model for CDMA-Networks.
MZ601 is the EU-3g-model for GSM-Networks.
MZ602 is the MZ600 upgraded with the LTE-Module.
MZ604 is the wifi-only-model
if you can't find a bugless beast-rom for your xoom, I'd recommend the team EOS nightlies, work really niceky for me
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
madmanrx said:
I followed these instructions. When I got to the point of installing the new ROM I ended up at the bot with the "!". What do I do now?
Click to expand...
Click to collapse
you are talking about the standard-android-bot, and it shows up after trying to reboot into recovery, right?
That means, that the recovery has been overwritten w/ the stock recovery. This happens when you don't root after installing the cwm recovery and before rebooting, or if the rooting fails.
If you already made the backup, you should be on the safe side, just go ahead and redo the section "installing ClockWorkMod". at the end of thiis section, you should be in the recovery, just install your rom from there, skip the backup- and root- sections and do not reboot before the rom and gapps-packages have been installed.
Boot screen
Thanks Llama.
I did what you said. After flashing ROM (i think) and loading Gapp I rebooted and now it is just on the red M screen and doing nothing else. Please help! I can get back into clockwork recovery. what am I doing wrong. As if its not obvious, I'm a total noob.
edit: Wow! Somehow I got it to work. I now have EOS rom. Thanks everyone!
Did something wrong
Okay, I have the EOS rom, but I can't find any of my apps. I thought I backed up everything on my internal storage. I loaded the backup into the internal storagage after the flash, but no apps. Maybe I didn't backup the apps properly. I don't have adroid market on the new rom, and cant download any of my apps from market or amazon. ICS is great, but not much use without apps. I can't even download new apps. What am I missing?
do you have the google mail app? Android market is usually part of the gapps package, maybe you didn't install that package correctly?
I'd try to do a factory reset (wipe /data, /cache and dalvik-cache from recovery) and install the gapps .zip again.
how did you backup your apps? If at all possible, you should not reatore apps using titanium backup or something like that after upgrading from Honeycomb to ICS. Instead, you should install these apps from market manually and only restore those apps that you can't find on the market.
factory reset
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
madmanrx said:
So I go into clockwork recovery and "wipe data/factory reset"? then do i "wipe cache partition" or do I wide data before factory reset? After factor reset were do a start back in the procedures you decribed in detailed post? I really appreciate your help!
Click to expand...
Click to collapse
I am not entirely sure if you even have to wipe the cace partition, as a factory reset should also wipe the cace-partition. But just to play it safe:
go to recovery
wipe /cache partition
advanced->wipe dalvik-cache
wipe /data/factory reset
install zip from sdcard-> pick the gapps .zip
reboot
you do not start back in tzhe instruction, as they never described installing custom roms;-)
also, make sure you use the current gapps .zip, that should be release 10.5
sd card?
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
madmanrx said:
I did what you instructed with no problem. I ensured that gapp v10.5 is the one I have on my sdcard(as viewed on pc). But when I go to select .zip file from sdcard (from clockwork recovery), I get a menu that has the files I had on my internal storage, and the gapp.zip is not there. There is also a 'ifx_permissions' file on my internal storage (viewed on pc), and there are files that were not wiped out (files for apps).
Click to expand...
Click to collapse
which recovery did you flash? Did you use the Tiamat-modded recovery I recommended in post #2? With that recovery you shouldn't be able to see the internal memorys contents, instead you should only be able to see the sd-cards contents.
When booted into recovery, the first line should read "Clockwork Mod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)". If not, please flash the recovery image I recommended in post #2, according to the section "Installing ClockworkMod". After that, do what I wrote in post #16.
If you still have problems after that feel free to ask some more, glad I can give back a little of my knowledge
Magnanimous Gratitute
llama,
you are a scholar and a gentleman. I think I am finally up and running. I was entering recovery from ROM recovery. After your tutelage all is in order. I have Market now and apps are downloading. One final (i hope) noob question. How do I thank you (on the thread). You have certainly earned it!
madmanrx said:
How do I thank you (on the thread). You have certainly earned it!
Click to expand...
Click to collapse
you are very welcome
underneath every post there is a Thanks-Button
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
P770 Flashing and rooting guide:
NOTE: Dropbox has temporarily suspended my public links for "generating too much trafic". Please use a mega alternative.
NOTE1: understand that I cannot keep no warranty or responsibility on a result of your effort. Please consider your abilities as following operations can easily brick your device. Also, for some dealers of mobile phones, modification like those bellow results in loss of your warranty.
NOTE2: this guide, all the modifications are created by community, to community. Please be noted that non of those shall be used for commercial purposes. Also I will not provide any support to those who wants to use stuff bellow anyhow for commercial purposes.
NOTE3: please note that I am not a pro-programmer, developer, geek. I am a bit advanced user who shares its result to community. All the stuff is provided as-is.. I am able to help but in time limits of my demandative work and personal life that is not on web .
NOTE4: if you have phone from Etotalk with their ROM, it already includes CWM. But the CWM has been modified by Etotalk to prevent a ROM Backup. Some features common in “normal” CWM might not work in Etotalk version.
Lets go!
This guide contains:
1) Short explanation of P770 firmware versions and its differences
2) Preparation for phone memory flashing
3) Guide for Winflash recovery flashing, including english CWM (Clockwork Mod Recovery)
4) Guide for rooting your phone (using CWM) and Google Apps (optionally)
5) Flashing your ROM - general
6) Guide for ROM flashing using Winflash utility
7) Guide for ROM flashing using CWM
8) Guide for ROM flashing using CWM - Recovery
9) Recommended ROMs and links
1) Short explanation of P770 firmware
P770 has two branches of fimware – “World” and “Asian” versions.
First and very crucial difference is, that they use different memory partitioning, resulting in fact that it is not possible to combine those two versions freely. Trying to do so may result in bricking your phone. Details will described in point 5 bellow:
Main differences for users are:
Asian version, marked S118-S124: usually more actual as Lenovo is focused on Asian market. Typically does not include Google Apps, and very often packed with strange Chinese applications of questionable use. Usually supports only Chinese and English
World version, marked S106-S113
Version for world customers, usually shrinked from useless apps and containing Google Apps. Released with a bit delay compared to Asian version. Better support of European languages, sometimes contains more languages than English. I suppose that version is prepared mainly for Russian Market
2) Preparation for memory flashing:
a) Download this package and upack it as a whole somewhere in your computer:
https://dl.dropbox.com/u/25344416/P770/P770_update_utility.zip
alternative link: https://mega.co.nz/#!tFcFyAhJ!OInJjjvLV8VYtJUIvN0EKEJo7vI8ul9kDzv9y_3ukNg
b) Turn off your phone, unplug cable, remove battery. Insert the battery but DO NOT plug your cable or power on the phone.
c) Open your device manager in “windows/system”
d) Connect your phone by cable. A new device named “MT65xx Preloader” shall appear for about 3 seconds in a section “Unknown devices”.
e) Catch it with mouse and manually change the drivers to the ones located in “SP_Drivers_v1.5” folder of downloaded (unpacked) file.
f) After updating, turn off phone, unplug and remove battery, reinsert battery and plug a phone. You should see a device “MediaTek Preloader USB VCOM (Android) (ComX)" in a “COM and LPT” section. If you see it, you are ready to go!
- If you don’t see it, you did something wrong, most probably you were not fast enough in point e), retry from b)
NOTE: if you are unable to pass step 2, please reconsider your decision to play with your phone. If something goes wrong during next phases, you will probably end up lost and sad with bricked phone :crying:
3) Guide for Winflash recovery flashing, including CWM (Clockwork Mod Recovery)
a) Turn off your phone, unplug cable, remove battery. Insert the battery but DO NOT plug your cable or power on the phone.
b) Run flash_tool.exe from directory downloaded in 2a
c) Hit “Scatter loading” button and choose a file “MT6577_Android_scatter_emmc” from a directory according to a FW version you have (described in Point 1):
110_recovery for a “world” version
121_recovery for a “Asian” version
Don’t mix it up otherwise a flashing will fail.
d) Hit “download” button and confirm any warning message.
e) Connect the phone by cable (phone has to be off and in state described in 3a)
f) Red bars on bottom side of the screen will show you a progress. When finished, green circle will appear.
g) Close flashtool.exe, unplug your phone, remove a battery, reinsert it.
h) To boot to CWM do this:
Press and Hold a power button for about 2 seconds, then release it and simultaneously press and hold volume buttons (both + and -) until phone boots to CWM
4) Guide for rooting your phone (using CWM) and Google Apps (optionally)
a) Download this zip file and place it to the root of your SDCard
https://dl.dropbox.com/u/25344416/P770/Root_by_javum.zip
alternative link: https://mega.co.nz/#!MYd1UQyL!DwroiHcoML_iEHD2r1pwvSReM2MZgXJlhjeWMaeHlkM
b) Reboot to CWM (point 3h), choose “install zip from sdcard” “choose zip from sdcard” and choose the Root_by_javum.zip file. As the update proceeds, your phone is rooted. Reboot
Optional: Install google apps if necessary
c) Download this zip file and place it to the root of your SDCard
https://dl.dropbox.com/u/25344416/P770/gapps-jb-20120726-signed.zip
https://mega.co.nz/#!ERUzQAYa!RNAKJAxLj38cLKi_ezNIpClrHoYIiIaPGHmKqwzcieQ
d) Reboot to CWM (point 3h), choose “install zip from sdcard” “choose zip from sdcard” and choose the “gapps-jb-20120726-signed .zip” file. As the update proceeds, your phone has GAAPS included. Reboot
Note: this Google apps will work with a roms using Android 4.1.1, for other versions, different gaaps might be needed.
5) Flashing your ROM – general
Generally you have 3 options how to flash your ROM – full wipe by FLASHtool, via CWM zip install or via CWM recovery. The choice is usually up to the creator of the ROM as he chooses a way how backup is created.
Flashtool way is a most basic one, it erases not only a rom, but also repartitions a memory and erases internal data. SD card remain untouched. Flashtool way is very useful for switching from “World” to “Asian” version”
If you want to switch from “World” to “Asian” you have as a first step flash an Asian version by flashtool (e.g. you can use a P770_S121_winflash linked in point 9), then flash whatever Asian version you want. To switch back to European you have to use flashtool again (e.g flash P770_S110_winflash). Maybe there are a different ways, but this is only safe process I would recommend.
LAST WARNING: as mentioned above – for CWM flashes, NEVER mix up an “world” and “asian” version of ROM. The reason is that both types are having different partitioning, so if you will be lucky, the flash will fail. If you are unlucky, the flash will proceed, and you have just successfully bricked your phone
NOTE1: first boot of the phone can easily take about 5 minutes. If the phone stuck on boot logo for 10 minutes or more you have 2 options:
a) Boot to CWM and wipe everything (see point 7) and reboot
b) Reflash ROM again, or reflash another ROM.
NOTE2: some ROMs are rooted, some are not. Some includes Gaaps, some not. For guide how to solve it, return to point 4.
NOTE3: As there is mistake in Android 4.1.1, commercial widgets disappears after reboot. Its a mistake of Android, not ROM and can be easily solved by Titanium Backup. (App with widget you want to use has to be backuped by TB, then uninstalled and recovered from backup (all by TB). Problem shall be solved in next release of Android:
6) Guide for ROM flashing using Winflash utility
a) Turn off your phone, unplug cable, remove battery. Insert the battery but DO NOT plug your cable or power on the phone.
b) Run flash_tool.exe from directory downloaded in 2a
c) Dowload a ROM you need (you might look at point 9)
d) Hit “Scatter loading” button and choose a file “MT6577_Android_scatter_emmc” from a directory with a ROM
e) Hit “Firmware update”, the program will check the images (purple bars running in bottom part) and then awaits a connection of a phone:
f) Connect the phone by plug (phone has to be off and in state described in 6a)
g) Red bars on bottom side of the screen will show you a progres. When finished, green circle will appear.
h) Reboot.
7) Guide for ROM flashing using CWM
a) Download a ROM you want to flash (you may see Point9) and copy a zip file to a root of your SD card.
b) Reboot to CWM (see 3h) and do “wipe factory data” and “wipe cache”. Go to “advanced” and do “wipe Dalwik cache”.
c) choose “install zip from sdcard” “choose zip from sdcard” and choose the file you have placed on SD card.
d) When update is finished, perform one more time “wipe factory data”. Reboot.
8) Guide for ROM flashing using CWM - Recovery
a) Download and unpack a ROM you want (you may see Point9), to a directory on your card /clockworkmod/backup, that means that final route shall be /clockworkmod/backup/Romdirectory
b) Reboot to CWM (see 3h) and do “wipe factory data” and “wipe cache”. Go to “advanced” and do “wipe Dalvik cache”.
c) Choose “backup and restore”, “restore” ad “Romdirectoryname”. Restoration might end by error message, but its no reason to be scared.
d) Reboot
9) Recommended ROMs and links
Updated ROMs for P770 can be found here:
http://www.needrom.com/phone-roms/lenovo/p770/
Most actual versions appears usually on this Russian and Chinese forum, Google can translate:
http://bbs.ydss.cn/forum-Lenovo_p770-1.html
http://lenovo-forums.ru/forum/119-lenovo-ideaphone-p770/
So far, best roms I reccomend are:
1) S121 flashable via flashtool, I use it as a starting point for all the „asian“ mods:
https://dl.dropbox.com/u/25344416/P770/P770_S121_winflash.zip
alternative link: https://mega.co.nz/#!UY9GRCyb!S1C-Tz8Foc47atKPkD20HSsBROBZfZbOKEt36-5iNGY
2) S110 flashable via flashtool, I use it as a starting point for all the „european“ mods:
https://dl.dropbox.com/u/25344416/P770/P770_S110_winflash.zip
alternative link: https://mega.co.nz/#!YYE03byB!I-iSvBu4pzi6PrZ9N3zn3TkRv24oQIHbmdau1FIEXXs
3) S124_maomi_Pu_mod, CWM zip flashable, my modification of latest Asian ROM, shrinked, removed Asian Apps, added More Locale and Xperia Launcher
https://dl.dropbox.com/u/25344416/P770/P770_S124_cwm_maomi_MOD_pu.zip
alternative link: https://mega.co.nz/#!FBN3SIwD!NK0jqVnxaYzlUPjGWvJf7iWb2YFp6sGo7zXMsltv76E
4) S113_Pu_mod, CWM Recovery flashable via Restore, not rooted, my modification of newest world ROM, shrinked, added More Locale, Calendar Pad and Xperia Launcher, FV5 Camera is installed along original one, battery percentage ability in settings, reboot option while holding a power keyboard
https://mega.co.nz/#!1A1BmTjZ!WAjB8kLmeddS2ZqnfeerZF9yvjRduCPGepBBcUFK6n8
Last link (4) is my actual version I do personaly use.
Hope it helps!
Fast guides for "typical scenarios", all the links in guides points to the steps described in first post.
1) I want to backup my Etotalk ROM:
Note: Etotalk uses its own, modifyed CWM version. It does not allow to perform a ROM backup, so a backup starts but never ends until phones memory is full. To backup your ROM you have to:
1.1. prepare your computer for winflash acc point 2
1.2. Flash "S121_recovery" according point 3 you will have CWM 5.5.0.4
1.3. Reboot to CWM, and perform a flash backup (advanced-backup and restore-backup)
Note: "Etotalk" rom is based on asean S_121 firmware, for going back to Etotalk, follow steps according scenario 5.
2) I have Etotalk ROM and I want to switch to "European" ROM (S106-113)
2.1. prepare your computer for winflash acc point 2
2.2. perform a winfflash of S110 rom (link 9.2) acc point 6
2.3. flash "S110_recovery" according point 3, you will have CWM 5.5.0.4
2.4. Now you can flash any rom or mod of "European family" you want. Be noted that flashing can overwrite your CWM again, so if it happens, repeat step 3.
2.5. (optionaly) root your ROM according point 4
3) I have Etotalk ROM and I want to switch to other "Asian" ROM (S118-124)
3.1. prepare your computer for winflash acc point 2
3.2. perform a winfflash of S121 rom (link 9.1) acc point 6
3.3. flash "S121_recovery" according point 3, you will have CWM 5.5.0.4
3.4. Now you can flash any rom or mod of "Asian family" you want. Be noted that flashing can overwrite your CWM again, so if it happens, repeat step 3.
3.5. (optionaly) root your ROM according point 4
4) I have Asian version (118-124) and I want to switch to "European" ROM (S106-113)
4.1. prepare your computer for winflash acc point 2
4.2. perform a winfflash of S110 rom (link 9.2) acc point 6
4.3. flash "S110_recovery" according point 3, you will have CWM 5.5.0.4
4.4. Now you can flash any rom or mod of "European family" you want. Be noted that flashing can overwrite your CWM again, so if it happens, repeat step 3.
4.5. (optionaly) root your ROM according point 4
5) I have "European" ROM (S106-113) and I want to switch to Asian version (118-124)
5.1. prepare your computer for winflash acc point 2
5.2. perform a winfflash of S121 rom (link 9.1) acc point 6
5.3. flash "S121_recovery" according point 3, you will have CWM 5.5.0.4
5.4. Now you can flash any rom of "Asian version" you want. Be noted that flashing can overwrite your CWM again, so if it happens, repeat step 3.
5.5. (optionaly) root your ROM according point 4
Guys, please think twice before you ask by PM. Last days I am overloaded by the tons of questions, and about half of them are motivated by your tendency to save your time by wasting mine. Especialy questions like"please can you compare batery life to SXXX" drives me crazy....
If you want to know - flash and try.
If you are too scared of bricking you phone - keep your stock ROM
I dont want to be unpolite, but please do not be offended if your PM remains unanswered, especially when its obvious that you did not even read whole guide.
ROM Archive: links to older versions of my mods, if handy for anyone:
S110_Pu_mod, CWM Recovery flashable via Restore, my modification of world ROM, shrinked, added More Locale and Xperia Launcher
https://dl.dropbox.com/u/25344416/P770/P770_S110_cwm_mod_pu.zip
alternative link: https://mega.co.nz/#!QNFjRb6Y!aqYy325w-WKS38QkcemhqnltLls_DpoTzntjOiA1JBY
S111_Pu_mod, CWM Recovery flashable via Restore, my modification of world ROM, shrinked, added More Locale, Calendar Pad and Xperia Launcher
https://mega.co.nz/#!pMsy1LKS!aWqukSNdPadQsEuyFAhKV1YvaqZiL2-EYjSAxSrEFLI
S112_Pu_mod, CWM Recovery flashable via Restore, my modification of world ROM, shrinked, added More Locale, Calendar Pad and Xperia Launcher
https://mega.co.nz/#!YZshkLyZ!LJi_HR6NRa6jJKoORSckEkj8SeJ3-D4pgVPvekvbtpA
Very nice, thanks for your sharing!
Nice work! :good:
I flashed your S124 ROM while my phone was S110... Before you created this thread... I didnt brick my phone.
S124 is a nice ROM but i missed the business theme and magic launcher and lotus widget so i flash back original ROM.
About partitioning, does anyone know how to make internal storage bigger and usb storage smaller? Cause unfortunately stock ROM takes lot of internal memory space...
vietchecz said:
I flashed your S124 ROM while my phone was S110... Before you created this thread... I didnt brick my phone.
S124 is a nice ROM but i missed the business theme and magic launcher and lotus widget so i flash back original ROM.
About partitioning, does anyone know how to make internal storage bigger and usb storage smaller? Cause unfortunately stock ROM takes lot of internal memory space...
Click to expand...
Click to collapse
Lucky you. I found several threads reporting a problems during S110xS124 and vice versa, so I recomend full flash as safe way.
As my primary goal is to shrink a size of a ROM, live wallpapers, etc are intentionaly deleted in my mods.
Non of above links is work
regards
s124 -> s110
hello,
i have a friend who have this phone with s124 version. (asia version)
but he need the phone in european version (s110) french if it's possible.
i think i just need to flash with flashtool all the rom but everytime i want use your dropbox link it's an error 509.
can you upload the files and maybe explain what i must take care to change the rom?
thank you
hallo, seems that a Dropbox has suspended my public links. I have added Mega alternatives.
sekptar: I hope that a to-do writen above is complete, all the informations are there. First flash the full S110 ROM according points 2 to 6. Then if you want, flash my S110 mod according point 7.
I dont know about any ROM with full french support. Install More Locale 2 to get at least partial French support.
many thanks
finally it works now.
regards
The instructions provided in the guides are quite clear however i dont understand the rooting procedure
Yes that's work.
He took english, easier than chinese..
Thank for all
Sent from my GT-N7100 using xda app-developers app
abs0lut3z33r0 said:
The instructions provided in the guides are quite clear however i dont understand the rooting procedure
Click to expand...
Click to collapse
Rooting is quite easy. Just download a "root_by_javum.zip" file, and flash it via CMW. Nothing more, nothing less.
I got it rooted , I will post some revisions in the instructions soon
Sent from my Lenovo P770 using Tapatalk 2
f) After updating, turn off phone, unplug and remove battery, reinsert battery and plug a phone. You should see a device “MediaTek Preloader USB VCOM (Android) (ComX)" in a “COM and LPT” section. If you see it, you are ready to go!
Click to expand...
Click to collapse
Hi, I've installed the driver (SP_Drivers_v1.5) in Step 2.. but couldnt find the 'Mediatek...' under 'COM and LPT'.. When I plug in the phone (turned off), it didnt show anything in the device manager..
what should I do next?
This is entirely on my own experience on win7 x64
2) Preparation for memory flashing:
a) Download this package and upack it as a whole somewhere in your computer:
https://dl.dropbox.com/u/25344416/P7...te_utility.zip
alternative link: https://mega.co.nz/#!tFcFyAhJ!OInJjj...l9kDzv9y_3ukNg
b) Turn off your phone, unplug cable, remove battery. Insert the battery but DO NOT plug your cable or power on the phone.
c) Open your device manager in “windows/system”
d) Connect your phone by cable. A new device named “MT65xx Preloader” shall appear for about 3 seconds in a section “Unknown devices”.
e) Catch it with mouse and manually change the drivers to the ones located in “SP_Drivers_v1.5” folder of downloaded (unpacked) file.
f) After updating, turn off phone [the phone is already off], unplug and remove battery, reinsert battery and plug a phone. You should see a device “MediaTek Preloader USB VCOM (Android) (ComX)" in a “COM and LPT” section. If you see it, you are ready to go! The device display is also displayed for about 3seconds similar to the the previous one
- If you don’t see it, you did something wrong, most probably you were not fast enough in point e), retry from b)
4) S110_Pu_mod, CWM Recovery flashable, my modification of latest world ROM, shrinked, added More Locale and Xperia Launcher
Click to expand...
Click to collapse
After all, i can use this rom using cwm mod recovery, but i think there s a bug since i cannot back up application using setting menu. Is it right ?
solved, have to install backup n restore apk
abs0lut3z33r0 said:
This is entirely on my own experience on win7 x64
2) Preparation for memory flashing:
a) Download this package and upack it as a whole somewhere in your computer:
https://dl.dropbox.com/u/25344416/P7...te_utility.zip
alternative link: https://mega.co.nz/#!tFcFyAhJ!OInJjj...l9kDzv9y_3ukNg
b) Turn off your phone, unplug cable, remove battery. Insert the battery but DO NOT plug your cable or power on the phone.
c) Open your device manager in “windows/system”
d) Connect your phone by cable. A new device named “MT65xx Preloader” shall appear for about 3 seconds in a section “Unknown devices”.
e) Catch it with mouse and manually change the drivers to the ones located in “SP_Drivers_v1.5” folder of downloaded (unpacked) file.
f) After updating, turn off phone [the phone is already off], unplug and remove battery, reinsert battery and plug a phone. You should see a device “MediaTek Preloader USB VCOM (Android) (ComX)" in a “COM and LPT” section. If you see it, you are ready to go! The device display is also displayed for about 3seconds similar to the the previous one
- If you don’t see it, you did something wrong, most probably you were not fast enough in point e), retry from b)
Click to expand...
Click to collapse
yes, I am using windows 7 x64 too.. it did show up under COM and LPT but only for a few sec.. then it disappears.. this means that I can proceed?
EDIT: I use windowx xp too, and its the same. only appears for a few sec. Rooted!
Confirmation & Questions
Hi,
i can confirm the same behaviour. I also managed to load the new driver but when I connect the device again the "MediaTek Preloader USB VCOM (Android) (ComX)" in a “COM and LPT” section" only shows a second or so and then it dissapears again. Just like furredd describes it.Not sure if this is ok.
Note: I can see the driver using USBDeview.
Another thing: I tried twice to download the "4) S110_Pu_mod, CWM Recovery flashable, my modification of latest world ROM, shrinked, added More Locale and Xperia Launcher" from Mega but the download stopped at ~65% both times.
I use windowx xp prof.
Any ideas?
Edit: One more thing: I have a phone from Etotalk with their Rooted ROM. Does this mean I can not pull this update through or how am i supposed to understand it?
Thanks
INTRODUCTION (don't skip it if you want understand what you are reading)
Here we are, as promised.
A guide for beginners who hardly understand all the brief steps described in guides: root Galaxy S5 G-900V, unlock-bootloaders, etc. thanks for everyone who helped me with big patience (jrkruse, Bryanx86, XeCuTioN, youdoofus and all other guys) and who developed the scripts/guides. This guide is to help you keep focusing there
I'll try to be as brief as possible, remembering me when I entered in theis world without knowing this phone, and eager of flashing quickly the desidered ROM. I admit I've spent different days and a bounch bad words around figuring out all the obstacles that appeared time by time: you should know from the beginning that a small variation of the process described here may force you start from zero, loosing an amount of time, and that there are different phone models and also with different chipset, so you need carefully understand which phone you have before learning the process or losing time with wrong experiments, they will not work.
Anyway this guide will help many figuring out different aspects of phone, useful to everyone who is appraching flash the S5, it's a collection of important things I've read arond and experimented myself.
PHONE:
I have a S5 G900V with Toshiba chipset "CID11", and I tested all the following only on this phone, for questions/explanations read this article:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
I'm not going to give any support to other versions, but post me if I forgot something
DEFINITIONS:
PHONE: unfortunately there are a moltitude of Galaxy S5 released, they are dedicated to particular geographic areas and particular service operators, the 900V is created for Verizon brand and it has a native ROM with SIM locked. If you bought one with SIM unlocked (and you may even read under "about" it is a 900F for example! check the right one starting the download mode) and you want root it/upgrade you should consider that the first rom uploaded to begin the following process is Verizion original, and it contains SIM lock: you will not use your phone later till you flash the final desidered rom! Chances are also, if you have like I do a CID11 chipset, the SD card will stop be recognized, and that's a boring thing. EDIT: the SD card will work, it was my phone with the SD gold contacts spoiled, accurately I lift them up and sd worked always later.
CHIPSET: as I know there are two variants around, one with Chipset Sasmung "eMMC" and one with Toshiba "eMMC". Before you start you need to read the file /sys/block/mmcblk0/device/cid under the root path, the first two bytes will be 11 or 15, if you have 15 you're lucky and you may even remove the locked bootloader, if you have 11 there are not solutions yet for unlock, but you can install Marshmellow 6.0.1 (unrooted/without root). To check the file CID I suggest to install xplore from Lonelycatgames (you may find a copy around, google it and download apk, open the folder root, the path /sys/block/mmcblk0/device/ and at file cid push long and use the hex editor.
BOOTLOADER: The Verizon phones accept ROMs only containing their certificate (it's more complex but let's say it's like that), they are called stock ROM (ROMs coming from brend, original, untouched). To load other custom roms you need to unlock the Bootloader to avoid checks on certifications, and this is possible only if you have a CID 15 and only after rooting phone, and unlock bootloader. Then you will you are able to flash TWRP which is a nice console for upload any kind of rom.
Anyway, anyCID, there is a "workaround" called Safestrap that loads a TWRP console instead of the classic Android operative system (OS).. and it happens when you will reboot from its Safestrap applications: the console will load instead of Android on next reboot, and when you will reboot from Safestrap console, itself will restores Android the next boot. It's the only way to load ROMS when your CID is 11, but only very particular releases (read about down); and the way to unlock bootloader on CID15. We're waiting that someone in future will unlock also the CID11..
the "bootloader" or "download mode" can be opened only from phone switched off by pressing VolDwn+Home and when u sure u're pressing them correctly then press power keeping them pressed(!) until u see the bootloader, press then volume up.
"recovery console" or "recovery" is reached from phone switched off in the same way, but pressing Volup+Home (the power) until u see the recovery.
ROM: it's a file containing usually the kernel, the system with main applications (excluded google apps), some scripts (commands) to cancel datas before installing.
GOOGLE APPS: you have to flash them after flashed the rom (if the rom asking explicitly for them because made without (it means it doesn't contain inside any google apps that may be crucial for booting), or.. you have to flash them if you're targeting the final result (the last flash) and you want have apps updated in your "new flashed phone". It's not necessary when u're in process of root phone/unlocking.
FLASH A BOOT IMAGE/package: it's a file used to replace the bootloader, when it's needed, for example if you are upgrading from Lollipop to Marshmellow the bootloader can't stay in lollipop version, the versions should match, be sure to have both compatible already downloaded.
ROOT: it means gain the administrators privileges to edit system files on phone.
TWRP: it's a smart console to manage the phone with full control, allows to change the Android versions and many other things.
RECCOMENDATIONS:
1) have battery on phone around 100%, looks because it seems that at lower values make the phone react sometime unexpectly (power safe) during operations, that means you may loose after a lot time to figure out what problem occured/process skipped.
2) During the flashing, in download mode, the phone may not be charged from USB, and the PC power is much less powerful then the charger, you may see a quite impressive battery draining even when connected to PC, this is why is better to start near 100%.
3) During update, the USB up/downs may use lot of CPU of your PC due to driver recognition, keep then your Windows "clean" for the process, no apps in backgroud which use lot of RAM and CPU (for example browsers with many tabs opened), so the driver detection could be faster, avoid programming interruptions (for example installing apps in root.bat)
NOTICE: any time u'll use Odin you don't need to change its flags/settings (for example auto reboot), leave them as they are. If you uploaded something wrong/not certifed under download mode and the phone refuses that, you need to switch off the phone and restart in download mode again, it's not up to software Odin in your PC; you can leave it opened.
Odin will check the checksum of files that are loaded, so for big rom files you have to be patient and give it time to read all file.
When Odin is open and USB connected, you have to see the phone connected by COM, if it doesn't connect the phone may be bricked or you have to install the latest Samsung drivers (!! **you can't forget installing them if it's the first time using a Samsung device!!)
HOW IT WORKS:
useful to understand how is reached the goal here to prevent bricks, solve easier problems, find yourself an overcome. This root kit targets to install 3 applications on the phone, then use a temporary "bricked" kernel to allow edit system files and root the phone before it loads all Android, then restore the previous kernel working, and it ends by using applications installed before to install Safestrap into boot, to have a TWRP console even if the phone is locked.
As the Safestrap substitute the normal Android boot, if there is any problem on the process (=Safestrap will not boot when it's supposed to boot = you started it from its application) the phone may brick here, because when Safestrap stars it need to restore Android normal usage: if it will hapen the Android won't load again, the phone is bricked, read in that section how to solve it.
The first application, Kingoroot,it's made for allow the root permission into other two applications, it's a supervisor. If you use it gently and its installation succeded ok in the beginning of root.bat it will be enough for do all the job (even if the main Guide author suggest to buy SuperSUme).
Busybox it's a software that allows Safestrap to install, whothout it Safestrap won't work.
Safestrap it's a simple application, that if used in right way (I failed lot of times, but I always recovered my phone) permits to have a powerful console on next reboot.
IMPORTANT:
Whne in process, wait always that the USB drivers finishing detecting phone and become "stable" (CPU and hard disk aren't working, keep check them to be sure, as well the icon of the phone should appear in Windows resouces). You may need to start from zero if u miss this, a really stupid reason to lose time.
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
PROCEDURE:
1) Open OK3_ROOT_V5.exe in one folder, if you use windows with particular language and not latin chars avoid to extract it on desktop, prefer a path like C:\galaxy for example.
2) Switch off phone, remove SIM card and SD, switch on in recovery mode and wipe data system and cache, then boot to bootloader
2) open Odin, open under AP G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 and wait until it finished read file, connect phone USB, be sure phone is recognized, start flashing. Wait until phone boots, wait until it shows the beginning screen.
3) choose english, then wi fi button down, then skip the connetcion and everything else asked, insert any fake name.
4) When setup ends don't activate Wi fi, go to settings, about, press 8 times build number, get the development menu active, go into it and enable usb debug, wait for popup and allow your PC always, then disable the verify usb application installation in the same menu. The driver may set itself again after this, wait some seconds befor go over and be sure the phone is seen by Windows resources, when you see the icon of the phone on Windows file explorer and the CPU is low again it's time to run root.bat, not before! Go into OK3_ROOT folder, run root.bat, a black old DOS window will open (this is not Odin! Not confuse this window and what you read there with Odin messages, please!) and follow the steps you read in this new DOS window..
it will install apps, reboot in download mode and show you a new Odin window, select NK2_kernel.tar and flash it, now put your eyes over DOS window of root.bat, it should recognize your firmware and after some seconds display a full page of ########, if it doesn't something went wrong, you need to go to recovery console, wipe everything, and flash again the main big flash (=start from zero).
If succeed, and you will read it in the DOS window, as the last step, you have to disconnect USB, pull battery, switch phone on in download mode and flash VZW_BOK3_KERNEL_ONLY.tar with Odin
5) After reboot open KingRoot application already installed, Click The Up Arrows a couple of time until you get to Try It and yes click Try It, then on the main circle, go back with arrow and you will have confirm that is rooted. Close Kingroot, open busybox free app, allow the root access, click on install (even if it start scannig) and wait some seconds, when it say it completed close it. Open Safestrap, allow root, click on install, the app will quit itself, open it again and click on install, it will quit again. Now reboot phone by the power key, hen rebooted open again Safestrap and now you'll be finally ready to click on the button "Reboot to recovery". Before doing it be ready to organize the next step, like files for unlocking bootloader or flashing a locked phone to 6.0.1.
END rooting phone procedure.
BRICK/RECOVERY: if it happens during root, before you upload any other ROM, there may be three ways to solve that:
Pull the battery out (it's almost safe) and:
1) Light: go under download mode and flash VZW_BOK3_KERNEL_ONLY.tar, see if the phones later boot up normally.
Chances are, with "dirty" chache data that lead the phone to brick, you can't start the root.bat procedure again succesfully (use root2.bat to avoid the install of the three applications that supposed already installed). Then you may try to:
2) medium: go under recovery console, wipe data and cache, boot fom there to download mode and flash again VZW_BOK3_KERNEL_ONLY.tar.
Or, if still not successful:
3) Strong: go under recovery console, wipe data and cache, boot fom there to download mode and flash flash full G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 (that means start from zero)
SAFESTRAP WORLD:
WARNING: you should follow at the letter the above process above, any difference may result in a fail of Safestrap recovery to open and phone bricked at samsung logo (+custom). If so don't worry, you have just to start the download mode and flash VZW_BPB1_KERNEL_ONLY.tar.md5 again to see the phone working. But chances you probably now have to repeat all the procedure from zero because your phone is "dirty" and Safestrap won't work more, proceed to what I called "strong" reflashing in brick section.
NOTICE: when you reboot to Safestrap, after Samsung logo, you need to wait 5-10 seconds to see Safestrap.
FLASH FIRE METHOD:
You may prefer to use FF (Flash Fire) to flash your room, it is a app (apk) that needs t be installed on phone when the phone works in normal mode, it allows you to create a list of different "orders" to execute exactly one after the other after you give it the final "ok". The app reboot the phone and starting itself to flash. It may be faster then Safestrap, but when I tried once it didn't work for me, it flashed partially and rebooted before it finished, I had a soft brick and I should restart from zero. Probably it was me pretending to flash something wrong, there is only one way to upload 6.0.1 on a CID11 phone and I did only once with Safestrap.
For dealing with FF you need the phone rooted, after you followed the process above you don't need to install Busybox, neither Safestrap, but you need to find and install SuperSUme.apk, which is another "root manager" program as Kingoroot is, but FF doesn't work with Kingoroot.
After loading kingoroot copy the Flashfire apk and SuperSUme in your phone, install both of them, start first SuperSUme, allow the root, and let it remove Kingoroot in its procedure, when it finished launch FF and let him the root as well.
You need to find these two apk, google them, since SUperSUme is available only paying you should know what you are doing. I used these versons and they worked: supersume-6.0.apk, flashfire-0-50-android-apk-download (notice there is 0.52, but I tested 0.50)
PS: if you feel this useful, please thank me pressing the button
For uploading 6.0.1 to my locked phone I folowed this guide:
http://forum.xda-developers.com/ver...t/rd-unlocking-galaxys-s5-bootloader-t3337909
I would just add that having the SD card "not recognized" I simply copied files of ROM and GAPPS into the phone folder accessed by Windows resources. And when I reboot to Safestrap I flashed as last step the GAPPS, nothing more to add.
When you wipe Data you actually don't delete the /sdcard folder, so the ROM files are safe there.
if you accidentally delete files under safestrap you can upload them by adb, but it will be really slow (around 500KB/s), here is the command: adb push /path/to/local/filename.zip /sdcard/filename.zip
You may evaluate to flash also this before GAPPS:
Tethering_Fix_Knox_Removal_Slight_Debloat_V2.zip to remove Knox and useless apps from this ROM
If you need to put your default system language (the ROM is in english) download from google MoreLocale 2, open a DOS windows with the path to the folder of root.bat, activate the developer menu (point N°4 of post above), connect the USB, and type
pm grant jp.co.c_lis.ccl.morelocale android.permission.CHANGE_CONFIGURATION
Do you know any details about the new pf4 modem?
no, Im not that expert, here is just a guide to help people into the process..
thank you for the great guide. I was able to root my phone with the clear instruction.
However, I am running into one trouble.
When my phone is setting up the language and etc, it requires me to insert sim or wifi. I can't skip that step without doing one or the other. When I do turn on the wifi, the phone then upgrades itself to android 5.0 but the root is still there. I am using T-mobile sim card.
Is there a way to get around the check up? I made sure to follow all the steps correctly too.
if u're talking about the first beginning steps, after the first big ROM loaded, yes you can skip. Select wi fi button, but after skip all the rest. I've never had to connect to internet or inserted a sim card for the process.
I connected/inserted sim only after the flash to desidered rom
thewebsiteisdown said:
Do you know any details about the new pf4 modem?
Click to expand...
Click to collapse
What kind of details did you want to know? Mine works fine.
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Bryanx86 said:
Very informative read, and also put in plain english for people that dont understand the usual processes for root, in layman's terms. But you're forgetting one thing available for locked bl that i found very useful before i unlocked mine, and that is flashfire. I was able to flash roms which could or would not flash through safestrap, through flashfire. Other than that, good job writing this
Click to expand...
Click to collapse
I added the FF guide
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
nachoalt said:
Hey! Thanks for this great guide! Could you help me understand how the check the file CID if my phone is still unrooted? Is it possible to do it?
Click to expand...
Click to collapse
you didn't read well the first post. Read it back.
Barabba11 said:
INTRODUCTION (don't skip it if you want understand what you are reading)
FILES YOU NEED:
G900VVRU2BPB1_G900VVZW2BPB1_G900VVRU2BPB1_HOME.tar.md5 as the main old rom, that works as starting point.
OK3_ROOT_V5.exe: set of tools and scripts for rooting.
Find them all in the first post here:
http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Seems like the file name for OK3_ROOT_V5.exe changed. They call it GS5_LOLLIROOT.tar.gz now (must unzip twice to get all the files) but I looks like what is needed is in this zipped file.
Might take the plunge tomorrow so wish me luck, and thanks again for the explanation!
By "run root.bat" in point 4 do you mean "3 - Root Process.bat"?
Thanks for clarifications
Barabba11,
Since you seems to have a genuine desire of helping people, (and because I want to have my phone rooted), I want to comment your instructions and also try to find what I did wrong, since my phone is locked in the black “Samsung Galaxy S5” screen when trying to accomplish step 4 (no worries, I have been there before…).
Here I go…
FILES YOU NEED
Samsung Drivers: No comments here, straight forward thing to accomplish.
From the original post Here, under “Installing PB1”:
1. Download G900VVRU2BPB1_G900VVZW2BPB1_VZW.zip and unzip it
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
From the same previously mentioned post, now under “Rooting Instructions”:
1. Download this zip GS5_LOLLIROOT_BLACKCAT.7z
Click to expand...
Click to collapse
This is what you get today (161108) if you download and unzip that file:
Then, under “crc” folder you will find:
And finally, “System” folder is empty.
At this stage my series of comments:
1. I don’t see anything called OK3_ROOT_V5.exe mentioned in step 4 of your procedure. I assume you’re referring to the zipped file GS5_LOLLIROOT_BLACKCAT.7z but since almost every suggestion here indicates to read thoroughly, I don’t want to miss any detail. Can you please confirm if what you call OK3_ROOT folder is the unzipped GS5_LOLLIROOT_BLACKCAT.7z?
2. I don’t see anything called root.bat in the unzipped folders above, mentioned in the same step 4. Can you confirm which one of the .bat files are you referring to? Is it 1 - Install APK's.bat, 2 - Flash NK2.bat, 3 - Root Process.bat or 4 - Flash PB1.bat?
Since my phone got stuck in the black screen when reaching this point and I had to get back to square 1, I’ll wait for comments.
Warmest regards, it is really appreciated what you do here, it is just my humble opinion that detailed instructions in plain English, with proper file names, punctuation etc, would save this world a lot of time and frustration, leaving you developers more time to deal with the important stuff, I’ll be happy to help rewriting or reviewing anything in this regard.
PD: Not sure if the images are going to appear, I don't see them in the preview. If that's the case, you can check here
This thread is out of date since the rooting method has entirely been changed
Can you please indicate where can I find the updated method? Rgds
I'm sorry for the inconvenience, since they changed the main files I'm disoriented too. If they removed the bat files it means everything is different now, and honestly I'm hearing now about that..
Would know too why they changed the process, it was working, complicated but working, and I still have my phone at unrooted Android 6 waiting for a major update, like root or Android7.. I don't have enough time to experiment something that may appear useless for me later.
Anyway reading the instructions may warn you about different aspects to consider.. and reduce the waste of time if some conditions happened.
Kindly write in this thread they way you proceed and I'll have care to edit the first post reminding it. Thank you
Great thread, need some help still
How do I check my chipset when I don't have root access? I downloaded xplore but I need root access to check the root folder.
go into the xplore settings and change the root inside, I've no-rooted phone and I can see it. In the beginning, it's just a way for them to push you install rooting apps
If I root my S5 900V using this method can I then reflash it with 4.4.2?
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!
Hey Guys,
Before you dive in, irrespective of your reading speed read this carefully and slowly for better understanding but if you cannot focus and read it slowly then you better give up music for a few weeks.
About the Device
Before you jump in and get your hands dirty.. you should know that what you will be installing is Generic System Image, It is not specifically made for your device so if you are going to install some other GSI other than this, you might face some issues.
If you are a beginner, you should Go Through Project Treble, just for the sake of knowledge.
Also Galaxy A51 has A/B partition and Supports Project Treble though remember that Treble Devices are not same as A/B devices and Vice Versa.
Things You’ll Need
A Computer (not an iPad)
Internet [requirement around 6 gigs (4.8 gigs optional, for downloading stock Firmware, Highly Recommended)]
Samsung Galaxy A51 (will not work on A50)
Patience and a madcap attitude.
Resources
Download Odin from the link given below and extract it in a folder.
https://odindownload.com/download/Odin3_v3.13.3.zip
Adb and Fastboot Drivers
https://gsmusbdrivers.com/download/adb-fastboot-drivers/#
Samsung Drivers
https://developer.samsung.com/mobile/file/68b2dc40-3833-4a8b-b58e-32f7aca25c00
Havoc OS GSI
Havoc-OS - Browse /arm64-ab at SourceForge.net
Don’t forget to check that there is “arm64” and “ab” written on the name of the file
Other option is with Gapps (it means the rom will come with Google Play services built in
otherwise it is Vanilla Android.
GSI Flasher
(It is used for converting your img file into flashable Zip)
https://drive.google.com/file/d/1J8OlI2CCXpvAJ5FhFlR2b_y58eHQERGs/view?usp=sharing
Extract it you’ll find three folders gsi, META-INF, scripts, keep all of them inside the GSI
Flasher extracted folder.
Twerp Recovery
twrp-a51-3.5.0_10-1_ianmacd.tar | by androidhowto for Utilities (androidfilehost.com)
Do not use any other in this case you might get mounting errors.
Encryption Disabler
Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip | by androidhowto for Utilities (androidfilehost.com)
Its Show time
1. Go to settings and go to about phone, tap build number 7 times and a dialog will appear, you are now a developer.
2. Go to additional setting or search developer options in the settings search bar
3. Once in the developer settings find OEM unlock and turn in on, scroll down and also turn on USB debugging, your phone will ask the permission for accessing the data by your computer.
4. Turn off your device. Get a usb cable and connect it to your computer.
5. While phone is off first press Volume UP and Volume Down together, and then then insert the usb cable into the phone while holding the buttons wait for two seconds. a blue screen will come up telling you about consequences and life choices.
6. Long press the Volume Up Button and a new blue screen will show up asking you for unlocking the bootloader. Press Volume Up to confirm. You device will erase everything and reset itself ( Don’t forget to take backup of your Data).
7. After the setup screen appears skip everything in the setup and enable developers option and enable USB debugging in the developer options.
8. Turn off your device again and Repeat step 5.
9. Press Volume up for entering the download mode
10. Now in your computer, Install Odin and open Odin.exe you’ll find your device as comm: xx
Now click on the AP button and select the twerp you downloaded.
Press start and twerp will be installed in your device. Your device will reboot don’t let it boot to one ui, press all three buttons together and hold, as soon as the screen goes black release only the volume down button. Keep holding the Volume UP and power buttons for 3 seconds and then release, you find yourself in twerp. If you miss it repeat the process again but don’t let it boot to One Ui.
In twerp press wipe => format data =>type yes. Press home button and again go to wipe advanced select Data, Cache and Dalvik and swipe to clear.
Press home again. Go to reboot and select recovery, twerp wil reboot. Once it reboots transfer the encryption disabler to your phone and in twerp press install select the storage, sdcard or internal storage, where you have stored the file, select it and swipe to install.
Now in your computer extract the Havoc os image and rename it as “system.img”.
Extract the GSI flasher, copy system.img and paste it in the gsi folder of the GSI Flasher.
Select gsi, Meta-inf, scripts and compress them into a zip and transfer into the phone.
Now in twerp Press install, select the zip file and swipe to install. Also install Gapps or Magisk if you want (though normal magisk will have problem try install phh_magisk, discussed later).
Reboot and KABLAMO You have installed Havoc OS.
Bugs
A small random issue in Auto Brightness
If you root with magisk and install modules, after you reboot your phone will get into a bootloop. Use Phh_Magisk but I aint sure if it’ll work or not Your call madcap.
NONE OF THE FILES IN THIS TUTORIAL HAVE ANYTHING TO DO WITH ME. If SOMETIHING HAPPENS I AM NOT RESPONSIBLE. ONLY DO IT AT YOUR OWN RISK.
Troubleshooting.
If you find errors in twerp, such as unable to mount vendor or system_root, or data. Then you got to install the stock One Ui Back again, therefore it is highly recommended to keep with yourself the stock firmware. You will need It. And it is 4.78 gigs. You can download it from
Model : SM-A515F - Galaxy A51 — Samfrew.com
To reinstall the stock firmware first extract it and the open odin and repeat steps 8 and 9, once your device is detected in Odin press the respective buttons and select the respective files such as for BL button select the file With BL in the name. Do it for buttons, BL, AP(once you select the file it will take long for it load into odin so do not panic and let it load, it might become unresponsive but use patience and wait.)CP , CSC. Click on start and you’ll have ONE Ui back on your device.
To Lock the bootloader repeat steps 5 and 6.
If you still want more stability and Control You can install a different Kernel NDataX from (@Hendamanu) https://forum.xda-developers.com/m/hendramanu.11224917/
Thanks for your contribution