For those who haven't used ODIN, the process can seem a bit daunting. Follow these steps to make flashing files via ODIN painless...
Reasons To Use This Tutorial
- Return your device to OEM Stock for warranty return
- Flash latest OTA Leak or revert firmware (ie; MJE, NC2, etc)
- Completely wipe device prior to private sale
- Return device to stock
- You're a bored crack-flasher with nothing better to do
* * * What you do with your device is completely your choice and solely your responsibility! - If You READ These Instructions FIRST, THEN Follow Them, You Will Be Up And Running In No Time* * *
STEP ONE:
Verify USB DEBUGGING is CHECKED in system settings>developer option (click 'BASEBAND or BUILD Version' in 'About Phone' 7 times to UNHIDE Developer Option) also verify UNKNOWN SOURCES is CHECKED in system settings>security.
On PC, go to CONTROL PANEL > Install/Uninstall Programs > uninstall ALL Samsung drivers
Download & Install The Following To Your PC
Samsung USB drivers for Odin (click “see all downloads”)
ODIN (latest version)
click middle “download” button - credit to DutchDogg54 for file
MJE Tar File (flash ONLY tar files for YOUR device)
credit to Beanstown106 for file (confirm Developer Edition or Retail device)
Verizon LTE PIT file
credit to Beanstown106 for file (confirm device)
STEP TWO:
Flash File In ODIN
- Power down your device (remove sdcard - not required but recommended)
- Simultaneously press and hold VOL DOWN + HOME BUTTON + POWER BUTTON
- At *Warning* screen, press VOL UP
- Start ODIN on PC
- Connect your device to its USB cable and plug cable into PC
- WAIT for ODIN to populate the COM box (pic 1)
- Verify that "Auto Reboot" and "F. Reset Time" are CHECKED (under COM box in Option section - pic 1)
- Click "AP" button (PDA if older Odin) (pic 2)
- Browse PC and insert file to be flashed (MJE tar file)
- Click "PIT" button *USE ONLY IF YOU HAVE PARTITION ISSUES* (pic 3)
- Browse PC and insert file to be flashed (PIT file)
- WAIT for "START" button (pic 4) to be enabled (may take a minute)
- Click START button to begin file install
- Disconnect USB when download is finished (device might auto reboot)
Profit, BACON & Joy you are now on MJE and your device is STOCK.
PERFORM A FACTORY RESET WIPING ENTIRE PHONE
This should return your device to "out-of-the-box" newness (remove ext SDcard)
- Turn off device
- Simultaneously hold VOL UP, HOME, POWER
- Release POWER when you see the Note 3 logo
- Release VOL UP & HOME when you see the System Recovery screen
- VOL UP after warning
- Using VOL DOWN choose WIPE DATA / FACTORY RESET
- Select using POWER button
- Using VOL DOWN choose "Delete ALL User Data"
- Select with POWER button
- Highlight REBOOT SYSTEM
- Select REBOOT SYSTEM NOW using POWER button
-Your device is now OEM Stock and ready to ship for warranty purposes, OR you can start over with a totally OEM stock device HERE> How To ROOT 4.3 & NC4 OTA, Install Recovery & Roms - Verizon RETAIL Note 3
Click HERE to Root, install Safestrap, update Chainfire's SuperSU, flash custom Roms, and learn about Rom Slots!
***Please click THANKS and RATE this thread***
{
"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"
}
]
az_biker said:
For those who haven't used ODIN, the process can seem a bit daunting. Follow these steps to make flashing files via ODIN painless...
! ! ! I am in NO WAY responsible for what you do with your device. YOU assume ALL responsibility for ALL actions performed on your device ! ! !
STEP ONE:
On PC, go to CONTROL PANEL > Install/Uninstall Programs > uninstall ALL Samsung drivers
Download & Install The Following To Your PC
Samsung USB drivers for Odin (click “see all downloads”)
ODIN 3.09 (latest version)
click middle “download” button - credit to DutchDogg54 for file
MJE Tar File
credit to Beanstown106 for file
STEP TWO:
Flash File In ODIN
- Power down your device (remove sdcard - not required but recommended)
- Simultaneously press and hold VOL DOWN + HOME BUTTON + POWER BUTTON
- At *Warning* screen, press VOL UP
- Start ODIN on PC
- Connect your Phone to its USB cable and plug cable into PC
- WAIT for ODIN to populate the COM box (pic 1)
- Click "AP" button (pic 2)
- Browse PC and insert file to be flashed (MJE tar)
- WAIT for "START" button (pic3) to be enabled (may take a minute)
- Click START button to begin file install
STEP THREE:
Profit, BACON & Joy you are now on MJE and your device is STOCK.
Click HERE to Root, install Safestrap, update Chainfire's SuperSU, flash custom Roms, and learn about Rom Slots!
***Please click THANKS and RATE this thread***
Click to expand...
Click to collapse
Worked perfectly thanks!!!:good::good::good::good::good:
nice write up.
i love odin. i always odin back to stock and start over when a new rom build comes out.
js0uth said:
nice write up.
i love odin. i always odin back to stock and start over when a new rom build comes out.
Click to expand...
Click to collapse
I appreciate the compliment!
Do you do this because you are an odin freak OR to ensure that none of the baseline firmware, kernel, software, etc got borked during the previous rom and useage cycle? Curious minds and all
az_biker said:
I appreciate the compliment!
Do you do this because you are an odin freak OR to ensure that none of the baseline firmware, kernel, software, etc got borked during the previous rom and useage cycle? Curious minds and all
Click to expand...
Click to collapse
Both. lol. and a personal preference.
its just more reassuring when everything is fresh. less prone to mishaps. ive been doing it since the note 2. and to be honest i rarely run into and problems. just the usual rom bugs.
and its way easier when you have everything saved on the sd especially since i just picked up a 64gb over black friday. :good:
js0uth said:
Both. lol.
its just more reassuring when everything is fresh. less prone to mishaps. ive been doing it since the note 2. and to be honest i rarely run into and problems. just the usual rom bugs.
and its way easier when you have everything saved on the sd especially since i just picked up a 64gb over black friday. :good:
Click to expand...
Click to collapse
Since you ODIN all the time, any suggestions to improve this write up or anything I missed?
az_biker said:
Since you ODIN all the time, any suggestions to improve this write up or anything I missed?
Click to expand...
Click to collapse
um.... no i think its fine. looks good to me. its pretty straight forward. dont know how much more easier itll get. lol.
good job and thanks again.
Does this wipe the device like apps games music
Sent from my SM-N900V using xda app-developers app
htcdroidincredible23 said:
Does this wipe the device like apps games music
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
yes. EVERYTHING. back to factory.
Rooting
Hi to everyone…..I'm a long time iPhone user converted to the Samsung Galaxy Note 3 (Verizon) and loving it. I've been trying to read as much as I can before asking questions but I'm just not sure about some things and I want to be sure before I proceed. I've tried at several different links to download the root file needed for my phone but can't find it….can someone point me in the right direction. I also know I need Odin3…..is there a particular version I need for my specific phone. Any help is greatly appreciated!!
htcdroidincredible23 said:
Does this wipe the device like apps games music
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
Yep. Save your valuables to sdcard and remove sdcard before flashing in odin
Notorious 3
ncphotographer said:
Hi to everyone…..I'm a long time iPhone user converted to the Samsung Galaxy Note 3 (Verizon) and loving it. I've been trying to read as much as I can before asking questions but I'm just not sure about some things and I want to be sure before I proceed. I've tried at several different links to download the root file needed for my phone but can't find it….can someone point me in the right direction. I also know I need Odin3…..is there a particular version I need for my specific phone. Any help is greatly appreciated!!
Click to expand...
Click to collapse
Everything you need is in the link in my signature. Easy to follow instructions
Notorious 3
az_biker said:
Everything you need is in the link in my signature. Easy to follow instructions
Notorious 3
Click to expand...
Click to collapse
Please forgive me ignorance…..but how do I know if I need the MJE tare file? And I'm sure it's right in front of me but I don't see the root file. I've downloaded the Odin3…..but now I'm stuck.
PS-- I don't mind making a $20 donation to someone who can help me like I'm a 2 year old child!!
ncphotographer said:
Please forgive me ignorance…..but how do I know if I need the MJE tare file? And I'm sure it's right in front of me but I don't see the root file. I've downloaded the Odin3…..but now I'm stuck.
PS-- I don't mind making a $20 donation to someone who can help me like I'm a 2 year old child!!
Click to expand...
Click to collapse
If you haven't taken the recent Verizon OTA (MJE) you are still running MJ7 software. Quickest way to know is check Baseband Version in ABOUT PHONE.
The MJE tar file is about 1.2 gb, I just checked all the links and they are working. Let me know what step you're at in the process.
I'll gladly accept donations, but they certainly are NOT expected
az_biker said:
If you haven't taken the recent Verizon OTA (MJE) you are still running MJ7 software. Quickest way to know is check Baseband Version in ABOUT PHONE.
The MJE tar file is about 1.2 gb, I just checked all the links and they are working. Let me know what step you're at in the process.
Click to expand...
Click to collapse
It appears that I'm on MJ7. As for what step I'm on….hmmmm, I've taken my phone out of the box (haha) I'm not sure what the h*** I'm doing…..I downloaded the Odin3…..but there doesn't seem to be anything to extract……and I still don't see the root file I need to download. If you'll send me your paypal info I'd gladly donate if you can help an idiot!!
Can anyone please help……I can't seem to get the Odin 3 file…….I'm on a mac…….is that why I'm having all the problems?
Can someone tell me this......do I want to update to the latest software version? If I do update do I then use the MJE root file?
ncphotographer said:
It appears that I'm on MJ7. As for what step I'm on….hmmmm, I've taken my phone out of the box (haha) I'm not sure what the h*** I'm doing…..I downloaded the Odin3…..but there doesn't seem to be anything to extract……and I still don't see the root file I need to download. If you'll send me your paypal info I'd gladly donate if you can help an idiot!!
Click to expand...
Click to collapse
Follow the link in my sig for Note 3 Root. It has every step and all the links to all the needed files. Donate link is under my avatar
Notorious 3
az_biker said:
Follow the link in my sig for Note 3 Root. It has every step and all the links to all the needed files. Donate link is under my avatar
Notorious 3
Click to expand...
Click to collapse
I've followed your link and I see all the files and I've read everything on there but still don't understand.
First of all, awesome guide, great for newbies like myself...
I am already rooted (only - no safestrap) and wanted to know
1. If I do this, will it make any changes to the Knox counter and will it change my status from custom to official? (ie. completely stock, ready for warranty?)
2. I obviously will have to root again, correct (will root survive with SUPro)?
3. I want to keep MJ7, I am assuming I can use the same method with MJ7 TAR file
Thanks for your help
Related
This is how to root and install a custom ROM on the Samsung I5500 mobile phone. I believe this may work on other Samsung handsets like the I5503 and I5508 but the I5500 is the only handset I have unlocked with the following tutorial.
I have tested this method using a new G5 in December 2011 but please understand that neither I nor the publishing website will take any responsibility for damage that may occur to your phone if you choose to follow this procedure and something goes wrong.
Firstly I’d like to thank JC_Master and CLShortFuse from XDA Developers and psyke83 from the ever informative MADTEAM for their work to make this possible.
There are a few different ways of doing this and I think I have tried them all, some resulting in a dead phone, some that just don’t work and some that are badly explained. This method has been tried and tested by myself and I will do my best to tutor it as simply as I can so that even a novice computer user may successfully flash / de-brand their phone from the putrid Samsung software!
OK, you ready?
Step 1
1.1 We need to install a boot-loader as the Samsung one is very limited and just plain awful! That said, it wasn’t intended to be used for anything other than the Samsung software so it’s not awful from their point of view but it’s pretty unfriendly to us.
1.2 If you know what a boot-loader is then skip to 1.3. A boot-loader is like a computers BIOS menu. If you have ever noticed when you turn on your computer there is some written text displayed (usually ‘Press F2 or DEL to enter Setup’) before it starts to boot Windows or whatever operating system it uses. If you push F2 or DEL when your computer tells you that you can you will go into a control interface that has options that you can set to tell your computer what to do when it is turned on and how to do it. Most computers are set to boot from the hard-disk first which is why yours starts to load your operating system. Many mobile phones work in the same way and the boot-loader (or BIOS) that we need to install will give us options to install our new ROM, to backup our phone data, to root it (gain entry to the system files – like being able to enter your ‘C:’ hard disk in Windows) and much more that the Samsung boot-loader will not.
1.3 Fortunately for us there is a clever bunch of people over at clockworkmod.com that have released a nice boot-loader for us that is just the job. They make these modded software files for us for free so please do donate something to them if you use their software so they can continue their work. Create a new folder called Samsung in your computers (C hard disk drive by left clicking Start Menu, Computer (or My Computer), double left click (C, right click (not on a file or icon) select New, Folder, type Samsung and the double click the folder to open it. Now resize the folder so it is not using the whole screen or minimize it but don’t close it. If you do close it, you know where it is! ‘C:\Samsung’
1.4 Download ClockworkMod-Galaxy5-v0.5 (Click the link) and SAVE it to your ‘C: \Samsung’ folder. For non I5500 mobile phones find your boot-loader here
1.5 Now let’s get the nice new Android ROM and its latest hotfix too. Remember to donate here as these boys have got to eat too! Download update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip and v1.7.2-hotfix1.zip SAVE to your ‘C: \Samsung’ folder.
1.6 Once this is all done we can install an app from the ClockworkMod team called ‘ROM Manager’ which will allow us to recover, backup and restore our phone. Download it now to the same folder and we’ll do that last ROM Manager APK
1.7 Lets also get the latest Google applications pack to install later too gapps-gb-20110828-signed.zip
1.8 **Ignore this step** In order to write any new information to the phones system files we need to get permission to do so and Samsung don’t give you this permission, this is known as ROOT access. There are many installable applications for the G5 that claim to root your phone but the only one I have found that works is Super One Click. This is a Windows installed based program (.exe) and not an APK (.apk – Android phone installed application). Download it here SuperOneClick usual folder!
1.9 Next we need to download and install the Samsung USB drivers. If you have Samsung Kies running then stop or disable it. If you don’t know what I mean then don’t worry about it! Download SamsungUSB to anywhere on your PC and double click it to install it.
1.10 We now need ODIN 4.28 which is the Samsung software that runs on Windows that will allow us to flash our new boot-loader and ROM over the USB cable that came with the phone. We also need an OPS file which is a text type document that specifies the phones perimeters to ODIN so that it can flash (install) the ROM correctly. Download to your Samsung folder ODINv4.28 and the OPS file EUROPA_v1.0.ops
Step 2 – Let’s Do It!
The following tutorial (edited) taken from MADTEAM with acknowledgement and thanks to MayurV
Copy to your phones micro SD card, ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed’, ‘v1.7.2-hotfix1’ and ‘gapps-gb-20110815-signed’ before proceeding. This is best done by removing it and inserting it into a P.C’s or laptop’s SD card reader, if it has one.
2.1 First we have to get into Samsung standard recovery mode. You can enable this mode by following screenshot shown below. You phone must be turned off with the USB unplugged before doing this.
{
"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"
}
2.2 Now start Odin Multi Downloader v4.28 in your C:\Samsung folder on your PC. You will see following window.
- At first you may notice Odin says ‘Android’ and not ‘GT-I5500’. This is because we have not yet loaded the OPS file.
Your phone must now be in Download Mode and should be connected to the PC with the USB Cable that the phone shipped with. This is the only way Odin can detect your phone.
2.3 Select the OPS file in by clicking the OPS button (No.3) and the ClockworkMod-Galaxy5-v0.5 by clicking the One Package button (No.4).
Once you click on start button you will see all files will write on your phone, it will take around 1-7 minutes.
Once you see “PASS” in ODIN tool, you can remove USB cable from PC. Once your phone has rebooted and you will see following screen shown below.
*Edit** you do not need to wait for the PASS sign anymore. Once you see the handset screen change to the picture below, close Odin with the red ‘X’ window button, disconnect your USB cable and continue.
2.4 If you are new to use ClockworkMod recovery manager then before doing anything, please have a look at next screen to learn the navigation keys.
2.5 First we have to wipe our old DATA which is not compatible with ClockworkMod. Wiping old DATA is necessary if you are installing for the first time.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
- Press BACK (H/W) button on phone and follow next screen.
2.5 Now it’s time for the ROM installation.
Important Note:
• You MUST install the three files in this exact order:
• The main ROM package ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip’
• The hotfix package ‘v1.7.2-hotfix1.zip’
• The Google Apps package ‘gapps-gb-20110828-signed.zip’
- Select to ‘Choose file from SD card’ that you have saved earlier.
Both file should be in ZIP format only. Don’t extract, keep it in ZIP format and store it on SD card.
2.6 Once you are done with installation of these files. Press the BACK button until you return to the first screen shown below. Go to the first option and do reboot.
2.7 On next start-up, you will see CyanogenMod 7 Logo and system will load in few mins. Enjoy your new phone software!
We hope you all get successful installations of ClockworkMod 7 ROM’s
Written by Phillip Thorne – A.K.A sparkyuiop
Nice summary, thanks. Can I add a couple of points? Do not use CWM v6, it just times out when flashing with Odin. If you want to flash a new UK baseband you can download the latest one (I5500XWJP4) here http://www.multiupload.com/81IBI2MD0X - the one listed on the baseband page does not work.
Baseband and unlocking?
dwl99 said:
If you want to flash a new UK baseband you can download the latest one ...
Click to expand...
Click to collapse
What does flashing the baseband achieve? I assume this will not unlock the phone?
I would also like to add that once people have loaded this ROM onto their Samsung G5 there are many safe ways to extract the 8 digit passcode number to unlock the phone to any network.
I had previously used Jc_master method to extract the passcode which worked on the first one and second one that I did but for some reason the second one failed to reboot after and became bricked. (This was done prior to flashing a non-samsung ROM on both phones and I believe it will not work on the Cyanogen ROM)
This method looks good but I have not yet tried it: method
sparkyuiop said:
What does flashing the baseband achieve? I assume this will not unlock the phone?
I would also like to add that once people have loaded this ROM onto their Samsung G5 there are many safe ways to extract the 8 digit passcode number to unlock the phone to any network.
I had previously used Jc_master method to extract the passcode which worked on the first one and second one that I did but for some reason the second one failed to reboot after and became bricked. (This was done prior to flashing a non-samsung ROM on both phones and I believe it will not work on the Cyanogen ROM)
This method looks good but I have not yet tried it: method
Click to expand...
Click to collapse
Flashing a new baseband ensures that the GPS & phone will continue to work. Although you might want to do it only if anything doesn't work after you flash the ROM.
It isn't working, it will not detect the ops file despite my downloading it to C:/Samsung. Any advice?
Update:
I removed the .txt from the ops filename, now its working
Rad, clear and concise.
Cheers!
gwildor said:
Rad, clear and concise.
Cheers!
Click to expand...
Click to collapse
Thank You. I'm no expert at this so I'm pretty chuffed it's working out for people.
Tactics119 said:
It isn't working, it will not detect the ops file despite my downloading it to C:/Samsung. Any advice?
Update:
I removed the .txt from the ops filename, now its working
Click to expand...
Click to collapse
The OPS file should not be a text (.txt) extension (as you found out). One way to check it has the correct extension is to do this:
Open 'Computer' or 'My Computer'
At the top of the page click 'Organize' or 'View'
Select 'Folder and search options' or 'View'
Move the radio dot from 'Don't show hidden files, folders and drives' to 'Show hidden files, folders and drives'
Click 'Apply' then 'OK'
Go back to your OPS file and read it
Your OPS should read like this: EUROPA_v1.0.ops
If it reads: EUROPA_v1.0.ops.txt or EUROPA_v1.0.txt edit it so it looks like how it should read.
Clockwork Mod isn't a bootloader, it's a recovery!
Sent from my GT-I5500 using Tapatalk
It would be useful for someone, maybe, to update this good how-to, wouldn't it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
brainvision said:
It would be useful for someone, maybe, to update this good how-to, wouldn't it?
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Click to expand...
Click to collapse
Hey man don't steal me thunder! LOL, that's fine with me!
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Gavin01 said:
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Click to expand...
Click to collapse
Yes I am getting same screen after following installtion steps here, Please help..
anishmathw said:
Yes I am getting same screen after following installtion steps here, Please help..
Click to expand...
Click to collapse
did you wipe the phone with ClockworkMod?
Is it me or dose the installing of the samsung usb drivers take a long time to install( about 1 hour)...??
---------- Post added at 10:32 PM ---------- Previous post was at 09:47 PM ----------
Thanks for this...worked perfect,I now have ClockworkMod 7 on my Samsung Galaxy 5 (Europa) phone... 5 stars..
anishmathw said:
Yes I am getting same screen after following installtion steps here, Please help..
Click to expand...
Click to collapse
Gavin01 said:
followed all the instructions and the phone just says android in white writing then goes to the samsung screen and back again?
in a cycle?
anyone help me im desparate!
thanks
edit after a few attempts i use odin to flash again and get into clock work.........
anyone please please !!!1 its my wifes phone and shes going mad!
managed to get it back by flashing I5500XXJED_Android_2.1 with odin............
does this help and why i cant flash cynogen or any other rom?
Click to expand...
Click to collapse
brainvision said:
did you wipe the phone with ClockworkMod?
Click to expand...
Click to collapse
i have having the same issues as well... flash CWM with odin, boots fine into CWM, flash CM7 and gapps, and just get the white android writing
i did the following steps:
1. flash CWM with odin
2. in recovery, wiped data, wiped cache, wiped dalvik, wiped battery stats
3. flashed CM7 and gapps
4. just for good measures i wipe cache and dalvik
4. reboot
doing that gets me into boot loop, just keeps giving me the white android writing over and over again.
(off topic here a bit)
tried to go back to stock with odin and still have bootloop with samsung writing on the screen.... so far the phones a brick... cannot get it to boot into any ROM at all
Just let you know that on my phone the camera is not working properly,when recording it shudders and if you switch back to photo mode it crashes.
---------- Post added at 05:43 PM ---------- Previous post was at 05:04 PM ----------
c_86 said:
i have having the same issues as well... flash CWM with odin, boots fine into CWM, flash CM7 and gapps, and just get the white android writing
i did the following steps:
1. flash CWM with odin
2. in recovery, wiped data, wiped cache, wiped dalvik, wiped battery stats
3. flashed CM7 and gapps
4. just for good measures i wipe cache and dalvik
4. reboot
doing that gets me into boot loop, just keeps giving me the white android writing over and over again.
(off topic here a bit)
tried to go back to stock with odin and still have bootloop with samsung writing on the screen.... so far the phones a brick... cannot get it to boot into any ROM at all
Click to expand...
Click to collapse
I have put this rom on my phone twice now and it sounds like you are doing it wrong and missing the file "v1.7.2-hotfix1.zip"..
This is how i did it..
Started odin
This is how mine looks..
Remember to copy update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip,v1.7.2-hotfix1.zip,gapps-gb-20110828-signed.zip to your sd card,If you can't via phone use your card reader on your pc.
But all mine files are in the Samsung folder,so..
OPS - C:\Samsung\EUROPA_I5500_v1.0.ops
One Package - C:\Samsung\ClockworkMod-Galaxy5-v0.5.tar(ClockworkMod recovery manager)
Make sure everything is left ticked when starting odin just make sure one package is ticked..
switch phone off and plug in usb cable in phone(make sure you have installed the usb drivers,once in download mode you will see them installing wait for them to finish installing.)
Download mode - hold vol - down then middle button then off/on button and wait for download mode pic to come up.
you will see COM3 go orange in odin,press start and it will download ClockworkMod recovery manager to your phone and boot it..
Now wipe - data/Factory reset - yes
Now wipe - cache partition - yes
Now wipe - advanced - Dalvik cache - yes - back - Battery Stats - yes
You MUST install the three files in this exact order:
The main ROM package ‘update-cm-7.1.0-galaxy5-v1.7.2-MADTEAM-signed.zip’
The hotfix package ‘v1.7.2-hotfix1.zip’
The Google Apps package ‘gapps-gb-20110828-signed.zip’
all files should be in ZIP format only. Don’t extract, keep it in ZIP format and store it on SD card.
on phone - ClockworkMod recovery manager - install zip from cdcard - choose zip from sdcard - click on each file and install it in order,once you have done that restart your phone and your done..
Well that how I did it and it worked every time..
Good luck..
P.S If anyone wants to show a video on how to do it let me know.
Video here.. http://www.youtube.com/watch?v=dYmTps4tdwU
Looks like I bricked it...help please.
Tried this today and only got as far as attempting to install ClockworkMod. ODIN went to downloading recovery image and then hung there. Over an hour there. So I disconnected...now my phone is ummm...not working. Any ideas?
Benglian said:
Tried this today and only got as far as attempting to install ClockworkMod. ODIN went to downloading recovery image and then hung there. Over an hour there. So I disconnected...now my phone is ummm...not working. Any ideas?
Click to expand...
Click to collapse
It's obvious that it doesn't work anymore for now: I presume it shows up an interrupted link between the phone and PC..
So remove the battery, restart the PC and do it again.. maybe you miss the USB Samsung driver: try to reinstall them.. and use the 0.5 or 0.7 tar file for now
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
brainvision said:
It's obvious that it doesn't work anymore for now: I presume it shows up an interrupted link between the phone and PC..
So remove the battery, restart the PC and do it again.. maybe you miss the USB Samsung driver: try to reinstall them.. and use the 0.5 or 0.7 tar file for now
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Click to expand...
Click to collapse
Just the 0.7 tar,
Check your device model ! Settings -> About device -> Model number. See the third post for exact supported model numbers. If your device is a totally different model, it will not work (may even brick) !
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock Samsung firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many device (Galaxy S1, Galaxy Tab 7", Galaxy S2, Galaxy Note, Galaxy Nexus, Galaxy S3) and has clocked over 7 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
Coming from a different device ?
Keep reading, the new CF-Auto-Root incarnation of CF-Root is different from other CF-Root's.
What's installed
- SuperSU binary and APK
- Stock recovery
Installation and usage
Flash the CF-Auto-Root package as PDA in ODIN (details on how to do that are in next post), and your device should reboot into a modified recovery (signified by a large red Android logo) and it will install SuperSU for you and restore the stock recovery, and reboot back into Android.
If you don't get to the red Android logo, boot into recovery manually ("adb reboot recovery", or boot while holding Power+VolUp+Home).
Using this root increases your flash counter. You should run Triangle Away (see below) after rooting to reset the counter. Note that if you want to run custom kernels or custom recoveries, your flash counter will be set to 1 at every boot. Either configure Triangle Away to reset the counter at every boot (Play version only) or only reset the counter when you need to go into warranty.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Why isn't this just called CF-Root
Because it's not a traditional CF-Root with all the bells and whistles. This is a new class of CF-Root I'm going to make for more devices that keeps everything stock and just gives you only root. I'm "done" with permanent custom recoveries, they cause too many issues on new devices, in my opinion. The "Auto" comes from the fact that I'm building it in such a way it does most of the work automatically without me having to adjust any code. It's a larger project I was not yet wanting to release, but because so many people have asked me to release a CF-Root for the Note2, here is the early Note2 version.
Not included - Triangle Away
Triangle Away can be used to reset the flash counter after installing CF-Root. The flash counter keeps track of how many custom firmwares you have flashed, as this voids warranty. (No idea what this about ? Read up on it, you will want to use this !)
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
ODIN Installation (detailed)
- Follow these instructions to the letter. Do not touch any buttons or checkboxes that are not listed below to touch!
- Unzip the attached Odin3-vX.X.zip file
- Download and unzip the CF-Auto-Root-....zip file (see posts below this one)
- If you end up with a recovery.img and cache.img file, you've extracted twice. You need to end up with a .tar.md5 file - don't extract that one
- (USB) Disconnect your phone from your computer
- Start Odin3-vX.X.exe
- Click the PDA button, and select CF-Auto-Root-....tar.md5
- Put your phone in download mode (turn off phone, then hold VolDown+Home+Power to boot - if it asks you to press a button to continue, press the listed button, or run adb reboot download command)
- (USB) Connect the phone to your computer
- Make sure Repartition is NOT checked
- Click the Start button
- Wait for Android to boot
- Done (if it took you more than 30 seconds, you need practise!)
- NOTE: Sometimes the device does *not* boot into recovery mode and root your device. Just do the entire procedure again if this happens. If it still will not install root and such, make sure that in Odin "Auto Reboot" is not checked. Then after flashing, pull the battery, and boot with VolUp+Home+Power button to boot into recovery manually. This will start the install process.
New to Samsung? Unfamiliar with Odin? Think all the above is a hassle? Get used to it. It's very simple, and us Samsung folk use Odin (or Mobile ODIN ) for everything! It's so very very convenient once you get used to it. Notice the 30 second comment above? For experienced users, the entire process indeed takes only 30 seconds!
You may now optionally want to install and run Triangle Away to reset the flash counter.
Download
2013.05.20 --- CF-Auto-Root
SuperSU: v1.30
Download:
GT-N7100: CF-Auto-Root-t03g-t03gxx-gtn7100.zip
GT-N7105: CF-Auto-Root-t0lte-t0ltexx-gtn7105.zip
SHV-E250K: CF-Auto-Root-t0ltektt-t0ltektt-shve250k.zip
SHV-E250L: CF-Auto-Root-t0ltelgt-t0ltelgt-shve250l.zip
SHV-E250S: CF-Auto-Root-t0lteskt-t0lteskt-shve250s.zip
--- History ---
2013.05.20: SuperSU v1.30
2013.02.20: SuperSU v1.05
2012.12.02: SuperSU v0.98
2012.10.12: SuperSU v0.96
Just use the thanks buttons to say thanks! Chainfire even asked you to do that in the post, if you actually read it!
We don't need a 100 page thread here of people going "thanks" or "+1" or "nice one"..... use some common sense
Lennyuk said:
Just use the thanks buttons to say thanks! Chainfire even asked you to do that in the post, if you actually read it!
We don't need a 100 page thread here of people going "thanks" or "+1" or "nice one"..... use some common sense
Click to expand...
Click to collapse
"Sorry, you are limited to 8 thanks per day"
I am sorry.
Considering i'm a noob @ rooting this is very useful so ty & also is it possible to have OTA updates remain on the device once rooted?
I've got SGN2 today and this thread fully to help.Thanks so much.
So when will "Dutchy" & "Indy" get Note 10.1 so that we can get some order over there as well??
Sent from my GT-N7100 using xda premium
Now all we need is chainfire3D support
toofank said:
Now all we need is chainfire3D support
Click to expand...
Click to collapse
don't hold your breath on this one, this isn't the first jellybean device he owns and he has so far chosen not to update it at all.
HI,why after reboot in recovery i saw the 3°recovery mode and no possibilitie to make a nandroid backup?
Thanks
thedid63 said:
HI,why after reboot in recovery i saw the 3°recovery mode and no possibilitie to make a nandroid backup?
Thanks
Click to expand...
Click to collapse
By reading the first post it doesn't look like CWM is included, but the stock recovery and that's why.
Sent from my GT-P7500 using Tapatalk 2
No, this doesn't have advanced cwm.
This is pure stock recovery + root
If you want cwm, read 2nd post of first line on my signature
Sent from my GT-N7100 using xda premium
@Chainfire
Congratulations to the five-year period at the XDA developers!
{
"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"
}
as i9000 said:
@Chainfire
Congratulations to the five-year period at the XDA developers!
Click to expand...
Click to collapse
Thanks, if you hadn't mentioned this, I wouldn't have noticed !
Can you update ota if you use stock rom and this root method?
Beamen1 said:
Can you update ota if you use stock rom and this root method?
Click to expand...
Click to collapse
Nope.....OTA is broken on mine...wondering if someone can fix this
Sent from my GT-N7100 using xda premium
Not sure about automatic OTAs, but if you can download the OTA from for example SamMobiles, Mobile ODIN can probably flash it for you ...
Chainfire said:
Not sure about automatic OTAs, but if you can download the OTA from for example SamMobiles, Mobile ODIN can probably flash it for you ...
Click to expand...
Click to collapse
Chainfire..I can confirm that the OTA is not working after following CF Root. is a fix possible for this ..? If I do triangle away on this will OTA work again..?
Alternately can i directly flash from Mobile Odin..? Dont I need advanced CWM ..?
Chainfire said:
Not sure about automatic OTAs, but if you can download the OTA from for example SamMobiles, Mobile ODIN can probably flash it for you ...
Click to expand...
Click to collapse
I have heard reports of mobile Odin not working properly on n7100...has it been fixed?
Sent from my GT-N7100 using xda premium
---------- Post added at 02:06 PM ---------- Previous post was at 02:04 PM ----------
zabaknilesh said:
Chainfire..I can confirm that the OTA is not working after following CF Root. is a fix possible for this ..? If I do triangle away on this will OTA work again..?
Alternately can i directly flash from Mobile Odin..? Dont I need advanced CWM ..?
Click to expand...
Click to collapse
Read his last post above you....
Sent from my GT-N7100 using xda premium
How to Root your Verizon Galaxy S4
***VRUAMDK Build Only! - Look for this***
{
"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"
}
Description: This is a simple guide that will allow you to easily root your Verizon Galaxy S4 device without having to wipe your device or flash a full prerooted factory image. This method works using a leaked prerelease kernel (provided by user sextape) and root method (provided by user djrbliss). Only change is I have modified the Motochopper root method to use the latest SuperSU instead.
Video Demo of the Full Process (Courtesy of DroidModd3rX)
Click to expand...
Click to collapse
***WARNING: DOES NOT WORK ON THE VRUAME7 BUILD***
If you have already updated to VRUAME7 BUILD please see link below for the NEW root method
Link to Thread
Click to expand...
Click to collapse
Step 1 - Preparation
Download and Install Samsung Official USB Drivers - Link
Download and extract ODIN v3.07 - Link
Download the VRUAMD2 Prerelease Kernel - Link
Download the Stock VRUAMDK Kernel for your phone - Link
Download and extract the Motochopper Root Exploit Tool - Link
Click to expand...
Click to collapse
Step 2 - Flashing VRUAMD2 Prerelease Kernel to remove Root block
Boot phone into ODIN mode (See here for how-to)
Flash the VRUAMD2 Prerelease Kernel using ODIN v3.07 ***in PDA section only*** (See here for guide on flashing)
Boot back to Android and verifying everything is still working and kernel has flashed successfully
Click to expand...
Click to collapse
Step 3 - Rooting Your Device
Go into Settings > More > About phone > tap "Build number" about 7 times until it unlocks Developer options
Verify in Developer options setting on your device that you have "USB debugging" checked
Verify in Developer options setting on your device that you have "Verify apps via USB" unchecked
Verify in Security setting on your device that you have "Unknown sources" checked
Verify in Security setting on your device that you have "Verify apps" unchecked
Connect your phone to your computer and open "Run.bat" file from the location you have extracted motochopper to
You will see a message on the phone asking you to accept the new computer connection (select to always allow and select OK)
After motochopper runs and your phone reboots on its own, check if SuperSU has any update in the Play Store
Open SuperSU app and let the binary update itself to the latest ***VERY IMPORTANT OR YOU WILL LOSE ROOT ON STEP 4***
Once complete, just open a root application and verify that is able to access root properly
Click to expand...
Click to collapse
Step 4 - Restoring Stock Kernel
Boot phone into ODIN mode (See here for how-to)
Flash the Stock VRUAMDK Kernel using ODIN v3.07 ***in PDA section only*** (See here for guide on flashing)
Boot back to Android and verifying everything is still working and kernel has flashed successfully
After your phone boots back to Android, you should now be fully rooted and on the fully stock original firmware that came on your device
Click to expand...
Click to collapse
Step 5 - Restoring Custom Recovery (Optional)
Make sure you are rooted first using the above 4 steps first
For official TWRP Recovery follow the steps in this thread (or download from Goomanager): Link Here
For official ClockworkMod Recovery just download ROM Manager app and install from there
For CWM-based Recovery follow the steps in this thread: Link Here
For OUDHS Gesture Touch CWM-based Recovery follow the steps in this thread: Link Here
Click to expand...
Click to collapse
Credits
Credit goes to sextape for providing the VRUAMD2 Prerelease Kernel (Original Source)
Credit goes to sextape for providing the VRUAMDK Stock Firmware and Kernel (Original Source)
Credit goes to djrbliss for creating Motochopper Root Exploit Tool (Original Post)
Credit goes to cnlson for providing ftp filehosting (via PM)
Credit goes to ChainsDD for creating Superuser (Original Source)
Please note: Credit for this method goes entirely to the users who have created these tools and provided the files. I am only bringing together all these files and creating a simple guide for everyone to follow.
Thank you for doing this! However, all of your links are making my Antivirus go nuts (which isnt normal, using Bit Defender)
Proweedsmoker said:
Thank you for doing this! However, all of your links are making my Antivirus go nuts (which isnt normal, using Bit Defender)
Click to expand...
Click to collapse
The motochopper link triggered mine. Followed the instructions and I had to run the motochopper run.bat twice, first time it installed Superuser.apk but it wasn't rooted. Second time everything worked perfectly, I am now rooted. Thanks!
--FCOD
Edit: Every reboot now, I get this notification "Detection information: The device has detected an application attempting unpermitted actions. To protect your devices, it is recommended you reboot". See attached screenshot. I can clear the notification without any issues, seemingly.
sweet. will give it a whirl once i get off work!
This worked for me this afternoon. As I mentioned in other threads if you're getting stuck at boot.img in Odin try using a USB port on the back of your PC. That was what did it for me (to get the kernel installed.) I did everything else from the back USB port as well and it went great.
Cubs2008 said:
This worked for me this afternoon. As I mentioned in other threads if you're getting stuck at boot.img in Odin try using a USB port on the back of your PC. That was what did it for me (to get the kernel installed.) I did everything else from the back USB port as well and it went great.
Click to expand...
Click to collapse
I've found this to be true for many different phones. I ALWAYS use the back USB port!
--FCOD
flyingcowofdoom said:
Every reboot now, I get this notification "Detection information: The device has detected an application attempting unpermitted actions. To protect your devices, it is recommended you reboot". See attached screenshot. I can clear the notification without any issues, seemingly.
Click to expand...
Click to collapse
This message is actually related to SEAndroid. If you freeze the apk using an app like Titanium Backup, it should remove the message.
open1your1eyes0 said:
This message is actually related to SEAndroid. If you freeze the apk using an app like Titanium Backup, it should remove the message.
Click to expand...
Click to collapse
Sweet. Frozen, looks like the messages stopped. Thanks!
--FCOD
I know I have read somewhere about the "Boot unlock- Custom" message that appears when you boot the phone, could somebody point me in the right direction on how to fix this please? (Running stock softwear, no ROM yet)
Also, how would I go about switching the Superuser app to SuperSU? (I have the paid SuperSU I use from my tablet and want to use it with my new S4)- NVM- Chainfire made it all to easy for beginners like myself. SuperSU will overwrite and remove superuser automaticly for anybody else with this!
open1your1eyes0 said:
This message is actually related to SEAndroid. If you freeze the apk using an app like Titanium Backup, it should remove the message.
Click to expand...
Click to collapse
I can confirm that freezing SEAndroid 1.0 removes the warning instantly
Install SuperSU and update the binaries. Then uninstall superuser and reboot the phone 2 times and the unlock icon will be gone. Good luck.
Proweedsmoker said:
I know I have read somewhere about the "Boot unlock- Custom" message that appears when you boot the phone, could somebody point me in the right direction on how to fix this please? (Running stock softwear, no ROM yet)
Also, how would I go about switching the Superuser app to SuperSU? (I have the paid SuperSU I use from my tablet and want to use it with my new S4)- NVM- Chainfire made it all to easy for beginners like myself. SuperSU will overwrite and remove superuser automaticly for anybody else with this!
Click to expand...
Click to collapse
So what about flashing back to the stock kernel once SU is installed as per the directions on sxtp?
ilkevinli said:
Install SuperSU and update the binaries. Then uninstall superuser and reboot the phone 2 times and the unlock icon will be gone. Good luck.
Click to expand...
Click to collapse
If this works for a couple of folks, later on I'll try to modify motochopper to use SuperSU instead of Superuser.
brizey said:
So what about flashing back to the stock kernel once SU is installed as per the directions on sxtp?
Click to expand...
Click to collapse
For now it's not required, I'm going to do a lot of testing tonight and if restoring the VRUAMDK kernel still works with latest SuperSU I may just update both at once.
It worked for me. This was posted somewhere in the AT&T S4 section.
Thanks I'll be trying this as soon as I get my hands on a S4 (soon).
Sent from my SCH-I605 using Xparent Green Tapatalk 2
We need an unlocked bootloader to get a working recovery right? Would it be semi safe to assume we can follow some of the other models (i9505, AT&T etc..,) "de-bloat" threads to de-bloat ours?
are there any risks with this method, i.e., not being able to receive OTA? can we easily de-root and restore root?
km8j said:
are there any risks with this method, i.e., not being able to receive OTA? can we easily de-root and restore root?
Click to expand...
Click to collapse
I was actually hoping to block OTAs until the bootloader unlock is released...then custom forevermore!
this needs to be pinned the other needs to be deleted !! i stay we stick with the guy who made all the s3 guides and he did them perfect.. and that is my buddy @open1your1eyes0 be back in about an hour missed fedex today now i gotta goto the warehouse to get my s4
jeez... that was too f'in ez
Do we have a list of what's safe to remove yet (before we get custom Roms) ?
Hi, I hope someone here has the know-how to help me out of the mess I've made for myself.
Okay, here's what I did:
1.) Accepted the KitKat upgrade.
2.) Ran qbking's autoroot thing. (It worked, thanks.)
3.) Flashed TWRP (I forget which version)
4.) Flashed Sac23's rom.
After the rom flash I was trapped in the 'boot-loop of death' where all powering my pone on
achieved was getting the "Samsung Galaxy Note 3" splash page & then rebooting, endlessly.
In a panic I flashed the "NAB Engineering bootloader tar file" I grabbed off ofhttp://forum.xda-developers.com/showthread.php?p=51165389 .
Now every time I power on I get the "Samsung Galaxy Note 3" splash page (again) a forced reboot and now get the message;
"Kernel Panic!
wait...
Done!
UDC START
KERNEL PANIC
UPLOAD MODE"
At which point it just plain freezes.
Is there anyone out there who tell me how (or IF it's even possible now) I can just get back to stock??
ANY help/opinion/advice would be seriously appreciated.
Flumpy said:
Hi, I hope someone here has the know-how to help me out of the mess I've made for myself.
Okay, here's what I did:
1.) Accepted the KitKat upgrade.
2.) Ran qbking's autoroot thing. (It worked, thanks.)
3.) Flashed TWRP (I forget which version)
4.) Flashed Sac23's rom.
After the rom flash I was trapped in the 'boot-loop of death' where all powering my pone on
achieved was getting the "Samsung Galaxy Note 3" splash page & then rebooting, endlessly.
In a panic I flashed the "NAB Engineering bootloader tar file" I grabbed off ofhttp://forum.xda-developers.com/showthread.php?p=51165389 .
Now every time I power on I get the "Samsung Galaxy Note 3" splash page (again) a forced reboot and now get the message;
"Kernel Panic!
wait...
Done!
UDC START
KERNEL PANIC
UPLOAD MODE"
At which point it just plain freezes.
Is there anyone out there who tell me how (or IF it's even possible now) I can just get back to stock??
ANY help/opinion/advice would be seriously appreciated.
Click to expand...
Click to collapse
You should check sacs rom for instructions on this issue, as the engineering bootloader isn't a fallback option to correct your inability to boot.
Please indicate the version of TWRP you're using, as knowing that will help. There's a chance that you are on the wrong version of TWRP, which could solve your issue.
You can always reflash stock NAB, flash TWRP, then the rom, which is pre-rooted.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I've been in a similar situation. Pull the battery on the Galaxy Note 3 page. Then hold the necessary buttons to get into recovery before putting the battery back in. Keep them held while putting the battery in. If that doesn't help break the cycle then do the same thing (battery pull and hold necessary buttons down for Odin mode/download mode and keep them down while placing battery back in) till it hits the correct screen. Then reboot to recovery from there.
@micmars: Tnx for the speedy reply (guess all that ostuff I've seen people writing about you here @ XDA are true, you really ARE a benignly omnipotent kinda dood. )
I ended up flashing the stock NAB firmware (with TWRP 2.7.0.0). It was nice not being mocked by the 'Boot-Loop of Doom'. [for a heartbeat @ least. =\ =D ]
BUT THEN
I started the root process thing again;
1.) Ran "CF-Auto-Root..." (sorry for my earlier snafu [see first post] Chainfire/QbKing77.)
2.) Flashed TWRP 2.7.0
3.) And then reflashed sac23's rom.
& I'll be uh, darned, if it didn't launch back into the same *#&$! boot-loop again. (Just to be certain I was getting a good d/l, I RE-downloaded it to both my phone AND computer this time.) And still kept getting stuck in the same "Samsung Gal..." splash screen loop. =\
For grins & giggles I downloaded a different ROM (Toxic Swamp v1.0.2), ran through the root process, all was good until I flashed the rom and the SAME bootloop started up again.
Can anyone please tell me if I'm doing something screwy in my process or if maybe I pissed of a diety somewhere or something?
ANY advice/comment/good guess would be greatly appreciated.
Always remember, ->Pobody's nerfect.<-
Sent from my Sprint-flavored SM-900P (using the XDA app.)
Make sure your flashing roms that are 4.4.2 you can't use 4.3 roms toxic Swamp 1.0.3 is 4.3 .... There is no going back to 4.3 now
Sent from my SM-N900P using Xparent BlueTapatalk 2
Oh, and Tw1sted247, I tried the technique you mentioned (appreciate it) but it's not that I can't get into either Odin/recovery, it's that anytime I try to start my phone with anything other than stock it immediately starts in w/the merry-go-round from hell (boot-loop) thang.
->Pobody's nerfect.<-
Sent from my Sprint-flavored SM-900P (using the XDA app.)
OK, I'm Confused...
Flumpy said:
Oh, and Tw1sted247, I tried the technique you mentioned (appreciate it) but it's not that I can't get into either Odin/recovery, it's that anytime I try to start my phone with anything other than stock it immediately starts in w/the merry-go-round from hell (boot-loop) thang.
->Pobody's nerfect.<-
Sent from my Sprint-flavored SM-900P (using the XDA app.)
Click to expand...
Click to collapse
OK, I'm confused..which is my favorite stage of enlightenment, so thank you.
So, as has been asked by others, why would you flash a TouchWiz Jellybean 4.3 ROM (Toxic Swamp) built on MJ4 onto a TouchWiz KitKat rom built on NAB(D)? You really shouldn't do that, as it is inviting trouble across the phone's OS.
I would kindly ask that you boot your phone and show us the "About Device" page (not the one that has all of your personal info, as no one needs to see your MEID, &c). That will give us a start.
You may be looking at a complete overhaul of your device.
Be thankful that your phone booted up, and then ONLY flash the original NAB(D) tar or One-Click, then TWRP from PC Odin, and then inject root from recovery, using the latest Chainfire Superuser zip found here.
After that, we can block and tackle where you wish to arrive.
Okay, here's the requested screenshot:
{
"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"
}
Sent from my Sprint-flavored SM-900P (using the XDA app.)
Or better yet:
Flumpy said:
Or better yet:
View attachment 2646244
Click to expand...
Click to collapse
I'm usually loathe to recommend a rom, but to recommend stock DeOdex or Odex, seems harmless enough, and it'll give us a clean slate. Looks like your completely stock.
We're going to take this on two phases, first to get you just recovery and root, then onto one of the stockish roms. It's weird, but so is your situation.
So, grab one of the two stockish NABD (we'll skip the NAB group), put it on your internal memory, but plan to use it later.
TWRP below,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
We'll get you no ads and some mods if you want, but for now, let's get you flashing something.
Superuser (goes on your phone, try internal storage),
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
1. Flash recovery above from PC Odin, version 3.07 below,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
Power down phone completely, take off any case, install Odin, leave auto restart checked (why not?), hold power + volume down + home to go into download mode, hit volume up to confirm, then, have your fingers at the ready, you'll be holding home + volume up simultaneously, very soon, load the tar I gave into the PDA slot, once Odin confirms it's ready, click start on the computer, have your fingers ready, once it flashes and starts to power cycle, hit those two keys, and you're in recovery...
2. In recovery, flash the superuser zip I gave you, reboot...
Now stay on this awhile before proceeding to the stockish rom.
Please quote me when responding.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
D'oh!
First of all I'd like to thank micmars et al. for lending your knowlege, expertise and namely, PATIENCE as I floundered through a SIMPLE root/flash.
Just to give ya'll the skinny, i FinAllY did manage to install both TWRP 2.7 and Sac23's kk rom onto my Sprint Note 3.
-> To be honest, I'm nearly beyond belief happy/surprised that I didn't manage to kill the $#%@ thing! =] <-
micmars said:
I'm usually loathe to recommend a rom, but to recommend stock DeOdex or Odex, seems harmless enough, and it'll give us a clean slate. Looks like your completely stock.
We're going to take this on two phases, first to get you just recovery and root, then onto one of the stockish roms. It's weird, but so is your situation.
So, grab one of the two stockish NABD (we'll skip the NAB group), put it on your internal memory, but plan to use it later.
TWRP below,
https://www.dropbox.com/s/ptl8dyomprxxn0l/openrecovery-twrp-2.7.0.0-hltespr-4.4.img.tar
We'll get you no ads and some mods if you want, but for now, let's get you flashing something.
Superuser (goes on your phone, try internal storage),
https://www.dropbox.com/s/lbtuggkhqknm2ik/UPDATE-SuperSU-v1.93.zip
1. Flash recovery above from PC Odin, version 3.07 below,
https://www.dropbox.com/s/z2n10tjzmxlhaz4/Odin3 v3.07.zip
Power down phone completely, take off any case, install Odin, leave auto restart checked (why not?), hold power + volume down + home to go into download mode, hit volume up to confirm, then, have your fingers at the ready, you'll be holding home + volume up simultaneously, very soon, load the tar I gave into the PDA slot, once Odin confirms it's ready, click start on the computer, have your fingers ready, once it flashes and starts to power cycle, hit those two keys, and you're in recovery...
2. In recovery, flash the superuser zip I gave you, reboot...
Now stay on this awhile before proceeding to the stockish rom.
Please quote me when responding.
Good luck!
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Flumpy said:
First of all I'd like to thank micmars et al. for lending your knowlege, expertise and namely, PATIENCE as I floundered through a SIMPLE root/flash.
Just to give ya'll the skinny, i FinAllY did manage to install both TWRP 2.7 and Sac23's kk rom onto my Sprint Note 3.
-> To be honest, I'm nearly beyond belief happy/surprised that I didn't manage to kill the $#%@ thing! =] <-
Click to expand...
Click to collapse
You'll likely come to find over time that these devices are pretty much able to withstand almost anything you can throw at them.
You can brick for good if you do something insane like flash a bootloader from the wrong device or build, but that aside, you can create quite the bit of turmoil for yourself.
Either way, terrific news.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Full credit goes to Edgardo_Uchicha for discovering this method. This is just a very specific tutorial using his process.
*DISCLAIMER* - EVEN THOUGH THERE IS A VERY MINUTE CHANCE OF ANYTHING HAPPENING TO YOUR DEVICE, I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR. FURTHERMORE ALL OF THE PROGRAMS USED IN THIS TUTORIAL BELONG TO THEIR RESPECTIVE OWNERS AND I DO NOT NOR DO I CLAIM TO OWN ANY OF THEM.
Now that we've got the boring stuff out of the way, lets get on with the tutorial.
This exact method that i will be showing you is the method that I used to root my own Samsung Galaxy S4 on Verizon.
First, you will want to download all of the files needed. I have created a zip file right here containing all of the programs / files that we will be using.
Step 1: First things first, were going to enable 'USB Debugging' on our S4. Go into the 'Settings > About phone.' Find the build number and tap it repeatedly until you get a message saying 'You are now a developer'. Go back into the settings and you should see 'Developer options' right above 'About phone'. Click on that. Once your in developer options, scroll until you see a 'USB debugging' option. Tap on it and hit 'OK' on the warning prompt that appears.
Step 2: After that switch over to your computer. Unzip the zip file that you downloaded earlier. Run the 'SamsungDrivers.exe' program to install the necessary drivers. Extract the file titled 'Odin3_v3.10.7.zip' as well as we will be using that to flash our kernel later on. Also run the 'mobilego_setup_full818.exe' because that will be the program we will be using to obtain root.
Step 3: Now go back to your S4 and shut it down. Once its shutdown, hold the 'Volume down', 'Home button', and 'Power button' to boot your device into download mode. When you get to a confirmation prompt, click the 'Volume up' button to continue. Once you see the android guy and text saying "Downloading..." your at the right place. Plug your phone into your computer and launch 'Odin3 v3.10.7.exe' from the zip we extracted earlier. You should see a message saying 'Added!!' If you don't see that message, you probably didn't install the drivers correctly. Click the button that says 'AP' and navigate to the unziped file and find the file titled 'OC1_kernel.tar.md5'. Select that file. Once Odin loads the file, click the 'Start' button. The flashing of the kernel should only take a few seconds and you should see your device reboot like normal.
Step 4: Now that you are rebooted MAKE SURE TO unlock your device. The MobileGo application on your computer should automatically sense your device. When the little alert windows from MobileGo pops up, click the 'Manage' button. It should start a whole process during which a confirmation with a bunch of random looking characters will probably popup on your S4. Click 'OK' when that pops up. Once that happens then just wait. The MobileGo application will be flashing an app to your device. When it does there will probably be another popup on your device from google. Just click the 'Decline' button and keep on letting it do its thing. When it's done, you should see your device in the MobileGo application along with a button that says 'One-Click Root'. Click on this button. While it might seem like it's taking a while, it's just running the rooting process. After a few minutes, you should get a popup on your computer saying that root was successful.
Step 5 (optional but HIGHLY recommended): Install Supersu. For those of you that don't know, Supersu is a root manager app than makes sure you are asked before an app gets root permission. To install it it's as simple as going to the play store and downloading it. Once you've downloaded it, open the app and it will ask you what recovery you have installed. Click the 'Normal' button and let it run. It should say that it was successful and from there hit the "Reboot" button to fully apply it.
Step 6 (optional but also HIGHLY recommended): Flashing the newer kernel. By flashing the newer 'OF1_kernel.tar.md5' you will not lose root and you will get rid of a very pesky message that pops up every time you do something with root on the OC1 kernel. There really is no downside to it and it only takes a minute. Repeat 'Step 3' but instead of selecting the 'OC1_kernel.tar.md5' choose the 'OF1_kernel.tar.md5'. Once it flashes your phone should automatically reboot and be rooted on the latest kernel.
All comments, feedback and questions are appreciated as this is my first post ever to XDA Forums.
Thanks!
So this works if I have accepted the OTA for OF1?
Yes
seadooman said:
So this works if I have accepted the OTA for OF1?
Click to expand...
Click to collapse
Yes
I followed this guide as written and everything worked perfectly. Could not be easier! Very happy to have root again on my S4 OF1!
Just to reiterate, once you click the "one click root" button in MobilGO, be patient. It does take a long time...close to 5 minutes in my case, so don't get all antsy!
Many thanks to the OP for this clear and concise guide!
jwhistler said:
I followed this guide as written and everything worked perfectly. Could not be easier! Very happy to have root again on my S4 OF1!
Just to reiterate, once you click the "one click root" button in MobilGO, be patient. It does take a long time...close to 5 minutes in my case, so don't get all antsy!
Many thanks to the OP for this clear and concise guide!
Click to expand...
Click to collapse
Glad I could help!:good:
guy theawesome said:
Full credit goes to Edgardo_Uchicha for discovering this method. This is just a very specific tutorial using his process.
*DISCLAIMER* - EVEN THOUGH THERE IS A VERY MINUTE CHANCE OF ANYTHING HAPPENING TO YOUR DEVICE, I AM NOT RESPONSIBLE FOR ANY DAMAGES THAT MAY OCCUR. FURTHERMORE ALL OF THE PROGRAMS USED IN THIS TUTORIAL BELONG TO THEIR RESPECTIVE OWNERS AND I DO NOT NOR DO I CLAIM TO OWN ANY OF THEM.
Now that we've got the boring stuff out of the way, lets get on with the tutorial.
This exact method that i will be showing you is the method that I used to root my own Samsung Galaxy S4 on Verizon.
First, you will want to download all of the files needed. I have created a zip file right here containing all of the programs / files that we will be using.
Step 1: First things first, were going to enable 'USB Debugging' on our S4. Go into the 'Settings > About phone.' Find the build number and tap it repeatedly until you get a message saying 'You are now a developer'. Go back into the settings and you should see 'Developer options' right above 'About phone'. Click on that. Once your in developer options, scroll until you see a 'USB debugging' option. Tap on it and hit 'OK' on the warning prompt that appears.
Step 2: After that switch over to your computer. Unzip the zip file that you downloaded earlier. Run the 'SamsungDrivers.exe' program to install the necessary drivers. Extract the file titled 'Odin3_v3.10.7.zip' as well as we will be using that to flash our kernel later on. Also run the 'mobilego_setup_full818.exe' because that will be the program we will be using to obtain root.
Step 3: Now go back to your S4 and shut it down. Once its shutdown, hold the 'Volume down', 'Home button', and 'Power button' to boot your device into download mode. When you get to a confirmation prompt, click the 'Volume up' button to continue. Once you see the android guy and text saying "Downloading..." your at the right place. Plug your phone into your computer and launch 'Odin3 v3.10.7.exe' from the zip we extracted earlier. You should see a message saying 'Added!!' If you don't see that message, you probably didn't install the drivers correctly. Click the button that says 'AP' and navigate to the unziped file and find the file titled 'OC1_kernel.tar.md5'. Select that file. Once Odin loads the file, click the 'Start' button. The flashing of the kernel should only take a few seconds and you should see your device reboot like normal.
Step 4: Now that you are rebooted MAKE SURE TO unlock your device. The MobileGo application on your computer should automatically sense your device. When the little alert windows from MobileGo pops up, click the 'Manage' button. It should start a whole process during which a confirmation with a bunch of random looking characters will probably popup on your S4. Click 'OK' when that pops up. Once that happens then just wait. The MobileGo application will be flashing an app to your device. When it does there will probably be another popup on your device from google. Just click the 'Decline' button and keep on letting it do its thing. When it's done, you should see your device in the MobileGo application along with a button that says 'One-Click Root'. Click on this button. While it might seem like it's taking a while, it's just running the rooting process. After a few minutes, you should get a popup on your computer saying that root was successful.
Step 5 (optional but HIGHLY recommended): Install Supersu. For those of you that don't know, Supersu is a root manager app than makes sure you are asked before an app gets root permission. To install it it's as simple as going to the play store and downloading it. Once you've downloaded it, open the app and it will ask you what recovery you have installed. Click the 'Normal' button and let it run. It should say that it was successful and from there hit the "Reboot" button to fully apply it.
Step 6 (optional but also HIGHLY recommended): Flashing the newer kernel. By flashing the newer 'OF1_kernel.tar.md5' you will not lose root and you will get rid of a very pesky message that pops up every time you do something with root on the OC1 kernel. There really is no downside to it and it only takes a minute. Repeat 'Step 3' but instead of selecting the 'OC1_kernel.tar.md5' choose the 'OF1_kernel.tar.md5'. Once it flashes your phone should automatically reboot and be rooted on the latest kernel.
All comments, feedback and questions are appreciated as this is my first post ever to XDA Forums.
Thanks!
Click to expand...
Click to collapse
One second. What's wrong with the original thread???
Ummmm
Newyork! said:
One second. What's wrong with the original thread???
Ummmm
Click to expand...
Click to collapse
This is just for any beginner user who want to root their S4. You have to remember that not everyone is on the same level and I know when I got into rooting I appreciated the very in-depth tutorials that I found.
Newyork! said:
One second. What's wrong with the original thread???
Ummmm
Click to expand...
Click to collapse
I looked at both threads and this one seemed easier for me to follow. Always nice to have choices!
jwhistler said:
I looked at both threads and this one seemed easier for me to follow. Always nice to have choices!
Click to expand...
Click to collapse
Thank you for you support!
trouble with a black screen
after using your method and getting though step three the device rebooted , the sounds came on and everything seems fine except once the virzon red boot up screen is supposed to come on the screen just goes dark and doesn't turn on, the sounds still work, but the hard buttons on the bottom dont light up either, any suggestions on how to fix it, and i can pull the battery and get into download mode as well.
Syconder said:
after using your method and getting though step three the device rebooted , the sounds came on and everything seems fine except once the virzon red boot up screen is supposed to come on the screen just goes dark and doesn't turn on, the sounds still work, but the hard buttons on the bottom dont light up either, any suggestions on how to fix it, and i can pull the battery and get into download mode as well.
Click to expand...
Click to collapse
First of all, sorry about your trouble. If it happened to me I would recommend to do step 6 and flash the OF1 kernel to your device. I've been in a similar situation before and I've found that updating the kernel with make it work perfectly again.
Syconder said:
after using your method and getting though step three the device rebooted , the sounds came on and everything seems fine except once the virzon red boot up screen is supposed to come on the screen just goes dark and doesn't turn on, the sounds still work, but the hard buttons on the bottom dont light up either, any suggestions on how to fix it, and i can pull the battery and get into download mode as well.
Click to expand...
Click to collapse
***ATTENTION!!!! - THIS WILL FACTORY RESET YOUR DEVICE AND YOU WILL LOSE ALL OF YOUR PERSONAL DATA. USE AS A LAST RESORT***
If flashing the OF1 kernel doesn't work for you then try using this program made by Verizon. After you install the program, boot your device into download mode. Once in download mode plug your S4 into your computer and launch the Verizon program. Click on the repair assistant tab and you should see your device listed - it might take a minute of two to sense your phone. Once it's listed, click on it and then click the repair button. It might take a while depending on your connection but the Verizon program will reflash your device with the latest software. Don't worry though, the latest version is still running the OF1 kernel and if fully root-able using the method described in my post. Hope everything works for you!
Root Failed
It appears that oc1_kernel.tar.md5 is applied successfully. In step 4, once I hit one click root, it says Verizon SCH-I545 root failed. When I run getprop ro.bootloader, it still shows I545VRUGOF1. Does anyone have any recommendations of what I'm doing wrong?
Would it also work coming from NC5 bootloader?
NC5 bootloader
seadooman said:
Would it also work coming from NC5 bootloader?
Click to expand...
Click to collapse
There are lots of other ways to root on a NC5 bootloader
seadooman said:
Would it also work coming from NC5 bootloader?
Click to expand...
Click to collapse
Use ToweRoot.
So I just successfully flashed my OF1 S4 to OC1 using the steps listed. I'm interested in installing a new ROM, but have read that only touchwiz based ROMs are currently compatible. If this is the case, what are my options? I'm very new to this and am not really sure what is available to use, given that I currently have lollipop. Sorry for the (probably) stupid questions that you probably hear all of the time
hankscaddy said:
It appears that oc1_kernel.tar.md5 is applied successfully. In step 4, once I hit one click root, it says Verizon SCH-I545 root failed. When I run getprop ro.bootloader, it still shows I545VRUGOF1. Does anyone have any recommendations of what I'm doing wrong?
Click to expand...
Click to collapse
Even after you update the kernel, it will still show up as I545VRUGOF1 but in reality it has changed and it rootable. All I can recommend is reflashing the kernel and retrying the root method. You might have to try rooting more than once.
tdwpgtp said:
So I just successfully flashed my OF1 S4 to OC1 using the steps listed. I'm interested in installing a new ROM, but have read that only touchwiz based ROMs are currently compatible. If this is the case, what are my options? I'm very new to this and am not really sure what is available to use, given that I currently have lollipop. Sorry for the (probably) stupid questions that you probably hear all of the time
Click to expand...
Click to collapse
I'm not going to lie, I'm actually pretty new to the ROM flashing on the S4 although I have done it on multiple other devices. However, from the things that I've read and tried I would say not to flash any ROM on the OF1 of OC1 kernel. I have tried a few that were and weren't trouchwiz compatible and with all of them they bricked my device and it was really a pain to undo it. I would just say to steer clear of any ROM flashing until a dedicated post comes out for it with someone who's a bit more knowledgeable on the topic for the S4 with the OF1 kernel. Until then sorry but I don't have any definitive answer and I would recommend not trying anything due to the fact that you could SERIOUSLY mess up your phone.