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.
I got a new phone in yesterday and after starting up, I immediately rooted and installed Hashcode's tweaked version of Koush's Bootstrap Recovery. I did a Nandroid backup and everything went smoothly. However, I went on to flash Dark Droid and everything worked great, but after clicking "Bootstrap Recovery" after flashing (as I read that one should after flashing a new ROM), I received the following error:
Failure
/data/data/com.hashcode.droid3.bootstrap/files/surunner.sh
[Permission denied]
Any idea as to what's going on here? Thanks in advance.
Sent from my DROID3 using Tapatalk
Check superuser it looks like it did not get su permission.
i had some issues like that, it was solved by updateing busybox then su. worth a shot anyway.
eww245 said:
Check superuser it looks like it did not get su permission.
Click to expand...
Click to collapse
I checked SU and the Bootstrapper definitely has SU permissions. I also updated SU, but to no avail.
Anyone else?
did you check busybox?
lordgodgeneral said:
did you check busybox?
Click to expand...
Click to collapse
I'm not very familiar with how Busybox works or how to "check" it. Could you teach me?
Edit: So I know there is some version of Busybox installed on my phone (doesn't psouza's one-click root automatically install it?), but I went ahead and donwloaded the Busybox installer from the Market and installed the latest version. Still not working. I even removed permission from SU in order to regain permission but that also didn't work.
Bump...still can't figure it out. Thank you again in advance.
Hello Lyxdeslic,
Have you tried Koush's stock Droid 3 Bootstrap? I'm curious if his apk would also have the same error.
I've seen a total of 2 users describe the issues that you're seeing. And 1 case was fixed, but never was explained how to me, the other issue was never resolved.
The 1st reply has it correct. The issue is that the Bootstrap "thinks" it has SU permissions, but it doesn't. And I'm 100% sure it has to do with the upgrade of Superuser.apk tho for 99% of users, all of it works seemlessly.
I apologize for not being able to provide much help :/
Hashcode said:
Hello Lyxdeslic,
Have you tried Koush's stock Droid 3 Bootstrap? I'm curious if his apk would also have the same error.
I've seen a total of 2 users describe the issues that you're seeing. And 1 case was fixed, but never was explained how to me, the other issue was never resolved.
The 1st reply has it correct. The issue is that the Bootstrap "thinks" it has SU permissions, but it doesn't. And I'm 100% sure it has to do with the upgrade of Superuser.apk tho for 99% of users, all of it works seemlessly.
I apologize for not being able to provide much help :/
Click to expand...
Click to collapse
My friend, no need to apologize at all. I appreciate the response, as I was considering PMing you but I didn't want to be a bother considering you probably get tons of PMs a day.
However, I uninstalled your tweaked Bootstrap this morning (also deleted data prior) and reinstalled it, and permissions were re-granted and it works now. I just realized that this did indeed happen after SU binaries were updated. All seems to be working well now.
One last quick question; after re-installing, if I boot into Recovery mode...will your Bootstrap still recognize and find the Nandroid backup on my SD card, which was also created with your Bootstrap during the first installation? I don't have my phone on me at the moment and I forgot to test.
Thanks again for the support. Kudos to you.
uninstall bootstrap and try the new safestrap
The Solutor said:
uninstall bootstrap and try the new safestrap
Click to expand...
Click to collapse
The Safestrap isn't to be used with ROMs other than CM7 Alpha and the stock MotoBlur ROM, if I'm not mistaken.
Lyxdeslic said:
The Safestrap isn't to be used with ROMs other than CM7 Alpha and the stock MotoBlur ROM, if I'm not mistaken.
Click to expand...
Click to collapse
It let to enter in the recovery, and is enough for me.
Ok, right...but why would you want to enter recovery in case of a bootloop when you can't flash the ROM you want to to restore your system? I mean yea Hashcode did create the MotoBlur ROM compatible with Safestrap only but still. Both options (safestrap and bootstrap) are needed, in my opinion.
Sent from my DROID3 using Tapatalk
Lyxdeslic said:
Ok, right...but why would you want to enter recovery in case of a bootloop when you can't flash the ROM you want to to restore your system? I mean yea Hashcode did create the MotoBlur ROM compatible with Safestrap only but still. Both options (safestrap and bootstrap) are needed, in my opinion.
Click to expand...
Click to collapse
I think that trying yourself is better than theorize...
They are two different sw created for different purposes, but those purposes are overlapping on the part that counts: booting in to recovery.
The Solutor said:
I think that trying yourself is better than theorize...
They are two different sw created for different purposes, but those purposes are overlapping on the part that counts: booting in to recovery.
Click to expand...
Click to collapse
Correct. They both get you into recovery...but he wants to flash a ROM other than CM or stock. Which Safestrap has no use for. He needs a bootstrap, no ifs ands or buts. Safestrap is of no use to him.
redsox985 said:
Correct. They both get you into recovery..
Click to expand...
Click to collapse
This is what is needed to flash a rom (whatever rom), to do a nandroid backup and so on.
Period.
If you don't use a safestrap enabled rom just don't use the related feature
The Solutor said:
This is what is needed to flash a rom (whatever rom), to do a nandroid backup and so on.
Period.
If you don't use a safestrap enabled rom just don't use the related feature
Click to expand...
Click to collapse
Safestrap is different in the way that it flashed roms. So. There.
OP:
You can install safestrap (after uninstalling whatever recovery app you had before) and hold tight until later tonight or tomorrow when I update DarkDroid with safestrap compatibility.
dpwhitty11 said:
Safestrap is different in the way that it flashed roms. So. There.
Click to expand...
Click to collapse
Listen, I'm used to talk just when I'm sure about things.
Right now I've installed a rom starting with safestrap, and works perfectly.
So why don't try yourself instead of posting guesses as facts ?
The Solutor said:
So why don't try yourself instead of posting guesses as facts ?
Click to expand...
Click to collapse
lol, ok buddy.
Don't get all offensive.
Sent from my DROID3 using XDA App
dpwhitty11 said:
OP:
You can install safestrap (after uninstalling whatever recovery app you had before) and hold tight until later tonight or tomorrow when I update DarkDroid with safestrap compatibility.
Click to expand...
Click to collapse
Looking forward to your latest
Hello. First off, I want to thank everyone for their hard work here. I have followed many tutorials and have seen many great conversations to keep noobs like me from making mistakes when trying to delve into the world of ROMs and rooting. However, I did encounter some troubles while installing the ICS rom onto my bionic (running on .902). I think I may have accidentally overwritten the stock rom backup that I made with safe strap or whatever that app is (I'm sorry, like I said, I am a complete noob). Is there a way to restore the phone to stock, as in before I even touched it, even if the backup I made during the process is gone by my mistake?
I'm sure this has been asked a million times, and if so, I apologize, but as I noob, I have no idea how to even begin to search for clues. Walkthroughs would be nice, but links are fine too, since I'm sure there are plenty of the same questions out there.
Thanks!!!
Pete's motorola tools check it out you will find what you need there just google Pete's tool bionic
Sent from my XT875 using XDA App
Also I believe if you disable safe mode it will boot up rooted stock from don't quote me on that I am not for sure. Also I believe there is a unroot method in development not sure if it is for 902 or not though..
Sent from my XT875 using XDA App
Thanks for the info!
No problem here to help
Sent from my AXI0M IONIC using XDA App
R3l3as3DRoot and for3v3r root will take you back to 886
Sent from the Evil Empire
Thanks! Can that be used after the .902 update? Is it possible to do a dual-boot type deal between stock and the ICS version I have installed? I've seen mentions of dual-boot around here, but I can't get a clear grasp on whether it is possible or not, or if so, how to do it. Thank you very much!
Lonepalm said:
Thanks! Can that be used after the .902 update? Is it possible to do a dual-boot type deal between stock and the ICS version I have installed? I've seen mentions of dual-boot around here, but I can't get a clear grasp on whether it is possible or not, or if so, how to do it. Thank you very much!
Click to expand...
Click to collapse
Yeah I'm sure you can.
Get on stock .902(here).
Install SafeStrap.
Backup Stock Rom by Toggling "SafeMode"
Boot up ICS.
When you want to go to Stock .902 undo "SafeMode" and the Stock Rom should boot up on Reboot
Thanks for the answer! Hopefully I can give this a shot soon!
Lonepalm said:
Thanks for the answer! Hopefully I can give this a shot soon!
Click to expand...
Click to collapse
Yeah those instructions above are correct. I just came back from the AOKP ICS Rom to stock. 902. Worked fine. I have all my apps and stuff too.
Sent from my DROID BIONIC using Tapatalk
Don't know what I'm doing wrong here, but when I plug my phone in to my PC, the phone realizes it, but doesn't seem like the PC does. Also, when I open RSD Lite and try to load the file, it doesn't do anything after clicking "Start". Please help me try to diagnose what I may be doing wrong if you can! Thank you!
Lonepalm said:
Don't know what I'm doing wrong here, but when I plug my phone in to my PC, the phone realizes it, but doesn't seem like the PC does. Also, when I open RSD Lite and try to load the file, it doesn't do anything after clicking "Start". Please help me try to diagnose what I may be doing wrong if you can! Thank you!
Click to expand...
Click to collapse
Enable Usb Debugging and Unknown Sources. Download Motohelper drivers
Sent from my DROID BIONIC using Tapatalk
I'm sorry I probably should be a little more specific. I have both of those enabled and I do have the Motohelper drivers installed. I am following the steps here: http://forum.xda-developers.com/showthread.php?p=22758211#post22758211
On step 8, I do not see a file named FXZ or a file with that extension, but I figured it was the file with the name that the zip file had. I chose that file after clicking "..." and hit Start, but it doesn't do anything.
I am running the ICS version cyanogen mod 9.0.0-rc0-droid_bionic-kang build number alpha_2012_02_10
I already have SafeStrap installed (used that to get this rom on). So, looks like I'm stuck on or around step 8 from the other steps posted. Once I can get past that, I can continue with the steps posted in this thread!
Thanks!!!
Lonepalm said:
I'm sorry I probably should be a little more specific. I have both of those enabled and I do have the Motohelper drivers installed. I am following the steps here: http://forum.xda-developers.com/showthread.php?p=22758211#post22758211
On step 8, I do not see a file named FXZ or a file with that extension, but I figured it was the file with the name that the zip file had. I chose that file after clicking "..." and hit Start, but it doesn't do anything.
I am running the ICS version cyanogen mod 9.0.0-rc0-droid_bionic-kang build number alpha_2012_02_10
I already have SafeStrap installed (used that to get this rom on). So, looks like I'm stuck on or around step 8 from the other steps posted. Once I can get past that, I can continue with the steps posted in this thread!
Thanks!!!
Click to expand...
Click to collapse
SafeStrap disables ADB(that Im sure of) which will not let RSD run(im pretty sure) you have to select the xml file
Sent from my DROID BIONIC using Tapatalk
Yes, the XML file is the one I select. However, it will not do anything in RSD. Is there anything I can do to enable ADB in order to let RSD run?
Update: I found a way to do it. I think things are going okay so far. Looks like it is installing. If it does install successfully, I would like to do everything perfectly right going forward.
So, after this is installed, I will want to:
1. Get root access again using Motofail? I assume doing this return to stock will remove root access.
2. Install SafeStrap. Once that is done, I toggle Safemode to enabled, which will backup my stock rom and protect it from being overwritten?
3. Then, flash ICS from the zip files on my sdcard?
Lonepalm said:
Update: I found a way to do it. I think things are going okay so far. Looks like it is installing. If it does install successfully, I would like to do everything perfectly right going forward.
So, after this is installed, I will want to:
1. Get root access again using Motofail? I assume doing this return to stock will remove root access.
2. Install SafeStrap. Once that is done, I toggle Safemode to enabled, which will backup my stock rom and protect it from being overwritten?
3. Then, flash ICS from the zip files on my sdcard?
Click to expand...
Click to collapse
Yes sir.
Sent from my DROID BIONIC using Tapatalk
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? I got confused with that.
Afterwards, I dl safestrap once I'm rooted? or should I just dl it and put it onto my phone all at once?
Apologies for the noobness. I'd rather be a noob asking questions than a retard who goes ahead and does things and finds out he screwed up too late.
Rooting is done to get superuser permissions within Android so you can install some advanced apps and modify system files which can all be done from within the stock ROM. Rooting then flashing an unofficial ROM is a little more advanced and something I haven't done yet so I can't help you much there. I'm waiting for something a little more stable since my Droid 3 is my main phone. You can read Hash of Codes site (the developer of ICS/JB for the Droid 3) on how to safestrap:
http://blog.hash-of-codes.com/how-to-safestrap/
To root use Motofail. I know it says its for the Droid 4 but the original Droid 3 root exploit was patched with the latest OTA so we have to use the Droid 4 method called Motofail:
http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/
DróidScìon said:
As the title says, I'd like to root, but with somewhat limited knowledge on the phone and it's processes, and no knowledge of scripting/coding, I want to avoid taking too much risk.
I've been stock with the D3 since I got the phone in 2011, found out we aren't getting ICS, and we aren't getting unlocked by Moto. (pissed off!) >.<
The way I see it I have 2 options, 1) stay stock until my contract is up in march and get a new phone, or 2) Give root a go, and Have ICS ported to me via a Custom Rom, and do more research as I go. (I like being hands-on when it comes to learning).
.
Click to expand...
Click to collapse
My D3 has Maverick as non-safe for daily driver and the latest Hashcode for fun. I find that to be the best combination. Once Hash finishes the camera and JB is working reasonable well, JB will be my DD.
I also have an SGS3, TF300T, and a Spica, all of them rooted.
once rooted, make sure you use safe strap. It makes roms easy to try out before having to settle
Sent from my DROID3 using Tapatalk
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
DróidScìon said:
Alright, so it appears I have been rooted, and still looks like I'm in .906 OTA. It was pretty easy using Motofail, actually. So, now I have Superuser and Titanium Backup(free, for now) on my D3.
Now, you guys mentioned Safestrap? Can you guys give me a suggestion on which one to use? There appear to be a few of them. 1 is SAFESTRAP v2.10 Recovery (Kexec) and the other is a Tweaked version of Safestrap v1.08e (Non-Kex) which one is better, or a better question, whats the difference between the 2?
Click to expand...
Click to collapse
Safestrap 1.08 is the 'normal' ssafestrap
Safestrap 1.08e/f/g is an advanced safestrap with extra features like touch etc but not by hashcode
Safestrap 2.10 is the latest which allows the new kernel with the kexec ICS/JB to be used.
2.10 It appears to also work fine with normal roms so i'd use that
DróidScìon said:
As to my phone, I am running 906 OTA Stock as it gets .. -_-' I'd like to root using
http://forum.xda-developers.com/showthread.php?t=1686911 <-- ovelayer's method in this thread. (thank you Ovelayer, I can't seem to find that button so I'm just acknowledging you here since I'm new to this kind-of thing).
I just need some clarification
in his thread it says to dl the 1-click .exe, then the Motofail root tool? or is that also a way to root? .
Click to expand...
Click to collapse
If you were stock 906, there was no reason to run the 1-click.exe - that's only for people who rooted their phones and deleted bloatware to get the phone back to stock, or people whose phones are bricked somehow. Coming from stock, just running Motofail was enough to root.
I will concur with everyone here that running rooting, installing and running Safestrap, and installing a custom ROM - and leaving your rooted stock alone - is the best way to go. It will be a lot easier to unroot later on if you want to sell the phone, etc.
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It doesn't matter. Choose which has enough space.
DróidScìon said:
Alright, Safestrap 2.01 is installed. According to Hash's Blog, I should create a backup when in the Recovery Menu since its my first time accessing the Safestrap Menu. Can I get a little more detail as to how I do this? When I select backup, it asks if I want to backup from Internal SD or External? I'm assuming Internal, but I just want to err on the side of caution and ask those who already know.
Click to expand...
Click to collapse
It's asking where to backup TO, like the post above me, choose wherever has space. Backups are about 1GB. You may wish to move it to your computer after if you don't have much space on your device. You can always stick it back on your external sd via card reader if needed, but it's really hard to brick while using safestrap
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Sent from my XT860 using xda premium
I saw that, and before I rooted, I did a Factory Reset on the phone and formatted my SD card. So I have 11+gig free on Internal and 15+gigs on External.
Now, I just need to learn to Flash RoMs (probably more to it than just hitting a button that says flash .zip) and find some info on the "must-have" apps for a rooted phone.
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
DróidScìon said:
Well guys, I've successfully installed CM9 Kexec ICS Sept 5th update from Hashcode on my Droid 3! Now, another big question, How will I restore stuff like contact and account info? I've read somewhere around here that Restoring Data from my google account is a bad idea?? Are there other ways of doing so without Titanium Backup, or should I just go ahead and buy the Pro Key? (currently limited funding)
Click to expand...
Click to collapse
If your contacts are on your google account they will show up.
What other account info do you mean?
You should go ahead and restore contacts. just go to Settings>Accounts and Sync>Google, then turn contacts sync on.
Endoroid said:
Also one of the most common errors for noobs on safestrap is, the first time you engage safe mode, you must flash a rom. Since its using a different partition for system, it's currently empty and if you switch to safe and try to boot you will get a black screen as you are booting an empty partition. All gingerbread roms are stable but there are no ics roms that are fully functional, although one is in the works
Click to expand...
Click to collapse
I must have made another noob mistake. Everything went well, up until my first startup with the new OS (cyanogenmod9). It has been at the startup screen for over 15minutes right now. I must say, it is one awesome startup screen, with the blue effects and all, but I would love to get to the desktop/homescreen, haha.
If you guys have any advice I would greatly appreciate it. This is a Droid 3, it was rooted a couple hours ago, I did the safestrap as described, created a backup file, etc. My only guess is I jumped the gun by trying this OS on my Droid3 and it may still be under development? FWIW to you, this is the first I've rooted or modded a smartphone in my life, from 0-full speed in a couple hours is what I was shooting for using everyone elses experience.
thanks
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Phibernaut said:
Make sure you wiped the data/user settings in Safestrap. You lose your apps & settings but those items from a previous install can cause that type of boot issue.
Sent from my XT862 using xda app-developers app
Click to expand...
Click to collapse
thanks. since my last post I used a more detailed how-to, and wiped 3 different areas for data. Now, i had only a black screen (with power, barely lit) and it never even got to the cool blue screen.
I'm currently in safestrap after pulling my battery again, just trying to figure out how to revert back to my standard OS (rooted) and try a ROM like MavRom since it's suppoedly fully capable and stable. I'd love ICS, but I just want a working phone right now
---------- Post added at 10:25 PM ---------- Previous post was at 10:14 PM ----------
good news is, I did enough steps correctly, that I was able to startup in my unsafe mode, and my normal rooted system is functioning fine. That makes me very happy.
This duel boot thing is pretty cool, reminds me of having bootable thumb drives on my old linux system with different OS's. I hope i can get a seperate OS working, however, that fits my needs for a day to day functional phone, without all of Verizon's crap on it
Once rooted use titanium backup to back up apps and data.
Only restore with the same ROM though, the following is in increasing order of risk
restore app only to exact same ROM+version
restore app+data to same ROM+ver
restore app only to update of same ROM
restore app+data to updated ROM version
play chicken with a bus on a highway
restore apps to different kernel e.g. CM7 backup => restore to CM9
check to see what a gun firing looks like down the barrel
restore app+data to different kernel
restore app+data to an older ROM or kernel
do anything at all with system apps+data if you don't know what you're doing
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