Develop Bugs

[DISCONTINUED][GSM][04.09.11][ALPHA] Honeycomb port by [DiP7]

Since Spacemoose has a GSM release approaching, I'm going to remove the download links here. (Also because apparently people are still attempting to flash this...) If and when I am contacted by DiP7 I will reopen this thread and add any links he wants me to add.... Or it can stay closed and he can start a new one (which is what I would hope he does.) I'm leaving the rest of the content here for reference only.
**READ ENTIRE FIRST POST BEFORE FLASHING**
This is an Alpha build. Almost nothing works at the moment. Don't expect a golden daily driver... This aint it. If you find a download link throughout this thread, don't flash it, as I can't promise anyone will help you un(soft)brick your device. ​
Let's start this with : I take zero, zilch and no responsibility for anything you do to your device using anything from this thread.
If space alien ninja cows come down and eat it because they want to taste honeycomb, your fault, sorry.
There have been zero reports of anyone "hard bricking" their device, but again, I'm not responsible if you become the first.
I also take no credit for any of the work, I've only compiled what I have found so far.
I also can't stress this enough... This is a VERY EARLY STAGE of the port. ALMOST NOTHING WORKS. Any updates that take place will need to be documented within this post. I'm willing to keep track of all this, but *I AM NOT A DEV.* The original dev of this port is from another website, dsf767 seems to be in contact with him however. here at XDA!
**Please see bottom of this post for change log**
Various vidoes have been made, but the quality of this one is really nice. Thanks museboy!
This is a direct port of Spacemoose's Alpha v.040211 release. Not much works.
In Spacemoose's thread, credit is given to
[*] A russian-language GSM port attempt based on this project. (Thanks, dsf767.)
Click to expand...
Click to collapse
It appears as though someone DiP7 is attempting to port Spacemoose's project to a GSM device. They also appear to have had mild success in doing so, and I'd like to start a thread to track and follow any progress anyone else may be having with flashing this rom/kernel.
[*] System must already be converted to EXT4. This can be done by various methods, flashing the Overcome rom/kernel will do it.
[*] Tab confirmed to charge while off and reports of lockscreen charging have been made.
I'm unsure if anyone has had any success other than the OP Cal-El has gotten it to boot! Directions appear to be as follows:
BACKUP EVERYTHING. Everything? EV-ER-Y-THING. Especially your internal SD card. There have been reports (that I've experienced) of your internal SD card getting wiped in either going to or coming from Honeycomb. (It usually requires a repartition to go back... so yeah, that'd do it.)
Did you back everything up? You will loose any information on your internal SD card coming back to normal from this build.
Download Rom to EXTERNAL SD:
Download Kernel to EXTERNAL SD:
Did you back up your internal SD card? What about external? Last warning. Next person to complain about their internal SD card get's the bonk.
Wipe Data/Factory restore
Wipe Cache Partition
Wipe Delvik Cache
Flash honeycomb rom using CWM (This seems to have only been tested and confirmed from the Overcome modified CWM, although any should work in theory.)
Reboot into new RED CWM.
Flash kernel using RED CWM
Reboot into new ORANGE CWM.
Wipe data/Factory reset
Wipe both caches.
Flash honeycomb rom using the ORANGE CWM.
There is no boot screen after the Galaxy Tab logo screen, just a black screen. Wait at least 5 minutes for it to boot. If it doesn't after 10, something went wrong.
If this fails, attempt to go back to stock by flashing p1_hidden.pit and any of Roto's stock roms/firmwares. From here it has been confirmed to work if you flash the Overcome rom/kernel before moving to the Android 3.0 rom/kernel. (Thanks Cal-El!)
This process must also be used to coming back from this
Honeycomb build. You will loose all information on your internal SD card.
I told you to back it up.
Taken from Alterbridge's Overcome Rom posting (which should fix any hangups while flashing to/from this Honeycomb)​
alterbridge86 said:
IF your Tab does not boot after flashing the kernel and hangs at the Samsung Galaxy Tab screen, you must follow the following procedure
Get a stock rom package (any of Rotohammer's firmwares will work)
Get P1_add_hidden.zip from this post and extract the P1_add_hidden.pit file
Using Odin 1.7, put stock rom (Roto-JME-Full-v4.tar for example) in PDA slot.
Put P1_add_hidden.pit in Pit slot
Check repartition box
Put Tab in download mode by holding Volume Down and Power, connect to the computer, and press start.
After this, the Tab will reboot normally. Shut it down and return to download mode.
Open Odin 1.7 and reconnect the Tab.
In the PDA slot, choose the Overcome Kernel v2.0 tar file for use with Odin. Press start
It will flash the kernel then reboot. Upon reboot, you should hear the sexy robot voices informing you of the status of the EXT4 conversion.
Once done, the Tab will boot normally. At this point you can load Overcome Rom (or any other Rom of your choosing)
Click to expand...
Click to collapse
[*]Remember, No wi-fi, no 3g, no phone calls, nothing. This is a test port. YOU HAVE BEEN WARNED OVER 5 TIMES NOW, no complaining about it later.
[*]If your internal SD card reads ~220 MB after coming from this ROM to anything else, you didn't read my post... Try again.
[*] Mirrors :
*Update on driver work for wi-fi (4/12): http://forum.xda-developers.com/showpost.php?p=12816258&postcount=224 (Thanks DemonGloom for translating)
*Also added video to OP (Thanks to museboy!)

the wife is russian. may attempt tonight when I get home. thanks for the heads up

Just try to make sure that any actual changes to the base system build are reported in the other thread as well so we can all stay on the same page.

This is a brilliant find! Downloading now to test this baby out
Is the rom and kernel in the zip or are there 2 different files to download?
Sent from my GT-P1000 using XDA Premium App

I tried flashing this using the mothod above and the methon on the russian site but I can't get it to work.
It keeps messing up my /data partition. After flashing the ROM CWM always fails to mount the /data partition.
I'm going back to overcome .

I already got a blank screen and then a broken internal sdcard error. Had to find an odin flash that repartitioned.
Ill be willing to do it all again as soon as there is wifi. At least this time I'll make sure to back up my internal sdcard.

-RioT- said:
I already got a blank screen and then a broken internal sdcard error. Had to find an odin flash that repartitioned.
Click to expand...
Click to collapse
Just trying to keep track of this all... Are you saying you got it to run successfully but had to repartition to go back? Or did you have to repartition to get it to run?
Adding in the hidden_pit to the process seems simple enough.
-RioT- said:
Ill be willing to do it all again as soon as there is wifi. At least this time I'll make sure to back up my internal sdcard.
Click to expand...
Click to collapse
Step #1

GANJDROID said:
This is a brilliant find! Downloading now to test this baby out
Is the rom and kernel in the zip or are there 2 different files to download?
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
They both appear to be contained within the same zip file, much like the Overcome rom. Best guess, can't verify as I'm on a work mac at the moment.

btyork said:
They both appear to be contained within the same zip file, much like the Overcome rom. Best guess, can't verify as I'm on a work mac at the moment.
Click to expand...
Click to collapse
Yeah, my mistake. Got confused about the reflash with new kernel/cwm.
So we:
Backup
Wipe everything
Flash
Wipe
Flash
Reboot
Sent from my GT-P1000 using XDA Premium App

There Directions are directly from DiP
Originally Posted by DiP7
- the first step (the file system should already be ext4) - flash honeycomb (Android3.0_by_DiP_signed _narod.yandex.ru/disk/9317202001/Android3.0_by_DiP_signed_040411_235124.zip
- the second step (to flash my kernel dl.getdropbox.com/u/937719/Recovery_install_pda1.4Ghz_CWR_v_2.1.0.zip) go to the recovery and make the wipe data/factory reset
- The third step - go to recovery and flash again android 3.0

GANJDROID said:
Yeah, my mistake. Got confused about the reflash with new kernel/cwm.
So we:
Backup
Wipe everything
Flash
Wipe
Flash
Reboot
Sent from my GT-P1000 using XDA Premium App
Click to expand...
Click to collapse
So far that's what I've gathered, I have yet to actually test this process.
The poster above appears to have mentioned something about repartitioning, which isn't a big deal, just flash the hidden_pit.
My best guess is to flash that pit after the second wipe with Odin. But I CAN NOT verify that.
It seems obvious you would need to repartition to go back though.

I would try and flash it all via cwm, but I'm unable to download the kernel. Can anyone mirror it please?
Away from my laptop for the next few hours so I'm unable to try with Odin.

GANJDROID said:
I would try and flash it all via cwm, but I'm unable to download the kernel. Can anyone mirror it please?
Away from my laptop for the next few hours so I'm unable to try with Odin.
Click to expand...
Click to collapse
Recommendations as to a site to mirror it on? I don't do a lot of hosting.

Here are some Mirrors you can put them in the OP of the Rom and Kernel
ROM: http://www.megaupload.com/?d=RC6WF2PG
Kernel: http://www.megaupload.com/?d=GP58GAOE

Anyone have luck getting HC port running o the tab yet and if so can we get a clear how to in place ?
Thanks in Advance =)

btyork said:
Recommendations as to a site to mirror it on? I don't do a lot of hosting.
Click to expand...
Click to collapse
I'd say Mediafire or Megauload are the best, IMHO.
Big thanks for the mirrors.
For now, FML. Now got 8% battery left *sigh* Ill have to wait for some Honeycomb love.
Sent from my GT-P1000 using XDA Premium App

Updated with Kernel and Mirror(s) for both Rom and Kernel.

clockedtouch said:
Anyone have luck getting HC port running o the tab yet and if so can we get a clear how to in place ?
Thanks in Advance =)
Click to expand...
Click to collapse
The clear "how to" is in the first post... If you can't understand those directions, you really shouldn't be flashing this.

btyork said:
The clear "how to" is in the first post... If you can't understand those directions, you really shouldn't be flashing this.
Click to expand...
Click to collapse
Thats why i dont post much simple remarks like that make members not want to contribute ...
You could of simply stated that the "how-to" was updated .. but thanks for your quick response anyway

clockedtouch said:
Thats why i dont post much simple remarks like that make members not want to contribute ...
You could of simply stated that the "how-to" was updated .. but thanks for your quick response anyway
Click to expand...
Click to collapse
I actually haven't updated the how-to since the original post... It wasn't meant to be rude, it's just how it is. I don't want people bricking a 600 dollar tab because they think this is a fully functional honeycomb port.
You'd also be surprised how many people post that kind of question without any understanding of what ADB even is.

Flashing a ROM won't work

So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?

When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?

cupfulloflol said:
When you say, won't work what do you mean?
Does the recovery not flash the file? If so, what error does it say?
Does it not boot after what seems to be a successful flash in recovery? Do you see the bootanimation?
Click to expand...
Click to collapse
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.

CheesieOnion said:
It flashs the files and all but it gets into a bootloop. I see the costum bootanimation of the ROM, but it keeps playing and it won't start up. After some time the screen goes black, but it's not off, because if I hold down power it won't turn on so I have to pull battery.
Click to expand...
Click to collapse
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.

CheesieOnion said:
So I wanted to flash the FNV AoSP ROM on my Galaxy Nexus GSM. First off al I flashed the 4.2 takyu version and rooted it with SuperSU. After that I flashed the recovery with Clockwork 6.0.1.5 after that I did the following things:
- Wipe data/factory reset
- Mounts and storage > Format /system
- Wipe cache
- Wipe dalvik
- Flashed ROM fnv_20121119_003_maguro.zip
- Flash 4.2 gapps
Am I doing something wrong?
Click to expand...
Click to collapse
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.

cupfulloflol said:
Your ROM name seems to show that it is a recent build. A quick search around, the last official FNV ROM I see was uploaded in September. The Gerrit, Github, Twitter, and threads here and on another site seem to have been untouched for quite some time.
Of course I am a little out of the loop, so perhaps I am missing something. As devs often post things in IRC, or in other non-official channels. Did you get this ROM from a trusted spot?
That said, it could be a ROM issue perhaps.
Click to expand...
Click to collapse
I got the rom from the topic here on XDA. It is the build from 19 november.
simms22 said:
it probably doesnt need the gapps. try reflashing, but without the gapps. don't wipe anything.
Click to expand...
Click to collapse
In the instuctions in the ROM-topic it says it needs them and I also need them to use.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
In the instuctions in the ROM-topic it says it needs them and I also need them to use.
Click to expand...
Click to collapse
install the gapps from the play store. you can flash without them, besides the ones that you cant get from the play store are included. you can try it, or just stay in your bootloop, its your call.

CheesieOnion said:
I got the rom from the topic here on XDA. It is the build from 19 november.
Click to expand...
Click to collapse
Ah, my bad I didn't realize it was picked up by someone else, I see that now (which I thank you for the heads up that it is back in production). I was just making sure you weren't flashing something that wasn't ready for public use, and that it was a real ROM.

[Q] MoKee random reboots

Hi everyone!
I'm using the latest MoKee MK44 ROM for our Ace.
I really like this ROM but there seems to be a problem with the kernel. It reboots randomly during read or write processes.
Does anybody know something to fix that problem?
I attached the last_kmsg, maybe you can tell me whats going wrong here.
EDIT: It seems that it's not MoKee causing this problem.
EDIT2: I got a solution for the problem, take look at this post.

I haven't experienced that....but if I were to,I would definitely just clean flash ROM again.

I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!

Does really nobody knows something about the last_kmsg? Here are so many professionals and none of you can help?
Attached another last_kmsg, I took it right after a reboot.
Pulled battery, booted to recovery and copied it so I think there aren't many non-relevant events at the end of the file.
Attached file is now zip, maybe you don't like rar, I don't know. Thanks

Vega Bullet said:
I did so, tested several times. Flashed CM11 -> seems to be no problem. Flashed MoKee (no matter if you choose stable or nightly) -> random reboots. When I flash CM11 again I cannot say theres any problem.
Maybe somebody who knows more about last_kmsg can tell me whats wrong.
But thank you for reply!
Click to expand...
Click to collapse
No reboots here

marknoll said:
No reboots here
Click to expand...
Click to collapse
:good:
Ok, tried clean flashing once again, still the same result.
So what about the last kmsg?

What recovery are you using?

marknoll said:
What recovery are you using?
Click to expand...
Click to collapse
TWRP 2.7.1.0
Used the latest 4ext before that but had some problems, so I changed to twrp which works better I think.

Use the mod twrp jriors... That flashes everything.

marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
So you think it's a flashing problem? Like I said, I think there were no problems (especially random reboots) with other ROMs, that's why I didn't thought it's a flashing problem. But I will try it again.
EDIT: Can you give a link? Would help me saving some time

http://forum.xda-developers.com/showthread.php?t=2780164&page=4

marknoll said:
Use the mod twrp jriors... That flashes everything.
Click to expand...
Click to collapse
marknoll said:
http://forum.xda-developers.com/showthread.php?t=2780164&page=4
Click to expand...
Click to collapse
Well...
Vega Bullet said:
TWRP 2.7.1.0
Click to expand...
Click to collapse
I didn't know if "jriors" one is a special version but that is exactly the recovery I am using.
I got it from that thread, not from the mirror on page 4 you linked me to but from his first post.
So this would not change anything. Please correct me if I'm wrong.

All I can say is that maybe u got a bad download. Redownload the ROM and check md5. Then flash it with jriors. Should work fine then

Ok, looked for the checksums, matched.
And again, does really nobody know anything about the kernel log file? No idea? No clues?
I'm testing latest CM11 once again, maybe I find something...
EDIT: Tested under same conditions. Same problem with CM11. So I think an app or setting is causing it.
Would be very helpful if someone can take a look into kernel log.

My advice is to factory reset from recovery. Then go under advanced wipe and chose cache, dalvik,android secure and system wipe. Then flash the ROM and gapps..reboot after and let it run before logging in play store or installing any apps
---------- Post added at 11:04 AM ---------- Previous post was at 11:01 AM ----------
[/COLO
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
Can I plz have the link you're getting this ROM from? I think that maybe ur downloading an incompatible rom

I'm sure I do the procedures correct, tried simple factory reset (with recovery) and additionally wipe /system and android secure too.
Download ROM from here, look for checksums, flash boot.img separately.
But now, even if I only use it like it's been flashed, I'm getting reboots. Not only reboots. It seems that everything isn't correct.
Freshly flashed, want to reboot device normally but hangs during reboot dialog or bootloops...
Currently I'm testing the first ROM flashed the DHD with, CM11 OnePlusOne Edition and
THAT Rom seems to work. No reboots, hangs or bootloops, very confusing...
So it's getting very difficult to help me, no pattern I can follow to get out what's wrong
I thought Titanium Backup was the problem but like I said, even if it's clean it doesn't work.
Well, I will test everything again, let's see.

Are you s off?

marknoll said:
Are you s off?
Click to expand...
Click to collapse
No, thought of it but I was to lazy to read me through all the things I have to do,
flashing original ROM and what I have to keep in mind and so on...
Maybe I will try it but my time is also limited.
In the last_kmsg you can read that right after "rebooting in 5 seconds" there is "BUG: scheduling while atomic: htc_ebdlogd..."
I simply deleted the file htc_ebdlogd (because I don't know what else to do) and rebooted, seems to be no problem without that.
Till now the problem does not occurred. Till now..

Same problem on CM11 M9?
I think I'm having the same problem with CM11 on my Ace. I installed it this afternoon and have had random reboots on multiple occasions. Can't find a pattern for when it occurs. I don't have a logcat log from when it happens yet, but I'll try to obtain one.
My phone is S-ON (only HTCDev unlocked) and I used the TWRP 2.7.1.0 from [1], the CM11 M9 build from [2] and the PA GApps Modular Nano package from [3]. I installed by:
In TWRP:
1) Wipe (should wipe everything right?)
2) Install CM11 zip
3) Install PA GApps zip
Then flashed the extracted boot.img from fastboot.
I'd be very interested in hearning if deleting htc_ebdlogd really worked for you Vega Bullet.
Cheers,
Elvis
[1] http://forum.xda-developers.com/showthread.php?t=2780164
[2] http://forum.xda-developers.com/showthread.php?t=2533007
[3] http://forum.xda-developers.com/showthread.php?t=2397942

The kernel log is located under /proc named last_kmsg
For now it works fine let's but I don't really know if there are any consequences nor if it works.
EDIT: After a few days of testing a can say there are no reboots anymore, I am using MoKee MK44 for Ace and it's working fine.
Although I still don't know about consequences I can't say there are any but you do it without warranty.
So if you experience the same error
(means random reboot,
look into /proc/last_kmsg,
you should see the line "BUG: scheduling while atomic: htc_ebdlogd..."),
make a nandroid and delete htc_ebdlogd (should be located in /system/bin).
Btw, looking at the MoKee Source I only see one reference to this binary, it's located under ramdisk/init.spade.rc .
Maybe someone know's more and what it's good for, like I said without it I don't see differences...

[Q&A] [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]

Q&A for [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [lt03wifi][P600][ROM][CM12][5.0.2] Temasek's UNOFFICIAL Build [v3.3]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Hi guys I did try it on my p601 and its ecelent
thought its easy just exported my modem on old p601 and tried to import it but I didnt make the trick
some other developer did mods for p601 then p600 maybe they can give a hint what else need to be done on a p601
ACTUALLY I use xkat 2.0 that developer did first an p601 and downgraded then a p600 version
would have no issue to use my device as p600 but get only internet by 3g

To get 3g to work requires a new device tree you can't just import your modem there will be a lot of files that need to call specific hard ware files, etc to get the 3g to work. I wish it was as simple as that
Sent from my SM-N9005 using Tapatalk

Does this Rom Have any Spen Support? Can anyone confirm?

cm12 how do i remove the mouse cursor?
As the question really. I am an artist and need to remove the onscreen mouse cursor when spen is used. I don't use an external mouse so dont mind losing it entirely.
Any ideas how?
Many thanks

My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?

WILDrBEAST said:
My P600 will come in the mail within a few days.
I've spent a few days (4) reading through the forums before posting my very first questions on xda......
1. Is this rom based on RaymanFX 12/18 build?
2. Would clean flashing version RaymanFX 12/5 then dirty flashing Temasek's UNOFFICIAL CM12 BUILD fix the camera force close?
Click to expand...
Click to collapse
I don't have the camera issue,i dirty flashed like you are intending to.

Dirty flashing will fix the camera issue as in dirty flashing guy rom over raymanfx build or the nexus experience ... Some reason from source code the camera is not working. I want to build regular cm to check what portion I am missing (if any) of correct sources. I know what the error is from the logs however I fix one part and another crops up so I think there is something missing
Sent from my SM-N9005 using Tapatalk

Thanks!
I also think that this rom ir best of best.

Can anyone confirm pressure sensitivity is working? I cant find an answer, I read that spen is only a pointer so that does not work for drawing apps that use pressure?

My P600 came FedEx today and I'm ready to root and flash.
Should I update the device from P600UEUCNI1 to P600UEUCNK2 to get the latest KK recovery before I start? (if the 2 newer updates even makes changes to recovery).
I am getting the update prompt though it doesn't say which build.

The recovery shouldn't matter it will get flashed over with a twrp build anyway...
I am not up to date on the root ability of the newest bootloader as my device was rooted when I got it stock and I don't recall updating bootloader at any stage
Sent from my SM-N9005 using Tapatalk

problem when flashing
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault

patrykket said:
Im tryingto flash youe rom, but during the file's verification in recovery mod, the device fails and after 2 tries is just force closes aand reboot on touchwiz. Dont know where I made my fault
Click to expand...
Click to collapse
Sounds to me that you are having problem with twrp recovery I had this when flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk

joshndroid said:
Sounds to me that you are having problem with twrp recovery I had this whdden flashing on any other recovery other than 6.3.3.3... What version twrp are you using
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
Click to expand...
Click to collapse
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]

patrykket said:
2.7.4.5 the newest one avalaible on googlemplay
---------- Post added at 11:20 PM ---------- Previous post was at 10:48 PM ----------
Im actually trying the version you told me. But not to use it, but to install it. The zips doesnt want to be installed, .img too. Cant you send me the installation file (and eventually the whole file) on my mail?
[email protected]
Click to expand...
Click to collapse
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/

joshndroid said:
your a bit hard to understand.
to flash it correctly you need to use odin and not the img flash tools, etc from the market. These tools can cause problems and can flash to the incorrect partition block for the device.
none of the TWRP zip files on their website ever seem to work for me, so i have also flashed these things manually because to many times i have been left with no recovery or back to stock recovery. Manual flash is always better.
you need an .img.tar file - here is the direct link from twrp website for lt03wifi (note 10.1 wifi only model) - https://goo.im/devs/OpenRecovery/lt03wifiue/openrecovery-twrp-2.6.3.3-lt03wifiue.img.tar
this needs to be flashed with odin, i would suggest read here first - http://forum.xda-developers.com/gal...08-2013-odin-3-09-odin-1-85-versions-t2189539
within this there is a further guide on how to use odin, the link of odin iteself can be obtained here - http://www.andromint.com/download-odin-latest-version/
Click to expand...
Click to collapse
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.

patrykket said:
I'll try to be clearer.
Actuallynit's the forst time I'm trying to work with roms etc. Actually I feel a little lost. I managed to install Odin on my computer (tried 3.09 version) managed to root my device. But the problems that I have occur from there. What do you meam by manually flash your rom, why do ypu ask to use tpwr if you tell me now it never works. And where do I need to download the cyanogenmod's rom file? On mu tablet, sd card or on my computer? I don't wan't to say this tutorial how to get the cm installed on ypur device is unclear, but as a newbie, I encountered some difficulties.
Thx for everything.
Ps. I took a looknon every link u sent me, but it didnt really help me.
Click to expand...
Click to collapse
Please re-read my previous post.
I did not say manually flash rom, i was talking about the RECOVERY which is the TWRP recovery by using ODIN.
Please have a good read through guides, if the ones i linked don't help you try googling, there are plenty others. There are videos on youtube showing how to flash files/recovery using odin.
Please read as much as you can before starting, because when it goes bad no one is going to be able to fix it for you. As much as it is at your own risk i wouldn't like to see someone's hard earned money turn into a paperweight.

Tell me please, working s-pen?

The GPS is not working for me on this rom, heres what I did...
Step 1:
I flashed TWRP 2.6.3.3 with Odin 3.10,
Made a backup with TWRP,
Cleared Cache,
Cleared Dalvik,
Cleared Data,
Flashed cm-12-20141205,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Step 2:
Flashed cm-12-20141218,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test Works, so does Navigation.
Made a backup with TWRP,
Step 3:
Flashed cm-12-20150104 v4.2,
Flashed gapps,
Flashed SuperSU,
Restarted to UI.... GPS Test does not work, neither does Navigation
Also tried "Step 3" with cm-12-20150103 v4.0 AND cm-12-20141231 v3.8 with the same result.
THIS ROM ROCKS! VERY SMOOTH AND FAST!!
Could this be a simple fix? did I take any incorrect steps?

[Q&A] [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-

[Q&A] [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-
Q&A for [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-2015
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][SM-T217S/NK1] Negalite WondeROM T3E | Mods | Xposed | Performance | 1-2-2015. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

negamann303 said:
You need to be on nk1 firmware and use Cwm recovery
Click to expand...
Click to collapse
My tab was completely stock till today, all i did was root it and flash this

(No longer relevant)

TWRP question?
Hi all, Just wanted to give a big thanks for the work being done on this. I thought it was going to be washed up but it has been
revived ! Thanks again
Now here is what I'm wondering.
After taking the NK1 firmware, I rebooted and Odin the recovery from #2 TWRP
- Noticed in the new recovery it has a message that says "E:unable to mount / firmware" and "E: error sending message to add(or remove) storage 65537" . Is there something else I should be clicking on more?
I basically flashed the ROM as I normally would when I was running the older version of TWRP for a clean install.
I was wondering if all this is normal or did something fail to install when I did my Odin?
thanks again and like I said so far its been running great !!
Z.

Hey guys I cant get my wifi to turn on after clean install

kashis32 said:
Hey guys I cant get my wifi to turn on after clean install
Click to expand...
Click to collapse
Did you double check ur firmware? I upgraded 2 NK1 @ first but only 2 of the 4 (pda csc) updated and the baseband and bootloader didn't @ first. Had to Odin back over again now all r NK1. I use the Samsung phone info app to double check. Try that and make sure u do a full clean install. Well that's what worked 4 me.
Z.

Any update on broken wifi? i am on nk1 so idk why it doesn't work.

zsibisi said:
- Noticed in the new recovery it has a message that says "E:unable to mount / firmware" and "E: error sending message to add(or remove) storage 65537".
Click to expand...
Click to collapse
I have the same errors... So far it doesn't seem like it has affected anything though. The only issue I have is the battery seems to drain a lot faster than on stock nk1.
This is actually my first time flashing a rom so idk if maybe it was one of the options I checked in the beginning or not. I chose the unsecured adb kernel so maybe I'll try the stock kernel and see if the errors or battery thing change because I don't really know what the difference between them is.
---------- Post added at 05:17 PM ---------- Previous post was at 05:09 PM ----------
Tijaun said:
Any update on broken wifi? i am on nk1 so idk why it doesn't work.
Click to expand...
Click to collapse
Hey like I said in my other post this is the first time I've flashed a rom so I don't know much. But when I started this I had to flash stock nk1 and apparently I flashed the wrong version because my wifi wouldn't work even in stock so I then flashed a different stock nk1 and everything worked and continued to work when I flashed this rom.
So what I'm trying to say is maybe you need to flash a different stock nk1 again and see if that works?

Any thoughts on improving battery life? Seems stock had better performance than this ROM. Other than that i love this ROM and will keep it as my daily driver. Buttery smooth and no force closes.
late,
Coz

cozboogie said:
Any thoughts on improving battery life? Seems stock had better performance than this ROM. Other than that i love this ROM and will keep it as my daily driver. Buttery smooth and no force closes.
late,
Coz
Click to expand...
Click to collapse
Try deleting /etc/init.qcom.post_boot and restarting. That's where most of my performance tweaks are. If it saves battery, let me know.
As for recovery. The /firmware mount error doesn't matter. TWRP is the only recovery that doesn't recognize it. I'll just comment it out for next release (already using TWRP 2.8.4.0 on my tablet [emoji14])
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so

negamann303 said:
Try deleting /etc/init.qcom.post_boot and restarting. That's where most of my performance tweaks are. If it saves battery, let me know.
As for recovery. The /firmware mount error doesn't matter. TWRP is the only recovery that doesn't recognize it. I'll just comment it out for next release (already using TWRP 2.8.4.0 on my tablet [emoji14])
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so
Click to expand...
Click to collapse
Deleted suggested file....device "feels" snappier....I'll keep an eye on battery life.
late,
Coz

negamann303 said:
As for wifi issues, I'm about to release my kernel on you guys, give me a day or so
Click to expand...
Click to collapse
When I flashed the rom it gave two options for the kernel one said something like "nega unsecured adb" the other said "completely stock". I figured the one that said nega was you're kernel and the other was the tablets stock? Am I wrong on that and what is the difference between them?

Level47 said:
When I flashed the rom it gave two options for the kernel one said something like "nega unsecured adb" the other said "completely stock". I figured the one that said nega was you're kernel and the other was the tablets stock? Am I wrong on that and what is the difference between them?
Click to expand...
Click to collapse
The version in the Rom just has an edited ramdisk for unsecured adb is all

@negamann303: Thank you for a fantastic rom. It's great to see some renewed interest in the T217S. I discovered it last night, read through both threads, updated firmware first and then flashed your TWRP, rom and themes. Everything is running smoothly. Looking forward to your TWRP update just to hide those firmware error messages.

I had this problem after flashing the recovery zip. Tried both TWRP and Philz with both reporting thd same.
Next question, how do change air gesture options. I made some changes when I turn the option on. Now I can not find Motion or any option in settings to edit or change. What am I missing? ???????

So I just flashed the new recovery and the firmware error is gone but when I flashed timberwolf's theme (atleast I think it was after the theme but I definitely got the error) I still got the "E:error sending message to remove storage 65537" error. But after a quick Google it turns out you have to turn off mtp in the recovery to fix this issue.
The twrp thread here on xda explains it and also tells you how to disable mtp in twrp.
http://forum.xda-developers.com/showpost.php?p=58224851&postcount=102
wingman358 said:
When you first enter recovery, go to the "Mount" menu then on the lower right side it should say "Disable MTP". Click it to disable and you shouldn't get the error if you go and wipe after doing that.
It's not persistent so you'll have to do it each time you restart the recovery and want to do a storage wipe.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse

Okay, so I guess I haven't been following this thread as closely as I thought. I didn't realize we were at v2. Downloading now. Can I dirty flash? Any plans to use SVN? If I need to do a clean flash, I will then have to re flash the kernel and theme, right? I remember SVN was a life saver before because Nega is like a mad scientist....always tinkering. Also, I have never learned how to back everything up for clean flashes. Do I go they the whole setup every time like a pilgrim. Titanium bckup is mystifying to me.

GAPO said:
Okay, so I guess I haven't been following this thread as closely as I thought. I didn't realize we were at v2. Downloading now. Can I dirty flash? Any plans to use SVN? If I need to do a clean flash, I will then have to re flash the kernel and theme, right? I remember SVN was a life saver before because Nega is like a mad scientist....always tinkering. Also, I have never learned how to back everything up for clean flashes. Do I go they the whole setup every time like a pilgrim. Titanium bckup is mystifying to me.
Click to expand...
Click to collapse
If you are using Titanium Backup Pro, I created a screencast video for my phone that shows the right way to create an update.zip file that you can flash from recovery immediately after doing a clean install. I also tried it on my Tab 3 with no problems.

Ramer said:
If you are using Titanium Backup Pro, I created a screencast video for my phone that shows the right way to create an update.zip file that you can flash from recovery immediately after doing a clean install. I also tried it on my Tab 3 with no problems.
Click to expand...
Click to collapse
Thanks! A couple of questions...when I apply the update.zip, will it have trouble re installing apps that I got from sources other than Google Play store? I mean, is it storing the apps to re install from the zip, or re-downloading them from the play store? Because I got some of mine from other sources.

GAPO said:
Thanks! A couple of questions...when I apply the update.zip, will it have trouble re installing apps that I got from sources other than Google Play store? I mean, is it storing the apps to re install from the zip, or re-downloading them from the play store? Because I got some of mine from other sources.
Click to expand...
Click to collapse
No trouble at all. It's creating the update.zip from the apps that you chose to backup, their coming from your phone tablet, not the Playstore.