New to samsung switched from htc - AT&T Samsung Galaxy Note I717

just as it says im new to samsung not to android, my question is i followed the root guide and can get to the recovery screen but everytime i try to flash a rom it fails to install the rom, did i do someting wrong in the rooting prosses? i have the samsung att i717

jjpeasl said:
just as it says im new to samsung not to android, my question is i followed the root guide and can get to the recovery screen but everytime i try to flash a rom it fails to install the rom, did i do someting wrong in the rooting prosses? i have the samsung att i717
Click to expand...
Click to collapse
you do have an alternate recovery, right
most likely very simple...............is it a STATUS 7 ????
if so, you just need to update your recovery.
if you are using CWM, many ROM's suggest TWRP. some are not having problems with CWM, but TWRP is much more user friendly and don't have to mess with vol +/- buttons

You don't need to be rooted to flash a rom.
Either flash from the phone using a custom recovery like ^^^^^ described, or flash from a pc using samsung software (Kies or Odin3).
All custom roms are rooted by the developer.

You know YouTube helps if you think you are having trouble it shows you how to do it.

Related

[Q] Help think phone is bricked

I recently rooted the phone and wanted to install a custom rom. When I tried to back up the current stock rooted rom with rom manager, someone went wrong. So I was then stuck on a flashing black screen. But I can still access Odin/download mode. But whenever I try to flash something, it flashes, but the screen just reboots back to the flashing black screen. Help please I dont know what to do
What firmware base did you start from, and what method did you use to root the phone?
Rom Manager is not recommended for use on the I777 phone. You need a custom kernel which contains ClockworkMod Recovery to back up the phone. Did you try to install ClockworkMod Recovery from Rom Manager?
Need more information before we can help. So, answer the above, and provide as much detail in addition as you can.
I almost messed my phone up by not rooting or flashing a ROM the proper (safe) way and ended up using a return to stock / unroot guide to start fresh and just follow the guides for rooting and installing ROMs from there.

[Q] How to Root and Flash using the latest tools..

Hi everyone,
I'm trying to flash a Samsung Galaxy S2 I9100 running Stock Android v.4.0.3 on Baseband I9100XXLPH.
I've searched a lot of threads but it seems that over the years there are 5 billion ways on how to root, install CWM and flash a ROM.
I'm not a 100% noob in this area as I successfully unlocked, rooted and flashed my HTC One X lately but:
Could someone please tell me the easiest way of rooting, installing CWM and flashing CM9.1 using the latest tools out there? Please also let me know on how to upgrade the Firmware if thats needed. I tried using Kies already but It keeps telling me that the device doesn't support that. And if someone could explain to me what a insecure kernel is compared to a original one, that would be fantastic!
I've already tried flashing CWM 5.8.1.5 using the standard samsung recovery but once I select "apply update from external storage" and select the CWM zip it starts CWM but after one reboot its gone again. I can repeat these steps everytime I would need CWM but isn't it supposed to replace the default samsung recovery?
Thanks in advance!
Memphizzz said:
Hi everyone,
I'm trying to flash a Samsung Galaxy S2 I9100 running Stock Android v.4.0.3 on Baseband I9100XXLPH.
I've searched a lot of threads but it seems that over the years there are 5 billion ways on how to root, install CWM and flash a ROM.
I'm not a 100% noob in this area as I successfully unlocked, rooted and flashed my HTC One X lately but:
Could someone please tell me the easiest way of rooting, installing CWM and flashing CM9.1 using the latest tools out there? Please also let me know on how to upgrade the Firmware if thats needed. I tried using Kies already but It keeps telling me that the device doesn't support that. And if someone could explain to me what a insecure kernel is compared to a original one, that would be fantastic!
I've already tried flashing CWM 5.8.1.5 using the standard samsung recovery but once I select "apply update from external storage" and select the CWM zip it starts CWM but after one reboot its gone again. I can repeat these steps everytime I would need CWM but isn't it supposed to replace the default samsung recovery?
Thanks in advance!
Click to expand...
Click to collapse
Hi!
If you want to flash firmwares, here's how http://androidflip.com/how-to-install-flash-firmware-on-samsung-galaxy-s-2-gt-i9100/
But you're on XXLPH, so I suggest you use this guide to root: http://www.androidauthority.com/root-xxlph-on-galaxy-s2-i9100-using-cf-root-kernel-54416/
and that'll get you started somewhere..
Here's the index of guides for our s2: http://forum.xda-developers.com/showthread.php?t=1826497
I hope this will help you!
Cheers

[Q] Flashing ROMs without ClockworkMod - POSSIBLY BRICKED

Hi,
I am unsure about how to flash a ROM on to my phone.
I have already rooted it and installed a insecure kernel using Odin and the Samsung Quick Root tool (found here: http://forum.xda-developers.com/showthread.php?t=1125414). :victory:
I am still running the insecure kernel that I flashed with Odin, and did not install CWM as I do not know what to do.
ROM Manager is installed on the phone but I don't think CWM is actually installed.
Currently, I want to install the F1 Galaxy Nexus ICS ROM. (http://forum.xda-developers.com/showthread.php?t=1601518)
All I want to know is do I need to install CWM, and how to install and flash the ROM to my phone.
The exact model of my phone is i1900-XWLPI.
Thanks.
Hi.
Yes you need cwm.
How to install Rom always be a guide in thread...
Send form Galaxy S2. Using XDA Premium
I was following a guide on it.
Now I am worried
I think it is bricked as it is stuck on the yellow triangle screen.
I don't have a jig and I NEED IT WORKING.:crying:
Ok I managed to get it to go in to d/l mode and flashed kernel back to the one I had earlier.
I think I'll just leave it for today and try another time.
Too much happened today and I don't want to risk a permanent brick.

[Q] Android System Recovery 3e

Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
jpp2109 said:
Hi All, I rooted my Verizon GS4 with this method "[GUIDE] Root for Verizon Galaxy S4 ***VRUAMDK Build Only!***" back before the first update so I have Root with Baseband I545VRUAMDK, Build JDQ39.I545VRUAMDKand Kernal 3.4.0-562219. I haven't tried to install any ROMs since then but started to get the itch so I started refreshing myself on the process and found that when I try to reboot into CWM Recovery it boots to Android System Recovery 3e. I'm looking for guidance on how to get CWM working properly. ROM Manager says I am using CWM 6.0.4.7. Any help will be appreciated.
Thanks
Click to expand...
Click to collapse
From what I've read about that issue is people have had to Odin back to stock then start over. Now maybe you could try installing another recovery like Philz maybe using Odin or try Goo for TWRP before you Odin back to mdk and go through all that.
Sent from my SCH-I545 using Tapatalk
I had a similar thing a few years ago, with what I know now I think the recovery is temporarily flashed with CWM to gain root and stock recovery is replaced after, I'd look for an actual CWM recovery to flash in.
Same applied to me using a ROM Manager, said it was v.xxx made a backup, flashed a ROM, turns out was left without a backup..... noob-old days
Bashing away at my HTC Desire C
Thank you for the solid replies, I'm interested in getting experience with the other recovery methods anyway so I'll try those and worse case I start from scratch.
I have pretty much this same issue. I was happily running 6.0.44 CWM, installed via CWM.
Then I happened to check and see there's an update to 6.0.47. I installed via ROM manager which reported success. Except that it isnt. I basically have 2 recoveries as far as ROM manager is concerned. It thinks I'm on 6.0.47, but 6.0.44 is what boots. I'm betting it's the same issue you have.
I re-flashed Twrp trying to fix it. Now twrp is what recovery always boots; but Rom manager still thinks 6.0.47 is installed. Rom manager shows BOTH recoveries in the "Recovery already installed" menu.
Seems the issue here is the 6.0.47 when flashed via Rom manager. It bugs the crap out of me that it seems like I have 2 recoveries installed somehow. Not sure how that's possible, but everything seems like it's functioning for me.
Compare the sizes of the recoveries, one thing I've come across is when you flash a new .img in because of the NAND chip process for writing/erasing I have had 'remnants' from previous files.
In one respect it is unlikely but I wouldn't rule it out until you check yourself. It could just be left on the list as a marker that it has previously been installed.
Personally I don't use ROM Managers now, it's into TWRP Recovery and backup from there
Bashing away at my HTC Desire C
Look Like I'll Have to Start From Scratch
I'm just getting back to this because work was crazy. No Matter what recovery I try always comes up with Android System Recovery 3e. Stock MDK and re-root it is.
Maybe try using GooManager to install TWRP after you've gone back to stock.

[Q] Installed CWM Recovery on Galaxy Note N7000 and got in a bootloop straight away

Hello dear community
This is my very first thread I am making on this website, so please pardon me if I am on the wrong page of this website.
Anyways, I'm more or less desperate. I saw a youtube tutorial on how to install Android 4.4 Kit Kat on a Samsung Galaxy Note N7000 and I heard I'd need root AND a custom recovery.
Because I'm a total newbie to this kind of stuff, I tried the very first thing I saw that had something to do with custom recovery, because I already had my phone rooted. So, I looked up a tutorial on youtube on how to install CWM custom recovery and ended up with installing it successfully, but now my phone is stuck in a bootloop. As I already mentioned, I am a newbie and therefore I am very desperate at the moment, you know.
The only thing I can do is go to Recovery Mode, but if I try to turn the phone on it gets stuck in a bootloop (It actually doesn't loop at all, it just freezes at the moment when the Samsung Galaxy Note logo appears and doesnt do anything after that.).
I think my problem is that I actually threw a new Kernel on my phone, because the video title says "How to install Kernel with CWM [...]"
I would be very very very very very grateful if anyone was kind enough to help me get out of this!
I really need help!
Thanks!
PS.
If this helps you help me:
This happened when I had Android 4.1.2 installed.
There's going to be 2 ways to get out of this:
1) Reinstall the stock firmware via Odin.
2) Install a custom rom via recovery.
Personally, I'd go with number 2 because a) you wanted to update anyway and b) if you have the right recovery and rom, it'll be easier as you can just put the files you need on an external SD card and install via the custom recovery. Now, not all recoveries are able to flash any file. Many times you need specific ones to install the newer android versions. So, if you are wanting to install something 4.4 based, then using a recovery that was made, say, last year, probably will not work well if at all.
Another thing to try first, is to wipe the cache and dalvik cache in recovery since you said you tried to install a kernel. It is always recommended to wipe these when installing (assuming you did pick a compatible kernel with what you were trying to install).

Categories

Resources