Database Users

[Q] Milestone 2 in bootloop

Hey all there,
i just bought for some cheap money a milestone 2 on the bay with bootloop problems.
it startsup like this:
just power on with the power button:
red m logo, after some seconds it turns for about a half second to a black screen, again red m logo, and again and again and again
enter the bootloader works fine - 70.13
enter the system recovery works on charger, wiping out didn't help
flashing with rsd lite worked, but didn't change the situation with the bootloop. even after flashing, and wipe out after that.
i'm using windows 7 32bit and x64 on another computer in combination with rsd-lite 5.6
with rsd-lite 4.9 or earlier my device isn't recognized. admin and compitibility is on at all versions of rsd-lite.
anone an idea how to get this stone working again?
i'm a little confused, cause i saw so many posts, of people getting the stone back after flashing with rsd...hmm any help is pleased
greetz

Download rom GingerBread of UK
http://www.multiupload.com/TUZHXCGLMZ
Flash with RSD Lite 5.6... reboot
make wipes (POWER and X....... Vol + and Vol -)... reboot
has to boot normally ...

Just tried several versions of firmware. nothing did work.
i'm thinking about getting the 70.13 bootloader file and flash the bootloader once more.
or give it a try and flash the phone with an update.zip over recovery mode.
but first problem is: i don't have the booloader and the only mirror was megaload, at second i don't have any oem update.zip files. well i will look forward. can't understand why the phone is still looping.
would be happy about any other good suggestions.
greetz

Bootloader 70.13

thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz

MKSilver said:
thanks a lot for the bootloader, but did not help. still bootloop.
now i tried all german, DACH, UK GB fimware.
always rebooting and wiping.
Tha phone is still in bootloop.
May be an OEM update.zip could help. i still got access to the recovery mode.
is it possible to boot from the recovery mode into openrecovery, when the bootloader is original? don't think so, but will try that now.
still happy about an help here.
greetz
Click to expand...
Click to collapse
Don't use a 2 ou 2.2 android..I think it's on GB so you can't downgrade..
Charge your battery to 100%
Folow the step here with a 2.3.4 SBF take here
Have a nice day.

Hey all there,
i already tried to flash GB 2.3.4 Firmware for: Germany, DACH, UK - didn't work out.
of course i did a wipe after installing.
also i tried a rebuilt by renaming CG66.img into CG37img - didn't work out.
just saw, that when i rebuilt the firmware after changing cg66.img to cg37.img, the cg37.img file doesn't appear in the new built SBF.
any reason for that? hmm...
while depacking and rebuilt a SBF i saw, that the RAMDLD.img (ramdownloader) in the 2.3.4 GB DE retail SBF is in version 70.12. i'm no expert in built SBF files, just did this the first time, but could this have an incompatibility with the 70.13 bootloader?
well cause the phone was quite cheap, i will go on trying. may be some more of you guys have any ideas.
the standing now is:
reflash 70.13 bootloader - didn't work out,
flash any 2.3.4 GB SBF and wiping out data after flash - didn't work out
flash update.zip from recovery mode - haven't tried yet - need update.zip file or instruction how to built one.
the last point is my next step i think. i will now go reading how to get this manage.
any help is welcome!
greetz

Okay just learned, that flashing an update.zip with system recovery, doesn't erase any data on the phone, so will look forward, trying flash the phone with sbf under linux live cd.
may be this will help.
does anyone of you know some hardware testing tools for the milestone 2?
to test the ram/rom hardware...
i'm starting to think, that some of the hardware chips may be damaged.
hmm i always thought, that it is not possible to brick a stone with original bootloader/rom-image/firmware. just starting to learn, that it is possible although.
any help is welcome guys! my ideas are going to end.
greetz

Got still no luck and tried to flash it with sfb about 16 times now. RSD-Lite tells me it was everything okay, but still bootloop.
Any good ideas?
Greetz

You have no real idea of the phones history, so you may have to accept the possibilty that it could be a hardware issue. Perhaps it has taken some water damage (the indicators do not always end up going off btw - I fell into a pool fully clothed and the nokia i had at the time wouldn't ever recognize a sim again, yet no water damage indicators get wet somehow . Yet the rest was soaking)
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
A thought occurs.... does it actually have a sim card slot? Like... is it possibly a Droid 2? :S
---------- Post added at 10:25 AM ---------- Previous post was at 10:20 AM ----------
Mikevhl said:
I know it's a bit extreme to do, but it might help for you. Try installing ubuntu or wubi, then use sbf_flash on ubuntu. It takes some time, but if you REALLY need to SBF you should give it a try. Usage is:
chmod 777 sbf_flash
./sbf_flash /path/to/sbf/file
Click to expand...
Click to collapse
Got that from the recovery thread.
I dug up this guide to using ubuntu live cd to flash sbf's for the droid 2, hopefully you are switched on enough to workout what you need to do differently for the MS2
http://forum.xda-developers.com/showthread.php?t=804088
I'd try that and see what happen

Hey guys,
first: thx to DreadPirateDan. you're right, i don't know enough about the phone. So i sat down after work and startet to read and with all the basic information i know about the phone. While analysing all the things i just saw a special thing in the bootloader:
When the phone is switched on into bootloader, the screen shows:
"Bootloader Fastboot mode
70.13
Battery OK
OK to Program
Transfer Mode:
USB"
So it seems that i've got the fastboot script active. So i should do everything with the phone i want to do, right?
i will go on reading. maybe i will find any way to check all the files.
Is it possible, that the phone loops because of fastboot mode and a secret saftyissue which bans all phones booting with active fastboot?
May any of u check on a not rooted and for difference rooted milestone 2, if the fastboot notify is standard?
Btw - got a Sim-Slot, so it seems to be a Milestone 2.
greetz

This ones a long shot - but if you have another USB cable available, try using that. Perhaps the one you are using is somewhat damaged - not enough to cause errors flashing, but enough to corrupt data? I don't know but i'd certainly give it a try! .
---------- Post added at 08:00 AM ---------- Previous post was at 07:59 AM ----------
Yeah that's the screen of bootloader saying it's all sweet to flash with rsd-lite
So that's a good sign
I'm concerned perhaps it's had some physical damage to the system storage.
I'm just confused, your steps appear to be all correct, what you've done allready, and it should have worked allready!

How did u get into Bootloader Fastboot mode???
Are you sure it says 'Fastboot' coz Fastboot could mean unlockable bootloader?
May be some developer could throw some more light on this.

When we first got the Chinese GB link I remember there were a couple of guys who had deceloper phones.. They never explained how they'd got them though lol
Sent from my MotoA953 using xda premium

Fastboot confirmed
Hey Guys,
well its definitly Fastboot. I installed Android SDK yesterday and tested a little bit.
I can flash images through fastboot and all those things.
Poblem is, i'm not so familiar with all those things. I know a little bit of electronics but not so much about how software and specially android works with the hardware. Just started yesterday to read about this.
Attached are some pics of my phone during bootloader and how it looks.
Now it would be first nice, to get this thing work!
Because at the moment it hangs still during booting, cause i don't know so much about how to flash from fastboot.
When it is true, that this could help this forum here, i won't sell it anymore. But i need help to work all this out.
I contated parallely the customer service of motorola at my country, to ask, if this device has still waranty via IMEI, but they don't have this IMEI in their database.
So come on guys, more information, how get the phone work again, may be with any rom we wish someday without hacking anything
greetz

I have the same problem. tried to bootstrap after ive installed cyanogen 7 and now im stuck on the M logo. wiping cache or factory reset won't work
thing is the links for sbf files at and-developers won't work :\ so now i cant flash anything
plz help

Alot of file sharing stuff got shut down just recently that's why all the links are dead
if you had previously upgraded to gingerbread, that is your problem - cm7 doesn't work with it. Have a crack at the dowgrade method endless7 has and then you can flash cm7 with CWM.

ok, i figured it out. just searched google for one of the builds. flashed it and it turned out to be a french retail version of froyo. installed MIUI rom. works fine

I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.

Nikunj3xP said:
I maybe resurrecting this but I need help. I got my milestone 2 yesterday and then I rooted it successfully and then I tried to use ClockworkMod (Rom Manger mainly) to flash CM7. and well my phone is stuck in a boot loop now. It starts with a red M logo and then it goes to the CM android sliding in and the circle spinning then freezing and going again. I can only get into bootloader mode and when ever I plug my phone into my computer to use RSD it says chip error 43. I can't even find an SBF for my phone since all the links where to Megaupload. Please help
EDIT:
Okay so I just used the newest version of RSD and got a SBF for my phone but still the same thing happened. This time RSD kept on going and the CM android did what it was doing before.
Click to expand...
Click to collapse
hi,
Can you please explain clearly if you are able to boot CWM recovery or are you just getting a boot loop and unable to boot to recovery? As far as I know you won't be able to flash clockwork mod recovery for the Milestone 2 using ROMManager .You need to use Droid 2 bootstrap recovery.

root HTC Legend - unlockroot.com

Hi,
did anyone tried the tool from unlockroot.com?
PHP:
HTC HTC Legend 2.1
HTC HTC Legend 2.2
It should work for HTC Legend but I tried one and it didn't work.
Is there any other one-click tool for rooting a HTC Legend 2.2 available?
greets, Makus

I tried it, and it worked for me, but for almost all the users with Froyo can't make it work...
I think the reason is that only works with S-OFF

Not sure if there is a one click root for legend yet.
Sent from my Legend using xda premium

On website is written that it should also work with Froyo 2.2 but on my Legend 2.2 I only get reboots and after 5 minutes I removed the battery. :-(

Hey all,
I have the same problem with an HTC Legend and Froyo 2.2.
When i clic on "root" i receive "failed to get shell root" and after few minutes, my phone reboot.
Any idea ?
I read we have to S-OFF, but how can i do that ?
Thanks

Doesn't work here either.
My legend has its bootloader unlocked (S-ON), HTC dev.
I receive this message: failed to chmod file: /data/local/tmp
Edit: I just rooted my HTC Legend with "HTC Supertool v3" (Step 1 and 3)

"Official" rooting mechanism?
HTCDEV now offers an official way of unlocking the bootloader; see http://www.htcdev.com/bootloader.
Has anyone used this yet?
I have a Legend lingering around; got a Nexus S, so the Legend is mostly lying in a drawer now. If I could get (say) CM7 onto it, it would be at least somewhat more interesting again.
I tried fighting through the "generate Gold card and root it" process without any success; I was on a newer version and had to do the RUU downgrade; it would get partway through and fail. It would certainly be interesting to have an extra toy

cbbrowne said:
HTCDEV now offers an official way of unlocking the bootloader; see http://www.htcdev.com/bootloader.
Has anyone used this yet?
I have a Legend lingering around; got a Nexus S, so the Legend is mostly lying in a drawer now. If I could get (say) CM7 onto it, it would be at least somewhat more interesting again.
I tried fighting through the "generate Gold card and root it" process without any success; I was on a newer version and had to do the RUU downgrade; it would get partway through and fail. It would certainly be interesting to have an extra toy
Click to expand...
Click to collapse
Did it today.. worked perfect to unlock bootloader.. will now try to get root access. Before this was available it wasnt possible for me to root with gold card method due to my bootloader version :-(.. I have a galaxy s2 but hoping to breathe new life into the legend .. I was on build 3.15.405.3 froyo 2.2 before I started this process if that helps...

do it with htc supertool:
http://forum.xda-developers.com/showthread.php?t=1431398
it worked for me after i unlocked my legend via htc dev

If you want to flash a rom you dont need root. Just flash recovery and Go
Sent from my Legend using XDA

is it necessary to be root on phone before flashing a custom rom ?
after unlocked i flashed recovery_legend_5.0.2.8.img but i am not able to flash a new rom
after i booted in to recovery mode i chose flash zip from sd card option in the list it couldn't pass to next screen, options listed in the main menu goes off and i can see only cwm icon (a black hat over a yellow circle) i waited 2-3 minutes but nothing happened when i press power button it returns to main menu again.
Also other options listed in the cwm main menu not goes further, reboot system and power off, wipe data... either, same thing happens as described above.
i am waiting your suggestions
---------- Post added at 03:45 PM ---------- Previous post was at 03:22 PM ----------
zupervisor said:
is it necessary to be root on phone before flashing a custom rom ?
after unlocked i flashed recovery_legend_5.0.2.8.img but i am not able to flash a new rom
after i booted in to recovery mode i chose flash zip from sd card option in the list it couldn't pass to next screen, options listed in the main menu goes off and i can see only cwm icon (a black hat over a yellow circle) i waited 2-3 minutes but nothing happened when i press power button it returns to main menu again.
Also other options listed in the cwm main menu not goes further, reboot system and power off, wipe data... either, same thing happens as described above.
i am waiting your suggestions
Click to expand...
Click to collapse
damn it!.. what a silly mistake
inside the cwm menu i have to make a selection by hitting the trackball but i was pressing the power-button

Yeah, pressing the powerbutton in recovery just Shows this Image.
Sent from my Legend using XDA

AlexS_xda said:
Yeah, pressing the powerbutton in recovery just Shows this Image.
Click to expand...
Click to collapse
thanks, i use trackball to select menu options and installed custom rom fuse 2

Well I am stuck, got a horrible Legend with 2.2 locked to Vodafone Spain - No bootloader update yet on HTCDEV and nothing works. Can't even update my aps on the SD card coz phone says not enough memory to install. Got 12Gb on the card and only stock Vodafone stuff on the phone itself.

rexjarvis said:
Well I am stuck, got a horrible Legend with 2.2 locked to Vodafone Spain - No bootloader update yet on HTCDEV and nothing works. Can't even update my aps on the SD card coz phone says not enough memory to install. Got 12Gb on the card and only stock Vodafone stuff on the phone itself.
Click to expand...
Click to collapse
try cyanogenmod.. with a good guide and using the stable rom you'll get a satisfying phone..

I unlocked with HTCDev, rooted with Supertool. Then installed RomManager, tried to install CWM, it said it was downloaded, great.
I rebooted to recovery, but only thing i can see is that exclamation mark, no CWM. Whadda?
---------- Post added at 08:19 PM ---------- Previous post was at 08:03 PM ----------
Solved, putted the image in the same directory as fastboot.exe, rebooted to fastboot with usb connected and
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Well, I could have spared many of my academic hours if i from the beginning knew of this and of the ability of rooting without downgrading.

reply
Ihaveatattoo said:
I unlocked with HTCDev, rooted with Supertool. Then installed RomManager, tried to install CWM, it said it was downloaded, great.
I rebooted to recovery, but only thing i can see is that exclamation mark, no CWM. Whadda?
---------- Post added at 08:19 PM ---------- Previous post was at 08:03 PM ----------
Solved, putted the image in the same directory as fastboot.exe, rebooted to fastboot with usb connected and
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
Well, I could have spared many of my academic hours if i from the beginning knew of this and of the ability of rooting without downgrading.
Click to expand...
Click to collapse
HI, i have done exactly what you did unlocked via HTCDev rooted with Supertool then installed RomManager.installed CWM n downloaded.like you when rebooted to recovery got the same exclamation mark!
Can you explain how you solved it as i dont understand how you did it ?? thanks

Loook at my thread for unlockroot.com
It works and you dont need to be s-off...........i rooted a legend with s-on.
The only thing you have to do when you use unlockroot is unlocking bootloader

Can't believe this xda website had me screwing around trying to get HTC Supertools for 3 hours, the tools that by the way are no longer on the file hosting site. I downloaded this tool and 20 seconds later the phone was rooted.
Message to xda moderators, please clean up all the out dated and garbage posts on this website. Never seen such a confusing pile of crap in my life. Specially that stickie post on all things Legend, I no longer trust anything posted on this website.
Thanks to the op, they should put you in charge of the Legend part of these forums.

Hi,
I don't know how you guys managed to root the legend, I'm stuck. I have a legend with stock Rom 2.1 update -1 I can't update to froyo or root my phone. I'm frustrated.

[Q] OUT OF IDEAS- Nexus 4 stuck on boot loop

Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.

airrunner said:
Could someone please offer some advice, i really am stumped on this one. I have a nexus 4 which is rooted has an unlocked bootloader and is running on the stock version of kitkat. Last week i changed network and as bizarre as it sounds when i got disconnected from three my phone bricked and got stuck on the boot logo.
Since then i went home and got the skipsoft toolkit up and running to essentially put a fresh rom on. Unfortunately no luck, i have gone into the bootloader and recovery,factory/wipe reset -- still no luck it's stuck on the boot logo. Now i realised that adb isn't working only fastboot which has also limited my options. i have tried multiple version of roms/recoverys etc.. they install which confirmed by the change of boot logo but that's it just hangs again.
Is there something else i can try? I would really appreciate some direction on it. Thanks very much in advanced.
Click to expand...
Click to collapse
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/youtube
---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK..www.wugfresh.com/
Click to expand...
Click to collapse

[/COLOR]
WelfareBaby said:
What do you mean you changed network? What recovery are you using twrp or cwm hope it's twrp I think you need to search forums for wugfresh tool kit and start fresh which means going back to stock rom, recovery etc.. Wugfresh toolkit is the easiest method for you and even has videos on YouTube for step by step instructions you can't go wrong be patient and pay attention and you will be OK
Click to expand...
Click to collapse
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.

airrunner said:
[/COLOR]
I meant literally that i changed network from three to ee, which i also brought my original number over with it. The day my number transfered to ee my phone bricked and it's been stuck on boot loop since.
I have never used wugfresh before but i followed your instructions and spent sometime with it this morning. It's a very simple piece of software and i must admit i was feeling hopeful it might have fixed my boot-loop issue, but it hasn't. I have done factorywipes/wiped cache, flashed multiple version roms. As far as recovery i had TWRP running on my device, but for some reason i am no longer able to go into it only the bootloader. When i do click on recovery i got the android on its back with the exclamation mark, which obviously gives me the wipe options which i have done.
If there is anything else you can think of i would be greatly appreciative.
Click to expand...
Click to collapse
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
---------- Post added at 12:57 AM ---------- Previous post was at 12:56 AM ----------
WelfareBaby said:
.
I really have no clue what changing network to ee is did you not create a backup if so you could restore it but since you can't once you get in bootloader and scroll to recovery you get dead android use to toolkit I told you and flash stock+unroot option it should work
Click to expand...
Click to collapse
If not pm me try to help you figure it out

I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential

airrunner said:
I am very grateful you taking the time to help me with the boot issue. But i have actually just managed to sort it, finally!
It came down to me changing to an older radio version for 4.4.4., then i installed a 4.3 rom which it worked! I then upgraded to 5.01 and hey presto it's back to normal.
Thanks again nexus root tool-kit is definitely an essential
Click to expand...
Click to collapse
Your welcome glad I could help we all been in some situation before since you back up and running don't forget to make a backup of current rom always good idea to have that handy in case.. Cheers...

Samsung Galaxy S5 (G870A) Bootloop Fix!

I've recently found away to fix a Galaxy S5 Active stuck in a boot loop. (This method only works if your device is on lollipop 5.0! )
Note: This method only works on the OC5 update.
More firmware support coming soon.
What happened: I accidentally made my Galaxy S5 Active get stuck in a boot loop. I couldn't find a solution for the longest time because the bootloader is locked. Time passed and I eventually found away to fix the boot loop if your devices is running Lollipop 5.0!
Solution:
1. You should always try to fix the boot loop by booting into recovery mode by holding down the Home+Volume-Up Key+Power button. Once the phone logo pops up on the screen releases the power button only, but continue to hold the Home+Volume-Up Key. If it worked is should say "Booting into recovery." or something along those lines in blue letters.
Once you're into recovery use the volume keys to navigate Up and Down. Find wipedata/factory reset. Select it with the power key and navigate down to Yes. Wait till it finishes. Then see if that fixed the problem. If not proceed to next step
2. Since the boot loader is locked it's really difficult to flash any kind of Recovery, ROM, or Stock Rom unless your phone accepts it as a valid file. So here's what you do!: (Method 1)
Download this file and save it to your desktop: https://drive.google.com/open?id=0B3UBRFq3BojVQnBSc3lCSzloYUU
Download ODIN v(3.09): http://odindownload.com/Samsung-Odin/#.VgiJ_8tViko - Extract it to your desktop.
Put your phone in download mode. (Note: Before you do this, install the correct drivers for your phone to your computer.)Make sure your phone is completely off and Hold the Home+Volume Down+Power. You will get a warning message just press the volume up key to continue.
Go to desktop and launch ODIN. After ODIN pops up, plug in your device. (Make sure you have the correct phone drivers installed)
You should see a dialog box in ODIN that say 0:[COM6] in blue. Note: It might be different for everyone, just make sure it says COM.
After that, Under "File [Download]" click "AP" Then navigate to the file you downloaded earlier called "boot.tar"
MAKE SURE RE-PARTITION IS UNCHECKED!
Leave everything else alone then click start. Wait till it says PASS! in green letters in ODIN!
(Method 2):
Go to this link download it to your desktop and follow the instructions: https://drive.google.com/file/d/0B3UBRFq3BojVdXlSUE43VzJPbEU/view?usp=sharing
Done! Your device shouldn't be in a boot loop anymore! If you have any questions let me know!
Note: Once this process is complete, your phone will permanently show a warning in your notifications saying "Unknown action detected." This happens because your phone will detect that your kernel was modified so if you don't want this to happen, then I suggest you wait for a official lollipop OS release.
UPDATE!: You should now be able to download the "Boot.tar" file. Sorry about that!
UPDATE!: New files and instructions added if the first method didn't work!

Having some major issues
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.

Ghujii said:
First post so forgive me if this is misplaced. Before I was aware I'm unable to down grade from 5.0 or 5.1 version of sm-g870a I attempted to downgrade and apply root from version 4.4.2/4.4.4 via another XDA thread in a faulty attempt to root. At first this presented no issues until restart. At this point the phone is soft bricked and bootloops. Both download mode and system recovery ARE accessible and prior to this I had USB debug open. I have the factory cable and odin identifies the device easily. All other md5 files failed to apply OTHER than one. (4.4.4 ota) I presume because of bootlocks which I'm now aware of. I have attempted three different stock flashes via odin all from XDA all fail at authentication claiming error fused 2 binary 1. I attempted add data pull before all of this and the device ignored a request which prompted a factory reset which was odd. I have attempted installing 3 alternative stock and stock rooted 5.0 and 5.1 firmwares from XDAs threads. All of which failed, hiwever one granted me some precious Information when I slowed down the error message via recording. It states, "Package expects fingerprint of Samsung kltattactive/lteactive:4.4.2/kot49h/g870aucu1ang3:user/release-keys o0A1:user/release-keys this device has kltactive/kltactive. This tells me as far as I know that the device is showing no firmware installed and a double fed file making the attempting installation incompatible. At this point I want to start anew, I have how attempted every route accessible via XDA and feel my options are running very low other than attempting to randomly apply firmware in sequence until odin accepts one and it sticks. That sound like a brick plan however. I don't care what firmware is loaded as long as an OS is accessible. I think this is all available Information I apologize for typos I have been at this for a total of 20 hrs straight. This bootloop was a tired lapse in judgement and has cost me 5 hours of trial and error. Wiping cache fails, reformatting internally fails, as far as I know root was never successful and I THINK philz was successful installed although at this point I cannot recall. Thanks for reading and in advance for any available help. I have SOME c# experience and some java script which is zebra vs dolphin situation I only mention as to aide and explain my trainers of thought. All other languages are vague at best
Edit: I stopped bootloop with the file attached to this thread. It now boots into samsung display bht will not go further and stops there as though it still has no operating system.
Click to expand...
Click to collapse
New method for you...

irontaco1 said:
New method for you...
Click to expand...
Click to collapse
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?

Ghujii said:
Alright this stopped the looping now, to find a proper rom. I believe. Im going tohave to wait for 5.1 in order for it to be successful, however is having 4.4.2 still on it is a bit worrisome, I predict overwriting it should be fine though. Thank you for giving me a way to at least resolve bootlooping. I believe I shoulda have safestrapped the device, but hindsight is always 20/20 eh?
Click to expand...
Click to collapse
I'm glad you got past your Bootloop! If you need anymore help let me know.

Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active

I'd say hold off for a while I did that exact 5 Hong with the s5 active and it bootlocks it. You need to, if you're going to do this install and use safestrap to di so and BACK UP EVERYTHING with safe strap to SD. As long as you follow those method you SHOULD be able to even soft brick it and come back from it.

shadavis08 said:
Is there a way to root my galaxy s5 active [G870A] on att with 5.0? I'm getting conflicting info and not finding the root.tar I need to flash in order to roll back to 4.4.2 so I can root. Right now I'm just trying to get root. Thanks for any help or direction.
S5 Active
Click to expand...
Click to collapse
I haven't found any successful way to to go back to Kit Kat or 4.4.2 for this phone. In fact that's why this thread exist is because people who have tried to flash back to 4.4.2 have failed and got stuck in a Bootloop. So if you plan on trying to find away make sure you back everything up and if you fail you can use this tutorial to get your phone working again.
Make sure you have "USB Debugging" on
Make sure you have the drivers for your phone installed on your PC before you start the process of looking for a root.

Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2

shadavis08 said:
Yeah I tried flashing back to 4.4.2 and it was a no go . I had the stuck on 5.0 issue where download mode says "downloading do not turn off ...... " but after I wiped my phone I was able to update to 5.1.1 successfully without any "download interrupted "errors . So at least I'm not stuck on 5.0 now lol
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
---------- Post added at 03:24 PM ---------- Previous post was at 03:21 PM ----------
Although I still have that "Downloading do not turn off target " thing when I try to enter download mode! Sheesh
Sent from my SAMSUNG-SM-G870A using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
There should not be anything attempting to download when you boot into ''download mode'' if there is, its highly likely there are still particulates of the last bad flash. I would as he said above, enable USB debugging and the like, and install safe strap to be safe. After safe strap is done and youve followed the tutorial which you can find in another thread on this site, boot your phone down and then power it back on, safe strap should come up first, when it does so push the ''recovery'' option to enter safe strap( someone correct me if thats wrong, my phone is currently dead/charging so i cant check) From there you can back up to an SD card, make sure you enable compression when you do.
Once thats done, WIPE YOUR PHONE, and Cache,( maybe dalvik as well if you cant find it dont worry.)and its all on SD CARD, then attempt to dirty flash( I dont recommend), or clean flash your device WITH safe strap. This typically entails downloading a .zip file and opening it THROUGH safestrap, which is done the same way as backing up your data, only via another option in the menu. Simply put; Back up data with safe strap, after thats done push back and choose FLASH, it should show you all available items it can flash from/to, pick and pray. I didnt go this route when I tried, I attempted to brute force the Bootlocked S5A, and it caused some errors that I now have reversed after much pain. If I HAD safe strapped, It may have went smoother for me, and may for you. Safestrap for us Samsung users is the same as Clockwork Mod for the rest if you weren't aware.
I'll edit this when my phone charges and I can walk you through appropriately, if need be MSG me and Ill do it as soon as I receive the message via this thread if I have not already.

hi guys! good day! i have tried the new method twice! and odin fails everytime! the problem is with the modem.bin! is there any way to fix this?

Make sure you're running lollipop and not Kit Kat and make sure you have the correct phone model. If you don't meet both those requirements then it won't work.

it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1

abatoir said:
it has on lollipop recoverymode comes up with LRX21T.G870AUCU1B0C5. ISNT that lollipop? download mode also says ;A2, P1
Click to expand...
Click to collapse
Yeah that information is correct. You might want to download the latest version of ODIN and try again. (Make sure you're putting the modem.bin file in the correct spot in Odin.)

I think I have the latest odin.. And modem can only fit in the cp field I think. Its just not working for me. I tried doing each part separately. And the modem flash always fail.
---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------
I used odin 3.10 and also tried with odin 3.7

Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.

abatoir said:
Hey irontac. Since you came up with this fix. Are you able to tell me why those s5 go into bootloop like that? By the way mine is not in bootloop. It hangs on the AT&T logo (the glob) . I was thinking maybe I need to flash the system.img , but where can I find that. And how can I flash it by itself? Actually the phone belongs to a friend. He seems to have rooted it. But I don't know what else he messed with.
Click to expand...
Click to collapse
You might want to boot into recovery mode and try to factory reset it normally. If his phone is rooted you could also flash a custom rom to it and get it out of Bootloop.

I also forgot to mention you can't get ahold of the system.img because it's not released to the public.

Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?

abatoir said:
Yeah. I wanted it back to stock. I downloaded the 5.0 cfg file. Opened it up and I realized that there is no system.img in there. Oh Well. You think it would boot if I used kitKat system.img?
Click to expand...
Click to collapse
If you flash the Kit Kat system.img you might have to downgrade the kernel also. I would give it a try and see if it works.

AT&T Samsung Galaxy S7 G930A Root Install Instructions?

If anybody can put up a step-by-step guide, or a video that shows how to properly install it all, I'm sure myself, and much of the community would appreciate it.
Recently, my laptop that I had ADB, and every tool imaginable for Androids, and specifically the Galaxy Series, took a huge dump on me and I lost it all. I installed it so long ago, that embarrassingly I've forgotten how I did it all. If someone could post how they rooted their GS7 (non-edge variant), I would be very appreciative. And I'm sure much of the community would be too. I'm embarrassed to even have to ask as someone who used to formerly develop mods on phones. But it is what it is. It's been so long since I've set it all up, and I've had to do so much since that time that I've simply forgotten how I did it/how to do it. Any help would be GREATLY appreciated. Thank you ahead of time...
I've tried following the instructions in the sticky above. I ran the 930X ROOT.TAR in the special version of ODIN. And every ran OK. It said "Success" and then rebooted. All seemed well, then it froze on the AT&T Boot Logo. What can I do from here? I know from history that this is one of the points that people panic and claimed "brick" (though I've never seen a real brick from rooting). Any help would be greatly appreciated

There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk

twizt3d said:
There's a great guide in the Verizon forum. Root was universal based on FW. Just make sure you flash the correct 930 or 935 with the modded odin. I recommend you follow the steps to "unroot" for the sake of doing an extremely in depth factory reset. Also make sure you get chain fires latest supersu built for the s7qc.
Sent from my SAMSUNG-SM-G930A using Tapatalk
Click to expand...
Click to collapse
thank you for that. I'll check it out. Hopefully it'll get me past this bootscreen issue
yup. Great instructions. All set rooted now. Now time to play with xposed and V4A and the like. Yay

OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks

thanirs said:
OK. Followed the instructions on the Verizon page and used the PrinceComsy version. Stuck at the AT&T logo. How did you go past this step? Should I have used the standard version? thanks
Click to expand...
Click to collapse
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can

Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
52brandon said:
(keep in mind this is only my personal experience...)
but the PrinceComsy version of ODIN was the only one to work for me. How far exactly have you gotten in the process before you got stuck at the logo? You do have ADB installed correctly installed on your PC and turned on on your phone right? and cd-ed the specific "super" folder for the SU adb install, right? FYI: It's not a simple root process, like 1-click roots on previous devices. This is more similar to the in-depth root methods like on the N1 and D1 before super nice devs went out of their way to make it simple. So if you're not familiar with ADB shell and the likes, it'll be difficult for you. But, no matter how high and mighty or condescending people act, we've all had to start somewhere. I'll help you get through the process as much as I can
Click to expand...
Click to collapse
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
Click to expand...
Click to collapse
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.

thanirs said:
Thanks for your reply. BTW I am fairly experienced in this stuff. This is what I did to get it to work. ADB and drivers all work fine.
Flashed the boot image using the PrinceComsy version. Got stuck at AT&T logo
Attempted to flash with the other version of Odin. When I open Odin, a window would pop-up with some ini issue and Odin would close immediately.
So I moved the ini file from PrinceComsy version to the other version. At this point, Odin would open and detect the phone at the correct COM port
Tried flashing it with this Odin but I got a SHA256 error
SO..
I went back to stock (which deletes all data, no big deal - everything was backed up)
Boot was successful
Re-flashed with the boot image and viola!
---------- Post added at 08:47 PM ---------- Previous post was at 08:21 PM ----------
OK. Proceeding with the recommended steps in the install guide, I ran into this one nagging pop-up:
Security notice: Unauthorized actions have been detected. Restart your phone to undo any unauthorized changes.
Its a rather annoying notice that keeps popping up. What is the fix for this? Quick 'google' suggested some people uninstalling Knox altogether and it seemed fairly drastic. Suggestions?
---------- Post added at 09:08 PM ---------- Previous post was at 08:47 PM ----------
OK never mind please and sorry. Found the answer in the Fix/debloat script.
Click to expand...
Click to collapse
so you got it all figured out and running great now right? No other issues right?

Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33

twizt3d said:
Just to add to this, I have verified that this still works using PG1.
http://forum.xda-developers.com/showpost.php?p=67970468&postcount=33
Click to expand...
Click to collapse
Can you please try restoring to af2?

Thanks for the ping. I think so. One thing I ran into which I don't know if its related to rooting. When I am in a phone conversation, audio on the other end goes in and out after a few minutes into the call. This happens with bluetooth or not. Still figuring out this issue.
52brandon said:
so you got it all figured out and running great now right? No other issues right?
Click to expand...
Click to collapse
Seeing battery drain. So went back to stock /unroot for now.

I was not trying to root my phone but reflash to an earlier version. I tried the Prince version of Odin and it did not work. The version that ended up working is in this thread
http://forum.xda-developers.com/att-galaxy-s7/how-to/firmware-g930a-edge-variant-afp-stock-t3415344
http://click.xda-developers.com/api...ww.mediafire.com/download/2t...din_3.12.3.rar