yashsingh1/xdaforums huggingface dataset:
[G 2014 Q&A, Help & Troubleshooting] quorr:
Hello everybody,

I am using The Titan Prime ROM (Version 1.0.2) on my XT1068. It is very stable and fast. (Thanks to [MENTION=5323673]Shawn5162[/MENTION] and his helpers!)

Nevertheless I would like to make some modifications to the boot.img. I am able to modify the system folder and resign the package.

But if I try to unpack and repack the boot.img the phone jumps immediately into the bootloader after the start and says 'Fastboot Reason: Fall-through from normal boot mode'.

I hoped you could have a look at my workflow and tell me what I am doing wrong:

First I take your Rom and unzip it:

$ unzip TitanPrimeROMv1.0.2-XT1068-69.zip -d Titan
$ cd Titan

Here is what the boot_info tells me:

$ boot_info boot.img
PAGE SIZE: 2048
BASE ADDRESS: 0x00000000
RAMDISK ADDRESS: 0x01000000
CMDLINE: 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags'

Then I unpack the boot image:

$ unpack boot.img
Boot = boot.img
unmkbootimg version 1.2 - Mikael Q Kuisma <kuisma@ping.se>
Kernel size 6449544
Kernel address 0x8000
Ramdisk size 807152
Ramdisk address 0x1000000
Secondary size 0
Secondary address 0xf00000
Kernel tags address 0x100
Flash page size 2048
Board name is ""
Command line "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags"
This image is built using standard mkbootimg
Extracting kernel to file zImage ...
Extracting root filesystem to file initramfs.cpio.gz ...
All done.
---------------
To recompile this image, use:
$ mkbootimg --kernel zImage --ramdisk initramfs.cpio.gz --base 0x0 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' -o new_boot.img
---------------
2974 blocks

Now I make some minor modification to the boot image like adding a file:

$ touch boot/ramdisk/hello_ramdisk

Then I try to rebuild the ramdisk:

$ mkbootimg --kernel boot/zImage --ramdisk boot/new-ramdisk.cpio.gz --base 0x0 --cmdline 'console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 vmalloc=400M utags.blkdev=/dev/block/platform/msm_sdcc.1/by-name/utags' -o boot.img

I remove the boot folder, zip it and sign it:

$ mv boot ../
$ zip -r myrom.zip *
$ java -classpath /opt/android-sdk/tools/sign/testsign.jar testsign myrom.zip myrom-signed.zip

Then I place the file on the sdcard and try to install it via TWRP ‘Install’.

I am not sure what I am doing wrong any help would be appreciated :fingers-crossed:

Edit

I have tried the same procedure with CM-12-unofficial and stock ROMs and the result is the same, if I touch anything.
[G 2014 Q&A, Help & Troubleshooting] 90180360:
Did you ever solve this problem?

Edit: https://github.com/xiaolu/mkbootimg_tools worked for me.
[Ascend Mate 7 Q&A, Help & Troubleshooting] KF Lam:
I have bought recently (within 3 months) bought 3 Huawei smart phones, namely Honor 3C, Honor 6 and Ascend Mate 7.

First two series are value for money products, particularly Honor 6, which come with 3gb RAM. Thumbs up!

I just got my Ascend Mate 7 less than a week now and still exploring.

Encountered 2 problems.

1) Could not find way to display the RAM & ROM usage. This usually easily display thru -->settings-->Storage-->??

Checked and found -->Settings-->Manage apps shown those apps installed/downloaded etc but did not display the memory used up and whats left.

2) Just curious how to set up and create a guest profile I can across in this forum such that only the intend apps will be shown/displayed when Guest password is log-in. That is to say it allow to creat the 'secondary layer' for Guest log-in to protect privacy.

Hope someone here could shade some lights.

Regards
[Fire TV Themes and Apps] 0rca:
I am seeing high CPU-loads when playing back music (that's actually all I am gonna use my AFTVs for) under Kodi 14.0, e.g. playing DI-fm via the addon.

The CPU is fluctuating heavily between 10-30 % on both cores, somtimes even more (as shown in Kodi system information.

That shouldn't be the case, should it? Any ideas?
[Miscellaneous Android Development] nikagl:
Here's some screenshots:
[Miscellaneous Android Development] Shreps:
You have done the hardest part, just need to push the su daemon service for KK ?

Envoyé de mon A1-840FHD en utilisant Tapatalk
[Miscellaneous Android Development] nikagl:
Just in case anyone reads this thread and decides to try it on their own - the system.img wasn't mountable (yet). Looks like I used seek= instead of skip= when creating the new image... will try again later.... :)
[Miscellaneous Android Development] nikagl:
Yeah, rooting works!

Check first post for details...
[Miscellaneous Android Development] ARRRDJ:
Nice!!! Realy like your work :) So we now have root on Acer Liquid S1! Will there be a quick way to root it? :)

with a kinda batch tool for instance?
[Miscellaneous Android Development] nikagl:
Oh yeah, we sure will. I'll contact [MENTION=3392632]entonjackson[/MENTION] to know whether we can add it to his toolkit and [MENTION=631273]Chainfire[/MENTION] to know whether we are allowed to include SuperSU in a kit this way...
[Miscellaneous Android Development] ARRRDJ:
Nice!! :o Finally, root for S1 :)

Will you keep us up to date with the latest developments? I cannot wait to run Xposed ;)
[Miscellaneous Android Development] nikagl:
Sure. I will need [MENTION=3392632]entonjackson[/MENTION] for that though, otherwise I'll have to rewrite his code to suite S1, use the MTKLogger and add SuperSU. Adding Xposed is a good idea too - the problem with the /system on this device is that it's locked and we cannot unlock it. So adding stuff (or removing for that matter) always requires to use an existing /system dump and restore it to the device using dd. Recovery too, will only allow installation of signed zips and as we don't have the right keys, we won't be able to use (or change) it... In the end, doing a root from scratch will always require either Ubuntu (to do it with the ROM you have on your device) or restore a system.img from another device... It requires Ubuntu btw, because in Ubuntu you can mount a system.img and easily change it, which is not feasible from DOS/Windows...

So... for the time being, let's wait for [MENTION=3392632]entonjackson[/MENTION] and if he doesn't have the option, I'll try to write something. Just keep in mind I am not a developer, I can follow procedures and hack my way into existing stuff, but writing from scratch remains a bridge too far... :)
[Miscellaneous Android Development] ARRRDJ:
Okay, let's hope [MENTION=3392632]entonjackson[/MENTION] can help! Oehw that's sad. So it's impossible to root this phone on the 'normal' way? Is it restricted in the software or in the hardware?

But once you've rooted it, can you use Xposed (or another rootapp), without having to restore a systemdump file?

Ubuntu is not a problem, since I develop in Ubuntu ;)

No problem! I've a lot of respect that you came so far without having a lot of experience ;) :o
[Miscellaneous Android Development] nikagl:
It's in the software/signing of the zips. The keys are unavailable for "normal" people like us. Just Acer has them I guess.

Yes, as soon as Xposed is integrated, you can use it. With the integration I am a bit worried to do it though. I have looked at the current release of Xposed (de.robv.android.xposed.installer_v33_36570c) and it requires me to replace /system/bin/app_process with the one from Xposed. My S1 does not have USB access anymore so I am very hesitant to replace a file like that. If it gets into a bootloop, I won’t be able to recover it…

Also, the update-binary that Xposed uses to integrate itself into the framework replaces that app_process file, but also expects certain configuration (/data/data/de.robv.android.xposed.installer) of the APK to be available. I am afraid that the apk needs to be installed before actually introducing the new app_process file. As the installation of the APK is not part of /system and therefore the /data folders will not be created, I wonder how it behaves if the new file is introduced in the new /system...hopefully it won't cause bootloops....

Regards,

Nika.
[Miscellaneous Android Development] nikagl:
I tried adding Xposed by changing the app_process file but it didn't work. I used the following commands:

sudo cp de.robv.android.xposed.installer_v33_36570c.apk /media/iconia/app/
sudo cp -a /media/iconia/bin/app_process /media/iconia/bin/app_process.orig
sudo cp de.robv.android.xposed.installer_v33_36570c/assets/arm/app_process_xposed_sdk16 /media/iconia/bin/app_process
sudo chmod 0755 /media/iconia/bin/app_process

It does see the new file version installed but Xposed is not running. Asked in some threads for extra help. Also no response yet from [MENTION=3392632]entonjackson[/MENTION], so asked in the Iconia thread whether there's others that can help :)
[Miscellaneous Android Development] ARRRDJ:
Ah okay, unfortunately!! :( I cant wait to run xposed! I hope you'll get some support from members with more experience, because I think we're really close to a more easier rooting way ;)

Let me know if you make some progress :)
[Miscellaneous Android Development] nikagl:
So do I and trust me - I tried it all. Also tried it on another device, it will simply not start and I don't know why :(

Regards,

Nika.
[Miscellaneous Android Development] ARRRDJ:
progress?

Any progress yet? ;)
[Miscellaneous Android Development] nikagl:
Nope, just root works. If you want I can add it to the rootfrom scratch method of the toolkit, but Xposed won't work. Simply do not get any help from anywhere to fix this and spent hours (if not days!) troubleshooting it, so i have given up...
[Miscellaneous Android Development] sidethorn:
thanks it's a wonderful job anyway u really deserve respect! :highfive:
[Miscellaneous Android Development] nikagl:
Make sure to monitor the following thread for new versions:

http://xdaforums.com/showthread.php?t=2240029

I am not yet sure when I get to make one, it's almost holiday week here in NL and with that and the preparations for it I don't have much time... more news soon.
[Miscellaneous Android Development] nikagl:
I have created the first Acer Liquid S1 version of the toolkit. Let me know what you think.
[Miscellaneous Android Development] sidethorn:
First of all thank you very much for your efforts, I just downloaded your toolkit but it says "put prerooted system.img.gz... " etc. Question is where do I find prerooted system.img.gz?
[Miscellaneous Android Development] nikagl:
Hi sidethorn,

If you do not have ubuntu you depend on someone that provides a prerooted system.img.gz if you want to root your phone. Anyone with an S1 and ubuntu who can run the Toolkit on Ubuntu can create that img file. I can provide mine, but it has three disadvantages:

1. I didn't make it with the toolkit but manually. It shouldn't matter, but I couldn't test it

2. It was created including a non-functioning xposed configuration. If you don't mind ignoring Xposed it's fine

3. Although it shouldn't matter, my phone is one of the first S1 devices. It therefore could be slightly different from others...

So, it would be best if someone else can make a prerooted system.img.gz. If not and you're still willing to try the above, let me know and I'll mine.

Regards,

Nika.
[Miscellaneous Android Development] sidethorn:
openSUSE user here so I can assume it will work anyway... but I'm quite a bit confused since I've only rooted samsung phones 'til now... well to cut a long story short I thought the kit would automate the process and it it does but you must have a prerooted system.img.gz right? procedure to preroot is in post #1?

thanks ;)
[Miscellaneous Android Development] nikagl:
No, in post 1 it's only the MANUAL procedure when I had not yet added it to the Toolkit. You should be able to use the Toolkit.

When using the toolkit, after the following selection:

[1] Root

You should get the ability to:

[1] Root from scratch (without prerooted system.img.gz).

[2] Root with prerooted system.img.gz (must be placed in folder 'system_image' on your PC)

If you do not get that question but get "================== Root =================" instead it means it detects your system as "windows".

But I think you must have chosen 2 instead of 1. When you select 1 it should do the whole process for you :)

Keep in mind it's definitely not as easy as Samsung devices. The root process is difficult because Acer decides to lock most of their devices in a way they are very difficult to unlock...

Regards,

Nika.
[Miscellaneous Android Development] sidethorn:
My fault... I saw an .exe so I launched it from windows and didn't notice toolkit.sh... shame on me :D still not sure if I want to root my phone, i just got it back from repair assistance due to mother board failure I will think about it
[Miscellaneous Android Development] nikagl:
In most cases it's not necessary to root it. I do it simply for fun ;) but you can brick it to so some caution is always necessary. In some cases root gives you a bit more access to some Android features for ultimate control from for instance Tasker. If it would also enable /system to be mounted as r/w it would also allow you to simply uninstall system apps or install new ones like Xposed. Uninstalling system apps I do by disabling them, so that's not necessary imho (would just safe some space) and running Xposed I have not gotten to work so far which is really a big shame because it would give us many more features (like custom buttons, changing lockscreens, power menu, blinking menu buttons for calls, etc., etc, etc.)...hoping for the community to help with Xposed but so far... nothing :(
[Miscellaneous Android Development] sidethorn:
I totally agree with you as I said before I used to have a small galaxy crap phone so I used root to uninstall bloatware that came with that phone but also to move app to sdcard (and depending the rom even some system directory to get free space) :D

Uh i tried the procedure with openSUSE, phone disconnected though, and I can confirm it works so we can assume it works with every linux distro. Xposed would be a dream... like lollipop on our device... well keep trying to ask developers maybe right now are to busy to adapt Xposed for lollipo i read somewhere that it is not fully compatible... let's cross our fingers
[Miscellaneous Android Development] sidethorn:
Hello any news from Xposed team? and do you know if we will ever get Lollipop on our device (just a dream... i know...) :D
[Miscellaneous Android Development] nikagl:
Nope, nothing :(
[Miscellaneous Android Development] sidethorn:
sh...ame! :crying:
[Miscellaneous Android Development] ARRRDJ:
Good job till now! Thanks for that. Hope we'll get some help soon!
[Miscellaneous Android Development] sidethorn:
Knock Knock

hello any news? did u abandoned us :crying: ?
[Miscellaneous Android Development] nikagl:
Lol. No, i'm always here. Root is available using the toolkit (not sure whether anyone ever tried it). But Xposed won't appear because I couldn't get it to work and no developers want or seem to be able to help me/us...
[Miscellaneous Android Development] 953091:
Hello nikagl ! Can you give a rooted KitKat firmware of S510 to me ? I'd like to try ! Thanks !
[Miscellaneous Android Development] nikagl:
I'm afraid someone else needs to provide it. The rooted firmwares I have are test versions when I was creating this topic. They include non-functioning xposed and older version of supersu. As my device does not have functioning USB I cannot easily create an image. So... hopefully someone that has unix can do a root from scratch for you and upload the image for you?
[Miscellaneous Android Development] RM57380:
Hello!

This tool works with the Acer Liquid S1 dual-sim?

And with the lastest update of the software?
[Miscellaneous Android Development] nikagl:
This thread does not actually contain a tool - the tool is in the Acer Iconia thread, see first post. And yes, it supports the latest version of S1 dual-sim. Note that you need Unix for it to root from scratch using the current ROM you have.
[Miscellaneous Android Development] sidethorn:
Hello

I know I could be irritating but are there any news with Xposed? Did u try asking for help in the G+ community? maybe a wider audience could help solve the problem ;)
[Miscellaneous Android Development] nikagl:
No, haven't tried. XDA is my community of choice... and I've given up creating Xposed for S1 (don't use the device anymore atm)...sorry...
[Miscellaneous Android Development] sgauge:
Hi nikagl, I finally managed rooting my S510 with v0.9.4 of the toolkit. So big thanks to you.

However that was not a straightforward process. I encountered 3 issues ("root from scratch" using a linux mint box) :

- First, device is not correctly detected by the script, although it is by adb. Had to change the script line 1282 :

if "33862727964" in out:

To readers : replace 33862727964 with your actual device id, as seen when running toolkit.sh with -d parameter

- Second, the telnet session was not launched automatically, I understood it was due to word completion on my phone's keyboard, preventing the script to actually run the command.

- Third, system.img.gz was too big to be unzipped (+5GB). This was solved uninstalling most useless apps and all games.

Kudos to you, I can now use greenify and other root apps !
[Miscellaneous Android Development] nikagl:
Thanks sgauge!

For adb, for a1 they had included some code in the previous version, that should work for s1 too.

Not sure why it's only for a1, because any other (non-a1) device should fail too:

elif a1:
regexp = re.compile(r'[a-zA-Z0-9]{11,16}\s+device')

I added " or s1" to the above and it should be ok now:

elif a1 or s1:
regexp = re.compile(r'[a-zA-Z0-9]{11,16}\s+device')

For telnet I'm not sure what to do. I guess instructions on the OP should include some instruction like "make sure to disable word completion"?

The space error is caused by lack of space on your laptop or device, right? Not really something we can do about....
[Miscellaneous Android Development] Ashby7:
Write the instruction obtaining root for inexperienced users. How to install adb driver? Get the following error:

======= Acer Iconia Toolkit v0.9.4 =======

Which device do you have?

[1] Acer Iconia B1-A71

[2] Acer Iconia A1-810 / A1-811 / A3-A10 / B1-711 / B1-720

[3] Acer Iconia B1-710 / B1-A710

[4] Acer Liquid S1 (S510 / A10)

[Q] Quit

Enter a selection: 4

======= Acer Liquid S1 (S510 / A10) Toolkit v0.9.4 =======

What do you want to do?

[1] Root

[2] Unroot

[3] Internal 2 External (needs root)

[4] Odex (needs root)

[5] Pull system.img.gz from tablet

[Q] Quit

Enter a selection: 1

What do you want to do?

[1] Root from scratch (without prerooted system.img.gz).

[2] Root with prerooted system.img.gz (must be placed in folder 'system_image' on your PC)

[Q] Quit

Enter a selection: 1

Do you want to make your external SDCard writeable?

[Y]es

[N]o

[Q]uit

Enter a selection: y

Do you want to do everything all at once (= do not wait for input before restoring system.img?

Make sure to:

1. Plugin both computer and device into power

2. Do not touch the device

3. Do not EVER disconnect the USB of the device

4. Make sure to wait till everything succeeds!

Failure to do so may cause disconnect in the restore procedure which can brick the device!

[Y]es

[N]o

[Q]uit

Enter a selection: y

================== Root =================

Before we can start, please do following:

1. Plug-In your Acer Liquid S1 (S510 / A10) into this PC.

2. Enable USB Debugging Mode by going into Settings -> Developer Tools.

3. Keep your device plugged in until it's finally unrooted, or this procedure is aborted!

If you sucessfully applied the steps above, we can now start.

You can always abort by pressing Ctrl+C.

The following procedures can take up to 30 minutes!

To finally play back the rooted system.img.gz a confirmation will be needed then.

[ENTER] Continue

[Q] Quit

Enter a selection:

[sudo] password for chelios:

2015/10/24 06:31:46: Trying to establish ADB Connection...

2015/10/24 06:31:46: E: Couldn't connect to your Acer Liquid S1 (S510 / A10) over adb. Plug-In the device with USB-Debugging Mode turned on.

If you keep getting this error, try to run toolkit with -d or --debug parameter

Press Enter to leave Application...
[Miscellaneous Android Development] nikagl:
Hmmm... If I knew, I would post it. Are you sure you have USB debugging on in your device? Did the -d parameter post more info? In my case it simply worked, maybe search xda how to install adb for android/acer devices on a linux distro?
[Miscellaneous Android Development] Ashby7:
ADB how do I installed, the device is defined as need, Internet wifi included.

Please make method of rooting in the Junior firmware using S1_Root-v1.2

adb installed:

sudo add-apt-repository ppa:nilarimogard/webupd8

sudo apt-get update

sudo apt-get install android-tools-adb android-tools-fastboot

usb debugging is enabled, there are no results
[Miscellaneous Android Development] Ashby7:
List of devices attached

33559283864	device

corrected line 1282: 33559283864

still get the following error:

2016/02/01 10:41:31: Trying to establish ADB Connection...

sudo: unable to execute bin/posix/64/adb: No such file or directory

2016/02/01 10:41:31: E: Couldn't connect to your Acer Liquid S1 (S510 / A10) over adb. Plug-In the device with USB-Debugging Mode turned on.

If you keep getting this error, try to run toolkit with -d or --debug parameter

Press Enter to leave Application...

How to start toolkit.sh? May need to put the penultimate firmware КК? Ubuntu installed on the system ubuntu-mate-15.10-desktop-amd64
[Miscellaneous Android Development] nikagl:
I wish I can help. I do not have USB connection to S1 because my USB port is broken. Maybe ask in the toolkit thread?

http://xdaforums.com/showthread.php?t=2240029

Did you extract the entire zip into a folder on your ubuntu system and navigate with terminal to that folder? One of the subfolders is bin/posix/64 and that has an executable called adb. Does adb have executable rights in your unix system ("ls -la adb" should show x rights for user and/or group)?

Also, search the above mentioned thread. I noticed similar error with (maybe?) the solution:

http://xdaforums.com/showpost.php?p=45009441&postcount=1564
[Miscellaneous Android Development] Luneya:
Hi there!

I'm new to the rooting of phones, but my warrenty expired on the Liquid S1 so I hoped this would be a way to keep Android updated (because of course, Acer only provided Android updates for a year or so.. now stuck at 4.4.2)

Since I am a newbie, I find myself wondering if it is even possible to update Android to the latest version when rooted? I understand it's not even possible to delete all the useless bloatware from Acer?
[Miscellaneous Android Development] nikagl:
Sorry, S1 is a locked device and there's not much you can do. When you have root you can access system files, but modifying is not possible either, you will need to use the linux image to do that which is a very, very difficult job. Best way to keep using the device is get it to the latest 4.4.2 release and simply disable the bloatware you do not like (from the Settings --> Apps screen)...It's still a very usable device that way.

Good luck.

Regards,

Nika.
[Miscellaneous Android Development] Ashby7:
Acer Liquid S1 (S510), acer_iconia_toolkit_v0.9.4b_32bit

nikagl

If I pour the rooted firmware system.img.gz KK Acer_AV0K0_S510_RV19RC01_WW_GEN1, can see it? May be able to mount it on the change in the system partition? Ideally would be to redo the image for the firmware as update.zip or through S1_Root-v1.2

I really want to win this shortcoming KK.

system.img.gz

text
[Miscellaneous Android Development] nikagl:
I don't think it is possible with this device. The KK sources were never published by Acer, and I think without that, it can't be created.
[Miscellaneous Android Development] Ashby7:
nikagl

a pity to throw out iron, agree to any experiments