Database Develop

[Q] Need Help Deciding What to do With Rooted Phone

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

[Q] Stuck, in many ways

Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,

ghane0 said:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
Click to expand...
Click to collapse
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow

Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.

koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
Click to expand...
Click to collapse
It is a 901s he said non Taiwan
Sent from my HTC Butterfly s using XDA Premium 4 mobile app

seyidaga said:
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Click to expand...
Click to collapse
I have downloaded the Maximus ROM. I am open to doing this, but I cannot figure out how to use the stock recovery (there seem to be no controls).

koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Click to expand...
Click to collapse
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
koniiiik said:
If it was a 901S, I'd suggest installing the stock ROM from scratch
Click to expand...
Click to collapse
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,

daorderdillon said:
It is a 901s he said non Taiwan
Click to expand...
Click to collapse
Oh, okay, I think I'm getting lost in which area has which version of the phone. Never mind then and thanks for the correction.
ghane0 said:
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
Click to expand...
Click to collapse
Well, to install custom ROMs, you'll have to use either TWRP or CWM, I don't know about a way to do that using stock recovery.

Ok, I did this:
Installed CWM Recovery
Flashed the Stock zip from koniiiik's archive
Rebooted successfully. Lots and lots of force closes, Everything from android.core to ...
Used Rom Manager to restore a backup made a month ago
Rebooted. All OK now
Flashed Stock Recovery (again, thanks koniiiik)
Booted. Checked OTA. Got a small update (1.x)
Applied. Rebooted, Checked OTA again
Got the 4.3 package. Applied.
All is well
Between Step #3 and #4, I got my entire backlog of SMS delivered, which I lost in the next step. But that is a small price to pay.
Thanks to all of you helped,

ghane0 said:
Used Rom Manager to restore a backup made a month ago
Click to expand...
Click to collapse
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.

Backup of /system, nearly stock
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
koniiiik said:
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Click to expand...
Click to collapse
I have three files in the directory:
system.ext4.tar (0B)
system.ext4.tar.a (954MB)
system.ext4.tar.b (500MB)
Is the split to avoid files greater than 1GB?
Will upload starting a few hours. Dropbox will do?

ghane0 said:
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
Click to expand...
Click to collapse
Don't worry about that, of these three, only root affects /system and it should be not too difficult to revert.
ghane0 said:
Is the split to avoid files greater than 1GB?
Click to expand...
Click to collapse
Most likely – FAT filesystems, depending on inode size and other factors, only support file sizes up to a certain limit. Sometimes it's 2 GB, sometimes 4 GB, sometimes probably as little as 1 GB.
ghane0 said:
Will upload starting a few hours. Dropbox will do?
Click to expand...
Click to collapse
That would be most helpful. Thanks.

Dropbox is back up, I have sent you a link.
Thanks

[Q] Booting to Non-Stock Recovery Without Flashing It

Hey All,
I only recently picked up an XT-1060 (2013 Moto X, Dev Ed) that I plan to set up on my Verizon account. I have some experience with both the Nexus 7 (2012) and HTC's Android variants, and, for those platforms, there are technical advantages to booting to a non-stock recovery image directly from fastboot *without flashing that recovery image to the device*. I did a search of all the Moto X forums for such an alternative, and a cursory look didn't give me anything that jumped off the page regarding whether or not this was even possible.
Which brings me to my question: Assuming that I've already taken care of unlocking the bootloader, can I boot to a non-stock recovery on my new unlocked Moto X without flashing that recovery?
Many thanks!
cheers,
john

What do you mean by flashing?
You can fastboot twrp.img,which is a custom recovery.

Unfortunately, booting a custom recovery isn't possible on the Moto X. Why? I have no idea.
Just think of it as an extra later of security against an inadvertent OTA installation.

Thanks to you both for your kind replies.
nhizzat said:
Unfortunately, booting a custom recovery isn't possible on the Moto X. Why? I have no idea.
Just think of it as an extra later of security against an inadvertent OTA installation.
Click to expand...
Click to collapse
This is a bit of a disappointment. It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs. I tend to stay on the "current-stock-plus-rooted" track. The only reason I need a custom recovery is (1) To root the device, and (2) To do nandroid backups from time to time (and possibly restores).
On devices that allow it, this means that I only need to boot the custom one occasionally, with the side benefit of being able to accept OTAs without problems. At least that's been the case for me so far.
Nicolae-Daniel said:
What do you mean by flashing?
You can fastboot twrp.img,which is a custom recovery.
Click to expand...
Click to collapse
This line doesn't make any sense to me. My typical scenarios are: If I'm trying to boot twrm, say, I'd issue: "fastboot boot twrp.img"; and, if I want to flash it, I'd use "fastboot flash recovery twrp.img". Day to day, the only thing I do with recovery is wipe the system cache, and I can do that with the stock recovery. *Sigh*
Regardless, thanks again you two...
cheers,
john

That's the approach I've always taken with my Nexus 7. All the functionality of flashing a custom recovery with one less variable to worry about.

jrredho said:
Thanks to you both for your kind replies.
This is a bit of a disappointment. It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs. I tend to stay on the "current-stock-plus-rooted" track. The only reason I need a custom recovery is (1) To root the device, and (2) To do nandroid backups from time to time (and possibly restores).
On devices that allow it, this means that I only need to boot the custom one occasionally, with the side benefit of being able to accept OTAs without problems. At least that's been the case for me so far.
This line doesn't make any sense to me. My typical scenarios are: If I'm trying to boot twrm, say, I'd issue: "fastboot boot twrp.img"; and, if I want to flash it, I'd use "fastboot flash recovery twrp.img". Day to day, the only thing I do with recovery is wipe the system cache, and I can do that with the stock recovery. *Sigh*
Regardless, thanks again you two...
cheers,
john
Click to expand...
Click to collapse
I'm guessing you will have to play with stock and custom recoveries for that.

jrredho said:
It means that I've got to strip out and save the stock recovery somewhere, then re-flash it to enable OTAs.
Click to expand...
Click to collapse
You always can take recovery.img from your official firmware zip archive and flash it anytime.
UPD: And i hope you know, that OTA will fail if you modify or remove pre-installed apps using root.

k3nny2k said:
You always can take recovery.img from your official firmware zip archive and flash it anytime.
Click to expand...
Click to collapse
Yes, and this is exactly what I'm trying to avoid!
k3nny2k said:
UPD: And i hope you know, that OTA will fail if you modify or remove pre-installed apps using root.
Click to expand...
Click to collapse
I do know that, yes. My plan is to leave the device largely stock. I just need nandroid backups, a handful of root-requiring apps, and tethering. These are the only reasons that I root. I also do not need moment-to-moment access to a custom recovery.
Anyway, thanks for keeping me on my toes!
cheers,
john

Accidentally flashed a file to root that was for KitKat (Im on Lollipop)

So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?

shahrukhraza said:
So I accidentaly flashed the wrong root file thus making my systemui continuously crash. Any suggestions as to what I can do?
Click to expand...
Click to collapse
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.

Paddington said:
Stock recovery or TWRP?
Are you looking to undo what you did without having to do a complete wipe, or are you open to more drastic solutions? Because you can always run the toolkit to reset to complete stock by flashing the stock images over your current system. But that would of course perform a complete wipe.
Click to expand...
Click to collapse
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.

shahrukhraza said:
I dont really mind a complete wipe. And are you referring to this toolkit? http://forum.xda-developers.com/mot...l-windroid-universal-android-toolkit-t3048099
if not could you please tell me which one?
And to clarify, I followed this tutorial: https://www.youtube.com/watch?v=_fPIYhzWlnw . The file that I flashed to attempt to root is in the description of that.
Click to expand...
Click to collapse
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.

Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.

Paddington said:
I actually used this one: http://forum.xda-developers.com/moto-x-2014/development/tool-moto-x-pure-edition-recovery-t2897819 when I was messed around, but I would imagine either would work. When I needed to return to unrooted stock, I believe that toolkit returned me to 4.4.4 unrooted stock, then I just ran the 5.0 OTA once the phone booted up.
The toolkit you referenced is the one I used to unlock the bootloader, flash TWRP, and root my phone. As long as you can get to recovery or fastboot, either toolkit should work to return you to stock. BUT I caution you, I have a pure edition, and these toolkits were made for the pure edition. If you do not have a pure edition, you'll want to read the disclaimers/instructions/other posts to make sure it will work on your phone.
Click to expand...
Click to collapse
Yessir thanks for replying. However I now have a whole new problem. Do you have any suggestions for that? It is the post above^

shahrukhraza said:
Okay so this escalated quickly.
So here I am being my dumb self , I try to flash TWRP. That goes fine and then I try to wipe my data. After that I reboot it and as its turning on it foes black on the boot animation. and now I cant even get into freaking recovery mode. I dont know what I did but im pretty sure I messed up bad. I need some serious help now and anything is appreciated.
Click to expand...
Click to collapse
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625

ewalk4866 said:
Hey thats an easy fix just load into the boatloader and reflash the rom through mfastboot
edit: you should be able to get all the files you need from his website http://forum.xda-developers.com/moto-x-2014/general/ota-pure-edition-lollipop-5-0-t2932625
Click to expand...
Click to collapse
Bootloader as in vol. down + power button right? Thats not working too. I also tried other combinations to no luck. And before it was turning on but now its not even booting to the boot animation. Thanks for the link though, if it does magically boot into the bootloader then i'll know what to do at least.
Edit: Okay so theres the charging animation, so thats a start, I guess. Still no luck on the bootloader tho.

Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody

shahrukhraza said:
Okay got it into bootloader mode!
Now before I do any other stupid thing can somebody just confirm one thing for me? On Graffix's website, this is the img I should flash through mfastboot right
Lollipop 5.0 22.21.11 FULL IMAGE PACKAGE Zip
Just a confirmation because I dont really trust my judgement. Thanks again everybody
Click to expand...
Click to collapse
Yes that's right remember you only have to flash system

Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.

Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.

Paddington said:
Sorry that my Toolkit suggestion messed you up. I really thought that solution would work, not make it worse.
Click to expand...
Click to collapse
Nah man that didnt mess it up, some other stupid thing did it lol. Nothing on you, rather thanks for the help.

ewalk4866 said:
Toolkit are never really a good idea it just makes people lazy and not learn how to flash or fix problems on there own.
Click to expand...
Click to collapse
I agree that Toolkits can make you lazy and not learn how to fix things on your own, but when you need a quick fix and don't have time to figure out what is going wrong, it's always nice to just boot your phone into fastboot or recovery and fix things with a few keystrokes on your computer.

I got it to work guys! Thanks for all the help. It was much appreciated.

Bad first time experience when I tried rooting my Nexus 6 Marshmallow.

I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?

meeniemuffin said:
.... But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot.
Click to expand...
Click to collapse
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493

meeniemuffin said:
I just bought myself an almost mint condition Nexus 6 (build MRA58R). It's running Marshmallow and I tried rooting it today. After I researched how to go by obtaining root I tried it out, felt very confident, didn't come across any errors. But then when I was booting back up, a screen with red letters saying something about my phone being corrupted was not allowing my phone to boot. Naturally, first I panicked. Afterwards I researched, found and then executed a manual flash of system, boot, bootloader, cache and recovery images. Then, my phone was back up and running. Discouraged and defeated, here I am knowing I could've done some better things with my time than mash commands into a terminal to fix my nooby mistake for a few hours. How should I approach obtaining root on my phone if at all possible with my model?
Click to expand...
Click to collapse
-enable "OEM unlocking" in developer options
-unlock bootloader
-flash TWRP using fastboot
-flash a custom kernel
-flash SuperSU 2.52
-KEEP BOOTLOADER UNLOCKED
-KEEP "OEM unlocking" ENABLED
---------- Post added at 09:50 AM ---------- Previous post was at 09:42 AM ----------
NLBeev said:
You could bring Google to court when your device is working 100% and the message says it is corrupt. Read the OP of this link. http://forum.xda-developers.com/showthread.php?t=3059493
Click to expand...
Click to collapse
There's nothing mentioned there.

Droidphilev said:
There's nothing mentioned there.
Click to expand...
Click to collapse
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15

NLBeev said:
Hmm, here the links works. It is a link to a stock rom that is already rooted.
The rom is updated with the latest security OTA.
Full name of the OP.
[ROM]【6.0_r3】Stock MRA58R [Lite] - 【Marshmallow】【hC kernel】- 11/05/15
Click to expand...
Click to collapse
It indeed works but i thought it would bring to a page about the court thing you have mentioned.

Droidphilev said:
It indeed works but i thought it would bring to a page about the court thing you have mentioned.
Click to expand...
Click to collapse
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.

NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Aha! i saw you posting this before but never knew that it was a joke

I didn't even need to read all this stuff. First thing I did was get into developer mode and almost instinctual that I turned on OEM unlocking before setting about unlocking the bootloader.
Sent from my Nexus 6 using Tapatalk

Yeah I bought my N6 recently and had a bad first time experience too. I ended up using a toolkit to root and all that, didn't need a custom rom so I kept it stock with TWRP and I'm very happy. Since then, I rooted some of the old devices I had laying around (you can check my signature), so I should be more prepared next time I need to update. My problem is I didn't really understand the commands, what did what and what exactly was required for root. Now that I have had plenty to practice with I'm pretty comfortable with commands and recoveries. Practice makes perfect I guess

NLBeev said:
No I was joking, sorry. But there is something serious behind the joke.
Here on XDA there are too many posts/questions about the 'corrupt message'.
The distance between ' customizing the phone' and 'Google' is growing.
Click to expand...
Click to collapse
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.

shadowcore said:
Pretty much the trend. I bet by Android 7.0, rooting will be impossible.
Click to expand...
Click to collapse
I hope not. Google's software and design will be the weak point. Google could not give us some simple options like a dark interface, reboot options and dpi settings.

So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?

If bootload is locked, unlock it - This will erase everything backup your device
1. Get modified boot.img for your version, flash it
2. Flash twrp
3. Flash SuperSu 2.52

meeniemuffin said:
So, people, to sum it all up... The road to obtaining root on this Marshmallow enabled phone is?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!

Droidphilev said:
http://forum.xda-developers.com/showpost.php?p=63999613&postcount=3
!!!
Click to expand...
Click to collapse
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?

meeniemuffin said:
Sorry! Slow to learn over here. I still have a question...do I need a custom kernel and flash stock rom? Or just a custom stock ROM thats already prerooted? Both, perhaps? Would I have to flash Twrp in order to even do this?
Click to expand...
Click to collapse
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)

Droidphilev said:
You have a stockrom now, right?
if you want to keep that for now then this is the easiest way. The TWRP step is there to be able to flash the custom kernel. (and of course make backups and flash other roms in the future)
Click to expand...
Click to collapse
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.

meeniemuffin said:
I had an epiphany earlier. I did everything....it all hit me at once. I finally managed to get Pure Nexus ROM working. Time for a test drive.
Thanks for the advice.
Click to expand...
Click to collapse
enjoy!
but DO NOT forget to keep "OEM unlocking" enabled!
(it will save you when you ever get locked out from your google acoount because you became aflashoholic)