Database Users

**FIX** JV* Battery Issues

Hi
After finding that I had problems with the Gingerbread update draining very quickly it was apparant that something somewhere was wrong, as other people was experiencing very good battery life.
The android os is not letting the phone go into sleep mode..
I got my phone to work correctly and this has worked for many others who I have spoken with..
Ask customer to back up all relevant data, or do it for them.. Then clear off the internal SD.
Use Odin and flash an Eclair rom, with repartition and pit 512
I use :- http://www.multiupload.com/BEPEXOJKY2
JM9 PDA
JM4 Phone
JM1 CSC
Let the phone bootup to the dashboard, then switch straight off back into download mode..
From here flash the JV* rom of your choice, with no PIT or no repartition.
Once complete put and the phone has booted put back the required contents onto the SD.. Best keep it to a minimum, just titanium backup etc and other essentials.
Hope it works for you
Before --------------------------------------------------------------------------------------After
{
"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"
}
___

What have you done with bootloaders?
Have you flashed the froyo bootloaders when downgrading and then the GB bootloaders when upgrading again? Or just kept the GB bootloaders during both of the flashes?
hope this works...

maartenlaeven said:
What have you done with bootloaders?
Have you flashed the froyo bootloaders when downgrading and then the GB bootloaders when upgrading again? Or just kept the GB bootloaders during both of the flashes?
hope this works...
Click to expand...
Click to collapse
I flash the full roms, so it flashes the boot loaders on each and every flash that I do

What exactly is the theory behind this trick?
Flashing to Eclair, and then flashing to Gingerbread. Sounds weird...

Updates OP.. Now with Download and Images..
I think it would work with any firmware that you can repartition and use a pit.. But for me JM9 works a treat.. It sounded strange to me also.. But I tried it and it went fine..

Looking good until you trigger draining again by any app ?!?

Not getting no where near as high drain though.. As you can see by the 2 images the drain should be high as WiFi is on constantly.. I don't use many apps, but Tapatalk, email and tweetdeck is all set to 30 minute updates..

This procedure doesn't make sense, I don't believe it. Probably the first JV* flashing procedure wasn't done properly or something.

Tyxerakias said:
This procedure doesn't make sense, I don't believe it. Probably the first JV* flashing procedure wasn't done properly or something.
Click to expand...
Click to collapse
How do you mean doesn't make sense !!!!!!!!!???????!!!!!!!!
I had crap battery with jvk jvb and jvh. This install method sorted it all out... Maybe an extreme way of going about it...
Sent from my GT-I9000 using Tapatalk

What is this??? Just 3 days for this trick?! I can even use mine for 4 days on stock JVB (with some UI mods though) on moderate use. And apps still trigger Android OS problem? So what is this exactly?
EDIT: Just saw your battery usage screenshot. Sorry but I doubt it much. Your phone signal went crap (red bars) but the graph didn't even flinch a bit...

Tricky103 said:
How do you mean doesn't make sense !!!!!!!!!???????!!!!!!!!
I had crap battery with jvk jvb and jvh. This install method sorted it all out... Maybe an extreme way of going about it...
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Ι mean that it is not a logical fix, hence, it doesn't make sense. Explain why this works, and then I'll believe it's not a coincidence....
You flash one rom, then you flash another one including bootloaders, wiping the first one entirely, then you reflash the first one including bootloaders on top of it, wiping it again entirely. What changes? Why does that improve the battery?

We do not know what is it but from what i know it is not: modem driver i have now set to 2G only data OFF wifi off gps off sync off and task killer killing everything but not clock when screen goes off, screen set to minimum brightness i have deleted samsung update app and some other apps (facebook etc) on desktop only apps shortcuts no widgets no wallpaper its pure dark. Now when i launch gameloft intensive game for 30 minutes, turn it off and put phone in a pocket after some time i get it back and i could feel that back of a phone is little bit hotter (on back plate where CPU is i think) and from now on every maybe 3 minutes battery is going constantly down 1% by 1% until i do reboot nothing will stop doing that.

No doubt about it, this trick works like a charm, I had a huge battery drain I flashed eclair then froyo then XWJVH, now I can use my phone moderately for more than two days with no problem, I ask everyone with battery drain to try it before judging, I know it doesn't make sense but believe me it does work.

Tyxerakias said:
Ι mean that it is not a logical fix, hence, it doesn't make sense. Explain why this works, and then I'll believe it's not a coincidence....
You flash one rom, then you flash another one including bootloaders, wiping the first one entirely, then you reflash the first one including bootloaders on top of it, wiping it again entirely. What changes? Why does that improve the battery?
Click to expand...
Click to collapse
My belief is that it is not due to bootloaders, as the only problem they give is a corrupt screen.. I think that constant flashing possibly fragments the internal sd and system storage and flashing jv* without a repartition or pit doesn't makes the faults occur..

How kernel JVH get more baterie life
How kernel JVH get more baterie life

It is not kernels fault, it is android OS core triggering phone to not sleep because of hi cpu usage, im trying to do it now because of dirtiness i have made before flashing JVH.
Adding additional info: i could feel when sleep is not working, when i click unlock button screen goes ON immediately, when sleep was working screen goes on little bit later

what helped you here is the reflash with repartition not flashing js*something first. could be the jv* only flash and you would not have drain again.
for me one app triggered drain not letting the wifi to change its state. noticed it as i had it set to turn off 10 seconds after screen and the stats showed the wifi on whole time.

Tricky103 said:
My belief is that it is not due to bootloaders, as the only problem they give is a corrupt screen.. I think that constant flashing possibly fragments the internal sd and system storage and flashing jv* without a repartition or pit doesn't makes the faults occur..
Click to expand...
Click to collapse
Interesting. So basically if someone updates from Froyo straight to JV* without repartition, they should, in principle, have great battery from the get go, right? (has anyone tried?) In that case there must be something wrong with how Odin flashes, not previously reported, since 512.pit is identical for Froyo and Gingerbread, and as far as we know the only thing that it does is to make the partitions.
What if we use Richtofen's method (the way he used to propose for flashing the leaked ROMs he posted), i.e. to flash first the pit file alone, with nothing else, then re-enter download mode with the 3button combo, and flash JV* without repartition or anything else. *Is there anyone who tried this and checked the battery?
This can potentially open a new line of investigation into how Odin works....

I think that Your methode make a clean install of rom. But i think that is just a small update. I dont wont less my data and apk. I ask to give me another method to make more batterie life. Thanks.

id the app causing the drain
make sure thats the case
report to app developer

[Guide] How to install ICS **EVERYTHING you need to know how to install them**

This is for a clean install. You can also install straight from Froyo. Just start at the CM7 part below and skip the Odin portion.
FLASH AT YOUR OWN RISK​
**If after you get on and are rocking the ICS of your dreams, you wake up one day and get the Encryption Unsuccessful - Reset Android - ICS Issue, see bottom of post for possible solution** ​
DO NOT HIT RESET repeat DO NOT HIT RESET​
It is a bug that is hitting all ICS ROMS (AOSP-Passion, AOKP-Zen/Euphoria, Docmasters, CM9,...) on many different types of phones (Captivate, Vibrant, I-9000) and someone got hit with it in my OG Transformer Tablet (TF101) forums too.
You have been warned​.
FLASH AT YOUR OWN RISK​
I have made some observations as to how and why the Encryption Error strikes. See this thread starting at page 38 on (my post is #379 and after).
If running CM9 then this may be a work around before the issue strikes. I have not tried this and take no responsibilty if it works or not. Good Luck
USB mode switch for SGS1 on CM
Click to expand...
Click to collapse
What you need. All files can be found in the [Repository] Essential Hard To Find Files
Odin or (AIO ToolBox AND .net files) ***DO NOT PM me for this, I will just delete your PM and not respond. If you want ODIN, use Google and Download it. Sorry for this but my Dropbox account is suspensed b/c of too many downloads***
Gingerbread Bootloaders Go here for instructions.
CM7
Whatever ICS ROM you want to flash
These directions should work with any ICS ROM because the OPs and requirements (i.e. GB bootloaders, CM7 first,...) for all are essentially the same.
Click on Gingerbread Bootloader and ICS to take you to their respective threads.
**Note that this step (Installing Gingerbread Bootloaders) is reported to be optional as the Rainbows seemed to be fixed** Note: ICZenwich does REQUIRE Gingerbread bootloaders for CWM purposes.
If you want to use different Kernels (this is done after you flash the ICS ROM) on Neobuddy89's ICS Passion or Euphoria, Closedcircuit has them all in one place. Check out his thread here and make sure to thank him otherwise you might have to search for them on your own and we all know what a P.I.T.A. that is don't we?
.::IMPORTANT::.
Remember that you have to do this steps before and after update your kernel:
Wipe cache
Wipe dalvik cache
Flash kernel
Fix permissions
Click to expand...
Click to collapse
If for some reason your External_SD card (soon to be called EMMC after you get on ICS) does not mount. See here. Click the link within and flash it in CWR and you should be good to go
Click to expand...
Click to collapse
Standard Disclaimer Applies: This is your choice to do this, not mine. If something goes wrong, ask. If something goes horribly wrong, it is on you.
The video: This was done by DJeddieone and is very informative and helpful. Please watch it and hit his thanks. What follows is generally the same thing but with a few differences and in written form for all those people that need text instructions.
Watch this video, then read the below, watch the video again. Video has Froyo bootloaders and getting into recovery is different key combo, see GB thread below about that.
Just to make sure, I am going to start at the very beginning.
Flash back to stock 2.1 with Odin and the pit/pda files already included in the Toolbox. You should already know how to do this if you are flashing ICS. If not, then use the search to find out how.
Download and put Clockwork Recovery.zip on your internal SD card. Make sure it is labeled Update.zip and is the only .zip on the root of your SD card (should look like this /sdcard/update.zip). Can be directly downloaded from my signature or the Noob Guide stickied in the Q&A sections. Thanks s15274n
On your INTERNAL SDcard create a folder called ICS or something.
Download the CM7 file and put in the ICS folder (doesn't matter about the 911 issue b/c you aren't going to be using CM7 anyways)
Put the ICS ROM version that you already downloaded in the Folder also.
So let's start.
**Note that this step is reported to be optional as the Rainbows seemed to be fixed**
You need to open Odin and boot phone into download mode. Download the Gingerbread Bootloader and put it on your Desktop and in Odin, click on PDA and browse to the GB bootloader and click it. Your option but I do not tick the Auto-Reboot just in case of a bad flash. Once it passed, you are good. Unplug and reboot.
To start the flashing process, you should have 2.1 (stock-Eclair) on your phone as per above directions
Once it is fully booted, turn it off.
Push the Volume-Down + Power until you see the Vibrant come up and let go of the Power but keep ahold of the Volume-Down button. This will boot you into recovery. (If you are on Froyo Bootloaders, then it is Volume Up AND Down + Power) Can be tricky, so try it a couple of times if it doesn't work the first try.
Tab down to Reinstall Packages and click it. Let it run. If it gets back to the Blue Recovery, you might have to do it again. This will install the CWR that you put on your internal SD that you downloaded from my signature earlier. The recovery will go from Blue (stock) to Green (CWR).
Wipe Data/ Factory Reset, Wipe Cache and go to advanced and Wipe Dalvik-Cache, go to "Mounts and Storage" and format /system (if flashing Euphoria you'll need to format /data too), hit Back twice to front page of CWR.
***See Bottom why you need to flash CM7 before.***Also, if coming from a Voodoo Kernel based 2.2 or higher ROM-Disable it before flashing CM7.***
Scroll down to "Install from SD Card" and scroll down to your ICS folder. Find your CM7 file and hit it. Once it finishes, reboot. It will probably bootloop. This is normal. Pull your battery and boot into (turquoise [or red or green]) recovery again, "Install from SD" and reflash CM7.
Once it finishes, reboot. First boot takes longer than normal because it has to build the Dalvik-Cache. It should boot up this time. Let it fully boot up and settle for a minute or two. Hit power on the side and reboot into recovery directly from the Extended Power Menu.
**There is a point in the flashing of CM7 where you will think that the install either aborted or is finished. IT IS NOT DONE. Let is sit and completley boot up. Don't get trigger happy. You will see a toast to install your Google password. Then is when it is fully booted.**
Once you are in recovery, scroll down to your folder and find the ICSv? (or whatever version you are wanting to flash) and flash it. First boot takes a long time just like before on CM7. Might also get into a bootloop like in CM7 too. If so, then do the same as before and reflash ICSv?, but this time you'll have to use the Volume-Down + Power (or if on Froyo Bootloaders the above key combo) to get into recovery. Boot up and you are good to go in you new ICS rom.
**IMPORTANT**
Why do I need to flash CM7 before ICS? Can't i just go from Eclair to ICS? i have seen some people do it this way and it worked for them.
ICS kernels and working recoveries use a MTD based /system (hence the flash to CM7, as CM7 will convert your /system properly) and Eclair/Froyo are either RFS or Ext4 (voodoo). It also converts your Externa_SD into the EMMC partition.
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
If you get the Encryption Unsuccessful - Reset Android - ICS Issue
{
"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"
}
Go here in the Captivate Forums.
******************
Couple of things.
Once you are in ICS
*your external sd is now called EMMC
*the GPS is sketchy (although there are new kernels that are reporting this issue fixed-see your respective ICS thread)
* there are some Deep Sleep issues
* when you RECEIVE a call, you will have to hit mute/unmute for them to hear you. (this seems to have been cleared up now)
These are all known bugs and if you ask about them in the thread, you'll get flamed for sure.
Good luck. The whole process should only take a hour or so and most of that is just finding the files and watching the video. Actual flashing should only take 10-20 minutes.
Hit the thanks. Pretty much gave everything needed to flash from 2.1 to 4.0.3

A computer lets you make more mistakes faster than any invention in human history – with the possible exceptions of handguns and tequila. ~Mitch Ratcliffe
Change log:
4/17/12 - I have made some observations as to how and why the Encryption Error strikes. See this thread starting at page 38 on (my post is #379 and after). Put in link to Play.Store for USB mode switch for SGS1 on CM and tag at top of guide re: its use.
4/2/12 - Emphasized the Encryption Bug to make it more visible and warning of hazards.
3/30/12 - Put in section at Top and Bottom about the Encryption Unsuccessful - Reset Android - ICS Issue and a link to the solution/workaround to the Captivate thread.
3/12/12 - Bolded AND in the kernel instructions re: wiping before AND after kernel flash. Put in something about waiting for CM7 to fully boot up and that it may seem like it is aborting or done, however it isn't and you need to wait for a complete boot. Don't jump the gun on this and pre-maturely pull out. This is called CyanogenMod-us Interruptus.
3/8/12 - Explained why you need to flash CM7 before ICS. Put in link to fix External Mounting issue.
2/22/12 - Put in blurb about PMing me for AIO Toolbox and made the Toolbox Secondary to Odin
Included Closedciruit's thread with the ICS Passion and Euphoria Kernels.
Put in blurb about RANDOM OFFSET error and how to fix/bypass it.
2/18/12 - Took out Dropbox links because my account got suspended for TOO MUCH TRAFFIC. You are on your own for those right now until I find another solution. I am not going to register for another file sharing site.
2/15/12 - Put Dropbox links in OP with Froyo and Gingerbread Bootloader. Revised to make this all ICS ROM compatible since the OPs and per-requisites are essentially the same.
2/12/12 - Now AIO Toolbox, .Net and CM7 have direct download links since MultiUpload is down
1/15/12 - Revised to show that you can come from 2.1 OR 2.2

Yea, rainbows are fixed. If you don't flash a gb bootloader you wont see the kernal boot image. That's the only known issue. So its not really needed

Thanks for the nod, good job man.

I'm glad you put the AIO toolbox there. It seems no one knows how valuable that little program is.

thanks woodrube for the simple guide. the video from djeddieone seems to be fairly simple also.
i heard that if odin was used to go back to stock eclair to never use kies mini for a future update or else it would hard brick the phone. I've never odined back to stock however tempting to install cm7 i fell victim to a bootloop so i freaked out and odined back to froyo kb5. the question is now, if i used odin to go back to froyo would it be the same outcome as using odin to stock eclair when tempting to update with kies mini?
the reason why i ask is, i had given up flashing a custom rom, hoping for a stock update. but if thats not possible anymore i will go ahead and flash ics.
i tried my best searching. if i'm asking in the wrong place please redirect me. thanks and be patient with the noob.

lazynoob said:
thanks woodrube for the simple guide. the video from djeddieone seems to be fairly simple also.
i heard that if odin was used to go back to stock eclair to never use kies mini for a future update or else it would hard brick the phone. I've never odined back to stock however tempting to install cm7 i fell victim to a bootloop so i freaked out and odined back to froyo kb5. the question is now, if i used odin to go back to froyo and not eclair would it be the same outcome as using odin to stock eclair when tempting to update with kies mini?
the reason why i ask is, i had given up flashing a custom rom, hoping for a stock update. but if thats not possible anymore i will go ahead and flash ics. thanks and be patient with the nood. i tried my best searching.
Click to expand...
Click to collapse
Couple of things. First DO NOT USE KIES. Kies will hardbrick you device. Not sure why anyone still uses this but don't. Second, you bootlooped in CM7 b/c of an CWR mismatch. This is normal for CM7. What you would want to do it pull the battery and reboot into recovery and reflash CM7, essentially over-top of itself. It should boot up the second time.
Don't give up on flashing custom ROMs. Once you do it, you will love all the cool things that you never knew you could do. Follow my instructions above and you can essentially flash whatever ROM you want from 2.1.

yea figured it out watching some youtube clips. should have reflashed. so what you are trying to say is kies mini in general is dangerous? i have used it sveral times to update when on stock. mine and my wife's vibrant.
last question, if the impossible happens and vibrant gets a stable stock update, will i be able to just odin to stock eclair and update? if not with kies maybe using odin?
thanks for your help. hoping to help those like me in the future. can't wait to start flashing.

lazynoob said:
so what you are trying to say is kies mini in general is dangerous? i have used it sveral times to update when on stock. mine and my wife's vibrant.
last question, if the impossible happens and vibrant gets a stable stock update, will i be able to just odin to stock eclair and update? if not with kies maybe using odin?
Click to expand...
Click to collapse
Kies is bad. Really surprised you haven't bricked it yet. Stick with Odin to do your fresh flash. The Vibrant is not going to get an update, so don't count on that (see the petition in my signature if you want that to change). Fortunately we have an outstanding development community.
If you want a stable 2.2 try Toxic8 (I run this with Gingerbread theme as my "home" ROM when I am not testing), Deranged9, Bionix (no longer supported) and Bionix Fishman's version (this is supported), Bi-winning. All you have to do to flash these is follow the instructions above and when it comes time to flashCM7, skip it and flash the ROM of your choice. All of these have working GPS and 911, so no issues there. Any GB ROM (CM7 included) will not have functioning 911, just an fyi.

Bump (sort of b/c I updated some things on the OP)

Reserved. Good guide here. Thanks for the effort for those who are not so familiar with flashing like me. Gonna flash ICS when i get my Vibrant back. Thanks buddy.

multiupload seems to be done, does anyone have another link or can they send me AIO Toolbox?

Quikster said:
multiupload seems to be done, does anyone have another link or can they send me AIO Toolbox?
Click to expand...
Click to collapse
help? does anyone have this file or another link? PM me

outstanding development community.

I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.

Woodrube said:
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Click to expand...
Click to collapse
awesome, i greatly appreciate that

OP updated with Dropbox links to AIO Toolbox, .Net add-on and CM7 7.1 ROM.

Thanks for the Guide, works perfectly. Now im enjoying ICS Passion v13 RC1.
I was in TeamToxic-D9RC3 rom. This is what i did:
- I started from CM7 part.
- Reboot into Recovery
- Wipe Data/ Factory Reset, Wipe Cache and go to advanced and Wipe Dalvik-Cache.
- Locate ICS folder-Install CM7.
- After boot into CM7-reboot into Recovery again.
- Install ICS Passion RC1.
- After finish installation, wait bout 5mins.
- Reboot into Recovery again, flash cleanup patch then reboot.
- That's it.
Thanks to:-
-Neobuddy
-Nelson for the Kernel
-Romanbb for source hack to enable FB sync
-Daniel for the Bootsplash and other graphical enhancements
-CM9/Teamhacksung for the drivers
-Annex for cosmetic upgrades which are really better than Stock ICS AOSP.
psycho for Mods
-Woodrube

Woodrube said:
I will upload a version of Toolbox and the generic CM7 build sometime tomorrow since multiupload is apparently down.
Click to expand...
Click to collapse
Thank you very much

Woodrube ... thanks for the nice tutorial. Couple questions re. the GB Bootloaders.
Woodrube said:
**Note that this step is reported to be optional as the Rainbows seemed to be fixed**
Click to expand...
Click to collapse
When you say "Rainbows seemed to be fixed" ... does this mean:
a) GB Bootloaders are still REQUIRED - ie. it's the GB Bootloaders that "fix" the rainbows?
b) Or ... GB Bootloaders NOT required - ie. some type of fix has now been incorporated into the ICS ROM packages?
Sorry for asking for noobish clarification, but I wanted to avoid any possibility of turning my phone into a paper weight.
Woodrube said:
Your option but I do not tick the Auot-Reboot just in case of a bad flash.
Click to expand...
Click to collapse
This is a great suggestion. Thanks for the tip.
Woodrube said:
Gingerbread Bootloaders
Click to expand...
Click to collapse
adyscorpius' link for his modified JFD ODIN file is down (ie. Multiupload is down). Wondering if anyone has this particular file or a fresh link to download it? It'd be nice to not have to worry about whether a JFD package has the proper boot.bin / sbl.bin combo or not.

[Q] Bootloop please help -Process system isn't responding

It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?

eagle909 said:
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
Click to expand...
Click to collapse
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device

radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?

eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Ahh, you will need to find an ext SD card, then you'll have to transfer it across via your PC then insert into phone, boot into Recovery and flash it.
Not flashable via Odin atm I'm afraid

eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Yes it does comes with an ext SD card slot... Beside ur sim card slot. Put that file into it then put into ur phone. Boot into custom recovery and flash it.
Sent from my proudly temaseked +Yankied note 3.

Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"

radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
radicalisto said:
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
Click to expand...
Click to collapse
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.

Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...

eagle909 said:
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Click to expand...
Click to collapse
The screenshot of the install. I suspect if there is something wrong with the install?
{
"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"
}

eagle909 said:
The screenshot of the install. I suspect if there is something wrong with the install?
sorry too big of the picture
Click to expand...
Click to collapse

ultramag69 said:
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
Click to expand...
Click to collapse
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/

That screenshot looks OK to me. The Mount error is standard in TWRP. Reboot your device and see.. or as posted re flash stock as it pretty much fixes everything
Sent from my SM-N9005 using XDA Premium 4 mobile app

eagle909 said:
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
Click to expand...
Click to collapse
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting

eagle909 said:
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
Click to expand...
Click to collapse
You haven't flashed a stock rom... That is rooted and so is no longer a stock rom. Go to Sammobile.com to get a pure stock rom...
Just a note for you, whether it says stock is solely reliant on it being NOT tampered with. Rooting a stock rom no longer makes it stock, it is just a description that means no tweaks were applied or bloatware removed...
Remember that the bootloader must match the stock rom. If you are trying to flash a lower version rom onto an MJ3 or higher bootloader you will get bootloops.
The same applies if you have updated to Kitkat rom.

If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk

I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Dahdoul said:
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse

eagle909 said:
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Click to expand...
Click to collapse
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.

I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
radicalisto said:
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
Click to expand...
Click to collapse

eagle909 said:
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
Click to expand...
Click to collapse
Is the phone bootlooping constantly ? and crashing after around 1minute?

rtanceF seize
radicalisto said:
Is the phone bootlooping constantly ? and crashing after around 1minute?
Click to expand...
Click to collapse
When you mean "install a custom recovery via Odin", you meant to install something like TWRP to install the zip using recovery mode?
The phone keeps booting again and again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding" before the phone restarts.

[Q] any rom for gty5363

There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.

bwizz60 said:
There does not seem to be any recent onfo on my partner phone, nor very clear if the 5360 rom is compatible
So here is the question. Is there a minimalist rom with equally good battery life. Her phone is much better than my ace
on battery life. but is full of samsung garbage.
Click to expand...
Click to collapse
As far as I'm aware the 5363 is the o2 variant of the 5360
You might be able to just unlock the phone if not already unlocked (use galaxy toolbox) & flash 5360 firmware and use 5360 roms
Anything you do you do at your own risk - neither myself or xda are responsible for damage caused

I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead

bwizz60 said:
I have rooted and unlocked phone ready to install reincarnation rom. I can't boot into clockwork recovery as I get the "error in sideload zip 7 message" I have tried installing clockwork from rom manager but still same. Think it is because the GTs 5363 bt number is not recognised.
can I get around this issue? I did a google search and found a cwm clockwork bla bla that seems to work.
but I will wait for any comments/imput before I go ahead
Click to expand...
Click to collapse
Why would you install cwm from rom manager? It's not supported - please do some searching and some reading else you will damage your device
There are two ways to get cwm on galaxy y
1- Flash temporary cwm zip in stock recovery - see http://d-h.st/u2m
2- Flash a kernel with cwm built in
If neither work on your variant you will need to flash 5360 firmware via odin at your own risk

I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.

bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Hi.
Here is the CWM link: http://forum.xda-developers.com/showthread.php?t=2649475
Please do some digging first before asking.
Also, ROM Manager is not supported on our phones, so do not use it.

bwizz60 said:
I thought that I read that the rom manager is the recommended way of flashing CMW? Your supplied link seems to be a windows install file
How do I activate it please.
Click to expand...
Click to collapse
Don't know what you are clicking on as it's a zip file
Make sure you are clicking on the right download button & not an ad - Install ad blocking software on pc or an app on phone if required
I never post exe files - all my files on dev host are Flashable zips/tars unless otherwise stated
See below Screenshot - Just press the download button as shown in Screenshot
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also you should take note of what you are reading, where you are reading it & what device it relates to - rom manager has never been a compatible way of flashing cwm on a galaxy y

The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that

bwizz60 said:
The reading re my device is quite confusing. but I got the CWM installed thanks. In the interim I have soft bricked the phone. When it boots it still reads gts 5363 in the boot screen. I was expecting it to now read 5360? would it be a good idea to flash a standard 5360 onto the phone via odin .
and maybe work forward from that
Click to expand...
Click to collapse
It would only say 5360 if you flashed 5360 firmware via odin
Iv kept telling you if you want to use 5360 kernels you will probably have to flash 5360 firmware
Feel free to do what you want at your own risk

Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick

bwizz60 said:
Sorry bad info on my part I was trying to use CWM via galaxy toolbox. I hit a snag with the CWM as I it was faulty and I could not go back out of the advanced screen. to follow the rom suppliers step by step. Only way out was to reboot, and hence brick
Click to expand...
Click to collapse
With respect Iv told you both ways to get into cwm
With the temp zip I provided by Flashing in stock rom or by Flashing a kernel with cwm built in
You have chosen to ignore all what I'm telling you & trying to do things in unconventional ways - Therefore I can no longer offer you support
Just flash stock rom via odin

I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative

bwizz60 said:
I was using the cwm downloaded from the the link that kindly supplied. I was using galaxy toolbox as suggested by yourself. There is lots of reading on the XDA site !.I am sure it is your prerogative to dismiss me as an idiot but I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
I said to use galaxy toolbox to unlock your phone - ie remove network sim lock if your phone is locked to a specific network
At no point did I say use it to flash cwm
If you can't get into recovery you need to flash stock rom via odin
I do have alot of patience but I find it annoying when people don't read things properly especially when the answers have already been written for them

I do appreciate your help. I am now following the odin info "supplied by yourself on the site"
Ta

bwizz60 said:
I am now following the odin info "supplied by yourself on the site"
Ta
Click to expand...
Click to collapse
That sounds sarcastic...
FYI, this Odin info can be found in his signature. It is also a sticky in the Android dev section.
Search, search, search.
bwizz60 said:
I am an enthusiastic phone tinkerer trying to find my way in an unfamiliar world of new termanology. If you don't have the patience to bear with people such as myself Then again that is your preragative
Click to expand...
Click to collapse
u wot m8
If you don't know what you're reading when it's filled with seemingly bizarre terminology (we've been at that stage one time or another), you do three things:
1) Read on and/or use Google.
Usually definitions will pop out after a while. If I'm not mistaken there are a few threads outlining terminology definitions and usage.
2) Follow everything that they say. And when I say follow, I mean follow 100%, by the book. Reread the instructions over and over to make sure you are actually doing it right.
3) PM another more well-informed member, and don't be afraid to ask.
As for patience, well...
He has dealt with countless people that were in about the same situation as you: thinking that they knew what they were doing and eventually getting into deep s**t with no way out. He has always tried helped them out. Problem is, some of them simply don't want to listen, even if he was correct (which he most likely was). Even then, he tries his best.
Trust me, he knows what he's doing.
Take a deep breath, reread EVERYTHING on this thread, and restart from square one: stock ROM.
If you're too lazy to find (I hope you're not) here is the link for Odin:
http://forum.xda-developers.com/showthread.php?t=2568853
Risky, but everything here is a risk, isn't it? I rarely hear of 5363 users getting stuck here, so this should be fine.
Good luck.

Why would I be sarcastic? there is volumes of stuff on the site all done by this guy.! I show appeciation of this . I can assure you I do spend hours trying to follow information. Some of the links don't work ,sometimes my Firefox security stops progress . very frustrating at times;.

Thanks Mr Smith, now unbricked. I could not find odin 3.184 "spent over an hour trying" 1.85 worked ok . Phone now wakes up as 5360! If the rom is less bloated than the 02 one .I might leave well alone! Stress level falling!

What he meant was Odin3 v1.84.
But, its nice to see things sorted out with your partner's phone.

I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!

bwizz60 said:
I 've had time to have a look at the standard rom Iinstalled. Glad the phone is working etc but I still have not achieved anything .
I still need to get rid of the samsung bundled stuff and be able to use the sd card storage. I am still unable to use CWM 5.0.26 "I get the code 7 error and the phone has re un rooted . Update ,Ive now re rooted it!
Click to expand...
Click to collapse
Root phone
Use Link2sd (playstore) to uninstall system apps
Use the temp cwm I posted a few pages back - place on root (not in any folder) of sd card & flash in stock recovery to get to cwm
Or use a custom recovery that has cwm built in eg hells fusion #50 for stock based roms
Can't give you any more support with this as I'm just repeating what Iv already said

Galaxy S4 SPH-L720T -> twrp, root, customrom and kernel(few questions!)

Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.

Oh one other problem I am having with the phone I was hoping a custom rom might fix, my Apps will not register as the correct size in Application manager. A 2gb game is showing up as 50mb total data, and when using "Move to SD Card" it only shows only like 200kb of data on the sd card, it does with with every single app on the phone. I know should not be like this because the last 2 phones I had were able to move every single byte of data from every one of the same exact apps to the SD card without an issue. Plus the application manager not registering the correct app size is just bugging me.

phenom2955 said:
Heyo, lets get started ruining this device even more! See if we can't brick it ey?
Anyways first off the battery is draining like a madman, 1% every 30 seconds or so. The thing is not getting the performance in games that it should be, using other devices with lower end hardware as a reference(1.1ghz quad core, adreno 305, 2gb ram one touch, and 1.2ghz quad core, adreno 306, 1.3gb ram kyocera), it keeps micro-stuttering while browsing chrome and doing basic actions with the UI, also when the battery is draining too(funny, sometimes while I have the charger plugged in and do basic activies such as chrome, youtube, read books, mess with menu settings the battery actually charges instead of deplete, but sometimes, seemingly always now, it depletes just as fast as though it was unplugged).
Anyways I have decided to try and customize the device with the plethora of information on here and all over the web for this device(after doing a lot more "research" of course and laying everything out for myself step by step to try to minimize failure.
First question is how much of a chance is there to brick the device installing TWRP alone? Really want to get that on there before doing anything, then install SuperSU from there with zip flash. And does it matter if I use a .tar or .img version of TWRP to flash with odin? The latest version of TWRP is in .img format and the tutorials I read say to use a .tar.
After that witch should I do try first, custom rom or custom kernel? What custom rom would be best at this point in time(5/13/2016) for this device, 100% compatible and fully tested. Also a kernel(unless overclocking can be unlocked within the custom rom, in witch case less chance of me ****ing up yet another android device).
One last thing, I really hope that even I am successful in doing all of this without ****ing up the phone that it does not turn out to be a fruitless effort, how much performance gains can I expect from all of this, custom rom, debloat after root, set sd as default storage after root(package does not belong to 2000 afterall), and then maybe a slight overclock on the cpu and gpu.
And thats all assuming that one day after getting all of this to work that one day I don't wake up and for no apparent reason boot up the phone and find its bootlooped or something without ever changing anything once all of this is done, I mean if I get the thing working as I would like it to work theres no more reason for me **** with it is there? Also I guess no reason to even have the thing if it aint gonna function how I need it to function right?
Thanks for the help though anyways, if anybody even decides to help me this time in a manner that they are not just "helping" just because the end result ****s me over.
Thanks again.
Click to expand...
Click to collapse
Well first it sounds like you need a new battery, I suggest having a couple and an external charger (it's great for gaming, just pop in a new fully charged battery). To install TWRP with Odin you need the tar file. The chance of Helicon with TWRP is almost zero, recovery is always overwritten when you flash a stock tar in Odin. So if something is messed up, just flash the stock tar and you are back to stock, grab it at www.sammobile.com . When you Odin TWRP make sure that you uncheck Auto Reboot in Odin. I would suggest my ROM as it is still being updated every few months, but I am biased. I use my S4 for gaming and this thing can handle PSP emulation when it is tweaked right.
Wicked X is my ROM and it's located here - http://forum.xda-developers.com/showthread.php?t=3115583
{
"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"
}

Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?

phenom2955 said:
Ok thanks, a little reluctant to install an OS with the name "Wicked" though.
Any ideas why the stock Application Manager is being wacky, done several factory resets. For instance I have installed Fifa 16 about 5 times now just to see if it would fix the data readout in App manager, the Game is at least 1.5gb total data, app manager shows it as about 50-70mb, when using "Move to SD Card" it shows about 700kb of data on sd card.
Whats the deal?
Also before flashing TWRP with odin I have to unlock bootloader or something?
Click to expand...
Click to collapse
No, bootloader is already unlocked. I can't tell you on the other without more information. What ROM are you on? Have you done any modifications? Have you Odined a full stock tar?

I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.

Nickvanexel said:
I bought this phone used on cl. Fully stock not a single mod on it as far as I am aware. The only thing I have done is factory reset.
It seems half the time as well when I Uninstall apps the data stays in misc section of storage manager. I have to go into recovery and clear cache and I get my space back. And misc section of storage manager will be back down to its normal size.
@ your comment about loader. You absolutely certain and no bs that if I attempt to flash something (even just twrp) it ain't gonna fail and go tit's up because I didn't unlock bootloader or something?
Just lost 2 phones already simply from uninstslling gltools after it failed to produce my desired results. Install went fine, but uninstslling rebooted the phones and got one caught in boot loop other just sits on manufacur er logo.
If asked why I was stupid enough to try it a second time I'll say I wasn't 100% sure it was absolutely gltools as the culprit.
Anyways this is the first device I have had with so much support with custom recoveries. Roms and kernels and even access to stock rom files. Would love to successfully apply some good stable/safe/and better running mods than the stock stuff though since I am convinced this hardware should be running better than it currently is!! But not trying anything for a while though till I've read as much as I can at least and have at least a few options for recovery should somehring go wrong.
Don't like being stuck with thumb up my ass stacking bricks, I am no mason.
Click to expand...
Click to collapse
100%, Sprint doesn't lock bootloaders (though Samsung has started to). You may have to turn off the an option in Settings/Security, I think it's called Write Protection, it won't let you Odin anything if it is on.

I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.

Mangodreads said:
I have a sprint sph-720T
I installed TWRP using ODIN
then reboot in recovery, put OCTOS-M on to internal memory and wipe the cache davik
install the OCTOS-M from zip file then install GAPPS from zip.
BOOOM! you have a rooted android 6.0.1 ! longer battery life.
EDIT: if you need direct links to the files, just ask.
Click to expand...
Click to collapse
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.

ABERBER1986 said:
Have you had any issues flashing the s4 to 6.0? It would be great if you added direct links. Thanks.
Click to expand...
Click to collapse
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro

Mangodreads said:
1. Put the Custom Rom Zip and the GAPPS zip on the phones memory card and then turn off the phone
2. Put the phone in download mode, connect to the computer via usb and run ODIN
Select AP and the select the TWRP recovery file. - Click Start - Once its finished
3. Put the phone in recovery mode - go to wipe, clear cache/davik a few times
go to install and select the Custom Rom Octos 6.0.1 that you put on the phones memory.
install it and then install GAPPS zip right afterwards
once those are installed reboot the phone and you are good.
These links are for user with Sprints galaxy s4 sph-720T ONLY
This is the TWRP recovery
https://dl.twrp.me/jfltespr
This link is to 6.0.1 Custom Rom by OCTOS
https://www.teamoctos.com/download/M_release/jfltespr/OCT-M-R1-6.0.1-20160319-jfltespr.zip
This is a link for GAPPS (google apps, playstore etc) - select the "variant" you want
http://opengapps.org/?arch=arm&api=6.0&variant=micro
Click to expand...
Click to collapse
Please advice which version of twrp you used. Because I am unable to flash thru through odin

bump........

earthworm82 said:
Please advice which version of twrp you used. Because I am unable to flash thru through odin
Click to expand...
Click to collapse
The link for teamoctos doesn't seem to work.

vikingjerr said:
The link for teamoctos doesn't seem to work.
Click to expand...
Click to collapse
You could just go their thread in the Android Development section[emoji6]

Wicked 10.9
bilgerryan said:
You could just go their thread in the Android Development section[emoji6]
Click to expand...
Click to collapse
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.

vikingjerr said:
I just downloaded Wicked 10.9 but am not sure I have all the files needed. In the first page it mentions to load the 720t conversion file and a kernal file.
Later I saw that the kernal file was include. I don't know if I should flash one, two or three files.
Click to expand...
Click to collapse
Three, the v11.0 update last.