yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] letama:
Difficult to say, there are so many cause for not booting...

I'd suggest to try something simple at first to make sure your process is ok, like for instance modifying CM initramfs and check if it still runs after repack :) You can simply add a comment to init.rc for instance and check that it's there after boot.
[Sony Xperia S, Acro S, Ion] lozohcum:
I don't have those directiories, I have

Data (empty)
Dev (empty)
Proc (empty)
res (has charging graphic)
sbin (has none of mentioned above files, no ramdisk)
sys (empty)
system (empty)

and bunch of standalone files

what now? I want to replace zImage with mine, compiled from source.

I tried to decode other bin files but program failed.

Oh, I see it's if I want to edit ramdisk.

I don't want to edit ramdisk, I just want to add kernel I compiled from source.

So I should exe command like this?:

mkelf.py -o new_kernel.elf zImage@0x00208000 sec1-0x01400000.bin@0x01400000,ramdisk sec2-0x00000000.bin@0x00000000,rpm

Those were my outputs:

... dumping sec0-0x00208000.bin
... dumping sec1-0x01400000.bin
... dumping sec2-0x00000000.bin
... dumping sec3-0x00000000.bin

I run that command and now I have new_kernel.elf file ( 5,8 MB ) but I am afraind of flashing it into my device. Is it safe if everything went without errors?
[Sony Xperia S, Acro S, Ion] letama:
What device is that ?

Basically, what you're trying to do is almost good, but I'm pretty sure sec2 or sec3 are not rpm.

Can you give me the sizes of each sec-xxx file, the size of the elf, and the size of your zImage ?

Regarding your last question, no, it's not safe for something else than XS/AcroS/Ion...
[Sony Xperia S, Acro S, Ion] letama:
And one last thing, can you tell me what displays sksplit when you unpack the elf ?
[Sony Xperia S, Acro S, Ion] lozohcum:
[MENTION=834547]letama[/MENTION]

It's Xperia J. Kernel is compiled from official source given by sony developers.

Here are sizes:

And split log:

ELF magic found
Entry point : 0x00208000
Program Header start : 0x34
Program Header size : 32
Program Header count : 4
-> PH[0], type=1, offset=00001000, virtual=00208000, phy=00208000, size=4310432
-> PH[1], type=1, offset=0041D5A0, virtual=01400000, phy=01400000, size=1313163
-> PH[2], type=4, offset=0055DF2B, virtual=00000000, phy=00000000, size=512
-> PH[3], type=558778707, offset=000000B4, virtual=00000000, phy=00000000, size=1072
... dumping sec0-0x00208000.bin
... dumping sec1-0x01400000.bin
... dumping sec2-0x00000000.bin
... dumping sec3-0x00000000.bin

So how other people compile kernel for this device? FXP has their own CM10 kernel, Rachit Rawat made his kernel based on open source given by sony developers too.

And this is my repo:

https://github.com/lozohcum/Kernel-JLO-JB
[Sony Xperia S, Acro S, Ion] letama:
Ok, Xperia J is different SOC, it doesn't have rpm.bin

cat you do a cat sec2-0x00000000.bin ?

I suspect it's kernel command line.

If I'm right, you should try this first:

mkelf.py -o new_kernel.elf sec0-0x00208000.bin@0x00208000 sec1-0x01400000.bin@0x01400000,ramdisk sec2-0x00000000.bin@0x00000000,cmdline

And try to flash it. It will be the same kernel, but at least we can be sure the extraction and rebuild is working.

If everything is ok, you can do this:

mkelf.py -o new_kernel.elf zImage@0x00208000 sec1-0x01400000.bin@0x01400000,ramdisk sec2-0x00000000.bin@0x00000000,cmdline

This time it will be your kernel...

*edit*

I found this regarding your device, a bit more complicated than working with sin and elf like here, but it kind of confirms what I said, basically he does manually what sksplit does.
[Sony Xperia S, Acro S, Ion] lozohcum:
Are you asking if I can do this?

root@lozohcum:/home/lozohcum/android/buildpackage/dir# cat ../sec2-0x00000000.bin | gzip -d | cpio -i --make-directories

gzip: stdin: not in gzip format
cpio: unexpected end of archive

as you see I can't, same with all other bin files. I can cat only the one you mentioned in tutorial.

I'm going to try what you said, I hope it won't birck my phone.

The tutorial you found is freaking me out...

After I exed

mkelf.py -o new_kernel.elf sec0-0x00208000.bin@0x00208000 sec1-0x01400000.bin@0x01400000,ramdisk sec2-0x00000000.bin@0x00000000,cmdline

There is a new_kernel.elf which is 0.2MB lighter than the first one...

I'm like

omgomgomg

I flashed that kernel and it works pretty well.

Now I am going to use kernel I compiled and if it works I will add some governors and OC
[Sony Xperia S, Acro S, Ion] letama:
No, simply

cat ../sec2-0x00000000.bin

This is probably text file.

:) I know, it's a bit complicated, but that's because he doesn't have sksplit and sin2raw. He does that manually, by dumping flashed kernel first then finding the right location.

That's ok, you don't have Sony signature, and you shouldn't have it.

Good! Method is working then, let me know if your own kernel works.
[Sony Xperia S, Acro S, Ion] lozohcum:
Operation successfull! Kernel I've compiled works.

Thank you very much for help, you restored my faith in people on this forum :)

Carrying on, here is an issue. After installing it, my phone is laggy, even very laggy. On the previous kernel my phone was very fast and smooth.

Do you have maybe any advice?

what about patch from this thread? Where can I read about removing rubbish from kernel and etc?
[Sony Xperia S, Acro S, Ion] letama:
Nice!

Ok, so now you have the method. Regarding kernel, well, I don't know why yours is laggy. Maybe a toolchain issue, what are you using to compile it ? I usually use Google toolchains. Depending on kernel version, I use gcc 4.3.3 or 4.6.0. You should check dmesg on stock kernel to see what version Sony used (third line or so in dmesg will show you kernel version and toochain used).
[Sony Xperia P, U, Sola, Go] Erkaft95:
Hi there!

I make a zip file which include all Xperia Jelly Bean files and install it to ICS.

Instructions:

1. Download attachment zip file

2. Boot CWM

3. Flash zip

4. Reboot

5. Extract from the zip system/apps/com.sonyericsson.home.apk

6. Turn on unkown sources

7. Install the extracted file and now complete.

You have full Xperia JB Style! :)

Mods:

Statusbar: http://xdaforums.com/showthread.php?t=2157195

http://d-h.st/Yod

Screenshots on the link! :)
[Nexus 7 (2013) Q&A] playboi:
any help is appreciated.

flashed with the latest gapps, tablet is showing only 11 gb total. Not sure what to do.

http://xdaforums.com/showthread.php?t=2391779
[Nexus 7 (2013) Q&A] rkennison:
16 gig model? If so.. that's correct. The device has 16 gig of memory total. That is before any OS / Petitions / Etc... ALL storage devices are like this. Format a 500g HD and see what your left with even before the os, not 500g.

Keep in mind too that what your reporting as 11g, is actually just the free space on THAT partition. There are several others you don't see.
[Nexus 7 (2013) Q&A] playboi:
32GB sorry should have clarified.

it was reporting 24gb on startup of stock rom.

holding down on vol + pwr doesn't work anymore, just pops up the cyanogen mod logo.
[Nexus 7 (2013) Q&A] goofball2k:
Did you dirty flash? or do a wipe and then flash?
[Nexus 7 (2013) Q&A] playboi:
wipe/flash, flashed stock rom and it still shows up with 11 gb.

?
[Nexus 7 (2013) Q&A] comminus:
Since you've already wiped everything and data loss is not an issue, run

fastboot format userdata
fastboot format cache

That should resolve it. Note for anyone else: this will entirely erase the contents of /sdcard.

Edit: I just remembered that running factory reset from settings>backup & reset has also been reported to fix this issue, but I can not personally confirm it.
[Nexus 7 (2013) Q&A] playboi:
Thanks!
[Xperia Z Q&A, Help & Troubleshooting] Buddingdev:
Device : XZ ( Rooted and bootloader unlocked )

I have a weird problem here, when ever i flash a custom ROM my phone no more charges it shows charging though ( but stays in the same level even after 1 hour of charge ) ;( i am not sure if it is some thing related to undervolt or overclock . please help..I guess this problem started after flashing Kernel, i overcloked it to 1670 some thing, and after that it never charged.

And weird thing is it charges so fast on stock ROM with Root.
[Xperia Z Q&A, Help & Troubleshooting] :
yup the kernel

kernel is connection between hardware and software

so bug in kernel can cause hardware issue

try another kernel or stock kernel

it s not about usb port or charger, it s about that phone cannot use charger & usb

:good:
[Xperia Z Q&A, Help & Troubleshooting] Buddingdev:
yes should be

Great Info :o Thanks a lot ..

Now firstly i have used Carbon ROM on day 1 and it was all fine that day and al of a sudden next day it doesn't charge :/ not sure wat the prob is :o
[Xperia Z Q&A, Help & Troubleshooting] zomer331:
Yeah, I have this problem with Carbon too, so I am going to flash stock ROM & kernel I hope it will be help.

Have You tried it already>??
[Xperia Z Q&A, Help & Troubleshooting] Buddingdev:
yes I did

Its too late :P actually issue was my usb cable which my hamster bite and I didn't notice it ..btw !! I switched to note 2 now, I loved sony a lot bt had so much trouble wit that so switched and I gotta to say note 2 is a beast ..;)
[Xperia Z Q&A, Help & Troubleshooting] zomer331:
Ough, good to know! :) yeah, I thought about change too.

But for now I think I found the fix for slow charge, when I connect phone by USB to laptop, on notification bar I switched the option from USB phone connection from MTP as mass storage to PTP as camera storage and phone charge much faster now. :)

How much You paid for sgn2? If I can ask? :)
[Xperia Z Q&A, Help & Troubleshooting] Buddingdev:
wow :o I hav never known this , so how long does the charge last ? did you try 4.3 carbon ROM didn't get a chance to use :/

yes yo can :P This is maa sisters phone so exchange my phone wit this :D beast battery man last for a day wit 3g use <3
[Shield Android Development] shimp208:
Unofficial OUDHS Recovery version 1.0.3.6 for the Nvidia Shield

Testers Greatly Appreciated! To test you can boot it rather then flashing it through fastboot with the command: "fastboot boot thor-oudhs-1.0.3.6-unofficial.img"​

Flashing Instructions

1. Download the above file.

2. Move the downloaded recovery file into the directory where you have ADB and Fastboot setup on your computer.

3. Navigate into the directory where you have ADB and Fastboot setup on your computer and run the following commands from the command prompt on your computer:

adb reboot bootloader
fastboot flash recovery thor-oudhs-1.0.3.6-unofficial.img

Congratulations you now have OUDHS Recovery version 1.0.3.6 running on the Nvidia Shield.

Credits: shabbypenguin for developing the OUDHS source code and for being an excellent mentor!
[Shield Android Development] wwjoshdew:
Sweet! Thanks for this. I'm going to unlock my shield next week, and I'm going to be making several tutorial videos on it.

I just got 3 years of SquareTrade warranty, with Accidental Drop Protection. So if I root it and I break it, I can still get it replaced.
[Shield Android Development] agrabren:
I'm curious... Never seen this recovery before. What does it offer that CWM doesn't? Or is it just a different recovery?
[Shield Android Development] shimp208:
OUDHS Recovery is based on CWMR sources and the full source code can be found here. It has some mortification for user interface and also it has a unique way of handling it's touch driven interface that's designed to make it compatible across a wide range of devices.
[Shield Android Development] agrabren:
Ok, cool. Just trying to decide if I should switch from my current CWM recovery over to this. Doesn't sounds like there's much of a difference.
[Shield Android Development] shimp208:
I haven't fully analyzed the OUDHS source code for all the changes that were made (It's on my to do list :good:) the main difference between your CWMR (Nice job on that by the way) and this is the touch interface that's really the main difference between them.
[Shield Android Development] agrabren:
None of the touch is working on my device. And navigation is a real pain with only one of the two buttons working (home acts as up). Have you tested this at all?
[Shield Android Development] shimp208:
For the touch issue I think I have ran into the same issue you were having with getting touch working on TWRP for the Shield. The unit I was going to test this on (Which is actually my friends who is still on vacation) I don't unfortunately have access to currently.
[Shield Android Development] agrabren:
Issues found while using it:

No touch support

No controller navigation

Screen is rotated 90 degrees

I didn't try anything else, since I'm not really willing to risk my device to test backup/restore. ;)
[Shield Android Development] shimp208:
Thanks for letting me know about these issues I will see what I can do about these and hopefully issue more test builds shortly :good:.
[Shield Android Development] chaind:
Neither the touch nor the D-Pad on the controller is functional.

Only 2 buttons, Home to scroll up & Shield button : functioning as OK.

The said gestures are not working.

As Agraben said. :)
[Shield Android Development] shimp208:
Always glad to have multiple people confirm what is and isn't working I intend to get more test builds out as soon as I can :).
[Shield Android Development] chaind:
Will be glad to help you with the testing!...
[Shield Android Development] Uvfriend:
Install from SD didn't work.. I did not have SD card in the shield but it did not let me access internal memory of shield either.
[Shield Android Development] yoyoshooter:
thanks:laugh:
[Shield Android Development] Ksehwail:
Do you think I could use this on my evga tegra note???? Sorry to bother just can't seem to find info in English about this device thanks....
[Shield Android Development] shimp208:
This is meant for the Nvidia Shield only. However if you can provide me with your devices stock recovery.img or a link to where I can find it I can try and compile recovery for your device.
[Shield Android Development] Ksehwail:
Thanks for the quick response I will try to find the recovery ima before the day ends... Thanks for taking the time to help... I should be able to find the recov.IMG... I have the Evga note do you think the recovery.IMG for the superfly one tegra note would suffice??
[Shield Android Development] Ksehwail:
Sorry for the noob question but is there a way to pull the recovery.IMG from my device?? Thanks in advance
[Shield Android Development] shimp208:
Is the superfly one just a re-branded regular Tegra Note 7? What you can do is fastboot boot (NOT FLASH) the superfly image to see if it works. I saw your other question thread if you can get root access on your Evga Tegra Note 7 then you can pull it's recovery.img.

Yes there is a way to pull your devices recovery.img, but it requires root access (Make sure you have root access on your device first. First reboot your device into recovery mode and wipe your devices cache then reboot the device into the Android OS. Then from terminal emulator or ADB shell please run the following command and upload the result of the following command:

su
cat /cache/recovery/log

This will allow me to determine which partition on your device is the recovery partition that you need to dump. As always if you have any questions let me know I'll be happy to help you out :).
[Shield Android Development] Ksehwail:
OK last question before I flash the boot.IMG do you know if it's OK to use the IMG from the fly one since it is the same device just different manufacturer as you mentioned,.. Thanks

Edit: after rereading your response I saw you said to fastboot not flash.... Can you run the command by me I'm a bit rusty
[Shield Android Development] aDigitalPhantom:
He did post the command...

here is a more specific example of the command to boot an image

fastboot boot image.name

image.name is the name of the image to boot.

If your recovery image is named recovery.img then the command becomes

fastboot boot recovery.img
[Shield Android Development] Ksehwail:
Shrimp208 I have replied to your last message however i am not seeing that it was even sent in my message list sorry for trolling just wanted to make sure the messages went through.... whenever you have some free time will you give me a heads up... Thanks a lot for all the help

---------- Post added at 09:41 PM ---------- Previous post was at 09:40 PM ----------

Thank You for the clarification... I just wanted to be sure
[Shield Android Development] shimp208:
All your messages have gone through okay and don't worry your not bother me I'm happy to help people :).
[Shield Android Development] twistedumbrella:
These are for you bro-seph:

https://github.com/StarKissed/roth-recovery-oudhs/commit/d387bc0c69c75760b60b4e0d80f4275d45193c15

https://github.com/StarKissed/roth-recovery-oudhs/commit/241f856014018b67b71de2ec067176cccbfbb387

I'm feeling like Sandroid Clause. I am still looking through stuff, but it seems I have a little downtime.
[Shield Android Development] shimp208:
Thanks man I appreciate it, I was hopping to take a look at things but also have had very little time but thank you Sandroid Clause for your presents ;). The original post has been updated with version 2 of the recovery image that hopefully fixes some of the problems people were having earlier, as always any testing feedback is greatly encouraged and appreciated :).
[Shield Android Development] twistedumbrella:
No problem. I stole the first part from the CWM decompile I did and the second was taking apart the SuperSU archive. I didn't test any of it, though, but it sounded like the right thing to do haha.
[Shield Android Development] roustabout:
Is the boot.img file from an update.zip file which is described as being the tool to use to recover a device in an emergency actually a stock recovery?

If so, the HP slate 8 has one and it's just about a poster child for OUD... :)

(sez he who's seeing how much of the T7 / shield work is applicable, unloved or not... turns out: quite a lot!)
[Shield Android Development] shimp208:
The boot.img file (Your devices stock boot image) found in your update.zip and recovery.img (Stock recovery image for your device) are two different things one contains your devices kernel (boot.img) and the other is used for recovery mode (recovery.img). Are you asking if someone can compile recovery for your device?
[Shield Android Development] roustabout:
I was looking to see if I had a copy of the recovery to share. But yes, if someone knows how to do a recovery for the platform that'd be great. Otherwise, it's possible I'll sound it out eventually :)

I tried

fastboot -i 0x03F0 boot thor-oudhs-1.0.3.6-unofficial-v2.img

downloading 'boot.img'...

OKAY [ 0.374s]

booting...

OKAY [ 0.016s]

finished. total time: 0.390s

but when I got back to the GUI, there were no files in /cache/recovery/log

Recovery mode on the device is minimal - there are no commands available, even the minimal ones I'm used to seeing with a stock recovery - so clearing cache before I started wasn't an option.

If /proc/mounts or /proc/partitions would help ID the recovery partion I'll post those.
[Shield Android Development] shimp208:
First off make sure to never flash anything that is not meant to be flashed on your device, the recovery image in this thread is for the Nvidia Shield not the HP Slate 8. Is your device rooted? Because if it is I can guide you on how to to dump your recovery.img that can be used for compiling recovery.
[Shield Android Development] roustabout:
Whoops - the oem unlock format is partial. The kingsoft-installed su persisted, so I could see the device booting in response to fastboot flash, but when I actually read the script on the github, I realized it was erroring out after the script asked the device for its name.

I am rooted, though :)

yes, I rooted using the tegra note root.img and fastboot boot.

Am I correct in thinking fastboot boot does not flash an image but instructs the device to boot from what's coming in over adb, somewhat analogous to pxe booting?

I hope so, or else I'm just crazy lucky :)
[Shield Android Development] Sess:
does this recovery flash OTAs?

the original CWM port stopped working and seems to have been abandoned...
[Shield Android Development] SkylerZio:
trying to test boot with

fastboot boot thor-oudhs-1.0.3.6-unofficial.img

but it just sits at booting downloaded image, or whatever it says at the fastboot menu

about how long should it pause there?
[Shield Android Development] shimp208:
I used the device name thor rather then then roth when compiling this recovery, so OTA's will most likely not work, I unfortunately do not own a Shield and my friend who owned a shield that I used to test it on sold his.
[Shield Android Development] shimp208:
It shouldn't sit there longer then 10-15 seconds I would power off the device. Reboot back into the bootloader and use fastboot to try and flash the image again.
[Shield Android Development] SkylerZio:
2 more attempts, and 2 more lock ups...?

See, the funny thing is I used it before and actually installed it the first time, and it worked great (I loved it BTW! Good work!) But then I restored a stock official image and now I'm having this problem. Granted I didn't yestboot the first time, and didn't actually install this time. Does that give you any ideas?
[Shield Android Development] shabbypenguin:
Imagine my surprise when i get an email asking for help fixing oudhs recovery on a device i knew we never ported it to. glad to see it impacted people enough that they wanted to spread it, however i was the only one from the team pushing changes to the source (and dhacker was nice enough to kick in a few) so i gave up trying to keep up with selinux and 4.4 changes etc. plus all of the cool features in oudhs have been merged into regular cwm now. so for teh sake of moving forward i would highly suggest just using mainline cwm, the swipe controls are in there as is rainbow mode :)

regardless just so im clear, screen is rotated, the joypad doesnt work? at all in recovery? or does it work in the key test function? if it does then you just need a custom recoverykeys.c mapping them. anything else i forget?
[Shield Android Development] twistedumbrella:
The keypad mapping is standard Android gamepad maps. 108 - Start, 109- Select, A, B, X, Y, Dpad are all standard too.

It's a landscape device, so the view just needs a 90 degree offset.

It's a lot of silly stuff that people coming from phones never really had to consider when porting stuff before. I'm pretty sure the documentation wasn't there at that time either.
[Android Q&A, Help & Troubleshooting] albinoium:
Hello. In have a Horizon H900D without HDMI out. Please tell me how to connect it to the TV or monitor. I tried with a microUSB to HDMI cable but it don't works.
[MDA III, XDA III, PDA2k, 9090 General] dhruvkataria:
Hi

I have the following softwares installed :-

1 Spb Pocket Plus

2. Phone alarm

3. Spb weather

4. Agile Messenger

5. Phone Plus III

My dear blueangel slows down considerably.

They all are on the rom...

My question is :--

1.Are these to heavy for the angel

2.How does it matter where I install it ( rom / card )

3.can some programs from startup be removed to increase speed of boot / functioning/.

Pls advise

regards

Dhruv
[MDA III, XDA III, PDA2k, 9090 General] KTamas:
a) 1.40 ROM itself slows down the device, at least for me, use 1.31

b) Today plugins (PocketPlus, PocketWeather for example) not recommended to install into the ROM

c)SPB PocketPlus can cause hangups on Phone Edition devices, especially with SD-card monitoring
[MDA III, XDA III, PDA2k, 9090 General] dhruvkataria:
Hi

Do we agree that 1.40 is a slow rom ....

I thought that was the best rom available in the and 1.13 radio was the best it could get .

What abt battery pack as a task manager and pda utility software.

regards

Dhruv
[MDA III, XDA III, PDA2k, 9090 General] CWolf:
I found a good solution:

Switch by www.hfrmobile.com

Free taskmanager. Has the great "Close all" option for when to much is running.