Related
[HOW-TO] The All-In-One Backup/Root/Flash Guide & Bootloader Support - [I747 & I747M]
{
"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"
}
This thread exists to give everyone that is just now getting around to taking advantage of their devices the opportunity to do it right the first time while also keeping all the necessary material in one common place. As always: Know what you're doing. Know what device model you have. Know you and your devices limits.
If followed correctly, this 5-step guide can be a very useful tool. These steps are listed in the order in which they should be completed. The intent is to seamlessly backup, root and flash, leaving as little room for error as possible. This process will erase and/or reset everything on your device. All steps are assuming you have backed up your contacts, texts, pictures, videos, etc. I do not take credit for any of this material or information. This is all the work of good people that I have simply brought together. Cheers!
**WARNING!** All information and attached links are for the I747 and I747M ONLY! No one here is responsible for anything that may happen to your device. Proceed at your own risk.
>>>>>>Before you begin, make sure your S3 has USB Debugging Mode switched on<<<<<<
STEP 1: Backing up your IMEI/EFS/NV
Part 1. Having a corrupt IMEI can be a real pain. It seems to happen randomly and having the radio go down on a cell phone really defeats the purpose of owning one. Thankfully it is not a problem that is overly common. Unfortunately, it does still happen. Since it is simplest to be on stock for this attached method, I have listed it as step number 1.
At the end of the "Instructions" section there is a video demonstration. Check it out first.
Part 2. Having a copy of your functioning EFS folder is also something every user should have. A great way to do this is to download an app like Root Browser or Root Explorer and copy the efs folder from your device to either your external micro SD card, your computer or both. This will allow you a much smoother transition back into a fully data-capable and functioning phone in the event your IMEI/EFS is ever corrupted.
STEP 2: Rooting your device
For those of you who want to get most out of your Galaxy S3, you will certainly want to root it. Rooting your I747 gives you lots of benefits like full control over your phone, ability to install custom ROMs, and much, much more...that's why you're here right now reading this. You want it all.
The attached link may be intimidating to you initially, so read over the page a few times to become familiar. Near the top of the page, the second paragraph links you to a video of the rooting process. Watch this to understand better what to do and what you should expect to see during these root procedures. After downloading Odin (the link is just below the video link), just follow the first 2 steps (1. Download the file to flash and 2. Unzip the file contents and flash the rooted firmware) and then return here to continue on to step 3.
**If you want to have root access only and are not interested in a custom recovery, you can stop here.**MrRobinson's debloating thread can be found here if you wish to remain
stock/rooted-only but cleaner, with less bloatware and without unused apps absorbing resources.
A custom recovery is required and TWRP is recommended
STEP 3: Installing a custom recovery
A recovery image is the system level software for your Android that lets you perform several maintenance and recovery tasks. The stock recovery image is quite limited in what it allows you to do and therefore, flashing a custom recovery image is required to gain full control of your device’s administration. A custom recovery image allows you to perform the following tasks:
- Wipe your phone’s data (Factory reset) and cache
- Make, restore and manage backups of your phone’s operating system and software
- Mount, unmount and format your phone’s internal as well as external storage partitions
- Install a custom ROM or application from a zip file to your phone
- Wipe Dalvik cache and battery statistics
- Make logs for error reporting and debugging
The 2 most common custom recoveries are listed here. Everyone has a preference but they both work well. Take your pick and download from the Play Store.
**ClockworkMod (CWM)** --- OR DOWNLOAD THE APK DIRECTLY HERE (Recommended)
1. Open Rom Manager and tap on Flash ClockworkMod Recovery option in the app.
2. You’ll be asked to select your device, select your device name.
3. As soon as you select the model, it should begin installing the recovery.
4. When it has done installing the recovery, you will get a message for the same on your screen.
*NOTE: I do not recommend Rom Manager as a tool to do anything but just install and update ClockworkMod Recovery Do not flash ROMs from Rom Manager.
**Team Win Recovery Project (TWRP)** --- OR DOWNLOAD THE APK DIRECTLY HERE (Recommended)
1. Once the download is complete launch Goo Manager.
2. On the top right of the screen there is the “options” menu.
3. Tap on options.
4. Then, click or choose the “Install OpenRecovery Script” option.
5. Select “yes” on the prompts that will follow. Now, the app will download and install TWRP Recovery on your S3
*NOTE: I do not recommend GooManager as a tool to do anything but just install and update TWRP Recovery Do not flash ROMs from Goo Manager.
STEP 4: Making a Backup (Nandroid)
Making a nandroid will allow you to try out new ROMs while still keeping a safe backup in the event you experience issues during or after the OS installation. Be sure your device is fully charged before proceeding onto the backup and flashing procedures.
1. Power off your device.
2. Press and hold Volume Up + Home + Power buttons at the same time.
3. Release the power button when the device vibrates and you see the blue script in the top left corner
4. You are now in custom recovery.
5. In CWM go to Backup and Restore and select Backup. In TWRP select Backup. Name and select the options you want. Swipe to backup.
6. After backup is finished, select reboot system now or stay in recovery to continue with this guide.
*NOTE: Be sure to save a copy of this backup to your computer and/or micro sd card. Having a recent backup saved to your computer and micro SD card can be useful if something happens to your phones internal memory.
STEP 5A: Wiping your device
When flashing any ROM, it is always important to follow the proper wipe procedures in order for everything to function properly. There are various levels of wiping based on what sort of transition you may be making. In this guide, I will list the procedures for a full wipe, presuming that you are coming from the stock firmware and changing your OS completely. This is all assuming you have made the appropriate backups. ALWAYS perform the appropriate wipe before flashing a new ROM or update!
1. If you are not already in recovery, boot in now (Vol Up + Home + Power. Release the power button at vibrate and when you see the blue script in the top left corner).
In CWM:
2. Select Wipe data/factory reset
3. Select Wipe Cache
4. Select Advanced and Wipe Dalvik Cache
5. Select Mounts and Storage and format /system
6. If you are transitioning from 4.1 to 4.2 or 4.2 to 4.1, you must also format /data. You will lose all personal data so back it up first.
In TWRP:
2. Select Wipe
3. Select Factory Reset and wipe
4. Select System and wipe
5. If you are transitioning from 4.1 to 4.2 or 4.2 to 4.1, you must also select Data and wipe. You will lose all personal data so back it up first.
STEP 5B: Flashing a custom ROM
First, read up on a couple ROMs you're interested in. Make sure they are for your model. Understand that the newest ROMs often still have some small bugs still to be worked out. Once you have decided on a ROM:
1. Download the ROM - If you are downloading a stock/TouchWiz-based ROM, Google Apps (gapps) will be included. If you are downloading an AOSP-based ROM, be sure to download the appropriate gapps as well.
2. From your PC, place the ROM/gapps on your internal or external SD card. Remember where they are.
3. Boot into custom recovery (Vol Up + Home + Power. Release the power button at vibrate and when you see the blue script in the top left corner).
4. Perform the wipe listed above if you have not already.
5. From the main recovery screen:
>>CWM - Choose the "install .zip from SD Card" or "install .zip from external SD card" option (depending on where you placed the files) then navigate to the ROM file, select it and confirm.
>>TWRP - Choose Install and locate the desired ROM on your internal or external SD.
6. If you need to flash gapps, repeat step 5 and select the gapps package.
7. Reboot system. It will take several minutes to load so be patient and don't worry. Once the phone is booted, let it sit for 5 minutes, reboot and enjoy!
>>>>>Fixes and Additional Resources<<<<<
Post #2 will, as it claims, contains further useful information and links that will hopefully restore your device and continue to make your device-modding travels safe, smooth and fun. Please do not disregard the initial purpose of this thread and all the useful steps and information listed above. Post #2 is for those who have encountered common issues and errors, and are comfortable and familiar with all the required procedures for successfully modifying their devices. Cheers!
Latest AOSP/CM/AOKP flash error - Updating Your Bootloader
For continued support and updates, read mrhaley30705's bootloader advisory first, then follow the Task's directions outlined in this thread. This is intended for those not on the necessary Jelly Bean bootloaders, allowing them to flash future [CM] builds.
Bootloops
Bootloops are mainly caused because system files are conflicting and interfering with each other. This instability causes crashes at the boot sequence.
To find the cause of a bootloop you have to think about what you did before the issue began. After flashing a new rom, stock firmware, kernel or restoring a system backup?
Method 1
1. Boot into recovery
2. Wipe Cache
3. Wipe Dalvik cache (custom recovery only)
4. Reboot your phone
If the problems still exists and you're sure it's not related to the ROM, then you need to wipe data as well:
Method 2
1. Boot into recovery
2. Wipe Data
3. Wipe Cache
4. Wipe Dalvik cache (custom recovery only)
5. Reboot your phone
Method 3 - This last method involves restoring your backup in order to correct the conflicting software by replacing it with a functioning platform
1. Boot into recovery
2. Wipe Data
3. Restore backup
4. Wipe Cache
5. Wipe Dalvik cache
6. Reboot your phone
Setting the wrong permissions or not adjusting permissions can also induce this error. Android is very dependent on the right permissions. If you adjust file permissions incorrectly you could find yourself in a bootloop. An easy fix is performing the "Fix permissions" option in recovery under Advanced. Be sure to mount the partitions before running the fix.
Status 7 error
When you receive a Status 7 error in CWM or TWRP, the most common reason for most users is that their recovery is not as up-to-date as the ROM requires it to be in order to install. There are a couple different ways to fix this, depending on each persons situation.
You've wiped everything on your device, removing your OS, and now you're receiving the error:
If you have a micro SD card, this fix is simple. You can download an up-to-date flashable CWM or TWRP recovery zip, place the file on your micro SD, flash the zip, go to Advanced and reboot recovery.
You've simply tried dirty flashing a ROM or ROM update and have only wiped data, cache and dalvik:
Use the above technique to update your recovery or boot back into your S3 to update. For CWM users, head to Rom Manager. If you use TWRP, hop into the Goo Manager app. Once you've applied the update, boot into recovery and flash the desired software.
Soft brick - Stuck at glowing Samsung logo
There are two types of bricks – the softbrick and hardbrick. The softbrick can be recovered if you can still get into download and recovery mode. Additionally, getting stuck at the Samsung logo is another one our most common issues seen. When you flash a stock ROM with Odin, your /data will be kept. This means your old dalvik cache is still being used for the new system files. If this is still possible, then boot into recovery and try these methods first:
Method A: Wipe
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik Cache
Method B: Wipe and Restore
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik Cache
4. In CWM: Select Mounts and Storage and format /system. In TWRP: Wipe System
5. Restore your backup
6. Wipe Data again
7. Wipe Cache
If neither of these methods has got your device back up and running, you will need to restore the phone with stock firmware via Odin. Make sure the battery is fully charged and follow these steps:
1. Download and run Odin on your PC
2. Download the stock firmware for your device
3. Boot into download mode and, when prompted with the warning, press Volume Up to continue. To access download mode, power down the phone and hold down the Volume Down + Home + Power buttons
4. Connect the phone to PC via USB. Make sure you can see the highlight COM:ID box once the device is detected
5. In the tickable option boxes, ensure ‘RE-Partition’ is unticked. Only ‘Auto Reboot’ and ‘F. Reset Time’ need to be checked off
6. Now click the PDA button and select the tar you downloaded
7. Click on “Start” to flash the stock firmware
8. Wait until the flashing successfully finishes and you see a word ‘PASS’
9. Unplug your device, pull the battery, replace and immediately press Volume Up + Home + Power to enter stock recovery. Release the power button when the device vibrates and you see the blue script in the top left corner
10. Wipe data, cache and wipe Dalvik cache (under advanced). Reboot
Low internal memory / Multiple "0" folders
This is a common issue when flashing a 4.2 ROM. Android 4.2 has multi-user support. The 0 folder is user 1. The best way to avoid this multiple folder problem is to always flash from the latest CWM or TWRP recoveries, whichever you prefer. The duplicate folders issue can be solved via the install method listed under the Reverting to 4.1 ROMs? section or as follows, if you've already flashed your 4.2 ROM:
Staying on 4.2+ ROMs?
1. Copy your sdcard data to /data/media/0 and then delete the /0/0 folders
2. When prompted, choose merge
3. Verify there is nothing in the other 0 folder, then you can delete it
4. Repeat with other /0 folders, if applicable
5. Reboot
Reverting to 4.1 ROMs?
1. In the event you are planning on returning to a 4.1.X ROM, I encourage users to make a backup and save/backup everything on the device that they wish to have on their device again after flashing. Save/move everything either to a micro SD card or to your computer.
2.*When you are in recovery and preparing to flash, wipe: data/factory reset, cache, dalvik, format /system, format /data & /media
This will eliminate the OS and all traces of the previous 4.2 data and folders, allowing you to boot into your device with the full amount of available memory and no duplicate "0" folders.
Simple and Fast Wiping Mods
In this thread by Upndwn4par, there are three recovery-flashable wiping tools that you can use while working on your device. They can be incredibly useful tools that save some power button & volume rocker mashing. With the snappy flashing of these zips, you can easily perform a Cache & Dalvik Cache wipe, a Full Wipe or a Full Wipe Factory Reset. These are handy and will ensure you perform the necessary wipe to best optimize your ROM, mods and troubleshooting. Per-wipe details in the link.
Unroot your device
Need to get your S3 ready to return to the manufacturer? Follow this link and you'll be squared away in under 10 minutes. You'll need:
- Triangle Away installed
- The official stock firmware for your device
- Odin installed on your PC
- Your Samsung USB cable, if possible
- Samsung drivers installed on PC
Build your own Must Have toolkit
In the world of rooted phones running custom ROMs, you will find the simple micro SD card to be the best $10 you've ever spent. I would strongly encourage everyone to purchase one of these and build themselves their very own emergency-response toolkit, stored right on the device. To do this, grab yourself a micro SD card and place these files on it:
- Your stock Nandroid backup
- Your most recent or preferred Nandroid running your current custom ROM
- The ROM/gapps you're currently running
- A current flashable CWM 6.0.3.0 / 6.0.3.1 or TWRP 2.4.4.0 / 2.5.0.0 custom recovery
- A flashable stock ROM
First.
Updated OP.
Please share. Lots of posts from beginners dealing with issues related to wrong root methods, outdated recoveries or incorrectly flashed files. Let's help make it a smooth transition by getting them the right procedures. Cheers!
cant find a recovery for SGH-i747M, any tip?
or can i use the same as the att samsung galaxy s3 SGH-i747?
edit
susesfully installed Cyanogenmod 10.1 on my d2ub (Claro Puerto Rico Samsung Galaxy s3 LTE SGH-i747M).
i instaled the last Clockworkmod recovery from the d2att
and flashed the cyanogenmod d2att rom, i just have to manually add my carrier APN settings.
working good so far, will come back 2 morrow and report more.
Very Nice and neatly done. I'm definitely bookmarking this page and help out our future xda members!
Thanks!
Beer,
You should direct people to these as well:
This has all the stock apps for the at&t phone that can be flashed in the aroma installer or pushed to /system/app or data
http://forum.xda-developers.com/showthread.php?t=2185221
This one is makes wiping easier so you know a step wasn't skipped and can be flashed in a custom recovery everytime you flash a ROM. I never get a bad flash using this:
http://forum.xda-developers.com/showthread.php?t=2097365
And also list the most invaluable asset: An awesome file explorer like root explorer or other tools they should also have when flashing
thanks, hednik! will make some mods today to the thread. cheers!
I really like the way this thread is shaping up. :good:
Have you thought about adding something like a rescue / emergency tips section?
Something like:
To get out of boot loops do X.
If you are stuck on the splash screen do Y.
Always store a flashable recovery, stock ROM, and stock backup on your external sd card.
Etc, etc.
upndwn4par said:
I really like the way this thread is shaping up. :good:
Have you thought about adding something like a rescue / emergency tips section?
Something like:
To get out of boot loops do X.
If you are stuck on the splash screen do Y.
Always store a flashable recovery, stock ROM, and stock backup on your external sd card.
Etc, etc.
Click to expand...
Click to collapse
This would be good because bootloops and bricks normally aren't that bad at all on our devices. People think bricked their device and panic when its not hard to recover form that.
I've flashed hundreds of times in the past years and never had a soft brick or bootloop. *Looks for the closest piece of solid oak*
Agreed. Good stuff. I'll get started on an edit and have it up by this weekend. Thanks guys
Updated Post #2. Added lots of new material. Thanks to Hednik and Upndwn4par for the suggestions and again, many thanks to all those who have put in the effort behind all the information on this thread. I simply consolidate and share. Cheers!
Can we get this in the sticky roll up thread
Re: [HOW-TO] The All-In-One Backup/Root/Flash Guide - [I747 & I747M]
Awesome man thanks s bunch!:thumbup::thumbup:
"Say WHAT one more time!"
Would it be worth adding something about moving between 4.1.X and 4.2.x roms? Regarding the changes to internal sd. I know as a rom flashing fiend I flip flop between the two pretty often.
Great post by the way, will be very helpful for new users!!
majorassface said:
Would it be worth adding something about moving between 4.1.X and 4.2.x roms? Regarding the changes to internal sd. I know as a rom flashing fiend I flip flop between the two pretty often.
Great post by the way, will be very helpful for new users!!
Click to expand...
Click to collapse
PM a Mod to see if you can get it added to the sticky thread. It's going to get lost otherwise as people wont search if it's not on the front page
majorassface said:
Would it be worth adding something about moving between 4.1.X and 4.2.x roms? Regarding the changes to internal sd. I know as a rom flashing fiend I flip flop between the two pretty often.
Great post by the way, will be very helpful for new users!!
Click to expand...
Click to collapse
Added. Thanks
hednik said:
PM a Mod to see if you can get it added to the sticky thread. It's going to get lost otherwise as people wont search if it's not on the front page
Click to expand...
Click to collapse
Thanks. Will do. Stay slick, old man
Added to the Roll-up sticky.
- Cleaned up the thread a little.
- Updated several links including grabbing y'all the latest CWM and TWRP flashable recovery zips. Thanks to clickclickpc and roughneckboren for lookin' out. :good:
majorassface said:
Would it be worth adding something about moving between 4.1.X and 4.2.x roms? Regarding the changes to internal sd. I know as a rom flashing fiend I flip flop between the two pretty often.
Great post by the way, will be very helpful for new users!!
Click to expand...
Click to collapse
made some tweaks on the fixes/resources section including the 4.1 - 4.2 changes and transitions. cheers
Hello to all genius folks of xda.
So, I bricked my Asus Zenfone 2 Laser (Ze550kl).
Actually, the problem began with error mounting /asdf partition. The phone's home and back buttons were not working, notifications drawer and quick buttons are not there when the notification bar is pulled down.
So, I decided to format it and downgrade to #1531 and then upgrade to #18xx. But when I downgraded, I needed to enable USB debugging. After enabling developer options from build version, the screen says, Developer options not available for this user. I thought I need to create a new user but there was no option in settings to create a new user (I have checked many times and under each sub-option).
Then I decided to format it. In Recovery options, I chose wipe data/factory reset. It wiped along with some erros "unable to mount /asdf (Invalid arguments)". Then I wiped cache partition. When I rebooted it, it stuck in ASUS logo.
Now I don't know how to enable USB debugging as shown in the most tutorials and under cmd "adb devices" there is an empty list of attached devices when in recovery mode. However, when I do "apply update from adb", it is showing my device. My OS in Windows 10 and I have heard that ASUS drivers are not for Windows 10. Help, I am stuck from every side.
I am trying to follow this tutorial to firstly remove the /asdf error. ( https://devs-lab.com/e-unable-to-mount-asdf-recovery-error-solved.html ) But it is for Asus Zenfone 2.
Please help me what and where I am doing wrong. If I can get USB debugging enable somehow, I would be able to follow any tutorial. Please share a guide that can resolve this. I have already wasted 4 days into it but I know guys here are Android gods and they can help me for sure.
If you need more info, here I am to reply as fast as possible.
Thanks a ton in advance.
Solved. It's Working now.
Hello, Everyone.
The power of xda is amazing.
Just 30 minutes before I started this new thread to fix my Asus Zenfone 2 Laser. Now, I fixed it. Though credit goes to the link mentioned above (which is actually for all Zenfone 2 phones) It worked.
I thank the site and xda for helping me out.
I will post the guide after few minutes so that anyone having the same problem can fix their device.
Guide to fix Zenfone 2 Laser
So here is the detailed guide for the people who are in similar to mine problem. Please note: I am not at all expert at this stuff. As I have previous experience, so I knew most of the technical stuff.
Device: ASUS Zenfone 2 Laser
Model Number: ZE550KL
System OS: Windows 10 (Website says drivers not available)
Problem
1. The phone got hard bricked. Stuck in ASUS logo.
2. Not able to wipe data/factory reset and wipe cache partition due to "mount /asdf error".
3. Not able to connect through ADB as the option to enable USB debugging wasn't available.
Symptoms
1. Home and Recent Apps Switcher soft buttons were not working.
2. Developer options say "Developer options not available for this user".
3. No ringtone and notification sounds, in fact, no notifications. at all.
4. No quick action buttons (Wifi and all other buttons) on notification drawer.
5. Apps not downloading from Play Store.
Error: "Error mounting /asdf partition", "Error in /asdf/recovery .... " kinds of error.
Time Taken: 15 Minutes
Downloadable files:
1. UL-Z00L-WW-1.17.40.1531-user.zip
2. All other files
Pre-install set-up:
1. Extract the zip files in "all other files" folder.
2. Paste the stockboot.img file in the extracted "ADB fastboot tool" folder. [Important]
Guide to Fix it.
1. Install ADB-setup executable file. A DOS window will open and opt for all yes. Self-explanatory as you install ADB and fastboot.
2. Go in Asus drivers folder and install (by right click option) on "android_winusb.inf" file located in Win_7_8_8.1 folder
3. Copy the ROM file ( UL-Z00L-WW-1.17.40.1531-user.zip ) in the root of your sdcard.
4. Enter fastboot mode on your device by pressing "UP volume key" and "Power button" until it vibrates. The fastboot text will be there on top-left of your Boot-up screen.
5. Now connect the device to the system.
6. While pressing Shift, right click anywhere ( Make sure you are in the ADB FastBoot Tool folder ) and select open Command Prompt here.
7. Type in the following commands.
> "fastboot flash boot stockboot.img" and press enter. If it says something ok..ok and all, then you are good to go. If not, then you should start a new thread here in XDA. Next, type this,
> "fastboot reboot" and then your device will reboot in recovery mode.
8. In recovery mode, select "Wipe data/factory reset" and "Wipe cache partition". Everything should execute without any problem now.
9. Now go to apply update from sd card and select the ROM file ( UL-Z00L-WW-1.17.40.1531-user.zip ) and select yes to install.
10. Once it is installed, your phone will work like it used to be. Install all your apps back and enjoy.
Please note, I am not expert in writing guides. If you need help please ask me.
Hope it fixes your device. If it does, leave a comment, I will be happy if it works.
Good Luck!
Note all devs: I am no expert. If I have done something somewhere wrong, please correct me. The exact method above worked for me though.
I can download firmware but i can't download other files because it's has got paswoord.
What is password of other files at mega?
I got one problem on every rom
Whenever i reboot my phone it takes too much time in booting up
I think every time i reboot cache wiped automatically
Any solution for this sorry for my bad english
best thing to do is just start again - the following steps will erase all user data on internal storage - backup photos documents or anything else you need first
put your phone into fastboot and connect to pc via usb
open a terminal/cmd window where you have your fastboot files
type
Code:
fastboot erase userdata
now go into twrp recovery
goto wipe
advanced wipe
format the following paritions
system
data
cache
art/delvik cache
goto home screen of twrp
mounts
mount the partitions you just wiped
goto home screen of twrp
install
select rom zip
dont restart
goto home screen of twrp
select nano gapps downloaded from http://opengapps.org/
you need arm 7.1 nano
optional
if using lineageos or rom based on it
goto home screen of twrp
install
select suaddon zip (see lineageos instructions for link or get from lineageos website)
Final step
after flashing of the last zip
wipe delvik/art cache from the option after flashing zip
restart
if you have flashed any other zips or modded in any other way it may have an impact on startup
first boot can take up to 10mins
normal boots after take up to around 2mins from power on
TheFixItMan said:
best thing to do is just start again - the following steps will erase all user data on internal storage - backup photos documents or anything else you need first
put your phone into fastboot and connect to pc via usb
open a terminal/cmd window where you have your fastboot files
type
now go into twrp recovery
goto wipe
advanced wipe
format the following paritions
system
data
cache
art/delvik cache
goto home screen of twrp
mounts
mount the partitions you just wiped
goto home screen of twrp
install
select rom zip
dont restart
goto home screen of twrp
select nano gapps downloaded from http://opengapps.org/
you need arm 7.1 nano
optional
if using lineageos or rom based on it
goto home screen of twrp
install
select suaddon zip (see lineageos instructions for link or get from lineageos website)
Final step
after flashing of the last zip
wipe delvik/art cache from the option after flashing zip
restart
if you have flashed any other zips or modded in any other way it may have an impact on startup
first boot can take up to 10mins
normal boots after take up to around 2mins from power on
Click to expand...
Click to collapse
Same process i tries but the problem is it takes too much time
And i didn't flash any other zip currently i am on viper os
Normal boot also takes around 10 mins
jatintomar said:
Same process i tries but the problem is it takes too much time
And i didn't flash any other zip currently i am on viper os
Normal boot also takes around 10 mins
Click to expand...
Click to collapse
Not used that rom
I just use lineageos
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
-> Boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously, including everything in storage, photos, documents, everything).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push xiaomi.eu_multi_MIMix3_V10.0.12.0.PEECNFH_v10-9.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Note for AMD Ryzen machines: There appears to be a USB2.0 bug associated with Ryzen CPUs which prevent the fastboot flash from working. If the flashing process starts then fails, try a different machine.
ROM File and TWRP not listed
invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
Yes they are, you need to look again
Mackay53 said:
Yes they are, you need to look again
Click to expand...
Click to collapse
Thanks, found them.
fahdsuleman said:
---
Hi, thanks for the guide, the ROM files and TWRP are not available on the link
Click to expand...
Click to collapse
They're right below the ROM table.
invisiblewave said:
Thought I'd post my experiences in case it helps anyone else out. Following this procedure will completely wipe your phone. As usual, I take no responsibility for bricks, headaches, wasted hours at the keyboard, etc. Do your research first. Please feel free to post corrections, improvements, etc, I will edit and add them. This post assumes your bootloader is already unlocked. If you're not unlocked, make sure you read all the various articles and warnings about Xiaomi's downgrade/relock protection which can result in a brick if you flash an older build with a locked bootloader. Unlocked is the safest way to go.
I installed the Xiaomi.eu rom, but this should work for any other rom in a flashable zip, downloads for the rom, TWRP and Magisk can be found here.
Install ADB and the relevant drivers. If you're on Linux or MAC, the easiest way I know of to do this is to use Corbin's excellent tool by running a single curl command.
Download TWRP, the ROM and Magisk (optional) into the same desktop folder as your ADB installation.
Boot into Fastboot (Vol- and Power).
fastboot flash recovery twrp.img
fastboot boot twrp.img
-> At this point, my phone would reboot to MIUI recovery. To solve this, as soon as the screen goes black after the previous command, boot to TWRP by holding Vol+ and Power.
Once you've booted to TWRP, change the language to English by touching the third button down in the second column (right above the button in the lower right), then touch the globe icon at on the right in the blue bar, then select English and hit the button in the lower right corner.
From the Wipe menu in TWRP, press Format Data, this will remove encryption (and wipe your phone, obviously).
While there, swipe to do a Factory Reset (which will also wipe your phone).
-> At this point, I repeated the recovery reboot procedure to be sure that TWRP would still boot, Vol+ and Power, or reboot recovery from TWRP menu. Not sure this is strictly necessary.
(For some reason, I couldn't get MTP to work in TWRP, it wouldn't copy files from the desktop. If you can get MTP to work you can simply drag and drop the rom and Magisk, otherwise you can do what I did and use ADB instead.)
From the desktop, push the rom you want to use, and Magisk, to the phone, this syntax (Linux) assumes your rom is in the adb folder, otherwise you need to provide the path:
adb push miui_MIMIX3Global_V10.0.11.0.PEEMIFH_9761b07e78_9.0.zip /sdcard/Download
adb push Magisk-v17.1.zip /sdcard/Download
From TWRP, install the rom followed by Magisk from /sdcard/Download on the phone.
Reboot System.
Drink beer, preferably something hoppy and top fermented.
Click to expand...
Click to collapse
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?
Lumpka21 said:
I'm doing all the things that you've said but it still boots me to miui receovery, what should i do ?
Click to expand...
Click to collapse
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).
invisiblewave said:
Boot to TWRP using the buttons instead of the fastboot boot twrp.img command. I had the same problem. Also, make sure you're not installing the stock rom, that appears to also overwrite TWRP (that's what it looked like to me, I didn't bother to confirm for sure).
Click to expand...
Click to collapse
You can use stock ROM and twrp. Twrp is replaced if you boot the OS
Mackay53 said:
You can use stock ROM and twrp. Twrp is replaced if you boot the OS
Click to expand...
Click to collapse
Ok, so once you've flashed TWRP, there are two recoveries on the device and booting into the stock OS changes the bootloader to boot to the MIUI recovery?
Hello, i found this very useful. thank you
Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)
Alexdruso said:
Hi, I followed your instructions and I flashed TWRP, but I just can't reach it. When I give the ADB command to boot I immediately try to start in TWRP recovery mode by pressing vol up+power, but at the beginning the phone doesn't do anything, then it boots to Android and I can only access MIUI recovery. Have you worked out another way or am I wrong in doing smth?
(Also pardon my ignorance, but I turned USB debugging on, am I right?)
Click to expand...
Click to collapse
You don't need ADB for flashing twrp so having usb debugging on is irrelevant.
Flash twrp In fastboot and once it's done and without giving any more commands just hold power and volume up. Eventually it will boot into twrp.
Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG
PWn3R said:
Did anyone wipe system before flashing the global zip over the Chinese rom? I didn't wipe data (which is not smart, I know this) and I have noticed some of the system apps have duplicates with different versions. I also have a few weird behaviors with Google Play store and some other items now. Debating installing TWRP, wiping both, and reflashing.
Nevermind, I can't do that. I don't have another activation for Google Play Music, and I can't set the device ID without root, and I can't root the global version so I can't wipe data. GG
Click to expand...
Click to collapse
You never ever need to wipe the System so it won't be that, wipe would be recommended if you can do it
Which version of twrp should I use?
Herrick1209 said:
Which version of twrp should I use?
Click to expand...
Click to collapse
The only one there is for the MM3.
invisiblewave said:
The only one there is for the MM3.
Click to expand...
Click to collapse
I couldn't find it on the twrp website??
Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
You can't find one for the Mix 2s there either.
You can find one for the Mix1 there, but it is non- functional.
. . .
DYODD
Herrick1209 said:
I couldn't find it on the twrp website??
Click to expand...
Click to collapse
That's why I posted the link in the OP.
Thanks, does this apply to the Xiaomi MI Mix 3 Forbidden City Edition?
IDEA AND NOTICE
So, according to my researches over the Internet, there are plenty of users owning this device looking for this and here I share what I did to root it. Don't worry about the simplicity. You'll just need a little bit command knowledge.
REQUIREMENTS
/ Vestel Venüs V5 (That's our device! - Please turn on USB Debugging in Developer Settings for everything to work well.)
/ A working Internet connection (You don't want to have a broken root, do you?)
/ Stock boot.img (I extracted+uploaded myself)
/ Magisk Manager (To patch the stock boot.img - Couldn't put a link to it as XDA appears to have censorship against it.)
/ A computer with ADB and Fastboot installed (To flash our boot.img - For Windows, I recommend using 15-second ADB installer to install if you don't have it.)
/ A USB Type-C cable (To transfer our patched image to the computer)
WARNINGS
IMPORTANT NOTE: Please follow the steps as-is. A misstep has the ability to make your phone unbootable without reflashing the ROM.
ATTENTION: BEFORE DOING ANYTHING, TAKE A FULL BACKUP OF YOUR DATA AS WE'RE GOING TO UNLOCK THE BOOTLOADER, WHICH WILL RESULT IN FACTORY RESET!
And as everyone says, I'm not responsible about the possibilities on these type of stuff as it worked on me plus I did a thing that nobody did: Mentioned possible problems and their solution.
TUTORIAL
/ At first stage, download the boot.img and Magisk Manager. Don't forget to install Magisk Manager.
/ Now open Magisk Manager and install Magisk. Select file patching as the installation method and point the boot.img you've just downloaded.
/ When download+patch is done, turn on your PC, connect your phone using USB cable and transfer "magisk_patched.img", which will be placed in your phone's internal storage's download folder.
/ Then, open a command prompt (Windows)/Terminal window (Linux - MacOS), navigate to the folder that you've transferred patched image to.
/ Now restart your phone into Fastboot.
Code:
adb reboot bootloader
/ Make sure your phone is being detected by your PC. For Windows, you have to open Device Manager (devmgmt.msc) and update the device "Android" online.
/ When all done and you made sure your PC detects your phone in Fastboot, unlock the bootloader first.
Code:
fastboot flashing unlock
/ Check your phone. It has to show a warning regarding to bootloader unlocking. If it does, use Vol- button to highlight "Yes". But before having this done, again, make sure you backed literally all your data up. If you're sure, just hit Power button and accept unlocking. Your phone will reboot and will see a warning regarding to software checking. On that screen, press a random volume button and select Fastboot. We're not done yet.
/ Now, finally, flash the image we patched and transferred earlier.
Code:
fastboot flash boot /path/to/patched/image
For my case, as a Windows user;
Code:
C:\adb\fastboot.exe flash boot C:\Users\owZ\Documents\magisk_patched.img
/ When it's done, reboot your phone regularly. Don't forget that the warning I've mentioned will come up until you lock the bootloader, which I don't recommend. Also, since we didn't allow it to do the factory reset before, it's going to do the reset now.
Code:
fastboot reboot
/ When your phone boots up and you set it up regularly, head to Magisk Manager website and install Magisk Manager again. If you want, you can now integrate it to the system using Root Essentials or some other apps.
PROBLEMS
/ When trying to remount/modify /system partition, phone freezes until I do hard reset! - To solve, you have to literally reset your phone!
/ Most of the times; when trying to apply/remove a substratum legacy theme, the phone freezes. - Because it tries to modify /system partition - It requires reset to solve. If you're removing the theme, you can use Lucky Patcher to remove the overlays as LP uses a different method to remove system apps. But be careful that if you remove Android System/System UI overlay, you have to reboot your system (Android System overlays)/System UI (System UI overlays) not to cause infinite boot!
/ Magisk Manager has a few seconds of latency for showing root confirmation dialog - It's a problem with Magisk itself, not the phone.
/ The phone freezes upon opening ES File Explorer - I guess you tried to mount a system partition through it - Clear its data, reboot your phone and try to open it again.
/ After I successfully modify /system partition and reboot the phone, it gets stuck on branding screen - Go to recovery, press both three keys (Power, Vol+, Vol-) using a flat surface to show up the options (I recommend a desk), mount /system there and reboot. If this doesn't solve, do same but also clear cache.
/ Xposed Framework fails to install, freezing my phone - Original Xposed causes that, right. Just install it through Magisk Manager. Don't forget to install patched Xposed Installer there, too. This will also clear Dalvik-cache, which will result in really long boot for the first time as Android detects it as a system update.
UPDATE
About /system mounting, I've just found a workaround and it appears to work really well here.
/ First, to make sure /system mount is not busy, go to recovery, activate it by pressing all three buttons (Power+Volume keys) and select Mount /system.
/ When mounting is done, reboot your phone regularly.
/ Now go to Magisk settings and find Magisk Core/Safe mode. Enable it.
/ Then reboot to recovery, repeating step 1 and 2.
/ After all, do whatever you want to on /system. Don't forget that you will need to do these every time you reboot.
Venus v5 error
İ was make fastboot flash boot . But im getting an this error ---> " couldn't parse partition size 0x " please help
AliYavuzZ said:
Venus v5 error
İ was make fastboot flash boot . But im getting an this error ---> " couldn't parse partition size 0x " please help
Click to expand...
Click to collapse
Have you tried patching the boot.img I extracted? It works just fine here.