yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Original Development] kokero:
HELP

[MENTION=1572963]marco9333[/MENTION] could you, or anyone, help me?

I was using the ROM normally and in this morning BAM, my tablet rebooted and wont turn on anymore. It loads recovery and download mode, but I can't flash nothing, keeps me showing error while flashing!

This what happens when I'm trying to flash the ROM again (after wiping data and everything):

--------------

Installing '/external_sd/Omni/omni - 5.0.2 -20150108 - HOMEMADE - 1.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

(normal till here, but the weird part is now: )

mount: failed to mount /dev/block/mmcblk0p9 at system: Invalid argument

ApplyParsedPerms: remvexattr of system/bin/backuptool.sh to 0 failed: Operation set_metadata: some changes failed

E: Error executing updater binary in zip '/external_sd/Omni/omni - 5.0.2 - 20150108 - n80

Error flashing zip '/external_sd/Omni/omni 5.0.2 - 20150108 - n8000 - HOMEMADE - 1.zip'

Updating partition details...

-----

FAILED

--------------------

The weird part is that I'm unable to flash the ROM, but Gapps and Super User flash normally!

I'm using TWRP v2.6.3.1 and everything was normal with my tablet, ROM and recovery, till this morning

Someone could help me? I'm desperate D':

UPDATE #1: Tried to re-download the ROM and flash trough another SD Card, no change.

UPDATE #2:Tried to flash the old official Omni ROM I was using (4.4.2) (after wiping of course) the log was different, but has FAILED too:

Installing '/external_sd/Omni/omni - 4.4.2 - 20140405 - n8000 - NIGHTLY.zip'

Checking for MD5 file...

Skipping MD5 check: no MD5 file found.

*OMNI LOGO MADE WITH CHACTERS*

Formating /system

Extracting /system

Symlinkig

set_metadata_recursive: some changes failed

E: Error executing updater binary in zip '/external_sd/omni - 4.4.2 - 20140405 - n80

Error flashing zip '/external_sd/Omni/omni - 4.4.2 - 20140405 -n8000 - NIGHTLY.zip'

Updating partition details...

----

FAILED

------------

Upadate #3: I guess the ROM somewhat broke a part of /system partition (I'm not sure, but this is what I guessed by the logs)

So I was thinking, fix permissions doesn't work with lollipop ROMs (Don't know if this could solve) but using -rf instead of formatting can fix /system issues?

And what about I fix permissions and flash 4.4.4, and then, after turning on by the fist time (If it turn on again, or even flash), flash Lollipop, this could work or not? Because I'm not sure if this Fix Permitions option really works in my device, or it could bring some incompatibility with Lollipop (people say it can when you are currently using Lollipop, but I have no idea if I can bypass this problem flashing 4.4.4 and then flashing Lollipop).

Hope anyone could help me, because I think (not sure) this problem is unfortunately connected with the ROM and need to be fixed in next updates (If it really is somewhat connected) :(

Kind regards.
[Galaxy Note 10.1 Original Development] Doscar:
Hello, i am using the version 5.0.2-20150108 for N801x and facing this issue too.

Do you have any idea for why this is happening??

Thanks a lot.
[Galaxy Note 10.1 Original Development] marco9333:
Quite strange actually but I don't think it's a ROM problem since we are using almost the same kernel of omni 4.4 (everything regarding voltages, frequency and other "delicate things" is untouched). Our tablets are starting to show their old age especially regarding storage (I think reading and writing speed is worse then a year before on mine) so hardware failures are becoming more probable. My advice is to try with odin with a full reformat using a stock samsung rom (use formate flag in odin), just make an efs backup before (just in case). If it fails giving you an awful red rectangle with a big "Fail" into it, it's almost surely an hardware failure, if you succeed in flashing a samsung rom then it's just a normal ext4 corruption (when flashing a zipped rom the installer tries to run a backup script).

I can give you a faster solution you can try:

open the zip using something like 7zip

go into meta-inf/com/google/android

open updater-script

delete

mount("ext4", "EMMC", "/dev/block/mmcblk0p9", "/system");
package_extract_file("system/bin/backuptool.sh", "/tmp/backuptool.sh");
package_extract_file("system/bin/backuptool.functions", "/tmp/backuptool.functions");
set_perm(0, 0, 0777, "/tmp/backuptool.sh");
set_perm(0, 0, 0644, "/tmp/backuptool.functions");
run_program("/tmp/backuptool.sh", "backup");
unmount("/system");

save the new file and overwrite the original inside the zip

try to flash the new zip (now it won't try to read the backup script from system partition and it'll format it directly)

Good luck :D
[Galaxy Note 10.1 Original Development] kokero:
Will I need to do this in all ROMs I eventually install?

And about ODIN, I really need the .exe file, cold you upload the one you are currently using, and route me to a tutorial that explains how to use it? I would be very happy :)

(I forget everything about ODIN, since I just used it once abouto more than a year ago)

Thanks, really, gonna try this faster solution of yours and see what happens :D

---------- Post added at 01:09 AM ---------- Previous post was at 12:52 AM ----------

[MENTION=1572963]marco9333[/MENTION] There is none

set_perm(0, 0, 0777, "/tmp/backuptool.sh");

set_perm(0, 0, 0644, "/tmp/backuptool.functions");

run_program("/tmp/backuptool.sh", "backup");

in my updater-script

But there is set_metadata("/system/bin/backuptool.sh", "uid", 0, "gid", 0, "mode", 0755, "capabilities", 0x0); run_program("/system/bin/backuptool.sh", "backup");

Should I delete them?
[Galaxy Note 10.1 Original Development] marco9333:
[/QUOTE]

No you need to do just this time: if you successfully recover your system partition then you will be able to flash them again.

About Odin: since I'm using linux as my first OS I usually use Heimdall. You can search here: there are tons of guides about odin.

EDIT:

Yes I picked up the old updater script: just delete the lines between mount system and unmount system including the line you posted (they should be before the ascii written omni)
[Galaxy Note 10.1 Original Development] kokero:
[/COLOR [MENTION=1572963]marco9333[/MENTION] I got " FAILED " again

Here is the full log:

http://wikisend.com/download/306888/recovery.log

And here is what shows in the screen:

----------------------(grey box)-----------------------------------

E: Mount: Unable to find partition for path '/sdcard'

E: Unmount: Unable to find partition path for path '/sdcard'

Updating partition details...

Full SELinux support is present.

E: TWFunc: :Copy_Log -- Can't open destinatyion log file 'cache/recovery/log'

E: Unable to open '/cache/recovery/.version'

Installing '/external_sd/Omni/omini-5.0.2- 2015 - HOMEMADE.zip

Checking for MD5 file...

Skipping MD5 file check: no MD5 file found

mount: failed to mount /dev/block/mmcblk0p9 at /system: Invalid argument

ApplyParsedPerms: removexa of /system/bin/backuptool.sh to 0 failed: Operation set_metadata: some changes failed

E: Error executing updater binary at zip'/external_sd/Omni/omni - 5.0.2 - 20150108 - n80

Error flashing zip 'external_sd/Omni/omni - 5.0.2 - 20150108 - n8000 - HOMEMADE.zip

Updtating partition details...

---------------------(grey box ends)-------------------------------------

FAILED

What should I do now?

Thanks for helping me till here, really :)
[Galaxy Note 10.1 Original Development] marco9333:
Nothing changed... Are you sure to have delete all the lines (and replaced the original file in the zip)? It's still trying to mount system and load the backup script, that should not happen.

BTW have you tried to format system from recovery before flashing the zip? Under "Mount and Storage" you should find a "format /system"
[Galaxy Note 10.1 Original Development] kokero:
There is no "mount and storage" in my recovery, the main options are Install, Backup, Restore, Wipe (I've wiped sistem trough this option into "advence wipe") Mount, Settings, Advanced, Reboot.

(And I guess I put the wrong sd card sorry :S )

---------- Post added at 02:12 AM ---------- Previous post was at 01:55 AM ----------

[MENTION=1572963]marco9333[/MENTION] unfortunately still showing failed :crying: , but changed a bit(gonna put with the wipe process, so you can see if there is any error on it):

-------------------------

E: Mount: Unable to find partition for path '/sdcard'

E: Unmount: Unable to find partition path for path '/sdcard'

Updating partition details...

Full SELinux support is present.

E: TWFunc: :Copy_Log -- Can't open destinatyion log file 'cache/recovery/log'

E: Unable to open '/cache/recovery/.version'

Wiping Dalvik cache Directories...

Complete!

Formating Cache using make_ext4fs function.

E: Unable to open '/cache/recovery/.version'

Formating System using make_ext4fs function.

Wiping data without wiping /data/media...

Done.

Wiping Internal storage -- data/media

E: Error opening 'data/media'

updating partition details...

Installing '/external_sd/Omni/omini-5.0.2- 2015 - HOMEMADE.zip

Checking for MD5 file...

Skipping MD5 file check: no MD5 file found

E: Error executing updater binary at zip'/external_sd/Omni/omni - 5.0.2 - 20150108 - n80

Error flashing zip 'external_sd/Omni/omni - 5.0.2 - 20150108 - n8000 - HOMEMADE.zip

Updtating partition details...

--------------------------------------------

FAILED
[Galaxy Note 10.1 Original Development] marco9333:
Something is off with your storage... It seems that data partition is not ok too. Try Odin with repartition as last resort. Search around here how to use it
[Galaxy Note 10.1 Original Development] mundodisco:
Lollipop and Nintendo Wiimores compatibility

Can anyone confirm if the issue with Bluetooth stack is fixed under Android 5.0 Lollipop?? (for those who do not know, wiimotes -and many other bluetooth devices- stopped working with firmwares with Android newer than 4.1.2)

I have a Samsung Galaxy Note 10.1 (n8000), and would like to install this firmware...

Kind regards,

GABRIEL
[Galaxy Note 10.1 Original Development] kokero:
[MENTION=1572963]marco9333[/MENTION] I can't find any Odin tutorial that says I should use this option, all of them says that this option will damage my device somehow.

I'm quite noob with Odin and custom ROMs, I just know how to install them, I don't even know how to search for re-partition tutorials in Odin for my tablet, I trow "re-partition Note 10.1 n8000 Odin" on Google, I just can find regular tutorials to how install Recoverys and Custom ROMs in Note 10.1, and all of them warns that I can't use this option, I'm confused :S

I would appreciate that you could indicate me to some tutorial (send me a link for example) to how perform correctly this process, If you prefer, you could send me by private message or though Hangouts.

If you couldn't, that's OK, I just need to thank you for trying to help me when you could till here, and thank you for the amazing ROM you and your team developed, really well made and stable for an unofficial build by the way, was good while it lasted.

Sorry for the inconvenience of asking you how to fix my tablet, really. As is not ROM related, you don't need to help me (even if it was, it's clear in this topic that anything I do with this ROM is by my own risk), I'm asking for help because if I can't fix this tablet, I don't know which one I'm gonna buy, as there are't any other options in Brasil with Stylus besides the 2014 edition, which is pretty expensive for me as a student.

Thanks again for helping me, and sorry.

Kind regards :)
[Galaxy Note 10.1 Original Development] marco9333:
Just follow one of those tutorials step by step. Try with that. If it fails just do not touch anything an add a tick to repartition. Press start again. If it fails again I think you need to use samsung assistance :rolleyes:
[Galaxy Note 10.1 Original Development] manu.augz:
i had similar problems , i let my battery drain and installed kitkat rom using odin. nothing else worked for me !!
[Galaxy Note 10.1 Original Development] kokero:
[MENTION=1572963]marco9333[/MENTION] Well, thanks for the help. Gonna send to assistance, Odin isn't working for me too, tried to flash another recovery with it, and when I rebooted, the old recovery remained there, unfortunately.

And [MENTION=5730361]manu.augz[/MENTION] as Odin seems not to be working for me so I can't even do that, thanks for trying to help :)

If fixing it at Samsung be too expensive, gonna buy 2013 Nexus 7 and a regular silicone Stylus, and be happy with it.
[Galaxy Note 10.1 Original Development] manu.augz:
dude just try with friends computer !! my tab wasnt even booting up, i couldn't even get to recovery mode !! just give it a try :)
[Galaxy Note 10.1 Original Development] arrico21:
Switching Bluetooth devices

Love this rom, but found a weird bug recently.

Started using the tab for audio so I could use viper (cracked note 3 screen and replacement came with 4.4.4 already :( ). When I switch from my headphones when I'm at the gym to my car's navi (or vice versa), I have to reboot to get audio to play. Devices are connected and whatever app I'm using for playback shows audio playing. Any ideas?
[Galaxy Note 10.1 Original Development] marco9333:
Sorry but I haven't got any bluetooth device to test. If you want you can send me a logcat of when you have this problem, otherwise I can't help.
[Galaxy Note 10.1 Original Development] marco9333:
New version up

This is just an update with upstream changes. So expect the same bugs as the previous version. Lots of code cleaning and some changes in core. Expect a better stability, consider this like a nightly.

For N8000 -> I haven't merged all the patches for RIL so the radio part should be almost the same as previous version

Happy flashing

Link in OP, changelog in second post (See gerrit for more infos) :D
[Galaxy Note 10.1 Original Development] saundsr:
It seems, at least for me, the latest update is much much less stable. IThe previous build didn't hard reboot once, and now I'm getting maybe 30 seconds of uptime before a reset. Completely unusable for me.

In other news. One the 0108 build, netflix doesn't work for me nor does the mounting of SD cards. Netflix says it can't connect and my device recognizes the physical removal of an SD card, but when an SD card is inserted it never mounts.
[Galaxy Note 10.1 Original Development] marco9333:
First clean or dirty flash? Second which model are you using? Wifi on or off? Which gapps are you using? And lastly send me a log or I can do nothing since for me everything is ok
[Galaxy Note 10.1 Original Development] saundsr:
Sorry for the lack of info. Wifi on and off. on during initial setup to create account. off the rest of the time, and during the reboots. No problems switching. n8013

initially dirty (exactly according to OP) with SuperSU 2.45 and the minimal gapps 1-19-15 also in OP. first boot went fine. had about 5 minutes. and then a hard reset. after that point i never had enough time to do or change anything.

did a full wipe and tried again, (exactly according to OP) same superSU, same gapps. identical results. first boot fine for about 5 minutes and then the reboots.

I've restored my 0108 backup and the logs for 0205 builds are gone. If i get more time today, I'll give another go and get some logs for you.

Marco, I really appreciate all the work you put in on this. The builds have been great. Guess I might be unlucky with the latest.
[Galaxy Note 10.1 Original Development] marco9333:
Have you checked the md5 of the zip? Try to redownload the rom again. My tab has been up for 5 hours and no reboots (I'm using a n8000). If another person report problems with n801x maybe something went wrong during compilation :confused:

EDIT: Google plus and youtube bug is again in the new version, something is wrong with core sources. I need to check what changes the core devs have made in this last month
[Galaxy Note 10.1 Original Development] saundsr:
Marco,

The MD5's do match. I got burned years ago with a bad download.. Only takes once and you start checking every download. :)

We'll see, maybe I'm the only one. I'll try again today/tonight/this weekend.
[Galaxy Note 10.1 Original Development] pcother:
Hi, I am using an N8010 and loved the January updated and find it quite stable for an early release. Tried the latest build yesterday and it kept causing my tablet to reboot every minute or so, couldnt really see what was causing it as it constantly rebooted.

Any thoughts

PS love the work, please keep supporting this tablet!
[Galaxy Note 10.1 Original Development] old papa sarge:
Hula Plus causes system reboot using 20150206 version. worked fine in previous ver

Samsung Galaxy 10.1 note wifi, N8013

Upgraded to version 5.0.2_r1 LRX22G dated 2015 02 06, Hula Plus Causes a system reboot

went back to 5.0.2_r1 LRX22G dated 2015 01 08, Hula plus works.

note that in the 2015/01/08 file I had to go into Dev Tools, scrolled down to Media section, unchecked Use NuPlayer (experimental) checkbox, for Hula Plus to work in that version
[Galaxy Note 10.1 Original Development] marco9333:
Something is wrong with chromium part: the bugs affects all the apps that use video/audio decoding in web pages: youtube, google+, youtube on chrome. I don't know why this problem is happening again it was fixed a couple of months ago after some updates in the core source code.
[Galaxy Note 10.1 Original Development] Huey_Pilot:
Yep my N8010 also keeps rebooting, I went back to the january version now everything is oke.
[Galaxy Note 10.1 Original Development] phearus:
I've been using your builds on my N8000 for months now. Its great to see the progress - thanks for that and well done.

I've also been holding-off on reporting any bugs as it was still early days... That is until now. I'm not reporting them here as an effort to say "please fix," just as an exercise in documenting what I've noticed. I know that some of these have been reported before, also.

1. Firefox ALWAYS causes a reboot (right back to the Samsung Galaxy Note 10.1 boot screen) when started-up.

2. Chrome sometimes causes a reboot.

3a. Chrome has weird screen glitches - kind of like tearing; lower parts of the display get drawn over higher-up sections (horizontally speaking, in both landscape and portrait). Scrolling up or down seems to sort it out momentarily.

Edit: Found a fix - Disable #enable-gpu-rasterization in chrome://flags

3b. Also with Chrome long clicking / touching(?) links reveals a noisy (as in TV static kind of thing) highlight over / on the link.

4. On boot the home and multitask buttons appear momentarily then disappear forever. Also power button does not trigger the lock screen as it should. As a workaround I use an app that turns the screen off (same behaviour to the power button) to turn the screen off, let it sit for 30 seconds, then the power button to reveal the lock screen, then after unlock the nav buttons remain and the power button behaves as it should.

If I remember correctly, the 4.x series of OmniROM went straight to the lock screen on boot - where your builds do not - maybe this was a historical fix for this problem... I dunno.

5. Screen-off screen rotation bug - this has been previously mentioned here by someone else.

6. ESExplorer causes reboots.

Its worth noting (a pun?!?) that I've NOT noticed a decrease in stability with the 20140206 build, as others have, but an increase in stability and responsiveness - only the web browsers and a few other apps seem to be causing issues. The 20140206 build seem to be improved performance significantly in regards to UI responsiveness. Shame about the reboots though.

This is all I've noticed bad.

What I've noticed good:

- Play Books works well.

- WiFi and GSM seem fine.

- EbookDroid works sweet.

- Hangouts (only Google chat, haven't tried video chat or nothing) works fine.

Hardly an extensive list of activities - but maybe an indication as to why I'm not experiencing as many reboots or decrease in performance as everyone else.

Thanks for all the effort and hard work. Very much appreciated.

Edit: Added another reboot-inducing app - ESExplorer.
[Galaxy Note 10.1 Original Development] MurrayBarn:
Cellular data not working in Feb update

I have the n8000 and just updated from Jelly Bean to this ROM. So far everything seems to be working fine (I havent used every app yet) except that I cannot get cellular data to work. The device connects fine to the network but I get an exclamation mark on the signal strength icon and cannot get it to use data. I saw there was a problem with this in December and just wondering if it is a bug or me doing something wrong
[Galaxy Note 10.1 Original Development] phearus:
I don't know friend. My data seems to be working OK.

Maybe your APN is not set-up correctly, or, you are only in 2G mode? I'm grasping at straws here :confused:
[Galaxy Note 10.1 Original Development] humberos:
[MENTION=1572963]marco9333[/MENTION],

All issues related here I got using new toolchain (4.8) - Exynos3 devices.

I think may the error is memset patches.

I got all issues fixed by returning back the old 4.7 and reverting memset patches.

I think you should consider to build new one with 4.7 toolchain and check all related issues.

[MENTION=3555890]cheers![/MENTION]
[Galaxy Note 10.1 Original Development] marco9333:
Thanks I'm going to try with the old 4.7 :D

By the way I'm trying to port samsung kernel code to kernel 3.10 (taken from google sources). I've already managed to compile most of the core parts (I still need to copy and fix the part about busfreq, after that I should try to boot it). Lots of exynos code (for older exynos models too) is already in that code... I hope to get something functional even if it'll be quite difficult. See https://github.com/marco9333/kernel_common
[Galaxy Note 10.1 Original Development] phearus:
Wow - this is awesome! That will be one epic feat once we are booting and operational!

I have a question - and most likely a very noob android kernel dev question - why Linux 3.10? Is this the kernel version released by google in their aosp or nexus series code payloads? Just wondering - as Linux 3.19 was just released the other day... The google-released kernel code would make sense here though :)

Edit: just reread your post. Google code it is. Still - is this from the Nexus line specifically?

While we are on the topic of kernels - have you seen that the maintainer of cm12 has started using a new kernel based on a new (how new I dunno) N7100 - the Note II (uses the Exynos 4412 also)? Looks interesting anyway and would be even more interesting to see how the n80xx and n7100 specific kernel code diffs look.
[Galaxy Note 10.1 Original Development] marco9333:
Google needs to integrate android specific code into the kernel and this is why android kernel is usually behind mainstream linux kernel.

No it isn't from nexus branch but I'm using the sources in kernel/common https://android.googlesource.com/kernel/common/+/android-3.10.y

Do not expect too much, it's just a test u.u

I know about the new kernel, at omnirom I've read about starting to use it, but it will be a long way :D
[Galaxy Note 10.1 Original Development] malosasha:
Hi Marco

I have seen that most of the commit have been merged; is it already possible to compile 5.0 version from sources for n8000 and having the same base rom as yours ?

Best Regards
[Galaxy Note 10.1 Original Development] marco9333:
Some parts in frameworks_av haven't been merged yet, and some other things here and there. I'll update the commit list in OP since now they are a few
[Galaxy Note 10.1 Original Development] malosasha:
Hi marco

Just as suggestion, is it not best to keep your github forks up to date/synced with you local repo on your har disk; so that one can use local manifest to build the same rom as yours.

I guess you will attract more devs interested in helping building a stable rom for n80xx

Best Regards
[Galaxy Note 10.1 Original Development] humberos:
[MENTION=1572963]marco9333[/MENTION],

we can use this gitspace: https://github.com/n80xx

I will add you as admin member.

feel free to upload what you looking for.