Ok so this may have been posted before but I've been searching and can't find anything.
So I got my note 2 when they released and I did the first "root" method available which I think was odin. Not really root with a custom recovery however I don't think. See the following screenshot to see what I'm currently running. Its been fine until now so I never re flashed anything or install twrp or anything.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Lately its been running slow so I want to fully root and install something along the lines of the latest Clean Rom. I had cleanrom on my Rezound and I love his roms.
Only reason I'm making this thread is because I'm not sure where to start because I don't think I'm stock yet I'm not "really" rooted.
Dont want to mess up my device.
Thanks!!
ufvj217 said:
Ok so this may have been posted before but I've been searching and can't find anything.
So I got my note 2 when they released and I did the first "root" method available which I think was odin. Not really root with a custom recovery however I don't think. See the following screenshot to see what I'm currently running. Its been fine until now so I never re flashed anything or install twrp or anything.
Lately its been running slow so I want to fully root and install something along the lines of the latest Clean Rom. I had cleanrom on my Rezound and I love his roms.
Only reason I'm making this thread is because I'm not sure where to start because I don't think I'm stock yet I'm not "really" rooted.
Dont want to mess up my device.
Thanks!!
Click to expand...
Click to collapse
Sounds like you are rooted, but your bootloader is still locked. In order to flash ROMs on Verizon you will need to unlock the bootloader (unless you did that via Odin the first time around). From those screenshots you won't be able to tell if you have unlocked the bootloader...as far as I know the only want to check is to boot into recovery. If you see TWRP or CWM you are set...if you get the stock recovery you need to follow Adam Outler's original unlock method as you are on baseband VRALJB. To access recovery power off the device and then press volume up + power button + home button simultaneously. Whatever boots up will tell you what you need to know.
stary by reading the stickies.
Yea I believe I'm still on the stock recovery.
Related
Hello,
I just flashed my wifi gtab 10.1 with the stock touchwiz ux rom via odin from the development thread.
Now, whenever i start the download mode on my tab, following is coming up:
http://samsunggalaxysforums.com/attachment.php?attachmentid=733&d=1304696743
The shown one here is from a S2, but I get exactly the same screen with my gtab.
Before I flashed it via odin this screen wasn't there and I got directly into download mode.
Even restoring the normal stock rom or installing cwm didn't remove it.
Am I the only one with this warning screen and is it possible to remove it again?
Thanks in advance.
So nobody knows something about this? That's sad. =/
Edit: Sorry for double posting, wanted to edit.
its nothing much
just means you've flashed a ROM
So it's absolutely normal that this warning screen will pop up everytime I start the download mode from now, because I flashed a ROM one time?
Also, there is no way to remove it?
Thanks so far.
on the Galaxy S II you can either get a usb jig or do that flash/reflash trick but on the Tab i dont think there's anything yet. but hey thats no big deal !
....DELETE
No, I think it came with the latest official ROM. I just got my tab the other day, brand new. The firmware on it is XXKG8. I haven't added anything, and as I said, it's new.
I get that message before download mode. I have been actually hesitating to root it because of this, thinking that they have added some sort of counter like on the SGS2.
So this is not the result of adding a rom, it appears on brand new retail tabs as well, it seems.
So from what I gather, nothing happens when you press the yes button to go into download mode after you see that message?
Draygon said:
I just flashed my wifi gtab 10.1 with the stock touchwiz ux rom via odin from the development thread.
Now, whenever i start the download mode on my tab, following is coming up:
http://samsunggalaxysforums.com/attachment.php?attachmentid=733&d=1304696743
Click to expand...
Click to collapse
That is normal, no need to worry about it. I got the same warning once I performed the 11MB update on my UEKG4 build. I have a feeling that warning was "borrowed" from vanilla 3.2, anyone with a Xoom tablet on 3.2 please let us know. Did you had an unlocked bootloader on your tablet (lockpad)?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Because if you did, the update locked your bootloader unfortunately. Still, there is no biggie on that also... Personally, I don't care if it locks the bootloader, as long I can flash the tablet with CWM. That means I can flash a custom ROM, kernel and also root. It makes no difference to have a locked or unlocked bootloader, unless you want to flash something that needs a different bootloader (i.e. Tabuntu).
So i just tried to root my SGS2 i9100 with SOC but it seems it's stuck on Step #5.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Can anyone help me proceed?
PS: If i force close the program since it froze will it affect my phone or something?
I think you can safely force close it. Which firmware are you on? Why are you rooting your phone? Are you planning to install a custom ROM?
immortalneo said:
I think you can safely force close it. Which firmware are you on? Why are you rooting your phone? Are you planning to install a custom ROM?
Click to expand...
Click to collapse
I'm using Stock 4.1.2 (as always) and i have been looking around those useful apps which pretty much always happends to require root, so i told myself "why not, it's one click away", right?
I suggest you try this method then:
http://forum.xda-developers.com/showthread.php?t=2116549
immortalneo said:
I suggest you try this method then:
http://forum.xda-developers.com/showthread.php?t=2116549
Click to expand...
Click to collapse
Thanks for your help but i'm not that power user and i don't want to deal with flashing , kernels , triangles etc.
This "one click" method seemed okay with me and if i can't get it to work - i'll just remain unrooted and that's it.
I just want to be sure that freezing on step 5 didn't affect my phone at all!?
psydex said:
Thanks for your help but i'm not that power user and i don't want to deal with flashing , kernels , triangles etc.
This "one click" method seemed okay with me and if i can't get it to work - i'll just remain unrooted and that's it.
I just want to be sure that freezing on step 5 didn't affect my phone at all!?
Click to expand...
Click to collapse
It shouldn't affect your phone, but I can't guarantee anything.
To be honest, the method I suggested is a lot more easier then the SOC method you tried. You never know how sweet candy is until you try it out yourself.
I seem to recall something along the lines of 'SuperOneClick won't work with anything > 2.3.6'. Put it this way, the thread hasn't been updated since just after ICS came on the scene. Take the advice you've been given & root your phone in less than 5 minutes with another method.
Edit - Using a method like that on firmware it's not meant to be used on given the level it works at (ADB) could bork your phone much more easily than other root methods which actually work.
Trying to delete thread. Posted in wrong forum. Moved here: http://forum.xda-developers.com/galaxy-s3-att/help/gs3-impregnable-wall-rooting-flashing-t2811864/post54055338
sirlitch said:
Hi guys. First post to the forum, been lurking for years, just registered.
I recently updated my phone with the update that Samsung kept bothering me about every 2 hours or so. And It has messed my phone up, it's slow, it drags. It doesn't even show the clock on my lock screen without thinking about it for about 10 seconds. Train wreck.
I've rooted, installed custom recovery, and loaded custom roms on my Galaxy S i9000 and on my grouper Nexus 7. I kinda get how all this works, I'm not a total newb, but with this phone I am at a dead end and i've tried everything I know, and a bunch more tricks I learned here and nothing is working.
My Phone: Samsung Galaxy S3: Canadian (Bell) version SGH-I747M, supposedly the same as the S3 AT&T,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LINK IF IMAGE WONT IMBED: https://www.dropbox.com/s/dmgw0wj59ry70f6/Screenshot_2014-07-10-10-22-46.png
I had to use zadig to replace my drivers for Heimdall
Heimdall will sucessfully flash clockwork recovery, but it refuses to install my CM rom. I haven't tried any other roms, but from what I've read in the forum here, it doesn't seem to matter what rom you use, it just wont do it.
I get Assert, bootloader errors when trying to install from zip in Clockwork Recovery. tried the fix here: http://forum.xda-developers.com/showthread.php?p=41503727
and it does not work. Odin just says "FAILED" right away.
I thought maybe if I just rooted the phone first, I could at least flash a custom recovery and not have it over written everytime I boot.
I tried CF-AutoRoot, Odin says success, but nothing changes on my phone.
I tried OneClickRoot which worked wonders on my GS i9000 back in the day. No success.
I have tried CM Installer to do it automated, It says success, but no change.
People have reported that Knox may be the problem, but as far as I can tell I don't have it on my phone.
I've been working on this for a day and a half and all I've managed to do is factory reset my phone about 12 times. I need help.. I don't know what to do. Has anybody managed to root their phone or install a custom recovery or rom with a GS3 running 4.4?
Click to expand...
Click to collapse
Wrong forum myfriend post your question here >> http://forum.xda-developers.com/galaxy-s3-att <<
Hello there, I won't lie, I ask for help, you answer me.
I don't understand enought your method, because it's not well described.
But.. Therefore...
I'm able to root my device.
I'm able to backup my ta partition or my drm keys.
I'm able to unlock my bootloader.
I'm able to restore my bootloader to lock it back.
i'm able to unbrick my phone when it couldn't boot via flashtool.
Click to expand...
Click to collapse
But I'm unable to install a custom recovery and or even launch the stock on it there was one.
I tried this method: http://forum.xda-developers.com/showthread.php?t=2647492 (normal boot and no pink led).
I tried this method: http://forum.xda-developers.com/showthread.php?t=2799388 via flashtool and my phone couldn't boot, even to the SONY logo, but it were vibrating when pushing on the power button.
Anyway, I flashed via flashtool the 14.4.A.0.108 back, now I'm still rooted and the bootloader is still unlocked.
Click to expand...
Click to collapse
What can I do to install a custom recovery via the 14.4.A.0.108 ?
Or this operation is impossible and I have to downgrade ?
(I read about downgrade and I'm affraid to lose my IMEI)
Click to expand...
Click to collapse
Thank you for your glorious complete explanations.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm pretty sure the problem here is that there is a stock firmware development aka the custom ROMs can't just start "taking over from where the devs left off" like it happened with Samsung Devices that get stuck at v4.1.2 unless someone else does something about it.
I guess most things here just are not stable. I hope the stock works out for you. Did you get the rooting done? I found a video tutorial for that here http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
Zhuinden said:
I'm pretty sure the problem here is that there is a stock firmware development aka the custom ROMs can't just start "taking over from where the devs left off" like it happened with Samsung Devices that get stuck at v4.1.2 unless someone else does something about it.
I guess most things here just are not stable. I hope the stock works out for you. Did you get the rooting done? I found a video tutorial for that here http://forum.xda-developers.com/xpe...de-root-android-4-4-4-ver-14-4-0-108-t2801587
Click to expand...
Click to collapse
Hello, of course I have done rooting, now I'm back in full stock, nk rooting, just pure sony beauty. And everything works better without root, or it doesn't matter, but the navigation and the use of the device is much smoother without lags
It's finally time for me to do what every XDA user done already - root my phone and use another ROM. I haven't ever before done this that's why I'm very excited.
I'm trying to follow this noob-friendly guide http://forum.xda-developers.com/showthread.php?t=2213910 . I read it like ten times already, but I still have some questions.
1. I want to have a CM rom. Should I get Lloir's CM 12.1 or the official CM 11? The thing is, I won't be able to get another rom for almost a year and I want a quite stable rom.
2. I guess I should install the latest TWRP 2.8 recovery from this forums, am I right? But then, why on the official CM download page there is a separate "Cyanogen Recovery" file?
3. According to the tutorial, I should install SuperSu, is this the right version?
https://download.chainfire.eu/696/SuperSU/
4. The thing I'm worried about mostly - my digitizer is damaged and I sometimes get "phantom touches", I can't tap anything on screen, the only solution is screen off & on. What if phantom touches appear when I'm in recovery? From what I read most things are controlled by physical buttons (which work), but not all, some requires to swipe. What then? Can I turn the screen off or abort the process and start again?
Thanks in advance for every reply.
If you need a stable rom you should stay on stock.
1. I use CM12.1 and used CM11 before. I prefer 12.1. They all have some more or less annoying bugs -> read the threads and make your own decision
2. Use the TWRP version which is linked in the rom thread. Cyanogen recovery has less functions and is not public released for x+ afaik
3. CyanogenMod is shipped with it's own su-management app. So no need to install SuperSU
4. you can turn screen on and off in recovery
Thank you very much!
An hour ago I installed CM12.1, I may say successfully, because it booted and now Play Store is downloading GBs of apps., so I can't in fact do anything .
Maybe just one lat thing. If I'd like to install a CM12.1 update in the future, do I have to wipe everything? Or just flash the boot.img and rom and that's it?
CM says you don't need to wipe, but Lloir sometimes wants us to wipe x)
In CM12 root must be enabled in developer options btw.
crusader727 said:
but Lloir sometimes wants us to wipe x)
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}