Related
hi!
i installed the regulat 1.6 update to my FP1 and everything was just fine.
then I tried to install the "unified 1.6 update" which worked but the problems begun:
things I noticed:
1. backup ist not really a backup for the apps but just a way to reinstall the apps I had installed without any settings. not a fun way to find that out when reopening your apps.
2. the update to the 1.6 unifyed also messed with my SD card and deleted files and put new ones there. not something I was expecting. luckily I had a backup of the SD card.
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
As all my settings are gone anyway I am open to reinstall the phone from scratch.
fivel_ said:
the thing I am looking for a solution:
after merging the partitions I cannot acces the phone storage on my PC (mac osx 10.9.4). not directly as a drive. the android fil transfer tool works, but it does not have all abilities finder/explorere provides. how do I get acces to the phone storage again?
Click to expand...
Click to collapse
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
I am not a mac user but I think you need to install some additional software.
https://www.android.com/filetransfer/
_keesj said:
Because of the partition layout it no longer is possible to expose the internal storage as mass storage device. Adb will work but the preferred way of transferring files is using the MTP protocol.
Click to expand...
Click to collapse
thanks a lot, that is what I feared.
hi, i'm also have an upgrade problem: mine is that i can't upgrade at all.
i've repartitioned earlier with the app mentioned in the wiki (wiki/Fairphone_Fairphone/Guides#How_to_partition_your_Fairphone).
i've also done the steps _keesj descripes in thread "unified storage setup on re-partitioned FP1" ("Steps for "fiixing" your upgrade").
i'm having Cherry 1.6, and two 7 GB partitions.
does anyone has a solution?
see other (missplaced) post
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Donat.Callens said:
This post might be of help:
http://forum.xda-developers.com/fairphone/general/unified-storage-setup-partitioned-fp1-t2834642
Click to expand...
Click to collapse
thanks, i've read it again and tried _keesj's solution again, unfortunately it didn't solve my situation.
i'm a layman in this area, so probably i shoudn't haved 'played' with partitions at all (but with the app it was easy).
my previous post wasn't quite complete... i have had an unified partition before...
because of an app that didn't work, i used the repartition app again to see if that could solve the problem.
it did, but later i wondered if a wrong install in the unified sistuation was the problem... so i thought 'let's try the unified partition again'...
i thought i could simply re-use the Fairphone Updater...
so maybe i'm now having a unified partition divided in 2?
and lost the ability to ever upgrade to newer versions of the Fairphone OS?
i hope someone can help me...
jjjanssen said:
i could simply re-use the Fairphone Updater...
Click to expand...
Click to collapse
Make sure you allow it to reinstall the default recovery.
Donat.Callens said:
Make sure you allow it to reinstall the default recovery.
Click to expand...
Click to collapse
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Hi,
jjjanssen said:
how do I allow it? i didn't get the question you've got ("ROM may flash stock recovery on boot. Fix?").
i downloaded Cherry 1.6 again and chose Install, gave it SU (forever) access, it automatically restarted to the Android with the text “Installing system update…” (no progress bar), and after a few minutes it restarted and nothing is changed. After starting the Fairphone Updater again, it immediately gave the Install option again. Same after selecting the Storage Upgrader.
I also tried restoring from the recovery (default, never replaced), from sd and adb (1.6 does install, 1.3 doesn't, and 1.6 partition upgrader doesn't either, gets aborted)…
Click to expand...
Click to collapse
Non unified images have a different signature. The moment you use the partition upgrader it will change the accepted signature and will no longer allow older images. If all is as I expected your running image is still the parition upgrader image and it contains the tools to perform the last step of the re-partitioning (e.g. calling the script and performing a recovery with format).
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
_keesj said:
If you want to know what is going wrong with the zip install check the /cache/recovery direcotry. it will contain logs of the failing install.
As for a solutions I think you either need to run the script or flash your device using a 1.6 FUSE image.
Click to expand...
Click to collapse
I couldn't find any (log) files in /cache/recovery, but...
flashing the EBR1 from the FUSE binaries (FP1U) to my FP1 solved it! :victory:
thanks to _keesj, Rick (from Fairphone) and Christian (Fairphone forum)!
here is Rick's tutorial (with a few notes of my own):
You can only fix this by flashing your phone:
For GURU's only! (flashing with ADB). The alternative is to use the windows flasher tool.
1) Download the original image binaries from Fairphone's site (as a new user I, jjjanssen, can't post links yet).
(Download FP1U's zip: Fairphone_Cherry_1.6_FUSE_Image_2014-07-31.zip)
2) unzip the file
(I chose to unzip to location D:/FP1U.
after that i moved all content from the directory which contained EBR1, to D:/FP1U.)
3) enable usb debugging (on your phone: Settings, Developer options, turn USB debugging on)
4) push EBR1 on the phone: (Open (if you're using Windows) the Command Prompt)
adb push FP1U/EBR1 /mnt/sdcard/
(For instructions on how to use ADB search this site)
5) become root:
adb shell
(after that I also became super user (command su), but maybe that's not necessary; Rick didn't mention it. )
6) override the partition inforation:
dd if=/mnt/sdcard/EBR1 of=/dev/ebr1
7) reboot into recovery:
reboot recovery
8) choose to wipe data and cache
(after that, choose reboot)
Click to expand...
Click to collapse
Q&A for [ROM]TN.kitkat.4.4.2.HTC.evo.supersonic(aosp)viper.mod. a2sd_updated4/26/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
paultyler82 said:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
Click to expand...
Click to collapse
TWRP 2.8 is probably fine - the GApps packages are likely just too large and the flash is failing because your system partition is full.
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
paultyler82 said:
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
Click to expand...
Click to collapse
Have you tried downloading the latest core GApps through the EV Updater in the ROM?
(I assume this ROM has that)
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
paultyler82 said:
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
Click to expand...
Click to collapse
Can you use the File Manager in Recovery to navigate to /system/priv-app and look for the Google apps? Maybe try extracting them from the zip and manually copying them and setting permissions? There must be some explanation. I've never had a problem with GApps. Can you try fully wiping (including system) and flash the ROM and core GApps again, just to be sure?
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
paultyler82 said:
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
Click to expand...
Click to collapse
You are wiping system, right?
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
paultyler82 said:
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
Click to expand...
Click to collapse
That's because you have to mount system in TWRP to see the actual contents.
What is the exact GApps package you're flashing?
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
paultyler82 said:
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
Click to expand...
Click to collapse
In the Mount menu in TWRP, there is a list of partitions and check boxes next to them. If you're not seeing that, then perhaps you have a bad recovery flash.
A recovery log would tell us exactly what's happening when you flash.
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
paultyler82 said:
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
Click to expand...
Click to collapse
Well it's weird that the updater-scripts aren't doing it. Like I said, I've never had an issue with flashing the ROM and GApps in TWRP.
I thought it was a bit weird as well, gonna have a look at the recovery log.
Found it. Gapps update script tries to run /sbin/busybox mount /system. This line fails because busybox isn't there, this failure only shows up in the recovery log, the script messages do not indicate that /system has failed to mount and the update script proceeds to run, installing to null and indicating install was successful.
And then there were two.
I still check in to this forum every day. And as far as I can tell, Vin and Cap are the only reason we are able put our legendary device in our pocket every day and know our rom and recovery are bleeding edge. Lollipop would be huge for our small but dedicated community. But for now the gift of KitKat plus a number of Android 5.0 apps gives me what I like to call "LolliKat". This is the most reliable phone I have ever owned! I hope I get to use it for another four years.
htc supersonic TN 4.4.4 problems
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
cody85 said:
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
Click to expand...
Click to collapse
im going to install this today.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cryptickid715 said:
im going to install this today.
Click to expand...
Click to collapse
will there be a LP lol
How to I Install Xposed on Rooted Amazon Fire TV 2? (Guide Please)
Do I download XposedInstaller_3.0_alpha4.apk? and xposed-v78-sdk21-arm64.zip?
Please Help
Could I Use Flashfire?
You can't install xposed since there is no custom recovery
Tried with Flashfire where no custom recovery is needed ? what version of xposed should i try?
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
yeah I've had no luck, just have to wait I guess
ians325 said:
No Luck with Flashfire and xposed v78-sdk22-arm 64. Going to have to wait for a fix
Click to expand...
Click to collapse
Did you encounter boot loop or soft-brick when you attempted this?
z_thompsonpa said:
Did you encounter boot loop or soft-brick when you attempted this?
Click to expand...
Click to collapse
No
ians325 said:
No
Click to expand...
Click to collapse
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
I couldn't run this command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
[*]SELinux enforces more policies when Busybox is installed
[*]Setting SELinux to Permissive has no effect
EDIT: **Details in my next post**
z_thompsonpa said:
Thanks! You prompted me to give this a shot after confirming that it wouldn't do any serious damage. I found some things out in the process that explain why this isn't working as of yet.
The Xposed zip you mentioned requires the following Linux GNU tools (or equivalent):
cut
find
head
sed
I suspect this is why it is failing, because I was able to backup my system partition and restore my backed-up system partition through FlashFire. (more on this later)
Sooo.. I thought why not go all the way and try to install BusyBox first? ..since this would fix the missing commands
Much to my surprise the Busybox install actually worked and I had the whole suite of linux commands at my disposal!!!
Things went south pretty quick, though, when I realized that SELinux was blocking my ability to run the following command:
Code:
mount -o remount rw /system
So, this would prevent a further attempt at installing Xposed through Flashfire, because it would have to mount the system partition as rw in order to modify the files and add the Xposed framework.
I ended up restoring my system partition after this fiasco using Flashfire. It re-enabled my ability to remount /system as rw and SELinux has seemed to calm down in the logs.
In conclusion:
Xposed requires Busybox
SELinux enforces more policies when Busybox is installed
Setting SELinux to Permissive has no effect
Click to expand...
Click to collapse
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
fldash said:
Nice work, have you seen this tidbit on BusyBox Github for SELinux?
https://github.com/ukanth/afwall/wiki/BusyBox#difference-between-selinux-and-non-selinux-busybox
There's also some decent results on Google that may offer some clues... https://www.google.com/search?q=SELinux+mount+system+as+rw+android&ie=utf-8&oe=utf-8
Click to expand...
Click to collapse
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
keep up the good work
z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
fldash said:
How are you restoring your system partition? Using that diff patcher (for root) with a USB A-A cable?
Click to expand...
Click to collapse
I haven't had to break out the USB A-A cable yet... thankfully (except for root of course).
I used Flashfire to backup my /system partition as RAW backup before I started all of this experimentation. I have just been restoring back to this known good state using Flashfire after each time I corrupt the system partition.
I intended on trying this method, and if it didn't work to fall back to the method mentioned in the root thread. I checked the logs last night and Flashfire seems to be succeeding at this task, at least.
Right now, I am picking through the Xposed installer script source and using the Flashfire logs to debug why it is failing. It appears to be a permissions issue, but a lot of the stdout/stderr is suppressed so its hard to tell exactly where. When I get home today, I am going to try to modify the installer script to produce more output so I can debug the issue further. If I cant figure it out, I'll post my findings either way.
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
z_thompsonpa said:
Thanks for helping out. I jumped the gun on blaming SELinux. I'll go back and edit my previous post.
BusyBox, as far as I can tell works great!
(It will probably require more testing, but for the time being I am not having any issues.)
I figured out what was causing the problem with the inability to mount /system as rw. It was actually caused by attempting to flash Xposed, I believe. I tried it all again tonight and stopped this time after installing BusyBox and before flashing Xposed using Flashfire. I was still able to mount /system properly with functional GNU utils. I hadn't tested this before at this this stage.
I couldn't remount because of "orphaned inodes" after attempting to flash Xposed. Pretty sure this means its corrupting the partition, but yet its still mountable as read-only.
I restored my /system again to get everything back to normal and just installed BusyBox this time. So far so good...
I want to go back and try to flash Xposed again, and this time look in the logs folder. I think the addition of the BusyBox binaries are causing the installer script to error somewhere else during execution causing the partition corruption. Who knows.. there may be a workaround.
Click to expand...
Click to collapse
z_thompsonpa said:
I've fixed a few bugs in the flash script already, but it always errors on overwriting:
Code:
/system/lib/libart.so
It's throwing some error about read-only filesystem. (I'll post exact error later)
I've thrown in some checks to see if the /system mount is unmounting or something odd like that, but that's not it.
I've got a few guesses as to why, but I am not going to mention them until I have more solid evidence.
Any advice would help as well... I just wanted to post the update I promised.
Click to expand...
Click to collapse
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
fldash said:
I think we should go another method. Use the tools in the root thread to just create an image with Xposed/root and just do a DIFF.
Click to expand...
Click to collapse
I think so... I am pretty sure its a dead end. I also tested using adb to write the files and it failed on /system/lib/libart.so, as well. It's, I believe, because the object is loaded in memory?? don't quote me on that... but loading through preloader, I think, would avoid this limitation as ART is not running.
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
sconnyuk said:
So can anyone in here tell me if its possible to have xposed on fire tv 2 5.0.5 thats rooted and now has twrp recovery on ? I have tried to flash the xposed zip in recovery but when i reboot its stuck at amazon logo. Went back into recovery and flashed rbox's pre rooted 5.0.5 and booted normally. Id like to have (im sure many others would also) xposed and playstore, ive searched the forums but because rbox method is new there is no information on this subject now.
Click to expand...
Click to collapse
Use this method, I've slightly modified the text from another post & added it into a text file for you, this works a 100% but as usual I take no responsibility if you do any thing wrong & brick the Fire Tv2.
Enjoy & press that thanks button If this helped you
Thanks for this. I will try it shortly and report back if it works for me. I have stumbled upon another thread that the guys seem to be working on playstore issues, http://forum.xda-developers.com/fire-tv/help/q-guide-to-getting-google-play-rbox-t3310974
Made a guide here if anyone wants to install
http://forum.xda-developers.com/fire-tv/general/installing-xposed-fire-tv-2-guide-t3314142
I'm having a problem with es file explorer and root explorer. Last night my fire tv kept booting to home screen and rebooting, so I had to re-install 5.0.5.1 prerooted rom thru recovery. I reinstalled all my apps, and when trying to enable root explorer, I get the superuser request as usual, I grant and get the notification that it's been granted. Root explorer access is enabled for about 6 seconds before disabling with the message "Sorry, test failed. This feature cannot run on your device". Adaway works fine when asking for su permission. Only thing I did differently this time around with installation of the rom is I installed Es file explorer and tried to enable root explorer before doing the SU command from adb shell. I've since uninstalled and reinstalled ES file explorer and reacquiring SU permission but it does the same thing. I went and installed a much older version and it does the exact same thing. Anyone else come across this problem?
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
deanr1977 said:
The only thing I could suggest would be to remove the manager app es file explorer & reinstall the prerooted rom again? Then start fresh, Su, then after you get access then reinstall es? Only other thing I would say if that don't work is do a factory reset (but only do it from within TWRP Recovery!) Then reinstall the prerooted, block updates, grant Su & then see if that works for you? I use ES pro & Root Explorer & haven't had no problems at all.
Click to expand...
Click to collapse
Thanks for your reply. I'll do what another user suggested and use Total Commander instead as I have it installed and granted root access for it, and it does the same functions. I haven't had any issues with es file explorer on my ftv 2 at all, but another user reported the exact same problem in a different thread on this forum so I'm not alone.
Ok mate no worries, just a note I have both manager apps working on 2 sticks (1 rooted & 1 not, both updates blocked but on different firmware) & also on my prerooted AFTV2 so dunno what happened with yours & the other forum member?
Sent from my SM-G900F using Tapatalk
i have this same issue on 2 firebox's after a full conversion from os3, running rbox latest 5.2.x
both give the identical error, yet other apps are getting su control just fine?
any idea's? @rbox
I am having this problem on my first FTV1 I upgraded from PreRooted FireOS 3 to latest PreRooted FireOS 5. It is a fully rooted with fully unlocked bootloader FTV1. ES File Explorer is giving me this error when trying to turn on its Root Explorer option and all though Total Commander & Root Explorer are not giving me this error. They are not letting me copy files from a Root folder into regular storage. I can view them & choose them but it errors out when trying to copy over. I had to copy them thru TWRP.
I plan to do a Factory Reset thru TWRP & reinstall the latest PreRooted Rom again. But this time after doing the TWRP special build number update blocking tweak. I plan to run the SU command before installing any apps. Will see if that helps at all or not. If not I will post more detail info in case someone can help. This is the last bug I've encounter since doing the move from FireOS 3 to FireOS 5.
@d3adpool , @deanr1977 , @LittleBill21
Where you guys ever able to come up with an answer or fix for this issue ??
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Y314K said:
I am having this problem on my first FTV1
Click to expand...
Click to collapse
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
d3adpool said:
Unfortunately no, I'm sure reinstalling the rom via twrp would've fixed it but never did. That ftv has since stopped working.
Click to expand...
Click to collapse
Sorry to hear that, thanks for responding. I had already done a few reinstalling of the latest PreRooted Rom via TWRP without that fixing it. Will keep at it, though.
phresch said:
ESFE's root explorer has worked fine for me on multiple sticks, running various firmware versions (5.0.5, 5.2.1.0, pre-rooted 5.0.5_r1)
I didn't see mention of which device the OP was using -- but I'm going to go out on a limb and say FTV1 as well.
The same apk on pre-rooted 5.0.5 FTV1 box gives me that error message.
It seems like this just affects 1st-gen firetv boxes.
The question is whether it's linked/limited to pre-rooted bueller ROMs or just AFTV1's in general.
I didn't use ESFE until I was already on bueller-5.0.5_r2, I wonder if it works on stock 5.x.x rooted with kingroot?
Click to expand...
Click to collapse
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
---------- Post added at 01:07 AM ---------- Previous post was at 12:17 AM ----------
@RBox ; @AFTVnews.com
Decided to upgrade my first TowlRoot Rooted Bueller FTV1 on the last FireOS 3 PreRooted Rom (v51.1.6.3) to the latest FireOS 5 PreRooted Rom (v5.2.1.1_r1). I verified that I meet all the requirements. My bootloader was FULLY unlocked & I was on the latest CWM (v6.0.5.1.4a) with BootMenu (v1.0). I decided I wanted from the start the upgrade on as a clean as possible FTV1. So I uninstalled all programs except for SuperSU. Then I went into CWM & did a Factory Reset (Wipe Dalvik, Cache, Factory Reset) from within CWM & Reinstalled the last FireOS 3 PreRooted Rom (v51.1.6.3). All that was left after the Factory Reset was SuperSU.
Then I pushed over the TWRP bueller-twrp_3.0.0-7.img to the /SDCard & verified it's hash to make sure it was not a corrupt upload. Then I ran the command to switch to the TWRP recovery & everything installed perfectly.
I had ready a USB stick (Fat32) so I could install & md5 verify the FireOS 5 PreRooted Rom (v5.2.1.1_r1) on installation. Booted into TWRP & first did a wipe from within TWRP of Dalvik, Cache, Data & Internal Storage. Then installed the FireOS 5 PreRooted Rom (v5.2.1.1_r1) without any errors. Then I rebooted into system & it went thru it's paces. I did hit a road block when it came to check updates. This was because I was blocking the HTTPS update address from both my router & thru OpenDNS. I did a few re-flashes of the FireOS 5 PreRooted Rom (v5.2.1.1_r1) until I figure out that since this was the latest Rom version I should just let it talk to the update servers or do the PropBuild mod. So finally I got past the update nag. I first turned on ADB Debuging & I first did the SU command & chose to GRANT SuperUser rights. Then I did the update block command from SU. I installed my apps & the only bug I found after that was that ES File Explorer, even after it has been granted SuperUSer rights. It will error out "Sorry, test failed. This feature cannot run on your device". I thought this problem was just with ES file Explorer. But it seems to happen to a lesser degree on Total Commander & Root Explorer too. On those I can see the Root directories. But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
I tried flashing the bueller-fixsusdcard.zip thru TWRP on that install but nothing changed on the test response. Then I tried to do a full reinstall of the PreRooted Rom with the bueller-fixsusdcard.zip as a secondary .zip to flash during the installation. And same... Then I re-verified that I do have a unlocked bootloader. And that I am rooted. Passed on both. I was able to verified I am rooted by using an SDCard app while trying to see what size my MBCache.db file was. I was able to find it in /Data/Data/ without any problem.
So this is where I am at. I wonder if the bueller-fixsusdcard.zip file needs an update for FireOS 5 PreRooted Rom (v5.2.1.1_r1). Or should we try to install SuperSU as a secondary .zip file in TWRP or what can possibly be the answer to getting SU & Root working properly.
I would appreciate any ideas to try.
Y314K said:
This is definitely an FTV1 Bueller on FireOS 5 PreRooted Rom problem. And in my case it is tied to the "unable to access the /sdcard and other directories while in su mode" bug. But the .zip fix provided over @ the PreRooted Rom OP is not fixing the issue. Gonna post a more detail assessment of what I am encountering & what I've tried to fix the issue & failed so far in a bit.
Click to expand...
Click to collapse
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
But if I ever try to copy something over from /Root to /SDcard or to /USB it won't allow it. They will have some type of error that stops it. Or makes /SDCard disappear.
Then I notice the "Can't cd to /sdcard after using su? Install this TWRP flashable zip to fix it." post in the PreRooted Rom's OP. And decided to do the SU test of "[email protected]:/ # ls -al /sdcard" & sure enough. I always get the non SU response of:
"lrwxrwxrwx root root 1970-01-06 19:40 sdcard -> /storage/emulated/legacy"
Click to expand...
Click to collapse
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
phresch said:
...
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
I searched for a download of v2.05 and could only fine sources that I did not trust. Do you have a link to that version?
phresch said:
I had the su & /sdcard/ problem too.
I'm going to guess that things went something like this (they did for me):
1] installed twrp & pre-rooted bueller ROM
2] discovered that the included superSU had no GUI
3] replaced superSU with another version to access a GUI
4] discovered su/sdcard bug
5] found & flashed the zip fix
6] tried to su /sdcard/ & still doesn't work
Click to expand...
Click to collapse
I haven't tried to change or flash to a different SuperSU then the one that comes stock with the PreRooted Roms. Which is v2.46. Trying my best not to loose having a Fully unlocked bootloader. Are you flashing/testing the different versions of SuperSU thru TWRP or are you just flashing APK's just to try to see which one's GUI might still work ?
I notice the SU /SDCard bug only after trying out Total Commander & Root Explorer. Others said those where working fine for them. But for me it looked like they where gonna work fine. But as soon as any of those went to Root mode. I started to see bugs in those programs too. Although in those programs I can at least view Root files. And this last time Root Explorer is letting me copy files over from Root to /SDCard. Total Commander is still hanging when trying to copy files from Root to /SDCard. Like I said this last time I installed the /SDCard SU .zip fix right after I flashed the PreRooted Rom. So it did changed something. But from ADB I still get the same response from the SU List command.
phresch said:
I was able to remedy this part of the problem; at this point, I still can't access Root Explorer within ES File Explorer..
However, I am able to access /sdcard/ and other previously invisible folders, as well as using RootBrowser and RootExplorer apps.
I'm pretty sure the reason that the zip flash didn't work is because (assuming swapped versions of superSU) your installed superSU binaries are different from the ones the zip was intended to fix.
Click to expand...
Click to collapse
I have not swapped SuperSU from what comes with the PreRooted Rom. Trying other SuperSU versions might be something I do after getting some feedback from @rbox since I really do not want to accidentally loose my Fully unlocked bootloader.
phresch said:
You have a couple of options, both will give pretty close to the same end result:
First option:
1. re-flash your firmware ROM
2. flash the zip to fix the mount namespace problem
3. install a different SuperSU with a GUI
Click to expand...
Click to collapse
Are you doing the SuperSU changing thru APK flashing or thru TWRP zip flashing ? Do you know a link to where we can find most versions of SuperSU from v2.16 (used when we towelrooted) to v2.78 ? I see v2.79 is the latest version. Have you tried v2.79 on your FTV1 ? Is there a version of SuperSU we shouldn't go beyond ?
phresch said:
Second option:
Install a version of SuperSU that includes a 'disable mount namespace' toggle button, and toggle it. v2.05 works for me.
Hopefully that helps
Click to expand...
Click to collapse
Please post v2.05. I wonder if we can go down to v2.05 for that option. And then when things are working right go back to v2.46.
Either way ES File Explorer / Root Setting will not work for your right. Not matter what?
Hope I can get past this bug before updating my other 3 FTV1's.
Just ran into something else that is very odd. I've been using Amazon FireTV Utility App v0.66 to access ADB non-Root & Root Shell. Decided to switch to the stand-alone "adb-setup-1.4.3" to see if that would help with the SU commands. But I found that as soon as I give it the "adb shell su" command. Even if SuperSU has been granted full access on a fresh install of the PreRooted Rom on the FTV1. The "[email protected]:/ # _" line gives me a blinking _ & it won't let me input anything else. On the FTV1's screen it says "ADB Shell (2000)" was granted root access each time. But I can't get past that. Is like ADB never receives the granted access response. Then I have to CTRL+C to be able to input anything & exit. This happens whether I opened the CMD with & without Admin rights on my Windows 8.1 PC.
Gonna try downgrading to adb-setup-1.4.2 but I doubt it will make a difference. So the bugs are bunching up. Seems SuperSU is not being installed or allowed to work properly. Any help would be appreciated.
Forgot that on FireOS 5 you have to break the command.
First "adb shell" to get "[email protected]:/ $" & then just "su" to get to "[email protected]:/ #" without it freezing.
The /SDCard list still had the same response though.
"lrwxrwxrwx root root 1970-01-07 19:45 sdcard -> /storage/emulated/legacy"
Solution:
First let me start by Thanking @rbox , @AFTVnews.com , @zroice , @phresch for all their work & feedback.
Was finally able to test multiple options & found a reproducible solution to this problem. The key was in @zroice post about Holo Themer.
https://forum.xda-developers.com/fi...w-to-supersu-xposed-app-t3552590#post71703744
Basically you got to make sure you install or have installed the latest version of BusyBox & XPosed & HDXPosed Module. And to have activated Holo Themer from within XPosed so you can run the SuperSU APK that comes with the PreRooted Rom. SuperSU should ask you to update. Once you have done a "Normal" update like we did when we first rooted our FTV1's then that should fix the Root Option fail that ES File Explorer & other apps have had. I am guessing the problem comes when we uninstall or wipe our FTV1's during our FireOS 3 to FireOS 5 update. Some of us thought BusyBox & Xposed would not be as important to functionality on FireOS 5 as it was on FireOS 3.
Make sure you only activate Holo Themer on a per needed basis. Since it will make your FTV reboot randomly if you leave it on all the time.
And like always. As long as you installed TWRP correctly. You can always start anew with a wipe (NEVER WIPE SYSTEM) & install of the latest PreRooted ROM. I would also recommend having all the files you know you will need in a USB drive or SDCard in FTV2's case ready to go & in separate folders before you start flashing away. Makes things much easier.
If you forgot how to install BusyBox or XPosed you can always find how in the many guides over @ AFTVNews.com . For me even the old FireOS 3 guides & FTV2 guides help as a good refresher or visual confirmation.
LG V30 Verizon VS996-20k ROMHi!
This Rom is 100% Stock. Most recent TWRP should first be installed. Then you can install this Rom and have Oreo with working TWRP.
This zip is created from the original KDZ. It contains almost the complete 20k firmware, but the partition table rewriting part and recovery image is removed. I changed the system.img, so you do not have to reinstall TWRP (recovery-from-boot.p deleted) when ROM once booted. I also changed the partition size of system.img, so the vendorized people can install this too without having problems because of a too small system partition. This is a continuation of westwood24's idea and work, I've updated it to the newest fw version and edited / advanced it a bit. I followed his idea and made this for users who can not take OTA's because they have Custom Recovery / Root installed.
Thanks to @gimpy1 and @nnjimmy59 for testing this zip! And to @ChazzMatt for searching testers
Features
Stock build made from official KDZ
Stock Build.prop(slightly modified to add dts and locksreen weather and custom EQ)
Added latest 7.0.14 com.lge.equalizer apk for equalizer in sound settings
Unrooted
system.img modified to keep TWRP
System image size shrunk for being able to flash this on a smaller system partition, mainly caused by vendorizing
Removed dm-verity
Removed rctd (LG's root checker tool daemon)
Enabled opt-encrypt, it's your choice now if you want to encrypt your phone, it's no more forced. TWRP now is capable of decryption (both AOSP and stock) since a few versions
Added DTS enabler prop and all lockscreen weather prop to stock build.prop and custom EQ prop
Installation
What you need
Unlocked Bootloader [How to do]
Working TWRP installed (should be installed already, otherwise you wouldn't need this zip )[Link to newest unofficial TWRP]
When you need Root, Latest Magisk [Download]
LATEST ZIP
john-fawkes.com VS99620K.zip [Click to Download]
OLDER ZIPS
AFH ZIPS [Download]
How to install
When you are still on Nougat,
you should start fresh: Reboot to recovery using button combo or reboot app (needs root; btw, Magisk offers this possibility too: Menu -> Modules -> three dot menu top right - Reboot to recovery)
Then flash this TWRP.img via image flashing function in TWRP, reboot to recovery again (for fully working new recovery) and do a backup, then copy this backup to your PC.
Then initiate a factory reset. Wipe your system partition too in TWRP advanced wiping menu, copy the 20k firmware zip to your SD and install it. Reboot and enjoy
From Oreo:
For clean install: Factory reset and wipe system
You can also keep your data by simply dirty flashing the zip. *Be aware that problems may occur, maybe you need to do a factory reset to start fresh*
Flash the 20k zip, then Magisk zip when you need root, then reboot to System = you're DONE
P.S.: could be, that you first need to boot up your fresh install and set it up before you can flash magisk.
At the first time you boot to system, it can be TWRP says No OS installed. You can ignore it.
If TWRP asks if you want to install SU, hit no (in newest TWRP SU is disabled, and the option to install the TWRP app is disabled too.)
Rom Version
Android Version: 8.0 Oreo
Android security patch level: 2019-5-1
DONATION
Don´t forget to hit the thanks-button if you like this zip! :good:
If you want to help me with a donation please click here to help out [Please Click Here]
#reserved
I am on the twrp vs 996_20f. Working very well. Thx, seadersn, and all others involved for your fine work.
Deleted
Third time is a charm. Finally got it to load, I think
nice, i can finally add security patch date now, thx!
@seadersn, the rom works perfectly, flashed it from DOTOS with US998a firmware. It works perfectly. Awesome, many thanks for making this and other TWRP flashable zips available!
I need native tether and so had to restore, and there was a quirk. I mention it not to complain but out of curiosity and to make others aware. TWRP complained about no partitions being selected when attempting to directly restore either my stock US998 setup or DOTOS. Flashing westwood's US998b rom fixed matters. Can you explain what is happening? It seems like TWRP backups are specific to a model firmware.
cmrntnnr said:
@seadersn, the rom works perfectly, flashed it from DOTOS with US998a firmware. It works perfectly. Awesome, many thanks for making this and other TWRP flashable zips available!
I need native tether and so had to restore, and there was a quirk. I mention it not to complain but out of curiosity and to make others aware. TWRP complained about no partitions being selected when attempting to directly restore either my stock US998 setup or DOTOS. Flashing westwood's US998b rom fixed matters. Can you explain what is happening? It seems like TWRP backups are specific to a model firmware.
Click to expand...
Click to collapse
hmm, that would be news for me: what exactly did you do to restore? just selected backup, chosen partitions, restore? or was the backup folder not visible? and: do you have a log of this?
I'll try to be specific and detailed and hopefully not offer too much useless fluff. The phone is an open market us998 v30s. It has never been flashed with any other firmware. I keep a stock and DOTOS TWRP backups. Restoring between them or with any of the other aosp roms has always worked perfectly. I've wanted to see what additional features might be in the Verizon rom so I downloaded the your fresh zip, verified md5sum , factory reset on TWRPv6a and flashed. After satisfying my curiosity, I button danced back to TWRP to restore. This is where things got weird. The names of the backups matched the phone serial number rather than the dated backup name. TWRP gave the no partitions selected error when attempting to restore. At this point I thought maybe the backups got damaged and so popped in the sdcard with extra backups, . Those backups did not register their names properly and would not restore either. At this point I was resigned to setting up the phone again and just moved forward with a factory reset and flash of ww's 998b zip. I thought maybe there was something about the firmware change the affected the ability to restore so I rebooted TWRP. The correct names for the backups appeared and they would flash.
No logs, but I can repeat the process and gather information.
seadersn said:
hmm, that would be news for me: what exactly did you do to restore? just selected backup, chosen partitions, restore? or was the backup folder not visible? and: do you have a log of this?
Click to expand...
Click to collapse
cmrntnnr said:
I'll try to be specific and detailed and hopefully not offer too much useless fluff. The phone is an open market us998 v30s. It has never been flashed with any other firmware. I keep a stock and DOTOS TWRP backups. Restoring between them or with any of the other aosp roms has always worked perfectly. I've wanted to see what additional features might be in the Verizon rom so I downloaded the your fresh zip, verified md5sum , factory reset on TWRPv6a and flashed. After satisfying my curiosity, I button danced back to TWRP to restore. This is where things got weird. The names of the backups matched the phone serial number rather than the dated backup name. TWRP gave the no partitions selected error when attempting to restore. At this point I thought maybe the backups got damaged and so popped in the sdcard with extra backups, . Those backups did not register their names properly and would not restore either. At this point I was resigned to setting up the phone again and just moved forward with a factory reset and flash of ww's 998b zip. I thought maybe there was something about the firmware change the affected the ability to restore so I rebooted TWRP. The correct names for the backups appeared and they would flash.
No logs, but I can repeat the process and gather information.
Click to expand...
Click to collapse
twrp has different mechanisms for setting backup folders names, the serial number is one of them (and the default). it may be that something boot.img or other related has changed in this new firmware, so that old backups have another name than newer ones.
would be nice to have some additional testing. with the new firmware installed. means: install the new firmware zip, then do a cache format, reboot to recovery and then try a restore: does this change everything back to normal?
It all repeated just like the first time. Clearing the caches had no effect. What is the best way to send you the logs?
seadersn said:
twrp has different mechanisms for setting backup folders names, the serial number is one of them (and the default). it may be that something boot.img or other related has changed in this new firmware, so that old backups have another name than newer ones.
would be nice to have some additional testing. with the new firmware installed. means: install the new firmware zip, then do a cache format, reboot to recovery and then try a restore: does this change everything back to normal?
Click to expand...
Click to collapse
pastebin.com :good:
seadersn said:
pastebin.com :good:
Click to expand...
Click to collapse
Oh well, if you remember me, i flashed your h930h twrp on us998 based with boombox before. I backup the Rom using latest twrp too. Then after i lost connection as i already told you, i tried to restore this backup, it show the name of backup correctly but there is no option to select which partitions to restore, i mean it completely blank without anything to select. Just then i thought it was corrupted backup but there is now someone like me. I kdz back to us998e but somehow lost twrp and fastboot unable to flash it back ( showing FAILED (remote: Requested download size is more than max allowed ). But after a few kdz back to nougat and us998b with relock and unlock bootloader i can flash twrp again. So not sure what really happened
cmrntnnr said:
It all repeated just like the first time. Clearing the caches had no effect. What is the best way to send you the logs?
Click to expand...
Click to collapse
the log is in /cache/recovery/last_log, you can copy it to sdcard within twrp or adb pull it.
Mrxyzl said:
Oh well, if you remember me, i flashed your h930h twrp on us998 based with boombox before. I backup the Rom using latest twrp too. Then after i lost connection as i already told you, i tried to restore this backup, it show the name of backup correctly but there is no option to select which partitions to restore, i mean it completely blank without anything to select. Just then i thought it was corrupted backup but there is now someone like me. I kdz back to us998e but somehow lost twrp and fastboot unable to flash it back ( showing FAILED (remote: Requested download size is more than max allowed ). But after a few kdz back to nougat and us998b with relock and unlock bootloader i can flash twrp again. So not sure what really happened
Click to expand...
Click to collapse
boombox; this was some weeks ago, right :good: i hope, this could be solved finally, i think this really could be firmware & partition table related, which indeed can only be fixed by a kdz flash or with the zip used before flashing this one (or relevant other firmware zip).
Apologies for disappearing in the middle of an activity, work called. The problem is a bug in TWRP. One could make the argument that backups are model-firmware specific, but the reason is not exciting and hardly genuine. The installed firmware model is being pre-pended to the serial number of the backup folder name. If model firmware changes then backups made with another model firmware aren't visible. Renaming the backup folder is probably an interim work-around to enable TWRP to see the backups and carry out the restore. A longer-term solution would be to just not prepend anything. Let me know if you still want the recoverly logs and I'll put them onto pastebin.
Here is a snippet from the recovery log with the VS996:
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/VS996xxyyzzaa'
This is the same snippet after flashing back to US998D:
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Setting up '/data' as data/media emulated storage.
I:mount -o bind '/data/media' '/sdcard' process ended with RC=0
I:mount -o bind '/data/media/0' '/sdcard' process ended with RC=0
I:Backup folder set to '/data/media/0/TWRP/BACKUPS/LGUS998xxyyzzaa'
seadersn said:
pastebin.com :good:
Click to expand...
Click to collapse
cmrntnnr said:
Apologies for disappearing in the middle of an activity, work called. The problem is a bug in TWRP. One could make the argument that backups are model-firmware specific, but the reason is not exciting and hardly genuine. The installed firmware model is being pre-pended to the serial number of the backup folder name. If model firmware changes then backups made with another model firmware aren't visible. Renaming the backup folder is probably an interim work-around to enable TWRP to see the backups and carry out the restore. A longer-term solution would be to just not prepend anything. Let me know if you still want the recoverly logs and I'll put them onto pastebin.
Here is a snippet from the recovery log with the VS996:
...
Click to expand...
Click to collapse
aaaaaahhhh...! very nice finding :good: sounds and looks logical, and *is* logical: *and* makes sense: it appends the model number, which seems legit in terms of security for your phone while restoring. think about two different models which just aren't compatible to each other. what will happen if you restore a wrong firmware's or model's backup to another hardware? it won't boot. to prevent that, it changes the names of the backup folders. absolutely ok. unfortunately
so i just didn't fully get this problem and its meanings... sry for that: but thanks to you! now we know what happened / -s and can write a little tipp for a workaround in one of the first posts of recovery thread. as i said: i don't like the crossflashing stuff thank you
It absolutely makes sense as a safety feature. Perhaps it is best not to remove like I had suggested. Working around the folder naming convention for restores is a minor inconvenience compared to a brick, .
With regard to safety in TWRP, is there any way to increase the space between the radio buttons used for selection of partitions. I once had an unfortunate fat-finger event and a phone that would't boot.
Happy Armistice Day
seadersn said:
aaaaaahhhh...! very nice finding :good: sounds and looks logical, and *is* logical: *and* makes sense: it appends the model number, which seems legit in terms of security for your phone while restoring. think about two different models which just aren't compatible to each other. what will happen if you restore a wrong firmware's or model's backup to another hardware? it won't boot. to prevent that, it changes the names of the backup folders. absolutely ok. unfortunately
so i just didn't fully get this problem and its meanings... sry for that: but thanks to you! now we know what happened / -s and can write a little tipp for a workaround in one of the first posts of recovery thread. as i said: i don't like the crossflashing stuff thank you
Click to expand...
Click to collapse
I just want to be clear before flashing... this can be applied to an existing US998 -> VS996 phone, correct? I see "H930" in the first post, so I was concerned about that.
Also, the issue mentioned in the last few posts - I'm planning to dirty-flash from VS996 20d to this... that won't experience any issue, correct?
Will I need TWRP 3.2.3-6a or will my existing 3.2.3-5 work fine?
I prefer to be over prepared, instead of running into problems!
I am a Verizon customer with the Verizon vs996 phone I ordered new from them back in April or May of this year when I upgraded from the droid turbo. If you see the third or fourth post in this thread, I took a screen shot of the phone system. I am still currently on this rom but, am a "flashaholic", so in the next day or so will probably change it again (probably flash the twrp US998 rom or maybe pie 9).
In the first post, seadersn tells you how to install it on your phone from "oreo". That is the procedure I used. I am pretty sure that I used the most current version of twrp, the one that says something like 6a data IMG.
Edit: I just went into twrp and checked the version. It is the 6a data IMG version that I am on.
Sorry, I just reread your post. You went from the US998 to the VS996, not the other way around as I first thought. I would think it would still l work, but, again, I started out with the VS996.
schwinn8 said:
I just want to be clear before flashing... this can be applied to an existing US998 -> VS996 phone, correct? I see "H930" in the first post, so I was concerned about that.
Also, the issue mentioned in the last few posts - I'm planning to dirty-flash from VS996 20d to this... that won't experience any issue, correct?
Will I need TWRP 3.2.3-6a or will my existing 3.2.3-5 work fine?
I prefer to be over prepared, instead of running into problems!
Click to expand...
Click to collapse
changed the h930 to V30 sry, forgot to change this
but these issues were special ones, more related to twrp than to this firmware. firmware itself is fine, it's just all the images of the kdz converted to twrp flashable zip :good: when you experience problems, these problems will be there too when flashing the kdz
your recovery version is fine, beside the fact that it has wrong modem partition handling. updating is always the best :good: i would suggest to install -6a.
gimpy1 said:
I am a Verizon customer with the Verizon vs996 phone I ordered new from them back in April or May of this year when I upgraded from the droid turbo. If you see the third or fourth post in this thread, I took a screen shot of the phone system. I am still currently on this rom but, am a "flashaholic", so in the next day or so will probably change it again (probably flash the twrp US998 rom or maybe pie 9).
In the first post, seadersn tells you how to install it on your phone from "oreo". That is the procedure I used. I am pretty sure that I used the most current version of twrp, the one that says something like 6a data IMG.
Edit: I just went into twrp and checked the version. It is the 6a data IMG version that I am on.
Sorry, I just reread your post. You went from the US998 to the VS996, not the other way around as I first thought. I would think it would still l work, but, again, I started out with the VS996.
Click to expand...
Click to collapse
i don't know anything about all these conversions, can therefore not give any tipps if this will work or not. for info about that @schwinn8 has to search or ask on other places