I was rooted on 7.3.0 from the day I got my replacement kfhd less than a month ago. I forgot to turn off automatic updates and yesterday 7.3.1 installed and immediately I'm having problems. Some apps I had installed are gone, like No Lock and Apex Launcher (I'm almost positive that's which one I was using) for starters. I tried to reinstall No Lock since I have Nova Launcher working and I'm sick of unlocking twice. Downloaded No Lock, went into ES File Explorer to move it, and there is NOTHING in /data/app to move.
I'm almost afraid to see what other problems there are. I downloaded a root checker and it says I'm not rooted anymore. Well that explains a lot. However Google Play has hung around problem free, which you did need root for.
How should I proceed? I fried my fiancee's kfhd a month ago after I rooted it. I was attempting to install TWRP, screwed up, and bricked it. She went out and bought another tablet. I called Amazon and told them it just died for no reason so they sent a replacement which became mine. If I brick another kfhd I don't think Amazon is going to want to replace it again.
I know 7.3.1 was just sent OTA and not to everyone a few days ago (found that info on the forum somewhere) so has anyone re-rooted after getting it? What other things can I safely try?
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
MightyBraeburn said:
It might seem kind of obvious but why not simply root again? I don't see any reason why it wouldn't work. I rooted my KFHD running 7.2.3 with Kindle Fire First Aide no problem. I'd imagine that 7.2.1 should be no problem. If you follow the steps in this thread it's pretty easy.
Also I should mention that it's pretty difficult to really brick your KFHD. If you get a factory cable (either make one yourself or order one from SkOrPn on here for pretty cheap) you can almost always fix any software problems. The factory cable essentially puts the KFHD in "factory" mode which lets you flash it in fastboot almost regardless of anything you've manage to damage. I messed up my KFHD pretty bad (stuck at the boot logo and would refuse to be be detected at all via usb) but with a factory cable it was super easy to fix.
Click to expand...
Click to collapse
Rooting it again would probably work from what I know about rooting phones. I'm kinda hoping someone else has already done it so I know for certain that it's gonna work before I do it.
Maybe I have to be the person who finds out if simply rooting again fixes the issue.
Rooting again should fix the problem. I would try that first.
Worst case scenario it doesn't help and you have to do a factory restore or re-flash in which case you can simply restore a clean copy and then either disable the OTA updates or else, better yet, let it update all the way to 7.2.3 and then root the latest version.
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
SGoatS said:
Yeah, I think I'll give rooting it a shot. I PM'ed the guy that made the Kinology 7.3.1 ROM about rooting and then flashing recovery from where I'm at right now since I can't post in the “development" forum until I have 10 posts. He also said it should go fine from where I'm at. I'd love to flash that ROM, I'm just afraid of screwing up since I massively screwed up the first time I flashed a recovery.
I'll give it a shot tonight when I've got time to mess with it.
Click to expand...
Click to collapse
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
-a- said:
It's not hard as long as you follow the instructions... It works flawlessly on mine.
Click to expand...
Click to collapse
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
SGoatS said:
Well I'm happy to say that rooting again after the 7.3.1 update Amazon snuck in on us went perfectly. So when others get that update and aren't sure if they can root again easily I hope they see this thread and know that it is no different than the first time you rooted.
My only concern is messing up the TWRP install. If I actually read the instructions a few times before doing it I shouldn't mess it up this time. I'm gonna look into it some more this week in my spare time and convince myself to do it. The extra encouragement of it working no problem is appreciated.
Click to expand...
Click to collapse
You're welcome.
Sent From my Kindle Fire HD running CM10.1
Related
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
Can I get a link to a thread on a WORKING method to root the KF2 running firmware version 10.1.3? There are thousands of people out there with old versions of rooting that do not WORK. Extremely frustrated. I've wasted a lot of time, and I cannot find what I am looking for in any threads.
I have installed drivers onto my machine and now need to get TWRP to show Online. It says offline all the time and I'm wondering if I simply haven't gained access to the correct version?
PLEASE! Help.
Zinja
zinja said:
Can I get a link to a thread on a WORKING method to root the KF2 running firmware version 10.1.3? There are thousands of people out there with old versions of rooting that do not WORK. Extremely frustrated. I've wasted a lot of time, and I cannot find what I am looking for in any threads.
I have installed drivers onto my machine and now need to get TWRP to show Online. It says offline all the time and I'm wondering if I simply haven't gained access to the correct version?
PLEASE! Help.
Zinja
Click to expand...
Click to collapse
I think you're getting a little confused here. First of all, TWRP never shows online or offline...It's custom recovery that sits on your recovery partition. You're probably thinking of KFU. Second, neither TWRP nor KFU work for the 2nd gen Kindle Fires. You cannot install any ROMs on the 2nd gen KFs, only root them. There are instructions for rooting them, but they aren't anything like the original.
http://forum.xda-developers.com/showthread.php?t=1893838
Thank you!
soupmagnet said:
I think you're getting a little confused here. First of all, TWRP never shows online or offline...It's custom recovery that sits on your recovery partition. You're probably thinking of KFU. Second, neither TWRP nor KFU work for the 2nd gen Kindle Fires. You cannot install any ROMs on the 2nd gen KFs, only root them. There are instructions for rooting them, but they aren't anything like the original.
http://forum.xda-developers.com/showthread.php?t=1893838
Click to expand...
Click to collapse
1. Thank you for clearing up my confusion on TWRP and KFU. You were correct.
2. I will follow insturctions on the new root method.
3. I want to make sure: NO ROMs are working yet on the KF2? Thanks, Amazon? Will someone crack that? Are you optimistic?
4. I also want to make sure: this is now bogus? Or never WAS for the KF2? Only KF1? ---> http://www.ibtimes.co.uk/articles/3...kindle-fire-miui-android-jellybean-update.htm
zinja said:
1. Thank you for clearing up my confusion on TWRP and KFU. You were correct.
2. I will follow insturctions on the new root method.
3. I want to make sure: NO ROMs are working yet on the KF2? Thanks, Amazon? Will someone crack that? Are you optimistic?
4. I also want to make sure: this is now bogus? Or never WAS for the KF2? Only KF1? ---> http://www.ibtimes.co.uk/articles/3...kindle-fire-miui-android-jellybean-update.htm
Click to expand...
Click to collapse
No, there are no ROMs - check out the thread here:
http://forum.xda-developers.com/forumdisplay.php?f=1786
no99sqrd said:
No, there are no ROMs - check out the thread here:
http://forum.xda-developers.com/forumdisplay.php?f=1786
Click to expand...
Click to collapse
Thank you for the link to the thread, in which I will eventually find what I am looking for.
I now see info in there that is for the KF2HD and that the new ones are locked?
Is there specific direction for KF2's and how to frickin' root them?
zinja said:
Thank you for the link to the thread, in which I will eventually find what I am looking for.
I now see info in there that is for the KF2HD and that the new ones are locked?
Is there specific direction for KF2's and how to frickin' root them?
Click to expand...
Click to collapse
The KF2s are the same way. They're already running ICS, so rooting and installing a new launcher is usually sufficient to get a decent tablet experience, but you still won't get the typical ICS interface you might be used to. You won't have any kind of decent recovery to fall back on in case something goes awry, so you should be very careful when messing with files you wouldn't normally have access to. If you do decide to go with a launcher, stay away from the ICS launcher. As tempting as it may be, it has caused a good number of the original KFs to be bricked, requiring the intervention of a custom recovery to fix.
As far as installing any kind of ROMs, you might as well forget about it for now. The motivation for getting past the new KFs security seems to have dwindled quite a bit in the last couple of weeks, and I personally think it's not going to happen, but you never know...
ComputerStill Can't Get My ComputerToo Recognize the Kindle. Looks A-ok In Device Manager.
Ive Read A Lot About The Usb .Ini Drive File And Doing Something With It. What Am I Doing Wrong? ADB tools And SDK are Installed, When I Run The Rootqemu File It Is Stuck At Mailer Demon Startered Successfully (Or Whatever It Says Officially).
A LittlE Korehelp Here Should Get Me There...
Hello to everyone!
First of all, english is not my native language, so please forgive my bad english
Here is my current problem:
I was working around with my new Kindle Fire HD 7'' (v. 11....), rooted it succesfully, everything was running smoothly.
So i was reading my way through some new posts in here on how to remove and get rid off the commercials on the Kindle.
One comment I saw was suggesting the following:
"You will need to have root access first.
Remount /system as read/write
Enter /system/app and rename or delete dtcp* (forgot the rest of the name.
Reboot
Enjoy."
After reading this, I did exactly what the user was suggesting and proceeded to delete both files I found in the "add"-folder beginning with "dtcp".
After doing this, my Kindle already started throwing some errors, so I went on to rebooting the device.
After that, I came into my current situation, with a red triangle showing up, offering me to reset the device to factory settings, which doesn't help me either. I'm basically stuck in a boot-loop atm.
I would really appreciate any help with this and thanks in advance!!
Greetings
You need a fastboot cable to fix it, you have to reflash the system partition with kindle fire first aid once it is in fastboot.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Edit: if you can't see since the xda app apparently doesnt support stike tags, that was incorrect above because i misread something. so strike that out in your mind if you dont see it stiked through. xD
cruzersteve said:
Hello to everyone!
First of all, english is not my native language, so please forgive my bad english
Here is my current problem:
I was working around with my new Kindle Fire HD 7'' (v. 11....), rooted it succesfully, everything was running smoothly.
So i was reading my way through some new posts in here on how to remove and get rid off the commercials on the Kindle.
One comment I saw was suggesting the following:
"You will need to have root access first.
Remount /system as read/write
Enter /system/app and rename or delete dtcp* (forgot the rest of the name.
Reboot
Enjoy."
After reading this, I did exactly what the user was suggesting and proceeded to delete both files I found in the "add"-folder beginning with "dtcp".
After doing this, my Kindle already started throwing some errors, so I went on to rebooting the device.
After that, I came into my current situation, with a red triangle showing up, offering me to reset the device to factory settings, which doesn't help me either. I'm basically stuck in a boot-loop atm.
I would really appreciate any help with this and thanks in advance!!
Greetings
Click to expand...
Click to collapse
Don't know what you did but you will have to wait and see if the bootloader gets any exploits because you have to factory reset that way now. I suggest you see if you can get an exchange. Amazon is great about that. There are no other options for you at at the moment.
LinearEquation said:
Don't know what you did but you will have to wait and see if the bootloader gets any exploits because you have to factory reset that way now. I suggest you see if you can get an exchange. Amazon is great about that. There are no other options for you at at the moment.
Click to expand...
Click to collapse
Alright thanks a ton for the advice.
I got in touch with Amazon support over chat, and the person talking to me was making almost an interrogation out of it since I think they were suspecting that I had bricked the Kindle by rooting it or something similar. But in the end they decided to send me a replacement device.
In addition, they told me I'd get notice from them as soon as they get to examine the state of the old Kindle. You think I'll have to expect any consequences of this if they get to figure out I bricked it by deleting something on root-level which I wasn't supposed to delete?
I just hope they won't make a big deal out of it.... :/ I just hope they won't say I voided the warranty and make me pay for the repair or something
Greetings!
Alright thanks a ton for the advice.
Click to expand...
Click to collapse
You're welcome.
You think I'll have to expect any consequences of this if they get to figure out I bricked it by deleting something on root-level which I wasn't supposed to delete?
I just hope they won't make a big deal out of it.... :/ I just hope they won't say I voided the warranty and make me pay for the repair or something
Click to expand...
Click to collapse
Not likely. They will most likely check for signs of physical damage and send it back to China. I don't think they have scoping capabilities at the return center.
Oh my bad I didn't see the version 11 part in the op, yea those steps I posted are kinda invalid on a 3rd gen kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
stunts513 said:
Oh my bad I didn't see the version 11 part in the op, yea those steps I posted are kinda invalid on a 3rd gen kindle.
Sent from my Amazon Kindle Fire HD running CM10.1 Tablet UI using xda-developers app
Click to expand...
Click to collapse
**** happens. But I think it would be nice if you could correct yourself in the mentioned post so that we can avoid other people to follow the instructions as well and brick their Kindles that way
But besides that, any idea why my Kindle got bricked just by deleting those 2 files that, afaik, only belong to the Amazon-ads-app?
Is it because the app is actually signed, which they introduced with the 3rd gen Kindles?
If that's the reason, that's pretty dumb from Amazon in my opinion, forcing those ads that hard
Greetings
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
hey guys hopefully ive gotthis in the right thread,
i have an amazon fire 7inch tablet i tryed to install cyno 12 onto it threw flashfire, everything went okay but then it restart and basically has got stuck on the logo of the cyno.. i have tryed getting intorecoverying by useing the power and down button .. seems to be no recovery screen there. i can tho get into boot screen, does anyone know how to get recovery screen on to it again to install stock rom etc.. its putting my head away lol
Without being able to boot into Amazon's recovery, your only option is to ask Amazon for a replacement if still under warranty.
If out of warranty and were on 5.0.x, you can try the unbrink with custom recovery but does not look promising.
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4.
There is a good chance when you flashed the new ROM, the order was not correct for the wipe. See:
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
There are plenty of posts on this subject, you could search those and see if someone finally found a solution, but as far as I know, not yet.
shabuboy said:
Without being able to boot into Amazon's recovery, your only option is to ask Amazon for a replacement if still under warranty.
If out of warranty and were on 5.0.x, you can try the unbrink with custom recovery but does not look promising.
http://forum.xda-developers.com/showpost.php?p=62986666&postcount=4.
There is a good chance when you flashed the new ROM, the order was not correct for the wipe. See:
http://forum.xda-developers.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
There are plenty of posts on this subject, you could search those and see if someone finally found a solution, but as far as I know, not yet.
Click to expand...
Click to collapse
Concure - no unbrick solution that I'm aware of.