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.
Related
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
http://forum.xda-developers.com/showthread.php?t=1313659
Branded? Unbranded?
There is only one variant of the I777 - AT&T Branded. Anything in the Development forum for the I777 will work on an I777.
It's not like the I9100 with a bunch of minor subvariants.
drmorbo said:
After a convoluted process and many mishaps on my part (I bricked it) my phone has a working, rooted and stripped down version of 2.3.6 on it. Which works as intended except the screen is now grainy and the colors are over-saturated. (side note: unfortunately I did not do a backup of the stock firmware-stupid I know)
I'm guessing this is a driver issue with the firmware or gpu because the pictures I took before I tried getting cyanogen on my phone now look very pixelated; almost like one of those cheesy after effects. I tried updating the firmware and it said I was current. Is there a way to update drivers? Do I have to find the original firmware for my phone (I looked on here the forum with the huge list of branded and unbranded and was at a loss)?
Also in my endeavor to attain the cm7 I tried rom manager which never worked even after getting the pre-rooted firmware. It will let me download the new clockwork but it does not appear to flash it and any attempt to install or reboot to clockwork doesn't do anything (gives prompts, I say yes, nothing happens). As a result of following the cyanogen wiki twice it says I have two custom firmwares and I cannot get into clockwork at all. I could the first time through before I bricked it but now I can't. Is there a way to remove the extra kernel?
The only reason I have a working phone is because of Odin. Is there a way to use Odin to install cm7 and would that fix the display issues or am I better off finding the stock firmware and hoping the display will default back to working?
Thank you in advance,
noob
Click to expand...
Click to collapse
Are you able to reboot the phone in recovery using ADB?
Its gotten to the point where nothing I try works. I managed to get cm7 installed and it got stuck in a boot loop. Flashed back to the stripped down version again. Everything that could go wrong has. For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Thanks again
defeated
drmorbo said:
For now I just want to go back to whatever firmware came with my phone out of the box. The startup logo was at&t so I guess I'll go for the branded version (which I can't find on here--its almost 3 am I apologize for my idiocy) and hope the screen issue is resolved.
Click to expand...
Click to collapse
Which you can't find? Someone posted the link to my return to stock guide in post #2 of this thread.
If you return to complete stock using Entropy512's Return/Unbrick to stock package, you will regain the AT&T boot logo instead of any custom boot logo. The phone will be just like it was when you first took it out of the box.
If you want the stock ROM plus root, Entropy has a package for that also. Just flash one of his packages with Odin, or use the One-Click downloaders for his package that are linked in my guides.
Update: You can also download all of these from my Download Repository.
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
drmorbo said:
Okay so I did the return to stock without root one click and that went fine. However the display is still not working properly. Solid colors are fine and I even went into the debug screen and tested all the colors. They were brilliant but any dimming or shading of two colors just looks wrong. The only thing that I can think of is the bootloader is wrong. It says my phone is a I9100 which it isn't. However I'm not sure why a bootloader would affect the display. Does the I777 have a different initialization process for the gpu? Or is the issue somewhere else?
Click to expand...
Click to collapse
That might affect it but I highly doubt it.
So do you have any idea what could have caused it? I tried searching the forums but I couldn't find somebody with a similar problem.
Where exactly does it say your phone is I9100?
It shows "Samsung galaxy s II I9100" before the at&t load screen.
drmorbo said:
It shows "Samsung galaxy s II I9100" before the at&t load screen.
Click to expand...
Click to collapse
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Entropy512 said:
The return to stock did not complete correctly. This screen appears after flashing a non-stock kernel with Odin/Heimdall.
Click to expand...
Click to collapse
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
drmorbo said:
Yes. The very first method I tried was the heimdall from the cyanogen wiki. I've used various methods without success. However the last effort was to restore the phone and I used the one click stock without root. Was it supposed to restore the bootloader? Also I updated ota and the display works much better. The remaining discoloration/pixelation could have been there all along as I didn't wait long to put cyanogen on it (1 day) and I have nothing to compare it to.
Click to expand...
Click to collapse
The return-to-stock-with-root shouldn't touch bootloaders - but it should have restored a stock kernel. IF you're getting the "yellow triangle" I9100 boot screen, the last thing flashed with Odin/Heimdall was NOT a stock kernel.
There is no yellow triangle. I used the exe from the link in the first response in this forum. In any case I'll throw a picture of the phone while turned off but charging tonight. The display issues aren't grave but they are noticeable and annoying. Do you know of an app that allows you adjust graphical/display settings? Maybe it would suffice.
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
drmorbo said:
I found information concerning my display issues. Apparently it's an issue with the phone. Its called black crush. My phone has this and oversaturated red. So shading details are pixelated and reddish.
http://forum.xda-developers.com/showthread.php?t=1124669
Also I noticed people repeatedly mentioning screen modes under setting>displays however my phone does not have this option. Also all of the mentions have been under the forum for the regular version of the phone not the AT&T variant. Is the AT&T version missing this option or am I blind?
Click to expand...
Click to collapse
AT&T version is missing screen tuning unless you run a custom ROM that readds it like Serendipity VIII or Unnamed.
Okay cool. So I used the one click with root and the wifi is broken and it won't let me do an OTA. however I had previously used the one click without root and I was able to OTA and that solved the broken wifi. What would be the easiest way to fix the wifi?
Flash cwm>factory restore/wipe (I don't have cwm and I remember the cyanogen wiki way to get cwm messed up my soft buttons--two didn't work anymore)
Or
Flash the 12/21 dd kernel (I did originally try this route. However Odin didn't recognize the kernel. I even repackaged I with just zImage. Still nothing.)
Thank You again Entropy
DrMorbo
Sounds like there is something broken about the oneclick... Try flashing the return-to-stock package with Heimdall. Heimdall also lets you flash kernel zImages without packaging into a tar.
However Heimdall needs its own driver mojo on Windows - I can't really help you with this, I've flashed a device from Windows only once, and that was the Tab 10.1 because Heimdall won't talk to it.
Nevermind. I tried the update a third time. It decided to work (48 hours later). Everything works. Wifi works. The screen is better (I used voodoo screen tuning to greatly diminish the black crush and red saturation. I can finally customize my phone now. Any nifty apps you know of Entropy? (Regular or root needed)
Thank you again Entropy,
DrMorbo
I have a few questions about updating my phone to ICS roms,
Current setup,
CWM 5.0.2.3
Rom: serendipity 8.1
Rooted: yes
kernel: unsure
Desired setup
siyah kernel v3.2.7.2
mod: Pure ICS v7.5
CWM 5.5??
Questions
1. do I need CWM 5.5 to install Siyah?
2. What order should I install everything or does it matter.
Sry for the noob questions I just dont want to brick my phone :laugh:
thanks in advance for the help.
I think that CWM 5.5 comes with Siyah already. I'm not 100% sure. And it doesn't really matter which version of CWM you have, they all work the same way.
First, flash the ROM and then flash Siyah (so you need to download the CWM version).
Ok so Installed Pure and Siyah
BUT, now my phone is forking slow, and it keeps telling me things have crashed such as com.google. and Exchange service. I must have messed somthing up but i cant figure out what
It seems upon further inspection that i really messed up, I am getting a new rom to try and fix things, the rom i have on my phone right now will not do ANYTHING, ill update when i get somthing figured out so others can avoid my mistakes.
Ok so i got Omega Series v15
installed and working....sort of, on the bottom of the phone the menu button works like a back button, the back button and search button both do nothing.
also the screen will dim but never black out on its own. So i still have things to figure out
weaponzero said:
Ok so i got Omega Series v15
installed and working....sort of, on the bottom of the phone the menu button works like a back button, the back button and search button both do nothing.
also the screen will dim but never black out on its own. So i still have things to figure out
Click to expand...
Click to collapse
You sure you have an I9100? The I9100 doesn't have a search button.
Sounds like maybe you have might have one of the US variants...
Check the label under your battery.
If the model number says:
SGH-i777, go here.
SPH-D710, go here.
SGH-T989, go here.
If it doesn't say any of those three, plug the model number it DOES say into google, followed by "site:forum.xda-developers.com" to find the forum for your device.
EDIT: a quick google of "Serendipity 8.1" reveals this as a ROM for the AT&T Galaxy S II, which is the SGH-i777. Follow the i777 link above.
Hello first time rooting this phone. Its a SGH-I777. I used the guide from galaxys2root.com/. At first it didnt work because my computer didnt recongnize my phone. I tried a different computer and it seemed successful until it rebooted. When the phone rebooted it did nothing but stay on the first screen. I still have the ability to get into Odin mode(download mode), but that is it. When i put the phone in download mode and use Odin it allows me to download the "zimage" but after rebooting it is the same exact thing. I have tried the one click root, one click factory restore. Tried restoring it on Kies. and nothing work took it to a store and the guy said he tried but it would stop in the middle of the download the only option i had with him was purchasing a new mother board for $80. Does anyone have a solution that can help me fix my phone.
Before i attempted to root it, it had OS 2.3.6 with kernal 2.6.35.7.
Go to the development section and read the stickies. There you will find stock rooted packages you can flash with Odin.
Sent from my SGH-I777 using xda premium
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
jmula said:
the only option that i have is to put the phone in download mode. when i try to download any kernel it reboots and does not go past the booting screen with the triangle.
Click to expand...
Click to collapse
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
creepyncrawly said:
You should be able to enter recovery. Hold down all three buttons, vol+ vol- and pwr, continuously until the phone boots into recovery. It could take 10 or 15 seconds or more. If that is unsuccessful, then since you can enter download mode, you will need to flash back to stock, or stock plus root. That is not just a kernel, but the entire package. Please see the links in my sig for instructions.
The dropbox links in the download repository are temporarily suspended until probably Monday night or Tuesday as someone abused and over-downloaded. But the hotfile links still work.
Click to expand...
Click to collapse
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
jmula said:
i Downloaded ''UCLE5 Stock ICS plus Root'' . i placed the phone in download mode started Odin and placed file in PDA. It starts but gets stuck at cache.img
Click to expand...
Click to collapse
The next thing I would suggest is to try and flash the UCKH7 full stock package with bootloaders. However, as the dropbox links in the download repository are currently suspended, you will have to download it from SamFirmware. To be able to download, you will need to register for free if you havn't already. Search sgh-i777 in the upper right hand corner of the page, then download the I777UCKH7 version. Let us know if that will flash.
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
jmula said:
Ok it finally wokred after countless times of changing usb ports. I used the one click recovery. It restroed my phone to 2.3.4 i had 2.3.6. I tried to update by kies to 4.01 and it didnt work. Kies froze. The queestion is how do i safltey root the phone?
Click to expand...
Click to collapse
Flash a .tar version of a custom kernel with Odin. I always use an old siyah.tar, but that's just me. There are other methods floating around but that's the quickest and easiest for me. I think there's an old entropy dd.tar around somewhere too. But just flash it through Odin and you're good to go, assuming you flashed one for your version of android. If you just want to get into recovery to flash something this works as well.
There may be links to tar versions of the kernels in creepy's sig I don't remember offhand.
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
jmula said:
Ok since i do not want to brick my phone again where it is just stuck at the boot loop. I tried looking for ways to root and when i tried some of them my phone went back to the problem it had it the beginning. Should i just call it quits or do you guys have a guide?
Click to expand...
Click to collapse
Give up???
I personally don't think flashing a kernel with odin is the best way to root. It increments the flash counter, for one thing, though I'm not sure how many people care about that anymore. I would suggest that you use the stock plus root package to root the phone with odin. See the links in my sig.
Guide... did someone say guide?
Feeling the pain....
creepyncrawly said:
@jmula,
Enter recovery and perform a wipe data/factory reset. That may clear the failure to boot. If not you'll need to flash back to stock and start over.
The yellow trangle is a result of flashing a custom kernel using Odin or Heimdall, and is expected. You are not the first person having problems with the tools provided by GalaxyS2Root. In the future, I would recommend you avoid his site.
And... as suggested, read and study till you understand the basics. Then if you have questions, feel free to ask.
Click to expand...
Click to collapse
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
judib said:
First, to Creepy....you've been a great resource here and I read a lot of what you post and you got me out of the very jam being discussed here. I made the mistake of trying to root via the galaxys2root.com site (actually, I thought it was a different site...was redirected), got the i9100 screen and a boot loop...couldn't go anywhere. I came back here and found resources eventually unrooting my phone all the way back to 2.3.4, then moved to 2.3.6, then the stock android 4.0.3 which updated to 4.0.4.
But I still want to root (4.0.4 shuts itself down A LOT...more than 4.0.3) and I have a Galaxy note 10.1 with JB 4.1.2 and I LOVE IT! I feel on a mission to get rooted and try out some of the JB roms I see talked about here, but can't seem to find the best way to root. I've heard exynosabuse referenced here (no links to it though) and I don't want to use the wrong one and mess up my phone. I've been reading for weeks here and there's obviously a lot of great material, but I'm not sure which material is critical to understand, and which is "nice to know" but might not even apply, and which material isn't even right. Very frustrating.
Judi
Click to expand...
Click to collapse
The ExynosAbuse application is the only practical way to root 4.0.4 without changing base. You can download it as an attachment in the OP of the developer's thread, but read through the thread first to understand its limitations and risks.
Alternatively, you could flash 4.0.3 plus root from the development forum. If you choose that route, please read the thread to understand how to install a custom kernel, which is recommended whether you plan to install a custom firmware or not. The custom kernel will contain ClockworkMod Recovery so you can flash the firmware of your choice if you wish.
There are really several routes you could choose. All of them work. Another would be to flash back to stock Gingerbread plus root. For that see my guide How to Flash Custom Binaries Without Ever Incrementing the Flash counter!! (link in sig)
Hmmmmm..
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
b0bb said:
Well, I see that their are many, more experienced than me following this thread and my following comment is not meant to jump on the knowledge train here, but............... I had the same event happen as the orig poster earlier today. I had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII, What I did was go into recovery ,cleared the Dalvik cache and that is all I cleared. Then I re-installed the RR Rom .rar, which I keep on my SD, over everything and rebooted, it came back as it was 4 mins before . All I did after, was do a system restore(only) using Titanium BU. So when I see all the "clear and restore this and that" I started to doubt some of the more experienced than I. My 2 cents is, that, if one does not know EXACTLY ,how to correct an issue,leave it for our more knowledgeable brothers and sisters.
If I am wrong ,please except my appology.
Click to expand...
Click to collapse
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Phalanx7621 said:
I don't know what you're trying to get across here. Yes, restoring a backup nandroid works. Yes, you can try wiping cache and dalvik to see if it fixes an issue. Yes you can restore apps via titanium backup. All these things are indeed true.
Click to expand...
Click to collapse
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
b0bb said:
Well if you did not fully grasp what I was trying to get across,you seemed to get it correct with your statement.
Click to expand...
Click to collapse
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
creepyncrawly said:
And yet you say, "All I did after, was do a system restore(only) using Titanium BU." This may have worked for you, but this is an absolute recipe for disaster, and should not be given as a recommendation.
And further, from what you say, you did not have the "same event happen as the orig poster." Instead you "had installed an app,I then rebooted and it got a bit stuck on the Galaxy SII." This is by far not the same as trying to root with a tool from GalaxyS2Root.
Click to expand...
Click to collapse
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
b0bb said:
Hey Bro, I think you think that I am challenging you, trust me I am not and I thank you for correcting me and putting me in my place, which is a bit phone techie challenged, I'll stick to building submarines. Thanks for what you do here.
Click to expand...
Click to collapse
Not at all. I want people to help others here. I want you to help other here as well. But it is important to post only accurate information. Inaccurate information can cause someone to do the wrong action. So I always correct misinformation.
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
weati said:
I've tried to put a new rom on phone after installing cwm. The 3 different jellybean roms that I've installed will not load up. They all stay on the loadup screen and never finish loading. I never had any problems flashing previous phones with CWM. Anyone's help would be appreciated.
Click to expand...
Click to collapse
Are you following the instructions as stated in the op?
Sent from my SGH-I777 running AOKP
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
No
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Phalanx7621 said:
He used Rom Manager. Like a bad bad little boy. Or at least that's what I'd put my money on.
Click to expand...
Click to collapse
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
And because this phone isn't other phones, you can't use rom manager with it. It's a nono. And there is a sticky about it. And many threads. And posts. Warning about it.
thanks
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Butchr said:
I have seen this on a few different roms. After the rom hangs on the loading screen go ahead and reboot the phone. If that doesn't work flash a different kernel, and try to boot. If that doesn't work let me suggest Shostock 3. Try that rom. I have never had a problem flashing that.
Click to expand...
Click to collapse
weati said:
Guess I should have tried that before restoring my cwm backup and ordering a different phone. I needed an unlocked phone anyway LOL.
Click to expand...
Click to collapse
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
mattdm said:
Let me get this straight. So you:
1. Decided to flash first and look later, using a method that "worked on other phones."
2. Didn't search the forums or even look at the stickies to find a solution to your problem.
3. Gave up and ordered a different phone rather than taking the 10 minutes it would take to easily get yours up and running?
Wow. Just wow. Tell me this; what phone did you order as a replacement?
Click to expand...
Click to collapse
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
1. Kies generally only works with stock unrooted phones. Use Odin instead.
2. The phone has no "inability to take a new rom" if you do it the right way.
3. Apparently you don't know pretty well what you're doing.
4. The i9100 works exactly the same way as the i777, and if you try to use Rom Manager on it, you'll end up with the same result: a phone that won't boot.
5. AT&T will unlock an i777 for you if you ask them.
6. Just read the damn stickies, particularly this one and this one.
This thread is full of win.
weati said:
I just installed CWM and flashed the Roms. I've never had problems with other phones with this method. I followed the original post completely and the first Rom I tried was the cyanogen 10.1. The phone wouldn't connect to Kies to update either on 4 different systems with different operating systems. I ordered an unlocked S2 from Amazon and taking this one back so the problem is resolved.
Click to expand...
Click to collapse
You resolved the problem by buying the unbranded version of the exact same phone?
weati said:
I wouldn't say that I searched the forums and flashed the roms the exact way you are supposed to for the phone. This isn't my first andoid and I know pretty well what I'm doing. The phones inability to update with Kies or take a new rom pissed me off. It was worth the extra 70 for me to get unlocked phone anyway. I ordered an unlocked S2 9100.
Click to expand...
Click to collapse
So u paid 70 dollars to unlock a phone. Great hope it was worth it. Because like others have said they are identical.
Sent from my SGH-I777 running AOKP
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Applejackson said:
As the title says, I'd like to flash Ditto Note 3 ROM v5.2. I am currently running Alliance ROM build 26 with TWRP 2.7.2.0.
What I'm looking for is a basic step-by-step (I feel pretty confident about finding detailed breakdowns of each step so please don't put yourself out too much--I'll follow up if there's anything I don't understand) so that there's nothing I miss, leaving me with a bricked phone, a locked bootloader that I can't revert, or non-functional radio/modem/anything.
I'm fine with ODIN, flashing, recovery, and other basics. I'm really just looking for each step that is ABSOLUTELY REQUIRED in order to not run into the problems mentioned above. I'd like to be able to get back to where I'm at now in case I decide I don't care for DN3. Thank you in advance.
I've attached a screenshot of "About Phone" in case the info helps.
I've also never taken an OTA or used an OFFICIAL stock ROM except for the one it came with, I rooted and unlocked as soon as it was possible after day one of release with no updates/upgrades prior (pre-ordered from Verizon, first ROM was BeansTown build 1 ).
Is what I'm asking possible? Can this be done without relocking the bootloader?
Click to expand...
Click to collapse
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Thanks for the reply.
devious_z said:
Since you are already using Alliance B26 (an MJ9 based ROM), you shouldn't need to use ODIN for anything.
I simply followed the instructions in the DN3 post, and I was up and running w/o issues.
I'm not sure about TWRP, bc I used the latest version of Philz myself, and had no issues. I've heard of some people not having issues with TWRP, and others who did. Seems like YMMV, based on all the posts I've gone through in that thread (you should go through it yourself and get an idea).
Also, I am having the odd lockup every so often with this ROM (I believe it is deep sleep based), which a few others are also experiencing. Outside of that, I love the ROM too.
Click to expand...
Click to collapse
Thanks for taking the time. I guess my main concern was with the bootloader and whether or not I had to upgrade it and possibly lock it accidentally, or if I could just stay with the bootloader I have now, which is actually VRUEMJB. Used the method outlined in the AllianceRom thread for flashing the ROM. Since I still have a virgin bootloader I didn't want to lock it. I think I'll just try flashing the ROM as I have it, after a wipe of course, and I can always flash a recovery backup if need be.
I did try looking through the info in the threads for the ROM, but there are thousands of pages on the original and 90+ in the [**UPDATED] Verizon DN3 thread. The ones that I have read through have some conflicting information, so this query is really just to eliminate any confusion on my part before changing anything I can't change back.
Update: Tried and failed.
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Applejackson said:
Just an update, I tried with my current configuration as I said I would above. Factory Reset, Data Format, the whole nine yards, and everything seems to go smoothly until the final reboot after everything is installed. The phone just hangs on the Samsung boot image and never goes any further. Tried reinstalling twice after but always the same problem. I was able to flash my previous backup no problem, so no damage, but no joy either. Any ideas?
Click to expand...
Click to collapse
I guess I would start with reinstalling the MJ9 firmware through odin, and then try the rom again. You mentioned you were actually on MJB earlier which doesn't sound right.