Flashing Issues | Will not pass Android Logo
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
RockyCaballero said:
I have have the T-Mobile version of the S5 and it is currently running XtreStolite rom on lollipop. I have been messing around with the SystemUI and framework apks. (getting them to work every now and again)
However, I was searching around and tried to push the apk files through adb at first, instead of a complete reflash with the modified apks inside, with no luck. Adb says that the files were successfully sent but are not there and no changes are made. I then stumbled across a method using a flashable zip that is supposed to just replace the files I need.
I n doing so, after reboot the phone just sits at the Android Logo on powerup, them I have to reflash or restore my recovery. My question is this: Is there a method that allows me to setup a flashable zip with the system/priv-app/systemui/systemui.apk so that it will only replace those files and not the whole system folder itself?
There may be some more information that I am leaving out, sorry I have not slept all night and I am about to go to class.
Thanks in advance, if I have posted incorrectly, please advise.
Click to expand...
Click to collapse
Here download this https://www.androidfilehost.com/?fid=24052804347782219
Extract and Add whatever directories/folders you want inside the system folder and flash. The script just extracts the system folder as a whole so as long as you make the correct folders, file names, directories etc it'll flash everything to the right spot.
Delete the jar file out of system/framework/ tho since it's a 5.1.1 jar file I did
Much obliged sir, worked perfectly. I'm sure it was the coding. [emoji2]
Related
today i deodexed my /system/app/ and /system/framework/ successfully.
used root explorer to copy and paste the framework directory in place.
before i could do the same for the app directory - multiple errors resulting in a reboot to a bootloop
i have tried for a few hours now to create a update.zip with the odexed files to return to a working environment.. what i get on the screen is.. installing update.zip.. installation aborted... no errors or anything. (this is with the stock samsung recovery)
i do have a copy of the the original odexed files and the deodexed files.
clockwork recovery isnt supported for this phone yet so i can't go that route
i can't adb push the files because i need to grant adb superuser permissions from the phone.
so basically i have a nice fancy brick with a rotating droid animation on the screen.
the phone is a Samsung Gravity Smart SGH-T589
any suggestions?
btw - the firmware hasn't been released yet for this phone or i'd attempt a fix with odin.
Last I checked you may have to go a custom route to install a custom recovery. That step is always the weirdest, and it's never been the same for any of my phones. Especially if the phone isn't going to start up the conventional way...
Here are two places with more information that I found, maybe you didn't.
http://androidforums.com/samsung-gravity-smart/395877-yay-gravity-smart-forum.html
http://forum.xda-developers.com/showthread.php?p=17354030
hey thanks guy
i actually started both those threads a while back =)
i'm making progress with my update.zip
got it to install finally but still bootlooping
Hi everyone,
I want to eventually create an edited ROM for an Android tablet. (Very simple stuff, really. Removing apks, adding build.prop mods)
I have a working update.zip file, which re-installs the image on the tablet, through stock recovery and the install from sdcard option.
But once I unzip it,
and then zip and even re-sign it (with the tool I found by searching the forum),
the recovery says 'installation aborted', when it is verifying the package.
1. How can I avoid this from happening? I get it that closing the update.zip is done wrong. How can I pass the verification section?
2. It IS possible to push such a .zip through stock recovery, right? I want to avoid CWM and TWRP and make it as simple as possible.
Thanks.
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
dxppxd said:
Have you tried making the changes without the unzip-rezip step? Editing the zip contents directly inside the zip (just drag n drop, delete, etc).
Click to expand...
Click to collapse
I tried this, too.
I only deleted one apk from system/app and later I tried again by deleting the apk and its odex file, too.
In both cases, instead of rejecting the update instanlty, it starts the process and then stops after a few seconds.
IS it possible that there is a filesize checker text inside the image?
(or maybe a propery inside the build.prop or updater-script ?)
Any ideas, anyone?
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
iraklisvel said:
Still no progress.
I am trying to avoid custom recovery,
(I guess that would involve re-compiling it - which I do not know how to do - or ... just asking so from someone?)
is it possible to push the update.zip through stock recovery?
Click to expand...
Click to collapse
No
Stock recovery doesn't flash custom roms
Get cwm from builder.recovery.com
Press thanks :good: I'd helped :highfive:
I have CM 10.1.3 installed on my i9100 and I flashed the ZIP file from the thread at the bottom of this post through CWM Recovery. Now, my phone is stuck at the boot screen.
I would realllly hate to reinstall my ROM and all apps, so I'd just like to fix the problem. The ZIP makes changes to the 'SurfaceFlinger' library. Could I reflash a ZIP of the original library? Any idea how I could get the file?
surfaceflinger-fix.zip
http://forum.xda-developers.com/galaxy-nexus/development/fix-lag-fix-cm10-based-roms-cm10-t1875490
SOLUTION:
The only file that surfaceflinger-fix.zip affects is libsurfaceflinger.so. So, I tried extracting this file from a copy of the CM 10.1 zip file. libsurfaceflinger.so is located in system/lib. I then created a flashable ZIP using this guide:
http://forum.xda-developers.com/showthread.php?t=2163974
I flashed the ZIP after pushing it via 'ADB push sample.zip /sdcard'. I installed the ZIP via CWM Recovery. Clear caches, reboot. STILL DIDN"T WORK.
So then I took a look a look in the META-INF folder of surfaceflinger-fix.zip and noticed some additional files that I did not have in my custom 'sample.zip'. So, I just took the libsurfaceflinger.so file that I extracted from CM 10.1 and put this file in surfaceflinger-fix.zip, replacing the original one in the ZIP file. Pushed this ZIP via ADB, everything works.
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
ghostofcain said:
Had you taken a backup prior to flashing the zip it would've been five minutes work fixing your problem, I'm sure there's a lesson for all of us there.
Click to expand...
Click to collapse
This was definitely easier and this is a better fix than using a backup, but I absolutely agree with you.
[FONT="]4 - Way Reboot Menu for Nabi2 JB 4.1[/FONT][FONT="]Haven't seen a lot of development for the Nabi2 as much as we had before and got the idea from my my Galaxy Phones. This is the extended Reboot Menu only and not the "Power Menu". I do not recommend flashing to Custom Roms as the ROMs may contain special permissions/policies ( if added ) that the Rom Developer may have implemented or even may be require so the Custom Rom may run or function properly. [/FONT][FONT="]
[/FONT][FONT="]Knowing there may not be any for the Nabi2 ATM, I guess we are safe from this LOL. [/FONT]
[FONT="]The Extended Reboot Menu Includes:[/FONT][FONT="]REBOOT[/FONT][FONT="]
[/FONT][FONT="]( Normal Complete Reboot)[/FONT]
[FONT="]HOT BOOT[/FONT][FONT="]
[/FONT][FONT="]( Quick Reboot for restarting the Android Shell only )[/FONT]
[FONT="]DOWNLOAD ( Not Working Correctly, will look into this one. Will also be renamed to BOOTLOADER )[/FONT][FONT="]
[/FONT][FONT="](Bootload Mode)[/FONT]
[FONT="]RECOVERY[/FONT][FONT="]
[/FONT][FONT="]( Restarts phone in your Recovery )
[/FONT][FONT="]SHUT DOWN[/FONT][FONT="]
( Turns the Tablet Off )[/FONT][FONT="]
[/FONT][FONT="]===================================================================[/FONT][FONT="]
[/FONT][FONT="]DISCLAIMER:[/FONT]
======================================================================================================================================
[FONT="]By YOU, the USER, flashing this file or manually pasting to modify your Android System, YOU understand and know what YOU are doing. I nor anyone will be held liable nor responsible for YOUR doing if your phone bricks. As always, as is suggested by many and myself, please make sure you perform a complete[/FONT]
[FONT="]NANDROID BACKUP[/FONT]
[FONT="]before flashing and/or modifying your OS or the mentioned stock .jar file. I also suggest YOU keep a separate copy of the stock .jar file handy, like in your External SDcard, if the phone decides not to boot up. Knowing this, YOU assume all responsibility for what happens as YOU, the USER, know and comprehend what YOU are doing and understand the consequences or severity of damages that can be brought to your [/FONT][FONT="]
[/FONT][FONT="]device by flashing or modifying your OS incorrectly. [/FONT]
[FONT="]You[/FONT][FONT="] Have Been Warned !![/FONT][FONT="]
[/FONT][FONT="]===================================================================[/FONT][FONT="]
[/FONT][FONT="]What's Needed / Recommended:[/FONT][FONT="]Rooted Device [/FONT][FONT="]( to extract the needed files Manually for backup )[/FONT][FONT="]
Custom Recovery ( TWRP for Flashing the ZIP and/or using the File Manager )
If you can do it via ADB Commands then all power to you.....[/FONT]
[FONT="]I provided [/FONT][FONT="]BOTH[/FONT][FONT="] , the stock NABI2 [/FONT][FONT="]( Stock NABI2 JAR )[/FONT][FONT="] and modded NABI2 .jar [/FONT][FONT="]( android.policy.jar )[/FONT][FONT="] files and the flashable zip [/FONT][FONT="]( Nabi2_4wayboot.zip )[/FONT][FONT="] below. If the flashable ZIP does not work for you let me know please. [/FONT]
[FONT="]What To Do:[/FONT][FONT="]
You have two choices on installing the .jar file. You can either Flash the ZIP in TWRP or manually copy & paste or push the .jar file to system/framework/. If you decide to do this manually, you will then need to set the file permissions to the modified android.policy.jar file to 0644. You can rename the stock .jar file with " .bak " at the end so you don't have to delete it from the framework folder if you so choose. Now using TWRP I was not able to automatically get the File Explorer to work properly but I did flash the Aroma File Manage in recover. It load up although the button presses and screen were off but I managed to copy and paste and set permissions to the file.
[/FONT]
[FONT="]The flashable zip may give you an SELinux Error but it will flash correctly.
[/FONT]
[FONT="]
Words of caution.....[/FONT][FONT="]if you attempt to do this manually and are still actively booted in your Android OS while modifying or deleting the .jar file, there is the highest probability that your tablet will immediately reboot and you will not be able to boot up the OS again and remain stuck on the Nabi boot screen as the android.policy.jar is no longer visible to your OS. This is why you need to do this before booting up like in recovery.
[/FONT]
[FONT="]===================================================================[/FONT] [FONT="]
Thanks and credits go out to :
[/FONT][FONT="]
@[/FONT][FONT="]tdunham[/FONT][FONT="]
@[/FONT][FONT="]CNexus[/FONT][FONT="]
@kahvitahra
for the information gathered on the How-Too's and the files needed for this MOD. If I missed someone please PM me or let me know.....
[/FONT]
[FONT="]
Enjoy!
[/FONT]
looks like a handy mod ... I haven't had a chance to try it out but I will .
thanks for making it .
I know this is old but thanks for this. Going to give it a go on my kids Nabi this week.
Hippie459MN said:
I know this is old but thanks for this. Going to give it a go on my kids Nabi this week.
Click to expand...
Click to collapse
Your Welcome. If you do upgrade the Nabi 2 up to 4.4.2. KitKat, here is the thread for that one.
DarkAngel said:
Your Welcome. If you do upgrade the Nabi 2 up to 4.4.2. KitKat, here is the thread for that one.
Click to expand...
Click to collapse
:good:
Dear Admins,
Could we get a forum setup for the Cube U27GT WiFi version? I dug around on the site a bit beforehand but didn't see one, I apologize if I missed it and please direct me there if I did.
I have this tablet and I am doing some initial basic firmware development for it and want a proper place to start putting threads.
Dear Dev Community,
I can't root this bloody thing... At least, not the rom itself. Let me explain...
I can flash the stock rom from Cube and that can be rooted using Kango Root. --Fine...
However, I can't figure out how to replicate this when I make my own rom.
Thus far, here is what I have attempted...
1. Setup dsixda's excellent kitchen on my Ubuntu workstation.
2. Unpack the rom, clean things up, manually put the boot image into the dsixda unpacked working rom folder, run dsixda's root functionality (which add SU binary to xbin and SuperSu apk file to app folder as well as do some things with the boot image file).
3. Rather than using repack with Dsixda (which makes an update.zip image which I can't use because the stock recovery environment on this device can't flash zip update files and I can't for the life of me figure out how to get and or make a working CWM or TWRP recovery image for this unit)...
4. What I do is I run commands in linux to unpack the stock rom to another directory and mount that directory, then clear out a bunch of folders and then manually copy in my files from dsixda's working folder, then repackage up my unpacked stock rom into a new system.img file.
5. Then copy my now modified boot image, system image, and also userdata image (I modify that as well as that is where most all of the chinese bloatware is loaded from) to my SP_Flash_Tool, generate new checksum.ini file and flash normally...
What I get as a result...
1. As long as I am really careful with how I copy files into my new image, the new system flashes okay (if I am not careful, after flash USB storage for some reason has a format error and the system will boot but can't mount USB storage and other odd issues ensue as a result).
2. Assuming everything flashes okay, and no issue with USB storage partition, I have SuperSU installed and when I go to use an app (ES File Explorer or Root Checker) that require's root, I do get the prompt. However none of the root functions actually work and Root Checker tells me I am not rooted.
That is as far as I have got. So as a result, I have a really nice, westernized, cleaned up rom but with no root.
Anyone have any ideas?
This is my first adventure into mod'ing MTK roms so I am sure I am doing all kinds of things wrong . I had a good bit of experience on Rockchip SoC's before this though.
Kind regards and thanks in advance!
Roman
Figured it out!
So I finally did the following rather hackish work-around...
1. Flash stock firmware...
2. Root with Kingo Root
3. Enabled ADB
4. Attach to PC and fire up MTK Droid Tools
5. Take a full backup
6. Modify the system image from the backup and make changes
7. Put that in new firmware flash package
8. Flash new firmware
YAY - Cleaned up rom, modified, with root!
Once I get it all packaged up and uploaded to mtkfirmware.com I will post a link for anyone that wants a cleaned up rom with root!
The only downfall of the above method is that it absolutely requires that the developer have a device on hand because you can't just root the stock image file (at least, I couldn't figure out how... - bleh...
Kind Regards,
Roman
Dear roman,
Thanks for your hard work.
I have a simple question (I think) and if you have the time to reply or -any other android guru- I would be thankful.
My later issue was with a U27GT cube tablet, but I have others, one for each kid, and this is more of general question.
I am reading this and other forums about how to flash tablets from PC. My question is:
Can the flashing process be done from a SD card?
Thanks a lot and regards,
Fernando
SKorea