yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Android Development] TempoRobo:
[MENTION=6975569]Vishal Vignesh[/MENTION]

All i know is that it was bought from the UK and unlocked from any network. Looking at the inside stickers (underneath the battery) it says:

Model: GT-N7100

FCC iD: A3LGTN7100

SSN: -N7100GSMH

Rated: 3.8V ; 1300mA

Made by Samsung
[Galaxy Note II Android Development] Vishal Vignesh:
Hey, can you try flashing a lollipop ROM....

Also

Just cross checking.....

On twrp, under mount option everything except efs is mounted rite......

Jus name those that are not...and try flashing after mounting all of them...... Except efs.....

After flashing in twrp try booting without clearing cache......

I m seriously not going to give up until your problem is solved.......
[Galaxy Note II Android Development] mad1mystic:
Before flash wipe dalvik and cache and system and data also.i had same problem when moving from one rom to another. Didn't go past boot screen.

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

Also try twrp 2.7.0 recovery if possible
[Galaxy Note II Android Development] logosA:
[MENTION=7649031]TempoRobo[/MENTION], i am really sorry i could not be able to helped you.

My knowledges are to this point, cannt go any further :(

Let your phone and your self rest for a whille and maybe something we can find out in the future.

Maybe your phone is to elegant for MM and want nougat ( N ) instead :)

It was nice talking to you
[Galaxy Note II Android Development] TempoRobo:
[MENTION=6975569]Vishal Vignesh[/MENTION]

Under mount i have the following 3 ticked:

1)Cache

2)Data

3)MicroSDCard

The following are unticked:

1) EFS

2) System

3) USB OTG

So if i well understood i should ticked (1) System & (2) USB OTG, then flash + boot without clearing cache/dalvik....right?
[Galaxy Note II Android Development] logosA:
as i can see the XDA is now officially considering you 'member'
[Galaxy Note II Android Development] TempoRobo:
[MENTION=5554397]logosA[/MENTION]

It is a privilege to be part of XDA and above all I can't thank you and the other team members well enough for the amount of time and efforts spent in trying to resolve this issue. It is nice talking to you too dear, but i haven't given up as yet ;) [MENTION=6975569]Vishal Vignesh[/MENTION] has proposed a couple of things to do and I shall post all updates here so we all know what works and what doesn't!
[Galaxy Note II Android Development] Vishal Vignesh:
Mount system also.......

Wipe everything, make sure everything is mounted then flash ROM then boot......

Make it boot without Gapps first.....
[Galaxy Note II Android Development] logosA:
ok then, lets go again :)

---------- Post added at 03:53 PM ---------- Previous post was at 03:39 PM ----------

and for you to know, we all have learned thinks in this proccess of yours.

This is the spirit and the meaning of a forum, learn things and help others, too.

You motivated us to categorize and analize things we know.

Learned something new from other users comments,too

All these are going to stay for the next users who will join in the next days
[Galaxy Note II Android Development] TempoRobo:
[MENTION=6975569]Vishal Vignesh[/MENTION] [MENTION=5554397]logosA[/MENTION]

So ive mounted everything except efs & usb otg (since it was disabled), then wiped everything as in format/cache/dalvik , installed cm-13.0.1-20160804-UNOFFICIAL-temasek-n7100-V10.4, still no luck.

What i'll do now is try a lollipop ROM as suggested by [MENTION=6975569]Vishal Vignesh[/MENTION] with the same process as above. Will keep you guys posted.
[Galaxy Note II Android Development] HellsAngel_NL:
TempoRobo the only other thing i can come up with is check in twrp > wipe > advanced > system > repair if its ext4

do the same for data maybe you have another filesystem it doesnt like.

Good luck hope you get it solved.
[Galaxy Note II Android Development] andrewKode:
Ok, here we go.

First of all I need to know if you can flash and use Stock ROM on your device. Visit www.sammobile.com and download it if you're not having it already. So if that boots let me know what bootloader you've got. You should WIPE everything on your device using TWRP 3.0.2.0 with "rm-rf" enabled,(another Wipe after that without "rm-rf") in Settings before you flash Stock with Odin.

If Stock ROM doesn't boot as well then you have bigger problems.
[Galaxy Note II Android Development] Malaquai:
You don't need to mount system, it's mounted as required by processes. Only necessary if you want to operate with files throw file manager. USB only if you connect a pen drive into uUSB port to make or restore a back up or install something from it.
[Galaxy Note II Android Development] TempoRobo:
Hi [MENTION=4349893]HellsAngel_NL[/MENTION]

I have checked and both system & Data are coming up as ext4
[Galaxy Note II Android Development] :
Thread closed by OP request.
[Galaxy S 5 Q&A, Help & Troubleshooting] DunnoNL:
Hi all,

Im new to this forum and i really dont know if i can post a topic here, sorry if it is the wrong section.

Ow yeah, im dutch so if i use wrong words ore something my apollogizes to :o

Well the problem is that i have a Samsung galaxy S5 (SM900F - KLTE) i suppose, and i would to flash CM13.

Well now you guys think thats not really a problem.. wel it is really.

First i tried to root the device, well that wouldnt work because odin keeps saying the same stupid problem..

<ID:0/004> Added!!

<OSM> Enter CS for MD5..

<OSM> Binary Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/004> Odin engine v(ID:3.1100)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> SingleDownload.

<ID:0/004> recovery.img

<ID:0/004> NAND Write Start!!

<ID:0/004> FAIL! (Auth)

<ID:0/004>

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Then i've searched and searched and found this video on youtube with some guy who calls himself the android docter and he said flash your S5 to an earlier firmware, and then you should able to root the device.

Well thats what i did, flashed the device from android 5.0 to 4.4.2..

And guess what still cant root it.

The root i tried was CF-auto-root-klte-kltexx-smg900f.zip and CF-auto-root-klte-kltexx-smg900f.zip

Both the same failure/error. i even tried to flash TWRP but i think i should root the device first.

I got the proper samsung drivers and i tried even some other odin versions.

Can someone help me plz, i would be so thankfull.
[Galaxy S 5 Q&A, Help & Troubleshooting] cooperke:
I'm Dutch to. First question i have is, are you using original data kabel?
[Galaxy S 5 Q&A, Help & Troubleshooting] DunnoNL:
Yes i do, i got 2 cables here both original and they both dont work.
[Galaxy S 5 Q&A, Help & Troubleshooting] cooperke:
Okee. Have you flashed stock rom? On what rom are you?
[Galaxy S 5 Q&A, Help & Troubleshooting] DunnoNL:
I did flashed from 5.0 to 4.4.2.

So currently im running a stock version of 4.4.2 kitkat
[Galaxy S 5 Q&A, Help & Troubleshooting] cooperke:
Ik heb mijn de laatste keer, gisteren nog, geroot op 5.0 rom van luxemburg BOJ1. taal kan je instellen op Nederlands. Heb je ook usb-foutopsporing aangevinkt in ontwikkelaarsopties?

---------- Post added at 04:20 PM ---------- Previous post was at 04:19 PM ----------

Send me private message than we can speak dutch
[Galaxy S 5 Q&A, Help & Troubleshooting] Lionheart_eaz:
I had the same problem... But i don't know how I came out... I've tried lots of time changing the USB port and the USB jack. Instead of using cf auto root try to root supersu from a custom recovery. So try to flash a custom recovery and see if it works.
[Galaxy S 5 Q&A, Help & Troubleshooting] DunnoNL:
Well i downloaded Cyanogen Recovery but thats an .img file, and i cant flash .img files.
[Galaxy S 5 Q&A, Help & Troubleshooting] Lionheart_eaz:
U can covert the .img file to md5

https://mega.nz/#!5BVwVSbK!OaAa2vC5J3J9TJ1leCMlT4NmFCDSH36aveblLIHKumk

https://mega.nz/#!JQkERaZR!UYk3o8bzhbr2Ua_yYMZBoCX9k38fMI1SWkNXhJ2X4jo

https://mega.nz/#!5IEUlCII!rzaphpXJwChTUcwSWfZIi3r1xBg1y07Zijj2g1MhyeQ

I suggest u to use twrp or philz touch recovery.
[Galaxy S 5 Q&A, Help & Troubleshooting] keithross39:
Ok....There seems to be a lot of conflicting, confusing information on this thread......

To clear things up a bit.....

It has been mentioned that rolling back to 4.4.2 is necessary in order to gain root....

While it is possible to do this, it certainly isn't *necessary*.

It has also been stated that the rollback and root didn't work.....

I'm guessing here (because the entire method wasn't mentioned) that it was suggested to rollback and use Towelroot to root the device. It is possible to do this, but only under certain circumstances.....

Go to 'about device' and check the build date.....

If the build was compiled AFTER the end of June 2014, towelroot WILL NOT WORK.

In this case, it is necessary to....

1) install (but do not run) the towelroot app.

2) Use Odin to flash a pre June 2014 kernel.

3) run towelroot.

4) re flash your original kernel.

5) enjoy your rooted device.

See this thread for full instructions....

Rooting knox 0x0 by wajiman

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

If the user is running Lollipop, rooting can be achieved by odin flashing TWRP 2.8.7.0, then booting into TWRP to flash SuperSU 2.46 zip.......

This exact method.....

1) deactivate 'Reactivation Lock'.

2) copy SuperSU zip to your device.

3) boot into download mode.

4) Odin flash TWRP 2.8.7.0 (specifically this version).

5) DO NOT allow phone to boot, (remove the battery as soon as the TWRP flash has completed if necessary) then.....

6) boot directly into recovery. (Vol +, Power & Home button combination)

7) flash SuperSU zip.

8) boot device as normal.

TWRP 2.8.7.0 by Dees_Troy

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

superSU zip v2.46 by Chainfire

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

http://i.imgur.com/rVnFwJM.jpg
[Verizon Samsung Galaxy S III] Eclipze_x:
I wanted to install twrp on my Galaxy S3 Verizon running Kitkat 4.4.2 and without realising till after I installed it the boot loader was locked . I then rebooted my phone and received a message somewhere along the lines of " this software is not authorized by verizon" now I did not install the recovery because I did not want to risk bricking my phone because the boot loader is locked I clicked canceled and bypassed the screen into the Os. The problem I'm having is that I wanted to know if anybody knows how to install At LEAST the stock recovery back on the phone so I do not have to worry about having a recovery anymore . My phone is also rooted with superuser permissions and before I installed the Custom Recovery I Backed up my User apps and System Data if that helps at all Please I just want the phone with the stock recovery at least or will I be stuck without a recovery screen ?
[Verizon Samsung Galaxy S III] ShapesBlue:
You can't install twrp on the locked 4.4.2 bootloader. The only soemwhat custom recovery you have the option of is safestrap with the few limited bootloader locked roms
[Verizon Samsung Galaxy S III] Eclipze_x:
Is there a way you or anybody know of to put back the stock recovery screen ? So I don't have to see " this software is not authorized by verizon "? Any help will be appreciated:)
[Verizon Samsung Galaxy S III] ShapesBlue:
Yes. You will have to use Odin to go back to stock 4.4.2.

Nexus 6 via SSHD/Cataclysm
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aymelis:
Guys,

I just bought a Note from a guy who only mentionned that after boot, he could enter his gmail and samsung credentials and then was having a error message : "shell cannot read videos"... I thought this was simple to fix by re-installing JB. The price was attracting because of this issue that the guy could not fix himself.

OK, I knew this was risky : when I received the phone (yes I did not see it before I bought it !), I did not get this error message at all..., but I noticed that the phone was rebooting every 10 minutes when fully charged, and every 2 minutes when batttery reached about 20%.

When fully charged, I could use Odin and install 4.1.2 (XEU-N7000XXLT9-20130611091825.tar.md5) with secured kernel (almost stock) fron philz (PhilZ-cwm6-XXLT9-ORA-5.08.5-signed.zip). This did not fix anything.

The phone is 3 to 4 years old, so is the battery as far as I know. So I first guessed the reboots would probably be due to a weak battery that could not stand the required voltage when the phone was attempting to draw too big a current.

But before I get a new battery, I tried to monitor its voltage during the reboot. I installed to (thin) wires on + and - terminals of the battery connector and connected them to a multimeter while the battery was in place. Unfortunately I could not observe any voltage drop when the phone rebooted. Which tells me it might not be as simple as an old battery problem...

I tried 2 other experiments. The first one was to drive on my 2 wires the same voltage level as the battery from an external supply (I had to keep the battery in place otherwise the phone would not boot, even with a 19kohms resistance between gound and thermistor terminal in the middle). I could observe up to about 300mA drawn at boot time, then around 150mA when ON. I was hoping that the phone would not reboot by itself anymore, as my external supply was not current limited (it could drive up to 1.5A). But it did...

The second experiment was the same, but with an additional (big !) 200nF capacitor between supply and ground to filter out any voltage glitch that could not be captured by the multimeter. The phone lasted longer, but rebooted after about 10 to 15 minutes :(

What do you guys think ? Do you still think a new battery would fix this (I doubt) ? Do you think I should try another android version ? Get back to Gingerbread maybe (I would rather avoid ICS as I read that ICS could brick my phone due to unsecure kernel...).

I noticed I could accelerate the reboot when trying to listen an mp3. At that time the phone starts lagging as hell, and I get a "bad format" error (the mp3 was the Ringtone.mp3 installed with the OS...). After a minute or so of such lagging , it rebooted. But if I just let the phone ON without starting any app, it still reboots after a while.

Any help, thought, comments appreciated !

Thanks and regards
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] :
Does the battery or phone heat up? It sounds like a battery or hardware problem, but you could try using a JellyBean rom first to make sure.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aymelis:
Thanks AutumQueen92, no, it does not heat up. Also I checked, the battery has no bulge at all (tried to make it spin on the table).

As I said, I installed JB 4.1.2 (XEU-N7000XXLT9-20130611091825.tar.md5), actually the first thing I did ;)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] aymelis:
Guys, I finally decided to try a step back to Gingerbread. It was very hard to get ROM links that were not obsolete. But I finally found some from here (in french)

I was surprised that I had to use a PIT file... which I did as mentionned. It almost bricked my device ! It failed. I then restarted the phone and got a message that an update had failed and that I should go to recovery and connect to Kies... I then tried to flash back 4.1.2 from Odin, same : FAIL... I then tried to reflash the PIT alone : FAIL ! Wow that was hot. I finally tried to reflash the whole GB + PIT and it worked fine this time

And you know what ? It's been running for 2 hours with no reboot !

Now I haven't told everything about the problems I am having with this phone : it does not have any sound... No sound from the louad speaker, no sound from the jack. Actually I had not noticed it until after I had opened it and teared apart... But I'm pretty sure the sound did not work right when I got it because I never heard the keyboard making any sound while this is the default setting after installing a new ROM.

I also have no Mic... I have not tested a phone call yet though (I have no big SIM card anymore), but google search voice recognition tells me the mic is not available. Gingerbread did not help on this.

No Mic and no speaker could be explained by the little daughter board that handles both. This costs 19€ on internet... But this would not explain that there is no sound on the earpiece either... My theory is that my audio chip is dead and that some checks implemented in JB make the phone reboot, these checks might not be implemented in GB... This makes me think that I might try going back to JB and see if it would still reboot if I'd turn all sounds off...

Any comments are welcome ! ;)
[Xperia Tablet Z Q&A, Help & Troubleshooting] mrjayviper:
Seems the device will sleep after around 15 seconds when it's gave down. When I play a game I sometimes leave it facing down so this auto sleep is bad for my situation

Hour do I disable this? Thanks

PS. My display auto turn off if set to 5 minutes.
[Android Q&A, Help & Troubleshooting] avatel:
Hi

I have a Samsung galaxy J700F /DD. I flash this firmware J700FXXU1AOFJ to my phone , after flash done and phone reset my phone dead. It hasn't show anything. It can't go to download mode or recovery. I try to turn on phone with external power supply but it only come to 0.13 to 0.15 ampere and phone doesn't start.

Please help me

Thanks
[Android Q&A, Help & Troubleshooting] avatel:
Hi

Please if anybody can help i am in bad trouble:crying::crying::crying:
[Android Q&A, Help & Troubleshooting] adilabdi110:
Hey avatel where ru from, which country is ur phone?

---------- Post added at 01:43 PM ---------- Previous post was at 01:42 PM ----------

Try from adb shell, for that serch in google n youtube maybe it will help u
[Moto G General] Jose Bostal:
Moderator Edit:

Forum Rule violation - please read them all before posting in future...

4. Use the English language.

We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature).

FORUM RULES

Thanks
[G3 Q&A, Help & Troubleshooting] koloko12:
Hey people! :)

1) I don't have LTE signal notification, it's always on 3G/H/G on above the signal lines. on other phone with the same sim card on the same place I do get 4g, I checked and the networks on my LG G3 is LTE/GSM/CDMA, How to fix this?

2)I tried to install a new recovery, but each time I flash it and go into recovery I get black screen with "fastboot mode started" message :/

Edit: Phone still works, just get the black screen with this message when I enter recovery :(
[G3 Q&A, Help & Troubleshooting] thurasisyein:
http://xdaforums.com/lg-g3/help/annoying-lg-g3-problem-lte-signal-solved-t3293721 for LTE

---------- Post added at 04:02 PM ---------- Previous post was at 04:00 PM ----------

http://xdaforums.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268 FOR ROOT AND RECOVERY
[G3 Q&A, Help & Troubleshooting] koloko12:
It doesn't let me save the build.prop file while changing values through ES FILE EXPLORER.

What D855 16/32 means? My phone is D855 but what is 16/32? for those who installed the 30b.kdz GLOBAL tested (no idea in EUR) by Flashtools 2014 = ????

Can you explain me please? :P
[G3 Q&A, Help & Troubleshooting] koloko12:
Anybody has a solution for me please? :(
[G3 Q&A, Help & Troubleshooting] NatusVincere:
If unable to save build.prop with ES, use this:

https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor&hl=en

or edit it on computer by coping /system/build.prop with command:

adb pull /system/build.prop c:/build.prop

find the needed value with notepad or any other text editor and change it to what's nessesary, then:

adb push c:/build.prop /sdcard/build.prop

adb shell

su

dd if=/sdcard/build.prop of=/system/build.prop

chmod 644 /system/build.prop

As for the 16/32 it stands for 16 or 32gb memory version of d855.

You have not specified what android system you possess, so don't follow the guide from [MENTION=7087028]thurasisyein[/MENTION] to flash TWRP unless you have Marsmallow.

If you have lollipop download [MENTION=3279781]bender_007[/MENTION] s autorec from Google Play or from this thread: http://xdaforums.com/lg-g3/general/apk-flash-twrp-autorec-thanks-to-t3081396

if you have kitkat follow this guide:

http://xdaforums.com/lg-g3/orig-development/recovery-twrp-touch-recovery-2-8-2-0-t2966129
[G3 Q&A, Help & Troubleshooting] koloko12:
Oh well im sorry :( I am 32 GB D855 and my system is running Kit Kat.

Currently I don't have any recovery (I think...) when I press power button+vol down I get the black screen with the "fastboot mode started" message. Should I still try the method you gave me fore the KitKat?
[G3 Q&A, Help & Troubleshooting] NatusVincere:
Nothing to be sorry for, poor me has a 16gb version xD.

Ofc follow that guide. You get fastboot because you either flashed wrong files or your recovery partition is empty.
[G3 Q&A, Help & Troubleshooting] koloko12:
A. With custom recovery already installed:

1. Download

2. Install TWRP in recovery

3. Reboot recovery

B. With stock recovery (Need ADB):

1. Download & extract zip

2. Move recovery.img to internal storage.

3. Open terminal window/command prompt to execute following commands

I go with B, right?

Do you have a skype account that I can contact you incase I need help? :D

edit: one more thing I see that's a "bumped" twrp, I saw somewhere on XDA that in case i'll want to flash rom i'll need to bump the rom? or something like this?

I go through all this because I want to change to some Cyanogenmod rom...
[G3 Q&A, Help & Troubleshooting] NatusVincere:
Yes, you go with B. I will send you my skype on pm in a moment.
[G3 Q&A, Help & Troubleshooting] krishna13:
Well. I faced the second problem which u mentioned. Actually by seeing the software version i confirmed that my phone is D855. This phone, I got from my brother. I flashed TWRP and booted. But instead of showing recovery menu it showed fastboot (just like u described). So I got doubt and I opened the back of my phone and found that actually my phone has LS990 motherboard. So I flashed back the LS990 TWRP and Now everything working fine.

I read somewhere that if the phone is booted in fastboot, there are 2 reasons:

1. If wrong Recovery is flashed

2. If build.prop is messed up (not sure )

So if possible check your motherboard as I personally Experienced this. :)
[G3 Q&A, Help & Troubleshooting] koloko12:
How do I check the motherboard? I see on the back when I take cover off, D855 signs
[G3 Q&A, Help & Troubleshooting] krishna13:
Yes.the same with my phone also.the sticker at the back shows D855 only. But go to an mobile repairer,tell him to unscrew the scews( remember,tell im to place the camera screws seperately as the size of them is different from others). After that jus lift the plastic panel and u can see the motherboard.now dnt do anything. Just look at the top right of the board,u can see small gold letters on it and u can find the model number. If possible,update me with the info.
[G3 Q&A, Help & Troubleshooting] koloko12:
is there other way checking it without opening the screws?
[Xiaomi Redmi 3 Questions & Answers] yoshco:
see title
[Xiaomi Redmi 3 Questions & Answers] askor:
It's B
[Xiaomi Redmi 3 Questions & Answers] neeraj.jmi:
Release date in india?
[Xiaomi Redmi 3 Questions & Answers] sandeep_7:
Will xiaomi release redmi 3's kernel sources ????
[Xiaomi Redmi 3 Questions & Answers] Vynikal:
yeah, ETA is 2020...
[General Topics] lil jefflito:
Mod Edit by [MENTION=4036181]Darth[/MENTION] : Not on XDA, thanks. Thread closed.