yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] Arthurion:
Hi guys!

Here's the deal. I got a brand new M7 Dual Sim edition from an official reseller's store here in Prague, the Czech Republic (Central Europe). I went home and did the dumbest thing possible. I tried to flash Android Revolution. I had no idea that the M7 and the M7 Dual Sim editions were totally different and that a ROM for one version did not have to be compatible with the other. Such an idiot! So since then (for 2 months now) I've been trying to get the phone back to it's original state with no luck. I can boot into recovery (TWRP or CWM) and bootloader so I have access to fastboot, thankfully. I have tried everything possible hence the reason why I'm writing here and bugging people who have much more important things to do. So let me apologize in advance for wasting everyone's time if this has already been solved once. It's just that every guide I come across explaining anything regarding this phone has impossible prerequisites for a phone that cannot boot into the system normally - like changing the CID, having the phone S-OFF or having an older HBOOT version which I've tried to change several times unsuccessfully.

Here's some info on my phone:

(bootloader) version: 0.5

(bootloader) version-bootloader: 2.49.0000

(bootloader) version-baseband: U3.15.3509.12

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.13.402.2

(bootloader) version-misc: PVT SHIP S-ON

(bootloader) meid: 00000000000000

(bootloader) product: m7cdug

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0771000

(bootloader) cidnum: HTC__032

(bootloader) battery-status: good

(bootloader) battery-voltage: 4158mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-6d8a0b9b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

And a screenshot is attached from the Bootloader.
[Galaxy S6 Edge Q&A, Help & Troubleshooting] jrrevoltar:
Model: SM-G925I

I have attempted to install the customer recovery such as TWRP OR CWM but after it reboots it just stays on the samsung boot logo. I have to hard reset it to just boot into the system which I can't boot into customer Recovery at all. Everytime I try to it does the same thing - Gets stuck on the Samsung boot logo

Does anybody have the correct Customer Recovery I can install on my s6 Edge (SM-G925I)?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Alex-V:
first you must be rooted
[Galaxy S6 Edge Q&A, Help & Troubleshooting] jrrevoltar:
I am rooted... Stil the same thing occurs

Unless someone can link me to the correct Recovery I can flash onto my device?
[Galaxy S6 Edge Q&A, Help & Troubleshooting] Alex-V:
what version you tried..?
[Desire 816 Q&A, Help & Troubleshooting] lgevo25:
Trying to RUU VM 816 that is rooted with s-off.

I used "fastboot oem lock". It says relocked on hboot screen

I changed name of zip to 0P9CDIAG and put it on root of sd card. I then return to hboot and it finds zip. it loads all the way then gives me that error that its the wrong image press power to reboot. not sure what else i can do.
[Desire 816 Q&A, Help & Troubleshooting] lgevo25:
ugh

Update

I have unlocked again with htcbin then relocked. i have no idea what to do. i get no service no matter what rom/backup i use so this was my only hope.

S-off a problem? is there a different RUU file or technique?
[Verizon Samsung Galaxy S 4] djcyph:
i want to remove root and restore to stock, im guessing taking the lollipop update finally will do that? i know how to do it via odin but my usb port i think is broke.

thanks
[Verizon Samsung Galaxy S 4] dgutierrez04:
Yes taking the over the air update will definitely remove root.
[Verizon Samsung Galaxy S 4] djcyph:
cool thanks...so it will be considered factory stock? im sending back to asurion want to make sure. i know they usually dont care, but you know might as well. i never flashed any roms & removed safestrap as well. taking the update should be only thing left right?

thanks
[Verizon Samsung Galaxy S 4] dgutierrez04:
Yes it it will be consider stock. And yes that is the only step u have.
[Verizon Samsung Galaxy S 4] KaosMaster:
The OTA well fall if you ever rooted it. You can try...but you might get stuck having to ODIN flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, catches fire, you get fired because the alarm failed, and global thermonuclear war

Kali Nethunter ported to the Samsung Galaxy S3​

REQUIREMENTS:

A Samsung Galaxy S3 USA CURRENTLY RUNNING CM11 failure to have this will result in a brick and possibly even a HARD BRICK

A functioning brain

A working recovery

Basic instruction following skills

STEPS:

Download the two zips and copy them to your phone

Link for file 1: https://drive.google.com/open?id=0B5BIHhwzM7wWdDhnbW9xR0E3d2M

Line for file 2: https://drive.google.com/file/d/0B5BIHhwzM7wWSDA5MmZmMjN1TFE/view?usp=sharing

Reboot into recovery

Flash the zips in either order.

Reboot the device and set up, setup however is NOT finished.

Download: https://drive.google.com/file/d/0B5BIHhwzM7wWaHJrUzByb20yWVk/view?usp=sharing and put it on your SDCARD

You now have 2 choices:

ADB METHOD:

run adb root

run adb shell mount -o remount,rw /system

run sh fixkaliterm.sh

MOBILE TERMINAL METHOD:

run su

accept the superuser prompt.

run mount -o remount,rw /system

run fixkaliterm.sh

The last part is to fix permissions and fix a strange CyanogenMod "feature" that breaks mobileterminal.

Use make kali_defconfig to make the Kali Kernel correctly if compiling

Please post flash time and results below, this should work on ALL d2 devices under the d2lte label CM uses.

XDA:DevDB Information

Kali Nethunter for d2lte , ROM for the AT&T Samsung Galaxy S III

Contributors

dank101

Source Code: https://bitbucket.org/dank101/android_kernel_samsung_d2_kali

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: CM11

Based On: CyanogenMod

Version Information

Status: Testing

Current Beta Version: 0.1

Beta Release Date: 2015-06-09

Created 2015-06-10

Last Updated 2015-07-08
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] linxcaesar:
First link down, please check ;)

Awesome ;) was hoping someone would port nethunter to our sgs3.

Kali is running without problems but am curious about this features.

Pls fix the first link and ill get right away to test it. Thx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
Fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] linxcaesar:
Downloading atm will let you know how it worked out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] linxcaesar:
Hmm the rom part flashes without issues but kernel fails with an error. Just realised this is for the lte version, so its my fault for not reading carefully. Any chance for a modified kernel for the I9300 SGS3 International? If needed ill pull out the logs with the exact error but I think you might already know what the issue could be.

---------- Post added at 03:25 PM ---------- Previous post was at 03:21 PM ----------

Btw the flash time for the rom was under 10min
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalfangs:
When running fixkaliterm.sh I'm getting thrown a few errors. Am I missing something?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
Try as SU.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
Maybe.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalfangs:
Clean flash followed the steps but selecting any option in Kali launcher just opens a terminal window that displays this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
You didn't read the entire thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] metalfangs:
Actually I did. As stated in my post above I followed the steps directly. Multiple times all yield same results.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
The SH file fixes it, run with su -c.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rjhingoor:
Android Terminal Commands

MOBILE TERMINAL METHOD:

run su

accept the superuser prompt.

run mount -o remount,rw /system

run fixkaliterm.sh

Do I just enter these commands verbatim? I know to run su you simply type su, but what about the other two commands? Any help would be nice, not that familiar with terminal on droid. Regardless I am currently working towards getting this to run, I still have to put cm11 on and install the other zips as well. Hopefully I can figure out the terminal stuff.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WaydeUltima:
Followed the instructions to the letter, as far as I can tell, and I was getting the same errors with fixkaliterm.sh. Started over and noticed that when I try to install the first zip (kernel installs fine), it runs into an error "set_perm: some changes failed, E: Error in <filename>, (Status 7), Installation Aborted."

Not sure how to proceed at this point. Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
Development is halted. can't help you, I don't own a S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Remoo:
Awesome!!

Will flash when I get home in a couple of hours, glad to see people still making things for the GS3.

Sad to leave Lollipop but this is so worth it :D

Ill keep you updated
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WaydeUltima:
So I did some research, and what ultimately worked was switching my recovery from Clockworkmod to TWRP.

After that, flashed both zips without a hitch and the software works great. Thanks for the port!

Note: to anyone receiving the "not found" error (I haven't seen any in this thread but the threads for other S3 versions had a few), go back and try to flash the zip again, and make sure it doesn't fail the installation. It's easy to overlook if you aren't paying attention.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ansaribro:
Not Working ON Galaxy s3 LTE GT-I9305
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dank101:
Hence why this is in the AT&T section and note the I9300/I9305 section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlw93:
I'm excited to try this, but the first link give me a 404 error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Accu767:
Anyone have a copy of fixkaliterm.sh or other zip files?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Shagerty:
Anyone have any of these zips? would love to load this on my phone..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vandelay_iind:
Very interested in trying this. Does anyone have an updated link or the name of the source files that used to be at those URLs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] holysaint1:
Pls any1 with the needed files to run this should please help in uploading them... Seriously in need of 'em
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PenTestBoii:
Uhm...

All links down... I guess i have to make my own kernel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] beynolds.rurt:
Did you ever fire up the kitchen and cook up that kernel?
[T-Mobile Samsung Galaxy S6] grneyez:
Looking for some help from you guys from the S6 forums. I have a rooted S6 Edge via Ping pong Root that I can not install custom recovery on no matter what I try. I've posted in the S6 Edge forums but no one has come up with anything to help. So, I'm trying here. I tried the TWRP app = No recovery install, tried Flasify = Bootloop. Any one have any ideas?

Tried Using:

2 PC's running Windows 8

1 Laptop running Win 7

Latest USB drivers.

Odin 3.10 (Elevated Privileges)

Couple of USB cables.
[T-Mobile Samsung Galaxy S6] lukebrantley:
Could this be your problem?

Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install.

I took this from here: https://twrp.me/devices/samsunggalaxys6.html
[T-Mobile Samsung Galaxy S6] grneyez:
Thanks, I tried this a dozen times without any success. Weirdest thing I've flashed countless recoveries on other phones HTC, Samsung, Lg, etc. and never once ran into this. I'm not giving up, gonna figure it out, hopefully.
[T-Mobile Samsung Galaxy S6] ThePagel:
Try this:

1. Download twrp recovery and zip it with the installer script. Make sure it's named recovery.img

2. Install flashfire

3. Flash twrp update zip with flashfire

4. Hopefully boot into twrp!
[T-Mobile Samsung Galaxy S6] grneyez:
Amazing, could not believe how simple it was. Worked like a charm, thanks for your help. I've been racking my brain for days with this.
[T-Mobile Samsung Galaxy S6] ThePagel:
Awesome!
[Galaxy S 5 Q&A, Help & Troubleshooting] willdareal2010:
Just wondering was there in the works or or is there any lollipop tw roms for the cricket gs5 at&t roms dont work just kitkat roms and all aosp lollipop roms are thes same just diffrtent yhemes???
[Galaxy S 5 Q&A, Help & Troubleshooting] willdareal2010:
I guess not ....
[Sprint HTC One (M8)] Spikebrian:
Hi,

My charge port on my htc one m8 has been having problems for the past several months. So I finally bit the bullet and bought a new board. It was a fairly straight forward process to replace.

So my charging port, and headphones work good, but now I have no mic. When I put the old board back in voilà, microphones back. Speaker mic works fine with either board.

I bought my replacement on eBay http://pages.ebay.com/link/?nav=item.view&id=161657397217&alt=web

Attached is a picture of my original board. I read on the forums that there were revisions but there is one difference. There's a metal brack soldered onto board on the charging port, and around the headphone jack, which the new one didn't have.

Do you guys just think I got a defective board, or possibly the wrong one? I looked at several adds on eBay and that bought one specifically said it worked for sprint only.

Any help is appreciated

Thanks
[Sprint HTC One (M8)] Spikebrian:
EBay seller sent me a replacement and it worked fine. So I can confirm they work fine. The first one was just faulty.
[JASJAR, XDA Exec, MDA Pro ROM Development] charlietruong:
does anyone have the ORIGINAL Universal WM6. I wanna try this version, untouched, on my Imate Jasjar. Thanks in advance
[JASJAR, XDA Exec, MDA Pro ROM Development] decebal:
please do read the posts before and also use the WIKI for info. as for the WM6, there is no original version (yet ?!?) for it. only the roms built by our gurus.
[JASJAR, XDA Exec, MDA Pro ROM Development] Tadeusz:
So do I. Unfortunately iMate, for some sily reason, does not want the public to get it.

Were did you come from, man? Did'nt you hear that they are not willing to release a WM6 OS for Universal? Read around first, please. ALL THE PEOPLE HERE ARE SPENDING THEIR TIME ONLY BECAUSE THERE IS NO SUCH THINK LIKE "ORIGINAL Universal WM6". Thanks to develpers here we can taste this on our unis, but please do not ask such questions, because it makes people mad.

Do not take it personal...
[JASJAR, XDA Exec, MDA Pro ROM Development] TehPenguin:
Um... What do you mean by this?

Did you mean:

1) The Original "Official" Release from I-Mate

Then your out of luck because that doesn't exist...​

2) The Original ROM Base before the Developers started working on them

I'm sure if you PM the Developers nicely they may still have a copy. However, there is a reason that the Developers are Developers - they need to do much customisation and work on a ROM Base before it works enough for it to be considered okay for everyday use​

3) A ROM that doesn't have all of the extra programs (ie a Pure Vanilla)

Now this we can do. Just look for any "Kitchen" and cook (build) your own ROM without any OEM packages​

Enjoy!
[JASJAR, XDA Exec, MDA Pro ROM Development] charlietruong:
Thanks for all your replies; I guess I'm out of this world then. I saw WM6 on many devices out in the market and i thought I could get the OFFICIAL ver for my JASJAR too. My bad. Sorry guys/gals
[Nexus 7 (2013) Themes and Apps] masri1987:
anyway i can get my BT to automatically connect to my music receiver in my car whenever it's in my car?

Bluetooth stays on but doesn't reconnnect even though the receiver has power.
[Nexus 7 (2013) Themes and Apps] masri1987:
Mods please close, i've reposted this in QA
[Motorola Droid RAZR] fullcesar:
Hi guys, first of all excuse me for my poor English, I'm from Argentina.

I am a newie at the custom roms, a few days ago install cyanogen mod 11 in my Motorola RAZR XT910. Everything was fine until I install lucky patcher and run it, I was not allowed to give root permission, not know why. But after that I no longer allowed me super user permissions to any other app more (adfree, root explorer, etc). So I decided to install SuperSU, with this app I could not get super user permissions in lucky patcher (or any other). After that I decided to uninstall SuperSU app, but the default super user of cyanogen mod disappeared from the menu. I had to reinstall the rom. My question is whether there is any incompatibility between lucky patcher and cyanogen mod or I can do to make me not the same thing happen if I install lucky patcher.

I hope you understand my English. Thank you very much to all.
[Motorola Droid RAZR] the_scotsman:
Lucky patcher is warez - we don't provide support for any warez or cracks. Pay for your apps and games, and you won't have any problems.
[HTC One S] JavierG123:
http://xdaforums.com/showthread.php?t=1630459
[HTC One S] Rapier:
In order to see anything on system in TWRP, you should have mounted it before (go to Mount and check system). But that's not the point.

You didn't say anything about which One S do you have (S4/Ville or S3/Ville C2),which version of TWRP you have and most important which hboot you're on.

For most ROMs you'll need 2.15 hboot, also because you're S-On you must flash kernel in fastboot after you flash the ROM. You flashed CM12 so I presume you have 2.15 hboot but you never said you flashed also the kernel in fastboot mode. That's why phone don't boot

Sent from nowhere over the air...
[HTC One S] inkyynki12:
The phone is S4/Ville.

It's on 2.15 hboot as well.

The TWRP version it had was 2.5.0.0.
[Verizon Samsung Galaxy S III] dank101:
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, catches fire, you get fired because the alarm failed, and global thermonuclear war

Kali Nethunter ported to the Samsung Galaxy S3​

REQUIREMENTS:

A Samsung Galaxy S3 USA CURRENTLY RUNNING CM11 failure to have this will result in a brick and possibly even a HARD BRICK

A functioning brain

A working recovery

Basic instruction following skills

STEPS:

Download the two zips and copy them to your phone

Link for file 1: https://drive.google.com/file/d/0B5BIHhwzM7wWQjZ5ejlsS2FqTjA/view?usp=sharing

Line for file 2: https://drive.google.com/file/d/0B5BIHhwzM7wWUmVsQzVBR3F1enM/view?usp=sharing

Reboot into recovery

Reboot the device and set up, setup however is NOT finished.

Download: https://drive.google.com/file/d/0B5BIHhwzM7wWaHJrUzByb20yWVk/view?usp=sharing and put it on your SDCARD

You now have 2 choices:

ADB METHOD:

run adb root

run adb shell mount -o remount,rw /system

run adb shell sh fixkaliterm.sh

MOBILE TERMINAL METHOD:

run su

accept the superuser prompt.

run mount -o remount,rw /system

run fixkaliterm.sh

The last part is to fix permissions and fix a strange CyanogenMod "feature" that breaks mobileterminal.

Use make kali_defconfig to make the Kali Kernel correctly if compiling

Please post flash time and results below, this should work on ALL d2 devices under the d2lte label CM uses.

XDA:DevDB Information

Kali Nethunter for d2vzw, ROM for the Verizon Samsung Galaxy S III

Contributors

dank101

Source Code: https://bitbucket.org/dank101/android_kernel_samsung_d2_kali

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: CM11

Based On: CyanogenMod

Version Information

Status: Testing

Current Beta Version: 0.1

Beta Release Date: 2015-06-09

Created 2015-06-10

Last Updated 2015-06-09
[Verizon Samsung Galaxy S III] TXBY417:
Any way you could post a link to the most recent cm11? I go to the cm download page and all he has posted are cm12.1. I could get the version from 20140209 but that's a little old.
[Verizon Samsung Galaxy S III] dank101:
Try d2lte.

It works, and is CM11.

You can TRY CM12.1, but it's untested, and I'm no longer using a SIII.
[Verizon Samsung Galaxy S III] TXBY417:
Thank you!
[Verizon Samsung Galaxy S III] TXBY417:
File number one doesn't exist anymore.
[Verizon Samsung Galaxy S III] AxeEdge:
Hey, still have those files handy? The above links are dead.. I sure would appreciate it. I'm interested in doing an experiment with nethunter on an old Verizon Galaxy s3, which is all I have laying around right now.
[Verizon Samsung Galaxy S III] Erik_65:
Bump
[Verizon Samsung Galaxy S III] d33dvb:
Could you update the links or someone post a new link ?
[Verizon Samsung Galaxy S III] d33dvb:
All linkS are dead, can you upload somewhere?
[Verizon Samsung Galaxy S III] the Doctor:
THREAD CLOSED

OP, if you want it back open then please send me a PM and provide working download links.
[Sprint Samsung Galaxy S III] dank101:
Disclaimer: I am not responsible if you use this and brick your device or if your device blows up, catches fire, you get fired because the alarm failed, and global thermonuclear war

Kali Nethunter ported to the Samsung Galaxy S3​

REQUIREMENTS:

A Samsung Galaxy S3 USA CURRENTLY RUNNING CM11 failure to have this will result in a brick and possibly even a HARD BRICK

A functioning brain

A working recovery

Basic instruction following skills

STEPS:

Download the two zips and copy them to your phone

Link for file 1: https://drive.google.com/open?id=0B5BIHhwzM7wWdDhnbW9xR0E3d2M

Line for file 2: https://drive.google.com/file/d/0B5BIHhwzM7wWSDA5MmZmMjN1TFE/view?usp=sharing

Reboot into recovery

Flash the zips in either order.

???

Profit.

Use make kali_defconfig to make the Kali Kernel correctly if compiling

Please post flash time and results below, this should work on ALL d2 devices under the d2lte label CM uses.

XDA:DevDB Information

Kali Nethunter for d2lte , ROM for the Sprint Samsung Galaxy S III

Contributors

dank101

Source Code: https://bitbucket.org/dank101/android_kernel_samsung_d2_kali

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: CM11

Based On: CyanogenMod

Version Information

Status: Testing

Current Beta Version: 0.1

Beta Release Date: 2015-06-09

Created 2015-06-10

Last Updated 2015-07-08
[Sprint Samsung Galaxy S III] hotwired34:
WooHoo!
[Sprint Samsung Galaxy S III] dank101:
FYI: I just updated the kernel zip to fix approximately everything.
[Sprint Samsung Galaxy S III] aron2hip:
I am trying to make a port for cm12.1 d2att could you upload the device scripts.
[Sprint Samsung Galaxy S III] dank101:
Uhhh....

Not that easy...

Also ask on the d2att thread.
[Sprint Samsung Galaxy S III] aron2hip:
I have the kernel source in the devices directory, I'm just too lazy to edit the androidmenu bash script for the device. Unless there are further modifications necessary.
[Sprint Samsung Galaxy S III] dank101:
There are indeed future mods needed.
[Sprint Samsung Galaxy S III] Knuxyl:
The first two Google Drive links are dead.

Here is a mirror for the files. I don't know how long they will last so urge OP for new mirror.

http://www.filedropper.com/kalilinuxnethunter121d2ltekitkat

946mb

http://www.filedropper.com/kalinhkernel

12.5mb
[Sprint Samsung Galaxy S III] dank101:
You really should have PMed me about this FIRST.

I didn't know they died.
[Sprint Samsung Galaxy S III] RootSuperSU:
When will file links be available for download again cause? I was only ever able to download the kali kernel!