Related
I posted an old thread about this but now I have spent a lot of time trying to investigate and I am at a complete loss of ideas now.
The first thing that has to be stated is that my N7100, bought in Sweden, is rock solid under the ALJ3 based BatteryPlus 0.2 ROM. It works absolutely excellent, not a single problem. Just stable and reliable operation.
The problem:
Now to the very strange problem.
The 4.1.2 ROMs causes the device to reboot randomly. I have tried the following options:
1. Stock ROM XXDLL7 flashed through Odin 3.0.4 in Windows 7.
It reboots very often, even without a single app or mod installed. Even before rooting, it reboots. When it reboots, it can perform the whole process and return to a working state.
2. Omega 9.1 flashed through CWM 6.0.1.5.
It reboots less than with stock DLL7 but still very often. The longest uptime I managed to get was approximately 10 hours and that was with the memory card removed as an experiment. During many of those reboots, it fails to boot up completely, it just hangs at the Omega animation. A reboot by pressing the power button works.
3. JellyBam 3.3.0 flashed through CWM 6.0.1.5.
This ROM worked great for a couple of hours but then started to reboot. I.e. it worked for approximately 4-5 hours without any problems and then the rebooting started and reached a high frequency.
4. Kingdroid 2.1 flashed through CWM 6.0.1.5.
This ROM carried my farthest with approximately 8 hours between the reboots. It worked reliable for that amount of time between the reboots while the other ROMs showed a tendency to reboot frequently when that "cycle" started.
5. WanAm Lite DLL5 based flashed through CWM 6.0.1.5.
It rebooted in a similar fashion to the Omega ROM.
The interesting thing with all this is that stability and reliable operation returns immediately when I flash back to BatteryPlus 0.2. I can experience random reboots with a high frequency with a 4.1.2 ROM and then immediately flash BatteryPlus 0.2 and get stability. One example is a ROM that reboots within 5 minutes or even during initial setup, if I then flash the BP 0.2 - everything works perfect again without any reboot.
The steps I have taken in order to troubleshoot are:
1. Full wipe - every flash has been made with full wipe including format /system and /preload.
2. I removed the memory card as one step, unfortunately the random rebooting continued but with a longer period.
3. I reformatted the card both from CWM and from the Settings but the rebooting continued.
4. I tried an older 8 GB SanDisk Ultra card from my Vivaz - and it still rebooted.
5. I removed the SIM card (Straight Talk mini SIM cut to micro SIM) - and the rebooting persisted.
6. I downloaded the emergency restore ROM and made a .PIT repartitioning through Odin - and the rebooting persists.
7. I flashed the latest XXDLL7 through Odin - and it reboots.
The interesting detail is that the flashes itself has been successful and I have been unable to pinpoint anything, for example radio or bootloader. I am now running BatteryPlus 0.2 with the latest DLL7 bootloader and radio - without any single problem.
The fact that the reboot behavior differs between different ROMs (some experiences random reboots within 10 minutes, others works for hours) together with the fact that BatteryPlus 0.2 works perfect clearly points AWAY from hardware problems. The memory card and everything runs perfectly well under that older ROM.
The only thing I have been thinking about is if there is a recovery problem. On my N7000 I had to revert to HyperDroid RedPill Recovery (Abyss Kernel 3.9 RedPill) since I noticed that CWM didn't properly wiped the cache partition (I got "Android is updating xx of yy" even after a full wipe) and instability. With the RedPill, everything worked perfectly well.
I have also tried to do some logcat but has been unable to pinpoint any single process causing a reboot. I suspected the Pure Messenger Widget for example (which works perfect in 4.1.1) but when the rebooting started without a single application installed etc, that theory failed.
The recovery I have used is the CWM 6.0.1.5 flashed through Odin as a part of the root package.
I tried to flash DLJ2 ROMs through TWRP as an experiment one month before but still with rebooting.
I am at a complete loss at this stage, the only thing I can think about is if there are some kind of "mismatch" between 4.1.2 based ROMs and CWM 6.0.1.5 - or if there is something going on with the CSC that is Nordic (I have never changed it).
The Note was delivered with ALJ1 originally if I remember that correctly.
This problem annoys me since it would be nice to upgrade to 4.1.2 ROMs but all random reboots prevents this.
Is there anyone that has experienced the same problem?
To me is it a bit strange that the device works perfectly under the 4.1.1 based BP 0.2 but acts up with random reboots under anything 4.1.2. Since I got farthest with JellyBam 3.3.0 and Kingdroid 2.1, it is obvious that the reboots are triggered differently. With some ROMs, I have noticed reboots when the USB cable is plugged in. Not immediately but after a while (5 minutes or so). In BP 0.2, this don't happen.
I would be grateful for any kind of help here.
I am not interested in sending the device for service since I clearly suspect a software problem - the extremely reliable operation in BP 0.2 indicates this. If it would be the hardware, it would act up in a very similar manner - and certainly in BP 0.2 too.
Well that's intriguing. Sorry if I missed it in your extensive post, but have you tried going all stock and updating to 4.1.2 via kies or stock update to eliminate or confirm whether it's something in 4.1.2 itself? I haven't checked in a while (from Norway myself), but I believe official 4.1.2 is available for Scandinavia now.
Sent from my GT-N7100 using Tapatalk 2
I have this strange reboots on my N7105 also. I'm on 4.1.2 with Deadman12' DLL1 Rom. I was not able to reproduce the reboots. Did not have them with T-Mobile branded 4.1.1 Rom.
Gesendet von meinem GT-N7105 mit Tapatalk 2
adytum said:
Well that's intriguing. Sorry if I missed it in your extensive post, but have you tried going all stock and updating to 4.1.2 via kies or stock update to eliminate or confirm whether it's something in 4.1.2 itself? I haven't checked in a while (from Norway myself), but I believe official 4.1.2 is available for Scandinavia now.
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Yes, I have also tried to flash the emergency DLJ2 ROM including PIT repartitioning without success. I have also tried the LL7 stock ROM a couple of times, in those cases with full wipe made in CWM before rebooting into download mode and flash through Odin (PC).
Since I hadn't any success with any 4.1.2 ROM even if the reboot frequency varies, it seems to be some kind of compatibility problem - the question is what.
When I flashed the LL7 stock ROM, it updated the bootloader and radio without any problems so now I am on BP 0.2 with the LL7 radio and latest bootloader. Without any problems.
Interestingly, the ROMs that has worked best (with 4.1.2) has been Kingdroid 2.1 and JellyBam 3.3.0. Since the reboot frequency varies, it seems to be differenses in the ROMs that causes it.
It is also worth to mention that I have noticed different reboot frequency on the same ROM in connection with reflashing.
That somehow points towards a CWM problem. I.e. that something goes on during the flash and that "something" somehow causes problems with the 4.1.2 ROMs.
niehof said:
I have this strange reboots on my N7105 also. I'm on 4.1.2 with Deadman12' DLL1 Rom. I was not able to reproduce the reboots. Did not have them with T-Mobile branded 4.1.1 Rom.
Gesendet von meinem GT-N7105 mit Tapatalk 2
Click to expand...
Click to collapse
This certainly points towards some kind of compatibility issue with 4.1.2 ROMs.
There is one theoretical possibility and that is if there are different batches of N7100/N7105 and that there are some kind of internal difference that creates the problems.
Otherwise, I suspect the CWM.
As I wrote before, on the N7000, I experienced problems with CWM flashing and solved them by switching to the RedPill Recovery in Abyss 3.9 kernel. It is also worth to mention that CWM worked well later, with ICS and JB. That problem persisted during the GB times with older kernels.
Have you tried twrp? Though I can't see how the procedure of flashing zips or having a certain recovery latent on your phone could affect rom behaviour, it's worth a shot.
If it were me, I'd approach it pseudo-scientifically, and start going completely stock and wiped unrooted, updating to 4.1.2 through the phone ota, simply leaving it in standby for a long time without doing or installing anything and see what happened. There might be the off chance that your NAND could be corrupted, so as to eliminating a few options, doing tests in a completely stock, non-Odin'ed environment could get you on your way.
Sent from my GT-N7100 using Tapatalk 2
Thanks for the answer.
I will try the suggestions but I think that I will wait a little while, perhaps for a newer update than the LL7 since I have spent many days troubleshooting already and since I also formatted my memory card and therefore removed my old Titanium backups (in order to start fresh), it has taken me a while to configure everything again.
I have considered NAND corruption and that is why I tried a PIT repartition with the emergency rescue firmware posted here. I have also done full wipes including format /system.
It is worth to mention that the strange thing here is that stability returns immediately when I flash BatteryPlus 0.2/4.1.1.
The other important thing here is that the reboot behavior depends on the ROM, complete stock DLL7 reboots insanely, Kingdroid and JellyBam works for a far longer time before rebooting. What I think is strange, regarding the theory of NAND corruption, is the fact that there is no problems with the flashing itself and on the same time, the behavior differs between different ROMs. Since the difference is hours between the first reboot, it is really hard to pinpoint the exact cause.
The only idea I can think about then is to flash stock ALJ3 through Odin and then try to run the OTA from there.
It seems like you might need to do what others are doing to try and see what's going on. You may need to start pulling the last_kmsg log. It's /proc/last_kmsg Unfortunately I don't know how to read them well, but others do. This at least could help to give a clue as to what's going on. I was going to ask if you did the format /system, but I saw you mentioned you've done that before. I see that you've also mentioned about trying a full reset with noting installed, but have you tried without installing accounts or at least say restoring accounts like google, samsung, and dropbox, but turning off the sync/backup/restore for them?
Also one thing to try and this bugs me about odin. Is a lot of these full odin firmwares still don't seem to wipe everything. So after flashing through odin you may want to boot to regular recovery and do a factory reset. I've had issues where after flashing new firmwares with odin my phone wouldn't boot. It was leaving /data or not completely wiping /data and I would run into staying at boot logo or if I got the phone on continuous force closes. I was going into cwm or whatever recovery and doing what you said. Format /system, /data, /cache. Then I'd battery pull wait about 10-15 seconds, then put the battery back in and go to download mode. Then I would flash the odin file which would then set up everything 100% factory. Of course I'd have to re-use the CF-root package, but that's not a big deal. I've encountered the odin issue not doing a proper wipe with my N7000, N7100, i9300, i777, i747. Also for what it's worth custom roms don't matter that much to me so I've completely stuck with stock recovery and just use mobile odin to flash new firmwares or kernels. I also use the latest Perseus kernel.
Hm, and i have randomly reboots after update to 4.1.2
Nothing is help me, wipe device,factory reset, wipe memory and all thing. Only when remove chrome from system app reboots stoped. From 2 days i dont have that app installed on phone and problem is gone. I cant explain how it affect to system, but problem is gone.
Try
I have taken the following steps during the flashing:
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik Cache
4. Format /system
5. Format /preload
Some of the 4.1.2 ROMs reboots already during initial setup, i.e. they fail to complete the setup guide. The reboot can happen after putting the Google account in or under Dropbox setup for example. Otherwise, it reboots without doing anything in some cases.
The strange thing is that immediately when I flash the BP 0.2 from the same recovery, stability returns. So I can have everything else the same, just flashing BP 0.2 and everything works great.
Regarding Odin. The procedure I have followed when I flashed stock DLL7 that way has been:
1. Boot into CWM, wipe data/factory reset, wipe Dalvik, format /system and format /preload (just in order to have everything wiped since the stock ROM doesn't do it).
2. After wiping in CWM, reboot into stock recovery/download mode and flash the DLL7 by Odin.
It is also worth to mention that I have checked the MD5 checksum on all ROMs in order to make sure that they are OK.
Still, despite wiping in CWM before flashing DLL7, the rebooting persisted.
Since it seems like this thread provides great input, I am planning to spend tomorrow with a new attempt to get 4.1.2 up and running.
I am going to remove Chrome and start from the stock 4.1.2 but will try to move to a custom ROM quickly since I want deodex etc. One option is obviously to flash a deodexed stock ROM or something.
mitky82 said:
Hm, and i have randomly reboots after update to 4.1.2
Nothing is help me, wipe device,factory reset, wipe memory and all thing. Only when remove chrome from system app reboots stoped. From 2 days i dont have that app installed on phone and problem is gone. I cant explain how it affect to system, but problem is gone.
Try
Click to expand...
Click to collapse
Sounds great, I will try that tomorrow then.
Flash a new 4.1.2 ROM, just skip the initial setup and then remove Chrome as soon as possible and hope that it will solve the problem.
Edit: BatteryPlus 0.2 doesn't have Chrome at all. It would be great if that is the cause of the reboots and perhaps already tonight I will do a very simple test by flashing one of the custom ROMs through CWM and then put Root Explorer in ASAP and then remove Chrome. Then I can watch the device over the night.
The theory is certainly interesting.
Strange, but helps for me. Hope and for you
Dont flash rom again if you are now on 4.1.2
Just wipe dalvik and cache, fix permisions and start phone.
I dont reflash rom, just eliminate one by one system app who i dont use and test for some time.
Mostly reboots i have when i surf in internet with stock browser. About a 10-15min an BAM-reboot. Now i use with hours stock browser and dont have any reboots after remove that app. Im not shure that from rom or that who i update from market is buggy, but never use again chrome
Dont remove CromeBookmarksSyncAdapter.apk that apk is for sync bookmarks with stock browser and google.
I am on 4.1.1, BatteryPlus 0.2.
My reboots hasn't been in the browser though, most of them has been in completely random manner. Either during initial setup or randomly in different apps or when the device has been completely untouched, for example during the night.
I have in other app, but mostly in browser. I dont know, try and test. Hope problem is gone
With 4.1.1 i have too, but for time to time, for 2-3 days is one restart. After 4.1.2 i insane from reboots.
Sorry for bad Eng, but i think you understand me
I saw a possible explanation in another thread about issues on XXDLL7. It seems to point toward some kind of problem with CWM/custom recoveries in general and the XXDLL7 with the updated bootloader.
That could be a possible explanation for the problems.
I can live without a custom recovery for a while but I don't like it very much since I want to be able to flash mods etc.
The theory seems to be that Samsung changed something in the partition scheme in the XXDLL7 which results in problems when a custom recovery is used.
Latest update:
I have just made a full wipe including format /system in CWM and reflashed XXDLL7 through PC Odin followed by an extra factory reset (wipe data) in stock recovery.
I tried an emergency restore with Kies but it proposed the old ALJ3 since it seems like the DLL7 isn't released for Sweden yet (and I bought the device there).
So now I will see how it behaves with this stock ROM again.
I also made a Triangle Away since my counter was standing at 8.
At the moment, the device should be 100% stock, stock ROM, recovery, bootloader and everything.
Edit: As a further precaution, I disabled Chrome from Settings.
I also skipped through the Setup Guide.
Edit 2: At the moment, it seems to be more stable than before. I experienced reboots almost immediately on this ROM. Could it be that simple that an extra wipe is necessary after flash before first boot?
New update:
I encountered the reboots again under stock XXDLL7. I have therefore flashed Android Revolution HD and will monitor it and see what will happen. I flashed it with full wipe, format /system and everything.
The only anomaly I noticed at the moment was "the Clock has stopped" so I froze that app. I ran an extra wipe after flashing and topped up with fix permissions (despite this, the Clock app acted up).
I flashed with CWM 6.0.1.5 and rerooted with the standard package containing it.
Save you important data and wipe device from stock recovery. They remove everything from you INTERNAL SD CARD.
And instal stock rom with odin. After that again wipe from stock recovery. Then root and use phone like you want.Do you test that?
Yes, I usually wipe the internal SD card when I flash.
Now, I am going to try to extract the logs. I had another crash with ARHD 8.0 now, it had been up for 2 hours 55 minutes (before that 2 reboots with approximately 20 minutes in between) and now when I activated WiFi, Settings just FCed and then it rebooted.
When I flashed the stock ROM, I wiped everything and after that, wiped again from stock recovery. Still rebooting....
Now with ARHD, it seems like the reboot behavior is similar to the stock ROM.
I am now going to see if I can find anything in the kernel logs.
I managed to extract the kernel log file. The last part of it looks like this:
Samsung S-Boot 4.0-679347 for GT-N7100 (Dec 26 2012 - 10:25:20)
EXYNOS4412(EVT 2.0) / 2047MB / 15028MB / Rev 11 / N7100XXDLL7
initialize_ddi_data: usable! (2:0xe)
PARAM ENV VERSION: v1.0..
<start_checksum:331>CHECKSUM_HEADER_SECTOR :4096
<start_checksum:333>offset:50, size:6296
<start_checksum:336>CHECKSUM_HEADER_INFO : NeedChecksum:0 PartNo:20
Not Need Movinand Checksum
Movinand Checksum Confirmation Pass
init_fuelgauge: fuelgauge power ok
init_fuelgauge: not POR status
init_fuelgauge: manual reset case, skip soc-cal.
get_table_soc: vcell(4025) is caculated to t-soc(77.410)
init_fuelgauge: start: vcell(4025), vfocv(4076), soc(78), table soc(77)
init_fuelgauge: finish: vcell(4025), vfocv(4076), soc(78), table soc(77)
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL1:0x00
init_microusb_ic: MUIC: CONTROL2:0x3b
init_microusb_ic: MUIC: CONTROL2:0x3b
PMIC_ID = 0x02
PMIC_IRQSRC = 0x00
PMIC_STATUS1 = 0x13
PMIC_STATUS2 = 0x00
PMIC_PWRON = 0x09
PMIC_IRQ1 = 0xc2
PMIC_IRQ2 = 0x00
s5p_check_keypad: 0x100000
s5p_check_reboot_mode: INFORM3 = 0 ... skip
s5p_check_upload: MAGIC(0x66262564), RST_STAT(0x10000)
s5p_check_upload: debug level is 4f4c!
s5p_check_upload: level low or unknown: skip 0
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
s5p_check_download: 0
microusb_get_attached_device: STATUS1:0x3f, 2:0x00
check_pm_status: charger is not detected
check_pm_status: voltage(4025) is ok
ddi type = 1, S.LSI
cmu_div:6, div:2, src_clk:880000000, pixel_clk:62614944
41, 16, a2,
load_kernel: loading boot image from 1141838212..
- read_bl1
Verify_Binary_Signature: failed.
pit_check_signature (BOOT) invalid.
Set invalid sign flag
if_ddi_data: succeeded. (2:0xe)
ATAG_CORE: 5 54410001 0 0 0
ATAG_MEM: 4 54410002 20000000 40000000
ATAG_MEM: 4 54410002 20000000 60000000
ATAG_MEM: 4 54410002 20000000 80000000
ATAG_MEM: 4 54410002 1ff00000 a0000000
ATAG_SERIAL: 4 54410006 4df1f97c 36cf9ff5
ATAG_INITRD2: 4 54420005 42000000 85ce3
ATAG_REVISION: 3 54410007 b
ATAG_CMDLINE: 6e 54410009 'console=ram loglevel=4 sec_debug.level=0 sec_watchdog.sec_pet=5 androidboot.debug_level=0x4f4c [email protected] s3cfb.bootloaderfb=0x5ec00000 sysscope=0xee000000 lcdtype=1 consoleblank=0 lpcharge=0 lpj=3981312 vmalloc=176m oops=panic pmic_info=67 cordon=58a4048e6da218bf13a26b048ba5702c androidboot.emmc_checksum=3 androidboot.bootloader=N7100XXDLL7 androidboot.serialno=4df1f97c36cf9ff5 snd_soc_core.pmdown_time=1000'
ATAG_NONE: 0 0
Starting kernel at 0x40008000...
SWITCH_SEL(3)
This is from ARHD 8.0.
Now, it suddenly did a "light factory reset" - i.e. it rebooted and then run the initial setup again, fortunately Root Explorer remained in place so I could extract the log file.
This is the last.kmsg log.
Edit: Since I see something about the .pit, perhaps I should try to use Odin 3.07 instead of 3.04 and reflash the stock ROM with it together with NAND erase, if there is something troublesome with the partition table.
On the other hand, it is still very strange that the old BP 0.2/ALJ3 works perfectly.
I rooted and ran a couple diff custom ROMs: cm10.1.3 and infamous alpha, both with oc kernels (never set mhz past 2051). Began getting random reboots, alot while running the Alpha ROM, and a couple while running cm10.1.3 which I thought was weird because its a RC. should be stable, right? Anyway, got tired of RRs, so I decided to unroot and got stock, till I had some free time.to tinker with it. Well guess what, getting RRs EVEN IN UNROOTED STOCK. Any ideas?
I'm not exactly sure what steps you have taken to get back to Stock, where you're still having random reboots, but I'll let you know what I've done in the past to get to Stock which resolved the issues:
- Factory reset device from device. Save and/or move your Internal files/data prior as you'll be wiping Internal. I'd remove my extSdCard prior to Factory reset and after moving files to it.
- ODIN Samsung Stock Firmware
http://samsung-updates.com/details/9595/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUAMDL.html
- After the device boots, you'll probably get stuck on the Samsung splash boot screen. After a few minutes - -
- pull the battery, replace the battery but Don't power the device on
- Place device in Stock Recovery mode by pressing Power and Vol up buttons at the same time.
Release the buttons when you see the blue letters appear in the upper left hand corner of the screen.
- Scroll to Factory reset using the volume buttons.
(During the above process, you'll see the Android on its side with a Red X on him/her.)
- press the power button to lock in Factory reset
Let the Recovery scroll through its script
(during this process the Android will come to life )
- After the script is completed which takes less than a minute or so, scroll to reboot and select it with the power button.
- the device will now boot.
Important: while the device is booting, the screen will stay on the T-Mobilessplash screen for what will seem forever. Don't panic. The screen will show T-Mobile across the screen for about 15 or so minutes. Could be a little more or a little less. The device will then continue and complete the booting cycle.
Some notes:
1) during the above process, I have removed my extSdCard card as I didn't want tottake a chanceiit would be wiped. ODIN doesn't wipe extSdCard card but I don'tbneed it during theiprocess so I remove it in case Murphy decides to pay a visit.
2) during ROM flashes, I've experienced almost every issue youccan imagine. This occurred while using TWRP 2.5.0.2, but only when flashing ROMs with Aroma. For months prior, I had zero issues.
The problems I was experiencing were:
Random reboots, splash screen freezes, bootloops, installation of choices in Aroma which only partially installed, issues which didn't seem to havesan answer, and when you found the solution, that solution wouldn't work when the issue appeared again.
- constantly ODINing back to stock
- sometimes in Recovery, I couldn't get past the TWRP lockscreen, and only wiping Internal SD resolved the issue so I could do a Factory reset. I was doing this so often, that I left all files on my extSdCard so Iewouldn't lose my data when I had to wipe internal. It was faster this way as I didn't have to keep moving stuff back & forth.
After endless hours of troubleshooting and aggravation, I changed Recoveries.
I installed Philz Touch Recovery, and I have had Zero issues since installing it about 3 or so weeks ago, which have included multiple ROM flashes with Aroma.
I didn't want to switch Recoveries as I was very used to TWRP, but I just couldn't deal with the new found issues I was having so I made the switch and haven't looked back. Some people don't have issues with TWRP, but I wasn't one of them
Hopefully you can relate to some of my experiences which I have written above, which may help you to resolve some of the issues you're experiencing.
Yes. Thats the file I used and also the steps. I dont know what the deal is.
twatts723 said:
Yes. Thats the file I used and also the steps. I dont know what the deal is.
Click to expand...
Click to collapse
If you:
Wiped Internal SD
ODINd Stock Firmware
which flashed successfully
and are still having random rebooting.....
I can only suggest:
Check your device settings, if you haven't done so already to insure you're running:
Stock ROM
Stock modem/radio
And that all settings are stock.
If everything checks out, I can only suggest to:
Download the Samsung Stock Firmware file again
Check the md5 checksum
ODIN Samsung Stock Firmware again
And see how it goes.
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
twatts723 said:
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
Click to expand...
Click to collapse
Glad everything worked out for you.
Don't shy away from custom ROMs though, as you'll be missing out on some good stuff
As a note, there can be many thinks which can contribute to issues after the installation of a Custom ROM, Kernels, etc. such as:
Bad downloads, corrupted files, app conflicts, dirty flashes instead of Full wipes, etc., etc.
Another issue can be related to the Recovery you are using.
I had many, many issues regarding flashing ROMs which installed with Aroma.
Prior to ROMs w/Aroma, I had Zero issues.
I suggest using Philz Touch Recovery.
In case you don't have it installed and want to try it, I'll post a link to the download page.
Flash the proper file for your specific carrier.
Install the tar file with ODIN or
Flash the zip file with your Recovery......
Well, I come from sgs2. On that device, I could flash everything through cmw, and just use darkside super wipe and darkside cache wipe. No problem. Every rom from cm to amatuer custom blibbidy blobbidy, no problem. When I rooted my s4, I went straight to twrp because everyone said it was better. I flashed cm10.1.3 rc - rr. Infamous alpha v.7, which was supposed to be stable - rr. I went back to stock, rooted again, and kept stock tw, and only flashed ktoonz kernel, which is supposed to be one of the best for this device. Everything ran great, but guess what - rr. So I gave up. Went back totally stock. Working a lot of hours at work right now. We slow down after thanksgiving, so I'll probably start flashing again around that time. Thanks for thw help though
cheers.
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )
So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.
All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.
ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.
I got the new phone 15 days ago, thinking it'll be as amazing as Zenfone Max ZC550KL (Great Camera, everlasting battery) but it had super annoying issues, specially the battery draining too fast. Even during deep sleep (screen off for hours) the battery drained from 100% to 70% in like an hour or so, without any SIM/WiFi/Hotspot.
I had to fix this as it was impossible to go outside for a day and not have it switch off on my face when I needed it. None of the power saving settings helped.
So, I unlocked the bootloader following a youtube guide (it was a batch file on windows, not the original app which I found out about 10 mins ago), and flashed TWRP into it. Took a full system backup of all partitions and rooted it by flashing the latest SuperSU Binary. Worked like a charm. Installed CPU Tuner, deleted all triggers and set frequency to manually locked 500 MHz. When I need to play a game or do something which needs performance, I'd just go and manually pull the slider ahead to 2.3 GHz.
The avg. battery drain during deep sleep or screen off for hours, reduced from 1120 mAh to 10 mAh which is HUGE (found out with an app I cant remember). I'm happy with it as now it can last about a day and about 3 days if I'm mostly not using it, with WiFi on all the time. Its just slightly not as butter smooth with the UI as before.
Now, the camera quality is the worst I've ever seen. During dark, the PixelMaster Camera makes things crippling dark and too much purple pixelated noise and grain, pics taken from it look like from my Galaxy Tab 2 which I bought in 2012, and I tried different camera apps and everything I could, no luck. Where, the image taken from almost the same place at the same time, both phones held side by side, my old phone ZC550KL takes a million times clearer picture, brighter, perfectly visible and great looking. I also tried setting the same enhancements and stuff but nothing helped.
Some posts on googling it, suggest to update the system firmwire to improve camera quality but it requires the original recovery mode to be there, where I have TWRP.
I want to update the system as I have nothing to lose, already have 4-5 complete TWRP backups of every state (Original before rooting, rooted once, some modifications later, etc). Just if the phone gets bricked or doesn't boot anymore, that would be the problem.
I've messed around with almost everything I could on my Windows 7 and Windows 10 Desktop over past 6 years, so I have an idea about how things work.
Now, how do I update the system?
I think I could flash an update manually downloaded on my PC using adb and fastboot drivers... If so, how?
Current Software Information:
Current Android Version: Lollipop v5.0
Build Number:
LRX21V.WW-ASUS_Z00A-2.20.40.184_20160504_4658_user_044030427
Available System Update from the inbuilt app:
Last Check: 09/14/2017 12:00 PM (today)
Build Number: WW_2.20.40.198_20160930_8756_user_rel (93.31 MB)
CaptianXLAB said:
I got the new phone 15 days ago, thinking it'll be as amazing as Zenfone Max ZC550KL (Great Camera, everlasting battery) but it had super annoying issues, specially the battery draining too fast. Even during deep sleep (screen off for hours) the battery drained from 100% to 70% in like an hour or so, without any SIM/WiFi/Hotspot.
I had to fix this as it was impossible to go outside for a day and not have it switch off on my face when I needed it. None of the power saving settings helped.
So, I unlocked the bootloader following a youtube guide (it was a batch file on windows, not the original app which I found out about 10 mins ago), and flashed TWRP into it. Took a full system backup of all partitions and rooted it by flashing the latest SuperSU Binary. Worked like a charm. Installed CPU Tuner, deleted all triggers and set frequency to manually locked 500 MHz. When I need to play a game or do something which needs performance, I'd just go and manually pull the slider ahead to 2.3 GHz.
The avg. battery drain during deep sleep or screen off for hours, reduced from 1120 mAh to 10 mAh which is HUGE (found out with an app I cant remember). I'm happy with it as now it can last about a day and about 3 days if I'm mostly not using it, with WiFi on all the time. Its just slightly not as butter smooth with the UI as before.
Now, the camera quality is the worst I've ever seen. During dark, the PixelMaster Camera makes things crippling dark and too much purple pixelated noise and grain, pics taken from it look like from my Galaxy Tab 2 which I bought in 2012, and I tried different camera apps and everything I could, no luck. Where, the image taken from almost the same place at the same time, both phones held side by side, my old phone ZC550KL takes a million times clearer picture, brighter, perfectly visible and great looking. I also tried setting the same enhancements and stuff but nothing helped.
Some posts on googling it, suggest to update the system firmwire to improve camera quality but it requires the original recovery mode to be there, where I have TWRP.
I want to update the system as I have nothing to lose, already have 4-5 complete TWRP backups of every state (Original before rooting, rooted once, some modifications later, etc). Just if the phone gets bricked or doesn't boot anymore, that would be the problem.
I've messed around with almost everything I could on my Windows 7 and Windows 10 Desktop over past 6 years, so I have an idea about how things work.
Now, how do I update the system?
I think I could flash an update manually downloaded on my PC using adb and fastboot drivers... If so, how?
Current Software Information:
Current Android Version: Lollipop v5.0
Build Number:
LRX21V.WW-ASUS_Z00A-2.20.40.184_20160504_4658_user_044030427
Available System Update from the inbuilt app:
Last Check: 09/14/2017 12:00 PM (today)
Build Number: WW_2.20.40.198_20160930_8756_user_rel (93.31 MB)
Click to expand...
Click to collapse
very first of all you must update to MM latest MM it has improved battery life and there are also security related issues fixed. the very best thing to do is.. go to the following link. see the section flash firmware without AFT. (you do not need to change recovery or boot image or any thing just follow the instruction)
reboot your phone in fastboot mode and run each and every command step by stem. even if some of them fails.. not reboot, after first boot go to recovery mode and factory reset. start again and then again sideload latest MM from asus website
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Not so sure I wana upgrade to MM though. Feels like something will definitely go bad during that.
On ASUS support site, in the firmwire tab, I found a LOT of options to download. It'll take time to find the correct version.
Say I found the correct version (or ROM) and downloaded it. (about 1.2 GB), what are the steps to flash it on my phone? Can it be done using TWRP?
Worth upgrading to Marshmallow IMHO
No freezing, less ram usage, better battery usage especially with a new battery, more compatibility to newer apps, Permissions control (love it)
If you say that you are handy on PC then great, cos you may need to be
ASUS ZenFone2 (ZE551ML) software Image: V4.21.40.352 for WW SKU only*(andriod M)
Thats the current version of MM
Download and place onto SD card, unplug cord and system should recognise.
Plenty of info on the web about upgrading however you need to unroot and renable all disabled.
More then likely will brick phone but piss easy once you have done many times lolol
Check out the Unbrick threads
https://forum.xda-developers.com/zenfone2/general/guide-fix-bricked-ze550ml-ze551ml-usb-t3405840
https://forum.xda-developers.com/zenfone2/general/guide-recover-fastboot-bricked-zenfone-t3284337
And what i initially used
http://www.techyoutubers.com/2017/04/fixed-how-to-fix-zenfone-2-hard-brick.html
https://www.youtube.com/watch?v=fsAse5F5xtM
CaptianXLAB said:
Not so sure I wana upgrade to MM though. Feels like something will definitely go bad during that.
On ASUS support site, in the firmwire tab, I found a LOT of options to download. It'll take time to find the correct version.
Say I found the correct version (or ROM) and downloaded it. (about 1.2 GB), what are the steps to flash it on my phone? Can it be done using TWRP?
Click to expand...
Click to collapse
as i suggested it is foolproof method to update to MM. i am 100 percent sure you will not brick if you follow what i suggested. don't see multiple threads. multiple instructions. do as i told earlier
Sorry to be away for such a long time... I'm back. xD
As soon as my exams are over, to do this upgrade.
I'll do it like this:
1. Copy the update zip file to MicroSD. [Filename: UL-Z00A-WW-4.21.40.352-user.zip]
2. Full system image backup using TWRP - All Partitions to MicroSD, then transfer to my PC (Just because I want to xD )
3. Clean format all partitions on my phone (I've had enough "errors after updating" issues on PC, so)
4. Select the update zip file from TWRP, flash it.
5. HOPEFULLY there won't be any errors (If there will, I'll simply restore everything from the backup I just made on step 2. Nothing lost!)
6. Reboot and pray for it to work xD
[if it still works and boots just fine]
7. Remove SIMs, MicroSD, etc., Factory Reset (again. Just cos I want to xD )
[Hope for it to still work on rebooting]
8. Check if everything's working (all apps, calling, playstore, etc. just to make sure)
9. Install everything, sync up, make it my phone again
10. Reboot, boot into Recovery (to see if TWRP is still there?)
11. if TWRP isn't there, Boot into Fastboot, flash a stable TWRP recovery to replace the default one using my PC.
12. Create a MM (before-root) backup of all partitions. (Actually, I'll create THREE backups, can't risk any failures xD )
13. Download the latest SuperSU, Flash it. Download a supported Viper4AndroidFX v5 apk or flashable zip, install/flash that too.
14. Set up root apps (CPU Tuner, Titanium Backup, BusyBox, etc) and first thing to see if Viper4Android works.
[Cos if my phone aint havin' v4a, everything above is useless for me because I can't live without that perfected sound and I'll just revert! xD ]
That seems to be about it. Will all this work? Any suggestions?
Some questions I still have -
There's also a recovery.img file in that zip. Will it overwrite TWRP?
Will the bootloader be locked again after this update? (unlocking it was a long search for android LP)
And the main reason not-that-tech-related I'm wanting an upgrade now (Substratum!):
Spoiler
Will Substratum Theme Engine work with MM? (I just want EVERYTHING BLACK - to rest my eyes. I'll buy themes too)
How well can substratum skin my phone? (I want literally everything dark themed, as much as possible)
Will backgrounds of apps like messenger/facebook be dark themed?