Hey people,
I am trying to make the Android Kitchen working with our device.
These roms are only for testers now!
Install:
1. Copy to SD
2. Go in RecoveryMode(TWRP)
3. Delete Data and Cache
4. Flash the zip
Download:
(It won't install)AndroidKitchen_Rom_Alpha1.zip
I have problems with flashing in TWRP now. Can somebody help?
This phone doesn't have the thing called boot partition but instead has a kernel partition which combines both kernel and recovery of the phone.
The partition address is mmcblk0p15.
There is no point if you define it there as there are repacking scripts present yet for this kernel.
First post edited! This one in theory work. I am gonna test it myself now!
Can't install in twrp just got a error
You are expected to tell what error you get.
Why our device has big problems abut developing ?? is there some new security ways of samsung to not develop custom roms ?
emosis said:
Why our device has big problems abut developing ?? is there some new security ways of samsung to not develop custom roms ?
Click to expand...
Click to collapse
Our device has a other way of how the rom's are made.
Verstuurd van mijn GT-I9070
varun.chitre15 said:
You are expected to tell what error you get.
Click to expand...
Click to collapse
Just Error thats the weird part if there was a specefic error I would tell you imidiatly
Verstuurd van mijn GT-I9070
Found something, I think it is the updater file. Edited something and now building the rom and testing. Hoping the best!
New problem. Problem with the can't install fixed. But now it won't boot. And twrp says no os installed... Tyring to take a look at the logcat, can't connect to logcat. Weird!
Now trying with a other updater-script
Try to use updater script from jetmod. That simply copy system foldet to /system partition, and then try to flash cocore into it.
skubi07 said:
Try to use updater script from jetmod. That simply copy system foldet to /system partition, and then try to flash cocore into it.
Click to expand...
Click to collapse
Now its installed right. But now it has to boot. Going to try that tommorow or something
Verstuurd van mijn GT-I9070
Related
OK . We all i believe find it chaotic to organize in forums now. So this is a thread just for ideas and problem with cwm or twrp on our device.
All that i have found now is that recovery.img is somehow backed with boot.img. So i have to ask if there is any developer that can look inside this.
Help appreciated. We (developers) have already compiled TWRP and CWM ( me via ubuntu and clockworkmod recovery builder) and none of them is booting.
You might want to look at xperia p boot.img??? Same processor u8500 same screen size. I'm a noob. Just said what I felt. Coming from xperia device where our recoveries are always packed inside boot.img
In ramdisk . /sbin/recovery is where our recovery binary is present.
#pitchblack5691#
thanks for help ! i will definetely looo for it
Might be useful
http://forum.xda-developers.com/showthread.php?t=2020895
http://forum.xda-developers.com/showthread.php?t=1903017
#pitchblack5691#
also coming from xperia forum and for My xperia U and have also novathor u8500 and i have asked dev to explain mothod used in XU for port this method to GIII mini but no reply from him now in XU the recovery are in tar and flashable to phone without odin or another flash only by ADB + run me script in commande window inside recovery tar we have unziped recovery ( icone ....) and some files relative to phone ( fstab ..... )
How is it going? Did everyone stop developing or are you guys just moving in silence trying to figure things out?
Sent thru time and space from my s3mini.
silently moving
Shapeshift said:
silently moving
Click to expand...
Click to collapse
Good to know! Give us a shout if we can help somehow.
currently working on cwm 6. dont know why i cant boot
Perhaps need to no only make recovery but also kernel ?
If this 2 filz run together
Sent from my GT-I8190 using xda app-developers app
From what I understand, You just need to write a piece of code in the ramdisk init files to execute the recovery during boot. No need to modify the kernel.
#pitchblack5691#
If any one is interested i got a dumped ram disk also a got it rebuild-ed,
and yes the recovery scripts are there plus the pngs etc.
I also believe that the device has 2 recovery's, they are the same one just acts as a backup.
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
spawk said:
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
Click to expand...
Click to collapse
They had the internet in 1969?
Take your time. We have root and what roms we have are stable.
Sent from Spaceball One.
Hahaha!
Sent thru time and space from my s3mini.
xd the error is not from me haha i have corect date and time
is new technologie hahahaha retoure backwards in android
and if you see here you can read need new builded kernel to make CWM just read thread 2# and 3# http://forum.xda-developers.com/showthread.php?t=1771347
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
spawk said:
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
Click to expand...
Click to collapse
I sent info about device to that developer. That app is now supporting our golden for full backup incl boot & recovery.img with .zip from here. Only problem is we dont have a working custom recovery to flash that .zip with :/
as Faria wrote above should change the recovery that is in the kernel and the same meter and the same rom in it and in the kernel for which you go just tell me that the two are complementary if a move (size , addition, retirees), the other answers are more about the two is that one feature that the other is that we will say to his control as .
now change I believe that both will adjust in any case theoretically
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
are you using any sound/volume mods? or any other flashable mods? i think awesomebeats dies this, at least others have complained about it wiping the dalvik after every reboot.
cdon2109 said:
Everytime I turned on my phone or if it rebooted, I always get:
Android is upgrading
-----------------------------
Starting Apps.
I am on stock ROM, TWRP recovery, Faux kernel. I think this happens after I wiped dalvik/cache in the recovery. Any idea how to stop it? It's nothing very major though as it only takes a few seconds.
Click to expand...
Click to collapse
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
CMNein said:
That's normal if you've wiped the Dalvik cache, and no you can't stop it.
Edit: so wait, this is happening even when you reboot normally after not wiping any caches or flashing a kernel?
Click to expand...
Click to collapse
yes.. and it updates apps after delvic wipe.. but in my case whenever i restart I see the "Android is upgrading" box for about 3-5 sec.. no update app progress bar.. and when I wipe delvic this upgrading apps takes like a min or so with my 150+ apps.. but this "Android is upgrading" dialogue box appears only for 3-5 sec..
I am using PA 3.99 with franco kernel.. once booted every thing inside is running smoothly and no fc's...
Same here. No odex files in app folder. No wipe, no cache clearing. Plain reboot. And Android is upgrading message on every boot. (Starting apps)
No optimizing apps message though.
Sent from my Nexus 4
Wouldn't it be related to "zipalign apk on each boot" parameter ? or an other init script put in place by a dirty flash (no /system or /data format) or a kernel... ?
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
anandbibek said:
Seems likely. Could you explain in detail kindly?
Sent from my Nexus 4
Click to expand...
Click to collapse
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
benbugohit said:
Have a look in the files located in this folder for example (maybe there's another location for init scripts) :
- /system/etc/init.d/
- /system/addon.d/
and open each one, to see what are the tasks contained
Click to expand...
Click to collapse
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
anandbibek said:
Removed the scripts present in init.d folder and then booted with empty folder, but message still present.
Checked the addon.d folder, but those scripts are only for backing up gapps etc.
Not sure where else to try. Please advise.
Thanks.
Click to expand...
Click to collapse
Did you try to re-flash your (stock) ROM (and the kernel after 2 reboots) with wiping only /cache and dalvik-cache ? with latest 2.6.2.0 TWRP ?
happens to me too
Sent from my Nexus 4
I've seen people get this with stuff like V6 Supercharger by Zepplinrox and similar scripts.
Edit : @Dungeon47: thanks for this information that users can't provide...
HeyyMyNameIs said:
happens to me too
Sent from my Nexus 4
Click to expand...
Click to collapse
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
benbugohit said:
Edit : @Dungeon47: thanks for this information that users can't provide...
A pity that so much details are missing : what did you do before it happened ?
What's your set up ? rom, kernel ? after having update your rom ? kernel ? apps ? which versions ?
Did you try to revert to a clean install after having backup up your apps+datas ?
Click to expand...
Click to collapse
im sorry, just wanted the OP to know that he is not the only one with this "problem" by the way im rooted stock rom and kernel, some apps start up when i boot like nova launcher, lucky patcher sidebar and udn. But i am not looking for a fix for this as this does not take that long and i just said that to let the OP know that he is not alone with this "problem"
Sent from my Nexus 4
Ok guys,
Here's the solution. Don't flame me for talking about unholy stuffs. I'm posting this only because it is the cause of the problem.
If you are using LP or such tools to create .odex files of some app in /app folder. It won't cause any boot msg.
But after you dirty flash a ROM, that .odex files somehow gets backdated and causes the UPGRADING msg.
Fix is, delete the odex files, and re create them if needed. Once after every dirty flash.
Sent from my Nexus 4
I have found fix for this error, it is mainly due to odex files which are created by lucky patcher so deleting these files using lucky patcher itself will surely remove this error with 50 percent success rate. Here's the fix; open lucky patcher, there in lower left section you can see Toolbox, click that Toolbox then select 4th last option i.e Remove all odex files.Thats it android will reboot on itself and vola no android is upgrading. .
Check out attachment for help.
:good:Hits Thanks If I helped u:good:
HI! I'm building Android 4.4 but when I try to flash the ROM via TWRP, I get the following error:
minzip: Extracted 1226 file(s)
ApplyParsedPerms: removexattr of /system/addon.d/50-hosts.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/external_sd/box/i9305/omni-4.4-20131107-i9305-HOMEMADE.zip'
Error flashing zip '/external_sd/box/i9305/omni-4.4-20131107-i9305-HOMEMADE.zip'
Any advice on what is needed to fix this fault is appreciated!
Is the recovery.img produced during ROM build flashable? It is 2MB smaller than the TWRP recovery image.
Hey, so I went through this yesterday (see the Q & A section) and while I didn't resolve it completely, I know that it's because of selinux, and you need a newer version of TWRP. Right now in the Omni 4.4 manifest it actually has the AOSP recovery so you'll wanna change that to Omni 's TWRP on a local manifest. Beyond that it depends on your BoardConfig.mk whether your recovery is flash able, if you configured it ok then yes!
Check the links Entropy512 posted in this thread for more on TWRP configuration: http://forum.xda-developers.com/showthread.php?t=2499514
In particular make sure you have a proper fstab in v1 format (see my last post in that thread for more details as well). My recovery built after I fixed the twrp.fstab at least looks and acts like a proper recovery, but haven't done anything with it yet for lack of time.
The reason for that message can be in the kernel configuration.
If those options are not set, this will cause this message:
Code:
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
regards Uwe
I used for fix that ROM Manager app from Play Store and update to the latest CWM recovery. DO NOT USE TWRP!!! Just update that.
u.k-f said:
The reason for that message can be in the kernel configuration.
If those options are not set, this will cause this message:
Code:
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT2_FS_POSIX_ACL=y
CONFIG_EXT2_FS_SECURITY=y
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
regards Uwe
Click to expand...
Click to collapse
Thanks.. I have all those set for Ext4 (the only FS used) and still no luck ....
mcampbellsmith said:
Thanks.. I have all those set for Ext4 (the only FS used) and still no luck ....
Click to expand...
Click to collapse
Did you enable SELINUX in the kernel used for recovery?
The xattributes to be written are SELINUX Attributes...
Regards Uwe
u.k-f said:
Did you enable SELINUX in the kernel used for recovery?
The xattributes to be written are SELINUX Attributes...
Regards Uwe
Click to expand...
Click to collapse
Thanks for your help everyone.
Recompiled TWRP and it works.
CWM also works when updated.
Cheers!
It is weird. I have compiled TWRP in the omni tree. The kernel config does contain the selinux settings:
if using Ext3:
Code:
CONFIG_EXT3_FS=y
CONFIG_EXT3_FS_XATTR=y
CONFIG_EXT3_FS_POSIX_ACL=y
CONFIG_EXT3_FS_SECURITY=y
if using Ext4:
Code:
CONFIG_EXT4_FS=y
CONFIG_EXT4_FS_XATTR=y
CONFIG_EXT4_FS_POSIX_ACL=y
CONFIG_EXT4_FS_SECURITY=y
But i am still getting the set_metadata_recursive stuff. Do i have to include HAVE_SELINUX ? I thought that was for android versions <4.3
I did a clean / clobber before building, but i added also a kernel command to make selinux permissive
Do i have to cherrypick something to make it work?
EDIT:
Hmm somehow the new recovery image is not flashed ?
With the change from Android 4.2 to Android 4.3 I needed to enable SELINUX in the Kernel-Config.
Did you do this?
And, by the way, you do not need to install your new recovery, you can start ist from bootloader with
Code:
fastboot boot recovery.img
without installing it any time you build a new version
regards uwe
u.k-f said:
With the change from Android 4.2 to Android 4.3 I needed to enable SELINUX in the Kernel-Config.
Did you do this?
And, by the way, you do not need to install your new recovery, you can start ist from bootloader with
Code:
fastboot boot recovery.img
without installing it any time you build a new version
regards uwe
Click to expand...
Click to collapse
I fixed the problem. It was because of the fact that the image was bigger then the partition size. Using another kernel compression solved it.
Sent from my Xperia T using Tapatalk
mcampbellsmith said:
Thanks for your help everyone.
Recompiled TWRP and it works.
CWM also works when updated.
Cheers!
Click to expand...
Click to collapse
Can you explain what you changed in the CWM tree to successfully flash 4.4?
scanno said:
I fixed the problem. It was because of the fact that the image was bigger then the partition size. Using another kernel compression solved it.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
hi
please explain all fix do, others dev have solution and clue...
we have to leave answer for duture and actual dev
thank you very much
lordtillt said:
Can you explain what you changed in the CWM tree to successfully flash 4.4?
Click to expand...
Click to collapse
Nothing.
The latest version of CWM that was available from the website was quite old. Recompiling it with latest sources worked fine.
desalesouche said:
hi
please explain all fix do, others dev have solution and clue...
we have to leave answer for duture and actual dev
thank you very much
Click to expand...
Click to collapse
My changes were for the TF300T. The commits are on gerrit. You can see the TWRP configuration and the changes needed in the kernel.
Sent from my Xperia T using Tapatalk
scanno said:
My changes were for the TF300T. The commits are on gerrit. You can see the TWRP configuration and the changes needed in the kernel.
Sent from my Xperia T using Tapatalk
Click to expand...
Click to collapse
can you send a link please?...thank you...
In short, if you want to flash KitKat Android 4.4, you'll have to upgrade to a version of CWM greater than v6.0.4.5. Or, use an alternate bootloader.
Try out another recovery.
I got this pb with phil touch, then I try it on TWRP and the ROM is now installed correctly : )
Disclaimer: I am NOT responsible for any damage you do to your device.
Slate 7 Plus 4200 owners, I have a version of this ROM for you guys as well. You can find it here.
This is JB-SlateROM, a customized and debloated ROM for the HP Slate 7! This was designed for the 2800 but might work on the 4600 as I haven't tested since I don't have a Slate 7.
EDIT: Confirmed working on the 2800!
EDIT: NOT working of the 4600/4601. I'll recook the ROM for you guys when time permits.
Before you can install this ROM you need CWM on your device. Go here to get a build of ClockWorkMod v6.0.3.3.
FEATURES
Bloatware removed! :victory:
If the bloatware is still there, go to Settings, then Apps. Find the app and hit Disable Updates. That will delete the bloatware permanently. If it's still there after that I did not remove it. Tell me what you want removed in that case.
Original launcher has been hidden (saved as an .apk-hide file) in favor of Apex Launcher.
ES File Explorer added.
GravityBox Xposed module added.
App Settings Xposed module added.
Quick Boot added.
Xposed Installer added. (Not activated by default! Go into the installer, hit Framework, then hit Install/Update, then hit Soft Reboot or Reboot!)
Download
Changelog
v2.0 - Coming Soon Complete redo. More bloatware removed and tweaked a few more things... (AKA the "If an android crashes and nobody is around to logcat, can it still be fixed?" Update)
v1.1 - Removed references to ePrint.kpa (UNRELEASED)
v1.0 - Initial release.
Sent from my Sero 7 Pro using Tapatalk
Hi, I just tried to install this ROM (on Slate 7 4601), but in CWM, I get the 'Status 7' error.
before this, I see the line 'set_perm: some changes failed'. If that helps, I don't know?
Thanks.
callidus_ex_de_latebros said:
Hi, I just tried to install this ROM (on Slate 7 4601), but in CWM, I get the 'Status 7' error.
before this, I see the line 'set_perm: some changes failed'. If that helps, I don't know?
Thanks.
Click to expand...
Click to collapse
The ROM must not be compatible with the 460x as I know it works fine with the 280x. I'll do a port of this with the 460x ROM and add it to the OP by next weekend at worst.
Hi. Same Error 7 here on my Slate 7 2800. Formatting all partitions before install doesn't change anything ..
dderek said:
Hi. Same Error 7 here on my Slate 7 2800. Formatting all partitions before install doesn't change anything ..
Click to expand...
Click to collapse
Which country is your Slate from? Status 7 means incompatible with device.
If you're really adventurous do a Nandroid then toggle signature verification then flash the ROM. Theoretically everything will work, but Nandroid just in case
Sent from my Sero 7 Pro using Tapatalk
Thank you for your reply.
My Slate is from Polish distribution channel. It's P/N is E0H92AA.
Signature verification is by default switched off in CWM. Looking at the detailed installation log I can see these lines before the Error 7 is reported:
minizip: Extracted file "/system/xbin/iwpriv"
minizip: Extracted file "/system/xbin/iwspy"
minizip: Extracted file "/system/xbin/su"
set_perm: chown of /system/vendor/app/ePrint.kpa to 0 0 failed: No such file or directory
set_perm: chown of /system/vendor/app/ePrint.kpa to 644 failed: No such file or directory
script aborted: set_perm: some changes failed
E:Error in /external_sd/_/JB-SlateROM.zip
(Status 7)
Installation aborted.
EDIT: adding original file /system/vendor/app/ePrint.kpa to your ROM allowed to install it within CWM 6.0.3.3.
But after reboot the device is now stuck at the HP logo
EDIT2: Suspecting the device incompatibility I have tested that the original firmware (taken from http://forum.xda-developers.com/showthread.php?t=2608181 ) runs without problems
dderek said:
Thank you for your reply.
My Slate is from Polish distribution channel. It's P/N is E0H92AA.
Signature verification is by default switched off in CWM. Looking at the detailed installation log I can see these lines before the Error 7 is reported:
minizip: Extracted file "/system/xbin/iwpriv"
minizip: Extracted file "/system/xbin/iwspy"
minizip: Extracted file "/system/xbin/su"
set_perm: chown of /system/vendor/app/ePrint.kpa to 0 0 failed: No such file or directory
set_perm: chown of /system/vendor/app/ePrint.kpa to 644 failed: No such file or directory
script aborted: set_perm: some changes failed
E:Error in /external_sd/_/JB-SlateROM.zip
(Status 7)
Installation aborted.
EDIT: adding original file /system/vendor/app/ePrint.kpa to your ROM allowed to install it within CWM 6.0.3.3.
But after reboot the device is now stuck at the HP logo
EDIT2: Suspecting the device incompatibility I have tested that the original firmware (taken from http://forum.xda-developers.com/showthread.php?t=2608181 ) runs without problems
Click to expand...
Click to collapse
It's because I removed bloatware and forgot to remove the references in the updater-script. Sorry about that, I'm VERY new to developing.
You should expect a updated ROM very soon. Probably tomorrow worst-case scenario.
Sent from my Sero 7 Pro using Tapatalk
Mmmh I tried to install your ROM but I got the same Error 7.
Then I proceeded to remove any reference into META-INF subfolders about ePrint.apk package and finally CWM installed it without hassle.
Nonetheless I got a stuck boot logo. I left it 5 minutes, but had no success, now I'm going back to my rooted 1.05.14 stock firmware.
I noticed a pair of things that may be useful to report:
- In /recovery folder there's a patch for the recovery. It may be useful to inhibit such patch, I added an exit 0 in /recovery/etc/install-recovery.sh just to be safe
- When you use CWM to do a factory reset (wipe data/factory reset), it doesn't wipe /system partition. You have to manually go in backup/restore -> format /system. Then you should wipe cache, maybe dalvik cache, and finally install the zip package.
blackshard83 said:
Mmmh I tried to install your ROM but I got the same Error 7.
Then I proceeded to remove any reference into META-INF subfolders about ePrint.apk package and finally CWM installed it without hassle.
Nonetheless I got a stuck boot logo. I left it 5 minutes, but had no success, now I'm going back to my rooted 1.05.14 stock firmware.
I noticed a pair of things that may be useful to report:
- In /recovery folder there's a patch for the recovery. It may be useful to inhibit such patch, I added an exit 0 in /recovery/etc/install-recovery.sh just to be safe
- When you use CWM to do a factory reset (wipe data/factory reset), it doesn't wipe /system partition. You have to manually go in backup/restore -> format /system. Then you should wipe cache, maybe dalvik cache, and finally install the zip package.
Click to expand...
Click to collapse
Is this a bootloop or stuck at bootloader?
Sent from my Sero 7 Pro using Tapatalk
how does this rom work on the 2801. Has it been updated?
Thx, vIgGeN!
jerbear294 said:
Is this a bootloop or stuck at bootloader?
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
jerbear294 said:
Is this a bootloop or stuck at bootloader?
Click to expand...
Click to collapse
Just stuck at bootloader. I see the HP logo (still image, not the boot animation) and then nothing happens. I have to push the power button for a long time to power off the device.
I'm redoing the ROM completely and hoping it works. Perhaps my Mediafire upload corrupted?
Sent from my Sero 7 Pro using Tapatalk
jerbear294 said:
I'm redoing the ROM completely and hoping it works. Perhaps my Mediafire upload corrupted?
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
Don't think so, the .zip file unpacked correctly.
Sorry for the hiatus- other devices were taking my attention.
I just need to add some things into the redone ROM then I'll upload it. It could take a couple days though, I'm busy porting PAC-ROM to my tablet. Once that's done I'll continue work on this.
Sent from my Sero 7 Pro using Tapatalk
jerbear294 said:
Sorry for the hiatus- other devices were taking my attention.
I just need to add some things into the redone ROM then I'll upload it. It could take a couple days though, I'm busy porting PAC-ROM to my tablet. Once that's done I'll continue work on this.
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
any idea on an update for this Rom?
keepaf1 said:
any idea on an update for this Rom?
Click to expand...
Click to collapse
Yep. I found the source of the error, and I am fixing it now.
Sent from my Sero 7 Pro using Tapatalk
Hellow, i want to request you to enable usb otg. There are many members on hp forums who are trying to enable it. Otg troubleshooter does not work on stock rom
jerbear294 said:
Yep. I found the source of the error, and I am fixing it now.
Sent from my Sero 7 Pro using Tapatalk
Click to expand...
Click to collapse
Looking forward to the new release. just got a slate 7 i repaired and cant wait to flash. thanks for your work on this!!!:good:
If you have the time please
Sorry to be a pain, but any idea when you will have the time to fix this. Its my grandsons tab and I would like to fix it for him. Thanks. I know I could probably learn how to do it myself but the old brain cells are a bit thick these days.
hi, i followed this guide ( https://forum.xda-developers.com/android/software-hacking/guide-port-nougat-roms-snapdragon-t3552897 ) to port validus rom from redmi note 4 (same chipset) but everytime i get error 7 in twrp:
...
patching system image unconditionally...
E1001: failed to update system image.
updater process ended with ERROR: 7
anyone can help me?
the rom is uploading to google drive. tomorrow i put link in this thread
rom link: https://drive.google.com/open?id=0ByWXQMKmKF0-NWplWlM5Z04xQzQ
Edit the updater-script by removing everything before the "ui_print" line.
wang1chung said:
Edit the updater-script by removing everything before the "ui_print" line.
Click to expand...
Click to collapse
i do it but same error, i uploaded my update scritp file below
ExperienceTesla said:
i do it but same error, i uploaded my update scritp file below
Click to expand...
Click to collapse
the script looks good to me, shouldn't be causing you issues as far as I can tell (but what do I know, lol). Are you using the latest version of TWRP?
Anyone try to flash this rom??
wang1chung said:
the script looks good to me, shouldn't be causing you issues as far as I can tell (but what do I know, lol). Are you using the latest version of TWRP?
Click to expand...
Click to collapse
yes: 3.1.0.0. i think the error is the system.new.dat. there is a way to keep system folder in rom zip instead of system.new.dat? like kitkat roms
ExperienceTesla said:
yes: 3.1.0.0. i think the error is the system.new.dat. there is a way to keep system folder in rom zip instead of system.new.dat? like kitkat roms
Click to expand...
Click to collapse
i know there is a command for the updater-script called package_extract_dir("system", "/system"); which should work if you extract system.new.dat to the /system directory of your rom zip, but there's a lot (like 100 lines) of other symlink and metadata commands that I don't understand.
Have you had any luck?
Edit.....think I found something. Try using the first 5 lines of transfer list file from the stock Rom. Maybe more, I'm not sure.
Edit 2: after looking at a breakdown of how the transfer list works, I think this is dangerous.
Edit 3: the "port rom" you uploaded is a lollipop 5.x android Rom, so I'm not sure what you're using as a "base Rom" when porting this as I thought the zf3 only came with 6.x and 7.x?
wang1chung said:
i know there is a command for the updater-script called package_extract_dir("system", "/system"); which should work if you extract system.new.dat to the /system directory of your rom zip, but there's a lot (like 100 lines) of other symlink and metadata commands that I don't understand.
Have you had any luck?
Edit.....think I found something. Try using the first 5 lines of transfer list file from the stock Rom. Maybe more, I'm not sure.
Edit 2: after looking at a breakdown of how the transfer list works, I think this is dangerous.
Edit 3: the "port rom" you uploaded is a lollipop 5.x android Rom, so I'm not sure what you're using as a "base Rom" when porting this as I thought the zf3 only came with 6.x and 7.x?
Click to expand...
Click to collapse
the port rom is Validus-mido-7.1.2.STABLE.15.1-UNOFFICIAL-20171022-2227 from xiaomi redmi note 4 and the stock rom is lineage os. i tried other tutorial with no success. tommorrow i try to port another rom :good:
@ExperiencedTesla
It's weird, because when I extracted the system.new.dat of the stock 7.1 Rom, it showed it was a android 7.1 Rom....but when I extracted your validus rom, it showed 5.0?