Phone stuck in bootloop - T-Mobile Samsung Galaxy S6

I have the model SM-G920T S6, I was attempting to root my phone and must of used the wrong file and now its stuck in bootloop with "Recovery Is Not Seandroid Enforcing" in red in the upper left corner. I've attempted to put it into recovery mode to flash my ROM...which it wouldn't allow me. I'm not quite sure how to fix this issue, I've been trying some videos I've seen on YouTube with no results. Does anyone know the way to fix this?

Use ODIN "Attached below" Flash the Stock ROM: https://www.androidfilehost.com/?fid=24269982086998283
That will get it back to Stock.. Just select AP
Then use odin to flash recovery..
Edit any recovery other than Stock will give you "Recovery Is Not Seandroid Enforcing", anyone with a custom recovery will have the same notification.. If you need further assistance, feel free to PM me..
Also, you asked a very easy question that you could of done on your own time, we all learned the same way..
XDA is not a place where simple questions get answered trust me on that one..

I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.

Tcrazz said:
I managed to get it to work last night after a bit of messing around on Odin. Thank you for the help though, I am new to the whole rooting phones, flashing the ROM, etc. Gradually learning but there are a many of things I don't know how to proficiently do.
Click to expand...
Click to collapse
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..
It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..
I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..
Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..

Zaphodspeaks said:
Flashing is a very dangerous thing to the uninitiated, before attempting to do something that can make your 700 dollar device into a worthless brick..
It is good to read as much as you can, don't rush the process or you will end up here asking a question that no one will answer..
I know because everytime I ask a question that to me appears to be legit, it ends up being ignored..
Now not everyone will ignore, but a good 98 percent will.. XDA is not a Support site, its a development directed at development..
Click to expand...
Click to collapse
Are there any sites that you might suggest that would help me learn a bit more. At the moment I have just been trying to root my phone before attempting anything else.

Related

Help Me Please

I feel I've made a terrible (and stupid) mistake. I decided to unroot my phone from cyanogen roms. I read a how to guide that I guess was outdated because now I have android 1.0 firmware. The guidw was [how to] unroot by tubaking182 (absolutely zero offense to him, not his fault, I'm stupid, etc etc.) So I now have stock version 1.0. There's no check for system updates under about phone in settings so I can't do that. There are file manager apps that I could use to rename the necessary updates into update.zip, but there's no apps available like download crutch so I can download them. I also can't enter recovery. It gives me a triangle with an exclamation inside next to a image of a phone and that's it and I have no idea how to install an update without recovery mode. As I'm sure you've noticed by now, I'm the epitome of newb and feel free to laugh at my failure. I just really need someone to help me and would be eternally grateful. In all likelihood, I'll need step by step instructions on what to do. I know this is a lot to ask and I've really done nothing to earn this help... I really just need assistance. Thank you to anyone who helps me in advance
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
ItsAndroidsWorld had many videos on You Tube. Look for ones on how to root, then how to install the death spl, then look for the ones with Super D or FastTest .. as it seems as though they are probably the best roms for everyday use at this point.
I've found that using these videos via You Tube is the easiest way to go.
Good Luck.
^^^ ABOVE POST stolen from another similar thread.
psyko-m1 said:
Not to be an asshole and say "Shoulda Coulda Woulda" but you really should have done your research before embarking on bricking your phone.
Click to expand...
Click to collapse
he didn't brick his phone, don't scare him
To OP: The same happened to me when I was a n00b at this ****.
Dude, google is your friend.
Calm down.
tsk tsk tsk.....Im gonig to say this....WRONG SECTION
but I will be nice as well. just find the updates on google from 1.0 to 1.5 and oh yeah to get back into recovery from the triangle withthe !...alt L...but if you somehow brick ya phone youe fault not mine next time do ya research before you mess with ya phone
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
psyko-m1 said:
Technically speaking he is in a DEFCON 2 "Brick" situation.
Sorry.
Click to expand...
Click to collapse
Well he's in the wet cement
SeEsAw12 said:
Well he's in the wet cement
Click to expand...
Click to collapse
Or...
You are late for work and have a flat...
click on this http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/:cool:
remove the cool http://theunlockr.com/category/howto/android_how_tos/htc-mytouch-3g-magic/
this website should help you get back on track and you just need to download the nbh file to get it back to cupcake
BUT 0MGAWWZZZ N00BZORZ DO3S 1.0 HAVE A DA SENSE RAOM???
in all seriousness, there's nothing actually wrong with your phone. You completely unrooted it. By following the aforementioned instructions, it'll be easy to reroot and update. What I DO find weird is why you're not getting 1.5 OTA...
although i hate when people post in the wrong section - im in a good mood this morning
http://zenthought.org/content/project/flashrec
not sure if it works in 1.0 - it should as it uses a rather old bug to do so
Easy as pie...just follow the guide in my sig.
=)
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
afiellerddr said:
To those who say I bricked it, I know that's not the case it still works so I obviously didn't brick it... not that fail thankfully.
To thenameismax, AHA! I did not know about alt+l retrieving text so thank you thank you thank you. I just need to get the necessary updates and copy them to sd card root, rename update.zip/install one at a time... I think lol
Thanks again to all who helped and sorry about the wrong section. When I was rooting, it was in development. I assumed that unrooting would be too and therefore problems with that... further fail.
Click to expand...
Click to collapse
yeah man no problem. good luck.
Don't do anything. In a day or two you get an OTA update.
You can force the update like people have mentioned, but as long as you can hold off for a day or two you dont need to.
BTW, at some point you will see the E or 3G icon downloading like crazy and you dont know why. It is downloading the update. Stay away from task killers and in my experience it is good to be around wifi.
Just relax.
Sent Move Request

News flash***rom manager***

It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
I couldn't agree more.
never used it thank goodness.........
Never happened to me
EDIT: Sorry for my rudeness, anyways, people should know that it's not the greatest idea to use rom manager with cm5/cm6. It has already been established that it may be a bad idea to use the program with the following roms. Sorry I get really cranky in the mornings, not the best idea to come onto the forum with some old news :|
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
I have never used it and I agree with him just from all the posts I have seen related too it messing up people's recovery images. Does that make me stupid?
I've used it for a few weeks now with no problems on my MyTouch on 1.6, 2.1, and 2.2 ROMs. Not saying others aren't having legitimate issues, but people in general are much more likely to post negative reports than positive ones.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
protomanez said:
Never happened to me, you're obviously too stupid to use it.
Click to expand...
Click to collapse
Please lead us retartds through your install procedure, current rom, set-up so we can be as learndededed as you. I have had cm5&6 with ra installed upon initial set up. No swap/ noext1234, stock mt3g spl 2.22.23.02 radio. Nothing special. I even did it with the donut mytouch rom w/root.I only use basic apps, nothing that would interfere with recovery. to me it seems that when u flash a cpl different roms a day is when it hangs up. I can usually get the phone to boot back up, which gives me a chance to get back into rom manager and flash ra recovery back to the phone. the last cpl times I had to wipe cache before it would actually flash RA recovery. so basically if u can get the phone to boot past the splash screen go to rom manager and flash the **** out of ra recovery until it works. First we found out that clockwork didnt like flashing zip's and backups on low batteries 30% and lower. then the always fun recoverly log issue(cant recall the exact error right now) and of course the cant get to recovery issue. I know it's not a widesporead problem but it is a problem that renders phones useless until u can find someone nice enough to help u and not treat u like a retard. Not everyone knows as much about phones as you guys do....congratulations you know all there is about phones. go learn some ****ing human decency, if u have nothing helpful to say then shut up.
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
hmmmmm. Maybe since its flashing clockwork from inside rom manager is what might be killing it for some of us. tonight I will try just flashing clockwork outside of rom manager and see how that goes. i like clockwork's set up and it is easy to use, just kinda freaks me out when my recovery goes bad.
arefin said:
have been using it without Rom manager and highly disagree with the poster.doing it 'wrong' or without knowing 'how to' can certainly cause problems but that should not be described as the problem of the product. lot of people can not use nuclear power correctly (look at the USA) and now we call describe nuclear power as menace which is lame :/
Sent from my T-Mobile G1 using XDA App
Click to expand...
Click to collapse
but at the same time thats why it is a part of rom manager. one click recovery flasher. to make it "easy". i highly doubt you can go into rom manager and incorrectly flash clockwork recovery. its a one click thing
it's also spoken out at many threads at xda that flashing the recovery from within the OS causes issues, so trying to install the recovery from PC or even RA1.7 should be a better option.
I'm considering that you already know the commands for that. better luck! remember, clock work will allow you to flash anything without signing - meaning? you can edit any update.zip to your liking and then forget about all the trouble of signing it before flashing. a simple toggle should do the trick while you are in recovery mode happy flashing.
Sent from my T-Mobile G1 using XDA App
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
crypysmoker said:
It is either a case of your phone, sd card setup/left over files etc..
I use rom manager on every phone I root with no problems since its release. 6 G1's, 3 Fender LE's, 7 Mytouch 1.2 and 4 Evos. Sometimes, it takes couple seconds to show up or go into recovery, but that doesnt mean its gone. Recovery cant just dissapear without something either trying to over write it or it being erased.
Click to expand...
Click to collapse
Im gonna give it one more try. I dont think I have ever.....
flashed clockwork from rom manager
reboot into recovery from rom manager right then (read some where that on some roms when u reboot to recovery using the regular way it might mess up....not sure about this one).
wipe everything (clockwork wipes more that amon ra)
reflash any rom
in my case... above steps then in this order
flash fireats custom mtd part 1.1
super E
Gapps
overclock update
fireats custom mtd part 1.2
anyone see a issue with what I have done so far??
Ok I will post back when clockwork fails again.....and if not f-in sweet
chrisgto4 said:
It does not like our phones. Has great options but.......it sucks. Everytime I flash it on my phone my recovery goes bad in a cpl days. Never had this problem with RA. Do a search rom manager pops up all over the place with bad recoveries. Stop using it ppl. Im sure ill get flamed for this but oh well. Kinda tired of reading of noobs that fall victim to a .apk that seems very easy to use until it craps out and then your stuck at the airport with a bad recovery and ADB no where in sight. Or even if u had ADB you still have no clue how to fix it!!!!!!!!!!!
http://forum.xda-developers.com/showthread.php?t=742007
http://forum.xda-developers.com/showthread.php?t=762325
http://forum.xda-developers.com/showthread.php?p=7443928&highlight=revovery#post7443928
Click to expand...
Click to collapse
chrisgto4 said:
hahahahaha good one. Not to stupid to use it. the ui is very simple and easy to use. Flash clockwork or flash alternate. What im to stupid to do is figure out how to fix it after it kills recovery. but thank you for your input, I'm sure it will help someone out.
Click to expand...
Click to collapse
You found your answer within the first example link that you provided, look at post #3:
http://forum.xda-developers.com/showthread.php?t=742007
rom manager is not for idiots like yourself. rom manager is a great tool for many different phones. sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it. an advanced user (who its made for) can still flash recovery via fastboot, and have all the helpfulness and easy ui of rom manager and easy access to cm nightlies.
dont knock a dev who works on many different phones, and dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
tehseano said:
sometimes it doesnt flash a recovery correctly maybe it be poor service to download the recovery, or low memory when flashing it.
dont rely on noob application reports and bad reviews. anyone who finds rom manager crap is just a poor android user.
Click to expand...
Click to collapse
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
I agree it is an 'easy' shortcut that is not the best decision.. Like for example I think it killed my phone. I repaired permissions via rom manager, rebooted as it told me to and now my g1 wont boot past the g1 logo. I could install from a backup but the backup is 1+ month old (my error oops!). I am hoping to find a solution... Really dont wanna wipe everything..
warsng said:
i didn't want to get into this pointless discussion, but you have made a ****ty argument for rom mgr, you have confirmed that it doesn't work properly in certain circumstances, which is a good enough reason to not bother with it.
also, why shouldn't we rely on bad reviews? that's the point of a review, to give some idea about what experience to expect.
(i have never used it myself, amon ra recovery is enough for me.)
Click to expand...
Click to collapse
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
tehseano said:
I made a perfectly good argument. Yes it can "mess up", but thats not at the fault of the app. It's at the fault of the phone. There are things that can go wrong that Koush cannot control. It is for ADVANCED users as a quick helpful UI for recovery-based operations. People that don't know what they're doing, or only half-way do shouldn't be using it. However, too many Android users *think* they are advanced enough, yet 5 minutes after using it, post a "PLEASE HELP, PHONE IS BROKEN", because they DON'T know what they're doing.
I'm not saying that all bad reviews are missguied, but I can assure that 90% of them are from noobs that have no idea what they're doing. They rooted their phone because someone told them it was cool, and they have absolutetly no idea whats in their hands and what they can do with it. Let alone, how to properly work it and fix problems. It's easy as pie to point out noobs from those crowds of users, those 3 links in the OP's post are all perfectly examples. People who came to XDA, signed up, never posted anything, then messed up and came crying to the board asking for help (usually in Android Development because people like them, and the OP too, don't how to to post in the correct section).
So for the last time, if you don't know what you're doing on your phone, don't do it. Just because you have root, and an app says "for root users", doesn't mean its for you, which EVERYONE assumes it is. It's piss-poor users like that, that ruin app reviews and the name of Android everywhere.
Click to expand...
Click to collapse
Get a clue , its a program any gimp, including you, can install from the market, it is made in such way ...the fact that it dosent fail to write the recovery in fastboot mode means nothing!
This program shouldnt let the G1 user flesh any rec image. Till that happens it is the DEV's fault. Shouldnt be in the G1 CM's either.

LG Phoenix Boot Errors

Hey all, Let me start by apologizing for not posting this in the right place (More than likely). i didnt see any threads for LG p505 Phoenix.
On to buisness, i had an error booting into ClockWorkMod Recovery. My phone is booting incorrectly ever since. ive tried to take the battery out and replace it, but that didnt work. I tried to follow some repair work listed on the forums, but i need further assistance. ive gotten as far as the SDK dev package and attempting to restart the bootloader, but no luck. it keeps saying it cant detect the device. the computer recognizes it as ASUS Android Bootloader Interface. Any help?
Where did you learn how to put CWM on you phone? If it wasn't here, why not try those forums where you did?
Try this
http://forums.androidcentral.com/t-lg-phoenix-thrive/
Well, i got CWM on my phone via the Rom Manager App on the Market. but, after toying around with my phone trying to fix it, it appears that it is stuck on the bootloader, and not CWM. when it DOES "boot up", it only displays lines of code that varies when i plug it into a power source or my PC.
Are you rooted?
yeah i am. couldnt have gotten this far without that step.
FawkesPhone said:
yeah i am. couldnt have gotten this far without that step.
Click to expand...
Click to collapse
Just didn't want you thinking you could flash cwm by installing rom manager.
What exactly is going on. Give lots of details.
* iTouched Epic
Well, good for you. im such a rookie that would be entirely possible. lol. anywho, i asked for help on another forum, who a couple people on have some experience with programing and such, and i pretty much explained everything there is to explain there.
however, the website wont let me post a link to said post, so im going to try to copy/paste because i REALLY dont feel like typing all that out again if i dont have to.
Copy link and put (dot) as the dot .
* iTouched Epic
the story is, i tried to boot my phone (LG phoenix [p505], running CarloROM, standard Kernnel) into ClockWorkMod Recovery Mode, but upon booting up, teh device went to a black screen, save for a couple words, most partial. the readable text says "UDC_Start()". on pluging it into the PC, it displays the following text:
-- suspend --
-- reset --
EP1/out FAIL nfo=40 pg0=74000
-- portchange --
usb_read() transaction failed
-- reset --
-- portchange --
fastboot: oops !
fastboot: Processing commands
i am trying to utilize the only fix ive found, which is to reboot the bootloader via andriod developer debug window. i tell the command prompt to run the "adb reboot bootloader" function but it says it cant find the device.
it also appears on the PC as "ASUS android bootloader interface"
Click to expand...
Click to collapse
here's all the details ive got thus far
Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic
boborone said:
Try flashing stock recovery on it. Flash back to complete stock. Did you check to make sure cwm was compatible with your device?
Was the other forum not helpful to you?
* iTouched Epic
Click to expand...
Click to collapse
First, not the other forum isnt helping as it's a small user group and no one's responded yet. second, as previously stated, after posting this thread, ive determined that the phone did NOT boot to CWM. and second, yes, CWM is compatable and has worked in the past. i heard about it from someone that has used it on his p505 and it works perfectly.
There are a lot of devices that only run a modded version of cwm. I have a Samsung intercept that won't run with standard cwm.
* iTouched Epic
people on the android central forum you posted a link to say the phoenix runs just fine with standard CWM
Did you try flashing the touch version of cwm? My epic touch sgsll bricks with that?
* iTouched Epic
i rooted my phone, downloaded ROM Manager, gave it Super user permissions, and flashed Optimus One (Old BaseBand). exactly as instructed.
Where did you learn about doing this? You said you tried asking on another forum. What did they say? Did you try what they said? Have you tried what I said about going stock?
* iTouched Epic
i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.
FawkesPhone said:
i learned all this from here: http://forums.androidcentral.com/t-lg-phoenix-thrive/138186-how-clock-workrecovery-mod-cwm.html
no one has responded on the other forum as previously stated
i have learned that my device is booting to the bootloader, not CWM, also as previously stated.
thus, flashing a new ROM of any sort is impossible.
Click to expand...
Click to collapse
You never said you didn't get any responses from the other forum. If you posted the question yesterday and gave it a couple hours, no responses, then started flipping out cause your is phone is messed up and so you decided to join for the soul reason of using it as a technical support and post in off topic cause this site doesn't even develop (notice I didn't say support) your phone, I say you need to chill out and go back to other site and get a lil bit more in depth with your question. Cause honestly I would have overlooked your question with how it was written and the little information given. Those guys know about your bootloader. I don't. Not many here do. LG doesn't make flagship devices, hence why they're not here.
I can tell you that if nobody does help you, you need to read up on how to shell into the phone and flash something else like that.
* iTouched Epic
FawkesPhone said:
First, no, the other forum isnt helping as it's a small user group and no one's responded yet.
Click to expand...
Click to collapse
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?
FawkesPhone said:
Also, why waste an hour of my time? If you're gonna tell me to eff off, why not do it at the beginning?
Click to expand...
Click to collapse
I didn't tell you to f off, but, in all seriousness, I don't like it when people join this site just to ask a question.
Then you post in the wrong forum about a phone that isn't even developed on here.
Sub-Forums : General discussion
Forum
Last PostStats
About xda-developers.com
Anything to do more with the site than with the phones. Feature requests, announcements, praise, moaning, etc.
General
Anything that involves all of the phones and doesn't fit in any of the other fora.
Paid Software Announcement and Discussion
Are you a developer wanting to promote for-pay software? Feel free to post announcements about your apps here and have the community discuss them.
Questions and Answers
This forum is for all questions, big or small, you might have. Please read the rules in this forum before asking.
Hardware Hacking
For discussion of development boards, hardware interfaces, datasheets, circuit modification and related tools
NFC Hacking
For discussion of Near Field Communication (NFC) hacking and development
Upgrading, Modifying and Unlocking
Some of the more advanced issues, involving multiple phones.
Accessories
For accessories that involves multiple phone-types. Car-kits, headphones, cables, chargers, extra batteries, replacement screens, sources for connectors, etc.
Networking
GPRS or WAP-settings, WiFi, ... This forum is for anything to do with getting your device talking to the rest of the world.
XDA TV
Here's your chance to communicate directly with the stars of XDA TV!
Off-topic
Anything not related to the phones.
^ Just wanted to point that out. ^
And I did try to help you. I don't know LG bootloaders. But I went through seeing if you made some noob mistake that I could help with. Then when that was sorted out, I told you how to help yourself. If you're are going to take someone telling you how to help yourself as telling you to f off, not sure you are going to make it here on XDA. Good luck with that attitude.
---------- Post added at 10:20 AM ---------- Previous post was at 10:16 AM ----------
Did you try to search here on this site?
Searched here on XDA and found this:
http://forum.xda-developers.com/showthread.php?t=1289265&page=3
You see, we don't mind helping people at all, it's the people that won't help themselves that get on people's nerves. Look man, I will help you as much as I can. But you have to be willing to help yourself, too. Finding threads like the one I posted above is what I mean by searching and reading on how to shell into the phone, using adb to fix your problems. You have a jacked up phone, don't get frustrated and mad at the world, calm down, chill out. You can fix it.

Installing GB ROM

Is it common to take about 25 minutes and still not be able to complete the installation of GB Rom using PC Odin..?
I am trying to install KL3_KL1 GB Rom and the PC Odin is stuck at Factory fs for 25 mins ...
unplugged the cable, removed the battery and restarted the process .. still the same no matter what I do...
I am at the moment following steps form dr.Ketan's threads.. but the process seems to take a little too long and am unable to get into recovery mode.. Its only download mode and never going past the factoryfs.img situation in PC Odin..
I was on Stock ICS ROM Indian version before i started the process with PC Odin.
My goal is to get into Criskelo ROM for now.
Any help of suggestions to get me out of the situation please..
Have you ever did factory reset or wipe on stock ICS?
this is bad sign, and highly suggestive of super brick emmc bug. if you cnfirm wiping on stock ICS then it must be that only.
sob sob ... may be i did ...
should i just handover my phone to Samsung service center now ??
Yes, just check your flash counter is zero
Sent from my GT-N7000 using xda premium
yep.. That one is set to Zero.. Will Samsung just re-install software or replace device in this case ?
I have a nandroid backup taken 2 days back. Can i use that backup on the new phone to get back all my settings ??I primarily need contacts that i do not want to loose.
I believe it's a Motherboard replacement that you will be given, I doubt there will be anything you can pull from the old phone..
I luckily copied the nandroid backup onto my PC along with the md5 checksum... Would that help me ?
what is the process to restore from Nandroid backup
Recovery --> restore --> show the target ? is that it ?
Coolkriss said:
I luckily copied the nandroid backup onto my PC along with the md5 checksum... Would that help me ?
what is the process to restore from Nandroid backup
Recovery --> restore --> show the target ? is that it ?
Click to expand...
Click to collapse
No, never try it. You wont be able to restore anything. Just send to repair center and have a new mobo replacement if still under warranty.
Then after get your devices back and check again how to do nand restore. ( please read or ask before do any nand restore).
Good luck, mate.
Sent from my GT-N7000 using xda premium
As per above post - just wait until they send the device back repaired -
In the meantime read, read, read on how to go about these things otherwise you risk another brick..
To be honest, I'd just start a fresh when the new phone comes back..
Thanks guys .. Thanks for all the prompt responses. I just hope they dont take long time to get me the repaired or new phone.
I will just let my gmail account do the sync.
CJSlim79 said:
As per above post - just wait until they send the device back repaired -
In the meantime read, read, read on how to go about these things otherwise you risk another brick..
To be honest, I'd just start a fresh when the new phone comes back..
Click to expand...
Click to collapse
You are right, actually i do believe for those who get bricked with their devices must be a experienced flasher. Those of them ( included myself) surely only read how to unroot the new devices but never read other thread such as ...how to ugrade rom...general section...problem.....
But i think after these brickbug dilemma, a lot of xda member like me and you sure will read ...read and read the whole forum before do any rooting and flashing no matter jump to which brand of devices......
Sent from my GT-N7000 using xda premium
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
dr.ketan said:
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
You're right mate, If the instructions are followed then I can't recall a single issue..
I've used your instructions (after extensive reading) and also had a lot of support from azzledazzle (Who was kind enough to walk me through my first downgrade).
I've had Android for a few years now since ditching the iPhone's and on HTC I used to flash anything and everything and just nandroid if anything went wrong. I think the issue here is that there is an issue, a bug with the eMMC, and people don't bother to research their NEW device, they approach with "I've flashed Android before" attitiude and this is where we end up...
It took me a while, and as I say alot of research before i started dabbling with the Note.... And as I am sure AD will confirm, I asked every n00b question under the sun of him about the process.. Yeah, I was a n00b and I am still learning... I asked the questions, nobody laughed and my Note is still purring...
I guess people either don't wanna feel stupid by asking (Old saying: No such thing as a stupid question!) or they are confident they "Know" how to do it because they have done so on other Android devices...
The guys on this forum are a wealth of knowledge and maybe it's just me, But I like to learn...
Hopefully, I maintain my head and don't mess it up in the near future and I am considering testing NoteCore V7 STD... but still not comfortable with the cleaning scripts etc - So i will read more, ask more and learn more... and hopefully continue to use my Note .. more...
dr.ketan said:
Usually new user are lazy to read n search, or searching just single targeted topic and follow it without even reading first few comments of op.
Though i remember coolcris is quite senior n if i remember correctly he had communicate with me many times on time of gb rom. But sadly sometime members not taking advise seriously. Or may be selects short cuts.
Have anyone remember single case faced any issue who updates rom theoritically clean or following instruction to d letter?
I believe if you read instruction fully n follow it word.to word, chances of brick is almost zero.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
I know and this was perfectly my mistake ..
I have flashed a lot of times and i actually remember know about the eMMC bug.. the only thing is that i did not check if i had that bug ..
Situation for me today.. I started the process and got an email that i had to respond immediately from my office..
In this process, I forgot if i did a reboot into recovery after flashing the Abyss Kernal .. that is when i just went ahead with the wipe cache/dalvik and data ...
This was my lazy A$$ to blame ..
but for anyone doing a flashing .. please concentrate on what you are doing and just dont rush ahead ...
and ofcourse read, read & read before you proceed with any steps...
Coolkriss said:
I know and this was perfectly my mistake ..
I have flashed a lot of times and i actually remember know about the eMMC bug.. the only thing is that i did not check if i had that bug ..
Situation for me today.. I started the process and got an email that i had to respond immediately from my office..
In this process, I forgot if i did a reboot into recovery after flashing the Abyss Kernal .. that is when i just went ahead with the wipe cache/dalvik and data ...
This was my lazy A$$ to blame ..
but for anyone doing a flashing .. please concentrate on what you are doing and just dont rush ahead ...
and ofcourse read, read & read before you proceed with any steps...
Click to expand...
Click to collapse
I'm on a wing and a prayer at the mo as before i did any modding i was helping my bro (who lives in another country) and was talking him through it - jumped into Stock recovery and hit wipe cache by mistake...
It can and does happen but I am very diligent now and I've flashed a a good few ROM's and a good few stock recoveries since then so I hope i got away with that stupid mistake...maybe it's the wipe data only that brings forth "The Brick"
Yes..
anyway. I gave my Note to the SSC today .. IT was strange that they said .. DO NOT DO OTA .. you have to come to SSC for any software upgrade.
They initially told me that this is out of warrenty as I did OTA and showed them who the BOSS was .. Instantly they changed the tone and now they say we will do it for now, but the next time bring it to SSC for upgrades ..
They asked me to visit them tomorrow to collect the unit, but i doubt if they can change the Motherboard by tomorrow. Hoping they will..
Will keep you all posted on the status
Thanks a lot for all your guidance guys ...I would not have loved my Note so much if I was not on XDA
Now this has gone bad.. the SSC tells me that the software upgrade is not covered under warranty and is asking me to take back my phone .. They are not ready to repair it ..
Help me here guys ... anyone aware of something that i can scare them with ??
Coolkriss said:
Now this has gone bad.. the SSC tells me that the software upgrade is not covered under warranty and is asking me to take back my phone .. They are not ready to repair it ..
Help me here guys ... anyone aware of something that i can scare them with ??
Click to expand...
Click to collapse
You can advise them of many many instances of this brickbug and provide evidences FROM SAMSUNG confirming that exists and acknowledging that this can be triggered by a simple update / large data move or copy.
This is standard practice for Service Centres, unfortunately they always try to get out of it.. Stand your ground, keep your head and you will be given a repaired / replaced device..
Oh - and answer any questions straightforward - Yes / No, Do not offer information.
Did you root / flash / play around - No
How did this happen - Via KIES
etc
Again - This can be triggered via a standard Factory reset / Wipe from within Settings > Factory Reset on ALL stock ICS kernels...
A little research on these forums will give you enough info...
Good luck
---------- Post added at 02:35 PM ---------- Previous post was at 02:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=1633938
Thanks a lot for the advice.. I am searching if I can find any official Samsung statement anywhere to get this resolved.
I called the head of SCC in my city and spoke to him today. He will check with the center and give me a call tomorrow..
Am just hoping this gets resolved... aaargh ...
Coolkriss said:
Thanks a lot for the advice.. I am searching if I can find any official Samsung statement anywhere to get this resolved.
I called the head of SCC in my city and spoke to him today. He will check with the center and give me a call tomorrow..
Am just hoping this gets resolved... aaargh ...
Click to expand...
Click to collapse
Check the thread I posted..
There's a few Dev's here been in touch with SS over this issue since it was realised and I'm pretty sure you've all you need to basically tell them to replace it, No, Demand it...
Even under the Sale of Goods act - the device should be fit for purpose it is sold for.
Given that even on STOCK Firmware you can brick this device without rooting / modding AT ALL.. indicates this statement is not met. The device has a highly publicised and highly know firmware issue and Samsung were stupid enough to release a software modification (Which they encourage you to download via THEIR software) which enables you, without knowledge to destroy your phone..
It's your fault as you know that it happened (As we know from this forum and more the safe way)
But it is THEIR problem that they have the issue.. Do not take no for an answer, And to be honest - I would have refused to wait for the callback.. I would have advised (As I have previously) that I will hold on the line while they contact whoever they need to because you are eager for resolution of this.
You will get a new/repaired device...

rooted sm-n910t3 Note 4 phone and now have error messages. please help with recovery.

Before coming across the link in this forum here at http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225 ...
I thought I could shortcut all the work by going to the auto root chainfire site to download the actual CF Auto Root File for model sm-n910t3. I successfully flashed that file using odin. It went into a bootloop and then I freaked out.
The error messages when I turn on the phone first show
"kernal is not seandroid enforcing" in red, and
"Set Warranty Bit: kernal" in yellow writing.
After being in this bootloop i went to the link posted above and followed each step by step. My phone is successfully rooted now and I can log in to my phone fine. However, there are two problems. First, those error messages are still there. How do I get rid of that? I tried a factory reset on my phone and it wont do it.
Will get to that after. Second, when I go into twrp by hitting volume up+home+power, once im in there it wont allow me to backup my current rom. It says an error message about E:/ data mount or something like that. And also while in twrp it won't let me factory reset my phone. So the recovery program is pretty useless to me. I don't know why it doesn't work properly.
Where do I go from here? Can someone help me out in fixing this error message and getting a recovery program to work? I'm just wondering why the twrp that I flashed while following that root guide above does not work. Has anyone ever encountered those two error messages while turning on their phone? Thanks.
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
mrfordwrench said:
The error messages are normal after rooting.
Sent from my SM-N920T using Tapatalk
Click to expand...
Click to collapse
So other people have those messages on the top of their phone after rooting this device? Im guessing we just ignore that message then? I thought it was there because I flashed the wrong kernal before doing it the right way and following the forum...
What if I flashed the original firmware for this note 4 phone that I have a copy of, then root the phone going through that tutorial step by step? Wouldn't that get rid of the error messages? And my twrp would work then?
Im not able to make a backup of my current rom. And Im not even able to factory reset this phone. This is a problem for me since I want to put marshmallow on here soon. When I do I get an error message. Part of my second question is wondering why twrp isn't working correctly?
please help
i took my battery out to charge it and put a new one in. now it wont even boot up. it turns on and says
"custom binary blocked by FRP"
"secure fail: kernal"
for those of you who followed my other post i rooted my phone and tripped knox. phone was giving a message but would still turn on. where do i go from here? i have everything backed up and can start fresh. please provide step by step instructions on how i can fix this phone. thank you so much in advance and god bless.
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
scary
areininger30 said:
I went to samsung and downloaded the firmware for this device and then flashed it. Now it's back to normal so you can disregard my post. Thanks guys.
Click to expand...
Click to collapse
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
V3racious said:
#UberNoob Drink your ovaltine. You should probably get an iPhone.
Everything worked as expected you are just so inexperienced you just gave us a play by play of your ignorance and then went running scared from the fear of 2x hello worlds and the unknown right back to momma Samsung. Good post
Click to expand...
Click to collapse
Easy dude, that's not how things are done around here.
Ubernoob?
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
areininger30 said:
Drink my ovaltine? Hash tag for uber noob? Didn't your parents raise you to not say something if you have nothing nice to say at all? Apparently not so who's really the ignorant. Ask yourself that question. Ignorance is bliss. That's a good hashtag huh.
And the bottom line is that we were all beginners at one point right? So cut me some slack im learning. It will take me time to get to where you guys are at. Yes I am brand new to this stuff and no I don't like the iphones. Androids are more user friendly. I like Samsung phones and want to learn more about them.
Its people like you that keep us beginners from wanting to come back to this website, when guys say blatantly rude comments. It shouldn't be a bashing forum. Let's all chill and get along.
Click to expand...
Click to collapse
Good for you. If you need anything further, please don't hesitate to ask. There are a lot of great, talented and humble people on here, who would be glad to help.

Categories

Resources