Related
Ok I wasnt paying attention when the guy at best buy was messing with my tablet I bought today and I think it updated to ics 4.1 or whatever its on now. But I have managed to unlock my tablet but I cant seem to root it for some reason. Is their anyway to go back to the factor honeycomb or am I F'ed?
EchoM3TH said:
Ok I wasnt paying attention when the guy at best buy was messing with my tablet I bought today and I think it updated to ics 4.1 or whatever its on now. But I have managed to unlock my tablet but I cant seem to root it for some reason. Is their anyway to go back to the factor honeycomb or am I F'ed?
Click to expand...
Click to collapse
If you have unlocked the bootloader just boot into CWM make a nandroid backup then flash a custom rom and you should be rooted with a custom rom. If you're looking for a more custom feel. Try AOKP (All Open Kang Project) they have a extension in settings app thats called rom control and lets you change a lot of things. Then maybe if you're tired of the ICS blue scheme try out my theme for AOKP =) link is in my sig.
Theres really no reason to stay stock since you've already unlocked the bootloader so yeah. But if you're looking for a stock asus rom, but with some optimizations your next best bet would be Virtuous and WSG Roms.
I don't know the relationship between unlocking and rooting....but if you're on a stock ROM, it can't be rooted yet....the 'root tool" hasn't been developed yet.....but I don't know how unlocking affects the process
it gives me a little dead android.
EchoM3TH said:
it gives me a little dea d android.
Click to expand...
Click to collapse
If you unlocked BEFORE it was updated, then you're right....read the threads on recovering from that situation.
I guess my question is, are you sure it's unlocked (the answer is probably YES), but I had a rooted V15, with some modded files....and got the dead guy.....had to update to v21 via the SD card.
Good luck
EchoM3TH said:
it gives me a little dead android.
Click to expand...
Click to collapse
Did you or did you not unlock your prime using the asus unlock tool app? If you did after you have unlocked your prime.
1. Go to market and download rom manager
2. Install CWM via rom manager.
3. Download a Custom Rom and transfer it to your tablet.
4. Boot into CWM Via Make sure its powered off, hold power and volume down till you see some white fine printed words on your upper left hand side. Then hit the Volume Up.
5. Once your into CWM using your Volume buttons (Power button to select) to navigate to Backup/restore & create your first nandroid backup.
6. Install the custom rom you have downloaded.
7.Boot it up.
8.Profit????
My device is unlocked i went through the vipers way too root/unlock device, it says that it rooted it but I went to see if superuser was on my tablet it wasnt. so i downloaded via market place and went to update the binary and its say busybox not found then says ok. checking md5sum okay then install path fail.
EchoM3TH said:
My device is unlocked i went through the vipers way too root/unlock device, it says that it rooted it but I went to see if superuser was on my tablet it wasnt. so i downloaded via market place and went to update the binary and its say busybox not found then says ok. checking md5sum okay then install path fail.
Click to expand...
Click to collapse
Again & again i must stress the fact that you should search and do some reading. Vipers Tool does not work with .21 so can you now boot into your tablet.
Root = allowing you to have system file access
Unlock = allowing you to install a custom recovery, thus letting you install custom roms.
Unlocking voids your warranty, while root does not. If you don't mind the voided warranty boot into your tablet and open the app drawer and look for the unlocking tool. Then run it and you should be unlocked. Then follow my previous post.
reNeglect said:
Again & again i must stress the fact that you should search and do some reading. Vipers Tool does not work with .21 so can you now boot into your tablet.
Root = allowing you to have system file access
Unlock = allowing you to install a custom recovery, thus letting you install custom roms.
Unlocking voids your warranty, while root does not. If you don't mind the voided warranty boot into your tablet and open the app drawer and look for the unlocking tool. Then run it and you should be unlocked. Then follow my previous post.
Click to expand...
Click to collapse
That still tells me its not rooted. can I downgrade to a older version like.20 or something. I did it once with my Evo4g.
Hey all,
I have a CWM backup of my current rom and have backups of apps and data but am stuck at a bootloop.
As I have read countless articles, it seems my error is because I have a locked bootloader(not actually sure). Though, I only tried to flash
clockcycle's wiped v20d cwm backup file. It failed part way saying it couldn't write to /system.
Since then, I haven't been able to fully enter CWM. just see the red triangle with the droid guy on his back.
I have read Cmahendra's unbricking guide but it doesn't work as I have installed JB and even the tips to unplug, wait 10s and reopen the program to flash again it still won't work. Still stops at 15% saying error connecting to the phone.
There is a similar thread which had this exact problem which said to
use the online method to recover your phone since I had already installed JB. I edited the hosts file to remove the fake offline server and opened up the b2CAppsetup.exe, clicked on customer support,
entered my model LGP769BK and my S/N and it began to start the process and 'analyze' then crashed and said "updating is not possible any longer due to a fatal error while the LG mobile phone software Update"
I've tried to search this out myself and not waste any space but I'm at loss here. If anyone has any help, it would be much appreciated
as I don't have a phone while this is not working.
I've tried all the ways to to hard reset, master reset and still I get the droid guy on his back. I can get to S/w mode like all the other posts say to do but none of those fixes seem to work for me. Am I missing something?
Do I have any options here? I have kind of read that I should just unlock the bootloader but I don't think that applies in my case as I can't turn on my phone fully.
edit: for the online method(LG support tool), it basically cancels when it goes to the 'downloading' phase --> this is what I've seen as most of the answers but doesn't work
Upon further reading,
many seemed to need to replace their u-boot and x-loader
I did so and installed fastboot using Lelus' script here:
http://forum.xda-developers.com/showpost.php?p=41768774&postcount=1
I used option 6 which allowed me to flash the u-boot and x-loader from p760(works with my 769 and others as it says in the options) for JB
I'm not sure if I needed this as I don't have an unlocked bootloader.
I'm not sure of commands in fastboot but I ran
fastboot devices and it showed something
I also ran: fastboot flash recovery recovery.img
and I put one of my cwm backups in the "yours" folder
After I activate fastboot, it brings me to the C:\fastboot\yours folder
I assume this is for me to put my intended files in but I'm unsure if I should use my cwm backup or something else?
After it flashed the recovery img, I sent a fastboot reboot command
but it still went back to the droid lying down with a red triangle.
As some of you may see, I'm not too great with this but I feel like I'm close. Does anybody have an idea of what I should be doing?
should I flash an update.zip?
I don't know many commands but hopefully this gets me going in the right direction.
PLEASE HELP ME!!!!
I guess your cmw restore formatted your system but couldnt load the new system
the recovery you run with a locked bootloader uses a technique called 2nd init which i think is somewhere stored in the system partition. so when the recovery formatted the system, it lost itself too.
I've had a similar problem. the way out would be booting into the SW upgrade mode--switch off the device, remove the battery, remove the usb cable. press the volume up button and connect the phone to the computer. wait for a couple of seconds and then insert the battery.
you should be in the SW upgrade mode
now use the B2C client. if it gives an option to upgrade, use that otherwise, go to the customer support menu and press recovery phone
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
shockah486 said:
I have already done earlier. It may have gotten lost in my frenzy of information. I have put the phone into software mode, as you said, and it won't work either; There's no option to click upgrade because it's JB(V20D) and when I click recovery phone and enter my imei, LG mobile support tool(B2capp.exe) analyzes and then has a 'fatal error'
Since I flashed the new u-boot and x-loader my screens are all backwards/mirrored. Maybe the tool flashed an unlocked u-boot and x-loader if that's possible.
Is a recovery possible by fastboot?
I have a clean and full copy of my cwm recovery as well as apps and data backed up, I just need to get this phone in working order
Click to expand...
Click to collapse
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Tablechair said:
If you fastboot flash the u-boot and x-loader from p769(ICS) it should go thru with the offline flash detailed in cmahendras guide.
Click to expand...
Click to collapse
Thanks.I'll try this. if I have the ICS bootloader, does that mean I'll have to flash the V10G kdz? or can i do the v20d kdz
dhruvbatra205 said:
http://forum.xda-developers.com/showthread.php?t=2085344
Use the KDZ_FW_UPD.zip from this thread
Or try this
Remove all of the stuff you have downloaded for this. Download the original B2C client from LG's site and use that
Click to expand...
Click to collapse
I have the updated kdz fw upd .zip from the unbrick and root thread as well as downloaded a new, official B2C client but they all still hang at the download part during phone recovery.
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
shockah486 said:
Tablechair, that did the trick.
Is this because the tool we use to flash for the offline method doesn't recognize the x and u-boot loaderse of JB?
After I installed the ICS boot loaders, my software upgrade mode wasn't mirrored anymore.
I did as tablechair and flashed the V20D.
Does anyone understand why this problem happened in the firstplace? Maybe I didn't get a full copy of clockcycle's backup cwm
or should I have not flashed his recovery in the first place since I didn't have an unlocked bootloader?
Again thank you for all your help and if anyone can provide answers to my other supplemental questions, that'd be great.
Off to root and probably unlock bootloader to be sure.
edit: I can't find the thanks button. but thank you very much tablechair. much appreciated. Hope this can help someone else
p.s. also big thanks to those who made the fastboot program for p769(Artas182x and sguerrini97). really an invaluable tool as I now know.
Click to expand...
Click to collapse
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
Not yet. having problems flashing a kdz again. I've tried the 2 different software modes, as well as setting emerg and diag but still getting stuck at 15% again.
Do i have to replace my uboot and xloader with the ICS ones every time I want to use the offline flash method?
edit: yup, after replacing with ICS loaders again i'm able to flash using software upgrade. will update on whether I can restore cwm
kuma82 said:
Things don't always go according to plan, maybe his Clockworkmod backup was made from the touch version and he didn't have artas182x second init recovery installed. So when the cwm failed the first time, did you try to restore your cwm backup?
Click to expand...
Click to collapse
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Help.
shockah486 said:
I realized I misread your question. When I flashed before the incident, it failed to write to system and I didn't restore my other folder. I rebooted and it was all missed up. Anyway, now that I've got everything back and now with an unlocked bootloader, i was able to recover my old image. However, data isn't working so I have to find the radio to flash as I recall reading in other threads.
Can someone explain in laymen terms why this is? recap, i was on unlocked bl rooted jb and I flashed my old cwm backup when I was rooted but had a locked bl. My apps and messages were all there but the radio was different. I'd understand if I was going from ICS to JB but I was on JB both times. The only difference being a locked BL. It's got to be something about the Radio from p760 or V20B that didn't work on my earlier backup or something like that because the layout status bar is different with a "data" button and showing H instead of 4g(which are the same afaik).
Since, I restored to my backup from after my bootloader unlock and root so data is working showing 'H' with the different layout
Also, I had problems backing up and restoring until I noticed that it works better when I power off the phone and do the manual commands to enter recovery as opposed to using the app to send me to recovery(where I incurred /system backup errors).
My last question is which cwm recovery should I use? I currently have the one for a locked bootloader installed as per Artas182x's website. On that post he has a link for an unlocked bootloader recovery on the xda forums but that thread was updated to not working. Are there any disadvantages to me using a locked bootloader cwm recovery?
I don't think I have any option but to try it as I want to flash CM10.1 for p769. I also read that if your bootloader is unlocked, you can download the cwm from the googleplay. If this is true, can I just install over or should I uninstall the Artas182x locked bootloader one????
update: have to remove l9 recovery by deleting the appropriate system folders and then flash the appropriate .img through adb commands
Click to expand...
Click to collapse
Although I might be late, I have the same problem and the same phone and I really need help. I have a soft bricked phone lg optimus l9 and I had the same problems that you had exactly... Which is weird exept I don't have Clock Work Mod or anything ... If you get this I would really appreciate some help. Thanks
yup me too
I finally got software upgrade to work with my lg p769 that was security error cuz i still haven't unlocked the bootloader, if i knew what a good job lg and T-Mobile did in locking it i would have waited and got a g3 that my buddy rooted in like 5 min and unlocked the boot....
What worked for me is this LG FLASH TOOL 2014 THREAD ON XDA
http://forum.xda-developers.com/showthread.php?t=2797190
flashed both the 20H and 20D successfully i uninstalled everything lg in the control panel first though.
Hope this works for you cuz i was struggling on and off for a month to get this far lol
the 2014 tool ultimately worked for me too, once I fixed a couple things. I had rooted and forgotten to unlock, so it was at Security Error, and it would also disconnect at 15% .. in the 2014 tool, I had to install all the updates even though I'm in windows 7 or it would keep doing it. All good now.
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Liger878 said:
I have been trying all these methods and I am still not able to get in the S/W upgrade mode. The only thing I am getting from the device is being able to put it fastboot mode (The inverted one). I really want to revive this phone
Thanks in advance for any help given
Click to expand...
Click to collapse
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
shockah486 said:
Hey, it's been ages since I have done any of this but IIRC, if you can get into fastbood mode u can still get into software mode,
- turn phone into fastboot mode
- open the software upgrader thing as you normally do
- maybe switch emerg to diag or something like that
- this part is where it's slightly different than the normal way(same program but u select a different option than the default 1st option on
I think if yoiu look through the tutorials it does mention an alternative method for getting into software mode
in one instance in my past, i had to reflash the ICS boot drivers so the software installer would recognize that
the flashing of the ICS boot drivers is done through fastboot. Should be a post in my history where I asked a question regarding this.
Sorry for the chaos but maybe this will help you get in the right direction since I don't know any of your phone history and what you've done etc
best of luck mate
Click to expand...
Click to collapse
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Hopefully you find the thread that states the exact steps bc that is off the top of my head and over a year ago by memory . GL bud
Liger878 said:
Thanks, Never tried switching to DIAG before but I will try it and let you know what is the outcome.
Click to expand...
Click to collapse
Hey, I have been trying it with the fastboot but it keeps timing out and not allowing me to finish. One thing I should let you know is that, ever since I had put the device in fastboot, I am not able to get back the S/W upgrade mode. Dont know if that will help in seeing what my problem is or if you want me to explain everything from the beginning again, I am more than happy to.
Have you followed the steps that I linked to in the first 3 posts of this thread?
Follow the steps to flash the ICS bootloaders in fastboot and then you can do the fastboot trick for getting the software to recognize your device.
Right now your phone has the JB boot loader on it and is thus not recognized by the software.
recap:
step 1: flash the ICS bootloaders in fastboot (look at the linked thread in post 2)
step 2: use the software in emerg or diag mode but sitll follow the same steps as the tutorial. I think my earlier posts should explain precisely.
if you dont flash the ICS bootloaders, it won't be recognized by the KDZ installer
Hello, recently I have rooted my phone using the toolkit. The current recovery I have is TWRP. I wanted the root in the first place to be able to use xposed. However, it wont work, Whenever I try to install the update or new version it force reboots my phone. Also I found out I cannot update my software! I tried unrooting using the unroot option on SU but it was only temporarily. I want a permanent unroot and back to stock.
Android version : 4.4.2
Software number : 1.12.502.18
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me. Thank you.
Update
So i just downloaded a different image. I flashed it successfully! I am currently rebooting from the original recovery! Currently I am on the htc one loading screen. It's been a couple minutes, hopefully I did not brick it...
NOPE! I successfully returned to stock! ANother issue...I still have root access! How can remove SU? I tried the unroot option in the app but I am still rooted after reboot...
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
helpmeunrootmyphone said:
UNROOTED. Sadly SU won't delete...but at least I'm unrooted and can update now.
Sent from my HTC One_M8 using XDA Free mobile app
Click to expand...
Click to collapse
I don't know if the app is that big of a deal to you, but if it is, your options are...
1. Try factory reset in settings (may or may not work)
2. Reflash TWRP and flash the SuperSU.zip again than do a full unroot in settings.
3. Reflash TWRP and flash stock Sense ROM
Also, I made a guide in general which will help you fully return to stock. To begin the guide, you will need to be unlocked, rooted, and S-Off. That guide will help you hide the tampered and relocked banner.
If you don't care about the banners and the SuperSU app, it's probably not worth the effort and time.
Good luck.
Sent from my HTC One_M8 using Tapatalk
So you had an issue with Xposed, and you solution was to unroot? Wouldn't it have made more sense to troubleshoot the xposed problem? If you bothered to unlock the bootloader and root in the first place, IMO unrooting is a step backwards.
I'm also not a big fan of applying OTAs to a modded device. Yes, you cannot install official OTA updates on a modded phone. In particular, if stock recovery is not present, as its required for the OTA to install. If you want the latest software, just wait until the rooted version is posted in the Development section. Custom ROMs based on the 1.58 update started to be posted one day after the OTA started rolling out; and the stock rooted version was posted only 2 days after OTA release. For some people, getting it from here may even be faster than waiting for the OTA! That's pretty much how it goes. As long as there is developer interest in the device, you can rely on the latest software being available very quickly in the Development section.
The stock AT&T software is garbage anyway. I can't stand the amount of bloat, gimped features (WiFi hotspot) and other AT&T meddling. I don't understand why anyone would prefer this over other options. Software updates are always going to go to the international version first, anyway (AT&T is notorious for delaying updates for "testing"). What are you really getting with the 1.58 update? Extreme Power Savings mode, and a few other fixes? International M8 has had EPS mode for some time now.
---------- Post added at 09:31 AM ---------- Previous post was at 09:17 AM ----------
helpmeunrootmyphone said:
I downloaded my stock image from http://forum.xda-developers.com/showthread.php?t=2701376 and the toolkit from http://forum.xda-developers.com/showthread.php?t=2699065
I tried to flash it using the toolkit but it gave me an error when I tried to flash it. I don't recall correctly but it said something about a remote error right when it was sending the image over. Honestly I do not want to do it again to see what it said in fear of bricking my phone. So I will try to be as detailed as possible.
When I downloaded the image it said something about the name not being the original one. When I first tried flashing the stock ROM with the original name when I download it"stock recovery 1.12.502 recovery.img" it (the toolkit) gave me an immediate error of not being able to select it. So I renamed it to "recovery.img". I tried again and it actually was in the process of flashing. THen the error showed up as said above. Someone please help me.
Click to expand...
Click to collapse
Why do you need to use the toolkit at all, to flash recovery? Flashing recovery is a single fastboot command. Easy.
The toolkit adds unnecessary complication; and I've seen them cause errors when doing it "manually" works just fine. The toolkit might not be the problem in your case, but we would never know unless you try to do it manually.
If you really want to flash stock recovery (not my personal recommendation), I would start by wiping cache and flashing recovery with fastboot. I've seen maybe dozens of cases where issues with flashing a recovery was solved simply by wiping cache:
fastboot erase cache
fastboot flash recovery "filename.img"
I am having the same issue as above using the same build file from the link given in the other thread. However, whenever I am in Bootloader, the computer or terminal does not recognize my device.
1.12.502.18
Anytime I try to use the toolkit or manually through the command line, it gives me "unc paths are not supported" or "device not found". It is the same for both Bootloader and Recovery. My original problem was the person I bought it from had root on it so I decided to wipe the OS without backing up and now cannot get the Stock Recovery ROM or any other Custom ROM to install on the phone. I have also tried the SD card method and that brought up an error as well resulting in "failed."
Any help would be appreciated as the phone as it sits right now does not have any OS on it so it is stuck on the HTC Boot up screen.
Thanks in advance for those that can help.
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
kmt5150 said:
Greetings, fellow Mega-Maniacs!
I am currently working with dev Geohot to get us root access for the SGH-I527 with Baseband Version I527UCUBNE7. All known root methods have been tested and proven to not work with this version of android with this baseband, due to the extremely locked down nature of Samsung Knox on this device.
I, personally, have been throwing every exploit I can think of at this device, to no avail. As of the time and date of this post, we have a donor ready to help the cause (Special thanks to caguas56). That is why I'm proposing a bounty on root access for this phone (SGH-I527 AT&T US version only, although there is a high possibility that it'll work on the Sprint,T-Mo and VZW variant).
The first developer who can successfully get ROOT on KitKat with baseband I527UCUBNE7 and demonstrate this with a successful public test will be awarded the bounty. The bounty will be split equally between devs and donors willing to team up.
I'm in for $10 at the moment, and I'll piss away more if needed down the line.
Who else is in? LETS GET THIS DONE, PEEPS!
Please, only posts regarding root access on this thread. For firmware rollbacks to 4.2.2, see azpatterson3's thread located HERE
Click to expand...
Click to collapse
In for at least $20.
Put me down for 2 bucks.
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Grarak said:
Bootloader is locked
So no recovery flashing
Sent from my GT-I9205 using XDA Free mobile app
Click to expand...
Click to collapse
Well technically all bootloaders are locked (except for the few that aren't) but I take it AT&T is wanting/trying to join the band wagon with Verizon and locking the bootloaders indefinitely by encrypting them on all the devices they can now.
Sorry then, my method will not work straight forward. Good luck. :good:
DarkAngel said:
I know you stated you had tried it all but I have a couple questions for you.
#1. Are you able to odin and access the latest PhilZ Recovery on your Mega? I ask because I read other sections like the Note 2's, etc on AT&T and they are able to flash recovery fine and boot into recovery fine.
#2. If you have tried this method, did you try and flash the latest SuperSU v2.00 from Chainfire through PhilZ?
================
Below is a method I suggested to some in my OTA Update thread to NE4 ( KitKat ) for Rooting all my Galaxy phones on KitKat listed and not one has failed to gain root or to disable KNOX. Note this method will trip KNOX and void your warranty. Try this at your own risk....
================
1.Flash the latest Philz recovery ( Galaxy Mega (meliusltexx) ) .
1a) Be sure when flashing a custom recovery not to allow the device to reboot into the OS right after and instead go straight to the recovery first.
( Uncheck reboot device in Odin or if you forgot to uncheck the box after a successful flash of the Custom Recovery in Odin, quickly hold down vol+, Menu & Power Button or last resort pull the battery before it has time to reboot into the OS {again this is after the phone reboots from flashing the custom recovery and passes}).
The security will over write the custom recovery with the stock recovery and you will have to flash Philz or if available TWRP again. First boot into custom recovery will make it stick on after.
2. Once flashed and booted into recovery, you'll be on the main screen.
( Optional but recommended )
2a) At this point, and it is just a suggestion to you all, make a complete backup of the phone as it sits unmodded. I couldn't really tell you how many times I have read/seen of people post that they forgot to back up their phones after they had attempted to do something to their phones and had caused them to have problems..... well many would be surprised how often this happens and I have been guilty of it due to just being impatient. This way you will have a starting point fresh, stock and even unrooted to go back to. After your done proceed to step #3.
3. Tick on Philz settings.
4. Tick on Re-root System (Super SU).
5. You will then see the log scroll at the bottom and tell you to reboot and install SuperSU through the Playstore.
6. Reboot Device and once you have booted up, install SuperSU via Playstore or if you have the APK on hand, install it.
7. Once installed it will ask you that it needs to update binaries, do so. It will also detect KNOX and ask to attempt
to disable it, go ahead and it will attempt to do so. ( I have yet for it to say unsuccessful )
8. Enjoy being rooted afterwards.
=======================================
If after step #6 it fails to update binaries or for some chance the SuperSU APK failed to install properly or failed to provide Root Access, below is a link for the newer SuperSU v2.00 that is flashable in your Custom Recovery. Flash it by rebooting back into Recovery and flashing the ZIP file that's downloadable from the middle of the main page in the link below. Once flashed continue on from step #6 above.
Thank you @Chainfire
SuperSU v2.00 <------- click here
.
.
.
.
.
Click to expand...
Click to collapse
Believe me, we have tried it all. I have tried a process similar to this and when the phone got done with all the flashing and went to boot up, I got a prompt that said 'We have detected software not approved for use by AT&T. Please take your phone to an AT&T store for assistance.' It also says Secure Check Failed: Kernel. I had to send my phone to sammy to get it fixed since I tripped a few flags. Should be back by Friday the 10th.
Possible to use this method with 4.4 kernel from mega?
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Will definitely try this again when my phone gets here tomorrow and post updates...
jstinger9489 said:
http://forum.xda-developers.com/showthread.php?t=2722073
I don't know much about this but my S4 active also has a locked bootloader, and I was able to achieve root on 4.4.2 using the above method. Thought it might be possible to adapt to your cause.
Click to expand...
Click to collapse
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
kmt5150 said:
Tried and my device still won't act right, can only get into download mode. recovery is gone and when i attempt to power on, I get a msg about Secure fail: Kernel and then a yellow triangle with a ! says 'System software not authorized by AT&T has been found on your phone. Please turn off your phone and go to the nesrest AT&T store for help."
UPDATE: A buddy of mine has a JTAG service and I'm going to send it to him for repair. UGH! I'm selling this sonofabitch. I should NOT have to go thru this much bull**** just do modify something I paid 500 bucks for without a contract.
Click to expand...
Click to collapse
Have you tried towel root
http://towelroot.com/
BarakOsama said:
Have you tried towel root
http://towelroot.com/
Click to expand...
Click to collapse
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Can anyone send me boot.img of ATT KK rom?
captemo said:
Have YOU tried towelroot?
Or have you not read any of the many theads on the subject?
Sorry, not trying to be rude, the same thing has been said so many times
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
My bad..
Alright.
To summarize for people who haven't paid attention. Phone was bricked in a last ditch effort to flash back to 4.3 because the 4.4 update made my phone run like s#it. I also have an S4 Active and the service sucks harder than it already did. The 4.4 update makes the S4 drop out constantly and the battery life blows. Samsung told me to run kies in download mode to get it back to 4.3 I did and BOOM, now phone is fu©k!ng bricked and they won't fix it, claiming it's 'rooted' because the kernel says it's version 3 when it's supposed to be at 4 for kitkat. Fu©k!ng duh, you jerks made me flash it back. I am personally never buying another samsung product again because their customer service was horsesh!t. I happen to have a sammy tv, blu ray, home theater and 2 of their former 'top end' phones, but now I'm ditching them. They can lick my scrotum for all I care anymore.
end rant, back to music.
SCH-R960
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
MeatHammer311 said:
I have the US Cellular Galaxy Mega SCH-R960 also updated to 4.4.2 out of the box. I am in for some bucks if you can apply this to my version also the baseband number is R960TYUBNF1, I will send you whatever info you need from the phone. Lets get this done! Thank you!
Click to expand...
Click to collapse
Can you make a complete firmware dump and compile a .PIT file?
No root.
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
MeatHammer311 said:
I do not have root so I can not do those things. If there is a way without root please point me in that direction. Thanks
Click to expand...
Click to collapse
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Grarak said:
sure you can
use heimdall
and can anyone send me the boot.img now?
I don't even think you guys want root if you're not even trying to help
Click to expand...
Click to collapse
tell me how to get it any you will have it 1 before 5pm today est.
also here is the pit file you asked for. I used it to unbvrick my phone a few times with odin.
ita for the at&t version
I know there has been many threads giving explicit instructions on how to unlock bootloader, gain s-off, and install TWRP recovery. But I am having problems/questions that no one (at least of what I've read) has encountered. I will try and make this clear for y'all but bear with me. Before I start just let it be known that I DO HAVE my bootloader unlocked. I ended up going to a cell phone repair place and paying a small fee to get my bootloader unlocked.
1. Do I need to gain s-off to be able to root and install TWRP recovery?
I say this because the I have tried the has00n application to unlock bootloader, gain s-off, root, and install TWRP recovery, but I ran into problems with my computer recognizing my device. I had all the necessary files downloaded (at least to my knowledge) but it honestly just wouldn't recognize my device.
2. If I do not need to gain s-off to install TWRP recovery and install a custom ROM (I'm going to be installing Cyanogenmod), how do I go about doing that?
Honestly I'm so fed up with this that I just want to sell this phone and get another one, all I want to do is get Cyanogenmod on this phone but it's so immensely difficult.
Please help me! I have been trying to get this accomplished for so long but I feel like because this phone is older all the info about how to root and gain s-off is outdated.....
All of your help is greatly appreciated!!
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
You shouldn't need s-off for installing a custom rom. That's for tinkering with model id and scary stuff like that. I'm not sure what that tool is but I only know of one way to get s-off, and that's sunshine s-off.
As for rooting, when you install a custom rom via twrp or cwm, it will typically ask you if you'd like to root your phone AFTER installing the rom, but BEFORE you restart the first time. So the process should be:
Unlock
Install twrp or cwm
Wipe and factory reset
Install rom
Once completed, phone will prompt if you want to restart
Select YES to root on restart
And then wait for the phone to reboot! (it'll take a little while first time)
After the boot, it'll probably ask you to install superSU, which is the root manager app. If it doesn't, find it in the play store and you're set.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply. So as of right now I am using the fastboot adb to control my phone from the command prompt on the computer, but there is a problem. When I try and flash the custom recovery (either TWRP or CWM) it says that the files are unrecognizable, so they're pretty much corrupted. I honestly don't know that to do. I know I can achieve root if I just get either one of these recoveries to flash but it seems that all the files for the htc one m8 TWRP and CWM are corrupted. What are you suggestions at this point? The fastboot iadb is working perfect I just need a non-corrupted recovery file and I'm searching around the internet withno luck of finding one. Is there one that you can attest to working? If so that would be amazing. Again, thanks for your help, hopefully we can get this sorted out!
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something ?
Sent from my HTC One_M8 using Tapatalk
shoe-jitsu said:
Hmm, do you have the latest version of twrp? Sometimes older versions don't install, I would try to see what version of twrp htc one m8 users are using, I'm not by my computer right now so I'm not sure. I also know that twrp works better on htc one for some reason, I've never found a version of cwm that works on my htc one. Make sure you are using the proper install command to install it too, I think it's fastboot flash recovery FILENAME.IMG
If all else fails, all I can think of at this point is that you got a bad download or something
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either. The fastboot command i am using is the same as the one you stated. There's just a problem with the files. I'm beyond frustrated but really thank you for your help. When you're by your computer can you please send me the twrp version you have, it would be much appreciated.
Click to expand...
Click to collapse
Can you copy and paste your command window to this thread? It would help to see the exact error outputting. You can highlight and right click to copy anything from command window.
flapjackSam said:
Yeah I've been trying to use the most current version of twrp and it didn't work. I ended up trying past versions and those didn't work either.
Click to expand...
Click to collapse
Is the phone currently on Lollipop, or otherwise? You can't know what version TWRP is correct, without this info. Current TWRP (2.8.7.0) won't work if the phone is on older OS version. Vice versa, if the phone is currently on Lollipop, older versions of TWRP (I believe older than 2.8) won't work. You have to flash the specific TWRP version that matches your OS version. Guessing which TWRP version to flash is not the right way to go about this.
Also, you need to tell us the actual TWRP version number you got, and where you downloaded it from. I've seen quite a few instances where folks thought they had the "most recent" version, but in fact they weren't even close. Its always best to be specific as possible, and provide all the details when getting help here.
Additionally, go into Settings (or do getvar all), and tell us the software number. If you got the Stagefright patch, it might be screwing up install of TWRP as well.
flapjackSam said:
The fastboot command i am using is the same as the one you stated. There's just a problem with the files..
Click to expand...
Click to collapse
Again, just saying you used the "same" command isn't enough. A single wrong character, wrong file name, wrong path will cause the command to fail. As the previous response requested, please cut/paste, or better yet post a screenshot of your command prompt window, so we can see the exact command syntax, and the specific error message.
I can virtually guarantee that as long as you downloaded the file direct from the TWRP website, and tried downloading (and flashing) it more than once (to eliminate the possibility of corruption during file transfer); that the issue is almost certainly pilot error.
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
MistakenUtopia said:
Somehow I'm a little frusrated. I've brought my phone since today. So it is currently on Lollipop. There is no Power in setting to uncheck Fastboot. Is there any way I can root my phone?
Click to expand...
Click to collapse
Press and hold the power button until is hard reboots, then hold vol down as well. You should go to boot loader before the HTC screen pops up.
Back Up!
Just a reminder, after you install TWRP, boot into recovery (TWRP) and create a backup file saved to your SD card first before trying to install a new ROM!
Always can restore if things go wrong or you don't like it.
:fingers-crossed: