yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

For this data line

/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /rdata ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0 wait,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

nothing to delete or change, right?

And what happens if I delete data=writeback wait for other lines? Just curious cus I'm... you know :)

EDIT:

For EMMC and HSMMC, the outcome of modifications doesn't have either, so would be the same, I guess.
[Samsung Galaxy Nexus] dlhxr:
add a r before data and make the mount point as /rdata.

delete the check part of data mounting because we have no system partition mounted before. The check command will search /system/bin for an e2fsck to check whether the data mounted correctly.

and you don't need to change other things in this line.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

I don't get what you said.

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#/dev/block/platform/omap/omap_hsmmc.0/by-name/system /system ext4 ro,noatime,noauto_da_alloc,barrier=0,data=writebackwait
/dev/block/platform/omap/omap_hsmmc.0/by-name/efs /factory ext4 ro wait
#/dev/block/platform/omap/omap_hsmmc.0/by-name/cache /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0,data=writeback wait,check
/dev/block/platform/omap/omap_hsmmc.0/by-name/userdata /rdata ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0 wait,encryptable=/dev/block/platform/omap/omap_hsmmc.0/by-name/metadata

Didn't I aleady do everything correctly including all of the things you mentioned?
[Samsung Galaxy Nexus] dlhxr:
Yes. fstab.tuna is ok now. You don't need to edit other things in fstab.tuna.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

Now, for creating img files for img boot, the first command gives me

sh: can't create 500.img: Read-only file system

How do I give it the permission?

Edit:

nvm. I was dumb. I was doing it on root. Silly me :D
[Samsung Galaxy Nexus] dlhxr:
mount -o remount rw /system

or

/data

I don't know where do you want to put your img file....

I recommand you put it to /data/media/rom/ directly.

did you run in root? please type su first to acquire root permission
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

nvm... I already edited the post right before you posted your last one. I was doing it on the root of my phone. I don't know why :)
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

The best place would be in a folder inside data. /data/media works but root data prevents any kernel from applying permissions to it recursively. Ironically they treat internal storage like a regular card where permissions are locked.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

When I

mke2fs -FT ext4 500.img

it says the image is too small. I don't want to agree with it, but I do because 500B seems small even to me.

I did -FT because it says 500.img is not a block device when I did -T.
[Samsung Galaxy Nexus] twistedumbrella:
export sysimage=`busybox du -s YOUR_ROM/system | busybox awk '{ print $1 }'`
busybox dd if=/dev/zero of=WHERE_TO/500.img bs=1k count=$sysimage > /dev/null

Always the right size ;)
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

its okay. That's why im a noob. If no one were noob, being a dev would not be as fun as now :), would it?

Does YOUR_ROM meam a flashable zip for a non-1st rom or what?
[Samsung Galaxy Nexus] twistedumbrella:
It means extract the folder somewhere and point that to it. The command gets the file size of a directory and sets it as a variable to determine the size of the image. I have to double check, but I'm pretty sure it's in KB or that may need to be edited slightly.

Edit: Nope, it's good. 1k units. It may have a "." at the end, though, so

export sysimage=`busybox du -s YOUR_ROM/system | busybox awk '{ print $1 }' | busybox sed -i 's/.//g'`
[Samsung Galaxy Nexus] antonio8297:
R: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03/

I have chmod 2nd.img but nothing

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] dlhxr:
About the u-boot.

Some kernel is not compatible with the u-boot, which lead to an strong green color on galaxy nexus....

I find out it is related to the android_cmdline and something about mms_ts.panel_id.

Any idea? Or what does this mms_ts.panel_id mean?
[Samsung Galaxy Nexus] twistedumbrella:
[KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03/31]

https://android.googlesource.com/ke....0-mr0/arch/arm/mach-omap2/board-tuna-input.c

The bootloader provides a panel_id to specify which display/touch panel hardware board is in the device.

I highly recommend anyone doing this read the *original* uBoot thread. I found some amazingly useful info over there to make this easier:

Make a boot.scr.uimg from it and push it to the correct location.

Code:

setenv bootargs "mem=1G vmalloc=768M omap_wdt.timer_margin=30 mms_ts.panel_id=18

no_console_suspend console=ttyFIQ0";

setenv loaddaddr 0x82000000;

setenv devtype mmc;

setenv devnum 0;

setenv kernel_part 0xc;

setenv kernel_name /media/boot/vmlinux.uimg;

echo Load Address: ${loaddaddr};

echo cmdline:${bootargs};

if ext4load ${devtype} ${devnum}:${kernel_part} ${loaddaddr} ${kernel_name}; then

bootm ${loaddaddr};

exit 0;

elif ext2load ${devtype} ${devnum}:${kernel_part} ${loaddaddr} ${kernel_name}; then

bootm ${loaddaddr};

exit 0;

else

echo failed to boot custom image;

fi

This means you don't even have to keep modifying uBoot itself. Make one and then plug in scripts to change what it does.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

The first command gives me

sed: -i requires an argument

and some things that is doing the command

Second one gives me

dd: invalid number ''

and some things proceeding the command

I don't see any difference after the commands. Are they done correctly?
[Samsung Galaxy Nexus] twistedumbrella:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

Ill look it over then. I have a couple things to fix first.
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

Hey if you are online, can you upload an partition image for image boot somewhere? I will make some later when I get correct commands for on phone, but I just wanna try it out quicker. Thanks
[Samsung Galaxy Nexus] Zittoro:
Re: [KERNEL] [U-boot]Dual-boot Powered by U-boot and Custom Kernel[Fully Working] [03

There is no phone call connection for toro. Any idea?

EDIT: Quad-boot version modified by dlhxr can't detect /data/media/boot/2nd.img

I pressed and held volume down right before google logo appeared. Did I do it wrong?

EDIT: Actually, it was finding for

/media/boot/2nd.scr.uimg

when I looked at the log.

Why does the instruction tells to put if in /data/media/boot/2nd.img?
[Samsung Galaxy Nexus] dlhxr:
It firstly looks for the 2nd.scr.uimg for boot script and then 2nd.img.

here is some images made by me.View attachment IMGs.zip
[Samsung Galaxy Nexus] twistedumbrella:
You don't mount data as data, so referencing a file in data doesn't work.
[Samsung Galaxy Nexus] Zittoro:
How do you make a boot script?
[Samsung Galaxy Nexus] twistedumbrella:
http://xdaforums.com/showthread.php?p=39415222
[Samsung Galaxy Nexus] Zittoro:
Thx. Can I also get a boot script from a kernel or do I have to make one for each?
[Samsung Galaxy Nexus] twistedumbrella:
They are designed to replace the uboot configuration. You really only need one for each way you want to load a kernel. The 3 or 4 uboot methods in the op would be one uboot and 3 or 4 sets of boot scripts.

It really useful in that you only install uboot once and then you can swap out those files instead of having to reinstall everything, or worse yet, recompile.
[Samsung Galaxy Nexus] Zittoro:
I made one using what the op of your link tells, but it says

mkimage: can't stat boot.scr: No such file or directory

Is it done successfully? and how do you edit the boot script like the "sample custom boot script" from the link's op?
[Samsung Galaxy Nexus] dlhxr:
Please use desktop linux... The mkimage is for i686, not for arm. So you can't do this on your phone.
[Samsung Galaxy Nexus] Zittoro:
I did it on windows with windows version of mkimage. I know I can't do it on my phone.
[Samsung Galaxy Nexus] twistedumbrella:
Your best bet is to look into a virtual desktop. For doing the script images you need to use the one in the u-boot tools folder and that's linux/Unix only.
[Samsung Galaxy Nexus] Zittoro:
https://github.com/Ksys-labs/uboot-tuna/tree/master/tools

mkimage.c or mkimage.h ?

or can you give me a link?

Sent from my Galaxy Nexus

EDIT: with mkimage.c,

mkimage -A arm -O linux -T script -C none -a 0x84000000 -e 0x84000000 -n android -d boot.scr boot.scr.uimg

gives me the same thing, which is

sh: can't stat boot.scr: No such file or directory

when I do it in Ubuntu 12.04 native.
[Samsung Galaxy Nexus] dlhxr:
It is the mkimage binary in the 'tools' folder of the source of uboot, neither mkimage.c nor mkimage.h. :)

You can download it from my repository of u-boot.

https://github.com/dlhxr/uboot-tuna
[Samsung Galaxy Nexus] dlhxr:
I am so careless... I correct the data mounting script~:laugh:

And I am back, finished the GMAT exam. HAHA!:laugh:
[Samsung Galaxy Nexus] Zittoro:
Still...

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ericko.samudera:
Hello, first of all thanks for your hard work. I finally can dual-boot with multiple kernels in my phone, thanks to your instructions.

However, there's something weird with my phone.

I used both your prebuilt kernels:

Dual Boot

GN_U-Boot_Kernel.zip

and

An image boot kernel based on learnkernel 6.2 for 4.2

2nd_image_boot.7z

to run Paranoid Android as my 2nd ROM.

However, after booting to PA:

The colors are a bit off, it's reddish.

The minimum screen brightness are too bright. Way more bright than it's supposed to be.

My 1st ROM is also affected by this.

Then I read that I need to add "mms_ts.panel_id=18" while repacking. So i unpacked both your prebuilt uboot kernel and 2nd kernel and repacked with "mms_ts.panel_id=18" command. However the problem still persists. Did I do wrong somewhere?

Thanks again for your help :D
[Samsung Galaxy Nexus] wkwkwk:
I have the same problem, adding mms_ts.panel_id=18 didn't seem to help.

Thanks
[Samsung Galaxy Nexus] dlhxr:
Fine... Download it from here and make sure it is executable.View attachment mkimage.7z

It works both on lastest AK kernel and Leankernel. I tested them by myself. I made an easy sript for this. Please see post #1.

See the easy script in post #1. Did you forget the blank before the mms_ts.panel_id=18?
[Samsung Galaxy Nexus] twistedumbrella:
You have to make everything with the argument. The kernel has to be packed with it, the script has to include it and be packed with it, and uboot has to have it in the ANDROID_CMNDLINE variable. One of them is missing.
[Samsung Galaxy Nexus] wkwkwk:
Thanks. I tried the script but it's the same. The colour doesn't seem to be an issue but the brightness is way too high.

The kernel in question is the 1st one and it's Franco R300 (for Android 4.1.2).

Thanks
[Samsung Galaxy Nexus] dlhxr:
I'll try to figure it out, but I don't know the reason for this till now....

Sorry, maybe try another kernel?
[Motorola Droid RAZR] hansip87:
Flash This with Custom Recovery, this is based on 982.124.14.XT910.Retail.en.Au. Any bug please give me feedback :)

EDIT: I decided to merge this thread into my other thread. Please visit here
[Motorola Droid RAZR] bigbalaboom:
Hi hansip87, this is working but have you noticed the extra space at left of the status bar?

Changing android:paddingLeft, android:layout_width and android:maxLength to 0 only removes the carrier name, but the extra space is still there. (see screenshot)

Any thoughts on how to remove it?

_
[Motorola Droid RAZR] romdroid.:
I would also like to know how to remove it
[Motorola Droid RAZR] bigbalaboom:
well, I did it.

I added a negative margin to the @id/statusIcons to shift it to the left (see screenshots)

-30.0dip is a bit too much, -27 might be exact the same as the space at the right.

so far so good. but I'm not quite sure if it's intended to be left for other purposes.

_
[Motorola Droid RAZR] williamlaw:
then i should flash 1.1 ?? (i am using DeOdexed rom)
[Motorola Droid RAZR] romdroid.:
can u please upload zip?
[Motorola Droid RAZR] bigbalaboom:
Here is the modified version of the 1.1 Total Black Notification Header Odexed by hansip87.

I just added a negative margin to remove the extra space, nothing else was changed.

Let me known if it works for you.
[Motorola Droid RAZR] romdroid.:
Thanks just flash it with bmm right? I am om 982.124.14 retail EU, should it work?
[Motorola Droid RAZR] BrainChecker:
Yes, it works great! Im also on this version.

Thanks a lot for this...some carrier-names are sooo long, I only saw two or three other symbols beside them :good:
[Motorola Droid RAZR] romdroid.:
Well it worked but now its not showing any notification at all :laugh:

any way to revert it back?

---------- Post added at 07:39 PM ---------- Previous post was at 07:26 PM ----------

Warning...dont install the latest .zip from this thread, it will break your notification system. restore with this .zip http://www.mediafire.com/download.php?6z5tvk36h2nkjfc

thanks hansip
[Motorola Droid RAZR] bigbalaboom:
Yes, 982.124.14 retail EU. Just make sure you have the odex file as well since this is an odex version (apk + odex).
[Motorola Droid RAZR] romdroid.:
it didnt work for me, all my notifications was gone not only the carrier name :( had to restore.

I am odex (I think because I have never touched my system)
[Motorola Droid RAZR] bigbalaboom:
Are you sure that you are using the odex version (apk + odex)?

If you are using the deodexed apk and the odex file is removed, you'll probably get errors.

I have no problem with the modified apk, notifications are showing correctly.
[Motorola Droid RAZR] romdroid.:
I downloaded your zip from here and flashed with bmm http://xdaforums.com/showpost.php?p=42391470&postcount=8

I think I am odex because I have never deodexed my system. Only stock system + root. Your zip broke my notifications, dont know why. I had to restore.

if u have any suggestions please tell

---------- Post added at 09:26 PM ---------- Previous post was at 08:31 PM ----------

Anyone with a solution? Did I do something wrong?
[Motorola Droid RAZR] bigbalaboom:
Notice the screenshots I posted here, I had the battery mod as well. I thought I did something wrong with the modified apk, but no, nothing wrong with my apk or zip file.

I just restored stock SystemUI.apk and services.odex, and then applied the zip file I uploaded with BMM, the carrier name and space are gone.

Notifications and other icons are shown properly.

Maybe you'll need to wait for someone to test my zip file.
[Motorola Droid RAZR] romdroid.:
Very odd I am on 982.124.14 retail EU rooted and with bmm (I put the zip file in external SD and flashed) the carrier name was gone but the problem was that the notification system broke and nothing was show anymore (I had battery widget reborn which was installed and not its gone also sms notifications was gone) idk why...:confused::crying:
[Motorola Droid RAZR] williamlaw:
is this file supported on DeOdexed rom ??
[Motorola Droid RAZR] romdroid.:
Anyone tried bigbalabooms zip with retail.eu jb?
[Motorola Droid RAZR] williamlaw:
could u also modify for Blacker 1.1 ver. ??

thanks
[Motorola Droid RAZR] bigbalaboom:
I compiled both odex and deodex version, try and let me know if they work
[Motorola Droid RAZR] williamlaw:
GREAT and Thanks !!!!!!!!!
[Motorola Droid RAZR] bigbalaboom:
did they work? are notifications and other icons showing properly?
[Motorola Droid RAZR] romdroid.:
yes I would like to know if I am the only one with this problem :confused:
[Motorola Droid RAZR] romdroid.:
edit: I downloaded hansips file and everything is working great now
[Motorola Droid RAZR] williamlaw:
Just tried today, carrier name has been disappeared, but all other icons on left hand side also missed ....
[Motorola Droid RAZR] romdroid.:
Yes download hansip87 mod it's working
[Motorola Droid RAZR] nicods:
Just to be sure, I have JB 4.1.2 Stock European firmware + root.

It's 982.124.14.xt910.Retail.en.EU

Which zip should I use?
[Samsung Galaxy Nexus] pdiggitydogg:
Received the OTA notification on my Verizon GNex yesterday. To make a long story short, as you can probably already guess, I can't turn bluetooth on. Not at all. I revert back to 4.1.1, BT works fine. Push the update from totally stock a second time, and still no BT. Tried it with and without unlock/root privileges.

Ive seen this is a common issue, but there doesnt seem to be a definitive answer on how to actually fix it. Some people have success with a reflash, some people mess with permissions, etc Nothing that Ive tied has worked.

(I am on the 4th reflash at this point, not even caring about my old data)

(really tired of this mtp garbage too)

Who has ideas??

(sorry, wrong forum - requested move)

edit

After 6 attempts of different combinations of roms and radios, I quit. Installed mwalt's mostly stock custom rom (http://xdaforums.com/showthread.php?t=2176954) and everything is fine. No idea what the problem is...
[Nexus 4 Q&A, Help & Troubleshooting] Helderg1984:
Hey I'm new to the forums but been reading them for a while and I just have a question with OTA updates. I have a nexus 4 that's been rooted and have clockwork mod. I have also flashed the .33 baseband on 4.2.2. I have stock rom but Franco kernel however I backed up the stock kernel with his updater app.

I know I can't OTA with the kernel but flashing the stock one is no big deal. Can I OTA with the rest being on there?

Also if I do the lte wifi hotspot fix will that stop the OTA update as well?

Thanks in advance.
[Nexus 4 Q&A, Help & Troubleshooting] Kid_droid:
As long you have clockwork mod on the rom you can not OTA...its always going to be manual way of flashing the OTA and that process will remove clockwork mod but using apps like voodoo keeps you rooted so you can easily install clockwork mod again after the update.

No Recovery+Stock ROM+Stock Kernel+Stock Latest Radio= auto OTA update.

I hope that made sense..but i could be wrong but that's what works for me.

Sent From My Beasty Nexus 4 with Awesome Beats.

ROM: Mysterious AOKP 4.2.2

Kernel: Faux 123 latest tbm.

Recovery: TWRP
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
You CAN ota if you have a custom recovery.

However, the WiFi hotspot fix will kill it.

I made a guide with all the info you need. http://xdaforums.com/showthread.php?t=2145848
[Nexus 4 Q&A, Help & Troubleshooting] Helderg1984:
So if anything is modded at all except for basic root I won't be able to apply the update that arrives to my phone directly right? I will have to flash it in cwm? I assume I will have to wipe cache and such before I apply the zip right?

Do I have to revert anything back stock or can I just flash the zip directly over what I have now and just re apply the kernel and baseband?
[Nexus 4 Q&A, Help & Troubleshooting] Helderg1984:
Sorry one more thing with the latest SU I will stay rooted I think but I will lose cwm and have to re obtain it or will I keep it if survival mode is checked?
[Nexus 4 Q&A, Help & Troubleshooting] steviewevie:
If you flash it from CWM then you will keep CWM and also keep root (if you say yes when it asks you).

Sent from my Nexus 4
[Nexus 4 Q&A, Help & Troubleshooting] Helderg1984:
Sorry I am a bit confused still, when I get the update.zip and flash it in CWM do I have to wipe or no? and if I don't will everything stay the same? or will I lose my 0.33 baseband and kernel? I'm also wanting to do the lte hotspot fix so would I lose that too?
[Nexus 4 Q&A, Help & Troubleshooting] heat361:
You don't have to wipe.It does not matter if you wipe or not, you will still lose your base band, you'll just have to flash the old baseband again. As for the kernel if the ota comes with a new kernel your old stock kernel will be replaced with the new one in the ota.
[Nexus 4 Q&A, Help & Troubleshooting] Rizy7:
You actually can accept a ota update with a custom recovery but you have to be stock everything else, no other mods or anything. The ota will install fine and youll see that it goes through your custom recovery when updating. After the update you will lose root and your custom recovery however unless you recovery someone holds onto it.
[Nexus 4 Q&A, Help & Troubleshooting] spicediablo:
As I know, we need to modify something after installing custom recovery. Else, stock recovery will be installed upon reboot. So even after modifying, OTA still works ?

Sent from Mako
[Nexus 4 Q&A, Help & Troubleshooting] Helderg1984:
So bascially no matter what i have on the phone update.zip will go through fine and put on the phone what it contains and it's up to me to put everything back? Also I've heard mixed opinions if I will lose root and CWM, mostly people say it will give me an option to keep it after applyng the update.
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
Everything about this post is incorrect.

I don't mean to be a jerk but I've seen you post a lot of false info lately. I know you'd like to help, but it only confuses people when they see contradictory info.

Just read the thread I linked earlier. It has answers to your questions.
[Nexus 4 Q&A, Help & Troubleshooting] heat361:
But thats only if he has the lte fix right. So if he just flashes a stock kernel without that patch, the ota could work.

For example the stock boot.img
[Nexus 4 Q&A, Help & Troubleshooting] Helderg1984:
I'm rooted with cwm, custom kernel and old baseband, stock rom. I mean I can very easily revert my kernel back to stock and flash the newest baseband.

The only thing is there's a bunch of stuff I might want to do more but don't want to make it hard to update since it's important to me.
[Nexus 4 Q&A, Help & Troubleshooting] El Daddy:
Yep. The phone needs to be 100% stock with the exception of the recovery to complete the OTA. If the files,kernel,radio, etc. are replaced to the original state you'd be good to go.

PS. Sorry if I came off as a jerk this morning. I had a case of the Mondays. :)

Just as I wrote above, You can do as many modifications as you want, just make sure you bring the phone back to stock before you flash the OTA.zip, otherwise it will fail.

When the new OTA comes out I will update my OTA Help-Desk thread with all the new requirements.
[Nexus 4 Q&A, Help & Troubleshooting] Karlo666:
Just watch this its eazy as 1 2 3!!!

http://www.youtube.com/watch?v=ky5miA8ilr0