yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II General] proxlwt:
Linaro cm11 20140219

devil-2 2.4.6

selinux disable
[Galaxy Note II General] silentvisitor:
I am currently using Regius ROM by [MENTION=4353853]ees552[/MENTION] and I found it to be The Best one out there. Dev has put a lot of work and time in it. Load of small and nice changes. And super smooth with solid battery life.
[Galaxy Note II General] mati4455:
AOSB

I decided to take no-TouchWiz ROM. Now - I'm using AOSB 1.3, It is very fast. Without useless many Samsung Apps.

I only miss Action Memo and Scrapbooker from Note 3.
[Galaxy Note II General] Blakebn2012:
Some awesome ROMs, keep them coming I liked the Regius one.
[Galaxy Note II General] Skatterkid12:
Pheonix 4.3 touch wiz rom smooth ,fast and stable,very reliable rom
[Galaxy Note II General] dcpathak:
Hi dabenaute,

I'm looking for pre-rooted, deknoxed N7100dduena1. Where can I get it? Since you are using it, please throw some light.

regards
[Galaxy Note II General] dabenaute:
Hello,

look at herehttp://xdaforums.com/showthread.php?t=2627419;)
[Galaxy Note II General] dcpathak:
Thanks. I also reached at this thread using search but then got confused since the download link says: "Sri Lanka version" :o
[Galaxy Note II General] dabenaute:
It is not a problem,it is the same prerooted rom. Download it

"Envoyé depuis mon GT-N7100 avec Tapatalk"
[Galaxy Note II General] dcpathak:
Thanks button pressed :cool:
[Galaxy Note II General] dabenaute:
You are welcome?

"Envoyé depuis mon GT-N7100 avec Tapatalk"
[Galaxy Note II General] dcpathak:
Just one more query: The modem version as per sammobile should be "MODEM: N7100DDENA1" while this rom has MODEM: N7100DDEMK1.

Hope it shouldn't be a problem.
[Galaxy Note II General] dabenaute:
this mdem(mk1) is working fine on my phone:laugh:
[Galaxy Note II General] tweeny80:
Sheesh - I spent a good 2 hours today getting Hurricane v10 with Note 3 mod install up and working.

I love Wesa's ROMs but his decision to not merge N3 mod means I curse and swear at my phone every time he has a new release... there are always dramas making everything work in harmony!

View attachment 2607116

sent from my mobile
[Galaxy Note II General] MysteryE:
I am using Ditto Note 3 rom.

I want to know is there any way to enable soft keys on touchwiz rom? Kinda interested..
[Galaxy Note II General] Reled:
I Use ProBam!

Love AOSP Roms!

Bye!
[Galaxy Note II General] hungimahar:
Android Revolution HD 19. 4.1.2 seems to have best battery life to me
[Galaxy Note II General] dragonw:
Using dn3 rom ? amazing
[Galaxy Note II General] Alexsandra:
I am using DN3 Rom made by E-Team. This rom is fantastic and is full of NOTE 3 features. I love it.
[Galaxy Note II General] Alexsandra:
How long does your cell phone last?

---------- Post added at 02:36 AM ---------- Previous post was at 02:33 AM ----------

Wow your desktop looks pretty. How does you make it? Custom launcher?
[Galaxy Note II General] ipsuvedi:
The one and only

Tamirda's Phoenix Rom v17

FULLY LOADED!!!
[Galaxy Note II General] bashar.abu.diak:
Phoenix V17

View attachment 2619123
[Galaxy Note II General] Jiestars_OH:
DN3 V.4

What a nice rom!
[Galaxy Note II General] gangsterx22:
Dito

Im using DitoN3 v4 awesome rom :victory:
[Galaxy Note II General] mehmetpara:
Ditto V4
[Galaxy Note II General] edong23:
DN3 amazing rom
[Galaxy Note II General] BenDarevan:
I'm using Samsung's stock ROM 4.3, with TSF Shell instead of TouchWiz :)
[Galaxy Note II General] Androidwizzard:
Blacktox :cool:
[Galaxy Note II General] nickmrad:
currently im using MoKee, but im downloading Pac-Rom nightly right now :)
[Galaxy Note II General] DönerXXL:
N7100XXUFNB4 with Aircommand - Knox free & insecured Kernel

Base on leaked N7100XXUFNB4 Android 4.4.2 Version.

This Rom is from "cosmyndemeter".

Runs actually quite good.

I'm very happy with it.

Sorry, google Translator ...
[Galaxy Note II General] mbdjeo35:
NB6 when it was published.

I m using DN3 4.4.2 V4.1 :good:
[Galaxy Note II General] Lukapetr:
I use omni rom
[Galaxy Note II General] Androidwizzard:
Seems to be an unknown leak..... just a few days ago
[Galaxy Note II General] mbdjeo35:
Thnx..Im not seeing sammobile. .

GT-N7100 cihazımdan Tapatalk kullanılarak gönderildi
[Galaxy Note II General] mpsnet:
Ditto N3 4.3 v3.2.1
[Galaxy Note II General] Cocolopes:
Where can I find that NB6 rom?
[Galaxy Note II General] Androidwizzard:
As far as I know there is no rom on that built, only a N3 modpack.
[Galaxy Note II General] amolsonthalia:
black tox

i use black tox v4.0.1 ,it's a kit kat rom :)
[Verizon Samsung Galaxy S III] snypaafk:
I bought a verizon 4g lte galaxy s3 16gb I wanted to put it on at&t's network with the straight talk bring your own phone thing. So I got it put the SIM card in activated it then I got Samsung kies and updated my android to 4.3 then I rooted it successfully. But I am only getting edge data speeds and its really slow. I have looked through these forums and googled so much but I really can't find anything. The straight talk box said I could get lte speeds and I really want to know is there a way to get them or at least 3g speeds or just anything faster than edge I think dial up is faster. I will happily donate a good sum if someone can help me with this problem
[Verizon Samsung Galaxy S III] buhohitr:
I think your best bet is sell the Verizon S3 and get an ATT S3 instead. (you could sell on Ebay and get an ATT S3 for about the same price). Unfortunately, it can't be done as Verizon uses CDMA and ATT uses GSM. Means radios are completely different. The most you can get is Edge data speed.
[Verizon Samsung Galaxy S III] snypaafk:
k

It gives me the option in mobile networks to switch to gsm. You absolutely sure there is nothing I can do to increase my data speed. I do have it rooted with supersu titanium backup lucky patched build prop editor and apn back and restore
[Verizon Samsung Galaxy S III] buhohitr:
Unless someone could hack the radio, up to now..none. So yes, the most you could get is edge.
[Verizon Samsung Galaxy S III] snypaafk:
another

OK one more thing i really need to ask. i have a choice to get a at&t galaxy s3 now if i get that phone and put the straight talk sim for the LTE will it work on this phone like it did not on the verizon phone. will i get the lte data connection or edge like i did with the verizon phone. just trying to get some light on this subject i dont want to buy the other phone if im going to be in the same position. im still donating by the way this place is very helpful and resourceful
[Verizon Samsung Galaxy S III] buhohitr:
AT&T is straight talk so shouldn't be any issue. I found a thread here you can read up on how to set APN for straight talk http://xdaforums.com/showthread.php?t=1781935

BTW: Straight talk also offer a "straight talk S3" which using LTE without any modification.
[G2 Q&A, Help & Troubleshooting] Ryanzirra:
I have noticed in the last couple weeks the glass has started to lift it would look like on the bottom of my phone wondering if anyone has seen this and warrantied on it.
[G2 Q&A, Help & Troubleshooting] Brava27:
So you create an account to ask this in the wrong section of XDA?:mad:
[G2 Q&A, Help & Troubleshooting] s1mpd1ddy:
I have not but that definitely sounds like a warranty claim to me
[G2 Q&A, Help & Troubleshooting] Ryanzirra:
I actually answered a question another time. Plus I thought I was asking a general question in the general section of the g2 forum. Is this the incorrect place for my question.
[G2 Q&A, Help & Troubleshooting] naturecannon:
So you go out of your way to comment and be a ****, yet cant be a helpful commenting **** and point him to the Q&A?? That is just being a straight up miserable ass!! 3 posts new and your an ass to the new member...... what a way to welcome a guy and represent the XDA community!!

The forums may look familiar to us...... but to a newcomer .....
[G2 Q&A, Help & Troubleshooting] Brava27:
That is how I learned, the hard way :laugh:
[One (M7) Q&A, Help & Troubleshooting] vmcp:
So I can't seem to find a solution to my specific issue. A little background first. I was on Modaco switch beta 13 and decided I'd move on to something else because 1) hadn't been an update for quite a while and 2) I really didn't switch back to Sense except when I wanted to play around with Zoe. I restarted into CWM recovery and tried to flash CM 11. It gave me an error and I realized I was downlevel on CWM recovery. I tried to flash an updated CWM and now only have access to fastboot. When I try to boot to recovery it gives me the HTC splashscreen and hangs. I tried TWRP, CWM, and stock with the same results.

Checking fastboot getvar I noticed some really strange entries. serialno and modelid were corrupt. Here is the output of fastboot getvar all

# fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.1540.3
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ߞ�X�C
w\	`2�#
(bootloader) imei: xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.063s

# fastboot getvar mid
mid: �
finished. total time: 0.002s

# fastboot getvar serialno
serialno: ߞ�X�C
w\	`2�#
finished. total time: 0.002s

I read the following post to recover my serial number

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

I don't believe I had the ENG hboot so I get the following:

fastboot oem writemid PN07120
...
(bootloader) [ERR] Command error !!!
OKAY [ 0.012s]
finished. total time: 0.012s

# fastboot oem writeserialno 1234567890
...
FAILED (status malformed (0 bytes))
finished. total time: 1.000s

I tried flashing the ENG hboot, but....

# fastboot flash zip ENG_hboot.zip
sending 'zip' (475 KB)...
OKAY [ 0.242s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s

Yep, catch 22. Corrupt model ID, so it won't flash.

Another interesting thing I noticed was the 2nd line on the display in fastboot

**** UNLOCKED ****
M7_UL UNKNOWN SHIP S-OFF RH
CID=BS_US001
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
...

Anyway one of the messages in the forums said that once they resolved the model ID and serial number everything worked.

Unfortunately this is my main phone and I'd like to use it. Not very useful right now. Anyone have any ideas?
[One (M7) Q&A, Help & Troubleshooting] alray:
Maybe you can edit the android-info.txt of the eng hboot. I.E replacing the ''MODELID: PN0710000'' for ''MODELID: ********* '' don't forget to add your CID too (BS_US001). Or maybe replacing the MODELID with your corrupted MID: (MODELID: ï¿½)

Which eng hboot are you trying to flash? There are some rumrunner hboot with eng commands set (full set of fastboot oem commands) here: http://rumrunner.us/hboots/

or maybe with the eng hboot from here

edit: Did you erased cache after flashing recovery?

if you can get recovery to boot then you could use this tool to change MID

did you tried a ruu.zip? even if im almost sure it will output the same model id error...
[One (M7) Q&A, Help & Troubleshooting] vmcp:
I was actually thinking/wondering about that. I guess that'll be my next step. I wasn't sure what to put for the MODELID since mine currently is corrupt. But I suppose I could try both. Good idea.

I have the ENG hboot from the 2nd link. I haven't tried rumrunner hboot. I'll d/l and give that a go too.

Yes, I did erase cache. Don't know if I need to, but usually do that every time I try something.

Yeah, saw that thread too. I thought it'd be easy to do if I had adb/recovery.

Yep. same result.

Thanks for the ideas, I'll give 'em a try.

EDIT: So I tried the rumrunner hboot and the ENG hboot.

# fastboot flash zip ENG_hboot.zip
< waiting for device >
sending 'zip' (474 KB)...
OKAY [ 0.241s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.648s

I got the same thing even when I tried to add the corrupt entry in the android-info.txt. Is there any way to bypass the model ID check?
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
DO NOT lock bootloader or go S-ON.

You should flash the HTC DEV edition firmware. Also use a different computer/USB/port to ensure this problem is in the phone
[One (M7) Q&A, Help & Troubleshooting] vmcp:
Yeah, no joke!

Yes, I tried the RUU from HTC's site for the developer edition and it claimed my battery was low. I'll charge and try again.

It was a good idea to try a different computer. I had already tried two different USB cables and a different port. All with the same results. Even the other computer gave me the same response.

So I had a few ideas. 1) modify the fastboot source to ignore the error for incorrect mid and flash anyway. After trying a few hacks with the code I read the protocol.txt and determined that it wasn't fastboot that was complaining but the bootloader. So that left my other idea (which was actually the first idea I had). Find out what that gibberish was and put that in the android-info.txt as my modelid then hope the bootloader did a compare with the gibberish I had in the android-info.txt. Unfortunately that didn't work either. I re-compiled fastboot with a few mods of my own so I could get the full details of the gibberish. I modified the output to give me the hex values of what the phone thought it's serial number and model id was. Here is the output:

# ./fastboot getvar modelid
modelid: �
b8
finished. total time: 0.002s

root# ./fastboot getvar serialno
serialno: ߞ�X�C
w\	`2�#
df9ef4588043d60a775c096032ea23
finished. total time: 0.002s

So I even tried an android-info.txt with the hex b8 value ctrl-code value, not the string b8, and got the same result... :mad:

Oh and yes I also tried with the wildcard modelid: *********

Same result.

# ./fastboot erase cache
< waiting for device >
erasing 'cache'...
OKAY [ 0.071s]
finished. total time: 0.071s

# ./fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.042s]
finished. total time: 0.042s

# ./fastboot flash zip ENG_hboot.zip
< waiting for device >
sending 'zip' (475 KB)...
OKAY [ 0.241s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.645s
[One (M7) Q&A, Help & Troubleshooting] nkk71:
looks really messy in here!! :crying:

is there any way you can get to an "adb shell" (custom recovery or booted ROM)?

you have "(bootloader) version-bootloader: 1.44.0000"

can you please try

fastboot boot <name of custom recovery>.img

if you can get to adb working let me know...

---------- Post added at 09:47 PM ---------- Previous post was at 09:29 PM ----------

though just for info, last (actually, one and only attempt with such corrupt partitions), didnt work :(

FYI: http://xdaforums.com/showpost.php?p=50067052&postcount=30
[One (M7) Q&A, Help & Troubleshooting] vmcp:
I tried this but got to the same white HTC splashscreen. Just sits there. Never seems to make it to recovery.

I've tried ADB commands, but it appears it isn't fully loaded so I'm not able to connect via ADB. I'll try flashing the RUU, but it sounds like that other person in that thread didn't have good results even after a successful RUU flash! :crying:

I'm really starting to get worried that there isn't much I can do to fix the issue. I'm going crazy without a phone.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
I know!!! Spent 3 or 4 serious teamviewer sessions with him, after getting android-info.txt "fixed" (for that MID, if you can call it that), and successfully fully flashing ruu (from a to z), still nothing.

and without able to get (and eventually, if possible, write) to the specific partitions in question, then it looks like it will need a motherboard replacement.
[One (M7) Q&A, Help & Troubleshooting] vmcp:
uh oh! Perhaps the only saving grace for me is that I have an unlocked bootloader. I read about using hexedit to make a malformed android-info.txt. Perhaps I should try that. Although I'm a little worried because I kinda thought I tried that. But wasn't able to flash the ENG bootloader. :eek:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
check

ROUND 2: was able to create a "good" (as you mentioned "malformed" android-info.txt), and able to flash anything and everything in ruu mode

ROUND 5: got the bootloader unlocked

==> still no joy

if you can get to read / write partitions, let me know, I know which ones i'm after, though only through adb; if there is a way doing it in fastboot i would love to know.

---------- Post added at 11:45 PM ---------- Previous post was at 11:18 PM ----------

hmm, am i thinking of what i'm thinking? would that even be possible?

OP

[MENTION=1283405]ayk33[/MENTION]

i'm gonna check something tomorrow

[MENTION=1283405]ayk33[/MENTION] you still have that phone?
[One (M7) Q&A, Help & Troubleshooting] vmcp:
This is kinda scary. Looks like the exact same issue the other guy had!

So I found out I had a special char before the proper hex number. So I was able to flash the ENG bootloader. I've set my serial number and model ID via fastboot oem write* commands. Now getvar shows correct information:

# ./fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.12
(bootloader) version-misc: UNKNOWN ENG S-OFF
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN07120
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4239mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!

Although all is NOT good. I still think that the model id is messed up somewhere. From the bootloader if I select "barcode", it displays correct IMEI and S/N. The Model ID is still all jacked up and has all sorts of gibberish. I don't get it because the getvar mid displays the correct model ID (PN07120).

I flashed recovery and tried to boot to recovery (also using the command you gave me), but hangs in the same spot. Still no ADB access! :crying:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Mid is 9 characters!

I'm gonna check something tomorrow... wicked!
[One (M7) Q&A, Help & Troubleshooting] vmcp:
Ah, that could have been my problem. I re-wrote the mid by the following:

# ./fastboot oem writemid PN0712000
...
(bootloader) Start Verify: 0
OKAY [ 0.073s]
finished. total time: 0.073s

But the model id is still messed up on the barcode.

One other thing to note is it still shows UNKNOWN instead of PVT for version-misc. I'd guess that be causing problems too. Sounds like more than just the mid and serialno got corrupt.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
So any updates? The real problem is that the partition that got corrupted contains a lot of info, that cannot be found anywhere else on the phone (not only MID and serial number, much more)

I even think I've thought of a way to rewrite that partition, but the question is: with what information (MID, PID, s/n, etc).

Do you still have the box of the phone? (some of that info in that partition is on the original box, but not all of it)
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
Are you thinking mmcblk0p6, the mfg partition? I think that could work by dumping a known good one, flashing over the corrupt partition in fastboot or recovery and then using eng hboot to rewrite original sn, imei, mid, cid, etc.

Imei is etched on sim tray, other info can also be found in a couple of other partitions.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Yep, ;) exactly :good:

CID and IMEI, not worried about, the original ones can be found in two other partitions (unless CID was changed, but of little consequence), the bad ones (that don't seem to be anywhere else), are: MAC (hmm), MID, S/N, PID and the others I don't even know what they mean

and would the rest of the parameters in that partition (board version, gains, etc) matter.

PS: unfortunately can't seem to get to recovery in any way with a corrupt p6, trust me I tried
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
But fastboot is OK? If so, eng hboot has a lot of commands, maybe possible to flash mfg info into p6 that way. Don't have access to my laptop atm, but can check it out later if you don't get to it first. ?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
actually, I was thinking of simply:

fastboot flash /dev/block/mmcblk0p6 <name of good p6>.img

(or /dev/mmcblk0p6 or mmcblk0p6, whatever would work)

but I would really like to pull the corrupted one first, since so many parameters are repeated in p6, then if it's only partially corrupted, one could (theoretically) reconstruct it.

Problem is, I have no idea how to "dd" it out, using only fastboot. in ENG hboot there are commands, but I've found zero (concrete) information about their use.
[One (M7) Q&A, Help & Troubleshooting] SaHiLzZ:
If the partition can be pulled using adb then it can be compared to a working file and being right information be inserted and written back to the device that is my theory.

sent from my mobile device

---------- Post added at 02:14 PM ---------- Previous post was at 02:13 PM ----------

EFS professional allows this on samsung devices. Someone will need to check if the same is true on htc

sent from my mobile device
[One (M7) Q&A, Help & Troubleshooting] nkk71:
no adb :(, that would make things a lot easier (maybe), only fastboot commands, so if anybody knows how to "dd" partitions using fastboot only please let us know.
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
Maybe eng hboot - saveprt2sd:

Usage: saveprt2sd <partition name> <-n> <file name> <-a>
<partition name> - Partition name want to save
<-n> <file name> - File name to store in(optional)
<-a> - Save whole blocks even read empty page(optional)
ex: saveprt2sd hboot hboot.bin
(use listpartition command get all partition name)
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Thought about that one, but no removable sdcard :(

and no way to pull it without adb

I was thinking about read_mmc , but to be honest, I've never tried any of those.
[One (M7) Q&A, Help & Troubleshooting] cschmitt:
Does it save to internal sd (i.e. /data/media)? Or you could get usb otg cable for a couple bucks and do it that way.

I'm thinking if you can dump p6 successfully then flash a known good p6 (unedited) just to get the phone to boot into recovery, then use adb to pull the p6 dump from the internal sd card, edit the known good version with values from the dumped p6 and flash it back to the phone to get back the original imei, sn, etc., etc.
[One (M7) Q&A, Help & Troubleshooting] vmcp:
No updates. I do have the box that it came in. I know on the back it has the IMEI, SN, MN, and 2 other numbers (with perhaps others). I'll grab it and report back.

Let me know if there is a way to "d/l" the current partition and I'd be willing to try to flash a new partition then re-write my values. Right now I'm working on activating my old phone so at least I'll have something. Going crazy. Nearly a week without my phone! :crying: