Just installed CWM Touch Recovery, Obviously to get into recovery you must press volume up, home and power button. That is allot of key pushing and needless wear and tear on the keys. Has anyone tried using the app called Quick Boot on the Samsung Galaxy S3? I use it on my HTC phones in the past and was hoping someone could tell me before I tried if it would some how cause problems with my phone or the new Recovery I just installed.
Thanks for any input.
Vinny
try it it cant hurt anything. i know rom manager can reboot into recovery so this should work too.
I might as well give it a go, thanks for the input. I also have the paid version of rom manager, i thought you could not use the other parts of rom manager unless you flashed their version of recovery. I didn't want rom manager to overwrite my 5845 touch recovery i just installed by terminal emulator. I have been using the Stock HTC Rezound for a while and have not rooted or flashed anything in a while. Just a little rusty I guess.
Finally Verizon sent out the OTA ICS for the Rezound, what a difference. The Rezound is a great phone that has great specs and screen. This SGS3 just gets better every day.
Vinny
I use it and it works great!
t-mobile sgs3 stock rom/rooted
Related
I'm pretty new to this rooting for Android, I recently got my Incredible.. I used unrevoked to root my incredible. I did it normally like USB debugging and all that. Soon as it started to root it, the phone rebooted itself like it was supposed too, got to the HTC Incredible screen (the first screen on the boot up) and black screen and white bars on the sides. Now I got this phone like November 27th.. and I'm pretty postive my screen is an SLCD? And that seems to be what the problem is with the black screen white bars.. Thing is, of course the black screen white bars stayed there, so I pulled the battery out and put it pack in. It loaded up normally and it seemed to be rooted fine. It had the Superuser (ninja). And everything was normal. I downloaded ROM Manager and then downloaded the Flash ClockWorkMod Recovery, and then I clicked on Cynagen Mod and went down to Google apps. Downloaded it, installed it, then it asked to reboot. ALL OF WHAT I JUST DID, (followed from The Start to Finish Guide to Rooting Your Android Phone, I con't post links yet) .. So as it rebooted it got the HTC Incredible screen (the first screen on the boot up) and it did the black screen white bars. I removed the battery either twice or three times.. And still nothing, I THEN FOLLWED THIS Incredibleforum dot com (I rooted and now I only see a black screen with white bars in recovery.) and went to the Hboot menu and went down to recovery and selected it. It rebooted and still black screen white bars at the HTC Incredible screen. I then tried his other method and went to download that file and went to unrevoked and did the custom recovery and put recovery in the file and plugged my phone in. ( He actually said to like check USB debugging, which I couldnt actually do because I couldnt get to my menu..) So then after plugging it in and showing the orange light for charging. It did nothing other then charge. I turned it on ( I'm pretty sure, it might have turned on by itself) and it worked. It got the menu screen. And everything was the same. ROM Manager was still there, same with superuser. And the 3 game apps that I downloaded before I rebooted for Google Apps. I haven't found Google Apps, I'm not really sure where Google Apps would be anyways.. But what I'm getting at here is, What actually happened????? Why those white bars?? And will this happen everytime I have to reboot? If someone could just give me their best answer or an explanation It would really help. I'm new to this stuff.. But I'm getting nervous with this black screen thing white bars.. and I'm debating wether to just unroot..(how easy is unrooting?).. But my phone is fine now, I haven't tried like downloading anything but everything seems to be working fine.. Where could I find Google Apps? And which ROM? Cynagen Mod Or Bugless Beast.. Please Help
You have an slcd screen. Your recovery is for smiled. Use unrevocks recovery for slcd screens. As I have read you need that one for recovery to work properly. I don't have an slcd so I don't know to much about that end
Just cruise the forums there is tons of info out there.
Sent from CM Nightly 11-20 using Tapatalk.
I had similar issues, and poster above is correct... I was able to flash a modified clockwork recovery to get it working with slcd...but I'm halfway afraid to try any ROM Manager abilities due to the different recovery :>
Just flash the modified Clockwork- very simple and works perfectly. I have the zip if you want it.
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
mcolib8 said:
Ok cool can I have the zip file? And would I have to like uninstall anything in order to use revoked again?... and just a quick question.. 'recovery' is basically _______?
P.S. Whats like rebooting into recovery
Click to expand...
Click to collapse
http://www.megaupload.com/?d=7O9ZPP2T
You don't need to uninstall anything from your phone obviously, but I'd uninstall any unrEVOKed stuff from your computer before you do the new version. Recovery is basically the tool that lets you modify the phone. You go there to do nandroid backups and restores, and to flash zips. Let me know if you need instructions on how to apply the fix.
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
mcolib8 said:
Yeah I'm new to this rooting stuff so if you could just give me a few instructions it'd be really helpful. thanks
Click to expand...
Click to collapse
1. Mount your phone as disk drive (I'm assuming you know how to do that, if not, lemme know)
2. Move the file to the root of your sd card (not in any folders) and make sure you don't re-name it at all.
3. Disconnect your phone, wait for the card to format, and then yank your battery.
4. Put the battery back in, hold Volume Down+Power.
5. You'll see your bootloader and it will find the file automatically, let it install it.
6. Once it's done, yank your battery again and repeat Step 4.
7. This time, choose not to install it, and instead choose Recovery- should load up Clockwork just fine. Easiest way to access Clockwork in the future is thru ROM Manager- there's an option to boot into recovery.
PS. might wanna check your clockwork version first thru ROM Manager- my version is 2.5.0.5 and I'm not sure if Koush has included the SLCD fix in any of the newer versions, so I'd make sure you have that version before doing this.
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Edit... responded too late. Thanks for the advice!
Sent from my ADR6300 using XDA App
ithuwakaga said:
From what I gather, the black screen and white bars is the ClockworkMod recovery that you booted into. It works fine, but the SLCD is incompatible with the current ROM Manager ClockworkMod (I have it too, ADB works when it's running). So the display is the only thing messed up.
I'd love to get ClockworkMod to work correctly though. Anyone know how I can flash the recovery to Amon Ra, or get ClockworkMod working? I have a mod .zip file for Clockwork, but I'm unsure on how to use it.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I'm guessing you didn't read to the end of the thread before you posted
iBowToAndroid said:
I'm guessing you didn't read to the end of the thread before you posted
Click to expand...
Click to collapse
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
ithuwakaga said:
Didn't see it at the time. I'm still ungodly slow at typing on this, haha.
Do you have any advice on flashing with CyanogenMod? I read the wiki and it talked about updating a radio, but there were several options. What should I be looking for?
I'm kinda terrified trying it with these new SLCD phones, and any help would be greatly appreciated!
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
iBowToAndroid said:
Sorry, I haven't found a ROM I like as much as stock Sense, so I just use that, but with my own mods. shipped-roms.com is a nice website.. Otherwise, almost any Android forum site will have a CM section since it's so popular..
Click to expand...
Click to collapse
Thank you!
Sent from my ADR6300 using XDA App
Hey, my friends incredible is stuck on the CM7 screen after flashing the latest rom from rom manager (cwm). He's been on it for 30 minutes. Can anyone offer a suggestion on what's wrong?
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
Mine did the same. Wipe everything again and install from recovery for the first flash. ROM Manager worked when I upgraded between release clients, but for the first flash I had to install from recovery. Cleaner install, I guess.
Should I just pull the battery so I can do that?
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
I'm said friend, I tried pulling the battery and going into recovery but when I'm on the clockwork recovery it sits there and does nothing. Almost as worthless as being bricked but there seems to be hope.
The admiral, can you tell me what you did? Asap?
Sent from my GingerBlur'd, de-odex'd, modded Motorola Atrix 4G (ish.)
ASAP = bad time for the forum to go down for maintenance. hehe
Well I'm no pro at this, so just because it worked for me, doesn't mean it will work for you. All I did was a battery pull to get it off, then back to recovery to wipe phone, cache, and dalvik. Then just flashing the ROM again, and I was in.
As a general rule, if you can get past the HTC Incredible screen (the one before Clockwork Mod screen) you can flash a ROM (or restore from Nandroid, if you can't get CM7 to boot).
I agree with The Admiral...
I've had install goes bad for some reason and I've been stuck on some part of the install (the HTC white screen, etc).
After about 10 minutes I say screw it and pull the battery and try over again.
I also want to mention that I've had a couple ROMs not install when I used ROM Manager, but when I installed the file manually from the SD card using ClockworkMod the install worked flawlessly.
Boy do I ever feel stoopid...
Somehow -- don't know how -- I've completely borked CWM Recovery on my Verizon Galaxy Nexus.
Everything worked fine when I unlocked, rooted & installed CWM.
I can reboot into CWM no problem. But up/down presses move multiple entries (sometimes two, sometimes four or five). That is irritating but not such a big deal.
However, very little if functioning correctly. Most entries, when I select them, just remove the current menu from the screen, increase the brightness of the CMW logo in the middle of the screen and then lock up. I have to battery pull to continue.
Using ROM Manager I did manage to reflash CWM 5.5.0.4 but that didn't help. Invoking CWM via ROM Manager to create a nandroid still works like a champ.
Verizon Samsung Galaxy Nexus
AOKP toro, Milestone 4, Build 28
Franco Milestone 1
ROM Manager Premium 5.0.0.6
Anybody have any idea what I did? And how to fix it?
RumRunR said:
Boy do I ever feel stoopid...
Somehow -- don't know how -- I've completely borked CWM Recovery on my Verizon Galaxy Nexus.
Everything worked fine when I unlocked, rooted & installed CWM.
I can reboot into CWM no problem. But up/down presses move multiple entries (sometimes two, sometimes four or five). That is irritating but not such a big deal.
However, very little if functioning correctly. Most entries, when I select them, just remove the current menu from the screen, increase the brightness of the CMW logo in the middle of the screen and then lock up. I have to battery pull to continue.
Using ROM Manager I did manage to reflash CWM 5.5.0.4 but that didn't help. Invoking CWM via ROM Manager to create a nandroid still works like a champ.
Verizon Samsung Galaxy Nexus
AOKP toro, Milestone 4, Build 28
Franco Milestone 1
ROM Manager Premium 5.0.0.6
Anybody have any idea what I did? And how to fix it?
Click to expand...
Click to collapse
seems like you have a volume button sensitivity issue? perhaps ...
Have you tried CWM touch? You can get that the same way through rom manager if you buy the paid version. I however always flash it via fastboot. CWM touch is available from clockworkmod.com for free.
hope this helps
Edit: I just read you have ROM Manager Premium ... download CWM touch 5.8.0.2
RumRunR said:
Boy do I ever feel stoopid...
Somehow -- don't know how -- I've completely borked CWM Recovery on my Verizon Galaxy Nexus.
Everything worked fine when I unlocked, rooted & installed CWM.
I can reboot into CWM no problem. But up/down presses move multiple entries (sometimes two, sometimes four or five). That is irritating but not such a big deal.
However, very little if functioning correctly. Most entries, when I select them, just remove the current menu from the screen, increase the brightness of the CMW logo in the middle of the screen and then lock up. I have to battery pull to continue.
Using ROM Manager I did manage to reflash CWM 5.5.0.4 but that didn't help. Invoking CWM via ROM Manager to create a nandroid still works like a champ.
Verizon Samsung Galaxy Nexus
AOKP toro, Milestone 4, Build 28
Franco Milestone 1
ROM Manager Premium 5.0.0.6
Anybody have any idea what I did? And how to fix it?
Click to expand...
Click to collapse
I don't have the .img or link on hand as i'm at work, but a quick search will get you the nexus touchscreen cwm img file that you can fastboot. I think i downloaded it off the clockwork website, so check there too. No more skipping as you can manually touch what you want and screen scroll. Just one solution as i'm sure there will be many posted.
Edit: http://www.clockworkmod.com/rommanager Scroll down to correct GNex you can, second column is touch version.
hi guys, this is my problem. I'd really appreciate it, if somebode could help me here!
so, i got a galaxy nexus, rooted it and started flashing roms. A lot. Then i heard of "Android Boot Manager" (awesome app btw) and set it up like this: aokp - milestone5 as "original"-rom because i knew it would always work. then i heard of the "paranoid android"-rom (also awesome) and flashed/installed it over the BootManager. Now when i wanted to boot back to milestone5, it wouldn't let me and the app instead kept crashing. so i uninstalled it and reinstalled it from market and then it wouldn't even recognize that the original rom was milestone5. so i uninstalled it again and from now on, it's stuck on bootscreen everytime i turn on my nexus.
when i try to get into recovery mode, in comes the oh-so-famous odin mode with "downloading, don't turn off target". So all i want is to have a working phone again, so to say, a factory reset. i don't care if i lose my root or my data (made a backup), i just want to have my phone working again
Many thanks in advance for reading my "novel" i wrote up here..
I heard of this...
Something being wrong with boot manager if I remember correctly.
I'll update if I find the link.
Definitely not bricked, though.
And you're holding volume up AND down AND power, right?
Edit:
This MAY be relelvant.
But isn't how I remember the error...so I haven't exactly heard of this one.
http://rootzwiki.com/topic/24978-boot-manager-ugh/page__hl__+boot++manager
Thanks for replying, got it working again. I flashed the original factory image (4.0.4) again. Now I'm busy rooting again, but doesn't matter, my phone works again!
btw, can't really recommend BootManager at all. It's a nice idea, but it can fu** things horribly up
If u could get into recovery. U can browse to the boot manager folder. Inside it there's an update.zip folder. If u were to flash that it would boot up in your case, the aokp m5. You can read more about this on their official website.
Sent from my Galaxy Nexus using XDA
And the only rom so far that would mess up was paranoid if you check it would only show 1gb available..so in some way it wasn't mounting storage correctly but if you install paranoid as main phone rom it's fine.....you over reacted it was easy fix by going into recovery from the paranoid rom and flashing the aokp rom again.....but good you fixed it the app is great though you should try it again
I thought it was app to begin with but all other roms I tried worked fine miui, dianXin, cm9 , etc ...but for some reason paranoid would not mount sd right as an extra rom but was fine as phone rom
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Ok so over the last couple of days I tried getting a little too flash happy and thought I completely ruined my device. I could get into download mode, but not into recovery. I've tried flashing the files in Odin listed here http://forum.xda-developers.com/showthread.php?t=2584533 and usually that works. This time it didn't and at first I didn't get too bothered/noided because I thought I may have done something wrong. Fast forward to now and I was able to get recovery back on my phone and reinstall CleanROM Ace 5.0 which is a personal fave of mine. I got it to work using the instructions and files found here http://forum.xda-developers.com/showthread.php?t=2573576 and I used a very old version of Odin to do this. The one I used was Odin3 v1.85 but I also have v3.07 and 3.09.
Now I will walk you through what I did that caused this dilemma, aka doing the absolute most :silly:
It started out as me wanting to test out 2 different ROMS (eZKAT Beta found here http://forum.xda-developers.com/showthread.php?t=2747733 and Ditto Note 3 found here http://forum.xda-developers.com/showthread.php?t=2541860). My smart @$$ (sarcasm of course) didn't do a full wipe internally when flashing between the two. Reason being, I honestly just started doing that and never ran into an issue until now because of not doing it. I recently got an S5 and my 32gb sd card is in that phone and I found an 8gb sd card in an old G1 I had. So because I had ROM files and TitaniumBackup files on the sd card, I was using internal storage to house the two test ROM's. Bad idea I now know. I'm so thankful my Note II is now just a backup along with my iPhone 4S but still, it's nice to be able to experiment with a test android phone and know your primary is fully functional. Plus, all the apps I bought and things I got used to using that are strictly for rooted devices...anyway back on topic.
I flashed eZKAT and got that fully booted, even installed xposed framework and wanam both worked. That ROM is not on hold but development is currently. I'm fine with that, what was put out for us to use does work. eZdubzitmk4 does great work, and has responded to PM's from me seeking assistance in the past. So since I'm somewhat familiar with his work, I didn't think twice about trying it out. My curiosity kicked in and I thought ok, let's try a different Note 3 ROM because I've successfully flashed and used Sky Note Air (both editions) in the past and seanzscreams is another developer who does great work. I'm not saying nor implying no one else does, I'm just shouting out two developers.
Something went wrong between me switching from eZKAT to Ditto Note 3 and the only thing I can recall not doing that likely enhanced my issue was not wiping internally. I tried to flash CWM and Philz Recovery as suggested here http://forum.xda-developers.com/showthread.php?t=2541860&page=429 and I thought that would fix the issue. What actually happened was after flashing in Odin, the phone would attempt to boot into recovery and all I'd see was a navigation bar at the bottom with 4 arrows but no text and the screen would immediately fade to black and reboot. I could not get into recovery at all. I saw the Samsung Galaxy Note II splash screen repeatedly. I left it off the charger all day, and it repeated that same process the entire time. I tried using KIES and KIES3 but neither worked. I almost got something to work in KIES3 but right before the end, it failed and my phone said unsupported version in red text. I did a few Google searches at work which did help point me in the right direction.
I tried flashing stuff in the PDA slot as well as the Bootloader slot, but it didn't matter everything was the same result. My thought process was try it and see, all that can go wrong is it not boot into download mode . I prayed on it last night then did another Google search tonight when I got home from work, after attempting all that stuff again. This time I did a search for note 2 will not boot into recovery and I found this http://forum.xda-developers.com/showthread.php?t=2573576. TWRP was successfully flashed and I was able to flash CleanROM Ace 5.0 again now I'm happy ...but also EXTREMELY hesitant to flash anything else at this point. I'm just glad I no longer have a $371 paper weight ($321 for the phone and $50 for the AT&T flap cover case with attached back). I did state that if and when I fixed my phone I would create a thread about what I did and what worked for me. Hopefully this can be of use to someone else, because I know I'm not the only who has faced this issue. I also was all over Google with generic searches because all I knew was what was happening, not the technical/official name for what it was if that makes sense .
Here's a video showing what I'm describing.
I always use cwm. Just been more stable for me.
Not exactly sure what happened here tho.. Never seen that before.
I'm glad you're up and running again. I honestly would just wait for the dn3 update to flash a kit kat rom
Sent from my NoteII
I prefer CWM myself as well. I've been using it since my HTC Inspire 4G. After I got my Note II to boot and flashed CleanROM, I transferred a backup I had made in the past onto my sd card. I read before that there's an issue with TWRP and/or Philz Touch when trying to restore a CWM backup. To avoid further issues, I installed CWM from the play store, reflashed CWM Touch. Then I deleted the text from the md5 file in root explorer text editor, rebooted into recovery cleared everything then restored the backup. No issues since.
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
eZdubzitmk4 said:
I always use cwm. Just been more stable for me.
Not exactly sure what happened here tho.. Never seen that before.
I'm glad you're up and running again. I honestly would just wait for the dn3 update to flash a kit kat rom
Sent from my NoteII
Click to expand...
Click to collapse
I added a video to the thread so people can see what I'm describing.
Assassyn said:
I added a video to the thread so people can see what I'm describing.
Click to expand...
Click to collapse
Happened to me before. Since I didn't have a rom installed I couldn't boot to android so I had to use Odin..Flash twrp. Let it boot into recovery. Then pull battery and go back into download mode and use odin again to flash cwm then cwm worked fine and didn't just restart.
Since you can boot into android you can actually just download Recovery Tools from playstore to install twrp then cwm. I recommend the odin way tho
Sent from my NoteII
Will definitely look into it!
Sent from my SAMSUNG-SM-G900A using XDA Premium 4 mobile app
I had the same issue but my phone won't even boot up...can't get into recovery or download mode...changed batteries and still no go.
allaidback said:
I had the same issue but my phone won't even boot up...can't get into recovery or download mode...changed batteries and still no go.
Click to expand...
Click to collapse
Are these new batteries?
one was new...I tried 2 others. Took to sprint and they are replacing the phone. This will be my 3rd note 4.
allaidback said:
one was new...I tried 2 others. Took to sprint and they are replacing the phone. This will be my 3rd note 4.
Click to expand...
Click to collapse
Wow, sorry you've had such trouble. Have you had any issues since your replacement? I recently shattered the screen on my S5 trying an at home wifi/bluetooth fix that actually did work but I pressed too hard on the device so my Note II is now my primary again. Holding off for a Note 5 unless I can get a 128 gb micro sd card, then I'll get a Note 4.