[Q] understandable nexus one unlock/root/upgrade - Upgrading, Modifying and Unlocking

Hi, I've a nexus one with android 2.0 stock! After loosing my contact list and had to restore or totally replace my phone several times because my cell provider was unable to detect/repair/help ... I've decide to do it by myself! ... my nexus one was stuck on X ... so I've unlock bootloader and fastboot recovery a RA-passion version ... black screen ... tried lots of 2.0, 2.1, 2.2 available version ... without success ... always black screen ... so I decide to install gingerbread 2.3 cyanogen ... working (root, superuser, etc) but without gapps so useless for me ... ive try some gapps for gingerbread ... didnt work (was stuck on cyanogen animation) ... so after 2 days I've decide to use PASSIMG.zip to install a factory recovery ... got android 2.2 ... installed my fb, twitter,gmail account ... installed my last apps ... and I've got a popups "system update" ... after rebooting android 2.3.4 build GRJ22 was installed with all gapps without root, look like a legal copy!
My questions:
1- Is it possible to root 2.3.4? if yes, how?
2- why 2.3.4 installed by itself?
3- how can I do a real downgrade?
4- and since Im with 2.3.4 do I really need trying to roots it or its useless?
thanks

Hi,
To answer your questions:
=> At this moment there is no possible way of rooting version 2.3.4
=> To do a real downgrade, go to the link below and do the PASSIMG method, using FRG83. Execute, and you'll be on 2.2.1.
http://forum.xda-developers.com/wik...des_&_Tutorials#Unroot_.2F_Restore_your_Nexus
Click to expand...
Click to collapse
Once you are on 2.2.1 use the following method to update manual to 2.3.3
http://www.intomobile.com/2011/02/24/how-to-manually-update-your-nexus-one-to-android-2-3-3/
Click to expand...
Click to collapse
Now we come to the process of rooting your nexus one to 2.3.4 using stock ROM
1) Root your GRI40 (2.3.3) build;
2) Flash a custom recovery (like Amon_RA 2.2.1, from his thread), using ROM Manager from the market, or do it manually using flash_image;
2) Download the GRJ22 (2.3.4) update and place it in the root of your sdcard;
3) Download the su-2.3.6.1-ef-signed.zip file and place it in the root of your sdcard;
4) Reboot into recovery;
5) If you flash any other recovery besides Amon_RA 1.9, turn signature verification OFF (it is off by default in 1.9);
6) Flash the GRJ22 update, but do NOT reboot once it finishes flashing;
7) Re-read step 6. It is important that you do not reboot, otherwise you are stuck;
8) Flash the su-2.3.6.1-ef-signed.zip file;
9) Reboot;
10) At this point, you are rooted, but you have lost the stock recovery. If you want a custom recovery to stick, follow the next steps;
11) Download a terminal emulator or a root file manager from the market;
12) Delete these two files from your ROM: /system/recovery-from-boot.p and /system/etc/install-recovery.sh
13) Re-flash the custom recovery you want.
14) Reboot.
The SU.Zip file is below:
http://dl.dropbox.com/u/6408470/su-releases/su-2.3.6.1-ef-signed.zip
Click to expand...
Click to collapse
The Update file for 2.3.4 is below:
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
Click to expand...
Click to collapse
Hope this helps. I don't credit for this. Had the same problem and got alot of info and finally figured it out.
Have fun

Related

[HOW-TO] Simplified Root + Recovery + Custom ROM

This is a simplified guide for those new to rooting & flashing a custom ROM on the Optimus V. No need to type complex commands that are hard to follow and prone to mistakes. Basically there are 3 main steps: Root, Install custom recovery, & flash custom ROM.
Windows Drivers for the Optimus V (Optional but suggested):
http://www.lg-phones.org/wp-content/uploads/LG-Optimus-V.zip
Rooting
Rooting is the process of gaining administrative rights to the phone so one can do customizations that aren't normally allowed. Root by itself doesn't do anything interesting, unless there's an app that needs it. The fancy stuff comes from custom ROMs. Just remember Virgin Mobile Activation only works on Froyo ROMs, so do it before going to Gingerbread. The easiest way to root nowadays is to use GingerBreak. It can be found here:
[26.04.2011][v1.2] GingerBreak APK (root for GingerBread) - xda-developers
Instruction Steps:
1. Turn on USB Debugging (Settings - Applications - Development)
2. Copy the GingerBreak.apk to a /sdcard dir, then using a 'file manager' app (search for one in Android Market) install it like a regular app.
3. It can take up to 10 minutes, and will reboot automatically when complete (rooted), if attempt fails, reboot manually & run it again.
Install custom recovery image
The recovery image is an alternative bootup instead of normal Android Operating System. It allows low-level operations such as backup/restore a ROM, wipe partitions, and flash ROMs.
4. Download and copy the recovery image VM670NH_recovery.img (works with new & old OV screens) onto your /sdcard.
5. Install the Flash Image GUI app (save the .apk to a /sdcard directory, then open it with file manager) Run the app & select 'Recovery Image' option with the file above.
Flash Custom ROM
I.H.O CyanogenMod 7 ROM (Gingerbread)
6. Copy the unextracted ROM .zip that you wish to install to the /sdcard dir. Also if installing a CyanogenMod Gingerbread ROM, the unextracted gapps.zip also needs to be placed in the same dir to flash right after the ROM .zip.
7. Boot into Clockworkmod recovery mode (From powered off state, hold vol-down, home, and power button until the LG logo appears).
8. FIRST, BACKUP ORIGINAL ROM! Don't continue until this is successful. Use vol-up/down, camera, & back keys to navigate in recovery.
9. Wipe Data/Factory Reset, wipe cache partition. Under Advanced submenu, wipe dalvik-cache. Then uner Mounts & Storage submenu, format all partitions EXCEPT /sdcard.
10. Flash the custom ROM.zip from sdcard and gapps.zip too if going to a CyanogenMod ROM
11. Reboot and enjoy the new ROM, the first boot takes longer than usual, also some problems may disappear after rebooting.
NOTES:
- NEVER use Android Settings 'Factory Reset' from now on, only do factory reset & wipes from within recovery mode. Most ROMs should have this option removed from the Android settings.
- Some newer Optimus V screens hardware changed, see link: [FIX]Black screen with custom recovery and custom roms (BobZHome's IHO recovery from the Wiki binary -> recovery page also works with newer screens.)
- If restoring a backed up ROM in CWM recovery gives 'MD5 mismatch' error (likely caused by renaming a ROM backup). Try this fix:
# cd /sdcard/clockworkmod/backup/<name_of_backup>
# rm nandroid.md5
# md5sum *img > nandroid.md5
- If you ever want to restore to original stock ROM (ONLY on OV's with older screen), with original recovery and UNrooted:
http://www.prepaidandroid.org/index...e_your_Optimus_V_to_almost_original_condition
titanium backup?
Excellent guide for the likes of me (noob), you might wanna mention titanium backup too
help
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Zachary droid said:
Hey u have a great step by step guide, however when I run gingerbreak to root it gives me an error I kno u said reboot manually and I did twice and I couldn't get it to work, any thoughts of to why it did this twice thanks
Click to expand...
Click to collapse
What is the exact error you're getting? I believe you have to keep retrying, maybe up to 10 times.
Thanks a lot.Real helpful
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
KidGusto said:
Will this work for LG Optimus S? It's been difficult to find specific information for this phone.
Thanks.
Click to expand...
Click to collapse
the windows drivers and gingerbreak will work.
you'll need an optimus S custom recovery and rom, though. If you use optimus V software, your home and menu keys will be backwards, and there may be other little issues with the network.
look on android central forums for optimus S development and you'll find roms and recoveries no problem.
Thank you for this. The Rom manager method is great, i was afraid not to brick my optimus one with the adb shell crap and pc connection. They should make a nici sticky like this in the euro section, not with adb crap.
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
cobraextreme said:
I used these steps and they worked great for rooting, but I'm having a problem with recovery. I flashed CWM 3.2.0.1 from ROM Manager and it appeared to work fine, but when I try to boot into recovery I just get a blank screen.
I have done the following:
Busybox 1.19.2 from Stericson, installed to /system/bin
Superuser from market, updated to 2.3.6.3, su is 2.3.2-efgh
Used ROM Manager 4.4.0.7 to flash CWM recovery 3.2.0.1
I've tried getting to recovery using Home+Vol Dn+Power, or the reboot menu option in rom manager, and just get the blank screen.
Anyone run into this or have suggestions?
Click to expand...
Click to collapse
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
bigsupersquid said:
[fix]black screen in custom recovery or custom roms
you probably have the newer screen type, which it appears the older custom kernels need a .config setting changed before building to support.
you'll have to use flash_image in adb or terminal.
probably. full instructions and downloads at that link.
yay, you didn't flash a rom through rom manager at the same time! or it'd be a lot harder.
Click to expand...
Click to collapse
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
cobraextreme said:
That did the trick! Thanks!
It would be great to get a sticky about this in here. It's pretty easy to miss the newer display issue if you're just now looking into this forum and don't check AC first.
Click to expand...
Click to collapse
Updated original post with link for the new OV screens.
lamenramen said:
Can this guide by updated, with more details?
The menu options in ROM manager are not the same anymore, and I am flailing around trying to figure out which options to hit.
I'm stuck at the LG logo boot up screen after doing what I think is flashing the bumblebee ROM step. (step 10 in the guide).
Click to expand...
Click to collapse
ROM Manager is only supposed to be use to flash the Clockworkmod recovery image, then everything else is done by booting into the recovery mode. ROM manager's other features should not be used on the OV.
Whyzor said:
Updated original post with link for the new OV screens.
...
Click to expand...
Click to collapse
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
bigsupersquid said:
the only big problem left is getting the "back to stock" up to par for the newer OV's...
if someone could upload the critical part of a nandroid made from the newer stock system after rooting but before installing a custom rom, a more up-to-date back to stock guide could be put up with the newer files, or at least the older files patched with the newer kernel.
anyone want to upload the boot.img from a first nandroid backup off of a newer ov? the boot.img doesn't have any personal info, and it's got the newer kernel, which is all that's needed to fix up the older back-to-stock nandroid files.
Click to expand...
Click to collapse
I think there's about an 85% chance that this contains the kernel that you're looking for; not sure if you have some way to deal with that 15% uncertainty but hopefully it's helpful.
Questions about ROM Manager
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
luwizwiz said:
Hi, can I get a clear clarification about installing the ROM Manager on my LG Optimus p500, when your about to install the ClockwordMod Recovery you would have to select the phone model. LG p500 is not listed. Is there an alternative to it?
Click to expand...
Click to collapse
This thread is under the Optimus V development section, you should ask questions about the p500 in this forum section:
http://forum.xda-developers.com/forumdisplay.php?f=839
Thanks, i didn't notice that its for Optimus V, i have a Optimus One. many thanks
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
ct200 said:
Complete noob here, I mean a complete noob...first cell phone.
I was hoping to tether my new OV, but i quickly found out i have software version 2.2.2 which does not allow me to turn on hot spots. So I heard I can root my phone to get around this. I did stes 1-3 without issue, now I am stuck on step 3a. When i try to install busybox (not sure what this does for me?), i get the follow error/message "It looks like you have Busybox installed, but there are multiple copies still installed. /system/bin/ is currently as RW. This means that something may have gone wrong in the installation process. Please verify on your end that everything is correctly installed and working.
What do I verify? There is no Busybox app to run, only to install so it looks like the install failed?
Click to expand...
Click to collapse
If you go into 'adb shell' from the PC with phone connected, or open the app 'terminal emulator' to get a unix prompt, and type 'busybox', you should see a list of commands. If you get a no command found, then it's not installed. It's suggested to install so you can run unix commands, but not really needed. Root & custom recovery are the important ones. You're probably safe to continue, just make sure to make a backup in recovery mode before doing anything else.

[Q] Flashing Defy with MIUI, Howto?

Hey Guys,
I spent almost 3 hours to flash my Motorola Defy, I tried many things but eventually everything FAILED .
Things i tried till now.
Flashing using OpenRecovery ( I just tried to use Official Motorola Milestone guide)
Result: When ever i try to install update.zip in stock recovery it says signature verification failed.
Installed 2ndInit tried to run .zip file from ClockworkMod Recovery
Result: FAILED!! unable to mount sdcard
I rooted the phone using SuperOneClickv2.1.1-ShortFuse, I don't know what else to do can anyone guide/suggest this whole how-to process?
I've attached a whole system info screenshot for reference
You need to upgrade to Froyo 2.2 firmware in order to install MIUI.
Sent from Android 2.3.7
kgthenerd said:
Hey Guys,
I spent almost 3 hours to flash my Motorola Defy, I tried many things but eventually everything FAILED .
Things i tried till now.
Flashing using OpenRecovery ( I just tried to use Official Motorola Milestone guide)
Result: When ever i try to install update.zip in stock recovery it says signature verification failed.
Installed 2ndInit tried to run .zip file from ClockworkMod Recovery
Result: FAILED!! unable to mount sdcard
I rooted the phone using SuperOneClickv2.1.1-ShortFuse, I don't know what else to do can anyone guide/suggest this whole how-to process?
I've attached a whole system info screenshot for reference
Click to expand...
Click to collapse
Use this thread http://forum.xda-developers.com/showthread.php?t=1216982 It will tell you anything you need to know to begin flashing.
1. froyo
2. root
3. 2nd int
4. recovery full wipe
5. instal from zip
6. enjoy your new rom
[SOLVED] Flashing Defy with MIUI, Howto?
strikoo said:
1. froyo
2. root
3. 2nd int
4. recovery full wipe
5. instal from zip
6. enjoy your new rom
Click to expand...
Click to collapse
Thanks man it's working, I flashed with this SBF
JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS 03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf
http://forum.xda-developers.com/showthread.php?t=1093352
Click to expand...
Click to collapse
Flashed MIUI, it's working great
But anyone have a better keyboard for this devices man I hate default android keyboard
SOLVED!! Just installed this one it works great atleast better than Android Keyboard
Code:
http://forum.xda-developers.com/showthread.php?t=624416
Thanks to all for helping
You can also try smart keyboard pro
it has a lots of skins and lot of options. Enjoy miui, I'm currently on pikachu edition, miui is a true eye candy for defy screen.

Wildfire ROM update - backup questions

Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself

Galaxy GIO to root

I have just bought a S5660, and it cannot get rooted , I have used a few update.zip and used oneclick without success
here are the details:
baseband version: S5660XXKT6
android version : 2.3.6
kernel version [email protected]#1
build number: GINGERBREAD.XXKTI
can someone help me?
http://www.mediafire.com/?coocq359vv15w5p
Try this. Also , are you sure it`s not rooted ? Verify if superuser is installed or get a file manager like Root Browser Lite and try to access root files.
I am sure it is not rooted. Il will compare tonight the file you provide with the ones I got.
If you want to root your gio just install a rom
Sent from my GT-S5660 using Tapatalk 2
fsosson said:
I have just bought a S5660, and it cannot get rooted , I have used a few update.zip and used oneclick without success
here are the details:
baseband version: S5660XXKT6
android version : 2.3.6
kernel version [email protected]#1
build number: GINGERBREAD.XXKTI
can someone help me?
Click to expand...
Click to collapse
Seek, and you shall find; http://forum.xda-developers.com/showthread.php?t=1111414 and http://forum.xda-developers.com/showthread.php?t=1623393 and
http://forum.xda-developers.com/showthread.php?t=1397120
And if it still wont root, then post here again with maybe a little bit more info about what's wrong --> e.g. what recovery have you installed, what error message do you get, etc...
- H
hhaznadar85 said:
Seek, and you shall find; http://forum.xda-developers.com/showthread.php?t=1111414 and http://forum.xda-developers.com/showthread.php?t=1623393 and
http://forum.xda-developers.com/showthread.php?t=1397120
And if it still wont root, then post here again with maybe a little bit more info about what's wrong --> e.g. what recovery have you installed, what error message do you get, etc...
- H
Click to expand...
Click to collapse
Hi,
I have used latest update.zip files to root my GIO. Maybe the way I do is wrong.
I have installed ROM Manager, I have rebooted my GIO in system recovery mode. But in the bottom of the screen and before applying update.zip there is a message:
--- Appling Multi-CSC --
Can't access to '/system/csc/MST/system'.
I can apply update.zip without any error message but it does not root the phone.
fsosson said:
Hi,
I have used latest update.zip files to root my GIO. Maybe the way I do is wrong.
I have installed ROM Manager, I have rebooted my GIO in system recovery mode. But in the bottom of the screen and before applying update.zip there is a message:
--- Appling Multi-CSC --
Can't access to '/system/csc/MST/system'.
I can apply update.zip without any error message but it does not root the phone.
Click to expand...
Click to collapse
Dude!! DON'T USE ROM Manager it will hard brick or phone. Just use the original way to root ur device.
Sent from my GT-S5660 using xda app-developers app
batman38102 said:
Dude!! DON'T USE ROM Manager it will hard brick or phone. Just use the original way to root ur device.
Sent from my GT-S5660 using xda app-developers app
Click to expand...
Click to collapse
OK. Could you please explain how to?
http://db.tt/XZRwKuZS
Flash this via cwm.
It worked for me on gingerbread so it must work for you too.
Sent from my GT-S5660 using xda premium
jkoetsier said:
http://db.tt/XZRwKuZS
Flash this via cwm.
It worked for me on gingerbread so it must work for you too.
Sent from my GT-S5660 using xda premium
Click to expand...
Click to collapse
I have rebooted in recovery mode, launched CWM then applied the Update.zip you linked but the phone is not rooted
Weird
I think only option is installing custom rom which is pre rooted
Sent from my GT-S5660 using xda premium
dont unzip the file to root the phone...... just put it as it is on a sd card and follow the instructions you were given.
The First Step In Modification of you Gio is Rooting , everything starts from Rooting. Many Applications Require Root access for working.
------------------------------------------------------------------------------------
How to Root Samsung Galaxy gio
Download root gb updated.zip file. and copy to SD card (not in any folder)
1. Shutdown/Power Off your Gio.
2. Put your phone in recovery Mode(press: Home button + Power button toghether)
3. In recovery mode, select Update from SD-card(Use Volume keys to navigate and home button for enter).
4. Search for the root gb updated.zip file on your SD-card
5. Run the update
6. Reboot
Phone will be turned on , An App SuperUser will be added , its mean you successfully done rooting , now you must be thinking you have done rooting and nothing really changed, let me tell you my friends its the first step real thing begins after this , read the whole thread and you'll find much more things than you imagined.
----------------------------------------------------------------------------------------
Also there is this video that might help
http://www.youtube.com/watch?v=EvdNt6-JCQc
s!mon said:
dont unzip the file to root the phone...... just put it as it is on a sd card and follow the instructions you were given.
The First Step In Modification of you Gio is Rooting , everything starts from Rooting. Many Applications Require Root access for working.
------------------------------------------------------------------------------------
How to Root Samsung Galaxy gio
Download root gb updated.zip file. and copy to SD card (not in any folder)
1. Shutdown/Power Off your Gio.
2. Put your phone in recovery Mode(press: Home button + Power button toghether)
3. In recovery mode, select Update from SD-card(Use Volume keys to navigate and home button for enter).
4. Search for the root gb updated.zip file on your SD-card
5. Run the update
6. Reboot
Phone will be turned on , An App SuperUser will be added , its mean you successfully done rooting , now you must be thinking you have done rooting and nothing really changed, let me tell you my friends its the first step real thing begins after this , read the whole thread and you'll find much more things than you imagined.
----------------------------------------------------------------------------------------
Also there is this video that might help
http://www.youtube.com/watch?v=EvdNt6-JCQc
Click to expand...
Click to collapse
Yes, SuperUser app is present but for ex. ROM Manager tells the phone is not rooted, in terminal app I cannot su
Philadel isjsocop
fsosson said:
I have rebooted in recovery mode, launched CWM then applied the Update.zip you linked but the phone is not rooted
Click to expand...
Click to collapse
I have found what is going wrong, /system is full so binaries cannot be copied ...
If you see superuser then your phone is rooted. You can install this app as a rooted phone can only have it. It is Titanium backup. And uninstall Rom Manager, its useless for this phone and can cause you trouble.
I guess superuser is not totally installed, /system is full and su command is not present in xbin
fsosson said:
I guess superuser is not totally installed, /system is full and su command is not present in xbin
Click to expand...
Click to collapse
do you see superuser icon on your phone?
Yes I do, but there is no su command available and (just for ex.) ROM Manager says the phone is not rooted
How can I be sure the phone is rooted ?
fsosson said:
Yes I do, but there is no su command available and (just for ex.) ROM Manager says the phone is not rooted
How can I be sure the phone is rooted ?
Click to expand...
Click to collapse
There is an app called Root checker on the market, otherwise you can install apps like Titanium backup, coz if it is rooted then it will install this app.
I have installed Titanium backup and it says it cannot aquire root privileges ...
As I said /system is full so I guess there is not free space to copy binaries
Does anyone know how to clean up?

[Q] root priviliges, unstable and lots of fun.

hey, im new to Android, after moving on from my Iphone 4 to my the new M9, i start wondering.
i got my phone unlock booter threw the devHTC,
got it S-ff with the great app (that i forgot the name) which i payed for it.
installed SuperSu update to give roots privilages, and also BusyBox Free.
thoese are my problems:
1. installed SB game hacker, and its says after i gave it root privilages that i dont gave it, or i dont have root acces.
the thing is that with GameKiller i do get root access...
2. trying to apply patch with the Lucky Patcher sometimes i get root unstable window error that asked me to update my
SuperSu even thew its update to last vesrion.
3. again with Lucky patcher (which does get root privilages for sometimes) - i try to install threw the toolBox -> patch to android -> Signature Verificcation Status Always True , and after it reboot i go back to it and it says its not patched. like the patch failed.
i tryed to clear the core.jar and the service.jar but it doesn't help, it doesn't patch it.
4. i got the new System Update 1.36.709.3 and when i press Install now, it enter the teemmod (the developer mode which i can wipe, install and everything) and does nothing. after reboot to system it ask me again if i want to install, and again go to this dev mode (which is needed for installing supersu to the system).
5. same as befor, apps like clean master doesn't get superuser privilages and cannot disable auto start apps even thew superSu do allow it. also, CPU manager in Battery Life app always get off after a while, or after a reboot.
i hope i could get help cuz im really lost in finding a way to fix all of this.
Please help?
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
TwinAdk said:
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
Click to expand...
Click to collapse
OK, by flash u mean to go to recovery mode and install the su u told me right?
waltobc6 said:
OK, by flash u mean to go to recovery mode and install the su u told me right?
Click to expand...
Click to collapse
Basic terminology:
- Recovery / recovery mode: Instead of booting into the Android OS, you can boot into the "recovery OS" (located on a partition of the phone storage, just like the android OS is located on its own partition). The OS used for the recovery partition can be either stock or custom - popular custom choices are TWRP (TeamWin Recovery Project) or CWM (Clockwork Mod) - TWRP is the best choice for the M9 - http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
- To flash something: To install something (always a zip-file, never apk files) while the phone is in recovery mode
TL;DR: Yes. :good:
Kind Regards
TwinAdk
TwinAdk said:
Hello,
You need to fix your root situation.
- Open supersu, and do a complete uninstall.
- Download the latest super su flashable from chainfires website (Google it)
- flash it in recovery mode
- boot and install supersu free from play store
- report back here
Also, if you flashed a custom recovery you cannot OTA update the stock Android, that update requires stock recovery to install.
Click to expand...
Click to collapse
TwinAdk said:
Basic terminology:
- Recovery / recovery mode: Instead of booting into the Android OS, you can boot into the "recovery OS" (located on a partition of the phone storage, just like the android OS is located on its own partition). The OS used for the recovery partition can be either stock or custom - popular custom choices are TWRP (TeamWin Recovery Project) or CWM (Clockwork Mod) - TWRP is the best choice for the M9 - http://forum.xda-developers.com/one-m9/orig-development/recovery-twrp-touch-recovery-t3066720
- To flash something: To install something (always a zip-file, never apk files) while the phone is in recovery mode
TL;DR: Yes. :good:
Kind Regards
TwinAdk
Click to expand...
Click to collapse
Okay I got 3 options - reinstall which is not what I need
And 2 more which are cleanup for switching userroot app
And a full cleanup for preparing uproot.
Which one should I pick.
Also I used last time Supersu 2.49, and now from the site is gave me I downloaded 2.46
I understand 2.49 is beta - so which one to pick?
2.49. Place it on the SD card of the phone before unroot. Choose complete unroot in the su app.
TwinAdk said:
2.49. Place it on the SD card of the phone before unroot. Choose complete unroot in the su app.
Click to expand...
Click to collapse
Not having SD - and install it from the internal storage of the phone can **** it up?
I press. Uninstall and it get stuck on it. I let it run for more then 40 min
And it didn't finish
Complete unroot just got the phone stuck?? If so, please walk me through the life of your phone from unboxing, eg what have you done with the device in terms of unlocking it, flashing stuff etc. Also, what carrier and soff status...
TwinAdk said:
Complete unroot just got the phone stuck?? If so, please walk me through the life of your phone from unboxing, eg what have you done with the device in terms of unlocking it, flashing stuff etc. Also, what carrier and soff status...
Click to expand...
Click to collapse
I mean got stuck on the please wait- I was able to switch app.
Also after trying few time to uninstall it - it worked.
I flashed the super 2.49 opened google store and unlocked the app.
The CPU manager in doctor battery still turn off after a while.
Also auto start app disable in clean master still says it don't have room access even
I have it again.
And I tried to install in lucky patcher the signal true - and after long "please wait"
And a auto robot it says it not patched.
What to do ?
Do you see a prompt to allow root access to the apps asking for it?
Can you post a screenshot of the Super su app with allowed and disallowed applications listed?
Are you on stock ROM with custom recovery?
TwinAdk said:
Do you see a prompt to allow root access to the apps asking for it?
Can you post a screenshot of the Super su app with allowed and disallowed applications listed?
Are you on stock ROM with custom recovery?
Click to expand...
Click to collapse
I do get the approve window, also it shows the permission granted
In the super all allowed listed.
I didn't change any stock rom. I'm on the default of HTC m9 system.
And I'm still-off, and unlocked
That is really wired... Either we are missing something obvious, or your system is really messed up..
TwinAdk said:
That is really wired... Either we are missing something obvious, or your system is really messed up..
Click to expand...
Click to collapse
How can I do a full reset, cuz factor reset still leave the Supersu broke
Look in the forum for it
TwinAdk said:
Look in the forum for it
Click to expand...
Click to collapse
Please oh: I'm into it for like week without any good sucsses
Guide , help please?
Find your device/carrier RUU and start over, if you went through all the steps to get s off, you should have made a back up that you could start over with in recovery. If not search for for the RUU or original system file in the m9 forum For your SPECIFIC device.
---------- Post added at 07:52 AM ---------- Previous post was at 07:45 AM ----------
waltobc6 said:
How can I do a full reset, cuz factor reset still leave the Supersu broke
Click to expand...
Click to collapse
Try entering ##786# on your dialer key paid
I bought my phone in Bolivia, and at the box it had Chinese so I think it's a new movie9 from Asia. How can I check my SPECIFIC so I can download what's needed

Categories

Resources