yashsingh1/xdaforums huggingface dataset:
[Galaxy Grand Duos i9082 General] gta112010:
No do not use triangle away

Don't use triangle away as it doesn't have support for our device yet. Chainfire has been requested for addition of our device.
[Galaxy Grand Duos i9082 General] yuvi123456:
help me 2 gta112010...

---------- Post added at 11:54 AM ---------- Previous post was at 11:47 AM ----------

where to find these files in the stock firmware package i downloaded

Click on PIT button and select: baffin.pit

- Click on PDA button and select: CODE_I9082xxxxxx...tar.md5

- Click on PHONE button and select: MODEM_I9082xxxxxx...tar.md5

- Click on CSC button and select: CSC_Oxx_I9082Oxxxxxx...tar.md5

stuck with downloading for 2 days and now stuck with flashing it too... someone know where to find them... thanks in advance

http://dl.xda-developers.com/attach...cadc3df9453cf/512da656/1/7/6/4/2/2/7/3333.jpg

just geting this two files .. what should i do
[Galaxy Grand Duos i9082 General] speedy_samy:
please someone try the unrooting process plzzz......... plz answer my Question if i only remove supeSU then my grand will come to official stateo or not ????
[Samsung Galaxy Nexus] quickToaster:
I just installed the Fugumod kernel (stable-v4.1). One of the main reasons was to mess around with Grsecurity using sysctl - the only problem is that there is only one option available in '/proc/sys/kernel/grsecurity' and it is 'romount_protect'.

Unfortunately there is no /proc/config.gz and I cannot seem to find the kernel config online - so I have no idea what features have been enabled.. I don't even know if sysctl support has been compiled in.

I was wondering if anyone here knew much about Fugumod.. What is supported.. how, if I can, configure Grsecurity without building my own kernel.

I'm also open to suggestions to other security orientated kernels.
[Samsung Galaxy Nexus] quickToaster:
Thanks. Rules have been read - sorry for posting in the wrong place.
[Samsung Galaxy Nexus] beekay201:
How about you talk to nikademus or post in his thread? No one better to ask than the man himself.
[Samsung Galaxy Nexus] quickToaster:
Thanks. I initially searched for that thread - that was in fact how I found the kernel - but I was under the (wrong) impression that the thread was locked. Sorry. I will post there thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gutlessmerc:
Hey Guys,

I've tried all kinds of different roms, from different versions of Liquid Smooth, Carbon, Jellybam, but one common issue i experience is WIFI tethering.

All roms except Liquid Smooth 4.1.1 RC7. I've done clean installs, even went back to stop and flash fresh, and to no avail. None of the roms let me tether other than RC7. Even with RC7, the native tether doesnt work. I'd have to use a wifi tether app which only works for rc7

So a quick summary of what ive done so far:

-All wipe steps, factory reset inclusing data and system but to no avail.

-go back to stock, root again, flash any rom, nothing.

-go back to RC7 liquid smooth rom, and the wifi tether app is the only way to get wifi tether to work.

Any recommendations on what i could try or even use another rom will be awesome.

Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xBeerdroiDx:
WiFi tether on AOKP's 4.1.2 works for perfectly. Additionally, the rom is super stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gutlessmerc:
Thanks for letting me know. The current ROM i am running is on 4.1.2 as well. It seems Wifi tethering hasnt yet been perfected on 4.2.2. Will wait this one out i guess.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
WiFi tethering works on task's aokp and i used it last night on Paranoid KangDroid both secured.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g35thrilla:
hey i just flashed over this rom, and was trying wifi tethering.

On this rom the connection went through and it connected on the other device however im still not being able to actually get a signal on the other devices. I tried connecting to my Galaxy tab and also my laptop. any advise?

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RPelham:
You can try flashing KT747 Kernel. WiFi tether states its been fixed a few days ago. May be something worth doing to see if this corrects your problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g35thrilla:
i was using 4.2.2 Rootbox prior to this flash. I had tried to flash over the KT747 kernel for D2ATT however it did not work it just hung the phone in a continuous boot loop. i tried to do the method with fixed permissions in TWRP also but still no luck.

However it seems like on the AOKP(Jellybean 4.2.2 )Task650 (2.23.2013) (AT&T) rom i'm running the wireless tether is an issue still for Canadian customers as per the FAQ section that's in their main Rom thread
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Not for everyone. I've tethered no problem on task's 4.2.2 and I'm on telus
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g35thrilla:
Well its not for me on Rogers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ragz:
Tasks latest version is works for me .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I've had working wifi tether on my 4.2.2 rom for quite some time. Where you getting the "Wifi tethering hasnt yet been perfected on 4.2.2" information from? You have to have a ROM + Kernel that will allow it. Most AOSP roms should be up to date. If they are not then I'm not sure why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] miatawnt2b:
Another plug for task's latest. Tethering works with underwear and ktoonsez kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g35thrilla:
^ latest task ROM? Or just the kernel.

---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------

Hey so WiFi tethering should be working but can you confirm if it works for Canadian devices?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
Task kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] altrikdout21:
Tasks and liquidsmooth worked well for me. Now I'm on stock using power toggles which works very well, enables native tethering!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Death&co:
No problems with tethering here.

I'm currently running RC1 Liquid Smooth 4.2.2 and BMS Kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
ROM and kernel have to support it.

I'm not Canadian nor do I have Canadian service. So I can't confirm that. But I have a ton of Canadian users and have seen no reports of it not working. So that must mean it works just fine. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] boomski17:
Did you use the native tethering app? I installed Liquid Smooth 4.2.2 on my VZ S3 yesterday and I can not get the native tethering to work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] g35thrilla:
How do you install and flash a kernel. Can it just normally be done through twrp??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kplam7:
Over the past week I've flashed a bunch of different roms, CM 10.1, AOKP, SuperNexus, etc. and none of them I can get working for wi-fi hotspot/tethering. I'm also on Rogers and my i747 works just fine on stock rooted for wi-fi hotspot, just none of the AOSP ROMs I've tried.

My tablet or laptop will connect to the wi-fi hotspot, but no data is passed through.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drazik0711:
I've the same problem with LiquidSmooth v2.8. My laptop connects just fine but there's no data exchanged when trying to browse the web etc. Does anyone have any advise for this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nighthawk29:
Same here.

I have never once had tethering work when I am using a custom rom, only when I am on the stock Samsung firmware. I am on Rogers network in Toronto and have the S3 I747M and with any rom no matter which one I have tried it does not tether. The hotspot is active, my laptop and tablet can connect to the hotspot but no data is passed through at all.

I am currently running LiquidSmooth 2.9 with KT747 kernel and still nothing. Even before flashing the kernel it didn't work. Why can't I get this tethering working with a 4.2.2 rom on my S3? This is extremely annoying. I love the roms, since TW is slow and sluggish and just all around sucks right now but I NEED tethering so can anyone help me figure this out? I have also made sure the APN settings are the same now as it is on stock but it doesn't help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gutlessmerc:
Send me a private message. I have a solution for Rogers S3s. I had the exact same issue and its been resolved.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ajay74:
Friends

I'm using Cm10 nightly and I want to change my framework I've tried reframer .sh by propec using adb shell but my mobile went boot loop

Is there any proper way to change framework.

As I was doing this to enable ums mode in my Cm10 rom

I have tried cwm method to flash the zip also but the result was same
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Abhinav1997:
Which framework were you trying to flash?

Press THANKS if I helped,

Best Regards,

AJ
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ajay74:
I was trying to flash enable ums.zip for enabling my mobile to show usb mass storage mode As my mobile is showing mtp mode in cm10,

I even change the build prop before flashing where I change

persist.sys.usb.config=mtp

to

persist.sys.usb.config=mass_storage

Then I flash firmware my mobile soft bricked as it strucked in cyanogen mod logo
[Nexus 7 Q&A, Help & Troubleshooting] hettige677:
I just started using the Nexus 7 (WiFi) and I am on 4.2.1 and I am rooted. I rooted with the Wug's Toolkit. Anyway I want to update to 4.2.2 and I don't want to use any custom rom's, I just want to have an original update that I can flash without having to unroot. I have flashed my nexus with Clockwork Mod Recovery. Any places were I can get this rom and how I can install it?

Help Please!!
[Nexus 7 Q&A, Help & Troubleshooting] rudedog1979:
Hello there!

What about a little search? is a search bar in every part of the forum!!! :D

Anyway there you go:

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

Just don't get used to it :good:

Read the forum rules!
[Nexus 7 Q&A, Help & Troubleshooting] hettige677:
So I downloaded the zip but it won't install properly it says error code 7??
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
n/m
[Nexus 7 Q&A, Help & Troubleshooting] Leonhan:
That's because you are using a custom recovery. You can either flash a stock recovery or edit some files in the zip so you can flash it in the custom recovery.
[Nexus 7 Q&A, Help & Troubleshooting] bftb0:
Possibly, but probably not. In most of the reports that have been coming in - when the users actually report the full error message rather than saying something ambiguous like "I got a Status 7 error" - the problems revolve around altered/removed files in /system, or having a custom kernel (boot or LNX partition) installed. That suggests that the recovery version is not causing assert() failures.

The other thing to rememder is that the program that is interpreting the edify updater-script is the "updater-binary" program which is shipped inside the OTA - so it is virtually identical independent of the choice of recovery (other than perhaps kernel behavior differences).

Even though what you are saying here does only require being able to operate a plain-text editor and a zip tool, it's way above the heads of most folks who think that OTAs should work on non-stock ROMs. And I'm not sure how these folks would be better off with partially-patched ROMs. In any event, if this course is taken indeed a custom recovery would need to be used for this, as modifying the zip contents will break the OTA package signing, so the stock recovery couldn't be used.

The OP should just

- make a full nandroid backup of what they have now

- download the factory 4.2.2 images from Google

- extract the system.img file and boot.img images

( hint for windoze users: 7-zip understands .tgz files)

fastboot flash boot boot.img

fastboot flash system system.img

- reflash a basic SuperSU or Superuser root kit

Sort of crude, but it's a decent hack for the lazy or poorly informed. It won't "erase my data", but presumably it will break whatever it was that altered the stock system and/or boot partitions - the very things that are causing the OTA to fail on them with their rooted & modified ROMs.

If they don't like the result, they can simply restore their nandroid backup.
[Galaxy Note GT-N7000 General] jaguaralani:
I have first mentioned the problem here

Discussion - Stuck at Sammy Logo Issue on Official Jellybean ROMs

The method was first described here and here by RbbCHan

Then suggested to me by kopitalk

So here is what I have done " a step by step guide"

1-on a safe kernel, do all wipes+formats 9system,data, and preload".

2-reboot into DOWNLOAD mode.

3-connect your N7000 to PC (I use PC Odin V. 3.04).

4-start PC ODIN, untic "Automatic Reboot"

5-flash stock official LSZ rom

6-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).

7-reflash again.

8-when you see the word "PASS", restart into DOWNLOAD MODE ( holding vol down+home+power).

8-reflash again (3rd time)

9-restart you phone.

10-let the rom settle down, do your settings.

11-do a couple of restarts (legitimate ones, not by holding power for 7secs).

12-root your rom with the latest PhilZ LSZ kernel

13-restart into recovery, format data only "under mount and storage", then restart your phone.

Installed eybee's rom with mods, restarted automatically after mod3:cool:, and right now I am with a JB rom that does not stuck at sammy logo even when I force restart pressing the power button for 7 sec.

If you feel it takes a longer time on Sammy N7000 Logo, just repress power button again for 7 secs and it will boot up.

Hope this helps anyone who suffered bootloops as I did.
[Galaxy Note GT-N7000 General] dio62000:
Have you taken out the battery while Note was on? That's what causing bootloops, just rebooting not necessarily.
[Galaxy Note GT-N7000 General] zai89:
Will try and report...:fingers-crossed::fingers-crossed:

---------- Post added at 01:32 PM ---------- Previous post was at 01:28 PM ----------

on 13rd steep should I wipe data/factory reset or format data under mount and storage?
[Galaxy Note GT-N7000 General] jaguaralani:
mount and storage mate..
[Galaxy Note GT-N7000 General] arinsms:
the JB bootloader will help and are they missing in ur step?
[Galaxy Note GT-N7000 General] rraaka:
its in step 5 - the official rom has the JB bootloader sbi.bin
[Galaxy Note GT-N7000 General] eybee1970:
though I'm crossing fingers that this will work for everyone, but i doubt....this is completely weird from any logical point of view (especially these 3 flashes in a row...what will be flashed on 2nd or 3rd attempt that wasn't flashed before??)...but hey...if it works, ok ;)
[Galaxy Note GT-N7000 General] ThaiDai:
Your forgot step 14: turn around yourself 3 times spitting every turn in your preferred direction.

Sorry but I have to ask: is this still a developer forum with a technical/scientifical approach for problems and solutions?

Superstition reigns...
[Galaxy Note GT-N7000 General] fleckhansi:
AW: N7000 Official JB Bootloop - "3x Bombardment Odin Flash" simply works!!

If I would have the bootloop problem (actually I never faced any) I would definitely give this a try. Superstition or not, doesn't matter if it solces the problem, right? :rolleyes:
[Galaxy Note GT-N7000 General] jaguaralani:
This is really silly of you. We are all trying to figure out a solution even if a temporary one which might help hundreds if not thousands who are trying to use their phones promptly and who regret buying this n7000 with the famous ics brick bug and now the unstable jb roms which are OFFICIAL SAMSUMG RELEASES.

To all, there really should be a 'counter' somewhere, which explains the 'every other restart' that succeeds and does not cause the n7000 to get stuck.
[Galaxy Note GT-N7000 General] rraaka:
essentially we are just ensuring the new image sticks

coz there may not be a way to verify which bootloader we actually have even after first flash
[Galaxy Note GT-N7000 General] kopitalk:
Shame on you... We may not know what's behind doing it but it works. I hope you will get this broplem so that you will swallow your saliva back.
[Galaxy Note GT-N7000 General] ThaiDai:
I'm not ashamed and I do not feel silly because of my statement.

It's only my point of view and so I still think this is ridiculous.

If any member is positive about the results my comments never will change it.

But that won't stop me from commenting when rationality moves to the far side of the moon.
[Galaxy Note GT-N7000 General] dio62000:
I don't know if it works; installing the bootloader seems to work too to avoid soft reboot bootloops. But when I take out the battery while the Note is on I get the bootloop.

J, have you taken out the battery to test if it works? That's what I'm interested in right now.
[Galaxy Note GT-N7000 General] dafreaking:
Why does anyone take there battery out while the phone is on!? Can one magically change the batteries without switching off the phone?
[Galaxy Note GT-N7000 General] jaguaralani:
Ues, I have just done that replacing my stock battery with my 5000mAh, and it has worked just fine.
[Galaxy Note GT-N7000 General] dio62000:
Sometimes you need to take your battery out, e.g. when you have a crash and nothing responds to buttons or touch anymore. I won´t happen too often, but once is enough to get really annoyed, because this always happens when you least expect it.
[Galaxy Note GT-N7000 General] jaguaralani:
Yes, I have just done that replacing my stock battery with my 5000mAh and it has worked just fine.
[Galaxy Note GT-N7000 General] dio62000:
Ok, so you didn´t first shut off the phone, you took out the battery while it was still on? Now that may be interesting...
[Galaxy Note GT-N7000 General] Formhault:
If a system freeze occurs, you don't have to pull the battery. You can long-press the power button and voila, reboob™ takes place!

How do you guys call this... soft reboot, soft reset...? :confused:
[Galaxy Note GT-N7000 General] jaguaralani:
Forced restart mate, which is virtually the same as pulling off battery.
[Galaxy Note GT-N7000 General] Formhault:
I'm inclined to stand by ThaiDai. Circuitry... nowadays... doesn't work like that. If you flash the same kernel on your phone, three times in a row, it's not gonna work better than, for example, if you'd flash it only once. It's not like extra files are being added. It's not like the kernel is being "pushed" with more force to the flash memory.

So, from a logical and theoretical point of view, flashing XXLSZ with Odin for three times in a row should not, by any logic, "stick" better.

What is logical, on the other hand, is my next statement :

Taking out the battery = suddenly losing power. The same could happen if, for example, you're playing a very intensive game, over a 3G network, with the screen brightness to the maximum, with bluetooth and GPS turned on and constantly streaming data... but this scenario isn't really a likely one.

Android system shuts itself down when the battery has reached a critical level, so that actual power-outtage doesn't occur (phone has time to save data, clear RAM and shut down properly). When it fails to do so, the power just goes too critical... When that happens, there's this thing called fsync... which matters, apparently - at least according to THIS post of g.lewarne, (ex? :( ) kernel dev for the Galaxy Note.

That is the first thing I thought my be the culprit for all these bootloops / bootstucks™. We don't know whether fsync is enabled or not in this JB build... However, no one got bootloops / bootstucks™ in previous, leaked JB builds... right? So... maybe Samsung turned fsync on in test builds, but disabled it in the official ROM? Although it doesn't make sense (why would they do that)...

It's still just a theory. Being given no informations on why a phenomenon happens, you can only speculate...
[Galaxy Note GT-N7000 General] dio62000:
Last time I had one I had to take the battery out, as far as I remember (but things go fast when flashing new ROMs, may have done something wrong ;) ) not even the power button worked :mad:
[Galaxy Note GT-N7000 General] xperiacle:
In layman's level, this method may be ridiculous or irrational but I think technically it is possible that it may work. The old rom is like a stain that a single wipe can not clean, sometimes it needs 3 wipes, so to speak. We are dealing here with electro-magnetic "stuff" that we can not see so it is not irrational or ridiculous to assume that 3 flashes may wipe clean the the old roms digital "residue". If you are familiar with data retrieval from a hard drive whose data has already been deleted or formatted, then you may know that with the right tools and skill, it is still possible to retrieve the already wiped/deleted/formatted data (which is ridiculous in layman's level) so in order to ensure that nobody can retrieve the deleted data, you have to make at least 3 and preferrably 7 passes of "shredding" or formatting.

I already have maybe more than 20+ bootloops since LSZ was released flashing different roms and so and so. If this method works, then I've got to try it. Thanks for sharing. :)
[Galaxy Note GT-N7000 General] eybee1970:
assuming you are right, 3 times formatting and Wiping should do the trick, but not flashing 3 times in a row
[Galaxy Note GT-N7000 General] xperiacle:
Formatting and wiping using the patched kernel (which doesn't actually formats because formatting the old fashion way was disabled, it just deletes recursively) may not be enough. Letting odin do the wipes/formats (with the new bootloader) may be more effective wiping the traces of the old rom.
[Galaxy Note GT-N7000 General] Formhault:
Indeed.

Odin uses the... erm... old way of formatting (unsafe in recovery), which is safe (and more thoroughly) if done with Odin (correct me if I'm wrong, please!) so it makes sense.

Unless a Samsung update is released within the next two weeks... Or another fix is found... I'm gonna give this a try.

Sent from my Galaxy Note held captive in Chasmodo's Asylum
[Galaxy Note GT-N7000 General] rraaka:
if the purpose of the bootloader and bombardment is wiping then we have go through this ritual more than once !! :laugh:

im not up to it then im afraid . once was enough i would have thought...
[Galaxy Note GT-N7000 General] gl7:
This remind me of hard disk bad sector, sometimes fixable with low level format, hdat2, hdd regenerate etc... if the 3 flashes overwrite really fix the problem, the main problem maybe the rom hardware failing or weakening which fail or corrupt the data bits if sudden power off. is there an app to scan the rom like the example hd2 bad blocks fixs? so one can try scan for bad blocks when bootloops...

btw, running 3 (x) times/passes also apply to some high-end data wiping software for hard disk. maybe the few flashes to the rom will refresh the hardware bits.
[Galaxy Note GT-N7000 General] xperiacle:
It maybe possible to use the old abyss kernel or the gingerbread kernel to do the wipes/formating 3x and flashing Philz patched LSZ kernel and then flashing the rooted deodex LSZ rom. Or if Philz can make an unpatched kernel with his touch cwm recovery then I will give it a try. Maybe samsung have already fixed the mmc_cap_erase problem in the JB roms. Nobody knows because nobody tried but I may try if its available.
[Galaxy Note GT-N7000 General] fearkillerr:
Man galaxy note such a weird device, all this Boot-loops and Hiccups, XD
[Galaxy Note GT-N7000 General] M3TALLICA:
I don't think flashing 3 times solves the issue.

Some of my friends press 'CE' and 'ON / AC' buttons of calculators 4-5 times to clear previous calculations. Their logic is pressing it multiple times clears the memory / previous calculations completely.

My grandma used to checks the latch / lock 10 times. I never argued with her.

=)))))))
[Galaxy Note GT-N7000 General] eybee1970:
so time to 'force' Philz to give us the unpatched :D