yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] saihia:
Please help me I want to root this phone but it's not so popular so I can't find some rooting procedure for this phone..
[Galaxy Note II Q&A, Help & Troubleshooting] mohsin125:
Hi guys,

I am in a state of panic at the moment and really need your help. My galaxy note 2 (N7100) was on 4.1.1 and it used to restart every 15mins so I decided to flash the 4.1.2 via odin to fix it (as data factory reset wasn't helping at all).

So I flashed the rom (4.1.2) from sammobile through odin 3.07 and straight after the flashing process completes, the device restarts and goes to recovery 3e and gives me the following error:

Installation started

bla bla

bla bla

e: failed to verify whole-file signature (in red)

e :failed to verify whole-file signature (in red)

e: signature verification failed

Installation aborted

Then if i choose to reboot device, it gets stuck at the samsung logo :'( and I cant do anything then. I can go to recovery again but even if i wipe everyyyything it doesnt make any difference.

I can install CWM recovery through odin and access it but I don't know what to do with it as I cant flash anything from there.

No matter what reigon stock rom I flash, it is not letting me get past through the samsung logo and straight after odin flash it goes to recovery 3e giving the error mentioned above.

PLEASE HELP XDA :'(
[Galaxy Note II Q&A, Help & Troubleshooting] aukhan:
what region you device belongs to , as you said you got CWM did you try with a custom rom ?
[Galaxy Note II Q&A, Help & Troubleshooting] Zionator:
Since u can't put a custom ROM on the sd card I suggest u take our the sdcard put put it in a adapter then download a custom ROM and copy it to the sdcard then put it back into or phone and boot into recovery wipe all the phone and then flash the ROM from SD card to phone.

Unless u got a faulty recovery then it will work this way.

Ps. You can only do so if your phone is rooted.

---------- Post added at 11:17 AM ---------- Previous post was at 10:55 AM ----------

Use one of these links

http://xdaforums.com/showthread.php?t=1980475

Or

http://xdaforums.com/showthread.php?t=2200625
[Galaxy Note II Q&A, Help & Troubleshooting] mjrshark:
Simply download another rom from sammob or reflash same rom again

better use odin 1.85 , dont know why but that what i use for note2

be sure that auto reboot is checked

only set PDA = Rom

everything else is blank

Goodluck
[Galaxy Note II Q&A, Help & Troubleshooting] UtkarshGupta:
Flash stock firmware. Then flash twrp then wipe data
[Galaxy Note II Q&A, Help & Troubleshooting] mohsin125:
Thanks for the help guys...i flashed a rom through cwm and it worked...i dunno y odin flashing did not work
[Fascinate Android Development] BDogg718:
<reserved>
[Fascinate Android Development] Mazda:
Great job Brian!!!

Glad you finally got this out for everyone to enjoy on this device :)
[Fascinate Android Development] BDogg718:
Thanx Alex. Appreciate it!
[Fascinate Android Development] Bubbadogg14:
This is exciting!! Can't wait to try it out
[Fascinate Android Development] Unjustified Dev:
Ikr adding a lot of to domination .
[Fascinate Android Development] iiandskater:
Great !!

New rom to get fun,

Thanks :D
[Fascinate Android Development] Unjustified Dev:
Lol is porting easy for you
[Fascinate Android Development] nyjw:
downloaded rom and gapps. it seems that my kernal refuses to update from previous. can you help please
[Fascinate Android Development] BDogg718:
Did you do a clean install?
[Fascinate Android Development] nyjw:
yeah..wiped the big three 3x then flashed. is there a kernel i can flash over to update?
[Fascinate Android Development] BDogg718:
Im not sure what ya mean? Update kernel? The kernel built in is new CM kernel. What did you want? Either way here is a nice list that hhp_211 put together. Maybe you can find what your looking for there.

http://xdaforums.com/showpost.php?p=38014509
[Fascinate Android Development] nyjw:
what kernels can i use with your rom?

---------- Post added at 05:12 PM ---------- Previous post was at 05:05 PM ----------

can i zip the files found on the android kernel aries github and flash that?
[Fascinate Android Development] BDogg718:
No. It doesnt work like that. Those are files to build a kernel. Whats wrong with the kernel I built in? As far as kernel that will work with this ROM, I have no idea. Its a brand new ROM. Just flah some from that link and find what ya like.

DISCLAIMER: Dont come back posting that a certain kernel soft-bricked ur phone. I have no idea what other kernels will do when flashed the this ROM. Shouldnt do too much damage..lol..maybe a soft brick here or there...lol
[Fascinate Android Development] nyjw:
sorry..i think you misunderstood me. there is nothing wrong with your kernel...its my phone..no matter what rom i update to it seems that the kernel refuses to change. i appreciate the time and effort you put in to help me
[Fascinate Android Development] BDogg718:
Are you windows or linux user? Ever used Heimdall? Its like ODIN
[Fascinate Android Development] nyjw:
use windows and never used heimdall. again im pretty much a noob
[Fascinate Android Development] jlvlawrence:
Definitely gonna flash this when I get home!
[Fascinate Android Development] BDogg718:
Send me a PM. Ill try to help ya from there.
[Fascinate Android Development] ulnevrwalkalone:
First of all thank you for all of your hard work, I appreciate all you guys do to give us these roms. I'm loving this new rom and was just wondering a couple of things. First, is Halo actually on this rom? I see it listed as a feature but I cannot figure out how to turn it on, when I was on PA it was available from the status bar or as a toggle. Also I am digging the kernal on this rom, did you build it from scratch or is it based off something else?
[Fascinate Android Development] PwnFx:
I attempted this, but without first going to the hacksung rom, I am unable to even get past the getprop message. DU will only even allow me to attempt to install only after I have flashed from stock to hacksung, so there must be a way to go straight from stock to DU or some alternative?

Apologies if I'm being unclear or confusing, I'm just so clueless here.
[Fascinate Android Development] Unjustified Dev:
Flash a another ROM first I don't have issues yet I never tried to flash this from stock try flashing PAC since its cm based
[Fascinate Android Development] PwnFx:
Will do, thank you.

If I can get it to flash, I may end up sticking with it, I really liked the look of this rom, but I've put a ton of hours into trying to get this to work lol. It's getting frustrating.

I really appreciate all the help you guys have given. Thank you.
[Fascinate Android Development] Unjustified Dev:
No prob
[Fascinate Android Development] PwnFx:
From stock, the only ROM I am able to flash is the hacksung roms, I have tried Avatar, DU, and PAC as of now. All of them return the same result when flashing from hacksung anyway, so it seems to not do any good to flash to hacksung.

So what are my options here? :/
[Fascinate Android Development] Unjustified Dev:
Do you have a fassy sch-i500?
[Fascinate Android Development] PwnFx:
Pardon my ignorance, but what is a "fassy"?
[Fascinate Android Development] Unjustified Dev:
Fascinate we gave it a nick name lol
[Fascinate Android Development] PwnFx:
Oh, lol. Guess I could have put two and two together.

Yes, it is a SCH-i500.
[Fascinate Android Development] Unjustified Dev:
Idk what your doing lol. I haven't had this issue . I Odin stock then Odin cwm and I flash away no issues .
[Fascinate Android Development] PwnFx:
It just gives me error 7 when I try to do that. Is it something I'm doing wrong?
[Fascinate Android Development] Unjustified Dev:
Add me on hangouts android.c357@gmail.com I'm on now
[Fascinate Android Development] PwnFx:
I added you I think. I never used it before though lol.
[Fascinate Android Development] hhp_211:
you can install this way::

Power off and pull battery,

remove micro sdhc card

put into d/l mode, install battery

odin:: :: PDA Slot :: CI500_VZW_EH03_GB_CM.tar.md5 ::

and in the :: PIT Slot :: Atlas_v2.2.pit ,,, and appropriately check box [[ Re-Partition ]]

when finished

reboot (important)

~~check out all of Verizon goodness ~~

oh sorry,,,

Power off and pull battery

put into d/l mode, install battery

odin:: :: PDA Slot :: cwm4_fixed_for_cm7-ODIN.tar

when finished, click reset in odin

pull battery and usb to power down the fassy and close out of odin

put into d/l mode, install battery

odin:: :: BOOTLOADER Slot :: GBbootloaders.tar ,,, and appropriately check box [[ Phone Bootloader Update ]]

when finished, click reset in odin

pull battery and usb to power down the fassy and close out of odin

Reinstall micro sdhc card

Use three finger ,, [[[ Hold -- Volume buttons UP / Down & Power ]] into CWM blue recovery 4 [ie: cwm4_fixed_for_cm7]

((you have to use this recovery at this point in the process,,, it lets file system properly update from a bml ROM to an mtd ROM)))

and, Choose the Wipe Data/Factory reset, and also wipe dalvik cache [1 time for each is fine]

then while still in recovery,,, flash your 4.2 // 4.3 ROM of choice,,,

It should auto reboot into any newer recovery 6.0.x.x, or new TWRP 2.x.x Recovery,,, ,,, never go back to the [cwm4_fixed_for_cm7] recovery,, ,, unless you have ODIN'ed back to stock,,, ,,, this is normal,,, ,,, and you will need to select install zip from sd [again]::

and choose to install/flash your 4.2./4.3 ROM of choice AGAIN,

if it auto reboots you back into this same recovery again [meening: any newer recovery]

...[[[ the recovery style and version is determined by the ROM you are installing, some have standard CWM Recovery, some have Hellybean Touch Recovery,,, some have TWRP Recovery, and some have a blue Touch Recovery version ]]]...

,,, still that is fine/normal ,,,,,,, simply install/flash your 4.2/4.3 ROM of choice AGAIN,

if it auto reboots and tries to load the ROM,, if not manually choose to Reboot Rom,,, and ,,, Wait ,,, patiently,,, ,,, maybe as much as 8-10 minutes for it to boot all the way up.

you may ultimately have to flash 1 more time,, some ROMs seem do be more finicky than others.

After that you really should be almost good to go.

On the 1st boot of your new 4.2/4.3 ROM give the filesystem about 5-10 minutes to scan through everything before making any changes to any of your ringtones or notifications

after that reboots into recovery,,,Wipe cache,,, and Install a gapps zip of choice::: [ either whats recommended by the ROM dev/maintainer,,, or an official gapps of the appropriate date that matches your ROM ]

reboot

Enjoy your jellybean goodness ~ Yummy!

.

.
[Fascinate Android Development] Szil66:
Just flashed 4.3! Love it so far, super fast!! I flashed gapps-20130813 with it, I went to restore all my apps and I got an error. Every app I try to install or update just gives me the same error,"' could not be downloaded due to an error. (Error retrieving information from server. [RPC:S-5:AEC-0]). Any idea on the fix? And once it's fixed how do I restore my apps? Thanks for the help
[Fascinate Android Development] hhp_211:
Method 1:

Open system settings

Go to Applications (or Apps) >> All

From all apps select Google Play Store >> Force Stop and Clear Data

Again, from All>>Download Manager >> Clear Cache and Data

Finally, All >> Google Services Framework >> Clear Cache and Data

Now, rerun Google play store.

Method 2:

Go to system settings>> Accounts>>Google>>remove your Gmail account

Now from settings>>Apps>>All> Force stop, Clear data and cache for Google Play Store, Google Service Framework and Download Manager (like in method 1)

Now again go to settings>> Accounts>>Google>>Add your gmail account

Restart your android and then accept all the Google terms and setup Google settings

Rerun Google Play Store and update or install your app.
[Fascinate Android Development] Szil66:
Thanks for the post! I just did a factory reset since I had just flashed the rom. I didn't have too much to lose and it fixed it! Thanks again!
[Fascinate Android Development] nm3210:
You can manually remove the 'assert(getprop("ro.product.device")' line (all the 'ro.product.device' checks) in the META-INF\com\google\android\updater-script (within the ROM zip you're trying to flash) to force it to try to install without checking to make sure it's the correct product first (generally dangerous). I believe that's what error 7 is? And always try different SD cards out to see if that's maybe an issue.

edit: and check & doublecheck MD5 sums of your downloads
[Fascinate Android Development] newbie4ever:
I was just wondering if everything works on your Mesmerize call,text,data and mms? I want to flash this to my friends Phone, but i dont want it to be a big hassle... thanks in advance
[Fascinate Android Development] jkok:
idk about the mesmorize, but it works on the fassy call, text, data work, but mms is flanky at times, but heres a modded apk i worked on that works just push it to system/app and chmod it to 644 (rw-r--r--)

adb commands to do it are: (taken u are in command prompt in the folder with the mms.apk), reboot WILL be required to fix it, new line means new command.

adb remount

adb push mms.apk /system/app/mms.apk

adb shell chmod 644 /system/app/mms.apk

adb reboot

in terminal emulator on phone (with mms.apk in root of sdcard)

su

mount -o rw,remount /dev/null/ /system

cp /sdcard/mms.apk /system/app/mms.apk

chmod 644 /system/app/mms.apk

reboot

edit: BTW this may fix other 4.3 roms if u all want to put it to test. it worked on fixing this roms mms, or at least the fix very long delay of sending it+adds some features
[Fascinate Android Development] Unjustified Dev:
Just tell me what you did :p . I can add it to my source
[Fascinate Android Development] hhp_211:
Yes do tell! And what ROM did it come from?

I notice it did not have dark theme in it either... Had to change back right away.. To much white screen!!! :cool::eek:
[Fascinate Android Development] Unjustified Dev:
If it doesn't have dark theme it must be from PAC . I removed it as its useless and dark switch is better . Don't know if any other ROM removed it too
[Fascinate Android Development] hhp_211:
:D not to confuse it moar,,

i meant:

the "dark ui switch" as it's called in dirty unicorns

I assume this is same as a "TRS" toggle and not the "theme" that pac developers used.

:D

.
[Fascinate Android Development] Unjustified Dev:
We use the same switch . We don't use the MMS dark theme . If you open messaging in settings it has dark theme. I removed as no one uses it and trds implementation overrides it. Trds slim aka PAC in black aka Dark ui for DU
[Fascinate Android Development] hhp_211:
Right right :p ,, just saying that the test mms did not have a dark ui to it after i installed.
[Fascinate Android Development] Unjustified Dev:
Maybe its from cm or something I still want to know what was done to it:D
[Fascinate Android Development] jkok:
i didnt mod it from source tbh i decompiled a mms.apk from a working mms 4.2.2 rom and copied any smali code from the DU 4.3 rom lol then recompiled+signed it so java source wise idk what is done it was more of a hit+win by luck, but u can add just the apk fro the meantime lol
[Fascinate Android Development] scelera:
+1 I've had to do this on a number of occasions for the same error. Gets rid of it every time.
[Fascinate Android Development] Unjustified Dev:
I removed that from my source now anyone can flash ROMs if bdogg continues using my source
[Fascinate Android Development] Unjustified Dev:
Show off :p
[Fascinate Android Development] hhp_211:
I've not experienced long sending times that I'm aware of. But do you think it could also be because of the larger picture sending size in du versus other mms apk's? The one you posted is

<int name="maxMessageSize">307200</int>
<int name="maxImageHeight">480</int>
<int name="maxImageWidth">640</int>

du is ::

<int name="maxMessageSize">1228800</int>
<int name="mmsHeaderSize">5120</int>
<int name="maxImageHeight">1920</int>
<int name="maxImageWidth">2560</int>

I pulled another from a working 4.2.2 (that is dark and themeable) and installed (for testing with same smaller size) with no changes, and tested and sent a mms picture just fine.

So it's got me thinking

.
[Fascinate Android Development] Unjustified Dev:
Actually you are correct I seen this in another commit
[Fascinate Android Development] puterdoc:
I am on Ntelos thus have had my own share of MMS issues. I use Go SMS Pro and it works great. It was the only thing that got my phone to receive pictures bigger than a postage stamp. Just like mentioned before, I too didn't have to mess with APNs on this Rom either. Have typed that in so many times now from prior Roms its embedded in my head. I was worried when Rom Konverter wouldn't convert this, but has worked well without.

I have had some pregnant pauses with this rom but when its not thinking it has done well. The only two things I have in mind right now is the scroll animation drives my eyes crazy, didn't find the turn off for that yet. And is there a fix for the vmail notification. I know it was an issue with other 4.22 Roms too. Was hoping it might have gotten fixed in 4.3.

Thanks for all your hard work. Love making better use of the older but not dead tech.
[Fascinate Android Development] BDogg718:
You can turn off listview animations. System Settings /Rom Control /Animations.
[Fascinate Android Development] hhp_211:
[MENTION=1903184]puterdoc[/MENTION]

I posted where the animations switch was at a few pages back

List animations

There us not a fix yet for voice mail,, but check out VMMonitor from play store, it works to retrieve vm

Edit,, correct name and link::

VMMonitor

https://play.google.com/store/apps/details?id=com.steepcanyon.VMMonitor

I now there is a fix floating it there,, but this works now and you don't need Google Voice if you don't want to use their service

.
[Fascinate Android Development] jkok:
thats acually one of the things i changed, cause i notcied when i was looking through the apk that the size was bigger then what i usually see, thats one of the things i thought would make it, when i did completely fresh flash (no mods with the mms.apk it came with), it took me 1 hour 35 mins to send a 480x480 picture, as for this mms.apk i posted with smaller values, it sent it within 2 mins lol thats one of the things i modded, then made sure some of the smali things were there to be sure, but anyways as far as ive experienced the mms.apk resizes any photo sent anyways to the values in

<int name="maxMessageSize"></int>

<int name="maxImageHeight"></int>

<int name="maxImageWidth"></int>

and if its smaller it remains the same, if bigger its resized, its resolution interchanges for landscape photos too but keeps the size same; the message size is also important too as far as i think not many pictures resized to 480x640 are over 307200 Bytes default lol thus making it send faster, as its not being resized to a high value, but dont get me wrong it risks making huge photos not send correctly, it could resize and made blurry, or even freeze up the app on one occassion when i sent using GO SMS, but other then that what i put for it is more of the common carrier mms size, so it only seems fair right? lol one thing from stock we all could agree with lol

edit:

i know this is for 4.2.2 but there was something posted from the main DEV of geewiz for voicemail fix that could possibly be portable with wenough work

heres the thread i made for it for everyones reference

http://xdaforums.com/showthread.php?t=2459816
[Fascinate Android Development] kb8no:
If we could get that dang voicemail thing fixed it would be a very very happy day.
[Fascinate Android Development] hutchjim:
Teasing

Your teasing again lol:good: good work man
[Fascinate Android Development] nm3210:
Weren't the changes for 4.3.1 pretty much just for the Nexus 7 LTE? Is there any benefit/changes to the framework at all? Here's the [supposed] changelog: https://gist.github.com/archon810/6895144
[Fascinate Android Development] puterdoc:
You guys are great. Thought I was nuts as I didn't see the list animation under animations. And I do try to read pretty well but didn't blow up the pics :) . Thanks I found it under the General UI after seeing the pic. As for the vmail options, will look at those now. I have gotten in a bit of trouble a few times missing messages because the Rom play is more important of course ;)
[Fascinate Android Development] scelera:
Everything works great on my Mez except for MMS, but looking around that might just be an issue with the app and not the phone. I just figured after 5 minutes that it wasn't going to work, that and I don't see any APNS for USC in the list. I tried to add one but I couldn't select it, I don't know if that matters or not....
[Fascinate Android Development] jkok:
push the mms.apk i posted a few posts before this using adb shell on a computer, download it, and put it in a folder where u can get to it easily with adb then do these commands

adb remount

adb push mms.apk /system/app/mms.apk

adb shell chmod 644 /system/app/mms.apk

adb reboot

and it should work, what he mentiuoned earlier is that the values are tooooooooooo high for phones to simply send as fast as we are used to since it makes it 2x-3x larger compacity then usuall mms applications. i lowered the ammount in a mms.apk that has more features, but is not togglable with dark DU toggle, but it has working mms as far as i tested, and has added features of

-read request (tells u if it has been read),

-gestures (if it wasnt already there in DU mms.apk)

-blacklist (again if it wasnt already there)

and overall untill the values i changed are set to the original apk, sadly i think my modded mms.apk is what is needed to make it work for now

heres the apk if u need it

http://xdaforums.com/attachment.php?attachmentid=2325404&stc=1&d=1381795056

as for the APN's u need to make sure your carrier is in the APN's

idk about the apns on a GSM (sim card enabled) phone

but for CDMA (non-simcard/built in sim) all the apns configured to the phone are licated in /system/etc/apns-conf.xml

do this on adb

adb pull /system/app/apns-conf.xml

then use notepad++ to open it, then search for your carriers name, u should see two seperate ones for lmost any carrier look for one(or multiple) saying your carriers name, and one saying your carriers name and "MMS" (e.g "STRAIGHT TALK", and "STRAIGHT TALK MMS" for mine i had to put on my fassy personally lol but theres usually serperate apns for mms and regular (data, talk, texts), and sometimes more for tethering, premium sms, etc...

edit them by copying and pasting the one above and carrier and paste it one line below, add the required fields for the apns (every carriers different, expecially by region/country so search for the ones u need) NEVER put the data,text,talk APNS with the tether, and the MMS, not alot of CDMA phones read them all from the same apns and can cause errors, (like the whole Straight Talk Global MMS error when they changed it to work seperatly from the regular apns, causeing alot of people to lose mms, even if their roms/phones worked before)

then do this in adb (taken that u are in the same folder in adb as the apns-conf.xml)

adb push apns-conf.xml /system/etc/apns-conf.xml

adb shell chmod 644 /system/app/apns-conf.xml

adb reboot
[Fascinate Android Development] Unjustified Dev:
I'll hook you up :)
[Fascinate Android Development] scelera:
I actually tried that MMS.apk and it didn't work either. Grabbed the one from PAC just for something to try and that didn't work. But, not sure if anything will work since I just flashed DU right on the Mez with no edits in the Framework or anywhere else. So right now, it says Verizon all over my phone, not that I care what it says but makes me think that there are a couple of things that haven't been fully built in for it to work.

Dude Thanks!!!! I've been messing with this since 4.3 dropped. Normally I just run it through RomKonverter but for some reason it doesn't work. And trying to do manual edits just hasn't been working. It's been driving me nuts :silly: