yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy Note II] Tanamir:
So...

Noob was finally successful in reverting the phone to 4.1.1... It took three tries because the first time I just tried to revert without going into recovery and I ended up eating a bowl of boot loops, the second time, I just wiped the cache memory and still ate boot loops so, the third time I wiped all user data AND the cache and, PRESTO!!!! I am now running 4.1.1 and I believe I have also unlocked my phone ( say, is there an app that will tell me if my phone is unlocked?) but I don't have a sim card from another carrier to test with.... Now my next question is: If I am running this altered version of a stock ROM for Rogers on my (Supposed) unlocked phone, can I now go run the 4.1.2 AT&T ROM from MrRobinson and can someone tell me what the difference is between that ROM and the others from the list of Canadian carriers?
[AT&T Samsung Galaxy Note II] Tanamir:
Ok, I have a question... Wait, make that two...

1) Where is the flash counter located? Is it on the Download screen in the upper left hand corner on the second line underneath the red "Odin Mode" line?

2) If the answer to 1) is Yes, then tell me why that line on my phone says: CUSTOM BINARY DOWNLOAD: Yes (2 counts) ????

If those are the only ROM's that I have downloaded and used? and when before I flashed the ROM originally, it said "NO"...

hmmmm.... noob thinks that this is strange... but, eh, I'm just a noob, so I ask questions.
[AT&T Samsung Galaxy Note II] Darkshado:
Yes, that's the counter I'm referring to. Didn't you try flashing AT&T firmwares on there as well? Could be it, iirc the system partition flashes first, so it would only have failed at the modem image afterwards.

There's always Triangle Away for that.
[AT&T Samsung Galaxy Note II] Tanamir:
Ok, smartypants.... If the only ROM's I Downloaded were the ones from MrRobinson, and those ones supposedly had the fix so you don't get the triangle, how did I get the triangles? yeah, I tried to load the AT&T ROM, but it was the MrRobinson one.... I'm not trying to be facetious, just trying to point something out...

Can I use the AT&T 4.1.2 ROM to upgrade and what is the difference between that one and the Canadian ones in the MrRobinson list?

Thanks,

Tanamir
[AT&T Samsung Galaxy Note II] Darkshado:
Because from what I've understood the bootloader can tell apart files meant for a specific model. Which is also why modem cross-flashes fail in Odin.

If you feel like using AT&T-based ROMs and other things of that nature, we're stepping way off topic. But by this point you might consider throwing caution to the wind and looking into custom recoveries and modified ROMs.
[AT&T Samsung Galaxy Note II] Tanamir:
Darkshado,

First off, I wish to thank you for the time that you have taken to answer my questions, and for every question that you answer I have two more pop up... (Grrrr..The more I know, the less I understand...) But I would like to disagree with you about stepping way off topic on the AT&T ROM's.

On the MrRobinson thread that I found with all the ROM links for Canadian carriers also contained a set of ROM's for AT&T ( 4.1.1 & 4.1.2 ). I ask specifically about these two ROM's and what you might be able to tell me about the difference in the .md5 for that ROM ( 4.1.2 ) versus the .md5's for the other ROM's ( 4.1.2 ) for the Canadian carriers?

Instructions:

First, Download Image:

ATT Rom

January 2013 JB 4.1.2 New!

Mirror 1: root66_ATT_I317UCAMA4.7z

October 2012 JB 4.1.1

Mirror 1: root66_ATT_I317UCALJ2.7z

Mirror 2: root66_ATT_I317UCALJ2.7z

Image supplied by Kirbo20. Please thank him for his time in getting the stock image to me.

Bell Rom

January 2013 JB 4.1.2

Download: root66_BMC_I317MVLBMA3.7z

October 2012 JB 4.1.1

Mirror 1: root66_BMC_I317MVLALJ2.7z

Mirror 2: root66_BMC_I317MVLALJ2.7z

Telus Rom

January 2013 JB 4.1.2

Download: root66_TLS_I317MVLBMA3.7z

October 2012 JB 4.1.1

Mirror 1: root66_TLS_I317MVLALJ2.7z

Mirror 2: root66_TLS_I317MVLALJ2.7z

Rogers Rom

January 2013 JB 4.1.2

Download: root66_RWC_I317MVLBMA3.7z

October 2012 JB 4.1.1

Mirror 1: root66_RWC_I317MVLALJ2.7z

Mirror 2: root66_RWC_I317MVLALJ2.7z

Sasktel Rom

January 2013 JB 4.1.2

Download: root66_BWA_I317MVLBMA3.7z

October 2012 JB 4.1.1

Mirror 1: root66_BWA_I317MVLALJ2.7z

Mirror 2: root66_BWA_I317MVLALJ2.7z

Virgin Rom

January 2013 JB 4.1.2

Download: root66_VMC_I317MVLBMA3.7z

October 2012 JB 4.1.1

Mirror 1: root66_VMC_I317MVLALJ2.7z

Mirror 2: root66_VMC_I317MVLALJ2.7z

Look at the list above and explain the difference....

I appreciate your help...

Tanamir
[AT&T Samsung Galaxy Note II] Darkshado:
The AT&T and Canadian "Big Three" models are slightly different. SGH-I317 (AT&T) vs SGH-I317M (Canada). I'll go on a limb and say the hardware is identical, but the low level software, e.g. bootloaders and modem firmware, has some differences.

Those .tar.md5 Odin images are in fact .tar archives, with an md5 hash tacked on at the end for data integrity purposes, in case there was an error resulting in a corrupt download, it won't flash and possibly hard brick the phone.

The tar archive contains multiple image files meant for different partitions on the phone. The bootloader used in Download mode can tell for which device those files were meant and whether they have been altered or are unmodified Samsung files. It will flash the boot.img (which contains both the kernel and ramdisk), recovery.img and system.img no questions asked, but increment the "Custom binary download" counter as required.

Modem images, modem.bin, on the other hand, will fail to flash. Which isn't a bad thing; if you're up for some reading, dig up my posts about flashing the I317M modem on my T889V.

What has happened is that you flashed AT&T ROMs, which didn't match the model number Download mode was expecting. The flash gave a "Fail" message in Odin because it halted at the modem.bin image, but it did write other parts of the image beforehand.

Oh, and unless you need some AT&T or T-Mobile specific feature (e.g. Wi-Fi calling) you'll notice most custom TouchWiz-based ROMs are based on international LTE model GT-N7105 ROMs because they're updated much more frequently, and don't have some of the limitations their US counterparts do. (Canadian ROMs are in between: updates aren't as frequent, but you usually have the same options as the international ROMs do.)

About the Samsung ROM build numbers: there's a logic to them.

Let's look at I317MVLBMA3 for instance:

I317M: Model

VL: Region/Carrier code. VL has been consistent for a few multi-carrier models launched in Canada now: SGH-I317M, SGH-T889V, SGH-M919V, SGH-I337M. Otherwise:

Bell: UG

Rogers: UX

Telus: TL

B: Not sure, it changed from A to B going from ALJ2 to BMA3, and the Android version did increment from 4.1.1 to 4.1.2, could be a link.

M: Year 2013

A: January

3: Revision. Starts with numbers, then letters.
[AT&T Samsung Galaxy Note II] Tanamir:
(see?.... more questions.... told ya so...)

ok, I'll ask this one again... How many variations of the Note II exist??? and why the differing model numbers? for example, you are running a Note II (SGH-T889V), and I am running a Note II (SGH-I317M), Why does Samsung release the same phone with completely different model numbers? (You don't have to answer that one, because its beside the point). I have a difficult time trying to relate how the ROM's are specific to a carrier, so I am going to try an analogy. I build and fix computers for sh**s and giggles so how about this: Its as though I am building six desktop computers, each one having the same mainboard but each computer has a unique BIOS chip that controls what is available on the MB. All six computers run Windows, but the BIOS chip loads instructions that are critical to the functioning of the MB. The difference in buying a pre-built computer from Compac or Dell, and building the same computer yourself. The BIOS chip in the pre-built unit will be a Compac or Dell BIOS as opposed to a BIOS found on a MB that you would buy alone... Hopefully I'm not too far off the mark. That being said, I'm going to a Telus or Bell outlet to see if I actually unlocked my phone, then I will flash the Rogers 4.1.2 rom from MrRobinson if the phone is unlocked.

At that point I might ask questions about Custom ROM's...

Thanks, I'll get back to ya later...

Tanamir
[AT&T Samsung Galaxy Note II] Tanamir:
So I guess that asking for a "One size fits all" kind of ROM is out of the question? Based on what you have been explaining to me, it sounds like the cellular networks in conjunction with the cell phone manufacturers are trying to pigeon hole the devices so as to limit our freedom with respect to the technology we purchase. I have been able to unlock my phone ( I went to a Bell store and asked the CSR if he had a microSIM that he could swap out with mine from Rogers... He took one out of his phone, I swapped it with mine and restarted the phone and he called his number, and it worked on my phone) and root my phone, so I can get rid of some apps that I don't like, but really, next time around I'm going to get an unbranded and unlocked phone straight from the manufacturer. As far as the flash counter goes, I used "triangle away" and now the flash counter says "NO". Very cool....

Thanks,

Tanamir
[Verizon Samsung Galaxy S III] GatorsUF:
I am planning to switch from MOAR ROM 5.0.1 VZW18 to CleanROM_Seven. I have had a few issues with my internal SD card (/0/ folder etc..) and wanted to make sure there was no special thing I should be doing between 4.1.2 ROMs. I am fairly certain the /0/ thing is based off of the 4.2 ROMs. To switch all I need to do is:

1. Factory Reset

2. Flash New ROM

Correct? I have been wiping the internal SD card just because I was testing out ROMs and I had nothing on there, now I have lots a pictures and things I'd like to keep.
[Verizon Samsung Galaxy S III] andybones:
wipe system, cache, dalvik cache, data (also known as a full wipe)

then flash ROM

no need to touch internel or sd-card for wiping purposes.

the 0 folder is only present for 4.2.2 ROMs, which right now is only AOSP ROMs.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
Hello friends,this is my first post in xda

Today i am gonna share how to fix touchscreen problem in xperia mini pro

Many users have this problem after flashing wrong rom i have too.I have tried all soution in xda forum and i can't fix it properly..

There is a working solution in xda

It is:

First flash xperia active rom (you can't install xperia ftf,it shows a error) You need custom rom

Then touch worked

Then flash cyanogenmod 9 or 10

I have used this method for 5 months,cm9 is good but it has no proper indic language support,Then i used cm10,it is not stable yet

Specially no sony xperience :(

Then i find out a method how to work official rom(ics) in Xperia mini pro,also U can use this method in custom rom,I have created a flashable zip for .587 rom then i flashed

Yahoo it is working

You have to change two files

Softwares u need:

WinRAR

Notepad++

And Brain :D

Open custom roms zip(e.g:Realics R6,smart xperia rom,Xperia ultimate HD,Revolution ics HD)

Showing this tutorial with revolution ics HD (author & port by:Saqib nazm)

Open revolution ics hd rom zip with winrar

s18.postimg.org/iay1he9uh/Screenshot_10.png

Then go to aroma folder>active>etc>firmware and extract touch_satsuma_hitachi.hex

Then go to aroma folder>minipro>etc>firmware and delete these files(just use keyboard del button):

s24.postimg.org/4b0fyfcat/Screenshot_11.png

Then u need the extracted touch_satsuma_hitachi.hex

Drag and drop this file in firmware folder of mini pro,Save any changes if need

Then you have to edit hw_config.sh

You can find this in aroma\minipro\etc

Open this file with notepad++

Delete this lines

s14.postimg.org/l5vnia6xd/Screenshot_12.png

Then copy this:

dev=/sys/devices/platform/spi_qsd.0/spi0.0
app_id=`cat $dev/appid`
case "$app_id" in
"0x0207")
fw=touch_satsuma_hitachi.hex
;;
*)
fw=touch_satsuma_hitachi.hex
;;

And paste this in there(you can find it also in xperia active hw_config.sh,Just copy these lines nothing else)

Then save that file with notepad++

Then flash rom,everything will work

You can do this with all rom just change this two files

Happy Flashing :)

Sorry for my bad english

Can anyone make a .62 Gingerbread a flashable zip ?? That will be helpful
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Saqib Nazm:
Great Bro :good: as many people reported that they are touchscreen is not recoverable by following many methods this should really help them :highfive:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] UchihaDareNial:
Nice to see someone made a more convenient but harder as required a lot of tutorials

Anyway,always double check before flashing the custom tom that you downloaded whether it is for your device or not...just my 2 cents :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
HMM i flashed gagans rom,in rom thread i see xperia mini pro poster,he didn't mention xperia mini pro there,i pm'ed him is this rom work in xperia mini pro?? he said yes,then i flash and got this bull**** problem .. :(
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] dude_xperia:
THankxxxxx

it worked:cowboy::laugh::laugh::laugh: woeeeee haaaa yaahoooo Thank u My Dear
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] UchihaDareNial:
Well probably the rom owner maker faults
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mihahn:
Thanks for the great method! Hope it works for the guys with a bricked touchscreen ;)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
don't know,u can test this,

Please inform me if it works :silly:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
Thanks for your nice comment bro :cowboy:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] afigienas:
God damn if this will work i'll be happy!! cause mootherfu*kers voided my warranty because of this,they say i broke it physically! assholes, i knew that this is firmware related..god damn noob service :)

Also i see that you have no idea about scripts :D by looking at code you're suggesting to use.

In fact need to change only to this:

dev=/sys/devices/platform/spi_qsd.0/spi0.0
app_id=`cat $dev/appid`
fw=touch_satsuma_hitachi.hex

cause we dont need any cases in this situation, we want to force to use this firmware.

EDIT2: looks like i fixed it.. by using FlashTool and flashed oficial ROM from Sony twice.

EDIT: ANyways this method doesn't help for me.. :( It's either depends on kernel, cwm or else.... for me doesnt work
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] olafsb:
FINALLY!! MY PHONE'S BACK TO NORMAL!! THANKS TO MR. bangladeshi!

but i'm still using custom rom, couldn't figure how to make a flashable zip of an FTF :'(
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
You have to unlock bootloader first,First flash stock mini pro ftf in ur phone then turn on your phone,Your touchscreen will not work use hardware keyboard to go to menu settings then turn on usb debugging,Then u can unlock your bootloader using flashtool :victory:

Contact me over fb:facebook.com/ashikur.tipu

Sorry for my bad english :silly:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
Its better to use ics custom rom because official fw have some bugs,U can use gingerbread,Sandy7 created a thread for stock GB,Just download that,Don't change anything in zip,It is working cause sandy bro deleted touch drivers and it is working :D

Sorry for my bad english :silly:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ersan18:
Wow thanks buddy :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] parth.chandak02:
sorry but i need to ask this...

i did all your steps exactly as written but no luck on restoring my touch screen...

my touch pad is also not responding...

i just need to ask while in the aroma installer do i select my device as st17i instead of my sk17i??

because i tried installing it with sk17i but unfortunately my touch is not responding... pls help i really need my device to work right...

thanks :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
It should work if u follow my process,You have to select sk17i :rolleyes:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] quest18:
Thanks works perfectly on Xperia SK17

Thank you very much friend, everything worked perfectly in Xperia SK17
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] matiasdelafuente90:
Thanks you!!!!

Oh my god! YOU are my new GOD! Hahaha thank you very much!!! My SK17a just have 1 Week and i bricked my touch, I'm happy, very happy now! Greetings from Argentina! :laugh::laugh::laugh::good::good::good:;)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] jangid:
confused with touch_satsuma_hitachi.hex file

how to extract touch_satsuma_hitachi.hex ??

with winrar it is a hex file .... ??

by the way i tried to extract it with 7z !!

no archieve found it says ?? what should i do ?? now plzz help
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Marília de Oliveira:
Thaks

:good:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] pagan_1:
Request For The Same Fix For Xperia U

Kudos for the working touchscreen solution! Could you please mention the procedure for modifying the touchscreen files for Xperia U as well. I'll be greatly thankful and obliged, my friend. Moreover, in zip file of Custom Roms of Xperia U, there is no folder called "Aroma". Please if you can, post a solution to fix touchscreen for XU as well.

I am suffering from the same issue of wrong ftf flashing that makes the touchscreen unresponsive. I have tried flashing different kernels and roms including the stock GB and ICS roms but nothing worked. :( :(
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
Sorry bro :( i can't help,i do not have this device

Sorry for my bad english :eek:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
:good:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] LikkiHalili:
sk15

can u make for xperia mini sk15 plss :(
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] burnin.dezire:
Xperia Mini Pro Touch Still Not working

Hi...

thanks for the wonderful toutorial....

This is how it started i installed the cust rom cm 9 and was very much unhappy so wanted to switch back to stock so...

i accidently selected xperia pro 2.3 firmware and flashed that firmware on my xperia mini pro...

and i didnt realised till the time i flashed it completely...

i started the phone then noticed that sony ericsson logo was much bigger and then check the logs of Flashtool saw that OMG ive now done something very very wrong and worng...

i tried all the steps from the threads hybrom custom kernel flash reflash stock firmware etc etc ...

everything is unlocked like the bootloader...

i can install any and every comptible firmware on my mini pro...

BUT MY TOUCH DONT WORK NOT EVEN THE BACK AND OPTION TOUCH PAD...

only home button works... and keyboard works, volume and power.....

i follwed ur steps this thing works but the touch is very very very very slow and if i want to use the back button i mean the touch pad on screen for back... i have too keep on pressing it 8 to 10 times... then it respons like a tortoise....

plz suggest anything what to do... how can i reprogaram the phone or do nething nething..... :confused:

please gus help plz XDA is full of Genius member and visitors plz suggest fix for this problem
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
is cm works fine ?? :confused:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] burnin.dezire:
inside eneadsin

yes the cm work but the problem is with the touch pad button the back and the option they do not respond fast... i need to hit many times the back button...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
it seems that it is hardware problem,try flashing xperia active kernel then flash mini pro kernel ...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] aswan_tepces:
​

how to flash this rom?touch screen not working so i cannot root and install cwmplease help me??
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ArmanKhan:
Thanks a lot

It worked for me... Thanks
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Gustavolww:
Can I do this in Live Walkman?
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] oiwnos:
+1 on this... can i do it in live with walkman? do you think something should change in the text?

ultimate 5.01 messed my phone... and he doesn't even reply... i would really appreciate the help.. as the guy above me as it seems :)
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
If there is no other way take risk and follow my way :o

don't forget to inform me :D
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
It will be great if this process works with lww,if there no chance of fixing ur device try my process

Don't fear because your touch driver is already broken :(

Don't forget to inform me :cowboy:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
use hardware keyboard to find out ur imei then using physical keyboard go to settings and mark usb debugging,then use flashtool for unlock bootloader,then download rage kernel and flash it via fastboot,download any rom from thread and change files following my tutorial,put it in your memory card and flash it via cwm

It should work :silly:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] bangladeshi:
Great :cool:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] oiwnos:
Lucky guy....I am waiting for mine..I'll try 2 to 3 different roms.. the Op's procedure has given me hope
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] hungdoan95:
Thank you bro so much
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] oiwnos:
i have lww.. i took ultimate 2.02 ... did the precedure.. and i had a little hope because i saw that it recognised the number 8 when tried to push the pin... and that was it,nothing else . i believe that i am a special case because my wrong rom was the ultimate 5.05 for arc ,arcs and pro... and not a rom for mini, lww , and active... i believe it messed up a bit extra my Lww... i know it can't be hardware because it happened the moment i flashed the rom... but 3rd day now and nothing .i am so sad .. so sad

can you tell me what you did? any ides? what kernel... what you did before or after? anything
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] Arrowblue:
take sk17i ftf and flash it via flashtool in flashmode

2nd you have to unlock your boot loader use flashtool for unlocking the bootloader how you unlock the bootloader:

when your device is on nevigate via keyboard to devlopment tools and tick usb debuging on.

then connect your device through usb and open flashtool and click on pluggins there is bootloader unlocking it wil tell you what to do further.

3rd once you have unlockedboot loader flash any custom kernel that has cwm in it.

so then you have cwm and unlockedboot loader you can flash any rom you like.

---------- Post added at 06:51 AM ---------- Previous post was at 06:36 AM ----------

thats not hardware problem. i did flashed xperia Active kernel got bootlooped, then i flashed mini pro kernel still touch responce is very low.

i am 2nd guy who has the lack of touch screen. Touchscreen and back button wont react how it should even in cwm recovery same issue. any other suggestions?

tried other kernel as well still same issue.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] oiwnos:
I am trying things to on my lww.I got a few results , recognising some pushes when I played with op s method and the ultimate 5,01 that messed my phone. I am testing the method with the folder for the Xperia pro that I chose back on Friday and did the mess up. Nothing yet
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] burnin.dezire:
Yes my friend... i also face the same problem tell me how can i restore back the original touch which i use to have my fone is bricked since 7 weeks... i tried this step as well very confused what to do... plz help...