Database Develop

[SOLVED] EU GT-P1000 w/ CM9 RC0: "Signature verification failed"

Dear valued Android and Samsung experts,
it is my first post in this forum. I waited until the flashable ROM etc. was released, so today I tried humbertOS' CM9 (RC0) from 02.02.2012. It is only my second time doing this, after initially upgrading von Android 2.0 or so to 2.3.3.
My Device Info (after wiping, while stuck now)
European SAMSUNG GALAXY TAB (GT-P1000)
Android 2.3.3
Current baseband version: P1000XXJPZ
Current kernel version: [email protected]#2
Build No : GINGERBREAD.XXJQ1
Rooted with Super One Click (Maybe. Can't remember anymore, but it is rooted.)
Installed ROM Manager Pro.
Backed up with TitaniumBackup (Premium I think) to my Dropbox (via Wifi). I hope that is correct this way.
I get the following error:
Finding update package...
Opening update package...
Verifying update package...
E: Signature verification failed
Installation aborted.
Click to expand...
Click to collapse
What did I try to solve the issue?
I redownloaded the ROM.zip, but it didn't help. As there are no md5 hashes available (why?) for the online files, I couldn't compare if there is a problem on my download side. But I used Google Chrome, Internet Explorer 9 and jDownloader now, they can't all be faulty. Of course I re-wiped the cache every time after I had to start the phone or transfer the files!
I read 3+ threads that I found via search, but there was no solution. By the way I was unable to find this forum (Samsung Galaxy Tab) in the forum scroll-down list? Am I blind? I triple-checked! ... In one of the threads I read there I should go go back to the stock version (2.1 or so), is that true? How do I force my Tab to do so?
Now what I think could be the problem source is that I'm wondering why the path /sdcard is showing all the other folders and stuff and why before I put the files on the flash partition of the Galaxy Tab it didn't initially show up! What I try to say is: It seems to me the bootloader accesses NOT the SD-card, but the Tab's flash (all while calling it /sdcard), how can that be!
My SD card is basically empty asides of the ROM, kernel and GApps, but (how) can it even happen that the bootloader choses the internal flash over the SD card?
The last time (2.1 to 2.33) I upgraded I used Odin. This time this is not an option? I only follow the procedure you outlined and ask no questions. I mean in the other thread I read "you will need to flash via odin first because stock rom of gtp1000 have limited options in the recovery mode." (source) - well why is this then not mentioned in this thread or on humberos website? As said, I just followed the directions, thus avoided Odin this time!
And here I read a lot about "Clockwork Recovery", do I really need it? *confused* I mean I already own and payed for ROM Manager and Titanium Backup, should be fine right? I mean it is almost absurd how much I read about it...I can assure you I bought the above tools because back then those were the ones in the talk!
I also heard about "disabling of signature verification", but as it involves a lot of steps, is it really necessary?
I also read about "3e Recovery" but what is that? I would be happy if everyone could stop throwing around with abbreviations that yield no helpful Google results and instead write out and describe what tool or method they use exactly. For the above example my open question is obviously if this recovery method also applies to me with a different brand (Samsung) and model (Galaxy Tab "classic") compared to where I found this method....
Finally do I need to / should I replace my bootloader / recovery menu with another one maybe? ... In conclusion I hope you see I did my research, but there are so many ways to get a solution, so right now I simply need a hint from more experienced pro's about in which direction I have to go!
Thank you for your help in advance!

ClockworkMod Recovery
Ok, I noticed now my mistake probably is that I was missing an installed "ClockworkMod Recovery".
But: When I try to install CWM from within the ROM Manager (v.5.0.0.6, Premium) it only displays a choice of two models - "Samsung Epic4G" and "Samsung GalaxyS i9000" - in the list and not my model (Galaxy Tab EU) or any other model! What is going on there, why does ROM Manager Premium not display an array of other devices?
And is there any alternative way to download and install CWM on my Tab?
PS: The "Euro bootstrap recovery" app mentioned in other threads is not available anymore in the market either.
PPS: I also found this directory full of clockwork builds: http*//download.clockworkmod*com/recoveries/, which one of those would be right for the GT-P1000? The "recovery-clockwork-tab.img" & "*.zip" from 04-Jun-2011 17:37?

The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App

Thanks priyana
Thanks priyana, that hint really made it for me!
Successfully made it through!
Now only the GApps don't show up even though I installed them.
Will browse the forum here and Google for solutions...

reset to factory default and re-install gapps once more?
seems to happen now and then to some flashes

Hey priyana, I didn't update the thread, yes I'm done with that already!
A question though: Is it normal that the internal + external storage show "as one" drive or is the SD card actually not mounting on my Windows laptop? (I assume.)
The problem is, even though I activated UMS with the toggle, I can only put the data on the "12,8 GB" drive, from which I also installed GApps.
But it seems I can't install *.apk files from this location and I also have difficulties restoring my Titanium backup files from there (I put them in the TB subfolder).
So far my progress. I only want my backup back and mount my SD card, then I'm done.

can't help you there yet. I am not yet on ICS
But in slimdizzy's latest built he confirms that both cards visible from windows.
remember one is on /sdcard (internal) and the other is /mnt/emmc (external) because that is CM standard.
One of these days I will follow you guys into ICS.
Tried once earlier before the wifi speed was fixed and didn't like it.

I mean looking from the Windows / PC perspective.
There, I have neither of those paths. I hope that is not unusual.
Another point maybe: As I can't use Kies now, how to manage music? I succeeded in putting videos into the "video" folder, but the same doesn't work for music files (in "Music" as *.mp3 files). Probably I'm lacking the basics (I self-teach them to myself ), so a link to a tutorial about all this is more than welcome. But as said, asides from restoring my backup (I'm still looking for a solution...) and the music issue, all is fine. I even managed to install the apps from within the internal storage with the pre-installed file-manager.

Dont know much about the kies and music.
For TB, there is a setting in there for backup folder.
Have you explore the options?
I can put my my backups anywhere and point TB to it and restore.
Sent from my GT-P1000 using XDA App

Actually, now after another restart it did recognize both the music and the missing TB backup files! I'm really a bit sloppy. Now I'm actually restoring successfully.
Now I will only try to find how to remove a few apps (not selected for restore!) from the backup (job). Apps that I actually don't ever want to see on my tablet again.
I'm sure I'll be able to find out myself...

same problem
priyana said:
The commonly known method is to restock according to Overcome 4.1 rom thread
Then install overcome kernel.
That gives you cwm recovery and it also converts your filesystem to ext4.
Then flash the cm9.
Sent from my GT-P1000 using XDA App
Click to expand...
Click to collapse
please help .... im new to this but having the same problem .n i didnt understand what is overcome n how will it solve this issue..please reply

I have replied the same way many times in this forum too
Here goes again:
Overcome ROM is a GB 2.3.6 custom ROM based on Samsung ROM.
We use it a lot because:
1) it has very clear step by step fool proof way to "re-stock" your TAB in a good clean stock condition, upon which you can then install most ROM
2) its kernel, Overcome Kernel 4.0 comes in ODIN flashable and gives you a CWM Recovery 5.x, which is needed to flash other ROMs
3) When flashed, the kernel performs conversion(and support) of RFS filesystem to EXT4 which is better and faster filesystem. This is sometimes desirable.
Go to overcome site
http://www.teamovercome.net/p1000/
Read the guide,
Missing pictures can be seen here.
http://forum.xda-developers.com/showthread.php?p=20974872
Follow the picture step by step.
But please read it many times until you get what it is saying.
Basically to restock:
Download GB-stock-safe-v5.zip, unzip it and and flash with ODIN according to the guide.
Stop there and you will have Gingerbread JQ1
Next step if you want, just continue following the guide.
Basically flash Overcome Kernel tar using ODIN, and it will reboot and converts your filesystem (you hear female robotic voice).
At the end of it, you get CWM recovery (access it while off : press volume-up and power button)
From CWM recovery you can flash any custom ROM you want.
You will find most of them ask you to flash from CWM.

[Q] i897 dont boot

I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.

kalabazoo said:
I have Samsung i897 Captivate (i9000) with SlimICS 4.1.1 Cyanogenmod installed.
Yesterday morning I've found, that my phone is repeatedly show me boot screen (video on boot with many blinking pieces/elements colors shown to me), but did not load an Android at all. I've tried to reboot the phone (with battery eject), but nothing changes: phone shows start-up animations repeatedly.
Last my action evening before was setting alarm (usual task that I've done for one year probably). Dont know what reason to reboot was, maybe no free space available, but dont sure. Before this problem with load I have no problems with phone at all.
I have Clockworkmod installed, but there's no options to boot an Android in safe mode or some similar options. I could get access to the internal phone memory, but not for system partitions. I've tried to wipe dalvik/cache, fix permissions, but no changes at boot.
So could you gents help me to get access to the filesystem: I have memo's & uncynchronised contacts & SMS, which I would like to save before do anything. I know how to reinstall the system (I have backup for it, but not for contacts & memo's).
Thanks.
Click to expand...
Click to collapse
The I9000 and the I897 are 2 different phones. I9000 is the international version of the Captivate, therefor, if you flashed the I9000 bootloaders on a I897 Captivate, you'll have distorted colors/screen.
What exactly was done to the phone before this happened?

Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.

kalabazoo said:
Pardon, I have AT&T i897 Captivate phone. I did not flashed, nor updated phone, nothing similar, that could affect phone booting process. Just set an alarm (default, from Clocks), then go sleep. In morning found that my phone stuck in boot process - it show boot-up animation but don't load OS.
Click to expand...
Click to collapse
Have you tried re-flashing the ROM (Without factory reset)? Wipe cache and dalvik.

BWolf56 said:
Have you tried re-flashing the ROM (Without factory reset)?
Click to expand...
Click to collapse
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
BWolf56 said:
Wipe cache and dalvik.
Click to expand...
Click to collapse
Yes, did it, but no changes at boot at all (wait there >10 minutes).

kalabazoo said:
No, I'm no so clean understand reflashing process, so worry to lost my data (I know that my contacts lie here - /data/data/com.android.providers.contacts , but can't found where memo's saved). I could choose "Restore /system" from
"Backup & Resore -> Advanced" in CWM, you mean this?
Yes, did it, but no changes at boot at all (wait there >10 minutes).
Click to expand...
Click to collapse
Reflashing your ROM won't touch your data as long as you don't wipe/factory reset. It's what we call a dirty flash, you just wipe cache/dalvik and flash your ROM again with the Gapps.

Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?

kalabazoo said:
Thank you for the way to resolve the problem. Spend some time to understand the process of reflashing. Now I collected all files (bootloader, ROM, essentials, gapps and so on of my actual setup) and ready to reflash it with Heimdall.
But still have a question: is there any possibilities to get access to filesystem (for maybe just copy all files from system partitions into Big Brother) before take action in my case?
Will I get access to my contacts & memo's after reflashing? As I understand, if I reflash phone, /data & /datadata partitions (as part of freshy ROM reinstall) will be touched too, then I lost as minumum link to the Wizard Memo (and I'm not sure that installing it from Google Play will restore access to my memo's).
As you could realise, I have no actual backup of my data, so asking maybe dumb questions (
Could I simple use Clockwork's mod option "Restore /system" & "Restore /data" (as I have it in almost fresh backup - 2 months ago)? Will it be analogue to reflashing? Or it revert /system and /data to the stage when it was make, with contacts, programs and so on with 2 months ago state, not current?
Click to expand...
Click to collapse
I guess i wasn't so clear. What I mean by reflashing is to simply get in recovery mode and reflashing RemICS and their Gapps. Not to start fresh with stock.
Sent from my SGH-I747 using xda app-developers app

You explained well, errors on my side Resolved this issue with copying all data from filesystem, then reflashing with fresh slimrom . For those who fall into same situation: you could get access to filesystem of your phone trough ADB tool, and just copy sensible data to another partition/SD/device. See QtADB program also, very friendly for that.

[ROM][KK][4.4.4][KTU84P] CyanogenMod 11 20140714-UNOFFICIAL

CyanogenMod is a free, community built after-market firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Downloads
Read install directions before downloading or use ^C^V
Latest ROM md5sum: c821ebacaa5c969c55b0a511be8a3933
Current GApps 4.4.4 :: PA
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Installation
Install at your own risk
- First time flashing CM11 to your Galaxy Exhibit (or coming from another ROM)?
Boot into existing recovery and create a Nandroid Backup!
Install at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
Reboot recovery into at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
CWM: WIPE dalvik-cache, format: data, system, and cache. TWRP: WIPE dalvik-cache, data, system, and cache.
** Optionally back-up sdcard0 before install and format it in recovery if experiencing install issues **
Install the ROM (without gapps)
Reboot system
After system boots, boot back into recovery and install KK Google Apps.
Wipe dalvik-cache and cache. Reboot.
- Upgrading from CM11
Boot into existing recovery and create a Nandroid Backup!
CWM: WIPE dalvik-cache and format cache. TWRP: WIPE dalvik-cache and cache.
Install the ROM
Reboot
Known Issues
ART takes ~15 minutes to install and some apps may not be compatible.
Display remains on while device is powered off and charging
Kernel Source
Credits
arco68, jocala, Christopher83,
pawitp, davidteri, mikeNG,
AriesVE DevConnection Team

Changelog
20140714
Sync with CM sources
Add center clock option
Add Xposed fix
Remove KSM
Disable LPA
416 MB userspace memory
md5sum: c821ebacaa5c969c55b0a511be8a3933
20140710
Sync with CM sources
Kernel 3.4.98 compiled with Christopher83's 2014.06 4.9.1 toolchain
406 MB userspace memory
Remove zram
md5sum: 7b0c0d8abf63adfa267b1f8f2c72b269
20140415
Sync with CM sources
Kernel compiled with Christopher83's 2014.04 toolchain
md5sum: bc9b6c5403d94a7e63f69aba7f1ec194
20140414
Sync with CM sources
Kernel v3.4.87
Enable LPA (credit arco)
md5sum: 23b1e4fb4b6f863eae2a5ac447f6dafb
20140402
Sync with CM sources
Kernel v3.4.85 (credit Christopher83)
Use older Adreno blobs
Netflix confirmed working
Add Performance Control (credit h0rn3t)
md5sum: d6dbb5bbeb4758657e9c74ad50c16ac8
20131125
Initial release
md5sum: 4fa0b6dd64730f4139d54375555dd91

Basebands & Misc.
Basebands
Flash in CWM recovery. Wipe cache and Dalvik-cache before installing.
T679UVLG3 2012 July
md5sum 61efc2e31fd0885dc0f948f84f94574f
T679UVLK2 2012 November
md5sum 0c0175d46e3fc4c9f11ee3352af85442
Odin 4.43 and USB driver
Placeholder for Odin 4.43, ancora.ops, and Samsung USB v1.3.2410 driver here in rar format.
Newer drivers will not connect with device in download mode.
Works with XP and will not work with win 8.

nice one didn't realize anyone else was deving for our phones. I'll test it out later after i get initial release up for AOIP CE.

Fantastic! I'll let you know if GPS doesn't work. I use it everyday during my runs.
edit*
GPS does work for me. The ROM does boot and works, but it's somewhat slow at times. The browser crashes. I tried clicking the news tab on the google main page. AND... everything is tiny. I'm not sure if that's how kit kat is suppose to look or not. Wow, they weren't kidding when they said kit kat uses little ram. Bluetooth also works... I paired my phone to my Windows 8.1 laptop successfully. I was able to play music on my phone through my laptop speakers, view files stored on my phone and send and receive files.

Thanks for the hard work and bringing us 4.4. Going to give it a whirl and see what happens!

I have heard of some issues with the stock browser on some other devices, due to webviewapi but everyone says chrome works fine. Don't know if that's helpful or the case here. Downloading now, eager to try some Kit Kat.
Sent from my SGH-T679 using xda app-developers app

I use chrome and it performs well enough that I never tested stock browser. chromewebview takes forever to compile, but I'll look at it later.

TripFX said:
nice one didn't realize anyone else was deving for our phones. I'll test it out later after i get initial release up for AOIP CE.
Click to expand...
Click to collapse
Let us know how camera works with ion, I think that's why arco switched back to pmem, but I'll try helping when you're there.

DPI
I went into the build.prop and changed the DPI to 240, I'm sure most folks know how to do that but thought I'd mention it for those who are wondering so all apps will be compatible & such.
On another note Titanium Backup is not showing all apps in batch restore mode that I have backed up, but when I view the Backup/Restore list they are all there. Might be a 4.4 bug.

Thanks for the effort to bring Kit Kat to our phone, hope you'll feel welcome to our community!

ArtfulDodger said:
I went into the build.prop and changed the DPI to 240, I'm sure most folks know how to do that but thought I'd mention it for those who are wondering so all apps will be compatible & such.
On another note Titanium Backup is not showing all apps in batch restore mode that I have backed up, but when I view the Backup/Restore list they are all there. Might be a 4.4 bug.
Click to expand...
Click to collapse
Might be st with the storage mounting points. I know usbdisk is logging a fit and sdcard1 doesn't seem mounted properly, so sdswap may be a temp issue.

jfbs said:
Might be st with the storage mounting points. I know usbdisk is logging a fit and sdcard1 doesn't seem mounted properly, so sdswap may be a temp issue.
Click to expand...
Click to collapse
Well when I try to restore most of those apps, the restore button is missing? Hmmmm...

ArtfulDodger said:
Well when I try to restore most of those apps, the restore button is missing? Hmmmm...
Click to expand...
Click to collapse
It could be caused by selinux permissions, or within TB itself regarding 4.4's API.

jfbs said:
It could be caused by selinux permissions, or within TB itself regarding 4.4's API.
Click to expand...
Click to collapse
Yeah because any system apps can be restored, and just a handful of user apps. 90% of the apps are being read as data only backups. Not sure what else to do at this point. Going to restore my nandroid, backup again and re-flash the ROM. Oddly enough the Play store didn't give the option of just downloading all of them again like it normally does. At any rate if I can't get my apps restored in bulk I won't be able to do this. Manually it would take forever and a day.
I have to tell you however your ROM is very light and smooth with zero tweaks. I'd really like to get this going if I can!

It could be superuser. Try supersu?

jfbs said:
It could be superuser. Try supersu?
Click to expand...
Click to collapse
I did, no luck. If I can get Play to just re-download the apps, I will do that and then restore data.

jfbs said:
Let us know how camera works with ion, I think that's why arco switched back to pmem, but I'll try helping when you're there.
Click to expand...
Click to collapse
Thanks since you are deving roms I can skip making my own rom then and focus more on ION :highfive:. Ya acro switched back because the cam driver has to be rewritten from scratch to work with it. It's not a biggie for me just mostly time consuming but it will be well worth the effort to keep our phones going longer and break the 3000 mark on quadrant :fingers-crossed: You should check out AOIP CE when it's up if ya like the installer I can mod/make one for you :angel:

some questionable advice
ArtfulDodger said:
Yeah because any system apps can be restored, and just a handful of user apps. 90% of the apps are being read as data only backups. Not sure what else to do at this point. Going to restore my nandroid, backup again and re-flash the ROM. Oddly enough the Play store didn't give the option of just downloading all of them again like it normally does. At any rate if I can't get my apps restored in bulk I won't be able to do this. Manually it would take forever and a day.
I have to tell you however your ROM is very light and smooth with zero tweaks. I'd really like to get this going if I can!
Click to expand...
Click to collapse
Don't tell anyone I suggested this, but as long as you have enough nandroids I suspect it can't hurt to try restoring just data from the backup and seeing if KitKat can cope with updating your JB-based data. Worst case nothing works and you have to go back to this unfortunate plan, but you might get away with it. Despite everyone's advice I haven't started from scratch since CM10 -- when moving to AOIP I just wiped ROM and cache but not data. When I briefly tried AOIP 2.0 I saw a message on the screen about "upgrading contacts database". So the bottom line is that Android knows how to handle version upgrades -- which makes sense, because the manufacturer OTA updates don't usually wipe your data.
With AOIP 1.5 the only trouble I had after my unorthodox migration was a crash in the calculator app and it went away when I performed "clear data" on just that app. So it might be worth a try.
[I didn't try asking Android to downgrade data when I switched back from AOIP 2.0 to 1.5 though... I restored the data from my last 1.5 nandroid at that point.]

aaopt said:
Don't tell anyone I suggested this, but as long as you have enough nandroids I suspect it can't hurt to try restoring just data from the backup and seeing if KitKat can cope with updating your JB-based data. Worst case nothing works and you have to go back to this unfortunate plan, but you might get away with it. Despite everyone's advice I haven't started from scratch since CM10 -- when moving to AOIP I just wiped ROM and cache but not data. When I briefly tried AOIP 2.0 I saw a message on the screen about "upgrading contacts database". So the bottom line is that Android knows how to handle version upgrades -- which makes sense, because the manufacturer OTA updates don't usually wipe your data.
With AOIP 1.5 the only trouble I had after my unorthodox migration was a crash in the calculator app and it went away when I performed "clear data" on just that app. So it might be worth a try.
[I didn't try asking Android to downgrade data when I switched back from AOIP 2.0 to 1.5 though... I restored the data from my last 1.5 nandroid at that point.]
Click to expand...
Click to collapse
I was a little skeptical I might get FCs out the wazoo but this actually works, for the most part. It breaks system settings however (no surprise). Only problem is now RAM Expander can no longer use the swap file, even if recreated. Get the "invalid argument" error after creation, although the file is there.
This was a great tip though as most all apps work just fine with no FCs. If I can get Expander working and Viper all will be well.
Edit: Swap files will not work with this ROM. Probably has something to do with path issues, IDK. Viper does not work either but that is a common issue among 4.3 and 4.4 ROMs. Oh well. Still this is nicely done, very lightweight and functional. 4.4 is going to have issues until app devs can catch up.
Great work and first effort @jfbs. I have a feeling I'll be back to try future updates.

How-To: Samsung Allshare Cast dongle with custom N7100 ROM

Hey guys,
I was having serious issues getting my Allshare Cast dongle to work with my rooted Note 2 (N7100). It either broke off the connection because of the flash counter or (even worse), when I ran TriangleAway beforehand, always rebootet my phone.
I've dug through countless threads addressing this issue and offering all kinds of different until I was finally able to make it work - still being rooted and using a custom rom. So I thought I'd just share my solution with anybody here who may find it useful.
*Edit*
Seems like Allshare Cast still tends to be a bit picky. The first connection is stable, but a second one reboots my phone after a few minutes. Quite annoying, but at least it works.
As usual, I will not be held responsible for any damage that might occur, so don't blame me if your phone blows up itself, or your house. :angel:
This works *for me*, other phones might yield other results.
These are step-by-step instructions if you're coming either from a f%*'ed up ROM that needs major repairs anyway (like me), or from a different android version. If you're running a 4.1.2 ROM you can try to jump directly to step 2. c). Still, I'd suggest you backup everything, see below 2. a)
Here we go:
1. Things you'll need:
a) Wanamlite 3.9 (http://wanamlite.com/2013/07/19/wanamlite-mg1-v3-9-android-4-1-2-clean-stable/) by Wanam (who saved me from ruining my phone btw: tried Wanamlite 4.2 with new bootloader, and without his warning, I would've used the MK4 bootloader instead of MJ5 and would've been stuck with Android 4.3/Know forever...)
b) Adam Kernel v2.7, Odin and/or CWM version (http://wanamlite.com/2013/07/19/adam-kernel-v2-7/) by Wanam
c) Stock recovery, kernel, etc. (http://forum.xda-developers.com/showpost.php?p=31986738&postcount=7), provided by dr. ketan. I'm using this one: http://d-h.st/gwn (Stock Recovery/Kernel/Modem from XXDMB6 19th March13)
d) Mobile Odin (http://forum.xda-developers.com/showthread.php?t=1347899) by Chainfire
along with the FlashKernel file (MobileODIN_FlashKernel_N7100-v5.0.apk) further down on the same page. if v5.0 doesn't work, try v4.0 instead.
e) TriangleAway (http://forum.xda-developers.com/showthread.php?t=1494114) by Chainfire
f) I'm assuming you're already rooted and therefore have a working CWM/TWRM running.
2. What to do (step-by-step):
a) I'm being a bit paranoid by now, but for various good reasons. These instructions may be a bit overcautious, but at least your data will be safe from being accidentally erased. Trust me, you do not want that ever to happen... :crying:
Also, I always carry a ROM with me so I can repair my phone on the go. So of course, you can also do the flashing via PC Odin, but I prefer the CWM method I've described further down.
- backup everything. And I mean EVERYTHING! I did a full backup, i.e. Titanium Backup, TWRP backup, and I copied the whole contents of my internal and external SD cards to my PC. I'd even suggest you use another extSd during this process (which will save you from the hassle of copying the whole thing btw). This whole backup thing took me about 2-3 hours, but I would've gone mad if I'd lost either internal or external SD data.
- copy Wanamlite 3.9 onto the external SD your're going to use.
- power off your phone (take out the battery to be sure)
- take out your external sd to protect all your precious data. Just in case you accidentally do something wrong and end up formatting the extSd (in TWRM, this option hovers dangerously between "Factory Reset" and "Format Data")
- boot into recovery and do a full wipe (Wipe Cache / Wipe Dalvik Cache / Factory Reset / Format Data)
- power off your phone (take out the battery to be sure), re-insert the external SD
- boot into recovery and flash Wanamlite 3.9 (follow the instructions on his site). Be sure to chose Adam Kernel and checke "Allshare Cast" during the installation process. The Adam Kernel works best with TriangleAway, because (unlike the stock kernel provided with his ROM) you can reset the flash counter without rebooting.
Now you have an absolutely clean 4.1.2 rooted custom ROM running on your phone.
b) Restore your data.
- run Titanium Backup, and restore everything that's important (all user apps w/ data, call logs, messages, email etc.). I'd suggest you just leave out system apps if you're coming from another ROM. You can try to restore everything of course, worst thing to happen is that you'll habe to re-wipe and then re-flash the ROM. In my case, it was no problem, because I had made my backup from this very ROM version.
- Next, copy at least the "Android" folder (containing /data and /obb) from your backup back to your internal SD card. By default, TB doesn't backup large files and folders, so all the bigger apps (like e.g. games) are still missing. If asked to overwrite, simply say "yes". If you want to make sure everything's back to how it was before, copy your whole internal SD backup back to your phone.
c) You've spent an awful lot of time by now, and still, Allshare Cast won't work. So let's go for it:
- install Mobile Odin and the appropriate Flashkernel.apk
- install TriangleAway
- unpack and then copy the contents of "Stock Recovery/Kernel/Modem from XXDMB6 19th March13" to your internal or external SD card (doesn't matter which one).
- run TriangleAway. It should read "Counter: 1 /Binary: Custom".
- tap "Reset flash counter". TriangleAway confirms that the counter was reset to 0 and closes.
- restart the app. Now you should see "Counter:0 / Binary: Official".
- run Mobile Odin, chose the stock kernel (tap "Kernel" -> "[path where you stored the kernel.tar from the archive]")
- tap "Flash Firmware". Your phone will reboot.
Congratulations! If you did everything correctly, you should now be running Wanamlite 3.9 (JB 4.1.2) ROM with rooted stock kernel. Allshare Cast works like it should. FIFA14 or DIII4A are really fun on a 40" screen.
If you don't want to use the stock kernel all the time, flash Adam Kernel v2.7 through Mobile Odin or CWM. Allshare Cast functionality will be broken, but you have all the nice benefits of the custom kernel like STweaks or BoefflaSound. To make Allshare Cast work again, simply repeat the last five steps from above: "c) - run TriangleAway... etc."
That's it. I hope this is helpful! Suggestions are welcome. If something's missing, or if I posted anything dangerous, please feel free to scream, and I'll correct it ASAP.
Cheers,
- Alex

Thanks for the nice review. I have these and wholeheartedly recommend them as well.

does anyone know how to update Allshare Dongle via N7100?
I've had many ROMs and on every single one I have message that update was downloaded and to restart the dongle, but after I restart the dongle it connects again with the same message, so it is infinite loop. I can connect, but sometimes it laggs, so I assume that newer firmware would fix that issue.
I've even contacted Samsung's support service and they couldn't help me. They told me to wait for update, but even on the newest stock it is still the same.
If anyone knows the solution please share.

thanks
thanks for the review its really helpful

What is 12gb of "other" storage data that I can not seem to find [OP3T, 128GB]

What is 12gb of "other" storage data that I can not seem to find [OP3T, 128GB]
Hello,
I just reflashed OxygenOS from Paranoid android after a clean wipe of data, system, cache etc. After set up, I realised there is 12gb of data being occupied under the "other" storage. I proceeded to factory wipe as well and I still have this 12gb of data.
I can not seem to figure out what this 12gb of data is. It is not the oem_logs. I do not have nandroid back ups. I do have around 4gb of titanium backup that I can account for. That means there is still 7gb of data that I can not seem to find.
Any help with figuring this out?
The only thing I could think of now was to wipe internal memory and flash the rom all over. Is that possible? I heard that wiping internal memory is a no no.
I have included some screenshots. If anyone needs more information, please ask.
(The massive app data is because this morning I finally gave in and redownloaded my spotify playlists. Spent 2 days trying to figure out this damn 12gb other data...)
Edit: Forgot to mention, I am on the latest OxygenOS stable. Rooted with latest Magisk and using TWRP 3.1.1-2

An update
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.

Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.

Any apk files you've downloaded, logs you've recorded all in that category. Even large flashable zip files and other firmware files are also under that category.

EatDahPewPew said:
An update.
I deleted the titanium back up. Other storage now shows 7gb.
I used DiskUsage to further pinpoint my data use. 10gb in System and 8ishGB in app data.
I checked System folder, it is 2.8 GB.
10gb minus 2.8gb means around 7gb of data that I do not know what is.
Click to expand...
Click to collapse
Twrp backups

If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.

Mr.RooT said:
Try look into /storage/emulated directory. I had same problem and in this folder I found missing GB's of storage.
Click to expand...
Click to collapse
Hey, Do you know what exactly I am looking for in there?

vighneshpillai90 said:
If this happens even after clean flashing a new rom/any rom then its something wrong with the partition.
I was facing a similar issue where my internal storage was being dislpayed as 24.6GB (Instead of 54GB) total capacity.
Can be easily fixed by using twrp, Firstly create a backup of the entire Internal Storage (Media)
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Flash your rom and it would be fixed.
Click to expand...
Click to collapse
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?

EatDahPewPew said:
I think you maybe right. I have flashed a few roms around and noticed it after flashing OOS. I do not know if it was also there before.
I do not care so much about my internal storage (media), I can afford to loose and restart all over.
Will wiping the internal storage be fine? I heard on forums that it messes things up.
Ill probably use OTG USB to flash the rom again. That should be good right?
Click to expand...
Click to collapse
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.

vighneshpillai90 said:
I have done all sorts of things with my phone, i have even deleted the root folder using TWRP file manager and managed to bring my device back to life.
So I guess i can assure you that it wont do a thing to your phone if u wipe internal storage
Provided make sure you are using BLU-Spark TWRP.
(BLU-Spark-TWRP v45 for Nougat based roms &
BLU-Spark-TWRP V52 for Oreo based roms).
Do not use the official TWRP as it hasn't been updated since its 3.1.1.2 release.
Click to expand...
Click to collapse
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.

EatDahPewPew said:
Hey, Do you know what exactly I am looking for in there?
Click to expand...
Click to collapse
Every folder except emulated directory. Firstly I thought that these other folders are links to their original location, but when I deleted that folders, original folders weren't affected. But delete it at your own risk! It could be coincidence, that these folders weren't linked to original ones.

EatDahPewPew said:
I ended up doing the steps but I have TWRP 3.1.1.2. I am a bit out of loop, why is BluSpark better for nougat? I just knew that we needed a specific one for Oreo since TWRP had not been updated
For other people who may come here. I did follow the steps. From 5gb other data, I am now down to 0.8gb. I do not know what that 0.8gb is but ill take it for now.
Steps were
Step 1. Go to Wipe>Advanced wipe>(Select all partitions)>Wipe.
Step 2. Go to Wipe>Format Data>(Type YES)>Done!
Step 3. Repeat Step 1.
Step 4. Flash rom, gapps, etc etc
I DID RUN into a problem at step 2. I got an error and then when wiping or flashing rom, my /data would not mount. I googled and found that if you change the data to different format, ext4 and then abck to f2fs, the /data should mount and you can do whatever.
Maybe it is because of the TWRP version, I was on the latest 3.1.1.2.
Click to expand...
Click to collapse
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:

vighneshpillai90 said:
With every new update of Oneplus (wether it be Beta or Stable) the bootloader & firmware might (or might not) get updated and hence if u use the old TWRP there are chances of being incompatible with the new builds/roms. If u notice BLU-Sparks TWRP releases, they follow a trend i.e. he releases a TWRP after every major update of Oneplus Roms which is basically to make sure that the recovery is compatible with the newer builds.
So i would suggest you to use the BLU-Spark TWRP to be on the safer side.
Hope i have cleared the doubt. Cheers. Good day. :good:
Click to expand...
Click to collapse
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.

other than media files and unrecognized file extension
like .zip .apk .flac and etc

EatDahPewPew said:
Yes! That helps. I guess I should flash the blu spark twrp soon. Or atleast when I am switching roms. Am on the last paranoid android for nougat. Will wait it out until Oreo is out on either oos or some major role.
Do you know where I can find blu spark twrp? I found blu spark kernel but could not find the twrp.
Click to expand...
Click to collapse
Open the Blu-Spark thread, go to downloads, keep scrolling and you find the twrp among the kernels listed there (Latest is v8.52).