Hi guys,
sorry for bothering you guys, but at this point i'm pretty much desperate. I tried to root my Xperia Z since it brings oh so many wonderful possibilities with it and i was sick watching at all the bloatware floating around my screen. Anyway. Since i'm a total noob when it comes to phones i have been reading quite a lot of confusing stuff on the internet, especially here as this site was recommended to me by a friend.
Now i do have a bit of experience flashing PSPs and such, so i thought "you're not a total moron, how much more difficult could flashing your phone be ?". Guess i was wrong =)
I followed this instruction: http://www.youtube.com/watch?v=Vs2iPY0J4ZA
Yeah, i know, it's a video and all. But the thing is. I've by now read different guides all explaining the same thing. And every one of them put things differently, most of them claiming it was totally easy, but most missed a few steps. So i thought a step by step video tutorial would be quite easy to follow. And it kinda was, until ...
The unlocking failed. At the point where it was supposed to say "unlocked successfully", nothing happened. Just the cmd-line and then "---", which from my knowledge stands for "proceeding". To me it was stuck. And it kept standing there for about half an hour, when impatiance kicked in. Yeah, im dumb like that. So i close the cmd and tried to reboot my phone and got a bootloop just after the logo.
So i went into fastboot again and basically tried to unlock it again. This time successfully only after a few seconds (i guess this is how it's supposed to be, since that's what it was like in the video.) Still bootlooping though.
Now at this point i'm frantically troubleshooting and kinda feel like a monkey with a wrench. It should work, but maybe i'm just doing it totally wrong, since i don't know better.
So at this point, from reading even more stuff i'm trying to flash a stock firmware onto that thing by using flashtool (http://forum.xda-developers.com/showthread.php?t=2162907). This is the firmware i found from that thread: http://forum.xda-developers.com/showthread.php?t=2216743 .
Now before i make things even worse. Is there anything wrong with my approach, do i need to think about anything else ?
The idea in the first place was to install this: http://www.cyanfox-rom.com/2014/01/01/cyanfox-2-0-2/
In that regard, would that be the right thing to do now ?
If you've read this far, thank you for your time and dedication to help. I really appreciate it. If you need any more information as to what i've done, don't hesitate to ask. Chances are im lurking around desperately.
First, dont worry, your phone can be repaired with flashtool. You can download flashtool (find it on Xperia Z android development section) and download FTF firmware for your phone, 4.3 is newest. and just follow simple instructions how to flash (cant search now for the link)
If you want to use 4.3 and to be rooted you must first flash 4.2.2 10.3.1.A.2.67 firmware and then follow this tutorial http://forum.xda-developers.com/showthread.php?t=2458268
Thanks a lot. Flashing worked like a charm.
However the info still says: "Bootloader unlocking allowed=Yes". From my understanding that means it's still locked ? So it's back to square one ? Add frustration to depair now... seems like i don't understand the process or something...
longerdonger said:
Thanks a lot. Flashing worked like a charm.
However the info still says: "Bootloader unlocking allowed=Yes". From my understanding that means it's still locked ? So it's back to square one ? Add frustration to depair now... seems like i don't understand the process or something...
Click to expand...
Click to collapse
It's not working. Went into fastboot again, unlocked, this time successfully in 1.0s. And again bootlooping.
What am i doing wrong ? I just don't get it. From my understanding it should work normally and i should be able to proceed to root. And this would require me to start the device normally in the first place right ? Im on here right now: http://forum.xda-developers.com/showthread.php?t=2327472
But to be perfectly honest, at this point i'm guessing here. :crying:
Okay, next try, same experience. Do i need to do anything else after the unlocking ?
Do i have to reboot and just go into that root thingy and start the runme.bat ? Edit: Which isn't even possible since i can't boot.
OR do i need to flash kernel and stuff.
These are basically the 2 options that i found and i'm totally confused about which one i need to do as to me both are exclusive of the other ? I think i need to solve that bootloop issue in the first place, right ?
I think it's absolutely clear that i need help with this stuff
Hours later i'm still trying to get this working. However it just doesn't. Bootloop keeps happening.
Since i don't know if i made a mistake or not, i just chose to try to go on about the rooting. This doesn't work either. I tried to do it like in this thread: http://forum.xda-developers.com/showthread.php?t=2154310
From my understanding it's for the .350 fw,but also works for the one stock rom i downloaded earlier ? Can anyone confirm that ? I'm just guessing here, since there is no explicit information about that for noobs like me. At least i didn't find it.
Well anyway. I ran fastboot flash boot auto root blabla... and this is what it tells me:
sending boot... okay
writing boot... failed (command not allowed)
WHY ? Does this have anything to do with the unlocking process before ? Did it fail ? Am i just using the wrong fw ? Any pointers as to what i'm doing wrong here ?
I know i cannot demand any help, since you don't really get anything for it, but it really drives me crazy. So any help is highly appreciated. So please... pretty please ! Thanks in advance.
drunkennes veenser
bump - thanks for reading - let me know if you have any ideas.
If it's root you want, you do realise you don't have to unlock your bootloader?
Xperia Z
---------- Post added at 10:49 PM ---------- Previous post was at 10:47 PM ----------
Use this guide, easy to follow and 100% works...
Xperia Z
---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------
http://forum.xda-developers.com/showthread.php?t=2565850
Xperia Z
Thanks, might try that one if everything else fails. This is still a stock rom build with all the bloatware right ?
However i am trying to get to install Cyanfox (see a few posts ago). To my understanding an unlocked bootloader and root are both required.
Just to my understanding, does that mean, that my unlocking the bootloader failed ? Or why isn't it showing an unlocked bootloader in the Config ? Sorry if i am asking dumb questions, but i seem to be stuck and i'd really like to understand what i'm doing wrong.
Tomorrow a friend of mine will try to help me with all that, since he has some experience with customs on his phone (a S3 i believe). So he told me that he has no experience with the Xperia Z. I'll also would like to show him this thread for additional info. So if there's anything you can throw at us, that might help, please go ahead. Again, i appreciate your help.
Hi, I would try and get back to stock if possible..
You might want to download Sony Update Service and connect your phone up through that. If your bootloader is unlocked, then SUS wont let you go any further but if you are locked you will be able to repair firmware back to stock...
Please dont take this the wrong way but if you are new to flashing ROMs then it might be better for you to take things one step at a time.
What I mean is start off by just getting used to rooting stock ,, then try flashing custom roms when you feel more confident with the process and after you have tried flashing a few custom ROMs to see which one you like best (there are some great ROMs for locked bootloaders out there), If you really want to unlock bootloader then go ahead...
It just seems like trying to root, flash ROM and unlock bootloader all in one hit just multiplies the likelyhood of errors occuring and it can be difficult to pinpoint at what stage it went wrong..
Good luck ...
Onmehedson said:
Hi, I would try and get back to stock if possible..
You might want to download Sony Update Service and connect your phone up through that. If your bootloader is unlocked, then SUS wont let you go any further but if you are locked you will be able to repair firmware back to stock...
Please dont take this the wrong way but if you are new to flashing ROMs then it might be better for you to take things one step at a time.
What I mean is start off by just getting used to rooting stock ,, then try flashing custom roms when you feel more confident with the process and after you have tried flashing a few custom ROMs to see which one you like best (there are some great ROMs for locked bootloaders out there), If you really want to unlock bootloader then go ahead...
It just seems like trying to root, flash ROM and unlock bootloader all in one hit just multiplies the likelyhood of errors occuring and it can be difficult to pinpoint at what stage it went wrong..
Good luck ...
Click to expand...
Click to collapse
I think that hit the nail on the spot =)
Thing is, i am a really impatient guy, which isn't the best trait when "taking it slow". It's more like "i want the best, and i want it now"
Of course what's best can't be answered objectively and i can't pinpoint why i decided on that specific rom, but it looked awesome to me, so i just went for it and tried to read up everything i need to know to make it work I just didn't expect to fail at the very first step... that's kinda very very frustrating.
Anyway, i'll see what we can get done tomorrow and make sure to report back. Again, thanks a bunch !
Sooo, aparently i made a mistake in the cmd line. We don't really know what i did wrong, since the KEY was correct, although i wrote ".exe", my friend didn't, and instead of typing it letter by letter, he copied it (i didn't know how, lol). And it worked at first try, no idea what i did wrong. So that's done.
Rooting was also easy. Sadly we couldn't go on at this point, since i had to download a few more things first. So after that, i'm on my own again and, who would have thought, next problem's not far away.
Now i do have a problem flashing roms. Every rom i tried gave me a "status 7" error. Now i already searched up a solution that includes removing a few lines in the updater-script.dat. However that didn't work either. I'm pretty sure i followed the guides exactly. But at this point i kinda have to assume, that i'm even too dumb for that.
Any suggestions ?
Here's what the log says:
Mounting partitions...
Extract busybox...
Extracting firmware update image file...
Note: This may take a while (it stays here for some time, np though)
Formatting SYSTEM...
Extracting firmware update to SYSTEM...
Note: This may take a while (and again it does)
Performing finalizing tasks...
set_perm: some changes failed
Error in zip
(status 7)
Installation aborted
Maybe this might help, tell me if u need anything else
longerdonger said:
Here's what the log says:
Mounting partitions...
Extract busybox...
Extracting firmware update image file...
Note: This may take a while (it stays here for some time, np though)
Formatting SYSTEM...
Extracting firmware update to SYSTEM...
Note: This may take a while (and again it does)
Performing finalizing tasks...
set_perm: some changes failed
Error in zip
(status 7)
Installation aborted
Maybe this might help, tell me if u need anything else
Click to expand...
Click to collapse
what recovery are u using and which rom u wanna flash?
Gesendet von meinem Nexus 5 mit Tapatalk
Tommy-Geenexus said:
what recovery are u using and which rom u wanna flash?
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
downloaded latest cwm via rommanager, it says v6.0.3.0
To make things simple i tried flashing the suggested stockbased rom (http://forum.xda-developers.com/showthread.php?t=2565850)
But since i keep getting the same error with any rom i tried, i assume i'm generally doing something wrong.
longerdonger said:
downloaded latest cwm via rommanager, it says v6.0.3.0
To make things simple i tried flashing the suggested stockbased rom (http://forum.xda-developers.com/showthread.php?t=2565850)
But since i keep getting the same error with any rom i tried, i assume i'm generally doing something wrong.
Click to expand...
Click to collapse
The recovery is probably your problem.
Try using atleast twrp 2.6.3.0 or philz touch cwm or the latest cwm
you can use the dual recovery as well
Gesendet von meinem Nexus 5 mit Tapatalk
Tommy-Geenexus said:
The recovery is probably your problem.
Try using atleast twrp 2.6.3.0 or philz touch cwm or the latest cwm
you can use the dual recovery as well
Gesendet von meinem Nexus 5 mit Tapatalk
Click to expand...
Click to collapse
Got cwm 6.0.4.5, worked great ! THANK YOU A LOT !!! :good::good: OH YEAH, double thumbs up ! And there's me thinking, the guide said get rom manager, the program knows where to find the latest version. Whatever, great forum, seems like i finally might have figured out what i'm doing, at least kind of
Now to exploring all the funny roms and apps. I'm so excited
PS: Since this solved, do i need to do anything else ? I've seen "Solved" being in the title. Can i do that or do i have to ask a mod ?
i saw you solved your problem but still have a look over THIS
Related
So i rooted my phone using the universal root in this forum, the day after i accidentally updated android and it broke the root, also i have noticed some bugs. I am trying to put the phone back to how it was when i got it in the post. i tried a "factory data reset" but it didnt do what i am trying to do, just deleted all the apps etc. Any ideas how i can do this? I dont mind if i have root access still.
Cheers!
Read my signature, the bigger link. I'm sure you'll find the info on rooting FRG83 there (because I've put it there).
Okay i think i need some help, i have downloaded the official rom an put it on the sd card but cant work out how to flash it, im holding down the track ball and resetting but cant see the option to flash anything, is this because it wasnt rooted properly where android updated?
this sux on an epic scale. when my phone was ****ed.. no one posted with a signature that had information about how to install stuff to phone without unlocking bootloader .
grrr...
dude read the wiki... its all there
Ive been reading this tutorial: /showthread.php?t=614850 but not sure how to run the commands on steps 8 - 13
To make it even easier, these are the words you need to concentrate on looking for:
Jack_R1 said:
rooting FRG83
Click to expand...
Click to collapse
I supposed my post would say it clearly enough that your idea of restoring the ROM to the older version won't work.
Just managed to root it, then got totally lost, might have to leave it like this..
Yes, that was the idea. Root it, and stay with it. If you post the bugs, they might have solutions / workarounds.
Plus, it might be a good time to try custom ROM Or even customized plain FRF91 you were looking for.
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Have you checked with Root Checker Basic to see if you even have Root? If you didn't follow the Super Guide step by step your phone could have relocked after you turned your phone off/on.
If it still fails to update you could try SuperUser Update Fixer.
Yes I have check with root checker.
This may be a dumb question but how do I uninstall Superuser? When I go to the typical application management it does not give me the option. I have done an install again to overwrite the files and nothing changed there.
I followed the instructions step by step (though obviously I messed up somewhere...)
Sent from my HTC PH39100 using XDA App
Kraizk said:
So I am a new person and therefor can not post this in the development thread under the forum where I feel it would belong with the other root related questions.... So i followed the SUPER GUIDE to root my phone (Thank you so much Slapshot and PirateGhost, I was beginning to regret not getting a skyrocket until I found your thread). My super user is running into an issue I can not seem to fix.....
Maybe this is simple or maybe I really messed something up....
Basically none of my apps have root anymore (they did at one point and to my knowledge I change nothing...)
When I go to the Super User app to update my binaries and hopefully get any issues resolved I am greeted by the following error message in the update log: "Failed to find currently installed SU binary. Update cannot continue"
Is there a resolution for this? I have not found anyone even running into the same issue on the Vivid.....
A little nervous.... I didnt have near this many issues rooting my ATRIX and modding the living daylights out of that.
Click to expand...
Click to collapse
Interesting... maybe your root didn't stick. We had a little trouble with that before but pirateghost fixed the CWM ROOT zip. You have a working CWM Recovery, correct?
In the superguide, I have a second option for root in case the first doesn't work. In your case, go ahead and try the second option. The one involving the supertool. That should get you perm root. If that doesn't even work, then we might have to put you back to stock and go at it again.
EDIT: BEFORE TRYING THE SUPERTOOL, try flashing the new CWM ROOT VER2 zip from CWM recovery and see if root sticks.
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Kraizk said:
Slapshot, thank you for checking the General Thread, I really do appreciate that. I have tried both methods multiple times since the root failure seeing as so many people said they had to run the methods multiple times to make them stick (this admittedly may be part of the issue). The most recent one has been the CWM ROOT VER2. Still no dice. Is there a method to remove and re install super user? Or am I reading into the error too literally and instead I just basically do not have root.
Click to expand...
Click to collapse
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
*Just a clarification*
You have to unroot your phone to get rid of it Idk why I put uninstall/reinstall earlier...still out there from last night I guess.
slapshot30 said:
No problem. At this point I think you may just not have root... but first, go ahead and go into bootloader (power off, then power on while holding power and vol down). Does your device say unlocked?
Click to expand...
Click to collapse
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Kraizk said:
Yes the device still says unlocked. That was one of the first things I checked... Haha....
As I said ive flashed the rooted CWM and it says it went over successfully.
If i use the Zerg exploit it still seems to go over successfully (I realize this has a tenancy to mess with internal storage and only provide a temp root but i do not even get that temp root).
How would I unroot my device? Do you mean flash to stock and relock my boot loader?
As I said I have flashed several devices in the past (Atrix, eee pad transformer, HTC Inspire, HTC DINC, SAMSUNG GALAXY S T-Mobile) but I am not completely up to date on all of the technical terms...
Click to expand...
Click to collapse
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
slapshot30 said:
Yes, I mean relock the bootloader and back to stock rom, then try again. Do you know how to get back to stock?
Click to expand...
Click to collapse
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Kraizk said:
actually that one I do not know how to do... I realize this is probably somewhat annoying because I am sure you have said how to do it before.... Some help would be greatly appreciated
Click to expand...
Click to collapse
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Kraizk said:
Thank you for this and all of your help, people like you and ghostpirate are why i still feel like I can turn to the XDA community. I will try this firs thing in the morning and give an update on how things went. I would try it tonight but lets be honest, its the 1st of the year and the last thing I need to be doing is messing with technology.....
Click to expand...
Click to collapse
It's no problem, this isn't a dumb question or easy issue by any means. If the method I directed to you doesn't work, let me know. There is another way to do it without all the code.
slapshot30 said:
I haven't told anyone how to do it surprisingly, and I'm more than happy to help . I was honestly thinking about adding reverting back to stock to the superguide, and I think I just may do that. Here is the link. Pirateghost is the man.
http://forum.xda-developers.com/showpost.php?p=20821226&postcount=4
Click to expand...
Click to collapse
Worked perfectly. I flashed it back to stock using the thread you linked me to. Then I did the CWM Root method and so far so good. I appreciate all of your help
Nice, I'm glad you were able to get everything working.
Sent from my HTC PH39100 using xda premium
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Jetboard said:
Okay so, since I'm sort of new, I wanted to ask a few questions:
1. Is it possible to root xperia x8 with manufacturing date 11w48? At least at 95% chance. I'm a bit scared of the bricking part...
2. If it is possible, what kind of "ROM" (if I understood correctly) should I get?
3. If I get hard bricked/soft bricked what's the chance my phone will be still usable.
That's about it. Please don't rage at me for "OMG USE SEARCH BUTTON" type of thing.
I have tried doing it but no results found. Just threads and posts of people updating their.. ROMs I gues? Correct me if I typed anything wrong there.
But yeah, help would be appreciated. Thanks!
Click to expand...
Click to collapse
1. You can safely root your x8 regardless of when it is manufactured, you will not brick it
2. You have 11w48 so it is very risky to unlock your bootloader, i suggest you flash ROMS that is for stock
3. If you get soft bricked you can flash the stock firmware back using flashtool or SEUS, if it is a hard brick, you need to go to the nearest Service center or use a JTAG
Swyped via Tapatalk 2
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Jetboard said:
Thanks a whole bunch. I thought I cannot root because of my manufacturer date. But what is a flash ROM tho?
Click to expand...
Click to collapse
you can root your phone. but you can't unlock bl.
when you root your phone, you cam install cwm recovery. simply dl a rom for stock kernel and go to recovery and install(flash) the rom. remember to check the instructions first.
Just because i don't doesn't mean i can't.
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
F308 said:
All what I found until today was that if I cannot unlock BL I cannot install CWM recovery.
Maybe it is related to model - mine is Sony Xperia J. Y2012.
There is no fastboot available.
Am I wrong, can I have CWM, nandroid backup etc on stock ROM as only such one I may flash ?
Click to expand...
Click to collapse
this is for x8. not sure how it works on J. but yeah we don't havt fastboot either. but we can install cwm even with a locked bl. again that's for se x8.
edit: my advice is go to your phone's subforum. you'll get your answers there.
Just because i don't doesn't mean i can't.
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
F308 said:
Thank you. I understand that lot of things is device dependent but thought there are non-breakable rules, like gravity,
and what is possible to do under certain circumstances was one of them.
Need walk through XDA forum once more, maybe there is a hope.
Click to expand...
Click to collapse
there probably are a few unbreakable rules, but not being familiar with your device i can't guarantee that it's safe or it would work.
Just because i don't doesn't mean i can't.
Despite lot of reading I still am missing knowledge.
Question is:
What is fastboot ?
I found more than one definition of it and compiled into my own.
1.
Of course fastboot.exe is Windows binary (part of flashtool pack) which does certain type of work.
This is not what we are interested in.
2.
I concluded that:
- fastboot is one of modes into what android device can wake up. Just like linux can boot in different ways or Windows into single mode.
- this feature is encoded into boot.img, it is not separate android application.
- boot.img will work only with related kernel.img. They are like love and marriage (which is like horse and carriage - Bundy's).
- Sony sometimes disables stock boot.img to boot into this mode then without replacing boot .img it is impossible.
More comments ?
Fastboot is protocol used to update the flash filesystem in Android devices from a host over USB. It allows flashing of unsigned partition images.
Just because i don't doesn't mean i can't.
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is okay.
Um, I tried that one it didn't work. It said some stuff are missing, then it exited randomly etc.. Can someone give me a link or a short/long guide which I can use that's latest? I do have some X8 drivers in a .zip file but no idea how to install them. Thanks in advance.
Jetboard said:
Okay, I got one more last question. Is this guide http://forum.xda-developers.com/showthread.php?t=906195&nocache=1 okay to use for rooting? I'm still trying to find the LATEST safe ones =/ I wonder if this one is good.
Click to expand...
Click to collapse
I rooted mine with this
Means its safe
Sent from my X8
Having few issues with the SuperOneClick thing... It sometimes randomly exits, tells me that some stuff are missing etc. Any help? =/
Using this guy's guide for the Nexus 5 I had no issues, bought a N6 today and was giddy to flash on Cataclysm for N6 and figured might as well use same person's guide for next phone up.
http://www.androidrootz.com/2014/12/how-to-root-nexus-6-windowsmaclinuxubun.html
Was able to unlock bootloader, then installed TWRP but now am getting the 'corrupt phone' message, however unlike others like I have read on XDA, am unable to boot up by just letting it sit. Screen turns off and that's that. Before beginning entire process I enabled "enable/allow oem unlocking". I'm assuming that when the phone factory resets after the bootloader unlock I need to go back in and recheck 'allow oem unlock' in dev options, but I didn't as I assume/ed that it wasn't necessary and the guide doesn't tell you to.
Tried relocking the bootloader to maybe get phone to open up, but terminal tells me that I need to have 'allow oem unlock' checked. Nice Catch-22 http://puu.sh/moOUf/d0f8fa9050.png
Tried formatting data from within TWRP and factory resetting/wiping everything but it tells me that it is unable to mount '/data'
Have since tried WugsToolkit and flashing to stock with 'softbricked' option enabled the shamu-mmb29k-fact....tgz image that I downloaded and imported myself into Wugs (was taking 10 minutes to dl 1%). That seemed to work and told me it was a success, however when I then went back to re-enable the bootloader via wugs it fails and reboots with the lock sign still open and boots again onto 'corruption' screen that then flashes off and turns phone off, left it for 30 minutes at one point and didn't boot so don't think I'm lucky enough to be able to sit if through like others who had that issue
Where to go from here? Really hoping I didn't brick this phone less that 3 hours after getting it. I can still boot and see the Google screen and can get onto the bootloader and used to be able to get into recovery (since wugs have been getting the android with red triangle)
Been rooting/rom'ing since day one that I've had androids. Had a Samsung Apollo with CM on it, same for the Nexus S, then the Galaxy Nexus, then the N5 and looks like my chain of no issues ended tonight
Anything you can do for guys would be greatly appreciated. No clue where to go from here....
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
DO NOT RELOCK THE BOOTLOADER!!!!! I cannot emphasize how critical it is that you do not relock the bootloader, given the position you are in. If you somehow manage to relock the bootloader and "enable OEM unlock" is toggled off and Android will not boot (even after attempting a factory reset), then you are 100% bricked with no way to fix your phone. Personally, I leave my bootloader unlocked 100% of the time so that I can fix anything that may go wrong with my phone. Additionally, I (as well as many other users on here) will always advise against using Wug's or any other toolkit in order to do stuff to your phone. While they do provide a nice GUI as well as an easy way to install the necessary drivers, using the regular platform-tools command line method isn't all that hard to figure out, and it allows you to know exactly what you have done to your phone. With Wug's and the like, you never really know what commands that they are running and exactly at what point in the process a flash may fail. Right now, I would advise you to read up on using the platform-tools method to flash stock images. After you have all of the necessary drivers, platform-tools, etc. working properly on your computer, I would strongly advise that you download MMB29S (the latest official update) from the Google Developer page and flash it using the platform-tools method, NOT with Wug's. And whatever you do, I repeat, DO NOT LOCK YOUR BOOTLOADER!
---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------
triguyrn said:
So from what I gathered, I think you are in luck. It sounds like your bootloader is unlocked. This is a very good thing. Under no circumstances do you want to try to re lock it right now or do you ever when stuck not being able to boot or any issues like that. If you lock it while stuck, thats when you are soft bricked. If I remember correctly, I got myself in the same situation , although maybe with out a custom recovery installed. None of that matters though. The way to fix this is to reflash the the factory image. Here are the guides for that.
https://www.youtube.com/watch?v=K_m6bYNKrXQ
This is the video I used the first time. A bit rough but, It did the job.
https://www.youtube.com/watch?v=2hao_Yf-gaw
Here is a bit of a nicer one. I used it the second time around.
and lastly here is an xda post http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
I would recommend reading and watching all of these and maybe doing more research so you really knows whats going on. The flash-all script is not going to work from what I've read and I've always done it manual so go with that. It may also be a good idea to keep the custom recovery, so look into to keeping that. Maybe it is as simple as not erasing the recovery partition and not flashing the recovery image. This is what should save your nexus.
Now, I am fairly new to the Rooting and ROMming, really only started 2 months ago, so I would really appreciate if any of the more experienced guys on XDA can confirm what I said. Please don't try any of this without confirmation from another member here, I do not want to be responsible for sending your device past the point of no return. I recently had to order a new Nexus 6 as the screen is dead, so I know it's frustrating to have that loss. In your case, as long as that boot loader is unlocked, you should be safe. Best of luck to you.
Click to expand...
Click to collapse
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
matthew2926 said:
Regarding the flash-all script, my friend and I just used the script included with MMB29S and it worked fine. In addition, I was able to use the one with MMB29K, MRA58K and MRA58R, all of which worked fine. I'm not sure if these scripts always work for some users and never work for others, but I always recommend that people who are new to flashing simply try them, as they are quite convenient when they work. In addition, I have only been in the rooting and ROMing scene for about a month or two as well, but I would consider myself pretty seasoned by now considering all the different ROMs, rooting methods, etc. that I have tried. All the advice that you gave to the OP is excellent and I agree with it all.
Click to expand...
Click to collapse
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
No problem! It's too bad to hear about your device but at least you got a new one on the way. There is really no harm to at least trying the flash-all script. It will either work and save you time or fail halfway through and force you to flash everything manually.
triguyrn said:
Thank you. I always wanted to try the flash-all script but, I ahve read a few places it wouldn't work and haven't had the chance to give it a try lately. When my new device arrives in a day or two, I'll give it a shot. Thanks for the confirmation, makes me feel good knowing I'm starting to get the hang of this stuff
Click to expand...
Click to collapse
Flash-all script is still broken, flash the img files individualy in fastboot.
gee2012 said:
Flash-all script is still broken, flash the img files individualy in fastboot.
Click to expand...
Click to collapse
You guys are life savers, thank you so much
Got it to work after I was getting ready to phone it in and bring it to a repair shop and eat whatever the charge might've been
Hi, I tried rooting with this \CF-Auto-Root-gts210ltespr-gts210ltespr-smt817p.tar.md5
And I seem to have missed a step? I am stuck with a black screen and red font with something along the lines of not seandroid enforcing on recovery. Away from tablet at the moment. Was curious if this is expected? and if so? Next step?
I was trying to simply root it, but at this point, I'd like to know if it is bricked or simply fixable to a working state, because I'd like to use it obviously.
Let me know ASAP, because I'd like to tackle this at home shortly.
ZeroComputing said:
Hi, I tried rooting with this \CF-Auto-Root-gts210ltespr-gts210ltespr-smt817p.tar.md5
And I seem to have missed a step? I am stuck with a black screen and red font with something along the lines of not seandroid enforcing on recovery. Away from tablet at the moment. Was curious if this is expected? and if so? Next step?
I was trying to simply root it, but at this point, I'd like to know if it is bricked or simply fixable to a working state, because I'd like to use it obviously.
Let me know ASAP, because I'd like to tackle this at home shortly.
Click to expand...
Click to collapse
You can either using Odin to reflash the stock ROM that you can download from Sammobile and start all over. I did that myself. Or you can try to getting to TWRP mode by Power+Home+Volume Up buttons to wipe the Dalvik cache. I read that on the other forum, but this did not work for me.
I realize, with the brevity of my last message, I came off uncoordinated, and impolite. I apologize fervently, and ask your forgiveness. I would please like some help with this device, as it is a new thing for me.
Have you enabled OEM Unlocking in Developer Options?
ZeroComputing said:
I realize, with the brevity of my last message, I came off uncoordinated, and impolite. I apologize fervently, and ask your forgiveness. I would please like some help with this device, as it is a new thing for me.
Click to expand...
Click to collapse
No problem with that, you got that fixed now? or you are asking a step by step instruction here?
Yes, I managed to restore to working. Not necessarily a step by step, just a generalized summary and possibly names of correct files, TWRP version for instance. Then once I flash TWRP I flash the 817 bootimg, and then super su? correct? No I did not enable OEM unlock, I feel outdated lol.
I gues my question is... should the autoroot work if oem unlock is enabled?
Managed to root after reading 20 plus pages for my device... now the question is, which roms work for the t817. Being wifi only doesnt matter. Not currently using the lte in mine.