I9300 Bootloop - Galaxy S III Q&A, Help & Troubleshooting

Hi guys.
Today I turn on my galaxy s3 and it displays a motionless lockscreen (I can't turn the screen off, nor do anything with the touchscreen). It has already happened twice or three times.
I reboot it holding the power button for some time, and it bootloops.
ROM: Omnirom 4.4 (I've had it for 2/3 weeks, worked well)
KERNEL: Boeffla Kernel
RECOVERY: Philz 6.0.4.8 (I also have Aroma file manager)
It has happened some times already since I installed this ROM and I had fixed it flashing the xposed-disable zip, but this time it didn't work.
I think if I do a factory reset and reinstall the ROM everything will work, but I really can't lose all the stuff I have there (e.g. notes, contacts, SMSs, whatsapp chats...).
I cleared cache, dalvik, pulled out the battery, updated to the latest nightly via recovery; nothing worked.
Tried to unroot via Aroma FM, didn't manage to.
/dev/log is empty for Aroma FM, if I "ls" with the console it shows there are the regular folders, but I can't "cd" them for logs.
I attach the last logcat got from the Aroma FM console.
Is there any way I can get my phone back to work? Or can I save all my data?

Fanaticism said:
Hi guys.
Today I turn on my galaxy s3 and it displays a motionless lockscreen (I can't turn the screen
off, nor do anything with the touchscreen). It has already happened twice or three times.
I reboot it holding the power button for some time, and it bootloops.
ROM: Omnirom 4.4 (I've had it for 2/3 weeks, worked well)
KERNEL: Boeffla Kernel
RECOVERY: Philz 6.0.4.8 (I also have Aroma file manager)
It has happened some times already since I installed this ROM and I had fixed it flashing
the xposed-disable zip, but this time it didn't work.
I think if I do a factory reset and reinstall the ROM everything will work, but I really can't
lose all the stuff I have there (e.g. notes, contacts, SMSs, whatsapp chats...).
I cleared cache, dalvik, pulled out the battery, updated to the latest nightly via recovery; nothing worked.
Tried to unroot via Aroma FM, didn't manage to.
/dev/log is empty for Aroma FM, if I "ls" with the console it shows there are the regular folders, but I can't "cd"
them for logs.
I attach the last logcat got from the Aroma FM console.
Is there any way I can get my phone back to work? Or can I save all my data?
Click to expand...
Click to collapse
I don't know about the bootloop issue, I would just do a clean install and start again, but if your recovery is working, mount internal sd card as usb storage and copy what you want to keep to your computer.

You don't need to wipe data partition were your stuff is located. Just format system and flash the same rom again via recovery. This will wipe any init.d scripts and uncommon apps or frameworks which causing bootloop.
Only ROM, do not install Boeffla kernel.
If this will not help than make backup of data partition via CWM and copy this file by adb to PC where you will be able to extract needed data.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2

Thanks for your replies!
I've already flashed the latest omnirom zip, which formatted /system in order to be installed (didn't it?).
What do you mean by "uncommon apps or frameworks"? What will I actually lose if I format /system?
However I'm making a backup of /data anyway.

System partition store only main system files, system settings and frameworks ie xposed framework, busybox binaries. All normal apps and their settings and data are stored on data partition ie SMS, emails etc.
Formatting system is good practice before flashing different android versions but also helps to get rid of all unnecessary scripts and garbage from old ROM.
You will not loose anything important from your private data.
And you are right, usually installer script formats system partition before copying new files but sometimes strange things happens it will not harm but may help.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2

SirKunon said:
System partition store only main system files, system settings and frameworks ie xposed framework, busybox binaries. All normal apps and their settings and data are stored on data partition ie SMS, emails etc.
Formatting system is good practice before flashing different android versions but also helps to get rid of all unnecessary scripts and garbage from old ROM.
You will not loose anything important from your private data.
And you are right, usually installer script formats system partition before copying new files but sometimes strange things happens it will not harm but may help.
Click to expand...
Click to collapse
I've formatted /system and installed the latest Omnirom zip (before getting the bootloop I had an earlier version). I've turned on the device and it shows a dialog:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Like if I've wiped dalvik cache. It says "Android upgrade" "Launching apps".
EDIT:
Rebooted. Now it bootloops "as usual".
Maybe I need to wipe /boot? I don't know what to do. :S

Try different rom, cyanogenmod maybe?
Or try to launch the system in safe mode by hitting left capacity button (menu) after powering on the phone, but I don't know it works on custom roms.
Finally if you have your backup you can factory reset your phone to check it will start clean or it is a hardware failure. You can restore your backup later.
Do not format boot partition.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2

SirKunon said:
Try different rom, cyanogenmod maybe?
Or try to launch the system in safe mode by hitting left capacity button (menu) after powering on the phone, but I don't know it works on custom roms.
Finally if you have your backup you can factory reset your phone to check it will start clean or it is a hardware failure. You can restore your backup later.
Do not format boot partition.
Click to expand...
Click to collapse
Thanks mate. I will try that today, and let you know this afternoon.

I've deleted some of the last modified folders and files in /data (apps-asec, system, .sto...), formatted /system, installed the latest omnirom, and this time it boots normally; altough it is impossible to use the phone, as "Google play services has force stopped" dialogs continuously appear.
Anyway, it looks like the whole /data folder has been wiped (maybe when the system recognizes something is missing from there, it wipes the whole thing), as apps don't have their data any more; altough some configurations have been kept (wifi passwords for example), and of course my apps have been kept as well (in fact I only deleted some folders from /data). It looks like the problem lies in /data.
Is all the data I'd like to preserve in "/data/data"? In that case I could try to restore only /data/data and see if the phone boots.
However the "force stop" dialogs problem is annoying.
Thanks for your help mate!

Don't wipe manually. Asec, you have removed , is virtual data folder.
Just make sure to have full backup of system. Choose backup, advanced, and select all partitions in CWM. When it's done connect to PC and copy backup in safe place.
Enter recovery once again and select wipe data factory settings. Wipe also cache, system and dalvik from advanced wipes menu.
Flash ROM and Gapps.
Flash SuperSU zip package if you like.
Reboot system and wait until first long boot finishes.
Config your Gmail account and wait for app restoration protocol.
If everything works fine reboot phone once more and load system. Check is it OK.
If so reboot into recovery and backup this clean system with all partitions, even efs.
Repeat copying this backup to PC procedure.
Now you can try to restore only data partition from first backup via recovery mode.
Choose restore, advanced and select only data partition.
Wait for restore and reboot.
Check if it's working, or not. If you got bootloops again then something is wrong with that data partition. Can't say what it may be.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2

SirKunon said:
Don't wipe manually. Asec, you have removed , is virtual data folder.
Just make sure to have full backup of system. Choose backup, advanced, and select all partitions in CWM. When it's done connect to PC and copy backup in safe place.
Enter recovery once again and select wipe data factory settings. Wipe also cache, system and dalvik from advanced wipes menu.
Flash ROM and Gapps.
Flash SuperSU zip package if you like.
Reboot system and wait until first long boot finishes.
Config your Gmail account and wait for app restoration protocol.
If everything works fine reboot phone once more and load system. Check is it OK.
If so reboot into recovery and backup this clean system with all partitions, even efs.
Repeat copying this backup to PC procedure.
Now you can try to restore only data partition from first backup via recovery mode.
Choose restore, advanced and select only data partition.
Wait for restore and reboot.
Check if it's working, or not. If you got bootloops again then something is wrong with that data partition. Can't say what it may be.
Click to expand...
Click to collapse
It bootloops, so the problem lies in /data. If I manually copy in /data "apps", "apps-lib" and "data", the new rom does not see them. I will restore apps and data with some nandroid extractor.
Thanks for you help.
Last thing: I'm now trying to restore apps+data with this app, but it kepps saying "unable to create applist". How can I restore them? Is there any better app for this purpose?

Related

Non-booting SII with CM 7.1

As of yesterday, my CM7.1 phone won't boot - it gets stuck at the "rotating arrow" blue Android for ever. It's a Samsung Galaxy S II GT-9100.
I have been running CM 7.1.0 for several happy months now, and haven't tried to install or upgrade my ROM. The last action I took before this happened is that I made a full system backup (using CWM 5.0.2.6).
That backup is present on the internal memory. I can boot into recovery, mount drives and access devices using adb shell. So I do have an opportunity to fix what's broken, if I can work out what it is.
Given that the last thing I did was a backup, I checked to see if any of the partitions were full, but none are. (None is more than 42% full according to df; although strangely, df does not show any partition mounted on /.) I tried making another backup, watching carefully - that worked fine. I tried restoring the first backup - no improvement.
I've also tried wiping everything Recovery allows me to that's non data-destructive - cache, Dalvik cache etc. It hasn't helped.
How do I work out what's wrong? Is there a boot log file anywhere which might give me a clue as to what is wrong? I've searched for "*.log" but can't find anything obvious.
I don't want to do a factory wipe if I can avoid it, because obviously that will lose all my data. If I do a factory wipe and restore just the data partition, does that put me pretty much back where I was? If so, how do I restore just the data partition? The Restore option in CWM Recovery seems to do full backups only, and only from a particular directory.
The original CM and Google Apps zips are still on the internal SD (same versions as are currently not working). Would it be worth trying to reinstall those, without wiping? Or would that be data-destructive?
Any other ideas?
Thanks!
Gerv
SOLVED - remove 0-byte data/system/profiles.xml
I tried doing a full factory reset from Recovery. This got the phone booting again, but without any of my data . Fortunately, ClockWorkMod has a "partial backup restore" function. I restored the data partition... and the phone stopped booting again.
So this is progress. I now had some idea where the problem lay. I finally found it using a laborious 5-minutes-per-cycle manual bisection technique. Delete half the stuff on the data partition, reboot, if it still fails, delete more, reboot... once you get it to boot, restore the data partition, narrow it down further. Once you find a top-level directory, repeat the process inside it.
The result: the existence of a single 0-byte file stopped my phone from booting entirely. The file was: data/system/profiles.xml.
I have no idea what that file does (there are only a few references online), how a 0-byte version of it got created, or why having it existent but empty breaks things but if it's not present everything works fine. I have no idea if anyone else will ever see this problem, or if they will ever find this forum post. But still, here's my Wisdom of the Ancients (google the phrase for the relevant XKCD comic).

Unable to access or backup /data, everything FCs

Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Flash a clean ROM, wipe cache and dalvik, do a factory reset and start from scratch.
Multiple fc can be caused due to several reasons like:
-wrong phone.apk
-wrong framework
-wrong ROM
-too much undervolt
Sorry for telling but my first sentence might be your fastest approach.
Tapatalked from my Samsung GT9100
Tyrol said:
Hello, I'm running RR 2.6.1 with Dorimanx's latest kernel and I've run into a huge problem.
I'm not sure what the trigger is but I think it could be updating the SuperSU app, or it could just be that I'm super unlucky. In any case, I really really hope someone will be able to help me here.
I was facing random freezes and SODs on the kernel but I was in the midst of tweaking my settings to see if I could fix it. I updated the SuperSU app on the bus on the way home, went home & tried to power my phone on but it wouldn't work so I force-restarted by holding down the power button. When it rebooted, I had all sorts of FCs so I went to CWM Recovery & cleared cache & dalvik & fixed permissions. Nothing worked. Here's what I've tried so far:
- reflashing the kernel
- reflashing the ROM
- re-rooting via Odin
- flashing another kernel (I tried fluxi but it was stuck at the animation screen & wouldn't boot)
- Googled for how to fix process.acore and Gapps FCs, tried to clear all the Google-related apps' data but they wouldn't clear
- trying to delete the apparent offending files from /data/data/... via adb and Android Explorer but it didn't work, kept saying it was read-only or something, even though I followed all the instructions to SU and mount as RW
By this time, exTweaks didn't recognise the kernel as compatible, Whatsapp and TB FC'd, just about everything FC'd.
I went into CWM Recovery to try and make a Nandroid but it said "Error while making a backup of /data".
I am truly at my wits' end. My phone wouldn't even let me access it after the right passcode was input. At this point, I just want to go in and backup my Whatsapp and relevant TB apps.
Please, if anyone is able to help me, PM me or something. I'm on Skype if you're so kind as to be willing to walk me through anything you think may help.
Thank you.
Click to expand...
Click to collapse
Try the following:
-Download this: Ultimate kernel cleaning script
-Reboot to CWM recovery
-Flash Ultimate kernel cleaning script
-Under kernel specific option, Reset extweaks settings
-format /system (under Mount and storage)
-Flash ROM (RR 2.61)
-Flash Gapps
-wipe cache partion
-wipe dalvik cache (under advanced)
-fix permissions (under advanced)
-Reboot your phone
My above steps will not wipe your and should definitely fix your problem
good luck
Thank you both for your suggestions!
Unfortunately, I didn't get to try them but I'll definitely be checking this again if (touch wood) this happens again. Hopefully it'll be useful to someone else facing similar issues, I know I couldn't find clear answers on what to do.
@jokesy If the /data partition is somehow stuck at read-only, I'm not sure formatting /system will help. I could be wrong, I apologise if I sound ungrateful ('cause I do appreciate your help) but wouldn't reflashing a ROM kind of overwrite the existing /system files already?
I'm not aware of the details and technicalities of what exactly happens during a ROM flash but according to the AROMA installer, it seems like /system is wiped first.
What I did
Gave up on backing up apps & WhatsApp through the normal ways, most of my TB apps are backed up daily anyway, just lost some data like that for Sleepbot.
Pulled WhatsApp database files from /data/data/com.whatsapp via ADB, restored the previous day's Nandroid backup & copied the database files to the relevant directory. I guess it may seem minor, but as everything was melting down on my phone, I kept getting messages from friends about project work in school & other stuff that I couldn't read so I really wanted to not lose all the new messages that had come in.
Restoring my Nandroid (thank God I backup daily) fixed everything, fortunately, but there are little quirks I'm still ironing out. Eg. My Godville app can't seem to connect to the main server & retrieve details of my character despite clearing data, uninstalling & reinstalling. Not too sure why.. :/
-----------------------
サンソングガラクシS II からタパトクで書いた。
@Tyrol
Ididn't know you were using aroma installer though, but formatting /system has nothing to ago with /data sms vice versa
Following my wouldn't have hurt though, ur would only ensure a clean system partition before install.
I'm happy for you
Better luck next time
Swyped from my Samsung Galaxy SII
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Karl.morteo said:
I recently had a very similar problem. The only way I could resolve it was to also format /data during the usual full wipe re-install
Click to expand...
Click to collapse
Tough luck man. I don't know why the data corrupts spontaneously, it happened once to me when I was playing Plague, everything started FC-ing all of a sudden while I was in-game. Bizarre. Didn't want to do a full wipe so I just restored the /data partition from my latest Nandroid.
-----------------------
サンソングガラクシS II からタパトクで書いた。

[Q] HELP! Odd problems - rom & recovery independent

Had a bad USB connection in my old phone, so AT&T just swapped it for a new one.
I immediately flashed Clockwork recovery and tried installing SlimBeam ROM.
Noticed some weird problems:
the notification bar is blank (I've got the toggles, but nothing else)
the home button didn't work (does nothing)
maps and other location-services failed to work (no network location errors)
Calendar data gives errors trying to sync with my Google account,
Contacts not syncable at all (doesn't even show as an option in sync settings)
So booted back to recovery and:
did a factory reset
cleared cache
formatted /system
installed slim & slim gapps.
Didn't install any of my own apps, didn't restore anything from Titanium Backup.
Not only did the problems persist, but I got android keyboard (aosp) errors on all text entry fields.
I thought I'd try a different rom.
Trying to install Paranoid Android gave me an assert error, so I SWITCHED FROM CLOCKWORK RECOVERY TO TWRP.
In TWRP, I did a factory reset, wiped data, wiped cache, wiped dalvik cache, wiped system, then installed Paranoid Android and the latest Google Apps.
SAME PROBLEMS, including the keyboard issue.
And I get an error connecting to the Play Store.
Anybody ever hear of something like this before?
The problem can't be in /system or /data, since I have wiped those before reinstalling.
And they appear to be independent of ROM and recovery package.
While it could be hardware related, in my gut I feel it must be something in the software.
Could there be a problem with files that ROMs and Recoveries don't touch? Something in the /dev, /efs, /sys, or some other folder?
I am curious to know what's going on, and am willing to do some troubleshooting and posting of logs.
But, more importantly, what can I do to get all this functionality working properly?

[Q] Proper ROM-ing procedure

I'm going to be ROM-ing for the first time (well, other than Safestrapping the Bionic for a day or two) and want to make sure I have the right thought in terms of running and upgrading a ROM over the long term. If I'm moving to AndroWook as my daily driver, I want to make sure I have a good procedure in place for quickly and easily upgrading to the latest version of the ROM.
The following is my understanding of this whole process. Is this procedure correct? My main concern is making sure I am doing everything right to be able to quickly update to the latest version of the ROM when it comes out, not spend a day re-configuring. Is there anything I am missing?
BACKGROUND: Partitions
Main Partitions Involved With Wiping
/system = Where the OS lives, along with the apps that are preinstalled
/data = Where user installed programs & their associated data/settings live. This data/settings is the part that gets deleted when you go Settings -> Applications -> pick an application and click "Clear Data". This is what Titanium Backup backs up for user apps (both the "apps" and "data" backed up live here). Also has SMS, contacts, settings, etc... the "system data" in TiBu
/cache = Cache files that help programs to load quickly. Harmless to wipe, as it will regenerate.
/sdcard = Internal sd card area where you keep files and use file manager. some programs also put files here. Not usually wiped.
external sdcard = Physical external sd card, if applicable. Not usually wiped.
Other partitions
/boot = Kernel and ramdisk. Don't wipe unless you fix it before rebooting.
/recovery = Where the recovery (stock or custom) lives.
/misc = Other settings not normally touched.
BACKGROUND: Types of Wiping
Cache = harmless. Cache regenerates itself over time to speed up phone.
Dalvik = harmless. This is simply another cache, this one having to do with Java.
Factory Reset = wipe /data and /cache. internal and external sdcard is NOT wiped
Wipe system = wipes /system (where the os and its preinstalled apps live)
Format data = wipes /sdcard (the internal sdcard)
Format external sd = wipes external sd card
ASSUMPTIONS & NOTES
You are rooted
You have Titanium Backup (TiBu)
For multi-user environment, modify the instructions to account for the need to backup/restore with TiBu for each user. Backup for each user, flash, then restore for each user.
BACKING UP
1. TiBu: Batch Backup all user apps & data (everything) in current ROM
2. TiBu: Batch verify the backup
3. Make a sketch of how your widgets/homescreen is supposed to look
4. If you are doing a total deep clean that wipes sdcard (generally not), here is where we want to back up anything else (sdcard files, etc)
5. File Manager: Backup apk for both TiBu & TiBu Pro to SD card
Alternate: Do nothing now, and we use market in new ROM later​6. Download ROM & put on SD
WIPING & FLASHING
This part subject to change based on ROM maker's recommendations
1. Boot into recovery
2. Wipe and flash:
Option A: Clean flash (typically done, does NOT wipe sdcard):
1. Factory reset
2. Wipe cache
3. Wipe dalvik
4. For a total deep clean (not usually done, DOES wipe sdcard): Wipe system; Format data
5. Flash zip
Option B: Dirty Flash (usually only OK for minor updates):
1. Wipe cache
2. Wipe dalvik
3. Flash zip
4. There is no need to set up the ROM again in this case.
SETTING UP NEW ROM
1. Boot into new ROM
It will take 30-60 minutes to get up to full speed. After that time, it will be full speed after a reboot.
You can tell it to keep backed up to Google (backups up TO Google), but tell it NOT to restore from Google right now (restores FROM Google right now).
2. System > Applications > Unknown Sources
Restore TiBu & TiBu Pro from apk backup
Alternate: get from market
3. TiBu: Batch Restore system data - ONLY THE GREEN ITEMS
Do not restore red items
Do not restore user stuff yet. We are doing system stuff first.
Note that icons will not show correctly yet... nothing to be concerned about.
If the new ROM is vastly different, take care to restore only what is necessary.
4. Reboot
5. TiBu: Batch Restore missing apps with data - ONLY THE WHITE ITEMS
6. Click Market Doctor to verify that everything is hooked back up to the Market OK
7. Fix up homescreen - widgets & wallpaper
One by one, delete empty Widget then add new one.
Also choose the wallpaper you want
8. Check:
Date & time, alarms, ringtone, voicemail number, other settings
Anti-theft is operating properly
9. Market Place > My apps > Update any other apps
10. If over the course of time you find any apps giving problems, use the market to uninstall them and reinstall them to clear out any problems it may have had in restoring from TiBu
I just glanced thru that and this is what I saw quickly.
Option A: clean flash..... I always wipe system as well. This is not a big deal if you don't do it because I format the system in the installer in case people have forgotten.
I also delete cache and dalvik in the installer also in case people forget but I still end up doing them on the wipe page.
The only one really you need to use for a major version update is factory reset. This is just on my rom tho.. I can't speak for how others do it so always best to do the manual wipes also.
Tibu : It is never advised to restore system apps. Even between minor updates in case I have changed a system app.
If there is one that you really need restored then try restoring just the data for that one app and test it properly.
In the installer I do not write all apps to system anyway. There is very little in there that would take more than a few seconds to set back up.

Xposed framework working?

Do you know if there's a way to get Xposed working? I tried the Xposed Framework SDK 26 from inside Magisk, but it put me in a boot loop.
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Well actually yes xposed is available. But I left this solution for a long time in favour of Magisk and it's modules to be honest
Sent from my HTC U11 using XDA Labs
thref23 said:
I think we now have Xposed - check the end of this discussion:
https://github.com/rovo89/Xposed/issues/310
I might give this a go when I'm feeling less lazy.
Click to expand...
Click to collapse
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment xposed-v90-sdk26-arm64-beta4-test1.zip
Install View attachment XposedInstaller_3.1.5.apk
PROFIT!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ZeuseZ said:
Thanks a lot for the link! Thanks a lot to rovo89 for the beta4!!!
xposed-v90-sdk26-arm64-beta4-test1.zip works fine on SHT-AL09 after flashing it via TWRP
What we need:
ROOT
TWRP
Flash with TWRP View attachment 4525802
Install View attachment 4525805
PROFIT!
View attachment 4525804
Click to expand...
Click to collapse
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Anyways, Edge and Edge Pro work. They don't remap the fingerprint sensor functionality. But they have other useful features.
thref23 said:
If I'm not mistaken, in the event of a bad module, Xposed can be disabled at boot by pressing a hardware key over and over again. Not that I want to find out.
Click to expand...
Click to collapse
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Apo11on said:
Which hardware key would that be? And what exactly does "over and over again" mean - how many times or for how long?
Click to expand...
Click to collapse
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Lukest85 said:
While the device boots you can activate the xposed safemode to disable the framework & modules, without flashing any files and without entering recovery or ROM.
Background:
People are posting when stuck at boot screens or bootloops with xposed installed and there have been lots of great solutions/advice from the community but I have not seen much info posted about the xposed safemode so thought I would share what I believe to be the easiest & first thing to try in order to boot & troubleshoot your setup.
To disable xposed:
1. Repeatedly press any single hardware button during early startup (as soon as device powers on)
2. Wait for device to finish booting into recovery/ROM
3. Fix your setup
Details:
1. The first recognised key press generates two vibrations
2. Then continue to press the same hardware button four more times within 5 seconds
*Each key press generates a short vibration*
3. Success is confirmed with a long vibration
NB
• Activating safemode adds the file 'disabled' (no quotes) to data/data/de.robv.android.xposed.installer/conf/
• The 'disabled' file can be created manually from recovery or rom to disable xposed & modules
• If problems with hardware buttons try pressing the touchscreen to activate safemode
To re-enable xposed:
1. Remove the file 'disabled' using file manager or terminal
2. Reboot
3. Enjoy
***common reasons for xposed related bootloops are due to xposed module/s conflicting with system or each other, and user installing the incorrect framework for the device/sdk. Please investigate these options first and read/search the xposed Q&A OP/thread if you're unsure before posting or contacting devs***
xposed Q&A thread:
http://forum.xda-developers.com/showthread.php?t=3030118
Disclaimer:
**I cannot guarantee safemode works with every version of xposed or every device but it has always worked for me on differing setups, roms & devices.**
I hope this is helpful and will be updating the post again so stay tuned for more detailed/technical info.
Give thanks to talented & amazing devs: @Tungstwenty - xposed safemode @romracer - xposed @rovo89 - official xposed
Fantastic work & great dedication !!!
Click to expand...
Click to collapse
thref23 said:
Any key. This must be where I read it:
https://forum.xda-developers.com/xposed/xposed-safemode-disable-xposed-easily-t3230336
Click to expand...
Click to collapse
That's not really helpful in our case. It says to keep pressing and then it will boot into recovery. Step 3 says "Fix your setup" . If TWRP is not working properly (and that's exactly point - it does not, so there is no fixing) there is no benefit in booting into the recovery. Doing stuff like clearing cache does nothing when Xposed module screws up the rom. Not to mention you dont really need this Xposed "feature" in order to boot into recovery or download mode. You can just shut down your device and then use the regular, designated hw key combination in order to boot into either.
Apo11on said:
A lot of Xposed modules do not work. GravityBox, which is my favorite, completely f*ked up the rom - had to reflash. Tried a couple of others - didnt break things, but didnt work either. It's dangerous to try these modules, because TWRP restore doesn't really work.
Click to expand...
Click to collapse
TWRP restore works fine for me.
magnumlove said:
TWRP restore works fine for me.
Click to expand...
Click to collapse
You have different M5 model than mine - the 10" if I recall correctly. Partition table and a bunch of other things are not the same. You have the same or very similar model as the OP from that twrp thread, so it's not surprising the recovery works for you. If someone with SHT-AL09 says the restore works for them - that's a different story, and I'd have to start troubleshooting my own device. As of this moment, I think this recovery build is not fully compatible with 8.4" LTE version. It's failing to mount /system and /vendor partitions, and after some troubleshooting I've done I can see there are 4 versions of mount binary on my device. For example, when I manually invoke the one in /sbin folder - I can do "mount -o remount,rw /system" just fine, but when I try the same with mount version from /system/bin folder - it fails. And there is 2 more of them. It's not clear which one twrp is using when it's trying to mount partitions for restore, but it's obviously the wrong one. The only way I see to fix this is to recompile twrp.
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Apo11on said:
"seems to work perfectly" and "I have not tried to restore a backup" are contradicting statements in this context. "seems" sounds like a guess. If you want to be about 95% sure it will work -boot into twrp, goto Advanced->Terminal and type "mount". Examine if your /system and /vendor partitions are mounted as "ro" or "rw" - if it's ro then your restore is likely to fail. Needless to say, to be 100% sure you have to actually attempt a restore. Make certain to decrypt your /Data using PIN/password when twrp prompts you, otherwise you will get screwed. TWRP doesn't need to decrypt in order to wipe, and it wipes the /Data partition before every restore. If you don't decrypt and attempt restore - /Data will get wiped, but then the /Data restore will fail, because it's encrypted. In that case, theoretically you should be able to boot into twrp again, and it should prompt you for PIN /password to restore /Data again. Once you provide it and successfully decrypt - you should be run the restore again and restore the missing /Data partition from nandroid backup.
Click to expand...
Click to collapse
Without rebooting back into TWRP, I think all partitions are mounted r/w. Previously, if I unchecked 'mount system partition read only,' it would stay checked - not anymore. And I was able to successfully flash Xposed. That's what I mean by "seems to work perfectly."
I have TWRP backups now, that I hope I never have to try and restore. For now I'd much rather leave well enough alone than to be 100% certain. Plus I kind of hate rebooting.
thref23 said:
I have the SHT-AL09. When I was bootlooped (I was actually more bricked than bootlooped), I installed TWRP, and I could not mount anything (except my SD card) as read/writeable.
After the equivalent of a factory reset, I installed TWRP, and it seems to work perfectly.
I have not tried to restore a backup. But I wonder if doing so would work after the equivalent of a factory reset, if not while bootlooped.
Click to expand...
Click to collapse
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Apo11on said:
A lot of Xposed modules do not work. didnt break things, but didnt work either
Click to expand...
Click to collapse
same here, most modules don't work, has anyone found a solution?
Si73 said:
Restore works fine from EMUI to EMUI. I had issues when trying to restore back to EMUI from a GSI-TWRP hung on the splash screen. Managed to restore in the end after flashing stock system img. All my back ups were made with PIN screenlock removed.
Click to expand...
Click to collapse
I don't have screenlock but I haven't managed to create any backup, because of the famous 255 error
I've got huawei mediapad m5 lite (bah2-w19)

Categories

Resources