Update: I flashed a custom kernel and have everything working again.
I have the Galaxy Player 5.0, US. So the three touch button on the bottom have stopped responding after I attempted to load ClockworkMod Recovery onto it.
Everything seems to be in order except for the home, setting, and return buttons. I am not sure if ClockworkMod Recovery could be causing it or if I should just unroot my device to fix it?
EDIT: Further Clarification may be needed for myself and you guys. I was using ROM Manager which I read somewhere bricks devices. Would the capacitive buttons not working be considered bricking the device?
This is the kernel I loaded: http://forum.xda-developers.com/showthread.php?p=20750550#post20750550
This is my first time attempting to root and then add a custom ROM to my device. Would there be a possibility of restoring factory defaults to get the buttons to work?
The kernel you linked is for the international version. Use this got the US version. http://forum.xda-developers.com/showthread.php?t=1445840
Sent from my YP-G70 using xda app-developers app
The capacitive buttons don't actually do anything within Clockwork Mod itself. All navigation there is with the volume up/down and power buttons.
If they're not working within the rom you installed, that often happens when you try to use an international kernel on a US device or vice-versa (which it sounds like you've done).
Apparently the international versions have physical buttons for those, while the US has just a dedicated area of the touch screen. Obviously, you need separate kernels for the two button types.
Related
I am now loving CM7, running great with Glitch's kernel, and enjoying learning the nuances and differences in the phone now.
I am pleased that we can do nightlies and such via Rom Manager, but there is some confusion in my mind with regard to using Rom Manager to do much of anything right now.
It seems from all my reading and experimenting that we have very specific versions of CWM for use with our various kernels and roms. It is also clear that we are not to use the three finger salute to get into CWM - and I have not tried to do so due to being told not to - only get threre from ADB or the power menu (reboot>recovery)
But if I try to use Rom Manaver to even look around, it states that I need to have CWM installed to use the features. But as I understand it, I do have CWM installed, and Rom Manager is unaware of that fact...
So - my question (long way to get there, I know, sorry, I am long winded) is do we essentially have 2 CWM's on phone now? One that is accessed from the three finger salute and will not play with CM7, and another from the power menu or ADB that does play with CM7?
Is it safe to let Rom Manager install its own version and still have access to the 'correct' version for US (meaning Fascinate users, not all CM7 users...) to use in CM7?
I'm guessing this is like when people had to apply update.zip from stock recovery, but would love to clarify the confusion in my head - I can;t be the only thick skull-ed user out here wondering about this...
A question I now have as well since I just installed CM7. Rom Manager shows no clockwork mod recovery installed, then when prompted asks for either Captivate MTD, Vibrant MTD or Galaxy Si9000 mtd.
I only have the 3 finger recovery or ask it to reboot via Rom Manager. I miss the long press of the power button to give me all those choices I used to have.
M00NEY said:
I am now loving CM7, running great with Glitch's kernel, and enjoying learning the nuances and differences in the phone now.
I am pleased that we can do nightlies and such via Rom Manager, but there is some confusion in my mind with regard to using Rom Manager to do much of anything right now.
It seems from all my reading and experimenting that we have very specific versions of CWM for use with our various kernels and roms. It is also clear that we are not to use the three finger salute to get into CWM - and I have not tried to do so due to being told not to - only get threre from ADB or the power menu (reboot>recovery)
But if I try to use Rom Manaver to even look around, it states that I need to have CWM installed to use the features. But as I understand it, I do have CWM installed, and Rom Manager is unaware of that fact...
So - my question (long way to get there, I know, sorry, I am long winded) is do we essentially have 2 CWM's on phone now? One that is accessed from the three finger salute and will not play with CM7, and another from the power menu or ADB that does play with CM7?
Is it safe to let Rom Manager install its own version and still have access to the 'correct' version for US (meaning Fascinate users, not all CM7 users...) to use in CM7?
I'm guessing this is like when people had to apply update.zip from stock recovery, but would love to clarify the confusion in my head - I can;t be the only thick skull-ed user out here wondering about this...
Click to expand...
Click to collapse
Rom manager is completely useless to us until nightlies start. You can use it to fix permissions but that's about it. Rom manager recognizes our kernel as the mtd kernel and the captivate, vibrant and galaxy s are the only mtd roms officially supported by RM. However, very soon, you will see fascinatemtd added to that list. Go ahead and use RM flash clockworkmod recovery. Even though you flash it in RM, it will use the recovery that you are already using.....so nothing to worry about.
Sent from my SCH-I500 using XDA Premium App
Thanks. Just learned from a user on another forum that hitting reboot in the power menu gives a submenu of recovery and reboot. So now I no longer have to depend on the 3 fingers. Looking forward to the ROM manager update to allow us nightlies.
kidserious said:
Go ahead and use RM flash clockworkmod recovery. Even though you flash it in RM, it will use the recovery that you are already using.....so nothing to worry about.
Click to expand...
Click to collapse
Sincerely appreciate this explanation. You sir, impress me each and every day with your patience<>knowledge.
(I used the thanks button, but I wanna personally thank you kidserious!)
Hey Everyone!
I have recently (Yesterday) installed VillainROM 3.0, and there seems to be 3 issues with it that I cannot figure out (it's more likely one, just affecting 3 things). The reason I am not posting this in the VillainROM thread is because I am a new member here, and I need at least 10 posts in order to post in a developer thread. Anyway, I love the ROM, but the problem I have relates to the capacitive keys on the phone. I am using the AT&T version of the SGS2, so it has 4 of the capacitive buttons, and no physical buttons on the bottom of the front face. The problem is with the home, back, and search buttons. When I tap the home button, it does not go "home", but instead it acts as the back button should, returning me to my last screen. Furthurmore, the back as well as the search buttons do not perform any action when pressed. The options button still works as it should. I figure it may help if I explain how I went about getting my phone to it's present state. I started a few days ago, with the full intent of ending up with the VillainROM, but as I read how to install it, it came to my attention that I first needed root access. I began by attempting to root it using Zedomax's method. Once I had done this, my phone, when I booted into clockwork recovery, would act strangly. I would see the main screen, but when I went to select an option, it would instead become a screen with just the background, and no further options, but I could still go back to the main screen with no issues. I figured I must have done something incorrectly, so I flashed my phone back to the stock kernel, and all was well, including the capacative buttons. I then found the Chainfire method, and after Accidently flashing the incorrect kernel, and again reverting it back to stock, I sucessfully achieved root access. The reason I did this was to be able to flash kernels via CWM. I then did a cache wipe as well as a factory reset, and flashed the Ninphetamine kernel, v 2.1.3. After this, I flashed VillainRom 3.0, and all went well. I quickly realized the problem, and here I am. I have no idea if this could be the issue, but since I did flash a newer version of Ninphetamine before installing VillainROM, the ROM did revert me back to Ninphetamine v2.0.5. If there is any other information that you may need, please feel free to ask. Thank you in advance for any help I may receive.
Arich Manas said:
Hey Everyone!
I have recently (Yesterday) installed VillainROM 3.0, and there seems to be 3 issues with it that I cannot figure out (it's more likely one, just affecting 3 things). The reason I am not posting this in the VillainROM thread is because I am a new member here, and I need at least 10 posts in order to post in a developer thread. Anyway, I love the ROM, but the problem I have relates to the capacitive keys on the phone. I am using the AT&T version of the SGS2
Click to expand...
Click to collapse
And I stopped reading there. You flashed a ROM meant for the GT-I9100, onto your SGH-I777. There is SOME cross compatibility, because they use the same chipset, but there are still differences, as you experienced with the capacitive keys not working right.
This is the forum for the GT-I9100. You should only be flashing firmwares/ROMs from the SGH-I777 forum.
Thanks for the very quick reply. I am assuming, then, that since VillainROM and Ninphetamine are paired, that the kernel is for GT-I9100 as well, and I should began another search for a kernel/ROM, and flash them from a stock setup?
Arich Manas said:
Thanks for the very quick reply. I am assuming, then, that since VillainROM and Ninphetamine are paired,
Click to expand...
Click to collapse
They (VillainROM and Ninphetamine) can be used independently. i.e. you can be on VillianROM and flash a different kernel, or you can be on a different ROM, and flash Ninphetamine.
Arich Manas said:
that the kernel is for GT-I9000 as well,
Click to expand...
Click to collapse
Not that it matters to you really, but I9000 is the Galaxy S 1. I9100 is the Galaxy S II. Just wanted to clear that up.
Arich Manas said:
and I should began another search for a kernel/ROM, and flash them from a stock setup?
Click to expand...
Click to collapse
Well, yes, you'll need to search for another ROM, because anything you download from the I9100 forums will probably not work right for you. Download a ROM from the I777 forum. I linked them above.
Again, Thank you. Well enough for me, one of the first posts in the linked forums is a tool to port GT-I9100 ROMS to I-777 ROMS.
No CWM for me? Primo not going into CWM recovery any way I try
So I unlocked the prime after realizing root was not the only thing I needed to start flashing ROMs.. TRUE
I rooted using Sparky's method, so easy too. I also tried to root with viper mod one time when apparently Sparkys wasnt working again after I did something like un-root for fun. But Vipermod failed due to drivers that weren't installed and still haven't, reason: could not figure out how or what part was the driver to be installed nothing i clicked on (in XP) worked to download the drivers. however XP does recognize the prime after Windows Media Player update 11 . it said flash complete or successful . I've flashed CWM from the app itself but the only real function I have from it is fixing permissions...
So should someone like me who just reads downloads and flashes (like a madman flasher) to just wait for a newer version that is fully functional so I dont mess things up and need to learn hours of great knowledge to unbrick the TFP/???
I've read that its not really working all the way is this true???
and another ?Q: I want my web to be speedy like Speedy Gonzales so what do I delete from it and what is the best web browser for speed surfing... this prime was crawling around untill I deleted some things that were uselessly running it seems to have worked a bit but not enough a delete list would be rad. Also one other question was it my order of operations which led to a faulty CWM? though I ve reflashed it several times to no better result.. And also if you are still reading (and thank you very much if you are) I dont know how to manually give CWM a go or how to manually get into recovery--- volume up and down plus power seems to soft brick the Prime untill I hold down the power button for a while untill it vibrates for a second then release and push it again to turn it on....and I held power plus volume down but such small print showed up on the upper left corner that i couldn't really know what to do... I also saw the symbols one was a USB symbol,Q: What is this function? WHat would happen should I push the USB symbol ???... ALso can I get updates from Asus after the unlocker app has been used EDIT: DON"T need them however I will find out how to turn these FOTAs off . And Q: does anybody know how to keep the Logitech keyboard connected it times out so when you go back for it it can take a good thirty seconds recovering from its nap... any fix? thanks alot I cant wait to start flashing better ROMs than stock, mine is fairly buggy
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Juggernaut 5.0
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Thanks
tedr108 said:
It is hard to tell if you tried to go into CWM correctly...here is how:
With the Prime OFF, hold the vol down button and the power button until the white lettering appears (you seemed to do that). Then, you have a few seconds to hit the vol up button. (If you wait too long, it won't work.) You should go into recovery at that point -- CWM version 5.8.2.0.
I did the first version of the recovery install manually, like you. But, honestlly, just download ROM Manager from the Market and let it install the latest Transformer Prime CWM for you. If it cannot do it, you have a problem.
If ROM Manager cannot do it, you are probably not actually unlocked. Do you remember giving your rights away to your warranty? If not, you did not unlock and you need to run the unlock .apk. Most of the guys with CWM problems did not unlock their devices correctly.
(P.S.) Personally, if my Prime had been too buggy, I would not have unlocked it. I would have RMA'd it!
Click to expand...
Click to collapse
Im giving it a go now thanks for the CWM instructions that part is solved however I asked like ten questions though and am thankful for your answers
I just did a backup in CWM thanks a lot I' d hit thank you again but its gone THANKS!!!
*If I helped hit thanks*
___________________________________
Mytouch 3g Cyanogen Mod
Galaxy S 4G Lightning Zapped! Valhalla Black
Galaxy S2 T989 Darkside Kernel ROM:Darkside
AND A VIRGIN PRIME TO FLASH BANG
___________________________________
I had a similar problem. Bought my Prime from Amazon in the USA and it came preloaded with Honeycomb - imagine that!!! Anyways I struggled as a result to flash a recovery...I seemed to get root quite easily using NachoRoot and ViperMod methods but flashing a recovery and trying to boot into recovery had me ending up with an exclamation marked Android on boot! 1 day of persistent trying and searching high and low, and am glad to report I finally have a rooted Prime with working recovery (just about to flash Touch Recovery now and then a custom ROM...) running ICS 4.0.3...
My steps:
Trying to flash a custom recovery on HoneyComb really was the show-stopper here, using NachoRoot, Memphi*, nor ViperMod...it just wouldn't work using ADB, fastboot etc
So after 1 day of trying and almost dreading having to send the device back to the US for a swap out, I decided to focus instead on upgrading my firmware to 9.x.x.15 (just below the .21 version which has no root tool at the moment!)
So downloaded a pre-rooted ICS 9.x.x.15 custom ROM from somewhere (google is your friend here) and then followed this tutorial here: http://forum.xda-developers.com/showthread.php?t=1492887
Once I was on ICS, it was then easy to use ViperMod (excellent tool!) to quickly get rooted and successfully flash CWM
Great work to the devs of the different tools I have come across and used.
great
fyi, you only need root to flash cwm FROM rom manager, otherwise you can use fastboot to flash cwm manually.
Sent from my TF201
Hey there!
I've got a little problem with my SGS2... it seems that I have two recoveries installed on my phone which seem to start up as they wish.
First I've got an (orange I think) 4.x version which seems a bit buggy and where I can't seem to choose zips on the internal sd.
Then there's the (blue I think) 5.x version which I preferably would like to use.
Normally the 4.x version starts up when rebooting from Rom Manager. Often when I use reboot in the 4.x version it jumps to the 5.x version. I can't seem to find a consistent behaviour so it's hard to describe what happens. Also I didn't intend to have a dual recovery... this just appeared out of the blue some day.
I didn't manage to flash the newest Miui 2.7.6: shortly after the system is fully running it crashes and the phone reboots. I couldn't find other people with this issue so my first guess is to resolve my recovery issues...
Any ideas?
Yes
Stop rebooting to recovery from rom manager. If you use the button combination you should get your blue recovery.
Thanks for the hint!
But are there still two recoveries located on my phone? Could this cause any problems?
get rid
I'm pretty sure I've read that rom manager has caused quite a few problems with the sII, I'd just delete the app and do without.
I'll definitely do that... I haven't heard too many good things about it actually.
However, there's really something wrong here. I tried to flash recovery touch.. the first time it said it installed fine but actually nothing happened. The second time I tried, right after the install the touch version was running. When I do a reboot though it's not there anymore. What to do?!?
Recovery is built into the kernel. If you flash a recovery independent of the kernel, it will only persist until the next reboot. If you want touch recovery, find a kernel with touch recovery (quite a few have it, search the development forums to find one you like).
So Rom Manager tempers with the kernel when flashing a new recovery?
Or is it some kind of temporary thing like when I flashed recovery within recovery?
Thanks for the replies... I'm interested to learn more about this stuff!
please do not use rom manager
it has bricked many s2
Hi XDA Developers
I am new to this and to a Dell Streak 5 recently purchased through EBay. I am interested in solving two issues on my new phablet.
It works well when it is turned on and kept running. When it has been off for a time, say an hour or two it then won't switch on, the home, menu and back buttons light and it hangs. To restart I have to remove and replace the battery and press start again. The supplier has suggested a factory reset which hasn't cured the problem, and a reload of the OS. They have pointed me towards your site for a copy of the OS but the packages you have listed aren't shown for my build number. Is it possible to use one that you do have for build 15380?
Is this likely to cure my problem?
My second question is can I upgrade to Gingerbread?
Thank you for any help you can offer.
To answer your question about upgrades, yes you can upgrade to Gingerbread. Click on the links in my signature to be taken to the two latest custom Gingerbread ROMs. Flash one of them and call it a day. The stock ROM is buggy compared to the custom ROMs. The custom ROMs do have their quirks but in general are a better option as they have had fixes applied that are not found in the stock ROM.
To answer your other question, it's possible to use any ROM package on your device, with a caveat. The caveat is that Dell divided the world into regions. Dell stock ROMs come in three parts: baseband, recovery, and the system image. These three parts must all have the same region number or else the flash will fail. The good news is that I provide a tool that will install the appropriate baseband and recovery files, if you wish to use a particular stock ROM. That same tool will also allow for installing a custom recovery, which is needed to install a custom ROM. Just make sure to immediately boot into the recovery (hold down both volume keys and press power), otherwise the recovery you just flashed will be lost.
Thank you
Strephon Alkhalikoi said:
To answer your question about upgrades, yes you can upgrade to Gingerbread. Click on the links in my signature to be taken to the two latest custom Gingerbread ROMs. Flash one of them and call it a day. The stock ROM is buggy compared to the custom ROMs. The custom ROMs do have their quirks but in general are a better option as they have had fixes applied that are not found in the stock ROM.
To answer your other question, it's possible to use any ROM package on your device, with a caveat. The caveat is that Dell divided the world into regions. Dell stock ROMs come in three parts: baseband, recovery, and the system image. These three parts must all have the same region number or else the flash will fail. The good news is that I provide a tool that will install the appropriate baseband and recovery files, if you wish to use a particular stock ROM. That same tool will also allow for installing a custom recovery, which is needed to install a custom ROM. Just make sure to immediately boot into the recovery (hold down both volume keys and press power), otherwise the recovery you just flashed will be lost.
Click to expand...
Click to collapse
Many thanks Strephon for your advice. Is this likely to cure my "fault" do you think?
You'll have to try it and find out. I do know that on rare occasions, Traveller DSC, the custom ROM built from stock, may fail to wake from sleep mode, meaning you have to power off the device completely and then turn it on again. PsudoCream has an issue where it may spontaneously reboot. I've not been able to pin down the cause, though I do suspect it has to do with low memory.
Strephon Alkhalikoi said:
You'll have to try it and find out. I do know that on rare occasions, Traveller DSC, the custom ROM built from stock, may fail to wake from sleep mode, meaning you have to power off the device completely and then turn it on again. PsudoCream has an issue where it may spontaneously reboot. I've not been able to pin down the cause, though I do suspect it has to do with low memory.
Click to expand...
Click to collapse
Thank you again Strephon for your quick response. I know that I now need to study all the info about flashing very carefully to avoid bricking my new streak 5. Incidentally I bought it to use with XCSoar navigation for glider pilots as it is highly recommended by their developers. Having got it I am keen to maximise its capability!