I have a question about my device. It is about how to mod a stock update zip to install mod apks and shell scripts or recovery scripts update binaries be flashed with stock recovery. Oh or to flash a modded recovery IMG like if I was to Port twrp IMG into my stock recovery IMG. But to have my stock recovery flash it as if it is from Google, Motorola or my carrier.
How come the only BOTs that even closely resemble real people all belong to Mr zucc? I feel disrespected. Here this is, a technology forum and we get the **** bots and the jerkoffs over on Facebook who heard it was cool and hip to eat a tide pod get the real good ones? Go away.
Sent from my [device_name] using XDA-Developers Legacy app
Related
I am making this thread because I am seeing *far* too many people posting things when they have no idea what they do or when things are coming, or what things are possible with the phone at this point, so please take these answers into consideration when deciding to post either a new thread, or a reply to someone in an existing thread:
(Note: This thread will be continuously updated when more issues need to be addressed)
QUESTION NUMBER 1:
What can our phone do at this point (9/17/2011)?
At this point, our phones can do the following:
-Be rooted
-Use a bootstrap ClockworkMod Recovery
-Make nandroid backups
-Use the 2nd init booting process
QUESTION NUMBER 2:
What is bootstrap recovery?
Bootstrap recovery is an alternative form of recovery which "hijacks" the boot process and instead goes into a recovery mode that loads the ClockworkMod Recovery.
In order to boot into it, you *must* bootstrap it through the app on Android *every time you want to boot into recovery*.
QUESTION NUMBER 3:
What does having bootstrap recovery do for us?
With bootstrap recovery, we can do EVERYTHING that a normal recovery can do for us, *INCLUDING* installing ROMs and making nandroid backups.
QUESTION NUMBER 4:
Now that we have bootstrap recovery, does this mean we can use ROM Manager to install stuff?
No. No, no, no, a thousand times no. This is not an official 2nd init Recovery release from koush and ROM Manager WILL NOT work with the bootstrap version of recovery.
QUESTION NUMBER 5:
What is 2nd init?
2nd init is altering the init files in the system partition to take over the booting process so that we can load whatever we want to on boot. It is a way to get around the locking of the bootloader. This is also what allows CM7 to run on Moto phones with locked bootloaders.
QUESTION NUMBER 6 (this is the important one):
What does it mean when our bootloader is "locked"?
The bootloader being locked means that we are not allowed to flash unsigned images in fastboot or flash custom kernels to our phone that can alter features such as overclocking, or BFS, etc.
HOWEVER: This *does NOT* mean we cannot start making custom ROMs on our phone. The bootloader being locked has *nothing* to do with the system partition and custom ROMs are still completely viable and can be made and now freely distributed.
ALSO: There *are* ways to get around the fact that we cannot flash custom kernels. With 2nd init and kernel modules, we can freely get around the locked bootloader and even achieve features such as overclocking without having to flash a different kernel.
Please read this and understand this before you post.
very useful information here...there seems to be many in these forums that are new-to-root and this explains the current status very well. thanks for this and all of the help you have provided people already.
Sent from my DROID BIONIC using XDA App
I liked this thread since I just picked the bionic up yesterday, like it better than the Droid 3
Sent from my DROID BIONIC using xda premium
If your truly new to root i suggest waiting or reading alot before attempting anything here way to early to be rooting and have no idea what your doing that makes for a perfect bionic paperweight
Sent from my DROID BIONIC using XDA App
Bump-This needs a sticky.
topxshelfxtre said:
If your truly new to root i suggest waiting or reading alot before attempting anything here way to early to be rooting and have no idea what your doing that makes for a perfect bionic paperweight
Sent from my DROID BIONIC using XDA App
Click to expand...
Click to collapse
If you know what you're doing, there's not much risk...if you don't, it's a disaster waiting to happen.
Sent from my DROID BIONIC using XDA App
Berzerker7 said:
I am making this thread because I am seeing *far* too many people posting things when they have no idea what they do or when things are coming, or what things are possible with the phone at this point, so please take these answers into consideration when deciding to post either a new thread, or a reply to someone in an existing thread:
......Please read this and understand this before you post.
Click to expand...
Click to collapse
Can you please include Pictures?
Forever root
Where can I find a link to Forever root and cheesecake?
Thankk you
Thanks
Nice write up. As a newbie I can't thank you enough for clearing those topics up in a short and sweet manner. Thanks!
this is the place for stupid questions?
im experienced (rooted droids) but total noob.
what is all the talk about 893 or 5.6something.
its seems totally differenent from ROMs but it looks like some say you need to have this # to use this rom and so forth. It looks also like people are screwing up there data with this stuff.
So...for people who want to Root&Rom is this stuff important? Where is info on what it actually is (893 and other #s)
covering my head and waiting for the smack...
Berzerker7 said:
QUESTION NUMBER 4:
Now that we have bootstrap recovery, does this mean we can use ROM Manager to install stuff?
No. No, no, no, a thousand times no. This is not an official 2nd init Recovery release from koush and ROM Manager WILL NOT work with the bootstrap version of recovery.
Click to expand...
Click to collapse
I was taking a look at the Bootstrap description on the market and it reads:
YOU MUST BE ROOTED TO USE THIS APPLICATION. FOR DROID BIONIC ONLY.
DO NOT DOWNLOAD THIS IF YOU AREN'T COMFORTABLE USING AN SBF!
Droid Bionic Recovery Bootstrap will set your phone up so you can access a custom recovery mode to create full backups of your phone and install new ROMs! Install ROM Manager afterwards for easy ROM installation and backup!
What does the developer mean by the last sentence of his description? Doesn't this conflict with FAQ #4? I'm just trying to make sense of everything before I begin using Roms... Thanks.
Ok so I took the OTA lollipop update, rooted and the phone was rocking. Installed TWRP backed up including cache and boot. I did factory reset and restored from backup file and I couldn't get past the boot animation. I downloaded these files http://forum.xda-developers.com/mot...g-lxe22-39-6-pure-edition-stock-boot-t2940437 and ran these commands:
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
Then, I lost the boot animation, only had the boot image. Then a lot of mfastboot stuff and I am back at on a fresh unrooted KK...... Any ideas wtf happened? Was it TWRP, restoring the cache or what? This is my fist no Sammy device so it's a learning experience.
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
dobbs3x said:
I don't think twrp is working on moto x lollipop yet. They just released the lollipop compatible twrp for nexus not long ago. We should get a new twrp for lollipop soon.
Sent from my XT1095 using Tapatalk
Click to expand...
Click to collapse
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
TWRP has been horribly quirky for me on my Moto X. I can't even get it to boot into recovery half the time, among other things.
Sent from my iPhone 6 using Tapatalk
cam30era said:
I am using TWRP 2.8.1.0 on my XT1095. Running 5.0 (.11 OTA). I've had no problems, at all.
Click to expand...
Click to collapse
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
dobbs3x said:
I also have twrp 2.8.1.0, but have you tried restoring lollipop backups with it? It will boot into twrp fine and flash zips etc. It just is not ready to to restores etc for lollipop.
Click to expand...
Click to collapse
Aahh. Good point. I've made a backup and flashed .zips. But have not tried to restore a backup. Thanks for the heads up.
I now know the restore of TWRP backups is what did it. I have successfully recreated the issue twice with the exact same results.
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
Currently what I have done is just:
- unlocked the bootloader via moto site.
- fastboot boot CF-Auto-Root-victara-victaratmo-xt1095.img
- installed/updated SuperSU via Playstore
- installed updated Binary via SuperSU
Back when I had the Nexus 5, I would change the DPI with DPI changer, but on some ROMs, flashing an updated GAPPS/etc would break the ROM, because of the DPI Changer... (I would just do a NAND restore/TWRP restore) How can I full-proof my current setup so that when I mess up I can always have something to fall back on?
From what I read above flashing TWRP is no ideal yet as NAND backups don't restore? is that right?
I'm just running stock Bootloader/Recovery right now, and I'm not sure how to fail-proof myself.
If I stick to default bootloader/recovery can I just flash default KitKat/Lollipop image to restore/fix any issues?
Lastly, on boot, that "Unlocked Bootloader" message comes up, it's not the worst, but from what I understand people flash a bootloader/recovery that removes that warning?
Thanks for help.
Shemploo said:
Interesting thread, what do you guys suggest one does if one wants to mess with things like DPI changer?
.
Click to expand...
Click to collapse
Edit build.prop :good:
TigerDNA said:
Edit build.prop :good:
Click to expand...
Click to collapse
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Shemploo said:
I meant how to safely change things like DPI (Or settings that might break ROM), but yet protect yourself from breaking the ROM.
- Example was doing something like changing the DPI either via App or by editing build.prop
Click to expand...
Click to collapse
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
TigerDNA said:
Change dpi system wide just edit the build.prop. if you break something you learned something. Im sure you can hard brick but really what would to I want to mess with that would cause a hard brick, most likely nothing. Just play with it and if you kill it, learn from it and do something different next time.
The only way to do something's is sounding like you are wanting is to make your own ROM.
Click to expand...
Click to collapse
Maybe someday, but right now I do not have time to learn, and the few times I tried to learn to program was a long time ago and it did not go well.
I would certainty like to go into Android programming, but for my short time needs, I guess I'm wondering how, if anything.. one can do to have an easy fix to breaking the OS/ROM, since TWRP back-ups don't seem to work for this device right now.
What is hard brick?, can anything I mess up software wise be restored via flashing factory images?
I wanna update TWRP to last version.
how do I do it?
thnx
If you're asking this question then I would recommend you flash it in fastboot. If the phrase "fastboot flash recovery recovery.img" doesn't make total sense to you then you really should read up on it before you do much of anything else from within recovery.
^^^^ What he said. Curious, how did you install it the first time? There is also a twrp app and flashify app that will flash img. files as long as you are rooted.
Flashing recoveries is one of the most basic things we do here. If you don't know, or can't find out how to do that, then you should study up.... Before you end up with a paperweight.
Not trying to offend you, just saying this to help. ?
Try the "complete moto X guide" at the top of the general section. And bookmark it. Almost anything you need to know is there.
[REF]The Complete Moto X Guides/Information Thread
XDA is a site for learning and development.... It requires us all to do some homework.
Good luck! ?
Root Toolkit for Android M
Download the Toolkit here.
For Step 1 - 1.2 you need to boot into Fastboot Mode.
For Step 2 & 3 you need to boot into your recovery and adb sideload.
For Step 4 you need to enable USB DEBUGGING.
Greetings ericgaebel​
This should not be post in development section q&a.
Sent from my Nexus 5 using xda premium
Thank you op
ericgaebel said:
Hello,
this is how to root Android M Developer Preview on the Nexus 5.
1. You must flash TWRP or CWM Recovery via Fastboot or the Nexus Root Toolkit.
2. Download the latest SuperSU Beta from here
3. Download the latest Kernel Patch from here
4. Put the files on your internal storage
5. Boot into your recovery then press "install zip from sd card"
6. As first flash SuperSU and then the Kernel Patch.
7. Boot up your phone normally then install BusyBox.
Click to expand...
Click to collapse
1- no you shouldn't use a toolkit. If you need a toolkit you shouldn't be flashing a developer preview
2- there isn't just despair kernel. There is also code blue and hellscore which all offer different features
3- flashing the kernel first is probably the better way around
Not being rude. But just giving you some info you are possibly unaware of
Sent from my Android M Nexus 5 yo!
Ben36 said:
1- no you shouldn't use a toolkit. If you need a toolkit you shouldn't be flashing a developer preview
2- there isn't just despair kernel. There is also code blue and hellscore which all offer different features
3- flashing the kernel first is probably the better way around
Not being rude. But just giving you some info you are possibly unaware of
Sent from my Android M Nexus 5 yo!
Click to expand...
Click to collapse
Is there a reason why we shouldn't use a toolkit? I've never had any problems. I've flashed images both ways and I can't tell the difference only that the toolkit is great.
Sent from my Nexus 5 using XDA Free mobile app
Nothing wrong with using a toolkit.
I'm on M and flashed with Wugfresh.
Flashed Twrp using adb / fastboot via cmd line
Sent from my Nexus 5 using XDA Free mobile app
uploaded my own little toolkit including all the .img and .zip files. FOR YOU GUYS!
push
Toolkits really aren't needed with Nexus devices since it is ridiculously easy to complete common tasks with adb, fastboot and your recovery.
Newcomers to the Nexus 5 are better off learning to use adb and fastboot since they will be better prepared to fix their device should something go wrong.
Horses for courses. I know I'd o ly ever use a toolkit by Wugfresh as it's never let me down ever. There are bad toolkits out there, which is the problem. People use them and don't know the basic principles of flashing images.
We don't all start with nexus. Some phones are a pain to root and if a toolkit does it OK. Hopefully then The bug to learn has taken root, literally.
No one who is not a Dev should be flashing this and making toolkits so noobs can is irresponsible at best. Its not stable. Its not meant for daily use, especially by noobs. Lollipop has only just been sorted out. Stick with that.
I'd like to see this closed as people are going to brick their phones
SENT BY ENTANGLEMENT
I had aokp installed through twrp and now im giving the phone to a friend whos not tech savvy so i wanted to put it back to stock yet every file i get for the stock rom fails to flash properly through twrp. Any help? Maybe im making a small mistake somewhere along the lines so if someone could either link me to the correct forum post for it or link me the correct file? ive tried about 7 different files and none of them have worked and they were all from XDA forums
KingHephaestus said:
I had aokp installed through twrp and now im giving the phone to a friend whos not tech savvy.
so i wanted to put it back to stock yet every file i get for the stock rom fails to flash properly through twrp.
Any help? Maybe im making a small mistake somewhere along the lines so if someone could either link me to the correct forum post for it or link me the correct file? ive tried about 7 different files and none of them have worked and they were all from XDA forums
Click to expand...
Click to collapse
You probably want to keep TWRP custom recovery. So you want to flash a TWRP-flashable stock firmware file. It's called a ROM, but it's really just stock firmware in a TWRP-flashable format.
You want to keep TWRP recovery, even if your friend is not tech savvy. It doesn't hurt in any way and can always help. For one, you can make a TWRP backup of the phone, before giving it to him and you or he could always "restore" that factory fresh image in case he ever screws it up.
THIS is what you are looking for. Download, flash in TWRP after doing a factory reset in TWRP.
[ROM] MCG24.251-5-5 100% Stock
https://forum.xda-developers.com/droid-turbo/general/rom-mcg24-251-5-5-100-stock-t3565795