SM-T335 Doesn't boot after editing build.prop - Galaxy Tab 4 Q&A, Help & Troubleshooting

Hello,
after trying to enable on screen buttons via adding a line to build.prop (not checking permissions after that) - rebooting - i'm not able to boot into the system anymore. I know now that this was stupid but it's to late..
I'm now downloading DBT-T335XXU1ANDD-20140520101235 and will try to sideload it in recovery. Since i am in ubuntu kies is no real option, but i am used to flash via console and will try that.
What do you think - is there a better way to fix it?
Thanks!
Update 1: I don't get it. How do i flash or sideload the .zip or the unpackend .tar or the unpacked system.img.ext4?

You need Odin

You're right. Only flashing it with Odin helped.

for the newer folks here at XDA ( like recent as of a month or so maybe greater but not exceeding 3 lol ) read read read and read somemore it helps that's were i learned to do this and the in's and outs of phones and tabs google EVERYTHING for ANYTHING literally it's the best used engine that has ever been concepted and widely used so but also the dev's member's such as myself will be more then willing to help out so just let one of us know even if it's not in the respective forum's someone will always help

Related

How To Recover Your Fascinate From Any Brick, And Rooting Methods

HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. Sorry but the links to some of the files are gone I don't have them anymore so I suggest you look through the comments someone will have someplace to get what you need. Your recovery methods may have changed but this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.​
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
This is a great source of information. The formatting could be a little better though. Perhaps break up those great giant paragraphs a bit. It would be easier to follow along. Especially for noobs in a panic state after "bricking" their phone.
Great work though. This should be stickied.
I will Update thread to an easier format over the next few days. Thanks for the tip, i looked good to me but now i see what you are talking about. It took hours today to gather all the info, pull up each program ans walk through it. I guess I was in mental overload.
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
You were that guy.
times_infinity said:
Not trying to be that guy, but the DL01 is actually DI01. The build number DL01 doesnt exist.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Oops, but at least i was consistant on the typo...LOL. I will fix it this weekend.
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Figured out this morning I wasnt using my factory usb cable switched cables odin'd stock eb01 worked perfectly now I feel retarded.
Sent from my SCH-I500 using XDA App
Excellent write up. Thanks a bunch.
What are some other differences in Odin 1.7 vs 1.3? I have used 1.3 many times and never had any issues. Any improvements?
Thanks so much Dale! headed to work now, but will try this tonight
Rayn1328 said:
I just got a fascinate.....commingle from a vibrant.....I can't find a root method that doesn't include a computer,my previous phone I downloaded update.zip went into recovery and bammo rooted then have spent the last unknown amount of time playing with the Roms and now want the same. With this phone anyone help? Thanks.
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
More reasons as to why you should never fear bricking your phone and testing new kernels and ROMs. Thank you for the thorough tutorial.
cbalt said:
http://forum.xda-developers.com/showthread.php?t=897889 you pretty much need a computer. z4root worked at one time iirc I used it on my fascinate at some point.
Click to expand...
Click to collapse
I prefer what i think is a much simpler method. Just go to this link and follow Post 2. I don't believe I have ever had it so easy to root a phone:
http://forum.xda-developers.com/showthread.php?t=948722
nice write up, thanks for posting. I hope I never have to use it
netwalker0099 said:
Attempted Heimdall today after odin has failed using the EB01, error was "Failed to retrieve config descriptor" any ideas?
If I flash with all CSC options unchecked the flash is successful.
When trying to boot after flash without CSC i receive a phone and a computer with a dotted line connecting the to on power up. Phone will return to DL mode.
Also attempted to flash DL01, it seems there are several files that correspond with Heim that are not in the package are the EB01 files interchangeable with the missing files?
Click to expand...
Click to collapse
Got that once cause i didn't install the drivers in zadig. I installed it, didn't reboot PC, worked fine. If you had the CSC unchecked then you didnt install a cache or database, so no your phone wont work like that. Unless you ran into something new, follow this guide step by step, and it should work. I would also make sure you get the files from here, they are tested and known to be good. There are some incomplete, and bad files out there, these work.
Heimdall is officially the greatest piece of software ever created and DaleV is my hero!!! FINALLY have my phone up and running again! Was serious contemplating dropping around $300 for a new phone on Craigslist.
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Oxirane said:
Trying to root a Fascinate, and it showed up in ODIN once, then the flash failed. Now it's in download mode and not showing up in ODIN, any ideas?
Click to expand...
Click to collapse
after it failed did you unplug then replug and go back into download mode? also I updated the OP with a superuser.zip file it works better than the one in the market for showing you have root access, I have no idea why.
Also you might try a different usb port, sometimes that does the trick.
I've unplugged and replugged and rebooted it a dozen times... it first goes to 2e recovery, then I reinstall packages and it reboots to the simplified download mode with just basic little icons. Doesn't get recognized by the computer though. :/
Wont boot into anything but 2e, and from there into oldschool download mode.

Need Urgent Fascinate Help

I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
want a droid said:
I had my girlfriend's fascinate running MIUI and then I flashed CM7. When I booted into recovery it took me into the red one and now I can't do anything. I'm always getting errors. How can I get back to the blue recovery or what can I do?
I can't get past the Glitch screen it just stays on there
Please help
Click to expand...
Click to collapse
Odin the proper clockwork,reboot straight to it, wipe data and then flash CM7 from the SD card.
Please give me step by step instructions with links. I'm an HTC Thunderbolt guy myself so I am having a hard time finding all the right links and stuff. I really appreciate your help!
First sticky in this forum has all the links and steps.
Sent from my SCH-I500 using Tapatalk
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
want a droid said:
I tried flashing the fix all recovery and it's still not working. Again, I appreciate your guy's help.
Click to expand...
Click to collapse
Really? did you look at the sticky?
Code:
HOW TO UN-BRICK YOUR FASCINATE NOW THAT YOU HAVE BRICKED IT
SINCE IT HAS COME TO MY ATTENTION SOME POEPLE ARE CONFUSED ABOUT WHAT PHONE THIS IS FOR, I WILL MAKE IT AS CLEAR AS POSSIBLE
THIS IS FOR THE VERIZON FASCINATE
So you think you bricked your phone? The first thing you need to do is CALM DOWN, NO NEED TO PANIC , the odds are great that following this guide will fix your mistakes and recover your phone.
Sorry Fascinate owners, but I can no longer support this thread. As state below I test everything I post to make sure it works as advertised. I no longer have a fascinate so i can not test anything new. All of the files, I cant guarantee links to other OP's, will still be available, I wont take them down. Your recovery methods have not changed, nor have the PIT files, so this can still be used to recover your device. If you are looking for anything new look at nitsuj17's roll up post here, he maintains it very well so you should be able to find whatever else you need there.
I HAVE PURPOSELY BRICKED MY PHONE BY DOING THE THINGS YOU ARE TOLD NOT TO JUST TO TEST THE CAPABILITIES OF THESE RECOVERY PROGRAMS. UNLESS YOU CAN AFFORD TO HAVE YOUR PHONE REPLACED BY INSURANCE, TRUST THAT I KNOW WHAT I AM TALKING ABOUT.
SECTION 1: ODIN
SECTION 2: HEIMDALL
SECTION 3: ROOTING METHODS
Since there seems to be an abundance of posts in the Q&A and General Forums asking for help fixing, unbricking, their Fascinates, I decided to try to make a one stop walk through for odin and heimdall with links. Most of us "flash addicts", Developers, and testers have found the Samsung Galaxy Phones are nearly impossible to truly brick without causing physical damage to your phone, in almost all cases it is possible to get it working again.This is nothing more than how to get back a working STOCK phone, nothing custom here that's in the Development section. The first section will cover odin, the second heimdall, the third recovery and rooting.
USUAL WARNING: Everything here is done at your own risk. None of us on the XDA Developers site are responsible in any way, after all we didn't brick it you did. Doing any of this is your decision, I am just providing a collection of information. All credit for everything here belongs to others, who worked hard to give you a way to fix your mistakes, and it usually is the owner of the device trying something without learning how first, or not following directions that got you here in the first place.
My Phone wont boot at all, is stuck at logo, or I cant do anything with it is it a paperweight?
Most likely, no, so lets get to fixing it. All download links necessary for each process will be posted in this walk through and have been tested to make sure they work.
SECTION 1: ODIN
Everything except for the pit file in odin MUST be done in the PDA slot, if not it will not work requiring you to odin again, or possibly have to use heimdall (covered later in this thread) to fix that. After you download odin, I use v1.83 but I will provide all versions I have.
First you need to decide if you want to go all the way back to DI01 (Android 2.1 "Eclair") or EB01, EC01, or a little more involved process for ED01, or ED03 (android 2.2 "Froyo") it makes all the difference with the files you need. The pit file is not necessary for most recoveries, but I have included due to a few issues that will require you to completely wipe everything but your SD card and start over. All of this is possible thanks to our talented developers. After you have odin and all the files you need on your Windows Vista or Win 7 PC, This DOES NOT work on XP, I have had a lot of responses to support this, so lets go with it won't work use Vista or Win 7. To load any file you click that button and use the windows explorer pop up to find your file select it and click open at the bottom of the window.
Start by powering off phone, the pull out battery.
Open odin and load your file in PDA and ONLY THE PDA (downloads) section, If you knew enough about this program to use the other areas you would not need this walk through, soPDA and ONLY THE PDA (downloads) section, for an, all in 1 Recovery. If you are doing a non packaged update I suggest installing the rom one first, modems and recoveries are a lot faster install.
If you are repartitioning put the pit file in the (Pit) section,verify repartition is checked.
Plug your phone into a USB slot, then hold the volume down hard key on the side of the phone. You should see a yellow triangle with a construction droid on your phones screen, and a box on the left right above options (ID:COM) is now yellow.
Now you are in download mode, verify check box next to PDA is checked and the block has the file location in it. Make sure Repartition (unless you are repartitioning and have the pit file in place), Dump, Phone EFS clear, and Bootloader, Phone Bootloader Update, and Flash Lock are NOT CHECKED in the Options section. Auto Reboot and F. Reset Time can be checked or not it doesn't really matter with the battery out. These are the default settings in the options section but double check it anyway.
You are ready to go, click start, and let odin run, it can take anywhere from just a minute to around a half hour. If anything happens like your computer shuts off, you accidentally unplug your phone from your PC, or download failed. Don't freak, just do it again from step one, sometimes it takes multiple attempts to get it. I think at six failed attempts in a row it may be time to look into heimdall, the walk through for that is below this one.
Once odin finishes and does its test you will get a green box lit up that says Pass in it just above where you saw the yellow box showing you were connected. Congratulations on a successful recovery. reinstall your battery and the back cover, reboot your phone and wait for it to boot up. The boot process can take several minutes so be patient. If the boot was successful you should be looking at a stock bloated Verizon Fascinate, that is asking you to back up your system and log into Gmail.
Fascinate USB driver from Samsung, just in case you need it.
Sch-i500 USB driver
odin v1.3
odin v1.7
odin v1.83
Atlas v2.2 Pit file
DI01All in 1
EB01All in 1
ODIN CWM ED01 Stock ROM/Kernel/Recovery Courtesy of Imnuts
ODIN ED03 ROM/Kernel/Recovery Courtesy of Imnuts
MODEM ODIN CWM DL09, EA28, ED01, ED03 modems without ridiculous 100MB OTAs Courtesy of Comradesven (I can now say this works and is easy to do just folloy the instrictions on thread.) Decided to try out this method after bricking my phone again, EASY AND FAST, love it.
EC09 Gingerbread Leak CAUTION:It has not happened to me yet even after several times of flashing something custom and using this to odin back to stock with, but there are many reports of this corrupting users SD cards. This is a leak and as always USE THIS AT YOUR OWN RISK!!
Here are the ONLY TWO, as far as we know guaranteed to get you fixed up, odin files, for anyone coming from CM7 or MUI MTD for the Fascinate.
YOU MUST USE THE ATLAS V2.2 PIT FILE, ONE OF THESE FILES, AND REPARTITION. IF YOU DON'T ODIN WILL FAIL TO COMPLETE THE RECOVERY.
CI500_VZW_DL09_ECLAIR
CI500_VZW_EB01_FROYO
SECTION 2: HEIMDALL
Now for the heimdall walk through, so follow along. I don't think it is possible to completely brick this phone short of actually smashing it, why take unnecessary chances.
First go to the link for heimdall. Download, unzip this and open the folder. In this folder you will find another folder labeled Drivers, open it and you will see a program called zadig.
Now put your Phone into download mode, that is remove the back cover, take out the battery and plug it into your PC with the OEM cable (the one that came with the phone when you got it), then press and hold the down volume button till a yellow triangle and construction droid , now you are in download mode.
Double click zadig and when it opens, click on options and click list all devices. Now drop the usb drop down box and you will find an option for SAMSUNG android composite ADB device, or Samsung composite usb driver, select it then click install drivers. the usual install stuff from windows about do you want to install this, yes you do. Now If the warning about publisher could not be verified, whatever, install it anyway, no it's not a virus. Your phone MUST be in download mode or zadig will not have the USB you need as an available option.
Now you need the files for this program to install and recover your phone. I was motivated to set up a zip file for download with files ready due to confusion on how to accomplish this step, you will find links below.
Now back into the heimdall file you opened earlier you will need to double click the heimdall.exe file, and click run on the windows pop up, it will show a cmd prompt type screen then disappear shortly after, it's supposed to do that.
Again in the click the application called heimdall-frontend. here is where you can go wrong so I will do this side by side with heimdall names and DI01/EB01 file names. I don't believe there are currently any other full recoveries.
To eliminate confusion on where to put your files follow the guige below.
Heimdall on this side of =Recovery file names on this side.
In Repartition:
PIT = atlas_v2.2.pit see below.
In PDA/Code:
FactoryFS=factoryfs.frs
Kernel(zImage)=zImage
Param.lfs=param.lfs
Primary Bootloader=boot.bin
Secondary Bootloader=slb.bin
In CSC:
Cache=cache.rfs
Database Data=dbdata.rfs
In Other:
Modem=modem.bin
Recovery=recovery.bin
Now that all the are files loaded into the correct spots, the necessary drivers installed, and phone in download mode, the start button will be able to be clicked, not shaded outlines like before, did you even notice that? If you followed everything in this tutorial step by step, click the START button and let heimdall run. After it finishes reboot your Verizon stock, Bing bloated, WORKING Fascinate. After this is completed successfully you will be able to use odin again if you need or want to.
Heimdall
DI01 heimdall package
EB01 heimdall package
Why did this happen?
Why was this necessary, as far as I can find out, through research, I wont even try to figure out how many times I had to odin ,and the eight, yes that's right I said 8, times I have HAD to use heimdall, because my phone would not recover through odin. Usually because like me you flashed a rom on for a different phone or, it seems to be, dbdata or another partition can not mount. This has happened to me because I didn't remove voodoo, or flashed a pre edify rom after accidently putting cwr3, which is for edify, on a non edify rom. So moral of the story is twofold, yes it is very likely it can be fixed, and remove voodoo before going to nonvoodoo, and make sure you have a version of cwr that supports both ammend and edify script if you are not sure. Don't flash a rom for a different phone on your Verizon Fascinate or you most likely WILL need heimdall.
NEVER USE A FILE, ROM, KERNEL, ANYTHING, THAT IS NOT CLEARLY FOR THE VERIZON FASCINATE.
Remember, thank the developers by clicking the thanks button on threads you find helpful, they did the work. All I did was take some time and put together all the links and processes I have read and had to learn. Some of the walk through threads are well written by the Dev's and some were hard for me to follow. Sometime I wonder if our Dev's forget that us mere mortals have no idea what they are talking about, and I pride myself on being much better than average with computers and software. That said if you have trouble working e mail and office, I think it's fair to say you would be lost. I hope this is easy to follow and always successful for you. Better yet I hope you never need this.
READ:If heimdall, or odin fail, but you can still get into download mode, do it again, and keep trying while you look for further assistance on this site. If you can't get into download mode with your phone plugged into your PC, unplug usb from PC and plug it into the wall outlet, and try to put it into download mode there. When It goes into download mode, unplug usb from adapter, plug it into PC and put it into download mode, This does work.
If this has Helped you not have a $600 dollar paperweight, consider donating to some of our Dev's working so hard to not only give you better than what big red and sammy gave you, but also a way to fix your mistakes without the need for an insurance claim. Isn't it worth a few bucks to support the developers who save you from the insurance deductable? Think about that before you complain about the devs.
SECTION 3: ROOTING METHODS
Here are two easy ways to accomplish rooting your phone.
ROOTING YOUR PHONE VOIDS YOUR WARRANTY. I NOR ANYONE ELSE WILL BE RESPONSIBLE FOR ANYTHING YOU CHOOSE TO DO. NO ONE HERE IS MAKING YOU DO ANYTHING, JUST PROVIDING INFORMATION ON WAYS TO ACCOMPLISH WHAT YOU WANT TO DO.
Super One Click method: unzip file, open file, double click ADB, it will show a quick cmd like window. Now make sure you phone has USB debugging enabled, connect to PC, don't mount USB. Click the SuperOneClick.exe icon and let it run. If it fails run it again, sometimes it does that. If anything pops up on the screen, read and answer. Unless you are using a Captivate leave the Captivate tab alone it is for getting an unlock code and you don't need that for your Fascinate. (works on all fascinate stock OS to include ED03, and EC09 GB, tested by me.)
CWR & SU Method: (DOES NOT WORK ON 2.2.1) Put superuser.zip zip file on root of SD card, odin in cwr, boot phone into recovery by holding power and volume at same time. To do this simply install battery after unpluging from PC press and hold power and volume buttons at the same time. DO NOT let the phone boot as far as the Samsung logo or you will have to odin in cwr again. Go to Install zip, choose zip, install from SD card. Find your superuser.zip file and install it. Reboot, you are rooted, install busybox, free from market if necessary. If you need odin or instruction on using it, see section 1.
GINGERBREAK Method: Gingerbreak v1.20.apk is an easy to do method, put the apk on your sd card, install from file manager, run it.
KEEPING CWR3 IN 2.2.1: To keep CWR on any ED OTA release you need to make some adjustments to a few files. Don't worry I am going to tell you which ones, and I suggest a simple method of adding .no to the end of the file. That way if you ever need to undo it, simply go back in and remove the .no and your not trying to remember what the file name and extension was. Now here are the file names for each file, you will need something like root explorer and a rooted Fascinate to do this, and you can't rename a file unless you tap the mount system as r/w not r/o, its easy here are the examples of how I did it.
/system/recovery-from-boot.p becomes /system/recovery-from-boot.p.no
/system/bin/recovery becomes /system/bin/recovery.no
/system/etc/install-recovery.sh becomes /system/etc/install-recovery.sh.no
Superuser+busybox
CWR 3/30 Fix all
CWR3 Voodoo.tar Blue
times_infinity's recoveries
Gingerbreak v1.20
Special thanks to Adrynalyne, Imnuts, Jt1134, Nitsuj17, Landshark, Sbrissen, ChainsDD, Times Infinity, and Comradesven and anyone I forgot to thank, for creating and sharing, the heimdall, odin, and other files.
Everything you need can be found here: http://forum.xda-developers.com/showthread.php?t=1026746
odin...
atlas_v2.2.pit
CI500_VZW_ED05_FROYO_REL.tar.md5
check repartition
then follow the CM wiki
I don't understand why I'm getting this: http://imgur.com/WkDsK
Sorry for rotated picture.
I'm in the process of flashing the verizon firmware but it's taking forever to download. I thought I could just odin the CWM?
You better do some research before u brick ur ****...there are guides all over the place on how to get back to stock/flash roms. And last but not least all questions should be posted in the q&a section...that's what its there for...seriously use it!
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
When I try to connect it to my mac it says it can't read what I'm trying to connect. When I connected it to windows laptop it says its a CD drive that is write protected.
I can't move any files in or out. Also when I try to flash a rom zip in recovery it doesn't work.
I'm in the process of trying to restore her MIUI backup. Here's to hoping that works.
EDIT: Supposedly the restore worked, but here is part of the error that showed when trying to flash a zip (top text): http://imgur.com/X1RQL
Oh and I'm stuck on the Samsung screen now...what do I do?
want a droid said:
Ok I flashed Verizon firmware, then did the CM Wiki steps, but for some reason my recovery is acting funky.
Click to expand...
Click to collapse
fail.
if you did CM Wiki, you have CWM 4.X, not 2 or 3
you need to flash back to stock like i said
I did flash back to stock. Anyways in the broken clockwork recovery I decided to try and install MIUI again and when I clicked it it took me to an orange recovery.
Then I flashed her backup and it loaded up fine. Hopefully everything is back to the way it was. I'm not sure what ever went wrong in the first place.Thanks for your help.
Dude...sounds like you just made it hard. Its actually quite simple.
Pull battery, put in download mode.
Odin the Verizon firmware with atlas.pit and repartition checked.
let it boot, then shut it back down and go back into download mode and Odin the fixed recovery for CM7. Then flash MIUI and profit.
It shouldn't take but about 15 minutes out so for the whole process
Swyped via Tapatalk
Well I wish you had been here last night. I was told to do the heimdall thing and then after all that the phone wouldn't be recognized in odin.
It was a frustrating 3 hour long process (granted ~1h was waiting for the 441MB file to download).
so I found this thread searching through the fascinate forums and i gotta say, it saved my ass. I used heimdall 1.3.1 and it wasn't working right for the flash. IDK why but when I tried 1.1.1 it worked first try to flash back to stock after brick. I used the eh03_full_odin.zip file in heimdall and it quick and easy to get back to stock =] this forum rox!!

[Q] Xoom files doesnt change

Hello guys,
i got a serious and frustrating problem here.
A few days ago my xoom was stuck on the M screen, so I used a thread in the forum and recovered it.
It solved myh problem back then, but since I had 3.2 before this and the solution injected me with Android 3.01 my problems started to show themselves.
the first one is that
<b> Through Fastboot, RecoveryMod, ADB </b> and any other way you can Imagine to install a new ROM or even remove or create a file,
All of them show success message but when I check them out I see no changes.
i tried fastboot and Recovery to install nearly every ROM,Recovery and bootimage in this site but so far it was wild goose chase.
so I want to ask if I'm doing anything wrong or if you need any more information here, but please help me with this
wow I cant believe it, All these masterminds here and no answer to my distress signal??
Guys I am so in trouble and this is the only place I hoped to get answered.
I can provide you with more info if you need, but please dont say I'm on my own here.
all these years this forum was the last hope for me.
i know I'll get my answer here one day
You are not being very clear about what you have done,, but I'm assuming that you reinstalled the stock image that got you back to HC 3.01. Can you see if you are able to get OTA updates to get you back to at least 3.1, or 3.2 if possible?
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Mohfath said:
If that's my problem forgive me please, Ive written that post in 3:00AM
for the sake of clearity I should add some info:
1. I even tried stock ROMs but you see I cant even flash them (Not from Recovery nor Fastboot) the steps seem successful : it opens the package,it installs them and it says everything was a success. But when I restart the device I see nothing has changed.
2. OTA updates are the same, they keep downloading and when the sysem reboots to recovery to install them it cant find them.
3. You dont believe it if I say even files and programs that I remove from device by my hand(Android OS) are back after the first restart.
And you see it's dark magic! everything from a file to a partition are back by one reboot. I dont know what should I call it but I havent seen anything like it on the whole Internet.
So seems like I should make a competition for the xda experts here
Can you publish it so all of them can see it?
Click to expand...
Click to collapse
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
okantomi said:
Actually, I have seen someone with the same problem here on this forum, but I can't recall exactly what the solution was.
Can you describe, step by step what you are doing, what cable you are connecting to your pc with, etc?
Click to expand...
Click to collapse
That would be relief to know this could be solvable.
I will look more too.
As for your post I must say:
1. I plug the Xoom to the PC using the included cable
2. I start the xoom and start fastboot
3. on the PC system has the drivers and completely knows it
4. I start with SDK:
I. Fastboot oem unlock (Completing onscreen instructions and reboot device)
II. Fastboot mode again I use Fastboot flash boot boot.img
III. Continuing with Recovery,System
IV. Rebooting the device anything is the same.
My ROM is unchanged by the process and keeeeeeeeps giving the damn error of System process error please submit
5. And with ClockworkrecoveryMod I have the stock ROM on my sd card.
I. I choose install zip from sd card.
II.Choose the correct zip file and start flashing.
III. Choosing Wipe Data/Factory reset will take the device into a complete hang. unless I first use the mount page to mount the System/Data
IV. I reboot the device and ..... you know nothing changed.
so thats my story.
Still hope to find something about it.
Thanks...that was helpful. But now I want to know the following:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
okantomi said:
Were you rooted before the trouble started?
What did you do to recover?
If rooted, what version of CWM recovery did you have installed? Did you do a nanadroid backup? (I guess the answer is no, because you could have just restored with that).
What recovery are you accessing when trying to flash a zip file?
If you can answer these questions I will continue to wrack my brain trying to recall where I saw that thread.
Edit: please check out this thread http://forum.xda-developers.com/showthread.php?t=1370312
Some of what I said to him may help you .
Click to expand...
Click to collapse
Being rooted? -> Yes, The world is more beautiful with root!
to recover -> I followed this: http://forum.xda-developers.com/showthread.php?t=1097997 Shame it was Android 3.0
I use ClockworkRecovery 3.0.0.28 and I cant upgrade it cause of ... you know
And for your help I must say you are definitely the most caring person I know...
I'm off to check the provided link now
I was thinking of something that might be a reason.
I have this tiny problem:
When I go to CWM and choose Erase userData/Factory Reset Device Hangs
Click to expand...
Click to collapse
I was thinking of may be the userdata partition is corrupted and I gotta find a way to flash it completely.
Somehow I used Fastboot utility to do this and after saying Success, Nothing changed again.
Do you know any other way to physically do this job?

Samsung Recovery Mode is useless! Grr

hiya, well i am new to the forums been learning a lot and found out a lot of weird things about this phone.
Yesterday downgraded wifes HTC Wildfire HBOOTs, Firmware, Rooted it, and Installed ClockWorkMod and cygenMod7
so i am fairly confident when it comes to using recovery mod so decided to try and see what i can do on my galaxy 3
--
i have my stock ROM (rooted) and just how i like it, the only thing i want to be-able to do now is just put ClockWorkMod
on my phone, so if anything goes wrong i can just restore via the bootloader.
Read a lot today and decided the best way to go is to just flash the kernel that includes CWM
and the install method for this i read was to boot into recovery and install the kernel from the SD card.
On booting into the recovery (power home volume up/down together) there is an option that says
"Apply SDcard update.zip"
do i rename the kernel to update.zip? or will it see the kernel file?.
i did try clicking this update.zip just to see what it would say but it give me this message.
---
Finding Update Package
E: can't mount /dev/block/mmcblk0 (or null)
(no such file or directory)
E: Can't mount SDCARD:Update.zip installation Aborted
----
Now is there something i am missing? does this mean i cannot flash the kernel to another one
Grrr all i want is to just get clockworkmod recovery on this phone nothing else and its just seeming impossible
does this now mean i have to use ODIN the magical Mystical Tool that everyone knows about but doesn't have a clue where it come from?
or is there some other way to get this kernel onto this phone
i don't want to try the other options wipe data factory reset to see if the options are in there?
Sorry if this sounds dumb just i have no clue what this Apply sdcard:update.zip is or meant to be for
and if thats not how to update the kernel i don't see any other options to install a file from the SD card!
it's frustating now any help advice would be great even if someone could explain more about what this option does?
GraphiX2004 said:
hiya, well i am new to the forums been learning a lot and found out a lot of weird things about this phone.
Yesterday downgraded wifes HTC Wildfire HBOOTs, Firmware, Rooted it, and Installed ClockWorkMod and cygenMod7
so i am fairly confident when it comes to using recovery mod so decided to try and see what i can do on my galaxy 3
--
i have my stock ROM (rooted) and just how i like it, the only thing i want to be-able to do now is just put ClockWorkMod
on my phone, so if anything goes wrong i can just restore via the bootloader.
Read a lot today and decided the best way to go is to just flash the kernel that includes CWM
and the install method for this i read was to boot into recovery and install the kernel from the SD card.
On booting into the recovery (power home volume up/down together) there is an option that says
"Apply SDcard update.zip"
do i rename the kernel to update.zip? or will it see the kernel file?.
i did try clicking this update.zip just to see what it would say but it give me this message.
---
Finding Update Package
E: can't mount /dev/block/mmcblk0 (or null)
(no such file or directory)
E: Can't mount SDCARD:Update.zip installation Aborted
----
Now is there something i am missing? does this mean i cannot flash the kernel to another one
Grrr all i want is to just get clockworkmod recovery on this phone nothing else and its just seeming impossible
does this now mean i have to use ODIN the magical Mystical Tool that everyone knows about but doesn't have a clue where it come from?
or is there some other way to get this kernel onto this phone
i don't want to try the other options wipe data factory reset to see if the options are in there?
Sorry if this sounds dumb just i have no clue what this Apply sdcard:update.zip is or meant to be for
and if thats not how to update the kernel i don't see any other options to install a file from the SD card!
it's frustating now any help advice would be great even if someone could explain more about what this option does?
Click to expand...
Click to collapse
You have to use odin
Download the G3MOD kernel and flash it via Odin. Search on this forum and you'll find Odin as well as the ops file for our phone and a guide on how to use odin.
Click thanks if I helped.
stubborn_d0nkey said:
You have to use odin
Click to expand...
Click to collapse
saying oh you'll have to use odin isn't really helpful
something like explaining any fatal flaws when using odin that you might know about would be helpful.
example do i tick protect ops? when flashing the kernel? or is that just for ROMS
some really in depth information would be really helpful and grateful not only to me but anyone else who's looking to do this.
You're over complicating it. There is a guide on how to use Odin on our forum so read that. You flash a kernel the same way you flash a ROM and there's not much risk. Yes you do protect ops. The process of flashing takes approximately 5-10 seconds for a kernel then your phone reboots. Just relax and do it. After you've done it once you'll be able to do it a million times.
Edit: http://forum.xda-developers.com/showthread.php?t=1372414 << here is the tutorial.
Click thanks if I helped.
GraphiX2004 said:
saying oh you'll have to use odin isn't really helpful
something like explaining any fatal flaws when using odin that you might know about would be helpful.
example do i tick protect ops? when flashing the kernel? or is that just for ROMS
some really in depth information would be really helpful and grateful not only to me but anyone else who's looking to do this.
Click to expand...
Click to collapse
well you could easily have just read the sticky topics explaining all the different things about our phone including how to flash using Odin.
Sent from my GT-I5800 using xda app-developers app
GraphiX2004 said:
saying oh you'll have to use odin isn't really helpful
something like explaining any fatal flaws when using odin that you might know about would be helpful.
example do i tick protect ops? when flashing the kernel? or is that just for ROMS
some really in depth information would be really helpful and grateful not only to me but anyone else who's looking to do this.
Click to expand...
Click to collapse
"You have to use odin" pretty much answered all of your questions since it did answer one and made all the rest irrelevant. You wrote all that text and all those questions yet you couldn't have written three little words ("If so, how?") after asking if you needed to use odin? You never made it seem as though you would need help if the answer was that you had to use odin, so dont shame me if I chose not to waste words when answering your post, which I did do. If I wasn't helpful the reason isn't because I was cheap on words, its because your post didn't require anything more than what I wrote (even if you did).
no worries thanks anyway 12 hours it was driving me nuts trying to just simply get clockworkmod on this phone.
in the end i decided to opt for a popular rom here (which will be donating after this post) the guys rom does everything i needed.
i made a post about odin 117 views but not a reply.. since this thread seems to be a little active
in simplyfied terms where on earth does this odin come from? everyone knows about it uses it but who makes it?
is there an official downloads page, their must be something otherwise how would people know when newer versions come out?
again donkey sorry i snarked, yes i looked into the guide it was great! followed everything and i now have a lovely G3Mod rom installed.
GraphiX2004 said:
no worries thanks anyway 12 hours it was driving me nuts trying to just simply get clockworkmod on this phone.
in the end i decided to opt for a popular rom here (which will be donating after this post) the guys rom does everything i needed.
i made a post about odin 117 views but not a reply.. since this thread seems to be a little active
in simplyfied terms where on earth does this odin come from? everyone knows about it uses it but who makes it?
is there an official downloads page, their must be something otherwise how would people know when newer versions come out?
again donkey sorry i snarked, yes i looked into the guide it was great! followed everything and i now have a lovely G3Mod rom installed.
Click to expand...
Click to collapse
Samsung made it, however there is no official download page since it is leaked software. It probably not intended for the general public, but I dont think Samsung minds that it gets out. AFAIK samsung uses it/used it internally.
No problem about the snarking, I understand what its like to be a noob, every has been a noob, but I do know what its like to be a person who tries to help noobs.

Would someone mind looking over my plan to root my Note 4? I just want to be sure

I have experience rooting a Xoom, an Atrix, and an S3, but at the same time I usually just follow instructions to the bullet point while only vaguely understanding what I'm doing.
I got my cracked screen replaced at a non-samsung outlet yesterday which I'm pretty sure voids my warranty, and if so, I want to take advantage of that by rooting. But a lot has changed since the last time I rooted a phone - they're talking about "systemless root" and flashing an SELinux Permissive Kernel and then "Oh no wait you don't have to flash such a kernel in this new version" and I have no idea what any of that is referring to, all that stuff is new to me.
I have a Canadian Note 4 SM-N910W8 running the latest COK3 OTA update on 5.1.1. I found this rooted ROM which I'm pretty sure is the one I want, but then, it's the only one I found, if there are more or better rooted ROMs please let me know:
http://forum.xda-developers.com/note-4/snapdragon-dev/trltecan-n910w8-aoa1-stock-rooted-t3025538
The instructions for how to install it keep changing for every version though. It also says I need to start by flashing TWRP via ODIN - Okay, I've done that before, but I want to make sure I get the right one. I found a couple of sources:
http://forum.xda-developers.com/note-4/general/ref-stock-firmware-kernel-modem-recovery-t2920452 - twrp-2.8.7.0-trltecan.img.tar
and:
http://galaxynote4root.com/cwmtwrp-recovery/ - openrecovery-twrp-2.8.1.0-trltecan.img.tar
Not sure which one I should use.
All I want is to be able to edit the keyconfig files to get my USB controller working, to be able to edit system files to change the Touchwiz aggressive background app closing and allow apps to remain in memory for much longer to make it more like Windows memory management, and to be able to install Xposed modules like statusbar volume.
But I want to make sure that I'm doing everything *exactly* right, and that's why I like to ask real human beings to confirm my plan before starting. So I download one of those TWRP files, download ODIN, plug my phone into my PC, use ODIN to flash TWRP, boot into TWRP, use TWRP to wipe data, cache, dalvik, and system, and then install the rooted ROM I linked above. Have I got all that right? What's all this SELinux and systemless root stuff I keep hearing about, and why don't I need to do that anymore with the latest version of this rooted rom? Will this break any key features on my Note 4 like my spen or my external USB or my blood oxygen meter or all the cool novelty **** that Samsung Note 4 comes with?
Right here goes the rom u have is the right one for ur phone. There will be others around byt u can try that ome to start with. The twrp recovery u need is the 6th one on the list down the model numner is at the end of the file name, its the .tar file u want zip can be used also but thats using recovery to flash the rom. Using odin 3.09 latest one i think. U need to hold down volume down, home and the power to boot into download mode open idon with kies closed and end task with task manager in window.
Now whem oden starts u need to select the phone tab and choose the twrp recovery and flash that leaving everything unchecked apart from restart and reset time all others should be blank, i flashed with erase nand and nearly bricked my phone, thats one to leave for the experts lol.
Once u flashed recovery i think u need to root even though the rom is rooted rom i think it needs to be rooted before u flash the rom, not sure but its what was on the instructions i followed. If u try find a root file off here for ur phone u do same as u did flashing the recovery file and tjats it wait for phone to restart and reboot fully after flashing each recovery and root, i always do from knowimg its best ti imstall wimdows apps ome at a ti, e and reboot between the installs as less syste, errors can happen that way , well not system errors but linked dll files not been copied right and the like.
Thanks
Steve
Still need help them post back and will do my nest nut i a newb, i have an understandimg of how things work but by no means am i an expert i do what u do, i follow imstructions and learn as i go along what thimgs are and what they do, best way then u kmow what ur messing or dealing with.
U also, well i did for my 910f need to use a specific twrp or at least the latest release.
The walk throughs on most sites are all the right way to do it, just others are explained better than others and imclude other stuff if it goes wrong which believe me it can go wrong, easy as not seeimg a check box tocked or not ticked and boom paper weight lol
Digipro said:
The twrp recovery u need is the 6th one on the list down the model numner is at the end of the file name, its the .tar file u want zip can be used also but thats using recovery to flash the rom.
Click to expand...
Click to collapse
Okay but what about the other site I found, the XDA forum with TWRP recovery files? They seem like newer versions, but then that left me wondering if the reason the other site has older versions is because it's just outdated, or because only the older versions will work.
Thanks for all your help btw!
Your welcom, the rom you want is fine, u want to go for either of the roms version 3.21 de bloated or regula,, de bloated is where they take slot of apps by google and also carrier apps that sometimes come installed.
Steve.

Categories

Resources