Develop Bugs

Need Xoom WiFi boot.img

Looks like the boot.img on the WiFi only model is slightly different. Flashed the rooted boot.img file and now I'm stuck at the Dual Core technology screen. Anyone have this available. All help greatly appreciated!
UPDATE
See thread -> http://forum.xda-developers.com/showthread.php?p=12432218

Can someone post the stock xoom wifi dump of the boot.img, recovery.img, system.img, and userdata.img in case something happens?
Apparently it looks like its slightly different than the wifi+3g version. Also is the overclocked kernel file working posted by coolbho3000?

i need the answer too... i m comfused.

Alright I have a stock Xoom tablet now Just gotta figure out how to pull the boot.img file off. Any ideas and I'll do it ASAP.

No clue mate. From my knowledge you have to be rooted, or have the SDK on your pc. I think. Neither which are available as of now

So is the wifi only version able to be rooted as of now?

currently, yes. We need a new root method. Well I would not say a new "method" but their need to be some modifications done to the original rootboot img file. Shouldnt be hard for devs

found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img

onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Issue 1: Don't currently have root
Issue 2: No SD card access
But I did try it and got an access denied.

onicrom said:
found the answer here:
http://forum.xda-developers.com/show...&postcount=134
coolbho3000 said:
If you want to rip your current one, run
# cat /dev/block/platform/sdhci-tegra.3/by-name/boot > /sdcard/boot.img
Click to expand...
Click to collapse
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App

B Dizzle said:
Think for the Xoom it would be from a windows command prompt:
adb shell cat /dev/block/platform/sdhci-tegra.3/by-name/boot > c:\boot.img
I could be wrong but try it and see.
Sent from my Nexus One using XDA Premium App
Click to expand...
Click to collapse
It's actually a Permission issue.
/dev/block/platform/sdhci-tegra.3/by-name/boot: Permission denied

So someone with root needs to run it. Anyone wanna help out? Im not getting mine till tomorrow but by then I suppose you would have yours exchanged
Sent from my Nexus One using XDA Premium App

B Dizzle said:
So someone with root needs to run it.
Click to expand...
Click to collapse
That's actually the catch-22... can't get root because we don't have the right boot.img file. I think it's going to boil down to Motorola releasing a stock one.
If anyone is up for IRC chat - hop onto Freenode and room #Xoom

I can try if someone tells me what needs to be done. I tried copying it over to another folder in root explorer but no luck.

Update: Ran through the fastboot oem unlock in hopes that it would resolve the Permission Denied. It did not.

http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154

destroyerbmx said:
http://forum.xda-developers.com/showpost.php?p=11863700&postcount=154
Click to expand...
Click to collapse
You'll end up with a (soft)brick

No luck
I also booted into fast boot, tried and still got no permission sometimes and no such directory some times... If some one will walk me through getting the img file I will gladly do so

how can I remove the softbrick, I saw this AFTER I tried to root and now I cannot even turn it off, just sitting on the Motorola Dual Core Technology screen.

ok I also now need to the stock boot.img from a wifi xoom. Can anyone help? I can flash it if someone can provide it please, if not I guess I will go exchange my xoom in the morning.

[Q] Need to brick my Tmobile G2

Hello all,
I could not find a thread that directly related to this phone and request.
I am having reception problems and have tried every radio available. I still get dropped calls etc. I think it has been dropped on the floor one to many times.
So, I would like to brick it completely. No bootloader, nothing. I have CM7 and the latest recovery Clockword Mod. If I do not brick it I will need to pay 130 dollars for my deductible... If I brick... well its free =) So does anyone have suggestions or experience with this? And no I cannot set it on fire or throw it in a puddle or etc... Thanks!

I have heard that putting it in a microwave for a couple seconds does the trick.

You could try flashing a corrupted radio image. Though I'm not sure how you would intentionally corrupt the file. Maybe dd if=/dev/urandom into the file?
--MrAnt--

Flash a radio or SPL then pull the battery half way through

type rm -r * in the root?

Suppose I could try the radio flash first... and if that does not work... Microwave for five seconds. I am suprised there isnt a section devoted to this here at xda. -Thanks

Flash a firmware from a diff device ... 100% chance of a brick ... Should be doable if ur completely s-off ...
Sent from my HTC Incredible S using XDA App

knightrocker said:
Flash a firmware from a diff device ... 100% chance of a brick ... Should be doable if ur completely s-off ...
Sent from my HTC Incredible S using XDA App
Click to expand...
Click to collapse
mrant said:
You could try flashing a corrupted radio image. Though I'm not sure how you would intentionally corrupt the file. Maybe dd if=/dev/urandom into the file?
Click to expand...
Click to collapse
dpgc213 said:
Flash a radio or SPL then pull the battery half way through
Click to expand...
Click to collapse
These sound like good ideas! These are more likely to brick your phone!
adamhlj said:
I have heard that putting it in a microwave for a couple seconds does the trick.
Click to expand...
Click to collapse
This idea will leave enough damage to it that T-Mobile will immeadiately think suspiciously. Your device might then get shipped back with no repair.

Yea the microwave would be the last ditch effort. Tmobile has shipped me a new phone already.. I have to return this one when it arrives. They will probably try to refurbish my phone or something. So a software brick is ideal. I really appreciate all the suggestions. I will post the one that I use and if it works when I recieve the new phone.

Just give it to some crackhead in exchange for a newer Android device.

Just kill your hboot partition using dd while in userland
I dont remember the partition number, but you'd
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
Or find an hboot for say the g1 and flash that, out would give new meaning to dangerspl.

amazinglarry311 said:
Just kill your hboot partition using dd while in userland
I dont remember the partition number, but you'd
dd if=/dev/zero of=/dev/block/mmcblk0p*
Where * = the partition number.
Or find an hboot for say the g1 and flash that, out would give new meaning to dangerspl.
Click to expand...
Click to collapse
Wow. Why not just tell him to flash CyanogenMod Recovery 1.4?

Uh.. Because flashing a bad recovery doesn't brick your device.
Read the thread.
He doesn't even want it to power up. A bad hboot will ignore boot signals and give him what he wants.
Do you guys like being contrary and wrong all the time? Or do you just single me out, because I know what I'm talking about?

knightrocker said:
Flash a firmware from a diff device ... 100% chance of a brick ... Should be doable if ur completely s-off ...
Click to expand...
Click to collapse
While a brick is possible, I don't know if its a sure thing. Not sure, but I seem to remember at least one noob on here who unwittingly tried to flash the ROM for another device. The ROM didn't work, but it didn't brick the phone either.

Flashing a rom for another device will only soft brick you.
Kill the hboot, kill the phone.

I've got a wonderful pre-bricked board for you! Let's trade .

Tell em u got an ota and you dropped ur your phone half way through....works every time!!!!!
Sent from my HTC Vision using XDA Premium App

blackknightavalon said:
Just give it to some crackhead in exchange for a newer Android device.
Click to expand...
Click to collapse
You mean like koush? Jaws just playing.. Don't suspend me koush.. I love you... Lol

amazinglarry311 said:
Flashing a rom for another device will only soft brick you.
Kill the hboot, kill the phone.
Click to expand...
Click to collapse
He is correct!
Kill Hboot, It will be all done!

Thanks for making my next HTC device cost more.....
Sent from my HTC Vision using XDA App

Phone app requesting superuser

This just started today. Anyone else having the Phone app request superuser?

I just had "reset notify" request superuser, and I'm at work so I haven't had a chance to figure out what it exactly is yet.
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Phone asked again today. Only one it seems. Tempted to let it go haha.

I have it also.

GrayTheWolf said:
I have it also.
Click to expand...
Click to collapse
At least I'm not going crazy. I managed to catch the command and it's trying to chmod 666 a modem file. I'm going to turn on full logging in su to see exactly what file.

isdnmatt said:
At least I'm not going crazy. I managed to catch the command and it's trying to chmod 666 a modem file. I'm going to turn on full logging in su to see exactly what file.
Click to expand...
Click to collapse
If the stock phone app is being granted root, might there be a possible root exploit somewhere depending on the command?

firepacket said:
If the stock phone app is being granted root, might there be a possible root exploit somewhere depending on the command?
Click to expand...
Click to collapse
I doubt it. I would be more interested to see if it's checking for root to change or disable something.
It only does it about once every other day though.

isdnmatt said:
I doubt it. I would be more interested to see if it's checking for root to change or disable something.
It only does it about once every other day though.
Click to expand...
Click to collapse
It happens to me too. Running BoneStock 1a. I have it set to deny and not prompt me and haven't noticed any difference whatsoever.
The phone app asking for root randomly seems like a dirty hack someone made and those tend to be sloppy. What if you could symlink the chmod target, or adjust the path variable to have it execute something else?
I am now pretty interested to see the command it's trying to run, lets turn on logging and see if it happens.

I have gotten it a few times, not since v1.0f but nothing I changed would make it stop, not sure what the hell it wants permission for and wy it's asking for it, but I also denied it.

I've also been getting it several times in the last few days.

I get it on my stock rom just after unlocking bootloader and installing supersu on launch day. Like others I just denied it. Haven't seen any side effects yet since then.
Sent from my HTC6500LVW using xda app-developers app

Zynesterysdan said:
I get it on my stock rom just after unlocking bootloader and installing supersu on launch day. Like others I just denied it. Haven't seen any side effects yet since then.
Sent from my HTC6500LVW using xda app-developers app
Click to expand...
Click to collapse
HTC Service Accessory or something similar to that requests root every few days on mine. Is that what you guys are asking about? Haven't had the phone app request access yet.

karn101 said:
HTC Service Accessory or something similar to that requests root every few days on mine. Is that what you guys are asking about? Haven't had the phone app request access yet.
Click to expand...
Click to collapse
No... the Phone app. I haven't had any other system app request root access on any of my devices, it completely undermines the security platform.
If the Phone app is being granted root on a stock phone, that means that app is whitelisted for root access somehow. And wasn't there a recent Android vulnerability that allows you to alter the code of a signed APK without affecting the signature?
---------- Post added at 04:15 AM ---------- Previous post was at 03:54 AM ----------
This is the command it is trying to run: chmod 666 /sys/devices/platform/mdm2_modem/msr_info
The mdm2_modem is public rx only, but would it be possible to change the app's PATH variable maybe and have it execute a different chmod since I can't tell if it is using the full file path to execute it.

Well my little newb investigation turned up nothing.
The Phone app is run as user "radio" uid 1001 which, unlike root, does have a PATH set to outside /system. Write access to /data/local/ would almost certainly give root but I'm sure that's probably known already.
Android bug 8219321 would have given root to original versions of The One running 4.1, but the Verizon version runs 4.2.2.
Oh well, obviously couldn't have been that easy.

firepacket said:
No... the Phone app. I haven't had any other system app request root access on any of my devices, it completely undermines the security platform.
If the Phone app is being granted root on a stock phone, that means that app is whitelisted for root access somehow. And wasn't there a recent Android vulnerability that allows you to alter the code of a signed APK without affecting the signature?
---------- Post added at 04:15 AM ---------- Previous post was at 03:54 AM ----------
This is the command it is trying to run: chmod 666 /sys/devices/platform/mdm2_modem/msr_info
The mdm2_modem is public rx only, but would it be possible to change the app's PATH variable maybe and have it execute a different chmod since I can't tell if it is using the full file path to execute it.
Click to expand...
Click to collapse
Wouldn't chmod 666 make it writeable? That would be a sneaky trick is they put that request in there to check for root and change something. I feel like root = free tethering to Verizon lol.
I would think that there is a root exploit available for the one, but there is no point in using it right now because system is protected and the phone resets whenever you try to change system.

isdnmatt said:
Wouldn't chmod 666 make it writeable? That would be a sneaky trick is they put that request in there to check for root and change something. I feel like root = free tethering to Verizon lol.
I would think that there is a root exploit available for the one, but there is no point in using it right now because system is protected and the phone resets whenever you try to change system.
Click to expand...
Click to collapse
Yeah it makes it world writable which could be relevant depending on how that file is used by other processes. I'm sure there are others who have been at this longer so I won't waste my time looking for a unicorn.
And I think people would still like root even if they lose it on restart.

I'm getting this issue on a stock Rogers HTC One with root. Has anybody been able to gather the SU logs?

going into recovery and fixing permissions worked for me.

wiredout46 said:
going into recovery and fixing permissions worked for me.
Click to expand...
Click to collapse
are you sure? I get it only every few days so hard to nail down a fix.

firepacket said:
[/COLOR]This is the command it is trying to run: chmod 666 /sys/devices/platform/mdm2_modem/msr_info
The mdm2_modem is public rx only, but would it be possible to change the app's PATH variable maybe and have it execute a different chmod since I can't tell if it is using the full file path to execute it.
Click to expand...
Click to collapse
As was posted, it's trying to make a modem file writable. Fixing permissions might make sense. It also probably means that this is no big deal.

need help from someone who is rumrunner s off

i would like a dump of mmcblk0p6 from someone who has NOT been s offed by sonic's java card.
you can be rum runner s offed,or just plain old unlocked. the important factor is to have not ever sent the phone to sonic,as im looking for info being changed by the diag file
in the booted os,plug in,open a cmd window:
adb shell
su (if needed)
dd if=/dev/block/mmcblk0p6 of=/sdcard/mmcblk0p6
exit (exit again if needed)
adb pull /sdcard/mmcblk0p6
youll find a file named mmcblk0p6 in your adb folder. please upload somewhere and pm me a link. dont publicly post the link,as p6 may have some personal info. if the adb pull command doesnt work,just look in your phones internal storage,the file should be in there with all the other folders.
dont worry,this is harmless- just dumping a partition,not making any changes.
if youre feeling froggy,repeat the process for blocks 3-5 and upload those as well

I guess the only question I would have before I upload is, is there any personal info in any of these blocks?

davehasninjas said:
I guess the only question I would have before I upload is, is there any personal info in any of these blocks?
Click to expand...
Click to collapse
yes. thats why i said do not pulicly post the link. i will not look at or retain your esn,meid,etc. but if youre leery of me seeing it,np,im sure someone else can do the dump.

Gotcha, didn't see that part. I'll pm you the link when it's done uploading, also, don't know if it matters if I'm rommed and recoveried or not, but I'll send you what I have.
---------- Post added at 05:49 AM ---------- Previous post was at 05:19 AM ----------
scotty1223 said:
yes. thats why i said do not pulicly post the link. i will not look at or retain your esn,meid,etc. but if youre leery of me seeing it,np,im sure someone else can do the dump.
Click to expand...
Click to collapse
Did you get the pm?

Yes I got it, thank you. I will have a look at them as soon as I get home this evening! Thanks again
Sent from my HTC One VX using Tapatalk

scotty1223 said:
Yes I got it, thank you. I will have a look at them as soon as I get home this evening! Thanks again
Sent from my HTC One VX using Tapatalk
Click to expand...
Click to collapse
No problem, the message wasn't showing in my outbox, so I wanted to make sure you got it.
Good luck in finding what you need.

Successful Root - Samsung Galaxy Note 4, Just one drawback...

Hello all,
I was testing and fooling around with my Note 4 SM-910A when I tried rooting my phone again. (Manually) and I did something different giving me root and the bootloader now shows the Custom (unlocked) symbol. Meaning, that I got root and my bootloader was unlocked. Here is some proof:
imgur (DOT) com/2qjJmWs
But there is one catch to it.
You get bricked. AT&T sees that you are rooted and you cannot use your phone unless you restore it to stock or you take it to AT&T store and they will do it for you.
Also you get a : SECURE = FAIL on your scree.
When I got this root, I made an account quickly and then I posted. This is the biggest day for me. I'm gonna try and see if I can bypass the SECURE = FAIL and make it into SECURE = I DON'T EVEN CARE!
--Sarmad Wahab
--Android Rootivist

Hahahahahahahaa
Sent from my SM-N910T using Tapatalk

No kidding
getyroks said:
Hahahahahahahaa
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Dude, no kidding this just happened to me like 10 minutes ago. I'll be going to AT&T store, like the phone said. I will see what they do.

If you look into the root progress forum, a couple of us has had the same thing happen. I am hoping that some devs are looking into this. I know how to do this every time now and have to unbrick my phone every time.
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app

http://forum.xda-developers.com/showthread.php?p=65784783
Look into this here.
I have done this more than 10 times trying various root procedures to stick on reboot. I'm sure there are A LOT of other that have had this happen also. It's not new.

What a troll. New user sign up, 1st post said ROOTED. LOL

getyroks said:
Hahahahahahahaa
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
sweetboy02125 said:
What a troll. New user sign up, 1st post said ROOTED. LOL
Click to expand...
Click to collapse
Bro, not a troll. My note 4 is now permanently bricked. The os was deleted by the bootloader. I took it to Att and they say that it is permanently bricked. Hard-bricked. Gonna send it to samsung or go to another att store to see wut happenes.

No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...

Walt
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?

getyroks said:
No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...
Click to expand...
Click to collapse
cboysfan said:
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?
Click to expand...
Click to collapse
use the link @getyroks posted, it unbricked my phone!

---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
[/COLOR]
cboysfan said:
I had the same thing happen to me. King root app popped & asked me to try again so I did. (Stupid me) I tried everything I know how to fix this.. In recovery mode I told phone to wipe data factory reset. Still pops up after reboot stating kernal is not seaddroid enforcing then says secure fail kernel and had large yellow triangle saying system software not authorized by at&t has been found etc. Turn off and take to at&t store.
Anyone know how to fix this or have I ruined the phone?
Click to expand...
Click to collapse
Please read the whole thread instead of asking to be spoon-fed, don't be lazy. READ, SEARCH,and RESEARCH!!!
Sent from my SM-N910T using Tapatalk

getyroks said:
No. No. No. Nonononono
I hope you didn't send it in yet.
Go here-> http://forum.xda-developers.com/showthread.php?p=63431559
Download needed files and don't forget about Odin program.
As I stated earlier, I have done this over 10 times trying various root methods to stick. If you weren't so noobish in thinking AT&T was going to help you...maybe you could read around on these awesome forums and figure it out for yourself... but alas, you can lead a horse to water, blah blah blah...
Click to expand...
Click to collapse
Dude thank you soo much, I got my phone fixed, and also I got my note 3 fixed using files from the same person

getyroks said:
---------- Post added at 03:11 PM ---------- Previous post was at 03:08 PM ----------
[/COLOR]
Please read the whole thread instead of asking to be spoon-fed, don't be lazy. READ, SEARCH,and RESEARCH!!!
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
Wow. Don't be lazy. Not cool dude. I did read the whole post and I am trying what was listed. Anyway I wanted to add that my phone has never been rooted. I have tried Kingroot many times with no success. I am running Lollipop 5.1.1 which is locked by AT&T so I am curious if bootloader is locked how this happened or how I will be able to fix this. I will continue to read as I have been doing prior to being called lazy. I have yet to see anyone else state they were running the same OS I am.

cboysfan said:
Wow. Don't be lazy. Not cool dude. I did read the whole post and I am trying what was listed. Anyway I wanted to add that my phone has never been rooted. I have tried Kingroot many times with no success. [bold]I am running Lollipop 5.1.1 which is locked by AT&T so I am curious if bootloader is locked how this happened [\bold]or how I will be able to fix this. I will continue to read as I have been doing prior to being called lazy. I have yet to see anyone else state they were running the same OS I am.
Click to expand...
Click to collapse
The files mentioned in my previous post are the 5.1.1 OS files. I have used them multiple times to recover from a soft-brick. So, YES, I have the same OS Lollipop as you should have. AT&T has locked the bootloader on the Note 4 from the beginning. But in 4.4.4 you could temp-root in order to get rid of some files. But results are so different from phone to phone that a temp-root scenario is complicated to explain. Some work some dont. KINGROOT is also in the same boat, might or not work. You might be able to keep your phone from rebooting or it might freeze and you HAVE to pull the battery. When the battery gets pulled and reboots SOMETIMES you can reboot to a temp-rooted phone, MOST OF THE TIME it soft bricks. All of this information is in either of the posts I linked earlier, so either you're lazy, or you don't understand what you're reading. If you don't understand, then please READ, SEARCH, and RESEARCH.
Sent from my SM-N910T using Tapatalk
Start at the beginning of this here->----->>>http://forum.xda-developers.com/showthread.php?t=2961974

Thank you getyroks.
I was concerned to load the files because I did not see anyone who was not rooted and running my OS. I installed them and all is well. Thank you again.
getyroks said:
The files mentioned in my previous post are the 5.1.1 OS files. I have used them multiple times to recover from a soft-brick. So, YES, I have the same OS Lollipop as you should have. AT&T has locked the bootloader on the Note 4 from the beginning. But in 4.4.4 you could temp-root in order to get rid of some files. But results are so different from phone to phone that a temp-root scenario is complicated to explain. Some work some dont. KINGROOT is also in the same boat, might or not work. You might be able to keep your phone from rebooting or it might freeze and you HAVE to pull the battery. When the battery gets pulled and reboots SOMETIMES you can reboot to a temp-rooted phone, MOST OF THE TIME it soft bricks. All of this information is in either of the posts I linked earlier, so either you're lazy, or you don't understand what you're reading. If you don't understand, then please READ, SEARCH, and RESEARCH.
Sent from my SM-N910T using Tapatalk
Start at the beginning of this here->----->>>http://forum.xda-developers.com/showthread.php?t=2961974
Click to expand...
Click to collapse

cboysfan said:
Thank you getyroks.
I was concerned to load the files because I did not see anyone who was not rooted and running my OS. I installed them and all is well. Thank you again.
Click to expand...
Click to collapse
The sad part is that it cleans the whole system. So starting from scratch everytime is a drag.
Sent from my SM-N910T using Tapatalk

ejectedmatrix said:
use the link @getyroks posted, it unbricked my phone!
Click to expand...
Click to collapse
It helped me as well. Just download the package and use ODIN and you are back in buisness. Btw, all your personal data is gone bye bye though, I will be like a having a brand new phone again.
Take care.
Sent from my SAMSUNG-SM-T537A using XDA Free mobile app

ejectedmatrix said:
Bro, not a troll. My note 4 is now permanently bricked. The os was deleted by the bootloader. I took it to Att and they say that it is permanently bricked. Hard-bricked. Gonna send it to samsung or go to another att store to see wut happenes.
Click to expand...
Click to collapse
1) Not a troll. Just someone not knowing what they're doing.
2) ATT reps don't even know the difference between a locked sim and locked bootloader, so they wouldn't know the difference between a hard and soft brick.
3) All you had to do was use Odin to fix the phone. You just traded your phone for a factory refurbished one. Good job!
4) Read the latest forum posts before doing things.
Sent from my SAMSUNG-SM-N910A using Tapatalk

Hey guys. Thought I'd chime in with a little insight here. Had someone call me the other day that tried to root one, and ended up with the same unauthorized software error. Couldn't get to download mode, couldn't get to recovery, couldn't get phone to boot. He took it to AT&T, where they of course told him the phone was "hard bricked". I just used a usb jig and restored it with odin. Did just fine.
This is the jig I used. It was $4.92 on eBay
http://www.ebay.com/itm/NEW-Samsung...SB-jig-EXCLUSIVELY-US-MADE-SOLD-/141351359584

strabo231 said:
Hey guys. Thought I'd chime in with a little insight here. Had someone call me the other day that tried to root one, and ended up with the same unauthorized software error. Couldn't get to download mode, couldn't get to recovery, couldn't get phone to boot. He took it to AT&T, where they of course told him the phone was "hard bricked". I just used a usb jig and restored it with odin. Did just fine.
This is the jig I used. It was $4.92 on eBay
You wasted $4.92 on ebay, All you got to do is download USB Driver for your phone and install it on your computer. Once this is done, your computer we recognize your soft bricked phone and you can use Odin to reload the firmware.
Click to expand...
Click to collapse