Related
Not sure where to post a victory message! After scouring the net over my truly new LG Escape P870, actually newly released to the world in mid-September, for rooting information, I somehow landed on Bin4ry's thread here: http://forum.xda-developers.com/showthread.php?t=1886460.
I am extremely happy to say that version 15 did the job! I wanted to post this in his thread, but I'm not allowed to because I'm new.
So for anybody enjoying using this great phone, there's hope. And it's EASY!
Peace, tinkicker.
I tried Bin4ry's as well but it did''t work for me. It kept giving me errors (i tried it like 10 times). I tried both methods (for tabs and the normal) I wanted to post on Bin4ry's and give him the output that I got but I couldnt post on that thread (new user) . Then I found a site, which I am not able to post the link to because xda doesn't let me( new user), but if you google "LG Esteem OneClickRoot" it is the first result that comes up. I tried that one, it also gave me errors and restarted my phone, I thought It didnt work but when I went and looked in the installed apps, for my surprise there was a new app - "superSU". So I opened a terminal typed su and there it was the coveted # sign . Now I need to find how to install a new recovery.
Hey guys, just got this phone today. Tried both of those methods with no luck so I figured why not try the method that worked on the recently ported ICS 4.0.4 for the LG Thrill.
You can find it here:
http://forum.xda-developers.com/showpost.php?p=31963526&postcount=532
The version 1.6 worked for me. The only problem I had was there was an error reading a file, second time through it worked with 0 errors.
Also there is an update to our firmware from P87010c to P87010f not sure what the difference is.
NO JOY!!!
Okay...I'm stupid. Rooted phone...one wrong move with a system file...yep. Brick.
Fortunately I was 1 day shy of my hardware warranty expiration so new phone. But...now Bin4ry's app no longer works for me! It will NOT root this new Escape!
Tomorrow I'll try MikesTooLz's and see what happens.
Look at your system info, did you get the newer software version? The v10f or P87010f is the update, the one on my phone that I rooted with wkparks method is v10c or P87010c.
If it's the updated version can't say for sure but the link I posted above worked on 2 LG phones that I have, may work on yours.
I suspected the software update--it's the F version--might be the culprit but I didn't know what the original was so I couldn't be sure.
So what can I do? Wait on someone to cover the F update? Could I download the older version, root, and then upgrade again?
Did you try the method posted in the link I provided? You may have to run it 2 times to get it to work. Also some have reported better results with version 1.2 of the root script vs 1.6
What exactly is going wrong? Can you give me a screenshot of the cmd prompt? I will do what I can to help, I have the update ready to go but haven't done it because I want to make sure I have root. haha
Downgrading isn't really possible because the only KDZ I can find is the v10f which I posted in a thread here:
http://forum.xda-developers.com/showthread.php?p=33752762
I'm slowly working on this phone so hopefully we can get a custom recovery going and everything no promises though but, I won't be happy till I can put a custom rom on this phone.
Urabewe, it worked!
I could NOT download v1.6. It would appear to download, virus scan would run, and browser would lock up. When I checked my "extract to" folder, the bin and files folders were there, but none of the .bat files had extracted. I was able to correctly download and extract v1.2, so I ran it, and my phone is now rooted. Thank you for the info!
It ran the first time and failed. Ran the second like you said I might have to, and it completed correctly.
I have the update ready to go but haven't done it because I want to make sure I have root. haha
Click to expand...
Click to collapse
Does that mean you were waiting to root your phone to see if I bricked mine? LOL!
Now...everybody talks about "install a new recovery". Can somebody point me to or describe the correct procedure/routine/script that I need to follow in order to set my phone up safely like it should be? What apps do I need to fulfill all the correct steps? Yes, I've messed around with a tablet root for a year, but I'm no developer. As far as the technicalities go, I'm pure NOOB. Windows, I understand. Linux, I'm learning. I don't know how to be safe about this and I can't afford to buy another phone if I screw up (wife is watching me closely).
Urabewe, thanks for the help!
Awesome glad it worked. No wasn't waiting for you to brick, just confirm root was possible, and this is nice to know I may just upgrade later then.
Recovery is not possible right now, bootloader is locked and only thing we can get into is download mode which has nothing to do with custom recoveries. Slowly working on it so anything I find will be posted.
Any info I find will be posted here http://forum.xda-developers.com/showthread.php?p=33752762 so keep an eye out there.
Sent from my LG-P870 using xda premium
has anyone tried any of the one click methods? ive found 3/4 different ones out there.
One Clicks...
I tried two specifically meant for LG phones, and I had no luck with them. I succeeded with Urabewe's posted links though. And yes, as I posted in their thread, v10f IS rootable. Once I figure out how to take screencaps again, or better take live video of the screen, I will get it as more proof. Now to see if ROMs will be possible soon....
I can't rooting my terminal, other method easy?
Enviado desde mi LG-P870 usando Tapatalk 2
General walkthrough posted in the other thread. Hope it helps.
Sent from my LG-P870 using xda premium
I'm having trouble finding firmware v10f I'm guessing there isn't a way to root v10i that v18 file and the 1.2 I newness they reboot it but no root it just says mounted permission denied are you root?
Sent from my LG-P870 using xda app-developers app
Yes, I am rooted with firmware 10f.
Sent from my LG-P870 using xda premium
Can u find the firmware for me? Or help I'm stuck on v10i I want to downgrade....
Sent from my LG-P870 using xda app-developers app
tman1992 said:
Can u find the firmware for me? Or help I'm stuck on v10i I want to downgrade....
Sent from my LG-P870 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1976116
This is the version v10f
Sent from my LG-P870 using xda app-developers app
Man are you talking bout the link on page 1 its broken just says forbbiden.....
Its broken... hold on ill look again the only file I can find is a .tot that says its the kdz but I didn't use it.. I can't find 10f anywhere all I need is the firmware
Sent from my LG-P870 using xda app-developers app
Thought I would share with everyone how to root Version 10i of the LG Escape.
How to Root Version v10i
Run LG Spectrum ICS Root script (Windows version) Batch file.
Takes about a minute
http://www.sendspace.com/file/jtcbmy
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Me too. ..
Sent from my MASSIVE Galaxy Note® II...*
mackentosh said:
I fell victim to #1 the IMEI wipeout I had to take my phone back for a replacement
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
but how did it happened ? can u please explain steps what u did that wiped yr imei?
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
i got the same problem with tmobile ver the problem is the partition i did tried to repartition in odin with gt-7100 pit file it did not work
can you see your storge and see your internal sd space
sorry for my english
An fyi when u get ur baseband back 3g will not work. I was able to get mine all back and working but I was always on 1x. T3 hit me up in gtalk.
Sent from my SPH-L900 using Tapatalk 2
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
t3project said:
Please Note: No other method listed in the GN2, GS3 forums work for this particular problem. I, as well as a few others have had this happen when flashing different ROMs. I have no idea what causes it but I do have an idea as to how to fix it. I just can't because what I need seems to be disabled in the phone.
Also, I did make a backup of my EFS and a restore does not fix this particular problem.
Problem #1:
After flashing a ROM, the GN2 is unable to activate the radio/modem. The following read "Unknown" in the "About Phone" menu:
Baseband, Network, Mobile Network Type, MEID, IMEI, ICCID.....etc. Basically anything to do with the mobile network.
Problem #2:
When booted up and running, PC will not recognize the phone as usual (unable to copy files to phone).
Problem #3:
And probably the biggest problem: ADB does not recognize the phone. ADB debugging is enabled on the phone in Developer Options but the icon on the notification button doesn't appear. Nor does ADB recognize the phone in recovery. So therefor I cannot transfer files this way either. "nvbackup/nvrestore" can not be used because of this either.
The following methods have all been tried and have failed. Yes, I know what I am doing,
http://forum.xda-developers.com/showthread.php?t=1867442
http://forum.xda-developers.com/showthread.php?t=1852255
http://forum.gsmhosting.com/vbb/f606/tutorial-galaxy-s3-backup-restore-imei-without-root-1513909/
Click to expand...
Click to collapse
You care to clarify which ROM you flashed in particular caused this to happen so that we don't replicate your problem? I want to assume it's your own ROM but just want to make sure.
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Click to expand...
Click to collapse
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
i did flash the s3 rom and after that i lost everythng my phone i need to know how to restor the orgenal sd card cuz im looking with rootexplore it sdcard0
when i go to setting storge it only show 266mb used and 0.00 avilabel any body can help please
mackentosh said:
Well I was testing a rom for someone, I wont tell which rom but he said it was the "in call recorder" he added. He's got it fixed now but it did wipe everything. I managed to restore it back to stock with no root but it bricked after that. Now I see why carriers dont like to unlock bootloaders cause of people bricking their phone and taking them back
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Which ROM had the "In Call Recorder"? I've been looking for a replacement to that functionality after dropping HTC/ Qualcomm with the 2WCR patch on the kernel. ..
Sent from my SPH-L900 using xda app-developers app
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
gotojanoo said:
but how did it happened ? can u please explain steps what u did that wiped yr imei?
Click to expand...
Click to collapse
it didnt actually wipe our imei. it repartitioned the phone.
t3project said:
it wasnt a rogue rom. it was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. i'll post it up in a few
Click to expand...
Click to collapse
Good to know it wasn't released here publicly. Happy to hear you found a solution to the problem too.
dc13 said:
You cant flash a s3 rom the partitions are different. Even the partitions forbthe international note 2. Tmo. Att. Verizon and sprint note 2 are different.
Try flashing the stock tar from sex tape or viper boy. This should fix those issues. Then update the phones prl. Profile. Software. And firmware. And see if u have 3g and everything else.
Then start over.
Sent from my SPH-L900 using Tapatalk 2
Click to expand...
Click to collapse
Try this.
ffolkes said:
Uhh.. no offense to anyone, but if we have a rogue ROM that's bricking phones, we need to know in case it's floating around somewhere.
Also, (and again, not to start any negativity, just curious) the general feel of this thread was random bricking from flashing any ROM, which is very scary and cause for alarm. But according to the quoted post I'm gathering now that this is an issue directly related to accidents within a specific ROM?
Click to expand...
Click to collapse
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
t3project said:
it wasnt a rogue rom. It was two seperate private roms that were never released to the public
there is a very simple fix to this, i've fixed 2 phones this morning already with it. I'll post it up in a few
Click to expand...
Click to collapse
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
mccurt29 said:
whats the fix cuz im going thru this problem right now ...i cant get any service (radios)
EDIT: NVM I JUST FLASHED TO STOCK RECOVERY THEN FLASHED STOCK LJ1 THRU ODIN AND ALL IS WELL NOW
Click to expand...
Click to collapse
simple, wasnt it? lol..................
mackentosh said:
I said I was testing a rom which means I was the only person he released it to at the time. I dont want to reveal the rom or the dev because I dont want any negativity towards him he's a great dev and your probably running his rom right now. So dont worry there isnt a rogue rom floating around
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
Was it mine? I can tell you that if any of the previous stuff happened to you, it wasn't from the ROM. Could have been a bad download, coinsidence, etc. The ROM flash wouldn't have caused it.
Sent from my SPH-L900 using Tapatalk 2
I wrote this request in another thread and I think hasn't been read by many people, so I opened a specific thread.
Our phone may remain stucked for several reasons in a QLOAD 9008 device state, or similar device (easily verifiable even with Windows). It's better to test a solution very simple and useful for all.
To do this is required to extract some files residing in an area of the phone's memory and only a working phone can be used to extract a dump of this files following how explained in this thread:
http://forum.xda-developers.com/showthread.php?t=2136738
Don't think an hardbrick can't happens to you, it may happens and without a tested solution your phone may become a paperweight. Alas my phone is bricked (!), I cannot extract any file from it, I can only try to repair the phone but I need this files to test this method. I invite anyone who has care of his phone to read the topic linked above and try to extract the files needed to repair the phone locked in QDLOAD mode (05c6:9008), we have only this way to unbrick the hardbricked phone for free (if the phone warranty is expired or invalid).
I thank anyone (uhm... mr. Arco68?...) who gives a hand to solve the "Qload 9008 mode" brick problem with this method!
I hope that someone will help you.
I've read the thread, and I'm willing to help... but what exactly I have to do?
Honestly, I can't make any sense of the thread...
Sent from my GT-I8150 using xda app-developers app
yep,,,, and i thought so too,,,,,
even arco himself mentioned he had two hard bricks,,, i dont think,, he just returned it to sammy for warranty use.. i think he had that unbricker you're mentioning..
R: Help to repair the phone stucked on Qload state
santiagoruel13 said:
yep,,,, and i thought so too,,,,,
even arco himself mentioned he had two hard bricks,,, i dont think,, he just returned it to sammy for warranty use.. i think he had that unbricker you're mentioning..
Click to expand...
Click to collapse
Why don't give a try?
Inviato dal mio GT-I8150 con Tapatalk 2
Today, or as soon as possible, I'll try to make backups of the bootloader, partition table and a .pit from an i9100. If I cannot do that, as soon as possible I will try with a i9001 that has hardware very similar to the i8150. I hope I can do it, so I will explain here how to do it step by step to allow other users do the same more easily. Stay tuned!
orsonbear said:
Today, or as soon as possible, I'll try to make backups of the bootloader, partition table and a .pit from an i9100. If I cannot do that, as soon as possible I will try with a i9001 that has hardware very similar to the i8150. I hope I can do it, so I will explain here how to do it step by step to allow other users do the same more easily. Stay tuned!
Click to expand...
Click to collapse
Will a dd dump be enough?
Sent from my GT-I8150 using xda app-developers app
pepoluan said:
Will a dd dump be enough?
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
I don't think, because i think isn't compatible with the tool...
So, on Thursday I picked up an LG G3 from Verizon. I was absolutely loving it. But like most people, I wanted custom ROM's and roots and all the fun stuff you can do with android phones. I rooted my device the day I got it with IORoot. Everything is working fine at this point.
After this, i wanted a custom ROM. I found that there wasn't many for my specific model, but i did see the Sphinx G3 Neo ROM. I payed no attention to what variant it was for and loaded it up on my phone. At first, everything was working perfectly and it was butter smooth. But then I noticed whatever messaging app I tried to use would not work. I did a factory reset and then did the same process to load Sphinx on my G3. This time, messages were working, however, mobile data was not. I finally had enough of this and decided to return to the stock ROM. I found all of the stock files and was attempting to use the TOT method. I put the phone in download mode (which it won't come out of btw) and tried to start flashing. I then realized what I had done and saw that my device was reading something like D855. So when I downloaded the Verizon files it wont work. But will I be able to fix this? Have any of you had this problem before? This phone is brand new and I cannot replace it at this point. I would really appreciate it if someone could help me out.
Hi,
So sad to hear that. Have you tried TOT files from this thread?
I hope your imei is intact.
VeriLG said:
So, on Thursday I picked up an LG G3 from Verizon. I was absolutely loving it. But like most people, I wanted custom ROM's and roots and all the fun stuff you can do with android phones. I rooted my device the day I got it with IORoot. Everything is working fine at this point.
After this, i wanted a custom ROM. I found that there wasn't many for my specific model, but i did see the Sphinx G3 Neo ROM. I payed no attention to what variant it was for and loaded it up on my phone. At first, everything was working perfectly and it was butter smooth. But then I noticed whatever messaging app I tried to use would not work. I did a factory reset and then did the same process to load Sphinx on my G3. This time, messages were working, however, mobile data was not. I finally had enough of this and decided to return to the stock ROM. I found all of the stock files and was attempting to use the TOT method. I put the phone in download mode (which it won't come out of btw) and tried to start flashing. I then realized what I had done and saw that my device was reading something like D855. So when I downloaded the Verizon files it wont work. But will I be able to fix this? Have any of you had this problem before? This phone is brand new and I cannot replace it at this point. I would really appreciate it if someone could help me out.
Click to expand...
Click to collapse
I don't it is bricked per say. I do believe that the only way to solve the problem will be to do as you were trying, return it to stock with .tot files, you just need to find some information which I did see in the threads somewhere with regards to getting out of download mode.
Once you get that done and flash back to stock, then you can root again, I would suggest using Stump root, and the unlock the bootloader with Bump, and this would be a good time to make a backup with the recovery TWRP.
Be calm and read as much as possible, I hope you sort it out. Good luck.
Sent from my LG-D855 using Tapatalk
hierarchy666 said:
Hi,
So sad to hear that. Have you tried TOT files from this thread?
I hope your imei is intact.
Click to expand...
Click to collapse
Just started the download hoping for different results.
BioVolt said:
I don't it is bricked per say. I do believe that the only way to solve the problem will be to do as you were trying, return it to stock with .tot files, you just need to find some information which I did see in the threads somewhere with regards to getting out of download mode.
Once you get that done and flash back to stock, then you can root again, I would suggest using Stump root, and the unlock the bootloader with Bump, and this would be a good time to make a backup with the recovery TWRP.
Be calm and read as much as possible, I hope you sort it out. Good luck.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
I have not found ANY information regarding being stuck in download mode. Not asking for you to go digging, but if happen to find a thread about that I would be pleased if you sent it my way. I have attached some screenshots for you to see the error I'm getting.
VeriLG said:
Just started the download hoping for different results.
I have not found ANY information regarding being stuck in download mode. Not asking for you to go digging, but if happen to find a thread about that I would be pleased if you sent it my way. I have attached some screenshots for you to see the error I'm getting.
Click to expand...
Click to collapse
Can you confirm that you are using a USB 2 port and not a USB 3? Just in case...
Sent from my LG-D855 using Tapatalk
---------- Post added at 10:39 AM ---------- Previous post was at 10:30 AM ----------
Also another question, what modes are you able to boot into when holding down etc the right combination of keys?
Or does it always boot into download mode no matter what?
Sent from my LG-D855 using Tapatalk
---------- Post added at 10:42 AM ---------- Previous post was at 10:39 AM ----------
And finally, have you tried using the LG pc suite?
Please note I have not had any of these problems and so I am only offering suggestions of various things I have read while owning a G3, just makes me sad to see posts like this... Really hope you manage to get it working again... Afterall, we finally have unlocked bootloader!
Sent from my LG-D855 using Tapatalk
Went and picked up another G3 today. Thanks everyone.
VeriLG said:
Went and picked up another G3 today. Thanks everyone.
Click to expand...
Click to collapse
Probably best not to flash something again... like ever
Vivasanti said:
Probably best not to flash something again... like ever
Click to expand...
Click to collapse
Nah, just gotta pay more attention to what I'm doing. Plus, bump just came out.
I take 6 hours to find solution, must use another dll "LGUP_8974.dll"
This one let .tot file take control and don't check phone model, if someone have the same issues this can help
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