Warning: I'm a total n00b. I'm afraid I permanently wrecked my phone and I want to know if I can get it back to normal again.
Here is a step by step of what I think happened:
I tried flashing CyanogenMod 10.1 by using the ClockWork ROM Manager. I went to the Download ROM section of ROM Manager and found Cyanogen 10.1. It gave me the prompt "Backup existing ROM" and "Wipe Data and Cache," and I selected both. My phone started downloading the ROM. After it finished downloading the recovery menu popped up and I pressed Reboot System Now which I think was my first mistake.
It rebooted into Samsung's TouchWiz, not CyanogenMod, and asked me to sign into my Google account, which I did. I knew I had made a mistake so I went back to the ClockWork Recovery menu to start over. I made a backup of my ROM (which at this point was not even useful due to my first attempt), wiped the data/Factory Reset, wiped the cache, and wiped the Dalvik Cache. Then I tried to install the CyanogenMod ROM by going to "choose zip from sd card," however I couldn't find any ROM saved! I then tried to restore from a safe point, but no files could be found to restore from. At this point I panicked and hit "reboot system now" not knowing what it would do.
It rebooted into TouchWiz again, except this time with zero of my contacts, apps, anything. And it kept freezing every couple of seconds. I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes.
At this point I just want to get out of the jam I created and hopefully get some files back, especially the photos I have saved. Can anyone help me?
ps sorry for the long post
Well the good news is that as long as your phone is booting all the way into ANY OS, you're doing okay. Here at XDA, the ROM MANAGER method is frowned upon. From this point, your best (safest) bet is a clean slate, and I think that the best way for you to get there is to ODIN to stock touchwiz jellybean 4.1.2 (UCMD8) -then start the root - ROM process over again.
Odin 1.85 or 3.07 will both work
the UCMD8 firmware can be found in creepyncrawly's download repository
---------- Post added at 07:35 AM ---------- Previous post was at 07:23 AM ----------
gschmutz said:
...I tried booting into the stock recovery image but instead of the menu it asked me if I was sure I wanted to download a custom OS. First I said no and it just froze again. Then I said yes and it started downloading something. My phone currently has the green android in the middle, and up top it says Odin Mode/Custom Binary Download: No/Current Binary: Samsung Official. It hasn't changed in about 20 minutes...
Click to expand...
Click to collapse
What you describe here indicates that you booted into download mode, not recovery. Although it seems as though the phone is actively downloading something, it's just entered a ready-to-receive mode until you actively tell ODIN to send data (from a PC).
the keypress to get into download mode or recovery:
download mode: usb cable PLUGGED IN; vol- & vol+ & power --> until the prompt appears, then release and follow the instructions on screen
recovery: usb cable UNPLUGGED; vol- & vol+ & power --> until bootlogo appears, then release, and the phone should continue to boot into recovery.
---------- Post added at 07:43 AM ---------- Previous post was at 07:35 AM ----------
Once you're comfotably back to stock, this is the easiest way to get from stock to custom recovery on the i777:
Framaroot <-- tool to establish root-access to the device
Mobile Odin Lite <-- tool that uses root-access to install...
Custom Kernel <-- a custom kernel (there are many available) installed primarily to provide cwm recovery, but are also commonly used to:
-install a different ROM
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different kernel
-flash cleanup scripts
-and many many other things
The ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.
This guide will walk you through the steps, but read through the thread carefully to be sure that you understand everything before leaping.
-happy flashing
Great thank you so much! I will try to flash Jelly Bean when I get home from work. You lifted a weight from my chest.
Here's another update before I go any further. Late last night my phone stopped its bootloader cycle and seemed to be stably running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
gschmutz said:
...running TouchWiz on 4.1.2, and it is still rooted. It has been running stable all day. Do you think I still need to flash stock TouchWiz using ODIN before trying anything with my phone?
Click to expand...
Click to collapse
probably not, I'm glad to hear that things have stabilised.
From here, my strongest recommendation is that whenever you flash firmware, do some house-cleaning:
-either run a rom-wipe script before-hand
OR (at least)
-factory reset
-format /system
Related
Since i'm restricted to post in the development section i will post my thread here.
( ROM Link: http://forum.xda-developers.com/showthread.php?t=1324408 )
So i followed the instructions,
First i installed the samsung stock rom
Then i installed the clockworkmod via Odin,
I placed the mod (Full_Package.zip) on my SDCard.
Then i boot into recovery, do a wipe, and then install zip from SDCard (Since i can't find any "flash" option)
Then i reboot my phone. Everything works. i get the "touch the droid to continue" option, After i completed the installation i get the standart Galaxy S 2 look, with no cyanogen option or anything.
What step did i take wrong?
Thanks in advance!
Regards.
post the link to the rom so we can take a look at it and tell you what is wrong.
Added in my 1st post.
you missed the last step.
-After first boot, the phone rimaning on the first screen, don't worry, remove the battery, put the battery, go to recovery and reflash the rom!! happen only in the first flash...
-This is the only procedure to flash correctly CyanogenMod and rom based on CyanogenMod
Click to expand...
Click to collapse
it will then install the missing apps.
try reflashing the rom again as instructed.
I keep reflashing, and still nothing happens..
I retook every step again. Placed clockwork mod on the phone using Odin,
Went in to recovery mode, Installed Full_Package.zip.
Booted up my phone.
Nothing, just Stock rom,
And when i look in my system info it does show me that it's the Cyanogen Kernel.
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
* RECOVERY: Install Rom: Download
* RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
* RECOVERY: Wipe Cache Partition
* RECOVERY: Wipe Dalvik Cache
* Reboot and enjoy
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good:
I have a Sprint Galaxy Note 3.
As of yesterday it was functioning perfectly with a rooted stock Android 5.0 I tried to put a custom rom on it so I could use xposed and it has been borked ever since, I will list the steps I took and everything I've tried and their results below:
(I did full wipes in between each different flash)
1. Flashed TWRP with Odin (worked)
2. Flashed CyanogenMod with TWRP (worked)
3. Booted into CM to discover I could not get any data connection (could still make calls)
3. Booted to TWRP and flashed DarkLord rom (said there were errors [writing symlinks], caused boot loop)
4. Tried step 3 with Norma rom, CivZ rom, and a Stock Rooted rom (all same results of boot loop)
5. Booted to download mode and tried to flash samsung stock kitkat (just said failed)
6. Booted to download mode and tried to flash samsung stock lolipop (failed)
7. Booted back to TWRP and flashed CM again (this time not only no data, but no calls either)
Seems like maybe one of the issues may be the abundance of region codes and whatnot for all of these roms (including samsung official) and none of them seem to be for USA.
Does anyone have any suggestions or help to offer that I haven't already tried? I don't care what the rom is at this point, I just need a working phone that makes calls and has data as I'm out of town away from family and need to be in touch.
That said, obviously my preference would be to have a rooted KitKat rom so I can install xposed, or a rooted lolipop that isn't a samsung ART (for the same reason), but I'll genuinely be happy with anything that works.
I could be wrong, but is it maybe best to stick with CM simply because it's the only thing that will boot right now? If so how would I go about solving the non existence of a network connection.
I am also using Ting as a provider and they hop off Sprint networks. I had full bars of signal in this location the entire time when I was stock. Thanks in advance!
HunterNIU said:
I have a Sprint Galaxy Note 3.
As of yesterday it was functioning perfectly with a rooted stock Android 5.0 I tried to put a custom rom on it so I could use xposed and it has been borked ever since, I will list the steps I took and everything I've tried and their results below:
(I did full wipes in between each different flash)
1. Flashed TWRP with Odin (worked)
2. Flashed CyanogenMod with TWRP (worked)
3. Booted into CM to discover I could not get any data connection (could still make calls)
3. Booted to TWRP and flashed DarkLord rom (said there were errors, caused boot loop)
4. Tried step 3 with Norma rom, CivZ rom, and a Stock Rooted rom (all same results of boot loop)
5. Booted to download mode and tried to flash samsung stock kitkat (just said failed)
6. Booted to download mode and tried to flash samsung stock lolipop (failed)
7. Booted back to TWRP and flashed CM again (this time not only no data, but no calls either)
Seems like maybe one of the issues may be the abundance of region codes and whatnot for all of these roms (including samsung official) and none of them seem to be for USA.
Does anyone have any suggestions or help to offer that I haven't already tried? I don't care what the rom is at this point, I just need a working phone that makes calls and has data as I'm out of town away from family and need to be in touch.
That said, obviously my preference would be to have a rooted KitKat rom so I can install xposed, or a rooted lolipop that isn't a samsung ART (for the same reason), but I'll genuinely be happy with anything that works.
I could be wrong, but is it maybe best to stick with CM simply because it's the only thing that will boot right now? If so how would I go about solving the non existence of a network connection.
I am also using Ting as a provider and they hop off Sprint networks. I had full bars of signal in this location the entire time when I was stock. Thanks in advance!
Click to expand...
Click to collapse
1. Power off your phone completely
2. Boot into download mode (power + volume down button - then press volume up button to get into download)
3. Use Odin to flash this, which is the tar for OC5 - http://forum.xda-developers.com/note-3-sprint/development/romodin-t3095540
4. Reboot into STOCK recovery and factory default reset. If you skip this step, you will have issues
5. Once booted into OS, power off again and re-do step # 2 to get into download mode
6. Use Odin to flash TWRP
7. Once complete, immediately reboot into TWRP, or you will be dumped into stock recovery next time you try to get into recovery. I've done it this way since MJ4 and never had an issue.
8. Wipe everything including internal storage - NOT your external SD
9. Install ROM of your choice; I would recommend this one which is deodex and will allow you to install Xposed - http://forum.xda-developers.com/note-3-sprint/development/rom-t3132662
10. Profit
Good luck!
rpenrod23 said:
1. Power off your phone completely
2. Boot into download mode (power + volume down button - then press volume up button to get into download)
3. Use Odin to flash this, which is the tar for OC5 - http://forum.xda-developers.com/note-3-sprint/development/romodin-t3095540
4. Reboot into STOCK recovery and factory default reset. If you skip this step, you will have issues
5. Once booted into OS, power off again and re-do step # 2 to get into download mode
6. Use Odin to flash TWRP
7. Once complete, immediately reboot into TWRP, or you will be dumped into stock recovery next time you try to get into recovery. I've done it this way since MJ4 and never had an issue.
8. Wipe everything including internal storage - NOT your external SD
9. Install ROM of your choice; I would recommend this one which is deodex and will allow you to install Xposed - http://forum.xda-developers.com/note-3-sprint/development/rom-t3132662
10. Profit
Good luck!
Click to expand...
Click to collapse
Thank you so much for such a quick response! I'm downloading the file now and will be trying this as soon as it's completed. Also the rom you recommended was one I tried that failed, but hopefully with your extra steps it will work because it looks exactly like what I'm looking for.
UPDATE:
That worked fantastic @rpenrod23 thank you so much! Where is your donate button?
Hello,
I come for you, because I am trying to install android 4.4 on my phone, because android 4.3 isn't compatible with pokemongo.
I have a galaxy s3 GT-I9300 from a few years, I've never rooted it and it runs on android 4.3.
I've been looking for guides that say that I need to install CWM recovery to then be able to install CyanogenMod.
So I've downloaded Odin, and CWM recovery, added the CWM recovery .tar in the AP box of Odin, put my phone on download mod, plugged it, and run Odin.
It appears that it works succesfully, but when I reboot my phone in recovery mode, I still have Android Recovery System <e3>, and I can't install zip from sdcards (if I understood correctly, <e3> doesn't support zip, whereas <e2> does, and CWM is supposed to put it to <e2>), so I can't install CyanogenMod.
Here is a screenshot of my Odin after running it: (I can't post the link since I'm a new user, so it's on imgur)
/87oPm2l
I can't think of any more information to provide for now.
Thanks for your help.
chocolote4444 said:
It could be permission issues. But try using a different cable.
Also, the recovery you are flashing has to support the model of the phone, otherwise, Odin will refuse to install it.
Click to expand...
Click to collapse
Thanks for the answer, I was not in root mode.
I fixed it and it now works, I have been able to install CyanogenMod from the zip in recovery.
Now I tried restarting my phone, and it's stuck in "Android is starting".
I have a little blue alien popping on my screen, then the screen turns off, then the screen turns on and says things like "starting applications, preparing settings, optimizing applications". But it seems to be doing it on repeat and it's been an hour. Is it normal that it takes so long? I haven't seen it mentionned anywhere from what I checked.