Develop Bugs

Boot Loop stuck in Animation help.

Hey everyone. I know there are already a few threads with boot loop animations, and am having difficulties finding the same situation as what I'm going through. Here is what the phone used to have before it randomly started looping:
Rooted - with Stock rom, using ClockwordMod Recovery 5.5.0.2
Used Go Launcher Theme ( if that even matters )
No additional roms installed or anything, the phone is 3 months old.
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Here's what screens I can get to:
1. Hold vol up/down while holding power ( the little android with its belly open, and the options Start - Restart Bootloader - Recovery mode - Power Off )
2. Hold vol down - ODIN mode, with the START option only
I can access WMD recovery and factory reset, Try to install my old backup, nothing works at all in that area, no matter what I do.
Can someone advise me a step by step way of getting my computer to recognize my phone, so that I am able to do fastboot, or reflash, or anything to get my phone working again. I can't access my internal memory at all.
It's even possible that I've read too much, and my frustration is getting in the way, if so I apologize! Some guidance would be greatly appreciated!
Thanks in advance of course! I need my phone for business!
Cheers,

Install the drivers on a computer then use fastboot oem unlock. Or just factory reset it from within recovery.
Sent from my Galaxy Nexus using Tapatalk 2 Beta-4

Try my siggy.
I'm not sure about the exact error:
But the link there will get you the correct drivers.
Also, as stated...try to factory reset.
You'll lose your apps/data that way though =/
Hopefully you can get the driver installed and get your computer to recognize.
If so, follow this to back up your apps:
http://forum.xda-developers.com/showthread.php?t=1420351

Have exactly the same setup as you (rooted/stock/CWM) and had the animation bootloop - animation would just loop until a battery pull.
Only thing that solved it was a factory reset from recovery. Been working fine for the 4 weeks since. No need for any reflashing etc. Titanium recoveries have all worked fine as well. Didn't try my Nandroid backup as I thought that may still have the 'fault' built in.

I had a boot loop for every from I tried to flash...wat fixed it was before flashing u need to wipe system data and wipe the cache in the recovery...ie a clean install...then every rom I tried worked...so I think ur missing that crucial step coz it worked for me
Sent from my Galaxy Nexus using Tapatalk

Hey guys, as stated above I've done numerous factory resets, it still seems to boot. I will for sure try to get the drivers installed so my phone is recongised by the computer, but would need step-by-step assistance when doing fastboot, or whatever the next step is.
Looking for more help though! Keep em coming!

?
Any other ideas?
Thanks!

Ok guys, so here's where I'm at now. I've used Jubakuba's sticky link, located here:
http://forum.xda-developers.com/showthread.php?t=1529058
Everything is able to be recognized up to the point where it says "Put the su.zip on your phone."
Since I cannot access my phone contents, since I keep getting this "Unable to open lunfile ( no such file or directory), it does not allow me to add anything to my phone.
I re-installed CWD as stated in the list of things to do, and all that went well. But I have the same issue, I tried factory resetting all that. erase cache, and still stuck with the same issue.
What's my next step now peeps? Looking for a quick answer as I have time to do it tonight!

Edit***
Just tried this trick: but it says it does not recognize the device?? what is going on! Please help someone! Thanks!
Panic Section! (Something is Wrong)
Q: My phone won't boot!
A: The easiest option is to get into recovery and restore a nandroid using the above guide (pull battery to put phone in an off-state if needed).
However, more advanced options are available if you don't have a nandroid available (You're naughty).
Do you have another rom .zip available on your SD card? If so, simply use the above guide for installing a rom to get you booting again.
If not, you can download one on your PC. Boot into fastboot (the green Android with open chest menu).
Move the .zip to the C:\android-sdk-windows\platform-tools folder.
Open ADB.
Change the NAMEOFZIP.zip below to the correct file name...and perform the action.

Surely your computer recognizes your phone. Otherwise how were you able to unlock the bootloader and flash the recovery?
And I've never seen that error message before. It doesn't even make any sense to me. Where are you seeing it? On your phone or on your computer? And in what context? What are you trying to do when it shows up?
If your phone isn't booting I'm not sure that you can copy any files to it yet. (Maybe you can use adb in clockworkmod? I'm not sure) What I do know you can do is flash the stock ROM and start over.
Download the image from Google here:
http://code.google.com/android/nexus/images.html
Here's a instructions for the GSM version:
http://forum.xda-developers.com/showthread.php?t=1366806
For the Verizon version, I can't find the thread at the moment but you just replace the filenames and also there's 2 radios to flash so:
fastboot flash radio *filename*
fastboot reboot-bootloader
fastboot flash radio-cmda *filename*

"Unable to open lunfile ( no such file or directory) appears on the phone, in CWD mode, when trying to attempt "mount Usb" to be able to access my internal storage .
I am attempting your thoughts right now.
I will post with results

Ok I tried to do this step. This is the outcome I received on the computer after even typing the first step:
'fastboot-windows' is not recognized as aninternal or external command, operable program or batch file.
A thing to stress, I'm not sure how to do step 1: 1) Take a Nandroid Backup if you have CWM installed.
EDIT***
GREAT NEWS!
used this setup!
http://android.modaco.com/topic/348161-01-feb-r4-superboot-rooting-the-gsm-lte-galaxy-nexus/
and it worked!
Thank you everyone! Going to play with my phone and make sure it all works!

Macinshak said:
Ok here is where I'm stuck. I understand I should reflash somethings like recovery image or something, but I'm stuck with one big problem. My computer and phone don't recognize using the USB mount.
The message I get is called "Unable to open lunfile ( no such file or directory)
Click to expand...
Click to collapse
the problem is when that happen?? when ur phone is booted and u plug the usb cable to ur pc? or when u are under recovery and want mount the usb mass storage? the second one doesn't work

[Q] Wildfire S [Marvelc] Stuck on opening update package

Hello all, for the past few days I have been trying to install android 4.0 ICS on my HTC Wildfire S CDMA phone, currently connected to youtube. on one instance I accidently formatted my backup so at this point im prettty scared.
I have already tried full resets, clearing memory, batttery, cache etc. I am stuck using CWM because TWRP touch screen doesnt seem to work at all. All help will be greatly appreciated. thank you.
I have also tried most of what is on other forums such as kernel update, redownloading.
I also find that if while installing, the phone restarts on its own. at first I thought the installation was done but to my dismay, it wasnt....

I'm not sure I can help but I would suggest you try to clarify what you are asking and trying to do. You state that you're doing an install of ICS 4.0 on your WFSc. I don't think any WFS, gsm or cdma got the ICS update unless you mean as Cyanogen Mod 9 or some other ROM? You also said something about being connected to You Tube now...that doesn't make sense.
That being said, if you meant you were trying to install the ICS theme then you might get a quicker more focused response if you posted in this forum:
http://forum.xda-developers.com/showthread.php?t=1504935

Clarification
I got a second wildfire s from my cousin. exact same model and was bought the exact time as my current one and it successfully installed the cynanogen 9 with the only failure being that the touchscreen is inoperable but I will work on that another time. also when I said connected to youtube, I meant I tried to look on youtube for fixes but never found one. anyway the main problem is that my phone stops midway through the "installin updates" to either freeze or restart to a blank operating system "meaning its stuck on the htc logo". I hope this clarifies what I was trying to convey in the previous post and I promise to keep a closer eye for any other messages. I also thank you for answering.

Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.

romemo two
MiCeltic said:
Instead of potentially aggravating you with 20 questions, I'll just briefly run thru the steps, FWIW. I see you mention CWM.
-So, you probably unlocked the booloader at HTC dev and are S-on.
-Installed CWM, so you have the adb files and htc sync on your computer.
-Rooted, although flashing CM will root.
-Battery charged.
-Downloaded the correct CM9 for your WFS, i.e., gsm or cdma, and moved it to your sd card after extracting the boot.img file and putting it into the folder on your computer with the adb, fastboot, etc. files for later.
-Booted into CWM and wiped the cache, dalvik-cache, and data/factory reset.
-Selected the CM9 file on your zip, and started the install.
I'm a little unsure what you are saying happens next, but normally you would:
-after CM9 is flashed go to fastboot in the bootloader or reboot into recovery>fastboot.
-Attach the USB cable from the computer to the phone and with the command prompt at that folder where you have those adb files type:
fastboot flash boot boot.img and press enter
-Then reboot and CM9 should load...unless now both of us have missed something ::yikes!::
For some reason most guides seem to skip that part about extracting the boot.img file and flashing it after the ROM install, which is needed if the phone is still S-on. Typically seen when stuck on the HTC logo after flashing the ROM and rebooting, and you mentioned being stuck on the HTC logo. If the phone is S-off, the boot.img gets flashed from within the ROM during the install.
Hope I found the missing step and that it installs successfully.
Click to expand...
Click to collapse
Thanks again for the reply. you have given me quite a lot of information and 90% of it was correct and dead on, but where you misunderstand is that while using CWM and flashing ANY Rom onto the phone, it either freezes at "installing updates" or restats if it ever gets to the next step. The confusing part of this is that the other phone which is the exact same model was able to be flashed with all the roms that I tried on my own phone with no problem.
To make things easier. after this I will adress the phones differently:
My phone (Not working Flash) is Marvelc 1
My cousins phone (working flash) is Marvelc 2

This is particularly challenging because you keep emphasizing that you are doing exactly what (you did?) on the other WFS, and I presume they have identical hboots (which they'd have to if you unlocked using htcdev). You also say that you re-downloaded the different files (recovery, CM9) and double checked that their for the MarvelC, and re-did then, re-tried, re-tried, re-tried...and I'm presuming that when you were re-trying that you didn't skip any steps, like the wipes. Oh, and most of all that everything worked on this phone before you started unlocking - flashing the recovery - and rooting. I thought about htc sync and adb, but the fail point is not when the computer is hooked up.
So all that being re-hashed, I'm looking for something concrete, a clue from what you've said or hinted at and right now I'm curious about your SD card. That is most likely not common to both phones and you did say, "on one instance I accidently formatted my backup..." Did you get everything formatted OK with no errors...that SD especially, as Fat32, shouldn't need an ext partition at this time. It could be corrupted and failing at some point when it's unpacking CM9, or whatever. You might re-do formatting that, including doing it on a computer if you have an adapter or a card reader, if not in CWM. It wouldn't hurt to put it in another phone and see if you can read it there and/or on a computer when that other phone is hooked up as a disk drive. Then put a fresh copy of whichever CM9 your flashing on it and try EVERYTHING one more time (back in your phone of course) ::haha:: be sure to leave the battery out for at least 30 sec. after all this and before trying the flash just to be sure any residual static in the phone has dissipated.
If it fails again, leave on and hook up to the computer and run: "adb logcat" from the prompt where you have your adb files and see if it will show you anything. You can exit logcat with the Ctrl + C keys. What do you think?
Oh, and while you're doing all that, who's CM9 are you trying to install. Do you have a link so I can look at it out of curiosity?

It took me awhile to absorb all that but after trying all.those steps,.there was no progress. Furthermore the microsd card I use is for both of my HTC's. And lastly the adb logcat or any adb script for that matter won't work unless the phone is in debug mode with a working o.s.
Thanks for hanging with me and I look forward to your next suggestion.
Sent from my HTC-PG762 using xda app-developers app

I wasn't sure whether there would be some kind of script running in a buffer of the install that might be captured with something like: logcat -b event > /sdcard/logcat.txt
so it was a shot in the dark and I don't know what's left, but perhaps someone else that is reading the post might have some ideas, or experience with this specific issue and jump in with a solution.
I was writing a macro once and couldn't get it to work and spent too much time over 3 days trying to figure it out. When I finally asked someone else to look at it, I was just missing a semi-colon or some one simple thing. You sound pretty knowledgeable, sorry I couldn't be the second set of eyes to come up with the missing thing. If I can think of anything more, I'm subscribed to this thread and I'll surely suggest it.

Thank you for trying, I hope to find an answer soon enough.
Sent from my HTC-PG762 using xda app-developers app

[Q] (Help) HTC One M8 Wiped System files / no recovery / no OS

Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.

nOOb HTC Guy said:
Hi everyone let me start by saying this: I know what I did was a stupid stupid stupid nOOb mistake, but please understand It did not occur due to lack of reading or negligence to the formation of good understanding prior to rooting and flashing roms etc.
I should also point out that I have read as many other threads and articles on this subject as I can and have resorted to making my own thread ONLY because it is specifically unique to all those I have found elsewhere (including on this site).
Anyway, heres how hellish my last two days have been:
Rooted phone, went perfectly.
Flashed Cyanogenmod Nightly, went perfectly
Decided I wanted go back to stock until stable Cyanogenmod was released as it was too bug ridden for my usage.
This is where it got bad. I cannot remember for the life of me WHY I thought I needed to do this but when I went into Advanced Wipe (TWRP) options i ticked pretty much everything (I am extremely embarrassed and ashamed of this idiotic and reckless action *hangs head in shame*)
Needless to say, at this point I no longer had an OS, so I went about restoring the lot from my backup in TWRP:
Boot Restored fine
DATA restored fine
Cache Restored fine
System FAILED again and again no matter what I tried (literally 20 plus attempts)
At this point I tried flashing back to Cyanogenmod out of desperation but was met only with FAILED and words to the effect of "cannot read .zip file", I found the same message appearing no matter what ROM I tried to flash (I tried a variety of the more popular/stable roms to rule out corrupt data)
At this point I tried sideloading RUU which failed in a similar manner although I cannot remember the exact message)
Then after more pulling my hair out and reading everything I could about other people having similar problems, someone suggested I relock Bootloader before flashing an RUU. This didnt help at all and now I cant unlock Bootloader again, which leaves me unable to access Recovery
I am now at the point of mental breakdown (only slightly exaggerating here) after HOURS of reading and troubleshooting and now a full two days without a phone. I only got the phone 3 days ago so you can imagine how crappy I feel right now.
If any of the resident magicians can help me here I would be grateful beyond words One more thing, In one of the threads I read on another site, someone was suggesting to the OP that since RUU and ROM flashing wernt working, he may have "corrupted NVRAM (internal Storage), If my memory serves me correctly Im sure one of the Advanced Wipe option tick boxes was indeed 'internal storage'
Thanks for any advice. Tommy.
Click to expand...
Click to collapse
are you using the all in one tool kit to do all of this?

skinsfanbdh said:
are you using the all in one tool kit to do all of this?
Click to expand...
Click to collapse
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.

nOOb HTC Guy said:
Yes and btw Ive regained access to Recovery which is a step in the right direction, but still have all the same problems ie nothing will flash and cannot restore system etc.
Click to expand...
Click to collapse
So you managed to unlock your bootloader again as well?

try using the all in one program to sideload a rom

Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.

nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
A ruu.exe is executed from the pc and not from the phone. Its useless to sideload it.
Sent from my HTC One_M8 using XDA Premium 4 mobile app

nOOb HTC Guy said:
Yer ive managed to unlock bootloader again. I have tried sideloading a variety of roms including the RUU and cyanogenmod. When attempting to sideload cyanogen mod, terminal simply bought up a loud of command lines and their meanings :S RUU however at least came up with the "sideloading" and percentage, gets to 100% and appears to finish, but nothing beyond that (I may be missing something im totally new to all of this) Cheers.
Click to expand...
Click to collapse
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.

BerndM14 said:
If you got the a list with commands and their meanings then either a) You're not in sideloading mode or b) you didn't type the command properly.
I'm assuming you're still using TWRP, if so, Got to Advanced >>> ADB Sideload >>> Swipe to start sideload ...
Open a command prompt and change directory to adb.exe & fastboot.exe folder / or hold shift and right click in folder where adb.exe/fastboot.exe is and then choose open command window here. Make sure your device is connected to PC and then type adb devices to make sure your device gets picked up, should show you the serial number for device AS WELL as "sideload" next to it, if so then you are hooked up right. If you're "hooked" up right and you can see the device serial number + sideload next to it, type adb sideload name_of_zip.zip wait until fully finished, once done reboot back into recovery and flash rom.
If sideload fails for one or other reason you can also try to push it. Reboot to recovery again, type adb devices to make sure device gets picked up, type adb push name_of_zip.zip /data/media/0/ or adb push name_of_zip.zip /sdcard/ ...I think you could use either, anyways, when finished flash as per usual.
Click to expand...
Click to collapse
Okay so I tried sideloading with your instructions, which came up "failed" but actually had put "sideload.zip" in the directory, but when I tried to flash it I got the same old "error flashing zip"
Next I tried to push file, which comes up with terminal message "error: closed".
It seems that the phone will not flash ANYTHING atall........

OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S

nOOb HTC Guy said:
OKAY BREAKTHROUGH lol instead of sitting here twiddling my thumbs waiting for replies, I thought I'd spend the time trying to sideload Cyanogenmod, IT WOOOOORRRKKEED and im in a good mood for the first time today thanks to you! My only problem now is that I cannot seem to restore from my backup, it always fails at system :S
Click to expand...
Click to collapse
I'll be back in around 2 hours or so, off to work now. At least a breakthrough of some sorts, will check on this thread later, hopefully you don't have to wait so long for your device to be fixed :fingers-crossed:
:victory:

if your using a different recovery or a different version of the same recovery your backups may not work unless you flash the recovery you made the backups with

Guys, Im still stuck with cyanogen mod, nothing else will flash or sideload successfully. Also, what I thought was the ruu for my phone was not, can anyone find the correct ruu for mine? Htc one m8 on vodafone uk, cant find an ruu anywhere
Also, cannot obtain s-off since I get "permission denied" message when trying to adb shell and "su" through terminal..... Dont know if I require s-off to flash roms or ruu? thanks.

Ok it doesnt look there is an ruu for mine yet. So maybe I should focus on trying to get my own stock backup to restore, but nothing works! Its always the system bit that fails, boot data cache all restore successfully, any ideas? Would be absolutely amazing if I could just restore to the backup successfully! :good:

success!
YES YES YES YES YES!!!!! NOOOOOBBB POOWWWEERRR!!!!! Sorted it finally!!!!
For anyone else who has had problems restoring from backups, try restoring with files on phone memory and not sd card! Thats what worked for me.
Guys, thankyou all so much for your help I am eternally grateful and more relieved than you can imagine. Finally have a phone again

[Q] phone crashed last night, now says it needs to be activated, wont activate

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.

[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