Related
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
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.
My phone's bootloader is locked, never messed with it at all.
So about a week ago I get a prompt on my One M9 for an update. I download it without problem, however while installing it gets stuck at 25%, and gives me a red ! in a triangle, then it reboots. I try to redownload a couple times with no luck. For a couple days I just click don't install after it downloads (why isn't there an option to just not download from the start?) and finally I try it again on Friday morning. This time the HTC One splash screen comes up, and it freezes. I research for a couple hours with no luck. I have a wedding out of town I need to go to, so I decide to wait until I'm back home today to work on it some more.
Today I get back home about 6 hours ago and all I'm trying to do is recover my data, specifically pictures from my wedding. I thought I had it set to auto backup, but I guess that was my One M8 I did that to. I look into TWRP, which won't work because of the locked bootloader, various programs to recover data that won't even work on old phones that I have, as well as "adb -d pull sdcard/ C:\RecoveredData". When I attempt to do that it gives me the error: closed, even though when I type in ADB devices, my phone shows up, although it says sideload next to the SN. I looked up how to fix the error: closed (update adb.exe), but I get the same result, or it freezes (I've left it up for awhile just to make sure it wasn't copying the files)
The only way I can get the ADB commands to work is if I go into the Android Recovery and select "Apply update from ADB". I'm wondering if that is why it says sideload next to my phones SN and why I can't pull the files off of the phone.
I'm wondering if I apply the update that the phone was trying to get via ADB, if that would allow my to keep my current data. Looking at the page
ok, so I can't post URL, but if you google "Flashing a stock Android image without wiping user data", its the first post.
It appears that I should be able to. My problem is that I'm terrified of wiping my pictures out if I do it incorrectly.
I'm on Sprint, and the newest version is 3.41.651.13. I'm pretty sure my phone had 3.41.651.4
I just want to make sure that if I follow that post, with the correct files from sprint, that it would work.
Any help at all would be wonderful.
Edit: I did have USB debugging active before all this happened as well
If I was to install the current version of the OTA on my phone via ADB would that work to get it up and running again? That way I the image would match what the phone is looking for since I can't update it because the bootloader is locked.
NGalaxyTimmyo said:
If I was to install the current version of the OTA on my phone via ADB would that work to get it up and running again? That way I the image would match what the phone is looking for since I can't update it because the bootloader is locked.
Click to expand...
Click to collapse
flashing stockrom should not wipe internal sd-card
can you connect via adb? (if the phone is in recovery mode)
The only way I seem to be able to flash anything is through the adb menu. I found the current update, but because I can't flash the system img files due to it being locked, it fails at around 47%.
I've been looking for the current version for a few days now with little luck.
When I type adb devices, the serial number comes up, with sideload next to it. I'm assuming if I find the right files it'll work
Hi.
Apologies if this is a very naive question, I am not particularly familiar with mods, roms and so forth.
I have rooted another phone in the past, but that is all.
The situation:
- Samsung Galaxy Nexus
- Not rooted/unlocked. Stock android automatically updated to the latest Android version supported
- Android developer option NOT set in settings
- Stuck in a boot loop: boots to android and then after a few seconds reboots, so no time to do anything
- Not sure how it happened, I had it for years, it was in my pocket and suddenly started doing that.
- Android fastboot and recovery loads up no problem
- I have tried anything I could find online to fix it: deleted cache, rebooted in safe mode, removed battery for 10 hours
- Nothing seems to fix it, it keeps rebooting
- I want to try a factory reset, but my family photos are in the phone
- Google synch seems to have stopped functioning for this device a year ago, all my 2016-17 photos and videos are locked in the phone.
Admitting there is nothing to do about the loop problem:
Is there any way I can copy photos and videos via usb while in recovery mode?
After I will reset the phone via recovery menu, hoping it will fix it. IF that does not fix it, I will flash another rom in. But I really do not want to wipe my data before backing them up.
I am assuming the answer is no, you cannot access the internal memory in fastboot/recovery unless your phone is rooted.
But I would like an expert opinion before I resolve to wipe one year of photos and videos which I will regret losing.
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
____Mdd said:
@mcaldo DON'T DO FACTORY RESET, EVERYTHING WILL BE LOST
which recovery are you using..?
if it's TWRP, then it's easy..
- boot into TWRP recovery
- go to "Mount" tab
- find "enable/disable MTP" button at lower options.. (enable it )
then connect your phone to that PC, where you always connected in past, ( to eliminate driver installation stage, all drivers will be preinstalled )
Regards
Click to expand...
Click to collapse
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
mcaldo said:
Thanks for your reply!
By recovery, I meant 'android system recovery'
It gives me the following options:
reboot system now
apply update from ADB
apply update from USB drive
wipe data/factory reset
wipe cache partition
Is any of the above useful?
Unfortunately, I do not have any alternative recovery software available
Edit: Googling I found this: "Apply update from ADB: The Android Debug Bridge allows you to plug your device into your PC and issue commands from there. "
If I can issue commands through ADB, perhaps there is a command to copy data from my phone to my computer?
Click to expand...
Click to collapse
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
____Mdd said:
Yes, you can copy through adb commands..
Get and extract Minimal ADB and Fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
From PC, run CMD to extracted folder directory.
Connect phone to PC, go to update from ADB(in recovery),
Type "adb device" , it will show serial number and connected..
Then "adb pull /sdcard " (if you know particular directory of data then write it like /sdcard/photos,, otherwise writing /sdcard will copy all folders from your phone. )
it will start copying to same adb folder ..
Click to expand...
Click to collapse
Thanks for the advice.
I followed the instructions closely, and nearly got there.
adb devices returns
#serialnumber sideload
so all good
but adb pull /sdcard returns
adb: error connect failed: closed
I tried several other commands with no success
kill-server and start-server work fine but do not solve the problem
adb usb returns
error closed
So, I am starting thinking that the problem is in the bootloader being locked.
However, if I unlock it, it will be wipe all my data, I understand?
Googling about it, I found this:
The behavior is status-by-design. Your stock recovery is not designed to grant shell access. Your only choice here is to somehow manage to flash a custom recovery. – Firelord Dec 30 '15 at 14:19
3
To achieve something similar to what @FireLord suggested: TWRP can be booted on many devices without being installed. For that, find a matching image, then boot to the bootloader and run fastboot boot twrp.img. Btw: you can check with fastboot devices resp. adb devices whether a device is visible to the corresponding tool. – Izzy♦ Jul 8 '16 at 19:40
So I understand one could boot TWRP without installing it, but I am not sure if that means I could do that with the bootloader locked?
I found WugFresh nexus root toolkit which seems to do that, among many other things, but again it warns that the phone must be unlocked (using the android build "Android *.* Any", I did not know what else to choose, not sure if that makes any difference as for locked/unlocked requirements)
EDIT: my fastboot screen reads "FASTBOOT STATUS - Failbootloader locked" as the last line, when trying to run TWRP without installing.
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
____Mdd said:
Yes, unlocking bootloader will wipe everything..
What actually you did ? Why it went into bootloop ???
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex.
Click to expand...
Click to collapse
What actually you did ? Why it went into bootloop ???
Click to expand...
Click to collapse
A very good question, to which I have no answer, unfortunately.
The phone was used by my wife for 2 years and then by me for other 2. I recently changed the battery.
Never rooted or unlocked. No unusual apps installed. I am a very basic user, as you might have guessed, and being my only phone at the moment, I really would not risk experimenting with it.
It went very slow over the last 4 months, so I was planning to reset it.
I put in my coat pocket for a few hours, when I took it out it had a train ticked stuck to the screen and was quite warm and on the lock screen. It froze, so I took the battery out and restarted it. From then on it is stuck in a loop, not sure why really.
I have also read that about boot into TWRP without installing.. and it worked for many one without unlocking bootloader... Don't know why not on GNex
Click to expand...
Click to collapse
That's good to know. I'll research more than.
It seems there might be a problem with the fastboot drivers on my computer, even selecting them from device manager did not work. Win7 refuses to install. The ADB drivers in theory work fine though.
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
____Mdd said:
If you have done nothing modification to system, then wiping data should work, but i have doubt if it also wipes personal data too, on TWRP it wipes data excepting /data/media/ which contains all personal data.. but don't know about wiping on stock recovery...
I hope you will find solution as soon as possible..
Regards.
PS. I can install stock recovery and try wiping /data.. and check what things get wiped.. but i need little time for that experiment...
Click to expand...
Click to collapse
Thanks so much.
Looking at google's documentation on the nexus:
You can remove data from your Pixel phone or Nexus device by resetting it to factory settings. Resetting to factory settings is also known as formatting the device or doing a "hard reset".
If you're factory resetting your device to fix an issue, make sure that you've tried all other troubleshooting options first. Find out how to troubleshoot your issue.
Important: Performing a factory reset will erase all data from the device.
Click to expand...
Click to collapse
It would seem that indeed all data will be removed.
This point, I will research a bit more into drivers, in case that is what it's preventing adb pull from working.
I really need a working phone, so if that fails I will hard reset, then unlock, root, flash in an alternative bootloader and perhaps a rom, and put ubuntu touch in dual boot. That will hopefully prevent me from loosing data in the future.
Sorry, this is out of topic to my question, but, , could you suggest any stable, solid rom for the nexus?
I read good things of CM12, and I ran into one which seemed to do to quite well with split windows, but I do not remember the name right now.
EDIT: I remember the name of the rom now, it's https://omnirom.org/about/
A last question if you can..
I tried to solve my boot loop problem by sideloading an update from google (maguro yakju yakju-jwr66y-factory-4cadea65.zip)
It loaded it fine but then failed because the installation it says it is not signed.
Basically, being a stock bootloader recovery from Samsung, it will only sideload OTAs from samsung, not the stock ones from google..
I cannot find the samsung ones anywhere, not for the nexus anyway, just the newer devices..
By any chance do you know where I could download proper Samsung OTA zip updates for the nexus?
Well, I talked with an android developer who confirmed that, unless you have a friend working in criminal forensic technology or similar, there is no way to get around a lock on this phone to pull data out.
So, sadly, I have wiped my phone by unlocking it, flashed TWRP and then omnirom with gapps.
My photos are gone, including a bunch of stuff my kid had made and asked me to photograph for safeeping. Very safe indeed
He kept asking me why they make the lock like that, instead of allowing some kind of password, perhaps he has a point.
So, it is quite unlikely that somebody who knows as little as I did will ever read this *before* finding themselves in the same situation.
But if you do, back up your data, unlock and flash TWRP, clockworks or some alternative, and thank yourself if and when disaster strikes..
@mcaldo wiping data/factory reset in STOCK RECOvERY will wipe everything... There is very few chances to get backup...
And yeah i found something interesting..
You can flash system.img.. only system files will be corrected not anything else..
Get appropriate zip from here : https://developers.google.com/android/images
Now take system.img to ADB/Fastboot folder ( i assume you know how it works )
Just go "Fastboot flash system system.img"
It will rewrite system partition..
Another one:
See downloads on this thread..
One says NON-WIPE, if you want me to try that zip, i will again require time for that. See here : https://forum.xda-developers.com/galaxy-nexus/general/guide-restore-to-stock-unbrick-galaxy-t2065470
---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------
I don't saw your reply, it was on next page.. its sad... Sorry i am late..
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