Related
Noob here. I've searched the forums and have tried to piece together what I need to know for what I would like to do. I think I have a general understanding, but was hoping someone could verify or clarify.
I've got a Nexus 1 running 2.3.3. Never been rooted. All OTA updates.
What I would like is to root it so that I can delete crap like Facebook and Amazon and make room on the built-in memory. I don't want to unlock the boot-loader, and I don't want to flash custom ROMs. I do want control of what is stored where, the ability to move things to SD (even if they aren't marked for that (and yes, aware that that can cause problems sometimes)), and the ability to run Titanium backup.
As I understand it, all of that can be done with just root permission. But it seems that simple root for the N1 under 2.3.3 isn't available. Can anyone comment?
Thanks,
DT
Depends what you call simple...
Since you don't want to unlock the bootloader, you can try using the passimg method to revert to an earlier build of android, and then use any "simple root" available.
Unfortunately, a small percentage of users don't seem to be able to use the passimg method, and if you get an "main version is older" error, then it means you are among them...
Passimg method can be found in the wiki, under the unroot/restore guide (passimg method, using FRG33):
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Sent from my Nexus One using XDA Premium App
Good luck rooting, without trying to unlock the bootloader. It's simply not available atm I belive. Any particular reason you don't want to unlock the bootloader, beside the warranty?
root without unlocking bootloader
I'm still coming up to speed on this, so it's quite possible that I don't understand all the subtleties.
What I want to do is uninstall space-wasting preinstalled junk, and to run Titanium backup. I'm not interested (for now) in custom ROMs. I think I want to avoid unlocking the bootloader both for the warranty (a minor issue), convenience (another minor issue that could be overcome...), and because I want to retain as much of a "stock" device as possible, mostly to allow for future OTA updates. From what I've read, it sounds like a root would accomplish all that. Hence I'd rather avoid all the additional complications if a simple root were in fact available.
Thanks for the help,
DT
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Sent from my Nexus One using XDA Premium App
efrant said:
Unlocking the bootloader does not affect you device's ability to receive/install OTA updates, but removing "space-wasting preinstalled junk" will certainly prevent you from installing the OTA...
Click to expand...
Click to collapse
Totally agree. If you check the threads that were active during the OTA onslaught, many people could not install stock Gingerbread due to removing stock system apps (Facebook, Amazon, Twitter, etc...)
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
danger-rat said:
...but, if you have a custom recovery, you can still install the updates in a modified form.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Thanks for the info. I hadn't thought about the OTA being affected by removal of unwanted programs.
DT
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
efrant said:
Really? I was unaware of that. Would you mind posting a link to an OTA (say, Gingerbread for example) that I would be able to install on a stock Froyo ROM, which I had removed say, Amazon and Facebook?
Thanks.
Click to expand...
Click to collapse
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
danger-rat said:
I said modified - meaning rooted, or even just having the verifications taken out of the update script...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
I was just asking if anyone has done this (or does this), as I would certainly love to remove apps, as long as I can install future updates as they become available. (Doing that is beyond my knowledge...) I like my stock ROM, and I would certainly remove certain apps if I know someone would provide a "modified" update.zip for a stock ROM that doesn't check if Amazon, etc are installed.
What I don't want is to flash a new ROM every time an update came out...
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Easiest approach would probably be to take a backup of the stock image before you remove any apps, and restore it when you hear that an update is available...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
Restoring a NAND backup is essentially the same thing as flashing a new ROM, which is what I don't want to be doing. What would be good is to be able to install a modified/repacked/whatever-you-want-to-call-it OTA update file that has the check (which checks to see if apps are installed) disabled.
If it is just a line in a script that needs to be removed in an OTA, so that it will flash (with a custom recovery of course) with Amazon removed, it is surely doable, no? If it is doable, I am surprised that no one has done it for any of the updates... (at least I haven't seen any).
albundy2010 said:
It is very simple. If you remove stuff from the stock rom the ota will fail.
You will then need flash the same way as you would for any of the custom roms for updates.
Or you could manually put the stuff you removed back but that is probably more work then you want to do.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Thanks, but my question was: is it possible to modify an OTA zip file in such a way that it disables checking for installed apps like Amazon?
This would be helpful, and I had never thought of it until danger-rat mentioned it, but I may have misunderstood his post - he was probably talking about just flashing a new ROM, but that is not what I am interested in.
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
danger-rat said:
Yes, it's possible.
The update script is pretty big though, so you'd have your work cut out making sure you covered everything...
The other option would be to build an restore zip, that just reinstalled the apps you remove. Just add the apps to a zip as you restore them...
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
That sounds like a good idea.
This is what I'd like to do as a test:
1) Restore a stock Froyo ROM
2) Remove the Amazon.apk (and possibly others) from my ROM and save it somewhere (and whatever other files would be needed).
3) Create an update.zip file that would place the Amazon.apk file back to the correct directory in a stock ROM (i.e., odexed).
4) Flash that update.zip
5) Flash the Gingerbread OTA and see if it works.
Would you be able to point me to a guide on how to create a flashable zip? Again, I would need to be able to do this for an odexed ROM.
Thanks.
EDIT: Nevermind. I found it here: http://www.londatiga.net/it/how-to-create-android-update-zip-package/
ameedi600 said:
I would just passimg back to stock 2.2 and then root it with z4root
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
I agree this is what I did had no problems at all
How compareable is flashing roms on the Droid 3 compared to the HTC Eris. I'm tired of the lag and bloat and wish to try some new ROMs. I just don't want brick my phone. Rooting looked simple but I don't understand bootstrap/safestrap. Any help would be greatly appreciated!
Sent from my DROID3 using XDA App
jwanny10 said:
How compareable is flashing roms on the Droid 3 compared to the HTC Eris. I'm tired of the lag and bloat and wish to try some new ROMs. I just don't want brick my phone. Rooting looked simple but I don't understand bootstrap/safestrap. Any help would be greatly appreciated!
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Get bootstrap/safestrap from the internet -- install the app.
Run the app, install recovery.
Turn phone off.
Press m + power.
Scroll to BP Tools -- select it.
You're in custom recovery.
Which is better, bootstrap or safestrap?
Sent from my DROID3 using XDA App
jwanny10 said:
Which is better, bootstrap or safestrap?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Safestrap by far, the rom will install to another partition /preinstall rather that /system. This keeps the VZW rom intact to prevent bricking and still get OTAs easily. It's practically impossible to brick it using Safestrap.
Thanks, I'll be giving this a try!
Sent from my DROID3 using XDA App
So root (obviously), install safestrap, then I just boot into recovery via safestrap and flash Liberty 2.0? Just being anal, the more I read the less confident I get. Once I burst my cherry, I should feel better. Lol. Thanks for all the help everyone!
Sent from my DROID3 using XDA App
if ur stock 5.6.890, root, install otarootkeeper, install safestrap, open the app, install recovery, boot into recovery (during boot you will hit menu), backup data, toggle safe mode, install ROM, wipe data/cache, reboot
---
check http://hash-of-codes.blogspot.com/p/android-downloads.html for safestrap and CM7 downloads. also if you are on 5.7.894 you will need to use his patch to run any roms.
Did you mean wipe data/cache THEN install ROM?
Sent from my DROID3 using XDA App
jwanny10 said:
Did you mean wipe data/cache THEN install ROM?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
most roms either way will work
Rooted, install ota rootkeeper, installed and ran safestrap, rebooted into recovery, tried to turn on safe mode and got error. rebooted and tried to make a back up, got error.
Error occured when attempting to make backup image of /data
Happened both times. Am I royally screwed?
Phone works still but I don't dare flashing a ROM until I get safe mode. Hints?
If im not mistaken, rootkeeper doesnt need to be used unless you are going to install 5.7.894, as it messes with your roms ability to access SU
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
My phone had trouble mounting as R/W when i got a SU update via the superuser app off the market, i unprotected and updated my binary again and it worked fine. Keep OTA Rootkeeper installed, activate it before upgrading to an update that has no root method yet, then after you reinstall SU, and reestablish the symlink in your new update, remove the protection and verify you still have root. Its not necessary for CWM recovery tasks though
Droid 1 Rooted (ChevyNo1 0.9MV Kernel, LGB2.6)
Droid 3 Rooted (Stock Kernel, Custom lite De-bloat)
So if I lose ota rootkeeper, I can create a backup? My problem is I can't create a data backup or switch to safe mode. It gives me an error message that says unable to create backup image of /data. Am I corrupted? My phone still works as far as I know.
Sent from my DROID3 using XDA App
jwanny10 said:
So if I lose ota rootkeeper, I can create a backup? My problem is I can't create a data backup or switch to safe mode. It gives me an error message that says unable to create backup image of /data. Am I corrupted? My phone still works as far as I know.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Safestrap and bootstrap(I believe) have issues creating a backup of a file that cannot be changed. So yes if you remove it, then you be able to use safestrap correctly.
Sent from my DROID3 using XDA App
Removed ota rootkeeper changes still get "Error occurs in creating backup image of /data"
Any other ideas.
Running Verizon 5.6.890 stock blur. Used psouza one click root. Ran debloat script, but I don't think I did it right.
Sent from my DROID3 using XDA App
I tried to run the debloat restore and then make a backup, but still the same error. I noticed in the thread pertaining the debloat script that someone also gets it to run until myverizon.apk messes it.
Making backups and flashing new ROMs was so easy with the Eris. I apologized because I'm such a noob when it comes to Moto Droids and scripting.
Sent from my DROID3 using XDA App
I went and rooted my droid 4, and without knowing about safestrap, i started backing up and deleting apps with the free version of Titanium Backup. I now have a couple of apps that will not restore back into place, and i am unable to perform the upgrade. Since then, i have installed safestrap, and attempted to flash the rom at http://forum.xda-developers.com/showthread.php?t=1508341, but all i do is bootloop on my safe system. Any idea what i can do to fix the unsafe side so i can apply the 219 update? Am i kinda out of luck until the fastboot files are released?
try asking here
http://forum.xda-developers.com/forumdisplay.php?f=565
this forum is nearly dead, like 5 people a day visit here, very few people have a droid 4
i wish i could help more, but im not very good at this, but there are more people there that could help
What I'd do is download the stock recovery files that Hashcode has put up, and make sure you have anything you want backed up, and try advanced restore and flash all 3 options. As for the boot loop, did you try to clear cache and dalvik cache?
Are you referring to the [SAFESTRAP ROM] Stock MotoBlur 6.13.215 for Droid 4 at droidforums (forum won't let me post link) for hashcode's stock recovery? Or do you mean simply uninstalling the safestrap recovery from the safestrap app? I haven't played much with the stock recovery, so i'm not sure what 3 options you are referring to.
As far as the safe side, i wiped cache, wiped dalvik cache in the advanced menu, and done a factory reset... still bootloops...
Gengar1603 said:
Are you referring to the [SAFESTRAP ROM] Stock MotoBlur 6.13.215 for Droid 4 at droidforums (forum won't let me post link) for hashcode's stock recovery? Or do you mean simply uninstalling the safestrap recovery from the safestrap app? I haven't played much with the stock recovery, so i'm not sure what 3 options you are referring to.
As far as the safe side, i wiped cache, wiped dalvik cache in the advanced menu, and done a factory reset... still bootloops...
Click to expand...
Click to collapse
I am having the same issue. I was recommended to unzip the stock rom posted and attempt either a direct or adb push install of those apk's that are missing. Someone did this one by one and was successful in installing the 219 update.
You could attempt to install the stock rom through safestrap to get the update. please make sure that you are at full 100% charge as most roms wont flash correctly with less. I recommend getting full charge and flashing while still plugged in.
Hey guys, so what exactly is going on? You are missing apks on your main system, and your safe system bootloops?
So, your primary system functions, it just is missing bloatware, preventing you from updating? I just want to be sure I understand before making a recommendation.
Welp, i got some good news, i got the main system fixed and then updated. I took a stock 215 rom, extracted the /system/app folder and the system/build.prop to the sd card. Then i simply copied the contents of that folder into the /system/app on the root of the system with a file manager (used estrong's, other file managers that support root should work.), copied the build.prop to /system, and then did the update OTA. I lost safestrap and root, but i was able to reroot with moto fail... i have not tried reinstalling safestrap yet, nor have i mess with the bloatware like i did last time.
Gengar1603 said:
Welp, i got some good news, i got the main system fixed and then updated. I took a stock 215 rom, extracted the /system/app folder and the system/build.prop to the sd card. Then i simply copied the contents of that folder into the /system/app on the root of the system with a file manager (used estrong's, other file managers that support root should work.), copied the build.prop to /system, and then did the update OTA. I lost safestrap and root, but i was able to reroot with moto fail... i have not tried reinstalling safestrap yet, nor have i mess with the bloatware like i did last time.
Click to expand...
Click to collapse
I sort of did the same thing. I downloaded the rooted stock from and unzipped it. I then rebooted and manually tried to install the update and noted what files needed to be restored and then I coped them to dropbox then moved them to /system/app and it worked
I attempted to move the files but got an error when doing so saying I could not move them to the folder. The only file I seem to be getting the error with is backupassistantclient.apk but that might be because it is getting to that first and erroring out. Does Astro not support root to ove the files in /system, etc?
Sent from my DROID4 using XDA
azrael293 said:
I attempted to move the files but got an error when doing so saying I could not move them to the folder. The only file I seem to be getting the error with is backupassistantclient.apk but that might be because it is getting to that first and erroring out. Does Astro not support root to ove the files in /system, etc?
Sent from my DROID4 using XDA
Click to expand...
Click to collapse
Why don't you just flash it back to stock instead of messing it up more. I got a thread up here on our to do that.
I was playing once like that with the Nook Tablet. It took me 3 weeks to fix it. I hope you don't fall under the same crap with your phone
mrbidjey said:
Why don't you just flash it back to stock instead of messing it up more. I got a thread up here on our to do that.
I was playing once like that with the Nook Tablet. It took me 3 weeks to fix it. I hope you don't fall under the same crap with your phone
Click to expand...
Click to collapse
I will try to flash the stock Rom via safestrap and update. Thanks mrbidjey
Sent from my DROID4 using XDA
azrael293 said:
I will try to flash the stock Rom via safestrap and update. Thanks mrbidjey
Click to expand...
Click to collapse
I think he was referring to the fastboot files that just leaked a few days ago. Check out this thread
SGMD1 said:
I think he was referring to the fastboot files that just leaked a few days ago. Check out this thread
Click to expand...
Click to collapse
I actually read that thread right after replying on here. ill definitely go that route. thanks everyone
Sent from my DROID4 using XDA
I am trying to update to ics from 2.3.6 I have uninstalled safestrap and frozen root with otarootkeeper. I get hung up during install, so I checked my error log. It seems I am missing files from /preinstall specifically from /knowyourdevice which no longer exists. Is there a way of getting a copy so I don't need to go through fast boot? There was a link up elsewhere, but it's dead. Any help is greatly appreciated.
I recommend to flash fastboot 4.0.4 files.
I know, but this has turned into a pet project for me. I was really hoping to do it the hard way. There was a link up in the dev forum, but it's dead now...
I had the same issue when upgrading. Turns out, the update scans your system for ANY modifications that would signify you were, or had been rooted. You either need to completely remove anything that signifies you are rooted and any apps that require root, or sbf to either gb or ics. Doing a simple factory format still leaves files behind. Honestly, just doing an sbf would easier, as it ensures your system is 100% clean. If you need new links to the one click sbf, I can pm you a link later.
Sent from my DROID4 using xda premium
I had this problem and just downloaded the fastboot files, extracted the /preinstall archive from there, and copied it to my phone using adb. Simple.
Sent from my DROID4 using Tapatalk
Trying to find way to update to current update,however,unable because rooted and on ss currently.on 5.6.890 and would like to update,please help!!! TY!!!
Sent from my DROID3 using Tapatalk 2
rooting alone will not, block or stop updates
removing stock apks, and changing other things will
fastest way to fix, flash 890 xml recovery file in rsd lite, wipe data before or after, and try updating again
Sent from my Clear using xda premium
sd_shadow said:
rooting alone will not, block or stop updates
removing stock apks, and changing other things will
fastest way to fix, flash 890 xml recovery file in rsd lite, wipe data before or after, and try updating again
Sent from my Clear using xda premium
Click to expand...
Click to collapse
Where can I find files?
Sent from my DROID3 using Tapatalk 2
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my Clear using xda premium
If you never deleted anything from stock, the easiest way is to change safestrap to non-safe system (or stock, if you are on 3.05) and restart in stock. The update should appear pretty fast.
Again, if you ever debloated stock before installing Safestrap, then the RSD Lite is your best bet.
You would need to root again and reinstall safestrap recovery. Root again with Motofail, because Pete Souza's script no longer works with 5.7.906.
Motofail: http://vulnfactory.org/blog/2012/02/11/rooting-the-droid-4-a-failed-bounty-experiment/