{***WARNING****WARNING*** } For SHV-E160L Models Only! You have been WARNED.
Link Online at bottom of post
Hi All,
Well i've been working on this for a while and finally decided i would consider release on what is done so far.
May I Present
Dakrpsr1te's Cherry Rom for SHV-E160L on JB JMA3 leak. MB2 NOW
This is a beta/test of my rom,a vast amount of testing has been done on my side, now it's time for the world to join in.
It's called Cherry Rom as it's my first rom ever, From debricking my galaxy Note in November 2012 to releasing my first cooked rom on Feb 18 2013(Actual File will take longer to upload).
For SHV-E160L Models Only, Flash onto the Jelly Bean Leak JMA3
This is a test rom and not recommended for your daily driver phone, Incorrect usage can and will brick you device, you have been warned and I wont be responsable.
It is also recommended you factory reset/clear cache via the TWRP recovery before you first boot, see below.
IF YOU DONT WANT TO FACTORY RESET,DO NOT FOLLOW THIS GUIDE, TESTERS ONLY.
Part One: Collecting Needed Files NOT for users not on Jelly Bean Leak JMA3
Download Jelly Bean Leak for SHV-E160L from Jelly Bean 4.2.1 ODIN TAR file .TAR.MD5
Download my TWRP 2.2.3 from TWRP-2-3-1 Odin Flash TAR DO NOT EXTRACT
Download Odin V3 from Odin V3 NEEDS EXTRACTING
You also Need latest ADB from ADB-Tools.zip NEEDS EXTRACTING
Extract All zips, each to their own folder, Remember where you put those files, we need them soon.
Once you have all the files we go onto part two
Part Two: Flashing
First thing is put your device into Odin Download Mode:-
Remove USB & battery, Replace Battery
Hold Volume Down & Home, Then press power, on first vibration release power
At the Screen showing Korean Text release all keys, Then press volume up.
You are now in ODIN Download mode (Odin in red writing in top left Corner, if the device reboots or does not show ODIN, try again from the battery pull)
Load Odin V3, and select PDA button, browse to where you extract the Jelly Bean .TAR file ( remember you have to unzip the download Jeall Bean Kies file to produce a dot .tar.md5 )
(NOTE: some users cannot flash with the .tar.md5 file, some version of odin reject it too, in this case remove/rename the .md5 extension so it's only .tar)
then select PHONE button and browse to where you placed TWRP .tar file and select that
you should end up with this screen or similar :-
{
"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"
}
NOTE: I added twrp to phone as the way odin does its flash is as such :-
Bootloaders flashed first
PDA flashed second
PHONE flashed third
CSC Fourth
UMS is final flashed file
so even though the .TAR kies odin flash is written, our PHONE flash file (TWRP) is flashed after, therefore overwriting out factory recovery.img in the ODIN tar file.
Then click Start, when you see recovery.img for the second time get ready to hold VOLUME UP & VOLUME DOWN, When the device says RESET OK, hold down those buttons,
The device should now boot directly into twrp, from the main screen select wipe, then factory reset. Once factory reset complete press the back arrow (The on screen back arrow, Not device's back button)
You will now be back at the main screen, now press ADVANCED
Now click on the start menu, type CMD and press enter
at the Windows C:\ Prompt type
cd \folder-to-where-you-extracted-ADB-Tools
then type
adb sideload "pathtowhereyouextracted-cherry-rom"
An Example
Code:
C:\Users\darkspr1te>cd desktop\adb-tools #enter#
C:\Users\darkspr1te\Desktop\adb-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
cfcXXXX sideload
C:\Users\darkspr1te\Desktop\adb-tools>adb sideload e:\cwm-build\Android\releases\darkspr1te-cherry-rom-release.zip #enter#
sending: 'sideload' 33%
now on your device press ADB Sideload, after a short time, you will get activity on TWRP display screen
Code:
[COLOR="Gray"][SIZE="3"]*******************************
Install darkspr1te-JB-ROM
******************************
Beta Rom - Plenty of bugs[/SIZE][/COLOR]
after a short time you will the see the reboot screen, press reboot and we are DONE!!!!
For users already on Jellbean, you can just follow the ADB side load instructions.
for users with issues's running ADB sideload then you will need to use adb push to transfer the cherry-rom zip file to your phone, in recovery mode /emmc/ is your internal data/sdcard and /sdcard/ is your external sd-card if you have ones installed, you will then just select install zip.
If you are having issues with above instructions, then please read the FORUMS BEFORE YOU POST QUESTIONS THAT ALREADY HAVE BEEN ANSWERED!!!
Well I hope you find my first attempt at a cooked/fixed rom a worth while effort, it's been a good lesson in learning the structure of android, apk, java and more.
Fixes/Patches Log:
deodex
zipaligned
sms fix
water ripple gs3 effect
init.d with domscript v1 (auto zipalign on boot plus others) domscript thread
debloated
installer
boot.img patched for tweaks & init.d
build.prop tweaks
whatsapp
svoice
rooted
su binary
busybox
xda forum reader
photo-editor
known bugs:-
strange Korean icon on desktop, cannot trace to apk
korean dialer
User applied tweaks :-
Code:
goto phone dialer
dial [SIZE="3"][COLOR="DarkOrange"]319712358[/COLOR][/SIZE]
password is [SIZE="3"][COLOR="DarkOrange"]0821[/COLOR][/SIZE]
Select PSVT settings, then IMS PSVT settings,
scroll to Enable IMS on Wifi and set to 1, this enables Video phone over wifi
and disable the "video telephoney over wifi is impossible" message
Dialer Codes:-
*#2663# touch firmware
*2767*3855# [SIZE="4"][COLOR="Red"]factory format do not use[/COLOR][/SIZE]
##DATA# Data config menu
##TTY# TTY menu
##786# RTN repaired menu
*#46744674# set IMSI to 9999
*#9090# Service Mode , MDM/MSM Uart/Usb selection
##8778# PhoneUtil , MODEM/PDA UART/USB
*#0*# Test menu 1
*#0228# battery status
##GPSCLRX# - Reset the GPS
*#2664# - Touchscreen Accuracy Test
*#9900# - SysDump
Bug reports/Suggestions via this thread.
Go easy on me, I just popped my Cherry-Rom
Enjoy
darkspr1te
NEW!! ROM!!
LINK ONLINE
SHV-E160LMB2
Darkspr1te's Cherry ROM MB2 for Vanilia Jelly Bean Install's
I will update the info later, time for bed, it's 1Am here and i wanted to get this out
This is a beta rom so expect a few niggles, I will produce patches later that will fix the minor stuff,
Ive not done much in the way of speed tweak, I also recomend you reset to factory, install Jelly Bean .tar file from odin first and then flash this file
It's a multipart .rar file, use win rar to reassemble, the flash the zip file using adb side load
if you cant sideload then copy to the device.
Recommended Steps For Flashing.
Put phone into download mode
In odin select Your valila copy of the kies update and put in PDA option box
then select the posted TWRP and put in phone.
click start to flash and watch the progress,
AS SOON AS IT finishes the flash with writing the second recovery image hold down VOL UP AND VOL DOWN for the reboot, the device is now in recovery with twrp
you can either do adb sideload (choose advansed on main menu) to apply the patch or adb push and place on the sd-card (Note in recovery the phones internal memory is /emmc and the sd-card is /sd-card , so it you dont have a sd-card inserted you must use adb push filename.zip /emmc/)
once the file is sideloaded ( or installed via twrp install menu option for adb push users)
then do a factory reset once more.
Enjoy your Cherry ROM
Cherry Rom Single Download Link updated 26/may/2013
Many thanks to @awesomefireduck for the upload and setting up a place to store our beloved roms.
SHV-E160L Original Kies Rom (AKA Vanilla Rom)
SHV-E160L Original Kies Rom Mirror (AKA Vanilla Rom)
Latest ADB in 7zip
{***WARNING****WARNING*** } For SHV-E160L Models Only! You have been WARNED.
{***WARNING****WARNING*** } For SHV-E160L Models Only! You have been WARNED.currently photo editor is broken, will resolve and patch it before final upload.
Reserved for changelog
tweaks list and more
reserved for screen shots
others
Re: [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom
Ayyeee! a new ROM awesome!
Sent from my SAMSUNG-SGH-I717 using xda premium
Re: [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom
OPGT said:
Ayyeee! a new ROM awesome!
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Not compatible with at & t i717.
Sent from my SHV-E160L using Tapatalk 2
Re: [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom
darkspr1te said:
Not compatible with at & t i717.
Sent from my SHV-E160L using Tapatalk 2
Click to expand...
Click to collapse
I know. Just like seeing rom development in our section.
Sent from my SAMSUNG-SGH-I717 using xda premium
Re: [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom
Wow another 4.2 ROM
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Re: [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom
Every patch I've applied to this ROM is portable to i717 ROMs too, technically they are the same chip sets, they differ in modems mainly. I've opened up a lot of technical info into the structure of the i717 and its counterparts.
See my signature for a link.
sent from the Darkspr1te's lair
{***WARNING****WARNING*** } For SHV-E160L Models Only! You have been WARNED.
Members there will be a WARNING put into place, and as usual the chance is always on the individual Member on flashing or tweaking anything on/to their device.
That is why one should do their homework before flashing anything. Thank You.
BTW there is not a forum in place for this model device, due to not having enough Users to compile a Forum, this is the XDA Staffs call, so lets just move on if you do not have this device then you do not need to worry about this Thread. The Users of this device have been doing just great with in the Note Forums here, so carry on with Development. Again Thank You.
Re: **WARNING** [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom **WARNING** SHV-E160L Models On
The title says 4.2.1 but the screen shot shows 4.1.2
Sent from my SAMSUNG-SGH-I717 using xda premium
So this is a rom that runs on korean Notes correct? Sucks that not to many people have them, and it really sucks that there is a leak of jelly bean to Korea and not the US......Sigh:fingers-crossed:
Looks like you put a lot of work into this though, hope some ports or something of that nature happen down the road.
Re: **WARNING** [ROM][4.2.1]SHV-E160L-JMA3-Cherry Rom **WARNING** SHV-E160L Models On
Over seas gets the best first. Even over seas get the best apples. Thats no joke
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Will this work on my GF's Galaxy note E160S SKT model ?
As far as i know the S,K,L are just for different networks.
As she says ' I need the update'
Re: **WARNING** [ROM][4.1.2]SHV-E160L-JMA3-Cherry Rom **WARNING** SHV-E160L Models On
punkmonkey1984 said:
Will this work on my GF's Galaxy note E160S SKT model ?
As far as i know the S,K,L are just for different networks.
As she says ' I need the update'
Click to expand...
Click to collapse
No this so only for the L model, please don't flash to S / K models.
see here why you dont flash s/k onto l
http://koxda.com/thread-109693-1-1.html
sent from the Darkspr1te's lair
Re: **WARNING** [ROM][4.1.2]SHV-E160L-JMA3-Cherry Rom **WARNING** SHV-E160L Models On
chris41g said:
The title says 4.2.1 but the screen shot shows 4.1.2
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Sorry I was tired, fixed to reflect 4.1.2.
sent from the Darkspr1te's lair
Re: **WARNING** [ROM][4.1.2]SHV-E160L-JMA3-Cherry Rom **WARNING** SHV-E160L Models On
Ltilt2 said:
Over seas gets the best first. Even over seas get the best apples. Thats no joke
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Click to expand...
Click to collapse
Ha ha ha,
sent from the Darkspr1te's lair, which is a mud hut in Africa.
Thank you darkspr1te....
Your work has been amazing in support of the Korean note.
I will get this thread added into the Korean users section of the super thread..
Thank you !!.....g
can this be also done using CWM and not TWRP recovery?
or should i flash TWRP first in order to install this rom..
currently im on JB leak with CWM touch recovery..
maestrobarako said:
can this be also done using CWM and not TWRP recovery?
or should i flash TWRP first in order to install this rom..
currently im on JB leak with CWM touch recovery..
Click to expand...
Click to collapse
I see that your carrier has ZM.. are you from zambia dark?
Re: **WARNING** [ROM][4.1.2]SHV-E160L-JMA3-Cherry Rom **WARNING** SHV-E160L Models On
maestrobarako said:
I see that your carrier has ZM.. are you from zambia dark?
Click to expand...
Click to collapse
Yes, born and bred in Zambia.
sent from the Darkspr1te's lair
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,
Ok guys with itchy hand me included =_="
This guide is for those who know what I'm talking about, and since ICS kernel with CWM is under its way soon. but we just dont want to make our lovely dev stop making new rom.
This thread originally made for Sola but i think the others will also work if you know what to do and what i mean.
well... I've tested this many times and its ok to flash kernel and also ok to jump from one to another.
!!!disclaimer!!!
!!!with this guide you are the one responsible on what you did to your phone bricking it included, not me or anyone else!!!
We have everything in our hands already.
things needed to make this happen
-A working fastboot
-ANY working kernel with CWM
-Stock kernel
grab that stock ics tft file and open archive using 7Zip and rip that kernel.sin
-remember this... POWER + Vol-up wait for the 3 combo vibrate is force POWER OFF <-- unless you can pull out your battery
-and the rom that you want to test
now lets get things moving
1. power off your phone and put it into fastboot mode "vol-up + usb to pc" purple LED
2. flash your favorite gingerbread kernel with working CWM
fastboot flash boot [NAME OF KERNEL+CWM.elf]
3. unplug the phone and power on. wait for LED light than press "vol-up" to get to CWM
4. if you have not copy the rom, this is a good time to visit mount usb and do your things.
5. wipe data.
6. flash your test ROM
7. after the zip have been completely flashed in to the system. dont bother to reboot phone. instead
8. FORCE power off by holding "vol-up and power button" wait for the 3 combo vibrate. now the phone is OFF.
9. put phone into fastboot mode "vol-up + usb to pc" purple LED again
10. flash that kernel.sin that you rip of from the whole tft... the ICS stock kernel
fastboot flash boot kernel.sin
11. power on and wait the first boot that take ages
12. there you are.... A new test rom
14. Give feed back to ROM dev
note: if it got stuck at Sony logo, where you should expect animation boot screen. force power off and on it again to test. and wonder did you flash the rite kernel.
note2: I'm not putting links as you should know where to get the stuff above. give them proper thanks by hitting the thanks button or donate beer for them if you can.
--------------- Added entry -----------------
* if you lost root, try Bin4rys method to trick the phone that in need to restore the root function<-------- updated 5th oct 2012 >__<
-----------------------------------------------------------------------------------------------------------------------------------------
This will be a big one.... <--------5th OCT 2012
-----------------------------------------------------------------------------------------------------------------------------------------
OK guys, I'm on a windows7 64bit machine and i'm not a linux guy...
the next entry will try to smooth the process and have lots of future use
------------------------------------------------------------------
only for your pc side
------------------------------------------------------------------
things to do
1. add system path
2. ease of access your cmd ^^
3. some batch file ideas that automate things
you should have known this as it have been floating around in xda,
skip this if you dont need it.
-----------------------------------------------------------------------------------
WARNING, we are going to touch some windows stuff,
try not to mess up. but if you do mess things up you are
the one responsible for it ^^
-you are here to learn something. try not to copy paste.
------------------------------------------------------------------------------------
1. add a system path
here's some basic and recap that's have been around xda.
set your windows system variable for ease of command key via your local cmd.
we need a place to start. as i know most of you have installed flashtool. flashtool have a good set of adb and fastboot within its folder.
where else if you want to use android sdk's folder thats up to you to look for the adb and fastboot folder.
here's the location of flashtools adb and fastboot "C:\Flashtool\x10flasher_lib" on my machine <----- yours might be different
we are going to add "C:\Flashtool\x10flasher_lib" into the system path
So, where is it??? (i'm on a windows 7 so you have to figure out where it is ok... )
from the control panel look for system,
In the System window, on the left panel click on the Advanced System Setting.
a System Properties window will pop up
In the Advanced section, click the Environment Variables button.
Finally, in the Environment Variables window (as shown below), highlight the Path variable in the Systems Variable section and click the Edit button. Add or modify the path lines with the paths you wish the computer to access. Each different directory is separated with a semicolon as shown below.
e.g (the ones below is mine... dont follow you should have yours)
C:\Program Files (x86)\AMD APP\bin\x86_64;C:\Program Files (x86)\AMD APP\bin\x86;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\QT Lite\QTSystem;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Flashtool\x10flasher_lib
{
"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"
}
so, in this path property click the "Edit" button, go to the end of the whole string.... and add a semicolon( ; ) and paste the address of where adb and fastboot located
and continue to 'OK' and close the rest of the windows that you dont need.
to test, press this combo [window key + "R"] to have to run windows up and just type cmd and hit ok
in the cmd try just type adb... and it'll give you feed back that just adb is not enough and throw you a list of things adb can do.
now you can fire up adb and fastboot anywhere you want.
2. ease of access your cmd ^^
make a cmd shortcut that will start at the current folder and also run as admin
as you will now go to the folder where you most likely do flash something or adb something
right-click on an empty space and hit new ---> shortcut.
Type the location of the item:
cmd
click next and finish..
now you have a cmd shortcut that only start in the system32 folder...
than we got 2 more things to do with this short cut before its usable.
1.right click the new cmd shortcut and hit properties
EMPTY the "start in:" text box, you want it to start anywhere the short cut is located.
2.still in the same properties and hit the "Advanced..." button and activate "Run as administrator"
OK than apply... you are done. now you can copy paste this short cut any where you want with proper use .
3. some batch file ideas that automate things
the good thing about adb and fastboot.. it will wait for your device. thus automating things can give a good approach.
bare in mind that automation is a good thing. but if you have multiple device. be careful dont automate the wrong command
we call a [something].bat file a [something] batch file...
with the "path" to your adb and flashtool done earlier, you can start making batch file to auto mate things in any folder you wish. just make sure all the other ingredient are in the same place or you can link it to. Bin4ry root tool that you just had is a good place to learn and i'm sure there are other tutorial floating in XDA... just use the search or ask GOOGLE for it.
and you can always right click and add a new ---> text document
fire up notepad and start writing automated fastboot comand or adb install "stuff"
and save as ".bat" file.... you should know what i mean. NOT "filename.bat.txt"
File name: [something].bat
Save as type: All Files
eg: a batch file "flash stock ICS kernel.bat" and "kernel.sin" MUST in the same folder where this batch file located
Code:
@echo off
COLOR 0A
fastboot flash boot kernel.sin
ping 127.0.0.1
PAUSE
echo device will boot after ping
ping 127.0.0.1
fastboot reboot
PAUSE
eg: logcat.bat
Code:
adb logcat
PAUSE
to exit the logcat press Ctrl+C
it will ask you if you really want to stop.
i add a ping 127.0.0.1 just to make a ping delay so that we can see the batch have done the fastboot and do other job like ping local host
4 times and proceed to fastboot reboot. PAUSE if you want it to wait it for you to hit any key than proceed. COLOR 0A to make things green.
there are many more to learn.
NOW... SOMEMORE OLD SCHOOL FUN ^_____^ batch files..... i love them and so will you
------------------------------------------------------------------------------------------------------------------------------------------
----------------------------------------------------
Last but not least, I would like to thank Koush who made CWM. next i want to thank the DEVs here who spend there time making good kernel with CWM. AND also ROM developers who made our android so fascinating! and those of us with itchy hands that made this forum fun and alive. and rohit3221 for lightning fast upload the ICS tft
LETS HAVE SOME FUN with OLD SCHOOL STYLE >_<
ouch!!!
@cooleagle OR E.Cadro- please send this thread to Xperia S, P, U, Sola, Acro S General. I think this tutorial fit as the others will be going trough the same process...
the only different is that some phone can take there battery out to force power off. This should also work for JB if theres no JB+CWM kernel. since CWM have nothing to do with the kernel or how the phone is running... its just a recovery part of the phone that should be there in the first place but Sony just didn't prepare us a recover partition..
psyionx said:
Ok guys with itchy hand me included =_="
This guide is for those who know what I'm talking about, and since ICS kernel with CWM is under its way soon. but we just dont want to make our lovely dev stop making new rom.
This thread originally made for Sola but i think the others will also work if you know what to do and what i mean.
well... I've tested this many times and its ok to flash kernel and also ok to jump from one to another.
!!!disclaimer!!!
!!!with this guide you are the one responsible on what you did to your phone bricking it included, not me or anyone else!!!
We have everything in our hands already.
things needed to make this happen
-A working fastboot
-ANY working kernel with CWM
-Stock kernel
grab that stock ics tft file and open archive using 7Zip and rip that kernel.sin
-remember this... POWER + Vol-up wait for the 3 combo vibrate is force POWER OFF <-- unless you can pull out your battery
-and the rom that you want to test
now lets get things moving
1. power off your phone and put it into fastboot mode "vol-up + usb to pc" purple LED
2. flash your favorite gingerbread kernel with working CWM
fastboot flash boot [NAME OF KERNEL+CWM.elf]
3. unplug the phone and power on. wait for LED light than press "vol-up" to get to CWM
4. if you have not copy the rom, this is a good time to visit mount usb and do your things.
5. wipe data.
6. flash your test ROM
7. after the zip have been completely flashed in to the system. dont bother to reboot phone. instead
8. FORCE power off by holding "vol-up and power button" wait for the 3 combo vibrate. now the phone is OFF.
9. put phone into fastboot mode "vol-up + usb to pc" purple LED again
10. flash that kernel.sin that you rip of from the whole tft... the ICS stock kernel
fastboot flash boot kernel.sin
11. power on and wait the first boot that take ages
12. there you are.... A new test rom
14. Give feed back to ROM dev
note: if it got stuck at Sony logo, where you should expect animation boot screen. force power off and on it again to test. and wonder did you flash the rite kernel.
note2: I'm not putting links as you should know where to get the stuff above. give them proper thanks by hitting the thanks button or donate beer for them if you can.
Last but not least, I would like to thank Koush who made CWM. next i want to thank the DEVs here who spend there time making good kernel with CWM. AND also ROM developers who made our android so fascinating! and those of us with itchy hands that made this forum fun and alive. and rohit3221 for lightning fast upload the ICS tft
LETS HAVE SOME FUN with OLD SCHOOL STYLE >_<
ouch!!!
@cooleagle OR E.Cadro- please send this thread to Xperia S, P, U, Sola, Acro S General. I think this tutorial fit as the others will be going trough the same process...
the only different is that some phone can take there battery out to force power off. This should also work for JB if theres no JB+CWM kernel. since CWM have nothing to do with the kernel or how the phone is running... its just a recovery part of the phone that should be there in the first place but Sony just didn't prepare us a recover partition..
Click to expand...
Click to collapse
nice trick...
ouch....
forgot to stress Nandroid backup as do your things at #4
psyionx said:
... combo vibrate is force POWER OFF <-- unless you can pull out your battery ...
Click to expand...
Click to collapse
This threat is under sola Android development ... And The battery of Sola (as far as i can see ) is sealed (mine is)
BTW: NICE TRICK
Moved to General per op's request
Sent from my Nocturnalized One XL using Forum Runner
Dude what if i install a GB ROM with a Kernel supporting CWM first..... then flash the ICS custom rom via CWM... then when the device is off connect it with the flashtool in flashmode and flash only by selecting the kernel.sin file from the official firmware ( given that the official ics rom is in the firmware folder) it should work..... do u have any opinion??? its may save us from unzipping and fastbooting (2nd time).....
pulak861 said:
Dude what if i install a GB ROM with a Kernel supporting CWM first..... then flash the ICS custom rom via CWM... then when the device is off connect it with the flashtool in flashmode and flash only by selecting the kernel.sin file from the official firmware ( given that the official ics rom is in the firmware folder) it should work..... do u have any opinion??? its may save us from unzipping and fastbooting (2nd time).....
Click to expand...
Click to collapse
yup, it'll work.
you'll have the option to wipe data and the other stuff came with the tft packages...
ok.... i'll add something on the "added entry" to speed things up... hope you guys can catch what i'm trying to pass...
stay tuned... [fingers crossed]
1. I flash a gingerbread kernel with CWM on my XPERIA U running ICS.
2. I fastboot or flash mode flash kernel.sin from the ICS ftf.
3. When done I'll have the ICS firmware with ICS kernel with CWM recovery.
Is that right?
Tapatalked !
Rapier07 said:
1. I flash a gingerbread kernel with CWM on my XPERIA U running ICS.
2. I fastboot or flash mode flash kernel.sin from the ICS ftf.
3. When done I'll have the ICS firmware with ICS kernel with CWM recovery.
Is that right?
Tapatalked !
Click to expand...
Click to collapse
I don't think you will have CWM with ICS kernel.When you flash ICS kernel CWM will be gone.
Rapier07 said:
1. I flash a gingerbread kernel with CWM on my XPERIA U running ICS.
2. I fastboot or flash mode flash kernel.sin from the ICS ftf.
3. When done I'll have the ICS firmware with ICS kernel with CWM recovery.
Is that right?
Tapatalked !
Click to expand...
Click to collapse
nope.... like other android phone... they have another partition called the recovery partition. Some phone like the one we have Xperia does not have this special partition. Sony Ericsson than Sony just didn't give us this partition.
normally we will just fastboot flash recovery [cmd-recovery] and we have a cmd recovery replacing the ones given.
but we dont have this recovery partition.
thus what the dev here came with the idea to cook the recovery with kernel together. And we have a working recovery side by side with kernel in boot partition.
in the early days of xperias.... i remember Xrecovery is cook into the system. well... i do hope this will turn up since building a kernel+recovery need kernel sourcecode. where else Xrecovery need to change some file in android system to make it accessible from boot.
i did try putting xrecovery in system folder along with the other files. and boot the phone with my fingers at the [back] touch button. the phone just hung there. thus it need further changes to make it work.
Also using the wrong kernel is quite regularly known to brick phones, so be careful not to turn it on without the correct installed!
Sent from my LT26i using Tapatalk 2
Ben36 said:
Also using the wrong kernel is quite regularly known to brick phones, so be careful not to turn it on without the correct installed!
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
well... if you put it that way. There's always a risk...
eg, the accidental USB unplug or thouse usb cable that you just need to twist the cable to get a connection really need to avoid... place your phone somewhere safe while working. and Keep cats away.... they just likes wriggling wires.
^ __ ^
I think you'll be fine as long as you don't turn it on to boot up with the wrong kernel. Lol
Sent from my LT26i using Tapatalk 2
Ben36 said:
I think you'll be fine as long as you don't turn it on to boot up with the wrong kernel. Lol
Sent from my LT26i using Tapatalk 2
Click to expand...
Click to collapse
did that many times.... it'll just get stuck and loops....
unbrick by flashing the correct ones ^ ^
Will this method work for locked bootloaders?
kevin.26 said:
Will this method work for locked bootloaders?
Click to expand...
Click to collapse
no
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
LGNPST E970 TeenyBin
DO NOT USE THIS ON NEXUS 4 CONVERTED PHONES!! BRICK CITY
TeenyBins do not help restore your N4 converted phones either.
Don't give me all the credit. Just as much goes to artlan for figuring out the tables and table offsets.
Special thanks to xonar_ for his LG Bin Firmware Extractor and releasing his source code.
Thank you Shelnutt2 for everything you do for the entire LGOG community.
Thank you k7raid for testing the first bin with major SBL changes.
And last and also least.. ha ha.. sawdey21 for suggesting the "updated" name change.
TeenyBin. Patent Pending.
Be sure to show them all thanks.
Background
After seeing tons of soft bricks on both the forums and IRC we have decided to look into how LG .bin files work. We've "cracked the code" and have been able to rebuild the .bins.. making the repair process both faster and easier. Normally the user must download a large .tot/.bin file(1GB+) to repair the phone. After a long download and 5+ minute LGNPST flash the phone is then completely stock... requiring a "re-root" and running the FreeGee unlock again.
TeenyBins are meant to do the bare minimum... fix your soft bricked LG OG and get you back into your rom.. or custom recovery to flash a new rom. These new .bins are as small as 32MB depending on what we build into the .bin. This means smaller files, shorter download times and a phone that's back up and running within minutes.
Other perks include...
Unlocking the bootloader.
SBL partitions safely flashed.
Preinstalled TWRP Recovery.
RPM/TZ partitions safely updated to support the latest AOSP roms.
Directions
E970 TeenyBins will quickly repair your soft bricked device. They will also unlock your phone, install the latest TWRP recovery and update your RPM/TZ partitions... which are needed to run the new AOSP roms based on the Mako kernel. These .bins are safe for any E970.
1. Download TeenyBin .zip and extract. You are going to use the .bin file inside along with LGNPST. LGNPST can be found in the "Additional Info" section at bottom of this post.
2. The TeenyBin LGNPST flash should take 30 seconds or less... your phone will reboot at either 67% or 85%. The flash is complete. All finished.. maybe...
3. Your phone still may not boot up!! If so you must reboot the phone.. boot into fastboot. No fastboot still? Flash the TeenyBin "AltBin" instead!!
4. From fastboot, boot into recovery. In recovery you can flash a rom. All fixed.
5. Nothing working? You're doing it wrong. Did you read this entire post... including everything under the "Additional Information" section at bottom?
Fastboot = Volume up + power
Recovery = once in fastboot.. press volume down, pause, volume down then power button
TeenyBins
These TeenyBins will repair a soft brick, unlock the bootloader, install custom recovery and upgrade rpm 'n' tz.
Remember to try the AltBin if the normal TeenyBin doesn't work. If you can't boot.. fastboot has to work. If you can't get to fastboot you're doing it wrong.
Fastboot = Volume up + power
Recovery = once in fastboot.. press volume down, pause, volume down then power button
DOWNLOAD:
E970 Original TeenyBin - This is the default TeenyBin every E970 user should LGNPST flash
E970 Original TeenyBin[AltBin] - Use this TeenyBin if your E970 still can't boot or get to fastboot
Current included recovery: TWRP 2.5.0.0 - Thank you Dees_Troy!
Additional Info
Q: Can you make *custom .bin here*?
A: Maybe... but I am lazy so make a good point.
Q: I flashed the small bin and still can't boot back into my phone.
A: First of all... it's a TeenyBin... but anyway.. booting directly back up into the rom may not always be possible. Your /system or boot.img may be damaged. You were soft bricked remember... how do you think the soft brick happened? In this scenario you will have to reboot into fastboot.. then enter recovery... and reflash a rom .zip
Q: How do I know if I'm soft bricked or perm bricked?
A: For most soft bricks you will see a LG or Google logo and then a black screen. You can also still get into download mode. If you think download mode may not even work, connect phone to a Windows computer and check device manager... if the phone is detected in a "QHSUSB-DLOAD" then there's a good chance you're perm bricked. Otherwise.. you may just be a n00b and aren't doing download mode correctly.
Q: Where's that LGNPST info you mentioned?
A: Hit the "Show Content" button below
LGNPST Guide
DO NOT ASK HOW TO USE LGNPST OR A VIRTUAL MACHINE IN THIS THREAD.
THIS IS A TEENBIN THREAD. THE FILES AND GUIDES BELOW ARE A BONUS ONLY. RESEARCH. READ. APPLY.
Downloads + basic guide HERE
Update - added a virtual machine with pre-installed LGNPST to the link above. This will be for those that aren't on Windows.. or just having install issues. Thanks to k7raid for that! Some files may need a password to extract... PW = lgog
BELOW IS A MORE DETAILED GUIDE FOR THOSE CONFUSED OR STUCK.
READ IT ALL AND MOST QUESTIONS SHOULD BE ANSWERED
{
"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"
}
Notice at the top it says LGNPST ACG and not some other weird version? And notice the version numbers. If yours don't match up then you installed the wrong version!!
1. COM port will show up if phone is connected properly in Download Mode. LGNPST will switch and say Emergency Mode.
2. Press the DLL button towards the bottom of Emergency tab.
3. Press the BIN button towards the bottom of Emergency tab. You should now see both both file names scrolling in LGNPST like the screenshot.
4. Press that START button.
5. A windows will pop up saying you will lose data.. you will NOT lose any personal data.. hit OK.
6. If LGNPST is working properly it will take 20 seconds or so before LGNPST hits 67% and reboots your phone. DONE. After your phone reboots at 67% or 85% it's safe to unplug and use phone.
7. If you still can't boot up, try booting into fastboot. Can't get into fastboot.. try flashing the AltBin. Still can't get into fastboot? you're doing it wrong.
Q: LGNPST Won't open and says "usb dongle not detected"
A: In the lgnpst folder where u ran the .bat to install it should be a lgnpst_acg.exe file somewhere. Copy it to your program files > lg electronics > lgnpst folder overwriting the current exe in that folder. Should work now.
Q: There's no LGNPST_LS970.dll file to select in LGNPST.
A: The install.bat should have registered your dlls but something went wrong. Check the link in the next answer.
Q: I still can't install LGNPST... help?
A: Check out this link.
Code:
[B]My other E970 thread..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2161611"][GUIDE] Backup/Restore LG Optimus G EFS Partitions[/URL][/B]
[B]My other LS970 threads..[/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2161498"][GUIDE] Backup/Restore/Repair Your EFS Partition [LS970][/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2049701"][HOW-TO] Enable DIAG mode without Service Code(MSL)[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2052816"][INFO] LS970 Hidden Dialer Codes[/URL][/B]
[B][URL="http://forum.xda-developers.com/showthread.php?t=2058506"][INFO] Optimus G AT Commands[/URL][/B]
Fantastic work!
Could this be used to add the 20j partitions to a phone that doesn't have them, rather than going the whole flash using 20j.TOT, rooting and FreeGeeing? Or is that still the recommended method?
Woot because TeenyBin's are awesomes.
artlan said:
Woot because TeenyBin's are awesomes.
Click to expand...
Click to collapse
And hellacoolz
This is very awesome. Thank you for posting this!
shrike said:
Fantastic work!
Could this be used to add the 20j partitions to a phone that doesn't have them, rather than going the whole flash using 20j.TOT, rooting and FreeGeeing?
Click to expand...
Click to collapse
yes! it add's the 20j RPM and TZ (needed for new AOSP roms)... it also adds the unlocked bootloader and custom recovery just like FreeGee. Although, FreeGee also flashes a boot.img. Our TeenyBin does not include boot.img due to the different roms people may be on.
What this means is... if you are on a 100% stock LG rom(not a custom rom or custom AOSP rom) and flash the TeenyBin.. you will not be able to boot right back into your stock rom... but you WILL be unlocked and be able to boot into both fastboot and recovery. From recovery you could flash a rom. I have assumed that most people using this are not on a 100% stock rom.. or at least do not care about booting back into the stock rom after unlocking.. since we all just want to flash custom roms, right? And being on ANY custom rom(LG-based or AOSP) will have no issues booting back into the rom(due to already having a pre-patched boot.img).
I suppose I can make a flashable zip for this exact situation I've described above. In the rare case that you run this TeenyBin on a 100% stock rom, can't boot back into the rom and do not wish to flash a new rom in recovery.... you can..
Boot into fastboot..
From fastboot.. boot into recovery..
flash the modified-boot-img.zip in recovery.. reboot and you'll be back into your 100% stock rom.
Phew.. got all that?
question about n4 conversion. if coming from n4 conversion, would this be recommended to flash after lgnpst'ing back to 11c? since when you OTA 20j camera is broken.
EDIT: i will be supplying autoprime with all the original partition tables for att lgog. he's going to look into possibly creating a zip file fix that will allow n4 converted att lgog's to refresh the original partitions so that hopefully 20j's camera and storage issue get fixed more reliably.
This... is badass! Thank you all so much! I love you guys (no homo).
Sent from my badass LG Optimus G
Tried to install TeenyBin (mako) on slickrom jb using cwm and install fails both on internal and external sd card. Does this only work with twrp?
Sent from my LG-E970 using xda app-developers app
freebee269 said:
question about n4 conversion. if coming from n4 conversion, would this be recommended to flash after lgnpst'ing back to 11c? since when you OTA 20j camera is broken.
EDIT: i will be supplying autoprime with all the original partition tables for att lgog. he's going to look into possibly creating a zip file fix that will allow n4 converted att lgog's to refresh the original partitions so that hopefully 20j's camera and storage issue get fixed more reliably.
Click to expand...
Click to collapse
I'm wondering a similar thing, should I lgnpst to stock 10o or 11c, root, etc and do the camera fix, then flash the 20j stock, or use the teenybin(s) for all of these?
cdub50 said:
Tried to install TeenyBin (mako) on slickrom jb using cwm and install fails both on internal and external sd card. Does this only work with twrp?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
I think you gotta LGNPST to flash buddy.
Sent from my LG Optimus Me
Smh
Sent from my LG-E970 using Tapatalk 2
cdub50 said:
Tried to install TeenyBin (mako) on slickrom jb using cwm and install fails both on internal and external sd card. Does this only work with twrp?
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
you didn't read the OP. You do not flash these files in recovery.
C2fifield said:
I'm wondering a similar thing, should I lgnpst to stock 10o or 11c, root, etc and do the camera fix, then flash the 20j stock, or use the teenybin(s) for all of these?
Click to expand...
Click to collapse
TeenyBins are not geared towards any sort of N4/Mako restore. Currently they do not help in restoring from a conversion. TeenyBins are used for unlocking, fixing soft brick and updating RPM/TZ(needed for new AOSP roms). LGNPST doen't touch the partitions that are required for your cam fix.
I suggest you currently stick to whatever previous method was used for restoring from a conversion.
I do want to add... as freebee269 mentioned on Page 1... we will be looking at exactly what is going on with the camera issue. A separate fix outside of the TeenyBin scope may emerge if we are successful. While I do not support the N4 conversion at all... I am interested in finding the easiest/best way to restore back to it's original firmware.
autoprime said:
you didn't read the OP. You do not flash these files in recovery.
TeenyBins are not geared towards any sort of N4/Mako restore. Currently they do not help in restoring from a conversion. TeenyBins are used for unlocking, fixing soft brick and updating RPM/TZ(needed for new AOSP roms). LGNPST doen't touch the partitions that are required for your cam fix.
I suggest you currently stick to whatever previous method was used for restoring from a conversion.
Click to expand...
Click to collapse
Thanks, I appreciate the help.
Sorry missed that will LGNPST using the zip. Thanks for the easiest way to update.
Sent from my LG-E970 using xda app-developers app
Any potential downsides to LGNPST'ing the TeenBin and flashing a ROM rather than LGNPST'ing to 20j, etc?
I'm guessing not, and am REALLY excited to get home and try this.
Thanks for the work!
Digil said:
Any potential downsides to LGNPST'ing the TeenBin and flashing a ROM rather than LGNPST'ing to 20j, etc?
I'm guessing not, and am REALLY excited to get home and try this.
Thanks for the work!
Click to expand...
Click to collapse
Only if you prefer to stay on 100% stock V20j /system... since TeenyBin skips system(the "rom") entirely. If you wanted to flash the stock 20j LGNPST bin ONLY so you could update RPM/TZ then TeenyBins got you covered.
TeenyBin does not flash modem. Do you ATT guys have flashable zips for all your modems? I included them in the Sprint thread but I'm not an ATT E970 user...
If you don't have a flashable V20j modem I can include one in the OP.
The modem, rpm and tz partitions are really all you want out of V20j...
autoprime said:
Only if you prefer to stay on 100% stock V20j /system... since TeenyBin skips system(the "rom") entirely. If you wanted to flash the stock 20j LGNPST bin ONLY so you could update RPM/TZ then TeenyBins got you covered.
TeenyBin does not flash modem. Do you ATT guys have flashable zips for all your modems? I included them in the Sprint thread but I'm not an ATT E970 user...
If you don't have a flashable V20j modem I can include one in the OP.
The modem, rpm and tz partitions are really all you want out of V20j...
Click to expand...
Click to collapse
There is a flashable zip for modem/radio buddy.
Sent from my LG-E970 using xda app-developers app
mikeylikey said:
There is a flashable zip for modem/radio buddy.
Sent from my LG-E970 using xda app-developers app
Click to expand...
Click to collapse
What he said. Thanks autoprime, you answered my question. All I want is 20j rpm/tz so I can flash all these nice AOSP ROMs. I can't wait!
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