Related
For a person with little or no knowledge on doing all the flash stuff with the Tablets..would you say this app would help alot? Or doing it without the app is better?
I seen the video of someone using it..on a phone tho...seems nice. Didnt see VEGAn TAB anywhere in the options thing. That would be able to find this also in "Download ROMS" right? Thanks for the help.
DJR0D said:
For a person with little or no knowledge on doing all the flash stuff with the Tablets..would you say this app would help alot? Or doing it without the app is better?
I seen the video of someone using it..on a phone tho...seems nice. Didnt see VEGAn TAB anywhere in the options thing. That would be able to find this also in "Download ROMS" right? Thanks for the help.
Click to expand...
Click to collapse
Rom Manager has been known to hose some users gTabs making them very difficult to fix.
Well, the recovery hooks used by the ROM manager app cause problems with the GTablet... I recommend avoiding it!!
Yea....after all the good i read about it....i saw all the bad stuff. Too bad...that would have been the thing for me to be brave and flash. With that it made it seem pretty easy. Oh well. Gotta learn the real way soon.
Anyone on here use this with the GTab and had success???? Alot say this is not good with the GTab. Some say it is. Man...
its not worth using on the gtablet. Trust me, once you figure out how to do a few other things, you wont need this tool anyways. Start looking through this site. You will learn a lot. http://viewsonic-gtablet-for-dummies.webs.com/
ROM Manager is just a GUI interface to installing .zips (ROMs, updates, etc..).
However, it requires a specific version of Clockworkmod Recovery to work.
If you already have Clockworkmod Recovery on your Gtablet, it's just as easy to use it manually than hoping the Rom Manager specific Clockworkmod Recovery doesn't brick your tablet.
Donwload the ROM you want, power off and boot in to clockworkmod recovery (Hold Volume + while powering on) and select the install .zip from sdcard. Just browse to the downloaded .zip and install it.
It's best to also do a factory reset before installing a rom....and making a backup before you flash something new in case you don't like it or it has issues.
Earlier it had a lot of problems....I think they've resolved most of those issues (Rom Manager now lists the Gtablet SMB_A1002 when flashing the recovery), but it's still so simple to flash manually and not worry the risks.
So I just successfully rooted my lovely HTC One from Sprint. I've got TWRP 2.6.0.1 on it and all.
I'd REALLY like to get rid of all this garbage on my phone that I'm never going to use, however I also would like to keep it as close to stock as possible. I really enjoy Sense for the most part (minus quirks that I'm willing to live with, and BlinkFeed). I know how/can find out how to load a custom rom - I had CM7 on my HTC EVO 4G (1st Gen) and loved it. But I really don't want to be without Sense.
Can anyone make any suggestions as to what I should do/which rom I should use?
wolfbuck22 said:
So I just successfully rooted my lovely HTC One from Sprint. I've got TWRP 2.6.0.1 on it and all.
I'd REALLY like to get rid of all this garbage on my phone that I'm never going to use, however I also would like to keep it as close to stock as possible. I really enjoy Sense for the most part (minus quirks that I'm willing to live with, and BlinkFeed). I know how/can find out how to load a custom rom - I had CM7 on my HTC EVO 4G (1st Gen) and loved it. But I really don't want to be without Sense.
Can anyone make any suggestions as to what I should do/which rom I should use?
Click to expand...
Click to collapse
omj's stock rooted sounds like the rom for you
wranglerray said:
omj's stock rooted sounds like the rom for you
Click to expand...
Click to collapse
With a custom kernel. And greenify.
And a whole boat load of other mods you can only discover by spending time on these forums.
Stock with goodies
Sent from my One using XDA Premium 4 mobile app
wranglerray said:
omj's stock rooted sounds like the rom for you
Click to expand...
Click to collapse
Sorry, I'm overwhelmed at the wealth of knowledge here. Is there a link to the specific one you're talking about? Search didn't do me a ton of good. Though I suppose I could send the guy a message and inquire about his ROM.
Thank you for all your help guys!
Okay so I've decided that I want to try the OMJ ROM. Now here's where I am unsure of exactly how to do it. I see that certain ROMs require different methods. I can't just copy the ZIP to my internal storage and use TWRP to flash it, right? It has to be more complicated than that...
Also, I just went past the return window for the phone so I really cannot afford to brick it. I assume that there's next to no chance of the aforementioned tragedy befalling me providing I stick with the mainstream ROMs?
Most roms are in a flashable format i use the CM 10.2 nightly myself. from what i can tell as long as you can get into the bootloader your safe. I wiped my whole phone SD card and everything accidentally with TWRP one time. Ended up having to use sideload to get a CM rom installed again but i was never in danger of bricking. When flashing roms always remember to do a factory reset to wipe the cache and do an advanced wipe of the data and system. after the rom is installed it will ask you to wipe the cache again which is always nice to do.
cloppy said:
Most roms are in a flashable format i use the CM 10.2 nightly myself. from what i can tell as long as you can get into the bootloader your safe. I wiped my whole phone SD card and everything accidentally with TWRP one time. Ended up having to use sideload to get a CM rom installed again but i was never in danger of bricking. When flashing roms always remember to do a factory reset to wipe the cache and do an advanced wipe of the data and system. after the rom is installed it will ask you to wipe the cache again which is always nice to do.
Click to expand...
Click to collapse
Awesome! So what was I hearing about having to plug the phone into the computer to flash the boot.IMG file? Sorry, I'm just really overwhelmed with the new ways of doing things.
wolfbuck22 said:
Awesome! So what was I hearing about having to plug the phone into the computer to flash the boot.IMG file? Sorry, I'm just really overwhelmed with the new ways of doing things.
Click to expand...
Click to collapse
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
cloppy said:
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
Click to expand...
Click to collapse
Awesome! I guess it really is that easy! Thanks so much for all your help!
cloppy said:
No worries, I am new to the unlocking scene too with this device . Those flashable zips will normally have the boot.img files included and when installing twrp will take care of it via the script inside the zip. if you open the zip file with winzip or something you should see that file on the root. TWRP or ClockworkMod recoveries make it really easy to install and backup roms.
flashing the boot.img i guess is for recovery purposes say if the system is in a boot loop. Or maybe if you upgrade the system only and didnt change boot img between two different roms. I personally never had to do this. After unlocking the device i used fastboot to replace the recovery and just do everything else inside the recovery.
Click to expand...
Click to collapse
Alright, so I've got OMJ's rom running no problem. Love the new feel but what I'm wondering is...is there still a way to delete apps like Stocks and other crap I won't use? I can disable some but not all, and none am I able to uninstall completely.
Would it be something as simple as going into the OMJ ZIP file and removing the unwanted apk files and then re-flashing to that version?
wolfbuck22 said:
Alright, so I've got OMJ's rom running no problem. Love the new feel but what I'm wondering is...is there still a way to delete apps like Stocks and other crap I won't use? I can disable some but not all, and none am I able to uninstall completely.
Would it be something as simple as going into the OMJ ZIP file and removing the unwanted apk files and then re-flashing to that version?
Click to expand...
Click to collapse
I suppose that could be one way of doing it, but i dont think its necessary. if you are already rooted or can install root easy i would just install a Root file explorer. Browse to the /system/app folder i think it is and delete the APKs from there.
cloppy said:
I suppose that could be one way of doing it, but i dont think its necessary. if you are already rooted or can install root easy i would just install a Root file explorer. Browse to the /system/app folder i think it is and delete the APKs from there.
Click to expand...
Click to collapse
Yeah I tried that with ES explorer AND Root File Manager. ES would have an error, and Root File Manager would simply say it was deleted but it was never actually deleted. I think it has something to do with the security. I'm not really sure, haha! I'm used to being able to just openly delete apps from within Settings>Apps like the old days of my EVO 1st gen.
hmm interesting as long as the /system is mounted as r/w permissions you should be able to delete. well if you are planning on reflashing using the modify zip method im curious to know if that works.
wolfbuck22 said:
Yeah I tried that with ES explorer AND Root File Manager. ES would have an error, and Root File Manager would simply say it was deleted but it was never actually deleted. I think it has something to do with the security. I'm not really sure, haha! I'm used to being able to just openly delete apps from within Settings>Apps like the old days of my EVO 1st gen.
Click to expand...
Click to collapse
use Root explorer, and set it at r/w
also Titanium Backup will delete it for you too.
If I remember correctly there are a few apps in the play store that are specifically for getting rid of "bloatware".....maybe search bloatware removal, our uninstall bloatware something like that. Hopefully this helps!
Sent from my HTCONE using xda premium
Aldo101t said:
use Root explorer, and set it at r/w
also Titanium Backup will delete it for you too.
Click to expand...
Click to collapse
Well for whatever reason neither of those two suggestions worked. So I installed Root Browser and was finally able to get rid of some things.
Scratch that. Rebooted phone and the apps are back.
wolfbuck22 said:
Well for whatever reason neither of those two suggestions worked. So I installed Root Browser and was finally able to get rid of some things.
Scratch that. Rebooted phone and the apps are back.
Click to expand...
Click to collapse
ROMCleaner
bigdaddy619 said:
ROMCleaner
Click to expand...
Click to collapse
Thanks! I'm working on it now. I did not see an app called "ROM Cleaner" or "ROMCleaner" but I did find something called Rom Toolbox Lite that I'm going to attempt to use.
Will post back. I may look for the ROMCleaner on the net and just install it manually.
Edit: So I guess I showed my ignorance there. It appears ROM Cleaner is something offered through the forum. I'm unsure of how to use it so I'll take a look around.
wolfbuck22 said:
Thanks! I'm working on it now. I did not see an app called "ROM Cleaner" or "ROMCleaner" but I did find something called Rom Toolbox Lite that I'm going to attempt to use.
Will post back. I may look for the ROMCleaner on the net and just install it manually.
Edit: So I guess I showed my ignorance there. It appears ROM Cleaner is something offered through the forum. I'm unsure of how to use it so I'll take a look around.
Click to expand...
Click to collapse
ROMCleaner
It's very doubtful you will have success with Romtoolbox either once you reboot all the apps will return
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
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
RLBL said:
(originally posted in the flashfire threads, but it was suggested I post here)
My apologies if this has already been covered (I could not find an answer in searching)
I appreciate that it can be dangerous to use flashfire to flash the bootloader partition and that one should use fastboot. My question is:
If I download a FW package and the bootloader has changed, what happens if I flash to the kernel, system, cache, vendor etc... and do not flash to bootloader and radio? Will the flash fail; will the phone soft brick; will nothing happen and I can go merrily along?
The question derives from this: If the phone can become unusable with a mismatched bootload and radio to the rest of the images, it would require to unpack the package and check for a version prior to flashing other partitions (so I assume). If I go that far, would it not be easier to not use flashfire and simply manually flash the required files when updates are available?
Thanks
N6, unlocked and rooted (previously always updating latest patches and rerooting myself (using TWRP), but wishing to try flashire)
Click to expand...
Click to collapse
it is really rare that a bootloader flash is required, and a radio update is never required. if you dont flash them, then you just dont flash them, thats all.
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
both mm a lollipop, i never updated my bootloader. i did update it after mm though.
ktmom said:
I'd add that going to a major update you'll want to pay close attention. The bootloader probably will need updating. e.g. lollipop to MM, the bootloader had to be updated.
The radio is optional and often with trial and error, you'll find a particular one that for your hardware, in your area, you get the best signal. There is a thread with N6 flashable radios here: http://forum.xda-developers.com/showthread.php?t=3066052.
Had you posted that you had an N6 in your original post, I'd have helped you, because that's what I use
Click to expand...
Click to collapse
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
RLBL said:
Oh That looks interesting. My Cellular signal sucks even though I am supposedly close to some towers. I am going to try using flashfire with these (hope I don't brick myself lol)
So I assume that when N comes out officially and I need to change bootloaders, I would do so via fasboot, then afterwards I can the the updates via fashfire.
Click to expand...
Click to collapse
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
simms22 said:
all the radios, and bootloaders, are available in flashable zip for here on xda as well. to flash via twrp recovery
Click to expand...
Click to collapse
Cool... But I only used TWRP to flash the SU binaries to root. Now that I am rooted, I figured I could simply go back to stock recovery* and use flashfire going forward.
* I figured that because I had no other use for for a custom recovery presently, I may as well stay completely stock and rooted. Furthermore, from my understanding (which can be wrong) I no longer need a custom recovery to flash/install anything, as flashfire can do it all. Of course that brings one to ask "why am I rooted if I am staying stock?". I root my device so I can simulate a power button press without cancelling smart lock operations (either through tasker shell keyevent, gravity screen, or nova prime swipe gesture). I like not having to use the buttons on my phone
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
scryan said:
Why get rid of custom recovery? Just leave it and keep a backup on hand, then when there is an issue with basically anything you can just restore your backup instead of freaking out and running here using caps and exclamation marks asking how to fix.
Click to expand...
Click to collapse
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
RLBL said:
1 - why use a custom recovery if I do not need to (serious question, not being confrontational - see below)
2 - I totally know how to flash to whatever I want without using any toolkits (and ofc using a custom recovery)
3 - Why would one assume that one panics? (just because I have a low post count and admittedly an Android noob - N6 1st phone - does not mean I am an idiot)
4 - Considering I am not using custom ROMs and staying stock, I would think the likelihood of things going wrong is low (could be totally wrong there lol but I have done everything myself manually since the get go (never even taken an OTA for my upgrades), and never had 1 issue as of yet. This post was a general question in nature. It was not posted because I needed something to be fixed)
If I do not need it, why have it: I am experimenting to see if I can use FF completely stock (and rooted). Please provide some rationale as to why I should keep a custom recovery so I can evaluate (you may be 100% right). The point is: from my understanding one can use FF without a custom recovery so why not try... so far, so good.
On backups: be aware (not that you should care, but you did comment)... I have nothing on my phone that requires backing up at that... I can completely wipe the phone and it only takes time to do a google restore and I am back to where I am (been there, done that. Annoying for time though lol but I have no data on the phone safe from tasker profiles which are on my google drive and easily restored).
Click to expand...
Click to collapse
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
31ken31 said:
And what happens when you flash a bootloader and something screws up? You can't fix it from the stock recovery menu, now can you. So what not have something useful on the recovery partition for that 1 and 1000 chance something goes wrong.... Just my opinion, being I've been flashing phones since the first Android device was released on T-Mobile. The g1 (still have and still flash Roms
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I think that was the whole point of my post was it not? What happens if you DON'T flash a bootloader while using FF (but in the case where it did change)? And like I said, in the 1/1000 chance that something does go wrong and I did not have a backup: Flash the complete package via adb? Like I said, I have nothing to backup, thus nothing to recover. Not saying I shouldn't, just saying I don't. I only used TWRP to gain root access, nothing more (no custom ROMs, kernels, optimizations, anything on my phone...not even local app data saves - I am one of those old farts who uses their phone as a PDA with phone capabilities and that is it. All "data" is cloud based for calendar info etc.)
It was a relatively simple (general) question around some experimentation I am doing to see if it would work if one was completely stock (safe from root); did not think it would turn in an philosophical argument on whether or not one should use a stock recovery (which I have been using a custom up until yesterday, but was thinking about putting it back on this evening anyways, just because)
Anyways, got my answer... thx
simms22 said:
1. the only one important thing about having twrp installed.. backups and restores. before dlashing or changing anything, i akways create a backup in twrp. if something doesnt work out, you can always restore your backup, as ive done many many times. its a quicky fix it.
Click to expand...
Click to collapse
Thanks!... Obviously when I do venture into more with the phone I will do that. Currently it is a work and personal device so the only thing I do is flash Google stock builds instead of waiting for OTAs. Not saying I should not have a backup, but I don't. Only once after the 1st flash I re-locked the bootloader (as per instructions). What I waste of time; but it did show me that in a non-efficient disaster recovery, I can get everything back to where I was.
A restore would have been efficient, but I have found that I really have nothing to back up.. yet.
I guess a (off-topic) question I have for you is: What and Why did things not work out? In my case where I am only flashing stock loads (not waiting for OTAs), what could one anticipate going wrong that a re-flash could not recover from, but a restore could? Example a write corruption of a partition and the only thing I can do is boot into recovery as my PC cannot see the phone via adb? Can something like that happen?
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
31ken31 said:
Backing up system is what saves your a**
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
RLBL said:
cool... but... what if you are stock? Save my ass from what? Will a (re)flash of stock binaries not suffice?
Look I appreciate I am sounding argumentative, but I am curious to understand what can happen and why. I can understand the "need" to do it if customizing a device etc... but I am very curious as to why if you are stock:
example:
A stock user unlocks his bootloader so they can flash files straight from google be it OTAs or the complete package. It is not listed anywhere to have a custom recovery in their instructions which would lead one to believe it is not required if flashing said files... I assume something could go wrong of course and the most efficient way is to do a restore from backup... but I also assume one could simply re-flash and start over.
I am not devaluating the merits of a custom recovery; I was just curious if one could use (easily) flash fire without one - and one can. The purpose of the question was two-fold:
- because I was flashing stock, then reflashing twrp to get root I found the process longer than it needed to be so I thought I could use flashfire and have it do it for me.
- then I realized that flashing re-roots as well so I did not need to flash the custom recovery to obtain root. I thought "hey what if I accidentally checked "recovery" and accidentally went back to stock. No harm done as I can move on and still be rooted.
Not sure my butt needs saving to ask. You may be doing something that having backups is a good and safe idea... what if you are not? No harm in still using a custom of course, but it was just a question (I ask such questions so I know in advance why something happened and what to do so I do not come running to forums in all caps as someone else said lol)
off topic: If one has nothing to backup, what is there to restore?
Click to expand...
Click to collapse
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
simms22 said:
its all a matter of choice, period.
flashing stock, you dont need to do anything. flashing different mods, custom roms, gapps, or supersu, you need to use twrp recovery. you can even flash twrp to be permenant or flash twrp for a one time use. if you are flashing custom roms/mods regularly, its convieniant to have twrp, if your not it doesnt matter. but the one thing twrp is great for is backing up, in case. and you dont need many back ups, just one recent backup. so you can back up, then get rid of twrp until needed again. anyways, its all a personal choice, and thats all it is. for me, flashing twrp then leaving it makes sense, since ill never ever do anything stock. for you, you have your own needs and wants.
Click to expand...
Click to collapse
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
RLBL said:
Thank you for answering the question.
I figure when this phone (or whichever phone) is not my daily driver and no longer linked to sensitive stuff I will start venturing into the domain of custom ROMs and Kernels.
Click to expand...
Click to collapse
custom recoveries just make things easier for you, overall, to do stuff. but kernels, that could be the bomb. but you will need to learn about how to use governors/schedulers to make any kind of headways. for example, i use a completely different governor/scheduler(ondemand/deadline) than any other nexus kernel, and i feel that my way makes my phone much better/faster than any other setup. and thats whats important to me
Update: test passed (I knew it would)
With a stock recovery, I was able to use flashfire and upgrade to the latest update and re-root.
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