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?
Related
NEXUS 7 3G-"nakasig" - Jelly Bean/KitKat Discussions, Problems and Solutions
Hi Nexus 7 "Nakasig" users,
I would like to consider this thread as your one place to chat or anything else related to Jelly Bean on the NEXUS 7 - 3G
I need everyone help to keep this thread somewhat sane, report any trolling or flaming and don't respond to it.
Keep all your posts in this thread polite and make sure you follow The Forum Rules.
I request you to stop posting:
- 'Thanks this helped'
- 'Yeah Me too'
-'+1'
These kind of posts are useless instead use the thanks button to show your appreciation
Click to expand...
Click to collapse
For all your JB needs, go to:
==>[Index] All for NEXUS 7 - "Nakasig" - (GSM/HSPA+)
==>[GUIDE] Unlock and Root a Nexus 7 3G “Nakasig- Tilapia”
==> [GUIDE][BOOTLOADER][4.3] TILAPIA JWR66V - 4.23 Flash Image Instructions - UPDATE
==>[GUIDE]If you need some help for install SDK and ADB drivers in Win 7, you can use this guide which is really good and comprehensive for all of us
It will be better for you to find one thread where we can concentrate all discussions, problems and solutions for the Nexus 7 3G
It 's a tool which is very good if you want to buy a Google Nexus Devices :good:
Google Nexus Devices World Availability Checker
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
WarningHPB said:
Top man!
Any one got a working recovery and supersu/superuser that works with 4.2?
Since I've heard people losing 3G and stuff when they rooted, and I kinda don't want to have to set my stuff up again
Click to expand...
Click to collapse
You've probably heard that from idiots who don't know what they are doing.
The latest version of TWRP works perfectly fine with 4.2 (3G and not). I'm using it on my 3G without any issues.
And the previous 'su' binaries and apk's should be fine. Neither of them should cause any problems with the 3G functionality as they have nothing to do with it. I installed custom recovery and rooted mine the day I got it. Everything is perfect.
Also, absolute worst case scenario, if you do screw something up, it's easy to revert without losing all of your data.
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
dave_uk said:
Hmm...I don't consider myself an idiot but did nothing more sinister than root and flash CWM and lost cellular data functionality completely at random two days later (unknown baseband). Had about 6 Android devices before this going back to HTC Hero, flashed all sorts, and never seen anything like it. Eventually had to flash factory image to get it back. Not especially helpful as inexplicable and not reproduced but worth saying nonetheless.
Click to expand...
Click to collapse
FYI, there seems to be a sporadic bug in JB on my GNex where on certain reboots it says Unknown Baseband and IMEI in the About menu, and then on the next reboot it's fine. I am wondering if that same bug is cropping up on the N7, and it's just coincidentally happening on some people's devices after rooting, but it goes away later. On my GNex this issue is particularly noticeable if I gave the phone a full reboot from inside software (e.g. using the app Easy Reboot). Whereas a power off / power on does not as frequently run into this issue.
I'm looking forward to getting mine Ordered today and it shipped today! I'm going to give my 16gb (bought in Aug for $249 so no price mod for me ) to either my GF or my daughter. lol
Sorry for the OT post.. I'm just excited. It will be nice to not have to tether my N7 to my phone. I just switched to the shared data plan on AT&T so it will only cost me $10 to add the N7 to my plan
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
kitsunisan said:
Just fired up my 3g and will root it tomorrow, is there anything really different in rooting this thing vs the 16gb, anything I should watch out for?
Click to expand...
Click to collapse
No, they are identical from a rooting perspective. However, they do run slightly different versions of the image, so if you wind up flashing stock, use the right one.
so first my success, i have managed to get root and a TWRP recovery.
now my question in menus im seeing horizontal lines that move with the landscape. so as the phone rotates the screen, the lines also rotate. maybe its just the background design but it seems really awkward to me that they would intend from these lighter brighter lines to be there
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
death 90 said:
if someone would do me a HUGE favor and get me a stock JVP15S recovery? i flashed over mine with CWM before i could back it up and now i have a 34mg OTA update i cant take because of the custom recovery image
Click to expand...
Click to collapse
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
philos64 said:
I'm not sure that you will find someone who can give you this file, cause it contains all personal data and apps.
Click to expand...
Click to collapse
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
cmstlist said:
I don't have my N7 yet, but on most Androids the stock recovery images do not vary much or at all between minor upgrades, so any stock recovery should be fine. Try the recovery.img inside the JOP40C image straight from Google. https://developers.google.com/android/nexus/images#nakasigjop40c
Worst case if the update still won't take, flash both system and boot from the stock image too (this will unroot you but so would the OTA, and you can fix that later), and then you'll be stock enough for OTAs to work the next time it prompts.
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
cmstlist said:
The recovery partition does not contain any personal data or apps. Everything personal is in /data.
Click to expand...
Click to collapse
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
ya i grabbed it thanks. what i don't understand is what the 34mg update is for? any ideas? i uploaded two shots, one settings page showing the build mine shipped with and the other is just the update screen i got showing size. Im about to flash the stock ROM from google now. we'll see how goes
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
death 90 said:
im pretty sure the "recovery" partition doesn't contain any of those things. i don't want a stock rom, i need stock a recovery. twrp allows you to back up certain partitions such as boot, cache, and recovery
i just downloaded that ill try flashing it now i downloaded the "Google Nexus 7 Toolkit" and while it didn't work for me, it did provide a JRo03d stock recovery which i flashed with fastboot and that recovery did not work. when you nexus 7 arrives i believe it would be possible to recover the stock recovery using "fastboot boot twrp-recovery", ALTHOUGH im not sure when you would execute the "backup recovery" if it would read the phones actual partition or the image you uploaded and booted on
Click to expand...
Click to collapse
Honestly don't try toolkits. Just don't, because you don't know what commands or files they are really flashing, and especially because they were written for the wi-fi version. The stock recovery from the wi-fi version is not guaranteed to be compatible with the 3G version.
philos64 said:
Sorry for my quick answer, I haven't seen the "recovery.img". that's file system.zip or tar which contains apps and data for restore
And if you want the Factory image, go to the thread : [Index] All for NEXUS 7 - "nakasig" - (GSM/HSPA+) , it is on, ready for download
Click to expand...
Click to collapse
System.img is also devoid of personal information because to the standard end user it is write-protected. All the personal stuff is in the data partition.
death 90 said:
the 34mg update was "signed-nakasig-JOP40C-from-JVP15S". i was able to flash the recovery from the stock ROM JOP40C and use that to patch through android and avoid flashing usuing TWRP
Click to expand...
Click to collapse
Glad it worked out for you. I had a feeling it was just going to give you JOP40C anyway.
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
spongers said:
So, I have been trying to root my 3G tablet (JOP40C), but have no luck. I installed TWRP and unlocked just fine using the Google Nexus 7 ToolKit 3.2. When I use the toolkit to root it seems like it is doing everything fine, reboots, and I do not see any errors during the process. However, when I access Titanium backup, or Root Checker it cannot gain root access. I have tried all the options in the toolkit and nothing is working. Can anyone give me some pointers? Thanks!
Click to expand...
Click to collapse
Yes - Don't use a toolkit!
Since you already have a custom recovery, put the attached file on your sdcard and install it using TWRP. Then you should be good to go.
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.
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.
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
ghane0 said:
Hi,
I have the non-Taiwan Butterfly S. I unlocked it via HTC Dev, and installed Clockwork Recovery.
This week, the 4.2 update was released for Singapore. It seems to have been in two parts, one which was a minor upgrade (235MB), and after that was applied, I got the option of the larger, 4.3, 700MB, OTA.
Applying the OTA seems to have left me, at boot time, with a blank screen (there is some backlight visible, after the HTC splash). I read tonight that OTA should not be used with custom recoveries, so I have (using fastboot) been able to flash the stock recovery.
I can now go into Fastboot, HBoot, and even Recovery. But I think I may no longer have an actual "system".
How can I flash either a custom ROM, or investigate the situation?
And also, after I see the Recovery screen (the battery icon), what can I do there?
Thanks,
Click to expand...
Click to collapse
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Also, did the CWM recovery actually succeed to install the smaller OTA? I find that somewhat weird, but then again, I haven't tried to install OTAs using CWM, only TWRP and that did fail early.
If it was a 901S, I'd suggest installing the stock ROM from scratch, but since your phone is 901E (as far as I understand) and my stock ZIPs are for 901S, that's not guaranteed to work. Still, you might try to do that, but make sure to make a backup of the current state first, just in case it only gets worse. If it does work, it's probably going to be the easiest way out.
Another option would be to get someone else with the 901E to post a backup of their /system, I could turn that into a ZIP, which would solve your problem.
Click to expand...
Click to collapse
It is a 901s he said non Taiwan
Sent from my HTC Butterfly s using XDA Premium 4 mobile app
seyidaga said:
What I would do is get TWRP Recovery (Just a matter of personal preference you can get clockwormod too) do a full wipe, clear the cache, dalvik cache and install a custom ROM hope I helped somehow
Click to expand...
Click to collapse
I have downloaded the Maximus ROM. I am open to doing this, but I cannot figure out how to use the stock recovery (there seem to be no controls).
koniiiik said:
Do you still have the OTA zipfile on your device? It should be possible to force the stock recovery to install it, I just don't know how exactly. If you manage to achieve that, it should fix any corrupted files or inconsistent state, unless something went completely wrong.
Click to expand...
Click to collapse
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
koniiiik said:
If it was a 901S, I'd suggest installing the stock ROM from scratch
Click to expand...
Click to collapse
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
daorderdillon said:
It is a 901s he said non Taiwan
Click to expand...
Click to collapse
Oh, okay, I think I'm getting lost in which area has which version of the phone. Never mind then and thanks for the correction.
ghane0 said:
I think so, too, but at this stage, I am willing to go clean-slate and restart with a stock, factory, look.
I have downloaded the stock zip from your website. How do i flash that in stock recovery?
I have access to fastboot from my laptop, I can see the device.
Thanks,
Click to expand...
Click to collapse
Well, to install custom ROMs, you'll have to use either TWRP or CWM, I don't know about a way to do that using stock recovery.
Ok, I did this:
Installed CWM Recovery
Flashed the Stock zip from koniiiik's archive
Rebooted successfully. Lots and lots of force closes, Everything from android.core to ...
Used Rom Manager to restore a backup made a month ago
Rebooted. All OK now
Flashed Stock Recovery (again, thanks koniiiik)
Booted. Checked OTA. Got a small update (1.x)
Applied. Rebooted, Checked OTA again
Got the 4.3 package. Applied.
All is well
Between Step #3 and #4, I got my entire backlog of SMS delivered, which I lost in the next step. But that is a small price to pay.
Thanks to all of you helped,
ghane0 said:
Used Rom Manager to restore a backup made a month ago
Click to expand...
Click to collapse
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Backup of /system, nearly stock
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
koniiiik said:
Would you mind uploading somewhere the /system part of that backup? I'd be interested in comparing it to the builds I have at hand.
Click to expand...
Click to collapse
I have three files in the directory:
system.ext4.tar (0B)
system.ext4.tar.a (954MB)
system.ext4.tar.b (500MB)
Is the split to avoid files greater than 1GB?
Will upload starting a few hours. Dropbox will do?
ghane0 said:
I say nearly stock, because it was taken after HTC Unlock, Clockwork Recovery was installed, and root flashed
Click to expand...
Click to collapse
Don't worry about that, of these three, only root affects /system and it should be not too difficult to revert.
ghane0 said:
Is the split to avoid files greater than 1GB?
Click to expand...
Click to collapse
Most likely – FAT filesystems, depending on inode size and other factors, only support file sizes up to a certain limit. Sometimes it's 2 GB, sometimes 4 GB, sometimes probably as little as 1 GB.
ghane0 said:
Will upload starting a few hours. Dropbox will do?
Click to expand...
Click to collapse
That would be most helpful. Thanks.
Dropbox is back up, I have sent you a link.
Thanks
CPL1 Stock Plus Rom
I would just like to share an enhanced version of stock note 4 with the only "foreign" app being the grace InCallUI mainly because I have yet to locate a guide on how to make all the buttons layout correctly and there is also very minor cosmetic changes (removed words from lock screen and extended the drop-down panel to go all the way across the screen). All features and modifications were done by me using guides from @Kamy, @ikrom, @jovy23, @asc1977, @EMSpilot, @tdunham, @daxgirl, @tkari4, @Hani K., @Misterxtc and the InCallUI ported by @Albe95. Last but certainly not least, all this was made possible with @ASSAYYED's great rom kitchen and @Ticklefish's Tickle my Android.
FEATURES
Stock kernel
Rooted
Busybox
Zip-Aligned
Deodexed
Toolbox Enabled
Flashlight in notification panel
5-way Reboot
Native Tethering
Loud Volume Warning Disabled
Brought back "once and always" buttons
Call Recording Enabled
6 in the Hotseat Launcher
TW Swipe Left Shortcut
Viper4Android - credits to @viper520
Vol up to turn on flashlight
Signatures Disabled
Write to Ext. Sd with Tibu
4 way Multi window
All apps Multi Window
CPL1 Safe Firmware Upgrade
Partial Firmware courtesy of @Misterxtc
Link to Full Firmware
ROM LINK
HERE
Flash this as well for viper- Viper SUpolicy
1.
Thank you Kevin!
Does Odin "CPL1 Safe Firmware Upgrade" include the modem?
1Xfan said:
Thank you Kevin!
Does Odin "CPL1 Safe Firmware Upgrade" include the modem?
Click to expand...
Click to collapse
Yes, the firmware includes everything except recovery and aboot. Also a few things I forgot to mention, the switch to turn on volume up for flashlight is in the display settings and to set the apps for toolbox you just long press on the toolbox icon (when activated) and then drag it up to the edit section at the top of the screen. Sorry guys I'm terrible at writing the info and summary for these roms but hopefully I can get it figured out one day.
kevintm78 said:
Yes, the firmware includes everything except recovery and aboot. Also a few things I forgot to mention, the switch to turn on volume up for flashlight is in the display settings and to set the apps for toolbox you just long press on the toolbox icon (when activated) and then drag it up to the edit section at the top of the screen. Sorry guys I'm terrible at writing the info and summary for these roms but hopefully I can get it figured out one day.
Click to expand...
Click to collapse
I understand. Please clarify for me...
I'm on pj2 unlocked/rooted. I want to stay unlocked/rooted. Do I flash the "partial".zip, or Odin the "full" ? :fingers-crossed:
When I read through hsbdr's post's, I must have 5 or six tabs open
I prefer instructions simple, and retail and Dev posts/instructions separate from each other. As well as return to "unrooted" or "keep root" posts. Many have accidentally locked their BL as a result. There is no reason to include a "return to stock-locked" link in with a custom rooted ROM post/links. Uhg
Thank you for keeping it simple for us, and all your work!
1Xfan said:
I understand. Thanks for clarifying :fingers-crossed:
When I read through hsbdr's post's, I must have 5 or six tabs open
I prefer instructions simple, and retail and Dev instructions separate!
Click to expand...
Click to collapse
Yeah it does get a little confusing. That's the main reason I just posted my own link just to make sure I'm not linking to the wrong thing. Fun fact while testing all this out, I was able to flash pj2 roms while I was on the cpl1 firmware and everything worked. I just tested one rom but it seems like once you upgrade your firmware you may not have to downgrade again if you want to go back to another rom.
kevintm78 said:
Yeah it does get a little confusing. That's the main reason I just posted my own link just to make sure I'm not linking to the wrong thing. Fun fact while testing all this out, I was able to flash pj2 roms while I was on the cpl1 firmware and everything worked. I just tested one rom but it seems like once you upgrade your firmware you may not have to downgrade again if you want to go back to another rom.
Click to expand...
Click to collapse
oooh really! So probably there is nothing new in the upgrade only that it's un-downgradable:silly:
1Xfan said:
oooh really! So probably there is nothing new in the upgrade only that it's un-downgradable:silly:
Click to expand...
Click to collapse
The first couple times I tested a firmware that I made, I was terrified of locking my bl. I flashed the one I posted and then tested for downgrade and all is good, but it doesn't seem to be necessary to downgrade again. As far as differences between them the only thing I noticed was more security stuff and some different bloatware.
Forgive me...
So the "full firmware link" (download file name: "cpl1_tar_32bit_ext4") doesn't include the recovery and aboot files(?)
1Xfan said:
Forgive me...
So the "full firmware"> link doesn't include the recovery and aboot files(?)
Click to expand...
Click to collapse
That's correct. If you flash it and let it boot you'll have your custom recovery, unlocked bootloader, no root, no busybox, cpl1 modem/kernel, and odexed system. That way if someone wants pure stock they can just flash the supersu file and your set.
She's running great for me! I installed xposed and oscar kernel and it's stable as a rock! Any chance of the additional grace apps - email, contacts, etc? Great work man!
CrazyCram said:
She's running great for me! I installed xposed and oscar kernel and it's stable as a rock! Any chance of the additional grace apps - email, contacts, etc? Great work man!
Click to expand...
Click to collapse
I just tried the email zip at this post and it worked. When I get off work I'll test those others. They all should work but if you don't want to be the guinnie pig I can do it.
So oscar works? I thought it might need an update but that's good to know.
Yes, Oscar 13 works great. I'll give the grace apps a try - thanks again!
kevintm78 said:
I just tried the email zip at this post and it worked. When I get off work I'll test those others. They all should work but if you don't want to be the guinnie pig I can do it.
So oscar works? I thought it might need an update but that's good to know.
Click to expand...
Click to collapse
For some reason after flashing grace email, I see high battery usage for email 19-30%. Tried clearing data but still see the drain. Am I missing something?
sam298 said:
For some reason after flashing grace email, I see high battery usage for email 19-30%. Tried clearing data but still see the drain. Am I missing something?
Click to expand...
Click to collapse
Honestly, I only use that app when testing it and I haven't noticed any battery drain, but I can't say I've ever checked either. I wonder if it just needs to settle in. Maybe someone that uses it more can chime in to see if it's an issue for everyone. If you want to, see if after a while it goes back to normal range and if it doesn't try to get a log and we can see what we can come up with.
Hello @kevintm78. Need a little help. I just odin'd the full firmware and now my phone won't boot. I get unfortunately System UI has stopped. I was on CPJ1 before I did this. Should I just try to restore a backup? Thanks
dhplap said:
Hello @kevintm78. Need a little help. I just odin'd the full firmware and now my phone won't boot. I get unfortunately System UI has stopped. I was on CPJ1 before I did this. Should I just try to restore a backup? Thanks
Click to expand...
Click to collapse
If Odin completed it should have at least updated your firmware. If that's the case you could just go ahead and flash the rom. All the files from the full firmware get overwritten anyway. Just make sure you do a complete wipe (everything but your sd/Ext sd) and you should be good to go.
kevintm78 said:
If Odin completed it should have at least updated your firmware. If that's the case you could just go ahead and flash the rom. All the files from the full firmware get overwritten anyway. Just make sure you do a complete wipe (everything but your sd/Ext sd) and you should be good to go.
Click to expand...
Click to collapse
Thank you. Yes I just restored a backup just fine and it's also showing my baseband is now CPL1. Now I'm going to flash your rom so I can have stock whenever I want it. Thank you for your time and help. And for the upgrade.
@kevintm78...thank you for this. I had lost 4g somewhere in all my flashing. I tried reflashing partial firmware and even restoring backups wouldnt give me 4g again.I was getting ready to go through the entire lock, unlock, root process again when I found this thread. I downloaded the full firmware in the op, flashed with flashfire, rebooted into recovery, wiped dalvik, data, cache, and rebooted system. I now have 4g back. I made a nandroid of stock, and then clean flashed LOS and still have 4g. So thankful to you!!
gcounts said:
@kevintm78...thank you for this. I had lost 4g somewhere in all my flashing. I tried reflashing partial firmware and even restoring backups wouldnt give me 4g again.I was getting ready to go through the entire lock, unlock, root process again when I found this thread. I downloaded the full firmware in the op, flashed with flashfire, rebooted into recovery, wiped dalvik, data, cache, and rebooted system. I now have 4g back. I made a nandroid of stock, and then clean flashed LOS and still have 4g. So thankful to you!!
Click to expand...
Click to collapse
Yeah man, I'm a bit of a flashaholic too and was having the same issues a while back when experimenting with data fixes and thought that I fried my sim card. Like you I tried the partial first but the only thing that got my 4g back was flashing a full stock firmware. :good: