Problems with TWRP and GNex Toolkit 7.8 - Samsung Galaxy Nexus

Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:

19blacktiger77 said:
Hi, i have this problem:
Two Galaxy Nexus, one is mine one of my friend 4.1.1 Yakju Maguro both.
I make the procedure with GNex TOOLKIT 7.8.
Install Drivers
Unlock Bootloader
Root
Flash CWM Touch
Click to expand...
Click to collapse
...
19blacktiger77 said:
Download TWRP 2.2.2.0 through site and flash with adb in bootloader.
Click to expand...
Click to collapse
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
19blacktiger77 said:
All works fine! ( mine)
For my friend same procedure, but flashed TWRP Recovery instead CWM
Install BusyBox. ( both with GNex TOOLKIT 7.8)
Recovery start only first time, then i get the Android with triangle and exclamation mark.
Click to expand...
Click to collapse
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
19blacktiger77 said:
Made unroot, unloock and flashed stock Google rom.
Made same procedure as mine, and worked... Since i installed GooManager, and flashed TWRP.
Phone get super slow, Cpu at 90-100%!!!
Android System App doesn't show any threads that makes the cpu goes crazy.
Now i don't know what maybe the problems!!!
Partitioning problems with GNex TOOLKIT 7.8???
TWRP bugs?
My phone works fine, my friends install stock JB another time, root, unlock, but after flashing TWRP through GooManager, same problems...
What could it be?
Thank you very much!!! :good:
Click to expand...
Click to collapse
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.

bk201doesntexist said:
ADB doesn't flash anything in bootloader, adb is not even available there, only fastboot.
Click to expand...
Click to collapse
Sorry, fastboot.
bk201doesntexist said:
stock rom has a file (/system/recovery-from-boot.p) that overwrites the recovery if it finds something else instead of stock recovery (the "Android with triangle and exclamation mark" - pressing vol up+power here opens the recovery menu). delete or rename it.
Click to expand...
Click to collapse
I read this, but i remember that with my phone i use a option with Galaxy Nexus ToolKit or Nexus Root Tolkit to prevent the recovery from be rewritten.
bk201doesntexist said:
can't help you since you didn't do it manually through fastboot official steps. post your question in that toolkit's thread.
don't install a custom recovery from android, flash it from bootloader with fastboot. no need for root to flash it, you see. then just flash (with the recovery you just flashed, of course) a su.zip with su binary/apk and you'll be rooted. mount /system rw in recovery through adb, delete /system/recovery-from-boot.p, and you're done. reboot.
Click to expand...
Click to collapse
My phone works fine, i can't understand why in phone's friend after installing GooManager and flash TWRP recovery, system got crazy...

If you did not use the toolkit I may get around my last arse helping you......
Beamed from Maguro

When going through the options before you install your twrp use option 5 to change the name and then use option 5 after you install twrp again... then the recovery will stick. It's all in the tool kit to read. Read everything that's in the instructions. It's right there when you go to install your recovery.

This is meant to be a friendly suggestion, so hopefully I won't get trounced but here goes. In the Sprint GNEX android development section, there are two stickies that explain the GNEX toolkit method of rooting, one by QBKing77 and the other by MSkip., two smart guys. A new guy or gal might think because there's no other way presented here that using a toolkit is the way to go. Maybe a correct, long form rooting guide could be placed along side these two guides in the development section.
In the Q and A section there is a stickie by Jobakuba that explains how to root the "right", long way. It might help new people and even people that have been around a while, if her guide or something similar was along side the QBKing videos and MSkips toolkit guide.
BTW, the QBKing video is new. He added the toolkit method fairly recently with the jellybean OTA. His new video replaces a video that showed the adb, fastboot method. When you go to the old video, you get redirected to the toolkit video.

// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:

bk201doesntexist said:
// rant
// oh please, there's threads to teach how to use a toolkit? :good:
// :sarcasm:
Click to expand...
Click to collapse
Two threads to teach people how to use the brainless toolkits... vs the 6 or 7 step guide by Jubakuba on how to actually do it yourself and know what's going on.
This is what's wrong with today's Android community.

OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium

El Daddy said:
OP. See here:
http://forum.xda-developers.com/showthread.php?t=1469909
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
EDIT - deleted
Sent from my Galaxy Nexus using Tapatalk 2

Related

Problem with rooting my gnex!! HELP!

I downloaded wugfresh rooting toolkit v1.3 and did all steps up to rooting just fine. when it boots it shows the unlocked icon but when i click ok on the terminal screen and it's supped to install the su.zip and reboot into recovery so i can install the zip, it say's failed. it doesn't allow me to proceed any further and I don't know what to do??? Any help is much appreciated! Thanks in advance!!!
Kochoa940 said:
I downloaded wugfresh rooting toolkit v1.3 and did all steps up to rooting just fine. when it boots it shows the unlocked icon but when i click ok on the terminal screen and it's supped to install the su.zip and reboot into recovery so i can install the zip, it say's failed. it doesn't allow me to proceed any further and I don't know what to do??? Any help is much appreciated! Thanks in advance!!!
Click to expand...
Click to collapse
flash an insecure kernel here (just match version i.e 4.0.2) just grab 1.2 one...
make sure you have clockwork recovery (flash one for cdma/lte from next link or get official)...grab gnex-su.zip from here (on bottom of first page) and flash from recovery
done
i would but it doesn't allow me to install anything from recovery. just reboot or wipe data
Kochoa940 said:
i would but it doesn't allow me to install anything from recovery. just reboot or wipe data
Click to expand...
Click to collapse
clockwork recovery right?
you need an insecure kernel and fastboot it in (not flash from recovery)...
Code:
fastboot flash boot boot.img
ogdobber said:
clockwork recovery right?
you need an insecure kernel and fastboot it in (not flash from recovery)...
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
yes cwm.
so download that kernal from your link, got that. and then by fastboot it in what do you mean? how do i do that?
do i do it with adb?
If you don't have much knowledge about all this stuff.
I suggest you use Galaxy Nexus Toolkit from mskip (really great tool).
1/ Download the factory image 4.0.2 from Google
2/ Use the toolkit to reflash back to stock
3/ Now you can root, unlock bootloader, etc.
Hope it helps.
thanks to both of you!
I just got my Gnexus today,verizon cdma Lte. From past experience and knowledge whats the best and safest way to root Gnex? Thanks for any help,links even better.I was watching Qbkink77 VIDEOS but what you guys think?
EvoSideHustlAZ said:
I just got my Gnexus today,verizon cdma Lte. From past experience and knowledge whats the best and safest way to root Gnex? Thanks for any help,links even better.
Click to expand...
Click to collapse
it is really easy with adb and fastboot but....
just go here as heo_con184 pointed out http://forum.xda-developers.com/showthread.php?t=1400871

Unlocked bootloader, installed superuser, but still no root

Hello to all,
I just tried to unlock and root my GSM Galaxy Nexus with OS X, following the terminal command line steps. I managed to unlock the bootloader, installed superuser, but when I try to access any root application it says that the phone is still not rooted. Could anyone help me please with some specific steps for OS X? I want to install CWM, but I don't know how to flash a ROM on the GN either...
Thank you in advance!
Did you flash the SU binary from CWM?
You will probably have to re-flash CWM through fastboot to get to it again unless you renamed install-recovery.sh
http://forum.xda-developers.com/showthread.php?t=1506536
hEaTLoE said:
Did you flash the SU binary from CWM?
You will probably have to re-flash CWM through fastboot to get to it again unless you renamed install-recovery.sh
http://forum.xda-developers.com/showthread.php?t=1506536
Click to expand...
Click to collapse
Thank you.
How do I flash CWM through fastboot? I downloaded filetransfer for mac, should I just copy the CWM ROM to the device? Or is there some specific folder I should put it in?
Buddhaa said:
Thank you.
How do I flash CWM through fastboot? I downloaded filetransfer for mac, should I just copy the CWM ROM to the device? Or is there some specific folder I should put it in?
Click to expand...
Click to collapse
fastboot flash recovery <name-of-recovery>.img
or if you have root access, you can download ROM manager from the play store
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/ for a complete guide.
so pretty much what you want to do is,
1. download http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-maguro.img (MAGURO ONLY... GSM)
2. put it in the same folder as "fastboot-mac"
3. go into bootloader mode
4. fastboot-mac flash recovery <nameofrecovery>.img (I believe.. I could be wrong on this, I don't use mac but it should be somewhat similar)
zephiK said:
fastboot flash recovery <name-of-recovery>.img
or if you have root access, you can download ROM manager from the play store
http://galaxynexusroot.com/galaxy-nexus-root/how-to-root-galaxy-nexus/ for a complete guide.
so pretty much what you want to do is,
1. download http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-maguro.img (MAGURO ONLY... GSM)
2. put it in the same folder as "fastboot-mac"
3. go into bootloader mode
4. fastboot-mac flash recovery <nameofrecovery>.img (I believe.. I could be wrong on this, I don't use mac but it should be somewhat similar)
Click to expand...
Click to collapse
i'm pretty sure you have to put a ./ infront of fastboot... so it'd be like ./fastboot
Thank you very much!! I will try those steps, I am just Mister Paranoia when it comes to these things, so i want to make sure i am doing it right!
Sent from my Galaxy Nexus using xda premium
Buddhaa said:
Thank you very much!! I will try those steps, I am just Mister Paranoia when it comes to these things, so i want to make sure i am doing it right!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
If you check the thread I posted above too, it's a guide on unlocking the bootloader and gaining root from a Mac. If you skip to the steps subsequent to locking the bootloader, you should be good to go!
I tried, and I have Superuser installed when I boot my phone, but when I try to access any root application, such as Root Explorer or Titanium backup, it doesn't allow me because it says the device is not rooted. There is no SU pop-up asking permissions either. I also downloaded CWM ROM MANAGER, tried to flash the recovery from there, but again it says it doesn't have permission.
Also half of the commands on terminal don't work...
Could anyone post a very easy step-by-step guide on how I could solve this please?
Thank you!
By the way, I am on 4.0.4
You are flashing a permanent recovery on your mac, right? fastboot flash recovery recovername.img Also, you put SU.zip on your SD card, then went into ClockworkMod recovery (volume up/down + power, choose recovery) and flashed SU.zip from your phone correct? It's still not working?
anton2009 said:
You are flashing a permanent recovery on your mac, right? fastboot flash recovery recovername.img Also, you put SU.zip on your SD card, then went into ClockworkMod recovery (volume up/down + power, choose recovery) and flashed SU.zip from your phone correct? It's still not working?
Click to expand...
Click to collapse
It did work! Thank you for the help!
Use my guide in my sig, sir.

Cant enter recovery

my phone will not boot into recovery mode through CWM or by powering off and manually starting it. I get a dead android with a red triangle and ! sign, how can i fix this?
galaxy nexus (verizon)
4.0.2
rooted via Gnex tool kit
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
If you are rooted, you need to check the CWM thread for the file to delete through root explorer and then re-flash CWM to get it to stick.
Or use rom manager to flash it.
Jubakuba said:
Or use rom manager to flash it.
Click to expand...
Click to collapse
Ah yea, good point.
I prefer the difficult and manual way lol
Or re-flash your recovery from fastboot, then boot into it, and install whatever ROM you wanted.
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
bk201doesntexist said:
OR don't flash cwm at all, just 'fastboot boot cwm.img', allow it a few seconds to enter cwm, then do your thing, flash your rom/much needed zips, reboot and you're good to go.
this world is all about choice ain't it?
Click to expand...
Click to collapse
I agree. This option will let you boot into cwm once. when you finish there and reboot your nexus will wipe every trace of cwm. When you need it again just use the same trick again.
Sent from my Galaxy Nexus using XDA
anton2009 said:
That is the stock recovery. You need to permanently flash CWM (a.k.a. a custom recovery) for you to get into it.
Click to expand...
Click to collapse
Before anybody suggests I use search - I DID search, and it brought me to this thread.
Background: After unboxing my shiny new GNex last week, I immediately flashed stock yakju IMM76D using GNex Tookit.
So ... let me make sure I understand this. With stock recovery, when I fire up fastboot and select recovery, it is NORMAL to get the little dead robot with a red triangle above him? And the only way I've found to get out of it is to pull the battery? Seems odd.....
(I did temporarily flash CWM via the Toolkit and it worked fine. I don't want to leave it on as I understand it will prevent me from getting future OTA updates.)
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
If you get that error, your phone will reboot after a minute or so, but like I said it should be gone after flashing a custom ROM.
Theshawty said:
As long as you run stock ICS, you'll always get that error upon every boot, even if you rename/delete the "boot-from-recovery.p" or whatever. The only solution is to flash a custom ROM and that error will be permanently gone.
At least what I've read and heard and what it's like for me.
Click to expand...
Click to collapse
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Zepius said:
no.
you delete the file, then flash CWM.
it is not a error. that is the stock recovery and if you press vol up and vol down (might have to press power too) it should get you a menu.
Click to expand...
Click to collapse
I renamed it, it should be the same as doing away with it. However, upon rebooting, I faced that triangle. I ran stock 4.0.4 by the time.
you still have to reflash CWM after deleting/renaming the file.
Zepius said:
you still have to reflash CWM after deleting/renaming the file.
Click to expand...
Click to collapse
Which I did, but the problem wouldn't wanna go away.
Theshawty said:
Which I did, but the problem wouldn't wanna go away.
Click to expand...
Click to collapse
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
efrant said:
Step-by-step:
1) Delete /system/recovery-from-boot.p (need root of course).
2) Delete /system/etc/install-recovery.sh (need root of course).
3) Check to make sure that the above files no longer exist.
4) Flash CWM AFTER making sure the above files are not present on your system.
5) Reboot.
Click to expand...
Click to collapse
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
I haven't read about the install script but ill be sure to follow your guide when and if I ever return to stock. They're awesome.
Sent from my Galaxy Nexus using Tapatalk 2
Theshawty said:
Thanks, but no thanks. I run a a custom ROM now so the issue doesn't seem to be there anymore.
Click to expand...
Click to collapse
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Just for additional info, those files are not present on any original stock ROMs. They are added to a stock ROM if that stock ROM is updated, i.e., OTA update. They serve no purpose but to re-flash the stock recovery (i.e., which is the android lying on its back with the red !) On every boot of your device.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Theshawty said:
Ah, ok.
Speaking of nothing, what's the real deal with no OTA's available for yakju users? Is Google really working on fixing the notorious signal-drop issue?
Click to expand...
Click to collapse
Who knows? I personally don't care, and no one else should either, as:
1) the OTA update file to IMM76D is availability for any yakju user to install,
2) the full IMM76D image is available to install,
3) the IMM76D source has been pushed to AOSP.
Those are three options for you to get IMM76D on your device, with the first one being the same as an OTA update.
For me, IMM76D runs perfectly fine, and better than ICL53F.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
For me, IMM76D runs perfectly fine, and better than ICL53F. 2
Click to expand...
Click to collapse
What radio are you using? The XXLA2?

[Howto] Install a Recovery

NOTE: If anyone has any further questions about recoveries on the S3, please note that I have moved on to another device. Sorry!
So you've got your device rooted, and you want to install a custom recovery? Great! Don't just follow any guide you stumble across though, as some of the early recovery packages for the "AT&T" model were actually just copies of the custom Sprint recovery, and then you'll have all sorts of fun trying to install ROMs. ("Status 7" errors anyone? )
I'd like to talk about 4 ways to get the custom recovery of your choice onto your device.
Using mskip's Toolkit CWM [link]
Follow the instructions posted in his thread, and if you have any problems, direct them there as well!
Using ROM Manager CWM [link]
For some reason, ROM Manager doesn't always offer the correct list of devices to flash a recovery for and you won't see the SGS3 (AT&T) in the list. If that happens, force-close the app from Settings > Applications and try again. If this method just won't work for you, move on to option 4.
Using GooManager TWRP [link]
If you've been looking at ROMs, you may have noticed Goo.IM is a popular hosting website for Android developers. It's so popular, in fact, that they have produced an Android app that searches their website for updates for your ROM, and can even install TWRP with only a few simple clicks! Just open up GooManager, tap Menu, and tap "Install OpenRecoveryScript". You will be guided step-by-step from there by the app.
Note: Some people (myself included) have reported issues with this method, where the app claims to have installed the recovery, but when you reboot into recovery mode, nothing has changed. This issue may have been resolved in newer versions; I was able to successfully install TWRP using this method on Sept 26 2012.
Manually via ADB or Terminal Emulator CWM or TWRP [Terminal Emulator link]
If the other options just won't work for you, or if you would rather do an install by hand to ensure you're getting the latest version, read on...
Manually Installing a Recovery​
While this may seem difficult, it's really not. Grab a recovery image (these files end in ".img") such as ClockWork Mod (CWM) or Team Win Recovery Project (TWRP) for your device. Most ROM developers say to use CWM, but they both work equally well.
In our case, we need an image for the Samsung Galaxy S3 AT&T. Telus, Rogers, Bell, and SaskTel phones are (almost*) the exact same phone as AT&T, if you have one of these devices, you will be installing the AT&T recovery.
Now, transfer the ".img" file you downloaded onto your device. I'd suggest somewhere with a nice short path, like "/sdcard/<file>.img" (you'll thank me later, especially if you're using terminal emulator on the device)
Now, let's back up your existing recovery. If things go wrong, you can use this backup to get back to where you started.
Code:
$ su
# dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery-backup.img
That should have created a "recovery-backup.img" on your phone's internal storage.
Here's the part you've been waiting for: Flashing the new image, which installs it as your recovery system. You do this from either an ADB shell or inside Terminal Emulator.
Code:
$ su
# dd if=/sdcard/[B]<file>[/B].img of=/dev/block/mmcblk0p18
You're done. Reboot into your new recovery by holding VolUp and Home while you power on your device.
If you need to return to the stock recovery, that IMG can be downloaded here: stock-recovery.img - 10.00 MB
*NOTE: While we're on the topic, let's take a second to talk about what makes the Canadian I747M different from the AT&T I747.
The short version is... The modem. AT&T is using completely different and incompatible modem firmware in their phones when compared with the Canadian models. Rogers, Bell, Telus, and any other Canadian I747M are the same device (Samsung worked some strange voodoo and got all the Canadian carriers to agree on the same hardware!) which means that if Rogers releases a new modem firmware update, a SaskTel user could install it without issue. AT&T modem updates will not work on Canadian models, nor will Canadian updates work on AT&T phones! I've tried it. Trust me. You don't want to deal with the hassle of fixing it.
Please remember to click/stick/lick/kick the "Thanks" button if you found this guide helpful!
How bout a 4th method for TWRP?
This should come in handy for some of the newer users
Well, the other TWRP method assumes that you already have a custom recovery installed to flash the ZIP from... If you've gotten that far already, I don't think you should need me to tell you how to flash a ZIP.
theres also GooManager from the market. its how I installed TWRP just download the app open it hit menu you'll see some options come up hit "install Open Recovery Script" it will ask if your sure hit ok and your done the whole process will take 30secs
Moved to General so new members can post questions
and stuck
FNM
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
Where'd you get it from? I'll add it to the OP.
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
tonymtl said:
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
There sure is! One of the benefits of manual installation is that you can find exactly what you want to use, and not rely on ROM Manager or other tools to make the decision for you!
Sent from my SAMSUNG-SGH-I747M
dstruct2k said:
Where'd you get it from? I'll add it to the OP.
Click to expand...
Click to collapse
+1. I am also looking for stock recovery...
Sent from my SAMSUNG-SGH-I747 using xda premium
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
nekkidtruth said:
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
Click to expand...
Click to collapse
That's a known issue with any recovery on the SGS3, it seems that the hardware clock cannot be accessed by the recovery no matter which recovery you use.
Did you happen to make a backup of your stock recovery? If so, I'd like to get a copy of it to add to the OP.
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
zmore said:
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
Click to expand...
Click to collapse
I could never get that to actually work in the past, so I guess I forgot about it. I just tested it now, and it worked fine, so I've updated the OP. Thanks!
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
See my Index for flash back to stock. There is a great vid tutorial.
PS dstruct2k I have added this thread to the INDEX. Nice work
Thanks, just flashed latest CWM Touch. External SD Card support rocks
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Then you're skipping a step, or typing something incorrectly. Once DD is done its work, you should get a response saying "Copied 10MB OK" or something similar. If it says that, then the stock recovery no longer exists.
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Please visit this post and follow from step 11-15. Shows kind of messed up on the XDA app so view it on your desktop. Very detailed guide for those who are confused. Thank you.
http://forum.xda-developers.com/showthread.php?t=1912335
Sent from my T&K Blessed SGH-I747
I followed those same steps but from a different thread and it still wasn't upgrading my clockwork recovery and kept getting status 7 when trying to flash cm10. Now I installed touch version hoping I would be able to get cm10 installed but still getting status 7. Any help appreciated
Sent from my SGH-I747M using xda app-developers app

Is having 2 Custom Recoverys bad?

After achieving S-Off, thanx to Romrunners method, I flashed CWM Recovery cause I prefer over TWRP. Just wanted to know if I should be concerned in having 2 recoverys installed, and how to delete the other.
Via HTC Uno!
fullmetal509 said:
After achieving S-Off, thanx to Roadrunners method, I flashed CWM Recovery cause I prefer over TWRP. Just wanted to know if I should be concerned in having 2 recoverys installed, and how to delete the other.
Via HTC Uno!
Click to expand...
Click to collapse
OK so first off you can't have 2 recoveries. Also it is called rumrunner. ROM manager is not support for this phone. And Twrp is better. Lol
fullmetal509 said:
After achieving S-Off, thanx to Romrunners method, I flashed CWM Recovery cause I prefer over TWRP. Just wanted to know if I should be concerned in having 2 recoverys installed, and how to delete the other.
Via HTC Uno!
Click to expand...
Click to collapse
That's ROM Manager's somewhat backwards way of asking you what to do about its recovery image.
The options, from top to bottom, are "Install CWM", "I have already installed CWM", and "I have already installed TWRP."
If you choose the one that applies to you, it will stop bothering you.
ROM Manager works fine, btw - once you've convinced it that you have CWM-m7vzw installed (it can even install it itself(!)) you can back up and restore and flash ROMs 'til your heart's content–even CM10.2 nightly updates.
I have a similar question, I have cwm on my htc and want to go over to twrp. What's the best way to remove cwm?
bsbuggs said:
I have a similar question, I have cwm on my htc and want to go over to twrp. What's the best way to remove cwm?
Click to expand...
Click to collapse
You do not need to remove cwm, all you need to do is put the twrp.img file in your adb/fastboot folder, boot to the bootloader, select fastboot usb - sometimes it loads automatically to this -, type fastboot devices to confirm your device then type "fastboot flash recovery twrp_filename.img" - type that without the quotes and the actual filename with .img. Once you enter that and hit enter you should get some text saying it is being sent to your phone and it should tell you if it worked or failed.
Thanks I appreciate the help..
Sent from my HTC6500LVW using Tapatalk
Guess I need to try and install twrp again. Some folks over in the omni room forum are saying that the latest cwm is what's causing baseband issues when flashing roms (no service)
Sent from my HTC6500LVW using Tapatalk

Categories

Resources