Related
Im rooted and im trying to go to 2.2, i'm on 2.1 right now.
When i go into recovery mode my phone pauses at a white triangle with a orange exclamation point inside and a droid(green guy) person underneath.
what do i need to do to get into recovery mode.....
You need a custom recovery, I recommend AmonRA, you can use jcase's 1Click Eris root to install it. Or you can download it and install it using Terminal Emulator,I'm on my phone now, can't recall the steps, just search for how.
Thats odd that your rooted without a custom recovery. Perhaps it got deleted somehow.
Anyways, as stated above, the one-click root is your best bet. Download it from the market, run it, then do a full reboot, then boot into recovery and you should be good to go.
thanks
IT worked, updating to froyo right now!
hey folks,
although i'm aware of several threads regarding cwm, my question is little bit different. hopefully I've not overseen something and it's ok to ask (again?):
just trying to flash cwm in order to be able to flash an alternate black status bar, but i'm on 351 and only found cwm recovery imgs for 345. isn't there a difference?
downloaded cwm 2.5.0.7. can I use the contained recovery file?
re-installed everything at the beginning of the week. if possible it would be great not to have to start from scratch again ...
thanks,
marc
crd_x said:
hey folks,
although i'm aware of several threads regarding cwm, my question is little bit different. hopefully I've not overseen something and it's ok to ask (again?):
just trying to flash cwm in order to be able to flash an alternate black status bar, but i'm on 351 and only found cwm recovery imgs for 345. isn't there a difference?
downloaded cwm 2.5.0.7. can I use the contained recovery file?
re-installed everything at the beginning of the week. if possible it would be great not to have to start from scratch again ...
thanks,
marc
Click to expand...
Click to collapse
I think you'll be fine with that one. Is there a reason you don't want to use Streakmod? I find it superior to clockworkmod for our devices in almost every way. Worst case scenario if you flash that one is you won't be able to boot into it. If that happens, flash a different one. Have you seen this thread? It has an easy to use tool for flashing lots of recoveries.
http://forum.xda-developers.com/showthread.php?t=1000455
will look into it tomorrow. in order to update minor things like the status bar and keep the stock image, which method would you choose?
hm, flashed cwm 2.5.0.7, but that didn't work. when trying to enter recovery i only get a blank screen
edit: fail - rebooted the device and the stock recovery appears.
http://forum.xda-developers.com/showthread.php?t=1047345
that worked. flashed streakmod successfully and applied gingerkrad351. only thing that's missing are white icons, but so far overall success!
So has CWM Recovery been fixed? The whole not being able to charge the phone if the battery died. I would like as many people to chime in so I feel assured that it either has, or has not been fixed. The latest CWM Recovery that I am inquiring about is 5.8.1.4.
I still consider myself a n00b with this stuff, but it seems like I'm still having the same issues with CWM that everyone else is describing.
Most importantly for me, CWM freezes every time it tries to make a nandroid backup. I had the amon recovery, but I guess I installed CWM through the ROM Manager app, not realizing what I was doing. No matter, though, since I couldn't get amonto make a nandroid backup of my Rezound either.
So if anyone can help me figure out how to make a nandroid backup, that would be great ...
bloodymurderlive said:
I still consider myself a n00b with this stuff, but it seems like I'm still having the same issues with CWM that everyone else is describing.
Most importantly for me, CWM freezes every time it tries to make a nandroid backup. I had the amon recovery, but I guess I installed CWM through the ROM Manager app, not realizing what I was doing. No matter, though, since I couldn't get amonto make a nandroid backup of my Rezound either.
So if anyone can help me figure out how to make a nandroid backup, that would be great ...
Click to expand...
Click to collapse
I am not sure what version of Amon Ra you tried to flash or how, but are you on the new firmware or old ? Regardless, download the newest Amon ra recovery img and place it in the same folder as you used to unlock with.
Bring up a command prompt , and change directory if needed to the folder containing your image. Have phone connected in hboot so that it says fastbootusb ... then type in fastboot flash recovery "nameofrecovery".img
This will flash the recovery ...
In recovery just choose backup/restore...nand backup ..press power to confirm and it will make a backup.
mjh68,
Thanks for the info. I will probably try again when I get home. But since I had problems with amon last time, do you know where I can get the version of amon that I should be using for my Rezound?
Here's my software info:
Android version 2.3.4
HTC Sense version 3.5
Software number 2.01.605.11
If amon works better than CWM currently does, at least for nandroid/B], I will definitely let you know. Too bad CWM doesn't just work, though ...
Use 3.15, use scotts clean flashtool. It taked the adb commands out. You can find it on his website
Sent from my INCREDIBLE, faster than a THUNDERBOLT, REZOUND!
Alright, I followed Scotty's "temporary recovery" instructions here: (darn, link not allowed for n00b's ... the title is "Scottys noob friendly root guide-start to finish" at androidforums)
These are the same instructions I used to root my phone in the first place.
I went into Amon.
I selected "Nand backup".
There were several options on the next screen. It looked like this:
- [X] boot
- [X] system
- [X] data
- [X] cache
- [] recovery
- [] sd-ext
- [] .android_secure
- [] .android_secure_internalsd
- [] compress_backup
- Perform Backup
- Return
I left the selections as they were, then selected "Perform Backup".
Before confirming my selection, it said:
Use Other\recoverylog2sd for errors.
I confirmed my selection. It gave me the following messages:
Performing backup : ..
Oops... something went wrong!
Please check the recovery log!
So now I'm stuck, and it looks like Amon is not working as an alternative to CWM.
I looked for Scott's clean flash tool, but I couldn't find it anywhere. Would that even make a difference?
Did you flash the ics ruu leak..if you did and are going back to gb there's a sd card patch he made. Also amon ra has a version 3.15.
Not sure if anything I said may help....just some ideas/thoughts.
Sent from my ADR6425LVW using XDA
I just realized, you're right ... I'm using Amon 3.14, not 3.15 ... But I don't see the download for 3.15 on the link that Scotty provided ... Anyone know where I can get it from?
Here you go....
http://forum.xda-developers.com/showthread.php?p=23781936
from my ADR6425LVW using XDA
Thanks. Again, I followed Scotty's "temporary recovery" instructions. This time, however, the md5 in the command window did not match the md5 at the link you gave me ... ?
This is probably a big no-no, but I flashed it anyway ... Nothing bad happened to my phone, but it gave me exactly the same message I described earlier.
Still no CWM alternative for nand backups.
Thanks for helping me with this, everyone ... mega thanks.
Guess I'm going to move my questions to another thread, since they're becoming more about nandroid than CWM (or finding an alternative to CWM).
bloodymurderlive said:
Guess I'm going to move my questions to another thread, since they're becoming more about nandroid than CWM (or finding an alternative to CWM).
Click to expand...
Click to collapse
CWM does have some problems but all of them are fixable from what I understand. The alternative to CWM is AmonRa. There really isn't anything else.
i choose the cwm route.... i am now flashing back....cwm will NOT charge a dead battery or let you turn it on.....u have to keep messing with it or boot into bootloader to charge...its a pain in the butt
Hi all - the weirdest thing is happening to me and it is definitely something I've done but I haven't the slightest what it is.
I've got CMX right now, and I've tried to go to a couple of ICS ROMs (Task, Sonic). They flash just fine, but on the new system if the screen goes to sleep the video flickers on screen wakeup. I have tried to remedy this by flashing an ICS kernel but haven't had any luck whatsoever. So today I thought I'd go back to my Nandroid backup that I took on CWM 5.0.2.7 way back on the 1st before I rooted my tab. I was on (and prefer) TWRP so I used Odin to re-flash the original recovery, wiped everything (including format /system from the Mounts menu to wipe the ROM) and restored the backup. Everything seemed fine. But to my horror, I locked the screen and woke it up to find the same flickering!!!!
I rebooted back into recovery and flashed TWRP back on so I could restore my CMX backup and I'm back to normal again. But now I feel like I'm stuck here, and the only way I'm going to be able to fix this issue is by using Odin to flash a stock firmware package. I really don't want to have to do that if I don't have to but will if I need to of course...
The one thing I haven't been able to get an answer on is before blowing everything away is what I'm asking now...in thinking about it, I had taken the backup before flashing a bootloader to fix my "rolling recovery screen" issue. Could the cause of this type of problem be a bootloader that the ROM doesn't like, or is this a crazy assumption?
OK I'm going to bump this thread with a simple to-the-point question - hoping for an answer as I work out my theories.
For those of you who have flashed ICS and custom recovery with no "rolling/flickering" issues - are you using an unlocked bootloader?
For the bootloader you just hit the point my friend,the bootloader that we use to fix rolling recovery problem has issues with most kernels except Pershoot's HC or CM9...
For your problem you should think of grabbing the official ICS or HC(just for getting rid of screen flicker),and in addition to flashing it you should extract it's stock bootloader,make a. tar.md5 out of it and keep it for future similar problems...
Note that the bootloader can only be flashed using Odin in PC and CWM or even stock flashing using MobileOdin can't make changes to it(or recover it)
For now there is not a proper fix for that but I think the best way is to have the stock bootloader and use ROMmanager or MobileOdin for flashing(since the recovery rolls with stock bootloader)...
Yeah I flashed stock ICS and rooted yesterday. I am just going to fight through the rolling recovery for now and stick with ICS until we can do more.
Thanks for the response!
some trick:you can rename the zip files you're going to flash so that their name starts with "Z",it's then easy to navigate to them(just press vol down twice)
Yep! That works, and you can also rename files as update.zip and use that option I believe. It's time to think outside of the box a bit with regard to flashing some ROMs...thats the bottom line. i am sure there are a few devs on this site that would appreciate it if we did more of that lol!
guys im really getting the same problem now... and i dont know what to do
would you be able to help me please?
New to this - I really apologize if this has been covered before but I've been searching all evening and not coming up with a definitive answer.
What's the easiest way to remove a custom recovery (like twrp) and go back to stock? Still on the stock rom, just have custom recovery. I manually deleted a nandroid backup using a file manager from my sd card yesterday, and now when booting into recovery it sits on the twrp screen for easily 10-15 minutes. I can't fathom why that would have an effect on the start up time but that's all I can think of that changed. I've tried re-installing twrp via goomanager - no change.
Is there a way to do so without using usb? I'm curious because the first S4 I had, the usb port went bad after only a month and I was in a panic that I wouldn't be able to get it back to stock (until I finally got it to work long enough to flash it with odin). Really don't want to risk that happening again.
Looking to run some roms once I think I understand at least half of what I'm doing, but trying to be cautious. I'd like to keep twrp but I want to make sure it's working right by loading a clean install of it.
Thanks in advance.
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
gadget! said:
A lot of users are experiencing the lag with TWRP version installed by Goo Manager - (TWRP 2.6.0).
The link below has a flashable zip to version 2.5.0.2, this version seems to be stable and doesn't lag at the TWRP screen for most people including myself.
I would try flashing this and I think it will solve your problem.
http://forum.xda-developers.com/showpost.php?p=45006486&postcount=289
Click to expand...
Click to collapse
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
You flash it via recovery. Put in your sdcard/internal boot to recovery amd use the install zip option. Navigate to where it is and flash away.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk. now Free
bretbretterson said:
Thank you. I'm a little stumped on what to do with the zip now that I have it though and all my searching for "loading recovery with goo manager" just shows the method to load the newer version. Or if you're supposed to load it via pc, what do you use? Odin doesn't like any of those file types.
Sorry if this is a dumb question. Probably just not searching for the right thing.
Click to expand...
Click to collapse
Yes, it is a flashable zip, just flash it in the recovery you have now.
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
margentieri said:
I found this post based on the OP's original question, "how to remove TWRP recovery".
I have been flashing rooted ROMs for a while now via ODIN, but am just now starting to foray into the realm of custom recoveries. Before I install TWRP though, I wanted to know how to remove it just in case something ever goes wrong. That is, I've been avoiding the use of a custom recovery so far because if something ever happened to my device, I could just flash the stock ROM, and having already used Triangle Away, Samsung will never be the wiser and would service my device, but with a custom recovery installed, they would be able to see I'm not running totally stock.
So, is there a way to completely return my device to 100% stock after installing TWRP? And if so, how would I go about doing that?
My device is a Samsung Galaxy Note 10.1 GT-N8013, currently running a root injected stock ROM, 4.1.2
EDIT: I just noticed that this is in the S4 forum, which my N8013 obviously is not, but the answer to my question should be the same regardless, yes?
Click to expand...
Click to collapse
Answer would be device specific
Sent from my cm_tenderloin using xda app-developers app
Thanks Gadget, Hex. TWRP 2.5.0.2 works great. But just for future reference, is the only way to revert to the stock recovery by flashing a stock device image via odin over usb? So if the USB port were to fail entirely, I would be SoL - correct?