Database Info

[Q] Gingerbreak, ROM Manager, Recovery, and Cyanogen 7

Nexus One 2.3.3 rooting:
I used the Gingerbreak App, which has the added benefit of leaving the bootloader alone and locked. The app Root Checker confirms root access and busy box (which I installed separately), and SuperUser is installed.
I've got 2 issues:
1. Titanium Backup claims I'm not rooted. I don't know if what it checks amounts to searching for an unlocked bootloader or not.
2. ROM Manager, while working fine mostly (I was able to make a nandroid backup i think), does not reboot into Clockworkmod Recovery, either by selecting the option, or choosing a .zip file with CyanogenMod 7 (stable). I just get the Android-with-exclamation-triangle screen, and either pull the battery or try to access standard recovery mode via Vol Up + Power (hit or miss). I've tried renaming a recovery flash file to "update.zip" and manually installing it, but the process always aborts (I've tried Recovery Zero and Clockworkmod).
CWM 3.0.0.5 is what ROMM shows, but I should note it did not work downloading the first time. (I got an error that I clicked out of by mistake, and when I tried again to see it, it said it was successful, and I've heard sometimes it takes a few tries).
I've also read something (link omitted since I'm a new user):
If after the "Reboot and Install" step, you immediately get a picture of Android with a big exclamation point, most likely it means the ROM image you downloaded was not cryptographically signed by the developer (which happens if they were in a hurry to release or simply don’t use encryption).
That’s OK – you can fix this by:
-clicking the exclamation point screen, which goes to the ClockworkMod recovery menu or simply rebooting into recovery manually (that’s one of the options in the ROM Manager). Alternatively, you can boot into recovery by holding Power and Home buttons together while powering up your phone
-selecting the option that says "install zip from sdcard"
-toggling the "toggle signature verification" option to turn the verification off (it should say "Signature Check: Disabled")
-giving flashing another try by selecting "choose zip from sdcard" and selecting the right ROM, just like before
However, I can't "click" anything, and I'm unsure of what the first bullet point means. I've tried reinstalling ROMM, but CWM doesn't uninstall (I don't know how to remove it since it arrived via ROMM).
I also tried the Amon RA route, but the bootloader method fails, the ROMM method is pay only (and no guarantee at that), and the terminal method needs a root password (su), which I've not activated and know nothing about, so it can't continue.
Anyone out there know what I can try? FWIW I'm on OS X 10.6.7.

[Q] OTA 2.3.7 update lost SU permissions

Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis

sobamaflyer said:
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
Click to expand...
Click to collapse
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?

krohnjw said:
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
Click to expand...
Click to collapse
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.

sobamaflyer said:
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
Click to expand...
Click to collapse
Yeah, you have the stock recovery. You can't apply a new recovery through rom manager because the su binary doesn't have the appropriate permissions since the update.
Boot into the boot loader (Vol up and pwr). Don't go into recovery. Use fastboot from the boot loader to load CWM. Boot into CWM after flashed and flash the SU binary (mount /system first). After this boot up and delete/rename /etc/install-recovery.sh so that it won't overwrite CWM on each reboot. Install CWM again from Rom Manager or via fastboot (as it was overwritten on boot). Done.

Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"

sobamaflyer said:
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
Click to expand...
Click to collapse
Fastboot is merely a command line tool used for various operations on the device. Mainly though you'll use it to flash an image to a specific partition.
You'll need to boot the device into the boot loader (hold Vol up and power on).
Plug the device in via USB.
Open a command windows in the tools or platform-tools folder of the SDK (depending on your version of the SDK, where the fastboot.exe can be found) and issue the fasboot devices commmand. This should display the serial of any connected devices. If this comes back blank there is an issue with the installed driver. Reinstall the USB driver for the device using the supplied driver from an updated SDK.
Assuming fastboot devices shows one device you now can flash a recovery to the device. Download the appropriate recovery for your device (i9020(a), i9203 or NS 4G) http://mirror.sea.tdrevolution.net/cm/recoveries/. Place this file in the same directory for simplicity.
At this point you can flash your recovery.
fastboot flash recovery file.name.you.downloaded.img
If it is not in the same directory you can alternatively pass the full path to the image.
You now have a custom recovery installed. Select Recovery from the bootloader menu to now boot into this recovery.
Assuming you've already downloaded the su binary and it is on your SD card, mount /system from within CWM and then chose to install zip and select this from the SD card. You now have root access.

Now that a panic attack is settling...
I think I'm getting somewhere but not yet where I want to be. I go to Bootloader, I connect my USB and don't get anything different than above from my sdk tools menu (unusable cmd screen, fail showing on my phone). What does [eventually] work is going back to my "nexus S one click root" folder and clicking run.bat (as fastboot.exe and adb.exe in that folder also do the nothing).
This run.bat reads some sort of fail and boots my phone telling me that debugging is not checked (which it is) and takes me directly to there, then the cmd screen tells me to press enter when I've turned on the [already checked] usb debugging toggle.....what the hell I press enter. Now it goes into the old beautiful CWMR (3.0.xxxx) screen where I'm able to apply .zips, backup etc.
(luckily I think ahead and do a backup right this min.)
Then I go from that screen and decide to apply my new CM7.zip that started all this, I apply that and get a bootloop on the CM7 boot screen.......crap......I go clear my davlik and cache and install CM7 again. Same thing.....crap......
I try restoring my original backup from 9/5/11 I made right after first unlocking my phone.......CM7 bootloop screen.....dammmmiiiiit
I try restoring backup from 9/12 I made after getting everything just like I wanted it.......CM7 bootloop screen.......uh oh, panic beginning.
I restore the backup from a few lines ago, my phone comes back (thank god)
So:
-I have to have the right USB driver in my laptop because something from sdk ultimately talked to my phone?!
-Clockworkmod recovery 5.xxxx has never worked quite right for me, apparently 3.xxxx is still my magic answer?!
-Now that I've gotten this far should I try the same process to get back to my CWMR 3.xxxx screen and put some different files in my root to use than what I've done to this point?
....again, I apologize if I'm being myopic or asking dumb questions. I often say I only know just enough to be dangerous.

[SOLVED] - maybe/sort of
Between reading (and re-reading) the help above and continued research on my own I [think] I solved my problem.
I found the following 2 links:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
And basically started over from scratch, I deleted what I'd put in my pc and re-loaded using those instructions (in the right place, the right way). Doing this I was able to pull up a cmd window and this time it properly accessed my phone. I got it to fastboot recovery - load CWM 5.0... and from there got into my recovery menus on my phone this time.
One curious thing....I tried the part VI in "how to root the samsung" ...""stop the phone uninstalling the custom recovery image"...... I've tried several things there but still get an error that it is read only.
....I went on to install CM7, and it consequently updated right after to the latest CM7, At this moment I have full permissions, superuser access, was able to make a backup of yesterday, the CM7 this morning and then CM7.1.0.1 that loaded.
Will I ultimately have the same issue as before? But be able to overcome it in the same manner when I want to?
Thanks for the help

This is why one click methods are bad. When a problem arises you have no clue what to do because a software did it for you the first time. Glad you got it figured out.
Sent from my Nexus S 4G using xda premium

[Q] Photon Q can't get root

hi guys, my photon q (unlocked bootloader) running on Jelly Bean can't root. I follow step by step from this . When I flash CWMrecovery I get "variable not supported" in the middle on my screen and then every into recovery there's triangle red (above android logo). I also can't find back-up and restore option in my recovery. And when I tried flash SuperSU via recovery I got this:
-- Install /sdcard/Root...
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I used another method, I used motofail2go to get root. but the problem goes to this: Always exploit failed, already factory reset (wipe data/cache) and push volume up + button power but nothing (exploid failed again)
Any ideas guys?

First, if your bootloader is unlocked you do NOT need to do motofail2go or any of that other nonsense.
Second, I recommend you try searching before posting.
If you search for "variable not supported" there is a treasure trove of information.
Take this thread for example. Seems stock recovery is playing tricks on you, unfortunately. It is curable tho.
Edit - this guy solved it by using TWRP...
I wonder if there's some file that just needs to be removed before flashing recovery? I'm not sure, but give TWRP a shot. It will root the device for you as well

Yeah I got rooted, I suggest to prefer TWRP than CWM. big thanks guys

How to install TWRP with JB OTA running
Here is a step-by-step for anyone who stumbles here looking for an answer. I had to remember how I forced it through the first time, so I could install TWRP on my second PQ. GOO manager doesn't install TWRP, despite offering to. I believe this is due to JB.
1. Download TWRP recovery file & save to "platform-tools" folder
2. Start command prompt in platform-tools folder
3. ~type "adb reboot-bootloader" (phone will boot into bootloader)
4. ~type "fastboot flash recovery openrecovery-twrp-2.5.0.0-asanti_c.img" (when that is the name of the TWRP recovery file in platform tools)
5. unplug USB, push power button - phone will turn off
6. Hold "vol-up" button in and press power button, release "vol-up" when screen turns on, phone will boot TWRP.
7. NAND backup, Flash rom or other.
Do it in this exact order & it will work. (should)
Enjoy *****es!

Help with rooting

Hello...I"m hoping I can get a little assistance with rooting...
I'm following the guide from http://forum.xda-developers.com/showthread.php?t=2737724
I've installed the drivers initially on a windows 8.1 x64 laptop (i've since installed on a win 7 32-bit machine). I kept getting:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I pulled the battery and when I try to start the phone up it goes straight to this screen again.
I pulled the battery again, went into download mode, and flashed philz_touch_6.57.8-klte.tar recovery img and it rebooted fine (unlike the cf-auto root.)
Everytime I try to do the first step of the guide (cf-root), I receive the same message. Can anyone help or at least point me in the right direction? Yes i'm new to samsung devices but have been flashing htc phones for years...clearly this is a different process. Thanks again for any assistance!
ALSO....even after pushing the recovery img through odin (at least it seems to reboot my phone).....turning the phone off...and then holding vol up+home button+power DOES NOT take me into recovery...it just takes me back to the screen with
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery

Is there anyone who can assist me?
EDIT
I went ahead and installed a the stock 4.4.4 from this thread:
http://forum.xda-developers.com/sprint-galaxy-s5/development/stock-rom-ni3-kitkat-rom-t2886171
This apparently restored my recovery img and I was able to boot into the stock recovery. I attempted the process of cf auto root again using this file: CF-Auto-Root-kltespr-kltespr-smg900p.tar.md5 and the result was the same. Immediately after it tries to restart I get:
RECOVERY BOOTING
Recovery is NOT SEANDROID ENFORCING
Set Warrenty Bit : recovery
I again pulled the battery and powered into download mode to flash a recovery. The file I used was: philz_touch_6.57.8-klte.tar.md5
This booted my phone back into the normal rom. I tried to use SuperSu but it says that I don't have root. I went ahead and reflashed the stock rom and once again I have stock recovery. Not sure why this is happening, but it appears that cf auto root is removing my recovery. I'm probably wrong, but I'm looking for input from anybody in this community.
Any help?

Solved the issue following suggestions from this thread:
http://forum.xda-developers.com/showpost.php?p=57022287&postcount=24
Instead of flashing cf-auto root first, flash the custom recovery first. Then let your phone boot up and then power it down. Hold up + home button + power and get into recovery...wait for few seconds as it will show the same message as before and then it'll let you into recovery. I selected reboot now and it prompted me for root...select yes. Done.

:good:

Still not getting root
I went through all the steps on CF's Auto Root listing and ended up with the same issue. I followed the above instructions to reset and was able to get the phone to reload fully. I have since been able to install TWRP, however I still can't get root access on my phone.
I can reboot to Recovery and get the same announcements. However, if I wait a sec or two it does proceed to TWRP, but upon reboot I get no root access. SuperSU won't proceed and root checker verifies that I have no root access.
Any suggestions?

Ademelo1 said:
I went through all the steps on CF's Auto Root listing and ended up with the same issue. I followed the above instructions to reset and was able to get the phone to reload fully. I have since been able to install TWRP, however I still can't get root access on my phone.
I can reboot to Recovery and get the same announcements. However, if I wait a sec or two it does proceed to TWRP, but upon reboot I get no root access. SuperSU won't proceed and root checker verifies that I have no root access.
Any suggestions?
Click to expand...
Click to collapse
Hmmm...so all I can suggest is the little steps I took. Flash the full rom again...ODIN the recovery (philz)...let boot up....shut down...and vol down +home button+power to get into recovery...select reboot...should be prompted to install root.

Worked
Got it rooted, thanks. Now to find a good ROM.

ademelo1 said:
:d got it rooted, thanks. Now to find a good rom.
Click to expand...
Click to collapse
moar rom ?

[Q] Help with bootloop? when installing CWM with flashtool

Not sure where to post this, as I'm quite new here, but here it goes.
Every time I try to flash the CWM in my M2 d2306 I get a screen black with blinking background led at reboot.
Then, I re-flash the kernel and bootbundle, and everything works okay. But then, no CWM.
What must I do in flashtool? I connect via fastboot, then click in Flash kernel with the .img provided in one of the topics here.
Also, I'm sorry for my newbieness... I used to own a WP 7.8 ....

Power + volume up button press(10 seconds) and off the phone
Open flashtool select firmware wait the connect phone message press volume down button connect pc and wait ending firmware flashing

ishakcez said:
Power + volume up button press(10 seconds) and off the phone
Open flashtool select firmware wait the connect phone message press volume down button connect pc and wait ending firmware flashing
Click to expand...
Click to collapse
I'm really sorry if I'm mistaken:
Well, maybe I'm just too dumb, but... ain't this just the same as I said...? Let me try this again:
1. I install CMW. Then, when I reboot, it gets the bootloop.
2. I, then, install the custom VIVO firmware for my Xperia M2 d2306 (realized that I just need to flash the kernel again). The phone DOES boot.
3. I can't enter recovery mode anymore
Context:
The real problem, actually, is that after all this work, ignoring that the recovery mode got broken, I try to uninstall some system apps, like the VIVO BS, Google Magazine, Xperia Lounge, etc... But after I close the Titanium (or NoBloat Free) the shortcut of the app is still there. It does not launch, giving an stop error or something, but if I reboot, it gets fully restored.
I thought it had something to do with the superSu not being installe properly, so I tried to boot into CMW to reinstall SuperSU., thus beggined my loop with the flash->bootloop->flash-bootloop... :crying:

You have system as writable? When i update from 4.3 to 4.4 i had root but not system as writable so i can't to uninstal apps. TB was showing to me that is uninstaling apps but after reboot they were still instaled. So if you don't have system as writable you can't install CWM and have bootloop.
Sent from my D2303

Dzepar said:
. So if you don't have system as writable you can't install CWM and have bootloop.
Click to expand...
Click to collapse
That seems to be the case, thanks! I'll try to figure out how to make /system writable.
Thank you again

I'm on phone but there was tread for that. Search it ?
Good luck.
Sent from my D2303

Root acces possibly lost.
I guess I let something very important slip...
I was trying to fix system, but couldn't write to sony_ric/enabled, so I've redone the rooting, and just after installing SuperSU, via CWM, I got the following error when I tried to power off:
Code:
Root access possibly l
THIS CAN NOT BE UNDO
- No
- Yes - Fix boot (/syst
As you see, it's missing some characters, so I had no idea of what it said. I've googled it a little and soon found that there may be some workaround,
like using TWRP.
Question time:
1) But can we, users of M2, have a stable access to TWRP (didn't found anything saying no, but neither saying yes)?
2) Does it have something to do with my su binaries been messed up?
3) Does it have something to do with the bootloop?
4) Everytime I install the kernel of my custom firmware, I can't access CWM anymore. Can I fix this or is this the default behavior (or both:fingers-crossed?
PS: I followed this topic: [TUT] Fix Mount System in Kitkat After Root

Two questions answered
tkgcmt said:
Question time:
1) But can we, users of M2, have a stable access to TWRP (didn't found anything saying no, but neither saying yes)?
2) Does it have something to do with my su binaries been messed up?
3) Does it have something to do with the bootloop?
4) Everytime I install the kernel of my custom firmware, I can't access CWM anymore. Can I fix this or is this the default behavior (or both:fingers-crossed?
PS: I followed this topic: [TUT] Fix Mount System in Kitkat After Root
Click to expand...
Click to collapse
Well, I guess I found the answer for two of my questions.
A2) Aparently I was using the Google Play Store version, that is known for not being able to update de binaries, and such...
A4) Using the flashtool removes the root somehow. I don't know how I got it working the first time, though, but now none of my apps given root access works. I'll try this: http://forum.xda-developers.com/xperia-m2/general/root-d2303-kitkat-18-3-c-0-40-locked-t2929893

update
Just an update.
The method of Engineer91 didn't worked out for me, as OTA fails to update me to 4.4.2
I've tried to flash the kk with flashtool, ticking (removing from the flash) only the kernel (as seen in androidclub, but then I got a bootloop again.
I'm running out of ideas... does anyone knows what can I do to fix the system not being able to be mounted as writable in the KK (Android 4.4.2)?