yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
Remove your serial number and your IMEI number from your original post like it did in the quote above, its dangerous to post it.

then see here for your problem and a fix http://xdaforums.com/showthread.php?t=2739126

copy and paste the dd commands to be safe, if you make a mistake with the command or code then its bye bye phone.
[One (M7) Q&A, Help & Troubleshooting] Flickayy:
ah thanks for that.

I've tried to flash a new recovery, but I still can't boot into it.
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
you HAVE TO flash that modified recovery in the thread I linked, its the only one that will work.
[One (M7) Q&A, Help & Troubleshooting] Flickayy:
Sorry if I didn't make it clear, but that was the recovery I flashed. Yet it still reboots to the bootloader instead.
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
Oh sorry, my bad, reading through the thread, its states you need to downgrade your HBOOT, but ill just double check that, you are s-off so shouldn't be a problem.
[One (M7) Q&A, Help & Troubleshooting] Flickayy:
it's proving tricky.

I've downloaded the hboot, when I get an error.. FAILED <remote: not allowed>
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
yup, seems the problem is with HBOOT 1.55 and upwards, a lot of people on there are just downgrading there HBOOT to 1.44 then the recovery works, however, if you decided to do this you need to be aware that windows 8 upwards will no longer detect your phone, you must use windows 7 or Ubuntu.
[One (M7) Q&A, Help & Troubleshooting] Flickayy:
I'm using Window 7 Professional 64-bit.

Can you point me in the right direction on how to correctly downgrade? I tried to dowgrade to 1.44 and got this.

C:\Users\Ricky\Downloads>fastboot flash zip h144.zip

target reported max download size of 1514139648 bytes

sending 'zip' (501 KB)...

OKAY [ 0.246s]

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.656s
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
send me a link to the hboot you downloaded please
[One (M7) Q&A, Help & Troubleshooting] Flickayy:
I managed to get this one to work http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/

it's booted, waiting for it to go past the logo now, thank you for the help! :)
[One (M7) Q&A, Help & Troubleshooting] Seanie280672:
excellent, glad it worked, you have to be very careful with HBOOTs, the wrong one will lead to an instant brick, you don't want to be seeing any error's :crying:
[One (M7) Q&A, Help & Troubleshooting] Flickayy:
Sorry for the slightly necro post.

I'm running into the same problem again, after updating via OTA.

My HBOOT got set to 1.57 and every time I try to flash the zip I get an error.

C:\Users\Ricky\Downloads>fast

< waiting for device >

target reported max download

sending 'zip' (501 KB)...

OKAY [ 0.251s]

writing 'zip'...

FAILED (remote: not allowed)

finished. total time: 0.295s

here is my getvar

C:\Users\Ricky\Downloads>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.57.0000

(bootloader) version-baseband: 4T.29.3218.08

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 6.09.401.5

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

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0710000

(bootloader) cidnum: 11111111

(bootloader) battery-status: good

(bootloader) battery-voltage: 3703mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-6d8a0b9b

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.163s

thanks!
[One (M7) Q&A, Help & Troubleshooting] alray:
what file are you trying to flash and using which command?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
filesize looks like the fw_hboot_zip

did you fastboot oem rebootRUU first?
[HTC Droid DNA] tdizzle404:
I keep getting this message no matter what Ron or gapps I flash anyone know what this problem might be?
[HTC Droid DNA] d08speed3:
Might just be the camera took a dump on you bud...

HTC DNA

LG Optimus G
[HTC Droid DNA] xlxcrossing:
Mods please move to Q&A
[AT&T Samsung Galaxy S 5] cspiresucks:
I'm trying to start a thread for at&t galaxy s5 users. A place to share information that others may not know. Currently I'am looking for a stock kernel for my s5 just incase, I mess something up.

Sent from my stock rooted SM-G900A
[AT&T Samsung Galaxy S 5] diestarbucks:
Here you go, an entire S 5 forum for ya:

AT&T Samsung Galaxy S 5-XDA

:good:
[Galaxy Note 3 Q&A, Help & Troubleshooting] Doodless:
I need help with rooting my Galaxy Note 3. I've never rooted a phone before so I am new to this. I've read some of the posts and understand a bit, but they're all confusing as there are quiet a few posts out there on how to root. I'd like to get some help on which correct tools and stuff I would need to download to help me root my phone. Preferably I would like to stick to stock ROM, or a custom ROM closest to stock without the Samsung bloatware. My phone model is the SM-N900W8, running on KitKat 4.4.2, with a baseband version of N900W8VLUCNB7, and Kernal 3.4.0-859721.
[Galaxy Note 3 Q&A, Help & Troubleshooting] zelenko:
Do you try with towelroot ? its a one click app

http://towelroot.com/

download apk, click make rain and voala, root
[Galaxy Note 3 Q&A, Help & Troubleshooting] thecoolster:
Friend just use a very famous app called framaroot.... It is a one click app which is available for ur device

Here is the link:

http://techbeasts.com/2013/11/04/how-to-root-any-android-device-with-just-one-click-via-framaroot/

They tell u the method also I guess...

U can also flash the su binary scripts files and stuff with Odin (just Makin it easier for u to understand)

Press the thanks button if I helped!!!!!:thumbup::cool:

Sent from my MIND using my BODY....(JUST KIDDING)
[Galaxy Note 3 Q&A, Help & Troubleshooting] Doodless:
If I were to use Towelroot would I be able to factory rest my phone and it'll still be rooted? Also do I need to do anything else after using Towelroot?

-update- using Towelroot did not work for me
[Galaxy Note 3 Q&A, Help & Troubleshooting] hey_joe:
Do a little bit of reading here.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Doodless:
Thanks I've read the other post too. I wouldn't have any to do anything after flashing the file through Odin right? Also would I be able to factory reset my phone no problem and keep my root?
[Galaxy Note 3 Q&A, Help & Troubleshooting] hey_joe:
Nothing to do.

You can do factory reset no problem but you might loose root, but just repeat the process in case you do loose root. Be warned though, although quite a lot of people rooted their N900W8 without tripping root, can't exactly say it will be the same for everybody, it might trip it.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Doodless:
As there are many models of Note 3 out there, would I have to a kernal that is specifically compatible with my phone?
[Galaxy Note 3 Q&A, Help & Troubleshooting] hey_joe:
If you intend to stay on stock firmware and not flash a rom, then you don't need one. But if you flash a rom made for a N9005, then you will need a kernel made for N900W8/Tmobile in order to make NFC, BT and Wifi work ( also need a patch for the said sensors/signal ).
[Galaxy Note 3 Q&A, Help & Troubleshooting] Doodless:
I guess I will stick with stock as everything still seems too confusing for me to understand. The root you gave me, I notice it says sm9005 instead of sm900w8, it wouldn't change my network frequency would it?
[Galaxy Note 3 Q&A, Help & Troubleshooting] thecoolster:
Friend just use a very famous app called framaroot.... It is a one click app which is available for ur device

Here is the link:

http://techbeasts.com/2013/11/04/how-to-root-any-android-device-with-just-one-click-via-framaroot/

They tell u the method also I guess...

U can also flash the su binary scripts files and stuff with Odin (just Makin it easier for u to understand)

Press the thanks button if I helped!!!!!

Just try it!!!!!!! It worked for my mtk device(which is also very hard to root)

Sent from my MIND using my BODY....(JUST KIDDING)

Sent from my MIND using my BODY....(JUST KIDDING)
[Galaxy Note 3 Q&A, Help & Troubleshooting] hey_joe:
It will not change anything except root your phone. I know it says it's for N9005 but quite a lot of people even with different phone models have tried it and it worked and that's including me who has a N900W8 from Rogers.
[Galaxy Note 3 Q&A, Help & Troubleshooting] Stuart Little:
You can root with:

POOT: This app is a one click root app. No computer needed

Framaroot: Framaroot is a oneclick root app . No computer needed

This is the most popular one!

Z4Root: Z4Root is an oneclick root app . No computer needed

Towelroot: Towelroot is an oneclick root app. No computer needed

Baidu: No information

Vroot: No information

Gingerbreak: This app can root almost all gingerbread devices

Downloads:

Poot - Download the app >>here<<

Framaroot - Download the app inside this XDA Thread - >> CLICK HERE <<

Z4ROOT - Download the app inside this XDA Thread - >> CLICK HERE <<

Towelroot - Download the app inside this XDA Thread - >> CLICK HERE <<

Baidu ROOT - Download the app >> HERE <<

vROOT - Download the app >> HERE <<

Gingerbreak - Download the app inside this XDA Thread - >> CLICK HERE <<

Flash a SU ZIP - Download the ZIP >> HERE << and flash it on your unlocked bootloader phone !

Hit thanks if you liked this post or this post has helped you out !
[T-Mobile Samsung Galaxy S 5] jojo4747:
Will these Roms work with the metro PCs variant?
[T-Mobile Samsung Galaxy S 5] fffft:
You forgot to tell us what ROMs you are referring to?

Find out if your bootloader is locked. If it isn't, then most custom ROMs should work for you. If you have a locked bootloader, then you can probably emulate some ROMs using the Safestrap program that is popular on Verizon.

.
[Galaxy S III Mini Q&A, Help & Troubleshooting] pang34:
When I installed miui rom no sim instead, I restore to stock rom the sim signal is normal, any idea?

send for I8190N R-Mod v2 using XDA Premium 4 mobile app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
The development for the AT&T I747 has been discontinued by the developer. Thank you for your support.

WARNING: YOU WILL PROBABLY BRICK YOUR PHONE! The possibility is very real. Samsung made it difficult to update the firmware with the introduction of Knox.

This is a full firmware update!

I'm not the best at giving directions. I do expect a certain level of knowledge and skill on your end.

I did try my best to safeguard you from bricking your phone. The install scripts will fail with an error 7 if something is wrong.

More then likely if it fails... you are on very old firmware version. I suggest you double check your bootloader version and if it is older then the latest Odin update available on http://www.sammobile.com/devices/specs/SGH-I747/ Update to DLK first.

Or try updating the firmware incrementally. If your firmware is MJ2 or below, it is safe to flash any previous firmware without fear.

All available recovery flashable firmware that I have https://www.androidfilehost.com/?w=files&flid=10522

Firmware list: oldest to newest

747UCALEM

I747UCALG1

I747UCDLK3

I747UCDMG2

I747UCUEMJ2

============

Knox firmware

I747UCUEMJB

I747UCUFNE4

1747UCUFNJ1

Need a 16 gig AT&T I747 with a custom recovery.

usb debugging turned on.

adb and a rooted device.

proper drivers for phone installed on your pc

Knowledge of flashing and using Odin.

Checking the bootloader.

If your not sure what bootloader your on.

adb shell
getprop ro.bootloader
exit
exit <--- the second exit is to completely terminate the shell connection.

Or in a terminal emulator on your phone.

su
getprop ro.bootloader

1. In a custom recovery flash MJB bootloaders https://www.androidfilehost.com/?fid=23269279319197285

Reboot phone fully then reboot back into your custom recovery.

2. In a custom recovery flash the MJB to NE4 firmware update. https://www.androidfilehost.com/?fid=23501681358559161

3. Wipe and install UCUFNE4 in custom recovery.

Stock + Root: https://www.androidfilehost.com/?fid=24052804347765735

DeOdex + Root: https://www.androidfilehost.com/?fid=95916177934549032

4. (Optional) Flash the stock recovery in your custom recovery. https://www.androidfilehost.com/?fid=23681161096070493

While working with spagman72 on debricking devices we figured out no amount of ODIN will be as effective as a full wipe in the stock S3 recovery.

A wipe in the stock S3 recovery will also fix any sdcard encryption issues as well.

Now reboot back into the stock recovery and do a factory reset.

5. Use Odin and flash your preferred custom recovery again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Hey man! Nice write up! Does this modded ota preserve root? Ive been trying to get one working all day here... http://xdaforums.com/showthread.php?p=53554046

For some reason it keeps failing to flash. My first attempt was in post #47 of that thread, but TWRP gave an error that the binary was incompatible (or something to that effect).

I changed the updater-binary but it still isnt working. Did you change yours? Just curious if you had any ideas. If yours preserves root though, I guess I don't need to worry about it anymore, but still wondering why it wouldnt work. If you have any thoughts I would love to hear them!

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
I didn't miss anything did I? [emoji3]

it's important that the directions are followed to a t.

I didn't replace the binary I only renamed the file and the extension from cfg to zip. then I just deleted the checks in the installer script. I didn't see anything that would get rid of root but with as easy as it is to obtain again it's really a moot issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chispas109:
ohhh well i did not select repartition and my device updated to kit kat oked. is it a must to select repartition [MENTION=2972841]enewman17[/MENTION]?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Sorry, I might not have been completely clear. It wasn't yours that didn't flash, it was min in the thread I linked. Was just trying to understand why my own modded versions don't work.

The first attempt I only preserved root, and removed the recovery flash. That one was reported to error due to the binary.

Replaced it with a different binary and it seems to have other issues now. (I tried replacing the binary in one and another also removed all the file checks.)

You're right about rooting being easy enough. Just didn't think it'd be so problematic when I started with it. Anyway, no worries. Don't want to take your thread off track any more than I already have!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spoonerdee:
THANK YOU!!!

A million thanks for the easy to follow write up! I've been waiting for this for what seems like forever lol.On the last steps now and everything has been smooth as butter. More or less.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Benzmaffia:
Is this a stock firmware can I jus install it in recovery mode if I don't wanna backup
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
Flashed it this morning, running flawlessly so far..followed every step down to a T !! Thanks man, great work! :good::good::good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ndp1:
Will this wipe out internal SD or just overwrite?

Thanks.

Never mind my question. I followed steps 2 and 6 and was able to update my phone to 4.4.2. Thank you enewman17 and DocHoliday77 for all the help.

thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] poppo101:
After several unsuccessful tries at updating with the OTA, I used this routine and I have successfully updated to 4.4.2.

I had gone back to stock 4.3 using the routine in enewman's thread - http://xdaforums.com/showthread.php?t=2658486 I tried with the phone rooted and unrooted. With CWM recovery and stock recovery. The phone would find the OTA update when checking for update and it would download. When I tried to run the update it would get to 24% and then fail. This morning I found this guide and found success.

Thanks enewman for providing this guide.

Thanks button clicked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jfishel:
Thank you so much for making this post! I ended up using this guide and it works very well.

Any chance we will get a Stock SGH-I747 AT&T 4.4.2 Odin *.tar file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
not sure if making one will be possible yet. missing a cache image that will be crucial to making a working tar.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
if fails because it looks at the bootloader for the warranty bit info. when it sees it is tripped it stops. 24% is around that time in the script when it checks that after verifying the system integrity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
Can I go back to using AOSP ROMS after flashing this? I have one backed up but I don't wanna restore before knowing that its safe to do so
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bronsonelliott:
In step 2, what boxes in Odin should/shouldn't be checked?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
auto reboot and f.reset
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] talkingmonkeys:
Should be fine. Worst that will happen is you'll have to go back on this when it hangs on boot or doesn't get signal/wifi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Well I flashed the latest AICP nightly and it seems all is well.

I also flashed S3Rx but I did have to use the MJ2 kernel to get working WiFi.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shad876:
Ok, thanks. I restored it without any issues whatsoever!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TylerMarshall256:
For some reason TWRP won't flash. This is what I get.

<ID:0/017> Added!!

<ID:0/017> Odin v.3 engine (ID:17)..

<ID:0/017> File analysis..

<ID:0/017> SetupConnection..

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

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

Alright what I had to do to fix that was reboot my computer and do a factory reset and I wiped the cashe too.

But anyways enewman17, You're the man! I'd like for you to take a bath with my two twin daughters, they could learn somethin from you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chandi1985:
no need wipe

No need to wipe data..just flash it will just update android..don't worry about backup.it will be remain as it is..just root flash twrp recovery and flash 4.4.2 OTA updae zip file with recoveery...after 5 minute you will be on android 4.4 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stormdude124:
I'm new to the s3 so forgive me for my noob questions...

Okay so my warranty bit is 1 so I can't do the ota update it failed at 26%

long story on how i screwed up and voided my warranty :p

so I recovered from that using the complete stock restore to 4.3 (which by the way came with the phone when i got it)

since im already on 4.3 I747UCUEMJB

can I just flash the OTA update via TWRP

keep in mind im not rooted

any clarification on if i have to be rooted and if i can just do step 2 and skip to 6

I dont want to brick my phone i already screwed up alittle and its only 1 day old!

Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
The warranty bit has nothing to do with the OTA. Lots of people have been running into issues with it failing at a certain percentage. No idea why though.

Before you do anything, install Terminal Emulator from the store and enter this:

getprop ro.bootloader

This will tell you your current bootloader/base firmware version. If it does say you have MJB and you are running completely stock, you should be ok to just flash the OTA from TWRP.

If it tells you the version is NE4, don't do anything and let us know. (Its possible part of the update was applied. This is why I'm recommending you check using the above command first.)

And in case you have not seen it yet, DO NOT try to flash older firmware than what you currently have or it'll hard brick! Only the same or newer builds are safe. (Old roms and kernels are ok, its just the firmware you need to be aware of)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gsm22:
NE4 firmware kinda screwed the camera on my 4.2 aokp rom (the only one with working sound on my phone), is there a way to fix this?

I've tried replacing the files in /system/cameradata with the ones from latest 4.4 AOKP as well as the ones from the deodexed AT&T 4.4 and fixing permissions. I also tried installing a newer version of gallery.apk and camera2.apk, same error "Can't connect to the camera".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Double check that the cameradata folder has permissions rwxr-xr-x and the files inside are all rw-r--r--

If that doesn't help, flash the stock rom from enewman17, factory reset and test. If it works with stock, you should probably ask the rom dev if he can help.

If its not working with stock, I'm not sure. Try flashing a 4.3 stock rom maybe....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stormdude124:
[MENTION=4081205]DocHoliday77[/MENTION] my boot loader is in fact ucuemjb

So I can just flash TWRP and in TWRP backup-factoryreset-flash zip? Also I don't want root. Do I need root to begin with? Because I had trouble rooting

Thank you for your help so far :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
I believe you should be good to go. And you won't be rooted after the ota. Nor do you need root to begin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stormdude124:
Alright I'm going for it wish me luck!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stormdude124:
Well it worked and I decided to root it after I flashed (my recovery didn't get removed it stayed twrp) Thanks for the help! :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Congrats! And now the real fun can begin! If you so choose of course!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stormdude124:
Could I flash any 4.4 ROM now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DocHoliday77:
Yup! Well, any rom you find in this part of the forum.

If you decide to flash a 4.3 Touchwiz rom, just remember you will need to use either ktoonsez' kt747 kernel, or the MJ2 kernel. Otherwise wifi will not work.

One more thing, well two actually. Backups.

Make a nandroid backup before flashing anything and copy it to your computer for safe keeping. Its rare to really need it, but can be a blessing when you do.

Also, make an on-device backup of your NV Data. Install and open Terminal Emulator and enter this:

su

reboot nvbackup

It'll reboot and create the backup. This will protect you from losing the IMEI and other potential NV corruption.

If you want a better explanation of this, just let me know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stormdude124:
Thanks for the help! Time to get customizing!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony90mr:
Custom Rom Instalation

Hi! So, when this came out I did it and it worked perfectly, but I decided to leave my device unrooted. Now, I'm in completely stock samsung 4.4.2 firmware and I want to install a custom ROM.

Do I have to use odin to flash TWRP 2.6.3.1, then install SU? Or will odin not work if im on this firmware?

Thanks! And sorry for the NOOB question!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enewman17:
Just install twrp via Odin, yes it works on the new firmware.

You don't have to install su in order to flash a custom ROM once TWRP is installed