Related
I have a Moto X, and used one of the first root methods that came out with the phone (I don't remember what it's called, but it didn't require any fancy cmd window to type commands in or many different executables... I think I just loaded an apk onto the phone and ran it). Unfortunately, today, I accidentally installed an OTA. Now, my phone is stuck in a boot loop and re-boots every 30 seconds or so. How can I get out of this??
I've (sadly) done this once before and recovered from it by quickly hopping to some directory using Root Explorer and deleting the OTA update file. I've spent a couple hours trying to find this thread or information, but with no luck. It's very similar to this post: http://forums.androidcentral.com/thunderbolt-rooting-roms-hacks/174996-19-ota-push-bootloop-fix.html
I've also tried booting into recovery, but I've learned this morning that I don't have a recovery program on my phone. When I try to launch recovery, it just boots the phone and the bootloop starts all over again.
Thank you for help any of you can offer!!
Can you get into the stock recovery? You know the dead Andy on his back. If so go in to stock recovery and try a wipe. Then if it boots up look and see if your android version changed or not to see if the phone updated.
Solved!
Travisdroidx2 said:
Can you get into the stock recovery? You know the dead Andy on his back. If so go in to stock recovery and try a wipe. Then if it boots up look and see if your android version changed or not to see if the phone updated.
Click to expand...
Click to collapse
I was able to solve it! Here is what I did:
Install the app, "Root Explorer", if you don't have it already. You may have to try many, many times to get this to install.
Go to the directory, "/cache". This folder is at the very top of the phone's file structure, along with "sdcard", "system", "firmware", and others.
In this "cache" folder is a zip file called, "Blur_Version.##.##.##.ghost_att.ATT.en.US.zip". There are also two other folders, "lost+found" and "recovery".
Delete or rename the file. At around the time the phone wants to reboot, it will be looking for this file and find that it no longer exists because you have deleted or renamed it, and it will give you an error message. Acknowledge the error message, and the phone should be back to normal.
The original information comes from XDA user "motomesh", and the thread I found this information is here: http://forum.xda-developers.com/mot...te-problem-t2467614/post46179190#post46179190
Phone: Moto X
Android: 4.2.2
Carrier: AT&T
System Version: 139.9.51
You should spend $25 for the Sunshine bootloader unlock since you're still on 4.2.2.
Also, good job searching. It's rare to see someone find an answer to their question which has been asked many many many many times.
nhizzat said:
You should spend $25 for the Sunshine bootloader unlock since you're still on 4.2.2.
Also, good job searching. It's rare to see someone find an answer to their question which has been asked many many many many times.
Click to expand...
Click to collapse
Thanks! I'll check out Sunshine bootloader and see what that's about.
I appreciate your comment on finding my own solution. I do always try to put in the research before even thinking about posting my question. The XDA-Developers community has been a great wealth of information, and I'm quite thankful to everyone involved. It's just that on that particular day, I wasn't planning on tinkering with my phone, and I had such a schedule packed day with so many things to get done, so I was freaking out a little, because I needed a phone and had no backup. I had already spend an hour searching without luck, so I was hoping someone would take pity and not mind answering this popular question. I recognize my ask is a pretty big pet peeve; hopefully the community will forgive me on this one.
nhizzat said:
You should spend $25 for the Sunshine bootloader unlock since you're still on 4.2.2.
Also, good job searching. It's rare to see someone find an answer to their question which has been asked many many many many times.
Click to expand...
Click to collapse
And he even posted what phone and version and everything.
root, roms, and themes.. oh my!
Thanks for the solution! but...
I did the same thing that you commented here. Thanks for the solution!
However, I've been wondering...
Now that you know where the .zip file with the OTA is located....
Can't you just flash it with TWRP from there?
Jorfapigo said:
I did the same thing that you commented here. Thanks for the solution!
However, I've been wondering...
Now that you know where the .zip file with the OTA is located....
Can't you just flash it with TWRP from there?
Click to expand...
Click to collapse
You can try, but they always have failed for me. The only way to install an OTA.ZIP has been with STock recovery.
That being said, I haven't tried CWM or Philz recoveries.
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
That's a rather non-descript post. Who's your carrier, what Rom's are you talking about, any custom kernels, did you perform a wipe before installing? As far as the Audio goes, I've got no complaints from the speakers nor using headphones (both hardwired and BT headphones). You do realize that the first boot after installing a fresh Rom can take several minutes, some as long as 8 minutes while everything is set in place. More info so that we can help, please.
alucke said:
I have a nexus 6. The sound quality is horrible with headphones and the speakers. I unlocked the bootloader, rooted the nexus 6. A lot of the custom roms I have tried freeze during installation and soft brick the phone. The only rom that works is the stock rom.
alucke
Click to expand...
Click to collapse
lol your doing something wrong.
i have flashed most of the available roms, in total hundreds of times, never failed to boot, not even once.
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Is this a rant or are you asking for help? This is a development forum, so not really the place to rant. If you want help, please ask specific questions whilst supplying relevant information
Need education
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
---------- Post added 21st September 2015 at 12:09 AM ---------- Previous post was 20th September 2015 at 11:59 PM ----------
simms22 said:
i know i say this often, but ill say it again(even if im wrong this time).. i bet you used used a toolkit to root your device. too bad that you learn absolutely nothing from a toolkit. what you should do is put your phone down, and not touch it until you do some serious research into your device. how you do things properly, what can you flash, etc. these are things that you have to do before you ever root your device.
Click to expand...
Click to collapse
You are correct. Where do I go for help and advice upon this Android phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online by self at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus 6 is back in order. I some how managed to use the Root Tool Kit v2.0.4 and "pushed" the factory, I downloaded from Google, to the phone. I assume this restored my ABD allowing debug thereby establishing USB connection between PC and Nexus 6, I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the Nexus 6 bootloader or Fastboot.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
This is the most idiotic post I've seen here all day. Seriously sell your nexus 6 and go buy a different phone if you don't like the phone or face the fact that you either don't know how to use a nexus device or you have a defective phone. But I'm almost entirely convinced this is 100% user error
Sent from my Nexus 6 using XDA Free mobile app
ray6279 said:
You are correct. Where do I go for help and advice upon this phone OS? I am willing to learn but know of no courses or clubs to join. I am taking lessons online at the Google developers site. This is a start but slow go. As an update, my soft bricked Nexus6 is back in order. I some how managed to use the Root Tool Kit and "pushed" the factory to the phone. I assume this restored my ABD and debug thereby establishing USB connection between PC and phone. I then wiped Cache, system and Dvalick. and loaded Cyanogen Mod 12.1 and Gapps. For a while there I lost debug and was never able to open the phone and enable it.
Still,I would like to know the alternate way such as sideload ABD and commands, Fastboot, Bootloader, etc.. Thank you.
Click to expand...
Click to collapse
here is a good place to start
http://forum.xda-developers.com/nexus-6/general/how-to-nexus-6-one-beginners-guide-t2948481
http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
good luck!
Android documentation is kinda lacking
Its not terrible... Its just not entirely coherent, well organized or complete. A lot of poking around and learn by doing, patching together threads that document how things work ect...
Here is my suggestion:
Follow the second link posted by simms22 above, this one here: http://forum.xda-developers.com/nexus-6/general/noob-read-adb-fastboot-how-help-t3006500
Go here: https://developers.google.com/android/nexus/images?hl=en
And download the latest image for your phone (shamu, the images at the bottom of the list are most recent. All carriers currently use same build, unless your on tmobile or Fi)
Use some kind of unzipping program (not sure if winrar can do .tgz, if not just google "Windows .tgz") to decompress the image you download. This will have a few .img files in it and a .zip Unzip the .zip for the rest of the partition images for the phone.
With these you can use fastboot to re-format partition to stock.
Here is an older guide, while devices may vary a little... and things have changed since 2011, were still mostly talking about system, boot, recovery, data....
http://www.addictivetips.com/mobile...plained-boot-system-recovery-data-cache-misc/
I would say read through the above guides thoroughly, then manually update your phone to stock.
You will notice the stock flash-all script will
Code:
fastboot flash bootloader bootloader-shamu-moto-apq8084-71.10.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-shamu-d4.0-9625-02.101.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-shamu-lmy48m.zip
You probably don't want to do all this... You will notice the last command I showed is fastboot -w update image-shamu-lmy48m.zip (assuming you downloaded the lmy48m image)
We already unzipped this, so rather then flash it in bulk (flashing userdata.img will wipe device) lets flash everything but leave data in place.
So get fastboot working, go to bootloader, and as the script does
With fastboot:
Flash the bootloader
then use fastboot to reboot, to the bootloader
flash the radio
then use fastboot to reboot to the bootloader
then fasboot flash system, recovery, boot and cache images, skipping userdata to avoid wiping the sd card.
At this point reboot. It may take a while for the first boot as android sets itself up and optimizing applications. If things appear to be hung give it 10 minutes before forcing a reboot checking your images and trying again. Pay attention to the output of the commands and make sure there are no errors. If there are read them, and google them.
Now you should be able to boot, and you will be fully stock. This is what it takes to recover from almost any situation. Often you can just flash system to update. Boot will overwrite your kernel, so it is often skipped when custom kernels are used... particularly when not encrypted.
Now find the website for twrp and find the image for your device, then go back to bootloader mode and flash recovery, after flashing reboot directly to recovery.
Also find chainfire's website with the recovery flashable supersu (should be a .zip)
Make sure the supersu install zip is on your phone, and the recovery is on your computer.
Reboot to bootloader and fastboot flash twrp to your recovery partition, then immediately reboot to recovery mode to finish the install.
In recovery make a backup of your working stock system.
After that install supersu
Reboot, and you should be stock and rooted with a backup of your completely stock system.
From here if your want to install a rom reboot to recovery, wipe caches, system and data. On future upgrades backup first, and try only wiping system and caches, then flash the new version of the rom and you wont have to set anything back up. You will have to reinstall xposed if your use it, as well as supersu if your rom does not include it for some reason.
If you do all that, read those guides to the point where you understand each step, and read the thread or at least the last hand full of pages of any rom or utility that you use... Things should work pretty good.
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
And likewise to this post , useless as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
nevermind
simms22 said:
nevermind
Click to expand...
Click to collapse
:laugh: :laugh:
Was going to post, and had this thought also....
btw JJD loves his N6 and his speakers Rock!
#nuffsaid
Nexus 6 ftw!
disturb1 said:
It so easy for some to assume user error, the phone might be a defective I know hate the layout of mine, and out of 13 android phones currently this d*m thing is the only one that freezes on me and will not show up in Linux (two versions) or windows 7 and it still stock. I have hated the phone from day two and tried very hard to use it stock for as long i could. I finally said screw it and went back to my old lg g flex till just died.. I wish i could sell this...but I am stuck trying to make it work. still cant even make it show up in any os and that makes it a bit hard to do anything (and yes my USB ports and drivers and cables are fine i have checked)
Click to expand...
Click to collapse
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it either.
What file manager do you use, and did you have gvfs-mtp or kio-mtp installed?
What utilities were you using to mount the mtp drive?
These instructions are for arch linux, https://wiki.archlinux.org/index.php/MTP#simple-mtpfs (I use simple mtpfs), adapt them to your distro, find your distros documentation.
But then you don't really need it to show up in the OS? Does fastboot recognize it? Have you installed udev rules for it?
ok, thanks for all the input. I will give the nexus 6 a try again, root it. Can anyone point me to a custom rom that is somewhat close to stock?
I like Pure Nexus
scryan said:
It is user error.
SOME hardware is bad... But people like to view their phones as these temperamental beasts that "need to settle" and "all have their own intricacies"
Its a computer. Is this the way we look at laptops?
Two, or two hundred version of linux... Doesn't really matter because linux is a kernel and MTP implementation is handled separately. Not Nexus' fault that you didn't configure linux correctly, or that you expected someone else to do it for you for free, and they didn't do it
Click to expand...
Click to collapse
Not sure if I just have issues with lollipop or the hardware and lollipop
I have it rooted now and also still hate it I don't have the sound issues that some have but freezing was a constant with nexus T-Mobile stock ROM or maybe I have a lucky lemon ether way
I don't blame others or look to others to do my rooting rom installation or themes nor do I assume that it the phone every time all I am saying is we need to stop blaming every confused user as noob and assume people are not trying to learn
I been here 3 years but I lurk and learn and move on but I constantly see issues of flaming it is sad ...I see your reply and that fact that you offered help is what I like to see what I would offer if I knew an answer..
Honestly I am just not a fan of the phone but I made my bed and in it I must... hack at it till I am happy...
So, I think I'm really dumb. So, earlier today: I put this thread out: http://forum.xda-developers.com/moto-x-2014/help/how-unroot-return-to-stock-xt1095-t3210040
Of course, I'm not gonna make you read it. Basically, I was rooted on 5.1 and tried to unroot. But then I ****ed a lot of things up (I think I flashed a Kitkat recovery image) so I hard reset and I was down to 4.4. Now, I screwed myself super over by trying to flash the 5.0 factory image thinking it would bring me to normal stock and what not, only to send me to the Android in distress every single time. I tried to hard reset once more, but even hard resetting would send me to android in distress.
Though, when I went to the recovery menu (or the place where you can hard reset, connect adb), it showed that it was on LXE 22.46...meaning, it was lolipop. So, I have no idea what's going on and I just want a phone at this point. I don't even care if it's KitKat. Hell, after today I'm never going to tamper with my phone again due to the anxiety I'm feeling right now. If anyone could help, please do.
Edit: I think I know what my problem is. I think I soft bricked my device since I'm only booting into recovery, but I still have access to bootloader. I'm assuming I just have to flash some recovery and then reboot? But I'm not going to do anything without anyone elses input or something.
Maybe I can help!
Greeting!
I think I have a similar problem, and I think I know how to fix it on yours, not on mine though. First I need to know if when connected by a USB cable to a computer it's recognized, if it isn't, which is what is happening to me, I don't think you can fix it. If it does recognize it, you can try and flash a custom ROM (or the stock ROM) on your phone using your computer. You have probably heard of something called fast-boot. Well, Motorola has it's on version (called "mfastboot") , in case you want to use that to flash the ROM. But I know a very good program (also much easier to use) called UniFlash V2(there is also V1 but V2 is better, I recommend you use V2), which instead of using a CLI (command-line interface, basically things like command prompt) uses a GUI, where no commands have to be input, making the whole process much easier and maybe faster. What you have to do is download the program, and download a ZIP file of a ROM. For example, I have a Moto X 2014 2ND Edition, and i f****d up in some way or another, and can't boot my phone up. I can download the ROM I want to install in a ZIP file, and flash it to my phone with UniFlash. Say I wanted CyanogenMod, on my Moto X. I would download the ZIP file (in this case it's called "cm-13.0-20160103-NIGHTLY-victara.zip" but it's different for each phone) and go to the section called "ROM Modding" (I think that's the one you have to use, if not use the section called "Flash"), find the ZIP file you downloaded, select it, and then basically just follow the steps! It doesn't get easier than that! I hope this works for you, reply if it does, and if i't doesn't work, the thing I'd do is just go to a Motorola store and get it fixed there, as a last resource. By the way, you don't need to use a custom ROM, you can use a stock one. For example, if I were to search for my stock ROM, I'd search for "Moto X 2nd Edition 2014 Stock ROM". I hope I helped, good luck :laugh:!
Download link for UniFlash V2: http://forum.xda-developers.com/showthread.php?t=1859261
Hi everyone,
Please forgive any n00b questions.
I got started with rooting / custom ROMs on a Nexus 4, and I didn't realize at the time that this made things really easy and I didn't need to learn very much about how everything worked. Fast forward to last week -- I decided, at long last, that I was tired of using stock MM on my T-Mo G4 / H811. How hard could it be? Probably not much different from playing on my old Nexus 4 right? Lol, maybe not.
So now 72 hours later, my phone is hard bricked and will not enter download mode. and I need some assistance, if anyone would be so kind.
I will try to recount what I did:
To start with, I was using a Mac, so I used Homebrew to install Android platform tools / ADB.
I decided I wanted to try out LineageOS so I went ahead and followed their very clear steps (on LOS wiki) to unlock the bootloader install TWRP. However, TWRP doesn't seem to have an official build for the G4(!) so I had to look up and use one of the betas from this post. Is this where I went off the rails already? [Of course, very stupidly I also failed to make a complete backup of anything before going on ahead. Rookie mistake.]
After unlocking bootloader and flashing my TWRP beta, I was able to boot into TWRP just fine. I followed the normal prescribed steps of doing a Wipe (normal TWRP defaults -- system, cache, etc.?) before flashing the latest LOS nightly (14.1-something) and also the nano-x64 variety of gapps. I rebooted and got stuck with the LOS boot animation. I let this go for 55 minutes, so I am pretty sure it was an actual bootloop, not just the 1st-time-startup and optimization going on.
I rebooted into TWRP and decided to try a different ROM to see if that was the issue. So I wiped again, flashed another ROM (I believe it was a flavor of AOKP 14.1.x), flashed gapps again, and gave it another try. Again got stuck with an endless bootloop (45 minutes).
Since this is my daily driver, I decided to go back to stock. Found this thread, downloaded the MM-debloated zip, pushed to phone, and again Wiped + Flashed. This time, when I hit reboot, my phone was immediately hard-bricked. No startup screen, no nothing. That was quite unexpected. Also, the first time I had ever HARD bricked a device that I was playing with. Yikes!
Since then, I got a hold of a PC, and have been trying to revive the device by flashing an image to the microSD and booting into Download mode, in the form of this thread or this one.
I did get this to work briefly yesterday, or at least I got to Download Mode / Firmware Update screen, and then attempted to run LGUP with the KDZ file. However I ran into an error at about 9%, and couldn't continue -- and then I had to give back my loaner PC for the day. I also noticed that the LG Mobile Support tool was recognizing my phone NOT as an H811 but as something like HX230 or ... whatever it was, it was definitely wrong. Which is worrisome.
Today I'm giving it another try but my phone will not enter Download Mode at all, nor respond in any other way. I'm curious if this is a battery issue? So I am simply charging it for the time being. I also re-formatted the microSD and re-flashed the single .img just to be safe, but still can't get a response out of the phone. On my PC's device manager it is showing up as the common Qualcomm 9008 that a lot of people seem to have seen. No recognition from LG Mobile Support tool, nor from LGUP.
So ... what now?
It's possible that once my battery gets some charge again, maybe I'll be able to enter DL mode. Let's hope so.
However, I am also totally in the dark about which software version I should be using. 20i? 20p? I have no idea what these refer to, and I did not make any prior notes to capture the state that my phone was in before this all began. So IF I get to DL mode I will definitely need further instruction on the CORRECT KDZ FILE to be flashing. Else I will just compound my problems.
ANY tips or suggestions will be appreciated! Thanks so much.
Should have verified being on 20o firmware
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
freeradical426 said:
Upon further reading, quite obvious, at the top of this thread, I definitely should have followed the Prerequisite steps. I did NOT verify that I was on 20o firmware. "OR RISK BRICKING YOUR DEVICE" is right.
So I bricked my device, in exactly the way I was warned not to do, it seems.
Still, what's the next step? Any thoughts?
Click to expand...
Click to collapse
try search for a fix if not may be @steadfasterX knows how to help you.
Re: searching for unbrick solutions
raptorddd said:
try search for a fix if not may be @steadfasterX knows how to help you.
Click to expand...
Click to collapse
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
freeradical426 said:
Thanks, I have been looking around for solutions, but can't seem to find anything aside from the unbrick-guides that I've already listed / already attempted.
Will hope for help from @steadfasterX ! Or some other knowledgeable / benevolent party.
Click to expand...
Click to collapse
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Ok what was the last KDZ file you flashed which had worked? 20o?
As you have hard bricked your device you can try the sdcard method again if it works flash 20o again (of it it was 20o).
If you flash a lower version you will hard brick again.
If the sdcard doesn't work anymore for you you can try to flash with QFIL but beware to use the right one. If you use the wrong one it will convert your device and believe me that's not what you want. I can share the good ones but unfortunately maybe on next week first.
Otherwise search on your own for 9008 unbrick but check the md5sum of the programmer!! Compare it with the Evil one mentioned in my ARB list here: http://tinyurl.com/antirollg4 and DO NOT USE THE EVIL one..
Click to expand...
Click to collapse
Thanks very much for the guidance! The post that you linked to REALLY helps. Until now I really was not sure what 10n, 20i, 20o, etc. referred to, aside from just various software versions. Having a definition for anti-rollback and further links to explain, really helps! This gives me more information and I might be able to self-resolve from here. I will give it a shot.
As for your question ... unfortunately there was NO instance where I flashed a working KDZ file, and I didn't know (due to my past experience with my Nexus) that I needed to check the STOCK software version of my phone before beginning to play with ROMs. In other words, I have no idea if I was on 20i, 20o, 20p, etc. From what I understand, this makes things a lot more difficult
Having looked at the linked thread just a little bit, it appears that using a 20o KDZ is the best bet -- because I bricked my device using a 20i ROM so I expect it was due to violating the anti-rollback restriction.
I will look into it more closely and come back if I hit another brick wall. Thanks so much!
If anyone cares, here are the ending results of all this ...
#1 Be wary of anti-rollback restrictions before you flash anything to your G4. You WILL brick your phone!
I tried multiple rounds and multiple variations of all the MicroSD card methods that I could find. I could NOT succeed in unbricking my phone.
#2 Luckily ... I was able to convince LG that I was still technically under warranty!
Because I had the stock bootloop issue in May 2017, LG did an in-warranty repair for me, and replaced the motherboard. So last week, I simply told them "my phone is AGAIN unable to charge and will not power on, just like in May". Since it had only been 5-6 months since the first issue, they agreed to replace the motherboard again.
Moral of the story: you can definitely unbrick your phone by having LG replace the mobo XD XD
From here, I think I will just totally avoid doing any rooting or custom ROMs on my totally-stock G4 coming today in the mail. I will cross my fingers and hope we get OEM Nougat in the USA sometime in the next couple of months.
Thanks again for the help everyone!
boost moto e4 plus (sku xt1776)
I am new to rooting and roms and whatnot, someone help me? i cant for life of me figure out how to flash a custom rom for this phone. Ive rooted it, but what i really need is a step by step guide on how to flash the correct rom. ive found the lineage ones but i dont know which one to flash.
i used twrp, phh superuser to root. now i want to put a custom rom on here so i can use substratum..
ive been at this for about 4 hours now and im frustrated and i figured instead of trying to figure it out i would just ask an expert who knows more about this stuff than me. I recently got into theming and love it. Im trying to learn as much about it as possible. I used to use tlauncher but once i read about substratum i was hooked in. thanks to whoever decides to help me lol. I appreciate it. There's probably a thread answering this already but i cant find it so sorry to the moderators in advance.
[edit]
I also now have N/A coming up when i boot. Idk if i did something wrong when i rooted?
I will help get you started, but let me say in advance that you will need to READ FURTHER.
Preamble - It is very important that you understand that the same model phone, the Moto E4 Plus, comes in two varieties - the phone's processor can be either MediaTek (Nichlaus) or Qualcomm (Owens.) You can determine which you have by going to Settings, then scrolling down to About phone.
You will also need to have the right drivers on your PC and to have installed Minimal ADB. There are guides for both of these and you should read them.
The N/A showing on your phone is normal after rooting and installing TWRP, see https://forum.xda-developers.com/moto-e4-plus/themes/fix-n-boot-logo-screen-t3738658 for some solutions to fix that.
These steps should help you get going:
1) Unlock your bootloader, seems like you already did that.
2) Install TWRP and then root. You seem to have already done that as well. For anyone else reading, there are two variants on TWRP depending on phone processor - install either the Owens or Nichlaus one and be CAREFUL to install the right one.
3) You will need to download two files now - the ROM itself and GAPPs (the suite of Google apps.) GAPPs comes in multiple varieties depending on how many of the Google applications that you want. Want only the minimal? Download the smallest file. You can generally add more through the Play store. (Example - I didn't have Google Maps on my phone. I had to install it later. Easy.) GAPPs also comes in different variations. The one that you need is for Android 7.1 and for the ARM family of processors. NOT ARM 64. That won't work.
4) Reboot into TWRP recovery. You can do this manually or use a command through ADB. If you don't know how to do this, read this: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
5) Using TWRP, make a backup of your phone first. If you don't know how to do this, read this: https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/ (You should use a microSD card for your backups and keep one on your PC just in case. You can just copy stuff back and forth, but keep one on your external card and one on your PC. It will give you peace of mind.) Understand that all your pictures, files and apps are going to be wiped out.
6) Read a guide to using TWRP: https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/ is one example. Move the ROM file and the GAPPs file to your phone. Also, the file that you used to gain Root, generally Magisk. Now, wipe your phone (you did make a backup first, right) and flash the ROM, the GAPPs file, and your root file.. TWRP lets you flash all three in sequence.
7) Reboot and expect that the first boot will take between 10 to 30 minutes. Go out for a walk. Watch a TV show. Don't sit and stare at your phone. People get nervous and interrupt things that they shouldn't.
8) Now you will have to set your phone up all over again. Log into wifi, log into Google, install your apps, etc.
Enjoy!
stonefabtim said:
boost moto e4 plus (sku xt1776)
I am new to rooting and roms and whatnot, someone help me? i cant for life of me figure out how to flash a custom rom for this phone. Ive rooted it, but what i really need is a step by step guide on how to flash the correct rom. ive found the lineage ones but i dont know which one to flash.
i used twrp, phh superuser to root. now i want to put a custom rom on here so i can use substratum..
ive been at this for about 4 hours now and im frustrated and i figured instead of trying to figure it out i would just ask an expert who knows more about this stuff than me. I recently got into theming and love it. Im trying to learn as much about it as possible. I used to use tlauncher but once i read about substratum i was hooked in. thanks to whoever decides to help me lol. I appreciate it. There's probably a thread answering this already but i cant find it so sorry to the moderators in advance.
[edit]
I also now have N/A coming up when i boot. Idk if i did something wrong when i rooted?
Click to expand...
Click to collapse
The N/A is a good sign, as I means your twrp has been successfully installed. Install all ROMs the same way.
- Boot into recovery
- Format Data ( type yes) the do normal factory reset wipe. Twice. You'll get some red lines and errors, ignore them and keep going.
- Reboot directly into recovery.
- Format data & then do factory reset again.
- Flash ROM
- Flash no-verity_opt-encrypt.zip
- Flash Magisk (or SuperSU.zip)
- Flash Gapps
- Wipe Cache/Dalvik
- reboot
ALWAYS let the device sit for about 10mins after booting to allow the software to finish expanding before ya start messing with it. I'll add this to my Root Guide in Android forums later.
Hope that helps.
---------- Post added at 09:16 AM ---------- Previous post was at 09:11 AM ----------
koop1955 said:
I will help get you started, but let me say in advance that you will need to READ FURTHER.
Preamble - It is very important that you understand that the same model phone, the Moto E4 Plus, comes in two varieties - the phone's processor can be either MediaTek (Nichlaus) or Qualcomm (Owens.) You can determine which you have by going to Settings, then scrolling down to About phone.
You will also need to have the right drivers on your PC and to have installed Minimal ADB. There are guides for both of these and you should read them.
The N/A showing on your phone is normal after rooting and installing TWRP, see https://forum.xda-developers.com/moto-e4-plus/themes/fix-n-boot-logo-screen-t3738658 for some solutions to fix that.
These steps should help you get going:
1) Unlock your bootloader, seems like you already did that.
2) Install TWRP and then root. You seem to have already done that as well. For anyone else reading, there are two variants on TWRP depending on phone processor - install either the Owens or Nichlaus one and be CAREFUL to install the right one.
3) You will need to download two files now - the ROM itself and GAPPs (the suite of Google apps.) GAPPs comes in multiple varieties depending on how many of the Google applications that you want. Want only the minimal? Download the smallest file. You can generally add more through the Play store. (Example - I didn't have Google Maps on my phone. I had to install it later. Easy.) GAPPs also comes in different variations. The one that you need is for Android 7.1 and for the ARM family of processors. NOT ARM 64. That won't work.
4) Reboot into TWRP recovery. You can do this manually or use a command through ADB. If you don't know how to do this, read this: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
5) Using TWRP, make a backup of your phone first. If you don't know how to do this, read this: https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/ (You should use a microSD card for your backups and keep one on your PC just in case. You can just copy stuff back and forth, but keep one on your external card and one on your PC. It will give you peace of mind.) Understand that all your pictures, files and apps are going to be wiped out.
6) Read a guide to using TWRP: https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/ is one example. Move the ROM file and the GAPPs file to your phone. Also, the file that you used to gain Root, generally Magisk. Now, wipe your phone (you did make a backup first, right) and flash the ROM, the GAPPs file, and your root file.. TWRP lets you flash all three in sequence.
7) Reboot and expect that the first boot will take between 10 to 30 minutes. Go out for a walk. Watch a TV show. Don't sit and stare at your phone. People get nervous and interrupt things that they shouldn't.
8) Now you will have to set your phone up all over again. Log into wifi, log into Google, install your apps, etc.
Enjoy!
Click to expand...
Click to collapse
Well done
koop1955 said:
I will help get you started, but let me say in advance that you will need to READ FURTHER.
Preamble - It is very important that you understand that the same model phone, the Moto E4 Plus, comes in two varieties - the phone's processor can be either MediaTek (Nichlaus) or Qualcomm (Owens.) You can determine which you have by going to Settings, then scrolling down to About phone.
You will also need to have the right drivers on your PC and to have installed Minimal ADB. There are guides for both of these and you should read them.
The N/A showing on your phone is normal after rooting and installing TWRP, see https://forum.xda-developers.com/moto-e4-plus/themes/fix-n-boot-logo-screen-t3738658 for some solutions to fix that.
These steps should help you get going:
1) Unlock your bootloader, seems like you already did that.
2) Install TWRP and then root. You seem to have already done that as well. For anyone else reading, there are two variants on TWRP depending on phone processor - install either the Owens or Nichlaus one and be CAREFUL to install the right one.
3) You will need to download two files now - the ROM itself and GAPPs (the suite of Google apps.) GAPPs comes in multiple varieties depending on how many of the Google applications that you want. Want only the minimal? Download the smallest file. You can generally add more through the Play store. (Example - I didn't have Google Maps on my phone. I had to install it later. Easy.) GAPPs also comes in different variations. The one that you need is for Android 7.1 and for the ARM family of processors. NOT ARM 64. That won't work.
4) Reboot into TWRP recovery. You can do this manually or use a command through ADB. If you don't know how to do this, read this: https://www.androidcentral.com/10-basic-terminal-commands-you-should-know
5) Using TWRP, make a backup of your phone first. If you don't know how to do this, read this: https://www.howtogeek.com/240582/how-to-back-up-and-restore-your-android-phone-with-twrp/ (You should use a microSD card for your backups and keep one on your PC just in case. You can just copy stuff back and forth, but keep one on your external card and one on your PC. It will give you peace of mind.) Understand that all your pictures, files and apps are going to be wiped out.
6) Read a guide to using TWRP: https://android.gadgethacks.com/how...only-custom-recovery-youll-ever-need-0156006/ is one example. Move the ROM file and the GAPPs file to your phone. Also, the file that you used to gain Root, generally Magisk. Now, wipe your phone (you did make a backup first, right) and flash the ROM, the GAPPs file, and your root file.. TWRP lets you flash all three in sequence.
7) Reboot and expect that the first boot will take between 10 to 30 minutes. Go out for a walk. Watch a TV show. Don't sit and stare at your phone. People get nervous and interrupt things that they shouldn't.
8) Now you will have to set your phone up all over again. Log into wifi, log into Google, install your apps, etc.
Enjoy!
Click to expand...
Click to collapse
Thanks bro. Much appreciated. My next question would be, in your opinion, what would be the best rom to get for my specific device?
stonefabtim said:
Thanks bro. Much appreciated. My next question would be, in your opinion, what would be the best rom to get for my specific device?
Click to expand...
Click to collapse
That depends on whatcha like and how you use it.. There's a few here in XDA and many more here: https://androidforums.com/threads/moto-e-4-plus-owens-all-things-root-guide.1259898/
Aaand another issue...
bcrichster said:
That depends on whatcha like and how you use it.. There's a few here in XDA and many more here: https://androidforums.com/threads/moto-e-4-plus-owens-all-things-root-guide.1259898/
Click to expand...
Click to collapse
Yeah, my sd card just took a dump. Can this be done without one? i found a thread but its from 2011...
https://forum.xda-developers.com/showthread.php?t=911228
stonefabtim said:
Yeah, my sd card just took a dump. Can this be done without one? i found a thread but its from 2011...
https://forum.xda-developers.com/showthread.php?t=911228
Click to expand...
Click to collapse
Yes, you can flash one without an SD card but you'll have to use a PC for side loading or copying the ROM to device (while in recovery) since you have to do a fill wipe of internal storage to remove encryption anyways..
Sent from my Moto E (4) Plus using Tapatalk
bcrichster said:
Yes, you can flash one without an SD card but you'll have to use a PC for side loading or copying the ROM to device (while in recovery) since you have to do a fill wipe of internal storage to remove encryption anyways..
Sent from my Moto E (4) Plus using Tapatalk
Click to expand...
Click to collapse
Ok, would I be doing it the way that it says in that thread just using twrp instead? Or does that method not work anymore? Thanks you guys for all the help.
stonefabtim said:
Ok, would I be doing it the way that it says in that thread just using twrp instead? Or does that method not work anymore? Thanks you guys for all the help.
Click to expand...
Click to collapse
Dude. No adb stuff needed anymore. Just boot into recovery and do all your wiping stuff. Then copy the ROM, no-verity, magisk, gapps zips from PC to device internal storage, I put in downloads folder. Then go back to the device and flash like normal. Internal storage on our owens is just labeled "sdcard". (I have the exact same device, using Boost Mobile)
Ok. Thanks. I'll give it a shot. Last phone I flashed was in like 2011 (I've been in prison for 5 years) so all this is new to me. It's probably frustrating trying to explain it to me. I appreciate the help though.
bcrichster said:
Dude. No adb stuff needed anymore. Just boot into recovery and do all your wiping stuff. Then copy the ROM, no-verity, magisk, gapps zips from PC to device internal storage, I put in downloads folder. Then go back to the device and flash like normal. Internal storage on our owens is just labeled "sdcard". (I have the exact same device, using Boost Mobile)
Click to expand...
Click to collapse
well, i did everything, used the lineage 14.1, now when i boot into system the start up failed. Should i try a different rom? I know I'm probably starting to be a pain.
stonefabtim said:
well, i did everything, used the lineage 14.1, now when i boot into system the start up failed. Should i try a different rom? I know I'm probably starting to be a pain.
Click to expand...
Click to collapse
Remember to format data and factory reset twice. Boot into recovery and do it again. Then flash ROM, no-verity.zip, magisk, gapps. Wipe cache & dalvik, Reboot recovery and flash again. Really. Afterwards ya should be fine..
Sent from my Moto E (4) Plus using Tapatalk
Yeah I think I just 'bricked' my phone.
stonefabtim said:
Ok. Thanks. I'll give it a shot. Last phone I flashed was in like 2011 (I've been in prison for 5 years) so all this is new to me. It's probably frustrating trying to explain it to me. I appreciate the help though.
Click to expand...
Click to collapse
I tryed flashing the lineage 14.1, gapps, no verity, superuser, now the boot fails. Tried going back into twrp and flashing a different rom, now instead of the 'install zip' button i have install image. And i didnt make a back up, I didnt have enough space in the phone to save the image. I dont know what to do lol
You really should use an external microSD card.
Question how did you root your E4 plus from boost I've been having hella time trying to do so
Funisillegal said:
Question how did you root your E4 plus from boost I've been having hella time trying to do so
Click to expand...
Click to collapse
- unlock bootloader
- flash twrp
- flash custom ROM &/or Root.zip
bcrichster said:
- unlock bootloader
- flash twrp
- flash custom ROM &/or Root.zip
Click to expand...
Click to collapse
Sorry I should of been more detailed. I know the process but my issue is the bootloader. My phone is thru boost and I know it can be unlocked but on Motorola's website I've gone thru pulling the sequence from ADB and when entered in I get a message saying it doesn't recognize what was entered and I've also tried using the data scrubber provided by motorola and same outcome. I've called Motorola and the best they could do was email me a link to their forums which was no help. I feel I have tried everything even the sunshine app and no dice. Frustrated as all help and any help would be greatly appreciated and I've been at this for two weeks
Sent from my Moto E (4) Plus using XDA-Developers Legacy app
Sounds like you accidentally left some letters/numbers/spaces that didn't need be there.. Pull that code again and remove all spaces, leave the #'s tho..
Funisillegal said:
Sorry I should of been more detailed. I know the process but my issue is the bootloader. My phone is thru boost and I know it can be unlocked but on Motorola's website I've gone thru pulling the sequence from ADB and when entered in I get a message saying it doesn't recognize what was entered and I've also tried using the data scrubber provided by motorola and same outcome. I've called Motorola and the best they could do was email me a link to their forums which was no help. I feel I have tried everything even the sunshine app and no dice. Frustrated as all help and any help would be greatly appreciated and I've been at this for two weeks
Sent from my Moto E (4) Plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Sent from my Moto E (4) Plus using Tapatalk
I've done that and gone as far as entering it in manually a couple of times. Just to be sure I even had my wife read it to me and entered it in with the hashes only
Sent from my Moto E (4) Plus using XDA-Developers Legacy app