Related
This post contains a complete firmware update package for N8013 UEALH2. It is based off the Kies images dumped by http://forum.xda-developers.com/showthread.php?t=1847706
It was rooted and the system image rebuilt using the guide at http://forum.xda-developers.com/showthread.php?t=1081239 - FYI partition size for N8013 is 1400M
The package is at http://d-h.st/8v0
This will give you a complete restore to stock UEALH2 plus root, without triggering the flash counter.
By complete, I mean EVERYTHING: Kernel, recovery, system, hidden/preload, cache will be returned to the same configuration as if you flashed UEALH2 via KIES - the only difference is root.
Use Odin to flash it.
Entropy will this my issues? Can you go take a look at my help thread and general and look at my picture of my download mode saying custom?
Sent from a Baked Black Jelly Belly
Entropy, will this work on my note even though i'm already running UEALH2? Got my update OTA last night before I had a chance to root it.
Also, if I'm able to use this and I root my device should I be wary about OTA in the future causing device malfunctions? In other words, what kind of update path should I follow in the future?
Sorry for the newb question. New to Samsung. Used to rooting and flashing and updating my old droid 2 global. Never did anything with my prime before I exchanged it for this and haven't done anything with my RAZR yet. I've kind of been flash cracker dormant for a while.
Sent from my GT-N8013 using xda premium
davidrules7778 said:
Entropy will this my issues? Can you go take a look at my help thread and general and look at my picture of my download mode saying custom?
Sent from a Baked Black Jelly Belly
Click to expand...
Click to collapse
Probably, however to reset DL mode to not be custom you'll need my TriangleAway support kernel (for now - Chainfire is going to integrate support into his app by including a compatible kernel for temp-flashing to reset). Flash it, run TA, then flash this and you should be on bone-stock except root.
BTW, this is a COMPLETE package including stock kernel and recovery. Once Mobile Odin supports this device (I gave Chainfire the info he needs to support N80xx) you can flash CWM and any kernel you want from rooted stock like this.
As to OTAs - In the past, many OTAs could be deployed safely to rooted devices as long as you weren't using CWM. However, Samsung seems to have switched to special incremental OTAs that patch the current binaries, so if even one of them is modified in any way, the update will fail. Happened to a lot of users with the last OTA.
Eventually you'll probably see custom firmwares that are deodexed and have the update-related APKs removed so you won't get OTAs.
OK so flash the kernel via Odin ? I am on the old injected rooted tar will it be ok?
Sent from a Baked Black Jelly Belly
---------- Post added at 04:20 PM ---------- Previous post was at 04:20 PM ----------
davidrules7778 said:
OK so flash the kernel via Odin ? I am on the old injected rooted tar will it be ok?
Then flash this?
Sent from a Baked Black Jelly Belly
Click to expand...
Click to collapse
Sent from a Baked Black Jelly Belly
Another newb question... will this wipe my data? And where can I download Odin for this device? Thanks
Sent from my GT-N8013 using xda premium
I hope it wipes my data and system! I feel like I need a wipe to get my pen working!!
Sent from a Baked Black Jelly Belly
Entropy512 said:
Probably, however to reset DL mode to not be custom you'll need my TriangleAway support kernel (for now - Chainfire is going to integrate support into his app by including a compatible kernel for temp-flashing to reset). Flash it, run TA, then flash this and you should be on bone-stock except root.
BTW, this is a COMPLETE package including stock kernel and recovery. Once Mobile Odin supports this device (I gave Chainfire the info he needs to support N80xx) you can flash CWM and any kernel you want from rooted stock like this.
As to OTAs - In the past, many OTAs could be deployed safely to rooted devices as long as you weren't using CWM. However, Samsung seems to have switched to special incremental OTAs that patch the current binaries, so if even one of them is modified in any way, the update will fail. Happened to a lot of users with the last OTA.
Eventually you'll probably see custom firmwares that are deodexed and have the update-related APKs removed so you won't get OTAs.
Click to expand...
Click to collapse
Hmm, if this fixes the S Pen on my tablet I'll be pleasantly surprised. If it's based on the image from jaaka, and ODINing that didn't fix the S Pen for me, would this be any different? I have the same issue as David, tried to root after taking the OTA and after installing CWM and rooting the S Pen stopped working. I've flashed the root injected stock image from zedo multiple times to no avail, and also the UEALH2 one from jaaka, as well as trying to update via Kies after installing the root injected stock image. Formatted data/cache and system too once, although flashing in ODIN should overwrite system completely, right?
Also, can we flash this in Heimdall? Or would you recommend against that?
iofthestorm said:
Hmm, if this fixes the S Pen on my tablet I'll be pleasantly surprised. If it's based on the image from jaaka, and ODINing that didn't fix the S Pen for me, would this be any different? I have the same issue as David, tried to root after taking the OTA and after installing CWM and rooting the S Pen stopped working. I've flashed the root injected stock image from zedo multiple times to no avail, and also the UEALH2 one from jaaka, as well as trying to update via Kies after installing the root injected stock image. Formatted data/cache and system too once, although flashing in ODIN should overwrite system completely, right?
Also, can we flash this in Heimdall? Or would you recommend against that?
Click to expand...
Click to collapse
I had weird issues when flashing with heimdall.
Try flashing this, wiping with STOCK recovery, and don't **** around with CWM until you're sure it's working.
Warning: I believe stock recovery is a full 100% wipe, including /sdcard (which is actually /data/media) - CWM takes measure to protect /data/media that might result in unclean wipes sometimes. This is why pershoot would always tell people to wipe in stock recovery if they had problems for example.
Entropy512 said:
I had weird issues when flashing with heimdall.
Try flashing this, wiping with STOCK recovery, and don't **** around with CWM until you're sure it's working.
Warning: I believe stock recovery is a full 100% wipe, including /sdcard (which is actually /data/media) - CWM takes measure to protect /data/media that might result in unclean wipes sometimes. This is why pershoot would always tell people to wipe in stock recovery if they had problems for example.
Click to expand...
Click to collapse
Wipe in stock recovery 1st? Also when I am on the rooted old firmware, the recovery reboot option doesn't work for me I have to old down power to reboot
Sent from a Baked Black Jelly Belly
Entropy512 said:
I had weird issues when flashing with heimdall.
Try flashing this, wiping with STOCK recovery, and don't **** around with CWM until you're sure it's working.
Warning: I believe stock recovery is a full 100% wipe, including /sdcard (which is actually /data/media) - CWM takes measure to protect /data/media that might result in unclean wipes sometimes. This is why pershoot would always tell people to wipe in stock recovery if they had problems for example.
Click to expand...
Click to collapse
Alright, will do that then. Still waiting for it to finish downloading, seems like dev-host is not that fast unfortunately (or maybe I'm just spoiled by university internet and 4G). I did wipe with stock recovery once during my couple hours of trying to fix my tablet and it didn't seem to help. I probably won't try flashing CWM or rooting again for a while until I can get confirmation from others that it doesn't break the S Pen again. The thing I wanted to try (Screencast) worked but was somewhat unimpressive in terms of quality so I don't need to show it to the person I wanted to show it to (plus without S Pen it's less useful for my specific use case).
iofthestorm said:
Alright, will do that then. Still waiting for it to finish downloading, seems like dev-host is not that fast unfortunately (or maybe I'm just spoiled by university internet and 4G). I did wipe with stock recovery once during my couple hours of trying to fix my tablet and it didn't seem to help. I probably won't try flashing CWM or rooting again for a while until I can get confirmation from others that it doesn't break the S Pen again. The thing I wanted to try (Screencast) worked but was somewhat unimpressive in terms of quality so I don't need to show it to the person I wanted to show it to (plus without S Pen it's less useful for my specific use case).
Click to expand...
Click to collapse
i know it is slow, we need a torrent LOL or on that other site that the other firmware was on,
Entropy do u mind if i mirror it on another site like the previous one? I have a pretty fast upload stream
davidrules7778 said:
i know it is slow, we need a torrent LOL or on that other site that the other firmware was on,
Entropy do u mind if i mirror it on another site like the previous one? I have a pretty fast upload stream
Click to expand...
Click to collapse
Do you have the whole thing downloaded? My download died at about 70% . Trying to download it from an EC2 instance now too, I'll see what happens I guess.
iofthestorm said:
Do you have the whole thing downloaded? My download died at about 70% . Trying to download it from an EC2 instance now too, I'll see what happens I guess.
Click to expand...
Click to collapse
I just started downloading it lol
Sent from a Baked Black Jelly Belly
Looking forward to trying this. Getting the same issue on downloading though. First attempt showed finished, but was corrupt when I tried to open. I have 50Meg service but can only get about 33KB/sec download grabbing this thing. Lol.
will have to try later when not over loaded or whatever. Annoying!!! Need a better site!!
I hate the post-MegaUpload era...
Entropy512 said:
I hate the post-MegaUpload era...
Click to expand...
Click to collapse
Ya lol, i really want to try this..
I can always seem to get touchscreen working again after installing your stock recovery/kernel but no pen, I am hoping this will fix my issue cause i have tried it all
i put clockwork on and tried wiping and nada question in order to wipe do u have to mount first in clockwork? I am use to twrp.
if that is the case i will give that a shot.
Entropy512 said:
I hate the post-MegaUpload era...
Click to expand...
Click to collapse
I think I've tried 5 times and each one failed partway through. Do sites like goo.im not let you upload files that big?
What about the site that the other guy used, http://www.peejeshare.com/ ?
ya i tried a lot too,
I also have tried every method in getting the pen to work, and always either get no touch screen or no pen.
I have tried wiping, different orders, flashing clockwork and wiping all in there.
NADA no pen
Shoulda of just waited to root til this came out officially.
I might have to throw in the towel if this tar doesn't work and and send it back after clearing the binary count.
Unless someone has another idea?
UPDATE: My hosting I had for XDA related work expired, so I re-uploaded everything here: http://www.mods4cars.com/pub/xda
Here's the new Verizon OTA packaged up as a full CWM flashable ROM. Wiping should not be necessary if you are coming from our last ICS ROM (LP10).
This is meant for those who have CWM installed and for those who modified their system to the point that the OTA does not work because it expects certain files.
If you are on full stock (rooted) ICS LP10 and are not getting the OTA update the regular way, you can look here for a way to manually install it:
http://forum.xda-developers.com/showthread.php?t=1932597&page=26
The rom is pre-rooted. After installing, run super-su and let it check for binary updates. Also a cached copy of su for restoring with Voodoo OTA rootkeeper is included (for extra safety).
Part1: The ROM
Install with CWM
http://electron73.org/XDA/i815/electron_ICS-LP11_i815.zip
Part2: The MODEM
Flash with ODIN in PHONE section
http://electron73.org/XDA/i815/electron_ICS-LP11_i815_modem.tar
Part3 (optional): Stock Recovery
If you want to be full stock afterwards, flash with ODIN in PDA section
http://electron73.org/XDA/i815/electron_ICS-LP11_i815_recovery.tar
Part4 (optional): Stock SBL
If you did all 3 parts above and want to be able to receive future Verizon OTA's flash this in ODIN in BOOTLOADER section
http://electron73.org/XDA/i815/electron_ICS-LP11_i815_sbl.tar
Enjoy
Many thanks!
Thanks Electron. You da man for us i815 owners.
Many thanks! I just decided to go back to stock for stability reasons. Your method works perfectly.
I don't know where many of us i815 users would be without your help. Thanks again man!
Sent from my Galaxy Nexus using xda premium
Gilbot said:
Many thanks! I just decided to go back to stock for stability reasons. Your method works perfectly.
I don't know where many of us i815 users would be without your help. Thanks again man!
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
So I was installing the ROM zip in CWM and it froze at "double-checking /data partition." Am I hosed?
esoh said:
So I was installing the ROM zip in CWM and it froze at "double-checking /data partition." Am I hosed?
Click to expand...
Click to collapse
How long did you wait?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
electron73 said:
How long did you wait?
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
20 mins or so. I was getting no movement on the status bar. I rebooted and I can get into Odin mode and I was able to get into CWM once, but that's it. Otherwise it just hangs on the Samsung Galaxy Tab 7.7 screen.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
esoh said:
20 mins or so. I was getting no movement on the status bar. I rebooted and I can get into Odin mode and I was able to get into CWM once, but that's it. Otherwise it just hangs on the Samsung Galaxy Tab 7.7 screen.
Click to expand...
Click to collapse
So I wound up getting back into CWM and tried reflash and it's going now. Will let you know result
esoh said:
20 mins or so. I was getting no movement on the status bar. I rebooted and I can get into Odin mode and I was able to get into CWM once, but that's it. Otherwise it just hangs on the Samsung Galaxy Tab 7.7 screen.
---------- Post added at 09:17 PM ---------- Previous post was at 09:12 PM ----------
So I wound up getting back into CWM and tried reflash and it's going now. Will let you know result
Click to expand...
Click to collapse
Did you have lots of apps installed? I just realized it's doing a run_program("/tmp/fsck.ext4", "-Dfy", "/dev/block/mmcblk0p10");
on the data partition. If that partition is full with lots of files then the check might take a while. The status bar doesn't move while this command is executing. I never tried it on a "full" partition! A freshly wiped data partition is checked in 2 seconds
electron73 said:
Did you have lots of apps installed? I just realized it's doing a run_program("/tmp/fsck.ext4", "-Dfy", "/dev/block/mmcblk0p10");
on the data partition. If that partition is full with lots of files then the check might take a while. The status bar doesn't move while this command is executing. I never tried it on a "full" partition! A freshly wiped data partition is checked in 2 seconds
Click to expand...
Click to collapse
Yeah, I had about 100 apps installed. In any case, I tried it again through CWM. When it did the check this time, it took about 10 secs. So the first one must've been a hiccup or something. I was able to flash ROM and then radios through ODIN, so I think I'm good. I looked at the files on the internal storage and the SD card and they are still there, so I'm assuming that I'm good. Anything else to check or are there any log files that you want me to try to grab for you? Thanks again.
esoh said:
Yeah, I had about 100 apps installed. In any case, I tried it again through CWM. When it did the check this time, it took about 10 secs. So the first one must've been a hiccup or something. I was able to flash ROM and then radios through ODIN, so I think I'm good. I looked at the files on the internal storage and the SD card and they are still there, so I'm assuming that I'm good. Anything else to check or are there any log files that you want me to try to grab for you? Thanks again.
Click to expand...
Click to collapse
Hmm ok, definitely good to hear that it ran through the 2nd time. Maybe I should kick the FS checks out. They are still left over from last time where we had all those partition problems...
If you want, go check in the /cache dir for any log files left by CWM, maybe there's something in there.
Btw. Thank you for the generous donation! It is very much appreciated
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
electron73 said:
Hmm ok, definitely good to hear that it ran through the 2nd time. Maybe I should kick the FS checks out. They are still left over from last time where we had all those partition problems...
If you want, go check in the /cache dir for any log files left by CWM, maybe there's something in there.
Btw. Thank you for the generous donation! It is very much appreciated
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Click to expand...
Click to collapse
I think the logs from the successful install are there but I don't see anything from the unsuccessful one, as far as I can tell.
RE: the donation, I meant to give you something from the original LP10 update and I just plumb forgot (after telling you that I was going to send something), so I figured that there was some interest involved. Thanks to all of your hard work.
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
esoh said:
I think the logs from the successful install are there but I don't see anything from the unsuccessful one, as far as I can tell.
RE: the donation, I meant to give you something from the original LP10 update and I just plumb forgot (after telling you that I was going to send something), so I figured that there was some interest involved. Thanks to all of your hard work.
Click to expand...
Click to collapse
Also, regarding the current ROM, I really curious about the supposed batt life increases. My tab at this point is barely getting 4-5 hours screen time with it set fairly dim. Is that normal or should I be getting more that that? I don't suppose that a ROM update will help with screen time much, but just curious to hear what others are getting.
Update was painless
Sent from my SCH-I815 using xda app-developers app
My battery life is just shy of 8 hours with 40% brightness, wifi and 4G on. GPS off. This is better than LP10.
The first step went flawlessly using TWRP. I'll flash the LP11 modem.bin tonight using Odin.
Thanks for this, Electron. I'm about to make another small donation to your beer (or whatever) fund!
jkrell said:
The first step went flawlessly using TWRP. I'll flash the LP11 modem.bin tonight using Odin.
Thanks for this, Electron. I'm about to make another small donation to your beer (or whatever) fund!
Click to expand...
Click to collapse
I have never tried TWRP on this tab. What's the current version for our i815? Does it work well? I assume just like CWM it doesn't accept stock OTAs though, does it?
I still keep going back to stock recovery in order to accept OTAs (which never come for me haha and I end up updating manually!)
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
electron73 said:
I have never tried TWRP on this tab. What's the current version for our i815? Does it work well? I assume just like CWM it doesn't accept stock OTAs though, does it?
I still keep going back to stock recovery in order to accept OTAs (which never come for me haha and I end up updating manually!)
Click to expand...
Click to collapse
It was hard to flash (the apk method didn't work, I had to use Odin -- which really is no big deal, just scary for some). In any event, I'm running 2.3.10 available here: http://forum.xda-developers.com/showthread.php?t=1809295
I love TWRP... so much easier than fumbling with the volume and power buttons.
Never tested with OTA because I rely on you! :good:
I like TWRP but wish it could mount my encrypted /data partition like it could for my Nexus 7.
Stuck on 4G LTE Boot Screen
I'm going back from CM10 but after flashing ROM I'm now stuck on the Verizon 4G LTE screen. Not sure what you recommend?
mindstream98 said:
I'm going back from CM10 but after flashing ROM I'm now stuck on the Verizon 4G LTE screen. Not sure what you recommend?
Click to expand...
Click to collapse
Did you wipe data/cache? Coming from CM10 you definitely need to do a clean install. You can simply flash the "wipe" version of the LP10 rom first, then upgrade to the LP11
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
I'm buying you dinner tomorrow (well, I hope the donation I send you will ) ROM and modem installed without a single hitch. Only thing that caught me off guard again was the modified hosts file, bit I fixed that. Wife is happy! Thanks for your work on this.
When should you do a full wipe when installing a custom rom and when is it ok to dirty flash? Can someone please explain?
Sent from my HTC One using xda app-developers app
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
lampel said:
If you're changing bases it's always good to wipe. And if you're changing roms you should always wipe. But if you're just applying an update you might get away with a dirty flash. Save a backup first and you don't risk much with a dirty flash.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
easyrabbit said:
I apologize if this is a stupid question. When you say change base what exactly do you mean? Is this from one rom to another or a version change on the same rom like 5.0 to 6.0? Or is it a kernal change? If it is a version change would 5.1 to 5.6 be considered changing base?
Thank you very much. Again, I apologize if this is a dumb question. I have read around a little and did not quite get an answer I was comfortable with.
Click to expand...
Click to collapse
What rom are you using?
CYNiCAL2KX said:
What rom are you using?
Click to expand...
Click to collapse
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
Click to expand...
Click to collapse
Sorry I meant ViperOne...
easyrabbit said:
I am using VenomOne 5.7.0 but it is more of a general question. I am a bit new to this and want to have a good understanding of everything from the ground up.
---------- Post added at 08:31 AM ---------- Previous post was at 08:23 AM ----------
Sorry I meant ViperOne...
Click to expand...
Click to collapse
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
Thank you very much for the info. So now I understand what the base is. Aside from time or laziness I would think that doing a full wipe is the way to go. Maybe I am wrong but I would rather not take chances.
Right now Iam currently having some issues. I basically did a dirty flash of the same version I am on to clear the theme and it went wrong. It never came back up after an hour in the "starting applications" state. After that I got back in to recovery (TWRP) and did full wipes and installs. They seem to go OK but then the android setup crashes right after the "name your device" part and the launcher wont start (chose Nova). Everything just hangs. I reboot but then it just hangs. I just did my nandroid restore and I am back up and running but not sure what is going wrong. I tried the install a few times with different options but everytime the setup part crashes. So my simple question is now another full blown issue haha.
I love this board tho, everyone is so helpful. One day I hope to be the one giving the advice.
CYNiCAL2KX said:
'4.19.401.8' that is the current base which is in use by viper. Sometimes it's okay to flash, it's trail and error.
Always make a Nand before you flash, incase anything goes wrong, you can go back to the previous version, like a windows restore point.
A fresh install is wiping data and cache in TWRP it's called a factory reset. This doesn't format the /sdcard/0 so all sd card data remains.
If you were to flash a older base with a newer one, it may work perfectly, it may not, what I do is: Create a Nandroid of system,data,boot. Wipe, then install, then I restore data only. This way the phone tends to be (fairly) just how you left it, with messages, apps etc still remaining.
Like I said, after making a Nand, just flash unless the OP says specifically not to. Then if you have issues, it's a simple case of rolling back by restoring Data, System. I hope this answers your question, I think you'll just get the hang of how it works just by actually giving it ago, not much can really go wrong unless you start flashing things not meant for your phone.
Click to expand...
Click to collapse
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
easyrabbit said:
May I ask, is restoring the data folder similar to adb backup/restore or even titanium? With titanium I could just restore messages or whatever. Doing the whole data folder could put back something I dont want or something I want to get rid of. With my current situation I think this might solve my issue with setup but I really wanted to start from scratch and retweak everything.
Regarding the base, I cant seem to find where I can check that on the device. It is not in settings-about where I would expect to find it.
I am finally working my nerve up to try this again and figure out why the initial android setup is crashing. I am getting more comfortable now especially since I know my nandroid restore works. Good fun but scares the hell out of me at the same time when things go wrong haha....
Click to expand...
Click to collapse
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
CYNiCAL2KX said:
Ususally most issues regarding cross flashed bases are problems derived from the system partition, however i'm not saying it doesn't happen, but I've never really had many issues restoring data. Also, once you back up data , you can install a Nandroid manager app where you can restore certain things from nand backups. This is what I chose to use over things like titanium as it's just another thing to do
Click to expand...
Click to collapse
Thank you very much. I have heard back and forth on wiping the system but had never done it till now. I am still not sure what was happening. in my initial installs I allways removed sense and used Nova. The last time I left Sense and most off the apps. I also 're-downloaded the zip. it worked like a charm. soon I will start investigating kernals and updating firmwae and antennas. Will play with the basics for a while first tho. eventually I would like to try my own. However the bar is set high with venomone.
I am now dealing with sense which is ok bit for me Nova is as close to perfect a launcher for me. still investigating battery lifevetc but will probably do another flash removing sense. venomone fixed everything I didnt like about it for the most part but I love to be able to swipe up or down anywhere to get quickbar and app drawer... still testing tho, I have a full life but definitely want to contribute here... my new obsession.
Just tried it and it reset the stats.
It does? I thought Chainfire said he was having issues with Knox and it might not ever work for our device? But this is great freaking news and I hope it's true. Anyone else confirm this.
This message brought to you in part by Sprint and the letters GS and the number 4
---------- Post added at 04:34 AM ---------- Previous post was at 04:30 AM ----------
Okay looks like it does work. One question. Can you get the device status to official? I can't access a app for work when my device status is not official so I have been not been able to root my device until this app fixes that.
This message brought to you in part by Sprint and the letters GS and the number 4
Yep, but I also have knox frozen with titanium backup. 0/official
And I have oudhs recovery and it's still good. The results I'm getting now are better than previous official roms with ta.
Please, can anyone else confirm this? I have been awaiting this news for some time now and just need a little more proof that I can safely run it on my Sprint SG4 with MF9.
TIA
Worked...but after reboot, Download mode shows Original, Binaries shows Custom, and phone status shows Custom. Triangle Away still shows 1. I am stock except for Hotspot mod.
Always-Learnin said:
Please, can anyone else confirm this? I have been awaiting this news for some time now and just need a little more proof that I can safely run it on my Sprint SG4 with MF9.
TIA
Click to expand...
Click to collapse
3.05 is working. Just ran it and counter has been rest. "Must be on a stock (Samsung) kernel,or you will soft-brick or boot-loop and will need to reflash your firmware."
Confirmation working but after first boot device status says scanning then goes back to custom.
I'm full stock rooted only, no mods.
So it's good to reset and flash to 100% stock it seems. Unless it is just something with my s4? If others can confirm this? Still happy that it works.
I'll freez knox and see what happens.
Like I said before, I'm running stock rooted odexed mf9 oudhs recovery and stock kernel. When I boot into download mode it says official official. Any other combinations of things that other people are running, could or could not work or work the same as me. Different kernels, recoveries, etc. I just checked in titanium backup and I have both Knox apps backed up but frozen so they're not running. Your mileage may vary. My counter, when triangle away polls it, used to be 4. Now it's 0. Like the warning screen in ta says, custom recoveries and kernels could muck things up. I took a chance with oudhs recovery and got the empty chamber.
For those thinking about changing recoveries, I've had zero problems since I first installed oudhs recovery. MDC, MDL and mf9. The only thing I see that might be missing is the ability to set the time and date for nandroid backups. I've flashed the hotspot mod before with no problems. I've flashed a custom ROM with no problems (I forgot which rom). I flashed a custom kernel and the reboot mod and the phone didn't like it. I don't think it's the Recovery's fault but I'm not certain. My phone could just be really picky about what custom things are on it.
patrockss said:
Confirmation working but after first boot device status says scanning then goes back to custom.
I'm full stock rooted only, no mods.
So it's good to reset and flash to 100% stock it seems. Unless it is just something with my s4? If others can confirm this? Still happy that it works.
I'll freez knox and see what happens.
Click to expand...
Click to collapse
Same results here, and I froze Knox before trying it. It did say all official on the first boot. So I guess this would be a way to get it official if you needed to for whatever reason, but you might have to install the stock recovery to get it to stick. I'm using the latest release of TWRP 2.6.5, I believe. MF9, stock rom, rooted.
I did a little more playing around with this. It stays all official as long as I don't go into TWRP. That always sets the binary back to 1.
If I cared more, I'd be tempted to load OUDHS again and try. But I like TWRP, so staying with it for now.
jejb said:
I did a little more playing around with this. It stays all official as long as I don't go into TWRP. That always sets the binary back to 1.
If I cared more, I'd be tempted to load OUDHS again and try. But I like TWRP, so staying with it for now.
Click to expand...
Click to collapse
Oudhs behaves the same way. It's not flashing something that trips the counter, it's going into custom recovery. Thanks for pointing that out. I just discovered something I didn't know.
i have Hotspot mod with MF9 and twp. if i go back to stook recovery can i get it to show stock on all settings or will the Hotspot Mod trigger the custom under settings for device status?
cwb1231 said:
i have Hotspot mod with MF9 and twp. if i go back to stook recovery can i get it to show stock on all settings or will the Hotspot Mod trigger the custom under settings for device status?
Click to expand...
Click to collapse
This is my setup also...I think that rentering TWRP is tripping the counter as indicated above. Download Mode shows "Custom" Binaries and Status shows "Official." Under About Phone I still have 1.
Sent from my SPH-L720 using Tapatalk 2
Flashing in recovery doesn't trip the counter and change to custom, booting into custom recovery does. I booted into recovery and didn't flash anything and it tripped the counter.
So if you use recovery, just go back into triangle away and reset everything and it should stick (until you boot in recovery again).
After TA I still have custom under device status. Is there any setting that will allow me to have this read official (apart from inheriting?)
Sent from my GT-P3113 using Tapatalk 4
---------- Post added at 07:30 PM ---------- Previous post was at 07:26 PM ----------
Unrooting sorry for auto correct
Sent from my GT-P3113 using Tapatalk 4
I have not used twrp for very long. I've read that some people had problems with previous versions. I don't know how stable it is now. It's your choice if you want to stay with that recovery or try another, just to get it to read Samsung official and zero flash count and stay that way after reboots (unless you go into into custom recovery that is).
Also, maybe the way I set my phone up might, or might not, have something that's different with yours. I did, with PC Odin, a full mf9 tar flash, chainfire root, then oudhs recovery. Before I rooted it, but after the main ROM flash, I did a full factory reset in the phone settings, in account section. I did a reboot into the normal phone running mode, then shut down after a couple minutes to let the installation settle down. I flashed the hotspot mod with custom recovery. I don't know if motochopper works because I've never used it. I've only ever used the chainfire PC Odin tar method. Just sharing this info so maybe, if anyone cares, we can possibly come up with what works and what doesn't and how the phone was flashed and set up. One person said they have twrp on stock rooted and it's working for them. Another person has a similar setup but it isn't working as good for them as it is with the first guy. More information given, easier to determine what is or isn't happening.
cwb1231 said:
After TA I still have custom under device status. Is there any setting that will allow me to have this read official (apart from inheriting?)
Click to expand...
Click to collapse
Probably not. If running it does not set it to all official, assuming you've NOT gone into any kind of custom recovery since running TA, you may have some combination that will not allow it to be reset.
---------- Post added at 07:29 AM ---------- Previous post was at 07:23 AM ----------
oscarthegrouch said:
Flashing in recovery doesn't trip the counter and change to custom, booting into custom recovery does. I booted into recovery and didn't flash anything and it tripped the counter.
Click to expand...
Click to collapse
Correct. I was bored yesterday, so put OUDHS recovery back on and did some more testing. Same, same.
So if you use recovery, just go back into triangle away and reset everything and it should stick (until you boot in recovery again).
Click to expand...
Click to collapse
Yep. I do nandroid backups fairly often, so it would not be worth it to me to do this each time I came out of TWRP. But I can for sure see using, and am glad it's available, in case I ever need to worry about a warranty claim. Of course, I'd probably just go back to stock MDL or MF9 in that case anyway, I guess.
thanks for the explanations. my knowledge level of rooting et al is that of a moderately well trained chimp. i can follow directions but not completely sure why i am doing something. i realize this is a little off topic but you have all been so helpful i will forge ahead. i am wondering why i need custom recovery rather than stock recovery. is it necessary because i am rooted or could i use the hotspot mod and then revert to stock recovery. i have no real desire to do any further tweaks (unless i can get this thing to pay my bills without charging my bank account). Also if my phone crashes and i wnat to bring it back for warranty do i need custom recovery in order to go back to stock rom or can i do that with stock recovery? thanks again.
cwb1231 said:
thanks for the explanations. my knowledge level of rooting et al is that of a moderately well trained chimp. i can follow directions but not completely sure why i am doing something. i realize this is a little off topic but you have all been so helpful i will forge ahead. i am wondering why i need custom recovery rather than stock recovery. is it necessary because i am rooted or could i use the hotspot mod and then revert to stock recovery.
Click to expand...
Click to collapse
Good questions. I've not used the stock recovery much, so not all that familiar with it. But the custom recoveries do give you options you don't have in the stock one. I don't think the stock one gives you the ability to do a Nandroid backup, for example (not sure on that, though).
Here's where you can get a .zip of the MF9 stock recovery, if you want to try it. You'd need to install it via your current recovery:
http://forum.xda-developers.com/showthread.php?t=2357471
Also if my phone crashes and i wnat to bring it back for warranty do i need custom recovery in order to go back to stock rom or can i do that with stock recovery? thanks again.
Click to expand...
Click to collapse
The stock recovery would install it from a .zip. But for sure you can use ODIN to do it from a .tar or .tar.md5 file. If you haven't used ODIN yet, install it on your PC and get familiar with it. Very easy to use.
EDIT: I just installed the MF9 stock recovery from the link above just to see. It does not have the backup/restore option, as I thought. Nandroid backups are awesome, too. TWRP also gives you a file manager, log export, fix permissions, ADB Sideload, terminal command, etc. So lots of nice tools compared to the stock. Stock only gives you a few "apply update" and wipe data/cache options.
thanks i did just install the stock recovery on my phone so i can restore if needed. i figured that it was pretty limited so keeping custom for now makes sense so i can make back ups. i am afraid to mess too much with anything because i won't know how to fix it if i crash it. i used odin to root and now have mobile odin so if i need to hopefully i can install the stock recovery if needed right from the phone.
As I've learned from my past mistakes, with this phone, which I continue to make from time to time, is to make a nandroid backup before flashing anything. Yeah it takes more time, but if something messes up, you have a backup ready of your most recent install and apps.
Hey guys, could you please give me a hand? I'm really new so forgive me if I don't express myself correctly!
I was trying to instal CM12, and an error ocurred during instalation and it said "instalation aborted" or something like that. After that it only stays in CWM and I can't reboot. I've wiped cache and dalvik numerous times but it's always the same. I also did factory reset and nothing. I can't seem to load another ROM because the SD drive doesn't show up in my computer even though the phone is conected. What else can I try?
Please help me get out of this, I'm a little freaked out =/
Please? I'm clueless
I'm thinking I need to try to flash the stock ROM with Odin...but I can't enter download mode because as soon as I put the battery in, it reboots to recovery mode. Any ideas?
Thanks!!
if you did nandroid backup before flashing you should be able to flash that, you would be better off using twrp for flashing this rom
I didn't do nandroid backup, it wasn't a step in the guide (http://forum.xda-developers.com/showthread.php?t=2400123)
So I hope I'll be able to flash it anyway? I'm following these steps now: http://forum.xda-developers.com/showthread.php?t=2159660
I figured the problem was using CWM and not TWRP =/
ok, let us know how you get on. always follow instructions for each rom, and do backup just incase a problem arises. what rom were you using before trying to flash this one?. dont forget cm12 is based on lollipop which isnt really meant for our phone.
Thanks! I'm downloading a stock rom, but it's taking forever. Is it normal that it downloads at 40 kbps? It's taking like 4 hours this way =/ I suppose there is nothing faster except paying for a premium account? I also tried it from other sites but download speeds are terrible. My connection is not so bad...
Anyway, I had CM 11. Once I get ti back (fingers crossed) I figure I'll try CM 12 again, this time with TWRP.
Thanks for the help!
ok, go here....http://www.sammobile.com/....and d/l the latest firmware for your region & carrier, then flash using odin, dont flash a stock-based rom, this will take ur fone back to original, then root & flash custom rom......carefully....
It worked!! Finally!! Thanks a lot, I'll do it more carefully next time, but I'll be stuck with this stock ROM for a little while. One last question, how important was it that it wasn't the one for my country? I didn't find one and I flashed a Romanian one...phone is working fine though!
Yea should be fine, glad I could help, walk before run, take it easy... Enjoy the ride....
Sent from my GT-I8190 using XDA Free mobile app
Seleuco said:
It worked!! Finally!! Thanks a lot, I'll do it more carefully next time, but I'll be stuck with this stock ROM for a little while. One last question, how important was it that it wasn't the one for my country? I didn't find one and I flashed a Romanian one...phone is working fine though!
Click to expand...
Click to collapse
All rom's are multilanguage, only difference you can see in baseband. Sometimes on different contries basebad can work more stability than others. Thats all.
If you want experiment wtih install some custom rom use twrp from novafusion site. Its bringing to use with different filesystem and give to you simple and easy manager to get backup your data and get it back when something goes wrong. Remember, Do backup your Efs/imei, boot before flash something on external memory. If you loose without backup this data, you get tablet to tap on something without calling, mobile internet, wifi.
Sent from my GT-I8190 using XDA Free mobile app