Related
Hi everyone, for Christmas my screen was crushed by a car .
The screen is completely destroyed (both touch screen & display screen).
However the phone is booting, so I can put it in recovery mod (I rooted the phone and I have clockworkmod).
After many trials, I succeeded in having adb connecting to my phone in blind mode.
I did this:
Code:
adb mount /data
adb pull /data /a_backup_folder
adb mount /system
adb pull /system /another_backup_folder
... and copied back my SD to my computer. I plan to buy another Desire and to revert the instruction by issuing a push for the data & system. This is:
Code:
adb mount /data
adb push /a_backup_folder /data
adb mount /system
adb push /another_backup_folder /system
Will it work ? Or is the system in sync with the flashed firmware ?
Can I selectively push some of the folders (namely applications, and the whole data). I hope to get back my settings, contacts etc...
I'm afraid I cannot do a whole lot more, since I do everything in blind mode.
Any advice on this ?
Thank you !
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
TheGhost1233 said:
Just make a nandroid, should be able to restore as long as you don't have a different screen version (AMOLED to SLCD) but not 100% sure.
Click to expand...
Click to collapse
Thank you for your suggestion.
Can I do it even if I do not have a screen ? I've tried to launch it but I fear it needs busybox (it says that it cannot find nc) and I think I do not have it (and don't know how to put it without the screen).
What are the supplementary steps that nandroid does ?
This is for CWM 2.5.0.7.
Sorry mist the part that you have to do everything blind, when in recovery press 5 times down on the volume rocker and then 2 times on the OJ let it sit for 10 min, should be done sooner but i don't know how to check if it's finished. After 10 min press once again on the OJ, your phone should reboot and in the Clockwork folder on the SD card should be a backup folder with a folder with the current date and time of the back up.
Unfortunately it did not work.
It did the steps as provided, and indeed the phone rebooted, but there is no clockworkmod folder on the sd card.
Is there any way to do a similar operation with adb ? This would be easier since when I'm in adb shell, I can type from the PC .
Try installing amon ra recovery. You should be able to do it. This is what the amon ra thread says:
Scripts available via adb :
* Nandroid v2.2.1 : enter "nandroid-mobile.sh" to start.
Explenation: http://forum.xda-developers.com/showpost.php?p=3046976&postcount=1
I think that this is what you are looking for
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
mercianary said:
Use the command below to find out what partitions each mtd is for (I don't remember)
cat /process/mtd
Then backup with
cat /dev/mtd/mtdx > /sdcard/mtd.img
(Replacing x with whatever number)
Get all the partitions you need, boot, cache, data and system. Then flash to your new phone from fastboot.
fastboot flash boot mtdx.img
You might want to get hold of a tool called unyaffs and take a look inside the images you make to check its all ok before you bin your old phone or send it back.
Click to expand...
Click to collapse
Ok the first step worked, but unyaffs does not want to open my imgs.
The size are as follow:
Code:
3*145*728 boot.img
3*145*728 boot_ro.img
41*943*040 cache.img
41*943*040 cache_ro.img
655*360 misc.img
655*360 misc_ro.img
4*718*592 recovery.img
4*718*592 recovery_ro.img
262*144*000 system.img
262*144*000 system_ro.img
154*796*032 userdata.img
154*796*032 userdata_ro.img
which seems good (I also made images from the mtdXro). However I should be able to extract userdata and system from my understanding. I tried with unyaffs both on linux and on windows, on both I get a segmentation fault.
Do I have a way to verify that theses images are good ? I do not want to trash the new phone I will buy with a faulty image...
Flash the same rom from recovery on your new phone, then flash the data image from fastboot, if it works the first boot should take a while as it builds the cache. If it doesn't work just clear data and it wont have done any damage to your new phone.
You will have to zip the data image before you fastboot flash it because it's too big for fastboot to receive.
If you have s-off on your old phone I would flash amon-ra recovery from fastboot then use the nandroid script over adb.
As long as you don't try to flash the recovery you backed up I don't think there's any chance of damaging your new phone doing this.
Ok the final solution was to use the new phone (rooted and with clockworkmod) as a reference.
I did the same backup sequence on the two phones, and have been able to restore the backup on the new phone.
Thank you everyone for your help !
Glad you got it sorted...don't drop your phone under a car again.
Sent from my HTC Desire using XDA App
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download
Warning! PhilZ recovery is currently in ALPHA stage for Xperia M. Some features may be broken!
Known bugs:
- Half-broken touch (you can use touch, however not select anything) - use hardware keys like in non-touch CWM recovery
- Broken navigation bar
- You tell me
XDA:DevDB Information
[c190x] [CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Sony Xperia M
Contributors
JustArchi
Version Information
Status: Alpha
Created 2014-07-05
Last Updated 2014-07-05
[size=+1]Flashing and updating instructions[/size]
If you have pure untouched stock
Before you begin: Make sure that you have the ROM you want in .zip format and this recovery in .zip format on your external sd card. If you don't have one, on your internal.
1. Install Towelroot APK.
2. Launch it, click on magic button, bah, you're now rooted.
3. Make a backup of your TA partition using i.e. Backup TA. DON'T SKIP THIS STEP, or you will lose your warranty forever. You need root for this step, so don't try it without 1 and 2.
4. Get familiar with fastboot.
5. Turn off your device.
6. Hold Vol-up button, don't release it.
7. Plug your phone to your PC, while you're holding Vol-up.
8. It won't boot (black screen) but LED should indicate that device is turned on.
9. Execute fastboot -i 0x0fce getvar version. Use fastboot.exe instead of fastboot if you're on windows, do the same for all fastboot commands, you should already know it.
10. If you got return value, such as "0.5", you did everything correctly, congratulations! If you did not get return value, don't go further until you get it, because your fastboot connection doesn't work.
11. Get bootloader unlock code from Sony here. You can view your IMEI with *#06# code if you need it.
12. Unlock bootloader with fastboot -i 0x0fce oem unlock 0xCODE where CODE is the code from Sony. I.e. if you got "ABCD0011" code on your e-mail, execute fastboot -i 0x0fce oem unlock 0xABCD0011
13. You should get response like "Okay".
14. Extract boot.img file from the zip you downloaded from this thread. Put in the same directory as fastboot.
15. Flash boot.img with fastboot flash boot boot.img.
16. Execute fastboot reboot to reboot.
17. Wait for your device to turn on, then immediately after you see that your led changed color to pink, start clicking Vol-Up button repeatedly. Stop when you see that your led changed it's color to blue.
18. If you did everything correctly, you should have booted custom recovery right now.
19. Enter "mounts & storage", and format: /system /cache /data. If you don't have anything important on your internal sd card, I strongly suggest to format /data and /data/media as well.
20. Flash any ROM you want
21. Remember that your ROM will overwrite your recovery (kernel), so if you want to preserve recovery, flash this zip right after every ROM flash.
22. Finally, reboot, be patient, you shouldn't get any bootloop.
If you already have CWM, TWRP or any custom recovery installed
1. Simply flash this recovery with install zip option.
I'm using CM11 (Free Xperia) with CWM Recovery , is it possible to install this recovery on the current? would it be possible to make any kernel related issues? (phone not booting up and else).
bugggmenot said:
I'm using CM11 (Free Xperia) with CWM Recovery , is it possible to install this recovery on the current? would it be possible to make any kernel related issues? (phone not booting up and else).
Click to expand...
Click to collapse
This kernel has been only tested on my private ArchiDroid 2.X build (not public yet), but it's based on FreeXperia sources so it should be compatible with all CM11 ROMs that don't need any kernel-ramdisk-based changes, including your CM11.
In case of issues you can always reflash, as this recovery boots and works properly, apart from some functions we're currently fixing with Phil.
JustArchi said:
This kernel has been only tested on my private ArchiDroid 2.X build (not public yet), but it's based on FreeXperia sources so it should be compatible with all CM11 ROMs that don't need any kernel-ramdisk-based changes, including your CM11.
In case of issues you can always reflash, as this recovery boots and works properly, apart from some functions we're currently fixing with Phil.
Click to expand...
Click to collapse
I also tried to build Philz and was succeeded, but it has same issue. I contacted Philz he told to me to enable Axis parameter in BoardConfig.mk but still the same. What you think, why this issue is caused? Due to faulty Touch screen events?
icoolguy1995 said:
I also tried to build Philz and was succeeded, but it has same issue. I contacted Philz he told to me to enable Axis parameter in BoardConfig.mk but still the same. What you think, why this issue is caused? Due to faulty Touch screen events?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53933204&postcount=4745
Failed to download ..
Can u give me mirror link like dev-host, mediafire, etc?
Edit: ok now fix
Edit again: i get bootloop, after flashing your phill touch -_-
itsnie said:
Failed to download ..
Can u give me mirror link like dev-host, mediafire, etc?
Edit: ok now fix
Edit again: i get bootloop, after flashing your phill touch -_-
Click to expand...
Click to collapse
Why you shouldn't get bootloop? It's only for CM11.
16. Execute fastboot reboot to reboot.
17. Wait for your device to turn on, then immediately after you see that your led changed color to pink, start clicking Vol-Up button repeatedly. Stop when you see that your led changed it's color to blue.
Click to expand...
Click to collapse
Upto step 16 was okay. 17th step won't work. Device is not getting into recovery mode when volume key is pressed.
no thing changed
JustArchi said:
[size=+1]Flashing and updating instructions[/size]
If you have pure untouched stock
Before you begin: Make sure that you have the ROM you want in .zip format and this recovery in .zip format on your external sd card. If you don't have one, on your internal.
1. Install Towelroot APK.
2. Launch it, click on magic button, bah, you're now rooted.
3. Make a backup of your TA partition using i.e. Backup TA. DON'T SKIP THIS STEP, or you will lose your warranty forever. You need root for this step, so don't try it without 1 and 2.
4. Get familiar with fastboot.
5. Turn off your device.
6. Hold Vol-up button, don't release it.
7. Plug your phone to your PC, while you're holding Vol-up.
8. It won't boot (black screen) but LED should indicate that device is turned on.
9. Execute fastboot -i 0x0fce getvar version. Use fastboot.exe instead of fastboot if you're on windows, do the same for all fastboot commands, you should already know it.
10. If you got return value, such as "0.5", you did everything correctly, congratulations! If you did not get return value, don't go further until you get it, because your fastboot connection doesn't work.
11. Get bootloader unlock code from Sony here. You can view your IMEI with *#06# code if you need it.
12. Unlock bootloader with fastboot -i 0x0fce oem unlock 0xCODE where CODE is the code from Sony. I.e. if you got "ABCD0011" code on your e-mail, execute fastboot -i 0x0fce oem unlock 0xABCD0011
13. You should get response like "Okay".
14. Extract boot.img file from the zip you downloaded from this thread. Put in the same directory as fastboot.
15. Flash boot.img with fastboot flash boot boot.img.
16. Execute fastboot reboot to reboot.
17. Wait for your device to turn on, then immediately after you see that your led changed color to pink, start clicking Vol-Up button repeatedly. Stop when you see that your led changed it's color to blue.
18. If you did everything correctly, you should have booted custom recovery right now.
19. Enter "mounts & storage", and format: /system /cache /data. If you don't have anything important on your internal sd card, I strongly suggest to format /data and /data/media as well.
20. Flash any ROM you want
21. Remember that your ROM will overwrite your recovery (kernel), so if you want to preserve recovery, flash this zip right after every ROM flash.
22. Finally, reboot, be patient, you shouldn't get any bootloop.
If you already have CWM, TWRP or any custom recovery installed
1. Simply flash this recovery with install zip option.
Click to expand...
Click to collapse
i installed it by cwm and by fastboot and cwm still exist
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
kevs888 said:
Hey all,
So, my smart self was attempting to flash Marshmallow 6.0 from 4.3 (rooted)...I did the same thing that was here on this THREAD and now my tab can only go into TWRP, but there's no OS installed because I wiped (and didn't make a darn backup....), but there are a few differences from the thread I referred to:
- I can get into my Bootloader
- I can get into TWRP
- I have the current TWRP 2.8.7
- I've tried the Nexus Toolkit from HERE, my device serial is recognized, but it states that I'm offline
- Because I'm offline, I can't push any files to my device through the tool
- When I'm in TWRP, my computer will recognize my tablet and I can actually get into folders and what not, but I can't copy/paste any files to flash within TWRP and I get an error
- Anytime I power down or reboot within TWRP, it tells me that I have No OS installed
- I can't use ADB (as far as I know) because my device shows that it's offline
Is there any hope that I can recover even back to 4.3?
Any guidance would really be appreciated. I have to step away because I'm frustrated and am angry at myself that I didn't make a nandroid.
Thanks in advance.
Click to expand...
Click to collapse
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
graphdarnell said:
Are you using stock rom? Because if you are, I wouldn't even try. What with the widespread knowledge that stock might brick, some people insist on it. Otherwise, if you can get to the bootloader:
(1) Make sure it's unlocked (if you're not familiar, connect tab to PC, make sure fastboot works, then enter "fastboot oem unlocked" without the quotes then follow instructions on your tab);
(2) Flash bootloader 4.05 if you haven't already;
(3) Get a USB OTG thumb drive (you might need an OTG adapter for this); and download a Marshmallow-based custom rom in the Android Development section;
(4) Get into TWRP and mount USB OTG. You should see all the files on your thumb drive;
(5) Copy all data you care about to your PC;
(6) Wipe everything except USB OTG twice. Then go to Format and do it twice too. If yours is 32GB, it will take a while (30 Mins average depending on how much data);
(7) Flash rom, then Gapps.
You should be able to boot after that. Good luck.
(4)
Click to expand...
Click to collapse
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
kevs888 said:
Thanks for this! A few questions...
- Before I wiped my OS, I was running the Smooth ROM. Does this make a difference? - Regarding fastboot, how do I get into it? I can't use adb because it lists my tablet as Offline when I type in "adb devices"...
- My lock icon is unlocked at the Google screen, but it stops there since I currently have no OS
- Would I be able to skip to your Step 4 just use the USB OTG and mount the original 4.3 OS through TWRP?
- Should I just flash the OEM 4.3? Or should I load the Smooth ROM or whatever other ROM instead of the OEM 4.3?
Thanks for your continued help!
Click to expand...
Click to collapse
Fastboot page
graphdarnell said:
It shouldn't make a difference what rom you flash now so long as you wipe and format everything inside TWRP. But you must make sure you have bootloader 4.05. 4.02 will not allow you to flash LL or MM successfully, and the system does not upgrade on its own no matter what rom you're flashing now.
Since you said you couldn't get TWRP to copy anything, I suggested that you use a thumb drive. Basically, if you turn the tab totally off, hold power + volume down for a few seconds, it should take you to the fastboot page (pic). Look to see what bootloader version you have there.
From here, you can basically flash anything. I recommended that you wipe and format first with TWRP because it happened to me a few times when for some reason, wiping alone still left some residual data that interfered with flashing newer roms.
Stay away from anything stock for the moment. God knows it has bricked more than a few devices. Download SkipsoftToolKit and flash from the fastboot page if you want an automated process. It has worked wonderfully in my experience. Ask if you have more questions. Have fun.
Click to expand...
Click to collapse
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
kevs888 said:
This is really helpful...I think I'm almost there.
I'm on a super old Bootloader (see attachment) so I'll need to update. I downloaded the update from this XDA Thread
More questions:
- Would I be able to push the 4.05 bootloader update and custom whatever Marshmallow ROM via the toolkit instead of from a USB OTG?
- If I was rooted on 4.3, am I still rooted so that I would be able to flash the custom ROM? I don't want to risk doing further damage, lol.
- I'm not home at the moment, so I can't test this out -- I'm thinking I couldn't put anything into my tablet last night because it was running TWRP and I didn't have it on the Fastboot screen. Would being in the Fastboot screen possibly allow me to copy/paste the zip files into my tablet?
- If there's nothing I need to copy from the tablet, would I still need the USB OTG? Or could I just use the Toolkit to push everything into my tablet and flash via TWRP?
Based on your answers to the above would this be the correct order:
1. Push 4.05 bootloader update and custom ROM via toolkit to my tablet
2. Flash 4.05 bootloader update within TWRP
3. *Per your earlier advice* Wipe everything except USB OTG twice. Is this cache, dalvik, system, and data? Or literally there's an option for "wipe everything" (I don't remember what I saw)?
4. Then go to Format and do it twice, too. I have a 32GB, so I'm expecting it to take awhile for the format
5. Flash ROM, then Gapps. I don't have any apps I need to put back so much as I need an OS to load, so I can add later.
Thanks again for everything!
EDIT:
Okay, so I came home and was able to use the Toolkit to recognize the device in fastboot mode. However, I wasn't able to push anything into the phone because the Toolkit said that I needed to be booted into Android.
The last thing I saw when I was in TWRP poking around was that I saw that I could install .zip files from USB OTG. Are either of these alright for me to connect my flash drive to and be recognized inside TWRP?
Example 1
Example 2
Click to expand...
Click to collapse
If you're comfortable using the ToolKit, you don't need an OTG cable. Connect your tab to PC, fire up ToolKit, complete all the prelim BS, then flash the bootloader from TK. Do not use TWRP for this. To do this, open the ToolKit folder in drive C:, locate the folder therein for zips, place the zip files (4.05 bootloader; TWRP; or custom roms) in there, and start to install. I am talking off the top of my head. But give me a few minutes to check the Kit again, and I'll give specific instructions. Bear with me, as I'm on Linux at the moment and therefore cannot start ToolKit (which is in Windows).
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
graphdarnell said:
Things to do in order:
1. Download bootloader 4.05 (flashable zip HERE); and custom rom of your choice (zip format)
2. Locate the Unified Android ToolKit on drive C: on your PC and open it;
3. Locate the folder “put zip file to sideload here” → “Nexus 7 2013” then paste
bootloader zip and Rom zip in there;
4. Fire up Toolkit with tab connected; complete all the prelim questions;
5. Follow all the steps to install TWR 2870 (pic 8, choice 6);
6. Go to TWRP, wipe and format.
7. Go back to TWRP main page → “Advanced” → “ADB sideload”;
8 Go to ToolKit (pic 8) enter choice 16 (Look at the pics that follow for the correct choices) to
sideload Bootloader;
9. Flash Bootloader.
10. Go back to TWRP main page → Reboot → Bootloader. Once there check bootloader version 4.05;
11. Get into TWRP to sideload Rom; flash it.
Click to expand...
Click to collapse
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
kevs888 said:
Wow, this is awesome. Thank you so much.
I had already flashed TWRP 2870 before I wiped the OS, but I figured I'd try again using the Toolkit, but I got an error. I stopped here just in case.
Earlier, I tried flashing the zip for the bootloader the same way you just instructed, but my serial number turned into question marks?
Please see attachments. My pics are on the right side of the comparisons and I blacked out some of my serial number just in case for the TWRP pic.
Thanks again for the continued support!
Click to expand...
Click to collapse
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
graphdarnell said:
Ok. One step at a time. Since you don't have an OS installed, ToolKit cannot complete the process of sideloading because it normally would have to use ADB from within the OS (which is absent) to restart the tab into recovery mode (TWRP). But if you're already in sideload mode within TWRP, it would detect it and transfer the file over to your tab. Let's go back.
(1) Fire up ToolKit (TK), go to sideload step, type the file name and stop. Get to fastboot page on your tab. Go back to TK and hit enter. TK should detect fastboot mode, download TWRP 2.7.1.1, take the tab into TWRP, tell you to go to sideload mode. Thereafter, it should detect this mode and transfer the file over. Then TWRP would flash the bootloader 4.05 automatically. If successful, sideload the rom the same way to flash it. Then upgrade TWRP back to 2870 with TK.
(2) Failing the above (because TWRP somehow doesn't function correctly), put the tab in fastboot mode, go to TK and follow the steps to flash TWRP anew. TK should detect fastboot and begin to flash the recovery. That done, go back and restart (1) above.
(3) If that still doesn't work, we have to resort to fastboot.exe and do it by command lines. But that's far ahead. Try the above first. We'll cross that bridge if we get to it.
I can send you an automated package that would upgrade the bootloader to 4.04 that I downloaded a year ago from Scott's Roms (thanks to him). It's good enough for Lollipop 5.1. The file is about 4MB and I'm not sure how we can do this through XDA. But if we ever get there, I'm certain we'll find a way. And smile, it's only a lousy tab.
Click to expand...
Click to collapse
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
kevs888 said:
Let me just say, I'm so thankful for your help in all of this. Seriously. Thank you.
I kept on tinkering with the ToolKit and Fastboot kept on stopping everytime I switched to TWRP. I got to the point where TWRP showed 2.7.1 but the ADB Sideload kept getting stuck at the "Starting Sideload" prompt.
I went out and bought a $3 OTB USG cable and figured I'd give it a go since this sounded easier (theoretically). At first, I couldn't understand why the OTG wasn't recognized within TWRP. Then, I realized I needed to mount it within TWRP.
Once it mounted, I wiped and flashed the 4.05 bootloader zip. Success.
I went back into the Fastboot screen to verify 4.05. Success.
Went back into TWRP 2.8.7 and flashed a 6.0 ROM from these boards. Success.
Flashed Gapps. Success.
Rebooted. I'm now running a custom Marshmallow ROM and it runs so smoothly now.
Seriously. Thank you.
Click to expand...
Click to collapse
I'm glad you got it working again. Sorry you had to make a trip to the store. You should've waited for KT to switch the tab to TWRP 2711 for you. But it was not a waste of time anyway.
The original thread was closed...sorry guys I've been busy. Link to the rom has been updated!!!!
Eureka! After two days of trials, tribulations, and extreme reading, I have been successfully able to create a flashable, working Stock Rom for the MetroPCS XT1765. And yes, I figured out how to get root working on it too (albeit experimental)!!!! This has been something visibly lacking in our E4 community, and since its the phone I have, I felt it was a necessity since once you unlock the bootloader or ever took an update its impossible to get the original .xml back on the phone.
Disclaimers Before You Begin:
This tutorial is for people like me that wanted a flashable stock rom for the Moto E4 XT1765 Metro PCS Qualcomm/Perry Variant running on stock Nougat 7.1.1 Please follow the guide carefully. Cutting corners and skipping steps could have MAJOR CONSEQUENCES.
For everybody with other Perry variants, I don't know if this rom will work or not, so if you're feeling frisky try at your own risk as this has only been tested on the XT1765.
Follow the following at your own risk! I am not responsible for any mishaps with your devices.
Introduction
The A8M'S METROPCS XT1765-PERRY STOCKROM PROJECT was created from the Motorola PERRY_METROPCS_C_7.1.1_NCQ26.69-46_cid22_subsidy-MPCS_regulatory-DEFAULT_CFC.xml firmware, straight from their official site. This was not made from a backup, but from extracting the firmware files itself, and compiling via Assayyad kitchen. Nothing was removed from the firmware on this build, but you will have to flash Open Gapps and add it during installation, as well as No-Verity. Outside of that, it's a virgin rom slightly removed.
Preparation
1. READ EVERYTHING IN THIS GUIDE BEFORE STARTING! This variant can tear you a new one, so get a handle of what you're working with on this.
2. This is only for people that have bootloader unlocked their phones, and can successfully use TWRP on their device. I highly recommend @squid2's TWRP (which is in my download files list on this guide). I can also only give support for those using his TWRP, as that is the one I used flashing this rom.
3. Backup all your data if you want - the phone has to be wiped clean for this to work right as a dirty flash won't cut the mustard. It's not hard exporting your contact list, or using SMS Backup Restore for your call log and text msgs to your SD card. This helps putting back your phone exactly how you had it before this. Takes a second (but be sure to uninstall SMSBackupRestore when you've successfully restored your stuff unless you like it).
4. Download all the files from the list below,and put all of them but the boot.img on your SD card. That is the Stock Rom, the noverity.zip, the magisk.zip, superuser.zip, rootchecker, and opengapps.zip. Make sure the file sizes are correctly matching and that there are no errors in your transferring.
***NOTES SO YOU DON'T FREAK OUT***
Once you flash the rom its going to take 3-5 minutes to boot the first time. It's normal. If you see the "Hello Moto" constantly repeat, that's a bootloop, and you need to wipe and reflash again (even though this did not happen to me). Also, if you see a Bad Key black screen and it doesn't boot, you've made a mistake by not flashing no-verity after flashing the rom. It isn't a brick, you just need to go to recovery and flash it again.
Files Needed:
Download and add these to your SD card. These are the exact files I used on my phone. ***NOTE*** My file share service says they will delete these June 14th, so if you know of a fast share site that's free and can handle big files, please let me know.
Mod Edit: If / When you update these links, PM @Az Biker to reopen this thread.
1. My Flashable Stock Rom: https://drive.google.com/open?id=1ScvA3zO6qHY4mhMtaM4aDajx9ZH6CpYj
2. OpenGapps Nano: https://drive.google.com/open?id=1x3Uz_sia1N3OYPGrdEwJ7TBeSmyiDlEZ
3. No Verity Opt Encrypt.zip: https://drive.google.com/open?id=1FqcpWgYJ16HYjIzZgIlHEZOlKJPjaorM
4.Superuser-r259.zip: https://drive.google.com/open?id=1iFswMvZ2vycIrQ4tK7nTWZAG7zktrPH2
5. Magisk v14.0.zip: https://drive.google.com/open?id=1wyV5EJe2wtSIadFNZsbJQOfGrsNQzG4p
6. Root Checker (Playstore)
7. Boot.Img file in case you make it to the bonus round: https://www45.zippyshare.com/v/Uhru1YeL/file.html
Additional Software: you may need Minimal ADB and Fastboot in case you don't have TWRP installed already for the rooting part or if you run into problems trying to gain root; you'll have to search XDA for that one .
Part I - Installation:
1. Make sure the phone is fully charged.
2. Make sure your sim card is REMOVED from the phone. As soon as you flash the stock you'll see the phone trying to push an update, as it auto turns on your data if you choose not to set up wifi (which you shouldn't do just yet).
3. Boot into Recovery TWRP. (If TWRP isn't installed, see 3A and skip this part.) If TWRP is installed you can power the device off and then hold the Volume Down plus the Power key to get into fastboot, and with the volume rocker select recovery and then hit the power button to boot. If you have unlocked the bootloader you will see N/A black screen in this process.
3A. If you do not have TWRP installed, With the phone on, run the command in Minimal ADB and Fastboot "adb devices" without the quotations. You should see your phone ID and device. Next, turn the phone completely OFF. Press Volume Down and Power to boot into fastboot mode. Do not use "adb reboot bootloader" as that command may or may not work and hang at "waiting for device" (it was iffy for me and it knocked off USB permissions BADLY). Connect device to PC via USB cable. Then open up Minimal ADB and Fastboot (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your recovery image file is in the Minimal ADB directory or it won't work; the type "fastboot boot thenameofyourrecoveryfile.img". This should boot you to the TWRP.
4. Once booted into TWRP, tap Wipe, then Advanced Wipe; check Dalvik/ART Cache, System, Data, Cache ONLY, then swipe to wipe. Just to be on the paranoid safe side, click back (triangle pointing left) to the main menu, go back to Wipe, Tap Format Data, Type yes and wipe. Click back to main menu after - do NOT reboot.
5. Click Install; install A8M'S-METROPCS-XT1765-PERRY-STOCKROM-PROJECT-04142018.zip. Afterwards, go back to main menu.
6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
7. Click Install; install open_gapps-arm-7.1-nano-20180331.zip. Note: This takes 3-5 minutes. You will see a warning that StockRom Gapps is installed. That's okay - ignore it, its necessary. Click back to main menu after.
8. Click Install; install no-verity-opt-encrypt.zip. Click back to main menu after.
If you don't want root, hit Reboot, then System. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed. Congratulations, welcome to your brand spanky new stock rom flashed phone.
If you do want root don't reboot, keep reading the next section.
Part II - Rooting:
Okay, this section might be challenging, but hopefully this will ease your nerves as you walk through the ever so daunting task of rooting. It has some of the same challenges that rooting the .xml had (refer to my "The Complete Noob Guide to Rooting MetroPCS XT1765 Qualcomm Variant" guide for such challenges). This might feel totally redundant, and to a lesser degree it is, but it will pay off in the end. And remember, if at first you don't succeed, wipe clean and flash again!
9. In TWRP, click Install; install Magisk-v14.0.zip FIRST - very important. Do not install supersuser first. Afterwards, click back to the main menu.
10. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
4. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
5. Disable Updates. This thing will race you to that. On initial launch, you should not have the wifi connected. As soon as you put your Sim card back in, IMMEDIATELY cut off your data until you disable updates.
Bonus Round - In Case Of Error -1 Issues:
Hopefully, the first two parts got you straight, and you're playing on your stock rom now. However, this variant is challenging, and getting root could be a pain in the android ass. If you installed either superuser.zip or magisk.zip and got an Error -1 for either or both, this section is for you.
Unfortunately, the boot.img getting corrupted probably is the main culprit. Don't freak, it was a problem with the original root method on this variant straight out the box. Also, if you have been flashing/re-flashing a lot, sometimes it just makes it funky. But its a fix with a little patience.
1. Turn your phone on, and let it boot.
2. Go into your phone settings, and activate developer options (you know, hitting the build number 7x).
3. Make sure your USB debugging is enabled AND you've given permissions for your computer to have administrative access with it enabled (more on this below). Very Important. Also uncheck "Verify Apps Over USB", but only if you having probs with fastboot in ADB. You can recheck it later.
4. Make sure you've enabled Allow installation of apps from Unknown Sources (its in the Security section of Settings).
5. Turn your phone completely off.
6. Plug your phone via USB cable into the computer.
7. Press Volume Down and Power to boot into fastboot mode.
8. Open up Minimal ADB and Fastboot command prompt on the PC (Make sure you don't have it set to open this as an administrator, it messes with permissions) Make sure your boot image file is in the Minimal ADB directory (same place you see recovery.img that boots/installs TWRP) or it won't work. Download it from the files list above.
9. In Minimal ADB command prompt type "fastboot erase boot. " It might say permission denied, and that's okay. Keep going.
10. In Minimal ADB command prompt type "fastboot flash boot boot.img" That should restore your original boot image to stock and correct any error 1 problems. And no, you don't have to reflash the stock rom after this either.
11. Reboot into recovery - make sure you select READ ONLY when it launches.
12. 6. Click Mount; make sure System, Data, Cache, and Micro SD Card are checked. Disable MTP. Click back to main menu after.
13. Click Install; install Magisk-v14.0.zip FIRST - very important. Afterwards, click back to the main menu. It should be successful.
14. Click Install; install superuser-r259.zip. Afterwards, click Reboot. Wait for the N/A to pass on the black screen and wait for the Hello Moto opening and then the white MetroPCS splash screen. Can takes 1-4 minutes on first boot. From the Metro Screen it will go Black - don't freak out, give it a couple of seconds and from there you should see the Google Wizard guide you on in. It might feel slow, but after you get past the wizard it's smooth sailing at regular speed.
15. Install Root Checker (free on Google Play). You can access your file without a file manager by hitting Downloads, selecting the three lines on the top left, and selecting SD Card from the pulldown menu. You should have root. Also check the Magisk Manager, it should confirm its installation with a green checkmark.
If you're still having problems after flashing the boot.img, start all the way over from the beginning wiping everything clean. That should correct the problem and let you install without trouble or needing to flash the boot.img again.
Bonus Round - In Case Of No Root After Root Issues:
As soon as the little bugger tried to force the update via my data when I stuck my Sim Card in, it messed with my root, even catching and cutting it off as quick as I could and not doing a full update. When I rebooted, I lost root. This has happened off and on every other flash - so your root may stick or it may not. If it doesn't, either you can 1. wait for a better method, 2. reflash, 3. live without it for now. This is still kind of experimental for me, as I had to wipe and reset to get root back. Still trying to figure out a more perm way for this like on the .xml.
Enjoy Everyone - I'm learning, taking it one android day at a time but I'll help when I can. It's an awesome day to be a nerd!
Sincere Thanks:
The devs that created a method of root for various variant E4's that sent me on this journey, I love you guys!
The devs behind Magisk, Superuser, and No-Verity!
@squid2 for the TWRP recovery that helped A BUNCH!
@ASSAYYED for the beautiful kitchen that forced me to keep learning.
@Al936 for the beautiful tutorial that helped me figure out how to extract the files needed in the journey.
@MotoJunkie01 for giving me the inspiration to try it on my own.
@madbat99 for the small, but powerful words of encouragement.
And to the community at large that let me ask questions to the point of getting on their nerves. Thank you!!!
[REPOST][ROM][PERRY][MetroPCS.XT1765][STOCK] A8M'S XT1765 STOCK ROM April 14th, 2018
Reserved.
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
ilanor said:
Good work. When you say nothing was removed, does that mean the six Metro apps are still included? I've been looking for the stock Motorola ROM for the unlocked variant of this phone. Thanks.
Click to expand...
Click to collapse
Everything is stock. Just as it was on a complete fresh out the box setup. You will find all the metropcs apps there.
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Moto_E4_xt1765_metroPcs said:
How do I put the boot image into the same directory as adb and fastboot ? I don't really understand stand what that means.
Click to expand...
Click to collapse
you install ADB and fastboot on your computer then open the folder that contains those. Put the boot image in that folder
Pretty sure this guy that is extremely outdated though
this flashed fine and magisk and superuser flashed fine booted actually a little faster than normal. I don ' know how but it say no service though and it throws an error "error occured could not search" or something similar . how can i get my radios back
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?