Develop Bugs

Unable to wipe encrypted GN

Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!

Flash stock images through fast boot?
Sent from my Galaxy Nexus using xda premium

I've just been reading up on fastboot since posting (I think I've only ever used it via other people's scripts before), and assuming that it can overcome the problem, I was thinking that maybe it would be able to do the wipe (though obviously I don't want to end up with a £500 paperweight...)
If I were to flash a stock image, how would I go about that? (It's been a long time since I've loaded a rom not via a recovery)
EDIT: Going to try a manual nandroid restore (from a backup made just before encrypting) as described here - http://wiki.cyanogenmod.com/wiki/Fastboot

Ok, flashed a stock image and back to factory state again so now all working (phew) - thankful I was doing this on a Nexus device where fastboot was easily available.
While this has solved the problem, it didn't really identify the cause - I'd be curious to hear of others' experiences with using the encryption in 3.0+.

Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d

jayharper08 said:
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
Click to expand...
Click to collapse
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).

Don Vincenzo said:
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Click to expand...
Click to collapse
No worries. Dev section is just for strictly developed roms and kernels and such. No biggie
Wish I could help you with the answer though :/
Sent from the MIUI powered 3d

Don Vincenzo said:
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Click to expand...
Click to collapse
just connect via adb in recovery and format it via mkfs.ext4...

and... then what? Once the partition is formatted - it seems it would need to be populated? Or does some subsequent restoration - once the /data partition is accessible - will re-create any files / folder structure in this filesystem?

Won't boot, can't mount sdcard

Hello,
First of all, I feel like an idiot right now, and I most probably am. I'm using a HTC One X from ROGERS. Here's the whole story:
1) I unlocked the bootloader succesfully
2) I rooted my phone via a superboot script or something like that
Note: At this point the phone was working perfectly and I stayed that way for 3-4 days.
3) I finally found a working CWM recovery image for the One X from Rogers
4) I flashed it and was able to enter CWM Recovery
5) Following the thread on Android Revolution that's around on these forum, I downloaded something called Super Wipe and the ROM itself
6) When trying to "install" Super Wipe from within CWM Recovery, it kept giving me an error with Status 0
7) Got tired trying stuff so I did Wiped data/cache/Delvin (however it is spelled) cache/battery stats/everything I could wipe
8) Tried again, still didn't work
9) This time -and here is where I think I massively screwed up- I decided I'd try the format options, so I formatted cache, data, sdcard and system.
10) At this point I noticed the phone wouldn't boot anymore, I'd just get the "This build is for development purposes blah blah blah" and it would loop on that forever
11) Going back into CWM recovery, I now noticed that the sdcard was unmounted, when I tried remounting it, it would give me an error message saying E:Can't mount \sdcard (or was it "Error mounting \sdcard"? Not so sure anymore)
12) Tried re-locking and re-unlocking the boot loader, didn't work
So now here I am, phone won't boot, will just loop, and I can't mount the (internal?) sdcard anymore, actually I never really noticed if it was mountable, but I assume it was since I recall being able to complete the wipe everything operation in CWM recovery.
Is there anything I can do? I've heard of a few options, namely installing the RUU or something like that and a software called Odin which after searching a bit I believe is only for Samsung devices. The thing with the RUU is that I have a Rogers handset, and I don't think the RUU for that one is available. Also, is there any way I can access the internal sdcard on my PC while the phone is in the bootloader or CWM recovery? Maybe I'd be able to do something that way...
Also, I bought with the 3-years contract from Future Shop 5 days ago, think I can just go back and say "Hey, the phone crapped up" and expect them to change it without inspecting it too much to notice the **Tampered** **Unlocked** tags in my bootloader?

Also stuck at kindleFire screen.

I really, REALLY have tried going through the threads and tried to figure this out on my own but I'm just stuck. A while back I got stuck in the boot loop (I guess). It was after a few factory resets. It had been rooted. Now, I can get into twrp but once there I can't seem to find any of the files that I need to flash to get it going again. When I launch the KFU it says the device is "online" and device manager reads "Android Composite ADB Interface". I'm sorry if this isn't enough info but can someone give me a push in the right direction? :silly:

Still vague bro but hey you have twrp do you have fff? If you have those things select mount in twrp transfer ROM zip and a gapps zip to your sdcard but don't place them inside a folder... leave them in the open this is considered the root of your sdcard then select unmount go to install see if you can navigate to the files you put on the kindle if so select wipe, wipe factory reset, wipe cache wipe dalvik, wipe system, select install tap on the ROM zip flash it when done use the back button upper right... flash gapps then select reboot and system if prompted let it boot.. I suggest this ROM or a cm7 flavored variety.. http://forum.xda-developers.com/showthread.php?t=1778010

fff is the kindle logo with the blue (fire) lettering, right? v1.4a in the upper right corner. Let's me go into normal, recovery and reset boot mode? The only option that let's me make any progress is the recovery option and that loads me into twrp. The "mount" option in twrp gives me 4 choices, mount system, mount data, unmount cache, and unmount sdCard. Mount system and mount data are unchecked. And if I click the "mount usb storage" button it takes me to a screen that says "USB Storage Mounted -- Be sure to safely remove your device from your computer before unmounting!" and there's an "unmount" button underneath. That's all I'm seeing. I'm not trying to be vague. I just don't know what specifically is the relevant info to give. But thanks for helping out those who can't help themselves

Ok plug to your computer select mount make sure there are no checks in the boxes of data and system then hit the big button this will mount your sdcard transfer zips select unmount follow my instructions above...

hey man, it worked!:victory: But I'm sure you knew it would. So, is it a bad idea or is it even possible at this point to revert to the factory reset? You know, have it be totally stock? And is it just tricky or dangerous to do factory resets a few times? I like using just the stock kindle version. The kindle app is just a little funky. Or it was the last time I used it. But obviously I love the google suite. I hadn't made a back-up the last time because it was just as easy to download a few of the things at a time from the cloud. So, making a back up would be a good habit and help in a situation like this? Do you know of any good threads re: backups? And superuser is something I don't know anything about but how does it work and where should I learn more about that? Mega MEGA thanks again dude! :highfive:

Yeah if you want the best of both worlds go with rooted stock all the wipes I suggested after backing up first then flash this http://forum.xda-developers.com/showthread.php?t=1439916 the standard version not the altrom thats for dualboot your miles from that

What's the process to get to rooted stock? I just made a back up

akaFoxMulder said:
What's the process to get to rooted stock? I just made a back up
Click to expand...
Click to collapse
just put this on your sdcard wipe every thing but your external storage and flash it http://loadbalancing.modaco.com/dow...gned-MD5-569fe6550cfcfba68dabc3d088324a46.zip your external storage is your sd card you dont wanna wipe that
its nothing but rooted stock with playstore and it wont wipe out your recovery and fff in the process

when installing the modaco custom rom, what boxes do I want to have checked? Zip file sig is checked by default and Force MD5 check on all zips is unchecked. Good?

akaFoxMulder said:
when installing the modaco custom rom, what boxes do I want to have checked? Zip file sig is checked by default and Force MD5 check on all zips is unchecked. Good?
Click to expand...
Click to collapse
Just leave them all unchecked

thanks again for all your help thePooch. I've tried installing the rom a couple of times and it either freezes or I've got the following message.
Writing Data - Writing System - Writing Boot then E:Error in /sdcard/Gr9.2-altrom-update-.....
(Status 0)
*Verifying filesystems...
*verifying partition sizes...
Error flashing zip ‘/sdcard/Gr9.2xxx
do I need to just stay with the cm10 rom at this point? what other kind of fun stuff can I do to get this working:fingers-crossed:

I believe Thepooch told you earlier NOT to download the altrom. Check your download and try again.

no doubt. Funny how this stuff works the way that it's supposed to

soupmagnet said:
I believe Thepooch told you earlier NOT to download the altrom. Check your download and try again.
Click to expand...
Click to collapse
Thanks soupmagnet yes the altrom version will fail everytime because it needs extra partitions to work which do not and very likely will not ever exist on your device.... Intructions well it helps if they are read I gave very clear ones and I definatly said not to use the altrom........

ありがとうございました。 I think I'm done.

your welcome

[STOCK ROM][PERRY][MetroPCS.XT1765]A8M'S XT1765 STOCK ROM April 14th, 2018

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

Lenovo P2 (P2a42) stuck mostly on blue logo screen

Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.

NickSergeant said:
Hello --
I found this very nice looking phone thrown away in a bin and I guess this problem was the reason.
It would be great to get it going maybe even worth paying to get it running.
But I would appreciate any suggestions on how to do it myself.
I am not familiar with a lot of the in-depth hacks people do with phones. Words like "flash" and "ROM" are foreign to me.
But I like to try to fix things.
I have tried a few simple actions to get the phone going but it still does only three main things:
1. Shows the "Lenovo powered by Android" screen of course.
2. Volume down + Power: shows Fastboot screen with just three options: Start, Barcodes, Power off
3. Occasionally, some buttons I push get to Teamwin Recovery Project. But I do not exactly know how it happens and it is hard to repeat. It seems to come up after trying everything and then putting the phone down.
From TWRP I have selected these options:
-- Factory reset
-- Restore (I think) -- I selected just a single item displayed available for restore
-- Wiped Delvik cache and format cache
-- Reboot
I also downloaded ADB and installed it. Instructions I read said to run an .exe file but all I could find was .bat so I clicked on it and saw the RUN screen open briefly then close.
Thank you.
Click to expand...
Click to collapse
YOU CAN CHECK IN MY SIGNATURE FOR ALL BASIC TERMS USED IN FLASHING.
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
If you have TWRP installed , you can update TWRP and then flash a custom rom. You can hold both volume up and down and power key to boot into TWRP when phone is switched off.
Remember new custom roms need newer version of TWRP.
What you'll need to do is download a custom rom like say Havoc OS Android 10 (just search it in the forum), you will need to upgrade your TWRP.
Once this is done, you will download Havoc OS Rom and put it in your phone or sd card
You just do a factory reset and then format only system . Don't format other partitions in TWRP.
Install that room and then you will also need to install gapps. (Google open gapps , chose Android 10 version and architect as 64bit and choose nano or pico gapps)
So in your sd card, you must have rom and gapps.
Once you install rom first and then gapps, restart. If it comes with an error, it means your TWRP needs update.
To update you will choose to download TWRP (zip format will install directly while IMG format can be flashed as well by choosing install IMG while you select install in your TWRP.
Restore is only available if you already made a backup with your TWRP .
I will suggest to make a full backup (except system and data ) in TWRP before you do the above.
I will also suggest you to Google if you are not sure. Make sure to follow instructions only from XDA as they are most reliable than other sources.
Watching YouTube videos may help you as well
In short:
Update TWRP
Download Havoc Rom and Gapps pico
Put them in your sd card
Install them in this order rom and then gapps.
Restart.
If you still feel you need help, please quote me for an answer
All the best .

Hnk1 said:
Look here if you want to return to offical stock Rom
https://forum.xda-developers.com/lenovo-p2/development/fastboot-files-stock-firmware-t3649914/amp/
Click to expand...
Click to collapse
Thank you for this advice -- it worked! Finally the phone gets past the logon and is operating.
Now I have a further problem and please let me know if you think this should be a new thread for this.
I cannot sign in to Google because of anti-theft feature -- instead I get this.
“This device was reset. To continue, sign in with a Google Account that was previously synced on this device”
I see a few solutions online but not exactly for Lenovo. What would you recommend?

I'm on the same boat as Nick. Do we have to wait 15 days to unlock the bootloader? Just coz it'll be hard to be 15 days without a phone and everything wiped out. I wanna try Syberia 2.9 as the last LineageOS is not ready yet. Thank you very much.