I have the latest version, not sure if its ED04 or EV04 i think its ED04
but i tried root with the same way how i root ED01 with CWM 2.5.1.x and ODin
if i reboots the phone it'll stuck on SAMSUNG's logo and wont go any further.
Any Suggestions?
my phone is Samsung Fascinate
wisleans said:
my phone is Samsung Fascinate
Click to expand...
Click to collapse
Well there is no EV04 to my knowledge so if you have a version with this naming sequence that could be your problem.
Now From what I could make out you attempted to root your phone but you didn't say how you did it. For one of us to understand what could be the problem we need more information other then "i tried root with the same way how i root ED01 with CWM 2.5.1.x and ODin."
The only way to "root" with odin or CWM is to flash/push a new ROM that is already rooted. Which if this is your method you may have improperly flashed a ROM which is causing you problem.
Again, I have never seen an Odin root method without using it to push a ROM to the device that is rooted nor have I seen a CWM that roots the phone. I may be wrong but I just have never seen it and I have flashed/rooted the hell out of my device.
wisleans said:
I have the latest version, not sure if its ED04 or EV04 i think its ED04
but i tried root with the same way how i root ED01 with CWM 2.5.1.x and ODin
if i reboots the phone it'll stuck on SAMSUNG's logo and wont go any further.
Any Suggestions?
Click to expand...
Click to collapse
You are gonna have to odin back and try again. rooting ED04 that way does just what you explained, it is rootable though Super One Click works just fine on that. my recovery guide has everything you need a how to for recovery, rooting, and any files you may need. Just go here, and with a little reading and time with odin you'll be good to go.
Related
Up until today, I've been rooted. Used the SuperOneClick program. It was a piece of cake.
Today, I decide to check for new software updates..Two new ones.
I updated them and now I'm running 2.2.2 and ed05. Well I'm assuming that's the problem.
Because I've been going through the process today of backing up my ROM and stuff, to flash MIUI for the first time. Well, nothing seemed to work.
I tried to backup my current ROM, but nothing happened. (Should've rebooted and come back on, like normal after 'backup current ROM' was selected and a name was entered for it; Didn't happen. )
So I figured that the new software updates unrooted my phone.
So I go back into SOC and root my phone again, but during the process, it tells me that I'm already rooted. Finishes the process and I reboot my phone, etc.
Well the Superuser app is in my list now, but none of the root-required apps are working. They all tell me that I'm not rooted. I even used Root Check to see the status. It tells me as well, that I'm not rooted.
I go back to the SOC program and UNroot. Well that was successful. I reboot, etc.
No Superuser app. So far so good. So I go BACK again and root, everything went well, except when it said an 'su' command was sent to my phone, I never got one, but I still got the Superuser app. And still, the apps tell me I'm not rooted.
Any kind of help is great. I really appreciate all the time, spent reading this.
Sorry if I went on and on, but it's bugging me now and I really need some answers to what the problem might be. Thanks, guys. ;(
superoneclick does not work on ed05
you need to odin cwm recovery
then reboot into recovery using three finger method
install root.zip file
then reboot
directions for rooting with odin is here:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
SOC does work with ED05.. I've used it several times, different phones.
Really? I thought quite a few folks were having trouble with soc after the ota ed05 update? If thats the case, then thanks for the clarification... although odin is still another option for the op since soc is not working.
droidstyle said:
superoneclick does not work on ed05
you need to odin cwm recovery
then reboot into recovery using three finger method
install root.zip file
then reboot
directions for rooting with odin is here:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
Click to expand...
Click to collapse
I read most of the first page on that thread, mostly just read the latest replies about that method. I'll read the full directional tutorial once I'm clarified of questions.
I think I read a couple of users saying this does root your phone, but it will wipe all data as well? I'm not quite sure. I want my phone rooted, no matter if I install MIUI or not. I don't want a factory reset though.
Thanks droidstyle, I'm back to being rooted!
Now onward to flashing MIUI! Wish me luck.
:^)
Hi guys. I have a Samsung Galaxy s3 GT-i9300 running 4.1.1 Baseband 19300XXDLIB.
I have been trying and trying and trying for the last few days to root my mobile. I take care following all of the steps and I have tried every type of root program and files I think are available but even though they download to the phone and reboot into their custom recovery, then install the files needed to root, none of them have worked!!
It's strange because the phone is just unrootable it seems. I have tried several versions of Odin. I've tried what should be 1 click rooters but nothing works! The most recent files I have used to download to my phone via Odin were CF-Auto-Root-m0-gti9300, CF-Root-SGS3-v6.4, SuperOneClickv2.2-ShortFuse, SuperOneClickv2.3.1-ShortFuse and SuperOneClickv2.3.3-ShortFuse all of which have been recommended to me and I have strictly followed YouTube videos and written guides. I don't think I am doing anything wrong yet I still have no root access. The last root I tried installed a CWM app (I know it stands for Clock Work Mod but not sure what I am supposed to do with it) but not SuperSU which is supposed to come with it.
Please can someone help? I'm tearing my hair out here!
I should probably point out I am not using the stock ROM as I did manage to brick my phone at one point and had to install another firmware, although I would like to go back to my original firmware yet I am not sure what it was...is it possible to figure out what the stock firmware should be? The phone is unbranded from the UK.
Many thanks
I should probably point out I am not using the stock ROM as I did manage to brick my phone at one point and had to install another firmware, although I would like to go back to my original firmware yet I am not sure what it was...is it possible to figure out what the stock firmware should be? The phone is unbranded from the UK.
No you can only guess .
TO ROOT .
Factory reset the phone and install CF root 6.4 via Odin .
But its really pointless rooting when you don't have a clue as to why or what .
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
May also be because your computer hasn't been installed with the samsung drivers yet? Kies i think it's called..
Have you tried downloading supersu from the play store? And be sure to not try superuser but supersu.
I had the same thing with cf-autoroot. supersu wasn't there and I didn't have root. Tried several times, never worked. After that I tried rooting with the old cf-root that also installs cwm recovery. Recovery was there but no supersu and the phone didn't get root. Tried that several times too but that didn't help either, although that is how I rooted my phone successfully right after I had bought it. Went back to cf-autoroot, same result, no root. But as soon as I downloaded the app supersu manually and updated the binarys as it tells you to at first start, I had root.
Zelmer said:
May also be because your computer hasn't been installed with the samsung drivers yet? Kies i think it's called..
Click to expand...
Click to collapse
Kies is not required (and its junkie bloatware that doesn't properly clean itself up on uninstall anyway)
Windows can pull the drivers from WU.
You Sir, are a legend! Thank you very much, you have sorted my problem I had SuperUser instead of SuperSU like you stated. Who would've thought it'd be so easy to fix?
shamez23 said:
Have you tried downloading supersu from the play store? And be sure to not try superuser but supersu.
I had the same thing with cf-autoroot. supersu wasn't there and I didn't have root. Tried several times, never worked. After that I tried rooting with the old cf-root that also installs cwm recovery. Recovery was there but no supersu and the phone didn't get root. Tried that several times too but that didn't help either, although that is how I rooted my phone successfully right after I had bought it. Went back to cf-autoroot, same result, no root. But as soon as I downloaded the app supersu manually and updated the binarys as it tells you to at first start, I had root.
Click to expand...
Click to collapse
You should probably not just imagine that just because someone has a problem that they don't have a clue what they are doing. I have done this numerous amounts of times with several phones, my Samsung was just slightly more difficult since I had made an easy mistake by not taking note of my original firmware and by not realizing that I needed SuperSU and not SuperUser (which I'm sure is a common and easy mistake).
Try next time not to put a fellow site member down.
JJEgan said:
I should probably point out I am not using the stock ROM as I did manage to brick my phone at one point and had to install another firmware, although I would like to go back to my original firmware yet I am not sure what it was...is it possible to figure out what the stock firmware should be? The phone is unbranded from the UK.
No you can only guess .
TO ROOT .
Factory reset the phone and install CF root 6.4 via Odin .
But its really pointless rooting when you don't have a clue as to why or what .
BASICS .
http://forum.xda-developers.com/showthread.php?t=1927113
jje
Click to expand...
Click to collapse
I did actually install Kies but thanks for the help anyway
Zelmer said:
May also be because your computer hasn't been installed with the samsung drivers yet? Kies i think it's called..
Click to expand...
Click to collapse
If I flashed a ROM that uses ME7 and I want to ODIN back to stock, is it possible?
Or will I brick my phone? Reason I want to go back to stock is no matter what ROM I flash; every time I reboot my phone gets stuck on the samsung logo.
Answered my own question:
It does not matter...
If you are not on the ME7 OTA update then you should be fine odin'ing back to mdk
If you are on the OTA, then you are stuck with me7
Exodus885 said:
If I flashed a ROM that uses ME7 and I want to ODIN back to stock, is it possible?
Or will I brick my phone? Reason I want to go back to stock is no matter what ROM I flash; every time I reboot my phone gets stuck on the samsung logo.
Answered my own question:
It does not matter...
Click to expand...
Click to collapse
The post above really answered your question. But just in case you need to be reassured:
On our device (at the moment), as long as you didn't accept the VRUAME7 OTA, then your okay.
I actually have a couple of questions for you (if you have the time).
Can you help me out by giving me a little more information about how your getting stuck at the boot logo?
I suppose you started out clean (with VRUAMDK) and then rooted your device and installed a custom recovery.
Did you root with SuperUser (new cwm opensource) or SuperSU?
Which recovery did you install and how did you install it (which method)?
Which VRAUME7 ROM did you flash that you think started your boot issues?
Did you install the VRUAME7 radio/modem as well?
If so, which method did you use for updating your radio/modem and which files were used in your method (and where were they from)?
Click to expand...
Click to collapse
-h311sdr0id
Sent from my SCH-I605 using Tapatalk 4
h311sdr0id said:
The post above really answered your question. But just in case you need to be reassured:
On our device (at the moment), as long as you didn't accept the VRUAME7 OTA, then your okay.
I actually have a couple of questions for you (if you have the time).
-h311sdr0id
Sent from my SCH-I605 using Tapatalk 4
Click to expand...
Click to collapse
Can you help me out by giving me a little more information about how your getting stuck at the boot logo?
Anytime I installed a ROM(any ROM), I would test to see if I still had this problem and I would reboot my phone. Upon rebooting my phone, it never got passed the samsung logo. ODIN-ing back to stock helped fix this problem and now it works. However now I have an issue where facebook and instagram does not show any photos.....any ideas?
I suppose you started out clean (with VRUAMDK) and then rooted your device and installed a custom recovery.
Correct, I ODIN-ed back to MDK.
Did you root with SuperUser (new cwm opensource) or SuperSU?
SuperSU (motochopper SU script)
Which recovery did you install and how did you install it (which method)?
TWRP 2.6 using Goo manager then reverted back to 2.5.0.2
Which VRAUME7 ROM did you flash that you think started your boot issues?
Honestly, hard to say could be the nightly of CM10.2 (8/21)
Did you install the VRUAME7 radio/modem as well?
No I did not, do I need to update the radio/modem???
If so, which method did you use for updating your radio/modem and which files were used in your method (and where were they from)?
See previous answer.
Hope this helps
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
sduffy89 said:
The first step for flashing Alliance was making sure i have the 4.3 firmware. Flashed via Odin.
I experfienced some trouble with a bootloop issue so i changed cables and then partitioned with the .pit file.
All's well now, it at least runs the stock firmware just fine. Now i'm strugglling with the most basic simple part IMO... how do i install the custom Rom without the recovery??
Click to expand...
Click to collapse
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
I chose to bump up my android version cuz i friend another SIM card. I tether for my Hulu, Netflix, Amazon Prime, and whatever else, thankfully my laptop can get weak unsecured internet signals, but i'm walking my Note around the apartment trying to get good 1x reception Problems may be overlapping but next step is something basic from the Play Store to verify root.
I read of some luck with root for 4.3, just not bootloader. Am i correct?
KuNiT said:
You are rooted still correct? Easiest way I guess is to just download Rom Manager or GooManager depending on using TWRP or CWM.
Click to expand...
Click to collapse
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
sduffy89 said:
Not rooted. it sounds like rooting is still an option, just not custom recovery?
Is using ODIN to flash stock rooted an option? No valuable files on phone currently.
(Fortunately I'm at work right now so I have time to make well informed decisions. Thanks for your help)
Click to expand...
Click to collapse
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
KuNiT said:
I believe if you took/flashed the OTA update, your kinda out of luck and stuck now. I'm not 100% certain of this though but I think it probably relocked the bootloader and the only thing to do is wait for someone to root/unlock 4.3.
Click to expand...
Click to collapse
Correct. If you took the OTA it relocked your bootloader and you are stuck. You can still root the official 4.3 but you are stuck waiting until someone unlocks the bootloader. This means no custom ROMs/Recovery.
Which 4.3 firmware did you flash? If its the OTA then yes you're outta luck.
If you did follow the Alliance's rom thread. There is a 4.3 MJ9 firmware you need to flash. It doesn't have the locked bootloader. You are then able to boot up in the basic recovery and then flash either TWRP or CWM recovery.
I was using Kingo Root to root my S3 i9300, until i realized it wasn't working because it kept looping and when i took my phone out it still kept looping with the rooting process(As if my device is still connected). It rebooted my phone once and the problem is it still keeps looping.
But the problem is, it change my Kernel Version to
3.0.31-2788594
[email protected] #1
Is that stock S3 kernel?
On S3 rooting changes kernel & recovery.
Get back a stable system by flashing latest firmware by Odin. If it boots normally, use cf-auto-root (by Odin, too).
rp158 said:
On S3 rooting changes kernel & recovery.
Get back a stable system by flashing latest firmware by Odin. If it boots normally, use cf-auto-root (by Odin, too).
Click to expand...
Click to collapse
Is there a tutorial on this?
I usually try not to use ODIN as i see a lot of people who have errors while rooting with that , but where can i get the firmware?
for i9300?
Eliminate007 said:
Is there a tutorial on this?
I usually try not to use ODIN as i see a lot of people who have errors while rooting with that , but where can i get the firmware?
for i9300?
Click to expand...
Click to collapse
Don't worry. Odin run perfectly if one READS the tutorials CAREFULLY, which is what most people don't seem to do... I never had any problem flashing all kinds of stuff with ODIN.