Related
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
gooner4life said:
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
Click to expand...
Click to collapse
Is it still recognised by the computer?
As in, if you plug it in with USB does it appear on your device manager?
Anyway, I would recommend using Wug's Toolkit (http://forum.xda-developers.com/showthread.php?t=2389107) to sort you out.
It's pretty straight forward so you should be able to fix it easly.
username4this said:
Is it still recognised by the computer?
As in, if you plug it in with USB does it appear on your device manager?
Anyway, I would recommend using Wug's Toolkit (http://forum.xda-developers.com/showthread.php?t=2389107) to sort you out.
It's pretty straight forward so you should be able to fix it easly.
Click to expand...
Click to collapse
No it's not recognized by my PC too. So the toolkit won't be useful too i presume?
Any other options? Just wait it out till the battery is dead?
gooner4life said:
No it's not recognized by my PC too. So the toolkit won't be useful too i presume?
Any other options? Just wait it out till the battery is dead?
Click to expand...
Click to collapse
Your best bet is to try them.
Also give a look here:
http://forum.xda-developers.com/showthread.php?t=2544361
gooner4life said:
Hi all,
I tried to root my Nexus 7 according to this youtube link
http://www.youtube.com/watch?v=X1cD-JXRGX8
During the step to install" super SU", i copied the the "unzipped" version of the file into the device, and couldn't install it as per video.
So i tried restating the device to try to copy the right file to the device, but now it just stucked at the loading screen (circle & square alternating, not the X screen) and i couldn't power it off too.
What should i do? Help please! Thanks!
Click to expand...
Click to collapse
Long press the power button and that will make it reboot, as soon as the screen turns OFF, hold down the volume down button and it will boot into the bootloader, use the volume button to select recovery, press the start button to go into recovery. In recovery (TWRP) click on wipe then do a factory reset. If it is off, press and hold volume down and power button together and that will get you to the bootloader screen.
wantabe said:
Long press the power button and that will make it reboot, as soon as the screen turns OFF, hold down the volume down button and it will boot into the bootloader, use the volume button to select recovery, press the start button to go into recovery. In recovery (TWRP) click on wipe then do a factory reset. If it is off, press and hold volume down and power button together and that will get you to the bootloader screen.
Click to expand...
Click to collapse
This whole rooting process confuse me. So you're saying after doing this, just start over the rooting process as per youtube link again or continue the step where i did wrong?
P/S is it easier to root using that rootkit as per post above?
gooner4life said:
This whole rooting process confuse me. So you're saying after doing this, just start over the rooting process as per youtube link again or continue the step where i did wrong?
Click to expand...
Click to collapse
You're two thirds of the way there. You supposedly have the bootloader unlocked, you can see that when it boots up at the "Google" screen the lock will be unlocked, It will also say unlocked in the bootloader screen. And you should have TWRP installed if you tried to flash supersu. So.. at this point, you need to flash the supersu "zip" in TWRP. Before you start making any changes I would recommend making a backup in TWRP.
gooner4life said:
P/S is it easier to root using that rootkit as per post above?
Click to expand...
Click to collapse
What you are using is part of the android sdk (adb/fastboot), the platform-tools folder with the usb drivers moved into it, not really a toolkit. I've never used a toolkit so I can't say a lot about them, I have the complete sdk installed, you were using part of it. Were you able to boot into recovery and do a factory reset?
You should not have followed that guide.
1st: Go to here: http://forum.xda-developers.com/showthread.php?t=1538053. Download the zip. DO NOT UNZIP.
2nd: Make sure that ADB is set up on your computer. To download, go to https://developer.android.com/sdk/index.html. Follow the instructions to install. Open the SDK (should be in C\development\adt-bundle-windows-x86_64-20131030\, or whereever you installed, it is an execultable file. It should have a little green android logo next to it, and it is called "SDK Manager". It will take a couple seconds to open. Once it has opened, install "Android SDK Platform-tools".
3rd: Move the Super SU zip into the C\development\adt-bundle-windows-x86_64-20131030\sdk\platform-tools, or wherever you installed the platform-tools. It should be inside the SDK folder. Just paste the zip there.
4th: Boot your Nexus 7 into recovery. Push and hold the power button and volume down button at the same time and boot into the bootloader.
5th: Boot into recovery. Do so by pressing the power button for a while, and eventually it will shut off, as mentioned above.
6th: Press and hold power button and volume down to boot into bootloader. Once in the bootloader, push the volume down button until recovery is selected.
7th: Boot into recovery by pressing the power button.
8th: In recovery, wipe the cache and dalvik under the advanced wipe in the wipe menu. Go back and click install. Click "apply from sideload", or something like that, I forgot the exact wording. Connect your tablet to your computer through a USB cable.
9th: Go back to your computer. Go to C\development\adt-bundle-windows-x86_64-20131030\sdk\ or wherever you installed the sdk. Press shift, and then right click on the folder that says "platform-tools". In the menu, click "open command window here".
10th: Copy the exact name of the supersu zip file in the platform-tools folder.
11th: In the command window type: adb sideload UPDATE-SuperSU-v1.86.zip
12th: Press enter. The name of the super su file may not be exactly that, but similar to it.
13: Reboot your tablet.
I don't know if you are a noob, or very experienced, so I made this as noob-friendly as posisble, sorry if I offended you in any way. Here are some pictures.
I did manage to boot into bootloader screen 7 the option to start, but same thing happen, it still stucked at the "4 colors" circle screen. Problem is guys i couldn't get the PC to recognise my tablet even in the bootloader screen. What should i do now?
wantabe said:
You're two thirds of the way there. You supposedly have the bootloader unlocked, you can see that when it boots up at the "Google" screen the lock will be unlocked, It will also say unlocked in the bootloader screen. And you should have TWRP installed if you tried to flash supersu. So.. at this point, you need to flash the supersu "zip" in TWRP. Before you start making any changes I would recommend making a backup in TWRP.
What you are using is part of the android sdk (adb/fastboot), the platform-tools folder with the usb drivers moved into it, not really a toolkit. I've never used a toolkit so I can't say a lot about them, I have the complete sdk installed, you were using part of it. Were you able to boot into recovery and do a factory reset?
Click to expand...
Click to collapse
Ok i can boot to recovery mode and get to TWRP. But as my post above the superSU is not in zipped form, what should i do then? And i couldn't copy the zipped verison into the tablet as my PC won't recognise the tablet. Do i choose wipe to start all over again from scratch? (assuming that's what wipe will do?) or browse into subfolder of superSU "i.e. app, bin, etc, xbi" and install form there manually? Dam im confused without knowing any basic of rooting...I thnk you're the closest to understanding where i am now, please help! Thanks!
ok guys i think my N7 got some serious problem!!
Now it would just stucked on the Google screen and won't even go to the recovery mode!!!
What should i do now to reset it back to original state now?!!
gooner4life said:
Ok i can boot to recovery mode and get to TWRP. But as my post above the superSU is not in zipped form, what should i do then? And i couldn't copy the zipped verison into the tablet as my PC won't recognise the tablet. Do i choose wipe to start all over again from scratch? (assuming that's what wipe will do?) or browse into subfolder of superSU "i.e. app, bin, etc, xbi" and install form there manually? Dam im confused without knowing any basic of rooting...I thnk you're the closest to understanding where i am now, please help! Thanks!
Click to expand...
Click to collapse
Try and do a factory reset. Just remember a factory reset is not a restore and it will not put your device back to the way it was before you tried to root. A factory reset will wipe the cache and data, not the system. Any changes to the system, kernel or recovery that you made will still be there after a factory reset. Go ahead and dot a reset and let's see if that will get your N7 to boot up. And we can go from there.
wantabe said:
Try and do a factory reset. Just remember a factory reset is not a restore and it will not put your device back to the way it was before you tried to root. A factory reset will wipe the cache and data, not the system. Any changes to the system, kernel or recovery that you made will still be there after a factory reset. Go ahead and dot a reset and let's see if that will get your N7 to boot up. And we can go from there.
Click to expand...
Click to collapse
I might have stuffed up here mate, you might have missed my last post. I did a factory wipe, and tried to use the toolkit as suggested, and i'm now im deeper water where i can't even get into recovery mode. Everything just stucked between the "Google" screen and the "volume down + power" screen....gosh i really feel stupid now...Any more suggestions?
gooner4life said:
I might have stuffed up here mate, you might have missed my last post. I did a factory wipe, and tried to use the toolkit as suggested, and i'm now im deeper water where i can't even get into recovery mode. Everything just stucked between the "Google" screen and the "volume down + power" screen....gosh i really feel stupid now...Any more suggestions?
Click to expand...
Click to collapse
I did miss your last post. Holy crap what are you doing? You went from knee deep to drowning.
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
What you're saying is that you can't get to the bootloader screen now?
wantabe said:
I did miss your last post. Holy crap what are you doing? You went from knee deep to drowning.
---------- Post added at 04:17 AM ---------- Previous post was at 04:16 AM ----------
What you're saying is that you can't get to the bootloader screen now?
Click to expand...
Click to collapse
Yep I'm serious **** now! Any more experts here have any idea? Or do i have to bring it to local mobile shop to get it fixed? Is Google able to help ?
Anyway... getting supersu installed is a non-issue if you can't get it to boot up. When you were trying to download supersu what you were looking for was the installable zip at Chainfires thread."CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu."
wantabe said:
Anyway... getting supersu installed is a non-issue if you can't get it to boot up. When you were trying to download supersu what you were looking for was the installable zip at Chainfires thread."CWM / TWRP / MobileODIN installable ZIP: http://download.chainfire.eu/supersu."
Click to expand...
Click to collapse
Nah i was just using the SuperSU zip i downloaded as per youtube link. The problem is my PC cant detect my tablet and i can't do sh**t!
Any manual hardware reset option on N7?
If a factory reset didn't clear it up you might be able to get away with just flashing the system image. Long pressing won't make it reboot?
I'll tell you how the tablet is right now, and hopefully you have some ideas where to go from here.
Atm, when i turn on and off the tablet.
but when i turn it on, it will go straight to the google screen with lock image at the bottom, then it will just stuck there
I tried going to recovery mode, and it won't come up with TWRP , and after a black screen, it will go back to boot screen
Tried "restart bootloader", did nothing too, just gone back original boot screen .
So now what? Gosh did i just break my brand new N7?
I'll tell you how my tablet is right now, and hopefully you have some ideas where to go from here.
ATM, I can turn on and off the tablet., but my PC won't recognise it
However, when i turn it on, it will go straight to the 'Google" screen with lock image at the bottom, then it will just stuck there
I tried going to recovery mode, and it won't come up with TWRP as before, and after a black screen, it will go back to boot screen
Tried "restart bootloader", did nothing too, just gone back original boot screen .
So now what? Gosh did i just break my brand new N7? :crying:
So my second zenfone is dead.
Like many others, it gets stuck at the asus loading screen with the spinning wheel.
This did not happen after any obvious action, like an update - it was just turned off when i woke up, and wont load beyond the spinning wheel of death.
I have booted into fast boot mode (power and vol +), selected [recover mode] and got the broken android logo.
I then hit power and vol+, then release vol+ as suggested, but instead of a menu, i get a bunch of yellow console output, 3rd line of which is:
E: failed to mount /cache (invalid argument)
This appears for less than a second, then back to flashing broken android logo.
Repeating ( power and vol+, then release vol+) results in the same briefly visible console output
I turn off, and reboot into fast boot mode, and try using adb.
I enter the command 'fastboot erase cache' and it completes in 0.4 seconds, no errors. Has no effect on phone (reboot stuck loading, recovery mode same error as above).
Next i try 'fastboot format cache' - the command appears to work, but again completes in just over a second, and has no effect on the phone.
The only info i could find directly relating to this error is on a random .info website, so im reluctant to follow the steps:
http://mobilecon.info/fix-asus-zenf...-into-recovery-mode.html#sthash.slqGoK95.dpbs
Anyone here solved this issue? Or is it time for a warranty claim?
Thanks
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
azthemansays said:
http://www.ibtimes.co.uk/how-unbrick-asus-zenfone-2-fix-bootloop-issues-1511521
Just don't do step 15 (factory reset) if you want to keep your old data.
Click to expand...
Click to collapse
Thanks for the link - it looks much the same as the one i posted, with the addition of flashing the system image.
Do you know if there is any danger in trying without flashing system 1st?
Also, have you used or seen this method used specifically to fix the mount failure i have described, or its just a general 'de-bricking' guide?
Finally, do you or anyone else have any insight into why this might have happened in the 1st place - as i mention, i did not do anything beyond normal use prior to the issue.
thanks
Sounds like the recovery corrupted... could be a range of things from improper shutdown to an improperly coded app that caused the error. If you want to flash just the recovery and see if that fixes it, go right ahead, but don't forget to erase your cache after you flash recovery.
Whenever I get stuck in a bootloop, the steps I follow are:
1) clear the cache and see if it fixes it, as something might be there that's preventing you from booting
2) flash the most current firmware to see if it fixes it, as something might have modified a section of one of the partitions that's preventing you from booting (make sure to clear cache after flashing)
3) contact support because it's more likely hardware failure
There's no danger in flashing any of those partitions, at most you'd lose the Xposed framework, root and busybox - which are easy to reinstall. It doesn't affect much else, and your info should be intact. I would advise getting the firmware from a reputable source though... I just get it off the Asus website, then root the phone after.
Try reinstall recovery
Download stock recovery(there is download link from zenfone2 index)>go fastboot mode>then flash recovery using command :
fastboot flash recovery (recovery image name).img
>Reboot to recovery>adb sideload full firmware
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
Hello, sorry for the generic title, but i'm quite the noob about android modding and stuff.
Anyway I wanted to root my phone, just to stream some music to my stereo system. How naive I was...
So I unlocked the bootloader, installed twrp with adb and SuperSU with twrp. Everything was fine and phone was rooted but my past naive me thought "well let's try a custom rom, why not". So I went forth and downloaded some stuff from getdroidtips and what I understood is that all I needed to do was to do a wipe, then install the zip file via twrp. I did that and didn't work. After that I realized I made a crucial mistake: I didn't backup my phone from twrp, so I was there with no OS, quite panicked and frustrated. So I tried some other roms, finally I got one that worked, this: https://forum.xda-developers.com/honor-7x/development/openkirin-aosp-8-0-honor-7x-t3746257
It works but it's barebones and on boot it shows a message: "There's an internal problem with your device. Contact your manifacturer for details.". So, I tried recovering from HiSuite, recovery mode etc but nothing worked, I reinstalled SuperSU in the new OS via twrp to see if that would help somehow, but no. in the end I had the even more naive thought that maybe unrooting would allow me to repair via hi suite or something, so I mindlessly selected "complete unroot" on the SuperSU app, and this was the second big mistake, the process somehow ****ed up the twrp install and it no longer works. Instead, if I try to enter twrp with power button + volume up button, it shows the regular "your phone has been unlocked" screen and then comes up for a split second a black screen with, on the bottom half of the screen the "no command" logo, under it some lines of code that I can't read. It suddenly disappears and sometimes enters in a bootloop showing this screen and powering off every time.
If I keep power button pressed bootloop ends and the phone boots "regularly" in the openkirin OS.
I tried reinstalling twrp the same way I did the first time. No error on adb but same no command behaviour
So what I got now is:
kind of bootlooping no command window
openkirin OS with internal problem message
fastboot and rescue mode
it seems to work on adb (everything is fine if I type adb devices)
not working HiSuite recovery
not working Huawei eRecovery
not working download mode (I guess? the power+volume up+volume down combination)
Maybe I should mention I also did a data wipe (?? the option on the right next to "advanced wipe" in the Wipe screen, if I remember correctly) in twrp before installing openkirin, it was suggested on a yt video about how to install openkirin. And that, at a stage I tried using MultiTool but it gives me an error: "exception during a web client request. Error#9", while at the bottom left it says "downloading AdbWinUsbApi.dll..."
Sorry for the general noobishness and the bad english that might be there.
So, any tips for bringing back the phone to normal? Or at least repair twrp??
Please help, I hate needing to throw this phone away just because I wanted to stream some music and because of a couple of stupid errors
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
sdivk said:
Sorry for not answering earlier. It seems, between TWRP and stock recovery, you have messed up I think. When there is no proper recovery it become difficult to bring back the phone. You should try to put it in fastboot mode first, by powering off, pressing the volume lower button and connecting it to computer. Try installing TWRP and flash a custom rom other than openkirin from there if possible. Fastboot is the choice to go if recovery is messed up.
Click to expand...
Click to collapse
No worries, I managed to fix it anyway. Some things might be obvious but I'll share what I did nevertheless, in case some other newbie finds himself in a similar situation.
So there was seemingly no way of reinstalling twrp nor the stock recovery. But luck came my way and by almost random clicking I found out that, even if multitool closed as soon as I clicked the ok button in the error message, if I simply ignored the error, the program worked just fine (as I write this I installed another version and it gave no error message). So I played with it a bit and found out that it can flash twrp and it does not need a file from you, it already has a twrp version ready to install. I did that and it worked. It looks like the first twrp file I used didn't work anymore or was someway corrupted by the countless things I tried. So, with twrp working again I was able to backup the sloppy openkiring OS and try the unbrick tool. So I browsed the internet for a guide. Guides always mention as the first step for unbricking using the VENDOR.img file located inside a full stock rom. Problem is, 99% of the times they provide a rom without the needed file. So after some tries I found a good complete stock rom with the VENDOR.img here: drive.google.com/file/d/1tjHefytEWbpuV1f4YjX8AaSMzT6jr8TQ/view but I can't remember which forum/site I found it in.
I followed the guide which involves:
-extracting the UPDATE.APP file contained in the provided zip with huawei extractor tool into an X folder on your pc
-copying the VENDOR.img file contained in the X folder, on the root folder of the sd card
-backing up OS (if there's any) via twrp (I had something like 50 partitions, I guess that was messing things up a bit, but for safety I backed them all up)
-doing an advanced wipe from twrp selecting ALL checkboxes BESIDES the SDcard of course
-flashing the vendor.img file via twrp selecting the "Vendor" partition when prompted
-downloading the update_full_[your model]_hw_[your region].zip file, in my case update_full_BND-L21C_hw_eu.zip
-extracting the UPDATE.APP file contained in update_full_BND-L21C_hw_eu.zip with Huawei extractor tool in some other folder Y
-looking for a file named cust.img/CUST.img/version.img/other_name.img (I don't know which other names it can have, I was lucky and had a VERSION.img file in it)
-rename the cust.img/CUST.img/version.img/other_name.img to CUST.img and copy it from the Y folder to the X folder
-boot your phone into fastboot mode
-connect phone to multitool via usb and select the "unbrick" tab
-there, Multitool asks for a folder, give it the X folder. There are some checkmarks on the Multitool "unbrick" page. 4/5 of them should become checked after the folder input. In my case the first 4
-then, simply press the unbrick button
-wait and pray (it can look like it freezes while it's copying the system.img file but wait, it'll be fine)
So I did that and it worked flawlessly, the phone booted slowly but surely into EMUI 5.1 with Android 7.0 I think and everything was fine.
At that point I had a working OS and a working twrp but wanted to go back to the OS I was used to, Android 8.something so, I tried connecting the thing to HiSuite and it automatically asked if I wanted to update, not to 8.something but to 9.1. I thought "SURE I DO!" and updated flawlessly (I thought 9.1 hadn't even been released here in Italy).
When it booted I found out the new OS was working like an antivirusless xp pc: it didn't recognise the SIM, it would crash every 20 seconds, app downloads got stuck at 99%, if it felt like it, it rebooted, pc connection was not stable. Besides, the update being "official" and installed from "trusted" sources (HiSuite), it completely wiped twrp.
And that was the "OH ****, here we go again" moment: no twrp and worse-than-ever-working OS.
So because of the new EMUI version, I guess, Multitool kept recognizing the phone but stopped offering its own recovery, eRecovery, twrp files available for flashing. I was completely frustrated with all of this and decided to give up, but I made the last effort: I tried the relock function in multitool. So I provided the key, pressed relock, waited, prayed, and finally cheered. It worked like a charm. Phone runs now on EMUI 9.1 with locked bootloader without problems. Finally
So I guess in the end I payed 4 euros for a nice update, a painful and frustrating trip into android modding and a lesson : never do android modding!
no, just kidding, don't do it just if you are a newbie AND you don't want to risk to throw the phone in the grabage.
In all other cases consider it carefully
Oh, and also, God bless the MT Team and Russia altogether!! thanks
Quite an experience. All the best. ?
Lol sounds fun. I've bricked my Huawei Mate SE/Honor 7x more times than I can count. I'm just awaiting my 9.1. I want my GPU Turbo! Is it as good as it's supposed to be?
I'm about 4 hours of reading in on this matter, and I still don't have a proper answer. I've run through countless threads with similar titles, and found some helpful tidbits, but nothing the resolves or fully explains what is going on here.
I just made the jump from Android 9.0.0 (latest) rooted to Android 10.0.0 (latest.) Here were my steps:
Download the latest Platform Tools & unzip
Download the latest Android 10.0.0 Factory image for Pixel 2 XL & unzip into the platform tools folder
Download the latest USB drivers & install
Hook up my phone to the computer (Windows 10) and verify that ADB & Fastboot are working properly via command prompt
Execute the flash-all.bat (left the -w flag in so that it wiped my data) -- it appeared to be only flashing the one slot except for a couple mentions of the other slot's system towards the end of the commands
The phone booted just fine and I went through and installed TWRP and Magisk 23 and so on
Here's where I encountered the error:
As I was rebooting out of TWRP, I realized I'd never used the "Slot A" or "Slot B" buttons, so I picked one, and it started rebooting the phone. The normal screen with the yellow text about phone being unlocked came up, then switched to the white background with the 'G' as expected. The expected next step would've been the 'G' spinning into a circle for a second, and then going to the homescreen, but instead what happened was the screen went black, and then a screen that said "Your device is corrupt. It can't be trusted and may not work properly." showed. It looked similar to the one when the phone first boots with the yellow text about the bootloader, but this text was red. I attempted to use the power button to bypass it, and when I did, it switched the the normal yellow-text-about-bootloader screen, and then switched to the 'G' with the white background again, but there it stayed, just frozen.
I was still able to boot to bootloader by using the power + down button, and could then boot to the stock recovery, but that was it. After a bit of reading, I discovered the following command:
fastboot set_active a
or
fastboot set_active b
and also fastboot getvar all
The set_active command chooses which Slot is being used, and the getvar command shows all the fastboot variables, one of which shows the "current_slot." Once I set the other Slot to be the active one and rebooted, the phone booted normally. Buuut, now I'm concerned that someone is screwed up with my phone, and it's going to fail at some point when I don't have my computer handy, so I went back to work trying to resolve the error when I booted out of the one slot.
Here's what I've tried:
Run the flash-all.bat file in one slot, let the phone reboot, boot to bootloader, switch slots, reboot to bootloader, flash-all.bat in the other slot.
Same as above, but without the -w flag.
Manually flash the bootloader, radio and image zip on both slots
Install the TWRP while booted into the adb-loaded TWRP img (this seems to write to both slots based on the output)
Install and uninstall Magisk both via recovery and via the patched stock boot image.
After every single attempt, the one slot would work just fine, and the other slot would exhibit the behavior I mentioned. Depending on which Slot is flashed first, the Slot that fails to boot properly does change (ie. it's not always Slot A or Slot B that fails.)
Untested methods:
Screwing with dm-verity -- I saw one thread that gave a few fastboot commands to disable dm-verity, and a couple people reporting success with it. After searching around and doing a bit of reading on dm-verity, I still don't understand what it does, whether disabling it would have any negative repercussions, and whether disabling it would fix the issue legitimately, or just kinda mute it.
Using Deuce's bootloop recovery tool -- again, I don't really know what that thing is running, it hasn't been maintained in quite some time as far as I can tell, and there are several threads indicating that it runs a bunch of haphazard stuff that could cause more problems. Some reports indicated it worked for them, but I'm concerned about what else it might be doing that may negatively affect things down the road.
Re-locking the bootloader -- I saw this one mentioned several times, but I also saw several people warning that you could brick your phone if you do it wrong. I also saw one or two folks who seemed like they couldn't get back to being unlocked after re-locking. I don't want to screw with this option given those risks.
Can anyone give me any more tips on how to resolve this? I'm pretty sure that the Pixels are supposed to run equally well from both slots, so I'd really like to get the matter resolved so I don't have to worry about what would happen if my phone moved me over to the other Slot for some reason. Any insight and explanations are appreciated!
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
runekock said:
People say that you cannot install both TWRP and magisk (I haven't tried it myself). So start again with a flash-all, and then, instead of installing TWRP, run it using fastboot boot whenever you need it.
Click to expand...
Click to collapse
The problem presents with even the stock boot image though.
Strephon Alkhalikoi said:
The OP needs to flash a factory image first or the corruption message will never disappear. While he's at it he should make the jump to Android 11...latest radios and all that. If he doesn't want to lose data he can edit flash-all.bat in the factory image and remove the -w flag in that batch file.
From there he can flash anything he wants. If he plans on rooting however he cannot install TWRP, only boot it using ADB. The combination of Magisk and TWRP causes a bootloop.
Click to expand...
Click to collapse
Understood on the magisk / twrp thing, but regarding the factory image, that is exactly what I was going. The problem presents even after doing that. That's why it's so puzzling.
Edit: it's admittedly a very long post, but if you look at the section that's numbered, you'll see I'm grabbing the latest factory image for Android 10 and flashing it. Then in the section labeled "Here's What I've Tried" (aka my attempts to troubleshoot) the very first thing I did was flash the factory image (including the wipe) to both Slots and then trying to boot from one slot and then from the other.
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Strephon Alkhalikoi said:
Grab an Android 11 package and don't remove the -w flag when installing. The corruption may be persisting because user storage isn't being wiped.
The factory image - NOT OTA - is the only way to fix this short of sending the device to Google for service.
Click to expand...
Click to collapse
Why would it be any different when I wipe with Android 10 or Android 11? I flashed the latest Android 10 factory image to the phone *with* the -w flag as mentioned in my "here's what I tried" section. I even went so far as to force the phone to Slot A with the "set_active" command, and then set_active Slot B and flashed the factory image (not the OTA) again. After doing that, the one slot will boot just fine while the other gives the error. If I change it up and flash Slot B first and then Slot A the same thing occurs, just in reverse (the slot that booted before throws the error while the slot that threw the error before now boots.)
My initial post explains why I recommended an Android 11 ROM (updated radio). Any of them will of course work, but that's beside the point. Try using ADB to format the partitions and see if that resolves the issue. Otherwise contact Google, as I can't think of anything else that would be blocking you.
I had this same issue and Flashing Android 11 on both partitions (without removing the -w command) resolved it.
I first booted into Recovery Menu and wiped both slots. Then downloaded the factory image (not ota) and flashed each slot separately wiping the device after each flash in recovery menu. it's the only way to fix this just like user @Strephon Alkhalikoi
If that doesn't resolve it then you have an issue that's more serious and will require a repair of some sort (not necessarily hardware).