Develop Bugs

HTC Desire Boot Animation [Ubuntu Guide]

Thought I would post as I'm not sure if anyone has tried this yet but I used the nexus 1 bootloader anamation found here and it works perfectly.
So for anyone who wants to do it them selves heres a guide once you have rooted your desire follow these steps.
1. Put the nexus-bios-boot.zip onto your sd card.
2. Load up into ubuntu.
3. Turn off your desire.
4. Turn it on again while holding down the 'volume down' button this time. The screen will look similar to before, but will say 'HBOOT' instead of 'FASTBOOT'. Use the volume buttons and the power button to select the 'RECOVERY' option. You should then see a screen with a red triangle - at this point, plug it into your usb.
5. Now you need to unzip the 'push files' zip that you downloaded.
6. copy pushfiles folder to the desktop
7. open terminal
8. type this into the terminal window
Code:
cd ~/Desktop/pushfiles
9. then type
Code:
sudo ./recovery-linux.sh
10. In the recovery image (moving around using the optical trackball), select 'Flash zip from sdcard' and choose the nexus-bios-boot.zip
11. Confirm then reboot desire.
I would like to point out that none of this is my own work I simply compiled all of the above information from others work to make a simple guide. All credits goto Paul @ MoDaCo for rooting and his guide and I am unsure of who actually made the boot screen. But the link is at the top of the post.
Below are all of the files you will need to get started
and here is a quick vid

nice one, thanks

Installed this too, looks smart!

Dont know if anyone noticed but as its booting it says nexus one lol I have posted in the original thread maybe someone who knows what they are doing will edit it and make one specifically for the desire.

Hi,
Great work!
Would this work for all Boot screens for Android?
Regards
Mo

I'm honestly not sure this is my first android phone. I saw the boot animation thread a few weeks ago an thought as soon as we have root I'm going to try it and to my sunrise it worked. I would guess any existing nexus one animations would work on the desire fine but I an not 100% sure. If you find any others I would be happy to try them and post my results.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk

FeaRThiS said:
I'm honestly not sure this is my first android phone. I saw the boot animation thread a few weeks ago an thought as soon as we have root I'm going to try it and to my sunrise it worked. I would guess any existing nexus one animations would work on the desire fine but I an not 100% sure. If you find any others I would be happy to try them and post my results.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Umm How about..
These over at modaco?
Green Android is Very Cool....
Regards
MoJo

As soon as I get my pc up and running again (can't believe I still use Windows) I will test them out and let you know if they are working
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk

FeaRThiS said:
As soon as I get my pc up and running again (can't believe I still use Windows) I will test them out and let you know if they are working
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk
Click to expand...
Click to collapse
Thanks buddy.
I'm looking forward to it.

It would be nice to have a bootup with the actual android on the screen lol

I quite like the Open Eclair boot animation. The one with the logo exploding into a million androids that fly at the screen.
Sent from my HTC Desire using the XDA mobile application powered by Tapatalk

as you can restore the original boot?
Thanks

I have not tried but as the boot animation is loaded onto the rom I would guess if you restored an original rom I would set it back to "how it was ment to be". I am jus grabbing the files I need now and will test a few more out and post my results + vids.

mojavaid36 said:
Umm How about..
These over at modaco?
Green Android is Very Cool....
Regards
MoJo
Click to expand...
Click to collapse
I have just tried all three and get the same message saying... E: No signiture E: Verification failed
I also tried another from the original thread I linked to the nexus-boot-apple 1 and it worked fine. Possible they need signing properly and then they would work but dont really know enough about android phones atm to really sepectualte.
Edit: Just been told that the files you linked to do not get flashed but you push them over via adb.

bootanimation.zip
Just a wierd question.
I tried to create a bunch of png files to create an animation.
Numbered from 00001 to 00009
I placed those in a folder named android.
Edited the desc.txt file to:
480 800 1
p 1 1 android
Zipped this to bootanimation.zip and placed this zip file in /data/local
When rebooting the phone i get a nice black screen.
Now what am i doing wrong in this progress?
Greetings from a vastloper

You need to re-sign the package. To do that just zip up the 'data' and 'META-INF' directories then use the following guide to sign it:
http://forum.xda-developers.com/showpost.php?p=3175518&postcount=2

i signed it also.
Didnt work either.
Do i need to change the meta.inf file ?
Thanks for the reply

It shouldn't be a file called meta.inf, it should be a directory named META-INF.
If you use nexus-bios-boot.zip as an example (from Post #1) then in the META-INF directory should be a few signature files:
CERT.RSA
CERT.SF
MANIFEST.MF
(delete these - they will be recreated when you sign the file)
and subdirectories com -> google -> android containing the update-script
(which can be left alone)
Do you have the update-script in the correct place? Zip it all up, sign and apply. Any change?

Might be a problem with bootanimation.zip actually.
http://androidforums.com/all-things-root-droid/25774-custom-boot-animation-figured-out.html
I think the folder with the .pngs needs to be called part0 and part1:
"the folder part 0 is the part that does not loop. part 1 will loop after part 0 plays and while phone is still loading."

Final tidbit...
You could always just use adb to push the bootanimation.zip to the correct place.
No need to worry about signing or update-script! Of course you have to do this from recovery mode after mounting the system, so the full code you would run:
Code:
adb shell mount /system
followed by:
Code:
adb push bootanimation.zip /data/local/

[REF][GUIDE]CWM md5 mismatch problem solved

So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
WARNING!​
I'm no dev, just someone, that knows linux.
If you follow this path, you do it on your own. I'm not responsible for bricked devices, lost data or whatsoever, including the future the past and the present.​
Click to expand...
Click to collapse
There are three ways for you, to make an md5 sum of the img files, the good and the bad one and also the quoted one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
cd /sdcard/clockworkmod/backup/{recovery_timestamped_directory} <- this is from your backup, so you need to fill in appropirate data
md5sum *img > nandroid.md5
Click to expand...
Click to collapse
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
.android_secure.vfat.tar
boot.img
data.ext4.tar
{nandroid.md5}
recovery.img
system.ext4.tar
Click to expand...
Click to collapse
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
Three (the quoted one)
Also on the 2nd page you will find an alternative solution for the problem which can help you if you have got busybox installed on your device.
The solution resembles the One type of fix, so with quotes here's the one (thanx for Meeshka for it).
Meeshka said:
For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me
Click to expand...
Click to collapse
If I helped, don't hesitate to push the Thanks button.

Thanks... a very useful guide. Bookmarked

WORKED!!! Tho I'm from a different device the first (adb) method saved my AOKP backup!!! Daysaver I'd say!!

I keep getting "md5sum: not found"

Put this in the general android section as it works across most devices. ..
Sent from my One V

Nevell said:
I keep getting "md5sum: not found"
Click to expand...
Click to collapse
if you send me the 2 img files i can create an appropirate md5 image of them, but send the one you did, so I can guess what the problem is.
send them to the email of my usr here, or in pm. and mainly, the md5 image has the name "nandroid.md5" like small caption all the way, even the md5? If it is there where it must, it must work, ad absurd it will be "wrong checksum error", but that is another version.
General android section has this, I have learned this from there, but it had only 1st option, and was "discovered" when cwm had generated wrong md5s, the V, in the V the problem is a tad bit different, but the solution is the same.

I fixed it in adb
Sent from my SPH-L710 using xda premium

Nevell said:
I fixed it in adb
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Can you explain what did you do to fix md5sum: not found error??
please i need it!

thatsgamer said:
Can you explain what did you do to fix md5sum: not found error??
please i need it!
Click to expand...
Click to collapse
Just created an md5sum manualy from the img files with the name of nandroid.md5, because on the V the recovery doesn't creates them because of cache mount problem.
The recovery process will end in an error message, because cache cannot be recovered, but the main thing will be recovered this way.

i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone

haky1988 said:
i have one x and i can't put sdcard in to card reader because one x dose not have sd card... and i cant fix it whit first solution because i cant acces my phone
Click to expand...
Click to collapse
See : http://forum.xda-developers.com/showpost.php?p=32248108&postcount=7

unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup

CWM showing different versions
-Delete-

maranello69 said:
unfortunately none of the methods described in the first post have worked for me, at the first one i got an "unable to write, source is read-only" error, and the second one failed from the first try
after almost giving up and beginning to deal with the idea of loosing my backups, i found this topic and in 10 secs it got the job done, now i'm back on my latest cwm backup
Click to expand...
Click to collapse
You do know that the first method is exactly like the one you linked right?
Aside that, I'm happy that the community could help you out

Loir can u help me. I can't locate the boot.img inside the downloads for cyanogen mod u provided. Forgive me but can you post a directory to this kernel file? Tks
Sent from my HTC Desire X using xda app-developers app

Thank you so much. You saved my phone.

For those who keep getting "md5sum not found" both in adb and in android terminql on device:
try instead
# busybox md5sum *img > nandroid.md5
worked for me

no * 's
Ken-Shi_Kun said:
So, many of you probably faced the issue, when you tried to restore your CWM backup, that the recovery says MD5 mistmach, and will do nothing. The problem is now solved, and was solved, so I'm not the one, who made thing possible, I'm just porting this to the V.
So, the problem (in my iterations at least) are based on the /cache/ cannot be mounted error, which is common in the V. For why is that, I simply don't have a clue, but it is present. Because of this, the backup won't be full, and thus, the md5 image won't be made for the recovery, so cannot be recovered as is.
But happily you can make an md5 image from the backup yourself, and thus recover your backup.
​
There are two ways for you, to make an md5 sum of the img files, the good and the bad one:
One (the good)
For this, you will need adb, root, and a working android. Yo don't have it? Here you go.
Go to the directory, were you have adb (or have extracted adb.exe, suggested c:\htc\), then plug in your phone (just for charge, no data connection), open terminal (syntax: cmd) then type in:
adb shell
this will get you to the phone's terminal
if you have # at the end of the line, you are good to go, if not, then type su
The syntaxes needed:
This will make an md5 image with the name that cwm acknowledges.
Two (the bad one)
So, you'we fired your ROM, cannot even boot, but cwm comes in. Than this is for you. There are programs (e.g. total commander) which can make md5 images. So if you have your backup folder, just go into it (sd card reader is preferred). You will see something like this in it:
sidenote:
If you have the nandroid.md5 and you cannot recover, don't try to recover from it!!!
The image itself is corrup, you have no luck, try RUU. (you can recover if you delete the md5 and create a new, but it is not really recommended)
1.
So, there are 2 .img files, highlight them in totalcommander. go to file->create checksum files
2.
tick in md5, then ok
3.
No, you're not done
open the md5 file in text editor, and remove the * 's from before the file names.
4.
Rename the file to nandroid.md5
5.
Now you're done, go to cwm, then recover.
If I helped, don't hesitate to push the Thanks button.
Click to expand...
Click to collapse
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.

Beastben13 said:
in 3. it says to remove the * *'s, but i don't see any, so i was wondering should i leave that be or if im doing something wrong.
Click to expand...
Click to collapse
I have done the thing with a legacy tcmd, so there is a probability, that they have modified the md5sum algorithm, so if you don't se the stars don't panic. (also it should do the trick even with stars in the file, but wanted to be sure at the time I wrote the post)

plz provide touch recovery for karbon a9+ plz and ther is bugs in cwm recovery 5.0.2.8 plz

[Q] HTC 1 Mini WILL NOT INSTALL BUSYBOX

HTC One Mini - AT&T
Tried installing Busybox from GooglePlay .apk, FAILED.
Now what?
I'm guessing I have root, not sure how to be completely sure.
Unlocked fastboot, flashed recovery w/ orange, installed SU from .zip
Gave BB SU permission.
FAILED.
Now what? I need BB. Tried looking for flashable .zip to flash from orange, but can't find any DL's.
S = ON :/
I have no idea where to begin fixing this issue...

On a side note...
Still can't find flashable .zip BB version.
Tried using Jrummy BB installer w/ root, still crashes.
Someone help before I manually brick this POS... i.e. throw it at a brick wall....

I just did a search on Google it said you need an app called busy box installer from the playstore
Sent from my GT-P3113 using xda app-developers app

.APK Method/Apps DO NOT WORK.
djerk said:
I just did a search on Google it said you need an app called busy box installer from the playstore
Click to expand...
Click to collapse
They do not work. Both of these:
google*com/store/apps/details?id=stericson.busybox[/url]
google*com/store/apps/details?id=com.jrummy.busybox.installer[/url]
(Official GooglePlay Online Store)
...either crash/reboot during "Advanced/smart" install, or fail using "Normal" install.
I need to to turn "S" off to enable write to nand possibly?
Tried both /xbin/ and /bin/ install directory through .apk
Also tried both Advanced & Normal install on both apps...
OP Specifically says .apk method = FAIL....
Next answer please, lol

Also....
I also verified root, it's there. Both .apk's (Apps) had SU privelage.
Even restarted the apps to make sure they had SU right from the beginning of their loading.
So to summarize:
AT&T HTC One mini
- fastboot : UNLOCKED
- recovery flashed : recovery-clockwork-touch-6.0.3.6-m4.img
- gained root : ClockWorkMod loaded "root.zip" (.zip courtesy root-wiki)
- DL'ed BusyBox .apk's : TWO FAILURES.
- And here I am....
Android version : 4.2.2
HTC Sense Ver : 5.0
Software number : 1.24.502.3
HTC SDK API level : 5.41
Kernel version:
- 3.4.10-10-gae2031e
[email protected] #1
SMP PREEMPT
Baseband version : 1.19.40d.00.14_10.20.40.4408L
Build number : 1.24.502.3 CL224405 release-keys
Browser version : Webkit/534.30

Moderator please move post
Move post to "AT&T HTC One Q&A"
Plz & TY:angel:

I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Sent from my GT-P3113 using xda app-developers app

Which ver?
djerk said:
I just installed busy box with no issues on my Verizon htc one running 4.3 maybe you have the wrong version for 4.22
Click to expand...
Click to collapse
Which version of Busy did you use?
1.20.2
1.20.1
1.20
1.19
or earlier?

screens
Here's my screens

I installed version 1.22.1
Sent from my GT-P3113 using xda app-developers app

This needs to be in proper section. This is the HTC One Verizon section. Not mini.
http://forum.xda-developers.com/htc-one-mini
Typed on a HTCone via rumrunners

I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip

cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
DL'ed your .zip, but i'm waiting to figure out if my Mini has this "ext4" formating.
I don't know how to check if it does, and I don't want to flash something w/o knowing more.
I know ext4 is the newest? linux file structure, but I'm not sure if my Mini is formatted to it....
Anybody know how to check this?
The Mini when hooked up to a PC is recognizable as an external storage device,
so doesn't that mean its FAT or NTFS if windows can recognize it? Right?
Windows won't automatically recognize ext4 w/o installing something right?
If you have to alter or change your phone to ext4, then mine is not. I have never formatted my phone.
How can I check if this is safe for my phone?
I plan on using ClockworkMod to install this through the GUI.
What exactly is this "recovery-flashable-busybox"?
Does it get flashed over top of my recovery partition?
If so, does that mean I will lose my clockworkmod recovery?
Somehow with no idea what I was doing, I managed to unlock fastboot, and get SU.
Now I'm thinking I have no real idea of how this all works......
I would feel more comfortable installing BusyBox using an .APK because I'm a n00b
at this with an expensive toy that i don't want to break.... Like I mentioned before, would
turning S "off", would that allow me to use an .APK to install BusyBox? Or did my two .APK
installations I attempted before fail bc my internal "emulated" SD card is not formatted to
"ext3/4"? I'm lost now...
I guess in summary I need to know WHY I can't install busybox via GooglePlay .APK's,
and is this .zip safe for me to use, and if it is, how would I even use it?

It seems like the more answers I get, the more complications and questions I have...
How would I message or get help from somebody "high up" on this forum, somebody that knows all the in and outs?
I'm not gunna lie, I need a "babysitter" for this....
All I want to do is install Busybox, and after that I'm good, I don't need to play around with the "sensitive internals" of my phone.
I don't want any special roms, or anything else special. I just want SU privelages, and busybox installed.
Soooo.... how do I find a babysitter lol....
cmlusco said:
I know this is the wrong forum, but im gonna help a guy out anyways.
Does the mini have ext4 formating for system and cache partitions? If so flash this https://www.dropbox.com/s/losui4x6nkt47nx/busybox_recovery_flashable.zip
Click to expand...
Click to collapse
Also, I forgot to ask, did you mean can my phone "READ" ext3/4, or did you mean is my device "FORMATTED" to ext3/4
Neither of which do I know how to check or verify, but it would at least tell me what to do next i guess....

I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?

lgally80 said:
I think I'm may be on to something... The Util's known as "BusyBox", are a bunch of basic/necessary/commonly.used Linux commands wrapped up in a package, correct? So if they are Linux commands, then they probably have to be written to a Linux formatted partition? Correct? And if they are Linux commands, on a Linux partition, then that means my phone must be able to "speak" Linux? Correct?
So essentially I need to create an ext3/4 partition, and then write/install BusyBox to that partition?
Is my assumption correct?
Now another assumption is that the .APK's I want to use, which require these Linux commands, act as an interpreter to translate these Linux commands for my phone? Essentially, my phone does not need to speak Linux bc the .APK's know how to use the Linux commands "automatically" or "within themselves" so to speak?
Click to expand...
Click to collapse
All you need to do is flash it thru recovery. If your phones partitions are not formated ext4, the install will fail before anything is ever changed.
To find out how there fornated type mount into a terminal emulator, or at an adb shell. Look for lines with /system and /cache. In those same lines it will say ext4, ext3, etc. If there not ext4 tell me, and i will edit the flashable with the correct partitions.
All this zip does is install the busybox binary file to /system/xbin, and then make the appropirate symlinks.
Yes i reccomend getting s-off. The reason the apk wont work is because your s-on and have a secured boot.img
Busybox is a bunch of linux commands rolled into one. Your phone is already linux, but busybox puts all these commands in one place, and adds some additiinal commands not native to the phone.

Your partitions are most likely ext4 as the regular one is. Are you sure you have an unsecured boot img installed. Pretty sure busy box won't work without one. If you are not s off flashing a rom will not change the boot img. You will have to extract the image and flash via fastboot manually.
Typed on a HTCone via rumrunners

Sounds good, hopefully w this info I can move on, stuck at the laundrmat w my b**** gf, so ill post results in or about 2 hours. Thnx in adv.:good:

Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!

htc_one_mini_m4 said:
Hello guys, I've been trying to install BusyBox myself too today, but without success.
The flashable via Recovery Mode linked file is dead.
Could somebody please re-upload the file ?
Thanks!
Click to expand...
Click to collapse
http://vzw1files.dyndns.org/BUSYBOX/busybox_recovery_flashable.zip

Cyanogen 12.1 test builds for Raspi2

Download:
https://www.androidfilehost.com/?w=files&flid=39635
Let me know if these work out for you. You can smack the ramdisk to the original kernel zimage to make the boot.img partition.
Source will be released if this works...
Cheers!

hey!
i would really love to test this.
im just now sure how to get the different .img-files to my SD card (win or osx)
do i partition manually first and then write each IMG seperately? what file system?
i'm really interested in this since im planning to construct my very own RPi2-Android-Car-Headunit...

I really wold like to test this out, I would really appreciate when someone gives install instructions

@Childofthehorn
don't take this the wrong way but can you highlight the zImage your referring too?
are you talking about the android generic device kernel?
are you talking about pulling it from another distro?
just a tad more explanation and I can give this a try. I have scoped out your git for some other clues but come up empty

feherneoh said:
As there is no kernel provided, try raspbian kernel first
I will check it later as I have a "working" lollipop kernel for rPi2 somewhere, but I have to find it
Click to expand...
Click to collapse
Thanks, if we can get some source of stuffs working i would give building a crack as well

feherneoh said:
Building CM12.1 using the same device tree that I used for AOSP 5.1, will see if it works
Click to expand...
Click to collapse
Hi, news about it?

feherneoh said:
I'm buildind inside screen, so I cannot scroll (I have no idea, how to do that) and the error message is outside of the 80x50 terminal I'm using
Click to expand...
Click to collapse
Many thanks for your effort.
If you could build it and boot it, please create your own topic so you are able to upgrade changelog and so on..

feherneoh said:
I'm buildind inside screen, so I cannot scroll (I have no idea, how to do that) and the error message is outside of the 80x50 terminal I'm using
Click to expand...
Click to collapse
Well, You could redirect the output to a file and read that file using vim. To redirect to file run
Code:
command > file.txt

Is it possible to write install instructions?

yes,I want to obtain the install instruction.
Sent from my MI 2S using Tapatalk

I'm interested too!

partition boot as fat,system as ext4, cache as ext4, and data as ext4, then restore file.
Sent from my MI 2S using Tapatalk

feherneoh said:
I know how to do this, and I would need to use command &> file.txt, as I need stderr, too
Click to expand...
Click to collapse
To put also stderr to the same file use:
Code:
command > file.txt 2>&1
To use different files:
Code:
command > file.txt 2> err_file
Another possibility to see output and stderr on screen and also put it in a file:
Code:
command 2>&1 | tee file.txt

i have a working rom for raspberry pi 1, 2 and 3. the only issue im having is getting the wifi and bluetooth to work. any suggestions?

How to install it ?

Badfiler said:
How to install it ?
Click to expand...
Click to collapse
Why install something that isn't working?

[OBSOLETE THREAD] Rooting LG G4S (H735)

[OBSOLETE THREAD]
This thread is obsolete. A solution was found, which is posted here:
http://forum.xda-developers.com/g4/help/method-to-root-lg-g4s-model-h735-lg-g4-t3248030
Please use the new thread for discussions.
------------------------
Original thread:
------------------------
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Approach 1
I tried the method posted by konsolen in this thread:
http://forum.xda-developers.com/g4/general/lg-g4s-world-root-lg-devices-t3231759
but it didn't work for me. I tried several times with varying approaches, but the boot process always gets stuck on the LG logo.
Approach 2
I also tried to inject the root as suggested in this thread for the G4:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491
I've used the Inject_Root_G4.zip from this link, which I believe is the same shared elsewhere:
https://mega.nz/#!BIxUzbqI!nt2YnGnGQlSiBQ-Ar-c-q7oDMIEsg6xd0Kmek-q0clg
And I get the same problem - stuck on the LG logo when booting.
For anyone who wants to reproduce Approach 2 to maybe find a solution:
1. Start up LGFlashTool2014. You can follow instructions in thread by konsolen (see Approach 1 above). You can use his .kdz file as well. Important: Pull out your USB cable as soon as the green letters COMX (with a number instead of X) appear on the phone. My flashtool actually didn't display the progress percentage, but apparently this at 9%. It doesn't matter if you don't see the percentage though, I've verified with this KDZ image that if you pull the cable at the very moment the green letters appear, nothing is corrupted. The phone will still display 0%. Leave it as it is after you unplugged the cable.
2. Kill your flash tool with the windows task manager. After it closed, you can plug the phone back in and open a windows command line in the folder where your Send_Command.exe is (you can download the package in konsolen's instructions which contains Send_Command.exe as well).
3. Open the console to your phone with
Code:
Send_Command.exe \\.\COMX.
(with your number instead of X)
You will have to do steps 1-3 every time you want to get this console, for example to run all the dd commands below.
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
5. Keep a copy of your system.img somewhere safe, you can use it to restore your system if something goes wrong. So don't use this original in the next steps!
6. Copy the .img file to a linux system and mount it. I'm guessing who is trying this knows how to do this. Anything you change in the folder you mounted the image on, will be saved in the image. You can then use this updated image to overwrite your original system partition, again with dd (as described in the thread by dominik-p) using your parameters. So here's the crucial bit: You get root access to your system files via linux. When you know the right things to mess with, you can root your phone with the updated image. Injecting the root as done in step 8 is one way to change the system on the G4 in order to root it.
7. [Optional] If you are new to this, you may want to do a simple test before you continue.
Create a testfile (test.txt) on the mounted system partition. Then copy the .img file back to your phone and try to "dd" it back over your system partition.
Then, check if you see the test file on your system partition -- you may have to reboot the phone after the dd command (and log back in with Send_Command.exe) in order to see the updates.
8. Inject root with the Inject_Root_G4.zip on the mounted folder of the image on your linux system. You can follow instructions (Step 2) here:
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
9. Copy the new img file to your phone and "dd" it over your system partition, using your own dd parameters.
10. Reboot the phone (you can also just type LEAVE in the Send_Command.exe console).
Now, it should be rooted - if it worked for you!
If it worked for you, that's great. It didn't for me, it got stuck on the LG logo in the boot process again. So I had to write my original system.img back onto my system partition to get the phone back.
I did get the following errors in Step 8 above, though I did try anyway to use the resulting image. The errors may have something to do with my problem, but it may also be because the inject root is for the G4, not the G4s.
Code:
sudo ./autoroot.sh
cp: cannot create regular file ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chcon: cannot access ‘operatingtable/lib64/libsupol.so’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process64_original’: No such file or directory
chmod: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
chcon: cannot access ‘operatingtable/bin/app_process_init’: No such file or directory
If anyone finds a solution to this, or has any ideas what could be tried, I would be very interested to hear it. I'm new to rooting phones and don't have much experience beyond what I did in the last days.
Cheers
Jennifer

jen.magnolis said:
4. Calculate the dd parameters and backup your system partition into a .img file. There is an excellent guide by @dominik-p for how to determine your individual dd parameters:
http://forum.xda-developers.com/g4/help/how-to-determine-dd-parameters-lg-g4-t3184867
Click to expand...
Click to collapse
Happy that my guide has helped you
As I said here:
http://forum.xda-developers.com/g4/help/rooting-lg-h735-g4-beat-t3192491/page5
Everyone who is interested to inject root must edit the autoroot.sh from the inject.zip and use the correct files from SuperSU
More information about the files:
https://su.chainfire.eu
Maybe you have to use other files. Not the files from the inject.zip
Download the Update-SuperSU zip from http://download.chainfire.eu/supersu
Copy the files you need to the "su" folder of the extracted inject.zip
For information which files are needed read the "update-binary" file from the SuperSU zip.
(located here META-INF/com/google/android/update-binary)
Good luck everyone :good:

Thanks again for the links! I'll try again soon, when I get time for it, and report the results here
By the way, here's the ls -lR of my system.

Ok, no problem, take your time.
I've got also lot of other work to do...
I just read your system.txt (thanks)
According to these lines:
Code:
lrwxr-xr-x. 1 root 2000 13 Aug 24 02:05 app_process -> app_process32
-rwxr-xr-x. 1 root 2000 13588 Aug 24 02:05 app_process32
It seems that the firmware is 32 bit.
More info about your firmware is in /system/build.prop
So you have to take the right lines from update-binary and copy them and edit the autoroot.sh
Please don't ask me which lines. It's a bit difficult... (you have to understand the logic in update-binary)
Then copy the files from the right folder (arm?) to the "su" folder.
Sorry. I'm out now here for the next time. I have a H815 and happy with it.
I think you will find the solution. :good:

Custom Recoverys
Hi All
Are there any custom recovery's for the G4 beat/G4s
Thanks

Thanks dominik-p for your help. Good luck with your other work, don't worry I won't distract you with asking questions You already helped a lot.
benji5688, you can check for official firmware (.kdz file) on this link, pasting your IMEI instead of YOUR-IMEI in the link below.
http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=YOUR-IMEI
I did not find any for mine there, but I did find it on
http://devtester.ro/projects/lg-firmwares/
Which brought me to this link where I could find mine:
http://pkg02.azure.gdms.lge.com/dn/downloader.dev?fileKey=FW703UV132GQAUP7A0ED99N/H73510c_00.kdz
but you should look for your specific model.

jen.magnolis said:
Hi,
I have been trying to root the LG G4S (H735), also known as "LG G4 Beat".
I tried two things:
Click to expand...
Click to collapse
LOL
I did the exact same thing as you, and really the EXACT, I also contacted dominik-p for the same problem you got with the bs. LOL
Was about to do the same thing you did here too just told that to dominik-p lol.
You post is great, well detailled. Hope someone found something
But got something different. my phone is the LGH731 LG G4 Vigor from Videotron in Canada.
If someone need files or system.img LINK
That's not the exact same thing as the post owner but i'm pretty sure the root method will be. (DON'T use this system.img to inject in you H735) it's from a H731 and they don't have the same partition size.

Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers

jen.magnolis said:
Ha, that's funny, and you got the same problem of course (frozen logo boot).
We will find a solution. It's just a matter of time. I'm a bit pressed for work in the next days but I'll get back into it around mid week. I think the main problem was, as I suspected and also as dominik-p pointed out, we've been using the wrong inject files. And the G4s is 32 bit so obviously it won't work with 64 bit libs.
First thing I'll try is using the other files from the link dominik-p shared. I'll also read the guide and try to understand which files need to be changed to gain root access in general, i.e. learn the basics of how to root. Then I think/hope I'll be able to fix this. And finally get to move all my stuff onto SD and get my storage back
Meanwhile, if you get any new results, let me know.
Cheers
Click to expand...
Click to collapse
Yes i'm trying this today (the 32-64 bits thing)

Custom recovery
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji

benji5688 said:
What does this file do though?
Is it a custom recovery or is it the stock rom?
Thanks Benji
Click to expand...
Click to collapse
It's the stock ROM. It can be used for recovery, depending what your problem is. If you destroyed your ROM by trying to root, you can recover with this.
If you mess with something in your system partition (where the Android OS is installed), you'd need a copy of your individual system partition (like a "backup") to restore. This highly depends on your phone/version, so you have to do this backup yourself. You can follow the instructions with the dd parameters, linked to from the main thread.

Are there any custom recoverys
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help

benji5688 said:
Hi
Are there any custom recovery available, I want to get Xposed.
Can anyone make one?
Thanks for all the help
Click to expand...
Click to collapse
I far as I know to get Xposed you need to be rooted... Well there is no root method availaible, well you can try the methods that Jen explained here but I doubt they will work... if yes, you lucky ****

Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app

larsdennert said:
Is the g4s running marshmallow? Is so you would need to use a compatible su install.
Sent from my VS986 using XDA Free mobile app
Click to expand...
Click to collapse
No the problem is really just changing the 64 bits command to make then use the 32 bits ones
I manage everything except this one
Code:
chcon --reference=operatingtable/bin/app_process32 operatingtable/bin/app_process64_original

I agree with xsteacy, this will most likely not work, that's why we opened this discussion
We just have to find the right files to use (instead of the 64 bit ones).
I will get back onto the subject by Wednesday when I have time.

I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!

jen.magnolis said:
I solved it! My phone is rooted
I asked someone to test my script before I post the results. Hang on there, tomorrow I'll post the solution.
Good times!
Click to expand...
Click to collapse
0.0 OH!?

Ok I'm putting it out there for others to test as well.
Please report if it worked so I can take this into account before updating the main thread instructions.
In the attached .zip file there is a README with instructions.
Note: Thanks goes to @konsolen who shared instructions on how to open the COM port on the H735.
The script in konsolens post is essentially the upater-binary script of the SuperSU package, but with a few modifications.
That may have been necessary on konsolens phone, but it didn't work on mine. For me, using the original script worked.
However, the zip file has to be extracted manually with busybox before the updater-binary script is started. I am not
sure if busybox absolutely needs to be in the /sbin folder, but that's where I saw elsewhere that it belonged, so
I moved it over there in my script. I haven't tested this with busybox being elsewhere.
Thanks goes also to @dominik-p for sharing the link to excellent documentation and for his instructions on how
to make a backup (with dd) of your system, in case anything goes wrong.
UPDATE: I did all commands in root_lgh375.sh manually when I found it already worked, so please report if all is good with the script, but I think it should be, it only does what I did manually.

Congratulations @jen.magnolis
Well done