Database Develop

Why can´t I get root access?

Okey, before FRG83D I rooted my phone with SuperOneClick. Then I decided to go back to the original ROM, and update to FRG83D. As you know, this revoked my root access. So now I unlocked the bootloader and ran Superboot. However I don`t get rooted. My suspicions are that because my old Superuser apk is left, something goes wrong. Plz help me figure this out!

Well all need a root for 2.2.1
Sent from my Nexus One using XDA App

Shivammcool said:
Well all need a root for 2.2.1
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Are you telling me there is NO way to root 2.2.1 ? :O

No, I think the other guy is just thinking of a root-without-unlock method.
You are already unlocked. So it's just a matter of changing the system correctly to root it. Easiest way is to probably flash an already rooted stock build over it. (I assume you want to remain stock)
Or at least you need to find the correct way to root 2.2.1, which is hard because there are probably a lot of people out there looking for a root without unlocking, so that will pollute your search results.
Edit: Of course, I could be way off base and not know what I'm talking about.

Yup, flash a rooted stock rom, like Geo's.

I still don't know why people love to make things harder on themselves than it needs to be lol.

Okey, this is kinda crazy, because Adblock is working and has all permission, but nothing else!
Sent from my Nexus One using XDA App

MrSvedberg said:
Okey, this is kinda crazy, because Adblock is working and has all permission, but nothing else!
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Not familiar with Adblock, but if it is similar to AdFree it just works by replacing your /system/etc/hosts file with one that directs every advertising address to the loopback address, thus preventing the apps from loading. If that file was in place before you lost root, it will continue to block ads for you.

Okey, but if I just want to flash CM, what do I do? Can't get to recovery :/
Sent from my Nexus One using XDA App

You're unlocked, right? Super easy :-D
Download a recovery *.img (or extract it from a recovery .zip).
Reboot your N1 to fastboot mode (press and hold VOL-DOWN while powering on - press Power to select Fastboot USB when the option is presented).
Connect your USB cable.
Run fastboot flash recovery recovery.img (replacing "recovery.img" with the appropriate file name). When complete, you have an aftermarket recovery again.
Boot to recovery and install whatever ROM you want

codesplice said:
You're unlocked, right? Super easy :-D
Download a recovery *.img (or extract it from a recovery .zip).
Reboot your N1 to fastboot mode (press and hold VOL-DOWN while powering on - press Power to select Fastboot USB when the option is presented).
Connect your USB cable.
Run fastboot flash recovery recovery.img (replacing "recovery.img" with the appropriate file name). When complete, you have an aftermarket recovery again.
Boot to recovery and install whatever ROM you want
Click to expand...
Click to collapse
Thx a lot m8, but could you dumb that down just a little bit? Still a bit n00b in the area x)
Sent from my Nexus One using XDA App

Those steps are broken down a bit more specifically (including prerequisites) in this thread, which I found from the NexusOne Wiki, which is a great place to look for such common information.

Done it, and I'm 110 % sure I did it right! Still does not work!
Sent from my Nexus One using XDA App

What part are you having trouble with?

Can't boot into recovery...
Sent from my Nexus One using XDA App

MrSvedberg said:
Can't boot into recovery...
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I'm afraid you'll have to be more descriptive than that.
HOW are you trying to boot to recovery? There are several methods:
1) Issue the adb reboot recovery command
2) Boot to the bootloader (press and hold Volume-Down while powering on), use the volume keys to scroll down to Recovery, and the power button to launch it.
3) Use an application like Quick Boot to reboot directly to recovery from the OS, though that may require a working root.
Have you tried these methods? If so, what happened? What did you see on the screen?

Number 2. Just seeing an Android and a triangle.
Sent from my Nexus One using XDA App

MrSvedberg said:
Number 2. Just seeing an Android and a triangle.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Then that is the stock recovery. Flashing a third-party recovery was not successful. Did you receive any error messages from the fastboot flash recovery recovery.img command?
Your bootloader IS unlocked, right? You have a padlock icon on the bottom of the screen immediately after poweron?

The flash was successful, no error messages. And yes, the padlock is there.
Sent from my Nexus One using XDA App

MrSvedberg said:
The flash was successful, no error messages. And yes, the padlock is there.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
What recovery image are you trying to use?

Navigate recovery with dead power button?

I'm helping a friend flash cyanogen on his nexus (its already rooted) with the famous power button issue. Can the trackball click instead of power?
And the bigger question, I know I can use rom manager to reboot into recovery, but how can I get into recovery from bootup? I read a trick about using the usb to jumpstart it, can that help get it into recovery?
I'm amazed that I can't find any info about this searching. Maybe bad wording?
Sent from my HTC Vision using XDA App

try here
http://forum.xda-developers.com/showthread.php?t=864321

Geeze, tried to reply a while ago and the page had no post reply buttons...
Anyways, what I am scared of *unlikely* is a bootloop. I know you can use ADB i just don't know how to access in a way I can flash if it's bootlooping and I can't just open the recovery easily.

Yes, you can navigate recovery with the trackball. Like you say, the biggest problem is getting into recovery if you can't boot...
If the "fit hits the shan", you can always unlock the bootloader, and flash images with fastboot...
Sent from my Nexus One using XDA App

hrm, I've done some fast boot on my G2 but I just did a reboot fastboot so I'm not sure how that works haha. I'll look into that if it ever arises but I doubt I'll encounter a boot loop. He was saying he doesn't think the Recovery will trackball navigate, but he has a Vibrant with no trackball so he's not used to it lol

Trackball navigation is in both Amon_Ra and Clockwork, so it's not a problem.
Getting into recovery w/o power button and w/o fastboot is tricky, if your ROM bootloops - if you don't have USB debugging enabled, you might be out of options.

Jack_R1 said:
if you don't have USB debugging enabled, you might be out of options.
Click to expand...
Click to collapse
Always on by Default for me lol

I had this exact problem on my old N1, here's how I was always prepared for bootloops should they happen: Link. An alternative way is to use PASSIMG method as this will wipe and flash a stock ROM which you can then adb reboot recovery to restore your nand backup. Either of these ways, although not the quickest, will guarantee that you can get back to recovery.

Oo awesome Exactly the kind of info I couldn't find in a search lol. *Bookmark*

[Q] HELP. Rooted Sprint Hero, recovery not working, S-ON?! RUU ERROR 170&140?!

I'm stressin now. Please help me guys. My phone won't RUU and I need to get S-OFF but I can't figure out how to do so for the life of me. I've been sitting here trying for hours and now I'm getting discouraged.
HTC Hero200 (CDMA) for Sprint
this is what the hboot keeps saying;
"HERC XC SHIP S-ON
HBOOT-1.47.0000 (HERO20000)
MI CROP-0110
TOUCH PANEL-SYN0104
RADIO-2.42.01.04.27
Mar 1 2010, 16:02:39
HBOOT
<VOL UP> Fastboot Mode
<Back> Simlock
<Home> Recovery
(after hitting volume up to fastboot)
FASTBOOT
<VOL DOWN> HBoot Mode
<MENU> Reset Device
<ACTION> Restart To HBoot
I've tried everything...well at least it feels that way. I've attempted flashing new recoveries, I've attempted RUU'ing, I've tried rerooting with desktop rooters and 1-click apk's and I'm stumped. I beg of you, Good folks here at XDA, Help me. Please.

Lets start with the simple questions:
1)why do you want to RUU/unroot?
2)what ROM and recovery and mods do you have?
3)have you tried RUU.exe or RUU.zip?
4)do you have the HTC drivers and SDK on your computer?
error 170 is USB failure, and you need the most recent drivers to fix (usually) and sprint hero is Sync 2.0.40 link here: http://www.htc.com/us/support/hero-sprint/downloads/
error 140 is phone image version failure, here's a link to fix it: http://forum.xda-developers.com/showthread.php?t=843544

I recently had trouble RUUing, see this my post here
http://forum.xda-developers.com/showpost.php?p=13290368&postcount=23

Well I just rooted and I want to put a recovery image on and install a custom Rom, but its says 's-on' on my phone and somebody.said to install a custom Rom or even just a recovery image, you hafta have s-off. I cant even access the stock recovery. I'm assuming during the rooting process, I corrupted the recovery somehow..
Sent from my HERO200 using XDA App

alexdemo said:
Well I just rooted and I want to put a recovery image on and install a custom Rom, but its says 's-on' on my phone and somebody.said to install a custom Rom or even just a recovery image, you hafta have s-off. I cant even access the stock recovery. I'm assuming during the rooting process, I corrupted the recovery somehow..
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
Wait, so you're rooted an want a custom ROM? (fyi you didn't really answer my Q's) Just so you know RUU and s-off is NOT needed to gain root and flash things. Does your phone boot? If so just grab the rom mangager app from the market and install clockworkmod recovery. Then go to the thread for whatever ROM you want, and follow the instructions to install it.

That's the thing though, I tried installing the clockworkmod recovery through Rom manager and through terminal and when I do it with terminal, it tells me the recovery.ing doesn't exist. I can't boot into recovery
Sent from my HERO200 using XDA App

alexdemo said:
That's the thing though, I tried installing the clockworkmod recovery through Rom manager and through terminal and when I do it with terminal, it tells me the recovery.ing doesn't exist. I can't boot into recovery
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
When I installed cwm recover via rom manager, I couldn't boot into recovery manually I had to use the button in rom manager that says 'reboot recovery' to get there. Have you tried that?

I just tried booting into recovery through ron manager, no go
Sent from my HERO200 using XDA App

Are you rooted?

Yessirrr, and I'm sure all this could be solved with a simple RUU to wipe it clean and start brand new but I can't manage to make the RUU even work
Sent from my HERO200 using XDA App

Flash a different recovery through terminal emulator, power off, hold home press power.
sent from a series of tubes.

If you can boot into the bootloader you can try the hercimg in my post above.

Is bootloader the screen that has the option to boot into recovery and hboot? Cause I tried the Herc.ing and I could figure it out. Where do I place the Herc.ing file?
Sent from my HERO200 using XDA App

alexdemo said:
Is bootloader the screen that has the option to boot into recovery and hboot? Cause I tried the Herc.ing and I could figure it out. Where do I place the Herc.ing file?
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
It's the white screen with plain text and a skateboarding android. You get there by holding volume down while you power up.
Follow these instructions.
moxlon69 said:
As far as not being able to RUU, some people have an issue running the RUU if they haven't ran HTC Sync. Try that and see if it works, and if not, follow this method.
HERCIMG-2.31.651.7.ZIP download it. it's the Sprint 2.31.651.7 executable but in signed zip format, for people who aren't running windows. Not sure who actually converted the executable to a signed zip, but props to you for helping those that can't run the regular RUU.
Rename the file to HERCIMG.zip and place it on the root of your SD card.
Power the phone off.
Press and hold your Volume Down button, and while still holding it press the power button to power your phone back up into HBoot mode.
HBoot should then automatically verify the zip file, and ask you if you would like
to flash it. Press your trackball (action button) to confirm the update (downgrade in this case),
or press your send button (green call button) to cancel.
Once on 651.7 you would root as normal, but you should not have to RUU back to 651.7 just to root.
Click to expand...
Click to collapse

aiwetir said:
It's the white screen with plain text and a skateboarding android. You get there by holding volume down while you power up.
Follow these instructions.
Click to expand...
Click to collapse
I tried that several times. It hasn't given me an option once to flash anything from hboot mode. I'm so stumped

alexdemo said:
I tried that several times. It hasn't given me an option once to flash anything from hboot mode. I'm so stumped
Click to expand...
Click to collapse
So you boot into hboot directly or fastboot? It says there (maybe) press volume down to get to hboot. After you press volume down, it should automagically find the HERCIMG.zip on your sdcard and offer you to update.

I'm going out for a couple of hours so good luck.
I just had a dumb thing happen, I kept using adb to push a HERCIMG to my phone and it wasn't overwriting the old one, make sure you delete any old hercimgs on the sdcard and try adding the one linked above again.

aiwetir said:
I'm going out for a couple of hours so good luck.
I just had a dumb thing happen, I kept using adb to push a HERCIMG to my phone and it wasn't overwriting the old one, make sure you delete any old hercimgs on the sdcard and try adding the one linked above again.
Click to expand...
Click to collapse
So I used regawmod's 1-click rooter and got clockworkmod's recovery image (3.0.0.5). So do I really need s-off or should I just live and let gingerbread?

Irrelevant sort of, but the "you have to be s-off" statement is actually true for many phones. Many phones you will end up s-off going through their rooting process. It just so happens to not be the case with the sprint hero and probably a lot of other android phones.
~maybe I set it too high...

alexdemo said:
So I used regawmod's 1-click rooter and got clockworkmod's recovery image (3.0.0.5). So do I really need s-off or should I just live and let gingerbread?
Click to expand...
Click to collapse
Sounds like you've had enough troubles. Just ignore s off for a bit, get used to flashing roms and such.
sent from a series of tubes.

E file signature verification failed?

I am a noob an I am alittle confused with installing roms. I tried to install one and it went through everything and then it stopped and it said in yellow that the E file signature verification has failed now what does this mean. Please help.
Sent from my DROID3 using XDA App

What was the exact name of the rom (or filename)... was it a stock rom (SBF/XML) or was it one of the custom roms?
Also was your phone rooted?

I was trying to install a couple but the one I really have been trying in the liberty 3 2.0.
Sent from my DROID3 using XDA App

Are you using safestrap for your clockworkmodrecovery or are you using regular bootstrap?
And when you're in clockworkmod recovery what exact steps did you do to flash? You should wipe data & cache, then choose install zip from sdcard.
Sent from my XT860

I don't know how to use or get bootstrap and I don't know alot about safe strap yet. I tried different ways I tried using rom manager an downloading the rom from there then it will ask if I want to boot into recover I push ok and the phone just reboots. Nothing happens so I tried rom toolbox an did the same thing. So I tried to boot myself by pushing the power and x an I did as you said I wiped data a cache then I reset and restored my phone went back an installed zip from sd card then it starts to install then it says E file signature verification has failed.
Sent from my DROID3 using XDA App

Ahhhh ok.
It sounds like you are trying to install zips via the stock recovery. That recovery will only install signed/official ones, not custom rom zips.
If you want to install custom roms, try this method (but I recommend browsing through the other threads. There is a lot of useful info out there). This is the safestrap method. Safestrap allows you to have your stock rom (that you are on now) in the "non-safe zone" and with safestrap you can enable the "safe zone" for installing your custom rom.
1) make sure your phone is rooted if it isn't already. There are threads about this... I used DoomLord's root (version 4) for my phone but read up.
2) install safestrap 1.08 (u can find it in the droid 3 development forum). It is an apk file.
3) when you run safestrap 1.08 from your app drawer, superuser will probably ask you if you want to allow it root access, say yes.
4) in the app, hit the first button. It will install safestrap so you can boot into safestrap recovery. When it says its done, restart phone.
5) upon restart, you will be greeted by the safestrap splashscreen. It gives u 10 seconds to hit Menu to take you into safestrap recovery. Otherwise it will just continue with booting.
6) so hit menu. Safestrap ecovery appears. It will indicate that safe mode is not enabled yet. You are in non-safe right now (your stock rom)
7) this step is optional but I'm sure everyone will recommend it (I do also). Navigate your selection with the down/up volume buttons and hit power when you get to "backup". This will back up your non-safe zone and dump it onto your sdcard (internal or external). You can restore it to your non-safe zone (only) if you happen to mess up your non-safe system. The backup will be stored in /safestrap/backup. of whatever card you select.
8) now that that's done, it will take you back to the main menu of safestrap recovery
9) Go to "safe boot menu" and hit Toggle safe zone. Don't do the quick toggle, just do the normal one (the first one)
10) when that is done, you will notice the colour of the text has changed. And at the top it will say safe zone enabled. You can now install your custom rom by going to "install zip from sdcard" from the main menu of safestrap*
*Note that when installing roms, make sure to choose Wipe Data first. It will wipe your data and cache. Then go into mounts and storage and choose "format /system" (thanks Endo). Some people also like to go into the advanced menu and wipe the dalvik cache as well (is this necessary? I do it every time because I had to back on my old htc... maybe someone can comment on this?) It doesn't seem to hurt anything when I do it, so...
So after your wipes, you can go to "install rom from sdcard" . Choose the .zip of the rom (of course) to begin install. When the rom has finished installing, you can go back to the main menu and choose reboot phone. You will be greeted by the safestrap splashscreen again. It will tell you that safe zone is enabled. Wait the 10 seconds to boot normally or you can hit the search button to go immediately.
On first boot of many roms, it may take a little longer than normal to start up. Be patient. If it never boots (and you are looking at the boot animation forever... say more than 5-10 minutes?) Then... somethings wrong, or you may have forgotten to do your wipe procedure, but go to that rom's thread and read all the posts to see if others experienced the same thing... someone could have posted a good suggestion or solution
Oh, if you want to switch back to non-safe mode, restart phone, get into safestrap recovery, go into safe boot menu, and hit toggle. Then restart phone.
If something disastrous occurs, there are Unbrick and Fastboot threads in this forum where you can download a stock rom for your phone and flash to your phone via RSD Lite, which will pretty much restore your phone to stock. (No more safestrap, no more root). Read through those to get more info.
Hope this is helpful. Good luck!
Sent from my XT860

ryanw5489 said:
I don't know how to use or get bootstrap and I don't know alot about safe strap yet. I tried different ways I tried using rom manager an downloading the rom from there then it will ask if I want to boot into recover I push ok and the phone just reboots. Nothing happens so I tried rom toolbox an did the same thing. So I tried to boot myself by pushing the power and x an I did as you said I wiped data a cache then I reset and restored my phone went back an installed zip from sd card then it starts to install then it says E file signature verification has failed.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
I'm not really sure what you are doing but uninstall any recovery you may have installed and ditch rom manage(you can keep the toolbox) go to www.hash-of-codes.blogspot.com go to downloads and get safestrap. Install it, open it and click install recovery. Reboot your phone, you'll get a screen saying pish menu to enter recovery then once it enters go to safe mode menu(or whatever it exactly says) and enter safe mode. Once safemode is active(it says at the top of the screen)go to mounts and storage and format system then do a data/cache wipe, the install zip from sd
If you're doing what I think you're doing you are new to this and I would suggest reading as much as you can in this forum and by googling the various terms you find so you don't brick your phone
Sent from my DROID3 using xda premium

So do you want me to uninstall clockwork recovery?
Sent from my DROID3 using XDA App

ryanw5489 said:
So do you want me to uninstall clockwork recovery?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Yes. Safestrap will install its own CWR
Sent from my DROID3 using xda premium

So how do I go about uninstalling cmw.
Sent from my DROID3 using XDA App

ryanw5489 said:
So how do I go about uninstalling cmw.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Safestrap will clean that up. Just get rid of any bootstraps and rom manager
Sent from my DROID3 using xda premium

So I have to get rid of rom manager because I paid for it an really don't feel like losing money on it. I don't think I have any bootstrap so I should be good there. I'm sorry that I don't know alot I'm really new an I don't have the most time to even do alot of research so thanks for helping me out greatly appreciated.
Sent from my DROID3 using XDA App

ryanw5489 said:
So I have to get rid of rom manager because I paid for it an really don't feel like losing money on it. I don't think I have any bootstrap so I should be good there. I'm sorry that I don't know alot I'm really new an I don't have the most time to even do alot of research so thanks for helping me out greatly appreciated.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
If you have your heart set on rom manager, I believe it will work, but I've never used it so I can't help you there. I recommend safestrap because once you're in safemode its pretty hard to screw up your phone in any serious manner. In safemode you'll always be able to access recovery.
In a google search of your issue I found a recommendation of turning off signature verification. I know I've seen an option for this or something really damn similar in clockwork recovery. You can try that if you like but I don't know the effects of it. As always, I'm not responsible if you brick your device
That said, I would also suggest that you look into obtaining rsdlite and the appropriate fastboot package(you may know this as an sbf, although that term isn't totally correct)so if you do brick your device you know how to recover it. There's a sticky in the dev forum about it
Sent from my DROID3 using xda premium

Thank you I understand I wouldn't ever blame anyone for my mistakes so your good. I was thinking about using safestrap anyways just haven't had time to research it much yet. Probably would be best since I don't know much about roms anyways. Now it's not that I have it set with rom manager just seemed easy to use and I like rom toolbox alittle more anyways. I also know that not all roms are comparable with the safestrap so that's another reason why I haven't used it yet.
Now on another topic. I have downloaded safestrap on my computer all I have to do is plug my phone to the computer an put it on mass storage and place it in the sd card or internal memory and unplug it an click on it on my phone.
I really need to start some research cause this stuff is pretty hard.
But thanks for your help again
Sent from my DROID3 using XDA App

I have installed safestrap. Is there anywhere that's best to look up how to use it.
Sent from my DROID3 using XDA App

i have installed safe strap i rebooted my phone and now it is stuck on boot screen now what did i do to my phone and what happen can it be fixed?

Which boot screen? What does it look like? Is it the safestrap boot screen (that says you can hit Menu to get into recovery?)
I replied to this thread with instructions on how to use it. Were they not useful? Did you get stuck somewhere?

LaZiODROID said:
Which boot screen? What does it look like? Is it the safestrap boot screen (that says you can hit Menu to get into recovery?)
I replied to this thread with instructions on how to use it. Were they not useful? Did you get stuck somewhere?
Click to expand...
Click to collapse
I don't know how I missed your huge write up. More detailed than mine.
I figured the same, stock recovery. I'm not sure what steps he's taken before he wrote this thread.
OP if its the boot animation, on first boot it takes a long time. 5 minutes normally but give it 10 to be sure. If its the splash screen you may have issues. Is the safestrap splash coming up, where it says press menu
You may have to use rsdlite or the fast unbrick to restore your phone to stock. If you can write us EVERYTHING you've done in as much detail as possible, and exactly what is happenig now we can come up with a solution.
I think often all the various terms can be confusing to newcomers. I have a feeling perhaps that you still have a bootstrap installed and safestrap.
Sent from my DROID3 using xda premium

ok well first i went to hash of codes and downloaded the safestrap. Then i put the download on my sd card and i went into my files and pushed sd memory. then i went and found the apk and downloaded the safestrap. it installed fine then i pushed install recovery.then after all that i rebooted my phone and now it is stuck on the BIG RED Motorola symbol that says DUAL CORE TECHNOLGY. I even took out battery and tried that did not work. i also tried pushing power and x and restoring phone. still nothing. i must of missed something i just cant figure what that would be! Please help!

ryanw5489 said:
ok well first i went to hash of codes and downloaded the safestrap. Then i put the download on my sd card and i went into my files and pushed sd memory. then i went and found the apk and downloaded the safestrap. it installed fine then i pushed install recovery.then after all that i rebooted my phone and now it is stuck on the BIG RED Motorola symbol that says DUAL CORE TECHNOLGY. I even took out battery and tried that did not work. i also tried pushing power and x and restoring phone. still nothing. i must of missed something i just cant figure what that would be! Please help!
Click to expand...
Click to collapse
No I meant with rom manager and rfom toolox. All the steps you took prior to posting on this thnread
Sent from my DROID3 using xda premium

3.41 bootloader info from google support

Well I decided to call Google about the boot loader recovery not working as it should. I was hoping this call would help them to work on another update but they say that's the way its supposed to work. Here's the email Instructions:
1. Power down your device
2. Press and hold both volume keys and the power button to enter
Bootloader mode
3. Press the volume keys to cycle to the Recovery mode option
4. Press the power button to select Recovery mode
5. From the Recovery mode screen, press and hold the Power button then
press the Volume up button.
6. Use the volume buttons to select wipe data/factory reset.
7. Select Yes -- delete all user data.
8. The factory data reset process will now start. Once its finished,
select 'Reboot system now.'
The only option we have in the new recovery is to wipe data. Maybe for those having problems accessing twrp or cwm will be able to a access it with step 5. I don't know haven't rooted yet. So I decided to ask about nvflash and they said they're not going to release any nvflash tools or files.

um, yup. thats how stock bootloader and stock recovery work. lol
whats the issue? if your not even rooted, you wouldn't even know if you have an issue or not with the new bootloader.

Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.

xjman said:
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
Click to expand...
Click to collapse
No. I saw people posting they couldn't get go cwm and could only see the red exclamation point. And I was just saying maybe after choosing recovery then holding volume up and power it would then go to cWm or twrp. I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was

kieso said:
I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
Click to expand...
Click to collapse
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app

smirkis said:
didn't know being informed makes me an asshole. stupid me, reading and understanding.
for what its worth, im on the newest bootloader, and selecting recovery goes straight to twrp. which is the recovery i installed.
Click to expand...
Click to collapse
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?

mr_tris said:
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info. I'm going to try unlocking and rooting when I get home. I really want to use the OTG cable and the 720p mod.

kieso said:
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
Click to expand...
Click to collapse
When I first flashed TWRP onto my Nexus 7 after that official 4.1.2 OTA update, I wasn't able to boot into it. I then flashed it again via fastboot, and then booted the TWRP image that was on my computer, and then TWRP loaded.
I believe TWRP does work normally now as well (I can boot into it and reboot into it).

kieso said:
I'm going to try unlocking and rooting when I get home.
Click to expand...
Click to collapse
Well if I was you I'd just use mskips toolkit, its absolutely epic it'll save you a lot of farting around. I take it that your fully updated? ( Not that it matters) You seem to know and understand your way around adb so just go for it and enjoy.
Its works smooth as silk and save you a lot off time. The options available to you are just staggering!
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my Nexus 7 using xda app-developers app

Thread Cleaned​
No need for personal insults, lets just try to help each other out and show each other some respect.​

going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.

There are plenty of people that are having issues with recovery on 3.41 bootloader.... Its confirmed some have it some don't.
The issue is that with 3.41 bootloader on some Nexus 7 Devices a custom recovery is unbootable no matter how you try, every time it will try to load recovery and fail at a black screen then reboot into the OS. It does not matter how you try from ADB reboot to recovery or from bootloader with USB attached or not.

psycho2097 said:
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
Click to expand...
Click to collapse
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.

kieso said:
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
Click to expand...
Click to collapse
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers

mr_tris said:
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
Click to expand...
Click to collapse
Thank you for all the help! I appreciate it.

kieso said:
Thank you for all the help! I appreciate it.
Click to expand...
Click to collapse
No problem, a click on the 'Thanks' button for me and my colleagues on this thread would really make our day. :thumbup:
I hope you get sorted mate, I wouldn't be able to sleep at night until I got custom recovery working properly on any of my devices!
Sent from my Nexus 7 using xda app-developers app

i tried changing the name of the file, but.. after reboot, the tablet gets stuck on google screen, recovery never loads... any suggestion? Thanks =)