Related
Hey guys,
I've had CM 7.2 Stable for a couple weeks on my phone. It was
working great until a few days ago when I tried to tweak the CPU
settings a little. Right now i'm using
Governor Smartass V2- Min 352 MHz, Max- 691 MHz
What CPU settings are you all using with CM 7.2???
Since I tweaked it from the default cpu settings I've been
experiencing screen freezes. Sometimes the trackball will work
sometimes it won't. It primarly happens when my phone has been
sitting idle for some time. I'll try to get it out of the lock screen
but it won't respond to my touch. I've tried rebooting, battery pull,
I've also tried lowering and raising the min and max settings. It'll
work periodically and then it will just freeze. Funny thing is I
don't know what the "default cpu settings" were set at. I've been
looking around a lot but couldn't find much.
Thanks!
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
kjjjjshab said:
I have never seen an issue here with 691. My experience though is that smartass 1 or 2 do not work as well as ondemand.
691/352 ondemand
Sent from my HERO200 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot for the input. I'll try to go back to On Demand. If that doesn't work then maybe I'll just re-flash the ROM.
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
laie1472 said:
Tell me do you have any other overclocking apps installed?? Or any kind of app that effects the lock screen??
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
Hi-
I looked at my list of apps to be sure and no extra overclocking app installed. I'm using the default "CyanogenMod Settings" to get to "Performance" and setting the cpu from there. I have not installed any extra lock screen apps or 'lock screen security app' other than what comes preinstalled on CM 7.2. I don't believe I have any app that effects the lock screen. All of the apps I have are fairly simple, mostly developed by google inc. and nothing that tweaks or alters the device (I have Maps, a Speedometer, Navigation.) I try to keep them all closed though with the Task Killer app I downloaded.
I have switched back to OnDemand. So far nothing has changed and it's still stalling up (even though it's only been about an hour.)
Thanks a lot.
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Update
laie1472 said:
Uninstall the task killer. Reboot to recovery. Wipe cache, and davlik cache. See if that helps at all.
#Root-Hack_Mod*Always\=LTE
Click to expand...
Click to collapse
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
That worked for ONE day
brentmxt said:
So I tried raising the minimum CPU And my phone would not respond at all in the lock screen the next morning. So I had to do a manual recovery and wiped the davlik cache and cache like you suggested (thank you Laie1472). Rebooted. Was able to navigate through my phone for about one minute and it froze again.
So I did a full wipe in recovery ( thanks to senior member SleepyEDB)
I re flashed cm 7.2 and so far it's running 'better' it still freezes every now and then in the lock screen and other places when I wake it up, but not as often. We'll see how it works tomorrow. Ive been searching through a couple other forums and one guy with a similar problem took his phone apart and found it was a hardware problem. Maybe I should send it back (BestBuy refurbished).
SleepyEDB said-
Doing a full wipe in recovery
Do the following steps in Recovery to perform a full wipe:
Wipe Data/Factory Reset
Wipe Cache Partition
Mounts and Storage -> Format /system
Mounts and Storage -> Format /boot
Advanced -> Wipe Dalvik Cache
To do a 'dirty wipe', only wipe the Cache Partition and Dalvik Cache, steps 2 and 5.
Click to expand...
Click to collapse
So that was short lived. Once I did the Full wipe around noon it worked almost perfectly until for about 12 hours. I think it froze right before I went to bed. I woke up and it was completely frozen at lock screen again. I did another full wipe and reinstalled cm 7.2 and it froze again. So I did a second full wipe and it is now working. I really hope it will accept my nandroid backup if it freezes again because it's A LOT quicker. Than doing a full wipe.
Hope this helps anybody who goes through the same thing.
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.
BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).
kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app
You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.
This is to at least avoid the need to boot into CWM recovery every time
Reason:
I immediately flashed my brand new Nook HD+ with the emmc CM 10.1 three weeks ago
The vanilla CM booted in 90 seconds but that was 350 app installs ago and many uninstalls and app updates as well
If I power on the HD+ seem to always get stuck in the boot loop of the CM Logo; I wait up to 10 minutes
It seems booting into CWM recovery via N button on Power on and choosing wipe dalvik-cache allows a rebuild of dalvik-cache for the 350 apps followed by normal boot into CM 10.2
Besides the long delay is there any harm in wiping Dalvik-Cache every time I reboot or poweron?
I believe only this method and CM safe mode are the only way I know to avoid bootloops
Do I need to modify Dalvik-Cache settings/properties to fix bootloops? If not can I automate/ default into the Dalvik-Cache wipe for each poweron / reboot
BTW reason I rebooted a few times is I am still trying to struggling getting USB OTG / USB host mode working
Should I turn off USB debugging if I can not use USB OTG and I also do not use ADB?
TIA
Dave
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Help with automating the Dalvik-Cache wipe
Thanks for the reply Leapinlar!
When I am booting into in CWM recovery and choose the Dalvik-Cache wipe is it wiping out both /data/dalvik-cache and /cache/dalvik-cache?
How long do I realistically need to wait before I can determine I am in a bootloop situation? I do wait 10 minutes but maybe less time?
Does CM 10.1 boot time dramatically increase over time or does adding apps also increase the boot time ?
I found a script on: http://smanager.wikidot.com/scripts:power-scripts[/U "Superclean and reboot "
As a newbie I would like to know which file or directory to put a subset of this script so that it automaticly runs when I poweroff or reboot via the power button even better would be how to add a popup question box asking me if I want to wipe out dalvik-cache as part of the shutdown.
TIA
Dave
leapinlar said:
What is CM safe mode?
The dalvik cache is split into two places. The system app dalvik cache is stored in /cache/dalvik-cache. The installed apps dalvik cache is stored in /data/dalvik-cache. It does no harm to clear those caches periodically. It just takes a while when you reboot for the operating system to rebuild them from the apks.
So you should be able to manually delete the /data/dalvik-cache folder with your file manager just before you reboot. I am assuming that is the one giving you problems. If not it, try the one in /cache.
If you know how to write scripts you can automate it.
Edit: if it turns out to be the dalvik-cache in /cache causing the problem, I have a build.prop setting to move the /cache dalvik to /data.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
safe mode on CM 10.1
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
leapinlar said:
The CWM dalvik wipe wipes both of them.
Yes, adding apps increases boot time. The operating system has to verify that the dalvik cache files match the apks. The more apks installed, the longer the boot. If they do not match, it rebuilds them. If they are missing (like after a wipe) it starts rebuilding immediately without checking. 350 apps sounds very high. Do you really need that many?
Some have said that the ability to read emmc decreases with use (kind of akin to defrag on a PC). That is what that trim controversy is all about. There is a process where that can be cleaned up with the trim app, but it has been known to brick certain Samsung memory chips (and some HD+s have them).
I don't know anything about that script or where to put it to execute on power off. You put it either in /system/etc/init.d or /data/local/userinit.d to execute on startup.
And you have still not told me what CM safe mode is.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
[email protected] said:
safe mode on CM 10.1
Press power button and then press and hold reboot option..
Phone / Tablet will ask you to boot in safe mode or normal mode..
I did this twice in the past
So the apps folder upon reboot is much smaller as most APKs are not loaded in this safe mode
I am kind of a newbie with CM but it is very nice
TIA
Dave
Click to expand...
Click to collapse
Huh! That is a new one for me. LOL. Thanks.
If it boots faster in that mode, that tells me you have too many apps.
Sent from my Nook HD+ running CM10.1 on emmc.
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Will try disable 'quick render' in the launcher settings.
Aaron thanks for the info * I will see if helps my bootloop issue
I went to Trebuchet settings to uncheck 'quick render' in the Homescreen panel
TIA
Dave
Solution: quick & dirty automating the Dalvik-Cache wipe
Thanks to Leapinlar for great explanations and patience and
Kudos to Bartito for his Shutdown APK!
Just tested the instructions below on HD+ CM 10.1
Leapinlar can you please verify the commands before other users try this as I am still a Newbie to CM
after following these instructions I powered on the HD+ and the dalvik-cache rebuilt 268 APKs without needing to boot into CWM recovery
This will continue for every poweron and reboot until the script /system/etc/shut.d/rmdalvikdata is removed
The boot process is obviously delayed significantly but hopefully no more bootloops!
1) launch terminal emulator app and type these commands from the terminal:
su
mount -o rw,remount /system
mkdir /system/etc/shut.d
chmod 755 /system/etc/shut.d
echo "rm /data/dalvik-cache/*" > /system/etc/shut.d/rmdalvikdata
chmod 777 /system/etc/shut.d/rmdalvikdata
ln -s /system/etc/shut.d /system/etc/shutdown
exit
exit
2) please, download the "SystemScriptsExecutor-cwminstaller.zip"
from: http://forum.xda-developers.com/showthread.php?t=1387692
Note: I saved it the zip file to the MicroSdXc card
3)install SystemScriptsExecutor-cwminstaller.zip from CWM recovery on Nook HD Plus.
Note: I actually used vi on term with a USB keyboard to create /system/etc/shut.d/rmdalvikdata
and I am not sure the symlink is necessary
It looks correct. And I would leave the symlink in. The Executer may need it.
Sent from my Nook HD+ running CM10.1 on emmc.
I saw the same problem on cm-10.1.3-RC2-ovation: "wallpaper quick render" enabled causes bootup to stall on the animated logo. Clearing cache was the only way to complete with it enabled. Disabling restores the ability to boot and reboot normally.
It's a devious bug as you might only run into it days after enabling the feature. In my case, it was a few days after a fresh CM installation, having setup and installed everything the way I wanted. adb logcat didn't show anything obvious within the boot loop. I spent a while building the installation back from scratch with incremental nandroid backups attempting to find the point where things broke. Glad I found this thread instead!
It'd be nice to have it fixed as quick render makes scrolling between home pages noticeably smoother.
Aaron Camp said:
Your boot loop sounds similar to the one I had for a while. It just sits at the Cyanogen Mod circle for EVER. The fix for me was to go in and disable 'quick render' in the launcher settings. (Remove the checkmark)
Click to expand...
Click to collapse
Thank you sir! I have struggled with this and your suggestion seems to have cured the problem. I have spread the word in 2 other threads.
Wish the developer would see this. Then, perhaps, a fix might be in the future.
How can I truly fully wipe my N6 XT1103 32GB so that it would be virtually impossible to restore any sort of data.
I want to make sure that any emails/accounts etc. are completely wiped and can never be restored.
Running stock 7.0.0 (NBD92G, Apr 2017) never rooted/unlocked etc.
Thanks
Fastboot oem unlock .. then fastboot flash twrp, then format data (where it asks you to type yes) then reboot. Profit
Any way of doing this without having to unlock,flash recoveries etc.?
The phone is encrypted if that matters.
Thanks
ursidae1 said:
Any way of doing this without having to unlock,flash recoveries etc.?
The phone is encrypted if that matters.
Thanks
Click to expand...
Click to collapse
Sure, I just like to be thorough. Just go into settings and do a factory reset. Settings > backup&reset > factory reset. Then connect the phone to computer and check if any files remaining
dictionary said:
Sure, I just like to be thorough. Just go into settings and do a factory reset. Settings > backup&reset > factory reset. Then connect the phone to computer and check if any files remaining
Click to expand...
Click to collapse
I heard that factory reset doesn't truly delete the files.
Some people after factory reset fill the phone with random data to remove the old invisible but not deleted data underneath.
Any comment on that?
Thanks
Wipe everything in TWRP (Factory Reset, Advanced Wipe everything, Format Data), and reboot back to recovery
Do the above again without rebooting (wipe everything again but don't reboot)
Mount firmware (Mount -> firmware)
Perform fstrim on /data, /cache, /system, and /firmware (can use adb shell or the terminal from TWRP; the command is fstrim -v /data (run it and then run it 3 more times changing data to cache, system, and firmware)
Reboot either to bootloader (if flashing stock), or recovery (if flashing a custom ROM)
Wiping everything twice with TWRP is mostly just an old habit from when that process was a little flaky on an unrelated device in the past (sometimes it wouldn't actually wipe partitions the first try). The fstrim erases data on the block device that's marked for deletion. Basically, the partition wipe throws a blanket over the data, and fstrim obliterates it for good
ursidae1 said:
How can I truly fully wipe my N6 XT1103 32GB...
Click to expand...
Click to collapse
In case someone else is going to use the wiped N6; don't forget to dismount this device from your account. To avoid Google's security blocking.
a little off topic, can i flash ota image from google going from 7.0.0 (NBD92G, Apr 2017) to 7.1.1 (N6F27H, Jul 2017)?
I tried going from 7.0.0 (NBD92G, Apr 2017) to 7.1.1 (N6F27E, Jun 2017) and it gave me an verification error at about 40% while copying.
Should i go apr may jun jul in sequence or thats not the problem?
Thanks
Or you can use Wug's Toolkit to completely wipe your device and storage, then d/l the newest image and use Wug's to flash it, unlock it, root it, unencrypt it, etc
Wug's NRT
Factory Images
HipKat said:
Or you can use Wug's Toolkit to completely wipe your device and storage, then d/l the newest image and use Wug's to flash it, unlock it, root it, unencrypt it, etc
Wug's NRT
Factory Images
Click to expand...
Click to collapse
THANK YOU!
Hello,
today I did have a strange experience with my ROG 2 and my best guess is that there is some UFS problem, but a second opinion or ideas are welcome.
During a bike ride when I was wifi scanning (apps: "Tower collector", "Radio Beacon"), navigating and listening to an audio book, the phone just went dark. I thought from previous experience on a Note 3 that it might have overheated. Pretty much stress proofed from the previous phone.
Yes - it was warm in its bike pocket but really not overly hot.
The phone is an ebay buy 2 months old and has been ever since with omnirom, stable so far. I only noticed that the RGB LED here has no blue light, but I plainly did not care.
I tried to boot it after some 10 minutes again and the phone would not go past its omnirom boot screen until it reboots after some time, boot loops.
30 Minutes later at home I wondered then what is going on, and I copied off the TWRP backup from the phone I took two days ago, just in case.
I then tried to restore the same backup, but the phone switched off during restore after ~30%. This was reproducible, so I thought this may be something with the backup, maybe I cannot restore a partition. When I restore I had all partitions marked and I tested them one by one. The restore of single partitions worked, one by one, except vendor as it was marked read only and data as it failed unpacking (my recent backup then is dead?).
I then tried formatting the partitions, so "data", originally f2fs. I lack experience with journal recovery on f2fs so went to ext4. System was ext4 and was just wiped. I lost of course other data on the internal storage so tried to restore again with my copied backup. It restores, but it cannot boot and just bootloops. I now formatted all partitions, including vendor.
Finally, I tried downloading omnirom again and installed it. It won't boot, it doesn't even get to the boot animation, but just boot loops.
I reformatted data back to f2fs. But no change here.
Trying more: lineageos won't flash for unknown reasons, it immediately dies as "Error installing zip file". Checksum of the downloaded zip is correct.
I downloaded a stock rom and installed it. This is now the best result so far - It does want to boot.
Here I get a boot animation and this incredibly lame "tching" sound (it is a phone, not a sword...). But it also stops there and never continues. Yes, first boot takes longer, but not 10 minutes.
Any ideas what else to try with this phone?
So far, I can boot twrp via sideload and interact with it fine. But that will be it; ran out of ideas.
Happy for suggestions.
Gaya
Use raw firmware to restore everything.
Install latest firmware zip on both slots.
After installing custom roms go to wipe -> format data by typing yes. Otherwise rom wont boot
thanks for getting back, If by raw firmware you meant the ASUS stock, I did. Not sure why data wipe after installation or double install to a/b partition would make a difference, but in the end I am new to this a/b concept, looks though like standard dual boot to me. Tried it, but no difference.
- installed asus firmware to inactive B
- switched to B partition
- installed asus firmware to inactive A
- wiped data
- started, so far same behaviour after 15 minutes of waiting (boot animation with sound, then it repeats boot animation until ...).
There are Two kind of rom raw firmware (used to restore bricked device) and recovery rom (zip file we use for update)
Raw firmware will flash ROM to both the slots, while recovery rom only flash to one slot. So you need to Only select reboot to recovery after flashing ROM to switch to the updated slot.
No, stock rom is not exactly raw firmware. RAW firmware uses EDL mode (in bootloader) to flash the stock rom. Download A10 raw from here version .90.
when extracting it you will see some files.
Steps To flash Raw:
* enable usb debugging in phone.
*connect the phone via side port to pc
open command prompt and run this command
adb devices
adb reboot bootloader
Now go to the folder where you extracted the raw firmware & run "flashall_AFT.cmd" as admin
wait [there will be no output]. After 15 -20 mins your device should boot. If you have any old version stock rom data the phone will carry the data to new version. If you have any custom rom/ updated version of stock rom data, it will ask to factory reset, so do that.
wiping is not exactly formatting so do it the right way
Why format: the one where you format by typing "yes" .If you switch between Roms ( stock to custom or vice versa) and go back to older versions (v .100 to .60) the old/previous rom data cant be used with new one so you must format data.
when formatting is not necessary : If you want to upgrade both stock images (version .90 to .100) & custom rom (v 1 to 1.2) i.e., flashing stock rom and then custom rom over it, you dont need to format data because you can reuse the data from custom rom to updated custom rom.
A/B device use two partition instead of one. so the upgrade can happen in the background. On restart you will switched to updated slot. So room for error is less.
The wiping here should be the same as formatting, as it is running the mke2fs (as per TWRP settings). But raw rom I do not have (I believe).
The link you have there seems broken, could you repost it again?
I did download the stock ROM earlier from ASUS directly, to not violate policies, HTTP links etc, here is only the path on asus . com
pub/ASUS/ZenFone/ZS660KL/UL-ASUS_I001_1-ASUS-17.0240.2103.75-1.1.229-user.zip
That is the one I installed via recovery. Am not sure what is in your mentioned flashall_AFT.cmd though, but suspect some adb sideload at least.
I eventually succeeded, but of course would liek to know
1) why
2) what happened?
I did follow a video about flashing the stock rom, basically as you explained (factory reset and data wipe), twice to a and b partition. That made the device bootable. Why is this needed?
I tested wiping system again (I am used to doing clean flashes) and installed omnirom again, and it failed booting.
I installed again the a/b with stocks, factory reset and data wipe and installed omnirom as dirty flash. All is well.
Now I was able to restore my backup finally without the device switching off and it did not complain about the data backup. So finally I am with my phone again rom and copy data to my fresh partition.
as to 1) why?
I understand a/b partition as sort of windows/linux dual boot with a more separate bootloader maybe. So I do not see the point in flashing the stock rom twice or in rendering the device unbootable when wiping system.
and as 2) what happened.
I may only guess: I did an omnirom upgrade 2 days earlier that worked fine and was the reason for my nandroid.
During my ride, the phone had some whateverissue and rebooted. I am unsure whether i tested booting but assume that after the upgrade it flashed to the other partition and it was not bootable. It does not make sense as this would make a/B partitions rather hard for custom rom makers, e.g. people complaining all the time.
Other guess: there was a file system issue with f2fs. Problem with data partition seems to cause bigger issues.
When I flash to ext4 after testing the bootable rom with a wiped data, it would not boot anymore. After factory reset again, it mke2fs the data partition again, back to f2fs and the device booted again happily.
Thanks for the help. Happy to know/learn more about this issue, as I would love to prevent or handle them quicker with more of I know what I'm doing.
Android Dual Partition (A/B) is made for seamless updates i.e, Dual system/vendor partition but uses same data partition. Lets say you are currently in slot A when you apply system update the slot B gets updated. As always rebooting the device switches to the B partition after update. & further update flashes the system to the A partition.
Basically there is no need to flash stock rom twice, unless you are coming from stock [one partition might be in higher firmware version than other] or there is new stock version with some minor/major upgrades to firmware files.
Our custom ROMs are not stand alone, Mostly it only replaces the system files and keep the vendor same as stock. (also this keeps the ROM update file size to be minimum)
you might even have different version of Android in A/B partition.
Here is a scenario on How A/B works:
Say you are currently using your device in B-slot and A9 so partition on slot-A will be A9 partition slot-B be A9. After that you are doing system update to A10 from System update (not via TWRP)
now you will have A10 on slot-A and A9 on slot-B.
then you want to go to custom rom, so you flashed say omni on A-slot and rebooted & it will surely work.
After that you are using inbuild system update from custom rom any applied it. now the system update will overwrite the A9's system files but (the device specifically needs A10s vendor to work properly). Now comes the fun part i.e., soft brick, boot looping, and corrupt images
That's why you have to flash latest stock to both A and B slots, and overwrite them all with system files from custom rom (also should be flashed once in slots A and B) to get neat experience from custom ROMs.
If you understand what was written above, then you will know the reason behind soft brick.
stock rom flashed only once (firmware image variation may affect stability)
custom rom only flashed in one slot (switching slot will boot loop device)
Not using Reboot to recovery to flash (you will be flashing to the same slot over and over & thus rebooting will boot loop)
Not formatting data ( Just Maybe, your custom ROM and stock uses different file system for data partition)
For Raw files search "ASUS rog 2 RAW firmware images" those files will be around 3 GB in size.